User equipment and system performing transmission and reception operations

1. A user equipment (UE), comprising:

a receiver, which in operation, receives a physical uplink shared channel (PUSCH) config information element (IE) in form of radio resource control (RRC) signaling, the PUSCH config IE being applicable to a particular bandwidth part;

a processor, which in operation, configures a RRC configured table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the RRC configured table comprising rows, each with a value indicating a PUSCH mapping type, a slot offset value (K2) indicating a slot offset, and a start and length indicator value (SLIV) indicating a start and length indicator, and a value indicating a number of PUSCH repetitions, wherein the number of PUSCH repetitions is one of a defined plurality of numbers of PUSCH repetitions; wherein

the receiver, in operation, receives downlink control information (DCI) signaling carrying a time-domain resource assignment field with value m, wherein the value m provides a row index m+1 to the RRC configured table, and

the processor, in operation, determines allocated resources for an initial PUSCH transmission and allocated resources for at least one of the number of PUSCH repetitions based on:

a number of a slot carrying the received DCI, and

the value K2 indicating the slot offset, the value SLIV indicating the start and length indicator, and the value indicating the number of PUSCH repetitions included in the indexed row of the RRC configured table; and

a transmitter, which in operation, transmits a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one of the number of PUSCH repetitions.

2. The user equipment (UE) according to claim 1 , wherein the determination of allocated resources is based on at least one additional value included in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission, and the at least one additional value is one of:

a second slot offset value (K2′) indicating a second slot offset for the at least one repetition, or

a second start and length indicator value (SLIV′) indicating a second start and length indicator value for the at least one repetition,

wherein the second start and length indicator value SLIV′ comprises:

a start value (S′) indicating a symbol number specifying the start of the allocated resources for the at least one repetition, and

a length value (L′) indicating a number of symbols specifying the length of the allocated resources for the at least one repetition.

3. The user equipment (UE) according to claim 2 , wherein, in case the at least one additional value is the value K2′ indicating the second slot offset,

the second slot offset specifies the allocated resources for all of the at least one repetition relative to:

the number of the slot carrying the received DCI, or

the value of time domain offset field additionally carried in the received configured grant config IE.

4. The user equipment (UE) according to claim 2 , wherein, in case the at least one additional value is the value K2′ indicating the second slot offset,

the second slot offset specifies the allocated resources for all of the at least one repetition relative to a number of a slot with the allocated resources for the initial PUSCH transmission.

5. The user equipment (UE) according to claim 2 , wherein, in case the at least one additional value is the value K2′ indicating the second slot offset,

the second slot offset specifies the allocated resources for a first of the at least one repetition relative to a number of a slot with the allocated resources for the initial PUSCH transmission, or

the second slot offset specifies the allocated resources for a subsequent one of the at least one repetition relative to a number of a slot with the allocated resources for a preceding one of the at least one repetition.

6. The user equipment (UE) according to claim 2 , wherein the at least one additional value is one of:

a gap value (G′) indicating a number of symbols of a gap before the allocated resources for the at least one repetition, or

the length value (L′) indicating a number of symbols specifying the length of the allocated resources for the at least one repetition.

7. The user equipment (UE) according to claim 6 , wherein, in case the at least one additional value is the value G′ indicating the number of symbols of the gap,

the number of symbols of the gap specifies the allocated resources for all of the at least one repetition relative to a number of a last symbol of the allocated resources for the initial PUSCH transmission.

8. The user equipment (UE) according to claim 6 , wherein, in case the at least one additional value is the value G′ indicating the number of symbols of the gap,

the number of symbols of the gap specifies the allocated resources for a first of the at least one repetition relative to a number of a last symbol of the allocated resources for the initial PUSCH transmission, or

the number of symbols of the gap specifies the allocated resources for a subsequent one of the at least one repetition relative to a number of a last symbol of the allocated resources for a preceding one of the at least one repetition.

9. The user equipment (UE) according to claim 2 , wherein, in case the at least one additional value is the value L′ indicating the number of symbols specifying the length of the allocated resources,

the number of symbols specifies the length of the allocated resources for all of the at least one repetition, or

the number of symbols specifies the length of the allocated resources for an individual one of the at least one repetition.

10. The user equipment (UE) according to claim 1 , wherein the PUSCH time domain resource allocation list IE additionally comprises at least one of:

a parameter indicating whether a transport block size is calculated for each PUSCH transmission separately, or whether a combined transport block size is calculated for all PUSCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof,

a parameter indicating whether frequency hopping is applied for each PUSCH transmission separately, or whether continuous frequency hopping is applied for all PUSCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof, and

a parameter indicating whether or not demodulation reference symbols (DMRS) are present in all or each individual one of the at least one repetition of the initial PUSCH transmission.

11. A method for a user equipment (UE), comprising:

receiving a physical uplink shared channel (PUSCH) config information element (IE) in form of radio resource control (RRC) signaling, the PUSCH config IE being applicable to a particular bandwidth part;

configuring a RRC configured table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the RRC configured table comprising rows, each with a value indicating a PUSCH mapping type, a slot offset value (K2) indicating a slot offset, and a start and length indicator value (SLIV) indicating a start and length indicator, and a value indicating a number of PUSCH repetitions, wherein the number of PUSCH repetitions is one of a defined plurality of numbers of PUSCH repetitions;

receiving downlink control information (DCI) signaling carrying a time-domain resource assignment field with value m, wherein the value m provides a row index m+1 to the RRC configured table;

determining allocated resources for an initial PUSCH transmission and allocated resources for at least one of the number of PUSCH repetitions based on:

a number of a slot carrying the received DCI, and

the value K2 indicating the slot offset, the value SLIV indicating the start and length indicator, and the value indicating the number of PUSCH repetitions included in the indexed row of the RRC configured table; and

transmitting a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one of the number of PUSCH repetitions.

12. A base station (B S), comprising:

a transmitter, which in operation, transmits a physical uplink shared channel (PUSCH) config information element (IE) in form of radio resource control (RRC) signaling, the PUSCH config IE being applicable to a particular bandwidth part;

a processor, which in operation, configures a RRC configured table which is defined by a PUSCH time domain resource allocation list IE carried in the PUSCH config IE, the RRC configured table comprising rows, each with a value indicating a PUSCH mapping type, a slot offset value (K2) indicating a slot offset, and a start and length indicator value (SLIV) indicating a start and length indicator, and a value indicating a number of PUSCH repetitions, wherein the number of PUSCH repetitions is one of a defined plurality of numbers of PUSCH repetitions; wherein

the transmitter, in operation, transmits downlink control information (DCI) signaling carrying a time-domain resource assignment field with value m, wherein the value m provides a row index m+1 to the RRC configured table, and

the processor, in operation, allocates resources for an initial PUSCH transmission and allocates resources for at least one of the number of PUSCH repetitions based on:

a number of a slot carrying the transmitted DCI, and

the value K2 indicating the slot offset, the value SLIV indicating the start and length indicator, and the value indicating the number of PUSCH repetitions included in the indexed row of the RRC configured table; and

a receiver, which in operation, receives a PUSCH transmission using the respectively allocated resources for the initial PUSCH transmission and for the at least one of the number of PUSCH repetitions.