PBR

Physically-Based Rendering

Other →
Introduced in Rel-8

PBR is a 3GPP rendering technique for XR that simulates light's physical behavior to create photorealistic graphics, crucial for immersive AR/VR over 5G networks.

Category
Other
Introduced
Rel-8
Where
Services › Codecs
Specifications
3 specs
PBR Description Purpose Detected Changes Specifications

Description

Physically-Based Rendering (PBR) within the 3GPP context refers to a set of advanced computer graphics techniques standardized to support high-quality, immersive Extended Reality (XR) services over mobile networks. Unlike traditional rendering methods that use approximations and artistic adjustments, PBR algorithms simulate the physical properties of materials and the real-world interaction of light with those surfaces. This involves complex calculations for light reflection, refraction, absorption, and scattering based on bidirectional reflectance distribution functions (BRDFs) and other physical models. The goal is to produce visuals that are consistent under various lighting conditions, thereby achieving a high degree of photorealism essential for convincing AR and VR environments.

In the architecture of an XR service delivery system, PBR processing can be distributed between the user equipment (UE), such as an XR headset, and edge or cloud servers. The 3GPP specifications, particularly in TS 26.928 and TS 26.998, study the implications of such rendering on the network. The rendering engine, whether local or remote, uses PBR shaders and texture maps (albedo, normal, roughness, metallic) to compute the final pixel color for each frame. This computation is computationally intensive and directly influences the bitrate, latency, and frame rate requirements for the media stream transmitted over the 5G system.

The role of PBR in the network is multifaceted. It defines a key characteristic of the traffic generated by next-generation XR applications. Network functions, including the 5G Core (5GC) and the Radio Access Network (RAN), must be aware of the stringent QoS demands of PBR-rendered content, such as ultra-low latency for interactive feedback and high bandwidth for detailed texture streaming. 3GPP studies model this traffic to design appropriate network slicing, edge computing (MEC) offloading strategies, and radio resource management policies that can efficiently deliver such demanding services while maintaining user Quality of Experience (QoE).

Purpose & Motivation

The standardization of Physically-Based Rendering techniques in 3GPP was motivated by the rise of immersive Extended Reality services as a key use case for 5G and beyond networks. Previous mobile graphics and streaming services, like traditional video, relied on simpler rendering models that did not require the same level of physical accuracy or interactivity. These older approaches were insufficient for creating believable virtual worlds where visual consistency and realism are paramount for user immersion and comfort, especially in professional training, social interaction, and entertainment applications.

PBR addresses the problem of visual inconsistency found in older, ad-hoc rendering methods. By basing calculations on physical laws, it ensures that materials look correct under any lighting environment, which is critical for AR applications that blend digital objects with the real world. From a network perspective, understanding PBR is essential because it creates a new class of traffic with predictable but demanding patterns. The 3GPP's work on PBR, starting in Release 15 with studies on XR, aims to characterize this traffic to solve network planning and optimization challenges. It helps define the necessary QoS parameters, such as packet delay budget and guaranteed bit rate, to support real-time, interactive, high-fidelity graphics streaming, which was not a primary concern for pre-5G multimedia services.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 3 changes

In Release 15, the PBR (Physically-Based Rendering) function was not newly introduced; the provided CR titles and grounding context exclusively discuss other topics such as split compute/rendering architectures, XR service delivery, and QoS models. The technical details from the specification text focus on rendering engines and APIs like OpenGL or Vulkan for generating 3D graphics, but do not specify any Release 15 introduction of PBR.

  • Introduction of DEFLATE based UDC Solution TS 36.300CR1090
  • Stage 2 Changes based on CN type indication for Redirection from ng-eNB to E-UTRA TS 36.300CR1185
  • Correction for duplication based on Rel-14 TX profile TS 36.300CR1193
Rel-17 1 change

In Release 17, the PBR (Physically-Based Rendering) function was not explicitly introduced as a new feature within the provided grounding context. The technical report focuses on outlining baseline technologies for XR services, including categories like split compute/rendering and the use of rendering engines that can employ various methods like rasterization or ray-tracing. Therefore, based on the given materials, there is no specific description of a new PBR capability distinct from the existing rendering engine functionalities documented for XR.

  • Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast TS 36.300CR1360
Rel-18 2 changes

In Release 18, the PBR (Physically-Based Rendering) function was not a new introduction; the provided grounding context and Change Request titles do not describe any specific new features or capabilities for PBR in this release. The technical material focuses on outlining baseline XR technologies, delivery categories like split compute/rendering, and architectural models, without detailing new PBR-specific procedures or interfaces introduced in Release 18. The listed CRs also pertain to other areas, such as corrections for IoT NTN and location-based measurements, not to PBR enhancements.

  • Correction of timer-based conditional handover for IoT NTN TS 36.300CR1399
  • Corrections to location-based measurement TS 36.300CR1417
Rel-19 2 changes

In Release 19, the PBR (Physically-Based Rendering) function was not a primary focus of the new standardization work. The release instead introduced new delivery categories for XR services, including split compute/rendering, and continued studies on integrating computational resources for edge-based rendering, as outlined in the technical report. The specific CR titles for this release indicate work on other areas, such as LTE-based 5G Broadcast Phase 2 and corrections for IoT NTN handover, rather than detailing new PBR-specific procedures or capabilities.

  • Introduction of LTE-based 5G Broadcast Phase 2 TS 36.300CR1428
  • Correction of time-based handover for IoT NTN TS 36.300CR1448

Explore further

Broader topics and technologies where PBR plays a role.

Defining Specifications

3GPP specifications that define or reference PBR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19