MPLS-TP Helps Mass Transit Move from Two Networks to One

Last year, U.S. public transit ridership increased by 16% compared to the year before, according to the American Public Transportation Association. In total, more than 7.1 billion total trips were made covering 36.9 billion miles in 2023 using some form of commuter system (subway, rail or bus).

When it comes to mass transit operations, most agencies and authorities have long operated under two separate networks:

• A network for critical systems (vital communications): train control (CBTC, PTC and ERTMS), signaling, fire detection, etc.
  
  
• A network for non-critical systems (non-vital communications): cameras, smart cards, passenger infotainment, digital signage, etc.
  
  

This common approach comes with drawbacks, however. For starters, managing two distinct networks increases complexity, as teams juggle maintenance work, upgrades and troubleshooting across distinct infrastructures and systems. Separate networks also widen the cyberthreat landscape, increasing the potential for cybersecurity vulnerabilities within mass transit organizations.

Physically segregating critical and non-critical networks also creates information siloes. For example, if the network that supports the train control system can’t communicate with the network that supports the digital signage system, then passengers may not be able to receive the real-time travel updates or notifications they rely on to get from point A to point B.

Finally, as mass-transit activity grows, scalability also becomes a concern with two networks. Both must be able to expand in tandem to adapt to future needs.

Streamline Networks through MPLS-TP Technology

To streamline operations, centralize control and maintenance, reduce costs and improve communication, it’s crucial for mass transit agencies to consider the possibility of unifying their critical and non-critical networks. This can be done through MPLS-TP (multi-protocol label switching – transport profile) technology.

MPLS-TP Explained

While you’ve likely heard of IP/MPLS networking protocol, MPLS-TP is different.

Defined in RFC 5317, MPLS-TP is based on MPLS technology (as is IP/MPLS) and optimized for mission-critical networks like those found in mass transit environments. The product of a joint effort between ITU-T and IETF, MPLS-TP is designed to address the unique needs of OT networks that IP/MPLS can’t manage.

As a packet networking technology, MPLS-TP delivers data quickly and accurately to any device, offering Quality of Service (QoS) that deals with real-time data, end-to-end OA&M (operations, administration and maintenance) and protection switching.

Instead of running unwanted dynamic protocols, MPLS-TP incorporates the key requirements of an OT network: in-band OAM, static configuration and bidirectional forwarding.

These features make MPLS-TP the best fit for deploying packet-based technology in mass-transit networks. By being able to effectively “slice and dice” your services and engineer network communications according to your needs, the protocol allows mass transit agencies to precisely manage and segregate traffic flow and guarantee bandwidth for the applications that require it.

In other words, MPLS-TP can support critical communication system requirements, including train control, signaling and fire detection systems, as well as non-critical operational systems, such as cameras, remote monitoring systems, security systems and passenger information systems.

The Benefits that MPLS-TP Can Provide

Because it utilizes deterministic technology, MPLS-TP makes sure a path is established before data is transmitted, guaranteeing specific levels of latency and delay for predictable network traffic behavior. This confirms consistent low latency and low jitter for mission-critical mass transit applications.

MPLS-TP also supports high levels of scalability for networks of all sizes, which means it can support a mass transit network as it grows in accordance with the demands of travelers. Because accelerated levels of network traffic can be managed without compromising performance or uptime, service does not suffer as a result of network overload.

Because the protocol provides robust, advanced OAM capabilities, network operators can rely on the assurance of connectivity checks and enjoy reduced operational complexity while maintaining the network control they need. Even operators that don’t have lots of experience can manage an MPLS-TP network without complex onboarding or hours of training.

For mass transit agencies that utilize legacy technologies like SDH/SONET, MPLS-TP can also serve as a practical migration path to more modern technology when the time is right.

How Belden Supports MPLS-TP Networks

Belden makes it extremely easy to commission and maintain MPLS-TP networks and dial in bandwidth requirements for different traffic paths so that the network is always available.

Managed through a GUI-based network management software (NMS) application, an entire network can be built and commissioned completely offline. This allows validation of your network design before it’s deployed to reduce rework, labor costs and revenue disruption.

Once devices are installed on the network, the NMS helps discover them and push configurations out, simplifying the process.

Learn more about how we can help.

Related Links

• MPLS-TP or IP/MPLS Networking Protocol
• Uninterrupted Power White Paper
• MPLS-TP for Utilities: It's Time for New Backbone Technology