Description
The PSS server is a core component of the 3GPP Packet-switched Streaming Service (PSS), which was introduced in Release 8 to provide streaming of multimedia content over packet-switched networks. It acts as the origin and delivery point for streaming sessions, supporting both progressive download and adaptive streaming. The server implements the IETF Real-Time Streaming Protocol (RTSP) for session control and the Session Description Protocol (SDP) for media negotiation, as well as HTTP-based streaming for compatibility with web technologies. In addition to these IETF standards, the PSS server incorporates 3GPP-specific requirements defined in specifications such as 26.234, 26.237, 26.244, 26.245, and 26.246, which cover aspects like codec support, quality of service, and interoperability with mobile networks.
Architecturally, the PSS server resides in the packet-switched domain and communicates with the PSS client on the user equipment (UE) over the IP network. The server manages media streams, handles session setup, control, and teardown, and adapts to network conditions through mechanisms like rate adaptation and buffering. It supports a variety of media types, including audio, video, and timed text, and can deliver content using unicast or multicast. The server also interacts with other network elements such as the PSS proxy, content delivery networks (CDNs), and the IP Multimedia Subsystem (IMS) for service integration.
Key components of the PSS server include the media repository, which stores or fetches content; the session manager, which handles RTSP and HTTP sessions; the media delivery engine, which packetizes and transmits media; and the adaptation logic, which adjusts streaming parameters based on feedback from the client or network. The server may also include a cache to improve performance and reduce latency. The PSS server supports both live streaming and on-demand streaming, and it can be integrated with Digital Rights Management (DRM) systems for content protection.
The PSS server plays a crucial role in enabling mobile streaming services, allowing operators to deliver rich multimedia experiences to subscribers. It ensures interoperability across different devices and networks by adhering to 3GPP specifications, which define profiles and test cases for compliance. Over successive releases, the PSS server has evolved to support higher resolutions, new codecs (e.g., HEVC), and adaptive streaming techniques like DASH (Dynamic Adaptive Streaming over HTTP), which is now a key part of 3GPP streaming services.
In summary, the PSS server is a standardized streaming server that combines IETF protocols with 3GPP enhancements to provide reliable, high-quality streaming over mobile networks. Its design addresses the unique challenges of wireless environments, such as variable bandwidth and latency, through adaptive mechanisms and robust error resilience.
Purpose & Motivation
The PSS server was created to standardize streaming services over 3GPP packet-switched networks, addressing the fragmentation of early mobile streaming solutions. Before its introduction, streaming implementations were proprietary and lacked interoperability, leading to inconsistent user experiences and limited service adoption. The PSS server provides a common set of protocols and requirements that ensure content can be delivered seamlessly across different devices, networks, and operators.
By leveraging IETF standards like RTSP and HTTP, the PSS server enables reuse of existing internet streaming infrastructure while adding 3GPP-specific features to handle mobile network constraints. This approach reduces development costs and accelerates time-to-market for streaming services. The server also supports quality of service (QoS) differentiation, allowing operators to offer tiered streaming services with guaranteed performance.
Over time, the PSS server has evolved to embrace HTTP-based adaptive streaming (e.g., DASH), which has become dominant due to its scalability and compatibility with web technologies. This evolution reflects the ongoing need to balance standardization with flexibility, ensuring that 3GPP streaming remains competitive with over-the-top (OTT) services while maintaining the reliability and efficiency of mobile networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define PSS server. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 26.234: 1 clause changed, with no change attributed to a release feature.
Full comparison in TS 26.234 →Added a suggested presentation offset for synchronized playout and updated the nBookmark XML schema to version 2.
Full comparison in TS 26.237 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced the PSS server as a server for the 3GPP packet-switched streaming service based on IETF RTSP/SDP and/or HTTP standards, with possible additional 3GPP requirements. This release established the foundational architecture and protocol support for mobile streaming.
Defining Specifications
3GPP specifications that define or reference PSS server, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 26.234 vj00 | 3GPP PSS Protocols and Codecs Specification | Rel-19 read |
| TS 26.237 vj00 | IMS for PSS and MBMS Control | Rel-19 read |
| TS 26.244 vj10 | 3GPP File Format (3GP) Specification | Rel-19 read |
| TS 26.245 vj00 | 3GPP Timed Text Format Specification | Rel-19 read |
| TS 26.246 vj00 | 3GPP SMIL Language Profile Specification | Rel-19 read |