7.2 Generic setup procedures

34.1083GPPCommon test environments for User Equipment (UE)Conformance testingRelease 15TS

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

7.2.1 UE Test States for Generic setup procedures

Figure 7.2.1.1: UE Test States for Generic setup procedures

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

Table 7.2.1.1: The UE states

		RRC	CC	MM	SM	GMM
State1	Power OFF	—–	null	null	pdp-inactive	GMM-null
State2	Registered Idle Mode on CS	idle	null	MM idle	pdp-inactive	GMM-deregistered
State3	Registered Idle Mode on PS	idle	null	null	pdp-inactive	GMM-registered
State4	Circuit Switched Connect	connected	active	MM connection active	pdp-inactive	same as previous state
State5	Packet Switched Connect	connected	null	same as previous state	pdp-active	GMM-registered
State7	Registered Idle Mode on CS/PS	idle	null	MM idle	pdp-inactive	GMM-registered

7.2.2 Registration of UE

The default procedures required to achieve the changes of state between State 1, in clause 7.2.1, and States 2, 3 and 7 are illustrated in the following clauses.

The choice of which procedure to use given a UE supporting packet services is influenced by the Network Mode of Operation being simulated by the SS and by the Operation Mode of the UE, as described in 3GPP TS 24.008 [32] clause 1.7.2.2. Table 7.2.2 shows the appropriate clause number for each combination of these two modes of operation.

Table 7.2.2: Registration Procedures for UEs Supporting Packet Services

Network Mode		NMO I	NMO II
UE Mode	PS/CS	7.2.2.3	7.2.2.4
UE Mode	PS	7.2.2.2	7.2.2.2

7.2.2.1 Registration on CS

7.2.2.1.1 Initial condition

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.2.1.2 Definition of system information messages

The default system information messages are used.

7.2.2.1.3 Procedure

Registration of UE for SS shall be established under ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	¬		SYSTEM INFORMATION (BCCH)	NW Broadcast
2			RRC CONNECTION REQUEST (CCCH)	RRC
3	¬		RRC CONNECTION SETUP (CCCH)	RRC
4			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
5			LOCATION UPDATING REQUEST	MM
6	¬		AUTHENTICATION REQUEST	MM
7			AUTHENTICATION RESPONSE	MM
8	¬		SECURITY MODE COMMAND	RRC
9			SECURITY MODE COMPLETE	RRC
10	¬		LOCATION UPDATING ACCEPT	MM
11			TMSI REALLOCATION COMPLETE	MM
12	¬		RRC CONNECTION RELEASE	RRC
13			RRC CONNECTION RELEASE COMPLETE	RRC

7.2.2.1.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.2.2 Registration on PS

7.2.2.2.1 Initial condition

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

-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 25.304 are available in the UE.

7.2.2.2.2 Definition of system information messages

The default system information messages are used.

7.2.2.2.3 Procedure

Registration of UE for SS shall be established under ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			SYSTEM INFORMATION (BCCH)	NW Broadcast
2			RRC CONNECTION REQUEST (CCCH)	RRC
3			RRC CONNECTION SETUP (CCCH)	RRC
4			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
5			ATTACH REQUEST	GMM
6			AUTHENTICATION AND CIPHERING REQUEST	GMM
7			AUTHENTICATION AND CIPHERING RESPONSE	GMM
8			SECURITY MODE COMMAND	RRC
9			SECURITY MODE COMPLETE	RRC
10			ATTACH ACCEPT	GMM
11			ATTACH COMPLETE	GMM
12			RRC CONNECTION RELEASE	RRC
13			RRC CONNECTION RELEASE COMPLETE	RRC

7.2.2.2.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.2.3 Registration on CS / PS combined environment

7.2.2.3.1 Initial condition

System Simulator:

– 1 cell operating in network operation mode I, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

– 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 25.304 are available in the UE.

7.2.2.3.2 Definition of system information messages

The default system information messages are used.

7.2.2.3.3 Procedure UE establish PS registration immediately after the UE has been switched on

Registration of UE for SS shall be established under ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	¬		SYSTEM INFORMATION (BCCH)	NW Broadcast
2	®		RRC CONNECTION REQUEST (CCCH)	RRC
3	¬		RRC CONNECTION SETUP (CCCH)	RRC
4	®		RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
5	®		ATTACH REQUEST	GMM
6	¬		AUTHENTICATION AND CIPHERING REQUEST	GMM
7	®		AUTHENTICATION AND CIPHERING RESPONSE	GMM
8	¬		SECURITY MODE COMMAND	RRC
9	®		SECURITY MODE COMPLETE	RRC
10	¬		ATTACH ACCEPT	GMM
11	®		ATTACH COMPLETE	GMM
12	¬		RRC CONNECTION RELEASE	RRC
13	®		RRC CONNECTION RELEASE COMPLETE	RRC

7.2.2.3.3a Procedure UE establish PS registration later the user decides to use the PS services

CS registration has been successfully completed and RRC connection is released, cee clause 7.2.2.1. Registration of UE for SS shall be established under ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	¬		SYSTEM INFORMATION (BCCH)	NW Broadcast
1a				The UE initiates an attach by MMI or by AT command.
2	®		RRC CONNECTION REQUEST (CCCH)	RRC
3	¬		RRC CONNECTION SETUP (CCCH)	RRC
4	®		RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
5	®		ATTACH REQUEST	GMM
6	¬		AUTHENTICATION AND CIPHERING REQUEST	GMM
7	®		AUTHENTICATION AND CIPHERING RESPONSE	GMM
8	¬		SECURITY MODE COMMAND	RRC
9	®		SECURITY MODE COMPLETE	RRC
10	¬		ATTACH ACCEPT	GMM
11	®		ATTACH COMPLETE	GMM
12	¬		RRC CONNECTION RELEASE	RRC
13	®		RRC CONNECTION RELEASE COMPLETE	RRC

7.2.2.3.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.2.4 Registration on CS / PS non-combined environment

7.2.2.4.1 Initial condition

System Simulator:

– 1 cell operating in network operation mode II, default parameters.

User Equipment:

– The UE set to Operation mode A

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.2.4.2 Definition of system information messages

The default system information messages are used.

7.2.2.4.3 Procedure

Registration of UE for SS shall be established under ideal radio conditions as defined in clause 5.

Registrations in the CS domain and in the PS domain shall execute independently. The separate registration procedures may occur sequentially or in parallel. If the procedures occur sequentially PS domain registration can be started immediately after power on or the UE can initiate PS registration by MMI or by AT command. If MMI or AT commands are used, registrations are done with two separate RRC connections. The procedures for CS and PS registration shall be as defined in clauses 7.2.2.1 and 7.2.2.2.

7.2.2.4.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.3 Call setup

7.2.3.1 Generic call set up procedure for mobile terminating circuit switched calls

7.2.3.1.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.1.2 Definition of system information messages

The default system information messages are used.

7.2.3.1.3 Procedure

The Call Set-up procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			SYSTEM INFORMATION (BCCH)	Broadcast
2			PAGING (PCCH)	Paging
3			RRC CONNECTION REQUEST (CCCH)	RRC
4			RRC CONNECTION SETUP (CCCH)	RRC
5			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
6			PAGING RESPONSE	RR
7			AUTHENTICATION REQUEST	MM
8			AUTHENTICATION RESPONSE	MM
9			SECURITY MODE COMMAND	RRC
10			SECURITY MODE COMPLETE	RRC
11			SET UP	CC (see note)
12			CALL CONFIRMED	CC
13			RADIO BEARER SETUP	RRC RAB SETUP
14			RADIO BEARER SETUP COMPLETE	RRC
15			ALERTING	CC (this message is optional)
16			CONNECT	CC
17			CONNECT ACKNOWLEDGE	CC
NOTE: The "Signal" information element is not included in the SETUP message.

7.2.3.1.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.3.2 Generic call set-up procedure for mobile originating circuit switched calls

7.2.3.2.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.2.2 Definition of system information messages

The default system information messages are used.

7.2.3.2.3 Procedure

The Call Set-up procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			SYSTEM INFORMATION (BCCH)	Broadcast
2			RRC CONNECTION REQUEST (CCCH)	RRC
3			RRC CONNECTION SETUP (CCCH)	RRC
4			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
5			CM SERVICE REQUEST	MM
6			AUTHENTICATION REQUEST	MM
7			AUTHENTICATION RESPONSE	MM
8			SECURITY MODE COMMAND	RRC
9			SECURITY MODE COMPLETE	RRC
10			SET UP	CC
11			CALL PROCEEDING	CC
12			RADIO BEARER SETUP	RRC RAB SETUP
13			RADIO BEARER SETUP COMPLETE	RRC
14			ALERTING	CC
15			CONNECT	CC
16			CONNECT ACKOWLEDGE	CC

7.2.3.2.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.3.3 Supplementary service procedures

7.2.3.3.1 Generic procedures for Multiparty call set up

7.2.3.3.1.1 General on generic procedures for Multiparty call set up

In the generic procedures for Multiparty call set up the following conventions shall apply. Subscriber A is the UE under test, and subscribers B, C, D and E are distant parties to the calls are made. The calls between the UE under test and subscriber B, C, D and E are referenced by Call A-B, Call A-C, Call A-D and Call A-E. The value of the transaction identifier for each call is arbitrary, except that each value must be different from the other ones.

7.2.3.3.1.2 Call A-B in state U10 "Active" with auxiliary state "Call held"

7.2.3.3.1.2.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.2.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.2.3 Procedure

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

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have Call A-B in state U10 "Active".	This state is achieved by the procedure given in section 7.2.3.2.
2			Make the UE to put Call A-B on hold
3			HOLD	CC
4			HOLD ACKNOWLEDGE	CC

7.2.3.3.1.2.4 Specific message contents

All Specific message contents shall be referred to clause 9 with the following exceptions.

HOLD (Step 3)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B
Message type	xx01 1000 B, bits 7 and 8 are not checked

HOLD ACKNOWLEDGE (Step 4)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B
Message type	0001 1001 B

7.2.3.3.1.3 Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U4 "Call Delivered"

7.2.3.3.1.3.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.3.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.3.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have Call A-B in state U10 "Active" with auxiliary state "Call held".	This state is achieved by the procedure given in section 7.2.3.3.1.2.
2			Make the UE attempt a call to subscriber C
3			CM SERVICE REQUEST	MM
4			CM SERVICE ACCEPT	MM
5			SET UP	CC
6			CALL PROCEEDING	CC
7			ALERTING	CC

7.2.3.3.1.3.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.3.3.1.4 Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active"

7.2.3.3.1.4.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.4.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.4.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U4 "Call Delivered" with no auxiliary state.	This state is achieved by the procedure given in section 7.2.3.3.1.3.
2			CONNECT	CC
3			CONNECT ACKOWLEDGE	CC

7.2.3.3.1.4.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.3.3.1.5 Call A-B and Call A-C in state U10 "Active" with Auxiliary state "Call in MPTY"

7.2.3.3.1.5.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.5.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.5.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state.	This state is achieved by the procedure given in section 7.2.3.3.1.4.
2			Make the UE to join Call A-B and Call A-C
3			FACILITY	CC
4			FACILITY	CC

7.2.3.3.1.5.4 Specific message contents

All Specific message contents shall be referred to clause 9 with the following exceptions.

FACILITY with Invoke component (Step 3)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B or Call A-C
Message type	xx11 1010 B, bits 7 and 8 are not checked
Facility IE
– Length of Facility IE contents	8
– Component type tag	1010 0001 B (invoke)
– Component length	6
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	arbitrary integer value.
– Operation Code tag	0000 0010 B
– Operation Code length	1
– Operation Code	0111 1100 B (BuildMPTY)
– Parameters	not present

FACILITY with Return Result component (Step 4)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in step 3
Message Type	0011 1010 B
Facility IE
– Length of Facility IE contents	5
– Component type tag	1010 0010 B (return result)
– Component length	3
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	The same value that has been used in step 3
– Operation Code tag	not present
– Operation Code length	not present
– Operation Code	not present
– Parameters	not present

7.2.3.3.1.6 Call A-B and Call A-C in state U10 "Active" with Auxiliary state "Call in MPTY, call held"

7.2.3.3.1.6.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.6.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.6.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY".	This state is achieved by the procedure given in section 7.2.3.3.1.5.
2			Make the UE to put the MultiParty call on hold
3			FACILITY	CC
4			FACILITY	CC

7.2.3.3.1.6.4 Specific message contents

All Specific message contents shall be referred to clause 9 with the following exceptions.

FACILITY with Invoke component (Step 3)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B or Call A-C
Message type	xx11 1010 B, bits 7 and 8 are not checked
Facility IE
– Length of Facility IE contents	8
– Component type tag	1010 0001 B (invoke)
– Component length	6
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	arbitrary integer value.
– Operation Code tag	0000 0010 B
– Operation Code length	1
– Operation Code	0111 1011 B (HoldMPTY)
– Parameters	not present

FACILITY with Return Result component (Step 4)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in step 3
Message Type	0011 1010 B
Facility IE
– Length of Facility IE contents	5
– Component type tag	1010 0010 B (return result)
– Component length	3
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	The same value that has been used in step 3
– Operation Code tag	not present
– Operation Code length	not present
– Operation Code	not present
– Parameters	not present

7.2.3.3.1.7 Call A-B and Call A-C in state U10 "Active" with Auxiliary state "Call in MPTY, call held" and Call A-D in state U10 "Active"

7.2.3.3.1.7.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.7.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.7.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have a held MultiParty call to two destinations (Call A-B and Call A-C). Both call states shall be U10 "Active" with auxiliary state "Call in MPTY, call held".	This state is achieved by the procedure given in section 7.2.3.3.1.6.
2			Make the UE attempt a call to subscriber D
3			CM SERVICE REQUEST	MM
4			CM SERVICE ACCEPT	MM
5			SET UP	CC
6			CALL PROCEEDING	CC
7			ALERTING	CC
8			CONNECT	CC
9			CONNECT ACKOWLEDGE	CC

7.2.3.3.1.7.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.3.3.1.8 Call A-B and Call A-C in state U10 "Active" with Auxiliary state "Call in MPTY" and Call A-D in state U10 "Active" with Auxiliary state "Call held"

7.2.3.3.1.8.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.8.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.8.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY, call held" and in addition a single call (A-D) in state U10 "Active" with no auxiliary state.	This state is achieved by the procedure given in section 7.2.3.3.1.7.
2			Make the UE to alternate between the active and held calls
3			HOLD	CC
4			FACILITY	CC
5			HOLD ACKNOWLEDGE	CC
6			FACILITY	CC

7.2.3.3.1.8.4 Specific message contents

All Specific message contents shall be referred to clause 9 with the following exceptions.

HOLD (Step 3)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-D
Message type	xx01 1000 B, bits 7 and 8 are not checked

FACILITY with Invoke component (Step 4)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B or Call A-C
Message type	xx11 1010 B, bits 7 and 8 are not checked
Facility IE
– Length of Facility IE contents	8
– Component type tag	1010 0001 B (invoke)
– Component length	6
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	arbitrary integer value.
– Operation Code tag	0000 0010 B
– Operation Code length	1
– Operation Code	0111 1010 B (RetrieveMPTY)
– Parameters	not present

HOLD ACKNOWLEDGE (Step 5)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-D
Message type	0001 1001 B

FACILITY with Return Result component (Step 6)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in step 4
Message Type	0011 1010 B
Facility IE
– Length of Facility IE contents	5
– Component type tag	1010 0010 B (return result)
– Component length	3
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	The same value that has been used in step 4
– Operation Code tag	not present
– Operation Code length	not present
– Operation Code	not present
– Parameters	not present

7.2.3.3.1.9 Call A-B, Call A-C and Call A-D in state U10 "Active" with Auxiliary state "Call in MPTY" and Call A-E in state U10 "Active" with Auxiliary state "Call held"

7.2.3.3.1.9.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.9.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.9.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			The UE is made to have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY" and in addition a single call (A-D) in state U10 "Active" with auxiliary state "Call held".	This state is achieved by the procedure given in section 7.2.3.3.1.8.
2			Make the UE to join the MultiParty call and Call A-D
3			FACILITY	CC
4			FACILITY	CC
5			Make the UE to put the MultiParty call on hold
6			FACILITY	CC
7			FACILITY	CC
8			Make the UE attempt a call to subscriber E
9			CM SERVICE REQUEST	MM
10			CM SERVICE ACCEPT	MM
11			SET UP	CC
12			CALL PROCEEDING	CC
13			ALERTING	CC
14			CONNECT	CC
15			CONNECT ACKOWLEDGE	CC
16			Make the UE to alternate between the active and held calls
17			HOLD	CC
18			FACILITY	CC
19			HOLD ACKNOWLEDGE	CC
20			FACILITY	CC

7.2.3.3.1.9.4 Specific message contents

All Specific message contents shall be referred to clause 9 with the following exceptions.

FACILITY with Invoke component (Step 3)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B, Call A-C or Call A-D
Message type	xx11 1010 B, bits 7 and 8 are not checked
Facility IE
– Length of Facility IE contents	8
– Component type tag	1010 0001 B (invoke)
– Component length	6
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	arbitrary integer value.
– Operation Code tag	0000 0010 B
– Operation Code length	1
– Operation Code	0111 1100 B (BuildMPTY)
– Parameters	not present

FACILITY with Return Result component (Step 4)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in step 3
Message Type	0011 1010 B
Facility IE
– Length of Facility IE contents	5
– Component type tag	1010 0010 B (return result)
– Component length	3
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	The same value that has been used in step 3
– Operation Code tag	not present
– Operation Code length	not present
– Operation Code	not present
– Parameters	not present

FACILITY with Invoke component (Step 6)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B, Call A-C or Call A-D
Message type	xx11 1010 B, bits 7 and 8 are not checked
Facility IE
– Length of Facility IE contents	8
– Component type tag	1010 0001 B (invoke)
– Component length	6
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	arbitrary integer value.
– Operation Code tag	0000 0010 B
– Operation Code length	1
– Operation Code	0111 1011 B (HoldMPTY)
– Parameters	not present

FACILITY with Return Result component (Step 7)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in step 6
Message Type	0011 1010 B
Facility IE
– Length of Facility IE contents	5
– Component type tag	1010 0010 B (return result)
– Component length	3
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	The same value that has been used in step 6
– Operation Code tag	not present
– Operation Code length	not present
– Operation Code	not present
– Parameters	not present

HOLD (Step 17)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-E
Message type	xx01 1000 B, bits 7 and 8 are not checked

FACILITY with Invoke component (Step 18)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-B, Call A-C or Call A-D
Message type	xx11 1010 B, bits 7 and 8 are not checked
Facility IE
– Length of Facility IE contents	8
– Component type tag	1010 0001 B (invoke)
– Component length	6
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	arbitrary integer value.
– Operation Code tag	0000 0010 B
– Operation Code length	1
– Operation Code	0111 1010 B (RetrieveMPTY)
– Parameters	not present

HOLD ACKNOWLEDGE (Step 19)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in Call A-E
Message type	0001 1001 B

FACILITY with Return Result component (Step 20)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	The same value that has been used in step 18
Message Type	0011 1010 B
Facility IE
– Length of Facility IE contents	5
– Component type tag	1010 0010 B (return result)
– Component length	3
– Invoke ID tag	0000 0010 B (invoke ID)
– Invoke ID length	1
– Invoke ID	The same value that has been used in step 18
– Operation Code tag	not present
– Operation Code length	not present
– Operation Code	not present
– Parameters	not present

7.2.3.3.1.10 Call A-B and Call A-C in state U10 "Active" with Auxiliary state "Call in MPTY" and Call A-D in state U7 "Call received"

7.2.3.3.1.10.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.3.3.1.10.2 Definition of system information messages

The default system information messages are used.

7.2.3.3.1.10.3 Procedure

The procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
	UE	SS
1			The UE is made to have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY".	This state is achieved by the procedure given in section 7.2.3.3.1.5.
			A mobile terminating call is set up between the UE and destination D (Call A-D).
2			SETUP	CC
3			CALL CONFIRMED	CC
4			ALERTING	CC

7.2.3.3.1.10.4 Specific message contents

All Specific message contents shall be referred to clause 9.

SETUP (Step 2)

Information Element	Value/remark
Protocol discriminator	0011 B (call control; call related SS messages)
Transaction identifier	A value that has not been used in Call A-B or Call A-C
Message type	0000 0101 B
BC repeat indicator	not present
Bearer capability 1	Present
– Bearer capability IEI	0000 0100 B
– Length of the bearer capability contents	1
– octet 3
– Extension	1 B
– Radio Channel Requirement	01 B
– Coding Standard	0 B
– Transfer Mode	0 B
– Information Transfer Capability	000 B
Bearer capability 2	not present
Facility	not present
Progress indicator	not present
Signal	Present
– Signal IEI	0011 0100 B
– Signal Value	0000 0111 B
Calling party BCD Number	not present
Calling party sub-Address	not present
Called party BCD Number	not present
Called party sub-Address	not present
Redirecting party BCD number	not present
Redirecting party sub-address	not present
LLC repeat indicator	not present
Low layer Compatibility I	not present
Low layer Compatibility II	not present
HLC repeat indicator	not present
High layer Compatibility i	not present
High layer Compatibility ii	not present
User-user	not present
Priority	not present
Alert	not present
Network Call Control Capabilities	not present
Cause of No CLI	not present
Backup bearer capability	not present

7.2.4 Session setup

7.2.4.1 Generic session set up procedure for mobile terminating packet switched sessions

7.2.4.1.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.4.1.2 Definition of system information messages

The default system information messages are used.

7.2.4.1.3 Procedure

The Session Set-up procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			SYSTEM INFORMATION (BCCH)	Broadcast
2			PAGING TYPE1 (PCCH)	Paging
3			RRC CONNECTION REQUEST (CCCH)	RRC
4			RRC CONNECTION SETUP (CCCH)	RRC
5			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
6			SERVICE REQUEST	GMM
7			AUTHENTICATION AND CIPHERING REQUEST	GMM
8			AUTHENTICATION AND CIPHERING RESPONSE	GMM
9			SECURITY MODE COMMAND	RRC
10			SECURITY MODE COMPLETE	RRC
11			REQUEST PDP CONTEXT ACTIVATION	SM
12			ACTIVATE PDP CONTEXT REQUEST	SM ( NOTE 1, NOTE 2)
13			RADIO BEARER SETUP	RRC RAB SETUP
14			RADIO BEARER SETUP COMPLETE	RRC
15			ACTIVATE PDP CONTEXT ACCEPT	SM

NOTE 1: The UE implemented according to the Rel-7 and earlier versions of the specification may include static PDP address. The UE implemented according to the Rel-8 and later versions of the specification shall not include the PDP address but the PDP address allocation is dynamic and shall be handled by the SS by including the IPv4 PDP address (set as per PIXIT) in the ACTIVATE PDP CONTEXT ACCEPT message. In UTRA-EUTRA test cases IPv4 and/or IPv6 address (set as per PIXIT) is included in the ACTIVATE PDP CONTEXT ACCEPT message.

NOTE 2: UEs supporting S1 mode shall indicate subscribed, interactive or background traffic class in the QoS requested. UEs not supporting S1 mode should indicate subscribed, interactive or background traffic class in the QoS requested.

NOTE 3: In RAN Assisted WLAN interworking test cases in the ACTIVATE PDP CONTEXT ACCEPT message WLAN Offload Indication is set as ‘0010’B indicating Offloading of the PDN connection is allowed.

7.2.4.1.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.4.2 Generic session set up procedure for mobile originating packet switched sessions

7.2.4.2.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE shall be operated under normal test conditions.

– The Test-USIM shall be inserted.

7.2.4.2.2 Definition of system information messages

The default system information messages are used.

7.2.4.2.3 Procedure

The Session Set-up procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			SYSTEM INFORMATION (BCCH)	Broadcast
2			RRC CONNECTION REQUEST (CCCH)	RRC
3			RRC CONNECTION SETUP (CCCH)	RRC
4			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
5			SERVICE REQUEST	GMM
6			AUTHENTICATION AND CIPHERING REQUEST	GMM
7			AUTHENTICATION AND CIPHERING RESPONSE	GMM
8			SECURITY MODE COMMAND	RRC
9			SECURITY MODE COMPLETE	RRC
10			ACTIVATE PDP CONTEXT REQUEST	SM (NOTE 1, NOTE 2)
11			RADIO BEARER SETUP	RRC RAB SETUP
12			RADIO BEARER SETUP COMPLETE	RRC
13			ACTIVATE PDP CONTEXT ACCEPT	SM

NOTE 1: The UE implemented according to the Rel-7 and earlier versions of the specification may include static PDP address. The UE implemented according to the Rel-8 and later versions of the specification shall not include the PDP address but the PDP address allocation is dynamic and shall be handled by the SS by including the IPv4 PDPaddress (set as per PIXIT) in the ACTIVATE PDP CONTEXT ACCEPT message. In UTRA-EUTRA test cases IPv4 and/or IPv6 address (set as per PIXIT) in the ACTIVATE PDP CONTEXT ACCEPT message.

NOTE 3: In RAN Assisted WLAN interworking test cases in the ACTIVATE PDP CONTEXT ACCEPT message WLAN Offload Indication is set as ‘0010’B indicating Offloading of the PDN connection is allowed.

7.2.4.2.4 Specific message contents

All Specific message contents shall be referred to clause 9.

7.2.5 IMS Emergency Call setup

7.2.5.1 Generic IMS Emergency call set up procedure for mobile originating packet switched sessions – Normal Service

7.2.5.1.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

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

– The Test-USIM shall be inserted and is capable of making Emergency Call.

7.2.5.1.2 Definition of system information messages

The default system information messages are used.

7.2.5.1.3 Procedure

The Emergency IMS Call Set-up procedure shall be performed under Ideal radio conditions as defined in clause 5.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			SYSTEM INFORMATION (BCCH)	Broadcast
2			Make the UE attempt an IMS Emergency call
3			RRC CONNECTION REQUEST (CCCH) with ‘establishmentCause’ set to ‘emergency’	NOTE 1
4			RRC CONNECTION SETUP (CCCH)	RRC
5			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
6			SERVICE REQUEST	GMM
7			SECURITY MODE COMMAND	RRC
8			SECURITY MODE COMPLETE	RRC
9			ACTIVATE PDP CONTEXT REQUEST with ‘Request Type’ set to ‘Emergency’	SM ( NOTE 2, NOTE 3)
10			RADIO BEARER SETUP	The SS establishes the AM RAB for IMS signalling
11			RADIO BEARER SETUP COMPLETE
12				EXCEPTION: In parallel to the events described in steps 15 to 21 below, the behaviour in steps 13 and 14 occurs
13				Steps 1-4 defined in annex C.20 in TS 34.229-1 [46]
14				Steps defined in annex C22 in TS 34.229-1[46]
15			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context

16			REQUEST SECONDARY PDP CONTEXT ACTIVATION	The SS requests a Secondary PDP context activation and starts timer T3385 (NOTE 4)
17			ACTIVATE SECONDARY PDP CONTEXT REQUEST	The UE requests a Secondary PDP context activation, enters the state PDP-ACTIVE-PENDING and starts timer T3380 .(NOTE 4)
18				The SS stops timer T3385
19			RADIO BEARER SETUP	The SS establishes the UM RAB for IMS voice
20			RADIO BEARER SETUP COMPLETE
21			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	The SS accepts the Secondary PDP context activation with the requested QoS

NOTE 1: The RRC establishment cause will be set to "Emergency".

NOTE 2: The UE shall not include the PDP address but the PDP address allocation is dynamic and shall be handled by the SS by including the IPv4 PDP and/or IPv6 address (set as per PIXIT) in the ACTIVATE PDP CONTEXT ACCEPT message.

NOTE 3: The UEs supporting S1 mode shall include interactive or background traffic class in the QoS requested. The UEs not supporting S1 mode should include interactive or background traffic class in the QoS requested.

NOTE 4: ‘Conversational’ is included in the QoS in the REQUEST SECONDARY PDP CONTEXT ACTIVATION and in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message sent by the UE.

7.2.5.1.4 Specific message contents

All Specific message contents shall be referred to clause 9.

Step 5: The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and

Step 6: The UE transmits the SERVICE REQUEST message.

Step 7: The SS transmits a SecurityModeCommand message to activate AS security.

Step 8: The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

Step 9: UE transmits an Activate PDP Context Request message with Request Type set to Emergency with a PDP type number "IPv4v6 address" in the Requested PDP address information element. See TS 34.229 Annex C.17

Step 10: SS sends Radio Bearer Setup message – Use the same message as specified for “Packet to CELL_DCH / E-DCH / HS-DSCH using one multiplexing option (1/1) and SRBs mapped on E-DCH/HS-DSCH”, condition A17c.

Step 19: Use the following specific message content:

RADIO BEARER SETUP

Information Element	Value/remark
Message Type
RRC transaction identifier	Arbitrarily selects an integer between 0 and 3
Integrity check info
– message authentication code	SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC message sequence number	SS provides the value of this IE, from its internal counter.
Integrity protection mode info	Not Present
Ciphering mode info	Not Present
Activation time	(256+CFN-(CFN MOD 8 + 8))MOD 256
New U-RNTI	Not Present
New C-RNTI	Not Present
New DSCH-RNTI	Not Present
New H-RNTI	‘1010 1010 1010 1010’
New Primary E-RNTI	‘1010 1010 1010 1010’
New Secondary E-RNTI	Not Present
RRC State indicator	CELL_DCH
UTRAN DRX cycle length coefficient	Not Present
CN information info	Not Present
URA identity	Not Present
RNC support for change of UE capability	Not Present
CHOICE Specification mode	Complete specification
– Signalling RB information to setup	Not Present
– RAB information for setup
– RAB info	(Conversational UM DTCH for PS domain)
– RAB identity	0000 0110B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity.
– CN domain identity	PS domain
– NAS Synchronization Indicator	Not Present
– Re-establishment timer	useT314
– RB information to setup
– RB identity	27
– PDCP info
– Support for lossless SRNS relocation	FALSE
– Max PDCP SN window size	Not present
– PDCP PDU header	Present
– Header compression information
– CHOICE algorithm type
– RFC3095
– Profiles	2 profiles
– Profile instance	1
– Profile instance	2
– Uplink
– Max_CID	15
– Downlink
– Max_CID	15
– Reverse_Decompression_Depth	0
– CHOICE RLC info type	RLC info
– CHOICE Uplink RLC mode	UM RLC
– Transmission RLC discard	Not present
– CHOICE Downlink RLC mode	UM RLC
– DL UM RLC LI size	7
– DL Reception Window Size	32
– One sided RLC re-establishment	FALSE
– Alternative E-bit interpretation	Not present
– RB mapping info
– Information for each multiplexing option	1 RBMuxOption
– RLC logical channel mapping indicator	Not Present
– Number of uplink RLC logical channels	1
– Uplink transport channel type	E-DCH
– Logical channel identity	9
– E-DCH MAC-d flow identity	4
– CHOICE RLC PDU size	Fixed size
– DDI	7
– RLC PDU size list	12 RLC PDU sizes
– RLC PDU size	96 bits
– RLC PDU size	112 bits
– RLC PDU size	144 bits
– RLC PDU size	160 bits
– RLC PDU size	176 bits
– RLC PDU size	192 bits
– RLC PDU size	208 bits
– RLC PDU size	224 bits
– RLC PDU size	288 bits
– RLC PDU size	296 bits
– RLC PDU size	312 bits
– RLC PDU size	336 bits
– Include in scheduling info	TRUE
– MAC logical channel priority	8
– Downlink RLC logical channel info
– Number of downlink RLC logical channels	1
– Downlink transport channel type	HS-DSCH
– DL DCH Transport channel identity	Not present
– DL DSCH Transport channel identity	Not present
– DL HS-DSCH MAC-d flow identity	3
– Logical channel identity	Not Present
RB information to reconfigure list	Not Present
RB information to be affected	Not Present
Downlink counter synchronization info	Not Present
PDCP ROHC target mode
– Target Mode	O-mode
UL Transport channel information for all transport channels	Not Present
Deleted UL TrCH information	Not Present
Added or Reconfigured UL TrCH information	1 E-DCH with one DCCH MAC-d flow and two DTCH MAC-d flows
– Uplink transport channel type	E-DCH
– CHOICE UL parameters	E-DCH
– UL MAC header type	Not present
– UL MAC header type	MAC-e/es
– CHOICE mode	FDD
– E-DCH Transmission Time Interval	set to 2ms if supported by the UE E-DCH category, or 10ms if the UE E-DCH category does not support 2ms TTI
– HARQ info for E-DCH
– HARQ RV Configuration	rvtable
– Added or reconfigured E-DCH MAC-d flow	(for DCCH)
– E-DCH MAC-d flow identity	1
– E-DCH MAC-d flow power offset	0
– E-DCH MAC-d flow maximum number of retransmissions	7
– E-DCH MAC-d flow multiplexing list	Not Present
– CHOICE transmission grant type	Non-scheduled grant info
– Max MAC-e PDU contents size	168 bits
– 2 ms non-scheduled transmission grant HARQ process allocation	Not Present
– Added or reconfigured E-DCH MAC-d flow	(for first DTCH)
– E-DCH MAC-d flow identity	2
– E-DCH MAC-d flow power offset	0
– E-DCH MAC-d flow maximum number of retransmissions	7
– E-DCH MAC-d flow multiplexing list	Not Present
– CHOICE transmission grant type	Scheduled grant info
– Added or reconfigured E-DCH MAC-d flow	(for second DTCH)
– E-DCH MAC-d flow identity	3
– E-DCH MAC-d flow power offset	0
– E-DCH MAC-d flow maximum number of retransmissions	7
– CHOICE transmission grant type	Scheduled grant info

DL Transport channel information common for all transport channel	Not Present
Deleted DL TrCH information	Not Present
Added or Reconfigured DL TrCH information	DCH for DCCH and HS-DSCH for 3 DTCHs
– Downlink transport channel type	DCH
– DL Transport channel identity	10
– CHOICE DL parameters	Explicit
– TFS
– CHOICE Transport channel type	Dedicated transport channels
– Dynamic Transport format information
– RLC Size	Reference to clause 6.10 Parameter Set
– Number of TBs and TTI List	(This IE is repeated for TFI number.)
– Transmission Time Interval	Not Present
– Number of Transport blocks	Reference to clause 6.10 Parameter Set
– CHOICE Logical channel list	All
– Semi-static Transport Format information
– Transmission time interval	Reference to clause 6.10 Parameter Set
– Type of channel coding	Reference to clause 6.10 Parameter Set
– Coding Rate	Reference to clause 6.10 Parameter Set
– Rate matching attribute	Reference to clause 6.10 Parameter Set
– CRC size	Reference to clause 6.10 Parameter Set
– DCH quality target
– BLER Quality value	-20 (-2.0)
– Downlink transport channel type	HS-DSCH
– DL Transport channel identity	Not Present
– CHOICE DL parameters	HS-DSCH
– HARQ Info
– Number of Processes	Reference to clause 6.10.2.4.5 Parameter Set
– CHOICE Memory Partitioning	Implicit
– CHOICE DL MAC header type	MAC-ehs
– Added or reconfigured MAC-ehs reordering queue
– MAC-ehs queue to add or reconfigure list	(three queues)

– MAC-ehs queue Id	2 (for first DTCH)
– T1	50
– MAC-ehs window size	16
– MAC-ehs queue Id	3 (for second DTCH)
– T1	50
– MAC-ehs window size	16
– DCH quality target	Not present
Frequency info
– UARFCN uplink (Nu)	Reference to clause 5.1 Test frequencies. This IE should be present, if the default duplex distance defined for the operating frequency band is not used and frequency is different from the current frequency, otherwise set to Not Present.
– UARFCN downlink (Nd)	Reference to clause 5.1 Test frequencies if frequency is different from the current frequency otherwise set to Not Present.
Maximum allowed UL TX power	33dBm
Uplink DPCH info
– Uplink DPCH power control info
– DPCCH power offset	-40 (-80dB)
– PC Preamble	1 frame
– SRB delay	7 frames
– Power Control Algorithm	Algorithm1
– TPC step size	0 (1dB)
– ACK	3
– NACK	3
– Ack-Nack repetition factor	1
– HARQ_preamble_mode	0
– Scrambling code type	Long
– Scrambling code number	0 (0 to 16777215)
– Number of DPDCH	0
– spreading factor	Not Present
– TFCI existence	FALSE
– Number of FBI bit	Not Present
– Puncturing Limit	Not Present
– Number of TPC bits	Not Present
E-DCH info
– MAC-es/e reset indicator	TRUE
– E-DPCCH info
– E-DPCCH/DPCCH power offset	0
– Happy bit delay condition	100 ms
– E-TFC Boost Info	Not Present
– E-DPDCH power interpolation	Not Present
– E-DPDCH info
– E-TFCI table index	0
– E-DCH minimum set E-TFCI	9
– Reference E-TFCIs	2 E-TFCIs
– Reference E-TFCI	11
– Reference E-TFCI PO	4
– Reference E-TFCI	83
– Reference E-TFCI PO	16
– Maximum channelisation codes	2sf4
– PLnon-max	0.84
– Scheduling Information Configuration
– Periodicity for Scheduling Info – no grant	Not present
– Periodicity for Scheduling Info – grant	Not present
– Power Offset for Scheduling Info	0
– 3-Index-Step Threshold	Not present
– 2-Index-Step Threshold	Not present
– Scheduled Transmission configuration
– 2ms scheduled transmission grant HARQ process allocation	Not present
– Serving Grant	Not present
-UL 16QAM settings	Not Present
Downlink HS-PDSCH Information
– HS-SCCH Info
– CHOICE mode	FDD
– DL Scrambling Code	Not present
– HS-SCCH Channelisation Code Information
– HS-SCCH Channelisation Code	7
– Measurement Feedback Info
– CHOICE mode	FDD
– POhsdsch	6 dB
– CQI Feedback cycle, k	4 ms
– CQI repetition factor	1
– CQI	5 (corresponds to 0dB in relative power offset)
– CHOICE mode	FDD (no data)
– Downlink 64QAM configured	TRUE
– HS-DSCH TB size table	Not present
Downlink information common for all radio links
– Downlink F-DPCH info common for all RL
– Timing Indication	Maintain
– Timing maintained Synchronization indicator	FALSE
– Downlink F-DPCH power control information
– DPC mode	0 (single)
– TPC command error rate target	0.04
– CHOICE mode	FDD
– DPCH compressed mode info	Not Present
– TX Diversity mode	None
– Default DPCH Offset Value	Not Present
– MAC-hs reset indicator	Not Present
Downlink information for each radio link list
– Downlink information for each radio link
– Choice mode	FDD
– Primary CPICH info
– Primary scrambling code	Ref. to the Default setting in clause 6.1 (FDD)
– Serving HS-DSCH radio link indicator	TRUE
– Serving E-DCH radio link indicator	TRUE
– Downlink DPCH info for each RL	Not Present
– Downlink F-DPCH info for each RL
– Primary CPICH usage for channel estimation	Primary CPICH may be used
– F-DPCH frame offset	Set to value Default DPCH Offset Value (as currently stored in SS) mod 38 400
– F-DPCH slot format	3 if UE supports enhanced F-DPCH, otherwise Not Present
– Secondary CPICH info	Not Present
– Secondary scrambling code	Not Present
– Code number	12
– TPC combination index	0
– E-AGCH Info
– E-AGCH Channelisation Code	10
– CHOICE E-HICH Information
– E-HICH Information
– Channelisation code	4
– Signature sequence	1
– CHOICE E-RGCH Information	Not Present
MBMS PL Service Restriction Information	Not Present

7.2.5.2 Generic IMS Emergency call set up procedure for mobile originating packet switched sessions – Limited Service

7.2.5.2.1 Initial conditions

System Simulator:

– 1 cell, default parameters.

User Equipment:

– The UE is in GMM-DEREGISTERED.LIMITED-SERVICE state. .

– The Test-USIM shall be inserted and is capable of making Emergency Call.

7.2.5.2.2 Definition of system information messages

The default system information messages are used, except the SIB3 contents specified in 7.2.5.2.4.

7.2.5.2.3 Procedure

The establishment of Emergency IMS Call Set-up procedure is assumed to be mobile originated.

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Make the UE attempt an IMS Emergency call
2			RRC CONNECTION REQUEST (CCCH) with ‘establishmentCause’ set to ‘emergency’
3			RRC CONNECTION SETUP (CCCH)	RRC
4			RRC CONNECTION SETUP COMPLETE (DCCH)	RRC
5			ATTACH REQUEST with Attach Type set to “Emergency Attach”	GMM
6	¬		AUTHENTICATION AND CIPHERING REQUEST	GMM
7	®		AUTHENTICATION AND CIPHERING RESPONSE	GMM
8	¬		SECURITY MODE COMMAND	RRC
9	®		SECURITY MODE COMPLETE	RRC
10	¬		ATTACH ACCEPT	GMM
11	®		ATTACH COMPLETE	GMM
12			ACTIVATE PDP CONTEXT REQUEST with ‘Request Type’ set to ‘Emergency’	SM ( NOTE 1, NOTE 2)
13			RADIO BEARER SETUP	The SS establishes the AM RAB for IMS signalling
14			RADIO BEARER SETUP COMPLETE
15				EXCEPTION: In parallel to the events described in steps 17 to 23 below, the behaviour in steps 16 occurs.
16				Steps defined in annex C22 in TS 34.229-1[46]
17			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context
18			REQUEST SECONDARY PDP CONTEXT ACTIVATION	The SS requests a Secondary PDP context activation and starts timer T3385 (NOTE 3)
19			ACTIVATE SECONDARY PDP CONTEXT REQUEST	The UE requests a Secondary PDP context activation, enters the state PDP-ACTIVE-PENDING and starts timer T3380 (NOTE 3)
20				The SS stops timer T3385
21			RADIO BEARER SETUP	The SS establishes the UM RAB for IMS voice
22			RADIO BEARER SETUP COMPLETE
23			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	The SS accepts the Secondary PDP context activation with the requested QoS

NOTE 1: The UE shall not include the PDP address but the PDP address allocation is dynamic and shall be handled by the SS by including the IPv4 and/or IPv6 PDP address (set as per PIXIT) in the ACTIVATE PDP CONTEXT ACCEPT message.

NOTE 2: The UEs supporting S1 mode shall include interactive or background traffic class in the QoS requested. The UEs not supporting S1 mode should include interactive or background traffic class in the QoS requested.

NOTE 3: ‘Conversational’ is included in the QoS in the REQUEST SECONDARY PDP CONTEXT ACTIVATION and in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message sent by the UE.

7.2.5.2.4 Specific message contents

All Specific message contents shall be referred to clause 9.

SYSTEM INFORMATION BLOCK TYPE 3 (Step 1)

The same content as in default message in TS 34.108 section 6.1.0b with the following exceptions:

Information Element	Value/remark
IMS Emergency Support Indicator	This IE specifies the support of IMS emergency call in the cell for limited service mode UE

Step 4: The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment

ATTACH REQUEST (Step 5)

Information Element	Value/remark
Attach Request message identity	Emergency Attach, Follow-on request pending
Mobile identity	IMSI

Step 8: The SS transmits a SecurityModeCommand message to activate AS security.

Step 9: The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

ATTACH ACCEPT (Step 10)

Information Element

Value/remark

Emergency number list

10 numbers (TS 24.008, 10.5.3.13)

The numbers shall be different than any of those indicated in TS 22.101 clause 10.1.1 AND the numbers stored in the USIM

Network feature support information element

Emergency bearer services supported in Iu mode, but not supported in A/Gb mode

Step 12: UE transmits a Activate PDP Context Request message with Request Type set to Emergency with a PDP type number "IPv4v6 address" in the Requested PDP address information element. See TS 34.229 Annex C.17

Step 13: SS sends Radio Bearer Setup message – Use the same message as specified in clause 7.2.5.1.4 step 10

Step 21: SS sends Radio Bearer Setup message – Use the same message as specified in clause 7.2.5.1.4 step 19.

7.2.6 IP address allocation

UE IP address is allocated during the mobile originating packet switched sessions procedure referred to 7.2.4.2.

If UE supports IPv4/IPv6 or IPv6, a full IPv6 address is allocated to UE via NAS signalling in the PDP CONTEXT ACCEPT message. Once the PDP context is established, if the UE supports IPv6 it may perform IPv6 Stateless Address Autoconfiguration. The UE sends an ICMPv6 Router Solicitation message; as response the network sends an ICMPv6 Router Advertisement message.

Depending on the UE configuration there may be unpredictable delay in the start of the Stateless Address Auto configuration procedure. A guarding time of 1.2 sec is granted within which the procedure is expected to start. If the timer expires then the test shall advance to the next specified step in the test sequence.