omniran13 0051 00 ecsg Omni RAN EC SG

omniran-13 -0051 -00 -ecsg Omni. RAN EC SG July 2013 Opening Report Chair: Max Riegel, NSN 1

omniran-13 -0051 -00 -ecsg Omni. RAN EC SG Objectives and Status • When renewing the Omni. RAN EC SG on March 22 nd the IEEE 802 EC refined the objectives for the Omni. RAN 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, 3 GPP, . . . ) 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. • The Omni. RAN EC SG completed the gap analysis and defined required activities in scope of IEEE 802. • Dissemination of the results has started and will continue during the July 2013 session • The investigations led to a more complex picture of required standardization activities. 2

omniran-13 -0051 -00 -ecsg Omni. RAN EC SG Results: Topics for Standardization in IEEE 802 • The discovered gaps in IEEE 802 technologies should be addressed by the related IEEE 802 WGs • Establishing a common approach of specifying ‘external’ control into IEEE 802 technologies would require: – specifications of the control attributes for the individual IEEE 802 technologies by their working groups • (normative, in annex of related specifications to ensure consistency) – a specification describing the ‘Omni. RAN’ Network Reference Model and listing the DL and PHY control functions demanded for access networks and SDN • (informative) – a specification on the usage of IP protocols for the transport of IEEE 802 attributes and the definition of IEEE 802 attributes for such IP protocols • (informative for IEEE 802, probably in cooperation with IETF) • The discussions in the July 2013 session will mainly address the progressing of the standardization topics mentioned above. • It is not clear yet, whether Omni. RAN EC SG will ask for an extension until the November 2013 session. – Depends on agreement in Omni. RAN EC SG on objectives for an extension 3

omniran-13 -0051 -00 -ecsg July 2013 Omni. RAN F 2 F Schedule Mon 08: 00 Tue EC Opening Session Wed Thu Fri Joint w/ 802. 11 ARC 10: 00 10: 30 IEEE 802 Opening Plenary 12: 30 13: 30 Mtg w/ 802. 19 Omni. RAN Opening Meeting Joint w/ 802. 21 Omni. RAN Closing Meeting EC Closing Session 15: 30 16: 00 Mtg w/ 802. 24 18: 00 4

omniran-13 -0051 -00 -ecsg Omni. RAN ECSG Resources • Website: http: //www. ieee 802. org/Omni. RANsg/ • Document Archive on mentor: https: //mentor. ieee. org/omniran/documents • Email reflector: ecsg-802 -omniran@listserv. ieee. org • Email archive: http: //grouper. ieee. org/groups/802/Omni. RANsg/email/ • Attendance: Paper list (normative) + IMAT – IMAT mandatory for participants seeking attendence credits – Reciprocal rights for most WGs 5