Disallowed communication directions for full duplex time intervals

Abstract

Aspects of the present disclosure generally relate to wireless communications. Some aspects relate to disallowed communication directions for full duplex time intervals. Some aspects are more particularly directed to defining, for a user equipment (UE), allowed and / or disallowed communication directions for full duplex time intervals (e.g., for slots and / or symbols associated with full duplex operations). In some aspects, a network node transmits to a UE an indication of a communication direction that is disabled or to be discarded (e.g., not received or transmitted) during a time slot or symbol associated with full duplex operation at the network node. The UE may transmit or receive communications in a permitted communication direction (e.g., which is not in a dispermitted communication direction) during a full duplex time interval.

Description

[0001] Cross-references to related applications

[0002] This patent application claims the benefit of U.S. Patent Application No. 18 / 191,696, filed March 28, 2023, entitled "DISALLOWED COMMUNICATION DIRECTION FOR FULL-DUPLEX TIME INTERVALS," which has been assigned to the assignee of this application. The disclosure of that earlier application is considered part of this patent application and is incorporated herein by reference.

[0003] open field

[0004] The aspects of this disclosure generally relate to wireless communication, and more specifically to techniques and apparatus associated with communication directions that are not permitted for full-duplex time intervals. Background Technology

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). 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 an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0006] The multiple access technologies mentioned above have been adopted in various telecommunications standards to provide a common protocol enabling different UEs to communicate at the city, country, region, or global level. New Radio (NR) (which may be referred to as 5G) is an enhancement set to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink, and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to grow.

[0007] In some examples, network nodes can operate using different operating states. In these different operating states, the network node can use different antennas, different antenna panels, different antenna configurations, and / or different transmit / receive points (TRPs) to communicate with one or more user equipment (UEs). For example, a network node can operate in full-duplex mode (e.g., it can transmit and receive communications simultaneously). To improve spatial isolation between antennas and / or TRPs used for the respective communication directions, when operating in full-duplex mode, the network node can use a first antenna and / or a first TRP for downlink signals and a second antenna and / or a second TRP for uplink signals. For example, increasing the spatial isolation between the first antenna and / or the first TRP and the second antenna and / or the second TRP can reduce self-interference associated with full-duplex operation. Thus, when the network node operates in full-duplex mode, the first antenna and / or the first TRP may not be available for uplink signals, and the second antenna and / or the second TRP may not be available for downlink signals.

[0008] In some situations, when a network node is operating in full-duplex mode, the UE may experience poor performance in a given communication direction due to the unavailability of a given TRP for uplink or downlink communication. For example, when a network node is operating in full-duplex mode, the serving TRP for the UE (e.g., for downlink and uplink) may be used by the network node for a given communication direction. The UE may not support multiple active Transmission Configuration Indicator (TCI) states or beams. If an active TCI state or beam associated with the UE (e.g., for uplink communication) is associated with a specific direction toward a TRP, the UE may be unable to transmit or receive communication in the given communication direction during the full-duplex time interval (e.g., because the TRP is unavailable for the given communication direction, and the UE cannot support additional active beams or TCI states associated with another TRP). Additionally or alternatively, the link between the UE and another TRP (e.g., used by the network node for the given communication direction) may be associated with poor radio conditions (e.g., large path loss), resulting in poor communication performance between the UE and the other TRP in the given communication direction.

[0009] In some examples, the UE may rely on network nodes to suppress the scheduling of communication in a given communication direction during a full-duplex time interval. However, relying on network nodes to perform scheduling determination may be infeasible or unreliable in some cases. For example, some communications may be periodic and / or semi-persistent (e.g., occurring every X timeslots, symbols, or milliseconds). The periodicity of these communications may be inconsistent with the periodicity of the timeslot format, resulting in some of the periodic and / or semi-persistent communications being scheduled to occur during the full-duplex time interval. As another example, communications may be associated with one or more repetitions. Although communications may be scheduled during non-full-duplex time intervals, repetitions of communications may occur during the full-duplex time interval. As another example, a single downlink control information (DCI) communication may schedule multiple communications (e.g., different transport blocks may be scheduled). Although one or more of the multiple communications may be scheduled during non-full-duplex time intervals, one or more other communications may occur during the full-duplex time interval.

[0010] The UE may not be aware of a given communication direction (e.g., this communication direction may be associated with poor performance for the UE during the full-duplex time interval). Therefore, the UE may consume resources (e.g., power resources, processing resources, and / or network resources) to attempt to transmit or receive communication to or from antennas and / or TRPs of network nodes that are not available during the full-duplex time interval for a given communication direction (e.g., which are associated with a given communication direction).

[0011] Overview

[0012] Some aspects described herein relate to user equipment (UE) for wireless communication. The UE may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor is operable to cause the UE to receive from a network node an indication of one or more full-duplex time intervals. The at least one processor is operable to cause the UE to receive from the network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals. The at least one processor is operable to cause the UE, during one of the one or more full-duplex time intervals, to transmit or receive communication from the network node in a communication direction that is not a disallowed communication direction. As a result, how the UE utilizes the full-duplex time intervals when the network node is operating in full-duplex mode is illustrated. For example, during a full-duplex time interval, the UE may transmit or receive communication in a permitted communication direction and / or may discard communication in a disallowed communication direction. This can save UE resources (e.g., power resources, processing resources, and / or network resources) that would otherwise be used to attempt to transmit or receive communication in prohibited communication directions (e.g., to or from antennas and / or TRPs of network nodes that are not available for prohibited communication directions during the full-duplex time interval). The efficiency of the UE and the wireless communication system can thus be improved.

[0013] Some aspects described herein relate to a network node for wireless communication. The network node may include at least one memory and at least one processor communicatively coupled to the at least one memory. The at least one processor is operable to cause the network node to transmit an indication associated with a UE for one or more full-duplex time intervals. The at least one processor is operable to cause the network node to transmit an indication associated with a UE for a disallowed communication direction associated with one or more full-duplex time intervals. The at least one processor is operable to cause the network node to transmit or receive communication during one of the one or more full-duplex time intervals, depending on whether the communication to the UE is in a communication direction that is not a disallowed communication direction.

[0014] Some aspects described herein relate to a wireless communication method performed by a UE. The method may include receiving an indication from a network node for one or more full-duplex time intervals. The method may include receiving from the network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals. The method may include, during one of the one or more full-duplex time intervals, transmitting or receiving communication to or from the network node based on whether the communication is in a communication direction that is not a disallowed communication direction.

[0015] Some aspects described herein relate to a wireless communication method performed by a network node. The method may include transmitting an indication associated with a UE for one or more full-duplex time intervals. The method may include transmitting an indication associated with a UE for a disallowed communication direction associated with one or more full-duplex time intervals. The method may include, during one of the one or more full-duplex time intervals, transmitting or receiving communication to the UE in a communication direction that is not a disallowed communication direction.

[0016] Some aspects described herein relate to a non-transient computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive from a network node an indication of one or more full-duplex time intervals. When executed by one or more processors of the UE, the set of instructions enables the UE to receive from a network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit or receive communication from a network node during one of the one or more full-duplex time intervals, depending on whether the communication is in a communication direction that is not a disallowed communication direction.

[0017] Some aspects described herein relate to a non-transient computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions can cause the network node to transmit indications associated with a UE for one or more full-duplex time intervals. When executed by one or more processors of the network node, the set of instructions can cause the network node to transmit indications associated with a UE for disallowed communication directions associated with one or more full-duplex time intervals. When executed by one or more processors of the network node, the set of instructions can cause the network node to transmit or receive communication during one of the one or more full-duplex time intervals, depending on whether the communication to the UE is in a communication direction that is not a disallowed communication direction.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving from a network node an indication of one or more full-duplex time intervals. The apparatus may include means for receiving from a network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals. The apparatus may include means for transmitting or receiving communication to or from the network node during one of the one or more full-duplex time intervals, depending on whether the communication is in a communication direction that is not a disallowed communication direction.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting an indication associated with a UE of one or more full-duplex time intervals. The apparatus may include means for transmitting an indication associated with a UE of a disallowed communication direction associated with one or more full-duplex time intervals. The apparatus may include means for transmitting or receiving communication during one of the one or more full-duplex time intervals, depending on whether the communication to the UE is in a communication direction that is not a disallowed communication direction.

[0020] The terms generally include, as substantially described herein with reference to the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transient computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as explained in the accompanying drawings and description.

[0021] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described thereafter. The disclosed concepts and specific examples can be readily used as the basis for modifications or the design of other structures for implementing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not for defining limitations on the claims. Brief description of the attached diagram

[0023] To gain a more detailed understanding of the features described above in this disclosure, reference can be made to various aspects of the above brief overview, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only some typical aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description. Identical reference numerals in different drawings may identify the same or similar elements.

[0024] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

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

[0026] Figure 3 This is a diagram illustrating an example decomposed base station architecture based on this disclosure.

[0027] Figures 4A-4C This is a diagram illustrating an example of full-duplex communication according to this disclosure.

[0028] Figure 5 This is a diagram illustrating an example of full-duplex communication according to this disclosure.

[0029] Figure 6 This is a diagram illustrating an example of a full-duplex time-slot configuration according to this disclosure.

[0030] Figure 7 This is a diagram illustrating an example of full-duplex operation at a network node according to this disclosure.

[0031] Figure 8 This is a diagram illustrating an example of an operation associated with a communication direction that is not permitted during a full-duplex time interval, in accordance with this disclosure.

[0032] Figure 9 This is a diagram illustrating an example of communication directions that are not permitted for full-duplex time intervals, according to this disclosure.

[0033] Figure 10 This is a diagram illustrating an example of communication directions that are not permitted for full-duplex time intervals, according to this disclosure.

[0034] Figure 11 This is a flowchart illustrating an example process performed by a UE, according to this disclosure, to support communication directions that are not permitted for full-duplex time intervals.

[0035] Figure 12 This is a flowchart illustrating an example process performed by a network node, according to this disclosure, to support communication directions not permitted for full-duplex time intervals.

[0036] Figure 13 This is a diagram of an example apparatus for supporting wireless communication in directions where communication is not permitted for full-duplex time intervals, according to the present disclosure.

[0037] Figure 14 This is a diagram of an example apparatus for supporting wireless communication in directions where communication is not permitted for full-duplex time intervals, according to the present disclosure.

[0038] Detailed description

[0039] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and is not to be construed as limited to any specific structure or function given throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using additional structures, functionalities, or structures and functionalities that complement or supplement the various aspects of this disclosure set forth herein. Any aspect of this disclosure disclosed herein may be implemented by one or more elements of the claims.

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

[0041] Various aspects generally relate to communication directions that are not permitted during a full-duplex time interval. Some aspects more specifically relate to defining permitted and / or prohibited communication directions for user equipment (UE) during a full-duplex time interval (e.g., for time slots and / or symbols associated with full-duplex operation). In some aspects, a network node may transmit an indication of a communication direction (and / or channel and / or reference signal) that is disabled or to be discarded (e.g., not received or transmitted) during a time slot or symbol associated with full-duplex operation at that network node. The UE may transmit or receive communication in a permitted communication direction during a full-duplex time interval (e.g., the communication is not in a prohibited communication direction). In some aspects, the UE may suppress the transmission or reception (e.g., may discard) of communication in a prohibited communication direction during a full-duplex time interval.

[0042] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to clarify how the UE will utilize the full-duplex time interval when a network node is operating in full-duplex mode (e.g., using non-co-located antennas and / or transmit-receive points (TRPs)). For example, during the full-duplex time interval, the UE can transmit or receive communication in permitted communication directions and / or can discard communication in prohibited communication directions. This can save UE resources (e.g., power resources, processing resources, and / or network resources) that would otherwise be used to attempt to transmit or receive communication in prohibited communication directions (e.g., to or from antennas and / or TRPs of network nodes that are not available for use in prohibited communication directions during the full-duplex time interval). The efficiency of the UE and the wireless communication system can thus be improved.

[0043] In some respects, feedback operations can be defined for dropped communications associated with disallowed communication directions. For example, when a UE does not receive downlink communication (e.g., because downlink is a disallowed communication direction), the UE can suppress the transmission of Hybrid Automatic Repeat Request (HARQ) feedback for downlink communication (e.g., thereby saving power resources, processing resources, and / or network resources that the UE would otherwise have used to transmit HARQ feedback for downlink communication, which the network node is already aware was not transmitted to the UE).

[0044] In some respects, indications of disallowed communication directions can be associated with a given control resource set (CORESET) pool index value. For example, a network node can transmit, and a UE can receive, indications that communication associated with a given communication direction and a given CORESET pool index value is disallowed, disabled, and / or to be discarded during a full-duplex time interval. This enables improved control and / or flexibility in indicating disallowed (and / or permitted) communication directions in multi-TRP and / or multi-downlink control information (multi-DCI) scenarios.

[0045] Figure 1This is a diagram illustrating an example of a wireless network according to this disclosure. Wireless network 100 may be or may include a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements thereof. Wireless network 100 may include one or more network nodes 110 (shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other network entities. Network node 110 is the entity that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 may be an aggregated network node, meaning that an aggregated network node is configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or cell). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), which means that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among 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)).

[0046] In some examples, network node 110 is or includes network nodes such as RU that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes such as DU that communicate with other network nodes 110 via outbound or mid-range links. In some examples, network node 110 is or includes network nodes such as CU that communicate with other network nodes 110 via mid-range links or with the core network via backhaul links. In some examples, network node 110 (such as aggregated network node 110 or 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. Network node 110 may include, for example, NR network nodes, LTE network nodes, B nodes, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, or TRPs, DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, and / or RAN nodes. In some examples, network nodes 110 can interconnect with each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network through various types of outbound, mid-range and / or return interfaces (such as direct physical connections, air interfaces or virtual networks).

[0047] Each network node 110 can provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area, depending on the context in which the term is used.

[0048] Network node 110 can provide communication coverage to macrocells, picocells, femtocells, or another type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs 120 with a service subscription. Picocells can cover a relatively small geographic area and allow unrestricted access by UEs 120 with a service subscription. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs 120 associated with that femtocell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). Network node 110 for macrocells may be referred to as a macro network node. Network node 110 for picocells may be referred to as a pico network node. Network node 110 for femtocells may be referred to as a femto network node or a home network node.

[0049] Wireless network 100 can be a heterogeneous network comprising different types of network nodes 110 (such as macro nodes, pico nodes, femto nodes, or relay nodes). These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in wireless network 100. For example, macro nodes may have high transmit power levels (e.g., 5 to 40 watts), while pico nodes, femto nodes, and relay nodes may have lower transmit power levels (e.g., 0.1 to 2 watts). Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. A network node can support one or more (e.g., three) cells. In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0050] In some aspects, the term "base station" or "network node" may refer to a clustered 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, "base station" or "network node" may refer to a CU, DU, RU, near real-time (near RT) RAN intelligent controller (RIC), and / or a non-real-time (non-RT) RIC. In some aspects, the term "base station" or "network entity" 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 multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat the performance of at least a portion of that 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 can 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 rather than another. In this way, a single device can include more than one base station.

[0051] Network controller 130 can be coupled to or communicate with a group of network nodes 110 and can provide coordination and control over these network nodes 110. Network controller 130 can communicate with network nodes 110 via a backhaul communication link. Network nodes 110 can communicate with each other directly or indirectly via wireless or wired backhaul communication links. In some aspects, network controller 130 can be a CU or a core network device, or network controller 130 may include a CU or a core network device.

[0052] In some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile network node 110 (e.g., a mobile network node). In some examples, network nodes 110 may interconnect with each other or to one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0053] Wireless network 100 may include one or more relay stations. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., network node 110 or UE 120) and transmitting those data to a downstream station (e.g., UE 120 or network node 110). A relay station may be a UE 120 capable of relaying transmissions for other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 that relays communication may be referred to as a relay station, relay network node, or relay.

[0054] Each UE 120 may be distributed 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, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), 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 device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

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

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

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

[0058] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). Although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2, although it is different from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0059] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) frequencies. Recent 5G NR studies have designated the operating bands of these IF frequencies as the frequency range designation FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 or FR2 characteristics, thus effectively extending the features of FR1 or FR2 into the IF frequency range. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been designated as the 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.

[0060] Considering the foregoing, unless otherwise stated, the term "sub-6GHz" as used herein may broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, it should be understood that the term "millimeter wave" as used herein may broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, or within the EHF band. It is conceivable that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0061] In some aspects, UE 120 may include a communication manager 140. As described elsewhere in this document in more detail, the communication manager 140 may: receive from a network node an indication of one or more full-duplex time intervals; receive from a network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals; and during one of the one or more full-duplex time intervals, transmit or receive the communication to or from the network node in a communication direction that is not a disallowed communication direction. That is, the communication manager 140 of UE 120 may transmit or receive the communication to or from the network node during one of the one or more full-duplex time intervals, depending on whether the communication is in a communication direction that is not a disallowed communication direction. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein. UE 120 may transmit or receive communication during a full-duplex time interval in response to communication in a permitted communication direction (e.g., communication not in a disallowed communication direction). Additionally or alternatively, UE 120 may suppress (e.g., drop) the transmission or reception of communication during a full-duplex time interval in response to communication being in an unallowed communication direction (e.g., communication is not in a permitted direction). For example, a permitted communication direction could be a downlink direction in which communication is transmitted from network node 110 to UE 120. In such an example, an unallowed communication direction could be an uplink direction. Alternatively, for example, a permitted direction could be an uplink direction in which communication is transmitted from UE 120 to network node 110. In such an example, an unallowed communication direction could be a downlink direction. Therefore, UE 120 may determine, based on, in response to, or otherwise in association with an indication of an unallowed communication direction received from network node 110, whether communication during one or more full-duplex time intervals is in an unallowed communication direction. UE 120 may transmit or receive communication, or suppress the transmission or reception of communication, based on this determination.

[0062] In some aspects, network node 110 may include communication manager 150. As described elsewhere in this document in more detail, communication manager 150 may: transmit an indication associated with the UE for one or more full-duplex time intervals; transmit an indication associated with the UE for a disallowed communication direction associated with the one or more full-duplex time intervals; and, during one of the one or more full-duplex time intervals, transmit or receive communication in a communication direction that is not a disallowed communication direction. That is, communication manager 150 of network node 110 may transmit or receive communication from UE 120 during one of the one or more full-duplex time intervals, depending on whether communication for UE 120 is in a communication direction that is not a disallowed communication direction. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein. Network node 110 may transmit or receive communication during a full-duplex time interval in response to communication in a permitted communication direction (e.g., communication not in a disallowed communication direction). Additionally or alternatively, network node 110 may suppress (e.g., drop) transmission or reception of communication during a full-duplex time interval in response to communication being in an unallowed communication direction (e.g., communication is not in a permitted direction). For example, a permitted communication direction may be a downlink direction in which communication is transmitted from network node 110 to UE 120. In such an example, an unallowed communication direction may be an uplink direction. Alternatively, for example, a permitted direction may be an uplink direction in which communication is transmitted from UE 120 to network node 110. In such an example, an unallowed communication direction may be a downlink direction. Therefore, network node 110 may determine, based on, in response to, or otherwise in association with an indication of an unallowed communication direction associated with UE 120, whether communication during one or more full-duplex time intervals is in an unallowed communication direction. Network node 110 may transmit or receive communication, or suppress transmission or reception of communication, based on this determination.

[0063] Figure 2 This is a diagram illustrating an example of communication between a network node and a UE in a wireless network according to this disclosure. The network node can correspond to... Figure 1 Network node 110 in the network. Similarly, the UE can correspond to... Figure 1 UE 120. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). Figure 2The network node 110 depicted includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0064] At network node 110, transmit processor 220 can receive data from data source 212 intended for UE 120 (or a group of UEs 120). Transmit processor 220 can select one or more modulation and coding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120, at least in part, based on the MCS(s) selected for UE 120, and can provide data symbols to UE 120. Transmit processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or higher-layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 can generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols where applicable, and can 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 can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can further use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can transmit downlink signal sets (e.g., T downlink signals) via corresponding sets of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0065] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to an array of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain an input sample. Each modem 254 can use a demodulator component to further process the input sample (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain the received symbols from modems 254, perform MIMO detection on these received symbols where applicable, and can provide detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) these detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers and / or one or more processors. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, or CQI parameters, etc. In some examples, one or more components of UE 120 may be included in housing 284.

[0066] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in the core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0067] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more antenna element assemblies, or one or more antenna arrays. Antenna panels, antenna groups, antenna element assemblies, or antenna arrays may include one or more antenna elements (within a single or multiple housings), coplanar antenna element assemblies, non-coplanar antenna element assemblies, or be coupled to one or more transmitting or receiving components (such as...). Figure 2 One or more antenna elements (one or more components).

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

[0069] At network node 110, uplink signals from UE 120 or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antennas 234, modems 232, MIMO detectors 236, receiver processors 238, transmitter processors 220, and / or TX MIMO processors 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein.

[0070] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or Figure 2Any other component may perform one or more techniques associated with communication directions not permitted for full-duplex time intervals, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or... Figure 2 Any other component may execute or direct, for example Figure 11 Process 1100 Figure 12 The operation of process 1200 or other processes as described. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, when executed by one or more processors of network node 110 or UE 120 (e.g., directly executed, or executed after compilation, transformation, or interpretation), the one or more processors, UE 120, or network node 110 may cause the one or more processors, UE 120, or network node 110 to perform or direct, for example... Figure 11 Process 1100 Figure 12 The operation of process 1200 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, or interpret instructions, etc.

[0071] In some aspects, UE 120 may include: means for receiving from a network node an indication of one or more full-duplex time intervals; means for receiving from a network node an indication of an unallowed communication direction associated with one or more full-duplex time intervals; and / or means for transmitting the communication to the network node during one of the one or more full-duplex time intervals based on the communication being in a communication direction that is not an unallowed communication direction, or means for receiving the communication from the network node during one of the one or more full-duplex time intervals based on the communication being in a communication direction that is not an unallowed communication direction (e.g., means for transmitting to the network node or means for receiving from the network node). Means for UE 120 to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0072] In some aspects, network node 110 may include means for transmitting an indication of one or more full-duplex time intervals associated with the UE; means for transmitting an indication of a disallowed communication direction associated with the one or more full-duplex time intervals associated with the UE; and / or means for transmitting communication in a communication direction that is not a disallowed communication direction during one of the one or more full-duplex time intervals, or means for receiving communication in a communication direction that is not a disallowed communication direction during one of the one or more full-duplex time intervals. Means for network node 110 to perform the operations described herein may include, for example, one or more of 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.

[0073] Communication systems (such as 5G NR systems) can be deployed with various components or parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a clustered or decomposed architecture. For example, base stations (such as B-nodes (NBs), evolved NBs (eNBs), NR base stations, 5G NBs, access points (APs), TRPs, or cells, etc.), or one or more units (or components) performing base station functions, can be implemented as clustered base stations (also known as self-contained base stations or monolithic base stations) or decomposed base stations. A "network entity" or "network node" can 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, and / or one or more RUs).

[0074] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). Decentralized base stations (e.g., decentralized network nodes) can be configured to utilize a protocol stack that is physically or logically distributed among 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 the CU, DU, and RU can also be implemented as a virtual unit, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0075] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate scaling of the communication system by partitioning base station functionality into one or more units that can be deployed individually. Decomposed base stations can include functionality implemented across two or more units located at various physical locations, as well as functionality implemented for at least one unit virtually distributed, which allows for flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0076] In some respects, actions described herein as being performed by network node 110 can be performed by multiple different network nodes. For example, configuration actions may be performed by a first network node (e.g., CU or DU), while radio communication actions may be performed by a second network node (e.g., DU or RU).

[0077] As used herein, "outputting" or "transmitting" communication from network node 110 to UE 120 can refer to direct transmission (e.g., from network node 110 to UE 120) or indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, indirect transmission to UE 120 can include the DU outputting or transmitting communication to an RU and the RU transmitting communication to UE 120, or can include causing the RU to transmit communication (e.g., triggering the transmission of a physical layer reference signal). Similarly, "transmitting" communication from UE 120 to network node 110 can refer to direct transmission (e.g., from UE 120 to network node 110) or indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, indirect transmission to network node 110 can include the UE 120 transmitting communication to an RU and the RU transmitting the communication to the DU. Similarly, network node 110 “receiving” communication can refer to receiving a transmission that directly carries the communication (e.g., from UE 120 to network node 110) or receiving communication (or information derived from receiving the communication) via one or more other network nodes or devices.

[0078] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via 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 a corresponding midrange link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding outhaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0079] Each of these units (including CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO frame 305) may include one or more interfaces, or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, may be configured to communicate with one or more other units via transmission media. In some examples, each of these units may include: a wired interface configured to receive or transmit signals to one or more other units over a wired transmission medium; and a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals to one or more other units over a wireless transmission medium, or both.

[0080] In some aspects, the CU 310 may store one or more higher-level 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 with an interface configured to communicate signaling with other control functions stored in the CU 310. The CU 310 may be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions) and / or control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions). In some implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). The CU 310 may be implemented as needed to communicate with the DU330 for network control and signaling.

[0081] Each DU 330 may correspond to a logical unit including one or more base station functions to control the operation of one or more RU 340s. In some aspects, the DU 330 may, at least in part, depend on functional splits (such as those defined by 3GPP) to store one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation. In some aspects, the DU 330 may further store one or more low PHY layers (such as through one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering). Each layer (which may also be referred to as a module) may be implemented with an interface configured to communicate signals with other layers (and modules) stored by the DU 330 or with control functions stored by the CU 310.

[0082] Each RU 340 can implement lower-layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that performs main memory (such as performing FFT, performing iFFT, digital beamforming, or PRSCH extraction and filtering) RF processing functions or low-PHY layer functions based on functional partitioning (e.g., functional partitioning defined by 3GPP) (such as lower-layer functional partitioning). In such architectures, each RU 340 can be operated to handle over-the-air (OTA) communication with one or more UEs 120. In some implementations, the real-time and non-real-time aspects of control and user plane communication with (the) RU 340s can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as vRAN architecture).

[0083] SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 305 can 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 the 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-RT RIC 315. In some implementations, SMO framework 305 can communicate with the hardware aspects of the 4G RAN (such as an Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, SMO framework 305 can communicate directly with one or more RU 340s via the corresponding O1 interface. SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of SMO framework 305.

[0084] The non-RT RIC 315 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-guided controls and optimizations of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

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

[0086] In some examples, an access node may include an access node controller. The access node controller may be a CU of a distributed RAN. In some examples, backhaul interfaces to the core network may terminate at the access node controller. The core network may include 5G control plane components and 5G user plane components (e.g., a 5G gateway including both 5G control plane components and 5G user plane components), and backhaul interfaces for one or both of the 5G control plane and 5G user plane may terminate at the access node controller. Additionally or alternatively, backhaul interfaces to one or more neighboring access nodes (e.g., another access node) may terminate at the access node controller.

[0087] An access node controller may be associated with or communicate with one or more TRPs (e.g., via an F1 control (F1-C) interface or an F1 user (F1-U) interface). In some cases, a TRP may be referred to as a cell, panel (e.g., antenna panel), antenna array, or array, etc. Each TRP may be a DU or RU of a distributed RAN. A TRP may be connected to a single access node controller or multiple access node controllers. In some examples, a TRP may correspond to a combination of the above. Figure 1 , 2 Or the base station described in 3. For example, different TRPs may be included in different corresponding base stations. Additionally or alternatively, multiple TRPs may be included in a single base station. In some aspects, a decomposed base station may include a CU (e.g., an access node controller) or one or more DUs (e.g., one or more TRPs). In some examples, the functional decomposition of base station functionality between the access node controller (e.g., CU) and the TRP (e.g., DU or RU) may be as defined by 3GPP. For example, the PDCP layer, RLC layer, or MAC layer may be configured to terminate at the access node controller or TRP.

[0088] In some examples, multiple TRPs can transmit communication (e.g., the same communication or different communication) in the same Transmission Time Interval (TTI) (e.g., time slot, mini-time slot, subframe, or symbol) or in different TTIs using different Quasi-Co-location (QCL) relationships (e.g., different spatial parameters, different TCI states, different precoding parameters, or different beamforming parameters). In some aspects, the TCI state can be used to indicate one or more QCL relationships. Each TRP can be configured to serve traffic to UE120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs).

[0089] In some examples, a first Physical Downlink Control Channel (PDCCH) (PDCCH 1) communication transmitted by a first TRP (TRP A) can be scheduled for a first Physical Uplink Shared Channel (PUSCH) communication (PUSCH 1) to transmit uplink data to TRP A, and a second TRP (TRP B) can be scheduled for a second PUSCH communication (PUSCH 2) to transmit uplink data to TRP B. A Control Resource Set (CORESET) pool index (or CORESETPoolIndex) value can be used by UE 120 to identify a TRP associated with an uplink grant received on a PDCCH. For example, multiple PDCCHs can be used to schedule downlink or uplink data communication for multiple corresponding Physical Downlink Shared Channels (PDSCHs) or multiple corresponding PUSCHs (e.g., one PDCCH for each PDSCH or PUSCH). In such examples, a DCI (e.g., having DCI format 1_0 or DCI format 1_1) can indicate the corresponding Transport Configuration Indicator (TCI) state of the TRP corresponding to that DCI. The TCI field of a DCI indicates the corresponding TCI state (e.g., the TCI field of the first DCI indicates the first TCI state and the TCI field of the second DCI indicates the second TCI state). This can be referred to as a multi-DCI (mDCI) multi-TRP operation.

[0090] A multi-TRP operation configuration based on multiple DCIs allows the UE to communicate concurrently via multiple TRPs. For example, the UE can receive a first DCI in a first PDCCH from a first TRP, where the first DCI is scheduled to be transmitted by the first TRP as a first PDSCH or PUSCH. Similarly, the UE can receive a second DCI in a second PDCCH from a second TRP, where the second DCI is scheduled to be transmitted by the second TRP as a second PDSCH or PUSCH. The first and second PDSCHs or PUSCHs can be non-overlapping, partially overlapping, or fully overlapping. In association with monitoring DCIs transmitted from different TRPs, the UE can monitor PDCCH candidates during PDCCH monitoring in different CORESETs.

[0091] "CORESET" can refer to a control region constructed to support efficient use of resources (such as by flexibly configuring or reconfiguring resources for one or more PDCCHs associated with the UE). In some examples, a CORESET may occupy the first symbol of an Orthogonal Frequency Division Multiplexing (OFDM) slot, the first two symbols of an OFDM slot, or the first three symbols of an OFDM slot. Thus, a CORESET may include multiple resource blocks (RBs) in the frequency domain and one, two, or three symbols in the time domain. In 5G, the number of resources included in a CORESET can be flexibly configured (e.g., by using RRC signaling to indicate the frequency domain region (e.g., the number of resource blocks) or the time domain region (e.g., the number of symbols) of the CORESET).

[0092] UE 120 can be configured with multiple CORESETs in a given serving cell. Each CORESET configured for UE 120 can be associated with a CORESET identifier (CORESET ID). In some examples, two or more (e.g., up to five) CORESETs can be grouped into a CORESET pool. Each CORESET pool can be associated with a CORESET pool index value. As an example, CORESET ID 1 and CORESET ID 2 can be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 can be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index value can be associated with a given TRP. As an example, TRP A can be associated with CORESET pool index 0, and TRP B can be associated with CORESET pool index 1. UE 120 can be configured with information identifying the association between a TRP and the CORESET pool index value assigned to that TRP via higher-layer parameters (such as PDCCH-Config (PDCCH configuration) RRC parameters). Accordingly, UE120 can identify a TRP that transmits DCI uplink grant by: determining the CORESET ID of the CORESET in which a PDCCH carrying DCI uplink grant is transmitted, determining the CORESET pool index value associated with the CORESET pool that includes the CORESET ID, and identifying the TRP associated with the CORESET pool index value.

[0093] Figures 4A-4C This is a diagram illustrating an example of full-duplex communication according to this disclosure. Figure 4AThe first full-duplex scenario 400 depicted includes UE1 402 and two network nodes (e.g., network entities or TRPs) 404-1 and 404-2, wherein UE1 402 is sending uplink transmissions to network node 404-1 and receiving downlink transmissions from network node 404-2. Figure 4A In the first full-duplex scenario 400, full-duplex is enabled for UE1 402, but not for network nodes 404-1 and 404-2. Figure 4B The second full-duplex scenario 410 depicted includes two UEs (shown as UE1 402-1 and UE2 402-2) and a network node 404, where UE1 402-1 is receiving downlink transmissions from network node 404 and UE2 402-2 is transmitting uplink transmissions to network node 404. In the second full-duplex scenario 410, full-duplex is enabled for network node 404, but not for UE1 402-1 and UE2 402-2. The third full-duplex scenario 420... Figure 4C The scenario depicts a UE1 402 and a network node 404, where UE1 402 is receiving downlink transmissions from network node 404 and transmitting uplink transmissions to network node 404. In the third full-duplex scenario 420, full-duplex is enabled for both UE1 402 and network node 404.

[0094] Figure 5 This is a diagram illustrating an example of full-duplex communication 500 according to this disclosure. The UE can operate in in-band full-duplex mode. In in-band full-duplex mode, the UE can transmit and receive on the same time and frequency resources. The uplink and downlink can share the same time and frequency resources. For example, in the first full-duplex communication 502, the time and frequency resources used for the uplink can completely overlap with the time and frequency resources used for the downlink. As another example, in the second full-duplex communication 504, the time and frequency resources used for the uplink can partially overlap with the time and frequency resources used for the downlink.

[0095] The UE can operate in subband full-duplex mode. SBFD mode can also be called subband frequency division duplex mode or flexible duplex mode. In SBFD mode, the UE can transmit and receive simultaneously, but on different frequency domain resources. For example, in third full-duplex communication 506, downlink resources can be separated from uplink resources in the frequency domain by guard bands. In some examples, SBFD can be associated with a network node operating in full-duplex mode (e.g., transmitting and receiving simultaneously on different frequency domain resources). In such examples, the UE communicating with the network node can operate in half-duplex mode.

[0096] In some examples, time slot configuration may include a combination of downlink time slots, uplink time slots, or full-duplex time slots (e.g., SBFD time slots or in-band full-duplex time slots). A full-duplex time slot may include one or more downlink time / frequency resources and one or more uplink time / frequency resources. Downlink time / frequency resources in a full-duplex time slot can be separated from uplink time / frequency resources in the same full-duplex time slot by gaps (e.g., in time or frequency), which can reduce self-interference and improve latency and uplink coverage. For example, a gap may be a frequency offset or frequency gap between downlink and uplink time / frequency resources within the same full-duplex time slot. For example, a network node may operate in full-duplex mode (e.g., simultaneously transmitting and receiving on the same or different frequency domain resources). A network node may schedule a first UE to receive downlink communication in a full-duplex time slot. A network node may schedule a second UE to transmit uplink communication in the same full-duplex time slot.

[0097] Figure 6 This is a diagram illustrating an example of a full-duplex timeslot configuration 600 according to this disclosure. In some examples, UE 120 may be configured to have a first configuration 602. In some examples, the first configuration 602 may indicate a first timeslot format pattern (sometimes referred to as a Time Division Duplex (TDD) mode) associated with a half-duplex or full-duplex mode. The first timeslot format pattern may include the number of downlink timeslots (e.g., three downlink timeslots 604a, 604b, and 604c as shown), the number of flexible timeslots (not shown), and / or the number of uplink timeslots (e.g., one uplink timeslot 606 as shown). The first timeslot format pattern may be repeated over time. In some examples, network node 110 may use one or more timeslot format indicators to indicate the first timeslot format pattern to UE 120. The timeslot format indicator used for a timeslot may indicate whether the timeslot is an uplink timeslot, a downlink timeslot, or a flexible timeslot, etc.

[0098] Network node 110 may transmit an indication (e.g., RRC message, MAC control element (MAC-CE), or DCI) to UE 120 to switch from first configuration 602 to second configuration 608. Alternatively, UE 120 may indicate to network node 110 that UE 120 is switching from first configuration 602 to second configuration 608. Second configuration 608 may indicate a second timeslot format pattern that repeats in time, similar to the first timeslot format pattern. In any of the examples described above, UE 120 may switch from first configuration 602 to second configuration 608 (e.g., before switching back to first configuration 602) for a period of time (e.g., the number of symbols and / or the amount of time) based on, in response to, or otherwise associated with an indication received from network node 110. During this period, UE 120 may use the second timeslot format pattern for communication and may then resume using the first timeslot format pattern after the end of the period. This time period may be indicated by network node 110 (e.g., in an instruction to switch from the first configuration 602 to the second configuration 608, as described above) and / or associated with, in response to, or otherwise with programmed and / or otherwise pre-configured rules. For example, the rules may be based at least in part on a table (e.g., a table defined in 3GPP specifications and / or another wireless communication standard) that associates different subcarrier spacings (SCS) and / or parameter designs (e.g., denoted by μ and associated with the corresponding SCS) with the corresponding time period used for switching configurations.

[0099] The second time-slot format pattern may include two SBFD time slots in place of the downlink time slots in the first time-slot format pattern. In Example 600, the second time-slot format pattern includes downlink time slot 610 and uplink time slot 618. In some examples, each SBFD time slot includes partial time slots (e.g., partial time slots 612a, 612b, 612c, and 612d, as shown) for downlink (e.g., a portion or subband of frequencies allocated to network node 110 and UE 120) and partial time slots (e.g., partial time slots 614a and 614b, as shown) for uplink. Accordingly, compared to using the first time-slot format pattern (e.g., the fourth time slot in the sequence, shown as UL time slot 606), UE 120 can use the second time-slot format pattern to operate in an earlier time slot (e.g., the second time slot in the sequence, shown as partial uplink (UL) time slot 614a). Other examples may include additional or replacement changes. For example, the second configuration 608 may indicate an SBFD time slot in place of the uplink time slot in the first configuration 602 (e.g., UL time slot 606). In another example, the second configuration 608 may indicate either a downlink time slot or an uplink time slot in place of the SBFD time slot in the first configuration 602. Figure 6(Not shown in the image). In yet another example, the second configuration 608 may indicate a downlink time slot or an uplink time slot to replace the uplink time slot or downlink time slot in the first configuration 602, respectively. "SBFD time slot" may refer to a time slot in which the SBFD format is used. The SBFD format may include a time slot format in which full-duplex communication (e.g., for both uplink and downlink communication) is supported, wherein one or more frequencies for the uplink portion of the time slot are separated from one or more frequencies for the downlink portion of the time slot by guard bands.

[0100] As used herein, "full-duplex time interval" can refer to a full-duplex time slot, a full-duplex mini-time slot (e.g., one or more symbols within a time slot associated with full-duplex operation), and / or a full-duplex OFDM symbol, etc. "Full-duplex" can refer to SBFD, in-band full-duplex, and / or other types of full-duplex operation. For example, a "full-duplex time slot" can refer to an SBFD time slot, an in-band full-duplex time slot, and / or a time slot associated with another type of full-duplex operation. For example, a full-duplex time interval can be the time interval during which network node 110 is operating in full-duplex mode, as described in more detail elsewhere herein.

[0101] In some examples, the SBFD format may include a single uplink portion and a single downlink portion separated by a guard band. In some examples, the SBFD format may include multiple downlink portions and a single uplink portion separated from those multiple downlink portions by corresponding guard bands (e.g., as shown in the image). Figure 6 (As shown). In some examples, the SBFD format may include multiple uplink portions and a single downlink portion separated from the multiple uplink portions by corresponding guard bands. In some examples, the SBFD format may include multiple uplink portions and multiple downlink portions, wherein each uplink portion is separated from the downlink portion by a guard band. In some examples, operating using SBFD mode may include activating or using full-duplex mode in one or more time slots based on, in response to, or otherwise associated with one or more time slots having the SBFD format. A time slot may support SBFD mode if the uplink bandwidth portion (BWP) and the downlink BWP are permitted or synchronously active in the time slot in an SBFD manner (e.g., with guard band separation).

[0102] By switching from the first configuration 602 to the second configuration 608, network node 110 and UE 120 can experience improved communication quality and / or reliability. For example, network node 110 and UE 120 may experience increased throughput (e.g., using full-duplex mode), reduced latency (e.g., UE 120 may be able to use the second configuration 608 instead of the first configuration 602 to transmit uplink and / or downlink communication faster), and increased network resource utilization (e.g., by using both downlink and uplink BWPs simultaneously, instead of using only one). Although some aspects are described in this document at the slot-level granularity, such as Figure 6 As shown in the figure, other granularities can be used, such as sub-slot level granularity or symbol level granularity, etc.

[0103] Figure 7 This is a diagram illustrating an example of full-duplex operation 700 at a network node according to this disclosure. For example... Figure 7 As shown, network node 110 can be associated with multiple TRPs, shown as TRP 1 705 and TRP 2 710. In the first operation 715, network node 110 can operate in full-duplex mode. For example, network node 110 can simultaneously transmit and receive communications (e.g., via multiple TRPs).

[0104] As described elsewhere in this document, network node 110 operating in full-duplex mode may experience self-interference. For example, downlink transmissions from network node 110 may self-interfere with uplink transmissions to network node 110. This can be caused by various factors, such as higher transmit power used for downlink transmissions (compared to uplink transmissions) and / or radio frequency bleeding. Therefore, to improve spatial isolation, when operating in full-duplex mode, network node 110 may use TRP 1 705 for downlink signals and a second TRP 2 710 for uplink signals. For example, TRP 1 705 and TRP 2 710 may be spatially isolated from each other, thereby reducing the likelihood of downlink transmissions from TRP 1 705 interfering with uplink transmissions to TRP 2 710 (e.g., when downlink and uplink transmissions at least partially overlap in the time domain). For example, improving the spatial isolation of the antennas and / or TRPs used by network node 110 during full-duplex operation can reduce self-interference associated with full-duplex operation. Therefore, when network node 110 is operating in full-duplex mode, TRP 1 705 may not be available for uplink operation, and TRP 2 710 may not be available for downlink operation.

[0105] like Figure 7As shown, network node 110 can communicate with UE 1 (e.g., UE 120), UE 2 (e.g., UE 120), and UE 3 (e.g., UE 120). UE 1, UE 2, and UE 3 can each operate in a non-full-duplex mode (e.g., half-duplex mode). In some cases, when network node 110 is operating in full-duplex mode, UEs (e.g., UE 1, UE 2, and / or UE 3) may experience poor performance in a given communication direction due to the unavailability of a given TRP for uplink or downlink communication. For example, the serving TRP of UE 1 (e.g., for downlink and uplink) could be TRP 1705. UE 1 may not support or be able to have multiple active TCI states or beams. If the active TCI state or beam associated with UE 1 (e.g., for uplink communication) is associated with a specific direction toward TRP 1 705, UE 1 may be unable to transmit uplink communication during the full-duplex time interval (e.g., because TRP 1 705 is unavailable for uplink operation, and UE 1 cannot support the additional active beam or TCI state associated with TRP 2 710). Additionally or alternatively, the link between UE 1 and TRP 2 710 may be associated with poor radio conditions (e.g., large path loss), resulting in poor performance of uplink communication transmitted from UE 1 to TRP 2 710.

[0106] As another example, UE 3 may be associated with poor performance of downlink communication during the full-duplex time interval. For example, the serving TRP of UE 3 (e.g., for both downlink and uplink) could be TRP 2 710. UE 3 may not support or be able to have multiple active TCI states or beams. If the active TCI states or beams associated with UE 3 (e.g., for downlink communication) are associated with a specific direction toward TRP 2 710, UE 3 may be unable to receive downlink communication during the full-duplex time interval (e.g., because TRP 2 710 is not available for downlink operation, and UE 3 cannot support additional active beams or TCI states associated with TRP 1 705). Additionally or alternatively, the link between UE 3 and TRP 1705 may be associated with poor radio conditions (e.g., large path loss), resulting in poor performance of downlink communication transmitted from TRP 1705 to UE 3.

[0107] For example, UE 1 and / or UE 3 may need to switch TCI states used for uplink and downlink communication during a full-duplex time interval. This is associated with significant signaling overhead related to network node 110 indicating which new TCI states to use by UE 1 and / or UE 3. Additionally, there may be a delay before UE 1 and / or UE 3 can apply which new TCI states (e.g., associated with the application and / or processing time of TCI states or beam indices). As a result, UE 1 and / or UE 3 may not be able to switch to which new TCI states before an upcoming full-duplex time interval and / or before an upcoming scheduled communication.

[0108] In some examples, a UE (e.g., UE 1 or UE 3) may rely on network node 110 to suppress the scheduling of communication in communication directions associated with poor performance during full-duplex time intervals (e.g., UE 1 may rely on network node 110 to suppress the scheduling of uplink communication for UE 1, and UE 3 may rely on network node 110 to suppress the scheduling of downlink communication for UE 3). However, relying on network node 110 for scheduling may be infeasible or unreliable in certain situations. For example, some communication may be periodic and / or semi-persistent (e.g., occurring every X timeslots, symbols, or milliseconds). The periodicity of these communications may be inconsistent with the periodicity of the timeslot format, resulting in some of the periodic and / or semi-persistent communication being scheduled to occur during full-duplex time intervals. Additionally, the full-duplex timeslot format may be dynamically configured for the UE, causing periodic and / or semi-persistent communication that would otherwise occur during non-full-duplex time intervals to be scheduled to occur during full-duplex time intervals.

[0109] As another example, communication can be associated with one or more repetitions. For example, PDSCH communication, PDCCH communication, PUSCH communication, and / or Physical Uplink Control Channel (PUCCH) communication can be associated with one or more repetitions. Although communication can be scheduled during non-full-duplex time intervals, repetition of communication may occur during full-duplex time intervals. Attempting to limit repetitions to occur during full-duplex time intervals may be associated with a high level of complexity and / or may limit the flexibility of scheduling communication associated with repetitions. As another example, a single DCI communication can schedule multiple communications (e.g., different transport blocks may be scheduled). Although one or more of the multiple communications may be scheduled during non-full-duplex time intervals, one or more other communications may occur during full-duplex time intervals. Attempting to limit communication scheduled by a single DCI communication to occur during full-duplex time intervals may be associated with a high level of complexity and / or may limit the flexibility of scheduling multiple communications with a single DCI communication.

[0110] The UE may be unaware of communication directions that could be associated with poor performance for the UE during the full-duplex time interval. Therefore, if the communication direction of a scheduled communication (e.g., periodic communication, repetition of communication, communication from multiple communications scheduled by a single DCI, or another communication) is associated with poor performance for the UE during the full-duplex time interval, the performance of the UE and / or the communication may be affected. For example, the UE may consume resources (e.g., power resources, processing resources, and / or network resources) that attempt to transmit or receive communication to or from the antennas and / or TRPs of network node 110, which are unavailable for a given communication direction during the full-duplex time interval (e.g., those associated with the given communication direction).

[0111] Various aspects generally involve communication directions that are not permitted during a full-duplex time interval. Some aspects are more specifically related to defining permitted and / or prohibited communication directions for the UE during a full-duplex time interval (e.g., for time slots and / or symbols associated with full-duplex operation). In some aspects, a network node may transmit to the UE an indication of a communication direction (and / or channel and / or reference signal) that is disabled or to be discarded (e.g., not received or transmitted) during a time slot or symbol associated with full-duplex operation at that network node. The UE may transmit or receive communication in permitted communication directions during a full-duplex time interval (e.g., communication is not in prohibited communication directions). In some aspects, the UE may suppress the transmission or reception (e.g., may discard) of communication in prohibited communication directions during a full-duplex time interval.

[0112] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to clarify how the UE will utilize the full-duplex time interval when a network node is operating in full-duplex mode (e.g., using non-co-located antennas and / or TRPs). For example, during the full-duplex time interval, the UE can transmit or receive communication in permitted communication directions and / or can discard communication in disallowed communication directions. This can save UE resources (e.g., power resources, processing resources, and / or network resources) that would otherwise be used to attempt to transmit or receive communication in disallowed communication directions (e.g., to or from antennas and / or TRPs of network nodes that are not available for disallowed communication directions during the full-duplex time interval).

[0113] In some respects, feedback operations can be defined for dropped communications associated with disallowed communication directions. For example, when the UE does not receive downlink communication (e.g., because the downlink is a disallowed communication direction), the UE can suppress the transmission of HARQ feedback for the downlink communication. For example, the UE can thus save power resources, processing resources, and / or network resources that would otherwise be used by the UE to transmit HARQ feedback for downlink communication, which the network node knows was not transmitted to the UE.

[0114] In some respects, indications of disallowed communication directions can be associated with a given CORESET pool index value. For example, a network node can transmit, and a UE can receive, indications that communication associated with a given communication direction and a given CORESET pool index value is disallowed, disabled, and / or to be discarded during a full-duplex time interval. This allows for improved control and / or flexibility in indicating disallowed (and / or permitted) communication directions in multi-TRP and / or mDCI scenarios. In some examples, a network node can transmit, and a UE can receive, indications of one or more disallowed channels and / or one or more disallowed signal types for a full-duplex time interval, rather than indicating that downlink or uplink is disabled during the full-duplex time interval. This provides the network node with additional flexibility to allow some communication (e.g., higher-priority communication) in directions that would otherwise be completely disallowed.

[0115] Figure 8 This is a diagram illustrating an example of operation 800 associated with a communication direction not permitted during a full-duplex time interval, according to this disclosure. Figure 8 As shown, one or more network nodes 110 (e.g., base stations, CUs, DUs, and / or RUs) can communicate with UE 120. In some aspects, network node 110 and UE 120 may be part of a wireless network (e.g., wireless network 100). UE 120 and network node 110 may already be... Figure 8 The operation shown is preceded by the establishment of a wireless connection. In some respects, network node 110 may be associated with two or more TRPs, antennas, and / or antenna panels. The two or more TRPs, antennas, and / or antenna panels may be non-quasi-co-located (e.g., they may be located in different physical locations and / or may be separated by a certain distance).

[0116] In the first operation 805, UE 120 can transmit and network node 110 can receive a capability report. UE 120 can transmit the capability report via UE capability signaling, UE auxiliary information (UAI) communication, uplink control information communication, RRC communication, PUSCH and / or PUCCH, etc. The capability report can indicate whether the UE supports one or more of the operations described herein. For example, the capability report can indicate whether UE 120 supports receiving indications of disallowed (and / or permitted) communication directions for full-duplex time intervals.

[0117] In some aspects, the capability report may indicate whether UE 120 supports receiving indications for one or more full-duplex time intervals, as described in more detail elsewhere herein. For example, the capability report may indicate whether UE 120 supports a time slot pattern (e.g., a time slot format pattern) that identifies full-duplex time slots and / or symbols. In some aspects, the capability report may indicate whether UE 120 supports selectively transmitting or receiving communication during a full-duplex time interval based on, in response to, or otherwise associated with an indicated disallowed communication direction. The capability report may indicate whether UE 120 supports multiple active TCI states and / or multiple active beams. For example, UE 120 may be configured to perform one or more of the operations described herein in response to, based on, or otherwise associated with a capability report indicating that UE 120 does not support multiple active TCI states and / or multiple active beams.

[0118] As used herein, “selectively” performing an operation means performing the operation or suppressing its execution. For example, selectively performing an operation based on, in response to, or otherwise associated with whether a condition is met means performing the operation if the condition is met and not performing the operation if the condition is not met (or vice versa). Thus, selectively performing an operation may include determining whether to perform the operation, and then performing or suppressing the operation based on, in response to, or otherwise associated with that determination.

[0119] As used herein, “selectively” performing a first operation or a second operation means performing either the first operation or the second operation. For example, selectively performing a first operation or a second operation based on, in response to, or otherwise associated with whether a condition is met means performing the first operation if the condition is met and performing the second operation if the condition is not met (or vice versa). Thus, selectively performing a first operation or a second operation may include determining whether to perform the first operation or the second operation, and then performing the first operation or the second operation based on, in response to, or otherwise associated with that determination.

[0120] As used herein, “full-duplex” can refer to SBFD, in-band full-duplex (e.g., frequency domain resources with partial or complete overlap), and / or another full-duplex type or mode. “Time interval” can refer to a time slot, OFDM symbol, mini-slot (e.g., one or more symbols within a time slot), and / or another time interval. For example, a “full-duplex time interval” can refer to an SBFD time slot, an SBFD symbol, an in-band full-duplex time slot, and / or an in-band full-duplex symbol, etc.

[0121] Network node 110 can configure UE 120 based on capability reports. For example, network node 110 can configure or trigger UE 120 to perform one or more operations based on, in response to, or otherwise associated with capability reports indicating that UE 120 supports one or more operations. For example, network node 110 can indicate disallowed communication directions for full-duplex time slots based on, in response to, or otherwise associated with capability reports indicating that UE 120 supports such indications and / or indicating that UE 120 supports full-duplex time slot intervals.

[0122] In the second operation 810, network node 110 can transmit and UE 120 can receive configuration information. In some aspects, UE 120 can receive configuration information via one or more of system information signaling, RRC signaling, one or more MAC-CEs and / or DCIs. In some aspects, configuration information may include: indications of one or more configuration parameters for UE 120 to select, and / or explicit configuration information for UE 120 to configure the UE.

[0123] In some aspects, the configuration information may instruct UE 120 to receive indications of disallowed communication directions for a full-duplex time interval. The full-duplex time interval may be the time interval during which network node 110 is operating in full-duplex mode, as described in more detail elsewhere herein. Disallowed communication directions may be communication directions (e.g., uplink or downlink) that UE 120 intends to discard. As used herein, "discarding" or "dropping" communication may refer to a device (e.g., UE 120) suppressing the transmission or reception of communication. In some aspects, the configuration information may instruct UE 120 to discard communication associated with a disallowed communication direction that at least partially overlaps with the full-duplex time interval in the time domain. In some aspects, the configuration information may instruct UE 120 to discard communication associated with a disallowed communication direction that is completely contained within the full-duplex time interval in the time domain.

[0124] In some aspects, configuration information can instruct network node 110 and / or UE 120 to use one or more full-duplex time intervals. For example, configuration information can instruct full-duplex operation to be enabled for network node 110. Full-duplex operation performed by network node 110 may include sub-band full-duplex operation and / or in-band full-duplex operation (e.g., associated with partially or fully overlapping frequency domain resources). For example, network node 110 may use a first TRP and / or a first antenna panel to receive uplink signals while using a second TRP and / or a second antenna panel to transmit downlink signals.

[0125] In some aspects, the configuration information may include indications of one or more full-duplex time intervals. For example, the configuration information may indicate the mode of the time intervals associated with full-duplex operation at network node 110. For example, the configuration information may indicate one or more time intervals during which network node 110 is operating in full-duplex mode. For example, the configuration information may indicate a time slot mode. For example, the configuration information may include TDD configuration. The time slot mode may indicate the duplex type or duplex mode used for the corresponding time slot. For example, the time slot mode may indicate the mode of uplink time slots, downlink time slots, and / or full-duplex time slots (e.g., subband full-duplex time slots).

[0126] In some aspects, configuration information may include indications of disallowed communication directions associated with one or more full-duplex time intervals. For example, an indication of disallowed communication directions may be associated with uplink signals and channels or downlink signals and channels being prohibited from use for one or more full-duplex time intervals. Disallowed communication directions can be uplink or downlink. For example, disallowed communication directions may be associated with downlink channels and / or signals or uplink channels and / or signals being disabled or dropped during a full-duplex time interval.

[0127] In some respects, the indication of a disallowed communication direction can be explicit. For example, the indication of a disallowed communication direction may include an indication of a communication direction (e.g., uplink or downlink) that the UE 120 should not use during a full-duplex time interval. As another example, the indication of a disallowed communication direction can be implicit. For example, the indication of a disallowed communication direction may include an indication of a communication direction that is permitted for a full-duplex time interval. Because there may only be two communication directions (e.g., uplink or downlink) associated with network node 110, the UE 120 may determine the disallowed communication directions based on, in response to, or otherwise associated with the indication of permitted communication directions. For example, if the indicated permitted communication direction is uplink, the UE 120 may determine that the disallowed communication direction for a full-duplex time interval is downlink. If the indicated permitted communication direction is downlink, the UE 120 may determine that the disallowed communication direction for a full-duplex time interval is uplink. In an example where the indication of disallowed communication directions is explicit, UE120 can determine the permitted communication directions for full-duplex time intervals in a similar manner. The indication of disallowed communication directions is described in more detail elsewhere in this document.

[0128] In some respects, configuration information can indicate one or more TCI states. For example, configuration information can indicate (e.g., via TCI state information elements) a given TCI state identifier (such as tci-StateID), QCL type (such as qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, or qcl-TypeD), cell identifier (such as ServCellIndex), bandwidth portion identifier (such as bwp-Id), and / or reference signal identifier (such as NZP-CSI-RS-ResourceId or SSB-Index), etc. One or more TCI states may include a unified TCI state (e.g., an uplink TCI state and a downlink TCI state, or a combined uplink and downlink TCI state). For example, a TCI state may indicate the directivity or characteristics of a beam, such as one or more quasi-co-location (QCL) attributes of a downlink beam. QCL attributes may include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc. For example, UE 120 may receive indications (e.g., beam indication, MAC-CE communication, and / or DCI communication) to apply a TCI state (e.g., a unified TCI state) to a given TRP of network node 110.

[0129] UE 120 can configure itself, at least in part, based on configuration information. In some respects, UE 120 can be configured to perform one or more operations described herein, at least in part, based on configuration information.

[0130] In the third operation 815, network node 110 can transmit and UE 120 can receive indications for one or more full-duplex time intervals. In some aspects, the third operation 815 can be performed as part of the second operation 810 (e.g., the indication for one or more full-duplex time intervals can be included in configuration information, as described above). In other examples, the third operation 815 and the second operation 810 can be separate operations. In some aspects, UE 120 can receive a TDD mode indicating a timeslot format pattern. The timeslot pattern can indicate one or more full-duplex timeslots. The timeslot format pattern can be repeated in time. For example, UE 120 can combine... Figure 6The description follows a similar manner, receiving indications for one or more full-duplex time intervals via a time slot format mode. The above example uses a time slot to describe a time interval, and UE 120 can receive indications for other full-duplex time intervals in a similar manner.

[0131] In some aspects, network node 110 can transmit, and UE 120 can receive, an indication to switch to a timeslot format mode that includes full-duplex timeslots. For example, network node 110 can transmit, and UE 120 can receive communications (e.g., RRC communications, MAC-CE communications, and / or DCI communications) instructing UE 120 to switch from a first timeslot format mode (e.g., which does not include full-duplex timeslots) to a second timeslot format mode (e.g., which includes full-duplex timeslots). UE 120 can identify one or more full-duplex time intervals based on, in response to, or otherwise associated with a mode (e.g., timeslot format mode). In other words, UE 120 can identify one or more time intervals during which network node 110 is operating in full-duplex mode.

[0132] In some respects, network node 110 can determine the disallowed communication directions (and / or channels or signal types) for the full-duplex time interval of UE 120. For example, network node 110 can determine the serving TRP (or TRP) associated with UE 120. The serving TRPs can be the TRPs used by UE 120 to communicate with network node 110. When network node 110 is operating in full-duplex mode, network node 110 can determine the communication direction to be used for the corresponding TRP. For example, network node 110 can associate with a first TRP and a second TRP. Network node 110 can determine that when operating in full-duplex mode, the first TRP will be used for the uplink and the second TRP will be used for the downlink. Network node 110 can determine that the serving TRP of UE 120 is the first TRP. Additionally, network node 110 may determine that UE 120 is unable to support multiple active TCI states (e.g., as indicated by the capability report transmitted by UE 120 in the first operation 805) and / or the communication parameters of the link between UE 120 and the second TRP (e.g., RSRP, signal-to-noise ratio (SNR), or another parameter) do not meet a threshold. Therefore, network node 110 may determine that UE 120 is unable to receive downlink communication from the second TRP and / or the link between UE 120 and the second TRP is unsuitable for downlink transmission. Therefore, network node 110 may determine that downlink is not permitted for UE 120 during the full-duplex time interval (e.g., and UE 120 may be able to continue transmitting uplink communication to the first TRP).

[0133] In some respects, such as in a multi-TRP scenario, network node 110 can determine communication directions that are not permitted for a given TRP. For example, network node 110 can determine to disable the downlink for a first TRP and disable the uplink for a second TRP during a full-duplex time interval. As described in more detail elsewhere herein, network node 110 can instruct the disabled communication direction for a given CORESET pool index value to disable that communication direction for the given TRP during a full-duplex time interval.

[0134] In the fourth operation 820, network node 110 can transmit, and UE 120 can receive, an indication of a disallowed communication direction associated with a full-duplex time interval. The indication of a disallowed communication direction can be included in higher-layer parameters (e.g., RRC parameters or MAC parameters) received by UE 120. In some aspects, the indication of a disallowed communication direction can be conveyed via RRC signaling, MAC-CE signaling, DCI signaling, or another type of signaling.

[0135] An indication of a disallowed communication direction may be associated with uplink signals and channels or downlink signals and channels not being permitted for one or more full-duplex time intervals. That is, a disallowed communication direction can be an uplink direction (e.g., uplink signals and channels) or a downlink direction (e.g., downlink signals and channels), and an indication of a disallowed communication direction can indicate the disallowed communication direction. As described elsewhere herein, an indication of a disallowed communication direction can be explicit or implicit. For example, an indication of a disallowed communication direction may include an indication of communication directions (e.g., uplink or downlink) that the UE 120 should not use during a full-duplex time interval. As another example, an indication of a disallowed communication direction may include an indication of permitted communication directions for a full-duplex time interval.

[0136] In some aspects, a disallowed communication direction can apply to all channels and / or signal types associated with the disallowed communication direction. For example, UE 120 can drop all communications and / or signals in the disallowed communication direction during a full-duplex time interval. In other aspects, a disallowed communication direction can apply to certain channels and / or signal types. For example, one or more channels and / or signal types associated with a communication direction can be disabled or dropped during a full-duplex time interval. In some aspects, network node 110 can transmit, and UE 120 can receive, indications of one or more channels and / or signal types associated with the disallowed communication direction.

[0137] In some respects, the indication of disallowed communication directions can be an indication of one or more channels and / or one or more signal types that are not permitted for full-duplex time intervals. For example, network node 110 can transmit, and UE 120 can receive, an indication of one or more disallowed channels and / or one or more disallowed signal types for full-duplex time intervals, rather than an indication that downlink or uplink is disabled for full-duplex time intervals. This can provide network node 110 with additional flexibility to allow some communication (e.g., higher priority communication) in communication directions that would otherwise be completely disallowed. For example, UE 120 can transmit higher priority communication (e.g., in communication directions that would otherwise be disallowed), and network node 110 (e.g., TRP of network node 110) can perform interference mitigation to receive higher priority communication.

[0138] In some respects, network node 110 can transmit, and UE 120 can receive, indications that one or more channels and / or signal types in a disallowed communication direction should be disabled or discarded by UE 120 during a full-duplex time interval. For example, one or more channels may include PUSCH or PUCCH (e.g., if the disallowed communication direction is uplink). As another example, one or more channels may include PDSCH or PDCCH (e.g., if the disallowed communication direction is downlink).

[0139] One or more signal types may include semi-persistent and / or periodic signals. For example, one or more signal types may include a semi-persistent scheduling (SPS) signal, a configured grant (CG) signal, a semi-persistent and / or periodic probe reference signal (SRS), semi-persistent and / or periodic channel state information (CSI) communicated via PUCCH, and / or a semi-persistent and / or periodic CSI reference signal (CSI-RS), etc. Additionally or alternatively, one or more signal types may include repetition. For example, repetition of PDSCH, PDCCH, PUCCH, and / or PUSCH communications in disallowed communication directions may be disabled or dropped during the full-duplex time interval. For example, semi-persistent and / or periodic signals or repetitions may be dropped because the communication may be retransmitted to UE 120 at a later time and / or may have already been transmitted to UE 120. Therefore, these signal types may be more tolerant of being dropped at a given time because the same communication may be transmitted to UE 120 at another time. Additionally or alternatively, one or more signal types may include signals associated with communications scheduled by a single DCI that schedules multiple communications. For example, one or more signal types may include signals associated with a PDSCH or PUSCH signal scheduled by a DCI that schedules multiple PDSCH or PUSCH signals. The described channels and signal types are provided as examples. Other channels and / or signal types may be disabled in disallowed communication directions in a manner similar to that described herein.

[0140] In some aspects, indications of disallowed communication directions may include indications of CORESET pool index values ​​associated with the indications of disallowed communication directions. For example, channels and / or signals associated with a given CORESET pool index value may be disabled or dropped in the disallowed communication direction during the full-duplex time interval. For example, indications of disallowed communication directions may include indications that downlink channels and / or signals associated with CORESET pool index 0 are disabled or disallowed, uplink channels and / or signals associated with CORESET pool index 0 are disabled or disallowed, downlink channels and / or signals associated with CORESET pool index 1 are disabled or disallowed, and / or uplink channels and / or signals associated with CORESET pool index 1 are disabled or disallowed, and so on. For example, if two TRPs of network node 110 are used for full-duplex operation, uplink transmissions to one TRP and downlink transmissions from the other TRP may be impossible or disallowed during the full-duplex time interval. Therefore, multi-DCI multi-TRP operation may be impossible during the full-duplex time interval. Network node 110 can indicate the communication directions that are not allowed per CORESET pool index value to indicate which TRP should be associated with which communication direction.

[0141] For example, UE 120 may communicate via multiple TRPs (e.g., TRP 1 and TRP 2) during non-full-duplex time intervals (e.g., using multiple TCI states corresponding to the respective TRPs). TRP 1 may be associated with a first CORESET pool index value and TRP 2 may be associated with a second CORESET pool index value. In some aspects, network node 110 may transmit, and UE 120 may receive, indications of a first disallowed communication direction for communication associated with the first CORESET pool index value and indications of a second disallowed communication direction for communication associated with the second CORESET pool index value. For example, when operating in full-duplex mode, network node 110 may use TRP 1 for uplink operation and TRP 2 for downlink operation. Therefore, the indication of the disallowed communication direction may indicate that downlink is not permitted for the first CORESET pool index value (e.g., for TRP 1) and / or uplink is not permitted for the second CORESET pool index value (e.g., for TRP 2). This provides additional flexibility for network node 110 to indicate which TRPs are associated with which communication directions during the full-duplex time interval in scenarios where network node 110 is communicating using multiple TRP operations.

[0142] In some aspects, the indication of disallowed communication directions may include an indication of a TCI state associated with a full-duplex operating state and a disallowed communication direction, wherein the TCI state indicates that the disallowed communication direction is not permitted for one or more full-duplex time intervals. For example, UE 120 may support TCI states associated with different duplex states of network node 110. For example, the TCI state may include an indication of an associated duplex type or duplex mode. UE 120 may apply the TCI state during the time interval associated with the duplex type or duplex mode associated with the TCI state. For example, UE 120 may apply a full-duplex TCI state during a full-duplex time interval and may apply a non-full-duplex TCI state during a non-full-duplex time interval. This can reduce the signaling overhead associated with switching the TCI state used by UE 120 when the network node changes the duplex state or duplex type. In some examples, the amount of time associated with UE 120 switching to a TCI state associated with a given duplex state or duplex type can be reduced because the processing time associated with receiving beam indication (e.g., receiving an indication of the TCI state) can be reduced or eliminated. Configuring the TCI state to be associated with a given duplex state or duplex type (e.g., full-duplex or half-duplex) can reduce self-interference at network node 110 by enabling network nodes to use spatially isolated antennas and / or TRPs for the corresponding communication direction, while also reducing the signaling overhead associated with the network node instructing UE 120 to use a spatially isolated TCI state.

[0143] In some aspects, network node 110 can transmit and UE 120 can receive communication that activates a TCI state associated with full-duplex (e.g., MAC-CE communication and / or DCI communication). The TCI state can be associated with a communication direction (e.g., uplink or downlink). The TCI state can include an indication that the communication direction is not permitted for one or more full-duplex time intervals. For example, the TCI state can include an "empty" indication or a "disabled" indication. In other words, the TCI state can include a flag or other indication indicating that the TCI state will not be used for communication (e.g., thus indicating that the communication direction associated with the TCI state is disabled or not permitted for full-duplex time intervals). For example, network node 110 can transmit and UE 120 can receive an indication of a first unified TCI state associated with a non-full-duplex time interval (e.g., downlink TCI state 1 and uplink TCI state 1). Network node 110 can transmit and UE 120 can receive an indication of a second unified TCI state associated with a full-duplex time interval. The second unified TCI state can include an "empty" TCI state for a given communication direction, thereby indicating that the communication direction is disabled for a full-duplex time interval. For example, the second unified TCI state can include a downlink TCI state 1 and an "empty" uplink TCI state, thereby indicating that the uplink is not allowed or disabled for a full-duplex time interval.

[0144] In some respects, the TCI state associated with full-duplex can be associated with a given CORESET pool index value. For example, network node 110 can transmit, and UE 120 can receive, an indication of an “empty” TCI state (e.g., associated with a full-duplex time interval) associated with a given communication direction and a given CORESET pool index value. For example, for a first CORESET pool index value, beamforming can indicate that a first unified TCI state (e.g., downlink TCI state 1 and uplink TCI state 1) is to be used for a non-full-duplex time interval and a second unified TCI state (e.g., downlink TCI state 1 and an “empty” uplink TCI state) is to be used for a full-duplex time interval. For a second CORESET pool index value, beamforming can indicate that a third unified TCI state (e.g., downlink TCI state 2 and uplink TCI state 2) is to be used for a non-full-duplex time interval and a fourth unified TCI state (e.g., an “empty” downlink TCI state and uplink TCI state 2) is to be used for a full-duplex time interval. This can indicate that during the full-duplex time interval, the uplink is disabled or not allowed for the first TRP associated with the first CORESET pool index value, and the downlink is disabled or not allowed for the second TRP associated with the second CORESET pool index value.

[0145] In the fifth operation 825, UE 120 may determine that the current time interval is a full-duplex time interval. For example, based on, in response to, or otherwise associated with an indication of one or more full-duplex time intervals (e.g., an indication received by UE 120 as part of the second operation 810 and / or the third operation 815), UE 120 may determine that the current time interval is associated with full-duplex. For example, UE 120 may determine that the current time interval is a full-duplex timeslot, a sub-band full-duplex timeslot, or another full-duplex time interval.

[0146] In the sixth operation 830, UE 120 and network node 110 may communicate via permitted communication directions during the current time interval (e.g., during a full-duplex time interval). UE 120 may determine permitted communication directions based on, in response to, or otherwise associated with an indication of disallowed communication directions (e.g., an indication received by UE 120 as part of the second operation 810 and / or the fourth operation 820). For example, an indication of disallowed communication directions may include an explicit indication of permitted communication directions. In some other aspects, UE 120 may determine permitted communication directions based on, in response to, or otherwise associated with disallowed communication directions (e.g., if the disallowed communication direction is a downlink, UE 120 may determine that the permitted communication direction is an uplink, and vice versa). UE 120 can transmit or receive communication during the current time interval (e.g., during a full-duplex time interval) depending on whether the communication is in a communication direction that is not a permitted communication direction (e.g., based on, in response to, or otherwise associated with the communication being in a permitted communication direction).

[0147] In some respects, UE 120 can determine whether a channel and / or signal type associated with a communication is permitted for a full-duplex time interval. For example, an indication of a disallowed communication direction can indicate one or more channels and / or one or more signal types that are disallowed or disabled for a full-duplex time interval. UE 120 can transmit or receive communication during the current time interval (e.g., during the full-duplex time interval) based on whether the communication is associated with a channel and / or signal type that is not disallowed or disabled for a full-duplex time interval.

[0148] In the seventh operation 835, UE 120 may discard communication during the current time interval (e.g., during the full-duplex time interval) based on whether the communication is in an unallowed communication direction. For example, UE 120 may identify communication scheduled or configured to occur during the full-duplex time interval. UE 120 may suppress transmission (e.g., if the unallowed communication direction is uplink) or suppress reception (e.g., if the unallowed communication direction is downlink) based on, in response to, or otherwise associated with the communication being in an unallowed communication direction. Additionally or alternatively, UE 120 may discard communication during the current time interval (e.g., during the full-duplex time interval) based on whether the communication is associated with an unallowed channel and / or an unallowed signal type. Similarly, network node 110 may discard communication during the current time interval (e.g., during the full-duplex time interval) based on whether the communication is in an unallowed communication direction. For example, network node 110 may identify communication scheduled or configured to occur during the full-duplex time interval. Network node 110 may suppress transmission (e.g., if the disallowed communication direction is downlink) or suppression of reception (e.g., if the disallowed communication direction is uplink) based on, in response to, or otherwise associated with communication in a disallowed communication direction.

[0149] In some aspects, feedback operations are used for communications (e.g., downlink communications or PDSCH communications) that are dropped by UE 120 based on communication directions not permitted for full-duplex time intervals. Feedback operations can be instructed and / or configured as part of a second operation 810. For example, UE 120 may support Hybrid Automatic Repeat Request (HARQ) feedback codebook transmission. HARQ feedback codebook transmission may include feedback messages that UE 120 wants to transmit to network node 110 to provide feedback regarding, for example, downlink data transmissions (e.g., transmissions associated with PDSCH).

[0150] The UE can be configured to have different types of codebooks, such as a Type 1 HARQ ACK codebook or a Type 2 HARQ ACK codebook. A Type 1 HARQ ACK codebook can be referred to as a semi-static HARQ ACK codebook. For example, a Type 1 HARQ ACK codebook can be associated with a fixed or static size (e.g., configured by network node 110). A Type 2 HARQ ACK codebook can be associated with a dynamic size (e.g., where the size of the Type 2 HARQ ACK codebook is at least partially based on or otherwise associated with a schedule received by UE 120). Typically, if UE 120 is configured to transmit a Type 1 HARQ ACK codebook, UE 120 can collect feedback for PDSCH communications that UE 120 attempts to receive during a feedback window (e.g., k time slots) and can transmit a Type 1 HARQ ACK codebook indicating feedback (e.g., ACK / NACK feedback) associated with the PDSCH communications that UE 120 attempts to receive during the feedback window.

[0151] In some respects, UE 120 may suppress the transmission of HARQ feedback indications associated with downlink communication that is dropped due to an unauthorized communication direction (e.g., dropped as part of operation 835 7). For example, UE 120 may not report HARQ-ACKs for downlink communication (e.g., for PDSCH). In an example where UE 120 is configured to transmit a Type 1 HARQ ACK codebook, UE 120 may exclude candidate PDSCH timings from the Type 1 HARQ ACK codebook associated with full-duplex time intervals. For example, UE 120 may transmit, and network node 110 may receive, a Type 1 HARQ codebook associated with a set of downlink timings (e.g., a set of candidate PDSCH timings) that includes downlink timings corresponding to downlink communication. The Type 1 HARQ codebook may not include indications for downlink timings corresponding to dropped downlink communication. For example, candidate PDSCH opportunities from a Time Domain Resource Assignment (TDRA) line that overlaps with time domain resources in a full-duplex time interval can be excluded from the Type 1 HARQ codebook (e.g., not included in it). In an example where the disallowed communication direction is also associated with a CORESET pool index value, UE 120 can exclude candidate PDSCH opportunities associated with the CORESET pool index value from the TDRA line that overlaps with time domain resources in the Type 1 HARQ codebook used for the CORESET pool index value. This can reduce the size of the Type 1 HARQ codebook, thereby saving network resources associated with transmitting the Type 1 HARQ codebook. Network node 110 can determine that downlink communication was not successfully received by UE 120 based on, in response to, or otherwise associated with downlink communication being scheduled or configured to occur during a full-duplex time interval, and based on, in response to, or otherwise associated with a communication direction disallowed for UE 120.

[0152] In other respects, UE 120 can transmit, and network node 110 can receive, a HARQ feedback indication for downlink communication that has been dropped due to an unauthorized communication direction (e.g., dropped as part of operation 835 7). For example, UE 120 can transmit a negative ACK (NACK) indication for the downlink communication (e.g., in a type 1 HARQ codebook or another type of feedback communication). This can indicate to network node 110 that UE 120 has not successfully received the downlink communication. Therefore, network node 110 can schedule another transmission of the downlink communication to ensure that UE 120 receives the downlink communication, thereby improving the reliability of downlink communication dropped due to an unauthorized communication direction.

[0153] Figure 9This is a diagram illustrating an example of communication directions not permitted during full-duplex time intervals, based on this disclosure. For example... Figure 9 As shown, UE 1 (e.g., UE 120) and UE 2 (e.g., UE 120) may be configured to have, or receive, indications of time intervals (e.g., time slots or symbols) associated with different duplex types. For example, some time intervals may be non-full-duplex time intervals (e.g., downlink time intervals or uplink time intervals). Other time intervals may be full-duplex time intervals (e.g., subband full-duplex time intervals). UE 1 and / or UE 2 may receive indications of different types of time intervals in a manner similar to that described in more detail elsewhere herein (such as in conjunction with second operation 810 and / or third operation 815).

[0154] As an example, network node 110 may be associated with multiple TRPs (such as TRP 1 and TRP 2). As described elsewhere in this document, when operating in full-duplex mode, network node 110 may use TRP 1 for downlink operations and TRP 2 for uplink operations. Figure 9 As shown, UE 1 can communicate with network node 110 via TRP 1. For example, UE 1 can transmit both uplink signals (e.g., during the uplink time interval) and downlink signals (e.g., during the downlink time interval) via TRP 1. Similarly, UE 2 can communicate with network node 110 via TRP 2. For example, UE 2 can transmit both uplink signals (e.g., during the uplink time interval) and downlink signals (e.g., during the downlink time interval) via TRP 2. In other words, TRP 1 can be a serving TRP for UE 1, and TRP 2 can be a serving TRP for UE 2. For example, UE 1 can use TCI states (e.g., downlink TCI state, uplink TCI state, and / or combined uplink and downlink TCI states) associated with the spatial direction toward TRP 1 to transmit and / or receive signals. Similarly, UE 2 can use TCI states (e.g., downlink TCI state, uplink TCI state, and / or combined uplink and downlink TCI state) associated with the spatial direction toward TRP 2 to transmit and / or receive signals.

[0155] In the first operation 905, the uplink can be disabled for UE 1 and the downlink can be disabled for UE 2 for the full-duplex time interval. For example, UE 1 can receive an indication of communication directions that are not permitted for the full-duplex time interval (e.g., in a manner similar to that described elsewhere herein). For example, because TRP 1 is the serving TRP for UE 1 when operating in full-duplex mode and because network node 110 uses TRP 1 for downlink operation (e.g., downlink only), network node 110 can transmit and UE 1 can receive an indication that the uplink channel and / or signaling is disabled or not permitted for the full-duplex time interval.

[0156] Additionally, UE 2 may receive indications regarding downlink communication directions that are not permitted for the full-duplex time interval (e.g., in a manner similar to that described elsewhere herein). For example, since TRP 2 is the serving TRP of UE 2 when operating in full-duplex mode and since network node 110 uses TRP 2 for uplink operation (e.g., uplink-only operation), network node 110 may transmit, and UE 2 may receive, indications regarding downlink channels and / or signals being disabled or not permitted for the full-duplex time interval.

[0157] For example, such as Figure 9 As shown, UE 1 can receive downlink communication and discard uplink communication during the full-duplex time interval. UE 2 can transmit uplink communication and discard downlink communication during the full-duplex time interval. This ensures that when network node 110 uses TRP 1 only for downlink operation, UE 1 does not consume resources (e.g., processing resources, battery resources, and / or network resources) associated with transmitting uplink communication to TRP 1. Similarly, this ensures that when network node 110 uses TRP 2 only for uplink operation, UE 2 does not consume resources (e.g., processing resources, battery resources, and / or network resources) associated with attempting to receive downlink communication from TRP 2 (e.g., monitoring downlink communication).

[0158] Figure 10 This is a diagram illustrating an example of communication directions not permitted during full-duplex time intervals, based on this disclosure. For example... Figure 10As shown, UE 1 (e.g., UE 120) can be configured to have, or can receive, indications of time intervals (e.g., time slots or symbols) associated with different duplex types. For example, some time intervals may be non-full-duplex time intervals (e.g., downlink time intervals or uplink time intervals). Other time intervals may be full-duplex time intervals (e.g., subband full-duplex time intervals). UE 1 may receive indications of different types of time intervals in a manner similar to that described in more detail elsewhere herein (such as in conjunction with second operation 810 and / or third operation 815).

[0159] As an example, network node 110 may be associated with multiple TRPs (such as TRP 1 and TRP 2). As described elsewhere in this document, when operating in full-duplex mode, network node 110 may use TRP 1 for downlink operations and TRP 2 for uplink operations. Figure 10 As shown, UE 1 can communicate using multiple TRP operations. For example, UE 1 can receive downlink communication from both TRP 1 and TRP 2 during a downlink time interval. UE 1 can transmit uplink communication to both TRP 1 and TRP 2 during an uplink time interval.

[0160] In the first operation 1005, for a full-duplex time interval, the uplink can be disabled for the CORESET pool index and / or TCI state associated with TRP 1, and the downlink can be disabled for the CORESET pool index and / or TCI state associated with TRP 2. For example, UE 1 can receive an indication that the uplink is disabled for a first CORESET pool index value and / or for a first TCI state (e.g., associated with TRP 1) for a full-duplex time interval (e.g., in a manner similar to that described elsewhere herein). For example, because network node 110 uses TRP 1 for downlink operation (e.g., downlink-only operation) when operating in full-duplex mode, network node 110 can transmit, and UE 1 can receive, an indication that the uplink channel and / or signal for TRP 1 is disabled or not permitted for use in the full-duplex time interval (e.g., by indicating the first CORESET pool index value and / or by indicating an uplink “empty” TCI state associated with TRP 1).

[0161] Similarly, UE 1 may receive indications regarding the disabling of downlink for a second CORESET pool index value and / or for a second TCI state (e.g., associated with TRP 2) for a full-duplex time interval (e.g., in a manner similar to that described elsewhere herein). For example, because network node 110 uses TRP 2 for uplink operation (e.g., uplink-only operation) when operating in full-duplex mode, network node 110 may transmit, and UE 1 may receive, indications regarding the disabling or prohibition of downlink channels and / or signals for TRP 2 for a full-duplex time interval (e.g., by indicating the second CORESET pool index value and / or by indicating a downlink “empty” TCI state associated with TRP 2).

[0162] Figure 11 This is a flowchart illustrating an example procedure 1100 performed by a UE according to this disclosure, supporting communication directions not permitted for full-duplex time intervals. Example procedure 1100 is an example in which a UE (e.g., UE 120) performs operations associated with communication directions not permitted for full-duplex time intervals.

[0163] like Figure 11 As shown, in some aspects, process 1100 may include receiving an indication of one or more full-duplex time intervals from a network node (box 1110). For example, a UE (such as by using...) Figure 13 The communication manager 140 or receiving component 1302 depicted herein can receive indications for one or more full-duplex time intervals from the network node, as described above.

[0164] As in Figure 11 As further illustrated herein, in some aspects, process 1100 may include receiving from a network node an indication of a disallowed communication direction associated with one or more full-duplex time intervals (box 1120). For example, a UE (such as by using...) Figure 13 The communication manager 140 or receiving component 1302 depicted herein can receive from the network node an indication of a disallowed communication direction associated with one or more full-duplex time intervals, as described above.

[0165] As in Figure 11 As further illustrated, in some aspects, process 1100 may include transmitting or receiving communication to or from a network node during one of one or more full-duplex time intervals, depending on whether the communication is in a communication direction that is not a permitted communication direction (box 1130). For example, a UE (such as by using...) Figure 13The communication manager 140 or transmission component 1304 or receiving component 1302 described herein can, during one or more full-duplex time intervals, transmit or receive communication to or from a network node in a communication direction that is not a permitted communication direction, as described above.

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

[0167] In the first additional aspect, the indication of a disallowed communication direction may be associated with the disallowance of uplink signals and channels or downlink signals and channels for one or more full-duplex time intervals.

[0168] In a second additional aspect, either alone or in combination with the first aspect, process 1100 may include discarding another communication in the full-duplex time interval or in another full-duplex time interval within the one or more full-duplex time intervals, based on the fact that the other communication is in an unallowed communication direction. That is, if the UE determines, based on an indication of an unallowed communication direction, that other communication may be discarded.

[0169] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the other communication may be a downlink communication, and process 1100 may include suppressing the transmission of a Hybrid Automatic Repeat Request (HARQ) feedback indication associated with the downlink communication.

[0170] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, suppressing the transmission of HARQ feedback indication associated with the downlink communication may include transmitting a Type 1 HARQ codebook associated with a set of downlink timings that includes the downlink timings corresponding to the downlink communication, the Type 1 HARQ codebook not including an indication for the downlink timing.

[0171] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, disallowed communication directions may be disallowed for CORESET pool index values, downlink timing may be associated with such CORESET pool index values, and type 1 HARQ codebooks may be associated with such CORESET pool index values.

[0172] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, another communication may be a downlink communication, and process 1100 may include transmitting a NACK indication for the downlink communication.

[0173] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, an indication of a disallowed communication direction may be conveyed via radio resource control signaling or MAC control element signaling.

[0174] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, the indication of a disallowed communication direction may include an indication that, during one or more full-duplex time intervals, the disallowed communication direction is not permitted for communication associated with the CORESET pool index value.

[0175] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, the indication of a disallowed communication direction may include an indication of a first disallowed communication direction for communication associated with a first CORESET pool index value and an indication of a second disallowed communication direction for communication associated with a second CORESET pool index value.

[0176] In the tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the indication of a disallowed communication direction may include an indication of a TCI state associated with a full-duplex operation state and a disallowed communication direction, the TCI state indicating that the disallowed communication direction is not permitted for one or more full-duplex time intervals.

[0177] In the eleventh additional aspect, either alone or in combination with one or more of the first to tenth aspects, the indication of the TCI status may include the TCI status being associated with a CORESET pool index value, the TCI status indicating that communication associated with the CORESET pool index value and a disallowed communication direction is not permitted for one or more full-duplex time intervals.

[0178] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, one or more full-duplex time intervals may be one or more sub-band full-duplex time intervals.

[0179] In the thirteenth additional aspect, alone or in combination with one or more of the first to twelfth aspects, one or more full-duplex time intervals may include one or more full-duplex time slots, or at least one of one or more full-duplex OFDM symbols.

[0180] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 1100 can be executed in parallel.

[0181] Figure 12 This is a flowchart illustrating an example process 1200 performed by a network node, according to this disclosure, to support communication directions not permitted for full-duplex time intervals. Example process 1200 is an example in which a network node (e.g., network node 110) performs operations associated with communication directions not permitted for full-duplex time intervals.

[0182] As in Figure 12 As shown, in some aspects, process 1200 may include transmitting an indication associated with the UE for one or more full-duplex time intervals (box 1210). For example, a network node (such as by using...) Figure 14 The communication manager 150 or transmission component 1404 depicted herein can transmit indications associated with the UE for one or more full-duplex time intervals, as described above.

[0183] As in Figure 12 As further illustrated, in some aspects, process 1200 may include transmitting an indication associated with the UE of a disallowed communication direction associated with one or more full-duplex time intervals (box 1220). For example, a network node (such as by using...) Figure 14 The communication manager 150 or transmission component 1404 depicted herein can transmit an indication associated with the UE of a disallowed communication direction associated with one or more full-duplex time intervals, as described above.

[0184] As in Figure 12 As further illustrated, in some aspects, process 1200 may include transmitting or receiving communication (box 1230) during one of one or more full-duplex time intervals, depending on whether the communication for the UE is in a communication direction that is not a permitted communication direction. For example, network nodes (such as those using...) Figure 14 The communication manager 150, transmission component 1404, or receiving component 1402 described herein may transmit or receive communication in a communication direction that is not a permitted communication direction during one of one or more full-duplex time intervals, as described above.

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

[0186] In the first additional aspect, the indication of a disallowed communication direction may be associated with the disallowance of uplink signals and channels or downlink signals and channels for one or more full-duplex time intervals.

[0187] In a second additional aspect, either alone or in combination with the first aspect, process 1200 may include discarding another communication in the full-duplex time interval or in another full-duplex time interval within the one or more full-duplex time intervals, based on the fact that the other communication is in an unallowed communication direction. That is, if the network node determines, based on an indication of an unallowed communication direction, that other communication may be discarded.

[0188] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the other communication may be a downlink communication, and process 1100 may include receiving a Type 1HARQ codebook associated with a set of downlink timings that includes downlink timings corresponding to the downlink communication, the Type 1HARQ codebook not including an indication for the downlink timing.

[0189] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, disallowed communication directions may be disallowed for CORESET pool index values, downlink timing may be associated with such CORESET pool index values, and type 1 HARQ codebooks may be associated with such CORESET pool index values.

[0190] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, another communication may be a downlink communication, and process 1200 may include receiving a NACK indication for the downlink communication.

[0191] In the sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, an indication of a disallowed communication direction may be conveyed via radio resource control signaling or MAC control element signaling.

[0192] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, the indication of a disallowed communication direction may include an indication that, during one or more full-duplex time intervals, the disallowed communication direction is not permitted for communication associated with the CORESET pool index value.

[0193] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, the indication of a disallowed communication direction may include an indication of a first disallowed communication direction for communication associated with a first CORESET pool index value and an indication of a second disallowed communication direction for communication associated with a second CORESET pool index value.

[0194] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, the indication of a disallowed communication direction may include an indication of a TCI state associated with a full-duplex operation state and a disallowed communication direction, the TCI state indicating that the disallowed communication direction is not permitted for one or more full-duplex time intervals.

[0195] In the tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the indication of the TCI status may include the TCI status being associated with a CORESET pool index value, the TCI status indicating that communication associated with the CORESET pool index value and a disallowed communication direction is not permitted for one or more full-duplex time intervals.

[0196] In the eleventh additional aspect, alone or in combination with one or more of the first to tenth aspects, one or more full-duplex time intervals may be one or more sub-band full-duplex time intervals.

[0197] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, one or more full-duplex time intervals may include one or more full-duplex time slots, or at least one of one or more full-duplex OFDM symbols.

[0198] although Figure 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... Figure 12 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 1200 can be executed in parallel.

[0199] Figure 13 This is a diagram of an example apparatus 1300 for supporting wireless communication in directions not permitted for full-duplex time intervals, according to the present disclosure. Apparatus 1300 may be a UE, or a UE may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302, a transmitting component 1304, and a communication manager 140, which can communicate with each other (e.g., via one or more buses). As shown, apparatus 1300 can use the receiving component 1302 and the transmitting component 1304 to communicate with another apparatus 1306 (such as a UE, a network node, or another wireless communication device).

[0200] In some respects, device 1300 may be configured and / or operable to perform the functions described herein. Figure 8-10 One or more operations described herein. Additionally or alternatively, device 1300 may be configured and / or operable to perform one or more processes described herein (such as...). Figure 11(process 1100). In some aspects, device 1300 may include the above combination. Figure 2 One or more components of the UE as described.

[0201] Receiver 1302 may receive communications (such as reference signals, control information, and / or data communications) from device 1306. Receiver 1302 may provide the received communications to one or more other components of device 1300 (such as communication manager 140). In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1302 may include a combination of the above. Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, and / or memory.

[0202] The transmission component 1304 can transmit communications (such as reference signals, control information, and / or data communications) to the device 1306. In some aspects, the communication manager 140 can generate communications and transmit the generated communications to the transmission component 1304 for transmission to the device 1306. In some aspects, the transmission component 1304 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and transmit the processed signals to the device 1306. In some aspects, the transmission component 1304 can include a combination of the above. Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, and / or memory. In some aspects, the transmit component 1304 may be co-located with the receive component 1302 in a transceiver.

[0203] Communication manager 140 may receive, or may cause receiving component 1302 to receive from network node, an indication of one or more full-duplex time intervals. Communication manager 140 may receive, or may cause receiving component 1302 to receive from network node, an indication of a disallowed communication direction associated with one or more full-duplex time intervals. Communication manager 140 may transmit communication to network node or cause transmission component 1304 to transmit communication to network node during one of the one or more full-duplex time intervals, depending on whether the communication is in a non-disallowed communication direction; or communication manager 140 may receive communication from network node or cause receiving component 1302 to receive communication from network node during one of the one or more full-duplex time intervals, depending on whether the communication is in a non-disallowed communication direction. In some aspects, communication manager 140 may perform one or more operations performed by one or more components of communication manager 140 as described elsewhere herein.

[0204] Communication manager 140 may include the above combination Figure 2 The described UE includes a controller / processor and memory. In some aspects, the communication manager 140 includes a set of components, such as a discard component 1308 and / or a determination component 1310, etc. Alternatively, this set of components may be separate from and distinct from the communication manager 140. In some aspects, one or more components in the set may include combinations of the above. Figure 2 The described UE may be implemented in a controller / processor, memory, or elsewhere. Additionally or alternatively, one or more components of this set of components may be implemented, at least in part, as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transient computer-readable medium and may be executed by a controller or processor to perform the function or operation of that component.

[0205] The receiving component 1302 can receive from the network node an indication of one or more full-duplex time intervals. The receiving component 1302 can also receive from the network node an indication of a disallowed communication direction associated with one or more full-duplex time intervals. The transmitting component 1304 can, during one of the one or more full-duplex time intervals, transmit or receive communication from the network node depending on whether the communication is in a non-disallowed communication direction.

[0206] The discard component 1308 may discard another communication in the full-duplex time interval or in another full-duplex time interval of the one or more full-duplex time intervals, depending on whether the other communication is in an unallowed communication direction.

[0207] The determining component 1310 can determine the duplex type associated with a time interval based on, in response to, or otherwise associated with an indication of one or more full-duplex time intervals.

[0208] Figure 13 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 13 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 13 The two or more components shown can be implemented within a single component, or Figure 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The set of components shown (e.g., one or more components) can perform actions described as being performed by Figure 13 The other set of components shown performs one or more functions.

[0209] Figure 14 This is a diagram of an example apparatus 1400 for supporting wireless communication in directions not permitted during full-duplex time intervals, 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, a transmitting component 1404, and a communication manager 150, which can communicate with each other (e.g., via one or more buses). As shown, apparatus 1400 can use the receiving component 1402 and the transmitting component 1404 to communicate with another apparatus 1406 (such as a UE, a network node, or another wireless communication device).

[0210] In some respects, device 1400 may be configured and / or operable to perform the functions described herein. Figure 8-10 One or more operations described herein. Additionally or alternatively, device 1400 may be configured and / or operable to perform one or more processes described herein (such as...). Figure 12 (process 1200). In some aspects, device 1400 may include the above combination. Figure 2 One or more components of the described wireless node.

[0211] Receiver 1402 may receive communications (such as reference signals, control information, and / or data communications) from device 1406. Receiver 1402 may provide the received communications to one or more other components of device 1400 (such as communication manager 150). In some aspects, receiver 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1402 may include a combination of the above. Figure 2 The described network node includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, and / or memory.

[0212] The transmission component 1404 can transmit communications (such as reference signals, control information, and / or data communications) to the device 1406. In some aspects, the communication manager 150 can generate communications and transmit the generated communications to the transmission component 1404 for transmission to the device 1406. In some aspects, the transmission component 1404 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and transmit the processed signals to the device 1406. In some aspects, the transmission component 1404 can include a combination of the above. Figure 2 The described network node includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, and / or memory. In some aspects, the transmit component 1404 may be co-located with the receive component 1402 in a transceiver.

[0213] The communication manager 150 may transmit or cause the transmission component 1404 to transmit an indication associated with the UE of one or more full-duplex time intervals. The communication manager 150 may transmit or cause the transmission component 1404 to transmit an indication associated with the UE of a disallowed communication direction associated with one or more full-duplex time intervals. The communication manager 150 may transmit or cause the transmission component 1404 to transmit the communication during one of the one or more full-duplex time intervals, depending on whether the communication for the UE is in a non-disallowed communication direction; or the communication manager 150 may receive or cause the receiving component 1402 to receive the communication during one of the one or more full-duplex time intervals, depending on whether the communication for the UE is in a non-disallowed communication direction. In some aspects, the communication manager 150 may perform one or more operations performed by one or more components of the communication manager 150 as described elsewhere herein.

[0214] Communication manager 150 may include the above combination Figure 2 The described network node includes a controller / processor, memory, scheduler, and / or communication unit. In some aspects, the communication manager 150 includes a set of components, such as a drop component 1408 and / or a communication direction determination component 1410. Alternatively, this set of components may be separate from and distinct from the communication manager 150. In some aspects, one or more components in the set may include combinations of the above. Figure 2 The controller / processor, memory, scheduler, and / or communication unit of the described wireless node may be implemented therein. Additionally or alternatively, one or more components of this set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of that component.

[0215] Transmission component 1404 can transmit an indication associated with the UE of one or more full-duplex time intervals. Transmission component 1404 can also transmit an indication associated with the UE of a disallowed communication direction associated with one or more full-duplex time intervals. Transmission component 1404 can transmit or receive communication during one of the one or more full-duplex time intervals, depending on whether the communication to the UE is in a communication direction that is not a disallowed communication direction.

[0216] The discard component 1408 may discard another communication if the other communication is in an unauthorized communication direction during the full-duplex time interval or another full-duplex time interval of the one or more full-duplex time intervals.

[0217] The communication direction determination component 1410 can determine communication directions that are not permitted for the UE. The communication direction determination component 1410 can determine communication directions that are not permitted for the UE based on, in response to, or otherwise associated with the antenna configuration of the UE's serving TRP or network node.

[0218] Figure 14 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 14 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The set of components shown (e.g., one or more components) can perform actions described as being performed by Figure 14The other set of components shown performs one or more functions.

[0219] The following provides an overview of some aspects of this disclosure:

[0220] Aspect 1: A wireless communication method performed by a user equipment (UE) comprising: receiving from a network node an indication of one or more full-duplex time intervals; receiving from the network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals; and during one of the one or more full-duplex time intervals, transmitting or receiving the communication to or from the network node according to whether the communication is in a communication direction that is not a disallowed communication direction.

[0221] Aspect 2: The method of aspect 1, wherein the indication of the disallowed communication direction is associated with the disallowance of uplink signals and channels or downlink signals and channels for one or more full-duplex time intervals.

[0222] Aspect 3: The method of any of Aspects 1-2 further includes: during the full-duplex time interval or another full-duplex time interval in the one or more full-duplex time intervals, dropping the other communication if the other communication is in the disallowed communication direction.

[0223] Aspect 4: The method of aspect 3, wherein the other communication is a downlink communication, the method further includes: suppressing the transmission of Hybrid Automatic Repeat Request (HARQ) feedback indications associated with the downlink communication.

[0224] Aspect 5: The method of aspect 4, wherein suppressing the transmission of the HARQ feedback indication associated with the downlink communication includes: transmitting a Type 1 HARQ codebook associated with a set of downlink timings including the downlink timings corresponding to the downlink communication, the Type 1 HARQ codebook not including an indication for the downlink timing.

[0225] Aspect 6: The method of aspect 5, wherein the disallowed communication direction is not permitted for use with the control resource set (CORESET) pool index value, wherein the downlink timing is associated with the CORESET pool index value, and wherein the type 1HARQ codebook is associated with the CORESET pool index value.

[0226] Aspect 7: The method of aspect 3, wherein the other communication is a downlink communication, the method further includes: transmitting a negative acknowledgment (NACK) indication for the downlink communication.

[0227] Aspect 8: The method of any of Aspects 1-7, wherein the indication of the disallowed communication direction is conveyed via radio resource control signaling or media access control (MAC) control element signaling.

[0228] Aspect 9: The method of any of Aspects 1-8, wherein the indication of the disallowed communication direction includes an indication that the disallowed communication direction is not permitted for communication associated with the control resource set (CORESET) pool index value during the one or more full-duplex time intervals.

[0229] Aspect 10: The method of any of Aspects 1-9, wherein the indication of the disallowed communication direction includes an indication of a first disallowed communication direction for communication associated with a first control resource set (CORESET) pool index value and an indication of a second disallowed communication direction for communication associated with a second CORESET pool index value.

[0230] Aspect 11: The method of any of Aspects 1-10, wherein the indication of the disallowed communication direction includes an indication of a Transmission Configuration Indicator (TCI) state associated with the full-duplex operation state and the disallowed communication direction, the TCI state indicating that the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

[0231] Aspect 12: The method of aspect 11, wherein the indication of the TCI state indicates that the TCI state is associated with a control resource set (CORESET) pool index value, the TCI state indicating that communication associated with the CORESET pool index value and the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

[0232] Aspect 13: The method of any of Aspects 1-12, wherein the one or more full-duplex time intervals are one or more sub-band full-duplex time intervals.

[0233] Aspect 14: The method of any of Aspects 1-13, wherein the one or more full-duplex time intervals include at least one of the following: one or more full-duplex time slots, or one or more full-duplex orthogonal frequency division multiplexing (OFDM) symbols.

[0234] Aspect 15: A wireless communication method performed by a network node, comprising: transmitting an indication associated with a user equipment (UE) of one or more full-duplex time intervals; transmitting an indication associated with the UE of a disallowed communication direction associated with the one or more full-duplex time intervals; and during one of the one or more full-duplex time intervals, transmitting or receiving communication according to whether the communication for the UE is in a communication direction that is not a disallowed communication direction.

[0235] Aspect 16: The method of aspect 15, wherein the indication of the disallowed communication direction is associated with the disallowance of uplink signals and channels or downlink signals and channels for one or more full-duplex time intervals.

[0236] Aspect 17: The method of any of Aspects 15-16 further includes: during the full-duplex time interval or another full-duplex time interval in the one or more full-duplex time intervals, dropping the other communication if the other communication is in the disallowed communication direction.

[0237] Aspect 18: The method of aspect 17, wherein the other communication is a downlink communication, the method further includes: receiving a Type 1HARQ codebook associated with a set of downlink timings including downlink timings corresponding to the downlink communication, the Type 1HARQ codebook not including an indication for the downlink timing.

[0238] Aspect 19: The method of aspect 18, wherein the disallowed communication direction is not permitted for use with the control resource set (CORESET) pool index value, wherein the downlink timing is associated with the CORESET pool index value, and wherein the type 1HARQ codebook is associated with the CORESET pool index value.

[0239] Aspect 20: The method of aspect 17, wherein the other communication is a downlink communication, the method further includes: receiving a negative acknowledgment (NACK) indication for the downlink communication.

[0240] Aspect 21: The method of any of Aspects 15-20, wherein the indication of the disallowed communication direction is conveyed via radio resource control signaling or media access control (MAC) control element signaling.

[0241] Aspect 22: The method of any of Aspects 15-21, wherein the indication of the disallowed communication direction includes an indication that the disallowed communication direction is not permitted for communication associated with the control resource set (CORESET) pool index value during the one or more full-duplex time intervals.

[0242] Aspect 23: The method of any of Aspects 15-22, wherein the indication of the disallowed communication direction includes an indication of a first disallowed communication direction for communication associated with a first control resource set (CORESET) pool index value and an indication of a second disallowed communication direction for communication associated with a second CORESET pool index value.

[0243] Aspect 24: The method of any of Aspects 15-23, wherein the indication of the disallowed communication direction includes an indication of a Transmission Configuration Indicator (TCI) state associated with the full-duplex operation state and the disallowed communication direction, the TCI state indicating that the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

[0244] Aspect 25: The method of aspect 24, wherein the indication of the TCI state indicates that the TCI state is associated with a control resource set (CORESET) pool index value, the TCI state indicating that communication associated with the CORESET pool index value and the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

[0245] Aspect 26: The method of any of Aspects 15-25, wherein the one or more full-duplex time intervals are one or more sub-band full-duplex time intervals.

[0246] Aspect 27: The method of any of Aspects 15-26, wherein the one or more full-duplex time intervals include at least one of the following: one or more full-duplex time slots, or one or more full-duplex orthogonal frequency division multiplexing (OFDM) symbols.

[0247] Aspect 28: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods of aspects 1-14.

[0248] Aspect 29: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform one or more of the methods of aspects 1-14.

[0249] Aspect 30: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of aspects 1-14.

[0250] Aspect 31: A non-transient computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of aspects 1-14.

[0251] Aspect 32: A non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 1-14.

[0252] Aspect 33: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods of aspects 15-27.

[0253] Aspect 34: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform one or more of the methods of aspects 15-27.

[0254] Aspect 35: An apparatus for wireless communication, comprising at least one means for performing one or more methods as described in aspects 15-27.

[0255] Aspect 36: A non-transient computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of aspects 15-27.

[0256] Aspect 37: A non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods as described in aspects 15-27.

[0257] The foregoing disclosure provides explanations and descriptions, 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 foregoing disclosure or may be obtained through practice.

[0258] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and software. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein can be implemented in various forms, either in hardware or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems and / or methods are described herein without reference to any specific software code, as those skilled in the art will understand that software and hardware can be designed to implement these systems or methods, at least in part, based on the descriptions herein.

[0259] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0260] As used herein, the term "determine" or "determine" encompasses a wide variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), inference, ascertainment, and / or measurement, etc. Furthermore, "determine" can include receiving (such as receiving information), accessing (such as accessing data in memory), and / or transmitting (such as transmitting information), etc. Additionally, "determine" can include parsing, selecting, obtaining, choosing, creating, and other similar actions.

[0261] Although specific combinations of features are described in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. Many of these features may be combined in ways not specifically described in the claims and / or not disclosed in the specification. The disclosure of aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase “at least one of” refers to any combination of these items, including 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, as well as any combination having 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).

[0262] The elements, actions, or instructions used herein should not be construed as essential or necessary unless explicitly described as such. Furthermore, as used herein, the articles “a” and “a certain” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referenced in conjunction with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” In cases where only one item is intended, the phrase “only one” or similar language is used. Moreover, as used herein, the terms “have,” “contain,” “include,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., the element “has” A may also have B). Additionally, as used herein, “based on” is intended to be interpreted in an inclusive sense unless explicitly indicated otherwise. For example, “based on” may be used interchangeably with “at least partially based on,” “associated with,” or “according to,” unless explicitly indicated otherwise. Specifically, unless the phrase refers to "based solely on 'a'" or its equivalent in the context, "based on 'a'" or "at least partially based on 'a'" can be based solely on "a" or based on "a" in combination with one or more other factors, conditions, or information. Furthermore, as used herein, the term "or" is intended to be inclusive when used in a sequence and can be used interchangeably with "and / or" unless otherwise explicitly stated (e.g., in conjunction with "either of" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; as well as At least one processor communicatively coupled to the at least one memory, the at least one processor being operable to cause the UE to: Receive instructions for one or more full-duplex time intervals from network nodes; Receive from the network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals; as well as During one of the one or more full-duplex time intervals, the communication is transmitted to or received from the network node in a communication direction that is not the permitted communication direction.

2. The UE of claim 1, wherein the indication of the disallowed communication direction is associated with uplink signals and channels or downlink signals and channels not being permitted for the one or more full-duplex time intervals.

3. The UE of claim 1, wherein the at least one processor is further operable to cause the UE to: During the full-duplex time interval or another full-duplex time interval of the one or more full-duplex time intervals, the other communication is dropped because it is in the disallowed communication direction.

4. The UE of claim 3, wherein the other communication is downlink communication, wherein the at least one processor is further operable to cause the UE to: Suppress the transmission of Hybrid Automatic Repeat Request (HARQ) feedback indications associated with the downlink communication.

5. The UE as described in claim 4, wherein, In order for the UE to suppress the transmission of the HARQ feedback indication associated with the downlink communication, the at least one processor is operable to cause the UE to: Transmit a Type 1 HARQ codebook associated with a set of downlink timings that includes downlink timings corresponding to the downlink communication, wherein the Type 1 HARQ codebook does not include an indication for the downlink timing.

6. The UE of claim 5, wherein the disallowed communication direction is not permitted for use with the control resource set CORESET pool index value, wherein the downlink timing is associated with the CORESET pool index value, and wherein the type 1 HARQ codebook is associated with the CORESET pool index value.

7. The UE of claim 3, wherein the other communication is downlink communication, wherein the at least one processor is further operable to cause the UE to: Transmit a negative acknowledgment (NACK) indication for the downlink communication.

8. The UE of claim 1, wherein the indication of the disallowed communication direction is conveyed via radio resource control signaling or media access control (MAC) control element signaling.

9. The UE of claim 1, wherein the indication of the disallowed communication direction includes an indication that the disallowed communication direction is not permitted for communication associated with the control resource set CORESET pool index value during the one or more full-duplex time intervals.

10. The UE of claim 1, wherein the indication of the disallowed communication direction includes an indication of a first disallowed communication direction for communication associated with a first control resource set CORESET pool index value and an indication of a second disallowed communication direction for communication associated with a second CORESET pool index value.

11. The UE of claim 1, wherein the indication of the disallowed communication direction includes an indication of a Transmission Configuration Indicator (TCI) state associated with the full-duplex operation state and the disallowed communication direction, the TCI state indicating that the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

12. The UE of claim 11, wherein the indication of the TCI state indicates that the TCI state is associated with a control resource set CORESET pool index value, the TCI state indicating that communication associated with the CORESET pool index value and the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

13. A network node for wireless communication, the network node comprising: At least one memory; as well as At least one processor communicatively coupled to the at least one memory, the at least one processor being operable to cause the network node to: Transmits indications of one or more full-duplex time intervals associated with the user equipment (UE); Transmit an indication associated with the UE of a disallowed communication direction related to one or more full-duplex time intervals; as well as During one of the one or more full-duplex time intervals, the communication to the UE is transmitted or received in a communication direction that is not the prohibited communication direction.

14. The network node of claim 13, wherein the indication of the disallowed communication direction is associated with uplink signals and channels or downlink signals and channels not being permitted for the one or more full-duplex time intervals.

15. The network node of claim 13, wherein the at least one processor is further operable to cause the network node to: During the full-duplex time interval or another full-duplex time interval of the one or more full-duplex time intervals, the other communication is dropped because it is in the disallowed communication direction.

16. The network node of claim 15, wherein the other communication is downlink communication, wherein the at least one processor is further operable to cause the network node to: Receive a Type 1 HARQ codebook associated with a set of downlink timings that includes downlink timings corresponding to the downlink communication, wherein the Type 1 HARQ codebook does not include an indication for the downlink timing.

17. The network node of claim 13, wherein the indication of the disallowed communication direction includes an indication that the disallowed communication direction is not permitted for communication associated with the control resource set CORESET pool index value during the one or more full-duplex time intervals.

18. The network node of claim 13, wherein the indication of the disallowed communication direction includes an indication of a Transmission Configuration Indicator (TCI) state associated with the full-duplex operation state and the disallowed communication direction, the TCI state indicating that the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

19. A wireless communication method performed by a user equipment (UE), comprising: Receive instructions for one or more full-duplex time intervals from network nodes; Receive from the network node an indication of a disallowed communication direction associated with the one or more full-duplex time intervals; as well as During one of the one or more full-duplex time intervals, the communication is transmitted to or received from the network node in a communication direction that is not the permitted communication direction.

20. The method of claim 19, wherein the indication of the disallowed communication direction is associated with uplink signals and channels or downlink signals and channels not being permitted for the one or more full-duplex time intervals.

21. The method of claim 19, further comprising: During the full-duplex time interval or another full-duplex time interval of the one or more full-duplex time intervals, the other communication is dropped because it is in the disallowed communication direction.

22. The method of claim 21, wherein the other communication is downlink communication, the method further comprising: Suppress the transmission of Hybrid Automatic Repeat Request (HARQ) feedback indications associated with the downlink communication.

23. The method of claim 22, wherein suppressing the transmission of the HARQ feedback indication associated with the downlink communication comprises: Transmit a Type 1 HARQ codebook associated with a set of downlink timings that includes downlink timings corresponding to the downlink communication, wherein the Type 1 HARQ codebook does not include an indication for the downlink timing.

24. The method of claim 23, wherein the disallowed communication direction is not permitted for use in controlling the resource set CORESET pool index value, wherein the downlink timing is associated with the CORESET pool index value, and wherein the type 1 HARQ codebook is associated with the CORESET pool index value.

25. The method of claim 19, wherein the indication of the disallowed communication direction includes an indication of a Transmission Configuration Indicator (TCI) state associated with a full-duplex operation state and the disallowed communication direction, the TCI state indicating that the disallowed communication direction is not permitted for the one or more full-duplex time intervals.

26. A wireless communication method performed by a network node, the method comprising: Transmits indications of one or more full-duplex time intervals associated with the user equipment (UE); Transmit an indication associated with the UE of a disallowed communication direction related to one or more full-duplex time intervals; as well as During one of the one or more full-duplex time intervals, the communication to the UE is transmitted or received in a communication direction that is not the prohibited communication direction.

27. The method of claim 26, wherein the indication of the disallowed communication direction is associated with uplink signals and channels or downlink signals and channels not being permitted for the one or more full-duplex time intervals.

28. The method of claim 26, further comprising: During the full-duplex time interval or another full-duplex time interval of the one or more full-duplex time intervals, the other communication is dropped because it is in the disallowed communication direction.

29. The method of claim 28, wherein the other communication is downlink communication, the method further comprising: Receive a Type 1 HARQ codebook associated with a set of downlink timings that includes downlink timings corresponding to the downlink communication, wherein the Type 1 HARQ codebook does not include an indication for the downlink timing.

30. The method of claim 26, wherein the one or more full-duplex time intervals comprise at least one of the following: One or more full-duplex time slots, or One or more full-duplex orthogonal frequency division multiplexing (OFDM) symbols.

Images