Diameter Routing Message Priority

Description

Diameter Routing Message Priority (DRMP) is a protocol extension defined in 3GPP to enhance the capabilities of Diameter-based signaling networks, particularly within the IP Multimedia Subsystem (IMS), Evolved Packet Core (EPC), and 5G Core (5GC). It is implemented as an Attribute-Value Pair (AVP) that can be included in Diameter request messages. The DRMP AVP carries an integer value representing the message's priority, with lower numerical values typically indicating higher priority (e.g., 0 for highest priority). The primary function of DRMP is to provide a standardized, in-band signaling mechanism for conveying priority information, allowing Diameter nodes to make more intelligent routing and processing decisions.

Architecturally, DRMP operates within the Diameter base protocol framework (RFC 6733). When a Diameter client or server generates a request (e.g., a Credit-Control-Request (CCR) or an AA-Request (AAR)), it can populate the DRMP AVP based on local policy, the type of service, or subscriber profile. This message is then sent into the Diameter network, often traversing one or more Diameter Routing Agents (DRAs). These intermediate DRAs, which are crucial for scalability and routing in large networks, inspect the DRMP value. Using this information, a DRA can implement priority-aware routing logic. For example, during periods of network congestion or node overload, the DRA can prioritize the forwarding of high-priority messages (like emergency service requests or messages for premium subscribers) while potentially delaying or rejecting lower-priority traffic. This is a key tool for implementing overload and congestion control mechanisms as specified in 3GPP.

The DRMP value influences behavior at multiple points. Beyond routing agents, the destination Diameter server can also use the DRMP to prioritize the order in which it processes incoming requests from its queue. The specifications define procedures for how DRMP values should be generated, forwarded, and potentially modified by trusted nodes. Its introduction formalized what was previously often handled via proprietary or network-local mechanisms, ensuring interoperability between equipment from different vendors in multi-vendor core networks. DRMP is a critical component for achieving carrier-grade reliability and service differentiation in all-IP core networks that rely heavily on Diameter signaling for authentication, authorization, accounting, and policy control.

Purpose & Motivation

DRMP was created to address the challenges of managing signaling load and ensuring service availability in increasingly complex and high-scale Diameter signaling networks. As 3GPP networks evolved to all-IP architectures (IMS, EPC), Diameter became the primary protocol for real-time AAA and policy functions. Without a standardized priority mechanism, all Diameter signaling messages were treated with equal importance by routing agents. This posed a significant problem during signaling storms or node failures, as critical messages (e.g., for emergency calls, handovers, or high-value customers) could be dropped indiscriminately alongside less important traffic, degrading essential services.

The development of DRMP in Release 13 provided a standardized solution to this problem. It was motivated by the need for explicit overload control mechanisms within the Diameter protocol itself. DRMP allows network functions and operators to implement policy-based priority marking. This enables the network to gracefully degrade under load by protecting high-priority sessions and services, a fundamental requirement for telecom-grade resilience. It addressed the limitations of previous ad-hoc approaches and provided a tool for fulfilling regulatory requirements for emergency service support and for implementing commercial service differentiation within the signaling plane.