Handling transport block level parity bits for interrupt transmission

文档序号:328352 发布日期:2021-11-30 浏览:8次 中文

阅读说明:本技术 处置中断发送的传输块级奇偶校验位 (Handling transport block level parity bits for interrupt transmission ) 是由 S.侯赛尼 A.阿明扎德戈哈里 J.郭 P.加尔 A.坎德卡尔 J.B.索里亚加 季庭方 于 2020-05-01 设计创作,主要内容包括:本发明描述了用于无线通信的方法、系统和设备。在一些系统中,基站可以在传输块(TB)编码期间中断用户设备(UE)。UE可以基于中断而取消TB的发送(例如,抑制处理),使得第一代码块子集被编码而第二子集未被编码。在一些情况下,UE可以接收针对包括用于TB的循环冗余校验(CRC)位的代码块的重传请求,其中CRC位未被准备。在一个示例中,UE可以修改CRC位(例如,将它们设置为公共值,丢弃它们等)以减少处理时间。在另一个示例中,基站可以请求所有被抢占的代码块的重传,从而支持TB CRC计算。在另一个示例中,基站或UE可以延长重传的处理时间线以支持TB CRC计算。(Methods, systems, and devices for wireless communication are described. In some systems, the base station may interrupt the User Equipment (UE) during Transport Block (TB) encoding. The UE may cancel transmission of the TB (e.g., suppression processing) based on the interruption such that the first subset of code blocks is encoded and the second subset is not encoded. In some cases, the UE may receive a retransmission request for a code block that includes Cyclic Redundancy Check (CRC) bits for the TB, where the CRC bits are not prepared. In one example, the UE may modify the CRC bits (e.g., set them to a common value, discard them, etc.) to reduce processing time. In another example, the base station may request retransmission of all preempted code blocks, thereby supporting TB CRC calculation. In another example, the base station or UE may extend the processing timeline for retransmissions to support TB CRC calculation.)

1. A method for wireless communications at a User Equipment (UE), comprising:

canceling transmission of a transport block comprising a plurality of code blocks, wherein a first subset of code blocks of the plurality of code blocks are encoded for transmission and a second subset of code blocks of the plurality of code blocks are not encoded for transmission based at least in part on the canceling;

receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the transport block;

determining, based at least in part on the cancelling, that a current state of the set of parity bits for the transport block corresponds to the first code block subset;

modifying the code block comprising the set of parity bits for the transport block based at least in part on the determination; and

transmitting the modified code block based at least in part on the retransmission request.

2. The method of claim 1, wherein the modifying comprises:

setting each bit of the set of parity bits for the transport block to a common bit value based at least in part on the determination.

3. The method of claim 2, wherein the common bit value is a zero bit value or a one bit value.

4. The method of claim 1, wherein the modifying comprises:

deleting the set of parity bits for the transport block from the code block based at least in part on the determination.

5. The method of claim 4, wherein the modifying further comprises:

rate matching the code block based at least in part on deleting the set of parity bits for the transport block from the code block.

6. The method of claim 1, further comprising:

receiving a message preempting the sending of the transport block, wherein the cancelling is based at least in part on receiving the message.

7. The method of claim 6, wherein:

the sending of the transport block is based at least in part on a first grant; and is

The message preempting the transmission of the transport block includes a second grant for a second transmission that overlaps with at least one time resource of the first grant.

8. The method of claim 6, wherein:

the sending of the transport block is based at least in part on a first grant; and is

The message preempting the sending of the transport block requests the UE to refrain from sending in the first granted at least one time resource.

9. The method of claim 1, further comprising:

transmitting the first subset of code blocks for the transport block based at least in part on the first subset of code blocks being encoded for transmission.

10. The method of claim 9, wherein transmitting the first subset of code blocks for the transport block comprises an initial transmission of the transport block by the UE.

11. The method of claim 1, wherein the set of parity bits comprises a set of cyclic redundancy check bits.

12. A method for wireless communications at a base station, comprising:

receiving a first subset of code blocks of a transport block from a User Equipment (UE), wherein transmission of the transport block is scheduled for a first set of resources;

transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources;

determining, based at least in part on the message, that transmission of a second subset of code blocks of the transport block is preempted by the UE, wherein the second subset of code blocks includes code blocks having a set of parity bits for the transport block; and

requesting retransmission of at least the second subset of code blocks based at least in part on the determination.

13. The method of claim 12, wherein requesting retransmission further comprises:

transmitting one or more retransmission request messages for a plurality of code block groups including at least the second subset of code blocks, wherein a retransmission request message for a code block group including the code block with the set of parity bits for the transport block is transmitted after each other retransmission request message in the one or more retransmission request messages.

14. The method of claim 13, wherein requesting retransmission further comprises:

requesting retransmission of each code block of the transport block based at least in part on the determination.

15. The method of claim 12, wherein requesting retransmission further comprises:

requesting retransmission of the transport block based at least in part on the determination.

16. The method of claim 15, wherein requesting retransmission of the transport block comprises:

requesting retransmission of the transport block based at least in part on a configuration of the base station, wherein the configuration enables preemption of transmissions by the UE and disables code block group-level retransmission requests by the base station.

17. The method of claim 12, wherein the determining further comprises:

identifying the second code block subset based at least in part on transmissions of the second code block subset scheduled for at least partial overlap in time with the second set of resources.

18. The method of claim 12, wherein the message indicating the second set of resources comprises a grant for a second transmission in the second set of resources.

19. The method of claim 12, wherein the message indicating the second set of resources requests the UE to refrain from transmitting in the second set of resources.

20. The method of claim 12, wherein the set of parity bits comprises a set of cyclic redundancy check bits.

21. A method for wireless communications at a User Equipment (UE), comprising:

canceling transmission of a transport block comprising a plurality of code blocks, wherein a first subset of code blocks of the plurality of code blocks are encoded for transmission and a second subset of code blocks of the plurality of code blocks are not encoded for transmission based at least in part on the canceling;

receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the transport block;

modifying a processing timeline based at least in part on the second subset of code blocks not being encoded for transmission;

encoding the second subset of code blocks for transmission based at least in part on the modified processing timeline; and

transmitting the code block based at least in part on the retransmission request and encoding the second subset of code blocks for transmission.

22. The method of claim 21, wherein modifying the processing timeline comprises:

modifying the processing timeline for transmitting the code chunk based at least in part on the retransmission request.

23. The method of claim 21, further comprising:

receiving a message comprising an authorization for a second transmission, wherein the cancelling is based at least in part on the authorization for the second transmission and modifying the processing timeline comprises:

modifying the processing timeline for the second transmission based at least in part on the second subset of code blocks not being encoded for transmission.

24. The method of claim 21, wherein modifying the processing timeline comprises:

determining a timeline extension based at least in part on the second subset of code blocks not being encoded for transmission; and

adding the timeline extension to the processing timeline to determine the modified processing timeline.

25. The method of claim 24, wherein the timeline extension comprises a configuration value.

26. The method of claim 24, further comprising:

calculating the timeline extension based at least in part on a number of code blocks in the second subset of code blocks, a length of the transport block, or a combination thereof.

27. The method of claim 21, further comprising:

calculating the set of parity bits for the transport block based at least in part on encoding the second subset of code blocks for transmission.

28. A method for wireless communications at a User Equipment (UE), comprising:

receiving a first grant for a first set of resources for a first uplink transmission;

receiving a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission;

canceling transmission of a transport block comprising a plurality of code blocks based at least in part on receiving the second grant, wherein the transport block is associated with the first uplink transmission, and wherein a first subset of code blocks of the plurality of code blocks are encoded for transmission and a second subset of code blocks of the plurality of code blocks are not encoded for transmission based at least in part on the cancellation;

receiving a third grant for a third set of resources for a third uplink transmission;

identifying a non-overlapping condition between the third set of resources and the first set of resources; and

processing the third grant based at least in part on identifying the non-overlapping condition.

29. The method of claim 28, further comprising:

determining that the third set of resources and the first set of resources at least partially overlap in time; and

identifying the third grant of the third set of resources as an error.

30. The method of claim 28, further comprising:

determining that the third set of resources and the first set of resources at least partially overlap in time;

encoding, using a first processing block, the transport block for the first uplink transmission based at least in part on the first uplink transmission corresponding to a first priority;

encoding, using a second processing block, an additional transport block for the third uplink transmission based at least in part on the third uplink transmission corresponding to a second priority different from the first priority; and

transmitting the third uplink transmission during a time resource that at least partially overlaps with the first set of resources.

Background

The following relates generally to wireless communications and more particularly to uplink retransmission handling.

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be able to support communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems, such as Long Term Evolution (LTE) systems, LTE-advanced (LTE-a) systems, or LTE-a Pro systems, and fifth generation (5G) systems that may be referred to as New Radio (NR) systems. These systems may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or discrete fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communication system may include multiple base stations or network access nodes, each supporting communication for multiple communication devices, which may be referred to as User Equipment (UE), simultaneously.

In some wireless communication systems, a base station may not be able to receive or decode a portion of an uplink transmission from a UE (e.g., due to poor channel quality, interference on a channel, etc.). In these cases, the base station may send a retransmission request message to the UE, and the UE may retransmit the information. For example, the base station may request the UE to retransmit the entire uplink transmission or may request the UE to retransmit a particular portion (e.g., a missing portion) of the uplink transmission. Uplink retransmission operations may improve communications in systems with unreliable uplink communication channels.

Disclosure of Invention

The described technology relates to improved methods, systems, devices, and apparatus that support handling Transport Block (TB) level parity bits. In general, the described techniques provide a processing operation that enables a User Equipment (UE) to meet a retransmission processing timeline if initial TB transmission is interrupted and code block processing is suspended. For example, in some wireless communication systems, the base station may interrupt the UE during TB coding. The UE may refrain from processing (e.g., cancelling transmission) of the TB based on the interruption such that a first code block subset of the TB is encoded for transmission while a second code block subset of the TB remains uncoded for transmission. If the UE receives a retransmission request for a code block that includes parity information (e.g., Cyclic Redundancy Check (CRC) bits) for a TB where the current state of the TB CRC bits does not correspond to the second subset of code blocks due to the TB encoding process being aborted (e.g., TB unsent), the UE may implement one or more techniques to handle the retransmission request.

In a first example, the UE may modify the code block (e.g., set the CRC bits to a common value or discard the CRC bits) to reduce processing time. In a second example, the base station may request retransmission of all preempted code blocks (e.g., all uncoded code blocks, all code blocks of a TB, or an entire TB) in order to support CRC calculation for the TB. In a third example, the base station or UE may extend the processing timeline for the transmission (e.g., the timeline for a higher priority transmission that retransmits or preempts the initial TB transmission) so that the allocated processing time supports TB CRC calculations in the UE.

A method for wireless communication at a UE is described. The method can comprise the following steps: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; determining, based on the cancelling, that a current state of a set of parity bits for the TB corresponds to the first code block subset; modifying a code block comprising a set of parity bits for the TB based on the determination; and transmitting the modified code block based on the retransmission request.

An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; determining, based on the cancelling, that a current state of a set of parity bits for the TB corresponds to the first code block subset; modifying a code block comprising a set of parity bits for the TB based on the determination; and transmitting the modified code block based on the retransmission request.

Another apparatus for wireless communication at a UE is described. The apparatus may include means for: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; determining, based on the cancelling, that a current state of a set of parity bits for the TB corresponds to the first code block subset; modifying a code block comprising a set of parity bits for the TB based on the determination; and transmitting the modified code block based on the retransmission request.

A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; determining, based on the cancelling, that a current state of a set of parity bits for the TB corresponds to the first code block subset; modifying a code block comprising a set of parity bits for the TB based on the determination; and transmitting the modified code block based on the retransmission request.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the modification may include operations, features, components, or instructions to: each bit of the set of parity bits for the TB is set to a common bit value based on the determination. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the common bit value may be a zero bit value or a one bit value.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the modification may include operations, features, components, or instructions to: the set of parity bits for the TB is deleted from the code block based on the determination. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the modification may also include operations, features, components, or instructions to: rate matching the code block based on removing the set of parity bits for the TB from the code block.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: receiving a message preempting transmission of the TB, wherein the cancelling may be based on receiving the message. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the transmission of the TB may be based on a first grant, and the message preempting the transmission of the TB includes a second grant for a second transmission that overlaps with at least one time resource of the first grant. In some other examples of the methods, apparatus, and non-transitory computer-readable media described herein, the transmission of the TB may be based on a first grant, and the message preempting the transmission of the TB requests that the UE refrain from transmitting in at least one time resource of the first grant.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: the first subset of code blocks is transmitted for the TB based on the first subset of code blocks being encoded for transmission. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmitting the first subset of code blocks to the TB may be an initial transmission of the TB by the UE.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of parity bits may be a set of CRC bits.

A method for wireless communication at a base station is described. The method can comprise the following steps: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and requesting retransmission of at least the second subset of code blocks based on the determination.

An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and requesting retransmission of at least the second subset of code blocks based on the determination.

Another apparatus for wireless communication at a base station is described. The apparatus may include means for: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and requesting retransmission of at least the second subset of code blocks based on the determination.

A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and requesting retransmission of at least the second subset of code blocks based on the determination.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, requesting retransmission may further include operations, features, means, or instructions for: transmitting one or more retransmission request messages for a set of Code Block Groups (CBGs) that includes at least the second subset of code blocks, wherein a retransmission request message for a CBG that includes a code block with a set of parity bits for the TB may be transmitted after each other retransmission request message in the one or more retransmission request messages. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, requesting retransmission may further include operations, features, means, or instructions for: requesting retransmission of each code block of the TB based on the determination.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, requesting retransmission may further include operations, features, means, or instructions for: requesting retransmission of the TB based on the determination. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, requesting retransmission of a TB may further include operations, features, components, or instructions to: requesting retransmission of the TB based on a configuration of the base station, wherein the configuration enables preemption of transmissions by the UE and disables CBG-level retransmission requests by the base station.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the determining may further include operations, features, components, or instructions for: identifying the second subset of code blocks based on transmissions that the second subset of code blocks is scheduled for at least partially overlapping in time with the second set of resources.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicating the second set of resources includes an authorization for a second transmission in the second set of resources. In some other examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message indicating the second set of resources requests that the UE refrain from transmitting in the second set of resources.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of parity bits may be a set of CRC bits. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the transmission of the TB may be an initial transmission of the TB by the UE.

A method for wireless communication at a UE is described. The method can comprise the following steps: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; modifying the processing timeline based on the second subset of code blocks not being encoded for transmission; encoding the second subset of code blocks for transmission based on the modified processing timeline; and transmitting the code block based on the retransmission request and encoding the second subset of code blocks for transmission.

An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; modifying the processing timeline based on the second subset of code blocks not being encoded for transmission; encoding the second subset of code blocks for transmission based on the modified processing timeline; and transmitting the code block based on the retransmission request and encoding the second subset of code blocks for transmission.

Another apparatus for wireless communication at a UE is described. The apparatus may include means for: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; modifying the processing timeline based on the second subset of code blocks not being encoded for transmission; encoding the second subset of code blocks for transmission based on the modified processing timeline; and transmitting the code block based on the retransmission request and encoding the second subset of code blocks for transmission.

A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; modifying the processing timeline based on the second subset of code blocks not being encoded for transmission; encoding the second subset of code blocks for transmission based on the modified processing timeline; and transmitting the code block based on the retransmission request and encoding the second subset of code blocks for transmission.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, modifying a processing timeline may include operations, features, components, or instructions for: a processing timeline for transmitting the code chunk is modified based on the retransmission request.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: a message including a grant for the second transmission is received, wherein the cancellation may be based on the grant for the second transmission. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, modifying a processing timeline may include operations, features, components, or instructions for: modifying a processing timeline for the second transmission based on the second subset of code blocks not being encoded for transmission.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, modifying a processing timeline may include operations, features, components, or instructions for: determining a timeline extension based on the second subset of code blocks not being encoded for transmission; and adding the timeline extension to the processing timeline to determine the modified processing timeline. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timeline extension may be a configuration value. Some other examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: the timeline extension is calculated based on the number of code blocks in the second subset of code blocks, the length of the TB, or a combination thereof.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: a set of parity bits for the TB is calculated based on encoding the second subset of code blocks for transmission.

A method for wireless communication at a base station is described. The method can comprise the following steps: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and transmitting a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block, the transmission being preempted based on the processing timeline for the UE and the second subset of code blocks.

An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and transmitting a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block, the transmission being preempted based on the processing timeline for the UE and the second subset of code blocks.

Another apparatus for wireless communication at a base station is described. The apparatus may include means for: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and transmitting a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block, the transmission being preempted based on the processing timeline for the UE and the second subset of code blocks.

A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: receiving a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and transmitting a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block, the transmission being preempted based on the processing timeline for the UE and the second subset of code blocks.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: determining a timeline extension based on the second subset of code blocks being preempted; and adding the timeline extension to the processing timeline to cause the UE to determine resources for transmission of the code chunks. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timeline extension may be a configuration value. Some other examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: the timeline extension is calculated based on the number of preempted code blocks in the second subset of code blocks, the length of the TB, or a combination thereof.

A method for wireless communication at a UE is described. The method can comprise the following steps: receiving a first grant for a first set of resources for a first uplink transmission; receiving a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; cancel transmission of a TB including a set of code blocks based on receiving the second grant, wherein the TB is associated with the first uplink transmission, and wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation; receiving a third grant for a third set of resources for a third uplink transmission; identifying a non-overlapping condition between the third set of resources and the first set of resources; and processing the third grant based on identifying the non-overlapping condition.

An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receiving a first grant for a first set of resources for a first uplink transmission; receiving a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; cancel transmission of a TB including a set of code blocks based on receiving the second grant, wherein the TB is associated with the first uplink transmission, and wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation; receiving a third grant for a third set of resources for a third uplink transmission; identifying a non-overlapping condition between the third set of resources and the first set of resources; and processing the third grant based on identifying the non-overlapping condition.

Another apparatus for wireless communication at a UE is described. The apparatus may include means for: receiving a first grant for a first set of resources for a first uplink transmission; receiving a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; cancel transmission of a TB including a set of code blocks based on receiving the second grant, wherein the TB is associated with the first uplink transmission, and wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation; receiving a third grant for a third set of resources for a third uplink transmission; identifying a non-overlapping condition between the third set of resources and the first set of resources; and processing the third grant based on identifying the non-overlapping condition.

A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receiving a first grant for a first set of resources for a first uplink transmission; receiving a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; cancel transmission of a TB including a set of code blocks based on receiving the second grant, wherein the TB is associated with the first uplink transmission, and wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation; receiving a third grant for a third set of resources for a third uplink transmission; identifying a non-overlapping condition between the third set of resources and the first set of resources; and processing the third grant based on identifying the non-overlapping condition.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: determining that the third set of resources and the first set of resources at least partially overlap in time; and identifying a third grant for the third set of resources as an error.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: determining that the third set of resources and the first set of resources at least partially overlap in time; encoding the TB for the first uplink transmission based on the first uplink transmission corresponding to a first priority using a first processing block; encoding, using a second processing block, an additional TB for the third uplink transmission based on the third uplink transmission corresponding to a second priority different from the first priority; and transmitting the third uplink transmission during a time resource that at least partially overlaps with the first set of resources.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the TB may occur at least partially concurrently with encoding the additional TBs.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: the method may further include sending an indication of a number of Component Carriers (CCs) for supporting uplink transmissions of a first priority and sending an indication of a number of CCs for supporting uplink transmissions of a second priority.

A method for wireless communication at a base station is described. The method can comprise the following steps: transmitting a first grant for a first set of resources for a first uplink transmission; transmitting a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; scheduling a third set of resources for the third uplink transmission according to a non-overlapping condition between the third set of resources and the first set of resources, and transmitting a third grant of the third set of resources for the third uplink transmission based on the scheduling.

An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: transmitting a first grant for a first set of resources for a first uplink transmission; transmitting a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; scheduling a third set of resources for the third uplink transmission according to a non-overlapping condition between the third set of resources and the first set of resources, and transmitting a third grant of the third set of resources for the third uplink transmission based on the scheduling.

Another apparatus for wireless communication at a base station is described. The apparatus may include means for: transmitting a first grant for a first set of resources for a first uplink transmission; transmitting a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; scheduling a third set of resources for the third uplink transmission according to a non-overlapping condition between the third set of resources and the first set of resources, and transmitting a third grant of the third set of resources for the third uplink transmission based on the scheduling.

A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: transmitting a first grant for a first set of resources for a first uplink transmission; transmitting a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission; scheduling a third set of resources for the third uplink transmission according to a non-overlapping condition between the third set of resources and the first set of resources, and transmitting a third grant of the third set of resources for the third uplink transmission based on the scheduling.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions to: a third uplink transmission is received based on a third grant and the schedule.

Drawings

Fig. 1 and 2 illustrate examples of a wireless communication system that supports handling Transport Block (TB) level parity bits that interrupt transmission according to aspects of the present disclosure.

Fig. 3 illustrates an example of an encoding process that supports handling TB-level parity bits for interrupted transmission, in accordance with aspects of the present disclosure.

Fig. 4A, 4B, and 4C illustrate examples of processing timelines in support of handling TB-level parity bits for interrupt transmission, according to aspects of the present disclosure.

Fig. 5-7 illustrate examples of process flows to support handling TB-level parity bits for interrupted transmission according to aspects of the present disclosure.

Fig. 8 and 9 present block diagrams of devices that support handling TB-level parity bits for interrupted transmissions, according to aspects of the present disclosure.

Fig. 10 illustrates a block diagram of a communication manager that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure.

Fig. 11 shows a diagram of a system including devices that support handling TB-level parity bits for interrupt transmission, in accordance with aspects of the present disclosure.

Fig. 12 and 13 depict block diagrams of apparatuses that support handling TB-level parity bits for interrupted transmissions, according to aspects of the present disclosure.

Fig. 14 illustrates a block diagram of a communication manager that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure.

Fig. 15 shows a diagram of a system including devices that support handling TB-level parity bits for interrupt transmission, in accordance with aspects of the present disclosure.

Fig. 16-19 show flow diagrams illustrating methods of supporting handling of TB-level parity bits for interrupted transmissions, according to aspects of the present disclosure.

Detailed Description

Some wireless communication systems may support uplink retransmissions in which a base station may request a User Equipment (UE) to retransmit uplink information that the base station fails to receive or decode. In some cases, the system may support Transport Block (TB) level retransmissions, Code Block Group (CBG) level retransmissions, code block level retransmissions, or some combination thereof. However, if operating with code block-based or CBG-based retransmissions, the transmission interruption may put pressure on the UE's processing timeline. For example, in some cases, the UE may interrupt during processing (e.g., encoding) of the TB, and the UE may cancel transmission of the TB. For example, the UE may abort or withhold the process based on the interrupt. Such cancellation of transmission (e.g., suppression of processing) may result in inaccurate current states of TB-level parity bits (e.g., Cyclic Redundancy Check (CRC) bits). That is, based on cancelling the transmission of the TB, a first subset of code blocks of the TB may be encoded for transmission, while a second subset of code blocks of the TB may be uncoded for transmission. The current state of the TB-level parity bits may correspond to the encoded first code block subset, rather than the unencoded second code block subset, resulting in an inaccurate set of parity bits with respect to the entire TB.

If the base station requests the UE to retransmit the code block including the TB-level parity bits (or the CBG containing the code block including the TB-level parity bits), the UE may process the uncoded second code block subset to calculate the parity bits for the entire TB. However, if the processing timeline for the retransmission corresponds to the minimum processing timeline for the UE (e.g., the minimum processing timeline N2 for Physical Uplink Shared Channel (PUSCH) preparation, which is measured as the gap between the end of the uplink grant, such as a Physical Downlink Control Channel (PDCCH) message, and the first symbol of the corresponding PUSCH resource), the UE may not be able to process the uncoded second generation code block subset within the allocated processing time. The UE, the base station, or both may implement one or more techniques to handle the TB-level parity bits that are interrupted from being transmitted.

In a first example, a UE may modify a code block including TB-level parity bits to reduce processing time and meet a processing timeline (e.g., a minimum processing timeline for the UE). In some cases, the UE may set each bit of the TB-level parity bits to a common bit value (e.g., "0"). In other cases, the UE may discard TB-level parity bits from the code block for transmission. In these other cases, the UE may perform rate matching based on the number of bits dropped from the code block (e.g., twenty-four bits).

In a second example, the base station may request retransmission of all preempted code blocks (e.g., all uncoded code blocks) of at least the TB based on the interrupted initial transmission. By requesting retransmission of all preempted code blocks, the UE may process and encode each code block in the subset of unencoded second code blocks based on the retransmission request. Processing the second code block subset allows the UE to update the state of the TB level parity bits to correspond to the entire TB (e.g., the CRC bits provide error checking for the second code block subset in addition to the first code block subset). By requesting retransmission of each other code block (or CBG) before retransmission of the code block (or CBG) including TB level parity bits, the UE can process the code blocks and calculate the TB level parity bits in time to send the last code block (or CBG). In some cases, the base station may request retransmission of the second subset of code blocks, all code blocks of the TB (e.g., in a code block or CBG level retransmission), or the entire TB (e.g., in a TB level retransmission).

In a third example, the base station, the UE, or both, may extend the processing timeline for the retransmission such that the allocated processing time supports the UE's computation of the TB level parity bits. For example, the minimum processing timeline may be extended by several symbols d to support processing of any unencoded code blocks and timely computation of TB-level parity bits to transmit code blocks that include TB-level parity bits. The timeline extension value may be determined statically or dynamically. In some cases, the base station may determine a timeline extension and indicate resources for retransmission based on the timeline extension. In other cases, the UE may determine a timeline extension and send the retransmission according to the timeline extension. Additionally or alternatively, if the interruption of the initial TB transmission is based on another uplink grant (e.g., an uplink grant for a higher priority uplink transmission), the base station may determine a timeline extension and indicate resources for the higher priority uplink transmission based on the timeline extension. In other cases, the UE may determine a timeline extension and transmit a higher priority uplink transmission according to the timeline extension.

Aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects are described with reference to an encoding process, a processing timeline, and a process stream. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to handling TB-level parity bits for interrupt transmission.

Fig. 1 illustrates an example of a wireless communication system 100 that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure. The wireless communication system 100 includes base stations 105, UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-advanced (LTE-a) network, an LTE-a Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low cost and low complexity devices.

The base station 105 may communicate wirelessly with the UE115 via one or more base station antennas. The base station 105 described herein may comprise or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a giga-NodeB (any of which may be referred to as a gNB), a home NodeB, a home eNodeB, or some other suitable terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UEs 115 described herein may be capable of communicating with various types of base stations 105 and network devices, including macro enbs, small cell enbs, gbbs, relay base stations, and the like.

Each base station 105 may be associated with a particular geographic coverage area 110 in which communications with various UEs 115 are supported. Each base station 105 may provide communication coverage for a respective geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE115 may utilize one or more carriers. The communication links 125 shown in the wireless communication system 100 may include uplink transmissions from the UEs 115 to the base stations 105 or downlink transmissions from the base stations 105 to the UEs 115. The downlink transmission may also be referred to as a forward link transmission, and the uplink transmission may also be referred to as a reverse link transmission.

The geographic coverage area 110 of a base station 105 can be divided into sectors that form a portion of the geographic coverage area 110, and each sector can be associated with a cell. For example, each base station 105 may provide communication coverage for a macro cell, a small cell, a hot spot, or other type of cell, or various combinations thereof. In some examples, the base stations 105 may be mobile and thus provide communication coverage for a moving geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, and overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous LTE/LTE-A/LTE-A Pro or NR network in which different types of base stations 105 provide coverage for various geographic coverage areas 110.

The term "cell" refers to a logical communication entity for communication with a base station 105 (e.g., over a carrier) and may be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) for distinguishing neighboring cells operating via the same or different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine Type Communication (MTC), narrowband internet of things (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access for different types of devices. In some cases, the term "cell" may refer to a portion (e.g., a sector) of the geographic coverage area 110 acted on by a logical entity.

The UEs 115 may be dispersed throughout the wireless communication system 100, and each UE115 may be fixed or mobile. UE115 may also be referred to as a mobile device, a wireless device, a remote device, a handset, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, station, terminal, or client. The UE115 may also be a personal electronic device, such as a cellular telephone, a Personal Digital Assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE115 may also refer to a Wireless Local Loop (WLL) station, an internet of things (IoT) device, an internet of everything (IoE) device, or an MTC device, among others, which may be implemented in various articles of manufacture such as appliances, vehicles, meters, and so on.

Some UEs 115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication techniques that allow devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communications or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay the information to a central server or application that may utilize the information or present the information to a human interacting with the program or application. Some UEs 115 may be designed to collect information or implement automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communications (e.g., a mode that supports unidirectional communications via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE115 include entering a power saving "deep sleep" mode when not engaged in active communication, or operating on a limited bandwidth (e.g., according to narrowband communication). In some cases, the UE115 may be designed to support critical functions (e.g., mission critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for these functions.

In some cases, the UE115 may also be able to communicate directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more of a group of UEs 115 communicating with D2D may be within the geographic coverage area 110 of the base station 105. The other UEs 115 in the group may be outside the geographic coverage area 110 of the base station 105 or may not be able to receive transmissions from the base station 105. In some cases, multiple groups of UEs 115 communicating via D2D may utilize a one-to-many (1: M) system, where each UE115 transmits to every other UE115 in the group. In some cases, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without base station 105 involvement.

The base stations 105 may communicate with the core network 130 and each other. For example, the base stations 105 may interface with the core network 130 over backhaul links 132 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130) over a backhaul link 134 (e.g., via an X2, Xn, or other interface).

Core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an Evolved Packet Core (EPC) that may include at least one Mobility Management Entity (MME), at least one serving gateway (S-GW), and at least one Packet Data Network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. User IP packets may be transmitted through the S-GW, which may itself be connected to the P-GW. The P-GW may provide IP address assignment as well as other functions. The P-GW may be connected to a network operator IP service. The operator IP services may include access to the internet, intranets, IP Multimedia Subsystem (IMS) or Packet Switched (PS) streaming services.

At least some network devices, such as base stations 105, may include subcomponents, such as access network entities, which may be examples of Access Node Controllers (ANCs). Each access network entity may communicate with UE115 through a plurality of other access network transmitting entities, which may be referred to as radio heads, smart radio heads, or transmit/receive points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or incorporated into a single network device (e.g., base station 105).

Wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, since the length of a wavelength ranges from about one decimeter to one meter, the region of 300MHz to 3GHz is called an Ultra High Frequency (UHF) region or a decimeter band. Building and environmental features may block or redirect UHF waves. However, the waves may penetrate the structure sufficiently for the macro cell to provide service to the UE115 located indoors. UHF-wave transmission can be associated with smaller antennas and shorter ranges (e.g., less than 100km) compared to transmission of smaller and longer waves using the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz.

The wireless communication system 100 may also operate in the ultra-high frequency (SHF) region using a frequency band from 3GHz to 30GHz, also referred to as a centimeter band. The SHF area contains bands such as the 5GHz industrial, scientific, and medical (ISM) band that may be opportunistically used by devices that may be tolerant of interference from other users.

The wireless communication system 100 may also operate in the Extremely High Frequency (EHF) region of the spectrum, also referred to as the millimeter-band (mm-band), e.g., from 30GHz to 300 GHz. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE115 and the base station 105, and EHF antennas of respective devices may be smaller and more closely spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays within the UE 115. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of bands across these frequency regions may vary from country to country or regulatory agency.

In some cases, the wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ Licensed Assisted Access (LAA), unlicensed LTE (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5GHz ISM band. When operating in the unlicensed radio frequency spectrum band, wireless devices such as base stations 105 and UEs 115 may employ a Listen Before Talk (LBT) procedure to ensure that a channel is cleared before data is transmitted. In some cases, operation in the unlicensed band may be based on a carrier aggregation configuration in combination with component carriers operating in the licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these. Duplexing in the unlicensed spectrum may be based on Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination of both.

In some examples, a base station 105 or UE115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, the wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication can improve spectral efficiency by employing multipath signal propagation by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by the transmitting device via different antennas or different combinations of antennas. Also, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) in which a plurality of spatial layers are transmitted to the same receiving device and multi-user MIMO (MU-MIMO) in which a plurality of spatial layers are transmitted to a plurality of devices.

Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting or receiving device (e.g., base station 105 or UE 115) to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array such that signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals communicated via the antenna elements may include the transmitting device or the receiving device applying certain amplitude and phase offsets to the signals carried via each of the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to an antenna array of a transmitting device or a receiving device, or relative to some other orientation).

In one example, the base station 105 may use multiple antennas or antenna arrays for beamforming operations for directional communication with the UEs 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times in different directions by the base station 105, which may include signals transmitted according to different sets of beamforming weights associated with different transmission directions. The beam directions may be identified (e.g., by the base station 105 or a receiving device such as the UE 115) using the transmissions in the different beam directions for subsequent transmission or reception by the base station 105.

Some signals, such as data signals associated with a particular receiving device, may be transmitted by the base station 105 in a single beam direction (e.g., a direction associated with a receiving device such as the UE 115). In some examples, a beam direction associated with transmission along a single beam direction may be determined based at least in part on signals transmitted in different beam directions. For example, the UE115 may receive one or more of the signals transmitted by the base station 105 in different directions, and the UE115 may report an indication to the base station 105 that it received a signal with the highest signal quality or other acceptable signal quality. Although the techniques are described with reference to signals transmitted by the base station 105 in one or more directions, the UE115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

A receiving device (e.g., a UE115, which may be an example of a mmW receiving device) may attempt multiple receive beams when receiving various signals such as synchronization signals, reference signals, beam selection signals, or other control signals from the base station 105. For example, a receiving device may attempt multiple receive directions by: receiving via different antenna sub-arrays, processing received signals according to the different antenna sub-arrays, receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array, or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array, any of which steps may be referred to as "listening" according to different receive beams or receive directions. In some examples, a receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving data signals). A single receive beam may be aligned in a beam direction determined based on sensing according to a different receive beam direction (e.g., a beam direction determined to have the highest signal strength, the highest signal-to-noise ratio, or otherwise acceptable signal quality based on sensing according to multiple beam directions).

In some cases, the antennas of a base station 105 or UE115 may be located within one or more antenna arrays that support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located in an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with the base station 105 may be located at different geographic locations. The base station 105 may have an antenna array with rows and columns of multiple antenna ports that the base station 105 may use to support beamforming for communications with the UEs 115. Likewise, the UE115 may have one or more antenna arrays that may support various MIMO or beamforming operations.

In some cases, the wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications over the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority processing and multiplex logical channels into transport channels. The MAC layer may also provide retransmissions in the MAC layer using hybrid automatic repeat request (HARQ) to improve link efficiency. In the control plane, a Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of RRC connections between the UE115 and the base station 105 or core network 130 that support radio bearers for user plane data. In the physical layer, transport channels may be mapped to physical channels.

In some cases, the UE115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is a technique that increases the likelihood of correctly receiving data over the communication link 125. 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)). Under poor radio conditions (e.g., signal-to-noise conditions), HARQ may improve throughput at the MAC layer. In some cases, a wireless device may support HARQ feedback for the same slot, where the device may provide HARQ feedback in a particular slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

The time interval in LTE or NR can be expressed as a multiple of the basic time unit, which may for example refer to TsA sample period of 1/30,720,000 seconds. The time intervals of the communication resources may be organized according to radio frames each having a duration of 10 milliseconds (ms), where the frame period may be expressed as Tf=307,200Ts. The radio frame may be identified by a System Frame Number (SFN) ranging from 0 to 1023. Each frame may include 10 subframes numbered 0 to 9, and each subframe may have a duration of 1 millisecond. The subframe may be further divided into 2 slots, each slot having a duration of 0.5ms, and each slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). Each symbol period may contain 2048 sample periods in addition to a cyclic prefix. In some cases, a subframe may be the smallest scheduling unit of the wireless communication system 100 and may be referred to as a Transmission Time Interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (e.g., in bursts of a shortened tti (sTTI) or in selected component carriers using sTTI).

In some wireless communication systems, a slot may be further divided into a plurality of minislots containing one or more symbols. In some examples, the symbol of the micro-slot or the micro-slot may be the minimum scheduling unit. For example, the duration of each symbol may vary depending on the subcarrier spacing or operating frequency band. Further, some wireless communication systems may implement time slot aggregation, where multiple time slots or minislots are aggregated together and used for communication between the UE115 and the base station 105.

The term "carrier" refers to a set of radio spectrum resources having a defined physical layer structure for supporting communications over the communication link 125. For example, the carrier of the communication link 125 may comprise a portion of a radio frequency spectrum operating according to physical layer channels for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. The carriers may be associated with predefined frequency channels (e.g., evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute radio frequency channel numbers (EARFCNs)) and may be located according to a channel grid for discovery by UEs 115. The carriers may be downlink or uplink (e.g., in FDD mode), or configured to carry downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted over the carrier may be composed of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or discrete fourier transform spread OFDM (DFT-S-OFDM)).

The organization of the carriers may be different for different radio access technologies (e.g., LTE-A, LTE-A Pro, NR). For example, communication over carriers may be organized according to TTIs or slots, each of which may include user data as well as control information or signaling to support decoding of the user data. The carriers may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling that coordinates the operation for the carriers. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers.

The physical channels may be multiplexed on the carriers according to various techniques. The physical control channels and physical data channels may be multiplexed on the downlink carrier using, for example, Time Division Multiplexing (TDM) techniques, Frequency Division Multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, the control information sent in the physical control channel may be distributed in a cascaded manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

The carrier may be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as a carrier or "system bandwidth" of the wireless communication system 100. For example, the carrier bandwidth may be one of several predetermined bandwidths of the carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each serving UE115 may be configured to operate over part or all of the carrier bandwidth. In other examples, some UEs 115 may be configured for operation using a narrowband protocol type associated with a predefined portion or range within a carrier (e.g., a set of subcarriers or RBs) (e.g., "in-band" deployment of narrowband protocol types).

In a system employing MCM technology, a resource element may consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are 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). Thus, the more resource elements the UE115 receives and the higher the order of the modulation scheme, the higher the data rate of the UE 115. In a MIMO system, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and using multiple spatial layers may further improve the data rate of communications with the UE 115.

Devices of the wireless communication system 100 (e.g., base stations 105 or UEs 115) may have a hardware configuration that supports communication over a particular carrier bandwidth or may be configured to support communication over one carrier bandwidth of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 and a UE115 that support simultaneous communication via carriers associated with more than one different carrier bandwidth.

The wireless communication system 100 may support communication with UEs 115 over multiple cells or carriers, which may be characterized as carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, a UE115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both FDD and TDD component carriers.

In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). An eCC may be characterized by one or more features including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., when more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be utilized by UEs 115 that may not be able to monitor the entire carrier bandwidth or otherwise configured to use a limited carrier bandwidth (e.g., to save power).

In some cases, an eCC may utilize a different symbol duration than other component carriers, which may include using a shortened symbol duration compared to the symbol duration of the other component carriers. Shorter symbol durations may be associated with increased spacing between adjacent subcarriers. A device utilizing an eCC, such as a UE115 or a base station 105, may transmit a wideband signal (e.g., according to a frequency channel or carrier bandwidth of 20, 40, 60, 80MHz, etc.) within a shortened symbol duration (e.g., 16.67 microseconds). A TTI in an eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in a TTI) may be variable.

The wireless communication system 100 may be an NR system that may utilize any combination of licensed, shared, and unlicensed frequency spectrum bands. Flexibility in eCC symbol duration and subcarrier spacing may allow eCC to be used across multiple spectra. In some examples, NR sharing spectrum may improve spectral utilization and spectral efficiency, particularly through dynamic vertical sharing (e.g., across frequency domains) and horizontal sharing (e.g., across time domains) of resources.

In some cases, the wireless communication system 100 may support TB level retransmissions, CBG level retransmissions, code block level retransmissions, or some combination thereof. However, if operating with code block-based or CBG-based retransmissions, the transmission interruption may put pressure on the UE115 processing timeline. For example, the UE115 may interrupt during processing (e.g., encoding) of the TB, and the UE115 may cancel transmission of the TB based on the interrupt. For example, the UE may abort or refrain from processing. This suppression of processing (e.g., due to cancellation) may result in an inaccurate current state of the TB-level parity bits (e.g., CRC bits). That is, based on canceling transmission of the TB (e.g., during initial transmission of the TB), a first subset of code blocks of the TB may be encoded for transmission, while a second subset of code blocks of the TB may be uncoded for transmission. Thus, the current state of the TB-level parity bits may correspond to the encoded first code block subset, rather than the unencoded second code block subset, resulting in an inaccurate set of parity bits with respect to the entire TB.

If the base station 105 requests the UE115 to retransmit a code block that includes TB-level parity bits (or a CBG that contains a code block that includes TB-level parity bits), the UE115 may process the unencoded second subset of code blocks to calculate parity bits for the entire TB. However, if the processing timeline for the retransmission corresponds to the minimum processing timeline for UE115 (e.g., minimum processing timeline N2 for processing and encoding a single code block or CBG for transmission), UE115 may not be able to process the subset of unencoded second code blocks within the allocated processing time. The UE115, the base station 105, or both may implement one or more techniques to handle the TB-level parity bits that are interrupted from being transmitted. In a first technique, the UE115 may modify the code block (e.g., set the TB level parity bits to a common bit value or discard the TB level parity bits from the code block) to reduce processing time. In a second technique, the base station 105 may request retransmission of all preempted code blocks (e.g., all uncoded code blocks, all code blocks of a TB, or an entire TB) to support TB level parity calculations at the UE 115. In a third example, the base station 105 or the UE115 may extend the processing timeline for the retransmission such that the allocated processing time supports TB-level parity calculations at the UE 115.

Fig. 2 illustrates an example of a wireless communication system 200 that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure. The wireless communication system 200 may include a base station 105-a and a UE 115-a, which may be examples of devices described with reference to fig. 1. The base station 105-a may serve the geographic coverage area 110-a described with reference to fig. 1. The UE 115-a may transmit signals to the base station 105-a on an uplink channel 205 (e.g., a Physical Uplink Control Channel (PUCCH), PUSCH, etc.) and may receive signals from the base station 105-a on a downlink channel 210 (e.g., a downlink control channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), etc.). In some cases, the wireless communication system 200 may support retransmission on the uplink channel 205. The UE 115-a, the base station 105-a, or both may perform operations to handle the retransmission request 250 in which the requested information is not ready for transmission.

In some wireless communication systems 200 (e.g., LTE systems, NR systems, or any other system that supports uplink retransmissions), the uplink transmission may support multiple retransmission modes. The first retransmission mode may support TB level retransmission. In TB level retransmission, if reception or decoding of any portion of TB 215 fails at base station 105-a, base station 105-a may request UE 115-a to retransmit the entire TB 215. The second retransmission mode may support CBG level retransmissions, where the CBG may include a plurality of code blocks 220 (e.g., a preconfigured plurality of code blocks 220 or a dynamic number of code blocks 220). In a CBG level retransmission, the base station 105-a may request the UE 115-a to retransmit one or more CBGs, where reception or decoding of at least one code block 220 (or a portion of a code block) fails at the base station 105 a-. In any of these retransmission modes, the base station 105-a may send a retransmission request 250 to the UE 115-a indicating information to retransmit (e.g., TB 215, CBG, code block 220, etc.). The retransmission request 250 may additionally indicate resources for retransmission, and the UE 115-a may send the requested information in the indicated resources. In some cases, the uplink transmission may support additional or alternative retransmission modes. The base station 105-a may operate according to a retransmission mode or may switch between retransmission modes (e.g., based on channel conditions, devices in the system, etc.).

In some cases, the base station 105-a may request a retransmission that interrupts the transmission. For example, the UE 115-a may start transmission (e.g., initial transmission) of the TB 215 on the uplink channel 205 (or, in some examples, on a sidelink channel to another UE 115). The UE 115-a may determine a TB 215 for transmission, where the TB 215 is comprised of a plurality of code blocks 220. These code blocks 220 may be grouped into CBGs of common or different sizes (e.g., two code blocks 220, three code blocks 220, etc.). TB 215 may contain a payload 225 that includes uplink information for transmission. In some cases, the payload 225 may additionally include redundant bits, frozen bits, or a combination thereof to improve decoding reliability at the base station 105-a. The TB payload 225 may be encoded into code blocks 220 for transmission, where each code block 220 may include a portion of the payload 225. In some cases, each code block 220 may additionally include a code block CRC 230. The code block CRC 230 (or code block parity bits) may be determined based on the payload 225 of the particular code block 220. The base station 105-a receiving the code block 220 may decode the payload 225 and the code block CRC 230 and may determine whether the payload 225 is decoded correctly based on the bits of the code block CRC 230 based on the CRC operation. If the decoding operation at the base station 105-a produces a code block payload 225 that is validated by the corresponding code block CRC 230, the base station 105-a can determine that the code block 220 was decoded correctly. Otherwise, the base station 105-a may determine that the decoding process of the code block 220 failed and may request retransmission of the code block 220.

In addition to the code block CRC 230, the UE 115-a may also include a TB CRC 235 in the uplink transmission. Although the code block CRC 230 allows the base station 105-a to determine whether each code block 220 was successfully decoded, the TB CRC 235 may support the base station 105-a in determining whether the entire TB 215 (e.g., the entire set of corresponding code blocks 220) was successfully decoded. Thus, the TB CRC 235 may be based on the bits in each code block 220 of the TB 215. TB CRC 235 may be included in code block 220 of TB 215, such as in the last code block 220 of TB 215 (e.g., code block n of TB including n code blocks). If the CRC operation is a linear function, the UE 115-a may sequentially calculate the TB CRC 235. For example, the UE 115-a may encode the code blocks 220 one by one, updating the state of the TB CRC 235 for each code block 220 before or during encoding. To support low latency operation, the UE 115-a may also transmit the code block 220 concurrently with encoding the TB 215 (e.g., concurrently with processing or encoding other code blocks 220 of the TB 215). As such, since UE 115-a may begin transmitting TB 215 before TB 215 completes encoding, a minimum processing timeline N2 for UE 115-a may be implemented for long TBs 215 (e.g., TB 215 spanning multiple symbols, sub-slots, subframes, etc.).

In one particular example, the UE 115-a may organize the TB 215 into code blocks 220-a, 220-b, 220-c, and 220-d. It should be appreciated that the TB 215 may correspond to any number of code blocks 220 or CBGs (e.g., based on the size of the TB 215, the coding rate used for transmission, etc.). The UE 115-a may process and encode the code block 220 in turn. For example, the UE 115-a may process the code block 220-a, determine a code block CRC 230 for the code block 220-a, update a TB CRC 235 based on the code block 220-a, and encode the code block 220-a for transmission. The UE 115-a may transmit the code block 220-a to the base station 105-a while encoding one or more other code blocks 220 (e.g., code blocks 220-b, 220-c, 220-d, or some combination thereof) of the TB 215. Thus, if the UE 115-a has not been interrupted during transmission, the UE 115-a may sequentially encode the code blocks 220-a, 220-b, 220-c, and 220-d and sequentially transmit the code blocks 220-a, 220-b, 220-c, and 220-d to the base station 105-a. Based on this procedure, the base station 105-a may receive the TB 215 in a code block segment and the sequential processing may reduce the processing time 215 required for the UE 115-a to start transmission of the TB 215 (i.e., start transmission of the first portion of the TB, the code block 220).

However, in some cases, the UE 115-a may be interrupted during the transmission of the TB 215. For example, UE 115-a may receive an interrupt message 240 (e.g., from base station 105-a) that interrupts the initial transmission of TB 215. In some examples, UE 115-a may suspend processing (e.g., encoding) of TB 215 due to interrupt message 240.

In a first example, the abort message 240 may be an example of an uplink grant for the UE 115-a. That is, the UE 115-a may receive a first uplink grant to transmit the TB 215 (e.g., as a first PUSCH message) and then may receive a second uplink grant (i.e., the abort message 240) to transmit a different TB (e.g., as a second PUSCH message). The second uplink grant may be associated with a higher priority or a lower latency than the first uplink grant, or both. For example, the second PUSCH may correspond to ultra-reliable low-latency communication (URLLC), while the first PUSCH may correspond to enhanced mobile broadband (eMBB) communication. The second uplink grant may preempt a number of symbols associated with the first uplink grant. For example, the first uplink grant may indicate a first set of resources for transmission of a first PUSCH message, and the second uplink grant may indicate a second set of resources for transmission of a second PUSCH message, where the second set of resources at least partially overlaps in time with the first set of resources. In this example, to handle intra-UE multiplexing of uplink transmissions by UE 115-a, UE 115-a may suspend processing of the first PUSCH message (e.g., encoding and transmission of first TB 215) to perform processing on the second PUSCH message according to the indicated second set of resources.

In a second example, interrupt message 240 may be a request to UE 115-a to preempt TB 215 transmission over several resources (e.g., using an uplink preemption indicator (ULPI)). The ULPI may indicate a set of time resources (e.g., a number of symbols) over which UE 115-a will refrain from transmitting (e.g., to support inter-UE multiplexing of uplink transmissions). In some cases, the UE 115-a may cancel transmission after the indicated set of resources and may not be able to resume transmission. In these cases, UE 115-a may stop processing TB 215 based on receiving interrupt message 240 sent by preempting TB 215. In other cases, the UE 115-a may resume transmission after the indicated set of resources. In these other cases, UE 115-a may continue processing TB 215 based on receiving interrupt message 240 sent by preempting TB 215, or UE 115-a may temporarily suspend processing and then resume processing of TB 215 based on receiving interrupt message 240 sent by preempting TB 215.

If UE 115-a stops processing TB 215 based on interrupt message 240, UE 115-a may not process or encode all code blocks 220 of TB 215. Thus, UE 115-a may not be able to complete calculating TB CRC 235. For example, the UE 115-a may process the first code block subset 245-a and may update the current state of the TB CRC 235 based on the first code block subset 245-a. If the UE 115-a is interrupted and cancels transmission, the second subset of code blocks 245-b may not be encoded (e.g., not processed for UE 115-a transmission). Thus, after an incomplete encoding process, the TB CRC 235 may indicate the bits included in the first subset of code blocks 245-a but not the second subset of code blocks 245-b.

If the base station 105-a sends a retransmission request 250 to the UE 115-a for a code block 220 (e.g., the last code block 220-d or the last CBG) that includes a TB CRC 235, the UE 115-a may process several code blocks 220 or CBGs to calculate the correct TB CRC 235 for transmission. This may put significant stress on the processing capabilities of the UE 115-a depending on the processing timeline of the retransmitted code block 220-d. For example, if the UE 115-a is scheduled to transmit a code chunk 220-d (or a CBG that includes the code chunk 220-d) according to the minimum processing timeline N2 of the UE 115-a, the minimum processing timeline may be based on the amount of time that the UE 115-a processes and encodes one code chunk 220 or CBG for transmission. However, in order to process and encode for transmission a code block 220 or CBG that includes the correct TB CRC 235 for the entire TB 215, the UE 115-a may process and encode multiple code blocks 220 or CBGs to calculate the TB CRC 235.

To handle TB-level parity bits (e.g., CRC bits) that interrupt transmission, UE 115-a, base station 105-a, or both may implement one or more techniques. In a first example, if UE 115-a is configured for code block-based or CBG-based uplink retransmission and initial TB 215 transmission is preempted, UE 115-a may modify code block 220-d to meet the processing timeline. For example, the UE 115-a may receive a retransmission request 250 indicating at least the code block 220-d including the TB CRC 235. The UE 115-a may identify, based on the interruption, that the current state of the TB CRC 235 corresponds to the encoded first code block subset 245-a (but not the unencoded second code block subset 245-b). Based on this current state not being accurate for the entire TB 215, the UE 115-a may set bits of the TB CRC 235 to a common bit value (e.g., all zero bits, all one bits, etc.) for retransmission. Alternatively, if the initial TB 215 transmission is preempted (e.g., the state of TB CRC 235 is not checked), UE 115-a may set the bits of TB CRC 235 to a common bit value. The UE 115-a may send the code block 220-d to the base station 105-a (e.g., within the last CBG) along with the TB CRC 235, with each TB CRC bit set to a common bit value. In this way, the UE 115-a may not process other unencoded code blocks 220 of the TB 215 in order to transmit the requested code block 220-d, supporting transmission according to a processing timeline. In some cases, such transmission of the code block 220-d based on the retransmission request 250 may be referred to as "retransmission" even if the UE 115-a did not transmit the code block 220-d in the initial transmission of the TB 215 (e.g., based on an interrupt).

In a second example, the UE 115-a may modify the code chunk 220-d to meet the processing timeline by deleting the TB CRC 235. For example, the UE 115-a may identify, based on the interruption, that the current state of the TB CRC 235 corresponds to the encoded first code block subset 245-a (but not the unencoded second code block subset 245-b). Based on the current state not being accurate for the entire TB 215, the UE 115-a may discard the TB CRC 235 from the code block 220-d for retransmission. Alternatively, if the initial TB 215 transmission is preempted (e.g., the status of TB CRC 235 is not checked), the UE 115-a may discard the TB CRC 235 from the retransmission of the code block 220-d. Discarding the TB CRC 235 may allow the UE 115-a to avoid processing other unencoded code blocks 220 of the TB 215 and satisfy the processing timeline for the requested retransmission. In some cases, to discard the TB CRC 235 from the code block 22-0d, the UE 115-a may modify the coding or rate matching procedure, or both, to enable the code block 220-d to support encoding using a different number of bits.

In some cases, UE 115-a may be configured to transmit a portion of an interrupted TB 215 known to base station 105-a. For example, in a first aspect, the UE 115-a may be configured to transmit in all symbols of the allocated set of resources transmitted by the TB 215 until the first preempted symbol begins. In this regard, base station 105-a may monitor and receive portions of TB 215 up to the first preempted symbol. In a second aspect, UE 115-a may determine when to suspend transmission of TB 215 upon receiving interrupt message 240. For example, based on the processing capabilities of UE 115-a and the processing to be performed by UE 115-a, UE 115-a may determine (e.g., based on some algorithm or a preconfigured value at UE 115-a) which symbol to suspend transmission to TB 215, where the first preempted symbol is the deadline of the transmission suspension.

Based on the configuration of the UE 115-a, the UE 115-a may transmit a first code block 220 up to (but not including) TB 215 that is scheduled, at least in part, for transmission within the preempted time resources. In a third example, for code block-based or CBG-based uplink retransmissions in which the initial TB 215 sends an interrupt, the base station 105-a may request that each code block 220 or CBG scheduled for transmission be retransmitted, in whole or in part, within the preempted time resources (e.g., preempted symbols). For example, code block 220-b may be the first sequential code block 220 of TB 215 that is partially or fully preempted by interrupt message 240. Based on the configuration, the UE 115-a may transmit each code block in turn up to (but not including) the code block 220-b (e.g., the UE 115-a may transmit the code block 220-a to the base station 105-a). The base station 105-a may determine to request retransmission from the UE 115-a and, based on the configuration of the UE 115-a, the base station 105-a may request retransmission of each code block 220, in whole or in part, within the preempted symbols. For example, starting with code block 220-b, base station 105-a may request retransmission of the remaining code blocks 220 of TB 215. As such, the UE 115-a may process (e.g., encode) each code block 220 of the second subset of code blocks 245-b for transmission based on the base station 105-a requesting the code block 220 or CBG for retransmission. Based on previously processing each code block 220 in the first code block subset 245-a, the UE 115-a may store a current state (e.g., current value) of the TB CRC 235 computed from the first code block subset 245-a. By processing each code block 220 in the second code block subset 245-b based on the retransmission request 250, the UE 115-a may update the current state of the TB CRC 235 from the second code block subset 245-b such that the TB CRC 235 is calculated from all code blocks 220 in the TB 215. As such, the UE 115-a may prepare the code block 220-d including the TB CRC 235 for transmission according to the processing timeline indicated by the retransmission request 250 (e.g., if each other code block 220 or CBG in the second code block subset 245-b is requested to be retransmitted before the code block 220 or CBG including the TB CRC 235 is retransmitted).

In a fourth example, the base station 105-a may request retransmission of all code blocks 220 or CBGs for the TB 215. For example, the base station 105-a may be configured for code block based or CBG based retransmissions. The base station 105-a may request retransmission of each code block 220 or CBG of the TB 215, such that the UE 115-a retransmits each other code block 220 or CBG of the TB 215 before retransmitting the code block 220 or CBG that includes the TB CRC 235. The requested retransmissions may not be continuously scheduled. For example, the base station 105-a may request retransmission of the code blocks 220-a and 220-b (e.g., a first CBG) in a first retransmission request 250 and may request retransmission of the code blocks 220-c and 220-d (e.g., a second CBG including a TB CRC 235) in a second retransmission request 250. The UE 115-a may transmit the code blocks 220-a and 220-b in a first set of resources and the code blocks 220-c and 220-d in a second set of resources subsequent to the first set of resources, respectively, where the first and second sets of resources may or may not be contiguous in time. In some cases, if UE 115-a determines when to suspend transmission of TB 215, base station 105-a may request retransmission of all code blocks 220 for TB 215. If the base station 105-a cannot identify whether the UE 115-a has processed and transmitted the code blocks 220 up to (but not including) the first code block 220 that is scheduled, at least in part, for transmission within the preempted symbols, the base station 105-a may fall back to requesting retransmission of each code block 220. Alternatively, the base station 105-a may request retransmission of each code block 220 of the TB 215 subsequent to the last code block 220 successfully received at the base station 105-a (e.g., where successful reception is determined based on the code block CRC 230 in the last code block CRC 220).

In a fifth example, if the initial TB 215 transmission is interrupted at the UE 115-a, the base station 105-a may implement TB level retransmission (e.g., instead of code block level or CBG level retransmission). For example, the base station 105-a may send a retransmission request 250 for the TB 215 and the UE 115-a may retransmit the complete TB 215. In this way, the base station 105-a may ensure that the UE 115-a may process (e.g., encode) all code blocks 220 of the TB 215 such that a TB CRC 235 is calculated for the entire TB 215. In some cases, base station 105-a may operate according to a CBG-based retransmission mode of operation, but may fall back to a TB-based retransmission mode of operation if base station 105-a determines to request retransmission of any portion of the interrupted initial TB 215 transmission.

In a sixth example, if preemption is configured on a given serving cell (e.g., a serving cell served by base station 105-a), uplink code block-based or CBG-based retransmissions may not be configured for the same serving cell. As such, the initial TB 215 transmission may be discontinued in cells in which TB-based retransmissions are performed, but may not be discontinued in cells in which code block-based or CBG-based retransmissions are performed. According to this example, in order for base station 105-a to transmit an interrupt message 240, base station 105-a is configured in a TB-based retransmission mode of operation. If base station 105-a discontinues the initial TB 215 transmission, base station 105-a may ensure that UE 115-a may process (e.g., encode) all code blocks 220 of TB 215 such that TB CRC 235 is calculated for the entire TB 215.

In some cases, preemption may affect one or more component carriers in uplink carrier aggregation (e.g., in-band component carriers). For example, if PUSCH transmissions are preempted on a first component carrier, the same symbols may be preempted by PUSCH transmissions on other component carriers. In one example, if the UE 115-a may continue to make the initial TB 215 transmission on the component carrier after the set of preempted symbols, the UE 115-a may not send out PUSCH information in the preempted symbols on the component carrier, and if there is a PUSCH transmission on other components, the same symbols may be preempted by other PUSCH transmissions. However, PUSCH transmission on any component carrier may be resumed after the preempted symbol set. In another example, if the UE 115-a cannot continue to continue the initial TB 215 transmission on the component carrier after the set of preempted symbols, the UE 115-a may abort (e.g., cancel) the PUSCH transmission at the beginning of the preempted symbols on the component carrier, and if there is a PUSCH transmission on other component carriers, other PUSCH transmissions may be preempted instead of continuing to start from the same symbols. Furthermore, preemption rules similar to those described herein with respect to PUSCH transmissions on other component carriers may be applied to PUSCH transmissions on other serving cells based on preemption on one cell.

In a seventh example, base station 105-a, UE 115-a, or both may modify the processing timeline to support code block-based or CBG-based retransmissions of interrupted TB 215 transmissions. For example, if the base station 105-a requests retransmission of a code block 220-d or a CBG that includes a TB CRC 235, the processing timeline for retransmitting the code block 220-d or CBG may extend d time resources (e.g., symbols). In some cases, the base station 105-a may indicate resources for retransmission in the retransmission request 250 based on extending the minimum processing timeline N2 for UE 115-a by timeline extension d. This timeline extension may support the UE 115-a processing at least the second subset of code blocks 245-b and determining the TB CRCs 235 of all code blocks 220 of the TB 215 in time to send the code blocks 220-d or CBGs including the TB CRCs 235 in the indicated resources. In other cases, the base station 105-a and the UE 115-a may identify a timeline extension d such that the UE 115-a may process at least the second subset of code blocks 245-b in time to transmit the code blocks 220-d or CBGs including the TB CRCs 235 in resources based on the identified timeline extension. The base station 105-a may monitor for retransmissions based on the identified timeline extension.

In some examples, the length of the timeline extension d may be preconfigured at the base station 105-a, the UE 115-a, or both. In other examples, the length of the timeline extension d may be dynamically determined based on the number of code blocks in the second subset of code blocks 245-b, the length of the TB 215, the processing power of the UE 115-a, or some combination of these or other variables related to the UE 115-a for calculating the TB CRC 235. For example, the value of d may be a subcarrier spacing that is dependent on or based on the processing timeline capability of UE 115-a (e.g., d may be different for UEs 115 capable of following PUSCH preparation timing capability #1 than for UEs 115 capable of following PUSCH preparation timing capability # 2).

In some cases (e.g., if the initial TB 215 transmission is interrupted by replacing some portion of the PUSCH with another, more urgent PUSCH), the base station 105-a, the UE 115-a, or both may modify the processing timeline for the more urgent PUSCH. Similar to the above, UE 115-a may transmit a more urgent PUSCH (e.g., the second TB corresponding to a URLLC transmission) according to a processing timeline that includes a minimum processing timeline for the more urgent PUSCH and a timeline extension d (which may be pre-configured or calculated as described herein). During the timeline extension, UE 115-a may complete processing of code block 220 of TB 215-and in some cases, complete transmission. In this way, the current state of TB CRC 235 can be calculated for the entire TB 215 even if the initial TB 215 transmission is preempted.

It should be understood that the wireless communication system 200 may implement any combination of the examples described herein. For example, UE 115-a, base station 105-a, or both may perform any combination of the above operations to support handling the TB-level parity bits that interrupt transmission.

Fig. 3 illustrates an example of an encoding process 300 that supports handling TB-level parity bits for interrupted transmission, in accordance with aspects of the present disclosure. The encoding process 300 may be performed by a UE, such as the UE115 described with reference to fig. 1 and 2. The encoding process 300 may support sequential processing of code blocks 310 of a TB 305, allowing code blocks 310 to be transmitted and processed simultaneously within the TB 305. Based on the encoding process 300, the initial TB 305 transmission may be interrupted in the middle of processing, as described with reference to fig. 2.

In the encoding process 300, the TB 305 may be partitioned into code blocks 310, where the code blocks 310 may be buffered (i.e., loaded) in an encoding input buffer 315. These code blocks 310 may be passed one-by-one into a code block CRC/TB CRC calculator 330 (e.g., within the encoder 325). Here, the encoder 325 may calculate a code block CRC of the code block 310 and may attach the code block CRC to the code block 310. In addition, the encoder 325 may update the status of the TB CRC (i.e., the TB CRC code) based on the code block 310, the code block CRC, or both. Since the CRC operation may be an example of a linear function with respect to an exclusive or (XOR) function (i.e., CRC (a XOR B) ═ CRC (a) XOR CRC (B)), the TB CRCs may be computed sequentially using one code block 310 at a time (e.g., rather than computing the TB CRCs once). This may improve transmission latency because UE115 may process and transmit other portions of TB 305 before or while processing other portions of TB 305.

In some cases, after the code block CRC/TB CRC calculator 330, the code block 310 may pass to a Low Density Parity Check (LDPC) calculator 335, which may calculate and append an LDPC code to the code block 310. Additionally or alternatively, the code block 310 may be issued to a rate matcher 340, which may perform rate matching on the code block 310 to determine the code block 310 for transmission (e.g., according to a particular codeword size). After rate matching, the code block 310 may be loaded into the coded output buffer 345. The wave generator 350 (e.g., and antenna) may retrieve the encoded code blocks 310 from the encoded output buffer 345 and transmit the encoded code blocks 310 according to a scheduler (e.g., where the code blocks 310 are transmitted in resources scheduled for TB 305 transmission). In some examples, the code blocks 310 are sent in groups (e.g., CBGs). Based on the sequential nature of the encoding process 300, one or more code blocks 310 may be transmitted while processing other code blocks 310 or before processing other code blocks 310. For example, the UE115 may send the first code block 310-a while processing the code blocks 310-b and 310-c and before processing the other code blocks 310-d through 310-n. The buffer pointer 320 may track the processing within the encoded input buffer 315.

If the processing of TB 305 is interrupted and the base station 105 receiving TB 305 fails to decode one or more code blocks 310 or CBGs, the base station 105 may request the UE115 to retransmit the one or more code blocks 310 or CBGs. If the last code block 310-n or the last CBG containing the last code block 310-n is requested and the last code block 310-n is to include a TB CRC, the UE115 may prepare the TB CRC for retransmission of that code block 310-n. The UE115, the base station 105, or both may perform any combination of the techniques described with reference to fig. 2 to support retransmission of the code block 310-n containing the TB CRC.

Fig. 4A, 4B, and 4C illustrate an example of a processing timeline 400 that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure. Fig. 4A shows an example of a processing timeline 400-a for TB 415 (e.g., initial transmission). For example, a UE (e.g., UE115 as described with reference to fig. 1-3) may receive PDCCH transmission 405 granting resources for uplink transmission of TB 415. PDCCH transmission 405 may indicate resources based on a minimum processing timeline 410 of UE115 or may indicate the minimum processing timeline 410 itself. In some cases, the minimum processing timeline 410 may be based on a processing time for the UE115 to prepare one code block 420 or one CBG for transmission, rather than a processing time for the UE115 to prepare a full TB 415 for transmission. For example, based on an encoding process (e.g., the encoding process 300 described with reference to fig. 3), the UE115 may process and encode the code block 420-a for transmission according to the processing timeline 410 before processing and encoding the code block 420-n (e.g., the last code block 420 of the TBs 415, which contains the set of parity bits for the TBs 415) for transmission. However, due to the length of the TB 415 and the encoding process, the code block 420-n may be ready in time for transmission of the code block 420-n with the correctly calculated set of parity bits (e.g., TB CRC bits) for the TB 415.

FIG. 4B shows an example of a processing timeline 400-B for code block-based or CBG-based retransmissions. Since the minimum processing timeline 410 may be based on the processing time for a UE115 to prepare one code chunk 420 or one CBG for transmission, the same minimum processing timeline 410 may be used for initial transmission and retransmission. Thus, if a base station (e.g., base station 105 described with reference to fig. 1-3) requests retransmission of unprocessed (e.g., unencoded) code blocks 420, the minimum processing timeline 410 may support the UE115 to process and encode the requested code blocks 420 in time to send the requested code blocks 420 in the indicated resources. However, if processing and encoding the requested code block 420 involves processing and encoding additional code blocks 420, the minimum processing timeline 410 may not allow the UE115 sufficient time to prepare the code blocks 420 for transmission. For example, if the base station 105 requests retransmission of a code block 420-n containing a set of parity bits for a TB 415, and the UE115 has multiple uncoded code blocks 420 that have not yet been the basis of the current state of the set of parity bits for the TB 415, the UE115 may implement one or more techniques to follow the minimum processing timeline 410 and complete encoding of the code blocks 420-n in time for transmission. For example, in some examples, the UE115 may set each bit of the set of parity bits for the TB 415 to a common bit value or may completely discard the set of parity bits for the TB 415 from the code block 420-n, allowing the UE115 to avoid processing other un-encoded code blocks 420 of the TB 415.

Fig. 4C shows an example of a processing timeline 400-C for code block-based or CBG-based retransmission with timeline extension 425. As discussed above with reference to fig. 4B, if the base station 105 requests retransmission of a code block 420-n containing the parity bit set of the TB 415, and the UE115 has one or more other uncoded code blocks 420 that are not reflected in the current state of the parity bit set of the TB 415, the UE115 may not be able to satisfy the minimum processing timeline 410 of the code block 420-n due to the calculation of the parity bit set for the TB 415. In some cases, to support computing the parity bit set for TB 415, the code block 420-n may be retransmitted in the resource based on the modified processing timeline. For example, a first time resource for transmitting the code block 420-n may be determined by adding a timeline extension 425 to the minimum processing timeline 410 for the UE 115. The timeline extension 425 may be a configuration value or may be calculated based on the number of code blocks 420 that are preempted or not encoded, the number of code blocks 420 in the TB 415, the processing power of the UE115, or some combination thereof. In some cases, the base station 105 may determine a modified processing timeline and may indicate corresponding resources for retransmission of the code block 420-n in the PDCCH transmission 405 (i.e., retransmission request). In other cases, the UE115 may determine a modified processing timeline and may retransmit the code chunk 420-n in a resource corresponding to the modified processing timeline. In these other cases, the base station 105 can additionally determine a modified processing timeline and receive the retransmission in a resource corresponding to the modified processing timeline.

Fig. 5 illustrates an example of a process flow 500 supporting handling of TB-level parity bits for interrupted transmission in accordance with aspects of the present disclosure. Process flow 500 may illustrate exemplary operations to support retransmission of a code block including TB parity bits. For example, the UE 115-b may be interrupted during processing (e.g., encoding) of the TB for transmission, and the base station 105-b may request the UE 115-b to retransmit at least a portion of the TB. UE 115-b and base station 105-b may be examples of corresponding wireless devices described with reference to fig. 1-4. The following alternative examples may be implemented in which some steps are performed in a different order than described or not performed at all. In some cases, the steps may include other features not mentioned below, or additional steps may be added.

At 505, the UE 115-b may begin sequentially encoding TBs for transmission, where the TBs comprise a set of code blocks. The UE 115-b may process and encode the first subset of code blocks of the TB for transmission. This process may involve iteratively updating the current state of the parity bit set (e.g., CRC bits) of the TB on a per code block basis. In some cases, at 510, the UE 115-b may transmit the first subset of code blocks to the base station 105-b.

At 515, the UE 115-b may receive an interrupt message. In some cases, the UE 115-b may receive an interrupt message from the base station 105-b. In a first example, the interrupt message may indicate authorization for a transmission having a higher priority than the TB in resources previously reserved for TB transmissions. In a second example, the interrupt message may instruct UE 115-b to refrain from transmitting in a portion of resources previously reserved for TB transmission. At 520, UE 115-b may cancel transmission of the TB (e.g., abort the encoding, refrain from processing, or both) based on the abort message. For example, transmission may be cancelled during initial transmission such that a first subset of code blocks is encoded but a second subset of code blocks of the TB is not encoded for transmission. Thus, the set of parity bits for the TB may not be based on the second code block subset. In some cases, at 525, the base station 105-b may determine that transmission of the second subset of code blocks is preempted.

At 530, the base station 105-b may send a retransmission request to the UE 115-b. In some cases, the message may request retransmission of a code block in the second subset of code blocks that includes a set of parity bits for the TB. At 535, the UE 115-b may modify the code block including the set of parity bits for transmission based on the interrupted initial TB transmission. For example, in some cases, the UE 115-b may determine, based on the cancelled transmission procedure, that the current state of the set of parity bits of the TB corresponds to a first code block subset (e.g., but not a second code block subset). Based on the determination, the UE 115-b may modify the code block. In some examples, UE 115-b may set each bit of the parity bit set of the TB to a common bit value (e.g., "0"). In other examples, the UE 115-b may delete the set of parity bits for the TB from the code block.

In other cases, the message may request retransmission of at least the second subset of code blocks. For example, the retransmission request may request retransmission of the second subset of code blocks, all code blocks of a TB, or a TB. At 540, the UE 115-b may process (e.g., encode) the requested code block (or TB) for transmission. Based on this procedure, the UE 115-b may update the state of the parity bits of the TB such that the parity bits are based on the second code block subset (i.e., all code blocks of the TB block) in addition to the first code block subset.

At 545, the UE 115-b may retransmit the requested information (e.g., the requested code block(s), CGB(s), TB(s), or some combination thereof) based on handling TB level parity bits for the interrupted transmission.

Fig. 6 illustrates an example of a process flow 600 supporting handling of TB-level parity bits for interrupted transmission in accordance with aspects of the present disclosure. Process flow 600 may illustrate exemplary operations to support retransmission of a code block including TB parity bits. For example, the UE 115-c may be interrupted during processing (e.g., encoding) of the TB for transmission, and the base station 105-c may request the UE 115-c to retransmit at least a portion of the TB. The UE 115-c and the base station 105-c may be examples of corresponding wireless devices described with reference to fig. 1-4. The following alternative examples may be implemented in which some steps are performed in a different order than described or not performed at all. In some cases, the steps may include other features not mentioned below, or additional steps may be added. Further, the UE 115-c, the base station 105-c, or both may additionally or alternatively perform the operations described with respect to fig. 5.

At 605, the UE 115-c may begin sequentially encoding TBs for transmission, where the TBs comprise a set of code blocks. The UE 115-c may process and encode the first subset of code blocks of the TB for transmission. This process may involve iteratively updating the current state of the parity bit set (e.g., CRC bits) of the TB on a per code block basis. In some cases, at 610, the UE 115-c may transmit a first subset of code blocks to the base station 105-c.

At 615, the UE 115-c may receive an interrupt message. In some cases, the UE 115-c may receive an interrupt message from the base station 105-c. At 620, the UE 115-c may cancel transmission of the TB (e.g., abort the encoding, refrain from processing, or both) based on the abort message. For example, transmission may be cancelled during initial transmission of the TB such that the first subset of code blocks is encoded but a second subset of code blocks of the TB is not encoded for transmission (e.g., the remaining code blocks in the TB other than the first subset of code blocks). Thus, the set of parity bits for the TB may not be based on the second code block subset. In some cases, the base station 105-c may determine that transmission of the second subset of code blocks is preempted at 625.

The base station 105-c or the UE 115-c may modify the processing timeline for the retransmission request based on the interrupted initial transmission. In some cases, at 630, the base station 105-c may generate a retransmission request message, where the retransmission request message indicates resources for transmission of a code block (e.g., a code block including a set of parity bits for a TB) based on the UE's processing timeline and the preempted second subset of code blocks. At 635, the base station 105-c may send a retransmission request message to the UE 115-c.

In some cases, at 640, the UE 115-c may modify the processing timeline based on the second subset of code blocks not being encoded for transmission. In other cases, the UE 115-c may use the resources indicated in the retransmission request, where the resources are determined using the modified processing timeline. At 645, the UE 115-c may process (e.g., encode) the second subset of code blocks based on the modified processing timeline. For example, due to the timeline lengthening, UE 115-c may have time to further calculate the parity bit set for the TB based on the second code block subset such that the parity bit set for the TB indicates the correct values for all code blocks of the TB. At 650, the UE 115-c may transmit a code block including the calculated set of TB parity bits based on the retransmission request message.

Fig. 7 illustrates an example of a process flow 700 supporting handling TB-level parity bits for interrupted transmission according to aspects of the present disclosure. Process flow 700 may illustrate exemplary operations in support of scheduling uplink transmissions such that the uplink transmissions do not overlap in time with preempted resources of another uplink grant. For example, the UE115-d may be interrupted during processing (e.g., encoding) of the TB for a first PUSCH transmission, and the base station 105-d may schedule an additional uplink grant for a second PUSCH transmission for a different symbol than the preempted symbol of the first PUSCH. The UE115-d and the base station 105-d may be examples of corresponding wireless devices described with reference to fig. 1-4. The following alternative examples may be implemented in which some steps are performed in a different order than described or not performed at all. In some cases, the steps may include other features not mentioned below, or additional steps may be added. Further, the UE115-d, the base station 105-d, or both may additionally or alternatively perform the operations described with respect to FIGS. 5 and 6.

At 705, the base station 105-d may transmit and the UE115-d may receive a first grant of a first set of resources for a first uplink transmission. At 710, the base station 105-d may transmit, and the UE115-d may receive, a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission. In some cases, the second grant may be referred to as an interrupt message because the grant may schedule preemption of the transmission of the first uplink transmission (i.e., the second uplink transmission). At 715, the UE115-d may cancel transmission of the TB associated with the first uplink transmission based on receiving the second grant. For example, due to the cancellation of the transmission, a first subset of code blocks of the TB is encoded for transmission, while a second subset of code blocks of the TB is not encoded for transmission.

At 720, the base station 105-d may schedule a third set of resources (e.g., preempted resources of the first set of resources) for a third uplink transmission according to a non-overlapping condition between the third set of resources and the first set of resources. The non-overlapping condition may be specific to a priority level or may be used for any transmission. Based on the non-overlapping condition, the base station 105-d may schedule the third set of resources in symbols that do not overlap with any preempted symbols of the first set of resources (e.g., symbols preempted due to the scheduled second uplink transmission). In some cases, the third uplink transmission may be a retransmission of the first uplink transmission (or a portion of the first uplink transmission).

At 725, the base station 105-d may transmit and the UE115-d may receive a third grant of a third set of resources for a third uplink transmission (e.g., based on scheduling at the base station 105-d). At 730, the UE115-d may identify a non-overlapping condition between the third set of resources and the first set of resources. For example, the non-overlapping condition implemented at the UE115-d may be the same as the non-overlapping condition implemented at the base station 105-d. For example, the UE115-d may determine whether the third set of resources partially overlaps in time with the first set of resources (e.g., preempts resources of the first set of resources). At 735, the UE115-d may process the third grant based on identifying the non-overlapping condition.

In a first example, the UE115-d may identify the third grant as erroneous if the third set of resources and the first set of resources at least partially overlap in time. In a second example (e.g., if the non-overlapping condition is priority-specific), if the third set of resources and the first set of resources overlap in time at least partially, but the third uplink transmission and the first uplink transmission correspond to different priorities, the UE115-d may encode a TB for the first uplink transmission based on a first uplink transmission corresponding to the first priority using the first processing block and encode an additional TB for a third uplink transmission corresponding to a second priority different from (e.g., higher than) the first priority (e.g., while encoding the TB) using the second processing block. During time resources that at least partially overlap with the first set of resources, the UE115-d may transmit and the base station 105-d may receive a third uplink transmission (e.g., based on parallel processing at the UE 115-d). In some cases, the UE115-d may send an indication of the number of Component Carriers (CCs) supporting each priority level (e.g., first priority and second priority). In a third example (e.g., if the non-overlapping condition is priority-specific), the UE115-d may identify the third grant as erroneous if the third set of resources and the first set of resources overlap at least partially in time and the third uplink transmission and the first uplink transmission correspond to the same priority.

In some particular embodiments, the UE115-d may receive a first Downlink Control Information (DCI) message (i.e., a first grant at 705) scheduled for a first PUSCH transmission to the base station 105-d. If the first PUSCH transmission is interrupted at the UE115-d (e.g., by the second grant at 710), the UE115-d may not receive either another DCI message (e.g., corresponding to the same or a different HARQ process) or a preempted symbol that schedules another PUSCH transmission. For example, the UE115-d may determine an uplink grant for a first PUSCH transmission, where the UE115-d is granted a set of symbols (e.g., slots, such as symbols 0 through 13) to transmit the first PUSCH transmission. If this first PUSCH transmission is preempted after a particular symbol (e.g., symbol 2), UE115-d may not receive a request (e.g., the third grant at 725) on the same carrier for another PUSCH transmission on a subset of remaining symbols (e.g., preempted symbols 3 through 13). For example, the base station 105-d may identify a preempted symbol for a first PUSCH transmission at the UE115-d and may schedule additional PUSCH transmissions in non-preemptive symbols (e.g., symbols after the preempted symbol). If the UE115-d receives a DCI message with an uplink grant that schedules a PUSCH transmission in at least one preemption symbol, the UE115-d may determine that the uplink grant is erroneous and may ignore the uplink grant (e.g., refrain from processing the uplink grant, refrain from encoding the corresponding PUSCH message, refrain from transmitting the corresponding PUSCH message, etc.).

In some cases, the UE115-d may manage transmissions corresponding to different priorities or priority levels. For example, the UE115-d may manage high priority transmissions and low priority transmissions (e.g., relative to high priority transmissions). In some examples, the UE115-d may use a Carrier Aggregation (CA) framework-or a framework similar to the CA framework-to indicate the UE's ability to handle different priority PUSCH messages. For example, for band combining, the UE115-d may indicate to the base station 105-d the number of CCs supporting low priority PUSCH and the number of CCs supporting high priority PUSCH on a per band basis. Depending on such UE capabilities, the UE115-d may support handling different priority channels separately. For example, the UE115-d may be able to process a low priority PUSCH channel separately from a high priority PUSCH channel. The priority of PUSCH transmission may be indicated at the Physical (PHY) layer based on a bit or bit field in the DCI, a Radio Network Temporary Identifier (RNTI), a particular DCI format or size, a particular set of control resources (CORESET), or a set of search spaces, or a combination thereof. Additionally or alternatively, the priority of PUSCH transmission may be indicated at the MAC layer as a result of Logical Channel (LCH) prioritization.

If the first PUSCH transmission is interrupted at the UE115-d (e.g., the UE115-d cancels or suspends encoding and transmission of the first PUSCH transmission at 715 based on the second PUSCH transmission or some other interrupt signal), the UE115-d may not receive another DCI message scheduling another PUSCH transmission (e.g., corresponding to the same or a different HARQ process) on any of the preempted symbols when the first PUSCH transmission and the other PUSCH transmission have the same priority. For example, if a low priority PUSCH transmission is preempted at UE115-d (e.g., based on a high priority PUSCH transmission), UE115-d may not be scheduled with a second low priority PUSCH transmission in the preempted symbols of a first low priority PUSCH transmission. However, if the low priority PUSCH is preempted and the UE115-d receives a grant to transmit the high priority PUSCH in a preempted symbol, the UE115-d may perform processing and transmission of the high priority PUSCH based on the UE115-d using different processing blocks for processing different priority channels. For example, the UE115-d may continue to process high priority PUSCHs (e.g., encode TBs for high priority PUSCHs) while continuing to process low priority PUSCHs (e.g., preempted PUSCHs). This simultaneous processing may allow for support of priority-based non-overlapping conditions at the UE115-d, the base station 105-d, or both. In this way, the UE115-d may obtain CRC bits for the TBs of the low priority PUSCH (e.g., without significant delay) as long as the base station 105-d does not request another low priority PUSCH overlapping with the same original low priority PUSCH resources. The base station 105-d may perform (e.g., at 720) uplink grant scheduling to satisfy a non-overlapping condition (e.g., based on PUSCH priority or independent of PUSCH priority) at the UE 115-d.

Fig. 8 illustrates a block diagram 800 of an apparatus 805 that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure. The device 805 may be an example of aspects of a UE115 as described herein. The device 805 may include a receiver 810, a communication manager 815, and a transmitter 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to handling TB-level parity bits for interrupt transmission, etc.). Information may be passed to other components of device 805. The receiver 810 may be an example of aspects of the transceiver 1120 described with reference to fig. 11. Receiver 810 may utilize a single antenna or a set of antennas.

In one embodiment, the communication manager 815 may: canceling transmission of a TB comprising a set of code blocks, wherein a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; determining, based on the cancellation, that a current state of a set of parity bits for the TB corresponds to the first code block subset (e.g., but not to the second code block subset); modifying a code block comprising a set of parity bits for the TB based on the determination; and transmitting the modified code block based on the retransmission request. This embodiment may be used to reduce processing latency at the UE115, as the UE115 may avoid processing one or more code blocks in the encoder. In addition, this embodiment may reduce computational complexity at the UE115, as the UE115 may avoid computing the parity bit set for the TB.

Further, based on modifying the code block including the set of parity bits for the TB, the processor of the UE115 (e.g., the control receiver 810, the communication manager 815, and/or the transmitter 820) may reduce the processing resources required to prepare the code block for retransmission. In some cases, the encoder may reduce the number of code blocks to process, thereby reducing the power required to prepare code blocks at the encoder for retransmission.

Additionally or alternatively, in another embodiment, the communication manager 815 may cancel transmission of a TB including a set of code blocks, wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation; encoding the second subset of code blocks for transmission based on the modified processing timeline; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; modifying the processing timeline based on the second subset of code blocks not being encoded for transmission; and transmitting the code block based on the retransmission request and encoding the second subset of code blocks for transmission. This embodiment may be used to improve the reliability of the UE115 transmissions, as the UE115 may process information in time to transmit within the allocated resources. This may reduce signaling overhead in the system, as the number of retransmissions for the UE115 may be reduced.

Further, based on modifying the processing timeline, a processor of UE115 (e.g., control receiver 810, communication manager 815, and/or transmitter 820) may efficiently use processing resources to prepare a code block for retransmission. For example, the modified processing timeline may reduce the instantaneous processing overhead at the processor, extending processing operations over a longer period of time.

The communication manager 815 may be an example of aspects of the communication manager 1110 described herein. The communication manager 815 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or in any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 815 or its subcomponents may be controlled by a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

The communication manager 815, or subcomponents thereof, may be physically located at various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 815, or subcomponents thereof, may be separate and distinct components in accordance with various aspects of the present disclosure. In some examples, the communication manager 815, or subcomponents thereof, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in accordance with the present disclosure, or combinations thereof, in accordance with various aspects of the present disclosure.

The transmitter 820 may transmit signals generated by other components of the device 805. In some examples, the transmitter 820 may be collocated with the receiver 810 in a transceiver module. For example, the transmitter 820 may be an example of aspects of the transceiver 1120 described with reference to fig. 11. The transmitter 820 may utilize a single antenna or a set of antennas.

Fig. 9 illustrates a block diagram 900 of a device 905 that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure. The device 905 may be an example of aspects of the device 805 or the UE115 as described herein. The device 905 may include a receiver 910, a communication manager 915, and a transmitter 950. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to handling TB-level parity bits for interrupt transmission, etc.). Information may be passed to other components of device 905. The receiver 910 may be an example of aspects of the transceiver 1120 described with reference to fig. 11. Receiver 910 may utilize a single antenna or a set of antennas.

The communication manager 915 may be an example of aspects of the communication manager 815 as described herein. The communication manager 915 may include an encoder 920, a retransmission request component 925, a CRC status component 930, a code block modification component 935, a retransmission component 940, and a timeline modification component 945. The communication manager 915 may be an example of aspects of the communication manager 1110 described herein.

In some cases, the encoder 920 may cancel transmission of a TB that includes a set of code blocks, where a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation. A retransmission request component 925 may receive a retransmission request for the code block in the second subset of code blocks that includes the set of parity bits for the TB. The CRC status component 930 may determine, based on the cancellation, that the current state of the set of parity bits for the TB corresponds to the first code block subset. Code block modification component 935 may modify a code block that includes a set of parity bits for the TB based on the determination. The retransmission component 940 can transmit the modified code block based on the retransmission request.

In some other cases, the encoder 920 may cancel transmission of a TB that includes a set of code blocks, where a first subset of code blocks in the set of code blocks are encoded for transmission and a second subset of code blocks in the set of code blocks are not encoded for transmission based on the cancellation. A retransmission request component 925 may receive a retransmission request for the code block in the second subset of code blocks that includes the set of parity bits for the TB. The timeline modification component 945 can modify the processing timeline based on the second subset of code blocks not being encoded for transmission. The encoder 920 may encode the second subset of code blocks for transmission based on the modified processing timeline. A retransmission component 940 may transmit the code block based on the retransmission request and encode the second subset of code blocks for transmission.

Transmitter 950 may transmit signals generated by other components of device 905. In some examples, the transmitter 950 may be collocated with the receiver 910 in a transceiver module. For example, the transmitter 950 may be an example of aspects of the transceiver 1120 described with reference to fig. 11. The transmitter 950 may utilize a single antenna or a set of antennas.

Fig. 10 illustrates a block diagram 1000 of a communication manager 1005 supporting handling of TB-level parity bits for interrupted transmission, in accordance with aspects of the present disclosure. The communication manager 1005 may be an example of aspects of the communication manager 815, the communication manager 915, or the communication manager 1110 described herein. The communication manager 1005 may include an encoder 1010, a retransmission request component 1015, a CRC status component 1020, a code block modification component 1025, a retransmission component 1030, a CRC modifier 1035, a CRC discard component 1040, a preemption component 1045, a transmission component 1050, a timeline modification component 1055, a timeline extension component 1060, a CRC calculator 1065, a reception component 1070, a non-overlapping condition component 1075, or a combination thereof. Each of these modules may communicate with each other, directly or indirectly (e.g., via one or more buses).

In a first embodiment, the encoder 1010 may cancel transmission of a TB that includes a set of code blocks, wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation.

The retransmission request component 1015 may receive a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB. The CRC status component 1020 may determine, based on the cancellation, that the current state of the set of parity bits for the TB corresponds to the first code block subset. In some cases, the set of parity bits is a set of CRC bits.

A code block modifying component 1025 may modify a code block that includes a set of parity bits for the TB based on the determination. In some examples, the modification may involve CRC modifier 1035 setting each bit of the set of parity bits for the TB to a common bit value based on the determination. In some cases, the common bit value is a zero bit value or a one bit value. In some other examples, the modification involves the CRC discard component 1040 removing the set of parity bits for the TB from the code block based on the determination. The modification may involve the CRC discard component 1040 rate matching the code block based on removing the set of parity bits for the TB from the code block.

The retransmission component 1030 can transmit the modified code block based on the retransmission request.

Preemption component 1045 may receive a message preempting the transmission of the TB, wherein the cancellation is based on receiving the message. In some cases, the transmission of the TB is based on a first grant, and the message preempting the transmission of the TB includes a second grant for a second transmission overlapping at least one time resource of the first grant. In some cases, the transmission of the TB is based on a first grant, and the message preempting the transmission of the TB requests the UE to refrain from transmitting in at least one time resource of the first grant.

Transmitting component 1050 may transmit the first subset of code blocks for the TB based on the first subset of code blocks being encoded for transmission. In some cases, the transmission of the first subset of code blocks is part of the UE's initial transmission of the TB.

In a second embodiment, the encoder 1010 may cancel transmission of a TB that includes a set of code blocks, wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation. The retransmission request component 1015 may receive a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB.

The timeline modifying component 1055 may modify the processing timeline based on the second subset of code blocks not being encoded for transmission. In some examples, modifying the processing timeline may involve the timeline modification component 1055 modifying the processing timeline for transmitting the code chunks based on the retransmission requests. Modifying the processing timeline may involve timeline extension component 1060 determining the timeline extension based on the second subset of code blocks not being encoded for transmission; and adding the timeline extension to the processing timeline to determine the modified processing timeline. In some cases, the timeline extension is a configuration value. In some other cases, the timeline extension component 1060 can calculate the timeline extension based on a number of code blocks in the second subset of code blocks, a length of the TB, or a combination thereof.

The encoder 1010 may encode the second subset of code blocks for transmission based on the modified processing timeline. A retransmission component 1030 may transmit the code block based on the retransmission request and encode the second subset of code blocks for transmission.

In some cases, preemption component 1045 may receive a message including authorization for the second transmission, where the cancellation is based on the authorization for the second transmission. In some of these cases, modifying the processing timeline involves preempting component 1045 modifying the processing timeline for the second transmission based on the second subset of code blocks not being encoded for transmission.

The CRC calculator 1065 may calculate a set of parity bits for the TB based on encoding the second subset of code blocks for transmission.

In a third implementation, receiving component 1070 may receive a first grant for a first set of resources for a first uplink transmission and receive a second grant for a second set of resources for a second uplink transmission, wherein the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission. The encoder 1010 may cancel transmission of a TB including the set of code blocks based on receiving the second grant, wherein the TB is associated with the first uplink transmission, and wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation.

Receiving component 1070 may receive a third grant of a third set of resources for a third uplink transmission. The non-overlapping condition component 1075 may identify a non-overlapping condition between the third set of resources and the first set of resources and may process the third grant based on identifying the non-overlapping condition.

In some cases, the non-overlapping condition component 1075 may determine that the third set of resources and the first set of resources at least partially overlap in time and may identify a third grant for the third set of resources as an error.

In some cases, the non-overlapping condition component 1075 may determine that the third set of resources and the first set of resources at least partially overlap in time. The encoder 1010 may encode the TB for the first uplink transmission based on the first uplink transmission corresponding to a first priority using a first processing block, and may encode an additional TB for the third uplink transmission based on the third uplink transmission corresponding to a second priority different from the first priority using a second processing block. In some examples, encoding the TB is performed at least partially concurrently with encoding the additional TBs. Transmitting component 1050 can transmit the third uplink transmission during a time resource that at least partially overlaps with the first set of resources. In some cases, sending component 1050 may send an indication of the number of CCs used to support uplink transmission of a first priority and may send an indication of the number of CCs used to support uplink transmission of a second priority.

Fig. 11 shows a diagram of a system 1100 that includes a device 1105 supporting handling TB level parity bits for interrupt transmission in accordance with aspects of the present disclosure. Device 1105 may be an example of or include a component of device 805, device 905, or UE115 described herein. Device 1105 may include components for bi-directional voice and data communications, including components for sending and receiving communications, including a communications manager 1110, an I/O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140. These components may communicate electronically over one or more buses, such as bus 1145.

The communication manager 1110 may cancel transmission of a TB including a set of code blocks, wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; determining, based on the cancelling, that a current state of a set of parity bits for the TB corresponds to the first code block subset; modifying a code block comprising a set of parity bits for the TB based on the determination; and transmitting the modified code block based on the retransmission request.

Additionally or alternatively, communication manager 1110 may cancel transmission of a TB that includes a set of code blocks, wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation; encoding the second subset of code blocks for transmission based on the modified processing timeline; receiving a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB; modifying the processing timeline based on the second subset of code blocks not being encoded for transmission; and transmitting the code block based on the retransmission request and encoding the second subset of code blocks for transmission.

I/O controller 1115 may manage input and output signals of device 1105. I/O controller 1115 may also manage peripheral devices that are not integrated into device 1105. In some cases, I/O controller 1115 may represent a physical connection or port to an external peripheral device. In some cases, I/O controller 1115 may utilize a signal such as Such as an operating system or another known operating system. In other cases, I/O controller 1115 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I/O controller 1115 may be implemented as part of a processor. In some cases, a user may interact with device 1105 via I/O controller 1115 or via hardware components controlled through I/O controller 1115.

The transceiver 1120 may communicate bi-directionally via one or more antennas, wired, or wireless links, as described herein. For example, transceiver 1120 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1120 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission and to demodulate packets received from the antenna.

In some cases, the wireless device may include a single antenna 1125. However, in some cases, the device may have more than one antenna 1125 that may be capable of transmitting or receiving multiple wireless transmissions simultaneously.

The memory 1130 may include a Random Access Memory (RAM) and a Read Only Memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135 comprising instructions that, when executed, cause the processor to perform various functions described herein. In some cases, memory 1130 may contain, among other things, an I/O system (BIOS) that may control basic hardware or software operations, such as interacting with peripheral components or devices.

Processor 1140 may include intelligent hardware devices (e.g., a general purpose processor, a DSP, a Central Processing Unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer readable instructions stored in a memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks to support handling TB-level parity bits for interrupt transmission).

Code 1135 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communications. Code 1135 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, code 1135 may not be directly executable by processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

Fig. 12 illustrates a block diagram 1200 of an apparatus 1205 that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure. The device 1205 may be an example of aspects of a base station 105 as described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to handling TB-level parity bits for interrupt transmission, etc.). Information may be passed to other components of the device 1205. The receiver 1210 may be an example of aspects of the transceiver 1520 described with reference to fig. 15. The receiver 1210 may utilize a single antenna or a set of antennas.

In one embodiment, the communication manager 1215 may receive a first subset of code blocks for a TB from a UE, wherein transmission of the TB is scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and requesting retransmission of at least the second subset of code blocks based on the determination. This embodiment may be used to improve the reliability of receiving retransmissions at the base station 105, as the base station 105 may improve the likelihood that the UE115 may process and send retransmissions in the indicated resources.

Further, based on requesting retransmission of at least the second subset of code blocks, the processor of the base station 105 (e.g., the control receiver 1210, the communication manager 1215, and/or the transmitter 1220) may reduce the processing resources wasted monitoring for code blocks that are not ready to be transmitted. In some cases, the decoder may reduce the number of unsuccessful decoding operations performed, thereby reducing the power required in the decoder to handle the retransmission.

Additionally or alternatively, in another embodiment, the communication manager 1215 may receive a first subset of code blocks of TBs from the UE, wherein transmission of the TBs is scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and transmitting a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block, the transmission being preempted based on the processing timeline for the UE and the second subset of code blocks. This embodiment may be used to improve the reliability of retransmissions for the UE115, since the UE115 may process the information in time to transmit within the allocated resources. Thus, the base station 105 may reduce the processing power for monitoring and decoding of retransmissions. This may reduce signaling overhead in the system, as the number of retransmissions for the UE115 may be reduced.

Further, based on the retransmission request message indicating resources for transmission of the code blocks based on the processing timeline for the UE115 and the second subset of code blocks being preempted, the processor of the base station 105 (e.g., the control receiver 1210, the communication manager 1215, and/or the transmitter 1220) may reduce the processing resources wasted monitoring for code blocks that are not ready for transmission. In some cases, the decoder may reduce the number of unsuccessful decoding operations performed, thereby reducing the power required in the decoder to handle the retransmission.

The communication manager 1215 may be an example of aspects of the communication manager 1510 described herein. The communication manager 1215, or subcomponents thereof, may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or in any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1215, or subcomponents thereof, may be controlled by a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is intended to perform the functions described in this disclosure.

The communication manager 1215, or subcomponents thereof, may be physically located at various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 1215, or subcomponents thereof, may be separate and distinct components in accordance with various aspects of the present disclosure. In some examples, the communication manager 1215, or subcomponents thereof, may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in accordance with the present disclosure, or combinations thereof, in accordance with various aspects of the present disclosure.

Transmitter 1220 may transmit signals generated by other components of device 1205. In some examples, the transmitter 1220 may be collocated with the receiver 1210 in a transceiver module. For example, the transmitter 1220 may be an example of aspects of the transceiver 1520 described with reference to fig. 15. The transmitter 1220 may utilize a single antenna or a set of antennas.

Fig. 13 illustrates a block diagram 1300 of a device 1305 supporting handling TB-level parity bits for interrupted transmission in accordance with aspects of the present disclosure. The device 1305 may be an example of aspects of a device 1205 or a base station 105 as described herein. The device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1345. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 1310 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to handling TB-level parity bits for interrupt transmission, etc.). Information may be communicated to other components of the device 1305. The receiver 1310 may be an example of aspects of the transceiver 1520 described with reference to fig. 15. Receiver 1310 may utilize a single antenna or a set of antennas.

The communication manager 1315 may be an example of aspects of the communication manager 1215 as described herein. The communication manager 1315 may include a TB receive component 1320, an interrupt component 1325, a preemption component 1330, a retransmission request component 1335, and a timeline modification component 1340. The communication manager 1315 may be an example of aspects of the communication manager 1510 described herein.

In some cases, TB receiving component 1320 may receive a first subset of code blocks of TBs from a UE, wherein transmission of the TBs is scheduled for a first set of resources. The interrupt component 1325 can send a message indicating that the second set of resources overlaps in time with at least a portion of the first set of resources. Preemption component 1330 may determine, based on the message, that the UE is preempted for transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB. A retransmission requesting component 1335 may request retransmission of at least the second subset of code blocks based on the determination.

In some other cases, TB receiving component 1320 may receive a first subset of code blocks of TBs from the UE, wherein transmission of the TBs is scheduled for the first set of resources. The interrupt component 1325 can send a message indicating that the second set of resources overlaps in time with at least a portion of the first set of resources. Preemption component 1330 may determine, based on the message, that the UE is preempted for transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB. The timeline modifying component 1340 may transmit a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block that are preempted based on the processing timeline for the UE and the second subset of code blocks.

The transmitter 1345 may transmit signals generated by other components of the device 1305. In some examples, the transmitter 1345 may be collocated with the receiver 1310 in a transceiver module. For example, the transmitter 1345 may be an example of aspects of the transceiver 1520 described with reference to fig. 15. The transmitter 1345 may utilize a single antenna or a set of antennas.

Fig. 14 illustrates a block diagram 1400 of a communication manager 1405 that supports handling TB-level parity bits for interrupted transmissions, in accordance with aspects of the present disclosure. The communication manager 1405 may be an example of aspects of the communication manager 1215, the communication manager 1315, or the communication manager 1510 described herein. Communication manager 1405 may include TB receive component 1410, interrupt component 1415, preemption component 1420, retransmission request component 1425, code chunk identification component 1430, timeline modification component 1435, timeline extension component 1440, grant component 1445, schedule component 1450, or a combination thereof. Each of these modules may communicate with each other, directly or indirectly (e.g., via one or more buses).

In a first embodiment, TB receiving component 1410 may receive a first subset of code blocks of TBs from a UE, where transmissions of the TBs are scheduled for a first set of resources. In some cases, the transmission of the TB includes an initial transmission of the TB by the UE.

The interrupt component 1415 can send a message indicating that the second set of resources overlaps in time with at least a portion of the first set of resources. In some cases, the message indicating the second set of resources includes a grant for a second transmission in the second set of resources. In some other cases, the message indicating the second set of resources requests the UE to refrain from transmitting in the second set of resources.

Preemption component 1420 may determine, based on the message, that the UE is preempted for transmission of a second subset of code blocks of the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB. In some cases, the set of parity bits is a set of CRC bits.

A retransmission request component 1425 can request retransmission of at least the subset of second code blocks based on the determination. In some examples, requesting retransmission may involve retransmission request component 1425 sending a set of retransmission request messages for a set of CBGs that includes at least a second subset of code blocks, where a retransmission request message for a CBG that includes a code block with a set of parity bits for that TB is sent after each other retransmission request message in the set of retransmission request messages. In some examples, retransmission request component 1425 may request retransmission of each code block of the TB based on the determination. In some examples, retransmission request component 1425 may request retransmission of the TB based on the determination. In some examples, requesting retransmission of TBs may involve retransmission request component 1425 requesting retransmission of TBs based on a configuration of the base station that enables preemption of transmissions by the UE and disables CBG level retransmission requests by the base station.

The code block identification component 1430 may identify the second subset of code blocks based on transmissions of the second subset of code blocks scheduled for at least partial overlap in time with the second set of resources.

In a second embodiment, TB receiving component 1410 may receive a first subset of code blocks of TBs from a UE, wherein transmissions of the TBs are scheduled for a first set of resources. The interrupt component 1415 can send a message indicating that the second set of resources overlaps in time with at least a portion of the first set of resources. Preemption component 1420 may determine, based on the message, that the UE is preempted for transmission of a second subset of code blocks of the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB. The timeline modifying component 1435 may transmit a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block that are preempted based on the processing timeline for the UE and the second subset of code blocks.

A timeline extension component 1440 may determine a timeline extension based on the second subset of code blocks being preempted, and may add the timeline extension to the processing timeline to cause the UE to determine resources for transmission of the code blocks. In some cases, the timeline extension is a configuration value. In some other cases, timeline extension component 1440 may calculate the timeline extension based on the number of preempted code blocks in the second subset of code blocks, the length of the TB, or a combination thereof.

In a third embodiment, a grant component 1445 may send a first grant for a first set of resources for a first uplink transmission and may send a second grant for a second set of resources for a second uplink transmission, where the second set of resources for the second uplink transmission at least partially overlaps in time with the first set of resources for the first uplink transmission. A scheduling component 1450 may schedule the third set of resources for the third uplink transmission according to a non-overlapping condition between the third set of resources and the first set of resources. A grant component 1445 may transmit a third grant for a third set of resources for a third uplink transmission based on the schedule. In some cases, TB receiving component 1410 may receive a third uplink transmission based on a third grant and schedule.

Fig. 15 shows a diagram of a system 1500 that includes a device 1505 that supports handling TB-level parity bits for interrupt transmission, in accordance with aspects of the present disclosure. Device 1505 may be an example of or include components of device 1205, device 1305, or base station 105 described herein. The device 1505 may include components for bi-directional voice and data communications, including components for sending and receiving communications, including a communications manager 1510, a network communications manager 1515, a transceiver 1520, an antenna 1525, a memory 1530, a processor 1540, and an inter-station communications manager 1545. These components may be in electronic communication via one or more buses, such as bus 1550.

The communication manager 1510 may receive a first subset of code blocks of TBs from the UE, wherein transmission of the TBs is scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and requesting retransmission of at least the second subset of code blocks based on the determination.

Additionally or alternatively, the communication manager 1510 may receive a first subset of code blocks of TBs from the UE, wherein transmission of the TBs is scheduled for a first set of resources; transmitting a message indicating that a second set of resources overlaps in time with at least a portion of the first set of resources; determining, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB; and transmitting a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block, the transmission being preempted based on the processing timeline for the UE and the second subset of code blocks.

The network communication manager 1515 may manage (e.g., via one or more wired backhaul links) communication with the core network 130. For example, the network communication manager 1515 may manage transmission of data communications for a client device (such as one or more UEs 115).

The transceiver 1520 may communicate bi-directionally via one or more antennas, wired or wireless links, as described herein. For example, the transceiver 1520 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1520 may also include a modem to modulate packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1525. However, in some cases, the device may have more than one antenna 1525, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously.

The memory 1530 may include RAM, ROM, or a combination thereof. The memory 1530 may store computer readable code 1535 comprising instructions that, when executed by the processor (e.g., processor 1540), cause the device to perform the various functions described herein. In some cases, memory 1530 may contain, among other things, a BIOS, which may control basic hardware or software operations, such as interacting with peripheral components or devices.

Processor 1540 may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1540 may be configured to operate the memory array using a memory controller. In some cases, a memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause device 1505 to perform various functions (e.g., functions or tasks to support handling TB-level parity bits for interrupt transmission).

The inter-station communication manager 1545 may manage communication with other base stations 105 and may include a controller or scheduler for controlling communication with UEs 115 in cooperation with the other base stations 105. For example, the inter-station communication manager 1545 may coordinate scheduling of transmissions to the UEs 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-station communication manager 1545 may provide an X2 interface within LTE/LTE-a wireless communication network technology to provide communication between base stations 105.

Code 1535 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communications. The code 1535 may be stored in a non-transitory computer-readable medium, such as system memory or other type of memory. In some cases, the code 1535 may not be directly executable by the processor 1540, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein.

Fig. 16 shows a flow diagram illustrating a method 1600 that supports handling TB-level parity bits for interrupt transmission, in accordance with aspects of the present disclosure. The operations of method 1600 may be implemented by UE115 or components thereof as described herein. For example, the operations of method 1600 may be performed by a communication manager as described with reference to fig. 8-11. In some examples, the UE may execute the set of instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may perform aspects of the functions described herein using dedicated hardware.

At 1605, the UE may cancel transmission of a TB including a set of code blocks, wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation. Operation 1605 may be performed in accordance with the methodologies described herein. In some examples, aspects of operation 1605 may be performed by an encoder as described with reference to fig. 8-11.

At 1610, the UE may receive a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB. Operation 1610 may be performed according to methods described herein. In some examples, aspects of operation 1610 may be performed by a retransmission request component as described with reference to fig. 8-11.

At 1615, the UE may determine, based on the cancellation, that the current state of the set of parity bits for the TB corresponds to the first code block subset. Operation 1615 may be performed according to methods described herein. In some examples, aspects of operation 1615 may be performed by a CRC status component as described with reference to fig. 8-11.

At 1620, the UE may modify a code block including a set of parity bits for the TB based on the determination. Operation 1620 may be performed according to methods described herein. In some examples, aspects of operation 1620 may be performed by a code block modification component as described with reference to fig. 8-11.

At 1625, the UE may transmit the modified code block based on the retransmission request. Operation 1625 may be performed according to methods described herein. In some examples, aspects of operation 1625 may be performed by a retransmission component as described with reference to fig. 8-11.

Fig. 17 shows a flow diagram illustrating a method 1700 of supporting handling of TB-level parity bits for interrupt transmission, in accordance with aspects of the present disclosure. The operations of method 1700 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of method 1700 may be performed by a communication manager as described with reference to fig. 12-15. In some examples, the base station may execute sets of instructions to control the functional elements of the base station to perform the functions described herein. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functionality described herein.

At 1705, the base station may receive a first subset of code blocks of TBs from the UE, wherein transmissions of the TBs are scheduled for a first set of resources. Operation 1705 may be performed according to methods described herein. In some examples, aspects of operation 1705 may be performed by a TB receive component as described with reference to fig. 12 through 15.

At 1710, the base station may transmit a message indicating that the second set of resources overlaps in time with at least a portion of the first set of resources. Operation 1710 may be performed according to the methods described herein. In some examples, aspects of operation 1710 may be performed by an interrupt component as described with reference to fig. 12-15.

At 1715, the base station may determine, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks having a set of parity bits for the TB. Operation 1715 may be performed in accordance with the methods described herein. In some examples, aspects of operation 1715 may be performed by a preemption component as described with reference to fig. 12-15.

At 1720, the base station may request retransmission of at least the second subset of code blocks based on the determination. Operation 1720 may be performed according to methods described herein. In some examples, aspects of operation 1720 may be performed by a retransmission request component as described with reference to fig. 12-15.

Fig. 18 shows a flow diagram illustrating a method 1800 that supports handling TB-level parity bits for interrupt transmission in accordance with aspects of the present disclosure. The operations of method 1800 may be implemented by UE115 or components thereof as described herein. For example, the operations of method 1800 may be performed by a communications manager as described with reference to fig. 8-11. In some examples, the UE may execute the set of instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may perform aspects of the functions described herein using dedicated hardware.

At 1805, the UE may cancel transmission of a TB including a set of code blocks, wherein a first subset of code blocks of the set of code blocks are encoded for transmission and a second subset of code blocks of the set of code blocks are not encoded for transmission based on the cancellation. Operation 1805 may be performed in accordance with the methods described herein. In some examples, aspects of operation 1805 may be performed by an encoder as described with reference to fig. 8-11.

At 1810, the UE may receive a retransmission request for a code block in the second subset of code blocks that includes a set of parity bits for the TB. Operation 1810 may be performed according to the methods described herein. In some examples, aspects of operation 1810 may be performed by a retransmission request component as described with reference to fig. 8-11.

At 1815, the UE may modify the processing timeline based on the second subset of code blocks not being encoded for transmission. Operation 1815 may be performed according to the methods described herein. In some examples, aspects of operation 1815 may be performed by a timeline modification component as described with reference to fig. 8-11.

At 1820, the UE may encode the second subset of code blocks for transmission based on the modified processing timeline. Operation 1820 may be performed according to methods described herein. In some examples, aspects of operation 1820 may be performed by an encoder as described with reference to fig. 8-11.

At 1825, the UE may transmit the code block based on the retransmission request and encode the second subset of code blocks for transmission. Operation 1825 may be performed according to methods described herein. In some examples, aspects of operation 1825 may be performed by a retransmission component as described with reference to fig. 8-11.

Fig. 19 shows a flow diagram illustrating a method 1900 of supporting handling of TB-level parity bits for interrupt transmission according to aspects of the present disclosure. The operations of method 1900 may be performed by a base station 105 or components thereof as described herein. For example, the operations of method 1900 may be performed by a communication manager as described with reference to fig. 12-15. In some examples, the base station may execute sets of instructions to control the functional elements of the base station to perform the functions described herein. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functionality described herein.

At 1905, the base station may receive a first subset of code blocks of TBs from the UE, wherein transmissions of the TBs are scheduled for a first set of resources. Operation 1905 may be performed in accordance with the methods described herein. In some examples, aspects of operation 1905 may be performed by a TB receive component as described with reference to fig. 12-15.

At 1910, the base station can transmit a message indicating that the second set of resources overlaps in time with at least a portion of the first set of resources. Operation 1910 may be performed according to the methods described herein. In some examples, aspects of operation 1910 may be performed by an interrupt component as described with reference to fig. 12-15.

At 1915, the base station may determine, based on the message, that the UE is preempted transmission of a second subset of code blocks for the TB, wherein the second subset of code blocks includes code blocks with a set of parity bits for the TB. Operation 1915 may be performed according to methods described herein. In some examples, aspects of operation 1915 may be performed by a preemption component as described with reference to fig. 12-15.

At 1920, the base station may transmit a retransmission request message for the code block, wherein the retransmission request message indicates resources for transmission of the code block that is preempted based on the processing timeline for the UE and the second subset of code blocks. Operation 1920 may be performed according to the methods described herein. In some examples, aspects of operation 1920 may be performed by a timeline modification component as described with reference to fig. 12-15.

It should be noted that the methods described herein describe possible embodiments, and that the operations and steps may be rearranged or otherwise modified, and that other embodiments are possible. Further, aspects from two or more methods may be combined.

The techniques described herein may be used for various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. The IS-2000 version IS commonly referred to as CDMA 20001X, 1X, etc. IS-856(TIA-856) IS commonly referred to as CDMA 20001 xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes wideband CDMA (wcdma) and other variants of CDMA. A TDMA system may implement a radio technology such as global system for mobile communications (GSM).

OFDMA systems may implement radio technologies such as ultra-mobile broadband (UMB), evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE)802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, and so forth. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A and LTE-A Pro are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, LTE-A Pro, NR, and GSM are described in documents entitled "3 rd Generation partnership project" (3GPP) organization. CDMA2000 and UMB are described in documents from an organization named "3 rd generation partnership project 2" (3GPP 2). The techniques described herein may be used for the systems and radio techniques mentioned herein as well as other systems and radio techniques. Although aspects of the LTE, LTE-A, LTE-A Pro or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro or NR terminology may be used in many of the descriptions, the techniques described herein may be applied beyond LTE, LTE-A, LTE-A Pro or NR applications.

A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs subscribing to a network provider for services. Small cells may be associated with lower power base stations than macro cells, and may operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. According to various examples, the small cells may include pico cells, femto cells, and micro cells. A pico cell may, for example, cover a small geographic area and may allow unrestricted access by UEs subscribing to a network provider for services. A femto cell may also cover a small geographic area (e.g., a home) and may provide unrestricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of home users, etc.). The eNB for the macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, pico eNB, femto eNB, or home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells and may also support communication using one or more component carriers.

The wireless communication systems described herein may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations are approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and the transmissions from different base stations may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operations.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

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

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

Computer-readable media includes both non-transitory computer storage media and communication media (including any medium that facilitates transfer of a computer program from one place to another). A non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can comprise RAM, ROM, electrically erasable programmable ROM (eeprom), Compact Disk (CD) ROM, flash memory, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Also, as used herein (including in the claims), "or" as used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of … …" or "one or more" indicates an inclusive list such that, for example, at least one of A, B or C represents a or B or C or AB or AC or BC or ABC (i.e., a and B and C). Also, as used herein, the phrase "based on" should not be construed as a reference to a closed condition set. For example, an exemplary step described as "based on condition a" may be based on both condition a and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".

In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first numerical reference label is used in the specification, that description applies to any one of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

The description set forth herein in connection with the drawings describes example configurations and is not intended to represent all examples that may be practiced or within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "superior to other examples. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

64页详细技术资料下载
上一篇:一种医用注射器针头装配设备
下一篇:针对侧行链路通信的HARQ反馈

网友询问留言

已有0条留言

还没有人留言评论。精彩留言会获得点赞!

精彩留言,会给你点赞!

技术分类