MPC

Media Preconfigured Channel

Services →
Introduced in Rel-8 Also in: Core Network, Radio Access Network

MPC is a network capability that pre-establishes bearer resources for a media flow before a user's service request to enable ultra-low latency for critical communications like Mission Critical Push-To-Talk.

Category
Services
Introduced
Rel-8
Where
Services
Also touches
2 segments
Specifications
6 specs
MPC Description Purpose Detected Changes Specifications

Description

The Media Preconfigured Channel (MPC) is a network architectural feature designed to support ultra-low latency and instant media establishment for critical communication services, most notably Mission Critical Push-To-Talk (MCPTT) as defined by 3GPP. It operates on the principle of pre-establishing the necessary bearer resources—the logical communication path with defined Quality of Service (QoS)—between network entities *before* the actual media (voice, video, data) needs to flow. This pre-configuration eliminates the signaling delay typically associated with setting up a bearer during call initiation, which can be hundreds of milliseconds, thereby achieving near-instantaneous media transmission.

Architecturally, MPC involves coordination between the core network and the Radio Access Network (RAN). For a group of users subscribed to a mission-critical service, the network proactively establishes a preconfigured bearer context. This context includes all the necessary QoS parameters (such as QoS Class Identifier, Guaranteed Bit Rate), tunnel endpoint identifiers (for GTP tunnels in the core), and radio resources. The context is stored in the relevant network functions: the User Plane Function (UPF) and Session Management Function (SMF) in the 5G Core, or the PGW and SGW in the EPC, as well as in the base station (gNB or eNB). The bearer remains in an 'idle' or 'dormant' state, consuming minimal resources until activated.

The mechanism works in tandem with service layer signaling. When an MCPTT user presses the push-to-talk button, the service layer (the MCPTT application server) sends an activation request. Because the bearer is already preconfigured, the network can immediately map the media flow to the existing bearer resources. The RAN can swiftly transition the user's radio connection from an idle state to active, or allocate the pre-reserved radio resources, and the UPF can start forwarding packets through the pre-established GTP tunnels. This results in extremely low End-to-End (E2E) latency for the first media packet. The MPC is managed through 3GPP-defined procedures involving the Policy Control Function (PCF) to authorize the pre-configuration and the Unified Data Management (UDM) for subscriber data. Specifications like TS 23.167 and TS 29.163 detail the signaling flows and interactions between the service layer, core network, and RAN to create, manage, and activate these preconfigured channels.

Purpose & Motivation

MPC was created to solve the fundamental latency problem in traditional cellular networks for mission-critical and real-time interactive services. Standard cellular voice and data sessions establish bearers on-demand when a user initiates a call or data session. This setup involves multiple signaling steps between the device, RAN, and core network, introducing a delay often unacceptable for critical scenarios like public safety, where a half-second delay in a push-to-talk conversation can be dangerous. The existing LTE/EPC architecture was optimized for efficiency, not for the instantaneity required by first responders.

The primary driver was the standardization of Mission Critical Services (MCS) over LTE, starting in 3GPP Release 13. MCPTT, as the flagship service, demanded sub-300ms call setup times, including media path establishment. The traditional bearer setup procedure could not meet this target. MPC addresses this by shifting the latency-critical path establishment work to a time when latency is not critical—such as when a user registers for the service or joins a talkgroup—so that when the urgent moment arrives, the path is ready to use. It effectively trades a small amount of persistent resource reservation for a massive reduction in reaction time.

Furthermore, MPC enables efficient group communications. For a large talkgroup, preconfiguring a shared multicast/broadcast bearer (like evolved Multimedia Broadcast Multicast Service - eMBMS) as an MPC allows all group members to receive media instantly when it is broadcast, without individual unicast setup delays. This evolution represents a significant shift in network design philosophy, moving from purely on-demand resource allocation to predictive and pre-emptive resource management to support latency-sensitive and life-critical applications over commercial cellular infrastructure.

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-15.

Rel-15 1 change

In Release 15, the MPC (Media Preconfigured Channel) function was not newly introduced; the provided grounding context and change request titles do not describe any MPC-specific features. The technical details from the context focus on media handling for IMS emergency sessions, including support for voice, GTT, and other media like video based on PSAP capabilities and local regulation, as well as procedures for domain selection and session establishment. The withdrawn CR title regarding an indoor industrial channel model is unrelated to the MPC function.

  • Addition of indoor industrial channel model – version created in error – withdrawn TS 38.901CR0023
Rel-16 2 changes

In Release 16, the MPC function was not explicitly defined or modified in the provided grounding context. The listed Change Request titles pertain solely to the addition of an indoor industrial channel model for IIoT, which is unrelated to media preconfiguration for emergency calls. The grounding text details IMS emergency session media handling, but does not specify any new MPC-related procedures or capabilities introduced in this release.

  • Addition of indoor industrial channel model – creation of rel-16 report TS 38.901CR0023
  • CR to TR 38.901 for remaining open issues in IIOT channel modelling TS 38.901CR0024
Rel-19 4 changes

In Release 19, the MPC function was not explicitly mentioned in the provided grounding context or associated Change Request titles. The listed CRs and specification text focus on channel model enhancements for higher frequency bands (7-24 GHz) and Integrated Sensing and Communication (ISAC), along with existing IMS emergency session procedures for media handling, but do not describe new MPC-specific features for this release.

  • Introduction of Rel-19 7-24 GHz channel model enhancements TS 38.901CR0026
  • CR to introduce channel model for ISAC TS 38.901CR0027
  • Correction of channel modeling enhancements for 7 - 24 GHz TS 38.901CR0028
  • Correction of Rel-19 enhancements for channel modeling for 7-24 GHz TS 38.901CR0036

Explore further

Broader topics and technologies where MPC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.167 vj11 IMS Emergency Sessions Rel-19
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19
TS 29.199 v1900 Multimedia Messaging Web Services Rel-9
TS 29.863 v820 IMS-CS Multimedia Interworking Feasibility Study Rel-8
TR 38.900 vf00 Channel Model Study for >6 GHz Rel-15
TR 38.901 vj10 Channel Model for 0.5-100 GHz Rel-19