Technologies for network energy saving
By introducing QoS-aware NES category mapping and configuration into the CU-DU architecture, radio resources are dynamically adjusted, solving the high energy consumption problem of wireless communication systems. This achieves maximum energy saving while meeting QoS requirements, thereby improving network robustness and efficiency.
Patent Information
- Application Number
- CN202580026433.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-12
- Filing Date
- 2025-03-21
- Publication Date
- 2026-11-17
AI Technical Summary
Wireless communication systems consume a lot of energy, and conventional energy-saving solutions fail to effectively meet QoS requirements, resulting in network performance degradation or inefficient energy saving.
By introducing QoS-aware NES category mapping and configuration into the CU-DU architecture, radio resources can be dynamically adjusted to achieve network energy saving while meeting the QoS requirements of different services.
It achieves maximum energy saving while meeting QoS requirements, improves network robustness and efficiency, and avoids radio link failures and performance degradation.
Smart Images

Figure CN123125940A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to wireless communications, and more specifically, to technologies for network power saving (NES). Background Technology
[0002] A wireless communication system may include one or more network communication devices, such as base stations (BS), which can support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system can support wireless communication across a variety of radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)). Summary of the Invention
[0003] The article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, the word “or,” as used in the claims, or in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, without departing from the scope of this disclosure, an example step described as “based on condition A” may be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, the word “group” may comprise one or more elements.
[0004] In one embodiment, a device may be configured to: determine a NEW mode for an NE, the NES mode including a distributed unit (DU) specific mode or a radio unit (RU) specific mode of a distributed architecture; determine an NES category and NES configuration for a service flow associated with the NE based on the NES mode, the NES category being associated with a Quality of Service (QoS) category for the service flow; map the service flow to a DU, RU, or a combination thereof based on the NES category associated with the service flow; and transmit the NES configuration to the DU, RU, or combination thereof mapped to the service flow.
[0005] In one embodiment, a device may be configured to: receive NES configuration from a DU of a distributed architecture, the NES configuration including a predetermined QoS Class Identifier (QCI) value associated with an 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 to the DU on the logical channel associated with the NES class. Attached Figure Description
[0006] Figure 1 Examples of wireless communication systems according to aspects of this disclosure are described.
[0007] Figure 2 This describes an instance of NES category mapping in the Central Unit (CU)-DU architecture according to aspects of this disclosure.
[0008] Figure 3 This describes an instance of a DU-specific NES configuration based on aspects of this disclosure.
[0009] Figure 4 This describes an instance of a RU-specific NES configuration based on aspects of this disclosure.
[0010] Figure 5 This describes an example of an NES / QoS flow model based on aspects of this disclosure.
[0011] Figure 6 This describes an example of coordinated NES category energy saving using multiple TRPs according to aspects of this disclosure.
[0012] Figure 7 Examples of UEs based on aspects of this disclosure are described.
[0013] Figure 8 Examples of processors according to aspects of this disclosure are described.
[0014] Figure 9 Examples of network equipment (NE) according to aspects of this disclosure are described.
[0015] Figure 10 A flowchart illustrating a method performed by an apparatus according to aspects of this disclosure.
[0016] Figure 11 A flowchart illustrating a method performed by an apparatus according to aspects of this disclosure. Detailed Implementation
[0017] Wireless communication systems can consume significant amounts of energy and are expensive to maintain. Emissions and energy consumption from various components of telecommunications systems can adversely impact the climate. In telecommunications, several industry-specific factors rooted in addressing rising network costs shape efficiency efforts. With the continued growth of mobile traffic, coupled with rising spectrum costs, capital investment costs, and ongoing radio access network (RAN) maintenance / upgrade costs, energy-saving measures are needed in network operations. 5G New Radio (NR) offers significant energy efficiency improvements compared to previous generations. However, new 5G use cases and the adoption of millimeter waves require more resources, which may provide more efficient networks but with higher emissions.
[0018] As discussed in 3GPP TR 38.864 (incorporated herein by reference), network energy efficiency is important for environmental sustainability, reducing environmental impact (e.g., greenhouse gas emissions), and saving operating costs. As 5G becomes more widespread across industries and geographic regions, and more advanced services and applications requiring high data rates (e.g., XR) are being handled, networks are becoming denser, using more antennas, greater bandwidth, and more frequency bands.
[0019] Energy consumption has become a critical component of operators' operating costs. Energy consumption can originate from the RAN, and more specifically from active antenna units (AAUs), with data centers and fiber optic transmission accounting for a smaller share. The power consumption of radio access can be divided into two parts: a dynamic component, which is consumed only when data transmission / reception is in progress; and a static component, which is continuously consumed to maintain the operation of the radio access device, even when data transmission / reception is not in progress.
[0020] Therefore, it is necessary to examine network energy consumption models, key performance indicators (KPIs) (e.g., spectral efficiency, capacity, user-aware throughput (UPT), latency, UE power consumption, complexity, handover performance, call drop rate, initial access performance, SLA guarantee-related KPIs, etc.), evaluation methodologies, and network energy-saving technologies in the target deployment scenario. More efficient operation (both dynamic and semi-static) and finer-grained adaptation of transmission and / or reception in the time, frequency, spatial, and power domains are required, along with potential support / feedback from the UE, potential UE assistance information, and information exchange / coordination through the network interface.
[0021] In one embodiment, a technique for improving network energy efficiency is, for example, discontinuous transmission (DTX) / discontinuous reception (DRX) in the time domain. In one embodiment, cell DTX / DRX is applied to a UE in the RRC_CONNECTED state. Periodic cell DTX / DRX (i.e., active and inactive periods) can be configured by the gNB via UE-specific RRC signaling for each serving cell. Cell DTX / DRX can also be configured and operated together. Per-cell DTX / DRX configuration can configure at least the following parameters: periodicity, start timeslot / offset, and on-duration duration.
[0022] In one embodiment, when a cell activates a single DTX / DRX configuration, UE behavior is examined. The network determines whether a legacy UE in idle mode can access a cell with cell DTX / DRX, and the network should allow UEs with NES capabilities to pre-occupy NES cells. Cell DTX / DRX modes can be activated / deactivated via dynamic L1 / L2 signaling and UE-specific RRC signaling. Both UE-specific signaling and common L1 / L2 signaling can be considered for activating / deactivating cell DTX / DRX modes.
[0023] In one embodiment, the motivation behind standardizing NES capabilities is to improve energy efficiency while serving users without compromising performance. Different use cases from various vertical industries result in different business models and service QoS. It is crucial to conserve maximum network energy while meeting the stringent QoS requirements of these diverse service categories. Furthermore, business models can vary depending on the type of use case or network scenario. Therefore, trade-offs between energy efficiency and required KPIs are likely to arise; for example, a cell benefiting from maximum energy efficiency may fail to meet latency-critical service requirements with sub-millisecond end-to-end latency for multiple UEs. For use cases such as augmented reality (AR) or virtual reality (VR), haptic feedback, autonomous vehicles, mission-critical communications, and mobile robots, such QoS degradation is unacceptable. Therefore, an adaptive and robust NES mechanism is needed to achieve the optimal balance.
[0024] Conventional solutions focus more on meeting user experience while simultaneously attempting to achieve energy efficiency within the network. Therefore, requirements, use cases, and solutions are essentially all within the network itself. Vertical industries and customers cannot obtain energy efficiency information from the network.
[0025] Furthermore, typically, network energy-saving solutions do not integrate QoS awareness into the gNB Central Unit (CU)-Distributed Unit (DU) architecture. The network is configured in NES mode independently of any QoS-related or energy-saving inputs from other entities such as customers, operators, or vertical industries. Moreover, QoS flow and radio bearer configurations are performed without considering the energy-saving solutions configured within the cell. This can lead to user performance degradation and thus service interruptions or inefficient energy-saving solutions.
[0026] The solutions disclosed herein relate to techniques for mitigating trade-offs between energy efficiency and user performance by incorporating QoS awareness into energy-saving modes. This disclosure introduces energy-saving methods that take into account the requirements of customers, operators, or vertical industries. It enables networks to determine radio resource allocation based on required energy efficiency and QoS, and further provides solutions for admission control that take into account network energy efficiency requirements and the NES modes configured in the cell.
[0027] Specifically, the solutions disclosed herein relate to a model for meeting energy-saving requirements while ensuring performance in a gNB CU-DU architecture. Typically, the network is configured in NES mode independently of any QoS-related or energy-saving inputs from other entities such as users, operators, or vertical industries. Furthermore, entities in the CU-DU architecture are entirely controlled by a central unit without any distributed energy-saving alternatives. In this solution, the CU-DU architecture is utilized to simultaneously meet different energy-saving requirements with energy-saving solutions configured per RAN entity (e.g., DU or Radio Unit (RU)). Therefore, better negotiation can be achieved while meeting service requirements and saving the maximum possible energy.
[0028] The proposed solution extends the traditional QoS framework in the CU-DU architecture with energy-saving awareness, enhancing the robustness, efficiency, reliability, and power consumption of the UE. Without the solution presented herein, the UE may experience radio link failures or performance degradation due to the lack of QoS awareness in the energy-saving solution. In one embodiment, the network uses cell load, service type, etc., to determine the NES configuration. Conventional solutions do not facilitate energy-saving-related configurations at the DU or RU level while maintaining different QoS requirements for service. The extensions proposed in this disclosure result in a robust solution and complement the traditional QoS / NES behavior in CU-DU type architectures.
[0029] Aspects of this disclosure are described in the context of wireless communication systems.
[0030] Figure 1This describes an example of a wireless communication system 100 according to aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).
[0031] One or more NEs 102 may be distributed across a geographical area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.
[0032] NE 102 can provide a geographic coverage area that supports services for one or more UEs 104 within that geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some embodiments, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.
[0033] One or more UEs 104 may be distributed across a geographical area of the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, and other instances thereof.
[0034] UE 104 may be able to support direct wireless communication with other UE 104 via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via 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, communication link 114 may be referred to as a side link. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.
[0035] NE 102 may support communication with CN 106 or with another NE 102, or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities (which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs)).
[0036] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) that manage access and mobility, and user plane entities (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) that route packets or interconnect to external networks. In some implementations, the control plane entities may manage non-access stratum (NAS) functions of one or more UEs 104 served by one or more NEs 102 associated with CN 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).
[0037] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session, etc.) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).
[0038] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 may support different resource structures. For example, NE 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 may support various frame structures based on one or more parameter sets.
[0039] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.
[0040] Time intervals for resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.
[0041] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot for the regular cyclic prefix and the extended cyclic prefix, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.
[0042] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, NE 102 and UE 104 may perform wireless communication on one or more of the operating frequency bands. In some embodiments, FR1 may be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.
[0043] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set containing a 15 kHz subcarrier spacing (e.g., μ=0); a second parameter set containing a 30 kHz subcarrier spacing (e.g., μ=1); and a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2); and a fourth parameter set containing a 120 kHz subcarrier spacing (e.g., μ=3).
[0044] In one embodiment, NES categories are created to mitigate the challenges posed by trade-offs between energy efficiency and demanding KPIs. NES categories are defined as identifiers of energy savings / consumption and incorporated into QoS awareness within energy-saving solutions. NES categories can be mapped to NES profiles, which may contain NES configurations, QoS profiles, or a combination thereof. NES categories can be provided by network entities or through operations and maintenance processes using Service Level Agreements (SLAs), or generated by the gNB according to certain rules. Admission control can be performed based on supported NES categories that also include negotiation processes.
[0045] NES profiles may contain NES configurations, such as radio resource configurations and energy cost metrics for representing energy savings / energy consumption. In one embodiment, an NES configuration is the radio resource configuration required to support a particular NES category. For example, a per-cell DTX / DRX configuration may configure the following parameters—periodicity, start time slot / off, and on-duration.
[0046] In one embodiment, the QoS profile represents a list of supported QoS Category Identifier (QCI) values for the corresponding NES category. Alternatively, a single QCI may be associated with an NES category, such as the highest achievable QoS for that NES category.
[0047] An NES category may be associated with one or more QCI values. An NES category may be mapped to one or more radio resource configurations (e.g., one or more NES configurations). The NES category definition may be extended to include additional factors, provided that such additional factors are related to NES characteristics.
[0048] In one embodiment, NES-related configurations are attached to an NES category, and the corresponding guaranteed QoS is indicated by a list of supported QCIs. Example implementations are illustrated in Table 1. One or more NES technologies can be configured and activated simultaneously by the network. Therefore, the corresponding NES configuration in the NES profile provides supported NES-related features. The guaranteed QCI can be provided by the QoS profile of the NES category.
[0049] Table 1 shows the instance definitions of NES categories and describes a list of predefined or dynamically configured NES categories. NES category definitions can be extended to include additional factors, provided that these additional factors are relevant to NES characteristics.
[0050]
[0051] Table 2: Mapping of NES Categories to QCI
[0052] Figure 2 This describes an example of NES category mapping in a CU-DU architecture according to aspects of this disclosure. In a first embodiment related to NES category mapping in the CU-DU architecture, CU 202 maps QoS / NES flow 204 to a corresponding DU 206 based on the NES category 208 associated with QoS / NES flow 204. DU 206 is individually configured, reflecting different power-saving modes. Each RU 210 can be configured with a specific sleep mode / power-saving mode. This allows different QoS / NES flows 204 to be efficiently served via different DU / RU modules.
[0053] Figure 3 This describes an example of a DU-specific NES configuration according to aspects of this disclosure. In one embodiment, for a DU-specific NES configuration, each DU 302 can be configured with an energy-saving mode. For example, configuring a DU-specific DTX / DRX requires specific sleep and activity patterns to accommodate different service and QoS requirements. CU 304 can guarantee a “global” NES class 306 with a cooperative DU mechanism, while each DU 302 provides a certain QCI 308. Depending on the DU-specific NES configuration that satisfies a certain QCI level 308, CU 304 directs QoS flows to the corresponding DU 302. The overall NES class is guaranteed and maintained by CU 304. The activity time of DU 302 determines energy consumption. Considering cell load, one or more DU 302s can be put into sleep mode and service can be maintained through appropriate service redirection between DU 302s. For example, different DU 302s (e.g., DU-1, DU-2, and DU-3) connected to a CU 304 may be able to support QCI 308, such as QCI-x, QCI-y, and QCI-z respectively.
[0054] Figure 4This describes an example of an RU-specific NES configuration according to aspects of this disclosure. In one embodiment, for an RU-specific NES configuration, an energy-saving mode can be configured at the RU level. For example, each RU 402 of DU 404 is configured with an individual NES configuration, such as a DTX / DRX sleep mode or antenna configuration. Therefore, each DU 404 can support an individual NES category 406 for different NES / QoS flows. CU 408 can guarantee different SLAs as a result of individual DU-specific NES category guarantees. Unlike DU-specific NES, in this case, the granularity of the energy-saving configuration method is tuned to the RU level. Therefore, the DU 404 to which one or more RUs 402 are connected can themselves support an individual NES category 406. DU 404 can control and monitor the energy-saving performance of its different RUs 402 and the different NES configurations assigned to the RUs 402. In one embodiment, the NES category 406 is provided to meet operator requirements, while in another embodiment, the requirements for the NES category 406 originate from user-specific or service-specific QoS requirements.
[0055] In one embodiment, at the NAS level (e.g., according to TS23.501, which is incorporated herein by reference), QoS flows are the finest-grained QoS distinctions within a PDU session. QoS flows within a PDU session are identified by a QoS Flow ID (QFI) carried in the encapsulation header on the NG-U. For each UE, one or more PDU sessions are established. The NG-RAN maps packets belonging to different PDU sessions to different Data Radio Bearers (DRBs). NAS-level packet filters in the UE and 5GC associate uplink (UL) and downlink (DL) packets with QoS flows. Access stratum (AS)-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.
[0056] NG-RAN and 5GC ensure QoS (e.g., reliability and target latency) by mapping packets to appropriate QoS flows and DRBs. Therefore, there is a two-step mapping process: IP flow to QoS flow (NAS) and from QoS flow to DRB (AS).
[0057] In one embodiment, at the NAS level, QoS flows are characterized by QoS profiles provided by the 5GC to the NG-RAN and QoS rules provided by the 5GC to the UE. The NG-RAN uses the QoS profiles to determine processing on the radio interface, while the QoS rules define the mapping between uplink user plane traffic and QoS flows to the UE. QoS flows can be guaranteed bit rate (GBR) or non-GBR depending on their profiles.
[0058] In one embodiment, at the AS level, the DRB defines packet processing on the radio interface (Uu). The DRB provides the same packet forwarding processing for packets. NG-RAN's QoS flow to DRB mapping is based on the QFI and associated QoS profiles (e.g., QoS parameters and QoS characteristics). Separate DRBs can be established for QoS flows requiring different packet forwarding processing, or several QoS flows belonging to the same PDU session can be multiplexed within the same DRB.
[0059] In the uplink, the mapping of QoS flows to the DRB is controlled by mapping rules, which are signaled in two different ways (reflection mapping and explicit configuration). A default DRB can be configured for each PDU session. If an incoming UL packet does not match either the configured RRC or the reflection mapping rule, the UE maps that packet to the default DRB of the PDU session.
[0060] Figure 5 This describes an example NES / QoS flow model based on aspects of this disclosure. In one embodiment, NG-RAN (gNBCU 502) and 5GC (UPF 504) ensure quality of service by mapping data packets to appropriate QoS / NES flows 506 and DRB 508. NES category 510 is incorporated into a two-step mapping from IP flow to QoS flow 506 (NAS) and from QoS flow 506 to DRB 508 (AS). NG-RAN uses QoS profiles and NES category 510 to determine processing on the radio interface, while NES / QoS rules define the mapping between uplink user plane traffic and NES / QoS flows 506 to UE 512. NES category 510 is a criterion used to map data to DRB 508 to ensure certain energy savings.
[0061] In one embodiment, a DRB 508 is created between gNB CU 502 and UE 512 to carry data via QoS / NES stream 506. In the downlink, CU 502 is responsible for mapping QoS stream 506 to DRB 508. DRB 508 is configured using RRC configuration. Multiple QoS streams 506 within a DRB 508 are carried via F1 General Packet Radio Service (GPRS) tunnels 514 (one tunnel per DRB 508). Tunnel allocation is performed by CU 502 and sent to DU 514 in the downlink, while DU 514 performs tunnel allocation in the UL, which is then sent to CU 502.
[0062] A logical tunnel (e.g., an NES tunnel) is a container for DRB 508s, which has a single NES class 510 as a lower bound. One or more DRBs 508s may belong to a single NES tunnel 514. For example, DRB1 and DRB2 are associated with a single NES class 1 tunnel. Because the CU (gNB CU 502) contains knowledge of the NES class 510, it is responsible for associating the appropriate DRB 508 with a given NES tunnel 514, ensuring minimal power efficiency when transmitting data via any of the DRBs 508s. Information about the mapping from NES tunnels 514 to DRBs 508s is provided using an RRC configuration similar to logical channel priorities.
[0063] Regarding the behavior of the UE, in one embodiment, in the uplink, there are two steps of mapping uplink data to data radio bearers. In the first step, the uplink data is mapped to an appropriate NES tunnel to ensure minimal power saving. In the second step, the data is mapped to one of the selected NES tunnels in the appropriate DRB.
[0064] In one embodiment, when DU-specific NES is configured, the UE receives different QCIs from different DUs configured with different power-saving profiles. When the NES mode is configured RU-specific, the UE receives different QCIs from different RUs configured with different power-saving profiles. The UE receives NES / QCI category to logical channel mapping information. Based on the mapping information, in the uplink, taking into account the QCI guaranteed by each DU / RU, the UE performs logical channel prioritization to transmit uplink data to the gNB.
[0065] In one embodiment, the RRC controls the scheduling of uplink data for each logical channel by signaling the following: priority, where an increased priority value indicates a lower priority level; prioritizedBitRate, which sets the priority bit rate (PBR); bucketSizeDuration, which sets the bucket size duration (BSD); and optionally allowedTTI-Lengths, which sets the allowed transmit time interval (TTI) length. The priorities of different logical channels are derived by taking into account the NES category guaranteed by the DU / RU. The mapping of UL packets to NES / QoS flows is based on the pre-configured NES category to logical channel mapping information received from the DU / RU.
[0066] In one embodiment, for feedback monitoring or energy consumption metrics (DU to CU), energy consumption metrics can be reported from all distributed units to the central unit and from the RU to the DU. This is used by the CU to assess energy performance and correlate QoS / NES flows. In one embodiment, NES measurements can be monitored at the CU based on feedback received from the DU. Furthermore, when NES is configured to be RU-specific, energy savings can also be monitored directly at the DU.
[0067] Figure 6 This describes an example of coordinated NES category power saving in multiple TRPs according to aspects of this disclosure. In one embodiment involving coordinated NES category power saving (for multiple TRPs), NES categories can be implemented in a multi-TRP scenario similar to a discrete architecture. Depending on the selected / provided NES category, the CU acts as the controller and instructs the DU on power saving targets. Different TRPs 602 can be configured individually, for example, with longer sleep cycles for some TRPs 602 and shorter sleep cycles for others. Therefore, users and services are distributed among the TRPs 602 to achieve network power saving for the TRPs 602.
[0068] In one embodiment, the UE receives different QCIs from different TRPs configured with different power-saving profiles. A mapping is performed between NES / QCI categories and quasi-co-location (QCL-D) containing transmit spatial filters (e.g., DL beams). For the guaranteed QCI, transmission can be directed on the corresponding downlink beam. The UE receives NES / QCI to QCL-D mapping information. This NES category to QCL-D mapping is used to schedule transmissions in the uplink. NES / QCI categories are restricted and mapped to corresponding radio bearers for UL beams and thus to certain UL TRPs. If multiple UL beams are available toward a single TRP, then UL data can be scheduled according to the QCI guaranteed by each beam.
[0069] Figure 7 An example of a UE 700 according to aspects of this disclosure is described. UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, memory 704, controller 706, or transceiver 708, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, electrically).
[0070] Processor 702, memory 704, controller 706, or transceiver 708, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may be a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured or otherwise supporting components for performing the functions described in this disclosure.
[0071] UE 700 can be configured to support components for: receiving NES configuration from a DU of a distributed architecture, the NES configuration including a predetermined QCI value associated with an NES category; determining a logical channel associated with the NES category; performing logical channel prioritization based on the logical channel associated with the NES category for transmitting uplink data to the DU; and transmitting the uplink data to the DU on the logical channel associated with the NES category.
[0072] In one embodiment, the UE 700 may be configured to support components for mapping the uplink data to the logical channel associated with the NES category and mapping the uplink data to the DRB associated with the logical channel. In one embodiment, the UE 700 may be configured to support components for transmitting the uplink data on the beam of the TRP associated with the NES category, based on QCI-to-QCL-D mapping information.
[0073] Processor 702 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 702 may be configured to operate memory 704. In some other embodiments, memory 704 may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory 704 to cause UE 700 to perform various functions of this disclosure.
[0074] Memory 704 may comprise volatile or non-volatile memory. Memory 704 may store computer-readable, computer-executable code containing instructions that, when executed by processor 702, cause UE 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 704 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.
[0075] In some implementations, processor 702 and memory 704 coupled to processor 702 may be configured to cause UE 700 to perform one or more of the functions described herein (e.g., processor 702 executing instructions stored in memory 704). For example, processor 702 may support wireless communication at UE 700 according to examples disclosed herein.
[0076] Controller 706 manages the input and output signals of UE 700. Controller 706 can also manage peripheral devices not integrated into UE 700. In some embodiments, controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 706 may be implemented as part of processor 702.
[0077] In some embodiments, UE 700 may include at least one transceiver 708. In other embodiments, UE 700 may have more than one transceiver 708. Transceiver 708 may represent a wireless transceiver. Transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.
[0078] Receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, receiver chain 710 may include one or more antennas for receiving signals over the air or over a wireless medium. Receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. 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 signal transmission. Receiver chain 710 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.
[0079] Transmitter chain 712 can be configured to generate and transmit signals (e.g., control information, data, packets). 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). 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 a wireless medium. Transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0080] Figure 8An example of a processor 800 according to aspects of this disclosure is described. Processor 800 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 800 may include a controller 802 configured to perform various operations according to the examples described herein. Processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 800 may optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0081] Processor 800 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 800) or contained within the processor chipset) 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).
[0082] Controller 802 can be configured to manage and coordinate various operations of processor 800 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 800 to support various operations according to the examples described herein. For example, controller 802 can operate as a control unit of processor 800, generating control signals that manage the operation of various components of processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timings.
[0083] Controller 802 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 804 and determine subsequent instructions to be executed to enable processor 800 to support various operations according to examples described herein. Controller 802 may be configured to track the memory addresses of instructions associated with memory 804. Controller 802 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 802 may be configured to interpret instructions and determine control signals to be output to other components of processor 800 to enable processor 800 to support various operations according to examples described herein. Additionally or alternatively, controller 802 may be configured to manage data flow within processor 800. Controller 802 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 800.
[0084] Memory 804 may include one or more caches (e.g., memory local to processor 800 or included in processor 800) or other memories, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some embodiments, memory 804 may reside within or on the processor chipset (e.g., local to processor 800). In some other embodiments, memory 804 may reside outside the processor chipset (e.g., remote from processor 800).
[0085] Memory 804 may store computer-readable, computer-executable code containing instructions that, when executed by processor 800, cause processor 800 to perform the 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. Controller 802 and / or processor 800 may be configured to execute computer-readable instructions stored in memory 804 to cause processor 800 to perform various functions. For example, processor 800 and / or controller 802 may be coupled to or coupled to memory 804, and processor 800, controller 802, and memory 804 may be configured to perform the various functions described herein. In some instances, processor 800 may include multiple processors, and memory 804 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or collectively configured to perform the various functions described herein.
[0086] One or more ALU 806s may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALU 806s may reside within or on a processor chipset (e.g., processor 800). In some other embodiments, one or more ALU 806s may reside outside the processor chipset (e.g., processor 800). One or more ALU 806s may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 806s may receive input operands and an opcode that determines the operation to be performed. One or more ALU 806s may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 806s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 806s to handle conditional operations, comparisons, and bitwise operations.
[0087] Processor 800 may support wireless communication according to examples disclosed herein. In one embodiment, processor 800 may be configured or operable to support components for: determining an NES mode for a NE, the NES mode including a DU-specific mode or an RU-specific mode for a distributed architecture; determining an NES category and NES configuration for a traffic flow associated with the NE based on the NES mode, the NES category being associated with a QoS category of the traffic flow; mapping the traffic flow to a DU, RU, or a combination thereof based on the NES category associated with the traffic flow; and transmitting the NES configuration to the DU, RU, or combination thereof mapped to the traffic flow.
[0088] In one embodiment, processor 800 may be configured to support components for: directing the service flow to the DU based on the NES configuration of the DU. In one embodiment, the NES configuration configures the DU, the RU, or a combination thereof for a predetermined QCI value based on the NES category. In one embodiment, processor 800 may be configured to support components for: mapping the NES category to the NES configuration and the predetermined QCI.
[0089] In one embodiment, the traffic flow includes a QoS flow, an NES flow, or a combination thereof. In one embodiment, the processor 800 may be configured to support components for mapping the traffic flow to one or more DRBs associated with the NES category.
[0090] In one embodiment, processor 800 may be configured to support components for allocating the traffic flow to a logical NES channel, the logical NES channel including one or more DRBs associated with the NES category. In one embodiment, processor 800 may be configured to support components for transmitting information of the logical NES channel to the DU, the RU, or a combination thereof.
[0091] In one embodiment, processor 800 includes the CU of the distributed architecture. In one embodiment, the service flow is associated with a TRP, wherein processor 800 is configured to support components for transmitting the NES configuration to the TRP according to the NES category and the service flow.
[0092] In one embodiment, processor 800 may be configured to support components for: receiving NES configuration from a DU of a distributed architecture, the NES configuration including a predetermined QCI value associated with an NES category; determining a logical channel associated with the NES category; performing logical channel prioritization based on the logical channel associated with the NES category for transmitting uplink data to the DU; and transmitting the uplink data to the DU on the logical channel associated with the NES category.
[0093] In one embodiment, processor 800 may be configured to support components for mapping the uplink data to the logical channel associated with the NES class and mapping the uplink data to the DRB associated with the logical channel. In one embodiment, processor 800 may be configured to support components for transmitting the uplink data on the beam of the TRP associated with the NES class, based on QCI-to-QCL-D mapping information.
[0094] Figure 9 An example of NE 900 according to aspects of this disclosure is described. NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, memory 904, controller 906, or transceiver 908, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively ground, communicatively ground, functional ground, electronic ground, electrical ground).
[0095] The processor 902, memory 904, controller 906, or transceiver 908, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may be a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured or otherwise supporting components for performing the functions described in this disclosure.
[0096] The NE 900 can be configured to support components for: determining an NES mode for the NE, the NES mode including a DU-specific mode or an RU-specific mode for a distributed architecture; determining an NES category and NES configuration for a service flow associated with the NE based on the NES mode, the NES category being associated with a QoS category of the service flow; mapping the service flow to a DU, RU, or a combination thereof based on the NES category associated with the service flow; and transmitting the NES configuration to the DU, RU, or combination thereof mapped to the service flow.
[0097] In one embodiment, the NE 900 may be configured to support components for: directing the service flow to the DU based on the NES configuration of the DU. In one embodiment, the NES configuration configures the DU, the RU, or a combination thereof for a predetermined QCI value based on the NES category. In one embodiment, the NE 900 may be configured to support components for: mapping the NES category to the NES configuration and the predetermined QCI.
[0098] In one embodiment, the service flow includes a QoS flow, an NES flow, or a combination thereof. In one embodiment, the NE900 may be configured to support components for mapping the service flow to one or more DRBs associated with the NES category.
[0099] In one embodiment, the NE 900 may be configured to support components for allocating the traffic flow to a logical NES channel, the logical NES channel including one or more DRBs associated with the NES category. In one embodiment, the NE 900 may be configured to support components for transmitting information of the logical NES channel to the DU, the RU, or a combination thereof.
[0100] In one embodiment, the NE 900 includes the CU of the distributed architecture. In one embodiment, the service flow is associated with a TRP, wherein the NE 900 can be configured to support components for transmitting the NES configuration to the TRP according to the NES category and the service flow.
[0101] Processor 902 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 902 may be configured to operate memory 904. In some other embodiments, memory 904 may be integrated into processor 902. Processor 902 may be configured to execute computer-readable instructions stored in memory 904 to cause NE 900 to perform various functions of this disclosure.
[0102] Memory 904 may comprise volatile or non-volatile memory. Memory 904 may store computer-readable, computer-executable code containing instructions that, when executed by processor 902, cause NE 900 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 904 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.
[0103] In some implementations, processor 902 and memory 904 coupled to processor 902 may be configured to cause NE 900 to perform one or more of the functions described herein (e.g., processor 902 executing instructions stored in memory 904). For example, processor 902 may support wireless communication at NE 900 according to examples disclosed herein.
[0104] Controller 906 manages the input and output signals of NE 900. Controller 906 can also manage peripheral devices not integrated into NE 900. In some embodiments, controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 906 may be implemented as part of processor 902.
[0105] In some embodiments, the NE 900 may include at least one transceiver 908. In other embodiments, 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.
[0106] Receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, receiver chain 910 may include one or more antennas for receiving signals over the air or over a wireless medium. Receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. 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 signal transmission. Receiver chain 910 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.
[0107] Transmitter chain 912 can be configured to generate and transmit signals (e.g., control information, data, packets). 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). 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 a wireless medium. Transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0108] Figure 10 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by an NE as described herein. In some embodiments, the NE can execute a set of instructions to control the functional elements of the NE to perform the described functions.
[0109] At 1002, the method can determine the NES mode for the NE, the NES mode including a DU-specific mode or an RU-specific mode for a distributed architecture. The operation of 1002 can be performed according to the instances described herein. In some embodiments, aspects of the operation of 1002 can be derived from references... Figure 9 The NE execution described.
[0110] At 1004, the method can determine the NES category and NES configuration of the service flow associated with the NE based on the NES mode, wherein the NES category is associated with the QoS category of the service flow. The operation of 1004 can be performed according to the examples described herein. In some embodiments, aspects of the operation of 1004 may be as referenced... Figure 9 The NE execution described.
[0111] At 1006, the method may map the service flow to a DU, RU, or a combination thereof based on the NES category associated with the service flow. The operation of 1006 may be performed according to the instances described herein. In some embodiments, aspects of the operation of 1006 may be as described in references... Figure 9 The NE execution described.
[0112] At 1008, the method may transmit the NES configuration to the DU, the RU, or a combination thereof mapped to the service flow. The operation of 1008 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1008 may be as described in references... Figure 9 The NE execution described.
[0113] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible.
[0114] Figure 11 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by a UE as described herein. In some embodiments, the UE can execute a set of instructions to control functional elements of the UE to perform the described functions.
[0115] At 1102, the method may receive an NES configuration from a DU in a distributed architecture, the NES configuration including a predetermined QCI value associated with an NES category. The operation of 1102 may be performed according to an instance as described herein. In some embodiments, aspects of the operation of 1102 may be provided by reference to [reference needed]. Figure 7 The UE execution described.
[0116] At 1104, the method can determine the logical channel associated with the NES category. The operation of 1104 can be performed according to the examples described herein. In some embodiments, aspects of the operation of 1104 can be determined by reference to... Figure 7 The UE execution described.
[0117] At 1106, the method may perform logical channel prioritization based on the logical channel associated with the NES category for transmitting uplink data to the DU. The operation of 1106 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1106 may be as described in references... Figure 7 The UE execution described.
[0118] At 1108, the method may transmit the uplink data to the DU on the logical channel associated with the NES category. Operation of 1108 may be performed according to the examples described herein. In some embodiments, aspects of operation of 1108 may be as described in references... Figure 7 The UE execution described.
[0119] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible.
[0120] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A network device NE for wireless communication, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the NE: Determine the network energy-saving NES mode for the NE, the NES mode including a distributed unit DU-specific mode or a radio unit RU-specific mode of a distributed architecture; Based on the NES mode, the NES category and NES configuration of the service flow associated with the NE are determined, and the NES category is associated with the Quality of Service (QoS) category of the service flow. The service flow is mapped to a DU, RU, or a combination thereof based on the NES category associated with it; and The NES configuration is transmitted to the DU, the RU, or a combination thereof mapped to the service flow.
2. The NE of claim 1, wherein the at least one processor is configured to cause the NE to route the service flow to the DU based on the NES configuration of the DU.
3. The NE according to claim 1, wherein the NES configuration configures the DU, the RU, or a combination thereof based on the NES category for a predetermined QoS category identifier QCI value.
4. The NE of claim 3, wherein the at least one processor is configured such that the NE maps the NES category to the NES configuration and the predetermined QCI.
5. The NE according to claim 1, wherein the service flow includes 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 being associated with the NES category.
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 category.
8. The NE of claim 7, wherein the at least one processor is configured to cause the NE to transmit information of the logical NES channel to the DU, the RU, or a combination thereof.
9. The NE of claim 1, wherein the NE includes the central unit (CU) of the distributed architecture.
10. The NE of claim 1, wherein the service flow is associated with a transmit-receive point (TRP), and the at least one processor is configured to cause the NE to transmit the NES configuration to the TRP according to the NES category and the service flow.
11. A method performed by a network equipment (NE), the method comprising: Determine the network energy-saving NES mode for the NE, the NES mode including a distributed unit DU-specific mode or a radio unit RU-specific mode of a distributed architecture; Based on the NES mode, the NES category and NES configuration of the service flow associated with the NE are determined, and the NES category is associated with the Quality of Service (QoS) category of the service flow. The service flow is mapped to a DU, RU, or a combination thereof based on the NES category associated with it; and The NES configuration is transmitted to the DU, the RU, or a combination thereof mapped to the service flow.
12. The method of claim 11, further comprising directing the service flow to the DU based on the NES configuration of the DU.
13. The method of claim 11, wherein the NES configuration configures the DU, the RU, or a combination thereof based on the NES category for a predetermined QoS category identifier (QCI) value.
14. The method of claim 13, further comprising mapping the NES category to the NES configuration and the predetermined QCI.
15. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor, coupled to and configured to enable the UE to: The network energy-saving NES configuration is received from the distributed unit (DU) of the distributed architecture, the NES configuration including a predetermined quality of service (QoS) category identifier (QCI) value associated with the NES category; Determine the logical channel associated with the NES category; Logical channel prioritization is performed based on the logical channel associated with the NES category for transmitting uplink data to the DU; and The uplink data is transmitted to the DU on the logical channel associated with the NES category.
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 category and to map the uplink data to the data radio bearer (DRB) associated with the logical channel.
17. The UE of claim 15, wherein the at least one processor is configured to enable the UE to transmit the uplink data on a beam of the transmit-receive point (TRP) associated with the NES category, based on QCI-to-quasi-co-located QCL-D mapping information.
18. A method performed by a user equipment (UE), the method comprising: The network energy-saving NES configuration is received from the distributed unit (DU) of the distributed architecture, the NES configuration including a predetermined quality of service (QoS) category identifier (QCI) value associated with the NES category; Determine the logical channel associated with the NES category; Logical channel prioritization is performed based on the logical channel associated with the NES category for transmitting uplink data to the DU; and The uplink data is transmitted to the DU on the logical channel associated with the NES category.
19. The method of claim 18, further comprising mapping the uplink data to the logical channel associated with the NES category and mapping the uplink data to the 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 category, based on QCI-to-quasi-co-located QCL-D mapping information.
