6.3 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 subclause apply to all Signalling test cases defined in TS 36.523-1 [18] unless otherwise specified, in addition to the common reference system configurations specified in subclause 4.4 of this specification.

For Signalling testing, MIMO (Multiple Input Multiple Output) is not applied for all cell configurations regardless of UE MIMO functionality. Only one SS Tx antenna is used.

One or two UE antennas are used for all signalling test cases. (*1)

(*1) Two UE antennas configuration is possible for UE diversity case.

6.3.1 Default parameter specific for simulated cells

Default parameters specific for simulated cells are specified in this subclause.

6.3.1.1 Intra-frequency neighbouring cell list in SIB4 for E-UTRA cells

Intra-frequency neighbouring cell list for signalling test cases is defined in table 6.3.1.1-1. This table is referred to in the default contents of IE intraFreqNeighbouringCellList in SystemInformationBlockType4 defined in table 4.4.3.3-3.

Table 6.3.1.1-1: Intra-frequency neighbouring cell lists for E-UTRA cells

cell ID	Test Frequency	intra-frequency neighbouring cell list
		number of entries	physCellId[n]			q-OffsetCell [n]
			1	2	3	1	2	3
Cell 1	f1	3	Cell 2	Cell 4	Cell 11	dB0	dB0	dB0
Cell 2	f1	3	Cell 1	Cell 4	Cell 11	dB0	dB0	dB0
Cell 4	f1	3	Cell 1	Cell 2	Cell 11	dB0	dB0	dB0
Cell 11	f1	3	Cell 1	Cell 2	Cell 4	dB0	dB0	dB0
Cell 3	f2	1	Cell 23	–	–	dB0	–	–
Cell 23	f2	1	Cell 3	–	–	dB0	–	–

NOTE: The intra-frequency E-UTRA neighbouring cell list for signalling NAS test cases when cells are on same PLMN is defined in table 6.3.2.3.1-1.

6.3.1.2 Inter-frequency carrier frequency list in SIB5 for E-UTRA cells

Inter-frequency E-UTRA carrier frequency list for signalling test cases is defined in table 6.3.1.2-1. This table is referred to in the default contents of IE interFreqCarrierFreqList in SystemInformationBlockType5 defined in table 4.4.3.3-4.

Table 6.3.1.2-1: Inter-frequency carrier frequency lists for E-UTRA cells

cell ID	Test Frequency	interFreqCarrierFreqList
		number of entries	dl-CarrierFreq[n]
			1	2	3
Cell 1 Cell 2 Cell 4 Cell 11	f1	3	f2	f3	f5
Cell 3 Cell 23	f2	3	f1	f3	f5
Cell 6	f3	3	f1	f2	f5
Cell 10	f5	3	f1	f2	f3
Note 1: The inter-frequency E-UTRA carrier frequency list for signalling NAS test cases when cells are on same PLMN is defined in table 6.3.2.3.2-1. Note 2: Depending on the Band under test, f3 may not be applicable. Note 3: In case of Test frequency f1, f2 and f3, dl-CarrierFreq f5 as part of inter-frequency list is applicable only in case of multi-band scenarios. Note 4: In case of Test frequency f5, dl-CarrierFreq f1 as part of inter-frequency list is applicable only in case of multi-band scenarios.

In the case of dual mode multi-cell network scenarios as defined in subclause 4.4.1.3, inter-frequency E-UTRA carrier frequency list for signalling test cases is defined in table 6.3.1.2-2.

Table 6.3.1.2-2: Inter-frequency carrier frequency lists for E-UTRA cells in dual mode scenario

cell ID	Test Frequency	interFreqCarrierFreqList
		number of entries	dl-CarrierFreq[n]
			1	2	3
Cell 1 Cell 2 Cell 4	f1	3	f2	f5	f6
Cell 3	f2	3	f1	f5	f6
Cell 10, Cell 30, Cell 31	f5	3	f1	f2	f6
Cell 28, Cell 29	f6	3	f1	f2	f5

6.3.1.3 UTRA carrier frequency list in SIB6 for E-UTRA cells

UTRA carrier frequency list for signalling test cases is defined in table 6.3.1.3-1. This table is referred to in the default contents of IE carrierFreqListUTRA-FDD and carrierFreqListUTRA-TDD in SystemInformationBlockType6 defined in table 4.4.3.3-5.

Table 6.3.1.3-1: UTRA carrier frequency lists for E-UTRA cells

interFreqCarrierFreqList
number of entries	carrierFreq[n]
	1	2	3
3	f8	f9	f10
Note: Band VI has two entries.

Table 6.3.1.3-2: Mapping of UTRA cell with TS 34.108 [5]

UTRA cell	Frequency	UTRA cell in TS 34.108, clause 6.1	UTRA frequency in TS 34.108
Cell 5	f8	Cell 1	High (Note 2)
Cell 7	f8	Cell 2	High (Note 2)
Cell 8	f9	Cell 4	Mid (Note 2)
Cell 9	f10	Cell 7	Low
Note 1: The following simultaneous co-existences in the test are not allowed: – cells on f1 (eUTRA cell 1, cell 2, cell 4, cell 11) and f9 (UTRA cell 8); – cells on f2 (eUTRA cell 3, cell 12, cell 23) and f8 (UTRA cell 5, cell 7); – cells on f3 (eUTRA cell 6, Cell 13) and f10 (UTRA cell 9). Note 2: On UTRA Band VI, the Low range test frequency is applied to f9 for Cell 8, and f8 for Cell 5 and Cell 7. Note 3: The combinations of the referred TS 34.108 UTRA Cell index and frequency in this table override that specified in TS 34.108.

6.3.1.4 GERAN carrier frequency group list in SIB7 for E-UTRA cells

GERAN carrier frequency group list for signalling test cases is defined in table 6.3.1.4-1. This table is referred to in the default contents of IE carrierFreqsInfoList in SystemInformationBlockType7 defined in table 4.4.3.3-6.

Table 6.3.1.4-1: GERAN carrier frequency group list for E-UTRA cells

carrierFreqsInfoList
number of entries	index (n)	carrierFreqs[n]
		startingARFCN[n]	explicitListOfARFCNs[n]
			number of entries	ARFCN-ValueGERAN
1	1	f11	2	f12, f13

Table 6.3.1.4-2: Mapping of GERAN cells with TS 51.010-1 [25]

GERAN cell	Frequency	GERAN cell in TS 51.010-1, clause 40
Cell 24	f11	Cell A
Cell 25	f12	Cell D
Cell 26	f13	Cell B

NOTE 2: Unless otherwise stated, GERAN cells 24/25/26 take the default values of GERAN cells A/B/D as defined in TS 51.010 clause 40.

6.3.1.5 CDMA2000 HRPD carrier frequency list in SIB8 for E-UTRA cells

CDMA2000 HRPD carrier frequency list for signalling test cases is defined in table 6.3.1.5-1. This table is referred to in the default contents of IE cellReselectionParametersHRPD in SystemInformationBlockTyp8 defined in table 4.4.3.3-7.

Table 6.3.1.5-1: CDMA2000 HRPD carrier frequency list for E-UTRA cells

neighCellsPerFreqList
number of entries	index (n)	arfcn[n]	physCellIdList[n]
			number of entries	index	PhysCellIdCDMA2000
3	1	f14	2	1	Cell 15
				2	Cell 16
	2	f15	1	1	Cell 17
	3	f16	1	1	Cell 18

6.3.1.6 CDMA2000 1xRTT carrier frequency list in SIB8 for E-UTRA cells

CDMA2000 1xRTT carrier frequency list for signalling test cases is defined in table 6.3.1.6-1. This table is referred to in the default contents of IE cellReselectionParameters1XRTT in SystemInformationBlockTyp8 defined in table 4.4.3.3-7.

Table 6.3.1.6-1: CDMA2000 1xRTT carrier frequency list for E-UTRA cells

neighCellsPerFreqList
number of entries	index (n)	arfcn[n]	physCellIdList[n]
			number of entries	index	PhysCellIdCDMA2000
3	1	f17	2	1	Cell 19
				2	Cell 20
	2	f18	1	1	Cell 21
	3	f19	1	1	Cell 22

6.3.1.7 E-UTRA carrier frequency list in SIB19 for UTRA cells

E-UTRA carrier frequency list for signalling test cases is defined in table 6.3.1.7-1. This table is referred to in the default contents of IE eutra-FrequencyAndPriorityInfoList in System Information Block type 19 defined in table 4.4.4.1-1.

Table 6.3.1.7-1: E-UTRA carrier frequency list for UTRA cells

eutra-FrequencyAndPriorityInfoList
number of entries	earfcn[n]
	1	2	3	4	–
4	f1	f2	f3	f4	–
Note: Depending on the Band under test, f2, f3 and f4 may not be applicable.

6.3.1.8 NR carrier frequency list in SIB24 for E-UTRA cells

NR carrier frequency list for signalling test cases is defined in table 6.3.1.8-1. This table is referred to in the default contents of IE carrierFreqListNR-r15 in System Information Block type 24 defined in Table 4.4.3.3-20.

Table 6.3.1.8-1: NR carrier frequency list for E-UTRA cells

carrierFreqListNR-r15
number of entries	nr-arfcn[n]
	1	2	3	4	–
4	NRf1	NRf2	NRf3	NRf4	–
Note 1: Depending on the NR Band under test, NRf2, NRf3 and NRf4 may not be applicable. Note 2: NRf1, NRf2, NRf3 and NRf4 are defined in TS 38.508-1[67] clause 4.4.2 and 6.2.3.

6.3.2 Default configurations for NAS test cases

The default configurations specified in this subclause apply only to NAS test cases. They apply to all NAS test cases unless otherwise specified.

6.3.2.1 Simulated network scenarios for NAS test cases

Simulated network scenarios for NAS test cases to be tested are specified in the pre-test conditions of each individual test case.

NOTE: 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 Table 6.1-1 for such information.

Any combination is allowed with the following restrictions:

– Cell E should not be used if Cell G or Cell H is used, otherwise two different PLMNs will be operated on the same frequency

– a maximum 3 cells on the same frequency can be used, i.e. only 3 cells out of cells A, B, C, D and M may be used simultaneously in each individual test case when cells in the test case are in different PLMNs (refer to Table 6.3.2.2-3).

6.3.2.2 Simulated NAS cells

Simulated NAS cells and default parameters are specified in table 6.3.2.2-1.

Unless otherwise specified, the default parameters specified in section 4 also apply to all NAS cells.

Table 6.3.2.2-1: Default parameters for simulated NAS cells

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
Cell A	TAI-1	(Note 3)		1	TAI-1	32769	1	Arbitrarily selected according to TS 23.003 subclause 2.8 [2].
Cell B	TAI-2	(Note 3)		2	TAI-2	32770	1
Cell C	TAI-3	(Note 3)		3	TAI-3	32771	1
Cell D	TAI-4	(Note 3)		4	TAI-4	32772	1
Cell E	TAI-12	002	101	3	TAI-12	32777	1
Cell F
Cell G	TAI-7	(Note 4)	02	1	TAI-7	32775	1
Cell H	TAI-8	(Note 4)	02	2	TAI-8	32776	1
Cell I	TAI-9	002	101	1	TAI-9	32777	1
Cell J	TAI-10	003	101	1	TAI-10	32778	1
Cell K	TAI-9	002	101	1	TAI-9	32777	1
Cell L	TAI-11	002	101	2	TAI-11	32779	1
Cell M	TAI-1	(Note 3)		1	TAI-1	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). Note 4: Set to the same Mobile Country Code stored in EFIMSI on the test USIM card (subclause 4.9.3). Note 5: Cell A is a serving cell and the other cells are suitable neighbour cells. The definitions are specified in subclause 6.2.2.1.

Table 6.3.2.2-2: Default cell identifiers for simulated NAS cells when cells are in same PLMN

NAS cell ID	Frequency	E-UTRAN Cell Identifier		Physical layer cell identity	rootSequenceIndex FDD	rootSequenceIndex TDD
		eNB Identifier	Cell Identity
Cell A	f1	‘0000 0000 0000 0001 0001’B	‘0000 0001’B	1	22	0
Cell B	f1	‘0000 0000 0000 0001 0001’B	‘0000 0010’B	2	86	8
Cell C	f2	‘0000 0000 0000 0001 0010’B	‘0000 0011’B	3	22	0
Cell D	f1	‘0000 0000 0000 0001 0001’B	‘0000 0100’B	4	150	16
Cell E	NA	NA	NA	NA	NA	NA
Cell F	NA	NA	NA	NA	NA	NA
Cell G	NA	NA	NA	NA	NA	NA
Cell H	NA	NA	NA	NA	NA	NA
Cell I	NA	NA	NA	NA	NA	NA
Cell J	NA	NA	NA	NA	NA	NA
Cell M	f2	‘0000 0000 0000 0010 0001’B	‘0001 0001’B	17	86	8

Table 6.3.2.2-3: Default cell identifiers for simulated NAS cells when cells are in different PLMNs

NAS cell ID	PLMN	Frequency	E-UTRAN Cell Identifier		Physical layer cell identity	rootSequenceIndex FDD	rootSequenceIndex TDD
			eNB Identifier	Cell Identity
Cell A	MCC/MNC= MCC/MNC in USIM	f1	‘0000 0000 0000 0010 0001’B	‘0000 0001’B	1	22	0
Cell B	MCC/MNC= MCC/MNC in USIM	f1	‘0000 0000 0000 0010 0001’B	‘0000 0010’B	2	86	8
Cell C	MCC/MNC= MCC/MNC in USIM	f1	‘0000 0000 0000 0010 0001’B	‘0000 0011’B	3	150	16
Cell D	MCC/MNC= MCC/MNC in USIM	f1	‘0000 0000 0000 0010 0001’B	‘0000 0100’B	4	214	24
Cell E	MCC=002 MNC=101	f2	‘0000 0000 0000 0011 0101’B	‘0001 0111’B	23	22	0
Cell F	NA	NA	NA	NA	NA	NA	NA
Cell G	MCC = MCC in USIM MNC=02	f2	‘0000 0000 0000 0010 0010’B	‘0000 1011’B	11	86	8
Cell H	MCC= MCC in USIM MNC=02	f2	‘0000 0000 0000 0010 0010’B	‘0000 1100’B	12	150	16
Cell I	MCC=002 MNC=101	f3 (Note 1)	‘0000 0000 0000 0010 0011’B	‘0000 1101’B	13	22	0
Cell J	MCC=003 MNC=101	f4 (Note 1)	‘0000 0000 0000 0010 0100’B	‘0000 1110’B	14	22	0
Cell K	MCC=002 MNC=101	f3 (Note 1)	‘0000 0000 0000 0010 0011’B	‘0000 1111’B	15	86	8
Cell L	MCC=002 MNC=101	f3 (Note 1)	‘0000 0000 0000 0010 0011’B	‘0001 0000’B	16	150	16
Cell M	MCC/MNC= MCC/MNC in USIM	f1	‘0000 0000 0000 0010 0001’B	‘0001 0001’B	17	278	32
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.

6.3.2.3 Broadcast system information

6.3.2.3.1 Intra-frequency neighbouring cell list in SIB4 for E-UTRA NAS cells

Intra-frequency neighbouring cell list of the same PLMN for the NAS signalling test is defined in table 6.3.2.3.1-1 when SIB4 to be broadcast.

Table 6.3.2.3.1-1: Intra-freq. lists in SIB4 for NAS test cases (same PLMN)

NAS cell ID	Test Frequency	Intra-frequency neighbouring cell list
		number of entries	physCellId[n]
			1	2
Cell A	f1	2	Cell B	Cell D
Cell B	f1	2	Cell A	Cell D
Cell D	f1	2	Cell A	Cell B
Cell C	f2	1	Cell M	N/A
Cell M	f2	1	Cell C	N/A

6.3.2.3.2 Inter-frequency carrier frequency list in SIB5 for E-UTRA NAS cells

Inter-frequency neighbouring carrier and cell lists for NAS signalling test cases are defined in table 6.3.2.3.2-1 for same PLMN and table 6.3.2.3.2-2 for different PLMN.

Table 6.3.2.3.2-1: Inter-freq. lists in SIB5 for NAS test cases (same PLMN)

NAS cell ID	Test Frequency	interFreqCarrierFreqList
		number of entries	dl-CarrierFreq[n]
			1	2
Cell A Cell B Cell D	f1	1	f2	NA
Cell C Cell M	f2	1	f1	NA
NOTE: Operating on Band 13, SIB5 is not broadcast.

Table 6.3.2.3.2-2: Inter-freq. lists in SIB5 for NAS test cases (different PLMN)

NAS cell ID	Test Frequency	interFreqCarrierFreqList			Condition
		number of entries	dl-CarrierFreq[n]
			1	2
Cell A Cell B Cell C Cell D Cell M	f1	0	NA	NA
Cell G Cell H	f2	0	NA	NA
Cell I Cell K Cell L	f3	0	NA	NA	E-NOT-CONF
		1	f2		E-CONF
Cell J	f4	0	NA	NA
Cell E	f2	1	f3	NA

Condition	Explanation
E-NOT-CONF	cell E is not configured in the test
E-CONF	cell E is configured in the test

6.3.3 Cell configurations

For the purpose of test not involving Carrier Aggregation, three types of SS cell configurations are defined, full (Active) cell configuration, broadcast only cell configuration and minimum uplink cell configuration.

The abovementioned configurations can also be used in Carrier Aggregation test cases, either for PCells or SCells. However another configuration, the virtual cell configuration, can additionally be used for an SCell that is not active.

6.3.3.1 Full cell configuration

Full cell configuration is also called active cell configuration. The cell configuration, in minimum, has all defined DL and UL physical channels configured, i.e.

in DL: PBCH, PCFICH, PDCCH, PDSCH, PHICH,

in UL: PRACH, PUCCH, PUSCH.

The DL and UL Reference and synchronization (both primary and secondary) signals are also configured.

6.3.3.2 Minimum uplink cell configuration

In this cell configuration,

in DL: physical channels capable of transmission, i.e. PBCH, PCFICH, PDCCH, PDSCH are configured;

DL physical reference and synchronization (both primary and secondary) signals are also configured.

In UL: PRACH is configured. SS shall report any detection of PRACH preambles, in order to assign test verdicts. Decoding the preambles is not required.

6.3.3.3 Broadcast only cell configuration

In this cell configuration,

in DL: physical channels capable of transmission, i.e. PBCH, PCFICH, PDCCH, PDSCH are configured;

DL physical reference and synchronization (both primary and secondary) signals are also configured.

in UL: no physical resources are configured, neither channels, nor signals.

6.3.3.3A Virtual cell configuration

In this cell configuration,

in DL: no physical resources are configured, neither channels, nor signals;

in UL: no physical resources are configured, neither channels, nor signals.

6.3.3.4 Application of different cell configurations

By default, the cells specified in 36.523-1 are defined with the full cell configuration, unless it is explicitly specified as either the broadcast only, minimum uplink, or virtual cell configuration. The full cell configuration is suitable for UE to start camping, establish RRC connection or hand over from another active cell.

The broadcast only cells identified as ‘DL only’ can be applied in some RRC measurement test cases to those neighbour cells which UE shall not camp on during the test case execution.

The capability of a minimum uplink cell is much weaker than a full cell, but stronger than a broadcast only cell in UL. This cell configuration identified as ‘min UL’ can be applied in the idle mode test cases to those neighbour cells which a conformant UE shall not camp on during the test case execution.

The virtual cell configuration can only be used in Carrier Aggregation test cases as an SCell which is not active, i.e. the UE has it configured via RRC signalling but does not need to send or receive anything in this SCell.

If a cell configuration is specified in a test case it shall remain unchanged throughout the test case specification. In addition, there shall not be any requirement in the test specification or test implementation for a cell reconfiguration from one of the above configurations to the other.

For the UE conformance test, the broadcast only cell configuration can be replaced and implemented with the minimum uplink or full cell configurations. The minimum uplink cell configuration can also be implemented with the full cell configuration. The replacements in the implementation have no impact on the test purposes and the test requirements. The implementation guidelines are referred to 36.523-3.

6.3.4 SCell configurations

For the purpose of System Simulator resource management for Carrier Aggregation testing the following types of SCell configurations are defined:

– Active SCell: A cell that becomes an SCell at any point of time during the test case and which, while being an SCell, is activated.

– Inactive SCell: A cell that becomes an SCell at any point of time during the test case, but is never activated while being an SCell.

SCell activation is defined as sending an Activation/Deactivation MAC Control Element (ref. 36.321 cl. 6.1.3.8) to the UE to activate the SCell.

The SCell type does not depend on what the cell is used for in the test case while not being an SCell, and does not directly relate to the cell type specified in section 6.3.3. In particular an Inactive SCell can still be used as full cell or broadcast only cell (e.g. for measurements to be performed on such a cell), and may be used for UE dedicated traffic while not acting as an SCell.

Also note that an Active SCell will not become an Inactive SCell if the SCell is deactivated via Activation/Deactivation MAC Control Element or after the sCellDeactivationTimer timer expires.