P802.1CF NRM Mapping to real networks

Slides:



Advertisements
Similar presentations
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Advertisements

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 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 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 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 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 IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
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
Key Concepts of Data Path establishment, relocation, and teardown
P802.1CF Information Model Structure
Progressing OmniRAN Abstract
802.1CF perspective on planned Industry Connections activity
Network instantiation
P802.1CF Information Model Structure
P802.1CF User Service Information Model
Information Model Structure
omniRAN Virtual Access Network Instantiation
P802.1CF architectural considerations for EM and NM
Model for Accounting and Monitoring
omniRAN Network Function Virtualization
P802.1CF Information Model Structure
P802.1CF NRM Refinements Abstract
P802.1CF NRM Discussions Abstract
Network reference model for access network virtualization
Chapter 7.1 Restructuring Proposal
WLAN as a Component (WaaC)
802.1CF-D1.0 WG ballot comment remedies
802.1CF-D1.0 WG ballot comment remedies
Date: < yyyy-mm-dd >
Information Model for AN Setup
Information Model Structure
Information Model Structure
P802.1CF D1.0 Figure Proposals Abstract
Overview of Transport Network Architecture
Network instantiation
Brief Introduction to OmniRAN P802.1CF
SDN Functional Decomposition
P802.1CF architectural considerations for EM and NM
Terminology clean-up User/Subscriber
Information Model Structure
Terminology clean-up User/Subscriber
P802.1CF Information Model Structure
P802.1CF operational models
omniRAN Network Function Virtualization
Key concepts of authorization, QoS, and policy control
IEEE 802 omniRAN R9c Reference Point
Thoughts on IEEE 802 network integration with respect to P802.1CF
P802.1CF D1.0 Figure Proposals Abstract
P802.1CF NRM Refinements Abstract
[place document title here]
IEEE 802 Scope of OmniRAN Abstract
P802.1CF NRM Refinements Abstract
Information Model for AN Setup
Thoughts on IEEE 802 network integration with respect to P802.1CF
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:

P802.1CF NRM Mapping to real networks Date: 2015-04-16 Authors: Name Affiliation Phone Email Max Riegel Nokia Networks +49 173 293 8240 maximilian.riegel@nokia.com Notice: This document does not represent the agreed view of the IEEE 802.1 OmniRAN TG. 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 <http://standards.ieee.org/IPR/copyrightpolicy.html>. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>. Abstract Contributions and discussions in the March 2015 meeting covered the mapping of P802.1CF NRM to real access networks, both IEEE 802 access networks as well as non-IEEE 802 access networks carrying Ethernet frames. The presentation introduces early considerations on mapping of Wi-Fi access network, China Mobile iPCN and Cable Networks to the P802.1CF NRM.

P802.1CF NRM mapping to real networks 2015-04-16 Max Riegel (Nokia Networks)

Terminology SS: Subscription Service CIS: Coordination and Information Service AN: Access Network ANC: Access Network Controller NA: Node of Attachment CN: Core Network CNI: Core Network Interface CNC: Core Network Controller TE: Terminal TEI: Terminal Interface TEC: Terminal Controller BH: Backhaul

Draft P802.1CF NRM R2c R9c R4c R5c R3c R8c/1c R6c R7c R1d R6d R3d Subscription Service Coordination and Information Service R2c R9c R4c R5c TE Ctrl AN Ctrl CN Ctrl R3c R8c/1c Terminal Interface R6c R7c Core Network Interface NA Backhaul R1d R6d R3d Terminal Access Network Core Network

NRM mapping to real networks Wi-Fi Access Network

End-to-end network topology Subscription Service Information Service Terminal Access Network Backhaul Core Network TE NA Scope of P802.1CF in the protocol layer architecture Data Link Physical Network Transport Application Data Link Physical Network Transport Application Network Network DL Phy DL Phy DL Phy Data Link Data Link Physical Physical Medium Medium Medium Medium Medium Terminal Interface Node of Attachment Backhaul Core Network Interface Scope of P802.1CF Schematic NRM for the IEEE 802 access network Subscription Service R2 R4 Terminal Access Network Core Network R1 R3

Wi-Fi access network further considerations Where is an appropriate public reference for Wi-Fi network architecture?

NRM mapping to real networks China Mobile iPCN

China Mobile iPCN omniran-15-0016-00-wsdn-sdn-practice-of-china-mobile China Mobile iPCN omniran-15-0016-00-wsdn-sdn-practice-of-china-mobile.pdf

P802.1CF model for iPCN P802.1CF It seems, P802.1CF can provide the access model and partly(?) the transport model Does iPCN comply with carrying Ethernet frames end-to-end? Further input from China Mobile needed to fully understand the required functionality for both, access and transport. What kind of access technologies are supported by iPCN? What is the demarcation between Transport Model and IP Backbone Model? How is access control for terminals realized?

NRM mapping to real networks CABLE Network

Mapping of cable networks CM CM AAA SNMP CMTS CM Cable Network

Mapping of cable networks Basic case: cable network represents R1 CM CM AAA SNMP CMTS CM Cable Network TE R1 NA R3

Second flavor of cable networks Community Wi-Fi (e.g. Comcast xfinity) CM CM AAA SNMP CMTS AAA CM Cable Network

Second flavor of cable networks Community Wi-Fi (e. g Second flavor of cable networks Community Wi-Fi (e.g. Comcast xfinity) Cable Network represents Backhaul CM CM AAA SNMP CMTS AAA CM Cable Network TE R1 NA Backhaul R3

R-MACPHY Architecture from Hesham R-MACPHY Architecture R-MACPHY Controller manages the configuration of the of the R-MACPHY device. The Controller can be either a separate device or a component embedded in an aggregation and switching device, such as a router, a switch, or an OLT

from Hesham R-PHY L2TPv3 Topology

R-PHY L2TPv3 Topology – Multiple Tunnels from Hesham R-PHY L2TPv3 Topology – Multiple Tunnels

Conclusion P802.1CF NRM can be easily mapped to real Ethernet access networks Details have to be worked out as multiple configurations may exist. It is important to have a public reference for the particular network architecture. Who would be willing to work on text on particular mappings?