Search

MPLS-TP, PTN Transport

MPLS-TP

The MPLS-TP (Multiprotocol Label Switching - Transport Profile) is a variant of the IP-MPLS protocol issue in 2006 from Internet Engineering Task Force (IETF) together with International Telecommunication Union Telecommunication Standardization (ITU-T).

This PTN (Packet Transport Network) protocol is a simplified version of IP/MPLS which is easier to deploy and focuses on the Industries and Mission Critical Communication. This includes the Power industry as well as Teleprotection, Air Traffic Management, Railway-Mobility, Oil & Gas, Defense and Carriers, as well as other customers that require high level of bandwidth stability, latency and security to transport voice communication, SCADA, signalization, power control, etc.

The MPLS IP or TP applies a Label Switching Path (LSP) on packet from multiple protocols to accelerate the speed of their distribution in Mesh infrastructure or over VPN without packet analysis.

The MPLS-TP is the right evolution for TDM/SDH/SONET infrastructures to carry the Multiservice TDM together with high volume of packets ,and it is easier to deploy stable transport than IP/MPLS or IP and Carrier Ethernet for long distances, thanks to:

  • MPLS-TP is a Connection-Oriented protocol using LSP from edge to edge, where it is easy to deploy the circuits as PseudoWire
  • MPLS-TP has a static planning that is provided by a NMS for the Multiservice TDM access, SDH/SONET, PseudoWire and the creation of circuits over multiple transports,
  • MPLS-TP with bidirectional LSP supports determinist performance for bandwidth, latency, jitter, codirectional transport with synchronization and timing distribution,
  • Large and dynamic bandwidth IP/Ethernet in E-Line, E-LAN and E-Tree services are transported by MPLS-TP over VPWS, VPLS or H-VPLS in case of large number of instances,
  • Multiservice TDM (E1/T1, FE1/FT1, voice, serial…), SDH, SONET, low-rate Ethernet SCADA… are transported in PseudoWire end-to-end (PW) with their frequency and timing synchronization for symmetric and asymmetric traffics
  • MPLS-TP networks support multiples protection based on PseudoWire on LSP/Tunnel as 1+1 or 1:1 to optimize the bandwidth utilization or recovery time, always less than 50ms,
  • MPLS-TP OAM verify the integrity of PW and LSP which is always more flexible than SDH/SONET,
  • Loop Telecom MPLS-TP switches support together GE/10GE MPLS-TP for aggregation and core network, and GE/10GE Carrier Ethernet 2.0 interfaces for access services,
  • Loop Telecom MPLS-TP switches PTN10G/G7820 support also Layer 3 routing services: RIP, OSPF, VRRP, VFR. Some IP/MPLS protocols are in development* as LDP, OSPF routing, PHP termination, Ping, Route and RSVP-TE.
Easy to deploy

TDM are carried in point-to-point PW, switched Ethernet is connected in VPWS for point-to-point or VPLS to support Mesh multipoint. The MPLS-TP is a connection-oriented packed switched profile, the administrator will implement PW and LSP like the circuits for SDH/SONET infrastructure.

herefore, MPLS-TP features the OAM functions for the Alarm Monitoring and Alarm Signaling, Traffic Diagnosis and Circuit Performance Monitoring at every layer (Section, LSP, PW). In addition, this layer 2.5 protocol optimizes the transport over PTN infrastructure with enhanced carrier-grade protection switching, OAM and clock synchronization SyncE and PTP 1588v2.

Fast transport of the MPLS

Based on transmission between 2 LER (Label Edge Router) crossing several LSR (Label Switch Router), the LSP (Label Switching Path) is created by adding/changing a label for fast switching over the path. This bidirectional LSP can carry several PW(TDM) and VPWS/VPLS between two LERs.

The capacity to carry the IP/Ethernet in MPLS-TP over the GE/10GE interfaces is not limited by the intermediate switch LSR with 100G capacity instead of the EoS limitation of the SDH/SONET cross-connect.

Traffic Engineering algorithms guarantee and optimize bandwidth per service

The Traffic Engineering in QoS controls bandwidth of data flow with metering algorithms to reshape rate fluctuations by applying buffers to accommodate burst traffic metering algorithms using Token Bucket (TB): Single Rate Three Color (SRTC), Two Rate Three Color (TRTC) and Hierarchical QoS (H-QoS).

The administrator can define per PW Service, LSP and/or Tunnel:

  • the Traffic rate CIR (Committed Info. Rate) and PIR (Peak Info. Rate)
  • moderate the traffic with CBS (Committed Burst Size) and PBS (Peak Burst Size).

Then OAM can guarantee a fixed bandwidth to TDM PW and SCADA Ethernet PW by Traffic Engineering engine.