8.3.3 UTRAN mobility information

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

Figure 8.3.3-1: UTRAN mobility information procedure, normal flow

Figure 8.3.3-2: UTRAN mobility information procedure, failure case

8.3.3.1 General

The purpose of this procedure is to allocate any one or a combination of the following to a UE in connected mode:

– a new C-RNTI;

– a new U-RNTI;

– a new H-RNTI (FDD, CELL_FACH state and 1.28 Mcps TDD only);

– a new E-RNTI (FDD, CELL_FACH state and 1.28 Mcps TDD only);

– other mobility related information;

– DSAC and/or PPAC related information.

8.3.3.2 Initiation

To initiate the procedure UTRAN transmits a UTRAN MOBILITY INFORMATION message to the UE on the downlink DCCH using AM or UM RLC. In case of SRNS relocation, the message is sent using UM RLC only.

8.3.3.3 Reception of UTRAN MOBILITY INFORMATION message by the UE

When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:

1> act on received information elements as specified in subclause 8.6;

1> if the IE "Dedicated Priority Information" is present:

2> act upon the received IE as described in subclause 8.6.7.23.

1> if the IE "Measurement Release Enhancement" is present:

2> if the IE "Measurement Release Enhancement" is set to "Release some measurements", for each measurement indicated by IE "Measurement Identity" in the "Released measurements" list, the UE shall:

3> terminate the corresponding measurement;

3> clear corresponding measurement control information stored in variable MEASUREMENT_IDENTITY.

2> else:

3> terminate all measurements;

3> clear all stored measurement control information in variable MEASUREMENT_IDENTITY.

1> if the IE "UE Timers and constants in connected mode" is present:

2> store the values of the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS, replacing any previously stored value for each timer and constant; and

2> if the IE "T323" is not present:

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

2> for each updated timer value:

3> start using the new value next time the timer is started;

NOTE: If a new value of timer T305 is included in the IE "UE Timers and constants in connected mode", and the old value of timer T305 is "infinity", the new value may not be used immediately.

2> for each updated constant value:

3> start using the new value directly;

1> if the IE "CN domain specific DRX cycle length coefficient" is present:

2> store the value of the IE "CN domain specific DRX cycle length coefficient" for that CN domain, replacing any previously stored value; and

2> use the value to determine the connected mode paging occasions according to [4].

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

1> clear that entry;

1> if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info" or contained the IE "Integrity protection mode info":

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

1> if the variable PDCP_SN_INFO is non-empty:

2> include the IE "RB with PDCP information list" in the UTRAN MOBILITY INFORMATION CONFIRM message and set it to the value of the variable PDCP_SN_INFO.

1> if the received UTRAN MOBILITY INFORMATION message included the IE "Downlink counter synchronisation info":

2> if the variable PDCP_SN_INFO is empty:

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

2> else:

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

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

2> re-establish the RLC entity for RB2;

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

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

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

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

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

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

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

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

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

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

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

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

3> else:

4> continue using the current ciphering configuration.

2> set the new uplink and downlink HFN component of 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 component 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" in the UTRAN MOBILITY INFORMATION CONFIRM message.

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> 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 the UE is in 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> if the UE is in CELL_DCH state:

2> if the received UTRAN MOBILITY INFORMATION message included the IE "Domain Specific Access Restriction Parameters Update":

3> for the variable "DSAC_PARAM_2":

4> if the variable "DSAC_PARAM_2" is not set, the UE shall:

5> store that Domain Specific Access Restriction Parameters to the variable "DSAC_PARAM_2" and maintain the variable until it is cleared or the PLMN is changed.

4> else (DSAC_PARAM_2 is stored), the UE shall:

5> update the variable "DSAC_PARAM_2" with that Domain Specific Access Restriction Parameters.

2> if the received UTRAN MOBILITY INFORMATION message included the IE "Paging Permission with Access Control Parameters Update":

3> for the variable "PPAC_PARAM_2":

4> if the variable "PPAC_PARAM_2" is not set, the UE shall:

5> store that Paging Permission with Access Control Parameters to the variable "PPAC_PARAM_2" and maintain the variable until it is cleared or the PLMN is changed.

4> else (PPAC_PARAM_2 is stored) UE shall:

5> update the variable "PPAC_PARAM_2" with that Paging Permission with Access Control Parameters.

2> the UE shall:

3> if the variable "DSAC_PARAM_2" is set:

4> if the variable "PPAC_PARAM_2" is set:

5> act on the stored IE "Paging Response Restriction Indication" when sending a response to any PAGING TYPE 2 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specifed in [79];

5> act on the stored IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "CS", when initiating a Location/Registration procedure to the CS domain, as specified in [4];

5> act on the stored IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "PS", when initiating a Location/Registration procedure to the PS domain, as specified in [4];

5> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS domain for any other reason, as specified in [4];

5> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, for any other reason ,as specified in [4].

4> if the variable "PPAC_PARAM_2" is not set:

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

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

3> else:

4> act as if no DSAC/PPAC restriction applies.

1> transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC;

1> if the IE "Integrity protection mode info" was present in the UTRAN MOBILITY INFORMATION message:

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

1> if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY INFORMATION message:

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

3> if the variable PDCP_SN_INFO is empty:

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

3> else:

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

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

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

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

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

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

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

2> if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info":

3> when RLC has confirmed the successful transmission of the UTRAN MOBILITY INFORMATION CONFIRM message:

4> perform the actions below:

2> if the UTRAN MOBILITY INFORMATION message did not contain the IE "Ciphering mode info":

3> when RLC has been requested to transmit the UTRAN MOBILITY INFORMATION CONFIRM 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 UTRAN MOBILITY INFORMATION CONFIRM 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> clear the variable PDCP_SN_INFO; and

3> perform the actions below.

The UE shall:

1> if the UTRAN MOBILITY INFORMATION 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 UTRAN MOBILITY INFORMATION 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 the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and

2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.

1> clear the variable SECURITY_MODIFICATION.

The procedure ends.

8.3.3.4 Reception of an UTRAN MOBILITY INFORMATION CONFIRM message by the UTRAN

When the network receives UTRAN MOBILITY INFORMATION CONFIRM message, UTRAN may delete any old U-RNTI. The procedure ends.

8.3.3.5 Cell re-selection

If the UE performs cell re-selection, the UE shall:

1> initiate a cell update procedure according to subclause 8.3.1;

1> if the UTRAN MOBILITY INFORMATION message contains the IE "New C-RNTI"; and

1> if the UE has not yet submitted the UTRAN MOBILITY INFORMATION CONFIRM message to lower layers for transmission; and

1> if the IE "Downlink counter synchronisation info" was not included in the received UTRAN MOBILITY INFORMATION message:

2> transmit a UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC;

2> set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION FAILURE message to the value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION 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 "cell update occurred";

2> when the UTRAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for transmission:

3> continue with any ongoing processes and procedures as if the invalid UTRAN MOBILITY INFORMATION message has not been received and the procedure ends.

1> otherwise:

2> if a UTRAN MOBILITY INFORMATION message was received and caused the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE; and

2> if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY INFORMATION message:

3> apply the new security (integrity protection) configuration received in the UTRAN MOBILITY INFORMATION message on the CELL UPDATE message to be transmitted.

2> continue the procedure normally.

8.3.3.5a Incompatible simultaneous security reconfiguration

If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION becomes set to TRUE of the received UTRAN MOBILITY INFORMATION message, the UE shall:

1> transmit a UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC;

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

1> clear that entry;

1> set the IE "failure cause" to the cause value "incompatible simultaneous reconfiguration";

1> when the UTRAN MOBILITY INFORMATION FAILURE message has been delivered to lower layers for transmission:

2> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to FALSE;

2> continue with any ongoing processes and procedures as if the UTRAN MOBILITY INFORMATION message has not been received;

2> and the procedure ends.

8.3.3.6 Invalid UTRAN MOBILITY INFORMATION message

If the UTRAN MOBILITY INFORMATION 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 UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC;

1> set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION FAILURE message to the value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION message in the table "Rejected transactions" in the variable TRANSACTIONS, and;

1> clear that entry.

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

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

1> when the UTRAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for transmission:

2> continue with any ongoing processes and procedures as if the invalid UTRAN MOBILITY INFORMATION message has not been received;

2> and the procedure ends.

8.3.3.7 T322 expiry

Upon expiry of timer T322 the UE shall:

1> clear the stored IE "Dedicated Priority Information";

1> clear the variable PRIORITY_INFO_LIST;

1> set the value of IE "Priority status" in the variable PRIORITY_INFO_LIST to "sys_info_priority";

1> if the UE is not in CELL_DCH state:

2> take the actions as described in subclause 8.1.1.6.19 using stored System information Block type 19.