omniran CF00 1 P802.1CF NRM Mapping to real networks Date: Authors: NameAffiliationPhone Max RiegelNokia Networks Notice: This document does not represent the agreed view of the IEEE 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. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. 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.

omniran CF00 2 P802.1CF NRM mapping to real networks Max Riegel (Nokia Networks)

omniran CF00 3 Terminology SS: Subscription Service CIS:Coordination and Information Service AN: Access Network ANC:Access Network Controller NA: Node of Attachment AR:Access Router ARI:Access Router Interface ARC:Access Router Controller TE: Terminal TEI:Terminal Interface TEC:Terminal Controller BH:Backhaul

omniran CF00 4 Draft P802.1CF NRM

omniran CF00 5 WI-FI ACCESS NETWORK NRM mapping to real networks

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

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

omniran CF00 8 CHINA MOBILE IPCN NRM mapping to real networks

omniran CF00 9 China Mobile iPCN omniran wsdn-sdn-practice-of-china-mobile.pdf

omniran CF00 10 P802.1CF model for iPCN 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? P802.1CF

omniran CF00 11 CABLE NETWORK NRM mapping to real networks

omniran CF00 12 Mapping of cable networks Cable Network SNMP CMTS CM AAA

omniran CF00 13 Mapping of cable networks Basic case: cable network represents R1 Cable Network SNMP CMTS CM AAA R1R3NATE

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

omniran CF00 15 Second flavor of cable networks Community Wi-Fi (e.g. Comcast xfinity) Cable Network represents Backhaul Cable Network CM SNMP CMTS AAA R1NATER3 Backhaul

omniran CF00 16 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  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

omniran CF00 17 R-PHY L2TPv3 Topology from Hesham

omniran CF00 18 R-PHY L2TPv3 Topology – Multiple Tunnels from Hesham

omniran CF00 19 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?