Inter-block time interleaving

Abstract

Methods, systems, and devices for conducting wireless communications are described. A network entity may send a DCI (Distributed Control Information Code) to the UE for scheduling instances of one or more MBS TBs, where multiple instances of the one or more TBs are time-interleaved. For example, the network entity may send a first set of DCIs for scheduling a first group of instances of a first TB and a second set of DCIs for scheduling a second group of instances of a second TB, wherein at least one instance in the first group of instances may be interleaved with the instances in the second group. In some cases, the first set of DCIs and the second set of DCIs may include a single DCI for scheduling the respective group of instances, or a DCI for each instance in the respective group of instances. Additionally or alternatively, the network entity may indicate to the UE one or more parameters associated with time interleaving between MBS TBs.

Description

Cross-references

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 506,982, entitled “INTER-TRANSPORTBLOCK TIME INTERLEAVING”, filed November 10, 2023, by Liu et al., which is assigned to the assignee of this application and is expressly incorporated herein by reference. introduction

[0002] The following pertains to wireless communication, including time interleaving between transport blocks. 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 can support communication with multiple users by sharing available system resources, such as 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 of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses supporting time interleaving between transport blocks (TBs), such as in multicast broadcast services (MBS). For example, the described technology provides a network entity for sending (e.g., broadcast, multicast) downlink control information (DCI) messages (e.g., referred to herein as DCIs) to user equipment (UEs), wherein the DCIs can schedule multiple instances of one or more TBs, and wherein the multiple instances of the one or more TBs can be interleaved (e.g., time-interleaved). For example, the network entity can send a first set of DCIs scheduling a first set of instances of a first TB and a second set of DCIs scheduling a second set of instances of a second TB, wherein at least one instance in the first set of instances can be interleaved with an instance in the second set.

[0004] In some aspects, the first set of DCIs and the second set of DCIs may each include a corresponding DCI for each corresponding instance in the first set of instances and the second set of instances, respectively (e.g., the ratio of DCI to instance is one-to-one). For example, the first DCI message may schedule the first transmission of a TB, the second DCI may schedule the first repetition of a TB, and so on. In some examples, the DCI may additionally include a TB indicator (e.g., NDI, HPI, or both), thereby allowing the UE receiving the instance to determine that various instances of the TB belong to the same TB (e.g., if various instances of the TB are using the same HPI, the same NDI, or both). The UE may then decode the TB, for example, by performing soft combination on the received instances of the TB. Additionally or alternatively, the network entity may indicate a duration to the UE, wherein the UE may determine that two instances of the TB belong to the same TB based on whether multiple TBs are received within that duration.

[0005] In some respects, network entities can use a single DCI to schedule multiple instances of a single TB (e.g., multiple RVs or multiple duplicates of a TB). The network entity can also indicate to the UE the number of instances in each group and the time delay between instances in each group.

[0006] Additionally or alternatively, the network entity may send a DCI to schedule instances of both the first TB and the second TB. For example, the DCI may have a format that indicates the number of TBs, the number of instances of each TB within the TBs, the interleaving mode between TBs and the TB scaling factor, as well as the resources available for the UE to receive each instance of each TB.

[0007] In some respects, network entities may indicate one or more parameters for receiving inter-TB interleaved transmissions via broadcast or multicast. For example, in order for a UE to receive the MBS Physical Downlink Shared Channel (PDSCH), if HPID and NDI are indicated in the associated Physical Downlink Control Channel (PDCCH) (e.g., DCI) that schedules the PDSCH, the UE may apply a processing time (e.g., Tproc,1) to receive the PDSCH. The network entity may indicate to the UE that the processing time (e.g., Tproc,1) may exist between instances of a first TB and between instances of a second TB. Additionally or alternatively, the network entity may indicate a limited bandwidth for inter-TB interleaved transmission of the MBS PDSCH for some UEs (e.g., enhanced capability reduction (eRedCap) UEs).

[0008] A method for wireless communication by a network entity for wireless communication is described. The method may include: receiving one or more DCI messages for a first group of instances of a first TB; receiving one or more DCI messages for a second group of instances of a second TB; receiving, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with instances of the second group of instances of the second TB; and decoding the first TB based on the received instances of the first TB.

[0009] A network entity for wireless communication is described. The network entity for wireless communication may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity for wireless communication to: receive one or more DCI messages for a first group of instances of a first TB; receive one or more DCI messages for a second group of instances of a second TB; receive, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with instances of the second group of instances of the second TB; and decode the first TB based on the received instances of the first TB.

[0010] Another network entity for wireless communication is described. This network entity for wireless communication may include: components for: receiving one or more DCI messages of a first group of instances of a first TB; components for: receiving one or more DCI messages of a second group of instances of a second TB; components for: receiving, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with instances of the second group of instances of the second TB; and components for: decoding the first TB based on the received instances of the first TB.

[0011] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive one or more DCI messages for a first group of instances of a first TB; receive one or more DCI messages for a second group of instances of a second TB; receive, via one or more PDSCHs, instances of the first TB and the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with instances of the second group of instances of the second TB; and decode the first TB based on the received instances of the first TB.

[0012] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing a soft combination of one or more instances in the first group of instances based on a first group of one or more DCI messages including an indication that each instance in one or more instances of the first group of instances belongs to the first TB.

[0013] The methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for decoding a first TB based on the fact that the network entity belongs to a first-generation network entity that may be different from a second-generation network entity, or that the network entity is capable of conveying a corresponding instance of time-interleaved TB that may be used for multicast or broadcast services or both.

[0014] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first set of one or more DCI messages and a second set of one or more DCI messages may be configured to be decoded by at least a second network entity that may belong to a different generation from the network entity. The network entity and the second network entity may be able to decode the first set of one or more DCI messages and the second set of one or more DCI messages, and the network entity may be able to convey the corresponding instances of time interleaving that may be available for multicast services or broadcast services or both.

[0015] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in a first group schedules a corresponding instance in a first group of instances in a first TB, and each DCI message in one or more DCI messages in a second group schedules a corresponding instance in a second group of instances in a second TB.

[0016] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in the first group includes a corresponding field indicating that the scheduled corresponding instance in the first group of instances corresponds to the first TB, and the processing system can be configured to decode the first TB based on the corresponding field of each DCI message in one or more DCI messages in the first group.

[0017] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the corresponding field of each DCI message in one or more DCI messages in the first group indicates the corresponding HPI associated with the corresponding scheduled instance in the first group of instances, the NDI associated with the HPI, or both.

[0018] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the NDI associated with the corresponding HPD indicates whether the scheduled corresponding instance can be a first-time transmission corresponding to the first TB.

[0019] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, HPID indicates whether the scheduled corresponding instance can be a retransmission corresponding to the first TB.

[0020] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in the first group of one or more DCI messages may have DCI format 4_0.

[0021] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_1, and at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_2.

[0022] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving information indicating a time window, wherein decoding of the first TB may be based on a first set of instances within the time window.

[0023] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving first information indicating the number of a first group of instances in a first TB and second information indicating the time delay between the instances in the first group of instances in the first TB, wherein decoding of the first TB may be based on the number and the time delay, and wherein the first group of one or more DCI messages may be a single DCI message for scheduling the first group of instances in the first TB.

[0024] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving RRC information corresponding to a group radio network temporary identifier associated with a network entity, wherein the RRC information includes first information and second information.

[0025] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a time-domain resource allocation index that indicates the first and second information.

[0026] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving RRC information that includes first information, wherein the single DCI message includes a time-domain resource allocation index that can indicate second information.

[0027] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving RRC information that includes second information, wherein the single DCI message includes a time-domain resource allocation index that can indicate the first information.

[0028] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a field with more than 2 bits indicating the RV index associated with an instance in the first set of instances of the first TB.

[0029] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving information indicating an RV index pattern for a first set of instances of a first TB, and decoding only a portion of each DCI message in one or more DCI messages of the first set, wherein the portion excludes the corresponding RV field of each corresponding DCI message based on receiving the information, and wherein decoding of the first TB may be based on the RV index pattern.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the RV index pattern indicates that the corresponding RV index associated with a first time instance in the first set of instances of the first TB may be zero.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in a first group of one or more DCI messages includes an RV field indicating an RV index associated with a first time instance in a first group of instances of a first TB, the indicated RV index corresponding to an RV index pattern in a group of multiple RV index patterns, and the RV index pattern beginning with the indicated RV index.

[0032] A method for wireless communication by a network entity for wireless communication is described. The method may include: transmitting one or more DCI messages for a first group of instances of a first TB; transmitting one or more DCI messages for a second group of instances of a second TB; and transmitting, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances in the first TB is interleaved with instances of the second group of instances in the second TB.

[0033] A network entity for wireless communication is described. The network entity for wireless communication may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity for wireless communication to: transmit one or more DCI messages for a first group of instances of a first TB; transmit one or more DCI messages for a second group of instances of a second TB; and transmit, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances in the first TB is interleaved with instances of the second group of instances in the second TB.

[0034] Another network entity for wireless communication is described. This network entity for wireless communication may include: components for transmitting one or more DCI messages for co-scheduling a first group of instances of a first TB; components for transmitting one or more DCI messages for co-scheduling a second group of instances of a second TB; and components for transmitting, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services, based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is interleaved with instances of the second group of instances of the second TB.

[0035] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit one or more DCI messages for a first group of instances of a first TB; transmit one or more DCI messages for a second group of instances of a second TB; and transmit, via one or more PDSCHs, the first group of instances of the first TB and the second group of instances of the second TB for multicast or broadcast services, based on the first group of one or more DCI messages and the second group of one or more DCI messages, wherein at least one instance of the first group of instances of the first TB is interleaved with the second group of instances of the second TB.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in a first group schedules a corresponding instance in a first group of instances in a first TB, and each DCI message in one or more DCI messages in a second group schedules a corresponding instance in a second group of instances in a second TB.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in the first group includes a field indicating that the scheduled corresponding instance in the first group of instances corresponds to a corresponding first TB.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the corresponding field of each DCI message in one or more DCI messages in the first group indicates the corresponding HPI associated with the corresponding scheduled instance in the first group of instances, the NDI associated with the HPI, or both.

[0039] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the NDI associated with the corresponding HPD indicates whether the scheduled corresponding instance can be the first-time transmission corresponding to the first transport block.

[0040] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, HPID indicates whether the scheduled corresponding instance can be a retransmission corresponding to the first TB.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in the first group of one or more DCI messages may have DCI format 4_0.

[0042] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_1, and at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_2.

[0043] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending information indicating a time window associated with the first set of instances and decoding the first TB.

[0044] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first set of one or more DCI messages and a second set of one or more DCI messages may be configured to be decoded by at least a second network entity that may belong to a different generation than at least a third network entity. The second and third network entities may be able to decode the first set of one or more DCI messages and the second set of one or more DCI messages, and the third network entity may be able to convey the corresponding instances of time interleaving that may be used for multicast services or broadcast services or both.

[0045] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending first information indicating the number of first group instances of a first TB and second information indicating the time delay between the individual instances in the first group instances of the first TB, and wherein the first group of one or more DCI messages may be a single DCI message scheduling the first group instances of the first TB.

[0046] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting RRC information corresponding to a group radio network temporary identifier associated with a second network entity, wherein the RRC information includes first information and second information.

[0047] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a time-domain resource allocation index that indicates the first and second information.

[0048] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending RRC information that includes first information, wherein the single DCI message includes a TDRA index that can indicate second information.

[0049] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending RRC information that includes second information, wherein the single DCI message includes a time-domain resource allocation index that can indicate the first information.

[0050] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a field with more than 2 bits indicating the RV index associated with an instance in the first set of instances of the first TB.

[0051] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in the first group includes a corresponding field with more than 2 bits, which indicates the corresponding RV index associated with the corresponding instance in the first group of instances of the first TB.

[0052] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending information indicating an RV index pattern for a first set of instances of a first TB, wherein the RV index pattern may be associated with decoding the first TB.

[0053] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the RV index pattern indicates that the corresponding RV index associated with a first time instance in the first set of instances of the first TB may be zero.

[0054] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in a first group of one or more DCI messages includes an RV field indicating an RV index associated with a first time instance in a first group of instances of a first TB, the indicated RV index corresponding to an RV index pattern in a group of multiple RV index patterns, and the RV index pattern beginning with the indicated RV index.

[0055] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving information instructing a second network entity to convey the capability of a corresponding instance of time-interleaved time for a corresponding TB that can be used for multicast or broadcast services, wherein sending a first set of one or more DCI messages, sending a second set of one or more DCI messages, sending a first set of instances of a first TB, or sending a second set of instances of a second TB, or any combination thereof may be based on receiving the information.

[0056] A method for wireless communication by a network entity for wireless communication is described. The method may include: receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; receiving, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time interleaved; and decoding the first TB based on the received first set of instances of the first TB.

[0057] A network entity for wireless communication is described. The network entity for wireless communication may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity for wireless communication to: receive control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; receive, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved; and decode the first TB based on the received first set of instances of the first TB.

[0058] Another network entity for wireless communication is described. This network entity for wireless communication may include: components for: receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; components for: receiving, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved; and components for: decoding a first TB based on the received first set of instances of the first TB.

[0059] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; receive, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved; and decode the first TB based on the received first set of instances of the first TB.

[0060] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control information and decoding a first TB that may be based on the network entity belonging to a first-generation network entity that may be different from a second-generation network entity, or the network entity being able to convey a corresponding instance of time-interleaved TB that may be used for multicast services or broadcast services or both.

[0061] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more RRC messages.

[0062] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more RRC messages semi-statically configure the one or more parameters.

[0063] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more DCI messages.

[0064] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one of the one or more DCI messages is scheduled to receive resources of one or more TBs from a set of multiple TBs and activate the one or more parameters.

[0065] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages may be in a time-interleaved TB format supported by a network entity for scheduling multicast or broadcast services.

[0066] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages may be associated with one or more of the following: a group radio network temporary identifier, a control resource set, a search space set, or any combination thereof, and the association may indicate that the one or more DCI messages relate to communications of a multicast service or a broadcast service.

[0067] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages include a time-domain resource allocation index corresponding to a time-domain resource allocation table, which includes entries for the one or more parameters.

[0068] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the one or more DCI messages include dedicated fields for the one or more parameters.

[0069] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control information indicating an HPID pattern corresponding to instances of the set of multiple TBs, wherein each corresponding instance in the first set of instances of the first TB corresponds to a corresponding HPID in the HPID pattern, and each corresponding instance in the second set of instances of the second TB corresponds to a corresponding HPID in the HPID pattern, and wherein the first set of instances of the first TB and the second set of instances of the second TB may be time-interleaved based on the HPID pattern.

[0070] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for decoding a first TB based on a TB scaling factor, wherein the size of the first TB may be based on the TB scaling factor and the corresponding number of instances of a first set of instances of the first TB.

[0071] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for decoding a first TB based on a low-density parity-check (LDPC) basemap defined by the decoding rate and payload size of the first TB, wherein the payload size of the first TB may be based on a TB scaling factor applied to an unscaled TB size.

[0072] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for decoding a first TB based on a finite buffer rate matching (LBRM) size that can be defined by a TB scaling factor.

[0073] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the per-duration threshold data rate for a set of multiple durations corresponding to a first set of instances of the first TB can be based on a TB scaling factor.

[0074] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the threshold data rate per duration for component carriers used in multicast or broadcast services may be less than or equal to the second threshold data rate used in unicast signaling.

[0075] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control information indicating one or more RV index patterns, wherein an RV index in a first RV index pattern corresponds to each corresponding instance in a first set of instances, and wherein the order of the first set of instances in the first TB may be based on the first RV index pattern.

[0076] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a first RV index pattern from one or more RV index patterns based on the number of a first group of instances in a first TB satisfying a threshold number, wherein the first group of instances in the first TB and the second group of instances in the second TB may be time-interleaved based on the first RV index pattern.

[0077] A method for wireless communication by a network entity for wireless communication is described. The method may include: transmitting control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and transmitting, according to the one or more parameters, via a set of one or more PDSCHs a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0078] A network entity for wireless communication is described. The network entity for wireless communication may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity for wireless communication to: transmit control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and transmit, according to the one or more parameters, via a set of one or more PDSCHs a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0079] Another network entity for wireless communication is described. This network entity for wireless communication may include: components for transmitting control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and components for transmitting, according to the one or more parameters, a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services via a set of one or more PDSCHs, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0080] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and transmit, according to the one or more parameters, via a set of one or more PDSCHs a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0081] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending one or more RRC messages.

[0082] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more RRC messages semi-statically configure the one or more parameters.

[0083] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending one or more DCI messages.

[0084] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one of the one or more DCI messages is scheduled to receive resources of one or more TBs from a set of multiple TBs and activate the one or more parameters.

[0085] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information includes one or more DCI messages, which may be in a time-interleaved TB format supported by a second network entity for scheduling multicast or broadcast services.

[0086] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages may be associated with one or more of the following: a group radio network temporary identifier, a control resource set, a search space set, or any combination thereof, and the association may indicate that the one or more DCI messages include the one or more parameters and are related to communication with a multicast or broadcast service.

[0087] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the one or more DCI messages include dedicated fields for the one or more parameters.

[0088] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages include a time-domain resource allocation index corresponding to a time-domain resource allocation table, which includes entries for the one or more parameters.

[0089] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending second control information indicating an HPID pattern corresponding to instances of the set of multiple TBs, wherein each corresponding instance in the first set of instances of the first TB corresponds to a corresponding HPID in the HPID pattern, and each corresponding instance in the second set of instances of the second TB corresponds to a corresponding HPID in the HPID pattern, and wherein the first set of instances of the first TB and the second set of instances of the second TB may be time-interleaved based on the HPID pattern.

[0090] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the size of the first TB may be based on a TB scaling factor and the corresponding number of instances of the first set of instances of the first TB.

[0091] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the per-duration threshold data rate for a set of multiple durations corresponding to a first set of instances of the first TB can be based on a TB scaling factor.

[0092] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending second control information indicating one or more RV index patterns, wherein an RV index in a first RV index pattern corresponds to each corresponding instance in a first set of instances, and wherein the order of the first set of instances in the first TB may be based on the first RV index pattern.

[0093] A method for wireless communication by a network entity for wireless communication is described. The method may include: receiving control information scheduling one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving mode, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; receiving, via a first set of one or more PDSCHs and based on the time-interleaving mode, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs for multicast or broadcast services, according to the time gaps, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure; and decoding at least the first TB based on the received first set of instances of the first TB.

[0094] A network entity for wireless communication is described. This network entity for wireless communication may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code to enable a network entity for wireless communication to: receive control information scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving mode, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; receive, via a first set of one or more PDSCHs and based on the time-interleaving mode, according to the time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein the processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses the first HARQ procedure or the second HARQ procedure; and decode at least the first TB based on the first set of instances received from the first TB.

[0095] Another network entity for wireless communication is described. The network entity for wireless communication may include: components for: receiving control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving mode, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; components for: receiving, via a first set of one or more PDSCHs and based on a time-interleaving mode, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs for multicast or broadcast services, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information for scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses the first HARQ procedure or the second HARQ procedure; and components for: decoding at least a first TB based on the first set of instances of the first TB received.

[0096] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive control information scheduling one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; receive, via a first set of one or more PDSCHs and based on the time-interleaving pattern, according to the time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure; and decode at least the first TB based on the received first set of instances of the first TB.

[0097] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information may be configured to be decoded by at least a second network entity that may belong to a different generation from the network entity. This second network entity may be able to decode the control information and may be able to convey a corresponding instance of time-interleaved time that may be available for multicast service or broadcast service or both.

[0098] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring a first set of instances of a first TB and a second set of instances of a second TB via bandwidth that satisfies a threshold bandwidth for multicast or broadcast.

[0099] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending registration information that instructs a network entity to receive one or more corresponding instances of a set of multiple corresponding TBs via a threshold bandwidth, wherein, in order to monitor a first set of instances of a first TB, the processing system may be configured to monitor the first set of instances of the first TB based on the sending of the registration information.

[0100] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the threshold bandwidth may be a reduced bandwidth; this reduced bandwidth includes fewer frequency resources compared to the second bandwidth used to receive the fourth set of instances of the fourth TB; and the fourth set of instances may be a single instance, may not be time-interleaved with the fifth TB of instances, or may be associated with a single PDSCH, or any combination thereof.

[0101] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the threshold bandwidth can be 5 MHz bandwidth.

[0102] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information includes one or more DCI messages that schedule a first group of instances of a first TB, the one or more DCI messages including an identifier that indicates the first group of instances corresponds to the first TB, and receiving the first group of instances of the first TB in the set of multiple corresponding TBs for multicast or broadcast services according to time slots may be based on the identifier that indicates the first group of instances corresponds to the first TB.

[0103] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing soft combination on one or more instances in the first group of instances based on control information, including an indication that each instance in one or more instances of the first group of instances belongs to the first TB.

[0104] A method for wireless communication by a network entity for wireless communication is described. The method may include: sending control information to schedule one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; and sending, via a first set of one or more PDSCHs and based on the time-interleaving pattern, according to the time gaps, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs for multicast or broadcast services, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information to schedule the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0105] A network entity for wireless communication is described. This network entity for wireless communication may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code to enable a network entity for wireless communication to: send control information scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving mode, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; and send, via a first set of one or more PDSCHs and based on a time-interleaving mode, according to time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein the processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0106] Another network entity for wireless communication is described. This network entity for wireless communication may include: components for: transmitting control information scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving mode, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; and components for: transmitting, via a first set of one or more PDSCHs and based on a time-interleaving mode, according to time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0107] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: send control information scheduling one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; and send, via a first set of one or more PDSCHs and based on the time-interleaving pattern, according to time gaps, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs for multicast or broadcast services, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0108] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information may be configured to be decoded by at least a second network entity that may belong to a different generation than the third network entity. The second and third network entities may be able to decode the control information, and the third network entity may be able to convey a corresponding instance of time-interleaved time that may be used for multicast or broadcast services or both.

[0109] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first set of instances of the first TB and a second set of instances of the second TB may be transmitted via at least one PDSCH through bandwidth that satisfies a threshold bandwidth for multicast or broadcast services.

[0110] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving registration information that instructs a second network entity to receive one or more corresponding instances of a set of multiple corresponding TBs via a threshold bandwidth, wherein a first set of instances of the first TB may be sent based on the registration information.

[0111] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the threshold bandwidth may be a reduced bandwidth; this reduced bandwidth includes fewer frequency resources compared to the second bandwidth used to receive the fourth set of instances of the fourth TB; and the fourth set of instances may be a single instance, may not be time-interleaved with the fifth TB of instances, or may be associated with a single PDSCH, or any combination thereof.

[0112] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the threshold bandwidth can be 5 MHz bandwidth.

[0113] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information includes one or more DCI messages that schedule a first group of instances of a first TB, the one or more DCI messages including an identifier that indicates that the first group of instances corresponds to a first TB, and the first group of instances of the first TB in the set of multiple corresponding TBs may be sent based on the identifier according to a time slot for multicast service or broadcast service.

[0114] A method for wireless communication by a network entity is described. The method may include: receiving one or more DCI messages for a first group of instances of a first TB; receiving one or more DCI messages for a second group of instances of a second TB; receiving, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances in the first TB is time-interleaved with instances of the second group of instances in the second TB; and decoding the first TB based on the received instances of the first TB.

[0115] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity to: receive one or more DCI messages for a first group of instances of a first TB that are co-scheduled; receive one or more DCI messages for a second group of instances of a second TB that are co-scheduled; receive, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with instances of the second group of instances of the second TB; and decode the first TB based on the received instances of the first TB.

[0116] Another network entity for wireless communication is described. This network entity may include: components for: receiving one or more DCI messages of a first group of instances of a first TB; components for: receiving one or more DCI messages of a second group of instances of a second TB; components for: receiving, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with instances of the second group of instances of the second TB; and components for: decoding the first TB based on the received instances of the first TB.

[0117] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive one or more DCI messages for a first group of instances of a first TB; receive one or more DCI messages for a second group of instances of a second TB; receive, via one or more PDSCHs, instances of the first TB and the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with instances of the second group of instances of the second TB; and decode the first TB based on the received instances of the first TB.

[0118] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, decoding the first TB may include operations, features, components, or instructions for performing a soft combination of one or more instances in the first set of instances, based on a first set of one or more DCI messages including an indication that each instance in one or more instances of the first set of instances belongs to the first TB.

[0119] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, decoding a first TB may include operations, features, components, or instructions for: decoding a first TB based on the fact that the network entity belongs to a first-generation network entity that may be different from a second-generation network entity, or that the network entity is capable of conveying a corresponding instance of a time-interleaved TB that may be used for multicast or broadcast services or both.

[0120] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first set of one or more DCI messages and a second set of one or more DCI messages may be configured to be decoded by at least a second network entity that may belong to a different generation from the network entity. The network entity and the second network entity may be able to decode the first set of one or more DCI messages and the second set of one or more DCI messages, and the network entity may be able to convey the corresponding instances of time interleaving that may be available for multicast services or broadcast services or both.

[0121] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in a first group schedules a corresponding instance in a first group of instances in a first TB, and each DCI message in one or more DCI messages in a second group schedules a corresponding instance in a second group of instances in a second TB.

[0122] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in the first group includes a corresponding field indicating that the scheduled corresponding instance in the first group of instances corresponds to a first TB, and decoding the first TB may be based on the corresponding field of each DCI message in one or more DCI messages in the first group.

[0123] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the corresponding field of each DCI message in one or more DCI messages in the first group indicates the corresponding HPI associated with the corresponding scheduled instance in the first group of instances, the NDI associated with the HPI, or both.

[0124] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the NDI associated with the corresponding HPD indicates whether the scheduled corresponding instance can be a first-time transmission corresponding to the first TB.

[0125] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, HPID indicates whether the scheduled corresponding instance can be a retransmission corresponding to the first TB.

[0126] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in the first group of one or more DCI messages may have DCI format 4_0.

[0127] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_1, and at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_2.

[0128] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving information indicating a time window, wherein decoding of the first TB may be based on a first set of instances within the time window.

[0129] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving first information indicating the number of a first group of instances in a first TB and second information indicating the time delay between the instances in the first group of instances in the first TB, wherein decoding of the first TB may be based on the number and the time delay, and wherein the first group of one or more DCI messages may be a single DCI message for scheduling the first group of instances in the first TB.

[0130] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving RRC information corresponding to a group radio network temporary identifier associated with a network entity, wherein the RRC information includes first information and second information.

[0131] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a time-domain resource allocation index that indicates the first and second information.

[0132] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving RRC information that includes first information, wherein the single DCI message includes a time-domain resource allocation index that can indicate second information.

[0133] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving RRC information that includes second information, wherein the single DCI message includes a time-domain resource allocation index that can indicate the first information.

[0134] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a field with more than 2 bits indicating the RV index associated with an instance in the first set of instances of the first TB.

[0135] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving information indicating an RV index pattern for a first set of instances of a first TB, and decoding only a portion of each DCI message in one or more DCI messages of the first set, wherein the portion excludes the corresponding RV field of each corresponding DCI message based on receiving the information, and wherein decoding of the first TB may be based on the RV index pattern.

[0136] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the RV index pattern indicates that the corresponding RV index associated with a first time instance in the first set of instances of the first TB may be zero.

[0137] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in a first group of one or more DCI messages includes an RV field indicating an RV index associated with a first time instance in a first group of instances of a first TB, the indicated RV index corresponding to an RV index pattern in a group of multiple RV index patterns, and the RV index pattern beginning with the indicated RV index.

[0138] A method for wireless communication by a network entity is described. The method may include: transmitting one or more DCI messages for a first group of instances of a first TB; transmitting one or more DCI messages for a second group of instances of a second TB; and transmitting, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances in the first TB is interleaved with instances of the second group of instances in the second TB.

[0139] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity to: transmit one or more DCI messages for a first group of instances of a first TB; transmit one or more DCI messages for a second group of instances of a second TB; and transmit, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services, based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances in the first TB is interleaved with instances of the second group of instances in the second TB.

[0140] Another network entity for wireless communication is described. This network entity may include: components for transmitting one or more DCI messages for co-scheduling a first group of instances of a first TB; components for transmitting one or more DCI messages for co-scheduling a second group of instances of a second TB; and components for transmitting, via one or more PDSCHs, instances of the first TB and instances of the second TB for multicast or broadcast services, based on the first or more DCI messages and the second or more DCI messages, wherein at least one instance of the first group of instances of the first TB is interleaved with instances of the second group of instances of the second TB.

[0141] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit one or more DCI messages for a first group of instances of a first TB; transmit one or more DCI messages for a second group of instances of a second TB; and transmit, via one or more PDSCHs, the first group of instances of the first TB and the second group of instances of the second TB for multicast or broadcast services, based on the first group of one or more DCI messages and the second group of one or more DCI messages, wherein at least one instance of the first group of instances of the first TB is interleaved with the second group of instances of the second TB.

[0142] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in a first group schedules a corresponding instance in a first group of instances in a first TB, and each DCI message in one or more DCI messages in a second group schedules a corresponding instance in a second group of instances in a second TB.

[0143] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in the first group includes a field indicating that the scheduled corresponding instance in the first group of instances corresponds to a corresponding first TB.

[0144] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the corresponding field of each DCI message in one or more DCI messages in the first group indicates the corresponding HPI associated with the corresponding scheduled instance in the first group of instances, the NDI associated with the HPI, or both.

[0145] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the NDI associated with the corresponding HPD indicates whether the scheduled corresponding instance can be the first-time transmission corresponding to the first transport block.

[0146] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, HPID indicates whether the scheduled corresponding instance can be a retransmission corresponding to the first TB.

[0147] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in the first group of one or more DCI messages may have DCI format 4_0.

[0148] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_1, and at least one DCI message in one or more of the first group of DCI messages may be used for broadcast services and may have DCI format 4_2.

[0149] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending information indicating a time window associated with the first set of instances and decoding the first TB.

[0150] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first set of one or more DCI messages and a second set of one or more DCI messages may be configured to be decoded by at least a second network entity that may belong to a different generation than at least a third network entity. The second and third network entities may be able to decode the first set of one or more DCI messages and the second set of one or more DCI messages, and the third network entity may be able to convey the corresponding instances of time interleaving that may be used for multicast services or broadcast services or both.

[0151] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending first information indicating the number of first group instances of a first TB and second information indicating the time delay between the individual instances in the first group instances of the first TB, and wherein the first group of one or more DCI messages may be a single DCI message scheduling the first group instances of the first TB.

[0152] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting RRC information corresponding to a group radio network temporary identifier associated with a second network entity, wherein the RRC information includes first information and second information.

[0153] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a time-domain resource allocation index that indicates the first and second information.

[0154] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending RRC information that includes first information, wherein the single DCI message includes a TDRA index that can indicate second information.

[0155] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending RRC information that includes second information, wherein the single DCI message includes a time-domain resource allocation index that can indicate the first information.

[0156] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the single DCI message includes a field with more than 2 bits indicating the RV index associated with an instance in the first set of instances of the first TB.

[0157] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, each DCI message in one or more DCI messages in the first group includes a corresponding field with more than 2 bits, which indicates the corresponding RV index associated with the corresponding instance in the first group of instances of the first TB.

[0158] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending information indicating an RV index pattern for a first set of instances of a first TB, wherein the RV index pattern may be associated with decoding the first TB.

[0159] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the RV index pattern indicates that the corresponding RV index associated with a first time instance in the first set of instances of the first TB may be zero.

[0160] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one DCI message in a first group of one or more DCI messages includes an RV field indicating an RV index associated with a first time instance in a first group of instances of a first TB, the indicated RV index corresponding to an RV index pattern in a group of multiple RV index patterns, and the RV index pattern beginning with the indicated RV index.

[0161] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving information instructing a second network entity to convey the capability of a corresponding instance of time-interleaved time for a corresponding TB that can be used for multicast or broadcast services, wherein sending a first set of one or more DCI messages, sending a second set of one or more DCI messages, sending a first set of instances of a first TB, or sending a second set of instances of a second TB, or any combination thereof may be based on receiving the information.

[0162] A method for wireless communication by a network entity is described. The method may include: receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; receiving, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved; and decoding the first TB based on the received first set of instances of the first TB.

[0163] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity to: receive control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; receive, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved; and decode the first TB based on the received first set of instances of the first TB.

[0164] Another network entity for wireless communication is described. This network entity may include: components for: receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; components for: receiving, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved; and components for: decoding a first TB based on the received first set of instances of the first TB.

[0165] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; receive, according to the one or more parameters, via a set of one or more PDSCHs, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved; and decode the first TB based on the received first set of instances of the first TB.

[0166] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control information and decoding a first TB that may be based on the network entity belonging to a first-generation network entity that may be different from a second-generation network entity, or the network entity being able to convey a corresponding instance of time-interleaved TB that may be used for multicast services or broadcast services or both.

[0167] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving control information may include operations, features, components, or instructions for receiving one or more RRC messages.

[0168] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more RRC messages semi-statically configure the one or more parameters.

[0169] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving control information may include operations, features, components, or instructions for receiving one or more DCI messages.

[0170] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one of the one or more DCI messages is scheduled to receive resources of one or more TBs from a set of multiple TBs and activate the one or more parameters.

[0171] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages may be in a time-interleaved TB format supported by a network entity for scheduling multicast or broadcast services.

[0172] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages may be associated with one or more of the following: a group radio network temporary identifier, a control resource set, a search space set, or any combination thereof, and the association may indicate that the one or more DCI messages relate to communications of a multicast service or a broadcast service.

[0173] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages include a time-domain resource allocation index corresponding to a time-domain resource allocation table, which includes entries for the one or more parameters.

[0174] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the one or more DCI messages include dedicated fields for the one or more parameters.

[0175] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control information indicating an HPID pattern corresponding to instances of the set of multiple TBs, wherein each corresponding instance in the first set of instances of the first TB corresponds to a corresponding HPID in the HPID pattern, and each corresponding instance in the second set of instances of the second TB corresponds to a corresponding HPID in the HPID pattern, and wherein the first set of instances of the first TB and the second set of instances of the second TB may be time-interleaved based on the HPID pattern.

[0176] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, decoding a first TB may include operations, features, components, or instructions for decoding the first TB based on a TB scaling factor, wherein the size of the first TB may be based on the TB scaling factor and the corresponding number of instances of a first set of instances of the first TB.

[0177] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, decoding a first TB may include operations, features, components, or instructions for decoding the first TB based on a low-density parity-check (LDPC) basemap defined by the decoding rate and payload size of the first TB, wherein the payload size of the first TB may be based on a TB scaling factor applied to an unscaled TB size.

[0178] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, decoding the first TB may include operations, features, components, or instructions for decoding the first TB based on a finite buffer rate matching (LBRM) size that can be defined by a TB scaling factor.

[0179] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the per-duration threshold data rate for a set of multiple durations corresponding to a first set of instances of the first TB can be based on a TB scaling factor.

[0180] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the threshold data rate per duration for component carriers used in multicast or broadcast services may be less than or equal to the second threshold data rate used in unicast signaling.

[0181] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control information indicating one or more RV index patterns, wherein an RV index in a first RV index pattern corresponds to each corresponding instance in a first set of instances, and wherein the order of the first set of instances in the first TB may be based on the first RV index pattern.

[0182] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a first RV index pattern from one or more RV index patterns based on the number of a first group of instances in a first TB satisfying a threshold number, wherein the first group of instances in the first TB and the second group of instances in the second TB may be time-interleaved based on the first RV index pattern.

[0183] A method for wireless communication by a network entity is described. The method may include: transmitting control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving pattern corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and transmitting, according to the one or more parameters, via a set of one or more PDSCHs a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0184] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, causing the network entity to: transmit control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving pattern corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and transmit, according to the one or more parameters, via a set of one or more PDSCHs a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0185] Another network entity for wireless communication is described. This network entity may include: components for transmitting control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and components for transmitting, according to the one or more parameters, a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services via a set of one or more PDSCHs, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0186] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, a time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof; and transmit, according to the one or more parameters, via a set of one or more PDSCHs a first set of instances of a first TB and a second set of instances of a second TB for multicast or broadcast services, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved.

[0187] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending control information may include operations, features, components, or instructions for sending one or more RRC messages.

[0188] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more RRC messages semi-statically configure the one or more parameters.

[0189] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, sending control information may include operations, features, components, or instructions for sending one or more DCI messages.

[0190] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one of the one or more DCI messages is scheduled to receive resources of one or more TBs from a set of multiple TBs and activate the one or more parameters.

[0191] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information includes one or more DCI messages, which may be in a time-interleaved TB format supported by a second network entity for scheduling multicast or broadcast services.

[0192] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages may be associated with one or more of the following: a group radio network temporary identifier, a control resource set, a search space set, or any combination thereof, and the association may indicate that the one or more DCI messages include the one or more parameters and are related to communication with a multicast or broadcast service.

[0193] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the one or more DCI messages include dedicated fields for the one or more parameters.

[0194] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more DCI messages include a time-domain resource allocation index corresponding to a time-domain resource allocation table, which includes entries for the one or more parameters.

[0195] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending second control information indicating an HPID pattern corresponding to instances of the set of multiple TBs, wherein each corresponding instance in the first set of instances of the first TB corresponds to a corresponding HPID in the HPID pattern, and each corresponding instance in the second set of instances of the second TB corresponds to a corresponding HPID in the HPID pattern, and wherein the first set of instances of the first TB and the second set of instances of the second TB may be time-interleaved based on the HPID pattern.

[0196] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the size of the first TB may be based on a TB scaling factor and the corresponding number of instances of the first set of instances of the first TB.

[0197] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the per-duration threshold data rate for a set of multiple durations corresponding to a first set of instances of the first TB can be based on a TB scaling factor.

[0198] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: sending second control information indicating one or more RV index patterns, wherein an RV index in a first RV index pattern corresponds to each corresponding instance in a first set of instances, and wherein the order of the first set of instances in the first TB may be based on the first RV index pattern.

[0199] A method for wireless communication by a network entity is described. The method may include: receiving control information scheduling one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; receiving, via a first set of one or more PDSCHs and based on the time-interleaving pattern, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs for multicast or broadcast services, according to the time gaps, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure; and decoding at least the first TB based on the received first set of instances of the first TB.

[0200] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code to enable the network entity to: receive control information scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; receive, via a first set of one or more PDSCHs and based on the time-interleaving pattern, according to the time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein the processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses the first HARQ procedure or the second HARQ procedure; and decode at least the first TB based on the first set of instances received from the first TB.

[0201] Another network entity for wireless communication is described. The network entity may include: components for: receiving control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving mode, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; components for: receiving, via a first set of one or more PDSCHs and based on a time-interleaving mode, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs for multicast or broadcast services, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein the processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information for scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses the first HARQ procedure or the second HARQ procedure; and components for: decoding at least a first TB based on the first set of instances received from the first TB.

[0202] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive control information scheduling one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; receive, via a first set of one or more PDSCHs and based on the time-interleaving pattern, according to the time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure; and decode at least the first TB based on the received first set of instances of the first TB.

[0203] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information may be configured to be decoded by at least a second network entity that may belong to a different generation from the network entity. This second network entity may be able to decode the control information and may be able to convey a corresponding instance of time-interleaved time that may be available for multicast service or broadcast service or both.

[0204] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring a first set of instances of a first TB and a second set of instances of a second TB via bandwidth that satisfies a threshold bandwidth for multicast or broadcast.

[0205] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending registration information that instructs a network entity to receive one or more corresponding instances of a set of multiple corresponding TBs via a threshold bandwidth, wherein, in order to monitor a first set of instances of a first TB, the processing system may be configured to monitor the first set of instances of the first TB based on the sending of the registration information.

[0206] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the threshold bandwidth may be a reduced bandwidth; this reduced bandwidth includes fewer frequency resources compared to the second bandwidth used to receive the fourth set of instances of the fourth TB; and the fourth set of instances may be a single instance, may not be time-interleaved with the fifth TB of instances, or may be associated with a single PDSCH, or any combination thereof.

[0207] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the threshold bandwidth can be 5 MHz bandwidth.

[0208] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information includes one or more DCI messages that schedule a first group of instances of a first TB, the one or more DCI messages including an identifier that indicates the first group of instances corresponds to the first TB, and receiving the first group of instances of the first TB in the set of multiple corresponding TBs for multicast or broadcast services according to time slots may be based on the identifier that indicates the first group of instances corresponds to the first TB.

[0209] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, decoding the first TB may include operations, features, components, or instructions for performing soft combination on the one or more instances in the first set of instances based on control information including an indication that each instance in one or more instances of the first set of instances belongs to the first TB.

[0210] A method for wireless communication by a network entity is described. The method may include: sending control information to schedule one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; and sending, via a first set of one or more PDSCHs and based on the time-interleaving pattern, according to the time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information to schedule the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0211] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute the code to enable the network entity to: send control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; and send, via a first set of one or more PDSCHs and based on a time-interleaving pattern, according to time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and each instance of the second set of instances, wherein the processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information for scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0212] Another network entity for wireless communication is described. This network entity may include: components for: transmitting control information scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving mode, and time gaps exist between each instance of the one or more corresponding instances of the set of multiple corresponding TBs; and components for: transmitting, via a first set of one or more PDSCHs and based on a time-interleaving mode, according to time gaps for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB of the set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0213] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: send control information scheduling one or more corresponding instances of a plurality of corresponding TBs, wherein the one or more corresponding instances of the plurality of corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each instance of the one or more corresponding instances of the plurality of corresponding TBs; and send, via a first set of one or more PDSCHs and based on the time-interleaving pattern, according to time gaps, a first set of instances of a first TB and a second set of instances of a second TB of the plurality of corresponding TBs for multicast or broadcast services, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time gaps existing between each instance of the first set of instances and between each instance of the second set of instances, wherein a processing time gap between the termination of the first set of one or more PDSCHs and the receipt of second control information scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure.

[0214] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information may be configured to be decoded by at least a second network entity that may belong to a different generation than the third network entity. The second and third network entities may be able to decode the control information, and the third network entity may be able to convey a corresponding instance of time-interleaved time that may be used for multicast or broadcast services or both.

[0215] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first set of instances of the first TB and a second set of instances of the second TB may be transmitted via at least one PDSCH through bandwidth that satisfies a threshold bandwidth for multicast or broadcast services.

[0216] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving registration information that instructs a second network entity to receive one or more corresponding instances of a set of multiple corresponding TBs via a threshold bandwidth, wherein a first set of instances of the first TB may be sent based on the registration information.

[0217] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the threshold bandwidth may be a reduced bandwidth; this reduced bandwidth includes fewer frequency resources compared to the second bandwidth used to receive the fourth set of instances of the fourth TB; and the fourth set of instances may be a single instance, may not be time-interleaved with the fifth TB of instances, or may be associated with a single PDSCH, or any combination thereof.

[0218] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the threshold bandwidth can be 5 MHz bandwidth.

[0219] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, control information includes one or more DCI messages that schedule a first group of instances of a first TB, the one or more DCI messages including an identifier that indicates that the first group of instances corresponds to a first TB, and the first group of instances of the first TB in the set of multiple corresponding TBs may be sent based on the identifier according to a time slot for multicast service or broadcast service. Attached Figure Description

[0220] Figure 1 An example of a wireless communication system supporting time interleaving between transport blocks (TBs) is shown according to one or more aspects of this disclosure.

[0221] Figure 2 Examples of inter-TB time interleaving diagrams supporting one or more aspects of this disclosure are shown.

[0222] Figure 3 and Figure 4 An example of a resource allocation diagram supporting time-interleaved TBs is shown, according to one or more aspects of this disclosure.

[0223] Figure 5 and Figure 6 An example of a process flow supporting time interleaving between TBs is shown according to one or more aspects of this disclosure.

[0224] Figure 7 and Figure 8 A block diagram of a device supporting inter-TB time interleaving is shown according to one or more aspects of this disclosure.

[0225] Figure 9 A block diagram of a communication manager supporting time-interleaved TBs according to one or more aspects of this disclosure is shown.

[0226] Figure 10 A diagram of a system including a device supporting inter-TB time interleaving, according to one or more aspects of this disclosure, is shown.

[0227] Figure 11 and Figure 12 A block diagram of a device supporting inter-TB time interleaving is shown according to one or more aspects of this disclosure.

[0228] Figure 13 A block diagram of a communication manager supporting time-interleaved TBs according to one or more aspects of this disclosure is shown.

[0229] Figure 14 A diagram of a system including a device supporting inter-TB time interleaving, according to one or more aspects of this disclosure, is shown.

[0230] Figures 15 to 20 A flowchart illustrating a method for supporting time interleaving between TBs according to one or more aspects of this disclosure is shown. Detailed Implementation

[0231] In some wireless communication systems, network entities may transmit signaling via multicast and broadcast services (MBS), where the signaling may include multiple transport blocks (TBs). In some cases, network entities may use a single downlink control information (DCI) message (e.g., which may be referred to herein as DCI) to schedule the successive transmission (e.g., broadcast, multicast) of multiple instances of a TB (e.g., redundant versions (RVs), duplicates), where each instance may be associated with a different RV of the TB, and thus with a different set of coded bits of the TB's data. Alternatively, network entities may schedule the transmission (e.g., broadcast, multicast) of multiple instances of a TB, where each instance of a TB corresponds to a scheduling DCI (e.g., scheduled by a scheduling DCI). In either case, the instances of each TB may not be time-interleaved, and the user equipment (UE) receiving the TB may not be able to determine whether the received TB is a new TB or another instance of a previously received TB (e.g., a duplicate or an RV). Soft combining (e.g., combining received instances of a single TB to increase the probability of successfully receiving the complete TB) can increase the reliability of wireless signaling and reduce system latency. However, based on the lack of indication to the receiving UE that various instances belong to the same TB, the UE may not be able to perform soft combination for different instances of the received TB.

[0232] Some scheduling DCIs used for multicast or broadcast services may not include any indication of whether a TB is a new TB or an instance of a previously sent TB. For example, a DCI sent by a network entity for scheduling a set of TBs may not include a Hybrid Automatic Repeat Request (HARQ) Procedure Identifier (HPID) or New Data Indicator (NDI) associated with an instance of a TB. Additionally, one or more UEs of certain generations or with certain capabilities (e.g., legacy UEs, first-generation UEs) may not be able to receive HPIDs or NDIs via broadcast or multicast DCIs. Therefore, a method is desired that allows network entity UEs (e.g., advanced UEs, UEs capable of performing the techniques described herein, second-generation UEs) to perform soft combination on different instances of TBs without affecting one or more UEs that cannot perform soft combination.

[0233] According to the techniques described herein, a network entity may send a DCI to a UE, wherein the DCI may schedule multiple instances of one or more TBs (e.g., multicast TB, broadcast TB), and wherein the multiple instances of the one or more TBs may be interleaved (e.g., time-interleaved). For example, a network entity may send a first set of DCIs scheduling a first group of instances of a first TB and a second set of DCIs scheduling a second group of instances of a second TB, wherein at least one instance in the first group of instances may be interleaved with an instance in the second group.

[0234] In some cases, the first set of DCIs and the second set of DCIs may each include a DCI for each instance in the first set of instances and the second set of instances, respectively (e.g., the ratio of DCIs to instances is one-to-one). For example, the first DCI message may schedule the first transmission of a TB, the second DCI may schedule the first repetition of a TB, and so on. In some examples, the DCI may have a first DCI format (e.g., DCI format 4_0), and the network entity may additionally include a TB indicator (e.g., NDI, HPI, or both) in the fields of each DCI in the DCI, thereby allowing the receiving UE to determine that various instances of a TB belong to the same TB (e.g., if various instances of a TB are using the same HPI, the same NDI, or both). The UE can then decode the TB by soft combining the received instances of the TB. Additionally or alternatively, the DCI may be a second format DCI (e.g., format 4_1, format 4_2, new DCI format), which may include fields for the TB indicator (e.g., such as HPI, NDI, or both). Additionally or alternatively, the network entity may indicate a duration to the UE, whereby the UE may determine that two instances of a TB belong to the same TB based on whether multiple TBs are received within that duration.

[0235] Additionally or alternatively, a network entity may use a single DCI to schedule multiple instances of a single TB (e.g., multiple RVs or multiple repetitions of a TB) (e.g., a one-to-many ratio of DCI to instances of a TB). Thus, multiple DCIs can schedule multiple interleaved instances of various TBs. The network entity may also indicate to the UE the number of instances in each group and the time delay between instances within each group. For example, the network entity may use Radio Resource Control (RRC) signaling, DCI signaling (e.g., a TDRA index corresponding to a Time Domain Resource Allocation (TDRA) table), or both, to indicate the number of instances of the scheduled TB and the time delay. In some cases, the network entity may send RRC signaling to the UE for different configurations (e.g., via these different configurations) of each group of Radio Network Temporary Identifiers (G-RNTIs) associated with different MBS broadcast or multicast data. Additionally or alternatively, when the index of the TDRA table indicates the time delay and the number of instances, the time delay may be based on the number of instances.

[0236] Additionally or alternatively, the network entity may send a DCI to schedule instances of both the first TB and the second TB. For example, the DCI may have a format that indicates the number of TBs, the number of instances of each TB within the TBs, the interleaving mode between TBs and the TB scaling factor, as well as the resources available for the UE to receive each instance of each TB.

[0237] In some cases, network entities may indicate one or more parameters for receiving inter-TB interleaved transmissions via broadcast or multicast. For example, to enable a UE to receive the MBS Physical Downlink Shared Channel (PDSCH), if HPID and NDI are indicated in the associated Physical Downlink Control Channel (PDCCH) (e.g., DCI) that schedules the PDSCH, the UE may apply a processing time (e.g., Tproc,1) to receive the PDSCH. The network entity may indicate to the UE that the processing time (e.g., Tproc,1) may exist between instances of a first TB and between instances of a second TB. Additionally or alternatively, the network entity may indicate a limited bandwidth for inter-TB interleaved transmission of the MBS PDSCH for some UEs (e.g., eRedCap UEs).

[0238] As described herein, network entities, UEs, or both may use at least one of a variety of exemplary techniques to implement MBS TB-to-TB time interleaving. These exemplary techniques are by no means limiting, but are merely examples of possible specific implementations of the techniques described herein.

[0239] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of time-interleaving diagrams between TBs, resource allocation diagrams, and process flows. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to time-interleaving between TBs.

[0240] Figure 1 An example of a wireless communication system 100 supporting TB-time interleaving according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some cases, one or more network entities 105 may include UEs, and one or more UEs 115 may be referred to as network entities. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

[0243] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), 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.

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

[0245] 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 (eNodeB, eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolved node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0246] 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 among two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. RU 170 may also be referred to as a radio headend, an intelligent radio headend, a remote radio headend (RRH), a remote radio unit (RRU), or a 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)).

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

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

[0249] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support inter-TB time interleaving as described herein. For example, some operations described as being performed by UE115 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).

[0250] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some 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.

[0251] The UE 115 described herein can 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, relay base stations, etc. Figure 1 As shown.

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

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

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

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

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

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

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

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

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

[0261] Depending on the technology, physical channels can be multiplexed using carriers for communication. 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 a downlink carrier. The control region (e.g., a control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions based on one or more search space (SS) sets for control information, and each SS set can include one or more control channel candidates arranged in a cascaded manner with one or more aggregation levels. The aggregation level of the control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information in a control information format having a given payload size. The SS set may include a common SS set configured to transmit control information to multiple UEs 115 and a UE-specific SS set configured to transmit control information to a specific UE 115.

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

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

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

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

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

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

[0268] Wireless communication system 100 may utilize both 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 with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

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

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

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

[0273] As described herein, a network entity (which may alternatively be referred to as an entity, node, network node, or wireless entity) can be, can be similar to, can include, or can be included in (e.g., can be a component of): a base station (e.g., any base station described herein, including a decomposed base station), a UE (e.g., any UE described herein), a RedCap device, an enhanced RedCap device, an ambient Internet of Things (IoT) device, an energy harvesting (EH) capable device, a network controller, apparatus, device, computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network entity can be a UE. As another example, a network entity can be a base station. As used herein, “network entity” can mean an entity configured to operate in a network (such as network 105). For example, “network entity” is not limited to an entity currently located in and / or currently operating in the network. Rather, a network entity can be any entity capable of communicating and / or operating within a network.

[0274] The adjectives "first," "second," "third," etc., are used to distinguish between two or more modified nouns in context, and do not imply absolute modifiers applicable only to a specific corresponding entity throughout the document. For example, a network entity may be referred to as "first network entity" in one discussion and as "second network entity" in another, and vice versa. As an example, the first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different from these examples.

[0275] Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network entities. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, a first processing entity, etc., configured to receive information; and the second network entity may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, a second processing entity, etc.

[0276] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to send information to a second network entity. In this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the first network entity is configured to provide, transmit, output, communicate, or send information to the second network entity. Similarly, in this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the second network entity is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network entity.

[0277] As shown in the figure, a network entity (e.g., network entity 105) may include a processing system 106. Similarly, a network entity (e.g., UE 115) may include a processing system 112. A processing system may include one or more components (or sub-components), such as those described herein. For example, a corresponding component among these one or more components may be, similar to, include, or be included in at least one memory, at least one communication interface, or at least one processor. For example, a processing system may include one or more components. In such an example, the one or more components may include a first component, a second component, and a third component. In this example, the first component may be coupled to the second and third components. In this example, the first component may be at least one processor, the second component may be a communication interface, and the third component may be at least one memory. A processing system is generally one or more components of a system capable of performing one or more functions (such as any function or combination of functions described herein). For example, one or more components may receive input information (e.g., any information as input, such as a signal, any digital information, or any other information), one or more components may process the input information to generate output information (e.g., any information as output, such as a signal or any other information), one or more components may perform any function as described herein or any combination thereof. As described herein, “input” and “input information” can be used interchangeably. Similarly, as described herein, “output” and “output information” can be used interchangeably. Any information generated by any component can be provided to one or more other systems or components of network entities such as those described herein. For example, a processing system may include a first component configured to receive or obtain information, a second component configured to process the information to generate output information, and / or a third component configured to provide the output information to other systems or components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., a first communication interface or a second communication interface). For example, a processing system may include at least one memory, at least one communication interface, and / or at least one processor, wherein the at least one processor may, for example, be coupled to the at least one memory and the at least one communication interface.

[0278] The processing system of the network entity described herein can interface with one or more other components of the network entity, process information received from one or more other components (such as input information), or output such information to one or more other components. For example, the processing system may include a first component configured to interface with one or more other components of the network entity to receive or obtain information, a second component configured to process the information to generate one or more outputs, and / or a third component configured to output the one or more outputs to one or more other components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or the second communication interface). For example, a chip or modem of the network entity may include the processing system. The processing system may include a first communication interface for receiving or obtaining information, and a second communication interface for outputting, transmitting, or providing information. In some examples, the first communication interface may be an interface configured to receive input information, and such information may be provided to the processing system. In some examples, the second system interface may be configured to transmit information output from the chip or modem. The second communication interface can also obtain or receive input information, and the first communication interface can also output, send, or provide information.

[0279] According to the techniques described herein, network entity 105 may send (e.g., broadcast, multicast, unicast) DCIs to UE 115, wherein the DCIs may schedule multiple instances of one or more TBs, and wherein the multiple instances of the one or more TBs may be interleaved (e.g., time-interleaved). For example, network entity 105 may send a first set of DCIs scheduling a first group of instances of a first TB and a second set of DCIs scheduling a second group of instances of a second TB, wherein at least one instance in the first group of instances may be interleaved with the instance in the second group.

[0280] In some cases, the first set of DCIs and the second set of DCIs may each include a DCI for each instance in the first set of instances and the second set of instances, respectively (e.g., the DCI-to-instance ratio is one-to-one). For example, the first DCI message may schedule the first transmission of a TB, the second DCI may schedule the first repetition of a TB, and so on. In some examples, the DCI may have a first DCI format (e.g., DCI format 4_0), and network entity 105 may additionally include a TB indicator (e.g., NDI, HPI, or both) in the fields of the DCI, thereby allowing the receiving UE 115 to determine that various instances of the TB belong to the same TB (e.g., if various instances of the TB are using the same HPI, the same NDI, or both). The UE 115 may then decode the TB by soft combining the received instances of the TB. Additionally or alternatively, the DCI may be a second format DCI (e.g., format 4_1, format 4_2, new DCI format), which may include fields for indicating the TB indicator (e.g., such as HPI, NDI, or both). Additionally or alternatively, network entity 105 may indicate a duration to UE 115, wherein UE 115 may determine whether two instances of a TB belong to the same TB based on whether multiple TBs (e.g., two instances) are received within the duration.

[0281] Additionally or alternatively, network entity 105 may use a single DCI to schedule multiple instances of a single TB (e.g., multiple RVs or multiple repetitions of the TB) (e.g., a one-to-many ratio of DCI to instances of the TB). Thus, multiple DCIs can schedule multiple interleaved instances of various TBs. Network entity 105 may also indicate to UE 115 the number of instances in each group and the time delay between instances within each group. For example, network entity 105 may use Radio Resource Control (RRC) signaling, DCI signaling (e.g., a TDRA index corresponding to a Time Domain Resource Allocation (TDRA) table), or both, to indicate the number of instances of the scheduled TB and the time delay. In some cases, network entity 105 may send RRC signaling to UE 115 with different configurations for each group of Radio Network Temporary Identifiers (G-RNTIs) associated with different MBS broadcast or multicast data (e.g., different configurations of the number of instances, time delay, or both). Additionally or alternatively, when the index of the TDRA table indicates the time delay and the number of instances, the time delay may be based on the number of instances.

[0282] Additionally or alternatively, network entity 105 may send a DCI to schedule instances of both the first TB and the second TB. For example, the DCI may have a format that indicates the number of TBs, the number of instances of each TB in the TBs, the interleaving mode between TBs and the TB scaling factor, as well as the resources available for UE 115 to receive each instance of each TB.

[0283] In some cases, network entity 105 may indicate one or more parameters for receiving inter-TB interleaved transmissions via broadcast or multicast. For example, to enable UE 115 to receive MBS PDSCH, if HPID and NDI are indicated in the associated PDCCH (e.g., DCI) that schedules the PDSCH, UE 115 may apply a processing time (e.g., Tproc,1) to receive the PDSCH. The network entity may indicate to UE 115 that the processing time (e.g., Tproc,1) may exist between instances of a first TB and between instances of a second TB. Additionally or alternatively, network entity 105 may indicate a limited bandwidth for inter-TB interleaved transmission of MBS PDSCH for some UE 115 (e.g., eRedCap UE). As described herein, network entity 105, UE 115, or both may use at least one of a variety of techniques to implement MBS TB time interleaving. These techniques are not intended to be limiting, but are merely examples of possible specific implementations of the techniques described herein.

[0284] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of time-interleaving diagrams between TBs, resource allocation diagrams, and process flows. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to time-interleaving between TBs.

[0285] Figure 2 An example of an inter-TB time interleaving diagram 200 supporting inter-TB time interleaving according to one or more aspects of this disclosure is shown. In some cases, aspects of the inter-TB time interleaving diagram 200 may be implemented. Figure 1 Various aspects or implementations thereof. For example, the inter-TB time interleaving diagram 200 may include multiple TBs (e.g., first TB 210, second TB 215, third TB 220, and fourth TB 225), which may be examples of TBs as described herein. In some aspects, network entities (e.g., network entity 105) and UEs (e.g., UE 115) may communicate according to the inter-TB time interleaving diagram 200.

[0286] Some wireless communication systems can implement time interleaving in MBS. For example, wireless communication systems can implement time interleaving because in MBS scenarios (e.g., when broadcasting a TV program), the opportunity for feedback-based retransmission may be limited (e.g., non-existent). However, wireless communication systems may not implement time interleaving of various instances of TBs (e.g., different TBs) (e.g., repetition, RV).

[0287] For example, a wireless communication system can implement MBS time interleaving of TBs without repeating each TB. The UE can receive first control signaling (e.g., DCI signaling) for a first instance of a schedulable TB, and can receive second control signaling for a second instance of a schedulable TB. However (e.g., for MBS broadcast), the first and second control signaling may have formats that do not include HPID or NDI (e.g., DCI format 4_0). Therefore, the UE may not be able to determine whether the first and second instances of a TB are new data transmissions or retransmissions of the TB, which may prevent the UE from performing soft combination of the first and second instances to decode the TB.

[0288] Additionally or alternatively, the wireless communication system may implement MBS time interleaving without interleaving instances of different TBs. For example, the UE may receive first control signaling (e.g., DCI signaling) for scheduling multiple consecutive (e.g., slot-level consecutive) instances of a first TB, wherein each consecutive instance of the first TB may be associated with a different redundant version of the first TB. In some cases, the instances of the first TB may be scheduled according to an RV index order following a predefined (e.g., pre-configured) RV index order. The UE may also receive second control signaling for scheduling one or more consecutive instances of a second TB. However, the instances of the first TB and the instances of the second TB may not be time-interleaved, such that the channel conditions for receiving the instances of the first TB and the instances of the second TB respectively can be similar across instances of each respective TB (e.g., due to the short amount of time available for channel condition changes between these instances). Therefore, decoding of instances of the first TB or the second TB may be affected due to the poor channel conditions during reception of each corresponding instance within the corresponding instances.

[0289] In some cases, the network entity may receive an indication of the number of instances in the first TB (e.g., via RRC signaling, a pdsch-AggregationFactor configured per G-RNTI, or a group-configured scheduling radio network temporary identifier (G-CS-RNTI)). Alternatively, the network entity may dynamically include the number of instances in entries in the TDRA table. Alternatively, the network entity may pre-configure the UE using the RV index order for instances in the first TB. However, because some wireless communication systems lack MBS inter-TB time interleaving, the UE in the system may experience degraded TB reception and decoding quality.

[0290] According to various aspects of this disclosure, the wireless communication system may support MBS inter-TB time interleaving (e.g., MBS multicast traffic channel (MTCH) with inter-TB time interleaving), as illustrated in Figure 200. In some cases, the wireless communication system may implement MBS inter-TB time interleaving via control signaling that schedules a single instance of a TB or multiple instances of a TB. Additionally or alternatively, the control signaling may indicate TB information (e.g., TB group duplication information) associated with each instance of a TB.

[0291] In some cases, the first group of UEs (e.g., second-generation UEs, UEs with MBS TB inter-time interleaving capability) may be able to implement MBS TB inter-time interleaving, while the second group of UEs (e.g., legacy UEs, first-generation UEs) may have limited (e.g., no) ability to implement MBS TB inter-time interleaving. For example, the first group of UEs may be able to implement MBS TB inter-time interleaving, while the second group of UEs may not be able to implement one or more aspects of MBS TB inter-time interleaving as described herein, or may not be able to perform soft combination procedures based on MBS TB inter-time interleaving as described herein.

[0292] However, some aspects of MBS inter-TB time interleaving (e.g., as described herein) may be compatible with the second group of UEs. For example, the techniques described herein may include utilizing one or more formats (e.g., DCI format) or one or more specific implementations of control information to support MBS inter-TB time interleaving, enabling the wireless communication system to implement MBS inter-TB time interleaving for the first group of UEs without affecting the second group of UEs (e.g., MBS inter-TB time interleaving may be backward compatible). Additionally, the techniques described herein may include one or more methods by which UEs in the first group of UEs distinguish control signaling used for MBS inter-TB time interleaving from other (e.g., legacy) control signaling.

[0293] In some cases, the inter-TB time interleaving diagram 200 may include one or more TB groups 205 (e.g., TB group 205-a, TB group 205-b, TB group 205-c, and TB group 205-d), wherein each TB group 205 may include one or more interleaved instances of one or more TBs. For example, TB group 205-a may include a first instance of a first TB 210 (e.g., associated with a first RV and RV index (e.g., RV0)), a first instance of a second TB 215, a first instance of a third TB 220, and a first instance of a fourth TB 225. TB group 205-b may include a second instance of a first TB 210, a second instance of a second TB 215, a second instance of a third TB 220, and a second instance of a fourth TB 225. TB groups 205-c and 205-d may follow a similar pattern to the third and fourth instances, respectively. When each TB group 205 is scheduled in this manner, instances of the corresponding (e.g., different) TBs may be time-interleaved across TB groups 205. In some cases, a TB (e.g., first TB 210, second TB 215, third TB 220, fourth TB 225) can be a multicast TB, a broadcast TB, or both. As used herein, the term "TB" can refer to a unicast TB, a multicast TB, or a broadcast TB, or any combination thereof. The techniques described herein can support such TB interleaving in MBS, as illustrated in Figure 200. Furthermore, similar techniques can be applied to frequency interleaving.

[0294] According to various aspects of this disclosure, wireless communication systems can implement one or more of a variety of techniques for MBS TB inter-time interleaving. For example, a network entity (e.g., network entity 105) can configure a UE (e.g., UE 115) using one or more techniques for implementing MBS TB inter-time interleaving. For example, a network entity can configure a UE using one or more techniques for MBS TB inter-time interleaving based on use cases (e.g., multicast and broadcast), data rates, or both. This disclosure provides a detailed description of a variety of techniques for implementing MBS TB inter-time interleaving. In some cases, network entity 105, UE 115, or both can select one or more of the described techniques (e.g., scenarios) based on various conditions or parameters (e.g., data rates, use cases, etc.).

[0295] Figure 3 An example of a resource allocation diagram 300 supporting signaling notification of time-interleaved TBs according to one or more aspects of this disclosure is shown. In some cases, aspects of the resource allocation diagram 300 may be implemented Figure 1 to Figure 2Various aspects or implementations thereof. For example, resource allocation diagram 300 may include various TBs (e.g., TB1, TB2, TB3, and TB4) and various instances of TBs (e.g., first instance 315, second instance 325), which may be examples of TBs and instances as described herein. In some cases, wireless communication systems may implement MBS TB time interleaving according to resource allocation diagram 300.

[0296] In some cases, implementing MBS inter-TB time interleaving may include scheduling a single instance of a TB (e.g., duplicate, redundant version) via a single DCI, where instances of different TBs may be interleaved. For example, a UE (e.g., UE 115, network entity) may receive one or more first DCIs 310 (e.g., including first DCI 310-a and first DCI 310-b) from a network entity (e.g., network entity 105), each first DCI scheduling a first instance 315 (e.g., including first instance 315-a and first instance 315-b) of a corresponding (e.g., different) TB (e.g., TB1, TB2, TB3, TB4, multicast TB, broadcast TB). The UE may also receive one or more second DCIs 320 (e.g., including second DCI 320-a and second DCI 320-b), each second DCI scheduling a second instance 325 (e.g., including second instance 325-a and second instance 325-b) of a corresponding TB. In some cases, as used herein, the phrase “DCI” may refer to the first DCI 310, the second DCI 320, or both.

[0297] In some cases, the UE may receive, in the first MBS PDCCH, the first DCI 310-a and the first DCI 310-b of TB2 and TB3 respectively, scheduled via the first MBS PDCCH. The UE may also receive, in the second MBSPDCCH, the second DCI 320-a and the second DCI 320-b respectively, scheduled for the second instance 325-a of TB2 and the second instance 325-b of TB3. The first instance 315-a and the second instance 325-a may be time-interleaved, such that instances of TB2 are interleaved among instances of other TBs, including TB3. Based on one or more indications of the first DCI 310-a and the second DCI 320-a, the UE may perform soft combination 330-a on the first instance 315-a and the second instance 325-a. Additionally or alternatively, based on one or more indications of the first DCI 310-b and the second DCI 320-b, the UE may perform a soft combination 330-b on the first instance 315-b and the second instance 325-b.

[0298] In some respects, MBS TB time interleaving (e.g., as referenced) Figure 3 The described method is backward compatible with a second group of UEs (e.g., older UEs, legacy UEs). For example (e.g., for broadcast MTCH), the second group of UEs can detect various transmissions of the first MTCH PDCCH and the second MTCH PDCCH, and can receive the first instance 315 and the second instance 325 of the TB. However, the second group of UEs may not perform soft combination 330 based on the fact that, for example, no NDI or HPD is received (e.g., not detected, not decoded, not known) in each of the first DCI 310 and the second DCI 320, which may indicate to some UEs (e.g., new UEs, UEs with MBS TB inter-time interleaving capability) that each first instance in the first instance 315 may be the initial transmission of the corresponding TB, and that each second instance in the second instance 325 may be a retransmission of the corresponding TB.

[0299] However, the first group of UEs (e.g., a new UE, a UE with MBS TB inter-time interleaving capability) can receive an indication that the first instance 315 and the second instance 325 of the same TB correspond to the same TB, which allows the first group of UEs to perform soft combination 330. In some cases, the first DCI 310, the second DCI 320, or both can indicate to the UE that the first instance 315 and the second instance 325 correspond to the same TB. For example, each of the first DCIs in the first DCI 310, each of the second DCIs in the second DCI 320, or both may include a field for indicating that the first instance 315, the second instance 325, or both scheduled respectively correspond to the corresponding TB. In some cases, this field may include NDI, HPI, or both. In some cases, one or more of the first DCIs in the first DCI 310, one or more of the second DCIs in the second DCI 320, or both may have a first DCI format (e.g., DCI format 4_0), and may additionally include this field. Additionally or alternatively, some UEs in the second group (e.g., legacy UEs, second-generation UEs) may omit this field in the first DCI 310 and the second DCI 320, and may not combine TB with different RVs.

[0300] In some cases, the first DCI format can be used to schedule PDSCH for broadcast in a downlink cell and may include a cyclic redundancy check (CRC) scrambled by the Multicast Control Channel Radio Network Temporary Identifier (MCCH-RNTI) or by broadcast scrambled with G-RNTI configured via MBS-SessionInfo to indicate information to the UE. For example, the indicated information may include frequency domain resource assignments (e.g., the size of the CORESET if it is configured for the cell; or the size of the initial downlink bandwidth portion if it is not configured for the cell), one or more time domain resource assignments (e.g., 4 bits as defined in one or more standard documents), Virtual Resource Block (VRB) to Physical Resource Block (PRB) mappings (e.g., 1 bit), MCS (e.g., 5 bits), RV (2 bits), MCCH change notifications (e.g., 2 bits if the CRC of the DCI is scrambled by MCCH-RNTI, otherwise reserved bits), reserved bits (e.g., 14 bits), or any combination thereof.

[0301] Additionally or alternatively, a second DCI format can be used to schedule interleaved TBs for MBS broadcast MTCH. For example, the first DCI 310, the second DCI 320, or both may have a format including an indication of the respective scheduled first instance 315, second instance 325, or both corresponding to the corresponding TB. For example, one or more of the first DCIs in the first DCI 310, one or more of the second DCIs in the second DCI 320, or both may have a second DCI format (e.g., DCI format 4_1, DCI format 4_2), wherein the second DCI format may indicate the NDI, HPI, or both of the respective scheduled instances for the corresponding TB. However, some UEs in the second group may not be able to use a DCI with the second DCI format to detect MBS TBs (e.g., MBS broadcast MTCH).

[0302] In some cases, the second DCI format can be used to schedule PDSCH for multicast in a downlink cell and may include a CRC scrambled by G-RNTI for multicast or by G-CS-RNTI configured via MBS-RNTI-SpecificConfig to indicate information to the UE. In some cases, the indicated information may include frequency domain resource assignments (e.g., the size of CORESET if CORESET is configured for a cell; or the size of the initial downlink bandwidth portion if CORESET is not configured for a cell), one or more time domain resource assignments (e.g., 4 bits as defined in one or more standard documents), VRB to PRB mapping (e.g., 1 bit), MCS (e.g., 5 bits), NDI (e.g., 1 bit), RV (2 bits), HARQ procedure number (e.g., 4 bits), downlink assignment index (e.g., 2 bits), PUCCH resource indicator (e.g., 3 bits), PDSCH to HARQ feedback timing indicator (e.g., 3 bits), reserved bits (e.g., 3 bits), or any combination thereof.

[0303] Additionally or alternatively, a UE implementing MBS inter-TB time interleaving may receive control information indicating a time window, wherein the UE may determine, based on the time window, that two or more instances correspond to the same TB. For example, one or more first DCIs in a first DCI 310, one or more second DCIs in a second DCI 320, one or more other DCIs, or one or more RRC messages, or any combination thereof, may indicate a time window to the UE. In some cases, the UE may determine that two or more instances of a TB scheduled in the same channel or subcarrier during the time window correspond to the same TB. In some cases, the UE may receive a first instance of a TB, and after receiving the first instance, after the time window expires, may receive a second instance of the TB. Based on the fact that the second instance is a first time instance of a TB received after the time window from the receipt of the first TB, the UE may determine that the first instance and the second instance belong to the same TB. In some cases, the UE may decode the TB based on the determination that the first instance and the second instance correspond to the same TB, which may include soft combining the first instance and the second instance. In some examples, the UE may determine that any TB received within the time window corresponds to the same TB.

[0304] In some cases, MBS TB time interleaving (e.g., as referenced) Figure 3The described features may be associated with one or more advantages. For example, a wireless communication system that implements time interleaving between MBS TBs allows UEs of different generations to receive the same control signaling and shared signaling (e.g., the same PDCCH / PDSCH transmission, the same first DCI 310 and second DCI 320). This reduces signaling overhead and supports backward compatibility across various types of UEs supporting different capabilities.

[0305] In some cases, the first DCI 310, the second DCI 320, or both may indicate the RV corresponding to the corresponding scheduling instance of the corresponding TB. The DCI may include an RV index field, which includes the number of bits used to indicate the RV. For example, the number of bits may be two, such that UEs in the second group (e.g., legacy UEs) and UEs in the first group (e.g., new UEs, UEs with MBS TB inter-time interleaving capability) can read the RV index field. In some cases (e.g., for up to four instances of a TB (e.g., duplicates)), the RV index field may include two bits to indicate the RV index for each instance from group {0, 1, 2, 3}.

[0306] In some cases, a TB may correspond to more than four instances (e.g., more than four RVs). For example, a TB may correspond to eight instances, and the DCI may include an RV index field with more than two bits (e.g., three bits) such that the RV index field indicates an RV index from the group {0, 1, 2, 3, 4, 5, 6, 7}. In some cases, for example, a TB associated with eight instances may be associated with greater diversity gain (e.g., achieving greater diversity gain) compared to a TB associated with four instances.

[0307] In some cases, the DCI may have a format that includes an RV index field of more than two bits (e.g., three bits) that indicates the RV index of the corresponding instance of the TB from the group {0, 1, 2, 3, 4, 5, 6, 7}. For example, as described herein, the DCI may have a second DCI format (e.g., DCI format 4_1, DCI format 4_2) to schedule instances of the TB using an RV index field of more than two bits.

[0308] Additionally or alternatively, a UE receiving a TB corresponding to more than four instances (e.g., a new UE) may receive these instances according to a predefined RV index order. For example, the UE may ignore the 2-bit RV index field in the DCI and may assume that the RVs of the instances of the TB follow a predefined (e.g., pre-configured) order (e.g., for each instance associated with the same HPID, NDI, or both). For example, the UE may decode a portion (e.g., only a portion) of each of the first DCI 310 and the second DCI 320, where that portion may not include (e.g., may exclude) the RV index field of the DCI. The UE may avoid decoding the excluded portion of the DCI later. In some cases, for a TB associated with eight or more instances, the RV index order may be {0, 4, 6, 2, 7, 3, 5, 1}, or for a TB associated with four instances (e.g., or fewer than eight instances), the RV index order may be {0, 2, 3, 1}.

[0309] Figure 4 An example of a resource allocation diagram 400 supporting inter-TB time interleaving is shown according to one or more aspects of this disclosure. In some cases, aspects of the resource allocation diagram 400 may be implemented Figure 1 to Figure 3 These aspects or are implemented by these aspects. For example, resource allocation diagram 400 may include one or more DCIs 410, one or more TBs, and one or more instances of TBs, which may be respectively as described herein relative to... Figure 1 to Figure 3 Examples of DCI, TB, and TB instances described. In some cases, wireless communication systems can implement MBS TB time intervals according to resource allocation diagram 300.

[0310] In some cases, implementing MBS inter-TB time interleaving may include scheduling one or more instances of a TB (e.g., at least first instance 415 and second instance 425) via a single (e.g., one) DCI (e.g., DCI 410, which may be referred to as a DCI message). For example, a UE (e.g., UE 115, a network entity) may receive one or more DCI 410s (e.g., including DCI 410-a and DCI 410-b, DCI messages) from a network entity (e.g., network entity 105), which may each schedule multiple instances of a TB (e.g., at least TB2 and TB3) (e.g., at least first instance 415 and second instance 425).

[0311] In some cases, network entities and UEs can utilize repetition and gap information to perform MBS single TB scheduling. The UE can receive signaling (e.g., receive control signaling) indicating information associated with the interleaving of MBS TBs. For example, this information may include the number of instances per TB and the time delay 420 between each instance of each TB (e.g., in time, slot, or symbol units). For example, the UE can receive DCI 410-a, which schedules a first instance 415-a and a second instance 425-a of TB 2. The scheduling information may indicate a first time offset or gap between DCI 410-a and the first instance 415-a of TB 2 (e.g., time resources, frequency resources, or both for the first instance 415-a), and a time delay 420-a between the first instance 415-a and the second instance 425-a of TB 2. Although the number of instances per TB shown in resource allocation diagram 400 can be two, the techniques described herein are applicable to any number of instances. In some cases, time delay 420-a may be the same as or different from time delay 420-b.

[0312] In some cases, the UE may receive indications of the number of instances and time delay 420 via a TDRA table or via control signaling (e.g., RRC signaling). For example, the UE may receive control signaling indicating both the number of instances and time delay 420, wherein the control signaling may be associated with a G-RNTI associated with the UE (e.g., both repetition information and time slots may be configured per G-RNTI via RRC). Additionally or alternatively, the TDRA table (e.g., in RRC signaling; and in DCI messages indicating the index of entries in the TDRA table) may indicate both the number of instances and time delay 420, wherein the time delay 420 (e.g., the length of time delay 420 in time, or the length in terms of the number of intervals such as time slots, micro-time slots, symbols, etc.) may be dynamic based on the number of TBs with interleaved instances (e.g., TB1, TB2, TB3, TB4). For example, if the number of TBs with interleaved instances increases, the time delay 420 may increase (e.g., to provide more space for instances of more TBs). In some cases, DCI 410 may include a TDRA index indicating the number of instances and time delay 420.

[0313] In some cases, some UEs (e.g., UEs with limited capabilities or UEs of different types or generations) may ignore (e.g., not decode) indications regarding the number of instances, time delay 420, or both in received control signaling. For example, some UEs may assume that the number of instances per TB is one. Additionally or alternatively, some UEs may ignore parameters associated with the number of instances and time delay 420 in the TDRA table and may assume that the number of instances is one.

[0314] Alternatively or additionally, the number of instances and time delay 420 may each be configured via a combination of a TDRA table or control signaling (e.g., RRC signaling). For example, the UE may receive control signaling (e.g., RRC signaling) indicating the number of instances in one or more TBs, and may determine the time delay 420 based on entries in the TDRA table. For example, DCI 410 may include a TDRA index indicating the time delay 420. Alternatively or additionally, the UE may receive control signaling indicating the time delay 420, and may determine the number of instances based on entries in the TDRA table. For example, DCI 410 may include a TDRA index indicating the number of instances in a scheduled TB.

[0315] In some cases, some UEs may not be able to receive the number of TB instances and time delay 420 individually via either control signaling or the TDRA table. For example, some UEs may not be configured to decode such information from control signaling (e.g., RRC signaling, DCI signaling) or may not have this capability, or some UEs may not be configured to determine information from the TDRA table or may not have this capability. Additionally or alternatively, some UEs may be able to receive DCI 410 and the first instance 415 of the TB (e.g., the first time instance of the TB scheduled by DCI 410) in the MBS PDCCH, but some UEs may not be able to receive later instances of the TB, including the second instance 425 outside the MBS PDCCH.

[0316] In some cases, MBS TB time interleaving (e.g., as relative to) Figure 4 The described features may be associated with one or more advantages. For example, due to the DCI 410 scheduling multiple instances of TB, it is comparable to the reference... Figure 3 Compared to the described technology, the reference Figure 4 The described technology can be associated with less signaling overhead (e.g., PDCCH overhead).

[0317] In some cases, network entities and UEs may support MBS single TB scheduling and indication of repetition and gaps, where repetition and gaps are configurable. DCI 410 may indicate RV indices associated with one or more instances of a TB (e.g., similar to those described herein relative to...). Figure 3(As described in the first DCI 310 and the second DCI 320). For example, DCI 410 may include an RV index field that indicates the RV index of one or more instances of a corresponding TB scheduled by DCI 410. In some cases, the RV index may be the same for all UEs (e.g., across multiple types of UEs, multiple capabilities of UEs, or multiple generations of UEs), or it may be different for different UEs (e.g., different RV indexes may apply to different types of UEs, different capabilities of UEs, or different generations of UEs). Since some UEs may not be able to receive or decode the RV index field in DCI 410, such UEs may assume that the RV indexes of the instances of TBs scheduled by DCI 410 follow a predefined (e.g., preconfigured) RV index order (e.g., pattern). For example, such UEs may assume the RV index order is {0, 2, 3, 1}. Additionally or alternatively, the RV index field of DCI 410 may indicate to such UEs the RV index of a first instance 415 of the TB, which may indicate a predefined RV index order. For example, the RV index field can indicate RV index 1, and the old UE can determine the RV index order {1, 0, 2, 3}.

[0318] In some cases, DCI 410 may have a first DCI format (e.g., DCI format 4_0 as described herein), which may include 2 bits for the RV index field. In some cases, DCI 410 may have a first DCI format when TBs (e.g., TB1, TB2, TB3, and TB4) may be associated with 4 instances (e.g., first instance 415, second instance 425, and 2 other instances).

[0319] However, in some cases, a TB may be associated with more than four instances. For example, a TB may be associated with eight instances (e.g., duplicates), such that the RV index for each instance may be a group {0, 1, 2, 3, 4, 5, 6, 7}. In some cases, increasing the number of instances of a TB may increase the gain associated with the TB. In such cases, and according to the techniques described herein, the UE in the first group may receive instances associated with the TB according to a predefined RV index order (e.g., for instances associated with the same HPID, NDI, or both). For example, for eight or more instances, the predefined RV index order may be {0, 4, 6, 2, 7, 3, 5, 1}.

[0320] In some cases, network entities and UEs may support MBS single TB scheduling and indication of repetition and gaps, where repetition and gaps are configurable. The RV index field in DCI 410 may indicate the RV index order for the corresponding TB. For example, the RV index field may indicate at least the initial RV in RV index order. For example, DCI 410 may have a second DCI format (e.g., DCI format 4_1, DCI format 4_2, new DCI format) that includes more than 2 bits (e.g., 3 bits) for the RV index field. Thus, the RV index field may indicate at least the initial RV index of the group {0, 1, 2, 3, 4, 5, 6, 7} (e.g., the RV index of the first instance 415), where the initial RV index may indicate the RV index order of the instance for the TB within a set of predefined RV index orders. As another example, DCI 410 may have a first DCI format and may include 2 bits for the RV index field, such that the RV index field may indicate the initial RV index of the group {0, 1, 2, 3}, wherein the initial RV index may indicate the RV index order of the instances for TB in a set of predefined RV index orders.

[0321] In some examples, some UEs (e.g., UEs of a specific type or generation, or UEs with limited capabilities) may ignore the RV index field of DCI 410 (e.g., an RV index field with 2 or more bits). In some cases, other UEs may assume the initial RV index (e.g., the RV index of the first instance 415) is 0. For example, a UE may receive DCI 410 and may decode a portion of DCI 410 that does not include (e.g., exclude) the RV index field.

[0322] In some examples, the wireless communication system can implement MBS TB-to-TB time interleaving, where MBS single-TB or multi-TB scheduling is supported by indications of the number of TBs, the number of repetitions or instances per TB, the TB-to-TB interleaving mode, TB scaling, or any combination thereof. In some cases, the UE (e.g., a UE with advanced capabilities or a higher-generation UE, a UE with MBS TB-to-TB time interleaving capability) can receive control information (e.g., one or more DCIs, RRC signaling) indicating one or more parameters corresponding to one or more MBS TB-to-TB time interleaving TBs (e.g., and one or more corresponding instances per TB). In some cases, the one or more parameters may include the number of TBs for MBS TB-to-TB time interleaving, the number of instances (e.g., repetitions) of each TB in that number of TBs, the time interleaving mode for the instances of TBs in that number of TBs, the TB scaling factor α, or any combination thereof. Additionally or alternatively, the HPI associated with each TB may be predefined as sequential and increasing in order. In some examples, each DCI 410 may include a set of parameters for a set of repetitions of the TB. In some examples, a single DCI 410 (e.g., DCI 410-a) may include parameters for multiple TBs (e.g., DCI 410-a may include parameters for scheduling interleaved instances of TB 2 and TB 3, and network entities may not send additional DCIs, such as DCI410-b).

[0323] As described herein, one or more parameters may include a TB scaling factor α. In some cases, the TB scaling factor can increase the data rate per time slot to avoid data rate reduction due to instances of TBs interleaved across multiple time slots. For example, the TB scaling factor can be used or defined via the following equation:

[0324] 1,

[0325] in It can represent the size of each instance of TB after the TB scaling factor is applied (e.g., in units of resources, symbols, slots, and time). It can represent the number of TBs, and This can represent the size of a TB that is not associated with multiple instances or time interleaving between MBS TBs (e.g., and therefore no TB scaling factor is applied). In some cases, the TB scaling factor can increase the size of the TB to provide higher throughput in MBS TB time interleaving scenarios. Additionally, the UE can base its TB on the decoding rate. and payload size To determine the low-density parity-check (LDPC) basemap for each TB (e.g., LDPC basemap). Figure 1 or LDPC base Figure 2 In some cases, the decoding rate... MCS indexes based on TB, and payload size It can be the TB size after scaling. For example, .

[0326] Implementing the TB scaling factor can affect other aspects of communication via MBS inter-TB time-interleaved TBs. For example, the finite buffer rate matching (LBRM) may increase due to TB scaling used for MBS point-to-multipoint (PTM) transmissions. In some cases, at least for multicast transmissions, if the LBRM differs between point-to-point (PTP) and PTM transmissions associated with TB scaling, the UE may not use the PTP associated with the C-RNTI for retransmissions of multicast PTM transmissions.

[0327] Implementing the TB scaling factor can also affect the threshold (e.g., maximum) data rate per symbol. For example, the threshold data rate per symbol can be increased due to TB scaling used for MBS PTM transmission. In some cases, the UE, network entity, or both can be configured to limit the threshold data rate in the component carriers (CCs) associated with the MBS utilizing TB scaling to no greater than the unicast threshold data rate of one or more CCs. For example, the threshold data rate across a certain number of CCs (e.g., wideband, all CCs) can remain constant (e.g., may not change).

[0328] In some cases, the time interleaving pattern, the RV index order associated with instances of a TB, or both, may be based on the number of instances per TB (e.g., indicated by one or more parameters). For example, when the number of instances of a TB is 4, the RV index order for instances of the TB may be {0, 2, 3, 1}. Additionally or alternatively, when the number of instances of a TB is 8 or more, the RV index order for instances of the TB may be {0, 4, 6, 2, 7, 3, 5, 1}.

[0329] In some cases, MBS TB time interleaving occurs (e.g., as in this paper relative to...). Figure 4 The described ( ) may be associated with one or more advantages. For example, with reference to this article Figure 3 Compared to the techniques described herein, the techniques for MBS TB inter-time interleaving described herein can be associated with less signaling overhead (e.g., PDCCH overhead) for some UEs, based on, for example, less control signaling (e.g., smaller control signaling after initial configuration, fewer control signaling messages).

[0330] In some examples, the techniques described herein may be compatible with semi-persistent scheduling (SPS) (e.g., SPS may be supported). For example, network entities may semi-statically configure any combination of parameters described herein on a per-SPS-Config basis or on a per-group configured scheduling radio network temporary identifier (G-CS-RNTI) basis via RRC signaling. Additionally or alternatively, network entities may dynamically configure any combination of parameters (e.g., on a per-SPS-Config basis or on a per-G-CS-RNTI basis) by activating a DCI via SPS. In some cases, UEs in the first group may receive a DCI in a first DCI format (e.g., legacy DCI, DCI format 4_0) to trigger an SPS-Config associated with the corresponding G-CS-RNTI, which may include one or more parameters from among the parameters for TB scheduling for MBS inter-TB time interleaving (e.g., parameters configured by RRC).

[0331] As described herein, the UE may receive dynamic scheduling for MBS inter-TB time-interleaving signaling, activation of MBS inter-TB time-interleaving SPS, or both of these DCIs (e.g., or other control signaling). In some cases, the DCI may have a format that includes a different size than the single-TB scheduling DCI format. The DCI format may also include fully flexible indications of the number of TBs to be scheduled, the number of instances per TB, the TB scaling factor, and the time-interleaving mode for the instances of the TB.

[0332] Additionally or alternatively, the DCI may include one or more DCI messages of a new format, which includes the same DCI message size as the single-TB DCI. In some cases, the new format of the DCI may be distinguished from other DCIs via separately configured G-RNTIs, non-overlapping SS sets, non-overlapping CORESETs, or any combination thereof (e.g., to distinguish a single-TB PDCCH from a new multi-TB PDCCH). In some cases, elements in such a DCI format may be each entry in a TDRA table. For example, entries in a TDRA table may include elements that may indicate (e.g., include) parameters described herein (e.g., in cases where multi-TB scheduling is dynamically indicated by the DCI). Additionally or alternatively, such a DCI format may include one or more fields to indicate parameters described herein (e.g., in cases where multi-TB scheduling is dynamically indicated by the DCI).

[0333] As described herein, a UE (e.g., UE 115) may implement one or more of the techniques described herein for MBS TB inter-time interleaving. For example, a network entity may select one or more of the described techniques for MBS broadcast services and MBS multicast services respectively, and the UE may be configured to use the selected technique for each MBS service. For example, a network entity may select the techniques described herein. Figure 1 The technology described is used in MBS broadcast services and may be referenced herein. Figure 4 The described technology is used for MBS multicast services (e.g., UE-based capabilities).

[0334] In some cases, network entities can select one or more technologies for MBS inter-TB time interleaving based on the data rate associated with MBS signaling and utilize those technologies to configure the UE. For example, based on the UE's capabilities, network entities can select the technologies referenced herein. Figure 3 and Figure 4 The described techniques are used for MBS broadcast services associated with low data rates (e.g., associated with a first G-RNTI or G-CS-RNTI) and may be optionally referenced herein. Figure 4 The described technology is used for MBS broadcast services associated with high data rates (e.g., associated with a second G-RNTI or G-CS-RNTI).

[0335] In some cases, devices implementing MBS TB time interleaving (e.g., UE, UE 115, network entity, network entity 105) can communicate based on MBS TB time interleaving configurations (e.g., scheduling, timelines). In some cases, some UEs in the first group of UEs can communicate based on configurations similar to or different from those in the second group of UEs (e.g., legacy UEs).

[0336] For example, in some multicast scenarios, the second group of UEs may include the processing time between the first PDSCH transmission and the second PDSCH transmission (e.g., time interval T). proc,1 This applies regardless of whether HARQ feedback is enabled or disabled. For example, when HARQ feedback for a HARQ procedure ID is disabled, the UE may not expect to receive another PDCCH carrying a DCI scheduled for the following: a PDSCH or a set of slot-aggregated PDSCHs scheduled for a given HARQ procedure, or it may not expect to receive another PDSCH without a corresponding PDCCH for a given HARQ procedure that begins before the processing time following the completion of the transmission of the first PDSCH or the reception of the slot-aggregated PDSCH for that HARQ procedure. The same configuration can be applied when HARQ feedback is enabled.

[0337] In some cases (e.g., for eRedCap UEs that support multicast), processing time can be applied to multicast MTCH and PDSCH, and the bandwidth used for MTCH and PDSCH can meet a threshold bandwidth. For example, the threshold bandwidth used for PDSCH can be 5 MHz, which can be similar to the threshold bandwidth applied to unicast PDSCH.

[0338] Additionally or alternatively, the first group of UEs may communicate with a configuration similar to that of the second group of UEs (e.g., legacy UEs). For example, except for the gaps between interleaved instances of TB (e.g., as described herein relative to...). Figure 3 In addition to the described time delay (420), the processing time described herein can be applied to the multicast MTCH PDSCH. For the eRedCap UE in the first group of UEs, the bandwidth of the multicast MTCH PDSCH can meet the first bandwidth threshold.

[0339] As another example, in some broadcast scenarios, the second group of UEs may not implement processing time. For example, processing time may not be applied to broadcast MCCH / MTCH PDSCH because HPID, NDI, or both may not be explicitly indicated in the DCI of the format used for broadcasting (e.g., DCI format 4_0), and the UEs in the second group may not be able to determine whether an instance scheduled by the DCI (e.g., PDSCH transmission) is an initial packet using the same HPID or a retransmission packet. Additionally, eRedCap UEs in the second group (e.g., broadcast-enabled) may not implement processing time for broadcast MCCH / MTCH PDSCH, and the bandwidth used for broadcast MCCH / MTCH PDSCH may meet a second bandwidth threshold. For example, the second bandwidth threshold may be 20MHz (e.g., it may be similar to the bandwidth of PDSCH used for transmitting System Information Blocks (SIBs), paging, or both).

[0340] Additionally or alternatively, if the HPID, NDI, or both used for broadcasting MTCH PDSCH are indicated by the corresponding scheduling DCI, then, except for the gaps between interleaved instances of TB (e.g., relative to this document), Figure 3 In addition to the described time delay (420), the first group of UEs may also apply processing time to broadcast MTCH PDSCH. Additionally or alternatively, the eRedCap UE in the first group of UEs may (e.g., via scheduling DCI, via other control signaling) receive indications for HPID, NDI, or both for broadcast MTCH PDSCH. In some cases, the bandwidth for broadcast MTCH PDSCH for the eRedCap UE in the first group of UEs may also meet a first bandwidth threshold.

[0341] Figure 5An example of a process flow 500 supporting inter-TB time interleaving according to one or more aspects of this disclosure is shown. In some cases, aspects of process flow 500 may be implemented Figure 1 to Figure 4 These aspects or are implemented by these aspects. For example, process flow 500 may include network entity 105-a and UE 115-b, which may be respectively as described in this article relative to... Figure 1 to Figure 4 Examples of network entity 105 and UE 115 described herein. Additionally or alternatively, UE 115-b may be referred to as a network entity. In some cases, UE 115-b and network entity 105-b may be referred to herein in relation to... Figure 3 The techniques described herein are used to perform time-interleaved communication between MBS TBs.

[0342] In the following description of process flow 500, these operations may be performed in a different order than those shown, or other operations may be added to or removed from process flow 500. For example, some operations may be omitted from process flow 500, some operations may be performed in a different order or at different times, or other operations may be added to process flow 500. Although UE 115-a and network entity 105-a are shown as performing the operations of process flow 500, some aspects of some operations may also be performed by one or more other wireless devices or network devices. In some aspects, a second network entity may refer to UE 115-a (e.g., UE 115-a may be an example of a network entity). As used herein, the term "DCI" may refer to one or more DCI messages.

[0343] At 505, network entity 105-a may receive information instructing a second network entity (e.g., UE 115-b) to convey the capability of a corresponding instance of time interleaving for a corresponding TB for multicast or broadcast services.

[0344] At 510, UE 115-a may receive information (e.g., control information, RRC signaling, DCI signaling) from network entity 105-a via one or more messages. For example, the information may indicate a time window associated with decoding a first TB of a first set of instances. Additionally or alternatively, UE 115-a may receive information indicating a redundant version index pattern for at least a first set of instances for the first TB.

[0345] At point 515, UE 115-a may receive from network entity 105-a one or more DCIs (e.g., DCI messages) for a first set of instances of a first TB co-scheduled. In some cases, network entity 105-a may configure the first set of one or more DCIs to be decoded by at least different UEs (e.g., a second network entity, an older UE) belonging to a different generation than UE 115-a (e.g., a new UE), wherein UE 115-a and the different UEs may be able to decode the first set of one or more DCIs. In some cases, UE 115-a may be able to convey the corresponding instances of time interleaving for the corresponding TB for multicast service or broadcast service or both, and the different UEs may not be able to do so.

[0346] In some cases, each DCI in one or more DCIs in the first group can schedule a corresponding instance in the first group of instances in the first TB. For example, each DCI in one or more DCIs in the first group can include a field indicating that the scheduled corresponding instance in the first group of instances corresponds to a corresponding instance in the first TB.

[0347] In some cases, the first group of one or more downlink control information messages may be a single DCI for scheduling the first group of instances in the first TB. In some aspects, the single DCI may include a field with two or more bits indicating an RV index associated with one instance in the first group of instances in the first TB. Additionally or alternatively, the single DCI may include a TDRA index indicating: first information indicating the number of instances in the first group of instances, and an indication of the time delay between corresponding instances in the first group of instances (e.g., ...). Figure 3 The second information (time delay 420) or both. Additionally or alternatively, UE 115-a may receive RRC information corresponding to the G-RNTI associated with UE 115-a, wherein the RRC information includes an indication of the first information, an indication of the second information, or both. For example, at 510, UE 115-a may receive RRC information having this information.

[0348] In some cases, each DCI in the first set of DCIs may include a corresponding field that indicates the corresponding HPI, the NDI associated with the scheduled corresponding instance in the first set of instances, or both. For example, the NDI associated with the corresponding HPI may indicate whether the scheduled corresponding instance is a first-time transmission corresponding to the first TB. Additionally or alternatively, the HPI may indicate whether the scheduled corresponding instance is a retransmission corresponding to the first TB.

[0349] The first set of DCIs may have one or more formats. For example, at least one DCI in the first set of one or more DCIs may have DCI format 4_0 (e.g., the first DCI format, as described herein relative to...). Figure 3 (As described). Additionally or alternatively, at least one of the first group of one or more DCIs may be used for broadcast services and may have DCI format 4_1 or DCI format 4_2 (e.g., as described herein with respect to...). Figure 3 The second DCI format described.

[0350] In some cases, UE 115-a can decode some or all of the portions of each DCI in the first group of DCIs. For example, UE 115-a can decode a portion (e.g., only a portion) of each DCI in one or more DCIs in the first group, wherein the portion can exclude the corresponding RV field of each corresponding DCI based on, for example, information indicating the RV index pattern received.

[0351] In some cases, the RV index pattern may indicate that the corresponding RV index associated with the first time instance in the first group of instances in the first TB is zero. In some cases, at least one DCI in one or more DCIs of the first group may include an RV field indicating the RV index associated with the first time instance in the first group of instances in the first TB, wherein the indicated RV index corresponds to an RV index pattern among a plurality of RV index patterns. In some cases, the RV index pattern may begin with the indicated RV index.

[0352] At 520, UE 115-a may (e.g., from network entity 105-a) receive a second set of one or more DCIs for co-scheduling a second set of instances of a second TB. In some aspects, the second set of one or more DCIs may be similar to the first set of DCIs (e.g., following the same configuration, pattern, or format as the first set of DCIs). For example, each DCI in the second set of one or more DCIs may schedule a corresponding instance in the second set of instances of the second TB, or the second set of DCIs may be a single DCI that schedules a second set of instances of the second TB. Additionally, network entity 105-a may configure the second set of one or more DCIs to be decodeable by at least a different UE belonging to a different generation than UE 115-a, wherein UE 115-a and another UE may be able to decode the first set of one or more DCIs and the second set of one or more DCIs. Additionally or alternatively, UE 115-a may be able to convey the corresponding instance of the time interleaving for the corresponding TB for multicast service or broadcast service or both.

[0353] At 525, UE 115-a can (from network entity 105-a) receive a first set of instances for a first TB and a second set of instances for a second TB for multicast service, broadcast service, or both. For example, UE 115-a can receive the first set of instances and the second set of instances via a set of one or more PDSCHs based on one or more DCIs in the first set and one or more DCIs in the second set, as described herein with respect to... Figure 2 and Figure 3 As described. For example, at least one instance in the first group of instances in the first TB and the second group of instances in the second TB may be temporally interleaved.

[0354] At 530, UE 115-a may decode at least the first TB based on the first set of instances received. In some cases, UE 115-a (e.g., for decoding the first TB) may perform a soft combination of the one or more instances in the first set of instances based on an indication that each instance in one or more instances of the first set of instances belongs to the first TB. Additionally or alternatively, UE 115-a may decode the first TB based on the fact that UE 115-a belongs to a first-generation UE different from a second-generation UE. Additionally or alternatively, UE 115-a may decode the first TB based on the fact that UE 115-a is capable of conveying the corresponding instances of time interleaving for the corresponding TB for multicast service, broadcast service, or both.

[0355] In some cases, one or more other factors may affect the decoding of the first TB. For example, decoding the first TB may be based on the number of instances of the first TB and the time delay (e.g., as described in this paper relative to...). Figure 3 The number of instances and time delay described are 420). Additionally or alternatively, decoding of the first TB may be based on the information received in the first set of instances at 510 within a time window (e.g., as described herein relative to...). Figure 3 (As described). Additionally or alternatively, based on the corresponding field of each DCI in the first group of one or more DCIs indicating that each instance in the first group of instances belongs to the first TB, UE 115-a can decode the first TB. In some cases, decoding the first TB may also be based on an RV index pattern indicated by one or more DCIs in the first group of DCIs (e.g., as described herein).

[0356] Therefore, network entity 105-a and UE 115-a can communicate one or more instances of MBS TB, where one or more instances of different TBs can be time-interleaved. In some cases, this can improve the reliability of communication between network entity 105-a and UE 115-a.

[0357] Figure 6An example of a process flow 600 supporting inter-TB time interleaving according to one or more aspects of this disclosure is shown. In some cases, aspects of process flow 600 may be implemented Figure 1 to Figure 5 These aspects or are implemented by these aspects. For example, process flow 600 may include network entity 105-b and UE 115-b, which may be as described herein with respect to... Figure 1 to Figure 5 Examples of network entity 105 and UE 115 described herein. In some respects, network entity 105-b and UE 115-b may be described according to this document relative to... Figure 4 The described technology refers to one or more aspects of the technique used to perform time-interleaved communication between MBS TBs.

[0358] In the following description of process flow 600, these operations may be performed in a different order than those shown, or other operations may be added to or removed from process flow 600. For example, some operations may be omitted from process flow 600, some operations may be performed in a different order or at different times, or other operations may be added to process flow 600. Although UE 115-b and network entity 105-b are shown as performing the operations of process flow 600, some aspects of some operations may also be performed by one or more other wireless devices or network devices. In some aspects, a second network entity may refer to UE 115-b (e.g., UE 115-b may be an example of a network entity). As used herein, the term “DCI” may refer to one or more DCI messages.

[0359] At 605, UE 115-b may send registration information to network entity 105-b. For example, the registration information may indicate UE 115-b's ability to receive one or more corresponding instances of multiple corresponding TBs via a threshold bandwidth (e.g., as described herein relative to...). Figure 4 (as described).

[0360] At 610, UE 115-b may receive control information from network entity 105-b indicating one or more parameters corresponding to a plurality of TBs, wherein the one or more parameters include the number of TBs in the plurality of TBs, the number of corresponding instances of each corresponding TB in the plurality of TBs, the time interleaving mode corresponding to the plurality of TBs, the TB scaling factor, or any combination thereof (e.g., as referenced herein). Figure 4 (as described).

[0361] In some cases, to receive control information, UE 115-b may receive one or more RRC messages indicating parameters (e.g., control information may be RRC messages). For example, these one or more RRC messages may semi-statically configure the one or more parameters to UE 115-b. In some cases, to receive control information, UE 115-b may receive one or more DCIs. For example, at least one of these one or more DCIs may activate the one or more parameters.

[0362] In some cases, UE 115-b may also receive control information (e.g., the same control information, different control information) for scheduling one or more corresponding instances of the multiple corresponding TBs, wherein the one or more corresponding instances of the multiple corresponding TBs may be time-interleaved according to a time-interleaving mode. In some cases, the one or more corresponding instances of the multiple corresponding TBs may be scheduled to have time gaps between each of the one or more corresponding instances.

[0363] In some cases, control information may include one or more DCIs that schedule a first group of instances of a first TB. In some cases, the one or more DCIs may include an identifier indicating that the first group of instances corresponds to a first TB. In some cases, at least one of the one or more DCIs may schedule resources (e.g., wireless communication resources, one or more frequency resources, one or more time resources) for receiving one or more of the plurality of TBs. In some cases, the one or more DCIs may have a format supported by UE 115-b for scheduling time-interleaved TBs between MBS TBs for multicast or broadcast services (e.g., DCI format 4_0, DCI format 4_1, DCI format 4_2, new DCI format).

[0364] In some cases, the one or more DCIs may be associated with one or more indicators, wherein the one or more indicators may include G-RNTI, CORESET, SS set, or any combination thereof. In some cases, the association of the one or more DCIs with the indicators may indicate that the one or more DCIs are related to communication with a multicast or broadcast service. Additionally or alternatively, the one or more DCIs may include (e.g., an indication) a TDRA index corresponding to a TDRA table that includes entries for the one or more parameters, as described herein. Additionally or alternatively, the one or more DCIs may include dedicated fields for the one or more parameters.

[0365] In some cases, UE 115-b may receive control information because it belongs to a first-generation UE (e.g., a new UE as described herein) that is different from a second-generation UE (e.g., an older UE as described herein). Additionally or alternatively, UE 115-b may receive control signaling because it is capable of conveying a corresponding instance of time interleaving for a given time interleaving TB for multicast or broadcast services. Additionally or alternatively, the control information may include one or more DCIs in a format supported by different UEs for scheduling time interleaved TBs for multicast or broadcast services (e.g., DCI format 4_0, DCI format 4_1, DCI format 4_2).

[0366] In some cases, network entity 105-b may be configured to allow control information to be decoded by at least a different UE belonging to a different generation than UE 115-b. Additionally or alternatively, UE 115-b and another UE may be able to decode the control information, and UE 115-b may be able to convey the corresponding instance of time interleaving for the corresponding TB for multicast or broadcast services.

[0367] In some cases, UE 115-b may receive control information indicating an HPI pattern corresponding to one or more instances of the plurality of TBs. For example, each corresponding instance in a first group of instances of a first TB may correspond to a corresponding HPI in the HPI pattern, and each corresponding instance in a second group of instances of a second TB may correspond to a corresponding HPI in the HPI pattern. As described herein, the first group of instances of the first TB and the second group of instances of the second TB may be time-interleaved based on the HPI pattern.

[0368] In some cases, UE 115-b may receive control information indicating one or more RV index patterns. For example, each RV index in a first RV index pattern of the one or more RV index patterns may correspond to each corresponding instance in a first group of instances of a first TB. Accordingly, the order of the first group of instances of the first TB may be based on the first RV index pattern.

[0369] At 615, UE 115-b can select a first RV index pattern from one or more RV index patterns based on the number of first group instances in the first TB satisfying a threshold number. In some cases, due to, for example, the UE selecting the first RV index pattern, the first group instances of the first TB and the second group instances of the second TB can be time-interleaved based on the first RV index pattern.

[0370] At 620, UE 115-b can monitor a first group of instances in the first TB and a second group of instances in the second TB via at least one PDSCH, through a bandwidth that meets a threshold bandwidth for multicast or broadcast. For example, the threshold bandwidth could be a 5 MHz bandwidth. In some cases, UE 115-b can also monitor the first group of instances in the first TB based on the transmission of registration information.

[0371] In some cases, the threshold bandwidth can be a reduced bandwidth. For example, a reduced bandwidth may include fewer frequency resources compared to the second bandwidth used to receive the fourth set of instances in the fourth TB, where the fourth set of instances can be a single instance, not time-interleaved with the fifth TB of instances, or associated with a single PDSCH, or any combination thereof.

[0372] At 625, UE 115-b can receive a first set of instances of a first TB and a second set of instances of a second TB among a plurality of TBs for multicast or broadcast services. For example, UE 115-b can receive the first and second sets of instances via a set of one or more PDSCHs based on one or more parameters, a time-interleaving mode, or any combination thereof. In some cases, the first set of instances of the first TB and the second set of instances of the second TB may be time-interleaved. In some cases, for multicast or broadcast services, the first set of instances of the first TB among the plurality of corresponding TBs may use a first HARQ procedure (e.g., associated with a first HPID), and the second set of instances of the second TB among the plurality of corresponding TBs may use a second HARQ procedure (e.g., associated with a second HPID).

[0373] As described herein, UE 115-b can be based on time gaps between each instance in the first set of instances and between each instance in the second set of instances (e.g., time delay 420, as described herein relative to...). Figure 4 The UE 115-b may receive the first and second sets of instances based on (e.g., according to, including) a processing time gap (e.g., a processing time, as described herein) between the termination of one or more PDSCHs of the first set associated with the first set of instances and another event. For example, this event may include additional control information for receiving the second set of one or more PDSCHs associated with the third TB, receiving the second set of one or more PDSCHs, or both. In some cases, the processing time gap may satisfy a threshold processing time, and the third TB may use either a first HARQ procedure or a second HARQ procedure. The UE 115-b may receive the first and second sets of instances based on the processing time gap satisfying a threshold processing time.

[0374] In some cases, receiving a first set of instances of a first TB among a plurality of corresponding TBs for multicast or broadcast services, based on time slots, may be based on an identifier included in the control information. For example, the identifier may indicate that the first set of instances corresponds to a first TB.

[0375] At 630, UE 115-b may decode the first TB (e.g., at least the first TB) based on a first set of instances received from the first TB. For example, decoding the first TB may be based on UE 115-b belonging to a first-generation UE (e.g., a new UE as described herein) that is different from a second-generation UE (e.g., an older UE as described herein). Additionally or alternatively, UE 115-b may decode the first set of instances based on UE 115-b's ability to convey the time-interleaved instances of the corresponding TB for multicast or broadcast services.

[0376] In some cases, decoding the first TB may include performing soft combination on one or more instances in a first set of instances of the first TB. For example, UE 115-b may perform soft combination on one or more instances in a first set of instances based on control information including an indication that each instance in the first set of instances of the first TB belongs to the first TB.

[0377] In some cases, UE 115-b can decode the first TB based on a TB scaling factor (e.g., as described in this paper relative to...). Figure 4 (As described). For example, the size of the first TB may be based on the TB scaling factor, the corresponding number of instances in the first group of instances of the first TB, or both.

[0378] Alternatively or additionally, UE 115-b may decode the first TB based on an LDPC basemap defined by the decoding rate and payload size of the first TB. In some cases, the payload size of the first TB may be based on a TB scaling factor applied to an unscaled TB size. Alternatively or additionally, UE 115-b may decode the first TB based on an LBRM size defined by the TB scaling factor.

[0379] Additionally or alternatively, the per-duration threshold data rate for multiple durations corresponding to the first set of instances of the first TB may be based on a TB scaling factor. In some cases, the per-duration threshold data rate for component carriers used for multicast or broadcast services may be less than or equal to the second threshold data rate used for unicast signaling.

[0380] In this manner, network entity 105-b and UE 115-b can communicate one or more instances of one or more corresponding TBs via MBS, the one or more instances being time-interleaved between TBs. In some cases, implementing the techniques described herein can increase the reliability of MBS communication between UE 115-b and network entity 105-b.

[0381] Figure 7 A block diagram 700 of a device 705 supporting inter-TB time interleaving according to one or more aspects of this disclosure is shown. Device 705 may be an example of various aspects of a UE 115 (which may also be referred to as a network entity) as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720) may include at least one processor that can be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0382] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to time interleaving between TBs). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a group of multiple antennas.

[0383] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to time interleaving between TBs), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a group of multiple antennas.

[0384] The communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be examples of components used to perform various aspects of inter-TB time interleaving as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be able to perform one or more of the functions described herein.

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

[0386] Additionally or alternatively, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented using code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, 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., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

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

[0388] The communication manager 720 can support wireless communication according to the examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages of a first group of instances of a first TB that are co-scheduled. The communication manager 720 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages of a second group of instances of a second TB that are co-scheduled. The communication manager 720 is capable of, configured to, or operable to support components for: receiving, based on one or more downlink control information messages of a first group of instances of a first TB and one or more downlink control information messages of a second group of instances of a second TB via one or more physical downlink shared channels (PDSCH) for multicast or broadcast services, wherein at least one instance of the first group of instances of the first TB is time-interleaved with the second group of instances of the second TB. The communication manager 720 is capable of, configured to, or operable to support components for: decoding the first TB based on the received first group of instances of the first TB.

[0389] Additionally or alternatively, the communication manager 720 may support wireless communication according to the examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for: receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, the time interleaving mode corresponding to the set of multiple TBs, the TB scaling factor, or any combination thereof. The communication manager 720 is capable of, configured to, or operable to support components for: receiving, according to the one or more parameters, via a set of one or more physical downlink shared channels (PDSCHs) for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved. The communication manager 720 is capable of, configured to, or operable to support components for: decoding a first TB based on the received first set of instances of the first TB.

[0390] Additionally or alternatively, the communication manager 720 may support wireless communication according to the examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for receiving control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each of the one or more corresponding instances of the set of multiple corresponding TBs. The communication manager 720 is capable of, configured to, or operable to support components for the following operations: receiving, via a first group of one or more physical downlink shared channels (PDSCHs) and based on a time interleaving mode, a first group of instances of a first TB and a second group of instances of a second TB in a group of multiple corresponding TBs for multicast or broadcast services, the first group of instances using a first HARQ procedure and the second group of instances using a second HARQ procedure, the time gap existing between each instance in the first group of instances and between each instance in the second group of instances, wherein the processing time gap between the termination of the first group of one or more PDSCHs and the receipt of second control information for scheduling the second group of one or more PDSCHs associated with a third TB or the receipt of the second group of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure. The communication manager 720 is capable of, configured to, or operable to support components for the following operations: decoding at least a first TB based on the first group of instances received from the first TB.

[0391] Additionally or alternatively, the communication manager 720 may support wireless communication according to the examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages for a first group of instances of a first TB that are co-scheduled. The communication manager 720 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages for a second group of instances of a second TB that are co-scheduled. The communication manager 720 is capable of, configured to, or operable to support components for: receiving, based on one or more downlink control information messages and one or more downlink control information messages, a first group of instances of a first TB and a second group of instances of a second TB via one or more physical downlink shared channels (PDSCH) for multicast or broadcast services, wherein at least one instance of the first group of instances of the first TB is time-interleaved with a second group of instances of the second TB. The communication manager 720 is capable of, configured to, or operable to support components for: decoding the first TB based on the received first group of instances of the first TB.

[0392] Additionally or alternatively, the communication manager 720 may support wireless communication according to the examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for: receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, the time interleaving mode corresponding to the set of multiple TBs, the TB scaling factor, or any combination thereof. The communication manager 720 is capable of, configured to, or operable to support components for: receiving, according to the one or more parameters, via a set of one or more physical downlink shared channels (PDSCHs) for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved. The communication manager 720 is capable of, configured to, or operable to support components for: decoding a first TB based on the received first set of instances of the first TB.

[0393] Additionally or alternatively, the communication manager 720 may support wireless communication according to the examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for receiving control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each of the one or more corresponding instances of the set of multiple corresponding TBs. The communication manager 720 is capable of, configured to, or operable to support components for the following operations: receiving, via a first group of one or more physical downlink shared channels (PDSCHs) and based on a time interleaving mode, a first group of instances of a first TB and a second group of instances of a second TB in a group of multiple corresponding TBs for multicast or broadcast services, the first group of instances using a first HARQ procedure and the second group of instances using a second HARQ procedure, the time gap existing between each instance in the first group of instances and between each instance in the second group of instances, wherein the processing time gap between the termination of the first group of one or more PDSCHs and the receipt of second control information for scheduling the second group of one or more PDSCHs associated with a third TB or the receipt of the second group of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure. The communication manager 720 is capable of, configured to, or operable to support components for the following operations: decoding at least a first TB based on the first group of instances received from the first TB.

[0394] By including or configuring a communication manager 720 according to examples as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources. For example, network entities (e.g., including UEs) implementing the techniques described herein can experience higher wireless communication reliability, which can result in fewer data retransmissions and thus more efficient use of communication resources.

[0395] Figure 8 A block diagram 800 of a device 805 supporting inter-TB time interleaving according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 (which may also be referred to as a network entity) as described herein. Device 805 may include receiver 810, transmitter 815, and communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0396] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to time interleaving between TBs). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a group of multiple antennas.

[0397] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to time interleaving between TBs), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a group of multiple antennas.

[0398] Device 805 or its various components may be examples of parts for performing various aspects of inter-TB time interleaving as described herein. For example, communication manager 820 may include DCI receiving component p, TB receiving component 830, TB decoding component 835, control information component 840, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use receiver 810, transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0399] Communication manager 820 can support wireless communication according to the examples disclosed herein. DCI receiving component 825 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages of a first group of instances of a first TB co-scheduled. DCI receiving component 825 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages of a second group of instances of a second TB co-scheduled. TB receiving component 830 is capable of, configured to, or operable to support components for: receiving, based on one or more downlink control information messages of a first group of instances of a first TB and one or more downlink control information messages of a second group of instances of a second TB via one or more physical downlink shared channels (PDSCH) for multicast or broadcast services, wherein at least one instance of the first group of instances of the first TB is time-interleaved with the second group of instances of the second TB. TB decoding component 835 is capable of, configured to, or operable to support components for: decoding the first TB based on the received first group of instances of the first TB.

[0400] Additionally or alternatively, the communication manager 820 may support wireless communication according to the examples disclosed herein. The control information component 840 is capable of, configured to, or operable to support components for receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, the time interleaving mode corresponding to the set of multiple TBs, the TB scaling factor, or any combination thereof. The TB receiving component 830 is capable of, configured to, or operable to support components for receiving, according to the one or more parameters, via a set of one or more physical downlink shared channels (PDSCHs) for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved. The TB decoding component 835 is capable of, configured to, or operable to support components for decoding a first TB based on the received first set of instances of the first TB.

[0401] Additionally or alternatively, the communication manager 820 may support wireless communication according to the examples disclosed herein. The control information component 840 is capable of, configured to, or operable to support components for receiving control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each of the one or more corresponding instances of the set of multiple corresponding TBs. TB receiving component 830 is capable of, configured to, or operable to support components for: receiving, via a first set of one or more physical downlink shared channels (PDSCHs) and based on a time interleaving mode, according to time slots for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the same set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time slots existing between each instance in the first set of instances and between each instance in the second set of instances, wherein a processing time slot between the termination of the first set of one or more PDSCHs and the receipt of second control information for scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure. TB decoding component 835 is capable of, configured to, or operable to support components for: decoding at least a first TB based on the received first set of instances of the first TB.

[0402] Additionally or alternatively, the communication manager 820 may support wireless communication according to the examples disclosed herein. The DCI receiving component 825 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages of a first group of instances of a first TB co-scheduled. The DCI receiving component 825 is capable of, configured to, or operable to support components for: receiving one or more downlink control information messages of a second group of instances of a second TB co-scheduled. The TB receiving component 830 is capable of, configured to, or operable to support components for: receiving, based on one or more downlink control information messages of a first group and one or more downlink control information messages of a first group and one or more downlink control information messages of a second group and one or more downlink shared channels (PDSCH) for multicast or broadcast services, wherein at least one instance of the first group of instances of the first TB is time-interleaved with the second group of instances of the second TB. The TB decoding component 835 is capable of, configured to, or operable to support components for: decoding the first TB based on the received first group of instances of the first TB.

[0403] Additionally or alternatively, the communication manager 820 may support wireless communication according to the examples disclosed herein. The control information component 840 is capable of, configured to, or operable to support components for receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, the time interleaving mode corresponding to the set of multiple TBs, the TB scaling factor, or any combination thereof. The TB receiving component 830 is capable of, configured to, or operable to support components for receiving, according to the one or more parameters, via a set of one or more physical downlink shared channels (PDSCHs) for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved. The TB decoding component 835 is capable of, configured to, or operable to support components for decoding a first TB based on the received first set of instances of the first TB.

[0404] Additionally or alternatively, the communication manager 820 may support wireless communication according to the examples disclosed herein. The control information component 840 is capable of, configured to, or operable to support components for receiving control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving pattern, and time gaps exist between each of the one or more corresponding instances of the set of multiple corresponding TBs. TB receiving component 830 is capable of, configured to, or operable to support components for: receiving, via a first set of one or more physical downlink shared channels (PDSCHs) and based on a time interleaving mode, according to time slots for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the same set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time slots existing between each instance in the first set of instances and between each instance in the second set of instances, wherein a processing time slot between the termination of the first set of one or more PDSCHs and the receipt of second control information for scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure. TB decoding component 835 is capable of, configured to, or operable to support components for: decoding at least a first TB based on the received first set of instances of the first TB.

[0405] Figure 9 A block diagram 900 is shown of a communication manager 920 supporting inter-TB time interleaving according to one or more aspects of this disclosure. The communication manager 920 may be an example of aspects of the communication manager 720, communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of inter-TB time interleaving as described herein. For example, the communication manager 920 may include a DCI receiving component 925, a TB receiving component 930, a TB decoding component 935, a control information component 940, an information receiving component 945, a DCI decoding component 950, a TB monitoring component 955, an RRC receiving component 960, a registration component 965, an RV index mode selection component 970, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0406] Communication manager 920 can support wireless communication according to examples disclosed herein. DCI receiving component 925 is capable of, configured to, or operable to support components for receiving one or more downlink control information messages of a first group of instances of a first TB. In some examples, DCI receiving component 925 is capable of, configured to, or operable to support components for receiving one or more downlink control information messages of a second group of instances of a second TB. TB receiving component 930 is capable of, configured to, or operable to support components for receiving, a first group of instances of a first TB and a second group of instances of a second TB for multicast or broadcast services via one or more physical downlink shared channels (PDSCHs) based on one or more first group of downlink control information messages and one or more second group of downlink control information messages, wherein at least one instance of the first group of instances of the first TB is time-interleaved with a second group of instances of the second TB. TB decoding component 935 is capable of, configured to, or operable to support components for decoding the first TB based on the received first group of instances of the first TB.

[0407] In some examples, a soft combination of the one or more instances in the first group of instances is performed based on the first group of one or more downlink control information messages including an indication that each instance in the first group of instances belongs to the first TB.

[0408] In some examples, the first TB is decoded based on the fact that the network entity belongs to a first-generation network entity that is different from the second-generation network entity, or the network entity is able to convey the corresponding instance of the time interleaving of the corresponding TB for multicast service or broadcast service or both.

[0409] In some examples, the first set of one or more downlink control information messages and the second set of one or more downlink control information messages are configured to be decoded by at least a second network entity belonging to a different generation than the network entity. In some examples, both the network entity and the second network entity are capable of decoding the first set of one or more downlink control information messages and the second set of one or more downlink control information messages. In some examples, the network entity is capable of conveying corresponding instances of time interleaving for the corresponding TB for multicast or broadcast services, or both.

[0410] In some examples, each downlink control information message in one or more downlink control information messages in a first group schedules a corresponding instance in the first group of instances in the first TB. In some examples, each downlink control information message in one or more downlink control information messages in a second group schedules a corresponding instance in the second group of instances in the second TB.

[0411] In some examples, each downlink control information message in the first group of one or more downlink control information messages includes a corresponding field indicating that the scheduled corresponding instance in the first group of instances corresponds to the first TB. In some examples, the processing system is configured to decode the first TB based on the corresponding field of each downlink control information message in the first group of one or more downlink control information messages.

[0412] In some examples, the corresponding field of each downlink control information message in one or more downlink control information messages in the first group indicates the corresponding HARQ procedure identifier (ID), the new data indicator (NDI) associated with the HARQ procedure ID, or both, associated with the corresponding instance scheduled in the first group of instances.

[0413] In some examples, the NDI associated with the corresponding HARQ process ID indicates whether the scheduled instance is the first time transmission corresponding to the first TB.

[0414] In some examples, the HARQ process ID indicates whether the scheduled instance is a retransmission corresponding to the first TB.

[0415] In some examples, at least one downlink control information message in the first group of one or more downlink control information messages has downlink control information format 4_.

[0416] In some examples, at least one downlink control information message in the first group of one or more downlink control information messages is used for broadcast services and has downlink control information format 4_1. In some examples, at least one downlink control information message in the first group of one or more downlink control information messages is used for broadcast services and has downlink control information format 4_2.

[0417] In some examples, information indicating a time window is received, where the first TB is decoded based on the first set of instances within that time window.

[0418] In some examples, first information indicating the number of first group instances of the first TB and second information indicating the time delay between the instances in the first group of instances of the first TB are received, wherein the first TB is decoded based on the number and the time delay, and wherein the first group of one or more downlink control information messages is a single downlink control information message that schedules the first group instances of the first TB.

[0419] In some examples, radio resource control information corresponding to a group radio network temporary identifier associated with a network entity is received, wherein the radio resource control information includes first information and second information.

[0420] In some examples, the single downlink control information message includes a time-domain resource allocation index indicating the first and second information.

[0421] In some examples, radio resource control information including first information is received, wherein the single downlink control information message includes a time-domain resource allocation index indicating second information.

[0422] In some examples, radio resource control information including second information is received, wherein the single downlink control information message includes a time-domain resource allocation index indicating the first information.

[0423] In some examples, the single downlink control information message includes a field with more than two bits that indicates a redundant version index associated with one instance in the first set of instances of the first TB.

[0424] In some examples, information indicating a redundancy version index pattern for a first set of instances for the first TB is received. In some examples, only a portion of each downlink control information message in one or more downlink control information messages of the first set is decoded, wherein the corresponding redundancy version field of each corresponding downlink control information message is excluded based on the received information, and wherein the first TB is decoded based on the redundancy version index pattern.

[0425] In some examples, the redundant version index pattern indicates that the corresponding redundant version index associated with the first instance in the first set of instances of the first TB is zero.

[0426] In some examples, at least one downlink control information message in one or more downlink control information messages in the first group includes a redundancy version field that indicates a redundancy version index associated with a first time instance in the first group of instances of the first TB. In some examples, the indicated redundancy version index corresponds to a redundancy version index pattern in a set of multiple redundancy version index patterns. In some examples, the redundancy version index pattern begins with the indicated redundancy version index.

[0427] Additionally or alternatively, the communication manager 920 may support wireless communication according to the examples disclosed herein. The control information component 940 is capable of, configured to, or operable to support components for receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, the time interleaving mode corresponding to the set of multiple TBs, a TB scaling factor, or any combination thereof. In some examples, the TB receiving component 930 is capable of, configured to, or operable to support components for receiving, via one or more physical downlink shared channels (PDSCHs) for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the set of multiple TBs, wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved. In some examples, the TB decoding component 935 is capable of, configured to, or operable to support components for decoding a first TB based on the received first set of instances of the first TB.

[0428] In some examples, receiving control information and decoding the first TB are based on: the network entity belonging to a first-generation network entity that is different from the second-generation network entity, or the network entity being able to convey the corresponding instance of time interleaving for the corresponding TB for multicast service or broadcast service or both.

[0429] In some examples, receiving control information may include receiving one or more radio resource control messages.

[0430] In some examples, the one or more radio resource control messages semi-statically configure the one or more parameters.

[0431] In some examples, receiving control information may include receiving one or more downlink control information messages.

[0432] In some examples, at least one of the one or more downlink control information messages is scheduled to receive resources from one or more TBs in the set of multiple TBs and activate the one or more parameters.

[0433] In some examples, the one or more downlink control information messages are in a time-interleaved TB format supported by network entities for scheduling multicast or broadcast services.

[0434] In some examples, the one or more downlink control information messages are associated with one or more of the following: a group radio network temporary identifier, a control resource set, an SS set, or any combination thereof. In some examples, this association indicates that the one or more downlink control information messages are related to communications of a multicast or broadcast service.

[0435] In some examples, the one or more downlink control information messages include a time-domain resource allocation index corresponding to a time-domain resource allocation table, which includes entries for the one or more parameters.

[0436] In some examples, the one or more downlink control information messages include dedicated fields for the one or more parameters.

[0437] In some examples, second control information is received indicating a HARQ process identifier (ID) pattern corresponding to instances of the set of multiple TBs, wherein each corresponding instance in the first set of instances of the first TB corresponds to a corresponding HARQ process ID in the HARQ process ID pattern, and each corresponding instance in the second set of instances of the second TB corresponds to a corresponding HARQ process ID in the HARQ process ID pattern, and wherein the first set of instances of the first TB and the second set of instances of the second TB are time-interleaved based on the HARQ process ID pattern.

[0438] In some examples, the first TB is decoded based on a TB scaling factor, where the size of the first TB is based on the TB scaling factor and the corresponding number of instances in the first group of instances of the first TB.

[0439] In some examples, the first TB is decoded based on a low-density parity-check (LDPC) basemap defined by the decoding rate and payload size of the first TB, and the payload size of the first TB is based on a TB scaling factor applied to the unscaled TB size.

[0440] In some examples, the first TB is decoded based on the finite buffer rate matching (LBRM) size defined by the TB scaling factor.

[0441] In some examples, the threshold data rate per duration in a set of multiple durations corresponding to the first set of instances of the first TB is based on the TB scaling factor.

[0442] In some examples, the threshold data rate per duration for component carriers used for multicast or broadcast services is less than or equal to the second threshold data rate used for unicast signaling.

[0443] In some examples, second control information indicating one or more redundant version index patterns is received, wherein the redundant version index in the first redundant version index pattern corresponds to each corresponding instance in the first group of instances, and wherein the order of the first group of instances in the first TB is based on the first redundant version index pattern.

[0444] In some examples, a first redundant version index pattern is selected from one or more redundant version index patterns based on the number of first group instances in the first TB satisfying a threshold number, wherein the first group instances in the first TB and the second group instances in the second TB are time-interleaved based on the first redundant version index pattern.

[0445] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. In some examples, the control information component 940 is capable of, configured to, or operable to support components for receiving control information for scheduling one or more corresponding instances of a set of multiple corresponding TBs, wherein the one or more corresponding instances of the set of multiple corresponding TBs are time-interleaved according to a time-interleaving pattern, with time gaps existing between each of the one or more corresponding instances of the set of multiple corresponding TBs. In some examples, the TB receiving component 930 is capable of, configured to, or operable to support components for: receiving, via a first set of one or more physical downlink shared channels (PDSCHs) and based on a time interleaving mode, according to time slots for multicast or broadcast services, a first set of instances of a first TB and a second set of instances of a second TB in the same set of multiple corresponding TBs, the first set of instances using a first HARQ procedure, the second set of instances using a second HARQ procedure, the time slots existing between each instance in the first set of instances and between each instance in the second set of instances, wherein the processing time slot between the termination of the first set of one or more PDSCHs and the receipt of second control information for scheduling the second set of one or more PDSCHs associated with a third TB or the receipt of the second set of one or more PDSCHs satisfies a threshold processing time, and wherein the third TB uses either the first HARQ procedure or the second HARQ procedure. In some examples, the TB decoding component 935 is capable of, configured to, or operable to support components for: decoding at least a first TB based on the received first set of instances of the first TB.

[0446] In some examples, the control information is configured to be decoded by at least a second network entity belonging to a different generation than the network entity. In some examples, both the network entity and the second network entity are capable of decoding the control information. In some examples, the network entity is capable of conveying the corresponding instance of time interleaving for the corresponding TB for multicast or broadcast services, or both.

[0447] In some examples, a first group of instances of the first TB and a second group of instances of the second TB are monitored via bandwidth that meets the threshold bandwidth for multicast or broadcast, via at least one PDSCH.

[0448] In some examples, registration information is sent, which instructs the network entity to receive the capability of one or more corresponding instances of a set of multiple corresponding TBs via a threshold bandwidth, wherein, in order to monitor the first set of instances of the first TB, the processing system is configured to monitor the first set of instances of the first TB based on the sending of the registration information.

[0449] In some examples, the threshold bandwidth is a reduced bandwidth. In some examples, the reduced bandwidth includes fewer frequency resources compared to the second bandwidth used to receive the fourth group of instances for the fourth TB. In some examples, the fourth group of instances is a single instance that is not time-interleaved with the fifth TB of instances, or associated with a single PDSCH, or any combination thereof.

[0450] In some examples, the threshold bandwidth is 5 MHz bandwidth.

[0451] In some examples, the control information includes one or more downlink control information messages scheduling a first group of instances of a first TB, the one or more downlink control information messages including an identifier indicating that the first group of instances corresponds to the first TB. In some examples, receiving the first group of instances of the first TB in the set of multiple corresponding TBs for multicast or broadcast services according to a time slot is based on the identifier indicating that the first group of instances corresponds to the first TB.

[0452] In some examples, soft combination is performed on the one or more instances in the first group of instances based on control information including an indication that each instance in one or more instances of the first group of instances belongs to the first TB.

[0453] Additionally or alternatively, the communication manager 920 may support wireless communications according to examples disclosed herein. In some examples, the DCI receiving component 925 is capable of, configured to, or operable to support components for receiving one or more downlink control information messages for a first group of instances of a first TB, co-scheduled. In some examples, the DCI receiving component 925 is capable of, configured to, or operable to support components for receiving one or more downlink control information messages for a second group of instances of a second TB, co-scheduled. In some examples, the TB receiving component 930 is capable of, configured to, or operable to support components for receiving, via one or more sets of first and second downlink control information messages for a first TB and a second TB for a multicast or broadcast service, wherein at least one instance of the first group of instances of the first TB is time-interleaved with an instance of the second group of instances of the second TB. In some examples, the TB decoding component 935 is capable of, can be configured to, or is operable to support components for decoding the first TB based on a first set of instances received from the first TB.

[0454] In some examples, in order to support decoding the first TB, the TB decoding component 935 is capable of, can be configured to, or can operate to support components for: performing a soft combination of the one or more instances in the first group of instances based on a first group of one or more downlink control information messages including an indication that each instance in one or more instances of the first group of instances belongs to the first TB.

[0455] In some examples, in order to support decoding the first TB, the TB decoding component 935 can be, configured, or operated to support components for decoding the first TB based on the network entity belonging to a first-generation network entity that is different from the second-generation network entity, or the network entity being able to convey a corresponding instance of time interleaving for the corresponding TB for multicast service or broadcast service or both.

[0456] In some examples, the first set of one or more downlink control information messages and the second set of one or more downlink control information messages are configured to be decoded by at least a second network entity belonging to a different generation than the network entity. In some examples, both the network entity and the second network entity are capable of decoding the first set of one or more downlink control information messages and the second set of one or more downlink control information messages. In some examples, the network entity is capable of conveying corresponding instances of time interleaving for the corresponding TB for multicast or broadcast services, or both.

[0457] In some examples, each downlink control information message in one or more downlink control information messages in a first group schedules a corresponding instance in the first group of instances in the first TB. In some examples, each downlink control information message in one or more downlink control information messages in a second group schedules a corresponding instance in the second group of instances in the second TB.

[0458] In some examples, each downlink control information message in the first group of one or more downlink control information messages includes a corresponding field indicating that the scheduled instance in the first group corresponds to the first TB. In some examples, the first TB is decoded based on the corresponding field of each downlink control information message in the first group of one or more downlink control information messages.

[0459] In some examples, the corresponding field of each downlink control information message in one or more downlink control information messages in the first group indicates the corresponding HARQ procedure identifier (ID), the new data indicator (NDI) associated with the HARQ procedure ID, or both, associated with the corresponding instance scheduled in the first group of instances.

[0460] In some examples, the NDI associated with the corresponding HARQ process ID indicates whether the scheduled instance is the first time transmission corresponding to the first TB.

[0461] In some examples, the HARQ process ID indicates whether the scheduled instance is a retransmission corresponding to the first TB.

[0462] In some examples, at least one downlink control information message in the first group of one or more downlink control information messages has downlink control information format 4_.

[0463] In some examples, at least one downlink control information message in the first group of one or more downlink control information messages is used for broadcast services and has downlink control information format 4_1. In some examples, at least one downlink control information message in the first group of one or more downlink control information messages is used for broadcast services and has downlink control information format 4_2.

[0464] In some examples, the information receiving component 945 is capable of, configured to, or able to operate to support components for receiving information indicating a time window, wherein the first TB is decoded based on a first set of instances within that time window.

[0465] In some examples, the information receiving component 945 is capable of, configured to, or operable to support components for: receiving first information indicating the number of first group instances of the first TB and second information indicating the time delay between the instances in the first group of instances of the first TB, wherein the first TB is decoded based on the number and the time delay, and wherein the first group of one or more downlink control information messages is a single downlink control information message that schedules the first group instances of the first TB.

[0466] In some examples, the RRC receiving component 960 is capable of, configured to, or able to operate to support components for receiving radio resource control information corresponding to a group radio network temporary identifier associated with a network entity, wherein the radio resource control information includes first information and second information.

[0467] In some examples, the single downlink control information message includes a time-domain resource allocation index indicating the first and second information.

[0468] In some examples, the RRC receiving component 960 is capable of, configured to, or able to operate to support components for receiving radio resource control information including first information, wherein the single downlink control information message includes a time-domain resource allocation index indicating second information.

[0469] In some examples, the RRC receiving component 960 is capable of, configured to, or able to operate to support components for receiving radio resource control information including second information, wherein the single downlink control information message includes a time-domain resource allocation index indicating the first information.

[0470] In some examples, the single downlink control information message includes a field with more than two bits that indicates a redundant version index associated with one instance in the first set of instances of the first TB.

[0471] In some examples, the information receiving component 945 is capable of, configured to, or operable to support components for receiving information indicating a redundancy version index pattern for a first set of instances of the first TB. In some examples, the DCI decoding component 950 is capable of, configured to, or operable to support components for decoding only a portion of each downlink control information message in the first set of one or more downlink control information messages, wherein this portion excludes a corresponding redundancy version field from each respective downlink control information message based on received information, and wherein the decoding of the first TB is based on the redundancy version index pattern.

[0472] In some examples, the redundant version index pattern indicates that the corresponding redundant version index associated with the first instance in the first set of instances of the first TB is zero.

[0473] In some examples, at least one downlink control information message in one or more downlink control information messages in the first group includes a redundancy version field that indicates a redundancy version index associated with a first time instance in the first group of instances of the first TB. In some examples, the indicated redundancy version index corresponds to a redundancy version index pattern in a set of multiple redundancy version index patterns. In some examples, the redundancy version index pattern begins with the indicated redundancy version index.

[0474] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. In some examples, the control information component 940 is capable of, configured to, or operable to support components for receiving control information indicating one or more parameters corresponding to a set of multiple TBs, wherein the one or more parameters include the number of TBs in the set of multiple TBs, the number of corresponding instances of each corresponding TB in the set of multiple TBs, the time interleaving mode corresponding to the set of multiple TBs, the TB scaling fac...

Claims

1. A network entity for wireless communication, the network entity comprising: Processing system, the processing system being configured to: Receive one or more downlink control information messages in the first group of the first instance of the first jointly scheduled first transport block; Receive one or more downlink control information messages in the second group of the second group instance of the jointly scheduled second transport block; The first set of instances of the first transport block and the second set of instances of the second transport block are received via one or more physical downlink control information messages (PDSCH) in accordance with the first set of one or more downlink control information messages and the second set of one or more downlink control information messages (PDSCH), wherein at least one instance of the first set of instances of the first transport block and the second set of instances of the second transport block are time-interleaved. as well as The first transport block is decoded based on the first set of instances that received the first transport block.

2. The network entity according to claim 1, wherein, in order to decode the first transport block, the processing system is configured to: Based on the first group of one or more downlink control information messages including an indication that each instance of one or more instances in the first group of instances belongs to the first transport block, a soft combination of the one or more instances in the first group of instances is performed.

3. The network entity according to claim 1, wherein, in order to decode the first transport block, the processing system is configured to: The first transport block is decoded based on the fact that the network entity belongs to a first-generation network entity that is different from the second-generation network entity, or the network entity is able to convey a corresponding instance of time interleaving for the corresponding transport block of the multicast service or the broadcast service or both.

4. The network entity of claim 1, wherein the first group of one or more downlink control information messages and the second group of one or more downlink control information messages are configured to be decoded by at least a second network entity belonging to a different generation than the network entity, wherein the network entity and the second network entity are capable of decoding the first group of one or more downlink control information messages and the second group of one or more downlink control information messages, and wherein the network entity is capable of conveying a corresponding instance of time interleaving for a corresponding transport block of the multicast service or the broadcast service or both.

5. The network entity of claim 1, wherein each downlink control information message in the first group of one or more downlink control information messages schedules a corresponding instance in the first group of instances of the first transport block, and wherein each downlink control information message in the second group of one or more downlink control information messages schedules a corresponding instance in the second group of instances of the second transport block.

6. The network entity of claim 5, wherein each downlink control information message in the first group of one or more downlink control information messages includes a field indicating that the scheduled corresponding instance in the first group of instances corresponds to a corresponding instance of the first transport block, wherein the processing system is configured to: The first transport block is decoded based on the corresponding field of each downlink control information message in the first group of one or more downlink control information messages.

7. The network entity of claim 6, wherein the corresponding field of each downlink control information message in the first group of one or more downlink control information messages indicates a corresponding Hybrid Automatic Repeat Request (HARQ) process identifier (ID) associated with the scheduled corresponding instance in the first group of instances, a New Data Indicator (NDI) associated with the HARQ process ID, or both.

8. The network entity of claim 7, wherein the NDI associated with the corresponding HARQ procedure ID indicates whether the scheduled corresponding instance is a first-time transmission corresponding to the first transport block.

9. The network entity of claim 7, wherein the HARQ procedure ID indicates whether the scheduled corresponding instance is a retransmission corresponding to the first transport block.

10. The network entity of claim 7, wherein at least one downlink control information message in the first group of one or more downlink control information messages has downlink control information format 4_0.

11. The network entity according to claim 7, wherein at least one of the following conditions exists: At least one downlink control information message in the first group of one or more downlink control information messages is used for the broadcast service and has downlink control information format 4_1; or At least one downlink control information message in the first group of one or more downlink control information messages is used for the broadcast service and has downlink control information format 4_2.

12. The network entity of claim 5, wherein the processing system is configured to: Receive information indicating a time window, wherein the first transport block is decoded based on the first set of instances within the time window.

13. The network entity of claim 1, wherein the processing system is configured to: Receive first information indicating the number of the first group instances of the first transport block and second information indicating the time delay between each instance in the first group instances of the first transport block, wherein the first transport block is decoded based on the number and the time delay, and wherein the first group of one or more downlink control information messages is a single downlink control information message that schedules the first group instances of the first transport block.

14. The network entity of claim 13, wherein the processing system is configured to: Receive radio resource control information corresponding to a group radio network temporary identifier associated with the network entity, wherein the radio resource control information includes the first information and the second information.

15. The network entity of claim 13, wherein the single downlink control information message includes a time-domain resource allocation index indicating the first information and the second information.

16. The network entity of claim 13, wherein the processing system is configured to: Receive radio resource control information including the first information, wherein the single downlink control information message includes a time-domain resource allocation index indicating the second information.

17. The network entity of claim 13, wherein the processing system is configured to: Receive radio resource control information including the second information, wherein the single downlink control information message includes a time-domain resource allocation index indicating the first information.

18. The network entity of claim 13, wherein the single downlink control information message includes a field having more than two bits, the field indicating a redundant version index associated with an instance of one of the first set of instances of the first transport block.

19. The network entity of claim 1, wherein the processing system is configured to: Receive information indicating the redundant version index pattern for the first set of instances of the first transport block; and Decode only a portion of each downlink control information message in the first group of one or more downlink control information messages, wherein the portion excludes the corresponding redundant version field of each corresponding downlink control information message based on the received information, and wherein the first transport block is decoded based on the redundant version index pattern.

20. The network entity of claim 19, wherein the redundancy version index mode indicates that the corresponding redundancy version index associated with the first time instance in the first set of instances of the first transport block is zero.

21. The network entity of claim 1, wherein at least one downlink control information message in the first group of one or more downlink control information messages includes a redundancy version field, the redundancy version field indicating a redundancy version index associated with a first time instance in the first group of instances of the first transport block, wherein the indicated redundancy version index corresponds to a redundancy version index pattern in a plurality of redundancy version index patterns, and wherein the redundancy version index pattern begins with the indicated redundancy version index.

22. A network entity for wireless communication, the network entity comprising: Processing system, the processing system being configured to: Send one or more downlink control information messages in the first group instance of the first jointly scheduled first transport block; Send one or more downlink control information messages in the second group of the second group instance of the jointly scheduled second transport block; as well as The first set of instances of the first transport block and the second set of instances of the second transport block are transmitted via one or more physical downlink control information messages of the first set and one or more downlink control information messages of the second set via one or more physical downlink shared channels (PDSCH) for multicast or broadcast services, wherein at least one instance of the first set of instances of the first transport block is interleaved with the second set of instances of the second transport block.

23. The network entity of claim 22, wherein each downlink control information message in the first group of one or more downlink control information messages schedules a corresponding instance in the first group of instances of the first transport block, and wherein each downlink control information message in the second group of one or more downlink control information messages schedules a corresponding instance in the second group of instances of the second transport block.

24. The network entity of claim 23, wherein each downlink control information message in the first group of one or more downlink control information messages includes a field indicating that the scheduled corresponding instance in the first group of instances corresponds to the first transport block.

25. The network entity of claim 24, wherein the corresponding field of each downlink control information message in the first group of one or more downlink control information messages indicates a corresponding Hybrid Automatic Repeat Request (HARQ) process identifier (ID) associated with the scheduled corresponding instance in the first group of instances, a New Data Indicator (NDI) associated with the HARQ process ID, or both.

26. The network entity of claim 25, wherein the NDI associated with the corresponding HARQ procedure ID indicates whether the scheduled corresponding instance is a first-time transmission corresponding to the first transport block.

27. The network entity of claim 25, wherein the HARQ procedure ID indicates whether the scheduled corresponding instance is a retransmission corresponding to the first transport block.

28. The network entity of claim 24, wherein at least one downlink control information message in the first group of one or more downlink control information messages has downlink control information format 4_0.

29. The network entity of claim 24, wherein at least one of the following conditions exists: At least one downlink control information message in the first group of one or more downlink control information messages is used for the broadcast service and has downlink control information format 4_1; or At least one downlink control information message in the first group of one or more downlink control information messages is used for the broadcast service and has downlink control information format 4_2.

30. The network entity of claim 23, wherein the processing system is configured to: Send information indicating the time window associated with the first set of instances and decoding the first transport block.

31. The network entity of claim 22, wherein the first group of one or more downlink control information messages and the second group of one or more downlink control information messages are configured to be decoded by at least a second network entity belonging to a different generation from at least a third network entity, wherein the second network entity and the third network entity are capable of decoding the first group of one or more downlink control information messages and the second group of one or more downlink control information messages, and wherein the third network entity is capable of conveying a corresponding instance of time interleaving for a corresponding transport block of the multicast service or the broadcast service or both.

32. The network entity of claim 22, wherein the processing system is configured to: Send first information indicating the number of the first group instances of the first transport block and second information indicating the time delay between each instance in the first group instances of the first transport block, wherein the first group of one or more downlink control information messages is a single downlink control information message that schedules the first group instances of the first transport block.

33. The network entity of claim 32, wherein the processing system is configured to: Send radio resource control information corresponding to a group radio network temporary identifier associated with a second network entity, wherein the radio resource control information includes the first information and the second information.

34. The network entity of claim 32, wherein the single downlink control information message includes a time-domain resource allocation index indicating the first information and the second information.

35. The network entity of claim 32, wherein the processing system is configured to: Transmit radio resource control information including the first information, wherein the single downlink control information message includes a time-domain resource allocation index indicating the second information.

36. The network entity of claim 32, wherein the processing system is configured to: Transmit radio resource control information including the second information, wherein the single downlink control information message includes a time-domain resource allocation index indicating the first information.

37. The network entity of claim 32, wherein the single downlink control information message includes a field having more than two bits, the field indicating a redundant version index associated with an instance of one of the first set of instances of the first transport block.

38. The network entity of claim 22, wherein each downlink control information message in the first group of one or more downlink control information messages includes a corresponding field having more than two bits, the corresponding field indicating a corresponding redundant version index associated with a corresponding instance in the first group of instances of the first transport block.

39. The network entity of claim 22, wherein the processing system is configured to: Send information indicating a redundant version index pattern for the first set of instances of the first transport block, wherein the redundant version index pattern is associated with decoding the first transport block.

40. The network entity of claim 39, wherein the redundancy version index mode indicates that the corresponding redundancy version index associated with the first time instance in the first set of instances of the first transport block is zero.

41. The network entity of claim 22, wherein at least one downlink control information message in the first group of one or more downlink control information messages includes a redundancy version field, the redundancy version field indicating a redundancy version index associated with a first time instance in the first group of instances of the first transport block, wherein the indicated redundancy version index corresponds to a redundancy version index pattern in a plurality of redundancy version index patterns, and wherein the redundancy version index pattern begins with the indicated redundancy version index.

42. The network entity of claim 22, wherein the processing system is configured to: Receive information instructing a second network entity to convey the capability of time-interleaved instances of a corresponding transport block for the multicast service or the broadcast service, wherein sending the first set of one or more downlink control information messages, sending the second set of one or more downlink control information messages, sending the first set of instances of the first transport block, or sending the second set of instances of the second transport block, or any combination thereof, is based on receiving the information.

Images