Sidelink buffer status reporting for multi-hop sidelink networks

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first network node can receive a first sidelink communication from a second network node, the first sidelink communication including second buffer state information associated with the second network node. The first network node can send a sidelink buffer status report (BSR) indicating the second buffer status information and first buffer status information associated with the first network node to a third network node. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 811,559, filed on July 8, 2022, entitled "SIDELINK BUFFER STATUS REPORTING FOR MULTI-HOP SIDELINK NETWORKS," and is assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Background Art

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for sidelink buffer status reporting for a multi-hop sidelink network.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a first network node for wireless communication. The first network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a first sidelink communication from a second network node, the first sidelink communication including second buffer status information associated with the second network node. The one or more processors may be configured to send a sidelink buffer status report (BSR) indicating the second buffer status information and the first buffer status information associated with the first network node to a third network node.

[0008] Some aspects described herein relate to a first network node for wireless communication. The first network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to a second network node. The one or more processors may be configured to receive a sidelink BSR from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node.

[0009] Some aspects described herein relate to a method of wireless communication performed by a first network node. The method may include receiving a first sidelink communication from a second network node, the first sidelink communication including second buffer status information associated with the second network node. The method may include sending a sidelink BSR indicating the second buffer status information and first buffer status information associated with the first network node to a third network node.

[0010] Some aspects described herein relate to a method of wireless communication performed by a first network node. The method may include sending a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to a second network node. The method may include receiving a sidelink BSR from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a first network node. The instruction set, when executed by one or more processors of the first network node, can cause the first network node to receive a first sidelink communication from a second network node, the first sidelink communication including second buffer status information associated with the second network node. The instruction set, when executed by one or more processors of the first network node, can cause the first network node to send a sidelink BSR indicating the second buffer status information and first buffer status information associated with the first network node to a third network node.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a first network node. The instruction set, when executed by one or more processors of the first network node, can cause the first network node to send a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to a second network node. The instruction set, when executed by one or more processors of the first network node, can cause the first network node to receive a sidelink BSR from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a first sidelink communication from a first network node, the first sidelink communication including second buffer status information associated with the first network node. The apparatus may include means for sending a sidelink BSR indicating the second buffer status information and first buffer status information associated with the apparatus to a second network node.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to a first network node. The apparatus may include means for receiving a sidelink BSR from the first network node indicating first buffer status information associated with the first network node and second buffer status information associated with a second network node.

[0015] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example environment in which apparatuses and / or methods described herein may be implemented according to the present disclosure.

[0020] Figure 2 is a diagram of example components of an apparatus.

[0021] Figure 3 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an environment including a network node in wireless communication with another network node according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of a multi-hop side link network according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example associated with a sidelink buffer status report for a multi-hop sidelink network.

[0026] Figure 8 is a diagram illustrating an example of side link buffer status reporting for a multi-hop side link network according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example of side link buffer status reporting for a multi-hop side link network according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example of side link buffer status reporting for a multi-hop side link network according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a first network node according to the present disclosure.

[0030] Fig.12 is a diagram illustrating an example process performed, for example, by a first network node according to the present disclosure.

[0031] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0033] Aspects and examples generally include methods, apparatus, network nodes, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as described or fully described herein with reference to the figures and description and as illustrated in the figures and description.

[0034] The present disclosure can be easily used as a basis for modifying or designing other structures for performing the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages are better understood from the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of the limitations of the claims.

[0035] Although various aspects are described in the present disclosure by illustrating some examples, such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence equipment). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. Various aspects described herein can be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of different sizes, shapes and compositions.

[0036] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0037] Figure 1 1 is a diagram illustrating an example environment 100 in which the apparatus and / or methods described herein may be implemented according to the present disclosure. Figure 1 As shown, environment 100 may include network node 102A, network node 102B, network node 102C, and network node 102D, which may communicate with each other via network 104. Network nodes 102A, 102B, 102C, and 102D may be dispersed throughout network 104, and each network node 102A, 102B, 102C, and 102D may be stationary and / or mobile. Network 104 may include wired communication connections, wireless communication connections, or a combination of wired and wireless communication connections.

[0038] For example, the network 104 may include a cellular network (e.g., a long term evolution (LTE) network, a code division multiple access (CDMA) network, a 3G network, a 4G network, a 5G network, another type of next generation network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-optic-based network, a cloud computing network, the like, and / or combinations of these or other types of networks.

[0039] In general, any number of networks 104 may be deployed in a given geographic area. Each network 104 may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, an open RAT, a new radio (NR), or a 5G RAT network may be deployed.

[0040] In some aspects, environment 100 may include one or more non-terrestrial network (NTN) deployments, where non-terrestrial wireless communication devices may include non-terrestrial network nodes (e.g., network nodes 102A, 102B, 102C, and / or 102D). Non-terrestrial network nodes may include network nodes such as user equipment (UE) (interchangeably referred to herein as "non-terrestrial UE"), base stations (interchangeably referred to herein as "non-terrestrial BS" and "non-terrestrial base stations"), and / or relay stations (interchangeably referred to herein as "non-terrestrial relay stations"). As used herein, "NTN" may refer to a network to which access is facilitated by non-terrestrial network nodes (such as non-terrestrial UE, non-terrestrial base stations, and / or non-terrestrial relay stations).

[0041] One or more of network nodes 102A, 102B, 102C and 102D may be, include or be included in any number of non-terrestrial wireless communication devices. Non-terrestrial wireless communication devices may include satellites, manned aircraft systems, unmanned aircraft systems (UAS) platforms, etc. Satellites may include low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, geostationary orbit (GEO) satellites, high elliptical orbit (HEO) satellites, etc. Manned aircraft systems may include aircraft, helicopters, spacecraft, etc. UAS platforms may include high altitude platform stations (HAPS), and may include balloons, spacecraft, aircraft, etc. Satellites may use satellite communications to communicate directly and / or indirectly with other entities in the environment. Other entities may include UEs (e.g., ground UEs and / or non-terrestrial UEs), other satellites in one or more NTN deployments, other types of base stations (e.g., stationed and / or ground-based BSs), relay stations, and / or one or more components and / or devices included in a core network, etc.

[0042] As described herein, a network node (which may alternatively be referred to as a node, a network entity, or a wireless node) may be, may be similar to, may include, or may be included in (e.g., a component of) a base station (e.g., any base station described herein, including a decomposed base station), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. For another example, a network node may be a base station or a network entity.

[0043] The adjectives "first", "second", "third", etc. are used in conjunction with a discussion to contextually distinguish between two or more modified nouns and are not meant to be absolute modifiers that apply only to specific corresponding nodes throughout the document. For example, a network node may be referred to as a "first network node" in conjunction with one discussion and may be referred to as a "second network node" in conjunction with another discussion, and vice versa. As an example, the first network node may be configured to communicate with the second network node or the third network node. In one aspect of the example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of the example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of the example, the first network node, the second network node, and the third network node may be different relative to these examples.

[0044] Similarly, references to UE, base station, apparatus, device, computing system, etc. may include disclosure of UE, base station, apparatus, device, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first apparatus, a first device, a first computing system, a first group of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second group of one or more components, a second processing entity, etc.

[0045] 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, transmit, output, communicate, 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, transmitted, output, communicated, or sent by the first network node.

[0046] As shown, network node 102A may include a communication manager 106 and a transceiver 108. Communication manager 106 may be configured to perform one or more communication tasks as described herein. In some aspects, communication manager 106 may direct transceiver 108 to perform one or more communication tasks as described herein. Although depicted with reference only to network node 102A for clarity of description, any one or more of network nodes 102B, 102C, and 102D may also include a communication manager and a transceiver.

[0047] As described in more detail elsewhere herein, the communication manager 106 of the first network node may receive a first sidelink communication from a second network node, the first sidelink communication including second buffer status information associated with the second network node, and send a sidelink buffer status report (BSR) to a third network node indicating the second buffer status information and the first buffer status information associated with the first network node.

[0048] As described in more detail elsewhere herein, the communication manager 106 of the first network node may send a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to a second network node; and receive a sidelink BSR from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node. Additionally or alternatively, the communication manager 106 may perform one or more other operations described herein.

[0049] Figure 1 The number and arrangement of entities shown are provided as one or more examples. In practice, there may be Figure 1 The network nodes and / or networks shown are additional network nodes and / or networks, fewer network nodes and / or networks, different network nodes and / or networks, or network nodes and / or networks arranged in a different manner than those shown. In addition, network nodes 102A, 102B, 102C, and / or 102D may be implemented using a single device or multiple devices.

[0050] Figure 2 2 is a diagram of example components of apparatus 200. Apparatus 200 may correspond to any one or more of network nodes 102A, 102B, 102C, and / or 102D. Additionally or alternatively, any one or more of network nodes 102A, 102B, 102C, and / or 102D may include one or more apparatuses 200 and / or one or more components of apparatus 200. For example, in some aspects, apparatus 200 may include an apparatus (e.g., a device, a device component, a modem, a chip, and / or a group of device components, etc.) configured to perform wireless communication methods, as described herein. Figure 2 As shown, the apparatus 200 may include components such as a bus 205, a processor 210, a memory 215, an input component 220, an output component 225, a communication interface 230, a communication manager 235, and a buffer status reporting component 240. One or more of the components 205, 210, 215, 220, 225, 230, 235, and / or 240 may be implemented in hardware, software, or a combination of hardware and software.

[0051] The bus 205 includes components that permit communication between the components of the device 200. The processor 210 includes a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a digital signal processor (DSP), a microprocessor, a microcontroller, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and / or another type of processing component. In some aspects, the processor 210 includes one or more processors that can be programmed to perform functions.

[0052] The memory 215 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by the processor 210. The memory 215 may store other information and / or software related to the operation and use of the device 200. For example, the memory 215 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cassette, a magnetic tape, and / or another type of non-transitory computer-readable medium.

[0053] Input component 220 includes components that allow device 200 to receive information, such as via user input. For example, input component 220 can be associated with a user interface as described herein (e.g., to allow a user to interact with one or more features of device 200). Input component 220 may include a capacitive touch screen display that can receive user input. Input component 220 may include a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone, etc. Additionally or alternatively, input component 220 may include a sensor for sensing information (e.g., a visual sensor, a position sensor, an accelerometer, a gyroscope, and / or an actuator, etc.). In some aspects, input component 220 may include a camera (e.g., a high-resolution camera and / or a low-resolution camera, etc.). Output component 225 may include a component that provides an output from device 200 (e.g., a display, a speaker, and / or one or more light-emitting diodes (LEDs), etc.).

[0054] The communication interface 230 may include a transmitting component and / or a receiving component. For example, the communication interface 230 may include a transceiver and / or one or more separate receivers and / or transmitters that enable the device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection. In some aspects, the communication interface may include one or more radio frequency reflective elements and / or one or more radio frequency refractive elements. The communication interface 230 may allow the device 200 to receive information from another device and / or provide information to another device. For example, the communication interface 230 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, an RF interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, a wireless modem, an internal integrated circuit (I 2 C) and / or serial peripheral interface (SPI), etc.

[0055] The communication manager 235 may include hardware, software, or a combination of hardware and software configured to cause the device 200 to perform one or more communication tasks associated with the communication manager 106 and / or the transceiver 108. In some aspects, the communication manager 235 may be, be similar to, include, or be included in Figure 1 In some aspects, the communication manager 235 may include the processor 210, the memory 215, the input component 220, the output component 225, the communication interface 230 and / or the buffer status reporting component 240 and / or one or more aspects thereof.

[0056] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Described differently.

[0057] As mentioned above, in some aspects, Figure 1 The network 104 depicted in the figure may include a cellular network including a RAT. Although some aspects may be described herein using terms generally associated with 5G or NR RAT, various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or 5G (e.g., 6G) RAT.

[0058] Figure 3300 is a diagram illustrating an example of a wireless network 300 according to the present disclosure. The wireless network 300 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of the 5G network and / or the 4G network, etc. The wireless network 300 may include one or more network nodes 310 (shown as network node 310a, network node 310b, network node 310c, and network node 310d), one UE 320 or multiple UEs 320 (shown as UE 320a, UE 320b, UE 320c, UE 320d, and UE 320e), and / or other entities. The network node 310 is a network node that communicates with the UE 320. As shown in the figure, the network node 310 may include one or more network nodes. For example, the network node 310 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 310 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 310 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0059] In some examples, the network node 310 is or includes a network node that communicates with the UE 320 via a radio access link, such as an RU. In some examples, the network node 310 is or includes a network node that communicates with other network nodes 310 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 310 is or includes a network node that communicates with other network nodes 310 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 310 (such as an aggregated network node 310 or a decomposed network node 310) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 310 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 310 may be interconnected with each other or with one or more other network nodes 310 in the wireless network 300 using any suitable transport network through various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0060] In some examples, the network node 310 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 310 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 310 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. 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 320 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 320 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 320 associated with a femto cell (e.g., a UE 320 in a closed subscriber group (CSG)). A network node 310 for a macro cell may be referred to as a macro network node. A network node 310 for a pico cell may be referred to as a pico network node. The network node 310 for a femto cell may be referred to as a femto network node or a home network node. Figure 3 In the example shown in , network node 310a can be a macro network node for macro cell 302a, network node 310b can be a pico network node for pico cell 302b, and network node 310c can be a femto network node for femto cell 302c. The network node can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cell can move according to the location of the mobile network node 310 (e.g., a mobile network node).

[0061] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 310). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0062] The wireless network 300 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 310 or a UE 320) and transmit transmissions of data to a downstream node (e.g., a UE 320 or a network node 310). A relay station may be a UE 320 that can relay transmissions for other UEs 320. Figure 3 In the example shown in , a network node 310d (e.g., a relay network node) can communicate with a network node 310a (e.g., a macro network node) and a UE 320d to facilitate communication between the network node 310a and the UE 320d. A network node 310 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0063] The wireless network 300 may be a heterogeneous network including different types of network nodes 310, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 310 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 300. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0064] The network controller 330 may be coupled to or in communication with a collection of network nodes 310 and may provide coordination and control for these network nodes 310. The network controller 330 may communicate with the network nodes 310 via a backhaul communication link or a midhaul communication link. The network nodes 310 may communicate with each other directly or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 330 may be a CU or a core network device, or may include a CU or a core network device.

[0065] For example, in some aspects, the wireless network 300 may be, include, or be included in a wireless backhaul network (sometimes referred to as an IAB network). In an IAB network, at least one network node (e.g., network node 310) may be an anchor base station that communicates with a core network via a wired backhaul link (such as a fiber connection). An anchor base station may also be referred to as an IAB donor (or IAB-donor), a central entity, a central unit, and the like. An IAB network may include one or more non-anchor base stations (sometimes referred to as relay base stations or IAB nodes (or IAB-nodes)). A non-anchor base station may communicate directly or indirectly with an anchor base station via one or more backhaul links (e.g., via one or more non-anchor base stations) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link may be a wireless link. An anchor base station and / or a non-anchor base station may communicate with one or more UEs (e.g., UE 320) via an access link, which may be a wireless link for carrying access traffic.

[0066] In some aspects, a radio access network including an IAB network may utilize millimeter wave technology and / or directional communications (e.g., beamforming, precoding, etc.) for communications between base stations and / or UEs (e.g., between two base stations, between two UEs, and / or between a base station and a UE). For example, a wireless backhaul link between base stations may use millimeter waves to carry information and / or may use beamforming, precoding, etc. to be directed toward a target base station. Similarly, a wireless access link between a UE and a base station may use millimeter waves and / or may be directed toward a target wireless node (e.g., a UE and / or a base station). In this way, inter-link interference may be reduced.

[0067] The IAB network may include an IAB donor connected to the core network via a wired connection (e.g., wired backhaul). For example, the Ng interface of the IAB donor may terminate at the core network. Additionally or alternatively, the IAB donor may be connected to one or more devices of the core network, which provide a core access and mobility management function (AMF). In some aspects, the IAB donor may include a base station 310, such as an anchor base station. The IAB donor may include a central unit (CU) that can perform access node controller (ANC) functions and / or AMF functions. The CU may configure the DU of the IAB donor and / or may configure one or more IAB nodes (e.g., mobile terminal (MT) functions and / or DU functions of IAB nodes) connected to the core network via the IAB donor. Therefore, the CU of the IAB donor may control and / or configure the entire IAB network (or a portion thereof) connected to the core network via the IAB donor, such as by using control messages and / or configuration messages (e.g., radio resource control (RRC) configuration messages or F1 application protocol (F1AP) messages).

[0068] The MT function of an IAB node (e.g., a child node) may be controlled and / or scheduled by another IAB node (e.g., a parent node of the child node) and / or by an IAB donor. The DU function of an IAB node (e.g., a parent node) may control and / or schedule other IAB nodes (e.g., child nodes of the parent node) and / or UE 320. Therefore, DU may be referred to as a scheduling node or a scheduling component, and MT may be referred to as a scheduled node or a scheduled component. In some aspects, an IAB donor may include a DU function without an MT function. That is, an IAB donor may configure, control and / or schedule the communication of an IAB node and / or UE 320. UE 320 may include only an MT function without a DU function. That is, the communication of UE 320 may be controlled and / or scheduled by an IAB donor and / or an IAB node (e.g., a parent node of UE 320).

[0069] When a first node controls and / or schedules the communication of a second node (e.g., when the first node provides a DU function for the MT function of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Thus, the DU function of the parent node may control and / or schedule the communication of the child node for the parent node. The parent node may be an IAB donor or an IAB node, and the child node may be an IAB node or a UE 320. The communication of the MT function of the child node may be controlled and / or scheduled by the parent node of the child node.

[0070] The link between UE 320 and the IAB donor or between UE 320 and the IAB node may be referred to as an access link. The access link may be a wireless access link that provides radio access to the core network to UE 320 via the IAB donor and optionally via one or more IAB nodes. Therefore, wireless network 300 may be referred to as a multi-hop network or a wireless multi-hop network.

[0071] The link between an IAB donor and an IAB node or between two IAB nodes may be referred to as a backhaul link. A backhaul link may be a wireless backhaul link that provides radio access to a core network to an IAB node via an IAB donor and optionally via one or more other IAB nodes. In an IAB network, network resources (e.g., time resources, frequency resources, and / or space resources) for wireless communication may be shared between an access link and a backhaul link. In some aspects, a backhaul link may be a primary backhaul link or an auxiliary backhaul link (e.g., a standby backhaul link). In some aspects, an auxiliary backhaul link may be used if the primary backhaul link fails, becomes congested, and / or becomes overloaded, etc.

[0072] UE 320 can be dispersed in wireless network 300, and each UE 320 can be stationary or mobile. UE 320 can include, for example, access terminal, terminal, mobile station and / or subscriber unit. UE 320 can be a cellular phone (e.g., smart phone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, medical device, biometric device, wearable device (e.g., smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring or smart bracelet)), entertainment device (e.g., music device, video device and / or satellite radio), transportation component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, UE function of network node and / or any other suitable device configured to communicate via wireless or wired medium.

[0073] Some UE 320 may be considered as machine type communication (MTC) UE or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 320 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 320 may be considered as customer premises equipment. UE 320 may be included in a housing that accommodates components of UE 320, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0074] In general, any number of wireless networks 300 may be deployed in a given geographic area. Each wireless network 300 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0075] In some examples, two or more UEs 320 (e.g., shown as UE 320a and UE 320e) can communicate directly using one or more side link channels (e.g., without using the network node 310 as an intermediary for communicating with each other). For example, the UE 320 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, the UE 320 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the network node 310.

[0076] The devices of the wireless network 300 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 300 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0077] 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.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0078] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0079] As described above, in some aspects, a network node (e.g., Figure 1The network nodes 102A, 102B, 102C, and / or 102D) depicted in FIG. 1 can be implemented in a wireless communication environment. For example, in some aspects, the network node can be implemented as a UE, a base station, a relay device, and / or a TRP, etc. In some such aspects, as Figure 3 As shown, UE 320a may include a communication manager 340 and / or a transceiver 345, and network node 310a may include a communication manager 350 and / or a transceiver 355. In some aspects, communication managers 340 and / or 350 may be, be similar to, include, or be included in Figure 1 The communications manager 106 and / or Figure 2 In some aspects, transceivers 345 and / or 355 may be, similar to, include, or be included in communications manager 235 as depicted in FIG. Figure 1 In some aspects, transceivers 345 and / or 355 may include or be included in transceiver 108 as depicted in FIG. Figure 2 In the communication interface 230 depicted in .

[0080] In some aspects, the first network node may include communications manager 340 and / or 350. As described in more detail elsewhere herein, communications manager 340 and / or 350 may receive a first sidelink communication from a second network node, the first sidelink communication including second buffer status information associated with the second network node, and send a sidelink BSR to a third network node indicating the second buffer status information and the first buffer status information associated with the first network node.

[0081] As described in more detail elsewhere herein, the communication manager 340 and / or 350 may send a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to a second network node; and receive a sidelink BSR from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node. Additionally or alternatively, the communication manager 340 and / or 350 may perform one or more other operations described herein.

[0082] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Described differently.

[0083] Figure 4 The present disclosure includes a network node 402 and a network node 404 performing wireless communication (eg, via a network (such as Figure 1 The network 104 depicted in FIG. 1 and / or Figure 33. A diagram of an environment 400 of the wireless network 300 depicted in FIG. 4. A network node 402 may be equipped with a set of antennas 406a to 406t, such as T antennas (T ≥ 1). A network node 404 may be equipped with a set of antennas 408a to 408r, such as R antennas (R ≥ 1).

[0084] At the network node 402, a transmit processor 410 may receive data intended for the network node 404 (or a set of network nodes 404) from a data source 412. The transmit processor 410 may select one or more modulation and coding schemes (MCS) for the network node 404 based on one or more channel quality indicators (CQIs) received from the network node 404. The network node 402 may process (e.g., encode and modulate) the data for the network node 404 based on the MCS selected for the network node 404 and provide data symbols for the network node 404. The transmit processor 410 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 410 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 414 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 416a to 416t (e.g., T modems). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem in the set of modems 416a to 416t. Each modem in the set of modems 416a to 416t may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem in the set of modems 416a to 416t may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a signal. One or more modems in the set of modems 416a to 416t may transmit a set of signals (e.g., T signals) via corresponding antennas in the set of antennas 406a to 406t. The signal may include, for example, a downlink signal.

[0085] At the network node 404, one or more antennas in the set of antennas 408a to 408r may receive signals from the network node 402 and / or the network node, and may provide a set of received signals (e.g., R received signals) to one or more modems in the set of modems 418a to 418r (e.g., R modems). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a corresponding modem in the set of modems 418a to 418r. Each modem in the set of modems 418a to 418r may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert and / or digitize) the received signal to obtain input samples. Each modem in the set of modems 418a to 418r may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. The MIMO detector 420 may obtain received symbols from one or more modems in the set of modems 418a to 418r, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols.

[0086] The receive processor 422 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the network node 404 to a data sink 424, and may provide decoded control information and system information to a controller / processor 426. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The controller / processor 426 may be, be similar to, include, or be included in Figure 2 Controller / processor 426 may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter.

[0087] The network controller 428 may include a communication unit 430, a controller / processor 432, and a memory 434. The network controller 428 may be, be similar to, include, or be included in Figure 3 4. The network controller 428 may include, for example, one or more devices in a core network. The network controller 428 may communicate with the network node 402 via a communication unit 430.

[0088] One or more antennas (e.g., antennas 406a to 406t and / or antennas 408a to 408r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 4 One or more antenna elements of one or more components in.

[0089] Similarly, at the network node 404, a transmit processor 436 may receive and process data from a data source 438 and control information from a controller / processor 426 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 436 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 436 may be pre-decoded by the TX MIMO processor 440, where applicable, and further processed by one or more modems in the set of modems 418a to 418r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 402. In some examples, each modem in the set of modems 418a to 418r of the network node 404 may include a modulator and a demodulator. In some examples, the network node 404 includes a transceiver. The transceiver may include any combination of antennas 408a to 408r, modems 418a to 418r, a MIMO detector 420, a receive processor 422, a transmit processor 436, and / or a TX MIMO processor 440. The transceiver may be, similar to, include, or be included in Figure 1 The transceiver 108 and / or Figure 2 The transceiver may be used by a processor (eg, controller / processor 426) and / or memory 442 to perform functions described herein (eg, reference Figures 7 to 13 ) or any aspects of any of the methods described herein.

[0090] At the network node 402, signals from the network node 404 and / or other network nodes may be received by one or more antennas in the set of antennas 406a to 406t, processed by one or more modems in the set of modems 416a to 416t (e.g., demodulator components, shown as DEMOD), detected by a MIMO detector 444 where applicable, and further processed by a receive processor 446 to obtain decoded data and control information transmitted by the network node 404. The receive processor 446 may provide the decoded data to a data sink 448 and the decoded control information to a controller / processor 450. The network node 402 may include a communication unit 452 and may communicate with the network controller 428 via the communication unit 452. The network node 402 may include a scheduler 454 to schedule one or more network nodes 404 for downlink communication and / or uplink communication. In some examples, one or more modems in the set of modems 416a to 416t of the network node 402 may include a modulator and a demodulator. In some examples, the network node 402 includes a transceiver. The transceiver may include any combination of antennas 406a to 406t, modems 416a to 416t, a MIMO detector 444, a receive processor 446, a transmit processor 410, and / or a TX MIMO processor 414. The transceiver may be, similar to, include, or be included in Figure 1 The transceiver 108 and / or Figure 2 The transceiver may be used by a processor (eg, controller / processor 450) and memory 456 to perform the functions described herein (eg, reference Figures 7 to 13 ) or any aspects of any of the methods described herein.

[0091] The controller / processor 450 of the network node 402, the controller / processor 426 of the network node 404, and / or Figure 4 Any other component in the network node 402 may perform one or more techniques associated with side link buffer status reporting for a multi-hop side link network, as described in more detail elsewhere herein. For example, the controller / processor 450 of the network node 402, the controller / processor 426 of the network node 404, and / or Figure 4 Any other component in can perform or direct e.g. Fig.11 Process 1100, Fig.121200 and / or operations of other processes as described herein. Memory 442 and memory 456 may store data and program codes for network node 402 and network node 404, respectively. In some examples, memory 442 and / or memory 456 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more corresponding processors of network node 402 and / or network node 404, may cause the one or more processors, network node 404, and / or network node 402 to perform or direct, for example, Fig.11 Process 1100, Fig.12 The process 1200 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0092] In some aspects, the first network node includes: a component for receiving a first sidelink communication from a second network node, the first sidelink communication including a second buffer status information associated with the second network node; and / or a component for sending a sidelink BSR indicating the second buffer status information and the first buffer status information associated with the first network node to a third network node. In some aspects, the first network node includes: a component for sending a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to the second network node; and / or a component for receiving a sidelink BSR indicating the first buffer status information associated with the second network node and the second buffer status information associated with the third network node from the second network node. In some aspects, the components for the first network node to perform the operations described herein may include, for example, one or more of the communication manager 460, the transmit processor 410, the TX MIMO processor 414, the modem 416, the antenna 406, the MIMO detector 444, the receive processor 446, the controller / processor 450, the memory 456, or the scheduler 454. In some aspects, means for the first network node to perform operations described herein may include, for example, one or more of a communication manager 458, an antenna 408, a modem 418, a MIMO detector 420, a receive processor 422, a transmit processor 436, a TX MIMO processor 440, a controller / processor 426, or a memory 442.

[0093] Although Figure 4The blocks in the 4000 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 436, the receive processor 422, and / or the TX MIMO processor 440 may be performed by or under the control of the controller / processor 426. Figure 4 Any number of other combinations of the various combinations of components depicted may be considered to be within the scope of the present disclosure.

[0094] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Described differently.

[0095] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0096] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0097] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0098] Figure 5 5 is a diagram illustrating an example disaggregated base station architecture 500 according to the present disclosure. The disaggregated base station architecture 500 may include a CU 502, which may communicate directly with a core network 504 via a backhaul link, or indirectly with the core network 504 through one or more disaggregated control units (such as a near RT RIC 506 via an E2 link, or a non-RT RIC 508 associated with a service management and orchestration (SMO) framework 510, or both). The CU 502 may communicate with one or more DUs 512 via respective midhaul links (such as via an F1 interface). The DU 512 may communicate with one or more RUs 514 via respective fronthaul links. Each of the RUs 514 may communicate with one or more UEs 516 via respective radio frequency (RF) access links. In some implementations, a UE 516 may be served simultaneously by multiple RUs 514.

[0099] Each of the units (including CU 502, DU 512, RU 514, near-RT RIC 506, non-RT RIC 508, and SMO framework 510) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0100] In some aspects, the CU 502 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 502. The CU 502 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 502 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, the CU 502 may be implemented to communicate with the DU 512 for network control and signaling.

[0101] Each DU 512 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 514. In some aspects, the DU 512 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 512 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 512 or with control functions hosted by the CU 502.

[0102] Each RU 514 may implement lower layer functionality. In some deployments, the RU 514 controlled by the DU 512 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering. In this architecture, each RU 514 may be operated to handle over-the-air (OTA) communications with one or more UEs 516. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 514 may be controlled by the corresponding DU 512. In some scenarios, this configuration may enable each DU 512 and CU 502 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0103] The SMO framework 510 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 510 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 510 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 518) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 502, DU 512, RU 514, near-RT RIC 506, and non-RT RIC 508. In some specific implementations, the SMO framework 510 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 520) via the O1 interface. Additionally, in some implementations, the SMO framework 510 can communicate directly with each of the one or more RUs 514 via a corresponding O1 interface. The SMO framework 510 can also include a non-RT RIC 508 configured to support the functionality of the SMO framework 510.

[0104] The non-RT RIC 508 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 506. The non-RT RIC 508 may be coupled to or in communication with the near-RT RIC 506 (such as via an A1 interface). The near-RT RIC 506 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 through an interface (such as via an E2 interface) that connects one or more CUs 502, one or more DUs 512, or both, and the O-eNB 520 with the near-RT RIC 506.

[0105] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 506, the non-RT RIC 508 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 506 and may be received from a non-network data source or from a network function at the SMO framework 510 or the non-RT RIC 508. In some examples, the non-RT RIC 508 or the near-RT RIC 506 may be configured to regulate RAN behavior or performance. For example, the non-RT RIC 508 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 510 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0106] In some aspects, one or more of the CU 502, DU 512, RU 514, near-RT RIC 506, non-RT RIC 508

[0107] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Described differently.

[0108] Figure 6 600 is a diagram illustrating an example of a multi-hop sidelink network according to the present disclosure. As shown, example 600 may include network node 602, network node 604, network node 606, network node 608, and network node 610.

[0109] The network node 602 and the network node 604 may communicate via a side link 612 (which may be referred to herein as a "communication link" and is shown as "link 1"). In some side link modes, the network node 604 may communicate with the network node 602 via a communication link 614 (shown as "link 2"), which may be a side link or an access link. In some aspects, the direct link (e.g., via a PC5 interface) between the network node 602 and the network node 606 (e.g., a UE and / or a relay node) may be referred to as a side link, and the direct link (e.g., via a Uu interface) between the network node 602 (e.g., a component of a base station or a decomposed base station) and the network node 604 may be referred to as an access link. Side link communications may be sent via a side link, and access link communications may be sent via an access link. Access link communications may be downlink communications (e.g., from a base station to a UE) or uplink communications (e.g., from a UE to a base station). Network node 606 may also communicate with network node 608 via side link 616 (shown as "Link 3") and may communicate with network node 610 via side link 618 (shown as "Link 4").

[0110] In the case where the network node 604 is a base station, the network node 602 may send a sidelink BSR to help the network node 604 make its scheduling decisions. In the BSR, the network node 602 may report the buffer size (e.g., the amount of data waiting to be sent) of each logical channel to the target UE. All data may be considered for the BSR, up to the packet data convergence protocol (PDCP) service data unit (SDU), for which the PDCP data protocol data unit (PDU) has not yet been constructed. The BSR may be used for a logical channel group and include multiple buffer sizes. For example, each logical channel in the BSR may correspond to a logical channel ID, a target index for receiving the target UE, and a buffer size for the target UE. The target index may be indicated by 5 bits and points to the first 32 entries of the target UE list reported to the base station via an RRC message. The network node 604 may provide a sidelink resource allocation to the UE via downlink control information (DCI) based on the BSR. However, the network node 604 may not specify the target UE in the DCI.

[0111] In some aspects, a network node (e.g., network node 602) may operate using a transmit mode (e.g., Mode 2) in which resource selection and / or scheduling is performed by network node 602 (e.g., rather than network node 604). In some aspects, network node 602 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, network node 602 may measure RSSI parameters associated with various sidelink channels (e.g., Sidelink-RSSI (S-RSSI) parameters), may measure RSRP parameters associated with various sidelink channels (e.g., PSSCH-RSRP parameters), and / or may measure RSRQ parameters associated with various sidelink channels (e.g., PSSCH-RSRQ parameters), and may select a channel for transmitting sidelink communications based at least in part on the measurements.

[0112] Additionally or alternatively, the network node 602 may perform resource selection and / or scheduling using sidelink control information (SCI) received from the network node 604, which may indicate occupied resources and / or channel parameters. Additionally or alternatively, the network node 602 may perform resource selection and / or scheduling by determining a channel busy rate (CBR) associated with each sidelink channel, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the network node 602 may use for a specified set of subframes).

[0113] In a transmission mode in which resource selection and / or scheduling is performed by the network node 602, the network node 602 may generate a sidelink grant and may transmit the grant in an SCI. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks to be used for an upcoming sidelink transmission, one or more subframes to be used for an upcoming sidelink transmission, and / or a modulation and coding scheme (MCS) to be used for an upcoming sidelink transmission. In some aspects, the network node 602 may generate a sidelink grant indicating one or more parameters for semi-persistent scheduling (SPS), such as the periodicity of the sidelink transmission. Additionally or alternatively, the network node 602 may generate a sidelink grant for event-driven scheduling (such as for an on-demand sidelink message).

[0114] In multi-hop scenarios (such as Figure 6), network node 604 may be unaware of buffer status information associated with network node 606, network node 608, and / or network node 610. In this way, network node 604 may make inappropriate (too large or too small) resource allocations for downstream network nodes, resulting in invalid and / or inefficient sidelink resource allocations, and thus negatively impacting network performance.

[0115] Some aspects of the techniques and devices described herein can facilitate side link buffer status reporting for a multi-hop side link network. In some aspects, a first network node can receive a first side link communication from a second network node, the first side link communication including second buffer status information associated with the second network node. The first network node can send a side link BSR indicating the second buffer status information and the first buffer status information associated with the first network node to a third network node. For example, network node 602 can send BSR 620 to network node 610, the BSR including buffer status information associated with network node 602 and downstream network nodes (e.g., network node 606, network node 608, and network node 604). If the first network node sends buffer status information to the second network node, the first network node is located downstream of the second network node. If the third network node sends its buffer status information in the communication direction of the first network node and the second network node, the third network node is located downstream of the first network node and the second network node, and so on.

[0116] For example, network node 608 may send buffer status information 622 associated with network node 608 to network node 606. Network node 610 may send buffer status information 624 associated with network node 610 to network node 606. Network node 606 may send a BSR 626 to network node 602, the BSR including buffer status information 622, buffer status information 624, and buffer status information associated with network node 606. Network node 602 may send a BSR 620 to network node 604, the BSR including buffer status information 622, buffer status information 624, buffer status information associated with network node 606, and buffer status information associated with network node 602.

[0117] In this way, the network node 604 can be made aware of the buffer status information of the network nodes 602, 606, 608, and 610, and can therefore make more appropriate resource allocation and scheduling decisions. For example, in a first use case, based on the buffer status information associated with different parts of the network, the network node 604 can dynamically allocate different amounts of side link resources. In a second use case, the network node 604 can schedule side link resources based on the buffer status information associated with each network node.

[0118] In some aspects, the BSR 620 may separately indicate buffer status information associated with each downstream network node. For example, as shown, a medium access control (MAC) control element (MAC CE) 628 may be used to send the BSR 620, which includes a first BSR 630 associated with the network node 602 and a kth BSR 632 associated with the kth network node among any k-1 network nodes downstream of the network node 602 (e.g., network node 606, network node 608, and network node 610). The BSR 630 may include a field 634 indicating a link identifier (ID) associated with the link 2 614, a reserved field 636, a field 638 indicating a logical channel group ID (LCGID) associated with the link 2 614, and a field 640 indicating the first buffer status information associated with the network node 602 (shown as "buffer size 1"). The buffer status information may include, for example, the size of the uplink transmit buffer (e.g., the amount of data stored in the uplink transmit buffer). The BSR 632 may include similar fields indicating the kth link ID, the kth LCGID, and the kth buffer status information associated with the kth network node. In this way, some aspects of the techniques and apparatus described herein may facilitate increased efficiency and / or effectiveness of sidelink resource allocation, thereby positively impacting network performance.

[0119] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Described differently.

[0120] Figure 7 is a diagram illustrating an example 700 associated with a side link buffer status report for a multi-hop side link network. As shown, example 700 includes network node 702, network node 704, network node 706, and network node 708. One or more of network nodes 702, 704, 706, and 708 may be, similar to, include, or be included in Figure 1 The network nodes 102A, 102B, 102C and / or 102D depicted in Figure 2 The device 200 depicted in Figure 3The network nodes 110 and / or 120 depicted in Figure 4 The network nodes 402 and / or 404 depicted in Figure 5 In some aspects, any one or more of the network nodes 702, 704, 706 and / or 708 may be similar to Figure 6 Any one or more of the network nodes 602, 604, 606, 608, and / or 610 depicted in FIG. The network nodes 702, 704, 706, and / or 708 may communicate with each other via a multi-hop side-link network.

[0121] As shown in reference numeral 710, network node 702 may send a configuration, and network node 704 may receive the configuration. In some aspects, the configuration may include a side link BSR configuration corresponding to a buffer status report for a multi-hop side link network. In some aspects, the configuration may include a side link configuration. The side link configuration may indicate a mode 1 side link configuration or a mode 2 side link configuration. In some aspects, the side link configuration may indicate a mixed mode operation associated with a mode 1 side link configuration and a mode 2 side link configuration.

[0122] As shown by reference numeral 712, the network node 706 may send buffer status information associated with the network node 706, and the network node 704 may receive the buffer status information. As shown by reference numeral 714, the network node 708 may send buffer status information associated with the network node 708, and the network node 704 may receive the buffer status information. For the purpose of description, the buffer status information associated with the network node 704 may be referred to as first buffer status information, and the buffer status information associated with the network node 706 and / or the network node 708 may be referred to as second buffer status information.

[0123] As shown by reference numeral 716, the network node 704 may determine the occurrence of at least one BSR triggering event. In some aspects, the network node 704 may determine the occurrence of at least one BSR triggering event based on receiving buffer status information from the network nodes 706 and 708 (e.g., the receipt of the buffer status information may be the triggering event). In some aspects, the network node 704 may receive a sidelink BSR from the network node 706 and / or the network node 708. The receipt of the sidelink BSR may trigger the network node 704 to forward the sidelink BSR upstream (e.g., to the network node 702) so that the network node 706 and / or the network node 708 may receive the scheduled sidelink resources from the network node 702. In some aspects, the network node 704 may receive a sidelink BSR from the network node 706 and / or the network node 708 to be relayed to another network node (e.g., the network node 702). In this case, the receipt of the sidelink BSR may also trigger the network node 704 to send a sidelink BSR, thereby relaying the sidelink BSR received from the network node 706 and / or the network node 708. In these cases, the sidelink BSR sent by the network node 704 may be referred to as a "relay sidelink BSR."

[0124] In some aspects, for example, network node 704 may receive a first relay sidelink BSR and may determine that a first sidelink resource for sending the second buffer status information is available based on receiving the first relay sidelink BSR. The sidelink BSR may indicate the second buffer status information based on determining that the first sidelink resource is available. In some aspects, network node 704 may receive sidelink data from network node 706 and / or network node 708. Receipt of the sidelink data may constitute the occurrence of a triggering event.

[0125] As shown by reference numeral 718, the network node 704 may send a sidelink BSR indicating buffer status information (e.g., second buffer status information) associated with the network node 706 and / or the network node 708 and buffer status information (e.g., first buffer status information) associated with the network node 704, and the network node 702 may receive the sidelink BSR. In some aspects, for example, the network node 704 may send the sidelink BSR based on determining the occurrence of a triggering event.

[0126] In some aspects, the network node 704 may determine whether the sidelink BSR resources are available for sending the sidelink BSR, and if so, the network node 704 may send the sidelink BSR. If the resources are not available for sending the sidelink BSR, the occurrence of a triggering event (e.g., the reception of a relay sidelink BSR) may trigger the network node 704 to send a sidelink scheduling request. For example, for a regular BSR (e.g., a BSR that is not a relay BSR), the network node 704 may be configured with a delay timer such as sl-logicalChannelSR-overSl-DelayTimer, and the timer may be started and / or restarted based on the occurrence of a regular sidelink BSR triggering event. For a relay BSR, the network node 704 may be configured with a delay timer such as sl-relayedBSR-SR-overSl-DelayTimer, and the timer may be started and / or restarted based on the occurrence of a relay sidelink BSR triggering event. In some aspects, the network node 704 may be configured with a hybrid mode sidelink configuration that facilitates the use of a combination of a mode 1 sidelink configuration and a mode 2 sidelink configuration. In such cases, the network node 704 may use Mode 2 to send a sidelink BSR without first receiving a sidelink resource grant. In this case, the sidelink BSR may serve the purpose of a sidelink scheduling request, and the corresponding sidelink data transmission may be based on the received Mode 1 sidelink resource grant.

[0127] In some aspects, the network node 704 may send the sidelink BSR by sending at least one MAC CE including the sidelink BSR. In some aspects, the at least one MAC CE may include only one MAC CE, the MAC CE including the first buffer status information and the second buffer status information. In some aspects, the at least one MAC CE may include a first MAC CE and a second MAC CE, the first MAC CE including the first buffer status information and the second MAC CE including the second buffer status information.

[0128] In some aspects, at least one format of at least one MAC CE may be based on at least one BSR trigger type of at least one BSR trigger event. For example, for conventional BSR triggering, periodic BSR triggering, and / or padding BSR triggering, the network node 704 may use a separate BSR MAC CE format. In some aspects, the format of the MAC CE may be a separate format based on a triggering event including a relay side link BSR trigger. In some aspects, at least one BSR MAC CE format may include a combined BSR MAC CE format. In some aspects, a truncated format may be used based on resource availability and / or the size of the BSR MAC CE. In some aspects, the network node 704 may send at least one MAC CE based on a priority rule associated with at least one of a side link BSR priority, a relay side link BSR priority, or an uplink BSR priority.

[0129] In some aspects, the MAC CE may include a link ID associated with a communication link associated with the network node 704. In some aspects, the side link BSR may include a first hop depth indication associated with the first buffer status information and a second hop depth indication associated with the second buffer status information. In some aspects, the side link BSR may include a logical channel group identifier (LCGID) corresponding to a relay route associated with the network node 704. The relay route may include a first communication link between the network node 704 and the network node 702 and a second communication link between the network node 704 and the network node 706. In some aspects, the LCGID may be associated with the first communication link and the second communication link. In some aspects, the LCGID may indicate a MAC CE type of the MAC CE.

[0130] In some aspects, the sidelink BSR may indicate the first buffer status information and the second buffer status information using a stack of fields ordered according to the order of the first communication link and the second communication link relative to the traffic. In some aspects, the second buffer status information may include a first value indicating the size of an uplink buffer associated with the network node 706 and / or the network node 708, and the first buffer status information may include a difference value indicating the difference between the size of the second uplink buffer and the size of the first uplink buffer associated with the network node 704. In some aspects, the MAC CE may indicate a first link ID corresponding to the first communication link between the network node 704 and the network node 702 and a second link ID corresponding to the communication link between the network node 704 and the network node 706 and / or the network node 708. In some aspects, one of the first link ID or the second link ID may include a logical channel group ID, and the other of the first link ID or the second link ID may include a layer 2 ID.

[0131] As shown by reference numeral 720, the network node 702 may send a grant indicating a set of sidelink resources, and the network node 704 may receive the grant. The grant may correspond to a specified aggregate buffer size, such as an aggregate buffer size indicated in a sidelink BSR. In some aspects, the network node 704 may associate a first subset of sidelink resources in the set of sidelink resources with the first buffer status information. For example, the network node 704 may use the first subset of sidelink resources to send sidelink data from an uplink buffer corresponding to the first buffer status information.

[0132] As shown in the figure numeral 722, the network node 704 may send a downstream side link grant indicating a second subset of the side link resources in the side link resource set, and the network node 706 may receive the downstream side link grant. The second subset of the side link resources may include the difference between the side link resource set and the first subset of the side link resources. Similarly, the network node 706 may use a subset of the second subset of the side link resources to send side link data from its uplink buffer, and may forward any remaining side link resources in the downstream side link grant to another network node downstream of the network node 706. In some aspects, the network node 702 may send a first grant indicating a first set of side link resources corresponding to the first buffer state information and a second grant indicating a second set of side link resources corresponding to the second buffer state information. The second grant may be received by the network node 706 from the network node 702, or may be forwarded to the network node 706 by the network node 704.

[0133] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Described differently.

[0134] Figure 8 800 is a diagram illustrating an example of a side link buffer status report for a multi-hop side link network according to the present disclosure. Figure 7 The various aspects described herein are associated with a MAC CE that individually indicates buffer status information associated with multiple downstream network nodes. Example 800 includes, for example, Figure 7 The network node 706 depicted in FIG. Figure 7 8. The BSR 804 may be sent from the network node 708 to the network node 704.

[0135] As shown, the first BSR 802 may be part of a MAC CE that includes a field 806 indicating a link ID (shown as "Link 3 ID") that identifies a communication link between the network node 706 and the network node 704. The first BSR 802 may also include a field 808 that includes a hop depth indication associated with buffer status information associated with the network node 706. In some aspects, a reserved bit may be used to indicate the hop depth indication. The hop depth indication is shown as "depth 0" because a network node (e.g., network node 706) may set the hop depth of its own buffer to 0 and may increase the hop depth of any BSR received from a downstream node by 1. The BSR 802 may include a field 810 that indicates an LCGID corresponding to a relay route associated with the network node 706. The BSR 802 may include a field 812 that indicates buffer status information associated with the network node 706 (e.g., shown as a buffer size of 100).

[0136] Similarly, BSR 804 may include the same fields shown in conjunction with BSR 802, which indicate corresponding information associated with network node 708. For example, BSR 804 may indicate a link ID (shown as "Link4ID") that identifies a communication link between network node 708 and network node 704. BSR 804 may include a hop depth indication showing a hop depth of 0, an LCGID corresponding to a relay route, and buffer status information associated with network node 708 (shown as "100").

[0137] As shown, network node 704 may send MAC CE 814 that individually indicates buffer status information associated with network nodes 706, 708, and 704. For example, as shown, MAC CE 814 may include BSR 802, BSR 804, and BSR 816 associated with network node 704. In BSRs 802 and 804, the hop depth indicator may be set to "1", and the hop depth indicator of BSR 816 may be set to "0".

[0138] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 Described differently.

[0139] Fig. 9 is a diagram illustrating an example 900 of a side link buffer status report for a multi-hop side link network according to the present disclosure. Example 900 is combined with Figure 7The various aspects described are associated, wherein the MAC CE individually indicates buffer status information associated with multiple downstream network nodes. In some aspects, the first relay route may be associated with a first group of communication links (e.g., a communication link between network node 706 and network node 704 and a communication link between network node 704 and network node 702), and the second relay route may be associated with a second group of communication links (e.g., a communication link between network node 708 and network node 704 and a communication link between network node 704 and network node 702). Each specific relay route may be associated with a unique corresponding LCGID. In this case, in some aspects, the LCGID can be used to indicate the entire route, and the link ID of each link can be omitted from the MAC CE, thereby facilitating more efficient buffer status reporting.

[0140] As shown, for example, the network node 706 may send a MAC CE 902 that includes a reserved field 904, a field 906 indicating an LCGID, and a field 908 indicating buffer status information associated with the network node 706. The network node 704 may add a field 910 including buffer status information associated with the network node 704 to the MAC CE 902. If the network node 702 also forwards a sidelink BSR, the network node 702 may add a field 912 including buffer status information associated with the network node 702 to the MAC CE 902. In some aspects, the LCGID used may be associated with different routes, but may be mapped to the LCGID along the route. In some aspects, the reserved field 904 may be used to indicate the number of hops. In some aspects, differential decoding may be used to encode the difference in buffer size along the route to further reduce the number of bits used for the sidelink BSR. In some aspects, buffer status information associated with two or more different routes may be included in the MAC CE 902, and the LCGID may be used to distinguish them.

[0141] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 Described differently.

[0142] Fig.10 1 is a diagram illustrating an example 1000 of a side link buffer status report for a multi-hop side link network according to the present disclosure. Example 1000 is combined with Figure 7The various aspects described are associated with a MAC CE indicating buffer status information associated with multiple downstream network nodes in an aggregated form. Example 1000 includes a portion of a MAC CE including a reserved field 1002, a field 1004 indicating an LCGID associated with the reported buffer status information, and a field 1006 indicating aggregated buffer status information (shown as "aggregate buffer size").

[0143] Aggregate buffer state information can be an aggregation of the buffer size associated with the network node sending the side link BSR and the buffer size of one or more downstream network nodes. The source ID can uniquely identify the network node along the multi-hop route. In some aspects, the LCGID can be set to the LCGID associated with the communication link along the route, and the communication link includes the highest quality of service (QoS) in the communication link. In some aspects, the BSR bit can be mapped to a buffer size range rather than an exact buffer size via a table. For example, BSR 52 may refer to a buffer size greater than or equal to 249 bytes and less than or equal to 264 bytes. In some aspects, when the aggregate buffer size, the network node 704 can use the lower limit (e.g., minimum value) or its upper limit of the corresponding mapping size range.

[0144] In some aspects, the SL BSR of the network node may separately indicate the aggregate forwarding buffer size and the network node's own buffer size. In some aspects, a bit in the reserved field 1002 may be used to indicate whether the corresponding buffer status information is associated with the network node that sent the side link BSR or whether the corresponding buffer status information is associated with a downstream network node. In some aspects, the reserved bit may be used to indicate a hop depth.

[0145] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 Described differently.

[0146] Fig.11 is a diagram illustrating an example process 1100 performed, for example, by a first network node in accordance with the present disclosure. Example process 1100 is an example in which a first network node (eg, network node 704) performs operations associated with sidelink buffer status reporting for a multi-hop sidelink network.

[0147] like Fig.11 As shown, in some aspects, process 1100 may include receiving a first sidelink communication from a second network node, the first sidelink communication including second buffer status information associated with the second network node (block 1110). For example, the first network node (e.g., using Fig.13The communication manager 1308 and / or receiving component 1302 depicted in FIG. 1 may receive a first side link communication from a second network node, the first side link communication including second buffer status information associated with the second network node, as described above.

[0148] like Fig.11 As further shown, in some aspects, process 1100 may include sending a sidelink BSR indicating the second buffer status information and the first buffer status information associated with the first network node to a third network node (block 1120). Fig.13 The communication manager 1308 and / or the sending component 1304 depicted in FIG. 1 may send a sidelink BSR indicating the second buffer status information and the first buffer status information associated with the first network node to the third network node, as described above.

[0149] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0150] In some aspects, the first network node comprises a UE, and the third network node comprises a base station. In some aspects, the second buffer status information is indicated separately from the first buffer status information. In some aspects, the sending side link BSR comprises sending a side link MAC CE.

[0151] In some aspects, the MAC CE includes a link ID associated with a communication link associated with the first network node in the multi-hop sidelink network. In some aspects, the link ID corresponds to a first traffic direction in a pair of traffic directions associated with the communication link, and the additional link ID corresponds to a second traffic direction in the pair of traffic directions. In some aspects, the sidelink BSR includes a traffic direction indication indicating a traffic direction in a pair of traffic directions associated with the communication link. In some aspects, the traffic direction indication includes a reserved bit of the sidelink MAC CE.

[0152] In some aspects, the MAC CE includes a sidelink BSR set, wherein the sidelink BSR set includes the sidelink BSR. In some aspects, the MAC CE includes a first subset of the sidelink BSRs in the sidelink BSR set, wherein the sidelink BSR set includes the sidelink BSR, and process 1100 includes sending an additional MAC CE including a second subset of the sidelink BSRs in the sidelink BSR set. In some aspects, the sidelink BSR includes a first hop depth indication associated with the first buffer status information and a second hop depth indication associated with the second buffer status information. In some aspects, sending the sidelink BSR includes sending a sidelink MAC CE, wherein the MAC CE includes one or more reserved bits, wherein the one or more reserved bits include the first hop depth indication and the second hop depth indication.

[0153] In some aspects, the sidelink BSR includes an LCGID corresponding to a relay route associated with the first network node. In some aspects, the relay route includes a first communication link between the first network node and the third network node and a second communication link between the first network node and the second network node, wherein the LCGID is associated with the first communication link and the second communication link, and wherein the sidelink BSR indicates the first buffer status information and the second buffer status information using a stack of fields ordered according to the order of the first communication link and the second communication link relative to the traffic direction. In some aspects, at least one additional LCGID is associated with at least one communication link of the relay route, and the at least one additional LCGID is mapped to the LCGID. In some aspects, the sidelink BSR includes a reserved bit indicating the number of hops associated with the relay route.

[0154] In some aspects, the second buffer status information includes a first value indicating a size of a second uplink buffer associated with the second network node, and the first buffer status information includes a difference value indicating a difference between the size of the second uplink buffer and the size of a first uplink buffer associated with the first network node. In some aspects, the transmit side link BSR includes a transmit side link MAC CE, wherein the MAC CE indicates a first link ID corresponding to a first communication link between the first network node and the third network node and a second link ID corresponding to a communication link between the first network node and the second network node, and one of the first link ID or the second link ID includes a logical channel group ID, and the other of the first link ID or the second link ID includes a layer 2 ID.

[0155] In some aspects, the sidelink BSR includes an aggregated BSR including an aggregated buffer size indication indicating an aggregation of a first buffer size associated with the first buffer status information and a second buffer size associated with the second buffer status information. In some aspects, the aggregated BSR includes a source ID corresponding to at least one of the first network node or the second network node. In some aspects, the first LCGID corresponds to a first communication link between the first network node and the third network node, and the second LCGID corresponds to a second communication link between the first network node and the second network node, wherein the aggregated BSR includes an indicated LCGID of the first LCGID and the second LCGID, wherein the indicated LCGID is based at least in part on a QoS value. In some aspects, the aggregated buffer size indication corresponds to an upper limit or a lower limit of a range indicated in a buffer size mapping table.

[0156] In some aspects, process 1100 includes: receiving a grant indicating a set of sidelink resources corresponding to a specified aggregated buffer size; associating a first subset of sidelink resources in the set of sidelink resources with first buffer state information; and sending a downstream sidelink grant indicating a second subset of sidelink resources in the set of sidelink resources to a second network node, wherein the second subset of sidelink resources includes a difference between the set of sidelink resources and the first subset of sidelink resources. In some aspects, the aggregated BSR also includes an indication of the first buffer size. In some aspects, the aggregated BSR also includes an indication of a forward downstream buffer size, the forward downstream buffer size including a second buffer size. In some aspects, the aggregated BSR includes an indication of a first hop depth corresponding to the first buffer size and an indication of a second hop depth corresponding to the forward downstream buffer size. In some aspects, the aggregated BSR includes a reserved bit indicating whether to indicate a forward downstream buffer size, the forward downstream buffer size including a second buffer size.

[0157] In some aspects, process 1100 includes: receiving a first grant indicating a first set of side link resources corresponding to first buffer status information; and receiving a second grant indicating a second set of side link resources corresponding to second buffer status information. In some aspects, the side link BSR includes an aggregated BSR, and the second buffer status information includes aggregated buffer status information associated with the second network node and at least one additional network node. In some aspects, the transmit side link BSR includes a transmit side link MAC CE, and a logical channel group identifier associated with at least one of a first communication link between the first network node and the third network node or a second communication link between the first network node and the second network node indicates a MAC CE type of the MAC CE.

[0158] In some aspects, sending the sidelink BSR includes sending a first sidelink MAC CE and a second sidelink MAC CE, wherein the first sidelink MAC CE includes first buffer status information and the second sidelink MAC CE includes second buffer status information. In some aspects, the first sidelink communication includes a downstream sidelink BSR, and sending the sidelink BSR includes sending the sidelink BSR based on receiving the downstream sidelink BSR. In some aspects, process 1100 includes receiving sidelink data from a second network node, and sending the sidelink BSR includes sending the sidelink BSR based on receiving the sidelink data.

[0159] In some aspects, process 1100 includes determining the occurrence of at least one BSR triggering event, wherein sending a sidelink BSR includes sending at least one sidelink MAC CE, wherein at least one BSR MAC CE format of the at least one MAC CE is based on at least one BSR triggering type of the at least one BSR triggering event. In some aspects, at least one BSR MAC CE format includes a combined BSR MAC CE format. In some aspects, sending at least one MAC CE includes sending at least one MAC CE based on a priority rule associated with at least one of a sidelink BSR priority, a relay sidelink BSR priority, or an uplink BSR priority. In some aspects, the first buffer status information includes buffer status information associated with multiple logical channels. In some aspects, the second buffer status information includes buffer status information associated with at least one additional network node.

[0160] In some aspects, sending the sidelink BSR includes sending at least one sidelink MAC CE, wherein the MAC CE includes a truncated BSR MAC CE based on at least one of a number of sidelink resources available to carry the MAC CE or a size of the MAC CE. In some aspects, the truncated BSR MAC CE includes a truncated set of buffer status information, wherein the truncated set of buffer status information indicates the first buffer status information and the second buffer status information based on at least one of a logical channel group priority, a priority associated with the first buffer status information, or a priority associated with the second buffer status information.

[0161] In some aspects, receiving the first sidelink communication includes receiving a first relay sidelink BSR trigger, and process 1100 includes determining that a first sidelink resource for sending a second buffer status information is available based on receiving the first relay sidelink BSR trigger, wherein the sidelink BSR indicates the second buffer status information based on determining that the first sidelink resource is available. In some aspects, process 1100 includes: receiving a second relay sidelink BSR trigger associated with third buffer status information; determining that a second sidelink resource for sending the third buffer status information is not available; and based on determining that the second sidelink resource is not available to send a sidelink scheduling request associated with the third buffer status information. In some aspects, process 1100 includes starting at least one of a logical channel scheduling request timer or a relay BSR scheduling request timer. In some aspects, process 1100 includes receiving a sidelink configuration indicating a mixed mode operation associated with a mode 1 sidelink configuration and a mode 2 sidelink configuration, wherein sending the sidelink BSR includes sending the sidelink BSR based on the mode 2 sidelink configuration.

[0162] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0163] Fig.12 is a diagram illustrating an example process 1200 performed, for example, by a first network node in accordance with the present disclosure. Example process 1200 is an example in which a first network node (eg, network node 702) performs operations associated with sidelink buffer status reporting for a sidelink multi-hop network.

[0164] like Fig.12 As shown, in some aspects, process 1200 may include sending a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to a second network node (block 1210). Fig.13 The communication manager 1308 and / or the sending component 1304 depicted in FIG. 1 may send a sidelink BSR configuration corresponding to a buffer status report for a multi-hop sidelink network to the second network node, as described above.

[0165] like Fig.12As further shown, in some aspects, process 1200 may include receiving a sidelink BSR from a second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node (block 1220). Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in FIG. 1 may receive a sidelink BSR from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with the third network node, as described above.

[0166] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0167] In some aspects, the first network node includes a base station and the second network node includes a user equipment. In some aspects, the second buffer status information is indicated separately from the first buffer status information. In some aspects, the receiving side link BSR includes a receiving side link MAC CE. In some aspects, the MAC CE includes a link ID associated with a communication link associated with the second network node. In some aspects, the link ID corresponds to a first service direction in a pair of service directions associated with the communication link, and the additional link ID corresponds to a second service direction in the pair of service directions. In some aspects, the side link BSR includes a service direction indication indicating a service direction in a pair of service directions associated with the communication link. In some aspects, the service direction indication includes a reserved bit of the side link MAC CE.

[0168] In some aspects, the MAC CE includes a sidelink BSR set, wherein the sidelink BSR set includes the sidelink BSR. In some aspects, the MAC CE includes a first subset of the sidelink BSRs in the sidelink BSR set, wherein the sidelink BSR set includes the sidelink BSR, and process 1200 includes receiving an additional MAC CE including a second subset of the sidelink BSRs in the sidelink BSR set. In some aspects, the sidelink BSR includes a first hop depth indication associated with the first buffer status information and a second hop depth indication associated with the second buffer status information. In some aspects, receiving the sidelink BSR includes receiving a sidelink MAC CE, wherein the MAC CE includes one or more reserved bits, wherein the one or more reserved bits include the first hop depth indication and the second hop depth indication.

[0169] In some aspects, the sidelink BSR includes an LCGID corresponding to a relay route associated with the second network node. In some aspects, the relay route includes a first communication link between the first network node and the second network node and a second communication link between the second network node and the third network node, wherein the LCGID is associated with the first communication link and the second communication link, and wherein the sidelink BSR indicates the first buffer status information and the second buffer status information using a stack of fields ordered according to the order of the first communication link and the second communication link relative to the traffic direction. In some aspects, at least one additional LCGID is associated with at least one communication link of the relay route, and the at least one additional LCGID is mapped to the LCGID. In some aspects, the sidelink BSR includes a reserved bit indicating the number of hops associated with the relay route.

[0170] In some aspects, the second buffer status information includes a first value indicating a size of a first uplink buffer associated with the third network node, and the first buffer status information includes a difference value indicating a difference between the size of the first uplink buffer and the size of a second uplink buffer associated with the second network node. In some aspects, the receive side link BSR includes a receive side link MAC CE, wherein the MAC CE indicates a first link ID corresponding to a first communication link between the first network node and the second network node and a second link ID corresponding to a communication link between the second network node and the third network node, and one of the first link ID or the second link ID includes a logical channel group ID, and the other of the first link ID or the second link ID includes a layer 2 ID.

[0171] In some aspects, the sidelink BSR includes an aggregated BSR including an aggregated buffer size indication indicating an aggregation of a first buffer size associated with the first buffer status information and a second buffer size associated with the second buffer status information. In some aspects, the aggregated BSR includes a source ID corresponding to at least one of the second network node or the third network node. In some aspects, the first LCGID corresponds to a first communication link between the first network node and the second network node, and the second LCGID corresponds to a second communication link between the second network node and the third network node, wherein the aggregated BSR includes an indicated LCGID of the first LCGID and the second LCGID, wherein the indicated LCGID is based at least in part on a QoS value. In some aspects, the aggregated buffer size indication corresponds to an upper limit or a lower limit of a range indicated in a buffer size mapping table.

[0172] In some aspects, process 1200 includes: sending a first grant indicating a first set of sidelink resources corresponding to the first buffer status information; and sending a second grant indicating a second set of sidelink resources corresponding to the second buffer status information. In some aspects, the sidelink BSR includes an aggregated BSR, and the second buffer status information includes aggregated buffer status information associated with the third network node and at least one additional network node. In some aspects, the receive sidelink BSR includes a receive sidelink MAC CE, and a logical channel group identifier associated with at least one of the first communication link between the first network node and the second network node or the second communication link between the second network node and the third network node indicates a MAC CE type of the MAC CE.

[0173] In some aspects, receiving the sidelink BSR includes receiving a first sidelink MAC CE and a second sidelink MAC CE, wherein the first sidelink MAC CE includes first buffer status information and the second sidelink MAC CE includes second buffer status information. In some aspects, the first buffer status information includes buffer status information associated with a plurality of logical channels. In some aspects, the second buffer status information includes buffer status information associated with at least one additional network node.

[0174] In some aspects, receiving the sidelink BSR includes sending at least one sidelink MAC CE, wherein the MAC CE includes a truncated BSR MAC CE based on at least one of a number of sidelink resources available to carry the MAC CE or a size of the MAC CE. In some aspects, the truncated BSR MAC CE includes a truncated set of buffer status information, wherein the truncated set of buffer status information indicates the first buffer status information and the second buffer status information based on at least one of a logical channel group priority, a priority associated with the first buffer status information, or a priority associated with the second buffer status information. In some aspects, process 1200 includes sending a sidelink configuration indicating a mixed mode operation associated with a mode 1 sidelink configuration and a mode 2 sidelink configuration, wherein receiving the sidelink BSR includes receiving the sidelink BSR based on the mode 2 sidelink configuration.

[0175] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be performed in parallel.

[0176] Fig.131 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network node, or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 1308. Communication manager 1308 may include a determining component 1310.

[0177] In some aspects, the apparatus 1300 may be configured to perform Figures 7 to 10 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 Process 1100, Fig.12 In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 4 One or more components of one or more of the described network nodes. Additionally or alternatively, Fig.13 One or more of the components shown in the figure may be combined with Figure 4 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0178] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1306. The receiving component 1302 may provide the received communications to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may include combining Figure 4 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of one or more of the described network nodes.

[0179] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include a combination of Figure 4 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of one or more of the described network nodes. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0180] The communication manager 1308 and / or the receiving component 1302 may receive a first side link communication from a second network node, the first side link communication including second buffer status information associated with the second network node. In some aspects, the communication manager 1308 may include in conjunction with Figure 4 One or more antennas, modems, controllers / processors, memories, or combinations thereof, of one or more of the described network nodes. In some aspects, the communications manager 1308 may include the receiving component 1302 and / or the sending component 1304. In some aspects, the communications manager 1308 may be, be similar to, include, or be included in Figure 1 In the communication manager 106 depicted in .

[0181] The communication manager 1308 and / or the sending component 1304 may send a sidelink BSR indicating the second buffer status information and the first buffer status information associated with the first network node to the third network node. The communication manager 1308 and / or the receiving component 1302 may receive a grant indicating a set of sidelink resources corresponding to the specified aggregated buffer size. The communication manager 1308 may associate a first subset of sidelink resources in the set of sidelink resources with the first buffer status information. The communication manager 1308 and / or the sending component 1304 may send a downstream sidelink grant indicating a second subset of sidelink resources in the set of sidelink resources to the second network node, wherein the second subset of sidelink resources includes a difference between the set of sidelink resources and the first subset of sidelink resources.

[0182] The communication manager 1308 and / or the receiving component 1302 may receive a first grant indicating a first set of sidelink resources corresponding to the first buffer status information. The communication manager 1308 and / or the receiving component 1302 may receive a second grant indicating a second set of sidelink resources corresponding to the second buffer status information. The communication manager 1308 and / or the receiving component 1302 may receive sidelink data from the second network node, and sending the sidelink BSR includes sending the sidelink BSR based on receiving the sidelink data.

[0183] The communication manager 1308 and / or the determining component 1310 can determine the occurrence of at least one BSR triggering event, wherein sending the sidelink BSR includes sending at least one sidelink MAC CE, wherein at least one BSRMAC CE format of the at least one MAC CE is based on at least one BSR triggering type of the at least one BSR triggering event. In some aspects, the determining component 1310 can include combining Figure 4 One or more antennas, modems, controllers / processors, memory, or a combination thereof of one or more of the described network nodes. In some aspects, determining component 1310 may include receiving component 1302 and / or sending component 1304.

[0184] The communication manager 1308 and / or the receiving component 1302 may receive a second relay side link BSR trigger associated with the third buffer status information. The communication manager 1308 and / or the determining component 1310 may determine that the second side link resource for sending the third buffer status information is unavailable. The communication manager 1308 and / or the sending component 1304 may be based on determining that the second side link resource is not available to send a side link scheduling request associated with the third buffer status information. The communication manager 1308 and / or the communication manager 1308 may start at least one of a logical channel scheduling request timer or a relay BSR scheduling request timer. The communication manager 1308 and / or the receiving component 1302 may receive a side link configuration indicating a mixed mode operation associated with a mode 1 side link configuration and a mode 2 side link configuration, wherein sending a side link BSR includes sending a side link BSR based on a mode 2 side link configuration.

[0185] The communication manager 1308 and / or the sending component 1304 may send a side link BSR configuration corresponding to a buffer status report for a multi-hop side link network to the second network node. The communication manager 1308 and / or the receiving component 1302 may receive a side link BSR indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node from the second network node. The communication manager 1308 and / or the sending component 1304 may send a first grant indicating a first set of side link resources corresponding to the first buffer status information. The communication manager 1308 and / or the sending component 1304 may send a second grant indicating a second set of side link resources corresponding to the second buffer status information. The communication manager 1308 and / or the sending component 1304 may send a side link configuration indicating a mixed mode operation associated with a mode 1 side link configuration and a mode 2 side link configuration, wherein receiving the side link BSR includes receiving the side link BSR based on the mode 2 side link configuration.

[0186] Fig.13 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.13 Two or more components shown in may be implemented in a single component, or Fig.13 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The collection of (one or more) components shown in can perform the operations described by Fig.13 One or more functions performed by another component collection shown in .

[0187] The following provides an overview of some aspects of the disclosure:

[0188] Aspect 1: A method of wireless communication performed by a first network node, comprising: receiving a first side link communication from a second network node, the first side link communication including second buffer status information associated with the second network node; and sending a side link buffer status report (BSR) indicating the second buffer status information and first buffer status information associated with the first network node to a third network node.

[0189] Aspect 2: The method according to aspect 1, wherein the second buffer status information is indicated separately from the first buffer status information.

[0190] Aspect 3: The method according to any one of aspects 1 or 2, wherein sending the sidelink BSR includes sending a sidelink medium access control (MAC) control element (MAC CE).

[0191] Aspect 4: The method according to aspect 3, wherein the MAC CE includes a link identifier (ID) associated with a communication link associated with the first network node in a multi-hop sidelink network.

[0192] Aspect 5: A method according to aspect 4, wherein the link ID corresponds to a first service direction of a pair of service directions associated with the communication link, and wherein an additional link ID corresponds to a second service direction of the pair of service directions.

[0193] Aspect 6: A method according to any one of Aspects 4 or 5, wherein the sidelink BSR includes a traffic direction indication indicating a traffic direction of a pair of traffic directions associated with the communication link.

[0194] Aspect 7: The method according to Aspect 6, wherein the service direction indication includes a reserved bit of the sidelink MAC CE.

[0195] Aspect 8: The method according to any one of aspects 3 to 7, wherein the MAC CE includes a sidelink BSR set, wherein the sidelink BSR set includes the sidelink BSR.

[0196] Aspect 9: A method according to any one of Aspects 3 to 8, wherein the MAC CE includes a first subset of sidelink BSRs in a sidelink BSR set, the sidelink BSR set includes the sidelink BSR, and the method further includes sending an additional MAC CE including a second subset of sidelink BSRs in the sidelink BSR set.

[0197] Aspect 10: The method according to any one of aspects 1 to 9, wherein the first network node comprises a user equipment, and the third network node comprises a base station.

[0198] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the sidelink BSR comprises a first hop depth indication associated with the first buffer status information and a second hop depth indication associated with the second buffer status information.

[0199] Aspect 12: A method according to Aspect 11, wherein sending the sidelink BSR includes sending a sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE includes one or more reserved bits, and the one or more reserved bits include the first hop depth indication and the second hop depth indication.

[0200] Aspect 13: The method according to any one of aspects 1 to 12, wherein the sidelink BSR includes a logical channel group identifier (LCGID) corresponding to a relay route associated with the first network node.

[0201] Aspect 14: A method according to Aspect 13, wherein the relay route includes a first communication link between the first network node and the third network node and a second communication link between the first network node and the second network node, wherein the LCGID is associated with the first communication link and the second communication link, and wherein the sidelink BSR uses a stack of fields sorted according to the order of the first communication link and the second communication link relative to the service direction to indicate the first buffer status information and the second buffer status information.

[0202] Aspect 15: The method according to any one of Aspects 13 or 14, wherein at least one additional LCGID is associated with at least one communication link of the relay route, and wherein the at least one additional LCGID is mapped to the LCGID.

[0203] Aspect 16: The method according to any one of aspects 13 to 15, wherein the sidelink BSR includes a reserved bit indicating the number of hops associated with the relay route.

[0204] Aspect 17: A method according to any one of Aspects 1 to 16, wherein the second buffer status information includes a first value indicating the size of a second uplink buffer associated with the second network node, and wherein the first buffer status information includes a difference value indicating the difference between the size of the second uplink buffer and the size of a first uplink buffer associated with the first network node.

[0205] Aspect 18: A method according to any one of Aspects 1 to 17, wherein sending the sidelink BSR includes sending a sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE indicates a first link identifier (ID) corresponding to a first communication link between the first network node and the third network node and a second link ID corresponding to a communication link between the first network node and the second network node, and wherein one of the first link ID or the second link ID includes a logical channel group ID, and the other of the first link ID or the second link ID includes a layer 2 ID.

[0206] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the sidelink BSR includes an aggregated BSR, the aggregated BSR includes an aggregated buffer size indication, and the aggregated buffer size indication indicates an aggregation of a first buffer size associated with the first buffer status information and a second buffer size associated with the second buffer status information.

[0207] Aspect 20: The method according to aspect 19, wherein the aggregated BSR includes a source identifier (ID) corresponding to at least one of the first network node or the second network node.

[0208] Aspect 21: A method according to any one of Aspects 19 or 20, wherein a first logical channel group ID (LCGID) corresponds to a first communication link between the first network node and the third network node, and a second LCGID corresponds to a second communication link between the first network node and the second network node, wherein the aggregated BSR includes an indication LCGID in the first LCGID and the second LCGID, wherein the indication LCGID is at least partially based on a quality of service (QoS) value.

[0209] Aspect 22: The method according to any one of aspects 19 to 21, wherein the aggregate buffer size indication corresponds to an upper limit or a lower limit of a range indicated in a buffer size mapping table.

[0210] Aspect 23: The method according to any one of Aspects 19 to 22 further includes: receiving a grant indicating a side link resource set corresponding to a specified aggregated buffer size; associating a first subset of side link resources in the side link resource set with the first buffer status information; and sending a downstream side link grant indicating a second subset of side link resources in the side link resource set to the second network node, wherein the second subset of side link resources includes the difference between the side link resource set and the first subset of side link resources.

[0211] Aspect 24: The method according to Aspect 23, wherein the aggregated BSR further includes an indication of the first buffer size.

[0212] Aspect 25: The method according to Aspect 24, wherein the aggregated BSR further includes an indication of a forwarding downstream buffer size, the forwarding downstream buffer size including the second buffer size.

[0213] Aspect 26: The method according to aspect 25, wherein the aggregated BSR includes an indication of a first hop depth corresponding to the first buffer size and an indication of a second hop depth corresponding to the forwarding downstream buffer size.

[0214] Aspect 27: The method according to any one of aspects 24 to 26, wherein the aggregated BSR includes a reserved bit indicating whether to indicate a forwarding downstream buffer size, and the forwarding downstream buffer size includes the second buffer size.

[0215] Aspect 28: The method according to any one of Aspects 1 to 27 further includes: receiving a first grant indicating a first set of side link resources corresponding to the first buffer status information; and receiving a second grant indicating a second set of side link resources corresponding to the second buffer status information.

[0216] Aspect 29: The method according to aspect 28, wherein the sidelink BSR comprises an aggregated BSR, and wherein the second buffer status information comprises aggregated buffer status information associated with the second network node and at least one additional network node.

[0217] Aspect 30: A method according to any one of Aspects 1 to 29, wherein sending the sidelink BSR includes sending a sidelink medium access control (MAC) control element (MAC CE), and wherein a logical channel group identifier associated with at least one of the first communication link between the first network node and the third network node or the second communication link between the first network node and the second network node indicates a MAC CE type of the MAC CE.

[0218] Aspect 31: A method according to any one of Aspects 1 to 30, wherein sending the sidelink BSR includes sending a first sidelink medium access control (MAC) control element (MAC CE) and a second sidelink MAC CE, wherein the first sidelink MAC CE includes the first buffer status information, and the second sidelink MAC CE includes the second buffer status information.

[0219] Aspect 32: A method according to any one of Aspects 1 to 31, wherein the first sidelink communication includes a downstream sidelink BSR, and wherein sending the sidelink BSR includes sending the sidelink BSR based on receiving the downstream sidelink BSR.

[0220] Aspect 33: The method according to any one of Aspects 1 to 32 further includes receiving sidelink data from the second network node, and wherein sending the sidelink BSR includes sending the sidelink BSR based on receiving the sidelink data.

[0221] Aspect 34: The method according to any one of Aspects 1 to 33 also includes determining the occurrence of at least one BSR triggering event, wherein sending the sidelink BSR includes sending at least one sidelink medium access control (MAC) control element (MAC CE), wherein at least one BSR MAC CE format of the at least one MAC CE is based on at least one BSR triggering type of the at least one BSR triggering event.

[0222] Aspect 35: The method according to aspect 34, wherein the at least one BSR MAC CE format comprises a combined BSR MAC CE format.

[0223] Aspect 36: A method according to any one of Aspects 34 or 35, wherein sending the at least one MAC CE comprises sending the at least one MAC CE based on a priority rule associated with at least one of a sidelink BSR priority, a relay sidelink BSR priority, or an uplink BSR priority.

[0224] Aspect 37: The method according to any one of Aspects 1 to 36, wherein the first buffer status information comprises buffer status information associated with a plurality of logical channels.

[0225] Aspect 38: The method according to any one of aspects 1 to 37, wherein the second buffer status information comprises buffer status information associated with at least one additional network node.

[0226] Aspect 39: A method according to any one of Aspects 1 to 38, wherein sending the sidelink BSR includes sending at least one sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE includes a truncated BSRMAC CE based on at least one of the number of sidelink resources that can be used to carry the MAC CE or the size of the MAC CE.

[0227] Aspect 40: A method according to Aspect 39, wherein the truncated BSR MAC CE includes a truncated buffer status information set, wherein the truncated buffer status information set indicates the first buffer status information and the second buffer status information based on at least one of a logical channel group priority, a priority associated with the first buffer status information, or a priority associated with the second buffer status information.

[0228] Aspect 41: A method according to any one of Aspects 1 to 40, wherein receiving the first side link communication includes receiving a first relay side link BSR trigger, and the method also includes determining that a first side link resource for sending the second buffer status information is available based on receiving the first relay side link BSR trigger, wherein the side link BSR indicates the second buffer status information based on determining that the first side link resource is available.

[0229] Aspect 42: The method according to Aspect 41 also includes: receiving a second relay side link BSR trigger associated with third buffer status information; determining that a second side link resource for sending the third buffer status information is unavailable; and sending a side link scheduling request associated with the third buffer status information based on determining that the second side link resource is not available.

[0230] Aspect 43: The method according to Aspect 42 further comprises starting at least one of a logical channel scheduling request timer or a relay BSR scheduling request timer.

[0231] Aspect 44: The method according to any one of Aspects 1 to 43 further includes receiving a side link configuration indicating a mixed mode operation associated with a mode 1 side link configuration and a mode 2 side link configuration, wherein sending the side link BSR includes sending the side link BSR based on the mode 2 side link configuration.

[0232] Aspect 45: A method of wireless communication performed by a first network node, comprising: sending a sidelink buffer status report (BSR) configuration corresponding to a buffer status report for a multi-hop sidelink network to a second network node; and receiving a sidelink BSR from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node.

[0233] Aspect 46: The method according to Aspect 45, wherein the second buffer status information is indicated separately from the first buffer status information.

[0234] Aspect 47: The method according to any one of aspects 45 or 46, wherein receiving the sidelink BSR includes receiving a sidelink medium access control (MAC) control element (MAC CE).

[0235] Aspect 48: The method of aspect 47, wherein the MAC CE comprises a link identifier (ID) associated with a communication link associated with the second network node.

[0236] Aspect 49: A method according to Aspect 48, wherein the link ID corresponds to a first service direction of a pair of service directions associated with the communication link, and wherein an additional link ID corresponds to a second service direction of the pair of service directions.

[0237] Aspect 50: A method according to any one of Aspects 48 or 49, wherein the sidelink BSR includes a traffic direction indication indicating a traffic direction of a pair of traffic directions associated with the communication link.

[0238] Aspect 51: The method according to aspect 50, wherein the traffic direction indication comprises a reserved bit of the sidelink MAC CE.

[0239] Aspect 52: A method according to any one of aspects 47 to 51, wherein the MAC CE includes a sidelink BSR set, wherein the sidelink BSR set includes the sidelink BSR.

[0240] Aspect 53: A method according to any one of Aspects 47 to 52, wherein the MAC CE includes a first subset of sidelink BSRs in a sidelink BSR set, the sidelink BSR set includes the sidelink BSR, and the method also includes receiving an additional MAC CE including a second subset of sidelink BSRs in the sidelink BSR set.

[0241] Aspect 54: A method according to any one of aspects 45 to 53, wherein the first network node comprises a base station and the second network node comprises a user equipment.

[0242] Aspect 55: A method according to any one of Aspects 45 to 54, wherein the sidelink BSR comprises a first hop depth indication associated with the first buffer status information and a second hop depth indication associated with the second buffer status information.

[0243] Aspect 56: A method according to Aspect 55, wherein receiving the sidelink BSR includes receiving a sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE includes one or more reserved bits, and the one or more reserved bits include the first hop depth indication and the second hop depth indication.

[0244] Aspect 57: A method according to any one of aspects 45 to 56, wherein the sidelink BSR comprises a logical channel group identifier (LCGID) corresponding to a relay route associated with the second network node.

[0245] Aspect 58: A method according to Aspect 57, wherein the relay route includes a first communication link between the first network node and the second network node and a second communication link between the second network node and the third network node, wherein the LCGID is associated with the first communication link and the second communication link, and wherein the sidelink BSR uses a stack of fields sorted according to the order of the first communication link and the second communication link relative to the service direction to indicate the first buffer status information and the second buffer status information.

[0246] Aspect 59: A method according to any one of Aspects 57 or 58, wherein at least one additional LCGID is associated with at least one communication link of the relay route, and wherein the at least one additional LCGID is mapped to the LCGID.

[0247] Aspect 60: A method according to any one of aspects 57 to 59, wherein the sidelink BSR includes a reserved bit indicating the number of hops associated with the relay route.

[0248] Aspect 61: A method according to any one of Aspects 45 to 60, wherein the second buffer status information includes a first value indicating the size of a first uplink buffer associated with the third network node, and wherein the first buffer status information includes a difference value indicating the difference between the size of the first uplink buffer and the size of a second uplink buffer associated with the second network node.

[0249] Aspect 62: A method according to any one of Aspects 45 to 61, wherein receiving the side link BSR includes receiving a side link medium access control (MAC) control element (MAC CE), wherein the MAC CE indicates a first link identifier (ID) corresponding to a first communication link between the first network node and the second network node and a second link ID corresponding to a communication link between the second network node and the third network node, and wherein one of the first link ID or the second link ID includes a logical channel group ID, and the other of the first link ID or the second link ID includes a layer 2 ID.

[0250] Aspect 63: A method according to any one of Aspects 45 to 62, wherein the sidelink BSR includes an aggregated BSR, the aggregated BSR includes an aggregated buffer size indication, and the aggregated buffer size indication indicates an aggregation of a first buffer size associated with the first buffer status information and a second buffer size associated with the second buffer status information.

[0251] Aspect 64: The method according to aspect 63, wherein the aggregated BSR includes a source identifier (ID) corresponding to at least one of the second network node or the third network node.

[0252] Aspect 65: A method according to any one of Aspects 63 or 64, wherein a first logical channel group ID (LCGID) corresponds to a first communication link between the first network node and the second network node, and a second LCGID corresponds to a second communication link between the second network node and the third network node, wherein the aggregated BSR includes an indication LCGID in the first LCGID and the second LCGID, wherein the indication LCGID is at least partially based on a quality of service (QoS) value.

[0253] Aspect 66: A method according to any one of aspects 63 to 65, wherein the aggregate buffer size indication corresponds to an upper limit or a lower limit of a range indicated in a buffer size mapping table.

[0254] Aspect 67: The method according to any one of Aspects 45 to 66 also includes: sending a first grant indicating a first set of side link resources corresponding to the first buffer status information; and sending a second grant indicating a second set of side link resources corresponding to the second buffer status information.

[0255] Aspect 68: The method according to aspect 67, wherein the sidelink BSR comprises an aggregated BSR, and wherein the second buffer status information comprises aggregated buffer status information associated with the third network node and at least one additional network node.

[0256] Aspect 69: A method according to any one of Aspects 45 to 68, wherein receiving the sidelink BSR includes receiving a sidelink medium access control (MAC) control element (MAC CE), and wherein a logical channel group identifier associated with at least one of a first communication link between the first network node and the second network node or a second communication link between the second network node and the third network node indicates a MAC CE type of the MAC CE.

[0257] Aspect 70: A method according to any one of Aspects 45 to 69, wherein receiving the side link BSR includes receiving a first side link medium access control (MAC) control element (MAC CE) and a second side link MAC CE, wherein the first side link MAC CE includes the first buffer status information, and the second side link MAC CE includes the second buffer status information.

[0258] Aspect 71: A method according to any one of aspects 45 to 70, wherein the first buffer status information comprises buffer status information associated with a plurality of logical channels.

[0259] Aspect 72: The method according to any one of aspects 45 to 71, wherein the second buffer status information comprises buffer status information associated with at least one additional network node.

[0260] Aspect 73: A method according to any one of Aspects 45 to 72, wherein receiving the sidelink BSR includes sending at least one sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE includes a truncated BSRMAC CE based on at least one of the number of sidelink resources that can be used to carry the MAC CE or the size of the MAC CE.

[0261] Aspect 74: A method according to Aspect 73, wherein the truncated BSR MAC CE includes a truncated buffer status information set, wherein the truncated buffer status information set indicates the first buffer status information and the second buffer status information based on at least one of a logical channel group priority, a priority associated with the first buffer status information, or a priority associated with the second buffer status information.

[0262] Aspect 75: The method according to any one of Aspects 45 to 74 further includes sending a side link configuration indicating a mixed mode operation associated with a mode 1 side link configuration and a mode 2 side link configuration, wherein receiving the side link BSR includes receiving the side link BSR based on the mode 2 side link configuration.

[0263] Aspect 76: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 44.

[0264] Aspect 77: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 44.

[0265] Aspect 78: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 44.

[0266] Aspect 79: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 44.

[0267] Aspect 80: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of aspects 1 to 44.

[0268] Aspect 81: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 45 to 75.

[0269] Aspect 82: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 45 to 75.

[0270] Aspect 83: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 45 to 75.

[0271] Aspect 84: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 45 to 75.

[0272] Aspect 85: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 45 to 75.

[0273] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0274] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0275] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0276] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0277] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more projects, and can be used interchangeably with "one or more". If you only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (wherein "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A", unless specifically recorded differently. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and can be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A first network node for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a first sidelink communication from a second network node, the first sidelink communication comprising second buffer status information associated with the second network node; as well as A sidelink buffer status report (BSR) is sent to a third network node indicating the second buffer status information and first buffer status information associated with the first network node. 2 . The first network node according to claim 1 , wherein the second buffer status information is indicated separately from the first buffer status information.

3. The first network node of claim 1 , wherein to send the sidelink BSR, the one or more processors are configured to send a sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE includes a link identifier (ID) associated with a communication link associated with the first network node in a multi-hop sidelink network. 4 . The first network node of claim 1 , wherein the first network node comprises a user equipment and the third network node comprises a base station. 5 . The first network node of claim 1 , wherein the sidelink BSR comprises a first hop depth indication associated with the first buffer status information and a second hop depth indication associated with the second buffer status information.

6. The first network node of claim 1, wherein the sidelink BSR comprises a logical channel group identifier (LCGID) corresponding to a relay route associated with the first network node.

7. The first network node of claim 6, wherein the relay route comprises a first communication link between the first network node and the third network node and a second communication link between the first network node and the second network node, wherein the LCGID is associated with the first communication link and the second communication link, and wherein the sidelink BSR indicates the first buffer status information and the second buffer status information using a stack of fields ordered according to an order of the first communication link and the second communication link relative to a traffic direction.

8. The first network node of claim 1 , wherein the second buffer status information comprises a first value indicating a size of a second uplink buffer associated with the second network node, and wherein the first buffer status information comprises a difference value indicating a difference between the size of the second uplink buffer and a size of a first uplink buffer associated with the first network node.

9. A first network node according to claim 1, wherein in order to send the side link BSR, the one or more processors are configured to send a side link medium access control (MAC) control element (MAC CE), wherein the MAC CE indicates a first link identifier (ID) corresponding to a first communication link between the first network node and the third network node and a second link ID corresponding to a communication link between the first network node and the second network node, and wherein one of the first link ID or the second link ID includes a logical channel group ID, and the other of the first link ID or the second link ID includes a layer 2 ID.

10. The first network node of claim 1 , wherein the sidelink BSR comprises an aggregated BSR comprising an aggregated buffer size indication indicating an aggregation of a first buffer size associated with the first buffer status information and a second buffer size associated with the second buffer status information.

11. The first network node of claim 10, wherein the one or more processors are further configured to: receiving a grant indicating a set of sidelink resources corresponding to a specified aggregated buffer size; associating a first subset of sidelink resources in the set of sidelink resources with the first buffer status information; and A downstream sidelink grant indicating a second subset of sidelink resources in the set of sidelink resources is sent to the second network node, wherein the second subset of sidelink resources comprises a difference between the set of sidelink resources and the first subset of sidelink resources.

12. The first network node of claim 1 , wherein the one or more processors are further configured to: receiving a first grant indicating a first set of sidelink resources corresponding to the first buffer status information; and A second grant indicating a second set of sidelink resources corresponding to the second buffer status information is received.

13. The first network node of claim 1 , wherein, to send the sidelink BSR, the one or more processors are configured to send a sidelink medium access control (MAC) control element (MAC CE), and wherein a logical channel group identifier associated with at least one of a first communication link between the first network node and the third network node or a second communication link between the first network node and the second network node indicates a MAC CE type of the MAC CE.

14. The first network node of claim 1 , wherein to send the sidelink BSR, the one or more processors are configured to send a first sidelink medium access control (MAC) control element (MAC CE) and a second sidelink MAC CE, wherein the first sidelink MAC CE includes the first buffer status information and the second sidelink MAC CE includes the second buffer status information.

15. The first network node of claim 1, wherein the first sidelink communication comprises a downstream sidelink BSR, and wherein sending the sidelink BSR comprises sending the sidelink BSR based on receiving the downstream sidelink BSR.

16. The first network node of claim 1 , wherein the one or more processors are further configured to receive sidelink data from the second network node, and wherein to send the sidelink BSR, the one or more processors are configured to send the sidelink BSR based on receiving the sidelink data.

17. The first network node of claim 1 , wherein the one or more processors are further configured to determine an occurrence of at least one BSR triggering event, and wherein to send the sidelink BSR, the one or more processors are configured to send at least one sidelink medium access control (MAC) control element (MAC CE), wherein at least one BSR MAC CE format of the at least one MAC CE is based on at least one BSR triggering type of the at least one BSR triggering event.

18. The first network node of claim 17, wherein the at least one BSR MAC CE format comprises a combined BSR MAC CE format.

19. The first network node according to claim 17, wherein, in order to send the at least one MAC CE, the one or more processors are configured to send the at least one MAC CE based on a priority rule associated with at least one of a sidelink BSR priority, a relay sidelink BSR priority, or an uplink BSR priority.

20. The first network node of claim 1, wherein the first buffer status information comprises buffer status information associated with a plurality of logical channels.

21. The first network node of claim 1, wherein the second buffer status information comprises buffer status information associated with at least one additional network node.

22. The first network node of claim 1 , wherein to send the sidelink BSR, the one or more processors are configured to send at least one sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE comprises a truncated BSR MAC CE based on at least one of a number of sidelink resources that can be used to carry the MAC CE or a size of the MAC CE.

23. The first network node of claim 1 , wherein to receive the first sidelink communication, the one or more processors are configured to receive a first relay sidelink BSR trigger, and wherein the one or more processors are further configured to determine that a first sidelink resource for sending the second buffer status information is available based on receiving the first relay sidelink BSR trigger, wherein the sidelink BSR indicates the second buffer status information based on determining that the first sidelink resource is available.

24. A first network node according to claim 1, wherein the one or more processors are further configured to receive a side link configuration indicating a mixed mode operation associated with a mode 1 side link configuration and a mode 2 side link configuration, and wherein in order to send the side link BSR, the one or more processors are configured to send the side link BSR based on the mode 2 side link configuration.

25. A first network node for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: sending a sidelink buffer status report (BSR) configuration corresponding to a buffer status report for the multi-hop sidelink network to the second network node; and A sidelink BSR is received from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node.

26. The first network node of claim 25, wherein to receive the sidelink BSR, the one or more processors are configured to receive a sidelink medium access control (MAC) control element (MAC CE).

27. A method of wireless communication performed by a first network node, comprising: receiving a first sidelink communication from a second network node, the first sidelink communication comprising second buffer status information associated with the second network node; as well as A sidelink buffer status report (BSR) is sent to a third network node indicating the second buffer status information and first buffer status information associated with the first network node.

28. The method of claim 27, wherein sending the sidelink BSR comprises sending a sidelink medium access control (MAC) control element (MAC CE), wherein the MAC CE comprises a link identifier (ID) associated with a communication link associated with the first network node in a multi-hop sidelink network.

29. A method of wireless communication performed by a first network node, comprising: sending a sidelink buffer status report (BSR) configuration corresponding to a buffer status report for the multi-hop sidelink network to the second network node; as well as A sidelink BSR is received from the second network node indicating first buffer status information associated with the second network node and second buffer status information associated with a third network node.

30. The method of claim 29, wherein receiving the sidelink BSR comprises receiving a sidelink medium access control (MAC) control element (MAC CE).

Images