1 / 15

IEEE 802 OmniRAN EC SG July 2013 Conclusion

IEEE 802 OmniRAN EC SG July 2013 Conclusion. Max Riegel (EC SG Chair). OmniRAN EC SG Jul ‘13 Objectives. When renewing the OmniRAN EC SG on March 22nd the IEEE 802 EC refined the objectives for the OmniRAN EC SG:

kele
Download Presentation

IEEE 802 OmniRAN EC SG July 2013 Conclusion

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IEEE 802 OmniRAN EC SGJuly 2013 Conclusion Max Riegel (EC SG Chair)

  2. OmniRAN EC SG Jul ‘13 Objectives • When renewing the OmniRAN EC SG on March 22nd the IEEE 802 EC refined the objectives for the 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. • The objectives were addressed by the study group and the results were shared with all the IEEE 802 working groups. Incorporating the feedback from the working groups, OmniRAN EC SG created a plan for progressing its work. • Requesting extension of the EC SG until Nov ‘13 to create a PAR and 5C for a ‘Recommended Practice for Network Reference Model and Functional Description of IEEE 802 based Access Networks’

  3. Gap Analysis • Deploying a simplistic network reference model, a couple of use cases were investigated • 3GPP Trusted WLAN Access to EPC • TS 23.402 V11.6.0 (2013-03) • ZigBee SEP2 Smart Grid Use Case • ZigBee docs-09-5449-33-0zse • SDN-based OmniRAN Use Case • Existing IEEE 802 specifications seem to fulfill the requirements. • However it was less than obvious how the pieces of IEEE 802 are fitting together • … still not clear how MACsec should provide point-to-point links across a bridged access network for roaming terminals • There is need for better documentation how IEEE 802 protocols work together to create access networks for particular deployments • There is no consistent way how IEEE 802 handles the IEEE 802 information elements going over IP protocols R2 Terminal R3 R1 Internet Ctrl Access

  4. External control of IEEE 802 AAAPolicy Configuration DHCP Application ANQP Access Network Scanning ? Network Selection Association Authentication Authorization Accounting Host Configuration Application Policy Control Application Host Config Release Disassociation Accounting IEEE 802 Access Technologies IEEE 802 ext. i/f

  5. Topics for Standardization in IEEE 802 • The potential gaps in IEEE 802 technologies, if any, should be addressed by the related IEEE 802 WGs • Establishing a common approach of specifying ‘external’ control into IEEE 802 technologies would require: • a specification describing the Network Reference Model and listing the DL and PHY control functions required for access networks and SDN • Description to facilitate mapping of protocols to service requirements • 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 • Topic for the joint IEEE 802 – IETF coordination group • specifications of the control attributes for the individual IEEE 802 technologies by their working groups • Should go into annex of related specifications to ensure consistency

  6. Tribute to ITUNetwork Protocol Specification in 3 Stages • For the specification of the Integrated Services Digital Network the ITU-T defined in its Rec. I.130 a sequential 3 stage process, each leading to a separate standards document. • The same process is nowadays commonly applied by all telecommunication network standardization activities. Specify requirements from the user's perspective; Develop a logical/functional model to meet those requirements; Develop a detailed specification of the protocols and attributes. • More Information: • ETSI: Making Better Standards • http://docbox.etsi.org/MTS/MTS/10-PromotionalMaterial/MBS-20111118/protocolStandards/stagedApproach.htm

  7. Applying the same approach to IEEE 802 • Direct evaluation of IEEE 802 protocols out of service/deployment requirements is challenging. • A Stage 2 specification provides a mapping of protocols into a functional network model, which facilitates easier evaluation. ‘External’ requirements from the service/deployment perspective Develop a logical/functional model for evaluation of those requirements; Available IEEE 802 specifications of protocols and attributes. ? ?

  8. OmniRAN EC SG Proposal • Develop a kind of ‘Stage 2’ document for IEEE 802 network protocol specifications • Actually re-engineering a ‘Stage 2’ to make it fitting to the existing IEEE 802 network protocol specifications (which represent ‘Stage 3’). • Such specification makes it much more easy to evaluate and qualify ‘service’ requirements, • and provide a common framework for further enhancements of IEEE 802 protocols • It is a proven process by several other SDOs addressing network specifications • There is a well-defined understanding what should go into such a document

  9. FYI: Usual ‘Stage 2’ Content ITU-T Rec I.130 WiMAX Forum Stage 2 ToC Introduction and Scope Abbreviations, Definitions, and Conventions References Identifiers Tenets Network Reference Model Functional Design and Decomposition • Derivation of a functional model • Information flow diagram • SDL diagrams for functional entities (optional) • Functional entity actions • Allocation of functional entities to physical locations Reference: http://resources.wimaxforum.org/sites/wimaxforum.org/files/technical_document/2010/12/WMF-T32-001-R016v01_Network-Stage2-Base.pdf

  10. OmniRAN EC SG Conclusion • We should try to develop a PAR and 5C for an IEEE 802 Recommended Practice • Similar to a Stage 2 specification • Potential title: ‘Network Reference Model and Functional Description of IEEE 802 based Access Networks’ • Leaving organizational questions open focusing only on the content of the PAR and 5C? • Identifying gaps to existing IEEE 802 technologies and communicating them to the related working groups

  11. Annex Background information material

  12. OmniRAN allows for mapping of complex IEEE 802 network infrastructures R2 Terminal Access Core R3 R3 R1 Internet Authentication Authentication Authorization Authorization R4 R3 Ctrl Ctrl Accounting Accounting Location Location CoA CoA Access Mobility Mobility DataPath R5 Encapsulation Encapsulation Access Access Transport R3 Internet • Reference Points represent a bundle of functions between peer entities • Similar to real network interfaces • Functions are extensible but based on IEEE 802 specific attributes

  13. Access Network Control Plane Functions AAAPolicy Configuration DHCP Application ANQP Access Network Scanning Network Selection Association Authentication Authorization Accounting Host Configuration Application Policy Control Application Host Config Release Disassociation Accounting L3+ Protocol L3+ Attributes L2 Protocol L3+ Attributes L3+ Protocol L2 Attributes Legend: L2 Protocol L2 Attributes

  14. Control Plane Functions in Scope of IETF AAAPolicy Configuration DHCP Application ANQP Access Network Scanning Network Selection Association Authentication Authorization Accounting Host Configuration Application Policy Control Application Host Config Release Disassociation Accounting L3+ Protocol L3+ Attributes L2 Protocol L3+ Attributes L3+ Protocol L2 Attributes Legend: L2 Protocol L2 Attributes

  15. Mapping of OmniRAN Reference Points to IEEE 802 Reference Model Higher Layers Higher Layers • Reference Points can be mapped onto the IEEE 802 Reference Model • R1 represents the PHY and MAC layer functions between terminal and base station • Completely covered by IEEE 802 specifications • R2 represents the L2 control protocol functions between terminal and central entities for control and AAA. • R3 represents the L1 & L2 control interface from a central control entity into the network elements • ‘R2’ and ‘R3’ cover IEEE 802 specificattributes • However IP based protocols are used to carry control information between network elements and core • Effectively each of IEEE 802 network elements contains an IP communication stack on top of the IEEE 802 data path for the exchange of the control information. Higher Layers Control Higher Layers Control R2 R3 R3 Current scope of IEEE 802 Data Link Data Link Data Link Data Link Data Link Data Link R1 Physical Physical Physical Physical Physical Physical Medium Medium Medium

More Related