# Summary of 3GPP TR 26.501 Change Request

## Document Information
- **CR Number**: S4-260249
- **Specification**: 3GPP TR 26.958 v0.1.1
- **Work Item**: FS_3DGS_MED (3D Gaussian Splatting for Media)
- **Category**: B (addition of feature)
- **Release**: Rel-20

## Purpose
This CR addresses the mapping of 3D Gaussian Splatting (3DGS) services to 3GPP services and specifications, specifically for the "All in UE" configuration.

## Main Technical Contributions

### Clause 10: Mapping to 3GPP Services/Specifications

This CR introduces a new clause (Clause 10) that maps high-level media data workflows for 3DGS to different 3GPP services. The mapping covers two configurations, with this CR specifically detailing the "All in UE" configuration.

### 10.1: All in UE Configuration Mapping

In this configuration, 3DGS content is treated as **downloadable or message-based assets**. The CR provides a comprehensive mapping table that covers the following functional areas:

#### Content Generation
- **Functions**: Scene capture, static 3DGS model generation, time-aligned animation stream generation for animating 3D Avatars
- **3GPP Mapping**: 3DGS/XR Application on the UE
- **Reference**: Media-Aware Application of Media Delivery architecture (TS 26.501)

#### 3DGS File Delivery
- **3GPP Mapping**: 
  - MMS (TS 26.140, TS 26.143)
  - RCS messaging
  - HTTP file transfer
- **Reference**: Media Access Function of Media Delivery architecture (TS 26.501)
- **Functionality**: Provides upload/download function for sending and receiving 3DGS content

#### Storage
- **3GPP Mapping**: UE Local storage (no 3GPP-specific mapping)

#### Rendering and Playback
- **3GPP Mapping**: 3DGS/XR Application on the UE
- **Reference**: Media-Aware Application (TS 26.501)

### Key Technical Notes

**NOTE 1 - File-based Delivery Requirements**:
- 5G latency or jitter requirements do not apply (strict 5G QoS is not necessary)
- Low Packet Error Rate and reliable delivery required
- Standard 5G bearers specified in TS 23.501 are adequate to carry 3DGS content

**NOTE 2 - Storage**: No 3GPP-specific mapping required

## Technical Implications

The CR establishes that for the All in UE configuration:
1. 3DGS content follows a file-based delivery model rather than streaming
2. Existing 3GPP services (MMS, RCS, HTTP) are sufficient for content delivery
3. Standard 5G bearers are adequate without requiring enhanced QoS
4. The architecture aligns with the existing Media Delivery framework in TS 26.501