Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 26.942  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   5…   6…   7…   7.3…   7.4…   7.5…   7.6…   7.7…   7.8…   7.9…   7.10…   8…   9…

 

8  Conclusionsp. 66

8.1  Generalp. 66

The present document highlights ongoing challenges in accurately estimating and reporting energy consumption of media delivery in the 5G System, including mobile network as well as end-user devices. The main difficulties are:
  • Data accuracy: Difficulty in obtaining precise power data at the hardware level and in reporting these data preserving privacy.
  • Energy attribution: Challenges in assigning energy usage to specific data throughput across multiple stakeholders as expected by regulators and protocols, complicated by non-linear relationships between energy and data.
  • Regulatory pressures: Legal requirements for net zero emissions necessitate clear energy allocation strategies, which can lead to disputes among network operators, service providers and consumers.
  • Measurement boundaries: Defining system boundaries for energy measurements affects responsibility and accountability.
Current assessments of energy use are often too coarse for effective policymaking or system design, and do not meet reporting standards set by the Greenhouse Gas Protocol (see clause 4.2.5) and regulatory bodies (see, for example, clause 4.2.8). The present document suggests that collecting fine-grained energy consumption data in real time could address these challenges and proposes a framework for future measurements.
Up

8.2  Conclusion for Key Issue #1 (Energy-related information exposure)p. 66

Five alternative Candidate Solutions addressing this Key Issue are documented:
  • Solution #4 in clause 7.5 proposes to extend the UE data collection, reporting and event exposure architecture defined in TS 26.531 such that the Direct Data Collection Client additionally collects and reports per-application UE energy-related information to the Data Collection AF.
  • Solution #5 in clause 7.6 proposes a new architecture and related procedures allowing energy-related information from the device and the network (including the AS) to be provided to a UE application during media consumption for exposure to the user with the definition of two new components, the Energy Information AF and the Energy Information Collector.
  • Solution #6 in clause 7.7 proposes to extend the MTSI UE QoE reporting mechanism with energy-related information
  • Solution #7 in clause 7.8 proposes an Energy Information Exposure Specification which represents the configuration of the Energy Information required to be exposed to a particular Application Service Provider.
  • Solution #9 in clause 7.10 describes an abstract UE energy-related information index. This information is abstracted such that it does not reveal any internal properties of the UE such as its battery capacity, battery discharge rate, etc.
The following aspects are concluded:
  • For exposure of end-to-end energy-related information to the network, the Direct Data Collection Client and Data Collection AF specified in TS 26.532 or MTSI UE QoE reporting specified in TS 26.114 would need to be extended to take into consideration UE energy-related information in addition of their existing data.
  • For exposure of end-to-end energy-related information to UE applications, two new entities and their associated interfaces would be required to provide energy-related information from the device, the network and other components of the Media Delivery system to a UE application: The Energy Information AF and the Energy Information Collector.
  • Definition of the Energy Information Exposure Specification is for further study.
  • No normative work is planned on the abstract UE energy-related information index.
There is consensus to address the above principles by the following normative work:
  1. Create a new stage-2 TS defining an energy architecture with the definition of two new entities, the Energy Information AF and the Energy Information Collector, using energy information available on Energy Information Function (EIF) allowing end-to-end energy-related information to be exposed to UE applications.
  2. Extend TS 26.501 and TS 26.506 to instantiate the above architecture in the media context.
  3. Address the relevant stage-3 aspects based on stage-2 work.
No consensus has been found on UE energy information exposed to the network. Hence, it is not recommended to pursue Solution #4 in clause 7.5 and Solution #6 in clause 7.7 with normative work.
Up

8.3  Conclusion for Key Issue #2 (Energy-related monitoring and measurement)p. 67

Three solutions addressing this Key Issue are documented:
  • Solution #3 in clause 7.4 describes how UE Operating Systems provide tools to assess the energy footprint of applications using system-wide metrics but lists some major limitations (information not publicly available on all UE OS, not limited to media consumption and with uncertain accuracy).
  • Solution #6 in clause 7.7 proposes a method leveraging energy consumption information to monitor and measure the way the media content is handled and delivered to the users, and to provide better Quality of Experience (QoE) for users.
  • Solution #8 in clause 7.9 proposes a new metric that allows to measure UE application energy consumption.
The following aspects are concluded:
  • On the device side, there is no consensus on defining a UE entity in the 5G System to manage the measurement of UE energy-related information. UE energy-related information can still be used on some UE Operating Systems providing these kinds of metrics, but because the metrics differ from one UE OS to another, there will not be normative work on UE energy-related information collection and metrics. A metric allowing UE application measurement thanks to MTD (Month-till-Date or Month-to-Date) is available, but its limitations (not including radio transmission, UE implementation-specifics and depending on conditions) make it seem not relevant for the scope of the study.
  • On the network side, the Energy Information Function (EIF) is defined in TS 23.501 to collect UE-related Energy Consumption information from Network Functions in the 5G Core, to calculate the Energy Consumption information at the granularity of UE, PDU Session and/or QoS Flow, and to expose the Energy Consumption information to the authorized consumer NF(s) (AF/NEF or another 5G Core NF). No additional information has been identified at this time in the context of media delivery or consumption.
In conclusion, there is no consensus at this time to initiate normative work addressing this Key Issue.
Up

8.4  Conclusion for Key Issue #3 (Evaluation framework)p. 68

Two different solutions addressing this Key Issue are documented:
  • Solution #1 in clause 7.2, based on work done by the French regulator, indicates how APIs available on some UE Operating Systems can be used to evaluate the impact of the use of some technologies on energy efficiency on devices in a lab.
  • Solution #2 in clause 7.3 proposes a method to evaluate the energy efficiency of the entire UE as a whole device, which is UE implementation-specific.
The following aspects are concluded:
  • No methodology has yet been identified allowing evaluation of the energy usage/savings of multimedia standards features and proposals, following best practices from these earlier characterization frameworks. The main difficulties are the lack of common UE metrics related to media consumption available on all mobile Operating Systems, and the lack of implementation of 5G network entities allowing to provide energy-related information from the network with sufficiently fine granularity.
  • It seems that Energy Information Function implementations are needed before being able to evaluate the energy usage/savings of a multimedia standards feature on a specific device in a lab.
In conclusion, there is no consensus at this time to initiate normative work addressing this Key Issue.
Up

Up   Top   ToC