Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

SSRC

Synchronization Source Identifier

Protocol →

SSRC is a unique identifier for the source of a media stream within an RTP session, distinguishing concurrent sources for proper synchronization and playback in IMS and VoLTE/VoNR.

Introduced
Rel-8
Where
Services › IMS
Specifications
17 specs
Also in
Core Network
SSRC Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Synchronization Source Identifier (SSRC) is a 32-bit numeric identifier defined within the Real-time Transport Protocol (RTP), which is used for delivering audio and video over IP networks. In an RTP session, each participant that generates a stream of RTP packets (e.g., a microphone, a camera, or a media mixer) is assigned a unique SSRC. This identifier is carried in the header of every RTP packet, allowing receivers to associate incoming packets with their specific source. The primary role of the SSRC is to provide a source-level distinction for synchronization and demultiplexing. The RTP Control Protocol (RTCP) uses the SSRC to associate control packets (containing reports on quality, participant membership, and source description) with the corresponding media source, enabling functionalities like participant identification and network monitoring.

Architecturally, the SSRC is a key component in the media plane of IP Multimedia Subsystem (IMS)-based services like Voice over LTE (VoLTE) and Voice over NR (VoNR). When a call is established, Session Description Protocol (SDP) negotiation during the SIP signaling phase agrees on media formats and ports, but the SSRCs are dynamically chosen by each media sender when the RTP stream begins. The mechanism for ensuring uniqueness is probabilistic; each source randomly picks a 32-bit number, with a very low chance of collision within a session. If a collision is detected (two sources pick the same SSRC), a conflict resolution procedure defined in RFC 3550 is invoked, where one source may change its SSRC. Related specifications like 3GPP TS 24.229 (IMS) and TS 26.114 (IMS Media) govern its usage in the 3GPP context.

How it works is integral to multi-party scenarios. In a conference call, each participant's device acts as a synchronization source with its own SSRC. A Media Resource Function (MRF) or conference bridge, which mixes the audio streams, may also become a synchronization source itself, generating a new composite stream with a new SSRC. Receivers use the SSRC to correctly render audio from different talkers, apply individual volume controls, or compute separate jitter and packet loss statistics per source via RTCP Receiver Reports. This per-source identification is crucial for quality of experience (QoE) monitoring and for advanced services like active speaker indication. The SSRC is also used in security contexts; for example, in Secure RTP (SRTP), cryptographic contexts are often bound to SSRC values to provide source authentication and confidentiality.

Purpose & Motivation

The SSRC exists to solve the fundamental problem of identifying and managing multiple concurrent media sources within a single RTP session. Before RTP's standardization, multimedia sessions over IP lacked a standardized way to distinguish between different contributors in a session, making features like audio conferencing, video switching, and independent stream quality assessment difficult to implement in an interoperable manner. The creation of the SSRC as part of RTP (standardized in IETF RFC 1889, later RFC 3550) provided a lightweight, in-band mechanism for source identification without requiring constant out-of-band signaling.

In the 3GPP ecosystem, the adoption of RTP/RTCP and thus the SSRC was motivated by the move to all-IP networks for voice and multimedia services with IMS. For circuit-switched voice, identifying speakers was handled by different, less flexible mechanisms. For packet-switched VoLTE and VoNR, the SSRC enables the network to deliver rich communication services (RCS), multi-party calls, and video telephony with standard Internet protocols. It addresses the limitation of simply using IP addresses and ports for stream identification, which is insufficient when a single host (like a conference server) generates multiple logical streams or when network address translation (NAT) is involved.

Historically, as 3GPP defined IMS in Rel-5 and later integrated it for LTE and 5G voice, the SSRC became a cornerstone for media handling. Its purpose extends to enabling detailed media analytics and lawful interception, as specified in 3GPP TS 33.179 and 33.180, where correlating media streams to specific parties is essential. The SSRC solves the problem of scalable, dynamic source management in real-time group communications, which is a critical requirement for modern telecom services beyond simple point-to-point calls.

What changed in its specifications

The latest release-to-release comparison of specifications that define SSRC. Each summary describes the whole specification, not only this term.

TS 24.281Rel-17 → Rel-18

Added MBS session management and XML schema types. Added MCVideo emergency and imminent peril adhoc group call procedures. Added MCVideo gateway UE function for non-3GPP access. Added 5G ProSe support to MCVideo. Added migration service authorization for MCVideo clients.

Full comparison in TS 24.281 →
TS 24.379Rel-18 → Rel-19

Rel-19 adds participant-criteria handling for ad hoc group emergency alerts, a Reason header with cause 200 on session-leaving messages, and SIP 302 rejection for migrated MCPTT IDs. It also adds location-information conditions for INVITE and REFER requests, removes implicit floor grants from such requests, and changes prearranged group call and emergency alert authorisation rules.

Full comparison in TS 24.379 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
  • Correction on MCVideo Group Identity and SSRC field TS 24.581CR0041
Rel-16 3 changes
  • SSRC handling for implicit floor request case TS 24.379CR0613
  • SSRC handling for implicit floor request case TS 24.380CR0242
  • Adding SSRC of Transmitter in reception control messages TS 24.581CR0046
Rel-18 5 changes
  • MCPTT support of multiplexing - SSRC used in RTCP signalling over 5MBS TS 24.380CR0363
  • MCVideo support of multiplexing - SSRC used in RTCP signalling over 5MBS TS 24.581CR0122
  • RTP SSRC of audio and video media streams usage during call setup using implicit transmission request - sig plane TS 24.281CR0206
  • Clarification of the SSRC to be used in video, audio and transmission control (TC) streams in MCVideo TS 24.581CR0092
  • RTP SSRC of audio and video media streams usage in during call setup using implicit transmission request - med plane TS 24.581CR0110
Rel-19 3 changes
  • Correction of SSRC for Multitalker floor participant TS 24.380CR0375
  • SSRC in implicit floor request in non-controlling function TS 24.379CR1058
  • Correction of transmitting user's video SSRC field ID in transmission control messages R19 TS 24.581CR0149

Defining Specifications

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

SpecificationTitleRelease
TS 24.281 vk10 MCVideo Signalling Control Rel-20 read
TS 24.379 vk10 MCPTT Call Control Protocol Rel-20 read
TS 24.380 vk10 MCPTT Media Plane Control Protocols Rel-20 read
TS 24.581 vj30 MCVideo Media Plane Control Rel-19 read
TS 25.414 vj00 UTRAN Iu Interface User Plane Transport Protocols Rel-19 read
TS 26.223 vj00 IMS Telepresence Client Specification Rel-19 read
TS 29.333 vj00 MRFC-MRFP Mp Interface Protocol Rel-19 read
TS 29.380 vj00 MCPTT-LMR Interworking Media Plane Control Rel-19 read
TS 29.414 vj00 Nb Interface Bearer Transport & Control Protocols Rel-19 read
TS 29.582 vj00 MCData Interworking with LMR Systems Rel-19 read
TS 33.179 vdc0 MCPTT Security Architecture and Procedures Rel-13 read
TS 33.180 vk10 Security of the Mission Critical Service (MCX) Rel-20 read
TS 33.879 vd10 MCPTT Security Study Rel-13 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read
TS 36.579 3GPP TR 36.579 Rel-8 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read
TS 48.103 vj00 A Interface User Plane Transport Protocols Rel-19 read