WO2025147946A1

WO2025147946A1 - Per pdu session and qos flow level energy information reporting

Info

Publication number: WO2025147946A1
Application number: PCT/CN2024/071762
Authority: WO
Inventors: Juan Zhang; Haris Zisimopoulos; Sebastian Speicher; Kefeng ZHANG
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-01-11
Filing date: 2024-01-11
Publication date: 2025-07-17
Anticipated expiration: 2026-07-11

Abstract

Apparatus, methods, and computer program products for wireless communication are provided. An example method may include activating energy information at a protocol data unit (PDU) session level or a quality of service (QoS) related level for a particular user equipment (UE) based on a configuration from an operations administration and maintenance (OAM) or a request from a session management function (SMF). The example method may further include providing, to a second network entity, the energy information at the PDU session level or the QoS related level for the particular UE.

Description

PER PDU SESSION AND QOS FLOW LEVEL ENERGY INFORMATION REPORTING

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to providing energy related information in a wireless communication system.

INTRODUCTION

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

BRIEF SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a first network entity (e.g., a radio access network (RAN) ) are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to activate energy information at a protocol data unit (PDU) session level or quality of service (QoS) related level for a particular user equipment (UE) based on a configuration from an operations administration and maintenance (OAM) or a request from a session management function (SMF) . Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to provide, to a second network entity, the energy information at the PDU session level or the QoS related level for the particular UE.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a first network entity (e.g., an SMF) are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to provide a request to a RAN to report energy information at the PDU session level or the QoS related level associated with a particular UE. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to obtain the energy information at the PDU session level or the QoS related level associated with the particular UE. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to provide, to a charging system, a charging data request (CDR) based on the energy information at the PDU session level or the QoS related level associated with the particular UE.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a first network entity (e.g., an access and mobility function (AMF) ) are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to obtain authorization information regarding release of energy information at the PDU session level or the QoS related level associated with a particular UE. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to provide the authorization information during an initial UE context set-up procedure.

To the accomplishment of the foregoing and related ends, the one or more aspects include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

FIG. 4 is a diagram illustrating example communications between network entities.

FIG. 5 is a diagram illustrating example communications between network entities.

FIG. 6 is a diagram illustrating example communications between network entities.

FIG. 7 is a diagram illustrating example communications between network entities.

FIG. 8 is a flowchart of a method of wireless communication.

FIG. 9 is a flowchart of a method of wireless communication.

FIG. 10 is a flowchart of a method of wireless communication.

FIG. 11 is a diagram illustrating an example of a hardware implementation for a network entity.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

An OAM may generate energy information, such as the energy Consumption, performance measurement, energy efficiency per node level (RAN node or core network (CN) node) or per slice level. However, the OAM may not provide UE level energy information to a third party. Aspects provided herein may enable a radio access network (RAN) to report protocol data unit (PDU) session level or quality of service (QoS) related level energy information associated with a particular user equipment (UE) based on a configuration from an operations administration and maintenance (OAM) or a request from a session management function (SMF) . Based on the RAN’s report, one or more AMFs may provide the energy information to one or more SMFs, which may provide the PDU level or QoS related level energy information to a charging system. The charging system may generate the UE level energy information based on the PDU level or QoS related level energy information.

Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) . Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmission reception point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) . In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .

Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) . Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework 105, or both) . A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.

Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) , configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit –User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit –Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.

The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.

Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU (s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.

The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) /machine learning (ML) (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .

At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102) . The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base station 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth^TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG) ) , Wi-Fi^TM (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs) ) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz –71 GHz) , FR4 (71 GHz –114.25 GHz) , and FR5 (114.25 GHz –300 GHz) . Each of these higher frequency bands falls within the EHF band.

With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 /UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The base station 102 may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU. The set of base stations, which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN) .

The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location/positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE) , a serving mobile location center (SMLC) , a mobile positioning center (MPC) , or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS) , global position system (GPS) , non-terrestrial network (NTN) , or other satellite position/location system) , LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS) , sensor-based information (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT) , DL angle-of-departure (DL-AoD) , DL time difference of arrival (DL-TDOA) , UL time difference of arrival (UL-TDOA) , and UL angle-of-arrival (UL-AoA) positioning) , and/or other systems/signals/sensors.

Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.

Referring again to FIG. 1, in some, the base station 102 may include an information component 199. In some aspects, the information component 199 may be configured to activate energy information at the PDU session level or the QoS related level for a particular UE based on a configuration from an OAM or a request from an SMF. In some aspects, the information component 199 may be configured to provide, to a second network entity, the energy information at the PDU session level or the QoS related level for the particular UE. In some aspects, the information component 199 may be configured to provide a request to a RAN to report energy information at the PDU session level or the QoS related level associated with a particular UE. In some aspects, the information component 199 may be configured to obtain the energy information at the PDU session level or the QoS related level associated with the particular UE. In some aspects, the information component 199 may be configured to provide, to a charging system, a CDR based on the energy information at the PDU session level or the QoS related level associated with the particular UE. In some aspects, the information component 199 may be configured to obtain authorization information regarding release of energy information at the PDU session level or the QoS related level associated with a particular UE. In some aspects, the information component 199 may be configured to provide the authorization information during an initial UE context set-up procedure.

Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein) , a UE (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU) , a central unit (CU) , a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU) ) , and/or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node) , the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to transmit information to a second network node. In this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network node.

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.

FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1) . The symbol length/duration may scale with 1/SCS.

Table 1: Numerology, SCS, and CP

For normal CP (14 symbols/slot) , different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2^μ slots/subframe. The subcarrier spacing may be equal to 2^μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended) .

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE.The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK) ) . The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with information component 199 of FIG. 1.

In some wireless communication systems, subject to operator policy, network energy related information (e.g., energy consumption related information, energy efficiency related information, renewable energy and carbon emission related information) may be provided (which may also be referred to as exposed or released) by the network to the authorized consumers, which may be charging systems operated by a third party. Aspects provided herein may provide mechanisms relating to the exposure of network energy related information, including what information, at what granularity (e.g. per network slice, UE, network function (NF) , PDU Session, QoS flow, etc) the network energy related information can be exposed, how the network energy related information may be exposed, and how and what network energy related information from the Network entities (e.g., RAN nodes, NFs) may be obtained in order to support network energy related information exposure.

As used herein, the term “energy information at the PDU session level or the QoS related level” or “PDU session level or QoS related level energy information” may refer to energy information in a per PDU session granularity level or a granularity level based on QoS, such as per QoS flow granularity level. As used herein, the term “energy information” may refer to energy efficiency (EE) key performance metrics (KPI) , energy consumption, energy-related performance measurements, or the like. Energy information for a particular UE may be provided from a RAN to one or more AMFs, which may in turn provide the energy information to one or more SMFs. The one or more AMFs or the one or more SMFs may not be aware of which particular UE that the energy information belongs to. The one or more AMFs or the one or more SMFs may transmit the energy information to a charging system, which may generate the UE-level energy information based on (e.g., by aggregating) all the energy information related to the particular UE, and may perform charging accordingly for the particular UE.

Energy efficiency KPI may include RAN data energy efficiency, network slice energy efficiency, NF energy efficiency or the like. For example, the RAN data energy efficiency may include NG-RAN data EE which may be a KPI that shows mobile network data energy efficiency in operational NG-RAN which may be a data volume (DV) divided energy consumption (EC) of the considered network elements. ) The Data Volume (in Kbits) is obtained by measuring amount of DL/UL PDCP SDU bits of the considered network elements over the measurement period. For split-gNBs, the data volume is calculated per Interface (F1-U, Xn-U, X2-U) . The Energy Consumption (in kWh) is obtained by measuring the PEE. Energy of the considered network elements over the same period of time. The samples may be aggregated at the NG-RAN node level. The NF energy efficiency may be the EC of a network function (NF) which may be obtained by summing up the energy consumption of PNF(s) and/or VNF (s) which compose the NF. The network slice EE may be performance of network slice divided by energy consumption of network slice.

The energy consumption may include per RAN node, per 5GC node, or per slice level energy consumption. The performance measurements may include performance measurements for gNB such as packet delay, PRB usage, UE throughput, per UE /per QoS flow, power, energy and environmental (PEE) measurements, or the like. The performance measurements may also include performance measurements for UPF such as data volume per QoS level, per N3 interface, data packet loss, data packet delay, or the like. The performance measurements may also include performance measurement for NFs such as virtual CPU usage, virtual memory usage, virtual disk usage, or the like.

An OAM may generate information regarding the energy consumption, performance measurement, EE per node level (RAN node, CN node) , or per slice level. However, in some wireless communication systems, OAM may not provide the UE level energy information to a third party. Aspects provided herein may enable a RAN to report energy information associated with a particular UE based on a configuration from an OAM or a request from an SMF. Based on the RAN’s report, one or more AMFs may provide the energy information to one or more SMFs, which may provide the PDU level or QoS related level energy information to a charging system. The charging system may generate the UE level energy information based on the PDU level or QoS related level energy information. In some aspects, the RAN may generate the energy related information, such as energy related parameters including energy consumption, performance measurement (s) , or EE, per different level of granularity such as per UE level, per PDU session level, or per QoS flow level. In some aspects, per PDU session level NG-RAN EE KPI may be equal to the NG-RAN data EE (equal to data volume divided energy consumption) divided by the number of PDU sessions. In some aspects, per PDU session level NG-RAN Energy Consumption may be equal to NG-RAN energy consumption divided by number of PDU session. In some aspects, per QoS flow level NG-RAN Energy Efficiency KPI may be equal to NG-RAN data energy efficiency divided by the number of QoS flow. In some aspects, per QoS flow level NG-RAN Energy Consumption may be equal to NG-RAN energy consumption divided by the number of QoS flow. In some aspects, the EE KPI may be defined for different network slices, for example, the eMBB slice, the URLLC slice, or the like, the DV and end to end latency may be both considered. In some aspects, the number of registered or activated UEs may also be considered. In some aspects, energy related information for PDU session EE or QoS flow EE for specific slice may also be generated. For example, the PDU session energy efficiency for specific slice may be equal to the EE of the slice divided by the total number of PDU session. The QoS flow energy efficiency for specific slice may be equal to the EE of the slice divided by the total number of QoS flow.

In a per PDU session/QoS flow level energy related information reporting procedure, the RAN may activate the PDU session/QoS flow level NG-RAN Energy related information by configuration of OAM, or a request from SMF. For OAM configuration, the configuration will indicate the reporting is, per PDU session or QoS flow, the configuration may also include the report time interval, periodic report, event trigger, or the like. For SMF requested procedure, the SMF may indicate the reporting is per PDU session or QoS flow, report time interval, periodic report, event trigger, or the like. The event trigger may be a trigger for the RAN to report the PDU session/QoS flow level energy related information, such as during handover procedure, connection release, deactivation of connection, or the like.

Depending on the configuration or request from the SMF, the RAN may report the PDU session/QoS flow level energy related information to SMF for the PDU session or for the selected QoS flows or both and per time interval. During handover (e.g., Xn or N2) , the source RAN node may report the PDU session/QoS flow level energy related information to the core network. At the time of connection release or deactivation of connection for a PDU session, the RAN node may report the PDU session/QoS flow level energy related information to the SMF. The RAN may also make periodic reports even if there is no trigger.

FIG. 4 is a diagram 400 illustrating example communications between network entities, including a RAN 402, an AMF 404, and an SMF 406. The communications described in connection with FIG. 4 may support a per PDU session/QoS flow level NG-RAN Energy related information reporting procedure. As illustrated in FIG. 4, the SMF 406 may send a Nsmf_RAN energy information request 408 (e.g., in a dedicated signaling or included in a session management (SM) information in other SM related signaling, such as a signaling in the PDU session establishment /modification procedure) to the AMF 404. In some aspects, the Nsmf_RAN energy information request 408 may indicate information related to the requested information, such as granularity (e.g., per PDU session, or per QoS flow or both) , QoS flow ID if per QoS flow is requested, PDU session ID, report time interval, periodic report or aperiodic report or both, event trigger (s) , or the like.

Upon receiving the Nsmf_RAN energy information request 408, the AMF 404 may send a RAN energy information request 410 to the RAN 402. The RAN energy information request 410 may also indicate information related to the requested information, such as granularity (e.g., per PDU session, or per QoS flow or both) , QoS flow ID if per QoS flow is requested, PDU session ID, report time interval, periodic report or aperiodic report or both, event trigger (s) , or the like.

Based on receiving the RAN energy information request 410, the RAN 402 may provide a RAN energy information report 412 including the energy related information to the AMF 404. In some aspects, RAN energy information report 412 may include PDU session ID, NG-RAN energy related information, start time stamp, end time stamp for each PDU session. In some aspects, RAN energy information report 412 may include QoS flow ID, NG-RAN energy related information, start time stamp, end time stamp for each QoS flow. The RAN energy information report 412 may include energy related information including per PDU session level RAN EE, per PDU session level RAN EC, per QoS flow level RAN EE KPI, per QoS flow level RAN EC, or the like. The RAN energy information report 412 may be transmitted via dedicated signaling or other signaling. In some aspects, during connection release procedure, the RAN energy information report 412 is included in N2 UE context release complete message. In some aspects, during PDU session modify procedure, the RAN energy information report 412 is included in PDU session resource modify response. In some aspects, during PDU session deactivation procedure, the RAN energy information report 412 is included in PDU session resource release response. In some aspects, during handover, the RAN energy information report 412 is included in the HO related message sent from source RAN to AMF and then to SMF.

In some aspects, for each PDU session or QoS flow, the AMF 404 may forward the report to the corresponding SMF 406. The AMF 404 may send the RAN energy information report 414 via dedicated message, or included in other SM related message, e.g., PDU session establishment or modification response message. The SMF 406 may receive the PDU session level or QoS level RAN energy related information in the RAN energy information report 414 and may generate corresponding CDR and send it to a charging system. The charging system may then generate the energy related information for a particular UE by summing all the PDU session /QoS flow NG-RAN energy information for the same UE.

FIG. 5 is a diagram 500 illustrating example communications between network entities, including a RAN 502, an AMF 504, and an SMF 506. The communications described in connection with FIG. 4 may support a per PDU session/QoS flow level NG-RAN Energy related information reporting procedure. Trigger by an OAM configuration at 510, the RAN 502 may provide a RAN energy information report 512 including the energy related information to the AMF 504. In some aspects, RAN energy information report 512 may include PDU session ID, NG-RAN energy related information, start time stamp, end time stamp for each PDU session. In some aspects, RAN energy information report 512 may include QoS flow ID, NG-RAN energy related information, start time stamp, end time stamp for each QoS flow. The RAN energy information report 512 may include energy related information including per PDU session level RAN EE, per PDU session level RAN EC, per QoS flow level RAN EE KPI, per QoS flow level RAN EC, or the like. The RAN energy information report 512 may be transmitted via dedicated signaling or other signaling. In some aspects, during connection release procedure, the RAN energy information report 512 is included in N2 UE context release complete message. In some aspects, during PDU session modify procedure, the RAN energy information report 512 is included in PDU session resource modify response. In some aspects, during PDU session deactivation procedure, the RAN energy information report 512 is included in PDU session resource release response. In some aspects, during handover, the RAN energy information report 512 is included in the HO related message sent from source RAN to AMF and then to SMF.

In some aspects, for each PDU session or QoS flow, the AMF 504 may forward the report to the corresponding SMF 506. The AMF 504 may send the RAN energy information report 514 via dedicated message, or included in other SM related message, e.g., PDU session establishment or modification response message. The SMF 506 may receive the PDU session level or QoS level RAN energy related information in the RAN energy information report 514 and may generate corresponding CDR and send it to a charging system. The charging system may then generate the energy related information for a particular UE by summing all the PDU session /QoS flow NG-RAN energy information for the same UE.

FIG. 6 is a diagram 600 illustrating example communications between network entities, including a RAN 602, an AMF 604, and a UDM 605. The UDM 605 may store the UE subscription regarding whether it may be allowed expose/release per UE/PDU session/QoS flow level RAN energy related information. In some aspects, for each UE, UDM stores whether allowed to expose the energy related information. During a registration procedure, the AMF 604 may transmit a request for subscription information (e.g., in Nudm_SDM_get 610) to the UDM 605 to obtain a response (e.g., in Nudm_SDM_notification 612) that includes the UE subscription from the UDM 605. The AMF 604 may inform the RAN 602 regarding whether the energy related information may be allowed to be released during an initial context setup procedure, which includes an initial context setup request 614 to the RAN 602 and an initial context setup response 616 to the AMF 604. The RAN 602 may check if the UE is allowed to expose energy related information and if PDU session or QoS flow level energy related information exposure is activated for the specific UE. Information regarding whether exposure/release is allowed or not may be referred to as “authorization information. ”

FIG. 7 is a diagram 700 illustrating example communications between network entities, including an SMF 706 and a UDM 708. For each UE and each PDU session, the UDM 708 may store whether it’s allowed to expose the energy efficiency related information. During PDU session establishment procedure, the UDM 708 may provide the energy efficiency authorization information as PDU session subscription to SMF 706 (e.g., in a Nudm_SDM_notification 714 in response to a Nudm_SDM_get 712) . At 716, the SMF 706 may check if the exposure is allowed. If the exposure is allowed, the SMF 706 may transmit a request (e.g., 408) .

FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a network entity, such as a RAN (e.g., the base station 102, the RAN 402, the RAN 502, the RAN 602, the network entity 1160) . The method may enable a RAN to report energy information associated with a particular UE based on a configuration from an OAM or a request from a SMF. Based on the RAN’s report, one or more AMFs may provide the energy information to one or more SMFs, which may provide the PDU level or QoS related level energy information to a charging system. The charging system may generate the UE level energy information based on the PDU level or QoS related level energy information.

At 802, the first network entity may activate energy information for a particular UE based on a configuration from an OAM or a request from an SMF. For example, the RAN 402, the RAN 502, or the RAN 602 may activate energy information for a particular UE based on a configuration from an OAM (e.g., 510) or a request from an SMF (e.g., 408) . In some aspects, 802 may be performed by information component 199.

In some aspects, to activate the energy information, the first network entity may obtain the configuration from the OAM, where the configuration configures the energy information to include per PDU session information or per QoS flow information. In some aspects, the configuration includes a report time interval associated with the energy information for the particular UE, a periodic report associated with the energy information for the particular UE, or an event trigger for providing the energy information for the particular UE. In some aspects, the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.

At 804, the first network entity may provide, to a second network entity, the energy information for the particular UE. For example, the RAN 402, the RAN 502, or the RAN 602 may provide, to a second network entity (e.g., 404) , the energy information for the particular UE. In some aspects, 804 may be performed by information component 199.

In some aspects, to provide the energy information for the particular UE, the first network entity may provide the energy information in the periodic report based on the report time interval. In some aspects, to provide the energy information for the particular UE, the first network entity may provide the energy information in an aperiodic report based on the event trigger, and where one of: the event trigger is a connection release procedure, the aperiodic report is included in a context release complete message, the event trigger is a handover procedure, the aperiodic report is included in a handover related message, the event trigger is a deactivation of a PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource release response, or the event trigger is a modification of the PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource modify response.

In some aspects, to activate the energy information, the first network entity may obtain the request from the SMF, where the request indicates for the energy information to include per PDU session information or per QoS flow information. In some aspects, the request indicates a report time interval associated with the energy information for the particular UE, a periodic report associated with the energy information for the particular UE, or an event trigger for providing the energy information for the particular UE. In some aspects, the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.

In some aspects, the energy information is associated with multiple PDU sessions or multiple QoS flows for the particular UE. In some aspects, the energy information includes at least one of: a per PDU session energy efficiency, a per PDU session energy consumption, a set of per PDU session key performance metrics, a per QoS flow energy efficiency, a per QoS flow energy consumption, a set of per QoS flow key performance metrics. In some aspects, the first network entity may provide at least one start time stamp, at least one end time stamp, and at least one identifier associated with the energy information. In some aspects, the first network entity may obtain, from the second network entity during a registration procedure (e.g., as described in connection with FIG. 6) , authorization information regarding release of the energy information and check the authorization information before providing the energy information.

FIG. 9 is a flowchart 900 of a method of wireless communication. The method may be performed by a first network entity, such as an SMF (e.g., the base station 102, the SMF 406, the SMF 706, the SMF 706, the network entity 1160) . The method may enable a RAN to report energy information associated with a particular UE based on a configuration from an OAM or a request from a SMF. Based on the RAN’s report, one or more AMFs may provide the energy information to one or more SMFs, which may provide the PDU level or QoS related level energy information to a charging system. The charging system may generate the UE level energy information based on the PDU level or QoS related level energy information.

At 902, the first network entity may provide a request to a RAN to report energy information associated with a particular UE. For example, the SMF 406, the SMF 706, or the SMF 706 may provide a request (e.g., 408) to a RAN to report energy information associated with a particular UE. In some aspects, 902 may be performed by information component 199. In some aspects, the first network entity may provide the request in a dedicated signaling or a session management (SM) related signaling. In some aspects, the request indicates a report time interval associated with the energy information for the particular UE, a periodic report associated with the energy information for the particular UE, or an event trigger for providing the energy information for the particular UE. In some aspects, the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.

At 904, the first network entity may obtain the energy information associated with the particular UE. For example, the SMF 406, the SMF 706, or the SMF 706 may obtain the energy information (e.g., 414 or 514) associated with the particular UE. In some aspects, 904 may be performed by information component 199.

At 906, the first network entity may provide, to a charging system, a CDR based on the energy information associated with the particular UE. For example, the SMF 406, the SMF 706, or the SMF 706 may provide, to a charging system, a CDR based on the energy information associated with the particular UE. In some aspects, 906 may be performed by information component 199.

In some aspects, the first network entity may check authorization information regarding release of the energy information associated with the particular UE (e.g., 716) and provide the request based on the authorization information regarding release of the energy information associated with the particular UE.

FIG. 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a first network entity, such as an AMF (e.g., the base station 102, the AMF 404, the AMF 504, the AMF 604, the network entity 1160) . The method may enable a RAN to report energy information associated with a particular UE based on a configuration from an OAM or a request from an SMF. Based on the RAN’s report, one or more AMFs may provide the energy information to one or more SMFs, which may provide the PDU level or QoS related level energy information to a charging system. The charging system may generate the UE level energy information based on the PDU level or QoS related level energy information.

At 1002, the first network entity may obtain authorization information regarding release of energy information associated with a particular UE. For example, the AMF 404, the AMF 504, or the AMF 604 may obtain authorization information (e.g., 610) regarding release of energy information associated with a particular UE. In some aspects, 1002 may be performed by information component 199.

At 1004, the first network entity may provide the authorization information during an initial UE context set-up procedure. For example, the SMF 406, the SMF 706, or the SMF 706 may provide the authorization information during an initial UE context set-up procedure (e.g., 614) . In some aspects, 1004 may be performed by information component 199.

FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for a network entity 1160. In some aspects, the network entity 1160 may include or carry the functions of a RAN, an SMF, or an AMF. In one example, the network entity 1160 may be within the core network 120. The network entity 1160 may include at least one network processor 1112. The network processor (s) 1112 may include on-chip memory 1112'. In some aspects, the network entity 1160 may further include additional memory modules 1114. The network entity 1160 communicates via the network interface 1180 directly (e.g., backhaul link) or indirectly (e.g., through a RIC) with the CU 1102. The on-chip memory 1112' and the additional memory modules 1114 may each be considered a computer-readable medium /memory. Each computer-readable medium /memory may be non-transitory. The network processor (s) 1112 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the corresponding processor (s) causes the processor (s) to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the processor (s) when executing software.

As discussed supra, the information component 199 may be configured to activate energy information for a particular UE based on a configuration from an OAM or a request from an SMF. In some aspects, the information component 199 may be configured to provide, to a second network entity, the energy information for the particular UE. In some aspects, the information component 199 may be configured to provide a request to a RAN to report energy information associated with a particular UE.In some aspects, the information component 199 may be configured to obtain the energy information associated with the particular UE. In some aspects, the information component 199 may be configured to provide, to a charging system, a CDR based on the energy information associated with the particular UE. In some aspects, the information component 199 may be configured to obtain authorization information regarding release of energy information associated with a particular UE. In some aspects, the information component 199 may be configured to provide the authorization information during an initial UE context set-up procedure. The component 199 may be within the network processor (s) 1112. The component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. The network entity 1160 may include a variety of components configured for various functions. In some aspects, the network entity 1160 may include means for activating energy information for a particular UE based on a configuration from an OAM or a request from an SMF. In some aspects, the network entity 1160 may include means for providing, to a second network entity, the energy information for the particular UE. In some aspects, the network entity 1160 may include means for obtaining the configuration from the OAM, where the configuration configures the energy information to include per PDU session information or per QoS flow information. In some aspects, the network entity 1160 may include means for providing the energy information in the periodic report based on the report time interval. In some aspects, the network entity 1160 may include means for providing the energy information in an aperiodic report based on the event trigger. In some aspects, the network entity 1160 may include means for obtaining the request from the SMF, where the request indicates for the energy information to include per PDU session information or per QoS flow information. In some aspects, the network entity 1160 may include means for providing the energy information in the periodic report based on the report time interval. In some aspects, the network entity 1160 may include means for providing the energy information in an aperiodic report based on the event trigger. In some aspects, the network entity 1160 may include means for providing at least one start time stamp, at least one end time stamp, and at least one identifier associated with the energy information. In some aspects, the network entity 1160 may include means for obtaining, from the second network entity during a registration procedure, authorization information regarding release of the energy information. In some aspects, the network entity 1160 may include means for checking the authorization information before providing the energy information. In some aspects, the network entity 1160 may include means for providing a request to a RAN to report energy information associated with a particular UE. In some aspects, the network entity 1160 may include means for obtaining the energy information associated with the particular UE. In some aspects, the network entity 1160 may include means for providing, to a charging system, a CDR based on the energy information associated with the particular UE. In some aspects, the network entity 1160 may include means for providing the request in a dedicated signaling or a session management (SM) related signaling. In some aspects, the network entity 1160 may include means for checking authorization information regarding release of the energy information associated with the particular UE. In some aspects, the network entity 1160 may include means for providing the request based on the authorization information regarding release of the energy information associated with the particular UE. In some aspects, the network entity 1160 may include means for obtaining authorization information regarding release of energy information associated with a particular UE. In some aspects, the network entity 1160 may include means for providing the authorization information during an initial UE context set-up procedure. The means may be the component 199 of the network entity 1160 configured to perform the functions recited by the means.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and/or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

Aspect 1 is a method for wireless communication performed by a first network entity, including: activating energy information at a protocol data unit (PDU) session level or quality of service (QoS) related level for a particular user equipment (UE) based on a configuration from an operations administration and maintenance (OAM) or a request from a session management function (SMF) ; and providing, to a second network entity, the energy information at the PDU session level or the QoS related level for the particular UE.

Aspect 2 is the method of aspect 1, where activating the energy information at the PDU session level or the QoS related level further includes: obtaining the configuration from the OAM, where the configuration configures the energy information at the PDU session level or the QoS related level to include per PDU session information or per QoS flow information.

Aspect 3 is the method of any of aspects 1-2, where the configuration includes a report time interval associated with the energy information at the PDU session level or the QoS related level for the particular UE, a periodic report associated with the energy information at the PDU session level or the QoS related level for the particular UE, or an event trigger for providing the energy information at the PDU session level or the QoS related level for the particular UE.

Aspect 4 is the method of any of aspects 1-3, where the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.

Aspect 5 is the method of any of aspects 1-3, where providing the energy information at the PDU session level or the QoS related level for the particular UE further includes: providing the energy information at the PDU session level or the QoS related level in the periodic report based on the report time interval.

Aspect 6 is the method of any of aspects 3-5, where providing the energy information at the PDU session level or the QoS related level for the particular UE further includes: providing the energy information at the PDU session level or the QoS related level in an aperiodic report based on the event trigger, and where one of: the event trigger is a connection release procedure, the aperiodic report is included in a context release complete message, the event trigger is a handover procedure, the aperiodic report is included in a handover related message, the event trigger is a deactivation of a PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource release response, or the event trigger is a modification of the PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource modify response.

Aspect 7 is the method of any of aspects 1, where activating the energy information at the PDU session level or the QoS related level further includes: obtaining the request from the SMF, where the request indicates for the energy information to include per PDU session information or per QoS flow information.

Aspect 8 is the method of aspect 7, where the request indicates a report time interval associated with the energy information at the PDU session level or the QoS related level for the particular UE, a periodic report associated with the energy information at the PDU session level or the QoS related level for the particular UE, or an event trigger for providing the energy information at the PDU session level or the QoS related level for the particular UE.

Aspect 9 is the method of aspect 8, where the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.

Aspect 10 is the method of any of aspects 8-9, where providing the energy information at the PDU session level or the QoS related level for the particular UE further includes: providing the energy information at the PDU session level or the QoS related level in the periodic report based on the report time interval.

Aspect 11 is the method of any of aspects 8-10, where providing the energy information at the PDU session level or the QoS related level for the particular UE further includes: providing the energy information at the PDU session level or the QoS related level in an aperiodic report based on the event trigger, and where one of: the event trigger is a connection release procedure, the aperiodic report is included in a context release complete message, the event trigger is a handover procedure, the aperiodic report is included in a handover related message, the event trigger is a deactivation of a PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource release response, or the event trigger is a modification of the PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource modify response.

Aspect 12 is the method of any of aspects 1-11, where the energy information is associated with multiple PDU sessions or multiple QoS flows for the particular UE.

Aspect 13 is the method of any of aspects 1-12, where the energy information includes at least one of: a per PDU session energy efficiency, a per PDU session energy consumption, a set of per PDU session key performance metrics, a per QoS flow energy efficiency, a per QoS flow energy consumption, a set of per QoS flow key performance metrics.

Aspect 14 is the method of any of aspects 1-13, further including: providing at least one start time stamp, at least one end time stamp, and at least one identifier associated with the energy information at the PDU session level or the QoS related level.

Aspect 15 is the method of any of aspects 1-14, further including: obtaining, from the second network entity during a registration procedure, authorization information regarding exposure of the energy information at the PDU session level or the QoS related level ; and checking the authorization information before providing the energy information at the PDU session level or the QoS related level.

Aspect 16 is a method for wireless communication performed by a first network entity, including: providing a request to a radio access network (RAN) to report energy information at a protocol data unit (PDU) session level or a quality of service (QoS) related level associated with a particular user equipment (UE) ; obtaining the energy information at the PDU session level or the QoS related level associated with the particular UE; and providing, to a charging system, a charging data request (CDR) based on the energy information at the PDU session level or the QoS related level associated with the particular UE.

Aspect 17 is the method of aspect 16, where providing the request further includes: providing the request in a dedicated signaling or a session management (SM) related signaling.

Aspect 18 is the method of any of aspects 16-17, where the request indicates a report time interval associated with the energy information at the PDU session level or the QoS related level for the particular UE, a periodic report associated with the energy information at the PDU session level or the QoS related level for the particular UE, or an event trigger for providing the energy information at the PDU session level or the QoS related level for the particular UE.

Aspect 19 is the method of aspect 18, where the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.

Aspect 20 is the method of any of aspects 16-19, further including: checking authorization information regarding exposure of the energy information at the PDU session level or the QoS related level associated with the particular UE; and providing the request based on the authorization information regarding the exposure of the energy information at the PDU session level or the QoS related level associated with the particular UE.

Aspect 21 is a method for wireless communication performed by a first network entity, including: obtaining authorization information regarding release of protocol data unit (PDU) session level or quality of service (QoS) related level energy information associated with a particular user equipment (UE) ; and providing the authorization information during an initial UE context set-up procedure.

Aspect 22 is an apparatus for wireless communication at a wireless device including at least one memory and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in combination, to implement any of aspects 1 to 21.

Aspect 23 is the apparatus of aspect 22, further including one or more transceivers or one or more antennas coupled to the at least one processor.

Aspect 24 is an apparatus for wireless communication at a wireless device including means for implementing any of aspects 1 to 21.

Aspect 25 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by at least one processor causes the at least one processor to implement any of aspects 1 to 21.

Claims

An apparatus for wireless communication at a first network entity, comprising:

at least one memory; and

at least one processor coupled to the at least one memory, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

activate energy information at a protocol data unit (PDU) session level or quality of service (QoS) related level for a particular user equipment (UE) based on a configuration from an operations administration and maintenance (OAM) or a request from a session management function (SMF) ; and

provide, to a second network entity, the energy information at the PDU session level or the QoS related level for the particular UE.
The apparatus of claim 1, wherein to activate the energy information at the PDU session level or the QoS related level , the at least one processor, individually or in any combination, is configured to cause the first network entity to:

obtain the configuration from the OAM, wherein the configuration configures the energy information at the PDU session level or the QoS related level to include per PDU session information or per QoS flow information.
The apparatus of claim 2, wherein the configuration comprises a report time interval associated with the energy information at the PDU session level or the QoS related level for the particular UE, a periodic report associated with the energy information at the PDU session level or the QoS related level for the particular UE, or an event trigger for providing the energy information at the PDU session level or the QoS related level for the particular UE.
The apparatus of claim 3, wherein the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.
The apparatus of claim 3, wherein to provide the energy information at the PDU session level or the QoS related level for the particular UE, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

provide the energy information at the PDU session level or the QoS related level in the periodic report based on the report time interval.
The apparatus of claim 3, wherein to provide the energy information at the PDU session level or the QoS related level for the particular UE, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

provide the energy information at the PDU session level or the QoS related level in an aperiodic report based on the event trigger, and wherein one of:

the event trigger is a connection release procedure, the aperiodic report is included in a context release complete message,

the event trigger is a handover procedure, the aperiodic report is included in a handover related message,

the event trigger is a deactivation of a PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource release response, or

the event trigger is a modification of the PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource modify response.
The apparatus of claim 1, wherein to activate the energy information at the PDU session level or the QoS related level , the at least one processor, individually or in any combination, is configured to cause the first network entity to:

obtain the request from the SMF, wherein the request indicates for the energy information to include per PDU session information or per QoS flow information.
The apparatus of claim 7, wherein the request indicates a report time interval associated with the energy information at the PDU session level or the QoS related level for the particular UE, a periodic report associated with the energy information at the PDU session level or the QoS related level for the particular UE, or an event trigger for providing the energy information at the PDU session level or the QoS related level for the particular UE.
The apparatus of claim 8, wherein the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.
The apparatus of claim 8, wherein to provide the energy information at the PDU session level or the QoS related level for the particular UE, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

provide the energy information at the PDU session level or the QoS related level in the periodic report based on the report time interval.
The apparatus of claim 8, wherein to provide the energy information at the PDU session level or the QoS related level for the particular UE, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

provide the energy information at the PDU session level or the QoS related level in an aperiodic report based on the event trigger, and wherein one of:

the event trigger is a connection release procedure, the aperiodic report is included in a context release complete message,

the event trigger is a handover procedure, the aperiodic report is included in a handover related message,

the event trigger is a deactivation of a PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource release response, or

the event trigger is a modification of the PDU session associated with the particular UE, the aperiodic report is included in a PDU session resource modify response.
The apparatus of claim 1, wherein the energy information is associated with multiple PDU sessions or multiple QoS flows for the particular UE.
The apparatus of claim 1, wherein the energy information comprises at least one of: a per PDU session energy efficiency, a per PDU session energy consumption, a set of per PDU session key performance metrics, a per QoS flow energy efficiency, a per QoS flow energy consumption, a set of per QoS flow key performance metrics.
The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to cause the first network entity to:

provide at least one start time stamp, at least one end time stamp, and at least one identifier associated with the energy information at the PDU session level or the QoS related level .
The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to cause the first network entity to:

obtain, from the second network entity during a registration procedure, authorization information regarding exposure of the energy information at the PDU session level or the QoS related level ; and

check the authorization information before providing the energy information at the PDU session level or the QoS related level .
An apparatus for wireless communication at a first network entity, comprising:

at least one memory; and

at least one processor coupled to the at least one memory, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

provide a request to a radio access network (RAN) to report energy information at a protocol data unit (PDU) session level or a quality of service (QoS) related level associated with a particular user equipment (UE) ;

obtain the energy information at the PDU session level or the QoS related level associated with the particular UE; and

provide, to a charging system, a charging data request (CDR) based on the energy information at the PDU session level or the QoS related level associated with the particular UE.
The apparatus of claim 16, wherein to provide the request, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

provide the request in a dedicated signaling or a session management (SM) related signaling.
The apparatus of claim 16, wherein the request indicates a report time interval associated with the energy information at the PDU session level or the QoS related level for the particular UE, a periodic report associated with the energy information at the PDU session level or the QoS related level for the particular UE, or an event trigger for providing the energy information at the PDU session level or the QoS related level for the particular UE, and wherein the event trigger includes at least one of: a handover procedure, a connection release, a deactivation of a PDU session associated with the particular UE, or a modification of the PDU session associated with the particular UE.
The apparatus of claim 16, wherein the at least one processor, individually or in any combination, is further configured to cause the first network entity to:

check authorization information regarding exposure of the energy information at the PDU session level or the QoS related level associated with the particular UE; and

provide the request based on the authorization information regarding the exposure of the energy information at the PDU session level or the QoS related level associated with the particular UE.
An apparatus for wireless communication at a first network entity, comprising:

at least one memory; and

at least one processor coupled to the at least one memory, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to cause the first network entity to:

obtain authorization information regarding release of protocol data unit (PDU) session level or quality of service (QoS) related level energy information associated with a particular user equipment (UE) ; and

provide the authorization information during an initial UE context set-up procedure.