Pusch retransmission

Abstract

Aspects of the present disclosure relate to apparatuses and methods for PUSCH retransmission. In one aspect, a UE transmits a plurality of PUSCH transmissions through a plurality of TOs in a period of a CG configuration. The UE determines a plurality of resources for retransmission of at least some of the PUSCH transmissions, and retransmits the at least some of the PUSCH transmissions using the determined plurality of resources. In this manner, retransmission of multiple CG PUSCH transmissions may be scheduled at one time, thereby reducing latency and signaling overhead for performing multiple CG PUSCH retransmissions.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more particularly to devices and methods related to retransmission of physical uplink shared channel (PUSCH) transmissions. BACKGROUND

[0002] A wireless communication system can include one or more network communication devices (such as base stations), which can also be referred to as eNodeBs (eNBs), next generation NodeBs (gNBs), or other suitable terminology. Each network communication device (such as a base station) can support wireless communication for one or more user communication devices, which can also be referred to as user equipment (UE) or other suitable terminology. The wireless communication system can support wireless communication with one or more user communication devices by utilizing resources (e.g., time resources (such as symbols, time slots, subframes, frames, etc.) or frequency resources (such as subcarriers, carriers) of the wireless communication system). Additionally, the wireless communication system can support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable beyond 5G radio access technologies (e.g., sixth generation (6G)).

[0003] In this wireless communication system, physical uplink shared channel (PUSCH) transmission(s) can be dynamically scheduled by uplink (UL) grant in downlink control information (DCI), or the PUSCH transmission(s) can also correspond to configured grant (CG) Type 1 or Type 2. Moreover, to achieve low latency requirement and large packet size, it has been decided in the third generation partnership project (3GPP) to configure multiple CG PUSCH transmission occasions (TOs) in a period of a single CG PUSCH configuration. Research on PUSCH retransmission is still needed. SUMMARY

[0004] The present disclosure relates to methods, apparatuses, and systems that support PUSCH retransmission. By determining multiple resources for retransmission of at least some of the multiple CG PUSCH transmissions, and retransmitting the at least some of the CG PUSCH transmissions using the determined multiple resources, retransmission of the multiple CG PUSCH transmissions in a period of a CG configuration can be scheduled at one time, thereby reducing latency and signaling overhead for performing the multiple CG PUSCH retransmissions.

[0005] In one aspect, some implementations of the method and apparatus described herein can include transmitting, to a base station, a plurality of PUSCH transmissions over a plurality of transmission occasions (TOs) in a period of a CG configuration; determining a plurality of resources for retransmission of at least some of the PUSCH transmissions; and retransmitting, to the base station, the at least some of the PUSCH transmissions using the determined plurality of resources.

[0006] Some implementations of the method and apparatus described herein can also include retransmitting the at least some of the PUSCH transmissions based on DCI received from the base station.

[0007] Some implementations of the method and apparatus described herein can also include retransmitting the at least some of the PUSCH transmissions based on a timer configured by the base station.

[0008] In some implementations of the method and apparatus described herein, a cyclic redundancy check (CRC) code of the DCI is scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) of the user equipment.

[0009] In some implementations of the method and apparatus described herein, the TDRA table is determined based on a format of the DCI.

[0010] In some implementations of the method and apparatus described herein, the DCI indicates N resources by an index of a time domain resource allocation (TDRA) table, N is an integer greater than 1, and the plurality of resources for retransmission of the at least some of the PUSCH transmissions are based on the N resources.

[0011] In some implementations of the method and apparatus described herein, a number of resources for retransmission of the at least some of the PUSCH transmissions is the same as or greater than N.

[0012] In some implementations of the method and apparatus described herein, assuming a number of resources for retransmission of the at least some of the PUSCH transmissions is M and M is less than N, a first M or a last M of the N resources are determined as the resources for retransmission of the at least some of the PUSCH transmissions; or the resources for retransmission of the at least some of the PUSCH transmissions are determined based on a first bitmap in the DCI.

[0013] In some implementations of the method and apparatus described herein, the plurality of resources for retransmission of the at least some of the PUSCH transmissions are in consecutive slots and have a same start and length indicator value (SLIV).

[0014] In some implementations of the methods and apparatuses described herein, the DCI indicates a first slot of a first resource of the plurality of resources for retransmission of at least some of the PUSCH transmissions and the SLIV.

[0015] In some implementations of the methods and apparatuses described herein, the first slot is indicated by one of the following in the DCI: a single K2 value in a case where only one K2 value is indicated in the DCI; or a first K2 value in a case where more than one K2 value is indicated in the DCI, where the K2 value is used to indicate a number of slots between a slot in which the DCI is received and the first slot.

[0016] In some implementations of the methods and apparatuses described herein, the DCI indicates a first resource of the plurality of resources for retransmission of at least some of the PUSCH transmissions via an index of a TDRA table, where each row of the TDRA table includes one SLIV; or in a case where there is more than one SLIV in an indexed row of the TDRA table, the first resource is determined via a first or last SLIV from the TDRA table.

[0017] In some implementations of the methods and apparatuses described herein, the DCI includes a second bitmap to indicate whether at least some of the plurality of PUSCH transmissions are to be retransmitted, and a bit of the second bitmap has a one-to-one mapping to at least a portion of the plurality of TOs.

[0018] In some implementations of the methods and apparatuses described herein, a number of bits in the second bitmap is equal to a number of the plurality of TOs.

[0019] In some implementations of the methods and apparatuses described herein, a number of bits in the second bitmap is equal to a maximum number K of PUSCH transmissions indicated by the TDRA table.

[0020] In some implementations of the methods and apparatuses described herein, K is greater than a number L of the plurality of TOs, and a first L or last L bits of the second bitmap are used to indicate whether at least some of the plurality of PUSCH transmissions are to be retransmitted; K is less than L, and K bits of the second bitmap are used to indicate whether a first K or last K of the at least some of the plurality of PUSCH transmissions are to be retransmitted; or K is equal to L, and the K bits of the second bitmap are used to indicate whether at least some of the plurality of PUSCH transmissions are to be retransmitted.

[0021] In some implementations of the method and apparatus described herein, the DCI includes a second bitmap to indicate whether at least some of the plurality of PUSCH transmissions corresponding to a hybrid automatic repeat request (HARQ) process number (HPN) are to be retransmitted, and a number of bits in the second bitmap is equal to a maximum number of HPNs configured for the CG configuration.

[0022] In some implementations of the method and apparatus described herein, the second bitmap is related to a new data indicator (NDI) field and / or a redundancy version (RV) field of the DCI.

[0023] In some implementations of the method and apparatus described herein, the DCI is a first DCI, and a second DCI having a same format as the first DCI is received, and the second DCI includes a CRC code scrambled by a cell radio network temporary identifier (C-RNTI) of the user equipment, and the first DCI is aligned in size with the second DCI by one of: adding padding bits to an NDI field or an RV field of the first DCI or a second other DCI such that a number of bits in the NDI field or the RV field is equal to a maximum between X and a number of PUSCH transmissions indicated by a TDRA table of the second DCI, where X is a number of TOs in a periodicity of the CG configuration, or X is a maximum number of HPNs for the CG configuration; or adding padding bits to one of the first DCI and the second DCI that has a smaller size.

[0024] Some implementations of the method and apparatus described herein can further include determining that a CG PUSCH transmission corresponding to a HPN indicated by a HPN field of the DCI is to be retransmitted, and determining that one or more CG PUSCH transmissions corresponding to HPNs greater than the HPN are to be retransmitted. Some implementations of the method and apparatus described herein can include determining that one or more CG PUSCH transmissions corresponding to a plurality of HPNs greater than the HPN are to be retransmitted, where a number of the HPNs is indicated by radio resource control (RRC) signaling or the DCI.

[0025] Some implementations of the method and apparatus described herein can further include determining a RV for retransmission of at least some of the PUSCH transmissions.

[0026] In some implementations of the methods and apparatuses described herein, a RV field of the DCI indicates the RVs, retransmissions of at least some of the PUSCH transmissions have the same RV; a number of the RV fields of the DCI is equal to a number of the multiple TOs, and each RV field corresponds to one of the multiple TOs; or a number of the RV fields of the DCI is equal to a maximum number of HPNs configured for the CG configuration, and each RV field corresponds to one of the number of HPNs; where the RV field includes 2 bits or 1 bit.

[0027] In some implementations of the methods and apparatuses described herein, the RVs for the retransmissions of at least some of the PUSCH transmissions are different from the RVs for the original transmissions of the PUSCH transmissions.

[0028] In some implementations of the methods and apparatuses described herein, a number of the RV fields of the DCI is equal to a maximum number of PUSCH transmissions K indicated by the TDRA table. In some implementations of the methods and apparatuses described herein, K is greater than a number L of the multiple TOs, and a first L or a last L of the RV fields of the DCI are used for the retransmissions of at least some of the PUSCH transmissions; K is less than L, and K RV fields of the DCI are used for a first K or a last K of the retransmissions of at least some of the PUSCH transmissions; or K is equal to L, and the K RV fields of the DCI are used for the retransmissions of at least some of the PUSCH transmissions.

[0029] In some implementations of the methods and apparatuses described herein, the DCI is a first DCI, and a second DCI is received, the second DCI has a same format as the first DCI, and the second DCI includes a CRC code scrambled by a C-RNTI of the user equipment, and the first DCI is aligned in size with the second DCI by one of: adding padding bits to a RV field of the first DCI or the second DCI such that a number of bits in the RV field is equal to a maximum of a number of the multiple TOs and a maximum number of PUSCH transmissions indicated by a TDRA table of the second DCI; adding padding bits to a RV field of the first DCI or the second DCI such that a number of bits in the RV field is equal to a maximum of a number of HPNs and a maximum number of PUSCH transmissions indicated by a TDRA table of the second DCI; or adding padding bits to the one of the first DCI and the second DCI that has a smaller size.

[0030] In some implementations of the methods and apparatuses described herein, the timer is started or restarted after a first or a last valid TO of the multiple TOs; or the timer is started or restarted after a last TO in a time domain that is not indicated by the user equipment as unused.

[0031] Some implementations of the methods and apparatuses described herein can further include determining that PUSCH transmissions corresponding to the HPN are to be retransmitted in the case that no acknowledgement (ACK) for the HPN is received in the CG period after the timer expires.

[0032] In another aspect, some implementations of the methods and apparatuses described herein can include receiving, from a user equipment, a plurality of PUSCH transmissions in a period of a CG configuration, determining a plurality of resources for retransmission of at least some of the PUSCH transmissions, and using the determined plurality of resources to receive retransmissions of at least some of the PUSCH transmissions from the user equipment.

[0033] Some implementations of the methods and apparatuses described herein can further include receiving at least some of the PUSCH transmissions retransmitted by the user equipment based on the DCI.

[0034] Some implementations of the methods and apparatuses described herein can further include configuring a timer for retransmission of at least some of the PUSCH transmissions and receiving the retransmissions based on the timer.

[0035] In some implementations of the methods and apparatuses described herein, the CRC code of the DCI is scrambled by a configured CS-RNTI of the user equipment

[0036] In some implementations of the methods and apparatuses described herein, the TDRA table is determined based on a format of the DCI.

[0037] In some implementations of the methods and apparatuses described herein, the DCI indicates N resources by an index of the TDRA table, N is an integer greater than 1, and the plurality of resources for retransmission of at least some of the PUSCH transmissions can be based on the N resources.

[0038] In some implementations of the methods and apparatuses described herein, the number of resources for retransmission of at least some of the PUSCH transmissions is the same as or greater than N.

[0039] In some implementations of the methods and apparatuses described herein, assuming that the number of resources for retransmission of at least some of the PUSCH transmissions is M and M is less than N, the first M or the last M of the N resources are determined as the resources for retransmission of at least some of the PUSCH transmissions; or the resources for retransmission of at least some of the PUSCH transmissions are determined based on a first bitmap in the DCI.

[0040] In some implementations of the methods and apparatuses described herein, the plurality of resources for retransmission of at least some of the PUSCH transmissions are in consecutive slots and have the same SLIV.

[0041] In some implementations of the methods and apparatuses described herein, the DCI indicates a first slot and the SLIV for a first resource of the plurality of resources for retransmission of at least some of the PUSCH transmissions.

[0042] In some implementations of the methods and apparatuses described herein, the first slot is indicated by one of the following in the DCI: a single K2 value in a case where only one K2 value is indicated in the DCI; a first K2 value in a case where more than one K2 value is indicated in the DCI, where the K2 value is used to indicate a number of slots between a slot in which the DCI is received and the first slot.

[0043] In some implementations of the methods and apparatuses described herein, the DCI indicates a first resource of the plurality of resources for retransmission of at least some of the PUSCH transmissions via an index of a TDRA table, where each row of the TDRA table includes one SLIV; or in a case where there is more than one SLIV in an indexed row of the TDRA table, the first resource is determined via a first or last SLIV from the TDRA table.

[0044] In some implementations of the methods and apparatuses described herein, the DCI includes a second bitmap to indicate whether at least some of the plurality of PUSCH transmissions are to be retransmitted, and a bit of the second bitmap has a one-to-one mapping to at least a portion of the plurality of TOs.

[0045] In some implementations of the methods and apparatuses described herein, a number of bits in the second bitmap is equal to a number of the plurality of TOs.

[0046] In some implementations of the methods and apparatuses described herein, a number of bits in the second bitmap is equal to a maximum number K of PUSCH transmissions indicated by the TDRA table.

[0047] In some implementations of the methods and apparatuses described herein, K is greater than a number L of the plurality of TOs, and a first L or a last L bits of the second bitmap are used to indicate whether at least some of the plurality of PUSCH transmissions are to be retransmitted; K is less than L, and K bits of the second bitmap are used to indicate whether a first K or a last K of the at least some of the plurality of PUSCH transmissions are to be retransmitted; or K is equal to L, and the K bits of the second bitmap are used to indicate whether at least some of the plurality of PUSCH transmissions are to be retransmitted.

[0048] In some implementations of the method and apparatus described herein, the DCI includes a second bitmap to indicate whether at least some of the plurality of PUSCH transmissions corresponding to the HPNs are to be retransmitted, and a number of bits in the second bitmap is equal to a maximum number of HPNs configured for the CG configuration.

[0049] In some implementations of the method and apparatus described herein, the second bitmap is related to a DCI NDI field and / or a RV field.

[0050] In some implementations of the method and apparatus described herein, the DCI is a first DCI, and a second DCI having a same format as the first DCI is received, and the second DCI includes a CRC code scrambled by a C-RNTI of the user equipment, and the first DCI is aligned in size with the second DCI by one of: adding padding bits to an NDI field or a RV field of the first DCI or a second other DCI such that a number of bits in the NDI field or the RV field is equal to a maximum between X and a number of PUSCH transmissions indicated by a TDRA table of the second DCI, where X is a number of TOs in a period of the CG configuration, or X is a maximum number of HPNs for the CG configuration; or adding padding bits to one of the first DCI and the second DCI that has a smaller size.

[0051] Some implementations of the method and apparatus described herein can further include receiving a retransmission of a CG PUSCH transmission corresponding to an HPN indicated by an HPN field of the DCI; and receiving a retransmission of one or more CG PUSCH transmissions corresponding to HPNs greater than the HPN. Some implementations of the method and apparatus described herein can include receiving a retransmission of one or more CG PUSCH transmissions corresponding to a plurality of HPNs greater than the HPN, where a number of the HPNs is indicated by RRC signaling or DCI.

[0052] Some implementations of the method and apparatus described herein can further include determining a RV for the retransmission of at least some of the PUSCH transmissions.

[0053] In some implementations of the method and apparatus described herein, the RV field of the DCI indicates the RV, the retransmission of at least some of the PUSCH transmissions has the same RV; a number of the RV fields of the DCI is equal to a number of the plurality of TOs, and each RV field corresponds to one of the plurality of TOs; or a number of the RV fields of the DCI is equal to a maximum number of HPNs configured for the CG configuration, and each RV field corresponds to one of the number of HPNs; where the RV field includes 2 bits or 1 bit.

[0054] In some implementations of the methods and apparatuses described herein, the RVs for retransmissions of at least some of the PUSCH transmissions are different from the RVs for original transmissions of the PUSCH transmissions.

[0055] In some implementations of the methods and apparatuses described herein, a number of RV fields of the DCI is equal to a maximum number of PUSCH transmissions K indicated by the TDRA table. In some implementations of the methods and apparatuses described herein, K is greater than a number of the multiple TOs L, and a first L or a last L RV fields of the DCI are used for retransmissions of at least some of the PUSCH transmissions; K is less than L, and K RV fields of the DCI are used for a first K or a last K retransmissions of at least some of the PUSCH transmissions; or K is equal to L, and the K RV fields of the DCI are used for retransmissions of at least some of the PUSCH transmissions.

[0056] In some implementations of the methods and apparatuses described herein, the DCI is a first DCI, and a second DCI is received, the second DCI has a same format as the first DCI, and the second DCI includes a CRC code scrambled by a C-RNTI of the user equipment, and wherein the first DCI is aligned in size with the second DCI by one of: adding padding bits to RV fields of the first DCI or the second DCI such that a number of bits in the RV fields is equal to a maximum between a number of the multiple TOs and a maximum number of PUSCH transmissions indicated by a TDRA table of the second DCI; adding padding bits to the RV fields of the first DCI or the second DCI such that the number of bits in the RV fields is equal to a maximum between a number of the HPNs and the maximum number of PUSCH transmissions indicated by the TDRA table of the second DCI; or adding padding bits to the one of the first DCI and the second DCI that has a smaller size.

[0057] In some implementations of the methods and apparatuses described herein, the timer is started or restarted after a first or a last valid TO of the multiple TOs; or the timer is started or restarted after a last TO in a time domain that is not indicated by the user equipment as unused.

[0058] Some implementations of the methods and apparatuses described herein can further include receiving a retransmission of a PUSCH transmission corresponding to the HPN after the timer expires, where no ACK for the PUSCH transmission corresponding to the HPN is sent within the CG period. BRIEF DESCRIPTION OF DRAWINGS

[0059] Figure 1A FIG. 1 illustrates an example of a wireless communications system that supports performing PUSCH retransmissions in accordance with aspects of the present disclosure.

[0060] Figure 1B FIG. illustrates an example diagram of CG PUSCH TO in a CG configuration period.

[0061] Figure 2 FIG. illustrates an example signaling diagram of an example process for performing PUSCH retransmission, in accordance with aspects of the present disclosure.

[0062] Figure 3 FIG. illustrates an example diagram for resource for PUSCH retransmission determined from resources indicated by DCI, in accordance with aspects of the present disclosure.

[0063] Figure 4 FIG. illustrates an example diagram for resource for PUSCH retransmission in consecutive slots and SLIV indicated by DCI, in accordance with aspects of the present disclosure.

[0064] Figure 5 FIG. illustrates an example diagram of a bitmap indicating whether PUSCH transmissions will be retransmitted, in accordance with aspects of the present disclosure.

[0065] Figure 6 FIG. illustrates an example diagram of PUSCH transmissions corresponding to certain HPNs will be retransmitted, in accordance with aspects of the present disclosure.

[0066] Figure 7 FIG. illustrates an example of a device that supports performing PUSCH retransmission, in accordance with aspects of the present disclosure.

[0067] Figure 8 FIG. illustrates an example of another device that supports performing PUSCH retransmission, in accordance with aspects of the present disclosure.

[0068] Figure 9 FIG. illustrates an example of a processor that supports performing PUSCH retransmission, in accordance with aspects of the present disclosure.

[0069] Figure 10 FIG. illustrates an example of another processor that supports performing PUSCH retransmission, in accordance with aspects of the present disclosure.

[0070] Figure 11 FIG. illustrates a flow diagram of a method that supports performing PUSCH retransmission, in accordance with aspects of the present disclosure.

[0071] Figure 12 FIG. illustrates a flow diagram of another method that supports performing PUSCH retransmission, in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0072] The principles of the present disclosure will now be described with reference to some embodiments. It will be appreciated that these embodiments are described for purposes of illustration only and to aid in the understanding of and implementation of the present disclosure, and are not intended to be limiting of the scope of the present disclosure. Embodiments described herein can be implemented in various ways, other than those described below.

[0073] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0074] Reference throughout this disclosure to “one embodiment,” “one example embodiment,” “an embodiment,” “some embodiments,” and so on, indicate that a described embodiment can include a particular feature, structure, or characteristic, but every embodiment can not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one of ordinary skill in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described or claimed. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0075] It should be understood that, although the terms “first” and “second” and the like can be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could also be termed a second element, and, similarly, a second element could also be termed a first element without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0076] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” “has” and / or “including” specify the presence of stated features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or groups thereof. As used herein, “at least one of ” and “one or more of ” and the like, wherein the list of two or more elements is

[0077] In a wireless communication system, PUSCH transmission(s) can be dynamically scheduled by UL grant in DCI, e.g., DCI format 0_1, the DCI can indicate SLIV by index of TDRA table, which can be: pusch-Config pusch-TimeDomainAllocationListForMultiPUSCH containing rows indicating SLIVs for two to eight consecutive PUSCH resource allocations, K 2 indicating the slot in which the UE should transmit the first of the multiple PUSCHs. Each PUSCH has a separate SLIV and mapping type. The number of scheduled PUSCHs is signaled by the number of indicated valid SLIVs in the row of the TDRA table signaled in DCI format 0_1. pusch-TimeDomainAllo cationListForMultiPUSCH For example, the TDRA table can be shown as Table 1, for index = 2, there are 4 SLIVs. Table 1: Example TDRA table.

[0078] For pusch-Config in pusch-Config, TimeDomainAllocationListForMultiPUSCH- r17 Each PUSCH has a separate SLIV, mapping type, and K 2 The number of scheduled PUSCHs is signaled by the number of indicated SLIVs in the row of the TDRA table signaled in DCI format 0_1. pusch-TimeDomainAllocationListForMultiPUSCH-r17

[0079] If a UE is configured with pusch-TimeDomainAllocationListForMultiPUSCH-r17 where one or more rows contain multiple SLIVs for PUSCH on the UL bandwidth part (BWP) of a serving cell, and the UE is indicated by DCI format 0_1 a retransmission of a PUSCH, where the PUSCH corresponds to a configured grant Type 1 or Type 2, the UE does not expect the number of SLIVs indicated by the DCI in the row of pusch-TimeDomainAllocationListForMultiPUSCH-r17 to be more than 1. That is, a single DCI cannot schedule multiple SLIVs to retransmit a PUSCH corresponding to a configured grant Type 1 or Type 2.

[0080] ​​For DCI format 0_1, there may be multiple NDI bits used to indicate whether a scheduled transport block (TB) is a retransmission or the initial transmission. The number of NDI bits is determined based on the maximum number of PUSCHs in the TDRA table. Multiple RV bits used to indicate multiple scheduled TBs are either 0 or 2, and the number of RV bits is also determined based on the maximum number of PUSCHs in the TDRA table. The least significant bit (LSB) of the RV field and the NDI field corresponds accordingly to the last scheduled PUSCH indicated by the TDRA information field. There may be an HPN field indicating the first HPN of the first scheduled PUSCH, and the HPNs of other PUSCHs are incremented sequentially in the order they were scheduled.

[0081] For example, the maximum number of PUSCHs in the TDRA table is 4. Then, the DCI can have 4 bits of NDI and 4 bits of RV. Assuming two SLIVs are scheduled by the TDTA field in the DCI, and the initial HPN is also indicated by the DCI as 1, this means that 2 TBs are scheduled by the DCI, and the corresponding HPNs are 1 and 2. The 4-bit NDI can be "0010", and the LSB bit "10" indicates the NDI corresponding to PUSCH transmission 1 and PUSCH transmission 2. The RV "0011" indicates that the corresponding RV for these two TBs is 2. For PUSCHs that are retransmissions of the initial transmission, this is determined by whether the NDI bits used for HPN are inverted. This means that multiple scheduled PUSCHs can include some initial transmissions and some retransmissions.

[0082] As mentioned above, (multiple) PUSCH transfers can also correspond to CG type 1 or type 2. The configuration of authorized type 1 PUSCH transfers is semi-statically configured to respond to the receipt of... rrc-ConfiguredUplinkGrant of configuredGrantConfig When operating with higher-level parameters, it does not require detection of UL authorization in the DCI. Configure authorization type 2 PUSCH transmission when receiving data that does not include... rrc-ConfiguredUplinkGrant higher-level parameters configuredGrantConfig Then, it is semi-persistently scheduled by the UL authorization in the effectively activated DCI.

[0083] The UE will be configured with one or more CG configurations, and for each CG configuration, a periodic P CG types are provided.

[0084] Higher layer parameters cg-nrofSlots Provides the number of consecutive time slots allocated within the configuration authorization period. Higher-layer parameters. cg-nrofPUSCH-InSlot The number of consecutive PUSCH allocations within a time slot is provided, where the first PUSCH allocation follows the higher-layer parameters for type 1 PUSCH transmissions. timeDomainAllocationor according to higher layer configuration of TS 38.321, and UL grant received on DCI for Type 2 PUSCH transmission, and the remaining PUSCH allocation has the same length and PUSCH mapping type, and is appended after the previous allocation without any gap. The same combination of starting symbol and length and PUSCH mapping type repeats on the consecutively allocated slots. A retransmission timer can be configured, and the timer is started after the PUSCH transmission, if the UE has not received the corresponding ACK for the corresponding HPN after the timer expires, the TB will be retransmitted by a new CG PUSCH.

[0085] The retransmission of CG PUSCH can also be scheduled by a DCI with CRC scrambled by CS-RNTI with NDI = 1. The DCI can indicate the retransmission of CG PUSCH by indicating the corresponding HPN. For example, the DCI with CRC scrambled by CS-RNTI with NDI = 1 also indicates HPN = 1, which means the CG PUSCH with HPN = 1 should be retransmitted according to the DCI.

[0086] With the development of wireless communication technology, scenarios with traffic of low latency and large packet size have emerged. For example, extended reality (XR) is a broad term that encompasses augmented reality (AR), mixed reality (MR), and virtual reality (VR). Together with cloud computing, XR applications often require high throughput and low latency, and have large packet size and variable data packet size. In order to achieve the low latency requirement and large packet size, it has been decided in 3GPP to configure multiple CG PUSCH TOs in a period of a single CG PUSCH configuration.

[0087] For some scenarios (e.g., XR service), reliability and latency are important requirements, and if multiple TOs are configured in a CG period, and multiple TBs can be transmitted in a CG period, in order to guarantee reliability, retransmission should be supported. If the retransmission is scheduled by DCI, according to the traditional specification, one DCI with CRC scrambled by CS-RNTI with NDI = 1 can only schedule one TB at a time, if multiple TBs need to be retransmitted, multiple DCIs should be sent, which will increase the latency, therefore, how to use a single DCI to schedule multiple CG retransmissions needs to be studied. In addition, if the retransmission is based on a timer, when the timer should be started should be determined.

[0088] In view of the above and other aspects, embodiments of the present disclosure provide a solution for PUSCH retransmission. In the solution, a UE transmits a plurality of PUSCH transmissions to a base station through a plurality of TOs in a CG configured period, determines a plurality of resources for retransmission of at least some of the PUSCH transmissions, and retransmits the at least some of the PUSCH transmissions using the determined plurality of resources. In some implementations of the solution, the UE can retransmit the at least some of the PUSCH transmissions based on DCI received from the base station. In other implementations of the solution, the UE can retransmit the at least some of the PUSCH transmissions based on a timer configured by the base station.

[0089] In this way, retransmission of a plurality of CG PUSCH transmissions in a CG configured period can be scheduled at one time, thereby reducing latency and signaling overhead for performing the plurality of CG PUSCH retransmissions.

[0090] Aspects of the present disclosure are described in the context of a wireless communications system.

[0091] Figure 1A One example of a wireless communications system 100 that supports performing PUSCH retransmission is illustrated in accordance with aspects of the present disclosure. The wireless communications system 100 can include one or more network entities 102 (also referred to as network equipment (NE)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 can support various radio access technologies. In some implementations, the wireless communications system 100 can be a 4G network, such as an LTE network or a LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 can be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 can be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 can support beyond-5G radio access technologies. Additionally, the wireless communications system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0092] One or more network entities 102 can be dispersed throughout the geographic area to provide wireless communication coverage for the wireless communication system 100. One or more of the network entities 102 described herein can be or include or can be referred to as a network node, base station, network element, radio access network (RAN), base transceiver station, access point, NodeB, eNodeB (eNB), next generation NodeB (gNB), or some other suitable terminology. The network entities 102 and the UEs 104 can communicate via communication links 110, which can be wireless connections or wired connections. For example, the network entities 102 and the UEs 104 can perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0093] The network entities 102 can provide a geographic coverage area 112 for which the network entities 102 can provide service (e.g., voice, video, packet data, messaging, broadcast, etc.) within a geographic coverage area 112 for one or more UEs 104. For example, the network entities 102 and the UEs 104 can support wireless communication of signals related to service (e.g., voice, video, packet data, messaging, broadcast, etc.) in accordance with one or more radio access technologies. In some implementations, the network entities 102 can be mobile, such as satellites associated with non-terrestrial networks. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. Information and signals described herein can be represented using various technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0094] The one or more UEs 104 can be dispersed throughout the geographic area of the wireless communication system 100. A UE 104 can comprise or be referred to as a mobile device, wireless device, remote device, remote unit, handset, or subscriber device, or some other suitable terminology. In some implementations, a UE 104 can be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, a UE 104 can be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples. In some implementations, a UE 104 can be static or have limited mobility in the wireless communication system 100. In some other implementations, a UE 104 can have mobility in the wireless communication system 100.

[0095] One or more UEs 104 can be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. As shown in FIG. 1, a UE 104 can be able to communicate with various types of devices, such as the network entity 102, other UEs 104, or a network device (e.g., core network 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network device). Additionally, or alternatively, a UE 104 can support communication with other network entities 102 or UEs 104 that can act as relays in the wireless communication system 100.

[0096] A UE 104 can also be able to support wireless communications with other UEs 104 directly, through a communication link 114. For example, a UE 104 can support wireless communications with another UE 104 directly, through a device-to-device (D2D) communication link. In some implementations, such as a vehicle-to-vehicle (V2V) deployment, a vehicle-to- everything (V2X) deployment, or a cellular V2X deployment, the communication link 114 can be referred to as a sidelink. For example, a UE 104 can support wireless communications with another UE 104 directly, through a PC5 interface.

[0097] A network entity 102 can support communication with the core network 106, or with another network entity 102, or both. For example, a network entity 102 can interface with a core network 106 through one or more backhaul links 116 (e.g., via an SI, N2, N3, or another network interface). The network entities 102 can communicate with one another through backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 can communicate directly with one another (e.g., between network entities 102). In some other implementations, the network entities 102 can communicate with, or indirectly through, one another (e.g., via core network 106). In some implementations, one or more network entities 102 can include subcomponents, such as an access network entity, which can be one example of an access node controller (ANC). An ANC can communicate with one or more UEs 104 through one or more other access network transmission entities, which can be referred to as a radio head, a smart radio head, or a transmission reception point (TRP).

[0098] In some implementations, the network entity 102 can be configured in a disaggregated architecture that can be configured to utilize protocol stacks that are physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 can include a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near-RT RIC, a non-RT RIC), a service management and orchestration (SMO) system, or any combination thereof.

[0099] The RU can also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entity 102 in a disaggregated RAN architecture can be co-located, or one or more components of the network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the disaggregated RAN architecture can be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0100] The functional split between the CU, the DU, and the RU can be flexible and can depend on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, the DU, or the RU to support different functionalities. For example, a functional split of a protocol stack can be employed between the CU and the DU, such that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and the one or more DUs or RUs can host lower protocol layers, such as layer 1 (LI) (e.g., physical layer (PHY)) or L2 (e.g., radio link control layer (RLC), medium access control layer (MAC)) functions and signaling, and can be at least partially controlled by the CU 160 per each.

[0101] Additionally or alternatively, the functional split of the protocol stack can also be employed between the DU and the RU, such that the DU can support one or more layers of the protocol stack, and the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU, or between the DU and the RU, can be within a protocol layer (e.g., some functions for a protocol layer can be performed by one of the CU, the DU, or the RU, while other functions for the protocol layer are performed by another one of the CU, the DU, or the RU).

[0102] The CU can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via a midhaul communication link (e.g., Fl, Flc, Flu), while the DU can be connected to one or more RUs via a front-haul communication link (e.g., open front-haul (FH) interface). In some implementations, the midhaul or front-haul communication link can be implemented according to an interface (e.g., channel) between layers of a protocol stack supported by the respective network entities 102 communicating via such communication link.

[0103] The core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 can be an evolved packet core (EPC), or a 5G core (5GC), which can comprise control plane entities (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) to manage access and mobility, as well as user plane entities (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) to route or

[0104] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0105] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multi-frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0106] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefix. The first parameter set (e.g., =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the regular cyclic prefix. In some implementations, the first set of parameters (e.g., ) associated with the first subcarrier spacing (e.g., 15 kHz) is... =0) can utilize one time slot per subframe. The second parameter set (e.g., =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the regular cyclic prefix. The third parameter set (e.g., =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the regular cyclic prefix or extended cyclic prefix. The fourth parameter set (e.g., =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the regular cyclic prefix. The fifth parameter set (e.g., = 4) can be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0107] Time intervals for resources (e.g., communication resources) can be organized as frames, which can also be referred to as radio frames. Each frame can have a duration of, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration of, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have a same duration.

[0108] Additionally or alternatively, time intervals of resources (e.g., communication resources) can be organized as slots. For example, a subframe can include a number (e.g., quantity) of slots. The number of slots in each subframe can also depend on the parameter set or sets supported in the wireless communications system 100. For example, a first, second, third, fourth, and fifth parameter set (i.e., = 0, = 1, = 2, = 3, = 4) can utilize one slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot can include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe can depend on the parameter set. For a normal cyclic prefix, one slot can include 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), one slot can include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame can depend on the parameter set. It should be understood that a first parameter set (e.g., = 0) can be interchangeably used between subframes and slots.

[0109] In the wireless communication system 100, the electromagnetic (EM) spectrum can be partitioned into various classes, bands, frequency channels, and so on based on frequency or wavelength. By way of example, the wireless communication system 100 can support one or more operating bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications on one or more of the operating bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104, and other devices or apparatuses, for cellular communications traffic (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104, and other devices or apparatuses, for short range, high data rate capabilities.

[0110] FR1 can be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 can be associated with a first numerology (e.g., = 0) that includes 15 kHz subcarrier spacing, a second numerology (e.g., = 1) that includes 30 kHz subcarrier spacing, and a third numerology (e.g., = 2) that includes 60 kHz subcarrier spacing. FR2 can be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 can be associated with a third numerology (e.g., = 2) that includes 60 kHz subcarrier spacing and a fourth numerology (e.g., = 3) that includes 120 kHz subcarrier spacing.

[0111] For illustrative purposes and without implying any limitation, some embodiments of the present disclosure will be described with reference to the scenarios of the UE 104 performing PUSCH transmissions and retransmissions to the network entity 102. It will be appreciated that the present disclosure described herein can be implemented in various ways beyond those described below.

[0112] Figure 1B ​​​​​An example diagram of CG PUSCH TOs in a CG configuration period is illustrated. As described above, to achieve low latency requirement and large packet size, it has been decided in 3GPP to configure multiple CG PUSCH TOs in a single CG PUSCH configuration period. The gNB can configure a parameter N, and indicate a single SLIV from a configured time domain resource allocation (TDRA) table, and the UE can determine N resources in each of the N consecutive slots of each CG period, and each resource has the same SLIV in that slot.

[0113] For example, assume the period of CG is 5 slots, and N=4, and SLIV is indicated, then the determined N TOs in a CG period can be as shown. Figure 1B

[0114] For each TO, the corresponding HARQ process number can be determined using the following formula. • The HPN for the first configured TO can be determined according to the following: HARQ Process ID = [X floor ((CURRENT_symbol) / period)] modulonrofHARQ-Processes. • The HPN of the remaining configured and valid CG PUSCH in the period is determined by incrementing the HARQ process ID of the previous PUSCH. • If a CG PUSCH is dropped due to collision with the DL symbol(s) indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated or SSB, the configured CG PUSCH is invalid.

[0115] Thus, in the above example, the HPN in the first period includes 1, 2, 3, and 4, and the HPN in the second period includes 5, 6, 7, and 8.

[0116] Figure 2 An example signaling diagram illustrating an example process 200 that supports performing PUSCH retransmission in accordance with aspects of the present disclosure is shown. For discussion purposes, process 200 will be described with reference to the UE 104 and the network entity 102 as shown in FIG. 1 and process 200 can involve the UE 104 and the network entity 102 as shown in FIG. 1. Figure 1A Figure 1A

[0117] As Figure 2 ​​​As shown in FIG. 1, the UE 104 transmits 201 multiple PUSCH transmissions 202 to the base station 102 through multiple TOs in a CG-configured period, and the base station 102 receives the multiple PUSCH transmissions. The UE 104 determines 204 multiple resources for retransmission of at least some of the PUSCH transmissions. Then, the UE 104 retransmits 206 at least some of the PUSCH transmissions using the determined multiple resources, i.e., the UE 104 performs retransmission 207 of at least some of the PUSCH transmissions to the base station 102 using the determined multiple resources. In some embodiments, the number of at least some of the PUSCH transmissions to be retransmitted can be equal to or greater than 2.

[0118] At the base station side, the base station 102 can also determine 205 multiple resources for retransmission of at least some of the PUSCH transmissions, and then receive 208 retransmission of at least some of the PUSCH transmissions using the determined multiple resources.

[0119] In some embodiments, the UE 104 can retransmit at least some of the PUSCH transmissions based on a DCI received from the base station 102. The CRC code of the DCI is scrambled by a CS-RNTI of the UE 104.

[0120] How to determine the resources for retransmission of at least some of the PUSCH transmissions will be described in details below. For the purpose of illustration without implying any limitation, it is assumed that the UE 104 determines M resources for retransmission of M PUSCH transmissions out of the multiple PUSCH transmissions, where M is an integer greater than 1.

[0121] In the context of the following embodiments, the term “resource” can refer to a time-domain resource, and thus the terms “resource” and “time-domain resource” can be used interchangeably.

[0122] In some embodiments, the DCI from the base station 102 indicates N resources, and the M resources for retransmission of at least some of the PUSCH transmissions are based on the N resources, where N is an integer greater than 1. For example, the DCI can indicate the N resources through an index of a TDRA table, where the TDRA table can be determined based on the format of the DCI.

[0123] In some embodiments, N can be equal to or less than M, i.e., the number of resources for retransmission of at least some of the PUSCH transmissions can be the same as or greater than N. In this case, the UE 104 can determine all the N resources as the resources for retransmission of at least some of the PUSCH transmissions.

[0124] If M is less than N, the UE 104 can determine the first M or the last M resources of the N resources as the resources for retransmission of at least some of the PUSCH transmissions. In other words, according to the scheduling order of the M CG PUSCH transmissions, only the first M or the last M of the N resources are used for the M CG PUSCH retransmissions. The remaining N-M resources are not used for any PUSCH transmission.

[0125] Figure 3 FIG. illustrates an example diagram for resources for PUSCH retransmission determined from the resources indicated by DCI according to aspects of the present disclosure. As shown in Figure 3 As shown in the middle, there are 4 PUSCH transmissions in 4 TOs, and 3 of the PUSCH transmissions (i.e., 1, 3, and 4) should be retransmitted. The DCI can indicate 4 SLIVs, and only the first three or the last three SLIVs are used for the 3 PUSCH retransmissions.

[0126] In the case that M is less than N, the resources for retransmission of at least some of the PUSCH transmissions are determined based on the first bitmap in the DCI. For example, a bit value of 1 (or 0) can indicate that the resource is used for retransmission.

[0127] For example, the bitmap is 1011, indicating that the first, third, and fourth PUSCH transmissions will be retransmitted, then the DCI can indicate four SLIVs, and the first, third, and fourth resources are used for PUSCH retransmission.

[0128] The bitmap can be a bitmap used to indicate whether at least some of the plurality of PUSCH transmissions will be retransmitted, which will be described in detail later.

[0129] The bitmap can be related to the NDI field and / or the RV field of the DCI, which will be described in detail later.

[0130] In some embodiments, the plurality of resources for retransmission of at least some of the PUSCH transmissions are in consecutive slots and have the same SLIV. For example, the time domain resources for the M CG PUSCH transmissions are M resources in M consecutive slots, the DCI can indicate the first slot and the SLIV for the first resource, and the resources in the M slots are the same.

[0131] For example, the first slot can be indicated by the k2 value in the DCI. If multiple k2 values are indicated, the first k2 value can be used.

[0132] In some embodiments, the DCI indicates, via an index of a TDRA table, a first resource of a plurality of resources for retransmission of at least some of the PUSCH transmissions, where each row of the TDRA table includes one SLIV. The TDRA table can be a TDRA table used for DCI detected in a user equipment specific search space (USS).

[0133] Alternatively, in a case where there is more than one SLIV in the indexed row of the TDRA table, the first resource is determined via the first or last SLIV from the TDRA table. That is, if there is more than one SLIV for the indexed row, the first or last SLIV can be used.

[0134] Figure 4 FIG. illustrates an example diagram of resources for PUSCH retransmission in consecutive slots and SLIVs indicated by DCI according to aspects of the present disclosure. As shown in FIG. Figure 4 As shown in FIG. 4, there are 4 PUSCH transmissions in 4 TOs, and 3 of the PUSCH transmissions (i.e., 1, 3, and 4) should be retransmitted. The DCI can indicate 1 SLIV, and then the 3 PUSCH transmissions can be transmitted in three consecutive slots from the first SLIV.

[0135] So far, the resources for retransmission of at least some of the PUSCH transmissions are described. In the following, how to indicate whether at least some of the plurality of PUSCH transmissions will be retransmitted will be described. It should be understood that the order of operations is provided for illustrative purposes, and does not imply any limitation. In some embodiments, the UE can be first indicated whether at least some of the plurality of PUSCH transmissions will be retransmitted, and then the resources for retransmission are determined.

[0136] In some embodiments, the DCI includes a second bitmap to indicate whether at least some of the plurality of PUSCH transmissions will be retransmitted, and a bit of the second bitmap has a one-to-one mapping to at least a portion of the plurality of TOs.

[0137] In some embodiments, the number of bits in the second bitmap can be equal to the number of the plurality of TOs configured for the plurality of CG PUSCH transmissions. For example, if 4 TOs are configured in one period, then there will be 4 bits in the DCI, and if the bit is 0100, it can indicate that the PUSCH transmission transmitted in the second TO should be retransmitted.

[0138] In some embodiments, the number of bits in the second bitmap can be equal to the maximum number of PUSCH transmissions K indicated by the TDRA table, and the number of the plurality of configured TOs is denoted as L. Then, only the first X bits / last X bits in the second bitmap indicate whether the first / last valid / configured PUSCH transmission should be retransmitted, where X can be equal to min{K, L}.

[0139] Specifically, there can be several cases. K is greater than L, and then the first L or last L bits in the second bitmap can be used to indicate whether at least some of the plurality of PUSCH transmissions will be retransmitted. Alternatively, K is less than L, and then the K bits in the second bitmap can be used to indicate whether the first K or last K bits of at least some of the plurality of PUSCH transmissions will be retransmitted. Alternatively, K is equal to L, and then the K bits in the second bitmap can be used to indicate whether at least some of the plurality of PUSCH transmissions will be retransmitted.

[0140] Figure 5 FIG. 13 illustrates an example diagram of a bitmap indicating whether a PUSCH transmission will be retransmitted, according to aspects of the present disclosure. As shown in FIG. 13, there are 4 PUSCH transmissions in 4 TOs. The maximum number of PUSCH transmissions in the TDRA table is 8, there will be 8 bits in the DCI, and then only the last 4 bits are valid bits. If the bits are 00000100, it can indicate that the PUSCH transmission sent in the second TO should be retransmitted. Figure 5

[0141] In some embodiments, the DCI includes a second bitmap to indicate whether at least some of the plurality of PUSCH transmissions corresponding to the HPN will be retransmitted, and the number of bits in the second bitmap can be equal to the maximum number of HPNs configured for the CG configuration.

[0142] For example, 4 TOs are configured in one period, and the maximum number of HPNs configured for the CG configuration is configured as 16, then there will be 16 bits in the DCI. If the bits are 0000 0100 0000 0000, it can indicate that the PUSCH transmission corresponding to HPN #5 should be retransmitted.

[0143] In some embodiments, the second bitmap can be related to the NDI field and / or the RV field of the DCI. For example, the second bitmap can reuse the NDI field and / or the RV field of the DCI. In some embodiments, the second bitmap can be the same as the first bitmap.

[0144] ​It is noted that the DCI should have the same size as the same DCI format with CRC scrambled by the C-RNTI of the UE 104. One approach is to make the number of bits in the NDI field or the RV field in the DCI equal to the maximum between {K, HPN number / configured TO number}, where K is the maximum number of PUSCH transmissions indicated by the TDRA table. Another approach is to make the total DCI size equal by adding padding bits at the DCI with the smaller size.

[0145] More specifically, the DCI can be referred to as a first DCI, and the UE 104 can receive a second DCI that has the same format as the first DCI, and the second DCI includes a CRC code scrambled by the C-RNTI of the UE 104. Then, the first DCI can be aligned in size with the second DCI. One approach is to add padding bits to the NDI field or the RV field of the first DCI or the second DCI such that the number of bits in the NDI field or the RV field is equal to the maximum between X and the number of PUSCH transmissions indicated by the TDRA table of the second DCI, where X is the number of TOs in the period of the CG configuration, or X is the maximum number of HPNs for the CG configuration. Another approach is to add padding bits to the one with the smaller size among the first DCI and the second DCI.

[0146] Additionally or alternatively, the DCI can have a new format that is not the same as the legacy DCI format 0_1 / 0_2 / 0_3 / 0_0. As an example, the new DCI format can be DCI format 0_4.

[0147] In some embodiments, the DCI includes a HPN field to indicate the first HPN that is to be retransmitted. For example, the UE 104 can determine that the CG PUSCH transmission corresponding to the HPN indicated by the HPN field of the DCI is to be retransmitted. Then, the UE 104 can determine that one or more CG PUSCH transmissions corresponding to HPNs that are greater than the HPN are to be retransmitted. In other words, all PUSCH transmissions sent using HPNs that are greater than the indicated HPN are to be retransmitted.

[0148] Figure 6 FIG. illustrates an example diagram where PUSCH transmissions corresponding to certain HPNs are to be retransmitted, according to aspects of the present disclosure. As shown in Figure 6 As shown in the middle, 4 PUSCH transmissions are sent, and the corresponding HPNs are 5, 6, 7, and 8. The DCI can indicate HPN = 6, then the UE 104 will retransmit the PUSCH transmissions corresponding to HPN 6, 7, and 8.

[0149] In some embodiments, the UE 104 can determine that one or more CG PUSCH transmissions corresponding to a number of HPNs greater than the indicated first HPN are to be retransmitted. The number of HPNs can be indicated by RRC signaling. Additionally or alternatively, the number of HPNs can also be indicated by DCI. For example, there are 4 PUSCH transmissions sent and the corresponding HPNs are 5, 6, 7, and 8. The DCI can indicate HPN = 6, and the RRC configuration or DCI indicates the number of retransmissions is 2, and then the UE 104 will retransmit the PUSCH transmissions corresponding to HPNs 6 and 7.

[0150] So far, it is described that whether at least some of the multiple PUSCH transmissions are to be retransmitted is indicated. In the following, how to determine the RVs for the retransmissions of at least some of the PUSCH transmissions will be described. It should be understood that the order of operations is provided for the purpose of illustration and does not imply any limitation.

[0151] In some embodiments, the number of RV fields of the DCI indicates the RVs for the retransmissions of at least some of the PUSCH transmissions, and the retransmissions have the same RV. In other words, the number of RV fields in the DCI to indicate the RVs should be 1, and all the retransmissions have the same RV.

[0152] Alternatively, the number of RV fields of the DCI can be equal to the number of the multiple TOs, and each RV field corresponds to one of the multiple TOs.

[0153] Alternatively, the number of RV fields of the DCI can be equal to the maximum number of HPNs configured for the CG configuration, and each RV field corresponds to one of the number of HPNs.

[0154] The RV field can include 2 bits (e.g., indicating 0, 2, 3, or 1) or 1 bit (e.g., indicating 0 or 2).

[0155] In some embodiments, the RVs for the retransmissions of at least some of the PUSCH transmissions are different from the RVs for the original transmissions of the PUSCH transmissions. For example, if the initial transmission uses RV = 0, then the retransmission uses RV = 2; or if the initial transmission uses RV = 2, then the retransmission uses RV = 0.

[0156] In some embodiments, the number of RV fields of the DCI can be equal to the maximum number K of PUSCH transmissions indicated by the TDRA table. Then, the first X / last X bits indicate the RVs for the first X / last X configured / valid PUSCH transmissions, where X = min{K, L}. More specifically, if K is greater than the number L of the multiple TOs, then the first L or last L RV fields of the DCI can be used for retransmission of at least some of the PUSCH transmissions. If K is less than L, then the K RV fields of the DCI can be used for the first K or last K retransmission of at least some of the PUSCH transmissions. If K is equal to L, then the K RV fields of the DCI can be used for retransmission of at least some of the PUSCH transmissions.

[0157] It will be noted that the DCI should have the same size as the same DCI format with CRC scrambled by the C-RNTI of the UE 104. One approach is to make the number of bits of the RV field equal to the maximum between {K, HPN number / configured TO number}, where K is the maximum number of PUSCH transmissions indicated by the TDRA table. Another approach is to make the total DCI size equal by adding padding bits at the DCI with the smaller size.

[0158] More specifically, the DCI can be referred to as a first DCI, and the UE 104 can receive a second DCI that has the same format as the first DCI and that includes a CRC code scrambled by the C-RNTI of the UE 104. Then, the first DCI can be aligned in size with the second DCI. One approach is to add padding bits to the RV field of the first DCI or the second DCI such that the number of bits in the RV field is equal to the maximum between the number of the multiple TOs and the maximum number of PUSCH transmissions indicated by the TDRA table of the second DCI. Another approach is to add padding bits to the RV field of the first DCI or the second DCI such that the number of bits in the RV field is equal to the maximum between the number of the HPN and the maximum number of PUSCH transmissions indicated by the TDRA table of the second DCI. A further approach is to add padding bits to the one with the smaller size among the first DCI and the second DCI.

[0159] So far, the determination of the RVs for retransmission of at least some of the PUSCH transmissions is described. By using the above approaches, the retransmission of the multiple CG PUSCH transmissions can be scheduled by the DCI from the base station 102.

[0160] In some embodiments, the UE 104 can retransmit at least some of the PUSCH transmissions based on a timer configured by the base station 102. The timer can be started or restarted after a first or last valid TO of the plurality of TOs. Alternatively, the timer can be started or restarted after a last TO in the time domain that is not indicated as unused by the UE 104. Then, if no ACK for the HPN is received in a CG period after the expiration of the timer, the UE 104 can determine that the PUSCH transmission corresponding to the HPN is to be retransmitted.

[0161] For example, the timer can be restarted or started after a first or last configured CG TO, and after the expiration of the timer, if no ACK for the HPN is received in a CG period, the PUSCH corresponding to the HPN is to be retransmitted. The first or last configured CG TO is the first or last valid TO. Alternatively, the timer can be restarted or started after a last TO in the time domain that is not indicated as unused by the UE in the UCI. After the expiration of the timer, if no ACK for the HPN is received in a CG period, then the PUSCH corresponding to the HPN is to be retransmitted.

[0162] With the above embodiments, the retransmission of the plurality of CG PUSCH transmissions in a period of CG configuration can be scheduled (e.g., by DCI or timer) once, thereby reducing latency and signaling overhead for performing the plurality of CG PUSCH retransmissions.

[0163] Figure 7 FIG. 2 illustrates an example of a device 200 that supports performing PUSCH retransmission in accordance with aspects of the present disclosure. The device 200 can be an example of one of the UEs 104 as described herein. The device 200 can support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 200 can include components for bi-directional communications, including components for transmitting and receiving communications, such as a processor 202, memory 204, transceiver 206, and (optional) I / O controller 208. These components can be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses). The device 200 can also include a power source 210 (e.g., a rechargeable or non-rechargeable battery, a renewable energy source, and / or an electrical connection).

[0164] The processor 202, memory 204, transceiver 206, or various combinations thereof can be examples of means for performing various aspects of the disclosure as described herein. For example, the processor 202, memory 204, transceiver 206, or various combinations thereof or components thereof can support a method for performing one or more of the operations described herein.

[0165] In some implementations, processor 702, memory 704, transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support components for performing the functions described herein. In some implementations, processor 702 and memory 704 coupled to processor 702 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 704 are executed by processor 702).

[0166] For example, processor 702 may support wireless communication at device 700 according to examples disclosed herein. Processor 702 may be configured to support components for transmitting multiple PUSCH transmissions via multiple TOs in a CG-configured period; components for determining multiple resources for retransmission of at least some PUSCH transmissions in the PUSCH transmissions; and components for retransmitting at least some PUSCH transmissions in the PUSCH transmissions using the determined multiple resources.

[0167] Processor 702 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 702 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory (e.g., memory 704) to cause device 700 to perform various functions of this disclosure.

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

[0169] I / O controller 708 can manage input and output signals for device 700. I / O controller 708 can also manage peripherals not integrated into device M02. In some implementations, I / O controller 708 can represent a physical connection or port to an external peripheral. In some implementations, I / O controller 708 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 708 can be implemented as part of a processor (such as processor 702). In some implementations, a user can interact with device 700 via I / O controller 708 or via hardware components controlled by I / O controller 708.

[0170] In some implementations, device 700 may include a single antenna 710. However, in other implementations, device 700 may have more than one antenna 710 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 706 may communicate bidirectionally via one or more antennas 710, using wired or wireless links as described herein. For example, transceiver 706 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 706 may also include a modem for modulating packets to provide modulated packets to one or more antennas 710 for transmission, and for demodulating packets received from one or more antennas 710. Transceiver 706 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0171] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes (e.g., phase shift keying (PSK) or quadrature amplitude modulation (QAM)). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 710 for transmitting the amplified signal over the air or wireless medium.

[0172] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 710 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0173] Figure 8 An example of another device 800 performing PUSCH retransmission according to aspects of this disclosure is illustrated. Device 800 may be an example of base station 102 as described herein. Device 800 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 800 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 802, memory 804, transceiver 806, and (optionally) I / O controller 808. These components may communicate electronically or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0174] Processor 802, memory 804, transceiver 806, or various combinations thereof or various components thereof may be examples of components for performing various aspects of this disclosure as described herein. For example, processor 802, memory 804, transceiver 806, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0175] In some implementations, processor 802, memory 804, transceiver 806, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support components for performing the functions described herein. In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 804 are executed by processor 802).

[0176] For example, processor 802 may support wireless communication at device 800 according to examples disclosed herein. Processor 802 may be configured to support components for receiving multiple PUSCH transmissions via multiple TOs in a CG-configured period; components for determining multiple resources for retransmission of at least some PUSCH transmissions in the PUSCH transmissions; and components for receiving retransmissions of at least some PUSCH transmissions in the PUSCH transmissions using the determined multiple resources.

[0177] Processor 802 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 802 may be configured to use a memory controller to operate a memory array. In some other embodiments, the memory controller may be integrated into processor 802. Processor 802 may be configured to execute computer-readable instructions stored in memory (e.g., memory 804) to cause device 800 to perform various functions of this disclosure.

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

[0179] I / O controller 808 can manage input and output signals for device 800. I / O controller 808 can also manage peripherals not integrated into device 800. In some implementations, I / O controller 808 can represent a physical connection or port to an external peripheral. In some implementations, I / O controller 808 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 808 can be implemented as part of a processor (such as processor 802). In some implementations, a user can interact with device 800 via I / O controller 808 or via hardware components controlled by I / O controller 808.

[0180] In some implementations, device 800 may include a single antenna 810. However, in other implementations, device 800 may have more than one antenna 810 (i.e., multiple antennas), which may include multiple antenna panels or antenna arrays, and may concurrently transmit or receive multiple wireless transmissions. Transceiver 806 may communicate bidirectionally via one or more antennas 810, using wired or wireless links as described herein. For example, transceiver 806 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 806 may also include a modem for modulating packets to provide modulated packets to one or more antennas 810 for transmission, and for demodulating packets received from one or more antennas 810. Transceiver 806 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0181] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes (e.g., phase shift keying (PSK) or quadrature amplitude modulation (QAM)). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 810 for transmitting the amplified signal over the air or wireless medium.

[0182] A receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 810 for receiving signals over the air or a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0183] Figure 9An example of a processor 900 supporting PUSCH retransmission according to aspects of this disclosure is illustrated. Processor 900 may be an example of a processor configured to perform various operations as described herein. Processor 900 may include a controller 902 configured to perform various operations as described herein. Processor 900 may optionally include at least one memory 904, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 900 may optionally include one or more arithmetic logic units (ALUs) 900. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0184] Processor 900 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included within the processor chipset (e.g., processor 900)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0185] Controller 902 can be configured to manage and coordinate various operations of processor 900 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 900 to support various operations according to the examples described herein. For example, controller 902 can operate as a control unit of processor 900, generating control signals that manage the operation of various components of processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0186] Controller 902 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 904 and determine subsequent instructions(s) to be executed, such that processor 900 supports various operations as described herein. Controller 902 may be configured to track the memory addresses of instructions associated with memory 904. Controller 902 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 902 may be configured to interpret instructions and determine control signals to be output to other components of processor 900, such that processor 900 supports various operations as described herein. Additionally or alternatively, controller 902 may be configured to manage data flow within processor 900. Controller 902 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 900.

[0187] Memory 904 may include one or more caches (e.g., memory native to or included therein of processor 900) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 904 may reside within or on the processor chipset (e.g., native to processor 900). In some other implementations, memory 904 may reside external to the processor chipset (e.g., remotely to processor 900).

[0188] Memory 904 may store computer-readable, computer-executable code including instructions that, when executed by processor 900, cause processor 900 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 902 and / or processor 900 may be configured to execute the computer-readable instructions stored in memory 904 to cause processor 900 to perform various functions. For example, processor 900 and / or controller 902 may be coupled to or coupled to memory 904, and processor 900, controller 902, and memory 904 may be configured to perform the various functions described herein. In some examples, processor 900 may include multiple processors, and memory 904 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0189] One or more ALU 900s can be configured to support various operations as described herein. In some implementations, one or more ALU 900s may reside within or on a processor chipset (e.g., processor 900). In some other implementations, one or more ALU 900s may reside outside the processor chipset (e.g., processor 900). One or more ALU 900s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 900s can receive input operands and an arithmetic code that determines the operation to be performed. One or more ALU 900s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Additionally or alternatively, one or more ALU 900s may support logical operations (such as AND, OR, XOR, NOR, and NAND), enabling one or more ALU 900s to handle conditional operations, comparisons, and bitwise operations.

[0190] Processor 900 may support wireless communication according to examples disclosed herein. Processor 902 may be configured or operable to support components for transmitting multiple PUSCH transmissions through multiple TOs in a cycle configured by CG; components for determining multiple resources for retransmission of at least some PUSCH transmissions in the PUSCH transmissions; and components for retransmitting at least some PUSCH transmissions in the PUSCH transmissions using the determined multiple resources.

[0191] Figure 10 An example of another processor 1000 supporting PUSCH retransmission according to aspects of this disclosure is illustrated. Processor 1000 may be an example of a processor configured to perform various operations according to examples described herein. Processor 1000 may include a controller 1002 configured to perform various operations according to examples described herein. Processor 1000 may optionally include at least one memory 1004, such as L1 / L2 / L3 cache. Additionally or alternatively, processor 1000 may optionally include one or more arithmetic logic units (ALUs) 1000. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0192] Processor 1000 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 1000)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0193] Controller 1002 can be configured to manage and coordinate various operations of processor 1000 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1000 to support various operations according to the examples described herein. For example, controller 1002 can operate as a control unit of processor 1000, generating control signals that manage the operation of various components of processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0194] Controller 1002 may be configured to obtain (e.g., fetch, retrieve, receive) instructions from memory 1004 and determine subsequent instructions(s) to be executed, such that processor 1000 supports various operations as described herein. Controller 1002 may be configured to track the memory addresses of instructions associated with memory 1004. Controller 1002 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1002 may be configured to interpret instructions and determine control signals to be output to other components of processor 1000, such that processor 1000 supports various operations as described herein. Additionally or alternatively, controller 1002 may be configured to manage data flow within processor 1000. Controller 1002 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1000.

[0195] Memory 1004 may include one or more caches (e.g., memory native to or included therein of processor 1000) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 1004 may reside within or on the processor chipset (e.g., native to processor 1000). In some other implementations, memory 1004 may reside external to the processor chipset (e.g., remotely to processor 1000).

[0196] Memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by processor 1000, cause processor 1000 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 1002 and / or processor 1000 may be configured to execute computer-readable instructions stored in memory 1004 to cause processor 1000 to perform various functions. For example, processor 1000 and / or controller 1002 may be coupled to or coupled to memory 1004, and processor 1000, controller 1002, and memory 1004 may be configured to perform the various functions described herein. In some examples, processor 1000 may include multiple processors, and memory 1004 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0197] One or more ALU 1000s can be configured to support various operations as described herein. In some implementations, one or more ALU 1000s may reside within or on a processor chipset (e.g., processor 1000). In some other implementations, one or more ALU 1000s may reside outside the processor chipset (e.g., processor 1000). One or more ALU 1000s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1000s can receive input operands and an arithmetic code that determines the operation to be performed. One or more ALU 1000s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Additionally or alternatively, one or more ALU 1000s may support logical operations (such as AND, OR, XOR, NOR, and NAND), enabling one or more ALU 1000s to handle conditional operations, comparisons, and bitwise operations.

[0198] Processor 1000 may support wireless communication according to examples disclosed herein. Processor 1000 may be configured or operable to support components for receiving multiple PUSCH transmissions through multiple TOs in a CG-configured period; components for determining multiple resources for retransmission of at least some PUSCH transmissions in the PUSCH transmissions; and components for receiving retransmissions of at least some PUSCH transmissions in the PUSCH transmissions using the determined multiple resources.

[0199] Figure 11 A flowchart illustrating a method 1100 for supporting PUSCH retransmission according to aspects of this disclosure is shown. The operation of method 1100 can be implemented by a device or its components as described herein. For example, the operation of method 1100 can be performed by a UE 104 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0200] At block 1105, the method may include: sending multiple PUSCH transmissions to the base station via multiple TOs in a period configured by the CG. The operation of sending multiple PUSCH transmissions may be performed according to examples as described herein. In some implementations, aspects of the operation of sending multiple PUSCH transmissions may be as described in the references... Figure 1A The device described is executed.

[0201] At block 1110, the method may include: determining multiple resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission. The operation of determining the multiple resources for retransmission may be performed according to examples as described herein. In some implementations, aspects of the operation of determining the multiple resources for retransmission may be provided by reference to [reference needed]. Figure 1A The device described is executed.

[0202] At block 1115, the method may include retransmitting at least some of the PUSCH transmissions in the PUSCH transmissions to the base station using a plurality of determined resources. The operation of retransmitting at least some of the PUSCH transmissions in the PUSCH transmissions may be performed according to the examples described herein. In some implementations, aspects of the operation of retransmitting at least some of the PUSCH transmissions in the PUSCH transmissions may be as described in the references... Figure 1A The device described is executed.

[0203] In some embodiments, the method 1100 may further include: retransmitting at least some of the PUSCH transmissions in the PUSCH transmissions based on the DCI received from the base station. In some embodiments, the CRC code of the DCI may be scrambled by the User Equipment's Configuration Scheduling Radio Network Temporary Identifier (CS-RNTI).

[0204] In some embodiments, the DCI may indicate N resources by indexing the TDRA table, where N is an integer greater than 1, and the multiple resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be based on N resources. In some embodiments, the number of resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be the same as or greater than N.

[0205] In some embodiments, assuming the number of resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission is M and M is less than N, method 1100 may further include determining the first M or the last M resources out of the N resources as resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission. Additionally or alternatively, the resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission may be determined based on the first bit map in the DCI.

[0206] In some embodiments, multiple resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be in consecutive time slots and have the same SLIV. In some embodiments, the DCI may indicate the first time slot and the SLIV of the first resource among the multiple resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission.

[0207] In some embodiments, the first time slot may be indicated by one of the following in the DCI: a single K2 value in the case where only one K2 value is indicated in the DCI; or a first K2 value in the case where more than one K2 value is indicated in the DCI, wherein the K2 value is used to indicate the number of time slots between the time slot in which the DCI is received and the first time slot.

[0208] In some embodiments, the DCI may indicate a first resource among a plurality of resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission via an index of a TDRA table, wherein each row of the TDRA table includes a SLIV. Alternatively, if there is more than one SLIV in an indexed row of the TDRA table, method 1100 may further include determining the first resource via a first or last SLIV from the TDRA table.

[0209] In some embodiments, the DCI may include a second bitmap for indicating whether at least some of the PUSCH transmissions among a plurality of PUSCH transmissions will be retransmitted, and the bits of the second bitmap have a one-to-one mapping to at least a portion of the plurality of TOs. In some embodiments, the number of bits in the second bitmap may be equal to the number of the plurality of TOs. Alternatively, the number of bits in the second bitmap may be equal to the maximum number K of PUSCH transmissions indicated by the TDRA table.

[0210] In some embodiments, K is greater than the number L of multiple TOs, and the first L or last L bits of the second bitmap can be used to indicate whether at least some of the multiple PUSCH transmissions will be retransmitted. Alternatively, K is less than L, and K bits of the second bitmap can be used to indicate whether the first K or last K PUSCH transmissions of at least some of the multiple PUSCH transmissions will be retransmitted. Alternatively, K is equal to L, and K bits of the second bitmap can be used to indicate whether at least some of the multiple PUSCH transmissions will be retransmitted.

[0211] In some embodiments, the DCI may include a second bitmap indicating whether at least some of the PUSCH transmissions among a plurality of PUSCH transmissions corresponding to an HPN will be retransmitted, and the number of bits in the second bitmap may be equal to the maximum number of HPNs configured for CG configuration. In some embodiments, the second bitmap may be associated with the NDI field and / or RV field of the DCI.

[0212] In some embodiments, the DCI is a first DCI, and method 1100 may further include receiving a second DCI having the same format as the first DCI, and the second DCI includes a CRC code scrambled by the C-RNTI of the user equipment, and the first DCI may be aligned in size with the second DCI by one of the following: adding padding bits to the NDI field or RV field of the first DCI or the second DCI such that the number of bits in the NDI field or RV field is equal to the maximum value between X and the number of PUSCH transmissions indicated by the TDRA table of the second DCI, where X is the number of multiple TOs in the CG configuration period, or X is the maximum number of HPNs used for CG configuration; or adding padding bits to the smaller of the first DCI and the second DCI.

[0213] In some embodiments, method 1100 may further include determining that a CG PUSCH transmission corresponding to an HPN indicated by the HPN field of the DCI will be retransmitted; and determining that one or more CG PUSCH transmissions corresponding to HPNs greater than that HPN will be retransmitted. Additionally or alternatively, method 1100 may include determining that one or more CG PUSCH transmissions corresponding to a plurality of HPNs greater than that HPN will be retransmitted, wherein the number of HPNs is indicated by RRC signaling or the DCI.

[0214] In some embodiments, method 1100 may further include determining the RV for retransmissions of at least some PUSCH transmissions in a PUSCH transmission. In some embodiments, the RV field of the DCI may indicate the RV, and retransmissions of at least some PUSCH transmissions in a PUSCH transmission may have the same RV. Alternatively, the number of RV fields of the DCI may be equal to the number of multiple TOs, and each RV field corresponds to one of the multiple TOs. Alternatively, the number of RV fields of the DCI may be equal to the maximum number of HPNs configured for CG configuration, and each RV field corresponds to one of the number of HPNs. The RV field may include 2 bits or 1 bit.

[0215] In some embodiments, the RV for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be different from the RV for the original transmission in the PUSCH transmission.

[0216] In some embodiments, the number of RV fields in the DCI can be equal to the maximum number K of PUSCH transmissions indicated by the TDRA table. In some embodiments, K is greater than the number L of multiple TOs, and the first or last RV field of the DCI can be used for retransmissions of at least some PUSCH transmissions. Alternatively, K is less than L, and K RV fields of the DCI can be used for the first K or last K retransmissions of at least some PUSCH transmissions. Alternatively, K is equal to L, and K RV fields of the DCI can be used for retransmissions of at least some PUSCH transmissions.

[0217] In some embodiments, the DCI is a first DCI, and method 1100 may further include receiving a second DCI having the same format as the first DCI, and the second DCI including a CRC code scrambled with the UE's C-RNTI, and the first DCI being aligned in size with the second DCI by one of the following: adding padding bits to the RV field of the first DCI or the second DCI such that the number of bits in the RV field is equal to the maximum value between the number of multiple TOs and the maximum number of PUSCH transmissions indicated by the TDRA table of the second DCI; adding padding bits to the RV field of the first DCI or the second DCI such that the number of bits in the RV field is equal to the maximum value between the number of HPNs and the maximum number of PUSCH transmissions indicated by the TDRA table of the second DCI; or adding padding bits to the smaller of the first DCI and the second DCI.

[0218] In some embodiments, method 1100 may further include retransmitting at least some of the PUSCH transmissions based on a timer configured by the base station. In some embodiments, the timer may be started or restarted after the first or last valid TO among a plurality of TOs. Additionally or alternatively, the timer may be started or restarted after the last TO in the time domain that was not indicated as unused by the user equipment.

[0219] In some embodiments, method 1100 may further include: if no ACK for HPN is received within the CG period after the timer expires, determining that the PUSCH transmission corresponding to the HPN will be retransmitted.

[0220] Figure 12 A flowchart illustrating a method 1200 for supporting PUSCH retransmission according to aspects of this disclosure is shown. The operation of method 1200 can be implemented by a device or its components as described herein. For example, the operation of method 1200 can be performed by a base station 102 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may also use dedicated hardware to perform aspects of the described functions.

[0221] At block 1205, the method may include receiving multiple PUSCH transmissions from the user equipment via multiple TOs in a period configured by the CG. The operation of receiving multiple PUSCH transmissions may be performed according to examples as described herein. In some implementations, aspects of the operation of receiving multiple PUSCH transmissions may be provided by reference to [reference missing]. Figure 1A The device described is executed.

[0222] At block 1210, the method may include determining multiple resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission. The operation of determining the multiple resources for retransmission can be performed according to examples as described herein. In some implementations, aspects of the operation of determining the multiple resources for retransmission may be provided by reference to [reference needed]. Figure 1A The device described is executed.

[0223] At block 1215, the method may include receiving retransmissions of at least some PUSCH transmissions from a user equipment using a plurality of determined resources. The operation of receiving retransmissions of at least some PUSCH transmissions may be performed according to examples as described herein. In some implementations, aspects of the operation of receiving retransmissions of at least some PUSCH transmissions may be as described in reference... Figure 1A The device described is executed.

[0224] In some embodiments, method 1200 may also receive at least some PUSCH transmissions in a PUSCH transmission based on the DCI. In some embodiments, the CRC code of the DCI may be scrambled by the User Equipment's Configuration Scheduling Radio Network Temporary Identifier (CS-RNTI).

[0225] In some embodiments, DCI may indicate N resources by indexing the TDRA table, where N is an integer greater than 1, and multiple resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be based on N resources. In some embodiments, the number of resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be the same as or greater than N.

[0226] In some embodiments, assuming the number of resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission is M and M is less than N, method 1200 may further include determining the first M or the last M resources out of the N resources as resources for retransmission of at least some PUSCH transmissions in the PUSCH transmission. Additionally or alternatively, the resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission may be determined based on the first bit map in the DCI.

[0227] In some embodiments, multiple resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be in consecutive time slots and have the same SLIV. In some embodiments, DCI may indicate the first time slot and the SLIV of the first resource among the multiple resources used for retransmissions of at least some PUSCH transmissions in a PUSCH transmission.

[0228] In some embodiments, the first time slot may be indicated by one of the following in the DCI: a single K2 value in the case where only one K2 value is indicated in the DCI; or a first K2 value in the case where more than one K2 value is indicated in the DCI, wherein the K2 value is used to indicate the number of time slots between the time slot in which the DCI is received and the first time slot.

[0229] In some embodiments, the DCI may indicate a first resource among a plurality of resources for retransmission of at least some PUSCH transmissions in a PUSCH transmission via an index of a TDRA table, wherein each row of the TDRA table includes a SLIV. Alternatively, if there is more than one SLIV in an indexed row of the TDRA table, method 1200 may further include determining the first resource via a first or last SLIV from the TDRA table.

[0230] In some embodiments, the DCI may include a second bitmap for indicating whether at least some of the PUSCH transmissions among a plurality of PUSCH transmissions will be retransmitted, and the bits of the second bitmap may have a one-to-one mapping to at least a portion of the plurality of TOs. In some embodiments, the number of bits in the second bitmap may be equal to the number of the plurality of TOs. Alternatively, the number of bits in the second bitmap may be equal to the maximum number K of PUSCH transmissions indicated by the TDRA table.

[0231] In some embodiments, K is greater than the number L of multiple TOs, and the first L or last L bits of the second bitmap can be used to indicate whether at least some of the multiple PUSCH transmissions will be retransmitted. Alternatively, K is less than L, and K bits of the second bitmap can be used to indicate whether the first K or last K PUSCH transmissions of at least some of the multiple PUSCH transmissions will be retransmitted. Alternatively, K is equal to L, and K bits of the second bitmap can be used to indicate whether at least some of the multiple PUSCH transmissions will be retransmitted.

[0232] In some embodiments, the DCI may include a second bitmap indicating that at least some of the multiple PUSCH transmissions corresponding to an HPN will be retransmitted, and the number of bits in the second bitmap may be equal to the maximum number of HPNs configured for CG configuration. In some embodiments, the second bitmap may be associated with the NDI field and / or RV field of the DCI.

[0233] In some embodiments, the DCI is a first DCI, and method 1200 may further include sending a second DCI having the same format as the first DCI, and the second DCI includes a CRC code scrambled by the C-RNTI of the user equipment, and the first DCI may be aligned in size with the second DCI by one of the following: adding padding bits to the NDI field or RV field of the first DCI or the second DCI such that the number of bits in the NDI field or RV field is equal to the maximum value between X and the number of PUSCH transmissions indicated by the TDRA table of the second DCI, where X is the number of multiple TOs in the CG configuration period, or X is the maximum number of HPNs used for CG configuration; or adding padding bits to the smaller of the first DCI and the second DCI.

[0234] In some embodiments, method 1200 may further include receiving a retransmission of a CG PUSCH transmission corresponding to an HPN indicated by the HPN field of the DCI; and receiving a retransmission of one or more CG PUSCH transmissions corresponding to HPNs greater than the HPN. Additionally or alternatively, method 1200 may include receiving one or more CG PUSCH transmissions corresponding to a plurality of HPNs greater than the HPN to be retransmitted, wherein the number of HPNs is indicated by RRC signaling or the DCI.

[0235] In some embodiments, method 1200 may further include determining the RV for retransmissions of at least some PUSCH transmissions in a PUSCH transmission. In some embodiments, the RV field of the DCI may indicate the RV, and retransmissions of at least some PUSCH transmissions in a PUSCH transmission may have the same RV. Alternatively, the number of RV fields of the DCI may be equal to the number of multiple TOs, and each RV field corresponds to one of the multiple TOs. Alternatively, the number of RV fields of the DCI may be equal to the maximum number of HPNs configured for CG configuration, and each RV field corresponds to one of the number of HPNs. The RV field may include 2 bits or 1 bit.

[0236] In some embodiments, the RV for retransmissions of at least some PUSCH transmissions in a PUSCH transmission may be different from the RV for the original transmission in the PUSCH transmission.

[0237] In some embodiments, the number of RV fields in the DCI can be equal to the maximum number K of PUSCH transmissions indicated by the TDRA table. In some embodiments, K is greater than the number L of multiple TOs, and the first L or the last L RV fields of the DCI can be used for retransmissions of at least some PUSCH transmissions. Alternatively, K is less than L, and the K RV fields of the DCI can be used for the first K or the last K retransmissions of at least some PUSCH transmissions. Alternatively, K is equal to L, and the K RV fields of the DCI can be used for retransmissions of at least some PUSCH transmissions.

[0238] In some embodiments, the DCI is a first DCI, and method 1200 may further include sending a second DCI having the same format as the first DCI, and the second DCI includes a CRC code scrambled by the UE's C-RNTI, and the first DCI may be aligned in size with the second DCI by one of the following: adding padding bits to the RV field of the first DCI or the second DCI such that the number of bits in the RV field is equal to the maximum value between the number of multiple TOs and the maximum number of PUSCH transmissions indicated by the TDRA table of the second DCI; adding padding bits to the RV field of the first DCI or the second DCI such that the number of bits in the RV field is equal to the maximum value between the number of HPNs and the maximum number of PUSCH transmissions indicated by the TDRA table of the second DCI; or adding padding bits to the smaller of the first DCI and the second DCI.

[0239] In some embodiments, method 1200 may further include a timer configured for retransmission of at least some PUSCH transmissions in a PUSCH transmission; and receiving retransmissions based on the timer. In some embodiments, the timer may be started or restarted after the first or last valid TO among a plurality of TOs. Additionally or alternatively, the timer may be started or restarted after the last TO in the time domain that was not indicated as unused by the user equipment.

[0240] In some embodiments, method 1200 may further include: receiving a retransmission of the PUSCH transmission corresponding to the HPN after the timer expires, wherein no ACK for the PUSCH transmission corresponding to the HPN is sent during the CG period.

[0241] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0242] The various illustrative blocks and components described herein can be implemented or executed using a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic circuit, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors incorporating a DSP core, or any other such configuration).

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

[0244] Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose computer or a special-purpose computer. By way of example, non-transitory computer-readable media can include 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 required program code components in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose processor or a special-purpose processor.

[0245] As used herein (including in the claims), the article “a” preceding an element is not limited and is understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are used interchangeably. As used herein (including in the claims), “or” as in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) 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). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein (including in the claims), “set” can include one or more elements.

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

Claims

1. A user equipment, comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: Multiple Physical Uplink Shared Channel (PUSCH) transmissions are sent to the base station via the transceiver during multiple transmission opportunities (TOs) within the period configured by the Configuration Grant (CG); Identify multiple resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission; as well as Using the identified plurality of resources, at least some of the PUSCH transmissions in the PUSCH transmissions are retransmitted to the base station via the transceiver.

2. The user equipment according to claim 1, wherein the processor is further configured to: The at least some of the PUSCH transmissions in the PUSCH transmissions are retransmitted based on the downlink control information (DCI) received from the base station.

3. The user equipment according to claim 1, wherein the processor is further configured to: At least some of the PUSCH transmissions in the PUSCH transmission are retransmitted based on a timer configured by the base station.

4. The user equipment of claim 2, wherein the DCI indicates N resources by an index of a Time Domain Resource Allocation (TDRA) table, where N is an integer greater than 1, and the plurality of resources for retransmission of the at least some PUSCH transmissions in the PUSCH transmission are based on the N resources.

5. The user equipment according to claim 4, wherein the number of resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission is the same as or greater than N.

6. The user equipment of claim 4, wherein it is assumed that the number of resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission is M and M is less than N. The processor is further configured to determine the first M or the last M of the N resources as the resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission; or The resources used for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission are determined based on the first bit graph in the DCI.

7. The user equipment of claim 2, wherein the plurality of resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission are in consecutive time slots and have the same start and length indicator (SLIV) values.

8. The user equipment of claim 7, wherein the DCI indicates a first time slot for a first resource among the plurality of resources and the SLIV, the plurality of resources being used for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission.

9. The user equipment of claim 2, wherein the DCI includes a second bitmap for indicating whether at least some of the plurality of PUSCH transmissions will be retransmitted, and the bits of the second bitmap have a one-to-one mapping to at least a portion of the plurality of TOs.

10. The user equipment of claim 9, wherein the number of bits in the second bitmap is equal to the maximum number K of PUSCH transmissions indicated by the TDRA table.

11. The user equipment according to claim 10, wherein: K is greater than the number L of the plurality of TOs, and the first L or the last L bits in the second bitmap are used to indicate whether at least some of the PUSCH transmissions in the plurality of PUSCH transmissions will be retransmitted; K is less than L, and the K bits in the second bitmap are used to indicate whether the first K or the last K PUSCH transmissions in at least some of the plurality of PUSCH transmissions will be retransmitted; or K equals L, and the K bits in the second bitmap are used to indicate whether at least some of the PUSCH transmissions in the plurality of PUSCH transmissions will be retransmitted.

12. The user equipment of claim 2, wherein the DCI includes a second bitmap for indicating that at least some of the PUSCH transmissions corresponding to Hybrid Automatic Repeat Request (HARQ) process numbers (HPNs) will be retransmitted, and the number of bits in the second bitmap is equal to the maximum number of HPNs configured for the CG configuration.

13. The user equipment according to any one of claims 9 to 12, wherein the second bitmap is associated with the New Data Indicator (NDI) field and / or Redundancy Version (RV) field of the DCI.

14. The user equipment of claim 13, wherein the DCI is a first DCI, and the processor is further configured to receive a second DCI having the same format as the first DCI, and the second DCI includes a CRC code scrambled by the Cell Radio Network Temporary Identifier (C-RNTI) of the user equipment, and wherein the first DCI is size-aligned to the second DCI by one of the following: Add padding bits to the NDI field or the RV field of the first DCI or the second DCI such that the number of bits in the NDI field or the RV field is equal to the maximum value between X and the number of PUSCH transmissions indicated by the TDRA table of the second DCI, where X is the number of the plurality of TOs in the period of the CG configuration, or X is the maximum number of HPNs used for the CG configuration; or The padding bit is added to the smaller of the first DCI and the second DCI.

15. The user equipment of claim 2, wherein the processor is further configured to: Determine the RV for the retransmission of at least some of the PUSCH transmissions in the PUSCH transmission.

16. The user equipment of claim 15, wherein the RV for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission is different from the RV for the original transmission of the PUSCH transmission.

17. The user equipment according to claim 3, wherein: The timer is started or restarted after the first or last valid TO among the plurality of TOs; or The timer is started or restarted after the last TO in the time domain that was not indicated as unused by the user equipment.

18. A base station, comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: Multiple Physical Uplink Shared Channel (PUSCH) transmissions are received from the user equipment via the transceiver during multiple transmission opportunities (TOs) within a period configured by the Configuration Authorization (CG); Identify multiple resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission; as well as The retransmission of at least some of the PUSCH transmissions in the PUSCH transmissions is received from the user equipment via the transceiver using the identified plurality of resources.

19. A method performed by a user equipment, comprising: Multiple Physical Uplink Shared Channel (PUSCH) transmissions are sent to the base station during multiple transmission opportunities (TOs) within the period configured by the Configuration Authorization (CG); Identify multiple resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission; as well as At least some of the PUSCH transmissions in the PUSCH transmissions are retransmitted to the base station using the identified plurality of resources.

20. A method performed by a base station, comprising: Multiple Physical Uplink Shared Channel (PUSCH) transmissions are received from the user equipment during multiple transmission opportunities (TOs) within the period configured by the Configuration Authorization (CG); Identify multiple resources for retransmission of at least some of the PUSCH transmissions in the PUSCH transmission; as well as The retransmission of at least some of the PUSCH transmissions in the PUSCH transmissions is received from the user equipment using the determined plurality of resources.

Images