Real-Time Communication Client

Description

The RTC Client is a functional entity residing in the User Equipment (UE) that serves as the bridge between RTC Applications and the 3GPP network. It is composed of two sub-functions: the RTC Access Function and the RTC Media Session Handler. The RTC Access Function is responsible for establishing and managing the transport-level connectivity between the UE and the network's RTC AS, including the WebRTC endpoint that handles media and data channels. The RTC Media Session Handler manages session-level control, such as session establishment, modification, and termination, and coordinates with IMS or other service control functions.

Architecturally, the RTC Client sits between the RTC Application (which it serves) and the network (with which it communicates). The RTC Application invokes the RTC Client's APIs to initiate or join sessions, send and receive media, and handle events. The RTC Client, in turn, interacts with the RTC AS in the network via standardized interfaces, and with IMS core functions when IMS-based service control is used. This layered design abstracts the complexity of WebRTC and 3GPP signaling from the application developer, enabling faster service creation.

The RTC Access Function within the RTC Client hosts a WebRTC endpoint, which implements the WebRTC framework's transport and media capabilities. This endpoint is responsible for ICE (Interactive Connectivity Establishment), DTLS handshakes, SRTP media encryption, and data channel management. It communicates with the corresponding WebRTC endpoint in the network's Media Function (part of the RTC AS) to establish a peer-to-peer or relayed media path. The RTC Media Session Handler, on the other hand, deals with SIP or HTTP-based signaling to set up and control the session, including negotiation of media parameters and QoS requirements.

The RTC Client also plays a key role in QoS and policy interactions. It can request dedicated bearers or QoS flows from the network based on the media characteristics negotiated for the session. This ensures that real-time media receives appropriate treatment in the 5G or LTE network, reducing latency and packet loss. The RTC Media Session Handler may interact with the PCF (Policy Control Function) or PCRF via the network's signaling to establish these QoS resources.

In terms of deployment, the RTC Client is typically implemented as part of the UE's modem or application processor software, or as a library integrated into the RTC Application. 3GPP specifications (TS 26.113, TS 26.506) define the functional requirements and interfaces for the RTC Client, ensuring interoperability across different UE vendors and network operators. The RTC Client is a cornerstone of the Release 19 WebRTC architecture, enabling operators to deliver high-quality, interoperable real-time communication services.

Purpose & Motivation

The RTC Client was introduced to provide a standardized, network-integrated client-side function for WebRTC-based real-time communication. Prior to Release 19, WebRTC clients were typically standalone applications that did not leverage network capabilities such as QoS, policy control, or IMS service integration. This limited the quality and feature set of WebRTC services compared to traditional operator telephony. The RTC Client solves this by defining a UE function that can interact with both the application layer and the network, enabling operators to offer WebRTC services with carrier-grade quality and integration.

A key motivation was the need to separate application logic from communication logic. By defining the RTC Client as a distinct function, 3GPP allows application developers to focus on user experience while the RTC Client handles the complexities of session management, media transport, and network interworking. This separation also enables reuse of the RTC Client across multiple applications, reducing development effort and ensuring consistent behavior.

Furthermore, the RTC Client enables operators to maintain control over real-time communication services. By anchoring session control in the network (via the RTC AS and IMS), operators can apply policy, charging, and regulatory features (e.g., lawful intercept, emergency call handling) to WebRTC sessions. This is essential for meeting regulatory requirements and for integrating WebRTC services into the operator's broader service portfolio. The RTC Client thus represents a convergence of web technologies and telecom-grade service delivery.