8.3.2 URA Update

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

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

8.3.2.1 URA Update: Change of URA

8.3.2.1.1 Definition

–

8.3.2.1.2 Conformance requirement

A UE in URA_PCH state shall initiate the URA update procedure in the following cases:

1> URA reselection:

2> if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not present in the list of URA identities in system information block type 2; or

2> if the list of URA identities in system information block type 2 is empty; or

2> if the system information block type 2 can not be found:

…

3> perform URA update using the cause "change of URA".

When initiating the URA update procedure, the UE shall:

1> stop timer T305;

1> set the variables PROTOCOL_ERROR_INDICATOR, FAILURE_INDICATOR, UNSUPPORTED_CONFIGURATION and INVALID_CONFIGURATION to FALSE;

1> move to CELL_FACH state, if not already in that state;

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

1> in case of a URA update procedure:

2> set the contents of the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;

2> submit the URA UPDATE message for transmission on the uplink CCCH.

1> set counter V302 to 1;

1> start timer T302 when the MAC layer indicates success or failure in transmitting the message.

In case of URA update procedure the UE shall transmit a URA UPDATE message.

The UE shall set the IEs in the URA UPDATE message as follows:

1> set the IE "U-RNTI" to the value of the variable U_RNTI;

1> set the IE "URA update cause" corresponding to which cause as specified in TS 25.331 subclause 8.3.1.2 that is valid when the URA UPDATE message is submitted to lower layers for transmission;

2> if the value of the variable PROTOCOL_ERROR_INDICATOR is TRUE:

…

2> if the value of the variable PROTOCOL_ERROR_INDICATOR is FALSE:

3> if the value of the variable INVALID_CONFIGURATION is TRUE:

…

3> if the value of the variable INVALID_CONFIGURATION is FALSE:

4> set the IE "Protocol error indicator" to FALSE.

If the URA UPDATE CONFIRM message:

– does not include "CN information elements"; and

– does not include the IE "Ciphering mode info"; and

– does not include the IE "Integrity protection mode info"; and

– does not include the IE "New U-RNTI"; and

– does not include the IE "New C-RNTI":

the UE shall:

1> transmit no response message.

…

If any or several of the following conditions are true:

…

– reselection to another UTRA cell (including the previously serving cell) before completion of the cell update or URA update procedure;

the UE shall:

…

1> check whether it is still in "in service area" (see TS 25.331 subclause 8.5.5.2);

…

1> in case of a URA update procedure:

2> clear any entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS.

If the UE detects "in service area" if it has not entered idle mode, and:

1> if V302 is equal to or smaller than N302, the UE shall:

2> if the UE performed cell re-selection:

3> delete its C-RNTI.

…

2> in case of a URA update procedure:

3> set the contents of the URA UPDATE message according to TS 25.331 subclauses 8.3.1.3 and 8.5.10;

3> if a URA UPDATE CONFIRM message was received and caused the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE:

…

3> submit the URA UPDATE message for transmission on the uplink CCCH.

…

The UE shall:

1> if the IE "URA identity" is included in a received message:

2> if the IE "RRC State Indicator" is included and set to "URA_PCH":

3> store this URA identity in the variable URA_IDENTITY;

3> after sending a possible message to UTRAN and entering URA_PCH state as specified elsewhere, read system information block type 2 in the selected cell;

3> if the stored URA identity in the variable URA_IDENTITY is not included in the list of URA identities in System Information Block type 2 in the selected cell, the list of URA identities in system information block type 2 is empty or if the system information block type 2 can not be found, a confirmation error of URA identity list has occurred:

4> if no URA update procedure is ongoing:

…

4> if a URA update procedure is ongoing:

5> take actions as specified in TS 25.331 subclause 8.3.1.10.

If the URA UPDATE CONFIRM message causes a confirmation error of URA identity list as specified in TS 25.331 subclause 8.6.2.1 the UE shall:

1> check the value of V302; and

1> if V302 is smaller or equal than N302:

…

2> set the IEs in the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;

2> submit the URA UPDATE message for transmission on the uplink CCCH;

…

Reference

3GPP TS 25.331 clause 8.3.1.2, 8.3.1.12, 8.6.2.1

8.3.2.1.3 Test purpose

1. To confirm that the UE executes an URA update procedure after the successful change of URA.

2. To confirm that the UE performs an URA update procedure after it detects that SIB 2 is not broadcasted.

3. To confirm that the UE performs an URA update procedure after it detects a confirmation error of URA identity list.

8.3.2.1.4 Method of test

Initial Condition

System Simulator: 2 cells: The URA-ID and transmission power for each cell is shown in Table 8.3.2.1, where the initial condition is shown in column "T0".

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108, with URA-ID 1 from the list of URA-ID in cell 1.

Test Procedure

Parameter	Unit	Cell 1								Cell 2
		T0	T1	T2	T3	T4	T5	T6	T7	T0	T1	T2	T3	T4	T5		T6		T7
UTRA RF Channel Number		Ch. 1								Ch. 1
CPICH Ec	dBm/3.84MHz	-60	-69		-60	-69	-60		-69	-69	-60		-69	-60		-69				-60
P-CCPCH RSCP (TDD)	dBm	-60	-69		-60	-69	-60		-69	-69	-60		-69	-60		-69				-60
URA ID		URA-ID 1		URA-ID 2						URA-ID 1,3 and 4								no SIB2

The test begins with the downlink power transmission of both cells set according to ‘T0’ column in table 8.3.2.1. The UE is in the URA_PCH state and assigned with only 1 URA identity in cell 1: URA-ID 1. The SS then adjusts the transmission power again according to the ‘T1’ column. This is expected to cause the UE to perform a cell reselection to cell 2. Since URA-ID 1 is also broadcasted in cell 2, the UE shall not perform any URA update procedure due to the change of URA. Starting from time ‘T2’, SS modifies the system information in cell 1, so that URA-ID 2 is the only URA identity in that cell. Next SS adjusts the transmission power according to ‘T3’ column. UE shall perform a cell reselection to cell 1 and when the UE finds that its current URA-ID 1 is not in the new broadcasted list of URA-IDs, it moves to CELL_FACH state and transmits a URA UPDATE message on the uplink CCCH. After the SS receives this message, it transmits a URA UPDATE CONFIRM message, which includes the IEs "RRC State Indicator" and IE "URA-ID" to the UE on the downlink CCCH. The IE "RRC State Indicator" is set to "URA_PCH". UE returns to URA_PCH state in cell 1 without sending any uplink response message. Next SS adjusts the transmission power according to ‘T4’ column. UE shall re-select to cell 2 and transmit a URA UPDATE message to SS. However, SS do not acknowledge but adjusts the transmission power according to ‘T5’ column. UE shall perform cell re-selection to cell 1 and then send a URA UPDATE message to SS. SS shall transmit URA UPDATE CONFIRM message to UE on the downlink CCCH. Starting from time ‘T6’, SS modifies the system information in cell 2, so that no SIB 2 is sent in that cell. Next the SS adjusts the transmission power according to the ‘T7’ column. The UE shall re-select to cell 2 and send a URA UPDATE message since no SIB2 is broadcasted in this cell. When the UE receives a URA UPDATE CONFIRM message including a URA identity, the UE will again send a URA UPDATE message. When receiving this last message, the SS shall transmit RRC Connection Release message on downlink CCCH to release the RRC connection.

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
Step	UE	SS	Message	Comment
1				The UE is updated with only 1 URA identity carried currently by cell 1. The starting state of the UE is URA_PCH
2				SS set the power transmission and system information of all cells according to column ‘T1’ of table 8.3.2.1.
3				UE shall perform a cell reselection but shall not transmit URA UPDATE message with the update cause of "change of URA".
3a				Starting from time ‘T2’, SS modifies the system information in cell 1, so that URA-ID 2 is the only URA identity in that cell
4				SS set the power transmission and system information of all cells according to column ‘T3’ of table 8.3.2.1.
5			URA UPDATE	The UE shall perform a cell reselection first and when it finds that its current URA-ID 1 is not in the newly broadcasted list of URA-IDs, it shall then transmit this message and set value "change of URA" into IE "URA update cause".
6			URA UPDATE CONFIRM	Message comprises IE "RRC State Indicator" set to "URA_PCH", and also IE "URA Identity" equal to "URA-ID 2".
7				SS set the power transmission and system information of all cells according to column ‘T4’ of table 8.3.2.1.
8			URA UPDATE
9				SS do not respond to the URA UPDATE message from UE and set the power transmission and system information of all cells according to column ‘T5’ of table 8.3.2.1.
10			URA UPDATE
11			URA UPDATE CONFIRM
11a				Starting from time ‘T6’, SS modifies the system information in cell 2, so that no SIB 2 is sent in that cell.
12				SS set the power transmission and system information of all cells according to column ‘T7’ of table 8.3.2.1.
13			URA UPDATE	The UE shall perform a cell reselection first and when it finds that no URA-ID is broadcasted in this cell, it shall then transmit this message and set value "change of URA" into IE "URA update cause".
14			URA UPDATE CONFIRM	Message comprises IE "RRC State Indicator" set to "URA_PCH", and also IE "URA Identity" equals to "URA-ID 2".
15			URA UPDATE
16			RRC CONNECTION RELEASE	This message is sent on CCCH.
17			Void
18				UE enters idle mode

Specific Message Contents

SYSTEM INFORMATION BLOCK TYPE 2

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

Cell 1, time T0-T1:

Information Element	Value/remark
– URA identity list
– URA identity	0000 0000 0000 0001B

Cell 2, time T0-T5:

Information Element	Value/remark
– URA identity list
– URA identity	0000 0000 0000 0011B
– URA identity	0000 0000 0000 0001B
– URA identity	0000 0000 0000 0100B

Cell 1, time T2-T7 (step 3a):

Information Element	Value/remark
– URA identity list
– URA identity	0000 0000 0000 0010B

Cell 2, time T6-T7 (step 11a):

No SYSTEM INFORMATION BLOCK TYPE 2 is broadcasted in cell 2 during this time period.

URA UPDATE (Step 5, 8, 10, 13, and 15)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
URA Update Cause	Check to see if set to ‘change of URA’

URA UPDATE CONFIRM (Step 6, 11 and 14)

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

Information Element	Value/remark
URA identity	URA-ID 2

8.3.2.1.5 Test requirement

After step 2 the UE shall not transmit a URA UPDATE message with update cause "change of URA".

After step 4 the UE shall find that URA-ID 2 is not in its maintained list of URA-IDs. After cell reselection, the UE shall move to CELL_FACH state and transmit a URA UPDATE message setting value "change of URA" into IE "URA update cause".

After step 7 the UE shall find that URA-ID 1 is not in its maintained list of URA-IDs. After cell reselection, the UE shall move to CELL_FACH state and a transmit URA UPDATE message setting value "change of URA" into IE "URA update cause".

After step 9 the UE shall find the new cell and transmit a URA UPDATE message setting value "change of URA" into IE "URA update cause".

After step 12 the UE shall find that no URA-ID is broadcasted in the cell, move to CELL_FACH state and transmit a URA UPDATE message setting the update cause to "change of URA".

After step 14 the UE shall find that no URA-ID is broadcasted in the cell and transmit a URA UPDATE message setting the update cause to "change of URA".

8.3.2.1a URA Update: Change of URA (Cells belong to different frequency bands)

8.3.2.1a.1 Definition

This test case is identical to test case 8.3.2.1 except that the cells belong to different frequency bands.

NOTE: The test case 8.3.2.1 is an intra frequency test.

8.3.2.1a.2 Conformance requirement

Same conformance requirement as in clause 8.3.2.1.2

8.3.2.1a.3 Test purpose

Same test purpose as in clause 8.3.2.1.3 except that the cells belong to different frequency bands

8.3.2.1a.4 Method of test

Initial Condition

Same initial conditions as in clause 8.3.2.1.4 except, Cell 2 is mapped to cell 4 (inter frequency) of 34.108 clause 6.1 and both cells belong to different frequency bands.

System Information Block type 3

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

Information Element	Value/Remarks
-Qualmin	-16dB

Related ICS/IXIT statement(s)

– UE supports multiple bands simultaneously yes/no

Test Procedure

Same test procedure as in clause 8.3.2.1.4 with the following exception

After step 8, SS shall send URA UPDATE CONFIRM message to the UE.

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

Expected sequence

Same expected sequence as in clause 8.3.2.1.4 with the following additional / modified test steps

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
8a			URA UPDATE CONFIRM
9				SS sets the power transmission and system information of all cells according to column ‘T5’ of table 8.3.2.1.

Specific Message Contents

Same specific message contents as in clause 8.3.2.1.4 with the following exceptions for the additional test steps:

URA UPDATE CONFIRM (Step 8a)

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

Information Element	Value/remark
URA identity	URA-ID 1

8.3.2.1a.5 Test requirement

Same test requirement as in clause 8.3.2.1.5.

8.3.2.1b URA Update: Change of URA (Cells belong to different frequency bands for LCR TDD)

8.3.2.1b.1 Definition

This test case is identical to test case 8.3.2.1 except that the cells belong to different frequency bands.

NOTE: The test case 8.3.2.1 is an intra frequency test.

8.3.2.1b.2 Conformance requirement

Same conformance requirement as in clause 8.3.2.1.2

8.3.2.1b.3 Test purpose

Same test purpose as in clause 8.3.2.1.3 except that the cells belong to different frequency bands

8.3.2.1b.4 Method of test

Initial Condition

Same initial conditions as in clause 8.3.2.1.4 except, Cell 2 is mapped to cell 4 (inter frequency) of 34.108 clause 6.1 and both cells belong to different frequency bands.

System Information Block type 3

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

Information Element	Value/Remarks
-Qrxlevmin	-115dBm

Related ICS/IXIT statement(s)

– UE supports multiple bands simultaneously yes/no

Test Procedure

Same test procedure as in clause 8.3.2.1.4 with the following exception

After step 8, SS shall send URA UPDATE CONFIRM message to the UE.

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

Expected sequence

Same expected sequence as in clause 8.3.2.1.4 with the following additional / modified test steps

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
8a			URA UPDATE CONFIRM
9				SS sets the power transmission and system information of all cells according to column ‘T5’ of table 8.3.2.1.

Specific Message Contents

Same specific message contents as in clause 8.3.2.1.4

URA UPDATE CONFIRM (Step 8a)

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

Information Element	Value/remark
URA identity	URA-ID 1

8.3.2.1b.5 Test requirement

Same as in clause 8.3.2.1.5.

8.3.2.2 URA Update: Periodical URA update and Reception of Invalid message

8.3.2.2.1 Definition

8.3.2.2.2 Conformance requirement

A UE in URA_PCH state shall initiate the URA update procedure in the following cases:

1> URA reselection:

…

1> Periodic URA update:

2> if the criteria for performing URA update with the causes as specified above in the current subclause are not met; and

2> if the timer T305 expires while the UE is in the service area; and

2> if periodic updating has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity":

3> perform URA update using the cause "periodic URA update".

…

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

1> If V302 is equal to or smaller than N302, the UE shall:

2> set the variable PROTOCOL_ERROR_INDICATOR to TRUE;

…

2> in case of a URA update procedure:

3> set the contents of the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;

3> submit the URA UPDATE message for transmission on the uplink CCCH.

2> increment counter V302;

2> restart timer T302 when the MAC layer indicates success or failure to transmit the message.

1> if V302 is greater than N302, the UE shall:

…

2> release all its radio resources;

2> enter idle mode;

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

2> the procedure ends.

Reference

3GPP TS 25.331 clause 8.3.1.2, 8.3.1.7, 8.3.1.11

8.3.2.2.3 Test purpose

1. To confirm that the UE executes a URA update procedure after the expiry of timer T305.

2. To verify that the UE handles an invalid URA UPDATE CONFIRM message correctly when executing the URA update procedure.

8.3.2.2.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108.

Test Procedure

The UE is in URA_PCH state. When the UE detects the expiry of timer T305, set according to the value specified in system information, the UE moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH. The message shall indicate the cause to be "periodic URA update" in IE "URA update cause". SS replies with an invalid URA UPDATE CONFIRM message sent on downlink DCCH, and check to see if the UE handles this event properly. The UE shall attempt to retransmit the identical URA UPDATE message. After the SS receives the second URA UPDATE message, it transmits a correct URA UPDATE CONFIRM message to the UE on the downlink CCCH. The UE then returns to URA_PCH state. SS calls for generic procedure C.5 to check that UE is in URA_PCH state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is in URA_PCH state. SS wait until T305 timer has expired.
2			URA UPDATE	UE shall transmit this message and set value "periodic URA update" into IE "URA update cause".
3			URA UPDATE CONFIRM	See specific message content.
4			URA UPDATE	UE shall not return to idle mode immediately, but attempts to re-transmit this message.
5			URA UPDATE CONFIRM

6			Void

7			CALL C.5	If the test result of C.5 indicates that UE is in URA_PCH state, the test passes, otherwise it fails.

Specific Message Contents

URA UPDATE (Step 2)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
URA Update Cause	Check to see if set to ‘Periodic URA update’

URA UPDATE CONFIRM (Step 3)

Use the URA UPDATE CONFIRM message as defined in [9] TS 34.108 clause 9, with the following exceptions:

Information Element	Value/remark
Critical extensions	’FF’H

URA UPDATE (Step 4)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
RRC Transaction identifier	Check to see if set to the value given in URA UPDATE CONFIRM message in step 3.
URA Update Cause	Check to see if set to ‘Periodic URA update’
Protocol error indicator	TRUE
Protocol error information
– Protocol error cause	Message extension not comprehended

URA UPDATE CONFIRM (Step 5)

Use the URA UPDATE CONFIRM message as defined in [9] TS 34.108 clause 9.

8.3.2.2.5 Test requirement

After step 1 the UE shall detect the expiry of timer T305, move to CELL_FACH state, and transmit a URA UPDATE message which sets the value "periodical cell update" into IE "URA update cause".

After step 3 the UE shall re-transmit URA UPDATE message with IE "Protocol error indicator" set to ‘TRUE’ and IE "Protocol error information" set to "Message extension not comprehended".

After step 5 the UE shall return to the URA_PCH state.

8.3.2.3 Void

8.3.2.4 URA Update: loss of service after expiry of timers T307 and T305

8.3.2.4.1 Definition

8.3.2.4.2 Conformance requirement

When the T305 expires and the UE detects that it is "out of service area" as specified in TS 25.331 subclause 8.5.5.1, the UE shall

1> start timer T307;

…

When the T307 expires, the UE shall:

1> move to idle mode;

1> release all dedicated resources;

1> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers;

1> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

1> clear the variable ESTABLISHED_RABS;

1> perform other actions when entering idle mode from connected mode as specified in TS 25.331 subclause 8.5.2;

1> and the procedure ends.

Reference

3GPP TS 25.331 clause 8.3.1.4.

8.3.2.4.3 Test purpose

1. To confirm that the UE moves to idle mode after the expiry of timer T307, following an expiry of timer T305 when it discovers that it is out of service area.

8.3.2.4.4 Method of test

Initial Condition

System Simulator: 1 cell

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

Test Procedure

Table 8.3.2.4

Parameter	Unit	Cell 1
Parameter	Unit	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency
CPICH Ec	dBm/3.84MHz	-60	-80
P-CCPCH RSCP (TDD)	dBm	-60	-80

Table 8.3.2.4 illustrates the downlink power to be applied at various time instants of the test execution. Columns marked "T0" denote the initial conditions.

The UE is in CELL_DCH state. The SS transmits UTRAN MOBILITY INFORMATION message to the UE to change the value of T305. The UE shall respond with UTRAN MOBILITY INFORMATION CONFIRM message. The UE transits to URA_PCH state using the generic procedure P18 in TS 34.108 clause 7.4. The content of the SYSTEM INFORMATION BLOCK TYPE 3 and 4 is modified. The SS waits for reception of a periodical URA update in order to know the timing of the T305 in the UE. The SS replies to the received URA UPDATE message with an URA UPDATE CONFIRM message on the downlink CCCH. SS configures its downlink transmission power settings according to columns "T1" in table 8.3.2.4 so that S<0. When the UE detects the expiry of periodic URA updating timer T305 according to the system information, the UE detects that it is out of service area. After the expiry of timer T307, the UE moves to the idle state. SS configures its downlink transmission power settings according to columns "T0" in table 8.3.2.4 so that S>0. SS waits for 60s and then calls for generic procedure C.1 to check that UE is in idle mode state.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
0				Initially, the UE is in CELL_DCH state.
0a			UTRAN MOBILITY INFORMATION	Include new timers value (see specific message contents).
0b			UTRAN MOBILITY INFORMATION CONFIRM
0c			SS executes procedure P18 (clause 7.4.2.7.2) specified in TS 34.108.	Transit the UE to URA_PCH state. URA-ID 1 shall be in the list of URA-ID.
1			Void
1a			MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 3 and 4	SS changes the contents of MASTER INFORMATION BLOCK and SYSTEM INFORMATION BLOCK (see specific message contents).
1b			PAGING TYPE 1	Include IE "BCCH modification info"
1c			URA UPDATE	IE "URA update cause" shall be set to "periodical URA update".
1d			URA UPDATE CONFIRM
2a				SS configures its downlink transmission power settings according to columns "T1" in table 8.3.2.4 so that the UE detects that it is out of service area.
2b				SS waits (T305+T307) +10% for UE to enter idle mode.
3				Upon the expiry of timer T305, the UE shall search for cell to camp and triggers T307 timer. SS listens to the uplink CCCH to verify that URA UPDATE message is not transmitted.
4				After the expiry of timer T307, the UE enters idle state. SS configures its downlink transmission power settings according to columns "T0" in table 8.3.2.4 so that the cell is suitable for camping. SS waits for 60s.
5			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

MASTER INFORMATION BLOCK (Step 1a)

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

Information Element	Value/remark
MIB Value Tag	A valid MIB value tag as defined in TS 25.331 that is different from the previous value.
Scheduling information	– Scheduling info for System Information Type 1
– PLMN Value tag	A valid PLMN value tag as defined in TS 25.331 that is different from the previous value.
Scheduling information	– Scheduling info for System Information Type 3
– Cell Value tag	A valid Cell value tag as defined in TS 25.331 that is different from the previous value.
Scheduling information	– Scheduling info for System Information Type 4
– Cell Value tag	A valid Cell value tag as defined in TS 25.331 that is different from the previous value.

SYSTEM INFORMATION BLOCK TYPE 3 and 4 (Step 1a)

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

Information Element	Value/remark
Qrxlevmin	-70

PAGING TYPE 1 (Step 1b)

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

Information Element	Value/remark
Paging record list	Not Present
BCCH modification info
MIB Value tag	A valid Cell value tag as defined in TS 25.331 that is different from the previous value.
BCCH modification time	Not present

UTRAN MOBILITY INFORMATION (Step 0a)

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

Information Element	Value/remark
– T305	5 minutes

UTRAN MOBILITY INFORMATION CONFIRM (Step 0b)

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

URA UPDATE (Step 1c)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
URA Update Cause	Check to see if set to "periodical URA update"

8.3.2.4.5 Test requirement

After step 0a the UE shall respond with UTRAN MOBILITY INFORMATION CONFIRM message.

After step 2 the UE shall not transmit any URA UPDATE message on the uplink CCCH.

8.3.2.5 URA Update: Success after Confirmation error of URA-ID list

8.3.2.5.1 Definition

8.3.2.5.2 Conformance requirement

The UE shall:

1> if the IE "URA identity" is included in a received message:

2> if the IE "RRC State Indicator" is included and set to "URA_PCH":

3> store this URA identity in the variable URA_IDENTITY;

3> after sending a possible message to UTRAN and entering URA_PCH state as specified elsewhere, read system information block type 2 in the selected cell;

4> if no URA update procedure is ongoing:

…

4> if a URA update procedure is ongoing:

5> take actions as specified in TS 25.331 subclause 8.3.1.10.

If the URA UPDATE CONFIRM message causes a confirmation error of URA identity list as specified in TS 25.331 subclause 8.6.2.1 the UE shall:

1> check the value of V302; and

1> if V302 is smaller or equal than N302:

2> set the IEs in the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;

2> submit the URA UPDATE message for transmission on the uplink CCCH;

2> increment counter V302;

2> restart timer T302 when the MAC layer indicates success or failure to transmit the message.

1> if V302 is greater than N302:

…

Reference

3GPP TS 25.331 clause 8.3.1.10, 8.6.2.1.

8.3.2.5.3 Test purpose

1. To confirm that the UE retries to perform the URA update procedure following a confirmation error of URA-ID list.

8.3.2.5.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108.

Test Procedure

At the start of this test, the UE is brought to URA_PCH state and assigned a URA with URA-ID 1. When the UE detects the expiry of timer T305 according to the system information, the UE moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH. The reason for performing URA updating shall be set to "periodic URA update" in IE "URA update cause". After the SS receives this message, it transmits a URA UPDATE CONFIRM message which includes the IE "RRC state indicator" set to "URA_PCH" and IE "URA identity" set to "URA-ID 2" to the UE on the downlink DCCH. The UE finds that the indicated URA-ID is not included in the list of URA-IDs broadcasted in system information block type 2, and then the UE shall retry to transmit a URA UPDATE message, with "change of URA" set in IE "URA update cause", for a confirmation error of URA-ID list. SS continue to send the same URA UPDATE CONFIRM message on the downlink DCCH until N302+1 URA UPDATE messages have been received. Then SS transmits a URA UPDATE CONFIRM message to the UE which includes IE "URA Identity" set to "URA-ID 1" and IE "new U-RNTI" on the downlink DCCH. The UE shall find this URA-ID in its URA-ID list and transmits an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is URA_PCH state. SS initializes counter K to 0
2			URA UPDATE	This message shall contain value "periodic URA update" set in IE "URA update cause" after expiry of timer T305.
3			Void
4			URA UPDATE CONFIRM	SS transmits this message, setting the value "URA-ID 2" to IE "URA Identity", and including “New U_RNTI”.
4a			UTRAN MOBILITY INFORMATION CONFIRM
5			URA UPDATE	This message shall contain value "change of URA" set in IE "URA update cause"
6				SS increments K by 1. If K is not greater than N302, proceed to step 7. If K is greater than N302, SS proceeds to step 8.
7			URA UPDATE CONFIRM	SS transmits this message, setting the value "URA-ID 2" to IE "URA Identity", and including “New U_RNTI”. And then returns to step 4a.
8			URA UPDATE CONFIRM	SS transmits this message, setting IE "URA Identity" to "URA-ID 1". This message also comprises IE "New U-RNTI".
9			UTRAN MOBILITY INFORMATION CONFIRM

Specific Message Contents

URA UPDATE (Step 2)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
URA Update Cause	Check to see if set to ‘Periodic URA update’

URA UPDATE CONFIRM (Step 4 &7)

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

Information Element	Value/remark
New U-RNTI
-SRNC Identity	‘0000 0000 0001’
-S-RNTI	‘0000 0000 0000 0000 0101’
New C-RNTI	‘1010 1010 1010 1010’ B
URA Identity	2

URA UPDATE (Step 5)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0101’
URA Update Cause	Check to see if set to ‘change of URA’

URA UPDATE CONFIRM (Step 8)

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

Information Element	Value/remark
New U-RNTI
-SRNC Identity	‘0000 0000 0001’
-S-RNTI	‘0000 0000 0000 0101 0101’
New C-RNTI	‘1010 1010 1010 0000’ B
URA Identity	1

UTRAN MOBILITY INFORMATION CONFIRM (Step 4a & 9)

Only the message type IE in this message is checked.

8.3.2.5.5 Test requirement

After step 1 the UE shall detect the expiry of timer T305, move to CELL_FACH state, transmit a URA UPDATE message on the uplink CCCH and set value "periodic URA update" into IE "URA update cause".

After step 4 the UE shall re-transmit a URA UPDATE message with IE "URA update cause" set to "change of URA" after it detects a confirmation error of URA-ID list for the URA-ID indicated in the URA UPDATE CONFIRM message. A total of (N302+1) URA UPDATE messages shall be received by the SS.

After step 8 the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH.

8.3.2.6 URA Update: Failure (V302 is greater than N302: Confirmation error of URA-ID list)

8.3.2.6.1 Definition

8.3.2.6.2 Conformance requirement

The UE shall:

1> if the IE "URA identity" is included in a received message:

2> if the IE "RRC State Indicator" is included and set to "URA_PCH":

3> store this URA identity in the variable URA_IDENTITY;

3> after sending a possible message to UTRAN and entering URA_PCH state as specified elsewhere, read system information block type 2 in the selected cell;

4> if no URA update procedure is ongoing:

…

4> if a URA update procedure is ongoing:

5> take actions as specified in TS 25.331 subclause 8.3.1.10.

If the URA UPDATE CONFIRM message causes a confirmation error of URA identity list as specified in TS 25.331 subclause 8.6.2.1 the UE shall:

1> check the value of V302; and

1> if V302 is smaller or equal than N302:

2> set the IEs in the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;

2> submit the URA UPDATE message for transmission on the uplink CCCH;

2> increment counter V302;

2> restart timer T302 when the MAC layer indicates success or failure to transmit the message.

1> if V302 is greater than N302:

2> release all its radio resources;

2> enter idle mode;

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

2> the procedure ends.

Reference

3GPP TS 25.331 clause 8.3.1.10, 8.6.2.1

8.3.2.6.3 Test purpose

1. To confirm that the UE make repeated attempts to perform the URA update procedure following a detection of a confirmation error of URA-ID list. It then moves to idle state when internal counter V302 is greater than N302.

8.3.2.6.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108.

Test Procedure

The UE is originally in URA_PCH state updated with URA-ID 1. When the UE detects the expiry of timer T305 according to the system information, the UE shall move to CELL_FACH state and transmit a URA UPDATE message to the SS on the uplink CCCH. In this message, the value "periodic URA update" shall be set in IE "URA update cause". After the SS receives this message, it transmits a URA UPDATE CONFIRM message which includes the IE "RRC state indicator" set to "URA_PCH" and indicating the IE "URA Identity" to be "URA-ID 2" to the UE on the downlink CCCH. The UE finds that the indicated URA-ID is not included in the list of URA-IDs broadcasted. Then the UE shall retry to transmit a URA UPDATE message, with "change of URA" set in IE "URA update cause", for N302 times and each time the SS responds with the URA UPDATE CONFIRM message similar to the previous one on the downlink CCCH. After that, the UE shall enter idle state. SS waits for 5s and then calls for generic procedure C.1 to check that UE is in idle mode state.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is in URA_PCH state at the start of the test. SS sets internal counter K to 0.
2			URA UPDATE	The message shall indicate "periodic URA update" in IE "URA update cause". This message is sent following the expiry of timer T305. SS increments counter K by 1.
3				SS increments K by 1.
4			URA UPDATE CONFIRM	The SS transmits this message and set IE "URA Identity" to "URA-ID 2".
5			URA UPDATE	The message shall indicate "change of URA" in IE "URA update cause". This message is sent following the expiry of timer T305. SS increments counter K by 1.
6			URA UPDATE CONFIRM	The SS transmits this message and set IE "URA Identity" to "URA-ID 2". When K is greater than N302 proceeds to step 7, else executes step 5.
7			Void	The UE shall enter idle state. SS waits for 5s.
8			Void
9			Void
10			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

URA UPDATE CONFIRM (Step 3)

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

Information Element	Value/remark
URA Identity	2

8.3.2.6.5 Test requirement

After step 1 the UE shall detect the expiry of timer T305, then it shall move to CELL_FACH state and transmit a URA UPDATE message on the uplink CCCH, setting value "periodic URA update" in IE "URA update cause".

After step 6 and if K is not greater than N302, the UE shall retry to transmit a URA UPDATE message, setting value "periodic URA update" in IE "URA update cause" after it detects the confirmation error of URA-ID list for the URA-ID included in the URA UPDATE CONFIRM message.

After step 6 and if K is greater than N302, the UE shall stop transmitting URA UPDATE message and then enters idle state.

8.3.2.7 URA Update: Success after T302 timeout

8.3.2.7.1 Definition

8.3.2.7.2 Conformance requirement

If any or several of the following conditions are true:

– expiry of timer T302;

…

the UE shall:

1> stop T302 if it is running;

1> check whether it is still in "in service area";

1> in case of a URA update procedure:

2> clear any entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS.

If the UE detects "in service area" if it has not entered idle mode, and:

1> if V302 is equal to or smaller than N302, the UE shall:

2> in case of a URA update procedure:

3> set the contents of the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;

3> submit the URA UPDATE message for transmission on the uplink CCCH.

2> increment counter V302;

2> restart timer T302 when the MAC layer indicates success or failure to transmit the message.

1> if V302 is greater than N302, the UE shall:

…

Reference

3GPP TS 25.331 clause 8.3.1.12.

8.3.2.7.3 Test purpose

1. To confirm that the UE attempts to repeat the URA update procedure upon the expiry of timer T302.

8.3.2.7.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108.

Test Procedure

The UE is in URA_PCH. When the UE detects the expiry of timer T305 according to the system information, the UE moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH, setting value "periodic URA update" into IE "URA update cause". The SS ignores this message. The UE shall then retry to transmit a URA UPDATE message after the expiry of timer T302, until a total of N302+1 URA UPDATE messages have been received by the SS. SS transmits a URA UPDATE CONFIRM message to the UE on the downlink CCCH to end the procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is in URA_PCH state at the beginning of test. SS initializes counter K to 0 SS waits for T305 to expire.
2			URA UPDATE	This message shall contain value "periodic URA update" in IE "URA update cause" sent upon the expiry of timer T305.
3				SS shall not reply. Increment K by 1.
4			URA UPDATE	This message shall contain value "periodic URA update" in IE "URA update cause" sent upon the expiry of timer T302.
5				SS shall not reply. SS increments K by 1. If K is not greater than N302, proceed to step 4. If K is greater than N302, SS proceeds to step 6.
6			URA UPDATE CONFIRM
7			UTRAN MOBILITY INFORMATION CONFIRM
8			CALL C.5	If the test result of C.5 indicates that UE is in URA_PCH state, the test passes, otherwise it fails.

Specific Message Contents

URA UPDATE CONFIRM (Step 6)

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

Information Element	Value/remark
New U-RNTI
SRNC identity	0000 0000 0001 B
S-RNTI	0000 0000 0000 1111 1111 B
New C-RNTI	‘1010 1010 1010 1010’ B

8.3.2.7.5 Test requirement

After step 1 the UE shall detect the expiry of timer T305, then it shall move to CELL_FACH state and transmit a URA UPDATE message on the uplink CCCH. The updating cause shall be set to "periodic URA update" in IE "URA update cause".

After step 3 the UE shall retry to transmit a URA UPDATE message at the expiry of timer T302, until a total of N302+1 URA UPDATE messages have been received by the SS.

After step 6, the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH.

8.3.2.8 Void

8.3.2.9 URA Update: Failure (UTRAN initiate an RRC connection release procedure on CCCH)

8.3.2.9.1 Definition

8.3.2.9.2 Conformance requirement

When the UTRAN receives a CELL UPDATE/URA UPDATE message, the UTRAN should:

1> … or

1> initiate an RRC connection release procedure (see subclause 8.1.4 in TS 25.331) by transmitting an RRC CONNECTION RELEASE message on the downlink CCCH.

…

The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH. Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed states.

When the UE receives the first RRC CONNECTION RELEASE message; and

1> if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable U_RNTI; or

1> if the message is received on DCCH:

the UE shall:

…

1> in state CELL_FACH:

2> if the RRC CONNECTION RELEASE message was received on the CCCH:

3> …

3> enter idle mode;

Reference

3GPP TS 25.331 clause 8.3.1.5, 8.1.4.3

8.3.2.9.3 Test purpose

To confirm that the UE moves to idle state upon the reception of RRC CONNECTION RELEASE message on downlink CCCH during a URA update procedure.

8.3.2.9.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108.

Test Procedure

The UE is in URA_PCH state. When the UE detects the expiry of periodic URA updating timer T305, the UE moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH. The message shall indicate the cause to be "periodic URA update" in IE "URA update cause". The SS transmits RRC CONNECTION RELEASE message on downlink CCCH. The UE shall return to idle mode after release of all current signalling flows and radio access bearers. 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				The UE is in the URA_PCH state. SS wait until T305 timer has expired.
2			URA UPDATE	UE shall transmit this message and set value "periodic URA update" into IE "URA update cause".
3			RRC CONNECTION RELEASE	SS transmits RRC CONNECTION RELEASE message to the UE on the downlink CCCH.
4				The UE releases L2 signalling radio bearer and radio resources then the UE goes to idle mode.
5			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

URA UPDATE (Step 2)

The same message found in Clause 9 of TS 34.108 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
URA Update Cause	Check to see if set to ‘Periodic URA update’

RRC CONNECTION RELEASE (Step 3)

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

8.3.2.9.5 Test requirement

After step 1 the UE shall transmit a URA UPDATE message on the uplink CCCH and set value "periodic URA update" into IE "Cell update cause".

After step 3 the UE shall enter idle state.

8.3.2.10 URA Update: Reception of URA UPDATE CONFIRM message that causes invalid configuration

8.3.2.10.1 Definition

8.3.2.10.2 Conformance Requirement

If the variable INVALID_CONFIGURATION is set to TRUE, the UE shall:

1> if V302 is equal to or smaller than N302:

2> in case of a URA update procedure:

3> set the contents of the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;

3> submit the URA UPDATE message for transmission on the uplink CCCH.

2> increment counter V302;

2> restart timer T302 when the MAC layer indicates success or failure to transmit the message.

1> if V302 is greater than N302:

…

Reference

3GPP TS 25.331 clause 8.3.1.9

8.3.2.10.3 Test Purpose

1. To confirm that the UE retransmits a URA UPDATE message when it receives a URA UPDATE CONFIRM message that will trigger an invalid configuration in the UE, if the number of retransmissions has not reached the maximum allowed value.

8.3.2.10.4 Method of Test

Initial Condition

System Simulator: 1 cell

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108.

Test Procedure

The UE is in URA_PCH state. When the UE detects the expiry of timer T305 according to the system information, the UE moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH. This message shall contain value "periodic URA update" in IE "URA update cause". Upon receiving such a message, the SS replies with a URA UPDATE CONFIRM message with IE "RRC State Indicator" set to "CELL_DCH" on the downlink CCCH. The UE shall detect its variable "invalid configuration" is set and re-transmit URA UPDATE message. SS then transmit a valid URA UPDATE CONFIRM message on the downlink CCCH to end the procedure.

Expected Sequence

Step	Direction		Message	Comment
	UE	SS
1				The UE is in the URA_PCH state. SS wait until T305 timer has expired.
2			URA UPDATE	UE shall transmit this message and set value "periodic URA update" into IE "URA update cause".
3			URA UPDATE CONFIRM
4			URA UPDATE	IE "Protocol error indicator" is set to TRUE and IE "Protocol error information" is set to "Information element value not comprehended".
5			Void
6			Void
7			URA UPDATE CONFIRM

URA UPDATE (Step 2)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
URA Update Cause	Check to see if set to ‘Periodic URA update’

URA UPDATE (Step 4)

The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:

Information Element	Value/remark
U-RNTI
– SRNC Identity	Check to see if set to ‘0000 0000 0001’
– S-RNTI	Check to see if set to ‘0000 0000 0000 0000 0001’
URA Update Cause	Check to see if set to ‘Periodic URA update’
Protocol error indicator	TRUE
Protocol error information
– Protocol error cause	Information element value not comprehended

URA UPDATE CONFIRM (Step 3)

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

Information Element	Value/remark
RRC State Indicator	CELL_DCH

8.3.2.10.5 Test Requirement

After step 3 the UE shall transmit a URA UPDATE message on the uplink CCCH, setting value “TRUE" in IE "Protocol error indicator", value "periodic URA update" in IE "URA update cause" and value "Information element value not comprehended" in "Protocol error cause".

8.3.2.11 URA Update: Cell reselection to cell of another PLMN belonging to the equivalent PLMN list

8.3.2.11.1 Definition

8.3.2.11.2 Conformance requirement

1. A UE in URA_PCH state shall initiate the URA update procedure in the following cases:

– URA reselection:

– if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not present in the list of URA identities in system information block type 2; or

– if the list of URA identities in system information block type 2 is empty; or

– if the system information block type 2 can not be found:

– perform URA update using the cause "change of URA".

2. A "suitable cell" is a cell on which the UE may camp on to obtain normal service. Such a cell shall fulfil all the following requirements.

– The cell is part of the selected PLMN or, of a PLMN considered as equivalent by the UE according to the information provided by the NAS.

– The cell is not barred, see clause 5.3.1.1 in TS 25.304.

– The cell is not part of the list of "forbidden LAs for roaming" TS 22.011

– The cell selection criteria are fulfilled, see clause 5.2.3.1.2 in TS 25.304.

3. The Mobile Equipment shall store a list of "equivalent PLMNs". This list is replaced or deleted at the end of each location update procedure, routing area update procedure and GPRS attach procedure. The stored list consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the network that downloaded the list. The stored list shall not be deleted when the MS is switched off. The stored list shall be deleted if the SIM is removed. The maximum number of possible entries in the stored list is six.

Reference

3GPP TS 25.331 clause 8.3.1.2.

3GPP TS 25.304 clause 4.3.

3GPP TS 24.008 clause 4.4.1.

8.3.2.11.3 Test purpose

1. To confirm that the UE executes a URA update procedure after a successful reselection of another UTRA cell with a URA identity that is not the URA of the UE and with a PLMN identity different from the original cell but with a PLMN that is part of the equivalent PLMN list in the UE.

NOTE: Verifies conformance requirements 1, 2 and 3.

2. To confirm that the UE refrains from executing a URA update procedure to a better UTRA cell with another PLMN identity when that PLMN identity is not part of the equivalent PLMN list in the UE.

NOTE: Test case in 8.3.2.1 is a test where the UE reselects to a cell with the same PLMN identity as the registered PLMN.

8.3.2.11.4 Method of test

Initial Condition

System Simulator: 3 cells – Cell 1 is active, with the downlink transmission power shown in column marked "T0" in table 8.3.2.1-1, while cell 4 and cell 7 is inactive.

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

UE: Shall have stored equivalent PLMN list containing PLMN-1 and PLMN-2. The equivalent PLMN list stored in the UE shall not contain PLMN-3. The UE shall also have stored the URA identity URA-ID 1 from the list of URA-IDs in cell 1.

Test Procedure

Table 8.3.2.11-1

Parameter	Unit	Cell 1			Cell 4			Cell 7
		T0	T1	T2	T0	T1	T2	T0	T1	T2
UTRA RF Channel Number		Mid Range Test Frequency			High Range Test Frequency			Low Range Test Frequency
PLMN identity		PLMN-1			PLMN-2			PLMN-3
URA identity		URA-ID 1			URA-ID 2			URA-ID 3
CPICH Ec (FDD)	dBm/3.84MHz	-58	-69	-69	Cell 4 is switched off	-58	-58	Cell 7 is switched off	Cell 7 is switched off	-47
P-CCPCH RSCP (TDD)	dBm	-62	-68	-68	Cell 4 is switched off	-62	-68	Cell 7 is switched off	Cell 7 is switched off	-62

Table 8.3.2.11-1 illustrates the downlink power to be applied for the 3 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions, while columns marked "T1" and "T2" are to be applied subsequently.

a) At T0, the SS activates Cell 1.

b) At T1, the SS activates Cell 4, and monitors Cell 4 for received messages from UE.

c) UE re-selects to Cell 4, and sends a URA UPDATE message. The SS replies with an URA UPDATE CONFIRM message on the downlink CCCH.

d) At T2, the SS activates Cell 7, and monitors Cell 7 for received messages from UE.

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				UE is in URA_PCH state, camped on Cell 1 and registered to PLMN1. SS applies downlink transmission power settings according to values in column "T0" of table 8.3.2.11-1.
1a			MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 3	Modified SIB 3 and MIB
1b			PAGING TYPE 1	Include IE "BCCH modification info"
1c				Wait 5 seconds to allow UE to read new system information
1d				SS applies downlink transmission power settings according to values in column "T1" of table 8.3.2.11-1.
2			URA UPDATE	The UE moves to CELL_FACH state and transmits this message in Cell 4. The value "change of URA" shall be set in IE "URA update cause".
3			URA UPDATE CONFIRM	The value "URA_PCH" set in IE "RRC State Indicator".
4				SS applies downlink transmission power settings according to values in column "T2" of table 8.3.2.11-1.
5				SS monitors that the UE does not send a URA UPDATE message or any other message.
6			CALL C.5	If the test result of C.5 indicates that UE is in URA_PCH state, the test passes, otherwise it fails.

Specific Message Contents

MASTER INFORMATION BLOCK (Step 1a)

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

Information Element	Value/remark
MIB Value Tag	Set to (Current MIB value tag + 1)
SIB 3 Cell Value tag	Set to (Current SIB3 value tag + 1)

System Information Block type 3 (Step 1a)

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

– Qqualmin

-16

PAGING TYPE 1 (Step 1b)

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

Information Element	Value/remark
Paging record list	Not Present
BCCH modification info
MIB Value tag	Set to latest value transmitted in MIB
BCCH modification time	Not present

URA UPDATE (Step 2)

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

Information Element	Value/remark
URA Update Cause	Check to see if set to ‘change of URA’

URA UPDATE CONFIRM (Step 3)

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

8.3.2.11.5 Test requirement

After Step 1d the UE shall send a URA UPATE message.

After Step 4 the UE shall refrain from sending a URA update (or any other message).

8.3.2.12 Restricted cell reselection to a cell belonging to forbidden LA list (URA_PCH)

8.3.2.12.1 Definition

8.3.2.12.2 Conformance requirement

1. A UE in URA_PCH state shall initiate the URA update procedure in the following cases:

– URA reselection:

– if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not present in the list of URA identities in system information block type 2; or

– if the list of URA identities in system information block type 2 is empty; or

– if the system information block type 2 can not be found:

– perform URA update using the cause "change of URA".

2. A "suitable cell" is a cell on which the UE may camp on to obtain normal service. Such a cell shall fulfil all the following requirements.

– The cell is part of the selected PLMN or, of a PLMN considered as equivalent by the UE according to the information provided by the NAS.

– The cell is not barred, see clause 5.3.1 in TS 25.304.

– The cell is not part of the list of "forbidden LAs for roaming" in TS 22.011.

– The cell selection criteria are fulfilled, see clause 5.2.3.1.2 in TS 25.304.

3. The Mobile Equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden location areas for regional provision of service". These lists shall be erased when the MS is switched off or when the SIM is removed, and periodically (with period in the range 12 to 24 hours). The location area identification received on the BCCH that triggered the location updating request shall be added to the suitable list whenever a location update reject message is received with the cause "Roaming not allowed in this location area" or with the cause "Location Area not allowed". The lists shall accommodate each 10 or more location area identifications. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted.

Reference

3GPP TS 25.331 clause 8.3.1.2.

3GPP TS 25.304 clause 4.3.

3GPP TS 24.008 clause 4.4.1.

8.3.2.12.3 Test purpose

1. To confirm that the UE refrains from selecting a UTRA cell and performing a URA update if that cell has a LA identity that is part of the list of LAs stored in the UE as "forbidden location areas for roaming".

NOTE: Test case in 8.3.2.1 is a test where the UE reselects to a cell with the same LA identity as the LA identity in the original cell.

8.3.2.12.4 Method of test

Initial Condition

System Simulator: 2 cells – Cell 1 is active, with the downlink transmission power shown in column marked "T0" in table 8.3.2.12-1, while cell 4 is inactive.

Qqualmin value for Cell 1 is set to -16 dB in SIB3 and SIB4 (FDD only) (see specific message contents).

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

UE: Shall have stored LA-ID 2 into the list of "forbidden location areas for roaming". The UE shall also have stored the URA identity URA-ID 1 from the list of URA-IDs in cell 1.

Test Procedure

Table 8.3.2.12-1

Parameter	Unit	Cell 1		Cell 4
		T0	T1	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency		High Range Test Frequency
URA identity		URA-ID 1		URA-ID 2
LA identity		LA-ID 1		LA-ID 2
CPICH Ec (FDD)	dBm/3.84MHz	-73	-73	Cell 4 is switched off	-67
P-CCPCH RSCP (TDD)	dBm	-62	-68	Cell 4 is switched off	-62

Table 8.3.2.12-1 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions, while column marked "T1" are to be applied subsequently.

a) At T1, verify that the UE does not reselect to cell 4 and not send a URA update in cell 4, although cell 4 is the best cell.

b) SS calls for generic procedure C.5 to check that UE is in URA_PCH state in cell 1.

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				UE is in URA_PCH state, camped on Cell 1 and registered to PLMN1. SS applies downlink transmission power settings according to values in column "T0" of table 8.3.2.12-1.
2				SS applies downlink transmission power settings according to values in column "T1" of table 8.3.2.12-1.
3				SS monitors that the UE does not send a URA UPDATE message or any other message within 30 seconds of step 2.
4			CALL C.5	If the test result of C.5 indicates that UE is in URA_PCH state in cell 1, the test passes, otherwise it fails.

Specific Message Contents

MASTER INFORMATION BLOCK

Use the same message sub-type found in clause 6.1.0a.3 of TS 34.108, with the following exception.

Information Element	Value/remark
MIB Value Tag	Set to (Current MIB value tag + 1)
SIB 3 Cell Value tag	Set to (Current SIB3 value tag + 1)
SIB 4 Cell Value tag	Set to (Current SIB4 value tag + 1)

System Information Block type 3

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

– Qqualmin

-16

System Information Block type 4

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

– Qqualmin

-16

8.3.2.12.5 Test requirement

After Step 2 the UE shall refrain from sending a URA UPDATE (or any other message).

8.3.2.13 URA Update: Change of URA due to HCS Cell Reselection

8.3.2.13.1 Definition

8.3.2.13.2 Conformance requirement

1. The quality level threshold criterion H for hierarchical cell structures is used to determine whether prioritised ranking according to hierarchical cell re-selection rules shall apply, and is defined by:

…

2. The cell-ranking criterion R is defined by:

where:

TEMP_OFFSET_n applies an offset to the H and R criteria for the duration of PENALTY_TIME_n after a timer T_n has started for that neighbouring cell.

The timer T_n is implemented for each neighbouring cell. T_n shall be started from zero when one of the following conditions becomes true:

– if HCS_PRIO_n <> HCS_PRIO_s and

Q_meas,_n> Qhcs_n

– if HCS_PRIO_n = HCS_PRIO_s and

– for serving FDD and neighbour FDD cells if the quality measure for cell selection and reselection is set to CPICH RSCP in the serving cell, and:

Q_meas,n > Q_meas,_s+ Qoffset1_s,n

– for serving FDD and neighbour FDD cells if the quality measure for cell selection and reselection is set to CPICH Ec/No in the serving cell, and:

Q_meas,n > Q_meas,_s+ Qoffset2_s,n

– for all other serving and neighbour cells:

Q_meas,n > Q_meas,_s+ Qoffset1_s,n

T_n for the associated neighbour cell shall be stopped as soon as any of the above conditions are no longer fulfilled. Any value calculated for TO_n is valid only if the associated timer T_n is still running else TO_n shall be set to zero.

At cell-reselection, a timer T_n is stopped only if the corresponding cell is not a neighbour cell of the new serving cell, or if the criteria given above for starting timer T_n for the corresponding cell is no longer fulfilled with the parameters of the new serving cell. On cell re-selection, timer T_n shall be continued to be run for the corresponding cells but the criteria given above shall be evaluated with parameters broadcast in the new serving cell if the corresponding cells are neighbours of the new serving cell.

…

3. The cell selection criterion S used for cell reselection is fulfilled when:

Where :

…

4. The UE shall perform ranking of all cells that fulfil the S criterion among

– all cells that have the highest HCS_PRIO among those cells that fulfil the criterion H >= 0. Note that this rule is not valid when UE high-mobility is detected.

– all cells, not considering HCS priority levels, if no cell fulfil the criterion H >= 0. This case is also valid when it is indicated in system information that HCS is not used, that is when serving cell does not belong to a hierarchical cell structure.

The cells shall be ranked according to the R criteria.

The best ranked cell is the cell with the highest R value.

5. If an FDD cell is ranked as the best cell and the quality measure for cell selection and re-selection is set to CPICH RSCP, the UE shall perform cell re-selection to that FDD cell.

In all cases, the UE shall reselect the new cell, only if the following conditions are met:

– the new cell is better ranked than the serving cell during a time interval Treselection.

– more than 1 second has elapsed since the UE camped on the current serving cell.

…

6. The cell reselection process in Connected Mode is the same as cell reselection evaluation process used for idle mode, described in subclause 5.2.6 of 25.304.

7. A UE in URA_PCH state shall initiate the URA update procedure in the following cases:

1> URA reselection:

2> if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not present in the list of URA identities in system information block type 2; or

…

3> perform URA update using the cause "change of URA".

Reference

3GPP TS 25.304 clause 5.2.6.1.4

3GPP TS 25.304 clause 5.4.3

3GPP TS 25.331 clause 8.3.1

8.3.2.13.3 Test purpose

1. To confirm that the UE can read HCS related SIB information and act upon all HCS parameters in URA_PCH state.

2. To confirm that the UE executes an URA update procedure after the successful change of URA due to HCS Cell Reselection in URA_PCH state.

3. To confirm UE responds correctly when it re-selects to a new cell while waiting from URA UPDATE CONFIRM message from SS.

8.3.2.13.4 Method of test

Initial Condition

System Simulator: 3 cells – Cell 1 is active with URA-ID 1 and downlink transmission power shown in column marked "T0" in table 8.3.2.13-1. Cell2 with URA-ID 1 and Cell 3 with URA-ID 2 are switched off

UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE, with URA-ID 1 from the list of URA-ID in cell 1

Specific Message Content

For system information blocks 4 and 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.

Contents of System Information Block type 4 (FDD)

Information Element	Value/remark
– Cell selection and re-selection info
– CHOICE mode	FDD
– Sintersearch	0 dB
– SsearchHCS	17 (35 dB)
– RAT List	This parameter is configurable
– S_{limit,SearchRAT}	0
– Qqualmin	-20 dB
– Qrxlevmin	-58 (-115 dBm)
– Qhyst1s	7 (gives actual value of 14 dB)
– Qhyst2s	Not Present
– HCS Serving cell information
-HCS Priority	6
– Q HCS	39 (results in actual value of –76)
– TcrMax	Not Present

Contents of System Information Block type 4 (3.84 Mcps TDD, 1.28 Mcps TDD and 7.68 Mcps TDD)

Information Element	Value/remark
– Cell selection and re-selection info
– CHOICE mode	TDD
– SsearchHCS	23 (47 dB)
– Qhyst1s	10 (gives actual value of 20 dB)
– HCS Serving cell information
-HCS Priority	6
– Q HCS	39 (results in actual value of –76)
– TcrMax	Not Present

Contents of System Information Block type 11 (FDD) (Cell 1)

Information Element	Value/remark
– SIB 12 indicator	FALSE
– Measurement control system information
– Use of HCS	used
– Cell selection and reselection quality measure	CPICH RSCP
– Intra-frequency measurement system information
– Intra-frequency cell info list
– New intra-frequency cells
– Intra-frequency cell id	1
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.1 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– Cell Selection and Re-selection info	Not Present
– Intra-frequency cell id	2
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info
– Qoffset1s,n	-20 dB
– Maximum allowed UL TX power	33 dBm
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	FDD
– Qqualmin	-20 dB
– Qrxlevmin	-58 (-115 dBm)
– Intra-frequency cell id	3
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.3 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info
– Qoffset1s,n	-20dB
– Maximum allowed UL TX power	33 dBm
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	FDD
– Qqualmin	-20 dB
– Qrxlevmin	-58 (-115 dBm)

Contents of System Information Block type 11 (3.84 Mcps TDD 1.28 Mcps TDD and 7.68 Mcps TDD) (Cell 1)

Information Element	Value/remark
– SIB 12 indicator	FALSE
– Measurement control system information
– Use of HCS	used
– Intra-frequency cell info list
– New intra-frequency cells
– Intra-frequency cell id	2
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not Present
– CHOICE mode	TDD
– Primary CCPCH info
– Cell parameters ID	Reference clause 6.1 Default settings for cell
– Primary CCPCH TX power	Not Present
– Timeslot list	Not Present
– Burst type	Not Present
– Cell Selection and Re-selection info
– Qoffset1s,n	-20 dB
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	TDD
– Qrxlevmin	-52 (-103 dBm)
– Intra-frequency cell id	3
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not Present
– CHOICE mode	TDD
– Primary CCPCH info
– Cell parameters ID	Reference clause 6.1 Default settings for cell
– Primary CCPCH TX power	Not Present
– Timeslot list	Not Present
– Burst type	Not Present
– Cell Selection and Re-selection info
– Qoffset1s,n	-20dB
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	TDD
– Qrxlevmin	-52 (-103 dBm)

Test Procedure

Table 8.3.2.13-1

Parameter	Unit	Cell 1			Cell 2			Cell 3
Parameter	Unit	T0	T1	T2	T0	T1	T2	T0	T1	T2
Cell id in system information		1			2			3
UTRA RF Channel Number		Mid Range Test Frequency			Mid Range Test Frequency			Mid Range Test Frequency
HCS Priority		6			7			7
CPICH Ec (FDD)	dBm/3.84 MHz	-60	-65	-65	-83	-83	-69	-83	-69	-69
H* (During penalty time)		16	11	-1	-19	-19	7	-19	-5	7
H* (After PenaltyTime)		16	11	11	-7	-7	7	-7	7	7
P-CCPCH RSCP (TDD)	dBm	-61	-61	-61	-80	-80	-67	-80	-73	-73
H* (After PenaltyTime)		15	15	15	-4	-4	9	-4	3	3
R* (During PenaltyTime)		-46	-51	-45	-63	-63	-61	-63	-49	-55
R* (After PenaltyTime)		-46	-51	-45	-63	-63	-49	-63	-49	-55

(*) Note: this parameter is calculated internally in the UE and is only shown for clarification of the test procedure.

The UE is in the URA_PCH state and assigned with only 1 URA identity in cell 1: URA-ID 1. SS configures Cell 2 and 3 with power level given in column "T0", and URA-Id 1 and 2 respectively and starts broadcast of BCCH on the primary CCPCH in cells 2 and 3. UE shall remain camped on the Cell 1 even after expiry of penalty time i.e. 40 seconds. SS sets downlink transmission power settings according to columns "T1" in table 8.3.2.13-1. SS then adjusts the transmission power again according to ‘T1’ column. This is expected to cause the UE to perform a cell reselection to cell 3 after at-least 40 Seconds (Penalty Time) after the power levels have been changed. UE on performing cell reselection to cell 3 finds that its current URA-ID 1 is not in the new broadcasted list of URA-IDs, it moves to CELL_FACH state and transmits a URA UPDATE message on the uplink CCCH. After the SS receives this message, it transmits URA UPDATE CONFIRM message to the UE on the downlink CCCH. The "RRC State Indicator" is set to "URA_PCH". UE returns to URA_PCH state in cell 3 without sending a uplink response message. Next SS adjusts the transmission power according to ‘T2’ column. After the expiry of penalty time the UE shall re-select to cell 2, and transmit URA UPDATE message to SS. However, SS do not acknowledge but adjusts the transmission power according to ‘T0’ column. UE shall perform cell re-selection to cell 1 and then sent URA UPDATE message to SS. Finally SS shall transmit URA UPDATE CONFIRM message to UE on the downlink CCCH. UE shall return to URA_PCH state in Cell 1 and will not transmit anything on PRACH.

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 UE is updated with only 1 URA identity carried currently by cell 1. The starting state of the UE is URA_PCH
2			BCCH	SS configures cell 2 (with URA-ID 1) and Cell 3 (with URA-ID 2) and power levels as given in column T0 of table 8.3.2.13-1 and starts transmission of BCCH.
3				UE shall Remain camped on Cell 1 and in URA_PCH state even after expiry of Penalty time.
4				SS set the power transmission of all cells according to column ‘T1’ of table 8.3.2.13-1.
5			URA UPDATE	The UE shall perform a cell reselection first after the penalty time to cell 3 and when it finds that its current URA-ID 1 is not in the new broadcasted list of URA-IDs, it shall then transmit this message and set value "change of URA" into IE "URA update cause".
6			URA UPDATE CONFIRM	Message sent on CCCH.
7				SS set the power transmission of all cells according to column ‘T2’ of table 8.3.2.13-1. SS makes sure that the UE does not send an URA Update message during penalty time
8			URA UPDATE	In Cell 2
9				SS do not respond to the URA UPDATE message from UE and set the power transmission of all cells according to column ‘T0’ of table 8.3.2.13-1.
10			URA UPDATE	In Cell 1
11			URA UPDATE CONFIRM	Message sent on CCCH.

Specific Message Contents

The contents of system information block 4 and 11 messages are identical as system information block 4 and 11 messages as found in 34.108 clause 6.1 with the following exceptions:

Contents of System Information Block type 4 (FDD) (Cell 2 and 3)

Information Element	Value/remark
– Cell selection and re-selection info
– CHOICE mode	FDD
– Sintersearch	0 dB
– SsearchHCS	17 (35 dB)
– RAT List	This parameter is configurable
– S_{limit,SearchRAT}	0
– Qqualmin	-20 dB
– Qrxlevmin	-115 dBm
– Qhyst1s	7 (gives actual value of 14 dB)
– Qhyst2s	Not Present
– HCS Serving cell information
-HCS Priority	7
– Q HCS	39 (results in actual value of –76)
– TcrMax	Not Present

Contents of System Information Block type 4 (3.84 Mcps TDD, 1.28 Mcps TDD and 7.68 Mcps TDD) (Cell 2 and 3)

Information Element	Value/remark
– Cell selection and re-selection info
– CHOICE mode	TDD
– SsearchHCS	23 (47 dB)
– Qhyst1s	10 (gives actual value of 20 dB)
– HCS Serving cell information
-HCS Priority	7
– Q HCS	39 (results in actual value of –76)
– TcrMax	Not Present

Contents of System Information Block type 11 (FDD) (Cell 2)

Information Element	Value/remark
– SIB 12 indicator	FALSE
– Measurement control system information
– Use of HCS	used
– Cell selection and reselection quality measure	CPICH RSCP
– Intra-frequency measurement system information
– Intra-frequency cell info list
– New intra-frequency cells
– Intra-frequency cell id	2
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– Cell Selection and Re-selection info	NOT PRESENT
– Intra-frequency cell id	1
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.1 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info
– Qoffset1s,n	-20dB
– Maximum allowed UL TX power	33 dBm
– HCS neighbouring cell information	Present
– HCS_Priority	6
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	FDD
– Qqualmin	-20 dB
– Qrxlevmin	-58 (-115 dBm)
– Intra-frequency cell id	3
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.3 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info
– Qoffset1s,n	-20 dB
– Maximum allowed UL TX power	33 dBm
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	FDD
– Qqualmin	-20 dB
– Qrxlevmin	-58 (-115 dBm)

Contents of System Information Block type 11 (3.84 Mcps TDD, 1.28 Mcps TDD and 7.68 Mcps TDD) (Cell 2)

Information Element	Value/remark
– SIB 12 indicator	FALSE
– Measurement control system information
– Use of HCS	used
– Intra-frequency cell info list
– New intra-frequency cells
– Intra-frequency cell id	1
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not Present
– CHOICE mode	TDD
– Primary CCPCH info
– Cell parameters ID	Reference clause 6.1 Default settings for cell
– Primary CCPCH TX power	Not Present
– Timeslot list	Not Present
– Burst type	Not Present
– Cell Selection and Re-selection info
– Qoffset1s,n	-20 dB
– HCS neighbouring cell information	Present
– HCS_Priority	6
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	TDD
– Qrxlevmin	-52 (-103 dBm)
– Intra-frequency cell id	3
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not Present
– CHOICE mode	TDD
– Primary CCPCH info
– Cell parameters ID	Reference clause 6.1 Default settings for cell
– Primary CCPCH TX power	Not Present
– Timeslot list	Not Present
– Burst type	Not Present
– Cell Selection and Re-selection info
– Qoffset1s,n	-20dB
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	TDD
– Qrxlevmin	-52 (-103 dBm)

Contents of System Information Block type 11 (FDD) (Cell 3)

Information Element	Value/remark
– SIB 12 indicator	FALSE
– Measurement control system information
– Use of HCS	used
– Cell selection and reselection quality measure	CPICH RSCP
– Intra-frequency measurement system information
– Intra-frequency cell info list
– New intra-frequency cells
– Intra-frequency cell id	3
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.3 (FDD)" in clause 6.1.4
– Cell Selection and Re-selection info	NOT PRESENT
– Intra-frequency cell id	1
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.1 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info
– Qoffset1s,n	-20 dB
– Maximum allowed UL TX power	33 dBm
– HCS neighbouring cell information	Present
– HCS_Priority	6
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	FDD
– Qqualmin	-20 dB
– Qrxlevmin	-58 (-115 dBm)
– Intra-frequency cell id	2
– Cell info
– Cell individual offset	Not Present
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info
– Qoffset1s,n	-20 dB
– Maximum allowed UL TX power	33 dBm
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	FDD
– Qqualmin	-20 dB
– Qrxlevmin	-58 (-115 dBm)

Contents of System Information Block type 11 (3.84 Mcps TDD, 1.28 Mcps TDD and 7.68 Mcps TDD) (Cell 3)

Information Element	Value/remark
– SIB 12 indicator	FALSE
– Measurement control system information
– Use of HCS	used
– Intra-frequency cell info list
– New intra-frequency cells
– Intra-frequency cell id	1
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not Present
– CHOICE mode	TDD
– Primary CCPCH info
– Cell parameters ID	Reference clause 6.1 Default settings for cell
– Primary CCPCH TX power	Not Present
– Timeslot list	Not Present
– Burst type	Not Present
– Cell Selection and Re-selection info
– Qoffset1s,n	-20 dB
– HCS neighbouring cell information	Present
– HCS_Priority	6
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	TDD
– Qrxlevmin	-52 (-103 dBm)
– Intra-frequency cell id	2
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not Present
– CHOICE mode	TDD
– Primary CCPCH info
– Cell parameters ID	Reference clause 6.1 Default settings for cell
– Primary CCPCH TX power	Not Present
– Timeslot list	Not Present
– Burst type	Not Present
– Cell Selection and Re-selection info
– Qoffset1s,n	-20dB
– HCS neighbouring cell information	Present
– HCS_Priority	7
-Q_HCS	39 (results in actual value of –76)
-HCS Cell Reselection Information
– Penalty Time	40
-Temporary Offset	12
– CHOICE mode	TDD
– Qrxlevmin	-52 (-103 dBm)

URA UPDATE (Step 5, 8 and 10)

Information Element	Value/remark
URA Update Cause	Check to see if set to ‘change of URA’

URA UPDATE CONFIRM (Steps 6 and 11)

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

8.3.2.13.5 Test requirement

After step 4 the UE shall find that URA-ID 2 is not in its maintained list of URA-IDs. After cell reselection, the UE shall move to CELL_FACH state and transmit URA UPDATE message setting value "change of URA" into IE "URA update cause".

After step 7 the UE shall find that URA-ID 1 is not in its maintained list of URA-IDs. After cell reselection, the UE shall move to CELL_FACH state and transmit URA UPDATE message setting value "change of URA" into IE "URA update cause".