160 likes | 169 Views
This article discusses the evolution of transport networks, including the drivers and requirements for hybrid packet transport. It explores the concept of a universal switching architecture and different hybrid fabric approaches. The advantages and drawbacks of each approach are also presented.
E N D
Packet Centric Transport in NG Hybrid TDM/Packet/WDM Transport Networks Enrique Hernandez-Valencia Alcatel-Lucent Optics CTO Group Internet 2 - Summer 2007 Joint Techs Workshop Fermilab - Batavia, IL July 15-18, 2007.
Agenda 1. Transport Network Evolution Drivers • NG Hybrid Transport Node Models • Packet Transport Framework • Closing Remarks
Hybrid Packet Transport SDH/SONET SDH/SONET SDH/SONET SDH/SONET NGPacket Transport EoS Enterprise Ethernet EoS Carrier Ethernet(e.g. MPLS) T-ROADM ROADM Transport Network Evolution Drivers In an All-IP, blended services world, traffic must be aggregated and transported over distance with high resiliency at thelowest cost per bit Application service layer convergence on IP Transport service layer moving toPackets Service Drivers Fix/Mobile Convergence Bus/Res 3-Play Switched Ethernet Internet Access Switched Ethernet Bus/Res 3-Play Switched Ethernet Transport Network Investments (Aggregation) Core Metro EoS Access 2000 2003 2006 2009
Scalability Cost-Efficiency Multi-service Quality Ability to support any number of client traffic instances whatever network size, from access to core Ability to ensure that client traffic is reliably delivered at monitored e2e performance Ability to deliver any type of client traffic (transparency to service) Acting as server layer for all the rest by keeping processing complexity low and operations easy Transport Network Equipment – Requirements & Enablers Transport Network Reliable aggregation and transport of any client traffic type, in any scale, at the lowest cost per bit • Networking Layering • Domain Partitioning • Client agnosticism(any L1, L2, L3) • Connection oriented • OAM, resiliency • Traffic engineering, resource reservation • CAPEX: low protocol complexity • OPEX: multilayer operations across Packets/TDM/λ Transport values have evolved through long TDM evolution They hold through transition to packets
Hybrid Architecture for Next-Generation Transport • Universal Switching • Integrated TDM/Packet switching architecture • Switching synch traffic (circuits) or asynch traffic (packets) in native format (technology-independent) • Non-stop forwarding (not affected by traffic congestion) Client Processing decoupled from Switching Photonic Universal TDM/Packet Switch • Specific Traffic Processing Line Cards • Technology-dependent traffic line cards • Host tech specific traffic processing functions (classification, policing, perf. monitoring, OAM, etc) • Open to any packet-based transport protocol, focused around carrier grade layer 2 transport such as Ethernet Provider Bridging & T-MPLS PKT TDM TDM TDM PKT PKT • Photonics Integration • CWDM/DWDM, OADM, Mux/Demux, Transponders • ROADM, OTH
100% Circuit 100% Packet Seamless Network Transformation to All-Packet Transport Carrier Ethernettransport model MSPP model SONET/SDH model Native switching of synch traffic (circuits) and asynch traffic (packets) Universal Switch Universal Switch Universal Switch C/D-WDM ROADM C/D-WDM ROADM OC-192 STM-64 OC-192 STM-64 Photonic card STM-1 OC-3 E1/DS1 GE FE 10GE 10GE GE/FE TDM card Packet card 10GE Any Traffic Mix • Freedom in planning network resources, reduced investment risk • Cost-optimized network consolidation
TDM Card TDM Card Mapper/ Framer TDM BP Int. Mapper/ Framer TDM BP Int. XSFP XSFP XSFP XSFP Packet Card Packet Card NPU & TM Packet BP Int. NPU & TM Packet BP Int. XSFP XSFP XSFP XSFP Hybrid-Fabric ApproachesDual Packet-TDM Fabric • Attributes: • Dual TDM/Packet Star • Separate TDM/Packet backplane traces Advantages: • Native TDM (e.g. crossbar) and Packet (e.g., self-routed) fabrics support & feature set • Leverage OTS components Drawbacks: • Duplicated modules (cost & footprint) • Duplicated backplane traces (CAPEX) • Independent subsystem technologies to be managed (OPEX)
TDM Card TDM Card Mapper/ Framer CES BP Int. Mapper/ Framer CES BP Int. XSFP XSFP XSFP XSFP Packet Card Packet Card NPU & TM Packet BP Int. NPU & TM Packet BP Int. XSFP XSFP XSFP XSFP Hybrid-Fabric ApproachesCentral Packet Fabric • Attributes: • Single packet fabric instance • Single-set of backplane traces • TDM emulation toward fabric Advantages: • Leverage OTS packet processing components • Single (packet-oriented) control framework Drawbacks: • Stringent packet/cell processing constraints to support TDM traffic emulation requirements • Higher TDM card cost from CE functions
TDM Card TDM Card Mapper/ Framer TDM BP Int. Mapper/ Framer TDM BP Int. XSFP XSFP XSFP XSFP Packet Card Packet Card NPU & TM Packet BP Int. NPU & TM Packet BP Int. XSFP XSFP XSFP XSFP Hybrid-Fabric ApproachesCentral TDM Fabric • Attributes: • Single TDM fabric instance • Single-set of backplane traces • Arbitrated TDM fabric access Advantages: • Native synchronous fabric (low cost) • Single TDM-oriented control framework Drawbacks: • More complex fabric access arbitration for packet cards • Fabric scaling to higher data rates?
Hybrid-Fabric ApproachesTradeoffs • Key hybrid-fabric tradeoffs: • Parallel Packet-based and TDM-based solution achieve high functionality with low component integration (multiple devices) and, hence, higher cost • Packet-based solutions require TDM-to-packet conversion on I/O Ports – High Cost – and greater performance budget (jitter and delay sensitivity) w.r.t TDM service • TDM-based solution delivers compatible with TDM performances w/o penalties on costs & provide option for interoperation with TDM only I/O TDM TDM Extra Cost on Data boards, Full or partial board capacity Packet Packet • A Multi-Service TDM fabric allows flexible and cost-effective cross-connection of SONET and G.709 OTN) containers and..... Packet Switching!
Connection between TDM/WDM Line Card Input/Output ports are Static • There is a static 1-to-1 relationship between input port signal and output port signal SIO(t) = 1, if I=X and O=Y t 0, otherwise • Connection between Packet Line Cards are Dynamic to allow packet aggregation • There is a dynamic N-to-1 relationship between input port signal and output port signal (e.g., re-arrangeable CLOS) SIO(t) = 1, if I=X and O=R(t) 0, otherwise Packet Line Card TDM/WDM Line Card SXY SUV Packet Line Card Packet Line Card TDM/WDM Line Card I/O & Agnostic TDM Fabric Connectivity: A typical Implementation I1 O1 Universal Switch IN ON Fabric Access controller
Others T-MPLS Path/ T-MPLS Channel (PWE3 based) T-MPLS Link/Section IP/MPLS Ethernet Optical-Packet Transport Network Packet Transport Aggregation Framework • Based on a connection-oriented packet switching (CO-PS) model • Intended as a carrier grade all-packet transport technology • Packet-oriented forwarding • Complemented with comprehensive OAM and resiliency capabilities • Profiled after the L2 aspects of IETF MPLS technology • Synergy with IETF IP/MPLS-based service networks and models (inc. multipoint emulation via VPLS/H-VPLS) • Simpler in forwarding scope, less complex in operations (no native IP forwarding) • Can operate independently of their clients (e.g., Ethernet, IP/MPLS, etc.) and associated control networks (management and signaling) • Being specified under ITU-S Study Group 15 (Rec. G.8110.1) & IETF PWE3 (as “MPLS Transport”)
Control Plane Directions: ASON/GMPLS • GMPLS proposed as the single generalized distributed control plane to be used form common control protocol for multiple networking technologies environment, including Packets, TDM/Optical and/or Photonics • GMPLS already define support for: • UNI, I-NNI and E-NNI interfaces (thus easing overlay dynamic approach) • Bidirectional & Unidirectional paths • GMPLS also allows for separation of data plane and control plane • Only control interfaces are used to flood control information • GMPLS allows for “horizontal” scalability in routing domains (thanks to separation of data plane and control plane and recursive topology) • GMPLS allows for “vertical” scalability (same control plane across photonic, TDM and packet layers) GMPLS is the ideal control plane for multilayered networks
Hybrid Transport-Switch implementation Transport instance target vision General Transport Switch architecture Typical Core node implementation Typical WDM node implementation Typical metro node implementation CBR(2,5Gb/s) CBR(<2,5Gb/s) Packets Lambda(ALU colored) CBR CBR - ODU CBR – SDH L2/L3 -Packet ODU switch SDH switch MPLS switch CBR - ODU ODU - ODU SDH - ODU TMPLS - ODU ODU - lambda ODU - lambda ODU - lambda ODU - lambda Och Switch Line
An Scalable Hybrid Transport Architecture Transport Service Switch Carrier Ethernet/MPLS Transport Generalized MPLS Control Plane (G-MPLS) Optical Transport Hierarchy (G.709) SDH/SONET TDM Och ODU Service T-MPLS TDM Service Ethernet Clients VC/VT Clients WDM Servers WDM STM-n/OC-x Servers OAM OAM Circuit Transport Packet / Photonic Transport Purposely designed for carrier-grade Packet Transport Networking • Synthesis of best-in-class packet (IETF) and transport (ITU) features • MPLS profiled, but transport-oriented (wrt. OAM/Resiliency/PM) • Client-independent, medium-independent (Multi-service) • Scalable forwarding, control/management planes (via ASON/GMPLS) • Cost-effective (simple forwarding & comprehensive operations capabilities)