Uplink shared channel resource allocation for multi-cell scheduling

Abstract

Methods, systems, and devices for wireless communication for uplink shared channel resource allocation for multi-cell scheduling are described. A user equipment (UE) may receive a downlink control information (DCI) message including a first set of bits and a second set of bits defining a resource allocation across a plurality of network entities, and an uplink shared channel message indicating scheduling to the first network entity and the second network entity according to a resource allocation type. The first set of bits may indicate one or more resource block indices, and the second set of bits may indicate one or more resource block set indices. The UE may transmit the uplink shared channel message to the first network entity and the second network entity according to the first set of bits and the second set of bits.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Patent Application No. 17 / 884,326, filed August 9, 2022, entitled “UPLINK SHAREDCHANNEL RESOURCE ALLOCATION FOR MULTI-CELL SCHEDULING,” which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including uplink shared channel resource allocation for multi-cell scheduling. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. 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, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for a communication device, which may be referred to as a User Equipment (UE).

[0005] In some wireless communication systems, network entities may send downlink control information (DCI) messages to a UE or other receiving devices. These DCI messages may include resource allocation information indicating uplink resources available for the UE. Techniques for instructing resource allocation information to the UE may be improved. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting uplink shared channel resource allocation for multi-cell scheduling. For example, the described technology provides a downlink control information (DCI) message or some other control message to indicate resource allocation information to a receiving device (e.g., a user equipment (UE)) indicating uplink resources available for uplink transmission by the UE (e.g., physical uplink shared channel (PUSCH) transmission). The DCI message may indicate that resource allocation type 2 is applied to schedule the uplink resources. In some cases, the DCI message (e.g., a single DCI message) may be configured to indicate resource allocation for multiple network entities, cells, etc., and according to resource allocation type 2, the DCI message may include at least two bit sets, wherein the first bit set (e.g., N bits) may indicate the scheduled resource blocks and may be referred to as resource block bits, and the second bit set (e.g., Y bits) may indicate the scheduled set of resource blocks and may be referred to as resource block set bits. In some examples, the resource block bit, the resource block set bit, or both may be common across multiple network entities, cells, etc. In some other examples, the DCI message may include multiple sets of resource block bits, each associated with a different network entity. Similarly, the DCI message may include multiple sets of resource block set bits, each associated with a different network entity. In some cases, the DCI message may include multiple sets of resource block bits, each associated with a different group of network entities. Similarly, the DCI message may include multiple sets of resource block set bits, each associated with a different group of network entities. Therefore, the UE can receive the DCI message including one or more sets of resource block bits and one or more sets of resource block set bits, and the UE can send uplink messages to the multiple network entities based on the resource block bits and resource block set bits.

[0007] A method for wireless communication at a UE is described. The method may include: receiving a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; receiving a first set indicating one or more resource block indices based on the resource allocation type; receiving a second set indicating one or more resource block set indices based on the resource allocation type; and transmitting the uplink shared channel message to at least the first network entity and the second network entity according to the first set and the second set.

[0008] 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 are executable by the processor to cause the apparatus to: receive a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; receive a first set indicating one or more resource block indices based on the resource allocation type; receive a second set indicating one or more resource block set indices based on the resource allocation type; and transmit the uplink shared channel message to at least the first network entity and the second network entity according to the first set and the second set.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: components for receiving a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; components for receiving a first set indicating one or more resource block indices based on the resource allocation type; components for receiving a second set indicating one or more resource block set indices based on the resource allocation type; and components for transmitting the uplink shared channel message to at least the first network entity and the second network entity according to the first set and the second set.

[0010] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; receive a first set indicating one or more resource block indices based on the resource allocation type; receive a second set indicating one or more resource block set indices based on the resource allocation type; and transmit the uplink shared channel message to at least the first network entity and the second network entity according to the first set and the second set.

[0011] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first set may include operations, features, components, or instructions for: receiving the first set, which may be associated with at least the first network entity and the second network entity, wherein the one or more resource block indexes may be assigned to send the uplink shared channel message to at least the first network entity and the second network entity.

[0012] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the alignment based on the reference point is different for the first network entity and the second network entity, and the interleaving pattern of the one or more resource block indexes may be different for the first network entity and the second network entity according to the first set that may be associated with at least the first network entity and the second network entity, and the reference point may be used to identify the resource block index.

[0013] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first set may include operations, features, components, or instructions for receiving the first set comprising a subset of bits, wherein each subset of bits may be associated with a different network entity, and wherein each subset of bits indicates a set of resource block indexes associated with a corresponding network entity.

[0014] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the bit subset includes a first bit subset associated with the first network entity and a second bit subset associated with the second network entity, based on the fact that the first network entity and the second network entity are different network entities.

[0015] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first subset indicates a first set of resource block indices allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second set of resource block indices allocated for sending the uplink shared channel message to the second network entity.

[0016] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the subset of bits included in the first set may be based on the number of network entities configured to be scheduled by the DCI message.

[0017] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the second set of bits may include operations, features, components, or instructions for receiving a plurality of first set sets, each plurality of which may be associated with a different network entity, and wherein each plurality of which indicates a set of resource block indexes associated with a corresponding network entity.

[0018] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the plurality of first-order sets may be based on the number of network entities configured to be scheduled by the DCI message.

[0019] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first set may include operations, features, components, or instructions for receiving the first set comprising a subset of bits, wherein each subset of bits may be associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with a network entity in the corresponding group.

[0020] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bit subsets included in the first set may be based on the number of groups of network entities configured to be scheduled by the DCI message.

[0021] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first network entity and the second network entity may be included in the same group of network entities or in different groups of network entities.

[0022] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the second bit set may include operations, features, components, or instructions for receiving the second bit set that may be commonly associated with at least the first network entity and the second network entity based on a resource block set assigned to each network entity by a resource block index, wherein the one or more resource block set indices may be allocated for sending the uplink shared channel message to at least the first network entity and the second network entity.

[0023] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bits included in the second bit set may be based on the network entities in at least the first network entity and the second network entity being associated with the highest number of resource block sets.

[0024] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the resource block set configuration associated with the first network entity may differ from the resource block set configuration associated with the second network entity, based on the intra-cell guard band configuration associated with the respective first and second network entities.

[0025] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, each resource block set configuration may indicate a starting common resource block index and the number of common resource blocks associated with each resource block set, wherein the starting common resource block index, the number of common resource blocks, or both are different for one or more resource block sets configured for the first network entity and the second network entity.

[0026] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the second set of bits may include operations, features, components, or instructions for receiving the second set of bits comprising subsets of bits, wherein each subset of bits may be associated with a different network entity, and wherein each subset of bits indicates a set of resource block set indexes associated with a corresponding network entity.

[0027] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the bit subset includes a first bit subset associated with the first network entity and a second bit subset associated with the second network entity, based on the fact that the first network entity and the second network entity are different network entities.

[0028] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first subset indicates a first resource block set index set allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second resource block set index set allocated for sending the uplink shared channel message to the first network entity.

[0029] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the subset of bits included in the first set may be based on the number of network entities configured to be scheduled by the DCI message.

[0030] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the second bit set may include operations, features, components, or instructions for receiving a plurality of second bit sets, each plurality of which may be associated with a different network entity, and wherein each plurality of which indicates a set of resource block set indices associated with a corresponding network entity.

[0031] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the plurality of second bit sets may be based on the number of network entities configured to be scheduled by the DCI message.

[0032] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the second set of bits may include operations, features, components, or instructions for receiving the second set of bits comprising subsets of bits, wherein each subset of bits may be associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with a network entity in the corresponding group.

[0033] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bit subsets included in the second bit set may be based on the number of groups of network entities configured to be scheduled by the DCI message.

[0034] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first network entity and the second network entity may be included in the same group of network entities or in different groups of network entities.

[0035] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the second bit set may include operations, features, components, or instructions for receiving the second bit set that may be associated with at least the first network entity and the second network entity, based on a resource block set index assigned to a resource block set across at least the first network entity and the second network entity, wherein each bit in the second bit set corresponds to a different resource block set index.

[0036] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the second bit set indicates that a contiguous set of resource blocks associated with the first network entity can be scheduled by the DCI message, and the methods, apparatuses, and nontransitory computer-readable media may include further operations, features, components, or instructions for identifying resource blocks between the contiguous resource block sets that are associated with the same network entity for scheduling the uplink shared channel message.

[0037] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the second bit set indicates that a first set of resource blocks associated with the first network entity and a contiguous set of resource blocks associated with the second network entity are available for scheduling by the DCI message, and the methods, apparatuses, and nontransitory computer-readable media may include further operations, features, components, or instructions for identifying resource blocks between the first set of resource blocks and the contiguous set of resource blocks that may not be scheduled for the uplink shared channel message based on the association of the first set of resource blocks and the contiguous set of resource blocks with different network entities.

[0038] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bits included in the second bit set may be based on the number of resource block sets allocated across at least the first network entity and the second network entity.

[0039] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the first set and the second set may include operations, features, components, or instructions for receiving a message including the first set and the second set.

[0040] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the message may be the DCI message.

[0041] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the format of the DCI message may be based on the DCI message that schedules the uplink shared channel message to at least the first network entity and the second network entity according to the resource allocation type.

[0042] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bits included in the first set is based on the subcarrier spacing associated with the one or more resource blocks.

[0043] A method for wireless communication at a first network entity is described. The method may include: transmitting a DCI message indicating an uplink shared channel message scheduled to at least the first and second network entities according to a resource allocation type; transmitting a first set indicating one or more resource block indices based on the resource allocation type; transmitting a second set indicating one or more resource block set indices based on the resource allocation type; and receiving the uplink shared channel message according to the first set and the second set.

[0044] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: transmit a DCI message indicating an uplink shared channel message scheduled to at least the first and second network entities according to a resource allocation type; transmit a first set indicating one or more resource block indices based on the resource allocation type; transmit a second set indicating one or more resource block set indices based on the resource allocation type; and receive the uplink shared channel message according to the first set and the second set.

[0045] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: components for transmitting a DCI message indicating an uplink shared channel message scheduled to at least the first and second network entities according to a resource allocation type; components for transmitting a first set indicating one or more resource block indices based on the resource allocation type; components for transmitting a second set indicating one or more resource block set indices based on the resource allocation type; and components for receiving the uplink shared channel message according to the first set and the second set.

[0046] A non-transitory computer-readable medium is described, storing code for wireless communication at a first network entity. The code may include instructions executable by a processor to: transmit a DCI message indicating an uplink shared channel message scheduled to at least the first and second network entities according to a resource allocation type; transmit a first set indicating one or more resource block indices based on the resource allocation type; transmit a second set indicating one or more resource block set indices based on the resource allocation type; and receive the uplink shared channel message according to the first set and the second set.

[0047] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the first set may include operations, features, components, or instructions for sending the first set, which may be associated with at least the first network entity and the second network entity, wherein the one or more resource block indexes may be assigned to send the uplink shared channel message to at least the first network entity and the second network entity.

[0048] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the alignment based on the reference point is different for the first network entity and the second network entity, and the interleaving pattern of the one or more resource block indexes may be different for the first network entity and the second network entity according to the first set that may be associated with at least the first network entity and the second network entity, and the reference point may be used to identify the resource block index.

[0049] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the first set may include operations, features, components, or instructions for transmitting the first set comprising a subset of bits, wherein each subset of bits may be associated with a different network entity, and wherein each subset of bits indicates a set of resource block indexes associated with a corresponding network entity.

[0050] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the bit subset includes a first bit subset associated with the first network entity and a second bit subset associated with the second network entity, based on the fact that the first network entity and the second network entity are different network entities.

[0051] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first subset indicates a first set of resource block indices allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second set of resource block indices allocated for sending the uplink shared channel message to the second network entity.

[0052] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the subset of bits included in the first set may be based on the number of network entities configured to be scheduled by the DCI message.

[0053] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the first set may include operations, features, components, or instructions for sending a plurality of first sets, each plurality of which may be associated with a different network entity, and wherein each plurality of which indicates a set of resource block indexes associated with a corresponding network entity.

[0054] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the plurality of first-order sets may be based on the number of network entities configured to be scheduled by the DCI message.

[0055] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the first set may include operations, features, components, or instructions for transmitting the first set comprising a subset of bits, wherein each subset of bits may be associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with a network entity in the corresponding group.

[0056] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bit subsets included in the first set may be based on the number of groups of network entities configured to be scheduled by the DCI message.

[0057] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first network entity and the second network entity may be included in the same group of network entities or in different groups of network entities.

[0058] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the second bit set may include operations, features, components, or instructions for transmitting the second bit set that may be associated with at least the first network entity and the second network entity based on a resource block set assigned to each network entity by a resource block index, wherein the one or more resource block set indices may be assigned to transmit the uplink shared channel message to at least the first network entity and the second network entity.

[0059] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bits included in the second bit set may be based on the network entities in at least the first network entity and the second network entity being associated with the highest number of resource block sets.

[0060] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the resource block set configuration associated with the first network entity may differ from the resource block set configuration associated with the second network entity, based on the intra-cell guard band configuration associated with the respective first and second network entities.

[0061] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, each resource block set configuration may indicate a starting common resource block index and the number of common resource blocks associated with each resource block set, wherein the starting common resource block index, the number of common resource blocks, or both are different for one or more resource block sets configured for the first network entity and the second network entity.

[0062] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the second set of bits may include operations, features, components, or instructions for transmitting the second set of bits comprising subsets of bits, wherein each subset of bits may be associated with a different network entity, and wherein each subset of bits indicates a set of resource block set indexes associated with a corresponding network entity.

[0063] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the bit subset includes a first bit subset associated with the first network entity and a second bit subset associated with the second network entity, based on the fact that the first network entity and the second network entity are different network entities.

[0064] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first subset indicates a first resource block set index set allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second resource block set index set allocated for sending the uplink shared channel message to the first network entity.

[0065] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the subset of bits included in the first set may be based on the number of network entities configured to be scheduled by the DCI message.

[0066] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the second bit set may include operations, features, components, or instructions for sending a plurality of second bit sets, each plurality of which may be associated with a different network entity, and wherein each plurality of which indicates a set of resource block set indices associated with a corresponding network entity.

[0067] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of the plurality of second bit sets may be based on the number of network entities configured to be scheduled by the DCI message.

[0068] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the second set of bits may include operations, features, components, or instructions for transmitting the second set of bits comprising subsets of bits, wherein each subset of bits may be associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with a network entity in the corresponding group.

[0069] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bit subsets included in the second bit set may be based on the number of groups of network entities configured to be scheduled by the DCI message.

[0070] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the first network entity and the second network entity may be included in the same group of network entities or in different groups of network entities.

[0071] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the second bit set may include operations, features, components, or instructions for sending the second bit set, which may be associated with at least the first network entity and the second network entity, based on a resource block set index assigned to a resource block set across at least the first network entity and the second network entity, wherein each bit in the second bit set corresponds to a different resource block set index.

[0072] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the second bit set indicates that a contiguous set of resource blocks associated with the first network entity can be scheduled by the DCI message, and the methods, apparatuses, and nontransitory computer-readable media may include further operations, features, components, or instructions for identifying resource blocks between the contiguous resource block sets that are associated with the same network entity for scheduling the uplink shared channel message.

[0073] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the second bit set indicates that a first set of resource blocks associated with the first network entity and a contiguous set of resource blocks associated with the second network entity are available for scheduling by the DCI message, and the methods, apparatuses, and nontransitory computer-readable media may include further operations, features, components, or instructions for identifying resource blocks between the first set of resource blocks and the contiguous set of resource blocks that may not be scheduled for the uplink shared channel message based on the association of the first set of resource blocks and the contiguous set of resource blocks with different network entities.

[0074] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bits included in the second bit set may be based on the number of resource block sets allocated across at least the first network entity and the second network entity.

[0075] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, sending the first set and the second set may include operations, features, components, or instructions for sending a message including the first set and the second set.

[0076] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the message may be the DCI message.

[0077] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the format of the DCI message may be based on the DCI message that schedules the uplink shared channel message to at least the first network entity and the second network entity according to the resource allocation type.

[0078] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the number of bits included in the first set is based on the subcarrier spacing associated with the one or more resource blocks. Attached Figure Description

[0079] Figure 1 Examples of wireless communication systems supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, are illustrated.

[0080] Figure 2 Examples of wireless communication systems supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, are illustrated.

[0081] Figures 3 to 7 An example of a resource allocation graph supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is illustrated.

[0082] Figure 8 An example flowchart illustrating a process for allocating uplink shared channel resources for multi-cell scheduling, according to one or more aspects of this disclosure, is provided.

[0083] Figure 9 and Figure 10 A block diagram of an apparatus for uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown.

[0084] Figure 11 A block diagram of a communication manager supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown.

[0085] Figure 12 A diagram is shown of a system including an apparatus for allocating uplink shared channel resources for multi-cell scheduling, according to one or more aspects of this disclosure.

[0086] Figure 13 and Figure 14 A block diagram of an apparatus for uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown.

[0087] Figure 15 A block diagram of a communication manager supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown.

[0088] Figure 16 A diagram of a system including an apparatus for allocating uplink shared channel resources for multi-cell scheduling, according to one or more aspects of this disclosure, is shown.

[0089] Figures 17 to 20 A flowchart illustrating a method for allocating uplink shared channel resources for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0090] In some wireless communication systems, one or more Frequency Domain Resource Allocation (FDRA) types (e.g., 0, 1, 2) can be used to indicate available (e.g., scheduled) resources to a receiving device (e.g., a User Equipment (UE)). For example, in type 0, the FDRA field in a scheduling downlink control information (DCI) message can be a bitmap indicating the scheduling of a group of resource blocks. According to type 1, the FDRA field in a scheduling DCI can be a Resource Indication Value (RIV) field indicating the number of consecutive resource blocks scheduled by the starting resource block and the DCI. Type 2 FDRA can allocate resources to achieve wideband transmission by utilizing interleaved resource blocks, which allows for fewer allocated resource blocks. According to type 2, the FDRA field may include a first set of bits (e.g., N bits) indicating the scheduled resource blocks, and may include a second set of bits (e.g., Y bits) indicating the set of scheduled resource blocks. In some examples, a single DCI can indicate scheduling information that can be applied by the UE to multiple network entities, cells, etc., such as uplink shared channel scheduling information. Techniques for indicating scheduling information (such as resource allocation type 2 information) across multiple network entities can be improved.

[0091] The techniques described herein can be implemented to support a single DCI configured to indicate resource allocation information across multiple network entities (e.g., cells). In the case of FDRA type 2, the DCI message may include one or more FDRA fields, which may include at least two sets of bits, wherein a first set (e.g., N bits) may indicate the scheduled resource blocks and may be referred to as the resource block bit, and a second set of bits (e.g., Y bits) may indicate the set of scheduled resource blocks and may be referred to as the resource block set bit. According to FDRA type 2, the resource block bit and the resource block set bit may be included in a single DCI indicating resource allocation information applicable across multiple network entities, wherein the FDRA fields of the DCI may indicate the resource allocation type (e.g., FRDA type 0, 1, 2). In some examples, the resource block bit, the resource block set bit, or both may be common across multiple network entities, such that a single set of resource block bits, a single set of resource block set bits, or both may be applicable across multiple network entities. In some other examples, the DCI message (e.g., the FDRA field of the DCI) may include multiple sets of resource block bits, each of which may be associated with a different network entity. Similarly, the DCI message may include multiple sets of resource block set bits, each of which may be associated with a different network entity. In some cases, the FDRA field may include multiple sets of resource block bits, each of which may be associated with one or more network entities in different groups. Similarly, the FDRA field may include multiple sets of resource block set bits, each of which may be associated with a different group of network entities. For example, network entities may be grouped based on similar resource grid alignments, resource block indexes, etc., and accordingly, different resource allocations may be assigned to different groups. Therefore, the UE may receive the FDRA field including one or more sets of resource block bits and one or more sets of resource block set bits, and may send uplink sharing messages to the multiple network entities based on the resource block bits and resource block set bits.

[0092] Specific aspects of the subject matter described herein can be implemented to achieve one or more advantages. The described techniques can support improvements in resource allocation by reducing signaling overhead, improving reliability, increasing UE signaling flexibility, and reducing latency. Therefore, supported techniques may include improved network operation, and in some examples, improved network efficiency, etc.

[0093] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to resource allocation diagrams and process flowcharts. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to uplink shared channel resource allocation in multi-cell scheduling.

[0094] Figure 1 Examples of wireless communication systems 100 supporting uplink shared channel resource allocation for multi-cell scheduling according to one or more aspects of this disclosure are illustrated. 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, 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 expressly mentioned herein.

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

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

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

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

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

[0100] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105 (such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

[0103] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support uplink shared channel resource allocation for multi-cell scheduling as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0105] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that 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 As shown.

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

[0107] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high-order modulation scheme can correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE 115.

[0108] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. The time interval of the communication resource can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

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

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

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

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

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

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

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

[0116] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, 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 approximately 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 are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0117] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency 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 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating using licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operations using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

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

[0120] In some implementations, network entity 105 may allocate resources, such as time resources, frequency resources, and spatial resources, to another device (e.g., UE 115, another network device). To allocate resources to a device, network entity 105 may send a DCI message including one or more FDRA fields indicating the frequency resources allocated to the receiving device. In some cases, the DCI fields may indicate the scheduled resource block and / or resource block set. A resource block may refer to time and frequency resources occupying 12 subcarriers (e.g., 12 x 15kHz = 180kHz) and a time slot of 0.5ms. A resource block set may refer to any number of resource blocks grouped into a set. Physical resource block indices may be assigned to each downlink bandwidth portion. Physical resource blocks and common resource blocks may be associated with specific subcarrier intervals.

[0121] In some cases, network entity 105 may allocate frequency resources based on different FDRA types, where different types are associated with different technologies used to indicate resource allocation to receiving devices. Examples of FDRA types may include type 0, type 1, and type 2. Fields in the DCI message (e.g., one bit) may indicate which FDRA type is used for resource scheduling. DCI may support dynamic switching between type 0 and type 1.

[0122] If network entity 105 indicates FDRA type 0, the FDRA field of the scheduled DCI may be or include a bitmap field indicating whether a Resource Block Group (RBG) is scheduled. The RBG size may depend on the bandwidth of the bandwidth segment. For example, an RBG at the edge of a bandwidth segment may have fewer resource blocks.

[0123] If network entity 105 indicates FDRA type 1, the FDRA field of the scheduling DCI can be a Resource Indication Value (RIV) field. Each code point in the RIV field can be associated with the starting resource block and the number of resource blocks consecutively scheduled from the starting resource block. In some examples, a similar mechanism can be used to allocate resources to groups of resource blocks (e.g., 2, 4, 5, 16 resource block granularity). In some cases, network entity 105 can support dynamic switching between type 0 and type 1. Bits in the DCI or some other message can indicate which resource allocation type is being used for scheduling.

[0124] FDRA Type 2 can use interleaved resource blocks to allocate resources, such as resources for uplink shared channel messages (e.g., Physical Uplink Shared Channel (PUSCH)). Interleaved resource blocks enable wideband transmission while reducing the number of resource blocks allocated. Type 2 can be applied to various wireless systems (e.g., NR-Unlicensed). Interleaving can be described by an interleaving index (e.g., m=0, m=1, etc.). The number of interleavings can be based on subcarrier spacing. For example, network entity 105 can allocate five interleavings for a 30 kHz subcarrier spacing and ten interleavings for a 15 kHz subcarrier spacing. The Physical Uplink Shared Channel (PUSCH) can be mapped to one or more resource blocks in one or more resource block sets. The grid of resource block sets can be specified based on Control Resource Blocks (CRBs).

[0125] According to Type 2, the FDRA field may include a first set of bits (e.g., N bits) indicating the scheduled resource blocks (e.g., resource block bits), and may include a second set of bits (e.g., Y bits) indicating the set of scheduled resource blocks (e.g., resource block set bits). In some examples, different numbers of bits may indicate different resource block options and may be based on subcarrier spacing. For example, the resource block bits may include five bits for a subcarrier spacing of 30 kHz and may indicate a bitmap of resource blocks in each resource block set. In another example, the resource block bits may include six bits and may indicate the length of the starting resource block and the resource blocks in each resource block set.

[0126] In some cases, the resource block set bit may be based on the DCI format. The resource block set bit may be fixed to zero, such as in the example of DCI format 0_0 in the Common Search Space (CSS) and / or in the scheduling of a resource block set. The resource block set bit may be included in multiple DCI formats (e.g., 0_0, 0_1). In some examples, such as in the UE-specified Search Space (USS), the resource block set bit may be based on the number of resource block sets per downlink bandwidth segment and may indicate the starting resource block set and the length of the resource block sets within the downlink bandwidth segment. The grid and interleaving indexes of the resource block sets may be defined in the Control Resource Block (CRB) number and, in some examples, may be independent of where the downlink bandwidth segment begins.

[0127] Techniques for indicating resource allocation in DCI messages can be improved. For example, in some cases, a single DCI can be used to schedule multiple cells, network entities 105, network nodes, etc. Therefore, the techniques described herein support DCI messages that can allocate resources for PUSCH messages sent across multiple cells, network entities, etc., according to FDRA type 2.

[0128] According to the techniques described herein, the FDRA field may include at least two sets of bits, wherein a first set (e.g., N bits) indicates the scheduled resource block and may be referred to as the resource block bit, and a second set of bits (e.g., Y bits) indicates the set of scheduled resource blocks and may be referred to as the resource block set bit. These resource block bits and resource block set bits may be included in a single DCI and may be applicable across multiple network entities 105, wherein the FDRA field of the DCI may indicate the resource allocation type (e.g., type 2). In some examples, the resource block bits, resource block set bits, or both may be common across multiple network entities. In some other examples, the FDRA field may include multiple sets of resource block bits, each of which may be associated with a different network entity 105. Similarly, the FDRA field may include multiple sets of resource block set bits, each of which may be associated with a different network entity 105. In some cases, the FDRA field may include multiple sets of resource block bits, each of which may be associated with a different group of network entities 105. Similarly, the FDRA field may include multiple sets of resource block set bits, each set being associated with a different group of network entities 105. Likewise, the UE 115 may receive the FDRA field including one or more sets of resource block bits and one or more sets of resource block set bits, and the UE 115 may send uplink sharing messages to the multiple network entities 105 based on the resource block bits and resource block set bits.

[0129] Figure 2 An example of a wireless communication system 200 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is illustrated. The wireless communication system 200 describes communication between UE 115-a and network entity 105-a, and between UE 115-a and network entity 105-b. UE 115-a may be as described in reference... Figure 1 The example of UE 115 described herein, and network entity 105-a and network entity 105-b may be as referenced. Figure 1 Examples of network entity 105 described herein. In some examples, network entity 105-a and network entity 105-b may include one or more cells, and the cells may be served by network entity 105. In some cases, the terms network entity 105 and cell are used interchangeably as described herein. UE 115-a may communicate with network entity 105-a via downlink 205 (e.g., communication link, channel, beam) and uplink 220-a (e.g., communication link, channel, beam), and communicate with network entity 105-b at least via uplink 220-b.

[0130] In some cases, network entity 105 can send a single DCI to schedule multiple cells, network entities 105, network nodes, etc. (See reference...) Figure 1 As described herein, the technology supports DCI messages that can allocate resources for PUSCH messages sent across multiple cells, network entities 105, etc., according to FDRA type (e.g., FDRA type 2). For example, network entity 105-a may send resource allocation 215 to UE 115-a, and resource allocation 215 may include resource block indication 225 and resource block set indication 230. According to resource allocation 215, UE 115-a may send uplink shared channel 210-a to network entity 105-a via uplink 220-a, and may send uplink shared channel 210-b to network entity 105-b via uplink 220-b.

[0131] In some cases, network entity 105-a may include resource allocation 215 in a single message or across multiple messages (such as DCI messages). Resource allocation 215 may include resource block indication 225, resource block set indication 230, indication of FDRA format, or a combination thereof. For example, as part of a DCI message, resource allocation 215 may indicate the type of FDRA applied to the scheduling, such as FDRA type 2. Resource block indication 225 may be referred to as resource block bits (e.g., N bits, first set), and resource block set indication 230 may be referred to as resource block set bits (e.g., Y bits, second set). In some cases, receiving devices such as UE 115-a may identify the type of FDRA applied based on messages from network entity 105 (e.g., RRC messages, MAC-CE messages, DCI messages, resource allocation 215). In some cases, receiving devices may implicitly identify the type of FDRA applied based on the format of resource allocation 215.

[0132] In some cases, according to FDRA Type 2, existing DCI formats can be used to support a single DCI indicating resource allocation for uplink shared channel messages across cells, network entities 105, etc. In some cases, according to FDRA Type 2, a DCI format (e.g., a new DCI format, DCI format 0_X) can be configured (e.g., pre-configured, configured by network entity 105-a) to support a single DCI indicating resource allocation for uplink shared channel messages across cells, network entities 105, etc. For example, DCI format 0_X can indicate an FDRA format, resource block indication 225, resource block set indication 230, or a combination thereof.

[0133] For a set of Physical Uplink Shared Channels (PUSCHs), such as one or more PUSCHs that can be sent to one or more network entities 105, the resource block indication 225 can be common, individual, or a combination thereof. In some examples, the resource block indication 225 can be common or shared for a set of PUSCHs that can be scheduled by DCI format 0_X. For example, UE115-a can receive resource allocation 215 for one or more PUSCHs that can be scheduled with a common resource block indication 225 (e.g., uplink shared channel 210-a to network entity 105-a, uplink shared channel 210-b to network entity 105-b). The common resource block indication 225 may include a single set of bits, wherein the set of bits can be applied collectively to uplink shared channel 210-a to network entity 105-a and uplink shared channel 210-b to network entity 105-b. Then, UE 115-a can use the same resource block indication 225 to send uplink shared channel 210-a and uplink shared channel 210-b to network entity 105-a and network entity 105-b, respectively. The number of bits included in the resource block indication 225 can be based on the subcarrier spacing. For example, the resource block indication 225 may include five bits for a 30 kHz subcarrier spacing and six bits for a 15 kHz subcarrier spacing.

[0134] In some other examples, the resource block indication 225 can be separate for each PUSCH in a set of PUSCHs for one or more cells that can be scheduled by DCI messages. UE 115-a can be configured with type 2 resource allocation and can monitor DCI format 0_X or some other DCI format for PUSCH scheduling. In some examples, resource allocation 215 can indicate that DCI format 0_X includes a resource block indication 225 for interleaving resource block indication. Depending on the separate indication, the resource block indication 225 field can include a set of bits that can be divided into bit subsets, where each subset is associated with a specific PUSCH (e.g., cell, network entity 105). If the resource block indication 225 field is divided into bit subsets for each PUSCH, each subset can be the same or different (e.g., the same or different number of bits, the same or different bit values ​​for each subset). In some cases, resource block indication 225 may include multiple bit sets, or resource allocation 215 may include multiple resource block indications 225, such that each resource block indication 225 or each bit set can be assigned to a specific PUSCH (e.g., cell, network entity 105). If each PUSCH applies a bit set or resource block indication 225, each resource block indication 225 for each cell may be the same or different. Therefore, a DCI message (e.g., DCI format 0_X) may include interleaved resource block indications for X cells scheduled by DCI. For example, in the case of a 30kHz subcarrier spacing, N can be equal to five, and in the case of two network entities 105 scheduled by DCI, resource allocation 215 may include ten bits for resource block indication (e.g., five bits for the first network entity 105 and the remaining five bits for the second network entity 105).

[0135] In some other examples, for a group of PUSCHs scheduled by a DCI message, the resource block indication 225 can be a combination of common and independent elements. For example, network entities 105, cells, PUSCHs, etc., can be grouped based on similar resource grid alignments, resource block indices, etc., and therefore, different groups can be allocated different resources. For example, a DCI message may include multiple resource block indications 225, or a resource block indication 225 may include multiple bit sets (e.g., multiple N bits). Each resource block indication 225 or each bit set can be used for a subgroup of one or more PUSCHs that can be scheduled by a DCI message. Thus, common resource block bits can be used to schedule network entities 105, cells, PUSCHs, etc., included in a group, but different resource block bits can be used to schedule different groups.

[0136] The resource block set indicator 230 and its corresponding index can be defined per cell or across multiple cells. For example, a resource block set index can be assigned to the resource block set for each cell. In some examples, the resource block set indicator 230 can be defined or identified for each cell. In this case, the resource block set indicator 230 can be common to a group of one or more PUSCHs that can be scheduled by a DCI message. For example, a DCI message can indicate that one or more resource block sets are scheduled, and because the resource block set indicator 230 is common, one or more scheduled resource block sets can be applied to each PUSCH indicated by the DCI message. If a DCI message indicates that a first resource block set is scheduled, then the first resource block set in all cells scheduled by the DCI is also scheduled. The number of bits included in the resource block set indicator 230 is determined based on the cell or downlink bandwidth portion that has the largest number of resource block sets across multiple cells.

[0137] In some examples, the DCI message may include a separate resource block set indication 230 for each PUSCH from a set of PUSCHs that can be scheduled by the DCI. The resource block set indication 230 field may be partitioned into a subset of bits for each PUSCH, or a full resource block set indication 230 may be assigned for each PUSCH. If the resource block set indication 230 field is partitioned into a subset of bits for each PUSCH, each subset may be the same or different. If a resource block set indication 230 is applied to each PUSCH, each resource block set indication 230 for each cell may be the same or different.

[0138] In some other examples, the resource block set indication 230 can be a common and independent combination for a group of PUSCHs scheduled by DCI. For example, network entities 105, cells, PUSCHs, etc., can be grouped based on similar resource grid alignments, resource block indices, etc., and therefore, different groups can be allocated different resources. For example, a DCI message may include multiple resource block set indications 230, or a resource block set indication 230 may include multiple bit sets (e.g., multiple Y bits). Each resource block set indication 230 or each bit set can be used for a subgroup of one or more PUSCHs that can be scheduled by DCI messages based on grouping. Thus, common resource block set bits can be used to schedule network entities 105, cells, PUSCHs, etc., included in a group, but different resource block set bits can be used to schedule different groups.

[0139] In some implementations, resource block set indication 230 and corresponding indexes can be defined or identified on multiple cells. Resource block set indication 230 can be common to a set of PUSCHs scheduled by DCI messages. In some examples, the number of bits included in resource block set indication 230 can be based on the number of resource blocks across multiple network entities (e.g., cells). If resource allocation 215 schedules multiple consecutive resource blocks for the same network entity 105 (such as network entity 105-a), interleaved resource blocks in the intra-cell protection band can also be scheduled, as referenced. Figure 6 In a more detailed description, if resource allocation 215 schedules multiple contiguous resource blocks across multiple cells (such as network entity 105-a and network entity 105-b), then resource blocks between two cells may not be scheduled, as shown in the reference. Figure 7 A more detailed description.

[0140] The techniques described herein for allocating resource blocks and resource block sets for PUSCH across multiple cells, network entities, etc., can be used in any combination. For example, resource allocation 215 may include common resource block bits applicable to multiple network entities 105, and may include separate resource block set bits for each network entity 105. In another example, resource allocation 215 may include common resource block bits applicable to multiple network entities 105 and common resource block set bits applicable to multiple network entities 105.

[0141] Figure 3 An example of a resource allocation diagram 300 supporting uplink shared channel resource allocation for multi-cell scheduling according to one or more aspects of this disclosure is illustrated. The resource allocation diagram 300 may be provided by network entity 105, UE 115, or reference... Figure 1 and Figure 2Other devices described herein may be used to implement this. According to resource allocation diagram 300, one or more common sets of resource block bits can be scheduled for multiple cells, network entities, PUSCHs, etc., such as network entity 105-c and network entity 105-d. Network entity 105-c and network entity 105-d can be as described in the reference... Figure 1 and Figure 2 An example of the described network entity 105.

[0142] Network entity 105-c may have one or more sets of resource blocks, such as resource block set 315-a, and network entity 105-d may have one or more sets of resource blocks, such as resource block set 315-d. Resource block set 315-a may include one or more interleaved resource blocks, such as interleaved resource block 320-a, which may include resource blocks, such as resource block 325-a. Similarly, resource block set 315-b may include one or more interleaved resource blocks, such as interleaved resource block 320-b, which may include one or more resource blocks, such as resource block 325-b.

[0143] The UE can be configured with FDRA type 2 for scheduling one or more PUSCHs associated with multiple cells. The UE can monitor DCI messages (e.g., DCI format 0_X) used for PUSCH scheduling. DCI messages may include common resource block bits for interleaved resource blocks 320-a and 320-b for different network entities (e.g., network entity 105-c and network entity 105-d). Therefore, resource block bits can be common to a set of PUSCHs scheduled by DCI messages for network entities 105-c and 105-d. Common resource block bits can indicate that PUSCHs are scheduled on the interleaved network using interleaving indices (e.g., m=0, m=1, etc.). For example, common resource set bits can indicate resource block indices 0 and 1 for scheduling network entities 105-c and 105-d.

[0144] Figure 4 An example of a resource allocation diagram 400 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is illustrated. Resource allocation diagram 400 may be provided by network entity 105, UE 115, or reference... Figures 1 to 3 Other devices described herein may be used to implement this. According to resource allocation diagram 400, one or more common sets of resource block bits may be scheduled for network entity 105-e and network entity 105-f. Network entity 105-e and network entity 105-f may be as described in reference... Figures 1 to 3 An example of the described network entity 105.

[0145] Network entity 105-e may have one or more sets of resource blocks, such as resource block set 415-a, and network entity 105-f may have one or more sets of resource blocks, such as resource block set 415-d. Resource block set 415-a may include one or more interleaved resource blocks, such as interleaved resource block 420-a, which may include one or more resource blocks, such as resource block 425-a. Resource block set 415-b may include one or more interleaved resource blocks, such as interleaved resource block 420-b, which may include one or more resource blocks, such as resource block 425-b. Network entity 105-e may have point 430-a, and network entity 105-f may have point 430-b.

[0146] An interleaving index (e.g., m) can be defined for each resource block of network entity 105 (e.g., resource block 425-a, resource block 425-b). The interleaving index can be determined by point 430-a for network entity 105-e and point 430-b for network entity 105-f. The interleaving index m can be different for the same resource block index of a cell where PUSCH can be scheduled by a DCI message (e.g., DCI format 0_X). Therefore, the alignment based on reference points (e.g., points 430-a and 430-b) is different for network entities 105-e and 105-f, and the interleaving patterns of one or more resource block indices are different for network entities 105-e and 105-f. Misalignment of points 430-a and 430-b can be based on spectral grid misalignment between network entities 105-e and 105-f.

[0147] Therefore, using a common set of resource block bits does not necessarily mean scheduling the same interleaving resource block pattern for multiple cells. Common resource block bits can be allocated for different interleaving resource block patterns scheduled for multiple cells. For example, point 430-a of network entity 105-e may be aligned with the lower edge of the carrier (e.g., the downlink bandwidth portion), while point 430-b of network entity 105-f may be two resource blocks lower than the lower edge of the carrier (e.g., the downlink bandwidth portion). Interleaving indices (e.g., m=0, m=1) can be scheduled on the lower set of resource blocks for both network entities (e.g., network entity 105-e and network entity 105-f). Therefore, both network entities 105-e and 105-f can share resource block indices for 0 and 1, but the physical locations of resource block indices 0 and 1 between network entities 105 can be different.

[0148] Figure 5 An example of a resource allocation diagram 500 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is illustrated. The resource allocation diagram 500 may be provided by network entity 105, UE 115, or reference... Figures 1 to 4 Other devices described herein shall be used to implement this. Resource allocation diagram 500 depicts the resource block sets and corresponding indices of network entities 105-g and 105-h. Network entities 105-g and 105-h may be as described in the reference. Figures 1 to 4 Examples of network entities 105 described. Network entities 105-g and 105-h may have one or more resource block sets 515. Each network entity 105 or cell may have one or more resource block sets 515.

[0149] In some cases, a set of resource blocks may be separated by one or more resource blocks. One or more resource blocks between sets of resource blocks may be referred to as a guard band. For example, network entity 105-g may have an intra-cell guard band 520-a between at least resource block set 1 and resource block set 2, and network entity 105-h may have an intra-cell guard band 520-b between at least resource block set 2 and resource block set 3.

[0150] Resource block sets and corresponding indexes can be defined or identified for each network entity 105 (e.g., network entity 105-g and network entity 105-h), each cell, etc., such that the resource block sets for network entities 105-g and 105-h can both include m=0, 1, 2, and 3 (e.g., the indexes are the same across network entities 105). The UE can be configured with FDRA type 2 for one or more PUSCHs associated with multiple network entities 105, wherein the UE can monitor DCI messages (e.g., DCI format 0_X) used for PUSCH scheduling. The resource block sets for network entities 105-g and 105-h can be indicated by a common bit set, a single bit set, or a combination thereof in the DCI.

[0151] In some cases, network entities 105-g and 105-h may have different resource block set patterns, such as based on higher-level configurations. For example, the initial control resource block index and the number of control resource blocks for each resource block set may be based on radio resource control (RRC) parameters for intra-cell protection band configurations such as intra-cell protection band 520-a and intra-cell protection band 520-b. Intra-cell protection band 520-a and intra-cell protection band 520-b may be resources scheduled between resource block sets, resulting in different resource block set patterns between network entities 105-h and 105-g. Different physical resource block sets may be scheduled for different network entities 105, such as when resource block sets are scheduled for different network entities 105. For example, resource block set 2 of network entity 105-g and resource block set 2 of network entity 150-h may have different or the same physical resource blocks. Therefore, scheduling resource block sets with the same index (e.g., resource block set 2) on multiple cells does not necessarily mean scheduling the same PRB set in different cells.

[0152] Figure 6 An example of a resource allocation diagram 600 supporting uplink shared channel resource allocation for multi-cell scheduling according to one or more aspects of this disclosure is illustrated. Resource allocation diagram 600 describes resource scheduling between sets of resource blocks for network entities 105-i and 105-j. Network entities 105-i and 105-j can be as shown in reference... Figures 1 to 5 Examples of network entities 105 described. Network entities 105-i and 105-j may have one or more resource block sets 615. Each network entity 105 or cell may have one or more resource block sets 615. Network entity 150-i may have a scheduled intra-cell protection band 620 between at least resource block set 0 and resource block set 1.

[0153] In some cases, resource block set bits, resource block sets, and corresponding indexes can be defined or identified across multiple network entities. Therefore, the indexes of resource block sets can be applied sequentially across network entities 105. For example, the indexes of resource block sets can begin with the first resource block set of network entity 105-i and continue through network entity 105-j, resulting in network entity 105-i being associated with resource block sets 0 through 3 and network entity 105-j being associated with resource block sets 4 through 7. In this case, common resource set bits for a set of PUSCHs can be scheduled by DCI messages (e.g., DCI format 0_X). The number of resource block set bits can be based on the number of resource block sets 615 across multiple network entities 105. For example, resource block set bits can include eight bits, one bit for each resource block set 0 through 7.

[0154] For reference Figure 5As described, a set of resource blocks may be separated by one or more resource blocks. One or more resource blocks between sets of resource blocks may be referred to as a guard band. A guard band may include any number of resource blocks and may not be uniform within or across network entity 105. For example, a guard band between resource block set 0 and resource block set 1 may include a first number of resource blocks, a guard band between resource block set 2 and resource block set 3 may include a second number of resource blocks, a guard band between resource block set 3 and resource block set 4 may include a third number of resource blocks, and a guard band between resource block set 6 and resource block set 7 may include a fourth number of resource blocks, wherein the first, second, third, and fourth numbers may be the same or different.

[0155] A protection band between resource block sets 615 of the same network entity 105 may be referred to as an intra-cell protection band. In some cases, an intra-cell protection band between two scheduled resource block sets 615 may also be scheduled. For example, if multiple consecutive resource block sets 615 associated with network entity 105-i (such as resource block set 0 and resource block set 1) are scheduled, an intra-cell protection band between resource block sets 615 may also be scheduled, resulting in a scheduled intra-cell protection band 620. The scheduled intra-cell protection band 620-a may include interleaved resource blocks. In some cases, the DCI message may include an explicit indication that an intra-cell protection band has been scheduled. In some cases, the UE may implicitly determine that an intra-cell protection band has been scheduled based on resource block sets 0 and 1 being scheduled and based on resource block sets 0 and 1 being associated with the same network entity 105.

[0156] Figure 7 An example of a resource allocation diagram 700 supporting uplink shared channel resource allocation for multi-cell scheduling according to one or more aspects of this disclosure is illustrated. Resource allocation diagram 700 depicts resource scheduling across resource block sets of network entities 105-k and 105-l. Network entities 105-j and 105-l can be as described in reference... Figure 1 and Figure 6 Examples of network entities 105 are described. Network entities 105-k and 105-l may have one or more resource block sets 715. Each network entity 105 may have one or more resource block sets 715.

[0157] In some cases, and as referenced Figure 6As described, resource block set bits, resource block sets, and corresponding indexes can be defined or identified across multiple network entities. Therefore, the indexes of resource block sets can be applied consecutively across network entities 105. For example, the indexes of resource block sets can begin with the first resource block set of network entity 105-i and continue through network entity 105-j, resulting in network entity 105-i being associated with resource block sets 0 through 3 and network entity 105-j being associated with resource block sets 4 through 7. In this case, common resource set bits can be used to schedule a set of PUSCHs by DCI messages (e.g., DCI format 0_X). The number of resource block set bits can be based on the number of resource blocks across multiple cells.

[0158] For reference Figure 5 and Figure 6 As described, a resource block set may be separated by one or more resource blocks. One or more resource blocks between resource block sets 715 may be referred to as a guard band. A guard band may include any number of resource blocks and may not be uniform within or across network entity 105. In some implementations, resources between multiple consecutive resource block sets 715 across two different cells may not be scheduled. For example, inter-cell resources or resource block sets 3 and 4 between network entity 105-k and network entity 105-l may not be scheduled (e.g., unscheduled inter-cell resource 720). In some cases, the DCI message may include an explicit indication that inter-cell resources are not scheduled. In some cases, the UE may implicitly determine that inter-cell resources are not scheduled based on the scheduled resource block sets 3 and 4 and based on the association of resource block sets 3 and 4 with different network entities 105.

[0159] Figure 8 An example of a process flowchart 800 supporting uplink shared channel resource allocation for multi-cell scheduling according to one or more aspects of this disclosure is illustrated. Process flowchart 800 describes the scheduling of resource blocks and sets of resource blocks for uplink messages to be sent by UE 115-b to network entity 105-m and network entity 105-n. Network entity 105-m and network entity 105-n can be as described in reference... Figures 1 to 8 Examples of network entity 105 described. In some cases, network entity 105-m and network entity 105-n may represent a cell. In some cases, network entity 105-m and network entity 105-n may be associated with different cells. UE 115-b may be as shown in the reference. Figures 1 to 8 An example of UE 115 as described.

[0160] At point 805, network entity 105-m can send a resource allocation indication, and UE 115-b can receive the resource allocation indication. The resource allocation indication may include a DCI or some other control message, which indicates that uplink shared channel messages can be scheduled to at least a first network entity (e.g., network entity 150-m) and a second network entity (e.g., network entity 105-n) according to the resource allocation type (e.g., FDRA type 2). The format of the DCI message may be based on a DCI message that schedules uplink shared channel messages to at least the first and second network entities according to the resource allocation type.

[0161] At 810, network entity 105-m can send a resource block index, and UE 115-b can receive the resource block index. The resource block index may include resource block bits or a first-bit set. The first-bit set may indicate one or more resource block indices based on the resource allocation type. The first-bit set may be associated with at least a first network entity (e.g., network entity 105-m) and a second network entity (e.g., network entity 105-n), wherein one or more resource block indices may be allocated for sending uplink shared channel messages to at least the first and second network entities.

[0162] The first set or resource block bit may include a subset of bits, wherein each subset of bits may be associated with a different network entity 105, and each subset of bits may indicate a set of resource block indexes associated with the corresponding network entity 105. Based on the fact that the first network entity 105 and the second network entity 105 are different network entities 105, the subset of bits may include a first subset associated with the first network entity (e.g., network entity 105-m) and a second subset of bits associated with the second network entity (e.g., network entity 105-n).

[0163] The first subset may indicate a first set of resource block indices allocated for sending uplink shared channel messages to the first network entity 105, and the second subset may indicate a second set of resource block indices allocated for sending uplink shared channel messages to the second network entity 105. The number of bit subsets in the first set may be based on the number of network entities 105 configured to be scheduled by DCI messages. The number of bits included in the first set may be based on the subcarrier spacing associated with one or more resource blocks.

[0164] The resource block index may indicate a first set including a subset of bits, wherein each subset of bits may be associated with one or more network entities 105 in different groups, and each subset of bits may indicate a set of resource block indexes associated with the network entity 105 in the corresponding group. The number of subsets of bits included in the first set may be based on the number of groups of network entities 105 configured to be scheduled by DCI messages. A first network entity (e.g., network entity 105-m) and a second network entity (e.g., network entity 105-n) may be included in the same group of network entities 105 or in different groups of network entities 105.

[0165] The alignment based on the reference point is different for the first network entity and the second network entity 105. According to the first set of reference points commonly associated with at least the first network entity and the second network entity, the interleaving pattern of one or more resource block indexes is different for the first network entity (e.g., network entity 105-m) and the second network entity (e.g., network entity 105-n), where the reference point is used to identify the resource block index.

[0166] At 815, network entity 105-m may send a resource block set index, and UE 115-b may receive the resource block set index. The resource block set index may include a resource block set bit or a second bit set. The second bit set may indicate one or more resource block set indices based on the resource allocation type. The second bit set may be a plurality of first bit sets, each plurality associated with a different network entity 105, and each plurality indicating a resource block index set associated with a corresponding network entity 105. The number of plurality of first bit sets may be based on the number of network entities 105 configured to be scheduled by DCI messages.

[0167] The second bit set or resource block set may be associated with at least the first network entity 105 and the second network entity 105 based on the resource block set assigned to each network entity 105 by a resource block index, wherein one or more resource block set indices may be allocated for sending uplink shared channel messages to at least the first network entity 105 and the second network entity 105. The number of bits included in the second bit set may be associated with the highest number of resource block sets among at least the first network entity 105 and the second network entity 105.

[0168] Based on the intra-cell protection band configuration associated with the corresponding first and second network entities, the resource block set configuration associated with the first network entity 105 may differ from the resource block set configuration associated with the second network entity 105. Each resource block set configuration may indicate a starting common resource block index and the number of common resource blocks associated with each resource block set. The starting common resource block index, the number of common resource blocks, or both may be different for one or more resource block sets configured for the first network entity 105 and the second network entity 105.

[0169] The second bit set may include bit subsets, each of which may be associated with a different network entity 105, and each bit subset indicates a set of resource block set indexes associated with the corresponding network entity 105. At least in part based on the fact that the first network entity 105 and the second network entity 105 are different network entities 105, the bit subset may include a first bit subset associated with the first network entity 105 and a second bit subset associated with the second network entity 105. The first bit subset indicates a first set of resource block set indexes allocated for sending uplink shared channel messages to the first network entity 105, and the second bit subset indicates a second set of resource block set indexes allocated for sending uplink shared channel messages to the second network entity 105. The number of bit subsets included in the first bit set may be based on the number of network entities 105 configured to be scheduled by DCI messages.

[0170] UE 115-b can receive multiple second bit sets, each of which can be associated with a different network entity 105, and each of which indicates a set of resource block set indices associated with the corresponding network entity 105. The number of the multiple second bit sets can be based on the number of network entities 105 configured to be scheduled by DCI messages.

[0171] The second bit set may include subsets of bits, each subset of bits may be associated with one or more network entities 105 in different groups, and each subset of bits indicates a set of resource block indexes associated with the network entity 105 in the corresponding group. The number of bit subsets included in the second bit set may be based on the number of groups of network entities 105 configured to be scheduled by DCI messages. A first network entity 105 (e.g., network entity 105-m) and a second network entity 105 (e.g., network entity 105-n) may be included in the same group of network entities 105 or in different groups of network entities 105. The second bit set may be associated with at least the first network entity 105 and the second network entity 105 based on resource block set indexes assigned to resource block sets across at least the first network entity 105 and the second network entity 105, wherein each bit in the second bit set corresponds to a different resource block set index.

[0172] The second bit set can indicate that a contiguous set of resource blocks associated with the first network entity 105 is scheduled by DCI messages, and can identify resource blocks between contiguous resource block sets that are scheduled for uplink shared channel messages based on the association of the contiguous resource block sets with the same network entity 105. The second bit set can also indicate that a first set of resource blocks associated with the first network entity 105 and a contiguous set of resource blocks associated with the second network entity 105 are scheduled by DCI messages, and can identify resource blocks between the first set of resource blocks and the contiguous set that are not scheduled for uplink shared channel messages based on the association of the first set of resource blocks and the contiguous set of resource blocks with different network entities 105. The number of bits in the second bit set can be based on the number of resource block sets allocated across at least the first network entity 105 and the second network entity 105.

[0173] In some examples, a DCI message may include a first set and a second set.

[0174] At 820, UE 115-b may send one or more uplink shared channels to network entity 105-m. At 825, UE 115-b may send one or more uplink shared channels to network entity 105-n. Uplink shared channels may be sent to at least a first network entity (e.g., network entity 105-m) and a second network entity (e.g., network entity 105-n) via uplink shared channel messages based on a first set and a second set.

[0175] Figure 9 A block diagram 900 of an apparatus 905 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Apparatus 905 may be an example of various aspects of UE 115 as described herein. Apparatus 905 may include a receiver 910, a transmitter 915, and a communications manager 920. Apparatus 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0176] Receiver 910 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to uplink shared channel resource allocation in multi-cell scheduling). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0177] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to uplink shared channel resource allocation in multi-cell scheduling). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0178] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0179] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, digital signal processors (DSPs), central processing units (CPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, microcontrollers, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof, configured to or otherwise support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

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

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

[0182] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured or otherwise supported to include components for receiving DCI messages indicating uplink shared channel messages scheduled to at least a first network entity and a second network entity based on a resource allocation type. The communication manager 920 may be configured or otherwise supported to include components for receiving a first set of indices indicating one or more resource block indices based on a resource allocation type. The communication manager 920 may be configured or otherwise supported to include components for receiving a second set of indices indicating one or more resource block set indices based on a resource allocation type. The communication manager 920 may be configured or otherwise supported to include components for transmitting uplink shared channel messages to at least a first network entity and a second network entity based on the first and second sets of indices.

[0183] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., a processor that controls or otherwise couples to receiver 910, transmitter 915, communication manager 920, or a combination thereof) can support techniques for uplink shared channel resource allocation for multi-cell scheduling, which can result in reduced processing, lower power consumption, or more efficient use of communication resources.

[0184] Figure 10 A block diagram 1000 of an apparatus 1005 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Apparatus 1005 may be an example of aspects of apparatus 905 or UE 115 as described herein. Apparatus 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Apparatus 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0185] Receiver 1010 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, and information channels related to uplink shared channel resource allocation in multi-cell scheduling). The information may be passed to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of antennas.

[0186] Transmitter 1015 may provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to uplink shared channel resource allocation in multi-cell scheduling). In some examples, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0187] Device 1005 or its various components may be examples of parts used to perform various aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein. For example, communication manager 1020 may include DCI message component 1025, resource block indication component 1030, resource block set indication component 1035, uplink shared channel message component 1040, or any combination thereof. Communication manager 1020 may be examples of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0188] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. The DCI message component 1025 may be configured or otherwise supported for receiving a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity based on a resource allocation type. The resource block indication component 1030 may be configured or otherwise supported for receiving a first set of indices indicating one or more resource block indices based on a resource allocation type. The resource block set indication component 1035 may be configured or otherwise supported for receiving a second set of indices indicating one or more resource block set indices based on a resource allocation type. The uplink shared channel message component 1040 may be configured or otherwise supported for sending an uplink shared channel message to at least a first network entity and a second network entity based on the first and second sets.

[0189] Figure 11 A block diagram 1100 is shown of a communication manager 1120 supporting uplink shared channel resource allocation for multi-cell scheduling according to one or more aspects of this disclosure. Communication manager 1120 may be an example of aspects of communication manager 920, communication manager 1020, or both as described herein. Communication manager 1120 or its various components may be examples of parts for performing aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein. For example, communication manager 1120 may include DCI message component 1125, resource block indication component 1130, resource block set indication component 1135, uplink shared channel message component 1140, resource block indication and resource block set indication component 1145, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0190] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. The DCI message component 1125 may be configured or otherwise supported for receiving a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity based on a resource allocation type. The resource block indication component 1130 may be configured or otherwise supported for receiving a first set of indices indicating one or more resource block indices based on a resource allocation type. The resource block set indication component 1135 may be configured or otherwise supported for receiving a second set of indices indicating one or more resource block set indices based on a resource allocation type. The uplink shared channel message component 1140 may be configured or otherwise supported for sending an uplink shared channel message to at least a first network entity and a second network entity based on the first and second sets.

[0191] In some examples, to support the reception of the first set, the resource block indication component 1130 may be configured or otherwise supported for receiving the first set associated with at least the first network entity and the second network entity, wherein one or more resource block indices are assigned to send uplink shared channel messages to at least the first network entity and the second network entity.

[0192] In some examples, the alignment based on the reference point is different for the first network entity and the second network entity, and the interleaving pattern of one or more resource block indexes is different for the first network entity and the second network entity according to the first set commonly associated with at least the first network entity and the second network entity, with the reference point used to identify the resource block index.

[0193] In some examples, to support receiving the first set, the resource block indicator component 1130 may be configured or otherwise supported for receiving a first set including a subset of bits, wherein each subset of bits may be associated with a different network entity, and wherein each subset of bits indicates a set of resource block indexes associated with the corresponding network entity.

[0194] In some examples, based on the fact that the first network entity and the second network entity are different network entities, the position subset includes the first position subset associated with the first network entity and the second position subset associated with the second network entity.

[0195] In some examples, the first subset indicates a first set of resource block indices allocated for sending uplink shared channel messages to a first network entity, and the second subset indicates a second set of resource block indices allocated for sending uplink shared channel messages to a second network entity.

[0196] In some examples, the number of bit subsets included in the first set is based on the number of network entities configured to be scheduled by DCI messages.

[0197] In some examples, to support receiving a second set of bits, the resource block set indicating component 1135 may be configured or otherwise supported for receiving a plurality of first set of bits, each plurality of which is associated with a different network entity, and each plurality of which indicates a set of resource block indexes associated with the corresponding network entity.

[0198] In some examples, the number of multiple first-order sets is based on the number of network entities configured to be scheduled by DCI messages.

[0199] In some examples, to support receiving the first set, the resource block indicator component 1130 may be configured or otherwise supported for receiving a first set including a subset of bits, wherein each subset of bits is associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with the network entities in the corresponding group.

[0200] In some examples, the number of bit subsets included in the first set is based on the number of groups of network entities configured to be scheduled by DCI messages.

[0201] In some examples, the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0202] In some examples, to support the reception of a second bit set, the resource block set indication component 1135 may be configured or otherwise supported for receiving a second bit set commonly associated with at least a first network entity and a second network entity based on the resource block set assigned to each network entity by a resource block index, wherein one or more resource block set indices are assigned to send uplink shared channel messages to at least the first network entity and the second network entity.

[0203] In some examples, the number of bits included in the second set is based on the network entities in at least the first and second network entities being associated with the highest number of resource block sets.

[0204] In some examples, the resource block set configuration associated with the first network entity differs from the resource block set configuration associated with the second network entity, based on the intra-cell protection band configuration associated with the corresponding first and second network entities.

[0205] In some examples, each resource block set configuration indicates a starting common resource block index and the number of common resource blocks associated with each resource block set, which are different for one or more resource block sets configured for the first network entity and the second network entity.

[0206] In some examples, to support receiving a second set of bits, the resource block set indicating component 1135 may be configured or otherwise supported for receiving a second set of bits including a subset of bits, wherein each subset of bits is associated with a different network entity, and wherein each subset of bits indicates a set of resource block set indexes associated with the corresponding network entity.

[0207] In some examples, based on the fact that the first network entity and the second network entity are different network entities, the position subset includes the first position subset associated with the first network entity and the second position subset associated with the second network entity.

[0208] In some examples, the first subset indicates the first set of resource block indexes allocated for sending uplink shared channel messages to the first network entity, and the second subset indicates the second set of resource block indexes allocated for sending uplink shared channel messages to the second network entity.

[0209] In some examples, the number of bit subsets included in the first set is based on the number of network entities configured to be scheduled by DCI messages.

[0210] In some examples, to support receiving a second set of bits, the resource block set indicating component 1135 may be configured or otherwise supported for receiving a plurality of second sets of bits, each plurality being associated with a different network entity, and each plurality indicating a set of resource block set indexes associated with the corresponding network entity.

[0211] In some examples, the number of multiple second-bit sets is based on the number of network entities configured to be scheduled by DCI messages.

[0212] In some examples, to support receiving a second set of bits, the resource block set indicating component 1135 may be configured or otherwise supported for receiving a second set of bits including a subset of bits, wherein each subset of bits is associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with a network entity in the corresponding group.

[0213] In some examples, the number of bit subsets included in the second bit set is based on the number of groups of network entities configured to be scheduled by DCI messages.

[0214] In some examples, the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0215] In some examples, to support receiving a second set of bits, the resource block set indicative component 1135 may be configured or otherwise supported for receiving a second set of bits commonly associated with at least the first network entity and the second network entity, based on a resource block set index assigned to a resource block set across at least the first network entity and the second network entity, wherein each bit in the second set of bits corresponds to a different resource block set index.

[0216] In some examples, the second set indicates that a set of consecutive resource blocks associated with the first network entity is scheduled by DCI messages, and the resource block set indication component 1135 can be configured or otherwise supported to identify resource blocks between consecutive resource block sets that are scheduled for uplink shared channel messages based on the association of consecutive resource block sets with the same network entity.

[0217] In some examples, the second set indicates that the first set of resource blocks associated with the first network entity and the consecutive set of resource blocks associated with the second network entity are scheduled by DCI messages, and the resource block set indication component 1135 may be configured or otherwise supported to identify resource blocks between the first set of resource blocks and the consecutive set of resource blocks that are not scheduled for uplink shared channel messages based on the association of the first set of resource blocks and the consecutive set of resource blocks with different network entities.

[0218] In some examples, the number of bits included in the second set is based on the number of resource block sets allocated across at least the first and second network entities.

[0219] In some examples, to support receiving the first set and the second set, the resource block indicator and resource block set indicator component 1145 may be configured or otherwise support components for receiving messages that include the first set and the second set.

[0220] In some examples, the message is a DCI message.

[0221] In some examples, the format of the DCI message is based on the DCI message that schedules uplink shared channel messages to at least a first network entity and a second network entity according to the resource allocation type.

[0222] In some examples, the number of bits included in the first set is based on the subcarrier spacing associated with one or more resource blocks.

[0223] Figure 12A diagram of a system 1200 including device 1205 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or UE 115 as described herein, or a component including such devices. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1245).

[0224] I / O controller 1210 manages the input and output signals of device 1205. I / O controller 1210 can also manage peripheral devices not integrated into device 1205. In some cases, I / O controller 1210 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, it may be another known operating system. Additionally or alternatively, the I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1210 may be implemented as part of a processor (such as processor 1240). In some cases, a user may interact with device 1205 via the I / O controller 1210 or via hardware components controlled by the I / O controller 1210.

[0225] In some cases, device 1205 may include a single antenna 1225. However, in other cases, device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1215 may communicate bidirectionally via one or more antennas 1225, wired or wireless links, as described herein. For example, transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1215 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1225 for transmission; and demodulating packets received from one or more antennas 1225. Transceiver 1215, or transceiver 1215 and one or more antennas 1225, may be an example of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein.

[0226] Memory 1230 may include random access memory (RAM) and read-only memory (ROM). Memory 1230 may store computer-readable, computer-executable code 1235, including instructions that, when executed by processor 1240, cause device 1205 to perform the various functions described herein. Code 1235 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1235 may not be directly executable by processor 1240, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, memory 1230 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0227] Processor 1240 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1240 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks supporting uplink shared channel resource allocation for multi-cell scheduling). For example, device 1205 or components of device 1205 may include processor 1240 and memory 1230 coupled to or coupled to processor 1240, processor 1240 and memory 1230 being configured to perform the various functions described herein.

[0228] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. For example, the communication manager 1220 may be configured or otherwise supported to include components for receiving DCI messages indicating uplink shared channel messages scheduled to at least a first network entity and a second network entity based on a resource allocation type. The communication manager 1220 may be configured or otherwise supported to include components for receiving a first set of indices indicating one or more resource block indices based on a resource allocation type. The communication manager 1220 may be configured or otherwise supported to include components for receiving a second set of indices indicating one or more resource block set indices based on a resource allocation type. The communication manager 1220 may be configured or otherwise supported to include components for transmitting uplink shared channel messages to at least a first network entity and a second network entity based on the first and second sets.

[0229] By including or configuring a communication manager 1220 according to the example described herein, device 1205 can support techniques for uplink shared channel resource allocation for multi-cell scheduling, which can lead to improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, extended battery life, or improved utilization of processing power.

[0230] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with transceiver 1215, one or more antennas 1225, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by processor 1240, memory 1230, code 1235, or any combination thereof. For example, code 1235 may include instructions that can be executed by processor 1240 to cause device 1205 to perform various aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein, or processor 1240 and memory 1230 may be otherwise configured to perform or support such operations.

[0231] Figure 13 A block diagram 1300 of an apparatus 1305 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Apparatus 1305 may be an example of aspects of network entity 105 as described herein. Apparatus 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Apparatus 1305 may also include a processor. Each of these components may communicate with each other, for example, via one or more buses.

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

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

[0234] The communication manager 1320, receiver 1310, transmitter 1315, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein. For example, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0235] In some examples, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, CPUs, ASICs, FPGAs, or other programmable logic devices, microcontrollers, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof, configured or otherwise supporting components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

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

[0237] In some examples, the communication manager 1320 may be configured to use or otherwise coordinate with the receiver 1310, transmitter 1315, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1320 may receive information from the receiver 1310, transmit information to the transmitter 1315, or integrate with the receiver 1310, transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0238] Communication manager 1320 may support wireless communication at a first network entity according to the examples disclosed herein. For example, communication manager 1320 may be configured or otherwise supported to support components for transmitting DCI messages for uplink shared channel messages scheduled to at least a first network entity and a second network entity based on a resource allocation type. Communication manager 1320 may be configured or otherwise supported to support components for transmitting a first set of indices indicating one or more resource block indices based on a resource allocation type. Communication manager 1320 may be configured or otherwise supported to support components for transmitting a second set of indices indicating one or more resource block set indices based on a resource allocation type. Communication manager 1320 may be configured or otherwise supported to support components for receiving uplink shared channel messages based on the first set and the second set.

[0239] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 (e.g., a processor that controls or is otherwise coupled to receiver 1310, transmitter 1315, communication manager 1320, or a combination thereof) can support techniques for uplink shared channel resource allocation for multi-cell scheduling, which can result in reduced processing, lower power consumption, and more efficient use of communication resources.

[0240] Figure 14 A block diagram 1400 of an apparatus 1405 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Apparatus 1405 may be an example of aspects of apparatus 1305 as described herein or network entity 105. Apparatus 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. Apparatus 1405 may also include a processor. Each of these components may communicate with each other, for example, via one or more buses.

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

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

[0243] Device 1405 or its various components may be examples of parts used to perform various aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein. For example, communication manager 1420 may include DCI message component 1425, resource block indication component 1430, resource block set indication component 1435, uplink shared channel message component 1440, or any combination thereof. Communication manager 1420 may be examples of various aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to use or otherwise cooperate with receiver 1410, transmitter 1415, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated in combination with receiver 1410, transmitter 1415, or both to acquire information, output information, or perform various other operations as described herein.

[0244] Communication manager 1420 may support wireless communication at a first network entity according to the examples disclosed herein. DCI message component 1425 may be configured or otherwise supported for transmitting DCI messages indicating uplink shared channel messages scheduled to at least a first network entity and a second network entity based on resource allocation type. Resource block indication component 1430 may be configured or otherwise supported for transmitting a first set of indices indicating one or more resource block indices based on resource allocation type. Resource block set indication component 1435 may be configured or otherwise supported for transmitting a second set of indices indicating one or more resource block set indices based on resource allocation type. Uplink shared channel message component 1440 may be configured or otherwise supported for receiving uplink shared channel messages based on the first set and the second set.

[0245] Figure 15A block diagram 1500 is shown of a communication manager 1520 supporting uplink shared channel resource allocation for multi-cell scheduling according to one or more aspects of this disclosure. The communication manager 1520 may be an example of aspects of the communication manager 1320, communication manager 1420, or both as described herein. The communication manager 1520 or its various components may be examples of parts for performing various aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein. For example, the communication manager 1520 may include a DCI message component 1525, a resource block indication component 1530, a resource block set indication component 1535, an uplink shared channel message component 1540, a resource block indication and resource block set indication component 1545, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0246] Communication manager 1520 may support wireless communication at a first network entity according to the examples disclosed herein. DCI message component 1525 may be configured or otherwise supported for transmitting DCI messages indicating uplink shared channel messages scheduled to at least a first network entity and a second network entity based on resource allocation type. Resource block indication component 1530 may be configured or otherwise supported for transmitting a first set of indices indicating one or more resource block indices based on resource allocation type. Resource block set indication component 1535 may be configured or otherwise supported for transmitting a second set of indices indicating one or more resource block set indices based on resource allocation type. Uplink shared channel message component 1540 may be configured or otherwise supported for receiving uplink shared channel messages based on the first set and the second set.

[0247] In some examples, to support the transmission of the first set, the resource block indicator component 1530 may be configured or otherwise supported for the transmission of the first set associated with at least the first network entity and the second network entity, wherein one or more resource block indices are assigned to transmit uplink shared channel messages to at least the first network entity and the second network entity.

[0248] In some examples, the alignment based on the reference point is different for the first network entity and the second network entity, and the interleaving pattern of one or more resource block indexes is different for the first network entity and the second network entity according to the first set commonly associated with at least the first network entity and the second network entity, with the reference point used to identify the resource block index.

[0249] In some examples, to support the transmission of the first bit set, the resource block indicator component 1530 may be configured or otherwise supported for transmitting a first bit set including a subset of bits, wherein each subset of bits may be associated with a different network entity, and wherein each subset of bits indicates a set of resource block indexes associated with the corresponding network entity.

[0250] In some examples, based on the fact that the first network entity and the second network entity are different network entities, the position subset includes the first position subset associated with the first network entity and the second position subset associated with the second network entity.

[0251] In some examples, the first subset indicates a first set of resource block indices allocated for sending uplink shared channel messages to a first network entity, and the second subset indicates a second set of resource block indices allocated for sending uplink shared channel messages to a second network entity.

[0252] In some examples, the number of bit subsets included in the first set is based on the number of network entities configured to be scheduled by DCI messages.

[0253] In some examples, to support the transmission of first-order sets, the resource block indicator component 1530 may be configured or otherwise support components for transmitting multiple first-order sets, each of which is associated with a different network entity, and each of which indicates a resource block index set associated with the corresponding network entity.

[0254] In some examples, the number of multiple first-order sets is based on the number of network entities configured to be scheduled by DCI messages.

[0255] In some examples, to support the transmission of the first set, the resource block indicator component 1530 may be configured or otherwise supported for transmitting a first set including a subset of bits, wherein each subset of bits is associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with the network entities in the corresponding group.

[0256] In some examples, the number of bit subsets included in the first set is based on the number of groups of network entities configured to be scheduled by DCI messages.

[0257] In some examples, the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0258] In some examples, to support the transmission of a second bit set, the resource block set indication component 1535 may be configured or otherwise supported for transmitting a second bit set commonly associated with at least a first network entity and a second network entity based on the resource block set assigned to each network entity by a resource block index, wherein one or more resource block set indices are assigned to transmit uplink shared channel messages to at least the first network entity and the second network entity.

[0259] In some examples, the number of bits included in the second set is based on the network entities in at least the first and second network entities being associated with the highest number of resource block sets.

[0260] In some examples, the resource block set configuration associated with the first network entity differs from the resource block set configuration associated with the second network entity, based on the intra-cell protection band configuration associated with the corresponding first and second network entities.

[0261] In some examples, each resource block set configuration indicates a starting common resource block index and the number of common resource blocks associated with each resource block set, which are different for one or more resource block sets configured for the first network entity and the second network entity.

[0262] In some examples, to support the transmission of a second set of bits, the resource block set indicator component 1535 may be configured or otherwise supported for transmitting a second set of bits including a subset of bits, wherein each subset of bits is associated with a different network entity, and wherein each subset of bits indicates a set of resource block set indexes associated with the corresponding network entity.

[0263] In some examples, based on the fact that the first network entity and the second network entity are different network entities, the position subset includes the first position subset associated with the first network entity and the second position subset associated with the second network entity.

[0264] In some examples, the first subset indicates the first set of resource block indexes allocated for sending uplink shared channel messages to the first network entity, and the second subset indicates the second set of resource block indexes allocated for sending uplink shared channel messages to the second network entity.

[0265] In some examples, the number of bit subsets included in the first set is based on the number of network entities configured to be scheduled by DCI messages.

[0266] In some examples, to support the transmission of second bit sets, the resource block set indication component 1535 may be configured or otherwise support components for transmitting multiple second bit sets, each of which is associated with a different network entity, and each of which indicates a set of resource block set indexes associated with the corresponding network entity.

[0267] In some examples, the number of multiple second-bit sets is based on the number of network entities configured to be scheduled by DCI messages.

[0268] In some examples, to support the transmission of a second set of bits, the resource block set indication component 1535 may be configured or otherwise supported for transmitting a second set of bits including a subset of bits, wherein each subset of bits is associated with one or more network entities in a different group, and wherein each subset of bits indicates a set of resource block indexes associated with a network entity in the corresponding group.

[0269] In some examples, the number of bit subsets included in the second bit set is based on the number of groups of network entities configured to be scheduled by DCI messages.

[0270] In some examples, the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0271] In some examples, to support the transmission of a second bit set, the resource block set indicative component 1535 may be configured or otherwise supported for transmitting a second bit set commonly associated with at least the first network entity and the second network entity, based on a resource block set index assigned to a resource block set across at least the first network entity and the second network entity, wherein each bit in the second bit set corresponds to a different resource block set index.

[0272] In some examples, the second set indicates that a set of consecutive resource blocks associated with the first network entity is scheduled by DCI messages, and the resource block set indication component 1535 can be configured or otherwise supported to identify resource blocks between consecutive resource block sets that are scheduled for uplink shared channel messages based on the association of consecutive resource block sets with the same network entity.

[0273] In some examples, the second set indicates that the first set of resource blocks associated with the first network entity and the consecutive set of resource blocks associated with the second network entity are scheduled by DCI messages, and the resource block set indication component 1535 may be configured or otherwise supported to identify resource blocks between the first set of resource blocks and the consecutive set of resource blocks that are not scheduled for uplink shared channel messages based on the association of the first set of resource blocks and the consecutive set of resource blocks with different network entities.

[0274] In some examples, the number of bits included in the second set is based on the number of resource block sets allocated across at least the first and second network entities.

[0275] In some examples, to support the sending of the first set and the second set, the resource block indicator and resource block set indicator component 1545 may be configured or otherwise support components for sending messages that include the first set and the second set.

[0276] In some examples, the message is a DCI message.

[0277] In some examples, the format of the DCI message is based on the DCI message that schedules uplink shared channel messages to at least a first network entity and a second network entity according to the resource allocation type.

[0278] In some examples, the number of bits included in the first set is based on the subcarrier spacing associated with one or more resource blocks.

[0279] Figure 16 A diagram of a system 1600 including device 1605 supporting uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Device 1605 may be an example of device 1305, device 1405, or network entity 105 as described herein, or a component including such device. Device 1605 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1605 may include components supporting output and acquisition of communication, such as a communication manager 1620, transceiver 1610, antenna 1615, memory 1625, code 1630, and processor 1635. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1640).

[0280] Transceiver 1610 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1610 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1610 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1605 may include one or more antennas 1615 that may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1610 may also include a modem for modulating signals, for providing modulated signals for transmission (e.g., via one or more antennas 1615, via a wired transmitter), for receiving modulated signals (e.g., from one or more antennas 1615, from a wired receiver), and for demodulating signals. In some embodiments, transceiver 1610 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1615 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1615 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1610 may include one or more processor or memory components or be configured to couple to said one or more processor or memory components, said one or more processor or memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1610, or transceiver 1610 and one or more antennas 1615, or transceiver 1610 and one or more antennas 1615 and one or more processor or memory components (e.g., processor 1635 or memory 1625 or both) may be included in a chip or chip assembly mounted in device 1605. In some examples, the transceiver may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0281] Memory 1625 may include RAM and ROM. Memory 1625 may store computer-readable, computer-executable code 1630, including instructions that, when executed by processor 1635, cause device 1605 to perform the various functions described herein. Code 1630 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1630 may not be directly executable by processor 1635, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, in addition, memory 1625 may also include a BIOS that controls basic hardware or software operation, such as interaction with peripheral components or devices.

[0282] Processor 1635 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, processor 1635 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1635. Processor 1635 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1625) to cause device 1605 to perform various functions (e.g., functions or tasks supporting uplink shared channel resource allocation for multi-cell scheduling). For example, device 1605 or components thereof may include processor 1635 and memory 1625 coupled to processor 1635, wherein processor 1635 and memory 1625 are configured to perform the various functions described herein. Processor 1635 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 1630) to perform the functions of device 1605. Processor 1635 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1605 (such as within memory 1625). In some specific implementations, processor 1635 may be a component of a processing system. A processing system can generally refer to a system or series of machines or components that receive input and process that input to produce a set of outputs that can be passed to other systems or components, such as device 1605. For example, the processing system of device 1605 may refer to a system that includes various other components or sub-components of device 1605 (such as processor 1635, or transceiver 1610, or communication manager 1620, or other components or combinations of components of device 1605). The processing system of device 1605 can interface with other components of device 1605 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1605 may include a processing system and one or more interfaces for outputting information or for receiving information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to receive information, or the same interface configured to both output and receive information, and other specific implementations. In some specific implementations, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1605 to transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1605 to receive information or signal input, and such information to be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface may also receive information or signal input, and the second interface may also output information or signal output.

[0283] In some examples, bus 1640 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1640 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1605, or communication performed between different components of device 1605 that are co-addressable or located in different locations (e.g., where device 1605 may refer to a system in which one or more of communication manager 1620, transceiver 1610, memory 1625, code 1630, and processor 1635 may be located in one of the different components or partitioned between the different components).

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

[0285] Communication manager 1620 may support wireless communication at a first network entity according to the examples disclosed herein. For example, communication manager 1620 may be configured or otherwise supported to support components for transmitting DCI messages for uplink shared channel messages scheduled to at least a first network entity and a second network entity based on resource allocation types. Communication manager 1620 may be configured or otherwise supported to support components for transmitting a first set of indices indicating one or more resource block indices based on resource allocation types. Communication manager 1620 may be configured or otherwise supported to support components for transmitting a second set of indices indicating one or more resource block set indices based on resource allocation types. Communication manager 1620 may be configured or otherwise supported to support components for receiving uplink shared channel messages based on the first and second sets.

[0286] By including or configuring a communication manager 1620 according to the example described herein, device 1605 can support techniques for uplink shared channel resource allocation for multi-cell scheduling, which can lead to improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, extended battery life, or improved utilization of processing power.

[0287] In some examples, the communication manager 1620 may be configured to use or otherwise coordinate with the transceiver 1610, one or more antennas 1615 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported or performed by the transceiver 1610, processor 1635, memory 1625, code 1630, or any combination thereof. For example, code 1630 may include instructions that can be executed by the processor 1635 to cause the device 1605 to perform various aspects of uplink shared channel resource allocation for multi-cell scheduling as described herein, or the processor 1635 and memory 1625 may be otherwise configured to perform or support such operations.

[0288] Figure 17 A flowchart illustrating a method 1700 for uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Operation of method 1700 may be implemented by a UE or its components as described herein. For example, operation of method 1700 may be performed by, as referenced... Figures 1 to 12 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0289] At 1705, the method may include receiving a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type. The operation of 1705 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 11 The DCI message component 1125 is used to execute this.

[0290] At 1710, the method may include receiving a first set of indices indicating one or more resource block indices based on the resource allocation type. The operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 11The resource block instruction component 1130 is used to execute this.

[0291] At 1715, the method may include receiving a second set of bits indicating one or more resource block set indices based on the resource allocation type. The operation of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to [reference needed]. Figure 11 The resource block set instruction component 1135 is used to execute this.

[0292] At 1720, the method may include sending an uplink shared channel message to at least a first network entity and a second network entity based on a first set and a second set. The operation of 1720 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1720 may be derived from references... Figure 11 The uplink shared channel message component 1140 described herein is used to perform this action.

[0293] Figure 18 A flowchart illustrating a method 1800 for uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. Operation of method 1800 may be implemented by a UE or its components as described herein. For example, operation of method 1800 may be performed by, as described in reference... Figures 1 to 12 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0294] At 1805, the method may include receiving a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type. The operation of 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 11 The DCI message component 1125 is used to execute this.

[0295] At 1815, the method may include receiving a first set commonly associated with at least a first network entity and a second network entity, wherein one or more resource block indices are allocated for sending uplink shared channel messages to at least the first network entity and the second network entity. The operation of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1815 may be provided by reference to [reference needed]. Figure 11 The resource block instruction component 1130 is used to execute this.

[0296] At 1820, the method may include receiving a second set of bits indicating one or more resource block set indices based on the resource allocation type. The operation at 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1820 may be provided by reference to [reference needed]. Figure 11 The resource block set instruction component 1135 is used to execute this.

[0297] At 1825, the method may include sending an uplink shared channel message to at least a first network entity and a second network entity based on a first set and a second set. The operation at 1825 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1825 may be provided by reference to [reference needed]. Figure 11 The uplink shared channel message component 1140 described herein is used to perform this action.

[0298] Figure 19 A flowchart illustrating a method 1900 for uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. The operation of method 1900 may be implemented by a network entity or its components as described herein. For example, the operation of method 1900 may be implemented by, as referenced... Figures 1 to 8 as well as Figures 13 to 16 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the function.

[0299] At 1905, the method may include sending a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type. The operation of 1905 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1905 may be provided by reference to [reference needed]. Figure 15 The DCI message component 1525 is used to execute this.

[0300] At 1910, the method may include sending a first set of indices indicating one or more resource block indices based on the resource allocation type. The operation of 1910 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1910 may be provided by reference to [reference needed]. Figure 15 The resource block instruction component 1530 is used to execute this.

[0301] At 1915, the method may include sending a second set of bits indicating one or more resource block set indices based on the resource allocation type. The operation at 1915 can be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1915 may be provided by reference to [reference needed]. Figure 15 The resource block set instruction component 1535 is used to execute this.

[0302] At 1920, the method may include receiving an uplink shared channel message based on a first set and a second set. The operation at 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1920 may be derived from references... Figure 15 The uplink shared channel message component 1540 described herein is used to perform this action.

[0303] Figure 20 A flowchart illustrating a method 2000 for uplink shared channel resource allocation for multi-cell scheduling, according to one or more aspects of this disclosure, is shown. The operation of method 2000 may be implemented by a network entity or its components as described herein. For example, the operation of method 2000 may be implemented by, as referenced... Figures 1 to 8 as well as Figures 13 to 16 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the function.

[0304] At 2005, the method may include sending a DCI message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type. The operation of 2005 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2005 may be provided by reference to [reference needed]. Figure 15 The DCI message component 1525 is used to execute this.

[0305] At 2015, the method may include sending a first set comprising subsets of bits, wherein each subset of bits is associated with a different network entity, and wherein each subset of bits indicates a set of resource block indexes associated with the corresponding network entity. The operation of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2015 may be provided by reference to [reference needed]. Figure 15 The resource block instruction component 1530 is used to execute this.

[0306] At 2020, the method may include sending a second set of bits indicating one or more resource block set indices based on the resource allocation type. The operation of 2020 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2020 may be provided by reference to [reference needed]. Figure 15 The resource block set instruction component 1535 is used to execute this.

[0307] At 2025, the method may include receiving an uplink shared channel message based on a first set and a second set. The operation of 2025 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2025 may be provided by reference to [reference needed]. Figure 15 The uplink shared channel message component 1540 described herein is used to perform this action.

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

[0309] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a downlink control information message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; receiving, at least partially based on the resource allocation type, a first set indicating one or more resource block indices; receiving, at least partially based on the resource allocation type, a second set indicating one or more resource block set indices; and transmitting the uplink shared channel message to at least the first network entity and the second network entity according to the first set and the second set.

[0310] Aspect 2: According to the method of aspect 1, receiving the first bit set includes: receiving the first bit set commonly associated with at least the first network entity and the second network entity, wherein one or more resource block indexes are allocated for sending the uplink shared channel message to at least the first network entity and the second network entity.

[0311] Aspect 3: According to the method of aspect 2, wherein the alignment based at least in part on the reference point is different for the first network entity and the second network entity, and the interleaving pattern of the one or more resource block indexes is different for the first network entity and the second network entity according to the first bit set commonly associated with at least the first network entity and the second network entity, wherein the reference point is used to identify the resource block index.

[0312] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the first bit set comprises: receiving the first bit set including bit subsets, wherein each bit subset is associated with a different network entity, and wherein each bit subset indicates a set of resource block indexes associated with the corresponding network entity.

[0313] Aspect 5: According to the method of aspect 4, wherein the position subset is based at least in part on the fact that the first network entity and the second network entity are different network entities, the position subset includes a first position subset associated with the first network entity and a second position subset associated with the second network entity.

[0314] Aspect 6: According to the method of aspect 5, wherein the first subset indicates a first set of resource block indices allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second set of resource block indices allocated for sending the uplink shared channel message to the second network entity.

[0315] Aspect 7: The method according to any one of Aspects 4 to 6, wherein the number of the subset of positions included in the first set is based at least in part on the number of network entities configured to be scheduled by the downlink control information message.

[0316] Aspect 8: The method according to any one of Aspects 1 to 7, wherein receiving the second bit set comprises: receiving a plurality of first bit sets, wherein each plurality is associated with a different network entity, and wherein each plurality indicates a set of resource block indexes associated with a corresponding network entity.

[0317] Aspect 9: According to the method of aspect 8, the number of the plurality of first-order sets is at least partially based on the number of network entities configured to be scheduled by the downlink control information messages.

[0318] Aspect 10: The method according to any one of Aspects 1 to 9, wherein receiving the first bit set comprises: receiving the first bit set including bit subsets, wherein each bit subset is associated with one or more network entities of a different group, and wherein each bit subset indicates a set of resource block indexes associated with network entities of the corresponding group.

[0319] Aspect 11: The method of claim 10, wherein the number of bit subsets included in the first set is based at least in part on the number of groups of network entities configured to be scheduled by the downlink control information messages.

[0320] Aspect 12: The method according to any one of Aspects 10 to 11, wherein the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0321] Aspect 13: The method according to any one of Aspects 1 to 12, wherein receiving the second bit set comprises: receiving the second bit set commonly associated with at least the first network entity and the second network entity based at least in part on a resource block set assigned to each network entity by a resource block index, wherein one or more resource block set indices are allocated for sending the uplink shared channel message to at least the first network entity and the second network entity.

[0322] Aspect 14: According to the method of aspect 13, the number of bits included in the second bit set is at least partially based on the fact that at least one of the first network entities and the second network entity is associated with the highest number of resource block sets.

[0323] Aspect 15: The method according to any one of Aspects 13 to 14, wherein it is based at least in part on the intra-cell protection band configuration associated with the respective first network entity and second network entity, and the resource block set configuration associated with the first network entity is different from the resource block set configuration associated with the second network entity.

[0324] Aspect 16: According to the method of aspect 15, each resource block set is configured to indicate a starting common resource block index and a number of common resource blocks associated with each resource block set, wherein the starting common resource block index, the number of common resource blocks, or both are different for one or more resource block sets configured for the first network entity and the second network entity.

[0325] Aspect 17: The method according to any one of Aspects 1 to 16, wherein receiving the second bit set comprises: receiving the second bit set including bit subsets, wherein each bit subset is associated with a different network entity, and wherein each bit subset indicates a set of resource block set indexes associated with the corresponding network entity.

[0326] Aspect 18: The method according to aspect 17, wherein the position subset is based at least in part on the fact that the first network entity and the second network entity are different network entities, the position subset includes a first position subset associated with the first network entity and a second position subset associated with the second network entity.

[0327] Aspect 19: According to the method of aspect 18, wherein the first subset indicates a first resource block set index set allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second resource block set index set allocated for sending the uplink shared channel message to the first network entity.

[0328] Aspect 20: The method according to any one of Aspects 17 to 19, wherein the number of the subset of positions included in the first set is based at least in part on the number of network entities configured to be scheduled by the downlink control information message.

[0329] Aspect 21: The method according to any one of Aspects 1 to 20, wherein receiving the second bit set comprises: receiving a plurality of second bit sets, wherein each plurality is associated with a different network entity, and wherein each plurality indicates a set of resource block set indexes associated with a corresponding network entity.

[0330] Aspect 22: According to the method of aspect 21, the number of the plurality of the plurality of second bit sets is at least partially based on the number of network entities configured to be scheduled by the downlink control information messages.

[0331] Aspect 23: The method according to any one of Aspects 1 to 22, wherein receiving the second bit set comprises: receiving the second bit set including bit subsets, wherein each bit subset is associated with one or more network entities of a different group, and wherein each bit subset indicates a set of resource block indexes associated with network entities of the corresponding group.

[0332] Aspect 24: The method of claim 23, wherein the number of bit subsets included in the second bit set is based at least in part on the number of groups of network entities configured to be scheduled by the downlink control information messages.

[0333] Aspect 25: The method according to any one of Aspects 23 to 24, wherein the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0334] Aspect 26: The method according to any one of Aspects 1 to 25, wherein receiving the second bit set comprises: receiving the second bit set commonly associated with at least the first network entity and the second network entity, at least in part based on a resource block set index assigned to a resource block set across at least the first network entity and the second network entity, wherein each bit in the second bit set corresponds to a different resource block set index.

[0335] Aspect 27: The method according to aspect 26, wherein the second bit set indicates that a set of consecutive resource blocks associated with the first network entity is scheduled by the downlink control information message, the method further comprising: identifying, at least in part, based on the fact that the set of consecutive resource blocks is associated with the same network entity, that resource blocks between the sets of consecutive resource blocks are scheduled for the uplink shared channel message.

[0336] Aspect 28: The method of any one of Aspects 26 to 27, wherein the second bit set indicates that a first set of resource blocks associated with the first network entity and a consecutive set of resource blocks associated with the second network entity are scheduled by the downlink control information message, the method further comprising: identifying resource blocks between the first set of resource blocks and the consecutive set of resource blocks that are not scheduled for the uplink shared channel message, at least in part based on the association of the first set of resource blocks and the consecutive set of resource blocks with different network entities.

[0337] Aspect 29: The method according to any one of Aspects 26 to 28, wherein the number of bits included in the second bit set is based at least in part on the number of resource block sets allocated across at least the first network entity and the second network entity.

[0338] Aspect 30: The method according to any one of aspects 1 to 29, wherein receiving the first bit set and the second bit set comprises: receiving a message including the first bit set and the second bit set.

[0339] Aspect 31: According to the method of aspect 30, the message is the downlink control information message.

[0340] Aspect 32: The method according to any one of Aspects 1 to 31, wherein the format of the downlink control information message is at least partially based on the downlink control information message scheduling the uplink shared channel message to at least the first network entity and the second network entity according to the resource allocation type.

[0341] Aspect 33: The method according to any one of aspects 1 to 32, wherein the number of bits included in the first set is based at least in part on the subcarrier spacing associated with the one or more resource blocks.

[0342] Aspect 34: A method for wireless communication at a first network entity, the method comprising: transmitting a downlink control information message indicating an uplink shared channel message scheduled to at least the first network entity and a second network entity according to a resource allocation type; transmitting a first set indicating one or more resource block indices, at least partially based on the resource allocation type; transmitting a second set indicating one or more resource block set indices, at least partially based on the resource allocation type; and receiving the uplink shared channel message according to the first set and the second set.

[0343] Aspect 35: According to the method of aspect 34, sending the first bit set includes: sending the first bit set commonly associated with at least the first network entity and the second network entity, wherein one or more resource block indexes are allocated for sending the uplink shared channel message to at least the first network entity and the second network entity.

[0344] Aspect 36: The method according to aspect 35, wherein the alignment based at least in part on the reference point is different for the first network entity and the second network entity, and the interleaving pattern of the one or more resource block indexes is different for the first network entity and the second network entity according to the first bit set commonly associated with at least the first network entity and the second network entity, wherein the reference point is used to identify the resource block index.

[0345] Aspect 37: The method according to any one of Aspects 34 to 36, wherein sending the first bit set comprises: sending the first bit set including bit subsets, wherein each bit subset is associated with a different network entity, and wherein each bit subset indicates a set of resource block indexes associated with a corresponding network entity.

[0346] Aspect 38: The method according to aspect 37, wherein the position subset is based at least in part on the fact that the first network entity and the second network entity are different network entities, the position subset includes a first position subset associated with the first network entity and a second position subset associated with the second network entity.

[0347] Aspect 39: According to the method of aspect 38, wherein the first subset indicates a first set of resource block indices allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second set of resource block indices allocated for sending the uplink shared channel message to the second network entity.

[0348] Aspect 40: The method according to any one of Aspects 37 to 39, wherein the number of the subset of positions included in the first set is based at least in part on the number of network entities configured to be scheduled by the downlink control information message.

[0349] Aspect 41: The method according to any one of Aspects 34 to 40, wherein sending the first bit set comprises: sending a plurality of bit sets, wherein each plurality is associated with a different network entity, and wherein each plurality indicates a set of resource block indexes associated with a corresponding network entity.

[0350] Aspect 42: According to the method of aspect 41, the number of the plurality of first-order sets is at least partially based on the number of network entities configured to be scheduled by the downlink control information messages.

[0351] Aspect 43: The method according to any one of Aspects 34 to 42, wherein sending the first bit set comprises: sending the first bit set including bit subsets, wherein each bit subset is associated with one or more network entities of a different group, and wherein each bit subset indicates a set of resource block indexes associated with the network entities of the corresponding group.

[0352] Aspect 44: The method of claim 43, wherein the number of bit subsets included in the first set is based at least in part on the number of groups of network entities configured to be scheduled by the downlink control information messages.

[0353] Aspect 45: The method according to any one of aspects 43 to 44, wherein the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0354] Aspect 46: The method according to any one of Aspects 34 to 45, wherein sending the second bit set comprises: sending the second bit set commonly associated with at least the first network entity and the second network entity based at least in part on the resource block set to which resource block indexes are assigned to each network entity, wherein one or more resource block set indexes are allocated for sending the uplink shared channel message to at least the first network entity and the second network entity.

[0355] Aspect 47: According to the method of aspect 46, the number of bits included in the second bit set is at least partially based on the fact that at least one of the first network entities and the second network entity is associated with the highest number of resource block sets.

[0356] Aspect 48: The method according to any one of Aspects 46 to 47, wherein it is based at least in part on the intra-cell protection band configuration associated with the respective first network entity and second network entity, and the resource block set configuration associated with the first network entity is different from the resource block set configuration associated with the second network entity.

[0357] Aspect 49: The method according to aspect 48, wherein each resource block set is configured to indicate a starting common resource block index and a number of common resource blocks associated with each resource block set, the starting common resource block index, the number of common resource blocks, or both, are different for one or more resource block sets configured for the first network entity and the second network entity.

[0358] Aspect 50: The method according to any one of Aspects 34 to 49, wherein sending the second bit set comprises: sending the second bit set including bit subsets, wherein each bit subset is associated with a different network entity, and wherein each bit subset indicates a set of resource block set indexes associated with the corresponding network entity.

[0359] Aspect 51: The method according to aspect 50, wherein the position subset is based at least in part on the fact that the first network entity and the second network entity are different network entities, the position subset includes a first position subset associated with the first network entity and a second position subset associated with the second network entity.

[0360] Aspect 52: According to the method of aspect 51, wherein the first subset indicates a first resource block set index set allocated for sending the uplink shared channel message to the first network entity, and the second subset indicates a second resource block set index set allocated for sending the uplink shared channel message to the first network entity.

[0361] Aspect 53: The method according to any one of aspects 50 to 52, wherein the number of the subset of positions included in the first set is based at least in part on the number of network entities configured to be scheduled by the downlink control information message.

[0362] Aspect 54: The method according to any one of Aspects 34 to 53, wherein sending the second bit set comprises: sending a plurality of second bit sets, wherein each plurality is associated with a different network entity, and wherein each plurality indicates a set of resource block set indexes associated with the corresponding network entity.

[0363] Aspect 55: According to the method of aspect 54, the number of the plurality of the plurality of second bit sets is at least partially based on the number of network entities configured to be scheduled by the downlink control information messages.

[0364] Aspect 56: The method according to any one of Aspects 34 to 55, wherein sending the second set of bits comprises: sending the second set of bits including subsets of bits, wherein each subset of bits is associated with one or more network entities of a different group, and wherein each subset of bits indicates a set of resource block indexes associated with the network entities of the corresponding group.

[0365] Aspect 57: The method of claim 56, wherein the number of bit subsets included in the second bit set is based at least in part on the number of groups of network entities configured to be scheduled by the downlink control information messages.

[0366] Aspect 58: The method according to any one of Aspects 56 to 57, wherein the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

[0367] Aspect 59: The method according to any one of Aspects 34 to 58, wherein sending the second bit set comprises: sending the second bit set commonly associated with at least the first network entity and the second network entity based at least in part on a resource block set index assigned to a resource block set across at least the first network entity and the second network entity, wherein each bit in the second bit set corresponds to a different resource block set index.

[0368] Aspect 60: The method according to aspect 59, wherein the second bit set indicates that a set of consecutive resource blocks associated with the first network entity is scheduled by the downlink control information message, the method further comprising: identifying, at least in part, based on the fact that the set of consecutive resource blocks is associated with the same network entity, that resource blocks between the sets of consecutive resource blocks are scheduled for the uplink shared channel message.

[0369] Aspect 61: The method according to any one of Aspects 59 to 60, wherein the second bit set indicates that a first set of resource blocks associated with the first network entity and a consecutive set of resource blocks associated with the second network entity are scheduled by the downlink control information message, the method further comprising: identifying resource blocks between the first set of resource blocks and the consecutive set of resource blocks that are not scheduled for the uplink shared channel message, at least in part based on the fact that the first set of resource blocks and the consecutive set of resource blocks are associated with different network entities.

[0370] Aspect 62: The method according to any one of aspects 59 to 61, wherein the number of bits included in the second bit set is based at least in part on the number of resource block sets allocated across at least the first network entity and the second network entity.

[0371] Aspect 63: The method according to any one of aspects 34 to 62, wherein sending the first bit set and the second bit set comprises: sending a message including the first bit set and the second bit set.

[0372] Aspect 64: According to the method of aspect 63, the message is the downlink control information message.

[0373] Aspect 65: The method according to any one of Aspects 34 to 64, wherein the format of the downlink control information message is at least partially based on the downlink control information message scheduling the uplink shared channel message to at least the first network entity and the second network entity according to the resource allocation type.

[0374] Aspect 66: The method according to any one of Aspects 34 to 65, wherein the number of bits included in the first set is based at least in part on the subcarrier spacing associated with the one or more resource blocks.

[0375] Aspect 67: An apparatus for wireless communication 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 the method according to any one of aspects 1 to 33.

[0376] Aspect 68: 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 33.

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

[0378] Aspect 70: An apparatus for wireless communication at a first 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 the method according to any one of aspects 34 to 66.

[0379] Aspect 71: An apparatus for wireless communication at a first network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 34 to 66.

[0380] Aspect 72: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code including instructions executable by a processor to perform the method according to any one of aspects 34 to 66.

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

[0382] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0384] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, 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 cooperating with a DSP core, or any other such configuration).

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

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

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

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

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

[0390] This document describes exemplary configurations in conjunction with the accompanying drawings and does not represent all achievable or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," not "preferred" or "advantageous over other examples." Detailed descriptions include specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. 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 downlink control information message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; receiving a first set of first bits indicating one or more resource block indices based at least in part on the resource allocation type; receiving a second set of bits indicating one or more resource block set indexes based at least in part on the resource allocation type; as well as The uplink shared channel message is sent to at least the first network entity and the second network entity according to the first set of bits and the second set of bits.

2. The apparatus of claim 1 , wherein the instructions to receive the first set of bits are executable by the processor to cause the apparatus to: The first set of bits commonly associated with at least the first network entity and the second network entity is received, wherein the one or more resource block indexes are allocated for sending the uplink shared channel message to at least the first network entity and the second network entity.

3. The apparatus of claim 2 , wherein the alignment based at least in part on a reference point is different for the first network entity and the second network entity, and the interleaving pattern of the one or more resource block indexes is different for the first network entity and the second network entity according to the first set of bits commonly associated with at least the first network entity and the second network entity, the reference point being used to identify the resource block index.

4. The device of claim 1, wherein the instructions to receive the first set of bits are executable by the processor to cause the device to: The first set of bits comprising subsets of bits is received, wherein each subset of bits is associated with a different network entity, and wherein each subset of bits indicates a set of resource block indices associated with the corresponding network entity.

5. The apparatus of claim 4, wherein the subset of bits comprises a first subset of bits associated with the first network entity and a second subset of bits associated with the second network entity based at least in part on the first network entity and the second network entity being different network entities.

6. The apparatus of claim 5, wherein the first subset of bits indicates a first set of resource block indices allocated for sending the uplink shared channel message to the first network entity, and the second subset of bits indicates a second set of resource block indices allocated for sending the uplink shared channel message to the second network entity.

7. The apparatus of claim 4, wherein the number of the subsets of bits included in the first set is based at least in part on a number of network entities configured to be scheduled by the downlink control information message.

8. The device of claim 1, wherein the instructions to receive the second set of bits are executable by the processor to cause the device to: A plurality of first bit sets are received, wherein each plurality is associated with a different network entity, and wherein each plurality indicates a set of resource block indices associated with the corresponding network entity.

9. The apparatus of claim 8, wherein a number of the plurality of the plurality of first bit sets is based at least in part on a number of network entities configured to be scheduled by the downlink control information message.

10. The device of claim 1, wherein the instructions to receive the first set of bits are executable by the processor to cause the device to: The first set of bits comprising subsets of bits is received, wherein each subset of bits is associated with a different group of one or more network entities, and wherein each subset of bits indicates a set of resource block indices associated with a corresponding group of network entities.

11. The apparatus of claim 10, wherein the number of subsets of bits included in the first set is based at least in part on a number of groups of network entities configured to be scheduled by the downlink control information message. 12 . The apparatus of claim 10 , wherein the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

13. The device of claim 1, wherein the instructions to receive the second set of bits are executable by the processor to cause the device to: The second set of bits commonly associated with at least the first network entity and the second network entity is received based at least in part on a resource block set assigned to each network entity based on a resource block index, wherein the one or more resource block set indexes are allocated for sending the uplink shared channel message to at least the first network entity and the second network entity.

14. The apparatus of claim 13, wherein a number of bits included in the second set of bits is based at least in part on a network entity of at least the first network entity and the second network entity being associated with a highest number of resource block sets.

15. The apparatus of claim 13, wherein the resource block set configuration associated with the first network entity is different from the resource block set configuration associated with the second network entity based at least in part on an intra-cell guard band configuration associated with the respective first and second network entities.

16. The apparatus of claim 15, wherein each resource block set configuration indicates a starting common resource block index and a number of common resource blocks associated with each resource block set, the starting common resource block index, the number of common resource blocks, or both being different for one or more of the resource block sets configured for the first network entity and the second network entity.

17. The device of claim 1, wherein the instructions to receive the second set of bits are executable by the processor to cause the device to: The second set of bits comprising subsets of bits is received, wherein each subset of bits is associated with a different network entity, and wherein each subset of bits indicates a set of resource block set indices associated with a corresponding network entity.

18. The apparatus of claim 17, wherein the subset of bits comprises a first subset of bits associated with the first network entity and a second subset of bits associated with the second network entity based at least in part on the first network entity and the second network entity being different network entities.

19. The apparatus of claim 18, wherein the first subset of bits indicates a first set of resource block set indices allocated for sending the uplink shared channel message to the first network entity, and the second subset of bits indicates a second set of resource block set indices allocated for sending the uplink shared channel message to the second network entity.

20. The apparatus of claim 17, wherein the number of the subsets of bits included in the first set is based at least in part on a number of network entities configured to be scheduled by the downlink control information message.

21. The device of claim 1, wherein the instructions to receive the second set of bits are executable by the processor to cause the device to: A plurality of second sets of bits are received, wherein each plurality is associated with a different network entity, and wherein each plurality indicates a set of resource block set indices associated with a corresponding network entity.

22. The apparatus of claim 21, wherein a number of the plurality of the plurality of second sets of bits is based at least in part on a number of network entities configured to be scheduled by the downlink control information message.

23. The device of claim 1, wherein the instructions to receive the second set of bits are executable by the processor to cause the device to: The second set of bits comprising subsets of bits is received, wherein each subset of bits is associated with a different group of one or more network entities, and wherein each subset of bits indicates a set of resource block indices associated with a corresponding group of network entities.

24. The apparatus of claim 23, wherein the number of subsets of bits included in the second set of bits is based at least in part on a number of groups of network entities configured to be scheduled by the downlink control information message.

25. The apparatus of claim 23, wherein the first network entity and the second network entity are included in the same group of network entities or in different groups of network entities.

26. The device of claim 1, wherein the instructions to receive the second set of bits are executable by the processor to cause the device to: The second set of bits commonly associated with at least the first network entity and the second network entity is received based at least in part on a resource block set index being assigned to a resource block set across at least the first network entity and the second network entity, wherein each bit in the second set of bits corresponds to a different resource block set index.

27. The apparatus of claim 26, wherein the second set of bits indicates that a set of consecutive resource blocks associated with the first network entity is scheduled by the downlink control information message, and the instructions are further executable by the processor to cause the apparatus to: Resource blocks between the consecutive sets of resource blocks are identified as being scheduled for the uplink shared channel message based at least in part on the consecutive sets of resource blocks being associated with a same network entity.

28. A method for wireless communication at a user equipment (UE), the method comprising: receiving a downlink control information message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; receiving a first set of first bits indicating one or more resource block indices based at least in part on the resource allocation type; receiving a second set of bits indicating one or more resource block set indexes based at least in part on the resource allocation type; as well as The uplink shared channel message is sent to at least the first network entity and the second network entity according to the first set of bits and the second set of bits.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for receiving a downlink control information message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; means for receiving a first set of first bits indicating one or more resource block indices based at least in part on the resource allocation type; means for receiving a second set of bits indicating one or more resource block set indices based at least in part on the resource allocation type; and Means for sending the uplink shared channel message to at least the first network entity and the second network entity according to the first set of bits and the second set of bits.

30. A non-transitory computer readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: receiving a downlink control information message indicating an uplink shared channel message scheduled to at least a first network entity and a second network entity according to a resource allocation type; receiving a first set of first bits indicating one or more resource block indices based at least in part on the resource allocation type; receiving a second set of bits indicating one or more resource block set indexes based at least in part on the resource allocation type; as well as The uplink shared channel message is sent to at least the first network entity and the second network entity according to the first set of bits and the second set of bits.

Images