1. OmniRAN EC SG May 2nd, 2013 Conference Call
Max Riegel
(OmniRAN SG Chair)

2. Meeting Thursday, May 2nd, 2013, 09:00-10:00 AM ET Conference Call:
September 2012
doc.: IEEE /0996r3
Meeting
Thursday, May 2nd, 2013, 09:00-10:00 AM ET
Conference Call:
Call-in number: 1-(972) (US)
Global numbers:
Conference Code: #
WebEX
Meeting Number: 
Meeting Password: OmniRAN
Stephen McCann, RIM

3. Guidelines for IEEE-SA Meetings
All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws.
Don’t discuss the interpretation, validity, or essentiality of patents/patent claims.
Don’t discuss specific license rates, terms, or conditions.
Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings.
Technical considerations remain primary focus
Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets.
Don’t discuss the status or substance of ongoing or threatened litigation.
Don’t be silent if inappropriate topics are discussed… do formally object.
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit
See IEEE-SA Standards Board Operations Manual, clause and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.
This slide set is available at

4. Resources – URLs Link to IEEE Disclosure of Affiliation
September 2012
doc.: IEEE /0996r3
Resources – URLs
Link to IEEE Disclosure of Affiliation
Links to IEEE Antitrust Guidelines
Link to IEEE Code of Ethics
Link to IEEE Patent Policy
Clint Chaplin, Chair (Samsung)

5. September 2012
doc.: IEEE /0996r3
Meeting Etiquette
IEEE 802 is a world-wide professional technical organization
Meetings are to be conducted in an orderly and professional manner in accordance with the policies and procedures governed by the organization.
Individuals are to address the “technical” content of the subject under consideration and refrain from making “personal” comments to or about the presenter.
The Copyright Act of 1976 made a dramatic change to U.S. copyright law. Copyright was now deemed to exist from the moment of creation. Thus anything that is created is deemed to be owned by its creator. Additionally, a work no longer needs to be published in order to be protected. Therefore, even your scribbles on a piece of note paper constitute copyrighted material that you own and control.
The NII (National Information Infrastructure) and the GII (Global Information Infrastructure) are causing lawmakers and copyright owners to assess the ability of current copyright law to protect owners rights in a digital environment. While at this point the changes being talked about are not significant, they will make it clear that copyright protection is afforded to owners in the digital environment making it a requirement to honor the rights accorded to owners.
It is a requirement under the IEEE Bylaws that copyright ownership of all material published by the IEEE resides with the IEEE. The Standards Department accomplishes the transfer of copyright ownership from the volunteer authors to the Institute via the Project Authorization Request (PAR) form.
Stephen McCann, RIM

6. LMSC Operations Manual
4.3 Study groups
4.3.1 Study group operation
Progress of each Study Group shall be presented at the closing Sponsor meeting of each IEEE 802 LMSC plenary session by the appropriate WG, TAG, or ECSG Chair. Study Groups may elect officers other than the Chair, if necessary, and will follow the general operating procedures for WGs specified in the IEEE 802 LMSC WG P&P. Because of the limited time duration of a Study Group, no letter ballots are permitted.
4.3.2 Voting at study group meetings
Any person attending a Study Group meeting may vote on all motions (including recommending approval of a PAR). A vote is carried by 75% of those present and voting “Approve” or “Disapprove.”

7. Agenda Thursday, May 2nd, 09:00–10:00am ET
September 2012
doc.: IEEE /0996r3
Agenda Thursday, May 2nd, 09:00–10:00am ET
Call Meeting to Order
Secretary position
Approval of minutes
Reports
Conclusion on list of use cases
Draft use cases document
Call for comments on use cases document
Classification of functional requirements
Review of project plan and timeline
Agenda for May ’13 interim session
AOB
Adjurn
Stephen McCann, RIM

8. Business#1 Call Meeting to Order Appointment of recording secretary
Antonio and Juan Carlos will take notes
Roll Call
Name
Affiliation
Max Riegel
NSN
Juan Carlos Zuniga
Interdigital
Antonio de la Oliva
UC3M
Hyunho Park
ETRI
Roger Marks
Consensii

9. Business #2 Approval of agenda Approval of minutes Reports
approved without objections
Approval of minutes
minutes uploaded
approval postponed to next session due to late availability
Reports
no formal response received yet from 3GPP
Antonio reported about ongoing activities on SDN
working on more comprehensive contribution for next session
more information desired on the P project as it seems to have close relation with SDN

10. Business #3 Contributions on OmniRAN use cases
no new contributions available
Draft use cases document
no new input for this session
Call for comments on use cases document
no comments received so far
Classification of functional requirements
contribution considered helpful to structure results of OmniRAN for acceptance by IEEE 802 and communication with other SDOs
Revision of figure on slide 16 requested to more clearly distinguish R1 from the other reference points and to be more specific that R3 control does not address physical layer parameters on the wired backhaul
Conclusion on slide 19 should also mention the creation of an informative document specifying the overall OmniRAN architecture
revised slides uploaded after call under
Review of project plan and timeline

11. Business #4 Task of OmniRAN EC SG
To perform a gap analysis that shows what pieces of work that are relevant to 802 (standards and standards under development) are not covered by existing external SDOs  (IETF, 3GPP,...) and internal, and socialize that analysis with those SDOs;
Having performed that gap analysis, define a crisp scope of the ECSG (target 15 words or less);
Define what piece(s) of work within that scope (a) fall legitimately within 802's remit and (b) are achievable within an 802 activity.

12. Business #5 Plan and Timeline (EC SG Motion)
Mar’21
Apr’11
May’2
Jun’15
Jul’15
Initial meeting
Use cases contributions
Draft Use cases document
Stretch activities out until end of Jul’13 plenary
Socialize results with IEEE 802 and external SDOs
Call for comments on Use cases document
Use cases document finalization
Classification of functional requirements
Prioritization of functional requirements
Gap analysis to existing solutions
Decision about initial topic
Initial PAR text
Draft PAR completed for EC submission
Finalization of PAR proposal ?
Conf Call
F2F meeting
Jan
Feb
Mar
Apr
May
Jun
Jul

13. Business #6 Plan and Timeline (EC SG Motion)
Mar’21
Apr’11
May’2
Jul’15
Initial meeting
Use cases contributions
Draft Use cases document
Call for comments on Use cases document
Use cases document finalization
Classification of functional requirements
Functional requirements within scope of IEEE 802
Gap analysis to existing solutions
Socializing of gap analysis
Potential standardization topics for IEEE 802
Refine scope of EC SG (crisp words) ?
Conf Call
F2F meeting
Jan
Feb
Mar
Apr
May
Jun
Jul

14. Business#7 Review of project plan and timeline
Slightly revised project plan and timeline accepted without objections
Defining crisp wording for scope will be addressed in the Jul ‘13 session when other results are available
Agenda for May ‘13 Waikoloa session
agenda agreed with slight modifications in the agenda proposal
revision uploaded as
AOB
nothing brought up
Adjurn
adjurned at 10:38 AM ET