Adaptive processing envelope based on power consumption

Abstract

Methods, systems, and devices for wireless communication are described. In general, the described techniques provide for reconfiguring a resource envelope allocated to a distributed unit (DU) or radio unit (RU) based on power consumption at the DU or RU. A virtual radio access network (VRAN) manager (e.g., a host platform of a VRAN) may perform baseband pooling to allocate a resource envelope to a DU or RU. After initially allocating a resource envelope to a DU or an RU, the DU, the RU, or both may report an amount of power consumed during signal processing of one or more dimensions of the resource envelope. The VRAN manager may then reconfigure a resource envelope of the DU or the RU based on power consumption at the devices (e.g., to minimize operating cost (OPEX) or maximize utilization of the resource envelope).

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 877,773, entitled “ADAPTIVE PROCESSING ENVELOPE BASED ON POWER CONSUMPTION,” filed by Uziel et al. on July 29, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including adaptive processing envelopes based on power consumption. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0005] A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Some wireless communication systems may support baseband pooling, where processing resources may be allocated to network entities in a pool. Processing resources may include hardware or software (e.g., memory or internal processing resources) for performing signal processing. Improved techniques for efficiently utilizing processing resources using baseband pooling may be desirable. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting adaptive processing envelopes based on power consumption. In general, the described technology provides for reconfiguring the resource envelope allocated to a distributed unit (DU) or a radio unit (RU) based on the power consumption at the DU or the RU. A virtual radio access network (VRAN) manager (e.g., a host platform of the VRAN) may perform baseband pooling to allocate resource envelopes to the DU or RU. After the resource envelope is initially allocated to the DU or RU, the DU, RU or both may report metrics for assisting system-level power consumption optimization. For example, the DU or RU may report the amount of power consumed during signal processing of one or more dimensions of the resource envelope. Different dimensions of the resource envelope may include different numbers of layers, different numbers of carriers, different bandwidth portions, different power backoffs, etc. The VRAN manager may then reconfigure the resource envelope of the DU or RU based on the power consumption at these devices (e.g., to minimize operating expenses (OPEX) or maximize the utilization of the resource envelope).

[0007] (The content of this invention will be completed after the final approval of the claims) BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 An example of a wireless communication system supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated.

[0009] Figure 2 An example of a wireless communication system supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated.

[0010] Figure 3 An example of baseband pooling according to one or more aspects of the present disclosure is illustrated.

[0011] Figure 4 Examples of radio frequency or radio unit (RU) power consumption according to one or more aspects of the present disclosure are illustrated.

[0012] Figure 5 An example of a wireless communication system supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated.

[0013] Figure 6 Examples of configuration and reporting signaling to support adaptive processing envelopes based on power consumption according to one or more aspects of the present disclosure are illustrated.

[0014] Figure 7 An example of a process flow supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated.

[0015] Figure 8An example of a process flow supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated.

[0016] Fig. 9 and Fig.10 A block diagram of a device supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is shown.

[0017] Fig.11 A block diagram of a communication manager supporting adaptive processing envelope based on power consumption is shown in accordance with one or more aspects of the present disclosure.

[0018] Fig.12 A diagram of a system including a device supporting adaptive processing envelope based on power consumption in accordance with one or more aspects of the present disclosure is shown.

[0019] Figure 13 to Figure 14 A flow chart illustrating a method of supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0020] Some wireless communication systems may support baseband pooling, where processing resources may be allocated to network entities in a pool. Processing resources may include hardware or software (e.g., memory or internal processing resources) for performing signal processing. The pool of processing resources allocated to the network entity may be referred to as a baseband resource envelope. The baseband resource envelope may be a virtualization of the processing resource pool and may refer to resources (e.g., physical resources) on which the network entity may perform signal processing. For example, the baseband resource envelope may be subject to or depend on the number of layers, the number of component carriers (e.g., per layer), and the range of frequency resources (e.g., per component carrier). The network entity may then perform signal processing on the baseband resource envelope, and it may be expected that the signal processing will not exceed the maximum capacity of the processing resource pool corresponding to the baseband resource envelope.

[0021] In some aspects, a distributed unit (DU) may be configured with a baseband resource envelope for signal processing, and the DU may be connected to one or more radio units (RUs). The DU may allocate its baseband resource envelope to one or more RUs in one or more sub-envelopes, and the DU may perform signal processing on each RU according to the sub-envelopes allocated to the RUs. The signal processing performed by the DU for the RU may support communication between the RU and one or more user equipments (UEs). However, in some cases, the baseband resource envelope configured at the DU may be static (e.g., a static envelope configuration), and the sub-envelopes allocated to each RU in one or more RUs may also be static. Therefore, the network may not be able to adjust the baseband resource envelope allocated to the DU, and the DU may not be able to maximize the use of the processing resource pool corresponding to the baseband resource envelope. In addition, the network may not be able to perform system optimization of communications at the RU (e.g., optimization of transmit power, number of antennas, digital pre-distortion (DPD), etc.). Therefore, there may be excessive power consumption at the DU, and there may be higher operating expenses (OPEX) in the network.

[0022] As described herein, a wireless communication system may support efficient techniques for reconfiguring a baseband resource envelope allocated to a DU or RU based on power consumption at the DU or RU. A virtual radio access network (VRAN) manager (e.g., a host platform of the VRAN) may perform baseband pooling to allocate a baseband resource envelope to a DU or RU. After the baseband resource envelope is initially allocated to the DU or RU, the DU, RU, or both may report the amount of power consumed during signal processing of one or more dimensions of the baseband resource envelope. Different dimensions of the baseband resource envelope may include different numbers of layers, different numbers of carriers, different bandwidth portions, different power backoffs, etc. (e.g., different distributions of resources of the baseband resource envelope). In some examples, different dimensions of the baseband resource envelope may be associated with different power consumption values ​​based on one or more conditions (e.g., Doppler, affecting performance at the receiver such as tile size, which in turn may affect power consumption). The VRAN manager may then reconfigure the baseband resource envelope of the DU or RU based on the power consumption at these devices (e.g., to minimize OPEX or maximize utilization of the processing resource pool corresponding to the baseband resource envelope).

[0023] Various aspects of the present disclosure are first described in the context of a wireless communication system. Examples of processes and signaling exchanges that support adaptive processing envelopes based on power consumption are then described. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to adaptive processing envelopes based on power consumption.

[0024] Figure 1An example of a wireless communication system 100 supporting an adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0025] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0026] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.

[0027] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0028] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other through the backhaul communication link 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0029] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0030] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0031] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate over those communication links.

[0032] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support an adaptive processing envelope based on power consumption as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0033] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0034] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0035] UE 115 and network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0036] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0037] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0038] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configured to support communication over one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0039] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0040] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0041] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δfmax It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0042] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0043] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the amount of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0044] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0045] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for respective coverage areas 110 using the same or different radio access technologies.

[0046] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0047] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0048] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0049] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0050] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of a spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, RU170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0051] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0052] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0053] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0054] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0055] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate through logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, transport channels may be mapped to physical channels.

[0056] The wireless communication system 100 may support baseband pooling, where processing resources may be allocated to the network entity 105 in a pool. The processing resources may include hardware or software (e.g., memory or internal processing resources) for performing signal processing. The pool of processing resources allocated to the network entity 105 may be referred to as a baseband resource envelope. The baseband resource envelope may be a virtualization of the processing resource pool and may refer to resources (e.g., physical resources) on which the network entity 105 may perform signal processing. For example, the baseband resource envelope may include a certain number of layers, a certain number of component carriers (e.g., per layer), and a certain range of frequency resources (e.g., per component carrier). The network entity 105 may then perform signal processing on the baseband resource envelope, and it may be expected that the signal processing will not exceed the maximum capacity of the processing resource pool corresponding to the baseband resource envelope.

[0057] In some aspects, the DU may be configured with a baseband resource envelope for signal processing, and the DU may be connected to one or more RUs. The DU may allocate its baseband resource envelope to one or more RUs in one or more sub-envelopes, and the DU may perform signal processing on each RU according to the sub-envelope allocated to the RU. The signal processing performed by the DU for the RU may support communication between the RU and one or more UEs 115. However, in some cases, the baseband resource envelope configured at the DU may be static (e.g., a static envelope configuration), and the sub-envelope allocated to each RU in one or more RUs may also be static. Therefore, the network may not be able to adjust the baseband resource envelope allocated to the DU, and the DU may not be able to maximize the use of the processing resource pool corresponding to the baseband resource envelope. In addition, the network may not be able to perform system optimization of communications at the RU (e.g., optimization of transmit power, number of antennas, DPD, etc.). Therefore, there may be excessive power consumption at the DU, and there may be higher OPEX in the network.

[0058] The wireless communication system 100 may support efficient techniques for reconfiguring baseband resource envelopes allocated to a DU or RU based on power consumption at the DU or RU. A VRAN manager (e.g., a host platform of the VRAN) may perform baseband pooling to allocate baseband resource envelopes to the DU or RU. After the baseband resource envelope is initially allocated to the DU or RU, the DU, RU, or both may report the amount of power consumed during signal processing of one or more dimensions of the baseband resource envelope. Different dimensions of the baseband resource envelope may include different numbers of layers, different numbers of carriers, different bandwidth portions, different power backoffs, etc. (e.g., different distributions of resources of the baseband resource envelope). The VRAN manager may then reconfigure the baseband resource envelope of the DU or RU based on the power consumption at these devices (e.g., to minimize OPEX or maximize utilization of a processing resource pool corresponding to the baseband resource envelope).

[0059] Figure 2An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting an adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.

[0060] Each network entity 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, the network entity 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0061] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0062] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0063] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0064] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0065] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0066] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0067] The network architecture 200 may support baseband pooling, where processing resources may be allocated to the network entity 105 in a pool. The processing resources may include hardware or software (e.g., memory or internal processing resources) for performing signal processing. The pool of processing resources allocated to the network entity 105 may be referred to as a baseband resource envelope. The baseband resource envelope may be a virtualization of the processing resource pool and may refer to resources (e.g., physical resources) on which the network entity 105 may perform signal processing. For example, the baseband resource envelope may include a certain number of layers, a certain number of component carriers (e.g., per layer), and a certain range of frequency resources (e.g., per component carrier). The network entity 105 may then perform signal processing on the baseband envelope, and it may be expected that the signal processing will not exceed the maximum capacity of the processing resource pool corresponding to the baseband envelope.

[0068] In some aspects, the DU 165 may be configured with a baseband resource envelope for signal processing, and the DU 165 may be connected to one or more RUs 170. The DU 165 may allocate its baseband resource envelope to the one or more RUs 170 in one or more sub-envelopes, and the DU 165 may perform signal processing for each RU 170 according to the sub-envelope allocated to the RU 170. The signal processing performed by the DU 165 for the RU 170 may support communication between the RU 170 and one or more UEs 115. However, in some cases, the baseband resource envelope configured at the DU 165 may be static, and the sub-envelope allocated to each RU in the one or more RUs 170 may also be static (e.g., static envelope configuration). Therefore, the network may not be able to adjust the baseband resource envelope allocated to the DU 165 or RU 170, and the DU 165 or RU 170 may not be able to maximize the use of the processing resource pool corresponding to the baseband resource envelope. Therefore, there may be excess power consumption at the DU 165 or RU 170, and there may be higher OPEX in the network.

[0069] The network architecture 200 may support efficient techniques for reconfiguring baseband resource envelopes allocated to a DU 165 or RU 170 based on power consumption at the DU 165 or RU 170. A VRAN manager (e.g., a host platform of the VRAN) may perform baseband pooling to allocate baseband resource envelopes to the DU 165 or RU 170. After the baseband resource envelopes are initially allocated to the DU 165 or RU 170, the DU 165, RU 170, or both may report the amount of power consumed during signal processing of one or more dimensions of the baseband resource envelope. The different dimensions of the baseband resource envelope may include different numbers of layers, different numbers of carriers, different bandwidth portions, different power backoffs, etc. (e.g., different distributions of resources of the baseband resource envelope). The VRAN manager may then reconfigure the baseband resource envelopes of the DU 165 or RU 170 based on power consumption at these devices (e.g., to minimize OPEX or maximize utilization of a processing resource pool corresponding to the baseband resource envelope).

[0070] Figure 3 An example of baseband pooling 300 according to one or more aspects of the present disclosure is illustrated. In a VRAN application utilizing baseband pooling, a centralized baseband unit (BBU) 305 (e.g., DU) handles the physical layer of many non-co-located sites 310 (e.g., a first RU 310-a and a second RU 310-b). For capital expenditure (CAPEX) optimization, the baseband capacity in the RAN can generally be sized as a sub-envelope usage of the system capacity, where it is not assumed that the maximum capacity can be achieved at all sites at any time. Therefore, the CAPEX and the achievable capacity may be dictated by the actual RAN infrastructure, the maximum first layer (L1) processing envelope of the baseband modem, and there may be a system tradeoff that allows L1 resources to be added to the baseband pool at the expense of increased CAPEX. This increase in L1 resources may also have a direct impact on the overall RAN infrastructure power consumption and, accordingly, the system OPEX. In some cases, power consumption may be a key performance indicator (KPI) for VRAN OPEX due to the impact of cooling and L1 resource increases in VRAN servers. Therefore, the achievable envelope of L1 PHY resources becomes a key parameter for VRAN cost component optimization. Because there may be a trade-off between required resources (e.g., for channel conditions, coverage, scheduling, etc.) and power consumption based on baseband pooling, power consumption reporting can help baseband pooling, thereby using the KPI of power consumption as a threshold or parameter.

[0071] In a VRAN application with a baseband pool, the size of the L1 physical resource envelope (e.g., baseband resource envelope) may be set to or depend on the number of layers, the number of frequency resources (e.g., MHz), and the number of component carriers (e.g., number of layers*MHz*number of component carriers). For example, when serving non-co-located sites (e.g., RUs), a BBU serving a large-capacity MIMO site may require a large number of layers (e.g., 16) with a small number of component carriers (e.g., 2), or a BBU serving a non-large-capacity MIMO site (e.g., with a smaller layer size) may require a smaller number of layers (e.g., 8, 4, or 2) with a larger number of component carriers (e.g., 32, 16, or 8) to support many RUs. In some cases, a VRAN system may be provided based on a static envelope configuration of L1 resources (e.g., according to an open RAN (ORAN) specification or a commercial VRAN implementation). When a carrier in a VRAN is initialized, baseband resources may be allocated based on the envelope it supports, which is affected by the number of layers, the number of frequency resources (e.g., the bandwidth part (BWP) size of each carrier), and the number of component carriers supported by the envelope. In some examples, the resource envelope may depend on the algorithm configuration (e.g., equalizer density).

[0072] Figure 4 An example of RF or RU power consumption 400 according to one or more aspects of the present disclosure is illustrated. The overall power consumption that affects the OPEX of the RU may also be affected by dynamic behavior. The dynamic behavior of the RU may be different along different dimensions of the resource envelope at the RU used to provide communication to one or more UEs. An example attribute that affects dynamic VRAN power consumption may be the actual physical allocation of each time slot. The actual physical allocation of each time slot may be affected by the traffic pattern and the link budget, thereby providing the product of the number of layers, the number of physical resource blocks (PRBs), and the number of symbols (e.g., MHz*μsec) for the UE at each component carrier. In some cases, RU power may be reduced with reduced load, which may reduce power consumption (e.g., where power consumption may also be based on the activation of a power saving mode at a network entity). Another example attribute that affects dynamic VRAN power consumption may be the RU configuration. The RU configuration may include the number of power amplifiers (PAs) (e.g., with corresponding power efficiencies) and the number of antenna elements. Yet another example attribute that affects dynamic VRAN power consumption may be the transmitted power. The transmitted power may be the transmit power of the RU (eg, based on overall network and cell requirements) and may be based on a DPD method (eg, based on capabilities of both the network entity and the UE, as well as PA efficiency).

[0073] Figure 5An example of a wireless communication system 500 supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated. The wireless communication system 500 includes a VRAN manager 505, which may be a reference Figures 1 to 4 The wireless communication system 500 also includes a DU 510, which may be a reference Figures 1 to 4 The wireless communication system 500 also includes RU 515-a, RU 515-b, and RU 515-c, which may be reference Figures 1 to 4 The wireless communication system 500 may implement aspects of the wireless communication system 100 or the network architecture 200. For example, the wireless communication system 500 may support efficient techniques for reconfiguring a processing envelope for signal processing at the DU 510 or RU 515 or both based on power consumption at the DU 510 or RU 515.

[0074] The VRAN manager 505 may provide initial configuration or pre-configuration of resource envelopes (e.g., baseband resource envelopes) for processing at the DU 510 and resource envelopes for each RU 515. The DU 510 (e.g., physical layer) may provide (e.g., to the VRAN manager 505) processing values ​​per allocated resource (e.g., memory or internal resources), and each RU 515 (e.g., radio frequency transmitter and receiver) may provide (e.g., to the VRAN manager 505) processing values ​​per PHY. in The initial configuration of the resource envelope of the DU 510 may be based on the processing values ​​provided by the DU 510, and the initial configuration of the resource envelope of each RU 515 may be based on the PA efficiency map and DPD reduction value provided by the RU 515.

[0075] After the initial configuration of the resource envelope at the DU 510 and each RU 515, the VRAN manager 505 can reconfigure the resource envelope at the DU 510 or one or more RUs 515 using the techniques described herein. The techniques introduce a set of reports provided to the VRAN manager 505 (e.g., VRAN) by the DU 510 (e.g., DU L1 infrastructure), a set of reports provided to the VRAN manager 505 (e.g., VRAN) by each RU 515 (e.g., RU infrastructure), and a set of corresponding configurations (e.g., configuration adjustments) for L1 that can allow the VRAN manager 505 to optimize the envelope (e.g., temporary envelope) and dynamically adjust the DU or RU L1 configuration to attributes that affect power consumption. The set of reports transmitted by the DU 510 to the VRAN manager 505 can be transmitted via a functional application platform interface (FAPI), and the set of reports transmitted by the RU 515 to the VRAN manager 505 can be sent via an ORAN interface.

[0076] Figure 6 An example of configuration and reporting signaling 600 to support adaptive processing envelope based on power consumption in accordance with one or more aspects of the present disclosure is illustrated.

[0077] In one aspect, the DU 510 may transmit a power consumption report 520 (e.g., a physically based report) to the VRAN manager 505 to provide a measure of the power consumption at the DU 510 that is affected by the dimension setting conditions. For example, each RU 515 connected to the DU 510 may be assigned a sub-envelope of the resource envelope of the DU 510, and the RU 515 may communicate using a specific dimension of the sub-envelope (e.g., a certain number of layers, a certain number of frequency resources, and a certain number of component carriers). The DU 510 may measure the power consumption used to perform signal processing of the RU 515 according to the sub-envelope assigned to the RU 515, and the DU 510 may report the power consumption of each RU 515 to the VRAN manager 505. The DU 510 may also indicate the dimension of the sub-envelope of the RU 515 associated with the power consumption at the DU 510. In this way, the VRAN manager 505 is able to populate a table with power consumption values ​​of different values ​​along one or more dimensions supported by the resource envelope of the DU 510.

[0078] Table 1 shows an example of a table of power consumption values ​​that may contain different values ​​along one or more dimensions supported by a resource envelope.

[0079] Table 1: Power consumption values ​​for different values ​​along one or more dimensions

[0080]

[0081] The DU 510 may provide information (e.g., power consumption values) of low, medium, or high correlation for each RU 515 (e.g., since correlation may affect equalizer density and signal processing complexity, which have a direct impact on DU power consumption). In addition, the DU 510 may provide a measure of the empirical correlation experienced by the received demodulation layer. The correlation of each RU 515 may refer to the correlation of signals received at or sent by the RU 515. For example, signals received from UEs 115 in the same area may have high correlation, while signals received from UEs 115 in different areas may have low correlation. Similarly, signals sent to UEs 115 in the same area may have high correlation, while signals sent to UEs 115 in different areas may have low correlation.

[0082] In addition to the measured layer correlation experienced from the over-the-air received signals processed by the DU 510, knowing the impact of DU modem power consumption at the VRAN, the VRAN manager 505 can optimize its L1 DU physical resource allocation by considering the infrastructure system power consumption. That is, the wireless communication system 500 can support techniques for system adaptation, and a centralized RAN (CRAN) adaptation entity can be introduced. In addition, the wireless communication system 500 can support techniques for adapting to changing envelopes. The physical layer can be notified of envelope reconfigurations 525 (e.g., reconfigured or updated resource envelopes) (e.g., reduce memory, reduce energy consumption, re-interpret internal processing resources), and the envelope can include a certain number of layers, a certain number of component carriers, bandwidth portions within a component carrier or CRAN, a certain number of scheduled UEs, spatial multiplexing between UEs, etc. Therefore, in the VRAN, these techniques can provide processing pooling between VRANs.

[0083] In another aspect, the RU 515 may transmit a power consumption report 520 (e.g., a physically based report) to the VRAN manager 505 (e.g., via the DU 510) to provide a measure of power consumption at the RU 515 that is affected by the dimension setting conditions. For example, the RU 515 may be assigned a sub-envelope of the resource envelope of the DU 510, and the RU 515 may communicate using specific dimensions of the sub-envelope (e.g., a certain number of PRBs and power backoff). The RU 515 may measure the power consumption used to perform signal processing according to the sub-envelope, and the RU 515 may report the power consumption to the VRAN manager 505. The RU 515 may also indicate the dimensions of the sub-envelope at the RU 515 associated with the power consumption at the RU 515. In this way, the VRAN manager 505 is able to populate a table with power consumption values ​​of different values ​​along one or more dimensions supported by the sub-envelope of the RU 515.

[0084] Table 2 shows an example of a table of power consumption values ​​that may contain different values ​​along one or more dimensions supported by a resource envelope.

[0085] Table 2: Power consumption values ​​for different values ​​along one or more dimensions

[0086]

[0087] The information provided by the RU 515 to the VRAN manager 505 (e.g., power consumption values) may depend on the RU radio frequency design involving DPD or the receiver frequency design involving channel estimation and cycle-based blocking. In addition, the RU 515 may report its temporary experienced power consumption, allowing direct visibility of the actual envisioned power consumption at the RU 515 through the VRAN. Knowing the impact of RU radio frequency power consumption at the VRAN, the VRAN can optimize its site geometry or bandwidth coverage by taking into account the RU system power consumption. The VRAN system can then react based on the overall RU power consumption optimization using dynamic configuration of the power for the RU (e.g., allocation of the number of layers or the number of PRBs). The VRAN system may instruct the RU's envelope reconfiguration 525 to reflect the dynamic configuration of the RU's baseband pooling.

[0088] Figure 7 An example of a process flow 700 for supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated. The process flow 700 includes a VRAN manager 705, which may be a reference Figures 1 to 6 The process flow 700 also includes a DU 710, which may be a reference Figures 1 to 6 The process flow 700 may implement aspects of the wireless communication system 100, the network architecture 200, or the wireless communication system 500. For example, the process flow 700 may support efficient techniques for reconfiguring a processing envelope for signal processing at the DU 710 or RU based on power consumption at the DU 710.

[0089] In the following description of process flow 700, signaling exchanged between VRAN manager 705 and DU 710 may be exchanged in an order different from the example order shown, or operations performed by VRAN manager 705 and DU 710 may be performed in a different order or at a different time. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0090] At 715, the VRAN manager 705 may transmit a first processing envelope for signal processing at the DU 710, and the DU 710 may receive the first processing envelope. The signal processing may be associated with providing communications for one or more UEs 115. At 720, the DU 710 may perform power consumption measurements to determine the amount of power consumed when performing signal processing. At 725, the DU 710 may transmit a report based on the amount of power consumed at the DU 710 during signal processing, and the VRAN manager 705 may receive the report. In some cases, the report may include power consumption values ​​for each of a plurality of values ​​along one or more dimensions supported by the first processing envelope. At 730, the VRAN manager 705 may transmit a second processing envelope for processing at the DU 710 based on the report, and the DU 710 may receive the second processing envelope.

[0091] In some cases, each of the one or more dimensions supported by the first processing envelope may include a different number of layers, a different number of carriers, and a different BWP size (e.g., for each carrier). In some cases, the DU 710 may also transmit in the report a resource utilization level of the first processing envelope at the DU 710 (e.g., utilization of a processing resource pool corresponding to the first processing envelope) or a temperature level during signal processing at the DU 710. In some cases, the VRAN manager 705 may determine that more resources in the second processing envelope are allocated to the DU 710 than in the first processing envelope based on one or more power consumption values ​​in the report (e.g., if the one or more power consumption values ​​fail to meet a threshold). In some cases, the VRAN manager 705 may determine that less resources in the second processing envelope are allocated to the DU 710 than in the first processing envelope based on one or more power consumption values ​​in the report (e.g., if the one or more power consumption values ​​meet a threshold).

[0092] In one example, DU 710 may report power consumption for performing signal processing for a first RU communicating on a first number of layers, a first number of carriers, and a first BWP size for each carrier. The first number of layers, the first number of carriers, and the first BWP size for each carrier may correspond to the dimensions of the sub-envelope allocated to the first RU. DU 710 may also report power consumption for performing signal processing for a second RU communicating on a second number of layers, a second number of carriers, and a second BWP size for each carrier. The second number of layers, the second number of carriers, and the second BWP size for each carrier may correspond to the dimensions of the sub-envelope allocated to the second RU.

[0093] Thus, the VRAN manager 705 is able to determine the power consumption at the DU 710 associated with the signal processing of the RUs based on the different dimensions of the sub-envelopes at the RUs. Thus, the VRAN manager 705 can reconfigure the sub-envelopes allocated to each RU connected to the DU 710 to minimize the power consumption at the DU 710 while continuing to provide communications to one or more UEs 115. For example, the VRAN manager 705 can allocate fewer resources to a first RU and more resources to a second RU if the VRAN manager 705 determines that such a configuration can reduce the power consumption at the DU 710. The VRAN manager 705 can also reconfigure the resource envelopes allocated to the DU 710 based on the power consumption at the DU 710.

[0094] Figure 8 An example of a process flow 800 for supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is illustrated. The process flow 800 includes a VRAN manager 805, which may be a reference Figures 1 to 7 The process flow 800 also includes a DU 810, which may be a reference Figures 1 to 7 The process flow 800 also includes a RU 815, which may be a reference Figures 1 to 7 The process flow 800 may implement aspects of the wireless communication system 100, the network architecture 200, or the wireless communication system 500. For example, the process flow 800 may support efficient techniques for reconfiguring a processing envelope for signal processing at the DU 810 or RU 815 based on power consumption at the RU 815.

[0095] In the following description of process flow 800, signaling exchanged between VRAN manager 805, DU 810, and RU 815 may be exchanged in an order different from the example order shown, or operations performed by VRAN manager 805, DU 810, and RU 815 may be performed in a different order or at a different time. Some operations may also be omitted from process flow 800, and other operations may be added to process flow 800. For example, VRAN manager 805 may transmit resource configuration directly to RU 815 instead of transmitting resource configuration to RU 815 via DU 810. Similarly, RU 815 may transmit reports directly to VRAN manager 805 instead of transmitting reports to VRAN manager 805 via DU 810.

[0096] At 820, the VRAN manager 805 may transmit a first processing envelope for signal processing at the RU 815, and the RU 815 may receive the first processing envelope. The signal processing may be associated with providing communications for one or more UEs 115. At 825, the RU 815 may perform power consumption measurements to determine the amount of power consumed when performing signal processing. At 830, the RU 815 may transmit a report based on the amount of power consumed at the RU 815 during signal processing, and the VRAN manager 805 may receive the report. In some cases, the report may include power consumption values ​​for each of a plurality of values ​​along one or more dimensions supported by the first processing envelope. At 835, the VRAN manager 805 may transmit a second processing envelope for processing at the RU 815 based on the report, and the RU 815 may receive the second processing envelope.

[0097] In some cases, each of the one or more dimensions supported by the first processing envelope may include a different number of PRBs and a different power backoff. In some cases, RU 815 may also transmit in the report a resource utilization level of the first processing envelope at RU 815 (e.g., utilization of a processing resource pool corresponding to the first processing envelope) or a temperature level during signal processing at RU 815. In some cases, VRAN manager 805 may determine that more resources in the second processing envelope are allocated to RU 815 than in the first processing envelope based on one or more power consumption values ​​in the report (e.g., if one or more power consumption values ​​fail to meet a threshold). In some cases, VRAN manager 805 may determine that less resources in the second processing envelope are allocated to RU 815 than in the first processing envelope based on one or more power consumption values ​​in the report (e.g., if one or more power consumption values ​​meet a threshold).

[0098] In one example, when communicating on a first number of PRBs with a first power backoff, a first RU may report power consumption for performing signal processing. The first number of PRBs and the first power backoff may correspond to the dimensions of the sub-envelopes allocated to the first RU. Then, when communicating on a second number of PRBs with a second power backoff, a second RU may report power consumption for performing signal processing. The second number of PRBs and the second power backoff may correspond to the dimensions of the sub-envelopes allocated to the second RU. Thus, the VRAN manager 805 is able to determine power consumption at different RUs of communication based on different dimensions of the sub-envelopes at the RUs. Thus, the VRAN manager 805 may reconfigure the sub-envelopes allocated to each RU to minimize overall power consumption on all RUs or at a particular RU while continuing to provide communications to one or more UEs 115. For example, the VRAN manager 805 may allocate fewer resources to the first RU and more resources to the second RU, provided that the VRAN manager 805 determines that such a configuration can reduce power consumption on all RUs. Thus, the first RU, the second RU, or both may be configured to communicate on different numbers of PRBs using different power backoffs.

[0099] In some cases, reference Figure 8 The technology described can be compared with Figure 7 In any case, the techniques described herein may allow minimization of power consumption at one or more RUs, DUs, or both in a network.

[0100] Fig. 9 A block diagram 900 of a device 905 supporting adaptive processing envelopes based on power consumption according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0101] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0102] The transmitter 915 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0103] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the adaptive processing envelope based on power consumption as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0104] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0105] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0106] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0107] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a first network entity. For example, the communication manager 920 may be configured to or otherwise support components for receiving, from a second network entity, a first processing envelope for signal processing at the first network entity, the signal processing being associated with providing communications for a UE. The communication manager 920 may be configured to or otherwise support components for transmitting to the second network entity a report based on an amount of power consumed at the first network entity during signal processing, the report including a power consumption value for each of a set of a plurality of values ​​along one or more dimensions supported by the first processing envelope. The communication manager 920 may be configured to or otherwise support components for receiving, from the second network entity, a second processing envelope for signal processing at the first network entity, the second processing envelope being based on transmitting the report.

[0108] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. For example, the communication manager 920 may be configured to or otherwise support components for transmitting to the second network entity a first processing envelope for signal processing at the second network entity, the signal processing associated with providing communications for the UE. The communication manager 920 may be configured to or otherwise support components for receiving from the second network entity a report based on an amount of power consumed at the second network entity during signal processing, the report including power consumption values ​​for each of a set of multiple values ​​along one or more dimensions supported by the first processing envelope. The communication manager 920 may be configured to or otherwise support components for transmitting to the second network entity a second processing envelope for signal processing at the second network entity, the second processing envelope based on receiving the report.

[0109] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) can support techniques for reduced power consumption. Specifically, because a network entity can report power consumption values ​​for different allocations of baseband resource envelopes, another network entity can reconfigure the baseband resource envelopes in the network to minimize power consumption and reduce OPEX.

[0110] Fig.10 A block diagram 1000 of a device 1005 supporting adaptive processing envelopes based on power consumption according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0111] The receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0112] The transmitter 1015 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0113] The device 1005 or its various components may be examples of components for performing various aspects of the adaptive processing envelope based on power consumption as described herein. For example, the communication manager 1020 may include an envelope configuration manager 1025, a reporting manager 1030, an envelope reconfiguration manager 1035, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0114] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a first network entity. The envelope configuration manager 1025 may be configured to or otherwise support components for receiving, from a second network entity, a first processing envelope for signal processing at the first network entity, the signal processing associated with providing communications for a UE. The reporting manager 1030 may be configured to or otherwise support components for transmitting, to the second network entity, a report based on an amount of power consumed at the first network entity during signal processing, the report including a power consumption value for each of a set of a plurality of values ​​along one or more dimensions supported by the first processing envelope. The envelope reconfiguration manager 1035 may be configured to or otherwise support components for receiving, from the second network entity, a second processing envelope for signal processing at the first network entity, the second processing envelope based on transmitting the report.

[0115] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first network entity. The envelope configuration manager 1025 may be configured to or otherwise support components for transmitting to the second network entity a first processing envelope for signal processing at the second network entity, the signal processing associated with providing communications for the UE. The reporting manager 1030 may be configured to or otherwise support components for receiving from the second network entity a report based on an amount of power consumed at the second network entity during signal processing, the report including power consumption values ​​for each of a set of a plurality of values ​​along one or more dimensions supported by the first processing envelope. The envelope reconfiguration manager 1035 may be configured to or otherwise support components for transmitting to the second network entity a second processing envelope for signal processing at the second network entity, the second processing envelope based on receiving the report.

[0116] Fig.11A block diagram 1100 of a communication manager 1120 supporting an adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the adaptive processing envelope based on power consumption as described herein. For example, the communication manager 1120 may include an envelope configuration manager 1125, a reporting manager 1130, an envelope reconfiguration manager 1135, a resource manager 1140, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0117] According to examples as disclosed herein, a communication manager 1120 may support wireless communications at a first network entity. An envelope configuration manager 1125 may be configured to or otherwise support components for receiving, from a second network entity, a first processing envelope for signal processing at the first network entity, the signal processing associated with providing communications for a UE. A reporting manager 1130 may be configured to or otherwise support components for transmitting to the second network entity a report based on an amount of power consumed at the first network entity during signal processing, the report including a power consumption value for each of a set of a plurality of values ​​along one or more dimensions supported by the first processing envelope. An envelope reconfiguration manager 1135 may be configured to or otherwise support components for receiving, from the second network entity, a second processing envelope for signal processing at the first network entity, the second processing envelope based on transmitting the report.

[0118] In some examples, each of the one or more dimensions supported by the first processing envelope includes a different number of layers, a different number of carriers, a different bandwidth portion, a different power backoff, or a combination thereof.

[0119] In some examples, the first network entity includes distributed units, and the reporting manager 1130 may be configured to or otherwise support components for transmitting in a report a resource utilization level of the first processing envelope at the first network entity, a temperature level during signal processing at the first network entity, or a combination thereof for each of one or more dimensions supported by the first processing envelope.

[0120] In some examples, the size of the second processing envelope is greater than the size of the first processing envelope based on one or more power consumption values ​​in the report failing to satisfy a threshold.

[0121] In some examples, based on one or more power consumption values ​​in the report satisfying a threshold, the size of the second processing envelope is less than or equal to the size of the first processing envelope.

[0122] In some examples, the first network entity includes a distributed unit or a radio unit, and the second network entity includes a distributed unit or a host platform for a virtual radio access network entity.

[0123] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network entity. In some examples, the envelope configuration manager 1125 may be configured to or otherwise support components for transmitting to the second network entity a first processing envelope for signal processing at the second network entity, the signal processing associated with providing communications for the UE. In some examples, the reporting manager 1130 may be configured to or otherwise support components for receiving from the second network entity a report based on an amount of power consumed at the second network entity during signal processing, the report including power consumption values ​​for each of a set of multiple values ​​along one or more dimensions supported by the first processing envelope. In some examples, the envelope reconfiguration manager 1135 may be configured to or otherwise support components for transmitting to the second network entity a second processing envelope for signal processing at the second network entity, the second processing envelope based on receiving the report.

[0124] In some examples, each of the one or more dimensions supported by the first processing envelope includes a different number of layers, a different number of carriers, a different bandwidth portion, a different power backoff, or a combination thereof.

[0125] In some examples, the second network entity includes a distributed unit, and the reporting manager 1130 may be configured to or otherwise support components for receiving in a report a resource utilization level of the first processing envelope at the second network entity, a temperature level during signal processing at the second network entity, or a combination thereof for each of one or more dimensions supported by the first processing envelope.

[0126] In some examples, resource manager 1140 may be configured or otherwise support components for determining to allocate more resources in the second processing envelope than in the first processing envelope to the second network entity based on one or more power consumption values ​​in the report failing to meet a threshold.

[0127] In some examples, resource manager 1140 may be configured or otherwise support components for determining that fewer resources in the second processing envelope than in the first processing envelope are allocated to the second network entity based on one or more power consumption values ​​in the report satisfying a threshold.

[0128] In some examples, the first network entity includes a distributed unit or a host platform for a virtual radio access network entity, and the second network entity includes a distributed unit or a radio unit.

[0129] Fig.12 A diagram of a system 1200 including a device 1205 supporting an adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0130] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215 that are capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and for demodulating a signal. The transceiver 1210 or transceiver 1210 and one or more antennas 1215 or wired interfaces (where applicable) may be examples of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0131] The memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by the processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1230 may not be directly executable by the processor 1235, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1225 may also include a BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0132] The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1225) to enable the device 1205 to perform various functions (e.g., functions or tasks that support an adaptive processing envelope based on power consumption). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, and the processor 1235 and the memory 1225 are configured to perform various functions described herein. The processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions for performing functions of the device 1205 (e.g., by executing code 1230).

[0133] In some examples, bus 1240 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1205, or communications performed between different components of device 1205 that may be co-located or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of the different components or divided between the different components).

[0134] In some examples, communication manager 1220 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1220 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1220 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1220 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0135] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a first network entity. For example, the communication manager 1220 may be configured to or otherwise support components for receiving, from a second network entity, a first processing envelope for signal processing at the first network entity, the signal processing associated with providing communications for a UE. The communication manager 1220 may be configured to or otherwise support components for transmitting to the second network entity a report based on an amount of power consumed at the first network entity during signal processing, the report including a power consumption value for each of a set of a plurality of values ​​along one or more dimensions supported by the first processing envelope. The communication manager 1220 may be configured to or otherwise support components for receiving, from the second network entity, a second processing envelope for signal processing at the first network entity, the second processing envelope based on transmitting the report.

[0136] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at the first network entity. For example, the communication manager 1220 may be configured to or otherwise support components for transmitting to the second network entity a first processing envelope for signal processing at the second network entity, the signal processing associated with providing communications for the UE. The communication manager 1220 may be configured to or otherwise support components for receiving from the second network entity a report based on an amount of power consumed at the second network entity during signal processing, the report including power consumption values ​​for each of a set of multiple values ​​along one or more dimensions supported by the first processing envelope. The communication manager 1220 may be configured to or otherwise support components for transmitting to the second network entity a second processing envelope for signal processing at the second network entity, the second processing envelope based on receiving the report.

[0137] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 can support techniques for reduced power consumption. Specifically, because a network entity can report power consumption values ​​for different allocations of baseband resource envelopes, another network entity can reconfigure the baseband resource envelopes in the network to minimize power consumption and reduce OPEX.

[0138] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1235, the memory 1225, the code 1230, the transceiver 1210, or any combination thereof. For example, the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform various aspects of the adaptive processing envelope based on power consumption as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0139] Fig.13 1 is a flowchart illustrating a method 1300 for supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 12 The network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0140] At 1305, the method may include receiving, from a second network entity, a first processing envelope for signal processing at a first network entity, the signal processing associated with providing communications for a UE. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig.11 The envelope configuration manager 1125 executes.

[0141] At 1310, the method may include transmitting to the second network entity a report based on the amount of power consumed at the first network entity during signal processing, the report including power consumption values ​​for each of a set of a plurality of values ​​along one or more dimensions supported by the first processing envelope. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Fig.11 The report manager 1130 executes.

[0142] At 1315, the method may include receiving, from the second network entity, a second processing envelope for signal processing at the first network entity, the second processing envelope being based on the transmission report. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Fig.11 The envelope reconfiguration manager 1135 executes.

[0143] Fig.14 A flowchart illustrating a method 1400 for supporting adaptive processing envelope based on power consumption according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 12 The network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0144] At 1405, the method may include transmitting to a second network entity a first processing envelope for signal processing at the second network entity, the signal processing associated with providing communications for the UE. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.11 The envelope configuration manager 1125 executes.

[0145] At 1410, the method may include receiving, from the second network entity, a report based on an amount of power consumed at the second network entity during signal processing, the report including power consumption values ​​for each of a set of a plurality of values ​​along one or more dimensions supported by the first processing envelope. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig.11 The report manager 1130 executes.

[0146] At 1415, the method may include transmitting to the second network entity a second processing envelope for signal processing at the second network entity, the second processing envelope based on the reception report. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Fig.11 The envelope reconfiguration manager 1135 executes.

[0147] (The inventive content supporting multiple dependent claims will be added after the claims are finally approved)

[0148] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0149] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0150] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0151] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0152] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0153] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0154] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so 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). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0155] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0156] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0157] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0158] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a second network entity, a first processing envelope for signal processing at the first network entity, the signal processing associated with providing communications for a user equipment (UE); transmitting to a second network entity a report based at least in part on an amount of power consumed at the first network entity during signal processing, the report comprising power consumption values ​​for each of a plurality of values ​​along one or more dimensions supported by the first processing envelope; as well as A second processing envelope for the signal processing at the first network entity is received from the second network entity, the second processing envelope being based at least in part on transmitting the report.

2. The apparatus of claim 1, wherein each of the one or more dimensions supported by the first processing envelope comprises a different number of layers, a different number of carriers, a different bandwidth portion, a different power backoff, or a combination thereof.

3. The apparatus of claim 1 , wherein the first network entity comprises a distributed unit, and the instructions are further executable by the processor to cause the apparatus to: For each of the one or more dimensions supported by the first processing envelope, a resource utilization level of the first processing envelope at the first network entity, a temperature level during signal processing at the first network entity, or a combination thereof is transmitted in the report. 4 . The apparatus of claim 1 , wherein the size of the second processing envelope is greater than the size of the first processing envelope based at least in part on one or more power consumption values ​​in the report failing to satisfy a threshold. 5 . The apparatus of claim 1 , wherein the size of the second processing envelope is less than or equal to the size of the first processing envelope based at least in part on one or more power consumption values ​​in the report satisfying a threshold.

6. The apparatus of claim 1, wherein the first network entity comprises a distributed unit or a radio unit, and the second network entity comprises a distributed unit or a host platform for a virtual radio access network entity.

7. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting, to a second network entity, a first processing envelope for signal processing at the second network entity, the signal processing associated with providing communications for a user equipment (UE); receiving, from the second network entity, a report based at least in part on an amount of power consumed at the second network entity during signal processing, the report comprising power consumption values ​​for each of a plurality of values ​​along one or more dimensions supported by the first processing envelope; as well as A second processing envelope for the signal processing at the second network entity is transmitted to the second network entity, the second processing envelope being based at least in part on receiving the report.

8. The apparatus of claim 7, wherein each of the one or more dimensions supported by the first processing envelope comprises a different number of layers, a different number of carriers, a different bandwidth portion, a different power backoff, or a combination thereof.

9. The apparatus of claim 7, wherein the second network entity comprises a distributed unit, and the instructions are further executable by the processor to cause the apparatus to: For each of the one or more dimensions supported by the first processing envelope, a resource utilization level of the first processing envelope at the second network entity, a temperature level during signal processing at the second network entity, or a combination thereof is received in the report.

10. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on one or more power consumption values ​​in the report failing to satisfy a threshold, determining to allocate more resources in the second processing envelope than in the first processing envelope to the second network entity.

11. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on one or more power consumption values ​​in the report satisfying a threshold, determining to allocate fewer resources in the second processing envelope than in the first processing envelope to the second network entity.

12. The apparatus of claim 7, wherein the first network entity comprises a distributed unit or a host platform for a virtual radio access network entity, and the second network entity comprises a distributed unit or a radio unit.

13. A method for wireless communication at a first network entity, the method comprising: receiving, from a second network entity, a first processing envelope for signal processing at the first network entity, the signal processing associated with providing communications for a user equipment (UE); transmitting to a second network entity a report based at least in part on an amount of power consumed at the first network entity during signal processing, the report comprising power consumption values ​​for each of a plurality of values ​​along one or more dimensions supported by the first processing envelope; as well as A second processing envelope for the signal processing at the first network entity is received from the second network entity, the second processing envelope being based at least in part on transmitting the report.

14. The method of claim 13, wherein each of the one or more dimensions supported by the first processing envelope comprises a different number of layers, a different number of carriers, a different bandwidth portion, a different power backoff, or a combination thereof.

15. The method of claim 13, wherein the first network entity comprises a distributed unit, the method further comprising: For each of the one or more dimensions supported by the first processing envelope, a resource utilization level of the first processing envelope at the first network entity, a temperature level during signal processing at the first network entity, or a combination thereof is transmitted in the report.

16. The method of claim 13, wherein the size of the second processing envelope is greater than the size of the first processing envelope based at least in part on one or more power consumption values ​​in the report failing to satisfy a threshold.

17. The method of claim 13, wherein the size of the second processing envelope is less than or equal to the size of the first processing envelope based at least in part on one or more power consumption values ​​in the report satisfying a threshold.

18. The method of claim 13, wherein the first network entity comprises a distributed unit or a radio unit, and the second network entity comprises a distributed unit or a host platform for a virtual radio access network entity.

19. A method for wireless communication at a first network entity, the method comprising: transmitting, to a second network entity, a first processing envelope for signal processing at the second network entity, the signal processing associated with providing communications for a user equipment (UE); receiving, from the second network entity, a report based at least in part on an amount of power consumed at the second network entity during signal processing, the report comprising power consumption values ​​for each of a plurality of values ​​along one or more dimensions supported by the first processing envelope; as well as A second processing envelope for the signal processing at the second network entity is transmitted to the second network entity, the second processing envelope being based at least in part on receiving the report.

20. The method of claim 19, wherein each of the one or more dimensions supported by the first processing envelope comprises a different number of layers, a different number of carriers, a different bandwidth portion, a different power backoff, or a combination thereof.

21. The method of claim 19, wherein the second network entity comprises a distributed unit, the method further comprising: For each of the one or more dimensions supported by the first processing envelope, a resource utilization level of the first processing envelope at the second network entity, a temperature level during signal processing at the second network entity, or a combination thereof is received in the report.

22. The method according to claim 19, further comprising: Based at least in part on one or more power consumption values ​​in the report failing to satisfy a threshold, determining to allocate more resources in the second processing envelope than in the first processing envelope to the second network entity.

23. The method according to claim 19, further comprising: Based at least in part on one or more power consumption values ​​in the report satisfying a threshold, determining to allocate fewer resources in the second processing envelope than in the first processing envelope to the second network entity.

24. The method of claim 19, wherein the first network entity comprises a distributed unit or a host platform for a virtual radio access network entity, and the second network entity comprises a distributed unit or a radio unit.

Images