Sub-band full-duplex aware user equipment

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can receive a first message identifying a duplex mode that allocates a first sub-band for uplink communications and a second sub-band for flexible communications during a sub-band full duplex (SBFD) time period. The UE can receive a second message identifying a modified duplex mode that allocates a subset of the SBFD time period for uplink communications or for downlink communications. The UE can perform uplink communications or downlink communications during one or more SBFD time periods of the subset of the SBFD time period in accordance with the modified duplex mode, where the uplink communications or the downlink communications are performed in one or both of the first sub-band and the second sub-band.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Patent Application No. 18 / 417,782, entitled “SUBBAND ​​FULL-DUPLEX AWARE USER EQUIPMENT”, filed January 19, 2024, by JABI et al., which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following text relates to wireless communications, including sub-band full-duplex sensing user equipment. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A 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 can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting Subband Full-Duplex (SBFD) aware user equipment (UE). For example, the described technology enables the UE to receive or otherwise obtain a first message indicating a duplex mode of SBFD time and frequency configuration. The duplex mode may allocate a first subband for uplink communication and a second subband for flexible communication (e.g., uplink or downlink communication) during an SBFD time period (e.g., during an SBFD symbol or time slot). The UE may receive or otherwise obtain a second message (e.g., a UE-specific message) identifying a modified duplex mode. The modified duplex mode may allocate one, some, or all (e.g., a subset) of SBFD time periods for uplink or downlink communication. The UE may perform uplink or downlink communication in the first subband, the second subband, or both subbands according to the modified duplex mode. That is, the UE may overwrite uplink or flexible communication from an initially configured duplex mode according to the modified duplex mode. Therefore, the UE can transmit or receive radio signals in each SBFD time period (e.g., time slot) according to the modified duplex mode.

[0006] Additionally or alternatively, the UE may receive or otherwise obtain a first message identifying the duplex mode. In this example, the duplex mode may allocate a first subband for uplink communication and a second subband for downlink communication during an SBFD time period. The UE may receive or otherwise obtain a second message (e.g., a UE-specific message) indicating or otherwise identifying a modified duplex mode. The modified duplex mode may allocate a subset of SBFD time periods for uplink communication or downlink communication. Therefore, the UE may perform uplink communication or downlink communication according to the modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods. The uplink communication or downlink communication may be performed in one or both of the first and second subbands.

[0007] A method for wireless communication by a UE is described. The method may include: receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and performing uplink communication or downlink communication according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0008] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be individually or jointly operable to execute code to cause the UE to: receive a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; receive a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0009] Another UE for wireless communication is described. The UE may include: components for receiving a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and components for performing uplink communication or downlink communication according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; receive a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or for downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0011] The methods described herein, some examples of user equipment (UE) and non-transitory computer-readable media may also include operations, features, components or instructions for performing downlink communication in a second subband during a subset of SBFD time periods according to a modified duplex mode.

[0012] The methods described herein, some examples of user equipment (UE) and non-transitory computer-readable media may also include operations, features, components or instructions for performing a second uplink communication in a second subband during a subset of the SBFD time period according to a modified duplex mode.

[0013] The methods described herein, some examples of user equipment (UE) and non-transitory computer-readable media may also include operations, features, components or instructions for performing downlink communication in a first subband and a second subband during a subset of SBFD time periods according to a modified duplex mode.

[0014] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, performing downlink communication may include operations, features, components, or instructions for combining a first subband and a second subband to form a downlink frequency band during a subset of SBFD time periods.

[0015] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, performing uplink communication may include operations, features, components, or instructions for combining a first subband and a second subband to form an uplink frequency band during a subset of SBFD time periods.

[0016] The methods described herein, some examples of user equipment (UE) and non-transitory computer-readable media may also include operations, features, components or instructions for performing uplink communication in a first subband and a second subband during a subset of SBFD time periods according to a modified duplex mode.

[0017] The methods described herein, some examples of user equipment (UE) and non-transitory computer-readable media may also include operations, features, components or instructions for performing uplink communication in a first subband during a subset of SBFD time periods according to a modified duplex mode and maintaining a second subband for flexible communication.

[0018] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing downlink communications scheduled in a second subband during a subset of SBFD time periods according to a modified duplex mode; and discarding uplink communications scheduled in a first subband during a subset of SBFD time periods according to a modified duplex mode.

[0019] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing uplink communications scheduled in a first subband during a subset of SBFD time periods according to a modified duplex mode; and discarding downlink communications scheduled in a second subband during a subset of SBFD time periods according to a modified duplex mode.

[0020] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0021] A method for wireless communication by a UE is described. The method may include: receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during a SBFD time period; receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and performing uplink communication or downlink communication according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0022] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be individually or jointly operable to execute code to cause the UE to: receive a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during a SBFD time period; receive a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0023] Another UE for wireless communication is described. The UE may include: components for receiving a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for downlink communication during a SBFD time period; components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and components for performing uplink communication or downlink communication according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0024] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during a SBFD time period; receive a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0025] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing downlink communications scheduled in a second subband during a subset of SBFD time periods according to a modified duplex mode; and discarding uplink communications scheduled in a first subband during a subset of SBFD time periods according to a modified duplex mode.

[0026] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing uplink communications scheduled in a first subband during a subset of SBFD time periods according to a modified duplex mode; and discarding downlink communications scheduled in a second subband during a subset of SBFD time periods according to a modified duplex mode.

[0027] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing flexible communication during a subset of SBFD time periods according to a modified duplex mode, wherein the performance includes performing uplink communication in a first subband or performing downlink communication in a second subband.

[0028] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing downlink communications scheduled in a first subband and a second subband during a subset of SBFD time periods according to a modified duplex mode; and discarding uplink communications scheduled in the first subband during a subset of SBFD time periods according to a modified duplex mode.

[0029] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing uplink communications scheduled in a first subband and a second subband during a subset of SBFD time periods according to a modified duplex mode; and discarding downlink communications scheduled in a second subband during a subset of SBFD time periods according to a modified duplex mode.

[0030] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing flexible communication during a subset of SBFD time periods according to a modified duplex mode, wherein the performance includes performing uplink communication in a first subband or performing downlink communication in a second subband.

[0031] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0032] A method for wireless communication by a network entity is described. The method may include: outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; outputting a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and performing uplink communication or downlink communication with the UE according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0033] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be individually or jointly operable to execute code to cause the network entity to: output a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; output a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication with the UE according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0034] Another network entity for wireless communication is described. This network entity may include: components for outputting a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for flexible communication during an SBFD time period; components for outputting a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and components for performing uplink or downlink communication with the UE according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0035] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; output a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication with the UE according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0036] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing downlink communication with the UE in a second subband during a subset of the SBFD time period according to a modified duplex mode.

[0037] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing a second uplink communication with the UE in a second subband during a subset of the SBFD time period, according to a modified duplex mode.

[0038] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing downlink communication with the UE in a first subband and a second subband during a subset of the SBFD time period, according to a modified duplex mode.

[0039] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, performing downlink communication may include operations, features, components, or instructions for combining a first subband and a second subband to form a downlink frequency band during a subset of SBFD time periods.

[0040] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing uplink communication with the UE in a first subband and a second subband during a subset of SBFD time periods, according to a modified duplex mode.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, performing uplink communication may include operations, features, components, or instructions for combining a first subband and a second subband to form an uplink frequency band during a subset of SBFD time periods.

[0042] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing uplink communication with the UE in a first subband during a subset of SBFD time periods according to a modified duplex mode and maintaining a second subband for flexible communication.

[0043] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: performing downlink communication scheduled with the UE in a second subband during a subset of the SBFD time period according to a modified duplex mode; and discarding uplink communication scheduled with the UE in a first subband during a subset of the SBFD time period according to a modified duplex mode.

[0044] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: performing uplink communication scheduled with the UE in a first subband during a subset of the SBFD time period according to a modified duplex mode; and discarding downlink communication scheduled with the UE in a second subband during a subset of the SBFD time period according to a modified duplex mode.

[0045] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0046] A method for wireless communication by a network entity is described. The method may include: outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during a SBFD time period; outputting a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and performing uplink communication or downlink communication with the UE according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0047] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be individually or jointly operable to execute code to cause the network entity to: output a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during a SBFD time period; output a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication with the UE according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0048] Another network entity for wireless communication is described. This network entity may include: components for outputting a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for downlink communication during an SBFD time period; components for outputting a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and components for performing uplink or downlink communication with the UE according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0049] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during a SBFD time period; output a second message to a UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication; and, during one or more SBFD time periods within the subset of SBFD time periods, perform uplink communication or downlink communication with the UE according to the modified duplex mode, wherein the uplink communication or downlink communication is performed in one or both of the first and second subbands.

[0050] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: performing downlink communication with the UE scheduled in a second subband during a subset of the SBFD time period according to a modified duplex mode; and discarding uplink communication scheduled in a first subband during a subset of the SBFD time period according to a modified duplex mode.

[0051] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: performing uplink communication with the UE scheduled in a first subband during a subset of SBFD time periods according to a modified duplex mode; and discarding downlink communication scheduled in a second subband during a subset of SBFD time periods according to a modified duplex mode.

[0052] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing flexible communication with the UE during a subset of SBFD time periods according to a modified duplex mode, wherein the performance includes performing uplink communication in a first subband or performing downlink communication in a second subband.

[0053] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: performing downlink communications with the UE scheduled in a first subband and a second subband during a subset of the SBFD time period according to a modified duplex mode; and discarding uplink communications scheduled in the first subband during a subset of the SBFD time period according to a modified duplex mode.

[0054] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: performing uplink communications with the UE scheduled in a first subband and a second subband during a subset of the SBFD time period according to a modified duplex mode; and discarding downlink communications scheduled in the second subband during a subset of the SBFD time period according to a modified duplex mode.

[0055] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing flexible communication with the UE during a subset of SBFD time periods according to a modified duplex mode, wherein the performance includes performing uplink communication in a first subband or performing downlink communication in a second subband.

[0056] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message. Attached Figure Description

[0057] Figure 1 An example of a wireless communication system supporting sub-band full-duplex (SBFD) aware user equipment (UE) according to one or more aspects of this disclosure is shown.

[0058] Figure 2 An example of a wireless communication system supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown.

[0059] Figures 3A to 3D An example of a duplex mode supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown.

[0060] Figures 4A to 4BAn example of a duplex mode supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown.

[0061] Figure 5 and Figure 6 A block diagram of an apparatus supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown.

[0062] Figure 7 A block diagram of a communication manager supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown.

[0063] Figure 8 A diagram of a system including a device supporting SBFD-aware UE is shown according to one or more aspects of this disclosure.

[0064] Figure 9 and Figure 10 A block diagram of an apparatus supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown.

[0065] Figure 11 A block diagram of a communication manager supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown.

[0066] Figure 12 A diagram of a system including a device supporting SBFD-aware UE is shown according to one or more aspects of this disclosure.

[0067] Figures 13 to 16 A flowchart illustrating a method for supporting SBFD-aware UE according to one or more aspects of this disclosure is shown. Detailed Implementation

[0068] Wireless networks can utilize various duplex schemes to improve communication between user equipment (UE) and network entities. The network can provide a Time Division Duplex (TDD) mode to the UE, which allocates available frequency resources as uplink, downlink, or flexible resources according to the TDD mode. The network can support full-duplex network entities and UEs capable of simultaneously transmitting and receiving radio signals. The network can support full-duplex communication in fully or partially overlapping frequency bands (e.g., in-band full-duplex (IBFD)) or in different subbands (where the frequency band is divided into uplink subbands and downlink subbands (e.g., subband full-duplex (SBFD))). SBFD-aware UEs can receive both a TDD mode indication and (e.g., when declaring support for SBFD) dedicated signaling for the SBFD duplex mode within each subband. However, such networks may not provide a mechanism for UEs to cover downlink or uplink subbands configured according to the TDD mode.

[0069] Therefore, the described technology provides a UE to receive or otherwise obtain a first message indicating a duplex mode of SBFD time and frequency configuration. The duplex mode may allocate a first subband for uplink communication and a second subband for flexible communication (e.g., uplink or downlink communication) during an SBFD time period (e.g., during an SBFD symbol or time slot). The UE may receive or otherwise obtain a second message (e.g., a UE-specific message) identifying a modified duplex mode. The modified duplex mode may allocate one, some, or all (e.g., a subset) of the SBFD time periods for uplink or downlink communication. The UE may perform uplink or downlink communication in the first subband, the second subband, or both subbands according to the modified duplex mode. That is, the UE may overwrite the uplink or flexible communication from the initially configured duplex mode according to the modified duplex mode. Therefore, the UE may transmit or receive radio signals in each SBFD time period (e.g., time slot) according to the modified duplex mode.

[0070] Additionally or alternatively, the UE may receive or otherwise obtain a first message identifying the duplex mode. In this example, the duplex mode may allocate a first subband for uplink communication and a second subband for downlink communication during an SBFD time period. The UE may receive or otherwise obtain a second message (e.g., a UE-specific message) indicating or otherwise identifying a modified duplex mode. The modified duplex mode may allocate a subset of SBFD time periods for uplink communication or downlink communication. Therefore, the UE may perform uplink communication or downlink communication according to the modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods. The uplink communication or downlink communication may be performed in one or both of the first and second subbands.

[0071] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to SBFD-sensing the UE, and are further described with reference to these diagrams.

[0072] Figure 1 An example of a wireless communication system 100 supporting SBFD-aware UEs according to one or more aspects of this disclosure is shown. 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 Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0073] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0074] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0075] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0076] In some examples, network entity 105 may communicate with core network 130, communicate 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 entities 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 links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to 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 can communicate with core network 130 via communication link 155.

[0077] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution 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, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0078] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across 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, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed 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 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0079] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0080] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can 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 partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with 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 node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0081] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0082] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0083] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

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

[0085] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0086] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0087] UE 115 and network entity 105 can 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" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0088] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0089] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to 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 and uplink communication (e.g., in TDD mode).

[0090] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 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., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or 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., subband, BWP) or all of the carrier bandwidth.

[0091] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier 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 high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0092] It can support one or more sets of parameters for a carrier, and the parameter sets may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured to utilize multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0093] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with 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).

[0094] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a 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 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, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0096] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on 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 concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0097] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0098] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0099] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0100] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, 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.

[0101] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0102] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0103] Some UE 115s can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at reduced peak rates. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

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

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

[0106] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0107] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0108] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0109] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0110] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0111] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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 an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0112] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), 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.

[0113] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

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

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

[0116] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding 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 to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0117] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver 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).

[0118] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0119] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0120] UE 115 may receive a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. UE 115 may receive a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. UE 115 may perform uplink or downlink communication according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0121] UE 115 may receive a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during an SBFD time period. UE 115 may also receive a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink or downlink communication. UE 115 may perform uplink or downlink communication according to the modified duplex mode during one or more SBFD time periods within the subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0122] Network entity 105 may output a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. Network entity 105 may output a second message to UE 115 identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink or downlink communication. Network entity 105 may perform uplink or downlink communication with UE 115 during one or more SBFD time periods within the subset of SBFD time periods, based on the modified duplex mode, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0123] Network entity 105 may output a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during SBFD time periods. Network entity 105 may output a second message to UE 115 identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink or downlink communication. Network entity 105 may perform uplink or downlink communication with UE 115 during one or more SBFD time periods within the subset of SBFD time periods, based on the modified duplex mode, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0124] Figure 2 An example of a wireless communication system 200 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a UE 205 and a network entity 210, which may be examples of the corresponding devices described herein.

[0125] The wireless communication system 200 can support full-duplex (FD) operation, such as using SBFD time periods (e.g., symbols or time slots configured for SBFD-based communication) having one or more uplink subbands, one or more downlink subbands, and optionally one or more guard bands or gap bands between adjacent uplink and downlink subbands. SBFD time periods enable simultaneous transmission and reception on different frequency resources (e.g., downlink resources and uplink resources are separated in the frequency domain). Other examples of FD operation include using in-band full-duplex (IBFD) time periods, where downlink and uplink communication share the same IBFD time and frequency resources (e.g., fully or at least partially overlapping). Therefore, at least to some extent or in some examples, communication during an IBFD time period involves simultaneous transmission and reception using the same frequency resources.

[0126] Therefore, the FD time slot structure can also be referred to as a "D+U" time slot to indicate the execution of both downlink and uplink communication. The FD time slot structure is defined as the simultaneous occurrence of both downlink and uplink transmissions in overlapping frequency bands (e.g., IBFD) or adjacent bands (e.g., adjacent sub-bands within the SBFD time slot). In a given symbol of an FD time slot, a half-duplex (HD) UE can perform uplink transmissions in the uplink (sub)band or receive downlink transmissions in the downlink (sub)band. In a given symbol of an FD time slot, an FD UE can perform uplink transmissions in either the uplink band (e.g., IBFD) or the uplink sub-band (e.g., SBFD), and can also receive downlink transmissions in either the downlink band (e.g., IBFD) or the downlink sub-band (e.g., SBFD).

[0127] The wireless communication system 200 can also support TDD operation, where frequency bands are allocated at the symbol or time slot level for uplink or downlink communication. Figure 2 In the non-limiting example shown, this may include: time period 220 being configured as a TDD time period to be scheduled or otherwise allocated to the downlink (DL). This may include: time periods 225, 230, and 235 being configured as SBFD time periods. SBFD time periods may include each SBFD subband configured for flexible (FL) communication (e.g., uplink or downlink), for uplink (UL) communication, or for downlink communication. Time period 240 may be configured as a TDD time period to be scheduled or otherwise allocated to uplink communication.

[0128] Downlink communication performed during time period 220 and uplink communication performed during time period 240 may use frequency band 245 (e.g., the UE's BWP). That is, frequency band 245 may be configured or otherwise used as the downlink frequency band during time period 220 and the uplink frequency band during time period 240. Uplink communication performed during time periods 225, 230, and 235 may be performed using subband 255 (e.g., the first subband in this example), which is scheduled or otherwise allocated for uplink communication. Flexible communication (e.g., downlink or uplink) performed during time periods 225, 230, and 235 may be performed in one or both of subbands 250 and 260 (e.g., each of which may be considered the second subband in this example).

[0129] Networks can typically provide specific uplink-downlink transmission modes to UEs using various Information Elements (IEs) (such as RRC IEs). For example, the TDD-UL-DL-ConfigCommon IE can be a cell-specific configuration that configures a specific TDD mode, which will remain valid unless it is reconfigured by subsequent RRC signaling. Another example could be the TDD-UL-DL-ConfigDedicated IE, which can be a UE-specific configuration that can only be reconfigured with flexible slots and symbols provided in the TDD-UL-DL-ConfigCommon IE.

[0130] Another approach may include the Slot Format Indicator (SFI) included in DCI format 2_0. This approach can use group signaling, where each UE uses the PositioninDCI IE specified in the SlotFormatIndicator IE to extract a different SFI. Each slot format combination can be generated using a normalized slot format sequence. The SlotFormatIndicator IE can be (pre)configured using RRC signaling. The SFI can be used to dynamically reconfigure only the remaining flexible symbols after TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated configurations. The UE can monitor PDCCH for uplink and downlink resource allocation during any flexible time period that has been configured using TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated, but not during flexible time periods configured using the DCI method (because these time periods are considered blocked).

[0131] Therefore, the TDD-UL-DL-ConfigDedicated IE can be used to signal or otherwise determine UE-specific uplink / downlink TDD configurations, and can be configured with symbols and time slots defined for flexible communication within the TDD-UL-DL-ConfigCommon IE. However, the TDD-UL-DL-ConfigDedicated IE may not be used to change symbols or time slots that have already been configured as uplink / downlink time periods or SBFD time periods.

[0132] However, these approaches may be inefficient or inadequate in some respects. For example, for SBFD symbols configured in flexible time slots, these techniques may not define how the UE is expected to respond when it receives a dedicated TDD-UL-DL mode for the flexible symbol / time slot. For example, when the FL time period is indicated for downlink, these approaches may not define the frequency resources (e.g., band 245 or a specific subband) to be used for downlink communication. Furthermore, for SBFD symbols configured in downlink time slots, these techniques may not define how the UE is expected to respond when a dedicated TDD-UL-DL mode is available to indicate the UE's traffic direction (e.g., uplink or downlink) within the SBFD symbol.

[0133] Therefore, aspects of the described technology provide a response to an SBFD-aware UE (e.g., UE 205 in this example) when configured with a dedicated TDD mode. These aspects relax restrictions on SBFD time periods (e.g., symbols or time slots associated with SBFD-based wireless communication). In some aspects, when the UE is configured with TDD-UL-DL-ConfigDedicated signaling, the described technology can provide UE behavior within the SBFD time period indicated by the common mode configuration signaling.

[0134] For example, network entity 210 may send or otherwise provide a first message to UE 205 for output, the first message carrying or transmitting information identifying the duplex mode. The duplex mode may allocate a first subband (e.g., subband 255 in this example) for uplink communication and a second subband (e.g., either or both of subband 250 and subband 260 in this example) for flexible communication (e.g., uplink or downlink) during the SBFD time period. The first message in this example may correspond to a public message or a broadcast message, or it may be a UE-specific message. For example, network entity 210 may broadcast a TDD-UL-DL-ConfigCommon IE to all UEs or a group of UEs. Figure 2In the non-limiting example shown, the duplex mode can be DFFFU, which can correspond to the TDD duplex mode during time periods 220 and 240, and the SBFD duplex mode during time periods 225, 230, and 235. That is, the TDD duplex mode can indicate that time period 220 is configured for downlink (D) communication and time period 240 is configured for uplink (U) communication, and the SBFD duplex mode can indicate that time periods 225, 230, and 235 are configured for flexible (F) communication.

[0135] UE 205 can transition to an RRC connected state and declare its SBFD-aware capability. For example, UE 205 can perform an access procedure with network entity 210 to establish an RRC connection. UE 205 can send or otherwise provide a UE capability or UE assistance information message to network entity 210, indicating that UE 205 supports SBFD-based communication, where frequency band 245 has been divided into multiple subbands, and in some examples, a gap band is configured between the uplink and downlink subbands.

[0136] Network entity 210 may send or otherwise provide UE 205 with an RRC message indicating the time and frequency location of SBFD for output. For example, the RRC message may indicate the uplink subband time location 01110, which may correspond to DXXXU, where X corresponds to the uplink subband being active during time periods 225, 230, and 235, or otherwise available for SBFD-based uplink communication.

[0137] Network entity 210 may send or otherwise provide a second message to UE 205, which indicates or otherwise identifies a modified duplex mode. The modified duplex mode may allocate a subset of SBFD time periods for uplink or downlink communication (e.g., one, some, or all of the SBFD time periods). In this example, the second message may be a UE-specific message. For example, network entity 210 may configure UE 205 with a TDD-UL-DL-ConfigDedicated IE via RRC signaling, which carries or otherwise transmits an indication of the modified duplex mode.

[0138] Therefore, the described technology can provide SBFD-aware UE (e.g., UE 205 in this example) response when configured with a dedicated TDD mode that indicates flexible resources as uplink or downlink resources. For example, UE 205 may perform uplink or downlink communication during one or more SBFD time periods depending on the modified duplex mode. In some aspects, this may include: UE 205 performing uplink or downlink communication in one or both of a first subband (e.g., subband 255) and a second subband (e.g., one or both of subband 250 and subband 260).

[0139] In some examples, UE 205 may perform downlink or uplink communication in a second subband. UE 205 may combine the first and second subbands and perform downlink or uplink communication in the combined subband (e.g., in each of subbands 250, 255, and 260). In some examples, UE 205 may maintain a second subband for flexible communication. In other examples, UE 205 may use a dedicated TDD duplex mode received in a second message to determine its communication direction during the SBFD period (e.g., uplink-only or downlink-only communication). For example, UE 205 may perform downlink communication in the second subband during the SBFD period and discard uplink communication scheduled in the first subband. In another example, UE 205 may perform uplink communication in the first subband during the SBFD period and discard downlink communication scheduled in the second subband.

[0140] Therefore, the described techniques provide various examples of UE behavior or response strategies when the UE is SBFD-aware and configured with a dedicated TDD mode. Network entity 210 can use the described techniques to synchronize with UE behavior during the SBFD period (e.g., to manage uplink communication from the UE and downlink communication to the UE).

[0141] Figures 3A to 3D An example of a duplex mode 300 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. The duplex mode 300 may implement aspects of wireless communication system 100 or wireless communication system 200. The aspects of the duplex mode 300 may be implemented at or by a UE or network entity, which may be an example of the corresponding device described herein. Figure 3A 300-a duplex mode Figure 3B 300-b duplex mode Figure 3C 300-c duplex mode and Figure 3D The duplex mode 300-d illustrates a non-limiting example of SBFD-aware UE behavior when configured with a dedicated TDD mode.

[0142] For example, the UE may receive or otherwise obtain a first message from a network entity. The first message may carry or otherwise convey an indication of a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during the SBFD time period. In the non-limiting example shown in Figure 3, the first subband may correspond to subband 335, and the second subband may correspond to one or both of subbands 330 and 340. Subbands 330, 335, and 340 typically correspond to the UE's available bandwidth (e.g., BWP).

[0143] SBFD time periods may correspond to symbols, micro-slots, transmission opportunities (TxOPs), slots, or other time periods utilized within the wireless network. In this example, the SBFD time periods identified in the first message may include time periods 310, 315, and 320. Time period 305 may be a TDD time period allocated for downlink communication within the available bandwidth, and time period 325 may be a TDD time period allocated for uplink communication within the available bandwidth.

[0144] In some respects, the first message can be a TDD-UL-DL-ConfigCommonIE indicated to the UE via RRC signaling. In the non-limiting example shown in Figure 3, the TDD-UL-DL-ConfigCommonIE can indicate the TDD mode of DFFFU. The first message can be a broadcast message or a common message sent to multiple UEs. The first message can be a UE-specific message addressed to a particular UE. The UE can establish an RRC connection with the network and indicate its support for SBFD-based wireless communication, such as by sending an indication of SBFD support in a UE capability message.

[0145] A network entity may transmit an RRC message to the UE, which indicates the time / frequency resources of the uplink subband to be used for uplink communication in the uplink subband (e.g., in the first subband). For example, the RRC message may indicate that the uplink subband time location resource corresponds to 01110, and its indicated time period is configured as DXXXU, where X corresponds to the time period during which the uplink subband (e.g., subband 335 in this example) is active or otherwise available for uplink communication.

[0146] The UE may receive a second message from a network entity indicating or otherwise identifying a modified duplex mode. The modified duplex mode may be configured or otherwise allocated a subset of SBFD time periods for uplink or downlink communication. That is, the second message may define one, some, or all of the SBFD time periods as being used for uplink or downlink communication. In the non-limiting example shown in Figure 3, the subset of SBFD time periods may include one or more of time periods 310, 315, and 320. The second message may be received in a UE-specific message, such as in RRC signaling. For example, the second message may be a TDD-UL-DL-ConfigDedicated IE carried in RRC signaling addressed to the UE.

[0147] Therefore, the UE and network entities can perform uplink or downlink communication during one, some, or all of the SBFD time periods, depending on the modified duplex mode. This may include the UE and network entities performing uplink or downlink communication in either or both of the first and second subbands. Duplex mode 300 illustrates a non-limiting example of a UE response to a modified duplex mode according to the techniques described herein.

[0148] First go to Figure 3A The duplex mode 300-a may include a dedicated TDD mode that designates flexible resources as uplink or downlink resources. Specifically, duplex mode 300-a illustrates a non-limiting example in which the UE responds to a dedicated TDD mode that designates flexible resources within a flexible time period (e.g., an SBFD time period) for either uplink or downlink communication. In this example, the dedicated TDD mode is not used to cover uplink communication scheduled in the first subband (e.g., in subband 335).

[0149] The modified duplex mode indicated or otherwise identified in the second message may indicate the DUU mode used for the SBFD time period. That is, the modified duplex mode may indicate that time period 310 is used for downlink communication in the second subband, and time periods 315 and 320 are used for uplink communication in the second subband. Similarly, the second subband in this example may include one or both of subbands 330 and 340.

[0150] Therefore, the UE can perform (e.g., receive) downlink communication in the second subband during the SBFD time period (e.g., during time period 310 in this example) according to the modified duplex mode, or the UE can perform (e.g., transmit) uplink communication in the first subband during the SBFD time period. The UE can also perform (e.g., transmit) uplink communication in the second subband during the SBFD time period (e.g., during time periods 315 and 320 in this example) according to the modified duplex mode. In this example, the modified duplex mode does not cover the uplink subband (e.g., subband 335), which supports maintaining the SBFD time period structure. Therefore, duplex mode 300-a illustrates a non-limiting example of TDD-UL-DL-ConfigDedicated (e.g., the second message) being used for signaling or otherwise determining uplink / downlink communication for the flexible subband without covering the uplink subband. In some examples, guard bands (e.g., gaps) may be used for uplink resources during time periods 315 and 320. In this example, the UE can rely on network entity scheduling and conflict resolution techniques to determine whether the UE is transmitting or receiving during the SBFD period.

[0151] Next, turn to Figure 3B The duplex mode 300-b may include: a dedicated TDD mode indicating the SBFD time period as being used for uplink communication or downlink communication. That is, the TDD-UL-DL-ConfigDedicated IE indicated in the second message may be used to override the SBFD time period back to the TDD time period. This may include: combining SBFD subbands (e.g., subband 330, subband 335, and subband 340) into a frequency band (e.g., the UE's BWP) during the TDD time period.

[0152] More specifically, in Figure 3B In the non-limiting example shown, the TDD-UL-DL-ConfigDedicated IE indicated in the second message can signal the DUU duplex mode for the SBFD time period. This indication can be used to cover the first subband from uplink communication and the second subband from flexible communication to either uplink or downlink communication.

[0153] Therefore, the UE can perform downlink communication in the first and second subbands during the SBFD time period. In this example, the SBFD time period for downlink communication may include time period 310. Downlink communication can be performed by combining all subbands 330, 335, and 340 into a downlink frequency band. Similarly, the UE can perform uplink communication in the first and second subbands during the SBFD time period. In this example, the SBFD time period for uplink communication may include time period 315 and time period 320. Uplink communication can be performed by combining all subbands 330, 335, and 340 into an uplink frequency band. According to the first message (e.g., TDD-UL-DL-ConfigCommon IE carried in RRC signaling), time period 305 is configured for downlink communication, and time period 325 is configured for uplink communication.

[0154] Next, turn to Figure 3C The duplex mode 300-c illustrates another aspect of a dedicated TDD mode where an SBFD time period is indicated as a TDD time period. However, in this example, one or more SBFD time periods within the SBFD time periods may be maintained as SBFD time periods. More specifically, in this example, the modified duplex mode indicated in the second message may be DXU. The modified duplex mode may include: time period 310 for performing downlink communication by combining the first subband and the second subband into a downlink frequency band. The modified duplex mode may include: time period 320 for performing uplink communication by combining the first subband and the second subband into an uplink frequency band.

[0155] However, the modified duplex mode in this example may indicate that time period 325 will be maintained as an SBFD time period (e.g., as a flexible resource). Therefore, the UE may perform uplink communication in the first subband (e.g., in subband 335) and maintain a second subband (e.g., one or both of subband 330 and subband 340) for flexible communication during time period 325.

[0156] Go to Figure 3D The duplex mode 300-d may include: a dedicated TDD mode indicated in the second message used to determine the UE's communication direction. That is, the TDD-UL-DL-ConfigDedicated IE indicated in the second message may not cover the SBFD time period configured by a common mode configuration (e.g., TDD-UL-DL-ConfigCommon). Instead, the modified duplex mode can be used to determine the direction of transmission or reception within the SBFD time period.

[0157] More specifically, in this example, the modified duplex mode indicated in the second message may indicate a DUU. Therefore, time period 310 can still be an SBFD time period, but it is used for downlink communication. This could include: the UE performing downlink communication in the second subband during time period 310 according to the modified duplex mode, while discarding uplink communication scheduled in the first subband. Therefore, if the UE receives a DCI scheduling uplink communication during time period 310, the UE may ignore the permission and not perform uplink transmission according to the modified duplex mode (e.g., it will not transmit PUCCH / PUSCH / SRS / PRACH).

[0158] Similarly, time periods 315 and 320 can still be SBFD time periods, but used for uplink communication. This could include the UE performing uplink communication in the first subband during time periods 315 and 320, while discarding downlink communication scheduled in the second subband. Therefore, if the UE has downlink communication (e.g., CSI-RS) scheduled during time period 315 or 320, the UE can ignore the reception of downlink communication (e.g., not receiving PDSCH / CSI-RS) depending on the modified duplex mode.

[0159] Figures 4A to 4B An example of a duplex mode 400 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. The duplex mode 400 may implement aspects of wireless communication system 100 or wireless communication system 200, or aspects of duplex mode 300. The aspects of duplex mode 400 may be implemented at or by a UE or network entity, which may be an example of the corresponding device described herein. Figure 4A The duplex mode 400-a and Figure 4B The duplex mode 400-b illustrates a non-limiting example of SBFD-aware UE behavior when configured with a dedicated TDD mode.

[0160] For example, the UE may receive or otherwise obtain a first message from a network entity. The first message may carry or otherwise convey an indication of a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during the SBFD time period. In the non-limiting example shown in Figure 4, the first subband may correspond to subband 435, and the second subband may correspond to one or both of subbands 430 and 440. Subbands 430, 435, and 440 typically correspond to the UE's available bandwidth (e.g., BWP).

[0161] SBFD time periods may correspond to symbols, micro-slots, transmission opportunities (TxOPs), slots, or other time periods utilized within the wireless network. In this example, the SBFD time periods identified in the first message may include time periods 410, 415, and 420. Time period 405 may be a TDD time period allocated for downlink communication within the available bandwidth, and time period 425 may be a TDD time period allocated for uplink communication within the available bandwidth.

[0162] In some respects, the first message can be a TDD-UL-DL-ConfigCommonIE indicated to the UE via RRC signaling. In the non-limiting example shown in Figure 4, the TDD-UL-DL-ConfigCommonIE can indicate the TDD mode DDDDU. The first message can be a broadcast message or a common message sent to multiple UEs. The first message can be a UE-specific message addressed to a particular UE. The UE can establish an RRC connection with the network and indicate its support for SBFD-based wireless communication, such as by sending an indication of SBFD support in a UE capability message.

[0163] A network entity may transmit an RRC message to the UE, which indicates the time / frequency resources of the uplink subband to be used for uplink communication in the uplink subband (e.g., in the first subband). For example, the RRC message may indicate that the uplink subband time location resource corresponds to 01110, and its indicated time period is configured as DXXXU, where X corresponds to the time period of the uplink subband (e.g., subband 335 in this example) that is active or otherwise available for uplink communication during its period, as well as the time periods of the second subband (e.g., subbands 430 and 440 in this example) and the flexible subband.

[0164] The UE may receive a second message from a network entity indicating or otherwise identifying a modified duplex mode. The modified duplex mode may be configured or otherwise allocated a subset of SBFD time periods for uplink communication or downlink communication. That is, the second message may define one, some, or all of the SBFD time periods as being used for uplink or downlink communication. In the non-limiting example shown in Figure 4, the subset of SBFD time periods may include one or more of time periods 410, 415, and 420. The second message may be received in a UE-specific message, such as in RRC signaling. For example, the second message may be a TDD-UL-DL-ConfigDedicated IE carried in RRC signaling addressed to the UE. The modified duplex mode illustrated in Figure 4 may include a DUX duplex mode, where time period 410 is configured for downlink communication (D), time period 415 is configured for uplink communication (U), and time period 420 is configured for flexible communication (X).

[0165] Therefore, the UE and network entities can perform uplink or downlink communication during one, some, or all of the SBFD time periods, depending on the modified duplex mode. This may include the UE and network entities performing uplink or downlink communication in either or both of the first and second subbands. Duplex mode 400 illustrates a non-limiting example of a UE response to a modified duplex mode according to the techniques described herein.

[0166] First go to Figure 4A The modified duplex mode 400-a may include: a dedicated TDD-UL-DL-ConfigDedicated signaling indicated in the second message used to determine the UE communication direction (e.g., uplink or downlink communication) during the SBFD time period. For example, if the modified duplex mode indicates downlink communication, the UE receives downlink communication in the downlink subband (e.g., in the second subband) while discarding uplink communication scheduled in the uplink subband (e.g., in the first subband). If the modified duplex mode indicates uplink communication, the UE transmits uplink communication in the uplink subband while discarding downlink communication scheduled in the downlink subband. If the modified duplex mode indicates flexible communication, the UE may perform uplink communication in the uplink subband or downlink communication in the downlink subband.

[0167] exist Figure 4AIn the non-limiting example illustrated, this may include: the UE performing downlink communication in a second subband (e.g., in one or both of subbands 430 and 440) during time period 410, depending on the modified duplex mode. The UE may perform uplink communication in a first subband (e.g., in subband 435) during time period 415, depending on the modified duplex mode. During time period 420, the UE may perform uplink communication in the first subband or downlink communication in the second subband.

[0168] Next, turn to Figure 4B The modified duplex mode 400-b may include: a dedicated TDD-UL-DL-ConfigDedicated signaling indicated in the second message used to cover the SBFD time period for downlink communication or uplink communication. For example, if the modified duplex mode indicates downlink communication, the UE receives downlink communication in both the downlink subband (e.g., in the second subband) and the uplink subband (e.g., the first subband), while discarding uplink communication scheduled in the uplink subband. If the modified duplex mode indicates uplink communication, the UE transmits uplink communication in both the uplink and downlink subbands, while discarding downlink communication scheduled in the downlink subband. If the modified duplex mode indicates flexible communication, the UE may perform uplink communication in the uplink subband or downlink communication in the downlink subband.

[0169] exist Figure 4B In the non-limiting example illustrated, this may include: the UE performing downlink communication in a first subband (e.g., in subband 435) and a second subband (e.g., in one or both of subbands 430 and 440) during time period 410, depending on the modified duplex mode. The UE may discard any uplink communication scheduled in an uplink subband during time period 410. The UE may perform uplink communication in the first subband (e.g., in subband 435) and a second subband (e.g., in one or both of subbands 430 and 440) during time period 415. The UE may discard any downlink communication scheduled in the second subband during time period 415. Depending on the modified duplex mode, during time period 420, the UE may perform uplink communication in the first subband or may perform downlink communication in the second subband.

[0170] Figure 5A block diagram 500 of an apparatus 505 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. Apparatus 505 may be an example of aspects of a UE 115 as described herein. Apparatus 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Apparatus 505, or one or more components of apparatus 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0171] 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 associated with an SBFD-aware UE). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0172] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with SBFD-aware UEs), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0173] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the SBFD-aware UE as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0174] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0175] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0176] In some examples, the communication manager 520 may be configured to use a receiver 510, a transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0177] Communication manager 520 can support wireless communication according to examples disclosed herein. For example, communication manager 520 is capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. Communication manager 520 is capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. Communication manager 520 is capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0178] Additionally or alternatively, the communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during SBFD time periods. The communication manager 520 may be capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The communication manager 520 may be capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0179] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for SBFD-aware UEs responding when configured with a dedicated TDD mode during SBFD time periods.

[0180] Figure 6A block diagram 600 of a device 605 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. 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, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0181] 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., control channels, data channels, information channels associated with an SBFD-aware UE). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0182] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with SBFD-aware UEs), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0183] Device 605 or its various components may be examples of parts for performing various aspects of the SBFD-aware UE as described herein. For example, communication manager 620 may include duplex manager 625, SBFD communication manager 630, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0184] Communication manager 620 can support wireless communication according to the examples disclosed herein. Duplex manager 625 is capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. Duplex manager 625 is capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. SBFD communication manager 630 is capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0185] Additionally or alternatively, the communication manager 620 may support wireless communication according to the examples disclosed herein. The duplex manager 625 is capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during SBFD time periods. The duplex manager 625 is capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The SBFD communication manager 630 is capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0186] Figure 7 A block diagram 700 is shown of a communication manager 720 supporting an SBFD-aware UE according to one or more aspects of this disclosure. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of the SBFD-aware UE as described herein. For example, the communication manager 720 may include a duplex manager 725, an SBFD communication manager 730, a TDD mode manager 735, a selection manager 740, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0187] Communication manager 720 can support wireless communication according to examples disclosed herein. Duplex manager 725 is capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. In some examples, duplex manager 725 is capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. SBFD communication manager 730 is capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0188] In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for performing downlink communication in a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for performing a second uplink communication in a second subband during a subset of the SBFD time period according to a modified duplex mode.

[0189] In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for performing downlink communication in a first subband and a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, to support the performance of downlink communication, the TDD mode manager 735 is capable of, configured to, or operable to support components for combining the first subband and the second subband to form a downlink frequency band during a subset of the SBFD time period.

[0190] In some examples, to support uplink communication, the TDD mode manager 735 is capable of, configured to, or operable to support components for combining a first subband and a second subband to form an uplink band during a subset of the SBFD time period. In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for performing uplink communication in the first and second subbands during a subset of the SBFD time period according to a modified duplex mode.

[0191] In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for performing uplink communication in a first subband during a subset of SBFD time periods according to a modified duplex mode and maintaining a second subband for flexible communication.

[0192] In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for performing downlink communications scheduled in a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for discarding uplink communications scheduled in a first subband during a subset of the SBFD time period according to a modified duplex mode.

[0193] In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for performing uplink communications scheduled in a first subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the TDD mode manager 735 is capable of, configured to, or operable to support components for dropping downlink communications scheduled in a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0194] Additionally or alternatively, the communication manager 720 may support wireless communication according to examples disclosed herein. In some examples, the duplex manager 725 is capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during an SBFD time period. In some examples, the duplex manager 725 is capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. In some examples, the SBFD communication manager 730 is capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of a first subband and a second subband.

[0195] In some examples, the selection manager 740 is capable of, configured to, or operable to support components for performing downlink communications scheduled in a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 740 is capable of, configured to, or operable to support components for discarding uplink communications scheduled in a first subband during a subset of the SBFD time period according to a modified duplex mode.

[0196] In some examples, the selection manager 740 is capable of, configured to, or operable to support components for performing uplink communications scheduled in the first subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 740 is capable of, configured to, or operable to support components for discarding downlink communications scheduled in the second subband during a subset of the SBFD time period according to a modified duplex mode.

[0197] In some examples, the selection manager 740 is capable of, configured to, or operable to support components for performing flexible communication during a subset of SBFD time periods based on a modified duplex mode, wherein the execution includes performing uplink communication in a first subband or performing downlink communication in a second subband.

[0198] In some examples, the selection manager 740 is capable of, configured to, or operable to support components for performing downlink communications scheduled in the first and second subbands during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 740 is capable of, configured to, or operable to support components for dropping uplink communications scheduled in the first subband during a subset of the SBFD time period according to a modified duplex mode.

[0199] In some examples, the selection manager 740 is capable of, configured to, or operable to support components for performing uplink communications scheduled in the first and second subbands during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 740 is capable of, configured to, or operable to support components for dropping downlink communications scheduled in the second subband during a subset of the SBFD time period according to a modified duplex mode.

[0200] In some examples, the selection manager 740 is capable of, configured to, or operable to support components for performing flexible communication during a subset of SBFD time periods based on a modified duplex mode, wherein the performance includes performing uplink communication in a first subband or downlink communication in a second subband. In some examples, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0201] Figure 8A diagram of a system 800 including a device 805 supporting SBFD-aware UEs is shown according to one or more aspects of this disclosure. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

[0202] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one 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.

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

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

[0205] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one 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 at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting SBFD-aware UEs). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, the at least one processor 840 and the at least one memory 830 being configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured to, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0206] The communication manager 820 can support wireless communication according to the examples disclosed herein. For example, the communication manager 820 is capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. The communication manager 820 is capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The communication manager 820 is capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0207] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during an SBFD time period. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The communication manager 820 may be capable of, configured to, or operable to support components for performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0208] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for SBFD-aware UEs to respond when a dedicated TDD mode is configured during the SBFD time period.

[0209] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 815, one or more antennas 825, or any combination thereof, or otherwise cooperating with them. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or executed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause the device 805 to perform various aspects of SBFD-aware UE as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0210] Figure 9 A block diagram 900 of a device 905 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. 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, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0212] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 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, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 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, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0213] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the SBFD-aware UE as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0214] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0215] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0216] In some examples, the communication manager 920 may be configured to use a receiver 910, a transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or integrate with the receiver 910, the transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0217] The communication manager 920 can support wireless communication according to the examples disclosed herein. For example, the communication manager 920 is capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. The communication manager 920 is capable of, configured to, or operable to support components for outputting a second message identifying a modified duplex mode to the UE, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The communication manager 920 is capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0218] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during SBFD time periods. The communication manager 920 may be capable of, configured to, or operable to support components for outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The communication manager 920 may be capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0219] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for SBFD-aware UEs responding when configured with a dedicated TDD mode during SBFD time periods.

[0220] Figure 10 A block diagram 1000 of a device 1005 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0222] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, 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, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, 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, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0223] Device 1005 or its various components may be examples of parts used to perform various aspects of the SBFD-aware UE as described herein. For example, communication manager 1020 may include duplex manager 1025, SBFD communication manager 1030, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0224] Communication manager 1020 can support wireless communication according to the examples disclosed herein. Duplex manager 1025 is capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. Duplex manager 1025 is capable of, configured to, or operable to support components for outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. SBFD communication manager 1030 is capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0225] Additionally or alternatively, the communication manager 1020 may support wireless communication according to the examples disclosed herein. The duplex manager 1025 is capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during SBFD time periods. The duplex manager 1025 is capable of, configured to, or operable to support components for outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The SBFD communication manager 1030 is capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0226] Figure 11A block diagram 1100 of a communication manager 1120 supporting an SBFD-aware UE according to one or more aspects of this disclosure is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the SBFD-aware UE as described herein. For example, the communication manager 1120 may include a duplex manager 1125, an SBFD communication manager 1130, a TDD mode manager 1135, a selection manager 1140, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within a protocol layer 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 virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0227] Communication manager 1120 can support wireless communication according to examples disclosed herein. Duplex manager 1125 is capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. In some examples, duplex manager 1125 is capable of, configured to, or operable to support components for outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. SBFD communication manager 1130 is capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0228] In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for performing downlink communication with the UE in a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for performing a second uplink communication with the UE in a second subband during a subset of the SBFD time period according to a modified duplex mode.

[0229] In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for performing downlink communication with the UE in a first subband and a second subband during a subset of the SBFD time period, based on a modified duplex mode. In some examples, to support the performance of downlink communication, the TDD mode manager 1135 is capable of, configured to, or operable to support components for combining the first subband and the second subband to form a downlink frequency band during a subset of the SBFD time period.

[0230] In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for performing uplink communication with the UE in a first subband and a second subband during a subset of the SBFD time period, based on a modified duplex mode. In some examples, to support the performance of uplink communication, the TDD mode manager 1135 is capable of, configured to, or operable to support components for combining the first subband and the second subband to form an uplink frequency band during a subset of the SBFD time period.

[0231] In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for performing uplink communication with the UE in a first subband during a subset of SBFD time periods according to a modified duplex mode and maintaining a second subband for flexible communication.

[0232] In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for performing downlink communication scheduled with the UE in a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for discarding uplink communication scheduled with the UE in a first subband during a subset of the SBFD time period according to a modified duplex mode.

[0233] In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for performing uplink communication scheduled with the UE in a first subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the TDD mode manager 1135 is capable of, configured to, or operable to support components for discarding downlink communication scheduled with the UE in a second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0234] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. In some examples, the duplex manager 1125 is capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during SBFD time periods. In some examples, the duplex manager 1125 is capable of, configured to, or operable to support components for outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. In some examples, the SBFD communication manager 1130 is capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0235] In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for performing downlink communications with the UE scheduled in the second subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for dropping uplink communications scheduled in the first subband during a subset of the SBFD time period according to a modified duplex mode.

[0236] In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for performing uplink communications with the UE scheduled in the first subband during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for dropping downlink communications scheduled in the second subband during a subset of the SBFD time period according to a modified duplex mode.

[0237] In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for performing flexible communication with the UE during a subset of SBFD time periods based on a modified duplex mode, wherein the performance includes performing uplink communication in a first subband or performing downlink communication in a second subband.

[0238] In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for performing downlink communications with the UE scheduled in the first and second subbands during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for dropping uplink communications scheduled in the first subband during a subset of the SBFD time period according to a modified duplex mode.

[0239] In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for performing uplink communications with the UE scheduled in the first and second subbands during a subset of the SBFD time period according to a modified duplex mode. In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for dropping downlink communications scheduled in the second subband during a subset of the SBFD time period according to a modified duplex mode.

[0240] In some examples, the selection manager 1140 is capable of, configured to, or operable to support components for performing flexible communication with the UE during a subset of SBFD time periods based on a modified duplex mode, wherein the performance includes performing uplink communication in a first subband or downlink communication in a second subband. In some examples, the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0241] Figure 12 A diagram of a system 1200 including a device 1205 supporting SBFD-aware UEs is shown according to one or more aspects of this disclosure. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and acquisition of communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically via one or more buses (e.g., bus 1240) or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0242] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1215, by 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 embodiments, 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 receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both), may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0243] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of the at least one 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 one of the at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may contain a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0244] At least one 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 units, discrete hardware components, or any combination thereof). In some cases, at least one 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 one or more processors in at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting SBFD-aware UEs). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more processors in at least one processor 1235, wherein at least one processor 1235 and at least one memory 1225 are configured to perform the various functions described herein. At least one 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 can host functions (e.g., by executing code 1230) to perform the functions of device 1205. At least one 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 one or more memories of at least one memory 1225). In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operable to cause the device 1205 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

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

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

[0247] Communication manager 1220 may support wireless communications according to examples disclosed herein. For example, communication manager 1220 may be capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during SBFD time periods. Communication manager 1220 may be capable of, configured to, or operable to support components for outputting a second message identifying a modified duplex mode to the UE, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. Communication manager 1220 may be capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0248] Additionally or alternatively, the communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during SBFD time periods. The communication manager 1220 may be capable of, configured to, or operable to support components for outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The communication manager 1220 may be capable of, configured to, or operable to support components for performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of the first and second subbands.

[0249] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for SBFD-aware UEs to respond when a dedicated TDD mode is configured during the SBFD period.

[0250] In some examples, the communication manager 1220 may be configured to use or cooperate with transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof, to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors in at least one processor 1235 to cause device 1205 to perform various aspects of SBFD-aware UE as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0251] Figure 13 A flowchart illustrating a method 1300 for supporting SBFD-aware UE according to one or more aspects of this disclosure is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0252] At 1305, the method may include: receiving a first message identifying a duplex mode, which allocates a first subband for uplink communication and a second subband for flexible communication during the SBFD time period. The operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 7 The duplex manager 725 is described and executed.

[0253] At 1310, the method may include: receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or for downlink communication. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 7 The duplex manager 725 is described and executed.

[0254] At 1315, the method may include: performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of a first subband and a second subband. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to [reference needed]. Figure 7 The SBFD communication manager 730 described is used to execute this.

[0255] Figure 14 A flowchart illustrating a method 1400 for supporting SBFD-aware UE according to one or more aspects of this disclosure is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0256] At 1405, the method may include: receiving a first message identifying a duplex mode, which allocates a first subband for uplink communication and a second subband for downlink communication during the SBFD time period. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 7 The duplex manager 725 is described and executed.

[0257] At 1410, the method may include: receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or for downlink communication. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference]. Figure 7 The duplex manager 725 is described and executed.

[0258] At 1415, the method may include: performing uplink or downlink communication according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of a first subband and a second subband. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be derived from references... Figure 7 The SBFD communication manager 730 described is used to execute this.

[0259] Figure 15 A flowchart illustrating a method 1500 for supporting SBFD-aware UE according to one or more aspects of this disclosure is shown. Operation of method 1500 may be implemented by a network entity or its components as described herein. For example, operation of method 1500 may be performed by, as referenced... Figure 1 up to Figure 4 and Figures 9 to 12 The network entity described performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0260] At 1505, the method may include: outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for flexible communication during the SBFD time period. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be derived from references... Figure 11 The duplex manager 1125 described is used to execute this.

[0261] At 1510, the method may include: outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or downlink communication. The operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 11 The duplex manager 1125 described is used to execute this.

[0262] At 1515, the method may include: performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of a first subband and a second subband. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to [reference]. Figure 11 The SBFD communication manager 1130 described is executed.

[0263] Figure 16 A flowchart illustrating a method 1600 for supporting SBFD-aware UE according to one or more aspects of this disclosure is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be performed by, as referenced... Figure 1 up to Figure 4 and Figures 9 to 12 The network entity described performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0264] At 1605, the method may include: outputting a first message identifying a duplex mode that allocates a first subband for uplink communication and a second subband for downlink communication during the SBFD time period. The operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be derived from references... Figure 11 The duplex manager 1125 described is used to execute this.

[0265] At 1610, the method may include: outputting a second message to the UE identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of SBFD time periods for uplink communication or for downlink communication. The operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be provided by reference to [reference needed]. Figure 11 The duplex manager 1125 described is used to execute this.

[0266] At 1615, the method may include: performing uplink or downlink communication with the UE according to a modified duplex mode during one or more SBFD time periods within a subset of SBFD time periods, wherein the uplink or downlink communication is performed in one or both of a first subband and a second subband. The operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be provided by reference to [reference]. Figure 11 The SBFD communication manager 1130 described is executed.

[0267] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for flexible communication during a SBFD time period; receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of the SBFD time periods for the uplink communication or for downlink communication; and performing the uplink communication or the downlink communication according to the modified duplex mode during one or more SBFD time periods in the subset of the SBFD time periods, wherein the uplink communication or the downlink communication is performed in one or both of the first subband and the second subband.

[0268] Aspect 2: According to the method of aspect 1, the method further includes: performing the downlink communication in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0269] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: performing a second uplink communication in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0270] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: performing the downlink communication in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0271] Aspect 5: According to the method of aspect 4, performing the downlink communication includes: combining the first subband and the second subband during the subset of the SBFD time period to form a downlink frequency band.

[0272] Aspect 6: The method according to any one of Aspects 4 to 5, wherein performing the uplink communication comprises: combining the first subband and the second subband to form an uplink frequency band during the subset of the SBFD time period.

[0273] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: performing the uplink communication in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0274] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: performing the uplink communication in the first subband during the subset of the SBFD time period according to the modified duplex mode and maintaining the second subband for the flexible communication.

[0275] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: performing the downlink communication scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the uplink communication scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode.

[0276] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: performing the uplink communication scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the downlink communication scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0277] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0278] Aspect 12: A method for performing wireless communication at a UE, the method comprising: receiving a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for downlink communication during an SBFD time period; receiving a second message identifying a modified duplex mode, wherein the modified duplex mode allocates a subset of the SBFD time periods for the uplink communication or the downlink communication; and performing the uplink communication or the downlink communication according to the modified duplex mode during one or more SBFD time periods in the subset of the SBFD time periods, wherein the uplink communication or the downlink communication is performed in one or both of the first subband and the second subband.

[0279] Aspect 13: The method according to aspect 12, the method further comprising: performing the downlink communication scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the uplink communication scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode.

[0280] Aspect 14: The method according to any one of Aspects 12 to 13, the method further comprising: performing the uplink communication scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the downlink communication scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0281] Aspect 15: The method according to any one of Aspects 12 to 14, the method further comprising: performing flexible communication during a subset of the SBFD time period according to the modified duplex mode, wherein the performance includes: performing the uplink communication in the first subband or performing the downlink communication in the second subband.

[0282] Aspect 16: The method according to any one of Aspects 12 to 15, the method further comprising: performing the downlink communication scheduled in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the uplink communication scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode.

[0283] Aspect 17: The method according to any one of Aspects 12 to 16, the method further comprising: performing the uplink communication scheduled in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the downlink communication scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0284] Aspect 18: The method according to any one of Aspects 12 to 17, the method further comprising: performing flexible communication during a subset of the SBFD time period according to the modified duplex mode, wherein the performance includes: performing the uplink communication in the first subband or performing the downlink communication in the second subband.

[0285] Aspect 19: The method according to any one of Aspects 12 to 18, wherein the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0286] Aspect 20: A method for wireless communication at a network entity, the method comprising: outputting a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for flexible communication during an SBFD time period; outputting a second message identifying a modified duplex mode to a UE, wherein the modified duplex mode allocates a subset of the SBFD time periods for the uplink communication or for downlink communication; and performing the uplink communication or the downlink communication with the UE according to the modified duplex mode during one or more SBFD time periods in the subset of the SBFD time periods, wherein the uplink communication or the downlink communication is performed in one or both of the first subband and the second subband.

[0287] Aspect 21: The method according to aspect 20, the method further comprising: performing the downlink communication with the UE in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0288] Aspect 22: The method according to any one of Aspects 20 to 21, the method further comprising: performing a second uplink communication with the UE in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0289] Aspect 23: The method according to any one of Aspects 20 to 22, the method further comprising: performing the downlink communication with the UE in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0290] Aspect 24: According to the method of aspect 23, performing the downlink communication includes: combining the first subband and the second subband during the subset of the SBFD time period to form a downlink frequency band.

[0291] Aspect 25: The method according to any one of Aspects 20 to 24, the method further comprising: performing the uplink communication with the UE in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0292] Aspect 26: According to the method of aspect 25, performing the uplink communication includes: combining the first subband and the second subband during the subset of the SBFD time period to form an uplink frequency band.

[0293] Aspect 27: The method according to any one of Aspects 20 to 26, the method further comprising: performing uplink communication with the UE in the first subband during the subset of the SBFD time period according to the modified duplex mode and maintaining the second subband for the flexible communication.

[0294] Aspect 28: The method according to any one of Aspects 20 to 27, the method further comprising: performing downlink communication scheduled with the UE in the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding uplink communication scheduled with the UE in the first subband during the subset of the SBFD time period according to the modified duplex mode.

[0295] Aspect 29: The method according to any one of Aspects 20 to 28, the method further comprising: performing uplink communication scheduled with the UE in the first subband during the subset of the SBFD time period according to the modified duplex mode; and discarding downlink communication scheduled with the UE in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0296] Aspect 30: The method according to any one of Aspects 20 to 29, wherein the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0297] Aspect 31: A method for wireless communication at a network entity, the method comprising: outputting a first message identifying a duplex mode, the duplex mode allocating a first subband for uplink communication and a second subband for downlink communication during an SBFD time period; outputting a second message identifying a modified duplex mode to a UE, wherein the modified duplex mode allocates a subset of the SBFD time periods for the uplink communication or the downlink communication; and performing the uplink communication or the downlink communication with the UE according to the modified duplex mode during one or more SBFD time periods in the subset of the SBFD time periods, wherein the uplink communication or the downlink communication is performed in one or both of the first subband and the second subband.

[0298] Aspect 32: The method according to aspect 31, the method further comprising: performing downlink communication with the UE scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding uplink communication scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode.

[0299] Aspect 33: The method according to any one of Aspects 31 to 32, the method further comprising: performing uplink communication with the UE scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode; and discarding downlink communication scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0300] Aspect 34: The method according to any one of Aspects 31 to 33, the method further comprising: performing flexible communication with the UE during a subset of the SBFD time period according to the modified duplex mode, wherein the performance includes: performing the uplink communication in the first subband or performing the downlink communication in the second subband.

[0301] Aspect 35: The method according to any one of Aspects 31 to 34, the method further comprising: performing downlink communication with the UE scheduled in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the uplink communication scheduled in the first subband during the subset of the SBFD time period according to the modified duplex mode.

[0302] Aspect 36: The method according to any one of Aspects 31 to 35, the method further comprising: performing uplink communication with the UE scheduled in the first subband and the second subband during the subset of the SBFD time period according to the modified duplex mode; and discarding the downlink communication scheduled in the second subband during the subset of the SBFD time period according to the modified duplex mode.

[0303] Aspect 37: The method according to any one of Aspects 31 to 36, the method further comprising: performing flexible communication with the UE during a subset of the SBFD time period according to the modified duplex mode, wherein the performance includes: performing the uplink communication in the first subband or performing the downlink communication in the second subband.

[0304] Aspect 38: The method according to any one of Aspects 31 to 37, wherein the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

[0305] Aspect 39: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 11.

[0306] Aspect 40: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 11.

[0307] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 1 to 11.

[0308] Aspect 42: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 12 to 19.

[0309] Aspect 43: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 12 to 19.

[0310] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 12 to 19.

[0311] Aspect 45: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 20 to 30.

[0312] Aspect 46: A network entity for wireless communication, the network node comprising at least one component for performing the method according to any one of aspects 20 to 30.

[0313] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 20 to 30.

[0314] Aspect 48: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 31 to 38.

[0315] Aspect 49: A network entity for wireless communication, the network node comprising at least one component for performing the method according to any one of aspects 31 to 38.

[0316] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 31 to 38.

[0317] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0318] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most 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 techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0319] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0320] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0321] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When 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 this disclosure and the appended 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. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0322] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. 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 coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0323] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0324] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of those one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0325] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0326] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0327] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a first message identifying the duplex mode, wherein the duplex mode allocates a first subband for uplink communication and a second subband for flexible communication during the subband full-duplex time period; Receive a second message indicating a modified duplex mode, wherein the modified duplex mode is allocated a subset of the subband full-duplex time period for the uplink communication or for the downlink communication; as well as During one or more subband full-duplex time periods in the subset of the subband full-duplex time periods, the uplink communication or the downlink communication is performed according to the modified duplex mode, wherein the uplink communication or the downlink communication is performed in one or both of the first subband and the second subband.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the downlink communication is performed in the second subband during the subset of the subband full-duplex time period.

3. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, a second uplink communication is performed in the second subband during the subset of the subband full-duplex time period.

4. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the downlink communication is performed in the first subband and the second subband during the subset of the subband full-duplex time period.

5. The UE according to claim 4, wherein, In order to perform the downlink communication, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The first subband and the second subband are combined during the subset of the subband's full-duplex time period to form a downlink frequency band.

6. The UE according to claim 4, wherein, In order to perform the uplink communication, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The first subband and the second subband are combined during the subset of the subband's full-duplex time period to form an uplink frequency band.

7. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the uplink communication is performed in the first subband and the second subband during the subset of the subband full-duplex time period.

8. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the uplink communication is performed in the first subband during the subset of the subband full-duplex time period, and the second subband for the flexible communication is maintained.

9. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the downlink communication scheduled in the second subband is performed during the subset of the full-duplex time period of the subband; and According to the modified duplex mode, uplink communications scheduled in the first subband are discarded during the subset of the subband's full-duplex time period.

10. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the uplink communication scheduled in the first subband is performed during the subset of the subband full-duplex time period; and According to the modified duplex mode, downlink communications scheduled in the second subband are discarded during the subset of the subband's full-duplex time period.

11. The UE of claim 1, wherein the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

12. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a first message identifying the duplex mode, wherein the duplex mode allocates a first subband for uplink communication and a second subband for downlink communication during the subband full-duplex time period; Receive a second message indicating a modified duplex mode, wherein the modified duplex mode is allocated a subset of the subband full-duplex time period for the uplink communication or the downlink communication; as well as During one or more subband full-duplex time periods in the subset of the subband full-duplex time periods, the uplink communication or the downlink communication is performed according to the modified duplex mode, wherein the uplink communication or the downlink communication is performed in one or both of the first subband and the second subband.

13. The UE of claim 12, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the downlink communication scheduled in the second subband is performed during the subset of the full-duplex time period of the subband; and According to the modified duplex mode, uplink communications scheduled in the first subband are discarded during the subset of the subband's full-duplex time period.

14. The UE of claim 12, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the uplink communication scheduled in the first subband is performed during the subset of the subband full-duplex time period; and According to the modified duplex mode, downlink communications scheduled in the second subband are discarded during the subset of the subband's full-duplex time period.

15. The UE of claim 12, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Flexible communication is performed during the subset of the subband full-duplex time period according to the modified duplex mode, wherein the execution includes: The uplink communication is performed in the first subband or the downlink communication is performed in the second subband.

16. The UE of claim 12, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the downlink communication scheduled in the first and second subbands is performed during the subset of the full-duplex time period of the subband; and According to the modified duplex mode, uplink communications scheduled in the first subband are discarded during the subset of the subband's full-duplex time period.

17. The UE of claim 12, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the modified duplex mode, the uplink communication scheduled in the first and second subbands is performed during the subset of the full-duplex time period of the subband; and According to the modified duplex mode, downlink communications scheduled in the second subband are discarded during the subset of the subband's full-duplex time period.

18. The UE of claim 12, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Flexible communication is performed during the subset of the subband full-duplex time period according to the modified duplex mode, wherein the execution includes: The uplink communication is performed in the first subband or the downlink communication is performed in the second subband.

19. The UE of claim 12, wherein the first message includes a public or broadcast message or a first UE-specific message, and the second message includes a second UE-specific message.

20. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Output a first message identifying the duplex mode, wherein the duplex mode allocates a first subband for uplink communication and a second subband for flexible communication during the subband full-duplex time period; A second message is output to the user equipment (UE) indicating a modified duplex mode, wherein the modified duplex mode allocates a subset of the subband full-duplex time period for the uplink communication or for the downlink communication. as well as During one or more subband full-duplex time periods in the subset of the subband full-duplex time periods, the uplink communication or the downlink communication with the UE is performed according to the modified duplex mode, wherein the uplink communication or the downlink communication is performed in one or both of the first subband and the second subband.

Images