DRA

Diameter Routing Agent

Core Network →
Introduced in Rel-8

DRA is a network element that provides routing and proxy functions for Diameter signaling messages in the EPC and 5G Core, centralizing routing logic for scalable policy, charging, and authentication.

Category
Core Network
Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
9 specs
DRA Description Purpose Related Classification Detected Changes Specifications

Description

The Diameter Routing Agent (DRA) is a fundamental component within the 3GPP Diameter-based signaling architecture, primarily used in the Evolved Packet Core (EPC) for LTE networks and, in certain interworking scenarios, with the 5G Core (5GC). It operates as a specialized Diameter relay agent, intercepting, examining, and forwarding Diameter messages between various network functions (NFs) such as the Policy and Charging Rules Function (PCRF), Online Charging System (OCS), and Home Subscriber Server (HSS). Its core function is to perform routing based on information within the Diameter messages, including the Application-ID, Destination-Realm, and Destination-Host AVPs (Attribute-Value Pairs). This routing intelligence decouples the network functions from needing direct, static knowledge of each other's addresses, which is essential in large-scale, multi-vendor deployments and for facilitating roaming.

Architecturally, a DRA can operate in two primary modes: stateless and stateful. In stateless mode, the DRA routes each Diameter request independently based on the information in that single message. In stateful mode, which is mandatory for certain procedures like the Gx interface for policy control, the DRA maintains transaction state. It binds together the request and answer messages of a Diameter session, ensuring that all subsequent signaling for that session is routed back through the same DRA instance and to the same downstream network function (e.g., the same PCRF). This session binding is critical for maintaining consistent policy and charging contexts. The DRA achieves this by inserting a proprietary Route-Record AVP as it forwards a request, which is then used to route the corresponding answer back.

The DRA's role extends beyond simple routing. It provides critical network functions like load balancing across pools of network elements (e.g., multiple PCRFs), message prioritization, topology hiding, and diameter edge agent (DEA) functionality for inter-operator roaming interfaces (e.g., S9, S6a). By acting as a central routing hub, it dramatically reduces the number of direct Diameter connections (NxN mesh) required between network functions, simplifying network management, improving scalability, and enhancing network resilience. In 5G networks, while the Service-Based Architecture (SBA) uses HTTP/2 and service-based interfaces, the DRA remains relevant for interworking with EPC, legacy Diameter interfaces, and within the Binding Support Function (BSF) for 5GC policy control, ensuring a smooth transition between network generations.

Purpose & Motivation

The DRA was introduced to solve critical scalability and operational challenges arising from the adoption of the Diameter protocol as the primary signaling protocol for policy, charging, and authentication in the 3GPP Evolved Packet Core (EPC), starting with Release 8. Prior to the DRA, network functions like the PCRF, OCS, and HSS were envisioned to communicate via direct point-to-point Diameter connections. In a large network with multiple instances of each function, this creates an NxN mesh of connections, which is complex to provision, manage, and scale. Adding a new network function would require reconfiguring all existing peers, leading to operational inefficiency and potential service disruption.

The DRA addresses this by introducing a centralized routing layer. Its creation was motivated by the need to support commercial deployments involving equipment from multiple vendors and to facilitate seamless roaming between operators. Without a DRA, roaming would require complex bilateral agreements and direct connections between every HSS and visited network PCRF, which is impractical. The DRA, acting as a Diameter Edge Agent, provides a standardized, secure point of interconnection for roaming partners. Furthermore, it enables advanced network capabilities like load balancing and session binding, which are essential for reliable policy and charging control. It abstracts the underlying network topology, allowing operators to scale, upgrade, or replace network functions without impacting the entire signaling fabric.

Classification

Part ofEPC
Related approachesPCRFBSF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, the DRA (Diameter Routing Agent) function was newly defined as a service consumer. This enhancement is reflected in the established DRA procedures, which include its role in PCRF selection for the Np reference point to route RAN User Congestion Information (RUCI) reports from the RCAF based on IMSI and APN.

Rel-16 1 change

In Release 16, the DRA function was newly defined as a service consumer of the Nbsf_management service. This addition integrates the DRA into the service-based architecture framework for network function discovery and selection.

  • Adding DRA as Nbsf_management service consumer TS 29.521CR0080

Explore further

Broader topics and technologies where DRA plays a role.

Defining Specifications

3GPP specifications that define or reference DRA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.203 vj20 Policy and charging control architecture Rel-19
TS 29.154 vj00 Nt Reference Point Protocol Rel-19
TS 29.201 vj00 RESTful Rx Interface for AF-PC Communication Rel-19
TS 29.213 vj20 PCC Signalling Flows and QoS Mapping Rel-19
TS 29.521 vj40 5G Binding Support Management Service Stage 3 Rel-19
TS 29.809 vc00 Diameter Overload Control Study Rel-12
TS 29.810 vd00 Diameter Load Control Study Rel-13
TS 29.816 va00 PCRF Failure & Restoration Study Rel-10
TS 29.817 vc10 Study on XML-based Rx interface for PCC Rel-12
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.