Description
Optimal Media Routeing (OMR) is a network-based optimization mechanism defined across several 3GPP specifications (e.g., TS 23.894, TS 24.229) that determines the most efficient path for media traffic (e.g., RTP streams for voice and video) in an IP-based communication session. Its primary goal is to avoid unnecessary traversal of core network elements, particularly the media gateways and session border controllers, by enabling a more direct media path between the two communicating endpoints when possible and permissible by policy. This is often referred to as achieving "local switching" or a "direct media path."
Architecturally, OMR involves several key network functions within the IMS and packet core. The main decision point typically resides in the Proxy-Call Session Control Function (P-CSCF) or the Service Centralization and Continuity Application Server (SCC AS), which analyze the session establishment signaling (SIP/SDP). These functions examine parameters like the IP addresses and port numbers offered by the endpoints in the SDP offer/answer exchange. Based on network topology knowledge, operator policies, and potentially input from the Policy and Charging Rules Function (PCRF), they determine if a direct media path is optimal and allowed. If so, the signaling path may be modified to instruct the endpoints to send media packets directly to each other's IP addresses, bypassing intermediary media processing nodes.
How it works involves a coordinated process during session setup. When a call is initiated, the originating UE sends a SIP INVITE with an SDP offer containing its media capabilities and proposed IP address/port for receiving media. This signaling traverses the IMS core (P-CSCF, S-CSCF, etc.). The OMR-enabled function analyzes this information. Upon receiving the SDP answer from the terminating side, it compares the two IP addresses. If they are determined to be on the same or closely connected IP subnet (e.g., within the same operator's network, or both behind the same NAT), and policy allows, the network may decide to enable a direct media path. The network functions may then potentially modify the SDP bodies in the signaling messages to reflect the optimal route or simply allow the endpoints to use the addresses they have already exchanged. The media (RTP/RTCP) then flows directly between the UEs, while the control signaling (SIP) continues to traverse the IMS core for session control and service logic.
Purpose & Motivation
OMR was developed to address significant inefficiencies in early VoIP and IMS deployments where media traffic was often "tromboned" through central media gateways or session border controllers, even when the two communicating parties were geographically close or within the same network. This tromboning increased latency, jitter, and packet loss, degrading the quality of experience for real-time services like voice and video calls. It also consumed unnecessary bandwidth on transport links and added load to expensive media processing resources, increasing both capital and operational expenditures for operators.
The motivation for OMR stemmed from the commercial deployment of services like Voice over LTE (VoLTE), where high-quality voice is a key requirement. The traditional model of anchoring all media at a central point (like a Media Gateway Control Function - MGCF or a Media Resource Function - MRF) was suboptimal for many call scenarios, especially mobile-to-mobile calls within the same network. OMR solves this by enabling intelligence in the session control layer to analyze the endpoints' locations and dynamically select a media path that minimizes hops and network resource usage. This directly improves call setup times, reduces end-to-end delay, and enhances voice/video quality. It also allows operators to scale their networks more efficiently by offloading media traffic from core nodes onto the more distributed IP transport network.
What changed in its specifications
The latest release-to-release comparison of specifications that define OMR. Each summary describes the whole specification, not only this term.
Rel-19 adds Rich Call Data support to TS 24.229, including the DC-Info header, rcd-np Call-Info parameter, and RCD info retrieval and verification across originating, terminating, IBCF and AS behaviour. It also adds MPS for Messaging, eCall alignment with EN 17184:2024 (test eCall and updated-MSD transfer), and satellite identifiers in P-Access-Network-Info.
Full comparison in TS 24.229 →Rel-12 added an iotl SIP URI parameter (RFC 7549) to Route, Request-URI, and Feature-Caps entries in message flows for NNI Routeing scenario indication.
Full comparison in TS 29.079 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Introduced the foundational concepts for Optimal Media Routeing within the IMS framework, primarily focusing on enabling direct media transfer between User Equipments (UEs) served by the same Access Gateway when policy allowed. Initial specifications defined the basic procedures and architectural impacts on IMS entities like the P-CSCF.
Enhanced OMR for IMS Centralized Services (ICS) and Service Centralization and Continuity (SCC), allowing for optimized media routing in scenarios involving circuit-switched access legs. Improved support for scenarios where one party is on CS voice and the other on IMS.
Extended OMR optimizations for Voice over LTE (VoLTE) deployments, refining procedures for when both parties are on LTE/EPC. Introduced more detailed interaction with the Policy and Charging Control (PCC) architecture to enforce operator policies on media routing.
Further refinements for SRVCC (Single Radio Voice Call Continuity) and eSRVCC scenarios, ensuring media path optimization could be maintained or efficiently re-established during handovers between LTE and 2G/3G networks.
Adapted OMR principles for the 5G System and Voice over New Radio (VoNR), integrating with the 5G Core's session management and policy framework. Supported optimized media routing for sessions using the new 5G media components.
Extended OMR for Ultra-Reliable Low Latency Communication (URLLC) services and industrial IoT, where deterministic and minimal-latency media paths are paramount. Enhanced support for edge computing scenarios where media processing is performed at the network edge.
Enhanced OMR for extended reality (XR) services and real-time interactive media, which have stringent bandwidth and latency requirements. Incorporated AI/ML-based analytics for predictive and dynamic media path optimization.
Defining Specifications
3GPP specifications that define or reference OMR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.894 va00 | IMS Local Breakout & Optimal Media Routing Study | Rel-10 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.802 vc10 | IMS II-NNI Traversal Scenario Determination Study | Rel-12 read |
| TS 29.079 vj00 | Optimal Media Routeing (OMR) Procedures | Rel-19 read |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 read |
| TS 29.165 vk00 | Inter-IMS Network-to-Network Interface (II-NNI) | Rel-20 read |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.260 vk10 | IMS Charging Management | Rel-20 read |