Presentation is loading. Please wait.

Presentation is loading. Please wait.

New Control Architectures for E2E networks Juan Pedro Fernandez-Palacios, Telefonica I+D April 2013.

Similar presentations


Presentation on theme: "New Control Architectures for E2E networks Juan Pedro Fernandez-Palacios, Telefonica I+D April 2013."— Presentation transcript:

1 New Control Architectures for E2E networks Juan Pedro Fernandez-Palacios, Telefonica I+D April 2013

2 Core network operation is not adapted to flexible networking Multiple manual configuration actions are needed in core network nodes Network solutions from different vendors typically use particularized Network Management System (NMS) implementations Very long service provisioning times InternetVoiceCDNCloudBusiness Service Management Systems Network Provisioning Systems Metro NMS Vendor A IP Core NMS Optical Transport NMS Umbrella Provisioning System Complex and long workflows for network provisioning over different segments (metro, IP core, Optical transport) requiring multiple configurations over different NMS NMS Vendor B NMS Vendor C NMS Vendor D NMS Vendor E NMS Vendor C NMS Vendor A NMS Vendor B Metro Node Vendor A Metro Node Vendor B IP Node Vendor C IP Node Vendor D IP Node Vendor E Optical Node Vendor A Optical Node Vendor B Optical Node Vendor C Core Network Nodes CURRENT APPROACH FOR NETWORK PROVISIONING Traditional core network operation is very complex and expensive

3 Control plane and SDN pave the path towards a unified network provisioning architecture Key building block of such unified network provisioning architecture are: Network configuration interface: Multivendor edge nodes configuration (e.g OLT and BRAS, IP core routers, etc) by standard interfaces (e.g OpenFlow) IT and network SDN orchestration: Coordinated network and datacenter resources control according to service requirements (e.g orchestrated Virtual Machine transfer among datacenters) Network-Service API: Application level API hiding details of the network InternetVoiceCDNCloudBusiness Multiservice network provisioning system (SDN Orchestrator) Standard signaling mechanisms running over network nodes enabling flexible networking and automated network provisioning over different network segments (metro, core IP, optical transport) including multiple vendors Metro Node Vendor A Metro Node Vendor B IP Node Vendor C IP Node Vendor D IP Node Vendor E Optical Node Vendor A Optical Node Vendor B Optical Node Vendor C Service Management Systems Network Provisioning Core Network Nodes Network-Service API Network configuration interface Unified network provisioning architecture

4 Infrastructur e Layer (e.g DataCenter ) SDN Controller ALTOSDN orchestrator Application Layer OAM Handler TEDVNTM PCE Provisioning Manager OPENFLOW SDN CONTROLLER API OpenFlow is based on the concept of actions that are applied to each packet of a given flow (Ethernet-level addresses, VLAN tags, IP addresses, MPLS labels or transport-level ports). The actions taken by SDN the controller comprise: inserting and removing tags (layer 2), performing routing (layer 3) and also providing differentiated treatment to packets (QoS) Basic SDN Approach for OpenFlow Domains

5 82nd IETF, Taipei 1) Discovery of network resources 2) Routing, path computation 3) Automated network orchestration in response to changing network conditions and service requirements 4) Network resources abstraction to application layer 5) QoS control and performance monitoring 6) Multilayer interworking 7) Multidomain/multivendor network resources provisioning through different control domains (e.g OpenFlow DataCenter, OpenFlow MAN, GMPLS optical transport…) E2E networks might be pure OpenFlow based one day, but the migration process will take some time Main actions to be taken by the SDN controller in E2E networks

6 OpenFLow Data Center SDN Controller 4-ALTO3-SDN orchestrator Applications (Internet, CDN, cloud…) 5-OAM Handler 1- TED6-VNTM 2-PCE 7-Provisioning Manager OpenFlow MAN Domain IP/MPLS core OpenFlow Optical Domain OPENFLOW GMPLS Optical Domains NETCONF MPLS MAN PCEPOPENFLOW CLI Most of these building blocks are still on definition and standardization process SDN controller based on standard building blocks

7 Physical Network NETWORK OPERATING SYSTEM CSO Multilayer Orchestrator Link Provisioni ng CDN and nionetwork optimizat API Provisioning Manager Cloud Services Live OTT Internet … Orchestration mechanisms (*) Network APIs … NetConfOpenFlowPCEPUNI Inside SDN Orchestrator

8 Access NetworkMetro Area NetworkCore Network Optical Transport Multidomain L2 service provisioning Data Center Network CPE Virtual Machine (e.g BRAS) Technical challenges: Horizontal Orchestration. Automated L2 service provisioning through different packet switching domains (metro, core, datacenter). Vertical Orchestration. This orchestration enables adaptive network resources allocation in IP and optical layers according to the traffic pattern to efficiently use network resources Multilayer orchestration SDN controller E2E SDN control

9 Access NetworkMetro Area NetworkCore NetworkData Center Network CPE Virtual Machine (e.g BRAS) SDN controller OpenFlow CLI Multidomain pseudowire over seamless MPLS Intra datacenter connection Multidomain L2 service provisioning (short term)

10 Access NetworkMetro Area NetworkCore NetworkData Center Network CPE Virtual Machine (e.g BRAS) SDN controller OpenFlow Multidomain pseudowire over seamless MPLS Intra datacenter connection Multidomain L2 service provisioning (Medium term)

11 For this scenario, OF is used to trigger control plane. This means that edge nodes have to decode OF and translate into CP messages. For the case of creating a Pseudo-Wire following parameters are required: Pseudowire Label MPLS Label Service VLAN (VLANs) Output port 10 CP node OF and CP node enable node OF Request 1 3 OF Information Updated 2 4 Multidomain L2 service provisioning (Medium term)

12 Access NetworkMetro Area NetworkCore NetworkData Center Network CPE Virtual Machine (e.g BRAS) SDN controller Intra datacenter connection OpenFlow Common Interface OpenFlow SDN controller Options: Hierarchical Approach. There is a controller which has a global view so it can orchestrate the configuration in each domain. Peer Relationship. Each controller can request for information or connections to other peers. Connection to datacenter Multidomain L2 service provisioning (Long term)

13 Access R1 Access Region 2 Transit R1 Transit R2 Transit Backup R3 Transit Backup R3 Interconnection Transit R3 Access R3 Increased survivability Extended reparation processes Capex Savings (best effort traffic only) Increased survivability Extended reparation processes Capex Savings (best effort traffic only) Load balancing between IP and optical networks Multi-layer restoration Vertical Orchestration

14 OpenFLow OPS Data Center SDN Controller 4-ALTO3-SDN orchestrator Applications (Internet, CDN, cloud…) 5-OAM Handler 1- TED6-VNTM 2-PCE 7-Provisioning Manager OpenFlow Metro-Core Node (L3/L2/L1) IP/MPLS core OpenFlow WSON network OPENFLOW, GMPLS OPENFLOW GMPLS FlexiGrid NETCONF PCEP, GMPLS OPENFLOW OFELIA IDEALIST DISCUSSTRAUSS IDEALIST: IP and Flexgrid configuration IDEALIST IDEALIST: Multilayer IP over FlexiGrid Orchestration STRAUSS: VM transfer orchestration EU projects situation in this picture

15 14 EU –Japan collaboration within STRAUSS project

16 E2E SDN control (KDDI, NTT, NEC…) Network Operating System Multilayer and multidomain orchestration mechanisms Network Functions Virtualisation Optical data plane (NTT, Fujitsu, Osaka University, NEC…) Subwavelength, Flexgrid, Optical OFDM Sliceable and Programmable Transponders sliceable BVT. Figure from NTT. Joint EU-Japan standardization contributions (IETF, ONF, NFV, ITU…) List of potential topics for future collaboration EU-Japan


Download ppt "New Control Architectures for E2E networks Juan Pedro Fernandez-Palacios, Telefonica I+D April 2013."

Similar presentations


Ads by Google