Multiplexing rules for subband full-duplex communication

Abstract

Methods, systems, and devices for wireless communications are described. A first network node may receive a control message identifying at least one symbol or at least one slot to be used for subband full-duplex communication at a second network node. The first network node may receive a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot. The first network node may receive a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot. The first network node may communicate with the second network node during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

Description

[Technical Field]

[0001] cross reference This patent application claims the benefit of U.S. Patent Application No. 18 / 050,350 by ZHANG et al., entitled "MULTIPLEXING RULES FOR SUBBAND ​​FULL DUPLEX COMMUNICATIONS," filed October 27, 2022, which is assigned to the assignee of the present application and expressly incorporated herein by reference.

[0002] introduction The following relates to wireless communications involving multiplexing rules for subband full duplex (SBFD) communications. Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and so on. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes referred to as New Radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM), etc. A wireless multiple-access communication system may include one or more base stations that each support wireless communication for communication devices, sometimes known as user equipment (UE). Summary of the Invention [Means for solving the problem]

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses that support multiplexing rules for subband full duplex (SBFD) communications. For example, the described techniques provide a framework for managing conflicting configuration information related to the same transmission time interval (TTI), such as a slot or symbol. For example, a first network node, such as a user equipment (UE), may receive a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node (such as a base station, also referred to herein as a network entity). In some examples, the first network node may receive a first indication of uplink resources for uplink communications during the at least one symbol or at least one slot. Further, the first network node may receive a second indication of downlink resources for downlink communications during the at least one symbol or at least one slot. In some examples, the first network node may communicate with the second network node during the at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules. In some examples, using one or more prioritization rules to determine whether to communicate according to a first instruction or a second instruction may lead to reduced latency and increased resource utilization, among other possible benefits.

[0004] A method for wireless communication in a first network node is described. The method may include receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node, receiving a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot, receiving a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot, and communicating with the second network node during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0005] An apparatus for wireless communication in a first network node is described, which may include a memory and at least one processor coupled to the memory. The at least one processor is configured to: receive a control message identifying at least one symbol or at least one slot to be used for SBFD communication at a second network node; receive a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot; receive a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot; and communicate with the second network node during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0006] Another apparatus for wireless communication in a first network node is described. The apparatus may include means for receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node, means for receiving a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot, means for receiving a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot, and means for communicating with the second network node during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0007] A non-transitory computer-readable medium having stored thereon code for wireless communications is described that, when executed by a first network node, causes the first network node to receive a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node, receive a first indication of uplink resources for uplink communications during the at least one symbol or at least one slot, receive a second indication of downlink resources for downlink communications during the at least one symbol or at least one slot, and communicate with the second network node during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink resources may be in at least one uplink subband or at least one flexible subband, and the downlink resources may be in at least one downlink subband or at least one flexible subband.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction may be for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction may be for reception of a synchronization signal block (SSB) in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink slot format indicator (SFI) related to at least one symbol or at least one slot.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a physical uplink control channel (PUCCH) signal, a physical uplink shared channel (PUSCH) signal, a sounding reference signal (SRS), or a random access preamble.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction may be for transmission of a random access preamble in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction may be for reception of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instructions include a downlink SFI related to at least one symbol or at least one slot.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction may be for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction may be for monitoring a downlink control channel in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions include an uplink SFI related to at least one symbol or at least one slot.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions may be for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instructions may be for reception of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI related to at least one symbol or at least one slot, and the second instruction includes a radio resource control (RRC) setting related to at least one symbol or at least one slot.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an RRC configuration related to at least one symbol or at least one slot, and the second instruction includes a downlink SFI related to at least one symbol or at least one slot.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink signal includes a physical downlink control channel (PDCCH) signal, a physical downlink shared channel (PDSCH) signal, a channel state information reference signal (CSI-RS), or a positioning reference signal (PRS).

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a flexible RRC configuration relating to at least one symbol or at least one slot.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI related to at least one symbol or at least one slot, the second instruction includes a dynamic grant related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal or a CSI-RS.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI or a flexible SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes a dynamic grant related to at least one symbol or at least one slot, the second instruction includes a downlink SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a downlink SFI or a flexible SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes a dynamic grant related to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, a CSI-RS, or a PRS.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a dynamic grant related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a downlink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more prioritization rules include: when a beam failure recovery procedure is not triggered, reception of a downlink signal may be prioritized over transmission of an uplink signal during at least one symbol or at least one slot; and when a beam failure recovery procedure is triggered, transmission of an uplink signal may be prioritized over reception of a downlink signal during at least one symbol or at least one slot.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a downlink SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes a flexible RRC configuration relating to at least one symbol or at least one slot, and the uplink signal includes an SRS or a random access preamble.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more prioritization rules include that reception of a downlink signal or transmission of an uplink signal may be prioritized based on a respective channel priority associated with each of the downlink signal and the uplink signal.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink and downlink resources may be within one or more carriers to be used for time division duplex (TDD) communications between the first network node and the second network node.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions may be for a first component carrier of a radio frequency spectrum band, and the second instructions may be for a second component carrier of the radio frequency spectrum band, where the first component carrier is different from the second component carrier.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message further identifies one or more of the frequency locations of at least one uplink subband to be used for transmission of an uplink message during at least one symbol or at least one slot, at least one downlink subband to be used for reception of a downlink message during at least one symbol or at least one slot, at least one guard band intermediate the uplink subband and the downlink subband during at least one symbol or at least one slot, and at least one flexible subband to be used for transmission of an uplink message or reception of a downlink message during at least one symbol or at least one slot.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink or downlink resources include periodic or semi-persistent resources.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network node includes a user equipment (UE) and the second network node includes a base station.

[0042] A method for wireless communication in a network node is described. The method may include outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communication at the network node, outputting a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot, outputting a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot, and communicating during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0043] An apparatus for wireless communication in a network node is described. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor is configured to output a control message identifying at least one symbol or at least one slot to be used for SBFD communication at the network node, output a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot, output a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot, and communicate during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0044] Another apparatus for wireless communication in a network node is described that may include means for outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communications at the network node, means for outputting a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot, means for outputting a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot, and means for communicating during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0045] A non-transitory computer-readable medium having stored thereon code for wireless communications is described that, when executed by a network node, causes the network node to output a control message identifying at least one symbol or at least one slot to be used for SBFD communications at the network node, output a first indication of uplink resources for uplink communications during the at least one symbol or at least one slot, output a second indication of downlink resources for downlink communications during the at least one symbol or at least one slot, and communicate during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink resources may be within at least one uplink subband or at least one flexible subband, and the downlink resources may be within at least one downlink subband or at least one flexible subband.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions may be for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instructions may be for communication of an SSB in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions include an uplink SFI related to at least one symbol or at least one slot.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction may be for communication of a random access preamble in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction may be for communication of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0051] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instructions include a downlink SFI related to at least one symbol or at least one slot.

[0052] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions may be for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instructions may be for communication using a downlink control channel in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions include an uplink SFI related to at least one symbol or at least one slot.

[0054] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions may be for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instructions may be for communication of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0055] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI related to at least one symbol or at least one slot, and the second instruction includes an RRC configuration related to at least one symbol or at least one slot.

[0056] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0057] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an RRC configuration related to at least one symbol or at least one slot, and the second instruction includes a downlink SFI related to at least one symbol or at least one slot.

[0058] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0059] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a flexible RRC configuration relating to at least one symbol or at least one slot.

[0060] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0061] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI related to at least one symbol or at least one slot, the second instruction includes a dynamic grant related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal or a CSI-RS.

[0062] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI or a flexible SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0063] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes a dynamic grant related to at least one symbol or at least one slot, the second instruction includes a downlink SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0064] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a downlink SFI or a flexible SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0065] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes a dynamic grant related to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, a CSI-RS, or a PRS.

[0066] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a dynamic grant related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0067] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes an uplink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0068] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a downlink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0069] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0070] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0071] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more prioritization rules include: when a beam failure recovery procedure is not triggered, communication of a downlink signal may be prioritized over communication of an uplink signal during at least one symbol or at least one slot; and when a beam failure recovery procedure is triggered, communication of an uplink signal may be prioritized over communication of a downlink signal during at least one symbol or at least one slot.

[0072] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second instruction includes a downlink SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0073] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instruction includes a flexible RRC configuration relating to at least one symbol or at least one slot, and the uplink signal includes an SRS or a random access preamble.

[0074] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more prioritization rules include that communication of downlink or uplink signals may be prioritized based on respective channel priorities associated with each of the downlink and uplink signals.

[0075] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink and downlink resources may be within one or more carriers to be used for TDD communications in the method.

[0076] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first instructions may be for a first component carrier of a radio frequency spectrum band, and the second instructions may be for a second component carrier of the radio frequency spectrum band, where the first component carrier is different from the second component carrier.

[0077] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message further identifies one or more of the frequency locations of at least one uplink subband to be used for communication of uplink messages during at least one symbol or at least one slot, at least one downlink subband to be used for communication of downlink messages during at least one symbol or at least one slot, at least one guard band intermediate the uplink and downlink subbands during the at least one symbol or at least one slot, and at least one flexible subband to be used for communication of uplink or downlink messages during the at least one symbol or at least one slot.

[0078] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink or downlink resources include periodic or semi-persistent resources.

[0079] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the network node includes a base station. [Brief explanation of the drawings]

[0080] [Figure 1] 1A-1D illustrate an example of a wireless communication system that supports multiplexing rules for sub-band full duplex (SBFD) communication, in accordance with one or more aspects of the present disclosure. [Figure 2] 1A-1D illustrate an example of a wireless communication system that supports multiplexing rules for sub-band full duplex (SBFD) communication, in accordance with one or more aspects of the present disclosure. [Figure 3A] 1 illustrates an example SBFD configuration that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 3B] 1 illustrates an example SBFD configuration that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 4] 1 illustrates an example process flow for supporting multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 5] 1 illustrates a block diagram of a device that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 6] 1 illustrates a block diagram of a device that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 7] 1 illustrates a block diagram of a communication manager that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 8]1 illustrates a diagram of a system including devices that support multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 9] 1 illustrates a block diagram of a device that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 10] 1 illustrates a block diagram of a device that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 11] 1 illustrates a block diagram of a communication manager that supports multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 12] 1 illustrates a diagram of a system including devices that support multiplexing rules for SBFD communications, in accordance with one or more aspects of the present disclosure. [Figure 13] 1 illustrates a flow diagram illustrating a method for supporting multiplexing rules for SBFD communications, according to one or more aspects of the present disclosure. [Figure 14] 1 illustrates a flow diagram illustrating a method for supporting multiplexing rules for SBFD communications, according to one or more aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0081] In some wireless communication systems, a communication device, such as a user equipment (UE) or a network entity (e.g., a base station), can support wireless communication using one or more radio access technologies (RATs). Examples of RATs may include fourth-generation (4G) systems, such as long-term evolution (LTE) systems, and fifth-generation (5G) systems, sometimes referred to as new radio (NR) systems, among other generations thereafter. In such cases, a communication device may operate in half-duplex mode or full-duplex mode, or a combination thereof. In half-duplex mode, a communication device can either transmit a communication or receive a communication during a time period, such as a transmission time interval (TTI), which may span one or more time resources (e.g., symbols, minislots, slots, etc.). In full-duplex mode, a communication device can simultaneously transmit and receive a communication during the time period. That is, a communication received at a communication device may overlap in the time domain with a communication transmitted at the communication device. For example, the symbols or slots occupied by the received signal may overlap with the symbols or slots occupied by the transmitted signal.

[0082] In some examples, a communication device (e.g., a network entity) may support multi-user multiple input multiple output (MU-MIMO) using full-duplex communication so that the communication device may communicate with multiple other communication devices (e.g., multiple UEs) simultaneously. For example, downlink communication transmitted at the network entity to a first UE may overlap in time with uplink communication received at the network entity from a second UE. In some examples, downlink communication transmitted at the network entity may interfere with uplink communication received at the network entity. That is, the network entity may experience signal leakage between an antenna panel used at the network entity for transmission and another antenna panel used at the network entity for reception. Such interference may be referred to as self-interference.

[0083] In some examples, to reduce self-interference, a network entity may support subband full-duplex (SBFD) operation, in which the network entity may use multiple subbands for uplink reception and downlink transmission. At the same time, UEs with which the network entity communicates may be limited to half-duplex communication. For example, the network entity may simultaneously use an uplink subband (or a flexible subband) for receiving uplink communications from a first UE and a downlink subband (or another flexible subband) for transmitting downlink communications to a second UE. In such examples, the UEs may be configured to simultaneously communicate with the network entity using half-duplex time division duplex (TDD). That is, during a TTI, each UE may be able to communicate with the network entity in either the uplink or downlink direction. In some examples, the transmit direction for a TTI may be specified (e.g., configured in the UE). However, because the network entity may use a full-duplex subband during a TTI for simultaneous uplink and downlink communications, each UE may be able to communicate with the network entity in either the uplink or downlink direction during a TTI, regardless of the transmit direction specified for the TTI. That is, use of full-duplex subbands at a network entity during a TTI may allow the TDD TTI designation at the UE to be overridden. However, in some examples, the UE (e.g., and network entity) may be configured with one or more multiplexing rules based on half-duplex operation. For example, according to such rules, the UE may refrain from monitoring (or the network entity may refrain from sending) messages that schedule both uplink and downlink communications during the same TTI (e.g., the same slot or symbol). Thus, multiplexing rules based on half-duplex operation may not support overriding the TDD TTI designation, which may lead to reduced resource utilization and unnecessary increases in latency.

[0084] Various aspects of the present disclosure generally relate to techniques for supporting multiplexing rules for SBFD communications, and more particularly, to a framework for managing conflicting configuration information related to the same TTI. For example, a UE implementing TDD with a network entity may receive multiple (e.g., different) messages scheduling both uplink and downlink communications within the same TTI (e.g., the same slot or the same symbol). In one such example, the UE may be configured with one or more multiplexing rules supporting SBFD operations at the network entity. For example, such multiplexing rules may enable the UE to be simultaneously configured with uplink and downlink configurations for the same TTI. That is, the multiplexing rules supporting SBFD operations at the network entity may enable the UE to receive conflicting configuration information related to the same TTI. In one such example, the UE may be configured with one or more prioritization rules for managing conflicting configuration information. For example, the UE may use the one or more prioritization rules to determine whether to communicate according to an uplink configuration or a downlink configuration during the TTI. In some examples, the prioritization rule may indicate to the UE to communicate uplink signals according to the uplink configuration or to communicate downlink signals according to the downlink configuration during the TTI based on the respective channel priority associated with each of the downlink or uplink signals.

[0085] Certain aspects of the subject matter described herein may be implemented to achieve one or more of the following potential advantages: For example, techniques employed by the described communications devices may provide benefits and enhancements to communications device operation, including enhancements to TDD communications between communications devices; for example, operations performed by the described communications devices may enable the communications devices to receive conflicting configuration information related to the same TTI and provide a framework for managing the conflicting configuration information; in some implementations, operations performed by the described communications devices to manage the conflicting configuration information may include using one or more prioritization rules to identify a configuration to use during the TTI; in examples, operations performed by the described communications devices may support reduced latency and increased resource utilization, among other benefits.

[0086] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are also described in the context of SBFD configurations and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to multiplexing rules for SBFD communications.

[0087] 1 illustrates an example of a wireless communication system 100 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0088] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices of different types or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, each network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entities 105 and the UEs 115 may support communication of signals over one or more radio access technologies (RATs).

[0089] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both at different times. The UEs 115 may be devices of different types or with different capabilities. Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

[0090] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, be, or be included in (e.g., may be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (also sometimes referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may differ relative to these examples. Similarly, references to a UE, a base station, an apparatus, a device, a computing system, etc. may include disclosure of the UE, the base station, the apparatus, the device, the computing system, etc. that are network nodes. For example, a disclosure that a UE is configured to receive information from a base station also discloses that the first network node is configured to receive information from a second network node.Consistent with this disclosure, when a specific example is expanded in accordance with this disclosure (e.g., also disclosing that the UE is configured to receive information from a base station and that the first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in a converse, but broad, open-ended manner. In the above example also disclosing that the UE is configured to receive information from a base station and that the first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, one or more first sets of one or more components, a first processing entity, etc. configured to receive the information, and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0091] As described herein, communication of information (e.g., any information, signal, etc.) may be described in various manners using different terms. A disclosure of one communication term includes a disclosure of other communication terms. For example, a first network node may be described as configured to transmit information to a second network node. In this example, consistent with the present disclosure, a disclosure that a first network node is configured to transmit information to a second network node includes a disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example, consistent with the present disclosure, a disclosure that a first network node is configured to transmit information to a second network node includes a disclosure that the second network node is configured to receive, acquire, or decode information provided, sent, output, communicated, or transmitted by the first network node.

[0092] In some examples, the network entities 105 may communicate with the core network 130, with each other, or with both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to an S1, N2, N3, or other interface protocol). In some examples, the network entities 105 may communicate with each other either directly (e.g., directly between the network entities 105), or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to an X2, Xn, or other interface protocol). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include, among other examples or various combinations thereof, one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links). The UE 115 may communicate with the core network 130 via the communication link 155.

[0093] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., base transceiver station, radio base station, NR base station, access point, radio transceiver, NodeB, eNodeB (eNB), Next Generation NodeB or Giga NodeB (any of which may be referred to as gNB), 5G NB, Next Generation eNB (ng-eNB), Home NodeB, Home eNodeB, or other suitable terminology). In some examples, the network entities 105 (e.g., base stations 140) may be implemented in a converged (e.g., monolithic, standalone) base station architecture that may be configured to utilize protocol stacks that are physically or logically integrated within a single network entity 105 (e.g., a single RAN node such as base station 140).

[0094] In some examples, the network entities 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real time RIC (Near-RT RIC), a non-real time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entity 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0095] The division of functionality among the CU 160, the DU 165, and the RU 170 is flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are implemented in the CU 160, the DU 165, or the RU 170. For example, a functional division of a protocol stack may be adopted between the CU 160 and the DU 165 such that the CU 160 can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, which may host lower protocol layers such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, each of which may be at least partially controlled by the CU 160. Additionally or alternatively, a functional division of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170).In some cases, the functional division between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of the CU 160, the DU 165, or the RU 170, while other functions for the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). The CU 160 may be further functionally divided into a CU control plane (CU-CP) function and a CU user plane (CU-UP) function. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DUs 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by the respective network entities 105 communicating over such communication link.

[0096] In a wireless communication system (e.g., the wireless communication system 100), infrastructure and spectrum resources for radio access can supplement wired backhaul connections to support wireless backhaul link capabilities and provide an IAB network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with the donor network entity 105 (e.g., the donor base station 140). The one or more donor network entities 105 (e.g., the IAB donors) may be in communication with one or more additional network entities 105 (e.g., the IAB nodes 104) via supported access links and backhaul links (e.g., the backhaul communication links 120). An IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the associated IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antenna (e.g., of the RU 170) of the IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., the IAB node 104, the UE 115) in an access network (e.g., downstream) relay chain or configuration. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104, or components of the IAB node 104) may be configured to operate in accordance with the techniques described herein.

[0097] For the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the multiplexing rules for SBFD communications described herein. For example, some operations described as being performed by the UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, an RU 170, a RIC 175, an SMO 180).

[0098] The UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or any other suitable terminology, and a “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. The UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, and may be implemented in various items such as an appliance, a vehicle, a meter, etc., among other examples.

[0099] The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as shown in FIG. 1, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples.

[0100] The UE 115 and the network entity 105 may communicate wirelessly with each other over one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure that supports the communication link 125. For example, a carrier used for the communication link 125 may include a portion (e.g., a bandwidth part (BWP)) of an RF spectrum band operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation on the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and TDD component carriers. Communication between a network entity 105 and another device may refer to communication between the device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, when referring to a network entity 105, the terms "transmit," "receive," or "communicate" may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

[0101] The communication links 125 shown in the wireless communication system 100 may include, among other transmission configurations, downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode).

[0102] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth or may be configurable to support communication using one of the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports simultaneous communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

[0103] A signal waveform transmitted over a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing may be inversely proportional. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during a transmission duration) and a relatively high order of the modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase data rates or data integrity for communications with UE 115.

[0104] The time interval for the network entity 105 or the UE 115 is, for example, T s =1 / (Δf max N f ) seconds, where Δf max may represent the supported subcarrier spacing, and N f may represent the supported discrete Fourier transform (DFT) sizes. The communication resource time intervals may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0105] Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on the subcarrier spacing. Each slot may include a certain number of symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may be further divided into multiple minislots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0106] A subframe, slot, minislot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a TTI. In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0107] Physical channels may be multiplexed for communication using carriers according to various techniques. Physical control channels and physical data channels may be multiplexed for signaling over downlink carriers using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may span the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates at one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0108] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus may provide communication coverage for moving coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include a heterogeneous network, for example, where different types of network entities 105 provide coverage to various coverage areas 110 using the same or different radio access technologies.

[0109] The wireless communication system 100 may be configured to support ultra-reliable or low-latency communications, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency, or critical functionality. Ultra-reliable communications may include private or group communications and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functionality may include service prioritization, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0110] In some examples, the UEs 115 may be configured to support direct communication with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group conducting D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable to or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, with each UE 115 transmitting to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without the involvement of the network entity 105.

[0111] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5G core, 5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (PDN gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be forwarded through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may connect to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, intranet(s), IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0112] The wireless communication system 100 may operate using one or more frequency bands, which may range from 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly known as the ultra-high frequency (UHF) region or decimeter band because wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, sometimes referred to as clusters, the waves may penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using lower frequency and longer waves in the shortwave (high frequency (HF)) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0113] The wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands, such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, the network entity 105 and devices, such as the UE 115, may employ carrier sensing for collision detection and collision avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0114] The network entity 105 (e.g., base station 140, RU 170) or the UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or the UE 115 may be arranged in one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated in an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located in various geographic locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming of communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted through the antenna ports.

[0115] The network entity 105 or the UE 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques are sometimes referred to as spatial multiplexing. Multiple signals may be transmitted by a transmitting device via, for example, different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0116] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming may be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjusting signals communicated through antenna elements may include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to signals carried through the antenna elements associated with the device. The adjustment associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting or receiving device, or with respect to some other orientation).

[0117] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform a beamforming operation for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. The transmissions along different beam directions may be used to identify beam directions (e.g., by a transmitting device such as the network entity 105 or by a receiving device such as the UE 115) for subsequent transmission or reception by the network entity 105.

[0118] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device, such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with a transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or otherwise acceptable signal quality.

[0119] In some examples, transmission by a device (e.g., by the network entity 105 or the UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a composite beam for transmission (e.g., from the network entity 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. The network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may be precoded or non-precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by the network entity 105 (e.g., base station 140, RU 170), the UE 115 may employ similar techniques to transmit a signal multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or to transmit a signal along a single direction (e.g., to transmit data to a receiving device).

[0120] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., network entity 105), such as a synchronization signal, a reference signal, a beam selection signal, or other control signals. For example, a receiving device may perform receiving according to multiple receiving directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receiving configurations or receiving directions. In some examples, a receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive setting may be aligned along a beam direction determined based on listening along different receive setting directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening along multiple beam directions).

[0121] In some examples, the wireless communication system 100 may support multiplexing rules for SBFD communications and a framework for managing conflicting configuration information related to the same TTI. For example, the network entity 105 may support SBFD operation with multiple UEs 115, which may operate using half-duplex TDD. In one such example, the UE 115 may receive a control message identifying at least one TTI (e.g., at least one symbol or at least one slot) to be used for SBFD communications at the network entity 105. Further, the UE 115 may receive a first indication of uplink resources for uplink communications during the at least one TTI and a second indication of downlink resources for downlink communications during the at least one TTI. In some examples, the UE 115 may communicate with the network entity 105 during the at least one TTI according to one of the first indication or the second indication based on one or more prioritization rules. That is, the UE 115 may use one or more prioritization rules to determine whether to use the indicated uplink resources for communicating with the network entity 105 during at least one TTI in the uplink direction or the downlink resources for communicating with the network entity 105 during at least one TTI in the downlink direction. In some examples, using one or more prioritization rules to manage conflicting configuration information related to the same TTI may lead to reduced latency within the wireless communication system 100, among other possible benefits.

[0122] 2 illustrates an example of a wireless communication system 200 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The wireless communication system 200 may implement or be implemented in one or more aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a network entity 205 and a UE 215-a and a UE 215-b, which may be examples of the corresponding devices described with reference to FIG. 1. In some examples, the wireless communication system 200 may implement or be implemented in one or more aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 215-a and a UE 215-b, which may be examples of the UE 115 described with reference to FIG. 1. The wireless communication system 200 may also include the network entity 205, which may be an example of one or more of the network entities 105 (e.g., a CU, a DU, a RU, a base station, an IAB node, or one or more other network nodes) described with reference to FIG. 1. Network entity 205 may communicate with UE 215-a and UE 215-b using communication link 220-a and communication link 220-b, respectively. Communication link 220 may be an example of communication link 125 described with reference to Figure 1. Wireless communication system 200 may include features for improved communication between network entity 205 and UE 215, among other possible benefits.

[0123] The wireless communication system 200 (e.g., an NR system) may support one or more types of duplex operation (e.g., half-duplex operation, full-duplex operation). For example, the wireless communication system 200 may support one or more types of duplex operation for one or more deployment scenarios. Performance evaluation results associated with one or more types of duplex operation supported in the wireless communication system 200 may be obtained using an evaluation of the one or more types of duplex operation (e.g., using an evaluation method). In some examples, the wireless communication system 200 may support subband non-overlapping full duplex. For example, the wireless communication system 200 may support coexistence of one or more uplink subbands and one or more downlink subbands in the same channel and adjacent channels. Additionally or alternatively, the wireless communication system 200 may support dynamic or flexible TDD. For example, the wireless communication system may support coexistence of one or more uplink subbands and one or more downlink subbands in the same channel and adjacent channels that may be configured for TDD.

[0124] For example, the wireless communication system 200 may support one or more potential extensions to support multiple types of duplex operation for TDD (e.g., duplex evolution). In some examples, the wireless communication system 200 may support multiple types of duplex operation for TDD (e.g., NR TDD) using paired or unpaired radio frequency spectrum bands. In some instances, a paired radio frequency spectrum band may be referred to as paired spectrum. Additionally or alternatively, an unpaired radio frequency spectrum band may be referred to as unpaired spectrum. As described herein, a paired radio frequency spectrum band (e.g., paired operating band) may refer to an operating band that includes a first set of frequencies configured for reception at a communication device (e.g., network entity 205, UE 215) and a second set of frequencies configured for transmission at the communication device that are paired with the first set of frequencies. In some examples of paired operating bands, the first set of frequencies (e.g., first band, first operating band, first carrier) and the second set of frequencies (e.g., second band, second operating band, second carrier) may not overlap in frequency. For example, the first set of frequencies and the second set of frequencies may not overlap in frequency, or there may be a frequency range or set of subcarriers between (e.g., separating) the two sets of frequencies. Additionally or alternatively, as described herein, an unpaired operating band may refer to a set of frequencies (e.g., a range of frequencies, which may be referred to as a band, operating band, or carrier) that can be used for both transmission and reception in a communication device.

[0125] In some examples, the wireless communication system 200 may support one or more duplex extensions at the network entity 205 (e.g., at the gNB side) and half-duplex operation at the UE 215 (e.g., at the UE side). For example, the network entity 205 may support subband non-overlapping full-duplex on a TDD carrier and one or more potential extensions associated with dynamic TDD, sometimes referred to as flexible TDD. That is, the network entity 205 may support subband non-overlapping full-duplex and one or more potential extensions for dynamic TDD. As described herein, dynamic TDD may refer to TDD operation in which a transmission direction associated with a time domain resource may be dynamically assigned or reassigned. For example, the time domain resource may be dynamically assigned or reassigned for uplink communication (e.g., uplink transmission direction) or downlink communication (e.g., downlink transmission direction). In such examples, one or more frequency ranges used for wireless communication between the network entity 205 and the UE 215 may be unconstrained. For example, the wireless communication system 200 may support one or more deployment scenarios for one or more duplex enhancements. In some examples, such deployment scenarios may be evaluated (e.g., using one or more evaluation methods).

[0126] In some examples, dynamic TDD may lead to interference between networks operating on adjacent channels (e.g., inter-operator interference). In some examples, interference between adjacent channel networks may not be coordinated. In such examples, interference may be mitigated at a communication device (e.g., network entity 205, UE 215). For example, the network entity 205 may support one or more potential schemes for supporting subband non-overlapping full duplex and one or more potential extensions to dynamic TDD. In some examples, the one or more potential schemes may include one or more schemes for managing (e.g., mitigating, handling) inter-network entity (e.g., inter-gNB) and inter-UE cross-link interference (CLI). As described herein, CLI may refer to interference experienced at a communication device (e.g., network entity 205, UE 215) when reception at a communication device overlaps (e.g., in the time domain) with transmission at another (e.g., neighboring) communication device. Additionally or alternatively, the network entity 205 may support one or more schemes for managing intra-subband CLI and inter-subband CLI (e.g., for subband non-overlapping full duplex). As described herein, intra-subband CLI may refer to CLI in which interfering transmission and reception occur using multiple (e.g., different) subbands. Additionally or alternatively, inter-subband CLI may refer to CLI in which interfering transmission and reception occur using the same subband. In some examples, the network entity 205 may support one or more operations to enable a scheme for managing CLI (e.g., intra-subband CLI and inter-subband CLI). For example, the network entity 205 may support one or more operations related to coexistence of uplink and downlink subbands in the same channel and adjacent channels.

[0127] In some examples, adjacent channel coexistence may lead to one or more radio frequency constraints due to self-interference, inter-subband CLI, inter-operator CLI, etc. at the network entity 205 (e.g., gNB). Additionally or alternatively, adjacent channel coexistence may lead to one or more radio frequency constraints due to inter-subband CLI and inter-operator CLI at the UE 215. As described herein, self-interference may refer to interference experienced at a communication device (e.g., network entity 205, device capable of supporting full-duplex operation), which may result from signal leakage between an antenna panel used at the communication device for transmission and another antenna panel used at the communication device for reception. Additionally or alternatively, as described herein, inter-operator CLI may refer to interference experienced at a communication device (e.g., network entity 205, UE 215) due to transmissions from another communication device (e.g., neighboring network entity, neighboring UE) that may operate in another communication network. In some examples, a communication device may support one or more antenna, radio frequency, and algorithm designs to mitigate one or more types of CLI. For example, the communications device may support antenna isolation, transmit interference measurement suppression (e.g., for receive), filtering, and digital interference suppression, among other possible examples. In such an example, the wireless communications system 200 may support one or more aspects for deploying duplex extensions for TDD (e.g., using unpaired spectrum).

[0128] As shown in the example of FIG. 2, the network entity 205 may support multi-user MIMO (MU-MIMO) communication with the UE 215. For example, the network entity 205 may support downlink MU-MIMO, in which the network entity may simultaneously transmit downlink communications to the UE 215-a and the UE 215-b. Additionally or alternatively, the network entity 205 may support uplink MU-MIMO, in which the network entity may simultaneously receive uplink communications to the UE 215-a and the UE 215-b. In some examples, the network entity 205 may support downlink and uplink MU-MIMO using full-duplex operation. For example, the network entity 205 may support full-duplex operation, in which the network entity 205 may simultaneously receive uplink communications from the UE 215-a and transmit downlink communications to the UE 215-b. The network entity 205 may use multiple beams (e.g., generated using one or more antenna panels) to support simultaneous communication with the UE 215. For example, the network entity 205 may use a first antenna panel to generate a beam 210-a for receiving uplink communications from the UE 215-a and a second antenna panel to generate a beam 210-b for transmitting downlink communications to the UE 215-b. In some examples, full-duplex communications at the network entity 205 may be spatially separated (e.g., by using different beams for downlink transmission and uplink reception at the network entity 205), but the network entity 205 may experience self-interference 235. For example, the network entity 205 may experience self-interference 235 due to signal leakage between the second antenna panel used for downlink transmission to the UE 215-b and the first antenna panel used for uplink reception from the UE 215-a.Additionally or alternatively, network entity 205 may experience clutter interference due, for example, to the presence of reflectors in the environment of network entity 205. As described herein, clutter interference may refer to interference caused by a portion of a signal transmitted from network entity 205 reflecting back to network entity 205 from a reflector (e.g., a reflective surface).

[0129] In some examples, to reduce self-interference 235 experienced at the network entity 205 (e.g., due to full-duplex communication), the network entity 205 may use multiple (e.g., different) subbands for uplink reception and downlink transmission at the network entity 205. For example, the network entity 205 may support SBFD operation, in which the network entity may use one or more subbands (e.g., uplink subbands, flexible subbands) for uplink reception from the UE 215-a and use one or more other subbands (e.g., downlink subbands, flexible subbands) for downlink transmission to the UE 215-b. That is, the network entity 205 may support simultaneous transmission and reception of downlink and uplink communications, respectively, on a subband-by-subband basis. For example, the network entity 205 may support SBFD operation, in which the network entity 205 may receive uplink communications from the UE 215-a using one or more uplink subbands (or one or more flexible subbands) and transmit downlink communications to the UE 215-b using one or more downlink subbands (or one or more flexible subbands) simultaneously using the same TTI (e.g., the same slot or the same symbol). In some examples, the network entity 205 may use SBFD to achieve spatial separation (e.g., using different beams) and frequency separation (e.g., using different subbands) to reduce self-interference 235. Additionally or alternatively, in some examples, SBFD operation may provide an increased uplink duty cycle, which may lead to latency reduction. For example, the network entity 205 may be configured to transmit one or more downlink signals in a TTI (e.g., slot) configured for uplink communications, which may enable latency reduction and one or more uplink coverage improvements.Additionally or alternatively, SBFD operation may provide enhanced system capacity, increased resource utilization, and increased spectral efficiency, among other possible benefits. In some examples, enabling flexible and dynamic uplink and downlink resource adaptation (e.g., based on uplink or downlink traffic conditions) may lead to increased reliability of communications between the UE 215 and the network entity 205.

[0130] In some examples, the network entity 205 may be configured to support SBFD operation, but the network entity 205 and the UE 215 may be configured with one or more multiplexing rules that may be based on (e.g., may assume) half-duplex operation in the network entity 205. For example, within a TDD carrier, the network entity 205 and the UE 215 may be configured with one or more multiplexing rules that indicate which TTIs may be used for transmission or reception. That is, the network entity 205 and the UE 215 may be configured to perform downlink and uplink channel (or downlink and uplink reference signal) prioritization and multiplexing according to one or more rules for half-duplex operation. In some examples, the one or more rules for half-duplex operation may indicate that synchronization signal block (SSB) transmissions from the network entity 205 may be prioritized over (e.g., may cancel) uplink transmissions from the UE 215. That is, the UE 215 may be configured to prioritize reception of SSBs from the network entity 205 over transmission of uplink signals to the network entity 205. For example, at the UE 215, SSB reception may be prioritized over transmission of a physical uplink shared channel (PUSCH) signal, a physical uplink control channel (PUCCH) signal, a random access preamble (e.g., a physical random access channel (PRACH) signal), and a sounding reference signal (SRS), among other examples of uplink signals. In some examples, the TTI may be configured (e.g., at the UE 215) for uplink or downlink communications using a slot format indicator (SFI). For example, the network entity 205 may signal (e.g., dynamically) the allocation of resources for one or more TTIs using the SFI. In some examples, the SFI may configure the allocated resources as downlink resources, uplink resources, or flexible resources.In some cases, resources configured as flexible may be overridden (e.g., reassigned as uplink or downlink). For example, the network entity 205 may transmit to one or both of the UEs 215 an SFI for uplink (SFI-U), which may indicate uplink resources for uplink communication during the TTI. In one such example, in accordance with one or more rules for half-duplex operation, the UE 215 may refrain from monitoring the SFI-U during a TTI that may be configured for reception of an SSB (e.g., may not be expected to receive it).

[0131] Additionally or alternatively, the network entity 205 may transmit to the UE 215 an SFI for downlink (SFI-D), which may indicate downlink resources for downlink communication during the TTI. In some examples, in accordance with one or more rules for half-duplex operation, the UE 215 may refrain from monitoring (e.g., may not expect to receive) the SFI-D during a TTI that may include (e.g., may be configured with) one or more random access occasions (e.g., valid random access occasions) for transmission of a random access preamble. In some examples, the one or more rules for half-duplex may indicate that the UE 215 may refrain from monitoring (e.g., may not expect to receive) the SFI-U during a TTI that may be configured (e.g., using an RRC configuration that transmits using a master information block (MIB)) with one or more control resource sets (CORESETs), such as CORESET0. Additionally or alternatively, the UE 215 may refrain from monitoring (e.g., not expect to receive) the SFI-U during a TTI that may be configured for downlink communications (e.g., using an RRC configuration) in accordance with one or more rules for half-duplex. For example, the UE 215 may receive an indication of one or more RRC parameters (e.g., a TDD-UL-DL-ConfigCommon information element (IE), a TDD-UL-DL-ConfigDedicated IE) that may identify uplink and downlink TDD configurations (e.g., UE-specific configurations) for one or more TTIs. That is, the one or more RRC parameters may configure one or more TTIs for downlink or uplink communications in the UE 215. In some examples, downlink communications configured using an RRC configuration in accordance with one or more rules for half-duplex may be prioritized over uplink communications, such as transmission of a PUCCH signal, a random access preamble (e.g., a PRACH), or an SRS.Additionally or alternatively, uplink communications configured using RRC configuration in accordance with one or more rules for half-duplex may be prioritized over downlink communications, including monitoring the PDCCH (e.g., using CORESET) and receiving a PDSCH signal, a channel state information reference signal (CSI-RS), or a positioning reference signal (PRS) (e.g., in the absence of a measurement gap). For example, in accordance with one or more rules for half-duplex, the UE 215 may refrain from monitoring (e.g., may not expect to receive) the SFI-D during a TTI that may be configured for uplink communications (e.g., using RRC configuration). It should be understood that the names of IEs described herein may vary based on the implementation of one or more devices (e.g., the UE 215, the network entity 205), and the examples described herein should not be construed as limiting the scope of the claims or the present disclosure.

[0132] In some examples, the network entity 205 may use RRC signaling (e.g., a TDD-UL-DL-ConfigCommon IE, a TDD-UL-DL-ConfigDedicated IE) to configure the UE 215 with a flexible TTI. In one such example, a previous resource allocation (e.g., a previous uplink resource allocation or a previous downlink resource allocation) may be overwritten. For example, the RRC configuration for the flexible TTI may overwrite a previous higher layer configuration (e.g., a previous RRC configuration) for the TTI, such as a higher layer configuration for periodic (or semi-persistent) downlink communications or periodic (or semi-persistent) uplink communications. Additionally or alternatively, in some examples, the network entity 205 may send an SFI to dynamically configure the flexible TTI for uplink or downlink communications. However, in some examples, the UE 215 may fail to detect the SFI. In such an example, one or more rules for half duplex may indicate that the periodic (or semi-persistent) downlink and uplink communications previously configured for the flexible TTI may be canceled. That is, if UE 215 fails to detect an SFI for a TTI, flexible RRC configuration may take precedence over periodic or semi-persistent communications configured during the TTI, such as higher layer configured downlink communications (e.g., reception of CSI-RS or PRS) and higher layer configured uplink communications (e.g., transmission of PUSCH, PUCCH, PRACH, and SRS signals in the absence of the EnableConfiguredUL-r16 IE).

[0133] In some examples, the network entity 205 may use an SFI that may indicate resources for either downlink or uplink communications during a TTI. For example, the network entity 205 may transmit an SFI for flexible communications (SFI-F) to the UE 215, which may configure one or more TTIs as flexible. In some examples, one or more TTIs may be previously configured for downlink or uplink communications (e.g., using an RRC configuration such as the tdd-UL-DL-configurationCommon IE). In such examples, the SFI-F may override the previous configuration. In some examples, one or more rules for half-duplex may indicate that the UE 215 may refrain from monitoring (e.g., not expect to receive) a dynamic grant (e.g., downlink control information (DCI)) indicating downlink resources for downlink communications (e.g., reception of a PDSCH signal or CSI-RS) during a TTI that may be configured for uplink communications using an SFI (e.g., SFI-U). Additionally or alternatively, the UE 215 may refrain from monitoring (e.g., may not expect to receive) a dynamic grant (e.g., DCI) indicating uplink resources for uplink communications (e.g., PUSCH signals, PUCCH signals, PRACH signals, SRS) during a TTI that may be configured for downlink communications using an SFI (e.g., SFI-D). However, in some examples, in accordance with one or more rules for half-duplex operation, the SFI may be used to override communications (e.g., periodic or semi-persistent transmissions of uplink or downlink signals) configured using higher layer configuration (e.g., RRC configuration). For example, in accordance with one or more rules for half-duplex operation, the SFI-F or SFI-D may take precedence over higher layer configured uplink communications (e.g., transmissions of PUSCH signals, PUCCH signals, PRACH, SRS).Additionally or alternatively, SFI-F or SFI-U may take priority over higher layer configured downlink communications (e.g., CORESET monitoring, transmission of signals configured using semi-persistent scheduling (SPS), transmission of CSI-RS).

[0134] In some examples, in accordance with one or more rules for half-duplex operation, the UE 215 may be configured to prioritize an uplink dynamic grant (e.g., a DCI) indicating uplink resources for uplink communication during a TTI over downlink communication (e.g., reception of a PDCCH signal, an SPS, a CSI-RS, or a PRS) that may be configured for that TTI using higher layer signaling (e.g., RRC configuration). Additionally or alternatively, the UE 215 may be configured to prioritize a downlink dynamic grant (e.g., a DCI) indicating downlink resources for downlink communication during a TTI over uplink communication (e.g., transmission of a PUSCH signal, a PUCCH signal, a PRACH, or an SRS) that may be configured for that TTI using higher layer signaling (e.g., RRC configuration). In some examples, one or more rules for half-duplex operation may apply to downlink and uplink communication configured for different component carriers of the same radio frequency spectrum band.

[0135] However, in some examples, one or more rules for half-duplex may lead to an unnecessary increase in latency. For example, the network entity 205 may be configured for SBFD operation, where the network entity can simultaneously use one or more uplink subbands (or flexible subbands) of an SBFD TTI (e.g., slots or symbols configured for SBFD communication) for uplink communication with a UE (e.g., UE 215-a) and one or more downlink subbands (or flexible subbands) of the same SBFD TTI for downlink communication with another UE (e.g., UE 215-b). In such examples, the downlink and uplink channel (or downlink reference signal and uplink reference signal) multiplexing constraints imposed by one or more rules for half-duplex may lead to reduced resource utilization and an unnecessary increase in latency. Therefore, one or more rules for half-duplex operation may be modified (or lifted) for SBFD communication so that the UE 215 may receive an uplink configuration and a downlink configuration for the same TTI. That is, multiple configurations may be enabled for UE relaying or SBFD operation (or other full-duplex operation or mode) at network entity 205 such that network entity 205 may conduct simultaneous uplink and downlink communications in an SBFD TTI (e.g., an SBFD symbol or slot). In one such example, according to one or more modified rules (or in the absence of one or more rules for half-duplex), UE 215-b may receive an uplink configuration for uplink transmission during the TTI and a downlink configuration for downlink reception during the TTI. Furthermore, in one such example, network entity 205 may configure UE 215 (or UE 215 may be configured otherwise) with one or more other rules, such as prioritization rules 245, for use for SBFD operation (or other full-duplex operation at network entity 205).For example, the UE 21-b may use the prioritization rule 245 to determine whether to transmit according to the uplink configuration during the TTI or receive according to the downlink configuration during the TTI.

[0136] 2, network entity 205 may indicate to UE 215-b downlink resources 265 for downlink communication during one or more TTIs (e.g., TTI 240-a, TTI 240-b, and TTI 240-c) and uplink resources 260 for uplink communication during one or more other TTIs (e.g., TTI 240-d and TTI 240-e). In some examples, network entity 205 may use an RRC configuration, such as via a TDD-UL-DL-ConfigCommon IE or a TDD-UL-DL-ConfigDedicated IE, to indicate downlink resources 265 for downlink communication and uplink resources 260 for uplink communication. Additionally or alternatively, network entity 205 may indicate (e.g., further indicate) to UE 215-b one or more of the TTIs (e.g., a subset of the TTIs configured in downlink resources 265) that may be used for SBFD operation. For example, the network entity 205 may transmit to the UE 215 a control message 225 that may identify one or more TTIs 240 to be used for SBFD communications between the UE 215-b and the network entity 205. For example, the control message 225 may configure the TTIs 240-a, 240-b, and 240-c for SBFD operation. In one such example, the control message 225 may indicate frequency locations of the downlink subbands 255-a and 255-b that may be used by the UE 215-b (or the UE 215-a) for downlink communications. Additionally or alternatively, the control message 225 may indicate frequency locations of the uplink subbands 250 that the UE 215-b (or the UE 215-a) may use for uplink communications. For example, during a TTI configured for SBFD communication, UE 215-a may use uplink subband 250 for uplink communication with network entity 205, and UE 215-b may use one or more of downlink subbands 255 for downlink communication with network entity 205.In some examples, a portion of the TTI may be configured for SBFD. For example, the TTI 240-a may correspond to a slot or a symbol (or some other suitable time duration). In one such example, the control message 225 may indicate that the TTI 240-a or a portion of the TTI 240-a (e.g., one or more symbols within a slot) may be used for SBFD. That is, the control message 225 may indicate time and frequency locations for the downlink subband 255 and the uplink subband 250. Additionally or alternatively, the control message 225 may indicate time and frequency locations of guard bands or flexible subbands that may be configured for SBFD. In some examples, the control message 225 may indicate TDD operation at the UE 215-b. For example, the control message 225 may correspond to a TDD configuration that the network entity 205 may send using RRC signaling. The RRC signaling may include a TDD-UL-DL-ConfigCommon IE or a TDD-UL-DL-ConfigDedicated IE. Additionally or alternatively, the network entity 205 may transmit the control message 225 using broadcast signaling.

[0137] In such an example, UE 215-b (e.g., and UE 215-a) may be able to receive downlink configuration and uplink configuration for TTI 240 (e.g., a TTI configured for SBFD communication). For example, UE 215-b may receive a first indication 230 of uplink resources 260 to be used for uplink communication during TTI 240-a and a second indication 231 of downlink resources 265 for downlink communication during TTI 240-a. In one such example, UE 215-b may use prioritization rule 245 to determine whether to communicate according to first indication 230 or second indication 231 during TTI 240-a. That is, UE 215-b may communicate during TTI 240-a according to one of first indication 230 or second indication 231 based on prioritization rule 245. For example, based on the prioritization rule 245, the UE 215-b may receive downlink signals using one or more of the downlink subbands 255 during the TTI 240-a, or may transmit uplink signals using the uplink subband 250 during the TTI 240-a.

[0138] In some examples, the UE 215-b may receive an indication of downlink resources 265 in one or more of the downlink subbands 255 to be used for reception of SSBs (e.g., from the network entity 205) during the TTI 240-a. Additionally or alternatively, the UE 215-b may receive an indication of uplink resources 260 in the uplink subband 250 to be used for uplink communication (e.g., periodic uplink transmissions) during the TTI 240-a. That is, the SSBs transmitted from the network entity 205 may overlap with the TTI configured for uplink communication using the SFI-U. For example, the first indication 230 may be for transmission of an uplink signal within the uplink subband 250 during the TTI 240-a. In some examples, the first indication 230 may include an SFI-U related to the TTI 240-a. Additionally or alternatively, the second indication 231 may be for reception of SSBs during TTI 240-a in one or more of downlink subbands 255. For example, UE 215-b may be configured for reception of SSBs using one or more of downlink subbands 255 during TTI 240-a (e.g., an SBFD symbol) and may also be configured with an uplink transmission (e.g., transmission of a PUSCH signal, a PUCCH signal, a PRACH, or an SRS) using uplink subband 250 of TTI 240-a (e.g., the same SBFD symbol).

[0139] Additionally or alternatively, the UE 215-b may receive an indication of a random access occasion (e.g., a valid random access occasion) in the uplink subband 250 during a TTI 240-a (e.g., an SBFD symbol), which may also be configured for downlink communications using SFI-D. That is, the first indication 230 may be for transmission of a random access preamble in the uplink subband 250 during the TTI 240-a, and the second indication 231 may be for reception of a downlink signal in one or more of the downlink subbands 255 during the TTI 240-a. In one such example, the second indication 231 may include the SFI-D associated with the TTI 240-a.

[0140] In some examples, the UE 215-b may receive (e.g., from the network entity 205) a MIB that may identify a CORESET (e.g., CORESET0) in one or more of the downlink subbands 255 during the TTI 240-a, which may be configured for uplink communication using the SFI-U. For example, the network entity 205 may use the SFI-U to indicate uplink resources 260 in the uplink subband 250 that will be used for uplink communication during the TTI 240-a. That is, the first indication 230 may be for transmission of an uplink signal in the uplink subband 250 during the TTI 240-a, and the second indication 231 may be for monitoring a downlink control channel (e.g., CORESET) in one or more of the downlink subbands 255 during the TTI 240-a. In one such example, the first indication 230 may include an SFI-U related to the TTI 240-a.

[0141] In some examples, the first instruction 230 may be for transmission of an uplink signal in the uplink subband 250 during the TTI 240-a. In such examples, the first instruction 230 may include an SFI-U, an SFI-F, an RRC configuration, or a dynamic grant related to the TTI 240-a. Additionally or alternatively, the second instruction 231 may be for reception of a downlink signal in one or more of the downlink subbands 255 during the TTI 240-a. In such examples, the second instruction 231 may include an SFI-D, an SFI-F, an RRC configuration, or a dynamic grant related to the TTI 240-a. For example, the UE 215-b may receive an RRC configuration that may indicate downlink resources for downlink communication using one or more of the downlink subbands 255 during the TTI 240-a (e.g., an SBFD symbol), which may overlap with uplink communication (e.g., transmission of a PUCCH signal, a PRACH, or an SRS) configured in the uplink subband 250 during the TTI 240-a (e.g., during the same SBFD symbol). That is, the second indication 231 may include a downlink RRC configuration that may be indicated to the UE 215-b using the SFI-U. In such an example, the prioritization rule 245 may include a rule indicating that the TTI 240-a may be used for uplink communication (e.g., uplink communication may be prioritized over downlink communication). In some examples, such a rule may be used in the network entity 205 to dynamically override a previously configured communication (e.g., may be used for dynamic override).

[0142] Additionally or alternatively, the UE 215-b may receive an RRC configuration that may indicate uplink resources 260 for uplink communications using the uplink subband 250 during the TTI 240-a (e.g., an SBFD symbol), which may overlap with downlink communications (e.g., CORESET monitoring, or transmission of PDSCH signals, CSI-RS, or PRS in the absence of a measurement gap) configured in one or more of the downlink subbands 255 during the TTI 240-a (e.g., during the same SBFD symbol). That is, the first indication 230 may include an uplink RRC configuration that may be indicated to the UE 215-b using the SFI-D. In such an example, the prioritization rule 245 may include a rule indicating that the TTI 240-a may be used for downlink communications (e.g., downlink communications may be prioritized over uplink communications). In some examples, such a rule may be used in the network entity 205 to dynamically override previously configured communications (e.g., for dynamic override).

[0143] In some examples, such as in the case of flexible TTI, the UE 215-b may fail to detect the SFI. In such examples, the UE 215 may be configured with periodic (or semi-persistent) downlink and uplink communications for the flexible TTI. For example, if the UE 215-b fails to detect the SFI for the TTI 240-a, the UE 215-b may receive a flexible RRC configuration for downlink communications (e.g., with an SPS or for transmission of a CSI-RS or a PRS) using one or more of the downlink subbands 255 during the TTI 240-a, which may overlap (e.g., in time) with the uplink subband 250. In one such example, the uplink subband 250 may be configured for uplink communications (e.g., transmission of a PUSCH signal, a PUCCH signal, a PRACH, or an SRS) during the TTI 240-a (e.g., the same SBFD symbol). That is, the second indication 231 may include a flexible RRC configuration for downlink communications during the TTI 240-a.

[0144] In some examples, the first indication 230 may include an SFI-U, and the second indication 231 may include a downlink dynamic grant. That is, the UE 215-b may receive the SFI-U related to the TTI 240-a and a downlink dynamic grant (e.g., DCI) for transmission of a PDSCH signal or a CSI-RS in one or more of the downlink subbands 255 during the TTI 240-a. Additionally or alternatively, the second indication 231 may include an SFI-D, and the first indication 230 may include an uplink dynamic grant. That is, the UE 215-b may receive the SFI-D related to the TTI 240-a and an uplink dynamic grant (e.g., DCI) for transmission of a PUSCH signal, a PUCCH signal, a PRACH, or an SRS in the uplink subband 250 during the TTI 240-a. In some examples, UE 215-b may receive SFI-F or SFI-D related to TTI 240 and may be configured (e.g., via RRC signaling) for transmission of a PUSCH signal, a PUCCH signal, a PRACH, or an SRS in uplink subbands 250 of TTI 240-a. Additionally or alternatively, UE 215-b may receive SFI-F or SFI-U related to TTI 240 and may be configured (e.g., via RRC signaling) to monitor CORESET for downlink signals, receive scheduled signals using SPS, or receive CSI-RS in one or more of downlink subbands 255 during TTI 240-a.

[0145] In some examples, the first indication 230 may include an uplink dynamic grant (e.g., a DCI). That is, the UE 215-b may receive an uplink dynamic grant for uplink transmission using the uplink subband 250 during the TTI 240-a. Further, the UE 215-b may be configured (e.g., using RRC signaling) with downlink communication (e.g., transmission of a signal configured using SPS, transmission of a PDCCH signal, a CSI-RS, a PRS) in one or more of the downlink subbands 255 using the TTI 240-a. Additionally or alternatively, the second indication 231 may include a downlink dynamic grant (e.g., a DCI). That is, the UE 215-b may receive a downlink dynamic grant for downlink reception using one or more of the downlink subbands 255 during the TTI 240-a. Additionally or alternatively, UE 215-b may be configured (e.g., using RRC signaling) with uplink communications (e.g., transmission of a PUSCH signal, a PUCCH signal, a PRACH, or an SRS) in uplink subband 250 using TTI 240-a. In some examples, first indication 230 may be for a first component carrier of a radio frequency spectrum band, and second indication 231 may be for a second component carrier of a radio frequency spectrum band that may be different from the first component carrier. In some examples, allowing UE 215 to receive uplink and downlink configurations for the same TTI may enable flexible and dynamic uplink and downlink resource adaptation (e.g., according to uplink and downlink traffic conditions), among other possible benefits.

[0146] 3A and 3B show example SBFD configurations 300 supporting multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. SBFD configurations 300 (e.g., SBFD configurations 300-a and 300-b) may be implemented in one or more aspects of wireless communication systems 100 and 200. For example, SBFD configuration 300 may be implemented in a network entity or UE, or a booth, which may be examples of the corresponding devices described with reference to FIGS. 1 and 2. SBFD configuration 300 may include features for improved communication between a network entity and a UE, among other possible benefits.

[0147] In some examples, a network entity (e.g., a gNB) may support SBFD or another full-duplex mode using SBFD slots or symbols, sometimes referred to as TTIs. That is, the network entity (e.g., a gNB) may receive uplink communications while transmitting downlink communications. In such examples, to reduce overhead, the network entity and UE may support an SBFD configuration 300 that may provide for configured downlink opportunities and configured uplink opportunities to coexist on a TTI (e.g., the same symbol). As shown in the example of FIG. 3A, the SBFD configuration 300-a may provide uplink opportunities using uplink subband 315-a and downlink opportunities using downlink subband 320-a or downlink subband 320-b, or both. That is, the UE may receive an indication of uplink resources 325 for transmission of uplink signals using uplink subband 315-a during TTI 305-a and downlink resources 330 for reception of downlink signals using one or both of downlink subband 320-a and downlink subband 320-b during TTI 305-a. Uplink subband 315-a, downlink subband 320-a, and downlink subband 320-b may correspond to different component carriers within the same radio frequency spectrum band (e.g., within bandwidth 310-a).

[0148] Additionally or alternatively, as shown in the example of FIG. 3B , the SBFD configuration 300-b may provide uplink opportunities using uplink subband 315-b and downlink opportunities using downlink subband 320-c. That is, the UE may receive an indication of uplink resources 325 for transmission of uplink signals using uplink subband 315-b during TTI 305-b and downlink resources 330 for reception of downlink signals using downlink subband 320-c during TTI 305-b. The uplink subband 315-b and downlink subband 320-c may correspond to different component carriers within the same radio frequency spectrum band (e.g., within bandwidth 310-b).

[0149] As shown in the example of FIG. 3A , a configured uplink opportunity (e.g., uplink resource 325) in uplink subband 315-a may coexist with a downlink opportunity (e.g., downlink resource 330) in downlink subband 320-a and downlink subband 320-b of TTI 305-a. In some examples, TTI 305-a (e.g., an SBFD symbol) may be configured for downlink communication using an SFI-D. For example, a UE may receive an RRC configuration indicating uplink resources 325 for transmission of an uplink signal using uplink subband 315-a during TTI 305-a and may receive an SFI-D related to TTI 305-a. In one such example, the UE may use one or more prioritization rules to determine whether to receive a downlink signal during TTI 305-a according to the SFI-D (e.g., a downlink dynamic grant) or transmit an uplink signal during TTI 305-a according to the RRC configuration. For example, a beam failure recovery procedure may fail to be triggered at the UE. In one such example, according to one or more prioritization rules, the UE may determine to communicate with a network entity according to the SFI-D during TTI 305-a. For example, the UE may use the SFI-D for reception of downlink signals during TTI 305-a. In some examples, the downlink signals may include PDSCH signals, SPS signals, or CSI-RS, which may be indicated to the UE using a dynamic grant. In some other examples, beam failure recovery may be triggered at the UE. In such an example, the UE may refrain from receiving (e.g., drop) downlink signals and may transmit uplink signals (e.g., SRS or PRACH) for the triggered beam failure recovery procedure during TTI 305-a (e.g., on the TTI configured using the SFI-D).

[0150] Additionally or alternatively, configured downlink opportunities (e.g., downlink resources 330) in one or both of downlink subbands 320-a and 320-b during TTI 305-a may coexist with uplink opportunities (e.g., uplink resources 325) in uplink subband 315-a of TTI 305-a. For example, the UE may receive an RRC configuration identifying flexible resources (e.g., flexible symbols) for transmitting uplink signals or receiving downlink signals during TTI 305-a (e.g., in the absence of a slot format provided using an SFI). In one such example, configured downlink opportunities (e.g., downlink resources 330) in one or both of downlink subbands 320-a and 320-b during TTI 305-a may coexist with uplink opportunities (e.g., uplink resources 325) in uplink subband 315-a during TTI 305-a. In such an example, if a beam failure recovery procedure fails to be triggered in the UE, the UE may determine to use the RRC configuration for flexible communication during the TTI 305-a (e.g., according to one or more prioritization rules). For example, the UE may determine to receive a configured downlink signal (e.g., an SPS signal or a CSI-RS). Additionally or alternatively, if a beam failure recovery procedure is triggered in the UE, the UE may decide to refrain from receiving (e.g., drop) the downlink signal and may transmit an uplink signal (e.g., an SRS signal or a PRACH) for beam failure recovery using the TTI 305-a. That is, the one or more prioritization rules may include that, if a beam failure recovery procedure is not triggered, during the TTI 305-a, reception of a downlink signal using the downlink subband 320-a or the downlink subband 320-b (or both) may be prioritized over transmission of an uplink signal using the uplink subband 315-a.Additionally or alternatively, the prioritization rule may include that, if a beam failure recovery procedure is triggered, transmission of an uplink signal may be prioritized over reception of a downlink signal during TTI 305-a. In some examples, the prioritization rule may be based on a priority or type of communication channel associated with a communication channel to be used for transmission of an uplink signal and another communication channel to be used for reception of a downlink signal. Additionally or alternatively, the prioritization rule may be based on one or more other suitable types of rules. In some examples, using a prioritization rule to determine whether to receive a downlink signal or transmit an uplink signal during TTI 305-a may lead to increased resource utilization and reduced latency, among other possible benefits.

[0151] FIG. 4 illustrates an example process flow 400 supporting multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. In some examples, the process flow 400 may implement one or more aspects of the wireless communication system 100, the wireless communication system 200, and the SBFD configuration 300. For example, the process flow 400 may include example operations associated with a network entity 405 and a UE 415, which may be examples of corresponding devices described with reference to FIGS. 1, 2, 3A, and 3B. The operations performed at the network entity 405 and the UE 415 can support, among other benefits, improvements to communications between the UE 415 and the network entity 405. In the following description of the process flow 400, the operations between the UE 415 and the network entity 405 may occur in a different order than the example order shown. Additionally or alternatively, the operations performed by the UE 415 and the network entity 405 may be performed in a different order or at different times. Some operations may be omitted. 4, network entity 405 may be configured for SBFD operation, where network entity 405 can communicate with multiple UEs (e.g., including UE 415) simultaneously using an SBFD TTI (e.g., slots or symbols configured for SBFD communication). For example, network entity 405 may use one or more uplink subbands (or one or more flexible subbands) for uplink communications with a UE and use one or more downlink subbands (or one or more flexible subbands) of the same SBFD TTI for downlink communications with another UE.

[0152] At 420, the UE 415 may receive a control message identifying at least one TTI (e.g., at least one symbol or at least one slot) to be used for SBFD communications at the network entity 405. The control message may be an example of a control message described throughout this disclosure, including with reference to FIG. 2. For example, the control message may correspond to a TDD configuration. For example, the network entity 405 may send the control message using RRC signaling, which may include a TDD-UL-DL-ConfigCommon IE or a TDD-UL-DL-ConfigDedicated IE. Additionally or alternatively, the network entity 405 may send the control message using broadcast signaling.

[0153] At 425, the UE 415 may receive a first indication of uplink resources for uplink communication during at least one SBFD TTI. In some examples, the first indication may be an example of a first indication described throughout this disclosure, including with reference to FIG. 2. For example, the first indication may be for transmission of an uplink signal in at least one uplink subband (or at least one flexible subband) during the at least one SBFD TTI. Additionally or alternatively, the first indication may include an uplink SFI (e.g., SFI-U), a flexible SFI (e.g., SFI-F), an RRC configuration, or a dynamic grant related to the at least one SBFD TTI.

[0154] At 430, the UE 415 may receive a second indication of downlink resources for downlink communication during the at least one SBFD TTI. The second indication may be an example of a second indication described throughout this disclosure, including with reference to FIG. 2. For example, the second indication may be for reception of a downlink signal in at least one downlink subband (or at least one flexible subband) during the at least one SBFD TTI. Additionally or alternatively, the second indication may include a downlink SFI (e.g., SFI-D), a flexible SFI (e.g., SFI-F), an RRC configuration, or a dynamic grant related to the at least one SBFD TTI.

[0155] At 435, the UE 415 may communicate with the network entity 405 during at least one SBFD TTI according to the first instruction or the second instruction based on one or more prioritization rules. In some examples, the prioritization rule may be an example of a prioritization rule described throughout this disclosure, including with reference to FIG. 2. For example, the prioritization rule may include that, if a beam failure recovery procedure is not triggered (e.g., at the UE 415), reception of a downlink signal is prioritized over transmission of an uplink signal during the at least one SBFD TTI. Additionally or alternatively, the prioritization rule may include, if a beam failure recovery procedure is triggered (e.g., at the UE 415), transmission of an uplink signal is prioritized over reception of a downlink signal during the at least one SBFD TTI. In some examples, the prioritization rule may include that reception of a downlink signal or transmission of an uplink signal is prioritized based on respective channel priorities associated with each of the downlink and uplink signals.

[0156] In some examples, at 440, the UE 415 may transmit an uplink signal to the network entity 405 using one or more uplink subbands (or one or more flexible subbands) during at least one SBFD TTI based on the prioritization rule. The uplink signal may be an example of an uplink signal described throughout this disclosure, including with reference to FIG. 2. For example, the uplink signal may include a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0157] In some other examples, at 445, the UE 415 may receive downlink signals from the network entity 405 using one or more downlink subbands (or one or more flexible subbands) during at least one SBFD TTI. The downlink signals may be an example of downlink signals described throughout this disclosure, including with reference to FIG. 2. For example, the downlink signals may include a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS. In some examples, using a prioritization rule to determine whether to receive a downlink signal or transmit an uplink signal during at least one SBFD TTI may lead to increased resource utilization and reduced latency, among other possible benefits.

[0158] 5 shows a block diagram 500 of a device 505 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The device 505 may be an example of an aspect of a UE 115 described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0159] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with multiplexing rules for SBFD communications). The information may be passed to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

[0160] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with multiplexing rules for SBFD communications). In some examples, the transmitter 515 may be collocated with the receiver 510 within a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0161] The communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components thereof may be examples of means for implementing various aspects of the multiplexing rules for SBFD communications described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0162] In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0163] Additionally or alternatively, in some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). If implemented in code executed by a processor, the functionality of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).

[0164] In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510 and send the information to the transmitter 515, or may be integrated in combination with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations described herein.

[0165] The communications manager 520 may support wireless communications at a first network node (e.g., device 505) according to examples disclosed herein. For example, the communications manager 520 may be configured as, or otherwise support a means for receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node. The communications manager 520 may be configured as, or otherwise support a means for receiving a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. The communications manager 520 may be configured as, or otherwise support a means for receiving a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. The communications manager 520 may be configured as, or otherwise support a means for communicating with a second network node during at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules.

[0166] By including or configuring a communications manager 520 according to examples described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for more efficient utilization of communications resources.

[0167] 6 shows a block diagram 600 of a device 605 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The device 605 may be an example of an aspect of the device 505 or UE 115 described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0168] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with multiplexing rules for SBFD communications). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0169] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with multiplexing rules for SBFD communications). In some examples, the transmitter 615 may be collocated with the receiver 610 within a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0170] The device 605 or its various components may be an example of a means for implementing various aspects of the multiplexing rules for SBFD communications described herein. For example, the communications manager 620 may include a control message component 625, an uplink component 630, a downlink component 635, a prioritization component 640, or any combination thereof. The communications manager 620 may be an example of an aspect of the communications manager 520 described herein. In some examples, the communications manager 620, or its various components, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610 and send information to the transmitter 615, or may be integrated in combination with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations described herein.

[0171] The communications manager 620 may support wireless communications at a first network node (e.g., device 605) according to examples disclosed herein. The control message component 625 may be configured as, or otherwise supporting a means for receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node. The uplink component 630 may be configured as, or otherwise supporting a means for receiving a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. The downlink component 635 may be configured as, or otherwise supporting a means for receiving a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. The prioritization component 640 may be configured as, or otherwise supporting a means for communicating with a second network node during at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules.

[0172] FIG. 7 shows a block diagram 700 of a communications manager 720 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. Communications manager 720 may be an example of aspects of communications manager 520, communications manager 620, or both, described herein. Communications manager 720 or its various components may be an example of a means for implementing various aspects of the multiplexing rules for SBFD communications described herein. For example, communications manager 720 may include a control message component 725, an uplink component 730, a downlink component 735, a prioritization component 740, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0173] The communications manager 720 may support wireless communications at a first network node according to examples disclosed herein. The control message component 725 may be configured as, or otherwise supporting a means for receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node. The uplink component 730 may be configured as, or otherwise supporting a means for receiving a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. The downlink component 735 may be configured as, or otherwise supporting a means for receiving a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. The prioritization component 740 may be configured as, or otherwise supporting a means for communicating with a second network node during at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules.

[0174] In some examples, the uplink resources are within at least one uplink subband or at least one flexible subband. Further, the downlink resources are within at least one downlink subband or at least one flexible subband. In some examples, the first instruction is for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot. Additionally or alternatively, the second instruction is for reception of a synchronization signal block in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot. In some examples, the first instruction includes an uplink SFI related to the at least one symbol or at least one slot. In some examples, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0175] In some examples, the first instruction is for transmission of a random access preamble in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot. In some examples, the second instruction is for reception of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot. Additionally or alternatively, the second instruction includes a downlink SFI related to the at least one symbol or at least one slot.

[0176] In some examples, the first instruction is for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot. In some examples, the second instruction is for monitoring a downlink control channel in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot. Additionally or alternatively, the first instruction includes an uplink SFI related to the at least one symbol or at least one slot.

[0177] In some examples, the first instruction is for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for reception of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0178] In some examples, the first indication includes an uplink SFI related to at least one symbol or at least one slot. Further, the second indication includes an RRC configuration related to at least one symbol or at least one slot. In some examples, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0179] In some examples, the first indication includes an RRC configuration related to at least one symbol or at least one slot. Further, the second indication includes a downlink SFI related to at least one symbol or at least one slot. In some examples, the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0180] In some examples, the second indication includes a flexible RRC configuration related to at least one symbol or at least one slot. Additionally or alternatively, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0181] In some examples, the first indication includes an uplink SFI related to at least one symbol or at least one slot, and the second indication includes a dynamic grant related to at least one symbol or at least one slot. Further, the downlink signal includes a PDSCH signal or a CSI-RS.

[0182] In some examples, the first indication includes an SFI or a flexible SFI related to at least one symbol or at least one slot. Further, the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0183] In some examples, the first indication includes a dynamic grant related to at least one symbol or at least one slot, the second indication includes a downlink SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0184] In some examples, the second indication includes a downlink SFI or a flexible SFI related to at least one symbol or at least one slot. Further, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0185] In some examples, the first indication includes a dynamic grant relating to at least one symbol or at least one slot. Further, the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, a CSI-RS, or a PRS.

[0186] In some examples, the second indication includes a dynamic grant relating to at least one symbol or at least one slot. Further, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0187] In some examples, the first indication includes an uplink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot. Additionally or alternatively, the second indication includes a downlink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0188] In some examples, the uplink signals include PUCCH signals, PUSCH signals, SRS, or random access preambles. Additionally or alternatively, the downlink signals include PDCCH signals, PDSCH signals, CSI-RS, or PRS.

[0189] In some examples, the one or more prioritization rules include: when a beam failure recovery procedure is not triggered, reception of a downlink signal is prioritized over transmission of an uplink signal during at least one symbol or at least one slot; and when a beam failure recovery procedure is triggered, transmission of an uplink signal is prioritized over reception of a downlink signal during at least one symbol or at least one slot. In some examples, the second indication includes a downlink SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal, a semi-persistent downlink signal, or a CSI-RS. In some other examples, the first indication includes a flexible RRC configuration related to at least one symbol or at least one slot, and the uplink signal includes an SRS or a random access preamble.

[0190] In some examples, the one or more prioritization rules include that the reception of downlink signals or the transmission of uplink signals is prioritized based on respective channel priorities associated with each of the downlink and uplink signals.

[0191] In some examples, the uplink and downlink resources are within one or more carriers to be used for TDD communications between the first network node and the second network node.

[0192] In some examples, the first instruction is for a first component carrier of the radio frequency spectrum band and the second instruction is for a second component carrier of the radio frequency spectrum band, where the first component carrier is different from the second component carrier.

[0193] In some examples, the control message further identifies one or more of the frequency locations of at least one uplink subband to be used for transmitting uplink messages during at least one symbol or at least one slot, at least one downlink subband to be used for receiving downlink messages during at least one symbol or at least one slot, at least one guard band intermediate the uplink and downlink subbands during at least one symbol or at least one slot, and at least one flexible subband to be used for transmitting uplink messages or receiving downlink messages during at least one symbol or at least one slot.

[0194] In some examples, the uplink or downlink resources include periodic resources or semi-persistent resources. In some examples, the first network node includes a UE and the second network node includes a base station.

[0195] FIG. 8 shows a diagram of a system 800 including a device 805 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The device 805 may be an example of, or include components of, a device 505, a device 605, or a UE 115 described herein. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, and a processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0196] The I / O controller 810 may manage input and output signals for the device 805. The I / O controller 810 may also manage peripheral devices that are not integrated with the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another operating system. Additionally or alternatively, the I / O controller 810 may represent or be able to interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of a processor, such as the processor 840. In some cases, a user may interact with the device 805 through the I / O controller 810 or through hardware components controlled by the I / O controller 810.

[0197] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have two or more antennas 825 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, wired links, or wireless links described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 825 for transmission, and demodulating packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of the transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination or component thereof described herein.

[0198] The memory 830 may include random access memory (RAM) and read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, the code 835 may not be directly executable by the processor 840, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some cases, the memory 830 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0199] Processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting multiplexing rules for SBFD communications). For example, device 805 or a component of device 805 may include processor 840 and memory 830 coupled to or connected to processor 840, where processor 840 and memory 830 are configured to perform various functions described herein.

[0200] The communications manager 820 may support wireless communications at a first network node (e.g., device 805) according to examples disclosed herein. For example, the communications manager 820 may be configured as, or otherwise support a means for receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node. The communications manager 820 may be configured as, or otherwise support a means for receiving a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. The communications manager 820 may be configured as, or otherwise support a means for receiving a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. The communications manager 820 may be configured as, or otherwise support a means for communicating with a second network node during at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules.

[0201] By including or configuring a communications manager 820 according to examples as described herein, the device 805 may support techniques for improved communications reliability, reduced latency, and more efficient utilization of communications resources.

[0202] In some examples, communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 815, one or more antennas 825, or any combination thereof. Although communications manager 820 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 820 may be supported or implemented by processor 840, memory 830, code 835, or any combination thereof. For example, code 835 may include instructions executable by processor 840 to cause device 805 to implement various aspects of the multiplexing rules for SBFD communications described herein, or processor 840 and memory 830 may be configured to perform or support such operations in other ways.

[0203] 9 shows a block diagram 900 of a device 905 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The device 905 may be an example of an aspect of a network entity 105 described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0204] The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information (e.g., I / Q samples, symbols, packets, protocol data units, service data units), such as user data, control information, or any combination thereof, associated with various channels (e.g., control channels, data channels, information channels, channels associated with protocol stacks). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0205] The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information (e.g., I / Q samples, symbols, packets, protocol data units, service data units), such as user data, control information, or any combination thereof, associated with various channels (e.g., control channels, data channels, information channels, channels associated with protocol stacks). In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and receiver 910 may be co-located within a transceiver that may include or be coupled to a modem.

[0206] The communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components thereof may be examples of means for implementing various aspects of the multiplexing rules for SBFD communications described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0207] In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0208] Additionally or alternatively, in some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). If implemented in code executed by a processor, the functionality of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).

[0209] In some examples, communications manager 920 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 910, transmitter 915, or both. For example, communications manager 920 may receive information from receiver 910 and send information to transmitter 915, or may be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations described herein.

[0210] The communications manager 920 may support wireless communications in a network node (e.g., device 905) according to examples disclosed herein. For example, the communications manager 920 may be configured as, or otherwise support a means for, outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communications in the network node. The communications manager 920 may be configured as, or otherwise support a means for, outputting a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. The communications manager 920 may be configured as, or otherwise support a means for, outputting a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. The communications manager 920 may be configured as, or otherwise support a means for, communicating during at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules.

[0211] By including or configuring a communications manager 920 according to examples described herein, the device 905 (e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for more efficient utilization of communications resources.

[0212] 10 shows a block diagram 1000 of a device 1005 that supports multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of an aspect of the device 905 or network entity 105 described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0213] The receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information (e.g., I / Q samples, symbols, packets, protocol data units, service data units), such as user data, control information, or any combination thereof, associated with various channels (e.g., control channels, data channels, information channels, channels associated with protocol stacks). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0214] The transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information (e.g., I / Q samples, symbols, packets, protocol data units, service data units), such as user data, control information, or any combination thereof, associated with various channels (e.g., control channels, data channels, information channels, channels associated with protocol stacks). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and receiver 1010 may be co-located within a transceiver that may include or be coupled to a modem.

[0215] The device 1005 or its various components may be an example of a means for implementing various aspects of the multiplexing rules for SBFD communications described herein. For example, the communications manager 1020 may include an SBFD component 1025, an uplink indication component 1030, a downlink indication component 1035, a rules component 1040, or any combination thereof. The communications manager 1020 may be an example of an aspect of the communications manager 920 described herein. In some examples, the communications manager 1020, or its various components, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010 and send information to the transmitter 1015, or may be integrated in combination with the receiver 1010, the transmitter 1015, or both to acquire information, output information, or perform various other operations described herein.

[0216] The communications manager 1020 may support wireless communications in a network node (e.g., device 1005) according to examples disclosed herein. The SBFD component 1025 may be configured as, or otherwise supporting a means for, outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communications in the network node. The uplink indication component 1030 may be configured as, or otherwise supporting a means for, outputting a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. The downlink indication component 1035 may be configured as, or otherwise supporting a means for, outputting a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. The rules component 1040 may be configured as, or otherwise supporting a means for, communicating during at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules.

[0217] 11 shows a block diagram 1100 of a communications manager 1120 supporting multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. Communications manager 1120 may be an example of aspects of communications manager 920, communications manager 1020, or both, as described herein. Communications manager 1120 or its various components may be an example of a means for implementing various aspects of the multiplexing rules for SBFD communications described herein. For example, communications manager 1120 may include an SBFD component 1125, an uplink indication component 1130, a downlink indication component 1135, a rules component 1140, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0218] The communications manager 1120 may support wireless communications in the network node according to examples disclosed herein. The SBFD component 1125 may be configured as, or otherwise supporting a means for, outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communications in the network node. The uplink indication component 1130 may be configured as, or otherwise supporting a means for, outputting a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. The downlink indication component 1135 may be configured as, or otherwise supporting a means for, outputting a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. The rules component 1140 may be configured as, or otherwise supporting a means for, communicating during at least one symbol or at least one slot according to one of the first indication or the second indication based on one or more prioritization rules.

[0219] In some examples, the uplink resources are in at least one uplink subband or at least one flexible subband, and in some examples, the downlink resources are in at least one downlink subband or at least one flexible subband.

[0220] In some examples, the first indication is for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot. In some examples, the second indication is for communication of a synchronization signal block in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot. Additionally or alternatively, the first indication includes an uplink SFI related to the at least one symbol or at least one slot. In some examples, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0221] In some examples, the first instruction is for communication of a random access preamble in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot. In some examples, the second instruction is for communication of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot. Additionally or alternatively, the second instruction includes a downlink SFI related to the at least one symbol or at least one slot.

[0222] In some examples, the first instructions are for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot. In some examples, the second instructions are for communication using a downlink control channel in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot. Additionally or alternatively, the first instructions include an uplink SFI related to the at least one symbol or at least one slot.

[0223] In some examples, the first instruction is for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and in some examples, the second instruction is for communication of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0224] In some examples, the first indication includes an uplink SFI related to at least one symbol or at least one slot. Further, the second indication includes an RRC configuration related to at least one symbol or at least one slot. In some examples, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0225] In some examples, the first indication includes an RRC configuration related to at least one symbol or at least one slot. Further, the second indication includes a downlink SFI related to at least one symbol or at least one slot. In some examples, the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0226] In some examples, the second indication includes a flexible RRC configuration related to at least one symbol or at least one slot. Additionally or alternatively, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0227] In some examples, the first indication includes an uplink SFI related to at least one symbol or at least one slot, and the second indication includes a dynamic grant related to at least one symbol or at least one slot. Further, the downlink signal includes a PDSCH signal or a CSI-RS.

[0228] In some examples, the first indication includes an SFI or a flexible SFI related to at least one symbol or at least one slot. Further, the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0229] In some examples, the first indication includes a dynamic grant related to at least one symbol or at least one slot, the second indication includes a downlink SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0230] In some examples, the second indication includes a downlink SFI or a flexible SFI related to at least one symbol or at least one slot. Further, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0231] In some examples, the first indication includes a dynamic grant relating to at least one symbol or at least one slot. Further, the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, a CSI-RS, or a PRS.

[0232] In some examples, the second indication includes a dynamic grant relating to at least one symbol or at least one slot. Further, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0233] In some examples, the first indication includes an uplink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot. In some examples, the second indication includes a downlink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot. In some examples, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble. In some examples, the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0234] In some examples, the one or more prioritization rules include: when a beam failure recovery procedure is not triggered, communication of a downlink signal is prioritized over communication of an uplink signal during at least one symbol or at least one slot; and when a beam failure recovery procedure is triggered, communication of an uplink signal is prioritized over communication of a downlink signal during at least one symbol or at least one slot. In some examples, the second indication includes a downlink SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal, a semi-persistent downlink signal, or a CSI-RS. In some other examples, the first indication includes a flexible RRC configuration related to at least one symbol or at least one slot, and the uplink signal includes an SRS or a random access preamble.

[0235] In some examples, the one or more prioritization rules include that communication of downlink or uplink signals is prioritized based on respective channel priorities associated with each of the downlink and uplink signals.

[0236] In some examples, the uplink resources and downlink resources are within one or more carriers to be used for TDD communications in the network node, hi some examples, the first instruction is for a first component carrier of the radio frequency spectrum band and the second instruction is for a second component carrier of the radio frequency spectrum band, the first component carrier being different from the second component carrier.

[0237] In some examples, the control message further identifies one or more of the frequency locations of at least one uplink subband to be used for communication of uplink messages during at least one symbol or at least one slot, at least one downlink subband to be used for communication of downlink messages during at least one symbol or at least one slot, at least one guard band intermediate the uplink and downlink subbands during at least one symbol or at least one slot, and at least one flexible subband to be used for communication of uplink or downlink messages during at least one symbol or at least one slot.

[0238] In some examples, the uplink or downlink resources include periodic resources or semi-persistent resources. In some examples, the network node includes a base station.

[0239] FIG. 12 shows a diagram of a system 1200 including a device 1205 supporting multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include components of the device 905, device 1005, or network entity 105 described herein. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0240] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving (e.g., simultaneously) wireless transmissions. The transceiver 1210 may also include a modem for modulating signals, providing the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter), receiving the modulated signals (e.g., from one or more antennas 1215 or from a wired receiver), and demodulating the signals. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with one or more antennas 1215 configured to support various receive or acquisition operations, or one or more interfaces coupled with one or more antennas 1215 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1210 may include, or be configured to couple with, one or more processors or memory components operable to perform or support an operation based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processor or memory components (e.g., the processor 1235, or the memory 1225, or both) may be included in a chip or chip assembly installed in the device 1205.In some examples, the transceiver may be operable to support communication over one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0241] Memory 1225 may include RAM and ROM. Memory 1225 may store computer-readable computer-executable code 1230 including instructions that, when executed by processor 1235, cause device 1205 to perform various functions described herein. Code 1230 may be stored on a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by processor 1235, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some cases, memory 1225 may include a BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0242] Processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting multiplexing rules for SBFD communications). For example, device 1205 or a component of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, where processor 1235 and memory 1225 are configured to perform various functions described herein. Processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functionality (e.g., by executing code 1230) to perform the functionality of device 1205. Processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored within device 1205 (e.g., in memory 1225). In some implementations, processor 1235 may be a component of a processing system. A processing system may generally refer to a system or set of machines or components that receives inputs, processes the inputs, and produces a set of outputs (e.g., that may be passed to other systems or components of device 1205).For example, the processing system of device 1205 may refer to a system that includes various other components or subcomponents of device 1205, such as processor 1235, or transceiver 1210, or communications manager 1220, or other components or combinations of components of device 1205. The processing system of device 1205 may interface with other components of device 1205 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information, acquiring information, or both. The one or more interfaces may be implemented as or may otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to output information and acquire information, among other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system and a transmitter of the chip or modem, such that device 1205 may transmit information output from the chip or modem. Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system and a receiver of a chip or modem, such that device 1205 may obtain information or signal input, which may be passed to the processing system. Those skilled in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0243] In some examples, bus 1240 may support communications within (e.g., within) protocol layers of a protocol stack. In some examples, bus 1240 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications conducted within a component of device 1205 or between different components of device 1205, which may be collocated or located in different locations (e.g., device 1205 may refer to a system in which one or more of communications manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of or split among different components).

[0244] In some examples, the communications manager 1220 may manage aspects of communications with the core network 130 (e.g., over one or more wired or wireless backhaul links). For example, the communications manager 1220 may manage the forwarding of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1220 may manage communications with other network entities 105 and may include a controller or scheduler that cooperates with the other network entities 105 to control communications with the UEs 115. In some examples, the communications manager 1220 may support an X2 interface within LTE / LTE-A wireless communications network technologies to provide communications between network entities 105.

[0245] Communications manager 1220 may support wireless communications in a network node (e.g., device 1205) in accordance with examples disclosed herein. For example, communications manager 1220 may be configured as, or otherwise support a means for, outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communications in the network node. Communications manager 1220 may be configured as, or otherwise support a means for, outputting a first indication of uplink resources for uplink communications during at least one symbol or at least one slot. Communications manager 1220 may be configured as, or otherwise support a means for, outputting a second indication of downlink resources for downlink communications during at least one symbol or at least one slot. Communications manager 1220 may be configured as, or otherwise support a means for, communicating during at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0246] By including or configuring a communications manager 1220 according to examples described herein, the device 1205 may support techniques for improved communications reliability, reduced latency, and more efficient utilization of communications resources.

[0247] In some examples, communications manager 1220 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with transceiver 1210, one or more antennas 1215 (e.g., if applicable), or any combination thereof. Although communications manager 1220 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 1220 may be supported or implemented by transceiver 1210, processor 1235, memory 1225, code 1230, or any combination thereof. For example, code 1230 may include instructions executable by processor 1235 to cause device 1205 to implement various aspects of the multiplexing rules for SBFD communications described herein, or processor 1235 and memory 1225 may be configured to perform or support such operations in other ways.

[0248] FIG. 13 shows a flow diagram illustrating a method 1300 for supporting multiplexing rules for SBFD communications according to one or more aspects of the present disclosure. The operations of method 1300 may be performed by a UE or components thereof as described herein. For example, the operations of method 1300 may be performed by the UE 115 described with reference to FIGS. 1-8. In some examples, the UE may execute a set of instructions that control functional elements of the UE to perform the described functionality. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functionality.

[0249] At 1305, the method may include receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communications at a second network node. The operations of 1305 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1305 may be performed by control message component 725 described with reference to FIG. 7.

[0250] At 1310, the method may include receiving a first indication of uplink resources for uplink communication during at least one symbol or at least one slot. The operations of 1310 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1310 may be performed by uplink component 730 described with reference to FIG. 7.

[0251] At 1315, the method may include receiving a second indication of downlink resources for downlink communication during at least one symbol or at least one slot. The operations of 1315 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1315 may be performed by downlink component 735 described with reference to FIG. 7.

[0252] At 1320, the method may include communicating with the second network node during at least one symbol or at least one slot according to one of the first instructions or the second instructions based on one or more prioritization rules. The operations of 1320 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1320 may be performed by prioritization component 740 described with reference to FIG. 7.

[0253] FIG. 14 shows a flow diagram illustrating a method 1400 for supporting multiplexing rules for SBFD communications in accordance with one or more aspects of the present disclosure. The operations of method 1400 may be performed by a network entity or components thereof as described herein. For example, the operations of method 1400 may be performed by a network entity described with reference to FIGS. 1-4 and 9-12. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may perform aspects of the described functions using dedicated hardware.

[0254] At 1405, the method may include outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communications at the network node. The operations of 1405 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed by SBFD component 1125 described with reference to FIG. 11.

[0255] At 1410, the method may include outputting a first indication of uplink resources for uplink communication during at least one symbol or at least one slot. The operations of 1410 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed by the uplink indication component 1130 described with reference to FIG. 11.

[0256] At 1415, the method may include outputting a second indication of downlink resources for downlink communication during at least one symbol or at least one slot. The operations of 1415 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed by downlink indication component 1135 described with reference to FIG. 11.

[0257] At 1420, the method may include communicating during at least one symbol or at least one slot according to one of the first instructions or the second instructions based on one or more prioritization rules. The operations of 1420 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1420 may be performed by rules component 1140 described with reference to FIG. 11 .

[0258] The following provides a summary of aspects of the present disclosure.

[0259] Aspect 1: A method for wireless communication in a first network node, the method comprising: receiving a control message identifying at least one symbol or at least one slot to be used for SBFD communication at a second network node; receiving a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot; receiving a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot; and communicating with the second network node during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0260] Aspect 2: The method of aspect 1, wherein the uplink resources are within at least one uplink subband or at least one flexible subband, and the downlink resources are within at least one downlink subband or at least one flexible subband.

[0261] Aspect 3: A method according to any one of aspects 1 to 2, wherein the first instruction is for transmitting an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for receiving an SSB in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0262] Aspect 4: The method of aspect 3, wherein the first instruction includes an uplink SFI related to at least one symbol or at least one slot.

[0263] Aspect 5: The method of any one of aspects 3 to 4, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0264] Aspect 6: A method according to any one of aspects 1 to 2, wherein the first instruction is for transmitting a random access preamble in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for receiving a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0265] Aspect 7: The method of aspect 6, wherein the second instruction includes a downlink SFI related to at least one symbol or at least one slot.

[0266] Aspect 8: A method according to any one of aspects 1 to 2, wherein the first instruction is for transmitting an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for monitoring a downlink control channel in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0267] Aspect 9: The method of aspect 8, wherein the first instruction includes an uplink SFI related to at least one symbol or at least one slot.

[0268] Aspect 10: A method according to any one of aspects 1 to 9, wherein the first instruction is for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for reception of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0269] Aspect 11: The method described in aspect 10, wherein the first instruction includes an uplink SFI related to at least one symbol or at least one slot, and the second instruction includes an RRC setting related to at least one symbol or at least one slot.

[0270] Example 12: The method of example 11, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0271] Aspect 13: The method of aspect 10, wherein the first instruction includes an RRC setting related to at least one symbol or at least one slot, and the second instruction includes a downlink SFI related to at least one symbol or at least one slot.

[0272] Example 14: The method of example 13, wherein the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0273] Aspect 15: The method of aspect 10, wherein the second indication includes a flexible RRC configuration related to at least one symbol or at least one slot.

[0274] Example 16: The method of example 15, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0275] Aspect 17: The method of aspect 10, wherein the first instruction includes an uplink SFI related to at least one symbol or at least one slot, the second instruction includes a dynamic grant related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal or a CSI-RS.

[0276] Aspect 18: The method of aspect 10, wherein the first indication includes an uplink SFI or a flexible SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0277] Aspect 19: The method of aspect 10, wherein the first instruction includes a dynamic grant related to at least one symbol or at least one slot, the second instruction includes a downlink SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0278] Aspect 20: The method of aspect 10, wherein the second instruction includes a downlink SFI or a flexible SFI related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0279] Aspect 21: The method of aspect 10, wherein the first indication includes a dynamic grant related to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, a CSI-RS, or a PRS.

[0280] Aspect 22: The method of aspect 10, wherein the second instruction includes a dynamic grant related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0281] Aspect 23: The method of aspect 10, wherein the first indication includes an uplink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0282] Aspect 24: The method of aspect 10, wherein the second indication includes a downlink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0283] Aspect 25: The method of aspect 10, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0284] Aspect 26: The method of aspect 10, wherein the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0285] Aspect 27: The method described in aspect 10, wherein the one or more prioritization rules include: when a beam failure recovery procedure is not triggered, reception of a downlink signal is prioritized over transmission of an uplink signal during at least one symbol or at least one slot; and when a beam failure recovery procedure is triggered, transmission of an uplink signal is prioritized over reception of a downlink signal during at least one symbol or at least one slot.

[0286] Aspect 28: The method of aspect 27, wherein the second instruction includes a downlink SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0287] Aspect 29: The method of aspect 27, wherein the first indication includes a flexible RRC configuration related to at least one symbol or at least one slot, and the uplink signal includes an SRS or a random access preamble.

[0288] Aspect 30: The method of any of aspects 10 to 29, wherein the one or more prioritization rules include prioritizing reception of downlink signals or transmission of uplink signals based on respective channel priorities associated with each of the downlink signals and uplink signals.

[0289] Aspect 31: The method of any of aspects 1 to 30, wherein the uplink and downlink resources are within one or more carriers to be used for TDD communication between the first network node and the second network node.

[0290] Aspect 32: The method of any of aspects 1 to 31, wherein the first instruction is for a first component carrier of the radio frequency spectrum band, and the second instruction is for a second component carrier of the radio frequency spectrum band, and the first component carrier is different from the second component carrier.

[0291] Aspect 33: A method according to any one of aspects 1 to 32, wherein the control message further identifies one or more of the frequency locations of at least one uplink subband to be used for transmitting an uplink message for at least one symbol or at least one slot, at least one downlink subband to be used for receiving a downlink message for at least one symbol or at least one slot, at least one guard band between the uplink subband and the downlink subband for at least one symbol or at least one slot, and at least one flexible subband to be used for transmitting an uplink message or receiving a downlink message for at least one symbol or at least one slot.

[0292] Aspect 34: The method of aspect 1, wherein the uplink resource or the downlink resource includes a periodic resource or a semi-persistent resource.

[0293] Example 35: The method of any of examples 1 to 34, wherein the first network node includes a UE and the second network node includes a base station.

[0294] Aspect 36: A method for wireless communication in a network node, the method comprising: outputting a control message identifying at least one symbol or at least one slot to be used for SBFD communication in the network node; outputting a first indication of uplink resources for uplink communication during the at least one symbol or at least one slot; outputting a second indication of downlink resources for downlink communication during the at least one symbol or at least one slot; and communicating during the at least one symbol or at least one slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0295] Aspect 37: The method of aspect 36, wherein the uplink resources are within at least one uplink subband or at least one flexible subband, and the downlink resources are within at least one downlink subband or at least one flexible subband.

[0296] Aspect 38: A method according to any of aspects 36 to 37, wherein the first instruction is for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for communication of an SSB in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0297] Aspect 39: The method of aspect 38, wherein the first instruction includes an uplink SFI related to at least one symbol or at least one slot.

[0298] Example 40: The method of any one of examples 38 to 39, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0299] Aspect 41: A method according to any of aspects 36 to 37, wherein the first instruction is for communication of a random access preamble in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for communication of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0300] Aspect 42: The method of aspect 41, wherein the second instruction includes a downlink SFI related to at least one symbol or at least one slot.

[0301] Aspect 43: A method according to any one of aspects 36 to 37, wherein the first instruction is for communication of an uplink signal in at least one uplink subband or at least one flexible subband for at least one symbol or at least one slot, and the second instruction is for communication using a downlink control channel in at least one downlink subband or at least one flexible subband for at least one symbol or at least one slot.

[0302] Aspect 44: The method of aspect 43, wherein the first instruction includes an uplink SFI related to at least one symbol or at least one slot.

[0303] Aspect 45: A method according to any of aspects 36 to 37, wherein the first instruction is for communication of an uplink signal in at least one uplink subband or at least one flexible subband during at least one symbol or at least one slot, and the second instruction is for communication of a downlink signal in at least one downlink subband or at least one flexible subband during at least one symbol or at least one slot.

[0304] Aspect 46: The method described in aspect 45, wherein the first instruction includes an uplink SFI related to at least one symbol or at least one slot, and the second instruction includes an RRC setting related to at least one symbol or at least one slot.

[0305] Aspect 47: The method of aspect 46, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0306] Aspect 48: A method according to any of aspects 36 to 37, wherein the first instruction includes an RRC configuration relating to at least one symbol or at least one slot, and the second instruction includes a downlink SFI relating to at least one symbol or at least one slot.

[0307] Example 49: The method of example 48, wherein the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0308] Aspect 50: The method of any of aspects 36 to 37, wherein the second instruction includes a flexible RRC configuration relating to at least one symbol or at least one slot.

[0309] Aspect 51: The method of aspect 50, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0310] Aspect 52: A method according to any one of aspects 36 to 37, wherein the first instruction includes an uplink SFI relating to at least one symbol or at least one slot, the second instruction includes a dynamic grant relating to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal or a CSI-RS.

[0311] Aspect 53: The method of any of aspects 36 to 37, wherein the first indication includes an uplink SFI or a flexible SFI related to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0312] Aspect 54: A method according to any of aspects 36 to 37, wherein the first instruction includes a dynamic grant relating to at least one symbol or at least one slot, the second instruction includes a downlink SFI relating to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0313] Aspect 55: A method according to any one of aspects 36 to 37, wherein the second instruction includes a downlink SFI or a flexible SFI relating to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0314] Aspect 56: The method of any of aspects 36 to 37, wherein the first indication includes a dynamic grant relating to at least one symbol or at least one slot, and the downlink signal includes a PDCCH signal, a semi-persistent downlink signal, a CSI-RS, or a PRS.

[0315] Aspect 57: The method of any of aspects 36 to 37, wherein the second instruction includes a dynamic grant related to at least one symbol or at least one slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0316] Aspect 58: The method of any one of aspects 36 to 37, wherein the first instruction includes an uplink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0317] Aspect 59: The method of any one of aspects 36 to 37, wherein the second instruction includes a downlink SFI, a flexible SFI, an RRC configuration, or a dynamic grant related to at least one symbol or at least one slot.

[0318] Example 60: The method of any one of examples 36 to 37, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0319] Example 61: The method of any one of examples 36 to 37, wherein the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0320] Aspect 62: A method described in any of aspects 45 to 61, wherein the one or more prioritization rules include: when a beam failure recovery procedure is not triggered, communication of a downlink signal is prioritized over communication of an uplink signal during at least one symbol or at least one slot; and when a beam failure recovery procedure is triggered, communication of an uplink signal is prioritized over communication of a downlink signal during at least one symbol or at least one slot.

[0321] Aspect 63: The method of aspect 62, wherein the second instruction includes a downlink SFI relating to at least one symbol or at least one slot, and the downlink signal includes a PDSCH signal, a semi-persistent downlink signal, or a CSI-RS.

[0322] Aspect 64: The method of aspect 62, wherein the first indication includes a flexible RRC configuration relating to at least one symbol or at least one slot, and the uplink signal includes an SRS or a random access preamble.

[0323] Aspect 65: The method of any of aspects 45 to 64, wherein the one or more prioritization rules include prioritizing communication of downlink or uplink signals based on respective channel priorities associated with each of the downlink and uplink signals.

[0324] Aspect 66: The method of any of aspects 36 to 65, wherein the uplink and downlink resources are in one or more carriers to be used for TDD communication in the method.

[0325] Aspect 67: The method of any of aspects 36 to 66, wherein the first instruction is for a first component carrier of the radio frequency spectrum band, the second instruction is for a second component carrier of the radio frequency spectrum band, and the first component carrier is different from the second component carrier.

[0326] Aspect 68: A method described in any of aspects 36 to 67, wherein the control message further identifies one or more of the frequency locations of at least one uplink subband to be used for communicating uplink messages for at least one symbol or at least one slot, at least one downlink subband to be used for communicating downlink messages for at least one symbol or at least one slot, at least one guard band intermediate the uplink subband and the downlink subband for at least one symbol or at least one slot, and at least one flexible subband to be used for communicating uplink messages or downlink messages for at least one symbol or at least one slot.

[0327] Aspect 69: The method of aspect 36, wherein the uplink resource or the downlink resource includes a periodic resource or a semi-persistent resource.

[0328]

[0072] Aspect 70: The method of any of aspects 36 to 69, wherein the network node comprises a base station.

[0329] Aspect 71: A first network node for wireless communication, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform a method described in any of aspects 1 to 35.

[0330] Aspect 72: An apparatus for wireless communication in a first network node, the apparatus comprising at least one means for performing the method of any of aspects 1 to 35.

[0331] Aspect 73: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code, when executed by a first network node, causing the first network node to perform a method described in any of aspects 1 to 35.

[0332] Aspect 74: A network node for wireless communication, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform a method described in any of aspects 36 to 70.

[0333] Aspect 75: An apparatus for wireless communication in a network node, the apparatus comprising at least one means for performing the method of any of aspects 36 to 70.

[0334] Aspect 76: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code, when executed by a network node, causing the network node to perform a method described in any of aspects 36 to 70.

[0335] The methods described herein represent possible implementations, and operations and steps may be rearranged or otherwise modified, other implementations are possible, and further, aspects from two or more of these methods may be combined.

[0336] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described as examples, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0337] The information and signals described herein may be represented using any of a wide variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0338] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0339] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored on or transmitted using one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0340] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one location to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. A disk can reproduce data magnetically, and a disc can reproduce data optically using a laser. Combinations of the above are also included within the scope of computer-readable media.

[0341] The term "or" as used herein is an inclusive "or" unless limiting language is used to the listed alternatives. For example, a reference to "X is based on A or B" shall be interpreted as including within its scope X is based on A, X is based on B, and X is based on A and B. In this regard, a reference to "X is based on A or B" refers to "at least one of A or B" or "one or more of A or B," since "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" shall be interpreted as including within its scope X is based on A, X is based on B, X is based on C, X is based on A and B, X is based on A and C, X is based on B and C, and X is based on A, B, and C. In this regard, a reference to "X is based on A, B, or C" refers to "at least one of A, B, or C" or "one or more of A, B, or C," since "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" shall be interpreted to include within its scope X is based on A and X is based on B, but not X is based on A and B. Also, as used herein, the phrase "based on" is not to be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) shall be interpreted as "based on at least A," unless expressly stated otherwise. Also, as used herein, the phrase "set" shall be interpreted as including the possibility of a set having one member. That is, the phrase "set" shall be interpreted similarly to "one or more" or "at least one."

[0342] The terms "determine" or "determining" encompass various actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or other data structure), ascertaining, and the like. "Determining" can also include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. "Determining" can also include resolving, obtaining, selecting, choosing, establishing, and other such similar acts.

[0343] In the figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of a second reference label, or other subsequent reference label.

[0344] The descriptions set forth herein with respect to the drawings describe exemplary configurations and do not necessarily represent every example that may be implemented or fall within the scope of the claims. As used herein, the term "aspect" or "example" means "serving as an aspect, example, instance, or illustration" and does not mean "preferred" or "advantageous over other aspects." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0345] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first network node for wireless communication, comprising: Memory and at least one processor coupled to the memory; wherein the at least one processor: receiving a control message at a second network node identifying at least one symbol or at least one slot to be used for sub-band full duplex communication; receiving a first indication of uplink resources for uplink communication during the at least one symbol or the at least one slot; receiving a second indication of downlink resources for downlink communication during the at least one symbol or the at least one slot; a first network node configured to communicate with the second network node during the at least one symbol or the at least one slot in accordance with one of the first instructions or the second instructions based on one or more prioritization rules.

2. 2. The first network node of claim 1, wherein the uplink resources are in at least one uplink subband or at least one flexible subband, and the downlink resources are in at least one downlink subband or the at least one flexible subband.

3. 2. The first network node of claim 1, wherein the first indication is for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second indication is for reception of a synchronization signal block in at least one downlink subband or at least one flexible subband during the at least one symbol or the at least one slot.

4. The first network node of claim 3 , wherein the first indication comprises an uplink slot format indicator relating to the at least one symbol or the at least one slot.

5. 2. The first network node of claim 1, wherein the first indication is for transmission of a random access preamble in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second indication is for reception of a downlink signal in at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one slot.

6. 2. The first network node of claim 1, wherein the first instruction is for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second instruction is for monitoring a downlink control channel in at least one downlink subband or at least one flexible subband during the at least one symbol or the at least one slot.

7. 2. The first network node of claim 1, wherein the first instruction is for transmission of an uplink signal in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second instruction is for reception of a downlink signal in at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one slot.

8. 8. The first network node of claim 7, wherein the first indication comprises an uplink slot format indicator, a flexible slot format indicator, a radio resource control setting, or a dynamic grant related to the at least one symbol or the at least one slot.

9. 8. The first network node of claim 7, wherein the second indication comprises a downlink slot format indicator, a flexible slot format indicator, a radio resource control setting, or a dynamic grant related to the at least one symbol or the at least one slot.

10. The first network node of claim 7 , wherein the uplink signal comprises a physical uplink control channel signal, a physical uplink shared channel signal, a sounding reference signal, or a random access preamble.

11. The first network node of claim 7 , wherein the downlink signals comprise physical downlink control channel signals, physical downlink shared channel signals, channel state information reference signals, or positioning reference signals.

12. 8. The first network node of claim 7, wherein the one or more prioritization rules include: if a beam failure recovery procedure is not triggered, reception of the downlink signal is prioritized over transmission of the uplink signal during the at least one symbol or the at least one slot; and if a beam failure recovery procedure is triggered, transmission of the uplink signal is prioritized over reception of the downlink signal during the at least one symbol or the at least one slot.

13. 8. The first network node of claim 7, wherein the one or more prioritization rules include that the reception of the downlink signal or the transmission of the uplink signal is prioritized based on a respective channel priority associated with each of the downlink signal and the uplink signal.

14. 2. The first network node of claim 1, wherein the uplink and downlink resources are within one or more carriers to be used for time division duplex communications between the first network node and the second network node.

15. 2. The first network node of claim 1, wherein the first indication is for a first component carrier of a radio frequency spectrum band and the second indication is for a second component carrier of the radio frequency spectrum band, the first component carrier being different from the second component carrier.

16. A network node for wireless communication, comprising: Memory and at least one processor coupled to the memory; wherein the at least one processor: outputting a control message identifying at least one symbol or at least one slot to be used for sub-band full duplex communication at said network node; outputting a first indication of uplink resources for uplink communication during the at least one symbol or the at least one slot; outputting a second indication of downlink resources for downlink communication during the at least one symbol or the at least one slot; and communicating during the at least one symbol or the at least one slot in accordance with one of the first instruction or the second instruction based on one or more prioritization rules.

17. 17. The network node of claim 16, wherein the uplink resources are in at least one uplink subband or at least one flexible subband, and the downlink resources are in at least one downlink subband or the at least one flexible subband.

18. 17. The network node of claim 16, wherein the first indication is for communication of an uplink signal in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second indication is for communication of a synchronization signal block in at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one slot.

19. 20. The network node of claim 18, wherein the first indication comprises an uplink slot format indicator relating to the at least one symbol or the at least one slot.

20. 17. The network node of claim 16, wherein the first indication is for communication of a random access preamble in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second indication is for communication of a downlink signal in at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one slot.

21. 17. The network node of claim 16, wherein the first indication is for communication of an uplink signal in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second indication is for communication using a downlink control channel in at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one slot.

22. 17. The network node of claim 16, wherein the first indication is for communication of an uplink signal in at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one slot, and the second indication is for communication of a downlink signal in at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one slot.

23. 23. The network node of claim 22, wherein the first indication comprises an uplink slot format indicator, a flexible slot format indicator, a radio resource control setting, or a dynamic grant related to the at least one symbol or the at least one slot.

24. 23. The network node of claim 22, wherein the second indication comprises a downlink slot format indicator, a flexible slot format indicator, a radio resource control setting, or a dynamic grant related to the at least one symbol or the at least one slot.

25. 23. The network node of claim 22, wherein the uplink signal comprises a physical uplink control channel signal, a physical uplink shared channel signal, a sounding reference signal, or a random access preamble.

26. 23. The network node of claim 22, wherein the downlink signals comprise physical downlink control channel signals, physical downlink shared channel signals, channel state information reference signals, or positioning reference signals.

27. 23. The network node of claim 22, wherein the one or more prioritization rules comprise: if a beam failure recovery procedure is not triggered, communication of the downlink signal is prioritized over communication of the uplink signal during the at least one symbol or the at least one slot; and if a beam failure recovery procedure is triggered, communication of the uplink signal is prioritized over communication of the downlink signal during the at least one symbol or the at least one slot.

28. 23. The network node of claim 22, wherein the one or more prioritization rules include that communication of the downlink signal or the uplink signal is prioritized based on a respective channel priority associated with each of the downlink signal and the uplink signal.

29. 1. A method for wireless communication in a first network node, comprising: receiving a control message at a second network node identifying at least one symbol or at least one slot to be used for sub-band full duplex communication; receiving a first indication of uplink resources for uplink communication during the at least one symbol or the at least one slot; receiving a second indication of downlink resources for downlink communication during the at least one symbol or the at least one slot; communicating with the second network node during the at least one symbol or the at least one slot according to one of the first instruction or the second instruction based on one or more prioritization rules; A method comprising:

30. 1. A method for wireless communication in a network node, comprising: outputting a control message identifying at least one symbol or at least one slot to be used for sub-band full duplex communication at said network node; outputting a first indication of uplink resources for uplink communication during the at least one symbol or the at least one slot; outputting a second indication of downlink resources for downlink communication during the at least one symbol or the at least one slot; communicating during the at least one symbol or the at least one slot according to one of the first instruction or the second instruction based on one or more prioritization rules; A method comprising:

Images