Description
The Simple WebRTC Application Protocol (SWAP) is a new protocol specified in 3GPP Release 19, defined in TS 26.510 and TS 26.565. It is designed to facilitate the deployment of WebRTC (Web Real-Time Communication) applications over 3GPP networks, particularly in the context of 5G and IMS (IP Multimedia Subsystem). SWAP provides a standardized way for web applications to establish and manage real-time communication sessions, such as voice and video calls, directly from web browsers without the need for plugins or additional software. The protocol leverages the underlying WebRTC APIs and integrates with 3GPP's IMS architecture to ensure interoperability, security, and QoS. SWAP operates at the application layer and defines a set of procedures and message formats for session establishment, modification, and termination. It uses the IMS SIP (Session Initiation Protocol) as the signaling protocol, but abstracts the complexity of SIP for web developers by providing a simpler, JavaScript-friendly API. The protocol also handles media negotiation, including codec selection and transport parameters, using SDP (Session Description Protocol) encapsulated within SIP messages. SWAP is designed to be extensible and secure, supporting authentication and authorization mechanisms defined by 3GPP, such as IMS AKA and OAuth. It enables service providers to offer WebRTC-based services that are fully integrated with their existing IMS infrastructure, allowing for seamless interworking with traditional circuit-switched and VoLTE/VoNR services. The protocol is particularly relevant for 5G networks, where low latency and high reliability are essential for real-time applications. SWAP also supports advanced features like multi-party conferencing, screen sharing, and data channel communication. By standardizing WebRTC application signaling, SWAP aims to reduce fragmentation and promote interoperability among different vendors and service providers. It is expected to play a key role in the evolution of 5G services, enabling new use cases such as immersive communication, cloud gaming, and remote collaboration. The specification TS 26.510 provides the overall architecture and procedures, while TS 26.565 details the protocol specifics, including message formats and state machines. SWAP is part of 3GPP's broader efforts to integrate web technologies into mobile networks, aligning with trends like network slicing and edge computing. Its introduction in Rel-19 reflects the growing importance of web-based real-time communication and the need for standardized enablers in 5G. As networks evolve towards 6G, SWAP is likely to be further enhanced to support new media types and interaction models.
Purpose & Motivation
SWAP was created to address the growing demand for WebRTC-based real-time communication services in mobile networks, particularly in the context of 5G. Prior to SWAP, integrating WebRTC applications with 3GPP networks required complex, non-standardized signaling and media handling, leading to interoperability issues and increased development effort. Service providers wanted to leverage their existing IMS infrastructure while offering web-friendly APIs to developers. SWAP solves this by providing a standardized, lightweight protocol that abstracts the complexity of IMS SIP and WebRTC APIs, enabling rapid development of real-time communication services. It also ensures that these services benefit from 3GPP's QoS, security, and policy frameworks, which are critical for commercial deployments. The protocol was motivated by the need to support new use cases such as browser-based calling, video conferencing, and interactive applications without requiring users to install dedicated apps. By standardizing SWAP, 3GPP aims to foster a vibrant ecosystem of WebRTC applications that can seamlessly interwork with traditional telephony services, thus bridging the gap between web and telecom domains. This is especially important as 5G networks enable ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB), making real-time web communication more viable than ever.
What changed in its specifications
The latest release-to-release comparison of specifications that define SWAP. Each summary describes the whole specification, not only this term.
Rel-19 added a new M10 reference point to SEAL Data Delivery, with small attribute corrections. It also specified signaling for multiplexed media flows via Media AF and PCF, plus a new term.
Full comparison in TS 26.510 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference SWAP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 26.510 vj20 | 5G Media Streaming and Real-Time Communication APIs | Rel-19 read |
| TS 26.565 vj00 | Split Rendering Media Service Enabler | Rel-19 read |