7 Test environment for RRM tests

36.5083GPPCommon test environments for User Equipment (UE) conformance testingEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Release 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

This section contains all the exceptions of the common test parameters specified in clause 4 for specific needs of test cases defined in TS 36.521-3 [34], TS 34.121-1 [50] and TS 34.122 [51]. Exceptions specified in clause 7 overwrite the parameter settings of clause 4; exceptions defined within the test cases overwrite parameter settings of clause 4 and 7.

This clause describes UE test states which can be used in the initial condition for TS 36.521-3 [34], TS 34.121-1 [50] and TS 34.122 [51].

7.1 Requirements of test equipment

<void>

7.2 RRM Reference system configurations

7.2.1 Common parameters for simulated E-UTRA cells

7.2.1.1 Combinations of system information blocks

<void>

7.2.1.2 Scheduling of system information blocks

<void>

7.2.1.3 Common contents of system information messages

– SystemInformationBlockType2

As defined in Table 4.4.3.3-1 with the following exceptions:

Table 7.2.1.3-1: SystemInformationBlockType2 exceptions

Derivation Path: Clause 4.4.3.3, Table 4.4.3.3-1 SystemInformationBlockType2
Information Element	Value/remark	Comment	Condition
mbsfn-SubframeConfigList SEQUENCE	Not Present	MBSFN not applicable for eMTC RRM Test cases	CEmodeA, CEmodeB
mbsfn-SubframeConfigList ::= SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {			FDD
radioframeAllocationPeriod	n1	Every radio frame is with MBSFN subframe
radioframeAllocationOffset	0
subframeAllocation CHOICE {
oneFrame	‘111111’B	Subframe 1, 2, 3, 6, 7, 8 is used for MBSFN
}
}

Condition	Explanation
FDD	FDD cell environment
CEmodeA	CE mode A test environment
CEmodeB	CE mode B test environment

– SystemInformationBlockType3

As defined in Table 4.4.3.3-2 with the following exceptions:

Table 7.2.1.3-2: SystemInformationBlockType3 exceptions

Derivation Path: Clause 4.4.3.3, Table 4.4.3.3-2 SystemInformationBlockType3
Information Element	Value/remark	Comment	Condition
neighCellConfig	‘10’B (The MBSFN subframe allocations of all neighbour cells are identical to or subsets of that in the serving cell)		FDD with E-UTRA FDD neighbour cell
	‘01’B (No MBSFN sub frames are present in all neighbor cells)		CEmodeA, CEmodeB

Condition	Explanation
FDD with E-UTRA FDD neighbour cell	FDD cell environment with a E-UTRA FDD neighbour cell
CEmodeA	CE mode A test environment
CEmodeB	CE mode B test environment

– SystemInformationBlockType5

As defined in Table 4.4.3.3-3 with the following exceptions:

Table 7.2.1.3-3: SystemInformationBlockType5 exceptions

Derivation Path: Clause 4.4.3.3, Table 4.4.3.3-4 SystemInformationBlockType5
Information Element	Value/remark	Comment	Condition
neighCellConfig[n]	‘10’B (The MBSFN subframe allocations of all neighbour cells are identical to or subsets of that in the serving cell)		FDD with E-UTRA FDD neighbour cell
	‘11’B (Different UL/DL allocation in neighbouring cells for TDD compared to the serving cell)		FDD with E-UTRA TDD neighbour cell, TDD with E-UTRA FDD neighbour cell
	‘01’B (No MBSFN sub frames are present in all neighbor cells)		CEmodeA, CEmodeB

Condition	Explanation
FDD with E-UTRA FDD neighbour cell	FDD cell environment with a E-UTRA FDD neighbour cell
FDD with E-UTRA TDD neighbour cell	FDD cell environment with a E-UTRA TDD neighbour cell
TDD with E-UTRA FDD neighbour cell	TDD cell environment with a E-UTRA FDD neighbour cell
CEmodeA	CE mode A test environment
CEmodeB	CE mode B test environment

– SystemInformationBlockType7

As defined in Table 4.4.3.3-6 with the following exceptions:

Table 7.2.1.3-4: SystemInformationBlockType7 exceptions

Derivation Path: Clause 4.4.3.3, Table 4.4.3.3-6 SystemInformationBlockType7
Information Element	Value/remark	Comment	Condition
commonInfo SEQUENCE {
p-MaxGERAN	33 (33 dBm)		GSM 400 & GSM 900 & GSM 850 & GSM 700
	30 (30 dBm)		DCS 1800 & PCS 1900
}

7.2.2 Common parameters for simulated GERAN cells

7.2.2.1 Mapping of GERAN cells

Unless otherwise stated, GERAN cells take the default values defined in Table 7.2.2.1-1.

Table 7.2.2.1-1: 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

7.2A Generic RRM procedures

7.2A.1 UE RRM test states

Table 7.2A.1-1: The E-UTRAN UE states

		RRC	ECM	EMM	ESM	UE Test Mode
State 2A-RF	Registered, Idle Mode, UE Test Mode Activated	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1
State 2A-RF-CE	Registered, Idle Mode, Cell supporting BL/CE UE, UE Test Mode Activated	Refer to Table 5.2A.1-1AA	Refer to Table 5.2A.1-1AA	Refer to Table 5.2A.1-1AA	Refer to Table 5.2A.1-1AA	Refer to Table 5.2A.1-1AA
State 3A-RF	Generic Default RB Established, UE Test Mode Activated	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1
State 3A-RF-CE	Generic Default RB Established, Cell supporting BL/CE UE, UE Test Mode Activated	Refer to Table 5.2A.2AA	Refer to Table 5.2A.2AA	Refer to Table 5.2A.2AA	Refer to Table 5.2A.2AA	Refer to Table 5.2A.2AA
State 3A-RF-DC1	DC MCG/SCG Dedicated RB established, UE Test Mode Activated	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1
State 3A-RF-DC2	DC Split Default RB established, UE Test Mode Activated	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1	Refer to Table 5.2A.1-1
State 3B-RF	Generic Default RB Established, UE Test Mode Activated, pre-registered on HRPD	RRC_CONNECTED 1 data radio bearer configured	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active

7.2A.2 UE Registration, UE Test Mode Activated (State 2A-RF)

As described in clause 5.2A.1A.

7.2A.2A UE Registration, UE Test Mode Activated in cell supporting BL/CE UE (State 2A-RF-CE)

As described in clause 5.2A.1AA.

7.2A.3 Generic Default Radio Bearer Establishment, UE Test Mode Activated (State 3A-RF)

As described in clause 5.2A.2.

7.2A.3A DC MCG/SCG Dedicated RB established, UE Test Mode Activated (State 3A-RF-DC1)

As described in clause 5.2A.2A.

7.2A.3AA Generic Default Radio Bearer Establishment, UE Test Mode Activated in cell supporting BL/CE UE (State 3A-RF-CE)

As described in clause 5.2A.2AA.

7.2A.3B DC Split Default RB established, UE Test Mode Activated (State 3A-RF-DC2)

As described in clause 5.2A.2B.

7.2A.3C Generic Default Radio Bearer Establishment, UE Test Mode Activated, V2X Setup (State 3A-RF-V2X)

As described in clause 5.2A.2C.

7.2A.4 Generic Default Radio Bearer Establishment, UE Test Mode Activated, pre-registration on HRPD (State 3B-RF)

Editor’s note: This section is incomplete. The following aspects are either missing or not yet determined:
Other than UATI Request message and UATI Assignment message are FFS

7.2A.4.1 Initial conditions

System Simulator:

– Cell 1

– Cell 1 is transmitting SystemInformationBlockType8

User Equipment:

– The Test USIM shall be inserted.

7.2A.4.2 Definition of system information messages

As described in clause 4.5.2B.2.

7.2A.4.3 Procedure

Table 7.2A.4.3-1: UE registration with default EPS bearer establishment, test mode activation and HRPD pre-registration procedures (state 1 to state 3B-RF)

Step	Procedure	Message Sequence
		U – S	Message
1 to 18	Steps 1 to 18 as specified in the procedure in clause 5.2A.1A.3 take place.	–	–
19 to 36	Same procedure for steps 17 to 30D as specified in the procedure in clause 4.5.2B.3.

7.2A.4.4 Specific message contents

As described in clauses 4.5.2B.4 and 7.2A.2.

7.2A.5 Procedure to configure SCC

As described in clause 5.2A.4.

7.2A.6 Exceptions for feICIC tests

As described in clause 5.2A.5.

7.2B Other generic RRM procedures

7.2B.1 Tracking area updating procedure

The procedure is defined in table 7.2B.1-1.

Table 7.2B.1-1: Tracking area updating procedure

Step	Procedure	Message Sequence
		U – S	Message
1	The SS transmits system information on the cell specified in the test case.	<–	RRC: SYSTEM INFORMATION (BCCH, BCCH-BR) Note 5.
–	EXCEPTION: If all EPS bearer contexts are inactive in UE, for Rel-8 and Rel-9, steps 2 to 8a are optional and depend on UE implementation. If all EPS bearer contexts are inactive in UE, a Rel-10 or higher UE directly starts attach procedure from step 9a.	–	–
2	The UE transmits an RRCConnectionRequest message on the cell specified in the test case.	–>	RRC: RRCConnectionRequest
3	The SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
4	The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST
–	EXCEPTION: If all EPS bearer contexts are marked as inactive in the EPS bearer context status IE included in the TRACKING AREA UPDATE REQUEST message then, events described in steps 5a to 26a. Otherwise, events described in steps 5 to 7.	–	–
5	The SS responds with TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT
6	The UE transmits a TRACKING AREA UPDATE COMPLETE	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE
7	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease
5a	The SS responds with TRACKING AREA UPDATE REJECT message with cause #40 (No EPS bearer context activated) to force attach the UE.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE REJECT
6a	EXCEPTION: Step 7a describes the behaviour that depends on UE behaviour (Note 3).	–	–
7a	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease
–	EXCEPTION: Step 8a describes a behaviour which depends on the UE capability	–	–
8a	IF NOT pc_Auto_PDN_Connectivity, the user initiates an attach by MMI or by AT command (NOTE 4).	–	–
9a to 27a	Steps 2 to 20 of the generic UE Registration procedure (5.2A.1A.3) take place to complete the Attach procedure	–	–
NOTE 1: The periodic tracking area updating timer T3412 is deactivated by default during the attach procedure (TS 36.508 clause 4.7.2). NOTE 2: The SS does not initiate authentication and NAS SECURITY MODE COMMAND are not performed (reuse of keys allocated during the attach procedure). NOTE 3: The SS waits for 1.5 second to receive the Attach Request on the existing RRC Connection. In case Attach Request is not received within 1.5 second, existing RRC Connection is released. NOTE 4: The request is assumed to be triggered by AT command AT+CGDCONT=1,"IP" followed by AT+CGACT=1. NOTE 5: For BL UE testing and for non-BL UE enhanced coverage testing the SS shall broadcast SystemInformation-BR-r13, SystemInformationBlockType1-BR-r13 and other relevant system information blocks as required by the specified combinations of system information blocks specified for the test case on BCCH-BR. For non-BL UE normal coverage testing the SS may exclude broadcasting of system information on BCCH-BR.

Specific message contents

Table 7.2B.1-1a: MasterInformationBlock (Step 1 and following steps)

Derivation Path: 36.508 Table 4.4.3.2-1 using condition CEmodeB if the test case specifically tests CE mode B else use condition CEmodeA.

Table 7.2B.1-1a1: SystemInformation-BR-r13 (Step 1 and following steps)

Derivation Path: 36.508 Table 4.4.3.2-2A.

Table 7.2B.1-1a2: SystemInformationBlockType1-BR-r13 (Step 1 and following steps)

Derivation Path: 36.508 Table 4.4.3.2-3A.

Table 7.2B.1-2: TRACKING AREA UPDATE ACCEPT (Step 5)

Derivation Path: 36.508 Table 4.7.2-24
Information Element	Value/remark	Comment	Condition
EPS network feature support	‘0000 0000’B	IMS voice over PS session in S1 mode not supported
Additional update result	Not present

7.3 Default RRC message and information elements contents

7.3.1 Contents of RRC messages

FFS.

7.3.2 Radio resource control information elements

Editor’s note: Unless otherwise stated in the test parameters or messages exceptions in the respective test cases in TS 36.521-3 [34], PRACH configuration index and exceptional message as specified in Table 7.3.2-1 is used.

As defined in clause 4.6.3 with the following exceptions:

Table 7.3.2-1: PRACH-Config-DEFAULT

Derivation Path: Clause 4.6.3 Table 4.6.3-7
Information Element	Value/remark	Comment	Condition
PRACH-Config-DEFAULT ::= SEQUENCE {
prach-ConfigIndex	3		TDD
}

Condition	Explanation
TDD	TDD cell environment

Table 7.3.2-2: RadioResourceConfigCommonSCell-r10-DEFAULT

Derivation Path: Clause 4.6.3 Table 4.6.3-13A
Information Element	Value/remark	Comment	Condition
RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {
mbsfn-SubframeConfigList-r10 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {			FDD
radioframeAllocationPeriod	n1	Every radio frame is with MBSFN subframe
radioframeAllocationOffset	0
subframeAllocation CHOICE {
oneFrame	‘111111’B	Subframe 1, 2, 3, 6, 7, 8 is used for MBSFN
}
}
ul-Configuration-r10	Not Present
}

Condition	Explanation
FDD	FDD cell environment

Table 7.3.2-3: PhysicalConfigDedicatedSCell-r10-DEFAULT

Derivation Path: Clause 4.6.3 Table 4.6.3-6A
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicatedSCell-r10 ::= SEQUENCE {
ul-Configuration-r10	Not Present
}

7.3.3 Measurement information elements

As defined in clause 4.6.6 with the following exceptions:

Table 7.3.3-0: MeasDS-Config-DEFAULT

Derivation Path: clause 4.6.6 Table 4.6.6-1B
Information Element	Value/remark	Comment	Condition
MeasDS-Config-DEFAULT ::= CHOICE {
release	NULL
setup SEQUENCE {
dmtc-PeriodOffset-r12 CHOICE {
ms40-r12	10		LAA_MeasProc
ms40-r12	0		LAA_MeasPerf
}
}
}

Condition	Explanation
LAA_MeasProc	Used for LAA measurements procedures test cases
LAA_MeasPerf	Used for LAA measurement performance test cases

Table 7.3.3-1: MeasObjectEUTRA-GENERIC (Freq)

Derivation Path: Clause 4.6.6, Table 4.6.6-2
Information Element	Value/remark	Comment	Condition
neighCellConfig	10’B (The MBSFN subframe allocations of all neighbour cells are identical to or subsets of that in the serving cell)		FDD with E-UTRA FDD neighbour cell
	‘11’B (Different UL/DL allocation in neighbouring cells for TDD compared to the serving cell)		FDD with E-UTRA TDD neighbour cell, TDD with E-UTRA FDD neighbour cell
	‘01’B (No MBSFN sub frames are present in all neighbor cells)		CEmodeA, CEmodeB

Condition	Explanation
FDD with E-UTRA FDD neighbour cell	FDD cell environment with a E-UTRA FDD neighbour cell
FDD with E-UTRA TDD neighbour cell	FDD cell environment with a E-UTRA TDD neighbour cell
TDD with E-UTRA FDD neighbour cell	TDD cell environment with a E-UTRA FDD neighbour cell
CEmodeA	CE mode A test environment
CEmodeB	CE mode B test environment

7.3A Default UTRA message and information element contents

7.3A.1 UTRA RRC messages

As defined in 4.7B with the following exceptions:

Contents of RRC CONNECTION SETUP message: UM

Information Element	Value/remark	Version	Index
– System specific capability update requirement list	1 entry		RCSU-019
– System specific capability update requirement	GSM		RCSU-019a
CHOICE specification mode	Complete specification	Rel-5	RCSU-020
– Complete specification		Rel-5	RCSU-021

7.4 Default NAS message and information elements contents

7.5 Reference radio bearer configurations

7.5.1 SRB and DRB parameters

7.5.1.1 MAC configurations

As defined in clause 4.8.2.1.5 with the following exceptions:

Table 7.5.1.1-1: MAC-MainConfig-RBC

Derivation Path: Clause 4.8.2.1.5 Table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
mac-MainConfig-v1020SEQUENCE {			SCell_AddMod
sCellDeactivationTimer-r10	Not present
extendedBSR-Sizes-r10	Not Present
extendedPHR-r10	Not Present
extendedPHR-r10	Setup		UL CA
}
}

Condition	Explanation
SCell_AddMod	Addition or modification of Scell
UL CA	This condition is used for UL CA.