I nternational Telecom m unication Union ITU-T Routing in Multi- -Layer Layer Routing in Multi Transport Networks Transport Networks Jonathan S adler Office of the CTO – Technology S trategy, Tellabs Chair, OIF Architecture & S ignaling Working Group S G15 S pecial Representative to IETF for Routing I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6
Agenda ITU-T o S ervice-based routing o AS ON Multi-layer Routing Architecture o Remote Path Computation I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2
Discussion of Convergence is Everyw here ITU-T o “ … the access infrastructure telcos are building to support IPTV services will finally give them the ability to converge voice, video and data onto a single network… ” – Americas Network Pseudo-Wires are “ the solution for convergence in future o telecom networks, because it preserves profitable legacy services even as it enables the creation of a truly next- generation network” – Heavy Reading “ 3GPP defines a new subsystem to enable the convergence of o voice and data applications and the harmonization of various mobile network technologies over IP” – Deutsche Bank Convergence is changing the face of the network I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 3
The Benefits of Convergence ITU-T o S ervices reduced to applications on converged infrastructure • Reduced operations • Reduced core cap-ex o New services can be provided • Individual Networks per S ervice limited service interaction o Packet & optical routing convergence can improve network performance even if only IP services are provided I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 4
The Reality of Convergence ITU-T o Non-native service delivery • End User S ervices are always layered on something else o The whole network will not be converged overnight • Too many existing services already deployed o The whole network will never be completely converged • Fully depreciated equipment still generates revenue I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 5
How Can This Be Accom m odated? ITU-T o Common flexible control method that understands layering • Path Computation that understand layered net works —Provides service routing given view of potential/ available server layer resources • S ignaling mechanisms that coordinate calls in different layers • OSS es that can handle integrated views of layer networks —Relate services requests (client layer calls) to server resources in use • Definitions for server layer resources other than SONET/ S DH I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 6
The Network is Segmented Access A ITU-T CPE-A Core CPE-B Access B I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 7
Different Organizations Access A Manage Different ITU-T Parts of the Network CPE-A Core CPE-B Access B I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 8
Provisioning We will fill your order Service is Access A within 3 months expensive and ITU-T time consuming CPE-A Core CPE-B Access B I forgot that we ordered this service! I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 9
Sure, we’re Control Plane setting your service up as Speeds it up Access A we speak ITU-T CPE-A Core CPE-B Access B Wow, that was fast! I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 0
Will use of different technologies cause Access A (Ethernet) the problem to ITU-T reoccur? CPE-A Core (MPLS Pseudo Wire) CPE-B Access B (SONET/SDH) I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 1
It doesn’t have to… Access A (Ethernet) ITU-T GE/NNI OCN Ethernet Network GE/NNI OCN UNI UNI GE/NNI T1, T3, OCN GE/NNI UNI CPE-A T1, T3, OCN UNI 10/100 BPON BPON OCN/NNI BPON GE/UNI Core 10/100 (MPLS Pseudo Wire) GE/MPLS MPLS Network* CPE-B Access B 10/100 GE/UNI nxT1 (SONET/SDH) OCN/NNI OCN/NNI nxT1 T1, T3, OCN UNI or Null 10/100 T1, T3, OCN UNI or Null OCN/NNI OCN/NNI OCN/NNI STS1 Network* OCN/NNI I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 2
Sure, we’re setting your service up as we speak ITU-T GE/NNI OCN Ethernet Network GE/NNI OCN UNI UNI GE/NNI T1, T3, OCN GE/NNI UNI T1, T3, OCN UNI 10/100 BPON BPON OCN/NNI BPON GE/UNI 10/100 End-to-end Signaled Service Provisioning! GE/MPLS MPLS Network* 10/100 GE/UNI nxT1 OCN/NNI OCN/NNI nxT1 T1, T3, OCN UNI or Null 10/100 T1, T3, OCN UNI or Null OCN/NNI OCN/NNI OCN/NNI STS1 Network* OCN/NNI Wow, that was fast! I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 3
I nternational Telecom m unication Union ITU-T ASON Multi- -layer Routing layer Routing ASON Multi Architecture Architecture I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6
Multi-layer overview ITU-T o Need path computation for a network made up of many different technologies, in any layer that has switching flexibility. o Current methods separate network topologies per technology, creating separate discontinuous graphs o Path Computation methods only operate on graphs without discontinuity. Need to make a continuous routing view for a multi-technology network I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 5
Representation of Server Layer connectivity ITU-T o G.8080 (2006): Two maj or approaches, with two minor forms: • S erver Layer Representation using Links only: —Client layer links resulting from established server layer trails o Result of cross connection of fibers, HOVC paths, etc. —Client layer links provided by potential server layer trails o Abstract links representing potential connectivity o Requires management specification • S erver Layer Representation using Links & S ubnetworks —Client layer abstract node containing server layer o Abstract topology representing potential connectivity o Can be generated automatically —S erver layer topology shadow in client layer o Non-abstract topology showing server links incl. attributes o Can be generated automatically I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 6
Representation using client links ( actual) ITU-T o Connection is established in S erver Layer o Link appears in Client Layer I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 7
Representation using client links ( potential) ITU-T o Link is put into client layer knowing that server layer resources exist o S erver layer trail is established when link is put into use I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 8
Representation using client subnetw ork ITU-T o Client layer is provided with an abstract node that represents the server layer connectivity • Routing can compute a path in the client layer o S erver layer connection established when abstract node appears in client layer ERO I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 9
Representation using client subnet & links ITU-T o Client layer contains server layer topology o Routing can see all attributes of server layer resources o S erver layer connection established using client layer ERO information I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 0
W hat inform ation is required? ITU-T o Understanding of adaptations in use G.805 o Understanding of termination/ switching capability o Ability to control choice of server layer trails in Policy place of client layer links I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 1
W hat inform ation is required? ITU-T o GMPLS Routing Announcements • Limited to switching capability information • Need to add adaptation and termination capability info o Adding this information creates a “ backward compatibility” problem • S imilar to problem that exists between MPLS and GMPLS I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 2
I nternational Telecom m unication Union ITU-T ASON Support for ASON Support for Remote Path Computation Remote Path Computation I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6
W hat is PCE? ITU-T o PCE = Path Computation Element o Facilitated by AS ON Functional Architecture • Functional Architecture makes no assumptions on physical location o Essentially a remote procedure call method • Used within an area between S ignaling (CC) and Routing instances (RC) • Used between areas by routing instances (RC) I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 4
Recommend
More recommend
