Buffer status reporting and scheduling grant for target UE in sidelink relay

Abstract

Methods and apparatus for BSR and scheduling grant for a target UE in a sidelink relay. The apparatus receives a request for sidelink communication from a target UE. The apparatus receives a first BSR from the target UE via the sidelink communication. The apparatus transmits a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or a sidelink BSR of the relay UE. The apparatus receives a resource allocation for the sidelink communication with the target UE based on the second BSR. The apparatus uses the resource allocation to communicate with the target UE via the sidelink communication.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 664,146, entitled “BUFFERSTATUS REPORT AND SCHEDULING GRANT FOR TARGET UE IN SIDELINK RELAY” and filed on May 19, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to configurations for transmitting a buffer status report (BSR) and scheduling grants for a target user equipment (UE) in a sidelink relay. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5GNR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a relay UE. The apparatus may be a processor and / or a modem at a relay UE, or the relay UE itself. The apparatus receives a request for sidelink communication from a target UE. The apparatus receives a first buffer status report (BSR) from the target UE via the sidelink communication. The apparatus sends a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE. The apparatus receives a resource allocation for the sidelink communication with the target UE based on the second BSR. The apparatus uses the resource allocation to communicate with the target UE via the sidelink communication.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a target UE. The apparatus may be a processor and / or a modem at the target UE, or the target UE itself. The apparatus sends a request for sidelink communication with a relay UE. The apparatus sends a first BSR to the relay UE via the sidelink communication. The apparatus communicates with the relay UE via the sidelink communication using a resource allocation based at least on the first BSR.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2 Example aspects of a sidelink slot structure are illustrated.

[0012] Figure 3 is a diagram illustrating an example of a first device and a second device involved in wireless communication based on, for example, a side link.

[0013] Figure 4Example aspects of sidelink communications between devices according to various aspects presented herein are illustrated.

[0014] Figure 5 An example of a sidelink BSR within a MAC-CE in accordance with various aspects presented herein is illustrated.

[0015] Figure 6 An example of a sidelink BSR in accordance with various aspects presented herein is illustrated.

[0016] Figure 7 An example of a MAC-CE including multiple BSRs in accordance with various aspects presented herein is illustrated.

[0017] Figure 8 is a call flow diagram 800 of signaling between a relay UE and a target UE.

[0018] Fig. 9 is a flow chart of a method of wireless communication.

[0019] Fig.10 is a flow chart of a method of wireless communication.

[0020] Fig.11 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0021] Fig.12 is a flow chart of a method of wireless communication.

[0022] Fig.13 is a flow chart of a method of wireless communication.

[0023] Fig.14 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0024] In sidelink communication (e.g., mode 1), resource allocation may be provided by a network entity so that the network entity determines resources for sidelink communication between UEs. For example, a sidelink transmission UE may transmit a sidelink BSR to a network entity, and the network entity responds by transmitting a sidelink grant indicating resources to be used for sidelink transmission to the sidelink transmission UE based on the sidelink BSR. However, in some cases, the quality of the direct link between the sidelink transmission UE and the network entity may be poor or blocked. In such cases, the network entity may utilize a relay UE to forward uplink or downlink data to the sidelink transmission UE. In some other cases, there is no direct link between the sidelink transmission UE and the network entity, so that the sidelink transmission UE cannot provide a sidelink BSR to the network entity. In order for the network entity to schedule resources for the sidelink transmission UE to transmit data to the relay UE, the network entity will need a sidelink BSR from the sidelink transmission UE. The sidelink transmission UE may have a sidelink connection with the relay UE 506, but cannot utilize the relay UE to relay the sidelink BSR to the network entity.

[0025] Aspects presented herein provide a configuration for providing a sidelink BSR of a target UE to a network entity in a sidelink relay configuration. Aspects presented herein may allow a relay UE to provide a BSR from a target UE to a network entity to configure sidelink communication resources.

[0026] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0027] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any 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.

[0028] By way of example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described in this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0029] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, clustered or disaggregated components, end-user devices, etc.

[0031] 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 radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS) or one or more units (or one or more components) that perform base station functionality) can be implemented in a clustered or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as a clustered base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0032] A clustered base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0034] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0035] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0036] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0037] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 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 (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0038] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DUs 130 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting such as lower layer functional splitting. In such an architecture, the RUs 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 140 may be controlled by the corresponding DUs 130. In some scenarios, this configuration may enable the DUs 130 and CUs 110 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0039] The SMO framework 105 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 105 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 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) 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 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

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

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

[0042] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0043] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0044] Some examples of sidelink communications may include communications that may be from vehicle to vehicle (V2V), vehicle to infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle to network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle to pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof, and / or vehicle-based communication devices communicating with other devices, which may be collectively referred to as vehicle-to-everything (V2X) communications. Sidelink communications may be based on V2X or other D2D communications, such as proximity services (ProSe), etc. In addition to the UE, sidelink communications may also be sent and received by other transmitting devices and receiving devices, such as a roadside unit (RSU) 107, etc. The PC5 interface may be used to exchange sidelink communications, such as in conjunction with Figure 2 Although the examples in Figure 2 The following description of an example time slot structure may provide examples for sidelink communications related to 5G NR, but the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0045] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0046] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, 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).

[0047] 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 FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0048] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0049] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0050] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include a decomposed base station and / or a clustered base station may be referred to as a next generation (NG) RAN (NG-RAN).

[0051] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, positioning determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the positioning of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0052] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0053] Reference again Figure 1 In certain aspects, the relay UE 104 may include a BSR component 198 configured to: receive a request for sidelink communication from a target UE; receive a first buffer status report (BSR) from the target UE via the sidelink communication; send a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE; receive a resource allocation for sidelink communication with the target UE based on the second BSR; and communicate with the target UE via the sidelink communication using the resource allocation.

[0054] Reference again Figure 1 In certain aspects, the target UE 104 may include a BSR component 199 configured to: send a request for sidelink communication with a relay UE; send a first BSR to the relay UE via the sidelink communication; and communicate with the relay UE via the sidelink communication using a resource allocation based at least on the first BSR.

[0055] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] Figure 2Diagrams 200 and 210 are included that illustrate example aspects of a slot structure that may be used for sidelink communications (e.g., between UE 104, RSU 107, etc.). In some examples, the slot structure may be within a 5G / NR frame structure. In other examples, the slot structure may be within an LTE frame structure. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. Figure 2 The example time slot structure in is only an example, and other side link communications may have different frame structures and / or different channels for side link communications. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a micro time slot, which may include 7, 4 or 2 symbols. Each time slot may contain 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Figure 200 illustrates a single resource block transmitted in a single time slot corresponding to a 0.5ms transmission time interval (TTI), for example. The physical side link control channel may be configured to occupy multiple physical resource blocks (PRBs), for example, 10, 12, 15, 20 or 25 PRBs. PSCCH may be limited to a single subchannel. For example, the PSCCH duration may be configured to be 2 symbols or 3 symbols. For example, a subchannel may include 10, 15, 20, 25, 50, 75, or 100 PRBs. Resources for sidelink transmissions may be selected from a resource pool including one or more subchannels. As a non-limiting example, a resource pool may include between 1 and 27 subchannels. A PSCCH size may be established for a resource pool, for example, between 10%-100% of a subchannel within a duration of 2 symbols or 3 symbols. Figure 2 Diagram 210 in illustrates an example in which the PSCCH occupies approximately 50% of a subchannel as an example to illustrate the concept of the PSCCH occupying a portion of a subchannel. A physical sidelink shared channel (PSSCH) occupies at least one subchannel. In some examples, the PSCCH may include a first portion of sidelink control information (SCI), and the PSSCH may include a second portion of the SCI.

[0057] A resource grid may be used to represent the frame structure. Each time slot may include a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. Figure 2As shown, some of the REs may include control information in the PSCCH and some of the REs may include a demodulation RS (DMRS). At least one symbol may be used for feedback. Figure 2 An example is illustrated having two symbols for a physical sidelink feedback channel (PSFCH) with adjacent gap symbols. Symbols before and / or after the feedback may be used to transition between reception of data and transmission of feedback. The gap enables the device to switch from operating as a transmitting device to preparing to operate as a receiving device, for example, in a subsequent time slot. As illustrated, data may be sent in the remaining REs. The data may include data messages as described herein. The location of any of the data, DMRS, SCI, feedback, gap symbols, and / or LBT symbols may be different from Figure 2 Illustrated example. In some aspects, multiple time slots can be grouped together.

[0058] Figure 3 3 is a block diagram of a first wireless communication device 310 communicating with a second wireless communication device 350 based on a side link. In some examples, devices 310 and 350 may communicate based on V2X or other D2D communications. The communication may be based on a side link using a PC5 interface. Devices 310 and 350 may include UEs, RSUs, base stations, etc. Packets may be provided to a controller / processor 375 that implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.

[0059] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the device 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0060] At the device 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the device 350. If multiple spatial streams are destined for the device 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the device 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by device 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0061] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. The controller / processor 359 may provide demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0062] Similar to the functionality described in conjunction with the transmission performed by the device 310, the controller / processor 359 may provide RRC layer functionality associated with system information (e.g., MIB, SIB) collection, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0063] Channel estimates derived by a channel estimator 358 from a reference signal or feedback sent by the device 310 may be used by a TX processor 368 to select an appropriate coding and modulation scheme, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0064] Transmissions are processed at device 310 in a manner similar to that described in connection with the receiver functionality at device 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to a RX processor 370.

[0065] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. The controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0066] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The 198 came to execute all aspects.

[0067] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 199 to perform all aspects.

[0068] Figure 4 An example 400 of sidelink communication between devices is illustrated. The communication may be based on a combination of Figure 2 The time slot structure of each aspect described. For example, UE 402 may send a sidelink transmission 414 that can be received by UE 404, 406, 408, for example, the sidelink transmission includes a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH). The control channel may include information for decoding the data channel (e.g., sidelink control information (SCI)), which includes reservation information, such as information about the time and / or frequency resources reserved for data channel transmission. For example, SCI may indicate the TTI and the number of RBs that will be occupied by the data transmission. SCI can also be used by the receiving device to avoid interference by avoiding transmission on the reserved resources. In addition to sidelink reception, UE 402, 404, 406, 408 may each be able to perform sidelink transmission. Therefore, UE 404, 406, 408 is illustrated as sending sidelink transmissions 413, 415, 416, 420. The sidelink transmissions 413, 414, 415, 416, 420 may be unicast, broadcast, or multicast to nearby devices. For example, UE 404 may transmit sidelink transmissions 413, 415 intended to be received by other UEs within range 401 of UE 404, and UE 406 may transmit sidelink transmission 416. Additionally / alternatively, RSU 407 may receive communications from UE 402, 404, 406, 408 and / or transmit communications 418 to these UEs. One or more of UE 402, 404, 406, 408 or RSU 407 may include, for example, a combination of Figure 1 The BSR component 198 described.

[0069] Sidelink communication may be based on resource allocation mechanisms of different types or modes. In a first resource allocation mode (which may be referred to herein as "mode 1"), centralized resource allocation may be provided by a network entity. For example, a base station 102 may determine resources for sidelink communication, and may allocate resources to different UEs 104 for sidelink transmission. In this first mode, the UE receives a sidelink resource allocation from the base station 102. In a second resource allocation mode (which may be referred to herein as "mode 2"), distributed resource allocation may be provided. In mode 2, each UE may autonomously determine resources for sidelink transmission. In order to coordinate the selection of sidelink resources by each UE, each UE may use a listening technique to monitor the resource reservations of other sidelink UEs, and may select resources for sidelink transmission from unreserved resources. A device communicating based on a sidelink may determine one or more radio resources used by other devices in the time domain and the frequency domain in order to select transmission resources that avoid conflicts with other devices. Sidelink transmissions and / or resource reservations may be periodic or aperiodic, where the UE may reserve resources for transmission in the current slot and up to two future slots (as discussed below).

[0070] Thus, in this second mode (e.g., Mode 2), each UE may autonomously select resources for sidelink transmission, e.g., without a central entity (such as a base station indicating resources for the device). A first UE may reserve the selected resources in order to inform other UEs about the resources that the first UE intends to use for sidelink transmission.

[0071] In some examples, resource selection for sidelink communication can be based on a listening-based mechanism. For example, before selecting resources for data transmission, the UE can first determine whether the resources have been reserved by other UEs.

[0072] For example, as part of the listening mechanism for resource allocation mode 2, the UE may determine (e.g., listen) whether the selected side link resource has been reserved by other UEs before selecting the side link resource for data transmission. If the UE determines that the side link resource has not been reserved by other UEs, the UE may use the selected side link resource for sending data, for example, in PSSCH transmission. The UE may estimate or determine which radio resources (e.g., side link resources) may be in use and / or reserved by other UEs by detecting and decoding the side link control information (SCI) sent by other UEs. The UE may estimate or determine which radio resources are in use and / or reserved by other UEs using a resource selection algorithm based on listening. The UE may receive an SCI from another UE, the SCI including reservation information based on a resource reservation field included in the SCI. The UE may continuously monitor (e.g., listen) and decode the SCI from a peer UE. The SCI may include reservation information, for example, indicating that a particular UE has selected a time slot and RB for future transmission. The UE may exclude resources used and / or reserved by other UEs from the candidate resource set used by the UE for sidelink transmission, and the UE may select / reserve resources for sidelink transmission from resources that are not used and thus form the candidate resource set. The UE may continuously perform listening on the SCI with resource reservations in order to maintain a candidate resource set from which the UE may select one or more resources for sidelink transmission. Once the UE selects a candidate resource, the UE may send an SCI indicating its own reservation of resources for sidelink transmission. The number of resources (e.g., subchannels per subframe) reserved by the UE may depend on the size of the data to be sent by the UE. Although this example is described with respect to a UE receiving reservation information from another UE, the reservation information may also be received from an RSU or other device communicating based on a sidelink.

[0073] In sidelink communications (e.g., Mode 1), resource allocation may be provided by a network entity such that the network entity determines resources to be used for sidelink communications between UEs. For example, a sidelink transmitting UE may transmit a sidelink BSR 502 to the network entity, and the network entity responds by transmitting a sidelink grant indicating resources to be used for sidelink transmission to the sidelink transmitting UE based on the sidelink BSR 502. The sidelink BSR 502 may be within a MAC-CE, such as Figure 5 500. In some cases, a sidelink transmitting UE may have multiple receiving UEs in a sidelink transmission. BSR 502 identifies the receiving UE, the logical channel group identifier, and the buffer size for each destination.

[0074] However, in some cases, the quality of the direct link between the sidelink transmission UE and the network entity may be poor or blocked. In such cases, the network entity 504 may utilize the relay UE 506 to forward uplink or downlink data to the sidelink transmission UE (e.g., the target UE 508). In some other cases, there is no direct link between the sidelink transmission UE 508 and the network entity 504, so that the sidelink transmission UE 508 cannot provide the sidelink BSR to the network entity. In order for the network entity to schedule resources for the sidelink transmission UE 508 to transmit data to the relay UE 506, the network entity 504 will need a sidelink BSR from the sidelink transmission UE 508. The sidelink transmission UE 508 may have a sidelink connection with the relay UE 506, but cannot utilize the relay UE 506 to relay the sidelink BSR to the network entity 504.

[0075] It is desirable for the network entity to control the sidelink resources used for the sidelink communication between the relay UE 506 and the target UE 508. For example, the interference caused by the sidelink between the relay UE 506 and the target UE 508 to the link (e.g., Uu) between the relay UE 506 and the network entity 504 may be limited or reduced. In addition, it is desirable for the network entity 504 to avoid scheduling downlink transmissions to the relay UE 506 and the target UE 508 to transmit uplink data to the relay UE 506 at the same time slot. Therefore, in order for the network entity 504 to allocate resources for the relay UE 506, the buffer status of the relay UE 506 should be notified to the network entity 504. In the case where the relay UE 506 is about to transmit data to the target UE 508, the relay UE 506 may transmit a sidelink BSR to the network entity 504 to request sidelink resources. However, in the case where the target UE 508 is to transmit data to the target UE 508 , the target UE 508 cannot provide the sidelink BSR to the network entity 504 , and cannot relay the sidelink BSR via the relay UE 506 .

[0076] Various aspects presented herein provide a configuration for providing a sidelink BSR of a target UE to a network entity in a sidelink relay configuration. Various aspects presented herein may allow a relay UE to provide a BSR from a target UE to a network entity to configure sidelink communication resources. At least one advantage of the present disclosure is that a network entity may be able to further limit or reduce interference caused by a sidelink link between a relay UE and a target UE. At least another advantage of the present disclosure is that a network entity may have further control over sidelink resources between a relay UE and a target UE, and may be able to avoid scheduling data conflicts between a relay UE and a target UE.

[0077] Figure 6An example of a sidelink BSR of a target UE is provided. The target UE may have a sidelink connection with a relay UE but not a connection with a network entity, while the relay UE has a connection with the network entity (e.g., Uu). The sidelink target UE may transmit its sidelink BSR to the relay UE so that the relay UE may provide the sidelink target UE to the network entity. The target UE may use the sidelink MAC-CE to send the sidelink BSR to the relay UE, such as Figure 6 As shown in diagram 600 of FIG. 602, the sidelink BSR may include an LCG ID and a buffer size. The LCG ID may indicate the logical channel group corresponding to the service in the buffer.

[0078] The relay UE may transmit the sidelink BSR of the target UE to the network entity. For example, the relay UE may use a Uu uplink MAC-CE to transmit the sidelink BSR of the target UE to the network entity. The MAC-CE may utilize a format similar to the sidelink BSR MAC-CE, which includes a new field of LCG ID to indicate that the Uu uplink MAC-CE is a sidelink BSR of the target UE, where the target UE ID is set to the destination ID.

[0079] In some cases, a relay UE may have its own BSR and the BSRs of one or more target UEs that the relay UE must provide to the network entity, but there may be only one resource available for transmitting one BSR report. In such cases, a priority may be utilized to determine which BSR report to transmit to the network entity. For example, the priority may indicate that the BSR of the relay UE is higher than the BSR of the target UE, the BSR of the target UE is higher than the BSR of the relay UE, the BSR with a larger buffer size has priority, or a combination thereof. In some aspects, the network entity may allocate different resources for the relay UE to transmit the BSR report to the relay UE and the BSR report to the target UE.

[0080] Figure 7 An example of a MAC-CE including multiple BSRs is provided. In some aspects, a relay UE may include a BSR for the relay UE and a BSR for one or more target UEs. For example, referring to Figure 7700, MAC-CE 702 may include a BSR for a relay UE and a BSR for one or more target UEs. MAC-CE 702 may include the BSR for the relay UE at the beginning, followed by the BSR for the one or more target UEs. For example, LCG ID 1 may indicate a logical channel group corresponding to the BSR for the relay UE and a buffer size 1 corresponding to the traffic in the buffer for the relay UE. Destination ID 1 may identify the relay UE. The BSR for the one or more target UEs may follow and be identified accordingly. The number of BSRs for the one or more target UEs may be indicated in the first octet of MAC-CE 702.

[0081] The network entity may utilize DCI (e.g., DCI 3_0) to grant sidelink resources to the relay UE so that the relay UE forwards downlink data from the network entity to the target UE. The network entity may transmit a sidelink resource grant for receiving sidelink data to the relay UE based on the BSR of the relay UE and / or one or more target UEs so that the relay UE receives uplink data from the target UE. The relay UE may forward the grant received from the network entity to the target UE to allow the target UE to send its uplink data to the relay UE via the sidelink transmission. Then, the target UE may provide the uplink data of the target UE to the network entity. In some aspects, the grant from the network entity may be included in the DCI (e.g., DCI 3_0), and a bit may be used to indicate whether the grant is for sidelink transmission or sidelink reception. In some aspects, the grant from the network entity may be included in the downlink MAC-CE. The relay UE may forward the grant to the target UE via the sidelink MAC-CE. The base station may transmit a sidelink resource grant so that the relay UE forwards the grant to the target UE, such that the target UE receives the grant from the relay UE and transmits uplink data to the relay UE as scheduled.

[0082] Figure 8 8 is a call flow diagram 800 of signaling between a relay UE 802 and a target UE 804. The UE 802 may be configured to communicate with a base station (not shown). Figure 1 In the context of , the relay UE 802 may correspond to at least the UE 104, and the target UE 804 may correspond to at least the UE 104. In another example, Figure 3 In the context of , target UE 804 may correspond to device 310 and UE 802 may correspond to device 350.

[0083] At 806, target UE 804 may send a request for sidelink communications. Target UE may send a request for sidelink communications with relay UE 802. Relay UE 802 may receive the request for sidelink communications from target UE 804.

[0084] At 808, the target UE 804 UE may send a first BSR to the relay UE 802. The target UE 804 may send the first BSR to the relay UE 802 via sidelink communication. The relay UE 802 may receive the first BSR from the target UE 804. In some aspects, the first BSR may be sent via a sidelink MAC-CE. The first BSR may be sent to the relay UE via a sidelink MAC-CE.

[0085] At 810, the relay UE 802 may receive a grant including resources for sending a second BSR. The relay UE 802 may receive a grant including resources for sending a second BSR from a network entity (not shown). The grant may include different resources for the relay UE to send information corresponding to the first BSR of the target UE or the sidelink BSR of the relay UE.

[0086] At 812, the relay UE 802 may send a second BSR to a network entity (not shown). The second BSR may include information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE. In some aspects, the second BSR may be sent via a MAC-CE. A logical channel identifier (LCID) within the header of the MAC-CE may indicate that the second BSR is associated with at least one of the target UE or the relay UE. In some aspects, the second BSR may include information corresponding to the first BSR. The second BSR may include a logical channel group identifier (LCGID) that may indicate that the logical channel group (LCG) within the second BSR corresponds to the service information of the target UE. In some aspects, the second BSR may include information corresponding to the sidelink BSR of the relay UE. The second BSR may include an LCGID that may indicate that the LCG within the second BSR corresponds to the service information of the relay UE. In some aspects, information corresponding to the first BSR of the target UE and the sidelink BSR of the relay UE may be sent separately. The sending of the first BSR of the target UE and the sidelink BSR of the relay UE may be based on a priority for determining which one is transmitted first. In some aspects, the second BSR may include the first BSR of the target UE and the sidelink BSR of the relay UE. The second BSR may be ordered to include the sidelink BSR of the relay UE first, followed by the first BSR of the target UE.

[0087] At 814, the relay UE 802 may receive a resource allocation for sidelink communications with the target UE 804. The relay UE 802 may receive the resource allocation for sidelink communications with the target UE 804 from a network entity (not shown). The relay UE may receive the resource allocation for sidelink communications with the target UE based on the second BSR.

[0088] At 816, UE 802 may relay the resource allocation for the sidelink communication. The relay UE may relay the resource allocation for the sidelink communication to the target UE 804. The target UE 804 may receive the resource allocation for the sidelink communication from the relay UE 802.

[0089] At 818, relay UE 802 may communicate via sidelink communication with target UE 804. Relay UE 802 may use the resource allocation to communicate via sidelink communication with target UE 804. The target UE may communicate via sidelink communication with the relay UE using the resource allocation based on at least the first BSR.

[0090] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a relay UE (e.g., UE 104; device 1104). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the relay UE to provide a BSR from a target UE to a network entity to configure sidelink communication resources.

[0091] At 902, the relay UE may receive a request for a sidelink communication. For example, 902 may be performed by the BSR component 198 of the device 1104. The relay UE may receive a request for a sidelink communication from a target UE.

[0092] At 904, the relay UE may receive a first BSR from the target UE. For example, 904 may be performed by the BSR component 198 of the device 1104. The relay UE may receive the first BSR from the target UE via a sidelink communication. In some aspects, the first BSR may be received from the target UE via a sidelink MAC-CE.

[0093] At 906, the relay UE may send a second BSR to the network entity. For example, 906 may be performed by the BSR component 198 of the device 1104. The second BSR may include information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE. In some aspects, the second BSR may be sent via a MAC-CE. The LCID within the header of the MAC-CE may indicate that the second BSR is associated with at least one of the target UE or the relay UE. In some aspects, the second BSR may include information corresponding to the first BSR. The second BSR may include an LCGID, which may indicate that the LCG within the second BSR corresponds to the service information of the target UE. In some aspects, the second BSR may include information corresponding to the sidelink BSR of the relay UE. The second BSR may include an LCGID that may indicate that the LCG within the second BSR corresponds to the service information of the relay UE. In some aspects, the information corresponding to the first BSR of the target UE and the sidelink BSR of the relay UE may be sent separately. The sending of the first BSR of the target UE and the sidelink BSR of the relay UE may be based on a priority for determining which one is transmitted first. In some aspects, the second BSR may include the first BSR of the target UE and the sidelink BSR of the relay UE. The second BSR may be ordered to include the sidelink BSR of the relay UE first, followed by the first BSR of the target UE.

[0094] At 908, the relay UE may receive a resource allocation for sidelink communications with the target UE. For example, 908 may be performed by the BSR component 198 of the device 1104. The relay UE may receive a resource allocation for sidelink communications with the target UE based on the second BSR.

[0095] At 910, the relay UE may communicate with the target UE via sidelink communication. For example, 910 may be performed by the BSR component 198 of the device 1104. The relay UE may communicate with the target UE via sidelink communication using the resource allocation.

[0096] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104; device 1104). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a relay UE to provide a BSR from a target UE to a network entity to configure sidelink communication resources.

[0097] At 1002, a relay UE may receive a request for a sidelink communication. For example, 1002 may be performed by the BSR component 198 of the device 1104. The relay UE may receive a request for a sidelink communication from a target UE.

[0098] At 1004, the relay UE may receive a first BSR from the target UE. For example, 1004 may be performed by the BSR component 198 of the device 1104. The relay UE may receive the first BSR from the target UE via a sidelink communication. In some aspects, the first BSR may be received from the target UE via a sidelink MAC-CE.

[0099] At 1006, the relay UE may receive a grant including resources for sending a second BSR. For example, 1006 may be performed by BSR component 198 of device 1104. The grant may include different resources for the relay UE to send information corresponding to the first BSR of the target UE or the sidelink BSR of the relay UE.

[0100] At 1008, the relay UE may send a second BSR to the network entity. For example, 1008 may be performed by the BSR component 198 of the device 1104. The second BSR may include information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE. In some aspects, the second BSR may be sent via a MAC-CE. The LCID within the header of the MAC-CE may indicate that the second BSR is associated with at least one of the target UE or the relay UE. In some aspects, the second BSR may include information corresponding to the first BSR. The second BSR may include an LCGID, which may indicate that the LCG within the second BSR corresponds to the service information of the target UE. In some aspects, the second BSR may include information corresponding to the sidelink BSR of the relay UE. The second BSR may include an LCGID that may indicate that the LCG within the second BSR corresponds to the service information of the relay UE. In some aspects, the information corresponding to the first BSR of the target UE and the sidelink BSR of the relay UE may be sent separately. The sending of the first BSR of the target UE and the sidelink BSR of the relay UE may be based on a priority for determining which one is transmitted first. In some aspects, the second BSR may include the first BSR of the target UE and the sidelink BSR of the relay UE. The second BSR may be ordered to include the sidelink BSR of the relay UE first, followed by the first BSR of the target UE.

[0101] At 1010, the relay UE may receive a resource allocation for sidelink communications with the target UE. For example, 1010 may be performed by the BSR component 198 of the device 1104. The relay UE may receive a resource allocation for sidelink communications with the target UE based on the second BSR.

[0102] At 1012, the UE may relay the resource allocation for the sidelink communication. For example, 1012 may be performed by the BSR component 198 of the device 1104. The relay UE may relay the resource allocation for the sidelink communication to the target UE.

[0103] At 1014, the relay UE may communicate with the target UE via sidelink communication. For example, 1014 may be performed by the BSR component 198 of the device 1104. The relay UE may communicate with the target UE via sidelink communication using the resource allocation.

[0104] Fig.111100 is a diagram illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., a cellular RF transceiver). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the apparatus 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1126, a power source 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include their own dedicated antennas and / or communicate using antennas 1180. The cellular baseband processor 1124 communicates with the UE 104 and / or with the RU associated with the network entity 1102 through the transceiver 1122 via one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The additional memory module 1126 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1124 / application processor 1106, enables the cellular baseband processor 1124 / application processor 1106 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software.The cellular baseband processor 1124 / application processor 1106 may be a component of the device 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1104 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1124 and / or the application processor 1106, and in another configuration, the apparatus 1104 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1104.

[0105] As discussed above, component 198 is configured to: receive a request for sidelink communication from a target UE; receive a first BSR from the target UE via sidelink communication; send a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE; receive a resource allocation for sidelink communication with the target UE based on the second BSR; and use the resource allocation to communicate with the target UE via sidelink communication. Component 198 may be within the cellular baseband processor 1124, the application processor 1106, or within both the cellular baseband processor 1124 and the application processor 1106. Component 198 may be one or more hardware components that are specifically configured to perform the described process / algorithm, implemented by one or more processors configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1104 may include a variety of components configured for various functions. In one configuration, the device 1104 (and specifically the cellular baseband processor 1124 and / or the application processor 1106) includes a component for receiving a request for sidelink communication from a target UE. The device includes a component for receiving a first buffer status report (BSR) from the target UE via the sidelink communication. The device includes a component for sending a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE. The device includes a component for receiving a resource allocation for sidelink communication with the target UE based on the second BSR. The device includes a component for communicating with the target UE via the sidelink communication using the resource allocation. The device also includes a component for receiving a grant including resources for sending the second BSR. The grant includes different resources for the relay UE to send information corresponding to the first BSR of the target UE or the sidelink BSR of the relay UE. The device also includes a component for relaying the resource allocation for the sidelink communication to the target UE. The component can be a component 198 of the device 1104 configured to perform the functions recorded by the component. As described above, the device 1104 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0106] Fig.121200 is a flow chart of a method of wireless communication. The method may be performed by a target UE (e.g., UE 104; device 1404). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow the target UE to provide a BSR to a relay UE via a side link, so that the relay UE provides the BSR from the target UE to a network entity to configure side link communication resources.

[0107] At 1202, the target UE may send a request for sidelink communication. For example, 1202 may be performed by BSR component 199 of device 1404. The target UE may send a request for sidelink communication with a relay UE. The target UE may send a request for sidelink communication with the relay UE to the relay UE.

[0108] At 1204, the target UE may send a first BSR to the relay UE. For example, 1204 may be performed by the BSR component 199 of the device 1404. The target UE may send the first BSR to the relay UE via sidelink communication. In some aspects, the first BSR may be sent via a sidelink MAC-CE. The first BSR may be sent to the relay UE via a sidelink MAC-CE.

[0109] At 1206, the target UE may communicate with the relay UE via sidelink communication. For example, 1206 may be performed by BSR component 199 of device 1404. The target UE may communicate with the relay UE via sidelink communication using resource allocation based on at least the first BSR.

[0110] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104; device 1404). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a target UE to provide a BSR to a relay UE via a side link, so that the relay UE provides the BSR from the target UE to a network entity to configure side link communication resources.

[0111] At 1302, the target UE may send a request for sidelink communication. For example, 1302 may be performed by BSR component 199 of device 1404. The target UE may send a request for sidelink communication with a relay UE. The target UE may send a request for sidelink communication with the relay UE to the relay UE.

[0112] At 1304, the target UE may send a first BSR to the relay UE. For example, 1304 may be performed by the BSR component 199 of the device 1404. The target UE may send the first BSR to the relay UE via sidelink communication. In some aspects, the first BSR may be sent via a sidelink MAC-CE. The first BSR may be sent to the relay UE via a sidelink MAC-CE.

[0113] At 1306, the target UE may receive a resource allocation for sidelink communications with the relay UE. For example, 1306 may be performed by BSR component 199 of device 1404. The target UE may receive a resource allocation for sidelink communications with the relay UE based at least on the first BSR. In some aspects, the resource allocation for sidelink communications may be received from the relay UE within a sidelink MAC-CE.

[0114] At 1308, the target UE may communicate with the relay UE via sidelink communication. For example, 1308 may be performed by BSR component 199 of device 1404. The target UE may communicate with the relay UE via sidelink communication using resource allocation based on at least the first BSR.

[0115] Fig.141400 is a diagram illustrating an example of a hardware implementation for an apparatus 1404. The apparatus 1404 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1404 may include a cellular baseband processor 1424 (also referred to as a modem) coupled to one or more transceivers 1422 (e.g., a cellular RF transceiver). The cellular baseband processor 1424 may include on-chip memory 1424'. In some aspects, the apparatus 1404 may also include one or more subscriber identity module (SIM) cards 1420 and an application processor 1406 coupled to a secure digital (SD) card 1408 and a screen 1410. The application processor 1406 may include on-chip memory 1406'. In some aspects, the device 1404 may also include a Bluetooth module 1412, a WLAN module 1414, an SPS module 1416 (e.g., a GNSS module), one or more sensor modules 1418 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1426, a power source 1430, and / or a camera 1432. The Bluetooth module 1412, the WLAN module 1414, and the SPS module 1416 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1412, the WLAN module 1414, and the SPS module 1416 may include their own dedicated antennas and / or communicate using an antenna 1480. The cellular baseband processor 1424 communicates with the UE 104 and / or with the RU associated with the network entity 1402 through the transceiver 1422 via one or more antennas 1480. The cellular baseband processor 1424 and the application processor 1406 may each include a computer-readable medium / memory 1424', 1406', respectively. The additional memory module 1426 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1424', 1406', 1426 may be non-transitory. The cellular baseband processor 1424 and the application processor 1406 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1424 / application processor 1406, enables the cellular baseband processor 1424 / application processor 1406 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1424 / application processor 1406 when executing the software.The cellular baseband processor 1424 / application processor 1406 may be a component of the device 310 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1404 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1424 and / or the application processor 1406, and in another configuration, the apparatus 1404 may be the entire UE (e.g., see. Figure 3 310) and includes additional modules of device 1404.

[0116] As discussed above, component 199 is configured to: send a request for sidelink communication with a relay UE; send a first buffer status report (BSR) to the relay UE via the sidelink communication; and communicate with the relay UE via the sidelink communication using resource allocation based at least on the first BSR. Component 199 may be within the cellular baseband processor 1424, the application processor 1406, or within both the cellular baseband processor 1424 and the application processor 1406. Component 198 may be one or more hardware components that are specifically configured to perform the described process / algorithm, implemented by one or more processors configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1404 may include a variety of components configured for various functions. In one configuration, the device 1404 (and specifically the cellular baseband processor 1424 and / or the application processor 1406) includes a component for sending a request for sidelink communication with a relay UE. The apparatus includes a component for sending a first BSR to a relay UE via sidelink communication. The apparatus includes a component for communicating with the relay UE via sidelink communication using resource allocation based at least on the first BSR. The apparatus also includes a component for receiving resource allocation for sidelink communication with the relay UE based at least on the first BSR. The component may be a component 199 of the apparatus 1404 configured to perform the functions recorded by the component. As described above, the apparatus 1404 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recorded by the component.

[0117] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0118] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "while" do not mean an instantaneous time relationship or reaction. That is, these phrases, such as "when ...", do not mean an instantaneous action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a condition is met, but no specific or instantaneous time limit is required for the occurrence of an action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device by a collection of devices. All structural and functional equivalents that are known to those of ordinary skill in the art or will be known later throughout the elements of the various aspects described in this disclosure are explicitly incorporated herein by reference, and are covered by the claims. In addition, anything disclosed herein is not intended to be dedicated to the public, regardless of whether such disclosures are explicitly recorded in the claims. "Module", "mechanism", "element", "equipment" and other words cannot replace the word "component". Therefore, no claim element will be understood as a functional component unless the element is explicitly recorded using the phrase "component for...".

[0119] 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" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0120] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0121] Aspect 1 is a method for performing wireless communication at a relay UE, the method comprising: receiving a request for sidelink communication from a target UE; receiving a first BSR from the target UE via the sidelink communication; sending a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE; receiving a resource allocation for the sidelink communication with the target UE based on the second BSR; and using the resource allocation to communicate with the target UE via the sidelink communication.

[0122] Aspect 2 is a method according to aspect 1, the method further comprising: receiving the first BSR via a sidelink MAC-CE.

[0123] Aspect 3 is a method according to any one of Aspects 1 and 2, the method further comprising: the second BSR is sent via MAC-CE, wherein a logical channel identifier (LCID) within a header of the MAC-CE indicates that the second BSR is associated with at least one of the target UE or the relay UE.

[0124] Aspect 4 is a method according to any one of Aspects 1 to 3, the method further comprising: the second BSR includes the information corresponding to the first BSR, wherein the second BSR includes an LCGID indicating that the LCG within the second BSR corresponds to the service information of the target UE.

[0125] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: the second BSR includes the information corresponding to the sidelink BSR of the relay UE, wherein the second BSR includes an LCGID indicating that the LCG within the second BSR corresponds to the service information of the relay UE.

[0126] Aspect 6 is a method according to any one of aspects 1 to 5, the method further comprising: the information corresponding to the first BSR of the target UE and the sidelink BSR of the relay UE is sent separately.

[0127] Aspect 7 is a method according to any one of aspects 1 to 6, the method further comprising: sending the first BSR of the target UE and the sidelink BSR of the relay UE is based on a priority for determining which one to transmit first.

[0128] Aspect 8 is a method according to any one of Aspects 1 to 7, the method further comprising: receiving a grant including resources for sending the second BSR, wherein the grant includes different resources for the relay UE to send the information corresponding to the first BSR of the target UE or the sidelink BSR of the relay UE.

[0129] Aspect 9 is a method according to any one of aspects 1 to 8, the method further comprising: the second BSR includes the first BSR of the target UE and the sidelink BSR of the relay UE.

[0130] Aspect 10 is a method according to any one of aspects 1 to 9, the method also including: the second BSR is ordered to include the sidelink BSR of the relay UE first, followed by the first BSR of the target UE.

[0131] Aspect 11 is a method according to any one of aspects 1 to 10, the method further comprising: relaying the resource allocation for the sidelink communication to the target UE.

[0132] Aspect 12 is an apparatus for wireless communication at a relay UE, the apparatus comprising: at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 1 to 11.

[0133] Aspect 13 is an apparatus for performing wireless communication at a relay UE, the apparatus comprising: a means for implementing any one of aspects 1 to 11.

[0134] Aspect 14 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 11.

[0135] Aspect 15 is a method for wireless communication at a target UE, the method comprising: sending a request for sidelink communication with a relay UE; sending a first BSR to the relay UE via the sidelink communication; and communicating with the relay UE via the sidelink communication using resource allocation based at least on the first BSR.

[0136] Aspect 16 is a method according to aspect 15, the method further comprising: sending the first BSR via a sidelink MAC-CE.

[0137] Aspect 17 is a method according to any one of aspects 15 and 16, the method further comprising: receiving the resource allocation for the sidelink communication with the relay UE based at least on the first BSR.

[0138] Aspect 18 is a method according to any one of aspects 15 to 17, the method further comprising: the resource allocation for the sidelink communication is received within a sidelink MAC-CE.

[0139] Aspect 19 is an apparatus for wireless communication at a target UE, the apparatus comprising: at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 15 to 18.

[0140] Aspect 20 is an apparatus for wireless communication at a target UE, the apparatus comprising: means for implementing any one of aspects 15 to 18.

[0141] Aspect 21 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 15 to 18.

Claims

1. An apparatus for wireless communication at a relay user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: receiving a request for sidelink communication from a target UE; receiving a first buffer status report (BSR) from the target UE via the sidelink communication; sending a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE; receiving a resource allocation for the sidelink communication with the target UE based on the second BSR; as well as The resource allocation is used to communicate with the target UE via the sidelink communication.

2. The device according to claim 1, further comprising: A transceiver is coupled to the at least one processor.

3. The apparatus of claim 1, wherein the first BSR is received via a sidelink medium access control (MAC) control element (CE) (MAC-CE).

4. The apparatus of claim 1 , wherein the second BSR is sent via a medium access control (MAC) control element (CE) (MAC-CE), wherein a logical channel identifier (LCID) within a header of the MAC-CE indicates that the second BSR is associated with at least one of the target UE or the relay UE.

5. The apparatus of claim 1, wherein the second BSR includes the information corresponding to the first BSR, wherein the second BSR includes a logical channel group identifier (LCGID) indicating that a logical channel group (LCG) within the second BSR corresponds to service information of the target UE.

6. The apparatus according to claim 1, wherein the second BSR includes the information corresponding to the sidelink BSR of the relay UE, wherein the second BSR includes a logical channel group identifier (LCGID) indicating that a logical channel group (LCG) within the second BSR corresponds to service information of the relay UE. 7 . The apparatus of claim 1 , wherein the information corresponding to the first BSR of the target UE and the sidelink BSR of the relay UE are transmitted separately. 8 . The apparatus of claim 7 , wherein the transmission of the first BSR of the target UE and the sidelink BSR of the relay UE is based on a priority for determining which one is transmitted first.

9. The apparatus of claim 1 , wherein the at least one processor is further configured to: A grant including resources for sending the second BSR is received, wherein the grant includes different resources for the relay UE to send the information corresponding to the first BSR of the target UE or the sidelink BSR of the relay UE.

10. The apparatus of claim 1, wherein the second BSR comprises the first BSR of the target UE and the sidelink BSR of the relay UE.

11. The apparatus of claim 10, wherein the second BSR is ordered to include the sidelink BSR of the relay UE first, followed by the first BSR of the target UE.

12. The apparatus of claim 1, wherein the at least one processor is further configured to: The resource allocation for the sidelink communication is relayed to the target UE.

13. A method for wireless communication at a relay user equipment (UE), the method comprising: receiving a request for sidelink communication from a target UE; receiving a first buffer status report (BSR) from the target UE via the sidelink communication; sending a second BSR to a network entity, the second BSR including information corresponding to at least one of the first BSR of the target UE or the sidelink BSR of the relay UE; receiving a resource allocation for the sidelink communication with the target UE based on the second BSR; as well as The resource allocation is used to communicate with the target UE via the sidelink communication. The method of claim 13 , wherein the first BSR is received via a sidelink MAC-CE.

15. The method of claim 13, wherein the second BSR is sent via a MAC-CE, wherein a logical channel identifier (LCID) within a header of the MAC-CE indicates that the second BSR is associated with at least one of the target UE or the relay UE.

16. The method of claim 13, wherein the second BSR includes the information corresponding to the first BSR, wherein the second BSR includes a logical channel group identifier (LCGID) indicating that a logical channel group (LCG) within the second BSR corresponds to service information of the target UE.

17. The method of claim 13, wherein the second BSR includes the information corresponding to the sidelink BSR of the relay UE, wherein the second BSR includes a logical channel group identifier (LCGID) indicating that a logical channel group (LCG) within the second BSR corresponds to service information of the relay UE.

18. The method of claim 13, wherein the information corresponding to the first BSR of the target UE and the sidelink BSR of the relay UE are transmitted separately.

19. The method of claim 18, wherein the transmission of the first BSR of the target UE and the sidelink BSR of the relay UE is based on a priority for determining which one is transmitted first.

20. The method according to claim 13, further comprising: A grant including resources for sending the second BSR is received, wherein the grant includes different resources for the relay UE to send the information corresponding to the first BSR of the target UE or the sidelink BSR of the relay UE.

21. The method of claim 13, wherein the second BSR includes the first BSR of the target UE and the sidelink BSR of the relay UE.

22. The method of claim 21, wherein the second BSR is ordered to include the sidelink BSR of the relay UE first, followed by the first BSR of the target UE.

23. The method according to claim 13, further comprising: The resource allocation for the sidelink communication is relayed to the target UE.

24. An apparatus for wireless communication at a target user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: sending a request for sidelink communication with a relay UE; sending a first buffer status report (BSR) to the relay UE via the sidelink communication; and Communicating with the relay UE via the sidelink communication using resource allocation based at least on the first BSR.

25. The apparatus according to claim 24, further comprising: A transceiver is coupled to the at least one processor.

26. The apparatus of claim 24, wherein the first BSR is sent via a sidelink medium access control (MAC) control element (CE) (MAC-CE).

27. The apparatus of claim 24, wherein the at least one processor is further configured to: The resource allocation for the sidelink communication with the relay UE is received based at least on the first BSR.

28. The apparatus of claim 27, wherein the resource allocation for the sidelink communication is received within a sidelink medium access control (MAC) control element (CE) (MAC-CE).

29. A method for wireless communication at a target user equipment (UE), the method comprising: sending a request for sidelink communication with a relay UE; sending a first buffer status report (BSR) to the relay UE via the sidelink communication; as well as Communicating with the relay UE via the sidelink communication using resource allocation based at least on the first BSR.

30. The method according to claim 29, further comprising: The resource allocation for the sidelink communication with the relay UE is received based at least on the first BSR.

Images