Real-Time (media) Communication

Description

Real-Time Communication (RTC) in 3GPP encompasses the end-to-end architecture, protocols, and codecs designed to support interactive, delay-sensitive media sessions over IP-based networks, primarily the IMS (IP Multimedia Subsystem). The core of RTC is the establishment and management of media flows using the Session Initiation Protocol (SIP) for signaling and the Real-time Transport Protocol (RTP) for actual media transport. The IMS core provides the control plane functions—including registration, session routing, and policy interaction—while the User Equipment (UE) and media gateways handle the media plane. Key architectural components include the Proxy-Call Session Control Function (P-CSCF) for the UE's first contact point, the Serving-CSCF (S-CSCF) for session control, and the Media Resource Function (MRF) for conferencing and tone generation. Quality of Service (QoS) is integral, with the Policy and Charging Rules Function (PCRF) ensuring dedicated bearers are established for RTC media flows to guarantee low latency and packet loss, a process defined in the Rx and Gx interfaces. The media negotiation uses the Session Description Protocol (SDP) within SIP messages to agree on codecs (like AMR-WB for voice or H.264 for video), port numbers, and IP addresses. Furthermore, RTC services incorporate mechanisms for emergency calls (eMPS), lawful interception, and transcoding when needed. The evolution towards WebRTC integration in later releases expanded RTC to browser-based applications, requiring new functional elements like the WebRTC Interworking Function (WIF) to bridge the WebRTC signaling and media protocols with native IMS procedures.

Purpose & Motivation

RTC was standardized to transition traditional circuit-switched telephony (like GSM voice) to a unified, all-IP network architecture, enabling richer multimedia services. Prior to RTC over IMS, voice and video services were siloed, with circuit-switched voice lacking integration with data applications and internet protocols. The motivation was to leverage IP networks for operational efficiency, service innovation, and network convergence. By defining RTC within the IMS framework, 3GPP solved the problem of providing carrier-grade voice and video with guaranteed quality, security, and interoperability across different operators and device types. It addressed the limitations of best-effort internet VoIP, which lacked standardized QoS, emergency calling support, and seamless mobility. The creation of RTC standards enabled the commercial deployment of Voice over LTE (VoLTE) and Voice over NR (VoNR), which are essential for retiring legacy circuit-switched cores and utilizing spectrum more efficiently in 4G and 5G networks.

Key Features

• End-to-end IP-based media transport using RTP/RTCP
• Call control and signaling via SIP within the IMS core
• Integrated QoS mechanisms using dedicated EPS bearers
• Support for high-definition voice (e.g., EVS codec) and video codecs
• Interworking with legacy circuit-switched networks via MGCF/IM-MGW
• Support for emergency services (eMPS) and lawful interception

Evolution Across Releases

Defining Specifications