S 36.213 Table 16.6-1/2/3) meets this condition b = u R k Starting subframe b consecutive subframes excluding subframes used for transmission of SI messages Figure 6.14 Search spaces and determination of NPDCCH location [4,25]. Internet of Things RNTI and, if found, decode the NPDCCH. Three DCI formats have been specified for NB- IoT, namely DCI format NO, N1, and N2. When an NB-IoT UE receives a NPDCCH, it can distinguish different formats in the fol- lowing manner. DCI format N2 is implicitly indicated, wherein the CRC is scrambled with the P-RNTI. If the CRC is scrambled with the C-RNTI, then the first bit in the message indicates whether it contains DCI format NO or N1. For the case that the CRC is scrambled with the RA-RNTI, the content is a restricted DCI format N1 including only those fields required for the random-access response. The scheduling delay is included in DCI formats NO and N1; that is, the time interval between the end of NPDCCH and the start of NPDSCH or the start of narrowband physical uplink shared channel (NPUSCH). This delay is at least five subframes for the NPDSCH and eight subframes for the NPUSCH. For down- link transmission via DCI format N2, the scheduling delay is fixed and equal to 10 sub- frames [4] (see Table 6.3). In order to determine whether there is any data sent through NPDSCH to an NB-IoT UE or to detect any uplink grant for NPUSCH, the UE should monitor and try to decode various regions within downlink subframes. There is no information explicitly sent by the network regarding which regions the UE needs to monitor. The UE should monitor all possible regions that are allowed for NPDCCH and attempt to decode the information; that is, blind decoding. However, the UE does not need to decode every possible combination of resource elements within a subframe. There are a certain set of predefined regions in which a PDCCH could be allocated. The UE monitors only those predefined regions which are called NPDCCH search spaces. Since an NB-IoT UE does not know in advance when a DCI 