8.1.2 RRC Connection Establishment

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

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

8.1.2.1 RRC Connection Establishment in CELL_DCH state: Success

8.1.2.1.1 Definition

8.1.2.1.2 Conformance requirement

The UE shall initiate the procedure when upper layers in the UE requests the establishment of a signalling connection and the UE is in idle mode (no RRC connection exists).

Upon initiation of the procedure, the UE shall:

…

1> set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

1> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

1> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

1> submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH;

1> set counter V300 to 1; and

1> start timer T300 when the MAC layer indicates success or failure to transmit the message;

1> select a Secondary CCPCH according to TS 25.304;

1> start receiving all FACH transport channels mapped on the selected Secondary CCPCH.

….

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

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

1> set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY;

…

The UE shall not include the IE "UE Specific Behaviour Information 1 idle".

….

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

1> stop timer T300, and act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified otherwise in the following:

2> if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of this procedure:

…

1> if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this procedure:

2> perform the physical layer synchronization procedure A as specified in TS 25.214;

2> enter UTRA RRC connected mode, in a state according to TS 25.331 subclause 8.6.3.3;

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per TS 25.331 subclause 8.6.3.3, with the contents set as specified below:

2> set the IE "RRC transaction identifier" to:

3> the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; and

3> clear that entry.

…

2> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE radio access capability" and IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

2> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE system specific capability".

When the RRC CONNECTION SETUP COMPLETE message has been submitted to lower layers for transmission the UE shall:

1> consider the procedure to be successful;

And the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.2, 8.1.3.3 and 8.1.3.6

8.1.2.1.3 Test purpose

1. To confirm that the UE leaves the Idle Mode and correctly establishes signalling radio bearers on the DCCH.

2. To confirm that the UE indicates the requested UE radio access capabilities and UE system specific capabilities (may be used by UTRAN e.g. to configure inter RAT- measurements).

3. To confirm that the UE does not include the IE "UE Specific Behaviour Information 1 idle" in the RRC CONNECTION REQUEST message.

8.1.2.1.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by attempting to make an outgoing call. After SS receives this message, it assigns the necessary radio resources and U-RNTI to be used by the UE. SS then transmits an RRC CONNECTION SETUP message containing an IE "Initial UE Identity" that does not match the IE "Initial UE Identity" in the most recent RRC CONNECTION REQUEST message sent by the UE. UE receives the RRC CONNECTION SETUP message before timer T300 expires but discards it due to an IE "Initial UE Identity" mismatch. UE shall wait for timer T300 to time out before re-transmitting a RRC CONNECTION REQUEST message to the SS. SS again assigns the necessary radio resources and U-RNTI. SS then transmits a RRC CONNECTION SETUP message containing an IE "Initial UE Identity" that matches the IE "Initial UE Identity" in the most recent RRC CONNECTION REQUEST sent by the UE. SS then waits for the UE to transmit an RRC CONNECTION SETUP COMPLETE message on the DCCH. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST	By outgoing call operation. See specific message contents.
2			RRC CONNECTION SETUP	This message is not addressed to the UE. See specific message contents.
3			RRC CONNECTION REQUEST	UE shall re-transmit the request message again after a time out of T300 from step 1.
3a				SS checks IE "UE Specific Behaviour Information 1 idle" is not included in received RRC CONNECTION REQUEST message.
4			RRC CONNECTION SETUP	See specific message contents.
5				The UE configures the layer 2 and layer 1.
6			RRC CONNECTION SETUP COMPLETE	See specific message contents.
7			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 Content

System Information Block type 11 (FDD)

Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:

Information Element	Value/remark
– Intra-frequency reporting quantity for RACH Reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode
– FDD
– Reporting quantity	CPICH Ec/N0
– Maximum number of reported cells on RACH	current cell

System Information Block type 11 (TDD)

Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:

Information Element	Value/remark
– Intra-frequency reporting quantity for RACH Reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode	TDD
– Reporting quantity list
– Reporting quantity	P-CCPCH RSCP
– Maximum number of reported cells on RACH	current cell

RRC CONNECTION REQUEST (Step 1) (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
UE Specific Behaviour Information 1 idle	Check if this IE is absent.
Measured results on RACH	Check to see if set in accordance with the IE "Intra-frequency reporting quantity for RACH Reporting" included in SYSTEM INFORMATION BLOCK Type 11
– Measurement result for current cell
– CHOICE mode
– FDD
– CHOICE measurement quantity
– CPICH Ec/N0	The actual reported value is not checked

RRC CONNECTION REQUEST (Step 1) (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	Check to see if set in accordance with the IE "Intra-frequency reporting quantity for RACH Reporting" included in SYSTEM INFORMATION BLOCK Type 11
– Measurement result for current cell
– CHOICE mode	TDD
– CHOICE measurement quantity
– P-CCPCH RSCP	The actual reported value is not checked

RRC CONNECTION SETUP (Step 2)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Set to unmatched identity (incorrect IMSI)

RRC CONNECTION SETUP (Step 4)

Use the default message with the same message type and covering the scenario used in this test (Transition to CELL_DCH) specified in clause 9 of TS 34.108.

RRC CONNECTION SETUP COMPLETE (Step 6)

Use the default message with the same message type specified in clause 9 of TS 34.108 with the following exception.

Information Element	Value/remark
UE Radio Access Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE radio access capability extension	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE system specific Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.

8.1.2.1.5 Test requirement

After step 2 the UE shall re-transmit the RRC CONNECTION REQUEST message again in order to continue the RRC connection establishment procedure.

After step 3 the SS shall check IE "UE Specific Behaviour Information 1 idle" isn’t included in received RRC CONNECTION REQUEST message.

After step 6 the UE shall establish an RRC connection and continue the procedure of the outgoing call on the DCCH.

8.1.2.1a RRC Connection Establishment in CELL_DCH state: Success (TDD Only)

8.1.2.1a.1 Definition

The features and operation of Multi-frequency and UpPCH shifting have been introduced to core specification (TS 25.331 clause 8.6.6.1, 8.6.6.26, and 8.6.6.43) for LCR TDD.

8.1.2.1a.2 Conformance requirement

The UE shall initiate the procedure when upper layers in the UE requests the establishment of a signalling connection and the UE is in idle mode (no RRC connection exists).

Upon initiation of the procedure, the UE shall:

…

1> set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

1> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

1> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

1> submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH;

1> set counter V300 to 1; and

1> start timer T300 when the MAC layer indicates success or failure to transmit the message;

1> select a Secondary CCPCH according to TS 25.304;

1> start receiving all FACH transport channels mapped on the selected Secondary CCPCH.

….

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

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

1> set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY;

…

The UE shall not include the IE "UE Specific Behaviour Information 1 idle".

….

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

1> stop timer T300, and act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified otherwise in the following:

2> if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of this procedure:

…

1> if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this procedure:

2> perform the physical layer synchronization procedure A as specified in TS 25.214;

2> enter UTRA RRC connected mode, in a state according to TS 25.331 subclause 8.6.3.3;

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per TS 25.331 subclause 8.6.3.3, with the contents set as specified below:

2> set the IE "RRC transaction identifier" to:

3> the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; and

3> clear that entry.

…

2> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE radio access capability" and IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

2> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE system specific capability".

When the RRC CONNECTION SETUP COMPLETE message has been submitted to lower layers for transmission the UE shall:

1> consider the procedure to be successful;

And the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.2, 8.1.3.3, 8.1.3.6, 8.6.6.1and 8.6.6.43.

8.1.2.1a.3 Test purpose

1. To confirm that the UE leaves the Idle Mode and correctly establishes signalling radio bearers on the DCCH of secondary frequency according to the downlink message sent by the network.

2. To confirm that the UE indicates the requested UE radio access capabilities and UE system specific capabilities (may be used by UTRAN e.g. to configure inter RAT- measurements).

3. To confirm that the UE does not include the IE "UE Specific Behaviour Information 1 idle" in the RRC CONNECTION REQUEST message.

8.1.2.1a.4 Method of test

Initial Condition

System Simulator: 1 cell, 3 frequency (one is primary frequency, others are secondary frequency).

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

Power on the UE, UE shall initialize the access procedure after receiving all system messages (CS: Location Update procedure or PS: GPRS ATTACH procedure). UE shall send SYNC UL in the position according to the indication of Uppch in SIB3, SS return corresponding FPACH message after receiving SYNC UL to indicate UE to send physical layer parameters for RACH. Then, SS send CON_SETUP_REJ message after receive CON_SETUP_REQ from UE to notify UE to end this access procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Sync UL code	UE shall send this message according to the indication of mapping-LCR in SIB3, otherwise SS will ignore this message.
2			FPACH message	SS indicate UE sent Layer1 messages needed by RACH.
13			RRC CONNECTION REQUEST	By outgoing call operation. See specific message contents.
24			RRC CONNECTION SETUP	This message is not addressed to the UE. See specific message contents.
35			RRC CONNECTION REQUEST	UE shall re-transmit the request message again after a time out of T300 from step 13.
3a				SS checks IE "UE Specific Behaviour Information 1 idle" is not included in received RRC CONNECTION REQUEST message.
46			RRC CONNECTION SETUP	See specific message contents.
57				The UE configures the layer 2 and layer 1.
68			RRC CONNECTION SETUP COMPLETE	See specific message contents.
79			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 Content

System Information Block type 11 3 (FDD1.28Mbps TDD)

Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:

Information Element	Value/remark
-v4b0NonCriticalExtensions- Intra-frequency reporting quantity for RACH Reporting
-sysInfoType3-v4b0ext – SFN-SFN observed time difference reporting indicator	No report
-mapping-LCR – CHOICE mode	22
– FDD
– Reporting quantity	CPICH Ec/N0
– Maximum number of reported cells on RACH	current cell

System Information Block type 11 (TDD)

Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:

Information Element	Value/remark
– Intra-frequency reporting quantity for RACH Reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode	TDD
– Reporting quantity list
– Reporting quantity	P-CCPCH RSCP
– Maximum number of reported cells on RACH	current cell

RRC CONNECTION REQUEST (Step 1) (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
UE Specific Behaviour Information 1 idle	Check if this IE is absent.
Measured results on RACH	Check to see if set in accordance with the IE "Intra-frequency reporting quantity for RACH Reporting" included in SYSTEM INFORMATION BLOCK Type 11
– Measurement result for current cell
– CHOICE mode
– FDD
– CHOICE measurement quantity
– CPICH Ec/N0	The actual reported value is not checked

RRC CONNECTION REQUEST (Step 13) (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	Check to see if set in accordance with the IE "Intra-frequency reporting quantity for RACH Reporting" included in SYSTEM INFORMATION BLOCK Type 11
– Measurement result for current cell
– CHOICE mode	TDD
– CHOICE measurement quantity
– P-CCPCH RSCP	The actual reported value is not checked

RRC CONNECTION SETUP (Step 24)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Set to unmatched identity (incorrect IMSI)
Uplink DPCH info
-Uplink Timing Advance Control
-Frequency info
-UpPCH position info	22

RRC CONNECTION SETUP (Step 6)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
RRCConnectionSetup-r4-TDD128-add-ext-IEs
frequencyInfo	Secondary frequency
Uplink DPCH info
-Uplink Timing Advance Control
-UpPCH position info	22

RRC CONNECTION SETUP (Step 4)

Use the default message with the same message type and covering the scenario used in this test (Transition to CELL_DCH) specified in clause 9 of TS 34.108.

RRC CONNECTION SETUP COMPLETE (Step 68)

Use the default message with the same message type specified in clause 9 of TS 34.108 with the following exception.

Information Element	Value/remark
UE Radio Access Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE radio access capability extension	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE system specific Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.

8.1.2.1a.5 Test requirement

After step 2 4 the UE shall re-transmit the RRC CONNECTION REQUEST message again in order to continue the RRC connection establishment procedure.

After step 3 the SS shall check IE "UE Specific Behaviour Information 1 idle" isn’t included in received RRC CONNECTION REQUEST message.

After step 6 the UE shall establish an RRC connection and continue the procedure of the outgoing call on the DCCH of secondary frequency.

8.1.2.2 RRC Connection Establishment: Success after T300 timeout

8.1.2.2.1 Definition

8.1.2.2.2 Conformance requirement

If the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and

if expiry of timer T300 occurs:

the UE shall:

1> check the value of V300; and

2> if V300 is equal to or smaller than N300:

3> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

3> submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink CCCH;

3> increment counter V300;

3> restart timer T300 when the MAC layer indicates success or failure to transmit the message.

2> if V300 is greater than N300:

…

Reference

3GPP TS 25.331 clause 8.1.3.5.

8.1.2.2.3 Test purpose

To confirm that the UE retries to establish the RRC connection until V300 is greater than N300 after the expiry of timer T300 when the SS transmits no response for an RRC CONNECTION REQUEST message.

8.1.2.2.4 Method of test

Initial Condition

System Simulator: 1 cell. SCCPCH configuration as specified in 6.1.0b of TS 34.108.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

NOTE: This test requires that N300 is bigger than 0, which is the case (see default contents of SIB 1, specified in TS 34.108). Expiry of timer T300 is verified only for N300 values exceeding 1.

Test Procedure

Before the test starts, SYSTEM INFORMATION BLOCK TYPE 1, SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. and SYSTEM INFORMATION BLOCK TYPE 7 message are modified and this modification is notified to the UE. An internal counter K in SS is initialized to a value = 0. Following this, the UE shall transmit an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by use of selected PRACH from the available PRACH No.1 and PRACH No.2, after the operator attempts to make an outgoing call. SS ignores this message, increments K every time such a message is received and waits for T300 timer to expire. This cycle is repeated until K reaches N300. When K is equal to N300, the SS transmits an RRC CONNECTION SETUP message containing an IE “RRC state indicator” set to ‘CELL_PCH’ as specified in step 6 to the UE. The UE shall send another RRC CONNECTION REQUEST message on the uplink CCCH. SS replies with a valid RRC CONNECTION SETUP message. The UE shall then acknowledge the establishment of RRC connection by sending the RRC CONNECTION SETUP COMPLETE message on uplink DCCH.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1			PAGING TYPE 1	SS transmits the paging message which comprises IE "BCCH Modification Information", with the "Value Tag" different from the "MIB Value Tag" of the current Master Information Block. See specific message contents.
1a			Void
1b			MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 1 SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. SYSTEM INFORMATION BLOCK TYPE 7, SCHEDULING BLOCK 1	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. At the same time, SS starts to transmit the affected SIB TYPE 1 , SIB TYPE 5 / SIB TYPE 5bis and SIB 7messages. See specific message contents.
1c				SS waits 5s (to ensure that the UE has time to read the new system information)
2				SS initializes counter K to 0. Operator is asked to make an outgoing call and SS starts to wait for RRC CONNECTION REQUEST on uplink CCCH.
3			RRC CONNECTION REQUEST	See the clause 9 in TS 34.108 on default message content
4				SS increments K.
5				SS checks to see if K is equal to N300. If so, goes to step 6. Else, continues to execute step 3.
6			RRC CONNECTION SETUP	IE “RRC state indicator” is set to ‘CELL_PCH’.
7			RRC CONNECTION REQUEST	See specific message contents.
8			RRC CONNECTION SETUP	This is a legal message. See the clause 9 in TS 34.108 on default message content for RRC.
9				The UE configures the layer 1 and layer 2.
10			RRC CONNECTION SETUP COMPLETE	See clause 9 in TS 34.108 on default message content

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element	Value/remark
Message Type
Paging record list	Not present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 1b)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 1
SIB 1 Cell Value tag	Set to (Current SIB1 value tag + 1)
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)
SB 1 Cell Value tag	Set to (Current SB1 value tag + 1)

SCHEDULING BLOCK 1(Step 1b)

Information Element	Value/remark
SIB 6 Cell Value tag	Set to (Current SIB 6 value tag + 1)

SYSTEM INFORMATION TYPE 1 (Step 1b)

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

– UE Timers and constants in idle mode
-T300	2000 milliseconds
-N300	3
-T312	10 seconds
– N312	1

SYSTEM INFORMATION TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis (Step 1b) – (FDD)

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

Information Element	Value/remark
– SIB6 indicator	FALSE
– PICH Power offset	-5 dB
– CHOICE Mode	FDD
– AICH Power offset	-5 dB
– Primary CCPCH info	Not present
– PRACH system information list
– PRACH system information	2PRACHs
– PRACH info (PRACH No.1)
– CHOICE mode	FDD
– Available Signature	‘0000 0000 1111 1111’B
– Available SF	64
– Preamble scrambling code number	0
– Puncturing Limit	1.00
– Available Sub Channel number	‘1111 1111 1111’B
– Transport Channel Identity	15
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	168
– Number of TB and TTI List
– Number of Transport blocks	1
– CHOICE Mode	FDD
– CHOICE Logical Channel List	Configured
– RLC size	360
– Number of TB and TTI List
– Number of Transport blocks	1
– CHOICE Mode	FDD
– CHOICE Logical Channel List	Configured
– Semi-static Transport Format information
– Transmission time interval	20 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	150
– CRC size	16
– RACH TFCS
– Normal
– TFCI Field 1 information
– CHOICE TFCS representation	Complete reconfiguration
– TFCS addition information
– CHOICE CTFC Size	2 bit
– CTFC information	0
– Power offset information
– CHOICE Gain Factors	Computed Gain Factor
– Reference TFC ID	0
– CHOICE Mode	FDD
– Power offset Pp-m	0dB
– CTFC information	1
– Power offset information
– CHOICE Gain Factors	Signalled Gain Factor
– Gain factor ßc	11
– Gain factor ßd	15
– Reference TFC ID	0
– CHOICE Mode	FDD
– Power offset Pp-m	0dB
– PRACH partitioning
– Access Service Class
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#1)
– Available signature End Index	7 (ASC#1)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#3)
– Available signature End Index	7 (ASC#3)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#5)
– Available signature End Index	7 (ASC#5)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#7)
– Available signature End Index	7 (ASC#7)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
CHOICE mode	FDD
– Primary CPICH DL TX power	31
– Constant value	–10
– PRACH power offset
– Power Ramp Step	3dB
– Preamble Retrans Max	4
– RACH transmission parameters
– Mmax	2
– NB01min	3 slot
– NB01max	10 slot
– AICH info
– Channelisation code	3
– STTD indicator	FALSE
– AICH transmission timing	0
– PRACH info (PRACH No.2)
– CHOICE mode	FDD
– Available Signature	‘0000 0000 1111 1111’B
– Available SF	64
– Preamble scrambling code number	1
– Puncturing Limit	1.00
– Available Sub Channel number	‘1111 1111 1111’B
– Transport Channel Identity	31
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	168
– Number of TB and TTI List
– Number of Transport blocks	1
– CHOICE Mode	FDD
– CHOICE Logical Channel List	Configured
– RLC size	360
– Number of TB and TTI List
– Number of Transport blocks	1
– CHOICE Mode	FDD
– CHOICE Logical Channel List	Configured
– Semi-static Transport Format information
– Transmission time interval	20 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	150
– CRC size	16
– RACH TFCS
– Normal
– TFCI Field 1 information
– CHOICE TFCS representation	Complete reconfiguration
– TFCS addition information
– CHOICE CTFC Size	2 bit
– CTFC information	0
– Power offset information
– CHOICE Gain Factors	Computed Gain Factor
– Reference TFC ID	0
– CHOICE Mode	FDD
– Power offset Pp-m	0 dB
– CTFC information	1
– Reference TFC ID	0
– Power offset information
– CHOICE Gain Factors	Signalled Gain Factor
– Gain factor ßc	11
– Gain factor ßd	15
– Reference TFC ID	0
– CHOICE Mode	FDD
– Power offset Pp-m	0dB
– PRACH partitioning
– Access Service Class
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#1)
– Available signature End Index	7 (ASC#1)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#3)
– Available signature End Index	7 (ASC#3)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#5)
– Available signature End Index	7 (ASC#5)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#7)
– Available signature End Index	7 (ASC#7)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
CHOICE mode	FDD
– Primary CPICH DL TX power	31
– Constant value	–10
– PRACH power offset
– Power Ramp Step	3dB
– Preamble Retrans Max	4
– RACH transmission parameters
– Mmax	2
– NB01min	3 slot
– NB01max	10 slot
– AICH info
– Channelisation code	13
– STTD indicator	FALSE
– AICH transmission timing	0

SYSTEM INFORMATION TYPE 5 (Step 1b) – 3.84 Mcps TDD

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

Information Element	Value/remark
– PRACH system information	2PRACHs
– PRACH info (PRACH No.1)
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Timeslot Number	14
– PRACH Channelisation Code
– CHOICE SF	8
– Channelisation Code List
– Channelisation Code	8/1
– Channelisation Code	8/2
– Channelisation Code	8/3
– Channelisation Code	8/4
– PRACH Midamble	Direct
-PNBSCH allocation	Not Present
– Transport Channel Identity	15
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	168
– Number of TB and TTI List
– Transport Time Interval	Not Present
– Number of Transport Blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	150
– CRC size	16
– RACH TFCS	Not Present
– PRACH partitioning
– Access Service Class
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#0)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#1)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#2)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#3)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#4)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#5)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#6)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘11110000’B (ASC#7)
– CHOICE subchannel size	Size1
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
– CHOICE mode	TDD
– PRACH info (PRACH No.2)
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Timeslot Number	14
– PRACH Channelisation Code
– CHOICE SF	8
– Channelisation Code List
– Channelisation Code	8/5 where i denotes an unassigned code
– Channelisation Code	8/6 where i denotes an unassigned code
– Channelisation Code	8/7 where i denotes an unassigned code
– Channelisation Code	8/8 where i denotes an unassigned code
– PRACH Midamble	Direct
-PNBSCH allocation	Not Present
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	168
– Number of TB and TTI List
– Transport Time Interval	Not Present
– Number of Transport Blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	150
– CRC size	16
– RACH TFCS	Not Present
– PRACH partitioning
– Access Service Class
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#0)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#1)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#2)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#3)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#4)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#5)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#6)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#7)
– CHOICE subchannel size	Size1
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
– CHOICE mode	TDD

SYSTEM INFORMATION TYPE 5 (Step 1b) – 1.28 Mcps TDD

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

Information Element	Value/remark
– PRACH system information	2PRACHs
– PRACH info (PRACH No.1)
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– SYNC_UL info
– SYNC_UL codes bitmap	‘11110000’B
– PRX_UpPCHdes	10
– Power Ramping Step	3
– Max SYNC_UL Transmissions	8
– Mmax	32
– PRACH Definition
– Timeslot Number
– CHOICE TDD option	1.28 Mcps TDD
– Timeslot number	1
– PRACH Channelisation Code
– Channelisation Code List
– Channelisation Code	8/8
– Midamble shift and burst type
– CHOICE TDD option	1.28 Mcps TDD
– Midamble Allocation Mode	Default
– Midamble Configuration	8
– Midamble Shift	Not Present
– FPACH info
– Timeslot number	0
– Channelisation code	16/15
– Midamble Shift and burst type
– CHOICE TDD option	1.28 Mcps TDD
– Midamble Allocation Mode	Default
– Midamble Configuration	8
– Midamble Shift	Not Present
– WT	4
– PNBSCH allocation	Not Present
– Transport Channel Identity	15
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	170
– Number of TB and TTI List
– Transport Time Interval	Not Present
– Number of Transport Blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	½
– Rate matching attribute	150
– CRC size	16
– RACH TFCS	Not Present
– PRACH partitioning
– Access Service Class
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#0)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#1)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#2)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#3)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#4)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#5)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#6)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#7)
– CHOICE subchannel size	Size1
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
– CHOICE mode	TDD
– PRACH info (PRACH No.2)
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– SYNC_UL info
– SYNC_UL codes bitmap	‘00001111’B
– PRX_UpPCHdes	10
– Power Ramping Step	1
– Max SYNC_UL Transmissions	8
– Mmax	32
– PRACH Definition
– Timeslot Number
– CHOICE TDD option	1.28 Mcps TDD
– Timeslot number	1
– PRACH Channelisation Code
– Channelisation Code List
– Channelisation Code	8/7
– Midamble shift and burst type
– CHOICE TDD option	1.28 Mcps TDD
– Midamble Allocation Mode	Default
– Midamble Configuration	8
– Midamble Shift	Not Present
– FPACH info
– Timeslot number	An available down-link timeslot
– Channelisation code	16/16
– Midamble Shift and burst type
– CHOICE TDD option	1.28 Mcps TDD
– Midamble Allocation Mode	Default
– Midamble Configuration	8
– Midamble Shift	Not Present
– WT	4
– PNBSCH allocation	Not Present
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	170
– Number of TB and TTI List
– Transport Time Interval	Not Present
– Number of Transport Blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	½
– Rate matching attribute	150
– CRC size	16
– RACH TFCS	Not Present
– PRACH partitioning
– Access Service Class
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#0)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#1)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#2)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#3)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#4)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#5)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#6)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	‘00001111’B (ASC#7)
– CHOICE subchannel size	Size1
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
– CHOICE mode	TDD

SYSTEM INFORMATION TYPE 5 (Step 1b) – 3.84 Mcps TDD

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

Information Element	Value/remark
– PRACH system information	2PRACHs
– PRACH info (PRACH No.1)
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Timeslot Number	14
– PRACH Channelisation Code list VHCR
– CHOICE SF	16
– Channelisation Code List
– Channelisation Code	16/1
– Channelisation Code	16/2
– Channelisation Code	16/3
– Channelisation Code	16/4
– PRACH Midamble	Direct
-PNBSCH allocation	Not Present
– Transport Channel Identity	15
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	168
– Number of TB and TTI List
– Transport Time Interval	Not Present
– Number of Transport Blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	150
– CRC size	16
– RACH TFCS	Not Present
– PRACH partitioning
– Access Service Class
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#0)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#1)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#2)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#3)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#4)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#5)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#6)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘1111000000000000’B (ASC#7)
– CHOICE subchannel size	Size1
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
– CHOICE mode	TDD
– PRACH info (PRACH No.2)
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Timeslot Number	14
– PRACH Channelisation Code list VHCR
– CHOICE SF	16
– Channelisation Code List
– Channelisation Code	16/5 where i denotes an unassigned code
– Channelisation Code	16/6 where i denotes an unassigned code
– Channelisation Code	16/7 where i denotes an unassigned code
– Channelisation Code	16/8 where i denotes an unassigned code
– PRACH Midamble	Direct
-PNBSCH allocation	Not Present
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	168
– Number of TB and TTI List
– Transport Time Interval	Not Present
– Number of Transport Blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	150
– CRC size	16
– RACH TFCS	Not Present
– PRACH partitioning
– Access Service Class
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#0)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#1)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#2)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#3)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#4)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#5)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#6)
– CHOICE subchannel size	Size1
– ASC Setting
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– Available SYNC_UL codes indices	‘0000111100000000’B (ASC#7)
– CHOICE subchannel size	Size1
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
– CHOICE mode	TDD

Contents of System Information Block type 7 (FDD) – (Step 1b)

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

– PRACHs listed in system information block type5 / system information block type 5bis
– Dynamic persistence level	(2,2)
– PRACHs listed in system information block type6	Not present

RRC CONNECTION SETUP (Step 6)

SS sends a message containing an invalid RRC State Indicator

Information Element	Value/remark
RRC state indicator	CELL_PCH

RRC CONNECTION REQUEST (Step 7)

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
Protocol Error Indicator	Check to see if set to TRUE

8.1.2.2.5 Test requirement

After step 2 the UE shall select either PRACH No.1 or PRACH No.2 and transmit an RRC CONNECTION REQUEST message.

After step 6 the UE shall re-send another RRC CONNECTION REQUEST message.

After step 9 the UE shall transmit an RRC CONNECTION SETUP COMPLETE message and establish an RRC connection on the DCCH logical channel.

8.1.2.3 RRC Connection Establishment: Failure (V300 is greater than N300)

8.1.2.3.1 Definition

8.1.2.3.2 Conformance requirement

The UE shall initiate the procedure when upper layers in the UE requests the establishment of a signalling connection and the UE is in idle mode (no RRC connection exists).

Upon initiation of the procedure, the UE shall:

1> set the IE "Initial UE identity" in the variable INITIAL_UE_IDENTITY according to TS 25.331 subclause 8.5.1;

1> submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH;

1> set counter V300 to 1; and

1> start timer T300 when the MAC layer indicates success or failure to transmit the message;

1> select a Secondary CCPCH according to TS 25.304;

1> start receiving all FACH transport channels mapped on the selected Secondary CCPCH.

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

1> set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY;

…

1> if the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and

1> if cell re-selection or expiry of timer T300 occurs:

the UE shall:

1> check the value of V300; and

2> if V300 is equal to or smaller than N300:

…

3> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

…

3> submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink CCCH;

3> increment counter V300;

3> restart timer T300 when the MAC layer indicates success or failure to transmit the message.

…

2> if V300 is greater than N300:

3> enter idle mode.

3> consider the procedure to be unsuccessful;

3> Other actions the UE shall perform when entering idle mode from connected mode are specified in TS 25.331 subclause 8.5.2;

3> the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.

8.1.2.3.3 Test purpose

To confirm that the UE stops retrying to establish the RRC connection if V300 is greater than N300 and goes back to idle mode.

8.1.2.3.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. A Class A UE in manual mode will execute this test case on the CS domain.

Specific Message Contents

SYSTEM INFORMATION TYPE 1

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions.

– UE Timers and constants in idle mode
-T300	2000 milliseconds

Test Procedure

Before the test starts, SS initializes an internal counter K to 0. The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by an outgoing call operation. SS shall not respond to any RRC CONNECTION REQUEST message, instead the counter K is increased by 1 every time such a message is received. To arrive at the verdict, the SS checks that a total of (N300+1) such messages are received. SS calls for generic procedure C.1 to check that UE is in Idle Mode state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				SS initializes counter K to 0 and then prompts the operator to make an outgoing call.
2			RRC CONNECTION REQUEST
3				SS increments K by 1.
4				If K is greater than N300, goes to step 5 else proceed to step 2.
5				SS monitor the uplink CCCH for a time period enough for UE to go back to idle state. SS waits for 5s.
6			CALL C.1	If the test result of C.1 indicates that UE is in Idle Mode state, the test passes, otherwise it fails.

Specific Message Contents

None

8.1.2.3.5 Test requirement

After step 5, counter K shall be equal to (N300+1) and there shall be no uplink transmission in the monitoring period specified in step 5.

8.1.2.4 RRC Connection Establishment: Reject ("wait time" is not equal to 0)

8.1.2.4.1 Definition

8.1.2.4.2 Conformance requirement

When the UE receives an RRC CONNECTION REJECT message on the downlink CCCH, it shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION REJECT message with the value of the variable INITIAL_UE_IDENTITY:

If the values are different, the UE shall ignore the rest of the message;

If the values are identical, the UE shall stop timer T300 and:

1> if the IE "wait time" <> ‘0’; and

1> if the IE "frequency info" is present and:

2> if V300 is equal to or smaller than N300:

3> initiate cell selection on the designated UTRA carrier;

3> after having selected and camped on a cell:

4> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

4> set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

4> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

4> transmit an RRC CONNECTION REQUEST message on the uplink CCCH;

4> reset counter V300;

4> start timer T300 when the MAC layer indicates success or failure in transmitting the message;

4> disable cell reselection to original carrier until the time stated in the IE "wait time" has elapsed;

3> if a cell selection on the designated carrier fails:

4> wait for the time stated in the IE "wait time";

4> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

4> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

4> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

4> then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH of the original serving cell;

4> increment counter V300;

4> restart timer T300 when the MAC layer indicates success or failure to transmit the message;

2> if V300 is greater than N300:

3> enter idle mode;

3> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode from connected mode;

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

…

1> If the IEs "frequency info" not present………:

2> if V300 is equal to or smaller than N300:

3> wait at least the time stated in the IE "wait time";

3> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.2;

3> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

3> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH;

3> increment counter V300;

3> restart timer T300 when the MAC layer indicates success or failure to transmit the message;

2> if V300 is greater than N300:

3> enter idle mode;

3> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode from connected mode;

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.9.

8.1.2.4.3 Test purpose

To confirm that the UE retries to establish the RRC connection after the "wait time" elapses, if the UE receives an RRC CONNECTION REJECT message which includes the IE "wait time" not set to 0.

To confirm that the UE performs a cell reselection when receiving an RRC CONNECTION REJECT message, containing relevant frequency information of the target cell to be re-selected.

8.1.2.4.4 Method of test

Initial Condition

System Simulator: 2 cells – both cell 1 and cell 4 are active and suitable for camping, but cell 1 is transmitted using a larger power. Cell 1 and cell 4 are being transmitted from different 2 UARFCNs. The transmission power of cell 4 is 12 dB smaller than cell 1.

Table 8.1.2.4

Parameter	Unit	Cell 1	Cell 4
UTRA RF Channel Number		Mid Range Test Frequency	High Range Test Frequency
CPICH Ec (FDD)	dBm/3.84 MHz	-60	-72
P-CCPCH (TDD)	dBm	-60	-72

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by an outgoing call operation in cell 1. SS rejects the first request by transmitting an RRC CONNECTION REJECT message which indicates a non-zero wait time. In this message, frequency information for cell 4 is available. SS then waits for RRC CONNECTION REQUEST message on the uplink CCCH of cell 4. SS will also monitor the uplink of cell 1 simultaneously to ensure that all transmission activities from cell 1 have ceased. When the UE has successfully camp onto cell 4, it shall send an RRC CONNECTION REQUEST with the same establishment cause as its previous attempt in cell 1. SS responds with an RRC CONNECTION REJECT message, indicating a non-zero "wait time" and omitting the IE "Redirection Info". The UE shall observe the wait time period indicated. After the wait time has elapsed, the UE shall re-transmit RRC CONNECTION REQUEST again. Finally, SS transmits an RRC CONNECTION SETUP message to establish an RRC connection with the UE, and the UE replies with an RRC CONNECTION SETUP COMPLETE message and enters CELL_DCH state.

NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST	SS prompts the operator to make an outgoing call in cell 1.
2			RRC CONNECTION REJECT	This message shall includes the IE "wait time" set to 5 seconds and IE "frequency info" set to the UARFCN of cell 4. Note: this wait time would apply after failure of the inter frequency cell re- selection, which is not verified in this test case
3				SS waits for a period of time sufficient for UE to reselect to cell 4. At the same time, it monitors the uplink of cell 1 to make sure that all transmissions have ceased.
4			RRC CONNECTION REQUEST	UE shall attempt to re-start an RRC connection establishment procedure in cell 4. The establishment cause shall remain unchanged.
5			RRC CONNECTION REJECT	This message shall include the IE "wait time" set to 5 seconds, but with IE "Redirection Info" absent.
6			RRC CONNECTION REQUEST	SS waits until the duration specified in IE "wait time" has elapsed and then listens to the uplink CCCH for a second RRC CONNECTION REQUEST message.
7			RRC CONNECTION SETUP	SS sends the message to UE to setup an RRC connection with the UE.
8				The UE shall configure the layer 2 and layer 1 in order to access the uplink and downlink DCCH assigned.
9			RRC CONNECTION SETUP COMPLETE

Specific Message Contents

RRC CONNECTION REQUEST (Step 1, step 4 and step 6)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Must be "Originating Call"

RRC CONNECTION REJECT (Step 2) – FDD

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Wait time	5 seconds
Redirection Info
– Frequency Info
– CHOICE mode	FDD
– UARFCN uplink (Nu)	Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink (Nd)	Set to the UARFCN for downlink carrier of cell 4

RRC CONNECTION REJECT (Step 2) – TDD

Information Element	Value/remark
Wait time	5 seconds
Redirection Info
Frequency Info
CHOICE Mode	TDD
UARFCN (Nt)	Set to a different UARFCN from the carrier of cell 1

RRC CONNECTION REJECT (Step 5)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Wait time	5 seconds

8.1.2.4.5 Test requirement

After step 3 the UE shall have successfully re-selected to cell 4. UE shall trigger the start of RRC connection establishment by transmitting RRC CONNECTION REQUEST. The establishment cause shall be originating call.

After step 5 the UE shall observe the period specified in IE "wait time" of the RRC CONNECTION REJECT message and not transmit an RRC CONNECTION REQUEST message in this period.

After step 7 the UE shall transmit an RRC CONNECTION SETUP COMPLETE message to SS on uplink DCCH and then establish an RRC connection.

8.1.2.5 RRC Connection Establishment: Reject ("wait time" is not equal to 0 and V300 is greater than N300)

8.1.2.5.1 Definition

8.1.2.5.2 Conformance requirement

If the values are different, the UE shall ignore the rest of the message;

If the values are identical, the UE shall stop timer T300 and:

1> if the IE "wait time" <> ‘0’; and

1> if the IE "frequency info" is present and:

2> if V300 is equal to or smaller than N300:

3> initiate cell selection on the designated UTRA carrier;

3> after having selected and camped on a cell:

4> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

4> set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

4> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

4> transmit an RRC CONNECTION REQUEST message on the uplink CCCH;

4> reset counter V300;

4> start timer T300 when the MAC layer indicates success or failure in transmitting the message;

4> disable cell reselection to original carrier until the time stated in the IE "wait time" has elapsed;

3> if a cell selection on the designated carrier fails:

4> wait for the time stated in the IE "wait time";

4> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

4> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

4> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

4> then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH of the original serving cell;

4> increment counter V300;

4> restart timer T300 when the MAC layer indicates success or failure to transmit the message;

2> if V300 is greater than N300:

3> enter idle mode;

3> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode from connected mode;

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

…

1> If the IEs "frequency info" not present………:

2> if V300 is equal to or smaller than N300:

3> wait at least the time stated in the IE "wait time";

3> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.2;

3> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

3> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH;

3> increment counter V300;

3> restart timer T300 when the MAC layer indicates success or failure to transmit the message;

2> if V300 is greater than N300:

3> enter idle mode;

3> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode from connected mode;

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.9.

8.1.2.5.3 Test purpose

To confirm that the UE retries to establish the RRC connection after the "wait time" elapses if the UE receives an RRC CONNECTION REJECT message which specifies a non-zero IE "wait time".

To confirm that the UE stops retrying to establish the RRC connection if V300 is greater than N300 and goes back to idle mode.

8.1.2.5.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE

Test Procedure

Before the test starts, SS initializes an internal counter K to 0. The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH, triggered by an outgoing data call operation. SS rejects all requests by transmitting an RRC CONNECTION REJECT message which indicates a non-zero wait time and the counter K is increased by 1 every time such a message is received. To arrive at the verdict, the SS checks that a total of (N300+1) such messages are received and the UE enters idle state. SS calls for generic procedure C.1 to check that UE is in Idle Mode state.

Expected sequence

Step	Direction			Message	Comment
	UE	SS
1					SS initializes counter K to 0 and then prompts the operator to make an outgoing data call.
2				RRC CONNECTION REQUEST	Shall be sent on CCCH and contain the correct establishment cause.
3				RRC CONNECTION REJECT	This message includes the IE "wait time" set to 15 seconds.
4					SS increments K by 1.
5					If K is greater than N300, goes to step 6. Else SS waits for 15 sec before proceeding to step 2.
6					SS monitor the uplink CCCH for a time period enough for UE to goes back to idle state. SS waits for 5s.
7			CALL C.1		If the test result of C.1 indicates that UE is in Idle Mode state, the test passes, otherwise it fails.

Specific Message Contents

RRC CONNECTION REQUEST (Step 2)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Must be "Originating Call"

RRC CONNECTION REJECT (Step 3)

Use the same message type found in TS 34.108 clause 9, with the following exception.

Information Element	Value/remark
Wait time	15 seconds

8.1.2.5.5 Test requirement

After step 6, counter K shall be equals to (N300+1) and there shall be no uplink transmission in the monitoring period specified in step 6.

8.1.2.6 RRC Connection Establishment: Reject ("wait time" is set to 0)

8.1.2.6.1 Definition

8.1.2.6.2 Conformance requirement

If the values are different, the UE shall ignore the rest of the message;

If the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and

if expiry of timer T300 occurs:

the UE shall:

1> check the value of V300; and

2> if V300 is equal to or smaller than N300:

3> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

3> submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink CCCH;

3> increment counter V300;

3> restart timer T300 when the MAC layer indicates success or failure to transmit the message.

2> if V300 is greater than N300:

…

Reference

3GPP TS 25.331 clause 8.1.3.9.

8.1.2.6.3 Test purpose

To confirm that the UE goes back to idle mode, if the SS transmits an RRC CONNECTION REJECT message which includes IE "wait time" set to 0. To confirm that the UE ignores an RRC CONNECT REJECT message not addressed to it. To confirm that the UE is capable of handling an erroneous RRC CONNECTION REJECT message correctly.

8.1.2.6.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by making an outgoing call. After the SS receives this message, it transmits an RRC CONNECTION REJECT message which is not addressed to the UE. The UE shall disregard this message and proceed to re-transmit RRC CONNECTION REQUEST message upon T300 timer expiry. SS answers the second RRC CONNECTION REQUEST message by transmitting an invalid RRC CONNECTION REJECT message. The UE shall continue to send the third RRC CONNECTION REQUEST message upon expiry of T300 timer. Next, the SS sends a legal RRC CONNECTION REJECT message which includes IE "wait time" which is set to ‘0’. To confirm that the UE goes back to idle mode immediately after receiving the reject message, SS shall monitor the uplink CCCH for the next 60 seconds and verify that there is no further transmission in the uplink direction.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST	Test operator is prompted to make an out-going call,
2			RRC CONNECTION REJECT	IE "Initial UE identity" contains an identity different from any of the UE identities available.
3			RRC CONNECTION REQUEST	UE shall send this message after T300 expires.
4			RRC CONNECTION REJECT
5			RRC CONNECTION REQUEST	UE shall send this message after T300 expires.
6			RRC CONNECTION REJECT	IE "wait time" is set to 0.
7				The UE goes back to idle mode.

Specific Message Contents

RRC CONNECTION REQUEST (Step 1, 3 and 5)

Information Element	Value/remark
Message Type
Initial UE Identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Checked to see if set to one of the supported originating call types
Protocol Error Indicator	Checked to see if set to "FALSE"
Measured Results on RACH	Checked to see if it is absent

RRC CONNECTION REJECT (Step 2)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Set to the same type as in RRC CONNECTION REQUEST message (step 1) but with a different value.

RRC CONNECTION REJECT (Step 4)

Information Element	Value/remark
All IEs	Not Present

RRC CONNECTION REJECT (Step 6)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Same as the type and value defined in RRC CONNECTION REQUEST message (step 5)
Reject Cause	Congestion
Wait time	0 second

8.1.2.6.5 Test requirement

After step 2 the UE shall transmit an RRC CONNECTION REQUEST message on uplink CCCH upon expiry of T300 timer.

After step 4 the UE shall re-transmit an RRC CONNECTION REQUEST message on the uplink CCCH upon expiry of T300 timer.

After step 6 the UE shall stop sending an RRC CONNECTION REQUEST message, go back to idle mode immediately and not transmit in the uplink direction again.

8.1.2.7 RRC Connection Establishment in CELL_FACH state: Success

8.1.2.7.1 Definition

8.1.2.7.2 Conformance requirement

The UE shall initiate the procedure when upper layers in the UE requests the establishment of a signalling connection and the UE is in idle mode (no RRC connection exists).

Upon initiation of the procedure, the UE shall:

…

1> set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

1> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

1> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

1> submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH;

1> set counter V300 to 1; and

1> start timer T300 when the MAC layer indicates success or failure to transmit the message;

1> select a Secondary CCPCH according to TS 25.304;

1> start receiving all FACH transport channels mapped on the selected Secondary CCPCH.

….

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

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

1> set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY;

…

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

1> stop timer T300, and act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified otherwise in the following:

2> if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of this procedure:

3> if the IE "Frequency info" is included:

4> select a suitable UTRA cell according to TS 25.304 on that frequency;

3> enter UTRA RRC connected mode;

3> select PRACH according to TS 25.331 subclause 8.5.17;

3> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;

3> ignore the IE "UTRAN DRX cycle length coefficient" and stop using DRX.

1> if the UE, according to subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this procedure:

2> perform the physical layer synchronization procedure as specified in TS 25.214 (FDD) or TS 25.224 (TDD);

2> enter UTRA RRC connected mode, in a state according to TS 25.331 subclause 8.6.3.3;

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per TS 25.331 subclause 8.6.3.3, with the contents set as specified below:

2> set the IE "RRC transaction identifier" to:

3> the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; and

3> clear that entry.

….

2> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE radio access capability" and IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED;

2> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then

2> include this in IE "UE system specific capability".

When the RRC CONNECTION SETUP COMPLETE message has been submitted to lower layers for transmission the UE shall:

1> if the UE has entered CELL_FACH state:

2> start timer T305 using its initial value if periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in system information block type 1.

….

1> consider the procedure to be successful;

And the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.2, 8.1.3.3 and 8.1.3.6.

8.1.2.7.3 Test Purpose

1. To confirm that the UE is able to enter CELL_FACH state and setup signalling radio bearers using common physical channels.

2. To confirm that the UE indicates the requested UE radio access capabilities (used by UTRAN to decide which RAB to establish) and UE system specific capabilities (may be used by UTRAN to configure inter RAT- measurements).

8.1.2.7.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by attempting to make an outgoing call. After the SS receives this message, it assigns the necessary radio resources and U-RNTI to be used by the UE, and then transmits an RRC CONNECTION SETUP message to the UE within timer T300. SS then waits for the UE to transmit an RRC CONNECTION SETUP COMPLETE message on the DCCH. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST	Test operator is requested to make an outgoing call. The UE shall transmit this message, indicating the correct establishment cause. See specific message contents.
2			RRC CONNECTION SETUP	See specific message contents.
3				The UE shall configure the layer 2 and layer 1.
4			RRC CONNECTION SETUP COMPLETE	UE shall send this message on the DCCH, carried by the assigned PRACH resources. See specific message contents. FDD or TDD
5			CALL C.2	If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails.

Specific Message Content

RRC CONNECTION REQUEST

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Originating Conversational Call or Originating Interactive Call or Originating Background Call or Originating Streaming Call or OriginatingSubscribedTrafficCall

RRC CONNECTION SETUP (FDD)

For this message, the contents of the message to be used are basically identical to the message sub-type entitled "RRC CONNECTION SETUP message (Transition to CELL_FACH)" found in TS 34.108, clause 9 with the following exception:

Information Element	Value/remark
Capability update requirement
UE radio access FDD capability update requirement	TRUE
UE radio access TDD capability update requirement	FALSE
System specific capability update requirement list	gsm

RRC CONNECTION SETUP (3.84 Mcps TDD)

Information Element	Value/remark
Capability update requirement
UE radio access FDD capability update requirement	FALSE
UE radio access TDD capability update requirement	TRUE
System specific capability update requirement list	gsm

RRC CONNECTION SETUP (1.28 Mcps TDD)

Information Element	Value/remark
Capability update requirement
UE radio access FDD capability update requirement	FALSE
UE radio access3.84 Mcps TDD capability update requirement	FALSE
UE radio access 1.28 Mcps TDD capability update requirement	TRUE
System specific capability update requirement list	gsm

RRC CONNECTION SETUP (7.68 Mcps TDD)

Information Element	Value/remark
Capability update requirement
UE radio access FDD capability update requirement	FALSE
UE radio access 3.84 Mcps TDD capability update requirement	FALSE
UE radio access 7.68 Mcps TDD capability update requirement	TRUE
UE radio access 1.28 Mcps TDD capability update requirement	FALSE
System specific capability update requirement list	gsm

RRC CONNECTION SETUP COMPLETE

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
UE Radio Access Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE radio access capability extension	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE system specific Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.

8.1.2.7.5 Test requirements

After step 3 the UE shall establish the RRC connection, and transmit RRC CONNECTION SETUP COMPLETE message on the DCCH using PRACH physical resource specified in system information block messages.

8.1.2.8 Void

8.1.2.9 RRC Connection Establishment: Success after Physical channel failure and Failure after Invalid configuration

8.1.2.9.1 Definition

8.1.2.9.2 Conformance requirement

If the UE failed to establish, per TS 25.331 subclause 8.5.4, the physical channel(s) indicated in the RRC CONNECTION SETUP message.

After having received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of the variable INITIAL_UE_IDENTITY.

Before the RRC CONNECTION SETUP COMPLETE message is delivered to lower layers for transmission,

the UE shall:

1> clear the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> check the value of V300, and:

2> if V300 is equal to or smaller than N300:

3> set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;

3> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

3> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

3> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH;

3> increment counter V300; and

3> restart timer T300 when the MAC layer indicates success or failure in transmitting the message.

2> if V300 is greater than N300:

…

If the UE receives an RRC CONNECTION SETUP message which contains an IE "Initial UE identity" with a value which is identical to the value of the variable INITIAL_UE_IDENTITY; and

the variable INVALID_CONFIGURATION becomes set to TRUE due to the received RRC CONNECTION SETUP message:

the UE shall:

1> clear the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS and proceed as below;

1> if V300 is equal to or smaller than N300:

2> set the variable PROTOCOL_ERROR_INDICATOR to TRUE;

2> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

2> perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13; and

2> apply the given Access Service Class when accessing the RACH;

2> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH;

2> increment counter V300; and

2> restart timer T300 when the MAC layer indicates success or failure in transmitting the message.

1> if V300 is greater than N300:

…

Reference

3GPP TS 25.331 clause 8.1.3.

8.1.2.9.3 Test purpose

1. To confirm that the UE retries to establish the RRC connection until V300 is greater than N300 when a physical channel failure occurs because SS does not configure the physical channel that is specified in the transmitted RRC CONNECTION SETUP message.

2. To confirm that the UE retries to establish the RRC connection until V300 is greater than N300 when the transmitted RRC CONNECTION SETUP message causes invalid configuration in the UE.

8.1.2.9.4 Method of test

Initial Condition

System Simulator: 1 cell

Test Procedure

Before the test starts, SYSTEM INFORMATION BLOCK TYPE 1 is modified and this modification is notified to the UE. An internal counter K in SS is initialised to a value = 0. Following this, the UE shall transmit an RRC CONNECTION REQUEST message to the SS on the uplink CCCH, after the operator attempts to make an outgoing call. SS increments K every time such a message is received. Then, SS shall send a RRC CONNECTION SETUP message that contains an invalid configuration. UE shall then send RRC CONNECTION REQUEST message to SS again. This cycle is repeated until K reaches N300+1. When K is equal to N300+1, the SS again transmits an RRC CONNECTION SETUP message including an invalid configuration. Upon receiving this message the UE shall not send another RRC CONNECTION REQUEST message.

Next the SS re-initialises the internal counter K to value = 0, after which the operator attempts to make another outgoing call. Following this, the UE shall transmit an RRC CONNECTION REQUEST message to the SS on the uplink CCCH. SS increments K every time such a message is received. SS transmits an RRC CONNECTION SETUP message to make the UE configure the physical channel in order to communicate on the DCCH but SS does not configure the physical channel. Then the UE detects the physical channel failure and transmits an RRC CONNECTION REQUEST message. This cycle is repeated until K reaches N300+1. When K is equal to N300+1, the SS transmits the RRC CONNECTION SETUP message and configures the physical channel. The UE shall detect "in-sync" from physical layer and then acknowledge the establishment of RRC connection by sending the RRC CONNECTION SETUP COMPLETE message on uplink DCCH.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
0			PAGING TYPE 1	SS transmits the paging message which comprises IE "BCCH Modification Information", with the "Value Tag" different from the "MIB Value Tag" of the current Master Information Block. See specific message contents.

0a			MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 1	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. At the same time, SS starts to transmit the affected SIB TYPE 1 messages. See specific message contents.
				SS waits 5s (to ensure that the UE has time to read the new system information)
1				SS initialises counter K to 0. Operator is asked to make an outgoing call and SS starts to wait for RRC CONNECTION REQUEST on uplink CCCH.
2			RRC CONNECTION REQUEST	See specific message contents.
2a				SS increments K by 1 for every RRC CONNECTION REQUEST message received in step 2
2b			RRC CONNECTION SETUP	See specific message contents.
3				SS checks to see if K is equal to N300+1. If so, goes to step 3a. Else, continues to execute step 2.
3a				SS waits to verify that the UE does not send any further RRC connection REQUEST message
3b				SS re-initialises counter K to 0. Operator is asked to make another outgoing call and SS starts to wait for RRC CONNECTION REQUEST on uplink CCCH.
3c			RRC CONNECTION REQUEST	See specific message contents.
3d				SS increments K by 1 for every RRC CONNECTION REQUEST message received in step 3c
3e				SS checks to see if K is equal to N300+1. If so, goes to step 6. Else, continues to execute step 4
4			RRC CONNECTION SETUP	Use the default message with the same message sub-type specified in clause 9 in TS 34.108. SS does not configure the physical channel.
5				The next step is step 3c.
6			RRC CONNECTION SETUP	Use the default message with the same message sub-type specified in clause 9 in TS 34.108. SS configures the physical channel.
7				The UE configures the layer 1 and layer 2.
8			RRC CONNECTION SETUP COMPLETE	Use the default message with the same message sub-type specified in clause 9 in TS 34.108.

Specific Message Contents

PAGING TYPE 1 (Step 0)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 0a)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 0
SIB 1 Cell Value tag	Set to (Current SIB1 value tag + 1)

SYSTEM INFORMATION TYPE 1 (Step 0a)

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

– UE Timers and constants in idle mode
-T300	2000 milliseconds
-N300	3
-T312	7 seconds
– N312	1

RRC CONNECTION REQUEST (Step 2 & step 3c, K=0)

The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:

Information Element	Value/remark
Initial UE identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or Originating Conversational Call or OriginatingSubscribedTrafficCall

RRC CONNECTION REQUEST (Step 2 & step 3c, K>0)

The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:

Information Element	Value/remark
Initial UE identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or Originating Conversational Call or OriginatingSubscribedTrafficCall
Protocol error indicator	Not Checked

RRC CONNECTION SETUP (Step 2b)

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

Information Element	Value/remark
RRC State Indicator	CELL_DCH
Uplink DPCH info	Not present

8.1.2.9.5 Test requirement

After step 3a the UE shall not send any further RRC CONNECTION REQUEST message.

After step 8 the UE shall transmit an RRC CONNECTION SETUP COMPLETE message and establish an RRC connection.

8.1.2.10 RRC connection establishment in CELL_DCH on another frequency

8.1.2.10.1 Definition

8.1.2.10.2 Conformance requirement

1. The UE shall, in the transmitted RRC CONNECTION REQUEST message:

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

1> set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY;

1> set the IE "Protocol error indicator" to the value of the variable PROTOCOL_ERROR_INDICATOR;

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 11; and

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

1> take care that the maximum allowed message size is not exceeded when forming the IE "Measured results on RACH".

….

2. The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

…

If the values are identical, the UE shall:

…

1> if the UE, according to subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this procedure:

2> perform the physical layer synchronisation procedure A as specified in [29] (FDD only).

Reference

3GPP TS 25.331 clauses 8.1.3.3, 8.1.3.6

8.1.2.10.3 Test Purpose

To confirm that the UE manages to establish an RRC CONNECTION on another frequency when so required by SS in the RRC CONNECTION SETUP message.

8.1.2.10.4 Method of test

Initial condition

System simulator: 2 cells – Cell 1 on UARFCN 1 and Cell 4 on UARFCN 4.

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

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

Use same message sub-clause 6.1 of TS 34.108, with following exception:

Information Element	Value/remark
SIB12 indicator	FALSE
Measurement control system information
– Intra-frequency measurement system information
– Intra-frequency reporting quantity for RACH reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode	FDD
– Reporting quantity	CPICH Ec/No
– Maximum number of reported cells on RACH	Current Cell
– Reporting information for state CELL_DCH	Not present

System Information Block type 11 (TDD)

Use same message sub-clause 6.1 of TS 34.108, with following exception:

Information Element	Value/remark
– SIB12 indicator	FALSE
Measurement control system information
– Intra-frequency measurement system information
– Intra-frequency reporting quantity for RACH reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode	TDD
– Reporting quantity	Primary CCPCH RSCP
– Maximum number of reported cells on RACH	Current Cell
– Reporting information for state CELL_DCH	Not present

Test procedure

The UE is initially in idle mode and is camping on cell 1. SIB 11 is broadcast in cell 1.

SS prompts the operator to make an outgoing call of a supported traffic class. The UE shall transmit an RRC CONNECTION REQUEST on the CCCH, and SS replies with the RRC CONNECTION SETUP, in which the IEs are set as described below. The UE shall send the RRC CONNECTION SETUP COMPLETE back to SS in cell 4 on the DPCH described in the RRC CONNECTION SET UP message received from the SS. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.

Note: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST	By outgoing call operation
2			RRC CONNECTION SETUP	Indicating frequency of cell 4 and IE "Primary CPICH info" set to Primary Scrambling Code assigned to P-CPICH of cell 4 for FDD / IE “Cell Parameters ID” set to cell 4 for LCR TDD.
3				The UE configures the layer 2 and layer 1.
4			RRC CONNECTION SETUP COMPLETE	This message is sent to SS on the frequency indicated in the RRC CONNECTION SETUP message
5			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 content

All messages indicated below shall use the same content as found in TS 34.108 clause 6.1 with the following exceptions:

RRC CONNECTION REQUEST (Step 1) (FDD)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Measured results on RACH	Check that the Ec/No for the cell 1 is reported.

RRC CONNECTION REQUEST (Step 1) (TDD)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Measured results on RACH	Check that the P-CCPCH RSCP for the cell 1 is reported.

RRC CONNECTION SETUP (Step 2) (FDD)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Frequency info
– UARFCN uplink(Nu)	Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink(Nd)	UARFCN downlink of cell 4
Downlink information for each radio links
– Primary CPICH info
– Primary Scrambling Code	Set to same code as used for cell 4

RRC CONNECTION SETUP (Step 2) (TDD)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element

Value/remark

Frequency info

– UARFCN(Nt)

UARFCN of the cell 4

Downlink information for each radio link list

– Downlink information for each radio link

– Choice mode TDD

– Primary CCPCH info

– CHOICE mode TDD

– Cell parameters ID

Cell parameters ID of the cell 4

8.1.2.10.5 Test requirement

In step 4, the UE shall send the RRC CONNECTION SETUP COMPLETE message on the frequency indicated in the RRC CONNECTION SETUP message.

8.1.2.10a RRC connection establishment in CELL_DCH on another frequency in a different frequency band

8.1.2.10a.1 Definition

This test case is identical to test case 8.1.2.10 except that the target cell is on a different frequency band.

8.1.2.10a.2 Conformance requirement

Same conformance requirement as in clause 8.1.2.10.2.

8.1.2.10a.3 Test Purpose

Same test purpose as in clause 8.1.2.10.3 except that the target cell is on a different frequency band.

8.1.2.10a.4 Method of test

Initial condition

Same initial conditions as in clause 8.1.2.10.4 except that cell 1 and cell 4 use the UARFCNs in two different frequency bands. The frequency bands for cell 1 and cell 4 are selected according to PIXIT parameters.

Related ICS/IXIT statement(s)

– UE supports multiple bands simultaneously yes/no

Specific message content

Same specific message content for system information as in clause 8.1.2.10.4.

Test procedure

Same test procedure as in clause 8.1.2.10.4.

Note: If the UE supports more than 2 frequency bands, the test may be executed for various band combinations.

Specific message content

Same specific message content as in clause 8.1.2.10.4.

8.1.2.10a.5 Test requirement

Same test requirement as in clause 8.1.2.10.5.

8.1.2.10b RRC connection establishment in CELL_DCH on another frequency in a different frequency band (TDD a-f band)

8.1.2.10b.1 Definition

This test case is identical to test case 8.1.2.10 except that the target cell is on a different frequency band.

8.1.2.10b.2 Conformance requirement

Same conformance requirement as in clause 8.1.2.10.2.

8.1.2.10b.3 Test Purpose

Same test purpose as in clause 8.1.2.10.3 except that the target cell is on a different frequency band.

8.1.2.10b.4 Method of test

Initial condition

Same initial conditions as in clause 8.1.2.10.4 except that carriers for cell 1 and cell 4 in two different frequency bands. The frequency bands for cell 1 and cell 4 are selected according to PIXIT parameters.

Related ICS/IXIT statement(s)

– UE supports multiple bands simultaneously yes/no

Specific message content

Same specific message content for system information as in clause 8.1.2.10.4.

Test procedure

Same test procedure as in clause 8.1.2.10.4.

Note: If the UE supports more than 2 frequency bands, the test may be executed for various band combinations.

Specific message content

Same specific message content as in clause 8.1.2.10.4.

8.1.2.10b.5 Test requirement

Same test requirement as in clause 8.1.2.10.5.

8.1.2.11 RRC Connection Establishment in FACH state (Frequency modification): Success

8.1.2.11.1 Definition

8.1.2.11.2 Conformance requirement

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the UE storing "Initial UE identity".

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified otherwise in the following:

2> if the UE, according to subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of this procedure:

3> if the IE "Frequency info" is included:

4> select a suitable UTRA cell according to TS 25.304 on that frequency;

3> enter UTRA RRC connected mode;

3> select PRACH according to TS 25.331 subclause 8.5.17;

3> select Secondary CCPCH according to TS5.331 subclause 8.5.19;

3> ignore the IE "UTRAN DRX cycle length coefficient" and stop using DRX.

1> if the UE, according to subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this procedure:

….

2> enter UTRA RRC connected mode, in a state according to TS 25.331 subclause 8.6.3.3;

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per TS 25.331 subclause 8.6.3.3, with the contents set as specified below:

….

And the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.6.

8.1.2.11.3 Test purpose

To confirm that the UE enters to CELL_FACH state and correctly establishes signalling radio bearers using common physical channels of a cell within the frequency band specified by SS in RRC CONNECTION SETUP message.

8.1.2.11.4 Method of test

Initial Condition

System Simulator: 2 cells–Cells 1 is active and cell 6 is inactive.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Specific Message Content

For system information block 3 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 3 (1.28Mcps TDD)

Use same message sub-clause 6.1 of TS 34.108, with following exception:

Information Element	Value/remark
– Cell selection and re-selection info
– CHOICE mode	TDD
— Qrxlevmin	-103 dBm

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

Use same message sub-clause 6.1 of TS 34.108, with following exception:

Information Element	Value/remark
– Intra-frequency reporting quantity for RACH Reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode
– FDD
– Reporting quantity	CPICH Ec/N0
– Maximum number of reported cells on RACH	current cell

System Information Block type 11 (TDD)

Use same message sub-clause 6.1 of TS 34.108, with following exception:

Information Element	Value/remark
– Intra-frequency reporting quantity for RACH Reporting
-SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode	TDD
– CHOICE measurement quantity	PCCPCH RSCP
– Maximum number of reported cells on RACH	current cell

Test Procedure

Table 8.1.2.11

Parameter	Unit	Cell 1		Cell 6
Parameter	Unit	T0	T1	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency		High Range Test Frequency
CPICH Ec (FDD)	dBm/3.84MHz	-55	-72	Off	-72
P-CCPCH RSCP (TDD)	dBm	-55	-72	Off	-72

Table 8.1.2.11 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. SS switches the power settings from columns "T0" to "T1", whenever the description in multi-cell condition specifies the transmission power settings for cell 1 and cell 6.

The UE is in Idle mode of cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.1.2.11. The SS switches its downlink transmission power settings to columns "T1" and the UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by attempting to make an outgoing call. After SS receives this message, it assigns the necessary radio resources and U-RNTI to be used by the UE. The SS then transmits an RRC CONNECTION SETUP message containing an IE "frequency info" IE "Frequency info" set to uplink/downlink UARFCN as used for cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code assigned to P-CPICH of cell 6 for FDD mode, and UARFCN as used for cell 6 and IE "Primary CCPCH RSCP info" set as assigned in cell 6 for TDD mode. The SS monitors all uplink RACH channels of cell 6.The UE transmitting an RRC CONNECTION SETUP COMPLETE message on the DCCH (mapped onto RACH) of cell 6.

NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The initial state of UE is in Idle mode of cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.1.2.11.
2				The SS switches its downlink transmission power settings to columns "T1" in table 8.1.2.11.
3			RRC CONNECTION REQUEST	Operator makes an outgoing call. The UE shall transmit this message, indicating the proper establishment cause.
4			RRC CONNECTION SETUP	Including IE "Frequency info" set to frequency information of cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code assigned to P-CPICH of cell 6 for FDD mode, and IE "Primary CCPCH RSCP info" set as assigned in cell 6 for TDD mode.
5			RRC CONNECTION SETUP COMPLETE	UE shall send this message on the DCCH, carried by the assigned PRACH resources in cell 6.

Specific Message Content

RRC CONNECTION REQUEST (Step 3) (FDD)

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

Information Element	Value/remark
Initial UE identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or Originating Conversational Call or OriginatingSubscribedTrafficCall
Measured results on RACH	Check to see if set in accordance with the IE "Intra-frequency reporting quantity for RACH Reporting" included in SYSTEM INFORMATION BLOCK Type 11
– Measurement result for current cell
– CHOICE mode
– FDD
– CHOICE measurement quantity
– CPICH Ec/N0	The actual reported value is not checked

RRC CONNECTION REQUEST (Step 3) (TDD)

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

Information Element	Value/remark
Initial UE identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or Originating Conversational Call or OriginatingSubscribedTrafficCall
Measured results on RACH	Check to see if set in accordance with the IE "Intra-frequency reporting quantity for RACH Reporting" included in SYSTEM INFORMATION BLOCK Type 11
– Measurement result for current cell
– CHOICE mode	TDD
– CHOICE measurement quantity
– P-CCPCH RSCP	The actual reported value is not checked

RRC CONNECTION SETUP (Step 4) (FDD)

Information Element	Value/remark
Frequency info
– UARFCN uplink(Nu)	Not Present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink(Nd)	Same downlink UARFCN as used for cell 6
Downlink information for each radio links
– Primary CPICH info
– Primary Scrambling Code	Set to same code as used for cell 6

RRC CONNECTION SETUP (Step 4) (TDD)

Information Element	Value/remark
Frequency info
– UARFCN (Nt)	Same UARFCN as used for cell 6
Downlink information for each radio links
– Primary CCPCH info
– Cell parameters ID	As used for cell 6

RRC CONNECTION SETUP COMPLETE (Step 5)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
UE Radio Access Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE radio access capability extension	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE system specific Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.

8.1.2.11.5 Test requirement

After step 5 the UE shall transmit RRC CONNECTION SETUP COMPLETE message on the uplink DCCH in cell 6.

8.1.2.12 RRC Connection Establishment: Reject with interRATInfo is set to GSM

8.1.2.12.1 Definition

8.1.2.12.2 Conformance requirement

If the values are different, the UE shall ignore the rest of the message;

If the values are identical, the UE shall:

1> stop timer T300; and

clear the entry for the RRC CONNECTION REJECT message in the table "Accepted transactions" in the variable TRANSACTIONS;

…

1> if the IE "inter-RAT info" is present and:

2> if V300 is equal to or smaller than N300:

3> select a suitable cell belonging to the selected PLMN or any PLMN indicated to be equivalent to that PLMN in the designated RAT;

3> after having selected and camped on a suitable cell on the designated RAT:

4> disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed.

8.1.2.12.3 Test Purpose

To verify that the UE shall select the GSM cell when RRC Connection Reject with Inter-RAT info set to GSM is received in response to RRC connection request.

Reference

3GPP TS 25.331, section 8.1.3.9

8.1.2.12.4 Method of test

Initial condition

System Simulator: 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9. The Inter-RAT Cell Info List of Cell 1 refers to Cell 9. The 3G Neighbour Cell Description List of Cell 9 refers to Cell 1.

UE: Idle state (state 2) as specified in clause 7.4 of TS 34.108

Related ICS/IXIT statement(s)

– UE supports both GSM and UTRAN Radio Access Technologies,

– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-850, GSM-PCS.

– PS Supported yes/no

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

Test procedure

The UE transmits an RRC CONNECTION REQUEST message for making an MO call. After the SS receives this message, it transmits an RRC CONNECTION REJECT message with interRATInfo set to “GSM” and wait time set to 10 seconds. UE then selects GSM cell specified in SIB11 and sends a CHANNEL REQUEST for making an MO call. RR connection is successfully established. Thereafter an MO call is established in the GSM cell.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				Prompt the operator to make an outgoing call.
2			RRC CONNECTION REQUEST
3			RRC CONNECTION REJECT	See specific message contents.
4	UE			UE selects the GSM cell specified in the SIB11.
5			CHANNEL REQUEST	UE requests for RR connection to establish the MO call.
6			IMMEDIATE ASSIGNMENT	RR connection is established. Thereafter UE proceeds with the MO call establishment. SS completes the call establishment procedure.
7	SS			It is verified that the MO call is successfully established by sending a STATUS ENQUIRY message. The UE shall respond with a STATUS message indicating that it is in state U10.

Specific message contents

RRC CONNECTION REJECT in step 4:

Wait time	10 seconds
Redirectioninfo
InterRATInfo	GSM

8.1.2.12.5 Test requirement

1) At step 5, UE should respond on GSM cell.

2) At step 7, UE should be in CC state U10 in the GSM cell.

8.1.2.13 RRC Connection Establishment: Reject with InterRATInfo is set to GSM and selection to the designated system fails

8.1.2.13.1 Definition

8.1.2.13.2 Conformance requirement

If the values are different, the UE shall ignore the rest of the message;

If the values are identical, the UE shall:

1> stop timer T300; and

clear the entry for the RRC CONNECTION REJECT message in the table "Accepted transactions" in the variable TRANSACTIONS;

…

1> if the IE "inter-RAT info" is present and:

2> if V300 is equal to or smaller than N300:

3> if no suitable cell in the designated RAT is found:

4> wait at least the time stated in the IE "wait time";

4> set CFN in relation to SFN of current cell according to subclause 8.5.15;

4> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.2.

4> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;

4> then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH;

4> increment counter V300;

restart timer T300 when the MAC layer indicates success or failure to transmit the message;

….

2> if V300 is greater than N300:

3> enter idle mode;

3> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode;

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

8.1.2.13.3 Test Purpose

To verify that the UE upon receiving RRC Connection Reject with Inter-RAT info set to GSM and failing to select the designated GSM system shall reselect UTRAN cell only after the wait time specified in RRC Connection Reject. The UE shall then continue with the RRC CONNECTION establishment procedure.

Reference

3GPP TS 25.331, section 8.1.3.9

8.1.2.13.4 Method of test

Initial conditions

System Simulator: 2 cells – Cell 1 is UTRAN, the value of N300 is set to 1. Cell 9 is GSM. GSM 51.010 clause 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9. The Inter-RAT Cell Info List of Cell 1 refers to Cell 9. The 3G Neighbour Cell Description List of Cell 9 refers to Cell 1.

UE: Idle state (state 2) as specified in clause 7.4 of TS 34.108

Related ICS/IXIT statement(s)

– UE supports both GSM and UTRAN Radio Access Technologies,

– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-850, GSM-PCS.

– PS Supported yes/no

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

Test procedure

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by making an outgoing call. After the SS receives this message, it transmits an RRC CONNECTION REJECT message with interRATInfo set to “GSM” and wait time set to 10 seconds. The GSM cell is switched off; therefore UE fails to select the GSM cell. UE reselects UTRAN cell only after waiting for duration specified in wait time. It then retransmits RRC CONNECTION REQUEST.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				Prompt the operator to make an outgoing call.
2			RRC CONNECTION REQUEST	Shall be sent on CCCH and contain the correct establishment cause.
3			RRC CONNECTION REJECT	See specific message contents.
4				Cell 9 is switched off
5			RRC CONNECTION REQUEST	SS verifies that RRC connection is received only after wait time.
6			RRC CONNECTION REJECT	SS sends the message to bring the UE to idle mode.

Specific message contents

RRC CONNECTION REJECT in step 3:

Wait time	10 seconds
Redirectioninfo
InterRATInfo	GSM

8.1.2.13.5 Test requirement

1) At step 5, RRC connection request is received after wait time.

8.1.2.14 RRC Connection Establishment using the default configuration for 3.4 kbps signalling bearers

8.1.2.14.1 Definition

8.1.2.14.2 Conformance requirement

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

—————-

2> if IE "Specification mode" is set to "Preconfiguration" and IE "Preconfiguration mode" is set to "Default configuration":

3> initiate the radio bearer and transport channel configuration in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity";

3> initiate the physical channels in accordance with the received physical channel information elements.

NOTE: IE "Default configuration mode" specifies whether the FDD or TDD version of the default configuration shall be used.

Reference

3GPP TS 25.331 clause 8.1.3.6, clause 13.7

8.1.2.14.3 Test purpose

To confirm that the UE establishes the radio bearer and transport channel configuration for 3.4kbps signalling radio bearers in accordance with the stored default parameters as identified by the IE “Default configuration identity” specified in the RRC Connection Setup Message

8.1.2.14.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE shall transmit a RRC CONNECTION REQUEST message to the SS on the uplink CCCH, after the operator attempts to make an outgoing call. SS shall send a RRC CONNECTION SETUP message that contains the stored default configuration identity 0 (for 3.4kbps signalling radio bearers). The UE accepts the message, configuring the radio bearer and transport channel configuration in accordance with the stored default parameters and acknowledges the establishment of RRC connection by sending the RRC CONNECTION SETUP COMPLETE message on uplink DCCH.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				Operator is asked to make an outgoing call.
2			RRC CONNECTION REQUEST
3			RRC CONNECTION SETUP	DefaultConfigIdentity used is ‘0’
4			RRC CONNECTION SETUP COMPLETE
5			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

RRC CONNECTION REQUEST (Step 2)

The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:

Information Element	Value/remark
Initial UE identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or Originating Conversational Call or OriginatingSubscribedTrafficCall

RRC CONNECTION SETUP (Step 3) (FDD)

Use the same message sub-type found in clause 9 of TS 34.108 (Transition to CELL_DCH), with the following exceptions:

Information Element	Value/remark
Choice Specification Mode	Preconfiguration
– Choice Preconfig Mode	Default Config
– Default Config Mode	FDD
-Default Config Identity	0
Uplink DPCH info
– Uplink DPCH power control info
– DPCCH power offset	-40 (-80 dB)
– PC Preamble	1 frame
– SRB delay	7 frames
– Power Control Algorithm	Algorithm1
– TPC step size	0 (1 dB)
– Scrambling code type	Long
– Scrambling code number	0 (0 to 16777215)
– Number of DPDCH	Not Present(1)
– Spreading factor	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– TFCI existence	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– Number of FBI bit	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– Puncturing Limit	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
Downlink information common for all radio links
– Downlink DPCH info common for all RL
– Timing Indication	Initialize
– CFN-targetSFN frame offset	Not Present
– CHOICE mode	FDD
– Downlink DPCH power control information
– DPC mode	0 (single)
– Power offset P Pilot-DPDCH	0
– DL rate matching restriction information	Not Present
– Spreading factor	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– Fixed or Flexible Position	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– TFCI existence	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– CHOICE SF	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– DPCH compressed mode info	Not Present
– TX Diversity mode	None
– Default DPCH Offset Value	Arbitrary set to value 0..306688 by step of 512
Downlink information for each radio links list
– Downlink information for each radio links
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Reference to clause 6.1 "Default settings (FDD)"
– Downlink DPCH info for each RL
– Primary CPICH usage for channel estimation	Primary CPICH may be used
– DPCH frame offset	Set to value: Default DPCH Offset Value mod 38 400
– Secondary CPICH info	Not Present
– DL channelization code
– Secondary scrambling code	1
– Spreading factor	According to clause 6.10.2.4.1.2 (standalone 3.4 kbps signalling radio bearer)
– Code number	0
– Scrambling code change	Not Present
– TPC combination index	0
– Closed loop timing adjustment mode	Not Present

RRC CONNECTION SETUP (Step 3)(1.28Mcps TDD)

Use the same message sub-type found in clause 9 of TS 34.108 (Transition to CELL_DCH), with the following exceptions:

Information Element	Value/remark
Choice Specification Mode	Preconfiguration
– Choice Preconfig Mode	Default Config
– Default Config Mode	TDD
-Default Config Identity	0

RRC CONNECTION SETUP COMPLETE (Step 4)

Use the same message sub-type found in clause 9 of TS 34.108.

8.1.2.14.5 Test requirement

In step 4 the UE shall transmit a RRC CONNECTION SETUP COMPLETE message on Radio Bearer Id: 2 and establish a RRC connection.

8.1.2.15 RRC Connection Establishment using the default configuration for 13.6 kbps signalling bearers

8.1.2.15.1 Definition

8.1.2.15.2 Conformance requirement

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

—————-

2> if IE "Specification mode" is set to "Preconfiguration" and IE "Preconfiguration mode" is set to "Default configuration":

3> initiate the radio bearer and transport channel configuration in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity";

3> initiate the physical channels in accordance with the received physical channel information elements.

NOTE: IE "Default configuration mode" specifies whether the FDD or TDD version of the default configuration shall be used.

Reference

3GPP TS 25.331 clause 8.1.3.6, clause 13.7

8.1.2.15.3 Test purpose

To confirm that the UE establishes the radio bearer and transport channel configuration for 13.6kbps signalling radio bearers in accordance with the stored default parameters as identified by the IE “Default configuration identity” specified in the RRC Connection Setup Message

8.1.2.15.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Test Procedure

The UE shall transmit a RRC CONNECTION REQUEST message to the SS on the uplink CCCH, after the operator attempts to make an outgoing call. SS shall send a RRC CONNECTION SETUP message that contains the stored default configuration identity 1 for Rel-5, or 22 for Rel-6 onwards (for 13.6kbps signalling radio bearers). The UE accepts the message, configuring the radio bearer and transport channel configuration in accordance with the stored default parameters and acknowledge the establishment of RRC connection by sending the RRC CONNECTION SETUP COMPLETE message on uplink DCCH.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				Operator is asked to make an outgoing call.
2			RRC CONNECTION REQUEST
3			RRC CONNECTION SETUP	DefaultConfigIdentity used is ‘1’ for Rel-5, or ‘22’ for Rel-6 onwards
4			RRC CONNECTION SETUP COMPLETE
5			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

RRC CONNECTION REQUEST (Step 2)

The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:

Information Element	Value/remark
Initial UE identity	Same as the IMSI stored in the TEST USIM card, or the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or Originating Conversational Call or OriginatingSubscribedTrafficCall

RRC CONNECTION SETUP (Step 3, Rel-5) (FDD)

Use the same message sub-type found in clause 9 of TS 34.108 (Transition to CELL_DCH), with the following exceptions:

Information Element	Value/remark
Choice Specification Mode	Preconfiguration
– Choice Preconfig Mode	Default Config
– Default Config Mode	FDD
-Default Config Identity	1

RRC CONNECTION SETUP (Step 3, Rel-6 onwards) (FDD)

Use the same message sub-type found in clause 9 of TS 34.108 (Transition to CELL_DCH), with the following exceptions:

Information Element	Value/remark
Choice Specification Mode	Preconfiguration
– Choice Preconfig Mode	Default Config
– Default Config Mode	FDD
-Default Config Identity	22

RRC CONNECTION SETUP (Step 3)( 1.28Mcps TDD)

Use the same message sub-type found in clause 9 of TS 34.108 (Transition to CELL_DCH), with the following exceptions:

Information Element	Value/remark
Choice Specification Mode	Preconfiguration
– Choice Preconfig Mode	Default Config
– Default Config Mode	TDD
-Default Config Identity	22

RRC CONNECTION SETUP COMPLETE (Step 4)

Use the same message sub-type found in clause 9 of TS 34.108

8.1.2.15.5 Test requirement

In step 4 the UE shall transmit a RRC CONNECTION SETUP COMPLETE message on Radio Bearer Id: 2 and establish an RRC connection.

8.1.2.16 RRC Connection Establishment / Domain Specific Access Control: Success

8.1.2.16.1 Definition

This test case is applicable for Rel-5 UEs supporting DSAC and Rel-6 or later UEs.

8.1.2.16.2 Conformance requirement

Access Class related cell access restrictions shall be checked by the UE before sending an RRC connection request message when entering Connected Mode from UTRAN Idle mode.

…

With respect to Domain Specific Access Control, the UE shall:

1> if the IE "Multiple PLMN List" is not included in the Master Information Block:

2> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters for PLMN of MIB".

…

The UE shall apply the following handling with respect to any Access Class Barring information:

1> if in idle mode and any Access Class Barring information is indicated:

2> if no Domain Specific Access Restriction Parameters are included in System Information Block Type 3, the UE shall:

3> act on the IE "Access Class Barred list" when initiating RRC Connection establishment as specified in [4] (TS 25.304).

2> if the Domain Specific Access Restriction Parameters to be applied are included in System Information Block Type 3 the UE shall:

3> act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4] (TS 25.304);

3> act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4] (TS 25.304);

3> upon transition to UTRA RRC connected, the UE shall:

4> store that Domain Specific Access Restriction Parameters to the variable "DSAC_PARAM" and maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC connection is released;

4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4] (TS 25.304);

4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4] (TS 25.304);

1> if in connected mode:

2> if no Access Class Barring information is indicated:

3> if the variable "DSAC_PARAM" is set, the UE shall

4> clear the variable "DSAC_PARAM";

4> act as if no Access Class is barred.

2> else if the Domain Specific Access Restriction Parameters to be applied is not included in System Information Block Type 3:

3> if the variable "DSAC_PARAM" is set, the UE shall:

4> clear the variable "DSAC_PARAM";

4> act as if no Access Class is barred.

2> else if the Domain Specific Access Restriction Parameters to be applied are included in the System Information Block Type 3:

3> if the variable "DSAC_PARAM is not set, the UE shall:

3> else (the access class barring information is stored) UE shall:

4> update the variable "DSAC_PARAM" with that Domain Specific Access Restriction Parameters;

4> act on the updated IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4] (TS 25.304);

4> act on the updated IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4] (TS 25.304).

….

Reference

3GPP TS 25.304 clause 5.3.1.2, TS 25.331 clause 8.1.1.6.3

8.1.2.16.3 Test purpose

To confirm that the UE establishes a RRC Connection on the non-barred domain under the Domain Specific Access Restriction.

8.1.2.16.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 7) as specified in clause 7.4 of TS 34.108

Related ICS/IXIT statements

The- Support of DSAC Yes/No.

Support of DSAC Yes/No.Test Procedure

This test case shall be run twice:

Case1) The system information block type 3 indicates that only the CS domain is barred at step2.

Case2) The system information block type 3 indicates that only the PS domain is barred at step2.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1	←		PAGING TYPE1	The SS transmits the message including the IE “BCCH Modification Information”.
2	← ←		MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE3	The SS starts to transmit the MIB with the “MIB value tag” IE different from the original setting. The SS transmits the new SIB3 to indicate that one of the supported domains in the cell is barred.
3				The SS waits 5 sec (to ensure that the UE has time to read the new system information).
4	→		RRC CONNECTION REQUEST	The SS prompts the test operator to make an outgoing call on the other non-barred domain.
5	←		RRC CONNECTION SETUP
6	→		RRC CONNECTION SETUP COMPLETE
7	→		INITIAL DIRECT TRANSFER

Specific Message Content

PAGING TYPE 1 (Step 1)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 2)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 1
SIB 3 Cell Value tag	Set to (Current SIB3 value tag + 1)

System Information Block type 3 (Step 2)

For Case 1 i.e. when only the CS domain is barred.

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

Information Element	Value/remark
Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
Domain Specific Access Restriction Parameters For PLMN Of MIB
-CS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
-PS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	not barred
– Access Class Barred1	not barred
– Access Class Barred2	not barred
– Access Class Barred3	not barred
– Access Class Barred4	not barred
– Access Class Barred5	not barred
– Access Class Barred6	not barred
– Access Class Barred7	not barred
– Access Class Barred8	not barred
– Access Class Barred9	not barred
– Access Class Barred10	not barred
– Access Class Barred11	not barred
– Access Class Barred12	not barred
– Access Class Barred13	not barred
– Access Class Barred14	not barred
– Access Class Barred15	not barred

System Information Block type 3 (Step 2)

For Case 2 i.e. when only the PS domain is barred

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

Information Element	Value/remark
Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
Domain Specific Access Restriction Parameters For PLMN Of MIB
-CS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	not barred
– Access Class Barred1	not barred
– Access Class Barred2	not barred
– Access Class Barred3	not barred
– Access Class Barred4	not barred
– Access Class Barred5	not barred
– Access Class Barred6	not barred
– Access Class Barred7	not barred
– Access Class Barred8	not barred
– Access Class Barred9	not barred
– Access Class Barred10	not barred
– Access Class Barred11	not barred
– Access Class Barred12	not barred
– Access Class Barred13	not barred
– Access Class Barred14	not barred
– Access Class Barred15	not barred
-PS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred

INITIAL DIRECT TRANSFER (Step 7)

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

Information Element	Value/remark
CN domain identity	Check to see if it is not the barred domain.

8.1.2.16.5 Test requirement

At step4, the UE transmits a RRC CONNECTION REQUEST message to the SS for establishing the non-barred domain service.

At step6, the UE transmits a RRC CONNECTION SETUP COMPLETE message to the SS on uplink DCCH.

8.1.2.17 RRC Connection Establishment for transition from Idle Mode to CELL_DCH: Success (start of E-DCH transmission)

8.1.2.17.1 Definition and applicability

All UEs which support FDD and HS-PDSCH and E-DCH and fully support F-DPCH or all UEs which support TDD and HS-PDSCH and E-PUCH.

8.1.2.17.2 Conformance requirement

In case the procedure was triggered by reception of a RRC CONNECTION SETUP message, the UE shall:

1> transmit a RRC CONNECTION SETUP COMPLETE as response message on the uplink DCCH using AM RLC.

…

The variable E_DCH_TRANSMISSION shall be set to "TRUE" only when all the following conditions are met:

1> the UE is in Idle Mode;

1> the variable E_RNTI includes either the Primary E-RNTI or the Secondary E-RNTI or both the Primary and the Secondary E-RNTI;

1> For FDD:

2> the UE has stored the following IEs:

– IE "E-DCH Transmission Time Interval";

– IE "HARQ info for E-DCH";

– IE "E-DCH information", including the IE "E-DPCCH info" and the IE "E-DPDCH info".

– one of the radio links in the active set is configured as the serving E-DCH radio link, and for this radio link the UTRAN has configured the IE "E-HICH configuration" and the IE "E-AGCH info".

1> For TDD:

2> for non-scheduled transmission, the UE has stored the following IEs:

– IE "HARQ info for E-DCH";

– IE "E-DCH information", including the IE "E-PUCH info";

– IE "Non-scheduled transmission grant info";

2> for scheduled transmission, the UE has stored the following IEs:

– IE "HARQ info for E-DCH";

– IE "E-DCH information", including the IE "E-RUCCH info" and the IE "E-PUCH info";

– IE "E-HICH info";

– IE "E-AGCH info".

1> there is at least one logical channel mapped to E-DCH for which:

2> the corresponding E-DCH MAC-d flow is configured, i.e. the IEs "E-DCH MAC-d flow power offset" and "E-DCH MAC-d flow maximum number of retransmissions", and the transmission grant type are configured.

If any of the above conditions is not met and the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall:

1> set the variable E_DCH_TRANSMISSION to FALSE;

1> stop any E-AGCH, E-HICH and E-RGCH reception procedures;

1> For FDD:

2> stop any E-RGCH reception procedures.

1> For FDD:

2> stop any E-DPCCH and E-DPDCH transmission procedures.

1> For TDD:

2> stop any E-RUCCH and E-PUCH transmission procedures.

1> clear the variable E_RNTI;

1> release all E-DCH HARQ resources;

1> no longer consider any radio link to be the serving E-DCH radio link.

Whenever the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall:

1>For FDD:

2> perform E_AGCH reception procedures according to the stored E_AGCH configuration as stated in:

3> subclause 8.6.3.14 for the IE "New Primary E-RNTI" and the IE "New Secondary E-RNTI".

2> perform E-HICH reception procedures for all radio links in the active set for which an E-HICH configuration has been provided;

2> perform E-RGCH reception procedures for all radio links in the active set for which an E-RGCH configuration has been provided;

2> perform E-DPCCH transmission procedures according to the stored E-DPCCH configuration as stated in:

3> subclause 8.6.6.37 for the IE "E-DPCCH Info";

2> perform E-DPDCH transmission procedures according to the stored E-DPDCH configuration as stated in:

3> subclause 8.6.5.16 for the IE "E-DCH Transmission Time Interval";

3> subclause 8.6.5.17 for the IE "HARQ info for E-DCH".

3> subclause 8.6.6.37 for the IE "E-DPDCH Info".

2> inclusion of MAC-d PDU’s in a MAC-e PDU for logical channels belonging to a MAC-d flow for which the IE "Non-scheduled transmission grant info" is configured shall:

3> obey the scheduling and size restrictions as specified for that MAC-d flow (see subclause 8.6.5.18).

2> inclusion of MAC-d PDU’s in a MAC-e PDU for logical channels belonging to a MAC-d flow for which the IE "Scheduled transmission grant info" is configured shall:

3> be performed in accordance with the received scheduling grant on E-AGCH/E-RGCH (see [15]); and

3> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37).

1>For TDD:

2> if scheduled transmission is configured, perform E-AGCH reception procedures according to the stored E_AGCH configuration as stated in:

3> subclause 8.6.3.14 for the IE "New Primary E-RNTI".

2> Perform E-HICH reception;

2> for 3.84/7.68 Mcps TDD, perform E-RUCCH transmission procedures according to the stored E-RUCCH configuration as stated in:

3> subclause 8.6.6.37 for the IE "E-RUCCH Info".

2> for 1.28 Mcps TDD, if scheduled transmission is configured, perform E-RUCCH transmission procedure according to the stored PRACH configuration (see [60]) and the stored E-RUCCH configuration as stated in:

3> subclause 8.6.6.37 for the IE "E-RUCCH Info".

NOTE 1: The PRACH configuration is signalled directly to the UE in "E-RUCCH Info" IE in case of E-DCH serving cell change.

2> Perform E-PUCH transmission procedures according to the stored E-PUCH configuration as stated in:

3> subclause 8.6.6.37 for the IE "E-PUCH Info".

2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Non-scheduled transmission grant info" is configured shall:

3> obey the scheduling and size restrictions as specified for that MAC-d flow (see subclause 8.6.5.18).

2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Scheduled transmission grant info" is configured shall:

3> be performed in accordance with the received scheduling grant on E-AGCH (see [15]); and

3> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37).

2> obtain and format the appropriate information on E-UCCH (see [15]). For 1.28 Mcps TDD, when performing transmission on signalling radio bearer before RAB has been established, the UE shall use the lowest E-DCH capability category, as specified in [35], to signal the UL control information on E-UCCH.

NOTE 2: For 1.28 Mcps TDD, when performing transmission on signalling radio bearer before RAB has been established, UTRAN should use the lowest E-DCH capability category when performing configuration, scheduling and reading the control information on E-UCCH, as it is not possible for Node B to be aware of the UE’s E-DCH capability category during this period.

Whenever the variable E_DCH_TRANSMISSION is set to FALSE, the UE shall:

1> not perform E-AICH, E-HICH and E-RGCH reception procedures;

1> not perform E-DPCCH and E-DPDCH transmission procedures.

…

If the IE "New Primary E-RNTI" and/or the IE "New Secondary E-RNTI" are/is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> store the new value(s) in the variable E_RNTI;

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall:

1> for FDD:

2>use the value of the Primary E-RNTI and/or Secondary E-RNTI stored in the variable E_RNTI as UE identities in the E-AGCH reception procedure in the physical layer.

1> for TDD:

2> use the value of New Primary E-RNTI stored in the variable E_RNTI as the UE identity in the E-AGCH reception procedure and the E-RUCCH transmission procedure in the physical layer.

…

If the IE "Added or Reconfigured UL TrCH information" is included then the UE shall:

1> for the transport channel identified by the IE "UL Transport Channel Identity" and IE "Uplink transport channel type":

2> perform the actions for the IE "Transport Format Set" as specified in subclause 8.6.5.1.

NOTE: The UE stores the UL transport channel configuration until it is explicitly deleted by a message containing the IE "Deleted UL TrCH information" or the UE leaves RRC Connected mode.

1> if the choice "UL parameters" is set to ‘EDCH’:

2> for FDD:

3> apply the values of the IE "E-DCH Transmission Time Interval" and the IE "HARQ info for E-DCH" to all E-DCH MAC-d flows.

2> for TDD:

3> apply the value of the IE "HARQ info for E-DCH" to all E-DCH MAC-d flows.

2> if the IE "HARQ Info" is included:

3> perform the actions specified in subclause 8.6.5.17.

2> if the IE "Added or Reconfigured E-DCH MAC-d Flow" is included:

3> for each MAC-d flow identified by the IE "Mac-d flow identity":

4> perform the actions as specified in subclause 8.6.5.18.

2> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

NOTE: In case of multiple E-DCH MAC-d flows, IE "Added or Reconfigured UL TrCH information" is only included once. If the IE "Added or Reconfigured UL TrCH information" is included more than once with the IE "Uplink transport channel type" set to ‘E-DCH’, the UE behaviour is unspecified.

…

If the IE "E-DCH Transmission Time Interval" is included, the UE shall:

1> store the received TTI;

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall:

1> apply the TTI as signalled in the IE "E-DCH Transmission Time Interval" on the E-DPDCH.

If the received "E-DCH Transmission Time Interval" is 2 ms and the previously stored TTI was 10 ms:

1> not send any data on E-DPDCH in first 8 TTIs after activation time of new TTI.

…

If the IE "HARQ Info for E-DCH" is included, the UE shall:

1> store the received configuration;

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall:

1> use a redundancy version for each HARQ transmission as configured by the IE "HARQ RV Configuration".

…

If the IE "Added or reconfigured E-DCH MAC-d flow" is included, the UE shall:

1> if the IE "E-DCH MAC-d flow power offset" is included:

2> configure the power offset indicated in the IE "E-DCH MAC-d flow power offset" for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity".

1> if the IE "E-DCH MAC-d flow maximum number of retransmissions" is included:

2> configure the maximum number of retransmissions indicated in the IE "E-DCH MAC-d flow maximum number of retransmissions" for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity".

1> for 1.28 Mcps TDD, if the IE "E-DCH MAC-d flow retransmission timer" is included:

2> configure the retransmission timer for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity".

1> if the IE "E-DCH MAC-d flow multiplexing list" is included:

2> only multiplex MAC-d PDU’s from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDU’s from E-DCH MAC-d flows with which multiplexing in the same MAC-e PDU is allowed in accordance to the IE "E-DCH MAC-d flow multiplexing list".

1> else:

2> if previously the IE "E-DCH MAC-d flow multiplexing list" was already received for this E-DCH MAC-d flow:

3> continue to only multiplex E-DCH PDU’s from the E-DCH MAC-d flow indicated in the IE “E-DCH MAC-d flow identity” with MAC-d PDU’s from E-DCH MAC-d flows with which multiplexing in the same MAC-e PDU is allowed according to the previously received IE “E-DCH MAC-d flow multiplexing list”.

2> else (never received the IE "E-DCH MAC-d flow multiplexing list" for this E-DCH MAC-d flow):

3> allow multiplexing of MAC-d PDU’s from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDU’s from any other E-DCH MAC-d flow in the same MAC-e PDU.

1> for FDD:

2> if the IE "Non-scheduled transmission grant info" is included:

3> if the TTI configured on the E-DCH equals 2ms, and the IE "2ms non-scheduled transmission grant HARQ process allocation" is configured for this MAC-d flow:

4> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall only be included in a MAC-e or MAC-i PDU transmitted by HARQ processes allowed by the IE "2ms non-scheduled transmission grant HARQ process allocation", with a total contribution from this MAC-d flow (i.e. including MAC-e/es or MAC-i/is headers) not exceeding the size as signalled by the IE "Max MAC-e PDU contents size".

3> else:

4> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall be included in a MAC-e or MAC-i PDU transmitted by any HARQ process, with a total contribution from this MAC-d flow (i.e. including MAC-e/es or MAC-i/is headers) not exceeding the size as signalled by the IE "Max MAC-e PDU contents size".

2> if the IE "Scheduled transmission grant info" is included:

3> transmission of MAC-d PDU’s for logical channels belonging to this MAC-d flow shall be in accordance with the received scheduled grant on E-AGCH/E-RGCH (see [15]).

1> for TDD:

2> if the IE "Non-scheduled transmission grant info" is included:

3> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall only be included in a MAC-e or MAC-i PDU transmitted by HARQ processes designated as non scheduled (Ids 4 – 7) in the TTIs indicated (for 3.84 Mcps TDD and 7.68 Mcps TDD, as determined from the IEs "Activation Time", "Resource Duration" and "Resource Periodicity"; for 1.28Mcps TDD, as determined from the IEs "Activation Time", "Subframe number", "Resource Duration" and "Resource Periodicity", and the calculation of assigned Non-scheduled transmission grant is specified in subclause 8.6.6.16a ).

2> if the IE "Scheduled transmission grant info" is included:

3> transmission of MAC-d PDUs for logical channels belonging to this MAC-d flow shall be in accordance with the received scheduled grant on E-AGCH (see [15]).

1> perform the actions as specified in subclause 8.5.21;

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

…

If the IE "Downlink information for each radio link" is included in a received message, the UE shall:

1> if the UE would enter CELL_DCH state according to subclause 8.6.3.3 applied on the received message:

2> if the UE is in TDD mode and shared transport channels are assigned to the UE:

3> start to receive the indicated Secondary CCPCH.

2> if the UE is in TDD mode and no shared transport channels are assigned to the UE:

3> set the variable UNSUPPORTED_CONFIGURATION to TRUE.

2> For FDD:

3> if the IE "Serving HS-DSCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving HS-DSCH radio link and no longer consider any other radio link as serving HS-DSCH radio link.

2> For FDD:

3> if the IE "Serving E-DCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving E-DCH radio link and no longer consider any other radio link as serving E-DCH radio link.

3> if the IE "E-AGCH Info" is included for the serving E-DCH radio link:

4> store the newly received E-AGCH configuration.

NOTE: The UTRAN should always include the IE "E-AGCH info" if the serving E-DCH radio link indicated in the message is another radio link than the serving E-DCH radio link prior to the procedure.

3> if the IE "E-HICH information" is included:

4> store this E-HICH configuration for the concerning radio link.

3> if the IE "E-HICH information" is included or previously stored:

4> store this E-RGCH configuration for the concerning radio link, if included.

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

2> for TDD:

3> if the IE "E-AGCH Info" is included:

4> store the newly received E-AGCH configuration.

3> if the IE "E-HICH information" is included:

4> store the E-HICH configuration.

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

2> act on the other IEs contained in the IE "Downlink information for each radio link" as specified in subclause 8.6 applied on this radio link.

1> in addition, if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according to subclause 8.6.3.3 applied on the received message:

2> For FDD:

3> if the IE "Serving HS-DSCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving HS-DSCH radio link;

4> if the serving HS-DSCH radio link was another radio link than this radio link prior to reception of the message and the IE "H-RNTI" is not included:

5> clear the variable H_RNTI.

3> if the IE "Serving HS-DSCH radio link indicator" is set to ‘FALSE’ and this radio link was considered the serving HS-DSCH radio link prior to reception of this message:

4> no longer consider this radio link as the serving HS-DSCH radio link.

3> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25;

3> if the IE "Serving E-DCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving E-DCH radio link;

4> if the serving E-DCH radio link was another radio link than this radio link prior to reception of the message:

5> if the IE "New Primary E-RNTI" is not included:

6> clear the Primary E-RNTI stored in the variable E_RNTI.

5> if the IE "New Secondary E-RNTI" is not included:

6> clear the Secondary E-RNTI stored in the variable E_RNTI.

3> if the IE "Serving E-DCH radio link indicator" is set to ‘FALSE’ and this radio link was considered the serving E-DCH radio link prior to reception of this message:

4> no longer consider this radio link as the serving E-DCH radio link.

3> if the IE "E-HICH release indicator" is present:

4> delete the stored E-HICH, E-AGCH and E-RGCH (if any) configurations.

3> if the IE "E-RGCH release indicator" is present:

4> delete the stored E-RGCH configuration for this RL.

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

2> For TDD:

3> if the IE "H-RNTI" is not included and the primary CCPCH has changed:

4> clear the variable H_RNTI.

3> determine the value for the HS-DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.

2> for TDD:

3> if the IE "New Primary E-RNTI" is not included:

4> clear the variable E_RNTI.

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

2> for each optional IE part of the IE "Downlink information for each radio link" that is not present:

3> do not change its current downlink physical channel configuration corresponding to the IE, which is absent, if not stated otherwise elsewhere.

NOTE: The Release ’99 RADIO BEARER RECONFIGURATION message always includes at least one IE "Downlink information for each radio link" containing the mandatory IEs, even if UTRAN does not require the reconfiguration of any radio link.

1> if the UE would enter either the CELL_FACH, CELL_PCH or URA_PCH state according to subclause 8.6.3.3 applied on the received message:

2> if IEs other than the IE "Primary CPICH info" (for FDD) or the IE "Primary CCPCH info" (for TDD) are included in the IE "Downlink information for each radio link":

3> ignore these IEs.

2> act on the other IEs contained in the IE "Downlink information for each radio link" as specified in subclause 8.6 applied on this radio link.

…

If the IE "E-DCH Info" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> for FDD:

2> if the IE "E-DPCCH Info" is included:

3> store the newly received E-DPCCH configuration.

2> if the IE "E-DPDCH Info" is included:

3> store the newly received E-DPDCH configuration.

2> if the IE "UL 16QAM settings" is not included:

3> indicate to lower layers to stop any operation in 16QAM mode.

1> for 3.84/7.68 Mcps TDD:

2> if the IE "E-RUCCH Info" is included:

3> store the newly received E-RUCCH configuration.

2> if the IE "E-PUCH Info" is included:

NOTE 1: The UTRAN should ensure the ordering of the E-TFCI table in strictly increasing order of transmission power prior to quantization, by correct setting of the reference E-TFCI power offsets otherwise the UE behaviour is unspecified.

NOTE 2: If a reference E-TFCI signalled to the UE is outside the UE physical channel capability, the UE behaviour is unspecified.

NOTE 2a: If E-TFCI boost is signalled to the UE and a reference E-TFCI <= E-TFCI Boost is signalled to the UE with a Reference E-TFCI PO of value 30 or 31, the UE behaviour is unspecified.

1> if the IE "MAC-es/e reset indicator" is included:

2> reset the MAC-es/e or MAC-i/is entity [15].

NOTE 3: If the IE "MAC-es/e reset indicator" is not set to TRUE in case the IE "E-DCH Transmission Time Interval" is reconfigured, the UE behaviour is unspecified.

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall:

1> for FDD:

2> configure the UL E-DPCCH in accordance with the stored IE "E-DPCCH" configuration;

2> configure the MAC with the stored IE "E-DPDCH" configuration and/or the information contained in IE "Scheduled Transmission configuration".

1> for TDD:

2> configure the E-RUCCH with the stored E-RUCCH configuration;

2> configure the MAC with the stored E-PUCH configuration.

Reference

3GPP TS 25.331 clauses 8.5.28, 8.6.3.14, 8.6.5.5, 8.6.5.16, 8.6.5.17, 8.6.5.18, 8.6.6.4, 8.6.6.37

8.1.2.17.3 Test purpose

To confirm that the UE establishes a signalling radio bearer mapped to HS-DSCH and E-DCH according to the received RRC CONNECTION SETUP message.

8.1.2.17.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Registered Idle Mode on PS (state 3), or CS/PS (state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Related ICS/IXIT statement(s)

– UE supports FDD or TDD

– UE supports HS-PDSCH

– UE supports E-DPDCH (FDD) or E-PUCH (TDD)

– UE fully supports F-DPCH (FDD only)

Test Procedure

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST	The SS prompts the operator makes an out-going call. The UE shall transmit this message, indicating the proper establishment cause.
2			RRC CONNECTION SETUP
3			RRC CONNECTION SETUP COMPLETE
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

RRC CONNECTION REQUEST (Step 1)

The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:

Information Element	Value/remark
Initial UE identity	Registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or OriginatingSubscribedTrafficCall.

RRC CONNECTION SETUP (Step 2)

Use the same message as specified for "Stand-alone SRBs mapped on E-DCH and HS-DSCH" in 34.108.

RRC CONNECTION SETUP COMPLETE (Step 3)

Use the same message sub-type found in clause 9 of TS 34.108

8.1.2.17.5 Test requirements

After step 2, the UE shall transmit a RRC CONNECTION SETUP COMPLETE message.

8.1.2.18 RRC Connection Establishment using the default configuration for HS-DSCH / E-DCH signalling bearers

8.1.2.18.1 Definition

All UEs which support FDD and HS-PDSCH and E-DCH and fully support F-DPCH or all UEs which support TDD and HS-PDSCH and E-PUCH.

8.1.2.18.2 Conformance requirement

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

—————-

2> if IE "Specification mode" is set to "Preconfiguration" and IE "Preconfiguration mode" is set to "Default configuration":

3> initiate the radio bearer and transport channel configuration in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity";

3> initiate the physical channels in accordance with the received physical channel information elements.

NOTE: IE "Default configuration mode" specifies whether the FDD or TDD version of the default configuration shall be used.

Reference

3GPP TS 25.331 clause 8.1.3.6, clause 13.7

8.1.2.18.3 Test purpose

To confirm that the UE establishes the radio bearer and transport channel configuration for HS-DSCH / E-DCH signalling radio bearers in accordance with the stored default parameters as identified by the IE “Default configuration identity” specified in the RRC Connection Setup Message

8.1.2.18.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Related ICS/IXIT statement(s)

– UE supports FDD or TDD

– UE supports HS-PDSCH

– UE supports E-DPDCH (FDD) or E-PUCH (1.28Mcps TDD)

– UE fully supports F-DPCH (FDD only)

Test Procedure

The UE shall transmit a RRC CONNECTION REQUEST message to the SS on the uplink CCCH, after the operator attempts to make an outgoing call. SS shall send a RRC CONNECTION SETUP message that contains the stored default configuration identity 17 (for standalone HS-DSCH / E-DCH signalling radio bearers). The UE accepts the message, configuring the radio bearer and transport channel configuration in accordance with the stored default parameters and acknowledge the establishment of RRC connection by sending the RRC CONNECTION SETUP COMPLETE message on uplink DCCH.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				Operator is asked to make an outgoing call.
2			RRC CONNECTION REQUEST
3			RRC CONNECTION SETUP	DefaultConfigIdentity used is ‘17’
4			RRC CONNECTION SETUP COMPLETE
5			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

RRC CONNECTION REQUEST (Step 2)

The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:

Information Element	Value/remark
Initial UE identity	Same as the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or OriginatingSubscribedTrafficCall.

RRC CONNECTION SETUP (Step 3) (FDD)

Use the same message sub-type found in clause 9 of TS 34.108 (Transition to CELL_DCH), for condition "Stand-alone SRBs mapped on E-DCH and HS-DSCH" with the following exceptions:

Information Element	Value/remark
Choice Specification Mode	Preconfiguration
– Choice Preconfig Mode	Default Config
– Default Config Mode	FDD
-Default Config Identity	17

RRC CONNECTION SETUP (Step 3) (1.28Mcps TDD)

Use the same message sub-type found in clause 9 of TS 34.108 (Transition to CELL_DCH), for condition "Stand-alone SRBs mapped on E-DCH and HS-DSCH" with the following exceptions:

Information Element	Value/remark
Choice Specification Mode	Preconfiguration
– Choice Preconfig Mode	Default Config
– Default Config Mode	TDD
-Default Config Identity	17

RRC CONNECTION SETUP COMPLETE (Step 4)

Use the same message sub-type found in clause 9 of TS 34.108

8.1.2.18.5 Test requirement

At step 4 the UE shall transmit a RRC CONNECTION SETUP COMPLETE message on Radio Bearer Id: 2 and establish an RRC connection.

8.1.2.19 RRC Connection Establishment for transition from Idle Mode to CELL_DCH: Success (start of discontinuous uplink transmission and downlink reception)

8.1.2.19.1 Definition and applicability

All UEs which support FDD and UL DTX.

8.1.2.19.2 Conformance requirement

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

…

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per subclause 8.6.3.3, with the contents set as specified below:

…

If the UE receives RRC CONNECTION SETUP, ACTIVE SET UPDATE, CELL UPDATE CONFIRM, or any reconfiguration message:

1> the UE shall determine the value for the DTX_DRX_STATUS variable.

The variable DTX_DRX_STATUS shall be set to TRUE only when all the following conditions are met:

1> the UE is in CELL_DCH state;

1> both variables HS_DSCH RECEPTION and E_DCH_TRANSMISSION are set to TRUE;

1> no DCH transport channel is configured;

1> the variable DTX_DRX_PARAMS is set;

1> the UE has received the IE "DTX-DRX timing information".

If any of the above conditions is not met and the variable DTX_DRX_STATUS is set to TRUE, the UE shall:

1> set the variable DTX_DRX_STATUS to FALSE;

1> clear the variable DTX_DRX_PARAMS;

1> stop DTX-DRX mode related activities.

If variable DTX_DRX_STATUS is set to true and the serving HS-DSCH cell was changed as a result of the received message the UE shall instruct the physical layer to consider HS-SCCH orders were never received.

Whenever the variable DTX_DRX_STATUS is set to TRUE after receiving this message and the value of IE "DTX-DRX timing information" included in this message is not "Continue", the UE shall:

1> if the variable DTX_DRX_STATUS was set to TRUE before receiving this message:

2> re-configure the physical layer to perform discontinuous uplink DPCCH transmission and enable discontinuous downlink reception operations according to the variable DTX_DRX_PARAMS at the CFN corresponding to the frame boundary that is offset by the value of the IE "Enabling Delay" from the frame boundary where uplink transmission starts with new configuration;

2> let the MAC layer continue with the current restriction on E-DCH transmission and monitoring of absolute and relative grant channels from the frame boundary where the uplink transmission starts with the new configuration and for the duration of the IE "Enabling Delay".

1> else:

2> perform discontinuous uplink DPCCH transmission and enable discontinuous downlink reception operations by configuring the physical layer according to the variable DTX_DRX_PARAMS at the CFN corresponding to the frame boundary that is offset by the value of the IE "Enabling Delay" from the frame boundary where uplink transmission starts with new configuration.

1> configure the MAC layer to start restricting E-DCH transmissions and monitor absolute and relative grant channels at the CFN corresponding to the frame boundary that is offset by the value of IE "Enabling Delay" from the frame boundary where uplink transmission starts with new configuration taking into account the IEs "UE DTX DRX Offset", "MAC DTX Cycle", "MAC Inactivity Threshold" and "Inactivity Threshold for UE Grant Monitoring".

…

If the IE "DTX-DRX timing information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "timing" is set to "New timing":

2> use the newly received DTX-DRX timing configuration.

1> determine the value for the DTX_DRX_STATUS variable and take the corresponding actions as described in subclause 8.5.34.

…

If the IE "DTX–DRX information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> store the contents of the IE in the variable DTX_DRX_PARAMS;

1> determine the value for the DTX_DRX_STATUS variable and take the corresponding actions as described in subclause 8.5.34;

1> if the value of the IE "UE DTX cycle 2" is not an integer multiple of the value of the IE "UE DTX cycle 1"; or

1> if the value of the IE "UE DTX cycle 2" is not an integer multiple or a divisor of the value of the IE "CQI Feedback cycle, k"; or

1> if the value of the IE "UE DPCCH burst 1" is greater than the value of the IE "UE DTX cycle 1"; or

1> if the value of the IE "UE DPCCH burst 2" is greater than the value of the IE "UE DTX cycle 2"; or

1> if the IE "UE DTX long preamble length" is set to 4 or 15 slots and the value of the IE "Inactivity Threshold for UE DTX cycle 2" is less than 4 TTIs (for 10ms E-DCH TTI) or 8 TTIs (for 2ms E-DCH TTI); or

1> if the IE "UE DRX cycle" is not an integer multiple or a divisor of the value of the IE "UE DTX cycle 1"; or

1> if the IE "DRX Information" is included in this message while the IE "DTX information" is not included in this message; or

1> if the value of the IE "UE DTX cycle 1" is not an integer multiple or a divisor of the value of the IE "MAC DTX cycle":

2> the UE behaviour is unspecified.

Reference

3GPP TS 25.331 clauses 8.1.3.6, 8.5.34, 8.6.6.38, 8.6.6.39

8.1.2.19.3 Test purpose

To confirm that the UE establishes a signalling radio bearer mapped to HS-DSCH and E-DCH, with discontinuous transmission and reception according to the received RRC CONNECTION SETUP message.

8.1.2.19.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Registered Idle Mode on PS (state 3), or CS/PS (state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Related ICS/IXIT statement(s)

– UE supports FDD

– UE supports DPCCH Discontinuous Transmission

Test Procedure

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH, after the test operator makes an out-going call. The SS transmits a RRC CONNECTION SETUP message to the UE. This message requests the establishment of a signalling radio bearer with SRB mapping to HS-DSCH and E-DCH and provides DTX and DRX parameters. After the UE receives this message, it establishes a signalling radio bearer and maps it to the HS-DSCH (with DRX enabled if supported) and E-DCH (with DTX enabled). Finally the UE transmits a RRC CONNECTION SETUP COMPLETE message using AM RLC. The SS waits to allow sufficient time for DTX cycle 2 to be active, and CQI DTX Timer to expire, and then verifies that the time between 11 consecutive CQI indications is 400ms. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			RRC CONNECTION REQUEST	The SS prompts the operator makes an out-going call. The UE shall transmit this message, indicating the proper establishment cause.
2			RRC CONNECTION SETUP	Requests establishment of SRBs mapped to HS-DSCH/E-DCH with DTX-DRX information,
3			RRC CONNECTION SETUP COMPLETE
4	SS			The SS waits to allow sufficient time for DTX cycle 2 to be active, and CQI DTX Timer to expire, and then verifies that the time between 11 consecutive CQI indications is 400ms (i.e. duration of 10 consecutive DTX cycle 2).
5			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

RRC CONNECTION REQUEST (Step 1)

The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:

Information Element	Value/remark
Initial UE identity	Registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or OriginatingSubscribedTrafficCall.

RRC CONNECTION SETUP (Step 2)

Use the same message as specified for "Stand-alone SRBs mapped on E-DCH and HS-DSCH" in 34.108, with the following exceptions:

Information Element	Value/remark
Added or Reconfigured UL TrCH information
– Uplink transport channel type	E-DCH
– CHOICE UL parameters	E-DCH
– E-DCH Transmission Time Interval	10ms
DTX-DRX timing information
CHOICE timing
– New timing
– Enabling Delay	16
– UE DTX DRX Offset	0
DTX-DRX Information
DTX information
– CHOICE E-DCH TTI length	10ms
– UE DTX cycle 1	10
– UE DTX cycle 2	20
– MAC DTX cycle	10
– Inactivity Threshold for UE DTX cycle 2	8
– UE DTX long preamble length	4
– MAC Inactivity Threshold	8
– CQI DTX Timer	32
– UE DPCCH burst_1	1
– UE DPCCH burst_2	1
DRX Information
– UE DRX cycle	10
– Inactivity Threshold for UE DRX cycle	32
– Inactivity Threshold for UE Grant Monitoring	8
– UE DRX Grant Monitoring	TRUE
Uplink DPCCH slot format information	1

RRC CONNECTION SETUP COMPLETE (Step 3)

Use the same message sub-type found in clause 9 of TS 34.108

8.1.2.19.5 Test requirements

At step 3, the UE shall transmit a RRC CONNECTION SETUP COMPLETE message.

At step 4 the time between 11 consecutive CQI indications shall be 400ms.

8.1.2.20 RRC Connection Establishment for transition from Idle Mode to CELL_FACH: Success (Start of HS-DSCH Reception)

8.1.2.20.1 Definition and applicability

All UEs which support FDD and HS-PDSCH in CELL_FACH.

8.1.2.20.2 Conformance requirement

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

…

1> if the UE supports HS-DSCH reception in CELL_FACH state:

2> include the IE "HS-PDSCH in CELL_FACH" and set it to TRUE.

…

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

…

2> if IE "Specification mode" is set to "Complete specification":

…

3> if the IE "HS-DSCH common system information" is not included in System Information Block type 5 or System Information Block type 5bis:

4> select Secondary CCPCH according to subclause 8.5.19;

3> else:

4> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE;

4> if the RBs have the multiplexing option with transport channel type "HS-DSCH" for the DL and transport channel type “RACH” in the UL; and

4> if "new H-RNTI" and "new C-RNTI" are included:

5> store the "new H-RNTI" according to subclause 8.6.3.1b;

5> store the "new C-RNTI" according to subclause 8.6.3.9;

5> and start to receive HS-DSCH according to the procedure in subclause 8.5.36.

4> else:

5> clear variable C_RNTI and delete any stored C-RNTI value;

5> clear variable H_RNTI and delete any stored H-RNTI value;

5> clear any stored IE "HARQ Info";

5> set the variable INVALID_CONFIGURATION to TRUE.

…

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per subclause 8.6.3.3, with the contents set as specified below:

2> set the IE "RRC transaction identifier" to:

3> the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; and

3> clear that entry.

2> if the USIM or SIM is present:

3> set the "START" for each CN domain in the IE "START list" in the RRC CONNECTION SETUP COMPLETE message with the corresponding START value that is stored in the USIM [50] if present, or as stored in the UE if the SIM is present; and then

3> set the START value stored in the USIM [50] if present, and as stored in the UE if the SIM is present for any CN domain to the value "THRESHOLD" of the variable START_THRESHOLD.

…

The variable HS_DSCH_RECEPTION_CELL_FACH_STATE shall be set to TRUE only when all the following conditions are met:

1> the UE is in CELL_FACH;

1> the variable H_RNTI is set;

1> the variable C_RNTI is set;

1> System Information Block type 5 or System Information Block type 5bis includes IE "HS-DSCH common system information".

If any of the above conditions is not met and the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, the UE shall:

1> set the variable HS_DSCH_RECEPTION_CELL_FACH_STATE to FALSE;

1> if the UE is in CELL_FACH and variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to FALSE:

2> set the variable HS_DSCH_RECEPTION_GENERAL to FALSE;

2> stop any HS_SCCH reception procedures;

2> stop any HS-DSCH reception procedures;

2> clear the variable H_RNTI and remove any stored H-RNTI;

2> reset the MAC-ehs entity [15];

2> release all HARQ resources;

2> clear any stored IEs "HARQ info";

Whenever the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, the UE shall:

1> set the variable HS_DSCH_RECEPTION_GENERAL to TRUE;

1> use the IE "HS-DSCH common system information" in System Information Block type 5 or System Information Block type 5bis;

1> receive the HS-SCCH(s) according to the IE "HS-SCCH channelization code" on the serving cell applying the scrambling code as received in the IE "DL Scrambling code" as received in IE "HS-DSCH common system information";

1> perform HS-DSCH reception procedures:

2> if the UE has a stored IE "HARQ info":

3> act on subclause 8.6.5.6b for the stored IE "HARQ info".

2> else:

3> act on subclause 8.6.5.20 for the IE "HARQ System info" as received in IE "HS-DSCH common system information".

2> and use the value of the variable H_RNTI as UE identity in the HS-SCCH reception procedure in the physical layer.

1> and for BCCH reception perform HS-DSCH reception procedures by listening to the first indexed HS-SCCH code listed in the IE "HS-SCCH channelization code" with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

Whenever the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to FALSE, the UE shall:

1> if the UE is in CELL_FACH and variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to FALSE:

2> not perform HS_SCCH reception procedures;

2> not perform HS-DSCH reception procedures.

…

When UE does not support HS-DSCH reception or when the IE "HS-DSCH common system information" is not included in System Information Block type 5 or System Information Block type 5bis, the UE shall:

1> set HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE;

1> set the variable HS_DSCH_RECEPTION_GENERAL to FALSE.

When HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE, the UE shall:

1> set the variable HS_DSCH_RECEPTION_GENERAL to TRUE;

1> use the IE "HS-DSCH common system information" in System Information Block type 5 or System Information Block type 5bis;

1> configure the HARQ according to IE "HARQ System info" as defined in subclause 8.6.5.20;

1> configure the common MAC-ehs reordering queues according to IE "Common MAC-ehs reordering queues" as defined in subclauses 8.6.5.22; and then

1> receive the CCCH according to IE "CCCH mapping info" as defined in subclause 8.6.5.21;

1> if the UE is RRC Connected mode:

2> select a common H-RNTI as specified in 8.5.38;

2> receive the SRB1 according to IE "SRB1 mapping info" as defined in subclause 8.6.5.19.

1> else:

2> select a common H-RNTI as specified in [4].

1> and start to receive the HS-SCCH(s) with selected H-RNTI according to the IE "HS-SCCH channelization code" on the selected cell applying the scrambling code as received in the IE "DL Scrambling code";

1> configure the MAC flow for BCCH reception as specified in [15];

1> and start to receive the first indexed HS-SCCH code listed in the IE "HS-SCCH channelization code" with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

Reference

3GPP TS 25.331 clauses 8.1.3.3, 8.1.3.6, 8.5.36, 8.5.37

8.1.2.20.3 Test purpose

To confirm that the UE establishes a signalling radio bearer mapped to HS-DSCH and RACH according to the received RRC CONNECTION SETUP message.

8.1.2.20.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Registered Idle Mode on PS (state 3), or CS/PS (state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Related ICS/IXIT statement(s)

– UE supports FDD

– UE supports HS-PDSCH in CELL_FACH

Test Procedure

The SS transmits System Information Type 5 including configuration for HS-DSCH reception in CELL_FACH state.

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH, after the test operator makes an out-going call.

The SS transmits a RRC CONNECTION SETUP message to the UE on RB0 mapped to HS-DSCH. This message requests the establishment of a signalling radio bearer with SRB mapping to HS-DSCH and RACH. After the UE receives this message, it establishes a signalling radio bearer and maps it to the HS-DSCH and RACH. Finally the UE transmits a RRC CONNECTION SETUP COMPLETE message using AM RLC on the RACH channel.

SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
0			SYSTEM INFORMATION TYPE 5	Includes configuration for HS-DSCH reception in CELL_FACH state
1			RRC CONNECTION REQUEST	The SS prompts the operator makes an out-going call. The UE shall transmit this message, indicating the correct establishment cause and support of HS-PDSCH in CELL_FACH
2			RRC CONNECTION SETUP	Transmitted on HS-DSCH, requests establishment of SRBs mapped to HS-DSCH/RACH,
3			RRC CONNECTION SETUP COMPLETE
4			CALL C.2	If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails.

Specific Message Contents

SYSTEM INFORMATION TYPE 5

Use default message in 34.108 section 6.1.0b, condition B1.RRC CONNECTION REQUEST (Step 1)

Use the same message type found in clause 9 of TS 34.108, with the following exceptions.

Information Element	Value/remark
Initial UE identity	Same as the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or OriginatingSubscribedTrafficCall
HS-PDSCH in CELL_FACH	Check to see if set to TRUE

RRC CONNECTION SETUP (Step 2)

Use default message in 34.108 section 9.1.1, condition A4.RRC CONNECTION SETUP COMPLETE (Step 3)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
UE Radio Access Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE radio access capability extension	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE system specific Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.

8.1.2.20.5 Test requirements

After step 3 the UE shall establish the RRC connection, and transmit RRC CONNECTION SETUP COMPLETE message on the DCCH using PRACH physical resource specified in system information block messages.

8.1.2.21 RRC Connection Establishment: Reject with Frequency Info set to the same frequency band – Successful case

8.1.2.21.1 Definition

8.1.2.21.2 Conformance requirement

If the values are different, the UE shall ignore the rest of the message;

If the values are identical, the UE shall:

1> stop timer T300 or T318, whichever one is running; and

1> clear the entry for the RRC CONNECTION REJECT message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> if the UE has disabled cell reselection to a UTRA carrier due to an earlier RRC CONNECTION REJECT message, the UE shall resume cell reselection to that UTRA carrier;

1> if the Rejection Cause is ‘unspecified’ and the IE "Counting Completion" is present, the UE shall terminate an ongoing MBMS counting procedure according to subclause 8.7.4.4;

1> if the IE "wait time" <> ‘0’; and

1> if the IE "frequency info" is present and:

2> if V300 is equal to or smaller than N300:

3> select a suitable UTRA cell according to [4] on that frequency;

3> after having selected and camped on a suitable cell on the designated UTRA carrier:

4> set CFN in relation to SFN of current cell according to subclause 8.5.15;

4> set the contents of the RRC CONNECTION REQUEST message according to subclause 8.1.3.3;

4> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH or the common E-DCH (for the Enhanced Uplink in CELL_FACH and Idle mode);

4> transmit an RRC CONNECTION REQUEST message on the uplink CCCH;

4> reset counter V300;

4> start timer T300 when the MAC layer indicates success or failure in transmitting the message;

4> disable cell reselection to original UTRA carrier until the time stated in the IE "wait time" has elapsed or until the RRC connection establishment procedure ends, whichever occurs first;

Reference

3GPP TS 25.331 clause 8.1.3.9.

8.1.2.21.3 Test purpose

To confirm that the UE retries to establish RRC connection in a suitable cell on the designated UTRA carrier, if it receives an RRC CONNECTION REJECT message including the optional IE "redirection info" referencing frequencies in the same band, but having different Qrxlevmin values and if a suitable cell on the designated UTRA carrier is found.

8.1.2.21.4 Method of test

Initial Condition

System Simulator: 2 cells – both cell 1 and cell 4 are active and cell 1 is suitable for camping.

Table 8.1.2.21Parameter	Unit	Cell 1				Cell 4
	Unit	T0	T1	T2	T3	T0	T1	T2		T3
UTRA RF Channel Number		Mid Range Test Frequency				High Range Test Frequency
CPICH Ec (FDD)	dBm/3.84 MHz	-60	-60	-60	-60	Non Suitable	-70		Off	-70
Qrxlevmin	dBm	-89				-79

UE: Switched off (state 1 as specified in clause 7.4 of TS 34.108).

Related ICS/IXIT statement(s)

None

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

Use same message sub-clause 6.1 of TS 34.108, with following exception:

Information Element	Value/remark
SIB12 indicator	FALSE
Measurement control system information
– Intra-frequency measurement system information
– Intra-frequency reporting quantity for RACH reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode	FDD
– Reporting quantity	CPICH Ec/N0
– Maximum number of reported cells on RACH	Current Cell
– Reporting information for state CELL_DCH	Not present

Test Procedure

SS adjusts the power setting for the cells according to “T0” in table 8.1.2.21. The UE is switched on.

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH for registration on cell 1. SS makes cell 4 suitable before SS rejects the first request by transmitting an RRC CONNECTION REJECT message which includes the IE “Redirection Info” indicating frequency information for cell 4. SS then waits for RRC CONNECTION REQUEST message on the uplink CCCH of cell 4. SS will also monitor the uplink of cell 1 simultaneously to ensure that all transmission activities from cell 1 have ceased. When the UE has successfully selected cell 4, it shall send an RRC CONNECTION REQUEST with the same establishment cause as its previous attempt in cell 1. Finally, SS transmits an RRC CONNECTION SETUP message to establish an RRC connection with the UE, and the UE replies with an RRC CONNECTION SETUP COMPLETE message. UE is brought to Idle state (state 2 or state 3 or state 7) in cell 4 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE andis made to perform a Detach in cell 4 followed by switching off the UE .SS adjust the power setting for cells according to “T2” in table 8.1.2.21.

The UE is switched on and brought to Idle state (state 2 or state 3 or state 7) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. SS adjusts the power setting for the cells accordingly to “T3” in table 8.1.2.21. The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by an outgoing call operation in cell 1. SS rejects the first request by transmitting an RRC CONNECTION REJECT message which includes the IE “Redirection Info” indicating frequency information for cell 4. SS will also monitor the uplink of cell 1 simultaneously to ensure that all transmission activities from cell 1 have ceased. When the UE has successfully selected cell 4, it shall send an RRC CONNECTION REQUEST with the same establishment cause as its previous attempt in cell 1. Finally, SS transmits an RRC CONNECTION SETUP message to establish an RRC connection with the UE, and the UE replies with an RRC CONNECTION SETUP COMPLETE message.

NOTE: If the UE fails the test because of a failure to reselect to the right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1	UE			The UE is powered up or switched on, (see ICS)
2			RRC CONNECTION REQUEST	The establishment cause must be “Registration”
2a				SS adjusts cell levels according to column T1.
3			RRC CONNECTION REJECT	This message shall include the IE "wait time" set to 5 seconds and IE "frequency info" set to the UARFCN of cell 4. Note: this wait time would apply after failure of the inter frequency cell re- selection, which is not verified in this test case
4				SS waits for a period of time sufficient for UE to select to cell 4. At the same time, it monitors the uplink of cell 1 to make sure that all transmissions have ceased.
5			RRC CONNECTION REQUEST	UE shall attempt to re-start an RRC connection establishment procedure in cell 4. The establishment cause shall remain unchanged.
6			RRC CONNECTION SETUP	SS sends the message to UE to setup an RRC connection with the UE.
7				The UE shall configure the layer 2 and layer 1 in order to access the uplink and downlink DCCH assigned.
8			RRC CONNECTION SETUP COMPLETE
9				UE is brought to Idle state (state 2 or state 3 or state 7) in cell 4 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE UE is made to perform a Detach in cell 4 followed by switching off the UE
10				The SS switches its downlink transmission power settings to columns "T2" in table 8.1.2.21.
11				UE is switched on and brought to Idle state (state 2 or state 3 or state 7) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. The SS switches its downlink transmission power settings to columns "T3" in table 8.1.2.21.
12			RRC CONNECTION REQUEST	SS prompts the operator to make an outgoing call in cell 1.
13			RRC CONNECTION REJECT	This message shall includes the IE "wait time" set to 5 seconds and IE "frequency info" set to the UARFCN of cell 4. Note: this wait time would apply after failure of the inter frequency cell re- selection, which is not verified in this test case
14				SS waits for a period of time sufficient for UE to select to cell 4. At the same time, it monitors the uplink of cell 1 to make sure that all transmissions have ceased.
15			RRC CONNECTION REQUEST	UE shall attempt to start an RRC connection establishment procedure in cell 4. The establishment cause shall be same as the one sent in step 10.
16			RRC CONNECTION SETUP	SS sends the message to UE to setup an RRC connection with the UE.
17				The UE shall configure the layer 2 and layer 1 in order to access the uplink and downlink DCCH assigned.
18			RRC CONNECTION SETUP COMPLETE
19			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

RRC CONNECTION REQUEST (Step 2 and Step 5)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Same as the IMSI stored in the TEST USIM card, or the previously registered TMSI or P-TMSI
Establishment Cause	Must be "Registration"

RRC CONNECTION REJECT (Step 3 and Step 13)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Rejection cause Wait time	Congestion 5 seconds
Redirection Info
– Frequency Info
– CHOICE mode	FDD
– UARFCN uplink (Nu)	Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink (Nd)	Set to the UARFCN for downlink carrier of cell 4

RRC CONNECTION REQUEST (Step 12 and Step 15)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Same as the registered TMSI or P-TMSI
Establishment Cause	Must be "Originating Call"

8.1.2.21.5 Test requirement

After step 4 the UE shall have successfully selected cell 4. UE shall trigger the start of RRC connection establishment by transmitting RRC CONNECTION REQUEST. The establishment cause shall be registration.

In step 8, the UE shall send the RRC CONNECTION SETUP COMPLETE message on the frequency indicated in the RRC CONNECTION SETUP message.

After step 14 the UE shall have successfully selected to cell 4. UE shall trigger the start of RRC connection establishment by transmitting RRC CONNECTION REQUEST. The establishment cause shall be originating call.

In step 18, the UE shall send the RRC CONNECTION SETUP COMPLETE message on the frequency indicated in the RRC CONNECTION SETUP message.

8.1.2.21a RRC Connection Establishment: Reject with Frequency Info set to a different frequency band – Successful case

8.1.2.21a.1 Definition

This test case is identical to test case 8.1.2.21 except that the RRC CONNECTION REJECT message shall indicate a cell on a different frequency band and a different IE “Wait time”.

8.1.2.21a.2 Conformance requirement

Same conformance requirement as in clause 8.1.2.21.2.

8.1.2.21a.3 Test purpose

Same test purpose as in clause 8.1.2.21.3 except that the optional IE "redirection info" is on a different frequency band.

8.1.2.21a.4 Method of test

Initial Condition

Same initial conditions as in clause 8.1.2.21.4 except that cells 1 and 4 use the UARFCNs in two different frequency bands. The frequency bands for cell 1 and cell 4 are selected according to PIXIT parameter.

Related ICS/IXIT statement(s)

– UE supports multiple bands simultaneously yes/no

Specific message content

Same specific message content for system information as in clause 8.1.2.21.4.

Test Procedure

Same test procedure as in clause 8.1.2.21.4.

NOTE: If the UE supports more than 2 frequency bands, the test may be executed for various band combinations.

Specific Message Contents

Same specific message content as in clause 8.1.2.21.4 except:

RRC CONNECTION REJECT (Step 3 and Step 13)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Rejection cause Wait time	Congestion 15 seconds
Redirection Info
– Frequency Info
– CHOICE mode	FDD
– UARFCN uplink (Nu)	Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink (Nd)	Set to the UARFCN for downlink carrier of cell 4

8.1.2.21a.5 Test requirement

Same test requirement as in clause 8.1.2.21.5.

8.1.2.22 RRC Connection Establishment: Reject with Frequency Info set to the same frequency band – Unsuccessful case

8.1.2.22.1 Definition

8.1.2.22.2 Conformance requirement

If the values are different, the UE shall ignore the rest of the message;

If the values are identical, the UE shall:

1> stop timer T300 or T318, whichever one is running; and

1> clear the entry for the RRC CONNECTION REJECT message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> if the UE has disabled cell reselection to a UTRA carrier due to an earlier RRC CONNECTION REJECT message, the UE shall resume cell reselection to that UTRA carrier;

1> if the Rejection Cause is ‘unspecified’ and the IE "Counting Completion" is present, the UE shall terminate an ongoing MBMS counting procedure according to subclause 8.7.4.4;

1> if the IE "wait time" <> ‘0’; and

1> if the IE "frequency info" is present and:

2> if V300 is equal to or smaller than N300:

3> select a suitable UTRA cell according to [4] on that frequency;

3> after having selected and camped on a suitable cell on the designated UTRA carrier:

4> set CFN in relation to SFN of current cell according to subclause 8.5.15;

4> set the contents of the RRC CONNECTION REQUEST message according to subclause 8.1.3.3;

4> transmit an RRC CONNECTION REQUEST message on the uplink CCCH;

4> reset counter V300;

4> start timer T300 when the MAC layer indicates success or failure in transmitting the message;

disable cell reselection to original UTRA carrier until the time stated in the IE "wait time" has elapsed or until the RRC connection establishment procedure ends, whichever occurs first;

3> if no suitable cell on the designated UTRA carrier is found:

4> wait for at least the time stated in the IE "wait time";

4> set CFN in relation to SFN of current cell according to subclause 8.5.15;

4> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.3;

4> then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH of the original serving cell;

4> increment counter V300;

4> restart timer T300 when the MAC layer indicates success or failure to transmit the message;

2> if V300 is greater than N300:

3> enter idle mode;

3> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode;

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.3.9.

8.1.2.22.3 Test purpose

To confirm that the UE retries to establish RRC connection in the original serving cell, if it receives an RRC CONNECTION REJECT message including the optional IE "redirection info" referencing frequencies in the same band, but having different Qrxlevmin values and if no suitable cell on the designated UTRA carrier is found.8.1.2.22.4 Method of test

Initial Condition

System Simulator: 2 cells – cell 1 is active and suitable for camping and cell 4 is non-suitable cell. Cell 1 is transmitted using a larger power. The transmission power of cell 4 is 6 dB lower than the default and the Qrxlevmin of cell 4 is 10dB higher than that of cell 1.

Table 8.1.2.22

Parameter	Unit	Cell 1	Cell 4
UTRA RF Channel Number		Mid Range Test Frequency	High Range Test Frequency
CPICH Ec (FDD)	dBm/3.84 MHz	-60	-66
Qrxlevmin	dBm	-69	-59

Switched off (state 1 as specified in clause 7.4 of TS 34.108).

Related ICS/IXIT statement(s)

None.

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

Use same message sub-clause 6.1 of TS 34.108, with following exception:

Information Element	Value/remark
SIB12 indicator	FALSE
Measurement control system information
– Intra-frequency measurement system information
– Intra-frequency reporting quantity for RACH reporting
– SFN-SFN observed time difference reporting indicator	No report
– CHOICE mode	FDD
– Reporting quantity	CPICH Ec/N0
– Maximum number of reported cells on RACH	Current Cell
– Reporting information for state CELL_DCH	Not present

Test Procedure

The UE is switched on.

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH for registration on cell 1. The SS rejects the first request by transmitting an RRC CONNECTION REJECT message which includes the IE “Redirection Info” indicating frequency information for cell 4. UE will not reselect to cell 4 as cell 4 does not satisfy cell selection criteria. It then waits for a second RRC CONNECTION REQUEST message and ensures that it is on the uplink CCCH of cell 1 and ensures that the “wait time” has been observed. Finally, the SS transmits an RRC CONNECTION SETUP message to establish an RRC connection with the UE, and the UE replies with an RRC CONNECTION SETUP COMPLETE message and enters CELL_DCH state. UE is brought to Idle state (state 2 or state 3 or state 7) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

NOTE: If the UE fails the test because of a failure to select to a right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1	UE			The UE is powered up or switched on, (see ICS)
2			RRC CONNECTION REQUEST	The establishment cause must be “Registration”
3			RRC CONNECTION REJECT	This message shall includes the IE "wait time" set to 5 seconds and IE "frequency info" set to the UARFCN of cell 4.
4				UE will not reselect to cell 4 as cell 4 does not satisfy cell selection criteria. SS checks that UE does not select cell 4 and send any access request on cell 4. The SS monitors the uplink of cell 1 for the duration specified in the IE “wait time” to make sure that all transmissions have ceased.
5			RRC CONNECTION REQUEST	UE shall send a second RRC connection request to cell 1. The establishment cause shall remain unchanged.
6			RRC CONNECTION SETUP	SS sends the message to UE to setup an RRC connection with the UE.
7				The UE shall configure the layer 2 and layer 1 in order to access the uplink and downlink DCCH assigned.
8			RRC CONNECTION SETUP COMPLETE
9				UE is brought to Idle state (state 2 or state 3 or state 7) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE
10			RRC CONNECTION REQUEST	SS prompts the operator to make an outgoing call in cell 1.
11			RRC CONNECTION REJECT	This message shall includes the IE "wait time" set to 5 seconds and IE "frequency info" set to the UARFCN of cell 4.
12				UE will not reselect to cell 4 as cell 4 does not satisfy cell selection criteria. SS checks that UE does not select cell 4 and send any access request on cell 4. The SS monitors the uplink of cell 1 for the duration specified in the IE “wait time” to make sure that all transmissions have ceased.
13			RRC CONNECTION REQUEST	UE shall attempt to start an RRC connection establishment procedure in cell 1. The establishment cause shall be same as the one sent in step 10.
14			RRC CONNECTION SETUP	SS sends the message to UE to setup an RRC connection with the UE.
15				The UE shall configure the layer 2 and layer 1 in order to access the uplink and downlink DCCH assigned.
16			RRC CONNECTION SETUP COMPLETE
17			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

RRC CONNECTION REQUEST (Step 2 and Step 5)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Same as the IMSI stored in the TEST USIM card, or the previously registered TMSI or P-TMSI
Establishment Cause	Must be "Registration"

RRC CONNECTION REJECT (Step 3 and Step 11)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Rejection cause Wait time	Congestion 5 seconds
Redirection Info
– Frequency Info
– CHOICE mode	FDD
– UARFCN uplink (Nu)	Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink (Nd)	Set to the UARFCN for downlink carrier of cell 4

RRC CONNECTION REQUEST (Step 10 and Step 13)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Initial UE Identity	Same as the registered TMSI or P-TMSI
Establishment Cause	Must be "Originating Call"

8.1.2.22.5 Test requirement

After step 3 the UE shall have determined that the redirection is not possible and adhere to the “wait time” before re-transmitting an RRC CONNECTION REQUEST. The establishment cause shall be registration.

In step 8, the UE shall send the RRC CONNECTION SETUP COMPLETE message on the frequency indicated in the RRC CONNECTION SETUP message.

After step 11 the UE shall have determined that the redirection is not possible and adhere to the “wait time” before re-transmitting an RRC CONNECTION REQUEST. The establishment cause shall be originating call.

In step 16, the UE shall send the RRC CONNECTION SETUP COMPLETE message on the frequency indicated in the RRC CONNECTION SETUP message.

8.1.2.22a RRC Connection Establishment: Reject with Frequency Info set to a different frequency band – Unsuccessful case

8.1.2.22a.1 Definition

This test case is identical to test case 8.1.2.22 except that the RRC CONNECTION REJECT message shall indicate a cell on a different frequency band and a different IE “Wait time”.

8.1.2.22a.2 Conformance requirement

Same conformance requirement as in clause 8.1.2.22.2.

8.1.2.22a.3 Test purpose

Same test purpose as in clause 8.1.2.22.3 except that the optional IE "redirection info" is on a different frequency band.

8.1.2.22a.4 Method of test

Initial Condition

Same initial conditions as in clause 8.1.2.22.4 except that cells 1and 4 use the UARFCNs in two different frequency bands. The frequency bands for cell 1 and cell 4 are selected according to PIXIT parameter.

Related ICS/IXIT statement(s)

– UE supports multiple bands simultaneously yes/no

Specific message content

Same specific message content for system information as in clause 8.1.2.22.4.

Test Procedure

Same test procedure as in clause 8.1.2.22.4.

NOTE: If the UE supports more than 2 frequency bands, the test may be executed for various band combinations.

Specific Message Contents

Same specific message content as in clause 8.1.2.22.4 except:

RRC CONNECTION REJECT (Step 3 and Step 11)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
Rejection cause Wait time	Congestion 15 seconds
Redirection Info
– Frequency Info
– CHOICE mode	FDD
– UARFCN uplink (Nu)	Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink (Nd)	Set to the UARFCN for downlink carrier of cell 4

8.1.2.22a.5 Test requirement

Same test requirement as in clause 8.1.2.22.5.

8.1.2.23 Void

8.1.2.23a Void

8.1.2.24 Void

8.1.2.24a Void

8.1.2.25 RRC Connection Establishment for transition from Idle Mode to CELL_FACH: Success (Start of E-DCH and HS-DSCH Reception)

8.1.2.25.1 Definition and applicability

All UEs which support 1.28Mcps TDD and E-DCH and HS-PDSCH in CELL_FACH.

8.1.2.25.2 Conformance requirement

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

…

1> if the UE supports MAC-ehs:

2> include the IE "MAC-ehs support" and set it to TRUE.

1> if the UE supports HS-DSCH reception in CELL_FACH state:

2> include the IE "HS-PDSCH in CELL_FACH" and set it to TRUE.

1> if the UE supports Enhanced Uplink in CELL_FACH state and Idle mode:

2> include the IE "Support of common E-DCH" and set it to TRUE.

NOTE: In 1.28 Mcps TDD, UE supporting HS-DSCH reception in CELL_FACH state always supports Enhanced Uplink in CELL_FACH state and Idle mode, and vice versa.

1> if the UE supports MAC-i/is:

2> include the IE "Support of MAC-i/is" and set it to TRUE.

…

The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY.

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

…

1> if IE "Default configuration for CELL_FACH" is set:

2> act in accordance with the default parameters according to section 13.8.

1> clear the variable ESTABLISHMENT_CAUSE;

1> for FDD and 1.28 Mcps TDD, if the HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE:

2> set the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE.

1> stop timer T300 or T318, whichever one is running, and act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following:

2> if the UE, according to subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of this procedure:

3> if the IE "Frequency info" is included:

4> select a suitable UTRA cell according to [4] on that frequency.

3> enter UTRA RRC connected mode;

3> determine the value for the READY_FOR_COMMON_EDCH variable and take the corresponding actions as described in subclause 8.5.47;

3> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46;

3> if variable READY_FOR_COMMON_EDCH is set to FALSE:

4> select PRACH according to subclause 8.5.17;

3> else:

4> configure the Enhanced Uplink in CELL_FACH state and Idle mode as specified in subclause 8.5.45 for FDD and 8.5.45a for 1.28 Mcps TDD.

3> for 3.84 Mcps and 7.68 Mcps TDD; or

3> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception in CELL_FACH state; or

3> if the IE "HS-DSCH common system information" is not included in System Information Block type 5 or System Information Block type 5bis; or

3> for 1.28 Mcps TDD, if the IE "Common E-DCH system info" is not included in System Information Block type 5:

4> select Secondary CCPCH according to subclause 8.5.19;

3> else:

4> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE;

4> For FDD if variable READY_FOR_COMMON_EDCH is set to FALSE:

5> if the RBs have the multiplexing option with transport channel type "HS-DSCH" for the DL and transport channel type “RACH” in the UL; and

5> if "new H-RNTI" and "new C-RNTI" are included:

6> store the "new H-RNTI" according to subclause 8.6.3.1b;

6> store the "new C-RNTI" according to subclause 8.6.3.9;

6> and start to receive HS-DSCH according to the procedure in subclause 8.5.36.

5> else:

6> clear variable C_RNTI and delete any stored C-RNTI value;

6> clear variable H_RNTI and delete any stored H-RNTI value;

6> clear any stored IE "HARQ Info";

6> set the variable INVALID_CONFIGURATION to TRUE.

4> else:

5> if the RBs have the multiplexing option with transport channel type "HS-DSCH" for the DL and transport channel type "E-DCH" in the UL; and

5> if the IEs "new Primary E-RNTI", "new H-RNTI" and "new C-RNTI" are included:

6> store the "new Primary E-RNTI" according to subclause 8.6.3.14;

6> store the "new H-RNTI" according to subclause 8.6.3.1b;

6> store the "new C-RNTI" according to subclause 8.6.3.9;

6> configure Enhanced Uplink in CELL_FACH state and Idle mode according to subclause 8.5.45 for FDD and 8.5.45a for 1.28 Mcps TDD;

6> and start to receive HS-DSCH according to the procedure in subclause 8.5.36.

5> else:

6> clear variable C_RNTI and delete any stored C-RNTI value;

6> clear variable H_RNTI and delete any stored H-RNTI value;

6> clear variable E_RNTI and delete any stored E-RNTI value;

6> clear any stored IE "HARQ Info";

6> set the variable INVALID_CONFIGURATION to TRUE.

3> ignore the IE "UTRAN DRX cycle length coefficient" and stop using DRX.

…

1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per subclause 8.6.3.3, with the contents set as specified below:

2> set the IE "RRC transaction identifier" to:

3> the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; and

3> clear that entry.

2> if the USIM or SIM is present:

3> set the START value stored in the USIM [50] if present, and as stored in the UE if the SIM is present for any CN domain to the value "THRESHOLD" of the variable START_THRESHOLD.

…

The variable HS_DSCH_RECEPTION_CELL_FACH_STATE shall be set to TRUE only when all the following conditions are met:

1> the UE is in CELL_FACH;

1> the variable H_RNTI is set;

1> the variable C_RNTI is set;

1> System Information Block type 5 or System Information Block type 5bis includes IE "HS-DSCH common system information";

1> for 1.28 Mcps TDD, System Information Block type 5 includes IE "Common E-DCH system info".

If any of the above conditions is not met and the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, the UE shall:

1> set the variable HS_DSCH_RECEPTION_CELL_FACH_STATE to FALSE;

1> if the UE is in CELL_FACH and variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to FALSE:

2> set the variable HS_DSCH_RECEPTION_OF_ETWS_ENABLED to FALSE;

2> set the variable HS_DSCH_RECEPTION_GENERAL to FALSE;

2> stop any HS-SCCH reception procedures;

2> stop any HS-DSCH reception procedures;

2> clear the variable H_RNTI and remove any stored H-RNTI;

2> reset the MAC-ehs entity [15];

2> release all HARQ resources;

2> clear any stored IEs "HARQ info";

Whenever the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, the UE shall:

1> set the variable HS_DSCH_RECEPTION_GENERAL to TRUE;

1> use the IE "HS-DSCH common system information" in System Information Block type 5 or System Information Block type 5bis;

1> for FDD, receive the HS-SCCH(s) according to the IE "HS-SCCH channelization code" on the serving cell applying the scrambling code as received in the IE "DL Scrambling code" as received in IE "HS-DSCH common system information";

1> for 1.28 Mcps TDD, receive the HS-SCCH(s) according to the stored HS-SCCH configuration, applying the HS-PDSCH midamble code according to the stored HS-PDSCH midamble configuration;

1> perform HS-DSCH reception procedures:

2> if the UE has a stored IE "HARQ info":

3> act on subclause 8.6.5.6b for the stored IE "HARQ info".

2> else:

3> act on subclause 8.6.5.20 for the IE "HARQ System info" as received in IE "HS-DSCH common system information".

2> and use the value of the variable H_RNTI as UE identity in the HS-SCCH reception procedure in the physical layer.

1> and for FDD, for BCCH reception perform HS-DSCH reception procedures by listening to the first indexed HS-SCCH code listed in the IE "HS-SCCH channelization code" with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

1> and for 1.28 Mcps TDD, for BCCH reception perform HS-DSCH reception procedures by listening to the first indexed HS-SCCH according to the stored HS-SCCH configuration with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

NOTE : For 1.28 Mcps TDD, when performing HS-DSCH reception in CELL_FACH state, the UE shall use the table of transport block size for the HS-DSCH physical layer category 9 as specified in [15].

Whenever the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to FALSE, the UE shall:

1> if the UE is in CELL_FACH and variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to FALSE:

2> not perform HS-SCCH reception procedures;

2> not perform HS-DSCH reception procedures.

…

When UE does not support HS-DSCH reception in CELL_FACH state or when the IE "HS-DSCH common system information" is not included in System Information Block type 5 or System Information Block type 5bis, the UE shall:

1> set the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE;

1> set the variable HS_DSCH_RECEPTION_OF_ETWS_ENABLED to FALSE;

1> set the variable HS_DSCH_RECEPTION_GENERAL to FALSE.

When the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED or the variable HS_DSCH_RECEPTION_OF_ETWS_ENABLED is set to TRUE, the UE shall:

1> set the variable HS_DSCH_RECEPTION_GENERAL to TRUE;

1> use the IE "HS-DSCH common system information" in System Information Block type 5 or System Information Block type 5bis;

1> configure the HARQ according to IE "HARQ System info" as defined in subclause 8.6.5.20;

1> configure the common MAC-ehs reordering queues according to IE "Common MAC-ehs reordering queues" as defined in subclauses 8.6.5.22; and then

1> receive the CCCH according to IE "CCCH mapping info" as defined in subclause 8.6.5.21;

1> if the UE is RRC Connected mode:

2> select a common H-RNTI as specified in 8.5.38;

2> if the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE:

3> receive the SRB1 according to IE "SRB1 mapping info" as defined in subclause 8.6.5.19.

1> else:

2> select a common H-RNTI as specified in [4].

1> and for FDD, start to receive the HS-SCCH(s) with selected H-RNTI according to the IE "HS-SCCH channelization code" on the selected cell applying the scrambling code as received in the IE "DL Scrambling code";

1> and for 1.28 Mcps TDD, start to receive the HS-SCCH(s) with selected H-RNTI according to the IE "HS-SCCH system info" on primary frequency in the selected cell applying the midamble code as received in the IE "HS-PDSCH Midamble Configuration";

1> configure the MAC flow for BCCH reception as specified in [15];

1> and for FDD, start to receive the first indexed HS-SCCH code listed in the IE "HS-SCCH channelization code" with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

1> and for 1.28 Mcps TDD, for BCCH reception perform HS-DSCH reception procedures by listening to the first indexed HS-SCCH according to the IE "HS-SCCH system info" with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

NOTE : For 1.28 Mcps TDD, when performing HS-DSCH reception in CELL_FACH state, the UE shall use the table of transport block size for the HS-DSCH physical layer category 9 as specified in [15].

Reference

3GPP TS 25.331 clauses 8.1.3.3, 8.1.3.6, 8.5.36, 8.5.37

8.1.2.25.3 Test purpose

To confirm that the UE establishes a signalling radio bearer mapped to HS-DSCH and E-DCH according to the received RRC CONNECTION SETUP message.

8.1.2.25.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: Registered Idle Mode on PS (state 3), or CS/PS (state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

Related ICS/IXIT statement(s)

– UE supports 1.28Mcps TDD

– UE supports HS-PDSCH in CELL_FACH

– UE supports E-DCH in CELL_FACH

Test Procedure

The SS transmits System Information Type 5 including configuration for E-DCH and HS-DSCH reception in CELL_FACH state.

The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH, after the test operator makes an out-going call.

The SS transmits a RRC CONNECTION SETUP message to the UE on RB0 mapped to HS-DSCH. This message requests the establishment of a signalling radio bearer with SRB mapping to HS-DSCH and E-DCH. After the UE receives this message, it establishes a signalling radio bearer and maps it to the HS-DSCH and E-DCH. Finally the UE transmits a RRC CONNECTION SETUP COMPLETE message using AM RLC on the E-DCH channel.

SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
0			SYSTEM INFORMATION TYPE 5	Includes configuration for E-DCH and HS-DSCH reception in CELL_FACH state
1			RRC CONNECTION REQUEST	The SS prompts the operator makes an out-going call. The UE shall transmit this message, indicating the correct establishment cause and support of E-DCH and HS-PDSCH in CELL_FACH
2			RRC CONNECTION SETUP	Transmitted on HS-DSCH, requests establishment of SRBs mapped to HS-DSCH/E-DCH,
3			RRC CONNECTION SETUP COMPLETE
4			CALL C.2	If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails.

Specific Message Contents

SYSTEM INFORMATION TYPE 5

Use default message in 34.108 section 6.1.0b, condition B1.RRC CONNECTION REQUEST (Step 1)

Use the same message type found in clause 9 of TS 34.108, with the following exceptions.

Information Element	Value/remark
Initial UE identity	Same as the registered TMSI or P-TMSI
Establishment Cause	Originating Interactive Call or Originating Background Call or Originating Streaming Call or OriginatingSubscribedTrafficCall
HS-PDSCH in CELL_FACH	Check to see if set to TRUE
MAC-ehs support	Check to see if set to TRUE
Support of common E-DCH	Check to see if set to TRUE
Support of MAC-i/is	Check to see if set to TRUE

RRC CONNECTION SETUP (Step 2)

Use default message in 34.108 section 9.1.1, condition A4.RRC CONNECTION SETUP COMPLETE (Step 3)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element	Value/remark
UE Radio Access Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE radio access capability extension	Checked to see if compatible with the stated capability in PIXIT/PICS statements.
UE system specific Capability	Checked to see if compatible with the stated capability in PIXIT/PICS statements.

8.1.2.25.5 Test requirements

After step 3 the UE shall establish the RRC connection, and transmit RRC CONNECTION SETUP COMPLETE message on the DCCH using common E-DCH physical resource specified in system information block messages.

8.1.2.26 RRC Connection Establishment / Paging Permission with Access Control: Success

8.1.2.26.1 Definition

This test case is applicable for Rel-8 or later UEs.

8.1.2.26.2 Conformance requirement

Access Class related cell access restrictions shall be checked by the UE before sending an RRC connection request message when entering Connected Mode from UTRAN Idle mode. Access Class related cell access restrictions, if it is sent as a part of Domain Specific Access Restriction parameters, shall also be checked by the UE before sending INITIAL DIRECT TRANSFER message. Access Class related cell access restrictions, if it is sent as a part of Paging Permission with Access Control Parameters, shall be checked by the UE before sending a response to Paging message or before initiating a Location/Registration procedure. Otherwise, cell access restrictions associated with the Access Classes shall not apply for a UE which already is in Connected Mode.

…

With respect to Domain Specific Access Control and Paging Permission with Access Control, the UE shall:

1> if the IE "Multiple PLMN List" is not included in the Master Information Block:

2> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", and the paging permission with access control as indicated by the IE "Paging Permission with Access Control Parameters for PLMN Of MIB".

…

The UE shall apply the following handling with respect to any Access Class Barring information:

1> if in idle mode:

2> if the IE "Paging Permission with Access Control Parameters For PLMN Of MIB", the IE "Paging Permission with Access Control Parameters For OperatorN" or the IE "Paging Permission with Access Control Parameters For All" to be applied according to the requirements above is included in System Information Block Type 3, the UE shall:

3> if Paging Response Restriction Indication is set to "None":

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79], act as if no Access Class is barred in the IE "Access Class Barred List" as specified in [4].

3> if Paging Response Restriction Indication is set to "PS":

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79] from CS domain, act as if no Access Class is barred in the IE "Access Class Barred List" as specified in [4];

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79] from PS domain, act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" (or IE "Access Class Barred list" if IE "Domain Specific Access Class Barred List" is not present) as specified in [4].

3> if Paging Response Restriction Indication is set to "CS":

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79] from PS domain, act as if no Access Class is barred in the IE "Access Class Barred List" as specified in [4];

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79] from CS domain, act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" (or IE "Access Class Barred list" if IE "Domain Specific Access Class Barred List" is not present) as specified in [4].

3> else (if Paging Response Restriction Indication is set to "All"):

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79] from PS or CS domain, act on the IE "Access Class Barred list" if the IE "Domain Specific Access Class Barred List" is not present.

Reference

3GPP TS 25.304 clause 5.3.1.2, TS 25.331 clause 8.1.1.6.3

8.1.2.26.3 Test purpose

To confirm that the UE responds to a paging request even when under access class barring.

8.1.2.26.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 7) as specified in clause 7.4 of TS 34.108

Test Procedure

The UE is in idle mode. The SS transmits a PAGING TYPE 1 message to inform the UE to change the system information and it needs to read new blocks of SYSTEM INFORMATION, in which the IE “Paging Permission with Access Control Parameters” to be applied are included in SYSTEM INFORMATION BLOCK TYPE 3. The SS transmits a PAGING TYPE 1 message, which includes a matched CN UE identity for the UE in the idle state. During transmission of PAGING TYPE 1 messages, SS selects the correct paging indicator on the PICH in order to allow the UE to respond to paging. Then the UE transmits an RRC CONNECTION REQUEST to the SS on the uplink CCCH by a terminating call operation on the other non-barred domain. Then the SS transmits a RRC CONNECTION SETUP message to establish a RRC Connection with the UE and the UE replies to send an RRC CONNECTION SETUP COMPLETE message and an INITIAL DIRECT TRANSFER message. The SS releases the RRC connection: The SS pages the UE for the barred domain, and the UE does not respond to the paging by sending a RRC CONNECTION REQUEST.

This test case shall be run twice:

Case 1) The system information block type 3 indicates that the UE is only allowed to respond to paging from PS domain at step 2.

Case 2) The system information block type 3 indicates that the UE is only allowed to respond to paging from CS domain at step 2.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1	←		PAGING TYPE1	The SS transmits the message including the IE “BCCH Modification Information”.
2	← ←		MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE3	The SS starts to transmit the MIB with the “MIB value tag” IE different from the original setting. The SS transmits the new SIB3 to indicate that one of the supported domains in the cell is barred.
3				The SS waits 5 sec (to ensure that the UE has time to read the new system information).
4	←		PAGING TYPE 1	The SS transmits the message, which includes a matched identity.
5	→		RRC CONNECTION REQUEST
6	←		RRC CONNECTION SETUP	The SS assigns DPCH resources to allow UE to establish an RRC connection.
7	→		RRC CONNECTION SETUP COMPLETE
8	→		INITIAL DIRECT TRANSFER
9			RRC CONNECTION RELEASE	The SS releases the RRC CONNECTION.
10	→		RRC CONNECTION RELEASE COMPLETE	SS waits for the arrival of N308 + 1 such message with an interval time of T308, using unacknowledged mode.
11			PAGING TYPE 1	SS pages the UE for the barred domain
12				No RRC CONNECTION REQUEST sent to the SS as the domain is barred. The SS waits 30 seconds.

Specific Message Content

PAGING TYPE 1 (Step 1)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 2)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 1
SIB 3 Cell Value tag	Set to (Current SIB3 value tag + 1)

System Information Block type 3 (Step 2)

For Case 1 i.e. when the UE is only allowed to respond to paging from PS domain.

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

Information Element	Value/remark
Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
Domain Specific Access Restriction Parameters For PLMN Of MIB
-CS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
-PS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
Paging Permission with Access Control Parameters For PLMN Of MIB
– Paging Response Restriction Indication	CS
– Location/Registration Restriction Indicator	All
– Location/Registration
– Location/Registration Access Restriction	no restriction

System Information Block type 3 (Step 2)

For Case 2 i.e. when the UE is only allowed to respond to paging from CS domain.

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

Information Element	Value/remark
Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
Domain Specific Access Restriction Parameters For PLMN Of MIB
-CS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
-PS Domain Specific Access Restriction	restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
– Access Class Barred0	barred
– Access Class Barred1	barred
– Access Class Barred2	barred
– Access Class Barred3	barred
– Access Class Barred4	barred
– Access Class Barred5	barred
– Access Class Barred6	barred
– Access Class Barred7	barred
– Access Class Barred8	barred
– Access Class Barred9	barred
– Access Class Barred10	barred
– Access Class Barred11	barred
– Access Class Barred12	barred
– Access Class Barred13	barred
– Access Class Barred14	barred
– Access Class Barred15	barred
Paging Permission with Access Control Parameters For PLMN Of MIB
– Paging Response Restriction Indication	PS
– Location/Registration Restriction Indicator	All
– Location/Registration
– Location/Registration Access Restriction	no restriction

PAGING TYPE 1 (Step 4)

For Case 1 i.e. when the UE is only allowed to respond to paging from PS domain.

Use the same message type found in clause 9.1 Contents of PAGING TYPE 1 message: TM (Packet in PS) of TS 34.108:

PAGING TYPE 1 (Step 4)

For Case 2 i.e. when the UE is only allowed to respond to paging from CS domain.

Use the same message type found in clause 9.1 Contents of PAGING TYPE 1 message: TM (Speech in CS) of TS 34.108:

PAGING TYPE 1 (Step 10)

For Case 1 i.e. when the UE should NOT respond to paging from CS domain.

Use the same message type found in clause 9.1 Contents of PAGING TYPE 1 message: TM (Speech in CS) of TS 34.108

PAGING TYPE 1 (Step 10)

For Case 2 i.e. when the UE should NOT respond to paging from PS domain.

Use the same message type found in clause 9.1 Contents of PAGING TYPE 1 message: TM (Packet in PS) of TS 34.108:

INITIAL DIRECT TRANSFER (Step 8)

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

Information Element	Value/remark
CN domain identity	Check to see if it is not the barred domain.

8.1.2.26.5 Test requirement

At step 5, the UE transmits an RRC CONNECTION REQUEST message to the SS for establishing the non-barred domain service on uplink CCCH.

At step 7, the UE transmits an RRC CONNECTION SETUP COMPLETE message to the SS on uplink DCCH.

At step 12, the UE does not transmit an RRC CONNECTION REQUEST message to the SS.

8.1.2.1 RRC Connection Establishment in CELL_DCH state: Success

8.1.2.1a RRC Connection Establishment in CELL_DCH state: Success (TDD Only)

8.1.2.2 RRC Connection Establishment: Success after T300 timeout

8.1.2.3 RRC Connection Establishment: Failure (V300 is greater than N300)

8.1.2.4 RRC Connection Establishment: Reject ("wait time" is not equal to 0)

8.1.2.5 RRC Connection Establishment: Reject ("wait time" is not equal to 0 and V300 is greater than N300)

8.1.2.6 RRC Connection Establishment: Reject ("wait time" is set to 0)

8.1.2.7 RRC Connection Establishment in CELL_FACH state: Success

8.1.2.8 Void

8.1.2.9 RRC Connection Establishment: Success after Physical channel failure and Failure after Invalid configuration

8.1.2.10 RRC connection establishment in CELL_DCH on another frequency

8.1.2.10a RRC connection establishment in CELL_DCH on another frequency in a different frequency band

8.1.2.10b RRC connection establishment in CELL_DCH on another frequency in a different frequency band (TDD a-f band)

8.1.2.11 RRC Connection Establishment in FACH state (Frequency modification): Success

8.1.2.12 RRC Connection Establishment: Reject with interRATInfo is set to GSM

8.1.2.13 RRC Connection Establishment: Reject with InterRATInfo is set to GSM and selection to the designated system fails

8.1.2.14 RRC Connection Establishment using the default configuration for 3.4 kbps signalling bearers

8.1.2.15 RRC Connection Establishment using the default configuration for 13.6 kbps signalling bearers

8.1.2.16 RRC Connection Establishment / Domain Specific Access Control: Success

8.1.2.17 RRC Connection Establishment for transition from Idle Mode to CELL_DCH: Success (start of E-DCH transmission)

8.1.2.18 RRC Connection Establishment using the default configuration for HS-DSCH / E-DCH signalling bearers

8.1.2.19 RRC Connection Establishment for transition from Idle Mode to CELL_DCH: Success (start of discontinuous uplink transmission and downlink reception)

8.1.2.20 RRC Connection Establishment for transition from Idle Mode to CELL_FACH: Success (Start of HS-DSCH Reception)

8.1.2.21 RRC Connection Establishment: Reject with Frequency Info set to the same frequency band – Successful case

8.1.2.21a RRC Connection Establishment: Reject with Frequency Info set to a different frequency band – Successful case

8.1.2.22 RRC Connection Establishment: Reject with Frequency Info set to the same frequency band – Unsuccessful case

8.1.2.22a RRC Connection Establishment: Reject with Frequency Info set to a different frequency band – Unsuccessful case

8.1.2.23 Void

8.1.2.23a Void

8.1.2.24 Void

8.1.2.24a Void

8.1.2.25 RRC Connection Establishment for transition from Idle Mode to CELL_FACH: Success (Start of E-DCH and HS-DSCH Reception)

8.1.2.26 RRC Connection Establishment / Paging Permission with Access Control: Success

8.1.2.27 Void