Description
High Definition (HD) within the 3GPP context is not a single technology but a comprehensive set of service requirements and performance metrics defined to guarantee superior media quality. It is primarily governed by QoS Class Identifiers (QCIs) and specific bearer characteristics that prioritize HD traffic. The architecture supporting HD involves multiple network domains: the Radio Access Network (RAN) must provide sufficient throughput and low packet loss; the core network must ensure low latency and jitter through traffic prioritization; and the User Equipment (UE) must have the capability to decode and render high-definition content.
The technical implementation relies on the EPS bearer model in LTE and the QoS Flow model in 5G System (5GS). For HD video, a dedicated Guaranteed Bit Rate (GBR) bearer or QoS Flow is typically established. This bearer is associated with specific QoS parameters such as a high priority level, a guaranteed and maximum bit rate, and stringent packet delay budget and packet error loss rate. The Policy and Charging Control (PCC) architecture plays a central role, where the Policy Control Function (PCF) authorizes these QoS parameters based on subscription data and service requests from the Application Function (AF).
Key components involved in delivering HD services include the UE's modem and application processor, the base station (eNB/gNB) which schedules radio resources, the core network functions (MME/AMF, SGW/UPF, PCF) that manage the bearer/flow, and the content delivery network. The process begins with a service request, triggering PCC interactions to set up a dedicated bearer with HD QoS profile. The RAN then admits this bearer based on resource availability and uses QoS-aware scheduling algorithms to meet the bit rate and latency targets. Continuous monitoring and reporting ensure the QoS is maintained, with potential adjustments or session termination if the network cannot sustain the required performance.
Purpose & Motivation
The purpose of standardizing High Definition requirements in 3GPP was to transition mobile networks from being primarily voice and basic data conduits to platforms capable of delivering rich, broadcast-quality media. Prior to explicit HD definitions, video services over mobile networks were often low-resolution, buffering-prone, and offered a poor user experience inconsistent across operators and devices. The proliferation of smartphones with high-resolution screens and consumer demand for TV-like video quality on the go created a market imperative.
Technically, earlier releases lacked the granular QoS controls and end-to-service awareness needed to reliably deliver high-bitrate, low-latency streams. The introduction of HD service requirements, beginning in Release 12, provided a standardized benchmark. This allowed operators to design, deploy, and monetize tiered service plans (e.g., standard vs. HD video passes), equipment vendors to build and certify devices and network elements against a common performance target, and application providers to ensure consistent service quality. It also drove underlying network advancements in radio efficiency, core network capacity, and traffic management by establishing clear performance goals that existing 'best-effort' data services could not meet.
What changed in its specifications
The latest release-to-release comparison of specifications that define HD. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 22.278: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 22.278 →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 formalization of High Definition service requirements within 3GPP. This release introduced explicit references to HD in service requirement specifications (e.g., 22.278 for service aspects), defining the need for enhanced QoS to support high-quality video streaming and communication services. It established the foundational architectural hooks in the Evolved Packet System (EPS) to support dedicated bearers for HD media.
Defining Specifications
3GPP specifications that define or reference HD, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.278 vj00 | Evolved Packet System Service Requirements | Rel-19 read |
| TS 22.803 vc20 | Proximity Services (ProSe) Study | Rel-12 read |
| TR 22.804 vg30 | 5G Automation in Vertical Domains Study | Rel-16 read |
| TR 22.816 ve10 | 3GPP TV Service Enhancement Technical Report | Rel-14 read |
| TS 22.870 vk00 | Study on 6G Use Cases and Service Requirements | Rel-20 read |
| TR 23.764 vh10 | Study on V2X Application Layer Enhancements | Rel-17 read |
| TS 26.116 vj00 | TV Video Formats for 3GPP Services | Rel-19 read |
| TS 26.511 vj00 | 5G Media Streaming Profiles, Codecs & Formats | Rel-19 read |
| TR 26.923 vj00 | Study on IMS-based Telepresence Media Handling | Rel-19 read |
| TR 26.925 vj00 | Media Traffic Characteristics for 3GPP Networks | Rel-19 read |
| TR 26.938 vj00 | DASH Deployment Guidelines for 3GPP Networks | Rel-19 read |
| TS 26.942 vk00 | Sustainable Media Metrics and Architectural Impacts for 5G | Rel-20 read |
| TR 26.949 vj00 | TV Service Profiles for 3GPP Networks | Rel-19 read |
| TR 26.952 vj00 | EVS Codec Selection, Verification & Characterization | Rel-19 read |
| TS 36.101 vk10 | E-UTRA UE RF Requirements | Rel-20 read |
| TS 38.101 vj40 | UE Radio Transmission and Reception; Satellite Access | Rel-19 read |
| TS 38.521 vj10 | UE Conformance Spec for NR Satellite Access | Rel-19 read |
| TR 38.785 vh00 | UE radio transmission for enhanced NR sidelink | Rel-17 read |
| TR 38.786 vi20 | Technical Report for NR Sidelink Evolution | Rel-18 read |
| TS 38.811 vf40 | Study on NR Support for Non-Terrestrial Networks | Rel-15 read |
| TR 38.845 vh00 | NR Positioning Use Cases Study | Rel-17 read |