1. OmniRAN EC SG Agenda May 2013, Waikoloa, HI
Max Riegel
(OmniRAN SG Chair)

2. Meetings Monday, May 13th, 10:30 – 12:30
September 2012
doc.: IEEE /0996r3
Meetings
Monday, May 13th, 10:30 – 12:30
Tuesday, May 14th, 10:30 – 12:30
Tuesday, May 14th, 13:30 – 15:30
Wednesday, May 15th, 08:00 – 10:00
Wednesday, May 15th, 13:30 – 15:30
Thursday, May 16th, 10:30 – 12:30
Thursday, May 16th, 16:00 – 18:00
Meeting Room:
King’s 1
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. OmniRAN ECSG Resources
Website:
Document Archive on mentor:
reflector:
archive:
Attendance: Paper list (normative) + IMAT
IMAT mandatory for participants seeking attendence credits
Reciprocal rights for most WGs

8. Agenda Call Meeting to Order Attendance recording Secretary position
September 2012
doc.: IEEE /0996r3
Agenda
Call Meeting to Order
Attendance recording
Secretary position
Approval of minutes
Reports
Feedback from 3GPP on liaison letter
OmniRAN scope and extension by Mar ‘13 closing EC plenary
IEEE 802 view on OmniRAN architecture
Establishment of architecture document
Conclusion on OmniRAN use cases
Review of use cases document
Gap analysis for the agreed use cases
Communication with external organizations
Plan and timeline for OmniRAN SG conclusion
Future sessions of OmniRAN EC SG
Summary report for communication inside IEEE 802
AOB
Adjourn
Stephen McCann, RIM

9. Agenda Scheduling Mon Tue Wed Thu 08:00 10:00 10:30 12:30 13:30 15:30
Smart Grid use case w/ gap analysis
10:30
12:30
Opening
Planning for the week
Approval of minutes
Reports
OmniRAN within the IEEE 802 scope and architecture
Structuring and composing of output documents
13:30
15:30
SDN Use Case
SaMOG and Wi-Fi Roaming use case /w gap analysis
16:00
18:00
Review and approval of output documents
Communication
Planning until July

10. May 2013 Session - #1 Call Meeting to Order Attendance recording
Please use paper sheets – and IMAT for attendance credit
Secretary position ?
Approval of minutes
March Orlando F2F session
April 11th conference call
May 2nd conference call
Reports
OmniRAN liaison letter to 3GPP SA2
Sent out on March 28th, 2013
So far no response received
OmniRAN extension by EC closing plenary in March ‘13
See next slide

11. #2 Refined directions provided by EC
After some hefty discussions OmniRAN was extended until end of July ‘13 plenary.
The EC provided further guidance for the tasks of OmniRAN ECSG:
Motion#28 The EC considers that the primary tasks of the OmniRAN ECSG, to be completed by the close of the July Plenary, are:
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.
Moved Jeffrey Second Thaler Results 8 / 2 / 3 Motion Passes

12. #3 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. #4 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. #5 May 2013 Objectives Conclude on contributions on OmniRAN use cases
Finalize use cases document including functional requirements based on agreed contributions
Establish architecture document aligned to existing IEEE 802 views to distinguish between functionality in scope of IEEE 802 and functionality out of scope.
Draft document on gaps to available IEEE 802 functionality for the agreed use cases
Plan for internal and external communication to retrieve feedback on architectural view and gaps document
Review and refine timeline and plan for creation of deliverables until Jul ‘13

15. May 2013 Session #6 IEEE 802 view on OmniRAN architecture
Establishment of architecture document
Conclusion on OmniRAN use cases
Review of use cases document
Gap analysis for the agreed use cases
Communication with external organizations
Plan and timeline for OmniRAN SG conclusion
Future sessions of OmniRAN EC SG
Summary report for communication inside IEEE 802
AOB
Adjourn