MUR

Modify UE context Request

Core Network →
Introduced in Rel-13

MUR is a Diameter command in the PCC architecture that requests modifications to a UE's session context, enabling dynamic policy updates like QoS changes without a full session re-establishment.

Category
Core Network
Introduced
Rel-13
Where
Core Network › Evolved Packet Core
Specifications
2 specs
MUR Description Purpose Related Classification Specifications

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

Part ofPCRF
Related approachesPCEFQoS

Evolution Across Releases

Rel-13 Initial

Introduced as a Diameter command within the PCC architecture to support dynamic session modification. It established the basic framework for the PCRF to request updates to a UE's active session context, including QoS and charging rules, over the Gx/Gxx interfaces.

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.

SpecificationTitleRelease
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
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.