3GPP TR 26.510 Change Request - Solution for KI1 and KI4

Document Information

• Meeting: 3GPP TSG-SA4 Meeting #135
• CR Number: 0008 rev 6
• Specification: 26.942
• Release: Rel-20
• Category: B (addition of feature)
• Work Item: FS_Energy_Ph2_MED

Change Request Summary

This CR proposes solutions for Key Issue #1 (Energy-related Information exposure) and Key Issue #4 (Energy-related configuration by the Application Service Provider for media delivery services) by introducing a Media Application Service Energy Metrics Reporting Configuration.

Main Technical Contributions

1. Solution #10: Media Application Service Energy Metrics Reporting Configuration

1.1 Overview and Approach

The solution extends the existing Metrics Reporting Configuration framework (defined in TS 26.501 clause 4.0.9) to support Energy-of-media-Service (EoS) metrics in addition to QoE metrics. This reuses the established M1 reference point provisioning mechanism.

The configuration determines:
- What energy-related information is collected and reported
- Which entities report (UE, Application Server, RAN, User Plane Function)
- Reporting frequency and intervals

1.2 Supported Energy Metrics

Four distinct energy exposing modes are defined, each with a dedicated metrics scheme:

1. Carbon intensity - reported in g CO₂-e/Wh
2. Energy consumption - reported in Wh
3. Energy renewable source ratio - reported as ratio
4. Energy contribution ratio - reported as ratio

All four schemes share an identical controlled vocabulary of metrics. Multiple schemes can be provisioned simultaneously under the same Provisioning Session.

2. Media Application Service Energy Metrics Reporting Configuration Parameters

2.1 Configuration Hierarchy

The solution defines a hierarchical configuration structure (Figure 7.11.2.2-1) that:
- Derives from the baseline Metrics Reporting Configuration
- Shares common parameters with existing QoE reporting
- Extends with energy-specific parameters
- Is conveyed via Service Access Information to Media Client

2.2 Key Configuration Parameters (Table 7.11.2.2-1)

Metrics Scheme:
- Specifies which of the four energy metrics schemes to use
- Determines format of aggregated energy-related metrics reports
- Multiple schemes can be provisioned

Delivery Session Sample:
- Sample mode (0 = all sessions, 1 = percentage-based, 2 = filtered by content type)
- Sample percentage
- Component content types filter (MIME-based filtering)

Reporting Parameters:
- Reporting start offset
- Reporting duration
- Reporting interval

Metrics to be Reported:
- Non-empty list from controlled vocabulary
- Uses fully-qualified term identifiers (URIs)
- All schemes share same vocabulary

Reporting Scope:
- Defines aggregation level for metrics
- Four options:
1. Per slice (identified by NSSAI) - aggregated over all sessions in slice
2. Per media delivery session - aggregated over all components in session
3. Across multiple media delivery sessions - aggregated according to sample mode
4. Per media delivery session with component filtering - filtered by MIME content type

Additional Flags:
- Contribution ratio flag - includes UE/RAN/CN breakdown when true

3. Controlled Vocabulary for Energy Metrics

Table 7.11.2.2-2 defines standardized metric identifiers:

| Metric Name | URI Identifier | Unit |
|-------------|----------------|------|
| Carbon intensity | urn:3gpp:media:application:service:energy:metric:carbonIntensity | g CO₂-e/Wh |
| Energy consumption | urn:3gpp:media:application:service:energy:metric:energyConsumption | Wh |
| Energy renewable source ratio | urn:3gpp:media:application:service:energy:metric:renewableSourceRatio | Ratio |
| Energy contribution ratio | urn:3gpp:media:application:service:energy:metric:energyContributionRatio | Ratio |

4. Architecture Mapping

The solution:
- Maps onto existing reference architecture from Solution #5
- Does not introduce new functional entities or reference points
- Configures reporting by UE, Application Server, and network entities
- Procedures detailed in clauses 7.12.3 and 7.13.3

5. Gap Analysis

5.1 Current Limitations (Release 19)

• Metrics Reporting Configuration primarily targets QoE metrics
• Framework assumes UE as sole reporting entity
• No standardized, entity-aware provisioning for energy metrics

5.2 Proposed Extensions

1. Media Application Service Energy Metrics Reporting Configuration inheriting from base Metrics Reporting Configuration
2. Controlled vocabulary for energy metrics (carbon intensity, energy consumption, renewable source ratio, contribution ratio)
3. Energy-specific reporting scopes including:
4. Per slice (NSSAI-based)
5. Per media delivery session
6. Aggregated across sessions
7. Component-level filtering by MIME type

6. Proposed Normative Changes

6.1 TS 26.501 (5G Media Streaming Architecture)

• Extend Metrics Reporting Configuration for energy metrics schemes
• Define hierarchy within Provisioning Session
• Specify conveyance over M1 to Energy Information AF and via Service Access Information

6.2 TS 26.510 (Metrics Reporting Configuration and Procedures)

• Extend data model with:
• Energy metrics schemes
• Reporting scope (including per-slice)
• Controlled vocabulary identifiers

6.3 TS 26.512 (Media Streaming APIs - M1)

• Support creation/management of Energy Metrics Reporting Configuration resources
• Support new configuration attributes
• Carry controlled vocabulary identifiers in configuration payload

7. Collaboration Scenarios

The solution is applicable to all collaboration scenarios requiring access to Media Application Service EoS metrics.

Summary

This candidate solution enables energy-related information collection and exposure by:

1. Extending metrics scheme to include carbon intensity, energy consumption, renewable source ratios, and contribution ratios
2. Refining reporting scope with per-session, per-component, and aggregated options including per-slice reporting
3. Reusing existing provisioning framework with configuration-driven reporting, cadence control, and controlled exposure mechanisms

The approach leverages the mature Metrics Reporting Configuration framework while adding energy-specific capabilities needed for network optimization, energy-aware service adaptation, user empowerment, and carbon emission attribution.