Description
IMS Media Coding (IMC) encompasses the set of media coding standards, codecs, and processing functions defined within the 3GPP IP Multimedia Subsystem (IMS) framework. IMS is the core network architecture for delivering IP-based multimedia services over mobile and fixed networks, and IMC ensures that the media components (audio, video, text) of these services are encoded, transmitted, and decoded consistently across different endpoints and networks. Specifications such as TS 23.228 (IMS stage 2) and TS 24.229 (IMS call control) reference media coding requirements, while TS 26 series (codec specifications) detail specific codecs like AMR, EVS, or H.264/AVC. IMC involves not only the codecs themselves but also procedures for codec negotiation, media adaptation, and transcoding when necessary.
In an IMS session establishment, such as a VoIP call or video conference, the Session Initiation Protocol (SIP) is used for signaling. During the SIP exchange, endpoints negotiate media parameters using Session Description Protocol (SDP) offers and answers. This negotiation includes selecting compatible codecs from the IMC set, determining bitrates, frame rates, and other media attributes. The IMS core, including elements like the Media Resource Function (MRF), may assist in media processing. The MRF can provide transcoding services if endpoints support different codecs, ensuring interoperability. For example, a device using Enhanced Voice Services (EVS) codec might communicate with a legacy device using Adaptive Multi-Rate (AMR) via transcoding in the MRF.
IMC covers a range of codecs optimized for different conditions. For speech, there are narrowband (AMR-NB), wideband (AMR-WB), and super-wideband/fullband (EVS) codecs, each offering varying quality and bandwidth efficiency. For video, codecs like H.264, H.265, and VP8 are supported. The choice of codec affects network bandwidth usage, battery consumption on devices, and user experience. IMC standards also define performance metrics, mandatory and optional codec support for devices and networks, and procedures for dynamic switching between codecs during a session (e.g., to adapt to changing network conditions). Security aspects, such as encrypted media streams, are also considered within the IMC context. Overall, IMC provides the technical foundation for high-quality, interoperable multimedia communication in IMS, enabling services like VoLTE, ViLTE, and rich communication services (RCS).
Purpose & Motivation
IMS Media Coding was developed to address the challenge of inconsistent media handling in early IP multimedia services. Without standardized codecs and negotiation procedures, endpoints might use incompatible media formats, leading to failed sessions or poor quality. The proliferation of diverse codecs across devices and networks necessitated a framework within IMS to ensure seamless multimedia communication. IMC provides this framework, defining a set of preferred codecs and procedures for media negotiation and adaptation.
The primary problems IMC solves are interoperability and quality assurance. By specifying a common set of codecs (like AMR for voice and H.264 for video) that IMS networks and devices should support, it reduces the likelihood of incompatibility. Furthermore, it introduces mechanisms like transcoding via MRF to bridge different codec capabilities, ensuring that sessions can still proceed even if endpoints support different codecs. This is especially important in mobile networks where devices range from advanced smartphones to basic feature phones. IMC also addresses bandwidth efficiency by including codecs that adapt bitrate to network conditions, optimizing resource usage while maintaining acceptable quality. Introduced in Release 5 alongside the IMS itself, IMC has evolved to include newer, more efficient codecs (e.g., EVS, H.265) to keep pace with advancing technology and user expectations for higher quality media.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the IMS Credentials (IMC) function was specifically extended to support terminals accessing the IMS via a Standalone Non-Public Network (SNPN). This involved correcting and clarifying the IMC definition to explicitly include this new access scenario. The update ensures IMC is applicable for SNPN access, as defined for terminals that do not use a traditional ISIM or USIM.
Explore further
Broader topics and technologies where IMC plays a role.
Defining Specifications
3GPP specifications that define or reference IMC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 22.944 vj00 | UE Functionality Split Scenarios and Requirements | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 33.203 vj10 | IMS Security Specification | Rel-19 |