Techniques for network energy savings

Abstract

Various aspects of the present disclosure relate to techniques for network energy savings. An apparatus is configured to determine a network energy saving (NES) mode where the NES mode includes a distributed unit (DU)-specific mode or a radio unit (RU)-specific mode of a distributed architecture, determine an NES class and an NES configuration for a traffic flow associated with the NE based on the NES mode, map the traffic flow to a DU, an RU, or a combination thereof based on the NES class associated with the traffic flow, and transmit the NES configuration to the DU, the RU, or a combination thereof mapped to the traffic flow.

Description

TECHNIQUES FOR NETWORK ENERGY SAVINGSTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to techniques for network energy savings (NES).BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations (BSs), which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] In one embodiment, an apparatus may be configured to determine a NEW mode for the NE, the NES mode comprising a distributed unit (DU)-specific mode or a radio unit (RU)- specific mode of a distributed architecture, determine an NES class and an NES configuration for a traffic flow associated with the NE based on the NES mode, the NES class associated with a quality of service (QoS) class for the traffic flow, map the traffic flow to a DU, an RU, or a combination thereof based on the NES class associated with the traffic flow, and transmit the NES configuration to the DU, the RU, or the combination thereof mapped to the traffic flow.

[0005] In one embodiment, an apparatus may be configured to receive NES configuration from a DU of a distributed architecture, the NES configuration comprising a predetermined QoS class identifier (QCI) value associated with a NES class, determine a logical channel associated with the NES class, perform logical channel prioritization based on the logical channel associated with the NES class for transmitting uplink data to the DU, and transmit the uplink data on the logical channel associated with the NES class to the DU.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0007] Figure 2 illustrates an example of NES-class mapping in the central unit (CU)-DU architecture, in accordance with aspects of the present disclosure.

[0008] Figure 3 illustrates an example of a DU-specific NES configuration, in accordance with aspects of the present disclosure.

[0009] Figure 4 illustrates an example of an RU-specific NES configuration, in accordance with aspects of the present disclosure.

[0010] Figure 5 illustrates an example NES / QoS flow model, in accordance with aspects of the present disclosure.

[0011] Figure 6 illustrates an example of coordinated NES-class energy saving for multi - TRP, in accordance with aspects of the present disclosure.

[0012] Figure 7 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0013] Figure 8 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0014] Figure 9 illustrates an example of a network equipment (NE) in accordance with aspects of the present disclosure.

[0015] Figure 10 illustrates a flowchart of a method performed by a device in accordance with aspects of the present disclosure.

[0016] Figure 11 illustrates a flowchart of a method performed by a device in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0017] Wireless communication systems may consume large amounts of energy and can be expensive to maintain. Emissions and energy consumption from different elements of a telecommunication system may adversely impact climate. In telecommunications, several industry-specific factors that are rooted in countering rising network costs have shaped efficiency efforts. As mobile traffic continues to rise, combined with the rising costs of spectrum, capital investment, and ongoing radio access network (RAN) maintenance / upgrades, energy-saving measures in network operations are needed. 5G New Radio (NR) offers significant energyefficiency improvements over previous generations. However, new 5G use cases and the adoption of mm-Wave requires more resources, which may provide a more efficient network, but with higher emissions.

[0018] As discussed in 3GPP TR 38.864 (incorporated herein by reference), network energy saving is important for environmental sustainability, reducing environmental impact (e.g., greenhouse gas emissions), and for operational cost savings. As 5G is becoming pervasive across industries and geographical areas, handling more advanced services and applications requiring high data rates (e.g., XR), networks become denser, use more antennas, larger bandwidths, and more frequency bands.

[0019] Energy consumption has become a key part of operators’ operating expenses. Energy consumption may come from the RAN and in particular from the Active Antenna Unit (AAU), with data centers and fiber transport accounting for a smaller share. The power consumption of a radio access can be split into two parts: the dynamic part, which is only consumed when data transmission / reception is ongoing, and the static part, which is constantly consumed to maintain the operation of the radio access devices, even when the data transmission / reception is not ongoing.

[0020] Therefore, there is a need to examine network energy consumption models, key performance indicators (KPIs) (e.g., spectral efficiency, capacity, user perceived throughput (UPT), latency, UE power consumption, complexity, handover performance, call drop rate, initial access performance, SLA assurance related KPIs, or the like), evaluation methodologies, and network energy savings techniques in targeted deployment scenarios. More efficient operations, both dynamic and semi-static, and finer granularity adaptation of transmissions and / or receptions in one or more network energy saving techniques in time, frequency, spatial, and power domains, with potential support / feedback from UE, potential UE assistance information, and information exchange / coordination over network interfaces are needed.

[0021] In one embodiment, one technique to improve network energy savings is in the time domain e.g., cell discontinuous transmission (DTX)Zdiscontinuous reception (DRX). In one embodiment, Cell DTX / DRX is applied to UEs in RRC CONNECTED state. A periodic Cell DTX / DRX (i.e., active and non-active periods) can be configured by a gNB via UE-specific RRC signaling per serving cell. Cell DTX / DRX can also be configured and operated together. At least the following parameters can be configured per Cell DTX / DRX configuration: periodicity, start slot / offset, on duration.

[0022] In one embodiment, UE behavior is examined when the cell activates a single DTX / DRX configuration. It is up to the network to determine whether legacy UEs in Idle mode can access cells with Cell DTX / DRX and the network should allow NES-capable UEs to camp on the NES cell. The Cell DTX / DRX mode can be activated / deactivated via dynamic L1 / L2 signaling and UE-specific RRC signaling. Both UE-specific and common L1 / L2 signaling can be considered for activating / deactivating the Cell DTX / DRX mode.

[0023] In one embodiment, a motivation behind standardizing NES capability is to improve the energy savings but also to serve users without compromising performance. The diverse use cases from industry verticals lead to different traffic models and service QoS. It is important to conserve maximum network energy while fulfilling the stringent QoS requirements of these diverse service categories. Additionally, the traffic pattern can change with the type of use case or network scenario. Therefore, a tradeoff in energy savings and the demanded KPIs is likely to occur, for e.g., a cell benefiting from maximum energy saving cannot satisfy latency-critical service requirements of sub-millisecond end-to-end latency for multiple UEs. Such degradation in QoS is intolerable for use cases like augmented reality (AR) or virtual reality (VR), haptic feedback, autonomous vehicles, mission-critical communications, mobile robots, or the like. Hence, an adaptive and robust NES mechanism is needed to attain an optimal balance.

[0024] Conventional solutions focus more on how to satisfy user experience and try to achieve energy efficiency within the network at the same time. Thus, the requirements, use cases and solutions are essentially within the network itself. Verticals and customers have no approach for energy efficiency related information from the network.

[0025] Moreover, conventionally, network energy savings solutions do not integrate QoS awareness in the gNB central unit (CU)-distributed unit (DU) architecture. The network configures the NES mode independent of any QoS-relevant or energy saving inputs from other entities such as the customers, operators, or verticals. Additionally, the QoS flow and radio bearer configuration is performed with no consideration of the energy saving solution configured in a cell. This can lead to either user performance degradation and thus service interruption or inefficient energy saving solutions.

[0026] The solutions disclosed herein are directed to techniques to mitigate the tradeoff in energy savings and user performance by incorporating QoS awareness in energy saving mode. This disclosure introduces a means of energy saving considering the requirements of the customers, operators, or verticals. It enables the network to determine the radio resource configuration based on the required energy saving and QoS, and further, provides a solution for admission control considering the network energy saving requirements and the NES mode configured in the cell.

[0027] In particular, the solutions disclosed herein are directed to a model to fulfill energy saving requirements with a performance guarantee in the gNB CU-DU architecture.Conventionally, the network configures the NES mode independent of any QoS-relevant or energy saving inputs from other entities such as the users, operators, or verticals. Further, the entities in CU-DU architecture are controlled completely by the central unit without any distributed energy saving alternative. In this solution, the CU-DU architecture is exploited for catering to diverse energy saving requirements simultaneously based on the energy saving solution configured per RAN entity (e.g., DU or radio unit (RU)). Consequently, a better negotiation can be achieved while fulfilling service requirements and saving the maximum possible energy.

[0028] The proposed solution extends the legacy QoS framework in the CU-DU architecture with energy saving awareness, which enhances the robustness, efficiency, reliability, and power consumption of UEs. Without the solutions proposed herein, the UE might experience radio link failures or performance degradation without QoS awareness in energy saving solutions. In oneembodiment, the network determines the NES configuration using cell load, traffic patterns, or the like. Conventional solutions do not promote energy saving relevant configurations at the DU or RU level while maintaining the diverse QoS requirements of services. The extensions proposed in this disclosure derive a robust solution and complement the legacy QoS / NES behavior in a CU-DU type of architecture.

[0029] Aspects of the present disclosure are described in the context of a wireless communications system.

[0030] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G- A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0031] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a nextgeneration NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0032] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, anNE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0033] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Intemet-of-Things (loT) device, an Intemet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0034] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0035] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmit-receive points (TRPs).

[0036] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolvedpacket core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P- GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0037] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0038] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0039] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., jU=O) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., jU=O) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., jU=I) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclicprefix. A third numerology (e.g., ^=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., ju=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., ^=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0040] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0041] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., jU=O, jU=I, ,11=2. ^=3. ^=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., ^=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0042] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz -114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0043] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., ^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., ^=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., jU=3), which includes 120 kHz subcarrier spacing.

[0044] In one embodiment, aNES-class is created to mitigate the challenge arising from the tradeoff in energy savings and demanding KPIs. The NES-class is defined as the identifier of the amount of energy saving / consumption and incorporates QoS awareness in energy saving solutions. The NES-class may be mapped to an NES profile that may contain a NES configuration, a QoS profile, or a combination thereof. The NES-class may be provided by the network entity or by an operation and maintenance process using service level agreements (SLAs) or generated by the gNB according to certain rules. Admission control may be performed based on the supported NES-class that also includes negotiation procedures.

[0045] A NES profile may include a NES configuration e.g., the radio resource configuration and an energy cost metric used to represent energy saving / consumption. The NES configuration, in one embodiment, is the radio resource configuration required to support a certain NES-class. For example, the following parameters can be configured per Cell DTX / DRX configuration - periodicity, start slot / offset, and on-duration.

[0046] A QoS profile, in one embodiment, represents a list of supported QoS class identifier (QCI) values for the respective NES-class. Alternatively, a single QCI may be associated with the NES-class, e.g., the highest attainable QoS for the respective NES-class.

[0047] One NES-class may be associated with one or more QCI values. One NES-class may be mapped to one or more radio resource configurations (e.g., one or more NES configurations).The NES-class definition may be extended with additional factors if they become relevant to the NES features.

[0048] In one embodiment, the NES-relevant configuration is attached to the NES-class and its respective guaranteed QoS is indicated by the list of supported QCIs. An example implementation is illustrated in Table 1. One or more NES techniques may be configured and activated by the network at the same time. Thus, the corresponding NES configuration in the NES profile may provide the NES-relevant features that are supported. The guaranteed QCIs may be provided by the QoS profile of the NES-class.

[0049] Table 1 shows an example definition of a NES-class and describes a list of NES- classes that are either pre-defined or configured dynamically. The NES-class definition can be extended with additional factors if they become relevant to the NES features.Mapping of NES class to QCI

[0050] Figure 2 illustrates an example of NES-class mapping in the CU-DU architecture, in accordance with aspects of the present disclosure. In a first embodiment, related to NES-class mapping in the CU-DU architecture, the CU 202 maps the QoS / NES flows 204 to the respective DU 206 based on the NES-class 208 associated with the QoS / NES flow 204. The DUs 206 areconfigured individually, which reflects different modes of energy savings. Each RU 210 may be configured with a specific sleep pattem / energy saving mode. This enables different QoS / NES flows 204 to be served efficiently via different DU / RU modules.

[0051] Figure 3 illustrates an example of DU-specific NES configuration, in accordance with aspects of the present disclosure. In one embodiment, for DU-specific NES configuration, energy saving mode can be configured per DU 302. For example, a DU-specific DTX / DRX is configured that entails a specific sleep and active pattern to accommodate the diverse traffic and QoS demands. The CU 304 may guarantee a “global” NES-class 306 with a cooperative DU mechanism while each DU 302 provides a certain QCI 308. The QoS flows are directed by the CU 304 to the respective DU 302 depending on the DU-specific NES configuration catering to a certain QCI level 308. The overall NES-class is guaranteed and maintained by the CU 304. The active time of the DUs 302 determines the energy consumption. Considering the cell load, one or more DUs 302 can be put to sleep and the services can be maintained by appropriate traffic steering between the DUs 302. For example, different DUs 302 such as DU-1, DU-2, and DU-3 connected to one CU 304, may be capable of supporting QCIs 308 such as QCI-x, QCI-y, and QCI-z, respectively.

[0052] Figure 4 illustrates an example of RU -specific NES configuration, in accordance with aspects of the present disclosure. In one embodiment, for RU-specific NES configuration, energy saving mode can be configured at the RU level. For example, each RU 402 of a DU 404 is configured with individual NES configuration such as DTX / DRX sleep pattern or antenna configuration. Thus, each DU 404 may support individual NES-class 406 with respect to different NES / QoS flows. Different SLAs may be guaranteed by the CU 408, as an effect of the individual DU-specific NES-class assurance. Unlike the DU-specific NES, in this case, the granularity of configuring energy saving methods is tuned to the RU-level. Therefore, the DU 404 to which one or more RUs 402 are connected can support individual NES-class 406 on itself. The DU 404 can control and monitor the energy saving performance of its different RUs 402 and the diverse NES configurations assigned to RUs 402. In one implementation, the NES-class 406 is provisioned catering to the operator’s requirements, whereas in another implementation, the requirement of a NES-class 406 arises from user-specific or service-specific QoS demands.

[0053] In one embodiment, at the NAS level (e.g., according to TS 23.501, incorporated herein by reference), the QoS flow is the finest granularity of QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over NG-U. For each UE, one or more PDU sessions are established. TheNG-RAN maps packets belonging to different PDU sessions to different data radio bearers (DRBs). NAS level packet fdters in the UE and in the 5GC associate uplink (UL) and downlink (DL) packets with QoS Flows. Access Stratum (AS) level mapping rules in the UE and in the NG-RAN associate UL and DL QoS Flows with DRBs.

[0054] NG-RAN and 5GC ensure QoS (e.g., reliability and target delay) by mapping packets to appropriate QoS Flows and DRBs. Thus, there is a two-step mapping of IP -flows to QoS flows (NAS) and from QoS flows to DRBs (AS).

[0055] In one embodiment, at NAS level, a QoS flow is characterized by a QoS profde provided by 5GC to NG-RAN and QoS rule(s) provided by 5GC to the UE. The QoS profde is used by NG-RAN to determine the treatment on the radio interface while the QoS rules dictates the mapping between uplink User Plane traffic and QoS flows to the UE. A QoS flow may either be guaranteed bit rate (GBR) or Non-GBR depending on its profile.

[0056] In one embodiment, at AS level, the DRB defines the packet treatment on the radio interface (Uu). A DRB serves packets with the same packet forwarding treatment. The QoS flow to DRB mapping by NG-RAN is based on QFI and the associated QoS profiles (e.g., QoS parameters and QoS characteristics). Separate DRBs may be established for QoS flows requiring different packet forwarding treatment, or several QoS Flows belonging to the same PDU session can be multiplexed in the same DRB.

[0057] In the uplink, the mapping of QoS Flows to DRBs is controlled by mapping rules that are signaled in two different ways, Reflective mapping and Explicit configuration. For each PDU session, a default DRB may be configured. If an incoming UL packet matches neither an RRC configured nor a reflective mapping rule, the UE then maps that packet to the default DRB of the PDU session.

[0058] Figure 5 illustrates an example NES / QoS flow model, in accordance with aspects of the present disclosure. In one embodiment, NG-RAN (gNB CU 502) and 5GC (UPF 504) ensure quality of service by mapping data packets to appropriate QoS / NES Flows 506 and DRBs 508. NES-class 510 is incorporated in the two-step mapping of IP-flows to QoS flows 506 (NAS) and from QoS flows 506 to DRBs 508 (AS). The QoS profile and the NES-class 510 are used by NG- RAN to determine the treatment on the radio interface while the NES / QoS rules dictate the mapping between uplink User Plane traffic and NES / QoS flows 506 to the UE 512. NES-class 510 is a criterion for mapping the data to DRBs 508 for guaranteeing certain energy saving.

[0059] In one embodiment, DRBs 508 are created between the gNB CU 502 and the UE 512 to carry data via QoS / NES flows 506. In downlink, the CU 502 is responsible for the QoS flow 506 to DRB 508 mapping. DRBs 508 are configured using RRC configuration. Multiple QoS flows 506 within one DRB 508 are carried via Fl general packet radio service (GPRS) tunnel 514 (one tunnel per DRB 508). The tunnel allocation is performed by the CU 502 and sent to the DU 514 in downlink whereas the DU 514 performs the tunnel allocation in UL which is sent to the CU 502.

[0060] A logical tunnel, e.g., an NES tunnel, is a container of DRBs 508 with a single NES- class 510 as a lower bound. One or more DRBs 508 can belong to one NES tunnel 514. For example, DRB1 and DRB2 are associated with a single NES-class 1 tunnel. As the CU (gNB CU 502) contains the knowledge of NES-class 510, it is responsible for associating the appropriate DRBs 508 to a certain NES tunnel 514 such that a minimum energy saving can be guaranteed when data is transmitted via any of the DRBs 508. The information regarding NES tunnel 514 to DRB 508 mapping is provided using RRC configuration similar to priority for logical channels.

[0061] Regarding the behavior of the UE, in one embodiment, in uplink, there are two steps of mapping the uplink data to data radio bearers. In the first step, the uplink data is mapped to an appropriate NES tunnel to ensure a minimum energy saving. In the second step, the data is mapped to one of the appropriate DRB belonging to the selected NES tunnel.

[0062] In one embodiment, the UE receives different QCIs from different DUs configured with different energy saving profiles when DU-specific NES is configured. When NES mode is configured to be RU-specific, the UE receives different QCIs from different RUs configured with different energy saving profiles. The UE receives the mapping information of the NES / QCI class to the logical channels. Based on the mapping information, in uplink, the UE performs logical channel prioritization to transmit uplink data to the gNB considering the QCI guaranteed by each DU / RU.

[0063] In one embodiment, RRC controls the scheduling of uplink data by signaling, for each logical channel, priority where an increasing priority value indicates a lower priority level, prioritisedBitRate that sets the Prioritized Bit Rate (PBR), bucketSizeDuration that sets the Bucket Size Duration (BSD), and optionally allowedTTI-Lengths that sets the allowed transmission time interval (TTI) lengths. The priority of different logical channels is derived by considering the NES-class guaranteed by the DU / RU. Mapping of UL packets to NES / QoS flowstakes place based on the preconfigured NES-class to logical channels mapping information received from DU / RU.

[0064] In one embodiment, directed to feedback monitoring or energy consumption measure (DU to CU), the consumed energy measure can be reported by all the distributed units to the central unit and from the RU to the DU. This is used by the CU to evaluate the energy performance and associate the QoS / NES flows. In one embodiment, NES measurements may be monitored at the CU based on the feedback received from the DUs. Additionally, the energy saving can also be monitored directly at the DU when NES is configured to be RU-specific.

[0065] Figure 6 illustrates an example of coordinated NES-class energy saving for multi- TRP, in accordance with aspects of the present disclosure. In one embodiment directed to coordinated NES-class energy saving (for multi-TRP), the NES-class can be implemented in a multi-TRP scenario similar to the split architecture. Depending on the selected / provisioned NES- class, energy saving target is indicated to the DU with CU as the controller. Different TRPs 602 may be configured with individual configurations such as longer sleep cycles for some TRPs 602 and shorter sleep cycles for others. Hence, the users and traffic is distributed among the TRPs 602 as the network energy saving of the TRPs 602.

[0066] In one embodiment, the UE receives different QCIs from different TRPs configured with different energy saving profiles. Mapping ofNES / QCI class to the quasi-colocation (QCL- D) containing transmit spatial filter (e.g., DL beam) is performed. The transmission can be directed on the respective downlink beam for a guaranteed QCI. The UE receives the NES / QCI to the QCL-D mapping information. This NES-class to QCL-D mapping is used for scheduling the transmissions in the uplink. The NES / QCI classes are restricted and mapped to the corresponding radio bearer with respect to the UL beam and thus transmission to certain UL TRPs. If multiple UL beams toward a single TRP are available, UL data can be scheduled as per the QCI guaranteed by each beam.

[0067] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0068] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0069] The UE 700 may be configured to support a means to receive aNES configuration from a DU of a distributed architecture, the NES configuration comprising a predetermined QCI value associated with a NES class, determine a logical channel associated with the NES class, perform logical channel prioritization based on the logical channel associated with the NES class for transmitting uplink data to the DU, and transmit the uplink data on the logical channel associated with the NES class to the DU.

[0070] In one embodiment, the UE 700 may be configured to support a means to map the uplink data to the logical channel associated with the NES class and map the uplink data to a DRB associated with the logical channel. In one embodiment, the UE 700 may be configured to support a means to transmit the uplink data on a beam of a TRP associated with the NES class according to QCI to QCL-D mapping information.

[0071] The processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.

[0072] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0073] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein.

[0074] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0075] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0076] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0077] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0078] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0079] The processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 800) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0080] The controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0081] The controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein. The controller 802 may be configured to track memory address of instructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 802 may beconfigured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 802 may be configured to manage flow of data within the processor 800. The controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.

[0082] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).

[0083] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein. The code may be stored in a non-transitory computer- readable medium such as system memory or another type of memory. The controller 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0084] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800). In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800). One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 806 may supportlogical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

[0085] The processor 800 may support wireless communication in accordance with examples as disclosed herein. In one embodiment, the processor 800 may be configured to or operable to support a means to determine a NES mode for the NE, the NES mode comprising a DU-specific mode or an RU-specific mode of a distributed architecture, determine an NES class and an NES configuration for a traffic flow associated with the NE based on the NES mode, the NES class associated with a QoS class for the traffic flow, map the traffic flow to a DU, an RU, or a combination thereof based on the NES class associated with the traffic flow, and transmit the NES configuration to the DU, the RU, or the combination thereof mapped to the traffic flow.

[0086] In one embodiment, the processor 800 may be configured to support a means to direct the traffic flow to the DU based on the NES configuration for the DU. In one embodiment, the NES configuration configures the DU, the RU, or the combination thereof for a predetermined QCI value based on the NES class. In one embodiment, the processor 800 may be configured to support a means to map the NES class to the NES configuration and the predetermined QCI.

[0087] In one embodiment, the traffic flow comprises a QoS flow, an NES flow, or a combination thereof. In one embodiment, the processor 800 may be configured to support a means to map the traffic flow to one or more DRBs, the one or more DRBs associated with the NES class.

[0088] In one embodiment, the processor 800 may be configured to support a means to allocate the traffic flow to a logical NES channel, the logical NES channel comprising the one or more DRBs associated with the NES class. In one embodiment, the processor 800 may be configured to support a means to transmit information for the logical NES channel to the DU, the RU, or the combination thereof.

[0089] In one embodiment, the processor 800 comprises a CU of the distributed architecture. In one embodiment, the traffic flow is associated with a TRP, wherein the processor 800 may be configured to support a means to transmit the NES configuration to the TRP according to the NES class and the traffic flow.

[0090] In one embodiment, the processor 800 may be configured to support a means to receive a NES configuration from a DU of a distributed architecture, the NES configuration comprising a predetermined QCI value associated with a NES class, determine a logical channelassociated with the NES class, perform logical channel prioritization based on the logical channel associated with the NES class for transmitting uplink data to the DU, and transmit the uplink data on the logical channel associated with the NES class to the DU.

[0091] In one embodiment, the processor 800 may be configured to support a means to map the uplink data to the logical channel associated with the NES class and map the uplink data to a DRB associated with the logical channel. In one embodiment, the processor 800 may be configured to support a means to transmit the uplink data on a beam of a TRP associated with the NES class according to QCI to QCL-D mapping information.

[0092] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0093] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0094] The NE 900 may be configured to support a means to determine a NES mode for the NE, the NES mode comprising a DU-specific mode or an RU-specific mode of a distributed architecture, determine an NES class and an NES configuration for a traffic flow associated with the NE based on the NES mode, the NES class associated with a QoS class for the traffic flow, map the traffic flow to a DU, an RU, or a combination thereof based on the NES class associated with the traffic flow, and transmit the NES configuration to the DU, the RU, or the combination thereof mapped to the traffic flow.

[0095] In one embodiment, the NE 900 may be configured to support a means to direct the traffic flow to the DU based on the NES configuration for the DU. In one embodiment, the NES configuration configures the DU, the RU, or the combination thereof for a predetermined QCIvalue based on the NES class. In one embodiment, the NE 900 may be configured to support a means to map the NES class to the NES configuration and the predetermined QCI.

[0096] In one embodiment, the traffic flow comprises a QoS flow, an NES flow, or a combination thereof. In one embodiment, the NE 900 may be configured to support a means to map the traffic flow to one or more DRBs, the one or more DRBs associated with the NES class.

[0097] In one embodiment, the NE 900 may be configured to support a means to allocate the traffic flow to a logical NES channel, the logical NES channel comprising the one or more DRBs associated with the NES class. In one embodiment, the NE 900 may be configured to support a means to transmit information for the logical NES channel to the DU, the RU, or the combination thereof.

[0098] In one embodiment, the NE 900 comprises a CU of the distributed architecture. In one embodiment, the traffic flow is associated with a TRP, wherein the NE 900 may be configured to support a means to transmit the NES configuration to the TRP according to the NES class and the traffic flow.

[0099] The processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.

[0100] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 causes the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0101] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904).For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein.

[0102] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripherals not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0103] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

[0104] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 910 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0105] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0106] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by an NE as described herein. Insome implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0107] At 1002, the method may determine a NES mode for the NE, the NES mode comprising a DU-specific mode or an RU-specific mode of a distributed architecture. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by the NE as described with reference to Figure 9.

[0108] At 1004, the method may determine an NES class and an NES configuration for a traffic flow associated with the NE based on the NES mode, the NES class associated with a QoS class for the traffic flow. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by the NE as described with reference to Figure 9.

[0109] At 1006, the method may map the traffic flow to a DU, an RU, or a combination thereof based on the NES class associated with the traffic flow. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed by the NE as described with reference to Figure 9.

[0110] At 1008, the method may transmit the NES configuration to the DU, the RU, or the combination thereof mapped to the traffic flow. The operations of 1008 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1008 may be performed by the NE as described with reference to Figure 9.

[0111] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0112] Figure 11 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0113] At 1102, the method may receive a NES configuration from a DU of a distributed architecture, the NES configuration comprising a predetermined QCI value associated with a NES class. The operations of 1102 may be performed in accordance with examples as describedherein. In some implementations, aspects of the operations of 1102 may be performed by a UE as described with reference to Figure 7.

[0114] At 1104, the method may determine a logical channel associated with the NES class. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a UE as described with reference to Figure 7.

[0115] At 1106, the method may perform logical channel prioritization based on the logical channel associated with the NES class for transmitting uplink data to the DU. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed by a UE as described with reference to Figure 7.

[0116] At 1108, the method may transmit the uplink data on the logical channel associated with the NES class to the DU. The operations of 1108 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1108 may be performed by a UE as described with reference to Figure 7.

[0117] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0118] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A network equipment (NE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the NE to: determine a network energy saving (NES) mode for the NE, the NES mode comprising a distributed unit (DU)-specific mode or a radio unit (RU)-specific mode of a distributed architecture; determine an NES class and an NES configuration for a traffic flow associated with the NE based on the NES mode, the NES class associated with a quality of service (QoS) class for the traffic flow; map the traffic flow to a DU, an RU, or a combination thereof based on the NES class associated with the traffic flow; and transmit the NES configuration to the DU, the RU, or a combination thereof mapped to the traffic flow.

2. The NE of claim 1, wherein the at least one processor is configured to cause the NE to direct the traffic flow to the DU based on the NES configuration for the DU.

3. The NE of claim 1, wherein the NES configuration configures the DU, the RU, or a combination thereof for a predetermined QoS class identifier (QCI) value based on the NES class.

4. The NE of claim 3, wherein the at least one processor is configured to cause the NE to map the NES class to the NES configuration and the predetermined QCI.

5. The NE of claim 1, wherein the traffic flow comprises a QoS flow, an NES flow, or a combination thereof.

6. The NE of claim 1, wherein the at least one processor is configured to cause the NE to map the traffic flow to one or more data radio bearers (DRBs), the one or more DRBs associated with the NES class.

7. The NE of claim 6. wherein the at least one processor is configured to cause the NE to allocate the traffic flow to a logical NES channel, the logical NES channel comprising the one or more DRBs associated with the NES class.

8. The NE of claim 7, wherein the at least one processor is configured to cause the NE to transmit information for the logical NES channel to the DU, the RU, or a combination thereof.

9. The NE of claim 1, wherein the NE comprises a central unit (CU) of the distributed architecture.

10. The NE of claim 1, wherein the traffic flow is associated with a transmit-receive point (TRP), the at least one processor configured to cause the NE to transmit the NES configuration to the TRP according to the NES class and the traffic flow.

11. A method performed by a network equipment (NE), the method comprising: determining a network energy saving (NES) mode for the NE, the NES mode comprising a distributed unit (DU)-specific mode or a radio unit (RU)- specific mode of a distributed architecture; determining an NES class and an NES configuration for a traffic flow associated with the NE based on the NES mode, the NES class associated with a quality of service (QoS) class for the traffic flow; mapping the traffic flow to a DU, an RU, or a combination thereof based on the NES class associated with the traffic flow; and transmitting the NES configuration to the DU, the RU, or a combination thereof mapped to the traffic flow.

12. The method of claim 11, further comprising directing the traffic flow to the DU based on the NES configuration for the DU.

13. The method of claim 11, wherein the NES configuration configures the DU, the RU, or a combination thereof for a predetermined QoS class identifier (QCI) value based on the NES class.

14. The method of claim 13, further comprising mapping the NES class to the NES configuration and the predetermined QCE15. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a network energy saving (NES) configuration from a distributed unit (DU) of a distributed architecture, the NES configuration comprising a predetermined quality of service (QoS) class identifier (QCI) value associated with a NES class; determine a logical channel associated with the NES class; perform logical channel prioritization based on the logical channel associated with the NES class for transmitting uplink data to the DU; and transmit the uplink data on the logical channel associated with the NES class to the DU.

16. The UE of claim 15, wherein the at least one processor is configured to cause the UE to map the uplink data to the logical channel associated with the NES class and map the uplink data to a data radio bearer (DRB) associated with the logical channel.

17. The UE of claim 15, wherein the at least one processor is configured to cause the UE to transmit the uplink data on a beam of a transmit-receive point (TRP) associated with the NES class according to QCI to quasi-colocation (QCL-D) mapping information.

18. A method performed by a user equipment (UE), the method comprising : receiving a network energy saving (NES) configuration from a distributed unit (DU) of a distributed architecture, the NES configuration comprising a predetermined quality of service (QoS) class identifier (QCI) value associated with a NES class; determining a logical channel associated with the NES class; performing logical channel prioritization based on the logical channel associated with the NES class for transmitting uplink data to the DU; and transmitting the uplink data on the logical channel associated with the NES class to the DU.

19. The method of claim 18, further comprising mapping the uplink data to the logical channel associated with the NES class and mapping the uplink data to a data radio bearer (DRB) associated with the logical channel.

20. The method of claim 18, further comprising transmitting the uplink data on a beam of a transmit-receive point (TRP) associated with the NES class according to QCI to quasicolocation (QCL-D) mapping information.

Images