# 3GPP TR 26.942 CR 0024 Rev 5 - Solution 5 Update for Energy Information Exposure

## General Information

**Title:** [FS_Energy_Ph2_MED] Solution 5 update  
**Work Item:** FS_Energy_Ph2_MED  
**Release:** Rel-20  
**Category:** F (Correction)  
**CR Revision:** 5

## Purpose of Change

This CR provides corrections and updates to Candidate Solution 5 in TR 26.942, focusing on:
- Correcting procedures in clauses 7.6.3.1 and 7.6.3.2 to align with TS 23.501 and TS 29.566
- Reformatting according to new principles for documenting Candidate Solutions
- Adding missing normative references

## Main Technical Contributions

### 1. References Update (Clause 2)

Added three new normative references:
- **TS 26.510:** Media delivery; interactions and APIs for provisioning and media session handling
- **TS 26.512:** 5G Media Streaming (5GMS); Protocols
- **TS 26.113:** Real-Time Media Communication; Protocols and APIs

### 2. Functional Description Enhancements (Clause 7.6.1A)

**Clarified scope and objectives:**
- Solution addresses exposure of energy-related information from Media AS to UE or Media AF
- Demonstrates integration into 5GMS architecture
- Enables UE or 5GMS AF to optimize environmental impact
- Explicitly states this is a **generic architecture** for reuse, not specific optimization strategies
- Energy information exposure controlled by Application Service Provider using Energy Information Exposure Specification

### 3. New Collaboration Scenarios Section (Clause 7.6.1B)

Added explicit statement that solution applies to all collaboration scenarios requiring access to energy-related information from:
- UE
- Application Server
- EIF (Energy Information Function)

### 4. Generic High-Level Procedures Update (Clause 7.6.3.1)

**Major restructuring of procedure flow:**

#### Provisioning Phase (Steps 1-4)
1. Application Service Provider provisions Energy Information AF with Energy Information Exposure Specification
2. Energy Information AF subscribes to NF Energy Information from EIF (E12 reference point)
3. EIF responds with NF Energy Information report
4. Energy Information AF configures and subscribes to AS Energy Information from AS (E3 reference point)
5. AS responds with most recent AS Energy Information report

#### UE-Initiated Phase (Steps 5-11)
5. UE Application creates energy information collection context with Energy Information Collector (E6 reference point)
6. Energy Information Collector requests UE Energy Information collection configuration from Energy Information AF (E5 reference point), including Application Identifier
7. Energy Information Collector subscribes to Network Energy Information from Energy Information AF with Service Data Flow descriptions and Session Identifier
8. Energy Information AF processes NF and AS Energy Information reports
9. Energy Information AF exposes processed Network Energy Information to Energy Information Collector
10. Energy Information Collector collects additional UE Energy Information from UE functions
11. Energy Information Collector processes UE-related Energy Information

#### Repetitive Reporting Phase (Steps 12-18)
12. EIF exposes NF Energy Information report to Energy Information AF
13. AS exposes AS Energy Information report to Energy Information AF
14. Energy Information AF processes received reports
15. Energy Information AF exposes processed Network Energy Information to Energy Information Collector
16. Energy Information Collector receives additional UE Energy Information
17. Energy Information Collector processes UE-related Energy Information
18. Energy Information Collector exposes energy-related information to UE Application

#### Context Modification Phase (Steps 20-23)
20. UE Application informs Energy Information Collector of context modification with new Service Data Flow filters
21. Energy Information Collector updates subscription with Energy Information AF
22. Energy Information AF updates subscription with EIF
23. Energy Information AF updates subscription with AS

### 5. 5GMS-Specific Procedures Update (Clause 7.6.3.2)

**Comprehensive restructuring aligned with 5GMS architecture:**

#### Provisioning Phase (Steps 1-4)
1. 5GMS Application Provider provisions 5GMS AF via M1, including Energy Information exposure configuration
2. Energy Information AF subscribes to NF Energy Information from EIF with Application Identifier, requesting immediate report
3. EIF responds with NF Energy Information report
4. Energy Information AF subscribes to AS Energy Information from 5GMS AS with Application Identifier
5. 5GMS AS responds with most recent AS Energy Information report

#### Media Session Initiation Phase (Steps 5-15)
5. 5GMS-Aware Application initiates media delivery session with flag enabling energy information collection
6. Media Session Handler obtains Service Access Information including Energy Information AF details
7. Media Session Handler creates energy information collection context in Energy Information Collector
8. Energy Information Collector requests UE Energy Information collection configuration from Energy Information AF
9. Response includes UE Energy Information collection configuration and subscription endpoint
10. Energy Information AF processes NF and AS Energy Information reports
11. Energy Information AF exposes processed Network Energy Information report to Energy Information Collector

**NOTE 1 added:** Explains that initial reports are not UE-specific but describe total energy consumed by all consumers (Application Identifier-based or AS service location-based)

12. Energy Information Collector subscribes to UE Network Energy Information from Media Stream Handler (M11)
13. Media Stream Handler responds with UE Network Energy Information report
14. Energy Information Collector processes Network and UE Energy Information
15. Energy Information Collector exposes aggregated Energy Information to Media Session Handler and Media Stream Handler
16. Media Session Handler provides available Media Entry Points to 5GMS-Aware Application, including Energy Information

#### Media Entry Point Selection (Steps 16-17)
16. 5GMS-Aware Application selects Media Entry Point
17. 5GMS-Aware Application invokes Media Stream Handler with selected Media Entry Point

#### Parallel Energy Information Reporting (Steps 18-26)
18. EIF exposes NF Energy Information report to Energy Information AF
19. 5GMS AS exposes AS Energy Information report to Energy Information AF
20. Energy Information AF processes network energy information reports
21. Energy Information AF exposes processed Network Energy Information to Energy Information Collector
22. Media Stream Handler exposes UE Energy Information report to Energy Information Collector
23. Energy Information Collector processes received Energy Information reports
24. Energy Information Collector shares processed report with Media Session Handler
25. Media Session Handler may expose energy-related information
26. 5GMS-Aware Application may expose received information to Application Service Provider via M8

#### Media Streaming with Context Modification (Steps 27-37)
27. Media Stream Handler establishes transport session at M4
28. Media Stream Handler requests Media Entry Point from 5GMS AS
29. Media Stream Handler selects Service Operation Point based on configuration and Energy Information
30. Media Stream Handler establishes new transport session with 5GMS AS service location
31. If Service Operation Point changed, Media Stream Handler notifies Media Session Handler with Service Data Flow identification information
32. Media Session Handler modifies energy information collection context in Energy Information Collector

**NOTE 2 added:** Explains that Service Data Flow description is now explicit based on known IP 5-tuples

33. Similar to step 9, subscribing with explicit Service Data Flow filters based on M4 transport sessions
34. Similar to step 2, subscribing to NF Energy Reports with explicit Service Data Flow filters
35. Similar to step 4, subscribing to AS Energy Reports with explicit Service Data Flow filters
36. Similar to step 24
37. Media streaming occurs between Media Stream Handler and 5GMS AS

### 6. Gap Analysis (Clause 7.6.4)

**Identified architectural gaps:**

- Defines two new entities:
  - **Energy Information AF:** Subscribes to NF Energy Information from EIF, receives AS Energy Information from AS, collates and exposes Network Energy Information to Energy Information Collector
  - **Energy Information Collector (UE function):** Acquires configuration from Energy Information AF, subscribes to Network Energy Information, collects UE Energy Information, exposes collected information to UE Application

**Specification gap identified:**
- TS 23.502 and TS 29.566 lack explicit provision for immediate reporting of energy consumption information as side effect of Neif_EventExposure_Subscribe operation
- Mitigation: Positioning of step 2 in provisioning phase means Energy Information AF likely receives initial NF Energy Report before application session initiation

### 7. Proposed Normative Changes (New Clause 7.6.5)

**Comprehensive normative work proposal:**

1. **New Stage 2 TS:** Generic architecture and procedures for Energy Information AF and Energy Information Collector, defining operations for:
   - Provisioning Energy Information AF (E1)
   - AS Energy Report subscription/exposure (E3)
   - Aggregated network energy information subscription/exposure (E5)
   - Energy information exposure to UE Application (E6)

2. **New Stage 3 TS:** Network APIs for Energy Information AF and Energy Information Collector at E1, E3, E5, and client API at E6

3. **TS 26.501 updates:**
   - Instantiation of generic architecture in 5GMS System
   - Collaboration scenarios for 5GMS Use Cases

4. **TS 26.506 updates:**
   - Instantiation of generic architecture in RTC System
   - Collaboration scenarios for RTC Use Cases

5. **TS 26.510 updates:**
   - Extensions to M5 procedures and interfaces for energy-related information in Service Access Information

6. **TS 26.512 updates:**
   - Extensions to E1, E3, E5 procedures for 5GMS System
   - Extensions to client API at M6 for 5GMS-Aware Application

7. **TS 26.113 updates:**
   - Extensions to E1, E3, E5 procedures for RTC System
   - Extensions to client API at RTC-6 for RTC-Aware Application

### 8. Summary Update (Clause 7.6.6)

**Revised summary emphasizing:**
- Generic approach for exposing energy-related information from device, network, and Application Server
- Integration into 5GMS and generalized Media Delivery architecture
- Introduction of two new components: Energy Information Collector (UE) and Energy Information Application Function (Media AF)
- Goal is generic architecture for reuse, not specific optimization strategies

## Key Technical Improvements

1. **Alignment with existing 3GPP specifications** (TS 23.501, TS 29.566)
2. **Clear separation of procedure phases** (provisioning, initiation, reporting, modification)
3. **Explicit Service Data Flow handling** (implicit during provisioning, explicit after transport session establishment)
4. **Session correlation** using Session Identifier throughout procedures
5. **Comprehensive reference point definitions** (E1, E3, E5, E6, E12, M1, M4, M6, M8, M11)
6. **Detailed normative work roadmap** across multiple specifications