Full duplex eligibility or prioritization

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal. The network node may schedule communications of the user equipment based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full duplex configuration. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 934,728, filed on September 23, 2022, entitled “FULL-DUPLEX ELIGIBILITY OR PRIORITIZATION” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for full duplex qualification or prioritization. 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 network node for wireless communication. The network node may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal. The one or more processors may be configured to schedule communications for a UE based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to output an indication of a resource type of a resource. The one or more processors may be configured to output a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction. The one or more processors may be configured to perform communication with a UE according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

[0009] Some aspects described herein relate to a UE for wireless communication. The user equipment may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal. The one or more processors may be configured to perform communication with a network node based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0010] Some aspects described herein relate to a UE for wireless communication. The UE may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a resource type of a resource. The one or more processors may be configured to receive a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction. The one or more processors may be configured to perform communication with a network node according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

[0011] 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 identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal. The instruction set, when executed by one or more processors of the network node, may cause the network node to schedule communications for a UE based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[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 output an indication of a resource type of a resource. The instruction set, when executed by one or more processors of the network node, may cause the network node to output a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction. The instruction set, when executed by one or more processors of the network node, may cause the network node to perform communication with a UE according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction will be used for the resource.

[0013] 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 identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal. The instruction set, when executed by one or more processors of the UE, may cause the UE to perform communication with a network node based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by one or more instructions when executed by one or more processors of a UE. The instruction set, when executed by one or more processors of the one or more instructions, may cause the one or more instructions to receive an indication of a resource type of a resource when executed by the one or more processors of the UE. The instruction set, when executed by one or more processors of the one or more instructions, may cause the one or more instructions to receive a resource configuration for uplink or downlink communication on the resource when executed by the one or more processors of the UE, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction. The instruction set, when executed by one or more processors of the one or more instructions, may cause the one or more instructions to perform communication with a network node according to a prioritization rule when executed by the one or more processors of the UE, the prioritization rule indicating whether the first link direction or the second link direction will be used for the resource.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal. The apparatus may include means for scheduling communications of a UE based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for outputting an indication of a resource type of a resource. The apparatus may include components for outputting a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction. The apparatus may include components for performing communication with a UE according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal. The apparatus may include means for performing communication with a network node based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a resource type of a resource. The apparatus may include means for receiving a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction. The apparatus may include means for performing communication with a network node according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

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

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

[0021] 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 for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0026] Figure 4 is a diagram illustrating an example of full-duplex communication in a wireless network according to the present disclosure.

[0027] Figure 5 is a diagram illustrating an example of a sub-band full-duplex scheme according to the present disclosure.

[0028] FIG. 6A to FIG. 6D is a diagram illustrating an example of full-duplex communication according to the present disclosure.

[0029] Figure 7 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0030] Figure 8 is a diagram illustrating an example of signaling associated with an indication of whether a first downlink channel or a reference signal is permitted to overlap in time with a second uplink channel or a reference signal in a full-duplex configuration according to the present disclosure.

[0031] Fig. 9 is a diagram illustrating an example of signaling associated with prioritization rules for overlapping full-duplex communications according to the present disclosure.

[0032] Figures 10 to 13 is a flow chart illustrating an example process for wireless communication according to the present disclosure.

[0033] Figure 14 to Figure 15 is a diagram illustrating an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION

[0034] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, 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 practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0051] In some aspects, the network node 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; and schedule communications for the UE based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0052] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may output an indication of a resource type for a resource; output a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction and the resource type for the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction; and perform communication with the UE according to a prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0053] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, communication manager 140 may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; and perform communications with a network node based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0054] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive an indication of a resource type for a resource; receive a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction and the resource type for the resource indicates one of a resource type for a second link direction different from the first link direction or a flexible resource type; and perform communication with a network node according to a prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

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

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

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

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

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

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

[0061] 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 4 to 15 )Aspects of any of the methods described herein.

[0062] 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 4 to 15 )Aspects of any of the methods described herein.

[0063] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the network node 110 may perform one or more techniques associated with full-duplex communication, 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 Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 1300 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, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), the one or more instructions may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 The process 1300 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.

[0064] In some aspects, the network node includes a component for identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; and / or a component for scheduling communications of the UE based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration. Means for the network node to perform 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.

[0065] In some aspects, the network node includes a component for outputting an indication of a resource type of a resource; a component for outputting a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates one of a resource type or a flexible resource type for a second link direction different from the first link direction; and / or a component for performing communication with the UE according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource. The means for the network node to perform operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0066] In some aspects, the UE includes means for identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; and / or means for performing communications with a network node based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration. Means for the UE to perform operations described herein may include, for example, one or more of the following: communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0067] In some aspects, the UE includes components for receiving an indication of a resource type for a resource; components for receiving a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates a resource type for a second link direction different from the first link direction or one of a flexible resource type; and / or components for performing communications with a network node according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communications 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. Although Figure 2The blocks in the 200 and 210 are shown as distinct components, but the functionality described above with respect to the 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.

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

[0069] 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) that perform base station functionality 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).

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

[0071] Base station type operations or network designs may take into account the aggregated nature of base station functionality. 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 functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual 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.

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

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

[0074] 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 functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some 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.

[0075] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, 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.

[0076] Each RU 340 may implement lower layer functionality. 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).

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

[0078] 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 communicate 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.

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

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

[0081] Figure 4 400, 405, and 410 are diagrams illustrating examples of full-duplex communication in a wireless network according to the present disclosure. "Full-duplex communication" in a wireless network refers to simultaneous bidirectional communication between devices in the wireless network. For example, a UE operating in full-duplex mode may send uplink communications and receive downlink communications at the same time (e.g., in the same time slot or the same symbol). "Half-duplex communication" in a wireless network refers to unidirectional communication (e.g., only downlink communication or only uplink communication) between devices at a given time (e.g., in a given time slot or a given symbol).

[0082] like Figure 4As shown, examples 400 and 405 illustrate examples of in-band full-duplex (IBFD) communications. In IBFD, a UE may send uplink communications to a network node and receive downlink communications from the network node on the same time resources and frequency resources. As shown in example 400, in a first example of IBFD, the time resources and frequency resources used for uplink communications may completely overlap with the time resources and frequency resources used for downlink communications. As shown in example 405, in a second example of IBFD, the time resources and frequency resources used for uplink communications may partially overlap with the time resources and frequency resources used for downlink communications.

[0083] like Figure 4 As further shown, example 410 illustrates an example of sub-band full-duplex (SBFD) communication, which may also be referred to as "sub-band frequency division duplex (SBFDD)" or "flexible duplex". In SBFD, a UE may send uplink communications to a network node and receive downlink communications from the network node on the same time resources but on different frequency resources. Alternatively, the network node may receive uplink communications from a first UE on an uplink frequency resource and may send downlink communications to a second UE on a downlink frequency resource. For example, the different frequency resources may be sub-bands of a frequency band such as a time division duplex band. In some examples, the frequency resources used for downlink communications may be separated from the frequency resources used for uplink communications in the frequency domain by a guard band.

[0084] In some examples, a conflict may occur between a first communication or resource (on a first cell) of an SBFD scheme and a second communication or resource (which may be associated with the SBFD scheme and may be on a second cell). Some techniques described herein provide intra-band conflict resolution according to an intra-band conflict resolution rule for resolving such conflicts based on the relative priority of the first communication or resource and the second communication or resource.

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

[0086] Figure 55 is a diagram illustrating an example 500 of an SBFD scheme according to the present disclosure. Example 500 illustrates a first SBFD scheme 505 and a second SBFD scheme 510. The first SBFD scheme 505 provides SBFD within a time division duplex (TDD) carrier, where the bandwidth of a single CC is divided into non-overlapping UL sub-bands and DL sub-bands. The second SBFD scheme 510 provides SBFD across multiple carriers using different TDD configurations (e.g., intra-band carrier aggregation (CA)). For example, CC1 and CC3 may have the same TDD configuration (e.g., DUDD, indicating that the first time slot is a DL time slot, the second time slot is a UL time slot, and the third time slot and the fourth time slot are DL time slots), and CC2 may be configured as an uplink carrier.

[0087] The TDD configuration may include a cell-common TDD configuration or a dedicated TDD configuration. The TDD configuration may be semi-statically configured via RRC signaling. The cell-common TDD configuration may be provided via the RRC parameter tdd-UL-DL-ConfigurationCommon and may be applicable to all UEs associated with the cell. The dedicated TDD configuration may be provided via the RRC parameter tdd-UL-DL-ConfigurationDedicated and may be applicable to the UE pointed to by the dedicated TDD configuration. Resources may also be semi-statically configured as flexible resources (e.g., with a flexible resource type), referred to herein as RRC-F resources. After being configured as semi-statically configured resources, flexible resources (e.g., RRC-F) (such as symbols of a time slot) may then be indicated as uplink resources (e.g., resources with an uplink resource type), downlink resources (e.g., resources with a downlink resource type) or flexible resources by a time slot format indicator (SFI). The SFI includes an index into a table that identifies how each symbol number in a time slot should be configured (e.g., as an uplink resource, a downlink resource, or a flexible resource). Flexible resources indicated by the SFI as uplink resources (e.g., having an uplink resource type) are referred to as SFI-U resources. Flexible resources indicated by the SFI as downlink resources (e.g., having a downlink resource type) are referred to as SFI-D resources. Flexible resources indicated by the SFI as flexible resources are referred to as SFI-F resources. SFI-D resources (or more generally, resources having a downlink resource type) may have a downlink link direction. SFI-U resources (or more generally, resources having an uplink resource type) may have an uplink link direction.

[0088] In some aspects, resources may be configured for uplink or downlink communications via resource configuration. For example, resource configuration may be provided via higher layer (e.g., RRC) signaling. In some examples, resource configuration may configure resources for downlink communications, such as to receive PDSCH (e.g., via semi-persistent scheduling (SPS) configuration), physical downlink control channel (PDCCH) (e.g., in a control resource set (CORESET)), or channel state information reference signal (CSI-RS). In some aspects, resource configuration may configure resources for uplink communications, such as to send PUSCH (e.g., via a configured grant (CG)), physical uplink control channel (PUCCH), sounding reference signal (SRS), or PRACH. Resources configured for downlink communications via resource configuration may have a downlink link direction, and resources configured for uplink communications via resource configuration may have an uplink link direction.

[0089] Legacy rules (such as rules of wireless communication specifications) may indicate how a resource with a given link direction should be handled, the resource being configured with a resource configuration for uplink or downlink communication in the opposite link direction. For example, a network node (e.g., network node 110) (such as a network node associated with a first TRP and a second TRP) may configure a resource by resource type. The network node may also configure the resource configuration on the resource by resource type. In some examples, the resource has a slot format indicated by an SFI (such as an SFI-D, SFI-U, or SFI-F). In some other examples, the first resource has a slot format (such as an RRC-F symbol) not indicated by an SFI. Alternatively, in some examples, a resource may be configured for downlink or uplink communication via dynamic grants. Examples of legacy rules are provided below.

[0090] For symbols with a slot format indicated by the SFI, a configured PUSCH, PUCCH, or PRACH transmission on an SFI-D or SFI-F symbol may be canceled (e.g., the network node may not expect to receive the configured PUSCH, PUCCH, or PRACH transmission, and the UE may not send the transmission). For symbols with a slot format indicated by the SFI, a configured CSI-RS, SPS, or control resource set (CORESET) reception that overlaps an SFI-U or SFI-F symbol may be canceled. DL or UL dynamic grants may be allowed on SFI-F symbols so that the network node may dynamically instruct the UE to send or receive communications. A CORESET is a configured set of resources mapped to a search space set, where the UE monitors control information (such as PDCCH).

[0091] For RRC-F symbols that do not have a slot format indicated by SFI, configured PUSCH, PUCCH, or PRACH transmission on the RRC-F symbol may be canceled unless specific parameters are configured (e.g., EnableConfiguredUL-r16). Configured CSI-RS or SPS reception on the RRC-F symbol may be canceled. DL or UL dynamic grants and CORESET reception may be allowed on RRC-F symbols.

[0092] The above-mentioned legacy rules may be effective for network nodes that cannot receive and send communications simultaneously (e.g., in FD). However, some network nodes (such as multi-TRP network nodes and other examples) may support FD communications. If the above-mentioned rules are applied at a network node that supports FD, network resources may be utilized inefficiently. For example, a network node that supports FD communications may be able to receive transmissions or receptions on resources associated with a resource configuration and transmissions or receptions in the opposite link direction on resources associated with a time slot format indicated by an SFI or RRC configuration. Therefore, prioritization rules (such as the above-mentioned rules) configured based on the assumption of half-duplex capabilities may result in reduced throughput and reduced resource utilization efficiency.

[0093] Some of the techniques described herein provide configuration of resources associated with a flexible slot format or a slot format with a second link direction (in a full-duplex configuration, such as SBFD, partially overlapping FD, or completely overlapping FD), wherein the resource configuration indicates a channel or reference signal with a first link direction. Examples are provided below. Therefore, downlink reception opportunities and uplink transmission opportunities can coexist on the same resource (e.g., symbol, time slot). Some of the techniques described herein provide prioritization rules (e.g., based at least in part on the priority level of the communication on the resource) indicating which link direction in the first link direction or the second link direction is applied to the resource. The network node can perform communication with the UE according to the prioritization rules. Therefore, the UE and the network node can identify whether to perform or cancel communication (such as uplink transmission or downlink transmission) according to the prioritization rules, which enables configuration and utilization of resources with a slot format and communication with a configuration of the opposite link direction. In this way, throughput is increased and the efficiency of resource use is increased.

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

[0095] FIG. 6A to FIG. 6D600, 610, 620, 630 are diagrams illustrating examples of FD communication according to the present disclosure. FD communication is a communication that uses overlapping time resources at a single node (such as a UE or a network node) to send and receive. For example, the UE or 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 quasi-co-location (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 DCI) and / or semi-static services. Semi-static services are services associated with semi-persistent resources (such as SPS-configured resources or CGs).

[0096] Fig. 6A Example 600 includes UE1 602 and two network nodes (eg, TRPs) 604-1, 604-2, where UE1 602 is transmitting uplink transmissions to network node 604-1 and is receiving downlink transmissions from network node 604-2. FIG. 6A to FIG. 4 The network node 604 described in D may be a base station, a TRP, a RU, a DU, or a similar network node associated with (eg, managed by) a network node. FIG. 6A to FIG. 4 D. The UE 602 described may be combined Figure 1 , Figure 2 and Figure 3 UE 120 or similar UE described herein. Fig. 6A In the example 600 of , FD is enabled for UE1 602 but not for network nodes 604-1, 604-2. Therefore, network nodes 604-1 and 604-2 are half-duplex (HD) network nodes.

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

[0098] Figure 6C Example 620 includes UE1 602 and network node 604, where UE1 602 is receiving downlink transmissions from network node 604 and UE1 602 is sending uplink transmissions to network node 604. Figure 6C In example 620, FD is enabled for both UE 1602 and network node 604. Figure 6C In example 620, UE1 602 and network node 604 communicate using a beam pair. The beam pair may include a downlink beam and an uplink beam. For example, UE1 602 may communicate with network node 604 using a beam pair including a downlink beam at UE1 602 (i.e., a receive beam) and an uplink beam at UE1 602 (i.e., a transmit beam). Network node 604 may use a downlink beam at network node 604 (i.e., a transmit beam) to transmit communications received via the downlink beam of UE1 602, and may use an uplink beam at network node 604 (i.e., a receive beam) to receive communications transmitted via the uplink beam of UE1 602.

[0099] Fig.6D Example 630 includes a network node 110 and a cell (such as in conjunction with Figure 1 102) is associated with two network nodes 604-1 and 604-2. Network nodes 604-1 and 604-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).

[0100] exist FIG. 6A to FIG. 6D In , interference is indicated by dashed lines. Interference may occur between network nodes of examples 600, 610, 620, 630 (referred to as cross-link interference (CLI)). Fig. 6A In , the downlink transmission of network node 604-2 interferes with the uplink transmission of network node 604-1. Figure 6BIn the example, the uplink reception of network node 604-1 may be interfered by the transmission from network node 604-2. The CLI between network nodes 604 is referred to herein as inter-network node CLI. Figure 6B In some examples, the uplink transmission of UE2 602-2 may interfere with the downlink transmission of UE1 602-1 (not shown). Fig.6D In the example, the uplink transmission of UE2 602-2 interferes with the downlink transmission of UE1 602-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 6C Examples of self-interference at UE 602 (from uplink transmission to downlink reception) and at network node 604 (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.

[0101] As described below, some network nodes support sub-band full-duplex (SBFD) communication. SBFD communication may involve FD communication at the network node and HD communication at the UE, such as Figure 6B as shown in .

[0102] As indicated above, FIG. 6A to FIG. 6D are provided as examples. Other examples can be found in the FIG. 6A to FIG. 6D The examples described are different.

[0103] Figure 7 is a diagram illustrating an example 700 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 7 As shown, the downlink channel and the downlink reference signal may carry information from the network node 110 to the UE 120 , and the uplink channel and the uplink reference signal may carry information from the UE 120 to the network node 110 .

[0104] As shown, downlink channels may include a PDCCH carrying DCI, a PDSCH carrying downlink data, or a PBCH carrying system information, among other examples. In some aspects, PDSCH communications may be scheduled by PDCCH communications. As further shown, uplink channels may include a PUCCH carrying UCI, a PUSCH carrying uplink data, or a PRACH for initial network access, among other examples. In some aspects, UE 120 may send acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0105] As further shown in the figure, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS) or a phase tracking reference signal (PTRS), etc. As also shown in the figure, the uplink reference signal may include a sounding reference signal (SRS), a DMRS or a PTRS, etc.

[0106] The SSB may carry information used for initial network acquisition and synchronization, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and a PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the network node 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0107] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, beam management, channel state feedback, tracking reference signaling, beam failure detection, candidate beam selection, path loss reference signaling, measurement of layer 1 measurements such as layer 1 reference signal received power (L1-RSRP) or layer 1 signal to interference plus noise ratio (L1-SINR), or radio link monitoring, among other examples. The network node 110 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on these measurement results, the UE 120 may perform channel estimation and may report channel estimation parameters to the network node 110 (e.g., in a CSI report), such as a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or a reference signal received power (RSRP), among others. The network node 110 may use the CSI reports to select transmission parameters for downlink communications to the UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), modulation and coding scheme (MCS), or refine downlink beams (e.g., using a beam refinement procedure or a beam management procedure), etc. The CSI-RS may be periodic (e.g., configured with periodicity), aperiodic (e.g., triggered, transmitted on demand, dynamically scheduled), or semi-persistent (e.g., configured and activated, then transmitted until deactivated).

[0108] DMRS may carry information for estimating a radio channel to demodulate an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS may be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, may be beamformed, may be restricted to scheduled resources (e.g., rather than being sent over a wideband), and may be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0109] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0110] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the network node 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may need to detect downlink signals from multiple adjacent neighboring network nodes in order to perform OTDOA-based positioning. Therefore, the UE 120 may receive the PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on the OTD measurements associated with the PRS received from the multiple cells. In some aspects, the network node 110 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0111] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The network node 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured purposes, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The network node 110 may measure the SRS, may perform channel estimation based at least in part on these measurement results, and may use the SRS measurement results to configure communications with the UE 120. The SRS may be periodic (e.g., configured with periodicity), aperiodic (e.g., triggered, sent on demand, dynamically scheduled), or semi-persistent (e.g., configured and activated, then sent until deactivated).

[0112] In a FD configuration (sometimes referred to as "FD"), a first downlink channel or reference signal (such as Figure 7 One or more of the downlink channels or signals described herein) may be combined with a second uplink channel or reference signal (such as a reference signal Figure 7 1. The first downlink channel or reference signal and the second uplink channel or signal described in the present invention overlap with each other (one or more of the uplink channels or signals described in the present invention). For example, the first downlink channel or reference signal and the second downlink channel or signal may overlap at a network node (such as a network node operating in FD), a UE (such as a UE operating in FD), or both. However, even at an FD node (such as a network node or UE), there are overlapping channels or signal pairs (including a first downlink channel or reference signal and a second uplink channel or reference signal) that may be incompatible for overlapping. In addition, the channel or signal may be associated with a use case, as described elsewhere herein. Although for some use cases, it may be acceptable for the first channel or signal to overlap with the second channel or signal in FD, it may be unacceptable in other use cases (for example, because interference is acceptable in some use cases and unacceptable in other use cases, due to the relative priority of communication in one use case relative to another use case, etc.). Therefore, a general rule indicating whether any pair of downlink and uplink channels or signals can be scheduled or configured may be inappropriate in various situations, resulting in degradation of network communication, inability to effectively utilize the FD spectrum, and increased latency.

[0113] Some techniques described herein provide an identification of whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration. A full-duplex configuration may include a sub-band full-duplex configuration, an intra-band full-duplex configuration, a partially overlapping full-duplex configuration (where two channels or signals partially overlap each other), a fully overlapping full-duplex configuration (where two channels or signals completely overlap each other), and the like. For example, two signals or channels in a full-duplex configuration may overlap each other in at least one of time or frequency (e.g., both time and frequency). The identification may be based at least in part on at least one of a channel type or signal type of the first downlink channel or reference signal or a channel type or signal type of the second uplink channel or reference signal. The network node may schedule communications for the UE based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in a full-duplex configuration. The UE or network node may identify whether to allow the first downlink channel or reference signal to overlap with the second uplink channel or reference signal in time based at least in part on signaling from the UE, signaling from the network node, or rules (e.g., in wireless communication specifications). In some aspects, the identification may be based at least in part on the use case. For example, the identification may be based at least in part on the channel type or signal type and the use case of the first downlink channel or reference signal and the second uplink channel or reference signal. In this way, the permission for overlapping channels or signals can be configured on a per-pair basis (such as for different pairs of overlapping channels or signals) and / or by use case, which improves the utilization efficiency of the FD spectrum and reduces latency relative to avoiding overlap in channel or signal pairs.

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

[0115] Figure 8 800 is a diagram illustrating an example of signaling associated with an identification of whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration in accordance with the present disclosure. Example 800 includes a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE may be capable of FD communication. In some aspects, the network node may be capable of FD communication. In some aspects, both the UE and the network node may be capable of FD communication.

[0116] As shown by reference numeral 810, the UE and / or the network node may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration. The UE and / or the network node may perform the identification based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal, and / or based at least in part on a second channel type or reference signal type of the second uplink channel or reference signal. For example, the first downlink channel or reference signal may have a first channel type or a first signal type. The second uplink channel or reference signal may have a second channel type or a second signal type. The UE and / or the network node may identify whether a channel or signal of a first channel type or a reference signal type is permitted to overlap in time with a channel or signal of a second channel type or a reference signal type, and thereby may identify whether the first downlink channel or the reference signal is permitted to overlap in time with the second uplink channel or the reference signal. The overlap may be at the UE (e.g., a first downlink channel or reference signal scheduled for reception at the UE may overlap with a second downlink channel or signal scheduled for transmission by the UE), at the network node (e.g., a first downlink channel or reference signal scheduled for transmission by the network node may overlap with a second downlink channel or signal scheduled for reception by the network node), or both. For example, in some aspects, in a full-duplex configuration, based at least in part on the network node being a full-duplex network node, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the network node. Additionally or alternatively, in some aspects, in a full-duplex configuration, based at least in part on the UE being a full-duplex UE, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the UE.

[0117] In some aspects, the UE may send signaling (e.g., capability information, uplink control information, etc.) indicating whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in full duplex. In this example, the network node may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full duplex configuration based on signaling received from the UE. For example, the UE may send signaling indicating whether a first (downlink) channel type is permitted to overlap in time with a second (uplink) channel type. As another example, the UE may send signaling indicating whether a first (downlink) channel type is permitted to overlap in time with a second (uplink) signal type. As another example, the UE may send signaling indicating whether a first (downlink) signal type is permitted to overlap in time with a second (uplink) channel type. As another example, the UE may send signaling indicating whether a first (downlink) signal type is permitted to overlap in time with a second (uplink) channel type. As another example, the UE may send signaling indicating whether a first (downlink) signal type is permitted to overlap in time with a second (uplink) signal type. The signaling may be based at least in part on the capabilities of the UE, channel conditions at the UE, hardware configuration of the UE, and / or the like.

[0118] In some aspects, the network node may send signaling (e.g., RRC signaling, system information, MAC signaling, DCI, etc.) indicating whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in full duplex. In this example, the UE may identify whether the first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full duplex configuration based on the signaling received from the network node. For example, the network node may send signaling indicating whether a first (downlink) channel type is permitted to overlap in time with a second (uplink) channel type. As another example, the network node may send signaling indicating whether a first (downlink) channel type is permitted to overlap in time with a second (uplink) signal type. As another example, the network node may send signaling indicating whether a first (downlink) signal type is permitted to overlap in time with a second (uplink) channel type. As another example, the network node may send signaling indicating whether the first (downlink) signal type is permitted to overlap in time with the second (uplink) signal type. The signaling may be based at least in part on the capabilities of the UE, channel conditions at the UE, hardware configuration of the UE, etc.

[0119] In some aspects, the network node and the UE may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on a preconfigured rule, such as a rule of a wireless communication specification. The preconfigured rule may identify a specific overlapping pair of one or more channel types and / or one or more signal types, and may indicate whether a specific overlapping pair is permitted. As another example, the preconfigured rule may indicate one or more first channels or signal types that are not permitted to overlap in time with one or more second channels or signal types. As another example, the preconfigured rule may indicate one or more first channels or signal types that are permitted to overlap in time with one or more second channels or signal types.

[0120] In some aspects, the UE and the network node may be associated with a beam pair. In some aspects, the beam pair may include a UE-side beam and a network node-side beam. For example, the UE may use the UE-side beam to send FD communications to the network node and receive FD communications from the network node. The network node may use the network node-side beam to send FD communications to the UE and receive FD communications from the UE. In some aspects, the beam pair may include a transmit beam and a receive beam at the UE, and a transmit beam and a receive beam at the network node.

[0121] In some aspects, identifying whether to permit a first downlink channel or reference signal to overlap in time with a second uplink channel or reference signal in a full-duplex configuration is based at least in part on whether the first downlink channel or reference signal and the second uplink channel or reference signal are associated with a beam pair. For example, identifying whether to permit a first downlink channel or reference signal to overlap in time with a second uplink channel or reference signal in a full-duplex configuration may be based at least in part on the first downlink channel or reference signal being associated with a beam pair. More specifically, whether to permit a first downlink channel or reference signal to overlap in time with a second uplink channel or reference signal in a full-duplex configuration may depend on whether the first downlink channel or reference signal is to be transmitted using the same beam pair as the second uplink channel or reference signal. In some aspects, a first downlink channel or reference signal of a first channel type or reference signal type may be permitted to overlap in time with a second uplink channel or reference signal of a second channel type or reference signal type when the first downlink channel or reference signal is not associated with the same beam pair as the second uplink channel or reference signal, and the first downlink channel or reference signal may not be permitted to overlap in time with the second uplink channel or reference signal when the first downlink channel or reference signal and the second uplink channel or reference signal are associated with the same beam pair.

[0122] In some aspects, the first channel type or reference signal type is an SSB type. For example, a first downlink channel or reference signal having an SSB type may include an SSB. In some aspects, the first channel type or reference signal type is a PDCCH type. For example, a first downlink channel or reference signal having a PDCCH type may include a PDCCH. In some aspects, the first channel type or reference signal type is a PDSCH type. For example, a first downlink channel or reference signal having a PDSCH type may include a PDSCH. In some aspects, the first channel type or reference signal type is a CSI-RS type. For example, a first downlink channel or reference signal having a CSI-RS type may include a CSI-RS. In some aspects, the first channel type or reference signal type is a positioning reference signal (PRS) type. For example, a first downlink channel or reference signal having a PRS type may include a PRS. In some aspects, the PDSCH type may be a dynamically granted PDSCH type, corresponding to a PDSCH granted by a dynamic grant. In some aspects, the PDSCH type may be a semi-persistent scheduling PDSCH type, corresponding to a PDSCH granted by a semi-persistent scheduling configuration.

[0123] In some aspects, the CSI-RS type may be a periodic CSI-RS type, which is a CSI-RS associated with a periodic CSI-RS resource. In some aspects, the CSI-RS type may be an aperiodic CSI-RS type, which is a CSI-RS associated with an aperiodic CSI-RS resource, such as a triggered CSI-RS. In some aspects, the CSI-RS type may be a semi-persistent CSI-RS type, which is a CSI-RS associated with a semi-persistently scheduled CSI-RS resource. In some aspects, the CSI-RS type may be a channel state feedback (CSF) CSI-RS type, which is a CSI-RS used to determine the CSF. In some aspects, the CSI-RS type may be a beam management CSI-RS type, which is a CSI-RS used for beam management. In some aspects, the CSI-RS type may be a tracking reference signal (TRS) CSI-RS type, which is a CSI-RS used for tracking (e.g., frequency tracking and / or time tracking). In some aspects, the CSI-RS type may be a radio resource management (RRM) CSI-RS type, which is a CSI-RS used for RRM operations. In some aspects, the CSI-RS type may be a beam failure detection (BFD) CSI-RS type, which is a CSI-RS used for BFD and / or beam failure recovery. In some aspects, the CSI-RS type may be a candidate beam detection CSI-RS type, which is a CSI-RS used to detect a candidate beam at a UE. In some aspects, the CSI-RS type may be a path loss reference signal CSI-RS type, which is a CSI-RS used to perform path loss measurements. In some aspects, the CSI-RS type may be a layer 1 measurement CSI-RS type, which is a CSI-RS used to perform layer 1 measurements (such as L1-RSRP or L1-SINR). In some aspects, the CSI-RS type may be a radio link monitoring CSI-RS type, which is a CSI-RS used to perform radio link monitoring.

[0124] In some aspects, the second channel type or reference signal type is a PUCCH type. For example, a second uplink channel or reference signal having a PUCCH type may include a PUCCH. In some aspects, the second channel type or reference signal type is a PUSCH type. For example, a second uplink channel or reference signal having a PUSCH type may include a PUSCH. In some aspects, the second channel type or reference signal type is a PRACH type. For example, a second uplink channel or reference signal having a PRACH type may include a PRACH transmission. In some aspects, the second channel type or reference signal type is an SRS type. For example, a second uplink channel or reference signal having an SRS type may include an SRS. In some aspects, the second channel type or reference signal type is an uplink PRS type. For example, a second uplink channel or reference signal having an uplink PRS type may include an uplink PRS. In some aspects, the PUSCH type may be a dynamically granted PUSCH type, which corresponds to a PUSCH granted by a dynamic grant. In some aspects, the PUSCH type may be a configured granted PUSCH type, which corresponds to a PUSCH granted by a configured grant configuration. In some aspects, the PRACH type includes a dynamically scheduled PRACH type, which is a PRACH scheduled by dynamic signaling. In some aspects, the PRACH type includes a configured PRACH type, which is a PRACH on configured resources (e.g., contention-free PRACH).

[0125] In some aspects, the SRS type is a periodic SRS type, which is an SRS associated with a configured periodicity. In some aspects, the SRS type is an aperiodic SRS type, which is an SRS associated with an aperiodic SRS resource, such as a triggered SRS. In some aspects, the SRS type is a semi-persistent SRS type, which is an SRS associated with a semi-persistently scheduled SRS resource. In some aspects, the SRS type is a beam management SRS type, which is an SRS for beam management. In some aspects, the SRS type is an antenna switching SRS type, which is an SRS for antenna switching. In some aspects, the SRS type is a codebook-based uplink transmission SRS type, which is an SRS for selecting a codebook for uplink transmission based on a codebook. In some aspects, the SRS type is a non-codebook-based uplink transmission SRS type, which is an SRS for selecting a pre-decoder for uplink transmission based on a non-codebook.

[0126] In some aspects, identifying whether to permit a first downlink channel or reference signal to overlap in time with a second uplink channel or reference signal in a full-duplex configuration is based at least in part on a use case. For example, depending on a use case associated with the first channel type or reference signal type and / or the second channel type or reference signal type, the first channel type or reference signal type may be permitted to overlap in time with the second channel type or reference signal type in a full-duplex configuration. The use case may be associated with the first downlink channel or reference signal, the second uplink channel or reference signal, or both. As used herein, a "use case" refers to a scenario in which a first downlink channel or reference signal overlaps with a second uplink channel or reference signal.

[0127] In some aspects, the use case may be a SBFD use case, where at least one of the UE or the network node communicates using SBFD. In some aspects, the use case may be an SDM-based FD use case (such as a partially overlapping FD use case or a fully overlapping FD use case), where at least one of the UE or the network node communicates using SDM-based FD. In some aspects, the use case may be an intra-operator use case, where a first downlink channel or reference signal and a second uplink channel or reference signal are associated with the same operator. In some aspects, the use case may be an inter-operator use case (such as an inter-operator use case with a shared spectrum or with an adjacent spectrum), where a first downlink channel or reference signal is associated with a first operator and a second downlink channel or signal is associated with a second operator. In some aspects, the use case may be a legacy UE use case, where a UE (or another UE associated with a first downlink channel or reference signal or a second uplink channel or reference signal) is a legacy UE (e.g., a UE that does not support FD communications according to a particular standard). In some aspects, the use case may be a full-duplex aware UE use case, where the UE is aware of FD communication or can process FD communication as FD communication (e.g., a UE that supports FD communication according to a specific standard). In some aspects, the use case may be a use case associated with a specific frequency range (e.g., FR2 only, FR1 only), where the first downlink channel or reference signal and the second uplink channel or reference signal are associated with the same frequency range. In some aspects, the use case may be associated with a specific frequency band, where the first downlink channel or reference signal and the second uplink channel or reference signal are associated with the same frequency band. In some aspects, the use case may be associated with a specific frequency band combination, where the first downlink channel or reference signal is on the first frequency band of the specific frequency band combination and the second uplink channel or reference signal is on the second frequency band of the specific frequency band combination. In some aspects, the use case may be a full-duplex UE use case, where the UE supports FD communication. In some aspects, the use case may be a full-duplex network node use case, where the network node supports FD communication.

[0128] As shown by reference numeral 820, the network node may schedule or configure the communication of the UE (or another network node) based at least in part on whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in a full-duplex configuration. For example, if the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in full-duplex, the network node may configure or schedule the first downlink channel or reference signal and the second uplink channel or reference signal in full-duplex. As another example, if the first downlink channel or reference signal is not allowed to overlap in time with the second uplink channel or reference signal in full-duplex, the network node may configure the first downlink channel or reference signal so that in the full-duplex configuration, the first downlink channel or reference signal does not overlap with the second uplink channel or reference signal. As shown by reference numeral 830, the UE and the network node may communicate according to the scheduling or configuration. For example, the network node may send and the UE may receive the first downlink channel or reference signal. As another example, the UE may send and the network node may receive a second uplink channel or reference signal.

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

[0130] Fig. 9 900 is a diagram illustrating an example of signaling associated with a prioritization rule for communications having resource types and configurations according to the present disclosure. Example 900 includes a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the network node is capable of FD communications, such as using multiple TRPs. In some aspects, the UE is capable of FD communications. In some aspects, both the network node and the UE are capable of FD communications.

[0131] As shown in reference numeral 910, the network node may output an indication of a resource type for a resource. As shown in reference numeral 920, the network node may output a resource configuration for uplink or downlink communication on a resource. The resource configuration may have a first link direction. The resource type may indicate a second link direction (e.g., SFI-D, SFI-U) that is different from (e.g., opposite) the first link direction, or may indicate a flexible resource type (e.g., SFI-F, RRC-F). Therefore, a downlink opportunity (such as configuring or indicating a resource as having a downlink link direction or a flexible resource type) and a configured uplink opportunity, or a configured downlink opportunity and an uplink opportunity (such as configuring or indicating a resource as having an uplink link direction or a flexible resource type) may coexist on the same symbol (e.g., may be allowed on the same symbol). Therefore, it is helpful to implement a full-duplex configuration (e.g., SBFD, partially overlapping FD, completely overlapping FD, etc.) on a resource.

[0132] In some aspects, the resource type of the resource is indicated by the SFI and is an uplink resource type or a flexible resource type (e.g., SFI-U or SFI-F), and the resource configuration is a configured CSI-RS configuration. For example, a network node may be permitted to configure CSI-RS transmission on SFI-U or SFI-F resources.

[0133] In some aspects, the resource type of the resource is indicated by the SFI and is an uplink resource type or a flexible resource type (e.g., SFI-U or SFI-F), and the resource configuration is a configured SPS configuration. For example, the network node may be permitted to configure an SPS configuration on an SFI-U or SFI-F resource.

[0134] In some aspects, the resource type of the resource is indicated by the SFI and includes a downlink resource type or a flexible resource type (e.g., SFI-D or SFI-F), and the resource configuration is a configured CORESET configuration. For example, a network node may be permitted to configure a CORESET (or a search space associated with a CORESET) on an SFI-D or SFI-F resource.

[0135] In some aspects, the resource type of the resource is indicated by the SFI and includes a downlink resource type or a flexible resource type (e.g., SFI-D or SFI-F), and the resource configuration is a configured PUSCH configuration. For example, a network node may be permitted to configure a configured PUSCH transmission on an SFI-D or SFI-F resource (e.g., a configured grant).

[0136] In some aspects, the resource type of the resource is indicated by the SFI and includes a downlink resource type or a flexible resource type (e.g., SFI-D or SFI-F), and the resource configuration is a configured PUCCH configuration. For example, a network node may be permitted to configure PUCCH transmission on SFI-D or SFI-F resources (e.g., a configured grant).

[0137] In some aspects, the resource type of the resource is indicated by the SFI and includes a downlink resource type or a flexible resource type (e.g., SFI-D or SFI-F), and the resource configuration is a PRACH configuration. For example, a network node may be permitted to configure PRACH transmissions on SFI-D or SFI-F resources.

[0138] In some aspects, the resource type is indicated by an RRC configuration and comprises a flexible resource type (eg, RRC-F), and the resource configuration is a configured CSI-RS configuration. For example, a network node may be permitted to configure CSI-RS transmission on RRC-F resources.

[0139] In some aspects, the resource type is indicated by an RRC configuration and comprises a flexible resource type (eg, RRC-F), and the resource configuration is a configured SPS configuration. For example, the network node may be permitted to configure an SPS opportunity for an SPS configuration on an RRC-F resource.

[0140] In some aspects, the resource type is indicated by an RRC configuration and comprises a flexible resource type (eg, RRC-F), and the resource configuration is a configured PUSCH configuration. For example, a network node may be permitted to configure PUSCH transmissions on RRC-F resources (eg, a configured grant).

[0141] In some aspects, the resource type is indicated by an RRC configuration and comprises a flexible resource type (eg, RRC-F), and the resource configuration is a configured PUCCH configuration. For example, the network node may be permitted to configure PUCCH transmissions on RRC-F resources.

[0142] In some aspects, the resource type is indicated by an RRC configuration and comprises a flexible resource type (eg, RRC-F), and the resource configuration is a PRACH configuration. For example, a network node may be permitted to configure a PRACH transmission on RRC-F resources (eg, PRACH resources).

[0143] As shown by reference numeral 930, the UE and the network node may perform communications according to a prioritization rule. The prioritization rule may indicate whether a first link direction (indicated by a resource configuration) or a second link direction (such as, if the resource type is SFI-D or SFI-U, it may be indicated by the resource type of the resource) will be used for the resource. For example, the UE and the network node may determine whether to assume downlink communication or uplink communication on the resource according to the prioritization rule. In some aspects, the prioritization rule may indicate that if a second communication associated with a threshold priority on the resource is to be performed, the first communication associated with the second link direction on the resource is discarded. For example, the resource may be associated with a flexible resource type or an SFI-D or SFI-U slot format. If the resource is associated with an SFI-D or SFI-U slot format, the first communication may have a link direction indicated by the SFI-D or SFI-U slot format. If the resource is associated with an RRC-F slot format or an SFI-F slot format, the first communication may have a link direction opposite to the link direction of the second communication. In one example, the second communication is a scheduling request transmission. In another example, the second communication is a PRACH transmission for beam failure recovery. In some aspects, the threshold priority may be indicated by the second communication. In some aspects, the threshold priority may be based at least in part on a scenario associated with the second communication. For example, the scenario may include beam failure recovery, and based on the second communication being a communication for beam failure recovery (e.g., a scheduling request or a physical random access channel), the second communication may have the threshold priority.

[0144] In some aspects, the resource type is indicated by the SFI and is a downlink resource type or a flexible resource type (e.g., SFI-D or SFI-F), and performing communications with the UE according to a prioritization rule may include: based at least in part on the uplink transmission being associated with a threshold priority, the UE transmits and the network node obtains an uplink transmission on a first link direction (e.g., uplink). For example, the uplink communication may include a scheduling request transmission or a PRACH transmission associated with beam failure recovery. In this example, the UE may discard downlink reception in the resource. If there is no uplink transmission associated with the threshold priority, the network node may output and the UE may receive a downlink transmission on a second link direction (e.g., downlink) on the resource. The downlink transmission may be configured by a resource configuration of reference numeral 820. For example, if beam failure recovery is not performed, the UE may receive a dynamic grant communication, a communication on an SPS opportunity, or a CSI-RS.

[0145] In some aspects, the resource type is indicated by an RRC configuration and includes a flexible resource type (e.g., RRC-F), and performing communications with the UE according to a prioritization rule further includes: based at least in part on the uplink transmission being associated with a threshold priority, the UE transmits and the network node obtains an uplink transmission on a first link direction (e.g., uplink). For example, the uplink communication may include a scheduling request transmission or a PRACH transmission associated with beam failure recovery. In this example, the UE may discard downlink reception in the resource. If there is no uplink transmission associated with the threshold priority, the network node may output and the UE may receive a downlink transmission on a second link direction (e.g., downlink) on the resource. The downlink transmission may be configured by a resource configuration of reference numeral 820. For example, if beam failure recovery is not performed, the UE may receive a dynamic grant communication, a communication on an SPS opportunity, or a CSI-RS.

[0146] In some aspects, the resource type is indicated by an SFI and includes an uplink resource type or a flexible resource type (SFI-U or SFI-F), and performing communications according to a prioritization rule further includes: based at least in part on the downlink transmission being associated with a threshold priority, the network node outputs and the UE receives a downlink transmission on a first link direction (e.g., downlink). For example, the downlink transmission may include a downlink transmission associated with a high priority, such as time-sensitive downlink communications, etc. In this example, the UE may discard the uplink transmission in the resource. If there is no downlink transmission associated with the threshold priority, the UE may send and the network node may receive an uplink transmission on a second link direction (e.g., uplink) on the resource. The uplink transmission may be configured by a resource configuration of reference numeral 920.

[0147] In some aspects, the resource type is indicated by an RRC configuration and includes a flexible resource type (e.g., RRC-F), and performing communications according to a prioritization rule further includes: based at least in part on the downlink transmission being associated with a threshold priority, the network node outputs and the UE receives a downlink transmission on a first link direction (e.g., downlink). For example, the downlink transmission may include a downlink transmission associated with a high priority, such as time-sensitive downlink communications, etc. In this example, the UE may discard an uplink transmission in the resource. If there is no downlink transmission associated with the threshold priority, the UE may send and the network node may receive an uplink transmission on a second link direction (e.g., uplink) on the resource. The uplink transmission may be configured by a resource configuration of reference numeral 920.

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

[0149] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a network node in accordance with the present disclosure. Example process 1000 is an example of a network node (eg, network node 110) performing operations associated with full duplex qualification or prioritization.

[0150] like Fig.10 As shown, in some aspects, process 1000 may include identifying whether to permit a first downlink channel or reference signal to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal (block 1010). For example, a network node (e.g., using Fig.14 The communication manager 150 and / or identification component 1408 depicted in FIG. 1 may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal, as described above.

[0151] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include scheduling communications for a user equipment (UE) based at least in part on whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration (block 1020). For example, a network node (e.g., using Fig.14 The communication manager 150 and / or the sending component 1404 depicted in FIG. 1 may schedule communications for a user equipment (UE) based at least in part on whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration, as described above.

[0152] Process 1000 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.

[0153] In a first aspect, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also includes receiving signaling from the UE indicating whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0154] In a second aspect, alone or in combination with the first aspect, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on a preconfigured rule.

[0155] In a third aspect, alone or in combination with one or more of the first and second aspects, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration includes identifying whether the channel or signal of the first channel type or reference signal type is permitted to overlap in time with the channel or signal of the second channel type or reference signal type.

[0156] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on the first downlink channel or reference signal and the second uplink channel or reference signal being associated with a beam pair.

[0157] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also includes sending an indication of whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0158] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, in the full-duplex configuration, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the network node, at least in part based on the network node being a full-duplex network node.

[0159] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, in the full-duplex configuration, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the UE, at least in part based on the UE being a full-duplex UE.

[0160] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first channel type or reference signal type includes at least one of: a synchronization signal block (SSB) type, a physical downlink control channel (PDCCH) type, a physical downlink shared channel (PDSCH) type, a channel state information reference signal (CSI-RS) type, or a positioning reference signal (PRS) type.

[0161] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the PDSCH type further includes at least one of a dynamic grant PDSCH type or a semi-persistent scheduling PDSCH type.

[0162] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the CSI-RS type also includes at least one of the following: a periodic CSI-RS type, a non-periodic CSI-RS type, a semi-persistent CSI-RS type, a channel state feedback CSI-RS type, a beam management CSI-RS type, a tracking reference signal CSI-RS type, a radio resource management CSI-RS type, a beam failure detection CSI-RS type, a candidate beam detection CSI-RS type, a path loss reference signal CSI-RS type, a layer 1 measurement CSI-RS type, or a radio link monitoring CSI-RS type.

[0163] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the second channel type or reference signal type includes at least one of the following: a physical uplink control channel (PUCCH) type, a physical uplink shared channel (PUSCH) type, a physical random access channel (PRACH) type, a sounding reference signal (SRS) type, or an uplink positioning reference signal (PRS) type.

[0164] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the PUSCH type further comprises at least one of a dynamically granted PUSCH type or a configured granted PUSCH type.

[0165] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the PRACH type further comprises at least one of a dynamically scheduled PRACH type or a configured PRACH type.

[0166] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the SRS type also includes at least one of the following: a periodic SRS type, a non-periodic SRS type, a semi-persistent SRS type, a beam-managed SRS type, an antenna switching SRS type, a codebook-based uplink transmission SRS type, or a non-codebook-based uplink transmission SRS type.

[0167] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, identifying whether to permit the first downlink channel or reference signal to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on usage of the first downlink channel or reference signal or on usage of the second uplink channel or reference signal.

[0168] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the usage of the first downlink channel or reference signal or the usage of the second uplink channel or reference signal: sub-band full-duplex usage; full-duplex usage with partial overlap or full overlap based on spatial division multiplexing; intra-operator usage; inter-operator usage; legacy UE usage; full-duplex aware UE usage; usage of a specific frequency range, frequency band or frequency band combination; full-duplex UE usage or full-duplex network node usage.

[0169] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the full-duplex configuration comprises at least one of: a sub-band full-duplex configuration, a partially overlapping full-duplex configuration, or a fully overlapping full-duplex configuration.

[0170] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 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 1000 may be performed in parallel.

[0171] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a network node, in accordance with the present disclosure. The example process 1100 is an example of a network node (eg, network node 110) performing operations associated with full duplex qualification or prioritization.

[0172] like Fig.11 As shown in FIG. 1 , in some aspects, process 1100 may include outputting an indication of a resource type for a resource (block 1110). For example, a network node (e.g., using Fig.14 The depicted communications manager 150 and / or sending component 1404) can output an indication of a resource type for a resource, as described above.

[0173] like Fig.11As further shown in FIG. 1 , in some aspects, process 1100 may include outputting a resource configuration for uplink or downlink communication on a resource, wherein the resource configuration has a first link direction and a resource type of the resource indicates one of: a resource type for a second link direction different from the first link direction or a flexible resource type (block 1120). For example, a network node (e.g., using Fig.14 The communication manager 150 and / or configuration component 1408 depicted in the figure may output a resource configuration for uplink or downlink communication on a resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates one of: a resource type for a second link direction different from the first link direction or a flexible resource type, as described above.

[0174] like Fig.11 As further shown in FIG. 1 , in some aspects, process 1100 may include performing communications with the UE according to a prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource (block 1130). For example, a network node (e.g., using Fig.14 The communication manager 150 and / or the sending component 1404 depicted in FIG. 1 may perform communications with a user equipment (UE) according to a prioritization rule indicating whether a first link direction or a second link direction is to be used for the resource, as described above.

[0175] Process 1100 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.

[0176] In a first aspect, the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0177] In a second aspect, alone or in combination with the first aspect, the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0178] In a third aspect, alone or in combination with one or more of the first and second aspects, the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured control resource set configuration.

[0179] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0180] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0181] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0182] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0183] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0184] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0185] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0186] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0187] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes obtaining an uplink transmission in the first link direction based at least in part on the uplink transmission being associated with a threshold priority.

[0188] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes outputting a downlink transmission on the resource in the second link direction.

[0189] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes obtaining an uplink transmission in the first link direction based at least in part on associating the uplink transmission with a threshold priority.

[0190] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes outputting a downlink transmission on the resource in the second link direction.

[0191] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the resource type is indicated by a time slot format indicator and includes an uplink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes outputting the downlink transmission in the first link direction at least in part based on associating the downlink transmission with a threshold priority.

[0192] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes obtaining an uplink transmission on the resource in the second link direction.

[0193] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes outputting the downlink transmission in the first link direction at least in part based on associating the downlink transmission with a threshold priority.

[0194] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes obtaining an uplink transmission on the resource in the second link direction.

[0195] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 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 1100 may be performed in parallel.

[0196] Fig.12 is a diagram illustrating an example process 1200 performed, for example, by a user equipment (UE) according to the present disclosure. Example process 1200 is an example of a UE (eg, UE 120) performing operations associated with full dual-work qualification or prioritization.

[0197] like Fig.12 As shown, in some aspects, process 1200 may include identifying whether to permit a first downlink channel or reference signal to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal (block 1210). For example, a UE (e.g., using Fig.15 The communication manager 140 and / or identification component 1508 depicted in FIG. 1 may identify whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal, as described above.

[0198] like Fig.12As further shown in FIG. 1 , in some aspects, process 1200 may include performing communication with a network node based at least in part on whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration (block 1220). For example, a UE (e.g., using Fig.15 The communication manager 140 and / or receiving component 1502 depicted in FIG. 1 may perform communications with a network node based at least in part on whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration, as described above.

[0199] Process 1200 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.

[0200] In a first aspect, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also sends signaling indicating whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0201] In a second aspect, alone or in combination with the first aspect, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on a preconfigured rule.

[0202] In a third aspect, alone or in combination with one or more of the first and second aspects, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration includes identifying whether the channel or signal of the first channel type or reference signal type is permitted to overlap in time with the channel or signal of the second channel type or reference signal type.

[0203] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on the first downlink channel or reference signal and the second uplink channel or reference signal being associated with a beam pair.

[0204] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also includes receiving an indication of whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0205] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, in the full-duplex configuration, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the network node, at least in part based on the network node being a full-duplex network node.

[0206] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, in the full-duplex configuration, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the UE, at least in part based on the UE being a full-duplex UE.

[0207] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first channel type or reference signal type includes at least one of: a synchronization signal block (SSB) type, a physical downlink control channel (PDCCH) type, a physical downlink shared channel (PDSCH) type, a channel state information reference signal (CSI-RS) type, or a positioning reference signal (PRS) type.

[0208] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the PDSCH type further includes at least one of a dynamic grant PDSCH type or a semi-persistent scheduling PDSCH type.

[0209] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the CSI-RS type also includes at least one of the following: a periodic CSI-RS type, a non-periodic CSI-RS type, a semi-persistent CSI-RS type, a channel state feedback CSI-RS type, a beam management CSI-RS type, a tracking reference signal CSI-RS type, a radio resource management CSI-RS type, a beam failure detection CSI-RS type, a candidate beam detection CSI-RS type, a path loss reference signal CSI-RS type, a layer 1 measurement CSI-RS type, or a radio link monitoring CSI-RS type.

[0210] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the second channel type or reference signal type includes at least one of the following: a physical uplink control channel (PUCCH) type, a physical uplink shared channel (PUSCH) type, a physical random access channel (PRACH) type, a sounding reference signal (SRS) type, or an uplink positioning reference signal (PRS) type.

[0211] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the PUSCH type further comprises at least one of a dynamically granted PUSCH type or a configured granted PUSCH type.

[0212] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the PRACH type further comprises at least one of a dynamically scheduled PRACH type or a configured PRACH type.

[0213] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the SRS type also includes at least one of the following: a periodic SRS type, a non-periodic SRS type, a semi-persistent SRS type, a beam-managed SRS type, an antenna switching SRS type, a codebook-based uplink transmission SRS type, or a non-codebook-based uplink transmission SRS type.

[0214] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, identifying whether to permit the first downlink channel or reference signal to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on usage of the first downlink channel or reference signal or on usage of the second uplink channel or reference signal.

[0215] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the usage of the first downlink channel or reference signal or the usage of the second uplink channel or reference signal: sub-band full-duplex usage; full-duplex usage with partial overlap or full overlap based on spatial division multiplexing; intra-operator usage; inter-operator usage; legacy UE usage; full-duplex aware UE usage; usage of a specific frequency range, frequency band or frequency band combination; full-duplex UE usage or full-duplex network node usage.

[0216] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the full-duplex configuration comprises at least one of: a sub-band full-duplex configuration, a partially overlapping full-duplex configuration, or a fully overlapping full-duplex configuration.

[0217] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 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 1200 may be performed in parallel.

[0218] Fig.13 1 is a diagram illustrating an example process 1300 performed, for example, by a UE according to the present disclosure. Example process 1300 is an example of a UE (eg, UE 120) performing operations associated with full dual-work qualification or prioritization.

[0219] like Fig.13 As shown in FIG. 1 , in some aspects, process 1300 may include receiving an indication of a resource type for a resource (block 1310). For example, a UE (e.g., using Fig.15 The communications manager 140 and / or receiving component 1502 depicted in FIG. 140 may receive an indication of a resource type for a resource, as described above.

[0220] like Fig.13 As further shown in FIG. 1 , in some aspects, process 1300 may include receiving a resource configuration for uplink or downlink communication on a resource, wherein the resource configuration has a first link direction and a resource type of the resource indicates one of: a resource type for a second link direction different from the first link direction or a flexible resource type (block 1320). For example, a UE (e.g., using Fig.15 The communication manager 140 and / or receiving component 1502 depicted in the figure can receive a resource configuration for uplink or downlink communication on a resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates one of the following: a resource type for a second link direction different from the first link direction or a flexible resource type, as described above.

[0221] like Fig.13 As further shown in FIG. 1 , in some aspects, process 1300 may include performing communications with a network node according to a prioritization rule indicating whether a first link direction or a second link direction is to be used for a resource (block 1330). Fig.15 The communication manager 140 and / or the sending component 1504 depicted in FIG. 1 may perform communications with the network node according to a prioritization rule indicating whether a first link direction or a second link direction is to be used for the resource, as described above.

[0222] Process 1300 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.

[0223] In a first aspect, the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0224] In a second aspect, alone or in combination with the first aspect, the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0225] In a third aspect, alone or in combination with one or more of the first and second aspects, the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured control resource set configuration.

[0226] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0227] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the resource type is indicated by a slot format indicator and includes an uplink resource type or the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0228] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the resource type is indicated by a slot format indicator and includes an uplink resource type or the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0229] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0230] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0231] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0232] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0233] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0234] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes sending an uplink transmission in the first link direction at least in part based on the uplink transmission being associated with a threshold priority, and discarding a downlink reception in the second link direction.

[0235] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes receiving a downlink transmission on the resource in the second link direction.

[0236] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication according to the prioritization rule further includes sending an uplink transmission in the first link direction based at least in part on associating the uplink transmission with a threshold priority, and discarding a downlink reception in the second link direction.

[0237] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication according to the prioritization rule also includes receiving a downlink transmission on the resource in the second link direction.

[0238] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the resource type is indicated by a time slot format indicator and includes an uplink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes receiving a downlink transmission in the first link direction at least in part based on the downlink transmission being associated with a threshold priority, and discarding the uplink transmission in the second link direction.

[0239] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes sending an uplink transmission on the resource in the second link direction.

[0240] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes receiving downlink transmissions in the first link direction at least in part based on the downlink transmissions being associated with a threshold priority, and discarding uplink transmissions in the second link direction.

[0241] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes sending an uplink transmission on the resource in the second link direction.

[0242] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 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 1300 may be performed in parallel.

[0243] Fig.141 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a network node, or a network node may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a sending component 1404, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and sending component 1404. As further shown, apparatus 1400 may include a communication manager 150. Communication manager 150 may include identification component 1408 and one or more of the other examples.

[0244] In some aspects, the apparatus 1400 may be configured to perform the Figures 4 to 9 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.10 The process of 1000 Fig.11 In some aspects, Fig.14 The device 1400 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.14 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.

[0245] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 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.

[0246] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 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 1404 can be co-located with the receive component 1402 in a transceiver.

[0247] The identifying component 1408 can identify whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal or a second channel type or reference signal type of the second uplink channel or reference signal. The transmitting component 1404 can schedule communication of a user equipment (UE) based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in a full-duplex configuration.

[0248] The transmitting component 1404 can output an indication of a resource type of the resource. The transmitting component 14040 can output a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates one of a resource type for a second link direction different from the first link direction or a flexible resource type. The receiving component 1402 can perform communication with the UE according to a prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

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

[0250] Fig.15 1 is a diagram of an example apparatus 1500 for wireless communication according to the present disclosure. Apparatus 1500 may be a UE, or a UE may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a sending component 1504, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and sending component 1504. As further shown, apparatus 1500 may include a communication manager 140. Communication manager 140 may include identification component 1508 and one or more of the other examples.

[0251] In some aspects, the apparatus 1500 may be configured to perform the Figures 4 to 9 Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.12 The process 1200 Fig.13 In some aspects, Fig.15 The device 1500 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.15 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.

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

[0253] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 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 1504 can be co-located with the receive component 1502 in a transceiver.

[0254] The identifying component 1508 can identify whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in a full-duplex configuration based at least in part on a first channel type or reference signal type of the first downlink channel or reference signal or a second channel type or reference signal type of the second uplink channel or reference signal. The transmitting component 1504 can perform communication with the network node based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in a full-duplex configuration.

[0255] Receiving component 1502 can receive an indication of a resource type of a resource. Receiving component 1502 can receive a resource configuration for uplink or downlink communication on a resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates one of a resource type for a second link direction different from the first link direction or a flexible resource type. Sending component 1504 can perform communication with the network node according to a prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

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

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

[0258] Aspect 1: A method of wireless communication performed by a network node, the method comprising: identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; and scheduling communication of a user equipment (UE) based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0259] Aspect 2: A method according to Aspect 1, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also includes receiving signaling from the UE indicating whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0260] Aspect 3: The method according to any one of aspects 1 to 2, wherein identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on a preconfigured rule.

[0261] Aspect 4: A method according to any one of Aspects 1 to 3, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration includes identifying whether a channel or signal of the first channel type or reference signal type is allowed to overlap in time with a channel or signal of the second channel type or reference signal type.

[0262] Aspect 5: A method according to any one of Aspects 1 to 4, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is at least partially based on the first downlink channel or reference signal and the second uplink channel or reference signal being associated with a beam pair.

[0263] Aspect 6: A method according to any one of Aspects 1 to 5, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also includes sending an indication of whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0264] Aspect 7: A method according to any one of Aspects 1 to 6, wherein in the full-duplex configuration, at least in part based on the network node being a full-duplex network node, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the network node.

[0265] Aspect 8: A method according to any one of Aspects 1 to 7, wherein in the full-duplex configuration, at least in part based on the UE being a full-duplex UE, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the UE.

[0266] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the first channel type or reference signal type includes at least one of the following: a synchronization signal block (SSB) type, a physical downlink control channel (PDCCH) type, a physical downlink shared channel (PDSCH) type, a channel state information reference signal (CSI-RS) type, or a positioning reference signal (PRS) type.

[0267] Aspect 10: The method according to aspect 9, wherein the PDSCH type further comprises at least one of a dynamic grant PDSCH type or a semi-persistent scheduling PDSCH type.

[0268] Aspect 11: A method according to Aspect 9, wherein the CSI-RS type also includes at least one of the following: a periodic CSI-RS type, an aperiodic CSI-RS type, a semi-persistent CSI-RS type, a channel state feedback CSI-RS type, a beam management CSI-RS type, a tracking reference signal CSI-RS type, a radio resource management CSI-RS type, a beam failure detection CSI-RS type, a candidate beam detection CSI-RS type, a path loss reference signal CSI-RS type, a layer 1 measurement CSI-RS type, or a radio link monitoring CSI-RS type.

[0269] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the second channel type or reference signal type includes at least one of the following: a physical uplink control channel (PUCCH) type, a physical uplink shared channel (PUSCH) type, a physical random access channel (PRACH) type, a sounding reference signal (SRS) type, or an uplink positioning reference signal (PRS) type.

[0270] Aspect 13: The method according to aspect 12, wherein the PUSCH type further comprises at least one of a dynamically granted PUSCH type or a configured granted PUSCH type.

[0271] Aspect 14: The method according to aspect 12, wherein the PRACH type further comprises at least one of a dynamically scheduled PRACH type or a configured PRACH type.

[0272] Aspect 15: A method according to Aspect 12, wherein the SRS type also includes at least one of the following: a periodic SRS type, a non-periodic SRS type, a semi-persistent SRS type, a beam management SRS type, an antenna switching SRS type, a codebook-based uplink transmission SRS type, or a non-codebook-based uplink transmission SRS type.

[0273] Aspect 16: A method according to any one of Aspects 1 to 15, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is at least partially based on the usage of the first downlink channel or reference signal or based on the usage of the second uplink channel or reference signal.

[0274] Aspect 17: A method according to Aspect 16, wherein the usage of the first downlink channel or reference signal or the usage of the second uplink channel or reference signal is: sub-band full-duplex usage; full-duplex usage with partial overlap or full overlap based on spatial division multiplexing; intra-operator usage; inter-operator usage; legacy UE usage; full-duplex aware UE usage; usage of a specific frequency range, frequency band or frequency band combination; full-duplex UE usage or full-duplex network node usage.

[0275] Aspect 18: The method according to any one of aspects 1 to 17, wherein the full-duplex configuration comprises at least one of: a sub-band full-duplex configuration, a partially overlapping full-duplex configuration, or a fully overlapping full-duplex configuration.

[0276] Aspect 19: A method for wireless communication performed by a network node, the method comprising: outputting an indication of a resource type of a resource; outputting a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of the following: a resource type for a second link direction different from the first link direction or a flexible resource type; and performing communication with a user equipment (UE) according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction will be used for the resource.

[0277] Aspect 20: The method according to aspect 19, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0278] Aspect 21: The method according to any one of Aspects 19, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0279] Aspect 22: The method according to aspect 19, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured control resource set configuration.

[0280] Aspect 23: The method according to aspect 19, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0281] Aspect 24: The method according to aspect 19, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0282] Aspect 25: The method according to aspect 19, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0283] Aspect 26: The method according to aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0284] Aspect 27: The method according to aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0285] Aspect 28: The method according to aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0286] Aspect 29: The method according to aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0287] Aspect 30: The method according to aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0288] Aspect 31: A method according to Aspect 19, wherein the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: obtaining an uplink transmission in the first link direction at least in part based on the uplink transmission being associated with a threshold priority.

[0289] Aspect 32: A method according to Aspect 19, wherein the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: outputting a downlink transmission in the second link direction on the resource.

[0290] Aspect 33: A method according to Aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and wherein performing the communication with the UE according to the prioritization rule also includes: obtaining an uplink transmission in the first link direction at least in part based on associating the uplink transmission with a threshold priority.

[0291] Aspect 34: A method according to Aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: outputting a downlink transmission in the second link direction on the resource.

[0292] Aspect 35: A method according to Aspect 19, wherein the resource type is indicated by a time slot format indicator and includes an uplink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: outputting the downlink transmission in the first link direction at least in part based on the downlink transmission being associated with a threshold priority.

[0293] Aspect 36: A method according to Aspect 19, wherein the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: obtaining an uplink transmission on the resource in the second link direction.

[0294] Aspect 37: A method according to Aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and wherein performing the communication with the UE according to the prioritization rule also includes: outputting the downlink transmission in the first link direction at least in part based on the downlink transmission being associated with a threshold priority.

[0295] Aspect 38: A method according to Aspect 19, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: obtaining an uplink transmission in the second link direction on the resource.

[0296] Aspect 39: A method for wireless communication performed by a user equipment (UE), the method comprising: identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; and performing communication with a network node based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0297] Aspect 40: A method according to Aspect 39, wherein an identifier indicating whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also sends a signal indicating whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0298] Aspect 41: A method according to any one of aspects 39 to 40, wherein identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on a pre-configured rule.

[0299] Aspect 42: A method according to any one of Aspects 39 to 41, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration includes identifying whether a channel or signal of the first channel type or reference signal type is allowed to overlap in time with a channel or signal of the second channel type or reference signal type.

[0300] Aspect 43: A method according to any one of Aspects 39 to 42, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is at least partially based on the first downlink channel or reference signal and the second uplink channel or reference signal being associated with a beam pair.

[0301] Aspect 44: A method according to any one of Aspects 39 or 41 to 43, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also includes receiving an indication of whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

[0302] Aspect 45: A method according to any one of Aspects 39 to 44, wherein in the full-duplex configuration, at least in part based on the fact that the network node is a full-duplex network node, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the network node.

[0303] Aspect 46: A method according to any one of Aspects 39 to 45, wherein in the full-duplex configuration, at least in part based on the UE being a full-duplex UE, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the UE.

[0304] Aspect 47: A method according to any one of Aspects 39 to 46, wherein the first channel type or reference signal type includes at least one of the following: a synchronization signal block (SSB) type, a physical downlink control channel (PDCCH) type, a physical downlink shared channel (PDSCH) type, a channel state information reference signal (CSI-RS) type, or a positioning reference signal (PRS) type.

[0305] Aspect 48: The method according to aspect 47, wherein the PDSCH type further comprises at least one of a dynamic grant PDSCH type or a semi-persistent scheduling PDSCH type.

[0306] Aspect 49: A method according to Aspect 47, wherein the CSI-RS type also includes at least one of the following: a periodic CSI-RS type, an aperiodic CSI-RS type, a semi-persistent CSI-RS type, a channel state feedback CSI-RS type, a beam management CSI-RS type, a tracking reference signal CSI-RS type, a radio resource management CSI-RS type, a beam failure detection CSI-RS type, a candidate beam detection CSI-RS type, a path loss reference signal CSI-RS type, a layer 1 measurement CSI-RS type, or a radio link monitoring CSI-RS type.

[0307] Aspect 50: A method according to any one of Aspects 39 to 46, wherein the second channel type or reference signal type includes at least one of the following: a physical uplink control channel (PUCCH) type, a physical uplink shared channel (PUSCH) type, a physical random access channel (PRACH) type, a sounding reference signal (SRS) type, or an uplink positioning reference signal (PRS) type.

[0308] Aspect 51: The method according to aspect 50, wherein the PUSCH type further comprises at least one of a dynamically granted PUSCH type or a configured granted PUSCH type.

[0309] Aspect 52: The method according to aspect 50, wherein the PRACH type further comprises at least one of a dynamically scheduled PRACH type or a configured PRACH type.

[0310] Aspect 53: A method according to Aspect 50, wherein the SRS type also includes at least one of the following: a periodic SRS type, a non-periodic SRS type, a semi-persistent SRS type, a beam-managed SRS type, an antenna switching SRS type, a codebook-based uplink transmission SRS type, or a non-codebook-based uplink transmission SRS type.

[0311] Aspect 54: A method according to any one of Aspects 39 to 53, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is at least partially based on the usage of the first downlink channel or reference signal or based on the usage of the second uplink channel or reference signal.

[0312] Aspect 55: A method according to Aspect 54, wherein the usage of the first downlink channel or reference signal or the usage of the second uplink channel or reference signal is: sub-band full-duplex usage; full-duplex usage with partial overlap or full overlap based on spatial division multiplexing; intra-operator usage; inter-operator usage; legacy UE usage, full-duplex aware UE usage; usage of a specific frequency range, frequency band or frequency band combination; full-duplex UE usage or full-duplex network node usage.

[0313] Aspect 56: The method according to any one of aspects 39 to 55, wherein the full-duplex configuration comprises at least one of: a sub-band full-duplex configuration, a partially overlapping full-duplex configuration, or a fully overlapping full-duplex configuration.

[0314] Aspect 57: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving an indication of a resource type of a resource; receiving a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction, and the resource type of the resource indicates one of the following: a resource type for a second link direction different from the first link direction or a flexible resource type; and performing communication with a network node according to a prioritization rule, the prioritization rule indicating whether the first link direction or the second link direction will be used for the resource.

[0315] Aspect 58: The method according to aspect 57, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0316] Aspect 59: The method according to aspect 57, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0317] Aspect 60: The method according to aspect 57, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured control resource set configuration.

[0318] Aspect 61: The method according to aspect 57, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0319] Aspect 62: The method according to aspect 57, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0320] Aspect 63: The method according to aspect 57, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0321] Aspect 64: The method according to aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

[0322] Aspect 65: The method according to aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

[0323] Aspect 66: The method according to aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

[0324] Aspect 67: The method according to aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

[0325] Aspect 68: The method according to aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a physical random access channel configuration.

[0326] Aspect 69: A method according to Aspect 57, wherein the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes: sending an uplink transmission in the first link direction at least in part based on the uplink transmission being associated with a threshold priority; and discarding downlink reception in the second link direction.

[0327] Aspect 70: A method according to Aspect 57, wherein the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes: receiving a downlink transmission in the second link direction on the resource.

[0328] Aspect 71: A method according to Aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication according to the prioritization rule also includes: sending an uplink transmission in the first link direction based at least in part on associating the uplink transmission with a threshold priority; and discarding a downlink reception in the second link direction.

[0329] Aspect 72: A method according to Aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication according to the prioritization rule also includes: receiving a downlink transmission in the second link direction on the resource.

[0330] Aspect 73: A method according to Aspect 57, wherein the resource type is indicated by a time slot format indicator and includes an uplink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes: receiving a downlink transmission in the first link direction at least in part based on the downlink transmission being associated with a threshold priority; and discarding an uplink transmission in the second link direction.

[0331] Aspect 74: A method according to Aspect 57, wherein the resource type is indicated by a time slot format indicator and includes a downlink resource type or the flexible resource type, wherein performing the communication according to the prioritization rule also includes: sending an uplink transmission on the resource in the second link direction.

[0332] Aspect 75: A method according to Aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: receiving a downlink transmission in the first link direction based at least in part on the downlink transmission being associated with a threshold priority; and discarding an uplink transmission in the second link direction.

[0333] Aspect 76: A method according to Aspect 57, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, wherein performing the communication with the UE according to the prioritization rule also includes: sending an uplink transmission on the resource in the second link direction.

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

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

[0336] Aspect 79: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 1 to 76.

[0337] Aspect 80: 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 76.

[0338] Aspect 81: 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 76.

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

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

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

[0342] 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 (it 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).

[0343] 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 one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless explicitly stated otherwise. 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 network node for wireless communication, the network node comprising: Memory; as well as one or more processors coupled to the memory and configured to: identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; as well as Communications of a user equipment (UE) are scheduled based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

2. The network node according to claim 1, wherein, in order to identify whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration, the one or more processors are configured to receive signaling from the UE indicating whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

3. The network node of claim 1, wherein identifying whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is based at least in part on a preconfigured rule.

4. A network node according to claim 1, wherein in order to identify whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration, the one or more processors are configured to identify whether the channel or signal of the first channel type or reference signal type is allowed to overlap in time with the channel or signal of the second channel type or reference signal type.

5. A network node according to claim 1, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is at least partially based on the first downlink channel or reference signal and the second uplink channel or reference signal being associated with a beam pair.

6. A network node according to claim 1, wherein in order to identify whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration, the one or more processors are configured to send an indication of whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

7. The network node of claim 1, wherein in the full-duplex configuration, based at least in part on the network node being a full-duplex network node, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the network node.

8. The network node of claim 1, wherein in the full-duplex configuration, based at least in part on the UE being a full-duplex UE, the first downlink channel or reference signal overlaps with the second uplink channel or reference signal at the UE.

9. The network node of claim 1, wherein the first channel type or reference signal type comprises at least one of: Synchronization Signal Block (SSB) type, Physical Downlink Control Channel (PDCCH) type, Physical Downlink Shared Channel (PDSCH) type, Channel State Information Reference Signal (CSI-RS) type, or Positioning Reference Signal (PRS) type.

10. The network node of claim 1, wherein the second channel type or reference signal type comprises at least one of: Physical Uplink Control Channel (PUCCH) type, Physical uplink shared channel (PUSCH) type, Physical Random Access Channel (PRACH) type, Sounding Reference Signal (SRS) type, or Uplink Positioning Reference Signal (PRS) type.

11. A network node according to claim 1, wherein identifying whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration is at least partially based on usage of the first downlink channel or reference signal or based on usage of the second uplink channel or reference signal.

12. The network node of claim 1, wherein the full-duplex configuration comprises at least one of: Sub-band full-duplex configuration, A full-duplex configuration with partial overlap, or Fully overlapped full-duplex configuration.

13. A network node for wireless communication, the network node comprising: Memory; as well as one or more processors coupled to the memory and configured to: outputting an indication of a resource type of a resource; outputting a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates one of a resource type for a second link direction different from the first link direction or a flexible resource type; as well as Communications with a user equipment (UE) are performed according to a prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

14. The network node according to claim 13, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

15. The network node of claim 13, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

16. The network node of claim 13, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured control resource set configuration.

17. The network node of claim 13, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

18. The network node of claim 13, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

19. The network node of claim 13, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, and the resource configuration is a physical random access channel configuration.

20. The network node of claim 13, wherein the resource type is indicated by a radio resource control configuration and comprises the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

21. The network node of claim 13, wherein the resource type is indicated by a radio resource control configuration and includes the flexible resource type, and the resource configuration is a configured semi-persistent scheduling configuration.

22. The network node of claim 13, wherein the resource type is indicated by a radio resource control configuration and comprises the flexible resource type, and the resource configuration is a configured physical uplink shared channel configuration.

23. The network node of claim 13, wherein the resource type is indicated by a radio resource control configuration and comprises the flexible resource type, and the resource configuration is a configured physical uplink control channel configuration.

24. The network node of claim 13, wherein the resource type is indicated by a radio resource control configuration and comprises the flexible resource type, and the resource configuration is a physical random access channel configuration.

25. The network node of claim 13, wherein the resource type is indicated by a slot format indicator and comprises a downlink resource type or the flexible resource type, wherein performing the communication with the UE according to the prioritization rule further comprises: An uplink transmission in the first link direction is obtained based at least in part on associating the uplink transmission with a threshold priority.

26. The network node of claim 13, wherein the resource type is indicated by a radio resource control configuration and comprises the flexible resource type, wherein performing the communication with the UE according to the prioritization rule further comprises: An uplink transmission in the first link direction is obtained based at least in part on associating the uplink transmission with a threshold priority.

27. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; as well as one or more processors coupled to the memory and configured to: identifying whether a first downlink channel or reference signal is permitted to overlap in time with a second uplink channel or reference signal in a full-duplex configuration based at least in part on: a first channel type or reference signal type of the first downlink channel or reference signal, or a second channel type or reference signal type of the second uplink channel or reference signal; as well as Communicating with a network node is performed based at least in part on whether the first downlink channel or reference signal is permitted to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

28. A UE according to claim 27, wherein an identifier indicating whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration also sends a signal indicating whether the first downlink channel or reference signal is allowed to overlap in time with the second uplink channel or reference signal in the full-duplex configuration.

29. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; as well as one or more processors coupled to the memory and configured to: receiving an indication of a resource type of a resource; receiving a resource configuration for uplink or downlink communication on the resource, wherein the resource configuration has a first link direction and the resource type of the resource indicates one of a resource type for a second link direction different from the first link direction or a flexible resource type; as well as The communication with the network node is performed according to a prioritization rule indicating whether the first link direction or the second link direction is to be used for the resource.

30. The UE of claim 29, wherein the resource type is indicated by a slot format indicator and comprises an uplink resource type or the flexible resource type, and the resource configuration is a configured channel state information reference signal configuration.

Images