Skip to main content
Definition Website Computer and Technology

Multiprotocol Label Switching

Subject: Computer and Technology noun /ˌmʌl.tiˈproʊ.tə.kɑːl ˈleɪ.bəl ˈswɪtʃ.ɪŋ/ 1 definition

  1. Definition (noun)

    Entry #171 · Updated

    Multiprotocol Label Switching (MPLS) is a packet-forwarding architecture operating between OSI Layer 2 and Layer 3 that routes traffic using short, fixed-length labels instead of full network-layer address lookups. When packets enter an MPLS network, an ingress router assigns a label corresponding to a forwarding equivalence class, enabling core routers to switch packets along a designated label-switched path by swapping labels rather than inspecting IP headers. Because its label-shim mechanism is independent of both the underlying link technology and the carried payload, MPLS transports IP, Ethernet, and legacy traffic uniformly over a single backbone. It is designed for carrier and enterprise core networks that require traffic engineering, deterministic quality of service, and isolated virtual private networks, rather than end-host routing on the open internet.

    Common Forms

    • Layer 3 MPLS VPN (L3VPN): Pairs MPLS label switching with Border Gateway Protocol (BGP) and Virtual Routing and Forwarding (VRF) tables to deliver isolated, routed IP connectivity across a shared service-provider backbone.

    • Layer 2 MPLS VPN (L2VPN): Transports Ethernet frames or point-to-point circuits across an MPLS core using pseudowires or Virtual Private LAN Service (VPLS), extending a customer's Layer 2 domain across distant sites.

    • MPLS Traffic Engineering (MPLS-TE): Uses constraint-based routing and signaling protocols such as RSVP-TE to steer traffic along explicit, bandwidth-reserved paths and enable rapid failover around link failures.

    • Segment Routing MPLS (SR-MPLS): Simplifies MPLS control planes by encoding an ordered stack of forwarding instructions directly into the packet's label stack at the ingress router, eliminating per-flow state in core switches.

    Example

    A regional bank connects 120 branch offices to two primary data centers over a carrier's MPLS backbone, assigning high-priority labels to VoIP traffic and lower-priority labels to nightly database backups at each branch ingress router. Transit routers in the carrier core swap those short label headers along traffic-engineered paths to keep voice latency predictable without inspecting each packet's IP destination at every hop.