Downlink reception in uplink subband

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can receive configuration information associated with downlink reception in an uplink subband corresponding to a subband full duplex (SBFD) aware configuration. The UE can receive downlink communications in the uplink subband based on the configuration information. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 377,963, filed on September 30, 2022, entitled “DOWNLINK RECEPTION IN AN UPLINK SUBBAND,” and U.S. Non-Provisional Patent Application No. 18 / 365,858, filed on August 4, 2023, entitled “DOWNLINK RECEPTION IN AN UPLINK SUBBAND,” which are 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 downlink reception in an uplink sub-band. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support 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) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, 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 communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be 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 spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, 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 to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to receive configuration information associated with downlink reception in an uplink subband corresponding to a subband full-duplex (SBFD) aware configuration. The one or more processors may be configured to cause the UE to receive downlink communications in the uplink subband based on the configuration information.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the network node to send configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration. The one or more processors may be configured to cause the network node to send downlink communications in the uplink subband based on the configuration information.

[0009] Some aspects described herein relate to a method of wireless communication performed by an apparatus at a UE. The method may include receiving configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration. The method may include receiving downlink communications in the uplink subband based on the configuration information.

[0010] Some aspects described herein relate to a method of wireless communication performed by an apparatus at a network node. The method may include sending configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration. The method may include sending downlink communications in the uplink subband based on the configuration information.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive downlink communications in the uplink subband based on the configuration information.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration. The instruction set, when executed by one or more processors of the network node, may cause the network node to send downlink communications in the uplink subband based on the configuration information.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration. The apparatus may include components for receiving downlink communications in the uplink subband based on the configuration information.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration. The apparatus may include means for sending downlink communications in the uplink subband based on the configuration information.

[0015] 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 drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose 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 of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology 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 devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment 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. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of 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] 4A to 4D is a diagram illustrating an example of full-duplex (FD) communication according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a time slot format for scheduling UE communications according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of sub-band full-duplex (SBFD) resources and communications according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of downlink reception in a flexible uplink subband according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0028] Fig.10 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0029] Fig.11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0030] 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 construed as being limited to any specific structure or function presented throughout the present disclosure. Rather, 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 should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the 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 cover such a device or method that is practiced using other structures, functions, or structures and functions 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 invention.

[0031] Aspects and examples generally include methods, apparatus, network nodes, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as described or fully described herein with reference to the figures and description and as illustrated in the figures and description.

[0032] The present disclosure can be easily used as a basis for modifying or designing other structures for the same purpose of performing the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages are better understood from the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, not as a definition of the limitations of the claims.

[0033] Although various aspects are described in the present disclosure by illustrating some examples, such aspects can be implemented in many different arrangements and scenarios. The technology 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 devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment 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. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein can be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of different sizes, shapes and compositions.

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

[0035] Although various aspects may be described herein using terms 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 RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0036] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The 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. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means 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 decomposed network node (sometimes referred to as a decomposed base station), which means 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)).

[0037] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The 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, a 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, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0038] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell 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 1In the example shown in , 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, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0039] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed 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, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC) or 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 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 a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, 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.

[0040] The 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., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. 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.

[0041] 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).

[0042] 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 or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0043] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0044] Some UEs 120 may be considered as 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 that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside 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, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] In general, 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. RAT may be referred to as a radio technology, air interface, etc. 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.

[0046] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may 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 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

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

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

[0049] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or 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.

[0050] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive configuration information associated with downlink reception in an uplink subband corresponding to a sub-band full-duplex (SBFD) aware configuration; and receive downlink communications in the uplink subband based on the configuration information. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0051] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration; and send downlink communications in the uplink subband based on the configuration information. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

[0053] Figure 2 2 is a diagram illustrating an 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 to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. 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 a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0054] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The 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. The 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, where 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 to 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 upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0055] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the 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 to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the 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 a 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, may perform MIMO detection on the received symbols where applicable, and may 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 the data sink 260, and may provide decoded control information and system information to the 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 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, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0056] 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.

[0057] 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 sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may 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.

[0058] Each of the antenna elements may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element that is cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements may allow signals having a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half wavelength, or other fraction of a wavelength of the spacing between adjacent antenna elements to allow interaction or interference of signals transmitted by individual antenna elements within the desired range.

[0059] Antenna elements and / or sub-elements may be used to generate beams. A "beam" may refer to a directional transmission, such as a wireless signal transmitted in the direction of a receiving device. A beam may include a directional signal, a direction associated with the signal, a set of directional resources associated with the signal (e.g., angle of arrival, horizontal direction, vertical direction), and / or a set of parameters indicating one or more aspects of a directional signal, a direction associated with the signal, and / or a set of directional resources associated with the signal.

[0060] As indicated above, antenna elements and / or sub-elements can be used to generate beams. For example, antenna elements can be individually selected or deselected for transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers. Beamforming includes generating beams using multiple signals on different antenna elements, wherein one or more or all of the multiple signals are shifted in phase relative to each other. The formed beams can carry physical or higher layer reference signals or information. When each of the multiple signals is radiated from the corresponding antenna element, the radiated signals interact, interfere (constructively and destructively) and amplify with each other to form the resulting beam. The shape (such as amplitude, width and / or the presence of side lobes) and direction (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shift or phase offset of the multiple signals relative to each other.

[0061] Beamforming may be used for communication between a UE and a network node, such as for millimeter wave communication, etc. In this case, the network node may provide the UE with a configuration of a transmit configuration indicator (TCI) state, which indicates beams that may be used by the UE, such as for receiving a physical downlink shared channel (PDSCH). The network node may indicate an activated TCI state to the UE, which the UE may use to select a beam for receiving the PDSCH.

[0062] The beam indication may be or include a TCI state information element, a beam identifier (ID), spatial relationship information, a TCI state ID, a closed loop index, a panel ID, a TRP ID, and / or a sounding reference signal (SRS) set ID, etc. The TCI state information element (referred to herein as TCI state) may indicate information associated with a beam such as a downlink beam. For example, the TCI state information element may indicate a TCI state identifier (e.g., tci-StateID), a quasi-co-location (QCL) type (e.g., qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, qcl-TypeD, etc.), a cell identifier (e.g., ServCellIndex), a bandwidth part identifier (bwp-Id), a reference signal identifier (such as CSI-RS (e.g., NZP-CSI-RS-ResourceId, SSB-Index, etc.)), etc. The spatial relationship information may similarly indicate information associated with an uplink beam.

[0063] The beam indication may be a joint or separate downlink (DL) / uplink (UL) beam indication in a unified TCI framework. In some cases, the network may use at least UE-specific (unicast) downlink control information (DCI) to indicate a joint or separate DL / UL beam indication from an active TCI state, thereby supporting beam indication based on layer 1 (L1). In some cases, existing DCI formats 1_1 and / or 1_2 may be reused for beam indication. The network may include a support mechanism for the UE to confirm successful decoding of the beam indication. For example, an acknowledgment / negative acknowledgment (ACK / NACK) of a PDSCH scheduled by a DCI carrying a beam indication may also be used as an ACK for the DCI.

[0064] Beam indication may be provided for carrier aggregation (CA) scenarios. In a unified TCI framework, the network may support common TCI state ID updates and activations to provide common QCL information and / or one or more common UL transmit spatial filters across a set of configured component carriers (CCs). This type of beam indication may be applicable to intra-band CA as well as joint DL / UL beam indication and separate DL / UL beam indication. A common TCI state ID may mean that a reference signal (RS) determined according to a TCI state indicated by a common TCI state ID is used to provide a QCL type D indication and determine a UL transmit spatial filter across a set of configured CCs.

[0065] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). 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 the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent 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 perform the functions described herein (eg, with reference to Figures 7 to 11 ) or any aspect of any of the methods described herein.

[0066] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes 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 perform operations described herein (e.g., with reference to Figures 7 to 11 ) or any aspect of any of the methods described herein.

[0067] In some aspects, the controller / processor 280 may be a component of a processing system. A processing system may generally be a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs that may be communicated to other systems or components, such as the UE 120. For example, the processing system of the UE 120 may be a system that includes various other components or subcomponents of the UE 120.

[0068] The processing system of UE 120 may interface with one or more other components of UE 120, may process information (such as input or signal) received from one or more other components, or may output information to one or more other components. For example, a chip or modem of UE 120 may include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, sending, or providing information. In some examples, the first interface may be an interface between a processing system and a receiver of the chip or modem, so that UE 120 may receive information or signal input, and may pass information to the processing system. In some examples, the second interface may be an interface between a processing system and a transmitter of the chip or modem, so that UE 120 may send information output from the chip or modem. A person of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0069] In some aspects, controller / processor 240 may be a component of a processing system. A processing system may generally be a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs that may be passed to other systems or components, such as network node 110. For example, a processing system of network node 110 may be a system that includes various other components or subcomponents of network node 110.

[0070] The processing system of the network node 110 may interface with one or more other components of the network node 110, may process information (such as input or signal) received from one or more other components, or may output information to one or more other components. For example, a chip or modem of the network node 110 may include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, sending, or providing information. In some examples, the first interface may be an interface between a processing system and a receiver of the chip or modem, so that the network node 110 may receive information or signal input, and may pass information to the processing system. In some examples, the second interface may be an interface between a processing system and a transmitter of the chip or modem, so that the network node 110 may send information output from the chip or modem. A person of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0071] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the may perform one or more techniques associated with downlink reception in the uplink subband, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 900 and / or operations of 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 by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0072] In some aspects, a UE (e.g., UE 120) includes: a component for receiving configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration; and / or a component for receiving downlink communications in the uplink subband based on the configuration information. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0073] In some aspects, a network node (e.g., network node 110) includes: a component for sending configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration; and / or a component for sending downlink communications in an uplink subband based on the configuration information. The components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0074] In some aspects, a single processor may perform all of the functions described as being performed by the one or more processors. In some aspects, the one or more processors may perform a set of functions together. For example, a first set of (one or more) of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more processors" should be understood to refer to the combination Figure 2 Any one or more of the processors described. References to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as in conjunction with Figure 2 For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or by a different subset of the one or more memories.

[0075] Although Figure 2The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for 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.

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

[0077] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing a base station function can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0078] An aggregated base station (e.g., an aggregated network node) may 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) may 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, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may 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), and the like.

[0079] Base station type operations or network designs may take into account the aggregated nature of base station functions. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a 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 the scaling of a communication system by separating base station functions into one or more units that can be deployed separately. A decomposed base station may include functions implemented across two or more units at various physical locations, as well as functions implemented virtually for at least one unit, which may enable flexibility in network design. Various units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

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

[0081] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as 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 a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0082] 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, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP) functions), control plane functions (e.g., central unit-control plane (CU-CP) functions), or a combination thereof. In some specific 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

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

[0084] Each RU 340 may implement lower layer functions. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane 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).

[0085] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an 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 an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an 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.

[0086] The non-RT RIC 315 may be configured to include logic functions that enable 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 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0087] In some implementations, in order to generate an AI / ML model 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 a non-network data source or from a network function 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 regulate RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

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

[0089] 4A to 4D4 is a diagram illustrating examples 400, 410, 420, 430 of full-duplex (FD) communication according to the present disclosure. FD communication is a communication that uses overlapping time resources to send and receive at a single node (such as a UE or a base station). For example, a UE or a network node may use the same time resources to perform transmission and reception, such as via frequency division multiplexing (FDM) or space division multiplexing (SDM). "FDM" refers to performing two or more communications using different frequency resource allocations. "SDM" refers to performing two or more communications using different spatial parameters (such as different TCI states that define different beams). SDM communication may use overlapping time resources and frequency resources, and FDM communication may use overlapping time resources and spatial resources (i.e., overlapping beam parameters, TCI states, etc.). The TCI state indicates the spatial parameters used for communication. For example, the TCI state used for communication may identify a source signal (such as a synchronization signal block, a channel state information reference signal, etc.) and a spatial parameter to be derived from the source signal for the purpose of sending or receiving communication. For example, the TCI state may indicate a QCL type. The QCL type may indicate one or more spatial parameters to be derived from the source signal. The source signal may be referred to as a QCL source. FD communications may include dynamic services (such as those scheduled by downlink control information (DCI)) and / or semi-static services. Semi-static services are services associated with semi-persistent resources (such as resources configured by semi-persistent scheduling (SPS) or configured grants (CG)).

[0090] Figure 4A The example 400 includes UE1 402 and two network nodes (e.g., TRPs) 404-1, 404-2, where UE1 402 is transmitting uplink transmissions to network node 404-1 and receiving downlink transmissions from network node 404-2. In some aspects, the network node 404 described in conjunction with FIG. 4 can be a base station, a TRP associated with (e.g., managed by) a network node, a RU, a DU, or a similar network node. In some aspects, the UE 402 described in conjunction with FIG. 4 can be a TRP associated with (e.g., managed by) a network node. Figure 1 , Figure 2 and Figure 3 UE 120 or similar UE described herein. Figure 4A In the example 400 of , FD is enabled for UE1 402 but not for network nodes 404-1, 404-2. Therefore, network nodes 404-1 and 404-2 are half-duplex (HD) network nodes.

[0091] Figure 4BExample 410 includes two UEs (UE1 402-1 and UE2 402-2), a network node 404-1, and a network node 404-2. UE1 402-1 is receiving a downlink transmission from the network node 404-1, and UE2 402-2 is sending an uplink transmission to the network node 404-1. Figure 4B In the example 410, FD is enabled for the network node 404-1 but not for UE1 402-1 and UE2 402-2. Therefore, UE1 402-1 and UE2 402-2 are half-duplex UEs.

[0092] Figure 4C Example 420 includes UE1 402 and network node 404, where UE1 402 is receiving downlink transmissions from network node 404 and UE1 402 is sending uplink transmissions to network node 404. Figure 4C In example 420, FD is enabled for both UE 1402 and network node 404. Figure 4C In example 420, UE1 402 and network node 404 communicate using a beam pair. The beam pair may include a downlink beam and an uplink beam. For example, UE1 402 may communicate with network node 404 using a beam pair including a downlink beam at UE1 402 (i.e., a receive beam) and an uplink beam at UE1 402 (i.e., a transmit beam). Network node 404 may use a downlink beam at network node 404 (i.e., a transmit beam) to transmit communications received via the downlink beam of UE1 402, and may use an uplink beam at network node 404 (i.e., a receive beam) to receive communications sent via the uplink beam of UE1 402.

[0093] Figure 4C Example 430 includes a network node 110 and a cell (such as a combination Figure 1 102) is associated with two network nodes 404-1 and 404-2. Network nodes 404-1 and 404-2 may be co-located (e.g., located at the same device, such as network node 110 or other device), or may be non-co-located (e.g., located separately from each other and / or network node 110, and thus may be independent devices).

[0094] exist 4A to 4D In the example of interference is indicated by the dashed line. Interference can occur between the network nodes of the examples 400, 410, 420, 430 (referred to as cross-link interference (CLI)). Figure 4A In , the downlink transmission of network node 404-2 interferes with the uplink transmission of network node 404-1. Figure 4BIn the example, the uplink reception of network node 404-1 may be interfered by the transmission from network node 404-2. The CLI between network nodes 404 is referred to herein as inter-network node CLI. Figure 4B In some examples, the uplink transmission of UE2 402-2 may interfere with the downlink transmission of UE1 402-1 (not shown). Figure 4D In the example, the uplink transmission of UE2 402-2 interferes with the downlink transmission of UE1 402-1. In some cases, self-interference may occur. Self-interference occurs when the transmission of a node interferes with the receiving operation of the node. For example, self-interference may occur due to the reception of radiated energy from the transmitting antenna by the receiving antenna, crosstalk between components, etc. Figure 4C Examples of self-interference at UE 402 (from uplink transmission to downlink reception) and at network node 404 (from downlink transmission to uplink reception) are shown in FIG. It should be noted that the above-described CLI and self-interference conditions may occur in both HD and FD deployments.

[0095] Some network nodes support SBFD communication, as described below. SBFD communication may involve configuring certain resources to have a SBFD format.

[0096] As indicated above, 4A to 4D is provided as one or more examples. Other examples may be found in relation to 4A to 4D The examples described are different.

[0097] Figure 5 5 is a diagram illustrating an example 500 of a time slot format for scheduling UE communications according to the present disclosure. As described above, the transmission timeline can be organized into radio frames, subframes, time slots, and symbols. However, for ease of description, Figure 5 Only the time slot and symbol granularity are depicted in. Example 500 illustrates how a time division duplex (TDD) time slot (eg, a time slot on a TDD carrier) may be configured to be usable for uplink and / or downlink communications using a combination of semi-static signaling and dynamic signaling.

[0098] A timeline of time slots is shown by reference numeral 510, which includes a plurality of time slots 515a through 515s. Each time slot 515 and / or portions thereof (e.g., symbols) may be scheduled and / or configured for uplink ("UL") communications, downlink ("DL") communications, or to be flexible ("F"). Flexible time slots (e.g., 515h through 515m) may be used for uplink communications or downlink communications. Resources that are configured and / or scheduled for uplink communications are described herein as having an uplink (U) format. Resources that are configured and / or scheduled for downlink communications are described herein as having a downlink (D) format. Resources that are configured and / or scheduled to include only flexible resources are described herein as having a flexible (F) format. All symbols within each time slot may be similarly assigned (e.g., all "UL," all "DL," or all "F"), otherwise the time slot may include multiple symbol assignment types. For example, in Figure 5 , time slots 515a to 515f (represented by “nrofDownlinkSlots”) are depicted as downlink time slots without showing symbol granularity because all symbols in each of those time slots are configured as downlink symbols. Similarly, time slots 515o to 515s (represented by “nrofUplinkSlots”) are depicted as uplink time slots without showing symbol granularity because all symbols in each of those time slots are configured as uplink symbols. In this regard, “nrofDownlinkSlots” refers to the number of consecutive full DL time slots (e.g., time slots that only include DL symbols) at the beginning of each time line of time slots 510 (e.g., time slots 515a to 515f), and “nrofUplinkSlots” refers to the number of consecutive full UL time slots (e.g., time slots that only include UL symbols) at the end of each time line of time slots 510 (e.g., time slots 515o to 515s).

[0099] Slots 515g and 515n include symbols of more than one format. More specifically, slot 515g includes six downlink symbols (represented by "nrofDownlinkSymbols"), of which the remaining eight symbols are flexible and can therefore be used for uplink or downlink, for a total of fourteen symbols. Slot 515n includes six uplink symbols (represented by "nrofUplinkSymbols"), of which the remaining eight symbols are flexible and can therefore be used for uplink or downlink, also for a total of fourteen symbols. In this regard, "nrofDownlinkSymbols" refers to the number of consecutive DL symbols at the beginning of slot 515g after the last full DL slot 515f, and "nrofUplinkSymbols" refers to the number of consecutive UL symbols at the end of slot 515n before the first full UL slot 515o. The remaining time slots in the timeline of time slots 510 (eg, time slots 515h through 515m) are flexible (eg, fully flexible, where all symbols in these time slots are configured as flexible symbols) and are therefore usable for uplink and downlink communications.

[0100] Resources (e.g., time slots and / or symbols) that are semi-statically configured as flexible may be later reconfigured for uplink or downlink communications. In some aspects, common configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon or similar common configuration parameters) sent to all UEs in a cell define a semi-static time slot and / or symbol structure, including designating certain time slots or symbols for uplink communications, downlink communications, or as flexible for uplink or downlink communications. For example, the common configuration parameters may semi-statically configure time slots and symbols to have, for example, Figure 5 The initial configuration shown in . A dedicated configuration parameter (e.g., tdd-UL-DL-ConfigurationDedicated) that may be sent to a specific UE via a slot format indicator (SFI) may then be used to reconfigure the flexible slots and symbols as uplink or downlink slots and symbols. In some cases, for the remaining flexible slots or symbols (e.g., still configured as flexible slots or symbols after reconfiguration due to dedicated configuration parameters), the UE may monitor physical downlink control channel (PDCCH) information and determine whether the flexible slots or symbols should be configured as uplink slots or symbols or downlink slots or symbols based at least in part on the uplink and / or downlink resource allocation indicated by the PDCCH information. In some cases, the flexible slots or symbols may be dynamically changed by a network node via a DCI message or similar message (which may be referred to as a UE-specific configuration).

[0101] Resources (e.g., time slots and / or symbols) may be configured to have an SBFD format. Resources having an SBFD format include one or more SBFD symbols. An SBFD symbol is a symbol having one or more subbands (referred to herein as SBFD subbands) that a network node (such as a gNB) may use or will use for SBFD operations. For SBFD operations within a TDD carrier, an SBFD subband may include 1 resource block or a group of consecutive resource blocks for the same transmission direction. In some aspects, for SBFD operations within a TDD carrier, an SBFD subband consists of 1 resource block or a group of consecutive resource blocks for the same transmission direction. In some aspects, an "SBFD symbol" is defined as a symbol having a subband that the gNB will use for SBFD operations. In some aspects, for SBFD operations within a TDD carrier, an SBFD subband consists of 1 resource block (RB) or a group of consecutive RBs for the same transmission direction. In combination Figure 6 Additional description of SBFD resources is provided.

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

[0103] Figure 6 is a diagram illustrating an example 600 of SBFD resources and communications according to the present disclosure. Figure 6 Examples 605, 610, and 620 of SBFD resources are shown, as well as an example 615 of a communication configuration between network node 110 and UEs 1 and 2 (eg, UE 120) configured using SBFD.

[0104] SBFD resources (i.e., resources with SBFD format) may include one or more symbols and / or one or more time slots. As mentioned above, SBFD resources may include at least one uplink subband (i.e., a subband for uplink communication of UE) and at least one downlink subband (i.e., a subband for downlink communication of UE). Example 605 includes two non-contiguous downlink subbands and one uplink subband. Example 610 includes one downlink subband and one uplink subband. The two downlink subbands of Example 605 may be used by a single UE, or may be used by different UEs (e.g., a first UE for a first downlink subband and a second UE for a second downlink subband). As mentioned above, a subband may include one or more continuous resource blocks associated with a transmission direction. Here, Example 605 includes two subbands associated with a downlink transmission direction and one subband associated with an uplink transmission direction, and Example 610 includes one subband associated with a downlink transmission direction and one subband associated with an uplink transmission direction. Examples 605 and 610 may illustrate a symbol having an SBFD format (e.g., a symbol in which there is a set of resource blocks including at least one downlink subband and a set of resource blocks including at least one uplink subband), a time slot having an SBFD format (e.g., a time slot in which there is at least one downlink subband and at least one uplink subband), or another time resource having an SBFD format.

[0105] In resources with SBFD format, the network node 110 may perform simultaneous transmission of downlink transmission and reception of uplink transmission on a subband basis. For example, the network node 110 may communicate with UE1 on the downlink and with UE2 on the uplink at the same time. In some examples, UE1 and / or UE2 may be configured only with subbands used by UE1 and / or UE2 for communication. For example, UE1 may be configured only with downlink subbands, and UE2 may be configured only with uplink subbands of SBFD formatted resources. This may be because, for example, UE1 and / or UE2 do not have the capability for SBFD communication. In some examples, UE1 and / or UE2 may be configured to utilize SBFD formatted resources. For example, if the UE has the capability for SBFD communication, the UE may know that a given resource has an SBFD format (while utilizing the resource only in one transmission direction), or may perform FD communication in a given resource.

[0106] The resource may be configured as a SBFD format. In some aspects, the resource may be configured as a SBFD format based at least in part on an indication of a change in the format of the resource. For example, the network node may provide signaling indicating that the format of the resource is selected as a SBFD format (similar to how signaling may indicate whether the format is an uplink format, a downlink format, or a flexible format). As another example, the network node may configure one or more subbands of the resource such that the resource includes at least one uplink subband and at least one downlink subband. For example, the network node may reconfigure a subband of a time slot having a downlink format as an uplink subband, thereby converting the time slot to have a SBFD format.

[0107] Example 620 shows downlink subbands and uplink subbands. In some cases, a UE may use an uplink subband for uplink transmissions but may not be scheduled to receive downlink communications in an uplink subband. However, in some cases, a UE may benefit from being able to receive downlink communications in an uplink subband, for example, to simultaneously receive certain types of downlink communications in more than one subband and / or for measuring CLI.

[0108] Some aspects of the techniques and apparatus described herein may facilitate downlink reception in an uplink subband. In some aspects, the uplink subband may be a flexible uplink subband. For example, in some aspects, downlink reception may be provided for downlink scheduling of physical downlink shared channel (PDSCH) communications, channel state information reference signal (CSI-RS), and / or physical downlink control channel (PDCCH) communications. In some aspects, downlink reception in an uplink subband may be provided for facilitating CLI measurements.

[0109] In some aspects, rules may be defined regarding what types of signals / channels may be received in an uplink subband. For example, in some aspects, only dynamic communications scheduled by DCI may be received in an uplink subband, while downlink communications configured by RRC may be skipped based on having a lower priority level. In some aspects, if the UE has a downlink subband RF filter and the downlink RF filter needs to be tuned (e.g., using a D / U subband configuration) or if the UE needs to re-tune the RF frequency, the scheduling offset associated with the network node that schedules downlink reception within the uplink subband in the SBFD symbol may be long enough to ensure that the UE has sufficient time to re-tune the RF and / or re-tune the downlink subband filter.

[0110] In some aspects, an SBFD-aware UE may perform downlink reception in an uplink subband for inter-UE CLI measurements within an uplink subband and / or a dynamically downlink scheduled PDSCH or CSI-RS. In some aspects, downlink reception configured by higher layers (e.g., PDCCH, semi-persistent scheduling (SPS), periodic or semi-periodic CSI-RS) in an uplink subband may be skipped or discarded, except, for example, when a network node indicates to the UE that symbols for RRC downlink reception are switched from SBFD symbols to DL-only symbols. In some aspects, a UE may not expect to be configured with a search space monitoring opportunity in which an associated control resource set (CORESET) overlaps an uplink subband. In some aspects, a UE may not receive a PDCCH in the case where a CORESET associated with a synchronization symbol overlaps an uplink subband.

[0111] For downlink PDSCH reception and / or downlink aperiodic CSI-RS reception within an uplink subband, the scheduling DCI format may indicate that the UE does not rate match the PDSCH around the uplink subband and associated guard band. The indication may be explicit by being included in a DCI bit field (e.g., an indication indicating duplex mode = 'HD' or 'SBFD', or an indication indicating enabling / disabling rate matching around the uplink subband and guard band). For downlink reception of CSI-RS, a dedicated duplex mode (HD / FD) bit field indicator may be included in the DCI that triggers the aperiodic CSI-RS, or the dedicated duplex mode (HD / FD) bit field indicator may be configured in the information element of the triggered aperiodic CSI-RS resource. For PDSCH, the network node may dynamically indicate whether the UE performs PDSCH rate matching around the uplink subband. For example, in some aspects, when scheduled by DCI formats 1_1 and 1_2, the network node may provide a dynamic indication to deactivate and / or disable rate matching around the uplink subband. In some aspects, the UE may receive a MAC CE to indicate whether the UE is to enable / disable uplink subbands and rate matching around a time span of a rate matching pattern.

[0112] In some aspects, for PDSCH, the indication may be implicit (e.g., the time domain resource allocation (TDRA) table may include an additional entry for the network node duplex or duplex mode TCI state). Based on the duplex mode, if configured as HD (non-SBFD mode), the UE does not rate match the PDSCH around the UL subband. If the duplex mode is SBFD, the UE may expect PDSCH reception in only the DL subband and rate match the PDSCH around the UL subband. In some aspects, for frequency domain resource allocation (FDRA) in DCI transmission, the UE may not ignore the bit fields mapped to uplink subbands and guard bands, because when the UE is indicated to receive DL reception in the UL subband, the corresponding resources may be considered as valid frequency resources for downlink scheduling.

[0113] In some aspects, based on the network node configuring non-continuous CSI-RS or continuous CSI-RS, the SBFD symbols may be subject to rules defined for the UE to avoid measuring uplink subbands. In the case where the network node schedules downlink reception within the uplink subband in the SBFD symbol, the UE may measure continuous CSI-RS in all frequency resources (including in the uplink subband). In some aspects, for example, a dedicated (HD / FD) bit field indicator may be included in the scheduling DCI, the triggering DCI, and / or the RRC configuration of the aperiodic CSI-RS. If the bit field indicates the SBFD mode, the UE may assume that the CSI-RS is non-continuous and may not receive the CSI-RS in the UL subband.

[0114] In some aspects, for downlink PDSCH reception and / or CSI-RS reception within an uplink subband, the scheduling offset may be greater than the application time. The application time may be the minimum required time between the received DCI (e.g., the last PDCCH symbol or the last symbol in a CORESET) and the first symbol of PDSCH / CSI-RS reception in the uplink subband. In some aspects, the application time may allow the UE to perform RF retuning and digital filter and sampling rate adaptation. In some aspects, the UE may report the application time to the network, and in some other aspects, the application time may be defined in the wireless communication standard.

[0115] Some aspects described herein for facilitating downlink reception in an uplink subband may extend the functionality of SBFD communications, thereby providing an increased uplink duty cycle (relative to full-band communications), thereby achieving latency reduction (because downlink signaling may be received in an uplink timeslot) and improved uplink coverage. In addition, some aspects may provide enhanced system capabilities, resource utilization, and spectral efficiency. Still further, some aspects may extend SBFD communications, thereby providing flexible and dynamic uplink / downlink resource adaptation based on uplink / downlink traffic in a robust manner.

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

[0117] Figure 7 is a diagram illustrating an example 700 of downlink reception in an uplink subband according to the present disclosure. Figure 7 As shown, UE 702 and network node 704 can communicate with each other. UE 702 can be, can be similar to, can include, or can be included in: Figure 6 UE1 and / or UE2 depicted in 4A to 4D UE 402 and / or Figures 1 to 3 UE 120 depicted in . The network node 704 may be, may be similar to, may include, or may be included in: Figure 6 The network node 110 depicted in 4A to 4D The network node 404 depicted in Figure 1 to Figure 2 The network node 110 and / or Figure 3 One or more components of the decomposed base station architecture 300 depicted in FIG.

[0118] As indicated by reference numeral 706, the UE 702 may send capability information and the network node 704 may receive the capability information. The capability information may indicate the capability of the UE 702 for downlink reception in the uplink subband 708. In some aspects, the capability information may indicate the capability of the UE 702 to be scheduled for downlink reception in the uplink subband. In some aspects, the capability information may indicate the capability of the UE 702 to measure cross-link interference based on downlink scheduling in the uplink subband 708 and the capability of the UE 702 to be scheduled for downlink reception in the uplink subband 708. In some aspects, the capability information may include a first indication indicating the capability of the UE 702 to measure cross-link interference based on downlink scheduling in the uplink subband 708, and a second indication indicating the capability of the UE 702 to be scheduled for downlink reception in the uplink subband 708. In some aspects, the capability information may include a single indication associated with downlink reception in the uplink subband 708.

[0119] As indicated by reference numeral 710, the network node 704 may send configuration information and the UE 702 may receive the configuration information. The configuration information may be associated with downlink reception in an uplink subband 708 corresponding to an SBFD-aware configuration. In some aspects, the SBFD-aware configuration may configure one or more attributes of the uplink subband 708, one or more guard bands 712, and / or one or more downlink subbands 714, among others. In some aspects, the configuration information may be based on capability information.

[0120] As shown by reference numeral 716, the network node 704 may send a DCI 718, and the UE 702 may receive the DCI. In some aspects, the DCI 718 may be received in a downlink subband 714. The DCI 718 may schedule a downlink communication 720. In some aspects, the DCI may schedule at least one of a PDSCH or a CSI-RS. In some aspects, the rate matching indication may include an explicit DCI bit field. In some aspects, the DCI may include a rate matching indication that the UE 702 does not rate match around at least one of an uplink subband 708 or a guard band 712 associated with the uplink subband 708. In some aspects, the rate matching indication may be received in a CSI-RS and / or a corresponding CSI-RS resource information element. In some aspects, the rate matching indication may be an implicit indication based on at least one of a TDRA or a FDRA.

[0121] As indicated by reference numeral 722, the network node 704 may send a downlink communication 720 in the uplink subband 708, and the UE 702 may receive the downlink communication in the uplink subband. The downlink communication 720 may be sent and received based on the configuration information. In some aspects, the length of the scheduling offset associated with the downlink reception may be greater than the length of the application time. The application time may include a minimum time period between the DCI 718 and the first symbol of the downlink communication 720.

[0122] As indicated by reference numeral 724, the UE 702 may obtain a CLI measurement. For example, in some aspects, the UE 702 may not be capable of performing CLI measurements and DL reception simultaneously. The UE 702 may then measure CLI in the UL subband and may not receive DL communications in the DL subband. In some aspects, the UE 702 may be configured to measure CLI in both the UL subband and the DL subband. If the UE 702 indicates FDM capability (CLI reception + DL reception), the UE 702 may measure CLI in the UL subband and simultaneously receive DL in the DL subband.

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

[0124] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a UE in accordance with the present disclosure. Example process 800 is an example in which a UE (eg, UE 702) performs operations associated with downlink reception in an uplink subband.

[0125] like Figure 8 As shown, in some aspects, process 800 may include receiving configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration (block 810). For example, a UE (e.g., using Fig.10 The communication manager 1008 and / or receiving component 1002 depicted in FIG. 1004 may receive configuration information associated with downlink reception in an uplink subband corresponding to a SBFD-aware configuration, as described above.

[0126] like Figure 8 As further shown, in some aspects, process 800 may include receiving downlink communications in an uplink subband based on the configuration information (block 820). Fig.10 The communication manager 1008 and / or receiving component 1002 depicted in FIG. 1 may receive downlink communications in an uplink subband based on the configuration information, as described above.

[0127] Process 800 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.

[0128] In a first aspect, downlink communications are associated with inter-UE cross-link interference measurement operations. In a second aspect, either alone or in combination with the first aspect, downlink communications include PDSCH communications. In a third aspect, either alone or in combination with one or more of the first and second aspects, downlink communications include CSI-RS. In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 800 includes receiving a DCI that schedules downlink communications. In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 800 includes receiving a rate matching indication that indicates that the UE does not rate match the PDSCH around at least one of an uplink subband or a guard band associated with an uplink subband.

[0129] In a sixth aspect, alone or in combination with the fifth aspect, process 800 includes receiving a DCI including a rate matching indication. In a seventh aspect, alone or in combination with the sixth aspect, the rate matching indication includes an explicit DCI bit field. In some aspects, the DCI bit field indicates a symbol set as an SBFD symbol or a non-SBFD symbol. In some aspects, the DCI bit field activates or deactivates rate matching around at least one of an uplink subband or a guard band. In an eighth aspect, alone or in combination with one or more of the sixth to seventh aspects, the DCI schedules at least one of a PDSCH or a CSI-RS. In a ninth aspect, alone or in combination with one or more of the fifth to eighth aspects, process 800 includes receiving a CSI-RS corresponding to a channel state information reference signal (CSI-RS) resource information element including an indicator of a duplex mode.

[0130] In a tenth aspect, either alone or in combination with one or more of the fifth to ninth aspects, the rate matching indication is an implicit indication based on time domain resource allocation. In some aspects, process 800 includes determining, based on frequency domain resource allocation, that a set of frequency resources corresponding to at least one of an uplink subband or a guard band is a frequency resource available for downlink communication. In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the length of a scheduling offset associated with downlink reception is greater than or equal to the length of an application time, wherein the application time includes a minimum time period between downlink control information and a first symbol of downlink communication.

[0131] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the UE is not capable of performing cross-link interference (CLI) measurements in an uplink subband and a downlink subband simultaneously, and process 800 includes obtaining CLI measurements in only an uplink subband or in both a downlink and an uplink subband. In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the UE is capable of performing CLI measurements in an uplink subband and a downlink subband simultaneously, and process 800 includes obtaining a first CLI measurement associated with a downlink communication in an uplink subband and obtaining a second CLI measurement associated with an additional communication in a downlink subband.

[0132] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, process 800 includes sending capability information indicating the capability of the UE for downlink reception in an uplink subband, wherein the configuration information is based on the capability information. In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, process 800 includes: sending capability information indicating the capability of the UE to be scheduled for downlink reception in an uplink subband; and receiving downlink control information for scheduling downlink communications based on the capability information. In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 800 includes: sending capability information indicating the capability of the UE to measure cross-link interference in an uplink subband and the capability of the UE to be scheduled for downlink reception in an uplink subband, wherein the configuration information is based on the capability information; and receiving downlink control information for scheduling downlink communications based on the capability information. In a seventeenth aspect, alone or in combination with the sixteenth aspect, the capability information comprises a first indication indicating the capability of the UE to measure cross-link interference in an uplink subband, and a second indication indicating the capability of the UE to be scheduled for downlink reception in the uplink subband. In an eighteenth aspect, alone or in combination with the sixteenth aspect, the capability information comprises a single indication associated with downlink reception in an uplink subband.

[0133] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0134] Fig. 9is a diagram illustrating an example process 900 performed, for example, by a network node in accordance with the present disclosure. Example process 900 is an example in which a network node (eg, network node 704) performs operations associated with downlink reception in an uplink subband.

[0135] like Fig. 9 As shown, in some aspects, process 900 may include sending configuration information associated with downlink reception in an uplink subband corresponding to an SBFD-aware configuration (block 910). For example, a network node (e.g., using Fig.11 The communication manager 1108 and / or the transmitting component 1104 depicted in FIG. 1 may transmit configuration information associated with downlink reception in an uplink subband corresponding to a SBFD-aware configuration, as described above.

[0136] like Fig. 9 As further shown, in some aspects, process 900 may include sending downlink communications in an uplink subband based on the configuration information (block 920). Fig.11 The communication manager 1108 and / or the transmitting component 1104 depicted in FIG. 1 may transmit downlink communications in the uplink subband based on the configuration information, as described above.

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

[0138] In a first aspect, downlink communications are associated with inter-UE cross-link interference measurement operations. In a second aspect, either alone or in combination with the first aspect, downlink communications include physical downlink shared channel communications. In a third aspect, either alone or in combination with one or more of the first and second aspects, downlink communications include channel state information reference signals. In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 900 includes sending a DCI that schedules downlink communications.

[0139] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 900 includes sending a rate matching indication indicating that the UE does not rate match the PDSCH around at least one of the uplink subband or the guard band associated with the uplink subband. In a sixth aspect, either alone or in combination with the fifth aspect, process 900 includes sending a DCI including a rate matching indication. In a seventh aspect, either alone or in combination with the sixth aspect, the rate matching indication includes an explicit DCI bit field. In some aspects, the DCI bit field indicates a symbol set as an SBFD symbol or a non-SBFD symbol. In some aspects, the DCI bit field activates or deactivates rate matching around at least one of the uplink subband or the guard band. In an eighth aspect, either alone or in combination with one or more of the sixth to seventh aspects, the DCI schedules at least one of a physical downlink shared channel or a channel state information reference signal. In a ninth aspect, either alone or in combination with one or more of the fifth to eighth aspects, process 900 includes sending a CSI-RS corresponding to a CSI-RS resource information element including an indicator of a duplex mode. In a tenth aspect, either alone or in combination with one or more of the fifth to ninth aspects, the rate matching indication is an implicit indication based on a time domain resource allocation.

[0140] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the length of the scheduling offset associated with the downlink reception is greater than the length of the application time, wherein the application time includes a minimum time period between the downlink control information and the first symbol of the downlink communication. In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the UE is not capable of performing CLI measurements and downlink reception simultaneously, wherein the downlink communication is associated with CLI measurements in only an uplink subband or in both a downlink and an uplink subband. In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the UE is capable of performing CLI measurements and downlink reception simultaneously, wherein process 900 includes receiving additional communications in the downlink subband.

[0141] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the process 900 includes receiving capability information indicating the capability of the UE for downlink reception in an uplink subband, wherein the configuration information is based on the capability information. In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the process 900 includes: receiving capability information indicating the capability of the UE to be scheduled for downlink reception in an uplink subband; and sending downlink control information for scheduling downlink communications based on the capability information. In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the process 900 includes: receiving capability information indicating the capability of the UE to measure cross-link interference based on downlink scheduling in an uplink subband and the capability of the UE to be scheduled for downlink reception in an uplink subband, wherein the configuration information is based on the capability information; and sending downlink control information for scheduling downlink communications based on the capability information. In a seventeenth aspect, alone or in combination with the sixteenth aspect, the capability information comprises a first indication indicating the capability of the UE to measure cross-link interference based on downlink scheduling in an uplink subband, and a second indication indicating the capability of the UE to be scheduled for downlink reception in the uplink subband. In an eighteenth aspect, alone or in combination with the sixteenth aspect, the capability information comprises a single indication associated with downlink reception in an uplink subband.

[0142] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0143] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication apparatus) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 1008.

[0144] In some aspects, the apparatus 1000 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.10 The device 1000 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set 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 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.

[0145] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 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 the one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0146] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 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 device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0147] In some examples, the means for sending, outputting, or transmitting (or the means for outputting for sending) may include the above-mentioned Figure 2One or more antennas, modulators, transmit MIMO processors, transmit processors, or a combination thereof of a UE are described.

[0148] In some examples, the means for receiving (or the means for obtaining) may include the above in combination with Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, or a combination thereof of a UE are described.

[0149] In some cases, a device may not actually send, for example, signals and / or data, but may have an interface (components for outputting) for outputting signals and / or data for transmission. For example, a processor may output signals and / or data to an RF front end via a bus interface for transmission. Similarly, a device may not actually receive signals and / or data, but may have an interface (components for obtaining) for obtaining signals and / or data received from another device. For example, a processor may obtain (or receive) signals and / or data from an RF front end via a bus interface for reception. In various aspects, the RF front end may include various components, including, for example, Figure 2 The transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc. described in the examples.

[0150] The communication manager 1008 and / or the receiving component 1002 may receive configuration information associated with downlink reception in an uplink subband corresponding to a subband full-duplex (SBFD) aware configuration. In some aspects, the communication manager 1008 may include in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the communication manager 1008 may include a receiving component 1002 and / or a sending component 1004. In some aspects, the communication manager 1008 may be Figure 1 and Figure 2 The communication manager 140 depicted in , may be similar to, may include, or may be included in, the communication manager.

[0151] The communication manager 1008 and / or the receiving component 1002 may receive downlink communications in a flexible uplink subband based on the configuration information. The communication manager 1008 and / or the receiving component 1002 may receive a DCI that schedules downlink communications. The communication manager 1008 and / or the receiving component 1002 may receive a rate matching indication that indicates that the UE does not rate match around at least one of the uplink subband or a guard band associated with the uplink subband. The communication manager 1008 and / or the receiving component 1002 may receive a DCI that includes a rate matching indication. The communication manager 1008 and / or the receiving component 1002 may receive a CSI-RS corresponding to a CSI-RS resource information element that includes a rate matching indication.

[0152] The communication manager 1008 and / or the transmitting component 1004 may transmit capability information indicating the capability of the UE for downlink reception in the uplink subband, wherein the configuration information is based on the capability information. The communication manager 1008 and / or the transmitting component 1004 may transmit capability information indicating the capability of the UE to be scheduled for downlink reception in the uplink subband. The communication manager 1008 and / or the receiving component 1002 may receive downlink control information for scheduling downlink communications based on the capability information. The communication manager 1008 and / or the transmitting component 1004 may transmit capability information indicating the capability of the UE to measure cross-link interference based on downlink scheduling in the uplink subband and the capability of the UE to be scheduled for downlink reception in the uplink subband, wherein the configuration information is based on the capability information. The communication manager 1008 and / or the receiving component 1002 may receive downlink control information for scheduling downlink communications based on the capability information.

[0153] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The illustrated set of component(s) may be described as being executable by Fig.10 Another collection of components shown performs one or more functions.

[0154] Fig.111 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a network node, or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication apparatus) using receiving component 1102 and sending component 1104. As further shown, apparatus 1100 may include a communication manager 1108.

[0155] In some aspects, the apparatus 1100 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set 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 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.

[0156] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1106. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 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 the one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0157] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 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 device 1106. In some aspects, the transmitting component 1104 may include combining 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 transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0158] In some examples, a component for sending, outputting, or transmitting (or a component for outputting for sending) may include the above in combination with Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, or a combination thereof, of the described network nodes.

[0159] In some examples, the means for receiving (or the means for obtaining) may include the above-mentioned Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, or a combination thereof, of the described network nodes.

[0160] In some cases, a device may not actually send, for example, signals and / or data, but may have an interface (components for outputting) for outputting signals and / or data for transmission. For example, a processor may output signals and / or data to an RF front end via a bus interface for transmission. Similarly, a device may not actually receive signals and / or data, but may have an interface (components for obtaining) for obtaining signals and / or data received from another device. For example, a processor may obtain (or receive) signals and / or data from an RF front end via a bus interface for reception. In various aspects, the RF front end may include various components, including, for example, Figure 2 The transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc. described in the examples.

[0161] The communication manager 1108 and / or the transmitting component 1104 may transmit configuration information associated with downlink reception in an uplink subband corresponding to the SBFD-aware configuration. In some aspects, the communication manager 1108 may include in conjunction with Figure 2One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the communications manager 1108 may include a receiving component 1102 and / or a sending component 1104. In some aspects, the communications manager 1108 may be Figure 1 and Figure 2 The communications manager 150 depicted in , may be similar to, may include, or may be included in, the communications manager.

[0162] The communication manager 1108 and / or the transmitting component 1104 may transmit downlink communications in the uplink subband based on the configuration information. The communication manager 1108 and / or the transmitting component 1104 may transmit DCI that schedules downlink communications. The communication manager 1108 and / or the transmitting component 1104 may transmit a rate matching indication that indicates that the UE does not rate match around at least one of the uplink subband or the guard band associated with the uplink subband. The communication manager 1108 and / or the transmitting component 1104 may transmit a DCI that includes the rate matching indication. The communication manager 1108 and / or the transmitting component 1104 may transmit a CSI-RS corresponding to the CSI-RS resource information element that includes the rate matching indication.

[0163] The communication manager 1108 and / or the receiving component 1102 may receive capability information indicating the capability of the UE for downlink reception in the uplink subband, wherein the configuration information is based on the capability information. The communication manager 1108 and / or the receiving component 1102 may receive capability information indicating the capability of the UE to be scheduled for downlink reception in the uplink subband. The communication manager 1108 and / or the sending component 1104 may send downlink control information for scheduling downlink communications based on the capability information. The communication manager 1108 and / or the receiving component 1102 may receive capability information indicating the capability of the UE to measure cross-link interference based on downlink scheduling in the uplink subband and the capability of the UE to be scheduled for downlink reception in the uplink subband, wherein the configuration information is based on the capability information. The communication manager 1108 and / or the sending component 1104 may send downlink control information for scheduling downlink communications based on the capability information.

[0164] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11The illustrated set of component(s) may be described as being executable by Fig.11 Another collection of components shown performs one or more functions.

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

[0166] Aspect 1: A method of wireless communication performed by a device at a user equipment (UE), comprising: receiving configuration information associated with downlink reception in an uplink subband corresponding to a sub-band full-duplex (SBFD) aware configuration; and receiving downlink communication in the uplink subband based on the configuration information.

[0167] Aspect 2: The method according to aspect 1, wherein the downlink communication is associated with an inter-UE cross-link interference (CLI) measurement operation.

[0168] Aspect 3: The method according to any one of aspects 1 or 2, wherein the downlink communication comprises a physical downlink shared channel (PDSCH) communication.

[0169] Aspect 4: The method according to any one of aspects 1 to 3, wherein the downlink communication includes a channel state information reference signal (CSI-RS).

[0170] Aspect 5: The method according to any one of aspects 1 to 4 further includes receiving downlink control information (DCI) scheduling the downlink communication.

[0171] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the downlink communication includes a physical downlink shared channel (PDSCH) communication, and the method further includes receiving a rate matching indication, wherein the rate matching indication indicates that the UE does not rate match the PDSCH around at least one of the uplink subband or a guard band associated with the uplink subband.

[0172] Aspect 7: The method according to aspect 6 also includes receiving downlink control information (DCI) including the rate matching indication.

[0173] Aspect 8: The method according to aspect 7, wherein the rate matching indication includes an explicit DCI bit field.

[0174] Aspect 9: The method according to aspect 8, wherein the DCI bit field indicates a set of symbols as SBFD symbols or non-SBFD symbols.

[0175] Aspect 10: The method according to any one of aspects 8 or 9, wherein the DCI bit field activates or deactivates rate matching around the at least one of the uplink subband or the guard band.

[0176] Aspect 11: The method according to any one of aspects 7 to 10, wherein the DCI schedules at least one of a physical downlink shared channel or a channel state information reference signal.

[0177] Aspect 12: The method according to any one of aspects 6 to 11 further comprises receiving a channel state information reference signal (CSI-RS) corresponding to a CSI-RS resource information element including an indicator of a duplex mode.

[0178] Aspect 13: The method according to any one of aspects 6 to 12, wherein the rate matching indication is an implicit indication based on time domain resource allocation.

[0179] Aspect 14: The method according to any one of Aspects 6 to 13 further includes determining, based on frequency domain resource allocation, that a frequency resource set corresponding to at least one of the uplink subband or the guard band is a frequency resource that can be used for the downlink communication.

[0180] Aspect 15: A method according to any one of Aspects 6 to 14, wherein the length of the scheduling offset associated with the downlink reception is greater than or equal to the length of an application time, wherein the application time includes a minimum time period between downlink control information and the first symbol of the downlink communication.

[0181] Aspect 16: A method according to any one of Aspects 1 to 15, wherein the UE is not capable of simultaneously performing cross-link interference (CLI) measurement uplink and downlink reception, and the method also includes obtaining CLI measurements in only an uplink subband or in both downlink and uplink subbands.

[0182] Aspect 17: A method according to any one of Aspects 1 to 15, wherein the UE is capable of performing cross-link interference (CLI) measurement and downlink reception simultaneously, and the method also includes obtaining CLI measurement in the uplink subband and receiving downlink communication in the downlink subband.

[0183] Aspect 18: The method according to any one of aspects 1 to 17 further includes sending capability information indicating the capability of the UE for downlink reception in the uplink subband, wherein the configuration information is based on the capability information.

[0184] Aspect 19: The method according to any one of Aspects 1 to 18 further includes: sending capability information indicating the ability of the UE to be scheduled for downlink reception in the uplink subband; and receiving downlink control information for scheduling the downlink communication based on the capability information.

[0185] Aspect 20: The method according to any one of Aspects 1 to 19 further includes: sending capability information indicating the UE's ability to measure cross-link interference in the uplink subband and the UE's ability to be scheduled for downlink reception in the uplink subband, wherein the configuration information is based on the capability information; and receiving downlink control information for scheduling the downlink communication based on the capability information.

[0186] Aspect 21: A method according to Aspect 20, wherein the capability information includes a first indication indicating the capability of the UE to measure cross-link interference in the uplink subband, and a second indication indicating the capability of the UE to be scheduled for downlink reception in the uplink subband.

[0187] Aspect 22: The method according to aspect 20, wherein the capability information includes a single indication associated with downlink reception in the uplink sub-band.

[0188] Aspect 23: A method of wireless communication performed by a device at a network node, comprising: sending configuration information associated with downlink reception in an uplink subband corresponding to a sub-band full-duplex (SBFD) aware configuration; and sending downlink communications in the uplink subband based on the configuration information.

[0189] Aspect 24: The method according to aspect 23, wherein the downlink communication is associated with an inter-UE cross-link interference (CLI) measurement operation.

[0190] Aspect 25: A method according to any one of aspects 23 or 24, wherein the downlink communication comprises a physical downlink shared channel (PDSCH) communication.

[0191] Aspect 26: A method according to any one of aspects 23 to 25, wherein the downlink communication includes a channel state information reference signal (CSI-RS).

[0192] Aspect 27: The method according to any one of Aspects 23 to 26 further includes sending downlink control information (DCI) scheduling the downlink communication.

[0193] Aspect 28: A method according to any one of Aspects 23 to 27, wherein the downlink communication includes a physical downlink shared channel (PDSCH) communication, and the method further includes sending a rate matching indication, wherein the rate matching indication indicates that the UE does not rate match the PDSCH around at least one of the uplink subband or a guard band associated with the uplink subband.

[0194] Aspect 29: The method according to aspect 28 further includes sending downlink control information (DCI) including the rate matching indication.

[0195] Aspect 30: The method according to aspect 29, wherein the rate matching indication comprises an explicit DCI bit field.

[0196] Aspect 33: A method according to any one of aspects 29 to 32, wherein the DCI schedules at least one of a physical downlink shared channel or a channel state information reference signal.

[0197] Aspect 34: The method according to any one of aspects 28 to 33 further comprises transmitting a channel state information reference signal (CSI-RS) corresponding to a CSI-RS resource information element including an indicator of a duplex mode.

[0198] Aspect 35: The method according to any one of aspects 28 to 34, wherein the rate matching indication is an implicit indication based on time domain resource allocation.

[0199] Aspect 36: A method according to any one of Aspects 23 to 35, wherein the length of the scheduling offset associated with the downlink reception is greater than or equal to the length of an application time, wherein the application time includes a minimum time period between downlink control information and the first symbol of the downlink communication.

[0200] Aspect 37: A method according to any one of Aspects 23 to 36, wherein the UE is not capable of performing cross-link interference (CLI) measurements and downlink reception simultaneously, wherein the downlink communication is associated with CLI measurements in only an uplink subband or in both downlink and uplink subbands.

[0201] Aspect 38: A method according to any one of Aspects 23 to 36, wherein the UE is capable of performing cross-link interference (CLI) measurement and downlink reception simultaneously, wherein the downlink communication is associated with the CLI measurement in the uplink subband, and the method also includes sending additional communications in the downlink subband.

[0202] Aspect 39: The method according to any one of Aspects 23 to 38 further includes receiving capability information indicating the capability of the UE for downlink reception in the uplink subband, wherein the configuration information is based on the capability information.

[0203] Aspect 40: The method according to any one of Aspects 23 to 39 further includes: receiving capability information indicating the ability of the UE to be scheduled for downlink reception in the uplink subband; and sending downlink control information scheduling the downlink communication based on the capability information.

[0204] Aspect 41: The method according to any one of Aspects 23 to 40 further includes: receiving capability information indicating the UE's ability to measure cross-link interference in the uplink subband and the UE's ability to be scheduled for downlink reception in the uplink subband, wherein the configuration information is based on the capability information; and sending downlink control information for scheduling the downlink communication based on the capability information.

[0205] Aspect 42: A method according to Aspect 41, wherein the capability information includes a first indication indicating the capability of the UE to measure cross-link interference in the uplink subband, and a second indication indicating the capability of the UE to be scheduled for downlink reception in the uplink subband.

[0206] Aspect 43: The method according to aspect 41, wherein the capability information includes a single indication associated with downlink reception in the uplink sub-band.

[0207] Aspect 44: An apparatus for wireless communication at a device, 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.

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

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

[0210] 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 1 to 22.

[0211] 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 1 to 22.

[0212] Aspect 49: An apparatus for wireless communication at a device, 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 43.

[0213] Aspect 50: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 23 to 43.

[0214] Aspect 51: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 23 to 43.

[0215] Aspect 52: 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 43.

[0216] Aspect 53: 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 43.

[0217] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0218] 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, procedures 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 hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0219] As used herein, "satisfying a threshold" may refer to a value being 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.

[0220] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (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).

[0221] 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 article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, 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, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", 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 user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the UE to: receiving configuration information associated with downlink reception in an uplink sub-band corresponding to a sub-band full-duplex (SBFD) aware configuration; as well as Downlink communications are received in the uplink subband based on the configuration information.

2. The UE of claim 1, wherein the downlink communication is associated with an inter-UE cross-link interference (CLI) measurement operation.

3. The UE of claim 1, wherein the downlink communication comprises a physical downlink shared channel (PDSCH) communication.

4. The UE of claim 1, wherein the downlink communication comprises a channel state information reference signal (CSI-RS).

5. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to receive downlink control information (DCI) scheduling the downlink communication.

6. A UE according to claim 1, wherein the downlink communication includes a physical downlink shared channel (PDSCH) communication, and wherein the one or more processors are further configured to cause the UE to receive a rate matching indication, wherein the rate matching indication indicates that the UE does not rate match the PDSCH around at least one of the uplink subband or a guard band associated with the uplink subband.

7. The UE of claim 6, wherein the one or more processors are further configured to cause the UE to receive downlink control information (DCI) including the rate matching indication.

8. The UE of claim 7, wherein the rate matching indication comprises an explicit DCI bit field.

9. The UE of claim 8, wherein the DCI bit field indicates a set of symbols as SBFD symbols or non-SBFD symbols.

10. The UE of claim 8, wherein the DCI bit field activates or deactivates rate matching around the at least one of the uplink subband or the guard band.

11. The UE according to claim 7, wherein the DCI schedules at least one of a physical downlink shared channel or a channel state information reference signal.

12. The UE of claim 6, wherein the one or more processors are further configured to cause the UE to receive a channel state information reference signal (CSI-RS) corresponding to a CSI-RS resource information element including an indicator of a duplex mode.

13. The UE according to claim 6, wherein the rate matching indication is an implicit indication based on time domain resource allocation.

14. The UE according to claim 6, wherein the one or more processors are further configured to enable the UE to determine, based on frequency domain resource allocation, that a frequency resource set corresponding to the at least one of the uplink subband or the guard band is a frequency resource that can be used for the downlink communication.

15. The UE of claim 1, wherein a length of a scheduling offset associated with the downlink reception is greater than or equal to a length of an application time, wherein the application time comprises a minimum time period between downlink control information and a first symbol of the downlink communication.

16. The UE of claim 1, wherein the UE is not capable of performing cross-link interference (CLI) measurements and downlink reception simultaneously, and wherein the one or more processors are further configured to enable the UE to obtain CLI measurements in an uplink subband only or in a downlink and uplink subband.

17. The UE of claim 1, wherein the UE is capable of performing cross-link interference (CLI) measurements and downlink reception simultaneously, and wherein the one or more processors are further configured to enable the UE to obtain CLI measurements in the uplink subband and receive downlink communications in the downlink subband.

18. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to send capability information indicating a capability of the UE for downlink reception in the uplink subband, wherein the configuration information is based on the capability information.

19. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: sending capability information indicating a capability of the UE to be scheduled for downlink reception in the uplink subband; and Downlink control information scheduling the downlink communication is received based on the capability information.

20. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: transmitting capability information indicating a capability of the UE to measure cross-link interference in the uplink subband and a capability of the UE to be scheduled for downlink reception in the uplink subband, wherein the configuration information is based on the capability information; and Downlink control information scheduling the downlink communication is received based on the capability information.

21. The UE of claim 20, wherein the capability information comprises a first indication indicating the capability of the UE to measure cross-link interference in the uplink subband, and a second indication indicating the capability of the UE to be scheduled for downlink reception in the uplink subband.

22. The UE of claim 20, wherein the capability information comprises a single indication associated with downlink reception in the uplink subband.

23. A network node for wireless communication, comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: transmitting, to a user equipment (UE), configuration information associated with downlink reception in an uplink subband corresponding to a sub-band full-duplex (SBFD) aware configuration; and Downlink communications are sent in the uplink subband based on the configuration information.

24. The network node of claim 23, wherein a length of a scheduling offset associated with the downlink reception is greater than or equal to a length of an application time, wherein the application time comprises a minimum time period between downlink control information and a first symbol of the downlink communication.

25. The network node of claim 23, wherein the UE is capable of simultaneous cross-link interference (CLI) measurements and downlink reception, wherein the downlink communication is associated with the CLI measurement in the uplink subband, and wherein the one or more processors are configured to send additional communications in the downlink subband.

26. The network node of claim 23, wherein the one or more processors are further configured to cause the network node to receive capability information indicating a capability of the UE for downlink reception in the uplink subband, wherein the configuration information is based on the capability information.

27. A method of wireless communication performed by an apparatus at a user equipment (UE), comprising: receiving configuration information associated with downlink reception in an uplink sub-band corresponding to a sub-band full-duplex (SBFD) aware configuration; as well as Downlink communications are received in the uplink subband based on the configuration information.

28. The method of claim 27, wherein a length of a scheduling offset associated with the downlink reception is greater than or equal to a length of an application time, wherein the application time comprises a minimum time period between downlink control information and a first symbol of the downlink communication.

29. A method of wireless communication performed by an apparatus at a network node, comprising: transmitting configuration information associated with downlink reception in an uplink sub-band corresponding to a sub-band full-duplex (SBFD) aware configuration; as well as Downlink communications are sent in the uplink subband based on the configuration information.

30. The method of claim 29, wherein a length of a scheduling offset associated with the downlink reception is greater than or equal to a length of an application time, wherein the application time comprises a minimum time period between downlink control information and a first symbol of the downlink communication.

Images