16.4 Narrowband physical downlink shared channel related procedures
36.2133GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Physical layer proceduresRelease 17TS
A NB-IoT UE shall determine whether a downlink subframe or a TDD special subframe configured for NB-IoT DL transmission is a NB-IoT DL subframe as follows
– If the UE determines that the subframe contains NPSS/NSSS/NPBCH/ SystemInformationBlockType1-NB transmission, then the subframe is not assumed as a NB-IoT subframe.
– Else if higher layer parameter resourceReservationConfigDL is configured
– for NPDSCH transmission associated with C-RNTI using UE-specific NPDCCH search space
– if the Resource reservation field in the DCI is set to 0, then the subframe is assumed as a NB-IoT DL subframe
– else if the Resource reservation field in the DCI is set to 1, then the subframe is assumed as a NB-IoT DL subframe if it is not fully reserved according to the higher layer parameters (a subframe is considered fully reserved if and only if all OFDM symbols are reserved in the subframe).
– for NPDCCH transmission associated with C-RNTI or SPS C-RNTI using UE-specific NPDCCH search space
– the subframe is assumed as a NB-IoT DL subframe if it is not fully reserved according to the higher layer parameters (a subframe is considered fully reserved if and only if all OFDM symbols are reserved in the subframe).
– In all other cases, a NB-IoT UE shall assume a subframe as a NB-IoT DL subframe if
– for a NB-IoT carrier that a UE receives higher layer parameter operationModeInfo, the subframe is configured as NB-IoT DL subframe or the subframe is a TDD special subframe configured for NB-IoT DL transmission after the UE has obtained SystemInformationBlockType1-NB.
– the subframe is configured as NB-IoT DL subframe by the higher layer parameter downlinkBitmapNonAnchor.
– except when the UE is configured with higher layer parameter additionalTxSIB1-Config set to TRUE, subframe #3 not containing additional SystemInformationBlockType1-NB transmission is assumed as a NB-IoT DL subframe if the UE monitors a NPDCCH UE-specific search space or decodes NPDSCH transmission scheduled by NPDCCH in the UE-specific search space.
For a NB-IoT UE that supports twoHARQ-Processes-r14 or the UE is configured with higher layer parameter npdsch-MultiTB-Config, there shall be a maximum of 2 downlink HARQ processes.
16.4.1 UE procedure for receiving the narrowband physical downlink shared channel
A UE shall upon detection on a given serving cell of a NPDCCH with DCI format N1, N2 ending in subframe n intended for the UE, decode, starting in
– n+5 DL subframe for FDD,
– n+5 subframe for TDD,
the corresponding NPDSCH transmission in N consecutive NB-IoT DL subframe(s) 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;
– subframe(s) ni with i=0,1,…,N-1 are N consecutive NB-IoT DL subframe(s) excluding subframes used for SI messages or scheduling gap (if any) or processing gap (if any) where, n0<n1<…,nN-1 ,
– 
, where the value of 
is determined by the repetition number field in the corresponding DCI (see Clause 16.4.1.3), the value of 
is determined by the resource assignment field in the corresponding DCI (see Clause 16.4.1.3), and the value of 
is determined by the Number of scheduled TB for Unicast field or Number of scheduled TB for SC-MTCH field, if present, in the corresponding DCI, 
otherwise,
– k0 is the number of NB-IoT DL subframe(s) starting in DL subframe n+5 for FDD or subframe n+5 for TDD, until DL subframe n0, where k0 is determined by the scheduling delay field (
) for DCI format N1, and k0 = 0 for DCI format N2. For DCI CRC scrambled by G-RNTI, k0 is determined by the scheduling delay field (
) according to Table 16.4.1-1a, otherwise k0 is determined by the scheduling delay field () according to Table 16.4.1-1. The value of 
is according to Clause 16.6 for the corresponding DCI format N1,
– for 
,
– if the UE is configured with higher layer parameter multiTB-Config in npdsch-MultiTB-Config set to ‘interleaved‘, and NPDSCH corresponding to a NPDCCH with DCI CRC scrambled by C-RNTI, and 
– NB-IoT DL subframes 
with 
are associated with TBr+1 , 
– otherwise,
– NB-IoT DL subframes 
with 
are associated with TBr+1 , 
– for 
and NPDSCH corresponding to an NPDCCH with DCI CRC scrambled by G-RNTI,
– if multiTB-Gap is not configured and 
, a processing gap of 20ms is inserted after every 2 TBs
– otherwise, a scheduling gap with a length equal to the indicated value of multiTB-Gap is inserted between TBr and TBr+1, 
.
– If the scheduling gap or the processing gap overlaps with the NPDSCH transmission gap defined in [3], the overlapped part of the scheduling gap or processing gap is also counted as the part of NPDSCH transmission gap.
Table 16.4.1-1: 
for DCI format N1.
|
|
|
|
|
|
|
|
|
0 |
0 |
0 |
|
1 |
4 |
16 |
|
2 |
8 |
32 |
|
3 |
12 |
64 |
|
4 |
16 |
128 |
|
5 |
32 |
256 |
|
6 |
64 |
512 |
|
7 |
128 |
1024 |
Table 16.4.1-1a: 
for DCI format N1 with DCI CRC scrambled by G-RNTI.
|
|
|
|
0 |
0 |
|
1 |
4 |
|
2 |
8 |
|
3 |
12 |
|
4 |
16 |
|
5 |
32 |
|
6 |
64 |
|
7 |
128 |
If a UE is configured with higher layer parameter twoHARQ-ProcessesConfig
– for FDD, the UE is not expected to receive transmissions in the Type B half duplex guard periods as specified in [3]
otherwise
– for FDD, the UE is not expected to receive transmissions in 3 DL subframes following the end of a NPUSCH transmission by the UE.
– for TDD, the UE is not expected to receive transmissions in 3 subframes following the end of a NPUSCH transmission by the UE.
If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the P-RNTI, the UE shall decode the NPDCCH and the corresponding NPDSCH according to any of the combinations defined in Table 16.4.1-2.
The scrambling initialization of NPDSCH corresponding to these NPDCCHs is by P-RNTI.
Table 16.4.1-2: NPDCCH and NPDSCH configured by P-RNTI
|
DCI format |
Search Space |
Transmission scheme of NPDSCH corresponding to NPDCCH |
|
DCI format N2 |
Type-1 Common |
If the number of NPBCH antenna ports is one, Single-antenna port, port 2000 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the RA-RNTI, the UE shall decode the NPDCCH and the corresponding NPDSCH according to any of the combinations defined in Table 16.4.1-3. The scrambling initialization of NPDSCH corresponding to these NPDCCHs is by RA-RNTI.
Table 16.4.1-3: NPDCCH and NPDSCH configured by RA-RNTI
|
DCI format |
Search Space |
Transmission scheme of NPDSCH corresponding to NPDCCH |
|
DCI format N1 |
Type-2 Common |
If the number of NPBCH antenna ports is one, Single-antenna port, port 2000 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the C-RNTI except during random access procedure, the UE shall decode the NPDCCH and the corresponding NPDSCH according to any of the combinations defined in Table 16.4.1-4. The scrambling initialization of NPDSCH corresponding to these NPDCCHs is by C-RNTI.
Table 16.4.1-4: NPDCCH and NPDSCH configured by C-RNTI
|
DCI format |
Search Space |
Transmission scheme of NPDSCH corresponding to NPDCCH |
|
DCI format N1 |
UE specific by C-RNTI |
If the number of NPBCH antenna ports is one, Single-antenna port, port 2000 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the Temporary C-RNTI and is not configured to decode NPDCCH with CRC scrambled by the C-RNTI during random access procedure, the UE shall decode the NPDCCH and the corresponding NPDSCH according to the combination defined in Table 16.4.1-5. The scrambling initialization of NPDSCH corresponding to these NPDCCHs is by Temporary 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 and the corresponding NPDSCH according to the combination defined in Table 16.4.1-5. The scrambling initialization of NPDSCH corresponding to these NPDCCHs is by C-RNTI.
Table 16.4.1-5: NPDCCH and NPDSCH configured by Temporary C-RNTI and/or C-RNTI during random access procedure
|
DCI format |
Search Space |
Transmission scheme of NPDSCH corresponding to NPDCCH |
|
DCI format N1 |
Type-2 Common |
If the number of NPBCH antenna ports is one, Single-antenna port, port 2000 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
For NPDSCH carrying SystemInformationBlockType1-NB and SI-messages, the UE shall decode NPDSCH according to the transmission scheme defined in Table 16.4.1-6. The scrambling initialization of NPDSCH is by SI-RNTI.
Table 16.4.1-6: NPDSCH configured by SI-RNTI
|
Transmission scheme of NPDSCH |
|
If the number of NPBCH antenna ports is one, Single-antenna port, port 0 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the SC-RNTI, the UE shall decode the NPDCCH and the corresponding NPDSCH according to any of the combinations defined in Table 16.4.1-7. The scrambling initialization of NPDSCH corresponding to these NPDCCHs is by SC-RNTI.
Table 16.4.1-7: NPDCCH and NPDSCH configured by SC-RNTI
|
DCI format |
Search Space |
Transmission scheme of NPDSCH corresponding to NPDCCH |
|
DCI format N2 |
Type-1A Common |
If the number of NPBCH antenna ports is one, Single-antenna port, port 2000 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the G-RNTI, the UE shall decode the NPDCCH and the corresponding NPDSCH according to any of the combinations defined in Table 16.4.1-8. The scrambling initialization of NPDSCH corresponding to these NPDCCHs is by G-RNTI.
Table 16.4.1-8: NPDCCH and NPDSCH configured by G-RNTI
|
DCI format |
Search Space |
Transmission scheme of NPDSCH corresponding to NPDCCH |
|
DCI format N1 |
Type-2A Common |
If the number of NPBCH antenna ports is one, Single-antenna port, port 2000 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the PUR-RNTI, the UE shall decode the NPDCCH and the corresponding NPDSCH according to any of the combination defined in Table 16.4.1-9. The scrambling initialization of the NPDSCH corresponding to these NPDCCHs is by PUR-RNTI.
Table 16.4.1-9: NPDCCH and NPDSCH configured by PUR-RNTI
|
DCI format |
Search Space |
Transmission scheme of NPDSCH corresponding to NPDCCH |
|
DCI format N1 |
UE specific by PUR-RNTI |
If the number of NPBCH antenna ports is one, Single-antenna port, port 2000 is used (see Clause 16.4.1.1), otherwise Transmit diversity (see Clause 16.4.1.2). |
A UE is not required to receive NPDSCH assigned by NPDCCH with DCI CRC scrambled by G-RNTI in subframes in which the UE monitors a Type1A-NPDCCH common search space or in subframes in which the UE receives NPDSCH assigned by NPDCCH with DCI CRC scrambled by SC-RNTI
A UE is not required to receive NPDSCH assigned by NPDCCH with DCI CRC scrambled by SC-RNTI or G-RNTI in subframes in which the UE monitors a Type1-NPDCCH common search space or in subframes in which the UE receives NPDSCH assigned by NPDCCH with DCI CRC scrambled by P-RNTI
A UE is not required to receive NPDSCH assigned by NPDCCH with DCI CRC scrambled by SC-RNTI or G-RNTI in subframes in which the UE monitors a Type2-NPDCCH common search space or in subframes in which the UE receives NPDSCH assigned by NPDCCH with DCI CRC scrambled by C-RNTI or Temporary C-RNTI.
The transmission schemes for NPDSCH are defined in the following Clauses.
16.4.1.1 Single-antenna port scheme
For the single-antenna port transmission schemes (port 2000) of the NPDSCH, the UE may assume that an eNB transmission on the NPDSCH would be performed according to Clause 6.3.4.1 of [3].
16.4.1.2 Transmit diversity scheme
For the transmit diversity transmission scheme of the NPDSCH, the UE may assume that an eNB transmission on the NPDSCH would be performed according to Clause 6.3.4.3 of [3]
16.4.1.3 Resource allocation
The resource allocation information in DCI format N1, N2 (paging) for NPDSCH indicates to a scheduled UE
– a number of subframes (
) determined by the resource assignment field (
) in the corresponding DCI according to Table 16.4.1.3-1.
– a repetition number (
) determined by the repetition number field (
) in the corresponding DCI according to Table 16.4.1.3-2. For NPDSCH with 16QAM, .
Table 16.4.1.3-1: Number of subframes (
) for NPDSCH.
|
|
|
|
0 |
1 |
|
1 |
2 |
|
2 |
3 |
|
3 |
4 |
|
4 |
5 |
|
5 |
6 |
|
6 |
8 |
|
7 |
10 |
Table 16.4.1.3-2: Number of repetitions (
) for NPDSCH.
|
|
|
|
0 |
1 |
|
1 |
2 |
|
2 |
4 |
|
3 |
8 |
|
4 |
16 |
|
5 |
32 |
|
6 |
64 |
|
7 |
128 |
|
8 |
192 |
|
9 |
256 |
|
10 |
384 |
|
11 |
512 |
|
12 |
768 |
|
13 |
1024 |
|
14 |
1536 |
|
15 |
2048 |
For FDD, the number of repetitions for the NPDSCH carrying SystemInformationBlockType1-NB is determined based on the parameter schedulingInfoSIB1 configured by higher-layers and according to Table 16.4.1.3-3.
Table 16.4.1.3-3: Number of repetitions for NPDSCH carrying SystemInformationBlockType1-NB, FDD.
|
Value of schedulingInfoSIB1 |
Number of NPDSCH repetitions |
|
0 |
4 |
|
1 |
8 |
|
2 |
16 |
|
3 |
4 |
|
4 |
8 |
|
5 |
16 |
|
6 |
4 |
|
7 |
8 |
|
8 |
16 |
|
9 |
4 |
|
10 |
8 |
|
11 |
16 |
|
12-15 |
Reserved |
For FDD, the starting radio frame for the first transmission of the NPDSCH carrying SystemInformationBlockType1-NB is determined according to Table 16.4.1.3-4.
Table 16.4.1.3-4: Starting radio frame for the first transmission of the NPDSCH carrying SystemInformationBlockType1-NB, FDD.
|
Number of NPDSCH repetitions |
|
Starting radio frame number for SystemInformationBlockType1-NB repetitions (nf mod 256) |
|
4 |
|
0 |
|
|
16 |
|
|
|
32 |
|
|
|
48 |
|
|
8 |
|
0 |
|
|
16 |
|
|
16 |
|
0 |
|
|
1 |
mod 4 = 0
mod 4 = 1
mod 4 = 2
mod 4 = 3
mod 2 = 0
mod 2 = 1
mod 2 = 0For the TDD NB-IoT carrier on which NPSS/NSSS/NPBCH are detected, the number of repetitions and subframe index for the NPDSCH carrying SystemInformationBlockType1-NB is determined based on the parameter schedulingInfoSIB1 configured by higher-layers and according to Table 16.4.1.3-5.
Table 16.4.1.3-5: Number of repetitions and subframe index for NPDSCH carrying SystemInformationBlockType1-NB, TDD.
|
Value of schedulingInfoSIB1 |
Number of NPDSCH repetitions |
Subframe index |
|
0 |
4 |
0 |
|
1 |
8 |
0 |
|
2 |
16 |
0 |
|
3 |
4 |
0 |
|
4 |
8 |
0 |
|
5 |
16 |
0 |
|
6 |
4 |
0 |
|
7 |
8 |
0 |
|
8 |
16 |
0 |
|
9 |
4 |
0 |
|
10 |
8 |
0 |
|
11 |
16 |
0 |
|
12-15 |
16 |
4 |
For the TDD NB-IoT carrier on which NPSS/NSSS/NPBCH are detected, the starting radio frame for the first transmission of the NPDSCH carrying SystemInformationBlockType1-NB is determined according to Table 16.4.1.3-6.
Table 16.4.1.3-6: Starting radio frame for the first transmission of the NPDSCH carrying SystemInformationBlockType1-NB, TDD.
|
Subframe index |
Number of NPDSCH repetitions |
|
Starting radio frame number for SystemInformationBlockType1-NB repetitions (nf mod 256) |
|
0 |
4 |
|
1 |
|
|
17 |
||
|
|
33 |
||
|
|
49 |
||
|
0 |
8 |
|
1 |
|
|
17 |
||
|
0 |
16 |
Any |
nf mod 256 = 1 |
|
4 |
16 |
|
nf mod 256 = 0 |
|
|
nf mod 256 = 1 |
mod 4 = 0
mod 4 = 1
mod 4 = 2
mod 2 = 0
mod 2 = 1
mod 2 = 0For a higher layer configured TDD NB-IoT carrier, the number of repetitions and subframe index for the NPDSCH carrying SystemInformationBlockType1-NB is determined based on the parameter schedulingInfoSIB1 configured by higher-layers and according to Table 16.4.1.3-7.
Table 16.4.1.3-7: Number of repetitions and subframe index for NPDSCH carrying SystemInformationBlockType1-NB, TDD.
|
Value of schedulingInfoSIB1 |
Number of NPDSCH repetitions |
Subframe index |
|
0 |
8 |
0, 5 |
|
1 |
16 |
0, 5 |
|
2 |
8 |
0, 5 |
|
3 |
16 |
0, 5 |
|
4 |
8 |
0, 5 |
|
5 |
16 |
0, 5 |
|
6 |
8 |
0, 5 |
|
7 |
16 |
0, 5 |
For a higher layer configured TDD NB-IoT carrier, the starting radio frame for the first transmission of the NPDSCH carrying SystemInformationBlockType1-NB is determined according to Table 16.4.1.3-8.
Table 16.4.1.3-8: Starting radio frame for the first transmission of the NPDSCH carrying SystemInformationBlockType1-NB, TDD.
|
Number of NPDSCH repetitions |
|
Starting radio frame number for SystemInformationBlockType1-NB repetitions (nf mod 256) |
|
8 |
|
0 |
|
|
16 |
|
|
16 |
|
0 |
|
|
1 |
mod 2 = 0
mod 2 = 1
mod 2 = 016.4.1.4 NPDSCH starting position
The starting OFDM symbol for NPDSCH is given by index in the first slot in a subframe 
and is determined as follows
– if subframe is a subframe used for receiving SIB1-NB
– 
if the value of the higher layer parameter operationModeInfo is set to ’00’ or ’01’
– 
if the value of the higher layer parameter operationModeInfo is set to ’10’ and the value of the higher layer parameter sib-GuardbandInfo is set to ’10’ or ’11’ for TDD
– 
otherwise
– elseif subframe 
is a special subframe for NPDSCH without repetition
– 
where 
is given by the higher layer parameter eutraControlRegionSize if the value of the higher layer parameter eutraControlRegionSize is present
– 
otherwise
– else
– 
is given by the higher layer parameter eutraControlRegionSize if the value of the higher layer parameter eutraControlRegionSize is present
– 
otherwise
16.4.1.5 Modulation order and transport block size determination
To determine the modulation order in the NPDSCH, the UE shall
– if the UE is configured with higher layer parameter npdsch-16QAM-Config and the DCI is mapped onto the UE specific search space given by C-RNTI, or the UE is configured with higher layer parameter pur-DL-16QAM-Config and the DCI is mapped onto the UE specific search space given by PUR-RNTI,
– If the 4-bit "modulation and coding scheme" field (
) in the DCI is set to ‘1111’,
– use modulation order, 
= 4
– otherwise
– use modulation order, 
= 2
– otherwise
– use modulation order, 
= 2.
To determine the transport block size in the NPDSCH, the UE shall first,
– if NPDSCH carries SystemInformationBlockType1-NB
– set 
to the value of the parameter schedulingInfoSIB1 configured by higher-layers
– else if NPDSCH with 16QAM
– read the 4-bit "modulation and coding scheme for 16QAM" () in the DCI
– If for the carrier on which NPSS/NSSS/NPBCH are detected the value of the higher layer parameter operationModeInfo is set to ’00’ or ’01’, or if the value of the higher layer parameter inbandCarrierInfo-r13 is configured for a higher layer configured carrier if any, set , otherwise set
– otherwise
– read the 4-bit "modulation and coding scheme" field (
) in the DCI and set 
.
and second,
– if NPDSCH carries SystemInformationBlockType1-NB
– use Clause 16.4.1.5.2 for determining its transport block size.
– otherwise,
– read the 3-bit "resource assignment" field (
) in the DCI and determine its TBS by the procedure in Clause 16.4.1.5.1.
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 npdsch-MultiTB-Config and single TB is scheduled in the corresponding DCI
– the NDI and HARQ process ID as signalled on NPDCCH, and the TBS, as determined above, shall be delivered to higher layers,
otherwise
– the NDI as signalled on NPDCCH, and the TBS, as determined above, shall be delivered to higher layers. If the UE is configured with higher layer parameter npdsch-MultiTB-Config and multiple TB are scheduled in the corresponding DCI, the HARQ process ID of 0 is for the first TB and HARQ process ID of 1 shall be assumed for the second TB, otherwise, HARQ process ID of 0 shall be assumed.
16.4.1.5.1 Transport blocks not mapped for SystemInformationBlockType1-NB
The TBS is given by the (
,
) entry of Table 16.4.1.5.1-1.
If for the carrier on which NPSS/NSSS/NPBCH are detected the value of the higher layer parameter operationModeInfo is set to ’00’ or ’01’, or if the value of the higher layer parameter inbandCarrierInfo-r13 is configured for a higher layer configured carrier if any,
– if NPDSCH with 16QAM , otherwise 
;
otherwise,
– if NPDSCH with 16QAM , otherwise .
Table 16.4.1.5.1-1: Transport block size (TBS) table.
|
|
|
|||||||
|
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 |
1032 |
|
7 |
104 |
224 |
328 |
472 |
584 |
680 |
968 |
1224 |
|
8 |
120 |
256 |
392 |
536 |
680 |
808 |
1096 |
1352 |
|
9 |
136 |
296 |
456 |
616 |
776 |
936 |
1256 |
1544 |
|
10 |
144 |
328 |
504 |
680 |
872 |
1032 |
1384 |
1736 |
|
11 |
176 |
376 |
584 |
776 |
1000 |
1192 |
1608 |
2024 |
|
12 |
208 |
440 |
680 |
904 |
1128 |
1352 |
1800 |
2280 |
|
13 |
224 |
488 |
744 |
1032 |
1256 |
1544 |
2024 |
2536 |
|
14 |
256 |
552 |
840 |
1128 |
1416 |
1736 |
2280 |
2856 |
|
15 |
280 |
600 |
904 |
1224 |
1544 |
1800 |
2472 |
3112 |
|
16 |
296 |
632 |
968 |
1288 |
1608 |
1928 |
2600 |
3240 |
|
17 |
336 |
696 |
1064 |
1416 |
1800 |
2152 |
2856 |
3624 |
|
18 |
376 |
776 |
1160 |
1544 |
1992 |
2344 |
3112 |
4008 |
|
19 |
408 |
840 |
1288 |
1736 |
2152 |
2600 |
3496 |
4264 |
|
20 |
440 |
904 |
1384 |
1864 |
2344 |
2792 |
3752 |
4584 |
|
21 |
488 |
1000 |
1480 |
1992 |
2472 |
2984 |
4008 |
4968 |
16.4.1.5.2 Transport blocks mapped for SystemInformationBlockType1-NB
The TBS is given by the
entry of Table 16.4.1.5.2-1 for FDD, and Table 16.4.1.5.2-2 for TDD NB-IoT carrier on which NPSS/NSSS/NPBCH are detected and Table 16.4.1.5.2-3 for a higher layer configured TDD NB-IoT carrier.
Table 16.4.1.5.2-1: Transport block size (TBS) table for NPDSCH carrying SystemInformationBlockType1-NB, FDD
|
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
|
TBS |
208 |
208 |
208 |
328 |
328 |
328 |
440 |
440 |
440 |
680 |
680 |
680 |
Reserved |
|||
Table 16.4.1.5.2-2: Transport block size (TBS) table for NPDSCH carrying SystemInformationBlockType1-NB, TDD
|
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
|
TBS |
208 |
208 |
208 |
328 |
328 |
328 |
440 |
440 |
440 |
680 |
680 |
680 |
208 |
328 |
440 |
680 |
Table 16.4.1.5.2-3: Transport block size (TBS) table for NPDSCH carrying SystemInformationBlockType1-NB, TDD
|
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|
TBS |
208 |
208 |
328 |
328 |
440 |
440 |
680 |
680 |
16.4.2 UE procedure for reporting ACK/NACK
The UE shall upon detection of a NPDSCH transmission ending in NB-IoT subframe n intended for the UE and for which an ACK/NACK shall be provided, start, after the end of
– 
DL subframe for FDD,
– 
NB-IoT UL subframes following the end of n+12 subframe for TDD,
transmission of the NPUSCH carrying ACK/NACK response, and SR (if any) if the serving cell is FDD and the UE is configured with higher layer parameter sr-with-HARQ-ACK-Config, using NPUSCH format 2 in N consecutive NB-IoT UL slots, where
– 
, where
– the value of 
is given by the higher layer parameter ack-NACK-NumRepetitions-Msg4 configured for the associated NPRACH resource for Msg4 NPDSCH transmission, and higher layer parameter ack-NACK-NumRepetitions otherwise,
– the value of 
is the number of slots of the resource unit (defined in clause 10.1.2.3 of [3]), and
– if the UE is configured with higher layer parameter harq-ACK-Bundling in npdsch-MultiTB-Config, then 
, otherwise 
, where the value of 
is determined by the Number of scheduled TB for Unicast field if present in the NPDCCH corresponding to the NPDSCH, otherwise 
,
– allocated subcarrier for ACK/NACK and value of k0 is determined by the ACK/NACK resource field in the DCI format of the corresponding NPDCCH according to Table 16.4.2-1, and Table 16.4.2-2,
– for FDD, 
.
– for TDD, 
.
– For 
– if the UE is configured with higher layer parameter harq-AckBundling in npdsch-MultiTB-Config, and the NPDSCH corresponding to a NPDCCH with DCI CRC scrambled by C-RNTI,
– the ACK/NACK response is generated by performing a logical AND operation of HARQ-ACKs corresponding to the TBr+1 , 
– otherwise,
– NB-IoT UL slots 
with 
of the NPUSCH carry ACK/NACK response for TBr+1 , 
Table 16.4.2-1: ACK/NACK subcarrier and 
for NPUSCH with subcarrier spacing 
.
|
ACK/NACK resource field |
ACK/NACK subcarrier |
|
|
0 |
38 |
13 |
|
1 |
39 |
13 |
|
2 |
40 |
13 |
|
3 |
41 |
13 |
|
4 |
42 |
13 |
|
5 |
43 |
13 |
|
6 |
44 |
13 |
|
7 |
45 |
13 |
|
8 |
38 |
21 |
|
9 |
39 |
21 |
|
10 |
40 |
21 |
|
11 |
41 |
21 |
|
12 |
42 |
21 |
|
13 |
43 |
21 |
|
14 |
44 |
21 |
|
15 |
45 |
21 |
Table 16.4.2-2: ACK/NACK subcarrier and 
for NPUSCH with subcarrier spacing 
.
|
ACK/NACK resource field |
ACK/NACK subcarrier |
|
|
0 |
0 |
13 |
|
1 |
1 |
13 |
|
2 |
2 |
13 |
|
3 |
3 |
13 |
|
4 |
0 |
15 |
|
5 |
1 |
15 |
|
6 |
2 |
15 |
|
7 |
3 |
15 |
|
8 |
0 |
17 |
|
9 |
1 |
17 |
|
10 |
2 |
17 |
|
11 |
3 |
17 |
|
12 |
0 |
18 |
|
13 |
1 |
18 |
|
14 |
2 |
18 |
|
15 |
3 |
18 |
