Unauthorized communication directions for full-duplex time intervals

Abstract

Various aspects of this disclosure relate, in general, to wireless communications. Some aspects relate to unauthorized communication directions for full-duplex time intervals. Some aspects relate, more specifically, to defining permitted and / or unauthorized communication directions for full-duplex time intervals (e.g., for slots and / or symbols associated with full-duplex operation) for user equipment (UE). In some aspects, a network node sends an indication to the UE of communication directions that will be disabled or dropped (e.g., not received or transmitted) during slots or symbols associated with full-duplex operation at the network node. During a full-duplex time interval, the UE may transmit or receive communications that are in an permitted communication direction (e.g., not in an unauthorized communication direction).

Description

Technical Field

[0001] (Cross - Reference to Related Applications)

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

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication, and more particularly, to techniques and apparatus associated with disallowed communication directions for full - duplex time intervals.

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, including telephone, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies that enable 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 a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard, published by the Third Generation Partnership Project (3GPP).

[0004]

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, national, regional, or global scale. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, enhancing service, utilizing new spectra, using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) (CP-OFDM) on the downlink, and using CP-OFDM or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM, DFT-s-OFDM) on the uplink, as well as by better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful.

[0005]

[0005] In some examples, a network node may operate using different operating states. In different operating states, a network node may 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 may operate in full-duplex mode (e.g., transmit and receive communications simultaneously). To improve the spatial isolation of the antennas and / or TRPs used in each communication direction, when operating in full-duplex mode, a network node may use a first antenna and / or first TRP for downlink signals and a second antenna and / or second TRP for uplink signals. For example, improving the spatial isolation of the first antenna and / or first TRP from the second antenna and / or second TRP can reduce self-interference associated with full-duplex operation. Therefore, when a network node is operating in full-duplex mode, the network node's first antenna and / or first TRP may be unavailable for uplink signals, and the network node's second antenna and / or second TRP may be unavailable for downlink signals.

[0006]

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

[0007]

[0007] In some examples, the UE may rely on network nodes to refrain from scheduling communications in a given communication direction during a full-duplex time interval. However, relying on network nodes to perform scheduling decisions may not be feasible or reliable in some situations. For example, some communications may be periodic and / or semi-persistent (e.g., occurring every X slot, symbol, or millisecond). The periodicity of these communications may not be consistent with the slot format periodicity, and as a result, some of the periodic and / or semi-persistent communications may be scheduled to occur during a full-duplex time interval. As another example, communications may be associated with one or more iterations. Communications may be scheduled during a non-full-duplex time interval, but the iterations of communications may occur during a full-duplex time interval. As yet another example, a single downlink control information (DCI) communication may schedule multiple communications (e.g., different transport blocks may be scheduled). One or more of the communications may be scheduled during a non-full-duplex time interval, but one or more other communications may occur during a full-duplex time interval.

[0008]

[0008] The UE may not know a given communication direction (which may be associated with, for example, insufficient performance of the UE during a full-duplex time interval). Therefore, the UE may consume resources (e.g., power resources, processing resources, and / or network resources) to or attempt to transmit or receive communications (e.g., associated with a given communication direction) from or to antennas and / or TRPs of network nodes that are unavailable for a given communication direction during a full-duplex time interval. [Overview of the project]

[0009]

[0009] Some embodiments described herein relate to user equipment (UE) for wireless communications. The UE may comprise at least one memory and at least one processor commutatically coupled to at least one memory. The at least one processor may be operable to cause the UE to receive indications of one or more full-duplex time intervals from a network node. The at least one processor may be operable to cause the UE to receive indications of unauthorized communication directions associated with one or more full-duplex time intervals from a network node. The at least one processor may be operable to cause the UE to transmit or receive communications during one of the one or more full-duplex time intervals, such that communications are in a communication direction that is not an unauthorized communication direction to or from a network node. As a result, it is made clear how the full-duplex time intervals should be utilized by the UE when the network node is operating in full-duplex mode. For example, the UE may transmit or receive communications in an authorized communication direction and / or drop communications in an unauthorized communication direction during a full-duplex time interval. This can save resources (e.g., power resources, processing resources, and / or network resources) that would otherwise have been used by attempting to transmit or receive communications in unauthorized communication directions (e.g., to or from antennas and / or TRPs of network nodes that are unavailable in unauthorized communication directions during a full-duplex time interval). Thus, the efficiency of the UE and the wireless communication system can be improved.

[0010]

[0010] Some embodiments described herein relate to network nodes for wireless communications. A network node may comprise at least one memory and at least one processor commutatically coupled to at least one memory. At least one processor may be operable to cause the network node to transmit one or more full-duplex time interval indications associated with a UE. At least one processor may be operable to cause the network node to transmit UE-associated indications for unauthorized communication directions associated with one or more full-duplex time intervals. At least one processor may be operable to cause the network node to transmit or receive communications for a UE during one of the full-duplex time intervals, such that the communication is in a communication direction that is not an unauthorized communication direction.

[0011]

[0011] Some aspects described herein relate to methods of wireless communication implemented by a UE. The method may include receiving indications for one or more full-duplex time intervals from a network node. The method may include receiving indications for unauthorized communication directions associated with one or more full-duplex time intervals from a network node. The method may include transmitting or receiving communications to or from a network node during one of the full-duplex time intervals of one or more full-duplex time intervals, such that the communication is in a communication direction that is not an unauthorized communication direction.

[0012]

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

[0013]

[0013] Some embodiments described herein relate to a non-temporary computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, can cause the UE to receive indications of one or more full-duplex time intervals from a network node. The set of instructions, when executed by one or more processors of the UE, can cause the UE to receive indications of unauthorized communication directions associated with one or more full-duplex time intervals from a network node. The set of instructions, when executed by one or more processors of the UE, can cause the UE to transmit or receive communications during one of the full-duplex time intervals of the one or more full-duplex time intervals, such that the communications are in a communication direction that is not an unauthorized communication direction to a network node.

[0014]

[0014] Some embodiments described herein relate to a non-temporary computer-readable medium for storing a set of instructions for wireless communication by network nodes. The set of instructions, when executed by one or more processors of the network nodes, can cause the network nodes to transmit one or more full-duplex time interval indications associated with the UE. The set of instructions, when executed by one or more processors of the network nodes, can cause the network nodes to transmit UE-associated indications for unauthorized communication directions associated with one or more full-duplex time intervals. The set of instructions, when executed by one or more processors of the network nodes, can cause the network nodes to transmit or receive communications for the UE during one of the full-duplex time intervals, such that the communication is in a communication direction that is not an unauthorized communication direction.

[0015]

[0015] Some embodiments described herein relate to devices for wireless communications. The devices may include means for receiving indications of one or more full-duplex time intervals from a network node. The devices may include means for receiving indications of unauthorized communication directions associated with one or more full-duplex time intervals from a network node. The devices may include means for transmitting or receiving communications to or from a network node during one of the full-duplex time intervals, such that the communication is in a communication direction that is not an unauthorized communication direction.

[0016]

[0016] Some embodiments described herein relate to devices for wireless communications. The device may include means for transmitting indications associated with a UE in one or more full-duplex time intervals. The device may include means for transmitting indications associated with a UE in an unauthorized communication direction associated with one or more full-duplex time intervals. The device may include means for transmitting or receiving communications for a UE in one of the full-duplex time intervals, such that the communications are in a communication direction that is not an unauthorized communication direction.

[0017]

[0017] The embodiments will be described in general with reference to the drawings and this specification and will include methods, apparatus, systems, computer program products, non-temporary computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices, or processing systems as shown in the drawings and this specification.

[0018]

[0018] The above provides a fairly broad overview of the features and technical advantages of the examples provided in this disclosure so that the modes for carrying out the following inventions may be better understood. Additional features and advantages are described below. The concepts and specific embodiments disclosed may be readily used as a basis for modifying or designing other structures to accomplish the same objectives of this disclosure. Such equivalent structures shall not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their configuration and method of operation, along with their relevant advantages, will be better understood from the following description by examining them with respect to the appended figures. Each of the figures is provided for illustrative and explanatory purposes and is not provided to define any limitation of the claims. [Brief explanation of the drawing]

[0019]

[0019] To better understand the features of the present disclosure listed above in detail, a more detailed description, briefly summarized above, may be obtained by referring to the aspects shown in part in the accompanying drawings. However, note that since the description may admit other equally valid aspects, the accompanying drawings show only some exemplary aspects of the present disclosure and should not be considered to limit its scope. The same reference numerals in different drawings may identify the same or similar elements.

[0020] [Figure 1]

[0020] FIG. showing an example of a wireless network according to the present disclosure. [Figure 2]

[0021] FIG. showing an exemplary network node communicating with a user equipment (UE) within a wireless network according to the present disclosure. [Figure 3]

[0022] FIG. showing an exemplary non - aggregated base station architecture according to the present disclosure. [Figure 4]

[0023] FIGS. 4A - 4C are diagrams showing examples of full - duplex communication according to the present disclosure. [Figure 5]

[0024] FIG. showing an example of full - duplex communication according to the present disclosure. [Figure 6]

[0025] FIG. showing an example of a full - duplex slot configuration according to the present disclosure. [Figure 7]

[0026] FIG. showing an example of full - duplex operation at a network node according to the present disclosure. [Figure 8]

[0027] FIG. showing an example related to operations associated with unallowed communication directions for a full - duplex time interval according to the present disclosure. [Figure 9]

[0028] FIG. showing an example related to operations associated with unallowed communication directions for a full - duplex time interval according to the present disclosure. [Figure 10]

[0029] FIGURE OF AN EXAMPLE ASSOCIATED WITH AN UNAUTHORIZED COMMUNICATION DIRECTION FOR ALL DUPLEX TIME INTERVALS ACCORDING TO THE PRESENT DISCLOSURE. [Figure 11]

[0030] FIGURE OF A FLOWCHART SHOWING AN EXEMPLARY PROCESS EXECUTED BY A UE THAT SUPPORTS, FOR EXAMPLE, AN UNAUTHORIZED COMMUNICATION DIRECTION FOR ALL DUPLEX TIME INTERVALS ACCORDING TO THE PRESENT DISCLOSURE. [Figure 12]

[0031] FIGURE OF A FLOWCHART SHOWING AN EXEMPLARY PROCESS EXECUTED BY A NETWORK NODE THAT SUPPORTS, FOR EXAMPLE, AN UNAUTHORIZED COMMUNICATION DIRECTION FOR ALL DUPLEX TIME INTERVALS ACCORDING TO THE PRESENT DISCLOSURE. [Figure 13]

[0032] FIGURE OF AN EXEMPLARY APPARATUS FOR WIRELESS COMMUNICATION THAT SUPPORTS, FOR EXAMPLE, AN UNAUTHORIZED COMMUNICATION DIRECTION FOR ALL DUPLEX TIME INTERVALS ACCORDING TO THE PRESENT DISCLOSURE. [Figure 14]

[0033] FIGURE OF AN EXEMPLARY APPARATUS FOR WIRELESS COMMUNICATION THAT SUPPORTS, FOR EXAMPLE, AN UNAUTHORIZED COMMUNICATION DIRECTION FOR ALL DUPLEX TIME INTERVALS ACCORDING TO THE PRESENT DISCLOSURE. [MODE FOR CARRYING OUT THE INVENTION]

[0021]

[0034] Hereafter, various aspects of the Disclosure will be described more fully with reference to the accompanying drawings. However, the Disclosure may be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the Disclosure. Rather, these aspects are provided to make the Disclosure sufficient and complete and to fully convey the scope of the Disclosure to those skilled in the art. Those skilled in the art will understand that the scope of the Disclosure is intended to encompass any aspect of the Disclosure disclosed herein, whether implemented independently of any other aspect of the Disclosure or in combination with any other aspect of the Disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of aspects described herein. Furthermore, the scope of the Disclosure is intended to encompass any such apparatus or method practiced using other structures, functions, or structures and functions in addition to, or other than, the various aspects of the Disclosure described herein. Any aspect of the Disclosure disclosed herein may be embodied by one or more elements of the claims.

[0022]

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

[0023]

[0036] Various embodiments generally relate to unauthorized communication directions for full-duplex time intervals. Some embodiments relate more specifically to defining permitted and / or unauthorized communication directions for full-duplex time intervals (e.g., for slots and / or symbols associated with full-duplex operation) for user equipment (UE). In some embodiments, a network node may transmit indications of communication directions (and / or channels and / or reference signals) that are disabled or dropped (e.g., not received or transmitted) during slots or symbols associated with full-duplex operation at the network node. A UE may transmit or receive communications that are in an permitted communication direction (e.g., not in an unauthorized communication direction) during a full-duplex time interval. In some embodiments, a UE may refrain from transmitting or receiving communications that are in an unauthorized communication direction during a full-duplex time interval (e.g., may drop them).

[0024]

[0037] Certain aspects of the subject matter described herein can be implemented to achieve one or more of the following potential benefits. In some examples, the techniques described may be used to clarify how full-duplex time intervals should be utilized by a UE when a network node is operating in full-duplex mode (e.g., using uncoordinated antennas and / or transmit / receive points (TRPs)). For example, during a full-duplex time interval, a UE may transmit or receive communications in permitted communication directions and / or drop communications in unauthorized communication directions. This can save resources (e.g., power resources, processing resources, and / or network resources) that the UE would otherwise have used by attempting to transmit or receive communications in unauthorized communication directions (e.g., to or from antennas and / or TRPs of a network node that are unavailable in unauthorized communication directions during a full-duplex time interval). Thus, the efficiency of the UE and the wireless communication system can be improved.

[0025]

[0038] In some embodiments, feedback behavior can be defined for dropped communications associated with unauthorized communication directions. For example, when a UE does not receive downlink communications (e.g., because the downlink is an unauthorized communication direction), the UE may refrain from sending Hybrid Auto Retransmission Request (HARQ) feedback for the downlink communications (e.g., thereby saving power, processing, and / or network resources that would otherwise have been used by a UE sending HARQ feedback for downlink communications that the network node knows have not been sent to the UE).

[0026]

[0039] In some embodiments, indications of unauthorized communication directions may be associated with a given control resource set (CORESET) pool index value. For example, a network node may send and a UE may receive an indication that communication associated with a given communication direction and a given CORESET pool index value is not permitted, disabled, and / or should be dropped during a full-duplex time interval. This allows for improved control and / or flexibility in indicating unauthorized (and / or permitted) communication directions in multi-TRP and / or multi-downlink control information (multi-DCI) scenarios.

[0027]

[0040] Figure 1 shows an example of a wireless network according to the present disclosure. The wireless network 100 may be, or may include, elements of a 5G (e.g., NR) network or a 4G (e.g., Long-Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (indicated as network node (NN) 110a, network node 110b, network node 110c, and network node 110d), a UE 120 or multiple UE 120s (indicated as UE120a, UE120b, UE120c, UE120d, and UE120e), or other entities. A network node 110 is an entity that communicates with a UE 120. As shown in the figure, a network node 110 may include one or more network nodes. For example, network node 110 could be an aggregated network node, meaning that the aggregated network node is 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). In another embodiment, network node 110 could be a non-aggregated network node (sometimes referred to as a non-aggregated base station), meaning that the 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)).

[0028]

[0041] In some examples, network node 110 is or includes a network node such as an RU that communicates with UE 120 via a wireless access link. In some examples, network node 110 is or includes a network node such as a DU that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node such as a CU that communicates with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as an aggregated network node 110 or an unaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs. Network nodes 110 may include, for example, NR network nodes, LTE network nodes, node B, eNB (e.g., in 4G), gNB (e.g., in 5G), access points, or TRP, DU, RU, CU, network mobility elements, core network nodes, network elements, network equipment, and / or RAN nodes. In some examples, network nodes 110 may interconnect with each other or with one or more other network nodes 110 within the wireless network 100 using any suitable transport network through various types of fronthaul, midhaul, or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0029]

[0042] Each network node 110 may provide communication coverage to a specific geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” may refer to the coverage area of ​​network node 110 or the network node subsystem that serves that coverage area, depending on the context in which the term is used.

[0030]

[0043] Network node 110 may provide communication coverage to macrocells, picocells, femtocells, or other types of cells. Macrocells may cover relatively large geographical areas (e.g., a radius of several kilometers) and may enable unrestricted access by UEs 120 subscribing to the service. Picocells may cover relatively small geographical areas and may enable unrestricted access by UEs 120 subscribing to the service. Femtocells may cover relatively small geographical areas (e.g., a home) and may enable limited access by UEs 120 associated with a femtocell (e.g., UEs 120 within a closed subscriber group (CSG)). Network node 110 relating to a macrocell may be referred to as a macronetwork node. Network node 110 relating to a picocell may be referred to as a piconetwork node. Network node 110 relating to a femtocell may be referred to as a femtonetwork node or home network node.

[0031]

[0044] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macronetwork nodes, piconetwork nodes, femtonetwork nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, macronetwork nodes may have high transmit power levels (e.g., 5 to 40 watts), while piconetwork nodes, femtonetwork nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts). In the embodiment shown in Figure 1, network node 110a may be a macronetwork node relating to macrocell 102a, network node 110b may be a piconetwork node relating to picocell 102b, and network node 110c may be a femtonetwork node relating to femtocell 102c. A network node may support one or more (e.g., three) cells. In some examples, cells may not necessarily be stationary, and the geographical area of ​​a cell may move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0032]

[0045] In some embodiments, the terms “base station” or “network node” may refer to an aggregated base station, a non-aggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some embodiments, “base station” or “network node” may refer to a CU, DU, RU, a quasi-real-time (quasi-RT) RAN intelligent controller (RIC), and / or a non-real-time (non-RT) RIC. In some embodiments, the terms “base station” or “network node” may refer to a single device configured to perform one or more functions, such as those described herein with respect to network node 110. In some embodiments, the terms “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 several different devices (which may be located at the same or different geographical locations) may be configured to perform at least a portion of a function, or to replicate the performance of at least a portion of a function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some embodiments, the terms “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 embodiments, two or more base station functions may be instantiated on a single device. In some embodiments, the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include two or more base stations.

[0033]

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

[0034]

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

[0035]

[0048] The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from an upstream station (e.g., a network node 110 or UE 120) and send data transmissions to a downstream station (e.g., a UE 120 or network node 110). A relay station may also be a UE 120 that relays transmissions to other UE 120s. In the embodiment shown in Figure 1, a network node 110d (e.g., a relay network node) may communicate with network nodes 110a (e.g., a macro network node) and UE 120d to facilitate communication between them. The network node 110 that relays communications may be called a relay station, a relay network node, or a relay.

[0036]

[0049] UE120 may be distributed across the entire wireless network 100, and each UE120 may be fixed or mobile. UE120 may include, for example, access terminals, terminals, mobile stations, or subscriber units. UE120 may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, game devices, netbooks, smartbooks, ultrabooks, medical devices, biomedical devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets)), entertainment devices (e.g., music devices, video devices, or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, UE functions of network nodes, or any other suitable devices configured to communicate via a wireless medium.

[0037]

[0050] Some UE120s 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, other devices (e.g., remote devices), or any other entities. Some UE120s may be considered Internet-of-Things (IoT) devices, or implemented as NB-IoT (Narrowband IoT) devices. Some UE120s may be considered customer premises equipment. A UE120 may be contained within a housing that accommodates its components, 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 operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0038]

[0051] In general, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be called a wireless technology or air interface. Frequencies may be called carriers or frequency channels. To avoid interference between wireless networks of different RATs, each frequency may support a single RAT within a given geographical area. In some cases, NR or 5G RAT networks may be deployed.

[0039]

[0052] In some examples, two or more UE120s (e.g., shown as UE120a and UE120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (e.g., vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol), or a mesh network. In such embodiments, UE120s may perform scheduling operations, resource selection operations, or other operations described elsewhere in this specification as being performed by network node 110.

[0040]

[0053] Devices in wireless network 100 may communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, or channels by frequency or wavelength. For example, devices in wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is above 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0041]

[0054] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. In recent 5G NR research, the operating band for these intermediate band frequencies is identified as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands within FR3 can inherit the characteristics of either FR1 or FR2, and therefore, the characteristics of FR1 or FR2 can be effectively extended to the intermediate band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0042]

[0055] With the above embodiments in mind, unless otherwise specified, the term “sub-6GHz” as used herein may broadly refer to frequencies that may be less than 6GHz, within FR1, or include intermediate band frequencies. Furthermore, unless otherwise specified, the term “millimeter wave” as used herein may broadly refer to frequencies that may include intermediate band frequencies, within FR2, FR4, FR4-a or FR4-1, or FR5, or within the EHF band. The frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and the techniques described herein are intended to be applicable to those modified frequency ranges.

[0043]

[0056] In some embodiments, UE120 may include a communications manager 140. As described in more detail elsewhere in this specification, the communications manager 140 may receive indications of one or more full-duplex time intervals from network nodes, receive indications of unauthorized communication directions associated with one or more full-duplex time intervals from network nodes, and transmit or receive communications to or from network nodes during one of the one or more full-duplex time intervals, in accordance with the fact that the communications are in a communication direction that is not an unauthorized communication direction. That is, the communications manager 140 of UE120 may transmit or receive communications to or from network nodes during one of the one or more full-duplex time intervals, in accordance with the fact that the communications are in a communication direction that is not an unauthorized communication direction. In addition or alternatively, the communications manager 140 may perform one or more other operations described herein. UE120 may transmit or receive communications during a full-duplex time interval in response to the fact that the communications are in an authorized communication direction (e.g., not in an unauthorized communication direction). As an addition or alternative, UE120 may refrain from sending or receiving a communication during a full-duplex time interval (e.g., drop it) in response to the communication being in an unauthorized communication direction (e.g., not in an authorized direction). An authorized communication direction may be, for example, the downlink direction in which the communication is sent from network node 110 to UE120. In such an example, the unauthorized communication direction may be the uplink direction. Alternatively, an authorized direction may be, for example, the uplink direction in which the communication is sent from UE120 to network node 110. In such an example, the unauthorized communication direction may be the downlink direction. Therefore, based on an indication of an unauthorized communication direction received from network node 110, UE120 may, in response to or in association with it, determine whether a communication during one or more full-duplex time intervals is in an unauthorized communication direction. UE120 may, in accordance with the determination, send or receive the communication, or refrain from sending or receiving the communication.

[0044]

[0057] In some embodiments, the network node 110 may include a communications manager 150. As described in more detail elsewhere in this specification, the communications manager 150 may transmit indications associated with the UE for one or more full-duplex time intervals, transmit indications associated with the UE for unauthorized communication directions associated with one or more full-duplex time intervals, and transmit or receive communications for the UE during one of the one or more full-duplex time intervals, in accordance with the fact that the communications are in a communication direction that is not an unauthorized communication direction. That is, the communications manager 150 of the network node 110 may transmit communications for or receive communications for / from the UE 120 during one of the one or more full-duplex time intervals, in accordance with the fact that the communications are in a communication direction that is not an unauthorized communication direction. In addition or alternatively, the communications manager 150 may perform one or more other operations described herein. The network node 110 may transmit or receive communications during a full-duplex time interval in response to the fact that the communications are in an authorized communication direction (e.g., not in an unauthorized communication direction). Additionally or alternatively, network node 110 may refrain from sending or receiving communications during a full-duplex time interval (e.g., drop them) in response to communications being in an unauthorized communication direction (e.g., communications not in an authorized direction). An authorized communication direction may be, for example, a downlink direction in which communications are sent from network node 110 to UE 120. In such an example, an unauthorized communication direction may be an uplink direction. Alternatively, an authorized direction may be, for example, an uplink direction in which communications are sent from UE 120 to network node 110. In such an example, an unauthorized communication direction may be a downlink direction. Thus, network node 110 may, based on, or in connection with, an indication of an unauthorized communication direction associated with UE 120, determine whether communications during one or more full-duplex time intervals are communications in an unauthorized communication direction.Network node 110 may, or may refrain from, transmitting or receiving communications, according to the determination.

[0045]

[0058] Figure 2 shows an exemplary network node communicating with a UE in a wireless network according to the present disclosure. The network node may correspond to network node 110 in Figure 1. Similarly, the UE may correspond to UE120 in Figure 1. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≧1). UE120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≧1). Network node 110 shown in Figure 2 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, a communication component, or another component that facilitates communication with UE120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with UE120, such as one or more CUs or one or more DUs.

[0046]

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

[0047]

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

[0048]

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

[0049]

[0062] One or more antennas (for example, antennas 234a-234t or antennas 252a-252r) may include, or be contained within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmitting or receiving components, such as one or more components in Figure 2.

[0050]

[0063] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information (for reporting, including RSRP, RSSI, RSRQ, or CQI) from controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may, where applicable, be precoded by the TX MIMO processor 266, further processed by the modem 254 (for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 in UE120 may include a modulator and demodulator. In some examples, UE120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modem(s) 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform any embodiment of the method described herein.

[0051]

[0064] In network node 110, uplink signals from UE 120 or other UEs are received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232, indicated as DEMOD), detected by MIMO detector 236 where applicable, and may be further processed by receiving processor 238 to obtain decoded data and control information sent by UE 120. The receiving 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 a communication unit 244, which may communicate with network controller 130 via the communication unit 244. Network node 110 may include a scheduler 246 for scheduling one or more UE 120 for downlink or uplink communication. In some examples, the modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antennas (one or more) 234, modems (one or more) 232, MIMO detectors 236, receiving processor 238, transmitting processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform any aspect of the methods described herein.

[0052]

[0065] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or any other component(s) in Figure 2 may perform one or more techniques associated with unauthorized communication directions for full-duplex time intervals, as described in more detail elsewhere in this specification. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or any other component(s) in Figure 2 may perform or direct the operation of, for example, process 1100 in Figure 11, process 1200 in Figure 12, or other processes described herein. Memories 242 and 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-temporary computer-readable medium that stores one or more instructions (e.g., code or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors of the network node 110 or UE 120 (for example, directly or after compilation, translation, or interpretation), one or more processors, UE 120, or network node 110 may be caused to perform or direct the operation of, for example, process 1100 in Figure 11, process 1200 in Figure 12, or other processes described herein. In some examples, executing an instruction may include, among other examples, running the instruction, translating the instruction, compiling the instruction, or interpreting the instruction.

[0053]

[0066] In some embodiments, the UE120 may include means for receiving indications of one or more full-duplex time intervals from a network node, means for receiving indications of unauthorized communication directions associated with one or more full-duplex time intervals from a network node, and / or means for transmitting or receiving communications to or from a network node during one of the full-duplex time intervals, such that the communication is in a communication direction that is not an unauthorized communication direction (e.g., means for transmitting to a network node or means for receiving from a network node). The means by which the UE120 performs the operations described herein may include, for example, one or more of the following: a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0054]

[0067] In some embodiments, the network node 110 may include means for transmitting indications associated with the UE for one or more full-duplex time intervals, means for transmitting indications associated with the UE for unauthorized communication directions associated with one or more full-duplex time intervals, and / or means for transmitting or receiving communications for the UE during one of the one or more full-duplex time intervals, in accordance with communications in a communication direction that is not an unauthorized communication direction. The means by which the network node 110 performs the operations described herein may include, for example, one or more of the following: communications manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0055]

[0068] The deployment of communication systems such as 5G NR systems can be configured in multiple ways using various components or parts. 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 an aggregated or unaggregated architecture. For example, a base station (e.g., among other examples, Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell), or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or an unaggregated base station. "Network entity" or "network node" may refer to an unaggregated base station, or one or more units of an unaggregated base station (e.g., one or more CUs, one or more DUs, and / or one or more RUs).

[0056]

[0069] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A non-aggregated base station (e.g., a non-aggregated network node) may 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, one or more DUs may be co-located with that CU, or alternatively, 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 may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0057]

[0070] The operation or network design of a base station type may take into account the aggregation characteristics of base station functionality. For example, by using non-aggregated base stations in an IAB network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network, C-RAN), the scaling of the communication system can be facilitated by separating base station functionality into one or more units that may be deployed individually. A non-aggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented in at least one unit, which can allow for flexibility in network design. Various units of a non-aggregated base station may be configured to communicate with at least one other unit of the non-aggregated base station via wired or wireless communication.

[0058]

[0071] In some embodiments, the actions described herein as being performed by network node 110 may be performed by multiple different network nodes. For example, configuration actions may be performed by a first network node (e.g., CU or DU), and wireless communication actions may be performed by a second network node (e.g., DU or RU).

[0059]

[0072] When used herein, "outputting" or "transmitting" a communication from network node 110 to UE 120 may refer to a direct transmission (e.g., from network node 110 to UE 120) or an indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, an indirect transmission to UE 120 may include the DU outputting or transmitting a communication to an RU, and the RU transmitting the communication to UE 120, or causing the RU to transmit a communication (e.g., triggering the transmission of a physical layer reference signal). Similarly, "transmitting" a communication from UE 120 to network node 110 may refer to a direct transmission (e.g., from UE 120 to network node 110) or an indirect transmission via one or more other network nodes or devices. For example, if network node 110 is a DU, an indirect transmission to network node 110 may include the UE 120 transmitting a communication to an RU, and the RU transmitting the communication to the DU. Similarly, for network node 110 to "acquire" a communication may mean directly receiving the transmission carrying the communication (for example, from UE 120 to network node 110), or receiving the communication (or information derived from the reception of the communication) via one or more other network nodes or devices.

[0060]

[0073] Figure 3 shows an exemplary non-aggregated base station architecture 300 according to the present disclosure. The non-aggregated base station architecture 300 may include a CU 310 that can communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more non-aggregated control units (e.g., a quasi-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 DU 330 via their respective midhaul links, for example, via an F1 interface. Each DU 330 may communicate with one or more RU 340 via their respective fronthaul links. Each RU 340 may communicate with one or more UE 120 via their respective radio frequency (RF) access links. In some implementations, the UE 120 may be serviced simultaneously by multiple RU 340s.

[0061]

[0074] Each of the units, including CU310, DU330, RU340, and the quasi-RT RIC325, non-RT RIC315, and SMO framework 305, may include, or be coupled to, one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmitting medium. Each of the units, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding units, may be configured to communicate with one or more of the other units via a transmitting medium. In some examples, each unit may include a wired interface configured to receive or transmit signals to or from one or more of the other units via a wired transmitting medium, and a wireless interface which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive, transmit, or send / receive signals to or from one or more of the other units via a wireless transmitting medium.

[0062]

[0075] In some embodiments, the CU310 may host one or more higher-layer control functions. Examples of such control functions include, but are not limited to, radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP). Each control function may implement an interface configured to communicate signals with other control functions hosted by the CU310. The CU310 may be configured to handle user plane functionality (e.g., Central Unit-User Plane (CU-UP) functionality) and / or control plane functionality (e.g., Central Unit-Control Plane (CU-CP) functionality). In some implementations, the CU310 may be logically divided 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 can communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. The CU310 can be implemented to communicate with the DU330 as needed for network control and signaling.

[0063]

[0076] Each DU330 may correspond to a logic unit containing one or more base station functions for controlling the operation of one or more RU340s. In some embodiments, the DU330 may host one or more of the radio link control (RLC) layer, the medium access control (MAC) layer, and one or more upper physical (PHY) layers, at least in part according to a functional partition such as a functional partition as defined by 3GPP. In some embodiments, one or more upper PHY layers may be implemented by one or more modules, among other examples, for forward error correction (FEC) coding and decoding, scrambling, and modulation and demodulation. In some embodiments, the DU330 may further host one or more lower-level PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (sometimes also referred to as a module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU330, or with control functions hosted by the CU310.

[0064]

[0077] Each RU340 can implement lower-layer functions. In some deployments, a RU340 controlled by a DU330 may correspond to a logical node hosting RF processing functions or lower-PHY layer functions, such as performing FFT, iFFT, digital beamforming, or PRACH extraction and filtering, based on a functional partitioning (e.g., functional partitioning defined by 3GPP), such as lower-layer functional partitioning. In such architectures, each RU340 can be operated to handle over-the-air (OTA) communication with one or more UE120s. In some implementations, the real-time and non-real-time modes of control plane and user plane communication with the RU340 can be controlled by the corresponding DU330. In some scenarios, this configuration allows each DU330 and CU310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0065]

[0078] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as the open cloud (O-Cloud) platform 390) to perform lifecycle management of the network element (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU310, DU330, RU340, non-RT RIC315, and quasi-RT RIC325. In some implementations, the SMO framework 305 may communicate with hardware embodiments of the 4G RAN, such as the open eNB (O-eNB) 311, via the O1 interface. In addition, in some implementations, the SMO framework 305 can communicate directly with each of one or more RU340s via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC315 configured to support the functionality of the SMO framework 305.

[0066]

[0079] Non-RT RIC315 may be configured to include logical functions that enable policy-based guidance for non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or applications / functions in quasi-RT RIC325. Non-RT RIC315 may be coupled to or communicate with quasi-RT RIC325 (via the A1 interface, for example). Quasi-RT RIC325 may be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources through data acquisition and action via an interface connecting one or more CU310s, one or more DU330s, or both, and an O-eNB to the quasi-RT RIC325 (via the E2 interface, for example).

[0067]

[0080] In some implementations, the non-RT RIC315 may receive parameter or external enrichment information from an external server to generate an AI / ML model that will be deployed in the quasi-RT RIC325. Such information may be used by the quasi-RT RIC325 and may be received in the SMO framework 305 or the non-RT RIC315 from a non-network data source or from a network function. In some examples, the non-RT RIC315 or quasi-RT RIC325 may be configured to adjust the behavior or performance of the RAN. For example, the non-RT RIC315 may monitor long-term trends and patterns in performance and take corrective action using the AI / ML model, either through the SMO framework 305 (e.g., reconfiguration via the O1 interface) or by creating a RAN management policy (e.g., an A1 interface policy).

[0068]

[0081] In some examples, an access node may have an access node controller. The access node controller may be a CU in a distributed RAN. In some examples, the backhaul interface 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 the backhaul interface for one or both of the 5G control plane and 5G user plane may terminate at the access node controller. Additionally or alternatively, the backhaul interface to one or more neighboring access nodes (e.g., another access node) may terminate at the access node controller.

[0069]

[0082] 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 called a cell, panel (e.g., an antenna panel), antenna array, or array, among other examples. Each TRP may be a DU or RU in a distributed RAN. A TRP may be connected to a single access node controller or to multiple access node controllers. In some examples, a TRP may correspond to the base stations described above with respect to Figures 1, 2, or 3. For example, different TRPs may be included in each of different base stations. As an addition or alternative, multiple TRPs may be included within a single base station. In some embodiments, a non-aggregated 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 partitioning of base station functions between the access node controller (e.g., CU) and the TRP (e.g., DU or RU) may be defined by 3GPP, etc. For example, the PDCP layer, RLC layer, or MAC layer may be configured to terminate at the access node controller or TRP.

[0070]

[0083] In some examples, multiple TRPs may transmit communications (e.g., the same or different communications) during the same transmission time interval (TTI) (e.g., slots, minislots, subframes, or symbols) or different TTIs, using different quasi-co-location (QCL) relationships (e.g., different spatial parameters, different TCI states, different precoding parameters, different beamforming parameters). In some embodiments, TCI states may be used to indicate one or more QCL relationships. Each TRP may be configured to service traffic to the UE120 individually (e.g., using dynamic selection) or together (e.g., using joint transmission with one or more other TRPs).

[0071]

[0084] In some examples, a first physical downlink control channel (PDCCH) (PDCCH 1) communication transmitted by a first TRP (TRP A) may schedule a first physical uplink shared channel (PUSCH) communication (PUSCH 1) to transmit uplink data to TRP A, and a second TRP (TRP B) may schedule a second PUSCH communication (PUSCH 2) to transmit uplink data to TRP B. The control resource set (CORESET) pool index (or CORESETPoolIndex) value may be used by the UE120 to identify the TRP associated with the uplink authorization received on the PDCCH. For example, multiple PDCCHs may be used to schedule downlink or uplink data communications for multiple corresponding physical downlink shared channels (PDSCH) or multiple corresponding PUSCHs (e.g., one PDCCH for each PDSCH or PUSCH). In such examples, a DCI (for example, having DCI format 1_0 or DCI format 1_1) may indicate the corresponding Transmit Configuration Indicator (TCI) state for the TRP corresponding to the DCI. The TCI field of the DCI indicates the corresponding TCI state (for example, 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 is sometimes called multiple DCI (mDCI) multi-TRP operation.

[0072]

[0085] A multi-DCI-based multi-TRP operational configuration allows a UE to communicate simultaneously through multiple TRPs. For example, a UE may receive a first DCI in a first PDCCH from a first TRP, and the first DCI schedules a first PDSCH or PUSCH to be transmitted by the first TRP. Similarly, a UE may receive a second DCI in a second PDCCH from a second TRP, and the second DCI schedules a second PDSCH or PUSCH to be transmitted by the second TRP. The first and second PDSCHs or PUSCHs can be non-overlapping, partially overlapping, or fully overlapping. In relation to monitoring DCIs transmitted from different TRPs, a UE may monitor PDCCH candidates in PDCCH monitoring opportunities within different CORESETs.

[0073]

[0086] A "CORESET" may refer to a control domain structured to support the efficient use of resources, such as by the flexible configuration or reconfiguration of resources for one or more PDCCHs associated with a 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 contain multiple resource blocks (RBs) in the frequency domain and one, two, or three symbols in the time domain. In 5G, the amount of resources included in a CORESET can be flexibly configured, for example, by using RRC signaling to indicate the frequency domain domain (e.g., the amount of resource blocks) and the time domain domain (e.g., the amount of symbols) for the CORESET.

[0074]

[0087] UE120 can consist of multiple CORESETs in a given serving cell. Each CORESET configured for UE120 may be associated with a CORESET identifier (CORESET ID). In some examples, two or more (e.g., up to five) CORESETs may be grouped into a CORESET pool. Each CORESET pool may be associated with a CORESET pool index value. In one embodiment, CORESET ID1 and CORESET ID2 may be grouped into CORESET pool index 0, and CORESET ID3 and CORESET ID4 may be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index value may be associated with a given TRP. For example, TRP A may be associated with CORESET pool index 0, and TRP B may be associated with CORESET pool index 1. UE120 can be configured with higher-layer parameters, such as the PDCCH-ConfigRRC parameter, using information that identifies the association between TRPs and the CORESET pool index values ​​assigned to those TRPs. Therefore, UE120 can identify the TRP that sent the DCI uplink grant by determining the CORESET ID of the CORESET sent by the PDCCH carrying the DCI uplink grant, determining the CORESET pool index value associated with the CORESET pool containing the CORESET ID, and identifying the TRP associated with the CORESET pool index value.

[0075]

[0088] Figures 4A to 4C illustrate examples of full-duplex communication according to this disclosure. The first full-duplex scenario 400 shown in Figure 4A includes UE1 402 and two network nodes (e.g., network entities or TRPs) 404-1 and 404-2, where UE1 402 transmits uplink transmissions to network node 404-1 and receives downlink transmissions from network node 404-2. In the first full-duplex scenario 400 in Figure 4A, full-duplex is enabled for UE1 402 but not for network nodes 404-1 and 404-2. The second full-duplex scenario 410 shown in Figure 4B includes two UEs, indicated as UE1 402-1 and UE2 402-2, and a network node 404, where UE1 402-1 receives downlink transmissions from network node 404 and UE2 402-2 transmits 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. A third full-duplex scenario 420, including UE1 402 and network node 404, is shown in Figure 4C, where UE1 402 receives downlink transmissions from network node 404 and UE1 402 sends 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.

[0076]

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

[0077]

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

[0078]

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

[0079]

[0092] Figure 6 shows an example of a full-duplex slot configuration 600 according to the present disclosure. In some examples, UE 120 may be configured with a first configuration 602. In some examples, the first configuration 602 may represent a first slot format pattern (sometimes called a time-division duplex (TDD) pattern) associated with half-duplex or full-duplex mode. The first slot format pattern may include a certain number of downlink slots (e.g., three downlink slots 604a, 604b, and 604c as shown), a certain number of flexible slots (not shown), and / or a certain number of uplink slots (e.g., one uplink slot 606 as shown). The first slot format pattern may be repeated over time. In some examples, network node 110 may indicate the first slot format pattern to UE 120 using one or more slot format indicators. Slot format indicators for slots may, among other examples, indicate whether the slot is an uplink slot, a downlink slot, or a flexible slot.

[0080]

[0093] Network node 110 may send an indication (e.g., an RRC message, a MAC control element (MAC-CE), or DCI) to UE 120 to switch from the first configuration 602 to the second configuration 608. Alternatively, UE 120 may indicate to network node 110 that UE 120 is switching from the first configuration 602 to the second configuration 608. The second configuration 608 may represent a second slot format pattern that repeats over time, similar to the first slot format pattern. In any of the examples described above, UE 120 may switch from the first configuration 602 to the second configuration 608 over a period of time (e.g., a number of symbols and / or a number of hours) based on, in response to, or otherwise associated with, an indication received from network node 110 (e.g., before switching back to the first configuration 602). During that time period, UE120 may communicate using a second slot format pattern, and then, after the end of the time period, may revert to using the first slot format pattern. The period may be indicated by the network node 110 (for example, in an instruction to switch from the first configuration 602 to the second configuration 608, as described above) and / or may be associated with it in response to or otherwise based on programmed and / or otherwise pre-configured rules. For example, the rules may be based at least in part on a table (for example, defined in the 3GPP specification and / or another wireless communication standard) that associates different subcarrier intervals (SCSs) and / or numerology (e.g., represented by μ and associated with the corresponding SCS) with corresponding time periods for switching configurations.

[0081]

[0094] The second slot format pattern may include two SBFD slots instead of the downlink slots in the first slot format pattern. In Example 600, the second slot format pattern includes a downlink slot 610 and an uplink slot 618. In some examples, each SBFD slot includes a sub-slot for downlink (e.g., a portion or subband of the frequency allocated for use by network node 110 and UE120) (e.g., sub-slots 612a, 612b, 612c, and 612d, as shown) and a sub-slot for uplink (e.g., sub-slots 614a and 614b, as shown). Thus, UE120 may operate using the second slot format pattern to transmit uplink communications in earlier slots (e.g., the second slot in the sequence, shown as a partial uplink (UL) slot 614a) compared to using the first slot format pattern (e.g., the fourth slot in the sequence, shown as UL slot 606). Other examples may include additional or alternative variations. For example, a second configuration 608 may represent an SBFD slot instead of what was an uplink slot in the first configuration 602 (e.g., UL slot 606). In another example, a second configuration 608 may represent a downlink slot or an uplink slot instead of what was an SBFD slot in the first configuration 602 (not shown in Figure 6). In yet another example, a second configuration 608 may represent a downlink slot or an uplink slot instead of what was an uplink slot or a downlink slot, respectively, in the first configuration 602. "SBFD slot" may refer to a slot in which the SBFD format is used. The SBFD format may include a slot format that supports full-duplex communication (e.g., for both uplink and downlink communication), where one or more frequencies used for the uplink portion of the slot are separated by a guard band from one or more frequencies used for the downlink portion of the slot.

[0082]

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

[0083]

[0096] 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 the multiple downlink portions by their respective guard bands (as shown, for example, in Figure 6). In some examples, the SBFD format may include multiple uplink portions and a single downlink portion separated from the multiple uplink portions by their respective guard bands. In some examples, the SBFD format may include multiple uplink portions and multiple downlink portions, each uplink portion being separated from the downlink portions by a guard band. In some examples, operating in SBFD mode may include activating or using full-duplex mode in one or more slots based on, in response to, or otherwise associated with, one or more slots having the SBFD format. A slot may support SBFD mode if the uplink bandwidth portion (BWP) and downlink BWP are permitted to be active simultaneously in the slot in an SBFD manner (e.g., using guard band isolation), or are already active simultaneously.

[0084]

[0097] By switching from the first configuration 602 to the second configuration 608, network nodes 110 and UE 120 may experience improved communication quality and / or reliability. For example, network nodes 110 and UE 120 may experience increased throughput (e.g., by using full-duplex mode), reduced latency (e.g., UE 120 may be able to transmit uplink and / or downlink communications faster by using the second configuration 608 instead of the first configuration 602), and increased network resource utilization (e.g., by using both downlink BWP and uplink BWP simultaneously instead of downlink BWP or uplink BWP alone). While some embodiments are described herein with respect to slot-level granularity, as shown in Figure 6, other granularities such as sub-slot-level granularity or symbol-level granularity may be used, among other examples.

[0085]

[0098] Figure 7 shows an example of full-duplex operation 700 of a network node according to the present disclosure. As shown in Figure 7, the network node 110 may be associated with a plurality of TRPs, indicated as TRP1 705 and TRP2 710. In the first operation 715, the network node 110 may operate in full-duplex mode. For example, the network node 110 may transmit and receive communications simultaneously (e.g., via a plurality of TRPs).

[0086]

[0099] As described elsewhere in this specification, a network node 110 operating in full-duplex mode may experience self-interference. For example, a downlink transmission from network node 110 may self-interfere with an uplink transmission to network node 110. This can be caused by a variety of factors, including higher transmit power for downlink transmissions (compared to uplink transmissions) and / or radio frequency bleeding, among other examples. Therefore, to improve spatial isolation, when operating in full-duplex mode, network node 110 may use TRP1 705 for the downlink signal and a second TRP2 710 for the uplink signal. For example, TRP1 705 and TRP2 710 may be spatially separated from each other, thereby reducing the possibility of a downlink transmission from TRP1 705 interfering with an uplink transmission to TRP2 710 (for example, when the downlink and uplink transmissions overlap at least partially 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 the self-interference associated with full-duplex operation. Therefore, while network node 110 is operating in full-duplex mode, TRP1 705 may be unavailable for uplink operation, and TRP2 710 may be unavailable for downlink operation.

[0087]

[0100] As shown in Figure 7, network node 110 can communicate with UE1 (e.g., UE120), UE2 (e.g., UE120), and UE3 (e.g., UE120). UE1, UE2, and UE3 can each operate in non-full-duplex mode (e.g., half-duplex mode). In some cases, the UEs (e.g., UE1, UE2, and / or UE3) may experience insufficient performance in a given communication direction when network node 110 is operating in full-duplex mode due to a given TRP being unavailable for uplink or downlink communication. For example, the serving TRP for UE1 (e.g., for downlink and uplink) may be TRP1 705. UE1 may not support or be able to have multiple active TCI states or beams. If an active TCI state or beam associated with UE1 (e.g., for uplink communication) is associated with a spatial direction toward TRP1 705, UE1 may be unable to transmit uplink communication during the full-duplex time interval (e.g., because TRP1 705 is unavailable for uplink operation and UE1 cannot support additional active beams or TCI states associated with TRP2 710). Additionally or alternatively, the link between UE1 and TRP2 710 may be associated with poor radio conditions (e.g., high path loss), resulting in poor performance of uplink communication transmitted by UE1 to TRP2 710.

[0088]

[0101] As another example, UE3 may be associated with insufficient performance for downlink communication during a full-duplex time interval. For example, the serving TRP for UE3 (e.g., for downlink and uplink) might be TRP2 710. UE3 may not support, or be unable to support, having multiple active TCI states or beams. If the active TCI states or beams associated with UE3 (e.g., for downlink communication) are associated in a spatial direction toward TRP2 710, UE3 may not receive downlink communication during a full-duplex time interval (e.g., because TRP2 710 is unavailable for downlink operation and UE3 cannot support additional active beams or TCI states associated with TRP1 705). Additionally or alternatively, the link between UE3 and TRP1 705 may be associated with poor radio conditions (e.g., high path loss), resulting in poor performance of downlink communication transmitted to UE3 by TRP1 705.

[0089]

[0102] For example, UE1 and / or UE3 may need to switch TCI states for uplink and downlink communications during a full-duplex time interval. This is associated with a significant signaling overhead associated with network node 110 indicating the new TCI state(s) to be used by UE1 and / or UE3. Furthermore, there may be delays (e.g., associated with the application and / or processing time of the TCI state or beam indication) before UE1 and / or UE3 can apply the new TCI state(s). As a result, UE1 and / or UE3 may not be able to switch to the new TCI state(s) before the next full-duplex time interval and / or before the next scheduled communications.

[0090]

[0103] In some cases, a UE (e.g., UE1 or UE3) may rely on network node 110 to refrain from scheduling communications in communication directions associated with insufficient performance during a full-duplex time interval (e.g., UE1 may rely on network node 110 to refrain from scheduling uplink communications for UE1, and UE3 may rely on network node 110 to refrain from scheduling downlink communications for UE3). However, relying on network node 110 for scheduling decisions may not be feasible or reliable in some situations. For example, some communications may be periodic and / or semi-persistent (e.g., occurring every X slot, symbol, or millisecond). The periodicity of these communications may not be consistent with the slot format periodicity, resulting in some of the periodic and / or semi-persistent communications being scheduled to occur during a full-duplex time interval. Furthermore, the full-duplex slot format may be dynamically configured for the UE, resulting in periodic and / or semi-persistent communications that would otherwise occur during a non-full-duplex time interval being scheduled to occur during a full-duplex time interval.

[0091]

[0104] As another example, a communication may be associated with one or more iterations. For example, PDSCH communication, PDCCH communication, PUSCH communication, and / or Physical Uplink Control Channel (PUCCH) communication may be associated with one or more iterations. A communication may be scheduled during a non-full-duplex time interval, but the iterations of the communication may occur during a full-duplex time interval. Attempting to restrict iterations from occurring during a full-duplex time interval may be associated with a high level of complexity and / or may limit the flexibility in scheduling communications associated with iterations. As another example, a single DCI communication may schedule multiple communications (e.g., different transport blocks). One or more of these communications may be scheduled during a non-full-duplex time interval, but one or more other communications may occur during a full-duplex time interval. Attempting to restrict communications scheduled by a single DCI communication from occurring during a full-duplex time interval may be associated with a high level of complexity and / or may limit the flexibility in scheduling multiple communications using a single DCI communication.

[0092]

[0105] The UE may not be aware of the communication direction that may be associated with the UE's poor performance during a full-duplex time interval. Therefore, if the communication direction of a scheduled communication (e.g., periodic communication, communication repetition, communication from multiple communications scheduled by a single DCI, or another communication) is associated with the UE's poor performance during a full-duplex time interval, the performance of the UE and / or the communication may be impaired. For example, the UE may consume resources (e.g., power resources, processing resources, and / or network resources) by attempting to send or receive communication (e.g., associated with a given communication direction) to or from the antenna and / or TRP of network node 110 that is unavailable for a given communication direction during a full-duplex time interval.

[0093]

[0106] Various embodiments generally relate to unauthorized communication directions for full-duplex time intervals. Some embodiments relate more specifically to defining permitted and / or unauthorized communication directions for full-duplex time intervals (e.g., for slots and / or symbols associated with full-duplex operation) for the UE. In some embodiments, a network node may send an indication to the UE of a communication direction (and / or channel and / or reference signal) that will be disabled or dropped (e.g., not received or transmitted) during a slot or symbol associated with full-duplex operation at the network node. The UE may transmit or receive communications that are in an permitted communication direction (e.g., not in an unauthorized communication direction) during a full-duplex time interval. In some embodiments, the UE may refrain from transmitting or receiving communications that are in an unauthorized communication direction during a full-duplex time interval (e.g., may drop them).

[0094]

[0107] Certain aspects of the subject matter described herein may be implemented to achieve one or more of the following potential benefits. In some examples, the techniques described may be used to clarify how a full-duplex time interval should be utilized by a UE when a network node is operating in full-duplex mode (e.g., using uncollated antennas and / or TRPs). For example, during a full-duplex time interval, a UE may transmit or receive communications in permitted communication directions and / or drop communications in unauthorized communication directions. This may save resources (e.g., power resources, processing resources, and / or network resources) that the UE would otherwise have used by attempting to transmit or receive communications in unauthorized communication directions (e.g., to or from antennas and / or TRPs of a network node that are unavailable in unauthorized communication directions during a full-duplex time interval).

[0095]

[0108] In some embodiments, feedback behavior can be defined for dropped communications associated with unauthorized communication directions. For example, if a UE does not receive downlink communications (e.g., because the downlink is an unauthorized communication direction), the UE may refrain from sending HARQ feedback for downlink communications. Thus, the UE may save power resources, processing resources, and / or network resources that would otherwise have been used by a UE that sent HARQ feedback for downlink communications, knowing that the network node has already not sent any such communications to the UE.

[0096]

[0109] In some embodiments, indications of unauthorized communication directions may be associated with a given CORESET pool index value. For example, a network node may send and a UE may receive an indication that communication associated with a given communication direction and a given CORESET pool index value is not permitted, disabled, and / or should be dropped during a full-duplex time interval. This can allow for improved control and / or flexibility in indicating unauthorized communication directions (and / or permitted communication directions) in multi-TRP and / or mDCI scenarios. In some examples, a network node may send and a UE may receive an indication of one or more unauthorized channels and / or one or more unauthorized signal types during a full-duplex time interval, rather than indicating that a downlink or uplink is disabled during the full-duplex time interval. This can give a network node additional flexibility to permit some communication (e.g., higher-priority communication) in what would otherwise be a completely unauthorized communication direction.

[0097]

[0110] Figure 8 is an example diagram relating to operation 800 associated with an unpermitted communication direction for a full-duplex time interval, as described herein. As shown in Figure 8, one or more network nodes 110 (e.g., base stations, CUs, DUs, and / or RUs) may communicate with a UE 120. In some embodiments, the network node 110 and the UE 120 may be part of a wireless network (e.g., wireless network 100). The UE 120 and the network node 110 may establish a wireless connection prior to the operation shown in Figure 8. In some embodiments, the 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 not be co-located (e.g., they may be located in different physical locations and / or separated by a certain distance).

[0098]

[0111] In the first operation 805, UE 120 may transmit a capability report, and network node 110 may receive a capability report. UE 120 may transmit a capability report via UE capability signaling, UE assistance information (UAI) communication, uplink control information communication, RRC communication, PUSCH, and / or PUCCH, among other examples. A capability report may indicate UE support for one or more operations described herein. For example, a capability report may indicate whether UE 120 supports receiving indications for unauthorized (and / or permitted) communication directions during a full-duplex time interval.

[0099]

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

[0100]

[0113] As used herein, "selectively" performing an action means either performing the action or refraining from performing the action. For example, selectively performing an action based on, in response to, or in association with, whether a condition is met means that the action is performed if the condition is met and not performed if the condition is not met (or vice versa). Thus, selectively performing an action may include determining whether to perform the action, and then, based on, in response to, or otherwise in association with, either performing the action or refraining from performing the action.

[0101]

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

[0102]

[0115] As used herein, “full duplex” may refer to SBFD, in-band full duplex (e.g., having partially or completely overlapping frequency domain resources), and / or other full duplex types or modes. “Time interval” may refer to a slot, OFDM symbol, minislot (e.g., one or more symbols within a slot), and / or another time interval. For example, “full duplex time interval” may refer to an SBFD slot, an SBFD symbol, an in-band full duplex slot, and / or an in-band full duplex symbol, among other examples.

[0103]

[0116] Network node 110 may configure UE 120 in accordance with capability reports. For example, network node 110 may configure or trigger UE 120 to perform one or more operations in response to, or otherwise in association with, a capability report indicating that UE 120 supports one or more operations. For example, network node 110 may indicate an unauthorized communication direction for a full-duplex slot in response to, or otherwise in association with, a capability report indicating that UE 120 supports such indication and / or that UE 120 supports identifying full-duplex time intervals.

[0104]

[0117] In the second operation 810, the network node 110 may transmit configuration information, and the UE 120 may receive configuration information. In some embodiments, the UE 120 may receive configuration information via one or more of the following, among other examples: system information signaling, RRC signaling, one or more MAC-CEs, and / or DCI. In some embodiments, the configuration information may include indications of one or more configuration parameters for selection by the UE 120, and / or explicit configuration information for the UE 120 to use to configure itself.

[0105]

[0118] In some embodiments, configuration information may indicate that UE120 will receive indications for unauthorized communication directions during a full-duplex time interval. A full-duplex time interval may be a time interval in which the network node 110 is operating in full-duplex mode, as described in more detail elsewhere in this specification. An unauthorized communication direction may be a communication direction (e.g., uplink or downlink) from which UE120 will drop communication. As used herein, “to drop” or “dropping” communication may mean that a device (e.g., UE120) refrains from sending or receiving communication. In some embodiments, configuration information may indicate that UE120 will drop communications associated with unauthorized communication directions that, in the time domain, at least partially overlap with a full-duplex time interval. In some embodiments, configuration information may indicate that UE120 will drop communications associated with unauthorized communication directions that, in the time domain, are entirely contained within a full-duplex time interval.

[0106]

[0119] In some embodiments, configuration information may indicate that one or more full-duplex time intervals should be used by network node 110 and / or UE 120. For example, configuration information may indicate that full-duplex operation is enabled for network node 110. Full-duplex operation performed by network node 110 may include subband 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 second TRP and / or second antenna panel to transmit downlink signals while simultaneously using a first TRP and / or first antenna panel to receive uplink signals.

[0107]

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

[0108]

[0121] In some embodiments, configuration information may include indications of unauthorized communication directions associated with one or more full-duplex time intervals. For example, an indication of an unauthorized communication direction may be associated with either an unauthorized uplink signal and channel or a unauthorized downlink signal and channel during one or more full-duplex time intervals. The unauthorized communication direction may be either uplink or downlink. For example, an unauthorized communication direction may be associated with either a downlink channel and / or signal, or an uplink channel and / or signal, that is disabled or dropped during a full-duplex time interval.

[0109]

[0122] In some embodiments, an indication of an unauthorized communication direction may be an explicit indication. For example, an indication of an unauthorized communication direction may include an indication of a communication direction (e.g., uplink or downlink) that should not be used by UE120 during a full-duplex time interval. In another example, an indication of an unauthorized communication direction may be an implicit indication. For example, an indication of an unauthorized communication direction may include an indication of an authorized communication direction during a full-duplex time interval. Since there can only be two communication directions associated with the network node 110 (e.g., uplink or downlink), UE120 may determine an unauthorized communication direction based on the indication of an authorized communication direction, either in response or in other related ways. For example, if the indicated authorized communication direction is an uplink, UE120 may determine that the unauthorized communication direction for a full-duplex time interval is a downlink. In an example where an indication of an unauthorized communication direction is an explicit indication, UE120 may determine the permitted communication direction for a full-duplex time interval in a similar manner. Indications of unauthorized communication directions are described in more detail elsewhere in this specification.

[0110]

[0123] In some embodiments, configuration information may indicate one or more TCI states. For example, for a given TCI state, configuration information may indicate (e.g., via a TCI state information element) TCI state identification information (e.g., tci-StateID), QCL type (e.g., qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, or qcl-TypeD), cell identification information (e.g., ServCellIndex), bandwidth partial identification information (e.g., bwp-Id), and / or reference signal identification information (e.g., NZP-CSI-RS-ResourceId or SSB-Index). One or more TCI states may include integrated TCI states (e.g., uplink TCI states and downlink TCI states, or joint uplink and downlink TCI states). For example, the TCI state may indicate the directivity or characteristics of a beam, such as one or more pseudo-collocation (QCL) properties of a downlink beam. QCL properties may include, among other examples, Doppler shift, Doppler spread, mean delay, delay spread, or spatial receive parameters. For example, UE120 may receive indications (e.g., beam indications, MAC-CE communications, and / or DCI communications) to use the TCI state (e.g., integrated TCI state) for a given TRP of network node 110.

[0111]

[0124] The UE120 may be configured based at least in part on configuration information. In some embodiments, the UE120 may be configured to perform one or more operations described herein based at least in part on configuration information.

[0112]

[0125] In the third operation 815, the network node 110 may transmit and the UE 120 may receive one or more full-duplex time interval indications. In some embodiments, the third operation 815 may be performed as part of the second operation 810 (for example, one or more full-duplex time interval indications may be included in the configuration information as described above). In other embodiments, the third operation 815 and the second operation 810 may be separate operations. In some embodiments, the UE 120 may receive a TDD pattern indicating a slot format pattern. The slot pattern may indicate one or more full-duplex slots. The slot format pattern may repeat over time. For example, the UE 120 may receive one or more full-duplex time interval indications via the slot format pattern in a manner similar to that described with respect to Figure 6. A slot is described above as an example of a time interval, and the UE 120 may receive other full-duplex time interval indications in a similar manner.

[0113]

[0126] In some embodiments, the network node 110 may transmit and the UE 120 may receive an indication to switch to a slot format pattern that includes full-duplex slots. For example, the network node 110 may transmit and the UE 120 may receive a communication (e.g., an RRC communication, a MAC-CE communication, and / or a DCI communication) indicating that the UE 120 should switch from a first slot format pattern (e.g., one that does not include full-duplex slots) to a second slot format pattern (e.g., one that includes full-duplex slots). The UE 120 may identify one or more full-duplex time intervals based on, in response to, or otherwise associated with, a pattern (e.g., a slot format pattern). In other words, the UE 120 may identify one or more time intervals in which the network node 110 is operating in full-duplex mode.

[0114]

[0127] In some embodiments, network node 110 may determine the unauthorized communication directions (and / or channels(s) or signal types(s)) for the full-duplex time interval for UE120. For example, network node 110 may determine the serving TRP(s) associated with UE120. The serving TRP(s) may be the TRP(s) that UE120 uses to communicate with network node 110. Network node 110 may determine the communication directions used for each TRP when network node 110 is operating in full-duplex mode. For example, network node 110 may be associated with a first TRP and a second TRP. When operating in full-duplex mode, network node 110 may determine that the first TRP is used for uplink and the second TRP is used for downlink. Network node 110 may determine that the serving TRP of UE120 is the first TRP. In addition, network node 110 may determine that UE 120 is not capable of supporting multiple active TCI states (for example, as indicated by the capability report transmitted by UE 120 in the first operation 805), and / or that 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 the threshold. Thus, network node 110 may determine that UE 120 is not capable of receiving downlink communication from the second TRP, and / or that the link between UE 120 and the second TRP is not suitable for downlink transmission. Thus, network node 110 may determine that downlink is not permitted for UE 120 during the full-duplex time interval (for example, UE 120 may be allowed to continue transmitting uplink communication to the first TRP).

[0115]

[0128] In some embodiments, such as in a multi-TRP scenario, the network node 110 may determine the unauthorized communication directions for each TRP. For example, the network node 110 may determine that during a full-duplex time interval, the downlink should be disabled for the first TRP and the uplink should be disabled for the second TRP. The network node 110 may indicate the disabled communication directions for each CORESET pool index value in order to disable the communication directions for each TRP during a full-duplex time interval, as will be described in more detail elsewhere in this specification.

[0116]

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

[0117]

[0130] An indication of an unauthorized communication direction may be associated with either an unauthorized uplink signal and channel or a unauthorized downlink signal and channel during one or more full-duplex time intervals. That is, an unauthorized communication direction may be an uplink direction (e.g., an uplink signal and channel) or a downlink direction (e.g., a downlink signal and channel), and an indication of an unauthorized communication direction may indicate an unauthorized communication direction. As described elsewhere in this specification, an indication of an unauthorized communication direction may be an explicit or implicit indication. For example, an indication of an unauthorized communication direction may include an indication of a communication direction (e.g., uplink or downlink) that should not be used by the UE120 during a full-duplex time interval. As another example, an indication of an unauthorized communication direction may include an indication of an authorized communication direction for a full-duplex time interval.

[0118]

[0131] In some embodiments, an unauthorized communication direction may apply to all channels and / or signal types associated with that unauthorized communication direction. For example, UE120 may drop all communications and / or signals in an unauthorized communication direction during a full-duplex time interval. In other embodiments, an unauthorized communication direction may apply to several channels and / or signal types. For example, one or more channels and / or signal types associated with a communication direction may be disabled or dropped during a full-duplex time interval. In some embodiments, network node 110 may transmit and UE120 may receive indications of one or more channels and / or signal types associated with an unauthorized communication direction.

[0119]

[0132] In some embodiments, an indication of an unauthorized communication direction may be an indication of one or more channels and / or one or more signal types that are not permitted during a full-duplex time interval. For example, rather than indicating that a downlink or uplink is disabled during a full-duplex time interval, network node 110 may transmit and UE 120 may receive an indication of one or more unauthorized channels and / or one or more unauthorized signal types during a full-duplex time interval. This may provide network node 110 with additional flexibility to permit some communications (e.g., higher-priority communications) in a communication direction that would otherwise be completely unauthorized. For example, UE 120 may transmit higher-priority communications (e.g., in a communication direction that would otherwise be unauthorized), and network node 110 (e.g., TRP of network node 110) may perform interference mitigation to receive higher-priority communications.

[0120]

[0133] In some embodiments, network node 110 may transmit and UE 120 may receive an indication that one or more channels and / or signal types in an unauthorized communication direction should be disabled or dropped by UE 120 during a full-duplex time interval. For example, one or more channels may include PUSCH or PUCCH (for example, if the unauthorized communication direction is an uplink). As another example, one or more channels may include PDSCH or PDCCH (for example, if the unauthorized communication direction is a downlink).

[0121]

[0134] One or more signal types may include semi-persistent and / or periodic signals. For example, one or more signal types may include, among other examples, semi-persistent scheduling (SPS) signals, configured permission (CG) signals, semi-persistent and / or periodic sounding reference signals (SRSs), semi-persistent and / or periodic channel status information (CSI) communicated via PUCCH, and / or semi-persistent and / or periodic CSI reference signals (CSI-RSs). Additionally or alternatively, one or more signal types may include repetitions. For example, repetitions of PDSCH, PDCCH, PUCCH, and / or PUSCH communications in an unauthorized communication direction may be invalidated 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 sent again to UE120 later and / or may have already been sent to UE120. Therefore, these signal types may be more resistant to being dropped on a given occasion, since the same communication may be transmitted to the UE120 on another occasion. Additionally or alternatively, one or more signal types may include signals associated with communications scheduled by a single DCI communication that schedules multiple communications. For example, one or more signal types may include signals associated with PDSCH or PUSCH signals scheduled by a single DCI that schedules multiple PDSCH or PUSCH signals. The channels and signal types described are provided as examples. Other channels and / or signal types may be disabled for unauthorized communication directions in a manner similar to that described herein.

[0122]

[0135] In some embodiments, an indication of an unauthorized communication direction may include an indication of a CORESET pool index value associated with the indication of an unauthorized communication direction. For example, a channel and / or signal associated with a given CORESET pool index value may be disabled or dropped in an unauthorized communication direction during a full-duplex time interval. For example, an indication of an unauthorized communication direction may include, among other examples, an indication that a downlink channel and / or signal associated with CORESET pool index 0 is disabled or not permitted, an uplink channel and / or signal associated with CORESET pool index 0 is disabled or not permitted, a downlink channel and / or signal associated with CORESET pool index 1 is disabled or not permitted, and / or an uplink channel and / or signal associated with CORESET pool index 1 is disabled or not permitted. For example, if two TRPs of network node 110 are used for full-duplex operation, during a full-duplex time interval, uplink transmissions to one of the TRPs and downlink transmissions from the other TRP may not be possible or permitted. Therefore, multi-DCI multi-TRP operation may not be possible during a full-duplex time interval. Network node 110 may indicate the unallowed communication directions for each CORESET pool index value to indicate which TRP should be associated with which communication direction.

[0123]

[0136] For example, UE120 may communicate via multiple TRPs (e.g., TRP1 and TRP2) during a non-full-duplex time interval (e.g., using multiple TCI states corresponding to each TRP). TRP1 may be associated with a first CORESET pool index value, and TRP2 may be associated with a second CORESET pool index value. In some embodiments, network node 110 may send and UE120 may receive a first unauthorized communication direction indication for communication associated with the first CORESET pool index value and a second unauthorized communication direction indication for communication associated with the second CORESET pool index value. For example, when network node 110 is operating in full-duplex mode, it may use TRP1 for uplink operations and TRP2 for downlink operations. Therefore, indication of an unauthorized communication direction may indicate that the downlink is not permitted for a first CORESET pool index value (e.g., for TRP1) and / or that the uplink is not permitted for a second CORESET pool index value (e.g., for TRP2). This may provide network node 110 with additional flexibility in indicating which TRP is associated with which communication direction during a full-duplex time interval in a scenario where network node 110 is communicating using multi-TRP operation.

[0124]

[0137] In some embodiments, indications for unauthorized communication directions may include indications for TCI states associated with full-duplex operation and unauthorized communication directions, where the TCI state indicates that the unauthorized communication direction is not permitted for one or more full-duplex time intervals. For example, UE120 may support TCI states associated with different duplex states of network node 110. For example, a TCI state may include an indication of the associated duplex type or duplex mode. UE120 may apply the TCI state during the time interval associated with the duplex type or duplex mode associated with the TCI state. For example, UE120 may apply a full-duplex TCI state during a full-duplex time interval and a non-full-duplex TCI state during a non-full-duplex time interval. This can reduce the signaling overhead associated with switching the TCI states used by UE120 when a network node changes its duplex state or duplex type. In some examples, the processing time associated with receiving beam indications (e.g., receiving TCI state indications) can be reduced or eliminated, thus reducing the amount of time associated with UE120 switching to a TCI state associated with a given duplex state or duplex type. Configuring a 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 allowing network nodes to use spatially separated antennas and / or TRPs for their respective communication directions, while also reducing the signaling overhead associated with network nodes indicating to UE120 to use a TCI state that enables spatial separation.

[0125]

[0138] In some embodiments, network node 110 may transmit and UE 120 may receive communications (e.g., MAC-CE communications and / or DCI communications) that activate a TCI state associated with full-duplex. A TCI state may be associated with a communication direction (e.g., uplink or downlink). A TCI state may include an indication that the communication direction is not permitted for one or more full-duplex time intervals. For example, a TCI state may include a "null" indication or a "disabled" indication. In other words, a TCI state may include a flag or other indication that the TCI state should not be used for communication (e.g., that the communication direction associated with the TCI state is disabled or not permitted during the full-duplex time interval). For example, network node 110 may transmit and UE 120 may receive an indication of a first integrated TCI state associated with a non-full-duplex time interval (e.g., downlink TCI state 1 and uplink TCI state 1). Network node 110 may transmit and UE 120 may receive an indication of a second integrated TCI state associated with a full-duplex time interval. The second integrated TCI state may include a “null” TCI state indicating that a given communication direction is disabled for the duration of the full-duplex time interval. For example, the second integrated TCI state may include a downlink TCI state 1 and a “null” uplink TCI state indicating that the uplink is not permitted or disabled for the duration of the full-duplex time interval.

[0126]

[0139] In some embodiments, TCI states associated with full-duplex can be associated with a given CORESET pool index value. For example, network node 110 may transmit and UE 120 may receive an indication of a “null” TCI state associated with a given communication direction and associated with a given CORESET pool index value (e.g., associated with a full-duplex time interval). For example, for a first CORESET pool index value, the beam indication may indicate that a first integrated TCI state (e.g., downlink TCI state 1 and uplink TCI state 1) should be used for a non-full-duplex time interval, and a second integrated TCI state (e.g., downlink TCI state 1 and “null” uplink TCI state) should be used for a full-duplex time interval. For a second CORESET pool index value, beam indication may indicate that a third integrated TCI state (e.g., downlink TCI state 2 and uplink TCI state 2) should be used for non-full-duplex time intervals, and a fourth integrated TCI state (e.g., "null" downlink TCI state and uplink TCI state 2) should be used for full-duplex time intervals. This may indicate that during full-duplex time intervals, the uplink is not disabled or permitted for the first TRP associated with the first CORESET pool index value, and the downlink is not disabled or permitted for the second TRP associated with the second CORESET pool index value.

[0127]

[0140] In the fifth operation 825, UE120 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., received by UE120 as part of the second operation 810 and / or the third operation 815), UE120 may determine that the current time interval is associated with full duplex. For example, UE120 may determine that the current time interval is a full-duplex slot, a subband full-duplex slot, or another full-duplex time interval.

[0128]

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

[0129]

[0142] In some embodiments, UE120 may determine whether the channels and / or signal types associated with the communication are permissible for a full-duplex time interval. For example, an indication of an unauthorized communication direction may indicate one or more channels and / or one or more signal types that are not permitted or disabled during a full-duplex time interval. UE120 may transmit or receive a communication during the current time interval (e.g., during a full-duplex time interval) depending on whether the communication is associated with channels and / or signal types that are not permitted or disabled during a full-duplex time interval.

[0130]

[0143] In the seventh operation 835, UE120 may drop a communication in accordance with the fact that the communication is in a communication direction that is not permitted during the current time interval (e.g., during a full-duplex time interval). For example, UE120 may identify a communication scheduled or configured to occur during a full-duplex time interval. Based on the fact that the communication is in a communication direction that is not permitted, UE120 may refrain from sending a communication in response to or in association with it (e.g., if the unauthorized communication direction is an uplink) or refrain from receiving a communication (e.g., if the unauthorized communication direction is a downlink). Additionally or alternatively, UE120 may drop a communication in accordance with the fact that the communication is associated with an unauthorized channel and / or an unauthorized signal type during the current time interval (e.g., during a full-duplex time interval). Similarly, network node 110 may drop a communication in accordance with the fact that the communication is in a communication direction that is not permitted during the current time interval (e.g., during a full-duplex time interval). For example, network node 110 may identify a communication scheduled or configured to occur during a full-duplex time interval. Network node 110 may refrain from sending communications in response to or in association with communications in a communication direction that is not permitted (for example, if the unauthorized communication direction is a downlink) or refrain from receiving communications (for example, if the unauthorized communication direction is an uplink).

[0131]

[0144] In some embodiments, a feedback operation is performed for communications (e.g., downlink communications or PDSCH communications) that are dropped by UE120 according to an unapproved communication direction during a full-duplex time interval. The feedback operation may be shown and / or configured as part of a second operation 810. For example, UE120 may support a Hybrid Automatic Retransmission Request (HARQ) feedback codebook transmission. A HARQ feedback codebook transmission may include a feedback message that UE120 should send to network node 110 to provide feedback on, for example, a downlink data transmission (e.g., a transmission associated with a PDSCH).

[0132]

[0145] A UE may consist of different types of codebooks, such as a Type 1 HARQ acknowledgment (ACK) codebook or a Type 2 HARQ ACK codebook. A Type 1 HARQ ACK codebook may be called a semi-static HARQ ACK codebook. For example, a Type 1 HARQ ACK codebook may be associated with a fixed or static size (e.g., composed of network node 110). A Type 2 HARQ ACK codebook may be associated with a dynamic size (e.g., if the size of a Type 2 HARQ ACK codebook is at least partially based on, or otherwise associated with, the scheduling received by UE 120). Typically, if UE120 is configured to send a Type 1 HARQ ACK codebook, UE120 may collect feedback about PDSCH communications that are attempted to be received by UE120 during a feedback window (e.g., k slots) and may send a Type 1 HARQ ACK codebook indicating the feedback (e.g., ACK / NACK feedback) associated with the PDSCH communications that are attempted to be received by UE120 during the feedback window.

[0133]

[0146] In some embodiments, UE120 may refrain from sending HARQ feedback indications associated with downlink communications that are dropped according to an unauthorized communication direction (e.g., dropped as part of operation 7 835). For example, UE120 may not report a HARQ-ACK for a downlink communication (e.g., for a PDSCH). In an example where UE120 is configured to send a type 1 HARQ ACK codebook, UE120 may exclude candidate PDSCH opportunities from the type 1 HARQ ACK codebook associated with a full-duplex time interval. For example, UE120 may send and network node 110 may receive a type 1 HARQ codebook associated with a set of downlink opportunities (e.g., a set of candidate PDSCH opportunities) that include a downlink opportunity corresponding to a downlink communication. The type 1 HARQ codebook may not include an indication for a downlink opportunity corresponding to a dropped downlink communication. For example, candidate PDSCH opportunities from Time Domain Resource Allocation (TDRA) rows that overlap with time domain resources for a full-duplex time interval may be excluded from the Type 1 HARQ codebook (e.g., not included). In an example where an unauthorized communication direction is also associated with a CORESET pool index value, UE120 may exclude candidate PDSCH opportunities associated with the CORESET pool index value from TDRA rows in the Type 1 HARQ codebook for the CORESET pool index value that overlap with time domain resources for a full-duplex time interval. This can reduce the size of the Type 1 HARQ codebook and thereby conserve network resources associated with transmitting the Type 1 HARQ codebook. Network node 110 may determine, in response to or in connection with, that the downlink communication was scheduled or configured to occur during a full-duplex time interval, and in response to or in connection with, an unauthorized communication direction for UE120, that the downlink communication was not successfully received by UE120.

[0134]

[0147] In other embodiments, UE120 may transmit and network node 110 may receive a HARQ feedback indication for downlink communications that are dropped according to an unauthorized communication direction (e.g., dropped as part of operation 7 835). For example, UE120 may transmit a negative ACK (NACK) indication for a downlink communication (e.g., in a Type 1 HARQ codebook or another type of feedback communication). This may indicate to network node 110 that the downlink communication was not successfully received by UE120. Network node 110 may then schedule another transmission of the downlink communication to ensure that UE120 receives the downlink communication, thereby improving the reliability of downlink communications that are dropped according to an unauthorized communication direction.

[0135]

[0148] Figure 9 is an example diagram of an unpermitted communication direction for a full-duplex time interval as described herein. As shown in Figure 9, UE1 (e.g., UE120) and UE2 (e.g., UE120) may be configured with time intervals (e.g., slots or symbols) associated with different duplex types, or may receive indications of such time intervals. 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). UE1 and / or UE2 may receive indications of different types of time intervals in a manner similar to that described in more detail elsewhere in this specification, such as with respect to the second operation 810 and / or the third operation 815.

[0136]

[0149] As an example, network node 110 may be associated with multiple TRPs, such as TRP1 and TRP2. When operating in full-duplex mode, as described elsewhere in this specification, network node 110 may use TRP1 for downlink operations and TRP2 for uplink operations. As shown in Figure 9, UE1 may communicate with network node 110 via TRP1. For example, UE1 may communicate both uplink signals (e.g., during uplink time intervals) and downlink signals (e.g., during downlink time intervals) via TRP1. Similarly, UE2 may communicate with network node 110 via TRP2. For example, UE2 may communicate both uplink signals (e.g., during uplink time intervals) and downlink signals (e.g., during downlink time intervals) via TRP2. In other words, TRP1 may be a serving TRP for UE1, and TRP2 may be a serving TRP for UE2. For example, UE1 may transmit and / or receive signals using TCI states associated with the spatial direction toward TRP1 (e.g., downlink TCI states, uplink TCI states, and / or joint uplink and downlink TCI states). Similarly, UE2 may transmit and / or receive signals using TCI states associated with the spatial direction toward TRP2 (e.g., downlink TCI states, uplink TCI states, and / or joint uplink and downlink TCI states).

[0137]

[0150] In the first operation 905, the uplink may be disabled for UE1 and the downlink may be disabled for UE2 during the full-duplex time interval. For example, UE1 may receive an indication that the uplink is a communication direction that is not permitted for the full-duplex time interval (for example, in the same way as described elsewhere in this specification). For example, because TRP1 is the serving TRP for UE1, and because network node 110 uses TRP1 for downlink operation (for example, downlink operation only) when operating in full-duplex mode, network node 110 may send and UE1 receive an indication that the uplink channel and / or signal is disabled or not permitted during the full-duplex time interval.

[0138]

[0151] Furthermore, UE2 may receive an indication that the downlink is an unpermitted communication direction during the full-duplex time interval (for example, in the same manner as described elsewhere in this specification). For example, since TRP2 is the serving TRP of UE2 and network node 110 uses TRP2 for uplink operation (e.g., uplink operation only) when operating in full-duplex mode, network node 110 may send and UE2 may receive an indication that the downlink channel and / or signal is disabled or unpermitted during the full-duplex time interval.

[0139]

[0152] For example, as shown in Figure 9, UE1 may receive downlink communications and drop uplink communications during a full-duplex time interval. UE2 may transmit uplink communications and drop downlink communications during a full-duplex time interval. This ensures that UE1 does not consume resources (e.g., processing resources, battery resources, and / or network resources) associated with transmitting uplink communications to TRP1 when TRP1 is used solely for downlink operations by network node 110. Similarly, this ensures that UE2 does not consume resources (e.g., processing resources, battery resources, and / or network resources) associated with attempting to receive downlink communications from TRP2 (e.g., monitoring downlink communications) when TRP2 is used solely for uplink operations by network node 110.

[0140]

[0153] Figure 10 is an example diagram of an unpermitted communication direction for a full-duplex time interval as described herein. As shown in Figure 10, UE1 (e.g., UE120) may consist of or receive indications of time intervals (e.g., 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). UE1 may receive indications of different types of time intervals in a manner similar to that described in more detail elsewhere in this specification, such as in relation to the second operation 810 and / or the third operation 815.

[0141]

[0154] As an example, network node 110 may be associated with multiple TRPs, such as TRP1 and TRP2. As described elsewhere in this specification, when operating in full-duplex mode, network node 110 may use TRP1 for downlink operations and TRP2 for uplink operations. As shown in Figure 10, UE1 may communicate using multi-TRP operation. For example, UE1 may receive downlink communications from both TRP1 and TRP2 during a downlink time interval. UE1 may transmit uplink communications to both TRP1 and TRP2 during an uplink time interval.

[0142]

[0155] In the first operation 1005, the uplink may be disabled for the CORESET pool index and / or TCI state associated with TRP1 during the full-duplex time interval, and the downlink may be disabled for the CORESET pool index and / or TCI state associated with TRP2. For example, UE1 may receive an indication that the uplink is disabled for the first CORESET pool index value and / or first TCI state (e.g., associated with TRP1) during the full-duplex time interval (e.g., in the same manner as described elsewhere in this specification). For example, since network node 110 uses TRP1 for downlink operation (e.g., downlink operation only) when operating in full-duplex mode, network node 110 may send and UE1 receive an indication that the uplink channel and / or signal is disabled or not permitted for the full-duplex time interval for TRP1 (e.g., by indicating the first CORESET pool index value and / or the uplink "null" TCI state associated with TRP1).

[0143]

[0156] Similarly, UE1 may receive an indication that the downlink is disabled for a second CORESET pool index value and / or a second TCI state (e.g., associated with TRP2) during a full-duplex time interval (e.g., in a similar manner to those described elsewhere in this specification). For example, since network node 110 uses TRP2 for uplink operations (e.g., uplink operations only) when operating in full-duplex mode, network node 110 may transmit an indication (e.g., by indicating a second CORESET pool index value and / or a downlink "null" TCI state associated with TRP2) that the downlink channel and / or signal is disabled or not permitted during a full-duplex time interval for TRP2, and UE1 may receive this indication.

[0144]

[0157] Figure 11 is a flowchart of an exemplary process 1100 performed by a UE supporting, for example, an unauthorized communication direction for a full-duplex time interval, as described herein. The exemplary process 1100 is an example in which a UE (e.g., UE120) performs an operation associated with an unauthorized communication direction during a full-duplex time interval.

[0145]

[0158] As shown in Figure 11, in some embodiments, process 1100 may include receiving one or more full-duplex time interval indications from network nodes (block 1110). For example, a UE (using, for example, the communications manager 140 or receiving component 1302 shown in Figure 13) may receive one or more full-duplex time interval indications from network nodes as described above.

[0146]

[0159] As further shown in Figure 11, in some embodiments, process 1100 may include receiving indications from network nodes for unauthorized communication directions associated with one or more full-duplex time intervals (block 1120). For example, a UE may receive indications from network nodes for unauthorized communication directions associated with one or more full-duplex time intervals (for example, by using the communication manager 140 or receiving component 1302 shown in Figure 13), as described above.

[0147]

[0160] As further shown in Figure 11, in some embodiments, process 1100 may include transmitting or receiving communications to and from network nodes in a communication direction that is not a communication direction in which communication is not permitted, during one or more full-duplex time intervals (block 1130). For example, a UE (for example, by using the communications manager 140, or the transmitting component 1304, or the receiving component 1302 shown in Figure 13) may transmit or receive communications to and from network nodes in a communication direction that is not a communication direction in which communication is not permitted, as described above.

[0148]

[0161] Process 1100 may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below or in relation to one or more other processes described elsewhere in this specification.

[0149]

[0162] In the first additional aspect, an indication of an unauthorized communication direction may be associated with either an unauthorized uplink signal and channel or a unauthorized downlink signal and channel during one or more full-duplex time intervals.

[0150]

[0163] In a second additional embodiment, either alone or in combination with the first embodiment, process 1100 may include dropping other communications during a full-duplex time interval or another full-duplex time interval among one or more full-duplex time intervals, on the grounds that the other communications are in an unauthorized communication direction. That is, other communications may be dropped if the UE determines, on the grounds that the other communications are in an unauthorized communication direction, according to an indication of an unauthorized communication direction.

[0151]

[0164] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the other communications may be downlink communications, and process 1100 may include refraining from transmitting Hybrid Automatic Retransmission Request (HARQ) feedback indications associated with the downlink communications.

[0152]

[0165] In a fourth additional aspect, refraining from transmitting HARQ feedback indications associated with downlink communications, either alone or in combination with one or more of the first to third aspects, may include transmitting a Type 1 HARQ codebook associated with a set of downlink opportunities, including a downlink opportunity corresponding to a downlink communications, the Type 1 HARQ codebook not containing indications for downlink opportunities.

[0153]

[0166] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, an unauthorized communication direction may be denied to a CORESET pool index value, a downlink opportunity may be associated with a CORESET pool index value, and a Type 1 HARQ codebook may be associated with a CORESET pool index value.

[0154]

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

[0155]

[0168] In the seventh additional aspect, indications of unauthorized communication directions may be communicated, either alone or in combination with one or more of the first to sixth aspects, via radio resource control signaling or MAC control element signaling.

[0156]

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

[0157]

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

[0158]

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

[0159]

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

[0160]

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

[0161]

[0174] In the 13th additional embodiment, one or more full-duplex time intervals, either alone or in combination with one or more of the first to 12th embodiments, may include at least one of one or more full-duplex slots or one or more full-duplex OFDM symbols.

[0162]

[0175] Figure 11 shows an exemplary block of process 1100, but in some embodiments, process 1100 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those shown in Figure 11. Additionally or alternatively, two or more blocks of process 1100 may be executed in parallel.

[0163]

[0176] Figure 12 is a flowchart of an exemplary process 1200 performed by a network node that supports, for example, an unauthorized communication direction for a full-duplex time interval, as described herein. The exemplary process 1200 is an example in which a network node (e.g., network node 110) performs an operation associated with an unauthorized communication direction during a full-duplex time interval.

[0164]

[0177] As shown in Figure 12, in some embodiments, process 1200 may include transmitting one or more full-duplex time interval indications associated with the UE (block 1210). For example, a network node may transmit one or more full-duplex time interval indications associated with the UE (for example, by using the communication manager 150 or the transmitting component 1404 shown in Figure 14), as described above.

[0165]

[0178] As further shown in Figure 12, in some embodiments, process 1200 may include sending UE-associated indications for unauthorized communication directions associated with one or more full-duplex time intervals (block 1220). For example, a network node may send UE-associated indications for unauthorized communication directions associated with one or more full-duplex time intervals, as described above, (for example, by using the communication manager 150 or the transmit component 1404 shown in Figure 14).

[0166]

[0179] As further shown in Figure 12, in some embodiments, process 1200 may include transmitting or receiving communications for the UE during one of one or more full-duplex time intervals, in accordance with the communication direction not being one in which communications are not permitted (block 1230). For example, a network node (for example, by using the communications manager 150, transmitting component 1404, or receiving component 1402 shown in Figure 14) may transmit or receive communications for the UE during one of one or more full-duplex time intervals, in accordance with the communication direction not being one in which communications are not permitted, as described above.

[0167]

[0180] Process 1200 may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below or in relation to one or more other processes described elsewhere in this specification.

[0168]

[0181] In the first additional aspect, an indication of an unauthorized communication direction may be associated with either an unauthorized uplink signal and channel or a unauthorized downlink signal and channel during one or more full-duplex time intervals.

[0169]

[0182] In a second additional embodiment, either alone or in combination with the first embodiment, process 1200 may include dropping other communications during a full-duplex time interval or another full-duplex time interval among one or more full-duplex time intervals, on the grounds that the other communications are in a communication direction that is not permitted. That is, other communications may be dropped if a network node determines, on the grounds that the other communications are in a communication direction that is not permitted, according to an indication of an unauthorized communication direction.

[0170]

[0183] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the other communications may be downlink communications, and process 1100 may include receiving a type 1 HARQ codebook associated with a set of downlink opportunities, which include downlink opportunities corresponding to the downlink communications, the type 1 HARQ codebook not including indications for downlink opportunities.

[0171]

[0184] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, an unauthorized communication direction may be disallowed for a CORESET pool index value, a downlink opportunity may be associated with a CORESET pool index value, and a Type 1 HARQ codebook may be associated with a CORESET pool index value.

[0172]

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

[0173]

[0186] In the sixth additional aspect, indications of unauthorized communication directions may be communicated via radio resource control signaling or MAC control element signaling, either alone or in combination with one or more of the first to fifth aspects.

[0174]

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

[0175]

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

[0176]

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

[0177]

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

[0178]

[0191] In the 11th additional aspect, one or more full-duplex time intervals, either alone or in combination with one or more of the first to tenth aspects, may be one or more subband full-duplex time intervals.

[0179]

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

[0180]

[0193] Figure 12 shows an exemplary block of process 1200, but in some embodiments, process 1200 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those shown in Figure 12. Additionally or alternatively, two or more blocks of process 1200 may be executed in parallel.

[0181]

[0194] Figure 13 is a diagram of an exemplary apparatus 1300 for wireless communication supporting an unpermitted direction of communication during a full-duplex time interval, as disclosed herein. The apparatus 1300 may be a UE, or a UE may include the apparatus 1300. In some embodiments, the apparatus 1300 includes a receiving component 1302, a transmitting component 1304, and a communications manager 140, which may be communicating with each other (e.g., via one or more buses). As shown, the apparatus 1300 may 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).

[0182]

[0195] In some embodiments, the apparatus 1300 may be configured and / or operable to perform one or more operations described herein with respect to Figures 8 to 10. Additionally or alternatively, the apparatus 1300 may be configured and / or operable to perform one or more processes described herein, such as process 1100 in Figure 11. In some embodiments, the apparatus 1300 may include one or more components of the UE described above with respect to Figure 2.

[0183]

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

[0184]

[0197] The transmitting component 1304 may transmit communications such as reference signals, control information, and / or data communications to the device 1306. In some embodiments, the communications manager 140 may generate communications and transmit the generated communications to the transmitting component 1304 for transmission to the device 1306. In some embodiments, the transmitting component 1304 may perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1306. In some embodiments, the transmitting component 1304 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, and / or memory of the UE described above with respect to Figure 2. In some embodiments, the transmitting component 1304 may be located in the transceiver alongside the receiving component 1302.

[0185]

[0198] The communication manager 140 may receive, or cause the receiving component 1302 to receive, one or more full-duplex time interval indications from the network node. The communication manager 140 may receive, or cause the receiving component 1302 to receive, an indication of an unauthorized communication direction associated with one or more full-duplex time intervals. During one of the one or more full-duplex time intervals, the communication manager 140 may transmit, or cause the transmitting component 1304 to transmit, a communication to or from the network node in a communication direction that is not an unauthorized communication direction, or the communication manager 140 may receive, or cause the receiving component 1302 to receive, a communication. In some embodiments, the communication manager 140 may perform one or more operations as described elsewhere herein as being performed by one or more components of the communication manager 140.

[0186]

[0199] The communication manager 140 may include the controller / processor and memory of the UE described above with respect to Figure 2. In some embodiments, the communication manager 140 includes a set of components, such as the drop component 1308 and / or the decision component 1310, among other examples. Alternatively, the set of components may be separate from the communication manager 140 and distinct. In some embodiments, one or more components of the set of components may be implemented within the controller / processor and memory of the UE described above with respect to Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium that can be executed by the controller or processor to perform the function or operation of that component.

[0187]

[0200] The receiving component 1302 may receive indications for one or more full-duplex time intervals from the network node. The receiving component 1302 may receive indications for unauthorized communication directions associated with one or more full-duplex time intervals from the network node. The transmitting component 1304 may transmit or receive communications to and from the network node during one of the one or more full-duplex time intervals, in accordance with the fact that the communication direction is not an unauthorized communication direction.

[0188]

[0201] The drop component 1308 may drop other communications during a full-duplex time interval or during another full-duplex time interval among one or more full-duplex time intervals, in accordance with the fact that the other communications are in a communication direction in which they are not permitted.

[0189]

[0202] The decision component 1310 may, based on indications of one or more full-duplex time intervals, determine in response to them, or otherwise determine the duplex type associated with the time interval associated therewith.

[0190]

[0203] The quantity and arrangement of components shown in Figure 13 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 13. Furthermore, two or more components shown in Figure 13 may be implemented within a single component, or a single component shown in Figure 13 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 13 may perform one or more functions that are described as being performed by another set of components shown in Figure 13.

[0191]

[0204] Figure 14 is a diagram of an exemplary apparatus 1400 for wireless communication supporting an unpermitted direction of communication during a full-duplex time interval, as disclosed herein. The apparatus 1400 may be a network node, or a network node may include the apparatus 1400. In some embodiments, the apparatus 1400 includes a receiving component 1402, a transmitting component 1404, and a communications manager 150, which may be communicating with each other (e.g., via one or more buses). As shown, the apparatus 1400 may 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).

[0192]

[0205] In some embodiments, the device 1400 may be configured and / or operable to perform one or more operations described herein with respect to Figures 8 to 10. Additionally or alternatively, the device 1400 may be configured and / or operable to perform one or more processes described herein, such as process 1200 in Figure 12. In some embodiments, the device 1400 may include one or more components of the network node described above with respect to Figure 2.

[0193]

[0206] The receiving component 1402 may receive communications such as reference signals, control information, and / or data communications from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400, such as the communications manager 150. In some embodiments, the receiving component 1402 may perform signal processing on the received communications (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) and provide the processed signals to one or more other components. In some embodiments, the receiving component 1402 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, and / or memory of the network nodes described above with respect to Figure 2.

[0194]

[0207] The transmitting component 1404 may transmit communications such as reference signals, control information, and / or data communications to the device 1406. In some embodiments, the communications manager 150 may generate communications and transmit the generated communications to the transmitting component 1404 for transmission to the device 1406. In some embodiments, the transmitting component 1404 may perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1406. In some embodiments, the transmitting component 1404 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, and / or memory of the network nodes described above with respect to Figure 2. In some embodiments, the transmitting component 1404 may be located in the transceiver alongside the receiving component 1402.

[0195]

[0208] The communications manager 150 may transmit or cause the transmitting component 1404 to transmit one or more full-duplex time interval indications associated with the UE. The communications manager 150 may transmit or cause the transmitting component 1404 to transmit UE-associated indications for unauthorized communication directions associated with one or more full-duplex time intervals. During one of the one or more full-duplex time intervals, the communications manager 150 may transmit or cause the transmitting component 1404 to transmit communications for the UE, in accordance with the communication direction not being an unauthorized communication direction, or the communications manager 150 may receive or cause the receiving component 1402 to receive communications. In some embodiments, the communications manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communications manager 150.

[0196]

[0209] The communication manager 150 may include the controller / processor, memory, scheduler, and / or communication unit of the network node described above with respect to Figure 2. In some embodiments, the communication manager 150 includes a set of components such as the drop component 1408 and / or the communication direction determination component 1410. Alternatively, the set of components may be separate from the communication manager 150 and distinct. In some embodiments, one or more components of the set of components may include, and be implemented within, the controller / processor, memory, scheduler, and / or communication unit of the network node described above with respect to Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium that can be executed by the controller or processor to perform the function or operation of that component.

[0197]

[0210] The transmitting component 1404 may transmit indications associated with the UE for one or more full-duplex time intervals. The transmitting component 1404 may transmit indications associated with the UE for unauthorized communication directions associated with one or more full-duplex time intervals. The transmitting component 1404 may transmit or receive communications for the UE during one of the full-duplex time intervals, in accordance with the fact that the communications are in a communication direction that is not an unauthorized communication direction.

[0198]

[0211] The drop component 1408 may drop other communications during a full-duplex time interval or during another full-duplex time interval among one or more full-duplex time intervals, in accordance with the fact that the other communications are in a communication direction in which they are not permitted.

[0199]

[0212] The communication direction determination component 1410 may determine an unauthorized communication direction for the UE. The communication direction determination component 1410 may determine an unauthorized communication direction for the UE based on, in response to, or otherwise associated with, the UE's serving TRP or the antenna configuration of the network node.

[0200]

[0213] The quantity and arrangement of components shown in Figure 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 14. Furthermore, two or more components shown in Figure 14 may be implemented within a single component, or a single component shown in Figure 14 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 14 may perform one or more functions that are described as being performed by another set of components shown in Figure 14.

[0201]

[0214] The following provides an overview of some aspects of this disclosure.

[0202]

[0215] Embodiment 1: A method of wireless communication performed by a user device (UE), comprising: receiving indications for one or more full-duplex time intervals from a network node; receiving indications for unauthorized communication directions associated with one or more full-duplex time intervals from a network node; and transmitting or receiving communications to or from a network node during one of the full-duplex time intervals, such that the communication is in a direction that is not an unauthorized communication direction.

[0203]

[0216] Embodiment 2: The method according to Embodiment 1, wherein an indication of an unauthorized communication direction is associated with either an unauthorized uplink signal and channel or a unauthorized downlink signal and channel during one or more full-duplex time intervals.

[0204]

[0217] Embodiment 3: The method according to Embodiment 1 or 2, further comprising dropping other communications during a full-duplex time interval or during another full-duplex time interval among one or more full-duplex time intervals, in accordance with the fact that the other communications are in a communication direction in which they are not permitted.

[0205]

[0218] Embodiment 4: The method of Embodiment 3, further comprising the method refraining from transmitting a Hybrid Automatic Retransmission Request (HARQ) feedback indication associated with the downlink communication, wherein the other communication is a downlink communication.

[0206]

[0219] Embodiment 5: The method according to Embodiment 4, wherein refraining from transmitting HARQ feedback indications associated with downlink communications includes transmitting a Type 1 HARQ codebook associated with a set of downlink opportunities, the downlink opportunities corresponding to the downlink communications, the Type 1 HARQ codebook does not include indications for downlink opportunities.

[0207]

[0220] Embodiment 6: The method according to Embodiment 5, wherein unauthorized communication directions are not permitted for a control resource set (CORESET) pool index value, downlink opportunities are associated with a CORESET pool index value, and a Type 1 HARQ codebook is associated with a CORESET pool index value.

[0208]

[0221] Embodiment 7: The method according to Embodiment 3, wherein the other communication is a downlink communication, and the method further comprises transmitting a Negative Response (NACK) indication to the downlink communication.

[0209]

[0222] Embodiment 8: The method according to any one of Embodiments 1 to 7, wherein an indication of an unauthorized communication direction is communicated via radio resource control signaling or media access control (MAC) control element signaling.

[0210]

[0223] Embodiment 9: The method according to any one of Embodiments 1 to 8, wherein the indication for an unauthorized communication direction includes an indication that the unauthorized communication direction is not permitted for communications associated with a control resource set (CORESET) pool index value during one or more full-duplex time intervals.

[0211]

[0224] Embodiment 10: The method according to any one of Embodiments 1 to 9, wherein the indication of an unauthorized communication direction includes a first indication of an unauthorized communication direction for communication associated with a first control resource set (CORESET) pool index value and a second indication of an unauthorized communication direction for communication associated with a second CORESET pool index value.

[0212]

[0225] Embodiment 11: The method according to any one of Embodiments 1 to 10, wherein the indication of an unauthorized communication direction includes an indication of a full-duplex operating state and a transmit configuration indicator (TCI) state associated with the unauthorized communication direction, the TCI state indicating that the unauthorized communication direction is not permitted for one or more full-duplex time intervals.

[0213]

[0226] Embodiment 12: The method according to Embodiment 11, wherein the TCI state indication indicates that the TCI state is associated with a control resource set (CORESET) pool index value, and the TCI state indicates that communication associated with the CORESET pool index value and the unauthorized communication direction is not permitted for one or more full-duplex time intervals.

[0214]

[0227] Embodiment 13: The method according to any one of Embodiments 1 to 12, wherein one or more full-duplex time intervals are one or more subband-full-duplex time intervals.

[0215]

[0228] Embodiment 14: The method according to any one of Embodiments 1 to 13, wherein one or more full-duplex time intervals include at least one of one or more full-duplex slots or one or more full-duplex orthogonal frequency division multiplexing (OFDM) symbols.

[0216]

[0229] Aspect 15: A method of wireless communication performed by a network node, comprising: transmitting one or more full-duplex time interval indications associated with a user device (UE); transmitting UE-associated indications for unauthorized communication directions associated with one or more full-duplex time intervals; and transmitting or receiving communications for the UE during one of the one or more full-duplex time intervals, such that communications are in a communication direction that is not an unauthorized communication direction.

[0217]

[0230] Embodiment 16: The method according to Embodiment 15, wherein an indication of an unauthorized communication direction is associated with either an unauthorized uplink signal and channel or a unauthorized downlink signal and channel during one or more full-duplex time intervals.

[0218]

[0231] Embodiment 17: The method according to Embodiment 15 or 16, further comprising dropping other communications during a full-duplex time interval or during another full-duplex time interval among one or more full-duplex time intervals, in accordance with the fact that the other communications are in a communication direction in which they are not permitted.

[0219]

[0232] Embodiment 18: The method of Embodiment 17, wherein the other communication is a downlink communication, and the method further comprises receiving a Type 1 HARQ codebook associated with a set of downlink opportunities, the Type 1 HARQ codebook does not include an indication for a downlink opportunity.

[0220]

[0233] Embodiment 19: The method according to Embodiment 18, wherein unauthorized communication directions are not permitted for a control resource set (CORESET) pool index value, downlink opportunities are associated with a CORESET pool index value, and a Type 1 HARQ codebook is associated with a CORESET pool index value.

[0221]

[0234] Embodiment 20: The method of Embodiment 17, further comprising the method receiving a Negative Response (NACK) indication for a downlink communication, wherein the other communication is a downlink communication.

[0222]

[0235] Embodiment 21: The method according to any one of embodiments 15 to 20, wherein an indication of an unauthorized communication direction is communicated via radio resource control signaling or media access control (MAC) control element signaling.

[0223]

[0236] Embodiment 22: The method according to any one of Embodiments 15 to 21, wherein the indication for an unauthorized communication direction includes an indication that the unauthorized communication direction is not permitted for communications associated with a control resource set (CORESET) pool index value during one or more full-duplex time intervals.

[0224]

[0237] Embodiment 23: The method according to any one of embodiments 15 to 22, wherein the indication of an unauthorized communication direction includes a first indication of an unauthorized communication direction for communication associated with a first control resource set (CORESET) pool index value and a second indication of an unauthorized communication direction for communication associated with a second CORESET pool index value.

[0225]

[0238] Embodiment 24: The method according to any one of Embodiments 15 to 23, wherein the indication of an unauthorized communication direction includes an indication of a full-duplex operating state and a transmit configuration indicator (TCI) state associated with the unauthorized communication direction, the TCI state indicating that the unauthorized communication direction is not permitted for one or more full-duplex time intervals.

[0226]

[0239] Embodiment 25: The method of Embodiment 24, wherein the TCI state indication indicates that the TCI state is associated with a Control Resource Set (CORESET) pool index value, and the TCI state indicates that communication associated with the CORESET pool index value and the unauthorized communication direction is not permitted for one or more full-duplex time intervals.

[0227]

[0240] Embodiment 26: The method according to any one of Embodiments 15 to 25, wherein one or more full-duplex time intervals are one or more subband-full-duplex time intervals.

[0228]

[0241] Embodiment 27: The method according to any one of Embodiments 15 to 26, wherein one or more full-duplex time intervals include at least one of one or more full-duplex slots or one or more full-duplex orthogonal frequency division multiplexing (OFDM) symbols.

[0229]

[0242] Embodiment 28: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor, wherein the instructions cause the device to perform one or more of the methods described in Embodiments 1 to 14.

[0230]

[0243] Embodiment 29: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein one or more processors are configured to perform one or more of the methods described in Embodiments 1 to 14.

[0231]

[0244] Embodiment 30: An apparatus for wireless communication, comprising at least one means for performing a method according to one or more of Embodiments 1 to 14.

[0232]

[0245] Embodiment 31: A non-temporary computer-readable medium storing code for wireless communication, wherein the code includes instructions that can be executed by a processor, and the instructions perform one or more of the methods described in Embodiments 1 to 14.

[0233]

[0246] Embodiment 32: A non-temporary computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising 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 described in Embodiments 1 to 14.

[0234]

[0247] Embodiment 33: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor, wherein the instructions cause the device to perform one or more of the methods described in Embodiments 15 to 27.

[0235]

[0248] Embodiment 34: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein one or more processors are configured to perform one or more of the methods described in Embodiments 15 to 27.

[0236]

[0249] Embodiment 35: An apparatus for wireless communication, comprising at least one means for performing one or more methods according to Embodiments 15 to 27.

[0237]

[0250] Embodiment 36: A non-temporary computer-readable medium storing code for wireless communication, wherein the code includes instructions that can be executed by a processor, and the instructions perform one or more of the methods described in Embodiments 15 to 27.

[0238]

[0251] Embodiment 37: A non-temporary computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising 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 described in Embodiments 15 to 27.

[0239]

[0252] The above disclosures are for illustrative and explanatory purposes only, and are not intended to be exhaustive or to limit the forms to those disclosed. Modifications and variations may be made in light of the above disclosures or obtained from the practice of the forms.

[0240]

[0253] When used herein, the term “Components” shall be broadly interpreted as hardware or a combination of hardware and software. “Software” shall be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, among other examples. When used herein, “Processor” is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in different forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited to any particular form. Therefore, a person skilled in the art will understand that software and hardware may be designed to implement a system or method based at least in part on the descriptions herein, so the operation and behavior of a system or method are described herein without reference to specific software code.

[0241]

[0254] As used herein, “meeting a threshold” may, depending on the context, mean, in the examples, that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold.

[0242]

[0255] As used herein, the terms “determine” or “determining” encompass a wide range of actions, and therefore “determining” can include, among other examples, calculating, performing calculations, processing, deriving, investigating, searching (such as searching within tables, databases, or other data structures), inferring, confirming, and / or measuring. “Determining” can also include, among other examples, receiving (such as receiving information), accessing (such as accessing data stored in memory), and / or transmitting (such as transmitting information). Furthermore, “determining” can also include resolving, selecting, obtaining, choosing, establishing, and other similar actions.

[0243]

[0256] Where specific combinations of features are described in the claims or disclosed herein, those combinations do not limit the disclosure of various embodiments. Many of these features can be combined in ways that are not specifically enumerated in the claims or disclosed herein. The disclosure of various embodiments includes each dependent claim in combination with any other claim in the set of claims. Where used herein, the phrase “at least one of” the list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” shall include 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 order of a, b, and c).

[0244]

[0257] None of the elements, actions, or commands used herein should be construed as essential or mandatory unless expressly stated otherwise. Furthermore, as used herein, the articles “a” and “an” 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 with respect to 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.” If only one item is intended, the phrase “only one” or similar words should be used. Also, as used herein, terms such as “has,” “have,” and “having” and similar terms are open-ended terms that do not limit the elements they modify (for example, an element that “has” A may also have B). Furthermore, as used herein, “based on” is intended to be interpreted in a comprehensive sense unless otherwise explicitly indicated. For example, “based on” may be used interchangeably with “at least partially based on,” “associated with,” or “according to,” unless otherwise explicitly indicated. Specifically, unless the phrase “based on ‘a’ alone” or refers to a contextual equivalent, “based on ‘a’” or “at least partially based on ‘a’” may be based on “a” alone, or on “a” in combination with one or more other factors, conditions, or pieces of information. Also, as used herein, the term “or” is comprehensive when used consecutively and may be used interchangeably with “and / or” unless otherwise explicitly indicated (for example, when used in combination with “either” or “only one of”).

Claims

1. User equipment (UE) for wireless communication, At least one memory, The system comprises at least one processor communicatively coupled to the at least one memory, and the at least one processor provides the UE to The network node receives one or more full-duplex time interval indications. The network node receives an indication of an unauthorized communication direction associated with one or more full-duplex time intervals. A UE capable of operating during one of the one or more full-duplex time intervals to transmit or receive communications with the network node, such that the communications are in a communication direction other than the unauthorized communication direction.

2. The UE according to claim 1, wherein the indication for the unauthorized communication direction is associated with either an uplink signal and channel or a downlink signal and channel that is not permitted during the one or more full-duplex time intervals.

3. The at least one processor provides the UE with The UE according to claim 1, further operable to drop other communications during the full-duplex time interval or another full-duplex time interval among the one or more full-duplex time intervals, such that the other communications are in the unauthorized communication direction.

4. The other communication is downlink communication, and the at least one processor communicates to the UE, The UE according to claim 3, further operable to refrain from transmitting a Hybrid Automatic Retransmission Request (HARQ) feedback indication associated with the downlink communication.

5. In order to cause the UE to refrain from transmitting the HARQ feedback indication associated with the downlink communication, at least one processor instructs the UE to The UE according to claim 4, which is operable to cause a Type 1 HARQ codebook associated with a set of downlink opportunities including a downlink opportunity corresponding to the downlink communication, wherein the Type 1 HARQ codebook does not include an indication for the downlink opportunity.

6. The UE according to claim 5, wherein the unauthorized communication direction is not permitted for a control resource set (CORESET) pool index value, the downlink opportunity is associated with the CORESET pool index value, and the type 1 HARQ codebook is associated with the CORESET pool index value.

7. The other communication is downlink communication, and the at least one processor communicates to the UE, The UE according to claim 3, further operable to transmit a negative response (NACK) indication for the downlink communication.

8. The UE according to claim 1, wherein the indication for the unauthorized communication direction is communicated via radio resource control signaling or media access control (MAC) control element signaling.

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

10. The UE according to claim 1, wherein the indication for the unauthorized communication direction includes a first unauthorized communication direction indication for communication associated with a first control resource set (CORESET) pool index value and a second unauthorized communication direction indication for communication associated with a second CORESET pool index value.

11. The UE according to claim 1, wherein the indication for the unauthorized communication direction includes an indication of a full-duplex operating state and a transmit configuration indicator (TCI) state associated with the unauthorized communication direction, the TCI state indicating that the unauthorized communication direction is not permitted during the one or more full-duplex time intervals.

12. The UE according to 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, and the TCI state indicates that communication associated with the CORESET pool index value and the unauthorized communication direction is not permitted during the one or more full-duplex time intervals.

13. A network node for wireless communication, At least one memory, The system comprises at least one processor communicatively coupled to the at least one memory, and the at least one processor is connected to the network node. To transmit one or more full-duplex time interval indications associated with the user equipment (UE), To transmit an indication associated with the UE for an unauthorized communication direction associated with one or more full-duplex time intervals, A network node capable of operating to transmit or receive communications for the UE during one of the one or more full-duplex time intervals, such that the communications are in a communication direction other than the unauthorized communication direction.

14. The network node according to claim 13, wherein the indication for the unauthorized communication direction is associated with either an uplink signal and channel or a downlink signal and channel that is not permitted during the one or more full-duplex time intervals.

15. The at least one processor provides the network node, The network node according to claim 13, further operable to drop other communications during the full-duplex time interval or another full-duplex time interval among the one or more full-duplex time intervals, such that the other communications are in the unauthorized communication direction.

16. The other communication is downlink communication, and the at least one processor communicates to the network node, The network node according to claim 15, which is further operable to receive a type 1 HARQ codebook associated with a set of downlink opportunities, including downlink opportunities corresponding to the downlink communications, wherein the type 1 HARQ codebook does not include indications for the downlink opportunities.

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

18. The network node according to claim 13, wherein the indication for the unauthorized communication direction includes an indication of a full-duplex operating state and a transmit configuration indicator (TCI) state associated with the unauthorized communication direction, the TCI state indicating that the unauthorized communication direction is not permitted during the one or more full-duplex time intervals.

19. A method of wireless communication performed by user equipment (UE), Receiving one or more full-duplex time interval indications from a network node, Receiving an indication from the network node of an unauthorized communication direction associated with one or more full-duplex time intervals, A method comprising transmitting or receiving a communication with the network node during one of the one or more full-duplex time intervals, such that the communication is in a communication direction other than the unauthorized communication direction.

20. The method according to claim 19, wherein the indication for the unauthorized communication direction is associated with either an uplink signal and channel or a downlink signal and channel that is not permitted during the one or more full-duplex time intervals.

21. The method according to claim 19, further comprising dropping other communications during the full-duplex time interval or another full-duplex time interval among the one or more full-duplex time intervals, such that the other communications are in the unauthorized communication direction.

22. The other communication is a downlink communication, and the method is The method according to claim 21, further comprising refraining from transmitting a Hybrid Automatic Retransmission Request (HARQ) feedback indication associated with the downlink communication.

23. Refraining from transmitting the HARQ feedback indication associated with the downlink communication, The method according to claim 22, comprising transmitting a type 1 HARQ codebook associated with a set of downlink opportunities, the downlink opportunities corresponding to the downlink communication, wherein the type 1 HARQ codebook does not include an indication for the downlink opportunities.

24. The method according to claim 23, wherein the unauthorized communication direction is not permitted for a control resource set (CORESET) pool index value, the downlink opportunity is associated with the CORESET pool index value, and the type 1 HARQ codebook is associated with the CORESET pool index value.

25. The method according to claim 19, wherein the indication for the unauthorized communication direction includes an indication of a full-duplex operating state and a transmit configuration indicator (TCI) state associated with the unauthorized communication direction, the TCI state indicating that the unauthorized communication direction is not permitted during the one or more full-duplex time intervals.

26. A method of wireless communication performed by network nodes, Transmitting one or more full-duplex time interval indications associated with a user device (UE), Transmitting an indication associated with the UE for an unauthorized communication direction associated with one or more full-duplex time intervals, A method comprising transmitting or receiving communications for the UE during one of the one or more full-duplex time intervals, such that the communications are in a communication direction other than the unauthorized communication direction.

27. The method according to claim 26, wherein the indication for the unauthorized communication direction is associated with either an uplink signal and channel or a downlink signal and channel that is not permitted during the one or more full-duplex time intervals.

28. The method according to claim 26, further comprising dropping other communications during the full-duplex time interval or another full-duplex time interval among the one or more full-duplex time intervals, such that the other communications are in the unauthorized communication direction.

29. The other communication is a downlink communication, and the method is The method of claim 28, further comprising receiving a type 1 HARQ codebook associated with a set of downlink opportunities, the type 1 HARQ codebook not containing an indication for the downlink opportunity.

30. The one or more full-duplex time intervals mentioned above are One or more full-duplex slots, or The method according to claim 26, comprising at least one of one or more full-duplex orthogonal frequency division multiplexing (OFDM) symbols.

Images