Packet Switched Streaming Client

Description

The Packet Switched Streaming (PSS) client is a key component of the 3GPP PSS service, which provides streaming of multimedia content (audio, video, text) over packet-switched networks. The client resides on the user equipment (UE) and is responsible for requesting, receiving, decoding, and rendering streaming media. It operates based on IETF standards such as Real-Time Streaming Protocol (RTSP) for session control and Session Description Protocol (SDP) for media negotiation, as well as HTTP for progressive download and adaptive streaming. 3GPP specifications (e.g., TS 26.234, 26.237, 26.244, 26.245, 26.246) define additional requirements and extensions to these protocols to ensure interoperability, quality of service (QoS), and efficient delivery over mobile networks.

The PSS client architecture includes several functional modules: session management (using RTSP), media decoding (e.g., H.264, AAC), buffering, and adaptation logic. It interacts with the PSS server, which may be located in the operator's network or on the internet. The client initiates a streaming session by sending an RTSP DESCRIBE request to obtain the SDP description of the media. It then sets up the session with RTSP SETUP and starts playback with RTSP PLAY. For HTTP-based streaming, the client uses standard HTTP GET requests to fetch media segments, often following the 3GPP Adaptive HTTP Streaming (AHS) or Dynamic Adaptive Streaming over HTTP (DASH) specifications.

One of the key features of the PSS client is its ability to adapt to changing network conditions. It can switch between different media bitrates based on available bandwidth, buffer status, and other metrics. This adaptation is crucial for maintaining a satisfactory user experience in mobile environments where bandwidth fluctuates. The client may also support features like trick play (fast forward, rewind), metadata handling, and digital rights management (DRM) for content protection.

The PSS client is specified to work over various access technologies, including GPRS, EDGE, UMTS, LTE, and 5G. It is designed to be codec-agnostic, but 3GPP specifies mandatory codecs (e.g., AMR-NB, AMR-WB, H.264) to ensure baseline interoperability. The client also supports QoS negotiation through mechanisms like PDP context activation with appropriate traffic class (streaming or conversational).

In terms of protocols, the PSS client uses RTSP for control and RTP/RTCP for media transport in the RTSP-based mode. For HTTP-based streaming, it uses HTTP/TCP and may employ byte-range requests for seeking. The 3GPP specifications define profiles and levels to categorize client capabilities, ensuring that servers can tailor content appropriately.

Overall, the PSS client is a standardized entity that enables rich media experiences on mobile devices, bridging the gap between internet streaming technologies and the unique constraints of cellular networks. Its evolution from Release 8 onwards reflects the ongoing shift towards HTTP-based adaptive streaming and integration with IMS and 5G media services.

Purpose & Motivation

The PSS client was created to provide a standardized way for mobile devices to access streaming media services over packet-switched networks. Before its introduction, streaming over mobile networks was fragmented, with proprietary solutions that lacked interoperability and often performed poorly due to varying network conditions. 3GPP recognized the need for a common framework that would allow operators, content providers, and device manufacturers to deliver consistent streaming experiences.

The primary motivation was to leverage IETF protocols (RTSP, SDP, HTTP) while adding 3GPP-specific enhancements to address mobile network challenges such as limited bandwidth, high latency, and variable radio conditions. The PSS client enables features like adaptive bitrate streaming, QoS support, and efficient buffering, which are essential for smooth playback. It also facilitates interoperability between different vendors' equipment, reducing deployment costs and accelerating service adoption.

Furthermore, the PSS client supports the evolution of streaming technologies. Starting with RTSP-based streaming in early releases, it later incorporated HTTP-based adaptive streaming (e.g., 3GPP AHS, DASH) to align with internet trends and improve scalability. This flexibility ensures that the PSS client remains relevant across generations, from 3G to 5G, and can be used for a wide range of services, including live TV, video on demand, and interactive applications. The client also plays a role in emergency services and mission-critical communications, where reliable streaming is vital.