LDP

Label Distribution Protocol

Protocol
Introduced in R99
A protocol defined by the IETF (RFC 5036) and referenced by 3GPP for distributing labels in MPLS (Multi-Protocol Label Switching) networks. It enables routers to establish Label Switched Paths (LSPs) by exchanging label mappings. In 3GPP architectures, it's used for traffic engineering and transport network control.

Description

The Label Distribution Protocol (LDP) is a fundamental control-plane protocol in MPLS networks, standardized by the IETF in RFC 5036. While not a 3GPP-originated protocol, it is referenced and utilized within 3GPP specifications (e.g., 23.207 on QoS, 23.802 on architecture enhancements for transport) for managing the transport layer that underlies the mobile core network. LDP's primary function is to automatically establish and maintain Label Switched Paths (LSPs) that map IP routing information to data-plane labels, enabling efficient packet forwarding through an MPLS cloud.

LDP operates between Label Switch Routers (LSRs). It works by creating LDP sessions between adjacent LSRs (LDP peers). Over these sessions, LSRs exchange messages to advertise, request, and release label mappings. The core process begins with each LSR running its IP routing protocol (like OSPF or IS-IS) to build a routing table. LDP then uses the Forwarding Equivalence Class (FEC) concept, typically corresponding to an IP prefix, to group packets that should be forwarded the same way. Each LSR independently binds a local label to a FEC for its incoming direction. It then distributes this binding to its LDP peers. Through this distributed exchange, a complete end-to-end LSP is established, where each hop swaps an incoming label for an outgoing label.

In a 3GPP system, LDP is particularly relevant in the context of the IP Multimedia Subsystem (IMS) and the Evolved Packet Core (EPC) transport. For example, within the IMS, LDP can be used to set up MPLS LSPs between P-CSCF, I-CSCF, and S-CSCF nodes to ensure QoS-guaranteed transport for SIP signaling and media flows as per the Policy and Charging Control (PCC) rules. It allows the transport network to provide Traffic Engineering (TE) capabilities, directing different classes of traffic (e.g., voice, signaling, user data) over specific paths with reserved resources. LDP, along with its extensions like CR-LDP (Constraint-Based Routing LDP) or in conjunction with RSVP-TE, gives network operators fine-grained control over the backbone traffic supporting mobile services.

Purpose & Motivation

LDP was created to solve the problem of scalable, efficient label distribution in pure IP-based MPLS networks, moving away from manual configuration or piggybacking on other protocols. Before LDP and similar protocols, establishing LSPs was cumbersome. The motivation was to automate the creation of LSPs in direct correlation with the underlying IP routing, allowing the MPLS network to be 'routing driven.' This automation is crucial for large-scale carrier networks, including those underpinning 3GPP systems.

3GPP references LDP to leverage the benefits of MPLS in mobile backhaul and core transport. Traditional mobile backhaul used TDM/ATM, which lacked flexibility. The shift to all-IP transport required mechanisms for traffic isolation, QoS guarantees, and efficient forwarding—all strengths of MPLS. LDP provides the standardized control protocol to realize these MPLS benefits. It addresses the limitations of using plain IP routing in the transport network, which is unaware of bandwidth constraints or service-specific paths. By using LDP (and its constraint-based extensions), 3GPP architectures can ensure that high-priority control plane traffic (e.g., S1-MME, Diameter) or real-time user plane traffic receives a dedicated, reliable path through the network, enhancing overall service quality and network manageability. Its use from 3GPP R99 onwards reflects the early adoption of IP/MPLS in core network evolution.

Key Features

  • Routing-Driven Label Distribution: Establishes LSPs based on the existing IP routing topology, simplifying network operations.
  • Peer-to-Peer Protocol: Uses direct TCP sessions between LSRs for reliable exchange of label mapping messages.
  • Forwarding Equivalence Class (FEC): Groups packets destined for the same endpoint and treatment, forming the basis for label binding.
  • Label Advertisement Modes: Supports both Downstream Unsolicited (DU) and Downstream on Demand (DoD) modes for flexible operation.
  • Session Reliability: Includes mechanisms for session initialization, keepalive, and graceful notification of errors.
  • Foundation for MPLS Services: Enables basic MPLS unicast forwarding, which is a building block for more advanced services like VPNs (L3VPN) used in mobile core.

Evolution Across Releases

R99 Initial

Initial referencing of MPLS and associated control protocols like LDP within 3GPP for transport in the core network. Recognized the role of MPLS in providing QoS-aware transport for IP-based services, including early IMS and backbone data services. LDP was identified as a key protocol for establishing basic LSPs in this all-IP transport layer.

Defining Specifications

SpecificationTitle
TS 23.207 3GPP TS 23.207
TS 23.802 3GPP TS 23.802