CN110574476B - Relay in a device-to-device communication system - Google Patents

Abstract

Aspects of the present disclosure relate to device-to-device (D2D) relaying in a wireless communication system. In an aspect, a remote User Equipment (UE) may transmit a scheduling request on at least one sidelink channel to a relay UE connected with a network entity. The remote UE may further receive a scheduling indication including a resource grant from the relay UE on one or more sidelink channels in response to transmitting the scheduling request. In a further aspect, the relay UE may receive a scheduling request from the remote UE on at least one sidelink channel. The relay UE may further determine a resource grant for the remote UE in response to receiving the scheduling request. The relay UE may further transmit a scheduling indication including the resource grant to the remote UE on one or more sidelink channels.

Description

Relay in a device-to-device communication system

Cross Reference to Related Applications

This patent application claims priority from U.S. non-provisional application No.15/960,095 entitled "RELAYING IN a DEVICE-TO-DEVICE COMMUNICATION SYSTEM" filed on 23.4.2018 and U.S. provisional application S/n.62/502,363 entitled "RELAYING IN a DEVICE-TO-DEVICE COMMUNICATION SYSTEM" filed on 5.5.2017, which are all expressly incorporated herein by reference.

Background

The present disclosure relates generally to communication systems, and more particularly to device-to-device (D2D) relay communication.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques 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.

These multiple access techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate on a city, country, region, and even global level. An example telecommunication standard is Long Term Evolution (LTE). LTE is an enhanced set of Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the third generation partnership project (3 GPP). LTE is designed to support mobile broadband access by improving spectral efficiency, reducing cost, and improving service using OFDMA on the downlink, SC-FDMA on the uplink, and multiple-input multiple-output (MIMO) antenna technology. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in LTE technology. These improvements are also applicable to other multiple access techniques and telecommunications standards employing these techniques.

For example, current implementations of D2D communication may inhibit efficient operation with respect to desired levels of power and resource utilization. Thus, improvements in wireless communication operation may be desirable.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate 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 the more detailed description that is presented later.

In an aspect, the disclosure includes a method for wireless communication at a relay User Equipment (UE). The method may include receiving a scheduling request from a remote UE on at least one sidelink channel. The method may further include determining a resource grant for the remote UE in response to receiving the scheduling request. The method may further include transmitting a scheduling indication including the resource grant to the remote UE on one or more sidelink channels.

In another aspect, the disclosure includes a relay UE for wireless communication that includes a memory, and a processor in communication with the memory. The processor may be configured to receive a scheduling request from a remote UE on at least one sidelink channel. The processor may be further configured to determine, by the relay UE, a resource grant for the remote UE in response to receiving the scheduling request. The processor may be further configured to transmit a scheduling indication including the resource grant to the remote UE on one or more sidelink channels.

In an additional aspect, the disclosure includes a relay UE for wireless communication that includes means for receiving a scheduling request from a remote UE on at least one sidelink channel. The relay UE may further include means for determining, by the relay UE, a resource grant for the remote UE in response to receiving the scheduling request. The relay UE may further include means for transmitting a scheduling indication including the resource grant to the remote UE on one or more sidelink channels.

In yet another aspect, the disclosure includes a computer-readable medium storing computer executable code for wireless communication at a relay UE. The computer-readable medium may include code for receiving a scheduling request from a remote UE on at least one sidelink channel. The computer-readable medium may further include code for determining, by the relay UE, a resource grant for the remote UE in response to receiving the scheduling request. The computer-readable medium may further include code for transmitting a scheduling indication including the resource grant to the remote UE on one or more sidelink channels.

In one aspect, the disclosure includes a method for wireless communication at a remote UE. The method may include transmitting a scheduling request to a relay UE connected with a network entity on at least one sidelink channel. The remote UE may further receive a scheduling indication including a resource grant from the relay UE on one or more sidelink channels in response to transmitting the scheduling request.

In another aspect, the disclosure includes a remote UE for wireless communication that includes a memory, and a processor in communication with the memory. The processor may be configured to transmit a scheduling request to a relay UE connected with a network entity on at least one sidelink channel. The processor may be further configured to receive a scheduling indication including a resource grant from the relay UE on one or more sidelink channels in response to transmitting the scheduling request.

In an additional aspect, the disclosure includes a remote UE for wireless communication that includes means for transmitting a scheduling request on at least one sidelink channel to a relay UE connected to a network entity. The remote UE may further include means for receiving a scheduling indication including a resource grant from the relay UE on one or more sidelink channels in response to transmitting the scheduling request.

In yet another aspect, the disclosure includes a computer-readable medium storing computer executable code for wireless communications at a remote UE. The computer-readable medium can include code for transmitting a scheduling request to a relay UE connected with a network entity on at least one sidelink channel. The computer-readable medium may further include code for receiving a scheduling indication including a resource grant from the relay UE on one or more sidelink channels in response to transmitting the scheduling request.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the present description is intended to include all such aspects and their equivalents.

Brief Description of Drawings

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network.

Fig. 2A, 2B, 2C, and 2D are diagrams illustrating LTE examples of a DL frame structure, DL channels within the DL frame structure, an UL frame structure, and UL channels within the UL frame structure, respectively.

Fig. 3 is a diagram illustrating an example of an evolved node B (eNB) and a User Equipment (UE) in an access network.

Fig. 4 is an illustration of a device-to-device communication system including a relay UE having a relay component and a remote UE having a communication component.

Fig. 5 is a flow diagram of a method of relaying a Radio Network Temporary Identifier (RNTI) at a relay UE.

Figure 6 is a flow chart of a method of RNTI reception at a remote UE.

Fig. 7 is a flow chart of a method of resource allocation at a remote UE.

Fig. 8 is a flow diagram of a method of resource allocation at a relay UE.

Fig. 9 is a flow chart of a method of wireless communication at a remote UE.

Fig. 10 is a flow diagram of a method of scheduling resources at a relay UE.

Fig. 11 is a conceptual data flow diagram illustrating the data flow between different apparatuses/components in an example apparatus, such as a relay UE, having a relay component.

Fig. 12 is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system.

Fig. 13 is a conceptual data flow diagram illustrating the data flow between different apparatuses/components in an example apparatus, such as a remote UE, having a communication component.

Fig. 14 is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system.

Detailed Description

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. It will be apparent, however, to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of a telecommunications system will now be presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and are 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 such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

As an example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include: a microprocessor, a microcontroller, a Graphics Processing Unit (GPU), a Central Processing Unit (CPU), an application processor, a Digital Signal Processor (DSP), a Reduced Instruction Set Computing (RISC) processor, a system on chip (SoC), a baseband processor, a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subprograms, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to in software, firmware, middleware, microcode, hardware description language, or other terminology.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. By way of example, and not limitation, such computer-readable media can comprise 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 the above 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.

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system, also referred to as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE 104, and an Evolved Packet Core (EPC) 160. For example, UE 104a and UE 104b may be communicating via device-to-device (D2D). D2D communication may be used to provide direct communication between devices, such as UEs. D2D communication enables one device to communicate with another device and transmit data to the other device on the allocated resources. In an aspect, UE 104a may include a relay component 410 configured to relay information from base station 102 to UE 104b and/or from UE 104b to base station 102. Further, in an aspect, the UE 104b may include a communication component 420 configured to facilitate sidelink communication with the UE 104 a. In some aspects, one or both of UEs 104a and/or 104b may be in a connected state with base station 102. Base station 102 may include macro cells (high power cell base stations) and/or small cells (low power cell base stations). The macro cell includes an eNB. Small cells include femtocells, picocells, and microcells.

The base stations 102, collectively referred to as the evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), interface with the EPC 160 over a backhaul link 132 (e.g., the S1 interface). Among other functions, the base station 102 may perform one or more of the following functions: communication of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio Access Network (RAN) sharing, multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other over a backhaul link 134 (e.g., an X2 interface) either directly or indirectly (e.g., through the EPC 160). The backhaul link 134 may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102 'may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The 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 120 between base station 102 and UE 104 may include Uplink (UL) (also known as reverse link) transmissions from UE 104 to base station 102 and/or Downlink (DL) (also known as forward link) transmissions from base station 102 to UE 104. The communication link 120 may use MIMO antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. These communication links may be over one or more carriers. For each carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) for transmission in each direction, the base station 102/UE 104 may use a spectrum of up to a Y MHz (e.g., 5, 10, 15, 20 MHz) bandwidth. These 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 than UL). The component carriers 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).

The wireless communication system may further include a Wi-Fi Access Point (AP) 150 in communication with a Wi-Fi Station (STA) 152 via a communication link 154 in a 5GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152/AP 150 may perform a Clear Channel Assessment (CCA) prior to the communication to determine whether the channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ LTE and use the same 5GHz unlicensed spectrum as used by the Wi-Fi AP 150. A small cell 102' employing LTE in unlicensed spectrum may boost coverage and/or increase capacity of an access network. LTE in unlicensed spectrum may be referred to as LTE unlicensed (LTE-U), licensed Assisted Access (LAA), or MuLTEfire.

Millimeter-wave (mmW) base station 180 may operate in mmW frequencies and/or near mmW frequencies to communicate with UE 182. Extremely High Frequency (EHF) is the portion of the RF in the electromagnetic spectrum. The EHF has a range of 30GHz to 300GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this frequency band may be referred to as millimeter waves. Near mmW can be extended down to frequencies of 3GHz and wavelengths of 100 mm. The ultra-high frequency (SHF) band extends between 3GHz to 30GHz, which is also known as a centimeter wave. Communications using the mmW/near mmW radio frequency band have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 184 with the UE 182 to compensate for the very high path loss and short range.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172.MME 162 may be in communication with Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE 104 and EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which serving gateway 166 itself connects to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to an IP service 176.IP services 176 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming service (PSs), and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may be used as an entry point for content provider MBMS transmissions, may be used to grant and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and for collecting eMBMS-related charging information.

A base station may also be called a node B, an evolved node B (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), or some other suitable terminology. The base station 102 provides an access point for the UE 104 to the EPC 160. Examples of UEs 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, or any other similar functioning device. UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Referring again to fig. 1, in certain aspects, the UE 104 may be configured to perform congestion control based on the energy-based channel busy rate and/or based on the decoded channel busy rate, and to control packet transmission based on the packet priority and the channel busy rate (198).

Fig. 2A is a diagram 200 illustrating an example of a DL frame structure in LTE. Fig. 2B is a diagram 230 illustrating an example of channels within a DL frame structure in LTE. Fig. 2C is a diagram 250 illustrating an example of an UL frame structure in LTE. Fig. 2D is a diagram 280 illustrating an example of channels within a UL frame structure in LTE. Other wireless communication technologies may have different frame structures and/or different channels. In LTE, a frame (10 ms) may be divided into 10 equally sized subframes. Each subframe may include two consecutive slots. A resource grid may be used to represent the two slots, each slot including one or more time-concurrent Resource Blocks (RBs) (also known as Physical RBs (PRBs)). The resource grid is divided into a plurality of Resource Elements (REs). In LTE, for a normal cyclic prefix, an RB contains 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain (OFDM symbols for DL; SC-FDMA symbols for UL), for a total of 84 REs. For an extended cyclic prefix, an RB contains 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

As illustrated in fig. 2A, some REs carry DL reference (pilot) signals (DL-RSs) used for channel estimation at the UE. The DL-RS may include cell-specific reference signals (CRS) (also sometimes referred to as common RS), UE-specific reference signals (UE-RS), and channel state information reference signals (CSI-RS). Fig. 2A illustrates CRSs (indicated as R, respectively) for antenna ports 0, 1, 2, and 3 ₀ 、R ₁ 、R ₂ And R ₃ ) UE-RS (indicated as R) for antenna port 5 ₅ ) And CSI-RS (indicated as R) for antenna port 15. Fig. 2B illustrates an example of various channels within the DL subframe of a frame. The Physical Control Format Indicator Channel (PCFICH) is within symbol 0 of slot 0 and carries a Control Format Indicator (CFI) indicating whether the Physical Downlink Control Channel (PDCCH) occupies 1, 2, or 3 symbols (fig. 2B illustrates a PDCCH occupying 3 symbols). The PDCCH carries Downlink Control Information (DCI) within one or more Control Channel Elements (CCEs), each CCE includes 9 RE groups (REGs), each REG including 4 consecutive REs in an OFDM symbol. The UE may be configured with a UE-specific enhanced PDCCH (ePDCCH) that also carries DCI. The ePDCCH may have 2, 4, or 8 RB pairs (fig. 2B shows 2 RB pairs, each subset including 1 RB pair). Physical hybrid automatic repeat request (ARQ) (HARQ) indicator channel: (a), (b), (c), and (d)PHICH) is also within symbol 0 of slot 0 and carries a Physical Uplink Shared Channel (PUSCH) indicator (HI) indicating HARQ Acknowledgement (ACK)/Negative ACK (NACK) feedback. The Primary Synchronization Channel (PSCH) is within symbol 6 of slot 0 within subframes 0 and 5 of the frame and carries a Primary Synchronization Signal (PSS) that is used by the UE to determine subframe timing and physical layer identity. The Secondary Synchronization Channel (SSCH) is within symbol 5 of slot 0 within subframes 0 and 5 of the frame and carries a Secondary Synchronization Signal (SSS) used by the UE to determine the physical layer cell identity group number. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DL-RS. The Physical Broadcast Channel (PBCH) is within symbols 0, 1, 2,3 of slot 1 of subframe 0 of the frame and carries a Master Information Block (MIB). The MIB provides the number of RBs in the DL system bandwidth, PHICH configuration, and System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information, such as System Information Blocks (SIBs), which are not transmitted through the PBCH, and a paging message.

As illustrated in fig. 2C, some REs carry demodulation reference signals (DM-RS) for channel estimation at the eNB. The UE may additionally transmit a Sounding Reference Signal (SRS) in a last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of comb teeth (comb). SRS may be used by the eNB for channel quality estimation to enable frequency-dependent scheduling on the UL. Fig. 2D illustrates an example of various channels within the UL subframe of a frame. A Physical Random Access Channel (PRACH) may be within one or more subframes within a frame based on a PRACH configuration. The PRACH may include 6 consecutive RB pairs within a subframe. The PRACH allows the UE to perform initial system access and achieve UL synchronization. The Physical Uplink Control Channel (PUCCH) may be located at the edge of the UL system bandwidth. The PUCCH carries Uplink Control Information (UCI) such as scheduling requests, channel Quality Indicators (CQIs), precoding Matrix Indicators (PMIs), rank Indicators (RIs), and HARQ ACK/NACK feedback. The PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSRs), power Headroom Reports (PHR), and/or UCI.

Fig. 3 is a block diagram of an eNB 310 in communication with a UE 350 in an access network. The UE 350 may include at least one of a relay component 410 configured to relay information from the eNB 310 to a remote UE and/or from a remote UE to the eNB 310 or a communication component 420 configured to facilitate sidelink communication with another UE. In the DL, IP packets from the EPC 160 may be provided to the controller/processor 375. The controller/processor 375 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. The controller/processor 375 provides RRC layer functionality associated with broadcast of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression/decompression, security (ciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer Packet Data Units (PDUs), error correction by ARQ, concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto Transport Blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel prioritization.

The Transmit (TX) processor 316 and the 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) encoding/decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary Phase Shift Keying (BPSK), quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel that carries a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to produce a plurality of spatial streams. The channel estimates from channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an 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 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined into a single OFDM symbol stream by the RX processor 356. RX processor 356 then transforms 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, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 310. These soft decisions may be based on channel estimates computed by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 310 on the physical channel. These data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, cipher interpretation, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the eNB 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction by ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel prioritization.

Channel estimates, derived by a channel estimator 358 from reference signals or feedback transmitted by the eNB 310, may be used by the TX processor 368 to select appropriate coding and modulation schemes, as well as to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to a different antenna 352 via separate transmitters 354 TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

UL transmissions are processed at the eNB 310 in a manner similar to that described in connection with receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, cipher interpretation, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from controller/processor 375 may be provided to EPC 160. The controller/processor 375 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

Fig. 4 is a diagram of a D2D communication system 460. The D2D communication system 460 includes a plurality of UEs 464, 466, 468, 470. The D2D communication system 460 may overlap with a cellular communication system, such as a WWAN, for example. Some of the UEs 464, 466, 468, 470 may communicate together in D2D communication using the DL/UL WWAN spectrum, some may communicate with the base station 462 (e.g., via communication links 432 and/or 434), and some may communicate both. For example, as shown in fig. 4, the UEs 468, 470 are in D2D communication, and the UEs 464, 466 are in D2D communication. The UEs 464, 466 are also communicating with the base station 462. D2D communications may be over one or more sidelink channels (e.g., sidelink channel 430), such as, but not limited to, a Physical Sidelink Broadcast Channel (PSBCH), a Physical Sidelink Discovery Channel (PSDCH), a physical sidelink shared channel (psch), and a Physical Sidelink Control Channel (PSCCH).

UE464 may correspond to a relay UE, while UE466 may correspond to a remote UE. The UE464 may include a relay component 410, which relay component 410 may be configured to relay information from the base station 462 to the UE466 and/or from the UE466 to the base station 462. Further, the remote UE466 can include a communication component 420 that can be configured to facilitate sidelink communications with the relay UE 464.

In an aspect related to the RNTI component 412 at the UE464 and the RNTI receiving component 422 at the remote UE466, one or more Radio Network Temporary Identifiers (RNTIs) for D2D based bi-directional association can be implemented. In some aspects, the RNTI is a physical layer identifier of the UE assigned by a base station (e.g., eNB). In particular, D2D relays may provide efficiencies in power and resource utilization. For example, a remote UE (e.g., a smart watch) such as the remote UE466 may have a limited battery and/or power source. When the remote UE466 communicates with the base station 462, the remote UE466 may transmit at a higher power (e.g., as compared to communicating with the relay UE464 on a sidelink). As such, the remote UE466 may consume lower power for transmission and reception when communicating with a relay UE (such as the relay UE 464). Thus, relay assistance conserves power at the remote UE 466. Further, from a resource utilization perspective, the remote UE466 can reuse at least some of the same resources between the relay UE464 and the remote UE466 that are used by the base station 462, thereby increasing system capacity.

The D2D relay may include a one-way relay and/or a two-way relay. A unidirectional relay may be used to relay uplink traffic from the remote UE466 to the base station 462 only via the relay UE464, while downlink traffic to the remote UE466 may be transmitted directly to the remote UE 466. However, using bi-directional relaying, both uplink traffic from the remote UE466 and downlink traffic to the remote UE466 can be relayed by the relay UE464 to/from the base station 462.

The remote UE466 and the relay UE464 may use a PC5 (D2D communication) interface for communication. Rel-12 and Rel-13 d2d communications may be based on a fixed number of retransmissions and the transmission power is based on open loop power control with respect to the base station 462. However, such approaches may not utilize feedback from other UEs to adjust the number of retransmissions and transmission power.

The remote UE466 (which may generally correspond to a remote UE) may have only a single receiver (Rx) chain, and as such may only be tuned to or otherwise listening to the base station 462 or the relay UE 464. For example, in one example, the remote UE466 can be tuned to the relay UE464, but the base station 462 can be controlling resources allocated to one or both of the relay UE464 and/or the remote UE466 for sidelink communications. Accordingly, it may be desirable to have the relaying UE464 relay RNTI information to the UE466 on the at least one sidelink channel 430.

For example, to allocate resources and during connection setup, the base station 462 may provide one or more RNTIs to the relay UE464 and may also indicate to the remote UE466 to establish a side link (e.g., PC 5) connection with the relay UE 464. As such, the base station 462 can control, via RRC message reception, when the remote UE466 is listening to the relay UE464 or when the remote UE466 is listening to the UE464 (e.g., when the side link is disconnected, the remote UE466 will automatically connect to the eNB for at least downlink communications). In some aspects, the remote UE466 and the base station 462 may maintain a logical connection even when the remote UE466 is connected to the relay UE464, although the remote UE466 no longer listens to the base station 462.

The relay UE464 may receive one or more RNTIs, which may include an RNTI of the relay UE464 and an RNTI of the remote UE 466. The UE464 may perform resource scheduling for the remote UE466 based on the base station 462 commands. In particular, for the RNTI of the relay UE464, the relay UE464 may decode a Physical Downlink Control Channel (PDCCH) to determine whether there are downlink grants and/or uplink grants that have been allocated by the base station 462. Similarly, for the RNTI of the remote UE466, the relay UE464 may decode the PDCCH to determine whether a grant of contralateral link resources has been allocated for the remote UE 466. Based on determining that a grant of sidelink resources has been provided for the remote UE466, the relay UE464 may forward the grant or an associated RNTI to the remote UE466 to facilitate bidirectional communication over the sidelink.

In some aspects, the base station 462 may provide a single RNTI for each remote UE466 connected with the relay UE464, or may provide a bulk RNTI for all remote UEs 466 connected with the relay UE 464. For example, in addition to the relay UE 464's own RNTI, the relay UE464 may monitor the PDCCH for the RNTI of the remote UE 466. In particular, the bulk RNTI may be received by the relay UE 464. In such examples, downlink Control Information (DCI) may distinguish remote UEs (including remote UE 466). The indexing may be performed using RRC connection setup of the remote UE. The bulk RNTI message may include an index to each remote UE. In some aspects, the index may have been pre-negotiated between the base station 462 and the relay UE464 in an RRC message. Further, for each remote UE identifier, there may be an index assigned to each remote UE. Based on the index, the relay UE464 may determine a remote UE identifier for which a grant is allocated.

In the case that a single RNTI may be determined and forwarded to a corresponding remote UE466, the relay UE464 may obtain the single RNTI associated with the remote UE466 for use in determining the sidechain routing grant allocated by the base station 462 for the remote UE 466. The relay UE464 may perform such procedures for each different RNTI associated with a different remote UE. As such, in any case, the relay UE464 receives an indication including one or more RNTIs of the remote UE466, and based on the indication, the relay UE464 may decode a PDCCH from the base station 462 to obtain a grant and communicate the grant on to the remote UE 466.

In some aspects, the relay UE464 may be a high-capability UE (e.g., a smartphone) in terms of battery and capacity (e.g., it may support MIMO, carrier aggregation, etc.). Further, the remote UE466 may be a low-powered device (e.g., a smart watch) with respect to battery and communication capabilities.

In some aspects, the relay UE464 and the remote UE466 may be associated with each other. For example, the relay UE464 and the remote UE466 may be associated with a single subscriber or the same subscriber or operator subscription. Further, during connection establishment, the base station 462 can possess association information (e.g., devices share the same subscription).

In aspects related to the resource allocation component 414 at the relay UE464 and the resource component 424 at the remote UE466, eNB-assisted resource allocation for sidelink communications between the remote UE466 and the relay UE464 may be provided. For example, D2D communication may include two resource allocation patterns for sidelink communication: (i) UE autonomous resource allocation, and (ii) eNB (e.g., base station 462) based resource allocation. In the case of UE autonomous resource allocation, the eNB may set aside a resource pool to be used for sidelink communications, and the UE may autonomously (e.g., randomly and/or based on distributed sensing-based MAC) select resources within the pool for transmission. In the case of eNB-based resource allocation, the UE requests resources from the eNB, and the eNB grants these resources to the UE. For out-of-coverage sidelink operation, the resource selection may always be UE autonomous.

For the case of a remote UE466 (e.g., which may be a wearable device), the remote UE466 may not be within coverage of the base station 462, or may be power limited and associated with the relay UE464 to communicate to the base station 462. For the case of a remote UE466 (e.g., which may be a wearable device), the remote UE466 may not be within coverage of the base station 462, or may be power limited and associated with the relay UE464 to communicate to the base station 462. eNB-assisted resource allocation may use centralized resource allocation to provide better coexistence with conventional uplink transmissions and improved link performance.

Further, the remote UE466 (e.g., a wearable UE) may be bandwidth limited (e.g., only capable of monitoring six radio bearers within the channel bandwidth). Thus, if the base station 462 assigns resources to the relay UE464 to communicate with the side link of the remote UE466, the remote UE466 may also need to be informed of the 6 PRB sub-pools to monitor the transmission.

Additionally, if the remote UE466 receives DCI with a resource allocation from an eNB (such as the base station 462) in subframe 'n', the resource may be used for subframe 'n +4'. However, it may be desirable to have the eNB allocate resources for the remote UE466, but such information is relayed via the relay UE464 via a sidelink route. Therefore, if DCI is used by the eNB for this, then 'n +4' may be modified since the forwarding delay of the relay UE464 should be considered.

In the case of a relay link, a remote UE (such as remote UE 466) may not have a timing advance available from the eNB (e.g., there is no direct uplink link between the remote UE and the eNB). For eNB-assigned/assisted resource allocation, it may still be desirable to assign an appropriate timing advance for the transmission of the remote UE for better coexistence with other UL transmissions.

In one example, an eNB (such as base station 462) may allocate resources (e.g., sidelink resources) to both the remote UE466 and the relay UE 464. The relay UE may then forward these resources to the remote UE in a transparent manner. For example, the relay UE464 may receive DCI for the relay UE resources (e.g., may be scrambled with the C-RNTI of the relay UE 464). Further, the relay UE464 may receive DCI for remote UE resources, but the resources may be for time 'n + T', where 'n' is a subframe and 'T' may be a time value. In some aspects, the 'T' may be RRC configured. Additionally, the configuration may be side-chain pool-specific. In some aspects, T may be a fixed value (such as 8) (e.g., implemented when there are HARQ retransmissions).

The DCI may be scrambled with a remote RNTI being monitored by the relay UE464 for the purpose of relaying to the remote UE466 or a group of remote UEs associated with the relay UE 464. Further, the DCI may be transmitted as an enhanced physical downlink control channel (E-PDCCH), and may include 'T' as a parameter, i.e., T may be a part of the DCI.

The relay UE464 may relay the DCI to the remote UE 466. In one example, the DCI may be sent as a Sidelink Control Indication (SCI) without any associated data. In another example, the DCI may be transmitted as part of a MAC control element and side link shared channel (SL-SCH) data. Additionally, the time 'X' after which the allocation applies may be determined such that n '+ X = n + T, where n' is the subframe in which the DCI is relayed to the remote UE 466.

In another example, the eNB (such as the base station 462) can allocate bulk resources to the relay UE464, and the relay UE464 then reallocates and forwards these resources to the remote UE466 in a transparent manner. For example, the base station 462 may transmit an initial resource allocation for both the relay UE464 and the remote UE466 resources to the relay UE464 in accordance with a semi-persistent scheduling (SPS) configuration. The relay UE464 may then reallocate resources from the SPS resources to the remote UE 466. In one example, the relay UE464 may allocate one resource at a time. In another example, as a sub-SPS procedure, the relay UE464 may first be notified of periodicity and then transmit according to n' + X using DCI or MAC CE.

In a further example, the resource pool for the remote UE466 can be configured by the base station 462 using RRC (e.g., RRC messages can be sent directly or indirectly via the relay UE 464). The resource pool may hop over frequency using a predetermined pattern.

Further, to account for timing differences, the remote UE466 can apply a timing advance to the sidelink transmissions. In an example, the relay UE464 may notify the remote UE466 of the timing advance to apply. The timing advance may be derived in at least two ways. First, the relay UE464 may notify the remote UE466 of the timing advance of the relay UE 464. Such information may be sent as a MAC CE or SCI. Second, the relay UE464 may notify the remote UE466 of the timing advance. For example, the timing advance may be the relay UE's own TA in addition to the correction (e.g., the correction may be within autonomous correction limits). Further, the timing advance may be the timing advance of the relay UE464 in addition to a correction (e.g., the correction may be within some limits configured by the eNB). Additionally, the correction may be based on any sidelink transmissions from the remote UE466 and the relay UE 464.

In another example, the remote UE466 can derive the timing for the sidelink transmission based on a sidelink synchronization signal (SLSS) transmitted by the relay UE 464. For example, the SLSS may be transmitted by the relay UE464 with the uplink timing. Further, the remote UE466 can then follow the timing advance of the relay UE464 with the correction as notified by the relay UE464 and/or the autonomous correction that was last made by it. Additionally, the relay UE464 may notify the remote UE466 of the correction to be applied at the SLSS timing received at the remote UE466 based on measurements on any sidelink transmissions from the remote UE466 to the relay UE 464.

In aspects related to the schedule determining component 416 at the relay UE464 and the scheduling component 426 at the remote UE466, a Scheduling Request (SR) and a Buffer Status Report (BSR) on a PC 5-side link interface between the remote UE466 and the relay UE464 can be provided.

Some sidelink designs may not include any specific L2 MAC control signaling for peer UEs to facilitate scheduling. In order for the relay UE464 to act as an L2 relay, the remote UE466 may be visible to the base station 462. The remote UE466 may be logically connected to the base station 462, but the base station 462 may not allocate physical resources for the remote UE 466. Thus, it may not be necessary to have an SR or BSR between the remote UE466 and the base station 462 for scheduling purposes. However, since the remote UE466 may still need to obtain the resources allocated by the relay UE464, signaling on the side-link interface (such as SR and BSR) may be desirable. Aspects of the present disclosure provide SR and BSR signaling schemes that use at least two MAC CEs within the L1 or L2 signaling exchange in the sidelink on the sidelink for direct resource allocation between the remote UE466 and the relay UE 464.

For a mode 1UE, the remote UE466 may rely on the eNB to dynamically allocate PC5 sidelink resources. For mode 2 UEs, the remote UE466 may read the SIB 21 or use preconfigured sidelink resources to transmit its data over the PC5 interface. However, for a UE that is neither in mode 1 nor mode 2, the UE may be in a third mode, where the eNB may not directly participate in remote resource assignment on the sidelink. From the perspective of the remote UE466, sidelink resources may be assigned by the relay UE 464. In this case, the scheduling request may be transmitted on a sidelink between the remote UE466 and the relay UE 464.

For example, the D2D UE may perform synchronization resource allocation for the SR (or RTS). Unlike asynchronous on-demand RTS operations, the resources used to send the SR may be short and periodic. The resource may be used to support Code Division Multiplexing (CDM) such that multiple remote UEs, including remote UE466, may transmit in the resource simultaneously. Relay UE464 may recognize the transmitter(s) or disparate remote UEs by identifying different code(s) used in the CDM scheme. In this SR, 1-bit information may be transmitted by each remote UE as a request for resources allocated for the relay to be used for sidelink operations.

When the remote UE466 is linked to the relay UE464, resources transmitted according to CDM for SR may be pre-allocated as periodic resources. The actual configuration for those resources may be determined by the relay UE464 or eNB 462. In the case of eNB 462, RRC-specific signaling or SIBs may be used. Furthermore, some of the PC5 data resources are statically configured as potential SR resources as part of the PSDCH. In addition, a SR response (CTS) may be generated by the relay UE464 on demand and may not use pre-assigned resources. If the relay UE464 includes an SR response in the MAC CE within the DATA part, the relay UE464 may indicate the SR response in the SCI before the DATA.

For a remote UE466 linked to the relay 464, the bsr may be similar to the RTS of the relay UE. For example, the BSR may be transmitted on the sidelink as a MAC CE, and the remote UE466 may generate the BSR (e.g., for the sidelink buffer) and include the BSR as part of the "DATA" transmitted to the relay UE 464. However, the relay UE464 may extract this portion of the DATA and discern what is represented by the BSR message and adjust the scheduling decision accordingly. To provide an indication to the relay UE464 that a BSR MAC CE is present in the DATA part of the transmission, the SCI (L1 signaling) transmitted prior to the DATA may include a flag indicating such a case.

The exemplary methods and apparatus discussed below may be applicable to any of a variety of wireless D2D communication systems, such as, for example, a wireless device-to-device communication system based on FlashLinQ, wiMedia, bluetooth, zigBee, or Wi-Fi based on the IEEE 802.11 standard. To simplify the discussion, exemplary methods and apparatus are discussed within the context of LTE. However, one of ordinary skill in the art will appreciate that these exemplary methods and apparatus are more generally applicable to various other wireless device-to-device communication systems.

Figure 5 is a flow diagram 500 of a method of relaying an RNTI at a relay UE. The method may be performed by a UE (e.g., UE 464). At block 502, the method may receive at least one message including an RNTI of a remote UE associated with the relay UE from a network entity on a downlink channel. For example, as described herein, the relay UE464 and/or the RNTI component 412 can execute the RNTI component 412 to receive at least one message including an RNTI of a remote UE466 associated with the relay UE464 from a network entity (e.g., the base station 462) over a downlink channel (e.g., the Uu interface). At block 504, the method may transmit a sidelink grant associated with the RNTI to the remote UE on a sidelink channel. For example, as described herein, the relay UE464 and/or the RNTI component 412 may execute the RNTI component 412 to transmit a sidelink grant associated with the RNTI to the remote UE466 on the sidelink channel 430.

In some aspects, the message may include an index including one or more index values, each index value associated with one of the RNTI of the remote UE466 and one or more additional RNTIs of one or more disparate remote UEs. For example, the index may be a list of a plurality of distinct index values, each index value associated with an RNTI of a different remote UE. Although not shown, the method 500 may further determine an index value associated with the remote UE466, identify/determine an RNTI of the remote UE466 based on the index value, and determine a sidelink grant for the remote UE466 based on the RNTI of the remote UE 466. In some aspects, the sidelink grant may be transmitted to the remote UE466 on the sidelink channel 430 based on determining the RNTI based on the index value.

In some aspects, determining a sidelink grant for the remote UE466 may include: the downlink channel is decoded after receiving the message including the RNTI of the remote UE466 to obtain the sidelink grant for the remote UE466 associated with the RNTI of the remote UE 466. In some aspects, the downlink channel may correspond to PDCCH. In some aspects, the method may further establish a sidelink channel 430 with the remote UE466, the sidelink channel 430 corresponding to the PC5 interface. In some aspects, the remote UE466 may share an operator subscription with the relay UE 464. In some aspects, the RNTI of the remote UE466 may be associated with the grant of radio resources on the contralateral link channel 430. In some aspects, the relay UE464 may be a high-capability UE, while the remote UE466 may be a low-capability UE.

Fig. 6 is a flow diagram 600 of a method of RNTI reception at a remote UE. The method may be performed by a UE (e.g., UE 466). At block 602, the method may receive, on a downlink channel from a network entity, an indication to establish a connection with a relay UE on a sidelink channel, the relay UE being in a connected state with the network entity. For example, as described herein, the remote UE466 and/or the communication component 420 can execute the RNTI receiving component 422 to receive an indication from a network entity (e.g., the base station 462) on a downlink channel to establish a connection with the relay UE464 on the sidelink channel 430, the relay UE464 being in a connected state with the network entity.

At block 604, the method may establish a connection with the relay UE on the sidelink channel. For example, the remote UE466 and/or the communication component 420 may execute the RNTI receiving component 422 to establish a connection with the relay UE466 on the sidelink channel 430, as described herein. At block 606, the method may receive a sidelink grant associated with the RNTI of the remote UE from the relay UE on a sidelink channel 430. For example, as described herein, the remote UE466 and/or the communication component 420 may execute the RNTI receiving component 422 to receive a sidelink grant associated with the RNTI of the remote UE466 from the relay UE464 on a sidelink channel 430.

In some aspects, sidelink channel 430 may correspond to a PC5 interface. In some aspects, the remote UE466 may share an operator subscription with the relay UE 464. In some aspects, the sidelink grant provides radio resources for bidirectional communications over the sidelink channel 430. In some aspects, the relay UE464 may be a high-capability UE, while the remote UE466 may be a low-capability UE.

Fig. 7 is a flow diagram 700 of a method of resource allocation at a relay UE. The method may be performed by a UE (e.g., UE 464). At block 702, the method may receive at least one indication including resource allocation information for at least one of the relay UE or the remote UE from a network entity on a downlink channel. For example, as described herein, the relay UE464 and/or the relay component 410 may execute the resource allocation component 414 to receive at least one indication including resource allocation information for at least one of the relay UE464 or the remote UE466 from a network entity (e.g., the base station 462) on a downlink channel. At block 704, the method may transmit resource allocation information for the remote UE to the remote UE on a sidelink channel. For example, as described herein, the relay UE464 and/or the relay component 410 may execute the resource allocation component 414 to transmit the resource allocation information to the remote UE466 on the sidelink channel 430.

In some aspects, the resource allocation information may correspond to DCI including a resource allocation for at least one of the relay UE464 or the remote UE466 at a first time value representing a subframe slot plus a first time variable associated with the resource allocation. In some aspects, the time variable may correspond to at least one of a fixed value or an RRC-configured value. In some aspects, the DCI may be scrambled using at least the C-RNTI of the relay UE464 or the RNTI of the remote UE 466. In some aspects, the DCI is transmitted via an E-PDCCH.

In some aspects, transmitting the resource allocation information to the remote UE466 may include: the DCI is transmitted to the remote UE466 as a SCI without associated data and/or as a MAC CE as part of SL-SCH data. In some aspects, the DCI may be transmitted at a second time value representing a subframe slot plus a second time variable less than the first time variable. Although not shown, in some aspects, the method 700 may determine the second time variable such that the first time value plus the first time variable is the same as or equal to the second time value plus the second time variable or is the same as or equal to a second time value other than the second time variable.

In some aspects, the resource allocation information may include or correspond to a bulk allocation of resources for one or more remote UEs, including the remote UE466, and is associated with an SPS configuration. In some aspects, transmitting the resource allocation information to the remote UE may include: at least the remote UE466 is allocated a single resource from the resources at a distinct time.

In some aspects, the indication may further include a periodicity indication associated with the SPS-RNTI, the periodicity indication representing a repetition period for bulk allocation of resources. In some aspects, transmitting the resource allocation information to the remote UE may include: the DCI is transmitted to the remote UE as a SCI without associated data or as a MAC CE as part of SL-SCH data.

In some aspects, although not shown, the method 700 may determine the first timing advance information and transmit the first timing advance information to the remote UE 466. Further, in some aspects, determining the first timing advance information may include: second timing advance information is received from the network entity for use in transmissions between the relay UE464 and the network entity (e.g., base station 462), and the first timing advance information is set equal to the second timing advance information.

In some aspects, determining the first timing advance information may include: receive second timing advance information from a network entity (e.g., base station 462) for use in transmissions between the relay UE464 and the network entity (e.g., base station 462), determine a timing offset based on received timing of one or more sidelink channels (e.g., sidelink channels 430), and set the first timing advance information according to the second timing advance information and the timing offset. Moreover, although not shown, in some aspects, the method 700 may further determine whether the timing offset is within at least one of a minimum limit or a maximum limit, and adjust the timing offset to at least one of the minimum limit or the maximum limit.

In some aspects, at least one of the minimum limit or the maximum limit may be within a fixed autonomous timing correction limit allowed by a network entity (e.g., base station 462). In some aspects, at least one of the minimum limit or the maximum limit is received as an RRC configuration from a network entity (e.g., base station 462). In some aspects, the method may further utilize timing corresponding to the first timing advance information to transmit one or more sidelink synchronization signals to the remote UE 466.

Fig. 8 is a flow chart 800 of a method of resource allocation at a remote UE. The method may be performed by a UE (e.g., UE 464). At block 802, the method may receive resource allocation information from the relay UE on at least one sidelink channel, the resource allocation information indicating one or more resources allocated for sidelink communication of the remote UE. For example, as described herein, the remote UE466 and/or the communication component 420 may execute the resource component 424 to receive resource allocation information from the relay UE464 on the at least one sidelink channel 430, the resource allocation information indicating one or more resources allocated for sidelink communication of the remote UE 466.

At block 804, the method may optionally receive timing information from the relay UE on the at least one sidelink channel. For example, the remote UE466 and/or the communication component 420 can execute the resource component 424 to receive timing information from the relay UE464 on the at least one sidelink channel 430, as described herein. At block 708, the method may transmit data to the relay UE on one or more sidelink channels in accordance with at least one of the one or more resources or timing information allocated for sidelink communications. For example, as described herein, the remote UE466 and/or the communication component 420 may execute the resource component 424 to transmit data to the relay UE464 on one or more sidelink channels (e.g., sidelink channel 430) in accordance with at least one of one or more resources or timing information allocated for sidelink communications.

In some aspects, receiving the timing information may include: at least one of timing advance information of the relay UE464 or timing advance information of the remote UE466 is received. In some aspects, receiving the timing information may include: the sidelink synchronization signal transmitted by the relay UE464 is detected, and timing advance information is determined based on the sidelink synchronization signal. In some aspects, the resource allocation information corresponds to at least one of one or more resources allocated by a network entity (e.g., base station 462) or relay UE 464.

In some aspects, a network entity (e.g., an eNB such as base station 462) may specify to relay UE464 a bulk set of resources for all of its remote UEs (including remote UE 466) linked to relay UE 464.

Fig. 9 is a flow chart of a method of wireless communication at a remote UE. The method may be performed by a UE (e.g., UE 466). At block 902, the method may transmit a scheduling request on at least one sidelink channel to a relay UE connected to a network entity. For example, as described herein, the remote UE466 and/or the communication component 420 may execute the scheduling component 426 to transmit a scheduling request to a relay UE464 connected with a network entity (e.g., the base station 462) over at least one sidelink channel 430.

At block 904, the method may receive a scheduling indication including a resource grant from the relay UE on one or more sidelink channels in response to transmitting the scheduling request. For example, as described herein, remote UE466 and/or communications component 420 may execute scheduling component 426 to receive a scheduling indication including a resource grant from relay UE464 on one or more sidelink channels (e.g., sidelink channel 430) in response to transmitting the scheduling request.

In some aspects, the resource grant may correspond to a resource allocation by the relay UE464 for a side link interface for communication between the remote UE466 and the relay UE 464. In some aspects, the scheduling request may be transmitted according to a code division multiplexing scheme. In some aspects, receiving the scheduling indication may include: receiving a SCI including an indication of an upcoming scheduling indication transmission, the indication being different from the scheduling indication; and receiving a scheduling indication from the relay UE464 corresponding to the MAC CE within the data portion of the sidelink transmission.

In some aspects, the scheduling request may be transmitted on periodic resources. Further, for example, the periodic resource may be allocated when the remote UE links to the relay UE. In some aspects, the method may further transmit the SCI on the at least one sidelink channel 430, the SCI including a flag indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, and transmit the buffer status report as a MAC CE within the data portion on the at least one sidelink channel 430.

Fig. 10 is a flow diagram 1000 of a method of scheduling resources at a relay UE. The method may be performed by a UE (e.g., UE 464). At block 1002, the method may receive a scheduling request from a remote UE on at least one sidelink channel. For example, as described herein, the relay UE464 and/or the relay component 410 may execute the schedule determining component 416 to receive a scheduling request from the remote UE466 on at least one sidelink channel 430. At block 1004, the method may determine, by the relay UE, a resource grant for the remote UE in response to receiving the scheduling request. For example, as described herein, the relay UE464 and/or the relay component 410 may execute the scheduling determining component 416 to determine, by the relay UE464, a resource grant for the remote UE466 in response to receiving the scheduling request. At block 1006, the method may transmit a scheduling indication including the resource grant to the remote UE on one or more sidelink channels. For example, as described herein, the relay UE464 and/or the relay component 410 may execute the schedule determining component 416 to transmit a scheduling indication including the resource grant to the remote UE466 on one or more sidelink channels (e.g., sidelink channel 430).

In some aspects, the scheduling request may be received according to a code division multiplexing scheme on periodic resources. In some aspects, the method may further receive another scheduling request from a disparate remote UE on the periodic resources on a sidelink channel 430, identify at least one first code associated with the remote UE466 for use in the code division multiplexing scheme and at least one second code associated with the disparate remote UE for use in the code division multiplexing scheme, the at least one first code being different from the at least one second code, determine a resource grant for the disparate remote UE based on identifying the at least one second code associated with the disparate remote UE, and transmit another scheduling indication including the resource grant for the remote UE466 to the remote UE466 on the one or more sidelink channels (e.g., sidelink channel 430).

In some aspects, transmitting the scheduling indication may include: transmit a scheduling indication including a resource grant for the remote UE466 on the one or more sidelink channels (e.g., sidelink channel 430) to the remote UE466 based on determining the at least one first code associated with the remote UE 466. In some aspects, transmitting the scheduling indication may include: the SCI including an indication of the upcoming scheduling indication transmission is transmitted to the remote UE466 and the scheduling indication corresponding to the MAC CE within the data portion of the sidelink transmission is transmitted to the remote UE 466. In some aspects, the method may further receive a SCI from the remote UE466 on the at least one sidelink channel 430, the SCI including a flag indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, and receive the buffer status report from the remote UE466 on the at least one sidelink channel 430 as a MAC CE within the data portion.

Fig. 11 is a conceptual data flow diagram 1100 illustrating the data flow between different apparatuses/components in an exemplary apparatus 1102. The apparatus may be a relay UE. The apparatus includes a receiving component 1104, a transmitting component 1106, an RNTI component 412, a resource allocation component 414, and a schedule determining component 416. Apparatus 1102 may receive communications from base station 1130 via receiving component 1104 and may transmit communications to base station 1130 via transmitting component 1106. Further, the apparatus 1102 can receive communications from the remote UE 1140 via the receiving component 1104 and can transmit communications to the remote UE 1140 via the transmitting component 1106. The RNTI component 412, resource allocation component 414, and scheduling determination component 416 can facilitate D2D communication as described herein with respect to fig. 4.

The apparatus may include additional components to perform each block of the algorithm in the aforementioned flow charts of fig. 5, 7 and 10. As such, each block in the aforementioned flow diagrams of fig. 5, 7, and 10 may be performed by a component and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the described processes/algorithms, implemented by a processor configured to perform the described processes/algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

Fig. 12 is a diagram 1200 illustrating an example of a hardware implementation of an apparatus 1202' employing a processing system 1214. The processing system 1214 may be implemented with a bus architecture, represented generally by the bus 1224. The bus 1224 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1214 and the overall design constraints. The bus 1224 links together various circuits including one or more processors and/or hardware components (represented by the processor 1204, the components 1104, 1106, 412, 414, 416, and the computer-readable medium/memory 1206). The bus 1224 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 1214 may be coupled to a transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1210 receives the signal from the one or more antennas 1220, extracts information from the received signal, and provides the extracted information to the processing system 1214 (and in particular, the receiving component 1104). Additionally, the transceiver 1210 receives information from the processing system 1214 (and in particular the transmission component 1106) and generates a signal to be applied to the one or more antennas 1220 based on the received information. The processing system 1214 includes a processor 1204 coupled to a computer-readable medium/memory 1206. The processor 1204 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 1206. The software, when executed by the processor 1204, causes the processing system 1214 to perform the various functions described supra for any particular apparatus. The computer-readable medium/memory 1206 may also be used for storing data that is manipulated by the processor 1204 when executing software. The processing system 1214 further includes at least one of the components 1104, 1106, 412, 414, and 416. These components may be software components running in the processor 1204, resident/stored in the computer readable medium/memory 1206, one or more hardware components coupled to the processor 1204, or some combination thereof. The processing system 1214 may be a component of the UE 350 and may include the memory 360 and/or at least one of: TX processor 368, RX processor 356, and controller/processor 359.

In one configuration, the apparatus 1202/1202' for wireless communication includes: the apparatus generally includes means for receiving a scheduling request from a remote UE on at least one sidelink channel, means for determining, by the relay UE in response to receiving the scheduling request, a resource grant for the remote UE, and means for transmitting a scheduling indication including the resource grant to the remote UE on one or more sidelink channels.

The aforementioned means may be the aforementioned components of the apparatus 1102 and/or one or more components of the processing system 1214 of the apparatus 1202' configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1214 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

Fig. 13 is a conceptual data flow diagram 1300 illustrating the data flow between different apparatuses/components in an exemplary apparatus 1302. The apparatus may be a remote UE. The apparatus includes a receive component 1304, a transmit component 1306, an RNTI receive component 422, a resource component 424, and a schedule component 426. Apparatus 1302 may receive communications from base station 1330 via a receiving component 1304 and may transmit communications to base station 1330 via a transmitting component 1306. Further, apparatus 1302 may receive communications from remote UE 1340 via receiving component 1304 and may transmit communications to remote UE 1340 via transmitting component 1306. RNTI receiving component 422, resource component 424, and scheduling component 426 can facilitate D2D communications as described herein with respect to fig. 4.

The apparatus may include additional components that perform each block of the algorithm in the aforementioned flow diagrams of fig. 6, 8, and 9. As such, each block in the aforementioned flow diagrams of fig. 6, 8, and 9 may be performed by a component and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the described processes/algorithms, implemented by a processor configured to perform the described processes/algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

Fig. 14 is a diagram 1400 illustrating an example of a hardware implementation of an apparatus 1402' employing a processing system 1414. The processing system 1414 may be implemented with a bus architecture, represented generally by the bus 1424. The bus 1224 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1414 and the overall design constraints. The bus 1424 links together various circuits including one or more processors and/or hardware components (represented by the processor 1204, the components 1304, 1306, 422, 424, 426, and the computer-readable medium/memory 1406). The bus 1424 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 1414 can be coupled to the transceiver 1410. The transceiver 1410 is coupled to one or more antennas 1420. The transceiver 1410 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1410 receives signals from the one or more antennas 1420, extracts information from the received signals, and provides the extracted information to the processing system 1414, and in particular the receiving component 1304. Additionally, transceiver 1410 receives information from processing system 1414, and in particular transmission component 1306, and generates a signal to be applied to the one or more antennas 1420 based on the received information. The processing system 1414 includes a processor 1404 coupled to a computer-readable medium/memory 1406. The processor 1404 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 1406. The software, when executed by the processor 1404, causes the processing system 1414 to perform the various functions described supra for any particular apparatus. The computer-readable medium/memory 1406 may also be used for storing data that is manipulated by the processor 1404 when executing software. Processing system 1414 further includes at least one of components 1304, 1306, 422, 424, and 426. These components may be software components running in the processor 1404, resident/stored in the computer readable medium/memory 1406, one or more hardware components coupled to the processor 1204, or some combination thereof. The processing system 1414 may be a component of the UE 350 and may include the memory 360 and/or at least one of: TX processor 368, RX processor 356, and controller/processor 359.

In one configuration, the apparatus for wireless communication 1402/1402' includes: the apparatus generally includes means for transmitting a scheduling request on at least one sidelink channel to a relay UE connected to a network entity, and means for receiving a scheduling indication including a resource grant on one or more sidelink channels from the relay UE in response to transmitting the scheduling request.

The aforementioned means may be the aforementioned components of apparatus 1302 and/or one or more components of processing system 1414 of apparatus 1402' configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1414 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

It should be understood that the specific order or hierarchy of blocks in the processes/flow diagrams disclosed is an illustration of exemplary approaches. It will be appreciated that the specific order or hierarchy of blocks in the processes/flow diagrams may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous 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 readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. The word "exemplary" is used herein to mean serving as an "example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. The term "a" or "an" refers to one or more, unless specifically stated otherwise. 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, and may include a plurality of a, B, or C. In particular, 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 a only, B only, C only, a and B, a and C, B and C, or a and B and C, wherein any such combination may include one or more members of a, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The terms "module," mechanism, "" element, "" device, "and the like may not be a substitute for the term" means. Thus, no claim element should be construed as a device plus function unless the element is explicitly recited using the phrase "device for \8230; \8230.

Claims (24)

1. A method of wireless communication at a remote user equipment, UE, comprising:

transmitting a scheduling request to a relay UE connected to a network entity on a first sidelink channel;

receiving a scheduling indication comprising a resource grant on a second sidelink channel from the relay UE in response to transmitting the scheduling request;

sending an Sidelink Control Indication (SCI) over the first sidelink channel on at least one resource allocated in accordance with a resource grant from the relay UE, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

transmitting the buffer status report as a media access control, MAC, control element, CE, within the data portion on the first sidelink channel.

2. The method of claim 1, wherein the resource grant corresponds to a resource allocation by the relay UE for a side link interface for communication between the remote UE and the relay UE.

3. The method of claim 1, wherein the scheduling request is transmitted according to a code division multiplexing scheme.

4. The method of claim 1, wherein receiving the scheduling indication comprises:

receiving a Sidelink Control Indication (SCI) for transmission of the buffer status report, the SCI being different from the scheduling indication; and

receiving the scheduling indication corresponding to a media access control, MAC, control element, CE, within a data portion of a sidelink transmission from the relay UE.

5. The method of claim 1, wherein the scheduling request is transmitted on a periodic resource.

6. The method of claim 5, wherein the periodic resource is allocated when the remote UE links to the relay UE.

7. A method of wireless communication at a relay User Equipment (UE), comprising:

receiving a scheduling request from a remote UE on a first sidelink channel;

determining, by the relay UE, a resource grant for the remote UE in response to receiving the scheduling request;

transmitting a scheduling indication including the resource grant to the remote UE on a second sidelink channel;

receiving a Sidelink Control Indication (SCI) from the remote UE via the first sidelink channel on at least one resource allocated according to the resource grant, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

receiving the buffer status report from the remote UE on the first sidelink channel as a media access control, MAC, control element, CE, within the data portion.

8. The method of claim 7, wherein the scheduling request is received on periodic resources according to a code division multiplexing scheme, the method further comprising:

receiving another scheduling request on the first sidelink channel from a disparate remote UE on the periodic resource;

identifying at least one first code associated with the remote UE used in the code division multiplexing scheme and at least one second code associated with the disparate remote UE used in the code division multiplexing scheme, the at least one first code being different from the at least one second code;

determining a resource grant for the disparate remote UE based on identifying the at least one second code associated with the disparate remote UE; and

transmitting, to the remote UE, another scheduling indication comprising the resource grant for the remote UE on the second sidelink channel.

9. The method of claim 8, wherein transmitting the scheduling indication comprises: transmitting the scheduling indication including the resource grant for the remote UE to the remote UE on the second sidelink channel based on the determination of the at least one first code associated with the remote UE.

10. The method of claim 7, wherein transmitting the scheduling indication comprises:

transmitting a Sidelink Control Indication (SCI) for transmission of the buffer status report to the remote UE; and

transmitting the scheduling indication corresponding to a media access control, MAC, control element, CE, within a data portion of a sidelink transmission to the remote UE.

11. A remote user equipment, UE, for wireless communication, comprising:

a memory; and

a processor in communication with the memory, wherein the processor is configured to:

transmitting a scheduling request to a relay UE connected to a network entity on a first sidelink channel;

receiving a scheduling indication comprising a resource grant on a second sidelink channel from the relay UE in response to transmitting the scheduling request;

sending a Sidelink Control Indication (SCI) via the first sidelink channel on at least one resource allocated according to a resource grant from the relay UE, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

transmitting the buffer status report as a media access control, MAC, control element, CE, within the data portion on the first sidelink channel.

12. The remote UE of claim 11, wherein the resource grant corresponds to a resource allocation by the relay UE for a side link interface for communication between the remote UE and the relay UE.

13. The remote UE of claim 11, wherein the scheduling request is transmitted according to a code division multiplexing scheme.

14. The remote UE of claim 11, wherein to receive the scheduling indication, the processor is further configured to:

receiving a Sidelink Control Indication (SCI) for transmission of the buffer status report, the SCI being different from the scheduling indication; and

receiving the scheduling indication corresponding to a media access control, MAC, control element, CE, within a data portion of a sidelink transmission from the relay UE.

15. The remote UE of claim 11, wherein the scheduling request is transmitted on a periodic resource.

16. The remote UE of claim 15, wherein the periodic resource is allocated when the remote UE links to the relay UE.

17. A relay user equipment, UE, for wireless communication, comprising:

a memory; and

a processor in communication with the memory, wherein the processor is configured to:

receiving a scheduling request from a remote UE on a first sidelink channel;

determining a resource grant for the remote UE in response to receiving the scheduling request;

transmitting a scheduling indication including the resource grant to the remote UE on a second sidelink channel;

receiving a Sidelink Control Indication (SCI) from the remote UE via the first sidelink channel on at least one resource allocated according to the resource grant, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

receiving the buffer status report from the remote UE on the first sidelink channel as a media access control, MAC, control element, CE, within the data portion.

18. The relay UE of claim 17, wherein the scheduling request is received on a periodic resource according to a code division multiplexing scheme, the processor further configured to:

receiving another scheduling request on the first sidelink channel from a disparate remote UE on the periodic resource;

identifying at least one first code associated with the remote UE used in the code division multiplexing scheme and at least one second code associated with the disparate remote UE used in the code division multiplexing scheme, the at least one first code being different from the at least one second code;

determining a resource grant for the disparate remote UE based on identifying the at least one second code associated with the disparate remote UE; and

transmitting, to the remote UE, another scheduling indication comprising the resource grant for the remote UE on the second sidelink channel.

19. The relay UE of claim 18, wherein to transmit the scheduling indication, the processor is further configured to transmit the scheduling indication to the remote UE on the second sidelink channel including the resource grant for the remote UE based on determining the at least one first code associated with the remote UE.

20. The relay UE of claim 17, wherein to transmit the scheduling indication, the processor is further configured to:

transmitting a Sidelink Control Indication (SCI) for transmission of the buffer status report to the remote UE; and

transmitting the scheduling indication corresponding to a media access control, MAC, control element, CE, within a data portion of a sidelink transmission to the remote UE.

21. A remote user equipment, UE, for wireless communication, comprising:

means for transmitting a scheduling request on a first sidelink channel to a relay UE connected to a network entity;

means for receiving a scheduling indication comprising a resource grant on a second sidelink channel from the relay UE in response to transmitting the scheduling request;

means for sending a Sidelink Control Indication (SCI) via the first sidelink channel on at least one resource allocated according to a resource grant from the relay UE, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

means for transmitting the buffer status report as a media access control, MAC, control element, CE, within the data portion on the first sidelink channel.

22. A relay user equipment, UE, for wireless communication, comprising:

means for receiving a scheduling request from a remote UE on a first sidelink channel;

means for determining, by the relay UE, a resource grant for the remote UE in response to receiving the scheduling request;

means for transmitting a scheduling indication including the resource grant to the remote UE on a second sidelink channel;

means for receiving, from the remote UE via the first sidelink channel, an Sidelink Control Indication (SCI) on at least one resource allocated in accordance with the resource grant, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

means for receiving the buffer status report from the remote UE on the first sidelink channel as a media access control, MAC, control element, CE, within the data portion.

23. A non-transitory computer-readable medium storing computer executable code for wireless communication at a remote User Equipment (UE), the computer executable code comprising code to:

transmitting a scheduling request to a relay UE connected to a network entity on a first sidelink channel;

receiving a scheduling indication comprising a resource grant on a second sidelink channel from the relay UE in response to transmitting the scheduling request;

sending a Sidelink Control Indication (SCI) via the first sidelink channel on at least one resource allocated according to a resource grant from the relay UE, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

transmitting the buffer status report as a media access control, MAC, control element, CE, within the data portion on the first sidelink channel.

24. A non-transitory computer-readable medium storing computer executable code for wireless communication at a relay User Equipment (UE), the computer executable code comprising code for:

receiving a scheduling request from a remote UE on a first sidelink channel;

determining, by the relay UE, a resource grant for the remote UE in response to receiving the scheduling request;

transmitting a scheduling indication including the resource grant to the remote UE on a second sidelink channel;

receiving a Sidelink Control Indication (SCI) from the remote UE via the first sidelink channel on at least one resource allocated according to the resource grant, the SCI indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, the buffer status report associated with the first sidelink channel; and

receiving the buffer status report from the remote UE on the first sidelink channel as a media access control, MAC, control element, CE, within the data portion.

Images