Preemptive buffer status report extension for network power savings

Abstract

Methods, systems, and devices for wireless communication are described. A first device (e.g., an integrated access and backhaul (IAB) node) may obtain one or more messages from one or more second devices (e.g., user equipment (UE), child nodes) in communication with the first device that trigger the first device to generate a buffer status report (BSR). The first device may output the BSR in BSR messages to a parent device, wherein the BSR may indicate one or more times of arrival associated with expected traffic for the second devices based on the messages. Upon obtaining the BSR message, the parent device may activate a sleep mode for one or more components associated with the parent device based on the times of arrival indicated in the BSR. For example, in cases where the arrival times are relatively long, the parent device may activate a sleep mode to increase power savings.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 826,078, entitled “PRE-EMPTIVE BUFFER STATUS REPORT EXTENSION FOR NETWORK POWER SAVING,” filed by Khalfi et al. on May 26, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference.

[0003] introduction

[0004] The following relates to wireless communications, and more particularly to network power conservation.

[0005] 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). 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). Summary of the invention

[0006] A method is described. The method may include: obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering generation of a first BSR by the first device; and outputting a BSR message including the first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based on the one or more messages.

[0007] An apparatus is described. The apparatus may include: a processor and a memory coupled to the processor, the processor being configured to obtain one or more messages from one or more second devices in communication with the first device, the one or more messages triggering generation of a first BSR by the first device; and outputting a BSR message including the first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based on the one or more messages.

[0008] Another apparatus is described. The apparatus may include: means for obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering generation of a first BSR by the first device; and means for outputting a BSR message including the first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based on the one or more messages.

[0009] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to perform the following operations: obtain one or more messages from one or more second devices in communication with the first device, the one or more messages triggering the generation of a first BSR by the first device; and output a BSR message including the first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based on the one or more messages.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: outputting the BSR message including the first BSR and the second BSR, wherein a first group of one or more bits of the BSR message may be used for the first BSR, and a second group of one or more bits of the BSR message may be used for the second BSR, the second BSR indicating one or more arrival times associated with current services of the one or more second devices.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: obtaining the one or more messages from the one or more second devices, the one or more messages including one or more second BSRs that trigger generation of the first BSR by the first device.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining one or more messages indicating a periodicity for generating the first BSR, wherein the BSR message may be output according to the periodicity.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: obtaining the one or more messages from a parent device of the first device, the one or more messages triggering generation of the first BSR by the first device, wherein the one or more second devices include the parent device.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: obtaining the one or more messages from the one or more second devices, the one or more messages indicating that a sleep mode has been activated for one or more components associated with the one or more second devices, the sleep mode triggering generation of the first BSR by the first device.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing an indication of a first average arrival time associated with expected traffic for one or more second devices of a first type and a second average arrival time associated with the expected traffic for one or more second devices of a second type to be included within the first BSR.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing an indication of an average arrival time associated with the expected traffic for the one or more second devices to include within the first BSR, wherein the one or more second devices may be of the first type or of the second type.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing an indication of a minimum arrival time associated with the expected traffic of the one or more second devices to include within the first BSR.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing an indication of a priority associated with each of the one or more second devices for inclusion in the first BSR.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for outputting the BSR message at a time determined based on the one or more arrival times.

[0020] A method for wireless communication at a first device in a wireless network is described. The method may include: obtaining a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device; and activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0021] An apparatus for wireless communication at a first device in a wireless network is described. The apparatus may include a processor and a memory coupled to the processor, the processor being configured to: obtain a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices communicating with the second device; and activate a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0022] Another apparatus for wireless communication at a first device in a wireless network is described. The apparatus may include: means for obtaining a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device; and means for activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0023] A non-transitory computer-readable medium storing code for wireless communication at a first device in a wireless network is described. The code may include instructions executable by a processor to: obtain a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device; and activate a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: obtaining the BSR message including the first BSR and the second BSR, wherein a first group of one or more bits of the BSR message may be used for the first BSR, and a second group of one or more bits of the BSR message may be used for the second BSR, the second BSR indicating one or more arrival times associated with current services of the one or more third devices.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting one or more messages to the second device, the one or more messages triggering generation of the first BSR by the second device.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining, within the first BSR, an indication of a first average arrival time associated with the expected traffic for one or more third devices of the first type and a second average arrival time associated with the expected traffic for one or more third devices of the second type.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining, within the first BSR, an indication of an average arrival time associated with the expected traffic for the one or more third devices, wherein the one or more third devices may be of the first type or of the second type.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for obtaining, within the first BSR, an indication of a minimum arrival time associated with the expected traffic for the one or more third devices.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for obtaining, within the first BSR, an indication of a priority associated with each of the one or more third devices.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for activating the sleep mode for the one or more components associated with the first device based on obtaining the BSR message at a determined time, the time being determined based on the one or more arrival times. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 An example of a wireless communication system supporting preemptive BSR extension for network power conservation in accordance with one or more aspects of the present disclosure is illustrated.

[0032] Figure 2 An example of a network architecture supporting preemptive BSR extension for network power conservation in accordance with one or more aspects of the present disclosure is illustrated.

[0033] Figure 3An example of a wireless communication system supporting preemptive BSR extension for network power conservation in accordance with one or more aspects of the present disclosure is illustrated.

[0034] Figure 4A An example of a timeline supporting preemptive BSR extension for network power conservation in accordance with one or more aspects of the present disclosure is illustrated.

[0035] Figure 4B An example of a wireless communication system supporting preemptive BSR extension for network power conservation in accordance with one or more aspects of the present disclosure is illustrated.

[0036] Figure 5 An example of a process flow supporting preemptive BSR extension for network power conservation in accordance with one or more aspects of the present disclosure is illustrated.

[0037] Figure 6 and Figure 7 A block diagram of a device supporting preemptive BSR extension for network power conservation is shown in accordance with one or more aspects of the present disclosure.

[0038] Figure 8 A block diagram of a communications manager supporting preemptive BSR extensions for network power conservation is shown in accordance with one or more aspects of the present disclosure.

[0039] Fig. 9 A diagram of a system including a device supporting preemptive BSR extension for network power conservation is shown in accordance with one or more aspects of the present disclosure.

[0040] Fig.10 and Fig.11 A block diagram of a device supporting preemptive BSR extension for network power conservation is shown in accordance with one or more aspects of the present disclosure.

[0041] Fig.12 A block diagram of a communications manager supporting preemptive BSR extensions for network power conservation is shown in accordance with one or more aspects of the present disclosure.

[0042] Fig.13 A diagram of a system including a device supporting preemptive BSR extension for network power conservation is shown in accordance with one or more aspects of the present disclosure.

[0043] Figures 14 to 19 A flow chart illustrating a method of supporting preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0044] In some examples, a wireless device (which may also be referred to as an integrated access and backhaul (IAB) node) may assist a parent device (e.g., a parent IAB node) communicating with the wireless device to activate or deactivate different sleep modes for one or more components or functionalities of the parent device to save power and maintain operations in a wireless communication system. The one or more components may include a central unit (CU), a radio unit (RU), a distributed unit (DU), a mobile termination (MT) antenna, and other physical components of the parent device, and the functionality may include transmission power, operation or communication bandwidth, etc. The sleep mode may be a time period during which the parent device may deactivate or reduce the functionality of one or more components of the parent device. In some cases, the time period may be based on a transition time of a component (e.g., a time for activating or deactivating the one or more components or functionality). The parent device may consume different amounts of power when activating or deactivating a component, and therefore, the parent device may select a sleep mode to activate for the one or more components based on how much power can be saved and the transition time of one or more components.

[0045] In some examples, the parent device may enter a shallow sleep mode corresponding to some power savings and a relatively short transition time between the shallow sleep mode and an active or wake-up mode (e.g., an operating mode in which all components of the parent device are activated and operable). During the shallow sleep mode, the parent device may limit or deactivate at least some functionality of one or more components of the parent device. Alternatively, the parent device may enter a deep sleep mode, which may correspond to higher power savings compared to the shallow sleep mode. In the deep sleep mode, the parent device may limit or deactivate more functionality of one or more components of the parent device than in the shallow sleep mode. For example, the parent device may completely deactivate the MT antenna in the deep sleep mode. According to one or more examples, the transition time between the deep sleep mode and the active or wake-up mode may be longer than the transition time of the shallow sleep mode. For example, the parent device may deactivate additional components or more complex components or functionality for the deep sleep mode compared to the shallow sleep mode. Therefore, the transition time of the deep sleep mode may be longer than the transition time of the light sleep mode because the time for deactivating (or activating) a component or functionality in the deep sleep mode may be longer than the time for deactivating (or activating) a component in the light sleep mode.

[0046] In some examples, the parent device may enter or activate a given sleep mode to achieve increased power savings by knowing the traffic conditions or expected communications (e.g., uplink transmissions) from one or more second devices (e.g., one or more UEs, one or more child IAB nodes) communicating with the wireless device or expected communications between second devices (e.g., sidelink transmissions between UEs). As described herein, traffic may refer to the number of uplink transmissions communicated to the wireless device from one or more second devices (e.g., UEs, child IAB nodes, or both) or the number of sidelink transmissions communicated between two or more UEs.

[0047] However, if the parent device (e.g., the parent IAB node) of the wireless device is unaware of the traffic conditions of the second device (e.g., the UE and the child IAB node communicating with the wireless device) communicating with the wireless device, the parent device may activate the sleep mode in an inefficient manner, resulting in increased power consumption or failed transmission. For example, the parent device may activate the inefficient sleep mode by activating the shallow sleep mode, wherein the deep sleep mode can save more power. Alternatively, the parent device may activate the inefficient sleep mode by activating a given sleep mode at a later time than when the parent device has information related to the traffic conditions at one or more second devices. For example, the parent device can save more power in the deep sleep mode than in the shallow sleep mode, but the parent device may use a longer transition time to enter the deep sleep mode, during which the parent device may not be able to perform communication (or other functions) with one or more wireless devices.

[0048] Additionally or alternatively, if the parent device enters deep sleep mode without knowing the traffic load of a second device (e.g., a UE, a child IAB node, or both) communicating with the wireless device, the parent device may miss or lose transmissions from the wireless device. In some cases, the parent device may activate a shallow sleep mode based on a scenario where the parent device receives a small amount of transmissions from one or more second devices (e.g., a light traffic condition corresponding to a traffic volume below a threshold). However, due to the light traffic condition, the parent device may save additional power if the parent device has activated the deep sleep mode. Therefore, knowing the traffic condition of the second device communicating with the wireless device can assist the parent device in determining to enter a deeper sleep mode to increase power savings.

[0049] As described herein, a wireless device (e.g., an IAB node) may output an extended preemptive BSR to a parent device (e.g., a parent IAB node), wherein the extended preemptive BSR may assist the parent device in activating a sleep mode for one or more of its components (e.g., MT antenna, CU, DU, RU). In some examples, the wireless device may obtain one or more messages from one or more second devices communicating with the wireless device (e.g., a UE, a child IAB node), a parent device, or a combination thereof. The one or more messages may trigger the wireless device to generate a BSR (e.g., an extended preemptive BSR) to be output to the parent device. For example, the one or more messages may include a BSR from a second device, or the one or more messages may include a trigger from a parent device, which may be a message indicating that the wireless device will generate a BSR, and so on.

[0050] The wireless device may generate a BSR, which may indicate an arrival time associated with an expected service (e.g., uplink communication) to be sent from one or more second devices to the wireless device. For example, the BSR may indicate a specific time (e.g., minimum time, average time) at which some data is to be received from one or more second devices at the wireless device. The parent device may obtain a BSR message including the generated BSR from the wireless device. Based on the arrival time indicated in the BSR, the parent device may activate a sleep mode for one or more components of the parent device (e.g., MT antenna, CU, DU, RU). For example, if the arrival time is relatively long, indicating a sparse traffic condition, the parent device may enter a deep sleep mode and shut down the functionality of some components, which may increase power savings. In addition, activating a sleep mode based on the arrival time may prevent dropped communications and improve the efficiency of the transition time between sleep mode and active or wake-up mode for the components of the parent device.

[0051] Various aspects of the disclosure are first described in the context of a wireless communication system. Various aspects of the disclosure are then described in the context of a network architecture and process flow. Various aspects of the disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to preemptive BSR extensions for network power conservation.

[0052] Figure 1 An example of a wireless communication system 100 supporting preemptive BSR extension for network power saving 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.

[0053] 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), over 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 over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0054] 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.

[0055] As described herein, a node, which may be referred to as a node, a network node, a network entity, or a wireless node, may be a network entity 105 (e.g., any network entity 105 described herein), a UE 115 (e.g., any UE 115 described herein), a network controller, an apparatus, a device, a computing system, one or more components, and / or another suitable processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE 115. As another example, the network node may be a network entity 105. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE 115, the second network node may be a network entity 105, and the third network node may be a UE 115. In another aspect of this example, the first network node may be a UE 115, the second network node may be a network entity 105, and the third network node may be a network entity 105. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different with respect to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure that UE 115, network entity 105, apparatus, device, computing system, etc. are network 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. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first network node is configured to receive information from the second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., UE 115 is configured to receive information from network entity 105 also discloses that the first network node is configured to receive information from the second network node), the broader example of the narrower example may be interpreted inversely, but in a broad, open-ended manner. In the above example in which the UE 115 configured to receive information from the network entity also discloses that the first network node is configured to receive information from the second network node, the first network node may refer to a first UE 115 configured to receive information, a first network entity 105, a first device, a first equipment, a first computing system, a first one or more components, a first processing entity, etc.; and the second network node may refer to a second UE 115, a second network entity 105, a second device, a second equipment, a second computing system, a first one or more components, a first processing entity, etc.

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

[0057] In some examples, the network entities 105 may communicate with the core network 130, or 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 links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 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 links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 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 .

[0058] 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 terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a clustered (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0059] 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 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 CU 160, a DU 165, a 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) system 180, 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)).

[0060] 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, 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 DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the 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 according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0061] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB-MT controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such a case, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0062] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).

[0063] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115 .

[0064] For example, the IAB node 104 may be referred to as a parent node supporting child IAB node communications and as a child node associated with the IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, and may directly signal the transmissions to the UE 115. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0065] In the case where the techniques described herein are applied to the environment of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the preemptive BSR extension for network power saving as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may be additionally or alternatively performed by one or more components of the disaggregated RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0066] 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.

[0067] 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.

[0068] The UE 115 and the network entity 105 may communicate wirelessly 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 defined physical layer structure to support the communication link 125. For example, a carrier for the 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 the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with 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 those 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 that communicates with another device (e.g., directly or via one or more other network entities 105).

[0069] 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 a "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 for 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). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on 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.

[0070] The signal waveform transmitted by the carrier may include 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 one symbol period (e.g., the duration of one modulation symbol) and one 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, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0071] One or more numerologies of carriers may be supported, where the numerologies may include subcarrier spacing ( ) 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.

[0072] 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. seconds, of which 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 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).

[0073] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a 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 code periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into a plurality of mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., Nf The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0074] A subframe, slot, mini-slot, or 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 number 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)).

[0075] Physical channels may be multiplexed on a carrier according to various techniques. For example, a physical control channel and a physical data channel may be multiplexed on a downlink carrier using 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 or a subset of a system bandwidth of a carrier. 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 the 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 the control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the 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 .

[0076] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0077] A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 115 through a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0078] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0079] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and, therefore, 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 various coverage areas 110 using the same or different radio access technologies.

[0080] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0081] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed with a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0082] 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). The UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communications may include private communications or group communications 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 are used interchangeably herein.

[0083] 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 communications 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 communications 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 communications 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 communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0084] 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 stratum (NAS) functions such as mobility, authentication, and bearer management of a 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 an IP service 150 for 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.

[0085] 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). The region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features that may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0086] 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 the 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, a RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. 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 techniques disclosed herein may be employed 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.

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

[0088] The electromagnetic spectrum is often subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles, even though a portion of FR1 is greater than 6 GHz. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, even though it is different from the EHF band (30 GHz–300 GHz) which is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0090] The network entity 105 or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 140 or the UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit beamforming or receive beamforming. For example, one or more network entity 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, the base station 140, or both may have antenna arrays having antenna ports of several rows and columns that the network entity 105, the base station 140, or both may 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 radio frequency beamforming for signals sent via the antenna ports.

[0091] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, 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 can 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 set of 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 can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0092] 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 communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated 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).

[0093] 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 to 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 for a radio bearer that supports user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, transport channels may be mapped to physical channels.

[0094] Some wireless communication systems 100 may include wireless devices, such as IAB nodes 104 and network entities 105, that support power saving in, for example, 5G wireless communications and massive MIMO systems (e.g., green networks). In some examples, wireless devices may utilize different sleep modes (e.g., light sleep mode, deep sleep mode) and operations to save power and maintain network operations. For example, a wireless device may turn off or reduce some capabilities or components when in a particular sleep mode to save power. Therefore, a wireless device may enter different sleep modes depending on the capabilities that the wireless device turns off. In some cases, a wireless device may enter a sleep mode, such as a micro sleep mode, a light sleep mode, a deep sleep mode, or a full sleep mode, wherein the closer a particular sleep mode is to a full sleep mode, the lower the power consumption of the wireless device.

[0095] In some examples, the sleep modes may differ in operation. For example, in some sleep modes, the wireless device may turn off the radio frequency chain. In addition, different sleep modes may result in different power consumption and different transition times for the wireless device to transition from a specific power consumption (e.g., an active or awake mode in conventional operation) to a specific sleep mode. For example, in a shallow sleep mode, the IAB node 104 or the network entity 105 may turn off some antennas and other features at the RU 170 so that the power consumption of the corresponding IAB node 104 or the network entity 105 may be transferred into and out of the shallow sleep mode in a relatively short transition time relative to the active or awake mode. In a deep sleep mode, the IAB node 104 or the network entity 105 may turn off more capabilities compared to a shallow sleep mode, and therefore, the corresponding wireless device may save relatively more power, but may use a longer transition time relative to the active or awake mode to enter and exit the deep sleep mode.

[0096] Whether the wireless device enters a shallower sleep mode or a deeper sleep mode may depend on the traffic associated with one or more second wireless devices (e.g., child IAB nodes, UE 115) that communicate with or are supported by the wireless device. The traffic may include a certain number of uplink transmissions scheduled for transmission to the wireless device. For example, if the IAB node 104 is communicating with a plurality of UEs 115 and child IAB nodes with a heavier traffic load (e.g., the number of uplink transmissions is higher than a threshold traffic volume), the parent IAB node (e.g., parent device) communicating with the IAB node 104 may avoid activating any sleep mode for one or more of its components. In some other examples, if the IAB node 104 is communicating with a small number of UEs 115 and child IAB nodes with a lighter traffic load (e.g., the number of uplink transmissions is lower than a threshold traffic volume), the parent IAB node communicating with the IAB node 104 may enter a shallow sleep mode. If the IAB node 104 does not schedule or expect communication with any UE 115 or child IAB node, the parent IAB node may enter a deep sleep mode or a full sleep mode (e.g., one or more components of the parent IAB node may be completely shut down). Thus, the wireless device may enter a given sleep mode based on the number of UEs 115, child IAB nodes, or both communicating with the wireless device, or the traffic or network load (e.g., the number of uplink communications) corresponding to the UE 115, child IAB nodes, or both (e.g., the number of uplink communications) (e.g., the UE 115 may have a higher traffic load at noon than at midnight), as well as other factors.

[0097] The wireless communication system 100 may support an extended preemptive BSR that may assist an IAB parent node (e.g., a parent device) in activating a sleep mode for one or more of its components. In some examples, the IAB node 104, the network entity 105, or the base station 140 may include a communication manager 101 that is configured to obtain one or more messages from one or more child IAB nodes, one or more UEs, or a parent IAB node that communicates with the IAB node 104. The one or more messages may trigger the IAB node 104 to generate a BSR (e.g., an extended preemptive BSR) for output to the parent IAB node. For example, the one or more messages may include a BSR from a child IAB node or UE 115, or the one or more messages may include a trigger from a parent IAB node, and so on.

[0098] The IAB node 104 may generate a BSR that may indicate an arrival time associated with an expected service (e.g., uplink communication) to be sent from one or more child IAB nodes, UE 115, or both to the IAB node 104. For example, the BSR may indicate a specific time (e.g., minimum time, average time) at which some transmissions are to be received from one or more child IAB nodes, UE 115, or both at the IAB node 104. The parent IAB node may include a communication manager 102 that is configured to obtain a BSR message including the generated BSR from the IAB node 104. Based on the arrival time indicated in the BSR, the parent IAB node may activate a sleep mode for one or more components (e.g., CU 160, DU 165, RU 170) of the parent IAB node. For example, if the arrival time is relatively long, thereby indicating a sparse traffic situation, the parent IAB node may enter a deep sleep mode and shut down the functionality of some components, which may increase power savings. Additionally, activating a sleep mode based on arrival time may prevent dropped communications and improve efficiency of transition times between sleep mode and active or awake mode for components of the parent IAB node.

[0099] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting preemptive BSR extension for network power saving 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 corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 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, the UEs 115-a may be served by multiple RUs 170-a simultaneously.

[0100] Each of the network entities 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, these network entities 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, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals over a wireless transmission medium, or to send signals over a wireless transmission medium to one or more of the other network entities 105, or both.

[0101] 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 handle 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.

[0102] 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.

[0103] 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 such an architecture, the 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 the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0104] 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 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.

[0105] The non-RT RIC 175-a may be configured to include logic functions that enable 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 or in communication 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 enable 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).

[0106] 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 in 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).

[0107] The network architecture 200 supports a technique for a wireless device (e.g., an IAB node) to send a BSR (e.g., an extended preemptive BSR) to a parent device (e.g., a parent IAB node) to assist the parent device in activating a sleep mode for one or more of its components. In some examples, a component of a wireless device (e.g., RU 170-a) may obtain one or more messages from one or more second devices (e.g., a child IAB node, one or more UE 115-a, or a parent device) communicating with the device. The one or more messages may trigger the wireless device to generate a BSR for output to the parent device. For example, the one or more messages may include a BSR from a child IAB node or UE 115-a, or the one or more messages may include a trigger from a parent device, and so on.

[0108] A component of a wireless device (e.g., DU 165) may generate a BSR that may indicate an arrival time associated with an expected service (e.g., uplink communication) to be sent from one or a second device to the wireless device. For example, the BSR may indicate a specific time (e.g., minimum time, average time) to receive some uplink transmissions from one or more child IAB nodes, UE 115-a, or both at the wireless device. The parent device may obtain a BSR message including the generated BSR from the wireless device. Based on the arrival time indicated in the BSR, the parent device may activate a sleep mode for one or more of its components (such as CU 160-a, DU165-a, RU 170-a, MT antenna, or any other component of the parent device). For example, if the arrival time is relatively long, thereby indicating a sparse traffic condition, the parent device may activate a deep sleep mode and turn off the functionality of DU 165-a, which may increase power savings. In addition, activating a sleep mode based on the arrival time may prevent dropped communications and improve the efficiency of the transition time between sleep mode and active or wake-up mode for the components of the parent device.

[0109] Figure 3 An example of a wireless communication system 300 supporting preemptive BSR extension for network power saving according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 may implement aspects of the wireless communication system 100 and the network architecture 200, or may be implemented by aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 300 may include a device 305 and a parent device 310, which may be examples of an IAB node and a parent IAB node as described herein, respectively. In addition, the wireless communication system 300 may include a UE 315-a, a UE 315-b, and a device 320 (e.g., a child IAB node) communicating with the device 305, which may be examples of corresponding devices as described herein. The device 305, the parent device 310, and the device 320 may each include an MT antenna 365, a DU 370, a CU, a RU, or other components in a decomposed RAN architecture, where these components may be co-located or located in a distributed location (e.g., a separate physical location). For example, device 305 may include MT antenna 365-a and DU 370-a, parent device 310 may include MT antenna 365-b and DU 370-b, and device 320 may include MT antenna 365-c and DU 370-c, wherein device 320 may communicate with device 305 via the corresponding MT antenna 365, and device 305 may communicate with parent device 310.

[0110] Device 305 (eg, first device) may communicate with parent device 310 via corresponding communication links 325, which may be as described in reference to Figure 1 In addition, the device 305 can communicate with the UE 315-a, UE 315-b, and the device 320 (e.g., one or more second devices) which can be a sub-IAB node via corresponding communication links 330, which can be as described in reference Figure 1 An example of the communication link 125 described above. UE 315-a and UE 315-b may be a first type of device (e.g., UE 315), and device 320 may be a second type of device different from the first type (e.g., a child IAB node). In some examples, device 305 may communicate with device 320 by communicating signaling between MT antenna 365-a and MT antenna 365-c. In addition, device 305 may communicate signaling with UE 315 via MT antenna 365-a. In some cases, device 305 may communicate with parent device 310 by communicating signaling between MT antenna 365-a and MT antenna 365-b. Device 305 may include DU 370-b and other components for communicating with parent device 310, UE 315, and device 320.

[0111] To increase power savings in the wireless communication system 300, the device 305 may utilize a preemptive BSR extension to assist the parent device 310 in activating a sleep mode for one or more components (e.g., MT antenna 365-b, DU 370-b) of the parent device 310 based on the traffic conditions of the UE 315 and the device 320. That is, the device 305 may send an extended preemptive BSR to the parent device 310, wherein the extended preemptive BSR may include information about the amount of traffic (e.g., the number of uplink transmissions) expected to arrive at the device 305 from the UE 315, the device 320, or any combination thereof.

[0112] In some cases, the device 305 may obtain one or more messages 335 from the UE 315-a, the UE 315-b, the device 320, or any other UE 315 or sub-device in communication with the device 305. The message 335 may trigger the device 305 to generate a first BSR 340 (e.g., an extended preemptive BSR). In some cases, the message 335 may include an additional BSR or an extended BSR reported from the UE 315 or device 320. For example, the UE 315 or device 320 may send an additional BSR indicating current traffic conditions associated with the sender device or an extended BSR indicating future traffic conditions associated with the sender device to the device 305, wherein the additional BSR or the extended BSR may trigger the device 305 to generate the first BSR 340.

[0113] Alternatively, one or more messages 335 sent from the UE 315, the device 320, or any combination thereof may indicate that a sleep mode has been activated for one or more components associated with the UE 315, the device 320, or any combination thereof, which may trigger the device 305 to generate the first BSR 340. For example, the UE 315-a may send one or more messages 335 to the device 305 indicating that the UE 315-a may not expect any traffic for the next hour. Additionally, the UE 315-b and the device 320 may send one or more messages 335 to the device 305 indicating that the UE 315-b and the device 320 may not expect any traffic for the next hour. Based on receiving message 335 from UE 315-a, UE 315-b and device 320, device 305 may generate a first BSR 340, which may trigger parent device 310 to activate sleep mode for one or more of its components in the next hour until expected traffic 355 from UE 315 and device 320 arrives at device 305.

[0114] In some cases, the one or more messages 335 may include an RRC configuration indicating a periodicity for generating the first BSR 340. Thus, the device 305 may generate the first BSR 340 according to the periodicity. Additionally or alternatively, the device 305 may receive one or more messages 335 from the parent device 310 via the communication link 325, the one or more messages 335 triggering the device 305 to generate the first BSR 340.

[0115] After receiving the one or more messages 335, the device 305 may generate a first BSR 340, wherein the first BSR 340 may indicate one or more arrival times 350 associated with expected traffic 355 from the UE 315-a, the UE 315-b, the device 320, or any combination thereof based on the message 335. The arrival time 350 may be the time at which the traffic 355 sent by the UE 315-a, the UE 315-b, or the device 320 is received at the device 305 (e.g., at the MT antenna 365-b). Since the device 305 may be connected to multiple UEs 315 and devices 320 (e.g., child IAB nodes), the respective arrival times 350 of the expected traffic 355 may be different for each UE 315 and device 320. For example, expected traffic 355 associated with device 320 may have an arrival time 350-a that may be later than or earlier than the arrival time 350 of expected traffic 355 associated with UE 315-a and UE 315-b. Figure 4A Additional information regarding arrival times 350 of expected traffic 355 from UE 315 - a , UE 315 - b , and device 320 is depicted.

[0116] In some examples, the device 305 may include in the first BSR 340 an indication of the arrival time 350 of the expected traffic 355 corresponding to the UE 315-a, UE 305-b, device 320, or a combination thereof (e.g., each UE 315, a child IAB node, or a connection node connected to the device 315). The expected traffic 355 may include uplink communications from the UE 315-a, UE 315-b, device 320, or any combination thereof to the device 305, sidelink communications between UEs 315, or both. In some examples, the device 305 may include a separate indication of the arrival time 350 in the first BSR 340 corresponding to each individual UE 315 or device 320. Alternatively, the indication of the arrival time 350 in the first BSR 340 may include an indication of the average arrival time 350 of the expected traffic 355 for a particular type of device. For example, the device 305 may include a first indication of an average arrival time 350 of expected traffic 355 for the UE 315 (e.g., a first type of device, UE 315) and a second indication of an average arrival time 350 of expected traffic 355 for the device 320 and any other connected sub-IAB nodes (e.g., a second type of device, sub-IAB nodes). In some examples, the average arrival time 350 may be different for each type of device.

[0117] In some cases, the device 305 may include an indication of an average arrival time 350 of expected traffic 355 associated with all devices of the first type and the second type (e.g., all UEs 315 and devices 320 communicating with the device 305, all connected nodes of the device 305). For example, the device 305 may include a single indication of the average arrival time 350 of expected traffic 355 associated with UE 315-a, UE 315-b, device 320, and any other UE 315 or sub-IAB node connected to the device 305. Alternatively, the device 305 may include an indication of a minimum arrival time 350 of expected traffic 355 associated with all devices of the first type or the second type. For example, UE 315-a may be associated with expected traffic 355 having the shortest arrival time 350 (e.g., expected traffic 355 from UE 315-a may arrive at device 305 first), device 320 may be associated with expected traffic 355 having an arrival time 350 that is longer than the arrival time of UE 315-a, and UE 315-b may be associated with expected traffic 355 having the longest arrival time 350 (e.g., expected traffic 355 from UE 315-b may arrive at device 305 last).

[0118] By reporting the minimum arrival time 350 associated with UE 315-a, device 305 can ensure that parent device 310 avoids activating a sleep mode for one or more of its components until the expected traffic 355 from UE 315-a has been received at device 305, which can subsequently reduce power conservation of device 305, thereby facilitating successful communication with UE 315-a and reducing traffic latency from UE 315-a. Alternatively, if an average arrival time 350 associated with expected traffic 355 from UE 315-a, UE 315-b, and device 320 is indicated in the first BSR 340-a (which may be an arrival time 350 that is later than the arrival time of UE 315-a), parent device 310 may enter a sleep mode until a time after the arrival time 350 associated with the expected traffic 355 from UE 315-a. Thus, the parent device 310 may increase power savings by activating a longer (and in some cases, deeper) sleep mode for one or more components of the parent device 310 while dropping the expected traffic 355 associated with the UE 315 - a .

[0119] Additionally, the device 305 may indicate the first BSR 340 in the BSR message 345. Additionally, the BSR message 345 may include a priority 360 for each of the UE 315 and the device 320, which may assist the parent device 310 in prioritizing communications with the device 305 or activating a sleep mode for one or more of its components. For example, if the UE 315-a is associated with the shortest arrival time 350 as described herein, and if the UE 315-a has a relatively low priority as indicated in the BSR message 345, the parent device 310 may activate the sleep mode at a time prior to the arrival time 350 associated with the UE 315-a, thereby determining that the expected traffic 355 associated with the UE 315-a may be delayed.

[0120] The device 305 may output a BSR message 345 including a first BSR 340 to the parent device 310, wherein the first BSR 340 may indicate one or more arrival times 350 associated with expected traffic 355 for the UE 315-a, the UE 315-b, the device 320, or any combination thereof. The device 305 may output the BSR message 345 after generating the first BSR 340 based on the one or more messages 335. For example, the device 305 may output the BSR message 345 according to a periodicity (e.g., as indicated in an RRC configuration in the one or more messages 335). In some examples, the BSR message 345 may be an independent report indicating the first BSR 340. Alternatively, the BSR message 345 may include multiple BSRs, including the first BSR 340 and a second BSR, which may be a preemptive BSR carrying different information. For example, a first set of one or more bits of the BSR message 345 may be used for a first BSR 340, and a second set of one or more bits of the BSR message 345 may be used for a second BSR, wherein the second BSR may indicate one or more arrival times 350 associated with current traffic of the UE 315, the device 320, or any other sub-device of the device 305. Figure 4B Additional information about the second BSR and other types of BSRs is described. Alternatively, the device 305 can output a BSR message 345 at a time determined based on one or more arrival times 350 indicated in the first BSR 340. That is, the device 305 can output the BSR message 345 so that the parent device 310 can activate or avoid activating a sleep mode for one or more of its components to increase power savings or prioritize communications from the UE 315 or device 320.

[0121] In some examples, the parent device 310 may activate a sleep mode for one or more components associated with the first device based on one or more arrival times 350 indicated in the first BSR 340 in the BSR message 345. For example, if the first BSR 340 indicates a relatively long arrival time 350 (e.g., indicating that expected traffic 355 associated with the UE 315 or device 320 may arrive at a later time), the parent device 310 may activate a sleep mode (e.g., a light sleep mode, a deep sleep mode) for the one or more components until the expected traffic 355 from the UE 315 or device 320 arrives at the device 305. In some examples, the parent device 310 may activate a sleep mode for different components of the parent device 310 (such as, for example, the MT antenna 365-b, the DU 370-b, or another component) based on the information included in the first BSR 340.

[0122] Figure 4AAn example of a timeline 400 supporting a preemptive BSR extension for network power saving according to one or more aspects of the present disclosure is illustrated. In some examples, the timeline 400 may implement aspects of the wireless communication system 100 and the network architecture 200, or may be implemented by aspects of the wireless communication system 100 and the network architecture 200. For example, the timeline 400 may be used by a device 405, which may be an example of an IAB node as described herein. In addition, the timeline 400 may be used by a UE 415-a, a UE 415-b, and a device 420 (e.g., a sub-IAB node) communicating with the device 405, which may be examples of corresponding devices as described herein. The device 405 and the device 420 may each include an MT antenna, a DU, a CU, a RU, or other components in a decomposed RAN architecture, where these components may be co-located or located in a distributed location (e.g., a separate physical location).

[0123] As referenced in this article Figure 3 As described, the device 405 may receive one or more messages from the UE 415-a, UE 415-b, device 420, or a combination thereof. These messages may trigger the device 405 to generate a BSR (e.g., an extended preemptive BSR) for sending to a parent device (e.g., a parent IAB node). The BSR may indicate one or more arrival times 425 associated with the expected traffic 430 from the UE 415-a, UE 415-b, device 420, or any combination thereof based on the information included in the message.

[0124] The arrival time 425 may be the time at which the expected traffic 430 (e.g., future uplink transmission) transmitted by UE 415-a, UE 415-b, and device 420 will be received at device 405 (e.g., the MT antenna of device 405). In some examples, the arrival time 425 may be different for the expected traffic 430 transmitted from each device communicating with device 405. For example, the expected traffic 430-a transmitted from UE 415-a may be received at device 405 (e.g., arrives at the device) at the arrival time 425-a, which may be the latest arrival time. That is, the expected traffic 430-a may arrive at device 405 before the expected traffic 430-b transmitted from UE 415-b and the expected traffic 430-c transmitted from device 420.

[0125] In addition, the expected traffic 430-b sent from the UE 415-b may be received at the device 405 at the arrival time 425-b, which may be the latest arrival time. That is, the expected traffic 430-b may arrive at the device 405 after the expected traffic 430-a and the expected traffic 430-c. In addition, the expected traffic 430-c sent from the device 420 may be received at the device 405 at the arrival time 425-c between the arrival time 425-a and the arrival time 425-c. Therefore, the device 405 may receive the expected traffic 430-a, followed by the expected traffic 430-c, and then the expected traffic 430-b. The device 405 may send a BSR to the parent device, which indicates the arrival time 425 of the expected traffic 430 of each of the UE 415-a, the UE 415-b, and the device 420. Based on the information in the BSR, the parent device may activate a sleep mode for one or more of its components (e.g., MT antenna, DU, RU), for example, by shutting down or reducing the functionality of the one or more components. For example, based on the arrival time 425, the parent device may activate a light sleep mode until the arrival time 425-a because there is no expected traffic 430 to be sent to the device 405 before the arrival time 425-a. Therefore, the parent device may save power before the device 405 receives the expected traffic 430-a.

[0126] Figure 4B An example of a wireless communication system 401 supporting preemptive BSR extension for network power saving according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 401 may implement aspects of the wireless communication system 100 and the network architecture 200, or may be implemented by aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 401 may include a device 405, which may be an example of an IAB node as described herein. In addition, the wireless communication system 401 may include a parent device 410 in communication with the device 405, which may be an example of a parent IAB node as described herein. The device 405 and the parent device 410 may each include an MT antenna, a DU, a CU, a RU, or other components in a decomposed RAN architecture, where these components may be co-located or located in a distributed location (e.g., a separate physical location).

[0127] In some examples, the device 405 or the parent device 410 may activate a sleep mode for one or more corresponding components based on a given type of BSR. For example, the device 405 may receive a BSR 435-a in a BSR message 440-a from the UE 415-a, which may trigger the device 405 to activate a sleep mode for one or more of its components. In some examples, the device 405 may receive a BSR 435-b in a BSR message 440-b from the UE 415-a. The BSR 435-b may be an extended BSR that triggers the device 405 to activate a sleep mode for one or more of its components. Alternatively, the parent device 410 may receive a BSR 435-c in a BSR message 440-c from the device 405. The BSR 435-c may be a preemptive BSR that triggers the parent device 410 to activate a sleep mode for one or more of its components. In some cases, parent device 410 may receive BSR 435-d in a BSR message 440-d from device 405. BSR 435-d may be an extended preemptive BSR that triggers parent device 410 to activate a sleep mode for one or more of its components.

[0128] As referenced in this article Figure 3 and Figure 4A As described, the device 405 may receive one or more messages from the UE 415-a, UE 415-b, device 420, or a combination thereof. These messages may trigger the device 405 to generate a BSR 435-d (e.g., an extended preemptive BSR) for transmission to the parent device 410. The BSR 435-a may indicate one or more arrival times 425 associated with the expected traffic 430 from the UE 415-a, UE 415-b, device 420, or any combination thereof based on the information included in the message. The arrival time 425 may be the time at which the expected traffic 430 (e.g., future uplink transmissions) transmitted by the UE 415-a, UE 415-b, and device 420 will be received at the device 405 (e.g., the MT antenna of the device 405).

[0129] Device 405 may send a BSR 435 to parent device 410 in a BSR message 440, which may include additional information. For example, device 405 may send a BSR 435-d to parent device 410 in a BSR message 440-d, where BSR message 440-d may also include an indication of one or more arrival times 425 of expected traffic 430 and priorities 445 of UE 415 and device 420. Priorities 445 included in BSR message 440-d may assist parent device 410 in prioritizing communications with device 405 or activating sleep mode for one or more of its components. For example, if UE 415-a is in communication with a parent device 410 as described herein, Figure 4A The parent device 410 may activate the sleep mode at a time prior to the arrival time 425 associated with the UE 415-a, and if the UE 415-a has a relatively low priority as indicated in the BSR message 440-d, thereby determining that the expected traffic 430 associated with the UE 415-a may be delayed. Therefore, the BSR 435-d indicated in the BSR message 440-d may be a preemptive extended BSR that indicates the arrival time 425 of the future expected traffic 430 (e.g., future uplink transmission) sent from one or more UEs 415, devices 420 (e.g., child IAB nodes), or a combination thereof to the device 405 (which may be an IAB node).

[0130] In some examples, if device 405 is an IAB node, device 405 may send a BSR 435-c in a BSR message 440-c to parent device 410. BSR 435-c may be a preemptive BSR that may indicate the current buffer status of UE 415-a, UE 415-b, device 420, or any combination thereof communicating with device 405 to assist parent device 410 in activating a sleep mode for one or more of its components. For example, BSR 435-c may indicate how many uplink transmissions UE 415-a, UE 415-b, and device 420 are currently sending to device 405.

[0131] Alternatively, if device 405 is a network entity, UE 415-a may send a BSR 435-a in a BSR message 440-a to device 405. BSR 435-a may indicate a current buffer status of UE 415-a to assist device 405 in activating a sleep mode for one or more of its components. For example, BSR 435-a may indicate how many uplink transmissions UE 415-a is currently sending to device 405, or how many sidelink transmissions UE 415-a is currently sending with another UE 415 (e.g., UE 415-b).

[0132] In some examples, UE 415-a may send a BSR 435-b to device 405 (e.g., a network entity) in a BSR message 440-b. BSR 435-b may be an extended BSR that may indicate a future buffer state of UE 415-a to assist device 405 in activating a sleep mode for one or more of its components. For example, BSR 435-b may indicate how many uplink transmissions (e.g., expected traffic 430) UE 415-a will send to device 405 in the future, or how many sidelink transmissions UE 415-a will send to another UE 415 (e.g., UE 415-b), where the uplink transmissions or sidelink transmissions arrive at device 405 or UE 415-b, respectively, at a specific arrival time 425.

[0133] Figure 5 An example of a process flow 500 for supporting a preemptive BSR extension for network power saving according to one or more aspects of the present disclosure is illustrated. The process flow 500 may implement aspects of the wireless communication systems 100 and 300, or may be implemented by aspects of the wireless communication systems 100 and 300. For example, the process flow 500 may illustrate operations between a UE 505, a device 510 (e.g., an IAB node), and a parent device 515 (e.g., a parent IAB node), which may be examples of corresponding devices described herein. In the following description of the process flow 500, operations between the UE 505, the device 510, and the parent device 515 may be sent in an order different from the example order shown, or operations performed by the UE 505, the device 510, and the parent device 515 may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 500, and other operations may be added to the process flow 500.

[0134] At 520, the device 510 may obtain one or more messages from one or more second devices in communication with the device 510, the one or more second devices including one or more UEs (e.g., UE 505), one or more sub-devices (e.g., sub-IAB nodes), or both. The one or more messages may trigger the generation of a first BSR (e.g., an extended preemptive BSR) by the device 510. For example, the one or more messages may include a BSR or an extended BSR, or the one or more messages may indicate that the second device has entered a sleep mode.

[0135] At 525, device 510 can obtain one or more messages from parent device 515, where parent device 515 is a parent device of device 510 and belongs to the one or more second devices. In some examples, the one or more messages can trigger generation of a first BSR by device 510.

[0136] At 530, the device 510 may generate a first BSR based on receiving the one or more messages. The device 510 may provide, in the first BSR, an indication of one or more arrival times associated with expected traffic of the one or more second devices communicating with the first device based on the one or more messages received at the device 510. For example, the device 510 may include an indication of an average arrival time associated with expected traffic of one or more second devices of one or more types (e.g., a first type is a UE and a second type is a sub-IAB node). Additionally or alternatively, the device 510 may include an indication of a minimum arrival time associated with expected traffic of the one or more second devices.

[0137] At 535, device 510 may output a BSR message including a first BSR that indicates one or more arrival times associated with expected traffic for one or more second devices in communication with the first device based on the one or more messages. In some examples, the BSR message may additionally carry a second BSR (e.g., a preemptive BSR), wherein a first set of one or more bits in the BSR message may be used for the first BSR, and a second set of one or more bits in the BSR message may be used for the second BSR.

[0138] At 540, the parent device 515 may activate a sleep mode for one or more components associated with the parent device 515 based on the one or more arrival times indicated in the first BSR report. For example, the parent device 515 may activate a sleep mode (e.g., a light sleep mode, a deep sleep mode) for an MT antenna, a DU, or a RU associated with the parent device 515 based on the one or more arrival times.

[0139] Figure 6 A block diagram 600 of a device 605 supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a device as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0140] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels related to preemptive BSR extensions for network power conservation, data channels, information channels), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0141] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., control channels related to preemptive BSR extensions for network power conservation, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0142] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the preemptive BSR extension for network power conservation as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0143] In some examples, the communication manager 620, the receiver 610, the transmitter 615, 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 configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, the 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).

[0144] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, 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 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

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

[0146] For example, the communication manager 620 may be configured or otherwise support a component for obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering the generation of a first BSR by the first device. The communication manager 620 may be configured or otherwise support a component for outputting a BSR message including a first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based on the one or more messages.

[0147] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) can support a technique for communicating at the device a BSR indicating an arrival time of expected traffic associated with one or more UEs, child IAB nodes, or any combination thereof, which can assist the parent device in activating a sleep mode for one or more of its components. Thus, the described techniques can support increased power savings, signaling efficiency, and communication reliability.

[0148] Figure 7 A block diagram 700 of a device 705 supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or device 305 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0149] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to preemptive BSR extensions for network power conservation), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0150] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., control channels related to preemptive BSR extensions for network power conservation, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0151] The device 705 or its various components may be examples of components for performing various aspects of the preemptive BSR extension for network power conservation as described herein. For example, the communication manager 720 may include a message component 725, a BSR message component 730, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 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 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0152] The message component 725 may be configured or otherwise support means for obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering generation of a first BSR by the first device. The BSR message component 730 may be configured or otherwise support means for outputting a BSR message including a first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based on the one or more messages.

[0153] Figure 8 A block diagram 800 of a communication manager 820 supporting preemptive BSR extensions for network power conservation is shown in accordance with one or more aspects of the present disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of means for performing various aspects of the preemptive BSR extensions for network power conservation as described herein. For example, the communication manager 820 may include a message component 825, a BSR message component 830, an arrival time component 835, a priority component 840, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0154] The message component 825 may be configured or otherwise support means for obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering generation of a first BSR by the first device. The BSR message component 830 may be configured or otherwise support means for outputting a BSR message including a first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based on the one or more messages.

[0155] In some examples, the BSR message component 830 may be configured to or otherwise support components for outputting a BSR message including a first BSR and a second BSR, wherein a first group of one or more bits of the BSR message is used for the first BSR and a second group of one or more bits of the BSR message is used for the second BSR, the second BSR indicating one or more arrival times associated with current services of the one or more second devices.

[0156] In some examples, the message component 825 can be configured or otherwise support means for obtaining the one or more messages from the one or more second devices, the one or more messages including one or more second BSRs that trigger generation of the first BSR by the first device.

[0157] In some examples, the message component 825 can be configured to or otherwise support means for obtaining the one or more messages indicating a periodicity for generating the first BSR, wherein the BSR message is output according to the periodicity.

[0158] In some examples, the message component 825 can be configured to or otherwise support means for obtaining the one or more messages from a parent device of the first device, the one or more messages triggering generation of a first BSR by the first device, wherein the one or more second devices include the parent device.

[0159] In some examples, the message component 825 may be configured as or otherwise support a component for obtaining the one or more messages from the one or more second devices, the one or more messages indicating that a sleep mode has been activated for one or more components associated with the one or more second devices, the sleep mode triggering generation of a first BSR by the first device.

[0160] In some examples, arrival time component 835 may be configured as or otherwise support components for providing an indication of a first average arrival time associated with expected traffic for one or more second devices of a first type and a second average arrival time associated with expected traffic for one or more second devices of a second type for inclusion within a first BSR.

[0161] In some examples, the arrival time component 835 may be configured to or otherwise support means for providing an indication of an average arrival time associated with expected traffic for the one or more second devices for inclusion within the first BSR, wherein the one or more second devices are of the first type or the second type.

[0162] In some examples, arrival time component 835 may be configured or otherwise support means for providing an indication of a minimum arrival time associated with expected traffic for the one or more second devices for inclusion within the first BSR.

[0163] In some examples, priority component 840 can be configured or otherwise support means for providing an indication of a priority associated with each of the one or more second devices for inclusion within the first BSR.

[0164] In some examples, BSR message component 830 can be configured or otherwise support means for outputting a BSR message at a time determined based on the one or more arrival times.

[0165] Fig. 9 A diagram of a system 900 including a device 905 supporting preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The device 905 may be an example of or may include components of the device 605, device 705, or device as described herein. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an I / O controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0166] I / O controller 910 can manage input signals and output signals of device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as iOS. ® ANDROID ® , MS-DOS ® 、MS-WINDOWS ® , OS / 2 ® ,UNIX ® 、LINUX® or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor such as processor 940. In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0167] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925 that may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, thereby providing the modulated packets to one or more antennas 925 for transmission, and for demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0168] The memory 930 may include RAM and ROM. The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 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 935 may not be directly executable by the processor 940, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition to this, the memory 930 may also include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0169] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 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 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to cause the device 905 to perform various functions (e.g., various functions or tasks supporting preemptive BSR extensions for network power saving). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0170] For example, the communication manager 920 may be configured or otherwise support a component for obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering the generation of a first BSR by the first device. The communication manager 920 may be configured or otherwise support a component for outputting a BSR message including a first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices based on the one or more messages.

[0171] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support a technique for communicating at the device a BSR indicating an arrival time of expected traffic associated with one or more UEs, child IAB nodes, or any combination thereof, which can assist the parent device in activating a sleep mode for one or more of its components. Thus, the described techniques can support increased power savings, signaling efficiency, and communication reliability.

[0172] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of the preemptive BSR extension for network power conservation as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0173] Fig.10 A block diagram 1000 of a device 1005 supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a parent device 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 be in communication with each other (e.g., via one or more buses).

[0174] 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.

[0175] The transmitter 1015 may provide means for outputting (e.g., transmitting, 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.

[0176] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the preemptive BSR extension for network power conservation as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0177] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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 means for performing the functions described in the present disclosure. In some examples, the 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).

[0178] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

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

[0180] The communication manager 1020 may support wireless communication at a first device in a wireless network according to examples as disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support a component for obtaining a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices communicating with the second device. The communication manager 1020 may be configured to or otherwise support a component for activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0181] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) can support a technique for communicating at the device a BSR indicating an arrival time of expected traffic associated with one or more UEs, child IAB nodes, or any combination thereof, which can assist the parent device in activating a sleep mode for one or more of its components. Thus, the described techniques can support increased power savings, signaling efficiency, and communication reliability.

[0182] Fig.11 A block diagram 1100 of a device 1105 supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or parent device 310 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0183] The receiver 1110 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 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0184] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 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 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 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 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0185] Device 1105 or its various components may be examples of means for performing various aspects of the preemptive BSR extension for network power conservation as described herein. For example, communication manager 1120 may include BSR component 1125, sleep mode activation component 1130, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0186] The communication manager 1120 may support wireless communication at a first device in a wireless network according to examples as disclosed herein. The BSR component 1125 may be configured to or otherwise support a component for obtaining a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device. The sleep mode activation component 1130 may be configured to or otherwise support a component for activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0187] Fig.12A block diagram 1200 of a communication manager 1220 supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of means for performing various aspects of the preemptive BSR extension for network power conservation as described herein. For example, the communication manager 1220 may include a BSR component 1225, a sleep mode activation component 1230, a message output component 1235, an expected service component 1240, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0188] The communication manager 1220 may support wireless communication at a first device in a wireless network according to examples as disclosed herein. The BSR component 1225 may be configured to or otherwise support a component for obtaining a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device. The sleep mode activation component 1230 may be configured to or otherwise support a component for activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0189] In some examples, the BSR component 1225 may be configured to or otherwise support components for obtaining a BSR message including a first BSR and a second BSR, wherein a first group of one or more bits of the BSR message is used for the first BSR and a second group of one or more bits of the BSR message is used for the second BSR, the second BSR indicating one or more arrival times associated with current services of the one or more third devices.

[0190] In some examples, message output component 1235 can be configured or otherwise support means for outputting one or more messages to the second device that trigger generation of a first BSR by the second device.

[0191] In some examples, the expected traffic component 1240 may be configured as or otherwise support a component for obtaining, within the first BSR, an indication of a first average arrival time associated with expected traffic for one or more third devices of the first type and a second average arrival time associated with expected traffic for one or more third devices of the second type.

[0192] In some examples, expected traffic component 1240 can be configured or otherwise support means for obtaining within the first BSR an indication of an average arrival time associated with expected traffic for the one or more third devices, where the one or more third devices are of the first type or the second type.

[0193] In some examples, expected traffic component 1240 may be configured as or otherwise support means for obtaining, within the first BSR, an indication of a minimum arrival time associated with expected traffic for the one or more third devices.

[0194] In some examples, the expected traffic component 1240 can be configured as or otherwise support means for obtaining, within the first BSR, an indication of a priority associated with each of the one or more third devices.

[0195] In some examples, sleep mode activation component 1230 may be configured or otherwise support means for activating a sleep mode for the one or more components associated with the first device based on obtaining the BSR message at a determined time, the time being determined based on the one or more arrival times.

[0196] Fig.13 A diagram of a system 1300 including a device 1305 supporting preemptive BSR extension for network power conservation in accordance with one or more aspects of the present disclosure is shown. The device 1305 may be an example of or may include components of the device 1005, device 1105, or parent device as described herein. The device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0197] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for modulating a signal, thereby providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and for demodulating a signal. The transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces (where applicable) may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, 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).

[0198] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1325 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0199] The processor 1335 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 1335 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 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to enable the device 1305 to perform various functions (e.g., various functions or tasks supporting preemptive BSR extensions for network power saving). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform the various functions described herein. Processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functionality for performing the functionality of device 1305 (e.g., by executing code 1330).

[0200] In some examples, bus 1340 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305, or communications performed between different components of device 1305 that may be co-located or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one component of different components or divided between different components).

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

[0202] The communication manager 1320 may support wireless communication at a first device in a wireless network according to examples as disclosed herein. For example, the communication manager 1320 may be configured to or otherwise support a component for obtaining a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices communicating with the second device. The communication manager 1320 may be configured to or otherwise support a component for activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR.

[0203] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 can support a technique for communicating a BSR indicating an arrival time of expected traffic associated with one or more UEs, child IAB nodes, or any combination thereof at the device, which can assist the parent device in activating a sleep mode for one or more of its components. Thus, the described techniques can support increased power savings, signaling efficiency, and communication reliability.

[0204] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of the preemptive BSR extension for network power conservation as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0205] Fig.14 A flowchart illustrating a method 1400 for supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1400 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 9 In some examples, the device may execute a set of instructions to control the functional units of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.

[0206] At 1405, the method may include obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering the first device to generate a first BSR. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The message component 825 is used to execute.

[0207] At 1410, the method may include: outputting a BSR message including a first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices communicating with the first device based on the one or more messages. 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 Figure 8 The BSR message component 830 is used to execute.

[0208] Fig.15 A flow chart illustrating a method 1500 for supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1500 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 9 In some examples, the device may execute a set of instructions to control the functional units of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.

[0209] At 1505, the method may include obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering the first device to generate a first BSR. The operations of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The message component 825 is used to execute.

[0210] At 1510, the method may include: outputting a BSR message including a first BSR and a second BSR, wherein a first set of one or more bits of the BSR message is used for the first BSR, and a second set of one or more bits of the BSR message is used for the second BSR, the second BSR indicating one or more arrival times associated with current traffic of the one or more second devices. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The BSR message component 830 is used to execute.

[0211] Fig.16A flowchart illustrating a method 1600 for supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1600 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 9 In some examples, the device may execute a set of instructions to control the functional units of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.

[0212] At 1605, the method may include: obtaining one or more messages from one or more second devices, the one or more messages including one or more second BSRs that trigger the first device to generate a first BSR. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The message component 825 is used to execute.

[0213] At 1610, the method may include: outputting a BSR message including a first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices communicating with the first device based on the one or more messages. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 8 The BSR message component 830 is used to execute.

[0214] Fig.17 A flowchart illustrating a method 1700 for supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1700 may be implemented by an apparatus or component thereof as described herein. Figures 1 to 9 In some examples, the device may execute a set of instructions to control the functional units of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.

[0215] At 1705, the method may include obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering the first device to generate a first BSR. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 8 The message component 825 is used to execute.

[0216] At 1710, the method may include providing an indication of a first average arrival time associated with expected traffic for one or more second devices of the first type and a second average arrival time associated with expected traffic for one or more second devices of the second type for inclusion in the first BSR. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figure 8 The arrival time component 835 is used to perform the above operation.

[0217] At 1715, the method may include: outputting a BSR message including a first BSR, the first BSR indicating one or more arrival times associated with expected traffic of the one or more second devices communicating with the first device based on the one or more messages. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figure 8 The BSR message component 830 is used to execute.

[0218] Fig.18 A flow chart illustrating a method 1800 for supporting a preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a parent device or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a parent device or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the parent device may execute an instruction set to control the functional elements of the parent device to perform the described functions. Additionally or alternatively, the parent device may use dedicated hardware to perform various aspects of the described functions.

[0219] At 1805, the method may include: obtaining a BSR message including a first BSR from the second device, the first BSR indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The BSR component 1225 executes.

[0220] At 1810, the method may include: activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.12 The sleep mode activation component 1230 is executed.

[0221] Fig.19A flow chart illustrating a method 1900 for supporting preemptive BSR extension for network power conservation according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a parent device or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a parent device or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the parent device may execute an instruction set to control the functional elements of the parent device to perform the described functions. Additionally or alternatively, the parent device may use dedicated hardware to perform various aspects of the described functions.

[0222] At 1905, the method may include: outputting one or more messages to the second device, the one or more messages triggering the second device to generate a first BSR. The operations of 1905 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1905 may be described with reference to Fig.12 The message output component 1235 is used to execute.

[0223] At 1910, the method may include: obtaining, from a second device, a BSR message including a first BSR indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.12 The BSR component 1225 executes.

[0224] At 1915, the method may include: activating a sleep mode for one or more components associated with the first device based on the one or more arrival times indicated in the first BSR. The operations of 1915 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.12 The sleep mode activation component 1230 is executed.

[0225] The following provides an overview of various aspects of the disclosure:

[0226] Aspect 1: A method for performing wireless communications at a first device, the method comprising: obtaining one or more messages from one or more second devices communicating with the first device, the one or more messages triggering generation of a first BSR by the first device; and outputting a BSR message including the first BSR, the first BSR indicating one or more arrival times associated with expected services of the one or more second devices communicating with the first device based at least in part on the one or more messages.

[0227] Aspect 2: According to the method described in Aspect 1, the output includes: outputting the BSR message including the first BSR and the second BSR, wherein a first group of one or more bits of the BSR message are used for the first BSR, and a second group of one or more bits of the BSR message are used for the second BSR, and the second BSR indicates one or more arrival times associated with the current services of the one or more second devices.

[0228] Aspect 3: According to the method according to any one of Aspects 1 to 2, the obtaining includes: obtaining the one or more messages from the one or more second devices, the one or more messages including one or more second BSRs that trigger the first device to generate the first BSR.

[0229] Aspect 4: According to the method according to any one of Aspects 1 to 3, the obtaining comprises: obtaining the one or more messages indicating the periodicity for generating the first BSR, wherein the BSR message is output according to the periodicity.

[0230] Aspect 5: According to the method described in any one of Aspects 1 to 4, the obtaining includes: obtaining the one or more messages from a parent device of the first device, the one or more messages triggering the generation of the first BSR by the first device, wherein the one or more second devices include the parent device.

[0231] Aspect 6: According to the method described in any one of Aspects 1 to 5, the obtaining includes: obtaining the one or more messages from the one or more second devices, the one or more messages indicating that a sleep mode has been activated for one or more components associated with the one or more second devices, and the sleep mode triggers the generation of the first BSR by the first device.

[0232] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: providing an indication of a first average arrival time associated with expected services of one or more second devices of the first type and a second average arrival time associated with the expected services of one or more second devices of the second type, so as to include them in the first BSR.

[0233] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method also includes: providing an indication of an average arrival time associated with the expected service of the one or more second devices to be included in the first BSR, wherein the one or more second devices are of the first type or the second type.

[0234] Aspect 9: According to any one of aspects 1 to 8, the method further includes: providing an indication of a minimum arrival time associated with the expected traffic of the one or more second devices to be included in the first BSR.

[0235] Aspect 10: The method according to any one of aspects 1 to 9, the method further comprising: providing an indication of a priority associated with each of the one or more second devices for inclusion in the first BSR.

[0236] Aspect 11: According to any one of aspects 1 to 10, the outputting comprises: outputting the BSR message at a time determined at least in part based on the one or more arrival times.

[0237] Aspect 12: A method for performing wireless communications at a first device in a wireless network, the method comprising: obtaining a BSR message including a first BSR from a second device, the first BSR indicating one or more arrival times associated with expected services of one or more third devices communicating with the second device; and activating a sleep mode for one or more components associated with the first device based at least in part on the one or more arrival times indicated in the first BSR.

[0238] Aspect 13: According to the method according to Aspect 12, the obtaining includes: obtaining the BSR message including the first BSR and the second BSR, wherein a first group of one or more bits of the BSR message are used for the first BSR, and a second group of one or more bits of the BSR message are used for the second BSR, and the second BSR indicates one or more arrival times associated with the current services of the one or more third devices.

[0239] Aspect 14: The method according to any one of aspects 12 to 13, further comprising: outputting one or more messages to the second device, wherein the one or more messages trigger the second device to generate the first BSR.

[0240] Aspect 15: According to the method described in any one of Aspects 12 to 14, the obtaining includes: obtaining within the first BSR an indication of a first average arrival time associated with expected services for one or more third devices of the first type and a second average arrival time associated with the expected services for one or more third devices of the second type.

[0241] Aspect 16: According to the method described in any one of Aspects 12 to 15, the obtaining includes: obtaining within the first BSR an indication of an average arrival time associated with the expected service associated with the one or more third devices, wherein the one or more third devices are of the first type or the second type.

[0242] Aspect 17: According to the method of any one of aspects 12 to 16, the obtaining comprises: obtaining, within the first BSR, an indication of a minimum arrival time associated with the expected traffic of the one or more third devices.

[0243] Aspect 18: According to the method according to any one of aspects 12 to 17, the obtaining comprises: obtaining, within the first BSR, an indication of a priority associated with each of the one or more third devices.

[0244] Aspect 19: According to the method described in any one of Aspects 12 to 18, the activation includes: activating the sleep mode for the one or more components associated with the first device based at least in part on obtaining the BSR message at a determined time, and the time is determined at least in part based on the one or more arrival times.

[0245] Aspect 20: An apparatus, comprising: a processor; and a memory coupled to the processor, wherein the processor is configured to execute the method according to any one of aspects 1 to 11.

[0246] Aspect 21: An apparatus, comprising: at least one component for performing the method according to any one of aspects 1 to 11.

[0247] Aspect 22: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0248] Aspect 23: An apparatus for wireless communication at a first device in a wireless network, the apparatus comprising: a processor; and a memory coupled to the processor, the processor being configured to execute the method according to any one of aspects 12 to 19.

[0249] Aspect 24: An apparatus for wireless communication at a first device in a wireless network, the apparatus comprising at least one means for performing the method according to any one of aspects 12 to 19.

[0250] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a first device in a wireless network, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 19.

[0251] It should be noted that the methods described herein describe possible implementations, and that the 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.

[0252] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system 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 described techniques 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.

[0253] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be 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.

[0254] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, DSP, ASIC, CPU, 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).

[0255] 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 any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0256] Computer-readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable media may 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 to carry or store desired program code components and any other non-transient medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.In addition, any connection is appropriately referred to as a computer-readable medium.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. Disk and disc, as used herein, includes 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.

[0257] 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). In addition, 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".

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

[0259] 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 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 reference label, or other subsequent reference labels.

[0260] 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 "having advantages 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 instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0261] 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. Therefore, 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 device in a wireless network, the apparatus comprising: processor; and a memory coupled to the processor, the processor being configured to: obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering generation of a first buffer status report by the first device; as well as A buffer status report message is outputted including the first buffer status report indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based at least in part on the one or more messages.

2. The apparatus according to claim 1, wherein in order to output the buffer status report message, the processor is configured to: Outputting the buffer status report message including the first buffer status report and a second buffer status report, wherein a first group of one or more bits of the buffer status report message is used for the first buffer status report, and a second group of one or more bits of the buffer status report message is used for the second buffer status report, and the second buffer status report indicates one or more arrival times associated with current services of the one or more second devices.

3. The apparatus of claim 1 , wherein to obtain the one or more messages, the processor is configured to: The one or more messages are obtained from the one or more second devices, the one or more messages comprising one or more second buffer status reports that trigger generation of the first buffer status report by the first device.

4. The apparatus of claim 1 , wherein to obtain the one or more messages, the processor is configured to: The one or more messages indicating a periodicity for generating the first buffer status report are obtained, wherein the buffer status report message is output according to the periodicity.

5. The apparatus of claim 1 , wherein to obtain the one or more messages, the processor is configured to: The one or more messages are obtained from a parent device of the first device, the one or more messages triggering generation of the first buffer status report by the first device, wherein the one or more second devices include the parent device.

6. The apparatus of claim 1 , wherein to obtain the one or more messages, the processor is configured to: The one or more messages are obtained from the one or more second devices, the one or more messages indicating that a sleep mode has been activated for one or more components associated with the one or more second devices, the sleep mode triggering generation of the first buffer status report by the first device.

7. The apparatus of claim 1, wherein the processor is further configured to: An indication of a first average arrival time associated with expected traffic for one or more second devices of a first type and a second average arrival time associated with the expected traffic for one or more second devices of a second type is provided for inclusion in the first buffer status report.

8. The apparatus of claim 1, wherein the processor is further configured to: An indication of a mean arrival time associated with the expected traffic for the one or more second devices is provided for inclusion in the first buffer status report, wherein the one or more second devices are of the first type or the second type.

9. The apparatus of claim 1, wherein the processor is further configured to: An indication of a minimum arrival time associated with the expected traffic for the one or more second devices is provided for inclusion in the first buffer status report.

10. The apparatus of claim 1, wherein the processor is further configured to: An indication of a priority level associated with each of the one or more second devices is provided for inclusion in the first buffer status report.

11. The apparatus of claim 1 , wherein to output the buffer status report message, the processor is configured to: The buffer status report message is output at a time determined based at least in part on the one or more arrival times.

12. An apparatus for wireless communication at a first device in a wireless network, the apparatus comprising: processor; and a memory coupled to the processor, the processor being configured to: obtaining, from a second device, a buffer status report message including a first buffer status report indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device; as well as A sleep mode is activated for one or more components associated with the first device based at least in part on the one or more arrival times indicated in the first buffer status report.

13. The apparatus according to claim 12, wherein in order to obtain the buffer status report message, the processor is configured to: Obtain the buffer status report message including the first buffer status report and a second buffer status report, wherein a first group of one or more bits of the buffer status report message is used for the first buffer status report, and a second group of one or more bits of the buffer status report message is used for the second buffer status report, and the second buffer status report indicates one or more arrival times associated with current services of the one or more third devices.

14. The apparatus of claim 12, wherein the processor is further configured to: One or more messages are output to the second device, the one or more messages triggering generation of the first buffer status report by the second device.

15. The apparatus according to claim 12, wherein in order to obtain the buffer status report message, the processor is configured to: An indication of a first average arrival time associated with the expected traffic for one or more third devices of a first type and a second average arrival time associated with the expected traffic for one or more third devices of a second type is obtained within the first buffer status report.

16. The apparatus according to claim 12, wherein in order to obtain the buffer status report message, the processor is configured to: An indication of a mean arrival time associated with the expected traffic for the one or more third devices is obtained within the first buffer status report, wherein the one or more third devices are of the first type or the second type.

17. The apparatus according to claim 12, wherein in order to obtain the buffer status report message, the processor is configured to: An indication of a minimum arrival time associated with the expected traffic for the one or more third devices is obtained within the first buffer status report.

18. The apparatus according to claim 12, wherein in order to obtain the buffer status report message, the processor is configured to: An indication of a priority level associated with each of the one or more third devices is obtained within the first buffer status report.

19. The apparatus of claim 12, wherein to activate the sleep mode, the processor is configured to: The sleep mode is activated for the one or more components associated with the first device based at least in part on obtaining the buffer status report message at a determined time, the time being determined based at least in part on the one or more arrival times.

20. A method for wireless communication at a first device, the method comprising: obtaining one or more messages from one or more second devices in communication with the first device, the one or more messages triggering generation of a first buffer status report by the first device; as well as A buffer status report message is outputted including the first buffer status report indicating one or more arrival times associated with expected traffic of the one or more second devices in communication with the first device based at least in part on the one or more messages.

21. The method of claim 20, wherein the output comprises: Outputting the buffer status report message including the first buffer status report and a second buffer status report, wherein a first group of one or more bits of the buffer status report message is used for the first buffer status report, and a second group of one or more bits of the buffer status report message is used for the second buffer status report, and the second buffer status report indicates one or more arrival times associated with current services of the one or more second devices.

22. The method according to claim 20, wherein the obtaining comprises: The one or more messages are obtained from the one or more second devices, the one or more messages comprising one or more second buffer status reports that trigger generation of the first buffer status report by the first device.

23. The method according to claim 20, wherein the obtaining comprises: The one or more messages indicating a periodicity for generating the first buffer status report are obtained, wherein the buffer status report message is output according to the periodicity.

24. The method according to claim 20, wherein the obtaining comprises: The one or more messages are obtained from a parent device of the first device, the one or more messages triggering generation of the first buffer status report by the first device, wherein the one or more second devices include the parent device.

25. The method according to claim 20, wherein the obtaining comprises: The one or more messages are obtained from the one or more second devices, the one or more messages indicating that a sleep mode has been activated for one or more components associated with the one or more second devices, the sleep mode triggering generation of the first buffer status report by the first device.

26. The method according to claim 20, further comprising: An indication of a first average arrival time associated with expected traffic for one or more second devices of a first type and a second average arrival time associated with the expected traffic for one or more second devices of a second type is provided for inclusion in the first buffer status report.

27. A method for wireless communication at a first device in a wireless network, the method comprising: obtaining, from a second device, a buffer status report message including a first buffer status report indicating one or more arrival times associated with expected traffic of one or more third devices in communication with the second device; as well as A sleep mode is activated for one or more components associated with the first device based at least in part on the one or more arrival times indicated in the first buffer status report.

28. The method according to claim 27, wherein the obtaining comprises: Obtain the buffer status report message including the first buffer status report and a second buffer status report, wherein a first group of one or more bits of the buffer status report message is used for the first buffer status report, and a second group of one or more bits of the buffer status report message is used for the second buffer status report, and the second buffer status report indicates one or more arrival times associated with current services of the one or more third devices.

29. The method according to claim 27, further comprising: One or more messages are output to the second device, the one or more messages triggering generation of the first buffer status report by the second device.

30. The method of claim 27, wherein obtaining comprises: An indication of a first average arrival time associated with the expected traffic for one or more third devices of a first type and a second average arrival time associated with the expected traffic for one or more third devices of a second type is obtained within the first buffer status report.

Images