An SDN-based approach for OmniRAN Reference Point mapping Date: [2013-05-14] Authors: NameAffiliationPhone Antonio de la

Slides:



Advertisements
Similar presentations
Omniran Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Advertisements

Omniran GPP Trusted WLAN Access to EPC Use Case Analysis 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.
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran OmniRAN Proximity Service use case Date: [ ] Authors: NameAffiliationPhone Hyunho ParkETRI
WiFi Privacy network experiment at IEEE Berlin Date: [ ] Authors: NameAffiliationPhone Carlos Jesús
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
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 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 – 3GPP SaMOG Document Number: IEEE Shet
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
Heterogeneous Networking – Setting the Scene
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:
Privecsg ‹#› IEEE 802 Privacy concerns about 802c PAR Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZunigaInterDigital.
OmniRAN SDN-based OmniRAN Use Cases Summary Date: Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34
MAC Address Randomization Tests Date: [ ] Authors: NameAffiliationPhone Fabio Carlos Jesús
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.
WiFi Privacy network experiment at IEEE 802 Berlin Plenary and IETF92 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús
Omniran Thoughts about the tenets in IEEE 802.1CF Date: Authors: NameAffiliationPhone Max RiegelNSN
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
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 Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
OmniRAN CF00 1 IEEE 802 omniRAN Network Reference Model Amendment Date: Authors: NameAffiliationPhone Yonggang
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.
3GPP SA2 SaMOG Status Document Number: Omniran Date Submitted: Source: Antonio de la Oliva UC3M *
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
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
Omniran CF00 1 P802.1CF NRM Ambiguities Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
IEEE 802 OmniRAN Study Group: SDN Use Case
omniRAN Virtual Access Network Instantiation
omniRAN Network Function Virtualization
WLAN as a Component (WaaC)
An SDN-based approach for OmniRAN
P802.1CF D1.0 Figure Proposals Abstract
SDN Functional Decomposition
Terminology clean-up User/Subscriber
Terminology clean-up User/Subscriber
P802.1CF operational models
omniRAN Network Function Virtualization
IEEE 802 omniRAN R9c Reference Point
P802.1CF D1.0 Figure Proposals Abstract
[place document title here]
IEEE 802 Scope of OmniRAN Abstract
An SDN-based approach for OmniRAN Reference Point mapping
[place document title here]
802.1CF ToC Refinements Abstract
OmniRAN SDN Use Case ToC
SDN-based OmniRAN Use Cases Summary
OmniRAN SDN Use Case ToC
IEEE 802 RAN Recommended Practice ToC Proposal
Presentation transcript:

An SDN-based approach for OmniRAN Reference Point mapping Date: [ ] Authors: NameAffiliationPhone Antonio de la Juan Carlos Charles 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 This presentation extends SDN use case with the mapping to OMNIRAN Reference Points and derived requirements

An SDN-based approach for OmniRAN Reference Point Mapping OmniRAN use case contribution

Heterogeneous Networking w/ OmniRAN

sdf Terminal Access Core Op B Internet Access Access Infrastructure Operators Core Op ACore Op C Traditional Operators Reference Model for OMNIRAN over SDN

sdf Access Access Infrastructure Operators Reference Model (Access Infrastructure operator with data and control split) Access Infrastructure Operators BackhaulSDN Controller Data path Control path Access Access Abstraction

Reference Points  R1: Terminal  Access point: technology specific  R2: Terminal  Core Network (connectivity services network)  User & terminal authentication, subscription & terminal management  R3: Access Network  Core network  Authorization, service management, user data connection, mobility support, accounting, location  R4: Access Network  Access network  Inter-access network coordination and cooperation, fast inter- technology handover  R5: Core Network  Core network  Inter-operator roaming plus access infrastructure sharing.

Access Access Infrastructure Operators BackhaulSDN Controller sdf Core Op B Internet Core Op ACore Op C Traditional Operators Terminal R1 R1: Access link SDN-based configuration/interaction between infrastructure and wireless link Access Abstraction R1

Access Access Infrastructure Operators BackhaulSDN Controller sdf Core Op B Internet Core Op ACore Op C Traditional Operators Terminal R2 R2: Control path only Access Abstraction

Access Access Infrastructure Operators BackhaulSDN Controller sdf Core Op B Internet Core Op ACore Op C Traditional Operators Terminal R3 R3: Data (e.g., mobility) and Control (e.g., configuration) path Access Abstraction

Access Access Infrastructure Operators BackhaulSDN Controller sdf Core Op B Internet Core Op ACore Op C Traditional Operators Terminal R4 R4: Data (e.g., fast handover) and Control (e.g., ICI) path Access Abstraction R4 Access Abstraction

sdf Core Op B Internet Core Op ACore Op C Traditional Operators Terminal R5 Access Access Infrastructure Operators BackhaulSDN Controller R5: Data path: Roaming between operators Control path: Roaming between operator + infrastructure sharing

Reference Points over SDN  R1: Access link  SDN-based configuration/interaction between infrastructure and wireless link  R2: User & terminal authentication, subscription & terminal management  This reference point can be implemented as a control path from the access network to the corresponding operator  R3: Authorization, service management, user data connection, mobility support, accounting, location  The SDN controller can configure the underlying network for user authorization (e.g. adding MAC to APs), managing mobility (e.g. reconfiguring forwarding path per user), accounting (e.g. counters per forwarding table)  Possible extension of SDN concepts for configuration of heterogeneous access network.  R4: Inter-access network coordination and cooperation, fast inter- technology handover  SDN based forwarding state between different RANs  R5: Inter-operator roaming control interface  Inter-operator roaming plus access infrastructure sharing outside access network