WebRTC IMS Client

Description

The WebRTC IMS Client (WIC) is a software component, typically implemented as a JavaScript library or a native application module, that resides on a user device such as a smartphone, tablet, or personal computer. Its primary function is to act as a protocol translator and session manager between the WebRTC stack and the IP Multimedia Subsystem (IMS) core network. Architecturally, the WIC implements the IMS client functions—including SIP registration, session establishment, and media negotiation—but does so using WebRTC APIs (like RTCPeerConnection and RTCDataChannel) for media handling and web transport protocols (WebSockets or HTTPS) for signaling, instead of traditional IMS UE protocols. It interfaces with a network-based element called the WebRTC-IMS Gateway, which performs the necessary protocol interworking between the WebRTC signaling and the IMS-specific SIP/IMS procedures.

The WIC works by first establishing a secure connection to the WebRTC-IMS Gateway, often using a web transport like WebSocket over TLS. For registration, the WIC sends SIP-like messages over this connection to the gateway, which translates them into standard IMS SIP REGISTER requests towards the IMS Core (CSCF). Once registered, for a call or messaging session, the WIC uses the WebRTC API to gather local ICE candidates for media paths and creates an SDP offer. This SDP is sent to the gateway, which maps it to a SIP INVITE with appropriate IMS SDP, routes it through the IMS network, and returns the remote answer. The WIC then instructs the WebRTC stack to establish the peer-to-peer or gateway-mediated media flow. Key components within the WIC logic include the SIP/HTTP stack for signaling, the WebRTC API handler for media control, and modules for authentication, security (DTLS-SRTP), and service logic for features like presence or file transfer.

Its role in the network is to democratize access to carrier services. It allows any WebRTC-capable browser or app to become a first-class citizen in the IMS domain, enabling telecom operators to extend VoLTE, ViLTE, RCS, and other IMS-based services to a vast ecosystem of web applications and devices that lack native IMS stacks. This bridges the gap between Over-the-Top (OTT) web communication and standardized, interoperable telecom services, facilitating convergence. The WIC handles the complexities of IMS procedures, network authentication (like IMS-AKA via the gateway), QoS marking, and emergency service identification, presenting a simplified WebRTC API interface to the web application developer.

Purpose & Motivation

The WIC was created to solve the problem of siloed communication ecosystems. Historically, IMS services were accessible only to devices with proprietary, integrated IMS client software, typically provided by the device manufacturer or operator. This limited the reach of high-quality, billable telecom services (like HD voice or video calling) to a subset of smartphones. Meanwhile, the web evolved with WebRTC, providing a standard API for real-time communication in browsers, but these sessions were often confined to isolated web domains or OTT applications without interoperability or carrier-grade features like number-based dialing, roaming, or integration with the PSTN.

The motivation for WIC, introduced in 3GPP Release 12, was to leverage the massive installed base of web browsers and the developer-friendly WebRTC environment to expand the reach of IMS. It addresses the limitation of the previous approach where IMS was a closed network for certified UEs. By defining a standardized client and gateway architecture, 3GPP enabled operators to offer their communication services as a platform to web developers. This solves business problems by creating new service delivery channels and technical problems by providing a standardized, secure method for web clients to access IMS authentication, routing, and policy control. It allows operators to compete with OTT web communication apps using their own branded services, network quality, and existing subscriber identity.

Key Features

• Protocol interworking between WebRTC JavaScript APIs/SDP and IMS SIP/SDP
• Secure access to IMS using web transports (WebSocket/TLS) and gateway-mediated authentication
• Support for IMS multimedia services: voice, video, real-time text, and file transfer
• Integration with IMS core for registration, routing, and service triggering
• End-to-end media security using DTLS-SRTP, negotiated via the gateway
• Capability exchange and media negotiation compliant with both WebRTC and IMS profiles

Evolution Across Releases

Defining Specifications