Description
Media Identification (MID) is a framework used within 3GPP to uniquely identify and describe distinct media components within a multimedia session established via protocols like the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). It is a crucial part of media negotiation and session control, particularly in IP Multimedia Subsystem (IMS) services. A multimedia session, such as a voice call with video or a multi-stream conferencing service, consists of multiple media streams (e.g., primary audio, secondary video for content sharing, text). Each of these logical media components is assigned a unique MID attribute within the SDP offer/answer exchange. The MID attribute, defined in IETF RFC 5888, is included in the 'm=' (media) line of the SDP description. It allows endpoints and network nodes (like the Media Resource Function Controller, MRFC) to correlate media lines across SDP offers and answers, and to refer to specific media streams for manipulation. For instance, during a session modification, an endpoint can use the MID value to indicate which specific media stream it wishes to put on hold, change the codec for, or remove entirely. This is more robust than using the order of media lines, which can change. Within 3GPP, MID is used in conjunction with other SDP and SIP mechanisms for features like Early Media, Interactive Connectivity Establishment (ICE) for NAT traversal, and media authorization. The Policy and Charging Rules Function (PCRF) or the Application Function (AF) can also use media identification to apply specific Quality of Service (QoS) and charging policies to individual media flows within a session, enabling sophisticated service differentiation.
Purpose & Motivation
MID was introduced to solve the limitations of managing complex multimedia sessions where multiple, simultaneous media streams are involved. Early multimedia sessions typically described media based on the order of 'm=' lines in SDP, which was fragile—if the order changed during negotiation, it could lead to misassociation of streams and failed sessions. The need for a stable, unique identifier became acute with the advent of advanced IMS services like Video Telephony, Collaborative Workspaces, and Rich Communication Services (RCS), where sessions may dynamically add or remove media components (e.g., adding a file transfer or a second video stream). MID provides an explicit, protocol-level handle for each media component, enabling robust session modification, hold/resume operations, and content adaptation. It allows network elements to precisely identify which media flow a policy rule should apply to, which is essential for implementing advanced charging models (e.g., charging video separately from voice) and guaranteed bitrate QoS. Its creation was driven by the IETF's work on SDP and adopted by 3GPP to ensure interoperability and reliable service control in the all-IP service architecture of IMS.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (15 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-5, normative work from Rel-15.
In Release 15, the MID (Media Identification) function saw enhancements related to identification and registration procedures, including specific updates to EAP-Identification within the EAP-AKA' primary authentication and key agreement framework. The specification defines the MID value, coded on two octets within the reserved CPI range of '1080' to '109F', as the key identifier for the source and type of a message, such as in Secured CBS messages. These messages are analyzed by the UICC using the MID value after being received by the Mobile Equipment.
In Release 16, the new development for the Media Identification (MID) function was the specification of an identification procedure for the RACS (Resource and Admission Control Subsystem). This procedure utilizes the MID value, which is coded on two octets within the Command Packet Identifier (CPI) range, to enable the identification of the source and type of a message for processing.
- Identification procedure for RACS TS 24.501CR1622
In Release 18, the MID (Media Identification) function was enhanced to enable the identification of PRUs (Positioning Reference Units) related to forwarded LCS (Location Services) messages. Additionally, the framework was extended to support the identification of Equivalent SNPNs (Standalone Non-Public Networks). These updates utilized the existing MID parameter, coded on two octets within the reserved CPI (Command Packet Identifier) range, to carry these new identification purposes within secured messaging procedures.
In Release 19, the MID function was enhanced to support (S)RTP multiplexed media information, including its use during UE-requested PDU session modification. The release introduced clarifications and corrections for matching this identification information within QoS rules and packet filters. It also expanded PDU set identification to cover non-3GPP access.
- (S)RTP multiplexed media information support TS 24.501CR6576
- PDU set identification for non-3GPP access TS 24.501CR6577
- Alt-1: Allow multiple multiplexed media packet filter components in one packet filter TS 24.501CR6699
- Rename the term of (S)RTP multiplexed media information TS 24.501CR6704
- Support of (S)RTP multiplexed media information during UE-requested PDU session modification procedure TS 24.501CR6772
- Correction to (S)RTP multiplexed media identification information component TS 24.501CR6804
+ 4 more changes
Explore further
Broader topics and technologies where MID plays a role.
Defining Specifications
3GPP specifications that define or reference MID, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.048 v1400 | Secured Packets for UICC Remote Management | Rel-5 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 29.333 vj00 | MRFC-MRFP Mp Interface Protocol | Rel-19 |
| TS 31.115 vj00 | Secured Packet Structure for UICC Applications | Rel-19 |
| TS 33.812 v920 | M2M Remote Subscription Management Security | Rel-9 |