Discontinuous resource blocks for bandwidth portion configuration

Abstract

Methods, systems, and devices for wireless communication are described. An example wireless communication system may implement control signaling that configures a user equipment (UE) to communicate in a sub-band full duplex (SBFD) mode. The SBFD mode may include a discontinuous bandwidth portion (BWP), and the control signaling may indicate resource blocks (RBs) included in the discontinuous BWP. In some cases, the discontinuous BWP may be used for communication between the UE and a network in one communication direction (e.g., uplink or downlink), and another BWP may be configured for communication between the UE and the network in another communication direction. The non-contiguous BWP may include two sub-bands, and the other BWP may not overlap with the two sub-bands (e.g., between the two sub-bands) in the frequency domain. The network may configure a BWP time domain switching mode (e.g., switch between an SBFD mode and a half-duplex mode according to the BWP time domain switching mode).

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to U.S. patent application No. 17 / 886,408, entitled “NON-CONTIGUOUS RESOURCE BLOCKS FOR BANDWIDTH PART CONFIGURATION,” filed by ZHANG et al. on August 11, 2022, which is assigned to the assignee of this application. Technical Field

[0002] The following relates to wireless communications including non-contiguous resource blocks for bandwidth portion configuration. Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to 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, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses that support non-contiguous resource blocks (RBs) for bandwidth part (BWP) configuration. For example, the described technology provides control signaling to configure a user equipment (UE) to communicate with a network in a sub-band full-duplex (SBFD) mode. The SBFD mode may include a non-contiguous BWP, and the control signaling may indicate the RBs included in the non-contiguous BWP. In some cases, the non-contiguous BWP may be configured for communication between the UE and the network in one communication direction (e.g., uplink or downlink), and another BWP may be configured for communication between the UE and the network in another communication direction. The non-contiguous BWP may include two subbands, and the other BWP may not overlap with the two subbands in the frequency domain (e.g., be located between the two subbands). In some cases, the control signaling may indicate the RBs in each BWP by including an array for each BWP, the array indicating the RBs included in the BWP (which may not be contiguous in the frequency domain). In some cases, the control signaling may indicate the RBs in each BWP by including an indication of the subbands in each BWP, the starting RB index of each subband, and the number of RBs in each subband. In some cases, the control signaling may indicate the RBs in each BWP by including a bitmap for each BWP, the bitmap indicating the RBs included in the BWP. Additional control signaling, such as a medium access control (MAC) control element (MAC-CE) or a downlink control information (DCI) message, may update the RBs associated with one or more BWPs and / or subbands. In some cases, the network may configure the BWP time domain switching mode. For example, the network may configure the communication to switch between SBFD mode and half-duplex mode according to the BWP time domain switching mode.

[0005] A method for wireless communication at a UE is described. The method may include: receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicating with the network entity in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicate with the network entity in SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and a component for communicating with the network entity in an SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicating with the network entity in SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving an indication of a first identifier associated with a first BWP; receiving an indication that the first BWP may be associated with a first communication direction; and, for the first BWP, receiving an indication of a first group of RBs and a second group of RBs from a group of multiple RBs associated with at least one carrier bandwidth including the first BWP.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving an indication of a second identifier associated with a second BWP; receiving an indication that the second BWP may be associated with a second communication direction; and receiving, for the second BWP, an indication of a third group of RBs from the group of multiple RBs.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first identifier may be equal to the second identifier.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first identifier may be different from the second identifier.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving an indication of a first identifier associated with a first BWP; receiving an indication that the first BWP may be associated with a first communication direction; receiving, for a first subband, an indication of a starting RB index of a first group of RBs and a size of the first group of RBs in RBs; and receiving, for a second subband, an indication of a starting RB index of a second group of RBs and a size of the second group of RBs in RBs.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving an indication of a second identifier associated with a second BWP; receiving an indication that the second BWP may be associated with the first communication direction; and receiving, for the second BWP, an indication of a starting RB index of a third group of RBs and a size in RBs of the third group of RBs.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving an indication of a first identifier associated with a first BWP; receiving an indication that the first BWP may be associated with a first communication direction; and receiving a bitmap for the first BWP indicating a first group of RBs and a second group of RBs.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving an indication of a second identifier associated with a first BWP; receiving an indication that the second BWP may be associated with a second communication direction; and receiving a second bitmap indicating a third group of RBs for the second BWP.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control signaling indicating a group of BWPs, the group of BWPs including a first subset of BWPs associated with non-contiguous RBs and a second subset of BWPs associated with contiguous RBs, the first subset of BWPs including a first BWP and a second BWP, and wherein receiving the control signaling includes receiving an indication that a group of time slots may be associated with the first BWP and the second BWP.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a third control signaling that updates an RB associated with at least one of a first BWP, a second BWP, a third BWP of a second subset of BWPs, or a fourth BWP of a second subset of BWPs, wherein the third BWP may be associated with a first communication direction and wherein the fourth BWP may be associated with a second communication direction, wherein the first subset of BWPs includes only the first BWP and the second BWP, and wherein the second subset of BWPs includes only the third BWP and the fourth BWP.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving third control signaling indicating another selected BWP for the second group of time slots from the set of BWPs.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control signaling to update RBs included in the first group of RBs, RBs included in the second group of RBs, RBs included in the third group of RBs, or a combination thereof.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving an indication of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including a first BWP and a second BWP, the second BWP configuration including a third BWP associated with a first communication direction and a fourth BWP associated with a second communication direction, wherein the control signaling also includes an indication of a time domain switching mode between the first BWP configuration and the second BWP configuration.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the time domain switching pattern includes a time gap between one or more time slots associated with the first BWP configuration and one or more time slots associated with the second BWP configuration.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first guard band may be located between the first and third groups of RBs in the frequency domain, and the second guard band may be located between the third and second groups of RBs in the frequency domain.

[0024] A method for wireless communication at a network entity is described. The method may include: outputting control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicating in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0025] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: output control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicate in SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0026] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for outputting control signaling, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and a component for communicating in SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0027] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to perform the following operations: output control signaling, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicate in SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control signaling may include operations, features, components, or instructions for: outputting an indication of a first identifier associated with a first BWP; outputting an indication that the first BWP may be associated with a first communication direction; and, for the first BWP, outputting an indication of a first group of RBs and a second group of RBs from a group of multiple RBs associated with at least one carrier bandwidth including the first BWP.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control signaling may include operations, features, components, or instructions for: outputting an indication of a second identifier associated with a second BWP; outputting an indication that the second BWP may be associated with a second communication direction; and, for the second BWP, outputting an indication of a third group of RBs from the group of multiple RBs.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first identifier may be equal to the second identifier.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first identifier may be different from the second identifier.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control signaling may include operations, features, components, or instructions for: outputting an indication of a first identifier associated with a first BWP; outputting an indication that the first BWP may be associated with a first communication direction; for a first subband, outputting an indication of a starting RB index of a first group of RBs and a size of the first group of RBs in RBs; and for a second subband, outputting an indication of a starting RB index of a second group of RBs and a size of the second group of RBs in RBs.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control signaling may include operations, features, components, or instructions for: outputting an indication of a second identifier associated with a second BWP; outputting an indication that the second BWP may be associated with a first communication direction; and, for the second BWP, outputting an indication of a starting RB index of a third group of RBs and a size in RBs of the third group of RBs.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control signaling may include operations, features, components, or instructions for: outputting an indication of a first identifier associated with a first BWP; outputting an indication that the first BWP may be associated with a first communication direction; and outputting a bitmap indicating a first group of RBs and a second group of RBs for the first BWP.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control signaling may include operations, features, components, or instructions for: outputting an indication of a second identifier associated with a first BWP; outputting an indication that the second BWP may be associated with a second communication direction; and outputting a second bitmap indicating a third group of RBs for the second BWP.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a second control signaling indicating a group of BWPs, the group of BWPs including a first subset of BWPs associated with non-contiguous RBs and a second subset of BWPs associated with contiguous RBs, the first subset of BWPs including a first BWP and a second BWP, and wherein receiving the control signaling includes receiving an indication that a group of time slots can be associated with the first BWP and the second BWP.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a third control signaling that updates an RB associated with at least one of a first BWP, a second BWP, a third BWP of a second subset of BWPs, or a fourth BWP of a second subset of BWPs, wherein the third BWP may be associated with a first communication direction and wherein the fourth BWP may be associated with a second communication direction, wherein the first subset of BWPs includes only the first BWP and the second BWP, and wherein the second subset of BWPs includes only the third BWP and the fourth BWP.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting third control signaling indicating another selected BWP from the set of BWPs for the second set of time slots.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting second control signaling that updates RBs included in the first group of RBs, RBs included in the second group of RBs, RBs included in the third group of RBs, or a combination thereof.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, output control signaling may include operations, features, components, or instructions for: outputting indications of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including a first BWP and a second BWP, the second BWP configuration including a third BWP associated with a first communication direction and a fourth BWP associated with a second communication direction, wherein the control signaling also includes an indication of a time domain switching mode between the first BWP configuration and the second BWP configuration.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the time domain switching pattern includes a time gap between one or more time slots associated with the first BWP configuration and one or more time slots associated with the second BWP configuration.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first guard band may be located between the first and third groups of RBs in the frequency domain, and the second guard band may be located between the third and second groups of RBs in the frequency domain. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 An example of a wireless communication system supporting non-contiguous resource blocks (RBs) for bandwidth part (BWP) configuration in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 2 An example of a multiplexing method supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated.

[0045] Figure 3 An example of a wireless communication system supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated.

[0046] Figure 4 An example of a time-domain BWP switching pattern supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated.

[0047] Figure 5 An example of a process flow supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated.

[0048] Figure 6 and Figure 7 A block diagram of a device supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown.

[0049] Figure 8 A block diagram of a communication manager supporting non-contiguous RBs for BWP configuration is shown in accordance with one or more aspects of the present disclosure.

[0050] Fig. 9 A diagram of a system including a device supporting non-contiguous RBs for BWP configuration is shown in accordance with one or more aspects of the present disclosure.

[0051] Fig.10 and Fig.11 A block diagram of a device supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown.

[0052] Fig.12 A block diagram of a communication manager supporting non-contiguous RBs for BWP configuration is shown in accordance with one or more aspects of the present disclosure.

[0053] Fig.13 A diagram of a system including a device supporting non-contiguous RBs for BWP configuration is shown in accordance with one or more aspects of the present disclosure.

[0054] Figures 14 to 17 A flow chart illustrating a method of supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0055] In some wireless communication systems, a wireless device may communicate with one or more other wireless devices according to a half-duplex mode (according to which the wireless device may transmit or receive at non-overlapping times) or a full-duplex mode (according to which the wireless device may transmit and receive simultaneously). Full-duplex communication may provide greater system capacity, higher data rates, and lower latency than half-duplex communication. Some wireless communication systems may implement a sub-band full-duplex (SBFD) communication scheme, in which a first bandwidth part (BWP) that may include multiple non-contiguous sub-bands may be used for communication in one direction (one of the uplink or downlink), and a second BWP may be used for communication in the other direction in the same time resource (e.g., the same time slot or symbol). The sub-bands may be non-contiguous, which means that the sub-bands are separated in the frequency domain. In half-duplex mode, the network may indicate resources for communication between the network and the user equipment (UE) via radio resource control (RRC) signaling. For example, the network may indicate a set of contiguous resource blocks (RBs) within the uplink BWP and the downlink BWP. Some wireless communication systems may lack a signaling mechanism by which the network may inform the UE of resources to be used for full-duplex (eg, SBFD) communications.

[0056] Some wireless communication systems may implement control signaling that configures a UE to communicate in an SBFD mode that includes a non-contiguous BWP and indicates the RBs included in the non-contiguous BWP. In some examples, the non-contiguous BWP may be configured for communication between the UE and the network in one direction (e.g., uplink or downlink), and another BWP may be configured for communication between the UE and the network in another direction. The non-contiguous BWP may include two subbands, and the other BWP may not overlap with the two subbands in the frequency domain (e.g., be located between the two subbands). In some examples, the control signaling may indicate the RBs in each BWP by including an array for each BWP, the array indicating the RBs included in the BWP (which may not be contiguous in the frequency domain). In some examples, the control signaling may indicate the RBs in each BWP by including an indication of the subbands in each BWP, the starting RB index of each subband, and the number of RBs in each subband. In some examples, control signaling may indicate RBs in each BWP by including a bitmap for each BWP, the bitmap indicating the RBs included in the BWP. In some examples, additional control signaling, such as a medium access control (MAC) control element (MAC-CE) or a downlink control information (DCI) message, may update the RBs associated with one or more BWPs and / or subbands. The network may configure the BWP time domain switching mode. For example, the network may configure the communication to switch between SBFD mode and half-duplex mode according to the BWP time domain switching mode.

[0057] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated and described with reference to multiplexing patterns, time domain BWP switching patterns, and process flows. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to non-contiguous RBs for BWP configuration.

[0058] Figure 1 An example of a wireless communication system 100 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

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

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

[0061] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a 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, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a 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 a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

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

[0063] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a clustered (e.g., monolithic, stand-alone) base station architecture, which 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 a base station 140).

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

[0065] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionality, 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 functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, MAC layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0066] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas (e.g., of the RU 170) of the IAB node 104 for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB 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 the IAB node 104) may be configured to operate according to the techniques described herein.

[0067] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an 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, the 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), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).

[0068] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, 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 that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115 .

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

[0070] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support non-contiguous RBs for BWP configuration 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).

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

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

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

[0074] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates 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 based on a channel raster used for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

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

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

[0078] One or more parameter sets for a carrier may be supported, and a parameter set may include a subcarrier spacing ( ) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP of a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0079] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period. Seconds, for this may indicate the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0080] 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 be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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 may depend on the subcarrier spacing or the operating frequency band.

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

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

[0083] The 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 to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0084] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0085] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0086] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for 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 provide coverage for various coverage areas 110 using the same or different radio access technologies.

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

[0088] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0089] Some UEs 115 may be configured to employ a mode of operation that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed with a reduced peak rate. Other power saving techniques for UEs 115 include entering a power saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or RB set) within a carrier, within a guard band of a carrier, or outside a carrier.

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

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

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

[0093] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0094] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0095] The wireless communication system 100 may also operate using a super high frequency (SHF) region that may be in the range of 3 GHz to 30 GHz (also referred to as a centimeter band) or an extremely high frequency (EHF) region that uses a spectrum (also referred to as a millimeter band, for example, from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within a device. However, the propagation of EHF transmissions may be affected by greater attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency zones, and the use of frequency bands specified across these frequency zones may vary by country or regulatory agency.

[0096] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ License Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

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

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

[0099] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

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

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

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

[0103] 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 receiving 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 received signals according to different antenna subarrays, receiving according to different reception beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different reception beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different 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 receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0104] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0105] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or based on some other time interval.

[0106] Various devices within the wireless communication system 100 may support one or more levels of duplex operation, depending on or associated with a deployment scenario, duplex mode (such as TDD only, FDD only, or both TDD and FDD), or interference management procedures. In some aspects, wireless devices within the wireless communication system 100 (such as UE 115, network entity 105, or IAB node 104) may support half-duplex or full-duplex operation. For example, the network entity 105 may support various types of MIMO communications, including: downlink multi-user MIMO (MU-MIMO), according to which the network entity 105 may send downlink signaling to two different UEs 115 at the same time; uplink MU-MIMO, according to which the network entity may receive uplink signaling from two different UEs 115 at the same time; or downlink and uplink MU-MIMO (which may be referred to herein as full-duplex operation), according to which the network entity 105 may send downlink signaling to a first UE 115 while receiving uplink signaling from a second UE 115. The network entity 105 may also support enhanced MIMO (eMIMO) or further enhanced MIMO (FeMIMO), which may be associated with a FeMIMO beam management session. According to full-duplex operation, the wireless device may be able to transmit and receive simultaneously. In other words, the wireless device may support simultaneous uplink and downlink transmissions (e.g., uplink transmissions and downlink transmissions that at least partially overlap in time).

[0107] Full-duplex operation may include sub-band full-duplex (SBFD), according to which the simultaneous transmission or reception of downlink or uplink signaling may be on a per-subband basis or intra-band full-duplex (IBFD). According to SBFD, the component carrier bandwidth may be divided in the frequency domain into a set of one or more downlink portions and a set of one or more uplink portions for a given duration (such as for a given time slot). For example, within a time slot, downlink communications may be conducted via a first set of one or more frequency bands, while uplink communications may be conducted via a second set of one or more frequency bands. In addition, full-duplex operation may include simultaneous transmission and reception on the same symbol, TTI, or time slot.

[0108] According to half-duplex operation, the wireless device can transmit or receive, but not transmit and receive at the same time. The wireless device can support full-duplex operation across various RF bands. For example, the wireless device can support simultaneous uplink and downlink transmission within the frequency range 1 (FR1) band, within the FR2 band, or across the FR1 and FR2 bands. In the scenario where the wireless device supports simultaneous uplink and downlink transmission within the FR2 band, the wireless device can also support associated aspects of the program for implementing or facilitating appropriate FR2 communications.

[0109] Full-duplex capability may be present at either or both of the network entity 105 or the UE 115. In scenarios where the UE 115 is capable of full-duplex operation, the UE 115 may use a first antenna panel, module, or set of elements for uplink transmission (such as transmitting to the network entity 105) and may use a second antenna panel, module, or set of elements for downlink reception (such as receiving from the network entity 105). In scenarios where the network entity 105 is capable of full-duplex operation, the network entity 105 may use a first antenna panel, module, or set of elements for uplink reception (such as receiving from the UE 115) and may use a second antenna panel, module, or set of elements for downlink transmission (such as transmitting to the UE 115). In some aspects, full-duplex capability may depend on one or more transmission parameters. For example, full-duplex capability may depend on beam separation (such as separation between a first directional beam for uplink and a second directional beam for downlink), which may involve or cause self-interference between downlink and uplink signaling, and clutter (such as clutter echo, which may refer to scattered signals that cause interference). Thus, if a first directional beam for uplink transmission or reception is sufficiently separated from a second directional beam for downlink transmission or reception in the spatial domain, the wireless device can use full-duplex operation. In some aspects, the amount of self-interference can be associated or related to the distance between the transmit antenna panel and the receive antenna panel. .

[0110] In some implementations, the UE 115 and the network entity 105 may support one or more signaling-based mechanisms according to which the network entity 105 may inform the UE 115 which time resources and frequency resources may be used for full-duplex communication. For example, the network entity 105 may send control signaling (e.g., RRC signaling) that configures the UE 115 to communicate with the network entity 105 in a SBFD mode that includes a non-contiguous BWP and indicates RBs included in the non-contiguous BWP. In some examples, the non-contiguous BWP may be configured for communication between the UE 115 and the network entity 105 in one direction (e.g., uplink or downlink), and another BWP may be configured for communication between the UE 115 and the network entity 105 in another direction. The non-contiguous BWP may include two subbands, and the other BWP may not overlap with the two subbands in the frequency domain (e.g., be located between the two subbands). In some examples, the control signaling may indicate the RBs in each BWP by including an array for each BWP, the array indicating the RBs included in the BWP (which may not be contiguous in the frequency domain). In some examples, the control signaling may indicate the RBs in each BWP by including an indication of the subbands in each BWP, the starting RB index of each subband, and the number of RBs in each subband. In some examples, the control signaling may indicate the RBs in each BWP by including a bitmap for each BWP, the bitmap indicating the RBs included in the BWP. In some examples, additional control signaling, such as a MAC-CE or DCI message, may update the RBs associated with one or more BWPs and / or subbands. The network entity 105 may configure the BWP time domain switching mode. For example, the network entity 105 may configure the communication to switch between SBFD mode and half-duplex mode according to the BWP time domain switching mode.

[0111] In some examples, the half-duplex UE 115 may be informed of the time and / or frequency resources of the subbands that the network entity 105 will use for SBFD operation. In some examples, the network entity 105 may inform the UE 115 of the time and / or frequency resources of the subbands that the network entity 105 will use for SBFD operation via BWP signaling (e.g., non-continuous downlink BWP and uplink BWP switching). In some examples, the network entity 105 may inform the UE 115 of the time and / or frequency resources of the subbands that the network entity 105 will use for SBFD operation via a semi-static switching time pattern between SBFD and half-duplex symbols or time slots, via MAC-CE or RRC.

[0112] Figure 2Examples of multiplexing patterns 200, 201, and 202 that support non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure are illustrated. The multiplexing patterns 200, 201, and 202 may be implemented to implement or facilitate aspects of the wireless communication system 100. For example, the multiplexing patterns 200, 201, and 202 illustrate communications between the IAB node 104, the MT device 205, the DU 165, and the UE 115, which may be via Figure 1 Examples of corresponding devices are illustrated and described with reference to the figure. In some implementations, the multiplexing patterns 200, 201, and 202 can support one or more signaling-based mechanisms by which a first device (such as an IAB node 104 or another network entity 105) can inform a UE 115 which time and frequency resources are available for full-duplex communication.

[0113] In some systems, the network entity 105 or one or more TRPs or any combination thereof may communicate with the UE 115 (e.g., transmit to the UE, receive from the UE, output to transmit to the UE, obtain from the UE, or any combination thereof) according to a "baseline" non-full-duplex operation. In such systems, flexible TDD may be disabled at both the network entity 105 and the UE 115. Alternatively, the network entity 105 or one or more TRPs or any combination thereof may communicate with the UE 115 (e.g., transmit to the UE, receive from the UE, output to transmit to the UE, obtain from the UE, or any combination thereof) according to any one or more of various types of full-duplex. These types of full-duplex may involve full-duplex operation at the UE 115 or at the network entity 105 (optionally via one or more TRPs), or at both.

[0114] In a first example type of full-duplex, the UE 115 may communicate with a first TRP (such as TRP 1) via a downlink (so that TRP 1 sends signaling to the UE 115) and the UE 115 may communicate with a second TRP (such as TRP 2) via an uplink (so that the UE 115 sends signaling to TRP 2). In this first example type of full-duplex (which may be associated with an mTRP deployment), flexible TDD may be disabled at the network entity 105 and may be enabled at the UE 115. In a second example type of full-duplex, the network entity 105 may communicate with the first UE 115 via a downlink and may communicate with the second UE 115 via an uplink. In this second example type of full-duplex (which may be associated with an IAB deployment), flexible TDD may be enabled at the network entity 105 and may be disabled at the first and second UEs 115. In a third example type of full-duplex, the network entity 105 may communicate with the UE 115 via both a downlink and an uplink. In this third example type of full-duplex, flexible TDD may be enabled at both the network entity 105 and the UE 115 .

[0115] In addition, one or more network entities 105 or one or more TRPs, or any combination thereof, may communicate with one or more UEs 115 (e.g., transmit to, receive from, output to transmit to, obtain from, or any combination thereof) according to one or more of various deployment scenarios utilizing a type of full-duplex. In a first deployment scenario, a full-duplex network entity 105 (e.g., such as via Figure 1 140) illustrated and described with reference to the figure may communicate with multiple half-duplex UEs 115. For example, a first network entity 105 may send downlink signaling to a first UE 115 and may simultaneously receive uplink signaling from a second UE 115. A second network entity 105 may send downlink signaling to a third UE 115 and may simultaneously receive uplink signaling from a fourth UE 115. In such a deployment scenario, cross-link interference (CLI) may occur between the various communicating devices (where uplink signaling may interfere with downlink signaling), and each of the two full-duplex network entities 105 may experience a certain amount of self-interference.

[0116] In a second deployment scenario, a full-duplex network entity 105 may communicate with a full-duplex UE 115, such as a full-duplex customer premises equipment (CPE). For example, the full-duplex network entity 105 may send downlink signaling to the full-duplex UE 115 and simultaneously receive uplink signaling from the full-duplex UE 115. In some aspects, the full-duplex network entity 105 may also send downlink signaling to another UE 115, such as a half-duplex UE 115, and in such aspects, CLI may occur between the two UEs 115. In addition, the full-duplex network entity 105 may experience CLI from the other network entity 105, and both the full-duplex network entity 105 and the full-duplex UE 115 may experience self-interference.

[0117] In a third deployment scenario, a half-duplex network entity 105 or TRP (such as in an mTRP deployment) may communicate with a full-duplex UE 115 (such as a full-duplex CPE). For example, a first network entity 105 or TRP may send downlink signaling to a full-duplex UE 115, and the full-duplex UE 115 may simultaneously send uplink signaling to a second network entity 105 or TRP. In some aspects, the first network entity 105 or TRP may also send downlink signaling to another UE 115 (such as a half-duplex UE 115), and in such aspects, CLI may occur between the two UEs 115. In addition, the two network entities 105 or TRPs may experience CLI, and the full-duplex UE 115 may experience self-interference.

[0118] In a fourth deployment scenario, a full-duplex IAB node may communicate with various UEs 115, such as half-duplex UEs 115. For example, an IAB node 104, such as an IAB donor or an IAB parent node, may control or operate multiple other IAB nodes 104, and one or more of the multiple IAB nodes 104 may support full-duplex operation. For example, the parent node may control or operate a first IAB node 104 capable of sending downlink signaling to a first UE 115 and simultaneously receiving uplink signaling from a second UE 115, and may control or operate a second IAB node 104 capable of sending downlink signaling to a third UE 115 and simultaneously receiving uplink signaling from a fourth UE 115. In such a deployment, the first and second IAB nodes 104 may experience CLI or self-interference from each other, or both. In some aspects, the IAB node 104 may support conditional duplex capability. Additionally or alternatively, the IAB node 104 may support single frequency full duplex and FDM or space division multiplexing (SDM) with RB group (RBG) granularity.

[0119] In some aspects, the network entity 105, one or more TRPs, and the UE 115 may support various evaluation techniques and performance evaluation metrics associated with different deployment scenarios for full-duplex operation (such as for NR duplex). In addition, the network entity 105, one or more TRPs, and the UE 115 may support one or more technologies to support coexistence with other systems in any co-channel or adjacent channel for sub-band non-overlapping full-duplex operation or for dynamic or flexible TDD or for both. For example, the network entity 105, one or more TRPs, and the UE 115 may support technologies associated with the evolution of duplex operation for NR TDD across various spectrums (including in unpaired spectrum). In such examples, the network entity 105 (via one or more TRPs) may support full-duplex operation, the UE 115 may support half-duplex operation, and the network entity 105 and the UE 115 may be configured or expected to have no restrictions on which frequency ranges are available for use.

[0120] Such techniques may include various full-duplex types or schemes and corresponding metrics for evaluating the performance of such full-duplex types or schemes, inter-network entity 105 and inter-UE 115 CLI mitigation techniques, intra-subband CLI and inter-subband CLI mitigation techniques (such as in a specific implementation of sub-band non-overlapping full-duplex), or a metric-based assessment procedure for the impact of full-duplex operation on half-duplex operation (assuming coexistence in co-channel and adjacent channels). Additionally or alternatively, such techniques may include a metric-based assessment procedure for considering the impact of adjacent channel coexistence on RF constraints or for considering the impact of self-interference, inter-subband CLI and inter-operator CLI at the network entity 105, and inter-subband CLI and inter-operator CLI at the UE 115 on RF constraints. In addition, such techniques may include antenna or RF and algorithm design for interference mitigation, including antenna isolation, transmit interference management suppression on the receive side, filtering, and digital interference suppression. In addition, such techniques may comply with one or more regulatory or network specifications associated with full-duplex operation in TDD unpaired spectrum.

[0121] In some aspects, various devices within the system may support a signaling mechanism to inform the UE 115 of the time or frequency locations of subbands that the network entity 105 may use for full-duplex operation (such as for SBFD operation). In addition, the various devices may support specific resource allocations in symbols or time slots with subbands that the network entity 105 may use for full-duplex operation (such as for SBFD operation).

[0122] Multiplexing modes 200, 201, and 202 may support various types of resource management and various types of multiplexing. For example, multiplexing mode 200-a and multiplexing mode 200-b may exemplify TDM. Multiplexing mode 200-a may exemplify DU transmission and reception, and multiplexing mode 200-b may exemplify MT transmission and reception. In the examples of multiplexing mode 200-a and multiplexing mode 200-b, the MT downlink or uplink may use a first set of time domain resources, and the DU downlink or uplink may use a second set of (non-overlapping) time domain resources.

[0123] Multiplexing mode 201-a and multiplexing mode 201-b may illustrate SDM reception and SDM transmission, respectively. For example, multiplexing mode 201-a illustrates MT reception and DU reception (which may occur using overlapping or non-overlapping time or frequency resources), and multiplexing mode 201-b illustrates MT transmission and DU transmission (which may occur using overlapping or non-overlapping time or frequency resources). Multiplexing mode 202-a and multiplexing mode 202-b illustrate example full-duplex scenarios. For example, multiplexing mode 202-a illustrates MT transmission and DU reception (which may occur using overlapping or non-overlapping time or frequency resources), and multiplexing mode 202-b illustrates MT reception and DU transmission (which may occur using overlapping or non-overlapping time or frequency resources).

[0124] In any SDM or full-duplex scenario, communications may occur simultaneously or at different times and may occur using different frequency resources, using partially overlapping frequency resources, or using the same frequency resources. For example, various devices or components may transmit MT downlinks or uplinks and DU downlinks or uplinks using non-overlapping frequency resources (e.g., in an FDM scheme), using partially overlapping frequency resources, or using completely overlapping frequency resources. In addition, various devices or components may use any combination of MT downlinks or uplinks and DU downlinks or uplinks across different RB sets or different subbands. In addition, various devices or components may support switching between different configurations over time (e.g., slot by slot).

[0125] Figure 3 An example of a wireless communication system 300 that supports non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may include a UE 115-a, which may be an example of a UE 115 as described herein. The wireless communication system 300 may include a network entity 105-a, which may be an example of a network entity 105 as described herein.

[0126] UE 115-a may communicate with network entity 105-a using communication link 125-a, which may be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a may include a bidirectional link that enables both uplink and downlink communications. For example, UE 115-a may send uplink transmissions (such as uplink control signals or uplink data signals) to network entity 105-a using communication link 125-a, and network entity 105-a may send downlink transmissions (such as downlink control signals or downlink data signals) to UE 115-a using communication link 125-a.

[0127] The network entity 105-a and the UE 115-a may implement SBFD communication. For example, the UE 115-a may receive control signaling 310 from the network entity 105-a, the control signaling including an indication of a first BWP 330-a associated with a first communication direction (e.g., downlink) and a second BWP 330-b associated with a second communication direction (e.g., uplink). The first BWP 330-a includes a first subband 340-a and a second subband 340-b, the first subband includes a first group of RBs 320-a, and the second subband includes a second group of RBs 320-b. The first group of RBs 320-a and the second group of RBs 320-b are not continuous in the frequency domain. The second BWP 330-b includes a third group of RBs 320-c. The third group of RBs 320-c does not overlap with the first group of RBs 320-a and the second group of RBs 320-c. In some examples, the first guard band may include a fourth group of RBs 320-d between the first group of RBs 320-a and the third group of RBs 320-c, and the second guard band may include a fifth group of RBs 320-e between the second group of RBs 320-b and the third group of RBs 320-c. The control signaling 310-a may indicate that the SBFD mode including the first BWP 330-a and the second BWP 330-b is applied to a set of time resources 325-a (e.g., one or more symbols or time slots).

[0128] The network entity 105 - a and the UE 115 - a may exchange communications 315 in the SBFD mode via the first BWP 330 - a and the second BWP 330 - b .

[0129] In some examples, the control signaling 310 may be RRC signaling. In some examples, the control signaling 310 may include a BWP information element (IE) indicating RBs associated with a downlink BWP (e.g., a first BWP 330-a) and an uplink BWP (e.g., a second BWP 330-b). For example, the control signaling 310 may include an IE for each of the first BWP 330-a and the second BWP 330-b, the IE indicating an array of RBs included in the corresponding BWP. For example, the IE locationAndBandwidth may indicate a frequency domain location and bandwidth of the BWP. Another IE may indicate an identifier (ID) for the BWP. The value of the IElocationAndBandwidth may be interpreted as a resource indicator value (RIV) indicating a starting RB index of a set of candidate RBs and a size of the BWP in RBs (e.g., the size of the BWP is 275 physical RBs (PRBs)). Another IE may indicate a subcarrier spacing (SCS) of the BWP. The first PRB may be determined by the RIV, the SCS of the BWP, and another IEoffsetToCarrier.The control signaling 310 may indicate the communication direction (eg, uplink or downlink) of each BWP (eg, the first BWP 330-a and the second BWP 330-b).

[0130] The half-duplex configuration may include a third BWP 330-c for downlink and a fourth BWP 330-d for uplink, the third BWP including the first group of RBs 320-a, the second group of RBs 320-b, the third group of RBs 320-c, the fourth group of RBs 320-d, and the fifth group of RBs 320-e, and the fourth BWP including the first group of RBs 320-a, the second group of RBs 320-b, the third group of RBs 320-c, the fourth group of RBs 320-d, and the fifth group of RBs 320-e. In the half-duplex configuration, the UE 115-a and the network entity 105-a may switch between the third BWP 330-c and the fourth BWP 330-d. For the half-duplex configuration, the BWP pair (e.g., the third BWP 330-c and the fourth BWP 330-d) has the same BWP ID and the same center frequency.

[0131] For SBFD configuration, the IE locationAndBandwidth-LIST may include an array indicating multiple values ​​that can be used to determine the RBs in the BWP. For example, the IE locationAndBandwidth-LIST for the first BWP 330-a may include two values ​​that can be interpreted as indicating the RIVs of the first group of RBs 320-a and the second group of RBs 320-b. The IE locationAndBandwidth-LIST for the second BWP 330-b may include one value that can be interpreted as indicating the RIV of the third group of RBs 320-c.

[0132] In some cases, the first BWP 330-a and the second BWP 330-b may have the same BWP identifier even though the first BWP 330-a and the second BWP 330-b may have different center frequencies. In some cases, the first BWP 330-a and the second BWP 330-b may have different IDs (eg, an activated SBFD BWP pair may have different IDs).

[0133] In some cases, for a non-contiguous BWP, the control signaling 310 may include a first IE locationAndBandwidth indicating a first group of RBs for a first subband of the BWP (e.g., the first group of RBs 320-a), and may include an additional IE AdditionallocationAndBandwidth for an additional subband indicating an additional group of RBs for the additional subband. For example, the IE locationAndBandwidth and AdditionallocationAndBandwidth may indicate respective starting RB indices and sizes in RBs for respective subbands. For example, for the first BWP 330-a, the control signaling 310 may include: an IE locationAndBandwidth indicating a first group of RBs 320-a for a first subband 340-a; and an IE AdditionallocationAndBandwidth indicating a second group of RBs 320-b for a second subband 340-b. The control signaling 310 may include an IE locationAndBandwidth for a second BWP 330-b indicating a third group of RBs 320-c.

[0134] As described herein, in some cases, the first BWP 330-a and the second BWP 330-b may have the same BWP identifier even though the first BWP 330-a and the second BWP 330-b may have different center frequencies. In some cases, the first BWP 330-a and the second BWP 330-b may have different IDs (e.g., an activated SBFD BWP pair may have different IDs).

[0135] In some cases, for each BWP (e.g., a first BWP 330-a and a second BWP 330-b), the control signaling 310 may include a bitmap indicating the RBs included within the corresponding BWP. For example, the control signaling 310 may include a bitmap for the first BWP 330-a indicating that the first BWP 330-a includes a first group of RBs 320-a and a second group of RBs 320-b. The control signaling 310 may include a bitmap for the second BWP 330-b indicating that the second BWP 330-b includes a third group of RBs 320-c. The bitmap may be mapped for each RB (e.g., of the 275 candidate RBs), or may be mapped for a subset of the 275 candidate RBs to save bit overhead. As described herein, in some cases, the first BWP 330-a and the second BWP 330-b may have the same BWP identifier even though the first BWP 330-a and the second BWP 330-b may have different center frequencies. In some cases, the first BWP 330-a and the second BWP 330-b may have different IDs (e.g., an activated SBFD BWP pair may have different IDs).

[0136] The fourth group of RBs 320 - d and the fifth group of RBs 320 - e may not be assigned to the first BWP 330 - a or the second BWP 330 - b in order to be used as guard bands.

[0137] In some cases, the control signaling 310 may indicate a plurality (eg, a number N) of BWPs including contiguous BWPs and non-contiguous BWPs (eg, for SBFD mode).

[0138] In some examples, the network entity 105-a may configure one BWP corresponding to one subband configuration via control signaling 310. For example, the control signaling 310 may configure only the first BWP 330-a and the second BWP 330-b for SBFD mode. The network entity 105-a may indicate an update to the BWP configuration via additional control signaling 345 (e.g., via a MAC-CE or DCI message). For example, the additional control signaling 345 may indicate an updated RB allocation for the first BWP 330-a and / or the second BWP 330-b (e.g., using the same ID for the first BWP 330-a and the second BWP 330-b).

[0139] As another example, the control signaling 310 may configure multiple BWPs (eg, multiple BWP IDs and associated RB groups) corresponding to multiple subband configurations. The network entity 105-a may switch the active BWP for the UE 115-a via BWP switching signaling (eg, via indicating an ID for a different BWP).

[0140] In some examples, the network entity 105-a may update the RBs for the first BWP 330-a and / or the second BWP 330-b via additional control signaling 345 (e.g., a MAC-CE or DCI message). For example, the additional control signaling 345 may include the same IE indicating the BWP and the RBs included within the BWP. Thus, the additional control signaling 345 may update the RBs for the BWP by indicating that the ID of the BWP is being updated and including an updated value for the IE indicating the RBs for the BWP. In some examples, the additional control signaling 345 may indicate a different BWP ID for the active BWP, and accordingly the UE 115-a and the network entity 105-a may switch to a BWP corresponding to the new identifier BWP ID. For example, the additional control signaling 345 indicating the different BWP IDs may be DCI format 1_1, DCI format 1_2, DCI format 0_1, or DCI format 0_2.

[0141] In some cases, the control signaling 310 (e.g., RRC signaling or MAC-CE) may indicate a time domain BWP switching pattern (e.g., a semi-static switching pattern) between SBFD symbols / time slots and half-duplex symbols / time slots. For example, the control signaling 310 may instruct the UE 115-a to communicate with the network entity 105-a in SBFD mode using the first BWP 330-a and the second BWP 330-b during the first set of time resources 325-a, and instruct the UE to communicate with the network entity 105-a in half-duplex mode using the third BWP 330-c and the fourth BWP 330-d during the second set of time resources 325-b and the third set of time resources 325-c. For example, UE 115-a may receive downlink communications from network entity 105-a via third BWP 330-c during second set of time resources 325-b, and UE 115-a may send uplink communications to network entity 105-a via fourth BWP 330-d during third set of time resources 325-c. The switching pattern may be repeated periodically. Control signaling 310 may indicate gap periods (e.g., time gap 335-a and time gap 335-b) between groups of time resources corresponding to BWP switching. For example, gap periods (e.g., time gap 335-a and time gap 335-b) may include multiple symbols or time slots, depending on the filter tuning delay of UE 115-a.

[0142] In some cases, the time domain BWP switching pattern may be linked to the corresponding BWP ID. For example, the control signaling 310 may indicate the RB groups associated with different BWP IDs, and then may indicate which BWP IDs are associated with which time resources (e.g., the first group of time resources 325-a, the second group of time resources 325-b, and the third group of time resources 325-c). In some cases, the time domain BWP switching pattern may be indicated via a bitmap or a periodic pattern. In some cases, the RRC signaling (e.g., the control signaling 310) may pre-configure multiple time domain switching patterns, and the MAC-CE or DCI message (e.g., the additional control signaling 345) may select one of the pre-configured time domain BWP switching patterns.

[0143] Figure 4 An example of a time domain BWP switching pattern 400 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated. The time domain BWP switching pattern 400 may implement aspects of the wireless communication system 100 or the wireless communication system 300.

[0144] The time domain BWP switching pattern 400 may be used for communication between a network entity 105 and a UE 115-a that may implement SBFD communication. For example, the UE 115 may receive control signaling including an indication of a first BWP 430-a, a second BWP 430-b, a third BWP 430-c, a fourth BWP 430-d, and a fifth BWP 430-e from the network entity 105. The control signaling may indicate that the first BWP 430-a is used for a downlink and includes a non-contiguous first group of RBs 410-a and a second group of RBs 410-b. Accordingly, the first BWP 430-a includes a first subband 440-a and a second subband 440-b. The control signaling may indicate that the second BWP 430-b is used for an uplink and includes a third group of RBs 410-c. The fourth group of RBs 410-d may form a guard band between the first group of RBs 410-a and the third group of RBs 410-c, and the fifth group of RBs 410-e may form a guard band between the second group of RBs 410-b and the third group of RBs 410-c. The control signaling may indicate that the second BWP 430-b is used for uplink and includes the first group of RBs 410-a, the second group of RBs 410-b, the third group of RBs 410-c, the fourth group of RBs 410-d, and the fifth group of RBs 410-e. The control signaling may indicate that the fourth BWP 430-d is used for downlink and includes the sixth group of RBs 410-f. The control signaling may indicate that the fifth BWP 430-e is used for uplink and includes the seventh group of RBs 410-g. The eighth group of RBs 410-h may form a guard band between the sixth group of RBs 410-f and the seventh group of RBs 410-g.

[0145] The control signaling may indicate that the first BWP 430-a and the second BWP 430-b are used for communication between the UE 115 and the network entity 105 during the first set of time resources 415-a (e.g., in SBFD mode). The control signaling may indicate that the third BWP 430-c is used for communication between the UE 115 and the network entity 105 during the second set of time resources 415-b (e.g., in half-duplex mode). The control signaling may indicate that the fourth BWP 430-d and the fifth BWP 430-e are used for communication between the UE 115 and the network entity 105 during the third set of time resources 415-c (e.g., in full-duplex mode). The time domain BWP switching pattern 400 may be repeated periodically. The control signaling may indicate the gap period (e.g., time gap 420-a and time gap 420-b) between the time resource groups corresponding to the BWP switching. For example, the gap period (eg, time gap 420 - a and time gap 420 - b ) may include multiple symbols or time slots, depending on the filter tuning delay of UE 115 .

[0146] Figure 5An example of a process flow 500 for supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is illustrated. The process flow 500 may include a UE 115-b, which may be an example of a UE 115 as described herein. The process flow 500 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 500, operations between the network entity 105-b and the UE 115-b may be sent in an order different from the example order shown, or operations performed by the network entity 105-b and the UE 115-b may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 500, and other operations may be added to the process flow 500.

[0147] At 505, UE 115-b may receive control signaling (e.g., RRC signaling) from network entity 105-b, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that does not overlap with the first group of RBs and the second group of RBs in the frequency domain.

[0148] At 510 , the UE 115 - b may communicate with the network entity in a SBFD mode in a first communication direction via a first BWP and in a second communication direction via a second BWP.

[0149] In some examples, receiving control signaling includes: receiving an indication of a first identifier associated with a first BWP; receiving an indication that the first BWP is associated with a first communication direction; and, for the first BWP, receiving an indication of a first group of RBs and a second group of RBs from a set of multiple RBs associated with at least one carrier bandwidth including the first BWP. In some examples, receiving control signaling also includes: receiving an indication of a second identifier associated with a second BWP; receiving an indication that the second BWP is associated with a second communication direction; and, for the second BWP, receiving an indication of a third group of RBs from the set of multiple RBs. In some examples, the first identifier is equal to the second identifier. In some examples, the first identifier is different from the second identifier.

[0150] In some examples, receiving control signaling includes: receiving an indication of a first identifier associated with a first BWP; receiving an indication that the first BWP is associated with a first communication direction; for a first subband, receiving an indication of a starting RB index of a first group of RBs and a size of the first group of RBs in RBs; and for a second subband, receiving an indication of a starting RB index of a second group of RBs and a size of the second group of RBs in RBs. In some examples, receiving control signaling also includes: receiving an indication of a second identifier associated with a second BWP; receiving an indication that the second BWP is associated with the first communication direction; and for the second BWP, receiving an indication of a starting RB index of a third group of RBs and a size of the third group of RBs in RBs. In some examples, the first identifier is equal to the second identifier. In some examples, the first identifier is different from the second identifier.

[0151] In some examples, receiving control signaling includes: receiving an indication of a first identifier associated with a first BWP; receiving an indication that the first BWP is associated with a first communication direction; and receiving a bitmap for the first BWP indicating a first group of RBs and a second group of RBs. In some examples, receiving control signaling also includes: receiving an indication of a second identifier associated with the first BWP; receiving an indication that the second BWP is associated with a second communication direction; and receiving a second bitmap for the second BWP indicating a third group of RBs. In some examples, the first identifier is equal to the second identifier. In some examples, the first identifier is different from the second identifier.

[0152] In some examples, UE 115-b may also receive second control signaling (e.g., RRC signaling) from network entity 105-b indicating a group of BWPs, the group of BWPs including a first subgroup of BWPs associated with non-contiguous RBs and a second subgroup of BWPs associated with contiguous RBs, the first subgroup of BWPs including a first BWP and a second BWP, and wherein receiving the control signaling includes receiving an indication that a group of time slots are associated with the first BWP and the second BWP. In some examples, UE 115-b may also receive third control signaling (e.g., a MAC-CE or DCI message) from network entity 105-b, the third control signaling updating RBs associated with at least one of the first BWP, the second BWP, a third BWP of the second subgroup of BWPs, or a fourth BWP of the second subgroup of BWPs, wherein the third BWP is associated with a first communication direction and wherein the fourth BWP is associated with a second communication direction, wherein the first subgroup of BWPs includes only the first BWP and the second BWP, and wherein the second subgroup of BWPs includes only the third BWP and the fourth BWP. In some examples, UE 115 - b may also receive third control signaling (eg, a DCI message) from network entity 105 - b indicating another selected BWP from the set of BWPs for the second set of time slots.

[0153] In some examples, UE 115-b may also receive second control signaling (e.g., MAC-CE, DCI message, or subsequent RRC signaling) from network entity 105-b to update RBs included in the first group of RBs, RBs included in the second group of RBs, RBs included in the third group of RBs, or a combination thereof.

[0154] In some examples, receiving control signaling includes: receiving an indication of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including a first BWP and a second BWP, the second BWP configuration including a third BWP associated with a first communication direction and a fourth BWP associated with a second communication direction, wherein the control signaling also includes an indication of a time domain switching pattern between the first BWP configuration and the second BWP configuration. In some examples, the time domain switching pattern includes a time gap between one or more time slots associated with the first BWP configuration and one or more time slots associated with the second BWP configuration.

[0155] In some examples, the first guard band is located between the first group of RBs and the third group of RBs in the frequency domain, and the second guard band is located between the third group of RBs and the second group of RBs in the frequency domain.

[0156] Figure 6 A block diagram 600 of a device 605 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0157] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with non-contiguous RBs for BWP configuration), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

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

[0159] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of non-contiguous RBs for BWP configuration as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

[0162] In some examples, communication manager 620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0163] According to examples as disclosed herein, the communication manager 620 may support wireless communication at the UE. For example, the communication manager 620 may be configured to or otherwise support components for receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The communication manager 620 may be configured to or otherwise support components for communicating with the network entity in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0164] By including or configuring a communication manager 620 according to examples as described herein, a device 605 (eg, a processor controlling or otherwise coupled with a receiver 610, a transmitter 615, a communication manager 620, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0165] Figure 7 A block diagram 700 of a device 705 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0166] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with non-contiguous RBs for BWP configuration), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0167] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with non-contiguous RBs for BWP configuration). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0168] The device 705 or its various components may be examples of components for performing various aspects of non-contiguous RBs for BWP configuration as described herein. For example, the communication manager 720 may include a BWP configuration manager 725, a SBFD communication manager 730, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0169] According to examples as disclosed herein, the communication manager 720 may support wireless communication at the UE. The BWP configuration manager 725 may be configured to or otherwise support components for receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The SBFD communication manager 730 may be configured to or otherwise support components for communicating with the network entity in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0170] Figure 8 A block diagram 800 of a communication manager 820 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of non-contiguous RBs for BWP configuration as described herein. For example, the communication manager 820 may include a BWP configuration manager 825, a SBFD communication manager 830, a BWP identifier manager 835, a BWP direction manager 840, a BWP RB manager 845, a BWPRB bitmap manager 850, a BWP switching manager 855, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0171] According to examples as disclosed herein, the communication manager 820 may support wireless communication at the UE. The BWP configuration manager 825 may be configured to or otherwise support components for receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The SBFD communication manager 830 may be configured to or otherwise support components for communicating with the network entity in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0172] In some examples, to support receiving control signaling, the BWP identifier manager 835 may be configured or otherwise support components for receiving an indication of a first identifier associated with a first BWP. In some examples, to support receiving control signaling, the BWP direction manager 840 may be configured or otherwise support components for receiving an indication that the first BWP is associated with a first communication direction. In some examples, to support receiving control signaling, the BWP RB manager 845 may be configured or otherwise support components for: receiving, for a first BWP, an indication of a first group of RBs and a second group of RBs from a group of a plurality of RBs associated with at least one carrier bandwidth including the first BWP.

[0173] In some examples, to support receiving control signaling, the BWP identifier manager 835 may be configured or otherwise support means for receiving an indication of a second identifier associated with a second BWP. In some examples, to support receiving control signaling, the BWP direction manager 840 may be configured or otherwise support means for receiving an indication that the second BWP is associated with a second communication direction. In some examples, to support receiving control signaling, the BWP RB manager 845 may be configured or otherwise support means for receiving, for the second BWP, an indication of a third group of RBs from the group of multiple RBs.

[0174] In some examples, the first identifier is equal to the second identifier.

[0175] In some examples, the first identifier is different from the second identifier.

[0176] In some examples, to support receiving control signaling, the BWP identifier manager 835 may be configured or otherwise support components for receiving an indication of a first identifier associated with a first BWP. In some examples, to support receiving control signaling, the BWP direction manager 840 may be configured or otherwise support components for receiving an indication that the first BWP is associated with a first communication direction. In some examples, to support receiving control signaling, the BWP RB manager 845 may be configured or otherwise support components for: for a first subband, receiving an indication of a starting RB index of a first group of RBs and a size of the first group of RBs in RBs. In some examples, to support receiving control signaling, the BWP RB manager 845 may be configured or otherwise support components for: for a second subband, receiving an indication of a starting RB index of a second group of RBs and a size of the second group of RBs in RBs.

[0177] In some examples, to support receiving control signaling, the BWP identifier manager 835 may be configured or otherwise support means for receiving an indication of a second identifier associated with a second BWP. In some examples, to support receiving control signaling, the BWP direction manager 840 may be configured or otherwise support means for receiving an indication that the second BWP is associated with the first communication direction. In some examples, to support receiving control signaling, the BWP RB manager 845 may be configured or otherwise support means for receiving, for the second BWP, an indication of a starting RB index of a third group of RBs and a size in RBs of the third group of RBs.

[0178] In some examples, to support receiving control signaling, the BWP identifier manager 835 may be configured or otherwise support means for receiving an indication of a first identifier associated with a first BWP. In some examples, to support receiving control signaling, the BWP direction manager 840 may be configured or otherwise support means for receiving an indication that the first BWP is associated with a first communication direction. In some examples, to support receiving control signaling, the BWP RB bitmap manager 850 may be configured or otherwise support means for receiving a bitmap indicating a first group of RBs and a second group of RBs for the first BWP.

[0179] In some examples, to support receiving control signaling, the BWP identifier manager 835 may be configured or otherwise support means for receiving an indication of a second identifier associated with the first BWP. In some examples, to support receiving control signaling, the BWP direction manager 840 may be configured or otherwise support means for receiving an indication that the second BWP is associated with a second communication direction. In some examples, to support receiving control signaling, the BWP RB bitmap manager 850 may be configured or otherwise support means for receiving a second bitmap indicating a third group of RBs for the second BWP.

[0180] In some examples, the BWP configuration manager 825 may be configured to or otherwise support components for receiving a second control signaling indicating a group of BWPs, the group of BWPs including a first sub-group of BWPs associated with non-contiguous RBs and a second sub-group of BWPs associated with contiguous RBs, the first sub-group of BWPs including a first BWP and a second BWP, and wherein receiving the control signaling includes receiving an indication that a group of time slots are associated with the first BWP and the second BWP.

[0181] In some examples, the BWP configuration manager 825 may be configured to or otherwise support components for receiving third control signaling that updates an RB associated with at least one of a first BWP, a second BWP, a third BWP of a second subgroup of BWPs, or a fourth BWP of the second subgroup of BWPs, wherein the third BWP is associated with a first communication direction and wherein the fourth BWP is associated with a second communication direction, wherein the first subgroup of BWPs includes only the first BWP and the second BWP, and wherein the second subgroup of BWPs includes only the third BWP and the fourth BWP.

[0182] In some examples, the BWP configuration manager 825 may be configured or otherwise support means for receiving third control signaling indicating another selected BWP from the set of BWPs for the second set of time slots.

[0183] In some examples, the BWP RB manager 845 may be configured or otherwise support components for receiving second control signaling that updates RBs included in the first group of RBs, RBs included in the second group of RBs, RBs included in the third group of RBs, or a combination thereof.

[0184] In some examples, to support receiving control signaling, the BWP switching manager 855 may be configured as or otherwise support components for receiving indications of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including a first BWP and a second BWP, the second BWP configuration including a third BWP associated with a first communication direction and a fourth BWP associated with a second communication direction, wherein the control signaling also includes an indication of a time domain switching pattern between the first BWP configuration and the second BWP configuration.

[0185] In some examples, the time domain switching pattern includes a time gap between one or more time slots associated with the first BWP configuration and one or more time slots associated with the second BWP configuration.

[0186] In some examples, the first guard band is located between the first group of RBs and the third group of RBs in the frequency domain. In some examples, the second guard band is located between the third group of RBs and the second group of RBs in the frequency domain.

[0187] Fig. 9 A diagram of a system 900 including a device 905 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein, or include components thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0188] I / O controller 910 may manage input and output signals for device 905. I / O controller 910 may also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 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, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0189] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired or wireless link, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

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

[0191] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks that support non-contiguous RBs for BWP configuration). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0192] According to examples as disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support components for receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The communication manager 920 may be configured to or otherwise support components for communicating with the network entity in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0193] By including or configuring according to an example communication manager 920 as described herein, the device 905 can support techniques for more efficiently utilizing communication resources and improving coordination between devices.

[0194] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of non-contiguous RBs for BWP configuration as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0195] Fig.10 A block diagram 1000 of a device 1005 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0198] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of non-contiguous RBs for BWP configuration as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0199] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

[0201] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0202] According to examples as disclosed herein, the communication manager 1020 may support wireless communication at a network entity. For example, the communication manager 1020 may be configured to or otherwise support components for outputting control signaling, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The communication manager 1020 may be configured to or otherwise support components for communicating in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0203] By including or configuring a communication manager 1020 according to examples as described herein, a device 1005 (eg, a processor controlling or otherwise coupled with a receiver 1010, a transmitter 1015, a communication manager 1020, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0204] Fig.11 A block diagram 1100 of a device 1105 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0207] The device 1105 or its various components may be examples of components for performing various aspects of non-contiguous RBs for BWP configuration as described herein. For example, the communication manager 1120 may include a BWP configuration manager 1125, a SBFD communication manager 1130, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0208] According to examples as disclosed herein, the communication manager 1120 may support wireless communication at a network entity. The BWP configuration manager 1125 may be configured to or otherwise support components for outputting control signaling, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The SBFD communication manager 1130 may be configured to or otherwise support components for communicating in SBFD mode in a first communication direction via a first BWP and in a second communication direction via a second BWP.

[0209] Fig.12A block diagram 1200 of a communication manager 1220 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of non-contiguous RBs for BWP configuration as described herein. For example, the communication manager 1220 may include a BWP configuration manager 1225, a SBFD communication manager 1230, a BWP identifier manager 1235, a BWP direction manager 1240, a BWP RB manager 1245, a BWP RB bitmap manager 1250, a BWP switch manager 1255, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0210] According to examples as disclosed herein, the communication manager 1220 may support wireless communication at a network entity. The BWP configuration manager 1225 may be configured to or otherwise support components for outputting control signaling, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The SBFD communication manager 1230 may be configured to or otherwise support components for communicating in SBFD mode in a first communication direction via a first BWP and in a second communication direction via a second BWP.

[0211] In some examples, to support output control signaling, BWP identifier manager 1235 may be configured or otherwise support components for outputting an indication of a first identifier associated with a first BWP. In some examples, to support output control signaling, BWP direction manager 1240 may be configured or otherwise support components for outputting an indication that the first BWP is associated with a first communication direction. In some examples, to support output control signaling, BWP RB manager 1245 may be configured or otherwise support components for: outputting, for a first BWP, an indication of a first group of RBs and a second group of RBs from a group of a plurality of RBs associated with at least one carrier bandwidth including the first BWP.

[0212] In some examples, to support output control signaling, BWP identifier manager 1235 may be configured or otherwise support components for outputting an indication of a second identifier associated with a second BWP. In some examples, to support output control signaling, BWP direction manager 1240 may be configured or otherwise support components for outputting an indication that the second BWP is associated with a second communication direction. In some examples, to support output control signaling, BWP RB manager 1245 may be configured or otherwise support components for: outputting, for the second BWP, an indication of a third group of RBs from the group of multiple RBs.

[0213] In some examples, the first identifier is equal to the second identifier.

[0214] In some examples, the first identifier is different from the second identifier.

[0215] In some examples, to support output control signaling, the BWP identifier manager 1235 may be configured or otherwise support components for outputting an indication of a first identifier associated with a first BWP. In some examples, to support output control signaling, the BWP direction manager 1240 may be configured or otherwise support components for outputting an indication that the first BWP is associated with a first communication direction. In some examples, to support output control signaling, the BWP RB manager 1245 may be configured or otherwise support components for: for a first subband, outputting an indication of a starting RB index of a first group of RBs and a size of the first group of RBs in RBs. In some examples, to support output control signaling, the BWP RB manager 1245 may be configured or otherwise support components for: for a second subband, outputting an indication of a starting RB index of a second group of RBs and a size of the second group of RBs in RBs.

[0216] In some examples, to support output control signaling, BWP identifier manager 1235 may be configured or otherwise support components for outputting an indication of a second identifier associated with a second BWP. In some examples, to support output control signaling, BWP direction manager 1240 may be configured or otherwise support components for outputting an indication that the second BWP is associated with the first communication direction. In some examples, to support output control signaling, BWP RB manager 1245 may be configured or otherwise support components for: outputting, for the second BWP, an indication of a starting RB index of a third group of RBs and a size in RBs of the third group of RBs.

[0217] In some examples, to support output control signaling, BWP identifier manager 1235 may be configured or otherwise support means for outputting an indication of a first identifier associated with a first BWP. In some examples, to support output control signaling, BWP direction manager 1240 may be configured or otherwise support means for outputting an indication that the first BWP is associated with a first communication direction. In some examples, to support output control signaling, BWP RB bitmap manager 1250 may be configured or otherwise support means for outputting a bitmap indicating a first set of RBs and a second set of RBs for a first BWP.

[0218] In some examples, to support output control signaling, BWP identifier manager 1235 may be configured or otherwise support means for outputting an indication of a second identifier associated with a first BWP. In some examples, to support output control signaling, BWP direction manager 1240 may be configured or otherwise support means for outputting an indication that a second BWP is associated with a second communication direction. In some examples, to support output control signaling, BWP RB bitmap manager 1250 may be configured or otherwise support means for outputting a second bitmap indicating a third group of RBs for a second BWP.

[0219] In some examples, the BWP configuration manager 1225 may be configured to or otherwise support components for outputting a second control signaling indicating a group of BWPs, the group of BWPs including a first sub-group BWP associated with non-contiguous RBs and a second sub-group BWP associated with contiguous RBs, the first sub-group BWP including a first BWP and a second BWP, and wherein receiving the control signaling includes receiving an indication that a group of time slots are associated with the first BWP and the second BWP.

[0220] In some examples, the BWP configuration manager 1225 may be configured to or otherwise support components for outputting third control signaling that updates an RB associated with at least one of a first BWP, a second BWP, a third BWP of a second subgroup BWP, or a fourth BWP of the second subgroup BWP, wherein the third BWP is associated with a first communication direction and wherein the fourth BWP is associated with a second communication direction, wherein the first subgroup BWP includes only the first BWP and the second BWP, and wherein the second subgroup BWP includes only the third BWP and the fourth BWP.

[0221] In some examples, the BWP configuration manager 1225 may be configured or otherwise support means for outputting third control signaling indicating another selected BWP from the set of BWPs for the second set of time slots.

[0222] In some examples, the BWP RB manager 1245 may be configured or otherwise support components for outputting second control signaling that updates RBs included in the first group of RBs, RBs included in the second group of RBs, RBs included in the third group of RBs, or a combination thereof.

[0223] In some examples, to support output control signaling, the BWP switching manager 1255 may be configured as or otherwise support components for outputting indications of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including a first BWP and a second BWP, the second BWP configuration including a third BWP associated with a first communication direction and a fourth BWP associated with a second communication direction, wherein the control signaling also includes an indication of a time domain switching pattern between the first BWP configuration and the second BWP configuration.

[0224] In some examples, the time domain switching pattern includes a time gap between one or more time slots associated with the first BWP configuration and one or more time slots associated with the second BWP configuration.

[0225] In some examples, the first guard band is located between the first group of RBs and the third group of RBs in the frequency domain. In some examples, the second guard band is located between the third group of RBs and the second group of RBs in the frequency domain.

[0226] Fig.13A diagram of a system 1300 including a device 1305 supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and receive communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0227] As described herein, the transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and for demodulating the signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform the following operations: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination of these operations. In some implementations, the transceiver 1310 or the transceiver 1310 and one or more antennas 1315 or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip component installed in the device 1305. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

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

[0229] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to enable the device 1305 to perform various functions (e.g., functions or tasks supporting non-contiguous RBs for BWP configuration). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 1330) to perform functions of the device 1305. The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as in the memory 1325). In some specific implementations, the processor 1335 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receives inputs and processes these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1305). For example, the processing system of the device 1305 may refer to a system including various other components or subcomponents of the device 1305, such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or other components or combinations of components of the device 1305. The processing system of the device 1305 may interface with other components of the device 1305, and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of the device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1305 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1305 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0230] In some examples, bus 1340 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

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

[0232] According to examples as disclosed herein, the communication manager 1320 may support wireless communication at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for outputting control signaling, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP includes a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The communication manager 1320 may be configured to or otherwise support components for communicating in SBFD mode in the first communication direction via the first BWP and in the second communication direction via the second BWP.

[0233] By including or configuring according to an example communication manager 1320 as described herein, the device 1305 can support techniques for more efficiently utilizing communication resources and improving coordination between devices.

[0234] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 can be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of non-contiguous RBs for BWP configuration as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0235] Fig.14 1400 is a flowchart illustrating a method 1400 for supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0236] At 1405, the method may include receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The BWP configuration manager 825 executes.

[0237] At 1410, the method may include communicating with a network entity in a SBFD mode in a first communication direction via a first BWP and in a second communication direction via a second BWP. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figure 8 The described SBFD communication manager 830 is executed.

[0238] Fig.15 1 is a flowchart illustrating a method 1500 for supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0239] At 1505, the method may include receiving control signaling from a network entity, the control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The BWP configuration manager 825 executes.

[0240] At 1510, the method may include receiving an indication of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including a first BWP and a second BWP, the second BWP configuration including a third BWP associated with a first communication direction and a fourth BWP associated with a second communication direction, wherein the control signaling further includes an indication of a time domain switching pattern between the first BWP configuration and the second BWP configuration. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The BWP switching manager 855 executes.

[0241] At 1515, the method may include communicating with the network entity in SBFD mode in a first communication direction via a first BWP and in a second communication direction via a second BWP. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Figure 8 The described SBFD communication manager 830 is executed.

[0242] Fig.16 1 is a flowchart illustrating a method 1600 for supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0243] At 1605, the method may include outputting control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.12 The BWP configuration manager 1225 executes.

[0244] At 1610, the method may include communicating in SBFD mode in a first communication direction via a first BWP and in a second communication direction via a second BWP. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Fig.12 The described SBFD communication manager 1230 is executed.

[0245] Fig.17 1 is a flowchart illustrating a method 1700 for supporting non-contiguous RBs for BWP configuration according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 as well as Figures 10 to 13In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0246] At 1705, the method may include outputting control signaling including an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP including a first subband and a second subband, the first subband including a first group of RBs, the second subband including a second group of RBs, wherein the first group of RBs and the second group of RBs are non-contiguous in the frequency domain, and the second BWP including a third group of RBs that do not overlap with the first group of RBs and the second group of RBs in the frequency domain. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The BWP configuration manager 1225 executes.

[0247] At 1710, the method may include outputting an indication of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including a first BWP and a second BWP, the second BWP configuration including a third BWP associated with a first communication direction and a fourth BWP associated with a second communication direction, wherein the control signaling further includes an indication of a time domain switching pattern between the first BWP configuration and the second BWP configuration. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The BWP switching manager 1255 executes.

[0248] At 1715, the method may include communicating in SBFD mode in a first communication direction via a first BWP and in a second communication direction via a second BWP. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Fig.12 The described SBFD communication manager 1230 is executed.

[0249] The following provides an overview of various aspects of the disclosure:

[0250] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving control signaling from a network entity, the control signaling comprising an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP comprising a first subband and a second subband, the first subband comprising a first group of RBs, the second subband comprising a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in a frequency domain, and the second BWP comprises a third group of RBs that does not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicating with the network entity in SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0251] Aspect 2: A method according to Aspect 1, wherein receiving the control signaling includes: receiving an indication of a first identifier associated with the first BWP; receiving an indication that the first BWP is associated with the first communication direction; and, for the first BWP, receiving an indication of the first group of RBs and the second group of RBs from a group of multiple RBs associated with at least one carrier bandwidth including the first BWP.

[0252] Aspect 3: A method according to Aspect 2, wherein receiving the control signaling includes: receiving an indication of a second identifier associated with the second BWP; receiving an indication that the second BWP is associated with the second communication direction; and for the second BWP, receiving an indication of the third group of RBs from the multiple RBs.

[0253] Aspect 4: The method according to aspect 3, wherein the first identifier is equal to the second identifier.

[0254] Aspect 5: The method according to any one of aspects 3 to 4, wherein the first identifier is different from the second identifier.

[0255] Aspect 6: A method according to Aspect 1, wherein receiving the control signaling includes: receiving an indication of a first identifier associated with the first BWP; receiving an indication that the first BWP is associated with the first communication direction; for the first subband, receiving an indication of the starting RB index of the first group of RBs and the size of the first group of RBs in RBs; and for the second subband, receiving an indication of the starting RB index of the second group of RBs and the size of the second group of RBs in RBs.

[0256] Aspect 7: A method according to Aspect 6, wherein receiving the control signaling includes: receiving an indication of a second identifier associated with the second BWP; receiving an indication that the second BWP is associated with the first communication direction; and for the second BWP, receiving an indication of a starting RB index of the third group of RBs and a size of the third group of RBs in RBs.

[0257] Aspect 8: A method according to Aspect 1, wherein receiving the control signaling includes: receiving an indication of a first identifier associated with the first BWP; receiving an indication that the first BWP is associated with the first communication direction; and receiving a bitmap indicating the first group of RBs and the second group of RBs for the first BWP.

[0258] Aspect 9: A method according to Aspect 8, wherein receiving the control signaling includes: receiving an indication of a second identifier associated with the first BWP; receiving an indication that the second BWP is associated with the second communication direction; and receiving a second bitmap indicating the third group of RBs for the second BWP.

[0259] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: receiving a second control signaling indicating a group of BWPs, the group of BWPs including a first sub-group BWP associated with non-contiguous RBs and a second sub-group BWP associated with contiguous RBs, the first sub-group BWP including the first BWP and the second BWP, and wherein receiving the control signaling includes receiving an indication that a group of time slots are associated with the first BWP and the second BWP.

[0260] Aspect 11: The method according to Aspect 10 also includes: receiving a third control signaling, wherein the third control signaling updates the RB associated with at least one of the first BWP, the second BWP, the third BWP of the second subgroup BWP, or the fourth BWP of the second subgroup BWP, wherein the third BWP is associated with the first communication direction and wherein the fourth BWP is associated with the second communication direction, wherein the first subgroup BWP includes only the first BWP and the second BWP, and wherein the second subgroup BWP includes only the third BWP and the fourth BWP.

[0261] Aspect 12: The method according to any one of aspects 10 to 11, further comprising: receiving a third control signaling indicating another selected BWP for the second group of time slots from the group of BWPs.

[0262] Aspect 13: The method according to any one of Aspects 1 to 12 also includes: receiving a second control signaling, wherein the second control signaling updates the RBs included in the first group of RBs, the RBs included in the second group of RBs, the RBs included in the third group of RBs, or a combination thereof.

[0263] Aspect 14: A method according to any one of Aspects 1 to 13, wherein receiving the control signaling includes: receiving an indication of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including the first BWP and the second BWP, the second BWP configuration including a third BWP associated with the first communication direction and a fourth BWP associated with the second communication direction, wherein the control signaling also includes an indication of a time domain switching mode between the first BWP configuration and the second BWP configuration.

[0264] Aspect 15: The method according to aspect 14, wherein the time domain switching pattern includes a time gap between one or more time slots associated with the first BWP configuration and one or more time slots associated with the second BWP configuration.

[0265] Aspect 16: The method according to any one of Aspects 1 to 15, wherein a first guard band is located between the first group of RBs and the third group of RBs in the frequency domain, and a second guard band is located between the third group of RBs and the second group of RBs in the frequency domain.

[0266] Aspect 17: A method for performing wireless communications at a network entity, the method comprising: outputting control signaling, the control signaling comprising an indication of a first BWP associated with a first communication direction and a second BWP associated with a second communication direction, the first BWP comprising a first subband and a second subband, the first subband comprising a first group of RBs, the second subband comprising a second group of RBs, wherein the first group of RBs and the second group of RBs are not continuous in the frequency domain, and the second BWP comprises a third group of RBs that does not overlap with the first group of RBs and the second group of RBs in the frequency domain; and communicating in SBFD mode via the first BWP in the first communication direction and via the second BWP in the second communication direction.

[0267] Aspect 18: A method according to Aspect 17, wherein outputting the control signaling includes: outputting an indication of a first identifier associated with the first BWP; outputting an indication that the first BWP is associated with the first communication direction; and, for the first BWP, outputting an indication of the first group of RBs and the second group of RBs from a group of multiple RBs associated with at least one carrier bandwidth including the first BWP.

[0268] Aspect 19: A method according to Aspect 18, wherein outputting the control signaling includes: outputting an indication of a second identifier associated with the second BWP; outputting an indication that the second BWP is associated with the second communication direction; and, for the second BWP, outputting an indication of the third group of RBs from the multiple RBs.

[0269] Aspect 20: The method according to aspect 19, wherein the first identifier is equal to the second identifier.

[0270] Aspect 21: The method according to any one of aspects 19 to 20, wherein the first identifier is different from the second identifier.

[0271] Aspect 22: A method according to Aspect 17, wherein outputting the control signaling includes: outputting an indication of a first identifier associated with the first BWP; outputting an indication that the first BWP is associated with the first communication direction; for the first subband, outputting an indication of the starting RB index of the first group of RBs and the size of the first group of RBs in RBs; and for the second subband, outputting an indication of the starting RB index of the second group of RBs and the size of the second group of RBs in RBs.

[0272] Aspect 23: A method according to Aspect 22, wherein outputting the control signaling includes: outputting an indication of a second identifier associated with the second BWP; outputting an indication that the second BWP is associated with the first communication direction; and, for the second BWP, outputting an indication of the starting RB index of the third group of RBs and the size of the third group of RBs in RBs.

[0273] Aspect 24: A method according to Aspect 17, wherein outputting the control signaling includes: outputting an indication of a first identifier associated with the first BWP; outputting an indication that the first BWP is associated with the first communication direction; and outputting a bitmap indicating the first group of RBs and the second group of RBs for the first BWP.

[0274] Aspect 25: A method according to Aspect 24, wherein outputting the control signaling includes: outputting an indication of a second identifier associated with the first BWP; outputting an indication that the second BWP is associated with the second communication direction; and outputting a second bitmap indicating the third group of RBs for the second BWP.

[0275] Aspect 26: The method according to any one of Aspects 17 to 25 further includes: outputting a second control signaling indicating a group of BWPs, the group of BWPs including a first sub-group BWP associated with non-contiguous RBs and a second sub-group BWP associated with contiguous RBs, the first sub-group BWP including the first BWP and the second BWP, and wherein receiving the control signaling includes receiving an indication that a group of time slots are associated with the first BWP and the second BWP.

[0276] Aspect 27: The method according to Aspect 26 also includes: outputting a third control signaling, wherein the third control signaling updates the RB associated with at least one of the first BWP, the second BWP, the third BWP of the second subgroup BWP, or the fourth BWP of the second subgroup BWP, wherein the third BWP is associated with the first communication direction and wherein the fourth BWP is associated with the second communication direction, wherein the first subgroup BWP includes only the first BWP and the second BWP, and wherein the second subgroup BWP includes only the third BWP and the fourth BWP.

[0277] Aspect 28: The method according to any one of aspects 26 to 27, further comprising: outputting a third control signaling indicating another selected BWP for the second group of time slots from the group of BWPs.

[0278] Aspect 29: The method according to any one of Aspects 17 to 28 also includes: outputting a second control signaling, wherein the second control signaling updates the RBs included in the first group of RBs, the RBs included in the second group of RBs, the RBs included in the third group of RBs, or a combination thereof.

[0279] Aspect 30: A method according to any one of Aspects 17 to 29, wherein outputting the control signaling includes: outputting an indication of a first BWP configuration and a second BWP configuration for half-duplex mode, the first BWP configuration including the first BWP and the second BWP, the second BWP configuration including a third BWP associated with the first communication direction and a fourth BWP associated with the second communication direction, wherein the control signaling also includes an indication of a time domain switching mode between the first BWP configuration and the second BWP configuration.

[0280] Aspect 31: The method according to aspect 30, wherein the time domain switching pattern includes a time gap between one or more time slots associated with the first BWP configuration and one or more time slots associated with the second BWP configuration.

[0281] Aspect 32: A method according to any one of Aspects 17 to 31, wherein a first guard band is located between the first group of RBs and the third group of RBs in the frequency domain, and a second guard band is located between the third group of RBs and the second group of RBs in the frequency domain.

[0282] Aspect 33: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 16.

[0283] Aspect 34: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing a method according to any one of aspects 1 to 16.

[0284] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 16.

[0285] Aspect 36: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 17 to 32.

[0286] Aspect 37: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one component for performing the method according to any one of aspects 17 to 32.

[0287] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 17 to 32.

[0288] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

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

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

[0292] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0293] Computer-readable media include both non-transient computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transient storage media can be any available media that can be accessed by a general or special computer. By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or may be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient media that can be accessed by a general or special computer or a general or special processor. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent 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 in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, while optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0294] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".

[0295] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0296] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0297] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling from a network entity, the control signaling comprising an indication of a first bandwidth portion associated with a first communication direction and a second bandwidth portion associated with a second communication direction, the first bandwidth portion comprising a first subband and a second subband, the first subband comprising a first set of resource blocks, the second subband comprising a second set of resource blocks, wherein the first set of resource blocks and the second set of resource blocks are non-contiguous in a frequency domain, and the second bandwidth portion comprising a third set of resource blocks that do not overlap with the first set of resource blocks and the second set of resource blocks in the frequency domain; as well as Communicating with the network entity in a sub-band full-duplex mode in the first communication direction via the first bandwidth portion and in the second communication direction via the second bandwidth portion.

2. The method according to claim 1, wherein receiving the control signaling comprises: receiving an indication of a first identifier associated with the first bandwidth portion; receiving an indication that the first bandwidth portion is associated with the first communication direction; as well as For the first bandwidth portion, an indication of the first set of resource blocks and the second set of resource blocks from a plurality of resource blocks associated with at least one carrier bandwidth comprising the first bandwidth portion is received.

3. The method according to claim 2, wherein receiving the control signaling comprises: receiving an indication of a second identifier associated with the second bandwidth portion; receiving an indication that the second bandwidth portion is associated with the second communication direction; as well as An indication of the third set of resource blocks from the plurality of resource blocks is received for the second bandwidth portion. The method of claim 3 , wherein the first identifier is equal to the second identifier. The method of claim 3 , wherein the first identifier is different from the second identifier.

6. The method of claim 1 , wherein receiving the control signaling comprises: receiving an indication of a first identifier associated with the first bandwidth portion; receiving an indication that the first bandwidth portion is associated with the first communication direction; receiving, for the first subband, an indication of a starting resource block index of the first set of resource blocks and a size in resource blocks of the first set of resource blocks; as well as For the second subband, an indication of a starting resource block index of the second set of resource blocks and a size in resource blocks of the second set of resource blocks is received.

7. The method of claim 6, wherein receiving the control signaling comprises: receiving an indication of a second identifier associated with the second bandwidth portion; receiving an indication that the second bandwidth portion is associated with the first communication direction; as well as For the second bandwidth portion, an indication of a starting resource block index of the third set of resource blocks and a size in resource blocks of the third set of resource blocks is received.

8. The method of claim 1, wherein receiving the control signaling comprises: receiving an indication of a first identifier associated with the first bandwidth portion; receiving an indication that the first bandwidth portion is associated with the first communication direction; as well as A bitmap indicating the first set of resource blocks and the second set of resource blocks is received for the first bandwidth part.

9. The method of claim 8, wherein receiving the control signaling comprises: receiving an indication of a second identifier associated with the first bandwidth portion; receiving an indication that the second bandwidth portion is associated with the second communication direction; as well as A second bitmap indicating the third set of resource blocks is received for the second bandwidth part.

10. The method according to claim 1, further comprising: receiving second control signaling indicating a group of bandwidth parts, the group of bandwidth parts comprising a first sub-group of bandwidth parts associated with non-contiguous resource blocks and a second sub-group of bandwidth parts associated with contiguous resource blocks, the first sub-group of bandwidth parts comprising the first bandwidth part and the second bandwidth part, and wherein receiving the control signaling comprises receiving an indication that a group of time slots is associated with the first bandwidth part and the second bandwidth part.

11. The method according to claim 10, further comprising: receiving third control signaling, the third control signaling updating resource blocks associated with at least one of the first bandwidth part, the second bandwidth part, a third bandwidth part of the second subgroup bandwidth part, or a fourth bandwidth part of the second subgroup bandwidth part, wherein the third bandwidth part is associated with the first communication direction and wherein the fourth bandwidth part is associated with the second communication direction, wherein the first subgroup bandwidth part includes only the first bandwidth part and the second bandwidth part, and wherein the second subgroup bandwidth part includes only the third bandwidth part and the fourth bandwidth part.

12. The method according to claim 10, further comprising: Third control signaling is received indicating another selected bandwidth portion from the set of bandwidth portions for a second set of time slots.

13. The method according to claim 1, further comprising: Second control signaling is received, the second control signaling updating resource blocks included in the first set of resource blocks, resource blocks included in the second set of resource blocks, resource blocks included in the third set of resource blocks, or a combination thereof.

14. The method of claim 1, wherein receiving the control signaling comprises: Receive an indication of a first bandwidth portion configuration and a second bandwidth portion configuration for half-duplex mode, the first bandwidth portion configuration comprising the first bandwidth portion and the second bandwidth portion, the second bandwidth portion configuration comprising a third bandwidth portion associated with the first communication direction and a fourth bandwidth portion associated with the second communication direction, wherein the control signaling also includes an indication of a time domain switching mode between the first bandwidth portion configuration and the second bandwidth portion configuration.

15. The method of claim 14, wherein the time domain switching pattern comprises a time gap between one or more time slots associated with the first bandwidth portion configuration and one or more time slots associated with the second bandwidth portion configuration.

16. The method of claim 1, wherein: A first guard band is located between the first group of resource blocks and the third group of resource blocks in the frequency domain, and A second guard band is located between the third group of resource blocks and the second group of resource blocks in the frequency domain.

17. A method for wireless communication at a network entity, the method comprising: outputting control signaling, the control signaling comprising an indication of a first bandwidth portion associated with a first communication direction and a second bandwidth portion associated with a second communication direction, the first bandwidth portion comprising a first subband and a second subband, the first subband comprising a first set of resource blocks, the second subband comprising a second set of resource blocks, wherein the first set of resource blocks and the second set of resource blocks are non-contiguous in a frequency domain, and the second bandwidth portion comprising a third set of resource blocks that do not overlap with the first set of resource blocks and the second set of resource blocks in the frequency domain; as well as Communicating in a sub-band full-duplex mode in the first communication direction via the first bandwidth portion and in the second communication direction via the second bandwidth portion.

18. The method according to claim 17, wherein outputting the control signaling comprises: outputting an indication of a first identifier associated with the first bandwidth portion; outputting an indication that the first bandwidth portion is associated with the first communication direction; as well as For the first bandwidth portion, an indication of the first set of resource blocks and the second set of resource blocks from a plurality of resource blocks associated with at least one carrier bandwidth comprising the first bandwidth portion is output.

19. The method according to claim 18, wherein outputting the control signaling comprises: outputting an indication of a second identifier associated with the second bandwidth portion; outputting an indication that the second bandwidth portion is associated with the second communication direction; as well as An indication of the third set of resource blocks from the plurality of resource blocks is output for the second bandwidth portion.

20. The method of claim 17, wherein outputting the control signaling comprises: outputting an indication of a first identifier associated with the first bandwidth portion; outputting an indication that the first bandwidth portion is associated with the first communication direction; outputting, for the first subband, an indication of a starting resource block index of the first set of resource blocks and a size in resource blocks of the first set of resource blocks; as well as For the second subband, an indication of a starting resource block index of the second set of resource blocks and a size in resource blocks of the second set of resource blocks is output.

21. The method according to claim 20, wherein outputting the control signaling comprises: outputting an indication of a second identifier associated with the second bandwidth portion; outputting an indication that the second bandwidth portion is associated with the first communication direction; as well as For the second bandwidth part, an indication of a starting resource block index of the third set of resource blocks and a size in resource blocks of the third set of resource blocks is output.

22. The method of claim 17, wherein outputting the control signaling comprises: outputting an indication of a first identifier associated with the first bandwidth portion; outputting an indication that the first bandwidth portion is associated with the first communication direction; as well as A bitmap indicating the first set of resource blocks and the second set of resource blocks is output for the first bandwidth part.

23. The method of claim 22, wherein outputting the control signaling comprises: outputting an indication of a second identifier associated with the first bandwidth portion; outputting an indication that the second bandwidth portion is associated with the second communication direction; as well as A second bitmap indicating the third set of resource blocks is output for the second bandwidth part.

24. The method of claim 17, further comprising: outputting second control signaling indicating a group of bandwidth parts, the group of bandwidth parts comprising a first sub-group of bandwidth parts associated with non-contiguous resource blocks and a second sub-group of bandwidth parts associated with contiguous resource blocks, the first sub-group of bandwidth parts comprising the first bandwidth part and the second bandwidth part, and wherein receiving the control signaling comprises receiving an indication that a group of time slots is associated with the first bandwidth part and the second bandwidth part.

25. The method according to claim 24, further comprising: Outputting third control signaling, the third control signaling updating resource blocks associated with at least one of the first bandwidth part, the second bandwidth part, the third bandwidth part of the second subgroup bandwidth part, or the fourth bandwidth part of the second subgroup bandwidth part, wherein the third bandwidth part is associated with the first communication direction and wherein the fourth bandwidth part is associated with the second communication direction, wherein the first subgroup bandwidth part includes only the first bandwidth part and the second bandwidth part, and wherein the second subgroup bandwidth part includes only the third bandwidth part and the fourth bandwidth part.

26. The method of claim 24, further comprising: A third control signaling is outputted, the third control signaling indicating another selected bandwidth portion from the set of bandwidth portions for a second set of time slots.

27. The method of claim 17, further comprising: A second control signaling is outputted, the second control signaling updating resource blocks included in the first group of resource blocks, resource blocks included in the second group of resource blocks, resource blocks included in the third group of resource blocks, or a combination thereof.

28. The method of claim 17, wherein outputting the control signaling comprises: Output an indication of a first bandwidth portion configuration and a second bandwidth portion configuration for half-duplex mode, wherein the first bandwidth portion configuration includes the first bandwidth portion and the second bandwidth portion, and the second bandwidth portion configuration includes a third bandwidth portion associated with the first communication direction and a fourth bandwidth portion associated with the second communication direction, wherein the control signaling also includes an indication of a time domain switching mode between the first bandwidth portion configuration and the second bandwidth portion configuration.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling from a network entity, the control signaling comprising an indication of a first bandwidth portion associated with a first communication direction and a second bandwidth portion associated with a second communication direction, the first bandwidth portion comprising a first subband and a second subband, the first subband comprising a first set of resource blocks, the second subband comprising a second set of resource blocks, wherein the first set of resource blocks and the second set of resource blocks are non-contiguous in a frequency domain, and the second bandwidth portion comprising a third set of resource blocks that do not overlap with the first set of resource blocks and the second set of resource blocks in the frequency domain; as well as Communicating with the network entity in a sub-band full-duplex mode in the first communication direction via the first bandwidth portion and in the second communication direction via the second bandwidth portion.

30. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: outputting control signaling, the control signaling comprising an indication of a first bandwidth portion associated with a first communication direction and a second bandwidth portion associated with a second communication direction, the first bandwidth portion comprising a first subband and a second subband, the first subband comprising a first set of resource blocks, the second subband comprising a second set of resource blocks, wherein the first set of resource blocks and the second set of resource blocks are non-contiguous in a frequency domain, and the second bandwidth portion comprising a third set of resource blocks that do not overlap with the first set of resource blocks and the second set of resource blocks in the frequency domain; as well as Communicating in a sub-band full-duplex mode in the first communication direction via the first bandwidth portion and in the second communication direction via the second bandwidth portion.

Images