Multiplexing rules for sub-band full duplex communications

Abstract

Methods, systems, and devices for wireless communication are described. A first network node may receive a control message identifying at least one symbol or at least one time slot to be used for sub-band 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 the at least one time slot. The first network node may receive a second indication of downlink resources for downlink communications during the at least one symbol or the at least one time slot. The first network node may communicate with the second network node during the at least one symbol or the at least one time slot according to one of the first indication or the second indication based on one or more prioritization rules.

Description

[0001] Cross-reference

[0002] This patent application claims the benefit of U.S. Patent Application No. 18 / 050,350, entitled "MULTIPLEXING RULES FOR SUBBAND FULL DUPLEX COMMUNICATIONS", filed on Oct. 27, 2022, by ZHANG et al., which is assigned to the assignee of the present application and is hereby incorporated herein by reference in its entirety. Background Art

[0003] The following is related 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, broadcasting, etc. 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 multi-access systems include fourth generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be 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). A wireless multi-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support multiplexing rules for sub-band full-duplex (SBFD) communication. For example, the described techniques provide a framework for managing conflict configuration information related to the same transmission time interval (TTI) (such as a time slot or a symbol). For example, a first network node (such as a user equipment (UE)) may receive a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication 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 to be used for uplink communication during at least one symbol or at least one time slot. Additionally, the first network node may receive a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot. In some examples, the first network node may communicate with the second network node during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication. In some examples, using one or more prioritization rules to determine whether to communicate according to the first indication or the second indication may result in reduced latency, increased resource utilization, and other possible benefits.

[0005] A method for wireless communication at a first network node is described. The method may include: receiving a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a second network node; receiving a first indication of uplink resources to be used for uplink communication during at least one symbol or at least one time slot; receiving a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot; and communicating with the second network node during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0006] An apparatus for wireless communication at a first 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: receive a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a second network node; receive a first indication of uplink resources to be used for uplink communication during at least one symbol or at least one time slot; receive a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot; and communicate with the second network node during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0007] Describes another apparatus for wireless communication at a first network node. The apparatus may include: means for receiving a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a second network node; means for receiving a first indication of uplink resources for use in uplink communication during at least one symbol or at least one time slot; means for receiving a second indication of downlink resources for use in downlink communication during at least one symbol or at least one time slot; and means for communicating with the second network node during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0008] Describes a non-transitory computer-readable medium storing code for wireless communication. The code stored thereon, when executed by a first network node, causes the first network node to: receive a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a second network node; receive a first indication of uplink resources for use in uplink communication during at least one symbol or at least one time slot; receive a second indication of downlink resources for use in downlink communication during at least one symbol or at least one time slot; and communicate with the second network node during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

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

[0010] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication may be used to transmit an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot, and the second indication may be used to receive a Synchronization Signal Block (SSB) within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes an Uplink Time Slot Format Indicator (SFI) related to at least one symbol or at least one time slot.

[0012] In some examples of the methods, apparatuses, 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.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first indication can be used to transmit a random access preamble within at least one uplink sub-band or at least one flexible sub-band during at least one symbol or at least one time slot, and a second indication can be used to receive a downlink signal within at least one downlink sub-band or at least one flexible sub-band during at least one symbol or at least one time slot.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second indication includes a downlink SFI related to at least one symbol or at least one time slot.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first indication can be used to transmit an uplink signal within at least one uplink sub-band or at least one flexible sub-band during at least one symbol or at least one time slot, and a second indication can be used to monitor a downlink control channel within at least one downlink sub-band or at least one flexible sub-band during at least one symbol or at least one time slot.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes an uplink SFI related to at least one symbol or at least one time slot.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first indication can be used to transmit an uplink signal within at least one uplink sub-band or at least one flexible sub-band during at least one symbol or at least one time slot, and a second indication can be used to receive a downlink signal within at least one downlink sub-band or at least one flexible sub-band during at least one symbol or at least one time slot.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes an uplink SFI related to at least one symbol or at least one time slot, and the second indication includes a Radio Resource Control (RRC) configuration related to at least one symbol or at least one time slot.

[0019] In some examples of the methods, apparatuses, 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.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes RRC configuration related to at least one symbol or at least one time slot, and the second indication includes downlink SFI related to at least one symbol or at least one time slot.

[0021] In some examples of the methods, apparatuses, 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).

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second indication includes flexible RRC configuration related to at least one symbol or at least one time slot.

[0023] In some examples of the methods, apparatuses, 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.

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

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

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes a dynamic grant related to at least one symbol or at least one time slot, and the second indication includes downlink SFI related to at least one symbol or at least one time 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, apparatuses, and non-transitory computer-readable media described herein, the second indication includes downlink SFI or flexible SFI related to at least one symbol or at least one time slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

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

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

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, 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 time slot.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, 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 time slot.

[0032] In some examples of the methods, apparatuses, 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.

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

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, one or more prioritization rules include: in the absence of a beam failure recovery process being triggered, the reception of downlink signals during at least one symbol or at least one time slot may be prioritized over the transmission of uplink signals, and in the presence of a beam failure recovery process being triggered, the transmission of uplink signals during at least one symbol or at least one time slot may be prioritized over the reception of downlink signals.

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

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

[0037] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, one or more prioritization rules include: the reception of downlink signals or the transmission of uplink signals can be prioritized based on the respective channel priorities associated with each of the downlink signals and the uplink signals.

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

[0039] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication can be used for a first component carrier of a radio frequency band, and the second indication can be used for a second component carrier of the radio frequency band, where the first component carrier is different from the second component carrier.

[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the control message further identifies one or more of the following: the frequency position of at least one uplink subband to be used for transmitting an uplink message during at least one symbol or at least one time slot; at least one downlink subband to be used for receiving a downlink message during at least one symbol or at least one time slot; at least one guard band between the uplink subband and the downlink subband during at least one symbol or at least one time slot; and at least one flexible subband to be used for transmitting an uplink message or receiving a downlink message during at least one symbol or at least one time slot.

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

[0042] In some examples of the methods, apparatuses, 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.

[0043] Describes a method for wireless communication at a network node. The method may include: outputting a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node; outputting a first indication of uplink resources for uplink communication during at least one symbol or at least one time slot; outputting a second indication of downlink resources for downlink communication during at least one symbol or at least one time slot; and communicating during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0044] Describes an apparatus for wireless communication at a network node. 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 that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node; output a first indication of uplink resources for uplink communication during at least one symbol or at least one time slot; output a second indication of downlink resources for downlink communication during at least one symbol or at least one time slot; and communicate during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0045] Describes another apparatus for wireless communication at a network node. The apparatus may include: means for outputting a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node; means for outputting a first indication of uplink resources for uplink communication during at least one symbol or at least one time slot; means for outputting a second indication of downlink resources for downlink communication during at least one symbol or at least one time slot; and means for communicating during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0046] Describes a non-transitory computer-readable medium storing code for wireless communication. The code stored thereon, when executed by a network node, causes the network node to: output a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node; output a first indication of uplink resources for uplink communication during at least one symbol or at least one time slot; output a second indication of downlink resources for downlink communication during at least one symbol or at least one time slot; and communicate during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

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

[0048] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication may be used to convey an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot, and the second indication may be used to convey an SSB within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot.

[0049] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes an uplink SFI related to at least one symbol or at least one time slot.

[0050] In some examples of the methods, apparatuses, 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.

[0051] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication may be used to convey a random access preamble within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot, and the second indication may be used to convey a downlink signal within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot.

[0052] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second indication includes a downlink SFI related to at least one symbol or at least one time slot.

[0053] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first indication can be used to convey an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot, and a second indication can be used to communicate using a downlink control channel within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot.

[0054] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes an uplink SFI related to at least one symbol or at least one time slot.

[0055] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first indication can be used to convey an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot, and a second indication can be used to convey a downlink signal within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot.

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

[0057] In some examples of the methods, apparatuses, 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.

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

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

[0060] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second indication includes a flexible RRC configuration related to at least one symbol or at least one time slot.

[0061] In some examples of the methods, apparatuses, 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.

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

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

[0064] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first indication includes a dynamic grant related to at least one symbol or at least one time slot, and the second indication includes a downlink SFI related to at least one symbol or at least one time 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, apparatuses, and non-transitory computer-readable media described herein, the second indication includes a downlink SFI or a flexible SFI related to at least one symbol or at least one time slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

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

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

[0068] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, 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 time slot.

[0069] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, 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 time slot.

[0070] In some examples of the methods, apparatuses, 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.

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

[0072] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, one or more prioritization rules include: in the absence of a beam failure recovery procedure being triggered, the conveyance of the downlink signal during at least one symbol or at least one time slot may be prioritized over the conveyance of the uplink signal, and in the presence of a beam failure recovery procedure being triggered, the conveyance of the uplink signal during at least one symbol or at least one time slot may be prioritized over the conveyance of the downlink signal.

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

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

[0075] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, one or more prioritization rules include: the conveyance of the downlink signal or the uplink signal may be prioritized based on the respective channel priorities associated with each of the downlink signal and the uplink signal.

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

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

[0078] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the control message further identifies one or more of the following: the frequency position of at least one uplink sub-band to be used for communicating an uplink message during at least one symbol or at least one time slot; at least one downlink sub-band to be used for communicating a downlink message during at least one symbol or at least one time slot; at least one guard band between the uplink sub-band and the downlink sub-band during at least one symbol or at least one time slot; and at least one flexible sub-band to be used for communicating an uplink message or a downlink message during at least one symbol or at least one time slot.

[0079] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the uplink resource or the downlink resource includes a periodic resource or a semi-persistent resource.

[0080] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the network node includes a base station. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] Figure 1 and Figure 2 each illustrate an example of a wireless communication system supporting multiplexing rules for sub-band full-duplex (SBFD) communication in accordance with one or more aspects of the present disclosure.

[0082] Figure 3A and Figure 3B illustrate an example of an SBFD configuration supporting multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure.

[0083] Figure 4 illustrate an example of a process flow supporting multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure.

[0084] Figure 5 and Figure 6 illustrate a block diagram of a device supporting multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure.

[0085] Figure 7 illustrate a block diagram of a communication manager supporting multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure.

[0086] Figure 8 illustrate a diagram of a system including a device supporting multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure.

[0087] Figure 9 and Figure 10A block diagram of a device that illustrates multiplexing rules for supporting SBFD communication in accordance with one or more aspects of the present disclosure.

[0088] Figure 11 A block diagram of a communication manager that illustrates multiplexing rules for supporting SBFD communication in accordance with one or more aspects of the present disclosure.

[0089] Figure 12 A diagram of a system that illustrates a device that includes multiplexing rules for supporting SBFD communication in accordance with one or more aspects of the present disclosure.

[0090] Figure 13 and Figure 14 A flowchart that illustrates a method that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION

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

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

[0093] In some examples, to reduce self-interference, a network entity may support sub-band full-duplex (SBFD) operation, where the network entity may use multiple sub-bands for uplink reception and downlink transmission. At the same time, a UE communicating with the network entity may be restricted to half-duplex communication. For example, the network entity may simultaneously use an uplink sub-band (or a flexible sub-band) to receive uplink communication from a first UE and use a downlink sub-band (or another flexible sub-band) to send downlink communication to a second UE. In such examples, these UEs may be configured to use half-duplex time-division duplex (TDD) to communicate with the network entity concurrently. That is, during a TTI, each UE may be able to communicate with the network entity in the uplink direction or the downlink direction. In some examples, the transmission direction of the TTI may be specified (e.g., configured at the UE). However, since the network entity may use a full-duplex sub-band for simultaneous uplink and downlink communication during the TTI, each UE may be able to communicate with the network entity in the uplink direction or the downlink direction during the TTI, regardless of the transmission direction specified for the TTI. That is, the use of a full-duplex sub-band at the network entity during the TTI may enable overriding the TDD TTI specification at the UE. However, in some examples, these UEs (e.g., as well as the network entity) may be configured with one or more multiplexing rules based on half-duplex operation. For example, according to such rules, these UEs may suppress monitoring (or the network entity may suppress sending) messages that schedule both uplink communication and downlink communication during the same TTI (e.g., the same time slot or symbol). Therefore, the multiplexing rules based on half-duplex operation may not support overriding the TDD TTI specification, which may result in reduced resource utilization and an unnecessary increase in latency.

[0094] Aspects of the present disclosure generally relate to techniques for supporting multiplexing rules for SBFD communication, and more particularly to an architecture for managing conflicting configuration information related to the same TTI. For example, a UE that performs TDD with a network entity may receive multiple (e.g., different) messages scheduling both uplink communication and downlink communication within the same TTI (e.g., the same time slot or the same symbol). In such an example, the UE may be configured with one or more multiplexing rules that support SBFD operation at the network entity. For example, such multiplexing rules may enable the UE to be configured with both an uplink configuration and a downlink configuration within the same TTI simultaneously. That is, the multiplexing rules that support SBFD operation at the network entity may enable the UE to receive conflicting configuration information related to the same TTI. In such an example, the UE may be configured with one or more prioritization rules to manage the conflicting configuration information. For example, the UE may use one or more prioritization rules to determine whether to communicate according to the uplink configuration or the downlink configuration during the TTI. In some examples, the prioritization rules may indicate to the UE to communicate an uplink signal according to the uplink configuration or a downlink signal according to the downlink configuration during the TTI based on the respective channel priorities associated with each of the downlink signal or the uplink signal.

[0095] Particular aspects of the subject matter described herein may be implemented to achieve one or more potential advantages. For example, the techniques employed by the described communication devices may provide benefits and enhancements to the operation of the communication devices, including enhancements to TDD communication between the communication devices. For example, the operations performed by the described communication devices may enable the communication devices to receive conflicting configuration information related to the same TTI and provide a framework for managing the conflicting configuration information. In some specific implementations, the operations performed by the described communication devices to manage the conflicting configuration information may include using one or more prioritization rules to identify the configuration to be used during the TTI. In an example, the operations performed by the described communication devices may support reduced latency and increased resource utilization and other benefits.

[0096] 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 configuration and process flows. Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flowcharts related to multiplexing rules for SBFD communication.

[0097] Figure 1An example of a wireless communication system 100 that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure is illustrated. 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.

[0098] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or having 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 and other designations. 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, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UEs 115 may support signal communication in accordance with one or more radio access technologies (RATs).

[0099] 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 stationary and mobile at different times. The UEs 115 may be devices in different forms or having different capabilities. Figure 1 Some example UEs 115 are illustrated. The UEs 115 described herein may be capable of supporting communication with various types of devices (such as Figure 1 other UEs 115 or network entities 105 as shown).

[0100] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include the following, may be the following, or may be included in the following (e.g., as a component of the following): a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, a device, an apparatus, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be 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 yet 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 be different from these examples. Similarly, references to UEs, base stations, devices, apparatuses, computing systems, etc. may include the disclosure of UEs, base stations, devices, apparatuses, computing systems, etc. as network nodes. For example, the disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended in accordance with this disclosure (e.g., the disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in reverse, but in a broad open-ended manner. In the above example where the disclosure that a UE is configured to receive information from a base station also discloses that a 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 device, a first apparatus, a first computing system, a first set of one or more components, a first processing entity, etc. configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second apparatus, a second computing system, a second set of one or more components, a second processing entity, etc.

[0101] As described herein, different terms may be used in various aspects to describe the conveyance of information (e.g., any information, signals, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the first network node is configured to provide, transmit, output, convey, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the second network node is configured to receive, obtain, or decode the information provided, transmitted, output, conveyed, or sent by the first network node.

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

[0103] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as a gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0104] In some examples, network entity 105 may be implemented in a split architecture (e.g., split base station architecture, split RAN architecture), which may be configured to utilize a protocol stack 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., a cloud RAN (C-RAN))). For example, network entity 105 may include one or more of the following: 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, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of network entity 105 in a split RAN architecture may be co-located, or one or more components of 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 split RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0105] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions are performed at the CU 160, DU 165, or RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU 160 and 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 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functionality and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be adopted between the DU 165 and 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 can support one or more different cells (e.g., via one or more RU 170s). In some cases, the functional split between the CU 160 and DU 165 or between the DU 165 and RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU 160 can be connected to one or more DU 165s via an intermediate transport communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RU 170s via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the intermediate transport communication link 162 or the fronthaul communication link 168 can be implemented according to the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the respective network entities 105 communicating via these communication links.

[0106] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be controlled in part 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 controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via the supported access and backhaul links (e.g., backhaul communication link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include a separate antenna set for relaying communications with the UE 115 or may share the same antenna (e.g., of the RU 170 of the IAB node 104) 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., IAB nodes 104, UEs 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the split RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0107] In the context of the techniques described herein being applied to the split RAN architecture, one or more components of the split RAN architecture may be configured to support the multiplexing rules for SBFD communication as described herein. For example, some operations described as being performed by the UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RICs 175, SMOs 180).

[0108] The UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where the "device" may also be referred to as a unit, a station, a terminal, or a client, etc. The UE 115 may also include or may 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 may 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 communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0109] The UE 115 described herein may be capable of communicating with various types of devices such as other UE 115s that may sometimes act as relays, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc., as Figure 1 shown.

[0110] The UE 115 and the network entity 105 may wirelessly communicate with each other via 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 for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion (e.g., bandwidth part (BWP)) of an RF spectrum band that operates 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 for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both frequency division duplex (FDD) and TDD component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "transmit", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0111] The communication link 125 shown in the wireless communication system 100 may include a downlink transmission (e.g., forward link transmission) from the network entity 105 to the UE 115, an uplink transmission (e.g., reverse link transmission) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink communication and uplink communication (e.g., in TDD mode).

[0112] 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 "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 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 a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent 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., sub-band, BWP) or all of the carrier bandwidth.

[0113] The signal waveform transmitted via a carrier may include multiple sub-carriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing an MCM technique, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one sub-carrier, in which case the symbol period and the sub-carrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during the transmission duration) and a relatively high-order 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 space resources (e.g., spatial layers or beams), and the use of multiple space resources may increase the data rate or data integrity for communication with the UE 115.

[0114] Time intervals for the network entity 105 or the UE 115 may be expressed as multiples of a basic time unit, which may refer, for example, to the sampling period T s =1 / (Δfmax ·N f ) seconds, where Δf max can represent the supported subcarrier spacing, and N f can represent the supported discrete Fourier transform (DFT) size. The time intervals of the communication resources can be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0115] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time 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 time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f number of) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0116] A subframe, time slot, mini-slot, or symbol may be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) 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 a burst of shortened TTIs (sTTIs)).

[0117] Physical channels can be reused according to various techniques to communicate using a carrier. For example, one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels to signal via a downlink carrier. The control region of a physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of a carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search a control region for control information according to one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format with a given payload size. The search space sets can include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set for transmitting control information to a specific UE 115.

[0118] In some examples, the network entity 105 (e.g., the base station 140, the RU 170) can be movable and thus provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different techniques can overlap, but different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different techniques can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

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

[0120] In some examples, UE 115 may be configured to communicate directly 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 performing D2D communication in a group may be within the coverage area 110 of a network entity 105 (e.g., base station 140, 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 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable 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, where each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving the network entity 105.

[0121] 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 (5GC), which may include at least one control plane entity that manages access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions, such as the mobility, authentication, and bearer management of UEs 115 served by a network entity 105 (e.g., base station 140) associated with the core network 130. User IP packets may be passed through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP services 150 of one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet-switched streaming services.

[0122] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or the decimeter band because, in terms of length, the wavelength range is from approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clutter, but these waves may be sufficient to penetrate structures so that a macro cell can serve a UE 115 located indoors. Compared with communications using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0123] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band) to employ licensed-assisted access (LAA), long-term evolution unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using an unlicensed band may be combined with component carriers operating using a licensed band based on a carrier aggregation configuration (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or device-to-device (D2D) transmissions, etc.

[0124] The network entity 105 (e.g., the base station 140, the RU 170) or the UE 115 may be equipped with multiple antennas, which may 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 located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as at an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports in multiple rows and columns that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays, which may support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel may support RF beamforming for signals transmitted via an antenna port.

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

[0126] Beamforming (which can also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a 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 device and the receiving device. Beamforming can be achieved by combining signals conveyed via the antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals conveyed via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or receiving device or relative to some other orientation).

[0127] The network entity 105 or the UE 115 may use beam scanning techniques as part of beamforming operations. For example, the network entity 105 (e.g., the base station 140, the RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent by the network entity 105 multiple times in different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by the transmitting device such as the network entity 105, or by the receiving device such as the UE 115)) the beam directions for later transmission or reception by the network entity 105.

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

[0129] In some examples, transmissions performed by a device (e.g., by network entity 105 or UE 115) may be carried out using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). 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. Network entity 105 may transmit reference signals (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying beam directions used by UE 115 for subsequent transmissions or receptions), or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

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

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

[0132] Figure 2 An example of a wireless communication system 200 that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement one or more aspects of the wireless communication system 100, or may be implemented in one or more of those aspects. For example, the wireless communication system 200 may include a network entity 205, a UE 215-a, and a UE 215-b, which may be examples of corresponding devices as discussed with reference to Figure 1 In some examples, the wireless communication system 200 may implement one or more aspects of the wireless communication system 100, or may be implemented in one or more of those aspects. For example, the wireless communication system 200 may include a UE 215-a and a UE 215-b, and the two UEs may be examples of the UE 115 as described with reference to Figure 1 The wireless communication system 200 may further include a network entity 205, which may be an example of the network entity as described with reference to Figure 1Examples of one or more network entities (e.g., CU, DU, RU, base station, IAB node, or one or more other network nodes) in the described network entity 105. The network entity 205 can communicate with the UE 215-a and the UE 215-b using the communication links 220-a and 220-b, respectively. The communication link 220 can be an example of the communication link 125 as described in reference Figure 1 The wireless communication system 200 can include features for improving communication between the network entity 205 and the UE 215 and other possible benefits.

[0133] The wireless communication system 200 (e.g., an NR system) can support one or more types of duplex operations (e.g., half-duplex operation, full-duplex operation). For example, the wireless communication system 200 can support one or more types of duplex operations for one or more deployment scenarios. An evaluation of one or more types of duplex operations (e.g., using an evaluation method) can be used to obtain performance evaluation results associated with one or more types of duplex operations supported within the wireless communication system 200. In some examples, the wireless communication system 200 can support sub-band non-overlapping full-duplex. For example, the wireless communication system 200 can support the coexistence of one or more uplink sub-bands and one or more downlink sub-bands in the same channel and adjacent channels. Additionally or alternatively, the wireless communication system 200 can support dynamic or flexible TDD. For example, the wireless communication system can support the coexistence of one or more uplink sub-bands and one or more downlink sub-bands in the same channel and adjacent channels that can be configured for TDD.

[0134] For example, the wireless communication system 200 may support one or more potential enhancements to support various types of duplex operations for TDD (e.g., duplex evolution). In some examples, the wireless communication system 200 may use paired radio frequency spectrum bands or unpaired radio frequency spectrum bands to support various types of duplex operations for TDD (e.g., NR TDD). In some instances, the paired radio frequency spectrum bands may be referred to as paired spectrums. Additionally or alternatively, the unpaired radio frequency spectrum bands may be referred to as unpaired spectrums. As described herein, a paired radio frequency spectrum band (e.g., a 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 paired with the first set of frequencies and configured for transmission at the communication device. In some examples of the paired operating band, the first set of frequencies (e.g., the first band, the first operating band, the first carrier) and the second set of frequencies (e.g., the second band, the second operating band, the 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 may have a frequency range or a set of subcarriers between the two sets of frequencies (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 that can be used for both transmission and reception at a communication device (e.g., a frequency range that may be referred to as a band, an operating band, or a carrier).

[0135] In some examples, the wireless communication system 200 may support one or more duplex enhancements 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 sub-band non-overlapping full duplex in a TDD carrier and one or more potential enhancements associated with dynamic TDD (which may also be referred to as flexible TDD). That is, the network entity 205 may support sub-band non-overlapping full duplex and one or more potential enhancements to dynamic TDD. As described herein, dynamic TDD may refer to a TDD operation in which the transmission direction associated with time domain resources can be dynamically assigned or reassigned. For example, time domain resources 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 for wireless communication between the network entity 205 and the UE 215 may not be constrained. 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).

[0136] In some examples, dynamic TDD may cause 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, network entity 205 may support one or more potential solutions to support sub-band non-overlapping full duplex and one or more potential enhancements to dynamic TDD. In some examples, one or more potential solutions may include one or more solutions for managing (e.g., mitigating, handling) cross-link interference (CLI) between network entities (e.g., between gNBs) and between UEs. As described herein, CLI may refer to interference experienced at a communication device (e.g., network entity 205, UE 215) when reception at the communication device overlaps (e.g., in the time domain) with transmission at another (e.g., adjacent) communication device. Additionally or alternatively, network entity 205 may support one or more solutions for managing in-band CLI and inter-band CLI (e.g., for sub-band non-overlapping full duplex). As described herein, in-band CLI may refer to CLI where interfering transmissions and receptions occur when multiple (e.g., different) sub-bands are used. Additionally or alternatively, inter-band CLI may refer to CLI where interfering transmissions and receptions occur when the same sub-band is used. In some examples, network entity 205 may support one or more operations to enable solutions for managing CLI (e.g., in-band CLI and inter-band CLI). For example, network entity 205 may support one or more operations related to coexistence of uplink sub-bands and downlink sub-bands in the same channel and adjacent channels.

[0137] In some examples, adjacent channel coexistence may result in one or more radio frequency constraints, such as due to self-interference at network entity 205 (e.g., gNB), inter-subband CLI, and inter-operator CLI. Additionally or alternatively, adjacent channel coexistence may result in one or more radio frequency constraints due to inter-subband CLI and inter-operator CLI at UE 215. As described herein, self-interference may refer to interference experienced at a communication device (e.g., network entity 205, a device capable of supporting full-duplex operation), which may be caused by signal leakage between an antenna panel used for transmission and another antenna panel used for reception at the communication device. 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., an adjacent network entity, an adjacent 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, a communication device may support antenna isolation, transmit interference measurement suppression (e.g., for reception), filtering, and digital interference suppression, among other possible examples. In such examples, wireless communication system 200 may support one or more aspects for deploying duplex enhancements for TDD (e.g., using unpaired spectrum).

[0138] As Figure 2As illustrated in the example, network entity 205 may support multi-user MIMO (MU-MIMO) communication with UE 215. For example, network entity 205 may support downlink MU-MIMO, where the network entity may simultaneously send downlink communication to UE 215-a and UE 215-b. Additionally or alternatively, network entity 205 may support uplink MU-MIMO, where the network entity may simultaneously receive uplink communication destined for UE 215-a and UE 215-b. In some examples, network entity 205 may use full-duplex operation to support downlink and uplink MU-MIMO. For example, network entity 205 may support full-duplex operation, where network entity 205 may simultaneously receive uplink communication from UE 215-a and send downlink communication to UE 215-b. Network entity 205 may use multiple beams (e.g., generated using one or more antenna panels) to support simultaneous communication with UE 215. For example, network entity 205 may use a first antenna panel to generate beam 210-a for receiving uplink communication from UE 215-a, and use a second antenna panel to generate beam 210-b for sending downlink communication to UE 215-b. In some examples, although full-duplex communication at network entity 205 may be spatially isolated (e.g., due to using different beams for downlink transmission and uplink reception at network entity 205), network entity 205 may experience self-interference 235. For example, network entity 205 may experience self-interference 235 due to signal leakage between the second antenna panel used for downlink transmission to UE 215-b and the first antenna panel used for uplink reception from UE 215-a. Additionally or alternatively, network entity 205 may experience clutter interference, for example, due 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 the signal transmitted from network entity 205 being reflected back to network entity 205 from a reflector (e.g., a reflective surface).

[0139] In some examples, to reduce the self-interference 235 experienced at network entity 205 (e.g., due to full-duplex communication), network entity 205 may use multiple (e.g., different) subbands for uplink reception and downlink transmission at network entity 205. For example, network entity 205 may support SBFD operation, where the network entity may use one or more subbands (e.g., uplink subbands, flexible subbands) to receive uplink from UE 215-a and use one or more other subbands (e.g., downlink subbands, flexible subbands) to transmit downlink to UE 215-b. That is, network entity 205 may support simultaneous transmission and reception of downlink and uplink communication on a subband basis. For example, network entity 205 may support SBFD operation, where network entity 205 may use the same TTI (e.g., the same time slot or the same symbol) to simultaneously receive uplink communication from UE 215-a using one or more uplink subbands (or one or more flexible subbands) and transmit downlink communication to UE 215-b using one or more downlink subbands (or one or more flexible subbands). In some examples, network entity 205 may use SBFD to achieve spatial isolation (e.g., using different beams) and frequency isolation (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 result in reduced latency. For example, network entity 205 may be configured to transmit one or more downlink signals in a TTI (e.g., time slot) configured for uplink communication, which may achieve reduced latency and improved one or more uplink coverage. Additionally or alternatively, SBFD operation may provide enhanced system capabilities, increased resource utilization, improved spectral efficiency, and other possible benefits. In some examples, implementing flexible and dynamic uplink and downlink resource adaptation (e.g., based on uplink or downlink traffic conditions) may increase the reliability of communication between UE 215 and network entity 205.

[0140] In some examples, although network entity 205 may be configured to support SBFD operations, network entity 205 and UE 215 may be configured with one or more multiplexing rules that may be based on (e.g., may assume) half-duplex operation at network entity 205. For example, within a TDD carrier, network entity 205 and UE 215 may be configured with one or more multiplexing rules for which TTIs may be used for transmission or reception. That is, network entity 205 and UE 215 may be configured to perform downlink channel and uplink channel (or downlink reference signal and uplink reference signal) prioritization and multiplexing according to one or more rules for half-duplex operation. In some examples, one or more rules for half-duplex operation may indicate that the transmission of a synchronization signal block (SSB) from network entity 205 may take precedence over (e.g., may cancel) an uplink transmission from UE 215. That is, UE 215 may be configured to prioritize the reception of the SSB from network entity 205 over the transmission of an uplink signal to network entity 205. For example, at UE 215, the reception of the SSB may take precedence over the 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), a sounding reference signal (SRS), and other examples of uplink signals. In some examples, a slot format indicator (SFI) may be used to configure (e.g., at UE 215) TTIs for uplink communication or downlink communication. For example, network entity 205 may use the SFI to signal (e.g., dynamically) the resource allocation for one or more TTIs. In some examples, the SFI may configure the allocated resources as downlink resources, uplink resources, or flexible resources. In some instances, resources configured in a flexible form may be rewritten (e.g., reassigned as uplink or downlink). For example, network entity 205 may send an SFI for uplink (SFI-U) to one or both of the UEs 215, which may indicate uplink resources for performing uplink communication during a TTI. In such an example, according to one or more rules for half-duplex operation, UE 215 may refrain from monitoring (e.g., may not expect to receive) the SFI-U within a TTI that may be configured for receiving the SSB.

[0141] Additionally or alternatively, network entity 205 may send a SFI (SFI-D) for the downlink to UE 215, which may indicate downlink resources for downlink communication during a TTI. In some examples, according to one or more rules for half-duplex operation, UE 215 may suppress monitoring (e.g., may not expect to receive) SFI-D within a TTI that may include (e.g., be configured with) one or more random access opportunities (e.g., valid random access opportunities) for transmitting a random access preamble. In some examples, one or more rules for half-duplex may indicate that UE 215 may suppress monitoring (e.g., may not expect to receive) SFI-U within a TTI that may be (e.g., using RRC configuration transmitted using the master information block (MIB)) configured with one or more control resource sets (CORESETs) such as CORESET 0. Additionally or alternatively, according to one or more rules for half-duplex, UE 215 may suppress monitoring (e.g., may not expect to receive) SFI-U within a TTI that may be configured for downlink communication (e.g., using RRC configuration). For example, UE 215 may receive an indication of one or more RRC parameters (e.g., TDD-UL-DL-ConfigCommon information element (IE), TDD-UL-DL-ConfigDedicated IE), which may identify the uplink and downlink TDD configurations (e.g., UE-specific configuration) of one or more TTIs. That is, the one or more RRC parameters may configure one or more TTIs for downlink communication or uplink communication at UE 215. In some examples, according to one or more rules for half-duplex, downlink communication configured using RRC configuration may have priority over uplink communication, such as the transmission of PUCCH signals, PUCCH signals, random access preambles (e.g., PRACH), or SRS. Additionally or alternatively, according to one or more rules for half-duplex, uplink communication configured using RRC configuration may have priority over downlink communication, including the monitoring of PDCCH (e.g., using CORESET) and the reception of PDSCH signals, channel state information reference signals (CSI-RS), or positioning reference signals (PRS) (e.g., in the absence of a measurement gap). For example, according to one or more rules for half-duplex, UE 215 may suppress monitoring (e.g., may not expect to receive) SFI-D within a TTI that may be configured for uplink communication (e.g., using RRC configuration). It should be understood that the names of the IEs described herein may change based on the specific implementation of one or more devices (e.g., UE 215, network entity 205), and the examples described herein should not be considered limited to the scope covered by the claims or this disclosure.

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

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

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

[0145] However, in some examples, one or more rules for half-duplex may result in an unnecessary increase in latency. For example, network entity 205 may be configured for SBFD operation, where the network entity may simultaneously use one or more uplink subbands (or flexible subbands) of an SBFD TTI (e.g., a time slot or symbol configured for SBFD communication) to communicate with a UE (e.g., UE 215-a) in the uplink and use one or more downlink subbands (or flexible subbands) of the same SBFD TTI to communicate with another UE (e.g., UE 215-b) in the downlink. In such examples, the downlink channel and uplink channel (or downlink reference signal and uplink reference signal) multiplexing constraints imposed by one or more rules for half-duplex may result in reduced resource utilization and an unnecessary increase in latency. Accordingly, one or more rules for half-duplex operation may be modified (or revoked) for SBFD communication such that UE 215 may receive an uplink configuration and a downlink configuration within the same TTI. That is, multiple configurations may be enabled for UE relaying or SBFD operation (or other full-duplex operations or modes) at network entity 205 such that network entity 205 may perform simultaneous uplink and downlink communication within an SBFD TTI (e.g., an SBFD symbol or time slot). In such an 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. Additionally, in such an example, network entity 205 may configure (or UE 215 may otherwise be configured with) one or more other rules (such as prioritization rule 245) for SBFD operation (or other full-duplex operations at network entity 205). For example, UE 21-b may use prioritization rule 245 to determine whether to transmit according to the uplink configuration or receive according to the downlink configuration during the TTI.

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

[0147] In such examples, UE 215-b (e.g., and UE 215-a) may be able to receive a downlink configuration and an 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 resource 260 to be used for uplink communication during TTI 240-a and a second indication 231 of downlink resource 265 to be used for downlink communication during TTI 240-a. In such an example, UE 215-b may use priority ordering rule 245 to determine whether to communicate according to the first indication 230 or the second indication 231 during TTI 240-a. That is, UE 215-b may communicate according to one of the first indication 230 or the second indication 231 during TTI 240-a based on priority ordering rule 245. For example, based on priority ordering rule 245, UE 215-b may use one or more of downlink subbands 255 to receive a downlink signal during TTI 240-a, or use uplink subband 250 to send an uplink signal during TTI 240-a.

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

[0149] Additionally or alternatively, UE 215-b may receive an indication of a random access opportunity (e.g., a valid random access opportunity) in the uplink subband 250 during TTI 240-a (e.g., SBFD symbol), which TTI may also be configured for downlink communication using SFI-D. That is, the first indication 230 may be used to transmit a random access preamble within the uplink subband 250 during TTI 240-a, and the second indication 231 may be used to receive downlink signals in one or more of the downlink subbands 255 during TTI 240-a. In such an example, the second indication 231 may include SFI-D related to TTI 240-a.

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

[0151] In some examples, the first indication 230 may be used to transmit an uplink signal within the uplink subband 250 during the TTI 240-a. In such examples, the first indication 230 may include SFI-U, SFI-F, RRC configuration, or a dynamic grant related to the TTI 240-a. Additionally or alternatively, the second indication 231 may be used to receive a downlink signal within one or more of the downlink subbands 255 during the TTI 240-a. In such examples, the second indication 231 may include SFI-D, SFI-F, 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., SBFD symbol), and the downlink communication may overlap with the uplink communication (e.g., transmission of PUCCH signal, PUCCH signal, PRACH, or 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 SFI-U. In such examples, 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 have priority over downlink communication). In some examples, such a rule may be used at the network entity 205 to dynamically rewrite a previously configured communication (e.g., may be used for dynamic rewriting).

[0152] Additionally or alternatively, UE 215-b may receive an RRC configuration that may indicate uplink resources 260 for uplink communication using uplink sub-band 250 during TTI 240-a (e.g., an SBFD symbol), where the uplink communication may overlap with downlink communication configured in one or more of downlink sub-bands 255 during TTI 240-a (e.g., monitoring of a CORESET or transmission of a PDSCH signal, CSI-RS, or PRS in the absence of a measurement gap). That is, the first indication 230 may include an uplink RRC configuration that may be indicated to UE 215-b using SFI-D. In such examples, the prioritization rule 245 may include a rule indicating that TTI 240-a may be used for downlink communication (e.g., downlink communication may have priority over uplink communication). In some examples, such a rule may be used at network entity 205 to dynamically rewrite previously configured communication (e.g., may be used for dynamic rewriting).

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

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

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

[0156] Figure 3A and Figure 3B illustrates an example of an SBFD configuration 300 that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure. The SBFD configuration 300 (e.g., SBFD configuration 300-a and SBFD configuration 300-b) may be implemented in one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the SBFD configuration 300 may be implemented at a network entity or a UE or both, which may be examples of corresponding devices as discussed in reference Figure 1 and Figure 2 The SBFD configuration 300 may include features for improving communication between the network entity and the UE and other possible benefits.

[0157] In some examples, a network entity (e.g., gNB) may use SBFD time slots or symbols (which may be referred to as TTIs) to support SBFD or another full-duplex mode. That is, the network entity (e.g., gNB) may receive uplink communication while transmitting downlink communication. In such examples, to reduce overhead, the network entity and the UE may support SBFD configuration 300, which may provide a configured downlink opportunity and a configured uplink opportunity that will coexist on a TTI (e.g., the same symbol). As Figure 3A illustrated in the example of, SBFD configuration 300-a may provide an uplink opportunity using uplink subband 315-a and a downlink opportunity using downlink subband 320-a or downlink subband 320-b or both. That is, the UE may receive an indication of uplink resource 325 for using uplink subband 315-a to transmit an uplink signal during TTI 305-a and downlink resource 330 for using one or both of downlink subband 320-a and downlink subband 320-b to receive a downlink signal 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).

[0158] Additionally or alternatively, as Figure 3B illustrated in the example of, SBFD configuration 300-b may provide an uplink opportunity using uplink subband 315-b and a downlink opportunity using downlink subband 320-c. That is, the UE may receive an indication of uplink resource 325 for using uplink subband 315-b to transmit an uplink signal during TTI 305-b and downlink resource 330 for using downlink subband 320-c to receive a downlink signal during TTI 305-b. 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).

[0159] As Figure 3AAs illustrated in the example, the uplink opportunity (e.g., uplink resource 325) configured in the uplink subband 315-a can coexist with the downlink opportunities (e.g., downlink resources 330) in the downlink subbands 320-a and 320-b of the TTI 305-a. In some examples, the TTI 305-a (e.g., SBFD symbol) can be configured for downlink communication using SFI-D. For example, the UE can receive an RRC configuration indicating the uplink resource 325 for transmitting an uplink signal using the uplink subband 315-a during the TTI 305-a, and can receive the SFI-D related to the TTI 305-a. In such an example, the UE can use one or more prioritization rules to determine whether to receive a downlink signal during the TTI 305-a according to the SFI-D (e.g., downlink dynamic grant) or to transmit an uplink signal during the TTI 305-a according to the RRC configuration. For example, it may not be possible to trigger a beam failure recovery process at the UE. In such an example, according to one or more prioritization rules, the UE can determine to communicate with the network entity according to the SFI-D during the TTI 305-a. For example, the UE can use the SFI-D to receive a downlink signal during the TTI 305-a. In some examples, the downlink signal can include a PDSCH signal, an SPS signal, or a CSI-RS that can be indicated to the UE using a dynamic grant. In some other examples, a beam failure recovery can be triggered at the UE. In such examples, the UE can suppress the reception (e.g., discard) of the downlink signal and can transmit an uplink signal (e.g., SRS or PRACH) within the beam failure recovery process triggered during the TTI 305-a (e.g., on the TTI configured with SFI-D).

[0160] Additionally or alternatively, a configured downlink opportunity (e.g., downlink resource 330) in one or both of downlink sub-bands 320-a and 320-b during TTI 305-a may coexist with an uplink opportunity (e.g., uplink resource 325) in uplink sub-band 315-a of TTI 305-a. For example, the UE may receive an RRC configuration that identifies flexible resources (e.g., flexible symbols) for transmitting an uplink signal or receiving a downlink signal during TTI 305-a (e.g., in the absence of a slot format provided using SFI). In such an example, a configured downlink opportunity (e.g., downlink resource 330) in one or both of downlink sub-bands 320-a and 320-b during TTI 305-a may coexist with an uplink opportunity (e.g., uplink resource 325) in uplink sub-band 315-a during TTI 305-a. In such examples, if the beam failure recovery procedure is not triggered at the UE, the UE may determine to use (e.g., according to one or more prioritization rules) the RRC configuration for flexible communication during TTI 305-a. For example, the UE may determine to receive a configured downlink signal (e.g., SPS signal or CSI-RS). Additionally or alternatively, if the beam failure recovery procedure is triggered at the UE, the UE may determine to suppress receiving (e.g., may discard) the downlink signal and may use TTI 305-a to transmit an uplink signal for beam failure recovery (e.g., SRS signal or PRACH). That is, one or more prioritization rules may include: in the absence of the beam failure recovery procedure being triggered, receiving a downlink signal using downlink sub-band 320-a or downlink sub-band 320-b (or both) during TTI 305-a may take precedence over transmitting an uplink signal using uplink sub-band 315-a. Additionally or alternatively, the prioritization rules may include: in the presence of the beam failure recovery procedure being triggered, transmitting an uplink signal during TTI 305-a may take precedence over receiving a downlink signal. In some examples, the prioritization rules may be based on the priority or type of a communication channel associated with the communication channel to be used for transmitting the uplink signal and another communication channel to be used for receiving the downlink signal. Additionally or alternatively, the prioritization rules may be based on one or more other suitable types of rules. In some examples, using the prioritization rules to determine whether to receive a downlink signal or transmit an uplink signal during TTI 305-a may result in increased resource utilization, reduced latency, and other possible benefits.

[0161] Figure 4An example of a process flow 400 that illustrates multiplexing rules in support of SBFD communication in accordance with one or more aspects of the present disclosure is shown. 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 the network entity 405 and the UE 415, which may be example devices as described with reference to Figure 1 , Figure 2 , Figure 3A and Figure 3B . Operations performed at the network entity 405 and the UE 415 may support improvements in communication between the UE 415 and the network entity 405 and other benefits. In the following description of the process flow 400, the operations between the UE 415 and the network entity 405 may occur in an order different from the example order shown. Additionally or alternatively, the operations performed by the UE 415 and the network entity 405 may occur in a different order or at different times. Some operations may also be omitted. In the example of Figure 4 , the network entity 405 may be configured for SBFD operation, where the network entity 405 may communicate with multiple UEs (e.g., including the UE 415) simultaneously using an SBFD TTI (e.g., a time slot or symbol configured for SBFD communication). For example, the network entity 405 may use one or more uplink subbands (or one or more flexible subbands) to communicate with a UE on the uplink and one or more downlink subbands (or one or more flexible subbands) of the same SBFD TTI to communicate with another UE on the downlink.

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

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

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

[0165] At 435, the UE 415 can communicate with the network entity 405 based on one or more prioritization rules according to the first indication or the second indication during at least one SBFD TTI. In some examples, the prioritization rules can be examples of the prioritization rules described throughout this disclosure (including reference to Figure 2 )Examples of the prioritization rules described. For example, the prioritization rules can include: when no beam failure recovery process is triggered (e.g., at the UE 415), the reception of a downlink signal during at least one SBFD TTI takes precedence over the transmission of an uplink signal. Additionally or alternatively, the prioritization rules can include: when a beam failure recovery process is triggered (e.g., at the UE 415), the transmission of an uplink signal during at least one SBFD TTI takes precedence over the reception of a downlink signal. In some examples, the prioritization rules can include: prioritizing the reception of a downlink signal or the transmission of an uplink signal based on the respective channel priorities associated with each of the downlink signal and the uplink signal.

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

[0167] In some other examples, at 445, the UE 415 may receive a downlink signal 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 signal may be an example of a downlink signal as described throughout this disclosure (including references Figure 2 ). For example, the downlink signal may include a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS. In some examples, using priority ordering rules to determine whether to receive a downlink signal or transmit an uplink signal during at least one SBFD TTI may result in increased resource utilization, reduced latency, and other possible benefits.

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

[0169] The receiver 510 may provide components 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 related to multiplexing rules for SBFD communication). The information may be passed to other components of the device 505. The receiver 510 may utilize a single antenna or an array of multiple antennas.

[0170] The transmitter 515 may provide components for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to multiplexing rules for SBFD communication), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or an array of multiple antennas.

[0171] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their various components may be examples of components for performing various aspects of the multiplexing rules for SBFD communication as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components may support methods for performing one or more of the functions described herein.

[0172] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). 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 components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in this disclosure. In some examples, a processor and a 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).

[0173] Additionally or alternatively, in some examples, the communication 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., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication 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 that is configured to or otherwise supports components for performing the functions described in this disclosure.

[0174] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 520 may receive information from the receiver 510, convey information to the transmitter 515, or integrate in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

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

[0176] By including or configuring communication manager 520 according to examples described herein, device 505 (e.g., a processor that controls or otherwise couples to receiver 510, transmitter 515, communication manager 520, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0177] Figure 6 Block diagram 600 illustrates a device 605 that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0178] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., a control channel, a data channel, an information channel related to multiplexing rules for SBFD communication). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or an array of multiple antennas.

[0179] The transmitter 615 can provide components for transmitting signals generated by other components of the device 605. For example, the transmitter 615 can transmit information associated with various information channels (e.g., control channels, data channels, information channels related to the multiplexing rules for SBFD communication), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 can be co-located with the receiver 610 in a transceiver module. The transmitter 615 can utilize a single antenna or an array of multiple antennas.

[0180] The device 605 or its various components can be examples of components for performing aspects of the multiplexing rules for SBFD communication as described herein. For example, the communication manager 620 can include a control message component 625, an uplink component 630, a downlink component 635, a prioritization component 640, or any combination thereof. The communication manager 620 can be an example of aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components can be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 620 can receive information from the receiver 610, convey information to the transmitter 615, or integrate with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

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

[0182] Figure 7FIG. 700 is a block diagram illustrating a communication manager 720 that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure. The communication manager 720 may be an example of the communication manager 520, the communication manager 620, or aspects of both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of the multiplexing rules for SBFD communication as described herein. For example, the communication 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 one another (e.g., via one or more buses).

[0183] In accordance with an example as disclosed herein, the communication manager 720 may support wireless communication at a first network node. The control message component 725 may be configured to or otherwise support a component for receiving a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a second network node. The uplink component 730 may be configured to or otherwise support a component for receiving a first indication of uplink resources to be used for uplink communication during at least one symbol or at least one time slot. The downlink component 735 may be configured to or otherwise support a component for receiving a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot. The prioritization component 740 may be configured to or otherwise support a component for communicating with the second network node during at least one symbol or at least one time slot based on one or more prioritization rules in accordance with one of the first indication or the second indication.

[0184] In some examples, the uplink resources are located within at least one uplink subband or at least one flexible subband. Additionally, the downlink resources are located within at least one downlink subband or at least one flexible subband. In some examples, the first indication is for transmitting an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot. Additionally or alternatively, the second indication is for receiving a synchronization signal block within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot. In some examples, the first indication includes an uplink SFI related to at least one symbol or at least one time slot. In some examples, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0185] In some examples, the first indication is used to transmit a random access preamble within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot. In some examples, the second indication is used to receive a downlink signal within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot. Additionally or alternatively, the second indication includes a downlink SFI related to at least one symbol or at least one time slot.

[0186] In some examples, the first indication is used to transmit an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot. In some examples, the second indication is used to monitor a downlink control channel within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot. Additionally or alternatively, the first indication includes an uplink SFI related to at least one symbol or at least one time slot.

[0187] In some examples, the first indication is used to transmit an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot. Additionally, the second indication is used to receive a downlink signal within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot.

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

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

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

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

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

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

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

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

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

[0197] 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 time 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 time slot.

[0198] In some examples, the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble. Additionally or alternatively, the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0199] In some examples, one or more prioritization rules include: in the absence of a beam failure recovery procedure being triggered, reception of a downlink signal during at least one symbol or at least one time slot takes precedence over transmission of an uplink signal, and in the presence of a beam failure recovery procedure being triggered, transmission of an uplink signal during at least one symbol or at least one time slot takes precedence over reception of a downlink signal. In some examples, the second indication includes a downlink SFI related to at least one symbol or at least one time slot, and wherein 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 time slot, and wherein the uplink signal includes an SRS or a random access preamble.

[0200] In some examples, one or more prioritization rules include: prioritizing reception of a downlink signal or transmission of an uplink signal based on respective channel priorities associated with each of the downlink signal and the uplink signal.

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

[0202] In some examples, the first indication is for a first component carrier of a radio frequency band, and the second indication is for a second component carrier of the radio frequency band, the first component carrier being different from the second component carrier.

[0203] In some examples, the control message further identifies one or more of the following: the frequency position of at least one uplink sub-band to be used for transmitting an uplink message during at least one symbol or at least one time slot; at least one downlink sub-band to be used for receiving a downlink message during at least one symbol or at least one time slot; at least one guard band between the uplink sub-band and the downlink sub-band during at least one symbol or at least one time slot; and at least one flexible sub-band to be used for transmitting an uplink message or receiving a downlink message during at least one symbol or at least one time slot.

[0204] In some examples, the uplink resources or the 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.

[0205] Figure 8FIG. illustrates a system 800 including a device 805 that supports multiplexing rules for SBFD communication, in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include components of the device 505, the device 605, or the UE 115 as described herein. The device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 805 may include components for two-way voice and data communication, including components for sending and receiving communication, such as a communication 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 communicate electronically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

[0206] The I / O controller 810 may manage input and output signals of the device 805. The I / O controller 810 may also manage peripheral devices not integrated into 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 or another operating system. Additionally or alternatively, the I / O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touch screen, or similar devices. 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 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0207] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired or wireless link, as 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 that is configured to: modulate packets; provide the modulated packets to one or more antennas 825 for transmission; and demodulate packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of or include components of the transmitter 515, the transmitter 615, the receiver 510, the receiver 610, or any combination thereof as described herein.

[0208] The memory 830 may include a random access memory (RAM) and a 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 the various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as the 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 the computer to perform the functions described herein. In some cases, among other things, the memory 830 may further contain a basic input / output system (BIOS) that may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0209] The processor 840 may include intelligent hardware devices (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, the 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 the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting multiplexing rules for SBFD communication). For example, the device 805 or components of the device 805 may include the processor 840 and the memory 830 coupled to or coupled with the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0210] According to an example as disclosed herein, the communication manager 820 may support wireless communication at a first network node (e.g., the device 805). For example, the communication manager 820 may be configured to or otherwise support components for receiving a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a second network node. The communication manager 820 may be configured to or otherwise support components for receiving a first indication of uplink resources for use in uplink communication during at least one symbol or at least one time slot. The communication manager 820 may be configured to or otherwise support components for receiving a second indication of downlink resources for use in downlink communication during at least one symbol or at least one time slot. The communication manager 820 may be configured to or otherwise support components for communicating with the second network node during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0211] By including or configuring a communication manager 820 according to examples as described herein, device 805 may support techniques for improving communication reliability, reducing latency, and more efficiently utilizing communication resources.

[0212] In some examples, communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in concert with transceiver 815, one or more antennas 825, or any combination thereof. Although communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to communication manager 820 may be supported or performed by processor 840, memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that, when executed by processor 840, cause device 805 to perform aspects of the multiplexing rules for SBFD communication as described herein, or processor 840 and memory 830 may otherwise be configured to perform or support such operations.

[0213] Figure 9 Block diagram 900 illustrates a device 905 that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

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

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

[0216] The communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can be examples of components for performing various aspects of the multiplexing rules for SBFD communication as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can support methods for performing one or more of the functions described herein.

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

[0218] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can 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 configured to or otherwise supporting components for performing the functions described in this disclosure.

[0219] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in concert with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, convey information to the transmitter 915, or integrate in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0220] In accordance with examples disclosed herein, the communication manager 920 may support wireless communication at a network node (e.g., device 905). For example, the communication manager 920 may be configured to or otherwise support a component for outputting a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node. The communication manager 920 may be configured to or otherwise support a component for outputting a first indication of uplink resources to be used for uplink communication during at least one symbol or at least one time slot. The communication manager 920 may be configured to or otherwise support a component for outputting a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot. The communication manager 920 may be configured to or otherwise support a component for communicating during at least one symbol or at least one time slot in accordance with one of the first indication or the second indication based on one or more prioritization rules.

[0221] By including or configuring a communication manager 920 in accordance with examples described herein, a device 905 (e.g., a processor that controls the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof or is otherwise coupled thereto) may support techniques for more efficiently utilizing communication resources.

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

[0223] The receiver 1010 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). 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, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0224] The transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). 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, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0225] The device 1005 or its various components may be examples of components for performing various aspects of the multiplexing rules for SBFD communication as described herein. For example, the communication manager 1020 may include SBFD components 1025, uplink indication components 1030, downlink indication components 1035, rule components 1040, or any combination thereof. The communication manager 1020 may be an example of aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, convey information to the transmitter 1015, or integrate in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0226] According to an example as disclosed herein, the communication manager 1020 may support wireless communication at a network node (e.g., device 1005). The SBFD component 1025 may be configured to or otherwise support a component for outputting a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node. The uplink indication component 1030 may be configured to or otherwise support a component for outputting a first indication of uplink resources to be used for uplink communication during at least one symbol or at least one time slot. The downlink indication component 1035 may be configured to or otherwise support a component for outputting a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot. The rules component 1040 may be configured to or otherwise support a component for communicating during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0227] Figure 11 FIG. 1100 illustrates a block diagram of a communication manager 1120 that supports multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the multiplexing rules for SBFD communication as described herein. For example, the communication 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 each other (e.g., via one or more buses), and such communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualized components associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0228] According to an example as disclosed herein, the communication manager 1120 may support wireless communication at a network node. The SBFD component 1125 may be configured to or otherwise support a component for outputting a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node. The uplink indication component 1130 may be configured to or otherwise support a component for outputting a first indication of uplink resources to be used for uplink communication during at least one symbol or at least one time slot. The downlink indication component 1135 may be configured to or otherwise support a component for outputting a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot. The rule component 1140 may be configured to or otherwise support a component for communicating during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0229] In some examples, the uplink resources are located within at least one uplink subband or at least one flexible subband. In some examples, the downlink resources are located within at least one downlink subband or at least one flexible subband.

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

[0231] In some examples, the first indication is used to convey a random access preamble within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot. In some examples, the second indication is used to convey a downlink signal within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot. Additionally or alternatively, the second indication includes a downlink SFI related to at least one symbol or at least one time slot.

[0232] In some examples, the first indication is used to convey an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot. In some examples, the second indication may be used to communicate using a downlink control channel within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot. Additionally or alternatively, the first indication includes an uplink SFI related to at least one symbol or at least one time slot.

[0233] In some examples, the first indication is used to convey an uplink signal within at least one uplink subband or at least one flexible subband during at least one symbol or at least one time slot. In some examples, the second indication is used to convey a downlink signal within at least one downlink subband or at least one flexible subband during at least one symbol or at least one time slot.

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

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

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

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

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

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

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

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

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

[0243] 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 time 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 time 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.

[0244] In some examples, one or more prioritization rules include: in the absence of a beam failure recovery process being triggered, the conveyance of the downlink signal during at least one symbol or at least one time slot takes precedence over the conveyance of the uplink signal, and in the presence of a beam failure recovery process being triggered, the conveyance of the uplink signal during at least one symbol or at least one time slot takes precedence over the conveyance of the downlink signal. In some examples, the second indication includes a downlink SFI related to at least one symbol or at least one time slot, and wherein 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 time slot, and wherein the uplink signal includes an SRS or a random access preamble.

[0245] In some examples, one or more prioritization rules include: prioritizing the conveyance of downlink signals or uplink signals based on respective channel priorities associated with each of the downlink signals and the uplink signals.

[0246] In some examples, uplink resources and downlink resources are within one or more carriers to be used for TDD communication at a network node. In some examples, a first indication is for a first component carrier of a radio frequency band, and a second indication is for a second component carrier of the radio frequency band, the first component carrier being different from the second component carrier.

[0247] In some examples, the control message further identifies one or more of the following: the frequency location of at least one uplink subband to be used for conveying an uplink message during at least one symbol or at least one time slot; at least one downlink subband to be used for conveying a downlink message during at least one symbol or at least one time slot; at least one guard band between the uplink subband and the downlink subband during at least one symbol or at least one time slot; and at least one flexible subband to be used for conveying an uplink message or a downlink message during at least one symbol or at least one time slot.

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

[0249] Figure 12 FIG. 1200 illustrates a system 1200 including a device 1205 that supports multiplexing rules for SBFD communication 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, the device 1005, or the network entity 105 as described herein. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, the communication including communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0250] 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 sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components, which may be operable to perform the following operations: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination of these operations. 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 processors or memory components (e.g., processor 1235 or memory 1225 or both) may be included in a chip or chip component installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0252] Processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, 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 communication). For example, device 1205 or components of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, and processor 1235 and memory 1225 are configured to perform the 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 functions (e.g., by executing code 1230) for performing the functions 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 in device 1205 (such as within memory 1225). In some specific implementations, processor 1235 may be a component of a processing system. A processing system generally may refer to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs (which may be passed to other systems or components such as, for example, device 1205). For example, the processing system of device 1205 may refer to a system including various other components or sub-components of device 1205, such as processor 1235, or transceiver 1210, or communication manager 1220, or a combination of other components or 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 or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a transmitter such that device 1205 may transmit information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a receiver such that device 1205 may obtain information or signal inputs, and the information may be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0253] In some examples, the bus 1240 may support communication within a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, the bus 1240 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of the device 1205, or communication performed between different components of the device 1205 that may be co-located or located at different locations (e.g., where the device 1205 may refer to a system in which one or more of the communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one component or divided between different components).

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

[0255] According to examples disclosed herein, the communication manager 1220 may support wireless communication at a network node (e.g., the device 1205). For example, the communication manager 1220 may be configured or otherwise support a component for outputting a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at the network node. The communication manager 1220 may be configured or otherwise support a component for outputting a first indication of uplink resources to be used for uplink communication during at least one symbol or at least one time slot. The communication manager 1220 may be configured or otherwise support a component for outputting a second indication of downlink resources to be used for downlink communication during at least one symbol or at least one time slot. The communication manager 1220 may be configured or otherwise support a component for communicating during at least one symbol or at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

[0256] By including or configuring a communication manager 1220 according to the examples described herein, the device 1205 may support techniques for improving communication reliability, reducing latency, and more efficiently utilizing communication resources.

[0257] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more of the functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions that can be executed by the processor 1235 to cause the device 1205 to perform various aspects of the multiplexing rules for SBFD communication as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0258] Figure 13 A flowchart is illustrated that illustrates a method 1300 for supporting multiplexing rules for SBFD communication in accordance with one or more aspects of the present disclosure. The operations of method 1300 may be implemented by a UE or its components as described herein. For example, the operations of method 1300 may be performed by a UE 115 as described with reference to Figures 1 to 8 In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions.

[0259] At 1305, the method may include receiving a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a second network node. The operation of 1305 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation of 1305 may be performed by a control message component 725 as described with reference to Figure 7 In some examples, aspects of the operation of 1305 may be performed by a control message component 725 as described with reference to

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

[0261] 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 time slot. The operations at 1315 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1315 may be performed by a downlink component 735 as described with reference to Figure 7 as described.

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

[0263] Figure 14 Illustrates a flowchart that illustrates a method 1400 for supporting multiplexing rules for SBFD communication according to one or more aspects of the present disclosure. The operations of method 1400 may be implemented by a network entity or its components as described herein. For example, the operations of method 1400 may be performed by a network entity as described with reference to Figures 1 to 4 and Figures 9 to 12 as described. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the functions.

[0264] At 1405, the method may include outputting a control message that identifies at least one symbol or at least one time slot to be used for SBFD communication at a network node. The operations at 1405 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1405 may be performed by an SBFD component 1125 as described with reference to Figure 11 as described.

[0265] 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 time slot. The operations at 1410 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1410 may be performed by an uplink indication component 1130 as described with reference to Figure 11 as described.

[0266] 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 time slot. The operations at 1415 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1415 may be performed by a component as described with reference toFigure 11 performed by the described downlink indication component 1135.

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

[0268] An overview of aspects of the present disclosure is provided below:

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

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

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

[0272] Aspect 4: The method according to aspect 3, wherein the first indication includes an uplink SFI related to the at least one symbol or the at least one time slot.

[0273] Aspect 5: The method according to 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.

[0274] Aspect 6: The method according to any one of Aspects 1 to 2, wherein the first indication is for transmitting a random access preamble within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is for receiving a downlink signal within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

[0275] Aspect 7: The method according to Aspect 6, wherein the second indication includes a downlink SFI related to the at least one symbol or the at least one time slot.

[0276] Aspect 8: The method according to any one of Aspects 1 to 2, wherein the first indication is for transmitting an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is for monitoring a downlink control channel within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

[0277] Aspect 9: The method according to Aspect 8, wherein the first indication includes an uplink SFI related to the at least one symbol or the at least one time slot.

[0278] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the first indication is for transmitting an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is for receiving a downlink signal within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

[0279] Aspect 11: The method according to Aspect 10, wherein the first indication includes an uplink SFI related to the at least one symbol or the at least one time slot, and the second indication includes an RRC configuration related to the at least one symbol or the at least one time slot.

[0280] Aspect 12: The method according to Aspect 11, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0281] Aspect 13: The method according to Aspect 10, wherein the first indication includes an RRC configuration related to the at least one symbol or the at least one time slot, and the second indication includes a downlink SFI related to the at least one symbol or the at least one time slot.

[0282] Aspect 14: The method according to aspect 13, wherein the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

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

[0284] Aspect 16: The method according to aspect 15, wherein the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

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

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

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

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

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

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

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

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

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

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

[0295] Aspect 27: The method according to aspect 10, wherein the one or more prioritization rules include: in the absence of a beam failure recovery process being triggered, the reception of the downlink signal during the at least one symbol or the at least one time slot takes precedence over the transmission of the uplink signal, and in the presence of a beam failure recovery process being triggered, the transmission of the uplink signal during the at least one symbol or the at least one time slot takes precedence over the reception of the downlink signal.

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

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

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

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

[0300] Aspect 32: The method according to any one of aspects 1 to 31, wherein the first indication is for a first component carrier of a radio frequency band, and the second indication is for a second component carrier of the radio frequency band, the first component carrier being different from the second component carrier.

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

[0302] Aspect 34: The method according to aspect 1, wherein the uplink resources or the downlink resources include periodic resources or semi-persistent resources.

[0303] Aspect 35: The method according to any one of aspects 1 to 34, wherein the first network node includes a UE, and the second network node includes a base station.

[0304] Aspect 36: A method for wireless communication at a network node, the method comprising: outputting a control message that identifies at least one symbol or at least one time 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 the at least one time slot; outputting a second indication of downlink resources for downlink communication during the at least one symbol or the at least one time slot; and communicating during the at least one symbol or the at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

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

[0306] Aspect 38: The method according to any one of aspects 36 to 37, wherein the first indication is for communicating an uplink signal within at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one time slot, and the second indication is for communicating an SSB within at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one time slot.

[0307] Aspect 39: The method according to aspect 38, wherein the first indication includes an uplink SFI related to the at least one symbol or the at least one time slot.

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

[0309] Aspect 41: The method according to any one of aspects 36 to 37, wherein the first indication is for communicating a random access preamble within at least one uplink subband or at least one flexible subband during the at least one symbol or the at least one time slot, and the second indication is for communicating a downlink signal within at least one downlink subband or the at least one flexible subband during the at least one symbol or the at least one time slot.

[0310] Aspect 42: The method according to aspect 41, wherein the second indication includes a downlink SFI related to the at least one symbol or the at least one time slot.

[0311] Aspect 43: The method according to any one of Aspects 36 to 37, wherein the first indication is used to convey an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is used to communicate using a downlink control channel within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

[0312] Aspect 44: The method according to Aspect 43, wherein the first indication includes an uplink SFI related to the at least one symbol or the at least one time slot.

[0313] Aspect 45: The method according to any one of Aspects 36 to 37, wherein the first indication is used to convey an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is used to convey a downlink signal within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

[0314] Aspect 46: The method according to Aspect 45, wherein the first indication includes an uplink SFI related to the at least one symbol or the at least one time slot, and the second indication includes an RRC configuration related to the at least one symbol or the at least one time slot.

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

[0316] Aspect 48: The method according to any one of Aspects 36 to 37, wherein the first indication includes an RRC configuration related to the at least one symbol or the at least one time slot, and the second indication includes a downlink SFI related to the at least one symbol or the at least one time slot.

[0317] Aspect 49: The method according to Aspect 48, wherein the downlink signal includes a PDCCH signal, a PDSCH signal, a CSI-RS, or a PRS.

[0318] Aspect 50: The method according to any one of Aspects 36 to 37, wherein the second indication includes a flexible RRC configuration related to the at least one symbol or the at least one time slot.

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

[0320] Aspect 52: The method according to any one of Aspects 36 to 37, wherein the first indication includes an uplink SFI related to the at least one symbol or the at least one time slot, and the second indication includes a dynamic grant related to the at least one symbol or the at least one time slot, and the downlink signal includes a PDSCH signal or a CSI-RS.

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

[0322] Aspect 54: The method according to any one of Aspects 36 to 37, wherein the first indication includes a dynamic grant related to the at least one symbol or the at least one time slot, and the second indication includes a downlink SFI related to the at least one symbol or the at least one time slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

[0323] Aspect 55: The method according to any one of Aspects 36 to 37, wherein the second indication includes a downlink SFI or a flexible SFI related to the at least one symbol or the at least one time slot, and the uplink signal includes a PUCCH signal, a PUSCH signal, an SRS, or a random access preamble.

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

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

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

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

[0328] Aspect 60: The method according to any one of aspects 36 to 37, wherein the uplink signal includes a PUCCH signal, PUSCH signal, SRS, or random access preamble.

[0329] Aspect 61: The method according to any one of aspects 36 to 37, wherein the downlink signal includes a PDCCH signal, PDSCH signal, CSI-RS, or PRS.

[0330] Aspect 62: The method according to any one of aspects 45 to 61, wherein the one or more prioritization rules include: in the absence of a beam failure recovery process being triggered, the conveyance of the downlink signal during the at least one symbol or the at least one time slot takes precedence over the conveyance of the uplink signal, and in the presence of a beam failure recovery process being triggered, the conveyance of the uplink signal during the at least one symbol or the at least one time slot takes precedence over the conveyance of the downlink signal.

[0331] Aspect 63: The method according to aspect 62, wherein the second indication includes a downlink SFI related to the at least one symbol or the at least one time slot, and the downlink signal includes a PDSCH signal, semi-persistent downlink signal, or CSI-RS.

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

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

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

[0335] Aspect 67: The method according to any one of Aspects 36 to 66, 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, and the first component carrier is different from the second component carrier.

[0336] Aspect 68: The method according to any one of Aspects 36 to 67, wherein the control message further identifies one or more of the following: the frequency position of at least one uplink sub-band to be used for conveying an uplink message during the at least one symbol or the at least one time slot; at least one downlink sub-band to be used for conveying a downlink message during the at least one symbol or the at least one time slot; at least one guard band between the uplink sub-band and the downlink sub-band during the at least one symbol or the at least one time slot; and at least one flexible sub-band to be used for conveying the uplink message or the downlink message during the at least one symbol or the at least one time slot.

[0337] Aspect 69: The method according to Aspect 36, wherein the uplink resource or the downlink resource includes a periodic resource or a semi-persistent resource.

[0338] Aspect 70: The method according to any one of Aspects 36 to 69, wherein the network node includes a base station.

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

[0340] Aspect 72: An apparatus for wireless communication at a first network node, the apparatus comprising at least one component for performing the method according to any one of Aspects 1 to 35.

[0341] Aspect 73: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code when executed by a first network node causes the first network node to perform the method according to any one of Aspects 1 to 35.

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

[0343] Aspect 75: An apparatus for wireless communication at a network node, the apparatus comprising at least one component for performing the method according to any one of Aspects 36 to 70.

[0344] 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 the method according to any one of Aspects 36 to 70.

[0345] The methods described herein depict possible specific implementations, and the operations and steps may be rearranged or otherwise modified, and other specific implementations are possible. Additionally, aspects from two or more methods may be combined.

[0346] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to a variety of 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.

[0347] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0348] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, 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. The general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The 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).

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

[0350] 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. A non-transitory storage medium can 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 can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code 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, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disk can magnetically reproduce data, and disc can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0351] As used herein, the term "or" is inclusive unless restrictive language is used with respect to the listed alternatives. For example, a reference to "X is based on A or B" should be interpreted to include within its scope that X is based on A, X is based on B, and X is based on both A and B. In this regard, a reference to "X is based on A or B" means "at least one of A or B" or "one or more of A or B" because "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" should be interpreted to include within its scope that 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" means "at least one of A, B, or C" or "one or more of A, B, or C" because "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" should be interpreted to include within its scope that X is based on A and X is based on B, but does not include X is based on both A and B. Further, as used herein, the phrase "based on" should not 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.) should be interpreted as "at least based on A" unless stated otherwise specifically. Additionally, as used herein, the phrase "group" should be understood to include the possibility of a group having one member. That is, the phrase "group" should be understood in the same manner as "one or more" or "at least one".

[0352] The term "determine" encompasses a variety of actions and, thus, "determine" can include operations, calculations, processing, derivation, research, lookups (such as looking up via a table, database, or other data structure), ascertaining, and similar actions. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Further, "determine" can include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0353] In the figures, similar components or features may have the same reference numeral. Additionally, various components of the same type can be distinguished by adding a dash and a second numeral used to differentiate between similar components after the reference numeral. If only the first reference numeral is used in the specification, the description can apply to any of the similar components having the same first reference numeral, regardless of the second reference numeral or any subsequent reference numerals.

[0354] The description provided herein with reference to the accompanying drawings describes example configurations and does not represent all examples that can be implemented or are within the scope of the claims. The term "aspect" or "example" as used herein means "serving as an aspect, example, instance, or illustration" and not "preferred" or "advantageous over other aspects." The detailed description includes specific details for providing an understanding of the described techniques. However, the 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.

[0355] The present disclosure is provided to enable a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present 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, the first network node comprises: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receive a control message that identifies at least one symbol or at least one time slot to be used for sub-band full-duplex communication at a second network node; receive a first indication of uplink resources for use in uplink communication during the at least one symbol or the at least one time slot; receive a second indication of downlink resources for use in downlink communication during the at least one symbol or the at least one time slot; and communicate with the second network node during the at least one symbol or the at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

2. The first network node according to claim 1, wherein the uplink resources are located within at least one uplink sub-band or at least one flexible sub-band, and the downlink resources are located within at least one downlink sub-band or the at least one flexible sub-band.

3. The first network node according to claim 1, wherein the first indication is for transmitting an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is for receiving a synchronization signal block within at least one downlink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot.

4. The first network node according to claim 3, wherein the first indication includes an uplink time slot format indicator related to the at least one symbol or the at least one time slot.

5. The first network node according to claim 1, wherein the first indication is for transmitting a random access preamble within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is for receiving a downlink signal within at least one downlink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot.

6. The first network node according to claim 1, wherein the first indication is for transmitting an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is for monitoring a downlink control channel within at least one downlink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot.

7. The first network node according to claim 1, wherein the first indication is for transmitting an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is for receiving a downlink signal within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

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

9. The first network node according to claim 7, wherein the second indication includes a downlink time slot format indicator, a flexible time slot format indicator, a radio resource control configuration, or a dynamic grant related to the at least one symbol or the at least one time slot.

10. The first network node according to claim 7, wherein the uplink signal includes 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 according to claim 7, wherein the downlink signal includes a physical downlink control channel signal, a physical downlink shared channel signal, a channel state information reference signal, or a positioning reference signal.

12. The first network node according to claim 7, wherein the one or more prioritization rules include: in the absence of a beam failure recovery process being triggered, the reception of the downlink signal during the at least one symbol or the at least one time slot has priority over the transmission of the uplink signal, and in the presence of a beam failure recovery process being triggered, the transmission of the uplink signal during the at least one symbol or the at least one time slot has priority over the reception of the downlink signal.

13. The first network node according to claim 7, wherein the one or more prioritization rules include: prioritize the reception of the downlink signal or the transmission of the uplink signal based on the respective channel priorities associated with each of the downlink signal and the uplink signal.

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

15. The first network node according to 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, the network node comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: Output a control message that identifies at least one symbol or at least one time slot to be used for sub-band full-duplex communication at the network node; Output a first indication of uplink resources for use in uplink communication during the at least one symbol or the at least one time slot; Output a second indication of downlink resources for use in downlink communication during the at least one symbol or the at least one time slot; and Based on one or more prioritization rules, communicate during the at least one symbol or the at least one time slot according to one of the first indication or the second indication.

17. The network node according to claim 16, wherein the uplink resources are located within at least one uplink sub-band or at least one flexible sub-band, and the downlink resources are located within at least one downlink sub-band or the at least one flexible sub-band.

18. The network node according to claim 16, wherein the first indication is used to convey an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is used to convey a synchronization signal block within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

19. The network node according to claim 18, wherein the first indication includes an uplink time slot format indicator related to the at least one symbol or the at least one time slot.

20. The network node according to claim 16, wherein the first indication is used to convey a random access preamble within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is used to convey a downlink signal within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

21. The network node according to claim 16, wherein the first indication is used to convey an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is used to communicate using a downlink control channel within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

22. The network node according to claim 16, wherein the first indication is used to convey an uplink signal within at least one uplink sub-band or at least one flexible sub-band during the at least one symbol or the at least one time slot, and the second indication is used to convey a downlink signal within at least one downlink sub-band or the at least one flexible sub-band during the at least one symbol or the at least one time slot.

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

24. The network node according to claim 22, wherein the second indication includes a downlink time slot format indicator, a flexible time slot format indicator, a radio resource control configuration, or a dynamic grant related to the at least one symbol or the at least one time slot.

25. The network node according to claim 22, wherein the uplink signal includes a physical uplink control channel signal, a physical uplink shared channel signal, a sounding reference signal, or a random access preamble.

26. The network node according to claim 22, wherein the downlink signal includes a physical downlink control channel signal, a physical downlink shared channel signal, a channel state information reference signal, or a positioning reference signal.

27. The network node according to claim 22, wherein the one or more prioritization rules include: In the case where no beam failure recovery process is triggered, the conveyance of the downlink signal during the at least one symbol or the at least one time slot takes precedence over the conveyance of the uplink signal, and in the case where a beam failure recovery process is triggered, the conveyance of the uplink signal during the at least one symbol or the at least one time slot takes precedence over the conveyance of the downlink signal.

28. The network node according to claim 22, wherein the one or more prioritization rules include: Prioritize the conveyance of the downlink signal or the uplink signal based on the respective channel priorities associated with each of the downlink signal and the uplink signal.

29. A method for wireless communication at a first network node, the method comprises: Receiving a control message that identifies at least one symbol or at least one time slot to be used for sub-band full-duplex communication at a second network node; Receiving a first indication of uplink resources for use in uplink communication during the at least one symbol or the at least one time slot; Receiving a second indication of downlink resources for use in downlink communication during the at least one symbol or the at least one time slot; and Communicating with the second network node during the at least one symbol or the at least one time slot based on one or more prioritization rules according to one of the first indication or the second indication.

30. A method for wireless communication at a network node, the method comprises: Outputting a control message that identifies at least one symbol or at least one time slot to be used for sub-band full-duplex communication at the network node; Outputting a first indication of uplink resources for use in uplink communication during the at least one symbol or the at least one time slot; Output a second indication of the downlink resources for downlink communication during the at least one symbol or the at least one time slot; And Based on one or more prioritization rules, communicate during the at least one symbol or the at least one time slot according to one of the first indication or the second indication.

Images