Method for performing uplink transmission in a wireless communication system and apparatus therefor
A method of performing, by a user equipment (UE), uplink transmission in a wireless communication system. The method includes: receiving, from a base station (BS), a plurality of RRC configuration information related to downlink control information (DCI); receiving, from the BS, first DCI for the uplink transmission, wherein the first DCI includes a field related to a usage of the first DCI; applying parameters of a specific RRC configuration information, among the plurality of RRC configuration information, to the first DCI based on the usage of the first DCI indicated by the field of the first DCI, wherein based on a size of the field of the first DCI being smaller than a field size of second DCI for PUSCH transmission, the field of the first DCI is zero bit padded and decoded; and performing the uplink transmission to the BS based on the first DCI.
1. A method of performing, by a user equipment (UE), uplink transmission in a wireless communication system, the method comprising:
receiving, from a base station (BS), first radio resource control (RRC) configuration information for a configured grant-based physical uplink shared channel (PUSCH);
receiving, from the BS, second RRC configuration information for a dynamic grant-based PUSCH;
receiving, from the BS, a first downlink control information (DCI) that is scrambled by a configured scheduling (CS)-radio network temporary identifier (RNTI);
validating the first DCI as a valid activation or a valid release of the configured grant-based PUSCH;
applying parameters of the first RRC configuration information to the first DCI, according to a DCI format of the first DCI, for a configured grant-based PUSCH transmission;
performing the configured grant-based PUSCH transmission to the BS;
receiving, from the BS, a second DCI that is scrambled by the CS-RNTI; and
based on a new data indicator (NDI) field of the second DCI indicating a PUSCH re-transmission: (i) applying parameters of the second RRC configuration information to the second DCI, according to the same DCI format as the first DCI, for the PUSCH re-transmission, and (ii) performing the PUSCH re-transmission to the BS,
wherein at least one field of the first DCI that is scrambled by the CS-RNTI comprises zero-padding to have a same size as each corresponding at least one field of a third DCI that is scrambled by a cell-RNTI (C-RNTI), wherein the third DCI has the same DCI format as the first DCI.
2. The method of claim 1 ,
wherein each of the first DCI and the second DCI that is scrambled by the CS-RNTI comprises a cyclic redundancy check (CRC) that is scrambled by the CS-RNTI, and
wherein the third DCI that is scrambled by the C-RNTI comprises a CRC that is scrambled by the C-RNTI.
3. The method of claim 1 ,
wherein validating the first DCI is performed based on one or more of a ‘new data indicator (NDI)’ field, a ‘redundancy version (RV)’ field, or an ‘HARQ process number’ field of the first DCI.
4. The method of claim 1 ,
wherein the zero-padding in the at least one field of the first DCI comprises at least one 0 that is inserted into each of the at least one field of the first DCI so that the field of the first DCI has a same size as a corresponding field of the third DCI.
5. The method of claim 1 ,
wherein the zero-padding in the at least one field of the first DCI comprises at least one 0 that is inserted into a most significant bit (MSB) position within each of the at least one field of the first DCI.
6. The method of claim 1 ,
wherein validating the first DCI is performed based on one or more specific fields of the first DCI that identify a usage of the first DCI, wherein the one or more specific fields of the first DCI are positioned after a common field of the first DCI that is configured regardless of the usage of the first DCI.
7. A user equipment (UE) configured to perform uplink transmission in a wireless communication system, the UE comprising:
a transceiver;
at least one processor; and
at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed by the at least one processor, perform operations comprising:
receiving, from a base station (BS) through the transceiver, first radio resource control (RRC) configuration information for a configured grant-based physical uplink shared channel (PUSCH);
receiving, from the BS through the transceiver, second RRC configuration information for a dynamic grant-based PUSCH;
receiving, from the BS through the transceiver, a first DCI that is scrambled by a configured scheduling (CS)-radio network temporary identifier (RNTI);
validating the first DCI as a valid activation or a valid release of the configured grant-based PUSCH;
applying parameters of the first RRC configuration information to the first DCI, according to a DCI format of the first DCI, for a configured grant-based PUSCH transmission;
performing the configured grant-based PUSCH transmission to the BS through the transceiver;
receiving, from the BS through the transceiver, a second DCI that is scrambled by the CS-RNTI; and
based on a new data indicator (NDI) field of the second DCI indicating a PUSCH re-transmission: (i) applying parameters of the second RRC configuration information to the second DCI, according to the same DCI format as the first DCI, for the PUSCH re-transmission, and (ii) performing the PUSCH re-transmission to the BS through the transceiver,
wherein at least one field of the first DCI that is scrambled by the CS-RNTI comprises zero-padding to have a same size as each corresponding at least one field of a third DCI that is scrambled by a cell-RNTI (C-RNTI), wherein the third DCI has the same DCI format as the first DCI.
8. The terminal UE of claim 7 ,
wherein each of the first DCI and the second DCI that is scrambled by the CS-RNTI comprises a cyclic redundancy check (CRC) that is scrambled by the CS-RNTI, and
wherein the second DCI that is scrambled by the C-RNTI comprises a CRC that is scrambled by the C-RNTI.
9. The UE of claim 7 ,
wherein validating the first DCI is performed based on one or more specific fields of the first DCI that identify a usage of the first DCI, wherein the one or more specific fields of the first DCI comprises at least one of a ‘new data indicator (NDI)’ field, a ‘redundancy version (RV)’ field, or an ‘HARQ process number’ field.
10. The UE terminal of claim 7 ,
wherein the zero-padding in the at least one field of the first DCI comprises at least one 0 that is inserted into each of the at least one field of the first DCI so that the field of the first DCI has a same size as a corresponding field of the third DCI.
11. The UE of claim 7 ,
wherein the zero-padding in the at least one field of the first DCI comprises at least one 0 that is inserted into a most significant bit (MSB) position within each of the at least one field of the first DCI.
12. The UE terminal of claim 7 ,
wherein validating the first DCI is performed based on one or more specific fields of the first DCI that identify a usage of the first DCI, wherein the one or more specific fields of the first DCI are positioned after a common field of the first DCI that is configured regardless of the usage of the first DCI.
13. The method of claim 1 , wherein validating the first DCI is performed based on a new data indicator (NDI) in the first DCI having a value of 0.
14. The method of claim 1 , wherein the DCI format of the first DCI, the second DCI, and the third DCI is a “DCI format 0_1”.
15. The UE of claim 7 , wherein validating the first DCI is performed based on a new data indicator (NDI) in the first DCI having a value of 0.
16. The UE of claim 7 , wherein the DCI format of the first DCI, the second DCI, and the third DCI is a “DCI format 0_1”.