Telco service providers worldwide select MPLS-TP
Next generation transport networking is heavily based on PTN solutions
Consumers adoption of mobile, cloud and video services require a lot more bandwidth and force telecommunication service providers worldwide to develop their existing networking infrastructure by selecting appropriate technologies and gear.
Currently in data networks, standard MPLS technology is the de-facto selection. This pure packet and carrier-grade technology offers connection-oriented operation with a very wide set of traffic engineering capabilities.
MPLS developments combined with next generation transport requirements open the door for MPLS-TP, and indeed, providers gradually include MPLS-TP in their networks. MPLS-TP introduces the following key benefits:
- Separated data plane with bi-directional PW and LSP for intuitive, predictable and deterministic transport
- Separated control plane with centralized NMS and static configuration approach for broader view of the network and planning and prediction tools
- Transport class and normally hardware based OAM. Enhanced tools include fault management, performance monitoring, and in-band PW/LSP/Section OAM levels
- Improved resiliency with PW/LSP sub 50mSec protection
Putting this all together: continues adoption of new methods based on MPLS-TP technologies, in addition to the widely deployed IP-MPLS leads to dual stack implementations in unified packet transport network. These successful networks demonstrate high capacity together with optimized cost for any mixture of available services.
Multi-service next-generation Packet Transport Network delivers any service type
Why dual stack IP-MPLS and MPLS-TP
Reasoning and benefits
- Flexibility to select IP-MPLS or MPLS-TP per application and/or region: with dual stack implementation downlinks can be used to serve different application and/or region with the technology that offers the best fit. Such separation and flexibility lower the total cost, simplifies network management and provide subscribers their required quality of service.
- Motivation to converge all services over unified PTN: one of the key elements in next-generation networking transport is the vision of having all types of services running on unified networking layer. This convergence includes both mobile and legacy services that typically mapped to MPLS-TP as well as residential triple play and enterprise VPN services that typically mapped to IP-MPLS. Therefore, with dual stack implementation the goal to perform complete migration and achieve unified packet transport network is doable and practical.
- Motivation to reorganize and join transport and data groups: another key element in next-generation networking is to bring together the different transport and data departments and work out together all aspects of networking challenges. This kind of transformation upgrades the service provider’s competitiveness with operational simplicity and budget optimization. It is clear that each group has its own gurus, expertise, methodologies, and existing services and subscribers. With dual stack implementation data groups continue as routing knowledge center while transport improvement is done using MPLS-TP.
- Simpler IP-MPLS to MPLS-TP migration: since it is reasonable to assume that MPLS-TP adoption will increase over time, networks will need to gradually adopt MPLS-TP gear. With dual stack implementation such migration is inherent and does not require product replacement, hardware upgrades and extra training. Smooth migration from IP-MPLS to MPLS-TP domains is easiest when dual stack is taking place from day one.
- Lower risk due to the evolving MPLS-TP standardization process: naturally, MPLS-TP technology imposes challenges in its standardization. The evident benefits and strengths from this technology brought international standard bodies such as IETF and ITU-T to work intensively on turning all aspects of MPLS-TP tool set into standards. This evolving effort was not completed yet and therefore dual stack implementation provides risk mitigation since the ability to quickly and natively revert to IP-MPLS provides a “safety net” against any possible issues.
- Simpler interoperability between IP-MPLS and MPLS-TP domains: both IP-MPLS and MPLS-TP relay on exactly the same data plane and use the same pseudowires and LSPs. With dual stack implementation the gateway that connects the two domains is simpler and interoperability between the two domains requires the minimal effort. The figure below these bullets demonstrates MS-PW as an example for end-to-end service delivery over IP-MPLS and MPLS-TP domains.
- Commercial perspective – option to revert to IP-MPLS: executive management, accounting and purchasing departments require alternative suppliers and technologies to assure continues service delivery to their customers. As a result, dual stack implementation provides risk reduction with the ability to quickly and natively revert to IP-MPLS.
- Network management: typically, networking vendors that offer dual stack implementation include single network management system that can handle both IP-MPLS and MPLS-TP. This is a valuable asset with operational and cost benefits since it is reasonable to assume different types of services at the same network domain and packing all management aspects into a single system is the most intuitive approach.
- Capex and Opex considerations: one of MPLS-TP promises in its transport design is to optimize the total cost of ownership, both in capital and operational expenditures. With dual stack implementation there is no need for separated and dedicated fibers and network management systems. Dual stack enables deployment of MPLS-TP with its cost advantages alongside IP-MPLS with its rich feature-set advantages.
Dual stack implementation enables multi-segment service stitching across different network domains
To conclude: reasoning to design and deploy dual stack IP-MPLS and MPLS-TP include wide range of commercial, technical and economical aspects. The concept of dual stack implementations is not new or specific only to these two technologies. For example, “dual stack IPv4 and IPv6” is a very popular migration solution in other networking layer. With dual stack implementation telco service providers can enjoy lower risks from new technology introduction, simpler migration and interoperability, and lowest possible cost. Fulfilling the “unified PTN” networking vision is becoming practical with dual stack solution.
Dual stack IP-MPLS and MPLS-TP at CM-4000 PTN products
End-to-end implementation with comprehensive scale and cost capabilities
Orckit-Corrigent designed and developed dual stack IP-MPLS and MPLS-TP all across its CM-4000 PTN portfolio. All the benefits mentioned in the previous section are achievable with this solution. This offering demonstrated interoperability during a public event at 2010 and is currently being deployed at live networks worldwide.
The CM-4000 products include 1RU CM-401x access series with 16Gbps of capacity, 3RU CM-4140 pre-aggregation switch-router with 84Gbps of capacity, CM-4206/CM-4314/CM-4314T medium/large/extra large capacity backbone network elements, and the CM-View NMS. In addition to dual stack IP-MPLS and MPLS-TP, the products can deliver any mix of PDH E1, SDH STM-1/4/16, GE and 10GE services over unified and pure packet networking layer.
Dual stack implementation at the CM-4000 products includes innovative capabilities of IP-MPLS and MPLS-TP traffic separation. This can be done per LSP – meaning that the same physical port and fiber deliver both technologies. In this innovation, manual or automatic provisioning (considering traffic-engineering properties such as class-of-service and bandwidth) is done per application, application is mapped to a specific service, service is mapped to a specific pseudowire and multiple pseudowires are being transported in a single LSP. This innovative mechanism provides maximum flexibility, simplifies interoperability with external IP-MPLS domains, and enables dedicated protection per LSP type and even per PW.
Orckit-Corrigent CM-4000 PTN portfolio
Innovative offering of IP-MPLS and MPLS-TP all across CM-4000 portfolio: dual stack per LSP