5 Test environment for RF test

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-1 [21]. Exceptions specified in clause 5 overwrite the parameter settings of clause 4; exceptions defined within the test cases overwrite parameter settings of clause 4 and 5.

5.1 Requirements of test equipment

No common RF test environment requirements are specified in addition to the common requirements described in clause 4.2. Specific RF requirements are indicated within the test cases defined in TS 36.521-1 [21].

5.2 RF Reference system configurations

5.2.1 Common parameters for simulated E-UTRA cells

For BL/CE testing the same content of system information blocks SIB2, SIB3, SIB5 and SIB13 are used for broadcasting on BCCH and/or BCCH-BR.

5.2.1.1 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:

– E-UTRA FDD single cell scenario

– E-UTRA TDD single cell scenario

– E-UTRA FDD intra-frequency multi cell scenario

– E-UTRA TDD intra-frequency multi cell scenario

Combination 2 applies to the following test case scenarios:

– E-UTRA FDD + MBMS

– E-UTRA TDD + MBMS

Combination 3 applies to the following test case scenarios:

– E-UTRA FDD intra-band carrier aggregation component carriers cell scenario

– E-UTRA FDD inter-band carrier aggregation component carriers cell scenario

– E-UTRA TDD intra-band carrier aggregation component carriers cell scenario

The combinations of system information blocks for test cases in TS 36.521-1 [21] is defined in table 5.2-1.1-1.

Table 5.2.1.1-1: Combinations of system information blocks

System information block type

Combination No.

SIB2

SIB3

SIB4

SIB5

SIB6

SIB7

SIB8

SIB9

SIB10

SIB11

SIB12

SIB13

5.2.1.2 Scheduling of system information blocks

The scheduling configurations for combinations of system information blocks are defined in the following tables. SIB1 will be transmitted during subframes#5 which SFN mod 2 = 0, and SIB2+SIB3 will be transmitted during subframes#5 which SFN mod 2 = 1 with 8 radio frames periodicity. SIB5 will be transmitted during subframes#5 which SFN mod 2 = 1 with 64 radio frames periodicity

Table 5.2.1.2-1: Scheduling for combination 1

Scheduling Information No.

Periodicity

[radio frames]

Mapping of system information blocks

SIB2, SIB3

Table 5.2.1.2-2: Scheduling for combination 2

Scheduling Information No.

Periodicity

[radio frames]

Mapping of system information blocks

SIB2, SIB3

SIB13

Table 5.2.1.2-3: Scheduling for combination 3

Scheduling Information No.

Periodicity

[radio frames]

Mapping of system information blocks

SIB2, SIB3

SIB5

5.2.1.3 Common contents of system information messages

– MasterInformationBlock

As defined in Table 4.4.3.2-1 without exceptions.

– SystemInformation

As defined in Table 5.2.1.3-1As defined in Table without exceptions.

Table 5.2.1.3-1: SystemInformation

Derivation Path: Clause 4.4.3.2 Table 4.4.3.2-2
Information Element	Value/remark	Comment	Condition
SystemInformation ::= SEQUENCE {
criticalExtensions CHOICE {
systemInformation-r8 SEQUENCE {
sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB)) OF CHOICE {}	See subclause 5.2.1.1 and 5.2.1.2
criticalExtensionsFuture SEQUENCE {}	Not present
}
}
}

– SystemInformationBlockType1

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

Table 5.2.1.3-2: SystemInformationBlockType1 exceptions

Derivation Path: Clause 4.4.3.2 Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
si-WindowLength	ms40
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {			RF_INTF_MITIG
hsdn-Cell-r15	Not present
cellSelectionInfoCE-v1530	Not present
crs-IntfMitigConfig-r15 CHOICE {	Not present
crs-IntfMitigNumPRBs	n6
}
cellBarred-CRS-r15	notBarred
plmn-IdentityList-v1530	Not present
posSchedulingInfoList-r15	Not present
cellAccessRelatedInfo-5GC-r15	Not present
ims-EmergencySupport5GC-r15	Not present
eCallOverIMS-Support5GC-r15	Not present
nonCriticalExtension	Not present
}
}
}
}
}
}
}
}

Condition	Explanation
RF_INTF_MITIG	This condition applies for CRS interference mitigation testing

– SystemInformationBlockType1-BR-r13

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

Table 5.2.1.3-2A: SystemInformationBlockType1-BR-r13 exceptions

Derivation Path: Clause 4.4.3.2 Table 4.4.3.2-3A
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
si-WindowLength-BR-r13	ms40
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {			RF_INTF_MITIG
hsdn-Cell-r15	Not present
cellSelectionInfoCE-v1530	Not present
crs-IntfMitigConfig-r15 CHOICE {	Not present
crs-IntfMitigNumPRBs	n6
}
cellBarred-CRS-r15	notBarred
plmn-IdentityList-v1530	Not present
posSchedulingInfoList-r15	Not present
cellAccessRelatedInfo-5GC-r15	Not present
ims-EmergencySupport5GC-r15	Not present
eCallOverIMS-Support5GC-r15	Not present
nonCriticalExtension	Not present
}
}
}
}
}
}
}
}

Condition	Explanation
RF_INTF_MITIG	This condition applies for CRS interference mitigation testing

– SystemInformationBlockType2

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

Table 5.2.1.3-3: SystemInformationBlockType2 exceptions

Derivation Path: Clause 4.4.3.3 Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
timeAlignmentTimerCommon	infinity
}

5.2A Generic RF procedures

The UE test state used for testing is specified in the individual test cases in the corresponding test specification TS 36.521-1 [21] or TS 36.521-3 [34].

This clause describes UE test states which can be used in the initial condition of many test cases defined in TS 36.521-1 [21] and TS 36.521-3 [34].

5.2A.1 UE RF test states

Table 5.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		RRC_IDLE	ECM-IDLE	EMM-REGISTERED	1 default EPS bearer context active	Active
State 2A-RF-CE	Registered, Idle Mode, Cell supporting BL/CE UE, UE Test Mode Activated		RRC_IDLE	ECM-IDLE	EMM-REGISTERED	1 default EPS bearer context active	Active
State 3A-RF		Generic Default RB Established, UE Test Mode Activated	RRC_CONNECTED 1 data radio bearer configured	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active
State 3A-RF-CE		Generic Default RB Established, Cell supporting BL/CE UE, UE Test Mode Activated	RRC_CONNECTED 1 data radio bearer configured	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active
State 3A-RF-DC1		DC MCG/SCG Dedicated RB established, UE Test Mode Activated	RRC_CONNECTED 2 data radio bearers configured	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active on the PCell 1 dedicated EPS bearer context(s) active on the PSCell	Active
State 3A-RF-DC2		DC Split Default RB established, UE Test Mode Activated	RRC_CONNECTED 1 data radio bearer configured	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active on the PCell and PSCell with UL transmission of PDCP SDUs on PSCell	Active
State 3A-RF-V2X		Generic Default RB Established, UE Test Mode Activated, V2X Setup	RRC_CONNECTED 1 data radio bearer configured	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active
State 3B-RF		Reserved for E-UTRAN UE state for RRM testing as described in Table 7.2A.1-1
State 4A-RF		Loopback Activation without looped data	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active
State 4A-RF-CE		Loopback Activation without looped data, Cell supporting BL/CE UE	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active
State 4A-RF-DC1		DC MCG/SCG DRBs Loopback Activation without looped data	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active on the PCell 1 dedicated EPS bearer context(s) active on the PSCell	Active
State 4A-RF-DC2		DC Split DRB Loopback Activation without looped data	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active on the PCell and PSCell	Active
State 4A-RF-V2X		Loopback Activation without looped data, V2X Setup	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active

5.2A.1A Registered, Idle Mode, UE Test Mode Activated (State 2A-RF)

5.2A.1A.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The Test USIM shall be inserted.

5.2A.1A.2 Definition of system information messages

The default system information messages are used.

5.2A.1A.3 Procedure

Table 5.2A.1A.3-1: UE registration with test mode activation procedure (state 1 to state 2A-RF)

Step	Procedure	Message Sequence
		U – S	Message
1 to 9a2	Steps 1 to 9a2 as specified in the procedure in clause 4.5.2.3 take place	–	–
10	The SS transmits an ACTIVATE TEST MODE message to activate UE radio bearer test mode procedure.	<–	RRC: DLInformationTransfer TC: ACTIVATE TEST MODE
11	The UE transmits an ACTIVATE TEST MODE COMPLETE message.	–>	RRC: ULInformationTransfer TC: ACTIVATE TEST MODE COMPLETE
12	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
13	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
14	The SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure.	<–	RRC: UECapabilityEnquiry
15	The UE transmits a UECapabilityInformation message to transfer UE radio access capability.	–>	RRC: UECapabilityInformation
16	The SS transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0) according to 4.8.2.2.1.1. This message includes the ATTACH ACCEPT message. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT.	<–	RRC: RRCConnectionReconfiguration NAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST
17	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer.	–>	RRC: RRCConnectionReconfigurationComplete
–	EXCEPTION: In parallel to the event described in step 18 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane if requested by the UE.
18	This message includes the ATTACH COMPLETE message. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE.	–>	RRC: ULInformationTransfer NAS: ATTACH COMPLETE NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT
–	EXCEPTION: Steps18a1 to 18b6 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if a particular configuration has been chosen	–	–
18a1	IF IMS voice not supported and pc_voice_PS_1_CS_2, pc_attach and pc_TAU_connected_in_IMS are set to TRUE (Note 1) THEN the UE transmits a TRACKING AREA UPDATE REQUEST message.	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE REQUEST
18a2	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT
18a3	The UE transmits a TRACKING AREA UPDATE COMPLETE message.	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE
18b1	ELSE IF IMS voice not supported and pc_voice_PS_1_CS_2, pc_attach and pc_TAU_idle_in_IMS are set to TRUE (Note 2) THEN the SS transmits an RRCConnectionRelease message to release the RRC connection.	<–	RRC: RRCConnectionRelease
18b2	The UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
18b3	The SS transmit an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
18b4	The UE transmits an RRCConnectionSetupComplete message including a TRACKING AREA UPDATE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST
18b5	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT
18b6	The UE transmits a TRACKING AREA UPDATE COMPLETE message.	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE
19	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2A-RF).	<–	RRC: RRCConnectionRelease
NOTE 1: The procedure is used with specific message with no IMS voice network support. The UE is configured for voice domain preference IMS PS voice preferred, CS Voice as secondary and to initiate EPS attach. The UE implementation supports TAU in connected mode. NOTE 2: The procedure is used with specific message with no IMS voice network support. The UE is configured for voice domain preference IMS PS voice preferred, CS Voice as secondary and to initiate EPS attach. The UE implementation supports TAU in idle mode.

5.2A.1A.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A with the exceptions below.

Table 5.2A.1A.4-1: RRCConnectionRequest (Step 2 and 19b2)

Derivation Path: Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
ue-Identity	Any allowed value
}
}
}

Table 5.2A.1A.4-2: UECapabilityInformation (Step 15)

Derivation Path: Table 4.6.1-23
Information Element	Value/remark	Comment	Condition
UECapabilityInformation ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
ueCapabilityInformation-r8	Any allowed value
}
}
}

Table 5.2A.1A.4-3: ATTACH ACCEPT (Step 16)

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

Table 5.2A.1A.4-4: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Step 16)

Derivation Path: Table 4.7.3-6
Information Element	Value/remark	Comment	Condition
EPS QoS	See Reference default EPS bearer context #1 in table 6.6.1-1		NON pc_Disable_E-UTRA_NOIMSVoIP
	See Reference default EPS bearer context #2 in table 6.6.1-1		pc_Disable_E-UTRA_NOIMSVoIP
Access point name	The SS defines a Default APN or, if the UE transmits an ESM INFORMATION RESPONSE message providing an APN, the SS shall use this value if it is not the IMS APN. If it is the default IMS APN, the SS defines a Default APN.		NON pc_Disable_E-UTRA_NOIMSVoIP
	IMS.apn.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org The <MNC> and <MCC> are set to the same values as in IMSI.		pc_Disable_E-UTRA_NOIMSVoIP
PDN address			IPv4v6
Length of PDN address contents	5 octets
PDN type value	‘001’B	IPv4
PDN address information	IPv4 address	The SS provides a valid IPv4 address
ESM cause	IF "PDN type" IE in step 4 is ‘IPv4v6’ THEN ‘00110010’B ELSE Not present	"PDN type IPv4 only allowed"

Table 5.2A.1A.4-5: TRACKING AREA UPDATE REQUEST (Steps 19a1 and 19b4)

Derivation Path: 36.508 Table 4.7.2-27 with condition combined_TA_LA

Table 5.2A.1A.4-6: TRACKING AREA UPDATE ACCEPT (Steps 19a2 and 19b5)

Derivation Path: 36.508 Table 4.7.2-24 with condition combined_TA_LA
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

5.2A.1AA Registered, Idle Mode, UE Test Mode Activated in cell supporting BL/CE UE (State 2A-RF-CE)

The same assumptions and definitions apply as in clause 5.2A.1A.

5.2A.1AA.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The Test USIM shall be inserted.

5.2A.1AA.2 Definition of system information messages

The default system information messages are used with the exceptions below.

Table 5.2A.1AA.2-1: MasterInformationBlock

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 5.2A.1AA.2-2: SystemInformation-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-2A.

Table 5.2A.1AA.2-3: SystemInformationBlockType1-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-3A.

5.2A.1AA.3 Procedure

For RF testing of BL-UE use the same procedure as in clause 5.2A.1A.3 with the exception below:

– BR-BCCH replaces BCCH.

For RF testing of non-BL UE supporting CE use the procedure in Table 5.2A.1AA.3-1.

Table 5.2A.1AA.3-1: UE registration procedure (state 1 to state 2A-RF-CE)

Step	Procedure	Message Sequence
		U – S	Message
1	In addition to the system information broadcasted on BCCH the SS broadcasts 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.	<–	RRC: SYSTEM INFORMATION (BCCH and BCCH-BR)
2 to 9a2	Same procedure for steps 2 to 9a2 as specified in the procedure in clause 4.5.2.3	–	–
10 to 19	Same procedure for steps 10 to 19 as specified in the procedure in clause 5.2A.1A.3	–	–

5.2A.1AA.4 Specific message contents

Same specific message content as in clause 5.2A.1A.4 with the exception below:

– In addition to any other conditions use the condition CEmodeB if the test case specifically tests CE mode B else use condition CEmodeA.

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

In tests referring to test mode State 3A-RF, in order to avoid any uncontrollable transmission of uplink U-plane data, test mode State 4A-RF (specified in 5.2A.3) may be used and configured instead.

5.2A.2.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The Test USIM shall be inserted.

5.2A.2.2 Definition of system information messages

The default system information messages are used.

5.2A.2.3 Procedure

Table 5.2A.2.3-1: UE registration with default EPS bearer establishment and test mode activation procedures

Step	Procedure	Message Sequence
		U – S	Message
1		<–	RRC: SYSTEM INFORMATION (BCCH)
2 to 18	Steps 2 to 18 as specified in the procedure in clause 5.2A.1A.3 take place.	–	–

For Rel-11 or higher UEs, that support frequencyBandRetrieval_r11, where the UE has not sent all supported band combinations in UECapabilityInformation (Step 15 of table 5.2A.2.3-1) the following procedure shall be executed after the completion of the procedure in table 5.2A.2.3-1:

Table 5.2A.2.3-2: Retrieval of additional UE capabilities for Rel-11 and higher UEs that support frequencyBandRetrieval_r11

Step	Procedure	Message Sequence
		U – S	Message
1 to 3	Steps 1 to 3 as specified in the procedure in clause 5.2A.7.3 take place.	–	–

5.2A.2.4 Specific message contents

All specific message contents shall be referred to clause 5.2A.1A.4 with the exception below:

– In addition to any other conditions use the condition CEmodeB if the test case specifically tests CE mode B else use condition CEmodeA.

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

5.2A.2A.1 Initial conditions

System Simulator:

– 2 cells, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The UE shall be in Generic Default RB Established, UE Test Mode Activated (State 3A-RF).

5.2A.2A.2 Definition of system information messages

The default system information messages are used.

5.2A.2A.3 Procedure

The establishment of MCG/SCG dedicated radio bearer connection is assumed to always be mobile terminated.

Table 5.2A.2A.3-1: Procedure for MCG/SCG dedicated bearer establishment

Step	Procedure	Message Sequence
		U – S	Message
1	The SS adds the PSCell and configures a new SCG data radio bearer and the associated dedicated EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new SCG data radio bearer, associated with the dedicated EPS bearer context in the NAS message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

5.2A.2A.4 Specific message contents

All specific message contents shall be referred to clause 5.2A.1A.4, with exceptions as below.

Table 5.2A.2A.4-1: RRCConnectionReconfiguration (Step 1, Table 5.2A.2A.3-1)

Derivation Path: 36.508, Table 4.6.1-8 using condition PSCell_Add_SCG_DRB

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

In tests referring to test mode State 3A-RF-CE, in order to avoid any uncontrollable transmission of uplink U-plane data, test mode State 4A-RF-CE (specified in 5.2A.3AA) may be used and configured instead.

5.2A.2AA.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The Test USIM shall be inserted.

5.2A.2AA.2 Definition of system information messages

The default system information messages are used with the exceptions below.

Table 5.2A.2AA.2-1: MasterInformationBlock

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 5.2A.2AA.2-2: SystemInformation-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-2A.

Table 5.2A.2AA.2-3: SystemInformationBlockType1-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-3A
Information Element	Value/remark	Comment	Condition
schedulingInfoList-BR-r13 SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {	n entries	n is the same number of entries, and listed in the same order, as in SchedulingInfoList (without suffix)
si-Narrowband-r13[1]	1	Narrowband index 0	1.4 MHz BW
si-Narrowband-r13[1]	2	Narrowband index 1	3 MHz BW
si-Narrowband-r13[1]	4	Narrowband index 3	5 MHz BW or 15 MHz BW or 20 MHz BW
si-Narrowband-r13[1]	6	Narrowband index 5	10 MHz BW
si-TBS-r13[1]	b712
….
si-Narrowband-r13[n]	1	Narrowband index 0	1.4 MHz BW
si-Narrowband-r13[n]	2	Narrowband index 1	3 MHz BW
si-Narrowband-r13[n]	4	Narrowband index 3	5 MHz BW or 15 MHz BW or 20 MHz BW
si-Narrowband-r13[n]	6	Narrowband index 5	10 MHz BW
si-TBS-r13[n]	b712
}

Condition	Explanation
1.4 MHz BW	Used for cells with 1.4 MHz bandwidth
3 MHz BW	Used for cells with 3 MHz bandwidth
5 MHz BW	Used for cells with 5 MHz bandwidth
10 MHz BW	Used for cells with 10 MHz bandwidth
15 MHz BW	Used for cells with 15 MHz bandwidth
20 MHz BW	Used for cells with 20 MHz bandwidth

5.2A.2AA.3 Procedure

For RF testing of BL-UE use the procedure in Table 5.2A.2AA.3-1. For RF testing of non-BL UE supporting CE use the procedure in Table 5.2A.2AA.3-2.

Table 5.2A.2AA.3-1: UE registration with default EPS bearer establishment and test mode activation procedures

Step	Procedure	Message Sequence
		U – S	Message
1		<–	RRC: SYSTEM INFORMATION (BR-BCCH)
2 to 18	Steps 2 to 18 as specified in the procedure in clause 5.2A.1A.3 take place.	–	–

Table 5.2A.2AA.3-2: UE registration procedure (state 1 to state 2A-RF-CE)

Step	Procedure	Message Sequence
		U – S	Message
1	In addition to the system information broadcasted on BCCH the SS broadcasts 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.	<–	RRC: SYSTEM INFORMATION (BCCH and BCCH-BR)
2 to 18	Steps 2 to 18 as specified in the procedure in clause 5.2A.1A.3 take place.	–	–

5.2A.2AA.4 Specific message contents

All specific message contents shall be referred to clause 5.2A.1A.4 with the exceptions below:

– In addition to any other conditions use the condition CEmodeB if the test case specifically tests CE mode B else use condition CEmodeA.

Table 5.2A.2AA.4-1: MPDCCH-Config-r13

Derivation Path: 36.508 Table 4.6.3-2B
Information Element	Value/remark	Comment	Condition
mpdcch-config-r13 CHOICE[1] {
setup SEQUENCE {
mpdcch-config-r13 CHOICE[1] {
setup SEQUENCE {
csi-NumRepetitionCE-r13	sf1
mpdcch-pdsch-HoppingConfig-r13	off
mpdcch-StartSF-UESS-r13 CHOICE {
fdd-r13	v1		FDD
tdd-r13	v1		TDD
}
mpdcch-NumRepetition-r13	r1	No repetitions to reduce impact on legacy E-UTRA test cases for category M1 UEs.
mpdcch-Narrowband-r13	1	Narrowband index 0
}
}
}
}

Condition	Explanation
FDD	FDD cell environment
TDD	TDD cell environment

5.2A.2B DC Split Default RB established, UE Test Mode Activate (State 3A-RF-DC2)

5.2A.2B.1 Initial conditions

Same as in sub-clause 5.2A.2A.1.

5.2A.2B.2 Definition of system information messages

The default system information messages are used.

5.2A.2B.3 Procedure

The establishment of split dedicated radio bearer connection is assumed to always be mobile terminated.

Table 5.2A.2B.3-1: Procedure for Dual Connectivity Split default bearer establishment

Step	Procedure	Message Sequence
		U – S	Message
4	The SS adds a PSCell and configures new split data radio bearer	<–	RRC: RRCConnectionReconfiguration
5	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the split data radio bearer with UL transmission of PDCP SDUs on the PSCell	–>	RRC: RRCConnectionReconfigurationComplete

5.2A.2B.4 Specific message contents

All specific message contents shall be referred to clause 5.2A.1A.4, with exceptions as below.

Table 5.2A.2B.4-1: RRCConnectionReconfiguration (Step 4, Table 5.2A.2A.3-1)

Derivation Path: 36.508, Table 4.6.1-8 using condition PSCell_Add_Split_DRB

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

5.2A.2C.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– 1 V2V transmitter for receiver characteristics or 1 V2V receiver for transmitter characteristics

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The Test USIM shall be inserted.

5.2A.2C.2 Definition of system information messages

The default system information messages are used with the exceptions below:

Table 5.2A.1B.2-1: SystemInformationBlockType21

Derivation Path: 36.508 Table 4.4.3.3-19.

5.2A.2C.3 Procedure

For RF testing of V2X Communication, use the same procedure as in clause 5.2A.2.3.

5.2A.2C.4 Specific message contents

All specific message contents shall be referred to clause 5.2A.1A.4, with exceptions as below:

Table 5.2A.2A.4-1: RRCConnectionReconfiguration (Step 16, Table 5.2A.1A.3-1)

Derivation Path: 36.508, Table 4.6.1-8B using conditions SETUP and SCHEDULED

5.2A.3 Loopback Activation without looped data (State 4A-RF)

Editor’s note: Test mode State 4A-RF is used and configured as an alternative to test mode State 3A-RF, to avoid any uncontrollable transmission of uplink U-plane data.

5.2A.3.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The UE shall be in Generic RB Establishment state, UE Test Mode Activated (State 3A-RF).

5.2A.3.2 Definition of system information messages

The default system information messages are used.

5.2A.3.3 Procedure

Table 5.2A.3.3-1: UE registration with default EPS bearer establishment and test mode activation procedures

Step	Procedure	Message Sequence
		U – S	Message
1	The SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode.	<–	RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP
2	The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.	–>	RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE

5.2A.3.4 Specific message contents

All specific message contents shall be referred to clause 4.5.4.4, with the exceptions below.

Table 5.2A.3.4-1: CLOSE UE TEST LOOP (in the preamble)
(Step 1 in Table 5.2A.3.3-1)

Derivation Path: 36.509 clause 6.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1 1 1 1
Skip indicator	0 0 0 0
Message type	1 0 0 0 0 0 0 0
UE test loop mode	0 0 0 0 0 0 0 0	UE test loop mode A
UE test loop mode A LB setup
Length of UE test loop mode A LB setup list in bytes	0 0 0 0 0 0 1 1	Length of one LB setup DRB (3 bytes)
LB setup DRB	0 0 0 0 0 0 0 0, 0 0 0 0 0 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0	UL PDCP SDU size = 0 bits (0 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1
UE test loop mode B LB setup	Not present
UE test loop mode B LB setup	Not present

5.2A.3A DC MCG/SCG DRBs Loopback Activation without looped data (State 4A-RF-DC1)

Editor’s note: Test mode State 4B-RF is used and configured as an alternative to test mode State 3B-RF, to avoid any uncontrollable transmission of uplink U-plane data.

5.2A.3A.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The UE shall be in DC MCG/SCG Dedicated RB established, UE Test Mode Activated (State 3A-RF-DC1).

5.2A.3A.2 Definition of system information messages

Same as in sub-clause 5.2A.3.2.

5.2A.3A.3 Procedure

Same as in sub-clause 5.2A.3.3.

5.2A.3A.4 Specific message contents

Same as in sub-clause 5.2A.3.4.

5.2A.3AA Loopback Activation without looped data in cell supporting BL/CE UE (State 4A-RF-CE)

Editor’s note: Test mode State 4A-RF-CE is used and configured as an alternative to test mode State 3A-RF-CE, to avoid any uncontrollable transmission of uplink U-plane data.

5.2A.3AA.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The UE shall be in Generic RB Establishment state, UE Test Mode Activated (State 3A-RF).

5.2A.3AA.2 Definition of system information messages

The default system information messages are used with the exceptions below.

Table 5.2A.3AA.2-1: MasterInformationBlock

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 5.2A.3AA.2-2: SystemInformation-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-2A.

Table 5.2A.2AA.2-3: SystemInformationBlockType1-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-3A.

5.2A.3AA.3 Procedure

Table 5.2A.3.3-1: UE registration with default EPS bearer establishment and test mode activation procedures

Step	Procedure	Message Sequence
		U – S	Message
1	The SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode.	<–	RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP
2	The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.	–>	RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE

5.2A.3AA.4 Specific message contents

Same as in clause 5.2A.3.4.

5.2A.3B DC Split DRB Loopback Activation without looped data (State 4A-RF-DC2)

Editor’s note: Test mode State 4C-RF is used and configured as an alternative to test mode State 3C-RF, to avoid any uncontrollable transmission of uplink U-plane data.

5.2A.3B.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The UE shall be in DC Split Default RB established, UE Test Mode Activated (State 3A-RF-DC2).

5.2A.3B.2 Definition of system information messages

Same as in sub-clause 5.2A.3.2.

5.2A.3B.3 Procedure

Same as in sub-clause 5.2A.3.3.

5.2A.3B.4 Specific message contents

Same as in sub-clause 5.2A.3.4.

5.2A.3C Loopback Activation without looped data, V2X Setup (State 4A-RF-V2X)

Editor’s note: Test mode State 4A-RF-V2X is used and configured as an alternative to test mode State 3A-RF-V2X, to avoid any uncontrollable transmission of uplink U-plane data.

5.2A.3C.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– 1 GNSS simulator

– 1 V2V transmitter for receiver characteristics or 1 V2V receiver for transmitter characteristics

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The UE shall be in Generic RB Establishment state, UE Test Mode Activated, V2X Setup (State 3A-RF-V2X).

5.2A.3C.2 Definition of system information messages

Same as in sub-clause 5.2A.3.2.

5.2A.3C.3 Procedure

Same as in sub-clause 5.2A.3.3.

5.2A.3C.4 Specific message contents

All specific message contents shall be referred to clause 5.2A.3.4, with exceptions as below:

Table 5.2A.3C.4-1: ACTIVATE TEST MODE: V2X Communication

Derivation Path: 36.508, Table 4.7A-1 using condition UE TEST LOOP MODE E

Table 5.2A.3C.4-2: CLOSE UE TEST LOOP: V2X Communication

Derivation Path: 36.508, Table 4.7A-3 using condition UE TEST LOOP MODE E

5.2A.4 Procedure to configure SCC

Table 5.2A.4.-1: UE RRC reconfiguration with sCELLToAdd

Step	Procedure	Message Sequence
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration(sCellToAddModList) message to establish the SCC(s).	<–	RRC: RRCConnectionReconfiguration
2	The UE transmits an RRCConnectionReconfigurationComplete	–>	RRC: RRCConnectionReconfigurationComplete
3	If not all SCCs are established, then repeat step 1 and 2.

5.2 A.41. Specific message contents

All specific message contents shall be referred to clause 4.5.2A.4, with exceptions as below.

5.2A.4.1.1 Exceptions for all CA tests

RRCConnectionReconfiguration

Table 5.2A.4.1.1-1: RRCConnectionReconfiguration

Derivation Path: Clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

MAC configurations

Table 5.2A.4.1.1-2: MAC-MainConfig-RBC

Derivation Path: Clause 4.8.2.1.5 Table 5.5.1.1-1, condition Scell_AddMod
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.

5.2A.4.1.2 Exceptions for UL CA tests

RadioResourceConfigCommonSCell-r10-DEFAULT

Table 5.2A.4.1.2-1: RadioResourceConfigCommonSCell-r10-DEFAULT

Derivation Path: Clause 4.6.3 Table 4.6.3-13A
Information Element	Value/remark	Comment	Condition
RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {
ul-Configuration-r10 SEQUENCE {			UL CA
ul-FreqInfo-r10 SEQUENCE {
ul-CarrierFreq-r10	Not Present	For FDD: If absent, the (default) value determined from the default TX-RX frequency separation defined in 3GPP TS 36.101 [27], table 5.7.3-1 applies. For TDD: This parameter is absent and it is equal to the downlink frequency.
ul-Bandwidth-r10	Not Present	Same downlink bandwidth as used for target SCell
additionalSpectrumEmissionSCell-r10	31 (CA_NS_31)		Intra-B UL CA
additionalSpectrumEmissionSCell-r10	1 (NS_01)		Inter-B UL CA
}
soundingRS-UL-ConfigCommon-r10	release
}
}

Condition	Explanation
UL CA	When UL Carrier Aggregation is used.
Intra-B UL CA	Intra-band Carrier Aggregation
Inter-B UL CA	Inter-band Carrier Aggregation

PhysicalConfigDedicatedSCell-r10-DEFAULT

Table 5.2A.4.1.2-2: 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	Present
ul-Configuration-r10 SEQUENCE {			UL CA
antennaInfoUL-r10	Not Present
pusch-ConfigDedicatedSCell-r10	Not present
uplinkPowerControlDedicatedSCell-r10	UplinkPowerControlDedicatedSCell-r10-DEFAULT
cqi-ReportConfigSCell-r10	Not present
soundingRS-UL-ConfigDedicated-r10	Not present
soundingRS-UL-ConfigDedicated-v1020	Not present
soundingRS-UL-ConfigDedicatedAperiodic-r10	Not present
}
}

Condition	Explanation
UL CA	When UL Carrier Aggregation is used.

5.2A.5 Exceptions for feICIC tests

5.2A.5.1 Specific message contents

All specific message contents shall be referred to clause 4.6, with exceptions as below.

5.2A.5.1.1 Neighbour cell info for all feICIC test cases

Table 5.2A.5.1.1-1: RRCConnectionReconfiguration

Derivation Path: clause 4.6.1, Table 4.6.1-8: RRCConnectionReconfiguration
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated	RadioResourceConfigDedicated-SRB2-DRB(n, m)		SRB2-DRB(n, m)
securityConfigHO	Not present
nonCriticalExtension SEQUENCE {}	Not present
}
}
}
}

Table 5.2A.5.1.1-2: RadioResourceConfigDedicated-SRB2-DRB(n, m)

Derivation Path: clause 4.6.3, Table 4.6.3-16 RadioResourceConfigDedicated-SRB2-DRB(n,m)
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SRB2-DRB(n, m) ::= SEQUENCE {
neighCellsCRS-Info-r11 ::= CHOICE {
setup SEQUENCE {
CRS-AssistancedInfoList-r11 ::= SEQUENCE (SIZE (1..maxCellReport)) OF CRS-AssistanceInfo-r11
CRS-AssistanceInfo-r11 :: = SEQUENCE {		CRS information for all the configured neighbour cells
physCellId-r11	Based on simulated cell requirements
antennaPortsCount-r11	Based on simulated cell requirements
mbsfn-SubframeConfigList-r11	Based on simulated cell requirements
}
}
}
}

5.2A.6 Exceptions for NAICS tests

5.2A.6.1 NAICS specific RRC Connection reconfiguration procedure

5.2A.6.1.1 Procedure

Table 5.2A.6.1.1-1: Procedure for RRC connection reconfiguration

Step	Procedure	Message Sequence
		U – S	Message
1	The SS transmits and RRCConnectionReconfiguration message.	<–	RRC: RRCConnectionReconfiguration
2	The UE transmits an RRCConnectionReconfigurationComplete message	–>	RRC: RRCConnectionReconfigurationComplete

5.2A.6.1.1 Specific message contents

Same as in 5.2A.6.2 with the condition “NAICS_ONLY”.

5.2A.6.2 Specific message contents

All specific message contents shall be referred to clause 4.6, with exceptions as below.

5.2A.6.2.1 RRCConnectionReconfiguration for setting up and releasing NAICS configuration in NAICS test cases

Table 5.2A.6.2.1-1: RRCConnectionReconfiguration

Derivation Path: 36.331 clause 6.2.2
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
dedicatedInfoNASList	Not present		NAICS_ONLY, NAICS_RELEASE
	Set according to specific message content		SRB2-DRB_NAICS(n, m)
radioResourceConfigDedicated	RadioResourceConfigDedicated-SRB2-DRB_NAICS_ONLY		NAICS_ONLY
	RadioResourceConfigDedicated-SRB2-DRB_NAICS(n, m)		SRB2-DRB_NAICS(n, m)
	RadioResourceConfigDedicated_NAICS_RELEASE		NAICS_RELEASE
securityConfigHO	Not present
}
}
}
}

Condition	Explanation
SRB2-DRB_NAICS(n,m)	Establishment of a SRB and DRB combination with n x AM DRB and m x UM DRB (including establishment of SRB2) plus NAICS information
NAICS_ONLY	Stand alone NAICS set-up
NAICS_RELEASE	Standalone release of all NAICS configurations

Table 5.2A.6.2.1-2: RadioResourceConfigDedicated-SRB2-DRB_NAICS(n, m)

Derivation Path: clause 4.6.3, Table 4.6.3-16 RadioResourceConfigDedicated-SRB2-DRB(n,m)
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SRB2-DRB_NAICS(n, m) ::= SEQUENCE {
neighCellsCRS-Info-r11	NeighCellsCRS-Info_NAICS
}

Table 5.2A.6.2.1-3: RadioResourceConfigDedicated-SRB2-DRB_NAICS_ONLY

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SRB2-DRB_NAICS_ONLY ::= SEQUENCE {
neighCellsCRS-Info-r11	NeighCellsCRS-Info_NAICS
}

Table 5.2A.6.2.1-4: NeighCellsCRS-Info_NAICS

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
neighCellsCRS-Info-r11 ::= CHOICE {
setup SEQUENCE {
naics-Info-r12 ::= CHOICE {
setup :: = SEQUENCE {
neighCellsToReleaseList-r12	Not present
neighCellsToAddModList-r12 SEQUENCE (SIZE (1..maxNeighCell-r12)) OF NeighCellsInfo-r12
NeighCellsInfo-r12 ::= SEQUENCE {
physCellId-r12	Based on simulated cell requirements
p-b-r12	Based on simulated cell requirements
crs-PortsCount-r12	Based on simulated cell requirements
mbsfn-SubframeConfig-r12	Not present
p-aList-r12 SEQUENCE (SIZE (1..maxP-a-PerNeighCell-r12)) OF P-a
P-a	dB-6
P-a	dB-3
P-a	dB0
transmissionModeList-r12	‘01110110’B	Transmission modes 2,3,4,8 and 9
resAllocGranularity-r12	1
}
servCellp-a-r12	Not present
}
}
}
}

Table 5.2A.6.2.1-5: RadioResourceConfigDedicated_NAICS_RELEASE

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SRB2-DRB_NAICS_ONLY ::= SEQUENCE {
neighCellsCRS-Info-r11 ::= CHOICE {
setup SEQUENCE {
naics-Info-r12 ::= CHOICE {
release	NULL
}
}
}
}
}

5.2A.7 Procedure to retrieve additional UE Capabilities for Rel-11 and higher UEs that support frequencyBandRetrieval_r11

5.2A.7.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under ideal radio conditions as defined in clause 5

User Equipment:

– The Test USIM shall be inserted.

5.2A.7.2 Definition of system information messages

The default system information messages are used.

5.2A.7.3 Procedure

Table 5.2A.7.3-1: Procedure to retrieve additional UE capabilities

Step	Procedure	Message Sequence
		U – S	Message
1	If the UE sent freqBandretrieval-r11 in previous UECapabilityInformation, the SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure	<–	RRC: UECapabilityEnquiry
2	The UE transmits a UECapabilityInformation message to transfer UE radio access capability.	–>	RRC: UECapabilityInformation
3	If the UE did not report all supported E-UTRA bands relevant to the tested bands, repeat steps 1 and 2.

5.2A.7.4 Specific message contents

Table 5.2A.7.4-1: UECapabilityEnquiry (Step 1)

Derivation Path: Clause 6.2.2 Table 4.6.1-22
Information Element	Value/remark	Comment	Condition
UECapabilityEnquiry ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE {
ueCapabilityEnquiry-r8 SEQUENCE {
ue-CapabilityRequest	eutra
nonCriticalExtension SEQUENCE {
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {
requestedFrequencyBands-r11 SEQUENCE (SIZE (1..16)) OF SEQUENCE{
FreqBandIndicator-r11
}
nonCriticalExtension SEQUENCE {}	Not Present
}
}
}
}
}
}

5.2A.8 Exceptions for DL Control channel interference mitigation (Type A and Type B) tests

5.2A.8.1 Specific message contents

All specific message contents shall be referred to clause 4.6, with exceptions as below.

5.2A.8.1.1 Neighbour cell info for all CCIM test cases

Table 5.2A.5.1.1-1: RRCConnectionReconfiguration

Derivation Path: clause 4.6.1, Table 4.6.1-8: RRCConnectionReconfiguration
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated	RadioResourceConfigDedicated-SRB2-DRB(n, m)		SRB2-DRB(n, m)
securityConfigHO	Not present
nonCriticalExtension SEQUENCE {}	Not present
}
}
}
}

Table 5.2A.5.1.1-2: RadioResourceConfigDedicated-SRB2-DRB(n, m)

Derivation Path: clause 4.6.3, Table 4.6.3-16 RadioResourceConfigDedicated-SRB2-DRB(n,m)
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SRB2-DRB(n, m) ::= SEQUENCE {
neighCellsCRS-Info-r13 ::= CHOICE {
setup SEQUENCE {
CRS-AssistancedInfoList-r13 ::= SEQUENCE (SIZE (1..maxCellReport)) OF CRS-AssistanceInfo-r13
CRS-AssistanceInfo-r13 :: = SEQUENCE {		CRS information for all the configured neighbour cells
physCellId-r13	Based on simulated cell requirements
antennaPortsCount-r13	Based on simulated cell requirements
}
}
}
}

5.3 Default RRC message and information elements contents

5.3.1 Radio resource control information elements

As defined in clause 4.6.3 with the following exceptions:

Table 5.3.1-1: TDD-Config-DEFAULT

Derivation Path: Clause 4.6.3 Table 4.6.3-23
Information Element	Value/remark	Comment	Condition
TDD-Config-DEFAULT ::= SEQUENCE {
subframeAssignment	sa1
specialSubframePatterns	ssp4		RF
}

Condition	Explanation
RF	For all the RF tests specified in 36.521-1

Table 5.3.1-2: RadioResourceConfigCommonSIB-DEFAULT

Derivation Path: Clause 4.6.3 Table 4.6.3-14
Information Element	Value/remark	Comment	Condition
RadioResourceConfigCommonSIB-DEFAULT ::= SEQUENCE {
rach-ConfigCommon	RACH-ConfigCommon-DEFAULT
bcch-Config	BCCH-Config-DEFAULT
pcch-Config	PCCH-Config-DEFAULT
prach-Config	PRACH-ConfigSIB-DEFAULT
pdsch-ConfigCommon	PDSCH-ConfigCommon-DEFAULT
pusch-ConfigCommon	PUSCH-ConfigCommon-DEFAULT
pucch-ConfigCommon	PUCCH-ConfigCommon-DEFAULT
soundingRS-UL-ConfigCommon CHOICE {
release	NULL
}
uplinkPowerControlCommon	UplinkPowerControlCommon-DEFAULT
ul-CyclicPrefixLength	len1
}

Table 5.3.1-3: 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-ConfigInfo SEQUENCE {
prach-ConfigIndex	3		TDD
}
}

Condition	Explanation
TDD	TDD cell environment

Table 5.3.1-4: RadioResourceConfigCommonSCell-r10-DEFAULT

Derivation Path: Clause 4.6.3 Table 4.6.3-13A
Information Element	Value/remark	Comment	Condition
RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {
ul-Configuration-r10	Not Present		DL CA only
}

Table 5.3.1-5: 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		DL CA only
}

Condition	Explanation
DL CA only	When DL CA without UL CA is used.

5.3.2 Measurement information elements

As defined in clause 4.6.6 with the following exceptions:

Table 5.3.2-1: 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	0		LAA_Receiver
ms80-r12	0		LAA_DemodCSI
}
}
}

Condition	Explanation
LAA_Receiver	Used for LAA receiver characteristics test cases
LAA_DemodCSI	Used for LAA demodulation and CSI reporting test cases

5.4 Default NAS message and information elements contents

5.5 Reference radio bearer configurations

5.5.1 SRB and DRB parameters

5.5.1.1 MAC configurations

As defined in clause 4.8.2.1.5 with the following exceptions:

Table 5.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 {
ul-SCH-Config	Not present		SCell_AddMod
ul-SCH-Config SEQUENCE {
maxHARQ-Tx	n1	Only one transmission per UL HARQ
}
drx-Config	Not present		SCell_AddMod
drx-Config CHOICE {
release	NULL
}
timeAlignmentTimerDedicated	infinity
}

Condition	Explanation
SCell_AddMod	Addition or modification of Scell

5.5.1.2 Physical Layer configurations

Table 5.5.1.2-1: PhysicalConfigDedicated-DEFAULT

Derivation Path: Clause 4.8.2.1.6 Table 4.8.2.1.6-1
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pdsch-ConfigDedicated	PDSCH-ConfigDedicated-DEFAULT	See subclause 4.6.3	SRB1
	Not present		RBC
pucch-ConfigDedicated	PUCCH-ConfigDedicated-DEFAULT	See subclause 4.6.3	SRB1
	Not present		RBC
pusch-ConfigDedicated	PUSCH-ConfigDedicated-DEFAULT	See subclause 4.6.3	SRB1
	Not present		RBC
uplinkPowerControlDedicated	UplinkPowerControlDedicated-DEFAULT	See subclause 4.6.3	SRB1
	Not present		RBC
tpc-PDCCH-ConfigPUCCH	Not present		SRB1
	TPC-PDCCH-Config-DEFAULT using condition PUCCH	See subclause 4.6.3	RBC
tpc-PDCCH-ConfigPUSCH	Not present		SRB1
	TPC-PDCCH-Config-DEFAULT using condition PUSCH	See subclause 4.6.3	RBC
cqi-ReportConfig	Not present		SRB1
	Not present		RBC
soundingRS-UL-ConfigDedicated	Not present		SRB1
	Not present		RBC
antennaInfo CHOICE {
defaultValue	NULL
}
schedulingRequestConfig	Not present		SRB1
	SchedulingRequest-Config-DEFAULT	See subclause 4.6.3	SRB1 and HalfDuplex and (CEmodeA or CEmodeB)
	Not present	See subclause 4.6.3	RBC
}
cqi-ReportConfig-r10	Not present		SCell_AddMod

Condition	Explanation
SRB1	Used at configuration of SRB1 during RRC connection (re-)establishment
RBC	Used at configuration of a radio bearer combination during SRB2+DRB establishment
SCell_AddMod	Addition or modification of SCell
CEmodeA	Used for CE mode A testing
CEmodeB	Used for CE mode B testing
HalfDuplex	Used during Type B HalfDuplex Operation

5.5.1.3 SRB and DRB combinations

5.5.1.3.1 Combinations on DL-SCH and UL-SCH

5.5.1.3.1.1 SRB1 and SRB2 for DCCH + n x AM DRB + m x UM DRB, where n=1 and m=0

This SRB and DRB combination is setup in UE Registration procedure and the Generic Radio Bearer Establishment with UE Test Mode Activated using specific message content – the default RRCConnectionReconfiguration message with condition SRB2-DRB(n, m).