8.1.3 RRC connection establishment

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

Figure 8.1.3-1: RRC Connection Establishment, network accepts RRC connection

Figure 8.1.3-2: RRC Connection Establishment, network rejects RRC connection

8.1.3.1 General

The purpose of this procedure is to establish an RRC connection.

8.1.3.2 Initiation

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

Upon initiation of the procedure, the UE shall:

1> set the variable PROTOCOL_ERROR_INDICATOR to FALSE;

1> if the USIM is present:

2> set the value of "THRESHOLD" in the variable "START_THRESHOLD" to the 20 MSBs of the value stored in the USIM [50] for the maximum value of START for each CN Domain.

1> if the SIM is present:

2> set the value of "THRESHOLD" in the variable "START_THRESHOLD" to the default value in [40] for each CN Domain.

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

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

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

1> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH or the common E-DCH (for the Enhanced Uplink in CELL_FACH state and Idle mode);

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

1> set counter V300 to 1; and

1> if the variable ESTABLISHMENT_CAUSE is set to "MBMS reception":

2> when the MAC layer indicates success or failure to transmit the message:

3> if the MAC layer indicates failure:

4> enter idle mode;

4> consider the procedure to be unsuccessful;

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

4> the procedure ends.

3> else:

4> start timer T318;

4> apply value 0 for counter N300 regardless of the value included in IE "UE Timers and Constants in idle mode".

1> otherwise:

2> start timer T300 when the MAC layer indicates success or failure to transmit the message.

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_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 a Secondary CCPCH according to [4];

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

1> otherwise:

2> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to TRUE; and

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

8.1.3.3 RRC CONNECTION REQUEST message contents to set

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

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

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

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

1> include the IE "Predefined configuration status information" and set this IE to TRUE if the UE has all pre- configurations stored with the same value tag as broadcast in the cell in which the RRC connection establishment is initiated;

1> if the UE is attempting to establish the signalling connection to PS-domain:

2> include the IE "Domain Indicator" and set it to "PS domain".

1> else if the UE is attempting to establish the signalling connection to CS domain:

2> include the IE "Domain Indicator" and set it to "CS domain";

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

1> if the UE only supports HS-DSCH but not E-DCH:

2> include the IE "UE capability indication" and set it to the "HS-DSCH" value.

1> if the UE supports HS-DSCH and E-DCH:

2> include the IE "UE capability indication" and set it to the "HS-DSCH+E-DCH" value.

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 the UE performs connection establishment 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 the 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 connection establishment 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 the UE supports MAC-ehs:

2> include the IE "MAC-ehs support" and set it to TRUE.

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

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

1> if the UE supports Enhanced Uplink in CELL_FACH state and Idle mode:

2> include the IE "Support of common E-DCH" and set it to TRUE.

NOTE: In 1.28 Mcps TDD, UE supporting HS-DSCH reception in CELL_FACH state always supports Enhanced Uplink in CELL_FACH state and Idle mode, and vice versa.

1> if the UE supports MAC-i/is:

2> include the IE "Support of MAC-i/is" and set it to TRUE.

1> if the UE supports E-UTRA:

2> if the UE is attempting to establish the signalling connection as a result of being redirected by E-UTRA; and

2> if this is the first attempt to establish the signalling connection:

3> do not include the IE "Pre-Redirection info".

2> else:

3> if the variable EUTRA_FREQUENCY_INFO_LIST contains no E-UTRA frequencies:

4> include the IE "Pre-Redirection info";

4> if the UE supports E-UTRA FDD:

5> set the IE "Support of E-UTRA FDD" to TRUE.

4> if the UE supports E-UTRA TDD:

5> set the IE "Support of E-UTRA TDD" to TRUE.

3> if the UE supports any of the bands that the E-UTRA frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:

4> include the IE "Pre-Redirection info";

4> if the UE supports any of the bands that the E-UTRA FDD frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:

5> set the IE "Support of E-UTRA FDD" to TRUE.

4> if the UE supports any of the bands that the E-UTRA TDD frequencies included in the variable EUTRA_FREQUENCY_INFO_LIST belong to:

5> set the IE "Support of E-UTRA TDD" to TRUE.

1> if the variable SYSTEM_INFORMATION_CONTAINER is not empty:

2> include the IE "System Information Container Stored Indication" and set it to TRUE.

1> For FDD, if the UE supports dual cell operation on adjacent frequencies:

2> include the IE "Multi cell support" and set it to TRUE;

2> if the UE supports dual cell with MIMO operation on adjacent frequencies:

3> include the IE "Dual cell MIMO support" and set it to TRUE.

2> if the UE supports multi-cell operation on more than two cells:

3> if the UE is of HS-DSCH category 30 or 32 or 34 or 35 or 36 or 38 according to [35]:

4> include the IE "More than two cell or MIMO mode with four transmit antennas support" and set it to "higher rate".

3> otherwise:

4> include the IE "More than two cell or MIMO mode with four transmit antennas support" and set it to "lower rate".

2> else if the UE supports multi-cell operation on two cells:

3> if the UE is of HS-DSCH category 37 according to [35]:

4> include the IE "More than two cell or MIMO mode with four transmit antennas support" and set it to "lower rate".

1> For 1.28 Mcps TDD, if the UE supports MU-MIMO:

2> if the UE supports uplink and downlink MU-MIMO:

3> include the IE "More than two cell support" and set it to "higher rate".

2> if the UE supports uplink MU-MIMO only:

3> include the IE "More than two cell support" and set it to "lower rate".

1> if the UE supports CS voice over HSPA:

2> include the IE "Support for CS Voice over HSPA" and set it to TRUE.

1> if the IE "Support of the first Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT is set to TRUE:

2> include the IE "Support of the first Frequency Band" and set it to TRUE.

1> if the IE "Support of the second Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT is set to TRUE:

2> include the IE "Support of the second Frequency Band" and set it to TRUE.

1> if the UE is attempting to establish the signalling connection to CS domain due to CSFB call initiated in E-UTRA:

2> include the IE "CSFB Indication" and set it to TRUE.

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

8.1.3.4 Reception of an RRC CONNECTION REQUEST message by the UTRAN

Upon receiving an RRC CONNECTION REQUEST message, UTRAN should either:

1> accept the request and use a predefined or default radio configuration, in which case it should:

2> include the following information in the RRC CONNECTION SETUP message:

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

3> the IE "Default configuration mode" and IE "Default configuration identity", to indicate which default configuration of RB and transport channel parameters shall be used;

3> PhyCH information elements.

2> submit the RRC CONNECTION SETUP message to the lower layers for transmission on the downlink CCCH.

NOTE 1: UTRAN should only apply a predefined radio configuration in case it orders the UE to enter CELL_DCH. This is because the predefined configuration information included in System Information Block 16 mandatorily includes information only required in CELL_DCH state.

1> accept the request without using a predefined or default radio configuration, in which case it should:

2> include in the RRC CONNECTION SETUP message the complete set of RB, TrCH and PhyCH information elements to be used;

2> submit the RRC CONNECTION SETUP message to the lower layers for transmission on the downlink CCCH.

NOTE 2: In R’99, the RRC CONNECTION SETUP message always includes the IEs "Added or Reconfigured TrCH information list", both for uplink and downlink transport channels, even if UTRAN orders the UE to move to CELL_FACH and hence need not configure any transport channels. In these cases, UTRAN may include a configuration that adds little to the encoded message size e.g. a DCH with a single zero size transport format. At a later stage, UTRAN may either remove or reconfigure this configuration.

1> submit an RRC CONNECTION REJECT message on the downlink CCCH. In the RRC CONNECTION REJECT message, the UTRAN may direct the UE to another UTRA carrier or to another system. The UTRAN may direct the UE to E-UTRAN FDD only if the IE "Pre-Redirection info" is present in the RRC CONNECTION REQUEST message and the IE "Support of E-UTRA FDD" is set to TRUE; the UTRAN may direct the UE to E-UTRAN TDD only if the IE "Pre-Redirection info" is present in the RRC CONNECTION REQUEST message and the IE "Support of E-UTRA TDD" is set to TRUE. After the RRC CONNECTION REJECT message has been sent, all context information for the UE may be deleted in UTRAN.

NOTE 3: UTRAN should not send RRC CONNECTION REJECT message to direct UE to E-UTRAN if there is no means for UTRAN to determine that UE subscription allows UE access to E-UTRAN.

8.1.3.5 Cell re-selection, T300 or T318 timeout

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

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

the UE shall:

1> if the UE performs cell reselection:

2> clear the variable SYSTEM_INFORMATION_CONTAINER.

1> check the value of V300; and

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

3> if cell re-selection occurred:

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

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

5> if variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE:

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

5> else:

6> set the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to TRUE;

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

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

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

3> apply the given Access Service Class when accessing the RACH or the common E-DCH (for the Enhanced Uplink in CELL_FACH state and Idle mode);

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

3> increment counter V300;

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

2> if V300 is greater than N300:

3> if the UE supports logging of failed RRC Connection Establishment, perform the actions specified in subclause 8.1.3.11;

3> if the UE supports RRC Connection Establishment failure temporary Qoffset and RRC Connection Establishment failure has occurred a consecutive "ConnEst Fail Count" times on the same cell for which "Tx Fail Params" is included in System Information Block Type 3:

4> for a period as indicated by "Offset Validity":

5> use "ConnEst Fail Qoffset_,temp" for the parameter Qoffset_temp for the concerned cell when performing cell selection and reselection according to TS 25.304 [4] and TS 36.304 [66].

NOTE : When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE implementation whether to stop using "ConnEst Fail Qoffset_,temp" for the parameter Qoffset_temp during "Offset Validity" for the concerned cell.

3> enter idle mode;

3> consider the procedure to be unsuccessful;

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

3> the procedure ends.

8.1.3.5a Abortion of RRC connection establishment

If the UE has not yet entered UTRA RRC Connected mode and the RRC connection establishment is to be aborted as specified in subclause 8.1.8, the UE shall:

1> consider the procedure to be unsuccessful;

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

The procedure ends.

8.1.3.6 Reception of an RRC CONNECTION SETUP message by the UE

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

If the values are different, the UE shall:

1> ignore the rest of the message.

If the values are identical, the UE shall:

1> if IE "Specification mode" is set to "Preconfiguration" and 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" with the following exception:

3> ignore the IE "RB to setup list" and the IE "Re- establishment timer".

NOTE: IE above IEs are mandatory to include in IE “Predefined RB configuration” that is included in System Information Block 16 but should be ignored since it is not possible to establish a RAB during RRC connection establishment.

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

1> if IE "Specification mode" is set to "Preconfiguration" and 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 IE "Default configuration identity" with the following exception:

3> ignore the radio bearers other than signalling radio bearers.

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

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

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> clear the variable ESTABLISHMENT_CAUSE;

1> for FDD and 1.28 Mcps TDD, if the HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE:

2> set the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE.

1> stop timer T300 or T318, whichever one is running, and act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following:

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

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

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

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

3> else:

4> for 1.28Mcps TDD, continue to use the currently used frequency as working frequency.

3> enter UTRA RRC connected mode;

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

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

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

3> if variable READY_FOR_COMMON_EDCH is set to FALSE:

4> select PRACH according to subclause 8.5.17.

3> else:

4> configure the Enhanced Uplink in CELL_FACH state and Idle mode as specified in subclause 8.5.45 for FDD and 8.5.45a for 1.28 Mcps TDD.

3> for 3.84 Mcps and 7.68 Mcps TDD; or

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

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

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

4> select Secondary CCPCH according to subclause 8.5.19.

3> else:

4> set variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED to FALSE;

4> For FDD if variable READY_FOR_COMMON_EDCH is set to FALSE:

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

5> if "new H-RNTI" and "new C-RNTI" are included:

6> store the "new H-RNTI" according to subclause 8.6.3.1b;

6> store the "new C-RNTI" according to subclause 8.6.3.9;

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

5> else:

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

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

6> clear any stored IE "HARQ Info";

6> set the variable INVALID_CONFIGURATION to TRUE.

4> else:

5> if the RBs have the multiplexing option with transport channel type "HS-DSCH" for the DL and transport channel type "E-DCH" in the UL; and

5> if the IEs "new Primary E-RNTI", "new H-RNTI" and "new C-RNTI" are included:

6> store the "new Primary E-RNTI" according to subclause 8.6.3.14;

6> store the "new H-RNTI" according to subclause 8.6.3.1b;

6> store the "new C-RNTI" according to subclause 8.6.3.9;

6> configure Enhanced Uplink in CELL_FACH state and Idle mode according to subclause 8.5.45 for FDD and 8.5.45a for 1.28 Mcps TDD;

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

5> else:

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

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

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

6> clear any stored IE "HARQ Info";

6> set the variable INVALID_CONFIGURATION to TRUE.

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

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

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

2> enter UTRA RRC connected mode;

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

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

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

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

3> clear that entry.

2> if the USIM or SIM is present:

3> set the "START" for each CN domain in the IE "START list" in the RRC CONNECTION SETUP COMPLETE message with the corresponding START value that is stored in the volatile memory of the ME if the USIM [50], or the SIM is present.

2> if neither the USIM nor SIM is present:

3> set the "START" for each CN domain in the IE "START list" in the RRC CONNECTION SETUP COMPLETE message to zero;

3> set the value of "THRESHOLD" in the variable "START_THRESHOLD" to the default value [40].

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

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

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

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

2> if the UE supports contiguous multi-cell operation on four cells in the same band, include the IE "Additional Secondary Cells" in the IE "UE radio access capability extension" and set it to ‘a2’ for the supported bands; otherwise, if the UE supports contiguous multi-cell operation on three cells in the same band, include the IE "Additional Secondary Cells" in the IE "UE radio access capability extension" and set it to ‘a1’ for the supported bands;

2> if the UE supports contiguous multi-cell operation on eight cells in the same band, include the IE "Additional Secondary Cells 2" in the IE "UE radio access capability extension" and set it to ‘a6’ for the supported bands;

2> if the UE supports contiguous multi-cell operation on seven cells in the same band, include the IE "Additional Secondary Cells 2" in the IE "UE radio access capability extension" and set it to ‘a5’ for the supported bands;

2> if the UE supports contiguous multi-cell operation on six cells in the same band, include the IE "Additional Secondary Cells 2" in the IE "UE radio access capability extension" and set it to ‘a4’ for the supported bands;

2> if the UE supports contiguous multi-cell operation on five cells in the same band, include the IE "Additional Secondary Cells 2" in the IE "UE radio access capability extension" and set it to ‘a3’ for the supported bands;

2> if the UE supports non-contiguous multi-cell operation on two cells in the same band:

3> set the IE "Aggregated cells" in IE "Non-contiguous multi-cell" in the IE "UE radio access capability extension" to ‘nc-2c’ for the supported band;

3> set the IE "Gap size" in IE "Non-contiguous multi-cell" in the IE "UE radio access capability extension" for the supported band to ‘fiveMHz’ or ‘tenMHz’ or ‘anyGapSize’, or

2> if the UE supports non-contiguous multi-cell operation on three cells in the same band:

3> set the IE "Aggregated cells" in IE "Non-contiguous multi-cell" in the IE "UE radio access capability extension" to ‘nc-3c’ for the supported band;

3> set the IE "Gap size" in IE "Non-contiguous multi-cell" in the IE "UE radio access capability extension" for the supported band to ‘fiveMHz’ or ‘tenMHz’ or ‘anyGapSize’, or

2> if the UE supports non-contiguous multi-cell operation on four cells in the same band:

3> set the IE "Aggregated cells" in IE "Non-contiguous multi-cell" in the IE "UE radio access capability extension" to ‘nc-4c’ for the supported band;

3> set the IE "Gap size" in IE "Non-contiguous multi-cell" in the IE "UE radio access capability extension" for the supported band to ‘fiveMHz’ or ‘tenMHz’ or ‘anyGapSize’;

3> if the UE supports an equal number of contiguous cells on each side of the gap, include the IE "Non-contiguous multi-cell Combination (2,2)";

3> if the UE supports a different number of contiguous cells on each side of the gap, include the IE "Non-contiguous multi-cell Combination (3,1) (1,3)".

2> if the UE supports Multiflow operation on two cells on one frequency:

3> set the IE "Number of cells" in IE "Multiflow per band capability" to two cells;

3> set the IE "Number of frequencies" in IE "Multiflow per band capability" to one frequency.

2> if the UE supports Multiflow operation on three cells on two frequencies in the same band:

3> set the IE "Number of cells" in IE "Multiflow per band capability" to three cells;

3> set the IE "Number of frequencies" in IE "Multiflow per band capability" to two frequencies.

2> if the UE supports Multiflow operation on four cells on two frequencies in the same band:

3> set the IE "Number of cells" in IE "Multiflow per band capability" to four cells;

3> set the IE "Number of frequencies" in IE "Multiflow per band capability" to two frequencies.

2> if the UE supports Multiflow operation on four cells on three frequencies in the same band:

3> set the IE "Number of cells" in IE "Multiflow per band capability" to four cells;

3> set the IE "Number of frequencies" in IE "Multiflow per band capability" to three frequencies.

2> if the UE support Multiflow operation on three or four non-contiguous cells in the same band:

3> set the IE "Gap size" in IE "Multiflow per band capability".

2> if the UE supports Multiflow operation with MIMO:

3> set IE "MIMO support" in IE "Multiflow per band capability" to single or dual stream MIMO transmission in all the frequency bands where the Multiflow operation is supported;

3> if the UE needs more processing to generate HARQ feedback for Multiflow with MIMO operation:

4> set IE "Longer HARQ processing time" in IE "Multiflow capability".

2> if the UE supports Multiflow operation on three or four cells on two frequencies in different bands:

3> set the IE "Supported Multiflow Combination" in IE "Radio Access Capability Band Combination List";

3> if the UE supports three cells on two frequencies in different bands:

4> set the IE "Number of cells in band A" to two cells;

4> set the IE "Number of cells in band B" to one cell;

4> set the IE "Number of frequencies in band A" to one frequency;

4> set the IE "Number of frequencies in band B" to one frequency.

3> if the UE supports four cells on two frequencies in different bands:

4> set the IE "Number of cells in band A" to two cells;

4> set the IE "Number of cells in band B" to two cells;

4> set the IE "Number of frequencies in band A" to one frequency;

4> set the IE "Number of frequencies in band B" to one frequency.

3> if the UE supports four cells on three frequencies in different bands:

4> set the IE "Number of cells in band A" to three cells;

4> set the IE "Number of cells in band B" to one cell;

4> set the IE "Number of frequencies in band A" to two frequencies;

4> set the IE "Number of frequencies in band B" to one frequency.

3> if the UE supports MIMO with Multiflow in different bands:

4> set IE "Support for Multiflow with MIMO operation in different bands" in IE "Multiflow capability".

2> if the variable DEFERRED_MEASUREMENT_STATUS is 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".

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

3> include IE "Logged Meas Available".

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

3> include IE "ANR Logging Results Available".

2> if an IE "Logged Connection Establishment Failure Info-FDD" or "Logged Connection Establishment Failure Info-TDD" in variable LOGGED_CONNECTION_ESTABLISHMENT_FAILURE is present and the current Registered PLMN is the same as the PLMN in IE "PLMN Identity" stored in variable LOGGED_CONNECTION_ESTABLISHMENT_FAILURE:

3> include IE "Connection Establishment Failure Info Available".

NOTE: If the "RRC State indicator" is set to the value "CELL_FACH", the UE continues to read and store the IEs in System Information Block type 11, System Information Block type 11bis, System Information Block type 11ter, System Information Block type 12, System Information Block type 18 and System Information Block type 19, if transmitted, after submitting the RRC Connection Setup Complete message to lower layers (see 8.5.31).

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

1> if the UE has entered CELL_DCH state:

2> clear the variable SYSTEM_INFORMATION_CONTAINER;

2> if the IE "Deferred measurement control reading" was included in the RRC CONNECTION SETUP COMPLETE message:

3> clear variable MEASUREMENT_IDENTITY;

3> clear the variable CELL_INFO_LIST.

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

3> stop the timer T330, if it is running;

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

3> if the variable WLAN_OFFLOAD_INFO is not empty:

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

1> if the UE has entered CELL_FACH state:

2> if the variable SYSTEM_INFORMATION_CONTAINER is not empty:

3> the UE behaviour is unspecified.

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

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

3> stop the timer T330, if it is running;

3> if the variable WLAN_OFFLOAD_INFO is not empty:

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

3> else:

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

1> store the contents of the variable UE_CAPABILITY_REQUESTED in the variable UE_CAPABILITY_TRANSFERRED;

1> initialise variables upon entering UTRA RRC connected mode as specified in subclause 13.4;

1> consider the procedure to be successful.

And the procedure ends.

8.1.3.7 Physical channel failure or cell re-selection

1> If the UE failed to establish, per subclause 8.5.4, the physical channel(s) indicated in the RRC CONNECTION SETUP message; or

1> if the UE performs cell re-selection; or

1> if the UE will be in the CELL_FACH state at the conclusion of this procedure; and

1> if the received RRC CONNECTION SETUP message included the IE "Frequency info" and the UE could not find a suitable UTRA cell on that frequency but it could find a suitable UTRA cell on another frequency; or

1> if the received RRC CONNECTION SETUP 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

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

1> after having received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and

1> before the RRC CONNECTION SETUP COMPLETE message is delivered to lower layers for transmission:

the UE shall:

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

1> clear the variable SYSTEM_INFORMATION_CONTAINER;

1> check the value of V300, and:

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

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

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

3> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH or the common E-DCH (for the Enhanced Uplink in CELL_FACH and Idle mode);

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

3> increment counter V300; and

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

2> if V300 is greater than N300:

3> if the UE supports logging of failed RRC Connection Establishment, perform the actions specified in subclause 8.1.3.11;

3> enter idle mode;

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

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

8.1.3.8 Invalid RRC CONNECTION SETUP message, unsupported configuration or invalid configuration

If the UTRAN instructs the UE to use a configuration, which it does not support e.g., the message includes a pre-defined configuration that the UE has not stored and/or if the received message causes the variable UNSUPPORTED_CONFIGURATION or the variable INVALID_CONFIGURATION to be set to TRUE the UE shall perform procedure specific error handling as specified in this subclause.

If the UE receives an RRC CONNECTION SETUP message which contains an IE "Initial UE identity" with a value which is identical to the value of the variable INITIAL_UE_IDENTITY, but the RRC CONNECTION SETUP 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> stop timer T300 or T318, whichever one is running; and

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

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

1> if the RRC CONNECTION SETUP message contained a configuration the UE does not support; and/or

1> if the variable UNSUPPORTED_CONFIGURATION becomes set to TRUE due to the received RRC CONNECTION SETUP message; and/or

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

the UE shall:

1> stop timer T300 or T318, whichever one is running; and

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

If V300 is equal to or smaller than N300, the UE shall:

1> set the variable PROTOCOL_ERROR_INDICATOR to TRUE;

1> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.3;

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

1> apply the given Access Service Class when accessing the RACH or the common E-DCH (for the Enhanced Uplink in CELL_FACH and Idle mode);

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

1> increment counter V300; and

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

If V300 is greater than N300, the UE shall:

1> if the UE supports logging of failed RRC Connection Establishment, perform the actions specified in subclause 8.1.3.11;

1> enter idle mode;

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

1> consider the RRC establishment procedure to be unsuccessful;

1> the procedure ends.

8.1.3.9 Reception of an RRC CONNECTION REJECT message by the UE

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

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

If the values are identical, the UE shall:

1> stop timer T300 or T318, whichever one is running; and

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

1> if the UE has disabled cell reselection to a UTRA carrier due to an earlier RRC CONNECTION REJECT message, the UE shall resume cell reselection to that UTRA carrier;

1> if the Rejection Cause is ‘unspecified’ and the IE "Counting Completion" is present, the UE shall terminate an ongoing MBMS counting procedure according to subclause 8.7.4.4;

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

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

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

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

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

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

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

4> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH or the common E-DCH (for the Enhanced Uplink in CELL_FACH and Idle mode);

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

4> reset counter V300;

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

4> disable cell reselection to original UTRA carrier until the time stated in the IE "wait time" has elapsed or until the RRC connection establishment procedure ends, whichever occurs first.

3> if no suitable cell on the designated UTRA carrier is found:

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

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

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

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

4> increment counter V300;

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

2> if V300 is greater than N300:

3> if the UE supports logging of failed RRC Connection Establishment, perform the actions specified in subclause 8.1.3.11;

3> enter idle mode;

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

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

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

2> if the IE "wait time" = ‘0’:

3> the UE behaviour is not specified.

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

3> if the IE "GSM target cell info" is present:

4> attempt to camp on a suitable cell of the list of cells indicated for that RAT;

4> if the UE selects and camps on one of the cells indicated for that RAT:

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

4> if the UE cannot find any suitable cell from the indicated ones within 10s, the UE is allowed to camp on any suitable cell on that RAT.

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

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

3> if the IE "E-UTRA target info" is present:

4> attempt to camp on a suitable cell on one of the frequencies indicated for that RAT, excluding any cell indicated in the list of not allowed cells for that RAT (i.e. the "exclude-listed cells per freq list" for E-UTRA), if present;

4> if the UE selects and camps on one such cell:

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

4> if the UE cannot find any suitable cell on the indicated frequencies within 10s, the UE is allowed to camp on any suitable cell on that RAT:

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

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

3> if neither the IE "GSM target cell info" nor the IE "E-UTRA target info" is present:

4> select a suitable cell in the designated RAT;

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

5> disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed or until the UE successfully establishes a connection on the designated RAT, whichever occurs first.

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

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

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

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

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

4> increment counter V300;

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

2> if V300 is greater than N300:

3> if the UE supports logging of failed RRC Connection Establishment, perform the actions specified in subclause 8.1.3.11;

3> enter idle mode;

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

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

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

1> if neither the IEs "frequency info" nor "inter-RAT info" are present:

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

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

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

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

3> increment counter V300;

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

2> if V300 is greater than N300:

3> if the UE supports logging of failed RRC Connection Establishment, perform the actions specified in subclause 8.1.3.11;

3> enter idle mode;

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

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

1> if the IE "wait time" = ‘0’:

2> if the IE "Extended Wait Time" is present and the UE supports "delay tolerant access":

3> forward the IE "Extended Wait Time" to the upper layers.

2> enter idle mode;

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

2> consider the RRC establishment procedure to be unsuccessful;

2> the procedure ends.

8.1.3.10 Invalid RRC CONNECTION REJECT message

If the UE receives an RRC CONNECTION REJECT message which contains an IE "Initial UE identity" with a value which is identical to the value of the IE "Initial UE identity" in the most recent RRC CONNECTION REQUEST message sent by the UE; but the RRC CONNECTION REJECT 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> stop timer T300 or T318, whichever one is running; and

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

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

2> set the variable PROTOCOL_ERROR_INDICATOR to TRUE;

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

2> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH or the common E-DCH (for the Enhanced Uplink in CELL_FACH and Idle mode);

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

2> increment counter V300;

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

1> if V300 is greater than N300:

2> if the UE supports logging of failed RRC Connection Establishment, perform the actions specified in subclause 8.1.3.11;

2> enter idle mode;

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

2> consider the procedure to be successful;

2> the procedure ends.

8.1.3.11 Logging of failed RRC Connection Establishment

If the RRC connection establishment fails and the UE supports logging of failed RRC Connection Establishment, the UE shall perform logging of information for later retrieval. The UE shall store connection establishment failure information in the variable LOGGED_CONNECTION_ESTABLISHMENT_FAILURE by setting its fields as follows:

1> clear the information included in the variable LOGGED_CONNECTION_ESTABLISHMENT_FAILURE, if any;

1> set the IE "PLMN Identity" to the same value as the selected PLMN [4];

1> set the IE "Number Of RRC Msg Transmitted" to indicate the number of times the RRC CONNECTION REQUEST message was transmitted by the UE during the failed RRC Connection Establishment procedure;

1> for TDD:

2> set the IE "FPACH Received" to TRUE if FPACH was received during the failed RRC Connection Establishment procedure;

2> if common E-DCH was used, include the IE "E-RUCCH Failure" and set it to TRUE if failure indication of the E-RUCCH transmission was received during the failed RRC Connection Establishment procedure.

1> if detailed location information is available:

2> if the UE has been able to calculate a 3-dimensional position:

3> set the IE "Ellipsoid point with altitude" or the IE "Ellipsoid point with altitude and uncertainty ellipsoid" to include the location coordinates.

2> else:

3> set the IE "Ellipsoid point" or the IE "Ellipsoid point with uncertainty circle" or the IE "Ellipsoid point with uncertainty ellipse" to include the location coordinates.

2> if horizontal velocity information is available:

3> set the IE "Horizontal velocity" to include the horizontal velocity.

2> a value of the IE "Confidence", different from "0" should be calculated, as the probability that the UE is located within the uncertainty region of the one of the IEs "Ellipsoid point with uncertainty ellipse" or "Ellipsoid point with altitude and uncertainty ellipsoid".

1> set the IE "PLMN Identity" of the Logged Measurements Failed Cell to indicate the IE "PLMN Identity" obtained from system information of the cell where the connection establishment failure was detected;

1> set the IE "Cell ID" to indicate cell identity obtained from system information of the cell where the connection establishment failure was detected;

1> set the IE "CPICH Ec/N0" and "CPICH RSCP" to include measured quantities of the cell where the connection establishment failure was detected for UTRA FDD;

1> set the "P-CCPCH RSCP" to include measured quantities for the cell where the connection establishment failure was detected for UTRA 1.28 Mcps TDD;

1> set the IE "Logged Measurements Intra Frequency Neighbouring Cells list", "Logged Measurements Inter Frequency list", "Logged Measurements E-UTRA frequency list", "Logged Measurements E-UTRA frequency extension list", in order of decreasing ranking quantity as used for cell re-selection in each frequency for at most the following number of neighbouring cells; 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency per RAT;

1> set the IE "Logged Measurements GSM Neighbouring Cells list" in order of decreasing RXLEV.

NOTE: The UE includes the latest available results of the measurement performed for cell reselection, which are performed in accordance with the regular performance requirements as specified in [19].