User equipment assisted bi-directional full duplex sidelink transmission

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first user equipment (UE) may send an indication to a network node that bi-directional full duplex sidelink transmission between the first UE and a second UE is feasible. The first UE may send, to the network node, sidelink scheduling information recommended for the bidirectional full duplex sidelink transmission. The first UE may receive, from the network node, downlink control information (DCI) scheduling the bidirectional full duplex sidelink transmission, the DCI based at least in part on the sidelink scheduling information and the indication indicating that the bidirectional full duplex sidelink transmission between the first UE and the second UE is feasible. The first UE may transmit the bidirectional full duplex sidelink transmission to the second UE. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 18 / 179,000, filed on March 6, 2023, entitled “USER EQUIPMENT ASSISTED BIDIRECTIONAL FULL DUPLEX SIDELINK TRANSMISSIONS,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for user equipment (UE)-assisted bidirectional full-duplex sidelink transmissions. Background Art

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

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

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables diverse UEs to communicate at the city, national, regional, and / or global levels. New Radio (NR), also referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, reducing costs, improving service, leveraging new spectrum, and integrating better with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM), also known as discrete Fourier transform-spread OFDM (DFT-s-OFDM), on the uplink. Furthermore, it supports beamforming, multiple-input, multiple-output (MIMO) antenna technology, and carrier aggregation. As demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain valuable. Summary of the Invention

[0007] In some specific implementations, an apparatus for wireless communication at a first user equipment (UE) includes: a memory; and one or more processors, the one or more processors coupled to the memory and configured to: send an indication to a network node that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; send sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node; receive downlink control information (DCI) from the network node that schedules the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; and send the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI.

[0008] In some specific implementations, an apparatus for wireless communication at a network node includes: a memory; and one or more processors coupled to the memory and configured to: receive an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; receive sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE; and send a DCI to the first UE to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

[0009] In some specific implementations, a method of wireless communication performed by a first UE includes: sending an indication to a network node indicating that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; sending sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node; receiving DCI from the network node for scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; and sending the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI.

[0010] In some specific implementations, a method of wireless communication performed by a network node includes: receiving an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; receiving sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE; and sending a DCI to the first UE to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

[0011] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a first UE, cause the first UE to: send an indication to a network node indicating that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; send sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node; receive DCI from the network node for scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; and send the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI.

[0012] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: receive an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; receive sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE; and send a DCI to the first UE scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

[0013] In some specific implementations, a first device for wireless communication includes: a component for sending an indication to a network node indicating that a bidirectional full-duplex side link transmission between the first device and a second device is feasible; a component for sending side link scheduling information recommended for the bidirectional full-duplex side link transmission to the network node; a component for receiving a DCI from the network node for scheduling the bidirectional full-duplex side link transmission via a side link grant, the DCI being based at least in part on the indication indicating that the bidirectional full-duplex side link transmission between the first device and the second device is feasible and the side link scheduling information; and a component for sending the bidirectional full-duplex side link transmission to the second device based at least in part on the DCI.

[0014] In some specific implementations, an apparatus for wireless communication includes: a component for receiving an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; a component for receiving sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE; and a component for sending a DCI to the first UE to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

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

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

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

[0018] In order that the above-described features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

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

[0022] Figure 4 is a diagram illustrating an example of full duplex in a vehicle-to-everything (V2X) system according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of side link bidirectional full-duplex communication according to the present disclosure.

[0024] Figure 6is a diagram illustrating an example of self-interference associated with a UE according to the present disclosure.

[0025] Figures 7 to 14 is a diagram illustrating an example associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0026] Figures 15 and 16 is a diagram illustrating example procedures associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0027] Figures 17 and 18 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] A network node may need to determine whether bidirectional sidelink full-duplex is feasible for two sidelink full-duplex user equipment (UEs) in order to schedule bidirectional full-duplex sidelink transmissions between the two sidelink UEs. The network node may determine the feasibility of sidelink full-duplex by, for example, collecting full-duplex performance-related metrics from each sidelink UE. However, such an approach may have a non-negligible impact on overhead and latency. In other words, determining the feasibility of sidelink full-duplex by collecting full-duplex performance-related metrics from each sidelink UE may increase signaling overhead, thereby reducing overall network performance.

[0029] In some aspects described herein, a first UE may send an indication to a network node that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible. The first UE may be capable of determining that the bidirectional full-duplex sidelink transmission is feasible based at least in part on a self-interference measurement. The first UE may send sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node. The first UE may receive a DCI from the network node that schedules the bidirectional full-duplex sidelink transmission via a sidelink grant. The DCI may be based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible. The first UE may send the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI.

[0030] In some aspects, rather than the network node determining sidelink full-duplex feasibility by collecting full-duplex performance-related metrics from each sidelink UE (which would otherwise increase signaling overhead and latency), the sidelink UEs can inform the network node of the sidelink full-duplex feasibility. The network node can use this information before scheduling bidirectional full-duplex sidelink transmissions between the two sidelink UEs. Such an approach can improve signaling overhead and latency, thereby improving overall performance for the first UE and / or the network node.

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

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

[0033] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RATs, 4G RATs, and / or post-5G (e.g., 6G) RATs.

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

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

[0036] In some examples, network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

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

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

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

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

[0041] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UEs 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UEs 120 may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablet computers, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets)), entertainment devices (e.g., music devices, video devices, and / or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system equipment, UE functionality of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0042] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0045] Devices in wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in wireless network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (and interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often (and interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0047] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term can be broadly construed to mean frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly construed to mean frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, a first UE (e.g., UE 120) may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may send an indication to a network node that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; send sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node; receive DCI from the network node scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; and send the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0049] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may receive an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; receive sidelink scheduling information from the first UE recommended for the bidirectional full-duplex sidelink transmission; and send a DCI to the first UE scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0050] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0051] Figure 2 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0052] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (Tx) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0053] At UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, perform MIMO detection on the received symbols where applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0056] On the uplink, at UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from a controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a Tx MIMO processor 266, as applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a Tx MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 7 to 18 ) any aspects of any of the methods described.

[0057] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 may include a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or Tx MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 7 to 18 ) any aspects of any of the methods described.

[0058] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with UE-assisted bidirectional full-duplex sidelink transmission, as described in more detail elsewhere herein. Figure 2 Any other component of the may perform or direct e.g. Figure 15 The process of 1500 Figure 16 1600 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 15 The process of 1500 Figure 16 The operations of process 1600 and / or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0059] In some aspects, a first UE (e.g., UE 120a) includes: means for sending an indication to a network node that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; means for sending sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node; means for receiving a DCI from the network node scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; and / or means for sending the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI. Means for the first UE to perform the operations described herein may include, for example, one or more of: the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the Tx MIMO processor 266, the controller / processor 280, or the memory 282.

[0060] In some aspects, a network node (e.g., network node 110) includes: means for receiving an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; means for receiving sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE; and / or means for sending a DCI to the first UE scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible. Means for the network node to perform the operations described herein may include, for example, one or more of: the communications manager 150, the transmit processor 220, the Tx MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0061] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the Tx MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0062] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0063] The deployment of a communication system, such as a 5G NR system, can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station, or network equipment can be implemented in a converged architecture or a disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or a single-chip base station) or a disaggregated base station. A "network entity" or "network node" can refer to a disaggregated base station or one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

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

[0066] Figure 3 FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. Decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). CU 310 may communicate with one or more DUs 330 via corresponding midhaul links (such as via an F1 interface). Each of DUs 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Each of RUs 340 may communicate with one or more UEs 120 via corresponding radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0067] Each of the units (including the CU 310, DU 330, and RU 340), as well as the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305, 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 one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via the wired transmission medium, and a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via the wireless transmission medium, or both.

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

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

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

[0071] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) 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, the CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0072] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0073] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to execute corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or through the creation of RAN management policies (such as A1 interface policies).

[0074] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0075] Figure 4 is a diagram illustrating an example 400 of full duplex in a V2X system according to the present disclosure.

[0076] like Figure 4 As shown, in V2X, the space within a vehicle or roadside unit (RSU) ensures sufficient spatial isolation between the Tx panel / array and the Rx panel / array. For example, the Tx array and Rx array on the vehicle / RSU can be separated by a certain distance to ensure sufficient spatial isolation. In both FR2 and FRx, the relatively large beamforming gain from the relatively large number of antenna elements per panel / array can reduce self-interference. Full-duplex communication (e.g., simultaneous transmission and reception) can be possible for IAB nodes, repeaters, network nodes (e.g., gNBs), and / or UEs.

[0077] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0078] Sidelink bidirectional full-duplex communication may involve at least one UE within network coverage. In a first scenario, two UEs (e.g., two sidelink UEs) may be within network coverage. Each UE may operate in Mode 1 (e.g., with sidelink resources scheduled by a network node). In a second scenario, one UE may be within network coverage, while the other UE may be outside of network coverage. The in-coverage UE may operate in Mode 1, while the out-of-coverage (OOC) UE may operate in Mode 2 (e.g., the UE may select its sidelink resources based at least in part on sensing).

[0079] Figure 5 is a diagram illustrating an example 500 of sidelink bidirectional full-duplex communication according to the present disclosure.

[0080] As shown in reference numeral 502, two UEs may be within network coverage. A first UE (e.g., full-duplex (FD) UE 1 in sidelink (SL) mode 1) may communicate with a network node via a Uu interface. A second UE (e.g., FD UE 2 in SL mode 1) may communicate with the network node via a Uu interface. The first UE may communicate directly with the second UE. In some cases, the first and second UEs may communicate with each other via a wireless channel that includes one or more reflectors.

[0081] As indicated by reference numeral 504, a UE may be out of network coverage. A first UE (e.g., FD UE 1 in SL mode 1) may communicate with a network node via a Uu interface. A second UE (e.g., FD UE 2 in SL mode 2) may not be able to communicate with the network node. The second UE may be an OOC UE. The first UE may communicate directly with the second UE. In some cases, the first and second UEs may communicate with each other via a wireless channel that includes one or more reflectors.

[0082] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0083] When two UEs are in Mode 1, bidirectional sidelink full-duplex can be achieved by the network node scheduling overlapping sidelink transmissions for the two UEs. Because the environment around each UE is different, the network node may need to track whether full-duplex relay is feasible at each UE. Full-duplex may not be feasible when reflectors near the UE cause relatively strong self-interference, or when both sidelink transmission and sidelink reception must use the same UE panel.

[0084] Figure 6 is a diagram illustrating an example 600 of self-interference associated with a UE according to the present disclosure.

[0085] like Figure 6As shown, two UEs may be within the network coverage. The first UE (e.g., FD UE 1 in SL mode 1) may communicate with the network node via the Uu interface. The second UE (e.g., FD UE 2 in SL mode 1) may communicate with the network node via the Uu interface. The first UE may communicate directly with the second UE. In some cases, the first UE and the second UE may communicate with each other via one or more reflectors. When the reflector near the UE causes relatively strong self-interference, full-duplex relay may not be feasible at the UE. For example, the reflector near the first UE may cause relatively strong self-interference to the first UE, and / or the reflector near the second UE may cause relatively strong self-interference to the second UE.

[0086] The transmission of the first UE using the first set of antennas may cause self-interference to the simultaneous reception of the first UE using the second set of antennas. The first UE may measure the self-interference power during the ongoing transmission and evaluate whether the self-interference is less than a threshold or similar metric, for example, whether the signal to interference plus noise ratio (SINR) is greater than a threshold. The first UE may measure and evaluate multiple transmit-receive beam pairs (with one or more second UEs) on different time-frequency resources and / or using different transmission parameters. Figure 6 Based at least in part on this evaluation, the first UE may determine the feasibility of full-duplex communication with the second UE and some preferred full-duplex sidelink scheduling information. A similar process may be performed by the second UE.

[0087] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0088] A network node may need to determine whether bidirectional sidelink full-duplex is feasible for two sidelink full-duplex UEs. The network node may determine the feasibility of sidelink full-duplex by, for example, collecting full-duplex performance-related metrics from each UE. However, such an approach may have a non-negligible impact on overhead and latency. In other words, determining the feasibility of sidelink full-duplex by collecting full-duplex performance-related metrics from each UE may increase signaling overhead, thereby reducing overall network performance.

[0089] In various aspects of the techniques and apparatus described herein, a first UE may send an indication to a network node that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible. The first UE may be capable of determining that the bidirectional full-duplex sidelink transmission is feasible based at least in part on a self-interference measurement. The first UE may send sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node. The first UE may receive a DCI from the network node that schedules the bidirectional full-duplex sidelink transmission via a sidelink grant. The DCI may be based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible. The first UE may send the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI.

[0090] In some aspects, rather than the network node determining sidelink full-duplex feasibility by collecting full-duplex performance-related metrics from each sidelink UE (which would otherwise increase signaling overhead and latency), the sidelink UE can inform the network node of the sidelink full-duplex feasibility. Such an approach can improve signaling overhead and latency, thereby improving overall performance of the first UE and / or the network node.

[0091] Figure 7 is a diagram illustrating an example 700 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure. Figure 7 As shown, example 700 includes communications between a first UE (e.g., UE 120a), a second UE (e.g., UE 120e), and a network node (e.g., network node 110). In some aspects, the first UE, the second UE, and the network node may be included in a wireless network, such as wireless network 100.

[0092] In some aspects, the first UE and the second UE may be in-coverage UEs.Both the first UE and the second UE may be within the coverage area of ​​the network node.

[0093] As shown in the reference numeral 702, the first UE may send an indication to the network node that a bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible. The bidirectional full-duplex sidelink transmission may be between the first UE and the second UE. The first UE may determine that the bidirectional full-duplex sidelink transmission is feasible based at least in part on self-interference measurements. The self-interference measurements may be based at least in part on dedicated reference signals or traffic transmission associated with the first UE. In some cases, the indication may indicate multiple neighboring UEs for which bidirectional full-duplex sidelink transmission is feasible. Each neighboring UE in the multiple neighboring UEs may be identified by a corresponding UE identifier. The first UE may send the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible based at least in part on a report scheduled by the network node, an autonomous report by the first UE, or a report triggered by an event.

[0094] As indicated by reference numeral 704, the first UE may send sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node. The sidelink scheduling information may indicate sidelink time-frequency resources for the sidelink grant, which may be relative information between two allocated sidelink resources associated with two sidelink grants for the first UE and the second UE. The relative information may indicate whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency. The first UE may send the sidelink scheduling information based at least in part on a report scheduled by the network node, an autonomous report by the first UE, or an event-triggered report.

[0095] In some aspects, the sidelink scheduling information may indicate non-time-frequency allocation information of sidelink resources associated with the sidelink grant. The non-time-frequency allocation information may indicate a sidelink transmit beam, a transmit configuration indicator (TCI) identifier, power information, timing information, ordering information, precoding matrix information, MIMO scheme, and / or a multiple transmit reception point (mTRP) scheme. The sidelink scheduling information may indicate candidate combinations of sidelink TCI states for both the first UE and the second UE.

[0096] In some aspects, the sidelink scheduling information may be partial sidelink scheduling information. The remaining sidelink scheduling information may be exchanged between the first UE and the second UE via inter-UE coordination signaling. The remaining sidelink scheduling information may be autonomously applied by the first UE to the bidirectional full-duplex sidelink transmission. The partial sidelink scheduling information may indicate the sidelink time-frequency resources used for the sidelink grant, and the sidelink time-frequency resources may be relative information between two allocated sidelink resources associated with two sidelink grants for the first UE and the second UE. The relative information may indicate whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency. The remaining sidelink scheduling information may indicate non-time-frequency allocation information of the sidelink resources associated with the sidelink grant. The non-time-frequency allocation information may indicate a sidelink transmit beam, a TCI identifier, power information, timing information, sorting information, precoding matrix information, a MIMO scheme, and / or an mTRP scheme. The remaining sidelink scheduling information may indicate a candidate combination of sidelink TCI states for both the first UE and the second UE, wherein the bidirectional full-duplex sidelink transmission may be sent based at least in part on the candidate combination of sidelink TCI states.

[0097] In some aspects, the sidelink scheduling information may indicate a set of full-duplex Tx beams and Rx beams associated with the first UE. The set of full-duplex Tx beams and Rx beams may indicate at least one Tx beam to at least one neighboring UE and at least one Rx beam for at least one neighboring UE. Each Tx beam or Rx beam may be identified by a reference signal identifier or a TCI identifier. The sidelink scheduling information may indicate a preferred mTRP scheme or a multi-panel Tx or Rx scheme. The sidelink scheduling information may indicate other scheduling information for each Tx beam or Rx beam per neighboring UE. The other scheduling information may indicate time-frequency resources, power information, timing information, sorting information, precoding matrix information, and / or a MIMO scheme.

[0098] As indicated by reference numeral 706, the first UE may receive DCI from the network node scheduling the bidirectional full-duplex sidelink transmission via the sidelink grant. The DCI may be based at least in part on the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible and the sidelink scheduling information. In some cases, the DCI scheduling the bidirectional full-duplex sidelink transmission via the sidelink grant may be based at least in part on the candidate combination of sidelink TCI states.

[0099] As indicated by reference numeral 708, the first UE may transmit the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI, which may be based at least in part on the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible and the sidelink scheduling information. The bidirectional full-duplex sidelink transmission may be a physical sidelink control channel (PSCCH) transmission or a physical sidelink shared channel (PSSCH) transmission.

[0100] In some aspects, the bidirectional full-duplex sidelink transmission may be a first bidirectional full-duplex sidelink transmission, and the DCI may be a first DCI. The network node may send a second DCI to the second UE (in Figure 8 ). The first UE may receive the second bidirectional full-duplex sidelink transmission from the second UE. The first bidirectional full-duplex sidelink transmission may overlap with the second bidirectional full-duplex sidelink transmission in the time domain. In some cases, the first UE may send bidirectional full-duplex sidelink feedback to the second UE based at least in part on the candidate combination of sidelink TCI states. The bidirectional full-duplex sidelink feedback may be based at least in part on the second bidirectional full-duplex sidelink transmission received from the second UE.

[0101] In some aspects, the first UE may be an in-coverage UE and the second UE may be an OOC UE. The second UE may be outside the coverage area of ​​the network node.

[0102] In some aspects, the first UE may send an indication of selected resources associated with the first bidirectional full-duplex sidelink transmission to the second UE. The first UE may receive an indication of selected resources associated with the second bidirectional full-duplex sidelink transmission from the second UE. The first UE may determine time-overlapping resources for the first bidirectional full-duplex sidelink transmission based at least in part on the selected resources associated with the first bidirectional full-duplex sidelink transmission and the selected resources associated with the second bidirectional full-duplex sidelink transmission. The first UE may apply full-duplex transmission parameters to the time-overlapping resources, wherein the full-duplex transmission parameters may indicate a TCI identifier, power information, timing information, ordering information, precoding matrix information, MIMO scheme, and / or mTRP scheme.

[0103] In some aspects, the first UE may send a request to the second UE for resources available for the second bidirectional full-duplex sidelink transmission associated with the second UE. The first UE may receive an indication of the resources available for the second bidirectional full-duplex sidelink transmission from the second UE. The first UE may send the indication of the resources available for the second bidirectional full-duplex sidelink transmission to the network node. The first DCI that schedules the first bidirectional full-duplex sidelink transmission via the sidelink grant may indicate time-overlapping resources for the first bidirectional full-duplex sidelink transmission that correspond to at least some of the resources available for the second bidirectional full-duplex sidelink transmission.

[0104] In some aspects, the first DCI scheduling the first bidirectional full-duplex sidelink transmission via the sidelink grant may indicate resources scheduled for the first bidirectional full-duplex sidelink transmission. The first UE may send an indication of the resources scheduled for the first bidirectional full-duplex sidelink transmission to the second UE as a preferred or non-preferred sidelink resource report.

[0105] In some aspects, the first UE may receive the second DCI associated with the second UE from the network node. The second DCI may indicate a relayed sidelink grant. The first UE may send the relayed sidelink grant to the second UE via sidelink control information (SCI). The second UE may send the second bidirectional full-duplex sidelink transmission to the first UE based at least in part on the relayed sidelink grant.

[0106] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0107] In some aspects, a UE (e.g., a sidelink UE) may inform a network node whether the UE is capable of performing two-way full-duplex communication with other UEs, which may enable UE-assisted sidelink two-way full-duplex communication. In other words, the UE may indicate the feasibility of the UE performing two-way full-duplex communication with other UEs. The UE may also indicate corresponding recommended sidelink scheduling information to the network node. The UE may determine full-duplex feasibility via its self-interference-related measurements, which may be based at least in part on the UE's own traffic transmissions or at least in part on dedicated reference signals.

[0108] As an example, a first UE may notify the network node that simultaneous Tx / Rx communication with a second UE is possible at the first UE, and the second UE may notify the network node that simultaneous Tx / Rx communication with the first UE is possible at the second UE. In this case, the network node may schedule time-overlapping sidelink bidirectional transmissions between the first UE and the second UE.

[0109] Figure 8 is a diagram illustrating an example 800 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0110] As indicated by reference numeral 802, two UEs may be within network coverage. A first UE (e.g., FD UE 1 in SL mode 1) may communicate with a network node via a Uu interface. A second UE (e.g., FD UE 2 in SL mode 1) may communicate with the network node via a Uu interface. The first UE may communicate directly with the second UE. In some aspects, the first UE may send an indication to the network node that full-duplex communication with the second UE is possible. The second UE may send an indication to the network node that full-duplex communication with the first UE is possible. In other words, both UEs may notify the network node of their respective bidirectional full-duplex feasibility, which may enable UE-assisted sidelink bidirectional full-duplex.

[0111] As indicated by reference numeral 804, a network node (NW) may send a first DCI to a second UE (e.g., FD SL UE 2). The network node may send a second DCI to a first UE (e.g., FD SL UE 1). The first DCI may schedule a first PSCCH or PSSCH transmission for the second UE. The second UE may schedule a second PSCCH / PSSCH transmission for the first UE. The first PSCCH / PSSCH transmission and the second PSCCH / PSSCH transmission may be simultaneous sidelink bidirectional transmissions. The network node may schedule the simultaneous sidelink bidirectional transmissions via the first DCI and the second DCI, which may be based at least in part on bidirectional sidelink full-duplex being available between the first UE and the second UE.

[0112] In some aspects, the first UE may receive the second PSCCH / PSSCH transmission from the second UE, and the first UE may send a PSSCH acknowledgement (ACK) to the second UE. The second UE may receive the first PSCCH / PSSCH transmission from the first UE, and the second UE may send a PSSCH ACK to the first UE. The first PSCCH / PSSCH transmission and the second PSCCH / PSSCH transmission may be sent simultaneously, and / or the PSSCH ACKs sent by the first UE and the second UE may be sent simultaneously. In some cases, the first PSCCH / PSSCH transmission and the second PSCCH / PSSCH transmission may be sent simultaneously, but the PSSCH ACKs may be scheduled by the network node at different times and, therefore, may not be sent simultaneously. Furthermore, the first UE may send an ACK to the network node via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) based at least in part on receiving the second DCI. The second UE may send an ACK to the network node via the PUCCH or the PUSCH based at least in part on receiving the first DCI.

[0113] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0114] In some aspects, a UE (e.g., a reporting sidelink UE) may report to a network node an indication of multiple neighboring UEs for which bidirectional full-duplex transmission is possible. Bidirectional full-duplex transmission may be possible between the reporting UE and the multiple neighboring UEs. Each neighboring UE may be identified by a corresponding Layer 2 (L2), Layer 1 (L1), or application layer UE identifier. For each reported neighboring UE, the UE may further recommend scheduling information to the network node when scheduling full-duplex bidirectional transmission between the two UEs using two corresponding sidelink grants. The scheduling information may indicate the sidelink time / frequency resources granted for each sidelink, which may be relative information between the two allocated sidelink resources. The scheduling information may indicate whether the two allocated sidelink resources are non-overlapping, partially overlapping, or fully overlapping in frequency. For non-overlapping resources, the scheduling information may indicate a required guard band between the two allocated sidelink resources. For partially overlapping resources, the scheduling information may indicate the allowed overlapping resource blocks between the two allocated sidelink resources. The scheduling information may indicate non-time / frequency allocation related information of the sidelink resources granted for each sidelink, which can ensure relatively low self-interference at least at the UE providing the scheduling information. The non-time / frequency allocation related information may indicate the sidelink Tx beam, TCI identifier, power information, timing information, rank information, precoding matrix, and / or MIMO or multi-TRP (mTRP) scheme.

[0115] In some aspects, for sidelink Tx beam selection for bidirectional full-duplex between a first UE and a second UE, the first UE may report to the network node candidate combinations of sidelink TCI states of the two UEs that are likely to cause relatively low self-interference at the first UE. For example, the first UE may report a first combination of TCI 1 for the first UE and TCI 2 for the second UE, and a second combination of TCI 3 for the first UE and TCI 4 for the second UE. The second UE may report to the network node candidate combinations of sidelink TCI states of the two UEs that are likely to cause relatively low self-interference at the second UE. For example, the second UE may report a first combination of TCI 3 for the first UE and TCI 4 for the second UE, and a second combination of TCI 5 for the first UE and TCI 6 for the second UE. The network node may receive the candidate combinations of sidelink TCI states from both the first UE and the second UE. The network node may schedule the candidate sidelink TCI combination associated with relatively low self-interference at the two UEs. For example, the network node may schedule TCI 3 for the first UE and TCI 4 for the second UE, which may be associated with relatively low self-interference at both the first UE and the second UE. Knowing that TCI 3 and TCI 4 are scheduled TCI states for bidirectional full-duplex between the first UE and the second UE, the first UE and the second UE may determine the Tx beam and Rx beam for bidirectional full-duplex between the first UE and the second UE.

[0116] Figure 9 is a diagram illustrating an example 900 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0117] As shown in reference numeral 902, a first UE (e.g., SL UE 1) may report candidate combinations of sidelink TCI states to a network node. A second UE (e.g., SL UE 2) may report candidate combinations of sidelink TCI states to the network node. For example, the candidate combinations of sidelink TCI states reported by the first UE may be {TCI 1 of UE 1 and TCI 2 of UE 2}, or {TCI 3 of UE 1 and TCI 4 of UE 2}. The candidate combinations of sidelink TCI states reported by the second UE may be {TCI 3 of UE 1 and TCI 4 of UE 2}, or {TCI 5 of UE 1 and TCI 6 of UE 2}. The network node may schedule candidate sidelink TCI combinations, such as {TCI 3 of UE 1 and TCI 4 of UE 2}, which may be based at least in part on the reports from the first UE and the second UE. Therefore, the first UE may perform sidelink transmission to the second UE using TCI 3, and the second UE may perform sidelink transmission to the first UE using TCI 4. The sidelink receive beam at the first UE may be its Rx beam corresponding to TCI 4 of the second UE, and the Rx beam at the second UE may be its Rx beam corresponding to TCI 3 of the first UE.

[0118] As indicated by reference numeral 904, a network node (NW) may send a first DCI to a second UE. The first DCI may indicate TCI 4. The second UE may send a first PSCCH / PSSCH transmission to the first UE using TCI 4, and the first PSCCH / PSSCH transmission may be based at least in part on the first DCI. The network node may send a second DCI to the first UE. The second DCI may indicate TCI 3. The first UE may send a second PSCCH / PSSCH transmission to the second UE using TCI 3, and the second PSCCH / PSSCH transmission may be based at least in part on the second DCI. In other words, the first DCI may instruct the second UE to use TCI 4 for the first PSCCH / PSSCH transmission, and the second DCI may instruct the first UE to use TCI 3 for the second PSCCH / PSSCH transmission. The first PSCCH / PSSCH transmission and the second PSCCH / PSSCH transmission may be sent simultaneously.

[0119] As indicated above, Figure 9 are provided as examples. Other examples can be found in the Figure 9 The examples described are different.

[0120] In some aspects, the network node may schedule two UEs to perform bidirectional full-duplex sidelink feedback using appropriate sidelink TCI combinations, which may be in addition to sidelink traffic (e.g., PSCCH / PSSCH traffic). For example, a first UE may transmit a physical sidelink feedback channel (PSFCH) with TCI 3, and a second UE may transmit a PSFCH with TCI 4.

[0121] Figure 10 is a diagram illustrating an example 1000 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0122] As shown in reference numeral 1002, a first UE (e.g., SL UE 1) may report candidate sidelink TCI state combinations to a network node. A second UE (e.g., SL UE 2) may report candidate sidelink TCI state combinations to the network node. The network node may schedule candidate sidelink TCI combinations, such as {TCI 3 for UE 1 and TCI 4 for UE 2}, which may be based at least in part on the reports from the first UE and the second UE. Consequently, the first UE may use TCI 3 for sidelink transmissions to the second UE, and the second UE may use TCI 4 for sidelink transmissions to the first UE.

[0123] As indicated by reference numeral 1004, a network node (NW) may transmit a first DCI to a second UE. The second UE may transmit a PSCCH / PSSCH transmission to the first UE based at least in part on the first DCI. The network node may transmit a second DCI to the first UE. The first UE may transmit a PSCCH / PSSCH transmission to the second UE based at least in part on the second DCI. The network node may schedule simultaneous sidelink feedback transmissions with full-duplex compatible TCIs, which may be based at least in part on the first DCI and the second DCI. The first UE may transmit a first PSFCH ACK transmission to the second UE using TCI 3, which may be based at least in part on the network node scheduling. The second UE may transmit a second PSFCH ACK transmission to the first UE using TCI 4, which may be based at least in part on the network node scheduling. The first and second PSFCH ACK transmissions may be transmitted simultaneously. Additionally, the first UE may send an ACK to the network node via the PUCCH based at least in part on receiving the second DCI.The second UE may send an ACK to the network node via the PUCCH based at least in part on receiving the first DCI.

[0124] As indicated above, Figure 10are provided as examples. Other examples can be found in the Figure 10 The examples described are different.

[0125] In some aspects, a UE may report basic sidelink scheduling information to a network node, rather than reporting complete scheduling information to the network node. In other words, each UE may report only the basic sidelink scheduling information to the network node, rather than reporting all sidelink scheduling information. The UE may coordinate with neighboring UEs to obtain remaining sidelink scheduling information, which may be autonomously applied by the two UEs when scheduling bidirectional full-duplex between the two UEs. This remaining sidelink scheduling information may not be reported to the network node, but may be autonomously applied by the UE itself. The basic sidelink scheduling information may include neighboring UE identifiers, which may be associated with neighboring UEs for which bidirectional full-duplex is possible. The basic sidelink scheduling information may include recommended time / frequency resources for transmission by the two UEs. The network node may schedule full-duplex sidelink time / frequency resources based at least in part on the basic sidelink scheduling information. The remaining sidelink scheduling information may include the UE's Tx beam, TCI identifier, power information, timing information, rank information, precoding matrix, MIMO / mTRP scheme, and / or other sidelink scheduling parameters. The two UEs may coordinate to exchange the remaining sidelink scheduling information via a sidelink channel (e.g., in half-duplex mode). The two UEs may exchange inter-UE coordination signaling to indicate the remaining sidelink scheduling information to each other. In this example, the network node may allocate sidelink time / frequency resources, while other non-time / frequency allocation-related scheduling information may be determined by the transmitting UE.

[0126] In some aspects, for sidelink Tx beam coordination between two UEs, a first UE may notify a second UE of possible sidelink TCI state combinations for full-duplex communication at the first UE. For example, the first UE may report a first combination of TCI 1 for the first UE and TCI 2 for the second UE, and a second combination of TCI 3 for the first UE and TCI 4 for the second UE. Based at least in part on the reports from the first UE, the second UE may report possible sidelink TCI state combinations for both the second UE and the first UE. For example, the second UE may report a combination of TCI 3 for the first UE and TCI 4 for the second UE. When scheduling full-duplex communication between the first UE and the second UE, the network node may indicate in the DCI of the first UE (or the second UE) that the corresponding sidelink grant is intended for bidirectional full-duplex communication with the second UE (or the first UE). Based at least in part on the indication, both the first UE and the second UE may apply a coordinated TCI combination (eg, a combination of TCI 3 for the first UE and TCI 4 for the second UE). The indication in the DCI may indicate an expected neighbor UE identifier for bidirectional full-duplex.

[0127] Figure 11 is a diagram illustrating an example 1100 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0128] As shown in reference numeral 1102, a first UE (e.g., SL UE 1) may exchange inter-UE coordination for a sidelink full-duplex beam with a second UE (e.g., SL UE 2). For example, the first UE may notify the second UE of a combination of sidelink TCI states that are feasible for full-duplex at the first UE. For example, the first UE may report {TCI 1 for UE 1 and TCI 2 for UE 2}, or {TCI 3 for UE 1 and TCI 4 for UE 2}. The second UE may notify the first UE of a combination of sidelink TCI states that are feasible at both the second UE and the first UE, and the combination of sidelink TCI states may be based at least in part on the report from the first UE. For example, the second UE may report {TCI 3 for UE 1 + TCI 4 for UE 2}.

[0129] As indicated by reference numeral 1104, a network node (NW) may send a first DCI to a second UE. The first DCI may indicate that a corresponding sidelink grant is intended for bidirectional full-duplex communication with the first UE. The network node may send a second DCI to the first UE. The second DCI may indicate that a corresponding sidelink grant is intended for bidirectional full-duplex communication with the second UE. The first UE may perform a first PSCCH / PSSCH transmission, which may be based at least in part on the second DCI. The second UE may perform a second PSCCH / PSSCH transmission, which may be based at least in part on the first DCI. The first UE may perform the first PSCCH / PSSCH transmission using TCI 3, and the second UE may perform the second PSCCH / PSSCH transmission using TCI 4, which may be based at least in part on inter-UE coordination for sidelink full-duplex beams exchanged between the first UE and the second UE. In addition to beams, inter-UE coordination may also include other types of sidelink scheduling parameters ( Figure 11 ), such as parameters related to power, timing, rank, precoding matrix and / or MIMO / mTRP scheme.

[0130] As indicated above, Figure 11 are provided as examples. Other examples can be found in the Figure 11 The examples described are different.

[0131] In some aspects, a UE's reporting of feasible full-duplex bidirectional Tx / Rx beams to a neighboring UE can be generalized to reporting at least one set of full-duplex beams having at least one Tx beam to at least one neighboring UE and at least one Rx beam for at least one neighboring UE. For example, a first UE can report to a network node that the first UE is capable of simultaneously receiving from a second UE using Rx beam 1 and Rx beam 2, simultaneously transmitting to a third UE using Tx beam 1 and Tx beam 2, and simultaneously receiving from a fourth UE using Rx beam 3. Each Tx beam and / or Rx beam can be identified by a reference signal identifier or TCI identifier, which is transmitted or indicated by either of the two UEs participating in sidelink communication with each other. For multiple Tx beams or Rx beams associated with a neighboring UE, the first UE can report to the network node a preferred multi-TRP or multi-panel Tx or Rx scheme, such as mTRP transmission or reception based on spatial division multiplexing (SDM) or frequency division multiplexing (FDM). The first UE may also indicate to the network node recommended other scheduling information per Tx beam / Rx beam and per neighboring UE. The other scheduling information may indicate time / frequency resources, such as non-overlapping resources in the frequency domain, partially overlapping resources in the frequency domain, or fully overlapping resources in the frequency domain. The other scheduling information may indicate power information, timing information, rank information, precoding matrix, and / or MIMO / mTRP scheme.

[0132] Figure 12 is a diagram illustrating an example 1200 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0133] like Figure 12 As shown, a first UE may send a report to a network node indicating a set of full-duplex Tx beams / Rx beams at the first UE. The report may indicate Rx beam 1 and Rx beam 2 for a second UE. The report may indicate Tx beam 1 and Tx beam 2 for a third UE. The report may indicate Rx beam 3 for a fourth UE. The first UE may indicate, via the report, that it can simultaneously use Rx beam 1, Rx beam 2, Rx beam 3, Tx beam 1, and Tx beam 2 to communicate with the second UE, the third UE, and the fourth UE, respectively.

[0134] As indicated above, Figure 12 are provided as examples. Other examples can be found in the Figure 12 The examples described are different.

[0135] In some aspects, a UE may report UE assistance information associated with its bidirectional full-duplex scheduling to a network node. This UE assistance information may enable UE-assisted sidelink bidirectional full-duplex. For example, the UE assistance information may indicate the feasibility of the UE performing bidirectional full-duplex communication with other UEs. In some aspects, the UE may indicate this UE assistance information using reports scheduled by the network node. The reports scheduled by the network node may be periodic, semi-persistent, or aperiodic reports. The reports scheduled by the network node may be based at least in part on a channel state information (CSI) reporting framework. In some aspects, the UE may indicate this UE assistance information using UE autonomous reporting. When the UE identifies a set of full-duplex feasible beams / UEs, the UE may send the UE autonomous report. In some aspects, the UE may indicate this UE assistance information using event-triggered reporting, which may be carried in uplink control information (UCI) or a MAC control element (MAC-CE). The events and / or thresholds associated with the event-triggered reporting may be configurable by the network node. For example, a report triggered by this event may be triggered when the self-interference caused by at least one sidelink transmission on at least one sidelink reception is less than a threshold. As another example, a report triggered by this event may be triggered when the SINR of a sidelink reception, taking into account the self-interference from a sidelink transmission, is greater than a threshold. Priority may be defined for UCI or MAC-CEs carrying full-duplex relay assistance when multiplexed with other UCI or MAC-CE types.

[0136] In some aspects, in a second scenario, a first UE may be within network coverage, while a second UE may be out of network coverage. The first UE and the second UE may be sidelink UEs. The first UE may operate in Mode 1, while the second UE (which may be an OOC UE) may operate in Mode 2 (e.g., the second UE may select its sidelink resources based at least in part on sensing). The second UE may operate in Mode 2 to select time / frequency resources based at least in part on its own sensing. When the first UE operates in Mode 1, the time / frequency resources of the first UE may be scheduled by the network node. In this second scenario, the two UEs may determine that full-duplex bidirectional transmission between them is feasible (e.g., by utilizing inter-UE full-duplex sidelink coordination). Even when one of the two UEs is OOC, the two UEs may need to coordinate time-overlapping resources for bidirectional sidelink transmissions with corresponding full-duplex optimized Tx parameters (e.g., beams). Furthermore, even when one of the two UEs may be OOC, the network node may need to schedule overlapping sidelink transmissions for both UEs.

[0137] In some aspects, two UEs may identify time-overlapping resources and use full-duplex-optimized Tx parameters for these time-overlapping resources. These full-duplex-optimized Tx parameters may include Tx beams, power information, timing information, ordering information, precoding matrices, and / or MIMO / mTRP schemes. In a first option, the two UEs may exchange information regarding selected resources planned for sidelink transmissions, and based at least in part on this information, the two UEs may be able to identify time-overlapping resource opportunities. The UEs may then use full-duplex-optimized Tx parameters for these time-overlapping resources. These selected resources may or may not be reserved over the air by the two UEs. In a second option, a first UE (e.g., an in-coverage UE) may request and forward to a network node an indication of resources selected by a second UE (e.g., an OOC UE). The network node may schedule the first UE's resources to overlap with the second UE's selected resources to maximize spectral efficiency. After the network node selects the overlapping resources, the first UE may notify the second UE of the first UE's overlapping resources. The UEs may then use full-duplex optimized Tx parameters for these temporally overlapping resources. In a third option, a first UE (e.g., the in-coverage UE) may forward an indication of the resources selected by the network node to a second UE (e.g., the OOC UE). The second UE may select its resources to overlap with the first UE's resources to maximize spectrum efficiency. After the second UE selects its overlapping resources, the second UE may notify the first UE of the overlapping resources. The UEs may then use full-duplex optimized Tx parameters for these temporally overlapping resources.

[0138] Figure 13 is a diagram illustrating an example 1300 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0139] like Figure 13 As shown, a first UE (e.g., an in-coverage UE) may be associated with a sidelink resource selected by a network node. A second UE (e.g., an OOC UE) may be associated with a sidelink resource selected by its sensing. The sidelink resource associated with the first UE may be associated with multiple opportunities. The sidelink resource associated with the second UE may be associated with multiple opportunities. Both the first UE and the second UE may need to use a full-duplex beam on overlapping resources. For example, the second opportunity and the fourth opportunity of the first UE and the second UE may correspond to overlapping resources, while the first opportunity and the third opportunity of the first UE and the second UE may not correspond to overlapping resources.

[0140] As indicated above, Figure 13 are provided as examples. Other examples can be found in the Figure 13 The examples described are different.

[0141] In some aspects, overlapping full-duplex bidirectional sidelink transmissions can be scheduled by a single network node, even when one of the two UEs is out-of-coverage. The network node can send a sidelink grant relayed by a first UE (e.g., an in-coverage UE) to a second UE (e.g., an out-of-coverage UE), and the sidelink resources for the first UE can overlap with the sidelink resources of the sidelink grant sent for the first UE. The second UE can operate in Mode 1, in which the second UE can receive the relayed sidelink grant from the network node. In other words, the second UE may not receive the sidelink grant directly from the network node, but rather may receive the sidelink grant via the first UE. At least in the case of periodic traffic, both sidelink grants can be scheduled with semi-persistent resources to reduce scheduling overhead.

[0142] Figure 14 is a diagram illustrating an example 1400 associated with UE-assisted bidirectional full-duplex sidelink transmission according to the present disclosure.

[0143] like Figure 14 As shown, a network node (NW) may send a first DCI to a first UE (e.g., SL UE1 in mode 1 and in coverage). The first DCI may indicate a sidelink grant for the relay. The first UE may send the sidelink grant for the relay to a second UE (e.g., SL UE 2 in mode 1' and in OOC). Mode 1' may be a mode in which the network node may be able to control some resource allocations for the OOC UE through the relay UE. For example, the first UE may send an SCI indicating a sidelink grant for the relay for the second UE to the second UE. The network node may send a second DCI to the first UE. The second DCI may indicate a sidelink grant for the first UE. The first UE may perform a first PSCCH / PSSCH transmission, which may be based at least in part on the second DCI with the sidelink grant. The second UE may perform a second PSCCH / PSSCH transmission, which may be based at least in part on the first DCI indicating the sidelink grant for the relay. The first PSCCH / PSSCH transmission and the second PSCCH / PSSCH transmission may be simultaneous. In other words, the sidelink grant for the relay indicated by the first UE and the sidelink grant indicated by the second DCI may correspond to overlapping sidelink resources.

[0144] As indicated above, Figure 14 are provided as examples. Other examples can be found in the Figure 14 The examples described are different.

[0145] Figure 15is a diagram illustrating an example process 1500 performed, for example, by a first UE in accordance with the present disclosure. Example process 1500 is an example in which the first UE (eg, UE 120a) performs operations associated with UE-assisted bidirectional full-duplex sidelink transmission.

[0146] like Figure 15 As shown, in some aspects, process 1500 may include sending an indication to a network node that bidirectional full-duplex sidelink transmission between a first UE and a second UE is possible (block 1510). For example, the first UE (e.g., using Figure 17 The transmitting component 1704 and / or the communication manager 1706 depicted in FIG. 1 may transmit an indication to the network node that bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible, as described above.

[0147] like Figure 15 As further shown, in some aspects, process 1500 may include: sending sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node (block 1520). For example, the first UE (eg, using Figure 17 The transmitting component 1704 and / or the communication manager 1706 depicted in FIG. 1 may transmit sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node, as described above.

[0148] like Figure 15 As further shown, in some aspects, process 1500 may include receiving DCI from the network node scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible (block 1530). For example, the first UE (e.g., using Figure 17 The receiving component 1702 and / or the communication manager 1706 depicted in the figure may receive a DCI from the network node to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible, as described above.

[0149] like Figure 15 As further shown, in some aspects, process 1500 may include: transmitting the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI (block 1540). For example, the first UE (e.g., using Figure 17 The transmitting component 1704 and / or the communication manager 1706 depicted in FIG. 1 may transmit the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI, as described above.

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

[0151] In a first aspect, process 1500 includes determining that bidirectional full-duplex sidelink transmission is feasible based at least in part on a self-interference measurement based at least in part on a dedicated reference signal or traffic transmission associated with the first UE.

[0152] In a second aspect, alone or in combination with the first aspect, the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and the DCI is a first DCI, the second DCI schedules a second bidirectional full-duplex side link transmission between the second UE and the first UE, and the first bidirectional full-duplex side link transmission overlaps with the second bidirectional full-duplex side link transmission in the time domain.

[0153] In a third aspect, alone or in combination with one or more of the first and second aspects, the bidirectional full-duplex sidelink transmission is a PSCCH transmission or a PSSCH transmission.

[0154] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication indicates a plurality of neighboring UEs for which bidirectional full-duplex sidelink transmission is feasible, and each of the plurality of neighboring UEs is identified by a corresponding UE identifier.

[0155] In a fifth aspect, alone or in combination with one or more aspects from the first to the fourth aspects, the sidelink scheduling information indicates the sidelink time-frequency resources used for the sidelink grant, the sidelink scheduling information indicates relative information between two allocated sidelink resources associated with the two sidelink grants for the first UE and the second UE, and the sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or fully overlap in frequency.

[0156] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a TCI identifier, power information, timing information, sorting information, pre-decoding matrix information, a MIMO scheme, or an mTRP scheme.

[0157] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the sidelink scheduling information indicates a candidate combination of sidelink TCI states of both the first UE and the second UE.

[0158] In an eighth aspect, alone or in combination with one or more of aspects 1 to 7, the DCI sent via the sidelink grant to schedule the bidirectional full-duplex sidelink is based at least in part on the candidate combination of sidelink TCI states.

[0159] In a ninth aspect, alone or in combination with one or more of aspects 1 to 8, process 1500 includes sending bidirectional full-duplex sidelink feedback to the second UE based at least in part on the candidate combination of sidelink TCI states.

[0160] In the tenth aspect, alone or in combination with one or more aspects from the first to the ninth aspect, the side link scheduling information is partial side link scheduling information, the remaining side link scheduling information is exchanged between the first UE and the second UE via inter-UE coordination signaling, and the remaining side link scheduling information is autonomously applied by the first UE to the bidirectional full-duplex side link transmission.

[0161] In the eleventh aspect, alone or in combination with one or more aspects from the first to the tenth aspect, the portion of the side link scheduling information indicates the side link time-frequency resources used for the side link grant, the portion of the side link scheduling information indicates relative information between two allocated side link resources associated with the two side link grants for the first UE and the second UE, and the portion of the side link scheduling information indicates whether the two allocated side link resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency; and the remaining side link scheduling information indicates non-time-frequency allocation information of the side link resources associated with the side link grant, and the non-time-frequency allocation information indicates one or more of the following: a side link transmit beam, a TCI identifier, power information, timing information, sorting information, pre-decoding matrix information, a MIMO scheme, or an mTRP scheme.

[0162] In the twelfth aspect, alone or in combination with one or more aspects of the first to eleventh aspects, the remaining sidelink scheduling information indicates a candidate combination of sidelink TCI states of both the first UE and the second UE, and the bidirectional full-duplex sidelink transmission is sent at least in part based on the candidate combination of sidelink TCI states.

[0163] In the thirteenth aspect, alone or in combination with one or more aspects of the first to twelfth aspects, the sidelink scheduling information indicates a set of full-duplex transmit and receive beams associated with the first UE, the set of full-duplex transmit and receive beams indicating at least one transmit beam to at least one neighboring UE and at least one receive beam for at least one neighboring UE, and each transmit beam or receive beam is identified by a reference signal identifier or a TCI identifier.

[0164] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the sidelink scheduling information indicates a preferred mTRP scheme or a multi-panel transmission or reception scheme.

[0165] In the fifteenth aspect, alone or in combination with one or more aspects of the first to fourteenth aspects, the sidelink scheduling information indicates other scheduling information for each transmit beam or receive beam of each adjacent UE, and the other scheduling information indicates one or more of the following: time-frequency resources, power information, timing information, sorting information, precoding matrix information or MIMO scheme.

[0166] In the sixteenth aspect, alone or in combination with one or more of aspects one to fifteen, process 1500 includes sending one or more of the indication or the side link scheduling information indicating that the bidirectional full-duplex side link transmission between the first UE and the second UE is feasible based at least in part on one of the following: a report scheduled by a network node, an autonomous report by the first UE, or a report triggered by an event.

[0167] In the seventeenth aspect, alone or in combination with one or more aspects of the first to sixteenth aspects, the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and process 1500 includes: sending an indication of selected resources associated with the first bidirectional full-duplex side link transmission to the second UE; receiving an indication of selected resources associated with the second bidirectional full-duplex side link transmission from the second UE; determining time overlapping resources for the first bidirectional full-duplex side link transmission based at least in part on the selected resources associated with the first bidirectional full-duplex side link transmission and the selected resources associated with the second bidirectional full-duplex side link transmission; and applying full-duplex transmission parameters to the time overlapping resources, the full-duplex transmission parameters indicating one or more of the following: a TCI identifier, power information, timing information, sorting information, pre-decoding matrix information, a MIMO scheme, or an mTRP scheme.

[0168] In the eighteenth aspect, alone or in combination with one or more of aspects one to seventeen, the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and process 1500 includes: sending a request for resources available for a second bidirectional full-duplex side link transmission associated with the second UE to the second UE; receiving an indication of the resources available for the second bidirectional full-duplex side link transmission from the second UE; and sending the indication of the resources available for the second bidirectional full-duplex side link transmission to the network node, and scheduling the first bidirectional full-duplex side link transmission via the side link grant, the DCI indication for the first bidirectional full-duplex side link transmission corresponding to time overlapping resources corresponding to at least some of the resources available for the second bidirectional full-duplex side link transmission.

[0169] In the nineteenth aspect, alone or in combination with one or more aspects of the first to eighteenth aspects, the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, the DCI indication for scheduling the first bidirectional full-duplex side link transmission via the side link grant indicates the resources scheduled for the first bidirectional full-duplex side link transmission, and process 1500 includes: sending an indication of the resources scheduled for the first bidirectional full-duplex side link transmission to the second UE as a preferred or non-preferred side link resource report.

[0170] In aspect 20, alone or in combination with one or more of aspects 1 to 19, the DCI is a first DCI and the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission, and process 1500 includes: receiving a second DCI associated with the second UE from the network node, the second DCI indicating a sidelink grant for the relay of the second UE; sending the sidelink grant of the relay to the second UE via the SCI; and receiving a second bidirectional full-duplex sidelink transmission from the second UE based at least in part on the sidelink grant of the relay.

[0171] In aspect 21, alone or in combination with one or more aspects from aspect 1 to aspect 20, the first UE and the second UE are in-coverage UEs, or the first UE is an in-coverage UE and the second UE is an OOC UE.

[0172] although Figure 15 Example blocks of process 1500 are shown, but in some aspects, process 1500 may include Figure 15 1500. In some embodiments, the process 1500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1500 may be executed in parallel.

[0173] Figure 16is a diagram illustrating an example process 1600, for example, performed by a network node, in accordance with the present disclosure. The example process 1600 is an example in which the network node (eg, network node 110) performs operations associated with UE-assisted bidirectional full-duplex sidelink transmission.

[0174] like Figure 16 As shown, in some aspects, process 1600 may include receiving an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is possible (block 1610). For example, the network node (e.g., using Figure 18 The receiving component 1802 and / or the communication manager 1806 depicted in FIG. 1 may receive an indication from a first UE that bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible, as described above.

[0175] like Figure 16 As further shown, in some aspects, process 1600 may include receiving, from the first UE, sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission (block 1620). For example, the network node (e.g., using Figure 18 The receiving component 1802 and / or the communication manager 1806 depicted in FIG. 1 can receive sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE, as described above.

[0176] like Figure 16 As further shown, in some aspects, process 1600 may include sending a DCI to the first UE scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible (block 1630). For example, the network node (e.g., using Figure 18 The transmitting component 1804 and / or the communication manager 1806 depicted in the figure may send a DCI to the first UE to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible, as described above.

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

[0178] In a first aspect, the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible based at least in part on self-interference measurements.

[0179] In a second aspect, alone or in combination with the first aspect, the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and the DCI is a first DCI, and the process further includes: sending a second DCI to the second UE to schedule a second bidirectional full-duplex side link transmission between the second UE and the first UE, and the first bidirectional full-duplex side link transmission overlaps with the second bidirectional full-duplex side link transmission in the time domain.

[0180] In a third aspect, alone or in combination with one or more of the first and second aspects, the bidirectional full-duplex sidelink transmission is a PSCCH transmission or a PSSCH transmission.

[0181] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication indicates a plurality of neighboring UEs for which bidirectional full-duplex sidelink transmission is feasible, and each of the plurality of neighboring UEs is identified by a corresponding UE identifier.

[0182] In a fifth aspect, alone or in combination with one or more aspects from the first to the fourth aspects, the sidelink scheduling information indicates the sidelink time-frequency resources used for the sidelink grant, the sidelink scheduling information indicates relative information between two allocated sidelink resources associated with the two sidelink grants for the first UE and the second UE, and the sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or fully overlap in frequency.

[0183] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a TCI identifier, power information, timing information, sorting information, pre-decoding matrix information, a MIMO scheme, or an mTRP scheme.

[0184] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the sidelink scheduling information indicates a candidate combination of sidelink TCI states of both the first UE and the second UE.

[0185] In the eighth aspect, alone or in combination with one or more aspects from the first to the seventh aspect, the side link scheduling information is partial side link scheduling information, the remaining side link scheduling information is exchanged between the first UE and the second UE via inter-UE coordination signaling, and the remaining side link scheduling information is autonomously applied by the first UE to the bidirectional full-duplex side link transmission.

[0186] In the ninth aspect, alone or in combination with one or more aspects from the first to the eighth aspects, the portion of the sidelink scheduling information indicates the sidelink time-frequency resources used for the sidelink grant, the portion of the sidelink scheduling information indicates relative information between two allocated sidelink resources associated with the two sidelink grants for the first UE and the second UE, and the portion of the sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency; and the remaining sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a TCI identifier, power information, timing information, sorting information, pre-decoding matrix information, a MIMO scheme, or an mTRP scheme.

[0187] In the tenth aspect, alone or in combination with one or more aspects of the first to ninth aspects, the remaining sidelink scheduling information indicates a candidate combination of sidelink TCI states of both the first UE and the second UE, and the bidirectional full-duplex sidelink transmission is sent at least in part based on the candidate combination of sidelink TCI states.

[0188] In the eleventh aspect, alone or in combination with one or more aspects from the first to the tenth aspect, the sidelink scheduling information indicates a set of full-duplex transmit and receive beams associated with the first UE, the set of full-duplex transmit and receive beams indicating at least one transmit beam to at least one neighboring UE and at least one receive beam for at least one neighboring UE, and each transmit beam or receive beam is identified by a reference signal identifier or a TCI identifier.

[0189] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the sidelink scheduling information indicates a preferred mTRP scheme or a multi-panel transmission or reception scheme.

[0190] In the thirteenth aspect, alone or in combination with one or more aspects of the first to twelfth aspects, the sidelink scheduling information indicates other scheduling information for each transmit beam or receive beam of each adjacent UE, and the other scheduling information indicates one or more of the following: time-frequency resources, power information, timing information, sorting information, precoding matrix information or MIMO scheme.

[0191] In the fourteenth aspect, alone or in combination with one or more of aspects one to thirteen, the DCI is a first DCI, and process 1600 includes sending a second DCI associated with the second UE to the first UE, the second DCI indicating a sidelink grant for the relay for the second UE.

[0192] In the fifteenth aspect, alone or in combination with one or more aspects from the first to the fourteenth aspects, the first UE and the second UE are in-coverage UEs, or the first UE is an in-coverage UE and the second UE is an OOC UE.

[0193] although Figure 16 Example blocks of process 1600 are shown, but in some aspects, process 1600 may include Figure 16 1600. In some embodiments, the process 1600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1600 may be executed in parallel.

[0194] Figure 17 1 is a diagram of an example apparatus 1700 for wireless communication according to the present disclosure. Apparatus 1700 may be a first UE, or the first UE may include apparatus 1700. In some aspects, apparatus 1700 includes a receiving component 1702, a sending component 1704, and / or a communication manager 1706, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1706 is in conjunction with Figure 1 The described communication manager 140. As shown, the device 1700 can communicate with another device 1708, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1702 and a sending component 1704.

[0195] In some aspects, the apparatus 1700 may be configured to perform the Figures 7 to 14 Additionally or alternatively, the apparatus 1700 may be configured to perform one or more of the processes described herein, such as Figure 15 In some aspects, the apparatus 1700 and / or Figure 17 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Figure 17 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0196] The receiving component 1702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1708. The receiving component 1702 may provide the received communications to one or more other components of the device 1700. In some aspects, the receiving component 1702 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1700. In some aspects, the receiving component 1702 may include a combination of Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described first UE.

[0197] The transmitting component 1704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1708. In some aspects, one or more other components of the apparatus 1700 may generate communications and may provide the generated communications to the transmitting component 1704 for transmission to the apparatus 1708. In some aspects, the transmitting component 1704 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1708. In some aspects, the transmitting component 1704 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described first UE. In some aspects, the transmitting component 1704 can be co-located with the receiving component 1702 in a transceiver.

[0198] The communications manager 1706 can support the operation of the receiving component 1702 and / or the sending component 1704. For example, the communications manager 1706 can receive information associated with configuring the receipt of communications by the receiving component 1702 and / or the sending of communications by the sending component 1704. Additionally or alternatively, the communications manager 1706 can generate and / or provide control information to the receiving component 1702 and / or the sending component 1704 to control the receipt and / or sending of communications.

[0199] The transmitting component 1704 may transmit an indication to a network node that a bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible. The transmitting component 1704 may transmit sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node. The receiving component 1702 may receive a DCI from the network node scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible. The transmitting component 1704 may transmit the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI.

[0200] The communication manager 1706 may determine that the bidirectional full-duplex sidelink transmission is feasible based at least in part on a self-interference measurement, the self-interference measurement being based at least in part on a dedicated reference signal or traffic transmission associated with the first UE. The transmitting component 1704 may transmit bidirectional full-duplex sidelink feedback to the second UE based at least in part on a candidate combination of sidelink TCI states. The transmitting component 1704 may transmit one or more of the indication that the bidirectional full-duplex sidelink transmission is feasible between the first UE and the second UE or the sidelink scheduling information based at least in part on one of: a report scheduled by a network node, an autonomous report by the first UE, or a report triggered by an event.

[0201] The transmitting component 1704 may transmit an indication of selected resources associated with a first bidirectional full-duplex sidelink transmission to the first UE. The receiving component 1702 may receive an indication of selected resources associated with a second bidirectional full-duplex sidelink transmission from the second UE. The communication manager 1706 may determine time-overlapping resources for the first bidirectional full-duplex sidelink transmission based at least in part on the selected resources associated with the first bidirectional full-duplex sidelink transmission and the selected resources associated with the second bidirectional full-duplex sidelink transmission. The communication manager 1706 may apply full-duplex transmission parameters to the time-overlapping resources, the full-duplex transmission parameters indicating one or more of: a TCI identifier, power information, timing information, ordering information, precoding matrix information, a MIMO scheme, or an mTRP scheme.

[0202] The transmitting component 1704 may transmit a request to the second UE for resources available for a second bidirectional full-duplex sidelink transmission associated with the second UE. The receiving component 1702 may receive an indication of the resources available for the second bidirectional full-duplex sidelink transmission from the second UE. The transmitting component 1704 may transmit the indication of the resources available for the second bidirectional full-duplex sidelink transmission to the network node, the DCI for scheduling the first bidirectional full-duplex sidelink transmission via the sidelink grant indicating time-overlapping resources for the first bidirectional full-duplex sidelink transmission corresponding to at least some of the resources available for the second bidirectional full-duplex sidelink transmission. The transmitting component 1704 may transmit the indication of the resources scheduled for the first bidirectional full-duplex sidelink transmission as a preferred or non-preferred sidelink resource report to the second UE.

[0203] Receiving component 1702 may receive, from the network node, a second DCI associated with the second UE, the second DCI indicating a relayed sidelink grant for the second UE. Transmitting component 1704 may transmit the relayed sidelink grant to the second UE via an SCI. Receiving component 1702 may receive a second bidirectional full-duplex sidelink transmission from the second UE based at least in part on the relayed sidelink grant.

[0204] Figure 17 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 17 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 17 Two or more components shown may be implemented in a single component, or Figure 17 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 17 The illustrated set (one or more) of components executable is described as being comprised of Figure 17 Another group of components is shown performing one or more functions.

[0205] Figure 18 1 is a diagram of an example apparatus 1800 for wireless communication according to the present disclosure. Apparatus 1800 may be a network node, or a network node may include apparatus 1800. In some aspects, apparatus 1800 includes a receiving component 1802, a sending component 1804, and / or a communication manager 1806, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1806 is a communication manager that is configured to communicate with one another. Figure 1The described communication manager 150. As shown, the device 1800 can communicate with another device 1808, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1802 and a sending component 1804.

[0206] In some aspects, the apparatus 1800 may be configured to perform the Figures 7 to 14 Additionally or alternatively, the apparatus 1800 may be configured to perform one or more of the processes described herein, such as Figure 16 The process 1600. In some aspects, Figure 18 The device 1800 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the described network node. Figure 18 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0207] The receiving component 1802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1808. The receiving component 1802 may provide the received communications to one or more other components of the apparatus 1800. In some aspects, the receiving component 1802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1800. In some aspects, the receiving component 1802 may include a combination of Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes. In some aspects, the receiving component 1802 and / or the transmitting component 1804 may include or be included in a network interface. The network interface may be configured to obtain and / or output signals for the apparatus 1800 via one or more communication links (such as a backhaul link, a midhaul link, and / or a fronthaul link).

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

[0209] The communications manager 1806 can support the operation of the receiving component 1802 and / or the sending component 1804. For example, the communications manager 1806 can receive information associated with configuring the receipt of communications by the receiving component 1802 and / or the sending of communications by the sending component 1804. Additionally or alternatively, the communications manager 1806 can generate and / or provide control information to the receiving component 1802 and / or the sending component 1804 to control the receipt and / or sending of communications.

[0210] Receiving component 1802 can receive an indication from a first UE that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible. Receiving component 1802 can receive sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE. Transmitting component 1804 can transmit a DCI to the first UE scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

[0211] The transmitting component 1804 may transmit, to the second UE, a second DCI scheduling a second bidirectional full-duplex sidelink transmission between the second UE and the first UE, wherein the first bidirectional full-duplex sidelink transmission overlaps with the second bidirectional full-duplex sidelink transmission in the time domain. The transmitting component 1804 may transmit, to the first UE, a second DCI associated with the second UE, the second DCI indicating a sidelink grant for the relay of the second UE.

[0212] Figure 18 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 18The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 18 Two or more components shown may be implemented in a single component, or Figure 18 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 18 The illustrated set (one or more) of components executable is described as being comprised of Figure 18 Another group of components is shown performing one or more functions.

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

[0214] Aspect 1: A method of wireless communication performed by a first user equipment (UE), the method comprising: sending an indication to a network node indicating that a bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; sending sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission to the network node; receiving downlink control information (DCI) from the network node for scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication indicating that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; and sending the bidirectional full-duplex sidelink transmission to the second UE based at least in part on the DCI.

[0215] Aspect 2: According to the method of aspect 1, the method also includes: determining that the bidirectional full-duplex sidelink transmission is feasible based at least in part on self-interference measurement, and the self-interference measurement is at least in part based on a dedicated reference signal or a service transmission associated with the first UE.

[0216] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and the DCI is a first DCI, the second DCI schedules a second bidirectional full-duplex side link transmission between the second UE and the first UE, and the first bidirectional full-duplex side link transmission overlaps with the second bidirectional full-duplex side link transmission in the time domain.

[0217] Aspect 4: The method according to any one of aspects 1 to 3, wherein the bidirectional full-duplex sidelink transmission is a physical sidelink control channel transmission or a physical sidelink shared channel transmission.

[0218] Aspect 5: The method according to any one of aspects 1 to 4, wherein the indication indicates a plurality of neighboring UEs for which bidirectional full-duplex sidelink transmission is feasible, and each of the plurality of neighboring UEs is identified by a corresponding UE identifier.

[0219] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the sidelink scheduling information indicates a sidelink time-frequency resource for the sidelink grant, the sidelink scheduling information indicates relative information between two allocated sidelink resources associated with two sidelink grants for the first UE and the second UE, and the sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency.

[0220] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a transmit configuration indicator identifier, power information, timing information, sorting information, pre-decoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit-receive point scheme.

[0221] Aspect 8: The method according to any one of aspects 1 to 7, wherein the sidelink scheduling information indicates candidate combinations of sidelink transmission configuration indicator (TCI) states of both the first UE and the second UE.

[0222] Aspect 9: The method of aspect 8, wherein the DCI for scheduling the bidirectional full-duplex sidelink transmission via the sidelink grant is based at least in part on the candidate combination of sidelink TCI states.

[0223] Aspect 10: The method according to aspect 8 further includes: sending bidirectional full-duplex sidelink feedback to the second UE based at least in part on the candidate combination of sidelink TCI states.

[0224] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the sidelink scheduling information is partial sidelink scheduling information, the remaining sidelink scheduling information is exchanged between the first UE and the second UE via inter-UE coordination signaling, and the remaining sidelink scheduling information is autonomously applied by the first UE to the bidirectional full-duplex sidelink transmission.

[0225] Aspect 12: A method according to Aspect 11, wherein: the partial sidelink scheduling information indicates the sidelink time-frequency resources used for the sidelink grant, the partial sidelink scheduling information indicates relative information between two allocated sidelink resources associated with the two sidelink grants for the first UE and the second UE, and the partial sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency; and the remaining sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a transmit configuration indicator identifier, power information, timing information, sorting information, pre-decoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit receiving point scheme.

[0226] Aspect 13: A method according to aspect 11, wherein the remaining sidelink scheduling information indicates a candidate combination of sidelink transmission configuration indicator (TCI) states of both the first UE and the second UE, and the bidirectional full-duplex sidelink transmission is sent at least in part based on the candidate combination of sidelink TCI states.

[0227] Aspect 14: A method according to any one of Aspects 1 to 13, wherein the sidelink scheduling information indicates a set of full-duplex transmit and receive beams associated with the first UE, the set of full-duplex transmit and receive beams indicating at least one transmit beam to at least one adjacent UE and at least one receive beam for at least one adjacent UE, and each transmit beam or receive beam is identified by a reference signal identifier or a transmit configuration indicator identifier.

[0228] Aspect 15: The method according to aspect 14, wherein the sidelink scheduling information indicates a preferred multi-transmission / reception point scheme or a multi-panel transmission or reception scheme.

[0229] Aspect 16: A method according to Aspect 14, wherein the sidelink scheduling information indicates other scheduling information for each transmit beam or receive beam of each adjacent UE, and the other scheduling information indicates one or more of the following: time-frequency resources, power information, timing information, sorting information, precoding matrix information or multiple-input multiple-output scheme.

[0230] Aspect 17: A method according to any one of Aspects 1 to 16, wherein sending one or more of the indication indicating that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible or the sidelink scheduling information is at least partially based on one of the following: a report scheduled by a network node, an autonomous report by the first UE, or a report triggered by an event.

[0231] Aspect 18: A method according to any one of Aspects 1 to 17, wherein the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and the method further includes: sending an indication of selected resources associated with the first bidirectional full-duplex side link transmission to the second UE; receiving an indication of selected resources associated with the second bidirectional full-duplex side link transmission from the second UE; determining time overlapping resources for the first bidirectional full-duplex side link transmission based at least in part on the selected resources associated with the first bidirectional full-duplex side link transmission and the selected resources associated with the second bidirectional full-duplex side link transmission; and applying full-duplex transmission parameters to the time overlapping resources, the full-duplex transmission parameters indicating one or more of the following: a transmission configuration indicator identifier, power information, timing information, sorting information, precoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit receiving point scheme.

[0232] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and the method further includes: sending a request for resources available for a second bidirectional full-duplex side link transmission associated with the second UE to the second UE; receiving an indication of the resources available for the second bidirectional full-duplex side link transmission from the second UE; and sending the indication of the resources available for the second bidirectional full-duplex side link transmission to the network node, and scheduling the first bidirectional full-duplex side link transmission via the side link grant, the DCI indication for the first bidirectional full-duplex side link transmission, which corresponds to time overlapping resources corresponding to at least some of the resources available for the second bidirectional full-duplex side link transmission.

[0233] Aspect 20: A method according to any one of Aspects 1 to 19, wherein the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, the DCI indication for scheduling the first bidirectional full-duplex side link transmission via the side link grant indicates the resources scheduled for the first bidirectional full-duplex side link transmission, and the method further includes: sending an indication of the resources scheduled for the first bidirectional full-duplex side link transmission to the second UE as a preferred or non-preferred side link resource report.

[0234] Aspect 21: A method according to any one of Aspects 1 to 20, wherein the DCI is a first DCI and the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission, and the method further includes: receiving a second DCI associated with the second UE from the network node, the second DCI indicating a sidelink grant for the relay of the second UE; sending the sidelink grant of the relay to the second UE via sidelink control information; and receiving a second bidirectional full-duplex sidelink transmission from the second UE based at least in part on the sidelink grant of the relay.

[0235] Aspect 22: The method according to any one of aspects 1 to 21, wherein the first UE and the second UE are in-coverage UEs, or the first UE is an in-coverage UE and the second UE is an out-of-coverage UE.

[0236] Aspect 23: A method of wireless communication performed by a network node, the method comprising: receiving an indication from a first user equipment (UE) indicating that bidirectional full-duplex sidelink transmission between the first UE and a second UE is feasible; receiving sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission from the first UE; and sending downlink control information (DCI) to the first UE to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication indicating that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

[0237] Aspect 24: The method of aspect 23, wherein the bidirectional full-duplex sidelink transmission between the first UE and the second UE is possible based at least in part on self-interference measurements.

[0238] Aspect 25: A method according to any one of Aspects 23 to 24, wherein the bidirectional full-duplex side link transmission is a first bidirectional full-duplex side link transmission, and the DCI is a first DCI, and the method further includes: sending a second DCI to the second UE to schedule a second bidirectional full-duplex side link transmission between the second UE and the first UE, and the first bidirectional full-duplex side link transmission overlaps with the second bidirectional full-duplex side link transmission in the time domain.

[0239] Aspect 26: The method according to any one of aspects 23 to 25, wherein the bidirectional full-duplex sidelink transmission is a physical sidelink control channel transmission or a physical sidelink shared channel transmission.

[0240] Aspect 27: The method according to any one of aspects 23 to 26, wherein the indication indicates a plurality of neighboring UEs for which bidirectional full-duplex sidelink transmission is feasible, and each of the plurality of neighboring UEs is identified by a corresponding UE identifier.

[0241] Aspect 28: A method according to any one of Aspects 23 to 27, wherein the sidelink scheduling information indicates a sidelink time-frequency resource for the sidelink grant, the sidelink scheduling information indicates relative information between two allocated sidelink resources associated with two sidelink grants for the first UE and the second UE, and the sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency.

[0242] Aspect 29: A method according to any one of Aspects 23 to 28, wherein the sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a transmit configuration indicator identifier, power information, timing information, sorting information, pre-decoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit-receive point scheme.

[0243] Aspect 30: The method according to any one of aspects 23 to 29, wherein the sidelink scheduling information indicates a candidate combination of sidelink transmission configuration indicator states of both the first UE and the second UE.

[0244] Aspect 31: A method according to any one of Aspects 23 to 30, wherein the sidelink scheduling information is partial sidelink scheduling information, the remaining sidelink scheduling information is exchanged between the first UE and the second UE via inter-UE coordination signaling, and the remaining sidelink scheduling information is autonomously applied by the first UE to the bidirectional full-duplex sidelink transmission.

[0245] Aspect 32: A method according to Aspect 31, wherein: the partial sidelink scheduling information indicates the sidelink time-frequency resources used for the sidelink grant, the partial sidelink scheduling information indicates relative information between two allocated sidelink resources associated with the two sidelink grants for the first UE and the second UE, and the partial sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency; and the remaining sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a transmit configuration indicator identifier, power information, timing information, sorting information, pre-decoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit receiving point scheme.

[0246] Aspect 33: A method according to Aspect 31, wherein the remaining sidelink scheduling information indicates a candidate combination of sidelink transmission configuration indicator states of both the first UE and the second UE, and the bidirectional full-duplex sidelink transmission is sent at least in part based on the candidate combination of sidelink TCI states.

[0247] Aspect 34: A method according to any one of Aspects 23 to 33, wherein the sidelink scheduling information indicates a set of full-duplex transmit and receive beams associated with the first UE, the set of full-duplex transmit and receive beams indicating at least one transmit beam to at least one adjacent UE and at least one receive beam for at least one adjacent UE, and each transmit beam or receive beam is identified by a reference signal identifier or a transmit configuration indicator identifier.

[0248] Aspect 35: The method according to aspect 34, wherein the sidelink scheduling information indicates a preferred multi-transmission / reception point scheme or a multi-panel transmission or reception scheme.

[0249] Aspect 36: A method according to Aspect 34, wherein the sidelink scheduling information indicates other scheduling information for each transmit beam or receive beam of each adjacent UE, and the other scheduling information indicates one or more of the following: time-frequency resources, power information, timing information, sorting information, precoding matrix information or multiple-input multiple-output scheme.

[0250] Aspect 37: A method according to any one of aspects 23 to 36, wherein the DCI is a first DCI, and the method further includes: sending a second DCI associated with the second UE to the first UE, the second DCI indicating a sidelink grant for the relay of the second UE.

[0251] Aspect 38: The method according to any one of aspects 23 to 37, wherein the first UE and the second UE are in-coverage UEs, or the first UE is an in-coverage UE and the second UE is an out-of-coverage UE.

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

[0253] Aspect 40: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 22.

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

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

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

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

[0258] Aspect 45: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 23 to 38.

[0259] Aspect 46: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 23 to 38.

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

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

[0262] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

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

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

[0265] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of the various aspects includes each dependent claim in conjunction with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items (including a single member). By way of example, “at least one of a, b, or c” is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0266] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the articles "a" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said" and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only one project is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms that do not limit the elements they modify (for example, an element "having" A may also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A first user equipment (UE) for wireless communication, the first user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to cause the first UE to: sending an indication to a network node indicating that bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; sending, to the network node, side link scheduling information recommended for the bidirectional full-duplex side link transmission; receiving, from the network node, downlink control information (DCI) scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; as well as The bidirectional full-duplex sidelink transmission is sent to the second UE based at least in part on the DCI.

2. The first UE of claim 1 , wherein the one or more processors are further configured to cause the first UE to: The bidirectional full-duplex sidelink transmission is feasible based at least in part on a self-interference measurement based at least in part on a dedicated reference signal or traffic transmission associated with the first UE.

3. The first UE according to claim 1, wherein the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission, and the DCI is a first DCI, a second DCI schedules a second bidirectional full-duplex sidelink transmission between the second UE and the first UE, and the first bidirectional full-duplex sidelink transmission overlaps with the second bidirectional full-duplex sidelink transmission in the time domain. 4 . The first UE according to claim 1 , wherein the bidirectional full-duplex sidelink transmission is a physical sidelink control channel transmission or a physical sidelink shared channel transmission. 5 . The first UE of claim 1 , wherein the indication indicates a plurality of neighboring UEs for which bidirectional full-duplex sidelink transmission is feasible, and each of the plurality of neighboring UEs is identified by a corresponding UE identifier.

6. The first UE according to claim 1, wherein the sidelink scheduling information indicates a sidelink time-frequency resource for the sidelink grant, the sidelink scheduling information indicates relative information between two allocated sidelink resources associated with two sidelink grants for the first UE and the second UE, and the sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency.

7. The first UE according to claim 1, wherein the sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a transmit configuration indicator identifier, power information, timing information, sorting information, precoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit reception point scheme. 8 . The first UE according to claim 1 , wherein the sidelink scheduling information indicates candidate combinations of sidelink transmission configuration indicator (TCI) states of both the first UE and the second UE.

9. The first UE of claim 8, wherein the DCI that schedules the bidirectional full-duplex sidelink transmission via the sidelink grant is based at least in part on the candidate combination of sidelink TCI states.

10. The first UE of claim 8, wherein the one or more processors are further configured to cause the first UE to: Bidirectional full-duplex sidelink feedback is sent to the second UE based at least in part on the candidate combination of sidelink TCI states.

11. The first UE according to claim 1, wherein the sidelink scheduling information is partial sidelink scheduling information, the remaining sidelink scheduling information is exchanged between the first UE and the second UE via inter-UE coordination signaling, and the remaining sidelink scheduling information is autonomously applied by the first UE to the bidirectional full-duplex sidelink transmission.

12. The first UE according to claim 11, wherein: The partial sidelink scheduling information indicates a sidelink time-frequency resource for the sidelink grant, the partial sidelink scheduling information indicates relative information between two allocated sidelink resources associated with two sidelink grants for the first UE and the second UE, and the partial sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency; and The remaining sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a transmit configuration indicator identifier, power information, timing information, sorting information, pre-decoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit reception point scheme.

13. The first UE of claim 11 , wherein the remaining sidelink scheduling information indicates a candidate combination of sidelink transmission configuration indicator (TCI) states for both the first UE and the second UE, and the bidirectional full-duplex sidelink transmission is transmitted based at least in part on the candidate combination of sidelink TCI states.

14. The first UE according to claim 1, wherein the sidelink scheduling information indicates a set of full-duplex transmit and receive beams associated with the first UE, the set of full-duplex transmit and receive beams indicating at least one transmit beam to at least one neighboring UE and at least one receive beam for at least one neighboring UE, and each transmit beam or receive beam is identified by a reference signal identifier or a transmit configuration indicator identifier. 15 . The first UE according to claim 14 , wherein the sidelink scheduling information indicates a preferred multi-transmission / reception point scheme or a multi-panel transmission or reception scheme.

16. The first UE according to claim 14, wherein the sidelink scheduling information indicates other scheduling information for each transmit beam or receive beam of each adjacent UE, and the other scheduling information indicates one or more of the following: time-frequency resources, power information, timing information, sorting information, precoding matrix information or multiple-input multiple-output scheme.

17. A first UE according to claim 1, wherein the one or more processors are configured to send one or more of the indication indicating that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible based at least in part on one of the following: a report scheduled by a network node, an autonomous report by the first UE, or a report triggered by an event.

18. The first UE of claim 1 , wherein the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission, and the one or more processors are further configured to cause the first UE to: sending an indication of selected resources associated with the first bidirectional full-duplex sidelink transmission to the second UE; receiving, from the second UE, an indication of selected resources associated with a second bidirectional full-duplex sidelink transmission; determining temporally overlapping resources for the first bidirectional full-duplex sidelink transmission based at least in part on the selected resources associated with the first bidirectional full-duplex sidelink transmission and the selected resources associated with the second bidirectional full-duplex sidelink transmission; as well as Full-duplex transmission parameters are applied to the time overlapping resources, where the full-duplex transmission parameters indicate one or more of the following: a transmission configuration indicator identifier, power information, timing information, sorting information, precoding matrix information, a multiple-input multiple-output scheme, or a multiple transmission reception point scheme.

19. The first UE of claim 1 , wherein the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission, and the one or more processors are further configured to cause the first UE to: sending a request to the second UE for resources available for a second bidirectional full-duplex sidelink transmission associated with the second UE; receiving, from the second UE, an indication of the resources available for use in the second bidirectional full-duplex sidelink transmission; and The indication of the resources available for the second bidirectional full-duplex side link transmission is sent to the network node, and the DCI for scheduling the first bidirectional full-duplex side link transmission via the side link grant indicates time overlapping resources for the first bidirectional full-duplex side link transmission that correspond to at least some of the resources available for the second bidirectional full-duplex side link transmission.

20. The first UE of claim 1 , wherein the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission, the DCI scheduling the first bidirectional full-duplex sidelink transmission via the sidelink grant indicates resources scheduled for the first bidirectional full-duplex sidelink transmission, and the one or more processors are further configured to cause the first UE to: An indication of the resources scheduled for the first bidirectional full-duplex sidelink transmission is sent to the second UE as a preferred or non-preferred sidelink resource report.

21. The first UE of claim 1 , wherein the DCI is a first DCI and the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission, and the one or more processors are further configured to cause the first UE to: receiving, from the network node, a second DCI associated with the second UE, the second DCI indicating a sidelink grant for relaying of the second UE; sending the relayed sidelink grant to the second UE via sidelink control information; and A second bidirectional full-duplex sidelink transmission is received from the second UE based at least in part on the relayed sidelink grant.

22. The first UE of claim 1, wherein the first UE and the second UE are in-coverage UEs, or the first UE is an in-coverage UE and the second UE is an out-of-coverage UE.

23. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to cause the network node to: receiving an indication from a first user equipment (UE) that bidirectional full-duplex sidelink transmission between the first UE and a second UE is possible; receiving, from the first UE, sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission; as well as Downlink control information (DCI) is sent to the first UE to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

24. The network node of claim 23, wherein the bidirectional full-duplex sidelink transmission is a first bidirectional full-duplex sidelink transmission and the DCI is a first DCI, and the one or more processors are further configured to cause the network node to: A second DCI scheduling a second bidirectional full-duplex sidelink transmission between the second UE and the first UE is sent to the second UE, and the first bidirectional full-duplex sidelink transmission overlaps with the second bidirectional full-duplex sidelink transmission in the time domain.

25. The network node of claim 23, wherein: The sidelink scheduling information indicates a sidelink time-frequency resource for the sidelink grant, the sidelink scheduling information indicates relative information between two allocated sidelink resources associated with two sidelink grants for the first UE and the second UE, and the sidelink scheduling information indicates whether the two allocated sidelink resources do not overlap in frequency, partially overlap in frequency, or completely overlap in frequency; or The sidelink scheduling information indicates non-time-frequency allocation information of the sidelink resources associated with the sidelink grant, and the non-time-frequency allocation information indicates one or more of the following: a sidelink transmit beam, a transmit configuration indicator identifier, power information, timing information, sorting information, pre-decoding matrix information, a multiple-input multiple-output scheme, or a multiple transmit reception point scheme.

26. The network node according to claim 23, wherein the sidelink scheduling information is partial sidelink scheduling information, the remaining sidelink scheduling information is exchanged between the first UE and the second UE via inter-UE coordination signaling, and the remaining sidelink scheduling information is autonomously applied by the first UE to the bidirectional full-duplex sidelink transmission.

27. A network node according to claim 23, wherein the sidelink scheduling information indicates a set of full-duplex transmit and receive beams associated with the first UE, the set of full-duplex transmit and receive beams indicating at least one transmit beam to at least one neighboring UE and at least one receive beam for at least one neighboring UE, and each transmit beam or receive beam is identified by a reference signal identifier or a transmit configuration indicator identifier.

28. The network node of claim 23, wherein the DCI is a first DCI, and the one or more processors are further configured to cause the network node to: A second DCI associated with the second UE is sent to the first UE, the second DCI indicating a sidelink grant for relaying of the second UE.

29. A method of wireless communication performed by a first user equipment (UE), the method comprising: sending an indication to a network node indicating that bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; sending, to the network node, side link scheduling information recommended for the bidirectional full-duplex side link transmission; receiving, from the network node, downlink control information (DCI) scheduling the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible; as well as The bidirectional full-duplex sidelink transmission is sent to the second UE based at least in part on the DCI.

30. A method of wireless communication performed by a network node, the method comprising: receiving an indication from a first user equipment (UE) that bidirectional full-duplex sidelink transmission between the first UE and a second UE is possible; receiving, from the first UE, sidelink scheduling information recommended for the bidirectional full-duplex sidelink transmission; as well as Downlink control information (DCI) is sent to the first UE to schedule the bidirectional full-duplex sidelink transmission via a sidelink grant, the DCI being based at least in part on the sidelink scheduling information and the indication that the bidirectional full-duplex sidelink transmission between the first UE and the second UE is feasible.

Images