Method, device and system for energy consumption management in wireless networks

Abstract

The present disclosure relates generally to methods, devices and systems for energy consumption measurement and management in wireless networks. A method performed by a first network element can comprise receiving, from a second network element, a first message carrying an energy consumption measurement configuration for measuring energy consumption associated with a served UE; obtaining, based on the energy consumption measurement configuration, energy consumption information for the energy consumption associated with the served UE; and sending, to a third network element, a second message carrying the energy consumption information associated with the served UE.

Description

Technical Field

[0001] This disclosure relates generally to wireless communication, and more particularly to methods, apparatus and systems for energy consumption measurement and management in wireless networks. Background Technology

[0002] To meet the unprecedented growth in mobile users and the demands of numerous new services, wireless communication networks need to continuously expand, leading to a sustained increase in energy consumption. Controlling power consumption and reducing energy costs while still meeting performance requirements is crucial for developing and deploying cost-effective wireless communication networks. Summary of the Invention

[0003] This invention relates to a method, apparatus, and system for power management in wireless networks (such as 3G, 4G, 5G, or 6G wireless networks). More specifically, power management includes: power management configuration, power consumption measurement, and reporting.

[0004] In some embodiments, a method performed by a first network element is disclosed. The method includes: receiving a first message from a second network element, the first message carrying an energy consumption measurement configuration for measuring energy consumption associated with a serving user equipment (UE); obtaining energy consumption information for energy consumption associated with the serving UE based on the energy consumption measurement configuration; and sending second information to a third network element, the second information carrying the energy consumption information associated with the serving UE.

[0005] In some embodiments, a method performed by a first network element is disclosed. The method includes: sending a first message to a second network element, the first message carrying an energy consumption measurement configuration for measuring energy consumption associated with a serving user equipment (UE); and receiving a second message from a third network element, the second message carrying energy consumption information associated with the serving UE, wherein the energy consumption information is collected based on the energy consumption measurement configuration. In some example embodiments, the second network element and the third network element are the same.

[0006] In some embodiments, there is a network element or network node including a processor and a memory, wherein the processor is configured to read code from the memory and implement any of the methods described in any embodiment.

[0007] In some embodiments, a computer program product includes computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the methods described in any embodiment.

[0008] Other aspects and alternatives to the above embodiments and their implementation are described in more detail in the following drawings, description and claims. Attached Figure Description

[0009] Figure 1 An example wireless communication network is shown.

[0010] Figure 2 An example wireless network node is shown.

[0011] Figure 3 An example user device is shown.

[0012] Figure 4A A high-level exemplary flowchart for power consumption measurement configuration and reporting is shown.

[0013] Figure 4B Example performance consumption measurement levels (or granularities) are shown.

[0014] Figure 5-7 Figures 8A, 8B, and 9-10 illustrate exemplary message flows in various network deployment scenarios for power consumption measurement configuration and reporting. Detailed Implementation

[0015] Wireless communication network Figure 1 An exemplary wireless communication network 100 is shown, which includes a core network 110 and a radio access network (RAN) 120. The core network 110 also includes at least one Mobility Management Entity (MME) 112 and / or at least one Access and Mobility Management Function (AMF). Figure 1No other functions that might be included in core network 110 are shown. RAN 120 also includes multiple base stations, such as base stations 122 and 124 (also referred to as eNB 122 and gNB 124). Base stations may include at least one evolved NodeB (eNB) for 4G LTE (Long Term Evolution), an enhanced LTE eNB (ng-eNB), or a next-generation NodeB (gNB) for 5G New Radio (NR), or any other type of signaling / receiving equipment (such as a Universal Mobile Telecommunications System (UMTS) NodeB). eNB 122 communicates with MME 112 via the S1 interface. Both eNB 122 and gNB 124 can connect to AMF 114 via the Ng interface. Each base station manages and supports at least one cell. For example, base station gNB 124 can be configured to manage and support cell 1, cell 2, and cell 3.

[0016] The gNB 124 may also include a Central Unit (CU) and at least one Distributed Unit (DU). The CU and DU may be located in the same location, or they may be located separately in different locations. The CU and DU may be connected via an F1 interface. Alternatively, for an eNB capable of connecting to a 5G network, the eNB may similarly be divided into a CU and at least one DU, the CU being referred to as ng-eNB-CU, and the at least one DU being referred to as ng-eNB-DU. The ng-eNB-CU and ng-eNB-DU may be connected via a W1 interface.

[0017] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1, labeled 140, includes cell 1, cell 2, and cell 3, and may also include… Figure 1Further cells, not shown, that can be managed by other base stations. The wireless communication network 100 may also include at least one UE 160. The UE can select a cell from among several cells supported by the base station to communicate with the base station via an over-the-air (OTA) wireless communication interface and resources, and the UE 160 can reselect the cell for communication as it travels within the wireless communication network 100. For example, the UE 160 may initially select cell 1 to communicate with base station 124, and subsequently, the UE 160 may reselect cell 2 at a later time. The cell selection or reselection performed by the UE 160 may be based on the wireless signal strength / quality in various cells and other factors.

[0018] The wireless communication network 100 can be implemented as, for example, a 2G, 3G, 4G / LTE, or 5G cellular communication network. Correspondingly, base stations 122 and 124 can be implemented as 2G base stations, 3G NodeBs, LTE eNBs, or 5G NR gNBs. The UE 160 can be implemented as a mobile or fixed communication device capable of accessing the wireless communication network 100. The UE 160 can include, but is not limited to: mobile phones, laptops, tablets, personal digital assistants, wearable devices, Internet of Things (IoT) devices, Machine Type Communication (MTC) / enhanced Machine Type Communication (eMTC) devices, distributed remote sensor devices, roadside assistance devices, XR devices, and desktop computers. The UE 160 may also be commonly referred to as a wireless communication device or a wireless terminal. The UE 160 can support sidelink communication to another UE via a PC5 interface.

[0019] Although the focus of the following description is as follows Figure 1 The cellular wireless communication system shown is based on the same principles, but the same principles also apply to other types of wireless communication systems for paging devices. These other wireless systems may include, but are not limited to, Wi-Fi networks, Bluetooth networks, ZigBee networks, and WiMax (World Interoperability for Microwave Access) networks.

[0020] Figure 2An example of an electronic device 200 is shown, which is used to implement a network base station (e.g., a radio access network node), a core network (CN), and / or operation and maintenance (OAM). Optionally, in one embodiment, the example electronic device 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 to transmit / receive communications with a UE and / or other base stations. Optionally, in one embodiment, the electronic device 200 may also include network interface circuitry 209 (e.g., optical or wired interconnect, Ethernet, and / or other data transmission media / protocols) for communicating between the base station and other base stations and / or the core network. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with operators, etc.

[0021] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include one or more processors 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for use by one or more processors 221 to perform functions of the network node. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0022] Figure 3An example of an electronic device (e.g., a user equipment (UE)) implementing terminal device 300 is shown. UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. UE 300 may include all or part of the following: communication interface 302, system circuitry 304, input / output interface (I / O) 306, display circuitry 308, and storage device 309. The display circuitry may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. System circuitry 304 may be implemented, for example, using one or more systems on a chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System circuitry 304 may be part of an implementation of any desired functionality in UE 300. In this regard, system circuitry 304 may include logic that facilitates, for example, decoding and playing music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (as an example, for an internet connection); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, a Universal Serial Bus (USB) connector, a memory card slot, a radiation sensor (e.g., an IR sensor), and other types of inputs.

[0023] Reference Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316, which processes signal transmission and reception via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver, including modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaper, an analog-to-digital converter (ADC), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals can follow any of a variety of formats, protocols, modulations (e.g., QPSK (Quadrature Phase Shift Keying), 16-QAM (Quadrature Amplitude Modulation), 64-QAM, or 256-QAM), channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), 5G (also known as New Radio (NR) or 5G NR), and 6G standards. However, the techniques described below are applicable to other wireless communication technologies, whether originating from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0024] Reference Figure 3System circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to implement the desired functions of UE 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that UE 300 will send or has received via communication interface 302. In various embodiments, system power for UE 300 may be provided by power storage devices such as batteries or transformers.

[0025] Energy management in wireless networks To meet the unprecedented growth in mobile users and the demands of numerous new services, wireless communication networks need to continuously expand, leading to a sustained increase in energy consumption. Energy consumption is a key factor to consider in developing more environmentally friendly wireless communication networks while still meeting quality of service requirements.

[0026] To reduce network energy consumption, various methods can be employed, such as complying with operator policies. For example, a wireless system can define a "maximum energy consumption limit" policy for users and / or the selected services provided to users. The maximum energy consumption limit can be a restriction on the total energy consumed by various network elements(s) and / or various network resources (e.g., hardware resources, software resources) to serve(s) a specific UE(s) or a specific service(s) of a UE(s). The maximum energy consumption limit may also apply for a given duration, such as daily, weekly, or monthly. In some example implementations, the limit may have several tiers. For example, the core network of a wireless network can set different limits and corresponding different tiers of charge rates. A higher charge rate may apply to a higher limit, or a higher charge rate may apply when a specified limit is exceeded. Thus, different charge rates may help reduce network energy consumption, as users may want to reduce costs by subscribing to plans or services that consume less energy. Therefore, it is beneficial for the core network to be able to identify how much energy the Radio Access Network (RAN) uses and whether the energy used by the RAN for a specific UE or a specific service of a UE exceeds the "maximum energy consumption limit."

[0027] However, current over-service makes it impossible for the core network to identify the energy consumption of the RAN side serving the UE or a specific service of the UE. This prevents the application of charging strategies based on total / maximum energy consumption limits. Furthermore, UEs may move frequently within the RAN network, and multiple base stations may serve the UE. Currently, the core network lacks an efficient and robust method to obtain the total energy consumed by these base stations to serve the UE (or a specific service of the UE). This document provides a method that enables the RAN to report to the core network the total energy consumed by network resources for a specific UE or a specific service of the UE (e.g., energy consumed at the UE level, PDU session level, or QoS flow level). This method can also be applied to scenarios where the UE moves and hands over between different base stations.

[0028] This disclosure describes various methods for implementing energy management in a wireless network. Energy management may include, for example, energy consumption measurement configuration and energy consumption reporting. A RAN (or one or more nodes, elements, or entities within a RAN) may be configured with energy consumption measurement requirements. Measurements may be configured to be performed at different levels. For example, these measurement levels may include UE level, Quality of Service (QoS) flow level, Packet Data Unit (PDU) session level, and Data Radio Bearer (DRB) level.

[0029] Figure 4A This illustrates a high-level example of performance consumption measurement configuration and energy consumption reporting framework. In this framework, the core network (or network elements within the core network, such as the AMF) is responsible for configuring energy consumption measurements. Figure 4B As shown, measurements can be configured at various levels. Table 1 below shows some example energy consumption measurement configurations.

[0030] Table 1: Example Measurement Levels

[0031] Note that the energy consumption measurement configuration can include one or more entries at different levels. For example, one or more rows in Table 1 can be configured.

[0032] In this disclosure, energy consumption may include the total energy consumed by network resources (e.g., network nodes, network entities, and network elements, which may be hardware, software, or a combination thereof) for providing services to a UE, one or more PDU sessions, one or more QoS flows, or one or more DRBs. Energy efficiency may be defined as the ratio between the service performance generated by the network (e.g., data volume, data rate, latency, etc.) and the energy consumed by network resources. For example, network energy efficiency may be defined as the ratio between the amount of data served and the energy consumed to serve that data volume, expressed in bits per joule. Note that energy consumption in this disclosure refers to the energy consumed by the RAN for serving a UE or one or more services of the UE (e.g., QoS flows, PDU sessions, DRBs).

[0033] In the embodiments described below, the gNB is used for illustrative purposes. Unless otherwise stated, the same basic principles apply to all types of base stations. The AMF is used as an example core network element. Other core network elements may also be used.

[0034] This disclosure presents various embodiments intended to provide mechanisms for energy consumption measurement configuration and energy consumption reporting. Details of these embodiments will be described below.

[0035] Example 1: RAN Energy Consumption Report In this embodiment, RAN energy consumption measurement and reporting are described at the base station (e.g., gNB) level or the RAN level (note that the gNB is part of the RAN). The base station may include, for example, a gNB with a non-split architecture. The core network element (e.g., AMF) is responsible for requesting and configuring RAN-side energy consumption measurements. The AMF may send a message carrying energy consumption measurement configuration to the base station. This message may be a Next Generation Application Protocol (NGAP) message, which may include, for example, an Initial Context Setup Request message. Then, as requested / configured in the message, the base station may begin measuring / collecting RAN energy consumption for serving the UE until the AMF sends another message triggering the RAN to stop energy consumption measurement. For example, the AMF may send a UE Context Release Command message to release the UE and stop energy consumption measurement for the UE. The base station can then report the total energy consumption measured for serving the UE to the AMF via, for example, a UE Context Release Complete message. Therefore, the core network (CN) can know the RAN power consumption used to serve the UE during that specific connection period (e.g., from UE context setup to UE context release, or from successful UE context establishment), and can use such reported RAN power consumption to formulate some policies, such as charging policies based on power consumption limit controls.

[0036] Figure 5 An exemplary message flow and network element interaction according to this embodiment are illustrated. The exemplary method may include some or all of the following steps.

[0037] Step 1: The UE initiates the PDU session setup process between the UE, gNB, and CN.

[0038] Step 2: The AMF sends a message to the gNB (e.g., an Initial Context Setting Request message). This message may include an energy consumption measurement configuration to request the gNB (or RAN) to measure the energy consumption used to serve the UE. Specifically, the energy consumption measurement configuration may indicate or notify various energy measurement levels, which may include at least one of the following: ●UE Level: When indicated for the UE level, it indicates the RAN measurement / reporting of RAN power consumption measurements used to serve the UE. For example, the RAN count of all services associated with the UE (e.g., multiple PDU sessions, multiple QoS flows, multiple DRBs, etc.).

[0039] ●QoS Flow Level: When indicated for a QoS flow level, it indicates the RAN power consumption used by the RAN to measure / report for each QoS flow in the QoS flow list. The QoS flow list can be indicated in this message, or it can be predefined / preconfigured.

[0040] ●PDU Session Level: When indicated at the PDU session level, this message instructs the RAN to measure / report the RAN power consumption for each PDU session in the service PDU session list. The PDU session list can be indicated in this message or it can be predefined / preconfigured.

[0041] In some example implementations, measurements can be performed individually, for example, per QoS flow or per PDU session. In some example implementations, measurements can be performed as an aggregation of multiple services. For example, measurements can be performed against a sublist of multiple services.

[0042] Note that energy consumption measurements are applicable to a specific duration. This duration can be, for example, the lifecycle of a service (e.g., from service startup / initiation to service release / termination).

[0043] Note that in this embodiment, if the AMF requests a UE-level energy consumption report, only the UE-level energy consumption indication will appear in the energy consumption measurement configuration.

[0044] Step 3: gNB configures resources for the connection between UE and gNB.

[0045] Step 4: The gNB sends an Initial Context Setup Response message to the AMF to notify that the UE context has been successfully set at the gNB.

[0046] Step 5: During the duration of the service provided by the gNB to the UE (i.e., the service lifecycle for the UE), the gNB, as requested by the AMF, measures the energy consumption of network resources in the RAN for serving the UE. Note that network resources include, but are not limited to, network nodes, network elements, and network entities in the RAN, which can be in hardware, software, or a combination thereof.

[0047] Step 6: After the data transmission between the core network (e.g., AMF) and the UE is completed, the AMF decides to release the logical NG connection associated with the UE.

[0048] Step 7: The AMF sends a message to the gNB (e.g., a UE context release command message) to release all resources associated with the UE.

[0049] Step 8: The gNB sends a message to the AMF (e.g., a UE context release complete message). This message may carry the measured energy consumption as requested / configured in Step 2. The measured energy consumption may include at least one of the following: ● The total energy consumed by network resources in the RAN to serve the UE.

[0050] ● The total energy consumed by network resources in the RAN for the QoS flow list serving the UE.

[0051] ● The total energy consumed by network resources in the RAN for the PDU session list serving the UE.

[0052] ● The total energy consumed by network resources in the RAN for the DRB list of serving UEs.

[0053] In this disclosure, when reporting energy consumption for a service, an identifier for that service can be indicated in the reporting message. For example, refer to... Figure 4B If the energy consumption measurement is for one or more QoS flows, the reporting message can be in the form of "QoS flow 1: Energy consumption information X; QoS flow 2: Energy consumption information Y".

[0054] The energy consumption measurement results sent to the core network can be based on the measurement configuration settings in step 2. Alternatively, the content to be reported can be configured separately, for example, by another message from the core network. Alternatively, the content to be reported can be predefined or pre-configured.

[0055] For example, in step 2, the AMF can send an Initial Context Setup Request message to the gNB to configure or indicate that power consumption measurement will be performed at the UE level. Then, in step 8, the gNB can send power consumption information to the AMF, which is the total energy consumed by network resources in the RAN to serve the UE.

[0056] This embodiment applies to, but is not limited to, UE-level power consumption configuration and reporting.

[0057] Example 2: RAN Energy Consumption Report In this embodiment, the AMF requests and configures RAN-side energy consumption measurement by including energy consumption measurement configuration in the NGAP request message sent to the gNB for setting up a PDU session or QoS flow. The NGAP request message may include, for example, an INITIAL UE CONTEX SETUP REQUEST message, a PDU SESSION RESOURCE SETUP REQUEST message, a PDU SESSION RESOURCE MODIFICATION REQUEST message, etc. Upon request, the gNB begins measuring the RAN energy consumption of the PDU session or QoS flow until the AMF sends an NGAP message (e.g., a UE CONTEXT RELEASE COMMAND message, a PDU SESSION RESOURCE RELEASE COMMAND message, a PDU SESSION RESOURCE MODIFY REQUEST message, etc.) to release the PDU session or QoS flow. The gNB reports the total measured energy consumption of a PDU session or QoS flow to the AMF via corresponding NGAP response messages sent to the AMF (e.g., UE CONTEXT RELEASE COMPLETE, PDU SESSION RESOURCE RELEASE RESPONSE, PDU SESSION RESOURCE MODIFY RESPONSE). The CN can then know the RAN energy consumption for a specific QoS flow(s) or PDU session(s) for the UE and use this reported RAN energy consumption to formulate policies, such as applying charging policies based on energy consumption limits.

[0058] Figure 6 An exemplary message flow and network element interaction according to this embodiment are illustrated. The exemplary method may include some or all of the following steps.

[0059] Step 1: The UE initiates the PDU session setup process between the UE, gNB, and CN.

[0060] Step 2: The AMF sends a message (e.g., an NGAP message) to the gNB. This message may carry an energy consumption measurement configuration to request the gNB (or RAN) to measure the energy consumption used to serve the UE. Specifically, the energy consumption measurement configuration may indicate or notify various energy measurement levels, which may include at least one of the following: ●UE Level: When indicated for the UE level, it indicates the RAN measurement / reporting of RAN power consumption measurements used to serve the UE. For example, the RAN count of all services associated with the UE (e.g., multiple PDU sessions, multiple QoS flows, multiple DRBs, etc.).

[0061] ●QoS Flow Level: When indicated for a QoS flow level, it instructs the RAN to measure / report RAN power consumption for a serving QoS flow list. The QoS flow list can be indicated by this message, or it can be predefined / preconfigured.

[0062] ●PDU Session Level: When indicated at the PDU session level, it instructs the RAN to measure / report RAN energy consumption for a list of serving PDU sessions. The list of PDU sessions can be indicated by a message or can be predefined / preconfigured.

[0063] Note that in this embodiment, if the QoS stream and / or PDU session level energy consumption report is requested by the AMF, then the energy consumption measurement configuration will include QoS stream level and / or PDU session level energy consumption indications.

[0064] Step 3: gNB configures resources for the connection between UE and gNB.

[0065] Step 4: The gNB sends a response message in response to the NGAP message in Step 2. The appropriate response message is sent depending on the specific NGAP message sent in Step 2.

[0066] Table 2 below shows an example message when the requested energy consumption measurement is at the PDU session level.

[0067] Table 2

[0068] Table 3 below shows an example message when the requested energy consumption measurement is for a QoS flow level.

[0069] Table 3

[0070] Step 5: During the duration of the service provided by the gNB to the UE (e.g., the service lifecycle for the UE), the gNB, as requested by the AMF, measures the energy consumption of one or more network resources used for the indicated QoS flow(s) and / or one or more PDU sessions(s) for the UE. Note that network resources include, but are not limited to, network nodes, network elements, and network entities in the RAN. For example, as requested in Step 2, energy consumption measurements can be performed at the QoS flow level or the PDU session level.

[0071] Step 6: The AMF decides to release resources that have been established for one or more PDU sessions, one or more QoS flows, or one or more DRBs for the UE.

[0072] Step 7: The AMF sends an NGAP message to the gNB to release the PDU session or QoS flow for the UE.

[0073] Step 8: The gNB sends a response message to the NGAP message in Step 7. This message may carry the measured energy consumption as requested / configured in Step 2. The measured energy consumption may include at least one of the following: ● The total energy consumed by network resources in the RAN to serve the UE.

[0074] ● The total energy consumed by network resources in the RAN for the QoS flow list serving the UE.

[0075] ● The total energy consumed by network resources in the RAN for the PDU session list serving the UE.

[0076] ● The total energy consumed by network resources in the RAN for the DRB list of serving UEs.

[0077] Table 4 below shows example messages in steps 7 and 8 when the requested energy consumption measurement is at the PDU session level.

[0078] Table 4

[0079] Table 5 below shows example messages in steps 7 and 8 when the requested energy consumption measurement is at the QoS session level.

[0080] Table 5

[0081] This embodiment can be applied to, but is not limited to, power consumption configuration and reporting at the PDU session level and QoS stream level.

[0082] Example 3: RAN Energy Consumption Report: CU-DU Split Base Station In this embodiment, the base station is implemented in a distributed architecture and can be divided into two entities, referred to as the Centralized Unit (CU) and the Distributed Unit (DU). From the perspective of the protocol stack, the CU provides support for the higher layers of the protocol stack (e.g., SDAP (Service Data Adaptation Protocol), PDCP (Packet Data Convergence Protocol), and RRC (Radio Resource Control), while the DU provides support for the lower layers of the protocol stack (e.g., RLC (Radio Link Control), MAC (Media Access Control), and the physical layer). A base station such as a gNB may include one CU and multiple DUs. The CU can be further divided into a control plane (e.g., the CU control plane (CUCP), or gNB-CU-CP) and a user plane (e.g., the CU user plane (CUUP), or gNB-CU-UP). The CUCP and CUUP can be implemented as different hardware or software entities, or they can share the same hardware entity but be implemented as different logical entities. Therefore, due to the split architecture, when performing energy consumption measurement and reporting, measurement tasks may be assigned to various entities within the base station. For example, the CU and DU can each measure the energy consumption of the UE they serve (or the services provided by the UE). Furthermore, within the CU, CUCP and CUUP can be responsible for measuring energy consumption in the control plane and user plane, respectively.

[0083] In some example implementations, the CU can be used as a gateway to receive energy consumption measurement configurations from, for example, the core network and distribute the configurations to one or more DUs.

[0084] In some example implementations, the CUCP can be used as a gateway to receive energy consumption measurement configurations from, for example, the core network and distribute those configurations to the CUUP and(one or more) DUs.

[0085] Figure 7 An exemplary message flow and network element interaction according to this embodiment are illustrated. The exemplary method may include some or all of the following steps.

[0086] Step 1: The UE initiates the PDU session setup process between the UE, gNB, and CN (such as AMF).

[0087] Step 2: The AMF sends a message (such as an Initial Context Setting Request message) to the gNB-CU-CP (hereinafter also referred to as CUCP). This message may carry an energy consumption measurement configuration to request the gNB (or RAN) to measure the energy consumption used to serve the UE. Specifically, the energy consumption measurement configuration may indicate or notify various energy measurement levels, which may include at least one of the following: ●UE level; ●QoS flow level; ●PDU session level; or ●DRB level.

[0088] These levels of detail can be found in the previous embodiments, and will be omitted here.

[0089] Step 3: As a gateway, CUCP can forward the energy consumption measurement configuration to gNB-CU-UP (gNB Control Unit - User Plane, hereinafter also referred to as CUUP). Specifically, CUCP can send a message (e.g., a Bearer CONTEXT SETUP REQUEST message) to CUUP. This message can carry the energy consumption measurement configuration to request CUUP (at the requested level) to measure the energy consumed by CUUP for serving the UE. The energy consumption measurement configuration can indicate or notify various energy measurement levels on the CUUP side, which can include at least one of the following: UE level; QoS flow level; PDU session level; or DRB level. Details of these levels can be found in the previous embodiments and are omitted here.

[0090] Step 4: CUUP responds to CUCP with, for example, a Bearer CONTEXT SETUP RESPONSE message to notify of the successful establishment of the requested resource.

[0091] Step 5: CUCP can also forward the energy consumption measurement configuration to the gNB-DU (hereinafter also referred to as DU). Specifically, CUCP can send a message (such as a UE CONTEXT SETUP REQUEST message) to the DU. This message can carry the energy consumption measurement configuration to request the DU (at the requested level) to measure the energy consumption of the serving UE at the DU. The energy consumption measurement configuration can indicate or notify the DU side of various energy measurement levels, which can include at least one of the following: UE level; QoS flow level; PDU session level; or DRB level.

[0092] In this disclosure, energy consumption can be measured when a measurement is performed. Alternatively, energy efficiency can be measured. For example, energy consumption needs to be measured for QoS flow 1; and / or energy efficiency needs to be measured for QoS flow 2.

[0093] Step 6: DU replies to CUCP with, for example, a UE CONTEXT SETUP RESPONSE message to notify of the successful setup of the UE context.

[0094] Step 7: DU configures resources for the connection between the UE and gNB.

[0095] Step 8: gNB-CU-CP can reply to AMF by sending, for example, an Initial Context Setup Response message to notify the UE at gNB that the context setting was successful.

[0096] Step 9: During the duration of the service provided by the gNB to the UE, the gNB-CU-CP, CUUP, and DU measure their respective energy consumption (or energy efficiency) associated with serving the UE (or the service provided by the UE) and perform the measurement at the requested level.

[0097] Step 10: Data transmission between AMF and UE is completed, and AMF decides to release UE.

[0098] Step 11: The AMF can send a message to the gNB-CU-CP (e.g., a UE context release command (UE CONTEXTRELEASE COMMAND) message) to release all resources associated with the UE.

[0099] Step 12: gNB-CU-CP can send a message to DU (e.g., UE context release command (UE CONTEXTRELEASE COMMAND) message) to release (on the DU side) all resources associated with the UE.

[0100] Step 13: The DU can send a message such as "UE CONTEXT RELEASE COMPLETE" to the gNB-CU-CP. This message can carry the energy consumption (or energy efficiency) measured on the DU side. The measured energy consumption can include the total energy consumed by network resources for serving the UE on the DU side. The measurement results can follow the same level indicated in the measurement configuration.

[0101] Step 14: gNB-CU-CP can send a Bearer Context Release Command (BEARER CONTEXTRELEASE COMMAND) message to CUUP to release (on the CUUP side) all resources associated with the UE.

[0102] Step 15: The CUUP can send a message such as "BEARER CONTEXTRELEASE COMPLETE" to the gNB-CU-CP. This message can carry the energy consumption (or energy efficiency) measured on the CUUP side. The measured energy consumption can include the total energy consumed by network resources for serving the UE on the CUUP side. The measurement results can follow the same level as indicated in the measurement configuration in Step 3.

[0103] Step 16: After collecting energy consumption (or energy efficiency), CUCP calculates the total energy consumption as the sum of the energy consumption at DU, CUUP and CUCP.

[0104] In some example implementations, the power consumption of the control plane CUCP is much smaller than that of other entities such as CUUP and DU. Therefore, the base station (e.g., gNB) can assume that the power consumption of the gNB-CU-CP is 0. Alternatively, if the power consumption of the CUCP is less than a pre-configured or predefined threshold, the base station can assume that the power consumption of the CUCP is 0.

[0105] Step 17: The gNB-CU-CP can send a message to the AMF (e.g., a UE CONTEXTRELEASE COMPLETE message). This message can carry measured energy consumption, if requested. The measured energy consumption is the total energy consumed by the base station (CUCP, CUUP, and DU) for serving the UE, the UE's QoS flow list, the UE's PDU session list, or the UE's DRB list.

[0106] This embodiment can be applied to, but is not limited to, UE-level power consumption configuration and reporting.

[0107] Example 4: RAN Energy Consumption Report: CU-DU Split Base Station Similar to Example 3, in this example, the base station has a distributed architecture and can be divided into CU and DU.

[0108] The AMF requests and configures energy consumption measurement by including energy consumption measurement configuration in the NGAP message sent to the gNB-CU for PDU session or QoS flow settings. The NGAP message may include an Initial UECONTEX SETUP REQUEST message, a PDU SESSION RESOURCE SETUPREQUEST message, and a PDU SESSION RESOURCE MODIFICATION REQUEST message, among others. Upon receiving the request, the gNB-CU-CP instructs the gNB-CU-UP and gNB-DU to configure the energy consumption measurement. The gNB-CU-CP, gNB-CU-UP, and gNB-DU then measure energy consumption as requested until the AMF sends an NGAP message to release the PDU session or QoS flow. NGAP messages may include, for example, UE CONTEXT RELEASE COMMAND messages, PDU SESSION RESOURCE RELEASE COMMAND messages, and PDU SESSION RESOURCE MODIFY REQUEST messages. The gNB-CU-CP sends F1AP and E1AP messages to the gNB-DU and gNB-CU-UP respectively to release the corresponding resources. The gNB-DU and gNB-CU-UP report their measured energy consumption to the gNB-CU-CP by sending corresponding F1AP and E1AP response messages. gNB-CU-CP calculates the sum of the energy consumption measured at gNB-CU-CP, gNB-CU-UP, and gNB-DU, and reports the total measured energy consumption of the PDU session or QoS flow to the AMF through the corresponding NGAP response messages (e.g., UE CONTEXT RELEASE COMPLETE message, PDU SESSION RESOURCE RELEASE RESPONSE message, PDU SESSION RESOURCE MODIFYRESPONSE message).

[0109] In some example implementations, the CU can be used as a gateway to receive energy consumption measurement configurations from, for example, the core network and distribute the configurations to one or more DUs.

[0110] In some example implementations, the CUCP can be used as a gateway to receive energy consumption measurement configurations from, for example, the core network and distribute those configurations to the CUUP and(one or more) DUs.

[0111] Figure 8A and 8B An exemplary message flow and network element interaction according to this embodiment are illustrated. The exemplary method may include some or all of the following steps.

[0112] Step 1: The UE initiates the PDU session setup process between the UE, gNB, and CN (such as AMF).

[0113] Step 2: The AMF sends a message (such as an NGAP message) to the gNB-CU-CP to set up the PDU session for the QoS flow. This message may carry an energy consumption measurement configuration to request the gNB (or RAN) to measure the energy consumption used to serve the UE (or the UE's service). The energy consumption measurement configuration may indicate or notify the gNB side of various energy measurement levels, which may include at least one of the following: UE level; QoS flow level; PDU session level; or DRB level. Details of these levels can be found in the previous embodiments and are omitted here.

[0114] In some example implementations, when configuring power consumption measurement at the PDU session level, the request message may include: an INITIAL CONTEXT SETUP REQUEST message and a PDU SESSION RESOURCE SETUP REQUEST message. When configuring power consumption measurement at the QoS flow level, the request message may include: an INITIAL CONTEXT SETUP REQUEST message, a PDU SESSION RESOURCE SETUP REQUEST message, and a PDU SESSION RESOURCE MODIFY REQUEST message.

[0115] Step 3: CUCP, acting as a gateway, can forward the energy consumption measurement configuration to CUUP. Specifically, CUCP can send an E1 Application Protocol (E1AP) message (e.g., a Bearer Context SETUP REQUEST message or a Bearer Context MODIFICATION REQUEST message) to CUUP. This message can carry the energy consumption measurement configuration to request CUUP (at the requested level) to measure the energy consumed by CUUP for serving the UE. The energy consumption measurement configuration can indicate or notify CUUP of various energy measurement levels, which can include at least one of the following: UE level; QoS flow level; PDU session level; or DRB level. Details of these levels can be found in the previous embodiments and are omitted here.

[0116] Step 4: CUUP replies to CUCP with the corresponding E1AP message (such as BearerContextSetupResponse message, BearerContextMoDIFICATIONResponse message, etc.) to notify that the requested resource has been successfully established.

[0117] Step 5: CUCP can also send / forward energy consumption measurement configurations to the DU. Specifically, CUCP can send F1 Application Protocol (F1AP) messages (e.g., UE CONTEXTSETUP REQUEST messages, UE CONTEXT MODIFICATION REQUEST messages, etc.) to the DU. This message can carry the energy consumption measurement configuration to request the DU (at the requested level) to measure the energy consumption of the serving UE at the DU. The energy consumption measurement configuration can indicate or notify the DU side of various energy measurement levels, which can include at least one of the following: UE level; QoS flow level; PDU session level; or DRB level.

[0118] In some example implementations, energy consumption can be measured when the measurement is performed. Alternatively, energy efficiency can be measured. For example, energy consumption needs to be measured for QoS flow 1; and / or energy efficiency needs to be measured for QoS flow 2.

[0119] Step 6: gNB-DU replies to CUCP with the corresponding F1AP message (such as UE CONTEXTSETUP RESPONSE message or UE CONTEXT MODIFICATION RESPONSE message) to notify DRB of the successful setup.

[0120] Step 7: DU configures resources for the connection between the UE and gNB.

[0121] Step 8: gNB-CU-CP can reply to AMF by sending, for example, an NGAP response message to notify that the UE context setting at gNB was successful.

[0122] In some example implementations, when energy consumption measurement is at the PDU session level, the NGAP response message may include an INITIAL CONTEXT SETUP RESPONSE message, a PDU SESSION RESOURCE SETUP RESPONSE message, etc. When energy consumption measurement is at the QoS flow level, the NGAP response message may include an INITIAL CONTEXT SETUP RESPONSE message, a PDU SESSION RESOURCE SETUP RESPONSE message, and a PDU SESSION RESOURCE MODIFY RESPONSE message, etc.

[0123] Steps 9-11: These three steps can be performed in parallel by three entities. During the duration of the gNB providing services (one or more) to the UE, gNB-CU-CP, CUUP, and DU measure their respective energy consumption (or energy efficiency) associated with the serving UE, and perform the measurement at the requested level.

[0124] Step 12: The AMF decides to release resources that have been established for the PDU session or QoS flow associated with the UE.

[0125] Step 13: The AMF sends an NGAP message to the gNB-CU-CP to release resources allocated for the PDU session or QoS flow associated with the UE.

[0126] In some example implementations, when power consumption measurement is at the PDU session level, the NGAP message may include a UE CONTEXT RELEASE COMMAND message, a PDU session resource release COMMAND message, etc. When power consumption measurement is at the QoS flow level, the NGAP message may include a UE CONTEXT RELEASE COMMAND message, a PDU session resource release COMMAND message, and a PDU session resource modification request message, etc.

[0127] Step 14: gNB-CU-CP can send F1AP messages (such as UE CONTEXTRELEASE COMMAND message, UE CONTEXT MODIFICATION REQUEST message, etc.) to DU to release the DRB established for the PDU session or QoS flow associated with the UE.

[0128] Step 15: The DU can send the corresponding F1AP response message (such as UEContext Release Complete message, UEContext Modification Response message, etc.) to the gNB-CU-CP. This message can carry the energy consumption (or energy efficiency) measured on the DU side. The measured energy consumption can include the total energy consumed by network resources for serving the UE on the DU side. The measurement results can follow the same level indicated in the measurement configuration.

[0129] In some example implementations, the response message may carry energy consumption information for the QoS flow list and / or DRB list. The energy consumption information may also use QoS flow identifiers or DRB identifiers to identify the corresponding QoS flow or DRB.

[0130] In some example implementations, the response message may carry energy efficiency information for a QoS flow list and / or a DRB list. The energy efficiency information may also use a QoS flow identifier or a DRB identifier to identify the corresponding QoS flow or DRB.

[0131] Step 16: CUCP receives energy consumption information or energy efficiency information from DU. When DU sends DRB-level energy consumption information or DRB-level energy efficiency information, CUCP may need to calculate the corresponding energy consumption in the QoS flow level.

[0132] For example, if DU sends DRB-level power consumption, CUCP can use the following formula to calculate the power consumption for a QoS flow:

[0133] in, For power consumption of QoS flow 1; This represents the data volume for QoS stream 1. The amount of data in the DRB associated with QoS flow 1; and This refers to the energy consumption of the DRB associated with QoS flow 1.

[0134] For example, if DU sends DRB-level energy efficiency, CUCP can use the following formula to calculate the energy consumption for QoS flows:

[0135] in, For power consumption of QoS flow 1; For the data volume of QoS stream 1; and Energy efficiency for DRBs associated with QoS flow 1.

[0136] In addition, for each requested PDU session, gNB-CU-CP can calculate the sum of the energy consumption of all QoS flows belonging to that PDU session to obtain the PDU session energy consumption.

[0137] Step 17: gNB-CU-CP can send E1AP messages (such as Bearer Context Release Command (BEARERCONTEXT RELEASE COMMAND) messages, Bearer Context Modification Request (BEARER CONTEXT MODIFICATIONREQUEST) messages to CUUP to release (on the CUUP side) all resources established for PDU sessions or QoS flows.

[0138] Step 18: The CUUP can send the corresponding E1AP response message to the gNB-CU-CP (such as the Bearer Context Release Complete message, the Bearer Context Modification Response message, etc.). This message can carry the energy consumption measured on the CUUP side for serving PDU sessions or QoS flows.

[0139] In some example implementations, the response message may carry energy consumption information for a list of QoS flows. This energy consumption information can be identified using a QoS flow identifier to denote the corresponding QoS flow.

[0140] In some example implementations, the response message may carry energy consumption information for a list of PDU sessions. The energy consumption information can be identified using a PDU session identifier.

[0141] Step 19: After collecting the energy consumption of DU and CUUP, CUCP calculates the total energy consumption as the sum of the energy consumption at DU, CUUP and CUCP.

[0142] In some example implementations, the power consumption of the control plane CUCP is much smaller than that of other entities such as CUUP and DU. Therefore, the base station (e.g., gNB) can assume that the power consumption of the gNB-CU-CP is 0. Alternatively, if the power consumption of the CUCP is less than a pre-configured or predefined threshold, the base station can assume that the power consumption of the CUCP is 0.

[0143] Step 20: The gNB-CU-CP sends an NGAP response message to the AMF. This message may, if requested, carry measured energy consumption. For example, the measured energy consumption is the total energy consumed by the base stations (CUCP, CUUP, and DU) for serving the UE's QoS flow list or UE's PDU session list. Similarly, an identifier for each QoS flow or PDU session may be indicated in the measured energy consumption information.

[0144] In some example implementations, when configuring power consumption measurement at the PDU session level, the corresponding NGAP response message may include a UE CONTEXT RELEASE COMPLETE message and a PDU SESSION RESOURCE RELEASE RESPONSE message. When configuring power consumption measurement at the QoS flow level, the NGAP response message may include a UE CONTEXT RELEASE COMPLETE message, a PDU SESSION RESOURCE RELEASE RESPONSE message, and a PDU SESSION RESOURCE MODIFY RESPONSE message.

[0145] This embodiment can be applied to, but is not limited to, power consumption configuration and reporting at the PDU session level and QoS stream level.

[0146] Example 5: RAN Energy Consumption Reporting – NG-Based Handover This embodiment covers UE handover scenarios based on NG.

[0147] During NG-based handover, RAN energy consumption measurement and reporting are considered. After the source gNB receives the energy consumption measurement configuration from the AMF (as described in the previous embodiment) or from another gNB (e.g., in the case of Xn-based handover in the next embodiment), the source gNB measures the requested energy consumption and, in the case of NG-based handover, transmits the measurement results to the AMF via, for example, a "HANDOVERREQUIRED" message. The energy consumption measurement configuration is relayed to the target gNB via a HANDOVERREQUEST message sent by the AMF. After the UE successfully hands over to the target gNB, the target gNB continues to measure the energy consumption of the UE and / or PDU sessions and / or QoS flows based on the received energy consumption measurement configuration until the AMF releases the corresponding resources or a new handover occurs. In this way, when multiple base stations provide services to the UE, the core network can track the total energy consumed by these base stations for serving the UE.

[0148] Figure 9 An exemplary message flow and network element interaction according to this embodiment are illustrated. The exemplary method may include some or all of the following steps.

[0149] Step 1: The source gNB has received the energy consumption measurement configuration from the AMF during the PDU session / QoS flow setup (e.g., as described in the previous embodiment); or the source gNB has received the energy consumption measurement configuration from another gNB during a previous Xn-based handover (see the following embodiment). The UE is currently being served by the source gNB, which, as requested, measures the energy consumed to serve the UE, and / or the PDU session, and / or the QoS flow (e.g., performing the measurement after the measurement level has been configured by the core network).

[0150] Step 2: Due to UE mobility, a handover is required, and the source gNB determines the target gNB for this handover. If there is no Xn interface between the source gNB and the target gNB, an NG-based handover may occur. The source gNB sends a message (e.g., a "HANDOVER REQUIRED" message) to the AMF to prepare resources at the selected target gNB. This message may carry measured energy consumption information associated with the UE. For example, the measured energy consumption information may include at least one of the following: The total energy consumed by network resources in the source gNB used to serve the UE; Energy consumption for each QoS flow in the QoS flow list, where each QoS flow is identified by a QoS flow identifier; or Energy consumption for each PDU session in the PDU session list, where each PDU session is identified by a PDU session identifier.

[0151] Step 3: The AMF stores the received measured energy consumption and sends a handover request message to the target gNB to request resource preparation. The handover request message may carry energy consumption measurement configuration to instruct / notify the target gNB to measure the energy consumption of the UE, and / or PDU sessions, and / or QoS flows. See the previous examples for details on energy consumption measurement configuration.

[0152] Step 4: If the target gNB accepts the handover, it can reply to the AMF with a handover request acknowledgment message.

[0153] Step 5: The UE switches from the source gNB to the target gNB.

[0154] Step 6: The target gNB continues to measure the power consumption of the UE and / or PDU sessions and / or QoS flows, as requested. Measurements may stop when the target gNB receives an instruction from the AMF to release the corresponding resources for the UE, or when a new handover occurs.

[0155] Step 7: Similar to the previous embodiments, the AMF can send a message (e.g., an NGAP message) to the target gNB to release the resources allocated to the UE (or the UE's PDU session, QoS flow).

[0156] Step 8: Similar to the previous embodiments, the target gNB can send a message (e.g., an NGAP response message) to the AMF. This message can, as requested, carry the measured energy consumption at the target gNB. The measured energy consumption can include at least one of the following: ● The total energy consumed by network resources in the target gNB used to serve the UE; ● Energy consumption at the target gNB for each QoS flow in the QoS flow list, where each QoS flow is identified by a QoS flow identifier; or ● Energy consumption for each PDU session in the PDU session list at the target gNB, where each PDU session is identified by a PDU session identifier.

[0157] Note: CN calculates the final power consumption of the UE (or one or more of the UE's services, such as one or more PDU sessions, one or more QoS flows) by adding the results of the source gNB and the target gNB.

[0158] In this embodiment, the source gNB and the target gNB can be in the same radio access network (RAN) or in different RANs.

[0159] Example 6: RAN Energy Consumption Reporting – Xn-based Handover This embodiment covers UE handover scenarios based on Xn.

[0160] During Xn-based (or Xn interface) handover, RAN energy consumption measurement and reporting are considered. Energy consumption measured at the source gNB and / or energy consumption measurement configuration are transmitted to the target gNB in ​​messages such as handover request messages. After a successful UE handover to the target gNB, the target gNB continues to measure the energy consumption of the UE and / or PDU sessions and / or QoS flows based on the received energy consumption measurement configuration until the AMF releases the corresponding resources or a new handover occurs. Then, even during UE handover, the core network can know the RAN energy consumption of the UE, or a specific QoS flow of the UE, or the UE's PDU session. The core network can use this reported RAN energy consumption to formulate policies, such as controlling application charging policies based on energy consumption limits.

[0161] Figure 10 An exemplary message flow and network element interaction according to this embodiment are illustrated. The exemplary method may include some or all of the following steps.

[0162] Step 1: The UE is served by the source gNB, which performs power consumption measurements on the UE and / or PDU sessions and / or QoS flows upon request. See the previous examples for details on how to configure gNB power consumption measurements.

[0163] Step 2: Due to UE mobility, a handover is required, and the source gNB determines the target gNB for this handover. If an Xn interface exists between the source and target gNBs, an Xn-based handover may occur. The source gNB sends a message (e.g., a HANDOVER REQUEST message) to the target gNB to prepare resources. This message may carry measured energy consumption information associated with the UE. For example, the measured energy consumption information may include at least one of the following: ● The total energy consumed by network resources in the source gNB used to serve the UE; ● Power consumption for each QoS flow in the QoS flow list, where each QoS flow is identified by a QoS flow identifier; or ● Energy consumption for each PDU session in the PDU session list, where each PDU session is identified by a PDU session identifier.

[0164] The message may also carry energy consumption measurement configuration to instruct / notify the target gNB to measure the energy consumption of the UE, and / or PDU sessions, and / or QoS flows. See the preceding examples for details on energy consumption measurement configuration.

[0165] Step 3: If the target gNB accepts the handover, it sends a handover request confirmation message to the source gNB.

[0166] Step 4: The UE switches from the source gNB to the target gNB.

[0167] Step 5: The target gNB sends a PATH SWITCH REQUEST message to the AMF, declaring itself as the new service gNB.

[0168] Step 6: After the UE successfully hands over from the source gNB, the target gNB measures the energy consumption of the UE, and / or the UE's PDU sessions, and / or the UE's QoS flows based on the received energy consumption measurement configuration, until it receives an instruction from the AMF to release the corresponding resources, or until the next handover occurs.

[0169] Step 7: Similar to step 7 in Example 5.

[0170] Step 8: Similar to step 8 in Example 5.

[0171] The target gNB calculates the final measured energy consumption of the UE, and / or one or more PDU sessions and / or one or more QoS flows by summing the energy consumption measured from the source gNB and the energy consumption measured at the target gNB, and reports it to the core network. For example, the target gNB receives the energy consumed by the source gNB for serving QoS flow 1 and adds the received energy consumption to the energy consumed by itself for serving QoS flow 1.

[0172] In this embodiment, the source gNB and the target gNB can be in the same radio access network (RAN) or in different RANs.

[0173] The method according to embodiments of this disclosure includes some or all of the following steps: Step 1: receiving a first message from a second network element, the first message carrying an energy consumption measurement configuration for measuring energy consumption associated with a serving user equipment (UE); Step 2: obtaining energy consumption information for energy consumption associated with the serving UE based on the energy consumption measurement configuration; and Step 3: sending second information to a third network element, the second information carrying energy consumption information associated with the serving UE.

[0174] In any part or combination of the above embodiments, the energy consumption measurement configuration indicates that the energy consumption associated with the serving UE will be measured at at least one of the following levels: UE level; Quality of Service (QoS) stream level; Packet Data Unit (PDU) session level; or Data Radio Bearer (DRB) level.

[0175] In any part or combination of the above embodiments, the granularity of energy consumption information follows the same measurement level as indicated in the energy consumption measurement configuration.

[0176] In any part or combination of the above embodiments, the energy consumption information includes at least one of the following: the total energy consumed by the first network element for serving the UE; the total energy consumed by the first network element for each QoS flow in the QoS flow list of the serving UE; the total energy consumed by the first network element for each PDU session in the PDU session list of the serving UE; or the total energy consumed by the first network element for each DRB in the DRB list of the serving UE.

[0177] This disclosure describes various embodiments for configuring energy consumption measurement and / or reporting. The configuration can be sent from the core network to a base station or an element of a base station. The configuration can also be sent from one element of a base station to another element of the base station. The configuration can also be sent from a source base station to a target base station. Various embodiments can be combined to form combined embodiments. For example, the energy consumption measurement configuration can initially be configured by a core network element to a first base station, and then during a handover process, the energy consumption measurement configuration can be configured from the first base station to a second base station, wherein the handover process can include Xn-based (or Xn-interface-based) handover and NG-based (or NG-interface-based) switching. Furthermore, the various embodiments in this disclosure are for illustrative purposes and can be divided into multiple sub-solutions that include some features of the embodiments.

[0178] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter can be embodied in a variety of different forms, and therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the example embodiments described herein. A reasonably broad scope is intended for the claimed or covered subject matter. For example, the subject matter can be embodied in particular as a method, apparatus, component, system, or non-transitory computer-readable medium for storing computer code. Therefore, embodiments can take the form of, for example, hardware, software, firmware, storage media, or any combination thereof. For example, the above method embodiments can be implemented by executing computer code stored in memory, by a component, apparatus, or system including memory and a processor.

[0179] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied in the context and go beyond their expressly stated meanings. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include, in whole or in part, combinations of exemplary embodiments.

[0180] Generally, terms can be understood, at least in part, based on their usage in the context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings that can depend at least in part on the context in which they are used. Typically, “or,” when used to associate a list such as A, B, or C, is intended to mean A, B, and C (inclusive meaning) and A, B, or C (in exclusive meaning). Furthermore, depending at least in part on the context, the term “one or more,” as used herein, can be used to describe any feature, structure, or characteristic in a singular sense, or a combination of features, structures, or characteristics in a plural sense. Similarly, depending at least in part on the context, terms such as “a,” “an,” or “the” can be understood to convey either a singular or a plural usage. Moreover, the term “based on” can be understood not necessarily to convey an exclusive set of factors, but rather, alternatively, also depending at least in part on the context, may allow for the presence of additional factors that are not necessarily explicitly described.

[0181] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable using this solution should be included or are all included in any single implementation thereof. Rather, the language referring to features and advantages is to be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, the discussion of features and advantages, and similar language throughout this specification, may, but do not necessarily, refer to the same embodiments.

[0182] Furthermore, the features, advantages, or characteristics described in this solution can be combined in one or more embodiments in any suitable manner. Those skilled in the art will recognize from the description herein that this solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in all embodiments of this solution may be recognized in certain embodiments.

Claims

1. A method for wireless communication, performed by a first network element, the method comprising: Receive a first message from the second network element, the first message carrying an energy consumption measurement configuration for measuring energy consumption associated with the serving user equipment (UE); Based on the energy consumption measurement configuration, energy consumption information is obtained for the energy consumption associated with serving the UE; as well as Send a second message to a third network element, the second message carrying the energy consumption information associated with the UE.

2. The method according to claim 1, wherein, The energy consumption measurement configuration indicates that the energy consumption associated with serving the UE will be measured at at least one of the following levels: UE level; Quality of Service (QoS) flow level; Packet Data Unit (PDU) session level; or Data Radio Bearer (DRB) level.

3. The method according to claim 1, wherein, The granularity of the energy consumption information follows the same measurement level as indicated in the energy consumption measurement configuration.

4. The method according to claim 1, wherein, The energy consumption information includes at least one of the following: The total energy consumed by the first network element to serve the UE; The total energy consumed by the first network element for each QoS flow in the QoS flow list serving the UE; The total energy consumed by the first network element for each PDU session in the PDU session list serving the UE; or The total energy consumed by the first network element for each DRB in the DRB list serving the UE.

5. The method according to any one of claims 1 to 4, wherein, Receiving the first message includes: During the resource setting process for the UE, a first message carrying the energy consumption measurement configuration is received from the second network element.

6. The method according to claim 5, wherein, The first message includes at least one of the following: Next Generation Application Protocol (NGAP) request message; Initial context setting request message; Switching request messages based on the NG interface; or Xn Application Protocol (XnAP) Switching Request Message.

7. The method according to any one of claims 1 to 4, wherein, Sending the second message includes: During the resource release process for the UE, a second message carrying the energy consumption information associated with serving the UE is sent to the third network element; or During the handover process for the UE, a second message carrying the energy consumption information associated with serving the UE is sent to the third network element.

8. The method according to claim 7, wherein, The second message includes at least one of the following: An NGAP response message is used to resolve a resource release request for the UE; or The NGAP handover request message is used to request that the UE be handed over from the first network element to the target base station.

9. The method according to any one of claims 1 to 4, wherein, The energy consumption information includes the total energy consumed by one or more entities to serve the UE at the level indicated by the energy consumption measurement configuration, wherein the one or more entities include at least one of the following: The first network element; The first radio access network (RAN) to which the first network element belongs; or The second RAN is the target RAN that serves the UE after the handover process.

10. The method according to claim 9, wherein, At least one of the following conditions applies: When energy consumption measurement is at the UE level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the UE; When the energy consumption measurement is at the QoS flow level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the QoS flow; When the energy consumption measurement is at the PDU session level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the PDU session; or When the energy consumption measurement is at the DRB level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the DRB.

11. The method according to any one of claims 1 to 4, wherein, The first network element includes at least one of the following: a base station; a control unit (CU) of the base station; or a CU control plane (CUCP) of the base station, and the base station includes at least one of the following: a gNodeB (gNB); an eNodeB (eNB); an ng-eNodeB (ng-eNB); or a NodeB; and The second network element includes the core network element.

12. The method according to claim 11, wherein, The first message includes at least one of the following: Initial context setting request message; PDU session resource setting request message; or PDU Session Resource Modification Request (NGAP) message.

13. The method according to claim 11, wherein, The second message includes at least one of the following: UE context release complete message; PDU session resource release response message; or PDU session resource modification response NGAP message.

14. The method according to any one of claims 1 to 4, wherein, The first network element includes the base station control unit control plane (CUCP); and The second network element includes the core network element.

15. The method of claim 14, further comprising: A third message is sent to the CU user plane (CUUP) of the base station, the third message carrying a CUUP power consumption measurement configuration indicating that the power consumption associated with serving the UE will be measured at a measurement level including at least one of the following: UE level; Quality of Service (QoS) flow level; Packet Data Unit (PDU) session level; or Data Radio Bearer (DRB) level.

16. The method according to claim 15, wherein, The third message includes E1 Application Protocol (E1AP) messages.

17. The method of claim 15, further comprising: A fourth message is received from the CUUP, the fourth message carrying CUUP power consumption information associated with serving the UE, wherein the granularity of the CUUP power consumption information follows the same measurement level as indicated in the CUUP power consumption measurement configuration.

18. The method according to claim 17, wherein, The fourth message includes the E1AP message.

19. The method of claim 17, wherein, Obtaining the energy consumption information includes: The energy consumption information associated with serving the UE in the measurement level is obtained based on the following information: 1) the CUUP energy consumption information; 2) the CUCP energy consumption information.

20. The method of claim 14, further comprising: A fifth message is sent to the distributed unit (DU) of the base station, the fifth message carrying a DU power consumption measurement configuration indicating that the power consumption associated with serving the UE will be measured at at least one of the following levels: UE level; Quality of Service (QoS) flow level; Packet Data Unit (PDU) session level; or Data Radio Bearer (DRB) level.

21. The method according to claim 20, wherein, The fifth message includes the F1 Application Protocol (F1AP) message.

22. The method of claim 20, further comprising: A sixth message is received from the DU, the sixth message carrying DU power consumption information associated with serving the UE, wherein the granularity of the DU power consumption information follows the same measurement level as indicated in the DU power consumption measurement configuration.

23. The method according to claim 22, wherein, Obtaining the energy consumption information includes: The energy consumption information associated with serving the UE in the measurement level is obtained based on the following information: 1) the DU energy consumption information; 2) the CUCP energy consumption information.

24. The method according to any one of claims 1 to 4, wherein, The first network element is the source base station; The second network element is the core network element; The third network element is the same as the second network element; as well as The UE is currently in the process of switching from the source base station to the target base station.

25. The method according to claim 24, wherein, The second message includes a handover request message requesting that the UE be switched from the source base station to the target base station.

26. The method according to any one of claims 1 to 4, wherein, The first network element includes the target base station; The second network element includes the source base station; The third network element includes a core network element; and The UE is in the process of switching from the source base station to the target base station.

27. The method according to claim 26, wherein, The first message includes a handover request message requesting that the UE be switched from the source base station to the target base station.

28. The method according to claim 27, wherein, The first message also includes energy consumption information of the second network element serving the UE at a granularity configured by the third network element.

29. The method according to claim 28, wherein, Obtaining the energy consumption information includes: The energy consumed by the first network element to serve the UE is measured according to the measurement level indicated in the energy consumption measurement configuration. Based on the energy consumption information of the second network element, determine the energy consumed by the second network element; and The energy consumption information is defined as the sum of the energy consumed by the first network element and the energy consumed by the second network element.

30. The method according to any one of claims 1 to 4, wherein, The first network element includes the user plane control unit (CUUP) of the base station. The second network element includes the CUCP of the base station; and The third network element is the same as the second network element.

31. The method according to claim 30, wherein, The first message includes at least one of the following: Bearer context setting request message; or Carry the context modification request message; and The second message includes at least one of the following: The message indicating that the context has been released is complete; or Carry context modification response message.

32. The method of claim 30, wherein, The first message includes an E1AP message; and The second message includes an E1AP response message.

33. The method according to any one of claims 1 to 4, wherein, The first network element includes the DU of the base station; The second network element includes the CUCP of the base station; and The third network element is the same as the second network element.

34. The method according to claim 33, wherein, The first message includes at least one of the following: UE context setting request message; or UE context modification request message; and The second message includes at least one of the following: UE context release complete message; or UE context modification response message.

35. A method for wireless communication, performed by a first network element, the method comprising: Send a first message to the second network element, the first message carrying an energy consumption measurement configuration for measuring the energy consumption associated with the serving user equipment (UE); as well as A second message is received from a third network element, the second message carrying energy consumption information associated with serving the UE, wherein the energy consumption information is collected based on the energy consumption measurement configuration.

36. The method according to claim 35, wherein, The energy consumption measurement configuration indicates that the energy consumption associated with serving the UE will be measured at at least one of the following levels: UE level; Quality of Service (QoS) flow level; Packet Data Unit (PDU) session level; or Data Radio Bearer (DRB) level.

37. The method of claim 35, wherein, The granularity of the energy consumption information follows the same measurement level as indicated in the energy consumption measurement configuration.

38. The method according to claim 35, wherein, The energy consumption information includes at least one of the following: The total energy consumed by the second network element to serve the UE; The total energy consumed by the second network element for each QoS flow in the QoS flow list serving the UE; The total energy consumed by the second network element for each PDU session in the PDU session list serving the UE; or The total energy consumed by the second network element for each DRB in the DRB list serving the UE.

39. The method according to any one of claims 35 to 38, wherein, Sending the first message includes: During the resource setting process for the UE, a first message carrying the energy consumption measurement configuration is sent to the second network element.

40. The method according to claim 39, wherein, The first message includes at least one of the following: Next Generation Application Protocol (NGAP) request message; Initial context setting request message; Switching request messages based on the NG interface; or Xn Application Protocol (XnAP) Switching Request Message.

41. The method according to any one of claims 35 to 38, wherein, Receiving the second message includes: During the resource release process for the UE, the third network element receives a second message carrying energy consumption information associated with serving the UE; or During the handover process for the UE, the third network element receives a second message carrying the energy consumption information associated with serving the UE.

42. The method according to claim 41, wherein, The second message includes at least one of the following: An NGAP response message is used to resolve a resource release request for the UE; or The NGAP handover request message is used to request that the UE be handed over from the first network element to the target base station.

43. The method according to any one of claims 35 to 38, wherein, The energy consumption information includes the total energy consumed by one or more entities to serve the UE at the level indicated by the energy consumption measurement configuration, wherein the one or more entities include at least one of the following: The second network element; The second network element belongs to the first radio access network (RAN); or The second RAN is the target RAN that serves the UE after the handover process.

44. The method according to claim 43, wherein, At least one of the following conditions applies: When energy consumption measurement is at the UE level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the UE; When the energy consumption measurement is at the QoS flow level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the QoS flow; When the energy consumption measurement is at the PDU session level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the PDU session; or When the energy consumption measurement is at the DRB level, the energy consumption information indicates the total energy consumed by the one or more entities to serve the DRB.

45. The method according to any one of claims 35 to 38, wherein, The first network element includes at least one of the following: a core network element; a base station control unit (CU); or the base station's CU control plane (CUCP), and the base station includes at least one of the following: a gNodeB (gNB); an eNodeB (eNB); an ng-eNodeB (ng-eNB); or a NodeB; and The second network element includes at least one of the following: the base station; the CU user plane (CUUP) of the base station; or the distributed unit (DU) of the base station.

46. ​​The method according to claim 45, wherein, The first message includes at least one of the following: Initial context setting request message; PDU session resource setting request message; or PDU Session Resource Modification Request (NGAP) message.

47. The method according to claim 45, wherein, The second message includes at least one of the following: UE context release complete message; PDU session resource release response message; or PDU session resource modification response NGAP message.

48. The method according to any one of claims 35 to 38, wherein, The first network element includes a core network element; and The second network element includes at least one of the following: a base station; or the CUCP of the base station; and The third network element is the same as the first network element.

49. The method according to any one of claims 35 to 38, wherein, The first network element includes the CUCP of the base station; and The second network element includes at least one of the following: the CUUP of the base station; or the DU of the base station; and The third network element is the same as the first network element.

50. The method according to any one of claims 35 to 38, wherein, The first network element includes a source base station in the process of handover for the UE; The second network element includes a target base station in the process of handover for the UE; as well as The third network element includes the core network element.

51. A device for wireless communication, comprising: A memory for storing computer instructions and a processor for communicating with the memory, wherein, when the processor executes the computer instructions, the processor is configured to implement the method according to any one of claims 1 to 50.

52. A computer program product comprising a non-transient computer-readable program medium having computer code stored thereon, the computer code, when executed by one or more processors, causing the one or more processors to implement the method according to any one of claims 1 to 50.

Images