Omniran-13-0032-04-0000 1 IEEE 802 Scope of OmniRAN Date: 2013-05-16 Authors: NameAffiliationPhone Max RiegelNSN+49 173 293

Slides:



Advertisements
Similar presentations
Omniran Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Advertisements

(omniran TG) Short introduction into OmniRAN P802.1CF Date: Authors: NameAffiliationPhone Max RiegelNokia.
Omniran Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran ecsg 1 Introduction to OmniRAN EC SG Max Riegel (OmniRAN SG Chair)
Omniran ecsg 1 OmniRAN Introduction and Way Forward Max Riegel (OmniRAN SG Chair)
Omniran ecsg 1 OmniRAN EC SG July 2013 Liaison Report Chair: Max Riegel, NSN.
Omniran TG 1 Cooperation for OmniRAN P802.1CF Max Riegel, NSN (Chair OmniRAN TG)
Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran IEEE 802 Enhanced Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
OmniRAN Smart Grid use case Document Number: Omniran Date Submitted: Source: Max Riegel Nokia.
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
SDN-based OmniRAN Use Cases Date: [ ] Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34 Juan Carlos ZúñigaInterDigital+1.
Omniran OmniRAN Proximity Service use case Date: [ ] Authors: NameAffiliationPhone Hyunho ParkETRI
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Access Infrastructure
Omniran PtP Links across IEEE 802 Bridged Infrastructure Date: Authors: NameAffiliationPhone Max
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
OmniRAN SoA and Gap Analysis Date: [ ] Authors: NameAffiliationPhone Antonio de la Juan Carlos
OmniRAN-15-00xx WLAN as a Component (WaaC) Date: xx Authors: NameAffiliationPhone Yonggang FangZTETX Bo SunZTE He HuangZTE Notice:
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
Omniran CF00 1 P802.1CF NRM Discussions Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Discussion on NRM Control Reference Points Information and Parameters Date: Authors: NameAffiliationPhone Antonio de la Oliva University.
Logical Interface Overview Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital Notice:
OmniRAN SDN-based OmniRAN Use Cases Summary Date: Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34
An SDN-based approach for OmniRAN Reference Point mapping Date: [ ] Authors: NameAffiliationPhone Antonio de la
Omniran CF00 1 OmniRAN R3 Considerations Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Mapping to real networks Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran Thoughts about the tenets in IEEE 802.1CF Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 VLANs in relation to P802.1CF NRM Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran IEEE 802 OmniRAN EC SG Results and Outlook Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 CF ToC Refinements Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 Content and outline considerations for Annex: Applicability to non-IEEE 802 PHY layer technologies Date: Authors:
OmniRAN IEEE 802 OmniRAN Recommended Practice ToC Proposal Date: Authors: NameAffiliationPhone Yonggang
Omniran CF00 1 Key Concepts of Authentication and Trust Establishment Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran CF00 1 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran CF00 1 IEEE OmniRAN TG Athens NRM Conclusions Max Riegel, Nokia Networks (OmniRAN TG Chair)
Omniran OmniRAN SaMOG Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Backhaul Considerations Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF00 1 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
OmniRAN IEEE 802 OmniRAN Architecture Proposal Date: Authors: NameAffiliationPhone Yonggang Bo.
Submission doc.: IEEE arc March 2014 Max Riegel (NSN)Slide 1 Cross-WG cooperation on OmniRAN P802.1CF E.g.: Network Discovery and Selection.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran TG 1 Cooperations for OmniRAN P802.1CF Max Riegel, NSN (Chair OmniRAN TG)
Omniran CF00 1 Key Concepts of Association and Disassociation Date: Authors: NameAffiliationPhone Max RiegelNokia
OmniRAN omniRAN Network Function Virtualization Date: Authors: NameAffiliationPhone Yonggang FangZTETX Zhendong.
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
IEEE 802 OmniRAN Study Group: SDN Use Case
IEEE 802 OmniRAN EC SG July 2013 Conclusion
IEEE 802 OmniRAN EC SG July 2013 Conclusion
OmniRAN Introduction and Way Forward
P802.1CF NRM Refinements Abstract
P802.1CF NRM Discussions Abstract
An SDN-based approach for OmniRAN
P802.1CF D1.0 Figure Proposals Abstract
Brief Introduction to OmniRAN P802.1CF
P802.1CF D1.0 Figure Proposals Abstract
P802.1CF NRM Refinements Abstract
IEEE 802 Scope of OmniRAN Abstract
P802.1CF NRM Refinements Abstract
OmniRAN Introduction and Way Forward
An SDN-based approach for OmniRAN Reference Point mapping
802.1CF ToC Refinements Abstract
OmniRAN SDN Use Case ToC
SDN-based OmniRAN Use Cases Summary
OmniRAN SDN Use Case ToC
Presentation transcript:

omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN Notice: This document does not represent the agreed view of the OmniRAN EC SG. It represents only the views of the participants listed in the ‘Authors:’ field above. It is offered as a basis for discussion. It is not binding on the contributor, who reserve the right to add, amend or withdraw material contained herein. Copyright policy: The contributor is familiar with the IEEE-SA Copyright Policy. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Abstract IEEE 802 cover networking functions represented by the PHY and DL layers of the 7- layer OSI/ 5-layer Internet model. OmniRAN provides an abstraction of access networks based on IEEE 802 technologies to forster interoperability and integration into common control infrastructures. The Reference Points of OmniRAN reflect IEEE 802 specific attributes which potentially are transferred over IP protocols. The definition of the attributes is completely within the scope of IEEE 802.

omniran IEEE 802 Scope of OmniRAN Architectural models and functional views of OmniRAN in the scope of IEEE 802

omniran IEEE 802 ARCHITECTURE IEEE 802 Scope of OmniRAN

omniran IEEE 802 Reference Model for End-Stations (802rev-D1.6) Reference Model within the 7 layer ISO-OSI model IEEE 802 provides link layer connectivity to the overall communication architecture It covers the Physical and the Data link layer of the ISO-OSI 7 layer model/Internet 5 layer model Data link layer is represented in IEEE 802 by MAC and LLC sub-layers Functionality above Data link layer is considered as ‘higher layer’. Reference Model exposing specific IEEE 802 functions The IEEE 802 end-station model comprises a management plane and a plane representing IEEE MIH. The network management model of IEEE 802 provides the definition of managed objects for each of the layers of the IEEE 802 RM The MICF of IEEE provides SAPs towards the PHY-, MAC- and Higher layers of the RM

omniran IEEE 802 Reference Model for Bridges IEEE 802 provides a bridging model for interconnection of multiple network segments based on data link layer functionality Different bridging protocols can handle the issues of various topologies including avoidance of data loops and establishment of ‘optimized’ filtering and forwarding decisions. Bridging protocols have been extended to cope with multiple operational domains of hierarchical provider structures.

omniran ACCESS NETWORK ARCHITECTURAL VIEWS IEEE 802 Scope of OmniRAN

omniran Access Networks enable the dynamic attachment of terminals to networks Communication networks supporting dynamic attachment of terminals are usually structured into –Access Network Distributed infrastructure for aggregation of multiple network access interfaces into a common interface –Core Infrastructure for control and management of network access and end- to-end IP connectivity –Services Infrastructure for providing services over IP connectivity Internet Terminal Access Network ServicesCore

omniran Functional decomposition of dynamic network access Access Network Network advertisement Pre-association signalling Authentication, authorization and accounting client L2 session establishment –w/ QoS and Policy Enforcement L2 mobility management inside access networks Traffic forwarding to core based on L2 addresses Mobility Gateway Core Subscription management Terminal provisioning Authentication, authorization and accounting server IP address management IP connectivity establishment to Internet and services Policy & QoS management server (policy decision) Mobility Anchor Roaming support to other cores

omniran Scope of IEEE 802 Medium Mapping Access Networks to the architectural model of IEEE 802 IEEE 802 is dealing with packet data transport functions in the Data Link and Physical layers. Access networks are dynamically controlled Layer 2 network infrastructures. Data Link Physical Network Transport Application Data Link Physical Network Transport Application Data Link Physical Data Link Physical Data Link Physical Data Link Physical Access Network Terminal Core

omniran Scope of IEEE 802 Medium Access Network Control and User Plane Data Link Physical Network Transport Application Data Link Physical Access Network Terminal Data Link Physical Data Link Physical Network Transport Application Network Medium Core Service Data Link Physical Data Link Physical Data Link Physical Data Link Physical Scanning Network Selection Association Authentication Host Configuration Application User Plane Control Plane

omniran Network Selection Accounting Disassociation Host Configuration Application Policy Control Application Host Config Release Accounting Authentication Authorization Association Scanning Access Network Control Plane Functions AAA Policy DHCPApplication ANQP L2 Protocol L2 Attributes L3+ Protocol L2 Attributes L3+ Protocol L3+ Attributes Legend: L2 Protocol L3+ Attributes

omniran Control Protocols used by Access Networks Scanning: Finding out about the existence of potential communication peers –Scope of individual IEEE 802.xx specifications Network selection: Finding the most appropriate network access –IEEE 802.xx protocol for higher layer information Association: Setting up the access link –Scope of individual IEEE 802.xx specifications Authentication –EAP framework, supported by IEEE 802.1X or IEEE 802.xx technology specific solutions Authorization: Setting up the IEEE 802 communication link –Attributes and functions including specifics of IEEE 802.xx technologies Accounting: Usage and inventory reporting –Attributes including specifics of IEEE 802.xx technologies Policy Control: Adjustment of the user data connection –Attributes including specifics of IEEE 802.xx technologies Host Configuration: Getting the IP communication parameters –IP protocol for IP configuration parameters Application: Setting up the productive use of the communication infrastructure –IP protocol for control of application Host Config Release: Releasing the IP communication parameters –IP protocol for IP configuration parameters Disassociation: Releasing the access link –Scope of individual IEEE 802.xx specifications

omniran OMNIRAN WITHIN THE SCOPE OF IEEE 802 IEEE 802 Scope of OmniRAN

omniran Access Network Abstraction by OmniRAN OmniRAN provides a generic model of an access network based on IEEE 802 technologies Access Network Terminal Core Service Medium Data Link Physical Network Transport Application Data Link Physical Data Link Physical Data Link Physical Network Transport Application Network Medium Data Link Physical Data Link Physical Data Link Physical Data Link Physical Core R2 R1R3 OmniRAN Architecture Access Network Terminal

omniran OmniRAN Reference Points capture the functions of an access network Reference Points denote the interconnections between functional entities of an access network, i.e.: –R1 between terminal and base station: Access link, technology specific –R2 between terminal and core network: User & terminal authentication, subscription & terminal management –R3 between access network and core network: Authorization, service management, user data connection, mobility support, accounting, location –R4 between access networks: Inter-access network coordination and cooperation, fast inter-technology handover –R5 between core networks to enable co-use of access networks: Inter-operator roaming control interface Reference Points build the foundation for realizing interoperability for real world access networks. The Reference Points capture the control information necessary to allow dynamic control of network functions by a central entity (core).

omniran OmniRAN architecture example showing all different reference points Access Core Internet R1 R3 R4 Access Core Internet R3 R5 Terminal R3 Authentication Authorization Accounting Location CoA Mobility Encapsulation Authentication Authorization Accounting Location CoA Mobility Encapsulation DataPath AccessCore Transport Reference Points represent a bundle of functions between peer entities -Similar to real network interfaces R2 Access R3

omniran Network Selection Accounting Disassociation Host Configuration Application Policy Control Application Host Config Release Accounting Authentication Authorization Association Scanning OmniRAN Functional Scope AAA Policy DHCPApplication ANQP IEEE 802 Access Technologies OmniRAN

omniran Current scope of IEEE 802 Medium Mapping of OmniRAN Reference Points to IEEE 802 Reference Model 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’ are build upon IEEE 802 specific attributes –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. Data Link Physical Higher Layers Data Link Physical Data Link Physical Data Link Physical Data Link Physical Data Link Physical Higher Layers Control Higher Layers R3R2 R3 R1

omniran Handling IEEE 802 Attributes in IP Protocols Handling of IEEE 802 specific attributes of IP protocols within the activities of IEEE P802: –IEEE P802 has an established routine for defining the MIBs of IEEE 802 technologies Partly done by itself and partly within the IETF –Processes for defining other IEEE 802 related attributes in IETF vary depending of protocol e.g. AAA attributes are mainly done by IETF with some informal review by IEEE 802 WGs Cooperation between IEEE 802 and IETF is currently reviewed and refined in [draft-iab- rfc4441rev-04.txt]

omniran CONCLUSION IEEE 802 Scope of OmniRAN

omniran Conclusion OmniRAN provides an abstraction of access networks based on IEEE 802 technologies. –Defining a common framework for deployment of IEEE 802 technologies for network access for various purposes –Creating unified control interfaces to enable integration of various IEEE 802 access technologies into a common architecture and control infrastructure –Supporting new developments for networking like SDN Reference Points reflect IEEE 802 specific control information –R1 is completely covered by IEEE 802 specifications –R2 and R3 are mainly carrying control information for IEEE 802 functions –R4 enhances direct cooperation among multiple IEEE 802 access networks –R5 is present for conceptual purposes to forster the cooperation among cores. Attributes carried on R5 may mostly be identical to the attributes defined for R3 OmniRAN Specification in the scope of IEEE 802 would consist of –an normative part defining control attributes and referencing the DL SAP –an informative part outlining the overall architecture –an informative part proposing the usage of particular IP protocols and the mapping of the IEEE 802 attributes into the IP protocols.