Energy consumption estimation
By integrating AI/ML techniques to account for frequency, QoS, S-NSSAI/DNN, and CPU load, the energy consumption estimation in telecommunication networks is improved, leading to optimized energy efficiency and reduced energy footprint through enhanced policy decisions.
Patent Information
- Application Number
- PCT/SE2026/050326
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing methods for energy consumption estimation in telecommunication networks, such as those used by the Energy Information Function (EIF), lack accuracy due to not considering factors like frequency, QoS, S-NSSAI/DNN, and CPU load, leading to inadequate predictions for network functions like the Policy Control Function (PCF) to make efficient energy-saving policies.
Implementing artificial intelligence/machine learning techniques to enhance energy consumption estimation by considering frequency, QoS, S-NSSAI/DNN, and CPU load, allowing for more accurate predictions of energy consumption in network nodes like gNB and UPF, and using these predictions to inform policy decisions for energy efficiency.
Enhances the accuracy of energy consumption estimation, enabling more informed policy decisions by network functions, thereby optimizing energy efficiency and reducing the overall energy footprint of the 5G network.
Smart Images

Figure SE2026050326_12112026_PF_FP_ABST
Abstract
Description
ENERGY CONSUMPTION ESTIMATIONTECHNICAL FIELD
[0001] The present disclosure is related to computer-implemented methods and apparatus for enhanced energy consumption estimation in a telecommunication network, and related methods and apparatus.BACKGROUND
[0002] In fifth generation core (5GC), network functions (NF) are network entities that provide and consume services to and from each other, through a service based architecture (SBA). An energy information function (EIF) is a NF designed primarily to monitor energy consumption in the network and provide related metrics. See e.g., Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.501 V19.3.0 (2025-03): System architecture for the 5G System (5GS); Stage 2 (Release 19). These metrics can be calculated per user equipment (UE), per packet data unit (PDU) session, or per quality of service (QoS) flow, based on the fraction of energy consumed by a network node such as a gNodeB (gNB) and user plane function (UPF). This calculation can be derived from the ratio of traffic consumed by a UE to the total user plane (UP) traffic. A service consumer can subscribe to EIF energy metrics and receive the calculations.
[0003] According to 3GPP TS 23.501 V19.3.0 (2025-03): System architecture for the 5G System (5GS); Stage 2 (Release 19), the subscription data for a UE may include an energy saving indicator that the UE is subject to a network energy saving operation. An access and mobility function (AMF) receives the energy saving indicator in the UE subscription data. The AMF forwards the energy saving indicator to a next generation radio access network (NG-RAN) and to a policy control function (PCF). Then, during a policy association establishment procedure, the AMF sends to the PCF the energy saving indicator. Based on the energy saving indicator the PCF may make policy decisions reusing the existing parameters according to configured operator policies.
[0004] Figure 1 is a block diagram of an example 3 GPP reference architecture for energy efficiency and energy savings. Figure 1 includes an EIF communicatively connected via N113 to a PCF. EIF is also communicatively connected to a session management function (SMF) via N114, a unified data management (UDM) function via N112, an application function (AF) via N110, and a network exposure function (NEF) via NHL
[0005] Further, in the context of FS_EnergySys_Ph2 / Rel-20, there have been contributions in the SA2#168 meeting related to PCF making policy control decisions(including session management (SM), UE, and access / mobility management (AM) policies) based also on power consumption input from the EIF (N113). Examples of contributions include, without limitation: 3GPP SA2 WG TDOC S2-2504344; 3GPP SA2 WG TDOC S2-2504314; 3GPP SA2 WG TDOC S2-2503788; 3GPP SA2 WG TDOC S2-2503832; and 3GPP SA2 WG TDOC S2-2503787.SUMMARY
[0006] There currently exist certain challenge(s). An existing approach for energy consumption by the EIF is derived from the ratio of traffic consumed by a UE to the total user plane traffic. Such an approach may be overly simplified and lack accuracy. For example, the energy consumed by a network node, such as a gNB, and a UPF for delivering UE traffic can vary due to several factors, which are not taken into account in such an approach, which can result in different energy consumption for transferring the same volume of data. Factors can include, for example, at least:Frequency. For example, the power required in the gNB to transmit the traffic may be different for different frequencies;Qos applied to the traffic. For example, due to the handling of different packet error rates, implying retransmissions;Single-network slice selection assistance information (S-NSSAI) and / or a data network name (DNN). For example, there can be different energy configurations in the NFs in the different S-NSSAI / DNNs; and / orCentral processing unit (CPU) load of the gNB / UPF when transmitting the traffic.
[0007] Neither the EIF, nor any other network function such as a network data analytics function (NWDAF), in such an approach can predict energy consumption per UE while considering such factors. As a consequence, network functions such as the PCF cannot use such predictions to assist in the determination of appropriate enforcement policies for UE traffic delivery aimed at enhancing or optimizing energy efficiency.
[0008] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. An enhanced calculation of the energy consumption in a first node that includes the EIF, for example, is provided. The calculation considers at least additional characteristics such as the frequency used by the delivery of the traffic in a gNB, the QoS applied to the traffic, the S-NSSAI / DNN used for the PDU session delivering the traffic, and / or the CPU load of the gNB / user plane function (UPF) during the delivery. In some embodiments, the calculation applies artificial intelligence (AI) / machine learning (ML) techniques (collectively or individually referred to herein as “ML” techniques) to generate the estimation.
[0009] The term “prediction” is used in a non-limiting manner and, as explained herein, can refer to an estimation or a calculation. The terms “prediction” or “predicted” herein may be interchangeable and replaced with the terms “estimation” or “calculation” or “estimated” or “calculated”.
[0010] Moreover, in some embodiments, the estimation(s) of the energy that will be consumed by a UE, a PDU session, or a QoS flow during a time period is associated to a set of characteristics. The characteristics can include at least the frequency, the QoS, and the S-NSSAI / DNN. The estimation(s) can be used by a NF consumer such as the PCF as input for policy decisions to select a most efficient set of characteristics for a UE(s) at the time some actions are required in relation with energy saving or energy efficiency. Among other actions, the PCF may apply, for example, a specific QoS, select a different frequency by providing a radio access technology (RAT) frequency selection priority (RFSP) within a policy, or change the S-NSSAI / DNN for some traffic by using a UE route selection policy (URSP). The estimation(s) can be provided by the first node (e.g., the EIF and / or the NWDAF).
[0011] In some embodiments, the first node provides predictions of the energy that will be consumed by a UE, a PDU session, or a QoS flow during a time period, associated to a set of characteristics. The set of characteristics can include, for example, at least the frequency, the QoS, and the S-NSSAUDNN so a NF consumer, e.g. the PCF, can use the estimation(s) as input to determine appropriate values of such characteristics when making policy decisions related to energy saving or energy efficiency.
[0012] Some embodiments are directed to a computer-implemented method performed by a first node in a telecommunications network. The computer-implemented method includes generating an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period, the estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from the user equipment. The computer-implemented method further includes providing, to a second node, the estimate of energy consumption associated with the plurality of characteristics.
[0013] Other embodiments are directed to a computer-implemented method performed by a second node in a telecommunications network. The computer-implemented method includes requesting an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period based on a plurality of characteristics related to delivery of traffic from the user equipment; and receiving 402 the estimate of energy consumption associated with the plurality of characteristics related to the delivery of traffic from the user equipment.
[0014] Still other embodiments are directed to a first node. The first node comprises processing circuitry; and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the first node to perform operations. The operations comprise to generate an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period, the estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from the user equipment; and to provide, to a second node, the estimate of energy consumption associated with the plurality of characteristics.
[0015] Yet other embodiments are directed to a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry of a first node whereby execution of the program code causes the first node to perform operations. The operations comprise to generate an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period, the estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from the user equipment; and to provide, to a second node, the estimate of energy consumption associated with the plurality of characteristics.
[0016] Some embodiments are directed to a second node. The second node comprises processing circuitry; and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the first node to perform operations. The operations comprise to request an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period based on a plurality of characteristics related to delivery of traffic from the user equipment; and to receive the estimate of energy consumption associated with the plurality of characteristics related to the delivery of traffic from the user equipment.
[0017] Still other embodiments are directed to a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry of a second node whereby execution of the program code causes the second node to perform operations. The operations comprise to request an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period based on a plurality of characteristics related to delivery of traffic from the user equipment; and to receive the estimate of energy consumption associated with the plurality of characteristics related to the delivery of traffic from the user equipment.
[0018] Certain embodiments may provide one or more of the following technical advantage(s). The role of the first node, such as an EIF or NWDAF, can be enhanced to estimatethe energy consumption of a UE, a PDU session, or a QoS flow associated with a set of characteristics. The estimation(s) may assist NF consumers, such as the PCF, in making more informed and efficient policy decisions related to energy saving in a telecommunication network such as 5G system (5GS). In an example, by selecting more efficient policy decisions, the 5GS may enhance energy saving across a 5G network and may reduce the overall energy footprint of the 5GS. Moreover, in some embodiments, estimating the energy consumption of a UE, a PDU session, or a QoS flow associated with a set of characteristics is further enhanced by integrating ML techniques to generate the estimation.BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:
[0020] Figure 1 is a block diagram of an example 3 GPP reference architecture for energy efficiency and energy savings;
[0021] Figure 2 is a sequence diagram illustrating operations in an example according to some embodiments;
[0022] Figures 3A and 3B are flow charts of operations of a first node in accordance with some embodiments;
[0023] Figure 4 is a flow chart of operations of a second node in accordance with some embodiments;
[0024] Figure 5 is a block diagram of a communication system in accordance with some embodiments;
[0025] Figure 6 is a block diagram of another example of a communication system in accordance with some embodiments;
[0026] Figure 7 is a block diagram of a node in accordance with some embodiments; and
[0027] Figure 8 is a block diagram of a virtualization environment in accordance with some embodiments.DETAILED DESCRIPTION
[0028] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to theembodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.
[0029] While embodiments discussed herein are explained in the non-limiting context of a EIF, the disclosure is not so limited. Instead, the method can be used in other cases, including without limitation, other types of functions such as a network data analytics function (NWDAF).
[0030] Some embodiments include an estimation of the energy consumption in a first node, such as an EIF, by considering at least characteristics such as the frequency used by the delivery of the traffic in a network node such as a gNB, the QoS applied to the traffic, the S-NSSAI / DNN used for the PDU session delivering the traffic, and / or the CPU load of the network node (e.g., gNB) / UPF during the delivery.
[0031] In some embodiments, the first node (e.g., EIF) is enabled to provide an estimation(s) of the energy that will be consumed by a UE, a PDU session, or a QoS flow during a time period, associated to a set of characteristics. The set of characteristics can include, for example, at least the frequency, the QoS, and the S-NSSAUDNN. The estimation(s) can be used by a NF consumer such as the PCF as input for policy decisions to determine a plurality of characteristics for a UE(s) at the time some actions are required in relation with energy saving or energy efficiency. The consumer (e.g., PCF) may request the estimation conditioned to value (single or multiple) of one or more of the characteristics.
[0032] In some embodiments, generating the estimate is generated by a ML model.
[0033] In one approach according to annex T.2 in 3GPP TS 23.501 V19.3.0 (2025-03), an EIF makes an estimation of the energy consumed by a UE based on the fraction of energy consumed by a gNB and UPF. The estimation is derived from only the ratio of traffic consumed by a UE to the total user plane traffic.
[0034] An enhanced estimation of the energy consumed by a UE is provided in certain embodiments. The enhanced estimation considers not only the volume of the traffic consumed by the UE but additional characteristics related with the transfer of such traffic that have an influence on energy. The characteristics can include, without limitation, frequency, QoS applied (e.g., due to handling of different packet error rates, implying retransmissions); S-NSSAUDNN; and CPU load of a network node such as a gNB / UPF.
[0035] For this purpose, the first node such as an EIF, in addition to the information already collected from a SMF and 0AM as described in clause 5.51.2.2 from 3GPP TS 23.501 V 19.3.0 (2025-03), also collects additional information. The additional information can include a used QoS, a frequency, a network node CPU load, a network node load per carrier, a UPF CPU load, and / or core network features that are an aggregation of information from a radio access network (RAN)as shown in the following examples:Table 5.51.2.2.2-2: Information from SMF for user-plane energy consumption calculation Information DescriptionUE IP address UE IP address.UE ID SUPI.S-NSSAI Network Slice applicable to a UES-NSSAI +DNN Slice and DNN applicable to a PDU session.Packet Filters Packet Filters as in clause 5.7.6 for IP or Ethernet traffic. Application Identifier Identification for the traffic of the service data flow.List of Data Volume The data volume and the associated UPF(s) and gNB(s) information serving the UE within the time interval.> UL / DL Data Volume The UL / DL Data Volume of a PDU Session identified by (UE-ID, S-NSSAUDNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters / Application Identifier).> (I-)UPF ID(s) Identifier of any (L)UPF(s) associated to a reported data volume used by a PDU Session identified by (UE-ID, S- NSSAUDNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters / Application Identifier).> gNB ID Identifier of the gNB serving the UE.Reference to Time Indicate the time interval of the collected information Interval (e.g. time stamps).Used QoS QoS parameters and QoS characteristics attributesTable 5.51.2.2.2-1: Information from OAM for user-plane energy consumption calculationInformation DescriptiongNB energy consumption The Energy consumed by a gNB over the configured time interval T based on clause 6.7.3.4.2 of TS 28.554
[0209] . gNB data volume The UL / DL data volume handled by a gNB over the configured time interval T based on clause 6.7.1.1 of TS 28.554
[0209] .UPF energy consumption The Energy consumed by a UPF over the configure time interval T based on clause 6.7.3.1 of TS 28.554
[0209] . UPF data volume Data volume consumed at a UPF.Frequency Frequency used by the UE over time Interval T gNB CPU load Load of the gNB over time Interval TgNB load per carrier Load of the gNB per carrier frequency over time Interval T UPF CPU load Load of the UPF over time interval TCore Network Features (these are an aggregation of information from the RAN:Information DescriptionradioTransmitPerfMode Describes if a gNB is set at coverage or capacity modeProductNumber and Band and The product number, band and revision for the Revision given cellpmPrbUsedDIBcch Total number of PRB pairs used for System Information. Continuous measurement on TTI granularity is aggregated to cell level. noOfPucchSrUsers Resource allocation for PUCCH SR users pmRadioRecinterferencePwrPucch The measured Noise and Interference Power on PUCCHpmSinrPuschDistr Distribution of SINR values for PUSCH prbUtilisation Distribution of filtered DL PRB utilization level for each cell. Note that only resources scheduled with high priority are considered. pmCellHoExeAttLtelnterF The number of outgoing intra LTE interfrequency handover execution attemptsexcluding handovers to small cells without having cell relation.HOSuccRate Success rate of Hand overs pmUlPathlossDistr Uplink pathloss distribution noOfPucchCqiUsers Number of Channel Quality Indicator (CQI) resources available on the PUCCH channel pmRrcConnLevSum Sum of all sample values recorded for number of UEs in RRC_CONNECTED mode excluding bandwidth-reduced UEs pmRrcConnEstabAtt Total number of RRC Connection Request attemptspZeroNominalPucch The nominal component of the UE transmit power for Physical Uplink Control Channel (PUCCH)pmSinrPucchDistr Distribution of the SINR values calculated for PUCCHpmSchedActivityUeDl Total UEs scheduling activity in the downlink.For CA it is counted once on each cell the UE uses. Can be used as the MAC timebase. pmRadioUeRepCqiDistr Reported CQI value from UEs not in higher order modulation (HOM) mode in a distribution. Bandwidth reduced UEs are excluded from this measurement. noOfTx No of Transmitters in the gNB pmSessionTimeUe Accumulated active session time for all UEs in a cell, excluding bandwidth-reduced UEs.pmRrcConnMax Peak number of UEs in RRC_CONNECTED mode, excluding bandwidth-reduced UEs. pmSchedActivityCellul Aggregated number of ms in which DRB datawas required to be scheduled in the uplink.Bandwidth-reduced UEs are excluded from this measurement.pmSchedActivityCellDl Aggregated number of ms in which DRB data has to be scheduled in downlink. For Carrier Aggregation, only pegged for PCell traffic. Can be used as PDCP timebase. Bandwidth-reduced UEs are excluded from this measurement. pmRrcConnEstabAttReatt The total number of RRC Connection Request attempts that are considered as re-attempts.pmSchedActivityUeUl Total UEs scheduling activity in the uplink. pmActiveUeUlSum Number of UEs considered active in the uplink direction.pmPdschBlankedSubframe Number of blanked subframes which have no PDSCH data.
[0036] The first node, such as an EIF, can collect such information from different UEs, in different situations (e.g., covering different frequencies, different QoS, different S-NSS AI / DNNs and gNB and UPF load levels) and from different areas to train a ML model(s) which may provide an enhanced and more accurate calculation of the energy consumed.
[0037] Training of a ML model(s) to generate the estimation can be initiated offline, under a set of controlled scenarios. There may be several advantages to this approach including, but not limited to, the following.
[0038] First, these scenarios will create training data that can provide a realistic amount of variance for the ML model input features and labels. This data collection process can happen independently of the deployment environment and, therefore, there is no computational overhead to the real system.
[0039] Second, training in controlled scenarios (also referred to as simulation settings) may allow an initial, baseline classification of features that have a greater impact on the energy estimation depending on the traffic and service characteristics of the UE (e.g., QoS, S-NSSAUDNN, frequency). This may lead to a smaller, highly efficient ML model(s) through feature selection.
[0040] Third, once feature selection is done, in controlled scenarios, ML model loss (e.g., the actual divergence of the energy estimation from the real consumption) may be easily calculated.
[0041] Fourth, through this process, what-if scenarios can be tested, e.g. how energy consumption of a UE changes with a shift in frequency or change of QoS requirements. These changes can be verified in the controlled settings. From controlled scenarios to a real environment(s) there can be some discrepancy or special traffic situations not treated.
[0042] Given a refined ML model architecture through feature selection and a set of pretrained, baseline ML model weights, the ML model(s) can be deployed with the first node (such as an EIF) in a running network. If during network operation, the network identifies an ML model drift (e.g., degradation in performance), then the training can be refined online either by retraining the entire ML model using new data (which can be prone to catastrophic forgetting - new learning overriding old data) or by training only a portion (e.g., the last layers) of the ML model which is also known as fine-tuning and allows for maintaining parity with past knowledge. The choice between training from scratch and fine-tuning can be made by observing the performance of the ML model via monitoring and checking the degree at which the ML model needs to perform on past or on new data.
[0043] Once the ML model(s) is trained and a NF asks an EIF, for example, to monitor the energy consumption for a UE, a PDU session, or a QoS Flow, the EIF in addition to the data collection already described in clause 5.51.2.2 from 3GPP TS 23.501 V19.3.0 (2025-03), obtains the characteristics of the traffic delivered by the UE (QoS, S-NSS AI / DNN, frequency, etc.) and can use it as input for inference on the trained ML model(s) of the energy consumed by the UE.
[0044] The first node, such as an EIF, can use the ML model(s) to provide an estimation(s) of the energy that will be consumed by a UE, a PDU session, or a QoS flow during a time period, associated to a set of characteristics. The set of characteristics can include at least the frequency, the QoS, and the S-NSS AI / DNN . The estimation(s) can be used by a NF consumer, such as a PCF, as input for policy decisions to determine a most efficient set of characteristics for a UE(s).
[0045] An event(s) can trigger the PCF to make policy decisions to reduce energy consumption. Examples include, without limitation: An operator may define some policies defining a maximum threshold for energy consumption for a UE or group of UEs (e.g., considering all QoS flows and PDU sessions for a UE), a maximum consumption for a network slice, area, etc.. The thresholds may be also stored as unified data repository (UDR) policyinformation. In another example, an application function (AF) may provide some inputs to influence the energy consumption levels for a UE, a group of UEs, or even a network slice.
[0046] In an example, an EIF or NWDAF exposes a new application interface (API) to provide estimations of the energy consumed by a UE for the delivery of traffic under certain characteristics, as the frequency, the QoS, S-NSSAFDNN, etc.
[0047] The consumer of the prediction, e.g. the PCF, indicates input information in the request or subscription. The input information can include, without limitation:Target: UEId or UEIds for a list of UEsTarget Period: the time period over which the estimation is requested Granularity: UE, PDU session, or QoS flowFrequency or Frequencies [Optional]: List of the frequencies to get energy consumption predictionS-NSSAI / DNNs [Optional]: List of the S-NSSAI / DNNs to get energy consumption predictionQoS parameter sets [Optional]: List of the QoS parameter sets (including a 5G QoS identifier (5QI_ or QoS characteristics, for guaranteed bit rate (GBR) flows, guaranteed flow bit rate (GFBR) and maximum flow bit rate (MFBR)) to get energy consumption predictionApplicationld or service data flow (SDF) template [Optional]: In case the granularity is per QoS flowData Volume [optional]: Expected data volume to be considered in the estimation of the energy consumption. It not provided, the EIF may estimate it by contacting with the NWDAF.Location [Optional] : Expected location of the UE to be considered in the estimation of the energy consumption. It not provided, the EIF may estimate that location by contacting with the NWDAF.
[0048] In some embodiments, the request does not include a volume of data and / or a location of the at least one user equipment, and the first node estimates the volume of data and / or the location by contacting a network data analytics function, NWDAF. Thus, the first node reuses existing analytics from the NWDAF, e.g., UE communication and UE mobility respectively.
[0049] The output provided by the EIF, for example, can contain the estimation of the energy consumed by the UE associated to the set of characteristics provided by the consumer.Thus, the estimation(s) can assist the consumer, e.g. the PCF, in the determination of the most efficient policy decisions to satisfy energy efficiency restrictions while having the lowest impact in the traffic delivery. It is noted that by using the estimation(s), among other actions, the PCF may apply a specific QoS, select a different frequency by providing RFSP within a policy, or change the S-NSSAI / DNN for some traffic by using URSP, for example.
[0050] An example of the estimation output is shown in Table 1 below:Table 1: Energy consumption predictionInformation DescriptionList of energy prediction information Predicted energy consumption during the target period (L.max)> Analytics target period subset Time window within the requested target.> energy consumption Predicted energy consumption for the UE during the target period and associated characteristics >Frequency Frequency>QoS Parameter set 5QI or QoS characteristics, for GBR flows GFBR and MFBR, as provided in the input>S-NSSAI S-NSSAI of the PDU session for the traffic delivery >DNN DNN of the PDU session for the traffic delivery
[0051] Figure 2 is a sequence diagram of operations in an example according to some embodiments. In this example, PCF 208 is a NF consumer. PCF 208 requests and makes use of the energy estimation(s) provided by EIF 200.
[0052] In operation 0, EIF 200 collects information about different types of UEs with different service level agreements (SLAs) and subscriptions, area, QoS values, traffic usage, throughput, latency, etc., and trains a ML model(s).
[0053] PCF 208, in operation 1, receives an internal or external trigger which requires to take some action(s) to reduce the energy consumption of a UE, a PDU session, or a QoS flow. Internal triggers can be, e.g., PCF 208 needs to keep the energy consumption of a slice under a target limit ( e.g., as described in 3GPP SA2 WG TDOC S2-2504479). External triggers can be, e.g., an AF sends a request to influence the energy consumption levels for a UE, a group of UEs, or even a network slice.
[0054] In operation 2, PCF 208 sends a request according to input parameters discussed herein, and asks EIF 200 about estimation of the consumed energy for a specific UE byproviding a set of characteristics (e.g. provides two frequency values and two different QoS parameter sets).
[0055] EIF 200, in operation 3, collects information about UE type, subscription, etc., from UE profile in unified data management (UDM) / UDR 204.
[0056] In operation 4, EIF 200 collects information about the UE from other NFs in the core network needed to make inference on the trained ML model(s). Non-limiting examples include:- gNB and UPF nodes are obtained from the expected location of the UE and S- NSSAUDNN- Predicted load of the gNB and UPF are obtained from NF 202 load analytic from NWDAF.- If expected data volume is not provided, EIF 200 can obtain predicted data volume from UE communication pattern from NWDAF.- If expected location is not provided, EIF 200 can obtain predicted location from UE mobility analytic from NWDAF.
[0057] In operation 5, EIF 200 queries 0AM 206 to collect information about energy consumption and energy metrics in a RAN.
[0058] In operation 6, using all collected information in operations 3 - 5, EIF 200 makes an estimation of the energy consumption of the UE during the requested period associated to combinations of characteristics provided by the consumer in the request (e.g. one estimation associated with frequency_l and QoS_ 1, another estimation for frequency _2 and QoS_2, etc..).
[0059] In operation 7, EIF 200 sends the estimation in response to the service consumer’s request.
[0060] In operation 8, PCF 208 uses the estimation(s) to determine the most efficient policy decisions to satisfy energy efficiency restrictions while having the lowest impact in the traffic delivery.
[0061] Figures 3A and 3B are flow charts are flowcharts illustrating operations of a first node according to some embodiments.
[0062] Referring to Figure 3A, some embodiments are directed to a computer-implemented method performed by a first node in a telecommunications network. The computer-implemented method includes generating 312 an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period, the estimate of energy consumption associated with a plurality of characteristicsrelated to delivery of traffic from the user equipment. The computer-implemented method further includes providing 314, to a second node, the estimate of energy consumption associated with the plurality of characteristics.
[0063] The plurality of characteristics can include at least a frequency used to deliver the traffic to a network node, the quality of service applied to the traffic, and at least one singlenetwork slice selection assistance information (S-NSSAI) and / or data network name (DNN) used for the packet data unit, PDU, session delivering the traffic.
[0064] The plurality of characteristics can further include a central processing unit (CPU) load of the network node and / or a user plane function during the delivery of the traffic.
[0065] The estimate of energy consumption can include an input to the second node to determine a respective value for a respective characteristic in the plurality of characteristics when the second node makes a policy decision related to energy saving or energy efficiency in the telecommunications network.
[0066] In some embodiments, the computer-implemented method further includes collecting 300 first information including energy consumption information from at least one of a SMF, an operations and management function (0AM), and core network features from a RAN and training 302 a ML model with the first information to generate an estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from a user equipment.
[0067] The training can be performed offline under a set of controlled scenarios.
[0068] Referring to Figure 3B, in other embodiments, the computer-implemented method further includes identifying 316 drift in a deployed ML model; and refining the deployed ML model based on identifying the drift, the refining comprising at least one of re-training the deployed ML model with new information and training a portion of the deployed ML model with past information.
[0069] Referring to Figure 3A, in still other embodiments, the computer-implemented method further includes receiving 304 a request for the estimate of energy consumption by at least one of the user equipment, the packet data unit session, and the quality of service flow for the traffic comprising the plurality of characteristics related to delivery of the traffic.
[0070] The request can further include an identification of at least one user equipment, the time period, and the request for the estimate of energy consumption is for one of the user equipment, the packet data unit session, and the quality of service flow. Wen the estimation is requested per packet data unit session, the request can further include a S-NSSAI and / or DNN identifying the packet data unit session. When the estimation is requested per quality of serviceflow, the request can further include a flow description or application identifier (AppID), and S-NSSAI and / or DNN.
[0071] In some embodiments, the request includes one or more of the following: an identity of at least one frequency for the estimate of energy consumption; an identity of one or more S-NSSAI and / or DNN for the estimate of energy consumption; an identity of at least one parameter for the quality of service for the estimate of energy consumption; when the estimate of energy consumption is for the quality of service flow, an application identifier or a service data flow, SDF, template; a volume of data for the estimate of energy consumption; and a location of the at least one user equipment for the estimate of energy consumption.
[0072] In other embodiments, the request does not include a volume of data and / or a location of the at least one user equipment, and the first node estimates the volume of data and / or the location by contacting a NWDAF.
[0073] In still other embodiments, the computer-implemented method further includes collecting 306 second information about at least a type of the user equipment.
[0074] In yet other embodiments, the computer-implemented method further includes collecting 308 third information about the user equipment for generating the estimate of energy consumption.
[0075] In other embodiments, the computer-implemented method further includes collecting 310 fourth information about energy consumption in a RAN.
[0076] Generating 312 the estimate of energy consumption can use information from the second, third, and fourth information during the time period associated to the plurality of characteristics.
[0077] The estimate of energy consumption can include one or more of the following: an identity of energy estimation information comprising an estimated energy consumption during the time period; a time window within the time period; the estimate of energy consumption for one of the user equipment, the packet data unit session, and the quality of service flow during the time period and the associated plurality of characteristics; at least one frequency; at least one parameter of the quality of service; a S-NSSAI of the packet data unit session for the traffic delivery; and a DNN of the packet data unit session for the traffic delivery.
[0078] In some embodiments, the plurality of characteristics includes an input to generate the estimate of energy consumption.
[0079] In other embodiments, providing 314 the estimate of energy consumption includes exposing an application interface (API) to provide the estimate of energy consumption.
[0080] The first node can include at least one of an EIF and a NWDAF.
[0081] The second network node can include a PCF.
[0082] In some embodiments, the estimate of energy consumption associated with the plurality of characteristics is an input to the second node when making a policy decision related to energy saving or energy efficiency.
[0083] Generating 312 the estimated of energy consumption can be generated with a ML model.
[0084] Operations 300 - 310 of Figure 3 A and operations 316 and 318 of Figure 3B may be optional with respect to some embodiments of first nodes and related methods.
[0085] Figure 4 is a flow chart illustrating operations of a second node according to some embodiments.
[0086] Referring to Figure 4, some embodiments are directed to a computer-implemented method performed by a second node in a telecommunications network. The computer-implemented method includes requesting 400 an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period based on a plurality of characteristics related to delivery of traffic from the user equipment; and receiving 402 the estimate of energy consumption associated with the plurality of characteristics related to the delivery of traffic from the user equipment.
[0087] The plurality of characteristics can include at least a frequency used to deliver the traffic to a network node, the quality of service applied to the traffic, and at least one S -NS SAI and / or DNN used for the packet data unit (PDU) session delivering the traffic.
[0088] The plurality of characteristics can further include a CPU load of the network node and / or a user plane function during the delivery of the traffic.
[0089] In some embodiments, the computer-implemented method further includes using 404 the estimate of energy consumption as an input when making a policy decision related to energy saving or energy efficiency.
[0090] Requesting 400 can further include an identification of at least one user equipment, the time period, and the request for the estimate of energy consumption is for one of the user equipment, the packet data unit session, and the quality of service flow. When the estimation is requested per packet data unit session, the request can further include a S-NSSAI and / or DNN identifying the packet data unit session. When the estimation is requested per quality of service flow, the request can further include a flow description or application identifier (AppID), and S-NSSAI and / or DNN.
[0091] Requesting 400 can further include one or more of the following: an identity of at least one frequency for the estimate of energy consumption; an identity of one or more S-NSSAI and / or DNN for the estimate of energy consumption; an identity of at least one parameter for the quality of service for the estimate of energy consumption. When the estimate of energy consumption is for the quality of service flow, an application identifier or a service data flow, SDF, template; a volume of data for the estimate of energy consumption; and a location of the at least one user equipment for the estimate of energy consumption.
[0092] The estimate of energy consumption can include one or more of the following: an identity of energy estimation information comprising an estimated energy consumption during the time period; a time window within the time period; the estimate of energy consumption for one of the user equipment, the packet data unit session, and the quality of service flow during the time period and the associated plurality of characteristics; at least one frequency; at least one parameter of the quality of service; a S-NSSAI of the packet data unit session for the traffic delivery; and a DNN of the packet data unit session for the traffic delivery.
[0093] The request 400 can be triggered by an event.
[0094] The event can include at least one of energy consumed by a user equipment exceeds a maximum threshold for energy consumption, or the energy consumed by a network slice exceeds a maximum threshold, and the maximum threshold is provided by an application function.
[0095] Using 404 can include the estimate of energy consumption is used as an input to determine a respective value for a respective characteristic in the plurality of characteristics when the second node makes a policy decision related to energy saving or energy efficiency in the telecommunications network while maintaining a lowest impact in the traffic delivery.
[0096] Operation 404 of Figure 4 may be optional with respect to some embodiments of second nodes and related methods.
[0097] Figure 5 shows an example of a communication system 500 in accordance with some embodiments.
[0098] In the example, the communication system 500 includes a telecommunications network 502 that includes an access network 504, such as a RAN, and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes or base stations of various types, access network nodes 510A and 510B are depicted (which may be collectively referred to as network nodes 510), or any other similar 3GPP access nodes or non-3GPP access points (APs). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one ormore of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.
[0099] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 502, including one or more access network nodes 510 and / or core network nodes 508.
[0100] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
[0101] The network nodes 510 facilitate direct or indirect connection of one or more UEs 512 to the core network 506 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other componentsor systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0102] The UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 510 and other communication devices. Similarly, the network nodes 508, 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 502) with the UEs 512 and / or with other network nodes or equipment in the telecommunications network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 502. More specifically, UEs 512 may send messages, data, and / or other signals to network nodes 508, 510 or other elements of the telecommunications network 502 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 508, 510 may send messages, data, and other signals to UEs 5122, other network nodes 508, 510, and other devices in telecommunications network 502 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 512 by transmitting the message to an access network node 510 that will then transmit the message to the intended UE 512. Similarly, a core network node 108 may receive a particular message from a UE 512 by receiving the message from an access network node 510 that itself received the message from the UE 512.
[0103] In the depicted example, the core network 506 connects elements of the access network 504 (e.g., one or more of the network nodes 510) to one or more host computing systems, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one or more core network nodes (e.g., core network node 508) of various types, one or more of which may be generally referred to as network nodes 508. Network nodes 508 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example corenetwork nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), AMF, SMF, Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), UDM, Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a UPF.
[0104] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunications network 502. The host 516 may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0105] As a whole, the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 500 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 500 supporting different standards, protocols, or rule sets.
[0106] As one example, in certain embodiments, access network 504 may contain some access network nodes 510 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 510 support (or the same access network nodes 510 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 502 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result,may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0107] Telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0108] In some examples, one or more of the UEs 512 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-RAT or multi- standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0109] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and / or 512D) and network nodes (e.g., network node 510B). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514.
[0110] As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0111] The hub 514 may have a constant / persistent or intermittent connection to the network node 510B. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512C and / or 512D), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510B. In other embodiments, the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 510B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0112] Figure 6 is another example of a communication system 600 according to some embodiments. As used herein, the communication system 600 includes multiple access points (APs) 610 (with four exemplary APs 610A, 610B, 610C, and 610D being depicted) and multiple wireless devices, referred to in the context of communication system 600 as stations (STAs) 612 (referred to individually as STA 612A, STA 612B, STA 612C, STA 612D, and STA 612E). STA 612A is served by AP 610A in a first basic service set (BSS) 620A. STA 610B and STA 610C are served by AP 610B in a second BSS, BSS 620B. STA 612D is served by AP 610C in a third BSS, BSS 620C. STA 612E is served by AP 610D in a fourth BSS, BSS 620D. Stations 612 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 612 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0113] Each of STAs 612 may connect through a radio link to one of APs 610. For example, depending on location or channel conditions experienced by a given STA 612, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from afrequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0114] Each AP 610 may provide data connectivity to STAs 612 connected to a particular AP 610. As illustrated, APs 610 may be connected to a data network 630. In this way, APs 610 may also provide data connectivity between STAs 612 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 612 and its serving AP 610 may be used for providing various kinds of services to STA 612, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 612 and / or on a device linked to STA 612. By way of example, Figure 6 illustrates an application service platform 632 provided in data network 630. The application(s) executed on STA 612 and / or on one or more other devices linked to STA 612 may use the radio link for data communication with one or more other STA 612 and / or the application service platform 632, thereby enabling utilization of the corresponding service(s) at STA 612.
[0115] Figure 7 shows a node 700 in accordance with some embodiments. As used herein, node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, node 700 may be configured to operate in communication system 500 of Figure 5, like network nodes 508 or 510, or in communication system 600 of Figure 6, like an AP 610 or a station 612. Examples of nodes include, but are not limited to, nodes comprising a logical function such as EIF / NWDAF 200 and / or PCF 208, which can include access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
[0116] Nodes 700 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Node 700 may be a relay node or a relay donor node controlling a relay. Nodes 700 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0117] Other examples of nodes 700 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0118] In particular embodiments, node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, a power source 708, and an EIF / NWDAF 200 and / or a PCF 208. In general, in a particular embodiment of node 700, processing circuitry 702, memory 704, communication interface 706, and power source 708 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of node 700.
[0119] The node 700 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the node 700 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 704 or portions of memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs). The node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into node 700, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within node 700.
[0120] The processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitablecomputing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 704, to provide node 700 functionality.
[0121] In some embodiments, the processing circuitry 702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.
[0122] The memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 702. The memory 704 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 702 and utilized by the node 700. The memory 704 may be used to store any calculations made by the processing circuitry 702 and / or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and memory 704 is integrated.
[0123] The communication interface 706 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 706 comprises port(s) / terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, node 700 may be capable of wireless communication and communication interface 706 may also include radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, an antenna 710. Particular embodiments of radio front-end circuitry 718 include filter(s) 720 and amplifier(s) 722. The radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702. The radio front-end circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry702. The radio front-end circuitry 718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 718 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 720 and / or amplifiers 722. The radio signal(s) may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0124] In certain alternative embodiments, node 700 may be capable of wireless communication but does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
[0125] The antenna 710 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 710 is separate from the node 700 and connectable to the node 700 through one or more interfaces or ports.
[0126] The antenna 710, communication interface 706, and / or the processing circuitry 702 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the node 700. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 710, the communication interface 706, and / or the processing circuitry 702 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the node 700. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0127] The power source 708 provides power to the various components of node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, powermanagement circuitry to supply the components of the node 700 with power for performing the functionality described herein. For example, the node 700 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708. As a further example, the power source 708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0128] Embodiments of the node 700 may include additional components beyond those shown in Figure 7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the node 700 may include user interface equipment to allow input of information into the node 700 and to allow output of information from the node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the node 700.
[0129] Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
[0130] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 800 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0131] Hardware 804 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 808A and VM 808B (which may be collectively referred to as VMs 808), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 808.
[0132] The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0133] In the context of NFV, each of the VMs 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of hardware 804 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 808 on top of the hardware 804 and corresponds to an application 802.
[0134] Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. Insome embodiments, some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.
[0135] In certain embodiments, a first node 200, 508, 610, 632, 700, 802 includes processing circuitry 702; and at least one memory 704 connected to the processing circuitry and storing instructions that when executed by the processing circuitry causes the first node to perform operations. The operations include to perform some or all of the functionality described herein.
[0136] In other embodiments a second node 208, 508, 610, 632, 700, 802 includes processing circuitry 702; and at least one memory 704 connected to the processing circuitry and storing instructions that when executed by the processing circuitry causes the second node to perform operations. The operations include to perform some or all of the functionality described herein.
[0137] Although the computing devices described herein (e.g., nodes, UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0138] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certainembodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
[0139] In the above-description of certain embodiments of the present disclosure, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which concepts of the present disclosure belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0140] When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and / or clarity. The term “and / or” (abbreviated “ / ”) includes any and all combinations of one or more of the associated listed items.
[0141] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements / operations, these elements / operations should not be limited by these terms. These terms are only used to distinguish one element / operation from another element / operation. Thus a first element / operation in some embodiments could be termed a second element / operation in other embodiments without departing from the teachings ofconcepts of the present disclosure. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.
[0142] As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components, or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
[0143] Example embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer- implemented methods, apparatus (systems and / or devices) and / or computer program products. It is understood that a block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and / or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and / or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions / acts specified in the block diagrams and / or flowchart block or blocks, and thereby create means (functionality) and / or structure for implementing the functions / acts specified in the block diagrams and / or flowchart block(s).
[0144] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions / acts specified in the block diagrams and / or flowchart block or blocks. Accordingly, embodiments of the present disclosure may be embodied in hardware and / or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.
[0145] It should also be noted that in some alternate implementations, the functions / acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Moreover, the functionality of a given block of the flowcharts and / or block diagrams may be separated into multiple blocks and / or the functionality of two or more blocks of the flowcharts and / or block diagrams may be at least partially integrated. Finally, other blocks may be added / inserted between the blocks that are illustrated, and / or blocks / operations may be omitted without departing from the scope of the present disclosure. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
[0146] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present disclosure. All such variations and modifications are intended to be included herein within the scope of present disclosure. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description
Claims
CLAIMS1. A computer-implemented method performed by a first node in a telecommunications network, the method comprising:generating (312) an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period, the estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from the user equipment; andproviding (314), to a second node, the estimate of energy consumption associated with the plurality of characteristics.
2. The computer-implemented method of Claim 1 , wherein the plurality of characteristics comprises at least a frequency used to deliver the traffic to a network node, the quality of service applied to the traffic, and at least one single-network slice selection assistance information (S-NSSAI) and / or data network name (DNN) used for the packet data unit, PDU, session delivering the traffic.
3. The computer-implemented method of Claim2, wherein the plurality of characteristics further comprises a central processing unit, CPU, load of the network node and / or a user plane function during the delivery of the traffic.
4. Th computer- implemented method of any one of Claims 1 to 3, wherein the estimate of energy consumption comprises an input to the second node to determine a respective value for a respective characteristic in the plurality of characteristics when the second node makes a policy decision related to energy saving or energy efficiency in the telecommunications network.
5. The computer-implemented method of any one of Claims 1 to 4, further comprising:collecting (300) first information comprising energy consumption information from at least one of a session management function, SMF, an operations and management function, 0 AM, and core network features from a radio access network, RAN; andtraining (302) a machine learning, ML, model with the first information to generate an estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from a user equipment.
6. The computer-implemented method of Claim 5, wherein the training is performed offline under a set of controlled scenarios.
7. The computer-implemented method of any one of Claims 5 to 6, further comprising:identifying (316) drift in a deployed ML model; andrefining the deployed ML model based on identifying the drift, the refining comprising at least one of re-training the deployed ML model with new information and training a portion of the deployed ML model with past information.
8. The computer-implemented method of any one of Claims 1 to 7, further comprising:receiving (304) a request for the estimate of energy consumption by at least one of the user equipment, the packet data unit session, and the quality of service flow for the traffic comprising the plurality of characteristics related to delivery of the traffic.
9. The computer-implemented method of Claim 8, wherein the request further comprises an identification of at least one user equipment, the time period, and the request for the estimate of energy consumption is for one of the user equipment, the packet data unit session, and the quality of service flow,wherein when the estimation is requested per packet data unit session, the request further comprises a single-network slice selection assistance information (S-NSSAI) and / or data network name (DNN) identifying the packet data unit session, andwherein when the estimation is requested per quality of service flow, the request further comprises a flow description or application identifier, AppID, and S-NSSAI and / or DNN.
10. The computer-implemented method of Claim 9, wherein the request further comprises one or more of the following:an identity of at least one frequency for the estimate of energy consumption,an identity of one or more single-network slice selection assistance information (S-NSSAI) and / or data network name (DNN) for the estimate of energy consumption,an identity of at least one parameter for the quality of service for the estimate of energy consumption,when the estimate of energy consumption is for the quality of service flow, an application identifier or a service data flow, SDF, template,a volume of data for the estimate of energy consumption, anda location of the at least one user equipment for the estimate of energy consumption.
11. The computer-implemented method of Claim 10, wherein the request does not include a volume of data for the estimate of energy consumption and / or a location of the at least one user equipment, and the first node estimates the volume of data and / or the location by contacting a network data analytics function, NWDAF.
12. The computer-implemented method of any one of Claims 1 to 11, further comprising:collecting (306) second information about at least a type of the user equipment.
13. The computer-implemented method of any one of Claims 1 to 12, further comprising:collecting (308) third information about the user equipment for generating the estimate of energy consumption.
14. The computer-implemented method of any one of Claims 1 to 13, further comprising:collecting (310) fourth information about energy consumption in a radio access network.
15. The computer-implemented method of any one of Claims 12 to 14, wherein generating (312) the estimate of energy consumption uses information from the second, third, and fourth information during the time period associated to the plurality of characteristics.
16. The computer-implemented method of any one of Claims 1 to 15, wherein the estimate of energy consumption comprises one or more of the following:an identity of energy estimation information comprising an estimated energy consumption during the time period,a time window within the time period,the estimate of energy consumption for one of the user equipment, the packet data unit session, and the quality of service flow during the time period and the associated plurality of characteristics,at least one frequency,at least one parameter of the quality of service,a single-network slice selection assistance information, S-NSSAI, of the packet data unit session for the traffic delivery, anda data network name, DNN, of the packet data unit session for the traffic delivery.
17. The computer-implemented method of any one of Claims 1 to 16, wherein the plurality of characteristics comprises an input to generate the estimate of energy consumption.
18. The computer-implemented method of any one of Claims 1 to 17, providing (314) the estimate of energy consumption comprises exposing an application interface, API, to provide the estimate of energy consumption.
19. The computer-implemented method of any one of Claims 1 to 18, wherein the first node comprises at least one of an energy information function, EIF, and a network data analytics function, NWDAF.
20. The computer-implemented method of any one of Claims 1 to 19, wherein the second network node comprises a policy control function.
21. The computer-implemented method of any one of Claims 1 to 20, wherein the estimate of energy consumption associated with the plurality of characteristics is an input to the second node when making a policy decision related to energy saving or energy efficiency.
22. The computer-implemented method of any one of Claims 1 to 21, wherein generating (312) the estimated of energy consumption is generated with a machine learning (ML) model.
23. A computer-implemented method performed by a second node in a telecommunications network, the method comprising:requesting (400) an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period based on a plurality of characteristics related to delivery of traffic from the user equipment; andreceiving (402) the estimate of energy consumption associated with the plurality of characteristics related to the delivery of traffic from the user equipment.
24. The computer-implemented method of Claim 23, wherein the plurality of characteristics comprises at least a frequency used to deliver the traffic to a network node, the quality of service applied to the traffic, and at least one single-network slice selection assistance information (S-NSSAI) and / or data network name (DNN) used for the packet data unit, PDU, session delivering the traffic.
25. The computer-implemented method of Claim 24, wherein the plurality of characteristics further comprises a central processing unit, CPU, load of the network node and / or a user plane function during the delivery of the traffic.
26. The computer-implemented method of any one of Claims 23 to 25, further comprising:using (404) the estimate of energy consumption as an input when making a policy decision related to energy saving or energy efficiency.
27. The computer-implemented method of any one of Claims 23 to 26, wherein requesting (400) further comprises an identification of at least one user equipment, the time period, and the request for the estimate of energy consumption is for one of the user equipment, the packet data unit session, and the quality of service flow,wherein when the estimation is requested per packet data unit session, the request further comprises a single-network slice selection assistance information (S-NSSAI) and / or data network name (DNN) identifying the packet data unit session, andwherein when the estimation is requested per quality of service flow, the request further comprises a flow description or application identifier, AppID, and S-NSSAI and / or DNN.
28. The computer-implemented method of Claim 27, wherein requesting (400) further comprises one or more of the following:an identity of at least one frequency for the estimate of energy consumption, an identity of one or more single-network slice selection assistance information (S-NSSAI) and / or data network name (DNN) for the estimate of energy consumption,an identity of at least one parameter for the quality of service for the estimate of energy consumption,when the estimate of energy consumption is for the quality of service flow, an application identifier or a service data flow, SDF, template,a volume of data for the estimate of energy consumption, anda location of the at least one user equipment for the estimate of energy consumption.
29. The computer-implemented method of any one of Claims 23 to 28, wherein the estimate of energy consumption comprises one or more of the following:an identity of energy estimation information comprising an estimated energy consumption during the time period,a time window within the time period,the estimate of energy consumption for one of the user equipment, the packet data unit session, and the quality of service flow during the time period and the associated plurality of characteristics,at least one frequency,at least one parameter of the quality of service,a single-network slice selection assistance information, S-NSSAI, of the packet data unit session for the traffic delivery, anda data network name, DNN, of the packet data unit session for the traffic delivery.
30. The computer-implemented method of any one of Claims 23 to 29, wherein requesting (400) is triggered by an event.
31. The computer-implemented method of Claim 30, wherein the event comprises at least one of energy consumed by a user equipment exceeds a maximum threshold for energy consumption, or the energy consumed by a network slice exceeds a maximum threshold, and the maximum threshold is provided by an application function.
32. The computer-implemented method of any one of Claims 23 to 31, wherein using (404) comprises the estimate of energy consumption is used as an input to determine a respective value for a respective characteristic in the plurality of characteristics when the second node makes a policy decision related to energy saving or energy efficiency in the telecommunications network while maintaining a lowest impact in the traffic delivery.
33. The computer-implemented method of any one of Claims 23 to 32, wherein the second network node comprises a policy control function.
34. A first node (200, 508, 610, 632, 700, 802) comprising:processing circuitry (702); andmemory (704) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first node to perform operations comprising:generate an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period, the estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from the user equipment; andprovide, to a second node, the estimate of energy consumption associated with the plurality of characteristics.
35. The first node (200, 508, 610, 632, 700, 802) of Claim 34 wherein the memory includes further instructions that when executed by the processing circuitry causes the first node to perform operations according to any one of Claims 2 to 22.
36. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (702) of a first node (200, 508, 610, 632, 700, 802) whereby execution of the program code causes the first node to perform operations comprising:generate an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period, the estimate of energy consumption associated with a plurality of characteristics related to delivery of traffic from the user equipment; andprovide, to a second node, the estimate of energy consumption associated with the plurality of characteristics.
37. The computer program product of Claim 36, wherein the non-transitory storage medium includes further program code, whereby execution of the program code causes the first node to perform according to any one of Claims 2 to 22.
38. A second node (208, 508, 610, 632, 700, 802) comprising:processing circuitry (702); andmemory (704) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the second node to perform operations comprising:request an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period based on a plurality of characteristics related to delivery of traffic from the user equipment; and receive the estimate of energy consumption associated with the plurality of characteristics related to the delivery of traffic from the user equipment.
39. The second node (208, 508, 610, 632, 700, 802) of Embodiment 38 wherein the memory includes further instructions that when executed by the processing circuitry causes the second node to perform operations according to any one of Embodiments 24 to 33.
40. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (702) of a second node (208, 508, 610, 632, 700, 802) whereby execution of the program code causes the second node to perform operations comprising:request an estimate of energy consumption by at least one of a user equipment, a packet data unit session, and a quality of service flow during a time period based on a plurality of characteristics related to delivery of traffic from the user equipment; andreceive the estimate of energy consumption associated with the plurality of characteristics related to the delivery of traffic from the user equipment.
41. The computer program product of Claim 40, wherein the non-transitory storage medium includes further program code, whereby execution of the program code causes the second node to perform according to any one of Claims 24 to 33.
