Description
The Multiple Stream Registration Protocol (MSRP) is an application-level protocol defined within the 3GPP IMS framework, standardized in cooperation with the IETF (RFC 4975, RFC 4976). It is designed for the transmission of a series of related instant messages or media chunks, such as files or real-time text, within an established IMS session. MSRP operates over reliable transport protocols like TCP or TLS, using SIP (Session Initiation Protocol) for session establishment and negotiation, but then switches to MSRP for the actual bulk data transfer.
MSRP works by establishing one or more MSRP sessions between endpoints. These sessions are logical channels for sending discrete messages or large content broken into chunks. A key mechanism is the use of MSRP URIs (Uniform Resource Identifiers) to identify endpoints and sessions. During the SIP/SDP (Session Description Protocol) offer/answer exchange, endpoints negotiate MSRP parameters such as the path, port, and acceptance of chunked transmission. Once the SIP session is established, the endpoints open a direct TCP (or TLS) connection for MSRP traffic, independent of the SIP signaling path.
Within an MSRP session, content is sent in SDP-carried MSRP messages. A sender can break a large piece of content (like a file) into multiple chunks, each sent in a separate SEND request. The receiver acknowledges each chunk with a 200 OK response, providing flow control and reliability. MSRP also supports report delivery notifications for successful reception. The protocol includes mechanisms for session keep-alive, error reporting, and graceful session termination. Its design allows it to traverse Network Address Translators (NATs) and firewalls when used in conjunction with techniques like Interactive Connectivity Establishment (ICE).
Purpose & Motivation
MSRP was created to address the limitations of using SIP message bodies for transmitting large amounts of content or a continuous stream of related instant messages. SIP, while excellent for session signaling, is not optimized for bulk data transfer. Embedding large files in SIP MESSAGE requests could lead to performance issues, fragmentation, and difficulties with intermediate proxies. MSRP provides a separate, more efficient channel for this content, allowing SIP to focus on session control.
It solves the problem of managing multiple media streams or discrete content items within a single multimedia session. Before MSRP, applications like file transfer within a chat session or multi-stream video conferencing required ad-hoc solutions or separate out-of-band mechanisms. MSRP standardizes this process, enabling interoperable, reliable, and negotiable content delivery. Its creation was motivated by the growth of rich communication services (RCS) and IMS-based multimedia applications requiring more than just simple voice or single-image exchange.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-6, normative work from Rel-16.
In Release 16, the MSRP function was updated to incorporate a new IETF draft specification for its usage over a data channel. This was introduced via a reference update to **draft-ietf-mmusic-msrp-usage-data-channel**, which defines the protocol's application within that transport context.
In Release 17, the MSRP function was enhanced with security updates for its algorithms and protocols as specified for 33.328. These updates were implemented to ensure the secure handling of multiple synchronization domains and their associated time protocol messages, such as IEEE 1588v2 and gPTP, across the 5G system. This strengthens the protocol's role in supporting industrial applications requiring precise clock synchronization and functional safety.
- Security updates for algorithms and protocols for 33.328 TS 33.328CR0068
In Release 18, the MSRP function was enhanced to support the IETF draft for multiple registration reasons and introduced mechanisms for distinguishing bootstrap data channels with identical stream IDs. It also included new IANA registrations for data channel sub-protocols and the SDP attribute `a=bdc-used-by`. Furthermore, support was added for registering RTCP feedback for viewport-related information within the ITT4RT framework.
- Support of IETF draft-ietf-sipcore-multiple-reasons TS 29.165CR1035
- LI of 5G Media Streaming (5GMS) (Control plane) TS 33.127CR0186
- Protocol Stack for MTSI UE TS 26.114CR0529
- IANA registration for data channel sub-protocols TS 26.114CR0537
- Mechanism to distinguish two bootstrap data channels with the same stream ID value (Rel-18) TS 26.114CR0560
- IANA registration information for a=bdc-used-by TS 26.114CR0565
+ 2 more changes
In Release 19, the MSRP function was enhanced with new support for data channel multiplexing and IMS DC multiplexing. These additions allow MSRP to handle multiple synchronization domains and their associated message flows more efficiently within the 5G system. This specifically enables the management of multiple working clock domains, such as for global time and redundant synchronization domains, through a common infrastructure.
Explore further
Broader topics and technologies where MSRP plays a role.
Defining Specifications
3GPP specifications that define or reference MSRP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.832 vh40 | Study on cyber-physical control in vertical domains | Rel-17 |
| TS 23.279 vj00 | Combined CS and IMS Services (CSI) Architecture | Rel-19 |
| TS 23.333 vj00 | MRFC-MRFP Mp Interface Requirements | Rel-19 |
| TS 23.334 vj00 | IMS-ALG to IMS-AGW Interface (Iq) Stage 2 | Rel-19 |
| TS 23.701 vc00 | WebRTC Access to IMS Architecture Study | Rel-12 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 24.247 vj10 | IMS Messaging Service Protocol Details | Rel-19 |
| TS 26.114 vj10 | IMS Multimedia Telephony Media Handling | Rel-19 |
| TR 26.980 vj00 | Multi-stream Multiparty Conferencing Media Handling | Rel-19 |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 |
| TS 29.165 vj10 | Inter-IMS Network to Network Interface (NNI) | Rel-19 |
| TS 29.238 vj00 | H.248 Profile for IBCF-TrGW Interface | Rel-19 |
| TS 29.311 vj00 | Service Level Interworking for Messaging | Rel-19 |
| TS 29.333 vj00 | MRFC-MRFP Mp Interface Protocol | Rel-19 |
| TS 29.334 vj00 | IMS-ALG to IMS-AGW Interface Protocol | Rel-19 |
| TS 29.828 vc10 | IMS Media Plane Security H.248 Profiles Study | Rel-12 |
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.180 vk00 | Security of Mission Critical (MC) Service | Rel-20 |
| TS 33.328 vj10 | IMS Media Plane Security Specification | Rel-19 |