Description
The Modify UE context Request (MUR) is a Diameter command defined in 3GPP specifications, primarily used in the interaction between the Policy and Charging Rules Function (PCRF) and the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Reporting Function (BBERF). It operates within the Gx and Gxx reference points. When network conditions change, a subscriber's service profile is updated, or new charging rules need to be applied, the PCRF initiates an MUR command. This command carries updated Policy and Charging Control (PCC) rules, which include parameters like QoS class identifiers (QCIs), allocation and retention priority (ARP), and charging key information. The receiving node (PCEF/BBERF) then enforces these new rules on the corresponding bearer(s), ensuring the UE's session adheres to the updated policy. This mechanism is crucial for implementing dynamic policy control, enabling services like on-the-fly QoS upgrades for video streaming or real-time application of sponsored data plans. The MUR process maintains session continuity while allowing the network to adapt to changing requirements, forming a core part of the 3GPP's policy framework for intelligent traffic management and monetization.
Purpose & Motivation
The MUR command was introduced to address the need for dynamic, mid-session policy modifications within the 3GPP PCC architecture. Prior to its standardization, policy changes often required cumbersome procedures like bearer deactivation and reactivation, or even full session teardown and re-establishment. This was inefficient, caused service interruption, and limited the network's ability to offer real-time, responsive services. The creation of MUR was motivated by the growing demand for sophisticated service differentiation, such as tiered data plans, quality-on-demand offerings, and network-slicing scenarios. It allows operators to instantly apply new business rules or adapt to network congestion without impacting the user experience. Historically, as mobile networks evolved from simple data pipes to service-aware platforms, the ability to modify sessions dynamically became a fundamental requirement for monetization and efficient resource utilization, which MUR fulfills.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the MUR (Modify UE Context Request) function was enhanced with a clarification regarding the handling of the Max-Requested-Bandwidth parameter. This update provided more precise definitions and procedures for its application within the PCC architecture. The modification ensured consistent behavior for bandwidth management during session modifications across network elements like the PCEF and PCRF.
- Clarification of Max-Requested-Bandwidth TS 29.213CR0721
In Release 17, the MUR (Modify UE Context Request) function was enhanced to enable PCRF control of MPS (Multimedia Priority Service) for DTS (Data Transfer Service). Furthermore, a correction was introduced to allow the retrieval of Network Provided Location information specifically within a MESSAGE request.
In Release 19, the MUR function introduced new mechanisms for the PCRF to address PCEF failure detection, including a specific new condition for the PCRF to detect this failure in a timely manner. Additionally, the release updated the existing procedure for how an Application Function (AF) can trigger the PCEF failure checking process.
Explore further
Broader topics and technologies where MUR plays a role.
Defining Specifications
3GPP specifications that define or reference MUR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.213 vj20 | PCC Signalling Flows and QoS Mapping | Rel-19 |
| TS 29.217 vj00 | Policy and Charging Control (PCC) for Np Interface | Rel-19 |