8.3.1 Cell and URA update procedures

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

Figure 8.3.1-1: Cell update procedure, basic flow

Figure 8.3.1-2: Cell update procedure with update of UTRAN mobility information

Figure 8.3.1-3: Cell update procedure with physical channel reconfiguration

Figure 8.3.1-4: Cell update procedure with transport channel reconfiguration

Figure 8.3.1-5: Cell update procedure with radio bearer release

Figure 8.3.1-6: Cell update procedure with radio bearer reconfiguration

Figure 8.3.1-6a: Cell update procedure with radio bearer setup

Figure 8.3.1-7: Cell update procedure, failure case

Figure 8.3.1-8: URA update procedure, basic flow

Figure 8.3.1-9: URA update procedure with update of UTRAN mobility information

Figure 8.3.1-10: URA update procedure, failure case

8.3.1.1 General

The URA update and cell update procedures serve several main purposes:

– to notify UTRAN after re-entering service area in the URA_PCH or CELL_PCH state;

– to notify UTRAN of an RLC unrecoverable error [16] on an AM RLC entity;

– to be used as a supervision mechanism in the CELL_FACH, CELL_PCH, or URA_PCH state by means of periodical update.

In addition, the URA update procedure also serves the following purpose:

– to retrieve a new URA identity after cell re-selection to a cell not belonging to the current URA assigned to the UE in URA_PCH state.

In addition, the cell update procedure also serves the following purposes:

– to update UTRAN with the current cell the UE is camping on after cell reselection;

– to act on a radio link failure in the CELL_DCH state;

– to act on the transmission failure of the UE CAPABILITY INFORMATION message;

– for FDD and 1.28 Mcps TDD, if the variable H_RNTI is not set, and for 3.84 Mcps TDD and 7.68 Mcps TDD:
when triggered in the URA_PCH or CELL_PCH state, to notify UTRAN of a transition to the CELL_FACH state due to the reception of UTRAN originated paging or due to a request to transmit uplink data;

– to count the number of UEs in URA_PCH, CELL_PCH and CELL_FACH that are interested to receive an MBMS transmission;

– when triggered in the URA_PCH, CELL_PCH and CELL_FACH state, to notify UTRAN of the UEs interest to receive an MBMS service;

– to request the MBMS P-T-P RB setup by the UE in CELL_PCH, URA_PCH and CELL_FACH state.

The URA update and cell update procedures may:

1> include an update of mobility related information in the UE;

1> cause a state transition from the CELL_FACH state to the CELL_DCH, CELL_PCH or URA_PCH states or idle mode.

The cell update procedure may also include:

– a re-establish of AM RLC entities;

– a re-establish of UM RLC entities;

– a radio bearer release, radio bearer reconfiguration, transport channel reconfiguration or physical channel reconfiguration.

8.3.1.2 Initiation

A UE shall initiate the cell update procedure in the following cases:

1> Uplink data transmission:

2> for FDD and 1.28 Mcps TDD, if the variable H_RNTI is not set, and for 3.84 Mcps TDD and 7.68 Mcps TDD:

3> if the UE is in URA_PCH or CELL_PCH state; and

3> if timer T320 is not running:

4> if the UE has uplink RLC data PDU or uplink RLC control PDU on RB1 or upwards to transmit:

5> perform cell update using the cause "uplink data transmission".

3> else:

4> if the variable ESTABLISHMENT_CAUSE is set:

5> perform cell update using the cause "uplink data transmission".

1> Paging response:

2> if the criteria for performing cell update with the cause specified above in the current subclause are not met; and

2> if the UE in URA_PCH or CELL_PCH state, receives a PAGING TYPE 1 message fulfilling the conditions for initiating a cell update procedure specified in subclause 8.1.2.3:

3> perform cell update using the cause "paging response".

1> Radio link failure:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met:

3> if the UE is in CELL_DCH state and the criteria for radio link failure are met as specified in subclause 8.5.6; or

3> if the transmission of the UE CAPABILITY INFORMATION message fails as specified in subclause 8.1.6.6; or

3> if the UE detects PDCP Unrecoverable Error [36] in a PDCP entity:

4> perform cell update using the cause "radio link failure".

1> MBMS ptp RB request:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and

2> if the UE is in URA_PCH, CELL_PCH or CELL_FACH state; and

2> if timer T320 is not running; and

2> if the UE should perform cell update for MBMS ptp radio bearer request as specified in subclause 8.6.9.6:

3> perform cell update using the cause "MBMS ptp RB request".

1> Re-entering service area:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and

2> if the UE is in CELL_FACH or CELL_PCH state; and

2> if the UE has been out of service area and re-enters service area before T307 or T317 expires:

3> perform cell update using the cause "re-entering service area".

1> RLC unrecoverable error:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and

2> if the UE detects RLC unrecoverable error [16] in an AM RLC entity:

3> perform cell update using the cause "RLC unrecoverable error".

1> Cell reselection:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met:

3> if the UE is in CELL_FACH or CELL_PCH state and the UE performs cell re-selection; or

3> if the UE is in CELL_FACH state and the variable C_RNTI is empty:

4> perform cell update using the cause "cell reselection".

1> Periodical cell update:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and

2> if the UE is in CELL_FACH or CELL_PCH state; and

2> if the timer T305 expires; and

2> if the criteria for "in service area" as specified in subclause 8.5.5.2 are fulfilled; 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> for FDD:

4> if the variable COMMON_E_DCH_TRANSMISSION is set to FALSE:

5> perform cell update using the cause "periodical cell update".

4> else:

5> restart the timer T305;

5> and end the procedure.

3> for 1.28 Mcps TDD and 3.84/7.68 Mcps TDD:

4> perform cell update using the cause "periodical cell update".

1> MBMS reception:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and

2> if the UE is in URA_PCH, CELL_PCH or CELL_FACH state; and

2> if the UE should perform cell update for MBMS counting as specified in subclause 8.7.4:

3> perform cell update using the cause "MBMS reception".

1> Transfer of application layer measurement report:

2> if the UE is in URA_PCH, CELL_PCH or CELL_FACH state; and

2> if the UE has received a "Container for application layer measurement reporting" which has not yet been sent:

3> perform cell update using the cause "application layer measurement report available".

NOTE: If the UE is not transferred to CELL_DCH after having successfully performed cell update using the cause "application layer measurement report available", the UE shall discard the application layer measurement report.

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

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:

3> if the timer T305 expires and 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"; or

3> if the conditions for initiating an URA update procedure specified in subclause 8.1.1.6.5 are fullfilled:

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

When initiating the URA update or cell update procedure, the UE shall:

1> if timer T320 is running:

2> stop timer T320;

2> if the UE has uplink RLC data PDU or uplink RLC control PDU on RB1 or upwards to transmit:

3> perform cell update using the cause "uplink data transmission".

2> else:

3> if the cell update procedure is not triggered due to Paging response or Radio link failure; and

3> if the UE should perform cell update for MBMS ptp radio bearer request as specified in subclause 8.6.9.6:

4> perform cell update using the cause "MBMS ptp RB request".

1> stop timer T319 if it is running;

1> stop timer T305;

1> for FDD and 1.28 Mcps TDD:

2> if the UE is in CELL_FACH state; and

2> if the IE "HS-DSCH common system information" is included in System Information Block type 5 or System Information Block type 5bis; and

2> for 1.28 Mcps TDD, if IE "Common E-DCH system info" in System Information Block type 5; and

2> if the UE does support HS-DSCH reception in CELL_FACH state:

3> if variable H_RNTI is not set or variable C_RNTI is not set; or

3> for FDD, an unrecoverable error [16] in an AM RLC entity detected:

4> clear variable H_RNTI;

4> clear variable C_RNTI;

4> clear variable E_RNTI;

4> clear any stored IEs "HARQ info";

4> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to TRUE;

4> and start receiving the HS-DSCH transport channels mapped physical channel(s) of type HS-SCCH and HS-PDSCH, by using parameters given by the IE(s) "HS-DSCH common system information" according to the procedure in subclause 8.5.37.

3> else:

4> receive the HS-DSCH transport channels mapped physical channel(s) of type HS-SCCH and HS-PDSCH, by using parameters given by the IE(s) "HS-DSCH common system information" according to the procedure in subclause 8.5.36;

4> determine the value for the HSPA_RNTI_STORED_PCH variable and take the corresponding actions as described in subclause 8.5.56;

4> determine the value for the READY_FOR_COMMON_EDCH variable and take the corresponding actions as described in subclause 8.5.47;

4> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46;

4> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75;

4> if variable READY_FOR_COMMON_EDCH is set to TRUE:

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

1> if the UE is in CELL_DCH state:

2> in the variable RB_TIMER_INDICATOR, set the IE "T314 expired" and the IE "T315 expired" to FALSE;

2> if the stored values of the timer T314 and timer T315 are both equal to zero; or

2> if the stored value of the timer T314 is equal to zero and there are no radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315" and signalling connection exists only to the CS domain:

3> release all its radio resources;

3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

3> clear the variable ESTABLISHED_RABS;

3> enter idle mode;

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

3> and the procedure ends.

2> if the stored value of the timer T314 is equal to zero:

3> release all radio bearers, associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314";

3> in the variable RB_TIMER_INDICATOR set the IE "T314 expired" to TRUE;

3> if all radio access bearers associated with a CN domain are released:

4> release the signalling connection for that CN domain;

4> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

4> indicate release (abort) of the signalling connection to upper layers.

2> if the stored value of the timer T315 is equal to zero:

3> release all radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315";

3> in the variable RB_TIMER_INDICATOR set the IE "T315 expired" to TRUE;

3> if all radio access bearers associated with a CN domain are released:

4> release the signalling connection for that CN domain;

4> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

4> indicate release (abort) of the signalling connection to upper layers.

2> if the stored value of the timer T314 is greater than zero:

3> if there are radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314":

4> start timer T314.

3> if there are no radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314" or "useT315" and the signalling connection exists to the CS domain:

4> start timer T314.

2> if the stored value of the timer T315 is greater than zero:

3> if there are radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315"; or

3> if the signalling connection exists to the PS domain:

4> start timer T315.

2> for the released radio bearer(s):

3> delete the information about the radio bearer from the variable ESTABLISHED_RABS;

3> when all radio bearers belonging to the same radio access bearer have been released:

4> indicate local end release of the radio access bearer to upper layers using the CN domain identity together with the RAB identity stored in the variable ESTABLISHED_RABS;

4> delete all information about the radio access bearer from the variable ESTABLISHED_RABS.

2> if the variable E_DCH_TRANSMISSION is set to TRUE:

3> set the variable E_DCH_TRANSMISSION to FALSE;

3> stop any E-AGCH and E-HICH reception procedures;

3> for FDD, stop any E-RGCH reception procedures;

3> for FDD, stop any E-DPCCH and E-DPDCH transmission procedures;

3> for 1.28 Mcps TDD, stop any E-PUCH transmission procedure;

3> clear the variable E_RNTI;

3> act as if the IE "MAC-es/e reset indicator" was received and set to TRUE;

3> release all E-DCH HARQ resources;

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

2> move to CELL_FACH state;

2> select a suitable UTRA cell on the current frequency according to [4];

2> clear variable E_RNTI and:

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

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> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75;

2> for 3.84 Mcps TDD and 7.68Mcps TDD; or

2> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception in CELL_FACH state; or

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

2> for 1.28 Mcps TDD, if the IE "Common E-DCH system info" is not included in System Information Block type 5:

3> select PRACH according to subclause 8.5.17;

3> select Secondary CCPCH according to subclause 8.5.19;

3> use the transport format set given in system information as specified in subclause 8.6.5.1;

3> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

2> else:

3> if variable READY_FOR_COMMON_EDCH is set to TRUE:

4> configure the Enhanced Uplink in CELL_FACH state and Idle mode as specified in subclause 8.5.45.

3> else:

4> select PRACH according to subclause 8.5.17 and:

5> use for the PRACH the transport format set given in system information as specified in subclause 8.6.5.1.

3> clear variable H_RNTI;

3> clear any stored IEs "HARQ info";

3> reset the MAC-ehs entity [15];

3> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to TRUE;

3> and start receiving the HS-DSCH according to the procedure in subclause 8.5.37.

2> for FDD, if the IE "Uplink CLTD info FDD" is stored in the UE:

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

2> for FDD, if the IE "Uplink OLTD info FDD" is stored in the UE:

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

2> set the variable ORDERED_RECONFIGURATION to FALSE.

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

1> set the variable CELL_UPDATE_STARTED to TRUE;

1> if any IEs releated to HS-DSCHare stored in the UE:

2> clear any stored IE "Downlink HS-PDSCH information";

2> clear any stored IE "Downlink Secondary Cell Info FDD";

2> clear all the entries from the variable TARGET_CELL_PRECONFIGURATION;

2> for 1.28Mcps TDD, clear the IE "HS-PDSCH Midamble Configuration" and the IE "HS-SCCH Set Configuration" in the IE "DL Multi Carrier Information";

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

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

1> if any IEs related to E-DCH are stored in the UE:

2> clear any stored IE "E-DCH info";

2> for FDD, clear any stored IE "Secondary serving E-DCH cell info" and IE "Secondary E-DCH info common";

2> for 1.28Mcps TDD, clear any stored IE "Multi-carrier E-DCH Info for LCR TDD";

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

1> if any of the IEs "DTX-DRX timing information" or "DTX-DRX information" are stored in the UE:

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

1> if the IE "HS-SCCH less information" is stored in the UE:

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

1> if any IEs related to MIMO are stored in the UE:

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

1> if the IE "MIMO mode with four transmit antennas" is stored in the UE:

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

1> for 1.28 Mcps TDD, if the IEs "Control Channel DRX Information" is stored in the UE:

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

1> for 1.28 Mcps TDD, if the IE "SPS information" is stored in the UE:

2> determine the value for the E_DCH_SPS_STATUS variable and take the corresponding actions as described in subclause 8.5.54;

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

1> for 1.28 Mcps TDD, if the IE "MU-MIMO info" is stored in the UE:

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

1> if the UE is not already in CELL_FACH state:

2> move to CELL_FACH state;

2> determine the value for the HSPA_RNTI_STORED_PCH variable and take the corresponding actions as described in subclause 8.5.56;

2> determine the value for the READY_FOR_COMMON_EDCH variable and take the corresponding actions as described in subclause 8.5.47;

2> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46;

2> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75;

2> for 1.28 Mcps TDD, determine the value for the MU_MIMO_STATUS variable and take the corresponding actions as described in subclause 8.5.61;

2> for 3.84 Mcps TDD and 7.68 Mcps TDD; or

2> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception in CELL_FACH state; or

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

2> for 1.28 Mcps TDD, if the IE "Common E-DCH system info" is not included in System Information Block type 5:

3> select PRACH according to subclause 8.5.17;

3> select Secondary CCPCH according to subclause 8.5.19;

3> use the transport format set given in system information as specified in subclause 8.6.5.1;

3> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

2> else:

3> if variable READY_FOR_COMMON_EDCH is set to TRUE:

4> configure the Enhanced Uplink in CELL_FACH state and Idle mode as specified in subclause 8.5.45.

3> else:

4> select PRACH according to subclause 8.5.17 and:

5> use for the PRACH the transport format set given in system information as specified in subclause 8.6.5.1.

3> if variable H_RNTI is not set or variable C_RNTI is not set:

4> clear variable C_RNTI;

4> clear variable H_RNTI;

4> clear any stored IEs "HARQ info";

4> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to TRUE;

4> and start receiving the HS-DSCH according to the procedure in subclause 8.5.37.

3> else:

4> receive the HS-DSCH according to the procedure in subclause 8.5.36.

1> if the UE performs cell re-selection in CELL_PCH or CELL_FACH state; or

1> if the UE performs cell re-selection in URA_PCH state and the URA_PCH_SEAMLESS_TRANSITION_RNTI_HANDLING_MODE variable is set to TRUE; or

1> if the UE performs URA re-selection in URA_PCH; or

1> if the UE re-enters service area and the UE supports HS-DSCH reception in CELL_FACH state and System Information Block type 5 or System Information Block type 5bis includes IE "HS-DSCH common system information", and for 1.28 Mcps TDD, System Information Block type 5 includes IE "Common E-DCH system info":

2> clear the variable C_RNTI; and

2> stop using that C_RNTI just cleared from the variable C_RNTI in MAC;

2> for FDD and 1.28 Mcps TDD, if the variable H_RNTI is set:

3> clear the variable H_RNTI; and

3> stop using that H_RNTI just cleared from the variable H_RNTI in MAC;

3> clear any stored IEs "HARQ info";

2> for FDD and 1.28 Mcps TDD, if the variable E_RNTI is set:

3> clear the variable E_RNTI.

2> determine the value for the HSPA_RNTI_STORED_PCH variable and take the corresponding actions as described in subclause 8.5.56;

2> determine the value for the READY_FOR_COMMON_EDCH variable and take the corresponding actions as described in subclause 8.5.47;

2> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46;

2> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75;

2> for FDD and 1.28 Mcps TDD, if the UE does support HS-DSCH reception in CELL_FACH state and IE "HS-DSCH common system information" is included in System Information Block type 5 or System Information Block type 5bis:

3> reset the MAC-ehs entity [15];

3> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to TRUE;

3> and start receiving the HS-DSCH according to the procedure in subclause 8.5.37.

2> else:

3> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

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

1> in case of a cell update procedure:

2> set the contents of the CELL UPDATE message according to subclause 8.3.1.3;

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

1> in case of a URA update procedure:

2> set the contents of the URA UPDATE message according to 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.

8.3.1.3 CELL UPDATE / URA UPDATE message contents to set

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

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

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

1> for FDD, if the UE supports the IE "Cell Update message with optimised encoding" and this IE is included in system information block type 5 or 5bis:

2> use "CELL UPDATE FDD" defined in subclause 10.2.7a to signal IEs;

1> else:

2> use "CELL UPDATE" defined in subclause 10.2.7 to signal IEs;

1> set the IE "Cell update cause" corresponding to the cause specified in subclause 8.3.1.2 that is valid when the CELL UPDATE message is submitted to lower layers for transmission;

NOTE: During the time period starting from when a cell update procedure is initiated by the UE until when the procedure ends, additional CELL UPDATE messages may be transmitted by the UE with different causes.

1> if the IE "Cell update cause" is set to "uplink data transmission" and if an event triggered traffic volume measurement has been configured:

2> if the TCTV is larger than the threshold in the IE "Reporting threshold" for a traffic volume measurement stored in the MEASUREMENT_IDENTITY variable and that traffic volume measurement has "measurement identity" equal to 4, "Traffic volume event identity" equal to "4a", "Measurement validity" equal to "all states" or "all states except CELL_DCH":

3> set the IE "Traffic volume indicator" to TRUE.

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

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

2> include the IE "RRC transaction identifier"; and

3> set it to the value of "RRC transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

2> include and set the IE "failure cause" to the cause value "protocol error";

2> set the IE "Protocol error information" set to the value of the variable PROTOCOL_ERROR_INFORMATION.

1> if the value of the variable FAILURE_INDICATOR is TRUE:

2> include the IE "RRC transaction identifier"; and

3> set it to the value of "RRC transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS.

2> include and set the IE "failure cause" to the value of the variable FAILURE_CAUSE.

1> if the variable "LATEST_CONFIGURED_CN_DOMAIN" has been initialised:

2> for each CN domain for which an entry exists in the variable ESTABLISHED_RABS or which is indicated in the variable LATEST CONFIGURED CN DOMAIN:

3> include the START value calculated according to subclause 8.5.9.

1> else:

2> include the START value for either the CS domain or the PS domain, calculated according to subclause 8.5.9.

1> if an unrecoverable error [16] in any of the AM RLC entities for the signalling radio bearers RB2, RB3 or RB4 is detected:

2> set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to TRUE;

2> set the variable AM_RLC_ERROR_PENDING_RB234 to TRUE.

1> otherwise:

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

3> set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to TRUE.

2> otherwise:

3> set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to FALSE.

1> if an unrecoverable error [16] in any of the AM RLC entities for the RB5 or upward is detected:

2> set the IE "AM_RLC error indication (RB>4)" to TRUE;

2> set the variable AM_RLC_ERROR_PENDING_RB5_AND_UP to TRUE.

1> otherwise:

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

3> set the IE "AM_RLC error indication (RB>4)" to TRUE.

2> otherwise:

3> set the IE "AM_RLC error indication (RB>4)" to FALSE.

1> set the IE "RB Timer indicator" to the value of the variable RB_TIMER_INDICATOR;

1> if the variable ESTABLISHMENT_CAUSE is initialised:

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

2> if the value of the variable ESTABLISHMENT_CAUSE is set to "Originating Conversational Call" or "Emergency Call" and a CS call is being initiated:

3> set the value of the IE "CS Call type" to "speech", "video" or "other" according to the call being initiated.

1> if the variable ORDERED_RECONFIGURATION is set to TRUE:

2> include the IE "Reconfiguration Status Indicator" and set it to TRUE.

1> if the IE "Cell update cause" is set to "radio link failure" or "RLC Unrecoverable error" and the UE has submitted a reconfiguration response message to RLC and the UE has not received the RLC acknowledgement for the response message:

2> include the IE "Reconfiguration Status Indicator" 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.

1> if the UE supports reporting of the IE "Security Revert Status Indicator":

2> if the UE has reverted back old security configuration by aborting ongoing security mode command as cell update procedure was initiated:

3> include the IE "Security Revert Status Indicator" and set it to "Reverted Back".

2> otherwise:

3> include the IE "Security Revert Status Indicator" and set it to "Normal Operation".

1> if the UE supports Two DRX schemes in URA_PCH and CELL_PCH

2> include the IE "Support for Two DRX schemes in URA_PCH and CELL_PCH" 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.

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

2> include the IE "Support of HS-DSCH DRX operation" and set it to TRUE.

1> if the UE supports SPS operation:

2> include the IE "Support of SPS operation" and set it to TRUE.

1> if the UE supports control channel DRX operation:

2> include the IE "Support of control channel DRX operation" and set it to TRUE.

1> if the UE performs cell update for MBMS ptp radio bearer request as specified in subclause 8.6.9.6; and

1> if one or more of the MBMS services for which the UE initiates the ptp radio bearer request concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates ptp radio bearer request:

3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority;

3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8.

1> otherwise, if the UE performs cell update for MBMS counting as specified in subclause 8.7.4; and

1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response:

3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority;

3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8.

1> if the UE included one or more "MBMS Selected Service ID" IEs:

2> include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29.

1> if, according to [4], the High-mobility state is applicable and it has been detected by the UE:

2> include the IE "UE Mobility State Indicator" and set it to the "High-MobilityDetected" value.

1> if an IE "Logged Measurement Info-FDD" or "Logged Measurement Info-TDD" in variable LOGGED_MEAS_REPORT_VARIABLE is present and registered PLMN is present in the IE "PLMN Identity List" stored in variable LOGGED_MEAS_REPORT_VARIABLE:

2> include IE "Logged Meas Available".

1> if an IE "Logged ANR Report Info" in variable LOG_ ANR_REPORT_VARIABLE is present and the registered PLMN is the same as one of the PLMNs in the IE "PLMN Identity" or IE "Equivalent PLMN Identity List" stored in variable LOG_ ANR_REPORT_VARIABLE:

2> include IE "ANR Logging Results Available".

The UE shall:

1> if the UE capability has changed compared to the value stored in the variable UE_CAPABILITY_TRANSFERRED and the variable RNC_CAPABILITY_CHANGE_SUPPORT is set to TRUE:

2> include the IE "Capability change indicator".

NOTE: Transmitting the IE "Capability change indicator" does not trigger any actual changed behaviour on the part of the UE. It serves only to inform the network that the UE is requesting an opportunity to send a UE CAPABILITY INFORMATION message.

If the UE needs to include the IE "Failure Cause" and the Cell Update message size exceeds the used transport format size, then the UE may omit the IE "Support for Two DRX schemes in URA_PCH and CELL_PCH" (i.e. omit the cellUpdate-r3-add-ext), the UE may omit IE "MBMS Selected Services" (i.e. omit the mbmsSelectedServices) and the UE may omit the Rel-10 non-critical extensions (i.e. omit the cellUpdate-va40ext).

If the UE does not need to include the IE "Failure Cause" and the Cell Update message size exceeds the used transport format size, then the UE may omit the IE "Support for Two DRX schemes in URA_PCH and CELL_PCH" (i.e. omit the cellUpdate-r3-add-ext), and the UE may omit IE "MBMS Selected Services" (i.e. omit the mbmsSelectedServices) to be able to include the Rel-10 non-critical extensions (i.e. include the cellUpdate-va40ext), or to be able to include IE "Measured results on RACH". The UE should first omit the IEs before applying the prioritization rules in section 8.5.23 to include the IE "Measured results on RACH".

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 subclause 8.3.1.2 that is valid when the URA UPDATE message is submitted to lower layers for transmission;

NOTE: During the time period starting from when a URA update procedure is initiated by the UE until when the procedure ends, additional URA UPDATE messages may be transmitted by the UE with different causes, depending on which causes are valid for the respective URA UPDATE message.

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

2 > include the IE "RRC transaction identifier"; and

3> set it to the value of "RRC transaction identifier" in the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

2> set the IE "Protocol error indicator" to TRUE;

2> include the IE "Protocol error information" set to the value of the variable PROTOCOL_ERROR_INFORMATION.

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

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

3> include the IE "RRC transaction identifier"; and

3> set it to the value of "RRC transaction identifier" in the entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS;

3> set the IE "Protocol error indicator" to TRUE;

3> include the IE "Protocol error information" set to "Information element value not comprehended".

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

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

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 HS-DSCH reception CELL_PCH and URA_PCH state:

2> include the IE "HS-PDSCH in CELL_PCH and URA_PCH" 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.

2> include IE "Logged Meas Available".

1> if IE "Logged ANR report" in variable LOG_ANR_REPORT_VARIABLE is present and registered PLMN is the same as one of the PLMNs in the IE "PLMN Identity" or IE "Equivalent PLMN Identity List" stored in variable LOG_ ANR_REPORT_VARIABLE:

2> include IE "ANR Logging Results Available".

8.3.1.4 T305 expiry and the UE detects "out of service area"

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

1> start timer T307;

1> act according to subclause 7.2.2.

8.3.1.4.1 Re-entering "in service area"

If the UE detects "in service area" according to subclause 8.5.5.2 and timer T307 or T317 is running, the UE shall:

1> check the value of V302; and

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

2> in case of a cell update procedure:

3> set the contents of the CELL UPDATE message according to subclause 8.3.1.3;

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

2> in case of a URA update procedure:

3> set the contents of the URA UPDATE message according to 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:

2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO;

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO;

2> in case of a cell update procedure:

3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

2> in case of a URA update procedure:

3> clear the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

2> release all its radio resources;

2> 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;

2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

2> clear the variable ESTABLISHED_RABS;

2> enter idle mode;

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

2> and the procedure ends.

8.3.1.4.2 Expiry of 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 subclause 8.5.2;

1> and the procedure ends.

8.3.1.5 Reception of an CELL UPDATE/URA UPDATE message by the UTRAN

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

1> in case the procedure was triggered by reception of a CELL UPDATE:

2> if SRNS relocation was performed:

3> transmit a CELL UPDATE CONFIRM message on the downlink DCCH.

2> otherwise:

3> update the START value for each CN domain as maintained in UTRAN (refer to subclause 8.5.9) with "START" in the IE "START list" for the CN domain as indicated by "CN domain identity" in the IE "START list";

3> transmit a CELL UPDATE CONFIRM message on the downlink DCCH or optionally on the CCCH but only if ciphering is not required; and

3> optionally set the IE "RLC re-establish indicator (RB2, RB3 and RB4)" and/or the IE "RLC re-establish indicator (RB5 and upwards)" to TRUE to request a RLC re-establishment in the UE, in which case the corresponding RLC entities should also be re-established in UTRAN; or

1> in case the procedure was triggered by reception of a URA UPDATE:

2> if SRNS relocation was performed:

3> transmit a URA UPDATE CONFIRM message on the downlink DCCH.

2> otherwise:

3> transmit a URA UPDATE CONFIRM message on the downlink CCCH or DCCH.

2> include the IE "URA identity" in the URA UPDATE CONFIRM message in a cell where multiple URA identifiers are broadcast; or

1> initiate an RRC connection release procedure (see subclause 8.1.4) by transmitting an RRC CONNECTION RELEASE message on the downlink CCCH. In particular UTRAN should:

2> if the CELL UPDATE message was sent because of an unrecoverable error in RB2, RB3 or RB4:

3> initiate an RRC connection release procedure (subclause 8.1.4) by transmitting an RRC CONNECTION RELEASE message on the downlink CCCH.

1> if the radio bearer is connected to a CS domain radio access bearer and the radio bearer uses UM RLC:

2> the UM RLC entity should be re-established in UTRAN.

UTRAN may transmit several CELL UPDATE CONFIRM/URA UPDATE CONFIRM messages to increase the probability of proper reception of the message by the UE. In such a case, the RRC SN for these repeated messages should be the same.

8.3.1.6 Reception of the CELL UPDATE CONFIRM/URA UPDATE CONFIRM message by the UE

When the UE receives a CELL UPDATE CONFIRM/URA UPDATE CONFIRM message; and

– 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

– if the message is received on DCCH:

the UE may:

1> maintain a list of the set of cells to which the UE has Radio Links if the IE "Cell ID" is present.

the UE shall:

1> stop timer T302;

1> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE;

1> in case of a cell update procedure and the CELL UPDATE CONFIRM message:

2> includes "RB information elements"; and/or

2> includes "Transport channel information elements"; and/or

2> includes "Physical channel information elements"; and

2> if the variable ORDERED_RECONFIGURATION is set to FALSE:

3> set the variable ORDERED_RECONFIGURATION to TRUE.

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

2> if the IE "Frequency info" is included in the message:

3> if the IE "RRC State Indicator" is set to the value "CELL_FACH":

4> select a suitable UTRA cell according to [4] on that frequency;

4> if the UE finds a suitable UTRA cell on that frequency:

5> if the received CELL UPDATE CONFIRM message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received CELL UPDATE CONFIRM message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):

6> act as specified in subclause 8.3.1.12.

5> else:

6> for 1.28Mcps TDD, decide the working frequency according to subclause 8.6.6.1.

4> else, if the UE can not find a suitable UTRA cell on the indicated frequency but it finds a suitable UTRA cell on another frequency:

5> act as specified in subclause 8.3.1.12.

3> if the IE "RRC State Indicator" is set to the value "CELL_PCH" or "URA_PCH":

4> select a suitable UTRA cell according to [4] on that frequency;

4> if the UE finds a suitable UTRA cell on that frequency:

5> if the received CELL UPDATE CONFIRM message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE in CELL_PCH state selects another cell than indicated by this IE or the received CELL UPDATE CONFIRM message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD); or

5> if the received CELL UPDATE CONFIRM message included the IE "URA identity", and the UE in URA_PCH state selects cell being part of another URA than indicated by this IE or the received CELL UPDATE CONFIRM message did not include the IE "URA identity":

6> act as specified in subclause 8.3.1.12.

4> else, if the UE can not find a suitable UTRA cell on the indicated frequency but it finds a suitable UTRA cell on another frequency:

5> act as specified in subclause 8.3.1.12.

3> if the IE "RRC State Indicator" is set to the value "CELL_DCH":

4> act on the IE "Frequency info" as specified in subclause 8.6.6.1.

2> if the IE "RRC State Indicator" is set to the value "CELL_PCH" or "URA_PCH":

3> if the IE "Wait time"<> 0 is included in the message and the UE supports timer T320:

4> start timer T320 with value set to the time stated in the IE "wait time".

2> use the transport channel(s) applicable for the physical channel types that is used; and

2> if the IE "TFS" is neither included nor previously stored in the UE for that transport channel(s):

3> use the TFS given in system information.

2> if none of the TFS stored is compatible with the physical channel:

3> delete the stored TFS;

3> use the TFS given in system information.

2> if the IE "RLC re-establish indicator (RB2, RB3 and RB4)" in the CELL UPDATE CONFIRM message is set to TRUE:

3> re-establish the RLC entities for signalling radio bearer RB2, signalling radio bearer RB3 and signalling radio bearer RB4 (if established);

3> clear all entries in the table "Processed transactions" in the variable TRANSACTIONS;

3> if the value of the IE "Status" in the variable CIPHERING_STATUS of the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN is set to "Started":

4> set the HFN component of the respective COUNT-C values for AM RLC entities with RB identity 2,RB identity 3 and RB identity 4 (if established) equal to the START value included in the latest transmitted CELL UPDATE message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN.

NOTE: UTRAN should not send a CELL UPDATE CONFIRM message with a target state CELL_PCH or URA_PCH, and including C-RNTI, and setting the IE "RLC re-establish indicator (RB2, RB3 and RB4)" to TRUE, otherwise the UE behaviour is not specified.

2> if the IE "RLC re-establish indicator (RB5 and upwards)" in the CELL UPDATE CONFIRM message is set to TRUE:

3> for radio bearers with RB identity 5 and upwards:

4> re-establish the AM RLC entities;

4> if the value of the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started":

5> set the HFN component of the respective COUNT-C values for AM RLC entities equal to the START value included in this CELL UPDATE message for the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS.

NOTE: UE actions, in case IE "Downlink counter synchronisation info" is included and either IE "RLC re-establish indicator (RB2, RB3 and RB4)" or IE "RLC re-establish indicator (RB5 and upwards)" are set to TRUE, are not defined.

1> if the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message contained the IE "Ciphering mode info" or contained the IE "Integrity protection mode info":

2> set the IE "Status" in the variable SECURITY_MODIFICATION for all the CN domains in the variable SECURITY_MODIFICATION to "Affected".

1> if the variable ESTABLISHMENT_CAUSE is set:

2> clear the variable ESTABLISHMENT_CAUSE.

1> enter a state according to subclause 8.6.3.3 applied on the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message.

If the UE after state transition enters CELL_DCH, CELL_FACH, CELL_PCH or URA_PCH state, the UE shall, after state transition:

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

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

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

1> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75;

1> for 1.28 Mcps TDD, determine the value for the MU_MIMO_STATUS variable and take the corresponding actions as described in subclause 8.5.61;

1> for 1.28 Mcps TDD, if the UE supports the non-rectangular resource allocation, the UE shall:

2> determine the value for the NON_RECTANGULAR_ALLOCATION STATUS variable and take the corresponding actions as described in subclause 8.5.82.

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

If the UE after state transition enters CELL_DCH state, it shall:

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

1> not prohibit periodical status transmission in RLC;

1> if the IE "Default DPCH Offset Value" is not included:

2> the UE behaviour is not specified.

If the UE after state transition remains in CELL_FACH state, it shall

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

1> start the timer T305 using its initial value if timer T305 is not running and periodical cell update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity";

1> if variable READY_FOR_COMMON_EDCH is set to TRUE:

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

1> else:

2> select PRACH according to subclause 8.5.17;

1> for 3.84 Mcps TDD and 7.68 Mcps TDD; or

1> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception in CELL_FACH state; or

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

1> for 1.28 Mcps TDD, if the IE "Common E-DCH system info" is not included in System Information Block type 5:

2> select Secondary CCPCH according to subclause 8.5.19;

2> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

1> else:

2> For FDD, 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

2> if the UE does not supports E-DCH transmission in CELL_FACH state and Idle mode or the IE "Common E-DCH system info" is not included system information block type 5 or 5bis; and

2> if variable H_RNTI and variable C_RNTI are set:

3> start to receive HS-DSCH according to the procedure in subclause 8.5.36.

2> else:

3> 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

3> if variable READY_FOR_COMMON_EDCH is set to TRUE; and

3> if variable H_RNTI and variable C_RNTI and variable E_RNTI are set:

4> start to receive HS-DSCH according to the procedure in subclause 8.5.36.

3> else:

4> clear variable C_RNTI and delete any stored C-RNTI value;

4> clear variable H_RNTI and delete any stored H-RNTI value;

4> clear variable E_RNTI and delete any stored E-RNTI value;

4> clear any stored IEs "HARQ info";

4> set the variable INVALID_CONFIGURATION to TRUE.

1> not prohibit periodical status transmission in RLC;

1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:

2> ignore that IE and stop using DRX.

If the UE after state transition enters URA_PCH or CELL_PCH state, it shall:

1> if the UE enters URA_PCH state:

2> if the UE supports HS-DSCH reception in CELL_PCH and URA_PCH state and the IE "HS-DSCH paging system information" is included in System Information Block type 5 or System Information Block type 5bis:

3> clear any stored IE "HARQ Info";

3> reset the MAC-ehs entity [15];

3> reset the MAC-i/is entity [15].

1> if the UE enters CELL_PCH state:

2> if the UE supports E-DCH transmission in CELL_FACH state and Idle mode and the IE "Common E-DCH system info" is included in system information block type 5 or 5bis:

3> if variable H_RNTI or variable C_RNTI or variable E_RNTI is not set:

4> clear variable C_RNTI and delete any stored C-RNTI value;

4> clear variable H_RNTI and delete any stored H-RNTI value;

4> clear variable E_RNTI and delete any stored E-RNTI value;

4> clear any stored IE "HARQ Info";

4> reset the MAC-ehs entity [15];

4> reset the MAC-i/is entity [15].

1> prohibit periodical status transmission in RLC;

1> for 3.84 Mcps TDD and 7.68 Mcps TDD; or

1> for FDD and 1.28 Mcps TDD, if the variable HSPA_RNTI_STORED_PCH is set to FALSE and the variable READY_FOR_COMMON_EDCH is set to FALSE:

2> clear the variable C_RNTI;

2> stop using that C_RNTI just cleared from the variable C_RNTI in MAC.

1> start the timer T305 using its initial value if timer T305 is not running and periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity";

1> for 3.84 Mcps TDD and 7.68 Mcps TDD; or

1> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception in CELL_PCH and URA_PCH state; or

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

2> select Secondary CCPCH according to subclause 8.5.19;

2> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

1> else:

2> if the UE is in CELL_PCH:

3> if IE "New C-RNTI" is not included:

4> clear the variable C_RNTI;

4> clear the variable H_RNTI;

4> clear any stored IEs "HARQ info";

4> determine the value for the READY_FOR_COMMON_EDCH variable and take the corresponding actions as described in subclause 8.5.47;

4> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75.

2> if the UE enters CELL_PCH state and the variable HSPA_RNTI_STORED_PCH is set to TRUE:

3> select Secondary CCPCH according to subclause 8.5.19;

3> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

2> else:

3> for FDD; or

3> for 1.28 Mcps TDD, if both variable H_RNTI and variable C_RNTI are set:

4> monitor its paging occasions on the selected PICH determined according to subclauses 8.6.3.1a, 8.6.3.2 and 8.5.39 and receive PCCH on the HS-DSCH mapped on the HS-PDSCH, or DCCH and DTCH mapped on the HS-PDSCH and the associated HS-SCCH selected by the UE according to the procedures in subclause 8.5.40 for FDD and 8.5.40a for 1.28 Mcps TDD.

1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:

2> use the values in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging Occasion and PICH Monitoring Occasion as specified in subclause 8.6.3.2.

NOTE: In the case of a cell update procedure during an ongoing reconfiguration procedure moving the UE into CELL_PCH/URA_PCH then the value of the IE "UTRAN DRX Cycle length coefficient" sent in the CELL UPDATE CONFIRM message should be the same as the value sent in the reconfiguration message.

1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:

2> set the variable INVALID_CONFIGURATION to TRUE.

If the UE after the state transition remains in CELL_FACH state; and

1> the contents of the variable C_RNTI are empty:

it shall check the value of V302; and:

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

2> if, caused by the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message:

3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or

3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE:

4> abort the ongoing integrity and/or ciphering reconfiguration;

4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Ciphering mode info":

5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and

5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.

4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Integrity protection mode info":

5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and

5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

2> in case of a URA update procedure:

3> stop the URA update procedure;

3> clear any entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and

3> continue with a cell update procedure.

2> set the contents of the CELL UPDATE message according to subclause 8.3.1.3, except for the IE "Cell update cause" which shall be set to "cell reselection";

2> submit the CELL 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> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO;

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO;

2> in case of a cell update procedure:

3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

2> in case of a URA update procedure:

3> clear the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

2> release all its radio resources;

2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

2> clear the variable ESTABLISHED_RABS;

2> enter idle mode;

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

2> and the procedure ends.

If the UE after the state transition remains in CELL_FACH state; and

– a C-RNTI is stored in the variable C_RNTI;

– the UE after the state transition moves to another state than the CELL_FACH state:

the UE shall:

1> in case cell reselection interrupted an ongoing cell update procedure and a CELL UPDATE CONFIRM/URA UPDATE CONFIRM was received with the IE "Downlink counter synchronisation info" present and the response to which was not submitted to the lower layers due to the cell re-selection:

2> include the IE "START list" in the response message transmitted according to subclause 8.3.1.7;

2> if the CELL UPDATE CONFIRM/URA UPDATE CONFIRM, the response to which was not delivered to the lower layers, due to the cell re-selection, included the IE "RB with PDCP information list":

3> include the IE "RB with PDCP information list" in the response message transmitted according to subclause 8.3.1.7.

1> in case of a cell update procedure:

2> set the IE "RRC transaction identifier" in any response message transmitted below to the value of "RRC transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and

2> clear that entry.

1> in case of a URA update procedure:

2> set the IE "RRC transaction identifier" in any response message transmitted below to the value of "RRC transaction identifier" in the entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and

2> clear that entry;

1> if the variable PDCP_SN_INFO is non-empty:

2> include the IE "RB with PDCP information list" in any response message transmitted below and set it to the value of the variable PDCP_SN_INFO.

1> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message included the IE "Downlink counter synchronisation info":

2> if the variable PDCP_SN_INFO is empty:

3> configure the corresponding RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "stop".

2> else:

3> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "stop";

3> configure the RLC entity for UM and AM radio bearers for which the IE "PDCP SN Info" is not included to "stop".

2> re-establish the RLC entity for RB2;

2> clear all entries in the table "Processed transactions" in the variable TRANSACTIONS;

2> for the downlink and the uplink, apply the ciphering configuration as follows:

3> if the received re-configuration message included the IE "Ciphering Mode Info":

4> use the ciphering configuration in the received message when transmitting the response message.

3> if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because the activation times not having been reached:

4> if the previous SECURITY MODE COMMAND was received due to new keys being received:

5> consider the new ciphering configuration to include the received new keys;

5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 as indicated in subclause 8.1.12.3.1.

4> else if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the previous SECURITY MODE COMMAND caused a change in LATEST_CONFIGURED_CN_DOMAIN:

5> consider the new ciphering configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN;

5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 to the most recently transmitted IE "START list" or IE "START" for the LATEST_CONFIGURED_CN_DOMAIN at the reception of the previous SECURITY MODE COMMAND.

4> apply the new ciphering configuration immediately following RLC re-establishment.

3> else:

4> continue using the current ciphering configuration.

2> set the new uplink and downlink HFN component of the COUNT-C of RB2 to MAX(uplink HFN component of the COUNT-C of RB2, downlink HFN component of the COUNT-C of RB2);

2> increment by one the downlink and uplink values of the HFN component of the COUNT-C for RB2;

2> calculate the START value according to subclause 8.5.9;

2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in any response message transmitted below;

2> for any measurement of type CSG Proximity detection or any measurement associated with CELL_INFO_CSG_LIST (i.e. CSG Proximity detection, CSG intra-frequency measurement, CSG inter-frequency measurement and/or SI acquisition):

3> stop all measurements of type CSG Proximity detection and all measurements associated with CELL_INFO_CSG_LIST (i.e. CSG Proximity detection, CSG intra-frequency measurement, CSG inter-frequency measurement and/or SI acquisition);

3> delete measurement control information for all measurements of type CSG Proximity detection and all measurements associated with CELL_INFO_CSG_LIST (i.e. CSG Proximity detection, CSG intra-frequency measurement, CSG inter-frequency measurement and/or SI acquisition);

3> clear the variable CELL_INFO_CSG_LIST.

2> if timer T323 value is stored in the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS:

3> stop and reset timer T323;

3> clear any value of the timer T323 stored in the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS.

1> else if the radio bearer is connected to a CS domain radio access bearer and the radio bearer uses UM RLC:

2> re-establish the UM RLC entity;

2> if the value of the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started":

3> set the HFN component of the respective COUNT-C values for the UM RLC entity equal to the START value included in this CELL UPDATE message for the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS;

3> set the remaining bits of the HFN component of the COUNT-C values of the UM RLC entity to zero.

1> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message did not include the IE "Downlink counter synchronisation info":

2> if the variable START_VALUE_TO_TRANSMIT is set:

3> include the value of the variable START_VALUE_TO_TRANSMIT in the IE "START" in the response message transmitted below.

1> if the variable DEFERRED_MEASUREMENT_STATUS is set to TRUE:

2> if System Information Block type 11 is scheduled on the BCCH and the UE has not read nor stored the IEs present in this System Information Block; or

2> if System Information Block type 11bis is scheduled on the BCCH and the UE has not read nor stored the IEs present in this System Information Block; or

2> if System Information Block type 11ter is scheduled on the BCCH and the UE has not read nor stored the IEs present in this System Information Block, or

2> if System Information Block type 12 is scheduled on the BCCH and the UE has not read nor stored the IEs present in this System Information Block:

3> include the IE "Deferred measurement control reading" in any response message transmitted.

1> transmit a response message as specified in subclause 8.3.1.7;

1> if the IE "Integrity protection mode info" was present in the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message:

2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted response message.

1> if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure:

2> set the variable ORDERED_RECONFIGURATION to FALSE.

1> clear the variable PDCP_SN_INFO;

1> when the response message transmitted per subclause 8.3.1.7 to the UTRAN has been confirmed by RLC:

2> if the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message contained the IE "Ciphering mode info":

3> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM;

3> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and

3> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.

2> if the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message contained the IE "Integrity protection mode info":

3> set "Uplink RRC Message sequence number" for signalling radio bearer RB0 in the variable INTEGRITY_PROTECTION_INFO to a value such that next RRC message to be sent on uplink RB0 will use the new integrity protection configuration;

3> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN;

3> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE.

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

1> in case of a cell update procedure:

2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

1> in case of a URA update procedure:

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

1> set the variable CELL_UPDATE_STARTED to FALSE;

1> if the variable AM_RLC_ERROR_PENDING_RB234 is set to TRUE:

2> set the variable AM_RLC_ERROR_PENDING_RB234 to FALSE.

1> if the variable AM_RLC_ERROR_PENDING_RB5_AND_UP is set to TRUE:

2> set the variable AM_RLC_ERROR_PENDING_RB5_AND_UP to FALSE.

1> clear the variable SECURITY_MODIFICATION.

1> stop timers T314 and/or T315 if they are running.

The procedure ends.

8.3.1.7 Transmission of a response message to UTRAN

If CELL UPDATE CONFIRM message:

– includes the IE "RAB information to setup":

the UE shall:

1> transmit a RADIO BEARER SETUP COMPLETE as response message using AM RLC.

If the CELL UPDATE CONFIRM message:

– does not include the IE "RAB information for setup"; and

– includes the IE "RB information to release list":

the UE shall:

1> transmit a RADIO BEARER RELEASE COMPLETE as response message using AM RLC.

If the CELL UPDATE CONFIRM message:

– does not include the IE "RAB information for setup", nor the IE "RB information to release list"; and

– includes the IE "RB information to reconfigure list"; or

– includes the IE "RB information to be affected list":

the UE shall:

1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message using AM RLC.

If the CELL UPDATE CONFIRM message:

– includes the IE "Other state configuration info":

the UE shall:

1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message using AM RLC.

If the CELL UPDATE CONFIRM message:

– does not include the IE "RAB information for setup", the IE "RB information to release list", the IE "RB information to reconfigure list", nor the IE "RB information to be affected list"; and

– includes "Transport channel information elements":

the UE shall:

1> transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE as response message using AM RLC.

If the CELL UPDATE CONFIRM message:

– does not include the IE "RAB information for setup", the IE "RB information to release list", the IE "RB information to reconfigure list", nor the IE "RB information to be affected list"; and

– does not include "Transport channel information elements"; and

– includes "Physical channel information elements":

the UE shall:

1> transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message using AM RLC.

If the CELL UPDATE CONFIRM message:

– does not include the IE "RAB information for setup", the IE "RB information to release list", the IE "RB information to reconfigure list", nor the IE "RB information to be affected list"; and

– does not include "Transport channel information elements"; and

– does not include "Physical channel information elements"; and

– includes "CN information elements"; or

– includes the IE "Ciphering mode info"; or

– includes the IE "Integrity protection mode info"; or

– includes the IE "New C-RNTI"; or

– includes the IE "New U-RNTI"; or

– includes the IE "Downlink counter synchronisation info" and the IE "New U-RNTI":

NOTE: In the case of a cell update procedure during an ongoing reconfiguration procedure moving the UE into CELL_PCH/URA_PCH the CELL UPDATE CONFIRM message should include the IE "New C-RNTI".

the UE shall:

1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.

If the CELL UPDATE CONFIRM message:

– does not include "RAB information to setup": and

– does not include "RB information elements"; and

– does not include "Transport channel information elements"; and

– does not include "Physical channel information elements"; and

– 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 C-RNTI"; and

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

the UE shall:

1> transmit no response message.

If the URA UPDATE CONFIRM message:

– includes "CN information elements"; or

– includes the IE "Ciphering mode info"; or

– includes the IE "Integrity protection mode info"; or

– includes any one or both of the IEs "New C-RNTI" and "New U-RNTI"; or

– includes the IE "Downlink counter synchronisation info" and the IE "New U-RNTI":

the UE shall:

1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.

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 the new state is CELL_DCH state, the UE shall, after the state transition:

1> if the IE "Deferred measurement control reading" was included in the response message:

2> clear the variable CELL_INFO_LIST.

If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition., and the UE shall:

1> if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message:

2> when RLC has confirmed the successful transmission of the response message:

3> if the variable PDCP_SN_INFO is empty:

4> configure the RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "continue".

3> else:

4> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "continue";

4> configure the RLC entity for UM and AM radio bearers for which the IE " PDCP SN Info" is not included to "continue".

3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;

3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;

3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;

3> if the IE "PDCP context relocation info" is not present:

> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36].

3> if the IE "PDCP context relocation info" is present:

4> perform the actions as specified in subclause 8.6.4.13.

1> if the variable PDCP_SN_INFO is empty:

2> if the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Ciphering mode info":

3> when RLC has confirmed the successful transmission of the response message:

4> continue with the remainder of the procedure.

2> if the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message did not contain the IE "Ciphering mode info":

3> when RLC has been requested to transmit the response message,

4> continue with the remainder of the procedure.

1> if the variable PDCP_SN_INFO is non-empty:

2> when RLC has confirmed the successful transmission of the response message:

3> for each radio bearer in the variable PDCP_SN_INFO:

4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":

5> configure the RLC entity for that radio bearer to "continue".

3> continue with the remainder of the procedure.

If the new state is CELL_PCH or URA_PCH, the response message shall be transmitted in CELL_FACH state, and the UE shall:

1> when RLC has confirmed the successful transmission of the response message:

2> if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message:

3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;

3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36].

2> for each radio bearer in the variable PDCP_SN_INFO:

3> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":

4> configure the RLC entity for that radio bearer to "continue".

2> enter the new state (CELL_PCH or URA_PCH, respectively).

1> continue with the remainder of the procedure.

8.3.1.7a Physical channel failure

If the received CELL UPDATE CONFIRM message would cause the UE to transit to CELL_DCH state:

1> if the UE failed to establish the physical channel(s) indicated in the received CELL UPDATE CONFIRM message according to the criteria defined in subclause 8.5.4 are not fulfilled;

1> for FDD and 3.84/7.68 Mcps TDD, if the received CELL UPDATE CONFIRM message does not contain dedicated physical channels; or

1> for 1.28 Mcps TDD, if the received CELL UPDATE CONFIRM message does not contain dedicated physical channels nor physical shared channels as defined in clause 8.5.4; or

1> for 3.84 Mcps TDD or 7.68 Mcps TDD, if the received CELL UPDATE CONFIRM does not contain physical channels to which DCCH(s) are mapped:

the UE shall:

1> if, caused by the received CELL UPDATE CONFIRM message

2> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or

2> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE:

3> abort the ongoing integrity and/or ciphering reconfiguration;

3> if the received CELL UPDATE CONFIRM message contained the IE "Ciphering mode info":

4> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and

4> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.

3> if the received CELL UPDATE CONFIRM message contained the IE "Integrity protection mode info":

4> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and

4> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

1> if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message:

2> set the IE "failure cause" to "physical channel failure";

2> set the variable ORDERED_RECONFIGURATION to FALSE.

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

2> select a suitable UTRA cell according to [4];

2> set the contents of the CELL UPDATE message according to subclause 8.3.1.3, except for the IE "Cell update cause" which shall be set to "Radio link failure";

2> submit the CELL 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> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO;

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO;

2> in case of a cell update procedure:

3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS.

2> release all its radio resources;

2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

2> clear the variable ESTABLISHED_RABS;

2> set the variable CELL_UPDATE_STARTED to FALSE;

2> enter idle mode.

8.3.1.8 Unsupported configuration by the UE

If the UE does not support the configuration in the CELL UPDATE CONFIRM message and/or the variable UNSUPPORTED_CONFIGURATION is set to TRUE, the UE shall:

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

2> if, caused by the received CELL UPDATE CONFIRM message

3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or

3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE:

4> abort the ongoing integrity and/or ciphering reconfiguration;

4> if the received CELL UPDATE CONFIRM message contained the IE "Ciphering mode info":

5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and

5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.

4> if the received CELL UPDATE CONFIRM message contained the IE "Integrity protection mode info":

5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and

5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

2> if the variable ORDERED_RECONFIGURATION is set to TRUE due to the received CELL UPDATE CONFIRM message in case of a cell update procedure:

3> set the variable ORDERED_RECONFIGURATION to FALSE.

2> set the variable FAILURE_INDICATOR to TRUE;

2> set the variable FAILURE_CAUSE to "Unsupported configuration";

2> set the content of the CELL UPDATE message according to subclause 8.3.1.3;

2> submit the CELL 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> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO;

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO;

2> clear the variable PDCP_SN_INFO;

2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS;

2> release all its radio resources;

2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

2> clear the variable ESTABLISHED_RABS;

2> set the variable CELL_UPDATE_STARTED to FALSE;

2> enter idle mode;

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

2> and the procedure ends.

8.3.1.9 Invalid configuration

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

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

2> if, caused by the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message

3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or

3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE:

4> abort the ongoing integrity and/or ciphering reconfiguration;

4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Ciphering mode info":

5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and

5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.

4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Integrity protection mode info";

5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and

5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

2> if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure:

3> set the variable ORDERED_RECONFIGURATION to FALSE.

2> in case of a cell update procedure:

3> set the variable FAILURE_INDICATOR to TRUE;

3> set the variable FAILURE_CAUSE to "Invalid configuration";

3> set the contents of the CELL UPDATE message according to subclause 8.3.1.3;

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

2> in case of a URA update procedure:

3> set the contents of the URA UPDATE message according to 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:

2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO;

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO;

2> clear the variable PDCP_SN_INFO;

2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS;

2> release all its radio resources;

2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

2> clear the variable ESTABLISHED_RABS;

2> set the variable CELL_UPDATE_STARTED to FALSE;

2> enter idle mode;

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

2> the procedure ends.

8.3.1.9a Incompatible simultaneous reconfiguration

In case of a cell update procedure and if the received CELL UPDATE CONFIRM message

– includes the IE "RB information to release list", and/or the IE "RB information to reconfigure list", and/or the IE "RB information to be affected list", and/or

– includes "Transport channel information elements"; and/or

– includes "Physical channel information elements"; and

– the variable ORDERED_RECONFIGURATION is set to TRUE because of an ongoing Reconfiguration procedure;

If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION is set to TRUE due to the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message: