8.2.2 Reconfiguration procedures

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

Figure 8.2.2-1: Radio Bearer Establishment, normal case

Figure 8.2.2-2: Radio Bearer Establishment, failure case

Figure 8.2.2-3: Radio bearer reconfiguration, normal flow

Figure 8.2.2-4: Radio bearer reconfiguration, failure case

Figure 8.2.2-5: Radio Bearer Release, normal case

Figure 8.2.2-6: Radio Bearer Release, failure case

Figure 8.2.2-7: Transport channel reconfiguration, normal flow

Figure 8.2.2-8: Transport channel reconfiguration, failure case

Figure 8.2.2-9: Physical channel reconfiguration, normal flow

Figure 8.2.2-10: Physical channel reconfiguration, failure case

8.2.2.1 General

Reconfiguration procedures include the following procedures:

– the radio bearer establishment procedure;

– radio bearer reconfiguration procedure;

– the radio bearer release procedure;

– the transport channel reconfiguration procedure; and

– the physical channel reconfiguration procedure.

The radio bearer establishment procedure is used to establish new radio bearer(s).

The radio bearer reconfiguration procedure is used to reconfigure parameters for a radio bearer, to establish new radio bearer(s) or to release radio bearer(s).

The radio bearer release procedure is used to release radio bearer(s).

The transport channel reconfiguration procedure is used to reconfigure transport channel parameters.

The physical channel reconfiguration procedure is used to establish, reconfigure and release physical channels.

While performing any of the above procedures, these procedures may perform a hard handover (subclause 8.3.5) and/or an HS-DSCH cell change and/or a serving E-DCH cell change. The reconfiguration procedures are also used to change the feedback configuration for HS-DSCH.

8.2.2.2 Initiation

To initiate any one of the reconfiguration procedures, UTRAN should:

1> configure new radio links in any new physical channel configuration;

1> start transmission and reception on the new radio links;

1> for a radio bearer establishment procedure:

2> transmit a RADIO BEARER SETUP or a RADIO BEARER RECONFIGURATION message on the downlink DCCH using AM or UM RLC;

2> if signalling radio bearer RB4 is setup with this procedure and signalling radio bearers RB1-RB3 were already established prior to the procedure:

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

4> connect any radio bearers setup by the same message as signalling radio bearer RB4 to the CN domain indicated in the variable "LATEST CONFIGURED CN DOMAIN".

1> for a radio bearer reconfiguration procedure:

2> transmit a RADIO BEARER RECONFIGURATION message on the downlink DCCH using AM or UM RLC.

1> for a radio bearer release procedure:

2> transmit a RADIO BEARER RELEASE or a RADIO BEARER RECONFIGURATION message on the downlink DCCH using AM or UM RLC.

1> for a transport channel reconfiguration procedure:

2> transmit a TRANSPORT CHANNEL RECONFIGURATION message on the downlink DCCH using AM or UM RLC.

1> for a physical channel reconfiguration procedure:

2> transmit a PHYSICAL CHANNEL RECONFIGURATION message on the downlink DCCH using AM or UM RLC.

1> if the reconfiguration procedure is simultaneous with SRNS relocation procedure:

2> if the transmitted message is a RADIO BEARER RECONFIGURATION:

3> include the IE "New U-RNTI".

2> else:

3> include the IE "Downlink counter synchronisation info".

2> if ciphering and/or integrity protection are activated:

3> include new ciphering and/or integrity protection configuration information to be used after reconfiguration.

2> use the downlink DCCH using AM RLC.

1> if transport channels are added, reconfigured or deleted in uplink and/or downlink:

2> set TFCS according to the new transport channel(s).

1> if transport channels are added or deleted in uplink and/or downlink, and RB Mapping Info applicable to the new configuration has not been previously provided to the UE, the UTRAN should:

2> send the RB Mapping Info for the new configuration.

1> if the UE supports the UM RLC re-establishment via reconfiguration; and

1> if one or more UM RLC radio bearers are re-established:

2> transmit a reconfiguration message on the downlink DCCH using AM or UM RLC;

2> include the IE "UM RLC re-establishment RB List" and include the Radio Bearer ID encountered the error in the list.

In the Radio Bearer Reconfiguration procedure UTRAN may indicate that uplink transmission shall be stopped or continued on certain radio bearers. Uplink transmission on a signalling radio bearer used by the RRC signalling (signalling radio bearer RB1 or signalling radio bearer RB2) should not be stopped.

NOTE 1: The Release ’99 RADIO BEARER RECONFIGURATION message always includes the IE "RB information to reconfigure", even if UTRAN does not require the reconfiguration of any RB. In these cases, UTRAN may include only the IE "RB identity" within the IE "RB information to reconfigure".

NOTE 2: The Release ’99 RADIO BEARER RECONFIGURATION message always includes the IE "Downlink information per radio link list", even if UTRAN does not require the reconfiguration of any RL. In these cases, UTRAN may re-send the currently assigned values for the mandatory IEs included within the IE "Downlink information per radio link list ".

NOTE 3: The Release ’99 RADIO BEARER RECONFIGURATION message always includes the IE "Primary CPICH Info" (FDD) or IE "Primary CCPCH Info" (TDD) within IE "Downlink information per radio link list". This implies that in case UTRAN applies the RADIO BEARER RECONFIGURATION message to move the UE to CELL_FACH state, it has to indicate a cell. However, UTRAN may indicate any cell; the UE anyhow performs cell selection and notifies UTRAN if it selects another cell than indicated by UTRAN.

NOTE 4: If any combination of setup, reconfiguration and release of the same radio bearer is included in the same RADIO BEARER RECONFIGURATION message, the UE behavior is unspecified.

If the IE "Activation Time" is included, UTRAN should set it to a value taking the UE performance requirements into account.

UTRAN should take the UE capabilities into account when setting the new configuration.

If the message is used to initiate a transition from CELL_DCH to CELL_FACH state, the UTRAN may assign a C-RNTI to be used in that cell by the UE. In FDD and 1.28 Mcps TDD, if a C-RNTI is assigned, then UTRAN may additionally assign an H-RNTI and an E-RNTI to be used in that cell by the UE.

For FDD and 1.28 Mcps TDD, if the message is used to initiate a transition to CELL_PCH state, the UTRAN may assign a C-RNTI, an H-RNTI and an E-RNTI to be used in that cell by the UE.

For FDD, if the message is used to initiate a transition to URA_PCH state, the UTRAN may assign a C-RNTI, an H-RNTI and an E-RNTI to be used by the UE.

8.2.2.2a Initiation of handover from GERAN Iu mode

To initiate the handover from GERAN Iu mode, UTRAN should:

1> provide a RADIO BEARER RECONFIGURATION message to be encapsulated in INTERSYSTEM HANDOVER TO UTRAN COMMAND message, sent on the downlink SRB2 in GERAN Iu mode;

1> in case UTRAN decides to use a predefined or default radio configuration that is stored in the UE, it should include the following information in the RADIO BEARER RECONFIGURATION message:

– PhyCH information elements; and

– either:

– the IE "Predefined configuration identity", to indicate which pre-defined configuration of RB, transport channel and physical channel parameters shall be used; or

– the IE "Default configuration mode" and IE "Default configuration identity", to indicate which default configuration of RB, transport channel and physical channel parameters shall be used.

8.2.2.3 Reception of RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE or TRANSPORT CHANNEL RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message, TTI switch HS-SCCH order or Target cell HS-SCCH order by the UE

The UE shall:

1> be able to receive any of the following messages:

2> RADIO BEARER SETUP message; or

2> RADIO BEARER RECONFIGURATION message; or

2> RADIO BEARER RELEASE message; or

2> TRANSPORT CHANNEL RECONFIGURATION message; or

2> PHYSICAL CHANNEL RECONFIGURATION message;

1> be able to perform a hard handover and apply physical layer synchronisation procedure A as specified in [29], even if no prior UE measurements have been performed on the target cell and/or frequency.

For FDD: in case a measurement report was triggered by intra frequency event 1d and if the table "Target cell preconfigurations" in the variable TARGET_CELL_PRECONFIGURATION includes the cell that triggered the event, or in case a measurement report was triggered by intra frequency event 1c requesting the serving HS-DSCH cell change and if the table "Target cell preconfigurations" in the variable TARGET_CELL_PRECONFIGURATION includes the target cell, as per the definition of Target cell HS-SCCH order

the UE shall be able to receive:

1> Target cell HS-SCCH order.

For FDD: in case a filtered UPH report [15] was triggered the UE shall be able to receive:

1> TTI switch HS-SCCH order.

In case the reconfiguration procedure is used to remove all existing RL(s) in the active set while new RL(s) are established the UE shall:

1> For FDD:

2> if the UE has a pending "TGPS reconfiguration CFN" at the activation time received in the reconfiguration message and the reconfiguration requests a timing re-initialised hard handover (see subclause 8.3.5.1), the UE may:

3> abort the pending CM activation;

3> set the CM_PATTERN_ACTIVATION_ABORTED to TRUE.

2> otherwise:

3> set the CM_PATTERN_ACTIVATION_ABORTED to FALSE.

If the UE will enter a target RRC state as defined in the OTHER_STATE_CONFIGURATION variable after successful transmission of the SIGNALLING CONNECTION RELEASE INDICATION message; or

If the UE receives:

– a RADIO BEARER SETUP message; or

– a RADIO BEARER RECONFIGURATION message; or

– a RADIO BEARER RELEASE message; or

– a TRANSPORT CHANNEL RECONFIGURATION message; or

– a PHYSICAL CHANNEL RECONFIGURATION message; or

– a TTI switch HS-SCCH order; or

– a Target cell HS-SCCH order

it shall:

1> stop and reset timer T324 if running;

1> stop monitoring target cell HS-SCCH;

1> set the variable ORDERED_RECONFIGURATION to TRUE;

1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:

2> if COMMON_E_DCH_TRANSMISSION is set to FALSE before entering CELL_DCH state or IE "E-DCH info" is not included in the reconfiguration message:

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

1> if the UE has received a Target cell HS-SCCH order:

2> if the IE "Serving Cell Change MAC reset" in the target cell preconfiguration is set to TRUE:

3> reset the MAC-hs/ehs entity [15].

2> else:

3> determine the value for the "TPC combination index" for current cell and the cell in which the Target cell HS-SCCH order is received;

3> if the values of the IE "TPC combination index" for current cell and the cell in which the Target cell HS-SCCH order is received are different:

4> reset the MAC-hs/ehs entity [15].

1> act upon all received information elements, or Target cell preconfiguration information in the case of received Target cell HS-SCCH order, as specified in subclause 8.6, unless specified in the following and perform the actions below;

1> in the case of received TTI switch HS-SCCH order, perform the actions as described in 8.5.86.

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 may first release the physical channel configuration used at reception of the reconfiguration message. The UE shall then:

1> enter a state according to subclause 8.6.3.3.

In case the UE receives a RADIO BEARER RECONFIGURATION message including the IE "RB information to reconfigure" that only includes the IE "RB identity", the UE shall:

1> handle the message as if IE "RB information to reconfigure" was absent.

NOTE: The ASN.1 "r3" version of the RADIO BEARER RECONFIGURATION message always includes the IE "RB information to reconfigure". UTRAN has to include it even if it does not require the reconfiguration of any RB.

In case the UE receives a RADIO BEARER RECONFIGURATION message with the IE "Specification mode" set to "Preconfiguration" while the message is not sent through GERAN Iu mode, the UE behaviour is unspecified.

In case the UE receives a RADIO BEARER SETUP message with the IE "Specification mode" not set to "Complete Specification", the UE behaviour is unspecified.

The UE shall:

1> if IE "Default configuration for CELL_FACH" is set:

2> if the message is RADIO BEARER RECONFIGURATION:

3> if IE "new U-RNTI" is included:

4> act in accordance with the default parameters according to section 13.8.

3> else:

4> the UE behaviour is unspecified.

For FDD: in CELL_DCH state, in case the UE receives a Target cell HS-SCCH order the UE shall:

1> ignore RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, TRANSPORT CHANNEL RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION messages as described in subclause 8.6.3.11.

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

1> in FDD; or

1> in TDD when "Primary CCPCH Info" is included indicating a new target cell and "New C-RNTI" is not specified:

2> remove any C-RNTI from MAC;

2> clear the variable C_RNTI.

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> if the IE "E-DCH info" was not included in the message:

2> for FDD:

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

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

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> for 1.28 Mcps TDD:

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

3> stop any E-RUCCH and E-PUCH transmission procedure;

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.

If after state transition the UE leaves CELL_DCH state, the UE shall, before state transition:

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

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

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

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

If after state transition the UE leaves CELL_DCH state, the UE shall, after the state transition:

1> if any IEs related to HS-DSCH are 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.

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> if the IE "UE Mobility State Indicator" was present in the reconfiguration message:

2> consider the High-mobility state to have being detected.

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> for FDD, if the IE "Uplink CLTD info FDD" is stored in the UE:

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

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

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

1> for FDD, clear the IE "Radio Links without DPCH/F-DPCH info", if stored;

1> for FDD, if the IE "DPCCH2 info FDD" is stored in the UE:

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

For 1.28 Mcps TDD, if the UE supports the non-rectangular resource allocation, the UE shall:

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

If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall:

1> if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration;

1> for FDD:

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

2> determine the value for the SECONDARY_CELL_E_DCH_TRANSMISSION and take the corresponding actions as described in subclause 8.5.58;

2> if the variable SECONDARY_CELL_E_DCH_TRANSMISSION is set to TRUE:

3> if the IE "Secondary E-DCH info common" is included and the IE "Frequency info" is different from the stored "Frequency info" in the IE "Secondary E-DCH info common"; or

3> if the IE "Frequency info" is included in an IE other than the IE "Uplink secondary cell info FDD":

4> consider the secondary uplink frequency as not activated and take the corresponding actions as described in subclause 8.5.58.

3> else:

4> if the IE "Downlink information per radio link list on secondary UL frequency" is not included in the received message:

5> keep the current activation status of the secondary uplink frequency and take the corresponding actions as described in subclause 8.5.58.

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

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

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

1> in TDD:

2> if "Primary CCPCH Info" is included indicating a new target cell and "New C-RNTI" is not specified:

3> remove any C-RNTI from MAC;

3> clear the variable C_RNTI.

2> if "Primary CCPCH Info" is included indicating a new target cell and "New H-RNTI" is not specified:

3> remove any H-RNTI from MAC;

3> clear the variable H_RNTI;

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

2> if the reconfiguration message caused a change from FDD mode to 3.84/7.68 Mcps TDD mode and provides for E-DCH/HS-DSCH operation without an uplink DPCH:

3> the UE shall obtain timing advance for the 3.84/7.68 Mcps TDD cell according to [15].

1> if "DPCH frame offset" is included for one or more RLs in the active set, and the reconfiguration procedure does not request a timing reinitialized hard handover (see subclause 8.3.5.1):

2> use its value to determine the beginning of the DPCH or F-DPCH frame in accordance with the following:

3> if the received IE "DPCH frame offset" is across the value range border compared to the DPCH or F-DPCH frame offset currently used by the UE:

4> consider it to be a request to adjust the timing with 256 chips across the frame border (e.g. if the UE receives value 0 while the value currently used is 38144 consider this as a request to adjust the timing with +256 chips).

3> if after taking into account value range borders, the received IE "DPCH frame offset" corresponds to a request to adjust the timing with a step exceeding 256 chips:

4> set the variable INVALID_CONFIGURATION to TRUE.

3> and the procedure ends.

2> adjust the radio link timing accordingly.

If after state transition the UE enters CELL_FACH state, the UE shall, after the state transition:

1> if the UE was in CELL_DCH state upon reception of the reconfiguration message:

2> clear the variable E_RNTI.

1> if the IE "new Primary E-RNTI" is included in the received reconfiguration message:

2> store the "new Primary E-RNTI" according to subclause 8.6.3.14.

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> 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> if the IE "Frequency info" is included in the received reconfiguration message:

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

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

3> if the received reconfiguration 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 reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

4> when the cell update procedure completed successfully:

5> if the UE is in CELL_PCH or URA_PCH state:

6> if variable READY_FOR_COMMON_EDCH is set to TRUE:

7> move to CELL_FACH state and proceed as below.

6> else:

7> if variable H_RNTI and variable C_RNTI are set:

8> proceed as below.

7> else:

8> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below.

3> else:

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

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

3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

3> when the cell update procedure completed successfully:

4> if the UE is in CELL_PCH or URA_PCH state:

5> if variable READY_FOR_COMMON_EDCH is set to TRUE:

6> move to CELL_FACH state and proceed as below.

5> else:

6> if variable H_RNTI and variable C_RNTI are set:

7> proceed as below.

6> else:

7> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below.

1> if the IE "Frequency info" is not included in the received reconfiguration message:

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

2> if the UE finds a suitable UTRA cell on the current frequency:

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

4> when the cell update procedure completed successfully:

5> if the UE is in CELL_PCH or URA_PCH state:

6> if variable READY_FOR_COMMON_EDCH is set to TRUE:

7> move to CELL_FACH state and proceed as below.

6> else:

7> if variable H_RNTI and variable C_RNTI are set:

8> proceed as below.

7> else:

8> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below.

3> else:

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

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

3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

3> when the cell update procedure completed successfully:

4> if the UE is in CELL_PCH or URA_PCH state:

5> if variable READY_FOR_COMMON_EDCH is set to TRUE:

6> move to CELL_FACH state and proceed as below.

5> else:

6> if variable H_RNTI and variable C_RNTI are set:

7> proceed as below.

6> else:

7> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below.

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

1> if variable READY_FOR_COMMON_EDCH is set to FALSE:

2> select PRACH according to subclause 8.5.17.

1> else:

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> for 3.84 Mcps and 1.28 Mcps TDD; or

1> for FDD, 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> use the transport format set given in system information;

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 variable READY_FOR_COMMON_EDCH is set to FALSE:

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

3> if variable H_RNTI and variable C_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 any stored IE "HARQ Info".

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 E_RNTI, variable H_RNTI and variable C_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 IE "HARQ Info".

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

2> ignore that IE and stop using DRX.

1> if the UE supports RAN-assisted WLAN interworking:

2> stop the timer T330 if it is running;

2> if the variable WLAN_OFFLOAD_INFO is not empty:

3> use the information stored in the variable WLAN_OFFLOAD_INFO as specified in [4], and forward it to the upper layers.

2> else:

3> use the information stored in the variable SYSTEM_INFO_WLAN_OFFLOAD_INFO as specified in [4] and forward it to the upper layers.

1> if the contents of the variable C_RNTI is empty:

2> perform a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

2> when the cell update procedure completed successfully:

3> if the UE is in CELL_PCH or URA_PCH state:

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission";

4> proceed as below.

If the UE was in CELL_FACH state upon reception of the reconfiguration message and remains in CELL_FACH state, the UE shall:

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> 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> if the IE "Frequency info" is included in the received reconfiguration message:

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

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

3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selected another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "cell reselection";

4> when the cell update procedure completed successfully:

5> if the UE is in CELL_PCH or URA_PCH state:

6> if variable READY_FOR_COMMON_EDCH is set to TRUE:

7> move to CELL_FACH state and proceed as below.

6> else:

7> if variable H_RNTI and variable C_RNTI are set:

8> proceed as below.

7> else:

8> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below.

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

3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

3> when the cell update procedure completed successfully:

4> if the UE is in CELL_PCH or URA_PCH state:

5> if variable READY_FOR_COMMON_EDCH is set to TRUE:

6> move to CELL_FACH state and proceed as below.

5> else:

6> if variable H_RNTI and variable C_RNTI are set:

7> proceed as below.

6> else:

7> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below.

1> if the IE "Frequency info" is not included in the received reconfiguration message:

2> if the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) is included the UE shall either:

3> ignore the content of the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) and proceed as below.

2> or:

3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CPCH info" (for TDD), and it is different from the current cell:

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

4> when the cell update procedure completed successfully:

5> if the UE is in CELL_PCH or URA_PCH state:

6> if variable READY_FOR_COMMON_EDCH is set to TRUE:

7> move to CELL_FACH state and proceed as below.

6> else:

7> if variable H_RNTI and variable C_RNTI are set:

8> proceed as below.

7> else:

8> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below.

If after state transition the UE leaves CELL_FACH state, the UE shall:

1> stop timer T305.

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

1> if the UE enters CELL_PCH or URA_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> 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> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the UE supports RAN-assisted WLAN interworking:

2> if timer T330 is not configured:

3> clear the variable WLAN_OFFLOAD_INFO;

3> use the information stored in the variable SYSTEM_INFO_WLAN_OFFLOAD_INFO as specified in [4], and forward it to the upper layers.

2> else:

3> if timer T330 is not running:

4> start the timer T330;

4> use the information stored in the variable WLAN_OFFLOAD_INFO as specified in [4], and forward it to the upper layers.

The UE shall transmit a response message as specified in subclause 8.2.2.4, setting the information elements as specified below. The UE shall:

1> if the received reconfiguration message included the IE "Downlink counter synchronisation info"; or

1> if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "New U-RNTI" is included; or

1> if the received reconfiguration message included the IE "SR-VCC 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-configuation 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 COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);

2> increment by one the downlink and uplink values of the HFN of 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";

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.

2> if after state transition the UE enters CELL_DCH state:

3> clear the variable DSAC_PARAM, the variable PPAC_PARAM, the variable EAB_PARAM, the variable DSAC_PARAM_2, the variable PPAC_PARAM_2, the variable CONNECTED_MODE_ACCESS_CONTROL and the stored IE "Access Class Barred List" if stored.

1> else if the received reconfiguration message included the IE "UM RLC re-establishment RB List":

2> for each radio bearer included in the IE "UM RLC re-establishment RB List"

3> if the radio bearer uses UM RLC:

4> calculate the START value according to subclause 8.5.9;

4> include the calculated START values for the CN domain associated with the radio bearer in the IE "START list" in the IE "Uplink counter synchronisation info";

3> re-establish the UM RLC entities for the radio bearer and set the first 20 bits of all the HFN component of the respective COUNT-C values to the latest transmitted START value for the CN domain associated with the radio bearer;

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

1> if the received reconfiguration message did not include the IE "Downlink counter synchronisation info":

2> if the variable START_VALUE_TO_TRANSMIT is set:

3> include and set the IE "START" to the value of that variable.

2> if the variable START_VALUE_TO_TRANSMIT is not set and the IE "New U-RNTI" is included:

3> calculate the START value according to subclause 8.5.9;

3> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info".

2> if the received reconfiguration message caused a change in the RLC PDU size, a change from flexible to fixed RLC PDU size or a change from fixed to flexible DL RLC PDU size with RLC length indicator set to 15 bits or a change of the RLC LI size for any RB using RLC-AM:

3> calculate the START value according to subclause 8.5.9;

3> include the calculated START values for the CN domain associated with the corresponding RB identity in the IE "START list" in the IE "Uplink counter synchronisation info".

1> if the received reconfiguration 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 received reconfiguration message contained the IE "Ciphering mode info":

2> if the reconfiguration message is not used to perform an SRNS relocation, an SR-VCC or a handover from GERAN Iu mode with change of ciphering algorithm:

3> the UE behaviour is not specified.

2> if the message is used to perform a timing re-initialised hard handover:

3> if IE "Ciphering activation time for DPCH" is included:

4> the UE behaviour is not specified.

2> else:

3> if the reconfiguration message is used to setup radio bearer(s) using RLC-TM; or

3> if radio bearer(s) using RLC-TM already exist:

4> if IE "Ciphering activation time for DPCH" is not included:

5> the UE behaviour is not specified.

1> if the received reconfiguration message contained the IE "Integrity Protection mode info":

2> if the reconfiguration message is not used to perform an SRNS relocation, an SR-VCC or a handover from GERAN Iu mode:

3> the UE behaviour is not specified.

1> if the received reconfiguration message did not contain the IE "Ciphering activation time for DPCH" in IE "Ciphering mode info":

2> if prior to this procedure there exist no transparent mode RLC radio bearers:

3> if, at the conclusion of this procedure, the UE will be in CELL_DCH state; and

3> if, at the conclusion of this procedure, at least one transparent mode RLC radio bearer exists:

4> include the IE "COUNT-C activation time" and specify a CFN value for this IE that is a multiple of 8 frames (CFN mod 8 = 0) and lies at least 200 frames ahead of the CFN in which the response message is first transmitted.

NOTE: UTRAN should not include the IE "Ciphering mode info" in any reconfiguration message unless it is also used to perform an SRNS relocation with change of ciphering algorithm or it is also used to perform an SR-VCC.

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

1> clear that entry;

1> if the variable PDCP_SN_INFO is not empty:

2> include the IE "RB with PDCP information list" and set it to the value of the variable PDCP_SN_INFO.

1> in TDD, if the procedure is used to perform a handover to a cell where timing advance is enabled, and the UE can calculate the timing advance value in the new cell (i.e. in a synchronous TDD network):

2> set the IE "Uplink Timing Advance" according or the IE "Extended UL Timing Advance" to subclause 8.6.6.26.

1> if the IE "Integrity protection mode info" was present in the received reconfiguration 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 IE "RRC state indicator" is set to "CELL_DCH":

2> if the variable DEFERRED_MEASUREMENT_STATUS is set to TRUE:

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

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

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

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

4> include IE "Deferred measurement control reading".

If after state transition the UE enters 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.

1> if the UE supports RAN-assisted WLAN interworking:

2> stop the timer T330 if it is running;

2> stop using the information stored in the variable SYSTEM_INFO_WLAN_OFFLOAD_INFO, and forward this indication to the upper layers;

2> if the variable WLAN_OFFLOAD_INFO is not empty:

3> use the information stored in the variable WLAN_OFFLOAD_INFO as specified in [4], and forward it to the upper layers.

If after state transition the UE enters URA_PCH state, the UE shall, after the state transition and transmission of the response message:

1> if the state transition was not triggered by the SIGNALLING CONNECTION RELEASE INDICATION message:

2> transmit the response message.

1> enter a state according to subclause 8.6.3.3;

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

1> if the IE "Frequency info" is included in the received reconfiguration message:

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

2> if the UE can not find a suitable UTRA cell on that frequency but it finds a suitable UTRA cell on another frequency:

3> proceed as below.

1> if the IE "Frequency info" is not included in the received reconfiguration message:

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

1> prohibit periodical status transmission in RLC;

1> if the variables H_RNTI, E_RNTI and C_RNTI are not set:

2> for 3.84 Mcps 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_PCH or URA_PCH state; or

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

3> remove any C-RNTI from MAC;

3> clear the variable C_RNTI;

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> clear variable C_RNTI and delete any stored C-RNTI value;

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

3> clear any stored IE "HARQ Info";

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

3> for FDD; or

3> for 1.28 Mcps TDD, if the IE "PICH info" isn’t included in IE "Secondary CCPCH system information" in System Information Block type 5 or System Information Block type 6:

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 paging on the HS-DSCH mapped on the HS-PDSCH 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> else:

2> if the UE does support 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];

3> 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 paging on the HS-DSCH mapped on the HS-PDSCH selected by the UE according to the procedures in subclause 8.5.40 for FDD and 8.5.40a for 1.28 Mcps TDD.

2> else:

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.

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

1> if the criteria for URA update caused by "URA reselection" according to subclause 8.3.1 are fulfilled after cell selection:

2> initiate a URA update procedure according to subclause 8.3.1 using the cause "URA reselection";

2> when the URA update procedure is successfully completed:

3> the procedure ends.

If after state transition the UE enters CELL_PCH state from CELL_DCH state, the UE shall, after the state transition and transmission of the response message:

1> if the state transition was not triggered by the SIGNALLING CONNECTION RELEASE INDICATION message:

2> transmit the response message.

1> enter a state according to subclause 8.6.3.3;

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

1> if the IE "Frequency info" is included in the received reconfiguration message:

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

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

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

4> proceed as below.

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

3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

3> proceed as below.

1> if the IE "Frequency info" is not included in the received reconfiguration message:

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

2> if the UE finds a suitable UTRA cell on the current frequency:

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

4> proceed as below.

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

3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

3> proceed as below.

1> prohibit periodical status transmission in RLC;

1> for 3.84 Mcps 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 or 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 and the variable HSPA_RNTI_STORED_PCH is set to FALSE:

2> remove any C-RNTI from MAC;

2> clear the variable C_RNTI;

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 IE "New C-RNTI" is not included:

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

3> clear any stored IE "HARQ Info";

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

2> if 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 or DCCH and DTCH on the HS-DSCH according to the procedures in subclause 8.5.40 for FDD and 8.5.40a for 1.28 Mcps TDD.

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

1> the procedure ends.

If after state transition the UE enters CELL_DCH state from CELL_FACH or from CELL_PCH state:

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

2> the UE behaviour is not specified.

If after state transition the UE enters CELL_PCH state from CELL_FACH state, the UE shall, after the state transition and transmission of the response message:

1> if the state transition was not triggered by the SIGNALLING CONNECTION RELEASE INDICATION message:

2> transmit the response message.

1> enter a state according to subclause 8.6.3.3;

1> if the IE "Frequency info" is included in the received reconfiguration message:

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

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

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "cell reselection";

4> proceed as below.

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

3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

3> proceed as below.

1> if the IE "Frequency info" is not included in the received reconfiguration message:

2> if the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) is included the UE shall either:

3> ignore the content of the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) and proceed as below.

2> or:

3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CPCH info" (for TDD), and it is different from the current cell:

4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";

4> proceed as below.

1> prohibit periodical status transmission in RLC;

1> for 3.84 Mcps and 7.68 Mcps TDD; or

1> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception; 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 and the variable HSPA_RNTI_STORED_PCH is set to FALSE:

2> remove any C-RNTI from MAC;

2> clear the variable C_RNTI;

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 IE "New C-RNTI" is not included:

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

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

3> clear any stored IE "HARQ Info";

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

2> if 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:

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

1> the procedure ends.

8.2.2.3a Reception of RADIO BEARER RECONFIGURATION message by the UE performing handover from GERAN Iu mode

If the UE is performing handover from GERAN Iu mode, the UE shall, in addition to the actions in 8.2.2.3:

1> if the IE "Specification mode" is set to "Preconfiguration" and the IE "Preconfiguration mode" is set to "Predefined configuration":

2> initiate the radio bearer and transport channel configuration in accordance with the predefined parameters identified by the IE "Predefined configuration identity";

2> initiate the physical channels in accordance with the predefined parameters identified by the IE "Predefined radio configuration identity" and the received physical channel information elements;

2> store information about the established radio access bearers and radio bearers according to the IE "Predefined configuration identity".

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

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

2> initiate the physical channels in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity" and the received physical channel information elements.

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

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

2> initiate the radio bearer, transport channel and physical channel configuration in accordance with the received radio bearer, transport channel and physical channel information elements.

1> if IE "Default configuration for CELL_FACH" is set:

2> act in accordance with the default parameters according to section 13.8.

1> perform an open loop estimation to determine the UL transmission power according to subclause 8.5.3;

1> set the following variables equal to the corresponding variables in GERAN Iu mode:

CIPHERING_STATUS

ESTABLISHED_RABS

ESTABLISHED_SIGNALLING_CONNECTIONS

INTEGRITY_PROTECTION_INFO

INTER_RAT_HANDOVER_INFO_TRANSFERRED

LATEST_CONFIGURED_CN_DOMAIN

START_THRESHOLD

UE_CAPABILITY_TRANSFERRED.

1> set the new uplink and downlink HFN of RB2 to MSB₂₀(MAX(uplink HFN of RB2, downlink HFN of RB2));

NOTE: MSB₂₀() operation provides the HFN mapping from GERAN Iu mode to UTRAN. In GERAN Iu mode the length of HFN component of the COUNT-C of RB2 is longer than 20 bits.

1> initialise the variable TIMERS_AND_CONSTANTS to the default values and start to use those timer and constants values.

8.2.2.4 Transmission of a response message by the UE, normal case

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

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

In case the procedure was triggered by reception of a RADIO BEARER RECONFIGURATION message, the UE shall:

1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message on the uplink DCCH using AM RLC.

In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:

1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.

In case the procedure was triggered by reception of a TRANSPORT CHANNEL RECONFIGURATION message, the UE shall:

1> transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE as response message on the uplink DCCH using AM RLC.

In case the procedure was triggered by reception of a PHYSICAL CHANNEL RECONFIGURATION message, the UE shall:

1> transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message on the uplink DCCH using AM RLC.

In case the procedure was triggered by reception of a Target cell HS-SCCH order, the UE shall:

1> determine the corresponding RADIO BEARER SETUP COMPLETE or RADIO BEARER RECONFIGURATION COMPLETE or TRANSPORT CHANNEL RECONFIGURATION COMPLETE or PHYSICAL CHANNEL RECONFIGURATION COMPLETE response message that shall be used given by the IE "Serving Cell Change Message Type" in the stored HS-DSCH cell configuration;

1> set the IE "RRC transaction identifier" in the corresponding response message to the value of "RRC Transaction Identifier" in the entry for the corresponding response message in the table "Accepted transactions" in the variable TRANSACTIONS; and

1> transmit the corresponding RADIO BEARER SETUP COMPLETE or RADIO BEARER RECONFIGURATION COMPLETE or TRANSPORT CHANNEL RECONFIGURATION COMPLETE or PHYSICAL CHANNEL RECONFIGURATION COMPLETE response message on the uplink DCCH using AM RLC;

1> store the IE "Serving Cell Change Message Type" and the IE "Serving Cell Change Transaction Id" in the table "Processed transactions" in the variable TRANSACTIONS.

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 reconfiguration message; or

1> if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "New U-RNTI" is included; or

1> if the received reconfiguration message included the IE "SR-VCC Info":

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 COUNT-C values of all UM RLC entities to zero;

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

4> 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 received reconfiguration message contained the IE "Ciphering mode info":

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

4> notify upper layers upon change of the security configuration;

4> perform the actions below.

2> if the received reconfiguration message did not contain the IE "Ciphering mode info":

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

4> perform the actions below.

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> perform the actions below.

If the new state is CELL_PCH or URA_PCH, the response message shall be transmitted using the old configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration message, and the UE shall:

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

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

2> perform the actions below.

The UE shall:

1> set the variable ORDERED_RECONFIGURATION to FALSE;

1> if the received reconfiguration message contained the IE "Ciphering mode info":

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

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

2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.

1> if the received reconfiguration message contained the IE "Integrity protection mode info":

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

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

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

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

1> clear the variable PDCP_SN_INFO;

1> clear the variable START_VALUE_TO_TRANSMIT;

1> clear the variable SECURITY_MODIFICATION.

8.2.2.5 Reception of a response message by the UTRAN, normal case

When UTRAN has received

– the RADIO BEARER SETUP COMPLETE message; or

– the RADIO BEARER RECONFIGURATION COMPLETE message; or

– the RADIO BEARER RELEASE COMPLETE message; or

– the TRANSPORT CHANNEL RECONFIGURATION COMPLETE message; or

– the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.

UTRAN may:

1> delete the old configuration.

If the procedure caused the UE to leave the CELL_FACH state, UTRAN may:

1> delete the C-RNTI of the UE.

If the IE "UL Timing Advance" or the IE "Extended UL Timing Advance" is included in TDD, UTRAN should:

1> evaluate the timing advance value that the UE has to use in the new cell after handover.

If the IE "START" or the IE "START list " is included, UTRAN should:

1> set the START value for each CN domain with the corresponding values as received in this response message;

1> consequently, then use the START values to initialise the hyper frame numbers, in the same way as specified for the UE in subclause 8.2.2.3, for any new radio bearers that are established.

If UTRAN has ordered a ciphering reconfiguration by including the IE "Ciphering mode info", UTRAN should:

1> for radio bearers using RLC-AM or RLC-UM:

2> on the receiving side of an RLC entity apply the new ciphering configuration in uplink immediately;

2> on the transmitting side of an RLC entity apply the new ciphering configuration in downlink immediately.

1> for radio bearers using RLC-TM:

2> begin incrementing the COUNT-C at the CFN only as indicated in:

3> the IE "Ciphering activation time for DPCH" in the IE "Ciphering mode info", if included in the message that triggered the radio bearer control procedure; or

3> the IE "COUNT-C activation time", if included in the response message for this procedure.

1> and the procedure ends on the UTRAN side.

8.2.2.5a Rejection by the UE

If the UTRAN establishes one or more p-t-p radio bearer(s) for the transmission of a session of an MBMS service, identified by the IE "MBMS Session identity", for which upper layers indicate that it has already been received correctly, the UE shall:

1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below:

2> include the IE "RRC transaction identifier";

2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS;

2> clear that entry; and

2> set the IE "failure cause" to "MBMS session already received correctly".

1> set the variable UNSUPPORTED_CONFIGURATION to FALSE;

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received;

1> the procedure ends.

If the UTRAN establishes one or more p-t-p radio bearer(s) for the transmission of a session of an MBMS service, which will inhibit reception of one or more MBMS services which according to upper layers are of higher priority, the UE may:

1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below:

2> include the IE "RRC transaction identifier";

2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS;

2> clear that entry; and

2> set the IE "failure cause" to "Lower priority MBMS service".

1> set the variable UNSUPPORTED_CONFIGURATION to FALSE;

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received;

1> the procedure ends.

8.2.2.6 Unsupported configuration in the UE

If the UTRAN instructs the UE to use a configuration, which it does not support and/or if the received message causes the variable UNSUPPORTED_CONFIGURATION to be set to TRUE, the UE shall:

1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below:

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

2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and

2> clear that entry;

2> set the IE "failure cause" to "configuration unsupported".

1> set the variable UNSUPPORTED_CONFIGURATION to FALSE;

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.

The procedure ends.

8.2.2.7 Physical channel failure

If the received message caused the UE to be in CELL_DCH state and the UE according to subclause 8.5.4 failed to establish the dedicated physical channel(s) indicated in the received message or for 3.84 Mcps TDD or 7.68 Mcps TDD failed to establish the physical channel(s) indicated in the received message to which DCCH(s) are mapped the UE shall:

1> For TDD or for FDD if the CM_PATTERN_ACTIVATION_ABORTED flag is not set to TRUE:

2> revert to the configuration prior to the reception of the message (old configuration), including any HS-DSCH, E-DCH, DTX and DRX configuration if existing. If there exists any DTX or DRX configuration, the UE shall instruct the physical layer to consider only the HS-SCCH orders which were acknowledged prior to the activation time of the received message;

2> For FDD: if the UE was in Cell DCH state prior to the reconfiguration:

3> if the variable DTX_DRX_STATUS is set to TRUE, re-configure the physical layer to perform discontinuous uplink DPCCH transmission and enable or disable discontinuous downlink reception operations according to the variable DTX_DRX_PARAMS at the CFN corresponding to the frame boundary that is offset by the stored value of the IE "Enabling Delay" from the frame boundary where uplink transmission resumes with the old configuration;

3> if the variable SECONDARY_CELL_E_DCH_TRANSMISSION is set to TRUE:

4> consider the secondary uplink frequency as not activated.

3> perform the physical layer synchronisation procedure A as specified in [29];

3> apply power control preamble according to [26] during the number of frames indicated in the IE "PC preamble" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE; and

3> then not send any data on signalling radio bearers RB0 to RB4 during the number of frames indicated in the IE "SRB delay" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE or while the physical channel is not considered established.

1> if the old configuration includes dedicated physical channels (CELL_DCH state) and the UE is unable to revert to the old configuration or for FDD if the CM_PATTERN_ACTIVATION_ABORTED flag is set to TRUE:

2> initiate a cell update procedure according to subclause 8.3.1, using the cause "radio link failure";

2> after the cell update procedure has completed successfully:

3> proceed as below.

1> if the old configuration does not include dedicated physical channels (CELL_FACH state):

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

2> if the UE selects another cell than the cell the UE camped on upon reception of the reconfiguration message:

3> initiate a cell update procedure according to subclause 8.3.1, using the cause "Cell reselection";

3> after the cell update procedure has completed successfully:

4> proceed as below.

1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below:

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

2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and

2> clear that entry;

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

1> set the variable ORDERED_RECONFIGURATION to FALSE;

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.

The procedure ends.

8.2.2.8 Cell re-selection

If the UE performs cell re-selection during the reconfiguration procedure, the UE shall:

1> initiate a cell update procedure, as specified in subclause 8.3.1;

1> continue with the reconfiguration procedure.

NOTE: After the completion of the cell update procedure and completion of the reconfiguration procedure within the UE, the UE will move to the RRC state as indicated in the reconfiguration message.

8.2.2.9 Transmission of a response message by the UE, failure case

The UE shall:

1> in case of reception of a RADIO BEARER SETUP message:

2> if the radio bearer establishment procedure affects several radio bearers:

3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER SETUP FAILURE message.

2> transmit a RADIO BEARER SETUP FAILURE as response message on the DCCH using AM RLC.

1> in case of reception of a RADIO BEARER RECONFIGURATION message:

2> if the radio bearer reconfiguration procedure affects several radio bearers:

3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER RECONFIGURATION FAILURE message.

2> transmit a RADIO BEARER RECONFIGURATION FAILURE as response message on the DCCH using AM RLC.

1> in case of reception of a RADIO BEARER RECONFIGURATION message encapsulated in INTERSYSTEM HANDOVER TO UTRAN COMMAND message in GERAN Iu mode:

2> perform the actions.

1> in case of reception of a RADIO BEARER RELEASE message:

2> if the radio bearer release procedure affects several radio bearers:

3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER RELEASE FAILURE message.

2> transmit a RADIO BEARER RELEASE FAILURE as response message on the DCCH using AM RLC.

1> in case of reception of a TRANSPORT CHANNEL RECONFIGURATION message:

2> transmit a TRANSPORT CHANNEL RECONFIGURATION FAILURE as response message on the DCCH using AM RLC.

1> in case of reception of a PHYSICAL CHANNEL RECONFIGURATION message:

2> transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE as response message on the DCCH using AM RLC.

1> when the response message has been submitted to lower layers for transmission:

2> continue with any ongoing processes and procedures as if no reconfiguration attempt had occurred.

8.2.2.10 Reception of a response message by the UTRAN, failure case

When the UTRAN has received:

– the RADIO BEARER SETUP FAILURE message; or

– the RADIO BEARER RECONFIGURATION FAILURE message; or

– the RADIO BEARER RELEASE FAILURE message; or

– the TRANSPORT CHANNEL RECONFIGURATION FAILURE message; or

– the PHYSICAL CHANNEL RECONFIGURATION FAILURE message:

the UTRAN may restore the old and delete the new configuration. Upper layers should be notified of the failure.

The procedure ends on the UTRAN side.

8.2.2.11 Invalid configuration

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

1> keep the configuration existing before the reception of the message;

1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below:

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

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

3> clear that entry.

2> set the IE "failure cause" to "invalid configuration".

1> set the variable INVALID_CONFIGURATION to FALSE;

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.

The procedure ends.

8.2.2.12 Incompatible simultaneous reconfiguration

If the table "Rejected transactions" in the variable TRANSACTIONS is set due to the received message and the variable PROTOCOL_ERROR_REJECT is set to FALSE, the UE shall:

1> not apply the configuration contained in the received reconfiguration message;

1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below:

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

2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and

2> clear that entry;

2> set the IE "failure cause" to "incompatible simultaneous reconfiguration".

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.

The procedure ends.

8.2.2.12a Incompatible simultaneous security reconfiguration

If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION is set to TRUE due to the received reconfiguration message, the UE shall:

1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below:

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

2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and

2> clear that entry;

2> set the IE "failure cause" to the cause value "incompatible simultaneous reconfiguration".

1> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to FALSE;

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.

The procedure ends.

8.2.2.12b Cell update procedure during security reconfiguration

If:

– a cell update procedure according to subclause 8.3.1 is initiated; and

– the received reconfiguration message causes either:

– the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE; and/or

– the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE:

the UE shall:

1> release all radio resources;

1> indicate the release 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; and

1> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS;

1> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

1> clear the variable ESTABLISHED_RABS;

1> if the received reconfiguration message contained the IE "Ciphering mode info":

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

2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO;

2> clear the variable SECURITY_MODIFICATION.

1> if the received reconfiguration message contained the IE "Integrity protection mode info":

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

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

1> enter idle mode;

1> perform the actions specified in subclause 8.5.2 when entering idle mode;

1> and the procedure ends.

NOTE: UTRAN should use RB Control messages to perform an SRNS relocation only in case of state transitions from CELL_DCH to CELL_DCH.

8.2.2.13 Invalid received message

If the received reconfiguration message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall:

1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below:

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

2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and

2> clear that entry;

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

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

The procedure ends.

8.2.2.14 Radio link failure

If the criteria for radio link failure are met in the old configuration during the reconfiguration procedure as specified in subclause 8.5.6, the UE shall:

1> if UE would have entered CELL_PCH or URA_PCH as a result of this reconfiguration procedure and UE has already submitted a response message to lower layers:

2> act as if the reconfiguration message was not received;

2> initiate a cell update procedure according to subclause 8.3.1, using the cause "radio link failure";

2> the procedure ends.

NOTE: UTRAN should consider the reconfiguration procedure as unsuccessful in this case even if a success response message had been received.

1> if the UE would have remained in CELL_DCH state as a result of this reconfiguration procedure:

2> initiate a cell update procedure according to subclause 8.3.1, using the cause "radio link failure";

2> after the cell update procedure has completed successfully:

3> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below:

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

4> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and

4> clear that entry;

4> set the IE "failure cause" to "physical channel failure".

3> act as if the reconfiguration message was not received;

3> the procedure ends.

In case of SRNS relocation, if the criteria for radio link failure are met in the new configuration during the reconfiguration procedure (i.e. while UE is waiting for RLC acknowledgement for a response message.) as specified in subclause 8.5.6, the UE shall:

1> if the received reconfiguration causes either:

– the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE; and/or

– the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE:

2> perform the actions specified in subclause 8.2.2.12b.

1> else:

2> release all its radio resources;

2> indicate the release 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 any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS;

2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;

2> clear the variable ESTABLISHED_RABS;

2> enter idle mode;

2> perform the actions specified in subclause 8.5.2 when entering idle mode; and

2> the procedure ends.