# US 2025/0159682 A1 · Inter-transport block time interleaving

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0159682 A1
- Document ID: US20250159682A1
- Status: Published application
- Kind: A1
- Application number: 18/506,982
- Filed: 2023-11-10
- Published: 2025-05-15
- Earliest claimed: 2023-11-10
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Le LIU; Alberto RICO ALVARINO; Ayan SENGUPTA
- Web page: https://patentgrep.com/patent/US20250159682A1

## CPC

- H04L 1/0071: {Use of interleaving (interleaving per se H03M13/27)}
- H04W 72/1273: of downlink data flows
- H04L 1/1812: Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04L 1/1845: {Combining techniques, e.g. code combining}
- H04L 1/1896: {ARQ related signaling}
- H04W 72/0446: Resources in time domain, e.g. slots or frames
- H04W 72/232: the control data signalling from the physical layer, e.g. DCI signalling
- H04L 2001/0093: {Point-to-multipoint}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Methods, systems, and devices for wireless communications are described. A network entity may transmit DCIs to a UE to schedule instances of one or more MBS TBs, the multiple instances of the one or more TBs being time-interleaved. For example, the network entity may transmit 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, where at least one instance of the first set of instances may be interleaved with the second set of instances. In some cases, the first and second set of DCIs may include one DCI to schedule the respective set of instances, or one DCI per instance of the respective set of instances. Additionally, or alternatively, the network entity may indicate one or more parameters to the UE associated with MBS inter-TB time interleaving.

## Claims

### Claim 1

A network entity for wireless communication, comprising:
a processing system configured to:
receive a first set of one or more downlink control information messages that collectively schedule a first set of instances of a first transport block;
receive a second set of one or more downlink control information messages that collectively schedule a second set of instances of a second transport block;
receive, via a set of one or more physical downlink shared channels (PDSCHs) 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, the first set of instances of the first transport block and the second set of instances of the second transport block for a multicast service or for a broadcast service, wherein at least one instance of the first set of instances of the first transport block is time-interleaved with the second set of instances of the second transport block; and
decode the first transport block based on reception of the first set of instances of the first transport block.

### Claim 2 (depends on 1)

The network entity of claim 1, wherein, to decode the first transport block, the processing system is configured to:
perform a soft combination of one or more instances of the first set of instances of the first transport block based on the first set of one or more downlink control information messages comprising an indication that each instance of the one or more instances of the first set of instances is of the first transport block.

### Claim 3 (depends on 1)

The network entity of claim 1, wherein, to decode the first transport block, the processing system is configured to:
decode the first transport block based on the network entity being of a first generation of network entity that is different from a second generation of network entity, or the network entity being capable of communicating time interleaved respective instances of respective transport blocks that are for the multicast service or the broadcast service, or both.

### Claim 4 (depends on 1)

The network entity of claim 1, wherein 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 decodable by at least a second network entity that is of a different generation than the network entity, wherein 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, and wherein the network entity is capable of communicating time interleaved respective instances of respective transport blocks that are for the multicast service or the broadcast service, or both.

### Claim 5 (depends on 1)

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

### Claim 6 (depends on 5)

The network entity of claim 5, wherein each downlink control information message of the first set of one or more downlink control information messages comprises a respective field indicating that the scheduled respective instance of the first set of instances corresponds to the first transport block, wherein the processing system is configured to:
decode the first transport block based on the respective field of each downlink control information message of the first set of one or more downlink control information messages.

### Claim 7 (depends on 6)

The network entity of claim 6, wherein the respective field of each downlink control information message of the first set of one or more downlink control information messages indicates a respective hybrid automatic repeat request (HARQ) process identifier (ID) associated with the scheduled respective instance of the first set of instances, a new data indicator (NDI) associated with the HARQ process ID, or both.

### Claim 8 (depends on 7)

The network entity of claim 7, wherein the NDI associated with the respective HARQ process ID indicates whether the scheduled respective instance is a first temporal transmission corresponding to the first transport block.

### Claim 9 (depends on 7)

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

### Claim 10 (depends on 7)

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

### Claim 11 (depends on 7)

The network entity of claim 7, wherein at least one of:
at least one downlink control information message of the first set of one or more downlink control information messages is for the broadcast service and has downlink control information format 4_1; or
at least one downlink control information message of the first set of one or more downlink control information messages is for the broadcast service and has downlink control information format 4_2.

### Claim 12 (depends on 5)

The network entity of claim 5, wherein the processing system is configured to:
receive information that indicates a time window, wherein decoding the first transport block is based on the first set of instances being within the time window.

### Claim 13 (depends on 1)

The network entity of claim 1, wherein the processing system is configured to:
receive first information that indicates a quantity of the first set of instances of the first transport block and second information that indicates a time delay between individual instances of the first set of instances of the first transport block, wherein decoding the first transport block is based on the quantity and the time delay, and wherein the first set of one or more downlink control information messages is a single downlink control information message that schedules the first set of instances of the first transport block.

### Claim 14 (depends on 13)

The network entity of claim 13, wherein the processing system is configured to:
receive radio resource control information that corresponds 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.

### Claim 15 (depends on 13)

The network entity of claim 13, wherein the single downlink control information message comprises a time domain resource allocation index that is indicative of the first information and the second information.

### Claim 16 (depends on 13)

The network entity of claim 13, wherein the processing system is configured to:
receive radio resource control information that includes the first information, wherein the single downlink control information message includes a time domain resource allocation index that is indicative of the second information.

### Claim 17 (depends on 13)

The network entity of claim 13, wherein the processing system is configured to:
receive radio resource control information that includes the second information, wherein the single downlink control information message includes a time domain resource allocation index that is indicative of the first information.

### Claim 18 (depends on 13)

The network entity of claim 13, wherein the single downlink control information message includes a field with more than 2 bits that indicates a redundancy version index associated with one instance of the first set of instances of the first transport block.

### Claim 19 (depends on 1)

The network entity of claim 1, wherein the processing system is configured to:
receive information that indicates a redundancy 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 of the first set of one or more downlink control information messages, wherein the portion excludes a respective redundancy version field of each respective downlink control information message based on receipt of the information, and wherein decoding the first transport block is based on the redundancy version index pattern.

### Claim 20 (depends on 19)

The network entity of claim 19, wherein the redundancy version index pattern indicates that a respective redundancy version index associated with a first temporal instance of the first set of instances of the first transport block is zero.

### Claim 21 (depends on 1)

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

### Claim 22

A network entity for wireless communication, comprising:
a processing system configured to:
transmit a first set of one or more downlink control information messages that collectively schedule a first set of instances of a first transport block;
transmit a second set of one or more downlink control information messages that collectively schedule a second set of instances of a second transport block; and
transmit, via a set of one or more physical downlink shared channels (PDSCHs) 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, the first set of instances of the first transport block and the second set of instances of the second transport block for a multicast service or a broadcast service, 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.

### Claim 23 (depends on 22)

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

### Claim 24 (depends on 23)

The network entity of claim 23, wherein each downlink control information message of the first set of one or more downlink control information messages comprises a respective field indicating that the scheduled respective instance of the first set of instances corresponds to the first transport block.

### Claim 25 (depends on 24)

The network entity of claim 24, wherein the respective field of each downlink control information message of the first set of one or more downlink control information messages indicates a respective hybrid automatic repeat request (HARQ) process identifier (ID) associate with the scheduled respective instance of the first set of instances, a new data indicator (NDI) associated with the HARQ process ID, or both.

### Claim 26 (depends on 25)

The network entity of claim 25, wherein the NDI associated with the respective HARQ process ID indicates whether the scheduled respective instance is a first temporal transmission corresponding to the first transport block.

### Claim 27 (depends on 25)

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

### Claim 28 (depends on 24)

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

### Claim 29 (depends on 24)

The network entity of claim 24, wherein at least one of:
at least one downlink control information message of the first set of one or more downlink control information messages is for the broadcast service and has downlink control information format 4_1; or
at least one downlink control information message of the first set of one or more downlink control information messages is for the broadcast service and has downlink control information format 4_2.

### Claim 30 (depends on 23)

The network entity of claim 23, wherein the processing system is configured to:
transmit information that indicates a time window associated the first set of instances and decoding the first transport block.

### Claim 31 (depends on 22)

The network entity of claim 22, wherein 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 decodable by at least a second network entity that is of a different generation than at least a third network entity, wherein the second network entity and the third 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, and wherein the third network entity is capable of communicating time interleaved respective instances of respective transport blocks that are for the multicast service or the broadcast service, or both.

### Claim 32 (depends on 22)

The network entity of claim 22, wherein the processing system is configured to:
transmit first information that indicates a quantity of the first set of instances of the first transport block and second information that indicates a time delay between individual instances of the first set of instances of the first transport block, and wherein the first set of one or more downlink control information messages is a single downlink control information message that schedules the first set of instances of the first transport block.

### Claim 33 (depends on 32)

The network entity of claim 32, wherein the processing system is configured to:
transmit radio resource control information that corresponds 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.

### Claim 34 (depends on 32)

The network entity of claim 32, wherein the single downlink control information message comprises a time domain resource allocation index that is indicative of the first information and the second information.

### Claim 35 (depends on 32)

The network entity of claim 32, wherein the processing system is configured to:
transmit radio resource control information that includes the first information, wherein the single downlink control information message includes a time domain resources allocation index that is indicative of the second information.

### Claim 36 (depends on 32)

The network entity of claim 32, wherein the processing system is configured to:
transmit radio resource control information that includes the second information, wherein the single downlink control information message includes a time domain resource allocation index that is indicative of the first information.

### Claim 37 (depends on 32)

The network entity of claim 32, wherein the single downlink control information message includes a field with more than 2 bits that indicates a redundancy version index associated with one instance of the first set of instances of the first transport block.

### Claim 38 (depends on 22)

The network entity of claim 22, wherein each downlink control information message of the first set of one or more downlink control information messages includes a respective field with more than 2 bits that indicates a respective redundancy version index associated with a respective instance of the first set of instances of the first transport block.

### Claim 39 (depends on 22)

The network entity of claim 22, wherein the processing system is configured to:
transmit information that indicates a redundancy version index pattern for the first set of instances of the first transport block, wherein the redundancy version index pattern is associated with decoding the first transport block.

### Claim 40 (depends on 39)

The network entity of claim 39, wherein the redundancy version index pattern indicates that a respective redundancy version index associated with a first temporal instance of the first set of instances of the first transport block is zero.

### Claim 41 (depends on 22)

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

### Claim 42 (depends on 22)

The network entity of claim 22, wherein the processing system is configured to:
receive information that indicate a capability of a second network entity to communicate time interleaved respective instances of respective transport blocks that are for the multicast service or the broadcast service, wherein transmitting the first set of one or more downlink control information messages, transmitting the second set of one or more downlink control information messages, transmitting the first set of instances of the first transport block, or transmitting the second set of instances of the second transport block, or any combination thereof, is based on receiving the information.
