3GPP TR 26.510 Change Request - Energy Efficiency Phase 2 for Media Services

Document Information

• CR Number: 0009 rev 2
• Specification: TR 26.942 v19.0.0
• Work Item: FS_Energy_Ph2_MED
• Category: B (addition of feature)
• Release: Rel-20

Purpose and Scope

This CR merges multiple contributions agreed by the MBS SWG before SA4#135, addressing energy efficiency aspects for media delivery services in Release 20. The CR builds upon Release 19 work on energy-related information exposure and extends it to media-specific scenarios.

Main Technical Contributions

1. References and Terminology Updates (Clauses 2, 3.1)

New References Added:
- TS 29.566: Energy Information Function Services (Stage 3)
- TS 29.122: T8 reference point for Northbound APIs

New/Updated Terms:
- AS Energy Information: Energy-related information collected and exposed by Application Servers
- NF Energy Information: Energy-related information collected from Network Functions and exposed by the EIF
- UE Energy Information: Energy-related information collected by the UE
- Network Energy Information: Combination of NF and AS Energy Information
- Energy availability: Remaining amount of energy locally available for consumption
- Energy capacity: Maximum amount of energy that can be locally available
- Energy supply mix: Combination of various energy sources (renewable and non-renewable)

2. Energy Information Function (EIF) Summary Update (Clause 4.2.2.3)

Enhanced EIF Responsibilities:
- Collection of "UE-related Energy Consumption information" from OAM and 5GC NFs comprising:
- Node-level energy consumption and data volume from OAM (gNodeB and UPF instances)
- Data transfer volumes from UPF via SMF with various filtering criteria
- Calculation of energy-related consumption information at multiple granularities
- Exposure via Neif_EventExposure service to authorized consumers

Subscription Filters Supported:
- Per UE
- Per slice and/or DNN
- Per PDU Session
- Per Service Data Flow

Stage 3 Information:
- Energy consumption expressed in Joules using floating-point representation
- EnergyEeNotif object contains array of EnergyEeReport data structures
- Each report includes timestamp, optional EnergyInfo, and granularity indication

3. Use Cases from SA1 (Clause 5.1)

Release 19 Use Cases (TR 22.882):
- Use case 5.5: Service energy monitoring by Application Server
- Use case 5.6: Service-level energy efficiency analysis for verticals
- Use case 5.8: Application service Energy Efficiency monitoring
- Use case 5.9: Renewable energy consumption information exposure
- Use case 5.10: Carbon-aware communication service
- Use case 5.14: Reducing GHG footprint of Application Services

New Release 20 Use Cases (TR 22.883):
- Use case 5.1: Energy saving service for UE (AR/XR applications)
- Use case 5.2: Dynamic service adjustment based on energy information
- Use case 5.7: Tolerance to QoS degradation due to network energy saving
- Use case 5.8: Green social media & email content download
- Use case 5.9: Notifying UEs about network energy-related characteristics

4. Key Issue #1 Updates: Energy-related Information Exposure (Clause 6.1)

Key Questions:
1. How should UE energy-related information be reported to the 5G System?
2. Which reference points should be used for reporting?
3. How to expose network energy information to Media Session Handler?
4. How to allow UE reporting without exposing energy consumption rate?

Requirements from TR 22.882 and TR 22.883:
- [22.882-CPR 6.1-7]: Application server selection based on energy consumption
- [22.882-CPR 6.3-2/4]: Energy consumption monitoring for 3rd parties
- [22.882-CPR 6.4-1 to 6.4-5]: Energy consumption exposure to authorized parties
- [22.883-CPR 6.1.1-1 to 6.1.1-4]: Carbon emissions exposure and energy-related characteristics

Additional Potential Requirements:
- [PR 1-1]: Reuse existing mechanisms (e.g., UE data collection architecture per TS 26.531)
- [PR 1-2]: Reuse common client data reporting formats
- [PR 1-3]: Enable 5GMS Client to obtain energy information from UE

5. Key Issue #2 Updates: Energy-related Monitoring and Measurement (Clause 6.2)

Scope Extension:
- Beyond 5G network monitoring to include complete end-to-end media delivery chain
- Focus on UE-related energy information measurement and monitoring
- Applicable to 5GMS, 5MBS, RTC, and Split Rendering systems

Key Questions:
1. Which UE energy-related information should be collected?
2. Can existing methods be leveraged for measurement/monitoring?
3. Which UE entity is appropriate for measurement?

Requirements:
- [22.882-CPR 6.3-1 to 6.3-3]: Energy consumption monitoring at various granularities
- [22.883-CPR 6.1.4-1]: Assist 3rd party to identify target UEs for service adjustment

Additional Potential Requirements:
- [PR 2-1]: Reuse existing mechanisms where possible
- [PR 2-2]: Reuse common client data metrics
- [PR 2-3]: Enable ASP to adapt service parameters based on 5GS feedback

6. New Key Issue #4: Energy-related Configuration by ASP (Clause 6.4)

Description:
Addresses how Application Service Providers can configure energy-related information collection and exposure for media delivery services.

Key Questions:
1. How can ASP specify to network the possibility to use 5G capabilities for energy optimization?
2. How can ASP specify acceptable service degradation levels?

Requirements from TR 22.882 and TR 22.883:
- [22.882-CPR 6.1-1/2/4]: Subscription policies for energy credit limits and consumption
- [22.882-CPR 6.1-8/9]: Service modification based on energy criteria
- [22.883-CPR 6.1.2-2 to 6.1.2-4]: Alternative service performance and energy saving actions
- [22.883-CPR 6.1.3-1]: Charging events for degraded performance

7. New Key Issue #5: Media Application Server Energy Management (Clause 6.5)

Description:
Studies how media Application Servers (5GMS AS, RTC AS) should react to energy-related information shared by the network via Energy Information AF and/or Energy Information Collector.

Key Questions:
1. Should network energy information from EIF be exposed to media delivery systems?
2. How might 5GMS AS and RTC AS modify ongoing sessions based on energy-related characteristics?

Requirements:
- [22.882-CPR 6.1-7/8/9]: Application server selection and service modification
- [22.883-CPR 6.1.2-1 to 6.1.2-5]: Service degradation, targeted actions, and access control
- [22.883-CPR 6.1.4-1]: Assistance to identify target UEs

8. New Key Issue #6: Client-driven Energy Optimization (Clause 6.6)

Description:
Addresses how 5GMS Client and RTC Client should react to energy-related information shared by the network.

Key Question:
How might clients modify media delivery sessions in response to network energy-related characteristics?

Requirements:
- [22.882-CPR 6.1-7]: Application server selection based on energy information
- [22.883-CPR 6.1.4-1]: Assistance to identify target UEs for service adjustment

9. New Annex A: Guidelines for Candidate Solutions

Recommended Content for Candidate Solutions:
1. Tables of high-level baseline parameters for UE-related Energy Consumption information
2. Formulae for aggregating energy information from multiple sources (EIF, AS, UE)
3. Procedures to collect AS energy information at various granularities:
- Per AS Service Data Flow
- Per AS service location
- Per AS host name
- Per application session identifier

Clause Skeleton Structure:
- Key Issue mapping
- Functional description
- Collaboration scenarios
- Architecture mapping
- Energy-related information
- Procedures
- Gap analysis
- Proposed normative changes
- Summary

Impact and Dependencies

Affected Systems:
- 5G Media Streaming (TS 26.501)
- 5G Multicast-Broadcast User Services (TS 26.502)
- Real-time Media Communication (TS 26.506)
- Split Rendering Media Session Enabler (TS 26.565)

Dependencies:
- Release 19 Energy Information Function (TS 23.501, TS 23.502, TS 29.566)
- SA1 requirements (TS 22.261, TR 22.882, TR 22.883)
- SA2 study (TR 23.700-66)