Meeting: TSGS4_135_India | Agenda Item: 8.5
20 documents found
[FS_Energy_Ph2_MED] Document Media Application Service Model
This Change Request introduces a comprehensive Media Application Service model to TR 26.942 for the FS_Energy_Ph2_MED study item. The CR establishes a common baseline understanding of how Application Services interact with the 5G System to exchange media over the User Plane, providing conceptual models for different media service types.
The CR defines a foundational model describing media delivery sessions over the 5G System User Plane:
Based on TS 26.501 reference architecture, the CR defines separate conceptual models for downlink and uplink media streaming.
| Concept | Description | |---------|-------------| | 5GMSd AS instance | (Edge) 5GMSd AS instance in deployment | | Content Hosting Configuration | Corresponds to single Provisioning Session in 5GMSd AF; may be present in multiple (Edge) 5GMSd AS instances | | Distribution Configuration | Models a service location exposed by (Edge) 5GMSd AS instance | | Downlink media streaming session | Models session spanning one or more content items | | Service Data Flow | HTTP connection at reference point M4d described by IP 5-tuple | | Application Data Flow | Series of media segment download requests at M4d; multiple HTTP requests may be multiplexed onto same HTTP connection (serial or parallel) |
| Concept | Description | |---------|-------------| | 5GMSu AS instance | (Edge) 5GMSu AS instance in deployment | | Content Publishing Configuration | Corresponds to single Provisioning Session in 5GMSu AF; may be present in multiple (Edge) 5GMSu AS instances | | Contribution Configuration | Models a service location exposed by (Edge) 5GMSu AS instance | | Uplink media streaming session | Models session spanning one or more content items | | Service Data Flow | HTTP connection at reference point M4u described by IP 5-tuple | | Application Data Flow | Series of media segment upload requests at M4u; multiple HTTP requests may be multiplexed onto same HTTP connection |
Based on TS 26.506 reference architecture, the RTC model has a simpler structure than 5GMS.
| Concept | Description | |---------|-------------| | RTC AS instance | (Edge) RTC AS instance in deployment | | Media Function Configuration | Corresponds to single Provisioning Session in RTC AF; may be present in multiple (Edge) RTC AS instances | | RTC session | Models set of RTP sessions comprising a WebRTC session | | Service Data Flow | UDP association at reference point RTC-4 described by IP 5-tuple; one or more Application Data Flows may be multiplexed | | Application Data Flow | SRTP packets sharing same Synchronisation Source (SSRC) value in packet headers |
The introduction (clause 4.2.2.6.1) clarifies that these models establish a common baseline understanding for how Application Services interact with the 5G System. Candidate Solutions in the Technical Report may reference one or more of these models as applicable.
[FS_Energy_Ph2_MED] Candidate Solution on Application Server Energy Information
Type: Category B (Addition of Feature)
Release: Rel-20
Work Item: FS_Energy_Ph2_MED
Source: BBC, Orange
This CR introduces a new Candidate Solution for reporting energy consumption of Application Servers in the Data Network as part of end-to-end service chain energy monitoring.
This Candidate Solution addresses:
The solution recognizes that total energy consumption for application services must account for: - 5G System energy (5G Core and RAN) via Energy Information Function - Application Server energy in the Data Network (focus of this solution) - UE energy consumption
Key principle: Application Servers exist in the Data Network and are not Network Functions, therefore outside the scope of the Energy Information Function and must be accounted for separately.
The solution identifies critical granularities for energy optimization:
Supports aggregated view across multiple (Edge) Application Server instances hosting the same service location
Per Service Data Flow:
Important Limitation: Application Servers cannot report energy consumption per UE (no visibility of UE identities), but the Energy Information AF can perform reverse IP address lookup in 5G Core for per-UE routing.
The solution proposes a comprehensive AS Energy Report with the following baseline parameters:
For each active Application Data Flow: - Service Data Flow description: IP 5-tuple identifying client and Application Server endpoints - Uplink data volume: Total Application Data Units delivered to AS instance - Downlink data volume: Total Application Data Units delivered from AS instance - AS host name: (Optional) Application Server host name for UE connection - Application session identifier: (Optional) Unique identifier for application session - Configuration identifier: Unique identifier for configuration in logical Application Server - Service location identifier: (Optional) Identifier for service location exposed by AS instance
The solution proposes a proportional attribution model: - Total energy consumption measured over sampling period - Bytes transferred per Service Data Flow metered during same period - Average energy attributed to Service Data Flows proportionally to data volume
The raw information enables multiple aggregation views:
The solution integrates with the Energy Information AF architecture (from Clause 7.6) via reference point E3, enabling: - Periodic AS Energy Reports from Application Server to Energy Information AF - Generic procedure realization (step 13 in generic procedure, step 19 in 5GMS procedure)
Based on generic architecture from Clause 7.6.2.2
5GMS instantiation (TS 26.501):
Extensions for in-band energy information from M2d (downlink) and M4u (uplink)
RTC instantiation (TS 26.506):
Service-based interface definitions for E3
5GMS extensions (TS 26.512):
5GMS AS Energy Report data structures
RTC extensions (TS 26.113):
[FS_Energy_Ph2_MED] Energy-aware Streaming
This Change Request introduces energy-aware streaming capabilities to TR 26.942 as part of the FS_Energy_Ph2_MED work item. It is a Category B (feature addition) CR for Release 20 that addresses limitations in the current energy-aware streaming approach by making it access-independent while maintaining integration with 3GPP architecture.
The contribution addresses two critical aspects of energy accounting: - Scope: Defines boundaries of what energy consumption to measure in the media delivery chain - Attribution: Determines how to assign energy costs across different stages and users
The document proposes limiting scope to content distribution aspects, starting from: 1. Content encoding - Different codecs and encoder implementations have varying energy costs 2. Content packaging - Different packaging technologies have different energy costs 3. Origin hosting - Energy costs for keeping media segments available and serving them
The contribution proposes a sophisticated attribution model: - For every fan-out in multi-tier CDN, energy cost is divided among next tier destinations - Maintains rolling average based on destinations served - First requester bears full acquisition cost at a CDN node - Subsequent requesters share acquisition cost fairly - Time-dependent caching factor creates "opportunity cost" for cache availability - Attribution divisor increments monotonically, decreasing per-requester cost until cache expiry
The solution addresses: - Key Issue #2: Energy-related monitoring and measurement - Key Issue #4: Energy-related configuration by Application Service Provider - Key Issue #5: Media Application Server Energy management - Key Issue #6: Client-driven management of media delivery service energy optimization - Key Issue #7: In-band signalling of upstream energy consumption
The solution defines a generic streaming workflow (Figure 7.X.2.1-1):
Proposes creating a registry/repository/catalogue for energy-related metrics: - Similar to MP4RA or DASH-IF identifiers - Each metric assigned a key (4CC code or URN) - Well-defined metrics with specification references - Allows evolution without framework changes
Hypothetical Examples:
- Greening of Streaming: urn:org:gos:energyindex:2025 or 4CC 'eeix' for average aggregated energy per second
- French AFNOR: urn:org:afnor:carbonindex:2025 or 4CC 'eecx' for average aggregated carbon per second
Multiple mechanisms proposed for carrying energy metrics:
Specific proposals for DASH MPD: - Energy information assigned to each resource - Assignment to individual components: - Content (aggregate consumption) - Adaptation Set - Representation - Segment - Service Locations (normalized to bitrate) - Labels: Describe energy information for user-based selection - Dedicated Energy descriptor: Similar to Accessibility descriptor for regulatory requirements - Combination rules: When information available at multiple levels, combine appropriately (e.g., CDN efficiency + encoding energy)
In Media Client: - Expose energy information to user and/or application - Enable content selection based on energy metrics - Select service locations based on energy information - Report aggregated metrics to reporting server (DASH Metrics or CMCD) - Optionally add client energy consumption to aggregated metrics
In Other Delivery Chain Functions: - Use in-band information for operational and reporting purposes
Specific integration points: - CDN mapping: CDN may be Media AS - Service locations: CDN1/CDN2 mapped to different service locations for energy optimization - Content Steering: Steer clients to energy-efficient delivery - Reporting options: Include or exclude UE consumption - Media AS/EIF integration: Media AS collects information from Media AF/EIF to insert energy metrics into streaming metadata
Call flow steps:
Shares accumulated energy info with Packager
Packager:
Shares accumulated energy info with Manifest Generator
Manifest Generator:
Adds energy information for each service location/CDN
Delivery:
Media Client requests media based on energy information from CDN1/CDN2
Reporting:
Based on 5GMSd architecture (TS 26.501): - References Solution #5 architecture (clause 7.6.3.2) - Media Stream Handler (in UE) is decision-making function - Receives energy information directly from 5GMSd AS via in-band information (manifest and/or CMSD) - Manifest differentiates energy information by service location and other parameters - Note: Does not use Energy Information Collector from Solution #5
Status: Detailed steps marked as "To be completed" - FFS
This CR is related to: - TR 26.952 CR 0003 - TR 26.952 CR 0004 - TR 26.952 CR 0005
[FS_AMD_Ph2] WT#2a - Common server- and network-assisted streaming
This is a Category C (functional modification) Change Request (CR 0031, revision 1) to TR 26.804 version 19.1.0, addressing Work Topic #2a on Common server- and network-assisted streaming under the FS_AMD_Ph2 study item. The CR proposes to merge with CRs 0032 and 0037.
Addition of new normative reference: - [X3] SVTA1108: "CMSD to Enhance Media Streaming: A White Paper" from SVTA organization - Provides industry perspective on CMSD usage and benefits
mb parameter (maximum suggested bitrate):The CR identifies CMSD as a candidate technology for in-band QoS signaling at application layer, with relevant parameters from CMSD-Dynamic header:
- currentBitrate
- bufferLevel
- playbackPosition
- throughputEstimate
Protocol Stack Constraints: - CMSD operates at HTTP layer - Network elements at lower protocol stack levels (e.g., routers with rate limiting) cannot interpret HTTP-level CMSD - More suitable for application servers than network infrastructure elements - Cannot be applied generically to non-streaming traffic types
Content-Specific Nature:
- CMSD data tightly coupled to media content and server-client connection
- Parameters like throughputEstimate and bufferLevel are client-specific and presentation-specific
- Not applicable to generic network link characterization
- Study will investigate whether more generic network connection information is needed for in-band QoS signaling
Comprehensive mapping of CMSD headers with their associated keys and descriptions:
| Header | Keys | Purpose | |--------|------|---------| | CMSD-Static | codec, resolution, duration, encodedBitrate | Static media object information | | CMSD-Dynamic | currentBitrate, bufferLevel, playbackPosition, throughputEstimate | Session-variable information | | CMSD-Cache | cacheStatus, cacheHitRatio, cacheExpiration | Cache status information | | CMSD-Error | errorCode, errorDescription | Error reporting | | CMSD-Quality | videoQuality, audioQuality, qualityAdjustments | Quality metrics | | CMSD-User | userID, sessionID, userPreferences | User-specific data | | CMSD-Session | sessionStartTime, sessionDuration, sessionID | Session information | | CMSD-Event | playbackStart, pause, resume, stop | Session events | | CMSD-Performance | serverResponseTime, networkLatency, throughput | Performance metrics | | CMSD-Content | contentID, contentType, contentDuration | Content metadata |
Reference to SVTA white paper [X3] demonstrating: - Experimental validation of CMSD benefits across delivery chain (origin servers to players) - Improvements in: - Latency reduction - Startup time - Quality of Experience (QoE)
The dash.js reference client implements a subset of CMSD parameters:
1. CMSD mb (Maximum Suggested Bitrate)
- Server Behavior: Sends mb in CMSD response headers as recommended upper bound
- Client Implementation:
- Treats mb as hard ceiling for ABR bitrate selection
- When enabled (abr.applyMb = true):
- Avoids selecting bitrates higher than mb
- Immediately throttles down if currently playing above mb
- Maintains upper bound until new mb received or playback ends
- Benefits:
- Prevents over-aggressive ABR decisions
- Reduces oscillations from bandwidth overestimation
- Leverages server's global visibility for client guidance
2. CMSD etp (Estimated Throughput)
- Server Behavior: Provides server-side throughput estimate (typically measured at response start)
- Client Implementation:
- Integrates into ABR logic via weighting mechanism
- abr.etpWeightRatio defines server vs. client estimate influence
- Example: 0.5 = 50% server estimate + 50% client estimate
- Can influence initial bitrate selection during manifest load
- Benefits:
- Server-side estimates more accurate (especially for low-latency/chunked-transfer scenarios)
- Reduces ABR oscillation/"ping-pong" from noisy client measurements
- Produces smoother bitrate choices and fewer stalls
- Validated by CMSD studies
The CR establishes CMSD as a viable application-layer mechanism for server-assisted streaming optimization while clearly identifying its architectural constraints for network-layer QoS signaling. The inclusion of dash.js implementation details provides concrete validation of CMSD's practical benefits in production environments.
[FS_Energy_Ph2_MED] Solution 5 update
Title: [FS_Energy_Ph2_MED] Solution 5 update
Work Item: FS_Energy_Ph2_MED
Release: Rel-20
Category: F (Correction)
CR Revision: 5
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
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
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
Added explicit statement that solution applies to all collaboration scenarios requiring access to energy-related information from: - UE - Application Server - EIF (Energy Information Function)
Major restructuring of procedure flow:
Comprehensive restructuring aligned with 5GMS architecture:
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)
NOTE 2 added: Explains that Service Data Flow description is now explicit based on known IP 5-tuples
Identified architectural gaps:
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
Comprehensive normative work proposal:
Energy information exposure to UE Application (E6)
New Stage 3 TS: Network APIs for Energy Information AF and Energy Information Collector at E1, E3, E5, and client API at E6
TS 26.501 updates:
Collaboration scenarios for 5GMS Use Cases
TS 26.506 updates:
Collaboration scenarios for RTC Use Cases
TS 26.510 updates:
Extensions to M5 procedures and interfaces for energy-related information in Service Access Information
TS 26.512 updates:
Extensions to client API at M6 for 5GMS-Aware Application
TS 26.113 updates:
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
[FS_Energy_Ph2_MED] Solution for KI6 Client-driven management of media delivery service energy optimisation with CMSD
This CR proposes a solution for Key Issue #6 (Client-driven management of media delivery service energy optimisation) by adding a new clause 7.11 to TR 26.942. The solution enables Media Clients to select Media Entry Points based on energy characteristics using Common Media Server Data (CMSD).
The CR introduces Solution #10: "Client-driven selection of Media Entry Point in the generalised Media Delivery System based on energy characteristics"
Key Issue Mapping: - Addresses KI#1 (Energy-related Information exposure) - Addresses KI#6 (Client-driven management of media delivery service energy optimisation)
Core Concept: - Leverages existing CMSD [CTA-5006] mechanisms to communicate energy consumption and COâ‚‚ equivalent information from media servers to media players - Enables media players to select distribution paths/modes with least environmental impact - Integrates an Energy Information Manager in media content servers to collect energy data across the distribution chain - Media players supplement server data with local UE energy consumption data
User Modes: Three energy preference modes are defined: - Eco mode: Prioritizes energy efficiency over QoE - Standard mode: Balances energy efficiency and QoE - Performance mode: Prioritizes QoE over energy consumption
Reporting Mechanisms: - Uses CMSD for downlink energy information (server to client) - Uses CMCD [CTA-5004] for uplink reporting (client to server/ASP) - Custom key names employed for energy-specific parameters (not yet standardized in CMCD/CMSD)
Scope Limitation: - Applicable only to downlink 5G Media Streaming (5GMS) context - UE energy collection methods are out of 3GPP scope
Reference Architecture: - Based on 5GMSd architecture (TS 26.501, TS 26.506) - Reuses Solution #5 architecture for collecting/exposing energy characteristics - Key difference: No Energy Information Collector in UE; Media Player receives energy data directly from 5GMSd AS via CMSD
Key Components: - Energy Information AF (instantiated in 5GMSd AF): - Subscribes to NF Energy Information from EIF (per TS 23.501 clause 5.51) - Subscribes to AS Energy Information from 5GMSd AS - Exposes aggregated Network Energy Information to 5GMSd AS
Reference Points Reused: M1d, M2d, M3d, E3, M4d, M5d, E5, M6d, M8, M11d, E12
Relevant Granularities: - Per media delivery session: Aggregating energy from Application Data Flows with same IP 5-tuple or session identifier - Per service location: Aggregating Media AS Energy Reports from all (Edge) Media AS instances exposing that service location
Energy Information Types: - Energy consumed (in Joules per TS 29.122) - Environmental cost of energy supply
NF Energy Report (7.11.4.3): - Reported by EIF per TS 29.566 clause 6.1 - Uses Application ID initially; refined using Service Data Flow Descriptions during session - Granularity as requested in subscription
Media AS Energy Report (7.11.4.4): - Uses Application ID and Service Location identifier initially - Fine-tuned using Service Data Flow Description during session - Reports from multiple Service Locations provided to enable comparison
CMSD Information (7.11.4.5): - Parameters defined for reporting energy information about service locations - Transmitted at reference point M4d from 5GMSd AS to Media Player
Key Procedure Steps (differences from baseline):
Step 2: Media-aware Application indicates selected end-user energy mode when initiating media delivery session
Step 4a: 5GMSd AS subscribes to Network Energy Information from Energy Information AF (including Application ID and Service Location notification URLs)
Step 6: Media Session Handler obtains Service Access Information including Energy Information AF access details and CMCD configuration
Step 10a/20a: Energy Information AF exposes processed Network Energy Information about provisioned service locations to 5GMSd AS
Step 15: Media Session Handler provides Media Entry Points to Media-aware Application including energy-related information for each
Step 16: Media-aware Application selects Media Entry Point with energy characteristics matching configured energy mode
Steps 16-19: Integrated into media delivery session loop to enable dynamic reselection of Media Entry Point if characteristics change
Note: Modifying Media Entry Point during session may cause playback discontinuity
Step 28a/28a bis: 5GMSd AS includes Network Energy Information in HTTP headers of Media Entry Point response using CMSD
Step 29/29bis: Media Stream Handler selects Service Operation Point based on Network Energy Information received via CMSD
Identified Gaps in Rel-19 Specifications:
New Stage 2 Specification Scope: - Provisioning Energy Information AF via M1d - Reporting energy information by 5GMSd AS via E3 with aggregations per: - Network slice - Data Network - Distribution Configuration (service location) - Application ID - Media streaming session - Subscription/exposure of aggregated network energy information from Energy Information AF to 5GMSd AS
TS 26.501 Changes: - Include Energy Management service subfunction in 5GMSd AS - Document AS service location selection based on energy information transmitted via CMSD
New Stage 3 Specification Scope: - Provisioning Energy Information AF via M1d - Reporting energy information by 5GMSd AS with specified aggregations - Subscription/exposure APIs at E3
TS 26.510 Changes: - Extend Content Hosting Configuration (clauses 5.2.8, 8.8.3.1) with Boolean flag in DistributionConfiguration indicating CMSD reporting eligibility
TS 26.512 Changes: - Extensions to procedures/interfaces at M1d, E3, M4d, M6d, M8d for energy-related information - Extensions to support energy information exposure using CMSD - Extensions to support CMCD version 2 information
Solution Advantages:
Applicability: - Any 5GMSd Application Provider delivering via 5GMSd System - Natural integration with MPEG-DASH and HLS adaptive streaming architectures - Supports French regulator (Arcom/Arcep) recommendations on environmental impact of audiovisual services
[FS_Energy_Ph2_MED] Solution for KI5 Media Application Server Energy management
CR Number: 0007 rev 6
Specification: 3GPP TR 26.942 v19.0.0
Work Item: FS_Energy_Ph2_MED
Category: B (Addition of feature)
Release: Rel-20
This CR proposes Solution #11 addressing Key Issue #5 (Media Application Server Energy management) by introducing a content steering mechanism based on energy characteristics for downlink media streaming service location selection.
Addresses KI#5 specifically: - Exposing energy-related information from the network (via EIF) to media delivery systems - Enabling 5GMS AS to modify ongoing media delivery sessions based on energy-related characteristics shared by the network via Energy Information AF instantiated in the 5GMSAF
Core Concept: - Leverages existing content steering capabilities in MPEG-DASH and HLS (already supported in 5GMS from Rel-19 per TS 26.512 clause 10.3A.4) - Extends steering server decision-making to include environmental impact considerations alongside traditional QoS criteria - Utilizes network energy characteristics from EIF (Energy Information Function) to select delivery paths with lowest environmental impact
Key Differentiator: - Compared to Solution #5, this approach adapts streaming sessions based on network environmental impact without affecting the UE or impacting the data plane - Decision-making is implementation-dependent but could use metrics like kgCOâ‚‚e per Joule of energy supplying the AS - Example use case: Content available on 2 Media 5GMSd AS service locations with different energy supply mixes; MNO adapts steering to maximize use of location with lower kgCOâ‚‚e per Joule
Applicability: - Exclusively for downlink media streaming (as per TS 26.512 clause 10.3A.4)
Requirements: - Energy information reporting from EIF and/or 5GMSd AS - No energy information from UE required - Downlink media streaming only
Architecture Components:
Based on TS 26.501 and TS 26.506, instantiating Solution #5 architecture with modifications:
Operates according to Energy Information Processing Configuration provisioned by 5GMSd Application Provider
Key Architectural Differences from Other Solutions:
Energy characteristics assumed unchanged on UE side; selection relies solely on network-provided energy information
Reference Points:
Advantages: - No impact on UE - Compatible with legacy devices - Less efficient than solutions incorporating UE energy data, but broader applicability
Objective: Dynamically select 5GMSd AS service location with energy information aligned with 5GMSd Application Provider configuration
Information Required: - Energy consumed from EIF and various 5GMSd AS instances - Environmental cost of energy supply - Network energy consumption related to specific 5GMSd AS service locations (since AS typically only report direct consumption)
Relevant Granularities:
Editor's Note: Energy Information Configuration will be detailed in separate solution
High-level baseline parameters describing 5GMSd Application Provider's operational constraints regarding collection, reporting, and exposure of energy-related information.
Source: TS 29.566 clause 6.1
Subscription Parameters: - Initial: Application ID only - During session: Refined using Service Data Flow Description per Service Location
Report Content: - Total energy consumption in joules (per TS 29.122 clause 5.3.2.3.20) - Provided at requested granularity - For specific timestamp
Subscription Parameters: - Initial: Application ID and Service Location Identifier - During session: Fine-tuned using Service Data Flow Description (exchange between all UEs and particular Service Location)
Report Content: - Energy consumed in joules at specified granularity - Reports from currently used Service Location AND other available Service Locations - Allows UE to be informed of Service Locations with better performance characteristics aligned with user mode requirements - Uplink data volume not used in this solution
Procedure Overview: Combines content steering procedure (TS 26.512 clause 10.3A.4) with baseline energy information sharing procedure (clause 7.6.3.2 Solution #5), omitting Energy Information Collector interactions.
Key Procedure Steps:
Step 0: Provisioning - 5GMSd Application Provider creates Provisioning Session and Content Hosting Configuration in 5GMSd AF - Content Hosting Configuration declares multiple service locations in different Distribution Configurations eligible for content steering - 5GMSd AF provides: - Endpoint of content steering service at M4d - Base URLs of provisioned 5GMSd AS service locations at M4d - Information included in Service Access Information advertised via M8d
Step 1: Energy Information Configuration - 5GMS Application Provider provisions 5GMS AF via M1d - Includes Provisioning Session resource and Energy Information exposure configuration for Energy Information AF - Contains Application Identifier for filtering Energy information reports - Flag indicating Energy Information Collector NOT instantiated in UE
Steps 4a-4c: Initial Content Steering Configuration - 4a: Energy Information AF processes NF and AS Energy Information reports (moved from step 10 in baseline; no UE interaction expected) - 4b: 5GMS AF makes content steering prioritization decision considering: - Load on available service locations - Energy-related information from step 4a - Configures selected service location with higher priority in steering instructions - 4c: 5GMSd AF provides content steering configuration via M3d to 5GMSd AS content steering service
Steps 15-17: Network Energy Reporting - 15: EIF submits Network Energy Information report to Energy Information AF via E12 - 16: 5GMSd AS submits AS Energy Information report to Energy Information AF via E3 - 17: Energy Information AF processes reports and provides to 5GMSd AF
Steps 17a-17b: Content Steering Update (replaces baseline steps 18-25) - 17a: 5GMSd AF makes content steering prioritization decision based on energy-related information - 17b: 5GMSd AF provides updated content steering configuration via M3d
Steps 20, 20a, 20b: Session-based Updates - Similar to steps 4a-4c, repeated during media streaming session
Steps 28a/28a bis: Media Player Entry Conditioning - 5GMSd AS conditions Media Player Entry to add content steering service endpoint (if not already added by Application Provider)
Step 28b: Steering Instruction Request - Media Player requests steering instruction from content steering service - No specific energy information in steering instructions themselves
Step 29: Service Operation Point Selection - Media Stream Handler selects based on steering instruction
Step 30/30bis: Transport Session Establishment - Media Player establishes new transport session at M4d for acquiring media from selected Service Location (per content steering instruction)
Step 37/37bis: Media Content Request - Media Player requests media content from selected 5GMSd AS service location
Identified Gaps in Rel-19 Specifications:
Step 0: Ability for 5GMSd Application Provider to declare in Content Hosting Configuration that service locations are eligible for content steering
Step 0: Ability for 5GMSd AF to nominate endpoint address of content steering service instantiated in 5GMSd AS
Step 1: Ability to indicate Energy Information Collector NOT instantiated in UE
Steps 4b, 20a: Functionality for 5GMSd AF to make content steering decision incorporating energy-related information from Energy Information AF
Steps 4c, 20b: Ability for 5GMSd AF to provide content steering configuration to 5GMSd AS content steering service via M3d
Steps 28a, 28a bis: Functionality for 5GMSd AS to condition Media Player Entry to add content steering service endpoint address
Editor's Note: Additional gap regarding "steering request" to be explained
New Stage 2 Specification for Energy Information AF:
Editor's Note: Specific provisioning requirements TBD
Energy-related information reporting by 5GMSd AS via E3 supporting aggregations:
Changes to TS 26.501:
Inclusion of content steering service in 5GMSd AS as part of Energy Information AF instantiation
Documentation of content steering based on energy-related information in Energy Information AF procedures (per clause 7.12.6), either:
Changes to TS 26.506:
Editor's Note: To be determined
New Stage 3 Specification for Energy Information AF:
Editor's Note: Specific provisioning requirements TBD
Energy-related information reporting by 5GMSd AS supporting same aggregations as Stage 2
Changes to TS 26.510:
New clauses specifying extensions to procedures and service-based interfaces at E1, E3, and E12 reference points pertaining to 5GMS, regarding additional energy-related information from 5GMS AS and EIF for media streaming sessions enabling steering servers to select AS based on environmental impact
Step 1 (clause 7.12.6): New Energy Information Exposure Configuration resource (clauses 5.2 and 8) identifying which applications fall within scope
Content Hosting Configuration extensions (clauses 5.2.8 and 8.8.3.1):
Changes to TS 26.512:
Extensions (as needed) to procedures and service-based interfaces at M1d, E3, and M5d reference points, particularly regarding additional energy-related information from 5GMS AS for media streaming sessions
Editor's Note: Specifics TBD
Changes to TS 26.113:
Editor's Note: To be determined
Candidate Solution Proposal:
New mechanism enabling 5GMSd Application Providers to steer 5GMSd Client towards service location with lowest environmental impact based on:
Information provided by EIF and 5GMSd AS to Energy Information AF (included in 5GMSd AF)
Standardized interfaces between 5GMSd AF and 5GMSd Application Provider:
Allows Application Provider to provision content steering mechanism with goal of reducing environmental impact of downlink media streaming
Dynamic steering by 5GMSd AS (acting as content steering server):
Benefits: - Optimizes energy efficiency of multimedia content delivery - Contributes to reducing environmental footprint of media streaming services - Applies to any 5GMSd Application Provider delivering content via 5GMSd System - Integrates naturally into existing adaptive streaming architectures (MPEG-DASH, HLS)
Implementation Characteristics: - No impact on UE (leverages existing adaptive streaming protocol mechanisms) - No impact on data plane - Service location selection achieved by prioritizing desired location in steering instructions - Compatible with legacy devices
Solution #11 added to table mapping, addressing KI#5 (Media Application Server Energy management).
Steps 10a to 10d added to baseline procedures (specific details not provided in change markings).
[FS_Energy_Ph2_MED] Merge of CRs agreed during MBS SWG post 134-e and before
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.
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)
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
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
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
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
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
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
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
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
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)
[FS_Energy_Ph2_MED] Recommendations
This CR proposes normative work and potential further study following the Feasibility Study on energy-related enhancements for media services (5GMS and RTC systems).
The study identified that normative work on Key Issue #1 (Energy-related information exposure) is premature because: - The Energy Information Function (EIF) defined in TS 23.501 is not yet fully specified - Capabilities and interfaces of EIF need complete definition first
A phased approach is recommended: 1. Wait for complete EIF definition and TR 22.883 completion 2. Update the TR with: - Detailed EIF interaction specifications - New Key Issues for unaddressed questions - New Key Issues from TR 22.883 use cases 3. Then initiate normative work
The study will address new use cases on: - Information exposure of network energy characteristics (consumption, supply mix, carbon footprint, capacity, availability) - Dynamic service adjustments based on energy characteristics - Security, charging, and privacy aspects
Normative definition and specification of an energy architecture based on Solution #5, instantiated in both 5GMS and RTC Systems.
Define generic architecture and procedures for Energy Information AF and Energy Information Collector, covering: - E1 reference point: Provisioning the Energy Information AF - E3 reference point: AS Energy Reports subscription/exposure from Application Servers to Energy Information AF (with baseline parameters) - E5 reference point: Aggregated network energy information exposure from Energy Information AF to Energy Information Collector in UE (with baseline parameters) - E6 reference point: Aggregated energy information exposure from Energy Information Collector to UE Application (with baseline parameters)
Specify network APIs for: - Energy Information AF and Energy Information Collector at E1, E3, E5 - Client API exposed by Energy Information Collector to Application at E6
New clauses defining: - Architecture instantiation in 5G Media Streaming System - Collaboration scenarios extending generic procedures for 5GMS-specific Use Cases
New clauses defining: - Architecture instantiation in RTC System - Collaboration scenarios for RTC-specific Use Cases - Note: Generic scenarios from TS 26.501 may be referenced
Specify: - Procedure and interface extensions at E1, E3, E5 for 5GMS System - Example: 5GMS AS extracting/exposing energy information from DASH media segments - Client API extensions at M6 reference point (Energy Information Collector in Media Session Handler to 5GMS-Aware Application)
Specify: - Procedure and interface extensions at E1, E3, E5 for RTC System - Example: RTC AS extracting/exposing energy information from RTP header extensions - Client API extensions at RTC-6 reference point (Energy Information Collector in Media Session Handler to RTC-Aware Application)
The CR establishes a comprehensive framework for energy-aware media services spanning: - Generic architecture applicable to multiple systems - System-specific instantiations (5GMS and RTC) - Protocol-level specifications - Client-side API definitions
[FS_Energy_Ph2_MED] Next steps
The Study on Media Energy Consumption Exposure and Evaluation Framework Phase 2 (FS_Energy_Ph2_MED) is facing schedule challenges. The study was originally planned for completion at SA4#135, but significant work remains outstanding.
The original plan required Stage 2 WID agreement at SA4#135 to allow: - Two SA meetings (SA#112 June 2026, SA#113 September 2026) for Stage 2 completion - Two additional meetings (SA#114 December 2026, SA#115 March 2027) for Stage 3 finalization - Meeting the Release 20 Stage 3 freeze deadline (SA#115 March 2027)
Phase 1 of TR 26.942 recommended normative work for Key Issue #1 (Energy-Related Information Exposure) based on: - Energy Information Function (EIF) within 5G System (TS 23.501) - Two new entities: Energy Information Application Function (EIAF) and Energy Information Collector (EIC)
To enable meaningful Stage 2 work, the following key points must be addressed:
The following tasks appear very challenging to complete during SA4#135: - Agree on candidate solutions addressing the key points listed in Section 2 - Reach consensus on conclusions, including candidate solution selection - Reach consensus on recommendations listing proposed normative changes - Agree on Stage 2 WID
Conclusion: The work plan requires adaptation.
Postpone FS_Energy_Ph2_MED completion from SA4#135 to SA4#136, providing two additional SA4 meetings to finalize the study. This approach would: - Complete the study at SA4#136 - Address Stage 2 in a single meeting (SA#136) - Complete Stage 3 in two meetings - Still meet Rel-20 Stage 2 freeze and address Release 20 SA1 requirements
To make this feasible:
Once consensus is reached on this proposal, the related workplan will be updated accordingly.
[FS_Energy_Ph2_MED] Conclusions update
This CR updates the conclusions section (Clause 8) of TR 26.942 to incorporate Phase 2 additions and modifications related to energy consumption in media delivery systems. Specifically, it adds conclusion sections for Key Issues 4, 5, and 6 which were previously incomplete.
The CR adds three new conclusion subclauses with placeholder content:
Topic: Energy-related configuration by the Application Service Provider for media delivery services
Topic: Media Application Server Energy management
Topic: Client-driven management of media delivery service energy optimisation
The CR does not modify existing conclusion sections for: - Key Issue #1: Energy-related information exposure (Clause 8.2) - Key Issue #2: Energy-related monitoring and measurement (Clause 8.3) - Key Issue #3: Evaluation framework (Clause 8.4)
The CR ensures structural completeness of the conclusions section by adding placeholders for Phase 2 Key Issues. These sections will be populated as candidate solutions for Key Issues 4, 5, and 6 are developed and agreed upon during the study.
Phase 2 work on Key Issues 4, 5, and 6 would not be properly reflected in the TR's conclusions structure, potentially causing organizational issues as solutions are developed.
[FS_Energy_ph2_MED] Work Plan v0.4
This document presents revision 0.4 of the Work Plan for the Study Item "Study on Media Energy Consumption Exposure and Evaluation Framework phase 2" (FS_Energy_ph2_MED). The study was approved at SA4#132 (S4-251182) and SA#108 (SP-250636).
The study addresses incomplete work from TR 26.942 v2.0.0 due to dependencies on other 3GPP groups. The phase 2 study aims to: - Incorporate new information from completed 3GPP work - Address key issues identified but not resolved in phase 1 - Propose new potential solutions
The study addresses new Rel-20 requirements in the media delivery context:
Clause 6.15a.2 - Energy-related information as service criterion: - Media delivery performance degradation (QoS adjustment, bit rate modification, deferring Background Data Transfers) in response to network energy supply mix changes or energy rationing - Per-UE energy saving actions based on subscription policies, including blocking media delivery - Mechanisms to assist Media Application Providers in identifying UEs for performance degradation and energy saving actions - All subject to operator policy, regulatory requirements, and user consent
Clause 6.15a.5 - Energy-related information exposure: - Exposure to UEs and authorized third parties over specific time periods - Network energy consumption and equivalent CO2e emissions for overall media delivery service and individual application data flows - Subject to operator policy, regulatory requirements, and user consent
Update or develop existing potential solutions incorporating new elements from TS 23.501, TS 23.502, and TS 23.503, including: - Energy Information Function (EIF) - Efficient energy use mechanisms - Energy saving items
Propose solutions for key issues on: - Energy-related monitoring and measurement during media consumption - Evaluation frameworks without identified normative work
a. Energy-related configuration by Media Application Service Provider: - How ASPs can configure energy-related information collection and exposure
b. AS Energy Management: - How 5GMS AS (and RTC System equivalent functions) react to energy-related information from the network via Energy Information AF instantiated in 5GMS AF and/or Energy Information Collector
c. Client Energy Management: - How 5GMS Client (and RTC System equivalent functions) react to network-shared energy-related information - Leverage existing QoS optimization mechanisms in RTC/5GMS for energy efficiency optimization
Original Plan: Completion by March 2026 (SA#111)
Revised Plan: Completion postponed to June 2026 (SA#112)
Rationale: - Original timeline too ambitious for two SA4 meetings - Additional two SA4 meetings provided - Addresses Rel-20 SA1 requirements while respecting Rel-20 Stage 2 freeze - Stage 2 addressed in single meeting, Stage 3 in two meetings
Key Decisions to Enable Revised Timeline: - No new candidate solutions accepted after SA4#135 - Consensus on Stage 2 draft WID during SA4#135-bis e-meeting - Begin Stage 2 Technical Specification work before WID approval at SA#112 by submitting discussion papers to SA4#135-bis and/or SA4#136 - Early drafts of TS 26.nnn V0.0.1/V0.0.2 based on agreed baseline of Solution 5
The document proposes the above Work Plan for SA4 team consideration.
[FS_Energy_Ph2_MED] Let's get friends with Greening of Streaming
This contribution documents the outreach and collaboration established between 3GPP SA4 and the Greening of Streaming (GoS) organization regarding energy efficiency in media streaming. The source contacted GoS to create awareness of the ongoing "energy for media" work in 3GPP, particularly in the context of 6G where sustainability is a core KPI.
A call was held on December 9 between the source, the study rapporteur, and Benjamin Schwarz (GoS President) to exchange information about respective activities.
The discussion identified that: - GoS focuses on streaming applications - 3GPP focuses on telco aspects not covered by GoS - Overlap exists in CDN and streaming delivery areas - Work is complementary rather than duplicative
Quick consultation with SA4 and MBS leadership confirmed support: - MBS chair endorsed the workshop concept - SA4 chair agreed, noting no need to escalate to SA plenary - MBS chair indicated GoS may become a formal liaison to 3GPP - 5G-MAG offered to organize the event
Engineers, architects, researchers, and standards contributors working on sustainable media delivery implementation
The document proposes to: - Take this information into account - Inform other 3GPP Working Groups about the event - Encourage participation and presentation proposals from interested organizations
[FS_Energy_Ph2_MED]: Solution for KI1 and KI4 for collecting and exposing Energy-Related information to authorized 3rd parties instantiating Media Application Service Energy Metrics configuration
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.
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
Four distinct energy exposing modes are defined, each with a dedicated metrics scheme:
All four schemes share an identical controlled vocabulary of metrics. Multiple schemes can be provisioned simultaneously under the same Provisioning Session.
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
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
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 |
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
The solution is applicable to all collaboration scenarios requiring access to Media Application Service EoS metrics.
This candidate solution enables energy-related information collection and exposure by:
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.
[FS_Energy_Ph2_MED]: Solution for KI1 and KI4 for collecting and exposing to authorized 3rd parties Media Application Service Energy Metrics configuration instantiation
CR Number: 0018 rev 2
Version: 19.0.0
Work Item: FS_Energy_Ph2_MED
Category: B (addition of feature)
Release: Rel-20
This CR proposes Solution #12 for Key Issue #1 (energy-related collection) and Key Issue #4 (exposure to authorized 3rd parties) for Media Application Service Energy Metrics.
This Candidate Solution builds upon Solution #5 (clause 7.6.2.4) for the architecture of energy-related information collection and exposure. Key differentiators:
The solution instantiates the reference architecture with the following key functions:
The solution defines/utilizes the following reference points:
Generated periodically by Application Server at E3, includes: - Sample timestamp and duration - Application Server instance identification - Metrics reporting configuration ID - Application Service location objects with contribution/renewable ratios - Media delivery session identifier - Session energy consumption and carbon emission - Downlink/uplink data volumes (per session and global) - Global energy consumption (uplink/downlink) - Media component energy objects (per MIME type with energy, carbon, data volumes)
Generated by Energy Information AF describing Mobile Network energy consumption: - Sample timestamp and duration - Metrics reporting configuration ID - Media delivery session identifier - Session slice energy and carbon emission - Session energy and carbon emission - Media component energy objects - RAN energy and carbon emission - Core Network (UPF) energy and carbon emission - RAN and Core Network renewable ratios
Generated by Energy Information AF, aggregates information from mobile network and Media AS: - Report timestamp - Aggregated information based on metrics reporting scheme, sample mode, and reporting scope
Generated by Energy Information Collector describing UE, Mobile network, and AS energy consumption: - Report timestamp - Aggregated Mobile Network and Media AS Energy Report - Sample timestamp and duration - Media delivery session identifier - Session energy and carbon emission - Network access energy ratio - Non-display and display playback energy ratios - Media component energy objects with UE-specific metrics
Collection of metrics reports exposed by Data Collection AF to subscribing event consumers on per-UE basis (details FFS)
Generated by Energy Information AF on per-UE basis for Media Application Provider (details FFS)
The solution defines comprehensive procedures including:
Energy Information AF subscribes to EIF for Core Network energy information
Session Establishment:
Configuration retrieval by Media AS and Energy Information Collector
Metrics Collection Loop:
Exposure to UE, Media Application Provider, and optionally Data Collection AF
Optional Exposure:
Additional detailed procedures mapping this solution on top of Solution #5: - Energy Information Collection provisioning - Media delivery session initiation with energy collection - Periodic energy information reporting during media streaming - Service Operation Point selection based on energy information - Dynamic subscription updates based on Service Data Flow changes
Identifies that Release-19 Metrics Reporting Configuration: - Provides generic metrics reporting framework - Does not enable standardized, entity-aware provisioning of energy metrics reporting
Proposes requirements for: - Media AF to support Media Application Service Energy Metrics Reporting Configuration - Energy Information AF to collect, process, and report energy information from multiple sources - Energy Information Collector to fetch, process, and propagate energy metrics - Defining energy metrics reports and events at new reference points
Scope for stage 3 specifications:
The Candidate Solution: - Describes how energy-related information is collected, estimated, and exposed by 5G System - Supports network optimization, energy-aware service adaptation, user empowerment, and energy/carbon-emission attribution - Reuses and extends existing 5G Metrics Reporting mechanism with energy-related metrics - Enables collection and exposure of carbon intensity, energy consumption, renewable source ratio, and contribution ratio for Media Application Services - Builds on Solution #5 while keeping M1 provisioning mechanism and adapting procedures for energy information collection from AS and Network
[FS_Energy_Ph2_MED] Solution for KI#5 and#6 Client-based Media Application Server selection
This CR proposes Solution #11(b) addressing: - Key Issue #5: Media Application Server Energy management - Key Issue #6: Client-driven management of media delivery service energy optimisation
New normative references added: - [36300]: TS 36.300 - E-UTRA and E-UTRAN Overall description - [28558]: TS 28.558 - UE level measurements for 5G system - [23288]: TS 23.288 - Architecture enhancements for network data analytics services
The solution enables Media AS service endpoint reselection during an active media delivery session based on: - UE application QoE requirements (resolution, bit rate, etc.) - Energy-related characteristics of individual Media AS service locations (load, energy consumption, QoE metrics)
Energy Information AF (EIAF): - Instantiated in Media AF - Evaluates energy consumption and efficiency for ongoing media services - Uses energy-related parameters provisioned via M1 - Provides energy-related indications/recommendations to Media AF when thresholds are crossed - Correlates QoE information with service-level and media-level energy information
Energy Information Collector (EIC): - Instantiated in Media Session Handler of UE Media Client - Receives information via E5 for correlation with QoS/service information - Provides feedback to Media Application Provider via M8 - Does not directly influence media adaptation decisions (controlled by Media AF)
The solution reuses the Application Server (AS) Energy Report for consistent reporting:
Reused elements:
- Energy consumption and efficiency indicators → mapped to EnergyConsumptionValue and EnergyEfficiencyMetric
- Reporting scope and aggregation level → determines EnergyMeasurementScope
- Reporting triggers and reasons → reflected in EnergyReportingReason
- Reporting timing and validity → reused for EnergyMeasurementTime, EnergyInformationTimestamp, EnergyReportValidityTime
The Energy Information AF combines AS Energy Report information with additional context (QoS degradation, QoE metrics from OAM, policy constraints from M1) to derive consolidated energy-related information conveyed via E5.
Parameters provisioned to Energy Information AF:
| Parameter | Description | |-----------|-------------| | Energy Policy identifier | Identifies the energy policy instance | | Energy monitoring Configuration scope | Scope and granularity (per service/session/component) | | Energy reporting configuration | Reporting conditions (frequency, threshold triggers) | | Energy thresholds | Threshold values for consumption/efficiency | | Energy adaptation guidance | Recommended energy-aware adaptation actions (codec selection, rate reduction, etc.) | | Energy suspension policy | Conditions for suspending media components/sessions | | Energy recovery policy | Conditions permitting increased energy consumption | | Energy reporting recipient | Entities receiving energy reports/notifications | | Service energy profile | Energy efficiency profile for service/application | | Energy Measurement Time | Time/interval for measurements | | Energy Report Validity Time | Validity period for reported information |
Parameters conveyed from Energy Information AF to Energy Information Collector:
| Parameter | Description | |-----------|-------------| | Energy Policy identifier | Identifies applicable energy policy | | Application Identifier | Service/application/media session group | | Energy measurement scope | Scope of reported information | | Energy measurement time | Time/interval of measurement | | Energy threshold status | Whether thresholds crossed | | Energy budget status | Current budget status | | Energy adaptation status | Whether adaptation actions applied | | Energy reporting reason | Reason for reporting | | EnergyReportValidity time | Validity period | | EnergyInformationTimestamp | Generation timestamp | | Energy Adaptation Recommendation | Recommended energy-related actions | | EnergyConsumptionValue | Measured/estimated consumption |
Follows TS 38.300 Clause 21.2.1 (management-based QMC activation):
Identified gaps in Release 19 specifications (in addition to Solution #5 gaps):
Beyond Solution #5 normative work, additional changes to TS 26.512:
a) Extensions to M11 procedures and service-based interfaces for: - Media Access Function reporting initial QoE metrics to Media Session Handler for ongoing sessions
b) Extensions to M11 procedures and service-based interfaces for: - Energy Information AF and Media AF mapping UEs to Media AS service locations based on base URL, UE-related metrics, and AS Energy Report information
The solution describes: - Exposure of energy-related information about different service locations from Media AS to Media AF - Exposure of this information to UE application during media delivery session - Dynamic reselection of Media AS service locations during ongoing M4 sessions based on: - UE application QoE requirements - Energy-related characteristics from Media AS service locations - Mechanism enabling Media Client to dynamically select most energy-efficient service location - Interaction between Energy Information AF and Media Client for joint selection based on network and UE energy information
Applicability: Downlink media sessions, uplink media sessions, and RTC communication sessions
Key Factors: 1. Energy efficiency metrics from Network Operator (power consumption profiles, energy performance indicators from Media AS service locations)
Approach: Optimizes energy consumption of multimedia content delivery while maintaining service quality, operating entirely within network layer using standard adaptive streaming frameworks for compatibility with existing ecosystems.
[FS_Energy_Ph2_MED] Solution for KI #6 Client-driven management of media delivery service energy optimisation
This CR adds Solution #12 addressing Key Issue #6: "Client-driven management of media delivery service energy optimisation". The solution enables the Media AF to manage energy-saving operations that may cause QoS and QoE degradation through coordination between the 5GC, Media Application Providers, and UE.
The solution defines three interaction models between AF and NWDAF:
Nnef_* APIs (TS 29.522)NEF interacts with NWDAF on AF's behalf
Via PCF (N5 reference point):
Npcf_PolicyAuthorization (TS 29.514)PCF passes results back to AF
Direct service-based interaction:
Nnwdaf servicesNnwdaf_AnalyticsInfo_Request/SubscribeSmf_EventExposure serviceNote: No direct AF-SMF interface exists in 3GPP specifications.
Energy Policy Provisioning: - Media Application Provider provisions energy policies in advance - Policies aligned with contracts (e.g., green streaming agreements) - Define acceptable QoS/QoE ranges for media delivery
Energy Saving Triggers: - 5G Core triggers: Network decides to reduce QoS (e.g., bandwidth allocation) - Media Application Provider triggers: Based on cloud provider contracts or resource status - Mix of real-time triggering and pre-provisioned policies
User Tolerance Assessment: - Energy Information AF assesses QoE impact when triggered - Compares requested QoE with predefined thresholds - May query SMF for user subscription QoE levels (from UDM) - If within agreed levels → proceed without approval (collect feedback) - If exceeds levels → request user approval via notification
UE QoE Control: - Energy Information Client in Media Session Handler assesses status - Determines if Media-aware Application can tolerate degradation - Manages QoE to stay above pre-defined thresholds
Energy Information AF Responsibilities: - Validates Energy Information Exposure Specifications - Subscribes to NF Energy Information from EIF (E12) - Subscribes to AS Energy Information from Application Server (E3) - Collates and exposes Network Energy Information to Energy Information Collector (E5) - Interacts with NWDAF via NEF (N33), PCF (N5), or direct service-based interface
Energy Information Collector Responsibilities: - Acquires collection configuration from Energy Information AF - Collects energy information at different granularities (UE, PDU Session, QoS flow) - Per TS 23.501 clause 5.51.2.3
Provisioned by Media Application Provider to guide Media AF behavior:
Conveyed by Media AF to Media Session Handler upon QoS degradation:
Based on TS 38.300 clause 21.2.1:
measConfigAppLayerContainer in RRCReconfiguration to UEMeasurementReportAppLayer to gNodeB5GC-Initiated Trigger Process (Step 21 details): 1. UDM provisions "QoE reduction authorization" in user subscription (TS 23.502 clause 5.2.3.1) 2. SMF selects specific UE/application for QoS reduction 3. SMF subscribes to Observed Service Experience analytics from NWDAF with candidate QoS parameter sets 4. NWDAF provides predicted QoE to SMF 5. SMF optionally queries UDM for "QoE reduction authorization" 6. SMF sends energy saving trigger to AF with QoE ranges
Media Application Provider Trigger (Step 10a): - Provider decides to reduce AS energy consumption (e.g., during peak hours 12:00-14:00) - Can be pre-provisioned schedule or real-time trigger - Trigger contains possible QoE ranges
EIF to EIAF Request (Step 10b/9): - EIF informs EIAF via E12 to request UE Media Client QoE degradation - Due to network and/or UE energy saving
EIAF Activation (Step 10/20): - EIAF receives request and activates energy saving mode - Determines which UEs under control to activate
QoE Reduction Request (Steps 18/22): - EIAF requests subset of Media Clients to reduce QoE via E5 - Based on comparison with pre-defined ASP standards
Current QoE Reporting (Steps 13/22a): - Media Session Handler requests current QoE metrics from Media Access Function (M11)
UE Decision Point (Step 14/23):
If UE does not agree: - Does not activate buffer control - Session continues unmodified - Optional notification to Media AF of preference
If UE agrees (Steps 25-31): 25. Media Session Handler instructs Media Access Function to activate buffer control 26. Media Access Function activates buffer control 27. Ongoing session requires modification 28. Media Session Handler requests Media AF to modify session (new dynamic QoS policy at M5) 29/24. Media AF modifies session and acknowledges 30. Media Session Handler establishes session with new QoE 31. Media continues with possibly reduced QoE
Identified gaps requiring specification:
Proposed normative work in TS 26.512:
Specific to 5G Media Streaming System sessions
Reference Point M5 Extensions:
Contrast with Alternate QoS Profile Feature: - This solution differs from TS 23.501 clause 5.7.1.2a Alternate QoS Profile feature - Alternate QoS Profile: Network (NG-RAN) dynamically adapts QoS for network energy saving - Solution #12: Client-driven approach with user consent and application-level adaptation
Solution Benefits: - Dynamic coordination between Media AF, 5GC, Media Application Provider, and UE - User-aware energy-saving decisions based on QoE tolerance - Joint network-UE optimization of energy while maintaining service continuity - Proactive QoE management before quality deteriorates
[FS_Energy_Ph2_MED] Solution for KI#5 Optimization of media sessions based on UE energy consumption
This CR proposes a solution for optimizing media sessions based on UE energy consumption during mobility scenarios. The solution addresses Key Issue #6 (previously #5) by leveraging energy-related information from the network's Energy Information Function (EIF) to help Application Servers optimize media delivery in an energy-efficient manner.
The solution targets scenarios where a user wishes to consume media content (e.g., watching a 90-minute football match) during mobility with limited battery capacity. The system optimizes media delivery QoE based on energy consumption predictions to enable completion of the media session while conserving both UE and network energy.
The solution defines an architecture where the 5G Core (5GC) plays a central role by providing:
The solution defines a three-phase process:
Phase 1: UE Energy Information Collection - Media-aware Application initiates media delivery session during mobility - Energy Information Collector (EIC) instantiated in Media Session Handler gathers energy consumption data - Context created including energy consumption prediction related to UE mobility (considering cell edge vs. center positioning)
Phase 2: Codec Adaptation Based on Energy Consumption and Mobility - Media Session Handler requests predicted energy consumption from Energy Information AF - Energy Information AF subscribes to EIF for energy consumption data from 5GC (per TS 23.501 clause 5.51) - NWDAF analytics engine analyzes UE mobility pattern to predict energy consumption - Media Session Handler selects energy-efficient media rendition/encoding parameters considering: - Battery level - Mobility pattern - Media content type and duration - Adaptation options include: - Downlink: Selection between Adaptation Sets (MPEG-DASH) at different bitrates/resolutions - Uplink: Adjustment of encoding bitrate - RTC: Request to RTC AS for transcoding
Phase 3: Media Session Update and Delivery - Media Session Handler informs Media Access Function of selected media encoding - Media delivered using optimal parameters balancing energy efficiency and QoE
The call flow includes 22 steps:
Initial Setup (Steps 1-9): - Media-aware Application requests media delivery session - Media Session Handler coordinates with Media Access Function - Transport connection established with Media AS - Baseline energy-related information collection procedures
Energy Management Initialization (Steps 10-13): - Media-aware Application initiates energy information collection considering mobility - Energy Information Collector registers/subscribes with Energy Information AF - Energy Information AF subscribes to UE mobility events from AMF
Parallel Media Delivery and Adaptation (Steps 14-22): - Media delivery starts - AMF notifies Energy Information AF of mobility events (handovers, access changes) - EIF returns network-level energy information to Energy Information AF - Energy Information AF reports network energy exposure and mobility-driven estimates to Energy Information Collector - Media Session Handler processes inputs and decides on adaptation - Media Session Handler selects appropriate media parameters - Media Access Function informed of new parameters - Adapted media delivery continues
Five key gaps identified requiring normative work:
Proposed normative work in TS 26.512:
New clauses specifying: - Extensions to procedures and service-based interfaces at reference point E5 for Energy Information Collector subscription with Energy Information AF regarding mobility-tied energy estimations - Extensions to procedures and service-based interfaces at reference point M5 for Energy Information AF reporting of network energy exposure and mobility-driven estimates to Energy Information Collector
The solution enables UE optimization of media delivery session energy consumption during mobility by: - Leveraging Energy Information AF and EIF collaboration with 5G Core and Media Application Provider - Utilizing 5GC service-based interfaces for exchanging energy-related information, mobility events, and session parameters - Enabling Media Delivery System to react dynamically to UE mobility context and network energy state - Maintaining high-quality media experience while minimizing energy consumption during transitions across cells, RATs, or network conditions
[FS_Energy_Ph2_MED] Solution for Key #6 on Client-driven switching between multipath and single path media delivery based on energy information
This CR proposes a solution for Key Issue #6 addressing client-driven management of media delivery service energy optimization, specifically focusing on switching between multipath and single-path media delivery based on energy information from the network.
The candidate solution addresses Key Issue #6 on client-driven switching between multipath and single-path transport sessions based on network energy consumption information. The solution is mapped in Table 7.1-1 showing the relationship between solutions and key issues.
The solution introduces switching between: - Multipath transport session: potentially over multiple access networks - Single-path session: based on energy consumption information from network to UE
Two operational modes are supported: - Transparent to application layer (hidden behind virtual tunnel interface per TS 23.501 clause 5.32.2) - Explicitly indicated to Media Access Function by Media Session Handler or Media-Aware Application (per TS 23.512 clause 13.2.4)
Figure 7.X.2.13-1 depicts the reference architecture based on the generalized Media Delivery architecture (TS 26.501 clause 4.1.2):
Network Side: - Energy Information Function (EIF): Collects energy consumption information per TS 23.501 clause 5.51.2.2 - Energy Information AF: Instantiated in Media AF, receives information from EIF
UE Side: - Energy Information Collector: Instantiated in Media Session Handler of Media Client - Media-Aware Application: Makes switching decisions - Media Access Function: Implements transport session changes
Key Reference Points: - E5: Energy information delivery from Energy Information AF to Energy Information Collector - M4: Media flow exchange and switching decision interface
No new reference points are defined; existing architecture is reused.
Table 7.X.25.21-1 defines the baseline information structure: - Access network energy cost information: Array of descriptors providing network energy cost for delivering application flows over specific access networks for the current Media Delivery session
This enables UE to determine relative cost of establishing transport connections over different available access networks.
Figure 7.X.36-1 details the complete procedure with the following key steps:
NOTE 2: Network Energy Information includes access network energy cost information per clause 7.X.5.1
Media delivery session established between UE and network entities, potentially using multipath transport (TR 26.804 clause 5.18.4)
Media Session Handler configures Energy Information Collector to subscribe to energy events via internal client API
Energy Information Collector subscribes to receive energy events from Energy Information AF over E5
M4 media flows exchanged between Media Access Function and Media AS
EIF provides NF energy information to Energy Information AF per TS 23.501 clause 5.51.2.2
May be relayed via NEF if Media AF is untrusted
Energy Information AF forwards energy consumption information to Energy Information Collector over E5
Energy Information Collector forwards energy information to Media Session Handler via internal client API
UE internal energy consumption to support multipath over multiple access networks
Media Session Handler updates transport session parameters per TS 26.512 clause 13.2.4 (if needed)
Media Access Function applies updated configuration to media delivery transport session
Media Access Function and Media AS switch to new transport session for M4 application flows
The solution identifies gaps beyond the baseline procedure (clause 7.6.4):
Additional Gaps for This Solution: - Energy Information AF must acquire per-access network energy cost information (clause 7.X.5.1) - Energy Information AF must include per-access network energy cost in Network Energy Information report to UE - Media Aware Application and Media Session Handler must implement decision logic for switching between single-path and multi-path based on received Network Energy Information
Beyond baseline normative changes in clause 7.6.5, the following additional normative work is proposed:
[FS_Energy_Ph2_MED] Solution for KI4 and KI6: Media service level degradation based on accumulated energy consumption
This CR proposes a solution for Key Issue 4 (Energy-related configuration by ASP) and Key Issue 6 (Client-driven management of media delivery service energy optimization) by introducing energy event-driven media service level degradation based on accumulated energy consumption.
Key information elements include: - External reference: Unique identifier for UE Media Client selection - Names/Descriptions: Multilingual human-readable information - Granularity: Scope of energy measurement (per-UE, per-PDU session, per-QoS flow, per-slice, or AS) - Accounting period: Time period for continuous energy monitoring (e.g., session, hour, day) - Client subscription permissions: Flag for Energy-driven Service Level Change Event notifications - Energy segments: List of segments with: - Segment range (lower/upper thresholds) - Applicable QoS parameters (e.g., degraded bit rate) - Applicable Policy Template identifier (optional) - AS Energy Policy parameters (optional, for AS granularity)
New event type containing: - Current Energy Segment status: Details of currently applied segment (unit, current usage, range) - Undegraded Policy Template/bit rate: Performance achievable if energy situation improves - Energy-degraded Policy Template/bit rate: Current degraded performance due to energy impacts - Predicted duration/end time: Optional timing information for degradation - Scope of degradation: Indicates whether degradation applies to UE/user, cells, service location, or network - Degradation cause: Network-to-device transmission or server processing
Upon receiving Energy-driven Service Level Change Event, Media Client can: 1. Continue with degradation: Adapt media delivery to stay within degraded service level 2. Upgrade service level: Spend energy credits or purchase mechanism 3. Re-select Energy Policy: Change to different policy (e.g., from "green" to "less green") 4. Other actions: Including session termination
16-17. Media-Aware Application selects Media Entry Point based on Energy Policy Status 18-19. Media Stream Handler establishes transport and requests Media Entry Point 20-24. Optional Service Operation Point selection and Service Data Flow updates 25. Media delivered between Media Stream Handler and Media AS
29-30. EIF and Media AS expose energy information reports to Energy Information AF 31. Energy Information AF processes reports, checks Energy Policy, detects segment changes 31a-d. Optional Dynamic Policy change triggered and Service Level Change Event generated 32. Network Energy Information report with Energy Policy status exposed to Energy Information Collector 35-36. Service Level Change Events shared with Media Session Handler and Media-Aware Application 37a-d. UE decides on energy-degradation response, results reported back through chain