8.1.6 Direct Transfer

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

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

8.1.6.1 Direct Transfer in CELL DCH state (invalid message reception and no signalling connection exists)

8.1.6.1.1 Definition

8.1.6.1.2 Conformance requirement

If the UE receives a DOWNLINK DIRECT TRANSFER message, and the signalling connection identified with the IE "CN domain identity" does not exist according to the variable ESTABLISHED_SIGNALLING_CONNECTIONS, the UE shall:

1> ignore the content of the DOWNLINK DIRECT TRANSFER message;

1> transmit an RRC STATUS message on the uplink DCCH using AM RLC;

1> include the IE "Identification of received message"; and

1> set the IE "Received message type" to DOWNLINK DIRECT TRANSFER; and

1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the DOWNLINK DIRECT TRANSFER message in the table "Accepted transactions" in the variable TRANSACTIONS; and

1> clear that entry;

1> include the IE "Protocol error information" with the IE "Protocol error cause" set to "Message not compatible with receiver state".

…

If the UE receives a DOWNLINK DIRECT TRANSFER message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to TS 25.331 clause 9, the UE shall perform procedure specific error handling as follows:

1> transmit an RRC STATUS message on the uplink DCCH using AM RLC;

1> include the IE "Identification of received message"; and

1> set the IE "Received message type" to DOWNLINK DIRECT TRANSFER; and

1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the DOWNLINK DIRECT TRANSFER message in the table "Rejected transactions" in the variable TRANSACTIONS; and

1> clear that entry;

1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION.

When the RRC STATUS message has been submitted to lower layers for transmission, the UE shall:

1> continue with any ongoing processes and procedures as if the DOWNLINK DIRECT TRANSFER message has not been received.

…

If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, containing an undefined critical message extension, the UE shall:

1> set the variable PROTOCOL_ERROR_REJECT to TRUE;

1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Message extension not comprehended";

Reference

3GPP TS 25.331 clause 8.1.9.3a, 8.1.9.4, 9.3b.

8.1.6.1.3 Test purpose

To confirm that the UE transmits an RRC STATUS message on the DCCH using AM RLC if it receives a DOWNLINK DIRECT TRANSFER message with a non comprehended critical extension. To confirm that the UE transmits an RRC STATUS message on the DCCH using AM RLC if it receives a DOWNLINK DIRECT TRANSFER message which includes an invalid IE "CN domain identity".

8.1.6.1.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_DCH (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE is in the CELL_DCH state. The SS transmits an invalid DOWNLINK DIRECT TRANSFER message to the UE. The UE shall transmit an RRC STATUS message on the DCCH using AM RLC. The error type "Message extension not comprehended" shall be indicated in IE "Protocol error cause". The SS transmits a DOWNLINK DIRECT TRANSFER message that contains an invalid IE "CN domain identity" to the UE. The UE shall transmit an RRC STATUS message on the DCCH using AM RLC. The error type "Message not compatible with receiver state" shall be indicated in IE "Protocol error cause".

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			DOWNLINK DIRECT TRANSFER	See specific message content
2			RRC STATUS
3			DOWNLINK DIRECT TRANSFER	Sent from a new CN domain.
4			RRC STATUS

Specific Message Contents

DOWNLINK DIRECT TRANSFER (Step 1)

Use the same message content as found in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Critical extensions	’FF’H

RRC STATUS (Step 2)

Message content is the same as found in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Identification of received message type
– Received message type	DOWNLINK DIRECT TRANSFER
– RRC transaction identifier	0
Protocol error information
– Protocol error cause	Message extension not comprehended

DOWNLINK DIRECT TRANSFER (Step 3)

Use the same message content as found in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
CN domain identity	CS domain or PS domain as unselected domain
NAS message	Arbitrary message.

RRC STATUS (Step 4)

Message content is the same as found in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Identification of received message type
– Received message type	DOWNLINK DIRECT TRANSFER
– RRC transaction identifier	Same value in the DOWNLINK DIRECT TRANSFER message in step 3.
Protocol error information
– Protocol error cause	Message not compatible with receiver state

8.1.6.1.5 Test requirement

After step 1 the UE shall transmit an RRC STATUS message on the DCCH using AM RLC setting "Message extension not comprehended" in IE "Protocol error cause" and "DOWNLINK DIRECT TRANSFER" in IE "Received message type".

After step 3 the UE shall transmit a n RRC STATUS message on the DCCH using AM RLC setting "Message not compatible with receiver state" in IE "Protocol error cause" and "DOWNLINK DIRECT TRANSFER" in IE "Received message type".

8.1.6.2 Direct Transfer in CELL FACH state (invalid message reception and no signalling connection exists)

8.1.6.2.1 Definition

8.1.6.2.2 Conformance requirement

1> ignore the content of the DOWNLINK DIRECT TRANSFER message;

1> transmit an RRC STATUS message on the uplink DCCH using AM RLC;

1> include the IE "Identification of received message"; and

1> set the IE "Received message type" to DOWNLINK DIRECT TRANSFER; and

1> clear that entry;

1> include the IE "Protocol error information" with the IE "Protocol error cause" set to "Message not compatible with receiver state".

…

1> transmit an RRC STATUS message on the uplink DCCH using AM RLC;

1> include the IE "Identification of received message"; and

1> set the IE "Received message type" to DOWNLINK DIRECT TRANSFER; and

1> clear that entry;

1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION.

When the RRC STATUS message has been submitted to lower layers for transmission, the UE shall:

1> continue with any ongoing processes and procedures as if the DOWNLINK DIRECT TRANSFER message has not been received.

…

1> set the variable PROTOCOL_ERROR_REJECT to TRUE;

1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Message extension not comprehended";

Reference

3GPP TS 25.331 clause 8.1.9.3a, 8.1.9.4, 9.3b.

8.1.6.2.3 Test purpose

To confirm that the UE transmits an RRC STATUS message on the DCCH using AM RLC if it receives a DOWNLINK DIRECT TRANSFER message which does not include any IEs except IE "Message Type". To confirm that the UE transmits an RRC STATUS message on the DCCH using AM RLC if it receives a DOWNLINK DIRECT TRANSFER message which includes an invalid IE "CN domain identity".

8.1.6.2.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CS-DCCH_FACH (state 6-6) or PS_DCCH_FACH (state 6-8) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE is in the CELL_FACH state. The SS transmits an invalid DOWNLINK DIRECT TRANSFER message to the UE. The UE shall transmit an RRC STATUS message on the DCCH using AM RLC. The error type "Message extension not comprehended" shall be indicated in IE "Protocol error cause". The SS transmits a DOWNLINK DIRECT TRANSFER message that contains an invalid IE "CN domain identity" to the UE. The UE shall transmit an RRC STATUS message on the DCCH using AM RLC. The error type "Message not compatible with receiver state" shall be indicated in IE "Protocol error cause".

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			DOWNLINK DIRECT TRANSFER	See specific message content
2			RRC STATUS
3			DOWNLINK DIRECT TRANSFER	Sent from a new CN domain.
4			RRC STATUS

Specific Message Contents

DOWNLINK DIRECT TRANSFER (Step 1)

Use the same message content as found in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Critical extensions	‘FF’H

RRC STATUS (Step 2)

Message content is the same as found in Clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Identification of received message type
– Received message type	DOWNLINK DIRECT TRANSFER
– RRC transaction identifier	0
Protocol error information
– Protocol error cause	Message extension not comprehended

DOWNLINK DIRECT TRANSFER (Step 3)

Use the same message content as found in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
CN domain identity	CS domain or PS domain as unselected domain
NAS message	Arbitrary message.

RRC STATUS (Step 4)

Message content is the same as found in Clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Identification of received message type
– Received message type	DOWNLINK DIRECT TRANSFER
– RRC transaction identifier	Same value in the DOWNLINK DIRECT TRANSFER message in step 3.
Protocol error information
– Protocol error cause	Message not compatible with receiver state

8.1.6.2.5 Test requirement

8.1.6.3 Measurement Report on INITIAL DIRECT TRANSFER message and UPLINK DIRECT TRANSFER message

8.1.6.3.1 Definition

8.1.6.3.2 Conformance requirement

In CELL_FACH state, the UE shall:

1> include a measurement report in the IE "Measured results on RACH", as specified in the IE "Intra-frequency reporting quantity for RACH reporting" and the IE "Maximum number of reported cells on RACH" in System Information Block type 12 (or "System Information Block Type 11" if "System Information Block Type 12" is not being broadcast);

1> include in the IE "Measured results on RACH" all requested reporting quantities for cells for which measurements are reported.

Reference

3GPP TS 25.331, clause 8.1.8.2, 8.1.10.2

8.1.6.3.3 Test Purpose

To confirm that the UE reports measured results on RACH messages, if it receives IE "Intra-frequency reporting quantity for RACH reporting" and IE "Maximum number of reported cells on RACH" from System Information Block Type 11 or 12 upon a transition from idle mode to CELL_FACH state.

8.1.6.3.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: "Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4 of TS 34.108. If the UE supports both CS and PS domains, the initial UE state shall be "Registered idle mode on CS/PS" (state 7).

Related ICS/IXIT statement(s)

– Support of automatic PS attach procedure at switch on yes/no

Specific Message Content

For system information block 11 for Cell 1 (gives IE’s which are different from defaults given in 34.108 sec 6.1) to be transmitted before idle update preamble.

System Information Block type 11 (Step 1) (FDD)

Use the same message sub-type found in clause 6.1 of TS 34.108, with the following exception:

Information Element	Value/remark
SIB12 indicator	FALSE
FACH measurement occasion info	Not Present
Measurement control system information
– Use of HCS	Not used
– Cell selection and reselection quality measure	CPICH RSCP
– Intra-frequency measurement system information
– Intra-frequency measurement identity	5
– Intra-frequency cell info list
– CHOICE intra-frequency cell removal	Remove no intra-frequency cells
– New intra-frequency cells
– Intra-frequency cell id	0
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not present
– Read SFN Indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH Info
– Primary Scrambling Code	Set to same code as used for cell 1
– Primary CPICH TX power	Not Present
– TX Diversity Indicator	FALSE
– Cell selection and Re-selection info	Not present
– Intra-frequency Measurement quantity
– Filter Coefficient	0
– Measurement quantity	CPICH RSCP
– Intra-frequency measurement for RACH reporting
– SFN-SFN observed time difference	No report
– Reporting quantity	CPICH RSCP
– Maximum number of reported cells on RACH	Current cell
– Reporting information for state CELL_DCH
– Intra-frequency reporting quantity
– Reporting quantities for active set cells
– Cell synchronisation information reporting indicator	FALSE
– Cell identity reporting indicator	FALSE
– CPICH Ec/No reporting indicator	FALSE
– CPICH RSCP reporting indicator	FALSE
– Pathloss reporting indicator	FALSE
– Reporting quantities for monitored set cells
– Cell synchronisation information reporting indicator	TRUE
– Cell identity reporting indicator	FALSE
– CPICH Ec/No reporting indicator	FALSE
– CPICH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Reporting quantities for detected set cells	Not present
– Measurement Reporting Mode
– Measurement Reporting Transfer Mode	Acknowledged mode RLC
– Periodic Reporting/Event Trigger Reporting Mode	Event trigger
– CHOICE report criteria	Intra-frequency measurement reporting criteria
– Parameters required for each event
– Intra-frequency event identity	1a
– Triggering condition 1	Not Present
– Triggering condition 2	Monitored set cells
– Reporting Range Constant	29 (15 dB)
– Cells forbidden to affect reporting range	Not Present
– W	0.0
– Hysteresis	2 (1.0 dB)
– Threshold used frequency	Not Present
– Reporting deactivation threshold	0
– Replacement activation threshold	Not Present
– Time to trigger	60 ms
– Amount of reporting	Infinity
– Reporting interval	16 seconds
– Reporting Cell Status
– CHOICE reported cell	Report cells within active and/or monitored set on used frequency or within active and/or monitored set on non‑used frequency
– Maximum number of reported cells	2
– Inter-frequency measurement system information	Not Present
– Traffic volume measurement system information	Not Present

System Information Block type 11 (Step 1) (TDD)

Use the same message sub-type found in clause 6.1 of TS 34.108, with the following exception:

Information Element	Value/remark
SIB12 indicator	FALSE
FACH measurement occasion info	Not Present
Measurement control system information
– Use of HCS	Not used
– Intra-frequency measurement system information
– Intra-frequency measurement identity	5
– Intra-frequency cell info list
– CHOICE intra-frequency cell removal	Remove no intra-frequency cells
– New intra-frequency cells
– Intra-frequency cell id	0
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not present
– Read SFN Indicator	FALSE
– CHOICE mode	TDD
– Primary CCPCH Info	Set to same as used for cell 1
– Primary CPICH TX power	Not Present
– TX Diversity Indicator	FALSE
– Cell selection and Re-selection info	Not present
– Intra-frequency Measurement quantity
– Filter Coefficient	0
– Measurement quantity	PCCPCH RSCP
– Intra-frequency measurement for RACH reporting
– SFN-SFN observed time difference	No report
– Reporting quantity	PCCPCH RSCP
– Maximum number of reported cells on RACH	Current cell
– Reporting information for state CELL_DCH
– Intra-frequency reporting quantity
– Reporting quantities for active set cells
– Cell synchronisation information reporting indicator	FALSE
– Cell identity reporting indicator	FALSE
– PCCPCH RSCP reporting indicator	FALSE
– Pathloss reporting indicator	FALSE
– Reporting quantities for monitored set cells
– Cell synchronisation information reporting indicator	TRUE
– Cell identity reporting indicator	FALSE
– PCCPCH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Reporting quantities for detected set cells	Not present
– Measurement Reporting Mode
– Measurement Reporting Transfer Mode	Acknowledged mode RLC
– Periodic Reporting/Event Trigger Reporting Mode	Event trigger
– CHOICE report criteria	Intra-frequency measurement reporting criteria
– Parameters required for each event
– Intra-frequency event identity	1g
– Reporting Range Constant	29 (15 dB)
– Cells forbidden to affect reporting range	Not Present
– W	0 (0.0)
– Hysteresis	2 (1.0 dB)
– Time to trigger	60 ms
– Amount of reporting	Infinity
– Reporting interval	16 seconds
– Reporting Cell Status
– CHOICE reported cell	Report cells within active and/or monitored set on used frequency or within active and/or monitored set on non‑used frequency
– Maximum number of reported cells	2
– Inter-frequency measurement system information	Not Present
– Traffic volume measurement system information	Not Present

Test Procedure

The UE is initially in idle mode and camps on cell 1. SS prompts the operator to make an outgoing call for one of the traffic classes supported by the UE. SS and UE shall execute out going call procedure. During this procedure UE transmits INITIAL DIRECT TRANSFER and UPLINK DIRECT TRANSFER messages with IE "Measured results on RACH" which is set to measured CPICH RSCP" (for FDD) or "Primary CCPCH info" (for TDD) in the current cell. After that SS releases a RRC connection.

Expected Sequence

Step		Direction		Message	Comment
	UE		SS
1					The UE is in idle mode and camps onto cell 1.
2					SS prompts the test operator to make an outgoing call.
3		à		RRC CONNECTION REQUEST
4		ß		RRC CONNECTION SETUP	See default message content (Transition to CELL_FACH)
5		à		RRC CONNECTION SETUP COMPLETE	See default message content
6		à		INITIAL DIRECT TRANSFER ( SERVICE REQUEST )	See specific message content
7		ß		DOWNLINK DIRECT TRANSFER( AUTHENTICATION AND CIPHERING REQUEST )
8		à		UPLINK DIRECT TRANSFER( AUTHENTICATION AND CIPHERING RESPONSE )	See specific message content
9		ß		SECURITY MODE COMMAND	See default message content
10		à		SECURITY MODE COMPLETE	See default message content
11		à		UPLINK DIRECT TRANSFER( ACTIVATE PDP CONTEXT REQUEST )	See specific message content
11a		ß		DOWNLINK DIRECT TRANSFER (ACTIVATE PDP CONTEXT REJECT)	Cause set to “Activation rejected, unspecified”
A11a				UPLINK DIRECT TRANSFER (DETACH REQUEST)	This step is performed only when UE is in manual attach mode: The UE may (optionally) send a Detach Request (only Note 1).
A11b				DOWNLINK DIRECT TRANSFER (DETACH ACCEPT)	This step is performed only when UE is in manual attach mode: SS responds with DETACH ACCEPT message as a Detach Request was transmitted by the UE.
12		ß		RRC CONNECTION RELEASE	See default message content
13		à		RRC CONNECTION RELEASE COMPLETE	See default message content
Note 1: Support of automatic PS attach procedure at switch on – no

Specific Message Content

RRC CONNECTION REQUEST (Step 3) (FDD)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘CPICH RSCP’
– CPICH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

RRC CONNECTION REQUEST (Step 3) (TDD)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘PCCPCH RSCP’
– PCCPCH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

INITIAL DIRECT TRANSFER (SERVICE REQUEST) (Step 6) (FDD)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘CPICH RSCP’
– CPICH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

INITIAL DIRECT TRANSFER (SERVICE REQUEST) (Step 6) (TDD)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘PCCPCH RSCP’
– PCCPCH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

UPLINK DIRECT TRANSFER (AUTHENTICATION AND CIPHERING RESPONSE) (Step 8)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘CPICH RSCP’
– CPICH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

UPLINK DIRECT TRANSFER (AUTHENTICATION AND CIPHERING RESPONSE) (Step 8) (TDD)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘PCCPCH RSCP’
– PCCPCH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

UPLINK DIRECT TRANSFER (ACTIVATE PDP CONTEXT REQUEST) (Step 11) (FDD)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘CPICH RSCP’
– CPICH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

UPLINK DIRECT TRANSFER (ACTIVATE PDP CONTEXT REQUEST) (Step 11) (TDD)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
Measured results on RACH
– Measurement result for current cell
– CHOICE measurement quantity	Check to see if set to ‘PCCPCH RSCP’
– PCCPCH RSCP	Checked to see if set to within an acceptable range.
– Measurement results for monitored cells	Checked to see if this IE is absent.

8.1.6.3.5 Test Requirement

After step 2 the UE shall transmit a RRC CONNECTION REQUEST message which includes IE "measured results on RACH", containing the measurement value for cell 1’s CPICH RSCP (FDD mode) or PCCPCH RSCP (TDD mode).

After step 5 the UE shall transmit a INITIAL DIRECT TRANSFER ( SERVICE REQUEST) message which includes IE "measured results on RACH", containing the measurement value for cell 1’s CPICH RSCP.

After step 7 the UE shall transmit a UPLINK DIRECT TRANSFER( AUTHENTICATION AND CIPHERING RESPONSE ) message which includes IE "measured results on RACH", containing the measurement value for cell 1’s CPICH RSCP (FDD mode) or PCCPCH RSCP (TDD mode).

After step 10 the UE shall transmit a UPLINK DIRECT TRANSFER( ACTIVATE PDP CONTEXT REQUEST ) message which includes IE "measured results on RACH", containing the measurement value for cell 1’s CPICH RSCP (FDD mode) or PCCPCH RSCP (TDD mode).

8.1.6.4 UPLINK Direct Transfer (RLC re-establishment)

8.1.6.4.1 Definition

8.1.6.4.2 Conformance requirement

If signalling radio bearer RB n (where n equals to 3 or 4) was used when transmitting the UPLINK DIRECT TRANSFER message and a re-establishment of RLC on same signalling radio bearer RB n occurs before the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, the UE shall:

1> retransmit the UPLINK DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB n.

Reference

3GPP TS 25.331 clause 8.1.10.2a.

8.1.6.4.3 Test purpose

To confirm that the UE transmits a second UPLINK DIRECT TRANSFER message after the re-establishment of RLC on RB3 which occurs before the successful delivery of the first UPLINK DIRECT TRANSFER message.

8.1.6.4.4 Method of test

Initial Condition

System Simulator: 1 cell – Cell 1 is active.

UE: PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108.

Specific Message Contents

For RRC CONNECTION SETUP message to be transmitted in the initial setup, use the default message given in TS 34.108 subclause 9 with the following exceptions:

RRC CONNECTION SETUP

Information Element	Value/Remarks
Signalling RB information to setup	(AM DCCH for NAS_DT High priority)
– RB identity	Not Present
– CHOICE RLC info type
– RLC info
– CHOICE Uplink RLC mode	AM RLC
– Transmission RLC discard
– SDU discard mode	No discard
– MAX_DAT	15
– Transmission window size	128
– Timer_RST	500
– Max_RST	1
– Polling info
– Timer_poll_prohibit	1000
– Timer_poll	1000
– Poll_PDU	Not present
– Poll_SDU	1
– Last transmission PDU poll	TRUE
– Last retransmission PDU poll	TRUE
– Poll_Window	99
– Timer_poll_periodic	Not Present
– CHOICE Downlink RLC mode	AM RLC
– In-sequence delivery	TRUE
– Receiving window size	128
– Downlink RLC status info
– Timer_status_prohibit	200
– Timer_EPC	Not present
– Missing PDU indicator	TRUE
– Timer_STATUS_periodic	Not Present
– RB mapping info
– Information for each multiplexing option	2 RBMuxOptions
– RLC logical channel mapping indicator	Not Present
– Number of RLC logical channels	1
– Uplink transport channel type	DCH
– UL Transport channel identity	5
– Logical channel identity	3
– CHOICE RLC size list	Configured
– MAC logical channel priority	3
– Downlink RLC logical channel info
– Number of RLC logical channels	1
– Downlink transport channel type	DCH
– DL DCH Transport channel identity	10
– DL DSCH Transport channel identity	Not Present
– Logical channel identity	3
– RLC logical channel mapping indicator	Not Present
– Number of RLC logical channels	1
– Uplink transport channel type	RACH
– UL Transport channel identity	Not Present
– Logical channel identity	3
– CHOICE RLC size list	Explicit List
– RLC size index	According to TS 34.108 clause 6.10.2.4.1.3 for FDD, 6.10.3.4.1.3 for TDD 3.84 Mcps option or 6.11.5.4.1.3 for TDD 1.28 Mcps option or 6.11.6.4.1.3 for TDD 7.68 Mcps option (standalone 13.6 kbps signalling radio bearer)
– MAC logical channel priority	3
– Downlink RLC logical channel info
– Number of RLC logical channels	1
– Downlink transport channel type	FACH
– DL DCH Transport channel identity	Not Present
– DL DSCH Transport channel identity	Not Present
– Logical channel identity	3

Test Procedure

UE is in CELL_DCH. SS set the RLC entity for SRB3 to stop. SS requests operator to deactivate the established PDP context. Then the UE shall transmit an UPLINK DIRECT TRANSFER message on the uplink DCCH. SS does not acknowledge the AM PDUs carrying UPLINK DIRECT TRANSFER message. The SS then sends a UTRAN MOBILITY INFORMATION message on SRB1 requesting the UE to do a SRNS relocation, 5s after asking the operator to deactivate the established PDP context. The UE shall send a UTRAN MOBILITY INFORMATION CONFIRM message on SRB2. The SS set the RLC entity for SRB3 to continue upon receiving UTRAN MOBILITY INFORMATION CONFIRM message. Then UE shall retransmit an UPLINK DIRECT TRANSFER message on the uplink DCCH.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				SS set the RLC entity for SRB3 to stop. SS requests the operator to initiate a PDP context deactivation.
2			UPLINK DIRECT TRANSFER	.
3			UTRAN MOBILITY INFORMATION
4			UTRAN MOBILITY INFORMATION CONFIRM	UE sends this message on uplink DCCH on AM RLC. After the reception, SS configures RB 3 to continue.
5			UPLINK DIRECT TRANSFER	DEACTIVATE PDP CONTEXT REQUEST message is embedded in UPLINK DIRECT TRANSFER message.

Specific Message Contents

UTRAN MOBILITY INFORMATION (Step 3)

Use the same message sub-type found in [9] TS 34.108 clause 9 with the following exception:

Information Element	Value/remark
Ciphering mode info	This presence of this IE is dependent on IXIT statements in TS 34.123-2. If ciphering is indicated to be active, this IE presents with the values of the sub IEs as stated below. Else, this IE is omitted.
– Ciphering mode command	Start/restart
– Ciphering algorithm	UEA0 or UEA1. The indicated algorithm must be one of the algorithms supported by the UE as indicated in the IE "security capability" in the RRC CONNECTION SETUP COMPLETE message.
– Ciphering activation time for DPCH	(256+CFN-(CFN MOD 8 + 8))MOD 256, this IE is set to "Not present" if only PS RABs are established during the initial setup procedure.
– Radio bearer downlink ciphering activation time info
– Radio bearer activation time
– RB identity	1
– RLC sequence number	Current RLC SN + 2
– RB identity	2
– RLC sequence number	Current RLC SN + 2
– RB identity	3
– RLC sequence number	Current RLC SN + 2
– RB identity	4
– RLC sequence number	Current RLC SN + 2
– RB identity	20, this IE is set to "Not present" if PS RAB is not established during the initial setup procedure.
– RLC sequence number	Current RLC SN + 2
Integrity protection mode info
– Integrity protection mode command	Start
– Downlink integrity protection activation info	Not Present
– Integrity protection algorithm	UIA1
– Integrity protection initialisation number	SS selects an arbitrary 32 bits number for FRESH. The first/ leftmost bit of the bit string contains the most significant bit of the FRESH.
New U-RNTI
– SRNC identity	0000 0000 0010B
– S-RNTI	0000 0000 0000 0000 0001B

UTRAN MOBILITY INFORMATION CONFIRM (Step 4)

Check that the UE uses the same message sub-type found in TS 34.108 clause 9.

UPLINK DIRECT TRANSFER (Step 5)

Information Element	Value/remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
CN domain identity	PS domain
NAS message	DEACTIVATE PDP CONTEXT REQUEST
Measured results on RACH	Not checked

8.1.6.4.5 Test requirement

After step 3, the UE shall transmit UTRAN MOBILITY INFORMATION CONFIRM message using uplink DCCH on AM RLC and then retransmit UPLINK DIRECT TRANSFER message on the uplink DCCH.

8.1.6.5 Initial Direct Transfer: Inclusion of establishment cause

8.1.6.5.1 Definition

8.1.6.5.2 Conformance requirement

In the UE, the initial direct transfer procedure shall be initiated, when the upper layers request establishment of a signalling connection. This request also includes a request for the transfer of a NAS message.

Upon initiation of the initial direct transfer procedure the UE shall:

1> set the variable ESTABLISHMENT_CAUSE to the cause for establishment indicated by upper layers.

…

The UE shall, in the INITIAL DIRECT TRANSFER message:

1> set the IE "NAS message" as received from upper layers; and

1> set the IE "CN domain identity" as indicated by the upper layers; and

1> set the IE "Intra Domain NAS Node Selector" as follows:

2> derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and

2> provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:

1. Derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a valid TMSI/PTMSI is available;

2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;

3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.

1> if the variable ESTABLISHMENT_CAUSE_ is initialised:

2> set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE;

2> clear the variable ESTABLISHMENT_CAUSE.

Reference

3GPP TS 25.331 clause 8.1.8.2

8.1.6.5.3 Test purpose

To confirm that, in the case the UE wants to start a new signalling connection while the UE is already in CELL_DCH state, the UE shall include the IE “Establishment cause” in the Initial Direct Transfer message.

8.1.6.5.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: PS-DCCH DCH (state 6-10) as specified in clause 7.4 of TS 34.108.

Related ICS/IXIT statement(s)

– UE supports FDD

– UE supports PS+CS

Test Procedure

The UE has a PS radio bearer set up in CELL_DCH state. Then, the test operator is prompted to make an out-going CS call. The UE shall transmit an Initial Direct Transfer message with the IE “Establishment cause” set to “Originating conversational call”. After reception of CM Service Request message from the UE, the SS will send CM Service Reject to complete the Service Request procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				SS prompts the test operator to make an outgoing CS call.
2			INITIAL DIRECT TRANSFER ( CM SERVICE REQUEST )	The UE sets the IE “Establishment cause” to “Originating conversational call”.
3			DOWNLINK DIRECT TRANSFER ( CM SERVICE REJECT )
4			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific Message Contents

INITIAL DIRECT TRANSFER (Step 2)

Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:

Information Element	Value/remark
CN Domain Identity	CS domain
Establishment cause	Originating conversational call

8.1.6.5.5 Test requirements

At step 2, the UE shall transmit an Initial Direct Transfer message with the IE “Establishment cause” set to “Originating conversational call”.