阅读说明：本技术 设备内冲突处理 (In-device conflict handling ) 是由 S·侯赛尼 陈万士 P·加尔 S·A·A·法库里安 于 2020-05-12 设计创作，主要内容包括：描述用于无线通信的方法、系统和设备以使得用户设备(UE)能够确定用于重叠下行链路传输资源的速率匹配方案或反馈方案。冲突处理方案可以使得UE能够独立于用于其它共享信道(比如第一重叠下行链路共享信道)的另一速率匹配模式或指示符来对第二更高优先级下行链路共享信道进行解速率匹配。UE可以确定围绕与第二信道相关联的控制信令或更高层信令内指示的资源来对第二信道进行解速率匹配。该冲突方案可以使UE针对第一信道中被第二信道抢占的一个或多个部分的反馈生成确认比特,以及针对未被抢占的部分生成其它反馈。基站可以跟踪被抢占的资源,以及可以重新发送第一信道的被抢占的部分。(Methods, systems, and devices for wireless communication are described to enable a User Equipment (UE) to determine a rate matching scheme or a feedback scheme for overlapping downlink transmission resources. The collision handling scheme may enable the UE to de-rate match the second higher priority downlink shared channel independently of another rate matching pattern or indicator for other shared channels, such as the first overlapping downlink shared channel. The UE may determine to de-rate match the second channel around resources indicated within control signaling or higher layer signaling associated with the second channel. The collision scheme may cause the UE to generate acknowledgement bits for feedback of one or more portions of the first channel that are preempted by the second channel and other feedback for portions that are not preempted. The base station may track the preempted resources and may retransmit the preempted portion of the first channel.)

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

identifying a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE;

identifying a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps the first set of resources;

identifying a set of rate matching resources configured for the second downlink shared channel; and

obtaining a downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independently of any rate-matched resources configured for the first downlink shared channel.

2. The method of claim 1, further comprising:

identifying a first priority associated with the first downlink shared channel and a second priority associated with the second downlink shared channel, wherein the second priority is higher than the first priority.

3. The method of claim 1, wherein the rate matching resources configured for the first downlink shared channel at least partially overlap with the set of rate matching resources configured for the second downlink shared channel.

4. The method of claim 1, further comprising:

receiving a first downlink control channel indicating the first set of resources; and

receiving a second downlink control channel indicating the second set of resources.

5. The method of claim 4, wherein the first downlink control channel comprises first Downlink Control Information (DCI) for the first downlink shared channel, the first DCI indicating the rate-matched resources configured for the first downlink shared channel.

6. The method of claim 4, wherein the second downlink control channel comprises second Downlink Control Information (DCI) for the second downlink shared channel, the second DCI indicating the set of rate-matched resources configured for the second downlink shared channel.

7. The method of claim 1, further comprising:

receiving an indication of the set of rate matching resources configured for the second downlink shared channel as the set of shared channel rate matching resources associated with the second priority, wherein the rate matching resources configured for the first downlink shared channel are associated with the first priority.

8. The method of claim 7, further comprising:

receiving an indication of the set of shared channel rate matching resources via Radio Resource Control (RRC) signaling.

9. The method of claim 1, wherein the second set of resources at least partially overlaps in time with the first set of resources.

10. The method of claim 1, wherein the second set of resources at least partially overlaps the first set of resources in time and frequency.

11. A method for wireless communication at a User Equipment (UE), comprising:

identifying a set of code blocks for a downlink shared channel for the UE;

identifying that a portion of the set of code blocks is preempted by a transmission;

assigning acknowledgement bits for each code block that is at least partially preempted by the transmission;

determining acknowledgement bits or negative acknowledgement bits for each code block of the set of code blocks that is not at least partially preempted;

determining one or more feedback messages based on the acknowledgement bits or the negative acknowledgement bits assigned or determined for each code block in the set of code blocks; and

sending the one or more feedback messages to report feedback for the set of code blocks.

12. The method of claim 11, further comprising:

identifying a first priority associated with the downlink shared channel and a second priority associated with the transmission, wherein the second priority is higher than the first priority.

13. The method of claim 11, further comprising:

refraining from assigning Negative Acknowledgement (NAK) feedback bits to each code block that is at least partially preempted by the transmission.

14. The method of claim 11, further comprising:

transmitting a respective feedback message for each code block group associated with the code block set, wherein each code block group comprises a plurality of code blocks of the code block set.

15. The method of claim 11, further comprising:

transmitting a respective feedback message for each transport block associated with the set of code blocks, wherein each transport block comprises a plurality of code blocks of the set of code blocks.

16. The method of claim 11, further comprising:

performing a decoding process on each code block of the set of code blocks that is not at least partially preempted; and

determining feedback for each code block of the set of code blocks that is not at least partially preempted based at least in part on the decoding process.

17. An apparatus for wireless communication at a User Equipment (UE), comprising:

means for identifying a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE;

means for identifying a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps with the first set of resources;

means for identifying a set of rate matching resources configured for the second downlink shared channel; and

means for obtaining a downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independent of any rate-matched resources configured for the first downlink shared channel.

18. The apparatus of claim 17, further comprising:

means for identifying a first priority associated with the first downlink shared channel and a second priority associated with the second downlink shared channel, wherein the second priority is higher than the first priority.

19. The apparatus of claim 17, wherein the rate matching resources configured for the first downlink shared channel at least partially overlap with the set of rate matching resources configured for the second downlink shared channel.

20. The apparatus of claim 17, further comprising:

means for receiving a first downlink control channel indicating the first set of resources; and

means for receiving a second downlink control channel indicating the second set of resources.

21. The apparatus of claim 20, wherein the first downlink control channel comprises first Downlink Control Information (DCI) for the first downlink shared channel, the first DCI indicating the rate-matched resources configured for the first downlink shared channel.

22. The apparatus of claim 20, wherein the second downlink control channel comprises second Downlink Control Information (DCI) for the second downlink shared channel, the second DCI indicating the set of rate-matched resources configured for the second downlink shared channel.

23. The apparatus of claim 17, further comprising:

means for receiving an indication of the set of rate matching resources configured for the second downlink shared channel as a set of shared channel rate matching resources associated with the second priority, wherein the rate matching resources configured for the first downlink shared channel are associated with the first priority.

24. The apparatus of claim 23, further comprising:

means for receiving an indication of the set of shared channel rate matching resources via Radio Resource Control (RRC) signaling.

25. The apparatus of claim 17, wherein the second set of resources at least partially overlaps in time with the first set of resources.

26. The apparatus of claim 17, wherein the second set of resources at least partially overlaps the first set of resources in time and frequency.

27. An apparatus for wireless communication at a User Equipment (UE), comprising:

means for identifying a set of code blocks for a downlink shared channel of the UE;

means for identifying that a portion of the set of code blocks is preempted by a transmission;

means for assigning acknowledgement bits for each code block that is at least partially preempted by the transmission;

means for determining acknowledgement bits or negative acknowledgement bits for each code block of the set of code blocks that is not at least partially preempted;

means for determining one or more feedback messages based on the acknowledgement bits or the negative acknowledgement bits assigned or determined for each code block in the set of code blocks; and

means for transmitting the one or more feedback messages to report feedback for the set of code blocks.

28. The apparatus of claim 27, further comprising:

means for identifying a first priority associated with the downlink shared channel and a second priority associated with the transmission, wherein the second priority is higher than the first priority.

29. The apparatus of claim 27, further comprising:

means for avoiding assigning Negative Acknowledgement (NAK) feedback bits to each code block that is at least partially preempted by the transmission.

30. The apparatus of claim 27, further comprising:

means for transmitting a respective feedback message for each code block group associated with the code block set, wherein each code block group includes a plurality of code blocks in the code block set.

Technical Field

The following relates generally to wireless communications and, more particularly, to intra-device collision handling.

Background

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, as well as fifth generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), orthogonal FDMA (ofdma), or discrete fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communication system may include multiple base stations or network access nodes, each simultaneously supporting communication for multiple communication devices, which may also be referred to as User Equipment (UE).

In some cases, the base station may assign downlink resources that overlap in time or in time and frequency for multiple transmissions to the UE. Some UEs may be able to handle overlapping transmissions, but other UEs may not be able to handle these transmissions, which may result in unsuccessful reception and inefficient use of network resources.

Disclosure of Invention

The described technology relates to improved methods, systems, devices, and apparatus to support intra-device conflict handling. In general, the described techniques provide for determining a rate matching scheme or feedback scheme for overlapping downlink transmission resources. In some cases, a User Equipment (UE) may determine rate matching resources using a collision handling scheme when two channels with different priorities (e.g., a first Physical Downlink Shared Channel (PDSCH) and a second PDSCH with different priorities) are scheduled to overlap in time. For example, if the second PDSCH is associated with a higher priority than the first PDSCH, the collision handling scheme may ensure that the UE de-rate matches the second PDSCH independently of any other rate matching patterns or indicators for other shared channels (e.g., the first PDSCH, other PDSCHs, other configured rate matching resources). In some cases, the UE may determine to de-rate match the second PDSCH around resources indicated by downlink control signaling associated with the second PDSCH (e.g., dynamic resources indicated in a corresponding scheduling grant for the second PDSCH). Additionally or alternatively (e.g., if no rate matching resources are indicated in the control signaling), the UE may de-rate match the second PDSCH according to a rate matching (or de-rate matching) pattern or rate matching resources configured for higher reliability communications indicated via Radio Resource Control (RRC) signaling.

The UE may also use a collision handling scheme to determine the feedback process when multiple channels (e.g., the first PDSCH and the second PDSCH) overlap in time or time and frequency. In some cases, the UE may generate Acknowledgement (ACK) bits for one or more preempted Code Blocks (CBs) of the first PDSCH (e.g., unprocessed overlapping CBs), and may process other CBs within the same Code Block Group (CBG) or Transport Block (TB) to produce feedback (e.g., generate ACK bits if all other CBs pass decoding, or generate Negative Acknowledgement (NAK) bits if one CB fails decoding or if the CB is unprocessed). The CBG or other CBs within the TB may include: the UE stops processing CBs before the preempted CB of the first PDSCH or CBs after the last preempted symbol of the first PDSCH. The UE may send a feedback message to the base station based on the ACK bits generated for the preempted CBs and the ACK/NAK feedback generated for the other CBs. The base station may track the preempted resources (e.g., preempted CBs of the first PDSCH) and may retransmit any CB that was preempted (e.g., even if an ACK is received from the UE for the CBG corresponding to the preempted CB).

A method of wireless communication at a UE is described. The method can comprise the following steps: identifying a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE; identifying a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps the first set of resources; identifying a set of rate matching resources configured for the second downlink shared channel; and obtaining a downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources, independent of any rate-matched resources configured for the first downlink shared channel.

An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: identifying a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE; identifying a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps the first set of resources; identifying a set of rate matching resources configured for the second downlink shared channel; and obtaining a downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources, independent of any rate-matched resources configured for the first downlink shared channel.

Another apparatus for wireless communication at a UE is described. The apparatus may include: means for identifying a first set of resources scheduled for downlink communication of the UE on a first downlink shared channel; means for identifying a second set of resources scheduled for downlink communication of the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps the first set of resources; means for identifying a set of rate matching resources configured for the second downlink shared channel; and means for obtaining a downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independent of any rate-matched resources configured for the first downlink shared channel.

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: identifying a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE; identifying a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps the first set of resources; identifying a set of rate matching resources configured for the second downlink shared channel; and obtaining a downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources, independent of any rate-matched resources configured for the first downlink shared channel.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include: an operation, feature, unit or instruction to identify a first priority associated with the first downlink shared channel and a second priority associated with the second downlink shared channel, wherein the second priority may be higher than the first priority.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the rate matching resources configured for the first downlink shared channel at least partially overlap with the set of rate matching resources configured for the second downlink shared channel.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving a first downlink control channel indicating the first set of resources and receiving a second downlink control channel indicating the second set of resources.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first downlink control channel includes first Downlink Control Information (DCI) for the first downlink shared channel, the first DCI indicating the rate-matched resources configured for the first downlink shared channel.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second downlink control channel includes a second DCI for the second downlink shared channel, the second DCI indicating the set of rate-matched resources configured for the second downlink shared channel.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving an indication of the set of rate matching resources configured for the second downlink shared channel as a set of shared channel rate matching resources associated with the second priority, wherein the rate matching resources configured for the first downlink shared channel may be associated with the first priority.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the set of shared channel rate matching resources may be received via RRC signaling.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second set of resources at least partially overlaps in time with the first set of resources.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second set of resources at least partially overlaps the first set of resources in time and frequency.

A method of wireless communication at a UE is described. The method can comprise the following steps: identifying a set of CBs for a downlink shared channel for the UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; assigning an ACK bit for each CB that is at least partially preempted by the transmission; determining ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted; determining one or more feedback messages based on the ACK bits or the NAK bits assigned or determined for each CB of the set of CBs; and sending the one or more feedback messages to report feedback for the set of CBs.

An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identifying a set of CBs for a downlink shared channel for the UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; assigning an ACK bit for each CB that is at least partially preempted by the transmission; determining ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted; determining one or more feedback messages based on the ACK bits or the NAK bits assigned or determined for each CB of the set of CBs; and sending the one or more feedback messages to report feedback for the set of CBs.

Another apparatus for wireless communication at a UE is described. The apparatus may include means for: identifying a set of CBs for a downlink shared channel for the UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; assigning an ACK bit for each CB that is at least partially preempted by the transmission; determining ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted; determining one or more feedback messages based on the ACK bits or the NAK bits assigned or determined for each CB of the set of CBs; and sending the one or more feedback messages to report feedback for the set of CBs.

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: identifying a set of CBs for a downlink shared channel for the UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; assigning an ACK bit for each CB that is at least partially preempted by the transmission; determining ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted; determining one or more feedback messages based on the ACK bits or the NAK bits assigned or determined for each CB of the set of CBs; and sending the one or more feedback messages to report feedback for the set of CBs.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include: an operation, feature, unit or instruction to identify a first priority associated with the downlink shared channel and a second priority associated with the transmission, wherein the second priority may be higher than the first priority.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include: operations, features, units, or instructions for avoiding assignment of NAK feedback bits to each CB that may be at least partially preempted by the transmission.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include: an operation, feature, unit, or instruction to send a respective feedback message for each CBG associated with the set of CBs, wherein each CBG comprises a plurality of CBs in the set of CBs.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include: an operation, feature, unit or instruction to send a respective feedback message for each TB associated with the set of CBs, wherein each TB comprises a plurality of CBs in the set of CBs.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: performing a decoding process on each CB of the set of CBs that may not be at least partially preempted; and determining feedback for each CB of the set of CBs that may not be at least partially preempted based on the decoding process.

A method of wireless communication at a base station is described. The method can comprise the following steps: identifying a set of CBs for a downlink shared channel for a UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is at least partially preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; receiving, from the UE, one or more feedback messages reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that is at least partially preempted by the transmission; and re-transmitting the portion of the set of CBs that was at least partially preempted regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK.

An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identifying a set of CBs for a downlink shared channel for a UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is at least partially preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; receiving, from the UE, one or more feedback messages reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that is at least partially preempted by the transmission; and re-transmitting the portion of the set of CBs that was at least partially preempted regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK.

Another apparatus for wireless communication at a base station is described. The apparatus may include means for: identifying a set of CBs for a downlink shared channel for a UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is at least partially preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; receiving, from the UE, one or more feedback messages reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that is at least partially preempted by the transmission; and re-transmitting the portion of the set of CBs that was at least partially preempted regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK.

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: identifying a set of CBs for a downlink shared channel for a UE, the downlink shared channel being associated with a first priority; identifying that a portion of the set of CBs is at least partially preempted by transmissions of a second priority, wherein the second priority is higher than the first priority; receiving, from the UE, one or more feedback messages reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that is at least partially preempted by the transmission; and re-transmitting the portion of the set of CBs that was at least partially preempted regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the receiving may include: an operation, feature, unit or instruction to receive a respective feedback message for each TB associated with the set of CBs, wherein each TB includes a plurality of CBs in the set of CBs.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the receiving may include: an operation, feature, unit, or instruction to receive a respective feedback message for each CBG associated with the set of CBs, wherein each CBG comprises a plurality of CBs in the set of CBs.

Drawings

Fig. 1 illustrates an example of a wireless communication system that supports intra-device collision handling in accordance with aspects of the present disclosure.

Fig. 2 illustrates an example of a wireless communication system that supports intra-device collision handling in accordance with aspects of the present disclosure.

Fig. 3A and 3B illustrate examples of downlink channel resource schemes to support intra-device collision handling according to aspects of the present disclosure.

Fig. 4 and 5 illustrate examples of process flows to support intra-device conflict handling according to aspects of the present disclosure.

Fig. 6 and 7 show block diagrams of devices that support intra-device conflict handling according to aspects of the present disclosure.

Fig. 8 illustrates a block diagram of a communication manager that supports intra-device conflict handling in accordance with aspects of the present disclosure.

Fig. 9 shows a schematic diagram of a system including devices that support intra-device conflict handling, according to aspects of the present disclosure.

Fig. 10 and 11 show block diagrams of devices that support intra-device conflict handling according to aspects of the present disclosure.

Fig. 12 illustrates a block diagram of a communication manager that supports intra-device conflict handling in accordance with aspects of the present disclosure.

Fig. 13 shows a schematic diagram of a system including devices that support intra-device conflict handling, in accordance with aspects of the present disclosure.

Fig. 14-18 show flowcharts illustrating methods of supporting in-device conflict handling according to aspects of the present disclosure.

Detailed Description

In some wireless communication systems, a base station may allocate or grant downlink resources to a User Equipment (UE) on a first channel (e.g., a first Physical Downlink Shared Channel (PDSCH)), which may be associated with a lower priority (e.g., enhanced mobile broadband (eMBB)) for transmitting downlink data (e.g., data packets). The base station may also assign downlink resources to the UE on a second channel (e.g., a second PDSCH) that may be associated with a higher priority (e.g., ultra-reliable low-latency communication (URLLC)), where the first PDSCH and the second PDSCH may overlap in time or both time and frequency. For example, a second higher priority PDSCH may be scheduled in time-frequency resources that overlap with a first lower priority PDSCH. In some cases, the second PDSCH may be scheduled after the first PDSCH (e.g., the second PDSCH may be scheduled later in time), with the second higher priority being based on the scheduling timing of the second PDSCH. The priority may be indicated to the UE using a number of different techniques, including transmission timing, control signaling characteristics, etc.

In some examples, the base station may configure (e.g., via Radio Resource Control (RRC) signaling or other control signaling) one or more resources for the UE to perform PDSCH rate matching or de-rate matching, and the UE may de-rate match the assigned PDSCH, such as the first PDSCH or the second PDSCH, around the configured resources. In some cases, the UE may be able to process data transmitted on overlapping portions of both the first PDSCH and the second PDSCH. Additionally or alternatively, the UE may not be able to process data transmitted on overlapping portions of the first PDSCH and the second PDSCH, and may process a higher priority (e.g., second) PDSCH. In one example, the UE may process non-overlapping portions of the first PDSCH and may not process overlapping (e.g., preempted) portions. The UE may also send feedback messages (e.g., Acknowledgement (ACK) or negative ACK (nak) feedback) to the base station based on the data.

In some cases, the UE may determine the rate matching resources using a collision handling scheme when the first PDSCH and the second PDSCH overlap in time. For example, if the rate matching configurations for the two PDSCHs (e.g., the resources around which the UE will perform rate matching for a given channel) do not overlap, a rate matching collision may occur for the UE. The collision handling scheme may enable the UE to de-rate match the second PDSCH independently of any other rate matching patterns or indicators for other shared channels (e.g., the first PDSCH). In some cases, the UE may determine to rate match the second PDSCH around resources indicated within downlink control signaling associated with the second PDSCH (e.g., dynamic resources indicated in a respective scheduling grant). Additionally or alternatively (e.g., if rate matching resources are not indicated in the control signaling), the UE may rate match the second PDSCH around the resources according to the rate matching resources configured for higher reliable communication in RRC signaling. Performing one or both of these collision handling schemes may allow the UE to rate match the first PDSCH and the second PDSCH around configured resources that independently overlap the two PDSCHs.

The UE may also determine an ACK/NAK feedback procedure using a collision handling scheme when the first PDSCH and the second PDSCH overlap in time. In some cases, the UE may generate ACK bits for one or more preempted Code Blocks (CBs) of the first PDSCH, and may process other CBs within the same Code Block Group (CBG) or Transport Block (TB) to produce ACK/NAK feedback (e.g., the UE may generate ACK bits if all other CBs of a CBG or TB pass decoding, or the UE may generate NAK bits if one CB of a CBG or TB fails decoding or is not processed). The CBG or other CBs within the TB may include the UE stopping or starting processing the preempted CB of the first PDSCH or the CB before the CB after the last preempted symbol of the first PDSCH. The UE may send a feedback message to the base station based on the ACK bits generated for the preempted CBs and the ACK/NAK feedback generated for the other CBs. The base station may track the preempted resources (e.g., preempted CBs of the first PDSCH) and may retransmit any CB that was preempted (e.g., even if an ACK is received from the UE for the CBG or TB corresponding to the preempted CB).

Aspects of the present disclosure are initially described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to downlink channel resource schemes, process flows, apparatus diagrams, system diagrams, and flowcharts related to in-device collision handling.

Fig. 1 illustrates an example of a wireless communication system 100 that supports intra-device collision handling in accordance with aspects of the present disclosure. The wireless communication system 100 may include 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-APro network, or a New Radio (NR) network. In some cases, wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low cost and low complexity devices, or any combination thereof.

The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be of different forms or devices with different capabilities. The base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UE115 and base station 105 may establish a communication link 125. Coverage area 110 may be an example of a geographic area: over the geographic area, base stations 105 and UEs 115 support transmitting signals according to one or more radio access technologies.

The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE115 may be stationary, or mobile, or both, at different times. The UEs 115 may be devices of different forms or with different capabilities. Some example UEs 115 are shown in fig. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, Integrated Access and Backhaul (IAB) nodes, or other network devices), as shown in fig. 1.

The base stations 105 may communicate with the core network 130, with each other, or both. For example, the base stations 105 may be connected with the core network 130 over the backhaul links 120 (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 the backhaul links 120 (e.g., via X2, Xn, or other interfaces), or both. In some examples, backhaul link 120 may be or include one or more wireless links.

One or more of the base stations 105 described herein may include or may be referred to by those of ordinary skill in the art as a base station transceiver, a radio base station, an access point, a wireless transceiver, a node B, an evolved node B (enb), a next generation node B or gigabit node B (any of which may be referred to as a gNB), a home node B, a home evolved node B, or other suitable terminology.

The UE115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a user equipment, or some other suitable terminology, where a "device" may also be referred to as a unit, station, terminal, or client, among other examples. The UE115 may also include or may be referred to as 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 include or be referred to as a Wireless Local Loop (WLL) station, an internet of things (IoT) device, an internet of everything (IoE) device, a Machine Type Communication (MTC) device, and so on, which may be implemented in various items such as home appliances, vehicles, meters, and so on.

The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as base stations 105 and network devices, including macro enbs or gnbs, small cell enbs or gnbs, relay base stations, and so forth, as shown in fig. 1.

The UE115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 over one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, the carrier used for the communication link 125 may comprise a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to physical layer channels for a given radio access technology (e.g., LTE-A, LTE-a Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carriers, user data, or other signaling. The wireless communication system 100 may support communication with UEs 115 using 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 Frequency Division Duplex (FDD) component carriers and Time Division Duplex (TDD) component 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 carriers may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode).

The carrier may be associated with a particular bandwidth of the 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 a plurality of predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) of the carrier for the particular radio access technology. Devices of the wireless communication system 100 (e.g., base stations 105, UEs 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth or may be configurable 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 or UE115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE115 may be configured to operate on a portion of a carrier bandwidth (e.g., a sub-band, a bandwidth portion (BWP)) or the entire carrier bandwidth.

The signal waveform transmitted on a carrier may be composed of a plurality of subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or discrete fourier transform spread OFDM (DFT-S-OFDM)). 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, the coding rate of the modulation scheme, or both). Thus, the more resource elements the UE115 receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE 115. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with the UE 115.

May be in basic time units (which may for example refer to T)_s＝1/(Δf_max·N_f) A sampling period of seconds, where Δ f_maxMay represent the maximum supported subcarrier spacing, and N_fMay represent a multiple of a maximum supported Discrete Fourier Transform (DFT) size) to represent a time interval for a base station 105 or UE 115. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

Each frame may include a plurality of consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some cases, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a plurality of slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each slot may include multiple symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of minislots comprising one or more symbols. Each symbol period may contain one or more (e.g., N) excluding the cyclic prefix_fOne) sampling period. The duration of the symbol period may depend on the subcarrier spacing or operating frequency band.

A subframe, slot, minislot, or symbol may be the smallest scheduling unit of the wireless communication system 100 and may be referred to as a Transmission Time Interval (TTI). In some cases, the TTI duration (i.e., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, a minimum scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of shortened ttis (stti)).

The physical channels may be multiplexed on the carriers according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using Time Division Multiplexing (TDM) techniques, Frequency Division Multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a set of control resources (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend over a system bandwidth or a subset of the system bandwidth of a carrier. One or more control regions (e.g., CORESET) may be configured for the set of UEs 115. For example, the UE115 may monitor or search for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., Control Channel Elements (CCEs)) associated with encoded information for a control information format having a given payload size. The set of search spaces may include a common set of search spaces configured for transmitting control information to a plurality of UEs 115 and a UE-specific set of search spaces for transmitting control information to a specific UE 115.

In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), eMBB, or other protocol types) that may provide access for different types of devices.

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, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for respective geographic coverage areas 110 using the same or different radio access technologies.

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., communication via machine-to-machine (M2M)). M2M communication or MTC may refer to data communication techniques that allow devices to communicate with each other or the 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 such information to a central server or application that utilizes the information or presents the information to a human interacting with the application. Some UEs 115 may be designed to gather information or to implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing for services.

The wireless communication system 100 may be configured to support ultra-reliable communications or low latency communications, or various combinations thereof. For example, the wireless communication system 100 may be configured to support URLLC or mission critical communications. The UE115 may be designed to support ultra-reliable, low latency, or critical functions (e.g., mission critical functions). The ultra-reliable communication may include private communication or group communication, and may be supported by one or more mission critical services, such as mission critical push-to-talk (MCPTT), mission critical video (MCVideo), or mission critical data (MCData). Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general business applications. The terms ultra-reliable, low latency, mission critical, and ultra-reliable low latency may be used interchangeably herein.

In some cases, the UE115 may also be able to communicate directly (e.g., using peer-to-peer (P2P) or D2D protocols) with other UEs 115 over the device-to-device (D2D) communication link 135. One or more UEs 115 communicating with D2D may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or otherwise unable 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 in which each UE115 transmits to every other UE115 in the group. In some examples, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base stations 105.

The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an Evolved Packet Core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., Mobility Management Entity (MME), access and mobility management function (AMF)) that manages access and mobility and at least one user plane entity (e.g., serving gateway (S-GW), Packet Data Network (PDN) gateway (P-GW), or User Plane Function (UPF)) that routes or interconnects packets to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the core network 130. User IP packets may be communicated through a user plane entity, which may provide IP address assignment as well as other functions. The user plane entity may be connected to a network operator IP service 150. The operator IP services 150 may include access to the internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

Some of the network devices, such as base station 105, may include subcomponents, such as access network entity 140, which may be examples of an Access Node Controller (ANC). Each access network entity 140 may communicate with the UE115 through a plurality of other access network transport entities 145, which may be referred to as radio heads, intelligent radio heads, or transmission/reception points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) 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). Typically, the region from 300MHz to 3GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by building and environmental features, but the waves may be sufficiently penetrating the structure for the macro cell to provide service to the UE115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) than transmission of smaller and longer waves using the High Frequency (HF) or Very High Frequency (VHF) portion 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 frequency band) or in the Extremely High Frequency (EHF) region of the spectrum (e.g., from 30GHz to 300GHz) (also referred to as a millimeter frequency band). 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 even smaller and more closely spaced compared to UHF antennas. In some cases, this may facilitate the use of antenna arrays within a device. However, propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and the use of designations of frequency bands across these frequency regions may differ depending on the country or regulatory agency.

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), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands, such as the 5GHz industrial, scientific, and medical (ISM) band. When operating in the unlicensed radio frequency spectrum band, devices such as base stations 105 and UEs 115 may employ carrier sensing for collision detection and avoidance. In some cases, operation in the unlicensed band may be based on a carrier aggregation configuration in conjunction with component carriers operating in the licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, and so on.

A base station 105 or UE115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of a base station 105 or UE115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with base stations 105 may be located at different geographic locations. The base station 105 may have an antenna array with multiple rows and columns of 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. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

Beamforming (which may also be referred to as spatial filtering, directional transmission or directional reception) is a signal processing technique that: the techniques may be used at a transmitting device or a receiving device (e.g., base station 105 or UE 115) to form or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by: signals transmitted via the antenna elements of the antenna array are combined such that some signals propagating in a particular orientation relative to the antenna array undergo constructive interference while other signals undergo destructive interference. The adjustment of the signal transmitted via the antenna element may comprise: either the transmitting device or the receiving device applies an amplitude offset, a phase offset, or both, to the signal carried via the antenna element 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).

The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at 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 on logical channels. A Medium Access Control (MAC) layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide for the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE115 and the base station 105 or core network 130. At the physical layer, transport channels may be mapped to physical channels.

The UE115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received on 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)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some examples, a device may support same slot HARQ feedback, 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.

In some wireless communication systems, a base station may assign or grant downlink resources to a UE on a first PDSCH that may be associated with a lower priority communication type (e.g., eMBB) for transmitting downlink data (e.g., data packets). The base station may also assign downlink resources to the UE on a second PDSCH that may be associated with a higher priority communication type (e.g., URLLC), where the first PDSCH and the second PDSCH may overlap in time or both in time and frequency. For example, a second higher priority PDSCH may be scheduled on a first lower priority PDSCH. In some cases, the second PDSCH may be scheduled after the first PDSCH, where a higher priority is based on later scheduling of the second PDSCH. The communication type priority may be indicated to the UE using a number of different techniques including transmission timing, control signaling characteristics, and so forth. In some cases, the UE may be able to process data transmitted on overlapping portions of both the first PDSCH and the second PDSCH. Additionally or alternatively, the UE may not be able to process data transmitted on overlapping portions of the first PDSCH and the second PDSCH, and may process a higher priority (e.g., second) PDSCH. In one example, the UE may process non-overlapping portions of the first PDSCH and may not process overlapping (e.g., preempted) portions.

In some cases, the UE may determine the rate matching resources using a collision handling scheme when the first PDSCH and the second PDSCH overlap in time. The collision handling scheme may ensure that the UE is able to rate match the second PDSCH independently of any other rate matching patterns or indicators for other shared channels (e.g., the first PDSCH). In some cases, the UE may rate match the second PDSCH around resources indicated within downlink control signaling or RRC signaling associated with the second PDSCH (e.g., dynamic resources indicated in a corresponding scheduling grant or resources configured for higher reliability communications). The UE may also use a collision handling scheme to determine the ACK/NAK feedback procedure. In some cases, the UE may generate ACK bits for one or more preempted CBs of the first PDSCH and may process other CBs (e.g., non-preempted CBs) within the same CBG or TB to produce ACK/NAK feedback. The UE may send feedback messages to the base station based on the ACK bits generated for the preempted CBs and the ACK/NAK feedback generated for the other CBs. The base station may track the preempted resources (e.g., preempted CBs of the first PDSCH) and may retransmit any CBs that were preempted (e.g., even if an ACK is received from the UE).

Fig. 2 illustrates an example of a wireless communication system 200 that supports intra-device collision handling in accordance with aspects of the present disclosure. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100 and may include a UE 115-a and a base station 105-a, which may be examples of the UE115 and base station 105 described with reference to fig. 1. In some cases, the base station 105-a may send a downlink message to the UE 115-a via two separate overlapping PDSCHs, and the UE 115-a may process the downlink message according to a collision handling scheme.

For example, the base station 105-a may assign (e.g., grant) downlink resources to the UE 115-a on a first PDSCH associated with a lower priority communication type (e.g., eMBB) for transmission of a downlink data message 215 (e.g., a data packet). The base station 105-a may also assign downlink resources to the UE 115-a on a second PDSCH associated with a higher priority communication type (e.g., URLLC), where the first PDSCH and the second PDSCH may overlap in time or both time and frequency. In some cases, the base station 105-a may assign resources in the second PDSCH to send a higher priority (e.g., urgent) downlink data message 220 (e.g., a data packet) to the UE 115-a. For example, a second higher priority PDSCH may be scheduled on a first lower priority PDSCH. In some examples, the second PDSCH may be scheduled after (e.g., immediately after in time) the first PDSCH.

In some cases, the priority of the communication type may be based on the transmission time for the downlink data messages 215 and 220. For example, if a downlink control message 210-a (e.g., Downlink Control Information (DCI) for a Physical Downlink Control Channel (PDCCH)) scheduling a downlink data message 215 on the first PDSCH is received before a downlink control message 210-b for a downlink data message 220 is scheduled on the second PDSCH, the second PDSCH may have a higher priority than the first PDSCH. Additionally or alternatively, the priority of the communication type may be indicated based on a size of the downlink control message 210, a format of the downlink control message 210, a Radio Network Temporary Identifier (RNTI), a CORESET used to send the downlink control message 210, a search space used to send the downlink control message 210, or a bit indication in the downlink control message 210.

In some examples, the base station 105-a may configure the UE 115-a via an RRC message 205 (e.g., RRC signaling) (e.g., prior to sending the downlink control message 210). For example, the base station 105-a may use the RRC message 205 to configure one or more resources (e.g., Resource Blocks (RBs) or symbols) for the UE 115-a to perform PDSCH de-rate matching. In some cases, the UE 115-a may rate match the assigned PDSCH (such as the first PDSCH or the second PDSCH) around RRC-configured resources (e.g., unavailable resources). In some cases, the configured resources (e.g., RRC configured resources) may be specific to certain priority communications (e.g., higher priority rate matched resources, lower priority rate matched resources). In some cases, the base station 105-a may configure other resources for de-rate matching a particular PDSCH, and may indicate the other resources to the UE 115-a via a downlink grant associated with the PDSCH (e.g., within the downlink control message 210). For example, the base station 105-a may include a bitmap or rate matching indicator within the downlink control message 210 (e.g., DCI on PDCCH) that may request the UE 115-a to rate match around the indicated resources.

In some cases, the UE 115-a may determine the rate matching resources using a collision handling scheme when the first PDSCH (e.g., carrying the downlink data message 215) and the second PDSCH (e.g., carrying the downlink data message 220) overlap in time. For example, if the rate matching configurations for the two PDSCHs do not overlap, a rate matching collision may occur for UE 115-a. In some wireless systems, the second PDSCH may be rate matched around resources indicated in the downlink control message 210-a (e.g., downlink data message 215 is scheduled within the first PDSCH). However, the first PDSCH and the second PDSCH may have different reliability targets that may affect reception of the downlink control message 210. If the UE 115-a is not to receive the downlink control message 210-a (e.g., due to lower reliability associated with the downlink control message 210-a), the UE 115-a may not be able to obtain rate matching information for the downlink data message 220 and the second PDSCH, which may affect reliability.

Thus, the collision handling scheme may ensure that the UE 115-a rate matches the second PDSCH independently of any other rate matching patterns or indicators for other shared channels (e.g., the first PDSCH). In some cases, the UE 115-a may determine to rate match the second PDSCH carrying the higher priority downlink data message 220 around resources indicated within the downlink control message 210-b (e.g., dynamic resources indicated in the corresponding scheduling grant). Thus, the base station 105-a may determine that the rate-matched resources are consistent with the second PDSCH (e.g., higher priority PDSCH). Additionally or alternatively (e.g., if rate matching resources are not indicated in the downlink control message 210-b), the UE 115-a may rate match the higher priority downlink data message 220 around resources configured for the second PDSCH (e.g., higher reliability communication) in the RRC message 205. Performing one or both of these collision handling schemes may allow the UE 115-a to rate match the first PDSCH and the second PDSCH around the configured resources that independently overlap both PDSCHs.

In some cases, the UE 115-a may be able to process both downlink data messages 215 and 220 (e.g., data transmitted on overlapping portions of both the first PDSCH and the second PDSCH). Additionally or alternatively, the UE 115-a may not be able to process data transmitted on overlapping portions of the first PDSCH and the second PDSCH, and the UE 115-a may process a downlink data message 220 on a higher priority (e.g., second) PDSCH. For example, UE 115-a may or may not be able to process overlapping portions of downlink data message 215 based on one or more conditions. In one example, UE 115-a may process non-overlapping portions of downlink data message 215 and may not process overlapping portions (e.g., preempted portions). The UE 115-a may also send a feedback message 225 (e.g., ACK/NAK feedback) associated with the downlink data message 215 or 220 to the base station 105-a.

In some cases, feedback (e.g., ACK/NAK feedback) may be reported at the TB level or at the CBG level. For example, if UE 115-a is configured to send TB level ACK/NAK feedback and one of the TBs fails decoding (e.g., even if the other CBs pass decoding), UE 115-a may send a NAK for that TB in feedback message 225 to base station 105-a. Similarly, if the UE 115-a is configured to send CBG level ACK/NAK feedback and one of the CBGs fails to decode (e.g., even if the other CBs pass decoding), the UE 115-a may send a NAK for that CBG in a feedback message 225 to the base station 105-a.

The UE 115-a may also use a collision handling scheme to determine the ACK/NAK feedback process when the first PDSCH (e.g., carrying the downlink data message 215) and the second PDSCH (e.g., carrying the downlink data message 220) overlap in time. In some cases, UE 115-a may include a NAK in feedback message 225 in response to one or more preempted CBs within a CBG or TB of the first PDSCH (e.g., corresponding to downlink data message 215). As used herein, a preempted CB or CBG may refer to a fully preempted or partially preempted CB or CBG (e.g., the CB or CBG partially overlaps with the second higher priority transmission). For example, the preempted CB or CBG may partially overlap symbols associated with the second PDSCH, where the first PDSCH and the second PDSCH may overlap in time, frequency, or both. Additionally or alternatively, the preempted resources may include one or more CBs or CBGs after the last overlapping symbol (e.g., where processing of the first PDSCH may be terminated after the UE 115-a encounters overlapping resources). In this case, the base station 105-a may determine that the UE 115-a has not processed any CBs or CBGs following the last overlapping symbol, and may consider these CBs or CBGs to be preempted.

If the UE 115-a generates a NAK for one or more preempted CBs, the NAK may then be applied to the entire CBG or TB even if the UE 115-a successfully decodes other portions (e.g., one or more CBs) of the CBG or TB. Thus, UE 115-a may generate an ACK for the one or more preempted CBs and may process the CBGs or other CBs within the TB to produce ACK/NAK feedback as described herein (e.g., send an ACK if all CBs decode or send a NAK if one CB fails to decode or does not process the CB). CBG or other CBs within TB may include: the CB before the preempted CB of the first PDSCH, or the CB after the last preempted symbol of the first PDSCH, are stopped from being processed by the UE 115-a. As discussed above, after receiving the downlink data message 220 on the second PDSCH, the UE 115-a may additionally or alternatively stop processing other CBs of the first PDSCH.

In some cases (e.g., where all CBs of a TB or CBG except the preempted CB pass decoding), UE 115-a may include an ACK in the feedback message 225 to base station 105-a for that TB or CBG. In some cases, one or more CBs (other than the preempted CB) in a TB or CBG may fail decoding, and the UE 115-a may include a NAK in the feedback message 225 for that TB or CBG. The base station 105-a may track the preempted resources (e.g., preempted CBs of the first PDSCH or downlink data message 215) and may resend any CB preempted (e.g., even if an ACK is received from the UE 115-a).

Fig. 3A illustrates an example of a downlink channel resource scheme 301 that supports intra-device collision handling in accordance with aspects of the present disclosure. In some examples, the PDSCH resource scheme 301 may implement aspects of the wireless communication system 100 or 200 and may be implemented by the UE115 and the base station 105, which may be examples of the UE115 and base station 105 described with reference to fig. 1 and 2. In some cases, the base station 105 may transmit a downlink message to the UE115 via two separate, overlapping PDSCHs according to the PDSCH resource scheme 301, and the UE115 may process the downlink message according to a collision handling scheme, as described with reference to fig. 2.

For example, the base station 105 may assign (e.g., grant) downlink resources on the first PDSCH305-a to the UE115 for transmitting downlink data messages (e.g., data packets), wherein the first PDSCH305-a may be associated with a lower priority communication type (e.g., eMBB) in some cases. The base station 105 may also assign downlink resources to the UE115 on a second PDSCH310-a, where the second PDSCH310-a may be associated with a higher priority communication type (e.g., URLLC) in some examples, where the first PDSCH and the second PDSCH may overlap in both time and frequency. In some cases, the base station 105 may assign resources in the second PDSCH310-a in order to send higher priority (e.g., urgent) downlink data messages (e.g., data packets) to the UE 115.

Thus, the UE115 may process data on the first PDSCH305-a and the second PDSCH310-a according to a collision handling scheme. In some cases, the UE115 may determine not to process portions of the first PDSCH305-a (e.g., data) that overlap portions of the second PDSCH310-a, which may be referred to as preempted portions (e.g., preempted CBs) of the first PDSCH 305-a. The UE115 may use a collision handling scheme to identify resources around which the UE115 may rate match the second PDSCH 310-a. Further, the UE115 may use a collision handling scheme to send ACK/NAK feedback to the base station 105 regarding data received on the first PDSCH 305-a.

As described with reference to fig. 2, if the UE 115-a does not receive a downlink control message corresponding to the first PDSCH305-a, the UE115 may not be able to obtain rate matching information for the second PDSCH310-a, which may affect the reliability of the second PDSCH 310-a. Thus, in some cases, the UE115 may rate match the second PDSCH310-a around resources dynamically indicated in the corresponding scheduling grant, where the base station 105 may determine that the rate-matched resources are consistent. Additionally or alternatively (e.g., if rate matching resources are not indicated in the scheduling grant), the UE115 may rate match around resources configured for the second PDSCH310-a (e.g., higher reliability communication) in RRC signaling.

The UE115 may also use a collision handling scheme to determine ACK/NAK feedback for preempted CBs of the first PDSCH305-a, where the preempted CBs may represent fully preempted or partially preempted CBs (e.g., the CBs partially overlap with the second PDSCH 310-a). For example, the preempted CB or CBG may partially overlap with the symbols associated with the second PDSCH 310-a. Additionally or alternatively, the preempted resources may include one or more CBs or CBGs after the last overlapping symbol of the first PDSCH305-a and the second PDSCH310-a (e.g., where processing of the first PDSCH305-a may be terminated after the UE115 encounters overlapping resources). In this case, the base station 105 may determine that the UE115 has not processed any CBs or CBGs following the last overlapped symbol and may consider these CBs or CBGs to be preempted.

UE115 may generate an ACK for the preempted CBs and may process the non-preempted CBs within the CBG or TB of first PDSCH305-a to produce ACK/NAK feedback. For example, UE115 may send an ACK if all non-preempted CBs in a CBG or TB pass decoding, or a NAK if one non-preempted CB fails decoding or if one non-preempted CB is not processed. In some cases where all CBs except the preempted CB pass decoding, the UE115 may send an ACK to the base station 105. The base station 105 may track the preempted resources (e.g., preempted CBs of the first PDSCH 305-a) and may retransmit any of the preempted CBs (e.g., even if an ACK is received from the UE 115).

Fig. 3B illustrates an example of a downlink channel resource scheme 302 that supports intra-device collision handling in accordance with aspects of the present disclosure. In some examples, the PDSCH resource scheme 302 may implement aspects of the wireless communication system 100 or 200 and may be implemented by the UE115 and the base station 105, which may be examples of the UE115 and the base station 105 described with reference to fig. 1 and 2. In some cases, the base station 105 may transmit a downlink message to the UE115 via two separate, overlapping PDSCHs according to the PDSCH resource scheme 302, and the UE115 may process the downlink message according to a collision handling scheme, as described with reference to fig. 2.

For example, the base station 105 may assign (e.g., grant) downlink resources to the UE115 on the first PDSCH305-b associated with a lower priority communication type (e.g., eMBB) for transmitting downlink data messages (e.g., data packets). The base station 105 may also assign downlink resources to the UE115 on a second PDSCH310-b associated with a higher priority communication type (e.g., URLLC), where the first PDSCH and the second PDSCH may overlap in frequency. In some cases, the base station 105 may assign resources in the second PDSCH310-b to send higher priority (e.g., emergency) downlink data messages (e.g., data packets) to the UE 115.

Thus, the UE115 may process data on the first PDSCH305-b and the second PDSCH310-b according to a collision handling scheme. In some cases, the UE115 may determine not to process portions of the first PDSCH305-b (e.g., data) that overlap portions of the second PDSCH310-b, which may be referred to as preempted portions (e.g., preempted CBs) of the first PDSCH 305-b. The UE115 may use a collision handling scheme to identify resources around which the UE115 may rate match the second PDSCH 310-b. Additionally, the UE115 may use a collision handling scheme to send ACK/NAK feedback to the base station 105 regarding data received on the first PDSCH 305-b.

As described with reference to fig. 2, if the UE115-b does not receive a downlink control message corresponding to the first PDSCH305-b, the UE115 may not be able to obtain rate matching information for the second PDSCH310-b, which may affect the reliability of the second PDSCH 310-b. Thus, in some cases, the UE115 may rate match the second PDSCH310-b around resources dynamically indicated in the respective scheduling grant, where the base station 105 may determine that the rate-matched resources are consistent. Additionally or alternatively (e.g., if rate matching resources are not indicated in the scheduling grant), the UE115 may rate match around resources configured for the second PDSCH310-b (e.g., higher reliability communication) in RRC signaling.

The UE115 may also use a collision handling scheme to determine ACK/NAK feedback for preempted CBs of the first PDSCH305-b, where the preempted CBs may represent fully preempted or partially preempted CBs (e.g., the CBs partially overlap with the second PDSCH 310-b). For example, the preempted CB or CBG may partially overlap with symbols associated with the second PDSCH 310-b. Additionally or alternatively, the preempted resources may include one or more CBs or CBGs after the last overlapping symbol of the first PDSCH305-b and the second PDSCH310-b (e.g., where processing of the first PDSCH305-b may be terminated after the UE115 encounters overlapping resources). In this case, the base station 105 may determine that the UE115 has not processed any CBs or CBGs following the last overlapped symbol and may consider these CBs or CBGs to be preempted.

UE115 may generate an ACK for the preempted CBs and may process the non-preempted CBs within the CBG or TB of first PDSCH305-b to produce ACK/NAK feedback. For example, UE115 may send an ACK if all non-preempted CBs in a CBG or TB pass decoding, or a NAK if one non-preempted CB fails decoding or if one non-preempted CB is not processed. Thus, in some cases where all CBs except the preempted CB pass decoding, the UE115 may send an ACK to the base station 105. The base station 105 may track the preempted resources (e.g., preempted CBs of the first PDSCH 305-b) and may retransmit any of the preempted CBs (e.g., even if an ACK is received from the UE 115).

Fig. 4 illustrates an example of a process flow 400 to support intra-device conflict handling in accordance with aspects of the present disclosure. In some examples, the process flow 400 may implement aspects of the wireless communication system 100 or 200 and may be implemented by a UE115-b and a base station 105-b, which may be examples of the UE115 and base station 105 described with reference to fig. 1-3. In some cases, the base station 105-b may assign resources for transmitting downlink data to the UE115-b via two separate, overlapping PDSCHs, and the UE115-b may process the PDSCHs according to a collision processing scheme.

In the following description of process flow 400, operations between UE115-b and base station 105-b may be transmitted in an order different than that shown, or operations performed by base station 105-b and UE115-b may be performed in a different order or at a different time. Certain operations may also be excluded from the process flow 400 or other operations may be added to the process flow 400. It is to be appreciated that although base station 105-b and UE115-b are illustrated as performing various operations of process flow 400, any wireless device may perform the illustrated operations.

At 405, in some cases, the base station 105-b may transmit a first downlink control channel (e.g., a downlink control message on the PDCCH) to the UE115-b indicating a first set of resources. In some cases, the first downlink control channel may include a first DCI for a first downlink shared channel, the first DCI indicating rate-matching resources configured for the first downlink shared channel.

At 410, the UE115-b may identify a first set of resources scheduled for downlink communications on a first downlink shared channel (e.g., PDSCH) for the UE115-b, and in some examples, the first downlink shared channel may be associated with a first priority (e.g., a lower priority). In some cases, the UE115-b may identify the first set of resources based on the first downlink control channel transmission.

At 415, in some cases, the base station 105-b may transmit a second downlink control channel (e.g., a downlink control message on the PDCCH) to the UE115-b indicating the second set of resources. In some cases, the second downlink control channel may include a second DCI for a second downlink shared channel, the second DCI indicating a set of rate-matching resources configured for the second downlink shared channel.

At 420, the UE115-b may identify a second set of resources scheduled for downlink communication on a second downlink shared channel (e.g., PDSCH for the UE115-b, and in some examples, the second downlink shared channel may have a second priority that may be higher than the first priority), where the second set of resources at least partially overlaps the first set of resources. In some cases, UE115-b may identify the second set of resources based on a second downlink control channel transmission. In some examples, the second set of resources may at least partially overlap in time with the first set of resources. In some examples, the second set of resources may at least partially overlap in time and frequency with the first set of resources.

At 425, the UE115-b may identify a set of rate matching resources configured for a second downlink shared channel. In some cases, the rate matching resources configured for the first downlink shared channel may at least partially overlap with the set of rate matching resources configured for the second downlink shared channel. In some cases, identifying the set of rate matching resources for the second downlink shared channel may include: an indication of a set of rate matching resources configured for a second downlink shared channel as a set of shared channel rate matching resources associated with a second priority, wherein the rate matching resources configured for the first downlink shared channel are associated with the first priority. In some examples, an indication of a set of rate-matched resources for a second downlink shared channel may be received via RRC signaling.

At 430, the UE115-b may obtain the downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independent of any rate-matched resources configured for the first downlink shared channel.

Fig. 5 illustrates an example of a process flow 500 to support intra-device conflict handling in accordance with aspects of the present disclosure. In some examples, the process flow 500 may implement aspects of the wireless communication system 100 or 200 and may be implemented by a UE 115-c and a base station 105-c, which may be examples of the UE115 and base station 105 described with reference to fig. 1-3. In some cases, the base station 105-c may assign resources for transmitting downlink data to the UE 115-c via two separate, overlapping PDSCHs, and the UE 115-c may process the PDSCHs according to a collision processing scheme.

In the following description of process flow 500, operations between UE 115-c and base station 105-c may be transmitted in an order different than that shown, or operations performed by base station 105-c and UE 115-c may be performed in a different order or at a different time. Certain operations may also be excluded from the process flow 500 or other operations may be added to the process flow 500. It is to be appreciated that although base station 105-c and UE 115-c are illustrated as performing various operations of process flow 500, any wireless device may perform the illustrated operations.

At 505, the base station 105-c may identify a set of CBs for a downlink shared channel (e.g., PDSCH) for the UE 115-c, which may be associated with a first priority (e.g., a lower priority) in some examples.

At 510, the UE 115-c may identify a set of CBs for a downlink shared channel (e.g., PDSCH) for the UE 115-c, the downlink shared channel being associated with a first priority (e.g., a lower priority).

At 515, the base station 105-c may identify that a portion of the set of CBs is at least partially preempted by a transmission, where the transmission may be associated with a second priority higher than the first priority.

At 520, the UE 115-c may identify that a portion of the set of CBs is preempted by transmission of a second priority, wherein the second priority is higher than the first priority. In some cases, a second higher priority may be associated with subsequent transmissions.

At 525, UE 115-c may assign an ACK bit to each CB preempted at least in part by the transmission. In some cases, UE 115-c may refrain from assigning NAK feedback bits to each CB that is at least partially preempted by the transmission.

At 530, UE 115-c determines an ACK bit or a NAK bit for each CB in the set of CBs that is not at least partially preempted. In some cases, UE 115-c may perform a decoding process for each CB of the set of CBs that is not at least partially preempted, and determine feedback for each CB of the set of CBs that is not at least partially preempted based on the decoding process.

At 535, the UE 115-c determines one or more feedback messages based on the ACK bits or NAK bits assigned or determined for each CB in the CB set.

At 540, the UE 115-c may send the one or more feedback messages to the base station 105-c to report feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to a portion of the set of CBs that is at least partially preempted by the transmission. In some cases, UE 115-c may send a respective feedback message for each CBG associated with a set of CBs, where each CBG may include multiple CBs in the set of CBs. In some cases, UE 115-c may send a respective feedback message for each TB associated with a CB set, where each TB may include multiple CBs in the CB set.

At 545, the base station 105-c may retransmit the at least partially preempted portion of the CB set regardless of whether at least one of the one or more feedback messages indicates an ACK or a NAK.

Fig. 6 illustrates a block diagram 600 of a device 605 that supports intra-device conflict handling in accordance with aspects of the present disclosure. The device 605 may be an example of aspects of a UE115 as described herein. The device 605 may include a receiver 610, a communication manager 615, and a transmitter 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 610 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 intra-device collision handling, etc.). Information may be communicated to other components of the device 605. The receiver 610 may be an example of aspects of the transceiver 920 described with reference to fig. 9. Receiver 610 may utilize a single antenna or a set of antennas.

The communication manager 615 may identify a first set of resources scheduled for downlink communication for the UE on a first downlink shared channel, identify a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps with the first set of resources, identify a set of rate matching resources configured for the second downlink shared channel, and obtain a downlink message on the second downlink shared channel by de-rate matching around the set of rate matching resources independent of any rate matching resources configured for the first downlink shared channel. In some examples, the first downlink shared channel may be associated with a first priority and the second downlink shared channel may be associated with a second priority. In some cases, the second priority may be greater than the first priority.

The communication manager 615 may also identify a set of CBs for a downlink shared channel of the UE, identify that a portion of the set of CBs is preempted by a transmission, assign ACK bits for each code block that is at least partially preempted by the transmission, determine ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted, determine one or more feedback messages based on the assigned or determined ACK bits or NAK bits for each CB of the set of CBs, and send the one or more feedback messages to report feedback for the set of CBs. In some examples, the first downlink shared channel may be associated with a first priority and the transmission may be associated with a second priority. In some cases, the second priority may be greater than the first priority. The communication manager 615 may be an example of aspects of the communication manager 910 described herein.

The communication manager 615, or subcomponents thereof, may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. When implemented in code executed by a processor, the functions of the communication manager 615, or subcomponents thereof, may be performed 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 615, or subcomponents thereof, may be physically distributed at various locations, including being distributed such that a portion of functionality is implemented at different physical locations by one or more physical components. In some examples, the communication manager 615, or subcomponents thereof, may be separate and distinct components in accordance with various aspects of the present disclosure. In some examples, the communication manager 615, 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 this disclosure, or a combination thereof.

In some examples, the communication manager 615 may be implemented as an integrated circuit or chipset for a mobile device modem and the receiver 610 and transmitter 620 may be implemented as analog components (e.g., amplifiers, filters, antennas, etc.) coupled with the mobile device modem to enable wireless transmission and reception over one or more frequency bands.

The actions performed by the communication manager 615 may be implemented as described herein to achieve one or more potential advantages. For example, the communication manager 615 may reduce communication latency and increase communication reliability at the UE115 by allowing the UE115 to properly process higher priority communications. Similarly, the communication manager 615 may reduce latency for lower priority communications at the UE115 by reducing the number of HARQ retransmissions. Improvements in communication latency and reliability may further conserve power at the UE115 and increase battery life (e.g., by reducing complexity and reducing the number of retransmissions to receive).

The transmitter 620 may transmit signals generated by other components of the device 605. In some examples, the transmitter 620 may be co-located with the receiver 610 in a transceiver module. For example, the transmitter 620 may be an example of aspects of the transceiver 920 described with reference to fig. 9. The transmitter 620 may utilize a single antenna or a set of antennas.

In some examples, the communication manager 615 may be implemented as an integrated circuit or chipset for a mobile device modem and the receiver 610 and the transmitter 620 may be implemented as analog components (e.g., amplifiers, filters, antennas, etc.) coupled with the mobile device modem to enable wireless transmission and reception.

The communication manager 615, as described herein, may be implemented to realize one or more potential advantages. Various implementations may enable the communication manager 615 to efficiently rate match overlapping scheduled downlink transmission resources and provide feedback based on the receipt of these resources. At least one implementation can enable the communication manager 615 to determine that a second transmission is prioritized over a first transmission based on a later scheduled second transmission.

Based on implementing the intra-device collision handling techniques as described herein, one or more processors of the device 605 (e.g., a processor controlling or in conjunction with one or more of the receiver 610, the communication manager 615, and the transmitter 620) may reduce latency of URLLC communications, improve communication reliability, and improve scheduling efficiency in wireless networks.

Fig. 7 illustrates a block diagram 700 of a device 705 that supports intra-device conflict handling in accordance with aspects of the present disclosure. The device 705 may be an example of aspects of the device 605 or the UE115 as described herein. The device 705 may include a receiver 710, a communication manager 715, and a transmitter 770. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 710 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 intra-device collision handling, etc.). Information may be communicated to other components of the device 705. Receiver 710 may be an example of aspects of transceiver 920 described with reference to fig. 9. Receiver 710 can utilize a single antenna or a set of antennas.

The communication manager 715 may be an example of aspects of the communication manager 615 as described herein. Communications manager 715 may include a first downlink channel identifying component 720, a second downlink channel identifying component 725, a rate matching resource identifying component 730, a downlink receiving component 735, a CB identifying component 740, a CB preemption component 745, an ACK assignment component 750, an ACK/NAK component 755, a feedback message component 760, and a feedback transmission component 765. The communication manager 715 may be an example of aspects of the communication manager 910 described herein.

The first downlink channel identifying component 720 may identify a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE. The second downlink channel identifying component 725 may identify a second set of resources scheduled for downlink communications for the UE on a second downlink shared channel, where the second set of resources at least partially overlaps the first set of resources. In some examples, the first downlink shared channel may be associated with a first priority and the second downlink shared channel may be associated with a second priority. In some cases, the second priority may be greater than the first priority.

The rate matching resource identifying component 730 can identify a set of rate matching resources configured for a second downlink shared channel. Downlink receiving component 735 can obtain the downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independent of any rate-matched resources configured for the first downlink shared channel.

The CB identification component 740 may identify a set of CBs for the downlink shared channel of the UE. The CB preemption component 745 may identify that a portion of the CB set is preempted by a transmission. ACK assigning component 750 can assign an ACK bit for each CB that is at least partially preempted by the transmission. In some examples, the first downlink shared channel may be associated with a first priority and the transmission may be associated with a second priority. In some cases, the second priority may be greater than the first priority. ACK/NAK component 755 may determine ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted. Feedback message component 760 may determine one or more feedback messages based on ACK bits or NAK bits assigned or determined for each CB in the CB set. The feedback transmission component 765 may send the one or more feedback messages to report feedback for the CB set.

A transmitter 770 may transmit signals generated by other components of the device 705. In some examples, transmitter 770 may be co-located with receiver 710 in a transceiver module. For example, the transmitter 770 may be an example of aspects of the transceiver 920 described with reference to fig. 9. The transmitter 770 may utilize a single antenna or a set of antennas.

The processor of UE115 (e.g., which controls receiver 710, transmitter 770, or transceiver 920, as described with reference to fig. 9) may reduce communication latency and increase communication reliability through rate matching and HARQ feedback processes (e.g., via implementations of the system components described with reference to fig. 8). Further, the processor of UE115 may receive an indication of rate matching resources to perform the processes described herein. The processor of the UE115 may use rate matching resources and HARQ feedback processes to improve communication latency and reliability to further conserve power and increase battery life at the UE115 (e.g., by reducing complexity and reducing the number of retransmissions to receive).

Fig. 8 illustrates a block diagram 800 of a communication manager 805 that supports intra-device conflict handling in accordance with aspects of the present disclosure. The communication manager 805 may be an example of aspects of the communication manager 615, the communication manager 715, or the communication manager 910 described herein. Communications manager 805 can include a first downlink channel identifying component 810, a second downlink channel identifying component 815, a rate matching resource identifying component 820, a downlink receiving component 825, a downlink controlling component 830, a CB identifying component 835, a CB preempting component 840, an ACK assigning component 845, an ACK/NAK component 850, a feedback message component 855, and a feedback transmitting component 860. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

The first downlink channel identifying component 810 can identify a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE.

The second downlink channel identifying component 815 may identify a second set of resources scheduled for downlink communications for the UE on a second downlink shared channel, where the second set of resources at least partially overlaps the first set of resources. In some cases, the second set of resources at least partially overlaps in time with the first set of resources. In some cases, the second set of resources at least partially overlaps in time and frequency with the first set of resources.

In some examples, the first downlink channel identifying component 810 and the second downlink channel identifying component 815 may identify a first priority associated with the first downlink shared channel and a second priority associated with the second downlink shared channel. In some examples, the second priority may be higher than the first priority.

Rate matching resource identifying component 820 can identify a set of rate matching resources configured for a second downlink shared channel. In some examples, rate matching resource identifying component 820 can receive an indication of a set of rate matching resources configured for a second downlink shared channel as a set of shared channel rate matching resources associated with a second priority, wherein the rate matching resources configured for a first downlink shared channel are associated with a first priority. In some cases, the rate matching resources configured for the first downlink shared channel at least partially overlap with a set of rate matching resources configured for the second downlink shared channel. In some cases, the indication of the set of shared channel rate matching resources is received via RRC signaling.

Downlink receiving component 825 can obtain the downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independently of any rate-matched resources configured for the first downlink shared channel. Downlink controlling component 830 may receive a first downlink control channel indicating a first set of resources. In some examples, downlink controlling component 830 may receive a second downlink control channel indicating a second set of resources. In some cases, the first downlink control channel includes first DCI for the first downlink shared channel, the first DCI indicating rate-matching resources configured for the first downlink shared channel. In some cases, the second downlink control channel includes a second DCI for a second downlink shared channel, the second DCI indicating a set of rate-matching resources configured for the second downlink shared channel.

The CB identification component 835 may identify a set of CBs for the downlink shared channel of the UE. The CB preemption component 840 can identify that a portion of the CB set is preempted by a transmission. In some examples, the first downlink shared channel may be associated with a first priority and the transmission may be associated with a second priority. In some cases, the second priority may be greater than the first priority. ACK assigning component 845 can assign an acknowledgement bit for each CB that is at least partially preempted by the transmission. In some examples, ACK assigning component 845 may refrain from assigning NAK feedback bits to each CB that is at least partially preempted by the transmission.

ACK/NAK component 850 may determine ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted. In some examples, ACK/NAK component 850 may perform a decoding process on each CB of the set of CBs that is not at least partially preempted. In some examples, ACK/NAK component 850 may determine feedback for each CB of the set of CBs that is not at least partially preempted based on the decoding process.

Feedback message component 855 may determine one or more feedback messages based on ACK bits or NAK bits assigned or determined for each CB in the CB set. Feedback transmission component 860 may transmit the one or more feedback messages to report feedback for the CB set. In some examples, a respective feedback message is sent for each CBG associated with a set of CBs, where each CBG includes a plurality of CBs in the set of CBs. In some examples, a respective feedback message is transmitted for each TB associated with a set of CBs, where each TB includes a plurality of CBs in the set of CBs.

Downlink controlling component 830 may receive a first downlink control channel indicating a first set of resources. In some examples, downlink controlling component 830 may receive a second downlink control channel indicating a second set of resources. In some cases, the first downlink control channel includes first DCI for the first downlink shared channel, the first DCI indicating rate-matching resources configured for the first downlink shared channel. In some cases, the second downlink control channel includes a second DCI for a second downlink shared channel, the second DCI indicating a set of rate-matching resources configured for the second downlink shared channel.

Fig. 9 shows a schematic diagram of a system 900 including a device 905 that supports intra-device conflict handling, according to aspects of the present disclosure. The device 905 may be an example of a device 605, device 705, or UE115, or include components of a device 605, device 705, or UE115, as described herein. The device 905 may include components for two-way voice and data communications, including components for sending communications and components for receiving communications, including a communication manager 910, an I/O controller 915, a transceiver 920, an antenna 925, a memory 930, and a processor 940. These components may be coupled via one or more buses, such as bus 945.

Communication manager 910 may identify a first set of resources scheduled for downlink communication for a UE on a first downlink shared channel, identify a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps with the first set of resources, identify a set of rate matching resources configured for the second downlink shared channel, and obtain a downlink message on the second downlink shared channel by de-rate matching around the set of rate matching resources independent of any rate matching resources configured for the first downlink shared channel.

In some examples, communication manager 910 may identify a first priority associated with a first downlink shared channel and a second priority associated with a second downlink shared channel. In some examples, the second priority may be higher than the first priority.

Communication manager 910 may also identify a set of CBs of a downlink shared channel for the UE, the downlink shared channel associated with a first priority, identify that a portion of the set of CBs is preempted by transmission of a second priority, wherein the second priority is higher than the first priority, assign ACK bits for each CB at least partially preempted by the transmission, determine ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted, determine one or more feedback messages based on the ACK bits or NAK bits assigned or determined for each CB of the set of CBs, and send the one or more feedback messages to report feedback for the set of CBs.

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

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

In some cases, the device 905 may include a single antenna 925, or the device 905 may have more than one antenna 925, which antennas 925 may be capable of simultaneously sending or receiving multiple wireless transmissions.

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

Processor 940 may include intelligent hardware devices (e.g., general purpose processors, DSPs, Central Processing Units (CPUs), microcontrollers, ASICs, FPGAs, programmable logic devices, split gate or transistor logic components, split hardware components, or any combinations thereof). In some cases, processor 940 may be configured to operate the memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 940. Processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., functions or tasks to support intra-device conflict handling).

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

Fig. 10 illustrates a block diagram 1000 of a device 1005 supporting intra-device conflict handling in accordance with aspects of the present disclosure. The device 1005 may be an example of aspects of a base station 105 as described herein. The device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 1010 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 intra-device collision handling, etc.). Information may be transferred to other components of the device 1005. The receiver 1010 may be an example of aspects of the transceiver 1320 described with reference to fig. 13. Receiver 1010 may utilize a single antenna or a set of antennas.

The communication manager 1015 may identify a set of CBs for a downlink shared channel for the UE, identifying that a portion of the set of CBs is at least partially preempted by a transmission. In some examples, the first downlink shared channel may be associated with a first priority and the transmission may be associated with a second priority. In some cases, the second priority may be greater than the first priority. The communication manager 1015 may receive one or more feedback messages from the UE reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that was at least partially preempted by the transmission, and retransmit the portion of the set of CBs that was at least partially preempted, regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK. The communication manager 1015 may be an example of some aspects of the communication manager 1310 described herein.

The communication manager 1015 or subcomponents thereof may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. When implemented in code executed by a processor, the functions of the communication manager 1015 or subcomponents thereof may be performed by a general purpose processor, DSP, ASIC, 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 1015, or subcomponents thereof, may be physically distributed at various locations, including being distributed such that a portion of functionality is implemented at different physical locations by one or more physical components. In some examples, the communication manager 1015, or subcomponents thereof, may be separate and distinct components in accordance with various aspects of the present disclosure. In some examples, the communication manager 1015, 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 this disclosure, or a combination thereof.

The transmitter 1020 may transmit signals generated by other components of the device 1005. In some examples, the transmitter 1020 may be co-located with the receiver 1010 in a transceiver module. For example, the transmitter 1020 may be an example of aspects of the transceiver 1320 described with reference to fig. 13. The transmitter 1020 may utilize a single antenna or a set of antennas.

Fig. 11 illustrates a block diagram 1100 of a device 1105 supporting intra-device conflict handling in accordance with aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or the base station 105 as described herein. The device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1140. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

Receiver 1110 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 intra-device collision handling, etc.). Information may be communicated to other components of the device 1105. The receiver 1110 may be an example of aspects of the transceiver 1320 described with reference to fig. 13. Receiver 1110 can utilize a single antenna or a set of antennas.

The communication manager 1115 may be an example of aspects of the communication manager 1015 as described herein. The communication manager 1115 may include a CB identification manager 1120, a CB preemption manager 1125, a feedback reception component 1130, and a CB retransmission component 1135. The communication manager 1115 may be an example of aspects of the communication manager 1310 described herein.

The CB identification manager 1120 may identify a CB set for the downlink shared channel of the UE.

The CB preemption manager 1125 may recognize that a portion of the CB set is preempted, at least in part, by a transmission.

In some examples, the CB preemption manager 1125 may identify a first priority associated with the downlink shared channel and a second priority associated with the transmission. In some examples, the second priority may be higher than the first priority.

Feedback receiving component 1130 may receive one or more feedback messages from the UE reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that was at least partially preempted by the transmission.

CB retransmission component 1135 may retransmit the at least partially preempted portion of the CB set regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK.

A transmitter 1140 may transmit signals generated by other components of the device 1105. In some examples, the transmitter 1140 may be co-located with the receiver 1110 in a transceiver module. For example, the transmitter 1140 may be an example of aspects of the transceiver 1320 described with reference to fig. 13. The transmitter 1140 may utilize a single antenna or a set of antennas.

Fig. 12 illustrates a block diagram 1200 of a communication manager 1205 that supports intra-device conflict handling in accordance with aspects of the disclosure. The communication manager 1205 may be an example of aspects of the communication manager 1015, the communication manager 1115, or the communication manager 1310 described herein. The communication manager 1205 may include a CB identification manager 1210, a CB preemption manager 1215, a feedback reception component 1220, and a CB retransmission component 1225. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

The CB identification manager 1210 may identify a CB set of downlink shared channels for the UE,

the CB preemption manager 1215 may identify that a portion of the CB set is at least partially preempted by a transmission.

In some examples, the CB preemption manager 1215 may identify a first priority associated with the downlink shared channel and a second priority associated with the transmission. In some examples, the second priority may be higher than the first priority.

Feedback receiving component 1220 may receive one or more feedback messages from the UE reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that was at least partially preempted by the transmission.

In some examples, a respective feedback message is received for each TB associated with a CB set, wherein each TB includes a plurality of CBs in the CB set.

In some examples, a respective feedback message is received for each CBG associated with a set of CBs, where each CBG includes a plurality of CBs in the set of CBs.

CB retransmission component 1225 may retransmit the at least partially preempted portion of the CB set regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK.

Fig. 13 shows a schematic diagram of a system 1300 including a device 1305 supporting intra-device conflict handling in accordance with aspects of the present disclosure. The device 1305 may be an example of, or include components of, the device 1005, the device 1105, or the base station 105 as described herein. Device 1305 may include components for two-way voice and data communications including components for transmitting communications and components for receiving communications including a communications manager 1310, a network communications manager 1315, a transceiver 1320, an antenna 1325, a memory 1330, a processor 1340, and an inter-station communications manager 1345. These components may be coupled via one or more buses, such as bus 1350.

The communication manager 1310 may identify a set of CBs for a downlink shared channel for a UE, identifying that a portion of the set of CBs is at least partially preempted by a transmission. In some examples, the communication manager 1310 may identify a first priority associated with the downlink shared channel and a second priority associated with the transmission. In some examples, the second priority may be higher than the first priority. Communication manager 1310 may receive one or more feedback messages from the UE reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that was at least partially preempted by the transmission, and resend the portion of the set of CBs that was at least partially preempted regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK.

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

The transceiver 1320 may communicate bi-directionally via one or more antennas, wired links, or wireless links, as described herein. For example, the transceiver 1320 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1320 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 1325. However, in some cases, the device may have more than one antenna 1325, which antennas 1325 may be capable of simultaneously sending or receiving multiple wireless transmissions.

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

Processor 1340 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combinations thereof). In some cases, processor 1340 may be configured to operate the memory array using a memory controller. In some cases, a memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks that support intra-device conflict handling).

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

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

FIG. 14 shows a flow diagram illustrating a method 1400 of supporting in-device conflict handling in accordance with aspects of the present disclosure. The operations of method 1400 may be implemented by UE115 or components thereof as described herein. For example, the operations of method 1400 may be performed by a communication manager as described with reference to fig. 6-9. In some examples, a UE may execute a 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 1405, the UE may identify a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE. The operations of 1405 may be performed in accordance with the methods described herein. In some examples, aspects of the operations of 1405 may be performed by the first downlink channel identifying component as described with reference to fig. 6-9.

At 1410, the UE may identify a second set of resources scheduled for downlink communications on a second downlink shared channel for the UE, where the second set of resources at least partially overlaps with the first set of resources. The operations of 1410 may be performed according to methods described herein. In some examples, aspects of the operations of 1410 may be performed by a second downlink channel identifying component as described with reference to fig. 6-9.

In some examples at 1410 or 1405, the UE may identify a first priority associated with the first downlink shared channel and a second priority associated with the second downlink shared channel. In some examples, the second priority may be higher than the first priority.

At 1415, the UE may identify a set of rate matching resources configured for a second downlink shared channel. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be performed by a rate matching resource identification component as described with reference to fig. 6-9.

At 1420, the UE may obtain the downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independently of any rate-matched resources configured for the first downlink shared channel. The operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operations of 1420 may be performed by a downlink receiving component as described with reference to fig. 6-9.

FIG. 15 shows a flow diagram illustrating a method 1500 of supporting in-device conflict handling in accordance with aspects of the present disclosure. The operations of method 1500 may be implemented by UE115 or components thereof as described herein. For example, the operations of method 1500 may be performed by a communication manager as described with reference to fig. 6-9. In some examples, a UE may execute a 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 1505, the UE may receive a first downlink control channel indicating a first set of resources. The operations of 1505 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1505 may be performed by a downlink control component as described with reference to fig. 6-9.

At 1510, the UE may identify a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be performed by a first downlink channel identifying component as described with reference to fig. 6-9.

At 1515, the UE may receive a second downlink control channel indicating a second set of resources. The operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operation of 1515 may be performed by a downlink control component as described with reference to fig. 6-9.

At 1520, the UE may identify a second set of resources scheduled for downlink communications on a second downlink shared channel for the UE, wherein the second set of resources at least partially overlaps the first set of resources. The operations of 1520 may be performed according to methods described herein. In some examples, aspects of the operations of 1520 may be performed by the second downlink channel identifying component as described with reference to fig. 6-9.

In some examples at 1510-1520, the UE may identify a first priority associated with the first downlink shared channel and a second priority associated with the second downlink shared channel. In some examples, the second priority may be higher than the first priority.

At 1525, the UE may identify a set of rate matching resources configured for a second downlink shared channel. The operations of 1525 may be performed according to the methods described herein. In some examples, aspects of the operations of 1525 may be performed by a rate matching resource identification component as described with reference to fig. 6-9.

At 1530, the UE can obtain the downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independent of any rate-matched resources configured for the first downlink shared channel. The operations of 1530 may be performed according to the methods described herein. In some examples, aspects of the operations of 1530 may be performed by a downlink receiving component as described with reference to fig. 6-9.

FIG. 16 shows a flow diagram illustrating a method 1600 of supporting intra-device conflict handling 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. 6-9. In some examples, a UE may execute a 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 identify a CB set for the downlink shared channel of the UE. The operations of 1605 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1605 may be performed by the CB identification component as described with reference to fig. 6-9.

At 1610, the UE may identify that a portion of the CB set is preempted by a transmission. The operations of 1610 may be performed according to methods described herein. In some examples, aspects of the operation of 1610 may be performed by a CB preemption component as described with reference to fig. 6-9.

In some examples at 1605 or 1610, the UE may identify a first priority associated with the first downlink shared channel and a second priority associated with the transmission. In some examples, the second priority may be higher than the first priority.

At 1615, the UE may assign an ACK bit for each CB that is at least partially preempted by the transmission. The operations of 1615 may be performed according to methods described herein. In some examples, aspects of the operation of 1615 may be performed by an ACK assignment component as described with reference to fig. 6-9.

At 1620, the UE may determine ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted. The operations of 1620 may be performed according to methods described herein. In some examples, aspects of the operation of 1620 may be performed by an ACK/NAK component as described with reference to fig. 6-9.

At 1625, the UE may determine one or more feedback messages based on the ACK bits or NAK bits assigned or determined for each CB in the CB set. The operations of 1625 may be performed according to methods described herein. In some examples, aspects of the operations of 1625 may be performed by a feedback message component as described with reference to fig. 6-9.

At 1630, the UE may send the one or more feedback messages to report feedback for the CB set. The operations of 1630 may be performed according to the methods described herein. In some examples, aspects of the operations of 1630 may be performed by a feedback transmission component as described with reference to fig. 6-9.

Fig. 17 shows a flow diagram illustrating a method 1700 of supporting in-device conflict handling in accordance with aspects of the present disclosure. The operations of method 1700 may be implemented by a UE115 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. 6-9. In some examples, a UE may execute a 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 1705, the UE may identify a CB set for the downlink shared channel of the UE. The operations of 1705 may be performed according to methods described herein. In some examples, aspects of the operations of 1705 may be performed by a CB identification component as described with reference to fig. 6-9.

At 1710, the UE may identify that a portion of the CB set is preempted by a transmission. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed by a CB preemption component as described with reference to fig. 6-9.

In some examples at 1705 or 1710, the UE may identify a first priority associated with the first downlink shared channel and a second priority associated with the transmission. In some examples, the second priority may be higher than the first priority.

At 1715, the UE may refrain from assigning NAK feedback bits to each CB that is at least partially preempted by the transmission. The operations of 1715 may be performed according to methods described herein. In some examples, aspects of the operations of 1715 may be performed by an ACK assignment component as described with reference to fig. 6-9.

At 1720, the UE may assign an ACK bit for each CB that is at least partially preempted by the transmission. The operations of 1720 may be performed according to methods described herein. In some examples, aspects of the operations of 1720 may be performed by an ACK assignment component as described with reference to fig. 6-9.

At 1725, the UE may determine ACK bits or NAK bits for each CB of the set of CBs that is not at least partially preempted. The operations of 1725 may be performed according to methods described herein. In some examples, aspects of the operation of 1725 may be performed by the ACK/NAK component as described with reference to fig. 6-9.

At 1730, the UE may determine one or more feedback messages based on the ACK bits or NAK bits assigned or determined for each CB in the CB set. The operations of 1730 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1730 may be performed by a feedback message component as described with reference to fig. 6-9.

At 1735, the UE may send the one or more feedback messages to report feedback for the CB set. The operations of 1735 may be performed in accordance with the methods described herein. In some examples, aspects of the operations of 1735 may be performed by a feedback transmission component as described with reference to fig. 6-9.

FIG. 18 shows a flow diagram illustrating a method 1800 of supporting in-device conflict handling in accordance with aspects of the present disclosure. The operations of method 1800 may be implemented by a base station 105 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. 10-13. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described herein. Additionally or alternatively, the base station may perform aspects of the functions described herein using dedicated hardware.

At 1805, the base station may identify a set of CBs for the downlink shared channel for the UE. The operations of 1805 may be performed in accordance with the methodologies described herein. In some examples, aspects of the operations of 1805 may be performed by a CB identification manager as described with reference to fig. 10-13.

At 1810, the base station may identify that a portion of the CB set is at least partially preempted by a transmission. The operations of 1810 may be performed in accordance with the methods described herein. In some examples, aspects of the operations of 1810 may be performed by a CB preemption manager as described with reference to fig. 10-13.

In some examples at 1805 or 1810, the base station may identify a first priority associated with the first downlink shared channel and a second priority associated with the transmission. In some examples, the second priority may be higher than the first priority.

At 1815, the base station may receive one or more feedback messages from the UE reporting feedback for the set of CBs, wherein at least one of the one or more feedback messages corresponds to the portion of the set of CBs that was at least partially preempted by the transmission. The operations of 1815 may be performed according to methods described herein. In some examples, aspects of the operations of 1815 may be performed by a feedback receiving component as described with reference to fig. 10-13.

At 1820, the base station may retransmit the portion of the set of CBs that was at least partially preempted, regardless of whether the at least one of the one or more feedback messages indicates an ACK or a NAK. The operations of 1820 may be performed according to methods described herein. In some examples, aspects of the operations of 1820 may be performed by a CB retransmission component as described with reference to fig. 10-13.

Example 1: a method for wireless communication at a User Equipment (UE), comprising: identifying a first set of resources scheduled for downlink communications on a first downlink shared channel for the UE; identifying a second set of resources scheduled for downlink communication for the UE on a second downlink shared channel, wherein the second set of resources at least partially overlaps the first set of resources; identifying a set of rate matching resources configured for the second downlink shared channel; obtaining a downlink message on the second downlink shared channel by de-rate matching around the set of rate-matched resources independently of any rate-matched resources configured for the first downlink shared channel.

Example 2: the method of example 1, further comprising: identifying a first priority associated with the first downlink shared channel and a second priority associated with the second downlink shared channel, wherein the second priority is higher than the first priority.

Example 3: the method of any of examples 1 or 2, wherein the rate matching resources configured for the first downlink shared channel at least partially overlap with the set of rate matching resources configured for the second downlink shared channel.

Example 4: the method of any of examples 1 to 3, further comprising: receiving a first downlink control channel indicating the first set of resources and receiving a second downlink control channel indicating the second set of resources.

Example 5: the method of example 4, wherein the first downlink control channel includes first Downlink Control Information (DCI) for the first downlink shared channel, the first DCI indicating the rate-matched resources configured for the first downlink shared channel.

Example 6: the method of any of examples 4 or 5, wherein the second downlink control channel includes second Downlink Control Information (DCI) for the second downlink shared channel, the second DCI indicating the set of rate-matching resources configured for the second downlink shared channel.

Example 7: the method of any of examples 1 to 6, further comprising: receiving an indication of the set of rate matching resources configured for the second downlink shared channel as the set of shared channel rate matching resources associated with the second priority, wherein the rate matching resources configured for the first downlink shared channel are associated with the first priority.

Example 8: the method of example 7, wherein the indication of the set of shared channel rate matching resources is received via Radio Resource Control (RRC) signaling.

Example 9: the method of any of examples 1 to 8, wherein the second set of resources at least partially overlaps in time with the first set of resources.

Example 10: the method of any of examples 1 to 9, wherein the second set of resources at least partially overlaps the first set of resources in time and frequency.

Example 11: a method for wireless communication at a User Equipment (UE), comprising: identifying a set of code blocks for a downlink shared channel for the UE; identifying that a portion of the set of code blocks is preempted by a transmission; assigning acknowledgement bits for each code block that is at least partially preempted by the transmission; determining acknowledgement bits or negative acknowledgement bits for each code block of the set of code blocks that is not at least partially preempted; determining one or more feedback messages based on the acknowledgement bits or the negative acknowledgement bits assigned or determined for each code block in the set of code blocks; and transmitting the one or more feedback messages to report feedback for the set of code blocks.

Example 12: the method of example 11, further comprising: identifying a first priority associated with the first downlink shared channel and a second priority associated with the transmission, wherein the second priority is higher than the first priority.

Example 13: the method of any of examples 11 or 12, further comprising: refraining from assigning Negative Acknowledgement (NAK) feedback bits to each code block that is at least partially preempted by the transmission.

Example 14: the method of any of examples 11 to 13, further comprising: transmitting a respective feedback message for each code block group associated with the code block set, wherein each code block group comprises a plurality of code blocks of the code block set.

Example 15: the method of any of examples 11 to 14, further comprising: transmitting a respective feedback message for each transport block associated with the set of code blocks, wherein each transport block comprises a plurality of code blocks of the set of code blocks.

Example 16: the method of any of examples 11 to 15, further comprising: performing a decoding process on each code block of the set of code blocks that is not at least partially preempted; and determine feedback for each code block of the set of code blocks that is not at least partially preempted based at least in part on the decoding process.

Example 17: a method for wireless communication at a base station, comprising: identifying a set of code blocks for a downlink shared channel for a User Equipment (UE); identifying that a portion of the set of code blocks is at least partially preempted by a transmission; receiving one or more feedback messages from the UE reporting feedback for the set of code blocks, wherein at least one of the one or more feedback messages corresponds to the portion of the set of code blocks that is at least partially preempted by the transmission; and re-transmitting the at least partially preempted portion of the set of code blocks regardless of whether the at least one of the one or more feedback messages indicates an acknowledgement or a negative acknowledgement.

Example 18: the method of example 17, further comprising: identifying a first priority associated with the first downlink shared channel and a second priority associated with the transmission, wherein the second priority is higher than the first priority.

Example 19: the method of any of examples 17 or 18, further comprising: receiving a respective feedback message for each transport block associated with the set of code blocks, wherein each transport block comprises a plurality of code blocks of the set of code blocks.

Example 20: the method of any of examples 17 to 19, further comprising: receiving a respective feedback message for each code block group associated with the code block set, wherein each code block group includes a plurality of code blocks in the code block set.

Example 21: an apparatus comprising at least one means for performing the method of any one of examples 1-20.

Example 22: an apparatus for wireless communication comprising: a processor, a memory coupled with the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of examples 1-20.

Example 23: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of any of examples 1-20.

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

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 much of the description, the techniques described herein may be applicable to ranges outside of LTE, LTE-A, LTE-A Pro or NR networks. For example, the described techniques may be applicable to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE)802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

The 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 components described in connection with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, 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 implementations 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 a combination of any of these. Features implementing functions may also be physically located at various locations, including being distributed such that some of the 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. Non-transitory storage media may be any available media 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), flash memory, Compact Disc (CD) ROM 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 computer-readable 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.

As used herein (including in the claims), an "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 of") indicates an inclusive list such that, for example, a list of at least one of A, B or C means a or B or C or AB or AC or BC or ABC (i.e., a and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, example steps 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" is interpreted.

In the drawings, similar components or features may have the same reference numerals. Further, 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 reference numeral is used in the specification, the description may be applicable to any one of the similar components having the same first reference numeral regardless of the second reference numeral or other subsequent reference numerals.

The example configurations described herein in connection with the descriptions set forth in the figures are not meant to be all examples that may be implemented 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 "advantageous over 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.