4.5 Generic procedures

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 clause describes UE test states which can be used in the initial condition of many test cases defined in TS 36.521-1 [21], TS 36.523-1 [18] and TS 36.523-3 [34] or other procedures defined in this specification. This section also defines a set of procedures to bring the UE into these states.

4.5.1 UE test states

NOTE: The need to have a procedure for the transition from State 4/State 3 to State 2 is for further study and it can added if the technical motivation for this procedure can be justified.

Figure 4.5.1-1: E-UTRAN UE Test States for Basic Generic Procedures

Figure 4.5.1-2: E-UTRAN UE Test States for CIoT

NOTE: Transition to state 5 is performed only when Test Loop Mode E is required to be performed when UE is out of coverage.

In order that the UE can set up a call or session in E-UTRAN, there are a number of procedures to be undertaken in a hierachical sequence to move between known states. The sequences are shown in figure 4.5.1-1 and the status of the relevant protocols in the UE in the different states are given in table 4.5.1-1.

Table 4.5.1-1: The E-UTRAN UE states

		RRC	ECM	EMM	ESM	UE Test Mode
State 1	Switched OFF	—–	—–	—–	—–	—–
State 2	Registered, Idle Mode	RRC_IDLE	ECM-IDLE	EMM-REGISTERED	1 default EPS bearer context active. 2 default EPS bearer contexts active (only for RAN Assisted WLAN interworking)	Not active
State 2-CE	Registered, Idle Mode, Cell supporting BL/CE UE	RRC_IDLE	ECM-IDLE	EMM-REGISTERED	1 default EPS bearer context active.	Not active
State 2A	Registered, Idle Mode, UE Test Mode Activated	RRC_IDLE	ECM-IDLE	EMM-REGISTERED	1 default EPS bearer context active.	Active
State 2A-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 2B	Registered, Idle Mode, pre-registered on HRPD	RRC_IDLE	ECM-IDLE	EMM-REGISTERED	1 default EPS bearer context active.	Active
State 2C	Registered, Idle Mode, pre-registered on 1xRTT	RRC_IDLE	ECM-IDLE	EMM-REGISTERED	1 default EPS bearer context active.	Active
State 3	Generic RB Established	RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases. 2 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases (only for for RAN Assisted WLAN interworking)	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases. 2 default EPS bearer contexts active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases (only for RAN Assisted WLAN interworking)	Not active
State 3-CP	CIoT CP Connection Established	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	–	Not active
State 3A-CP	CIoT CP Connection Established, UE Test Mode Activated	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	–	Active
State 3-UP	CIoT UP Connection Established	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active.	Not active
State 3A-UP	CIoT UP Connection Established, UE Test Mode Activated	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active.	Active
State 4A-UP	Loopback Activation User Plane	RRC_CONNECTED	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active.	Active
State 3-CE	Generic RB Established, Cell supporting BL/CE UE	RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases.	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases.	Not active
State 3A	Generic RB Established, UE Test Mode Activated	RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases	Active
State 3A-CE	Generic RB Established, UE Test Mode Activated, Cell supporting BL/CE UE, UE Test Mode Activated	RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases	Active
State 3B	Generic RB Established, pre-registered on HRPD	RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases	Active
State 3C	Generic RB Established, pre-registered on 1xRTT	RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases	Active
State 4	Loopback Activated	RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases	Active
State 4-CE	Loopback Activated, Cell supporting BL/CE UE	RRC_CONNECTED 1 data radio bearer configured	ECM-CONNECTED	EMM-REGISTERED	1 default EPS bearer context active	Active
State 5	Out of Coverage	Any Cell Selection state	—–	—–	—–	Active
State 5-V2X	Out of Coverage, V2X setup	Any Cell Selection state	—–	—–	—–	Not active
State 5A-V2X	Out of Coverage, Loopback Activated, V2X setup	Any Cell Selection state	—–	—–	—–	Active

NOTE: Refer to TS 24.301 [28] subclause 5.5.1.1 for more details on the ESM state.

NOTE: Refer to TS 36.509 [38] for details regarding UE test mode and UE Loopback.

Figure 4.5.1-2: HRPD UE Test States for Basic Generic Procedures

In order for the UE to set up a session in an HRPD RAN, there are a number of procedures that need to be performed in a certain sequence to move between known UE states. These states and sequences are shown in figure 4.5.1-2. HRPD UE states are described in table 4.5.1-2.

Table 4.5.1-2: Description of HRPD UE states

State	Description
H2	The UE is registered on the HRPD network, but has no active connection to the network. The Inter-RAT Idle State Protocol (IR-ISP) is in Monitor State. The UE should be ready to perform a non-optimised cell reselection to E-UTRAN (as per [41] cl. 8 and [42] cl. 14.1).
H3	The UE is registered on the HRPD network, and has an active network connection. The UE should be ready to perform a non-optimised handover to E-UTRAN (as per [41] cl. 8).
H2A	Same state as State H2, but the UE is also pre-registered in E-UTRAN. The UE should be ready to perform an optimised cell reselection to E-UTRAN (as per [41] cl. 9.6).
H3A	Same state as State H3, but the UE is also pre-registered in E-UTRAN. The UE should be ready to perform an optimised handover to E-UTRAN (as per [41] cl. 9.5).

4.5.2 UE Registration (State 2)

4.5.2.0 General

IF pc_ue_CategoryDL_M1 THEN use the procedure for State 2-CE according to clause 4.5.2AA ELSE use the procedure defined in the present clause.

NOTE: The statement to use alternate procedure for CAT M1 UE (pc_ue_CategoryDL_M1 is set) is to enable LTE legacy protocol test cases to be used for CAT M1 UE testing. Any CAT M1 or CE specific test cases should not rely on this statement, but refer directly to the relevant CE specific state.

UE Registration depends on the specific configuration of a UE, which is expressed by PICS according to TS 36.523-2 [19]. In order to reduce complexity and to achieve testability several assumptions and definitions are made:

– An IMS capable UE is compliant to GSMA PRD IR.92 [52];

– During initial UE registration the UE requests for one or two PDN connectivities;

– When the UE requests for two PDN connectivities:

– it re-uses the existing RRC connection for signalling regarding the 2^nd PDN connectivity;

– one of the PDN connectivities is for IMS;

– If the UE is configured with an APN for XCAP only usage (pc_XCAP_only_APN==true), connectivity to this PDN is not established during the initial UE registration;

– As for any 2^nd PDN connectivity request security protection is already established the UE provides a valid APN in the PDN CONNECTIVITY REQUEST.

In detail the following UE configurations are supported:

Configuration	Condition	Explanation
IMS_Only	pc_IMS AND NOT pc_Provide_Internet_as_second_APN AND NOT pc_Provide_IMS_as_second_APN	UE is configured to request for IMS PDN connectivity only
Internet_Only	NOT pc_IMS	UE does not support IMS
IMS_Internet	pc_IMS AND pc_Provide_Internet_as_second_APN	UE is configured to request for IMS PDN connectivity first and then to request for an internet PDN connectivity
Internet_IMS	pc_IMS AND pc_Provide_IMS_as_second_APN	UE is configured to request for an internet PDN connectivity first and then to request for the IMS PDN connectivity
NOTE 1: pc_Provide_Internet_as_second_APN and pc_Provide_IMS_as_second_APN are mutually exclusive i.e. shall not be true at the same time. NOTE 2: IMS_Only configuration is not considered for EN-DC test cases defined in TS 38.523-1 [71]

Further auxiliary definitions:

Configuration	Condition
PDN1_IMS	IMS_Only OR IMS_Internet
PDN2_IMS	Internet_IMS
PDN1_INTERNET_ONLY	Internet_Only
MULTI_PDN	IMS_Internet OR Internet_IMS
XCAP_SIGNALLING	test case requires XCAP signalling
EN-DC	Applicable to EN-DC test cases defined in TS 38.523-1 [71]
NR	Applicable to NR test cases defined in TS 38.523-1 [71]

4.5.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 UICC shall be inserted. This shall contain either ISIM and USIM applications or only a USIM application on UICC.

– If RAN Assisted WLAN interworking test cases are being performed for ANDSF rules using RAN provided thresholds, ANDSF rules to match the RAN rules defined in TS 36.304 shall be available in the UE.

4.5.2.2 Definition of system information messages

The default system information messages are used.

4.5.2.3 Procedure

Table 4.5.2.3-1: UE registration procedure (state 1 to state 2)

Step	Procedure	Message Sequence
		U – S	Message
1		<–	RRC: SYSTEM INFORMATION (BCCH)
2	UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
3	SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
4	The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message. The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST	–>	RRC: RRCConnectionSetupComplete NAS: ATTACH REQUEST NAS: PDN CONNECTIVITY REQUEST
5	The SS transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure.	<–	RRC: DLInformationTransfer NAS: AUTHENTICATION REQUEST
6	The UE transmits an AUTHENTICATION RESPONSE message and establishes mutual authentication.	–>	RRC: ULInformationTransfer NAS: AUTHENTICATION RESPONSE
7	The SS transmits a NAS SECURITY MODE COMMAND message to activate NAS security.	<–	RRC: DLInformationTransfer NAS: SECURITY MODE COMMAND
8	The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration.	–>	RRC: ULInformationTransfer NAS: SECURITY MODE COMPLETE
–	EXCEPTION: Steps 9a1 to 9a2 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that take place if the UE has ESM information which needs to be transferred.	–	–
9a1	IF the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the SS transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN.	<–	RRC: DLInformationTransfer NAS: ESM INFORMATION REQUEST
9a2	The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN.	–>	RRC: ULInformationTransfer NAS: ESM INFORMATION RESPONSE
10	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
11	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
12	The SS transmits a UECapabilityEnquiry message including RAT-Type eutra to initiate the UE radio access capability transfer procedure.	<–	RRC: UECapabilityEnquiry
13	The UE transmits a UECapabilityInformation message to transfer UE radio access capability.	–>	RRC: UECapabilityInformation
–	EXCEPTION: Steps 13Aa1 to 13Aa2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation.	–	–
13Aa1	IF EN-DC OR NR THEN, the SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure.	<–	RRC: UECapabilityEnquiry
13Aa2	The UE transmits a UECapabilityInformation message to transfer UE radio access capability.	–>	RRC: UECapabilityInformation
14	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
15	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer.	–>	RRC: RRCConnectionReconfigurationComplete
–	EXCEPTION: In parallel to the event described in step 16 below, if initiated by the UE 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.	–	–
–	EXCEPTION: IF PDN1_IMS THEN in parallel to the event described in step 16 below the generic procedure for IMS signalling in the U-plane specified in subclause 4.5A.3 takes place if requested by the UE	–	–
16	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: Steps 16a1 to 16c1 describe behaviour that depends on test case requirements and UE behaviour; the "lower case letter" identifies the different branches.	–	–
16a1	IF IMS VoPS is set to ‘0’ in ATTACH ACCEPT at step 14 THEN the procedure according to Table 4.5.2.3-2 takes place	–	–
16a2-16b6	Void.	–	–
16c1	ELSE IF MULTI_PDN = TRUE THEN The generic procedure for UE establishing additional PDN connectivity as specified subclause 4.5A.16 takes place	–	–
17	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2).	<–	RRC: RRCConnectionRelease
–	EXCEPTION: Steps18a1 to 18b1 describe behaviour that depends on UE capabilities/configuration and test requirements; the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured.	–	–
18a1	IF additional PDN has been established AND (pc_XCAP_only_APN OR NOT XCAP_SIGNALLING) AND pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in TS 36.508 [2]. subclause 4.5A.17	–	–
18b1	IF additional PDN has been established AND (pc_XCAP_only_APN OR NOT XCAP_SIGNALLING) AND NOT pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in subclause 4.5A.18	–	–
NOTE 1: Void NOTE 2: Void

Table 4.5.2.3-2: Specific behaviour when IMS voice is not supported by the network

Step	Procedure	Message Sequence
		U – S	Message
–	EXCEPTION: Steps 1a1 to 1b6 describe behaviour that depends on UE configuration; the "lower case letter" identifies the different branches	–	–
1a1	IF 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
1a2	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT
1a3	The UE transmits a TRACKING AREA UPDATE COMPLETE message.	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE
1b1	ELSE IF 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
1b2	The UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
1b3	The SS transmit an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
1b4	The UE transmits an RRCConnectionSetupComplete message including a TRACKING AREA UPDATE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST
1b5	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT
1b6	The UE transmits a TRACKING AREA UPDATE COMPLETE message.	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE
2	Start Timer_1 = 5 s	–	–
–	EXCEPTION: Steps 3a1 to 3b1 describe behaviour that depends on UE behaviour; the "lower case letter" identifies the different branches	–	–
3a1	The generic procedure for UE establishing additional PDN connectivity as specified in TS 36.508 subclause 4.5A.16 takes place	–	–
3a2	Stop Timer_1	–	–
3b1	Timer_1 expires	–	–
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.

4.5.2.4 Specific message contents

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

Table 4.5.2.4-1: RRCConnectionRequest (Step 2)

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 4.5.2.4-2: UECapabilityInformation (Steps 13 and 13Aa2)

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 4.5.2.4-3: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Step 14)

Derivation Path: Table 4.7.3-6 with condition IMS_PDN_ConnEstab for PDN1_IMS and NOT IMS_PDN_ConnEstab
Information Element	Value/remark	Comment	Condition
EPS bearer identity	‘0101’B	arbitrary value used for PDN connectivity being maintained during the test case	PDN1_IMS OR (PDN2_IMS AND ImsVoPS0_NoImsPDN) OR NOT MULTI_PDN
EPS bearer identity	‘1100’B	arbitrary value used for additional PDN connectivity which may be released before entering the test procedure of the test case	MULTI_PDN AND NOT PDN1_IMS AND NOT (PDN2_IMS AND ImsVoPS0_NoImsPDN)
EPS bearer identity	‘0101’B	arbitrary value used for IMS PDN connectivity being maintained during EN-DC test case	EN-DC AND PDN1_IMS
EPS bearer identity	‘1100’B	arbitrary value used for non-IMS PDN connectivity being maintained during EN-DC test case	EN-DC AND (PDN1_INTERNET_ONLY OR PDN2_IMS)
PDN address			IPv4_address_only
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	NOT IPv4-DHCP
	0.0.0.0	DHCPv4 is to be used to allocate the IPv4 address	IPv4-DHCP
ESM cause	IF “PDN type” IE in step 4 is ‘IPv4v6’ THEN ‘00110010’B ELSE Not present	“PDN type IPv4 only allowed”

NOTE: The default message contents specified in table 4.7.3-6 apply unless the condition IPv4_address_only in table 4.5.2.4-3 is true.

Condition	Explanation
IPv4_address_only	This condition applies if the test case preamble description indicates that the UE is allocated an IPv4 address only.
IPv4-DHCP	If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message, the IE Protocol configuration options contains a configuration protocol option = ‘000B00H’ (“IPv4 address allocation via DHCPv4”, length of contents = 0). Note 1: This condition is used in conjunction with IPv4 or IPv4v6 as indicated in the “PDN address row” just above. Note 2: If both messages, PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE, are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used.
ImsVoPS0_NoImsPDN	If the test case sets IMS VoPS to 0 AND (pc_UE_NoReqIMS_IMSVoPS_0 == TRUE)

Table 4.5.2.4-4: TRACKING AREA UPDATE REQUEST (Steps 16a1 and 16b4)

Derivation Path: Table 4.7.2-27 with condition combined_TA_LA

Table 4.5.2.4-5: TRACKING AREA UPDATE ACCEPT (Steps 16a2 and 16b5)

Derivation Path: Table 4.7.2-24 with condition combined_TA_LA

4.5.2A UE Registration, UE Test Mode Activated (State 2A)

4.5.2A.0 General

IF pc_ue_CategoryDL_M1 THEN use the procedure for State 2A-CE according to clause 4.5.2AB ELSE use the procedure defined in the present clause.

The same assumptions and definitions apply as in clause 4.5.2.

4.5.2A.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.

4.5.2A.2 Definition of system information messages

The default system information messages are used.

4.5.2A.3 Procedure

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

Step	Procedure	Message Sequence
		U – S	Message
1 to 9a2	Same procedure for steps 1 to 9a2 as specified in the procedure in clause 4.5.2.3	–	–
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 including RAT-Type eutra 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
–	EXCEPTION: Steps 15Aa1 to 15Aa2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation.	–	–
15Aa1	IF EN-DC OR NR THEN the SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure.	<–	RRC: UECapabilityEnquiry
15Aa2	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 18c1 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place when the UE is configured in a certain way.	–	–
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
18c1-18c3	ELSE IF MULTI_PDN = TRUE THEN Steps from 1 to 3 from the generic procedure for UE establishing additional PDN connectivity as specified in TS 36.508 subclause 4.5A.16 takes place	–	–
–	EXCEPTION: In parallel to the event described in step 18c4 below the generic procedure for IP address allocation in the U-plane specified in subclause 4.5A.1 takes place performing IP address allocation in the U-plane if requested by the UE.	–	–
18c4	The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message	–>	RRC: ULInformationTransfer NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT
19	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2A).	<–	RRC: RRCConnectionRelease
–	EXCEPTION: Steps 20a1 to 20b1 describe behaviour that depends on UE capabilities/configuration; the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured.	–	–
20a1	IF MULTI_PDN AND pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in subclause 4.5A.17	–	–
20b1	IF MULTI_PDN AND NOT pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in subclause 4.5A.18	–	–
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.

4.5.2A.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 4.5.2A.4-1: RRCConnectionRequest (Step 2)

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 4.5.2A.4-2: UECapabilityInformation (Steps 15 and 15Aa2)

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 4.5.2A.4-3: TRACKING AREA UPDATE REQUEST (Steps 18a1 and 18b4)

Derivation Path: Table 4.7.2-27 with condition combined_TA_LA

Table 4.5.2A.4-4: TRACKING AREA UPDATE ACCEPT (Steps 18a2 and 18b5)

Derivation Path: Table 4.7.2-24 with condition combined_TA_LA

4.5.2AA UE Registration in cell supporting BL/CE UE (State 2-CE)

The same assumptions and definitions apply as in clause 4.5.2.

4.5.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.

4.5.2AA.2 Definition of system information messages

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

Table 4.5.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 4.5.2AA.2-2: SystemInformation-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-2A.

Table 4.5.2AA.2-3: SystemInformationBlockType1-BR-r13

Derivation Path: 36.508 Table 4.4.3.2-3A using condition ENHANCED COVERAGE if the BL/CE UE initial condition is intended to be in enhanced coverage; else use condition NORMAL COVERAGE.

4.5.2AA.3 Procedure

Table 4.5.2AA.3-1: UE registration procedure (state 1 to state 2-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 18b1	Same procedure for steps 2 to 18b1 as specified in the procedure in clause 4.5.2.3	–	–

4.5.2AA.4 Specific message contents

Same specific message content as in clause 4.5.2.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.

4.5.2AB UE Registration, UE Test Mode Activated in cell supporting BL/CE UE (State 2A-CE)

The same assumptions and definitions apply as in clause 4.5.2.

4.5.2AB.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.

4.5.2AB.2 Definition of system information messages

Same system information message content as in clause 4.5.2AA.2.

4.5.2AB.3 Procedure

Table 4.5.2AB.3-1: UE registration procedure (state 1 to state 2A-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 20b1	Same procedure for steps 10 to 20b1 as specified in the procedure in clause 4.5.2A.3	–	–

4.5.2AB.4 Specific message contents

Same specific message content as in clause 4.5.2A.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.

4.5.2B UE Registration, pre-registration on HRPD (State 2B)

The same assumptions and definitions apply as in clause 4.5.2.

4.5.2B.1 Initial conditions

System Simulator:

– Cell 1

– Cell 1 is transmitting SystemInformationBlockType8

User Equipment:

– The Test USIM shall be inserted.

4.5.2B.2 Definition of system information messages

Table 4.5.2B.2-1: SystemInformationBlockType1 for cell 1 (Steps 1-41, Table 4.5.2B.3-2)

Derivation Path: 36.508 Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
schedulingInformation ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {}	Combination 6 in TS 36.508 section 4.4.3.1	SIB2, SIB3 and SIB 8 are transmitted
}

Table 4.5.2B.2-2: SystemInformationBlockType8 for cell 1 (Steps 1-41, Table 4.5.2B.3-2)

Derivation Path: 36.508 Table 4.4.3.3-7, condition HRPD
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType8 ::= SEQUENCE {
parametersHRPD SEQUENCE {
preRegistrationInfoHRPD SEQUENCE {
preRegistrationAllowed	TRUE
preRegistrationZoneId	ColorCode
secondaryPreRegistrationZoneIdList SEQUENCE (SIZE (1..2)) OF SEQUENCE {	Not present
PreRegistrationZoneIdHRPD	Not present
}
}
cellReselectionParametersHRPD SEQUENCE {
bandClassList SEQUENCE (SIZE (1..maxCDMA -BandClass)) OF SEQUENCE {	1 entry
bandClass	Band Class of frequency under test	ENUMERATED {bc0, bc1, bc2, bc3, bc4, bc5, bc6, bc7, bc8, bc9, bc10, bc11, bc12, bc13, bc14, bc15, bc16, bc17, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1, …}
cellReselectionPriority	3
threshX-High	30(-30)	INTEGER (0..63)
threshX-Low	32(-32)	INTEGER (0..63)
}
neighCellList SEQUENCE (SIZE (1..16)) OF SEQUENCE {	1 entry
bandClass	Band Class of frequency under test	ENUMERATED {bc0, bc1, bc2, bc3, bc4, bc5, bc6, bc7, bc8, bc9, bc10, bc11, bc12, bc13, bc14, bc15, bc16, bc17, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1, …}
}
}
t-ReselectionCDMA2000	3	INTEGER (0..7)
}
}
}

4.5.2B.3 Procedure

Table 4.5.2B.3-1 shows the cell power levels during the procedure.

Table 4.5.2B.3-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1		Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-75		–

Table 4.5.2B.3-2: UE registration with HRPD pre-registration procedure (state 1 to state 2B)

Step	Procedure	Message Sequence
		U – S	Message
1 to 16	Same procedure for steps 1 to 16 as specified in the procedure in clause 4.5.2.3	–	–
–	EXCEPTION: IF MULTI_PDN = TRUE THEN in parallel to the events described in steps 17 to 40 below, the generic procedure for UE establishing additional PDN connectivity as specified in TS 36.508 subclause 4.5A.16 takes place
17	The UE transmits an ULInformationTransfer containing a tunneled UATIRequest message Cell 1.	–>	ULInformationTransfer
18	The SS transmits a DLInformationTransfer containing a tunneled UATIAssignment message on Cell 1.	<–	DLInformationTransfer
19	The UE transmits an ULInformationTransfer containing a tunneled UATIComplete message on Cell 1.	–>	ULInformationTransfer
20	The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenReqmessage on Cell 1.	–>	ULInformationTransfer
21	The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkOpenConfmessage on Cell 1.	<–	DLInformationTransfer
22	The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenCompleteon Cell 1.	–>	ULInformationTransfer
23	The UE transmits an ULInformationTransfer containing a tunneled ConfigurationRequest message for SCP configuration on Cell 1.	–>	ULInformationTransfer
24	The SS transmits a DLInformationTransfer containing a tunneled ConfigurationResponse message for SCP configuration on Cell 1.	<–	DLInformationTransfer
25	The UE transmits an ULInformationTransfer containing a tunneled ConfigurationRequest message for Stream protocol on Cell 1.	–>	ULInformationTransfer
26	The SS transmits a DLInformationTransfer containing a tunneled ConfigurationResponse message for Stream protocol accepting EMPA bound to service network on Cell 1.	<–	DLInformationTransfer
27	The UE transmits an ULInformationTransfer containing a tunneled EMPA ConfigurationRequest message or MMPA ConfigurationRequest message on Cell 1.	–>	ULInformationTransfer
28	The SS transmits a DLInformationTransfer containing a tunneled EMPA ConfigurationResponse message or MMPA ConfigurationResponse message on Cell 1.	<–	DLInformationTransfer
29	The UE transmits an ULInformationTransfer containing a tunneled ConfigurationComplete message on Cell 1.	–>	ULInformationTransfer
30	The SS transmits a DLInformationTransfer containing a tunneled EMPA ConfigurationRequest message or MMPA ConfigurationRequest message on Cell 1.	<–	DLInformationTransfer
30A	The UE transmits an ULInformationTransfer containing a tunneled EMPA ConfigurationResponse message or MMPA ConfigurationResponse message on Cell 1.	–>	ULInformationTransfer
30B	The SS transmits an DLInformationTransfer containing a tunneled SoftConfigurationComplete message on Cell 1.	<–	DLInformationTransfer
30C	The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkCloseReq message on Cell 1.	–>	ULInformationTransfer
30D	The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkCloseConf message on Cell 1.	<–	DLInformationTransfer
31	Optionally tunneled device level authentication may take place on Cell 1.	<–>	–
32	Optionally tunneled Location Update procedure may take place if the SS is configured to support it.	<–>	–
32A	The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenReq message on Cell 1.	–>	ULInformationTransfer
32B	The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkOpenConf message on Cell 1.	<–	DLInformationTransfer
32C	The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenComplete message on Cell 1.	–>	ULInformationTransfer
33	Tunneled PPP LCP negotiation is performed between the UE and the SS. EAP-AKA’ is selected as the authentication protocol.	<–>	–
33A	After entering PPP LCP Open State, optionally tunneled PPP Version Capability Indicaiton and/or Max PPP Inactivity Timer negotiation may take place.	<->	–
34	Tunneled EAP-AKA’ is performed between the UE and the SS.	<–>	–
35	The UE transmits an ULInformationTransfer containing a tunneled VSNCP Configure-Request message, including a PDN-ID, PDN Type, APN, PDN Address, Protocol Configuration Options, and Attach Type = “handover”. The Address Allocation Preference option contained in the Protocol Configuration Options indicates whether the UE wants to perform the IP address allocation during the attach procedure or deferred IP address allocation. PDN Type indicates the UE’s IP capability (IPv4, IPv6 or IPv4/v6)	–>	ULInformationTransfer
36	The SS transmits a DLInformationTransfer containing a tunneled VSNCP Configure-Ack message.	<–	DLInformationTransfer
37	The SS transmits a DLInformationTransfer containing a tunneled VSNCP Configure-Request message including the PDN-ID configuration option.	<–	DLInformationTransfer
38	The UE transmits an ULInformationTransfer containing a tunneled VSNCP Configure-Ack message.	–>	ULInformationTransfer
39	Optionally deferred IP address allocation using tunnelled IETF messages can take place depending on the Address Allocation Preference indicated by the UE at Step 35.	<–>
39A	The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkCloseReq message on Cell 1.	–>	ULInformationTransfer
39B	The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkCloseConf message on Cell 1.	<–	DLInformationTransfer
40	Void
41	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease
–	EXCEPTION: Steps 42a1 to 42b1 describe behaviour that depends on UE capabilities/configuration; the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured.	–	–
42a1	IF MULTI_PDN AND pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in TS 36.508 subclause 4.5A.17	–	–
42b1	IF MULTI_PDN AND NOT pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in TS 36.508 subclause 4.5A.18	–	–
Note 1: The sequence in steps 17-40 lists important eHRPD procedures. More protocol negotiations can happen based on UE capability and SS emulation. Note 2: Message contents of tunnelled CDMA2000 messages (steps 17-40) are not checked in terms of conformance testing.

NOTE: If step 31 is performed, an alternative link establishement procedure is also performed.

4.5.2B.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 4.5.2B.4-1: RRCConnectionRequest (Step 2, Table 4.5.2B.3-2)

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 4.5.2B.4-2: UECapabilityInformation (Step13, Table 4.5.2B.3-2)

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 4.5.2B.4-3: UATI Request message (Step 17, Table 4.5.2B.3-2)

Field	Value/remark	Comment	Condition
SAPState	‘0’B	SAP Header
SessionConfigurationToken	16 bits, Set by UE
ConnectionLayerFormat	1 bit, Set by UE
ATI Record	34 bits, RATI set by UE
Reserved	‘0000’B
MessageID	‘00000000’B	UATI Request
TransactionID	8 bits, Set by UE

Table 4.5.2B.4-4: UATI Assignment message (Step 18, Table 4.5.2B.3-2)

Field	Value/remark	Comment	Condition
SAPState	‘1’B	SAP Header
SessionConfigurationToken	‘0’
ConnectionLayerFormat	1 bit, Set by SS
ATI Record	34 bits, RATI set in UATI Request
Reserved	‘0000’B
MessageID	‘00000001’B	UATI Assignment
MessageSequence	8 bits, Set by SS
Reserved1	‘0000000’B
SubnetIncluded	‘1’B
UATISubnetMask	‘1101000’B
UATI104	104 bits, Set by SS
UATIColorCode	8 bits, Set to ColorCode
UATI024	24 bits, Set by SS
UpperOldUATILength	‘0000’B
Reserved2	‘0000’B

4.5.2C UE Registration, pre-registration on 1xRTT (State 2C)

The same assumptions and definitions apply as in clause 4.5.2.

4.5.2C.1 Initial conditions

System Simulator:

– Cell 1

– Cell 1 is transmitting SystemInformationBlockType8

User Equipment:

– The Test USIM shall be inserted.

– The UE is switched OFF.

4.5.2C.2 Definition of system information messages

Table 4.5.2C.2-1: SystemInformationBlockType1 for cell 1 (Steps 1-19, Table 4.5.2C.3-2)

Derivation Path: 36.508 Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
schedulingInformation ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SEQUENCE {}	Combination 6 in TS 36.508 section 4.4.3.1	SIB2, SIB3 and SIB 8 are transmitted
}

Table 4.5.2C.2-2: SystemInformationBlockType8 for cell 1 (Steps 1-19, Table 4.5.2C.3-2)

Derivation Path: 36.508 Table 4.4.3.3-7, condition 1XRTT
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType8 ::= SEQUENCE {
parameters1XRTT SEQUENCE {
csfb-RegistrationParam1XRTT SEQUENCE {
Sid	SID under test For Signalling test cases, see table 4.4.2-4	BIT STRING (SIZE (15))
Nid	NID under test For Signalling test cases, see table 4.4.2-4	BIT STRING (SIZE (16))
multipleSID	TRUE	BOOLEAN
multipleNID	TRUE	BOOLEAN
homeReg	TRUE	BOOLEAN
foreignSIDReg	TRUE	BOOLEAN
foreignNIDReg	TRUE	BOOLEAN
parameterReg	TRUE	BOOLEAN
powerUpReg	TRUE	BOOLEAN
registrationPeriod	’0000000’	BIT STRING (SIZE (7))
registrationZone	Registration zone under test For Signalling test cases, see table 4.4.2-4	BIT STRING (SIZE (12))
totalZone	‘001’B	BIT STRING (SIZE (3))
zoneTimer	‘000’B or ‘001’B	BIT STRING (SIZE (3))
}
longCodeState1XRTT	A valid value, calculated and updated by the SS	BIT STRING (SIZE (42)) OPTIONAL
cellReselectionParameters1XRTT SEQUENCE {
bandClassList SEQUENCE (SIZE (1..maxCDMA -BandClass)) OF SEQUENCE {	1 entry
bandClass	Band Class of frequency under test	ENUMERATED {bc0, bc1, bc2, bc3, bc4, bc5, bc6, bc7, bc8, bc9, bc10, bc11, bc12, bc13, bc14, bc15, bc16, bc17, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1, …}
cellReselectionPriority	3
threshX-High	30(-30)	INTEGER (0..63)
threshX-Low	32(-32)	INTEGER (0..63)
}
}
csfb-RegistrationParam1XRTT-v920{
powerDownReg-r9	TRUE
}
}
}

4.5.2C.3 Procedure

Table 4.5.2C.3-1 shows the cell power levels after the preamble.

Table 4.5.2C.3-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1		Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-60		–

Table 4.5.2C.3-2: UE registration with 1xRTT pre-registration procedure (state 1 to state 2C)

Step	Procedure	Message Sequence
		U – S	Message
1 to 16	Same procedure for steps 1 to 16 as specified in the procedure in clause 4.5.2.3	–	–
–	EXCEPTION: IF MULTI_PDN = TRUE THEN in parallel to the events described in steps 16A to 18 below, the generic procedure for UE establishing additional PDN connectivity as specified in TS 36.508 subclause 4.5A.16 takes place
16A	The UE transmits a CSFBParametersRequestCDMA2000 on Cell 1?	–>	CSFBParametersRequestCDMA2000
16B	The SS transmits a CSFBParametersResponseCDMA2000 on Cell 1.	<–	CSFBParametersResponseCDMA2000
17	The UE transmits an ULInformationTransfer containing a 1xRTT GCSNA Encapsulated Registration message on Cell 1.	–>	ULInformationTransfer
17A	The SS transmits a DLInformationTransfer containing a GCSNA Ack message on Cell 1.	<–	DLInformationTransfer
18	The SS transmits a DLInformationTransfer containing a 1x RTT GCSNA Encapsulated Registration Accept Order on Cell 1.	<–	DLInformationTransfer
19	The SS transmits an RRCConnectionRelease message on Cell 1.	<–	RRCConnectionRelease
–	EXCEPTION: Steps 20a1 to 20b1 describe behaviour that depends on UE capabilities/configuration; the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured.	–	–
20a1	IF MULTI_PDN AND pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in TS 36.508 subclause 4.5A.17	–	–
20b1	IF MULTI_PDN AND NOT pc_UE_supports_user_initiated_PDN_disconnect THEN the non-IMS PDN shall be released as specified in TS 36.508 subclause 4.5A.18	–	–
Note: Message contents of tunnelled CDMA2000 messages (steps 17-18) are not checked in terms of conformance testing.

Table 4.5.2C.3-3: Void

4.5.2C.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 4.5.2C.4-1: RRCConnectionRequest (Step 2, Table 4.5.2C.3-2)

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 4.5.2C.4-2: UECapabilityInformation (Step 13, Table 4.5.2C.3-2)

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 4.5.2C.4-3: Void

Table 4.5.2C.4-4: Void

Table 4.5.2C.4-5: CSFBParametersResponseCDMA2000 (Step 16B, Table 4.5.2C.3-2)

Derivation Path: 36.508 Table 4.6.1-2
Information Element	Value/remark	Comment	Condition
CSFBParametersResponseCDMA2000 ::= SEQUENCE {
criticalExtensions CHOICE {
csfbParametersResponseCDMA2000-r8 SEQUENCE {
Rand	Random Challenge Data set by SS
mobilityParameters	Set according to Table 4.5.2C.4-6
}
}
}

Table 4.5.2C.4-6: mobilityParameters (CDMA2000Parameters) (Step 16B, Table 4.5.2C.3-2)

Information Element	Value/remark	Comment	Condition
RecordType	‘00000000’B
SIDIncluded	‘1’B
SID	The same as SIB8
NIDIncluded	‘1’B
NID	The same as SIB8
REG_ZONEIncluded	‘1’B
REG_ZONE	The same as SIB8
TOTAL_ZONESIncluded	‘1’B
TOTAL_ZONES	The same as SIB8
ZONE_TIMERIncluded	‘1’B
ZONE_TIMER	The same as SIB8
PACKET_ZONE_IDIncluded	‘0’B
PACKET_ZONE_ID	Not present
PZIDHystParametersIncluded	‘0’B
PZ_HYST_ENABLED	Not present
PZ_HYST_INFO_INCL	Not present
PZ_HYST_LIST_LEN	Not present
PZ_HYST_ACT_TIMER	Not present
PZ_HYST_TIMER_MUL	Not present
PZ_HYST_TIMER_EXP	Not present
P_REVIncluded	‘1’B
P_REV	’00000110’B
MIN_P_REVIncluded	‘1’B
MIN_P_REV	’00000110’B
‘0’B NEG_SLOT_CYCLE_INDEX_SUPIncluded
NEG_SLOT_CYCLE_INDEX_SUP	Not present
ENCRYPT_MODEIncluded	‘0’B
ENCRYPT_MODE	Not present
ENC_SUPPORTEDIncluded	‘0’B
ENC_SUPPORTED	Not present
SIG_ENCRYPT_SUPIncluded	‘0’B
SIG_ENCRYPT_SUP	Not present
MSG_INTEGRITY_SUPIncluded	‘0’B
MSG_INTEGRITY_SUP	Not present
SIG_INTEGRITY_SUP_INCLIncluded	‘0’B
SIG_INTEGRITY_SUP_INCL	Not present
SIG_INTEGRITY_SUPIncluded	‘0’B
SIG_INTEGRITY_SUP	Not present
AUTHIncluded	‘1’B
AUTH	‘00’B
MAX_NUM_ALT_SOIncluded	‘1’B
MAX_NUM_ALT_SO	‘000’B
USE_SYNC_IDIncluded	‘0’B
USE_SYNC_ID	Not present
MS_INIT_POS_LOC_SUP_INDIncluded	‘0’B
MS_INIT_POS_LOC_SUP_IND	Not present
MOB_QOSIncluded	‘0’B
MOB_QOS	Not present
BAND_CLASS_INFO_REQIncluded	‘0’B
BAND_CLASS_INFO_REQ	Not present
BAND_CLASSIncluded	‘1’B
BAND_CLASS	‘00000’B
BYPASS_REG_INDIncluded	‘0’B
BYPASS_REG_IND	Not present
‘0’B ALT_BAND_CLASSIncluded
ALT_BAND_CLASS	Not present
MAX_ADD_SERV_INSTANCEIncluded	‘0’B
MAX_ADD_SERV_INSTANCE	Not present
HOME_REGIncluded	‘1’B
HOME_REG	The same as SIB8
FOR_SID_REGIncluded	‘1’B
FOR_SID_REG	The same as SIB8
FOR_NID_REGIncluded	‘1’B
FOR_NID_REG	The same as SIB8
POWER_UP_REGIncluded	‘1’B
POWER_UP_REG	The same as SIB8
POWER_DOWN_REGIncluded	‘1’B
POWER_DOWN_REG	The same as SIB8
PARAMETER_REGIncluded	‘1’B
PARAMETER_REG	The same as SIB8
REG_PRDIncluded	‘1’B
REG_PRD	The same as SIB8
REG_DISTIncluded	‘0’B
REG_DIST	Not present
PREF_MSID_TYPEIncluded	‘1’B
PREF_MSID_TYPE	’11’B
EXT_PREF_MSID_TYPEIncluded	‘0’B
EXT_PREF_MSID_TYPE	Not present
MEID_REQDIncluded	‘0’B
MEID_REQD	Not present
MCCIncluded	‘1’B
MCC	See the Table 4.4.2-4 Note 1, Note 2
IMSI_11_12Included	‘1’B
IMSI_11_12	See the Table 4.4.2-4 Note 1, Note 2
IMSI_T_SUPPORTEDIncluded	‘1’B
IMSI_T_SUPPORTED	’0’B
RECONNECT_MSG_INDIncluded	‘0’B
RECONNECT_MSG_IND	Not present
RER_MODE_SUPPORTEDIncluded	‘0’B
RER_MODE_SUPPORTED	Not present
TKZ_MODE_SUPPORTEDIncluded	‘0’B
TKZ_MODE_SUPPORTED	Not present
TKZ_IDIncluded	‘0’B
TKZ_ID	Not present
PILOT_REPORTIncluded PILOT_REPORT	‘0’B
PILOT_REPORT	Not present
SDB_SUPPORTEDIncluded	‘0’B
SDB_SUPPORTED	Not present
AUTO_FCSO_ALLOWEDIncluded	‘0’B
AUTO_FCSO_ALLOWED	Not present
SDB_IN_RCNM_INDIncluded	‘0’B
SDB_IN_RCNM_IND	Not present
FPC_FCH_Included	‘1’B
FPC_FCH_INIT_SETPT_RC3	’00011000’B
FPC_FCH_INIT_SETPT_RC4	’00011000’B
FPC_FCH_INIT_SETPT_RC5	’00011000’B
FPC_FCH_INIT_SETPT_RC11	’00000000’B
FPC_FCH_INIT_SETPT_RC12	’00000000’B
T_ADD_Included	‘0’B
T_ADD	Not present
PILOT_INC_Included	‘1’B
PILOT_INC	’0010’B
RAND_Included	‘0’B
RAND	Not present
LP_SEC_Included	‘1’B
LP_SEC	‘00000000’B
LTM_OFF_Included	‘1’B
LTM_OFF	‘000000’B
DAYLT_Included	‘1’B
DAYLT	‘0’B
GCSNAL2AckTimer_Included	‘1’B
GCSNAL2AckTimer	‘00000001’B
GCSNASequenceContextTimer_Incl uded	‘1’B
GCSNASequenceContextTimer	‘00000101’B

Table 4.5.2C.4-7: ULInformationTransfer (Step 17, Table 4.5.2C.3-2)

Derivation Path: 36.508 Table 4.6.1-25
Information Element	Value/remark	Comment	Condition
ULInformationTransfer ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
ulInformationTransfer-r8 SEQUENCE {
dedicatedInformationType CHOICE {
dedicatedInfoCDMA2000-1XRTT	Set according to Table 4.5.2C.4-8
}
}
}
}
}

Table 4.5.2C.4-8: 1xRTT GCSNA Encapsulated Registration message (Step 17, Table 4.5.2C.3-2)

Information Element	Value/remark	Comment	Condition
MessageID	‘00000001’B	GCSNA1xCircuitService message
GCSNAOption	‘00000001’B
AlternativeGCSNAOption_INCL	‘0’B
IWSIDIncl	‘0’B
AckRequired	‘1’B
StopDupDetect	‘0’B
MessageSequence	Set by UE
NumTLACEncapsulated1xL3PDU	‘00’B
Reserved	‘0000’B
1xLogicalChannel	‘0’B
1xProtocolRevision	’00000110’B
MsgType	‘00000001’B	Registration message
NumTLACHeaderRecords	‘0001’B
TLACHeaderRecordType	‘0000’B
TLACHeaderRecordLength	8 bits, Set by UE
MSID_TYPE	‘011’B
MSID_LEN	4 bits, Set by UE
MSID	Variable, Set by UE
Reserved	‘0000000’B
1xL3PDULength	16 bits, Set by UE
REG_TYPE	‘0001’B	Power up registration
SLOT_CYCLE_INDEX	‘010’B
MOB_P_REV	8 bits, Set by UE
SCM	8 bits, Set by UE
MOB_TERM	‘1’B
RETURN_CAUSE	‘1’B
QPCH_SUPPORTED	‘1’B
ENHANCED_RC	‘1’B
UZID_INCL	‘0’B

Table 4.5.2C.4-9: 1xRTT CS Registration Accept Order (Step 18, Table 4.5.2C.3-2)

Information Element	Value/remark	Comment	Condition
MessageID	‘00000001’B
GCSNAOption	‘00000001’B
AlternativeGCSNAOption_INCL	‘0’B
IWSIDIncl	‘0’B
AckRequired	‘0’B
StopDupDetect	‘0’B
MessageSequence	6 bits, Set by SS
NumTLACEncapsulated1xL3PDU	‘00’B
Reserved	‘0000’B
1xLogicalChannel	‘0’B
1xProtocolRevision	’00000110’B
MsgType	‘00000111’B	Order message
NumTLACHeaderRecords	‘0000’B
Reserved	‘000’B
1xL3PDULength	16 bits, Set by SS
ORDER	‘011011’B	Registration Accept Order
ADD_RECORD_LEN	‘001’B
ORDQ	‘00000000’B

Table 4.5.2C.4-10: ATTACH ACCEPT (Step 14, Table 4.5.2C.3-2)

Derivation Path: 36.508 clause 4.7.2
Information Element	Value/remark	Comment	Condition
EPS attach result	‘0001’B	EPS only
EMM cause	‘0001 0010’B	#18 “CS domain not available”	combined_EPS_IMSI

4.5.2D UE Registration, 2 PDN for RAN Assisted WLAN Interworking (State 2)

The same assumptions and definitions apply as in clause 4.5.2.

4.5.2D.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 UICC shall be inserted. This shall contain either ISIM and USIM applications or only a USIM application on UICC.

4.5.2D.2 Definition of system information messages

The default system information messages are used.

4.5.2D.3 Procedure

Table 4.5.2D.3-1: UE registration procedure (state 1 to state 2)

Step	Procedure	Message Sequence
		U – S	Message
1-16	Steps 1 to 16 of the generic test procedure for UE registration sub clause 4.5.2.3.	–	–
	EXCEPTION: Step17 depends on UE configuration, executed if UE does not automatically trigger additional PDN Connection.
17	Cause the UE to request connectivity to an additional PDN (see Note 1)
18-21	The generic procedure for UE establishing additional PDN connectivity as specified in TS 36.508 subclause 4.5A.16 takes place
22	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2).	<–	RRC: RRCConnectionRelease
NOTE 1: The request of connectivity to an additional PDN may be performed by MMI or AT command.

4.5.2D.4 Specific message contents

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

Table 4.5.2D.4-1: RRCConnectionRequest (Step 2)

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 4.5.2D.4-2: UECapabilityInformation (Step 13)

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 4.5.2D.4-3: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Step 14 a)

Derivation Path: Table 4.7.3-6 with condition IMS_PDN_ConnEstab for PDN1_IMS and NOT IMS_PDN_ConnEstab else
Information Element	Value/remark	Comment	Condition
EPS bearer identity	‘0101’B	arbitrary value used for PDN connectivity being maintained during the test case	PDN1_IMS OR NOT MULTI_PDN
EPS bearer identity	‘1100’B	arbitrary value used for additional PDN connectivity which may be released before entering the test procedure of the test case	MULTI_PDN AND NOT PDN1_IMS
PDN address			IPv4_address_only
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	NOT IPv4-DHCP
	0.0.0.0	DHCPv4 is to be used to allocate the IPv4 address	IPv4-DHCP
ESM cause	IF "PDN type" IE in step 4 is ‘IPv4v6’ THEN ‘00110010’B ELSE Not present	"PDN type IPv4 only allowed"
WLAN offload indication	Not present		NOT PDN1_Offload
WLAN offload indication			PDN1_Offload
WLAN offload acceptability	‘0001’B	Offloading the traffic of the PDN connection via a WLAN when in S1 mode is acceptable

NOTE: The default message contents specified in table 4.7.3-6 apply unless the condition IPv4_address_only in table 4.5.2D.4-3 is true.

Condition	Explanation
IPv4_address_only	This condition applies if the test case preamble description indicates that the UE is allocated an IPv4 address.
IPv4-DHCP	If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message, the IE Protocol configuration options contains a configuration protocol option = ‘000B00H’ ("IPv4 address allocation via DHCPv4", length of contents = 0). Note 1: This condition is used in conjunction with IPv4 or IPv4v6 as indicated in the "PDN address row" just above. Note 2: If both messages, PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE, are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used.
PDN1_Offload	This condition applies if the test execution requests the first PDN connection PDN1 to be offloaded to WLAN

Table 4.5.2D.4-4: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 19)

Derivation path: Table 4.7.3-6 with condition IMS_PDN_ConnEstab for ADD_IMS and NOT IMS_PDN_ConnEstab else and table 4.6.1-8 with condition AM-DRB-ADD(1) for ADD_IMS or with condition AM-DRB-ADD(8) else
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	‘0101’B	arbitrary value used for PDN connectivity being maintained during the test case	PDN2_IMS
EPS bearer identity	‘1100’B	arbitrary value used for additional non-IMS PDN connectivity	NOT PDN2_IMS
Procedure transaction identity	PTI-1	SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure
WLAN offload indication	Not present		PDN1_Offload
WLAN offload indication			NOT PDN1_Offload
WLAN offload acceptability	‘0001’B	Offloading the traffic of the PDN connection via a WLAN when in S1 mode is acceptable

Condition	Explanation
PDN1_Offload	This condition applies if the test execution requests the first PDN connection PDN1 to be offloaded to WLAN

4.5.3 Generic Radio Bearer Establishment (State 3)

IF pc_ue_CategoryDL_M1 THEN use the procedure for State 3-CE according to clause 4.5.3AA ELSE use the procedure defined in the present clause.

4.5.3.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Registered, Idle Mode state (State 2).

4.5.3.2 Definition of system information messages

The default system information messages are used.

4.5.3.3 Procedure

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

Table 4.5.3.3-1: Generic Radio Bearer establishment procedure (state 2 to state 3)

Step	Procedure	Message Sequence
		U – S	Message
1	Void
2	SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordLists.	<–	RRC: Paging (PCCH)
3	UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
4	SS transmit an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
5	The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message. (State3)	–>	RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST
6	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
7	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
8	The SS configures a new data radio bearer, associated with the default EPS bearer context. IF the test case using state 3 as an initial state is using N additional data radio bearers (0 ≤ N ≤ 7), the RRCConnectionReconfiguration message contains the configuration of these additional data radio bearers in the drb-ToAddModify IE and one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1+n, m) where n and m are the number of DRBs associated with dedicated EPS bearer contexts and configured respectively with RLC-AM and RLC-UM (n+m = N).	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST … ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
–	EXCEPTION: the steps 9 and 10a1 to 10a3 (if present) happen in any order.	–	–
9	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the default EPS bearer context.	–>	RRC: RRCConnectionReconfigurationComplete
10a1	IF N ≥ 1 (see step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 1st ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
10a2	IF N ≥ 2 (see step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 2nd ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
10a3	IF N ≥ 3 (see step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 3rd ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
10a4	IF N ≥ 4 (see step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 4th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
10a5	IF N ≥ 5 (see step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 5th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
10a6	IF N ≥ 6 (see step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 6th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
10a7	IF N = 7 (see step 8), the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 7th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

4.5.3.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7.

4.5.3A Generic Radio Bearer Establishment, UE Test Mode Activated (State 3A)

IF pc_ue_CategoryDL_M1 THEN use the procedure for State 3A-CE according to clause 4.5.3AB ELSE use the procedure defined in the present clause.

4.5.3A.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Registered, Idle Mode state, UE Test Mode Activated (State 2A for Signalling testing).

– The UE shall be in Registered, Idle Mode state, UE Test Mode Activated (State 2A-RF for RF and RRM testing).

– The UE shall be in Registered, Idle Mode state, UE Test Mode Activated (State 2A or State 2A-RF for UE positioning testing).

4.5.3A.2 Definition of system information messages

The default system information messages are used.

4.5.3A.3 Procedure

Same procedure as specified in the procedure in clause 4.5.3.3.

4.5.3A.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A.

4.5.3AA Generic Radio Bearer Establishment (State 3-CE)

4.5.3AA.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Registered, Idle Mode state (State 2-CE).

4.5.3AA.2 Definition of system information messages

The default system information messages as specified in clause 4.5.2AA.2.

4.5.3AA.3 Procedure

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

Step	Procedure	Message Sequence
		U – S	Message
1	Void
2 to 10a7	Same procedure for steps 2 to 10a7 as specified in the procedure in clause 4.5.3.3.	–	–

4.5.3AA.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7 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.

4.5.3AB Generic Radio Bearer Establishment, UE Test Mode Activated (State 3A-CE)

4.5.3AB.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Registered, Idle Mode state, UE Test Mode Activated (State 2A-CE for Signalling testing).

– The UE shall be in Registered, Idle Mode state, UE Test Mode Activated (State 2A-RF-CE for RF and RRM testing).

4.5.3AB.2 Definition of system information messages

The default system information messages are used as specified in clause 4.5.2AA.2.

4.5.3AB.3 Procedure

Table 4.5.3AB.3-1: UE registration procedure (State 2A-CE/2A-RF-CE to state 3A-CE)

Step	Procedure	Message Sequence
		U – S	Message
1	Void
2 to 10a7	Same procedure for steps 2 to 10a7 as specified in the procedure in clause 4.5.3.3	–	–

4.5.3AB.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A 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.

4.5.3B Generic Radio Bearer Establishment, pre-registered on HRPD (State 3B)

4.5.3B.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Registered, Idle Mode state, pre-registered on HRPD (State 2B).

4.5.3B.2 Definition of system information messages

The default system information messages are used.

4.5.3B.3 Procedure

Same procedure as specified in the procedure in clause 4.5.3.3.

4.5.3B.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A.

4.5.3C Generic Radio Bearer Establishment, pre-registered on 1xRTT (State 3C)

4.5.3C.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Registered, Idle Mode state, pre-registered on 1xRTT (State 2C).

4.5.3C.2 Definition of system information messages

The default system information messages are used.

4.5.3C.3 Procedure

Same procedure as specified in the procedure in clause 4.5.3.3.

4.5.3C.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A.

4.5.3D Generic Radio Bearer Establishment for RAN Assisted WLAN Interworking (State 3)

4.5.3D.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Registered, Idle Mode state (State 2) as per 4.5.2D establishing 2 PDN connections.

4.5.3D.2 Definition of system information messages

The default system information messages are used.

4.5.3D.3 Procedure

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

Table 4.5.3D.3-1: Generic Radio Bearer establishment procedure (state 2 to state 3)

Step	Procedure	Message Sequence
		U – S	Message
1-7	Steps 1 to 16 of the generic test procedure for Radio Bearer Establishment sub clause 4.5.3.3	–	–
8	The SS configures a 2 new data radio bearer, associated with the 2 default EPS bearer contexts. IF the test case using state 3 as an initial state is using N additional data radio bearers (0 ≤ N ≤ 7), the RRCConnectionReconfiguration message contains the configuration of these additional data radio bearers in the drb-ToAddModify IE and one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1+n, m) where n and m are the number of DRBs associated with dedicated EPS bearer contexts and configured respectively with RLC-AM and RLC-UM (n+m = N).	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST … ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
9-10a7	Steps 9 to 10a7 of the generic test procedure for Radio Bearer Establishment sub clause 4.5.3.3	–	–

4.5.3D.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7.

4.5.3E Control plane CIoT connection request (State 3-CP)

4.5.3E.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

– TS 36.508 condition CIoT-test apply.

User Equipment:

– The UE shall be in Registered, Idle Mode state (State 2 or 2-CE).

4.5.3E.2 Definition of system information messages

The default system information messages are used.

4.5.3E.3 Procedure

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

Table 4.5.3E.3-1: Generic control plane CIoT connection request procedure (state 3-CP)

Step	Procedure	Message Sequence
		U – S	Message
1	Void
2	SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordLists.	<–	RRC: Paging (PCCH)
3	UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
4	SS transmit an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
5	The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the CONTROL PLANE SERVICE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: CONTROL PLANE SERVICE REQUEST
6	The SS transmits a SERVICE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: SERVICE ACCEPT

4.5.3E.4 Specific message contents

All specific message contents shall be referred to clauses 4.6 and 4.7.

4.5.3EA Control plane CIoT connection request, UE Test Mode Activated (State 3A-CP)

4.5.3EA.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

– TS 36.508 condition CIoT-test apply.

User Equipment:

– The UE shall be in Registered, Idle Mode state (State 2A or 2A-CE).

4.5.3EA.2 Definition of system information messages

The default system information messages are used.

4.5.3EA.3 Procedure

Same procedure as specified in the procedure in clause 4.5.3E.3.

4.5.3EA.4 Specific message contents

All specific message contents shall be referred to clauses 4.6 and 4.7.

4.5.3F User plane CIoT connection request (State 3-UP)

4.5.3F.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

– TS 36.508 conditions CIoT-test and UP-CIoT applies.

User Equipment:

– The UE shall be in Registered, Idle Mode state (State 2 or 2-CE).

4.5.3F.2 Definition of system information messages

The default system information messages are used.

4.5.3F.3 Procedure

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

Table 4.5.3F.3-1: Generic user plane CIoT connection request procedure (state 3-UP)

Step	Procedure	Message Sequence
		U – S	Message
1	Void
2	SS sends a Paging message to the UE on the appropriate paging block, and including the UE identity in one entry of the IE pagingRecordLists.	<–	RRC: Paging (PCCH)
3	UE transmits an RRCConnectionResumeRequest message.	–>	RRC: RRCConnectionResumeRequest
4	SS transmit an RRCConnectionResume message.	<–	RRC: RRCConnectionResume
5	The UE transmits an RRCConnectionResumeComplete message.	–>	RRC: RRCConnectionResumeComplete

4.5.3F.4 Specific message contents

All specific message contents shall be referred to clauses 4.6 and 4.7.

4.5.3FA User plane CIoT connection request, UE Test Mode Activated (State 3A-UP)

4.5.3FA.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

– TS 36.508 conditions CIoT-test and UP-CIoT applies.

User Equipment:

– The UE shall be in Registered, Idle Mode state (State 2 or 2-CE).

4.5.3FA.2 Definition of system information messages

The default system information messages are used.

4.5.3FA.3 Procedure

Same procedure as specified in the procedure in clause 4.5.3F.3.

4.5.3FA.4 Specific message contents

All specific message contents shall be referred to clauses 4.6 and 4.7.

4.5.4 Loopback Activation (State 4)

IF pc_ue_CategoryDL_M1 THEN use the procedure for State 4-CE according to clause 4.5.4A ELSE use the procedure defined in the present clause.

4.5.4.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

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

4.5.4.2 Definition of system information messages

The default system information messages are used.

4.5.4.3 Procedure

Table 4.5: 4.3-1: Loopback activation procedure (state 3A to state 4)

Step	Procedure	Direction	Message Sequence
		UE – SS	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 (State 4).	–>	RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE

4.5.4.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7A.

4.5.4A Loopback Activation in cell supporting BL/CE UE (State 4-CE)

4.5.4A.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Generic RB Established, UE Test Mode Activated, Cell supporting BL/CE UE, UE Test Mode Activated (State 3A-CE).

4.5.4A.2 Definition of system information messages

Same system information message content as in clause 4.5.2AA.2.

4.5.4A.3 Procedure

Table 4.5.4A.3-1: Loopback activation procedure (state 2A-CE to state 4-CE)

Step	Procedure	Direction	Message Sequence
		UE – SS	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 (State 4).	–>	RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE

4.5.4A.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7A.

4.5.4B Loopback Activation user plane (State 4A-UP)

4.5.4B.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

– TS 36.508 conditions CIoT-test and UP-CIoT applies.

User Equipment:

– User plane CIoT connection request, UE Test Mode Activated (State 3A-UP).

4.5.4B.2 Definition of system information messages

The default system information messages are used.

4.5.4B.3 Procedure

Same procedure as specified in the procedure in clause 4.5.4A.3.

4.5.4B.4 Specific message contents

All specific message contents shall be referred to clauses 4.6 and 4.7.

4.5.5 HRPD registration (State H2)

Editor’s note: The default parameter and system information will depend on progress in Clause 4.4, once it is finalised RAN5 can refer to them accordingly.

4.5.5.1 Initial conditions

System Simulator:

– Cell 1 and Cell 15.

– Cell 1 has a lower reselection priority than Cell 15.

– Cell 15 is transmitting default overhead messages.

User Equipment:

– The Test USIM shall be inserted (State 1).

4.5.5.2 Definition of system information messages

The default overhead messages as specified in clause 4.4 are used.

4.5.5.3 Procedure

Editor note: procedure needs to be specified.

4.5.5.4 Specific message contents

Editor’s note: message contents need to be specified where necessary.

4.5.5A HRPD registration, pre-registration on E-UTRAN (State H2A)

Editor’s note: The default parameter and system information will depend on progress in Clause 4.4, once it is finalised RAN5 can refer to them accordingly.

4.5.5A.1 Initial conditions

System Simulator:

– Cell 1 and Cell 15.

– Cell 1 has a lower reselection priority than Cell 15.

– Cell 15 is transmitting default overhead messages.

User Equipment:

– The Test USIM shall be inserted (State 1).

4.5.5A.2 Definition of system information messages

The default overhead messages as specified in clause 4.4 are used.

4.5.5A.3 Procedure

Editor’s note: procedure needs to be specified.

4.5.5A.4 Specific message contents

Editor’s note: message contents need to be specified where necessary.

4.5.6 HRPD session establishment (State H3)

Editor’s note: The default parameter and system information will depend on progress in Clause 4.4, once it is finalised RAN5 can refer to them accordingly.

4.5.6.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in HRPD Registered, Dormant Mode state (State H2).

4.5.6.2 Definition of system information messages

The default overhead messages as specified in clause 4.4 are used.

4.5.6.3 Procedure

Editor’s note: procedure needs to be specified.

4.5.6.4 Specific message contents

Editor’s note: message contents need to be specified where necessary.

4.5.6A HRPD session establishment, pre-registered on E-UTRAN (State H3A)

Editor’s note: The default parameter and system information will depend on progress in Clause 4.4, once it is finalised RAN5 can refer to them accordingly.

4.5.6A.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in HRPD Registered, Dormant Mode, pre-registered on E-UTRAN state (State H2A).

4.5.6A.2 Definition of system information messages

The default overhead messages as specified in clause 4.4 are used.

4.5.6A.3 Procedure

Same procedure as specified in the procedure in clause 4.5.6.3

4.5.6A.4 Specific message contents

Editor’s note: message contents need to be specified where necessary.

4.5.7 Out of Coverage (State 5)

Out of coverage UE operation is applicable only for sidelink direct communication. In this case UE uses preconfigured radio parameters for transmission and reception of side link direct communication. UE remains in any cell selection state.

4.5.7.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

– The procedure shall be performed under the condition that there is no reference signal and SIB transmission by the cell.

User Equipment:

– The Test UICC shall be inserted. This shall contain either ISIM and USIM applications or only a USIM application on UICC.

4.5.7.2 Definition of system information messages

MIB and SIBs are not transmitted.

4.5.7.3 Procedure

UE remains in any cell selection state and search for any available cell.

4.5.8 Out of Coverage, V2X setup (State 5-V2X)

4.5.8.1 Initial conditions

System Simulator:

– No E-UTRA cell configured

– 1 GNSS simulator

– 1 simulated V2V UE (transmitter or receiver according to specific test case configuration)

User Equipment:

– If supported by the UE, the Test UICC shall be inserted. This shall contain either ISIM and USIM applications or only a USIM application on UICC.

4.5.8.2 Definition of system information messages

None.

4.5.8.3 Procedure

UE remains in any cell selection state and search for any available cell.

4.5.9 Out of Coverage, Test Loopback Activation, V2X setup (State 5A-V2X)

The same assumptions and definitions apply as in clause 4.5.8. State 5A-V2X shall be invoked either in Receive Mode or in Transmit Mode, depending on the test purpose.

4.5.9.1 Initial conditions

System Simulator:

– No E-UTRA cell configured

– 1 GNSS simulator

– 1 simulated V2X UE (transmitter or receiver according to specific test case configuration)

User Equipment:

– The UE shall be in Out of Coverage, V2X setup state (State 5-V2X)

4.5.9.2 Definition of system information messages

None.

4.5.9.3 Procedure

Table 4.5.9.3-1: Out of Coverage, Test Loopback Activation, V2X setup procedure (state 5-V2X to state 5A-V2X)

Step	Procedure	Message Sequence
		U – S	Message
1	Trigger UE to activate UE test loop mode. NOTE: The activation of UE test loop mode may be performed by MMI or AT command (+CATM).	–	–
2A	Trigger UE to close UE test loop back mode E (Receive Mode). NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE)	–	–
2B	Trigger UE to close UE test loop back mode E (Transmit Mode). NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE)	–	–
3	Trigger UE to reset or clear the current UTC time that has been calculated from GNSS. NOTE: The UTC time can be reset or clear on the UE using AT command (+CUTCR).	–	–
Note 1: If State 5A-V2X was invoked in Receive Mode use Step 2A; if State 5A-V2X was invoked in Transmit Mode use Step 2B.

4.5.9.4 Specific message contents

All specific message contents shall be referred to clause 4.7I with the exceptions below.

Table 4.5.9.4-1: AT COMMAND: +CATM (Step 1)

Derivation Path: Table 4.7I-1: +CATM with condition Activation

Table 4.5.9.4-2A: AT COMMAND: +CCUTLE (Step 2A)

Derivation Path: Table 4.7I-2: +CCUTLE with condition Close and Receive.

Table 4.5.9.4-2B: AT COMMAND: +CCUTLE (Step 2B)

Derivation Path: Table 4.7I-2: +CCUTLE with condition Close and Transmit.

Table 4.5.9.4-3: AT COMMAND: +CUTCR (Step 3)

Derivation Path: Table 4.7I-3: +CUTCR