Managing signals over multiple wireless links

Abstract

A method and related apparatus for wireless communication at a first user equipment (UE) are provided. In the method, the first UE communicates with one or more UEs over an SL (SL). The first UE also sends or receives configuration information for SL communication with the one or more UEs or uplink communication with a network entity. The approach improves the reliability of wireless communications, particularly in XR-related applications, and facilitates power transfer for energy harvesting UEs.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 935,080, filed on September 23, 2022, entitled “MANAGING SIGNALS ON MULTIPLEWIRELESS LINKS,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communications including signal management over multiple wireless links. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

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

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

[0007] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to communicate with one or more UEs via a sidelink (SL). The at least one processor may also be configured to send or receive configuration information for SL communication with the one or more UEs or uplink communication with a network entity.

[0008] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to receive configuration information for SL communication of a first UE. The at least one processor may also be configured to provide the configuration information for the SL communication of the first UE to a second UE with which the network entity communicates via an access link.

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

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

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4is a diagram illustrating an example time slot structure for SL communication.

[0017] Figure 5A is a diagram illustrating a connection between a UE and a base station according to various aspects of the present disclosure.

[0018] Figure 5B is a diagram illustrating overlap between uplink transmissions and sidelink transmissions according to various aspects of the present disclosure.

[0019] Figure 6 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0020] Figure 7 is a first flow chart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0021] Figure 8 is a second flow chart illustrating a method of performing wireless communication at a UE according to various aspects of the present disclosure.

[0022] Fig. 9 is a first flow chart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure.

[0023] Fig.10 is a second flow chart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure.

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

[0025] Fig.12 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0026] Fig.13A and Fig. 13B is a communication flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0027] Fig.14A and Fig. 14B is a communication flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0028] Wireless communication services related to extended reality (XR) are quasi-periodic, with the characteristics of low latency and high reliability requirements. For XR-related applications, there may be jitter when the periodic services of the application layer arrive at the modem, for example, there may be random jitter in the arrival time of the data service. The present disclosure provides a method, an apparatus, and a computer-readable storage medium for exchanging information between a sidelink (SL) UE and an access link UE (Uu UE) with or without the participation of a base station to enhance the reliability of wireless communication. In some examples, the various aspects presented herein may improve wireless communications over multiple links. In some examples, the various aspects presented herein may be used to improve wireless communications for XR-related applications, as well as other examples of wireless communications. In some aspects, a UE may communicate with one or more UEs via SL. The UE may send or receive configuration information for SL communication with the one or more UEs or uplink communication with a network entity. For example, if the UE is communicating with a network, the UE may receive configuration information for sidelink communication of another UE. The UE may use the information to adjust uplink transmission with the network and / or sidelink communication with the other UE. The adjustment may be to improve communication with the network and / or improve sidelink reception at the other UE based on the sidelink communication. If the UE is communicating via a sidelink, the UE may receive configuration information for uplink communication of another UE. In some aspects, the UE may adjust communications based on the information, for example, to improve accurate reception of the sidelink communication and / or reduce interference with communications between the other UE and the network. The various aspects presented herein enable adjustment of communications between UEs based on information in the configuration information, improve reliability of wireless communications (such as in XR-related applications), and / or facilitate power transmission of energy harvesting UEs.

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

[0030] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

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

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

[0034] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or components. In a 5GNR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements or network equipment such as base stations (BS) or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

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

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

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

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

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

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

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

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

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

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

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

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

[0047] Some examples of SL communications may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle-to-network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle-to-pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof, and / or a vehicle-based communication device communicating with other devices, which may be collectively referred to as vehicle-to-everything (V2X) communications. SL communications may be based on V2X or other D2D communications, such as proximity services (ProSe), etc. In addition to UEs, SL communications may also be sent and received by other sender devices and receiver devices, such as roadside units (RSUs), etc. In some aspects, a PC5 interface may be used to exchange SL communications. Figure 4 An example time slot structure that can be used for SL communication is illustrated. Figure 4 The example time slot structure may provide example aspects for SL communications related to 5G NR, but the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

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

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

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

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

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

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

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

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

[0056] See again Figure 1 In some aspects, the UE 104 may include a SL communication component 198 configured to: communicate with one or more UEs via SL; and send or receive configuration information for SL communication with the one or more UEs or uplink communication with a network entity. In some aspects, the base station 102 may include a SL indication component 199 configured to: receive configuration information for SL communication of a first UE; and provide the configuration information for the SL communication of the first UE to a second UE with which the network entity communicates via an access link. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0057] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0058] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0059]

[0060] Table 1: Parameter set, SCS and CP

[0061] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0062] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0063] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0064] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0065] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0066] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may be used to carry, among other things, buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0067] Figure 3 3 is a block diagram of a first wireless communication device 310 in communication with a second wireless communication device 350. In some aspects, the wireless communication may be based on an access link, such as a Uu connection. In some aspects, the wireless communication may be based on a SL, such as using a PC5 interface. In some aspects, the device 310 may be a base station 310 that communicates with a UE (e.g., device 350) in an access network. In some examples, the devices 310 and 350 may communicate based on SL communications such as V2X or other D2D communications. For example, the device 350 may be a UE, and the device 310 may include a second UE, an RSU, a base station, etc.

[0068] For instance, in a DL example, an Internet Protocol (IP) packet 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 service data adaptation protocol (SDAP) layer, 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 broadcasting of system information (e.g., MIB, SIB), 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 for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

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

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

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

[0072] Similar to the functionality described in conjunction with DL transmissions performed by device 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 (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

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

[0074] UL transmissions are handled at device 310 in a manner similar to that described in conjunction with the receiver functionality at device 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to an RX processor 370.

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

[0076] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the SL communication component 198.

[0077] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The SL indicates various aspects related to component 199.

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

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

[0080] The UE may send a SL transmission including a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH), which may be received by one or more UEs, for example, directly from the sending UE rather than via a base station. The control channel may include information for decoding the data channel (e.g., SL control information (SCI)), which includes reservation information, such as information about time and / or frequency resources reserved for data channel transmission.

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

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

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

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

[0085] Wireless communication services related to extended reality (XR) are quasi-periodic, with the characteristics of low latency and high reliability requirements. For XR-related applications, there may be jitter when the periodic services of the application layer arrive at the modem. There may be random jitter in the arrival time. For example, it can be assumed that the random jitter follows a truncated Gaussian distribution with a mean of 0, a standard deviation of 2 milliseconds, and a range of [-4,4] milliseconds. The packet delay budget (PDB) of XR-related service flows may be limited, and the PDB requirements may be strict for some flows. In actual applications, UL XR-related services may be sent frequently. Table 2 shows the PDB for various XR-related applications.

[0086]

[0087] Table 2. PDBs for various XR-related applications

[0088] In some applications, the UE may not send a scheduling request (SR) or BSR for each TB, and the UE may not blindly decode the DCI for each PUSCH transmission, which can reduce the transmission latency and save power consumption of XR-related UEs. Considering the characteristics of XR-related services, it may be beneficial to send a cell group (CG)-based PUSCH or multiple PUSCHs scheduled by UL DCI.

[0089] The various aspects provided herein provide improvements and optimizations that can improve wireless communications for XR-related applications. These improvements / optimizations may include enabling increased awareness of XR service (both UL and DL) characteristics, QoS metrics, and application layer attributes, and utilizing such information to assist in XR specific service handling. These improvements / optimizations may also include increased capacity, such as SPS and CG enhancements and dynamic scheduling / grant enhancements, which provide more efficient resource allocation and scheduling for XR service characteristics (such as periodicity, multiple streams, jitter, latency, and reliability of XR services). Although XR is an example of a type of wireless communication or signaling, the various aspects presented herein can help improve any of various types of wireless communications and signaling, including access link communications, sidelink communications, energy harvesting, and the like with a network.

[0090] The present disclosure provides methods, apparatus, and computer-readable storage media for exchanging information between sidelink (SL) UEs and Uu UEs with or without network involvement to enhance the reliability of wireless communications of these UEs. Various aspects include power control switching based on events (such as providing data or energy to energy harvesting UEs), and discuss power control constraints for non-orthogonal multiple access (NOMA) transmissions and the concept of relaxing power control when the SL UE has shared information and / or configuration information about sidelink resource allocations with a base station. The methods, apparatus, and computer-readable media presented herein improve the reliability of wireless communications (such as in XR applications) and facilitate power transfer for energy harvesting UEs while also supporting communication over multiple links.

[0091] Figure 5A 5 is a diagram illustrating signal management on multiple links according to various aspects of the present disclosure. Figure 5A As shown, UE1 501 and UE2 502 may communicate using a sidelink (SL) connection (e.g., 510). UE3 503 may be using a Uu link or access link 530 with a network node (such as a base station 504), and may also be exchanging sidelink communications with UE1 501 and / or UE2 502, for example, via a sidelink 520. For example, UE3 503 may have established an RRC connection with one or both of UE1 501 and UE1 502 for the sidelink.

[0092] See also Figure 5A In one example, UE2 502 and UE3 503 may, for example, be in an RRC connected state and may exchange sidelink communications, as shown at 520. During some UL time slots (a subset of which may overlap with SL communications of one or more UEs among UE1 501, UE2 502 and / or UE3 503, for example, for such SL communications), uplink and / or downlink communications between UE3 503 and the base station 504 may interfere with the sidelink communications of UE1 501 and / or UE2 502. Similarly, sidelink communications from UE1 501 and / or UE2 502 may interfere with downlink reception of UE3 503 and / or uplink reception of the base station 504. Various aspects presented herein support exchanging communications regarding a planned sidelink communication and / or access link communication of a UE, enabling one of the other UEs to make wireless communication adjustments to improve their own communications or to improve reception at the UE providing the information.

[0093] In some aspects, UE3 503 may signal its UL configuration grant configuration information (e.g., which may include CG type 1 or CG type 2) so that UE1 501 and UE2 502 adjust their transmission parameters (e.g., modulation and coding scheme (MCS)) accordingly to optimize communication. For example, UE2 502 may use a different MCS for sidelink communications that will overlap with UE3's CG resources (e.g., to avoid interference with communications between UE3 503 and base station 504 or to improve sidelink reception at UE1 501). Changing the MCS is just one example of communication adjustment. In other aspects, UE2 may use different transmit power, resources, MCS, or other transmit parameters for the transmission of sidelink communications that will overlap with resources configured for UE3 503, compared to sidelink communications that will not overlap with resources configured for UE3 503. Figure 5B An example resource map 550 is illustrated showing an uplink transmission 552 overlapping in time with a sidelink transmission 554. Although only the overlap in the time domain is shown, in some aspects the uplink transmission and the sidelink transmission may additionally or alternatively have overlapping frequency resources.

[0094] In another example, see Figure 5A, the sending UE (which may be one of UE1 501 and UE2 502) or the base station 504 may signal the configuration of the SL configuration grant to UE3 503. In some aspects, the resources used for sidelink communication may be configured by the base station 504 for UE1 501 and / or UE2 502. For example, UE2 502 may provide resource allocation information for sidelink communication of UE2 502 and / or UE1 501 to UE3 503 in a sidelink message. In some aspects, the base station 504 may provide resource allocation information for sidelink communication of UE1 501 and / or UE2 502 to UE3 in a downlink message. UE3 503 may avoid using the resources (e.g., time slots) in the SL configuration grant of UE1 501 or UE2 502 for its own uplink transmission.

[0095] In some aspects, a SL UE (e.g., UE1 501 or UE2 502) may share configuration information for sidelink communication with a Uu UE (e.g., a UE participating in or supporting Uu communication with a network, such as UE3 503), so that the other UE may adjust its communication based on the configuration information for sidelink communication. The configuration information may be provided directly to UE3, for example, in a sidelink message from UE1 501 or UE2 502. After UE1 501 or UE2 502 provides the configuration information to the base station 504, UE3 may receive the configuration information via the base station 504, for example, in a downlink message. The shared configuration information for sidelink communication (e.g., of UE1 501 or UE2 502) may include, but is not limited to, one or more of the following: time domain resource allocation (TDRA), frequency domain resource allocation (FDRA), power control information of the transmit power that the UE will use to send the sidelink communication, beam information (e.g., the beam that UE1 or UE2 plans to use to send the sidelink communication), MCS for sidelink communication, data priority indication for data to be sent in the sidelink communication, and PDB information (such as remaining PDBs for data to be sent in the sidelink communication). For example, based on the configuration information shared by the SL UE (e.g., UE1 501 or UE2 502), UE3 503 may cancel uplink transmission or adjust uplink transmission, such as to reduce the power or other transmission parameters of the uplink transmission, thereby reducing or eliminating the interference caused by the uplink transmission of UE3 503 to the SL communication of UE1 501 or UE2 502.

[0096] UE3 503 may change the transmission parameters of the uplink transmission that overlaps with the sidelink communication of UE1 501 or UE2 502 in time and / or frequency based on whether the uplink transmission overlaps with the sidelink communication of UE1 501 or UE2 502 (e.g., using corresponding resources), including using different power control, MCS and / or beam for the uplink transmission. UE3 503 may also change the transmission parameters of the uplink transmission based at least in part on one or more of the following elements: the priority of the Uu packet to be sent by UE3503 in the uplink transmission, the priority of the SL UE packet to be sent by UE1 501 or UE2 502, the remaining PDB of the Uu packet to be sent by UE3 503 in the uplink transmission, the remaining PDB of the SL packet to be sent by UE1 501 or UE2 502 (for example, if the remaining PDB is known based on the priority and the timestamp added to the packet), configuration information about sidelink communication shared by SL UEs (for example, UE1 501 or UE2 502) (such as the beam direction used for sidelink communication, the transmit precoding matrix indicator (TPMI), TDRA, FDRA and / or power control information), or a combination thereof.

[0097] Fig.13A An example communication flow 1300 is illustrated showing a UE 1304 exchanging Uu communications with a base station 1306. For example, the UE 1304 may correspond to UE3 503. As illustrated at 1310, the UE 1304 receives configuration information regarding sidelink communications from the UE 1302, e.g., in a sidelink message from the UE 1302. In response, at 1312, the UE 1304 may adjust one or more parameters or resources for an uplink transmission 1317 to the base station 1306. The adjustment may be to address potential interference that a sidelink transmission (e.g., 1316) from the UE 1302 to the UE 1308 may cause to the uplink transmission 1317. Alternatively, the adjustment to the uplink transmission 1317 may be to reduce interference caused by the uplink transmission 1317 to the reception of the sidelink communication 1316 (e.g., reception by the UE 1308 or the UE 1302).

[0098] Fig. 13BAn example communication flow 1350 is illustrated showing a UE 1352 exchanging Uu communications with a base station 1354. For example, UE 1352 may correspond to UE3 503. As illustrated at 1362, UE 1352 receives configuration information regarding sidelink communications for UE 1356 from base station 1354, e.g., in a downlink message. At 1360, base station 1354 may receive the configuration information from UE 1356. As illustrated at 1364, UE 1352 may adjust one or more parameters or resources for uplink transmissions 1368. Similarly, at 1366, base station 1354 may adjust one or more parameters for downlink transmissions 1370 based on the received configuration information for sidelink communications for UE 1356. The adjustment at 1364 or 1366 may be to address potential interference that a sidelink transmission (e.g., 1372) from UE 1356 to UE 1358 may cause to an uplink transmission 1368 or a downlink transmission 1370. Alternatively, the adjustment to the uplink transmission 1368 or the downlink transmission 1370 may be to reduce interference caused by the uplink transmission 1368 of the downlink transmission 1370 to the reception of the sidelink communication 1372 (e.g., reception by UE 1358 or UE 1356).

[0099] In some aspects, a UE, such as UE1 501 or UE2 502, that is transmitting a sidelink communication may change a transmission parameter for the sidelink transmission based on information about the Uu communication of UE3 503. For example, UE1 501 or UE2 502 may adjust or change at least one of the resources, power control, MCS, and / or beam of the sidelink transmission based on whether UE3 503 is using the corresponding resources to communicate with the base station 504. UE1 501 or UE2 502 may adjust the sidelink transmission to improve the reception of the sidelink communication. For example, when the sidelink transmission to UE1 501 overlaps in time and / or frequency with the uplink transmission by UE3 503, UE2 502 may adjust the parameters of the sidelink transmission (e.g., increase the transmission power or reduce the MCS) to improve the reception of the sidelink transmission. In other aspects, UE2 502 may adjust the parameters of the sidelink transmission to UE1 to avoid interference with the communication between UE3 503 and the base station 504. The SL UE may change the transmission parameters of the sidelink transmission based at least in part on one or more of the following elements: the priority of the Uu UE packet to be sent by UE3 503, the priority of the SL UE packet, the remaining PDB of the Uu packet to be sent by UE3 503, the remaining PDB of the SL packet (if the remaining PDB is known based on the priority and the timestamp added to the packet), information shared by UE3 503 and the SL UE or received via the base station (such as the beam of the uplink transmission, TPMI, TDRA, FDRA, power control), or a combination thereof.

[0100] Fig.14A An example communication flow 1400 is illustrated showing a UE 1404 exchanging Uu communications with a base station 1406. For example, UE 1404 may correspond to UE3 503. As illustrated at 1410, UE 1404 sends configuration information regarding Uu communications to UE 1402, such as in a sidelink message from UE 1404. In response, UE 1402 may adjust one or more parameters or resources for a sidelink transmission (e.g., 1416) to UE 1408, as illustrated in 1412. The adjustment may be to address potential interference that the sidelink transmission (e.g., 1416) from UE 1402 to UE 1408 may cause to Uu communications 1417. Alternatively, the adjustment to the sidelink transmission (eg, 1416) may be to reduce interference caused by the Uu communication 1417 to the reception of the sidelink communication 1416 (eg, reception by UE 1408 or UE 1402).

[0101] Fig. 14BAn example communication flow 1450 is illustrated showing a UE 1452 exchanging Uu communications 1470 with a base station 1454. For example, UE 1452 may correspond to UE3 503. As illustrated at 1460, UE 1456 receives configuration information regarding Uu communications for UE 1452 from base station 1454, e.g., in a downlink message. As illustrated at 1466, UE 1456 may adjust one or more parameters or resources for sidelink transmissions (e.g., 1472) based on the configuration information for Uu communications 1470 received from the base station. The adjustment at 1366 may be to address potential interference that sidelink transmissions (e.g., 1472) from UE 1456 to UE 1458 may cause to Uu communications 1470. Alternatively, the adjustment at 1466 to the sidelink transmission (e.g., 1472) can be to reduce interference caused by the Uu communication 1470 to the reception of the sidelink communication 1472 (e.g., reception by UE 1458 or UE 1456).

[0102] If the base station 504 is aware of the SL configuration (e.g., received from UE1 501 or UE2 502), the base station may instruct UE3 503 to adjust at least one or more of the transmission parameters of the uplink communication of UE3 503 to take into account the sidelink communication of UE1 501 or UE2 502. The transmission parameters may include, but are not limited to, power control, beam, TPMI, MCS, and the number of transmit ports / layers. The adjustment of the transmission parameters may be based at least in part on one or more of the following elements: priority of Uu UE packets, priority of SL UE packets, remaining PDB of Uu packets, remaining PDB of SL packets, information shared by SLUE with Uu UE or with the base station (such as beam, TPMI, TDRA, FDRA, power control), or a combination thereof. In some aspects, the Uu UE may adjust the beam and may select the TPMI to reduce or eliminate interference at the SL receiving UE.

[0103] In one example, UE3 503 may signal beam limitation to UE1 501 or UE2 502 so as to limit one or more beams used for sidelink communications transmitted by UE1 501 or UE2 502. In another example, the base station 504 may indicate one or more beams to be used or avoided by UE1 501 or UE2 502 based on feedback information from UE3 503 about beams currently recommended for communication with the base station. In addition, the base station 504 may signal beam limitation for UE3 503 so as to avoid interference of sidelink transmissions of UE1 501 or UE2 502 with Uu communications of UE3 503. In some aspects, the base station 504 may indicate beams or beam limitation to UE3 503 so as to avoid interference of uplink transmissions of UE3 503 with sidelink communications of UE1 501 or UE2 502. In some aspects, the base station 504 or UE3 503 may indicate beam information based on the importance / priority of the SL transmission. The base station 504 may reduce the interference impact from the SL transmitting UE at the base station by adjusting the analog beam and digital beam / precoder of the Uu UE.

[0104] In the above example, the adjustment of the transmission parameter may depend on the degree or amount of resource overlap between the resources used for Uu communication and the resources used for sidelink communication. That is, the parameter adjustment and the mapping table reflecting the correspondence between the parameter adjustment and the corresponding element may depend on the amount of overlap between SL communication and Uu communication in the time domain or frequency domain (or both), for example, such as Figure 5B In some examples, the mapping may be a function of the degree of overlap between REs, RBs, RE groups, or RB groups between the SL link and the Uu link. The mapping may also depend on the amount of resources that overlap in the time domain and the amount of resources that overlap in the frequency domain between the SL communication and the Uu communication.

[0105] The base station may utilize the information shared by the SL for NOMA transmission. The base station 504 may constrain the power reaching its receiver (e.g., UE1 501 or UE2 502) from the SL communication to reduce interference at the base station. However, in applications employing NOMA, doing so may introduce interference at the base station, especially when more than two UEs use the same time slot. Therefore, the NOMA time slot may include adjustments from the base station (e.g., more power control constraints).

[0106] In one configuration, the base station 504 may define some additional power offsets at UEs that apply NOMA for SL communications to further reduce interference at the base station 504. The power offset may be a function of the number of UEs using NOMA allocations (configuration grant type of type 1 or type 2, or dynamic allocation) during resource allocation.

[0107] If UE1 501 or UE2 502 shares SL configuration information with the base station 504, the base station can eliminate some interference without constraining the interference of the sidelink communication from UE1 501 or UE2 502. In this example, when the base station 504 performs continuous interference cancellation, receiving the SL transmission at a higher power can actually facilitate the elimination of interference caused by the SL transmission. Therefore, the base station 504 may not constrain the transmission power used for the sidelink transmission or may reduce the constraint on the transmission power, which may be useful for energy harvesting applications. For example, a higher transmission power can transmit a more efficient signal to provide energy to an energy harvesting device.

[0108] If UE1 or UE2 shares the SL configuration with base station 504, and if the receiving UE is an energy harvesting (EH) UE (receiving data or energy), UE1 or UE2 may relax the DL path loss constraint (e.g., based on an agreement between the energy harvesting UE or the energy harvesting UE and base station 504).

[0109] In some applications, even if the base station 504 requests the UE to use a DL path loss configuration, there may be an event-based switching mechanism that uses another path loss configuration and target power configuration (e.g., such a configuration for a SL link between UEs or a Uu link between a UE and a network node, or another path loss / target power configuration) to send energy or data at a relatively higher power so that the EH receiving UE can utilize the higher power (e.g., some EH UEs can split power between EH and data reception).

[0110] Figure 6 600 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure. Although various aspects are described with respect to base station 604, these aspects may be performed by a base station in an aggregation and / or by one or more components of base station 604 (e.g., such as CU 110, DU 130, and / or RU 140).

[0111] like Figure 6 As shown, the first UE 602 can communicate with one or more UEs 606 via SL communication 608. At 610, the first UE 602 can send or receive configuration information for SL communication with the one or more UEs 606. At 612, the first UE 602 can send or receive uplink communications with the base station 604.

[0112] In some aspects, at 614, the first UE 602 may establish an RRC connection with a second UE 616 communicating with the network over an access link. In one configuration, the second UE 616 may be one of the one or more UEs 606. In another configuration, the second UE 616 may be a different UE than the one or more UEs 606.

[0113] At 618, the first UE 602 may send a configuration for SL communication (608) to the second UE 616. At 620, the first UE 602 may receive resource information for uplink communication of the second UE 616 from the second UE 616. At 622, the first UE 602 may adjust SL communication (608) with a third UE. The adjustment may be made based on the resource information for uplink communication of the second UE 616. In one configuration, the third UE may be one of the one or more UEs 606.

[0114] At 624, the first UE 602 may adjust uplink communications (612) with the base station 604 based on the configuration information for SL communications (608) with the one or more UEs 606. In some aspects, the first UE 602 may receive an indication from the base station 604 to adjust uplink communications (612) with the base station 604 based on the configuration information for SL communications (608).

[0115] At 626, the first UE 602 may send configuration information for the SL communication (608) of the first UE to the base station 604. At 628, the base station 604 may adjust uplink communication (612) based on the configuration information for the SL communication (608) it received at 626.

[0116] At 630, the first UE 602 may receive a first beam limitation from the base station 604. The first UE 602 may also receive the first beam limitation from the second UE 616. At 630, the first UE 602 may also receive a power offset for non-orthogonal multiple access (NOMA) on the SL from the base station 604 to reduce interference at the base station 604. At 632, the first UE 602 may send a second beam limitation for SL communication (608) to one or more UEs 606. At 634, the first UE 602 may relax the path loss constraint. In one configuration, the base station 604 may relax the path loss constraint based on the energy harvesting operation of the first UE 602. Alternatively, the base station 604 may relax the path loss constraint based on sending configuration information for SL communication (608) to the base station 604.

[0117] Figure 7700 is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure. The method may be performed by a UE (i.e., a first UE). The UE may be UE 104, 502, 503, 602, 1302, 1304, 1352, 1356, 1402, 1404, 1452, 1456; device 350; or Fig.11 The method enables adjusting SL communication between UEs based on information of access links. Therefore, the method improves the reliability of wireless communication (especially for XR-related applications) and facilitates power transmission of energy-harvesting UEs.

[0118] like Figure 7 As shown, at 702, a first UE may communicate with one or more UEs via a SL. Figure 6 Various aspects of the steps associated with flowchart 700 are illustrated. For example, see Figure 6 , the first UE 602 can communicate with one or more UEs 606 via SL communication 608.

[0119] At 704, the first UE may send or receive configuration information for SL communication with one or more UEs or uplink communication with a network entity. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 504; base station 504, 604; device 310; or Fig.11 For example, see Figure 6 At 610, the first UE 602 may send or receive configuration information for SL communication (608) with one or more UEs 606. At 612, the first UE 602 may send or receive uplink communication (612) with a network entity (base station 604). Fig.13A An example is illustrated in which UE 1302 sends configuration information for sidelink communication to UE 1304. Fig.13A Also illustrated is an example in which UE 1304 receives configuration information for sidelink communications from UE 1302. Fig. 13B An example is illustrated in which UE 1356 sends configuration information for sidelink communications to base station 1354. Fig. 13B Also illustrated is an example in which UE 1352 receives configuration information for sidelink communications for UE 1356 from base station 1354. Fig.14A An example is illustrated in which UE 1402 receives configuration information for Uu communication of UE 1404 from UE 1404. Fig. 14BAn example is illustrated in which UE 1456 receives configuration information for Uu communication of UE 1452 from base station 1454.

[0120] Figure 8 800 is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure. The method may be performed by a UE (i.e., a first UE). The UE may be UE 104, 502, 503, 602, 1302, 1304, 1352, 1356, 1402, 1404, 1452, 1456; device 350; or Fig.11 The method enables adjusting SL communication between UEs based on information of access links. The method improves the reliability of wireless communication (especially in XR-related applications) and facilitates power transmission of energy-harvesting UEs.

[0121] like Figure 8 As shown, at 802, a first UE may communicate with one or more UEs via a SL. Figure 6 Various aspects of the steps associated with flowchart 800 are illustrated. For example, see Figure 6 , the first UE 602 can communicate with one or more UEs 606 via SL communication 608.

[0122] At 812, the first UE may send or receive configuration information for SL communication with one or more UEs or uplink communication with a network entity. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102; base stations 504, 604; device 310; or Fig.11 For example, see Figure 6 At 610, the first UE 602 may send or receive configuration information for SL communication (608) with one or more UEs 606. At 612, the first UE 602 may send or receive uplink communication (612) with a network entity (base station 604). Fig.13A An example is illustrated in which UE 1302 sends configuration information for sidelink communication to UE 1304. Fig.13A Also illustrated is an example in which UE 1304 receives configuration information for sidelink communications from UE 1302. Fig. 13B An example is illustrated in which UE 1356 sends configuration information for sidelink communications to base station 1354. Fig. 13B Also illustrated is an example in which UE 1352 receives configuration information for sidelink communications for UE 1356 from base station 1354. Fig.14AAn example is illustrated in which UE 1402 receives configuration information for Uu communication of UE 1404 from UE 1404. Fig. 14B An example is illustrated in which UE 1456 receives configuration information for Uu communication of UE 1452 from base station 1454.

[0123] In some aspects, the configuration information may include one or more of: a configuration grant resource allocation for SL communication, power control information for SL communication, beam information for SL communication, a modulation and coding scheme (MCS) for SL communication, a data priority indication for SL communication, or packet delay budget information for SL communication. For example, see Figure 6 When the first UE 602 sends or receives configuration information for SL communication with one or more UEs 606 at 610, the configuration information may include one or more of the following: configuration grant resource allocation for SL communication (608), power control information for SL communication (608), beam information for SL communication (608), MCS for SL communication (608), data priority indication for SL communication (608), or PDB information for SL communication (608).

[0124] At 804, the first UE may establish a radio resource control (RRC) connection with a second UE communicating with the network over an access link. In one configuration, the second UE may be one of the one or more UEs. For example, see Figure 6 , the first UE 602 may establish an RRC connection with a second UE 616 communicating with the network over an access link. In one configuration, the second UE 616 may be one of the one or more UEs 606.

[0125] At 806, the first UE may send configuration information for SL communication to the second UE in a SL message. Figure 6 , at 618, the first UE 602 may send configuration information for SL communication (608) to the second UE 616 in a SL message.

[0126] At 808, the first UE may receive resource information for uplink communication of the second UE from the second UE or the network entity. Figure 6 At 620, the first UE 602 may receive resource information for uplink communication of the second UE 616 from the second UE 616. In one configuration, the first UE 602 may receive resource information for uplink communication of the second UE 616 from a network entity (base station 604).

[0127] At 810, the first UE may adjust SL communication with a third UE based on resource information for uplink communication of the second UE. In one configuration, the third UE may be one of the one or more UEs. For example, see Figure 6 At 622, the first UE 602 may adjust SL communication with the third UE based on the resource information for uplink communication of the second UE 616 received at 620. In one configuration, the third UE may be one of the one or more UEs 606.

[0128] In some aspects, the first UE may adjust the sidelink communication with the third UE by adjusting one or more of the following: the transmit power of the SL communication, the MCS of the SL communication, or the beam direction used for the SL communication. For example, see Figure 6 , when the first UE 602 adjusts the SL communication with the third UE at 622, the first UE 602 may adjust one or more of the following: the transmit power of the SL communication with the third UE, the MCS of the SL communication with the third UE, or the beam direction used for the SL communication with the third UE.

[0129] At 820, the first UE may adjust uplink communications with the network entity based on the configuration information for SL communications of one or more UEs. Figure 6 At 624 , the first UE 602 may adjust uplink communication ( 612 ) with the network entity (base station 604 ) based on the configuration information of the SL communication ( 608 ) of one or more UEs 606 received at 610 .

[0130] In some aspects, the first UE may adjust uplink communication with a network entity by adjusting one or more of the following: resources used for the uplink communication, transmit power of the uplink communication, MCS of the uplink communication, transmit analog beam of the uplink communication, TPMI of the uplink communication, rank of the uplink communication, or beam direction used for the uplink communication. For example, see Figure 6 , when the first UE 602 adjusts the uplink communication with the network entity (base station 604) at 624, the first UE 602 may adjust one or more of the following: resources used for uplink communication (612), transmit power of uplink communication (612), MCS of uplink communication (612), transmit simulation beam of uplink communication (612), TPMI of uplink communication (612), rank of uplink communication (612), or beam direction used for uplink communication (612).

[0131] At 818, the first UE may receive an indication from the network entity to adjust uplink communications based on the configuration information for SL communications. Figure 6 Before adjusting the uplink communication at 624, the first UE 602 may receive an indication from a network entity (base station 604) to adjust the uplink communication based on the configuration information for the SL communication (608).

[0132] In some aspects, the first UE may adjust uplink communications to reduce interference to SL reception at one or more UEs. For example, see Figure 6 , the first UE 602 may adjust uplink communication (612) to reduce interference to SL reception at one or more UEs 606.

[0133] In some aspects, when the first UE adjusts uplink communication with the network entity, the adjustment may be done based on one or more of the following: an uplink packet priority at the first UE, a SL packet priority for SL communication, a first PDB of an uplink packet at the first UE, a quality of service (QoS) of an uplink packet at the first UE, a second PDB of an SL packet for SL communication, a QoS of an SL packet for SL communication, or one or more transmission parameters for SL communication. The uplink packet priority may be based on a layer 1 priority of an uplink packet, a layer 2 priority of an uplink packet, or a combination of a layer 1 priority and a layer 2 priority of an uplink packet. The SL packet priority may be based on a layer 1 priority of an SL packet, a layer 2 priority of an SL packet, or a combination of a layer 1 priority and a layer 2 priority of an SL packet. The layer 1 priority of an uplink (or SL) packet may refer to the priority at which an uplink (or SL) packet is sent among other packets in layer 1 of wireless communication. The layer 2 priority of an uplink (or SL) packet may refer to the priority at which an uplink (or SL) packet is sent among other packets in layer 2 of wireless communication. For example, see Figure 6 , when the first UE 602 adjusts the uplink communication (612) with the network entity (base station 604) at 624, the adjustment can be done based on one or more of the following: uplink packet priority at the first UE 602, SL packet priority for SL communication (608), a first PDB of the uplink packet at the first UE 602, quality of service (QoS) of the uplink packet at the first UE 602, a second PDB of the SL packet for SL communication (608), QoS of the SL packet for SL communication (608), or one or more transmission parameters for SL communication (608).

[0134] At 822, the first UE may receive a first beam limitation from a network node or a second UE, or send a second beam limitation for SL communication to one or more UEs. In some aspects, the beam limitation may be based on an overlap between uplink resources and SL resources in at least one of time or frequency.

[0135] For example, see Figure 6 At 630, the first UE 602 may receive a first beam restriction from a network node (base station 604). In one configuration, the first UE 602 may receive the first beam restriction from a second UE 616. At 632, the first UE 602 may send a second beam restriction for SL communication (608) to one or more UEs 606. The beam restriction (i.e., the first beam restriction or the second beam restriction) may be based on an overlap in at least one of time or frequency between uplink resources used for uplink communication (612) and SL resources used for SL communication (608).

[0136] At 824, the first UE may receive a power offset for non-orthogonal multiple access (NOMA) on the SL from the network node to reduce interference at the network node. For example, see Figure 6 , at 630, the first UE 602 may receive a power offset for NOMA on the SL from the network node (base station 604) to reduce interference at the network node (base station 604).

[0137] At 814, the path loss constraint may be relaxed based on at least one of: energy harvesting operation of the first UE, or sending configuration information for SL communication to the network node. Figure 6 , at 634, the first UE 602 may relax the path loss constraint based on at least one of: energy harvesting operations of the first UE 602, or sending configuration information for SL communication to the network node (base station 604).

[0138] At 816, a switch between path loss constraints may be performed in response to the occurrence of an event. Figure 6 At 634, the first UE 602 may switch between path loss constraints in response to the occurrence of the event.

[0139] Fig. 9 900 is a flowchart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 504, 604, 1306, 1354, 1406, 1454; device 310; or Fig.11 The method enables adjusting SL communication between UEs based on information of access links. Therefore, the method improves the reliability of wireless communication (especially for XR-related applications) and facilitates power transmission of energy-harvesting UEs.

[0140] like Fig. 9 As shown, at 902, the network entity may receive configuration information for SL communication of the first UE. The first UE may be UE 104, 502, 503, 602; device 350; or Fig.11 Device 1104 in a hardware specific implementation. Figure 6 Various aspects of the steps associated with flowchart 900 are illustrated. For example, see Figure 6 , at 626 , the network entity (base station 604 ) may receive configuration information for SL communication ( 608 ) for the first UE 602 .

[0141] At 904, the network entity may provide configuration information for SL communication of the first UE to a second UE with which the network entity communicates via an access link. Figure 6 , the network entity (base station 604) may provide the second UE 616 with the configuration information for SL communication of the first UE 602 received at 626. The network entity (base station 604) may communicate with the second UE 616 via an access link. Fig. 13B An example is illustrated in which base station 1354 sends configuration information for sidelink communications to UE 1352. Fig. 14B An example is illustrated in which base station 1454 sends configuration information for Uu communication of UE 1452 to UE 1456.

[0142] Fig.10 1000 is a flowchart illustrating a method of wireless communication at a network entity according to various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 504, 604, 1306, 1354, 1406, 1454; device 310; or Fig.11 The method enables adjusting SL communication between UEs based on information of access links. Therefore, the method improves the reliability of wireless communication (especially for XR-related applications) and facilitates power transmission of energy-harvesting UEs.

[0143] like Fig.10 As shown, at 1002, the network entity may receive configuration information for SL communication of a first UE. The first UE may be UE 104, 502, 503, 602; device 350; or Fig.11 Device 1104 in a hardware specific implementation. Figure 6 Various aspects of the steps associated with flowchart 1000 are illustrated. For example, see Figure 6, at 626 , the network entity (base station 604 ) may receive configuration information for SL communication ( 608 ) for the first UE 602 .

[0144] At 1004, the network entity may provide configuration information for SL communication of the first UE to a second UE with which the network entity communicates via an access link. Figure 6 , the network entity (base station 604) may provide the second UE 616 with the configuration information for SL communication of the first UE 602 received at 626. The network entity (base station 604) may communicate with the second UE 616 via an access link. Fig. 13B An example is illustrated in which base station 1354 sends configuration information for sidelink communications to UE 1352. Fig. 14B An example is illustrated in which base station 1454 sends configuration information for Uu communication of UE 1452 to UE 1456.

[0145] In some aspects, the configuration information for sidelink communication may include one or more of: configuration grant resource allocation for SL communication, power control information for SL communication, beam information for SL communication, MCS for SL communication, data priority indication for SL communication, or PDB information for SL communication. For example, see Figure 6 , when the network entity (base station 604) receives configuration information for SL communication (608) at 626, the configuration information may include one or more of the following: configuration grant resource allocation for SL communication (608), power control information for SL communication (608), beam information for SL communication (608), MCS for SL communication (608), data priority indication for SL communication (608), or PDB information for SL communication (608).

[0146] At 1006, the network entity may adjust the uplink communication based on the configuration information for the SL communication. The network entity may adjust the uplink communication by adjusting one or more of the following: resources for uplink communication of the second UE, transmit power of the uplink communication, MCS of the uplink communication, transmit analog beam of the uplink communication, TPMI of the uplink communication, rank of the uplink communication, or beam direction for the uplink communication. For example, see Figure 6, the network entity (base station 604) may adjust the uplink communication (612) based on the configuration information for the SL communication (608) received at 626. The network entity (base station 604) may adjust the uplink communication (612) by adjusting one or more of the following: resources for the uplink communication (612) for the second UE 616, transmit power for the uplink communication (612), MCS for the uplink communication (612), transmit analog beam for the uplink communication (612), TPMI for the uplink communication, rank for the uplink communication (612), or beam direction for the uplink communication (612).

[0147] In some aspects, the network entity may adjust communications with the second UE to reduce interference with SL reception at the first UE or with access link communications with the second UE. Figure 6 , the network entity (base station 604) may adjust communications with the second UE 616 to reduce interference to SL reception at the first UE 602 or to access link communications with the second UE 616.

[0148] At 1008, the network entity may send a beam restriction for SL communication to the first UE. In some aspects, the beam restriction is based on an overlap between the uplink resources and the SL resources in at least one of time or frequency. For example, see Figure 6 At 630, the network entity (base station 604) may send a beam limitation (i.e., a first beam limitation) for SL communication (608) to the first UE 602. In some aspects, the beam limitation (i.e., the first beam limitation) may be based on an overlap in at least one of time or frequency between uplink resources used for uplink communication (612) and SL resources used for SL communication (608).

[0149] At 1010, the network entity may provide a power offset for NOMA for SL communication to the first UE to reduce interference at the network node. The power offset for NOMA for SL communication may be based on the number of UEs assigned using NOMA. For example, see Figure 6 , the network entity (base station 604) may provide a power offset for NOMA for SL communication (608) to the first UE 602 to reduce interference at the network node (base station 604). The power offset for NOMA for SL communication (608) may be based on the number of UEs assigned using NOMA.

[0150] At 1014, the path loss constraint may be relaxed based on at least one of: energy harvesting operation of the first UE, or receiving configuration information for SL communication from the first UE. Figure 6At 634 , the first UE 602 may relax the path loss constraint based on at least one of: energy harvesting operations of the first UE 602 , or receiving configuration information for SL communication ( 608 ) from the first UE 602 .

[0151] At 1012, the network entity may instruct the first UE to switch between path loss constraints in response to the occurrence of the event. Figure 6 , the network entity (base station 604) may instruct the first UE 602 to switch between path loss constraints in response to the occurrence of the event at 634.

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

[0153] As discussed above, component 198 is configured to communicate with one or more UEs via SL. Component 198 is also configured to send or receive configuration information for SL communication with the one or more UEs or uplink communication with a network entity. Component 198 may also be configured to perform a combined Figure 7 , Figure 8 Any of the aspects described in the flowcharts and / or by Figure 6 Any of the aspects performed by the UE 602 in . Component 198 may be within the cellular baseband processor 1124, within the application processor 1106, or within both the cellular baseband processor 1124 and the application processor 1106. Component 198 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1104 may include a variety of components configured for various functions. In one configuration, the device 1104 (and specifically the cellular baseband processor 1124 and / or the application processor 1106) includes a component for communicating with one or more UEs via SL. The device 1104 may also include a component for sending or receiving configuration information for SL communication with the one or more UEs or uplink communication with a network entity. The device 1104 may also include a component for performing a combined Figure 7 and Figure 8 Any of the aspects described in the flowcharts and / or by Figure 6 104. The device 1104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the device 1104 may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the device 1104.

[0154] Fig.121200 is a diagram illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or a RU 1240. For example, depending on the layer functionality handled by the component 199, the network entity 1202 may include a CU 1210; both a CU 1210 and a DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both a DU 1230 and a RU 1240; or the RU 1240. The CU 1210 may include a CU processor 1212. The CU processor 1212 may include an on-chip memory 1212'. In some aspects, the CU 1210 may also include an additional memory module 1214 and a communication interface 1218. CU 1210 communicates with DU 1230 via a midhaul link, such as an F1 interface. DU 1230 may include a DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include an additional memory module 1234 and a communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include a RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include an additional memory module 1244, one or more transceivers 1246, an antenna 1280, and a communication interface 1248. RU 1240 communicates with UE 104. On-chip memory 1212', 1232', 1242' and additional memory modules 1214, 1234, 1244 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1212, 1232, 1242 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0155] As discussed above, component 199 is configured to receive configuration information for SL communication of a first UE. Component 199 may also be configured to provide configuration information for SL communication of the first UE to a second UE with which the network entity communicates via an access link. Component 199 may also be configured to perform a combined Fig. 9 and Fig.10 Any of the aspects described in the flowcharts and / or by Figure 6Any of the aspects performed by the base station 604 in the UE. Component 199 may be within one or more processors of one or more of the CU 1210, the DU 1230, and the RU 1240. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1202 may include a variety of components configured for various functions. In one configuration, the network entity 1202 includes a component for receiving configuration information for SL communication of the first UE. The network entity 1202 may also include a component for performing a combined Fig. 9 and Fig.10 Any of the aspects described in the flowcharts and / or by Figure 6 Components of any of the aspects performed by the base station 604 in the network entity 1202. The network entity 1202 may also include a component for providing configuration information for SL communication of the first UE to a second UE with which the network entity communicates via an access link. The component may be a component 199 of the network entity 1202 configured to perform the functions recited by the component. As described above, the network entity 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the component.

[0156] The present disclosure provides a method for wireless communication at a first UE. The method may include communicating with one or more UEs via SL; and sending or receiving configuration information for SL communication with the one or more UEs or uplink communication with a network entity. The method enables SL communication between UEs to be adjusted based on information of the access link. Therefore, the method improves the reliability of wireless communication (especially for XR-related applications) and facilitates power transmission of energy-harvesting UEs.

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

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

[0159] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0161] Aspect 1 is a method for wireless communication at a first UE. The method includes: communicating with one or more UEs via a SL; and sending or receiving configuration information for SL communication with the one or more UEs or uplink communication with a network entity.

[0162] Aspect 2 is a method according to Aspect 1, wherein the configuration information includes one or more of the following: configuration grant resource allocation for the SL communication, power control information for the SL communication, beam information for the SL communication, MCS for the SL communication, data priority indication for the SL communication, or packet delay budget information for the SL communication.

[0163] Aspect 3 is a method according to any one of Aspects 1 and 2, wherein the method further includes: establishing an RRC connection with a second UE communicating with the network on an access link, and sending the configuration information for the SL communication to the second UE in a SL message.

[0164] Aspect 4 is a method according to any one of Aspects 1 and 2, wherein the method further includes: establishing an RRC connection with a second UE communicating with a network on an access link, and receiving resource information for the uplink communication of the second UE from the second UE or the network entity.

[0165] Aspect 5 is a method according to aspect 4, wherein the method further comprises: adjusting the SL communication with a third UE based on the resource information used for the uplink communication of the second UE.

[0166] Aspect 6 is a method according to Aspect 5, wherein adjusting the SL communication with the third UE includes: adjusting one or more of the following: the transmission power of the SL communication, the modulation and decoding scheme of the SL communication, or the beam direction used for the SL communication.

[0167] Aspect 7 is a method according to any one of Aspects 1 to 6, wherein the method further includes: communicating with the network entity on an access link, receiving the configuration information for the SL communication of the one or more UEs; and adjusting the uplink communication with the network entity based on the configuration information for the SL communication of the one or more UEs.

[0168] Aspect 8 is a method according to Aspect 7, wherein adjusting the uplink communication with the network entity includes: adjusting one or more of the following: resources used for the uplink communication, transmit power of the uplink communication, MCS of the uplink communication, transmit simulation beam of the uplink communication, TPMI of the uplink communication, rank of the uplink communication, or beam direction used for the uplink communication.

[0169] Aspect 9 is a method according to aspect 8, wherein the method further comprises: receiving, from the network entity, an indication to adjust the uplink communication based on the configuration information for the SL communication.

[0170] Aspect 10 is a method according to aspect 8, wherein the method further comprises: adjusting the uplink communication to reduce interference with SL reception at the one or more UEs.

[0171] Aspect 11 is a method according to Aspect 7, wherein the method includes: adjusting the uplink communication with the network entity also based on at least one of the following: an uplink packet priority at the first UE, wherein the uplink packet priority is based on the layer 1 priority of the uplink packet, the layer 2 priority of the uplink packet, or a combination of the layer 1 priority and the layer 2 priority of the uplink packet; an SL packet priority for the SL communication, wherein the SL packet priority is based on the layer 1 priority of the SL packet, the layer 2 priority of the SL packet, or a combination of the layer 1 priority and the layer 2 priority of the SL packet; a first PDB of the uplink packet at the first UE; a QoS of the uplink packet at the first UE; a second PDB of the SL packet for the SL communication; a QoS of the SL packet for the SL communication; or one or more transmission parameters for the SL communication.

[0172] Aspect 12 is a method according to any one of Aspects 1 to 11, wherein the method further includes: receiving a first beam limitation from the network entity or a second UE, or sending a second beam limitation for the SL communication to the one or more UEs.

[0173] Aspect 13 is a method according to aspect 12, wherein the beam limitation is based on an overlap between uplink resources and SL resources in at least one of time or frequency.

[0174] Aspect 14 is a method according to any one of Aspects 1 to 13, wherein the method further comprises: receiving a power offset for NOMA on the SL from the network entity to reduce interference at the network entity.

[0175] Aspect 15 is a method according to any one of Aspects 1 to 14, wherein the method further includes: relaxing the path loss constraint based on at least one of: energy harvesting operation of the first UE, or sending the configuration information for the SL communication to the network entity.

[0176] Aspect 16 is a method according to aspect 15, wherein the method further comprises: switching between path loss constraints in response to occurrence of an event.

[0177] Aspect 17 is an apparatus for performing wireless communications at a first UE, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured to perform a method according to any one of Aspects 1 to 16 based at least in part on information stored in the memory.

[0178] Aspect 18 is an apparatus according to aspect 17, the apparatus further comprising at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and configured to send or receive the configuration information.

[0179] Aspect 19 is an apparatus for wireless communication, the apparatus comprising means for implementing the method according to any one of aspects 1 to 16.

[0180] Aspect 20 is a computer-readable medium (eg, a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the method according to any one of aspects 1 to 16.

[0181] Aspect 21 is a method for wireless communication at a network entity. The method includes: receiving configuration information for SL communication of a first user equipment (UE); and providing the configuration information for the SL communication of the first UE to a second UE with which the network entity communicates via an access link.

[0182] Aspect 22 is a method according to Aspect 21, wherein the configuration information includes one or more of the following: configuration grant resource allocation for the SL communication, power control information for the SL communication, beam information for the SL communication, MCS for the SL communication, data priority indication for the SL communication, or packet delay budget information for the SL communication.

[0183] Aspect 23 is a method according to any one of Aspects 21 to 22, wherein the method further includes: adjusting one or more of the following based on the configuration information used for the SL communication: resources for uplink communication of the second UE, transmit power of the uplink communication, MCS of the uplink communication, transmit simulation beam of the uplink communication, TPMI of the uplink communication, rank of the uplink communication, or beam direction used for the uplink communication.

[0184] Aspect 24 is a method according to aspect 23, wherein the method further comprises: adjusting communication with the second UE to reduce interference with SL reception at the first UE or interference with access link communication with the second UE.

[0185] Aspect 25 is a method according to any one of Aspects 21 to 24, wherein the method further comprises: sending a beam limitation for the SL communication to the first UE.

[0186] Aspect 26 is a method according to aspect 25, wherein the beam limitation is based on an overlap between uplink resources and SL resources in at least one of time or frequency.

[0187] Aspect 27 is a method according to any one of Aspects 21 to 26, wherein the method further includes: providing a power offset to the first UE for NOMA used for the SL communication to reduce interference at the network entity.

[0188] Aspect 28 is a method according to Aspect 27, wherein the power offset for the NOMA used for the SL communication is based on the number of UEs allocated using NOMA.

[0189] Aspect 29 is a method according to any one of Aspects 21 to 28, wherein the method further includes: relaxing the path loss constraint based on at least one of: energy harvesting operation of the first UE, or receiving the configuration information for the SL communication from the first UE.

[0190] Aspect 30 is a method according to aspect 29, wherein the method further comprises: instructing the first UE to switch between path loss constraints in response to the occurrence of an event.

[0191] Aspect 31 is an apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured to perform a method according to any one of Aspects 21 to 30 based at least in part on information stored in the memory.

[0192] Aspect 32 is an apparatus according to aspect 30, the apparatus further comprising at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and configured to receive the configuration information.

[0193] Aspect 33 is an apparatus for wireless communication, the apparatus comprising means for implementing a method according to any one of aspects 21 to 30.

[0194] Aspect 34 is a computer-readable medium (eg, a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the method according to any one of aspects 21 to 30.

Claims

1. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the stored information stored in the memory, the at least one processor is configured to: communicating with one or more UEs via a SL (SL); and Send or receive configuration information for SL communication with the one or more UEs or uplink communication with a network entity.

2. The apparatus of claim 1 , wherein the configuration information comprises one or more of: configuring grant resource allocation for said SL communication, power control information for said SL communication, beam information for said SL communication, a modulation and coding scheme (MCS) for said SL communication, an indication of the data priority for said SL communication, or Packet delay budget information for the SL communication.

3. The apparatus of claim 1 , wherein the at least one processor is configured to: A radio resource control (RRC) connection is established with a second UE communicating with a network over an access link, wherein the at least one processor is configured to send the configuration information for the SL communication to the second UE in a SL message.

4. The apparatus of claim 1 , wherein the at least one processor is configured to: A radio resource control (RRC) connection is established with a second UE communicating with a network over an access link, wherein the at least one processor is configured to receive resource information for the uplink communication of the second UE from the second UE or the network entity.

5. The apparatus of claim 4, wherein the at least one processor is further configured to: The SL communication with a third UE is adjusted based on the resource information used for the uplink communication of the second UE.

6. The apparatus of claim 5, wherein to adjust the SL communication with the third UE, the at least one processor is configured to adjust one or more of: the transmission power of the SL communication, the modulation and coding scheme of the SL communication, or The beam direction used for the SL communication.

7. The apparatus of claim 1 , wherein the at least one processor is further configured to: communicating with the network entity over an access link, wherein the at least one processor is configured to receive the configuration information for the SL communication of the one or more UEs; and The uplink communication with the network entity is adjusted based on the configuration information of the SL communication of the one or more UEs.

8. The apparatus of claim 7, wherein to adjust the uplink communication with the network entity, the at least one processor is configured to adjust one or more of: resources for said uplink communication, the transmit power of the uplink communication, the modulation and coding scheme (MCS) of the uplink communication, the uplink communication transmits a simulated beam, a transmit precoding matrix indicator (TPMI) for the uplink communication, a rank for the uplink communication, or A beam direction to be used for said uplink communication.

9. The apparatus of claim 8, wherein the at least one processor is further configured to: An indication is received from the network entity to adjust the uplink communication based on the configuration information for the SL communication.

10. The apparatus of claim 8, wherein the at least one processor is configured to adjust the uplink communication to reduce interference to SL reception at the one or more UEs.

11. The apparatus of claim 7, wherein the at least one processor is configured to adjust the uplink communication with the network entity further based on at least one of: an uplink packet priority at the first UE, wherein the uplink packet priority is based on a layer 1 priority of the uplink packet, a layer 2 priority of the uplink packet, or a combination of the layer 1 priority and the layer 2 priority of the uplink packet; a SL packet priority for the SL communication, wherein the SL packet priority is based on a layer 1 priority of the SL packet, a layer 2 priority of the SL packet, or a combination of the layer 1 priority and the layer 2 priority of the SL packet; a first packet delay budget (PDB) for the uplink packet at the first UE; a quality of service (QoS) of the uplink packets at the first UE; a second PDB of the SL packet for the SL communication; a QoS of the SL packets for the SL communication; or One or more transmission parameters for the SL communication.

12. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a first beam limitation from the network entity or a second UE, or Sending a second beam limitation for the SL communication to the one or more UEs.

13. The apparatus of claim 12, wherein the beam limitation is based on an overlap between uplink resources and SL resources in at least one of time or frequency.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: A power offset for non-orthogonal multiple access (NOMA) on the SL is received from the network entity to reduce interference at the network entity.

15. The apparatus of claim 1, wherein the at least one processor is further configured to: Relax the path loss constraint based on at least one of the following: the energy harvesting operation of the first UE, or The configuration information for the SL communication is sent to the network entity.

16. The apparatus of claim 15, wherein the at least one processor is further configured to: Switching between path loss constraints is performed in response to the occurrence of an event.

17. The apparatus according to claim 1, further comprising: At least one transceiver is coupled to the at least one processor, and the at least one processor is configured to send or receive the configuration information via the at least one transceiver.

18. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the stored information stored in the memory, the at least one processor is configured to: receiving configuration information for sidelink (SL) communications of a first user equipment (UE); and The configuration information for the SL communication of the first UE is provided to a second UE with which the network entity communicates via an access link.

19. The apparatus of claim 18, wherein the configuration information comprises one or more of: configuring grant resource allocation for said SL communication, power control information for said SL communication, beam information for said SL communication, a modulation and coding scheme (MCS) for said SL communication, an indication of the data priority for said SL communication, or Packet delay budget information for the SL communication.

20. The apparatus of claim 18, wherein the at least one processor is configured to adjust one or more of the following based on the configuration information for the SL communication: resources for uplink communication of the second UE, the transmit power of the uplink communication, the modulation and coding scheme (MCS) of the uplink communication, the uplink communication transmits a simulated beam, a transmit precoding matrix indicator (TPMI) for the uplink communication, the rank of the uplink communication, or A beam direction to be used for said uplink communication.

21. The apparatus of claim 20, wherein the at least one processor is configured to adjust communications with the second UE to reduce interference with SL reception at the first UE or interference with access link communications with the second UE.

22. The apparatus of claim 18, wherein the at least one processor is further configured to: Sending beam limitations for the SL communication to the first UE.

23. The apparatus of claim 22, wherein the beam limitation is based on an overlap between uplink resources and SL resources in at least one of time or frequency.

24. The apparatus of claim 18, wherein the at least one processor is further configured to: A power offset is provided to the first UE for non-orthogonal multiple access (NOMA) used for the SL communication to reduce interference at the network entity.

25. An apparatus according to claim 24, wherein the power offset for the NOMA used for the SL communication is based on the number of UEs allocated using NOMA.

26. The apparatus of claim 18, wherein the at least one processor is further configured to: Relax the path loss constraint based on at least one of the following: the energy harvesting operation of the first UE, or The configuration information for the SL communication is received from the first UE.

27. The apparatus of claim 26, wherein the at least one processor is further configured to: The first UE is instructed to switch between path loss constraints in response to the occurrence of an event.

28. The apparatus according to claim 18, further comprising: At least one transceiver is coupled to the at least one processor, and the at least one processor is configured to receive the configuration information via the at least one transceiver.

29. A method of wireless communication at a first user equipment (UE), the method comprising: Communicate with one or more UEs via the SL; as well as Send or receive configuration information for SL communication with the one or more UEs or uplink communication with a network entity.

30. A method for wireless communication at a network entity, the method comprising: receiving configuration information for SL communication of a first user equipment (UE); as well as The configuration information for the SL communication of the first UE is provided to a second UE with which the network entity communicates via an access link.

Images