16.5 Narrowband physical uplink shared channel related procedures
36.2133GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Physical layer proceduresRelease 17TS
For a NB-IoT UE that supports twoHARQ-Processes-r14 or the UE is configured with higher layer parameter npusch-MultiTB-Config, there shall be a maximum of 2 uplink HARQ processes.
For a NB-IoT UE and NPUSCH transmission using preconfigured uplink resource, there shall be 1 uplink HARQ process.
A NB-IoT UE shall determine whether a subframe is a NB-IoT UL subframe as follows
– If higher layer parameter resourceReservationConfigUL is configured
– for NPUSCH format 1 transmission associated with C-RNTI or SPS C-RNTI using UE-specific NPDCCH search space including NPUSCH format 1 transmission without a corresponding NPDCCH
– if the Resource reservation field in the DCI is set to 0, then the subframe is assumed as a NB-IoT UL subframe
– else if the Resource reservation field in the DCI is set to 1, then the subframe is assumed as a NB-IoT UL subframe if it is not fully reserved according to the higher layer parameters (a subframe is considered fully reserved if and only if all SC-FDMA symbols are reserved in the subframe).
– for NPUSCH format 2 transmission
– the subframe is assumed as a NB-IoT UL subframe if it is not fully reserved according to the higher layer parameters (a subframe is considered fully reserved if and only if all SC-FDMA symbols are reserved in the subframe).
– In all other cases,
– for TDD, a NB-IoT UE shall assume a subframe as a NB-IoT UL subframe if, for a NB-IoT carrier, it is configured as NB-IoT UL subframe by higher layers
– for FDD, a NB-IoT UE shall always assume a subframe as a NB-IoT UL subframe.
16.5.1 UE procedure for transmitting format 1 narrowband physical uplink shared channel
NPUSCH format 1 transmission can be scheduled by a NPDCCH with DCI format N0, or the transmission can correspond to using preconfigured uplink resource configured by higher layers. Transmission using preconfigured uplink resource is initiated by higher layers as specified in [14] , while retransmission of transport blocks transmitted using preconfigured uplink resource are scheduled by a NPDCCH with DCI format N0.
A UE shall upon detection on a given serving cell of a NPDCCH with DCI format N0 ending in NB-IoT DL subframe n scheduling NPUSCH intended for the UE, perform, at the end of
– n+k0+Koffset DL subframe for FDD,
– k0 NB-IoT UL subframes following the end of n+8 subframe for TDD,
a corresponding NPUSCH transmission using NPUSCH format 1 in N consecutive NB-IoT UL slots ni with i = 0, 1, …, N-1 according to the NPDCCH information where
– subframe n is the last subframe in which the NPDCCH is transmitted and is determined from the starting subframe of NPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; and
– 
, where the value of 
is determined by the repetition number field in the corresponding DCI (see Clause 16.5.1.1), the value of 
is determined by the resource assignment field in the corresponding DCI (see Clause 16.5.1.1), the value of 
is the number of NB-IoT UL slots of the resource unit (defined in clause 10.1.2.3 of [3]) corresponding to the 
allocated number of subcarriers (as determined in Clause 16.5.1.1) in the corresponding DCI, and the value of 
is determined by the Number of scheduled TB for Unicast field, if present, in the corresponding DCI, 
otherwise
– n0 is the first NB-IoT UL slot starting after the end of subframe n+k0+Koffset for FDD
– n0 is the first NB-IoT UL slot starting after k0 NB-IoT UL subframes following the end of n+8 subframe for TDD
– value of k0 is determined by the scheduling delay field (
) in the corresponding DCI according to Table 16.5.1-1 for FDD and Table 16.5.1-1A for TDD
– For 
,
– if the UE is configured with higher layer parameter npusch-MultiTB-Config set to ‘interleaved’, and NPUSCH corresponding to a NPDCCH with DCI CRC scrambled by C-RNTI, and 
where 
for 
, 
otherwise.
– NB-IoT UL slots 
with 
are associated with TBr+1 , 
– otherwise,
– NB-IoT UL slots 
with 
are associated with TBr+1 , 
Table 16.5.1-1: 
for DCI format N0 for FDD.
|
|
|
|
0 |
8 |
|
1 |
16 |
|
2 |
32 |
|
3 |
64 |
Table 16.5.1-1A: 
for DCI format N0 for TDD.
|
|
|
|
0 |
0 |
|
1 |
8 |
|
2 |
16 |
|
3 |
32 |
If a NPUSCH transmission without a corresponding NPDCCH collides partially or fully with a NPDSCH transmission, the NPUSCH transmission is dropped.
If a UE is configured by higher layers to decode NPDCCHs with the CRC scrambled by the C-RNTI, the UE shall decode the NPDCCH according to the combination defined in Table 16.5.1-2 and transmit a corresponding NPUSCH. The scrambling initialization of this NPUSCH corresponding to these NPDCCHs and the NPUSCH retransmission for the same transport block is by C-RNTI.
Table 16.5.1-2: NPDCCH and NPUSCH configured by C-RNTI
|
DCI format |
Search Space |
|
DCI format N0 |
UE specific by C-RNTI |
If a UE is configured to receive random access procedures initiated by "PDCCH orders", the UE shall decode the NPDCCH according to the combination defined in Table 16.5.1-3.
Table 16.5.1-3: NPDCCH configured as "PDCCH order" to initiate random access procedure
|
DCI format |
Search Space |
|
DCI format N1 |
UE specific by C-RNTI |
If a UE is configured by higher layers to decode NPDCCHs with the CRC scrambled by the Temporary C-RNTI regardless of whether UE is configured or not configured to decode NPDCCH with the CRC scrambled by the C-RNTI during random access procedure, the UE shall decode the NPDCCH according to the combination defined in Table 16.5.1-4 and transmit the corresponding NPUSCH. The scrambling initialization of NPUSCH corresponding to these NPDCCHs is by Temporary C-RNTI.
If a Temporary C-RNTI is set by higher layers, the scrambling initialization of NPUSCH corresponding to the Narrowband Random Access Response Grant in Clause 16.3.3 and any NPUSCH retransmission(s) for the same transport block is by Temporary C-RNTI. Otherwise, the scrambling initialization of NPUSCH corresponding to the Narrowband Random Access Response Grant in Clause 16.3.3 and any NPUSCH retransmission(s) for the same transport block is by C-RNTI.
If a UE is also configured by higher layers to decode NPDCCH with CRC scrambled by the C-RNTI during random access procedure, the UE shall decode the NPDCCH according to the combination defined in Table 16.5.1-4 and transmit the corresponding NPUSCH. The scrambling initialization of NPUSCH corresponding to these NPDCCH is by C-RNTI.
Table 16.5.1-4: NPDCCH and NPUSCH configured by Temporary C-RNTI and/or C-RNTI during random access procedure
|
DCI format |
Search Space |
|
DCI format N0 |
Type-2 Common |
If a UE is configured by higher layers to decode NPDCCHs with the CRC scrambled by the SPS C-RNTI, the UE shall decode the NPDCCH according to the combination defined in Table 16.5.1-5 and transmit a corresponding NPUSCH if a transport block corresponding to the HARQ process of the NPUSCH transmission is generated as described in [8].
The scrambling initialization of this NPUSCH corresponding to these NPDCCHs and NPUSCH retransmission for the same transport block is by SPS C-RNTI. The scrambling initialization of initial transmission of this NPUSCH without a corresponding NPDCCH and the NPUSCH retransmission for the same transport block is by SPS C-RNTI.
Table 16.5.1-5: NPDCCH and NPUSCH configured by SPS C-RNTI
|
DCI format |
Search Space |
|
DCI format N0 |
UE specific by C-RNTI |
A UE may transmit NPUSCH on preconfigured uplink resources as configured by higher layers. The scrambling initialization of NPUSCH transmission using preconfigured uplink resource is by PUR-RNTI.
If a UE is configured by higher layers to decode NPDCCHs with the CRC scrambled by the PUR-RNTI, the UE shall decode the NPDCCH according to the combination defined in Table 16.5.1-6 and in case the indication in the DCI corresponds to the retransmission of a transport block transmitted using preconfigured uplink resource, transmit a corresponding NPUSCH. The scrambling initialization of this NPUSCH corresponding to these NPDCCHs and the NPUSCH retransmission for the same transport block is by PUR-RNTI.
Table 16.5.1-6: NPDCCH and NPUSCH configured by PUR-RNTI
|
DCI format |
Search Space |
|
DCI format N0 |
UE specific by PUR-RNTI |
16.5.1.1 Resource allocation
The resource allocation information in uplink DCI format N0 for NPUSCH transmission or configured by higher layers for NPUSCH transmission using preconfigured uplink resource indicates to a scheduled UE
- a set of contiguously allocated subcarriers (
) of a resource unit determined by the Subcarrier indication field, or by the higher layer parameter npusch-SubCarrierSetIndex in PUR-Config-NB - a number of resource units (
) determined by the resource assignment field according to Table 16.5.1.1-2, or by the higher layer parameter npusch-NumRUsIndex in PUR-Config-NB - a repetition number (
) determined by the repetition number field according to Table 16.5.1.1-3. For a NPUSCH transmission using preconfigured uplink resource, the UE shall use the repetition number configured by higher layers. For NPUSCH with 16QAM, .
The subcarrier spacing 
of NPUSCH transmission is determined by
– the higher layer parameter npusch-SubCarrierSetIndex, in the case of NPUSCH transmission using preconfigured uplink resources and subsequent NPUSCH transmissions until a Narrowband Random Access Response Grant is received,
– the uplink subcarrier spacing field in the Narrowband Random Access Response Grant according to Clause 16.3.3 otherwise.
For NPUSCH transmission with subcarrier spacing
, 
where 
is the subcarrier indication field and 
is reserved, or nsc is configured by higher layers parameter npusch-SubCarrierSetIndex in PUR-Config-NB for NPUSCH transmissions using preconfigured uplink resources.
For NPUSCH transmission with subcarrier spacing
, the subcarrier indication field (
) in the DCI or npusch-SubCarrierSetIndex in PUR-Config-NB for NPUSCH transmissions using preconfigured uplink resources determines the set of contiguously allocated subcarriers (
) according to Table 16.5.1.1-1.
Table 16.5.1.1-1: Allocated subcarriers for NPUSCH with 
.
|
Subcarrier indication field ( |
Set of Allocated subcarriers ( |
|
0 – 11 |
|
|
12-15 |
|
|
16-17 |
|
|
18 |
|
|
19-63 |
Reserved |
)
) 
Table 16.5.1.1-2: Number of resource units (
) for NPUSCH.
|
|
|
|
0 |
1 |
|
1 |
2 |
|
2 |
3 |
|
3 |
4 |
|
4 |
5 |
|
5 |
6 |
|
6 |
8 |
|
7 |
10 |
Table 16.5.1.1-3: Number of repetitions (
) for NPUSCH.
|
|
|
|
0 |
1 |
|
1 |
2 |
|
2 |
4 |
|
3 |
8 |
|
4 |
16 |
|
5 |
32 |
|
6 |
64 |
|
7 |
128 |
16.5.1.2 Modulation order, redundancy version and transport block size determination
To determine the modulation order, redundancy version and transport block size for the NPUSCH, the UE shall first
– read the "modulation and coding scheme" field (
) in the DCI or configured by higher layers for NPUSCH transmission using preconfigured uplink resource, and
– read the "redundancy version" field (
) in the DCI or initiate with for NPUSCH transmission using preconfigured uplink resource, and
– read the "resource assignment" field (
) in the DCI or configured by higher layers for NPUSCH transmission using preconfigured uplink resource, and
– compute the total number of allocated subcarriers (
), number of resource units (
), and repetition number (
) according to Clause 16.5.1.1.
If the UE is configured with higher layer parameter edt-Parameters and the most recent NPUSCH transmission including a transport block with EDT, the UE is not expected to receive a DCI indicating a NPUSCH retransmission as part of the contention based random access procedure with 3 ≤ IMCS ≤ 14.
If the UE is configured with higher layer parameter edt-Parameters, and for a NPUSCH retransmission of the same transport block including EDT as part of the contention based random access procedure with 
in the DCI,
– the modulation order is set to 
.
– if the UE is configured with higher layer parameter edt-SmallTBS-Enabled set to ‘true’, the repetition number for the NPUSCH retransmission is the smallest integer multiple of 
value that is equal to or larger than
where 
is the TBS corresponding to the NPUSCH transmission scheduled by the Narrowband Random Access Response Grant, and 
is given by the higher layer parameter edt-TBS.
elseif the UE is configured with higher layer parameter edt-Parameters, and if the DCI indicates a retransmission as part of the contention based random access procedure with 
and the most recent NPUSCH transmission including a transport block with EDT,
– the TBS and modulation are determined according to Table 16.3.3-1 in Clause 16.3.3, for 
and the transport block does not include EDT
elseif the UE is configured with higher layer parameter npusch-16QAM-Config, and the DCI is mapped onto the UE specific search space and 
set to ‘1111’, or for NPUSCH transmission using preconfigured uplink resource and higher layer parameter pur-UL-16QAM-Config configured, 
= 4
otherwise, the UE shall use modulation order, 
= 2 if 
. The UE shall use
and Table 16.5.1.2-1 to determine the modulation order to use for NPUSCH if 
.
Table 16.5.1.2-1: Modulation and TBS index table for NPUSCH with 
.
|
MCS Index |
Modulation Order |
TBS Index |
|
0 |
1 |
0 |
|
1 |
1 |
2 |
|
2 |
2 |
1 |
|
3 |
2 |
3 |
|
4 |
2 |
4 |
|
5 |
2 |
5 |
|
6 |
2 |
6 |
|
7 |
2 |
7 |
|
8 |
2 |
8 |
|
9 |
2 |
9 |
|
10 |
2 |
10 |
If the UE is configured with higher layer parameter npusch-MultiTB-Config and multiple TB are scheduled in the corresponding DCI, 
is used for each TB.
The NPUSCH associated with a TB is transmitted in N NB-IoT UL slots associated with the TB, ni , i=0,1,…,N-1. For the NPUSCH transmission in jth block of B consecutive NB-IoT UL slots associated with the TB ni ,
, the redundancy version 
associated with the TB is determined by, 
, where 
if 
, 
otherwise. Portion of NPUSCH codeword with 
associated with a TB as defined in clause 6.3.2 in [4] mapped to slot 
of allocated 
resource unit(s) is transmitted in NB-IoT UL slots associated with the TB ni
for 
and 
for 
The UE shall use (
,
) and Table 16.5.1.2-2 to determine the TBS to use for the NPUSCH. 
is given in Table 16.5.1.2-1 if 
, or if NPUSCH with 16QAM except for NPUSCH transmission using preconfigured uplink resource in which case is given by higher layers in PUR-Config-NB, 
otherwise. is the value of the "modulation and coding scheme for 16QAM" in the DCI.
– If NPUSCH with 16QAM , otherwise .
Table 16.5.1.2-2: Transport block size (TBS) table for NPUSCH.
|
|
|
|||||||
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|
|
0 |
16 |
32 |
56 |
88 |
120 |
152 |
208 |
256 |
|
1 |
24 |
56 |
88 |
144 |
176 |
208 |
256 |
344 |
|
2 |
32 |
72 |
144 |
176 |
208 |
256 |
328 |
424 |
|
3 |
40 |
104 |
176 |
208 |
256 |
328 |
440 |
568 |
|
4 |
56 |
120 |
208 |
256 |
328 |
408 |
552 |
680 |
|
5 |
72 |
144 |
224 |
328 |
424 |
504 |
680 |
872 |
|
6 |
88 |
176 |
256 |
392 |
504 |
600 |
808 |
1000 |
|
7 |
104 |
224 |
328 |
472 |
584 |
712 |
1000 |
1224 |
|
8 |
120 |
256 |
392 |
536 |
680 |
808 |
1096 |
1384 |
|
9 |
136 |
296 |
456 |
616 |
776 |
936 |
1256 |
1544 |
|
10 |
144 |
328 |
504 |
680 |
872 |
1000 |
1384 |
1736 |
|
11 |
176 |
376 |
584 |
776 |
1000 |
1192 |
1608 |
2024 |
|
12 |
208 |
440 |
680 |
1000 |
1128 |
1352 |
1800 |
2280 |
|
13 |
224 |
488 |
744 |
1032 |
1256 |
1544 |
2024 |
2536 |
|
14 |
256 |
552 |
840 |
1128 |
1416 |
1736 |
2280 |
|
|
15 |
280 |
600 |
904 |
1224 |
1544 |
1800 |
2472 |
|
|
16 |
328 |
632 |
968 |
1288 |
1608 |
1928 |
2536 |
|
|
17 |
336 |
696 |
1064 |
1416 |
1800 |
2152 |
||
|
18 |
376 |
776 |
1160 |
1544 |
1992 |
2344 |
||
|
19 |
408 |
840 |
1288 |
1736 |
2152 |
2536 |
||
|
20 |
440 |
904 |
1384 |
1864 |
2344 |
|||
|
21 |
488 |
1000 |
1480 |
1992 |
2536 |
|||
For a NPDCCH UE-specific search space, if the UE is configured with higher layer parameter twoHARQ-ProcessesConfig, or the UE is configured with higher layer parameter npusch-MultiTB-Config and single TB is scheduled in the corresponding DCI
– the NDI and HARQ process ID as signalled on NPDCCH, and the RV and TBS, as determined above, shall be delivered to higher layers,
otherwise
– the NDI as signalled on NPDCCH, and the RV and TBS, as determined above, shall be delivered to higher layers. If the UE is configured with higher layer parameter npusch-MultiTB-Config and multiple TB are scheduled in the corresponding DCI, HARQ process ID of 0 shall be assumed for the first TB and HARQ process ID of 1 shall be assumed for the second TB.
16.5.2 UE procedure for NPUSCH retransmission
For a NPUSCH retransmission, the UE shall follow the HARQ information in DCI as specified in [8].
16.5.3 UE procedure for transmitting SR
If the UE is configured with higher layer parameter sr-WithoutHARQ-ACK-Config, the UE is configured with Narrowband Random access channel parameters (NPRACH configuration) for SR transmission by higher layers.
The UE shall, if requested by higher layers for transmitting SR, start transmission of a narrowband random access preamble on the NB-IoT carrier configured in sr-NPRACH-Resource at the next available NPRACH resource, unless the transmission would overlap with any subframe(s) of NPDSCH reception. The narrowband preamble is transmitted on the allocated subcarrier and a number of NPRACH repetitions for the associated NPRACH repetition level as indicated by higher layers. The narrowband random access preamble is transmitted with transmission power as determined in clause 16.2.1.2, commencing on the indicated NPRACH resource.