Scheduling time domain resource allocation for multiple transmissions across subbands

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive an authorization to schedule communications during a full duplex slot, the communications including a first communication using a first set of one or more resource blocks and a second communication using a second set of one or more resource blocks. The UE identifies a first frequency resource for the first one or more set of resource blocks and a second frequency resource for the second one or more set of resource blocks based at least in part on a time domain resource allocation field indicated in the grant. The UE may perform the communication during the full duplex slot using the first frequency resource and the second frequency resource.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 891,940, filed by Abotabl et al. on August 19, 2022, entitled “TIME DOMAIN RESOURCE ALLOCATION SCHEDULING MULTIPLE TRANSMISSIONS ACROSS SUBBANDS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications including time domain resource allocation for scheduling multiple transmissions across subbands. Background Art

[0004] 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 communication of a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting time domain resource allocation (TDRA) for scheduling multiple transmissions across subbands. For example, the described technology provides a single grant for scheduling multiple wireless communications during a full-duplex (FD) time slot. A network entity may send a grant to a user equipment (UE). The DCI grant schedules communications during a FD time slot (e.g., a sub-band full-duplex (SBFD) or an intra-band full-duplex (IBFD) time slot). The communications scheduled during the FD time slot may include a first communication (e.g., an uplink or downlink communication) and a second communication (uplink or downlink communication), although more than two communications may be scheduled during the FD time slot. Communications may also be scheduled in one or more half-duplex time slots by the grant. The UE uses a TDRA field indicated in the grant to identify or determine a first frequency resource for a first one or more resource block (RB) sets (e.g., a set of RBs for the first communication) and a second frequency resource for a second one or more RB sets (e.g., a set of RBs for the second communication). The TDRA indication signals that the time slot index associated with each communication is the same (e.g., shared). The network entity schedules physical uplink or downlink shared channel (PxSCH) communications in different frequency resources during the FD time slot, and configures the TDRA field in the DCI grant to carry an indication of the RB set for each frequency resource. Thus, the UE and the network entity perform wireless communication during the FD time slot using the frequency resources identified by the TDRA field.

[0006] A method for wireless communication at a UE is described. The method may include: receiving a grant to schedule a communication during an FD time slot, the communication including a first communication using a first one or more RB sets and a second communication using a second one or more RB sets; identifying a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based on a TDRA field indicated in the grant; and performing the communication during the FD time slot using the first frequency resource and the second frequency resource.

[0007] 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 executable by the processor to cause the apparatus to: receive an authorization to schedule communication during an FD time slot, the communication including a first communication using a first one or more RB sets and a second communication using a second one or more RB sets; identify a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based on a TDRA field indicated in the authorization; and perform the communication using the first frequency resource and the second frequency resource during the FD time slot.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving a grant to schedule a communication during an FD time slot, the communication including a first communication using a first set of one or more RBs and a second communication using a second set of one or more RBs; identifying a first frequency resource for the first set of one or more RBs and a second frequency resource for the second set of one or more RBs based on a TDRA field indicated in the grant; and performing the communication during the FD time slot using the first frequency resource and the second frequency resource.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to perform the following operations: receiving an authorization to schedule communication during an FD time slot, the communication including a first communication using a first one or more RB sets and a second communication using a second one or more RB sets; identifying a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based on a TDRA field indicated in the authorization; and performing the communication using the first frequency resource and the second frequency resource during the FD time slot.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first time slot index for the first communication and a second time slot index for the second communication based on the TDRA field and determining the authorization to schedule communication during the FD time slot based on the first time slot index and the second time slot index indicating a shared time slot index.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying, based on the authorization, a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication, and determining that the second communication may be a repetition of the first communication based on the first redundancy version and the second redundancy version being the same redundancy version and the first codeword and the second codeword being the same codeword.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying, based on the authorization, a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication, and determining that the first communication and the second communication may be different communications based on the first redundancy version and the second redundancy version being different redundancy versions and the first codeword and the second codeword being different codewords.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first start symbol for the first communication during the FD time slot and a second start symbol for the second communication during the FD time slot based on the TDRA field, wherein the first start symbol and the second start symbol include the same start symbol or different start symbols.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on a frequency domain resource allocation field indicated in the grant and identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on the first starting RB.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on a first portion of the frequency domain resource allocation field indicated in the grant and identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on a second portion of the frequency domain resource allocation field.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying, based on the authorization, the first communication and the second communication scheduled during the FD time slot based on a shared time slot index associated with the first communication and the second communication, and a third communication scheduled during the half-duplex time slot based on a time slot index that may be different from the shared time slot index.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first frequency resource and the second frequency resource include different subbands during SBFD or include overlapping frequency resources during IBFD time slots.

[0018] A method for wireless communication at a network entity is described. The method may include: identifying, for a UE, a first frequency resource for a first set of one or more RBs associated with a first communication during an FD time slot and a second frequency resource for a second set of one or more RBs associated with a second communication during the FD time slot; sending to the UE an authorization to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource; and performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0019] 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 executable by the processor to cause the apparatus to: identify, for a UE, a first frequency resource for a first one or more RB sets associated with a first communication during an FD time slot and a second frequency resource for a second one or more RB sets associated with a second communication during the FD time slot; send to the UE an authorization to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource; and perform the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0020] Another apparatus for wireless communication at a network entity is described. The apparatus may include components for performing the following operations: identifying, for a UE, a first frequency resource for a first set of one or more RBs associated with a first communication during an FD time slot and a second frequency resource for a second set of one or more RBs associated with a second communication during the FD time slot; sending to the UE an authorization to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource; and performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0021] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to perform the following operations: identify a first frequency resource for a first one or more RB sets associated with a first communication during an FD time slot and a second frequency resource for a second one or more RB sets associated with a second communication during the FD time slot for a UE; send an authorization to schedule the first communication and the second communication during the FD time slot to the UE, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource; and perform the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first time slot index for the first communication and a second time slot index for the second communication based on the TDRA field, wherein the authorization schedules communication during the FD time slot based on the first time slot index and the second time slot index indicating the same time slot index.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying, based on the grant, a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication, wherein the second communication may be a repetition of the first communication based on the first redundancy version and the second redundancy version being the same redundancy version and the first codeword and the second codeword being the same codeword.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying, based on the authorization, a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication, wherein the first communication and the second communication may be different communications based on the first redundancy version and the second redundancy version being different redundancy versions and the first codeword and the second codeword being different codewords.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first start symbol for the first communication during the FD time slot and a second start symbol for the second communication during the FD time slot based on the TDRA field, wherein the first start symbol and the second start symbol include the same start symbol or different start symbols.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on a frequency domain resource allocation field indicated in the grant, wherein a second starting RB of the second one or more RB sets within the second frequency resource may be identified based on the first starting RB.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on a first portion of the frequency domain resource allocation field indicated in the grant and identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on a second portion of the frequency domain resource allocation field.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying, based on the authorization, the first communication and the second communication scheduled during the FD time slot based on a shared time slot index associated with the first communication and the second communication, and a third communication scheduled during the half-duplex time slot based on a time slot index that may be different from the shared time slot index.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first frequency resource and the second frequency resource include different subbands during SBFD or include overlapping frequency resources during IBFD time slots. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 An example of a wireless communication system supporting time domain resource allocation (TDRA) for scheduling multiple transmissions across subbands in accordance with one or more aspects of the present disclosure is illustrated.

[0031] Figure 2 An example of a wireless communication system supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is illustrated.

[0032] Figure 3A and Figure 3B An example of a time slot configuration of a TDRA supporting scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 4A and Figure 4BAn example of a time slot configuration of a TDRA supporting scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 5 An example of a time slot configuration of a TDRA supporting scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 6 and Figure 7 A block diagram of a device supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown.

[0036] Figure 8 A block diagram of a communication manager supporting TDRA for scheduling multiple transmissions across subbands in accordance with one or more aspects of the present disclosure is shown.

[0037] Fig. 9 A diagram of a system including a device supporting TDRA for scheduling multiple transmissions across subbands in accordance with one or more aspects of the present disclosure is shown.

[0038] Fig.10 and Fig.11 A block diagram of a device supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown.

[0039] Fig.12 A block diagram of a communication manager supporting TDRA for scheduling multiple transmissions across subbands in accordance with one or more aspects of the present disclosure is shown.

[0040] Fig.13 A diagram of a system including a device supporting TDRA for scheduling multiple transmissions across subbands in accordance with one or more aspects of the present disclosure is shown.

[0041] Figures 14 to 18 A flow chart illustrating a method of supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0042] Wireless networks may operate according to a grant-based protocol, in which a network entity manages resources (e.g., time resources, frequency resources, space resources, or code resources) used for wireless communications within the wireless network. For example, a network entity may send a grant to a user equipment (UE) that identifies the resources to be used for wireless communications within the network, as well as other parameters. These technologies support network entities to schedule wireless communications in one time slot or in multiple time slots using a single transmission to transmit a single grant (e.g., a downlink control information (DCI) grant). However, advanced wireless networks may use full-duplex (FD) time slots (e.g., sub-band full-duplex (SBFD) time slots or in-band full-duplex (IBFD) time slots), in which frequency resources are divided into different sub-bands or overlapping frequencies. FD time slots support UEs to perform multiple communications during FD time slots, such as concurrent downlink transmissions, uplink transmissions, or both uplink and downlink communications during FD time slots (at least to some extent). Conventional networks do not provide a mechanism to schedule FD communications (eg, multiple physical uplink or downlink shared channel (PxSCH) communications) during a FD time slot through a single DCI grant.

[0043] Thus, aspects of the described technology relate to improved methods, systems, devices, and apparatuses for supporting time domain resource allocation (TDRA) for scheduling multiple transmissions across subbands. For example, the described technology provides a single grant for scheduling multiple wireless communications during an FD time slot. A network entity sends a grant to a UE. The DCI grant schedules communications during an FD time slot (e.g., an SBFD or IBFD time slot). The communications scheduled during the FD time slot may include a first communication (e.g., an uplink or downlink communication) and a second communication (uplink or downlink communication), although more than two communications may be scheduled during the FD time slot. Communications may also be scheduled in one or more half-duplex time slots by the grant. The UE uses a TDRA field indicated in the grant to identify or determine a first frequency resource for a first one or more resource block (RB) sets (e.g., a set of RBs for the first communication) and a second frequency resource for a second one or more RB sets (e.g., a set of RBs for the second communication). The TDRA indication signals that the time slot index associated with each communication is the same (e.g., shared). The network entity schedules PxSCH communications in different frequency resources during the FD time slot and configures the TDRA field in the DCI grant to carry an indication of the RB set for each frequency resource. Thus, the UE and the network entity perform wireless communications during the FD time slot using the frequency resources identified by the TDRA field.

[0044] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams involving TDRA for scheduling multiple transmissions across subbands.

[0045] Figure 1 An example of a wireless communication system 100 supporting TDRAs for scheduling multiple transmissions across subbands 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).

[0046] 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).

[0047] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both 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 communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0048] 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.

[0049] 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 directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or 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), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0050] 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 converged (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).

[0051] 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)).

[0052] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may 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, medium access control (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 DUs 165 and the RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via those communication links.

[0053] 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 the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a 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 DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna of the IAB node 104 (e.g., of the RU 170) 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.

[0054] 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 that has 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).

[0055] 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. Thus, 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 .

[0056] 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 IAB 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 IAB node 104 via the F1 interface that the communication link is established, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via the NR Uu interface of the MT to the IAB node 104 via signaling. 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 .

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

[0058] 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 terminology, 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.

[0059] 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.

[0060] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a 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 bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier 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 a device 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).

[0061] 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 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 the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0062] 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, among 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).

[0063] 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 (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 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 a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent 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 a carrier bandwidth.

[0064] 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 employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, 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 communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0065] 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 for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0066] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period. seconds, of which can represent the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of 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).

[0067] 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, the 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 to the 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.

[0068] A subframe, a time slot, a mini-time slot, or a 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)).

[0069] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. 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 UE115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates 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 a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0070] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, 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 (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. 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.

[0071] A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with a network provider, or may provide restricted access to UEs 115 associated with the small cell (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.

[0072] 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 for different types of devices.

[0073] 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.

[0074] 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 synchronous or asynchronous operation.

[0075] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide 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, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0076] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at 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.

[0077] 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, low-latency, or critical functions. Ultra-reliable communications may include private or group communications and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency 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.

[0078] In some examples, a 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 of 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, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0079] 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), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0080] 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 transferred 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.

[0081] 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). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter. 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 service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using the lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

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

[0083] 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 licensed 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 performed using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0084] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which 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 communication 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.

[0085] 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 technique may be referred to as spatial multiplexing. The multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques 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.

[0086] 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 in 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).

[0087] 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. Transmissions 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) beam directions for later transmission or reception by the network entity 105.

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

[0089] 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 set of beams 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 unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel 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).

[0090] 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), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving 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 receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive 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).

[0091] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication 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.

[0092] 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.

[0093] UE 115 may receive a grant to schedule communications during an FD time slot, the communications including a first communication using a first set of one or more RBs and a second communication using a second set of one or more RBs. UE 115 may identify a first frequency resource for the first set of one or more RBs and a second frequency resource for the second set of one or more RBs based at least in part on a TDRA field indicated in the grant. UE 115 may perform the communications using the first frequency resource and the second frequency resource during the FD time slot.

[0094] The network entity 105 may identify, for the UE 115, a first frequency resource for a first set of one or more RBs associated with a first communication during the FD time slot and a second frequency resource for a second set of one or more RBs associated with a second communication during the FD time slot. The network entity 105 may send a grant to the UE 115 to schedule the first communication and the second communication during the FD time slot, the grant including a TDRA field identifying the first frequency resource and the second frequency resource. The network entity 105 may perform communications with the UE 115 using the first frequency resource and the second frequency resource during the FD time slot.

[0095] Figure 2 An example of a wireless communication system 200 supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a UE 205 and a network entity 210, which may be examples of corresponding devices described herein.

[0096] The wireless communication system 200 may support FD operation, such as using SBFD time slots (e.g., "flexible duplex" time slots) having one or more uplink subbands, one or more downlink subbands, and optionally also having one or more guard bands or gap bands between adjacent uplink and downlink subbands. SBFD time slots enable transmission and reception at the same time but on different frequency resources (e.g., downlink resources and separated from uplink resources in the frequency domain). Other examples of FD operation include using in-band full-duplex (IBFD) time slots, where the downlink and uplink share the same IBFD time resources and frequency resources (e.g., completely or at least partially overlap). Therefore, at least to some extent or in some examples, communication during an IBFD time slot includes transmission and reception at the same time and using the same frequency resources.

[0097] Therefore, the FD slot structure may also be referred to as a "D+U" slot to indicate that both downlink and uplink communications are performed during the FD slot. The FD slot structure is defined as both downlink transmissions and uplink transmissions occurring simultaneously and in overlapping frequency bands (e.g., IBFD) or in adjacent frequency bands (e.g., adjacent subbands within an SBFD slot). In a given symbol of an FD slot, a half-duplex (HD) UE may perform uplink transmissions in the uplink frequency band or receive downlink transmissions in the downlink frequency band. In a given symbol of an FD slot, an FD UE may perform uplink transmissions in the uplink frequency band (IBFD) or the uplink subband (SBFD), and may receive downlink transmissions in the downlink frequency band (IBFD) or the downlink subband (SBFD).

[0098] The frequency resources (e.g., bands or subbands) are indicated to the UE in the FDRA field, which identifies the frequency domain resources at the RB level, where an RB consists of 12 adjacent frequencies (also known as tones or subcarriers) and multiple RBs form an RB set or RBG. The FDRA field can use Type 0 or Type 1 format to identify or configure the frequency domain resources for the UE. Type 0 FRDR indication can also be considered as a discontinuous RB allocation, where a bitmap is used to identify the allocated or configured RBG. The indicated frequency resource allocation can be a multiple of RBG, where the RBG size is based on the BWP size and other configurations (e.g., RBG size) signaled to the UE. In the Type 0 FDRA format, each bit corresponds to an RBG, so that if the bit is set (e.g., "1"), the corresponding RBG is allocated to the UE. In contrast, the Type 1 FDRA field format is considered a continuous RB allocation scheme, where the FDRA field indicates the starting RB and the number of combined continuous RBs in the resource indicator value (RIV) field. That is, the number of bits representing the RIV indication may be a function of the length of the BWP (eg, a BWP spanning 5 RBs may use a four-bit RIV indication).

[0099] The wireless communication system 200 may operate according to a grant-based protocol in which a network entity 210 manages resources (e.g., time resources, frequency resources, space resources, or code resources) used for wireless communication within a wireless network. For example, the network entity 210 may send a grant (e.g., a DCI grant 215) to the UE 205 that identifies the resources to be used for wireless communication within the network, as well as other parameters. This enables the network entity 210 to schedule wireless communication in one time slot or in multiple time slots using a single transmission to transmit a single grant (e.g., one DCI grant 215).

[0100] More specifically, the wireless network may support multiple physical uplink shared channels (PUSCH) / physical downlink shared channels (PDSCH) (e.g., PxSCH) DCIs. The number of multiple PDSCHs or PUSCHs scheduled by the same DCI may be based on the number of time domain resources allocated to the UE in the corresponding row in the configured TDRA table (i.e., the entry in the RRC configuration message of the table). That is, the UE may be an RRC configured with a table corresponding to a TRDA indication, wherein each TDRA indication corresponds to a row, column, or both in the configured table. More specifically, the scheduling DCI may indicate or otherwise provide a TDRA field as a row index of a row in a plurality of rows in the TDRA table. Each row contains one or more combinations of {mapping type, scheduling offset K0 or K2, starting symbol, number of consecutive symbols} for each PDSCH or PUSCH scheduled by the DCI.

[0101] A non-limiting example of a row of the TDRA table may include: column (PDSCH mapping type) / row (type A); column (K0) / row (0); column (S) / row (2); column (L) / row (6). Column (K0) (or K2) indicates a slot offset (e.g., slot index) that is an offset from a downlink slot in which the scheduled DCI is received and a slot in which the PxSCH is scheduled. Column (S) indicates a start symbol and column (L) indicates the number of consecutive symbols, which are also collectively referred to as SLIV (start and length indicator value). Typically, there is one combination (e.g., row) for a legacy feature in which the DCI schedules a single PxSCH. Multiple combinations of this feature may be supported so that one DCI may schedule multiple PxSCHs. The network typically configures the TDRA table to have enough combinations (e.g., rows) to provide good scheduling flexibility. A row of the TDRA table may indicate a PDSCH or PUSCH in consecutive or non-consecutive slots. Many fields are common to all scheduled PUSCHs or PDSCHs in a DCI (eg, to minimize the DCI size).

[0102] However, the wireless communication system 200 may use FD time slots (e.g., SBFD time slots or IBFD time slots) in which frequency resources are divided into different sub-bands or overlapping frequencies. The FD time slots support the UE 205 to perform multiple communications during the FD time slot, such as (e.g., at least to some extent) concurrent downlink transmissions, uplink transmissions, or a mix of uplink and downlink communications during the FD time slot.

[0103] In a SBFD time slot, this may result in two non-contiguous subband allocations (e.g., two downlink non-contiguous downlink subbands separated by an uplink subband, or vice versa). The two non-contiguous subbands may be separated by a relatively large subband going in the other direction (e.g., a relatively large amount of frequency resources in an uplink subband separating two non-contiguous downlink subbands, or vice versa), in addition to any guard bands or gap bands (e.g., frequency resources between adjacent subbands to mitigate leakage and interference).

[0104] Conventional networks provide for scheduling a single PxSCH (uplink or downlink) communication in one time slot using a single DCI. Conventional networks also support scheduling multiple PxSCH communications across multiple time slots using a single DCI. However, such conventional networks do not provide a mechanism for scheduling FD communications (e.g., multiple PxSCH communications) during a FD time slot with a single grant (e.g., DCI grant 215).

[0105] Thus, aspects of the techniques described herein provide various mechanisms to support scheduling multiple PxSCHs (e.g., communications including a first communication and a second communication) across multiple RB sets (e.g., different subbands in an SBFD slot example, different or the same frequency resources in an IBFD slot) in an FD slot using a single DCI. For HD UEs, the scheduled PxSCH communications may be downlink communications or uplink communications. For FD UEs, the single DCI may schedule PDSCH / PDSCH, PDSCH / PUSCH, or PUSCH / PUSCH communications in different RB sets (e.g., different subbands in an SBFD slot, different or the same frequency resources in an IBFD slot) during the FD slot. This reduces the number of DCIs required to schedule FD communications during the FD slot and improves communication between the UE 205 and the network entity 210.

[0106] This may include scheduling two downlink communications across two downlink subbands, scheduling one downlink and one uplink communication across a downlink subband and an uplink subband, or scheduling two uplink communications across two uplink subbands during a FD time slot (e.g., a SBFD time slot) using a single DCI (e.g., DCI grant 215). This may include scheduling two downlink communications, two uplink communications, or one downlink communication and one uplink communication on different frequency resources, on partially overlapping frequency resources, or on completely overlapping frequency resources during a FD time slot (e.g., an IBFD time slot) using a single DCI (e.g., DCI grant 215). Thus, references to RB sets in this context generally include one or more RB sets scheduled for each communication scheduled during a FD time slot, wherein different RB sets are configured in separate subbands during a SBFD time slot, or in different or overlapping frequency resources during an IBFD time slot. Accordingly, references to FD slots in this context may include SBFD slots, IBFD slots, or any other FD slot structure configured for use in a wireless communication system.

[0107] The network entity 210 may send or otherwise provide a grant (e.g., a DCI grant 215) to the UE 205. The DCI grant 215 may allocate, identify, or otherwise schedule a communication during a FD time slot (e.g., a SBFD or IBFD time slot). The communication scheduled during the FD time slot may include a first communication (e.g., an uplink or downlink communication) and a second communication (an uplink or downlink communication). More than two communications may be scheduled in the FD time slot by the DCI grant 215 as well as communications scheduled in other time slots. For example, communications may also be scheduled by the DCI grant 215 in one or more FD time slots, additional FD time slots, or both.

[0108] At 220, the UE 205 may identify or otherwise determine a first frequency resource for a first RB set and a second frequency resource for a second RB set for the FD time slot (e.g., the UE 205 may identify or otherwise determine RB information). Each communication scheduled during the FD time slot (e.g., the first communication and the second communication) may be associated with one or more corresponding RB sets during the FD time slot (e.g., a first one or more RB sets associated with the first communication and a second one or more RB sets associated with the second communication). As discussed above, each of the one or more RB sets may include frequency domain resources scheduled or otherwise allocated for the associated communication. Each RB includes 12 subcarriers or tones in the frequency domain, an RB set may include one or more RBs, and one or more RB sets generally span frequency resources allocated to the associated communication. Frequency resources may be allocated or otherwise signaled absolutely (e.g., identifying a specific frequency) or relatively (e.g., relative to frequency resources within a subband or within a frequency band). In an example where the FD time slot is an SBFD time slot, the first RB set and the second RB set may be in different subbands of the SBFD time slot. In an example where the FD slot is an IBFD slot, the first set of RBs and the second set of RBs may be in the same (eg, partially or completely overlapping) frequency resources of the IBFD slot.

[0109] The network entity 210 may select, configure, identify, or otherwise determine the TDRA field indicated in the DCI grant 215 to signal or otherwise identify the frequency resources for the first RB set and the second RB set. The TDRA field may be selected or otherwise configured to carry or convey an indication of the first frequency resource for the first RB set and the second frequency resource for the second RB set. The TDRA field may be used to schedule the first communication and the second communication during the FD time slot. As discussed above, each row or combination of rows in the TDRA table may indicate a K0 or K2 value (e.g., a time slot index) that signals an offset or delay in the time domain (e.g., in a time slot) between the DCI grant 215 (e.g., a time slot sent by the network entity 210 and received by the UE 205) and the FD time slot in which the first communication and the second communication are scheduled. Therefore, each communication scheduled by the DCI grant 215 may have its own time slot index, which indicates which time slot the communication is scheduled to.

[0110] In the HD example, communications with different slot indices scheduled by the DCI grant 215 are scheduled in different slots. In the FD example, two or more communications with the same or common (e.g., shared) slot index (e.g., K0=0 or 1 or 2 or some other slot offset) scheduled by the DCI grant 215 may signal that the communications are scheduled during the FD slot (e.g., the same slot corresponding to the same slot index). More specifically, the first slot index (K0 or K2) of the first communication scheduled in the first RB set is the same (e.g., shared) as the second slot index (K0 or K2) of the second communication scheduled in the second RB set, which may schedule or otherwise identify that the first communication and the second communication are scheduled during the same slot (e.g., during the FD slot). The DCI grant 215 that schedules the two (or more) communications in the FD slot may carry or otherwise convey an indication of the first frequency resource and the second frequency resource to be used for the two (or more) communications scheduled during the FD slot.

[0111] Thus, the UE 205 may use the TDRA field indicated in the grant to identify or determine the first frequency resources for the first set of RBs and the second frequency resources for the second set of RBs. The TDRA indication signals that the time slot index associated with each communication is the same (e.g., shared), and based on this, the frequency resources used for the communication may be identified. For example, the FDRA field carried or otherwise conveyed in the DCI grant 215 may identify the same frequency resources (e.g., the same number of allocated RBs) for the first set of RBs and the second set of RBs (e.g., using a single FDRA indication), or separately identify the frequency resources for the first set of RBs and the second set of RBs (e.g., using a single FDRA indication, but split into different portions corresponding to different communications being scheduled).

[0112] Thus, the network entity 210 may schedule PxSCH communications in different frequency resources during the FD time slot and configure the TDRA field in the DCI grant 215 to carry an indication of the RB set for each frequency resource. That is, the TDRA field may be interpreted to signal that the communication is scheduled in the FD time slot, and thus the FDRA field may be interpreted based on the FD time slot to identify a first set of RBs and a second set of RBs in different or overlapping frequency resources in different subbands of the SBFD time slot or in a frequency band of the IBFD time slot. Thus, the UE 205 and the network entity 210 may perform wireless communications 225 during the FD time slot using (at least to some extent) the frequency resources identified by the TDRA field (e.g., alone or in combination with the FDRA field) carried in the DCI grant 215.

[0113] Figure 3A and Figure 3BAn example of a time slot configuration 300 for supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is illustrated. The time slot configuration 300 may implement various aspects of the wireless communication system 100 or 200. Various aspects of the time slot configuration 300 may be implemented at or by a UE or a network entity, which may be an example of a corresponding device described herein.

[0114] The time slot configuration 300 illustrates an example of an SBFD time slot having a downlink subband 320, an uplink subband 325, and a downlink subband 330. In this example, the downlink subband 320 and the downlink subband 330 are non-contiguous subbands separated by the uplink subband 325 and any configured guard bands or gap bands. That is, the time slot configuration 300 may include gap bands or guard bands between adjacent uplink and downlink subbands that provide a degree of separation in the frequency domain between the subbands to mitigate leakage and interference.

[0115] Figure 3A The timeslot configuration 300 - a illustrates an example in which a DCI grant 305 schedules two downlink transmissions in non-contiguous downlink subbands of a SBFD timeslot. Figure 3B The time slot configuration 300-b illustrates an example in which a DCI grant 305 schedules one downlink transmission in the downlink subband of an SBFD time slot and one uplink transmission in the uplink subband. Although the time slot configuration 300 illustrates an example in which the techniques described herein are applied to an SBFD time slot, it should be understood that such techniques may also be applied to an IBFD time slot. For example, two downlink communications or two uplink communications or at least one uplink communication and one downlink communication scheduled during an IBFD time slot may be scheduled on different, partially overlapping, or completely overlapping frequency resources in the frequency band of the IBFD time slot.

[0116] Although the time slot configuration 300 illustrates a non-limiting example of an SBFD time slot having two non-contiguous subbands separated by an uplink subband, it should be understood that other SBFD time slot structures may also be used with the techniques described herein (e.g., an SBFD time slot having two non-contiguous uplink subbands separated by a downlink subband, or an SBFD time slot having one uplink subband and one downlink subband).

[0117] As discussed above, aspects of the techniques discussed herein provide a single DCI to schedule multiple communications during an FD time slot. For example, a network entity may send, provide, or otherwise convey a DCI grant 305 to a UE to schedule communications for the UE. The scheduled communications may be for an FD time slot (e.g., an SBFD time slot, an IBFD time slot, or both) or for both an FD time slot and an HD time slot. The UE may receive, obtain, or otherwise identify the DCI grant 305 from the network entity, and use the TDRA field indicated in the DCI grant 305 to identify or otherwise determine a first frequency resource for a first set of RBs and a second frequency resource for a second set of RBs. That is, the DCI grant may schedule multiple (e.g., first and second) communications during the FD time slot, wherein each communication during the FD time slot has the same or shared time slot index (e.g., K0 or K2 signals that two communications are in the same time slot). The TDRA field of the DCI grant 305 may be interpreted to schedule the first communication and the second communication during the FD time slot (e.g., the same or shared time slot index). Based on the first and second communications scheduled during the FD time slot, the UE may generally use the FDRA field of the DCI grant 305 to identify or otherwise determine the first and second sets of RBs allocated for communications during the FD time slot.

[0118] The time slot configuration 300 illustrates two non-limiting examples of how the FDRA field indicated in the DCI grant 305 may be interpreted from the perspective of the DCI grant 305 scheduling a first communication and a second communication during the FD time slot. Figure 3AThe time slot configuration 300-a of the DCI grant 305 may include the FDRA field indicated in the DCI grant 305 signaling or otherwise conveying information for identifying the starting RB (e.g., the first starting RB) of the first RB set (e.g., the starting RB of the RB set allocated to the PDSCH 310). The first starting RB (e.g., the starting RB of the first RB set in the first RB set) may then be used to identify or otherwise determine the starting RB (e.g., the second starting RB) of the second RB set (e.g., the starting RB of the RB set allocated to the PDSCH 315). That is, when two or more PxSCHs (e.g., PDSCH 310 and PDSCH 315) are scheduled with the same time slot index and in different subbands (e.g., based on the DCI format, in different RB sets) during the FD slot, the frequency resources may be configured such that each PxSCH may have the same number of allocated RBs in each subband or frequency band. Thus, the starting RB indicated in the FDRA field of the DCI grant 305 may be interpreted such that a first RB in a first set of RBs of the set of RBs indicated for the first communication is a starting RB within a first subband or frequency band for which the first communication is being scheduled. The starting RB of the first set of RBs in the second set of RBs may be interpreted as the same starting RB but within a second subband or frequency band for which the second communication is being scheduled. Thus, in this example, two PxSCHs scheduled during an FD slot may have or use the same FDRA field, wherein the FDRA field is interpreted relative to a subband or frequency band rather than a bandwidth part (BWP) configured for the UE.

[0119] Next reference Figure 3BThe time slot configuration 300-b of the DCI grant 305 may include the FDRA field indicated in the DCI grant 305 signaling or otherwise conveying information for identifying the starting RB (e.g., the first starting RB) of the first RB set (e.g., the starting RB of the RB set allocated to the PDSCH 310). However, in this example, the FDRA field may be split into two (or more) parts or bits, where each part or bit field indicates the FDRA for each subband or frequency band. That is, the FDRA field indicated in the DCI grant 305 may be configured to carry or otherwise convey: a first part, which is used to identify the starting RB (e.g., the first starting RB) of the first RB in the first RB set for the first communication (e.g., PDSCH 310) in the first subband or the first frequency band (e.g., the downlink subband 320 in this example); and a second part, which is used to identify the starting RB (e.g., the second starting RB) of the first RB of the second RB set for the second communication in the second subband or the second frequency band (e.g., the uplink subband 325 in this example). Thus, in this example, the UE may use the second portion of the FDRA field to identify or otherwise determine a second starting RB (e.g., a second starting RB) of a first set of RBs in a second set of RBs for a second communication (e.g., PUSCH 335 in this example) in a second subband or subband (e.g., in the uplink subband 325 in this example). It should be understood that the FDRA field may be split evenly (e.g., allocating the same number of bits to each of the first set of RBs and the second set of RBs) or unevenly (e.g., using different bits for the first set of RBs and the second set of RBs).

[0120] Therefore, the UE and the network entity can perform wireless communications (e.g., first communications and second communications) in the first subband or frequency band and the second subband or frequency band, respectively, according to the first frequency resources and the second frequency resources (e.g., the first RB set and the second RB set, respectively) during the FD time slot according to the DCI authorization 305.

[0121] 4 illustrates an example of a time slot configuration 400 for a TDRA supporting scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure. The time slot configuration 400 may implement aspects of the wireless communication system 100 or 200 or aspects of the time slot configuration 300. Aspects of the time slot configuration 400 may be implemented at or by a UE or a network entity, which may be examples of corresponding devices described herein.

[0122] The time slot configuration 400 illustrates an example of a FD time slot, where Figure 4A The time slot configuration 400-a shows the SBFD time slots, and Figure 4BThe time slot configuration 400-b of FIG. 4 shows an IBFD time slot. The SBFD time slot may include subband 420, subband 425, and subband 430. Each subband in subband 420, subband 425, or subband 430 may be an uplink subband or a downlink subband. The SBFD time slot may also include one or more gap bands or guard bands that separate adjacent subbands. The IBFD time slot may include a downlink frequency band 435 and an uplink frequency band 440, and the downlink frequency band and the uplink frequency band may include time resources, frequency resources, or both that overlap partially or completely at least to some extent.

[0123] Figure 4A The time slot configuration 400 - a illustrates an example in which a DCI grant 405 schedules two wireless communications in non-contiguous sub-bands of a SBFD time slot. Figure 4B The timeslot configuration 400 - b illustrates an example in which the DCI grant 405 schedules one downlink transmission in the downlink frequency band 435 and one uplink transmission in the uplink frequency band 440 of the IBFD timeslot.

[0124] As discussed above, aspects of the techniques discussed herein provide a single DCI to schedule multiple communications during an FD time slot. For example, a network entity may send, provide, or otherwise convey a DCI grant 405 to a UE to schedule communications for the UE. The scheduled communications may be for an FD time slot (e.g., an SBFD time slot, an IBFD time slot, or both) or for both an FD time slot and an HD time slot. The UE may receive, obtain, or otherwise identify the DCI grant 405 from the network entity, and use the TDRA field indicated in the DCI grant 405 to identify or otherwise determine a first frequency resource for a first RB set 410 and a second frequency resource for a second RB set 415. That is, the DCI grant 405 may schedule multiple (e.g., first and second) communications during the FD time slot, wherein each communication during the FD time slot has the same or shared time slot index (e.g., K0 or K2 signals that two communications are in the same time slot). The TDRA field of the DCI grant 405 may be interpreted to schedule the first communication and the second communication during a FD time slot (e.g., the same or shared time slot index). Based on the first communication and the second communication scheduled during the FD time slot, the UE may generally use the FDRA field of the DCI grant 405 to identify or otherwise determine the first RB set and the second RB set allocated for communication during the FD time slot.

[0125] More specifically, the DCI grant 405 may carry or otherwise convey various parameters, indexes, etc. for scheduling each communication during the FD time slot. Such parameters, etc. may be configured to convey an indication that the wireless communications being scheduled are all for the FD time slot and to convey additional details. One example may include using a redundancy version (RV) and a codeword (CW) scheduled by the DCI grant 405 for signaling repetitions within a communication during the FD time slot. For example, each communication scheduled during the FD time slot may have an associated RV and CW (e.g., a first RV and a first CW for a first communication using the first RB set 410 and a second RV and a second CW for a second communication using the second RB set 415). For two communications scheduled during the FD time slot, configuring the RV and CW to be the same may indicate that the second communication is a repetition of the first communication. For two communications scheduled during the FD time slot, configuring the RV and CW to be different may indicate that the first communication and the second communication are different communications (e.g., different CWs). Although both allocations (eg, scheduled wireless communications) are configured with the same time slots (eg, same slot index, signaling the FD slots), each allocation may have a different symbol index such that each communication in the FD slots starts at a different symbol.

[0126] The time slot configuration 400 illustrates two non-limiting examples of how the FDRA field indicated in the DCI grant 405 may be interpreted from the perspective of the DCI grant 405 scheduling a first communication and a second communication during the FD time slot. Figure 4AThe time slot configuration 400-a of the DCI grant 405 may include the FDRA field indicated in the DCI grant 405 signaling or otherwise conveying information for identifying the starting RB (e.g., the first starting RB) of the first RB set 410 (e.g., the starting RB of the RB set to which the first communication is allocated). The first starting RB (e.g., the starting RB of the first RB set in the first RB set 410) may then be used to identify or otherwise determine the starting RB (e.g., the second starting RB) of the second RB set 415 (e.g., the starting RB of the RB set allocated to the second communication). That is, when two or more communications are scheduled during the FD time slot with the same time slot index and in different subbands (e.g., based on the DCI format, in different RB sets) or in different but overlapping frequency bands (e.g., based on the DCI format), the frequency resources may be configured such that each communication may have the same number of allocated RBs in each subband or frequency band. Thus, the starting RB indicated in the FDRA field of the DCI grant 405 may be interpreted such that the first RB in the first set of RBs of the set of RBs indicated for the first communication is the starting RB within the first subband or frequency band for which the first communication is being scheduled. The starting RB of the first set of RBs in the second set of RBs 415 may be interpreted as the same starting RB, but within the second subband or frequency band for which the second communication is being scheduled. Thus, in this example, two communications scheduled during the FD time slot may have or use the same TDRA field, wherein the FDRA field is interpreted relative to the subband or frequency band rather than the BWP configured for the UE.

[0127] Next reference Figure 4BIn the example of the time slot configuration 400-b, the FDRA field indicated in the DCI grant 405 may signal or otherwise convey information for identifying a starting RB (e.g., a first starting RB) of a first set of RBs (e.g., a starting RB of a set of RBs allocated to a first communication). However, in this example, the FDRA field may be split into two (or more) parts or bits, where each part or bit field indicates a FDRA for each subband or frequency band. That is, the FDRA field indicated in the DCI grant 405 may be configured to carry or otherwise convey: a first portion for identifying the starting RB (e.g., the first starting RB) of the first RB in the first RB set 410 for the first communication in the first subband (e.g., in the subband 420) or in the first frequency band (e.g., in the downlink frequency band 435); and a second portion for identifying the starting RB (e.g., the second starting RB) of the first RB in the second RB set 415 for the second communication in the second subband (e.g., in the subband 430) or in the second frequency band (e.g., in the uplink frequency band 440). Therefore, in this example, the UE may use the second portion of the FDRA field to identify or otherwise determine the second starting RB of the first RB set in the second RB set 415 for the second communication in the second subband or subband. It should be understood that the FDRA field may be evenly split (e.g., allocating the same number of bits to each of the first RB set and the second RB set) or unevenly split (e.g., using different bits for the first RB set and the second RB set).

[0128] Therefore, the UE and the network entity can perform wireless communications (e.g., first communications and second communications) in the first subband or frequency band and the second subband or frequency band, respectively, according to the first frequency resources and the second frequency resources (e.g., the first RB set and the second RB set, respectively) during the FD time slot according to the DCI authorization 405.

[0129] Figure 5 An example of a time slot configuration 500 for supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is illustrated. The time slot configuration 500 may implement aspects of the wireless communication system 100 or 200 or aspects of the time slot configuration 300 or 400. Various aspects of the time slot configuration 500 may be implemented at or by a UE or a network entity, which may be an example of a corresponding device described herein.

[0130] Slot configuration 500 illustrates an example of a mix of FD and HD slots scheduled by DCI grant 505, wherein two FD slots (slot n and slot n+1) and two HD slots (slot n+2 and slot n+3) are shown by way of example only. The two FD slots shown in slot configuration 500 include two SBFD slots, although the techniques described may be applicable to IBFD slots. SBFD slots during slot n may include downlink subband 540, uplink subband 545, and downlink subband 550. SBFD slots during slot n+1 may include downlink subband 555, uplink subband 560, and downlink subband 565. HD slots during slot n+2 may be downlink slot 570. HD slots during slot n+3 may be downlink slot 575. SBFD slots may also include one or more gap bands or guard bands that separate adjacent subbands.

[0131] Timeslot configuration 500 illustrates an example where a DCI grant 505 schedules two wireless communications in non-contiguous sub-bands during two SBFD timeslots and schedules wireless communications in two subsequent HD timeslots.

[0132] As discussed above, aspects of the techniques discussed herein provide a single DCI to schedule multiple communications during an FD time slot. For example, a network entity may send, provide, or otherwise convey a DCI grant 505 to a UE to schedule communications for the UE. The scheduled communications may be for an FD time slot (e.g., during two SBFD time slots in this example) and for an HD time slot (e.g., during two HD time slots in this example). The UE may receive, obtain, or otherwise identify the DCI grant 505 from the network entity and use the TDRA field indicated in the DCI grant 505 to identify or otherwise determine a first frequency resource for a first RB set (e.g., corresponding to PDSCH 510) and a second frequency resource for a second RB set (e.g., corresponding to PDSCH 515). In this example, the DCI grant 505 may schedule additional communications (e.g., a third communication) for the UE. For example, the TDRA field carried or otherwise conveyed in the DCI grant 505 may point to (e.g., indicate an index or number corresponding to a row in the TDRA table) the M PxSCHs scheduled, where M is a positive integer value corresponding to two or more wireless communications. Some of the communications scheduled by the DCI grant 505 may have the same (e.g., shared) time slot index, signaling that these communications are scheduled during the FD time slot. Other communications scheduled by the DCI grant 505 may have different time slot indices, signaling that these communications are scheduled during the HD time slot.

[0133] exist Figure 5In the non-limiting example illustrated in , this may include DCI grant 505 scheduling PDSCH 510 in downlink subband 540 and PDSCH 515 in downlink subband 550 during time slot n, scheduling PDSCH 520 in downlink subband 555 and PDSCH 525 in downlink subband 565 during time slot n+1, scheduling PDSCH 530 in downlink time slot 570 (e.g., during time slot n+2), and scheduling PDSCH 535 in downlink time slot 575 (e.g., during time slot n+3).

[0134] The UE may use the TDRA field indicated in the DCI grant 505 to identify or otherwise determine that FD communications and HD communications are being scheduled. The UE may then interpret the FDRA field indicated in the DCI grant 505 based on the communications scheduled during the FD time slot or during the HD time slot. For example, the FDRA field may be interpreted relative to the downlink subband 540 of the PDSCH 510 and relative to the downlink subband 550 of the PDSCH 515, similarly for time slot n+1, relative to the downlink frequency band during time slot n+2, and similarly for time slot n+3. For example, the FDRA field may be interpreted relative to the subband or frequency band and used to identify or otherwise determine the starting RB of the first RB in each set of RBs allocated for each scheduled communication. In some examples, the UE may be configured with a BWP for the HD time slot. In this case, the FDRA field may be interpreted relative to the BWP during the HD time slot.

[0135] Therefore, the UE and the network entity can perform wireless communications (e.g., first communications and second communications) in the first subband or frequency band and the second subband or frequency band, respectively, according to the first frequency resources and the second frequency resources (e.g., the first RB set and the second RB set, respectively) during the FD time slot and the HD time slot according to the DCI authorization 505.

[0136] Figure 6 A block diagram 600 of a device 605 supporting TDRA for scheduling multiple transmissions across subbands 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).

[0137] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to TDRAs that schedule multiple transmissions across subbands). 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.

[0138] 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 related to TDRAs that schedule multiple transmissions across subbands, data channels, information channels). 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.

[0139] 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 TDRA for scheduling multiple transmissions across subbands 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.

[0140] 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).

[0141] 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, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0142] 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.

[0143] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. For example, the communication manager 620 may be configured to or otherwise support a component for receiving a grant to schedule communications during an FD time slot, the communications comprising a first communication using a first one or more RB sets and a second communication using a second one or more RB sets. The communication manager 620 may be configured to or otherwise support a component for identifying a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based on a TDRA field indicated in the grant. The communication manager 620 may be configured to or otherwise support a component for performing the communication using the first frequency resource and the second frequency resource during the FD time slot.

[0144] By including or configuring a communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling or otherwise coupled to the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) may support techniques for improving the scheduling of wireless communications in FD time slots using the TDRA field to carry or otherwise convey an indication that the communication is scheduled in an FD time slot, and accordingly the FDRA field may be interpreted relative to a subband or frequency band in the FD time slot.

[0145] Figure 7A block diagram 700 of a device 705 supporting TDRA for scheduling multiple transmissions across subbands 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).

[0146] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to TDRAs that schedule multiple transmissions across subbands). The information may be passed to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0147] 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 related to TDRAs that schedule multiple transmissions across subbands, data channels, information channels). 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.

[0148] The device 705 or its various components may be examples of components for performing various aspects of TDRA for scheduling multiple transmissions across subbands as described herein. For example, the communication manager 720 may include a scheduling manager 725, a frequency manager 730, an FD communication manager 735, 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 perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. 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.

[0149] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The scheduling manager 725 may be configured to or otherwise support components for receiving a grant to schedule communications during an FD time slot, the communications comprising a first communication using a first one or more RB sets and a second communication using a second one or more RB sets. The frequency manager 730 may be configured to or otherwise support components for identifying a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based on a TDRA field indicated in the grant. The FD communication manager 735 may be configured to or otherwise support components for performing the communication using the first frequency resource and the second frequency resource during the FD time slot.

[0150] Figure 8 A block diagram 800 of a communication manager 820 supporting TDRA for scheduling multiple transmissions across subbands 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 TDRA for scheduling multiple transmissions across subbands as described herein. For example, the communication manager 820 may include a scheduling manager 825, a frequency manager 830, an FD communication manager 835, an FD time slot manager 840, an RB manager 845, an FDRA manager 850, a multi-slot scheduling manager 855, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0151] According to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The scheduling manager 825 may be configured to or otherwise support components for receiving a grant to schedule communications during an FD time slot, the communications comprising a first communication using a first one or more RB sets and a second communication using a second one or more RB sets. The frequency manager 830 may be configured to or otherwise support components for identifying a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based on a TDRA field indicated in the grant. The FD communication manager 835 may be configured to or otherwise support components for performing the communication using the first frequency resource and the second frequency resource during the FD time slot.

[0152] In some examples, the FD slot manager 840 may be configured to or otherwise support components for performing the following operations: identifying a first slot index for the first communication and a second slot index for the second communication based on the TDRA field. In some examples, the FD slot manager 840 may be configured to or otherwise support components for performing the following operations: determining that the authorization is scheduled for communication during the FD slot based on the first slot index and the second slot index indicating a shared slot index.

[0153] In some examples, the FD slot manager 840 may be configured to or otherwise support components for performing the following operations: identifying a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication based on the grant. In some examples, the FD slot manager 840 may be configured to or otherwise support components for performing the following operations: determining that the second communication is a repetition of the first communication based on the first redundancy version and the second redundancy version being the same redundancy version and the first codeword and the second codeword being the same codeword.

[0154] In some examples, the FD slot manager 840 may be configured to or otherwise support components for performing the following operations: identifying a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication based on the grant. In some examples, the FD slot manager 840 may be configured to or otherwise support components for performing the following operations: determining that the first communication and the second communication are different communications based on the first redundancy version and the second redundancy version being different redundancy versions and the first codeword and the second codeword being different codewords.

[0155] In some examples, the FD time slot manager 840 may be configured to or otherwise support components for performing the following operations: identifying a first start symbol for the first communication during the FD time slot and a second start symbol for the second communication during the FD time slot based on the TDRA field, wherein the first start symbol and the second start symbol include the same start symbol or different start symbols.

[0156] In some examples, the RB manager 845 may be configured to or otherwise support components for performing the following operations: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on the FDRA field indicated in the grant. In some examples, the RB manager 845 may be configured to or otherwise support components for performing the following operations: identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on the first starting RB.

[0157] In some examples, the FDRA manager 850 may be configured to or otherwise support components for performing the following operations: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on a first portion of the FDRA field indicated in the grant. In some examples, the FDRA manager 850 may be configured to or otherwise support components for performing the following operations: identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on a second portion of the FDRA field.

[0158] In some examples, the multi-slot scheduling manager 855 may be configured to or otherwise support components for performing the following operations: based on the grant, identifying the first communication and the second communication to be scheduled during the FD time slot based on a shared time slot index associated with the first communication and the second communication and a third communication to be scheduled during the HD time slot based on a time slot index different from the shared time slot index. In some examples, the first frequency resource and the second frequency resource include different subbands during SBFD, or include overlapping frequency resources during IBFD time slots.

[0159] Fig. 9 A diagram of a system 900 including a device 905 supporting TDRA for scheduling multiple transmissions across subbands 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 a component 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., a bus 945).

[0160] I / O controller 910 can manage input signals and output signals of device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can 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.

[0161] 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, wired or wireless links, 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.

[0162] 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 include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0163] 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 enable the device 905 to perform various functions (e.g., functions or tasks that support scheduling multiple transmitted TDRAs across subbands). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0164] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE. For example, the communication manager 920 may be configured to or otherwise support a component for receiving a grant to schedule communications during an FD time slot, the communications comprising a first communication using a first one or more RB sets and a second communication using a second one or more RB sets. The communication manager 920 may be configured to or otherwise support a component for identifying a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based on a TDRA field indicated in the grant. The communication manager 920 may be configured to or otherwise support a component for performing the communication using the first frequency resource and the second frequency resource during the FD time slot.

[0165] By including or configuring a communication manager 920 according to the examples described herein, the device 905 may support techniques for improving the scheduling of wireless communications in FD time slots by using the TDRA field to carry or otherwise convey an indication that a communication is scheduled in an FD time slot, and accordingly the FDRA field may be interpreted relative to a subband or frequency band in the FD time slot.

[0166] 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 scheduling multiple transmitted TDRAs across subbands as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0167] Fig.10 A block diagram 1000 of a device 1005 supporting TDRA for scheduling multiple transmissions across subbands 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).

[0168] 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 passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0169] The transmitter 1015 may provide 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.

[0170] 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 TDRA for scheduling multiple transmissions across subbands 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.

[0171] 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, 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).

[0172] 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 functionality 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, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0173] 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.

[0174] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to or otherwise support components for performing the following operations: identifying, for the UE, a first frequency resource for a first one or more RB sets associated with a first communication during an FD time slot and a second frequency resource for a second one or more RB sets associated with a second communication during the FD time slot. The communication manager 1020 may be configured to or otherwise support components for performing the following operations: sending an authorization to the UE to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource. The communication manager 1020 may be configured to or otherwise support components for performing the following operations: performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0175] By including or configuring a communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) may support techniques for improving the scheduling of wireless communications in FD time slots by using the TDRA field to carry or otherwise convey an indication that the communication is scheduled in an FD time slot, and accordingly the FDRA field may be interpreted relative to a subband or frequency band in the FD time slot.

[0176] Fig.11 A block diagram 1100 of a device 1105 supporting TDRA for scheduling multiple transmissions across subbands 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).

[0177] 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 passed 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.

[0178] The transmitter 1115 may provide 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 transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by transmitting 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.

[0179] The device 1105 or its various components may be examples of components for performing various aspects of TDRA for scheduling multiple transmissions across subbands as described herein. For example, the communication manager 1120 may include a frequency manager 1125, a scheduling manager 1130, an FD communication manager 1135, 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 perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 1110, the transmitter 1115, or both. 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.

[0180] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The frequency manager 1125 may be configured to or otherwise support components for performing the following operations: identifying, for the UE, a first frequency resource for a first one or more RB sets associated with a first communication during an FD time slot and a second frequency resource for a second one or more RB sets associated with a second communication during the FD time slot. The scheduling manager 1130 may be configured to or otherwise support components for performing the following operations: sending an authorization to the UE to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource. The FD communication manager 1135 may be configured to or otherwise support components for performing the following operations: performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0181] Fig.12 A block diagram 1200 of a communication manager 1220 supporting TDRA for scheduling multiple transmissions across subbands 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 TDRA for scheduling multiple transmissions across subbands as described herein. For example, the communication manager 1220 may include a frequency manager 1225, a scheduling manager 1230, an FD communication manager 1235, an FD time slot manager 1240, an RB manager 1245, an FDRA manager 1250, a multi-slot scheduling manager 1255, or any combination thereof. Each of these components may communicate with each other directly or indirectly (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.

[0182] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The frequency manager 1225 may be configured to or otherwise support components for performing the following operations: identifying, for the UE, a first frequency resource for a first one or more RB sets associated with a first communication during an FD time slot and a second frequency resource for a second one or more RB sets associated with a second communication during the FD time slot. The scheduling manager 1230 may be configured to or otherwise support components for performing the following operations: sending an authorization to the UE to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource. The FD communication manager 1235 may be configured to or otherwise support components for performing the following operations: performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0183] In some examples, the FD timeslot manager 1240 may be configured to or otherwise support components for performing the following operations: identifying a first timeslot index for the first communication and a second timeslot index for the second communication based on the TDRA field, wherein the authorization schedules communication during the FD timeslot based on the first timeslot index and the second timeslot index indicating the same timeslot index.

[0184] In some examples, the FD timeslot manager 1240 may be configured to or otherwise support components for performing the following operations: identifying a first redundant version and a first codeword for the first communication and a second redundant version and a second codeword for the second communication based on the authorization, wherein based on the first redundant version and the second redundant version being the same redundant version and the first codeword and the second codeword being the same codeword, the second communication is a repetition of the first communication.

[0185] In some examples, the FD timeslot manager 1240 may be configured to or otherwise support components for performing the following operations: identifying a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication based on the authorization, wherein the first communication and the second communication are different communications based on the first redundancy version and the second redundancy version being different redundancy versions and the first codeword and the second codeword being different codewords.

[0186] In some examples, the FD time slot manager 1240 may be configured to or otherwise support components for performing the following operations: identifying a first start symbol for the first communication during the FD time slot and a second start symbol for the second communication during the FD time slot based on the TDRA field, wherein the first start symbol and the second start symbol include the same start symbol or different start symbols.

[0187] In some examples, RB manager 1245 may be configured to or otherwise support components for performing the following operations: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on the FDRA field indicated in the grant, wherein a second starting RB of the second one or more RB sets within the second frequency resource is identified based on the first starting RB.

[0188] In some examples, the FDRA manager 1250 may be configured to or otherwise support components for performing the following operations: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on a first portion of the FDRA field indicated in the grant. In some examples, the FDRA manager 1250 may be configured to or otherwise support components for performing the following operations: identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on a second portion of the FDRA field.

[0189] In some examples, the multi-slot scheduling manager 1255 may be configured to or otherwise support components for: identifying, based on the grant, the first communication and the second communication scheduled during the FD time slot based on a shared time slot index associated with the first communication and the second communication, and identifying a third communication scheduled during the HD time slot based on a time slot index different from the shared time slot index. In some examples, the first frequency resource and the second frequency resource include different subbands during SBFD, or include overlapping frequency resources during IBFD time slots.

[0190] Fig.13 A diagram of a system 1300 including a device 1305 supporting TDRA for scheduling multiple transmissions across subbands 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 a component 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 acquisition of 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).

[0191] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. 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 sending or receiving wireless transmissions (e.g., concurrently). 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 a 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 or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. 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 assembly 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 ).

[0192] 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, among other things, memory 1325 may also include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0193] 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 that support scheduling multiple transmitted TDRAs across subbands). 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, virtual machine, or container instance) that can 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 series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed 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 device 1305 may be docked with other components of device 1305, and may process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1305 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that device 1305 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0194] 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 component of different components or divided between different components).

[0195] In some examples, the communication manager 1320 may 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 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1320 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UE 115 in collaboration with the other network entities 105. In some examples, the communication manager 1320 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0196] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for performing the following operations: identifying, for the UE, a first frequency resource for a first one or more RB sets associated with a first communication during an FD time slot and a second frequency resource for a second one or more RB sets associated with a second communication during the FD time slot. The communication manager 1320 may be configured to or otherwise support components for performing the following operations: sending an authorization to the UE to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource. The communication manager 1320 may be configured to or otherwise support components for performing the following operations: performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0197] By including or configuring a communication manager 1320 according to the examples described herein, the device 1305 may support techniques for improving the scheduling of wireless communications in FD time slots by using the TDRA field to carry or otherwise convey an indication that a communication is scheduled in an FD time slot, and accordingly the FDRA field may be interpreted relative to a subband or frequency band in the FD time slot.

[0198] In some examples, the communication manager 1320 may 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 may 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 scheduling multiple transmitted TDRAs across subbands as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0199] Fig.14 A flow chart illustrating a method 1400 for supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown. 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 described UE 115 may be performed. 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.

[0200] At 1405, the method may include receiving an authorization to schedule communications during the FD time slot, the communications including a first communication using a first set of one or more RBs and a second communication using a second set of one or more RBs. 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 described schedule manager 825 is executed.

[0201] At 1410, the method may include identifying, based on the TDRA field indicated in the grant, a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets. 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 in reference to Figure 8 The described frequency manager 830 is implemented.

[0202] At 1415, the method may include performing the communication using the first frequency resource and the second frequency resource during the FD time slot. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described with reference to Figure 8 The described FD communication manager 835 is executed.

[0203] Fig.15 A flow chart illustrating a method 1500 for supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown. 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 described UE 115 may be performed. 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.

[0204] At 1505, the method may include receiving an authorization to schedule communications during the FD time slot, the communications including a first communication using a first set of one or more RBs and a second communication using a second set of one or more RBs. 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 described schedule manager 825 is executed.

[0205] At 1510, the method may include identifying, based on the TDRA field indicated in the grant, a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets. 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 described frequency manager 830 is implemented.

[0206] At 1515, the method may include identifying a first time slot index for the first communication and a second time slot index for the second communication based on the TDRA field. 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 in reference to Figure 8 The described FD time slot manager 840 is executed.

[0207] At 1520, the method may include determining that the authorization is to schedule communications during the FD time slot based on the first time slot index and the second time slot index indicating a shared time slot index. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The described FD time slot manager 840 is executed.

[0208] At 1525, the method may include performing the communication using the first frequency resource and the second frequency resource during the FD time slot. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described with reference to Figure 8 The described FD communication manager 835 is executed.

[0209] Fig.16 A flow chart illustrating a method 1600 for supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. 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.

[0210] At 1605, the method may include receiving an authorization to schedule communications during the FD time slot, the communications including a first communication using a first set of one or more RBs and a second communication using a second set of one or more RBs. 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 Figure 8 The described schedule manager 825 is executed.

[0211] At 1610, the method may include identifying, based on the TDRA field indicated in the grant, a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets. 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 in reference to Figure 8 The described frequency manager 830 is implemented.

[0212] At 1615, the method may include identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on the FDRA field indicated in the grant. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The described RB manager 845 is executed.

[0213] At 1620, the method may include identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on the first starting RB. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 8 The described RB manager 845 is executed.

[0214] At 1625, the method may include performing the communication using the first frequency resource and the second frequency resource during the FD time slot. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described with reference to Figure 8 The described FD communication manager 835 is executed.

[0215] Fig.17 A flow chart illustrating a method 1700 for supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown. 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 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.

[0216] At 1705, the method may include identifying, for the UE, a first frequency resource for a first set of one or more RBs associated with a first communication during the FD time slot and a second frequency resource for a second set of one or more RBs associated with a second communication during the FD time slot. 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 described frequency manager 1225 is executed.

[0217] At 1710, the method may include sending to the UE an authorization to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource. 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 described schedule manager 1230 is executed.

[0218] At 1715, the method may include performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot. 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 FD communication manager 1235 is executed.

[0219] Fig.18 A flow chart illustrating a method 1800 for supporting TDRA for scheduling multiple transmissions across subbands according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. 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.

[0220] At 1805, the method may include identifying, for the UE, a first frequency resource for a first set of one or more RBs associated with a first communication during the FD time slot and a second frequency resource for a second set of one or more RBs associated with a second communication during the FD time slot. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The described frequency manager 1225 is executed.

[0221] At 1810, the method may include identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based on a first portion of the FDRA field indicated in the grant. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.12 The described FDRA manager 1250 is executed.

[0222] At 1815, the method may include identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based on the second portion of the FDRA field. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.12 The described FDRA manager 1250 is executed.

[0223] At 1820, the method may include sending to the UE an authorization to schedule the first communication and the second communication during the FD time slot, the authorization including a TDRA field identifying the first frequency resource and the second frequency resource. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.12 The described schedule manager 1230 is executed.

[0224] At 1825, the method may include performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot. The operations of 1825 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed as described with reference to Fig.12 The described FD communication manager 1235 is executed.

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

[0226] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving an authorization to schedule communications during an FD time slot, the communications comprising a first communication using a first one or more RB sets and a second communication using a second one or more RB sets; identifying a first frequency resource for the first one or more RB sets and a second frequency resource for the second one or more RB sets based at least in part on a TDRA field indicated in the authorization; and performing the communications using the first frequency resource and the second frequency resource during the FD time slot.

[0227] Aspect 2: According to the method described in Aspect 1, the method also includes: identifying a first time slot index for the first communication and a second time slot index for the second communication based at least in part on the TDRA field; and determining the authorization to schedule communication during the FD time slot based at least in part on the first time slot index and the second time slot index indicating a shared time slot index.

[0228] Aspect 3: According to the method described in Aspect 2, the method also includes: identifying a first redundant version and a first codeword for the first communication and a second redundant version and a second codeword for the second communication based at least in part on the authorization; and determining that the second communication is a repetition of the first communication based at least in part on the fact that the first redundant version and the second redundant version are the same redundant version and the first codeword and the second codeword are the same codeword.

[0229] Aspect 4: According to the method described in any one of Aspects 2 to 3, the method further includes: identifying a first redundant version and a first codeword for the first communication and a second redundant version and a second codeword for the second communication based at least in part on the authorization; and determining that the first communication and the second communication are different communications based at least in part on the fact that the first redundant version and the second redundant version are different redundant versions and the first codeword and the second codeword are different codewords.

[0230] Aspect 5: According to the method described in any one of Aspects 2 to 4, the method further includes: identifying a first start symbol for the first communication during the FD time slot and a second start symbol for the second communication during the FD time slot based at least in part on the TDRA field, wherein the first start symbol and the second start symbol include the same start symbol or different start symbols.

[0231] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based at least in part on the FDRA field indicated in the authorization; and identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based at least in part on the first starting RB.

[0232] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based at least in part on a first part of the FDRA field indicated in the authorization; and identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based at least in part on a second part of the FDRA field.

[0233] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: identifying, at least in part based on the authorization, the first communication and the second communication scheduled during the FD time slot at least in part based on a shared time slot index associated with the first communication and the second communication, and a third communication scheduled during the half-duplex time slot at least in part based on a time slot index different from the shared time slot index.

[0234] Aspect 9: The method according to any one of aspects 1 to 8, wherein the first frequency resource and the second frequency resource include different sub-bands during SBFD, or include overlapping frequency resources during IBFD time slots.

[0235] Aspect 10: A method for performing wireless communications at a network entity, the method comprising: identifying for a UE a first frequency resource for a first one or more RB sets associated with a first communication during an FD time slot and a second frequency resource for a second one or more RB sets associated with a second communication during the FD time slot; sending an authorization to the UE to schedule the first communication and the second communication during the FD time slot, the authorization comprising a TDRA field identifying the first frequency resource and the second frequency resource; and performing the communication with the UE using the first frequency resource and the second frequency resource during the FD time slot.

[0236] Aspect 11: According to the method according to Aspect 10, the method also includes: identifying a first time slot index for the first communication and a second time slot index for the second communication based at least in part on the TDRA field, wherein the authorization schedules communication during the FD time slot based at least in part on the first time slot index and the second time slot index indicating the same time slot index.

[0237] Aspect 12: According to the method according to Aspect 11, the method also includes: identifying a first redundant version and a first codeword for the first communication and a second redundant version and a second codeword for the second communication based at least in part on the authorization, wherein the second communication is a repetition of the first communication based at least in part on the fact that the first redundant version and the second redundant version are the same redundant version and the first codeword and the second codeword are the same codeword.

[0238] Aspect 13: According to the method described in any one of Aspects 11 to 12, the method further includes: identifying a first redundant version and a first codeword for the first communication and a second redundant version and a second codeword for the second communication based at least in part on the authorization, wherein the first communication and the second communication are different communications based at least in part on the fact that the first redundant version and the second redundant version are different redundant versions and the first codeword and the second codeword are different codewords.

[0239] Aspect 14: According to the method described in any one of Aspects 11 to 13, the method further includes: identifying a first start symbol for the first communication during the FD time slot and a second start symbol for the second communication during the FD time slot based at least in part on the TDRA field, wherein the first start symbol and the second start symbol include the same start symbol or different start symbols.

[0240] Aspect 15: According to the method described in any one of Aspects 10 to 14, the method further includes: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based at least in part on the FDRA field indicated in the authorization, wherein a second starting RB of the second one or more RB sets within the second frequency resource is identified at least in part based on the first starting RB.

[0241] Aspect 16: According to the method described in any one of Aspects 10 to 15, the method further includes: identifying a first starting RB of the first one or more RB sets within the first frequency resource for the first communication based at least in part on a first part of the FDRA field indicated in the authorization; and identifying a second starting RB of the second one or more RB sets within the second frequency resource for the second communication based at least in part on a second part of the FDRA field.

[0242] Aspect 17: According to the method described in any one of Aspects 10 to 16, the method further includes: identifying, at least in part based on the authorization, the first communication and the second communication scheduled during the FD time slot at least in part based on a shared time slot index associated with the first communication and the second communication, and a third communication scheduled during the half-duplex time slot at least in part based on a time slot index different from the shared time slot index.

[0243] Aspect 18: The method according to any one of aspects 10 to 17, wherein the first frequency resource and the second frequency resource include different sub-bands during SBFD, or include overlapping frequency resources during IBFD time slots.

[0244] Aspect 19: 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 9.

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

[0246] Aspect 21: A non-transitory computer-readable medium storing a 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 9.

[0247] Aspect 22: 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 10 to 18.

[0248] Aspect 23: 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 10 to 18.

[0249] Aspect 24: 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 10 to 18.

[0250] 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.

[0251] 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.

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

[0253] 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).

[0254] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored 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 this 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 functions are implemented at different physical locations.

[0255] Computer-readable media include both non-transient computer storage media and communication media, and the communication media include any media that facilitates the transfer of computer programs 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 devices, magnetic disk storage devices or other magnetic storage devices, or can 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 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 microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0256] 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".

[0257] 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.

[0258] 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 or other subsequent reference labels.

[0259] 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 "having advantages over other examples." The specific embodiments include 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.

[0260] 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. 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 a grant to schedule communications during a full-duplex time slot, the communications comprising a first communication using a first set of one or more resource blocks and a second communication using a second set of one or more resource blocks; identifying, based at least in part on a time domain resource allocation field indicated in the grant, a first frequency resource for the first one or more sets of resource blocks and a second frequency resource for the second one or more sets of resource blocks; as well as The communication is performed using the first frequency resource and the second frequency resource during the full-duplex time slot.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: identifying a first time slot index for the first communication and a second time slot index for the second communication based at least in part on the time domain resource allocation field; and The grant is determined to schedule communications during the full-duplex time slot based at least in part on the first time slot index and the second time slot index indicating a shared time slot index.

3. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication based at least in part on the grant; and The second communication is determined to be a repeat of the first communication based at least in part on the first redundancy version and the second redundancy version being the same redundancy version and the first codeword and the second codeword being the same codeword.

4. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication based at least in part on the grant; and The first communication and the second communication are determined to be different communications based at least in part on the first redundancy version and the second redundancy version being different redundancy versions and the first codeword and the second codeword being different codewords.

5. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: A first start symbol for the first communication during the full-duplex time slot and a second start symbol for the second communication during the full-duplex time slot are identified based at least in part on the time domain resource allocation field, wherein the first start symbol and the second start symbol comprise the same start symbol or different start symbols.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a first starting resource block of the first one or more sets of resource blocks within the first frequency resource for use for the first communication based at least in part on a frequency domain resource allocation field indicated in the grant; and A second starting resource block of the second set of one or more resource blocks within the second frequency resource for use for the second communication is identified based at least in part on the first starting resource block.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a first starting resource block of the first set of one or more resource blocks within the first frequency resource for use for the first communication based at least in part on a first portion of a frequency domain resource allocation field indicated in the grant; and A second starting resource block of the second set of one or more resource blocks within the second frequency resource for the second communication is identified based at least in part on a second portion of the frequency-domain resource allocation field.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The first and second communications scheduled during the full-duplex time slot based at least in part on a shared time slot index associated with the first and second communications and a third communication scheduled during a half-duplex time slot based at least in part on a time slot index different from the shared time slot index are identified based at least in part on the grant.

9. The apparatus of claim 1, wherein the first frequency resource and the second frequency resource comprise different sub-bands during sub-band full-duplex (SBFD) or comprise overlapping frequency resources during an in-band full-duplex (IBFD) time slot.

10. 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: identifying, for a user equipment (UE), first frequency resources for a first set of one or more resource blocks associated with a first communication during a full-duplex time slot and second frequency resources for a second set of one or more resource blocks associated with a second communication during the full-duplex time slot; sending, to the UE, an authorization to schedule the first communication and the second communication during the full-duplex time slot, the authorization comprising a time domain resource allocation field identifying the first frequency resource and the second frequency resource; as well as The communicating is performed with the UE using the first frequency resources and the second frequency resources during the full-duplex timeslot.

11. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: A first time slot index for the first communication and a second time slot index for the second communication are identified based at least in part on the time domain resource allocation field, wherein the grant schedules communication during the full-duplex time slot based at least in part on the first time slot index and the second time slot index indicating the same time slot index.

12. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: A first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication are identified based at least in part on the grant, wherein the second communication is a repeat of the first communication based at least in part on the first redundancy version and the second redundancy version being the same redundancy version and the first codeword and the second codeword being the same codeword.

13. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: A first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication are identified based at least in part on the grant, wherein the first communication and the second communication are different communications based at least in part on the first redundancy version and the second redundancy version being different redundancy versions and the first codeword and the second codeword being different codewords.

14. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: A first start symbol for the first communication during the full-duplex time slot and a second start symbol for the second communication during the full-duplex time slot are identified based at least in part on the time domain resource allocation field, wherein the first start symbol and the second start symbol comprise the same start symbol or different start symbols.

15. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: A first starting resource block of the first one or more sets of resource blocks within the first frequency resource for the first communication is identified at least in part based on a frequency domain resource allocation field indicated in the grant, wherein a second starting resource block of the second one or more sets of resource blocks within the second frequency resource is identified at least in part based on the first starting resource block.

16. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a first starting resource block of the first set of one or more resource blocks within the first frequency resource for use for the first communication based at least in part on a first portion of a frequency domain resource allocation field indicated in the grant; and A second starting resource block of the second set of one or more resource blocks within the second frequency resource for the second communication is identified based at least in part on a second portion of the frequency-domain resource allocation field.

17. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: The first and second communications scheduled during the full-duplex time slot based at least in part on a shared time slot index associated with the first and second communications and a third communication scheduled during a half-duplex time slot based at least in part on a time slot index different from the shared time slot index are identified based at least in part on the grant.

18. The apparatus of claim 10, wherein the first frequency resource and the second frequency resource comprise different sub-bands during sub-band full-duplex (SBFD) or comprise overlapping frequency resources during an in-band full-duplex (IBFD) time slot.

19. A method for wireless communication at a user equipment (UE), the method comprising: receiving a grant to schedule communications during a full-duplex time slot, the communications comprising a first communication using a first set of one or more resource blocks and a second communication using a second set of one or more resource blocks; identifying, based at least in part on a time domain resource allocation field indicated in the grant, a first frequency resource for the first one or more sets of resource blocks and a second frequency resource for the second one or more sets of resource blocks; as well as The communication is performed using the first frequency resource and the second frequency resource during the full-duplex time slot.

20. The method according to claim 19, further comprising: identifying a first time slot index for the first communication and a second time slot index for the second communication based at least in part on the time domain resource allocation field; as well as The grant is determined to schedule communications during the full-duplex time slot based at least in part on the first time slot index and the second time slot index indicating a shared time slot index.

21. The method according to claim 20, further comprising: identifying a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication based at least in part on the grant; as well as The second communication is determined to be a repeat of the first communication based at least in part on the first redundancy version and the second redundancy version being the same redundancy version and the first codeword and the second codeword being the same codeword.

22. The method according to claim 20, further comprising: identifying a first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication based at least in part on the grant; as well as The first communication and the second communication are determined to be different communications based at least in part on the first redundancy version and the second redundancy version being different redundancy versions and the first codeword and the second codeword being different codewords.

23. The method according to claim 20, further comprising: A first start symbol for the first communication during the full-duplex time slot and a second start symbol for the second communication during the full-duplex time slot are identified based at least in part on the time domain resource allocation field, wherein the first start symbol and the second start symbol comprise the same start symbol or different start symbols.

24. The method according to claim 19, further comprising: identifying a first starting resource block of the first set of one or more resource blocks within the first frequency resource for the first communication based at least in part on a frequency domain resource allocation field indicated in the grant; as well as A second starting resource block of the second set of one or more resource blocks within the second frequency resource for use for the second communication is identified based at least in part on the first starting resource block.

25. The method of claim 19, further comprising: identifying a first starting resource block of the first set of one or more resource blocks within the first frequency resource for the first communication based at least in part on a first portion of a frequency domain resource allocation field indicated in the grant; as well as A second starting resource block of the second set of one or more resource blocks within the second frequency resource for the second communication is identified based at least in part on a second portion of the frequency-domain resource allocation field.

26. The method of claim 19, further comprising: The first and second communications scheduled during the full-duplex time slot based at least in part on a shared time slot index associated with the first and second communications and a third communication scheduled during a half-duplex time slot based at least in part on a time slot index different from the shared time slot index are identified based at least in part on the grant.

27. The method of claim 19, wherein the first frequency resource and the second frequency resource comprise different sub-bands during sub-band full-duplex (SBFD) or comprise overlapping frequency resources during an in-band full-duplex (IBFD) time slot.

28. A method for wireless communication at a network entity, the method comprising: identifying, for a user equipment (UE), first frequency resources for a first set of one or more resource blocks associated with a first communication during a full-duplex time slot and second frequency resources for a second set of one or more resource blocks associated with a second communication during the full-duplex time slot; sending, to the UE, an authorization to schedule the first communication and the second communication during the full-duplex time slot, the authorization comprising a time domain resource allocation field identifying the first frequency resource and the second frequency resource; as well as The communicating is performed with the UE using the first frequency resources and the second frequency resources during the full-duplex timeslot.

29. The method according to claim 28, further comprising: A first time slot index for the first communication and a second time slot index for the second communication are identified based at least in part on the time domain resource allocation field, wherein the grant schedules communication during the full-duplex time slot based at least in part on the first time slot index and the second time slot index indicating the same time slot index.

30. The method according to claim 29, further comprising: A first redundancy version and a first codeword for the first communication and a second redundancy version and a second codeword for the second communication are identified based at least in part on the grant, wherein the second communication is a repeat of the first communication based at least in part on the first redundancy version and the second redundancy version being the same redundancy version and the first codeword and the second codeword being the same codeword.

Images