8.1.4 NB-IoT Reference system configurations
36.5083GPPCommon test environments for User Equipment (UE) conformance testingEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Release 17TS
The reference system configurations specified in this sub clause apply to all NB-IoT test cases unless otherwise specified.
8.1.4.1 NB-IoT Simulated network scenarios
Simulated network scenarios to be tested are listed in this sub clause.
NOTE 1: The number of cells specified does not necessarily correspond to the maximum number of resources to be configured simultaneously in test equipment. Please refer to clause 8.3.1 for such information.
NOTE 2: Void.
8.1.4.1.1 NB-IoT Single cell network scenarios
For NB-IoT basic single cell environment, Ncell 1 is used.
8.1.4.1.2 NB-IoT single mode multi cell network scenarios
For NB-IoT basic intra-frequency multi cell environment, Ncell 1, Ncell 2 and Ncell 4 are used.
For NB-IoT basic inter-frequency multi cell environment, Ncell 1 Ncell 3 and Ncell 6 are used.
For NB-IoT basic inter-band cell environment, Ncell 1 and Ncell 10 are used.
For NB-IoT multi tracking area intra-frequency multi cell environment, Ncell 1 and Ncell 11 are used.
For NB-IoT multi tracking area inter-frequency multi cell environment, Ncell 1 and Ncell 23 are used.
For NB-IoT multi PLMN inter-frequency multi cell environment, Ncell 1, Ncell 12, Ncell 13 and Ncell 14 are used.
8.1.4.2 NB-IoT Simulated cells
NOTE 1: Void
NOTE 2: Test frequency and range defined in table 8.1.4.2-1 do not apply to 36.521-1 test cases.
Test frequencies and simulated cells are defined in table 8.1.4.2-1. For NB-IoT cells, f1 is the default test frequency.
Default parameters for simulated cells are specified in table 8.1.4.2-1A and table 8.1.4.2-2.
Common parameters for simulated cells are specified in subclauses 8.1.4.3.
Table 8.1.4.2-1: Definition of test frequencies and simulated NB-IoT cells – Batch1
Test frequency |
RAT |
Operating band |
Range |
Simulated cells |
f1 |
NB-IoT |
Operating band under test |
Mid (Note 1) |
Ncell 1, Ncell 1a, Ncell 2, Ncell 4, Ncell5, Ncell 6a, Ncell 11 (Note 2), Ncell 18 |
f2 |
NB-IoT |
Operating band under test |
High (Note 1) |
Ncell 3, Ncell 12, Ncell 23 |
f3 |
NB-IoT |
Operating band under test |
Low (Note 1) |
Ncell 6, Ncell 13 |
f4 |
NB-IoT |
Operating band under test |
(Note 1) |
Ncell 14 |
f5 |
NB-IoT |
Operating band for inter-band cells |
Mid (Note 1) |
Ncell 10 |
Note 1: For signalling test, see clause 8.3.2.3 (note that f4 is not defined for signalling tests). Note 2: For signalling test, simultaneous co-existence of Ncell 2 with Ncell 11 is not allowed. |
Table 8.1.4.2-1A: Default NB-IoT parameters for simulated NB-IoTcells – Batch1
cell ID |
NB-IoT Cell Identifier |
Physical layer cell identity |
|
eNB Identifier |
Cell Identity |
||
Ncell 1 |
‘0000 0000 0000 0000 0001’B |
‘0000 0000’B |
0 |
Ncell 1a |
‘0000 0000 0000 0000 0001’B |
‘0000 0001’B |
1 |
Ncell 2 |
‘0000 0000 0000 0000 0001’B |
‘0000 0010’B |
2 |
Ncell 3 |
‘0000 0000 0000 0000 0010’B |
‘0000 0011’B |
3 |
Ncell 4 |
‘0000 0000 0000 0000 0011’B |
‘0000 0100’B |
4 |
Ncell 5 |
‘0000 0000 0000 0000 0011’B |
‘0000 0101’B |
5 |
Ncell 6 |
‘0000 0000 0000 0000 0100’B |
‘0000 0110’B |
6 |
Ncell 6a |
‘0000 0000 0000 0000 0100’B |
‘0000 0110’B |
6 |
Ncell 10 |
‘0000 0000 0000 0000 0101’B |
‘0000 1010’B |
10 |
Ncell 11 |
‘0000 0000 0000 0000 0110’B |
‘0000 1011’B |
11 |
Ncell 12 |
‘0000 0000 0000 0000 0010’B |
‘0000 1100’B |
12 |
Ncell 13 |
‘0000 0000 0000 0000 0100’B |
‘0000 1101’B |
13 |
Ncell 14 |
‘0000 0000 0000 0000 0111’B |
‘0000 1110’B |
14 |
Ncell 18 |
‘0000 0000 0000 0000 0100’B |
‘0001 0010’B |
18 |
Ncell 23 |
‘0000 0000 0000 0000 0110’B |
‘0001 0111’B |
23 |
Table 8.1.4.2-2: Default NAS parameters for simulated NB-IoT cells – Batch1
cell ID |
Tracking Area |
TA# list (Note 1) |
GUTI (Note 2) |
|||||
TA# |
PLMN |
TAC |
MME Identifier |
M-TMSI |
||||
MCC |
MNC |
MME Group ID |
MME Code |
|||||
Ncell 1 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
Arbitrarily selected according to TS 23.003 subclause 2.8 [2]. |
|
Ncell 1a |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 2 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 3 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 4 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 5 |
TAI-2 |
(Note 3) |
2 |
TAI-2 |
32769 |
1 |
||
Ncell 6 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 6a |
TAI-2 |
(Note 3) |
2 |
TAI-2 |
32769 |
1 |
||
Ncell 10 |
TAI-10 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 11 |
TAI-2 |
(Note 3) |
2 |
TAI-2 |
32769 |
1 |
||
Ncell 12 |
TAI-3 |
002 |
11 |
1 |
TAI-3 |
32769 |
1 |
|
Ncell 13 |
TAI-4 |
003 |
21 |
1 |
TAI-4 |
32769 |
1 |
|
Ncell 14 |
TAI-5 |
004 |
31 |
1 |
TAI-5 |
32769 |
1 |
|
Ncell 18 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 23 |
TAI-2 |
(Note 3) |
2 |
TAI-2 |
32769 |
1 |
||
Note 1: The value(s) in the column TA# list indicates TAI(s) included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell. Note 2: The value in the column GUTI indicates GUTI included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell. Note 3: Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card (subclause 4.9.3). |
Table 8.1.4.2-3: Default NAS parameters for simulated NB-IoT cells – Batch2
NAS cell ID |
Tracking Area |
TA# list (Note 1) |
GUTI (Note 2) |
|||||
TA# |
PLMN |
TAC |
MME Identifier |
M-TMSI |
||||
MCC |
MNC |
MME Group ID |
MME Code |
|||||
Ncell 50 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
Arbitrarily selected according to TS 23.003 subclause 2.8 [2]. |
|
Ncell 51 |
TAI-2 |
(Note 3) |
2 |
TAI-2 |
32770 |
1 |
||
Ncell 52 |
TAI-3 |
(Note 3) |
3 |
TAI-3 |
32771 |
1 |
||
Ncell 53 |
TAI-4 |
(Note 3) |
4 |
TAI-4 |
32772 |
1 |
||
Ncell 54 |
TAI-12 |
002 |
101 |
3 |
TAI-12 |
32777 |
1 |
|
Ncell 55 |
TAI-7 |
(Note 4) |
02 |
1 |
TAI-7 |
32775 |
1 |
|
Ncell 56 |
TAI-8 |
(Note 4) |
02 |
2 |
TAI-8 |
32776 |
1 |
|
Ncell 57 |
TAI-9 |
002 |
101 |
1 |
TAI-9 |
32777 |
1 |
|
Ncell 58 |
TAI-10 |
003 |
101 |
1 |
TAI-10 |
32778 |
1 |
|
Ncell 59 |
TAI-9 |
002 |
101 |
1 |
TAI-9 |
32777 |
1 |
|
Ncell 60 |
TAI-11 |
002 |
101 |
2 |
TAI-11 |
32779 |
1 |
|
Ncell 61 |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
32769 |
1 |
||
Ncell 62 |
TAI-7 |
(Note 4) |
02 |
1 |
TAI-7 |
32775 |
1 |
|
Ncell 63 |
TAI-13 |
(Note 4) |
03 |
1 |
TAI-13 |
32770 |
1 |
|
Note 1: The value(s) in the column TA# list indicates TAI(s) included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell. Note 2: The value in the column GUTI indicates GUTI included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell. Note 3: Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card (subclause 4.9.3). Note 4: Set to the same Mobile Country Code stored in EFIMSI on the test USIM card (subclause 4.9.3). Note 5: Ncell 50 is a serving cell and the other cells are suitable neighbour cells. The definitions are specified in subclause 8.3.2.2.1. |
Table 8.1.4.2-4: Default cell identifiers for simulated NB-IoT cells – Batch2 when cells are in same PLMN
cell ID |
Frequency |
NB-IoT Cell Identifier |
Physical layer cell identity |
|
eNB Identifier |
Cell Identity |
|||
Ncell 50 |
f1 |
‘0000 0000 0000 0001 0001’B |
‘0000 0001’B |
1 |
Ncell 51 |
f1 |
‘0000 0000 0000 0001 0001’B |
‘0000 0010’B |
2 |
Ncell 52 |
f2 |
‘0000 0000 0000 0001 0010’B |
‘0000 0011’B |
3 |
Ncell 53 |
f1 |
‘0000 0000 0000 0001 0001’B |
‘0000 0100’B |
4 |
Ncell 54 |
NA |
NA |
NA |
NA |
Ncell 55 |
NA |
NA |
NA |
NA |
Ncell 56 |
NA |
NA |
NA |
NA |
Ncell 57 |
NA |
NA |
NA |
NA |
Ncell 58 |
NA |
NA |
NA |
NA |
Ncell 61 |
f2 |
‘0000 0000 0000 0010 0001’B |
‘0001 0001’B |
17 |
Table 8.1.4.2-5: Default cell identifiers for simulated NB-IoT cells – Batch2 when cells are in different PLMNs
NAS cell ID |
PLMN |
Frequency |
NB-IoT Cell Identifier |
Physical layer cell identity |
|
eNB Identifier |
Cell Identity |
||||
Ncell 50 |
MCC/MNC= MCC/MNC in USIM |
f1 |
‘0000 0000 0000 0010 0001’B |
‘0000 0001’B |
1 |
Ncell 51 |
MCC/MNC= MCC/MNC in USIM |
f1 |
‘0000 0000 0000 0010 0001’B |
‘0000 0010’B |
2 |
Ncell 52 |
MCC/MNC= MCC/MNC in USIM |
f1 |
‘0000 0000 0000 0010 0001’B |
‘0000 0011’B |
3 |
Ncell 53 |
MCC/MNC= MCC/MNC in USIM |
f1 |
‘0000 0000 0000 0010 0001’B |
‘0000 0100’B |
4 |
Ncell 54 |
MCC=002 MNC=101 |
f2 |
‘0000 0000 0000 0011 0101’B |
‘0001 0111’B |
23 |
Ncell 55 |
MCC = MCC in USIM MNC=02 |
f2 |
‘0000 0000 0000 0010 0010’B |
‘0000 1011’B |
11 |
Ncell 56 |
MCC= MCC in USIM MNC=02 |
f2 |
‘0000 0000 0000 0010 0010’B |
‘0000 1100’B |
12 |
Ncell 57 |
MCC=002 MNC=101 |
f3 (Note 1) |
‘0000 0000 0000 0010 0011’B |
‘0000 1101’B |
13 |
Ncell 58 |
MCC=003 MNC=101 |
f4 (Note 1) |
‘0000 0000 0000 0010 0100’B |
‘0000 1110’B |
14 |
Ncell 59 |
MCC=002 MNC=101 |
f3 (Note 1) |
‘0000 0000 0000 0010 0011’B |
‘0000 1111’B |
15 |
Ncell 60 |
MCC=002 MNC=101 |
f3 (Note 1) |
‘0000 0000 0000 0010 0011’B |
‘0001 0000’B |
16 |
Ncell 61 |
MCC/MNC= MCC/MNC in USIM |
f1 |
‘0000 0000 0000 0010 0001’B |
‘0001 0001’B |
17 |
Ncell 62 |
MCC = MCC in USIM MNC=02 |
f1 |
‘0000 0000 0000 0010 0010’B |
‘0001 0010’B |
18 |
Ncell 63 |
MCC = MCC in USIM MNC=03 |
f1 |
‘0000 0000 0000 0010 0010’B |
‘0001 0011’B |
19 |
Note 1: The test frequency f3 or f4 is allocated to the cell if f1 and f2 are already allocated to the cells in the test. Otherwise, f1 or f2 is allocated instead. Note that f4 is not defined for signalling tests (see clause 8.3.2.3). |
Table 8.1.4.2-6 defines TAC values only for Idle Mode Test Cases defined in TS 36.523-1 section 22.2.
Table 8.1.4.2-6: Tracking Area Code (TAC) for NB-IoT cells – Batch1 for Idle Mode test cases
cell ID |
TAC |
Ncell 1 |
1 |
Ncell 2 |
2 |
Ncell 3 |
3 |
Ncell 4 |
4 |
Ncell 6 |
6 |
Ncell 11 |
11 |
Ncell 12 |
12 |
Ncell 13 |
13 |
Ncell 14 |
14 |
Ncell 23 |
23 |
8.1.4.3 NB-IoT Common parameters for simulated cells
The parameters specified in this sub clause apply to all simulated cells unless otherwise specified.
8.1.4.3.1 NB-IoT Common configurations of system information blocks
8.1.4.3.1.1 NB-IoT Combinations of system information blocks
The combination of system information blocks required by a test case depends on the test case scenario. In this clause, the following combinations of system information blocks are defined.
Combination 1 is the default combination which applies to the following test case scenarios:
– single cell scenario
Combination 2 applies to the following test case scenarios:
– intra-frequency multi cell scenario
– intra-frequency multi cell scenario with neighbouring cell related information
Combination 3 applies to the following test case scenarios:
– inter-frequency multi cell scenario
Combination 4 applies to the following test case scenarios:
– access barring single cell scenario
Combination 5 applies to the following test case scenarios:
– SC-PTM single cell scenario (SC-PTM cell broadcasting SIB20-NB)
Combination 6 applies to the following test case scenarios:
– single cell on multi carriers scenario
Combination 7 applies to the following test case scenarios:
– single cell NPRACH resources using preamble format 2 on non-anchor carriers scenario
Combination 8 is the default combination which applies to the following test case scenarios:
– single cell scenario + NTN
Combination 9 is the default combination which applies to the following test case scenarios:
– intra-frequency multi cell scenario + NTN
– intra-frequency multi cell scenario with neighbouring cell related information + NTN
Table 8.1.4.3.1.1-1: Combinations of system information blocks
System information block type |
|||||||||||
Combination No. |
SIB2-NB |
SIB3-NB |
SIB4-NB |
SIB5-NB |
SIB14-NB |
SIB16-NB |
SIB20-NB |
SIB22-NB |
SIB23-NB |
SIB31-NB |
|
1 |
X |
||||||||||
2 |
X |
X |
X |
||||||||
3 |
X |
X |
X |
||||||||
4 |
X |
X |
X |
||||||||
5 |
X |
X |
|||||||||
6 |
X |
X |
|||||||||
7 |
X |
X |
X |
||||||||
8 |
X |
X |
|||||||||
9 |
X |
X |
X |
X |
8.1.4.3.1.2 NB-IoT Scheduling of system information blocks
The scheduling configurations for combinations of system information blocks are defined in the following tables.
Table 8.1.4.3.1.2-1: Scheduling for combination 1
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
Table 8.1.4.3.1.2-2: Scheduling for combination 2
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB3-NB |
3 |
64 |
every16thRF |
256 |
SIB4-NB |
Table 8.1.4.3.1.2-3: Scheduling for combination 3
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB3-NB |
3 |
64 |
every16thRF |
256 |
SIB5-NB |
Table 8.1.4.3.1.2-4: Scheduling for combination 4
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB3-NB |
3 |
64 |
every16thRF |
256 |
SIB14-NB |
Table 8.1.4.3.1.2-5: Scheduling for combination 5
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB20-NB |
Table 8.1.4.3.1.2-6: Scheduling for combination 6
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB22-NB |
Table 8.1.4.3.1.2-7: Scheduling for combination 7
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB22-NB |
3 |
64 |
every16thRF |
256 |
SIB23-NB |
Table 8.1.4.3.1.2-8: Scheduling for combination 8
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB31-NB |
Table 8.1.4.3.1.2-9: Scheduling for combination 9
Scheduling Information No. |
Periodicity [radio frames] |
Repetition pattern [radio frames] |
TB size [bits] |
Mapping of system information blocks |
1 |
64 |
every8thRF |
552 |
SIB2-NB |
2 |
64 |
every16thRF |
256 |
SIB3-NB |
3 |
64 |
every16thRF |
256 |
SIB4-NB |
4 |
64 |
every16thRF |
256 |
SIB31-NB |
8.1.4.3.2 NB-IoT Common contents of system information messages
– MasterInformationBlock-NB
The MasterInformationBlock-NB includes the system information transmitted on BCH.
Table 8.1.4.3.2-1: MasterInformationBlock-NB
Derivation Path: 36.331 clause 6.7.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-NB ::= SEQUENCE { |
|||
systemFrameNumber-MSB-r13 |
A valid value as defined in TS 36.331 [17] |
||
hyperSFN-LSB-r13 |
A valid value as defined in TS 36.331 [17] |
||
schedulingInfoSIB1-r13 |
2 |
TBS = 208 bits, 16 repetitions |
|
systemInfoValueTag-r13 |
0 |
||
ab-Enabled-r13 |
FALSE |
||
operationModeInfo-r13 CHOICE { |
|||
inband-SamePCI-r13 SEQUENCE { |
Inband-Same |
||
eutra-CRS-SequenceInfo-r13 |
23 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB30 |
24 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB35 |
|
7 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB17 |
|
8 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB22 |
|
} |
|||
inband-DifferentPCI-r13 SEQUENCE { |
Inband_Different |
||
eutra-NumCRS-Ports-r13 |
same |
same number of ports as NRS |
|
rasterOffset-r13 |
2.5*(2MDL+1) kHz |
MDL See subclause 8.1.3.1 |
|
spare |
’00’B |
||
} |
|||
guardband-r13 SEQUENCE { |
Guardband |
||
rasterOffset-r13 |
2.5*(2MDL+1) kHz |
MDL See subclause 8.1.3.1 |
|
spare |
‘000’B |
||
} |
|||
standalone-r13 SEQUENCE { |
Standalone |
||
spare |
‘0000 0’B |
||
} |
|||
} |
|||
additionalTransmissionSIB1-r15 |
FALSE |
A Rel-13/Rel-14 UE will interpret FALSE as spare ‘0’ |
|
spare |
‘0000 0000 00’B |
Rel-15 |
|
} |
Condition |
Explanation |
Inband-Same |
In-band with same PCI test environment |
Inband-Different |
In-band with different PCI test environment |
PRB30 |
For 10 MHz LTE Cell with In-Band NB-IoT in PRB 30 |
PRB35 |
For 10 MHz LTE Cell with In-Band NB-IoT in PRB 35 |
PRB17 |
For 5 MHz LTE Cell with In-Band NB-IoT in PRB 17 |
PRB22 |
For 5 MHz LTE Cell with In-Band NB-IoT in PRB 22 |
Standalone |
Standalone test environment |
Guardband |
Guard-band test environment |
– MasterInformationBlock-TDD-NB
The MasterInformationBlock-TDD-NB includes the system information transmitted on BCH in TDD.
Table 8.1.4.3.2-1A: MasterInformationBlock-TDD-NB
Derivation Path: 36.331 clause 6.7.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-TDD-NB ::= SEQUENCE { |
|||
systemFrameNumber-MSB-r15 |
A valid value as defined in TS 36.331 [17] |
||
hyperSFN-LSB-r15 |
A valid value as defined in TS 36.331 [17] |
||
schedulingInfoSIB1-r15 |
2 |
16 repetitions |
|
systemInfoValueTag-r15 |
0 |
||
ab-Enabled-r15 |
FALSE |
||
operationModeInfo-r15 CHOICE { |
|||
inband-SamePCI-r15 SEQUENCE { |
Inband-Same |
||
eutra-CRS-SequenceInfo-r15 |
23 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB30 |
24 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB35 |
|
7 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB17 |
|
8 |
As specified in TS 36.213 [29] Clause 16.8 |
PRB22 |
|
sib-InbandLocation-r15 |
lower |
||
} |
|||
inband-DifferentPCI-r15 SEQUENCE { |
Inband_Different |
||
eutra-NumCRS-Ports-r15 |
same |
same number of ports as NRS |
|
rasterOffset-r15 |
2.5*(2MDL+1) kHz |
MDL See subclause 8.1.3.1 |
|
sib-InbandLocation-r15 |
lower |
||
spare |
’00’B |
||
} |
|||
guardband-r15 SEQUENCE { |
Guardband |
||
rasterOffset-r15 |
2.5*(2MDL+1) kHz |
MDL See subclause 8.1.3.1 |
|
sib-GuardbandInfo-r15 CHOICE { |
|||
sib-GuardbandAnchor-r15 SEQUENCE { |
sib-GuardbandAnchor |
||
spare |
‘0’B |
||
} |
|||
sib-GuardbandGuardband-r15 SEQUENCE { |
sib-GuardbandGuardband |
||
spare |
‘0’B |
||
} |
|||
sib-GuardbandInbandSamePCI-r15 SEQUENCE { |
sib-GuardbandInbandSamePCI |
||
spare |
‘0’B |
||
} |
|||
sib-GuardbandinbandDiffPCI-r15 SEQUENCE { |
sib-GuardbandinbandDiffPCI |
||
sib-EUTRA-NumCRS-Ports-r15 |
same |
||
} |
|||
eutra-Bandwitdh-r15 |
bw5or10 |
EUTRA system bandwidth Value 5 or 10 MHz |
|
Bw15or20 |
EUTRA system bandwidth Value 15 or 20 MHz |
||
} |
|||
standalone-r15 SEQUENCE { |
Standalone |
||
sib-InbandLocation-r15 |
lower |
||
spare |
‘0000 0’B |
||
} |
|||
} |
|||
sib1-CarrierInfo-r15 |
anchor |
||
spare |
‘0000 0000 0’B |
||
} |
– SystemInformation-NB
The SystemInformation-NB message is used to convey one or more System Information Blocks. All the SIBs included are transmitted with the same periodicity.
Table 8.1.4.3.2-2: SystemInformation-NB
Derivation Path: 36.331 clause 6.7.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformation-NB ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
systemInformation-r13 SEQUENCE { |
|||
sib-TypeAndInfo-r13 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE {} |
See subclause 8.1.4.3.1 |
||
lateNonCriticalExtension |
Not present |
||
nonCriticalExtension SEQUENCE {} |
Not present |
||
} |
|||
} |
|||
} |
– SystemInformationBlockType1-NB
SystemInformationBlockType1-NB contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information.
Table 8.1.4.3.2-3: SystemInformationBlockType1-NB
Derivation Path: 36.331 clause 6.7.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
hyperSFN-MSB-r13 |
A valid value as defined in TS 36.331 [17] |
||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
plmn-IdentityList-r13 SEQUENCE (SIZE (1.. maxPLMN-r11)) OF SEQUENCE { |
1 entry |
||
plmn-Identity-r13[1] SEQUENCE { |
|||
mcc |
See table 8.1.4.2-2 |
||
mnc |
See table 8.1.4.2-2 |
||
} |
|||
cellReservedForOperatorUse-r13[1] |
notReserved |
||
attachWithoutPDN-Connectivity-r13[1] |
true |
ATTACH_WITHOUT_PDN |
|
Not present |
ATTACH_WITH_PDN |
||
} |
|||
trackingAreaCode-r13 |
See table 8.1.4.2-2 |
||
cellIdentity-r13 |
Cell ID for the simulated cell |
||
cellBarred-r13 |
notBarred |
||
barred |
NTN |
||
intraFreqReselection-r13 |
notAllowed |
||
} |
|||
cellSelectionInfo-r13 SEQUENCE { |
|||
q-RxLevMin-r13 |
-70 (-140 dBm) |
For RF/RRM test cases |
RF |
-106 dBm |
For signalling test cases |
Signaling |
|
q-QualMin-r13 |
-20 (-20dB) |
||
} |
|||
p-Max-r13 |
Not Present |
||
freqBandIndicator-r13 |
Operating band under test. |
||
freqBandInfo-r13 |
Not Present |
||
multiBandInfoList-r13 |
Not Present |
||
downlinkBitmap-r13 |
Not Present |
||
eutraControlRegionSize-r13 |
n2 |
Inband-Same, Inband- Different |
|
Not Present |
Standalone, Guard |
||
nrs-CRS-PowerOffset-r13 |
dB0 |
Inband- Same |
|
Not Present |
Inband-Different, Standalone, Guardband |
||
schedulingInfoList-r13 |
See subclause 8.1.4.3.1 |
||
si-WindowLength-r13 |
ms160 |
||
si-RadioFrameOffset-r13 |
Not Present |
||
systemInfoValueTagList-r13 |
Not Present |
||
lateNonCriticalExtension |
Not Present |
||
nonCriticalExtension SEQUENCE { |
Not Present |
FDD |
|
cellSelectionInfo-v1350 |
Not Present |
TDD |
|
nonCriticalExtension SEQUENCE { |
|||
cellSelectionInfo-v1430 |
Not Present |
||
nonCriticalExtension SEQUENCE { |
|||
nrs-CRS-PowerOffset-v1450 |
Not Present |
||
nonCriticalExtension SEQUENCE { |
|||
tdd-Parameters-r15 SEQUENCE { |
|||
tdd-Config-r15 SEQUENCE { |
|||
subframeAssignment-r15 |
sa1 |
||
specialSubframePatterns-r15 |
ssp6 |
||
} |
|||
tdd-SI-CarrierInfo-r15 |
anchor |
||
tdd-SI-SubframesBitmap-r15 |
Not Present |
||
} |
|||
schedulingInfoList-v1530 |
Not Present |
||
nonCriticalExtension SEQUENCE { |
Not Present |
||
nonCriticalExtension SEQUENCE { |
NTN |
||
cellAccessRelatedInfo-NTN-r17 SEQUENCE { |
|||
cellBarred-NTN-r17 |
notBarred |
||
} |
|||
nonCriticalExtension |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Condition |
Explanation |
||
ATTACH_WITH_PDN |
If the UE shall perform ATTACH with PDN connectivity procedure. |
||
ATTACH_WITHOUT_PDN |
If the UE may perform ATTCH without PDN connectivity procedure. |
||
Inband_Same |
In-band with same PCI test environment |
||
Inband_Different |
In-band with different PCI test environment |
||
Standalone |
Standalone test environment |
||
Guardband |
Guard-band test environment |
||
RF |
For RF/RRM test cases |
||
Signaling |
For Signaling test cases |
||
NTN |
Non-Terrestrial Networks test environment |
8.1.4.3.3 NB-IoT Common contents of system information blocks
– SystemInformationBlockType2-NB
The IE SystemInformationBlockType2-NB contains radio resource configuration information that is common for all UEs.
Table 8.1.4.3.3-1: SystemInformationBlockType2-NB
Derivation Path: 36.331 clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType2-NB-r13 ::= SEQUENCE { |
|||
radioResourceConfigCommon-r13 SEQUENCE {} |
RadioResourceConfigCommonSIB-NB-DEFAULT |
See subclause 8.1.6 |
|
ue-TimersAndConstants-r13 SEQUENCE { |
|||
t300-r13 |
ms10000 |
||
t301-r13 |
ms10000 |
||
t310-r13 |
ms1000 |
||
n310-r13 |
n2 |
||
t311-r13 |
ms1000 |
||
n311-r13 |
n1 |
||
} |
|||
freqInfo-r13 SEQUENCE { |
|||
ul-CarrierFreq-r13 |
Not present |
Default UL EARFCN applies |
Standalone |
ul-CarrierFreq-r13 |
See subclause 8.1.3.1 |
Inband_Same, Inband_Different, Guardband |
|
additionalSpectrumEmission-r13 |
1 (NS_01) |
A-MPR doesn’t apply by default. See TS 36.101 table 6.2.4F -1. |
|
4 (NS_04) |
NS_04 |
||
} |
|||
timeAlignmentTimerCommon-r13 |
infinity |
||
multiBandInfoList-r13 SEQUENCE {} |
Not present |
||
lateNonCriticalExtension SEQUENCE { |
Not present |
FDD |
|
freqInfo-v1530 SEQUENCE { |
TDD |
||
tdd-UL-DL-AlignmentOffset-r15 |
khz0 |
||
} |
|||
} |
|||
} |
Condition |
Explanation |
Inband_Same |
In-band with same PCI test environment |
Inband_Different |
In-band with different PCI test environment |
Standalone |
Standalone test environment |
Guardband |
Guard-band test environment |
NS_04 |
When using the NS_04 frequency table variants in subclause 8.1.3.1 |
– SystemInformationBlockType3-NB
The IE SystemInformationBlockType3-NB contains cell re-selection information common for intra-frequency, inter-frequency as well as intra-frequency cell re-selection information other than neighbouring cell related.
Table 8.1.4.3.3-2: SystemInformationBlockType3-NB
Derivation Path: 36.331 clause 6.7.3.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
||||
cellReselectionInfoCommon-r13 SEQUENCE { |
||||
q-Hyst-r13 |
dB0 |
To reduce interference between intra-frequency multiple cells |
||
} |
||||
cellReselectionServingFreqInfo SEQUENCE-r13 { |
||||
s-NonIntraSearch-r13 |
31 (62dB) |
|||
} |
||||
intraFreqCellReselectionInfo-r13 SEQUENCE { |
||||
q-RxLevMin-r13 |
-70 (-140 dBm) |
For RF/RRM test cases |
||
-106 dBm |
For signalling test cases |
|||
q-QualMin-r13 |
Not present |
|||
p-Max-r13 |
Not present |
|||
s-IntraSearchP-r13 |
31 (62dB) |
|||
t-Reselection-r13 |
0 |
|||
} |
||||
freqBandInfo-r13 |
Not present |
|||
multiBandInfoList-r1 |
Not present |
|||
lateNonCriticalExtension |
Not present |
|||
} |
– SystemInformationBlockType4-NB
The IE SystemInformationBlockType4-NB contains neighbouring cell related information relevant only for intra-frequency cell re-selection. The IE includes cells with specific re-selection parameters.
Table 8.1.4.3.3-3: SystemInformationBlockType4-NB
Derivation Path: 36.331 clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
|||
intraFreqNeighCellList-r13 SEQUENCE (SIZE (1..maxCellIntra)) OF SEQUENCE {} |
Not present |
Not required unless Qoffset configuration is tested. When Qoffset configuration is tested, see table 8.3.3.1.1-1 |
|
intraFreqBlackCellList SEQUENCE-r13 (SIZE (1..maxCellBlack)) OF SEQUENCE {} |
Not present |
Not required unless Blacklisted cell list configuration is tested. When Blacklisted cell list configuration is tested, see table FFS. |
|
lateNonCriticalExtension |
Not present |
||
} |
– SystemInformationBlockType5-NB
The IE SystemInformationBlockType5-NB contains information relevant only for inter-frequency cell re-selection i.e. information about other NB-IOT frequencies and inter-frequency neighbouring cells relevant for cell re-selection. The IE includes cell re-selection parameters common for a frequency.
Table 8.1.4.3.3-4: SystemInformationBlockType5-NB
Derivation Path: 36.331 clause 6.7.3.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType5-NB-r13 ::= SEQUENCE { |
||||
interFreqCarrierFreqList-r13 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
The same number of entries as the configured inter-freq carriers. For Signalling test cases see clause 8.3.2.3 |
n denotes the index of the entry |
||
dl-CarrierFreq-r13[n] SEQUENCE { |
Downlink EARFCN under test. For Signalling test cases see clause 8.3.2.3 |
|||
carrierFreq-r13[n] |
Downlink EARFCN under test. For Signalling test cases see clause 8.3.2.3 |
|||
carrierFreqOffset-r13 [n] |
Not present |
|||
carrierFreqOffset-r13 [n] |
Offset of the NB-IOT channel number under test to the EARFCN under test |
RRM-InterFreq |
||
} |
||||
q-RxLevMin-r13[n] |
-65 (-130 dBm) |
For RF/RRM test cases |
||
-106 dBm |
For signalling test cases |
|||
q-QualMin-r13[n] |
Not present |
|||
p-Max-r13[n] |
Not present |
|||
q-OffsetFreq-r13[n] |
dB0 |
Qoffset doesn’t apply by default. |
||
interFreqNeighCellList-r13[n] SEQUENCE (SIZE (1..maxCellInter)) OF SEQUENCE {} |
Not present |
Not required unless Qoffset configuration is tested |
||
interFreqBlackCellList-r13[n] SEQUENCE (SIZE (1..maxCellBlack)) OF SEQUENCE {} |
Not present |
Not required unless Blacklisted cell list configuration is tested |
||
multiBandInfoList-r13 |
Not present |
|||
} |
||||
t-Reselection-r13 |
s0 |
|||
lateNonCriticalExtension |
Not present |
|||
} |
Condition |
Explanation |
RRM-InterFreq |
Used for RRM NB-IOT inter-frequency mobility scenarios |
– SystemInformationBlockType14-NB
The IE SystemInformationBlockType14-NB contains the AB parameters.
Table 8.1.4.3.3-5: SystemInformationBlockType14-NB
Derivation Path: 36.331 clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType14-NB-r13 ::= SEQUENCE { |
|||
ab-Param-r13 CHOICE { |
|||
ab-Common-r13 SEQUENCE { |
|||
ab-Category-r13 |
a |
AB applies to all UEs |
|
ab-BarringBitmap-r13 |
‘1111111111’B |
All UE classes 0-9 |
|
ab-BarringExceptionData-r13 |
Not present |
||
ab-BarringForSpecialAC-r13 |
‘11111’B |
All UE classes 11-15 |
|
} |
|||
} |
|||
lateNonCriticalExtension |
Not present |
||
} |
– SystemInformationBlockType15-NB
The IE SystemInformationBlockType15-NB contains the MBMS Service Area Identities (SAI) of the current and/ or neighbouring carrier frequencies.
Table 8.1.4.3.3-5A: SystemInformationBlockType15-NB
FFS
– SystemInformationBlockType16-NB
The IE SystemInformationBlockType16-NB contains information related to GPS time and Coordinated Universal Time (UTC). The UE may use the parameters provided in this system information block to obtain the UTC, the GPS and the local time.
Table 8.1.4.3.3-6: SystemInformationBlockType16-NB
FFS
– SystemInformationBlockType20-NB
The IE SystemInformationBlockType20-NB contains the information required to acquire the control information associated with transmission of MBMS using SC-PTM.
Table 8.1.4.3.3-7: SystemInformationBlockType20-NB
Derivation Path: 36.331 clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType20-NB-r14 ::= SEQUENCE { |
|||
npdcch-SC-MCCH-Config-r14 SEQUENCE { |
|||
npdcch-NumRepetitions-SC-MCCH-r14 |
r8 |
||
npdcch-StartSF-SC-MCCH-r14 |
v1dot5 |
||
npdcch-Offset-SC-MCCH-r14 |
zero |
||
} |
|||
sc-mcch-CarrierConfig-r14 CHOICE { |
|||
dl-CarrierIndex-r14 |
0 |
||
} |
|||
sc-mcch-RepetitionPeriod-r14 |
rf32 |
||
sc-mcch-Offset-r14 |
1 |
||
sc-mcch-ModificationPeriod-r14 |
rf512 |
||
sc-mcch-SchedulingInfo-r14 |
Not present |
||
lateNonCriticalExtension |
|||
} |
– SystemInformationBlockType22-NB
The IE SystemInformationBlockType22-NB contains radio resource configuration for paging and random access procedure on non-anchor carriers.
Table 8.1.4.3.3-8: SystemInformationBlockType22-NB
Derivation Path: 36.331 clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType22-NB-r14 ::= SEQUENCE { |
|||
dl-ConfigList-r14 SEQUENCE (SIZE (1.. maxNonAnchorCarriers-NB-r14)) OF DL-ConfigCommon-NB-r14 SEQUENCE { |
|||
DL-ConfigCommon-NB-r14[1] SEQUENCE { |
|||
dl-CarrierConfig-r14 |
DL-CarrierConfigCommon-NB-DEFAULT |
||
pcch-Config-r14 |
Not present |
||
wus-Config-r15 |
Not present |
||
} |
|||
} |
|||
ul-ConfigList-r14 SEQUENCE (SIZE (1.. maxNonAnchorCarriers-NB-r14)) OF UL-ConfigCommon-NB-r14 SEQUENCE { |
|||
UL-ConfigCommon-NB-r14[1] SEQUENCE { |
|||
ul-CarrierFreq-r14 |
See subclause 8.1.3.1 |
||
nprach-ParametersList-r14 |
Not present |
||
} |
|||
} |
|||
pagingWeightAnchor-r14 |
Not present |
||
nprach-ProbabilityAnchorList-r14 |
Not present |
||
lateNonCriticalExtension |
Not present |
||
} |
– SystemInformationBlockType23-NB
The IE SystemInformationBlockType23-NB contains radio resource configuration for NPRACH resources using preamble format 2 on non-anchor carriers.
Table 8.1.4.3.3-9: SystemInformationBlockType23-NB
Derivation Path: 36.331 clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType23-NB-r15 ::= SEQUENCE { |
|||
ul-ConfigList-v1530 SEQUENCE (SIZE (1.. maxNonAnchorCarriers-NB-r14)) OF UL-ConfigCommon-NB-v1530 SEQUENCE { |
1 entry |
||
nprach-ParametersListFmt2-r15 SEQUENCE (SIZE (1.. maxNPRACH-Resources-NB-r13)) OF NPRACH-ParametersFmt2-NB-r15 SEQUENCE { |
1 entry |
||
nprach-Parameters-r15 SEQUENCE { |
|||
nprach-Periodicity-r15 |
ms640 |
||
nprach-StartTime-r15 |
ms8 |
||
nprach-SubcarrierOffset-r15 |
n12 |
||
nprach-NumSubcarriers-r15 |
n36 |
||
nprach-SubcarrierMSG3-RangeStart-r15 |
oneThird |
||
npdcch-NumRepetitions-RA-r15 |
r16 |
||
npdcch-StartSF-CSS-RA-r15 |
v4 |
||
npdcch-Offset-RA-r15 |
zero |
||
nprach-NumCBRA-StartSubcarriers-r15 |
n24 |
||
npdcch-CarrierIndex-r15 |
Not present |
||
} |
|||
} |
|||
nprach-ParametersListFmt2EDT-r15 |
Not present |
||
} |
|||
ul-ConfigListMixed-v1530 |
Not present |
||
lateNonCriticalExtension |
Not present |
||
} |
– SystemInformationBlockType31-NB
The IE SystemInformationBlockType31-NB contains satellite assistance information for the serving cell.
Table 8.1.4.3.3-10: SystemInformationBlockType31-NB
Derivation Path: TS 36.331 [17], clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType31-NB-r17 ::= SEQUENCE { |
|||
servingSatelliteInfo-r17 SEQUENCE { |
NTN |
||
ephemerisInfo-r17 CHOICE { |
|||
stateVectors SEQUENCE { |
|||
positionX-r17 |
-11605245 |
||
positionY-r17 |
-30240830 |
||
positionZ-r17 |
-1854603 |
||
velocityVX-r17 |
44 |
||
velocityVY-r17 |
-31 |
||
velocityVZ-r17 |
195 |
||
} |
|||
} |
|||
nta-CommonParameters-17 SEQUENCE { |
|||
nta-Common-r17 |
7681821 |
||
nta-CommonDrift-r17 |
-37 |
||
nta-CommonDriftVariation-r17 |
0 |
||
} |
|||
ul-SyncValidityDuration-r17 |
s240 |
||
epochTime-r17 |
Not present |
||
k-Offset-r17 |
550 |
||
k-Mac-r17 |
Not present |
||
} |
|||
lateNonCriticalExtension |
Not present |
||
} |
Condition |
Explanation |
NTN |
Non-Terrestrial Networks test environment |
– SystemInformationBlockType32-NB
The IE SystemInformationBlockType32-NB contains satellite assistance information for prediction of discontinuous coverage.
Table 8.1.4.3.3-11: SystemInformationBlockType32-NB
Derivation Path: TS 36.331 [17], clause 6.7.3.1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType32-NB-r17 ::= SEQUENCE { |
|||
satelliteInfoList-r17 |
FFS |
||
lateNonCriticalExtension |
Not present |
||
} |