* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download MPLS-TP Shared Ring protection (MSRP) mechanism
Wake-on-LAN wikipedia , lookup
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Computer network wikipedia , lookup
Distributed firewall wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Network tap wikipedia , lookup
ACTN Use-cases for Packet Transport Networks draft-cheng-actn-ptn-requirements-00 IETF 90th , July 20 – July 25, 2014 Weiqiang Cheng (CMCC) Yunbin Xu, Guoying Zhang (CATR) Scope • • • • CMCC PTN network overview Services requirements for PTN Networks Requirements for PTN Overview of Virtual Network Operations for Packet transport networks CMCC PTN network overview CMCC End to end PTN networks Volume PTN >500,000 Enterprise access Metro Capacity >1Tbps backbone Data Plane-Configurable: MPLS-TP: Labels of PW and LSP distributed statically L3 VPN: L3 Tunnels in core layer for LTE X2 configured statically Protection: configuration statically Management Plane-Centralized: centralized NMS server and manually configuration Need Control Plane - faster provisioning and operational tools foe end-to-end connectivity Separated from data Plane PTN is able to evolve to ACTN in nature Services requirements 1. Fast Provisioning 2. Operation optimization • Apply service • Apply service in through PAD/Phone carrier office • Provisioning period • Provisioning period mins~days >1month • Manual operation process • Show service status to Operator 3. Added value IT services • Intelligent operation system • Show service status to users/operator What benefits? Virtual NE PTN vCPE … vCPE2 Firewall vCPE1 NAT NFV Server … Hypervisor VCPE On-demand Value added services NFV vCPEn Controller OSS Firewall/NAT etc. Operation optimized Service provisioning Simplify Edge Reduces some functions from CPE Branch Enterprise branch PTN CPE without virtulization Network requirements: Multi-domain end to end control The operators had built a large scale of packet transport networks and divided them into different areas such as access, metro and backbone networks, each area has their own management systems. Separated operation in different domains makes the provisioning slow and operation efficiency low. Network requirements: Multi-Layer resources coordination LTE backhauling requires the PTN to realize L3 network function. This function requires the management systems operate in different layers of networks, and leads to separate and fragmented network configuration Operators want to obtain the flow information and realize the load balancing within PTN networks MPLS-TP MPLS Network requirements: Migration from network management systems Super Controller compatibility • • App OSS/NMS Interface Compatible with legacy EMS/OSS interface VNC Services provider Super Controller (VNC Services provider) EMS evolution • ACTN extension • VNC agency EMS with VNC agent Forwarding layer • Keep the legacy PTN box Qx PTN In order to realize end-to-end service provision, the ACTN architecture [ACTN-FWK] should consider the migration from traditional network management systems. Network requirements: Multi-user Network Slices ACTN Enterprise customers Access point 1 Family broadband Reconfigurable MPLS-TP based PTN Access Point 2 PTN Nodes Access Point 3 Wireless backhauling Networks slices End to END Virtual Networks Operations APP Control super controller (VNC Provider) Control OSS AB agent AB agent Metro EMS Backbone EMS Qx Enterprise PTN Accessing Networks Metro (PTN/POTN) AB agent Controller Controller Metro EMS Qx Backbone Metro PTN/POTN Enterprise PTN Accessing Networks Super Controller (VNC Service Provider) provide centralized network control of enterprise access network、metro network、backbone enterprise network The traditional networks can be considered as a virtual network for VNC service provider, which can be realized by network management systems providing an abstract (AB) agent for VNC ACTN Use-case for Mobile Virtual Network Operation for Multiple Domains in a Single Operator Network draft-shin-actn-mvno-multi-domain-00 July 24, 2014 IETF 90 – Toronto Jongyoon Shin, Rod Hwang, Jongmin Lee (SK Telecom) SKT 4G Mobile network overview PTN EMS Radio Access Network PTN (MPLS-TP) IP/MPLS EMS PTN (MPLS VPN) EMS Mobile Core Network (LTE EPC) Internet LTE RU Mobile Backhaul Network • Domain-specific control • Separation of domain operation 11 Pre-5G Mobile network overview No relationship PTN EMS Radio Access Network PTN (MPLS-TP) IP/MPLS EMS Mobile Edge DC Network NFV/SDN Controller PTN (MPLS VPN) Mobile Core Network Internet LTE RU Mobile Backhaul Network • Similar issue as previous slide with more complexity in control and operation 12 SKT 5G Mobile network Strategy Enabling Platform is the virtualized network architecture with centralized control for value creating network - Need a global abstract view - Need an operational simplicity SKT Enabling Platform Internet Radio Access Network 5G Connectivity Mobile Edge DC Network Packet-Optical Transport Network Mobile Core DC Network Transport Network 13 Local Breakout 5G data offloading to reduce congestion/load on core and to provide cost effective solutions SKT Enabling Platform Internet Radio Access Network 5G Connectivity Mobile Edge DC Network Packet-Optical Transport Network Mobile Core DC Network Transport Network 14 Virtual Network Operations for Mobile Operator’s Networks • SKT Enabling Platform (MVNO Coordinator) is a centralized control for value creating network • Need a standard API/protocols from each Domain Control of various kinds to SKT Enabling Platform (MVNO Coordinator) to facilitate dynamic connectivity requirements. • Need a common network resource abstraction model • Need a unified control scheme to interface various technology/data plane/management plane/vendor domains that operates on a virtual level. 15 Thank you! IETF 88, Vancouver 16