Centralized beam determination for full duplex communication

Abstract

Certain aspects of the present disclosure provide techniques for centralized beam determination for full duplex (FD) communications. An example method performed by a wireless node includes obtaining at least one report indicating information about a candidate beam; selecting a pair of beams from the candidate beams based on the information; and outputting, for transmission, signaling indicating that at least one user equipment (UE) is to use the pair of beams for full duplex (FD) wireless communication over the first link and the second link.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Patent Application No. 18 / 193,514, filed March 30, 2023, which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety, as fully set forth below and for all applicable purposes. Background Technology Technical Field

[0003] Various aspects of this disclosure relate to wireless communication, and more specifically to techniques for determining beams for full-duplex (FD) communication.

[0004] Related technical descriptions

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available wireless communication system resources.

[0006] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0007] One aspect provides a method for wireless communication at a wireless node. The method includes: obtaining at least one report indicating information about candidate beams; selecting a pair of beams from the candidate beams based on the information; and outputting signaling instructing at least one user equipment (UE) to use the pair of beams for full-duplex (FD) wireless communication on a first link and a second link for transmission.

[0008] On the other hand, a method for wireless communication at a wireless node is provided. The method includes: obtaining signaling instructing a wireless device to use a pair of beams for FD wireless communication on a first link and a second link; and using the pair of beams to perform communication according to the signaling.

[0009] Other aspects provide: an apparatus capable of operating to, being configured to, or otherwise adapted to perform any or more of the foregoing methods and / or those methods described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising: code for performing the foregoing methods and those methods described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those methods described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0010] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0011] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example decomposed base station architecture is described.

[0014] Figure 3 Various aspects of the example base station and example user equipment are described.

[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0016] Figure 5 An example scenario involving full-duplex (FD) vehicle-to-everything (V2X) communication is depicted.

[0017] Figure 6 An example scenario involving the forward relay direction is depicted (Scenario 1).

[0018] Figure 7 An example scenario involving the reverse relay direction is depicted (Scenario 2).

[0019] Figures 8 to 10 An example of scenario 1, which is described according to certain aspects of this disclosure, is provided.

[0020] Figures 11 to 14 A timing diagram illustrating an example of scenario 1 according to certain aspects of this disclosure is depicted.

[0021] Figure 15 An example of scenario 1, which is described according to certain aspects of this disclosure, is provided.

[0022] Figure 16 A timing diagram illustrating an example of scenario 1 according to certain aspects of this disclosure is depicted.

[0023] Figure 17 A timing diagram illustrating an example of scenario 1 according to certain aspects of this disclosure is depicted.

[0024] Figure 18 An example of scenario 2 is depicted according to certain aspects of this disclosure.

[0025] Figure 19 An example of scenario 2 is depicted according to certain aspects of this disclosure.

[0026] Figure 20 A timing diagram illustrating an example of scenario 2 according to certain aspects of this disclosure is provided.

[0027] Figure 21 A timing diagram illustrating an example of scenario 2 according to certain aspects of this disclosure is provided.

[0028] Figure 22 An example of scenario 2 is depicted according to certain aspects of this disclosure.

[0029] Figures 23 to 26 A timing diagram illustrating an example of scenario 2 according to certain aspects of this disclosure is provided.

[0030] Figure 27 An example of scenario 2 is depicted according to certain aspects of this disclosure.

[0031] Figure 28 A timing diagram illustrating an example of scenario 2 according to certain aspects of this disclosure is provided.

[0032] Figure 29 A timing diagram illustrating an example of scenario 2 according to certain aspects of this disclosure is provided.

[0033] Figure 30 An example of bidirectional full-duplex (FD) communication according to certain aspects of this disclosure is depicted, wherein both side-link (SL) UEs are within the coverage (IC) range of the network.

[0034] Figure 31 An example of bidirectional FD communication according to certain aspects of this disclosure is depicted, wherein at least one SL UE is outside the coverage area of ​​the network (OOC).

[0035] Figures 32 to 33 An example of bidirectional FD communication according to certain aspects of this disclosure is depicted.

[0036] Figures 34 to 35 Timing diagrams illustrating examples of bidirectional FD communication according to certain aspects of this disclosure are depicted.

[0037] Figure 36 Timing diagrams illustrating FD beam configurations according to certain aspects of this disclosure are depicted.

[0038] Figure 37 A method for wireless communication is described.

[0039] Figure 38 A method for wireless communication is described.

[0040] Figure 39 Various aspects of the example communication device are described. Detailed Implementation

[0041] This disclosure provides apparatus, methods, processing systems, and computer-readable media for determining beams for full-duplex (FD) communication. The techniques presented herein provide centralized FD beam management at a wireless node. As used herein, the term wireless node generally refers to any type of device capable of wireless communication, such as a UE or a network entity, such as a base station (e.g., a gNB). The terms wireless node and wireless device are used interchangeably.

[0042] Full-duplex (FD) communication refers to the ability of devices to send and receive data simultaneously. This means, for example, that two FD devices can communicate with each other in real time without any interruption or delay caused by the need to switch between send and receive modes. Compared to half-duplex (HD) communication, where devices take turns sending and receiving data, full-duplex communication allows for more efficient use of available bandwidth and faster data transfer rates. It also enables more seamless and reliable real-time applications such as voice and video communication.

[0043] Sidelink (SL) communication specifically refers to direct communication between two devices, without the need for an intermediate base station or access point. This type of communication is typically used in peer-to-peer scenarios, such as device-to-device communication, or vehicle-to-vehicle (V2V) or vehicle-to-everything (V2X) communication for autonomous driving applications.

[0044] Beamforming generally refers to a technique used to improve the signal-to-noise ratio (SNR) of a received signal by focusing a transmitted signal to a specific location using a directional beam. Beamforming for FD SL communication presents potential problems. For example, FD SL communication can lead to self-interference (SI) and / or cross-link interference (CLI), negatively impacting the accuracy of beamforming. Additionally, the beamforming process can be complex, requiring significant computational resources, which may result in delayed or erroneous beamforming.

[0045] Various aspects of this disclosure provide techniques for beam determination in FD communications included in SL. For example, the techniques disclosed herein can allow a centralized node (e.g., a network entity, gNB, operation, management and maintenance (OAM) entity, or UE) to initiate / coordinate beam measurements and / or reporting to identify FD beams and to signal the identified FD beams to one or more FD nodes. For example, a network entity can coordinate beam measurements and reporting from two FD UEs (e.g., SL FD UEs), determine FD beams, and signal the determined FD beams to both FD UEs for transmitting and receiving signals (e.g., SLFD communication).

[0046] These techniques can be applied to scenarios involving FD SL UE relay (e.g., relaying signals between a network entity and a remote UE in the forward or reverse direction) or scenarios involving bidirectional FD communication between two side-link UEs. Centralized beamforming in such scenarios can prevent / reduce SI and / or CLI, thereby improving beamforming and user quality of experience (QoE).

[0047] An introduction to wireless communication networks

[0048] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0049] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0050] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of a BS, servers, etc.). For example, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Furthermore, wireless communication network 100 includes terrestrial aspects, such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0051] In the depicted example, wireless communication network 100 includes BS 102, UE 104, and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0052] Figure 1 Various example UE 104s are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, handheld devices, etc.

[0053] BS102 communicates wirelessly with UE 104 via communication link 120 (e.g., transmitting or receiving signals to or from UE 104). Communication link 120 between BS102 and UE 104 may include uplink (UL) transmission (also referred to as reverse link) from UE 104 to BS102 and / or downlink (DL) transmission (also referred to as forward link) transmission from BS102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity.

[0054] BS102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each of BS102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0055] Although the BS102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near-real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., the BS102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0056] Different BS102s within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., the S1 interface). A BS102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BS102s can communicate directly or indirectly with each other (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., the X2 interface), which can be wired or wireless.

[0057] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, frequency modulation, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz-7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz-52,600MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0058] The communication link 120 between BS102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0059] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1The beamforming 180 of BS 180 and UE 104 can be used with UE 104 to improve path loss and range. For example, BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182'. UE 104 may also transmit beamformed signals to BS 180 in one or more transmit directions 182'. BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of BS 180 and UE 104. It is worth noting that the transmit and receive directions of BS 180 may be the same or different. Similarly, the transmission and reception directions of UE 104 may or may not be the same.

[0060] The wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0061] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0062] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0063] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP service 176, which may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming service, and / or other IP services.

[0064] The BM-SC 170 provides functions for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to BS102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0065] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196.

[0066] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0067] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0068] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0069] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units (such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both). CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0070] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more other units via a transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other units, or both.

[0071] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions managed by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface (such as an E1 interface). CU 210 can be implemented to communicate with DU 230 for network control and signaling as needed.

[0072] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may host one or more of the Radio Link Control (RLC) layer, 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 functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0073] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, the RU240 controlled by the DU 230 may correspond to a logical node that at least partially 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.) based on functional decomposition such as lower-layer functional decomposition, or both. In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration enables the DU 230 and CU210 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0074] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0075] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225 (e.g., via an A1 interface). The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface (e.g., via an E2 interface) through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0076] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0077] Figure 3 Various aspects of examples BS102 and UE 104 are described.

[0078] Generally, BS102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively referred to as 334), transceivers 332a-332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS102 can transmit and receive data between BS102 and UE 104. BS102 includes a controller / processor 340 that can be configured to implement the various functions described herein related to wireless communication.

[0079] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively referred to as 352), transceivers 354a-354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieved from data source 362) and the wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various functions described herein related to wireless communication.

[0080] Regarding example downlink transmission, BS102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may be for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical HARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Shared PDCCH (GC PDCCH), and / or others. In some examples, the data may be for the Physical Downlink Shared Channel (PDSCH).

[0081] The transmitter processor 320 can process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0082] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t can process its corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a-332t can be transmitted via antennas 334a-334t respectively.

[0083] To receive downlink transmissions, UE 104 includes antennas 352a-352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a-354r respectively. Each demodulator in transceivers 354a-354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0084] The MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes (e.g., demodulates, deinterleaves, and decodes) the detected symbols, provides the decoded data for UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0085] Regarding example uplink transmission, UE 104 also includes a transmit processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmit processor 364 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmit processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0086] At BS102, uplink signals from UE 104 can be received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 where applicable, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0087] Memory 342 and memory 382 can store data and program code for BS102 and UE 104, respectively.

[0088] Scheduler 344 can schedule UE to transmit data on the downlink and / or uplink.

[0089] In various respects, BS102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceiver 332a-332t, antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms that acquire data, such as from antenna 334a-334t, transceiver 332a-332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0090] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceiver 354a-354t, antenna 352a-352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antenna 352a-352t, transceiver 354a-354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0091] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0092] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0093] Specifically, Figure 4A Figure 400 illustrates an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0094] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth described herein is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0095] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0096] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0097] In some respects, the number of slots within a subframe is based on the slot configuration and parameter set. For example, for slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slots and 2μ slots / subframes. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2. μ ×15kHz, where μ is the parameter set from 0 to 5. Thus, parameter set μ = 0 has a subcarrier spacing of 15kHz, and parameter set μ = 5 has a subcarrier spacing of 480kHz. Symbol length / duration is negatively correlated with subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D Examples are provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67μs.

[0098] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0099] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or 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 / or a phase tracking RS (PT-RS).

[0100] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0101] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0102] The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing.

[0103] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. 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. The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0104] like Figure 4CAs illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0105] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0106] Overview of sidelink communication

[0107] User equipment (UE) communicates with each other using sidelink signals. Real-world applications of sidelink communication can include UE-to-network relay, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, Internet of Things (IoE) communication, IoT communication, mission-critical mesh networks, and / or various other suitable applications.

[0108] Sidelink signaling refers to a signal transmitted from one UE to another without relaying the communication through a scheduling entity (e.g., a UE or a network entity), even if that scheduling entity may be used for scheduling and / or control purposes. In some examples, licensed spectrum may be used to transmit sidelink signals (e.g., unlike WLANs that typically use unlicensed spectrum). An example of sidelink communication is PC5, as used in V2V, LTE, and / or New Radio (NR).

[0109] Various sidelink channels are used for sidelink communication, including the Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Feedback Channel (PSFCH). The PSDCH carries discovery expressions that enable neighboring UEs to discover each other. The PSCCH carries control signaling, such as sidelink resource configuration, resource reservation, and other parameters for data transmission. The PSSCH carries data transmission. The PSFCH carries feedback corresponding to transmissions on the PSSCH, such as acknowledgment (ACK) and / or negative ACK (NACK) information.

[0110] In some NR systems, two-stage sidelink control information (SCI) is supported. Two-stage SCI includes a first-stage SCI (e.g., SCI-1) and a second-stage SCI (e.g., SCI-2). SCI-1 includes resource reservation and allocation information. SCI-2 includes information that can be used to decode data and determine whether the UE is the intended recipient of the transmission. SCI-1 and / or SCI-2 can be transmitted on the PSCCH.

[0111] V2X generally refers to a vehicle technology system that enables vehicles to communicate with traffic and their surrounding environment using short-range radio signals known as sidelink signals. V2X systems typically offer two complementary transmission modes. The first transmission mode involves direct communication between participants that are adjacent to each other in a local area (e.g., also known as sidelink communication). The second transmission mode involves network communication over a network, which can be implemented via a Uu interface (e.g., a wireless communication interface between a radio access network (RAN) and a UE).

[0112] In the first transmission mode, vehicles have wireless communication links with individuals via the PC5 interface. Communication between vehicles can also occur via the PC5 interface. Communication from vehicles to other highway components (such as roadside units (RSUs), which can be traffic signals or signs) can occur similarly via the PC5 interface. Bidirectional communication is possible between devices with respect to each communication link, so each device can be both a transmitter and a receiver of information. The V2X system can be a self-managing system implemented without the assistance of network entities. Self-managing systems enable improved spectrum efficiency, reduced costs, and increased reliability because no network service interruption occurs during handover operations for mobile vehicles. The V2X system can be configured to operate in licensed or unlicensed spectrum, so any vehicle equipped with the system can access public frequencies and share information. Such coordinated / shared spectrum operation allows for safe and reliable operation.

[0113] In the second transmission mode, communication between vehicles can occur through network entities. Network communication can occur through discrete nodes (such as network entities) that send and receive information to and from vehicles (e.g., relaying information between vehicles). Network communication via vehicle-to-network (V2N) links can be used for long-range communication between vehicles, such as to inform of a traffic accident at a distance along a road or highway. Wireless nodes can transmit other types of communication to vehicles, such as traffic flow conditions, road hazard warnings, environmental / weather reports, and service station availability. Such data can be obtained from cloud-based shared services.

[0114] Overview of Sidelink Resource Allocation Modes

[0115] Different sidelink allocation modes can be used to allocate resources for sidelink communication, such as sidelink resource allocation mode 1 (referred to herein as mode 1) and sidelink resource allocation mode 2 (referred to herein as mode 2). For example, in mode 1 operation, a network entity, such as a base station, indicates to the sidelink UE which resources to use to communicate (e.g., receive or transmit) sidelink transmissions. In mode 2 operation, the sidelink UE identifies and selects resources for sidelink transmissions independently, for example, based on channel sensing (e.g., without the assistance of a network entity).

[0116] In Mode 1 operation, the resources available for transmission by the sidelink UE can be dynamically scheduled in downlink control information (DCI) messages (such as DCI 3_0 messages). The DCI message may include time resource assignments indicating which time slots the sidelink transmitting UE can use to transmit sidelink transmissions. The time resource assignments may indicate up to three sidelink time slots, where the first sidelink time slot may be the initial transmission, and the second and third sidelink time slots may be retransmissions. Additionally, the DCI message may also include frequency resource assignments indicating where in the spectrum the sidelink UE can transmit sidelink transmissions.

[0117] In addition to DCI messages, Sidelink Control Information (SCI) may also include time resource assignments. SCI time resource assignments can be used by a sidelink user equipment to indicate to another sidelink user equipment (e.g., a receiving sidelink user equipment) which time slot it will use for sidelink transmission.

[0118] In Mode 2 operation, as described above, the sidelink transmitter UE determines, for example, which resources it will use for sidelink transmission based on channel sensing. Once the sidelink transmitter UE has determined which resources to use, it can include this information in the time resource allocation of the SCI to indicate to the sidelink receiver UE in which time slots it is expected to receive sidelink transmissions.

[0119] In addition to time resource allocation, SCI may also include a resource reservation period. A resource reservation period can be used to configurably and periodically reserve multiple time slots. The reserved time slots can then be used for new future transmissions.

[0120] In some cases, two UEs communicating on a sidelink may not use the same sidelink mode (e.g., mode 1 or mode 2). For example, the receiving UE may not care whether the sending UE uses a different or the same mode. For sidelink modes 1 and 2, the sidelink resource pool can be pre-configured by the network.

[0121] Overview of Full-Duplex (FD) Vehicle-to-Everything (V2X) Communication

[0122] Figure 5 An example scenario 500 involving full-duplex (FD) vehicle-to-everything (V2X) communication is depicted. As illustrated, each FD vehicle (502, 504, 506) may include at least one transmit (Tx) array and at least one receive (Rx) array. Figure 5 As illustrated in the scenario, self-interference (SI) can be a significant problem. For example, as illustrated, when vehicle 502 is receiving a signal from vehicle 506, a transmission from vehicle 502 to vehicle 504 may cause SI. SI in such scenarios can reduce the reception efficiency and power of the Rx array of vehicle 502.

[0123] In some cases, spatial isolation mechanisms can be used to mitigate the impact of SI (Self-Isolation). In such cases, 80dB to 90dB of spatial isolation can be achieved in FD communication between two panels / arrays (e.g., operating at 28GHz), which can help reduce SI. In the case of vehicle-to-everything (V2X) communication, vehicles or roadside units (RSUs), such as... Figure 5 The vehicles 502, 504, and 506 illustrated herein may have sufficient space to ensure adequate spatial isolation between the transmitting panel / array and the receiving panel / array. In some cases, SI may be further reduced due to the greater beamforming gain resulting from more antenna elements per panel / array (e.g., in frequency range 2 (FR2) or other frequency ranges).

[0124] Various aspects related to centralized beam determination for FD communication

[0125] Various aspects of this disclosure provide techniques for beam determination in FD communications included in SL. For example, the techniques disclosed herein can allow a centralized node (e.g., gNB, OAM, or UE) to identify suitable FD beams and signal the identified FD beams to one or more FD nodes. For example, such a centralized node can coordinate beam measurements and reporting from two FD UEs (e.g., SL FD UEs), determine FD beams, and signal the determined FD beams to both FD UEs for transmitting and receiving signals (e.g., SL FD communication).

[0126] According to certain aspects of this disclosure, a centralized node can manage FD beams in a first scenario (Scenario 1) involving forward relay direction and a second scenario (Scenario 2) involving reverse relay direction, as well as in a bidirectional FD SL communication scenario. In these scenarios (which will be discussed in further detail below), in scenarios involving non-beamforming based communication (e.g., Frequency Range 1 (FR1)), the beam can be identified by a measured beam identifier (ID), a measured link or node ID.

[0127] Figure 6 Example scenario 600 (Scenario 1) is depicted, involving an FD SL relay UE 104 between a network entity (e.g., gNB) 102 and a remote side link (SL) UE. As described above, Scenario 1 relates to the operational direction of the FD relay UE from the network entity to the remote UE (e.g., which may be referred to as the "forward direction" of the relay). In other words, as shown, an air / radio interface (e.g., Uu) link 602 can be formed from the network entity to the relay UE, and an SL (e.g., SL mode 1) link 604 can be formed from the relay UE to the remote SL UE (e.g., which may be outside the network's coverage area (OOC) or within its coverage area (IC)). In this scenario, the relay UE can perform FD communication using Uu reception and SL transmission.

[0128] like Figure 6 As illustrated, SI can occur at the FD relay UE, and CLI can occur between the gNB and the remote SL UE. However, aspects of this disclosure provide techniques that allow the gNB to act as a centralized beam manager. For example, the gNB can determine the beams in both Uu and SL to minimize self-interference (SI) at the FD relay UE and cross-link interference (CLI) from the gNB to the remote SL UE. In contrast, in a conventional relay UE-assisted design, the FD relay UE can autonomously initiate measurements and determine the Uu and SL beams used for FD relaying, which can then be reported to the network.

[0129] Figure 7Example scenario 700 (Scenario 2) is depicted, which involves a reverse relay direction from a remote UE to a network entity. In other words, an SL (e.g., SL mode 1 or SL mode 2) link can be formed from a remote SL UE (e.g., which may be at the network's OOC or IC) to the relay UE, and a Uu link can be formed from the relay UE to the network entity. In this scenario, the relay UE can perform FD communication using SL reception and Uu transmission.

[0130] like Figure 7 As illustrated, the second scenario can be further divided into two sub-scenarios based on whether the remote SL UE is within the coverage area (IC) or outside the coverage area (OOC) of the network area served by the gNB. Scenario 2A may refer to the scenario where the remote SL UE 702 is in OOC and the relay provides coverage extension. In Scenario 2A, the link from the remote UE to the relay UE may be in SL mode 2. Scenario 2B may refer to the scenario where the remote SL UE 704 is in IC and the relay provides UL throughput enhancement. In Scenario 2B, the link from the remote UE to the relay UE may be in SL mode 1.

[0131] In Scenario 2, aspects of this disclosure provide techniques that allow the gNB to determine the beams in both Uu and SL to minimize self-interference (SI) at the FD relay UE and cross-link interference (CLI) from the remote SL UE to the gNB.

[0132] Figures 8 to 10 Example deployments 800, 900, and 1000 according to certain aspects of this disclosure are depicted in Scenario 1.

[0133] As described above, according to certain aspects of this disclosure, a network entity (e.g., gNB) can initiate / coordinate beam measurement / reporting to identify / select / determine the FD beam for the relay UE in the forward direction. According to certain aspects, in Scenario 1, as a centralized design, the gNB can determine the beam in both the air / radio interface (e.g., Uu) link and the SL link to minimize the SI at the FD relay UE and the CLI from the gNB to the remote SL UE. Figure 8 As illustrated in section 802, once the beam is determined, the gNB can signal the determined Uu and SL FD beams to the relay UE.

[0134] In some aspects, to determine the FD Uu and SL beams for a relay UE, when the relay UE is serving multiple remote UEs, the gNB may notify the relay UE which SL beam(s) of which remote SL UE should be measured. In some aspects, to minimize CLI from the gNB to the remote SL UE, the gNB may transmit a request for beam reporting to the remote UE (e.g., especially when the gNB cannot reliably reach the remote UE but can still influence it via CLI). In some aspects, this request may be transmitted via the relay UE.

[0135] For gNB configuration of beam measurements for FD beam selection at the relay UE, the gNB can benefit from information about the SL beam used for the intended remote UE at the relay UE. For example... Figure 9 As illustrated in section 902, according to certain aspects of this disclosure, a relay UE may provide the gNB with information about candidate SL beams and corresponding remote UE identifiers in order to facilitate the gNB's scheduling of FD beam measurements.

[0136] In some aspects, a relay UE may report candidate SL transmit (Tx) and / or receive (Rx) beam IDs and associated remote UE IDs (e.g., the top X best SL Tx and / or Rx beams in half-duplex (HD) mode) to the gNB. In some aspects, the SLTx / Rx beam ID may be represented by the SL Tx / Rx transmit configuration indicator (TCI) status ID. In some aspects, the remote UE ID may be represented by the Layer 1 (L1) and / or Layer 2 (L2) SL UE ID. In some cases, the reporting may be autonomously transmitted, periodically (P) / semi-persistently (SP) / or aperiodically (AP) scheduled, or event-triggered (e.g., when the threshold amount of the current X best SL Tx and / or Rx beams changes or when the threshold amount of the link quality metric measured on the top X best SL Tx and / or Rx beams changes).

[0137] As mentioned above, SI can occur at an FD device that simultaneously transmits and receives. For example, such as Figure 10 As illustrated, SI1002 may occur at the FD relay UE. According to certain aspects of this disclosure, the gNB may be configured for measurement and / or reporting of FD relay beam pair selection. For example, in some aspects, in order to select the FD Uu and SL beams at the relay UE, the gNB may request the relay UE to report the downlink (DL) signal-to-interference-and-noise ratio (SINR) of candidate pairs of SI 1002 or SL Tx beam 1006 and Uu Rx beam 1004.

[0138] In some aspects, FD beam measurement and reporting can be based on SL operations, such as... Figure 11As illustrated in timing diagram 1100, the gNB can instruct the relay UE (e.g., via DCI) to transmit SL services (e.g., PSCCH / PSSCH) using a specific SL Tx beam 1106 for a given remote SL UE, while simultaneously measuring SI 1002 associated with a specific Uu Rx beam 1004 at the relay UE. This contrasts with conventional SL Mode 1 operation, where detailed SL operation parameters are determined by the SL UE, rather than controlled by the gNB as presented herein. In some respects, FD relay beam measurement reports based on SL services can be scheduled dynamically, semi-persistently, or periodically.

[0139] like Figure 12 As illustrated in timing diagram 1200, in some respects, as an alternative to (or, for example, a supplement to) SI, in addition to SI 1002 from SL Tx beam 1006, the gNB may also request the relay UE to measure the DL SINR of Uu Rx beam 1004. To calculate SINR without additional overhead, the DL reference signal received power (RSRP) can be measured from the downlink control information (DCI) received by the expected Uu Rx beam 1202. This can be combined with the measured SI 1002 to calculate the DL SINR of Uu Rx beam 1004 when paired with SL Tx beam 1006.

[0140] Alternatively, for example, such as Figure 12 As illustrated, the gNB may schedule a dedicated DL reference signal (RS) (e.g., received by the desired Uu Rx beam 1202) to the relay UE to measure the DL RSRP using the desired Uu Rx beam. In some aspects, based on the measured DL RSRP and SI, the relay UE may calculate the corresponding DL SINR. In some aspects, as illustrated at 1204, the relay UE may report the SI or DL ​​SINR to the gNB in ​​a separate report or together with acknowledgment (ACK) or negative ACK (NACK) information for SL services.

[0141] In some respects, the gNB can also indicate the time / frequency location of the DL measurement resources (e.g., the DL bandwidth portion (BWP) or DL ​​subband) for which SI and / or RSRP are to be measured. By measuring SI and / or RSRP over a smaller bandwidth, the relay UE can save power without sacrificing measurement accuracy.

[0142] like Figure 13 As illustrated in timing diagram 1300, according to certain aspects of this disclosure, FD beam measurements / reporting can be based on a dedicated RS (such as SL RS1302) in the SL and Uu. For example, as Figure 13As illustrated, in some aspects, in order to measure SI at the relay station from the SL Tx beam at the relay UE to the Uu Rx beam at the relay station, the gNB may schedule (e.g., via DCI 2) the relay UE to transmit SL RS1302 using the intended SL Tx beam 1006, while scheduling (e.g., via DCI 1) the SI measurement resources of the relay UE to measure SI 1002 using the intended Uu Rx beam 1004.

[0143] In some aspects, such as Figure 13 As illustrated, the gNB can also schedule the DL RS of the relay UE to measure the DL RSRP using the expected Uu Rx beam (e.g., via DCI 3). The relay UE can calculate the corresponding DL SINR based on the DL RSRP and SI. In some cases, the gNB can also schedule the UL resources of the relay UE to report (e.g., via PUCCH) the measured SI or DL ​​SINR for the considered FD relay beam pair including the SLTx beam and the Uu Rx beam, as illustrated at 1304.

[0144] RS-based FD relay beam measurements / reporting can be scheduled dynamically, semi-persistently, or periodically. In some cases, such as Figure 14 As illustrated in timing diagram 1400, when measurements / reporting are dynamically scheduled, any combination of the SL RS Tx1404, SI measurement resources, and DL RS1406 can be co-scheduled by a single DCI 1402, rather than by multiple corresponding DCIs as described in the example above. For example, as illustrated, Figure 14 The DCI 1402 schedules SL RS1404 and DL RS1406.

[0145] In some respects, the gNB can indicate the time / frequency location of SI measurement resources (e.g., the entire DL BWP or DL ​​subband), enabling the relay UE to schedule measurements of the SI on the intended DL subband for potential DL services.

[0146] In some respects, for a given beam report, the gNB can schedule the UE to report results for multiple candidate FD Uu+SL beam pairs. For example, as Figure 14 As illustrated, the gNB can schedule the UE to report the results of SL Tx beam 1 + Uu Rx beam 1 and SL Tx beam 2 + Uu Rx beam 2. In some cases, the UE can report the top Y best pairs of DL SINR or SI out of the total X beam pairs measured.

[0147] In some cases, such as Figure 15As illustrated in scenario 1500, due to the selected Uu+SL FD relay beam, a non-negligible CLI 1502 may occur at the remote UE. In some cases, CLI 1502 may be significant in power even if the remote UE is outside the gNB's coverage area for communication purposes. According to certain aspects of this disclosure, such as Figure 16 As illustrated in timing diagram 1600, the gNB can configure CLI measurement resources and beam reports (e.g., CLI reports in PUCCH) 1604 from the remote SL UE to determine whether the selected Uu+SL FD relay beam will cause a non-negligible CLI at the remote UE.

[0148] In some cases, the remote UE may be within the network's coverage area (IC) (e.g., the relay is primarily used for throughput improvement purposes). In such cases, the gNB may use the selected Uu beam to transmit DL RS and request the remote UE to report the corresponding CLI metric (e.g., RSRP or Received Signal Strength Indicator (RSSI)) measured using the selected SL beam, which may be identified by the relay UE's SL TCI status.

[0149] As mentioned above, the remote UE may be out of control (OOC), and the relay may be primarily used for coverage improvement purposes. In such cases, the control / data from the gNB may not be decoded by the remote UE, but it may still cause a non-negligible CLI for the remote UE. Since the remote UE cannot reliably decode control information from the gNB, the relay UE may be required to relay measurement / reporting related information between the gNB and the remote UE.

[0150] For example, such as Figure 17 As illustrated in timing diagram 1700, the relay UE can forward CLI measurement resource locations and SL Rx beams (e.g., provided by the gNB via DCI) to the remote UE via Side Link Control Information (SCI). Additionally, in some cases, the remote UE can provide CLI reports (e.g., via PSFCH) 1702, and the relay UE can forward CLI reports / measurement results to the gNB via PUCCH or PUSCH, as... Figure 17 Example of 1704 locations in China.

[0151] Figure 18Example 1800 of Scenario 2 according to certain aspects of this disclosure is depicted. As described above, Scenario 2 relates to the operational direction of the FD relay UE from the remote UE to the network entity (e.g., which may be referred to as the "reverse direction" of the relay). In other words, an SL (e.g., SL mode 1 or SL mode 2) link can be formed from the remote SL UE (e.g., which may be at the OOC or IC of the network) to the relay UE, and a Uu link can be formed from the relay UE to the network entity. In this scenario, the relay UE can perform FD communication using SL reception and Uu transmission. In Scenario 2, aspects of this disclosure provide techniques that allow the gNB to determine the beam in both Uu and SL to minimize self-interference (SI) at the FD relay UE and cross-link interference (CLI) from the remote SL UE to the gNB.

[0152] Similar to Scenario 1 discussed above (e.g., the forward direction of the relay), centralized FD relay beam selection can be used in the reverse direction of the relay (Scenario 2) (e.g., the gNB can determine the Uu and SL beams) to minimize the SI at the FD relay UE and the CLI from the remote SL UE to the gNB. For example, the gNB can initiate / coordinate beam measurement / reporting, and based on this beam measurement / reporting, the gNB selects / determines the FD beams for both Uu and SL, and signals the determined FD beams to the relay UE in the reverse direction, such as... Figure 18 Example of location 1802.

[0153] A key difference from the forward direction described in Scenario 1 is that, in order to measure SL SINR considering SI, the relay UE may want to know the SL RSRP from the remote UE, which can be measured based on the SL feedback channel from the remote UE (e.g., the Physical Side Link Feedback Channel (PSFCH)). Another key difference is that if the remote UE is outside the NW coverage area, it may have to send requests and / or measurement reports from / to the gNB relay SL RS.

[0154] In some cases, the FD relay beam used for the forward direction (Scenario 1) may not be suitable for the reverse direction (Scenario 2) because different Tx and Rx beams can be used for Uu or SL communication (e.g., due to Maximum Permissible Exposure (MPE) requirements / issues). In this case, the FD beam pair can be selected separately for the reverse relay direction.

[0155] like Figure 19 As illustrated in example scenario 1900, SI 1902 can be generated by simultaneous uplink transmission (e.g., using Uu Tx beam 1904) and sidelink reception (e.g., using SL Rx beam 1906). According to certain aspects of this disclosure, FD beam measurements / reporting can be based on Uu / SL services. For example, as... Figure 20As illustrated, the gNB can instruct the relay UE (e.g., via DCI) to use a specific Uu Tx beam 1904 to transmit UL Tx (e.g., PUSCH / PUCCH) in Uu, and simultaneously measure SI 1902 via a specific SL Rx beam 1906 for a given remote SL UE. Figure 20 As illustrated in timing diagram 2000, the measured SI 1902 can also be reported to the gNB (e.g., via PUCCH / PUSCH in the SI report or in the Media Access Control-Control Element (MAC-CE)).

[0156] Figure 21 A timing diagram 2100 depicts an example of scenario 2 exemplified according to certain aspects of this disclosure.

[0157] In some respects, as an alternative to (or supplement to) SI, gNB can also request the relay UE to measure the SL SINR from the remote UE to the relay UE, taking into account the SI at the relay UE, based on Uu and SL services.

[0158] To calculate SL SINR, SI can be measured based on UL traffic in Uu as described above, while SL RSRP can be measured based on the SL traffic / feedback channel from the remote UE to the relay UE. For example, SL RSRP can be measured based on feedback from the remote UE (e.g., ACK / NACK feedback) (e.g., transmitted via PSFCH), such as... Figure 21 As illustrated at 2102. As shown at 2104, a relay UE can report the SL SINR based on the measured SL RSRP and SI (e.g., together with the ACK / NACK of the SL service in the PUCCH / PUSCH). In some aspects, the relay UE can report the SI and SL RSRP separately to the gNB, and the gNB can calculate the SL SINR accordingly.

[0159] As stated above, and as Figure 22 As illustrated in example scenario 2200, SL RSRP can be measured based on SL traffic or feedback channels from the remote UE to the relay UE. In some respects, this can be accomplished using ongoing traffic from the remote UE (e.g., in half-duplex (HD) mode), such as... Figure 23 As illustrated in timing diagram 2300. For example, as... Figure 23 As illustrated, the HD SL Tx beam 2302 of the remote UE can be used to measure the SL RSRP. The relay UE can recommend that the remote UE use a specific SL Tx beam that matches the SL Rx beam on which the relay UE has already measured SI for its HD transmission, thereby enabling the calculation of an accurate SINR.

[0160] Similar to FD beam measurement / reporting in Scenario 1, FD beam measurement / reporting in Scenario 2 can also be based on dedicated RS in SL and Uu. For example, as Figure 24 As illustrated in timing diagram 2400, in order to measure SI at the relay UE from the Uu Tx beam at the relay UE to the SL Rx beam at the relay UE, the gNB can schedule the relay UE to transmit UL RS (e.g., SRS) 2402 using the expected Uu Tx beam 2404, while scheduling the SI measurement resources of the relay UE to measure SI 2406 using the expected SL Rx beam 2408.

[0161] To measure the SL SINR at a relay, when using the expected SL Tx / Rx beam, the relay UE may want to know the SL RSRP from the remote UE. To achieve this, the gNB can schedule the remote UE to send SL RS2410 (e.g., SL Channel State Information (CSI) - RS) to the relay UE using the expected SL Tx beam 2412, and also schedule the relay UE to measure the RSRP using the expected SL Rx beam, such as... Figure 24 As illustrated. If the remote UE is in the OOC of the network, the gNB's request to send SL RS can be relayed by the relay UE (e.g., via SCI).

[0162] As mentioned above, in some cases, time-frequency resources can be allocated for SINR reports. In such cases, when the remote UE is in Mode 2SL, the sidelink transmission timing may not be controlled by the gNB. Therefore, some gNB flexibility regarding SINR report resources may be necessary, since the SL transmission timing may not be known in advance at the gNB (e.g., affecting RSRP calculation). See [references to...] for details. Figures 25 to 26 The timing diagrams 2500 and 2600 illustrated in the figure are used to understand the options for increasing gNB flexibility (e.g., flexibility for reporting timing requirements).

[0163] In some respects (e.g., according to the first option: Alt 1), compared to mode 1, the gNB can instruct a longer default time between SI measurement resources and SINR reporting resources in mode 2 to increase the probability of capturing SL transmissions at the relay UE. If no SL transmission is captured, the relay UE may not report anything, and the gNB may reschedule SINR measurements.

[0164] In some respects (e.g., according to the third option: Alt 3), the gNB can allocate fixed SINR reporting time-frequency resources with flexible content. If the SL transmission is captured before the allocated time and the SL RSRP is calculated, the relay UE can indicate SINR in the report.

[0165] In some cases, when using Alt 1 or Alt 3, and if no SL transmission is captured, the relay UE may indicate only SI in the report. In such cases, a bit can be configured to indicate whether the report includes the SINR value or the SI value.

[0166] For reference Figure 25 The timing diagram 2500 can be used to understand Alt 1 and Alt 3. For example, as illustrated, if no SL transmission is captured (e.g., within a long default time window or a fixed SINR reporting resource), the SI or SL SINR report can be cancelled (as indicated at 2502). In such cases, the gNB can reschedule the SINR measurement, or, as illustrated, the relay UE can instead send an SL SI report 2504 (e.g., including SI, but without SINR).

[0167] In some respects (e.g., according to the second option: Alt 2), gNB can schedule periodic / semi-persistent resources for SINR reporting in mode 2. See also... Figure 26 The timing diagram 2600 can be used to understand Alt 2. For example, a relay UE can use resources received later in time than in SL mode 2 to transmit SINR report 2602 (e.g., in PUCCH), as... Figure 26 As illustrated. If no SL reception occurs in a certain (e.g., configured) number of resources, authorization can be automatically revoked, or the gNB can revoke authorization.

[0168] As described above, a remote UE can cause a non-negligible CLI to gNB UL communication using selected Uu and SL FD relay beams (e.g., in the reverse direction). See also... Figure 27 The example scenario 2700 illustrates this non-negligible CLI.

[0169] According to certain aspects of this disclosure, the gNB can request the remote UE to participate in CLI measurements based on the selected Uu and SL FD relay beams in the reverse direction to determine whether the remote UE will cause non-negligible CLI 2702 to gNB UL communication. For example, in some aspects, the CLI estimation can be based on UL measurements. In such aspects, such as Figure 28 As illustrated in timing diagram 2800, the gNB can request the remote UE to transmit SL RS 2802 using the expected SL Tx beam 2804. Based on this, the gNB can use the expected UuRx beam 2806 to measure CLI. In some cases, if the remote UE is in an OOC state of the network, the gNB's request to transmit SL RS may have to be relayed (e.g., via SCI), such as... Figure 28 Example of location 2808 in China.

[0170] In some respects, CLI estimation can be based on DL measurements. In such respects, such as... Figure 29 As illustrated in timing diagram 2900, the gNB can transmit DL RS 2902 to the FD relay UE (e.g., which can use the corresponding Uu UL beam) using Uu DL beam 2904 (e.g., which could be an example of Uu Rx beam 2806), and the gNB can request the remote UE to report the RSRP / RSSI of the DL RS using SL Rx beam 2906 (e.g., which could be an example of SL Tx beam 2804) corresponding to the SL Tx beam used by the FD relay UE. Based on this DL report, the gNB can estimate the path loss and CLI (e.g., if the gNB knows the remote UE's Tx power). In some cases, the CLI can be reported by the remote UE, rather than estimated by the gNB. In some cases, if the remote UE is in OOC of the network, the gNB's request for measuring DL RS and the DL report may have to be relayed (e.g., via SCI and PSFCH respectively), as... Figure 29 As illustrated. In such cases, the time-frequency resources reported by the relayed CLI can be configured by the gNB.

[0171] The aspects of this disclosure (including centralized beam determination for FD communication) can be applied to scenarios involving bidirectional FD between two SL UEs (e.g., with at least one SL UE within network coverage). According to some aspects, for example, the gNB can determine and signal the SL Tx and Rx beams at each of the two UEs participating in bidirectional FD communication between UEs.

[0172] Figure 30 An example scenario 3000 involving bidirectional FD communication is depicted, in which two SL UEs are both within the coverage area (IC) of the network. In such a scenario, each SL UE can operate in mode 1 (e.g., its SL resources are scheduled by the gNB). According to certain aspects of this disclosure, in order to achieve bidirectional SL FD between the two SL UEs, the gNB should determine the SL Tx and Rx beams of each SL UE to minimize self-interference (SI) at each SL UE.

[0173] like Figure 30As shown, in this scenario, each SL UE has a transmit beam and a receive beam. For example, FD UE 1 has a transmit beam 3002 and a receive beam 3004, and FD UE 2 has a transmit beam 3006 and a receive beam 3008. The transmit beam of each SL UE forms a beam pair with the receive beam of another SL UE. For example, as illustrated, transmit beam 3002 forms a beam pair with receive beam 3008, and transmit beam 3006 forms a beam pair with receive beam 3004. Additionally, as illustrated, each SL UE forms a Uu link with a network entity.

[0174] According to certain aspects of this disclosure, the gNB can initiate / coordinate SL beam measurements / reports for each SL UE. The gNB can then determine and signal the SL Tx and Rx beams for each SL UE (e.g., for a bidirectional SL FD) based on the measurements / reports, such as... Figure 30 Examples of locations 3010 and 3012 are shown.

[0175] However, in some cases, one SL UE may be within the network's IC (In-Coverage), while another SL UE may be outside the network's coverage area (OOC). For example... Figure 31 As illustrated in example scenario 3100, in such cases, the SL UE (e.g., FD UE2) in the OOC of the network may not form a Uu link with the network entity. Furthermore, in such cases, the IC SL UE is in mode 1, while the OOC SL UE is in mode 2 (e.g., its SL resources are selected by itself based on its own sensing). When an SL UE is in OOC, measurement / reporting / beam indication can be relayed via the SL UE in the IC, such as... Figure 31 Example of location 3102.

[0176] Similar to scenarios 1 and 2 discussed above, to facilitate gNB scheduling of FD beam measurements at the SL UE, the SL UE can provide the gNB with candidate SL Tx and / or Rx beam IDs and associated communication neighbor UE IDs (e.g., the top X best SL Tx and / or Rx beams in half-duplex (HD) mode), such as... Figure 32 Example scenario 3200 illustrates this. For instance, since FD UE2 is in OOC, it can provide SL beam and remote UE information to FD UE1 (e.g., it is in IC), as illustrated at 3202. As shown at 3204, FD UE1 can relay the SL beam and remote UE information to the network entity / gNB.

[0177] In some aspects, the SL Tx and / or Rx beam IDs can be represented by the SL Tx and / or Rx TCI state IDs (e.g., by signal notification). In some aspects, the associated neighboring UE IDs can be represented by the Layer 1 / L2 (L1 / L2) SL UE IDs. In some aspects, reports can be periodically (P) / semi-persistently (SP) / aperiodically (AP) scheduled, or event-triggered (e.g., every X current optimal SL Tx and / or Rx beam changes). In some cases, as described above, when one of the SL UEs is out of commission (OOC), the information it provides can be relayed via the IC SL UE relay, such as... Figure 32 exemplified.

[0178] As described above, according to certain aspects of this disclosure, the gNB can be configured for measurement / reporting of FD SL beam pair selection (e.g., in a two-way FD scenario). To select an FD SL beam between two UEs, the gNB can request each UE to report the SI or DL ​​SINR of candidate pairs of SL Tx and Rx beams at each UE. For example, in some aspects, FD beam measurement / reporting can be based on SL services. For example, as... Figure 33 As illustrated in timing diagram 3300, gNB may instruct UE (e.g., UE 1 in IC) to transmit SL services (e.g., PSCCH / PSSCH) using a specific SL Tx beam 3302 given a neighboring SL UE (e.g., UE 2), and simultaneously measure SI 3304 caused at a specific SL Rx beam 3306.

[0179] In some respects, the SL Tx and Rx beams of a given neighboring UE can be indicated by the corresponding SL TCI state.

[0180] In some respects, as an alternative to (or, for example, a supplement to) SI, the gNB may also request the SL UE to consider the SI from the SL Tx beam to measure the SL SINR of the SL Rx beam, such as Figure 34 The timing diagram 3400 illustrates this. In this way, SL RSRP can be measured from services / feedback using the same SL Rx beam without additional overhead. For example, the gNB can instruct a neighboring UE (e.g., UE 2) to transmit PSFCH using the expected SL Tx beam 3402 corresponding to the SL Rx beam at the measuring UE (e.g., UE 1). In some cases, SL RSRP can be measured based on (e.g., by the gNB or by one or both SL UEs) configured to transmit PSCCH / PSSCH using the same SLTx-Rx beam.

[0181] In some respects, the SL UE may report SI or SL SINR to the gNB in ​​a separate report or together with the SL service ACK / NACK, as illustrated at 3404. In some respects, FD relay beam measurements / reporting based on SL services may be scheduled dynamically, semi-persistently, or periodically.

[0182] In some respects, gNB can also indicate the time / frequency location of SL measurement resources used for SI measurements (e.g., the entire SL BWP / resource pool or SL subband).

[0183] According to certain aspects of this disclosure, FD beam measurement / reporting can be based on a dedicated RS in the SL. In some aspects, for example, the SL services transmitted and received at the measurement UE (e.g., PSCCH / PSSCH and PSFCH) can be replaced by transmitted and received SL RS 3502 and 3504 (e.g., CSI-RS), such as... Figure 35 The timing diagram 3500 illustrates this.

[0184] In some cases, when a neighboring UE (e.g., UE 2) is also in the IC, its transmitted SL RS can be directly scheduled by the gNB, such as... Figure 35 Example at location 3506. Alternatively, the request can be sent via IC SL UE (e.g., UE 1) relay SL RS.

[0185] According to certain aspects of this disclosure, after determining the FD beam (e.g., the Tx and Rx FD beams of a relay UE or a two-way FD UE), the gNB may indicate the selected FD beam to the corresponding UE (e.g., configure the UE with the selected FD beam), such as Figure 36 The timing diagram 3600 illustrates this. For an IC UE, the indication can be direct (e.g., via Uu DL). For an OOC UE, the indication can be relayed via an IC UE.

[0186] For example, such as Figure 36 As illustrated, in a bidirectional FD UE scenario, procedure 3602 (e.g., as described in detail above) can be performed for UE 1 to determine its FD Tx and Rx beams. A similar procedure 3604 can be performed to determine the FD Tx and Rx beams for UE 2. Once the FD beams have been determined for both UEs, the gNB can configure UE 1 with its respective determined FD beam at 3606 and UE 2 with its respective determined FD beam at 3608. As stated above, if UE 2 is in OOC, UE 1 (e.g., it may be in IC) can relay the FD beam configuration of UE 2 (e.g., via SCI), as illustrated at 3610.

[0187] Example Operation

[0188] Figure 37 This shows a wireless node (such as...) Figure 1 and Figure 3 At BS102) or as relative to Figure 2 An example of a method for wireless communication at a decomposed base station 3700 is discussed.

[0189] Method 3700 begins at step 3705, where at least one report indicating information about the candidate beam is obtained. In some cases, the operation of this step involves, as referenced... Figure 39 The circuit described is used to obtain and / or the code used to obtain, or can be executed by the circuit and / or the code.

[0190] Then, method 3700 proceeds to step 3710, where a pair of beams is selected from the candidate beams based on information. In some cases, this step involves operations such as those described in the reference. Figure 39 The circuitry and / or code described for selection, or that can be executed by the circuitry and / or the code.

[0191] Then, method 3700 proceeds to step 3715, where an output indicates that at least one UE wants to use the pair of beams for FD wireless communication on the first and second links to transmit. In some cases, the operation of this step involves, as referenced... Figure 39 The circuitry described for the output and / or the code for the output, or the circuitry and / or the code that can be executed.

[0192] In some aspects, the beam pair includes: a first beam for use by at least one UE to communicate with a wireless node on a first link; and a second beam for use by at least one UE to communicate with a second UE on a second link.

[0193] In some aspects, method 3700 also includes: outputting a signal for transmission on the first link. In some cases, the operation of this step involves, as described in the reference... Figure 39 The circuitry described for the output and / or the code for the output, or the circuitry and / or the code that can be executed.

[0194] In some aspects, method 3700 also includes: obtaining a signal on a second link. In some cases, the operation of this step involves, as described in the reference... Figure 39 The circuit described is used to obtain the circuit and / or the code used to obtain the circuit, or the circuit and / or the code can be executed by the circuit and / or the code.

[0195] In some respects, the second UE is in the IC or OOC of the wireless node.

[0196] In some aspects, at least one UE includes a first UE and at least a second UE, and the pair of beams includes: a first beam for use by the first UE to transmit to the second UE on a first link; and a second beam for use by the first UE to receive from the second UE on a second link.

[0197] In some respects, the information includes at least one of the following: SI measurement; CLI measurement; SINR measurement; RSRP measurement; RSSI measurement; candidate beam ID; or the ID of a second UE associated with at least one of the candidate beams.

[0198] In some respects, at least one report is at least one of the following: periodically scheduled; semi-persistently scheduled; non-periodic scheduled; or event-triggered.

[0199] In some aspects, method 3700 further includes: outputting a request for transmission of at least one of the following: at least one report; or measurement information regarding the candidate beam. In some cases, the operation of this step involves, as referenced... Figure 39 The circuitry described for the output and / or the code for the output, or the circuitry and / or the code that can be executed.

[0200] In some respects, the request requires instructions on at least one of the following: candidate beam pairs to be included in the report; candidate beam pairs for which measurements are to be performed; measurement type; beam ID; or time and frequency resources for the measurement.

[0201] In some respects, the report indicates at least one measurement performed by the second UE.

[0202] In some aspects, method 3700 further includes: scheduling at least one transmission associated with at least one UE, wherein at least one report also indicates one or more measurements of at least one transmission. In some cases, the operation of this step involves, as referenced... Figure 39 The circuitry described for scheduling and / or the code for scheduling, or the circuitry and / or the code that can be executed.

[0203] In some aspects, method 3700 further includes: outputting an indication of a resource associated with at least one scheduled transmission for transmission. In some cases, the operation of this step involves, as referenced... Figure 39 The circuitry described for the output and / or the code for the output, or the circuitry and / or the code that can be executed.

[0204] In one respect, method 3700 or any aspect thereof may be made by means of a device (such as...) Figure 39The communication device 3900 performs the method, which includes various components operable to, configured to, or adapted to perform the method 3700. The communication device 3900 is described in more detail below.

[0205] It should be noted that Figure 37 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0206] Figure 38 This shows wireless devices (such as...) Figure 1 and Figure 3 An example of a method 3800 for wireless communication at UE 104.

[0207] Method 3800 begins at step 3805, wherein signaling is obtained instructing the wireless device to use a pair of beams for FD wireless communication on the first and second links. In some cases, the operation of this step involves, as described in reference... Figure 39 The circuit described is used to obtain the circuit and / or the code used to obtain the circuit, or the circuit and / or the code can be executed by the circuit and / or the code.

[0208] Then, method 3800 proceeds to step 3810, where the pair of beams is used for communication according to signaling. In some cases, the operation of this step involves, as described in the reference... Figure 39 The circuitry described is for communication and / or the code for communication, or the circuitry and / or the code is executable.

[0209] In some respects, the beam pair includes: a first beam for use by a wireless device to communicate with a wireless node on a first link; and a second beam for use by a wireless device to communicate with a second wireless device on a second link.

[0210] In some aspects, method 3800 also includes: obtaining a signal on the first link. In some cases, the operation of this step involves, as referenced... Figure 39 The circuit described is used to obtain the circuit and / or the code used to obtain the circuit, or the circuit and / or the code can be executed by the circuit and / or the code.

[0211] In some aspects, method 3800 also includes: outputting a signal for transmission on a second link. In some cases, the operation of this step involves, as described in the reference... Figure 39 The circuitry described for the output and / or the code for the output, or the circuitry and / or the code that can be executed.

[0212] In some respects, the second wireless device is in the IC or OOC of the wireless node.

[0213] In some respects, the beam pair includes: a first beam for use by the wireless device to transmit to the second wireless device on the first link; and a second beam for use by the wireless device to receive from the second wireless device on the second link.

[0214] In some respects, the information includes at least one of the following: SI measurement; CLI measurement; SINR measurement; RSRP measurement; RSSI measurement; candidate beam ID; or the ID of a second wireless device associated with at least one of the candidate beams.

[0215] In some respects, at least one report is at least one of the following: periodically scheduled; semi-persistently scheduled; non-periodic scheduled; or event-triggered.

[0216] In some aspects, method 3800 further includes: outputting at least one report indicating information about the candidate beam for transmission. In some cases, the operation of this step involves, as referenced... Figure 39 The circuitry described for the output and / or the code for the output, or the circuitry and / or the code that can be executed.

[0217] In some aspects, method 3800 further includes: obtaining a request for at least one of the following: at least one report; or measurement information regarding the candidate beam. In some cases, this step involves, as referenced... Figure 39 The circuit described is used to obtain the circuit and / or the code used to obtain the circuit, or the circuit and / or the code can be executed by the circuit and / or the code.

[0218] In some respects, the request requires at least one of the following: candidate beam pairs to be included in the report; candidate beam pairs for which measurements are to be performed; measurement type; beam ID; or time and frequency resources for the measurement.

[0219] In some respects, the report indicates at least one measurement performed by a second wireless device.

[0220] In some respects, at least one report also indicates one or more measurements that are scheduled to be transmitted and associated with at least one wireless device.

[0221] In some aspects, method 3800 further includes: obtaining an indication of a resource associated with at least one scheduled transmission. In some cases, this step involves operations such as those described in reference... Figure 39 The circuit described is used to obtain the circuit and / or the code used to obtain the circuit, or the circuit and / or the code can be executed by the circuit and / or the code.

[0222] In one respect, method 3800 or any aspect thereof may be made by means of a device (such as...) Figure 39The communication device 3900 performs the method, which includes various components operable to, configured to, or adapted to perform the method 3800. The communication device 3900 is described in more detail below.

[0223] It should be noted that Figure 38 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0224] Example communication device

[0225] Figure 39 Various aspects of the example communication device 3900 are described. In some aspects, the communication device 3900 is user equipment, such as those described above relative to... Figure 1 and Figure 3 The UE 104 is described. In some respects, the communication device 3900 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as relative to Figure 2 The decomposed base station is discussed.

[0226] The communication device 3900 includes a processing system 3905 coupled to a transceiver 3975 (e.g., a transmitter and / or receiver). In some aspects (e.g., when the communication device 3900 is a network entity), the processing system 3905 may be coupled to a network interface 3985, which is configured to communicate via a communication link (such as as described herein, relative to...). Figure 2 The described backhaul link, midhaul link, and / or fronthaul link receive and transmit signals from the communication device 3900. The transceiver 3975 is configured to transmit and receive signals from the communication device 3900 via the antenna 3980, such as the various signals described herein. The processing system 3905 can be configured to perform processing functions of the communication device 3900, including processing signals received by the communication device 3900 and / or to be transmitted by the communication device.

[0227] Processing system 3905 includes one or more processors 3910. In various aspects, the one or more processors 3910 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as relative to... Figure 3 As described. In various respects, one or more processors 3910 may represent one or more of the following: receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as relative to Figure 3As described. One or more processors 3910 are coupled to a computer-readable medium / memory 3940 via a bus 3970. In some aspects, the computer-readable medium / memory 3940 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 3910, cause one or more processors 3910 to perform relative to Figure 37 The method described in 3700 or any aspect thereof; and relative to Figure 38 The method 3800 described or any aspect thereof. It should be noted that reference to a processor performing the functions of the communication device 3900 may include one or more processors 3910 performing those functions of the communication device 3900.

[0228] In the depicted example, computer-readable medium / memory 3940 stores code (e.g., executable instructions), such as code 3945 for acquisition, code 3950 for selection, code 3955 for output, code 3960 for scheduling, and code 3965 for communication. Processing the code 3945 for acquisition, the code 3950 for selection, the code 3955 for output, the code 3960 for scheduling, and the code 3965 for communication enables the communication device 3900 to perform operations relative to... Figure 37 The method described in 3700 or any aspect thereof; and relative to Figure 38 The method described is 3800 or any aspect thereof.

[0229] One or more processors 3910 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 3940, including circuitry 3915 for acquisition, circuitry 3920 for selection, circuitry 3925 for output, circuitry 3930 for scheduling, and circuitry 3935 for communication. Processing performed using the acquisition circuitry 3915, selection circuitry 3920, output circuitry 3925, scheduling circuitry 3930, and communication circuitry 3935 enables the communication device 3900 to perform operations relative to... Figure 37 The method described in 3700 or any aspect thereof; and relative to Figure 38 The method described is 3800 or any aspect thereof.

[0230] Various components of the communication device 3900 can provide parts for performing relative to Figure 37 The method described in 3700 or any aspect thereof; and relative to Figure 38 The described method 3800 or any aspect thereof. For example, components for transmitting, conveying, or outputting to perform the transmission may include... Figure 3The transceiver 354 and / or antenna 352 of UE 104 illustrated in the figure Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 illustrated in the figure are... Figure 39 The communication device 3900 includes a transceiver 3975 and an antenna 3980. Components for receiving or acquiring data may include... Figure 3 The transceiver 354 and / or antenna 352 of UE 104 illustrated in the figure Figure 3 The transceiver 332 and / or antenna 334 of the BS102 illustrated in the figure are... Figure 39 The transceiver 3975 and antenna 3980 of the communication equipment 3900.

[0231] The components for acquisition, selection, output, scheduling, and communication may include... Figure 3 or Figure 39 Any of the various processors and / or transceivers shown.

[0232] Example Terms

[0233] Specific implementation examples are described in the following numbered clauses:

[0234] Clause 1: A method for wireless communication at a wireless node, the method comprising: obtaining at least one report indicating information about candidate beams; selecting a pair of beams from the candidate beams based on the information; and outputting signaling indicating that at least one UE wants to use the pair of beams to perform FD wireless communication on a first link and a second link for transmission.

[0235] Clause 2: The method according to Clause 1, wherein the pair of beams comprises: a first beam for use by the at least one UE to communicate with the radio node on the first link; and a second beam for use by the at least one UE to communicate with a second UE on the second link.

[0236] Clause 3: The method described in Clause 2 further includes: outputting a signal to be transmitted on the first link.

[0237] Clause 4: The method described in Clause 2 further includes: obtaining a signal on the second link.

[0238] Clause 5: The method described in Clause 2, wherein the second UE is in the IC or OOC of the wireless node.

[0239] Clause 6: The method according to any one of Clauses 1 to 5, wherein the at least one UE comprises a first UE and at least a second UE, and the pair of beams comprises: a first beam for use by the first UE to transmit to the second UE on the first link; and a second beam for use by the first UE to receive from the second UE on the second link.

[0240] Clause 7: The method according to any one of Clauses 1 to 6, wherein the information includes at least one of the following: SI measurement; CLI measurement; SINR measurement; RSRP measurement; RSSI measurement; candidate beam ID; or ID of a second UE associated with at least one of the candidate beams.

[0241] Clause 8: The method according to any one of Clauses 1 to 7, wherein the at least one report is at least one of the following: periodically scheduled; semi-persistently scheduled; non-periodic scheduled; or event-triggered.

[0242] Clause 9: The method according to any one of Clauses 1 to 8 further comprises: outputting a request for transmission of at least one of the following: the at least one report; or measurement information regarding the candidate beam.

[0243] Clause 10: The method described in Clause 9, wherein the request indicates at least one of the following: to include candidate beam pairs in the report; candidate beam pairs for which measurements are to be performed; measurement type; beam ID; or time and frequency resources for the measurement.

[0244] Clause 11: The method according to any one of Clauses 1 to 10, wherein the report indicates at least one measurement performed by the second UE.

[0245] Clause 12: The method according to any one of Clauses 1 to 11, the method further comprising: scheduling at least one transmission associated with the at least one UE, wherein the at least one report further indicates one or more measurements of the at least one transmission.

[0246] Clause 13: The method according to Clause 12 further includes: outputting an indication of a resource associated with at least one scheduled transmission for transmission.

[0247] Clause 14: A method for wireless communication at a wireless node, the method comprising: obtaining signaling instructing the wireless device to use a pair of beams for FD wireless communication on a first link and a second link; and using the pair of beams to communicate in accordance with the signaling.

[0248] Clause 15: The method according to Clause 14, wherein the pair of beams comprises: a first beam for use by the wireless device to communicate with a wireless node on the first link; and a second beam for use by the wireless device to communicate with a second wireless device on the second link.

[0249] Clause 16: The method according to Clause 15 further includes: obtaining a signal on the first link.

[0250] Clause 17: The method according to Clause 15 further includes: outputting a signal for transmission on the second link.

[0251] Clause 18: The method according to Clause 15, wherein the second wireless device is in the IC or OOC of the wireless node.

[0252] Clause 19: The method according to any one of Clauses 14 to 18, wherein the pair of beams comprises: a first beam for use by the wireless device to transmit to the second wireless device on the first link; and a second beam for use by the wireless device to receive from the second wireless device on the second link.

[0253] Clause 20: The method according to any one of Clauses 14 to 19, wherein the information includes at least one of the following: SI measurement; CLI measurement; SINR measurement; RSRP measurement; RSSI measurement; candidate beam ID; or ID of a second wireless device associated with at least one of the candidate beams.

[0254] Clause 21: The method according to any one of Clauses 14 to 20, wherein the at least one report is at least one of the following: periodically scheduled; semi-persistently scheduled; non-periodic scheduled; or event-triggered.

[0255] Clause 22: The method according to any one of Clauses 14 to 21 further comprises: outputting at least one report indicating information about the candidate beam for transmission.

[0256] Clause 23: The method according to Clause 22 further includes: obtaining a request for at least one of the following: the at least one report; or measurement information regarding the candidate beam.

[0257] Clause 24: The method described in Clause 23, wherein the request indicates at least one of the following: to include candidate beam pairs in the report; candidate beam pairs for which measurements are to be performed; measurement type; beam ID; or time and frequency resources for the measurement.

[0258] Clause 25: The method according to any one of Clauses 14 to 24, wherein the report indicates at least one measurement performed by the second wireless device.

[0259] Clause 26: The method according to any one of Clauses 14 to 25, wherein the at least one report further indicates one or more measurements of at least one scheduled transmission associated with the wireless device.

[0260] Clause 27: The method according to Clause 26 further includes: obtaining an indication of a resource associated with the at least one scheduled transmission.

[0261] Clause 28: An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform a method according to any one of Clauses 1 to 27.

[0262] Clause 29: An apparatus comprising components for performing the method according to any one of Clauses 1 to 27.

[0263] Clause 30: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of a device, cause the device to perform the method according to any one of Clauses 1 to 27.

[0264] Clause 31: A computer program product embodied on a computer-readable storage medium, said computer-readable storage medium including code for performing a method according to any one of Clauses 1 to 27.

[0265] A network entity comprising: at least one transceiver; a memory including executable instructions; and a processor configured to execute the executable instructions and cause the network entity to perform a method according to any one of clauses 1 to 13, wherein the at least one transceiver is configured to perform at least one of: receiving the report or sending the signaling.

[0266] A user equipment (UE) comprising: at least one transceiver; a memory including executable instructions; and a processor configured to execute the executable instructions and cause the UE to perform a method according to any one of clauses 14 to 27, wherein the at least one transceiver is configured to transmit the signaling.

[0267] Additional Notes

[0268] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. 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. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Additionally, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0269] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0270] As used in this article, the phrase “at least one of” in a list of items refers to any combination of those items (including single members). For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0271] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, and so on. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, building, and so on.

[0272] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specified order of actions is given, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0273] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated, the term “some” refers to one or more. No element of any claim shall be interpreted in accordance with the provisions of 35 U.S.SC §112(f) unless that element is expressly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known to a person skilled in the art or will later be known are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims.

Claims

1. An apparatus for wireless communication, the apparatus comprising: The memory includes executable instructions; and One or more processors, the one or more processors being configured to execute the executable instructions and cause the device to: Obtain at least one report indicating information about the candidate beam; Based on the information, a pair of beams is selected from the candidate beams; as well as The output indicates that at least one user equipment (UE) wants to use the pair of beams to perform full-duplex (FD) wireless communication on the first and second links for transmission.

2. The apparatus of claim 1, wherein the pair of beams comprises: A first beam for use by the at least one UE to communicate with the device on the first link; and A second beam for use by the at least one UE to communicate with a second UE on the second link.

3. The apparatus of claim 2, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to perform at least one of the following: The output signal is transmitted on the first link via the first beam; or The signal is obtained on the second link via the second beam.

4. The apparatus of claim 2, wherein the second UE is within the coverage area (IC) or outside the coverage area (OOC) of the apparatus.

5. The apparatus of claim 1, wherein the at least one UE comprises a first UE and at least a second UE, and the pair of beams comprises: A first beam for use by the first UE to be transmitted to the second UE on the first link; and A second beam for use by the first UE to receive from the second UE on the second link.

6. The apparatus of claim 1, wherein the information includes at least one of the following: Self-interference (SI) measurement; Cross-link interference (CLI) measurement; Signal-to-interference-and-noise ratio (SINR) measurement; Reference signal (RS) received power (RSRP) measurement; Reference Signal Strength Indicator (RSSI) measurement; Candidate beam identifier (ID); or The ID of the second UE associated with at least one of the candidate beams.

7. The apparatus of claim 1, wherein the at least one report is at least one of the following: Periodically scheduled; Semi-persistent scheduling; Non-periodic scheduling; or The event was triggered.

8. The apparatus of claim 1, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to output a request for at least one of the following for transmission: The at least one report; or Measurement information regarding the candidate beam.

9. The apparatus of claim 8, wherein the request indicates at least one of the following: The candidate beam pairs in the at least one report must be included; The candidate beam pairs for which measurements are to be performed; Measurement type; Beam identifier (ID); or Time and frequency resources used for measurement.

10. The apparatus according to claim 1, wherein: The at least one report also indicates at least one measurement performed by the second UE, and The selection is further based on the at least one measurement.

11. The apparatus of claim 1, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to schedule at least one transmission associated with the at least one UE, wherein: The at least one report also indicates one or more measurements sent by the at least one, and The selection is further based on the one or more measurements.

12. The apparatus of claim 11, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to output an indication of a resource associated with at least one scheduled transmission for transmission.

13. The apparatus of claim 1, further comprising at least one transceiver, wherein the at least one transceiver is configured to receive the at least one report and transmit the signaling, and the apparatus is configured as a network entity.

14. An apparatus for wireless communication, the apparatus comprising: The memory includes executable instructions; and One or more processors, the one or more processors being configured to execute the executable instructions and cause the device to: Obtain signaling indicating that the device is to be used for full-duplex (FD) wireless communication on the first and second links; as well as Communication is performed using the pair of beams according to the signaling.

15. The apparatus of claim 14, wherein the pair of beams comprises: A first beam for the device to use in communicating with a wireless node on the first link; and A second beam for the device to use in communicating with a wireless device on the second link.

16. The apparatus of claim 15, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to perform at least one of the following: Signals are obtained on the first link via the first beam; or The output signal is transmitted on the second link.

17. The apparatus of claim 15, wherein the wireless device is within the coverage area (IC) or outside the coverage area (OOC) of the wireless node.

18. The apparatus of claim 14, wherein the pair of beams comprises: A first beam for use by the device to be transmitted to a wireless device on the first link; and A second beam for the device to receive from the wireless device on the second link.

19. The apparatus of claim 14, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to output at least one report indicating information about the candidate beam for transmission.

20. The apparatus of claim 19, wherein the information includes at least one of the following: Self-interference (SI) measurement; Cross-link interference (CLI) measurement; Signal-to-interference-and-noise ratio (SINR) measurement; Reference signal (RS) received power (RSRP) measurement; Reference Signal Strength Indicator (RSSI) measurement; Candidate beam identifier (ID); or The ID of the wireless device associated with at least one of the candidate beams.

21. The apparatus of claim 19, wherein the at least one report is at least one of the following: Periodically scheduled; Semi-persistent scheduling; Non-periodic scheduling; or The event was triggered.

22. The apparatus of claim 19, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to receive a request for at least one of the following: The at least one report; or Measurement information regarding the candidate beam.

23. The apparatus of claim 22, wherein the request indicates at least one of the following: The candidate beam pairs in the at least one report must be included; The candidate beam pairs for which measurements are to be performed; Measurement type; Beam identifier (ID); or Time and frequency resources used for measurement.

24. The apparatus of claim 19, wherein the at least one report further indicates at least one measurement performed by the wireless device.

25. The apparatus of claim 19, wherein the at least one report further indicates at least one scheduled transmission of one or more measurements associated with the apparatus.

26. The apparatus of claim 25, wherein the one or more processors are further configured to execute the executable instructions and cause the apparatus to obtain an indication of a resource associated with the at least one scheduled transmission.

27. The apparatus of claim 14, further comprising: At least one transceiver, wherein the at least one transceiver is configured to receive the signaling, and the device is configured as a user equipment (UE).

28. A method for wireless communication at a wireless node, the method comprising: Obtain at least one report indicating information about the candidate beam; Based on the information, a pair of beams is selected from the candidate beams; as well as The output indicates that at least one user equipment (UE) wants to use the pair of beams to perform full-duplex (FD) wireless communication on the first and second links for transmission.

Images