Summary of S4-260058: Preliminaries - Assumptions and Requirements for 6G Media Delivery

Overview

This change request introduces foundational content for the new FS_6G_MED (6G Media Delivery) study in TR 26.870. It establishes the preliminary assumptions, requirements framework, and baseline for existing media services that will inform the 6G media architecture work.

Main Technical Contributions

References Section

Adds comprehensive normative and informative references including:
- Core 6G specifications (TR 22.870, TR 23.801-01, TS 22.ABC)
- Existing 5G media specifications (TS 26.501, TS 26.506, TS 26.511, TS 26.512, TS 26.114, TS 26.117, TS 26.510, TS 26.517, TS 26.502, TS 26.143)

Clause 4.1: Assumptions

Architecture Assumptions (from SA2)

Establishes baseline architectural assumptions carried forward from TR 23.801-01:

1. SBA Framework: 5GC Service-Based Architecture as starting point
2. Single Core Network: 6G RAN connects to single 6G CN type (standalone architecture)
3. RAN/CN Split: Maintains 5GS RAN and CN functionality split
4. No Duplication: Avoids functionality duplication between 6G RAN and 6G CN
5. IMS for Real-time Services: MMTel voice/video services provided by IMS
6. Native TN/NTN Support: Both Terrestrial and Non-Terrestrial Networks natively supported

Key Issues Baseline

Identifies SA2 key issues serving as baseline for 6G media delivery:
- Key Issue #3: Network Slicing
- Key Issue #4: User Plane Architecture
- Key Issue #5: QoS Framework
- Key Issue #7: Network Exposure
- Key Issue #11: Non-3GPP access support
- Key Issue #12: Voice Services
- Key Issue #15: Messaging Services
- Key Issue #19: 6G Network for AI
- Key Issue #20: Integrated Sensing and Communication
- Key Issue #21: 6G data framework
- Key Issue #22: 6G Computing Support
- Key Issue #23: 6G NTN Support

Media-Specific Assumptions

Establishes 5G media specifications as starting points:

1. Common Architecture: TS 26.501 (5GMS) and TS 26.506 (5G RTC) architectures as baseline
2. Streaming Codecs/Formats: TS 26.511 as starting point for 6G media streaming
3. Streaming Protocols: TS 26.512 as baseline for 6G media streaming protocols
4. RTC Protocols/Codecs/Formats: TS 26.114 as baseline for Voice Services
5. Messaging Codecs/Formats: TS 26.143 as baseline for Messaging Services

Clause 4.2: Requirements

Placeholder for architectural and media-related requirements from SA1, including use cases and requirements.

Clause 4.3: Existing Media Services

Media Services Classification

Defines 3GPP media services structure across working groups:
- SA1: Service definition
- SA2: Architectural support
- SA4: Media technologies (protocols, codecs, formats, QoE)

Distinguishes between:
- Full media services: Complete 3GPP-defined services
- Media service enablers: Components enabling interoperability for third-party services

Relevant Media Services (Clause 4.3.2)

Identifies existing services for 6G consideration:

1. IMS-Based Multimedia Telephony and Communication Services
2. SA1: Service requirements
3. SA2: System architecture for multimedia services

4. SA4: TS 26.114 (codecs, formats, protocols, QoE, telephony acoustics)

5. XR (AR/VR/MR) Media Services

6. SA1: Use cases and Stage-1 requirements
7. SA2: 5G XR/media architecture improvements (multi-modal QoS, information exposure)
8. SA4: XR traffic characteristics, formats, codecs, streaming frameworks

Media Service Enablers (Clauses 4.3.3 and 4.3.4)

Lists existing 3GPP media service enabler components:

• Real-time Communication beyond IMS
• 5G Media Streaming: TS 26.501, TS 26.510, TS 26.511, TS 26.512, TS 26.117
• Messaging Media Profiles: TS 26.143
• MBS User Services: TS 26.502, TS 26.517
• Formal MSE: TS 26.565 (Split Rendering MSE)

References TR 26.857 for formalized Media Service Enabler framework.

Editorial Notes

Multiple editor's notes indicate areas requiring further development:
- Additional assumptions may be added
- Requirements clause to be populated with SA1 inputs
- Additional media services and enablers to be added
- Existing media services status (relevancy/deployments) to be identified