Title - METHOD FOR A USER DEVICE CONFIGURED TO OPERATE IN A CELL OF THE WIRELESS NETWORK, METHOD FOR A NETWORK NODE CONFIGURED TO SERVE A CELL IN A WIRELESS NETWORK AND SAID USER DEVICE AND NETWORK NODE

Abstract

The embodiments include methods for a user equipment (UE) configured to operate in a cell of a wireless network. These methods include receiving, from a network node of the wireless network, one or more configurations for the operation of the user equipment in the cell and determining one or more of the following information associated with at least the received configurations and with the user equipment's data traffic: energy efficiency (EE) of the UE, and quality of service (QoS). These methods also include sending the determined information, or one or more indications thereof, to the network node. In some embodiments, these methods also include receiving, from the network node, an additional configuration for the operation of the UE in the cell. Other embodiments include supplementary methods for a network node, as well as UEs and network nodes configured to implement these methods.

Description

User Equipment (UE) Feedback to Improve Energy Efficiency Configuration TECHNICAL FIELD This disclosure relates generally to wireless communication networks, and more specifically to techniques for reducing the power consumption of user equipment (UE) based on UE feedback related to UE operating configurations provided by a network. BACKGROUND Currently, the fifth generation (“5G”) of cellular systems, also known as New Radio (NR), is being standardized within the Third Generation Partnership Project (3GPP). NR has been developed to offer maximum flexibility and support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine-type communications (MTC), ultra-reliable low-latency communications (URLLC), device-to-device sidelink (D2D), and other use cases. Figure 1 illustrates a high-level example view of the 5G network architecture, consisting of a next-generation RAN (NG-RAN) and a 5G core (5GC). The NG-RAN may include a set of gNodeBs (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100 and 150 connected via interfaces 102 and 152, respectively. Furthermore, the gNBs may be interconnected via one or more Xn interfaces, such as Xn interface 140 between gNBs 100 and 150. At the NR interface for user equipment (UEs, e.g., wireless devices), each gNB may support frequency-division duplexing (FDD), time-division duplexing (TDD), or a combination of these. NG-RAN 199 is divided into a radio network layer (RNL) and a transport network layer (TNL). The NG-RAN architecture, that is, the logical NG-RAN nodes and the interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the corresponding TNL protocol and its functionality are specified. The TNL provides services for user plane transport and signaling transport. In some example configurations, each gNB is connected to all 5GC nodes within an “AMF Region,” the term “AMF” being described in more detail below. The NG-RAN nodes shown in Figure 1 include a central unit (or 1779950 of 88 centralized) (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130. CUs (e.g., gNB-CU 110) are logical nodes that host upper-layer protocols and perform various gNB functions, such as controlling the operation of the DUs. Each DU is a logical node that hosts lower-layer protocols and may include, depending on the functional division, several subsets of gNB functions. As such, each CU and DU may include several circuits necessary to perform its respective functions, including processing circuits, transceiver circuits (e.g., for communication), and power circuits. Furthermore, the terms “central unit” and “centralized unit” are used interchangeably in this document, as are the terms “distributed unit” and “decentralized unit”. A gNB-CU connects to the gNB-DUs via their respective F1 logical interfaces, such as interfaces 122 and 132 shown in Figure 1. The connected gNB-CU and gNB-DUs are only visible to other gNBs and the 5GC as gNBs. In other words, the F1 interface is not visible beyond the gNB-CU. Energy consumption is a critical operating characteristic for UEs, to the point that it affects, and in some cases dictates, the configuration of both UEs and the network for UEs operating in specific network and traffic scenarios. For example, the network is expected to configure user equipment to prevent excessive energy consumption, extend battery life, and avoid overheating. As a general principle, the energy consumption of user equipment can be reduced by 1) increasing the amount of operating time the user equipment spends in standby and / or low-power states, especially deep sleep, where a large portion of the user equipment's radio frequency (RF) circuitry is switched off, and / or 2) operating the receiver with the minimum necessary configuration when monitoring signals transmitted over the network (e.g., minimum number of receiving antennas, reduced receive bandwidth, minimum required reception quality, etc.). The network can facilitate the reduction of user equipment energy consumption by adjusting various parameters in the user equipment configurations assigned to the respective UE (Enterprise Units). As another general principle, UE configurations that provide favorable UE power consumption may impose undesirable effects on network performance and / or other aspects of UE performance. For example, data latency may increase, and UE and cell throughput may be reduced. 1779950 of 88 can be reduced, and / or network signaling overload may increase. SYNTHESIS To understand these trade-offs, the grid needs to grasp the true energy efficiency (EE) benefits of user equipment that accompany the undesirable effects of a given equipment configuration. Energy consumption models of currently used equipment can provide the grid with a qualitative understanding of the EE benefits of equipment in a particular configuration. However, these models do not accurately reflect the actual energy consumption of equipment, which can vary significantly depending on the devices, manufacturers, chipsets, software, and other factors. Therefore, better solutions are needed. The methods of implementation described in this disclosure provide specific improvements in communication between user equipment and network nodes in a wireless network, for example, by providing, enabling, and / or facilitating solutions to overcome the example problems summarized above and described in more detail below. The embodiments include methods (e.g., procedures) for a UE (e.g., wireless device, etc.) operating in a cell of a wireless network (e.g., E-UTRAN, NG-RAN). These example methods may include receiving, from a network node, one or more configurations for the operation of the UE in the cell. These example methods may also include determining one or more of the following information associated with at least the received configurations and the UE data traffic: UE energy efficiency (EE) and quality of service (QoS). These example methods may also include sending the determined information, or one or more indications thereof, to the network node. In some embodiments, these example methods may also include receiving, from the network node, another configuration for the operation of the UE in the cell. In some implementations, each configuration includes settings or values ​​for one or more of the following: • Intermittent reception (DRX) while the UE is operating in a state connected to the wireless network; • DRX while the UE is operating in a state not connected to the wireless network; • Activation signals (WUS) while the user equipment is operating 1779950 of 88 in a state not connected to the wireless network; • measurement or monitoring of the beams and / or reference signals transmitted by the network node; • carrier aggregation (CA); • dual connectivity (DC); • bandwidth parts (BWP); • reception and / or transmission of multiple inputs and outputs (MIMO); • monitoring of the physical downlink control channel (PDCCH); and • quality of service (QoS). In some embodiments, determining the EE information of the user equipment associated with each of the received configurations may include the determination by the user equipment of one of the following aspects for one of the configurations that the user equipment uses to operate in the cell: • an actual energy consumption of the user equipment based on measurements of the operating current during an observation period; or • an estimated energy consumption of the user equipment based on the duration of each of the operating states during the observation period and on a model of the energy consumption of the user equipment in each of the operating states. In some embodiments, the determination of the user equipment's EE information associated with each of the received configurations may include the user equipment determining an estimated energy consumption for a configuration that is not being used by the user equipment, based on one or more of the following aspects: • a database that stores information about the energy consumption of at least one of the manufacturers, a model number and a chipset associated with the user equipment; • the actual energy consumption of the UE during the above operation in the configuration or in a configuration similar to the configuration; and • the estimated duration of use of the user equipment in each of the operating states and a model of the energy consumption of the user equipment in each of the operating states. In some of these forms of realization, the determination of the information 1779950 of 88 EE of the user equipment associated with each of the received configurations may also include adjusting the actual or estimated power consumption of the user equipment by eliminating power consumption that is independent of one or more configurations. In some implementations, each configuration may include a QoS identifier associated with one or more QoS features. In this case, the user equipment determines and sends EE information from the user equipment only for configurations that have a QoS identifier and / or QoS features that correspond to a data radio carrier (DRB) established for the user equipment and / or the data traffic of one or more user equipment applications. In some embodiments, the specified information or one or more indications thereof sent to the network node may include one or more of the following: • the respective absolute EE ratings for the received configurations; • an absolute EE classification for a received configuration that is being used by the UE; • the respective EE ratings of the received configurations in relation to a reference EE rating; • the respective EE differences between the received configurations and a configuration that is being used by the UE; • an EE difference between two of the received configurations; • the absolute, actual or estimated energy consumption of the user equipment for the received configurations; and • the actual or estimated energy consumption of the user equipment for the received configurations, relative to the user equipment reference energy consumption. In some of these embodiments, each received configuration may include a corresponding reference EE rating, which may include an estimated range of absolute EE ratings for the corresponding configuration. In these embodiments, the indications sent to the network node comprise indications of whether the actual EE ratings of the received configurations are within the respective estimated ranges of absolute EE ratings. In other embodiments, the EU reference energy consumption may be one of the following: • the actual energy consumption of the user equipment when operating in a 1779950 of 88 state of no connection with the wireless network; or • the actual or estimated power consumption of the equipment when operating in a reference configuration. In some embodiments, the specified information or one or more indications thereof sent to the network node may also include one or more of the following: • the respective absolute QoS ratings for the received configurations; • an absolute QoS rating for a received configuration that is being used by the UE; • the respective QoS differences between the received configurations and a configuration that is being used by the UE; and • a QoS difference between two of the received configurations. In some of these implementations, the absolute EE rating and the absolute QoS rating associated with the same received configuration are represented by a combined EE / QoS rating. In some embodiments, the determination of information (e.g., UE EE and / or QoS) is based on UE data traffic during a single observation period or during each of a plurality of non-overlapping measurement periods comprising the single observation period. In some embodiments, the specified information or one or more indications thereof sent to the network node may include an indication of a UE-preferred configuration not included in the received configurations and one or more of the following: • UE EE and / or QoS information associated with the UE's preferred configuration; and • an indication of one or more criteria for selecting the UE's preferred configuration. In some embodiments, the specified information or one or more indications thereof are sent to the network node in response to one or more of the following: • receiving the configurations; • a change in EU data traffic; • activation or deactivation of applications by the UE; • UE change between a connected state and a non-connected state 1779950 of 88 the wireless network; • EU mobility operation; • change in one or more of the following elements used by the user equipment: network portion, QoS flow, data radio carrier (DRB), signaling radio carrier (SRB), and quality of experience (QoE) measurement configuration; • the actual or estimated energy consumption of the UE for a configuration used by the UE is greater than a first threshold; • the quality of service of a configuration used by the user equipment is below a second threshold; and • a periodic or semi-static schedule configured by the network. In some embodiments, the example method may also include sending, to the network node, an indication of the UE's feedback capabilities for network-provided configurations and / or dynamic information associated with the current UE conditions. Other implementations include example methods (e.g., procedures) for a network node (e.g., base station, eNB, gNB, ng-eNB, etc.) serving a cell in a wireless network (e.g., E-UTRAN, NG-RAN). In general, these example methods can complement the example methods for a UE summarized above. These example methods may include sending one or more configurations for the UE's operation in the cell to a UE. These example methods may also include receiving one or more of the following information from the UE, associated with at least the UE's configurations and data traffic: the UE's energy efficiency (EE) and quality of service (QoS). These example methods may also include determining an additional configuration for the UE's operation in the cell based on the received information and one or more of the following additional information: cell configuration; statistics associated with cell operation; current traffic conditions in the cell; and the capabilities, status, and / or configuration of at least the UE. In various embodiments, one or more configurations may include any of the same information, have any of the same characteristics, and / or be sent by any of the same mechanisms as those summarized above for the embodiments related to the EU. In some implementations, the cell configuration may include one 1779950 of 88 or more of the following parameters: cell size, carrier frequency, bandwidth, multi-user input and output capabilities (MU-MIMO). In some embodiments, the statistics associated with cell performance may be based on one or more of the following parameters: block error rate (BLER), modulation and coding scheme (MCS), power control outer loop settings, data throughput, signal-to-interference-to-noise ratio (SINR), and traffic load. In some embodiments, the current traffic conditions in the cell are represented by one or more of the following parameters: traffic load over the most recent duration, number of UEs in a state connected to the wireless network over the most recent duration, signal quality as measured by the UEs over the most recent duration, number of mobility operations by the UEs over the most recent duration, and number and / or type of radio carriers currently set up for the UEs. In some embodiments, the capabilities, status and / or configuration of at least the UE include any of the following: UE antenna configuration, UE power source, UE manufacturer and / or model, UE chipset manufacturer and / or model, UE software version, UE class, UE performance category, and UE compatibility with one or more transmission modes used in the cell. In various embodiments, the information received (i.e., from the EU) may include any of the same information, have any of the same characteristics, and / or be received by the same mechanism, as the information determined and sent by the EU, as summarized above for embodiments related to the EU. Similarly, in various embodiments, the additional configuration determined and sent by the network node may include any of the same information and / or have any of the same characteristics as the additional configuration received by the UE, such as those summarized above for the UE-related embodiments. In some embodiments, this example method may also include sending one or more configurations to one or more additional UEs; and receiving, from the additional UEs, one or more of the following additional information associated with at least the configurations and data traffic of the additional UEs: respective EE of the additional UEs, and respective QoS of the additional UEs. 1779950 of 88 In these embodiments, determining the additional configuration for UE operation in the cell may include the network node applying a reinforcement learning (RL) algorithm to the received information, additional received information, and additional information. In some of these embodiments, the additional configuration may apply to all UEs operating in the cell, all UEs served by a particular network segment, or all UEs associated with a particular QoS profile. In some forms of implementation, the receipt of information from the EU responds to one or more of the following: • sending the configurations to the UE; • a change in EU data traffic; • activation or deactivation of applications by the UE; • UE switching between a connected state and a state not connected to the wireless network; • EU mobility operation; • change in one or more of the following elements used by the EU: network portion, QoS flow, DRB, SRB and QoE measurement configuration; • the actual or estimated energy consumption of the UE for a configuration used by the UE is greater than a first threshold; • The QoS of a configuration used by the UE is below a second threshold; and • a periodic or semi-static schedule configured by the network. In some embodiments, these example methods may also include configuring one or more of the following elements for operation in the cell according to the specified additional configuration: the UE, and one or more additional UEs. In some embodiments, these example methods may also include receiving, from the UE, one or more of the following information: • an indication of the UE's feedback capabilities for network-provided configurations; and • dynamic information associated with the current conditions of the UE. In such a case, the one or more configurations sent to the UE are based on the information received. Other embodiments include UE (e.g., wireless devices, 1779950 of 88 IoT devices, etc. or components thereof) and network nodes (e.g., base stations, eNBs, gNBs, ng-eNBs, etc. or components thereof) configured to perform operations corresponding to any of the example methods described herein. Other embodiments include non-transient, computer-readable media that store program instructions which, when executed by processing circuits, configure such UEs and network nodes to perform operations corresponding to any of the example methods described herein. These and other embodiments described herein enable a user device to provide information about the actual power consumption of the user device, energy efficiency (EE), and / or the impact of QoS, for one or more configurations provided by a network node. In this way, the embodiments facilitate improved network discovery of configurations that can reduce the power consumption of the user device for a particular QoS requirement, for all user devices that share at least some common characteristics and / or conditions (e.g., manufacturer, chipset, software, RF architecture, radio conditions, cell traffic conditions, etc.). For example, by using machine learning (ML) techniques, the network can adapt to the specific characteristics of user equipment, as well as the different feedback metrics provided by each user device. Furthermore, devices are incentivized to provide accurate response parameters, as this helps train the ML model used to generate improved configurations for all devices with the same characteristics and / or conditions. At a higher level, these implementation methods facilitate improved management of user equipment energy consumption by the network. These and other objects, features and advantages of the forms of implementation of this disclosure will become evident upon reading the following detailed description in view of the drawings briefly described below. BRIEF DESCRIPTION OF THE DRAWINGS Figures 1-2 illustrate two high-level views of an example 5G / NR network architecture. Figure 3 shows an example configuration of the NR user plane (UP) and control plane (CP) protocol stacks. Figure 4 shows an example configuration of the frequency domain 1779950 of 88 for a UE NR. Figures 5-6 show example NR slot structures. Figure 7 shows a block diagram of a model-based system according to various embodiments of this disclosure. Figure 8 shows a signal flow between a user device, a first network node, and a second network node, according to various ways of implementing this disclosure. Figure 9 shows a flowchart of an example method for a user device (e.g., a wireless device), according to various embodiments of this disclosure. Figure 10 shows a flowchart of an example method for a network node (e.g., base station, eNB, gNB, ng-eNB, etc.), according to various embodiments of this disclosure. Figure 11 shows a communication system according to various forms of implementation of this disclosure. Figure 12 shows a user team according to various ways of carrying out this disclosure. Figure 13 shows a network node according to various forms of implementation of this disclosure. Figure 14 shows a host computer system according to various forms of implementation of this disclosure. Figure 15 is a block diagram of a virtualization environment in which functions implemented by some forms of realization of this disclosure can be virtualized. Figure 16 illustrates communication between a host computer system, a network node, and a UE through multiple connections, at least one of which is wireless, according to various embodiments of this disclosure. DETAILED DESCRIPTION Some of the embodiments contemplated herein will now be described in more detail with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the object disclosed herein, and the object disclosed herein should not be interpreted as being limited only to the embodiments set forth herein; rather, these embodiments are provided as examples to convey the scope of the object to those skilled in the art. 1779950 of 88 In general, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or can be inferred from the context in which they are used. All references to an element, apparatus, component, means, step, etc., should be clearly interpreted as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method and / or procedure disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or it is implied that one step must follow or precede another.Any feature according to any of the embodiments set forth herein may be applied to any other embodiment, where appropriate. Likewise, any advantage according to any embodiment may be applied to any other embodiment, and vice versa. Other features and advantages of the appended embodiments will become apparent from the following description. Furthermore, the following terms are used throughout the description that follows: • Radio node: as used herein, a “radio node” may be a “radio access node” or a “wireless device”. • Radio Access Node: As used herein, a “radio access node” (or equivalently, “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that functions to wirelessly transmit and / or receive signals. Examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) (gNB) base station in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved (eNB) Node B in a 3GPP LTE network), distributed base station components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., a micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, and a transmission point. 1779950 of 88 (TP), a transmit receiving point (TRP), a remote radio unit (RRU or RRH) and a relay node. Core network node: As used herein, a “core network node” is any type of node in a core network. Examples of a core network node include, for instance, a Mobility Management Entity (MME), a Service Gateway (SGW), a PDN Gateway (P-GW), a Policy and Billing Rules Function (PCRF), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Billing Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a Location Management Function (LMF), or similar. Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by means of wireless communication with network nodes and / or other wireless devices. Wireless communication may involve the transmission and / or reception of wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air. Unless otherwise specified, the term “wireless device” is used interchangeably herein with “user equipment” (or “UE” for short).Some examples of a wireless device include, but are not limited to, smartphones, mobile phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), mobile-type communication (MTC) devices, Internet of Things (IoT) devices, wireless vehicle-mounted terminal devices, etc. 1779950 of 88 • Network Node: As used herein, a “network node” is any node that is part of the radio access network (e.g., a radio access node or equivalent name discussed previously) or the core network (e.g., a core network node discussed previously) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or other network nodes or equipment in the cellular communications network, to enable and / or provide wireless access to the wireless device, and / or to perform other functions (e.g., management) in the cellular communications network. • Base station: as used herein, a “base station” may comprise a physical or logical node that transmits or controls the transmission of radio signals, e.g., eNB, gNB, ngeNB, en-gNB, centralized unit (CU) / distributed unit (DU), transmitter radio access node, transmit point (TP), transmit receive point (TRP), remote radio head (RRH), remote radio unit (RRU), distributed antenna system (DAS), relay, etc. In the following description, the term “message” is used generically to refer to any type of structured information carrier used by a first entity to send information to a second entity. Specific examples include messages or information elements (IEs) defined (or to be defined) in the 3GPP specifications for existing or newly defined interfaces, architectures, and / or protocol layers (e.g., RRC, MAC, Xn, F1AP, etc.). Furthermore, “message” can be used in conjunction with a numeric modifier, for example, “first message,” “second message,” etc. Numeric modifiers do not imply a strict temporal order for these messages unless explicitly stated otherwise. Rather, they are intended to distinguish between different messages with distinct content. Furthermore, the fact that a first entity receives a message "from" a second entity does not preclude the possibility that the message travels through one or more intermediate entities. Likewise, the fact that a first entity transmits a message "to" a second entity does not preclude the possibility that the message travels through one or more intermediate entities. 1779950 of 88 The definitions above are not intended to be exhaustive. In other words, several of the terms above may be explained and / or described elsewhere in this disclosure using the same or similar terminology. However, to the extent those other explanations and / or descriptions conflict with the definitions above, the definitions above shall prevail. Note that the description in this document focuses on a 3GPP cellular communications system and, as such, often uses 3GPP or 3GPP-like terminology. However, the concepts discussed here are not limited to a 3GPP system. Furthermore, although the term “cell” is used here, it should be understood that (particularly with regard to 5G NR) beams can be used instead of cells, and as such, the concepts described here apply equally to both cells and beams. As briefly mentioned earlier, the energy consumption models of currently used user equipment can give the network a qualitative idea of ​​the energy efficiency advantages of a particular configuration. However, these models do not accurately reflect the actual energy consumption of the equipment, which can vary considerably depending on the devices, manufacturers, chipsets, software, and other factors. This issue is discussed in more detail below, following the analysis of the RN architecture, protocols, and physical layer. Figure 2 shows a high-level view of another example 5G network architecture, which includes the NG-RAN 299 and the 5GC 298. As shown in the figure, the NG-RAN 299 can include gNBs (e.g., 210a,b) and ng-eNBs (e.g., 220a,b) that are interconnected via their respective Xn interfaces. The gNBs and ng-eNBs are also connected via NG interfaces to the 5GC 298, specifically to the Access and Mobility Management Functions (AMF, e.g., 230a,b) via their respective NG-C interfaces and to the User Plane Functions (UPF, e.g., 240a,b) via their respective NG-U interfaces. In addition, AMFs can communicate with one or more policy control functions (PCF, for example, 250a,b) and network exposure functions (NEF, for example, 260a,b). Each gNB 210 can support the NR radio interface, including frequency-division duplexing (FDD), time-division duplexing (TDD), or a combination of these. Each ng-eNB 220 can support the fourth-generation (4G) Long-Term Evolution (LTE) radio interface. However, unlike conventional LTE eNBs, the ng-eNB 220s connect to the 5GC via the NG interface. Each gNB and ng-eNB can serve a coverage area. 1779950 of 88 geographic that includes one more cell, such as cells 211a-by 221a-b shown in Figure 2. Depending on the cell it is in, a UE 205 can communicate with the gNB or ng-eNB that serves that cell through the NR or LTE radio interface, respectively. Although Figure 2 shows the gNB and ng-eNB separately, it is possible for a single NG-RAN node to provide both types of functionality. 5G / NR technology shares many similarities with LTE. For example, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the UL. In the time domain, the physical resources of NR DL and UL are organized into equal-sized 1 ms subframes. A subframe is further divided into multiple equal-length slots, each containing multiple OFDM-based symbols. However, time-frequency resources can be configured much more flexibly for an NR cell than for an LTE cell. For example, instead of LTE's fixed 15 kHz OFDM subcarrier spacing (SCS), NR's SCS can range from 15 to 240 kHz, with even larger SCSs being considered for future NR versions. In addition to providing coverage through cells, as in LTE, NR networks also provide coverage through "beams." Generally, a downlink (DL, i.e., from the network to the UE) "beam" is a coverage area of ​​a reference signal (RS) transmitted by the network that can be measured or monitored by a UE. In NR, for example, the RS can include any of the following: PBCH synchronization / block signal (SSB), channel status information RS (CSI-RS), tertiary reference signals (or any other synchronization signal), positioning RS (PRS), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc. Generally, SSB is available to all UEs regardless of their network connection status, while other RSs (e.g., CSI-RS, DM-RS, PTRS) are associated with specific UEs that have a network connection. Figure 3 shows an example configuration of the NR user plane (UP) and control plane (CP) protocol stacks between a UE (310), a gNB (320), and an AMF (330), as shown in Figures 1-2. The physical (PHY), media access control (MAC), radio link control (RLC), and packet data convergence protocol (PDCP) layers between the UE and the gNB are common to both UP and CP. The PDCP layer provides encryption / decryption, integrity protection, sequence numbering, reordering, and duplicate detection. 1779950 of 88 for CP as well as for UP. In addition, PDCP provides header compression and retransmission for UP data. On the upstream side, Internet Protocol (IP) packets arrive at the PDCP layer as Service Data Units (SDUs), and PDCP creates Protocol Data Units (PDUs) for delivery to the RLC. The Service Data Adaptation Protocol (SDAP) layer handles Quality of Service (QoS), including mapping between QoS flows and Data Radio Carriers (DRBs) and marking QoS Flow Identifiers (QFIs) on the upper and lower layers (UL and DL). The RLC layer transfers the PDUs from PDCP to the MAC layer via Logical Channels (LCHs). The RLC layer is responsible for error detection / correction, concatenation, segmentation / reassembly, sequence numbering, and reordering of data transferred to / from the upper layers.The MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ error correction (HARQ), and dynamic scheduling (on the gNB side). The PHY layer provides transport channel services to the MAC layer and manages the transfer across the NR radio interface, for example, through modulation, coding, antenna mapping, and beamforming. On the CP side, the Non-Access Layer (NAS) sits between the UE and the AMF and handles UE / gNB authentication, mobility management, and security control. The RRC layer sits below the NAS in the UE but terminates in the gNB instead of the AMF. The RRC controls communication between the UE and the gNB at the radio interface, as well as UE mobility between cells in the NG-RAN. The RRC also disseminates System Information (SI) and performs the establishment, configuration, maintenance, and release of Signaling Radio Carriers (SRBs) and DRBs used by the UE. The RRC also controls the addition, modification, and release of Carrier Aggregation (CA) and Dual Connectivity (DC) configurations for the UE. The RRC also performs various security functions, such as key management. After a device is powered on, it will remain in the RRC_IDLE state until an RRC connection to the network is established, at which point the device will transition to the RRC_CONNECTED state (for example, when data transfer can occur). The device returns to the RRC_IDLE state when the network connection is released. In the RRC_IDLE state, the UE's radio is active during a discontinuous receive (DRX) schedule configured by the upper layers. During active DRX periods (also called "DRX On durations"), a UE in RRC_IDLE receives 1779950 of 88 The SI broadcast in the cell where the UE is camping, performs measurements of neighboring cells to support cell reselection, and monitors a paging channel on PDCCH for 5GC pages via gNB. An NR UE in the RRC_IDLE state is not known to the gNB serving the cell where the UE is camping. However, NR RRC includes an RRC_INACTIVE state where a UE is known (e.g., through the UE context) by the gNB server. RRC_INACTIVE has some properties similar to the "suspended" state used in LTE. As used herein, the term “connected state” encompasses RRC_CONNECTED and similar operational states of the UE with and / or to a wireless network (e.g., E-UTRAN, NG-RAN, etc.). Likewise, the term “not connected state” encompasses RRC_IDLE, RRC_INACTIVE, and similar operational states of the UE with and / or to a wireless network (e.g., E-UTRAN, NG-RAN, etc.). Support for bandwidths exceeding 20 MHz was introduced in LTE Rel-10 carriers, with backward compatibility for LTE Rel-8. Thus, an LTE Rel-10 carrier exceeding 20 MHz would appear as a series of component carriers (CCs) to an LTE Rel-8 (“legacy”) terminal. This technique is generally known as carrier aggregation (CA). A dual connectivity (DC) framework was introduced in LTE Rel-12. DC refers to an operating mode where a UE, in the RRC_CONNECTED state, consumes radio resources provided by at least two different network nodes (or points) connected to each other via a non-ideal backhaul network. In LTE, these two network nodes are called the master eNB (MeNB) and secondary eNB (SeNB), but can be more generally referred to as the master node (MN) and secondary node (SN), respectively.The NR also includes new CC variants, including multi-RAT CC (MR) which involves a connection to an NR node (e.g., gNB) and a second connection to an eNB. In DC, a UE is configured with a Master Cell Group (MCG) associated with the MN and a Secondary Cell Group (SCG) associated with the SN. Each GC is a group of server cells that includes a MAC entity, a set of logical channels with associated RLC entities, a primary cell (PCell), and optionally, one or more secondary cells (SCells). The term “special cell” (or “SpCell” for short) refers to the PCell of the MCG or the PCell of the SCG (also called the “primary cell of the SCG” or “PSCell”) depending on whether the UE's MAC entity is associated with the MCG or the SCG, respectively. In non-DC operation (e.g., CA), SpCell refers to the PCell. A SpCell is always active and supports 1779950 of 88 the PUCCH transmission and containment-based random access by the UE. Figure 4 shows an example frequency-domain configuration for a UE NR. In Rel-15 NR, a UE can be configured with up to four carrier bandwidth (BWP) parts within a DL carrier bandwidth, with only one DL BWP active at any given time. A UE can be configured with up to four BWPs within an UL carrier bandwidth, with only one UL BWP active at any given time. If a UE is configured with a supplemental UL, it can be configured with up to four additional BWPs within the supplemental UL carrier bandwidth, with only one supplemental UL BWP active at any given time. Common Reference Bases (CRBs) are numbered from 0 to the end of the carrier bandwidth. Each configured Bandwidth Parameter (BWP) for a UE has a common reference of CRB0, so a configured BWP can start at a CRB greater than zero. CRB0 can be identified by one of the following network-provided parameters, as defined in section 4.4 of 3GPP TS 38.211 (v16.5.0): • PRB-index-DL-common for DL ​​in a primary cell (PCell, for example, PCell or PSCell); • PRB-index-UL-common for UL on a PCell; • PRB-index-DL-Dedicated for DL ​​in a secondary cell (SCell); • PRB-index-UL-Dedicated for UL in a SCell; and • PRB-index-SUL-common for a supplemental UL. Thus, a user's equipment can be configured with a narrow BWP (e.g., 10 MHz) and a wide BWP (e.g., 100 MHz), each starting at a particular CRB, but only one BWP can be active for the user's equipment at any given time. Within a BWP, PRBs are defined and numbered in the frequency domain from 0 to NBWP, where i is the index of the particular BWP for the carrier. For example, as shown in Figure 3, BWP0 includes PRBs 0 to N1, BWP1 includes PRBs 0 to N2, and BWP2 includes PRBs 0 to N3. NR supports several SCS values ​​Δf = (15 × 2μ) kHz, where pe(0,1,2,3,4) are called “numerologies.” The numerology μ = 0 (i.e., Δf = 15 kHz) provides the basic (or reference) SCS, which is also used in LTE. Symbol duration, cyclic prefix (CP) duration, and slot duration are inversely related to the SCS or numerology. For example, there is one slot (of 1 ms) for every 19 1779950 of 88 subframes for Δf=15kHz, two 0.5 ms slots per subframe for Δf=30kHz, etc. Furthermore, the maximum carrier bandwidth is directly related to the numerology based on 2μ · 50 MHz. Table 1 summarizes the currently supported NR numerologies and their associated parameters. The network can be configured with different DL and UL numerologies. Table 1. μ 21 / = 2 · 15 (kHz) Cyclic Prefix (CP) CP Duration Symbol Duration Symbol + CP Slot Duration Carrier Max BW 0 15 Normal 4.69 μ8 66.67 μ8 71.35 μ8 1 ms 50 MHz 1 30 Normal 2.34 μ8 33.33 μ8 35.68 μ8 0.5 ms 100 MHz 2 60 Normal, Extended 1.17 μ8 16.67 μ8 17.84 μ8 0.25 ms 200 MHz 3 120 Normal 0.59 μ8 8.33 μ8 8.92 μ8 125 μ8 400 MHz 4 240 Normal 0.29 μ8 4.17 μ8 4.46 μ8 62.5 μ8 800 MHz Figure 5 shows an example time-frequency resource grid for an NR slot. As illustrated in Figure 5, a resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a slot duration of 14 symbols. Similar to LTE, a resource element (RE) consists of one subcarrier in a slot. An NR slot can include 14 OFDM symbols for the normal cyclic prefix (e.g., as shown in Figure 3) and 12 symbols for the extended cyclic prefix. NR also supports Type B scheduling, also known as "mini-slots." These are shorter than time slots, typically between one and one symbol shorter than the number of symbols in a slot (for example, 13 or 11), and can start on any symbol within a slot. Mini-slots can be used if the transmission duration of a slot is too long and / or if the start of the next slot (slot alignment) occurs too late. Applications of mini-slots include unlicensed spectrum and latency-critical transmission (for example, URLLC). However, mini-slots are not service-specific and can also be used for eMBB or other services. Figure 6 shows an example NR slot structure comprising 14 symbols. In this arrangement, the PDCCH is confined to a region containing a specified number of symbols and a specified number of subcarriers, called the control resource set (CORESET). In the example structure shown in Figure 6, the first two symbols contain PDCCHs, and each of the remaining 12 symbols contains physical data channels (PDCHs), i.e., PDSCHs or PUSCHs. However, depending on the particular CORESET configuration (discussed later), the PDCCH may be the one used. 1779950 from 88 onwards), the first two slots may also carry PDSCH or other information, as required. The smallest unit used to define CORESET is the REG, which spans one PRB in frequency and one OFDM symbol in time. In addition to the PDCCH, each REG contains demodulation reference signals (DM-RS) to aid in estimating the radio channel over which that REG is transmitted. An NR control channel element (CCE) consists of six REGs. These REGs can be contiguous or frequency-distributed. When the REGs are frequency-distributed, the CORESET is said to use an interleaved mapping of REGs to a CCE, whereas if the REGs are frequency-contiguous, a non-interleaved mapping is used. Interleaving can provide frequency diversity. Not using interleaving is beneficial in cases where channel knowledge allows the use of a precoder in a specific part of the spectrum, which improves the SINR at the receiver. As with LTE, NR data scheduling can be performed dynamically, for example, in slots. In each slot, the base station (e.g., the gNB) transmits downlink control information (DCI) via the PDCCH, indicating which UE is scheduled to receive data in that slot, as well as which RB will carry that data. A UE first detects and decodes the DCI, and if it includes downlink scheduling information for the UE, it receives the corresponding PDSCH based on that information. The DCI 1_0 and 1_1 formats are used to transmit the PDSCH schedule. Similarly, the DCI in PDCCH may include UL grants that indicate which UE is scheduled to transmit data on PUCCH in that slot, as well as which RB will carry that data. A UE first detects and decodes the DCI, and if the DCI includes an uplink grant for the UE, it transmits the corresponding PUCCH on the resources indicated by the UL grant. DCI formats 0_0 and 0_1 are used to transmit UL grants for PUCCH, while other DCI formats (2_0, 2_1, 2_2, and 2_3) are used for other purposes, including transmitting slot format information, reserved resources, transmit power control information, and so on. In NR Rel-15, DCI formats 0_0 / 1_0 are called “fallback DCI formats,” while DCI formats 0_1 / 1_1 are called “non-fallback DCI formats.” Fallback DCIs support resource allocation type 1, where the DCI size depends on the size of the active BWP. As such, DCI formats 0_1 / 1_1 are intended for scheduling a single TB transmission with a 1779950 of 88 limited flexibility. On the other hand, non-fallback DCI formats can provide flexible TB scheduling with multi-layer transmission. A DCI includes a payload supplemented with a cyclic redundancy check (CRC) of the payload data. Since the DCI is sent on the PDCCH received by multiple user equipment, it is necessary to include an identifier for the destination equipment. In NR, this is done by encoding the CRC with a Radio Network Temporary Identifier (RNTI) assigned to the UE. Most commonly, the cell RNTI (C-RNTI) assigned to the destination equipment by the server cell is used for this purpose. The DCI payload, along with an identifier-encrypted CRC, is encoded and transmitted over the PDCCH. Given the pre-configured search spaces, each UE attempts to detect a PDCCH addressed to it based on multiple hypotheses (also called “candidates”) in a process known as “blind decoding.” PDCCH candidates span 1, 2, 4, 8, or 16 CCEs, and the number of CCEs is called the aggregation level (AL) of the PDCCH candidate. If more than one CCE is used, the information from the first CCE is repeated across the other CCEs, increasing robustness for a given payload size. In other words, PDCCH link adaptation can be achieved by adjusting the AL. Depending on the AL, PDCCH candidates can be located at various time-frequency locations within the CORESET. Once a UE decodes a DCI, it decrypts the CRC using the RNTI(s) assigned to it and / or associated with the specific PDCCH search space. If there is a match, the UE considers the detected DCI to be addressed to it and follows the instructions (e.g., programming information) in the DCI. For example, to determine the modulation order, target code rate, and TB size(s) for a scheduled PDSCH transmission, the UE first reads the 5-bit Modulation and Coding Scheme (IMCS) field in the DCI (e.g., formats 1_0 or 1_1) to determine the modulation order (Qm) and target code rate (R) based on the procedure defined in section 5.1.3.1 of 3GPP TS 38.214 (v16.5.0). Subsequently, the UE reads the Redundancy Version (RV) field in the DCI to determine the redundancy version. Based on this information, together with the number of layers (o) and the total number of PRBs allocated before rate adaptation (nPRB), the UE determines the transport block size (TBS) for the PDSCH according to the procedure defined in section 5.1.3.2 of 3GPP TS 38.214 (v16.5.0). The DCI may also include information about various time lags (by 1779950 of 88 example, in slots or subframes) between PDCCH and PDSCH, PUSCH, HARQ, and / or CSIRS. For example, the K0 offset represents the number of slots between the UE's PDCCH reception of a PDSCH programming DCI (for example, 1_0 or 1_1 formats) and the subsequent PDSCH transmission. Likewise, the K1 offset represents the number of slots between this PDSCH transmission and the UE's response HARQ ACK / NACK transmission on the PUSCH. Furthermore, the K3 offset represents the number of slots between this response ACK / NACK and the corresponding data retransmission on the PDSCH. Additionally, the K2 offset represents the number of slots between the UE's PDCCH reception of a PUSCH grant DCI (for example, 0_0 or 0_1 formats) and the subsequent PUSCH transmission. Each of these displacements can take values ​​of zero and positive integers. K0 is part of a PDSCH time-domain resource allocation (TDRA). Also included in the PDSCH TDRA is a slot length indicator value (SLIV) that identifies a particular combination of a starting symbol (S) and a length (L) of the resource allocation. In general, S can be any symbol 0–13, and L can be any number of symbols starting from S to the end of the slot (i.e., symbol 13). The SLIV can be used as an index in a table of (S, L) combinations. Similarly, K2 is part of a PUSCH TDRA that also includes a corresponding SLIV. Depending on the DRX configuration, a UE may expend a substantial portion of its energy decoding the PDCCH without detecting a DL scheduling allocation or UL resource grant intended for it. Techniques that reduce unnecessary PDCCH monitoring, allow a UE to enter sleep mode more frequently and / or for longer periods, or allow a UE to wake up less frequently and / or for shorter periods can be beneficial. One such technique, introduced in LTE Rel-15 for LTE-M and NB-IoT, is a wake-up signal (WUS) that can be detected by the UE using significantly less energy compared to MPDCCH / NPDCCH detection (generically referred to as “PDCCH detection”). When a UE detects a WUS intended for it, the UE wakes up and activates a conventional PDCCH decoder. The decoding time of a WUS is considerably shorter than that of a full (M / N)PDCCH because the WUS only needs to hold one bit of information. In comparison, the (NPDCCH) can hold up to 35 bits of information. This reduced decoding time results in lower power consumption for the equipment and 1779950 of 88, longer battery life. The waiting time between actual WUSs also improves these aspects of equipment performance. In other words, for the same channel and the same miss detection rate, it is possible to transmit a shorter WUS compared to the PDCCH, since the WUS carries less information. A shorter WUS requires the user equipment's receiver to be powered on for less time and allows for faster baseband processing by the user equipment, thus reducing the user equipment's power consumption. In some cases, a UE may include a dedicated, low-complexity receiver for the WUS. The primary receiver will only power on (for example, to decode PDCCH) based on an indication that the dedicated receiver has detected a WUS. This arrangement can allow the UE to remain in deep sleep mode for extended periods with very low power consumption. Energy consumption is a critical operating characteristic for UEs, to the point that it affects, and in some cases dictates, the configuration of both UEs and the network for UEs operating in specific network and traffic scenarios. For example, the network is expected to configure user equipment to prevent excessive energy consumption, extend battery life, and avoid overheating. As a general principle, the power consumption of user equipment can be reduced by 1) increasing the proportion of operating time that the user equipment spends in a standby or low-power state, especially in deep sleep mode, where a large part of the user equipment's radio frequency (RF) circuitry is powered off, and / or 2) operating with the minimum necessary receiver configuration when monitoring signals transmitted over the network (e.g., minimum number of receiving antennas, reduced receive bandwidth, minimum required receive quality, etc.). The network can facilitate these reductions in user equipment power consumption by adjusting various parameters in the user equipment configurations signaled by the network to the respective user equipment. Network configurations for reducing user equipment power consumption may include any of the following: • UE DRX configurations that allow for short monitoring intervals and long rest intervals in between. This can include DRX for paging monitoring in the RRC_IDLE and RRC_INACTIVE states (e.g., period, paging opportunity (PO) length, number of POs, etc.) as well as DRX 1779950 of 88 connected (cRDX) for data scheduling in the RRC_CONNECTED state (e.g., period, length of onDuration, etc.) • Minimize idle timers, including the cRDX idle timer from last data scheduling to return to cRDX and / or the data idle time from last data scheduling to return to the RRC_IDLE state. • Enable mechanisms that provide advance notice of the need for monitoring in the next intervals, including the previously mentioned WUS to indicate the status of the next onDuration in the RRC_CONNECTED state, as well as the PEI to indicate the status of the next PO in the RRC_IDLE state. • Ensure sufficient time for receiver reconfiguration UE from a minimal mode to an optimized performance mode, including cross-slot scheduling with a minimum PDCCH / PDSCH separation (i.e., K0), PDCCH skip durations, PDCCH search space adaptations, etc. • Provide guarantees for the maximum receiver performance required to handle the programmed data formats, such as indicating the maximum number of MIMO layers to be programmed. • Avoid unnecessary measurements that reduce UE sleep opportunities, such as reducing measurements in the RRC_CONNECTED state for stationary UEs in good signal conditions. • Relax the measurement requirements of the UE (e.g., for Radio Resource Management (RRM), Radio Link Monitoring (RLM), Beam Fault Detection (BFD), etc.) in the RRC_CONNECTED, RRC_IDLE and / or RRC_INACTIVE states. • Activation of the Unified Air Interface (UAI) functionality so that the UE indicates specific configuration preferences, etc. • Reduction of energy consumption due to SCells, for example, through dynamic release / activation / deactivation of SCells, SCell inactivity, etc. As another general principle, UE configurations that provide favorable UE energy consumption or energy efficiency (EE) may impose undesirable effects on grid performance and / or other aspects of performance 1779950 of 88 UE. For example, data latency may increase, equipment and cell throughput may decrease, or network signaling overhead may increase. To understand the trade-offs, the network needs to understand the benefits of user equipment efficiency (EE) that accompany the undesirable effects of a user equipment configuration. The user equipment energy consumption models currently in use (for example, those described in 3GPP TR 38.814) can give the network a qualitative understanding of the user equipment energy efficiency (EE) benefits of a particular configuration. However, the network lacks information on how a given configuration actually affects the equipment's EE and, optionally, its QoS. Typically, configurations are based on intuitive interpretations, such as that a UE sleep duration of 100 ms will save more energy compared to a sleep duration of 50 ms. However, the practical designs of user equipment are considerably more complex and varied, and cannot be captured by these simple models. For example, these models do not show how other configurations affect the equipment's EE, such as the choice of BWP and / or CC, the use of a smaller BWP, or moving the equipment to a different carrier, the combination of CCs configured with the same total BW that provides the best EE for the equipment, and so on. In general, the answers to these and similar questions can depend on the UE model, the manufacturer, the chipset, the software, the RF / antenna configuration, and so forth. For example, depending on the user equipment's RF implementation, the specific secondary circuits that are activated may be more important than the total number of activated circuits from the user equipment's energy efficiency (EE) perspective. These specific circuits may be implemented on different RF transceivers (and possibly processing chains) that are managed independently for power consumption, so the UE could disconnect the transceivers / processing chains associated with the unused circuits. In this way, different UE EEs can be obtained depending on how the active circuits are allocated to the independently managed hardware. Currently, the network has no way of obtaining this information from the UE. In general, there is no mechanism to determine the best EE configuration for a user's equipment, based on their quality of service requirements. In other words, the optimal, best, and / or preferred configuration for a 1779950 of 88 user equipment is necessarily a balance between competing EE and QoS requirements. Currently, the UE can provide the network with a preferred and / or desired configuration. However, this configuration provided by the UE does not take into account other factors known only to the network, such as current traffic conditions and / or the beamforming capabilities of the cell serving the UE. This can result in the configuration provided by the user equipment being unsuitable for the user equipment's quality of service requirements or negatively impacting network performance, while alternative configurations that provide similar EE benefits without these drawbacks may remain undiscovered by the user equipment and the network. Accordingly, the methods described in this disclosure provide flexible and efficient techniques for a UE to provide information about the UE's actual energy consumption, energy efficiency (EE), and / or the impact of quality of service (QoS) for one or more configurations provided by a network node. The network node (and, optionally, the RAN and / or the network operator (CN) serving the UE) can use this feedback information to train a machine learning (ML) model that can optimize one or more target metrics for the UE's EE and / or QoS and use the trained ML model to select configurations for other UEs by inference. The embodiments of this disclosure may provide various advantages, benefits, and / or solutions to problems. For example, the network may use feedback from a first UE to train the model used to select configurations that provide better UE energy efficiency for other UEs, provided that the other UEs have one or more characteristics and / or conditions in common with the first UE (e.g., manufacturer, chipset, software, RF architecture, radio conditions, cell traffic conditions, etc.). As another example, in certain embodiments, a UE may provide a relative score for the configuration(s) with the disclosure of sensitive and / or proprietary information about the UE's energy consumption. For example, using machine learning (ML) techniques, the network can adapt to the specific characteristics of user devices (e.g., device type, chip vendor, software version, etc.) as well as the different feedback metrics provided by those devices. Furthermore, devices are incentivized to provide accurate response parameters, as this helps train the ML model used to generate the data. 1,779,950 of 88 improved configurations for all devices with the same characteristics or conditions. Even so, the network can filter device information to remove inaccurate or biased entries. More generally, the implementation forms facilitate improved discovery of network configurations that will provide reduced UE power consumption for a particular QoS requirement, for all UEs that share at least some common characteristics and / or conditions. Figure 7 shows a block diagram of a model-based system according to several embodiments of this disclosure. In this example system, the network (e.g., the RAN nodes, such as the gNB 720) provides model inputs that include static information about the UE (710) and / or the cell in which the UE is operating. Static information can provide model generalization, allowing a model trained for one cell / UE to be reused for a similar cell / UE. Static information can also be used when selecting a model. For example, a model might be specific to a particular device vendor or a particular energy metric. Some examples of static information are given below: • Static cell information, such as antenna configuration, cell size, carrier frequency(ies), bandwidth, multi-user MIMO capabilities, etc. • Cell statistics, such as block error rate (BLER), modulation and coding scheme (MCS), outer loop settings, throughput, signal-to-interference-noise (SINR) load, etc. • Static user equipment information, such as antenna configuration, AC / DC support, transmission mode support, EE priority level (e.g., low if connected to a power outlet), manufacturer, mode, chipset vendor, chipset model, user equipment class and / or performance category, software version, etc. In this example system, the model inputs provided by the network also include dynamic information about the user equipment and / or the cell in which the user equipment is operating. Some examples of dynamic information are provided below: 1779950 of 88 Dynamic EU information or traffic information, for example, historical and / or forecast; or Signal measurements, for example, RSRP, RSRQ, RSSI, timing advance, etc.; or Mobility information, for example, speed, number of transfers in the last x seconds, etc.; or Type of service and / or QoS requirements; or EU preferred EE configuration; or Battery life forecast / remaining battery level; or If it is connected to a power outlet; • Dynamic cell information, including traffic information such as PRB utilization, for example, during the last x seconds before the UE connects; or Number of users connected, for example, during the last x seconds before the equipment connects; or Number of carriers, for example, total or by carrier type. The model can be trained based on this information provided by the network. The trained model can then output one or more configurations for a specific UE operating in the cell (for example, the one shown in Figure 7), based on the use of one or more known characteristics of the specific UE and / or the cell (for example, static information). The model can also receive as input information from the specific UE regarding the UE's EE and / or QoS for the one or more provided configurations, which can be used to further train the model. In some implementations, the network node (e.g., gNB) serving the cell can train the model and use it for inference. In other implementations, a first network node (e.g., gNB) responsible for setting UE configurations receives the model from a second network node (e.g., another gNB, CN function, OAM, etc.) responsible for training it. For example, the first network node might be the destination node of a UE mobility operation, while the second network node might be the source node of the UE mobility operation. In some cases, the second network node might have a more up-to-date and / or better-trained model than the first network node. In other implementations, training and inference can be performed and / or hosted by network nodes or functions outside the RAN, such as 1779950 of 88 by newly defined network functions (NFs) or newly defined operations for existing NFs in the 5GC. When hosted in this way, the model would receive inputs and provide outputs to the network nodes serving the cells in the RAN. In some implementations, training and inference can be based on artificial intelligence and / or machine learning, referred to as “AI / ML” for brevity. A 3GPP study on AI / ML aims to examine the functional framework for RAN intelligence enabled by improved data collection through use cases, examples, and so on, and to identify the potential impacts of standardization on current NG-RAN nodes and interfaces. Specific objectives include defining the high-level principles and functional framework for AI / ML-enabled RAN intelligence, as well as identifying the benefits of AI / ML-enabled NG-RAN through potential use cases, such as energy savings, load balancing, mobility management, coverage optimization, and so forth. The applicant has acknowledged that reinforcement learning (RL) is a specific type of AI / ML that may be particularly beneficial for the ways in which this disclosure is made. In RL, the model continuously interacts with its environment and receives implicit (and sometimes delayed) feedback in the form of “reward signals.” RL maximizes short-term rewards but can also make decisions that are irrational in the short term but yield long-term gains. More generally, RL models attempt to maximize expected future rewards by exploiting existing knowledge and exploring the action space in different scenarios, such as network and / or UE configurations. Figure 8 shows a signal flow between a user equipment (810), a first network node (820), and a second network node (830) illustrating various ways of implementing this disclosure. In this example arrangement, the first network node serves the cell in which the UE is or will be operating, while the second network node may be another RAN node, a CN node or function, an OAM function, etc. Although the operations shown in Figure 8 have numerical labels, these are not intended to imply a corresponding execution order unless explicitly stated otherwise. Optional operations are indicated by dashed lines. Operation 0 is the model training, discussed previously. This can be performed by the first node of the network or by the second network, in several ways. 1779950 of 88 implementation. However, it is indicated as optional so as not to exclude scenarios in which a fully trained model is used for subsequent operations. In operation 1, the first network node selects user equipment configurations based on model inference, as briefly discussed above and in more detail below. For example, each configuration might include settings or values ​​for one or more of the following: • DRX while the UE is operating in a state connected to the wireless network (e.g., cRDX in RRC_CONNECTED); • DRX while the UE is operating in a state not connected to the wireless network (e.g., DRX in RRC_IDLE or RRC_INACTIVE); • WUS while the UE is operating in a state connected to the wireless network; • PEI while the UE is operating in a state not connected to the wireless network; • measurement or monitoring of beams (e.g., SSB, CSI-RS) transmitted by the network node, including for radio resource management (RRM) • carrier aggregation (CA), including cell activation / deactivation / sdormancy, cross-carrier scheduling, cell combinations, etc.; • dual connectivity (DC); • bandwidth parts (BWP); • MIMO reception and / or transmission; • PDCCH control, including cross-slot programming, PDCCH bypass, SS switching, etc.; and • QoS. In operation 2, the first network node sends the selected configuration(s) to the UE. In operation 3, the UE determines the EE and / or QoS information associated with the received configuration(s); this determination can also be based on the UE's data traffic, for example, actual and / or projected. In operation 4, the user equipment sends information about the configuration(s) to the first network node, including the determined EE and / or QoS information (or its indication). Figure 8 also shows other optional operations. In operation 5, the first network node can send the UE one or more new configurations based on the feedback received in operation 4. In operation 6, the UE can send the first network node an indication of the UE's capabilities to support the 1779950 of 88 feedback. In operation 7, the user equipment can send the first network node an indication of the user equipment's dynamic information, such as any of the user equipment dynamic information mentioned previously. For example, the first network node can base the configuration(s) sent to the UE in operation 2 (and optionally in operation 5) on the indicated capabilities and / or the UE's dynamic information. Furthermore, the indicated capabilities and / or the user equipment's dynamic information can be used to train the model. In some embodiments, the first network node can request the model from the second network node in operation 8, and the second network node responds with the model in operation 9. This arrangement can be used when the second network node trains the model or when the second network node has a version of the model that is more accurate, newer, and / or better trained than a version used by the first network node. The following section will discuss in more detail various implementation methods related to user team feedback associated with network-provided configurations. In some implementations, the UE can return a value between [0, N], where a value higher than N indicates the best score (or vice versa). Such values ​​can be signaled by configuration; for example, the UE can signal a list of values, each associated with a configuration that may or may not be active in the UE. Alternatively, each value can be associated with a group of configurations, for example, those that share one or more features. In some embodiments, each value may comprise a combination of an EE metric and a QoS metric, or the two may be provided as two separate values. In other embodiments, the UE indicates a preference order for the configurations. To determine the energy metric, in one embodiment, the user team can directly measure its energy consumption over an observation period and obtain an estimate of the average current or power. The team can subtract other known contributions to energy consumption, for example, those due to display or application processor activity. In another embodiment, the user team can use a detailed model of its energy consumption (for example, energy levels in different operating states) by recording its activity timeline (for example, sequence of operations, states of 1779950 of 88 rest, transitions, etc.) associated with a sequence of received / transmitted data and accumulate power in the relevant states. In some implementations, the user device can also report a score for a configuration that has not been used. For example, the user device could also estimate a score for a cRDX cycle parameter of 80 ms, in addition to a provided configuration with a parameter of 40 ms. To estimate the score, the user device can record the actual data arrival pattern and emulate its processing timeline for the same or similar data arrival when configured with a different setting. In some implementations, the network may provide a set of possible configurations (including parameter settings), and the user team provides feedback on all or a subset of the EE configurations in the set. The user team might estimate the score for each corresponding configuration based on prior experience or other sources of information, such as dry runs of the configurations, shared experience from other user teams with similar architectures, vendors, or software. For example, the user team might obtain information about other user teams' experiences from an external database and / or directly from the other user teams. In various implementations, the network can use feedback to understand the limitations of the user equipment—for example, which aspects of the configurations have the greatest impact on the EE and / or QoS of the user equipment. Based on this understanding, the network can provide configurations that further improve the EE and / or QoS for the particular UE implementation (for example, operation 5 in Figure 8). In some implementations, the possible configuration groups can be configured semi-statically by the network, for example, when a UE connects to a cell, when the UE enters the RRC_CONNECTED state, etc. Alternatively, the possible configurations can be changed dynamically depending on factors such as the traffic the UE is transmitting (for example, based on the DRBs configured for the UE by the network), the load on the cell, the buffer status reported by the UE, etc. Each configuration provided by the network can be associated with a QoS feature (for example, 5QI) or a combination of QoS features. Multiple configurations can be associated with the same QoS feature or with different QoS features. 1779950 of 88 the same combination of QoS features. In some embodiments, the UE would provide its feedback only for configurations associated with QoS features that apply to the UE's current traffic, currently configured DRBs, etc. In other embodiments, if the UE has current traffic and / or DRBs associated with different QoS features, the UE provides its feedback only for the configuration(s) associated with the highest-priority QoS feature. For example, if the user equipment is configured with a default DRB and a higher-priority DRB for carrying voice, the user equipment considers only the configurations associated with the combination of default and voice DRBs, or only the configurations associated with the higher-priority voice DRB. In some implementations, the network does not provide a set of possible configurations, and the UE provides feedback on the configurations and associated parameter settings. In one variant, the UE can indicate the QoS characteristic(s) it considered when providing feedback for a particular configuration, such as the QoS characteristic(s) for the currently configured DRBs. If a particular QoS characteristic was not considered in the UE's feedback, this may implicitly indicate that the UE cannot find a configuration that provides adequate EE for that QoS characteristic. The network can use this implicit information to deconfigure a DRB and stop the associated QoS flow. In a related variant, the UE receives an initial configuration or initial set of configurations from the network, and then provides a score based on an EE model provided by the network (e.g., as part of a model download) or pre-configured (e.g., as part of the 3GPP descriptive memory). In one example, the user equipment reports its energy consumption (e.g., milliwatt-hours), its power (e.g., milliwatts), or some generic unit consistent with the user equipment's reporting. The latter option can be used to avoid a global comparison of the UE equipment's absolute energy performance. In another example, the UE equipment returns an energy efficiency (EE)-related value in various formats, such as percentage, discrete value (e.g., class, label, etc.), absolute, relative to a reference, etc. The network attempts to minimize this metric, given that the network's QoS targets are being met. The user equipment may indicate that the QoS is unsatisfactory, suggesting that the network should use a different configuration. 1779950 of 88 In various implementations, the UE can provide feedback that could be a single value for an entire reporting period or a series of values ​​throughout the reporting period, with each value corresponding to a measurement interval within the reporting period. For example, if the reporting period is 100 ms and the measurement interval is 10 ms, the UE would include a set of 10 values ​​in the feedback, with the first value corresponding to the first 10 ms, the second value to the next 10 ms, and so on. This could be used by the network to correlate with other status parameters collected by the network, such as the traffic pattern during the reporting period, and use this information to configure other UEs. In some embodiments, the user equipment returns energy efficiency (EE) information for a configuration relative to a reference energy or power consumed by the user equipment in a reference operating state, such as the RRC_IDLE state, a standby state, etc. For example, the EE information might be for connected-mode operation relative to the energy consumption for a corresponding period of time in the RRC_IDLE state. In other embodiments, the reference level might be a well-defined power level in the user equipment (UE), known to the UE but not required to be disclosed to the grid. In still other embodiments, the reference might be a configuration specified in the descriptive memory or one previously provided by the grid. In some embodiments, the user equipment may provide energy efficiency (EE) information as a delta relative to a benchmark score. For example, if the benchmark score corresponds to a configuration where energy consumption and / or service quality are set to pre-configured levels, the delta score (e.g., combined for EE and service quality, or separate for both) would represent the deviation from that benchmark score. For example, the delta score reported by the user equipment may be a numerical value (e.g., between -5 and +5, where -5 represents the maximum negative deviation from the benchmark and +5 the maximum positive deviation from the benchmark).As another example, the delta score may include or be based on an actual difference between the currently measured energy consumption and the reference energy consumption level (e.g., in terms of energy / power used) and / or the currently measured QoS level metrics minus the preconfigured reference QoS level (e.g., in terms of packet throughput or latency). In some implementations, the user device returns the configuration 1779950 of 88 preferred, and the reason for this selection, for which the user team can indicate the policy used by the user team to arrive at this decision. With this information, the network can gain insights into the quality of the user team's suggestion in relation to the user team's situation, and the degree to which the user team's selection policy aligns with the network's operational preferences. As non-limiting examples, the user team may indicate (1) that the quality of service requirements are met with this configuration, indicating that compliance with quality of service is a top priority for the user team; or (2) that it operates in deep power-saving mode. The latter may be indicated if the UE has reached a low residual battery level (for example, below a threshold).This indication can also be used by the network to configure the user equipment to operate according to a more suitable alternative quality of service profile. Therefore, this information can be used by the network to develop a configuration that balances the QoS of the UE and the EE. In some implementations, the UE can provide feedback (e.g., one or more values ​​or metrics) that compares different configurations (e.g., actually applied and / or candidate) with respect to a particular traffic scenario. Some examples of comparison configurations include: • current actual user equipment configuration (measured EE) versus previous actual user equipment configuration (measured EE); • the configuration of the candidate user equipment (estimated EE) versus the current actual configuration of the user equipment (measured EE); • the configuration of the candidate user equipment (estimated EE) versus the previous actual configuration of the user equipment (measured EE); and • the configuration of candidate user equipment 1 (estimated EE) versus the configuration of candidate user equipment 2 (estimated EE). In various implementations, the values ​​and / or metrics for candidate configurations can be determined and / or estimated in any of the ways discussed previously. If the user team has received multiple configurations associated with the same or similar traffic patterns and / or use cases, the network may request the user team to report its preferred configuration. The network may also request the UE to report a ranking of the multiple configurations in terms of preference. In some forms of implementation, the EU can, based on its traffic 1779950 out of 88 experienced in a past time window, estimate the best configuration and optionally an EE metric or value for the preferred configuration. For example, the UE should have been configured with a different DRX cycle parameter given its QoS requirements and the traffic experienced. The network can identify the traffic pattern / state of the past time window and use the learnings to configure a second UE that experiences the same / similar state as the first UE, with the new optimal configuration. In some implementations, the network may include a predicted value or metric (for example, for EE, QoS, or a combination thereof) for a configuration, and the UE provides a “true” or “false” (alternatively “correct” or “incorrect”) response for the predicted value or metric. For example, a user device is configured with config-1 and config-2, which are considered a baseline or reference with a metric value of 100. The network then sends the user device config-3 with a predicted metric value of 85 and, optionally, an uncertainty range (for example, + / -5) associated with the predicted metric. The UE could label the predicted metric as true or false after evaluating the new configuration, which can be based on the uncertainty range if included.If the predicted value is labeled as “false”, the UE may optionally include some additional information, such as whether the actual score was lower or higher than the one predicted by the network. In some implementations, when the network reconfigures the UE, the UE can indicate to the network an expected relative score between the configuration currently used by the UE and a different configuration that the UE prefers for ongoing procedures affecting services executed by the UE. Alternatively, the UE can confirm the validity of the current configuration. Such a reconfiguration event can occur in any of the following cases: • when at least one service is configured, removed, or modified (e.g., 5QI) • when there is a change in the mapping between QoS flows and DRBs • when there is a change in the set of S-NSSAIs to which the services running in the UE are assigned; • in mobility, for example, intra-frequency, inter-frequency, inter-RAT, inter-system; • in roaming between PLMNs; • when moving from a public network to a private network or vice versa; and • for quality of experience (QoE) measurements, for example, a 1779950 of 88 RRC reconfiguration message enabled to start, stop, pause or resume application layer QoE measurements associated with at least one service type (e.g. MTSI, streaming, VR, AR, MBMS, etc.), In the last example, the UE's QoE measurements can be based on signaling or management, and the UE can signal the network a new preferred energy efficiency configuration. The UE can provide feedback on configurations in several ways, depending on the implementation. In some implementations, the UE provides feedback as part of the upper-layer signaling, such as RRC signaling or connection configuration. For example, the user equipment receives an initial cRDX configuration from the network as part of an RRC signaling procedure (e.g., reconfiguration) and provides its feedback as part of the same RRC signaling procedure. In other implementations, the UE receives a configuration broadcast via SI and transmits feedback via dedicated signaling (e.g., RRC). In some implementations, the UE can provide feedback as part of the lower-layer signaling, such as UCI, MAC CE, etc., transmitted via PUSCH or PUCCH. In various implementations, the specific feedback mechanism used by the UE can be configured by the network or predefined, for example, as part of the 3GPP descriptive memory. For instance, the UE can infer the specific feedback mechanism to use (e.g., RRC, UCI, MAC CE, etc.) based on the mechanism by which it received the configuration(s) to be evaluated (e.g., RRC, SI broadcast, DCI, MAC CE, etc.). Furthermore, the network can also enable or disable any particular UE feedback mechanism. In some implementations, the time-frequency resources used for UE feedback can be preconfigured (e.g., the next slot after receiving the configuration(s), etc.) or explicitly or implicitly indicated by the network. For example, the network might indicate the feedback resources along with the configuration(s) that the UE should evaluate. As illustrated in Figure 8, the user equipment can return EE and / or QoS information associated with a configuration in response to reception. 1779950 of 88 of the network configuration. In addition, the user equipment may return EE and / or QoS information associated with a configuration based on any of the following events and / or conditions: • UE / network status changes, traffic pattern changes, newly activated applications, UE DRB or SRB configuration / disconfiguration, etc. • UE transition between RRC states, in the event of a handover, in the update / change of the QoS flows served, etc.; • Change in QoS and / or EE relative to a threshold, e.g., feedback when a new configuration provided leads to an EE and / or QoS metric changing (e.g., decreasing or increasing) more than a threshold configured by the network or pre-configured compared to another configuration (see several examples of comparisons discussed above); • In the case of network-configured events, for example, the user equipment may be configured to report whenever energy consumption exceeds (or falls below) a threshold, and / or if the quality of service (e.g., performance) falls below a threshold; • Periodically or semi-statically, as configured by the network; • Change in the portion of the network used by the UE; and • Updated QoE measurement configuration. In various implementations, the network uses feedback from the UE to evaluate the best possible configuration to signal to the UE, maximizing all target parameters, such as EE and / or QoS levels. The network can perform one or more of the following actions based on the information received from the user equipment, as described below. In some implementations, the network can determine the best configuration for a UE, considering one or more of the following: • The known capabilities of the EU; • the current conditions of the UE, for example, the cell status, the radio environment, the services used by the UE, etc.; and • the known characteristics of the UE, for example, a group of model versions identifiable by the masked IMEISV parameter, defined in 3GPP TS 36.413 (v16.5.0). In some implementations, the network can determine the best 1779950 of 88 configuration that maximizes EE and other target parameters, including QoS, for a group of UEs such as all UEs served by a cell, all UEs served by one or more cells by a particular network portion, etc. For example, you can determine the best configuration that maximizes EE for a given QoS profile (e.g., 5QI) or a combination of QoS profiles (e.g., 5QIs assigned to DRBs that can be configured to the UE). In some implementations, the network may determine that none of the configurations provided to a UE achieve the desired and / or acceptable performance for the configured objectives. In this case, the network may use information received from user equipment to determine the best supported configuration, the new configuration that should be supported, and / or the configuration that would maximize overall performance once provided to user equipment and with one or more 5QIs. The network may also decide to unconfigure certain DRBs and / or SRBs if the UE does not provide a sufficiently suitable configuration for those DRBs or SRBs. Once a network node serving a cell knows the configurations that are preferred, optimal, acceptable, supported, and / or unsupported by a particular UE under certain conditions, the network node can signal this information to a management system, which in turn can provide this information to other network nodes. Alternatively, the network node can signal the information directly to network nodes serving other cells, for example, via Xn interfaces. Several features of the previously described implementations correspond to various operations illustrated in Figures 9-10, which show example methods (e.g., procedures) for a UE and a network node, respectively. In other words, several features of the operations described below correspond to various implementations described above. Furthermore, the example methods shown in Figures 9-10 can be used together to provide various benefits, advantages, and / or solutions to the problems described herein. Although Figures 9-10 show specific blocks in particular orders, the operations of the example methods can be performed in different orders and can be combined and / or divided into blocks with different functionality. Optional blocks or operations are indicated by dashed lines. In particular, Figure 9 shows an example method (for example, 1779950 of 88 procedure) for a UE configured to operate in a cell of the wireless network, according to various embodiments of this disclosure. The example method may be implemented by a UE (for example, a wireless device) as described elsewhere in this document. The example method may include operations in block 920, where the UE can receive, from a network node, one or more configurations for UE operation in the cell. The example method may also include operations in block 930, where the UE can determine one or more of the following information associated with at least the received configurations and with UE data traffic: UE energy efficiency (EE) and quality of service (QoS). The example method may also include operations in block 940, where the UE can send the determined information, or one or more indications thereof, to the network node. In some embodiments, the example method may also include operations in block 950, where the UE can receive, from the network node, an additional configuration for UE operation in the cell. In some implementations, each configuration includes settings or values ​​for one or more of the following: • DRX while the UE is operating in a state connected to the wireless network; • DRX while the UE is operating in a state not connected to the wireless network; • WUS while the UE is operating in a state not connected to the wireless network; • measurement or monitoring of the beams and / or RS transmitted by the network node; • AC, DC, and / or BWPs; • MIMO reception and / or transmission; • PDCCH monitoring; and • QoS. In some embodiments, the determination of the user equipment EE information associated with each of the configurations received in block 930 may include the operations of sub-block 931, where the user equipment can determine one of the following aspects for one of the configurations that the user equipment is using to operate in the cell: • an actual energy consumption of the user equipment based on the 1779950 of 88 measurements of the operating current during an observation period; or • an estimated energy consumption of the user equipment based on the duration of each of the operating states during the observation period, and based on a model of the energy consumption of the user equipment in each of the operating states. In some embodiments, the determination of the UE's EE information associated with each of the configurations received in block 930 may include operations in sub-block 932, where the UE can determine an estimated UE energy consumption for a configuration that is not being used by the UE based on one or more of the following: • a database that stores information about the energy consumption of at least one of the manufacturers, a model number and a chipset associated with the user equipment; • the actual energy consumption of the UE during the above operation in the configuration or in a configuration similar to the configuration; and • the estimated duration of use of the user equipment in each of the operating states and a model of the energy consumption of the user equipment in each of the operating states. In some of these embodiments, the determination of the UE's EE information associated with each of the configurations received in block 930 may also include the operations of sub-block 933, where the UE can adjust the actual or estimated energy consumption of the UE by eliminating energy consumption that is independent of one or more configurations (e.g., for the user interface, such as a display). In some implementations, each configuration may include a QoS identifier associated with one or more QoS features. In such a case, the UE determines (for example, in block 930) and sends (for example, in block 940) UE EE information only for configurations that have a QoS identifier and / or QoS features that correspond to a data radio carrier (DRB) established for the UE and / or the data traffic of one or more UE applications. In some embodiments, the specified information or one or more indications thereof sent to the network node (for example, in block 940) may include one or more of the following: • the respective absolute EE ratings for the configurations 1,779,950 out of 88 received; • an absolute EE classification for a received configuration that is being used by the UE; • the respective EE ratings of the received configurations in relation to a reference EE rating; • the respective EE differences between the received configurations and a configuration that is being used by the UE; • an EE difference between two of the received configurations; • the absolute UE energy consumption, actual or estimated, of the user equipment for the received configurations; and • the actual or estimated UE energy consumption of the user equipment for the received configurations, in relation to the reference UE energy consumption of the user equipment. In some of these embodiments, each received configuration may include a corresponding reference EE rating, which may include an estimated range of absolute EE ratings for the corresponding configuration. In such embodiments, the indications sent to the network node comprise indications of whether the actual EE ratings of the received configurations are within the respective estimated ranges of absolute EE ratings. In other forms of implementation, the reference energy consumption of The EU can be one of the following: • the actual power consumption of the user equipment when operating in a state of non-connection to the wireless network; or • the actual or estimated power consumption of the equipment when operating in a reference configuration. In some embodiments, the specified information or one or more indications thereof sent to the network node (for example, in block 940) may also include one or more of the following: • the respective absolute QoS ratings for the received configurations; • an absolute QoS rating for a received configuration that is being used by the UE; • the respective QoS differences between the received configurations and a configuration that is being used by the UE; and • a QoS difference between two of the received configurations. 1779950 of 88 In some of these implementations, the absolute EE rating and the absolute QoS rating associated with the same received configuration are represented by a combined EE / QoS rating. In some embodiments, the received configurations may include a plurality of configurations previously used by the UE for data traffic patterns corresponding to the UE's data traffic. In such embodiments, the determined information or one or more indications thereof sent to the network node includes an indication of one of the following: • a user-preferred configuration, or • a UE preference order of previously used configurations. In some embodiments, the determination of information (e.g., in block 930) is based on the user equipment data traffic during a single observation period or during each of a plurality of non-overlapping measurement periods comprising the single observation period. In some embodiments, the specified information or one or more indications thereof sent to the network node (for example, in block 940) may include an indication of a UE preferred configuration not included in the received configurations and one or more of the following: • UE EE and / or QoS information associated with the UE's preferred configuration; and • an indication of one or more criteria for selecting the UE's preferred configuration. In some of these embodiments, the configuration preferred by the UE is associated with one of the following: • change in one or more services for the UE • change in the mapping between QoS flows and DRBs for the UE • change in the mapping between network outages and services for the UE; • EU mobility operation; • user equipment roaming between PLM networks; • user equipment roaming between a PLMN and a private network; or • reconfiguration of UE QoE measurements. In other embodiments, the indication of one or more criteria indicates the prioritization of EU QoS for EU or EE data traffic due to the remaining energy in the EU battery. In some variants of these embodiments In implementation 1779950 of implementation 88, the additional configuration (e.g., received in block 950) provides either an EE boost or a QoS boost, relative to the current UE configuration, based on whether the indication specifies the UE prioritizing QoS or EE, respectively. In some cases, the additional configuration differs from the UE's preferred configuration and / or the UE's preferred configuration is not supported in the cell. In some implementations, one or more of the following apply to the additional configuration (e.g., received in block 950): includes at least one SRB or DRB not currently configured for the UE; and excludes at least one SRB or DRB currently configured for the UE. In some implementations, the one or more configurations are received (for example, in block 920) as one of the following: IF broadcast in the cell; at least one unicast or dedicated RRC message; at least one MAC CE; or at least one DCI message. In some embodiments, the specified information or one or more indications thereof are sent to the network node (for example, in block 940) as one of the following: at least one unicast or dedicated RRC message; at least one MAC CE; or at least one DCI message. In some embodiments, the specified information or one or more indications thereof are sent to the network node (for example, in block 940) in response to one or more of the following: receive the configurations (for example, in block 920); a change in EU data traffic; activation or deactivation of applications by the UE; UE switching between a connected state and a non-connected state with the wireless network; EU mobility operation; change in one or more of the following elements used by the UE: network portion, QoS flow, DRB, SRB and QoE measurement configuration; 1779950 of 88 • the actual or estimated energy consumption of the UE for a configuration used by the UE is greater than a first threshold; • The QoS of a configuration used by the UE is below a second threshold; and • a periodic or semi-static schedule configured by the network. In some implementations, the example method may also include block 910 operations, in which the user equipment can send the network node an indication of the user equipment's feedback capabilities for network-provided configurations and / or dynamic information associated with the user equipment's current conditions. Examples of these operations are shown in Figure 8 (operations 6-7). In addition, Figure 10 shows an example method (e.g., procedure) for a network node configured to service a cell in a wireless network, according to various embodiments of this disclosure. The example method can be implemented by a network node (e.g., base station, eNB, gNB, ng-eNB, etc.) as described elsewhere in this document. The example method may include operations in block 1020, where the network node can send one or more configurations for the UE's operation in the cell to a UE. The example method may also include operations in block 1040, where the network node can receive one or more of the following information from the UE, associated with at least the UE's configurations and data traffic: UE EE and QoS. The example method may also include operations in block 1060, where the network node can determine an additional configuration for the UE's operation in the cell based on the received information and one or more of the following additional information: cell configuration; statistics associated with cell operation; current traffic conditions in the cell; and the capabilities, status, and / or configuration of at least the UE. In some implementations, each configuration includes settings or values ​​for one or more of the following: • DRX while the UE is operating in a state connected to the wireless network; • DRX while the UE is operating in a state not connected to the wireless network; • WUS while the UE is operating in a state not connected to the 1779950 of 88 wireless network; • measurement or monitoring of the reference beams and / or signals transmitted by the network node; • AC, DC, and / or BWP; • MIMO reception and / or transmission; • PDCCH monitoring; and • QoS. In some embodiments, the cell configuration may include one or more of the following parameters: cell size, carrier frequency, bandwidth, multi-user input and output (MU-MIMO) capabilities. In some embodiments, the statistics associated with cell operation may be based on one or more of the following parameters: BLER, MCS, power control outer loop settings, data throughput, SINR, and traffic load. In some embodiments, the current traffic conditions in the cell are represented by one or more of the following parameters: traffic load over the most recent duration, number of UEs in a state connected to the wireless network over the most recent duration, signal quality as measured by the UEs over the most recent duration, number of mobility operations by the UEs over the most recent duration, and number and / or type of radio carriers currently set up for the UEs. In some embodiments, the capabilities, status and / or configuration of at least the UE include any of the following: UE antenna configuration, UE power source, UE manufacturer and / or model, UE chipset manufacturer and / or model, UE software version, UE class, UE performance category, and UE compatibility with one or more transmission modes used in the cell. In some embodiments, the information received (for example, in block 1040) includes one or more of the following elements: • the respective absolute EE ratings for the received configurations; • an absolute EE classification for a received configuration that is being used by the UE; • the respective EE ratings of the received configurations in relation to a reference EE rating 1779950 of 88 • the respective EE differences between the received configurations and a configuration that is being used by the UE • an EE difference between two of the received configurations • the absolute, actual or estimated energy consumption of the user equipment for the received configurations; and • the actual or estimated energy consumption of the user equipment for the received configurations, relative to the reference energy consumption of the user equipment. In some of these embodiments, each configuration may include a corresponding reference EE rating, which may include an estimated range of absolute EE ratings for the corresponding configuration. In such embodiments, the received information (for example, in block 1040) includes indications of whether the actual EE ratings of the received configurations fall within the respective estimated ranges of absolute EE ratings. In other forms of implementation, the reference energy consumption of The EU can be one of the following: • the actual power consumption of the user equipment when operating in a state of non-connection to the wireless network; or • the actual or estimated power consumption of the equipment when operating in a reference configuration. In some embodiments, the information received (for example, in block 1040) may also include one or more of the following elements: • the respective absolute QoS ratings for the received configurations; • an absolute QoS rating for a received configuration that is being used by the UE; • the respective QoS differences between the received configurations and a configuration that is being used by the UE; and • a QoS difference between two of the received configurations. In some of these implementations, the absolute EE rating and the absolute QoS rating associated with the same configuration are represented by a combined EE / QoS rating. In some embodiments, the configurations may include a plurality of configurations previously used by the UE for data traffic patterns corresponding to the UE's data traffic. In such embodiments, the 1779950 of 88 information received (for example, in block 1040) includes an indication of one of the following: a user-preferred configuration, or a UE preference order of previously used configurations. In some embodiments, the information received (for example, in block 1040) comprises one of the following: a single set of UE EE and / or QoS information associated with a single observation period, or a plurality of sets of UE EE and / or QoS information associated with a corresponding plurality of non-overlapping measurement periods comprising the single observation period. In some of these embodiments, the determination of the additional configuration for the operation of the user equipment in the cell (for example, in block 1060) may include the network node correlating the plurality of EE and / or QoS information sets of the user equipment with a corresponding plurality of sets of additional information associated with the respective measurement periods. In some embodiments, the information received (for example, in block 1040) may include an indication of a configuration preferred by the UE not included in the configurations and one or more of the following: UE EE and / or QoS information associated with the UE's preferred configuration; and an indication of one or more criteria for selecting the UE's preferred configuration. In some of these embodiments, the configuration preferred by the UE is associated with one of the following: change in one or more services for the UE; change in the mapping between QoS flows and DRBs for the UE; change in the mapping between network outages and services for the UE; EU mobility operation; user equipment roaming between PLM networks; user equipment roaming between a PLMN and a private network; or reconfiguration of UE QoE measurements. In other forms of realization, the indication of one or more criteria 1779950 of 88 indicates the UE's QoS prioritization for UE or EE data traffic due to the remaining energy in the UE's battery. In some variations of these embodiments, the additional setting is for the UE and provides either an EE boost or a QoS boost relative to the UE's current setting, depending on whether the indication specifies UE QoS or EE prioritization, respectively. In some cases, the additional setting differs from the UE's preferred setting and / or the UE's preferred setting is not supported in the cell. In some embodiments, one or more of the following apply to the additional configuration (e.g., determined in block 1060): • includes at least one SRB or DRB not currently configured for the UE; and • excludes at least one SRB or DRB currently configured for the UE. In some embodiments, the example method may also include operations in blocks 1030 and 1050. In block 1030, the network node may send one or more configurations to one or more additional UEs. In block 1050, the network node may receive from the other UEs one or more of the following additional information associated with at least the UE configurations and data traffic: the respective UE EE and the respective UE QoS. In such embodiments, determining the additional configuration for UE operation in the cell (e.g., in block 1060) may include operations in subblock 1061, where the network node may apply a reinforcement learning (RL) algorithm to the received information (e.g., in block 1040), the additional information received (e.g., in block 1050), and the additional information.In some of these implementations, the additional configuration may be for all UEs operating in the cell, all UEs served by a particular network portion, or all UEs associated with a particular QoS profile. In some implementations, the one or more configurations are sent (for example, in block 1020 and optionally in block 1050) as one of the following: • IF broadcast in the cell; • at least one unicast or dedicated RRC message; • at least one MAC CE; or • at least one DCI message. In some implementations, the information is received (for example, in block 1040) as one of the following: 1779950 of 88 at least one unicast or dedicated RRC message; at least one MAC CE; or at least one DCI message. In some implementations, the reception of information (for example, in block 1040) corresponds to one or more of the following: • sending the configurations (for example, in block 1020); • a change in EU data traffic; • activation or deactivation of applications by the UE; • UE switching between a connected state and a state not connected to the wireless network; • EU mobility operation; • change in one or more of the following elements used by the EU: network portion, QoS flow, DRB, SRB and QoE measurement configuration; • the actual or estimated energy consumption of the UE for a configuration used by the UE is greater than a first threshold; • The QoS of a configuration used by the UE is below a second threshold; and • a periodic or semi-static schedule configured by the network. In some embodiments, the example method may also include operations in block 1070, where the network node can configure one or more of the following for operation in the cell according to the specified additional configuration: the UE, and one or more additional UEs. In some embodiments, the example method may also include operations in block 1010, where the network node can receive, from the UE, one or more of the following information: • an indication of the UE's feedback capabilities for network-provided configurations; and • dynamic information associated with the current conditions of the UE. Examples of these operations are shown in Figure 8 (operations 6-7). In such a case, the one or more configurations sent to the UE (for example, in block 1020) are based on the information received. Although several forms of implementation are described above in terms of methods, techniques, and / or procedures, the person with ordinary knowledge will readily understand that such methods, techniques, and / or procedures can be 1779950 of 88 incorporated by various combinations of hardware and software in various systems, communication devices, computer devices, control devices, apparatus, non-transient computer-readable media, computer program products, etc. Figure 11 shows an example of an 1100 communication system according to some embodiments. In the example, the 1100 communication system includes a 1102 telecommunications network comprising an 1104 access network, such as a radio access network (RAN), and a 1106 core network, comprising one or more 1108 core network nodes. The 1104 access network comprises one or more access network nodes, such as 1110a and 1110b network nodes (one or more of which may be referred to generally as 1110 network nodes), or any other similar 3GPP Third Generation Partnership Project (3GPP) access node or non-3GPP access point. The 1110 network nodes facilitate the direct or indirect connection of user equipment (UE), for example, by connecting UE 1112a, 1112b, 1112c, and 1112d (one or more of which may be referred to collectively as UE 1112) to the core 1106 network via one or more wireless connections. Examples of wireless communication via a wireless connection include the transmission and / or reception of wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other physical conductors. Furthermore, in various embodiments, the 1100 communication system may include any number of wired or wireless networks, network nodes, UEs (Engineering Units), and / or any other component or system that can facilitate or participate in the communication of data and / or signals via either wired or wireless connections. The 1100 communication system may include and / or interact with any type of communication, telecommunications, data, cellular, radio network, and / or any other similar system. UE 1112s can be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with 1110 network nodes and other communication devices. Similarly, 1110 network nodes are arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 1112s and / or other network nodes or equipment in the 1102 telecommunications network to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as... 1779950 of 88 administration in the telecommunications network 1102. In the example shown, the core network 1106 connects network nodes 1110 to one or more hosts, such as host 1116. These connections can be direct or indirect, through one or more intermediary networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 1106 includes one or more core network nodes (for example, core network node 1108) that are structured with hardware and software components. The characteristics of these components may be substantially similar to those described for UEs, network nodes, and / or hosts, such that the descriptions of these are generally applicable to the corresponding components of core network node 1108.Examples of core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Unmasking Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF). Host 1116 may be owned or controlled by a service provider other than an operator or provider of the access network 1104 and / or the telecommunications network 1102 and may be operated by or on behalf of the service provider. Host 1116 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as the retrieval and compilation of data on various environmental conditions detected by multiple UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. Taken together, the 1100 communication system in Figure 11 enables connectivity between UEs, network nodes, and hosts. In this regard, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards including, but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long-Term Evolution (LTE); and / or other suitable 2G, 3G, 4G, 5G, or any future-generation standards. 1779950 of 88 applicable (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide area network (LPWAN) standard such as LoRa and Sigfox. In some examples, the 1102 telecommunications network is a cellular network that implements standardized 3GPP features. Consequently, the 1102 telecommunications network can support network slicing to provide different logical networks to different devices connected to it. For example, the 1102 telecommunications network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Mass Machine-Type Communication (mMTC) / Massive IoT services to still others. In some examples, UE 1112 devices are configured to transmit and / or receive information without direct human interaction. For example, a UE might be designed to transmit information to the 1104 access network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the 1104 access network. Additionally, a user device might be configured to operate in single- or multi-RAT or multi-standard mode. For example, a user device might operate with one or more combinations of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (ENDC). In the example, hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (for example, UE 1112c and / or 1112d) and network nodes (for example, network node 1110b). In some examples, hub 1114 may be a controller, a router, a content source and analyzer, or any of the other communication devices described herein in relation to user equipment. For example, hub 1114 may be a broadband router that provides access to the core network 1106 for UEs. As another example, hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. The commands or instructions may be received from user equipment, network nodes 1110, or 1779950 of 88 by means of executable code, a script, a process, or other instructions on the 1114 hub. As another example, the 1114 hub can be a data collector that acts as temporary storage for the UE's data and, in some implementations, can perform analysis or other data processing. In another example, the 1114 hub can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the 1114 hub can retrieve VR assets, video, audio, or other media or sensory information-related data via a network node, which the 1114 hub provides to the UE directly, after performing local processing, and / or after adding additional local content.In another example, the 1114 concentrator acts as a proxy server or orchestrator for the UEs, particularly if one or more of the UEs are low-power IoT devices. Hub 1114 can have a constant / persistent or intermittent connection with network node 1110b. Hub 1114 can also allow a different communication scheme and / or schedule between hub 1114 and the UEs (e.g., UE 1112c and / or 1112d), and between hub 1114 and the core network 1106. In other examples, hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Additionally, hub 1114 can be configured to connect to an M2M service provider via the access network 1104 and / or another UE via a direct connection. In some scenarios, UEs can establish a wireless connection with network nodes 1110 while remaining connected through hub 1114 via a wired or wireless connection.In some embodiments, the 1114 concentrator can be a dedicated concentrator, meaning a concentrator whose primary function is to route communications to / from the UEs to / from the 1110b network node. In other embodiments, the 1114 concentrator can be a non-dedicated concentrator, meaning a device capable of routing communications between user equipment and the 1110b network node, but also capable of operating as a starting and / or ending point for certain data channels. Figure 12 shows a UE 1200 according to some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), 1779950 of 88 wireless cameras, a gaming console or device, a music storage device, a playback device, a portable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop computer, laptop embedded equipment (LEE), laptop mounted equipment (LME), a smart device, customer premises wireless equipment (CPE), a vehicle mounted or embedded wireless device, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an Enhanced MTC (eMTC) UE. A user equipment (UE) can support device-to-device (D2D) communication, for example, by implementing a 3GPP standard for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, or vehicle-to-everything (V2X) communication. In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the device in question. Instead, a UE may represent a device intended to be sold to or operated by a human user, but which may not be associated, or not initially associated, with a specific human user (for example, a smart sprinkler controller).Alternatively, a UE may represent a device that is not intended for sale or operation by an end user, but which may be associated with or operated for the benefit of a user (e.g., a smart energy meter). The UE 1200 includes processing circuitry 1202 that is operationally coupled via a bus 1204 to an input / output interface 1206, a power supply 1208, memory 1210, a communication interface 1212, and / or any other component, or any combination thereof. Some user equipment may utilize all or a subset of the components shown in Figure 12. The level of integration among the components may vary from one UE to another. Furthermore, some user equipment may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The 1202 processing circuit is configured to process instructions and data and can be configured to implement any operational sequential state machine to execute instructions stored as machine-readable computer programs in memory 1210. The processing circuitry 1779950 of 88 1202 can be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs; general-purpose processors, such as a microprocessor or a digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the 1202 processing circuitry may include multiple central processing units (CPUs). In the example, the 1206 input / output interface can be configured to provide an interface to an input device, an output device, or one or more input and / or output devices. Examples of an output device include a speaker, sound card, video card, display, monitor, printer, actuator, emitter, smart card, another output device, or any combination thereof. An input device can allow a user to capture information on the UE 1200. Examples of input devices include a touchscreen or presence-sensitive display, a camera (e.g., a digital camera, digital video camera, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, and so on.The presence-sensitive display may include a capacitive or resistive touch sensor to detect user input. A sensor could be, for example, an accelerometer, gyroscope, tilt sensor, force sensor, magnetometer, optical sensor, proximity sensor, biometric sensor, etc., or any combination thereof. An output device can use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port can be used to provide both input and output functionality. In some embodiments, the power source 1208 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., a wall outlet), a photovoltaic device, or a power cell. The power source 1208 may further include power supply circuitry to deliver power from the power source 1208 itself, and / or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as a power cable. The power delivery may be, for example, to charge the power source 1208. The power supply circuitry may perform any type of 1779950 of 88 formatting, conversion or other modification of the power from the 1208 power supply so that the power is suitable for the respective UE 1200 components to which power is supplied. Memory 1210 can be, or be configured to include, memories such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, etc. For example, memory 1210 includes one or more application programs 1214, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and the corresponding data 1216. Memory 1210 can store, for use by UE 1200, any of a variety of different operating systems or combinations of operating systems. The 1210 memory can be configured to include a variety of physical disk drives, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard disk drive, a Blu-ray optical disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini-dual in-line memory module (DIMM), synchronous dynamic random-access memory (SDRAM), an external micro-DIMM SDRAM, smart card memory as a tamper-resistant module in the form of a universal integrated circuit card (UICC) that includes one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof.The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a “SIM card.” The 1210 memory can allow the UE 1200 to access instructions, application programs, and the like, stored on transient or non-transient memory media, to download or upload data. A manufactured item, such as one that uses a communication system, can be tangibly incorporated as or in the 1210 memory, which can be or comprise a device-readable storage medium. The 1202 processing circuit can be configured to communicate with an access network or other network using the 1212 communication interface. The 1212 communication interface can comprise one or more communication subsystems and 1779950 of 88 may include or be communicatively coupled to an antenna 1222. The communication interface 1212 may include one or more transceivers used for communication, such as communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1218 and / or a receiver 1220 appropriate for providing network communications (e.g., optical, electrical, frequency allocations, etc.). In addition, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software, or firmware, or alternatively be implemented separately. In the illustrated embodiment, the communication functions of the 1212 communication interface may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using the Global Positioning System (GPS) to determine a location, other similar communication functions, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronized Optical Network (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc. Regardless of the sensor type, a user device can output data captured by its sensors via its 1212 communication interface through a wireless connection to a network node. Data captured by a user device's sensors can be communicated wirelessly to a network node by another user device. The output can be periodic (e.g., every 15 minutes if reporting the detected temperature), random (e.g., to balance the reporting load from multiple sensors), triggered by an event (e.g., an alert is sent when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient). 1779950 of 88 As another example, a UE comprises an actuator, motor, or switch connected to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the states of the actuator, motor, or switch can change. For example, the UE might include a motor that adjusts the control surfaces or rotors of a drone in flight based on the received input, or a robotic arm that performs a medical procedure based on the received input. A UE, when it takes the form of an Internet of Things (IoT) device, can be a device for use in one or more application domains. These domains include, but are not limited to, wearable city technology, extended industrial applications, and healthcare. Non-limiting examples of such an IoT device are a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, or a vehicle parking control device.An electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable device for tactile augmentation or sensory enhancement, a water sprinkler, an animal or item tracking device, a sensor for monitoring a plant or animal, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device, such as a heart rate monitor or a remotely controlled surgical robot. A user equipment in the form of an IoT device includes circuitry and / or software depending on the intended application of the IoT device, in addition to other components, as described in relation to the 1200 user equipment shown in Figure 12. As another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE can be an M2M device, which in a 3GPP context might be called an MTC device. As a particular example, the UE might implement the 3GPP NB-IoT standard. In other scenarios, a UE might represent a vehicle, 1779950 of 88 such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. In practice, any number of UEs can be used together for a single use case. For example, a first UE might be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE can adjust the drone's throttle (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UEs can also include more than one of the functionalities described above. For example, a UE might include both the sensor and the actuator, and manage data communication between both the speed sensor and the actuators. Figure 13 shows a 1300 network node according to some embodiments. As used herein, a network node refers to equipment capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or other network nodes or equipment in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node B, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations can be classified according to the amount of coverage they provide (or, in other words, their transmit power level). Depending on the coverage area, they may be called femtobase stations, picobase stations, microbase stations, or macrobase stations. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) of the components of a distributed radio base station, such as centralized digital units and / or remote radio units (RRUs), sometimes called remote radio heads (RRHs). Such remote radio units may or may not be integrated with an antenna, such as an integrated antenna radio. The components of a distributed radio base station may also be referred to as nodes of a distributed antenna system (DAS). Other examples of network nodes are 5G multi-transmission point (multiTRP) access nodes, multi-standard radio equipment (MSR) such as BS MSRs, 1779950 of 88 network controllers such as Radio Network Controllers (RNCs) or Base Station Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multicell / Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Service Mobile Location Centers (E-SMLCs)), and / or Driving Minimization Tests (MDTs). The 1300 network node includes processing circuitry 1302, memory 1304, a communication interface 1306, and a power supply 1308. The 1300 network node may consist of multiple physically separate components (for example, a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios where the 1300 network node comprises multiple separate components (for example, BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique pair of NodeB and RNC may, in some cases, be considered a single, separate network node. In some embodiments, the 1300 network node may be configured to support multiple Radio Access Technologies (RATs).In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., the same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into the network node 1300, such as GSM, WCDMA, LTE, NR, Wi-Fi, Zigbee, Z-Wave, LoRaWAN, radio-frequency identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1300. The processing circuit 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide, either alone or in conjunction with other components of the 1300 network node, such as the 1304 memory, the functionality of the 1779950 of 88 network node 1300. In some embodiments, the processing circuitry 1302 includes a system-on-a-chip (SoC). In some embodiments, the processing circuitry 1302 includes one or more of the radio frequency (RF) transceiver circuits 1312 and the baseband processing circuits 1314. In some embodiments, the radio frequency (RF) transceiver circuit 1312 and the baseband processing circuit 1314 may be on separate chips (or chipsets), boards, or units, such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuits 1312 and the baseband processing circuits 1314 may be on the same chip or chipset, board, or unit. Memory 1304 may comprise any form of computer-readable volatile or non-volatile memory, including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk drive), removable storage media (e.g., a flash drive, a compact disc (CD), or a digital video disc (DVD)), and / or any other non-transient, device-readable and / or computer-executable volatile or non-volatile memory device that stores information, data, and / or instructions that can be used by the processing circuit 1302.Memory 1304 can store any suitable instruction, data, or information, including a computer program, software, or application that includes one or more of the logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuit 1302 and used by the network node 1300. Memory 1304 can be used to store any calculations performed by the processing circuit 1302 and / or any data received through the communication interface 1306. In some embodiments, the processing circuit 1302 and memory 1304 are integrated. The communication interface 1306 is used for wired or wireless signaling and / or data communication between a network node, an access network, and / or a UE. As illustrated, the communication interface 1306 comprises port(s) / terminal(s) 1316 for sending and receiving data, for example, to and from a network via a wired connection. The communication interface 1306 also includes a radio front-end circuit 1318, which may be coupled to the antenna 1310 or, in certain embodiments, form part of it. The radio front-end circuit 1318 comprises filters 1320. 1779950 of 88 and amplifiers 1322. The radio front-end circuit 1318 can be connected to the antenna 1310 and the processing circuit 1302. The radio front-end circuit can be configured to condition the signals communicated between the antenna 1310 and the processing circuit 1302. The radio front-end circuit 1318 can receive digital data that is to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1318 can convert digital data into a radio signal with the appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal can then be transmitted via antenna 1310. Similarly, when receiving data, antenna 1310 can collect radio signals which are then converted into digital data by the radio front-end circuit 1318. The digital data can then be passed to the processing circuit 1302.In other embodiments, the communication interface may comprise different components and / or different combinations of components. In some alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318; instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or part of the RF transceiver circuitry 1312 is part of the communication interface 1306. In other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown). Antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 1310 may be coupled to radio front-end circuitry 1318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In certain embodiments, antenna 1310 is separate from network node 1300 and may be connected to network node 1300 via an interface or port. Antenna 1310, communication interface 1306, and / or processing circuit 1302 may be configured to perform any receive operation and / or certain obtain operations described herein as performed by the network node. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. The 1779950 mode 88, antenna 1310, communication interface 1306, and / or processing circuit 1302 may be configured to perform any transmission operation described herein as performed by the network node. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment. Power supply 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level required by each component). Power supply 1308 may further comprise, or be coupled to, power management circuitry to supply power to the components of network node 1300 to perform the functionality described herein. For example, network node 1300 may be connected to an external power source (e.g., the electrical grid, a power outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to the power circuitry of power supply 1308.As a further example, power source 1308 may comprise a power source in the form of a battery or battery pack that is connected to, or integrated into, the power circuitry. The battery can provide backup power in the event of an external power source failure. The implementations of the 1300 network node may include additional components beyond those shown in Figure 13 to provide certain aspects of the network node's functionality, including any of the functionalities described herein and / or any functionality necessary to support the subject matter described herein. For example, the 1300 network node may include user interface equipment to allow information input to the 1300 network node and to allow information output from the 1300 network node. This may allow a user to perform diagnostics, maintenance, repair, and other administrative functions for the 1300 network node. Figure 14 is a block diagram of a 1400 host, which can be an implementation of the 1116 host in Figure 11, according to several aspects described herein. As used herein, the 1400 host can be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-deployed server, a distributed server, a virtual machine, a container, or processing resources in a server farm. The 1400 host can provide one or more 1779950 of 88 services to one or more EUs. The 1400 host includes processing circuitry 1402 that is operationally coupled via a bus 1404 to an input / output interface 1406, a network interface 1408, a power supply 1410, and memory 1412. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those described with respect to the devices in the preceding Figures, such as Figures 12 and 13, so that the descriptions of these are generally applicable to the corresponding components of the 1400 host. Memory 1412 may include one or more software programs, including one or more host application programs 1414 and data 1416, which may include user data, for example, data generated by a UE for the host 1400, or data generated by the host 1400 for a UE. Implementations of the host 1400 may use all or several subsets of the components shown. The host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (for example, Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (for example, FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (for example, phones, desktop computers, portable display systems, head-mounted display systems).Host 1414 application programs can also provide user authentication and license checks and can periodically report on the health, routing, and availability of content to a central node, such as a device at or within a core network. Consequently, the host 1400 can select and / or specify a different host for over-the-top services for a UE. Host 1414 application programs can support various protocols, such as HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), and others. Figure 15 is a block diagram illustrating a 1500 virtualization environment where functions implemented by certain embodiments can be virtualized. In this context, virtualization means creating virtual versions of appliances or devices, which may include the virtualization of hardware platforms, storage devices, and network resources. As used herein As stated in document 1779950 of 88, virtualization can be applied to any device described herein, or to its components, and refers to an implementation in which at least some of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) deployed in one or more virtual environments hosted on one or more hardware nodes, such as a hardware computing device operating as a network node, UE, core network node, or host. Furthermore, in embodiments where the virtual node does not require radio connectivity (for example, a core network node or a host), then the node may be fully virtualized. The 1502 applications (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) run in the Q400 virtualization environment to implement some of the features, functions and / or benefits of some of the embodiments disclosed herein. Hardware 1504 includes processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, an input / output interface, etc. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may be referred to collectively as VMs 1508), and / or perform any of the functions, features, and / or benefits described in connection with some embodiment described herein. The virtualization layer 1506 may present the VMs 1508 with a virtual operating platform that appears to be network hardware. The 1508 VMs comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding 1506 virtualization layer. Different ways of realizing a 1502 virtual appliance instance can be implemented on one or more of the 1508 VMs, and these implementations can be carried out in various ways. Hardware virtualization is sometimes referred to as network function virtualization (NFV). NFV can be used to consolidate many types of network equipment onto industry-standard, high-volume server hardware, physical switches, and physical storage, which may be located in data centers and on-premises. 1779950 of 88 the customer's facilities. In the context of NFV, a 1508 VM can be a software implementation of a physical machine that runs programs as if it were running on a non-virtualized physical machine. Each 1508 VM, and the portion of the 1504 hardware that runs on that VM—whether dedicated hardware and / or hardware shared by that VM with other VMs—forms a separate virtual network element. Also within the context of NFV, a virtual network function is responsible for handling specific network functions that run on one or more 1508 VMs on the 1504 hardware and corresponds to the 1502 application. Hardware 1504 can be deployed on a standalone network node with generic or specific components. Hardware 1504 can implement some functions through virtualization. Alternatively, hardware 1504 can be part of a larger hardware cluster (for example, in a data center or CPE) where many hardware nodes work together and are managed through management and orchestration (1510), which, among other things, oversees application lifecycle management (1502). In some embodiments, hardware 1504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas.The radio units can communicate directly with other hardware nodes through one or more suitable network interfaces and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, certain signaling can be provided using a 1512 control system, which can alternatively be used for communication between the hardware nodes and the radio units. Figure 16 shows a communication diagram of a host 1602 communicating through a network node 1604 with a UE 1606 via a partially wireless connection according to several embodiments. The example implementations, according to various embodiments, of the UE (such as a UE 1112a in Figure 11 and / or a UE 1200 in Figure 12), the network node (such as network node 1110a in Figure 11 and / or network node 1300 in Figure 13), and the host (such as host 1116 in Figure 11 and / or host 1400 in Figure 14) discussed in the preceding paragraphs will now be described with reference to Figure 16. Like host 1400, host 1602 implementation forms include The 1602 host, part number 1779950, contains hardware such as a communication interface, processing circuitry, and memory. It also includes software, which is stored on or accessible by the host and executable by the processing circuitry. This software includes a host application that can be used to provide a service to a remote user, such as the UE 1606, which connects via an over-the-top (OTT) connection (1650) spanning between the UE 1606 and the host 1602. In providing the service to the remote user, the host application can provide user data transmitted using the OTT connection (1650). Network node 1604 includes hardware that allows it to communicate with host 1602 and UE 1606. The connection to 1660 can be direct or pass through a core network (such as core network 1106 in Figure 11) and / or one or more intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet. The UE 1606 includes hardware and software, which is stored on or accessible by the UE 1606 and is executable by the UE's processing circuitry. The software includes a client application, such as a web browser or an operator-specific app, which can be used to provide a service to a human or non-human user through the UE 1606 with the support of the host 1602. On the host 1602, a running host application can communicate with the running client application via the OTT connection 1650, which terminates at the UE 1606 and the host 1602. When providing the service to the user, the UE's client application can receive request data from the host application and provide user data in response to the request data. The OTT connection 1650 can transfer both the request data and the user data.The user's device client application can interact with the user to generate user data that it provides to the host application via the 1650 OTT connection. OTT connection 1650 can be extended via a connection 1660 between host 1602 and network node 1604 and via a wireless connection 1670 between network node 1604 and UE 1606 to provide the connection between host 1602 and UE 1606. Connection 1660 and wireless connection 1670, through which OTT connection 1650 can be provided, have been drawn abstractly to illustrate communication between host 1602 and UE 1606 through network node 1604, without explicit reference to any intermediary devices or the precise routing of messages through these devices. As an example of data transmission via the OTT 1650 connection, in the In step 1608 of section 1779950, host 1602 provides user data, which can be done by running a host application. In some embodiments, the user data is associated with a particular human user interacting with UE 1606. In other embodiments, the user data is associated with a UE 1606 that shares data with host 1602 without explicit human interaction. In step 1610, host 1602 initiates a transmission carrying the user data to UE 1606. Host 1602 can initiate the transmission in response to a request transmitted by UE 1606. The request can be caused by human interaction with UE 1606 or by the operation of the client application running on UE 1606. The transmission can pass through network node 1604, according to the embodiments described throughout this disclosure.Accordingly, in step 1612, network node 1604 transmits to user computer 1606 the user data that was carried in the transmission initiated by host 1602, in accordance with the embodiments described throughout this disclosure. In step 1614, user computer 1606 receives the user data carried in the transmission, which can be accomplished by a client application running on user computer 1606 associated with the host application running on host computer 1602. In some examples, UE 1606 runs a client application that provides user data to host 1602. The user data may be provided in reaction to or in response to data received from host 1602. Consequently, in step 1616, user computer 1606 may provide user data, which can be done by running the client application. When providing user data, the client application may also consider user input received through an input / output interface of UE 1606. Regardless of the specific method used to provide the user data, user computer 1606 initiates, in step 1618, the transmission of the user data to host 1602 via network node 1604.In step 1620, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1604 receives user data from UE 1606 and initiates the transmission of the received user data to host 1602. In step 1622, host 1602 receives the user data carried in the transmission initiated by UE 1606. One or more of the various implementation methods improve the performance of OTT services provided to UE 1606 using the OTT connection 1650, in which the wireless connection 1670 forms the final segment. More precisely, the 1779950 of 88 learnings from these implementations allow a UE to provide information about the UE's actual power consumption, energy efficiency (EE), and / or QoS impact for one or more configurations provided by a network node. These implementations facilitate improved discovery of network configurations that will provide reduced UE power consumption for a particular QoS requirement, for all UEs that share at least some common characteristics and / or conditions (e.g., manufacturer, chipset, software, RF architecture, radio conditions, cell traffic conditions, etc.). For example, by using machine learning (ML) techniques, the network can adapt to the specific characteristics of the UEs, as well as to the different feedback metrics provided by the different UEs.In addition, teams are encouraged to provide accurate response parameters, as this helps train the ML model used to generate improved configurations for all teams that have the same characteristics or conditions. These improvements can increase the value of OTT services for end users and service providers through longer battery life for user equipment, as well as greater reliability, lower latency and / or improved quality of experience (QoE) for OTT services. In one example scenario, factory status information can be collected and analyzed by host 1602. As another example, host 1602 can process audio and video data that may have been retrieved from a UE for use in map creation. As yet another example, host 1602 can collect and analyze real-time data to help manage traffic congestion (e.g., controlling traffic lights). As another example, host 1602 can store surveillance videos uploaded by a UE. As another example, host 1602 can store or control access to multimedia content such as video, audio, VR, or AR, which it can stream, multicast, or unicast to UEs.As other examples, the 1602 host can be used for energy pricing, remote control of non-critical electrical load over time to balance power generation needs, location services, presentation services (such as compiling diagrams, etc., from data collected from remote devices), or any other data collection, retrieval, storage, analysis and / or transmission function. In some examples, a measurement procedure may be provided to monitor data rate, latency, and other factors that are improved by one or more implementations. Network functionality may also be included. 1779950 of 88 optional for reconfiguring the OTT 1650 connection between host 1602 and UE 1606 in response to variations in measurement results. The measurement procedure and / or network functionality for reconfiguring the OTT connection can be implemented in software and hardware of host 1602 and / or UE 1606. In some embodiments, sensors (not shown) can be deployed on or in association with other devices through which the OTT 1650 connection passes; the sensors can participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified above or by supplying values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguring the OTT 1650 connection can include message format, relay configuration, preferred routing, etc.The reconfiguration does not need to directly alter the operation of network node 1604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of performance, propagation times, latency, and the like, by host 1602. The measurements may be implemented by having the software transmit messages, particularly empty or "dummy" messages, using the OTT connection 1650 while monitoring propagation times, errors, etc. The foregoing only illustrates the principles of disclosure. Various modifications and alterations of the described embodiments will be evident to those skilled in the art in light of the teachings presented here. It will therefore be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures which, although not explicitly shown or described herein, incorporate the principles of disclosure and may thus fall within the spirit and scope of disclosure. Various embodiments may be used together, as well as interchangeably, as should be understood by those of ordinary knowledge of the art. The term unit, as used herein, may have a conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, solid-state and / or discrete logic devices, computer programs or instructions for carrying out the respective tasks, procedures, calculations, outputs and / or display functions, etc., such as those described herein. 1779950 of 88 All appropriate steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual appliances. Each virtual appliance may comprise a number of such functional units. These functional units may be implemented through processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, and so forth.The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols, as well as instructions for carrying out one or more of the techniques described herein. In some implementations, processing circuitry may be used to enable the respective functional unit to perform the corresponding functions according to one or more embodiments of this disclosure. As described herein, the device and / or apparatus may be represented by a semiconductor chip, a chip module, or a module (hardware) comprising such a chip or chipset; however, this does not preclude the possibility that a device or apparatus's functionality, instead of being implemented by hardware, is implemented as a software module, such as a computer program or a program of computer programs comprising executable portions of software code for execution on a processor. Furthermore, the functionality of a device or apparatus may be implemented by any combination of hardware and software. A device or apparatus may also be considered as an assembly of multiple devices and / or apparatuses, either functionally cooperating with or independently of one another.Furthermore, devices and apparatus can be deployed in a distributed manner throughout a system, provided that the functionality of the device or apparatus is maintained. Such and similar principles are considered to be known by a person skilled in the art. Unless otherwise defined, all terms (including technical and scientific terms) used in this document have the same meaning. 1779950 of 88 meaning that is commonly understood by one of the ordinary skills in the technique to which this disclosure pertains. It shall be further understood that the terms used herein are to be interpreted in a sense that is consistent with their meaning in the context of this descriptive memorandum and the relevant technique and shall not be interpreted in an idealized or overly formal sense unless expressly defined herein. Furthermore, certain terms used in this disclosure, including the descriptive report and drawings, may be used synonymously in some cases (e.g., “data” and “information”). It should be understood that, although these terms (and / or other terms that may be synonymous with each other) may be used synonymously herein, there may be instances where such terms are not intended to be used synonymously. In addition, to the extent prior art knowledge has not been explicitly incorporated by reference herein, it is explicitly incorporated in its entirety. All referenced publications are incorporated herein by reference in their entirety. The forms of implementation of the techniques and apparatus described in this document also include, but are not limited to, the following listed examples: A1. A method for a user equipment (UE) operating in a cell of the wireless network, wherein the method comprises receiving, from a network node, one or more configurations for the operation of the user equipment in the cell; Determine one or more of the following information associated with at least the received configurations and data traffic of the UE energy efficiency (EE) of the user equipment, and quality of service (QoS); and send, to the network node, the determined information or one or more indications thereof. A2. The method according to embodiment A1, wherein each configuration includes settings or values ​​for one or more of the following: Discontinuous reception (DRX) while the UE is operating in a connected state; DRX while the UE is operating in an unconnected state; activation signals (WUS) while the UE is operating in an unconnected state; measurement or monitoring of beams and / or reference signals transmitted by the network node 1779950 of 88 carrier aggregation (CA); dual connectivity (DC); bandwidth parts (BWP); multiple input / output (MIMO) reception and / or transmission; Physical downlink control channel (PDCCH) monitoring; and quality of service (QoS). A3. The method according to any of embodiments A1-A2, wherein the determination of the EE information of the user equipment associated with each of the received configurations comprises the determination of one of the following elements for one of the configurations used by the user equipment to operate in the cell: an actual energy consumption of the UE based on operating current measurements over an observation period; or an estimated energy consumption of the user equipment based on: the duration of the user equipment's operating states during the observation period, and a model of the equipment's energy consumption in each of the operating states. A4. The method according to any of embodiments A1-A3, wherein the determination of the user equipment EE information associated with each of the received configurations comprises the determination of an estimated energy consumption of the user equipment for a configuration that is not being used by the user equipment, based on one or more of the following elements: a database that stores energy consumption information from at least one of the manufacturers, a model number, and a chipset associated with the user equipment; the actual energy consumption of the equipment during the above operation in the configuration or in a configuration similar to the configuration; and the estimated duration of use of the user equipment in each of the operating states and a model of the energy consumption of the user equipment in each of the operating states. A5. The method in accordance with any of embodiments A3-A4, wherein the determination of the user equipment EE information associated with each of the received configurations further comprises adjusting the actual or estimated energy consumption of the user equipment by eliminating the consumption of 1779950 of 88 energy that is independent of one or more configurations. A6. The method in accordance with any of embodiments A1-A5, wherein each of the configurations includes a QoS identifier associated with one or more QoS features; and the UE determines and forwards UE EE information only for configurations that have a QoS identifier and / or QoS features that correspond to at least one of the following: a data radio carrier (DRB) established for the UE, and data traffic from one or more UE applications. A7. The method in accordance with any of embodiments A1-A5, wherein the specified information or one or more indications thereof sent to the network node includes one or more of the following: a respective absolute EE classification for the received configurations; an absolute EE rating for a received configuration that is being used by the UE; respective EE ratings of the received configurations in relation to a reference EE rating; the respective EE differences between the received configurations and a configuration that is being used by the UE; an EE difference between two of the received configurations; the absolute, actual or estimated energy consumption of the user equipment for the received configurations; and the actual or estimated energy consumption of the user equipment for the received configurations, in relation to the reference energy consumption of the user equipment. A8. The method according to embodiment A7, wherein each received configuration includes a corresponding reference EE classification; Each reference EE rating includes an estimated range of absolute EE ratings for the corresponding configuration; and the indications sent to the network node comprise indications of whether the actual EE ratings of the received configurations are within the respective estimated ranges of absolute EE ratings. A9. The method according to embodiment A7, wherein the reference energy consumption of the user equipment is one of the following: 1779950 of 88 the actual energy consumption of the UE when operating in an unconnected state; or the actual or estimated power consumption of the user equipment when operating in a reference configuration. A10. The method in accordance with any of embodiments A7-A9, wherein the specified information or one or more indications thereof sent to the network node also includes one or more of the following: respective absolute QoS ratings for the received configurations; an absolute QoS rating for a received configuration that is being used by the UE; the respective QoS differences between the received configurations and a configuration that is being used by the UE; and a QoS difference between two of the received configurations. A11. The method according to embodiment A10, wherein the absolute EE rating and the absolute QoS rating associated with the same received configuration are represented by a combined EE / QoS rating. A12. The method in accordance with any of embodiments A1-A5, wherein the received configurations include a plurality of configurations previously used by the UE for data traffic patterns corresponding to the UE's data traffic; and the determined information or one or more indications thereof sent to the network node include an indication of one of the following: one of the previously used configurations preferred by the UE, or a UE preference order of the previously used configurations. A13. The method according to any of embodiments A1-A12, wherein the EE and / or QoS of the UE is determined based on the UE's data traffic during a single observation period or during each of a plurality of non-overlapping measurement periods comprising the single observation period. A14. The method according to any of embodiments A1-A13, wherein the determined information or one or more indications thereof sent to the network node includes an indication of a UE-preferred configuration not included in the received configurations and one or more of the following: EE information from UE and / or QoS associated with the preferred configuration by 1779950 of 88 the EU; and an indication of one or more criteria for selecting the configuration preferred by the EU. A15. The method according to embodiment A14, wherein the user-preferred configuration is associated with one of the following elements: change in one or more services for the EU; change in the mapping between QoS flows and data radio carriers (DRB) for the UE; change in the mapping between network cuts and services for the UE; user equipment mobility operation; roaming of user equipment between public land mobile networks (PLMN); user equipment roaming between a PLMN and a private network; or reconfiguration of user equipment quality of experience (QoE) measurements. A16. The method in accordance with embodiment A14, wherein the indication of one or more criteria indicates the prioritization by the EU of one of the following: QoS for UE data traffic; or EE due to the remaining energy in the UE battery. A16a. The method according to embodiment A16, further comprising receiving, from the network node, an additional configuration for the operation of the user equipment in the cell, wherein the additional configuration provides higher EE or higher QoS, relative to the current configuration of the user equipment, based on whether the indication indicates the prioritization of the user equipment of QoS or EE, respectively. A16b. The method according to embodiment A16a, wherein one or more of the following features are applied: The additional settings are different from the user's preferred settings; and the user's preferred settings are not compatible with the cell. A16c. The method according to any of embodiments A1-A16, further comprising receiving, from the network node, an additional configuration for the operation of the user equipment in the cell, wherein one or more of the following circumstances occur: The additional configuration includes at least one radio carrier of 1779950 of 88 signaling (SRB) or a data radio carrier (DRB) not currently configured for the UE; and the additional configuration excludes at least one SRB or DRB currently configured for the UE. A17. The method in accordance with any of embodiments A1-A16, wherein one or more configurations are received as one of the following: System information (SI) disseminated in the cell; at least one unicast or dedicated Radio Resource Control (RRC) message; at least one Medium Access Control (MAC) Control Element (CE); or at least one Downlink Control Information (DCI) message. A18. The method in accordance with any of embodiments A1-A17, wherein the specified information or one or more indications thereof are sent to the network node as one of the following: at least one unicast or dedicated Radio Resource Control (RRC) message; at least one medium access control (MAC) control element (CE); or at least one downlink control information (DCI) message. A19. The method in accordance with any of embodiments A1-A18, wherein the specified information or one or more indications thereof are sent to the network node in response to one or more of the following: the reception of the configurations; a change in EU data traffic; activation or deactivation of applications by the UE; UE change between a connected state and a non-connected state; user equipment mobility operation; change in one or more of the following elements used by the user team: network portion configuration, quality of service flow, data radio carrier (DRB), signaling radio carrier (SRB), and quality of experience (QoE) measurement; the actual or estimated energy consumption of the UE for a configuration used by the UE is greater than a first threshold; the quality of service of a configuration used by the user equipment is below a second threshold; and a periodic or semi-static schedule configured by the network. A20. The method according to any of embodiments A1-A19, further comprising sending to the network node one or more of the following elements: 1779950 of 88 an indication of the UE's feedback capabilities for network-provided configurations; and dynamic information associated with the current conditions of the UE. B1. A method for a network node serving a cell in a wireless network, the method comprising: send, to a user equipment (UE), one or more configurations for the operation of the UE in the cell; Receive, from the user equipment, energy efficiency (EE) information and / or quality of service (QoS) information associated with at least the user equipment configurations and data traffic; and determine an additional configuration for the operation of the user equipment in the cell, based on the information received and one or more of the following additional information: cell configuration, statistics associated with cell operation, current traffic conditions in the cell; and capabilities, status and / or configuration of at least the user equipment. B2. The method according to embodiment B1, wherein each configuration includes settings or values ​​for one or more of the following: Discontinuous reception (DRX) while the UE is operating in a connected state; DRX while the UE is operating in an unconnected state; activation signals (WUS) while the UE is operating in an unconnected state; measurement or monitoring of the beams and / or reference signals transmitted by the network node; carrier aggregation (CA); dual connectivity (DC); bandwidth parts (BWP); multiple input / output (MIMO) reception and / or transmission; Physical downlink control channel (PDCCH) monitoring; and quality of service (QoS). B3. The method in accordance with any of the embodiments B1-B2, wherein the cell configuration includes one or more of the following parameters: cell size, carrier frequency, bandwidth, capacities 1779950 of 88 multi-user multiple input and output (MU-MIMO). B4. The method in accordance with any of the embodiments B1-B3, wherein the statistics associated with the operation of the cell are based on one or more of the following parameters: block error rate (BLER), modulation and coding scheme (MCS), power control outer loop settings, data throughput, signal-to-interference-to-noise ratio (SINR), and traffic load. B5. The method in accordance with any of embodiments B1-B4, wherein the current traffic conditions in the cell are represented by one or more of the following parameters: traffic load during the most recent duration, number of UEs in a connected state during the most recent duration, signal quality as measured by the UEs during the most recent duration, number of mobility operations by the UEs during the most recent duration, and number and / or type of radio carriers currently set up for the UEs. B6. The method in accordance with any of embodiments B1-B5, wherein the capabilities, status and / or configuration of at least the UE include any of the following: UE antenna configuration, UE power source, UE manufacturer and / or model, UE chipset manufacturer and / or model, UE software version, UE class, UE performance category, and UE support for one or more transmission modes used in the cell. B7. The method in accordance with any of embodiments B1-B6, wherein each of the configurations includes a QoS identifier associated with one or more QoS features; and UE EE information and / or QoS information is received only for configurations that have a QoS identifier and / or QoS features that correspond to at least one of the following: a data radio carrier (DRB) established for the UE, and data traffic from one or more UE applications. B8. The method in accordance with any of embodiments B1-B6, wherein the received UE EE information and / or QoS information includes one or more of the following: a respective absolute EE classification for the received configurations; an absolute EE rating for a received configuration that is being used by the UE; respective EE ratings of the received configurations in relation to a reference EE rating; 1779950 of 88 the respective EE differences between the received configurations and a configuration that is being used by the UE; an EE difference between two of the received configurations; the absolute, actual or estimated energy consumption of the user equipment for the received configurations; and the actual or estimated energy consumption of the user equipment for the received configurations, in relation to the reference energy consumption of the user equipment. B9. The method according to embodiment B8, wherein each configuration includes a corresponding reference EE classification; Each reference EE rating includes an estimated range of absolute EE ratings for the corresponding configuration; and the received UE EE information and / or QoS information includes indications of whether the actual EE ratings of the received configurations are within the respective estimated ranges of absolute EE ratings. B10. The method according to embodiment B8, wherein the reference energy consumption of the user equipment is one of the following: the actual energy consumption of the UE when operating in an unconnected state; or the actual or estimated energy consumption of the UE when operating in a reference configuration. B11. The method in accordance with any of embodiments B8-B10, wherein the received UE EE information and / or QoS information also includes one or more of the following: respective absolute QoS ratings for the received configurations; an absolute QoS rating for a received configuration that is being used by the UE; the respective QoS differences between the received configurations and a configuration that is being used by the UE; and a QoS difference between two of the received configurations. B12. The method according to embodiment B11, wherein the absolute EE rating and the absolute QoS rating associated with the same configuration are represented by a combined EE / QoS rating. B13. The method in accordance with any of embodiments B1-B6, in 1779950 of 88 where the configurations include a plurality of configurations previously used by the UE for data traffic patterns corresponding to the UE's data traffic; and the UE EE information received and / or QoS information includes an indication of one of the following: a configuration preferred by the UE from those previously used, or a preference order of the UE from the configurations previously used. B14. The method according to any of embodiments B1-B13, wherein the EE information of UE and / or QoS comprises one of the following: a single set of UE EE and / or QoS information associated with a single observation period, or a plurality of sets of UE EE and / or QoS information associated with a corresponding plurality of non-overlapping measurement periods comprising the single observation period. B14a. The method according to embodiment B14, wherein the determination of the additional configuration for the operation of the UE in the cell comprises correlating the plurality of UE EE and / or QoS information sets with a corresponding plurality of additional information sets associated with the respective observation periods. B15. The method in accordance with any of embodiments B1-B14, wherein the received UE EE information and / or QoS information includes an indication of a preferred UE configuration not included in the configurations and one or more of the following: UE EE information and / or QoS information associated with the UE's preferred configuration; and an indication of one or more criteria for selecting the user's preferred configuration. B16. The method according to embodiment B15, wherein the configuration preferred by the UE is associated with one of the following elements: change in one or more services for the EU; Change in mapping between QoS flows and data radio carriers (DRB) for the UE; change in mapping between network outages and services for the UE; user equipment mobility operation; 1779950 of 88 user equipment roaming between public land mobile networks (PLMN); user equipment roaming between a PLMN and a private network; or reconfiguration of user equipment quality of experience (QoE) measurements. B17. The method in accordance with embodiment B15, wherein the indication of one or more criteria indicates the prioritization by the EU of one of the following: QoS for UE data traffic; or EE due to the remaining energy in the UE battery. B17a. The method according to embodiment B17, wherein the additional configuration is for the UE; and the additional configuration provides either higher EE or higher QoS, relative to the current UE configuration, based on whether the indication indicates UE prioritization of QoS or EE, respectively. B17b. The method according to embodiment B17a, wherein one or more of the following are applied: The additional configuration is different from the configuration preferred by the UE; and the configuration preferred by the UE is not supported in the cell. B18. The method in accordance with any of embodiments B1-B17b, wherein the additional configuration is for the UE and one or more of the following applies: the additional configuration includes at least one signaling radio carrier (SRB) or data radio carrier (DRB) not currently configured for the UE; and the additional configuration excludes at least one SRB or DRB currently configured for the UE. B19. The method according to any of embodiments B1-B17, wherein the method further comprises: send the one or more configurations to one or more additional UEs; and receive, from the other user equipment, the EE information of the user equipment and / or the quality of service information associated with at least the configurations and with the data traffic of the user equipment; and determine the additional configuration for the operation of the UE in the cell comprises the application of a reinforcement learning (RL) algorithm to the received information, the additional information received and the additional information. B20. The method according to embodiment B19, wherein the configuration 1779950 of 88 additional is for one of the following: all UEs operating in the cell, all UEs served by a particular network portion, or all UEs associated with a particular QoS profile. B21. The method in accordance with any of embodiments B1-B20, wherein one or more configurations are submitted as one of the following: System information (SI) broadcast in the cell at least one unicast or dedicated Radio Resource Control (RRC) message or at least one Medium Access Control (MAC) Control Element (CE); or at least one Downlink Control Information (DCI) message. B22. The method in accordance with any of embodiments B1-B21, wherein the UE EE information and / or QoS information is received as one of the following: at least one unicast or dedicated Radio Resource Control (RRC) message; at least one medium access control (MAC) control element (CE); or at least one downlink control information (DCI) message. B23. The method in accordance with any of embodiments B1-B22, wherein the UE EE information and / or QoS information is received in response to one or more of the following: sending one or more configurations, a change in UE data traffic, activation or deactivation of applications by the UE, change of the UE between a connected state and a disconnected state, user equipment mobility operation; change in one or more of the following elements used by the user equipment: network portion, QoS flow, data radio carrier (DRB), signaling radio carrier (SRB), and quality of experience (QoE) measurement configuration; the actual or estimated energy consumption of the UE for a configuration used by the UE is greater than a first threshold; the quality of service of a configuration used by the user equipment is below a second threshold; and a periodic or semi-static schedule configured by the network. B24. The method according to any of embodiments B1-B22 further comprises configuring one or more additional UEs to operate in the cell of 1779950 of 88 according to the additional configuration determined. B25. The method according to embodiment B1-B23, further comprising configuring the user equipment for operation in the cell according to the additional determined configuration. B26. The method according to any of embodiments B1-B25, further comprising receiving from the UE one or more of the following information: an indication of the UE's feedback capabilities for configurations provided by the network; and dynamic information associated with the current conditions of the UE, wherein the one or more configurations sent to the UE are based on the information received. C1. A user equipment (UE) configured to operate in a cell of a wireless network, wherein the UE comprises: radio transceiver circuits configured to communicate with a network node of the wireless network; and a processing circuit operatively coupled to the radio transceiver circuit, wherein the processing circuit and the radio transceiver circuit are configured to perform operations corresponding to any of the methods of embodiments A1-A20. C2. A user equipment (UE) configured to operate in a cell of a wireless network, wherein the UE is further configured to perform operations corresponding to any of the methods of embodiments A1-A20. C3. A non-transient, computer-readable medium that stores computer-executable instructions that, when executed by the processing circuits of a user equipment (UE) configured to operate in a cell of a wireless network, configure the UE to perform operations corresponding to any of the methods in embodiments A1-A20. C4. A computer program product comprising computer-executable instructions that, when executed by the processing circuits of a user equipment (UE) configured to operate in a cell of a wireless network, configure the UE to perform operations corresponding to any of the methods of embodiments A1-A20. D1. A network node configured to service a cell in a wireless network, the network node comprises: radio network interface circuits configured to communicate with equipment 1779950 of 88 user (UE); and processing circuits operatively coupled to the radio network interface circuits, whereby the processing circuits and the radio network interface circuits are configured to perform operations corresponding to any of the methods of embodiment forms B1-B26. D2. A network node configured to service a cell in a wireless network, wherein the network node is further configured to perform operations corresponding to any of the methods of embodiments B1-B26. D3. A non-transient, computer-readable medium that stores computer-executable instructions that, when executed by the processing circuits of a network node configured to service a cell in a wireless network, configure the network node to perform operations corresponding to any of the methods in embodiments B1-B26. D4. A computer program product comprising computer-executable instructions that, when executed by the processing circuits of a network node configured to serve a cell in a wireless network, configure the network node to perform operations corresponding to any of the methods in embodiments B1-B26.

Claims

1. A method for a user device (UD) configured to operate in a cell of the wireless network, characterized in that it comprises receiving (920) from a network node of the wireless network one or more configurations for the operation of the UD in the cell; determining (930) one or more of the following information associated with at least the received configurations and with the data traffic of the UD: Energy efficiency of the UD, EE; and quality of service, QoS; and sending (940) to the network node the determined information or one or more indications thereof. 14 Claims follow