Respeto por la propiedad intelectual

If there is no RR connection available when initializing location updating, MM sub-layer of MS will request RR sub-layer to establish RR connection.

MS sends "Location Updating Request" to the network, and start T3210. The information unit of location updating type in this message will indicate the type of this location updating. On this occasion, the network can initialize the type querying procedure (e. g. to get the ciphering capability of MS). If the network cannot obtain the IMSI according to TMSI and LAI, the network can initialize the identification process.

After receiving "Location Updating Request" from MS, the network will initialize the authentication process. If it is necessary to reallocate TMSI, the network will initiate the process of ciphering mode setting.

1) Attempt counter

To restrict the frequency of location updating attempt, the attempt counter is recommended in the specification. It is used to count the number of consecutive unsuccessful location updating. When a location updating failure occurs, the counter will add one. The attempt counter will be reset in the following cases:

z MS powered on.

z SIM inserted.

z Location update successfully completed, and the service statuses switch from Attempting to Update.

z MS roaming into a new location updating area.

z T3212 timeout.

z Location update initiated by CM sub-layer.

Attempt counter is used to decide whether to implement another attempt after T3212 timeout.

2) Location update accepted by the network

If the network accept location updating, it will send "Location Updating Accept" to MS.

When authenticating the validity of security, TMSI reallocation is a part of location updating process. "Location Updating Accept" contains the TMSI allocated for MS and the current LAI. In this case the network will initialize T3250.

If the network needs to prolong the RR connection so that MS can initialize MM connection (e.g. MS sends a request subsequent to "Location Updating Request"), the network will attach "Continue" to "Location Updating Accept" and initiate T3255. After receiving "Location Updating Accept", MS stores LAI, terminates T3210, restarts the attempt counter, and sets the status in SIM as Updated. If what contained in the message is IMSI, MS will delete the corresponding TMSI stored in SIM. If the message contains TMSI, MS will store it in the SIM and send "TMSI Reallocation Complete" to the network. If neither of them can be received, MS will delete the original TMSI stored in SIM. If the LAI or PLMN identifier in "Location Updating Accept" is one of "Barred series", all of original input will be deleted. After that, MS will use "Continue" to direct it action. If this unit exists, and MS has the underway CM service request, it will send "CM Service Request" to the network.

3) Location update denied by the network

If location updating is denied, the network will send "Location Updating Denied" to MS.

After receiving this message, MS will terminate T3210, store the reject cause, activate T3240, enter location denied status and wait for the network to trigger RR connection release.

a) If the reject cause is IMSI unknown to HLR, invalid MS, invalid ME.

MS will set the location updating status as Roaming not Allowed, and store it in SIM.

Delete TMSI, stored LAI and ciphering SN and regard the SIM as an invalid one until MS powered off or SIM removed.

b) If the reject cause is : PLMN not allow, location area not allow, international roaming not allowed in this location area.

allowed in this location area", it will return to MM Idle and then implement PLMN selection instead of cell selection.

Other situations will be treated as abnormal ones.

4) RR connection release after location updating

After location updating, MS will set T3240, enter "wait for network command phase"

and wait for the release of RR connection.

If MS cannot receive RR connection release command from the network within a period of time (controlled by T3240), it will terminate RR connection. No matter RR connection is released by MS or the network, MS will enter "idle status".

5) Abnormality at MS side

a) Access denial controlled by access level, unable to initiate location updating. MS camps on the current serving cell, and implements normal cell reselection. Try to initiate before denial status ends or cell changed.

b) Random access delayed (after receiving Immediate Allocation Denied): unable to initiate location updating. MS stays in the selected cell and initializes normal cell selection. When changing, initialize location updating before T3122 timeout.

c) Random access failed: activate T3213. Activate location updating after it times out.

d) RR connection failure: terminate location-updating process.

e) T3210 timeout: terminate location updating process and RR connection.

f) RR released before normal termination: terminate location-updating process.

g) Location update denied caused by other reasons: MS waits for RR connection release.

For (d) ~ (g) and random access occurring for many times, MS will terminate T3210.

When T3210 times out, RR connection will be canceled, and attempt counter adds 1.

The action afterwards is decided by LAI and the record of the attempt counter:

a) The update status is "Updated", the stored LAI equals to the one received from the previous cell, and the record of attempt counter is four. MS will maintain the "Updated"

status. The MM idle status after RR connection release is "Normal Service". MS stores the type of location updating. After RR connection release, T3211 will be activated.

After T3211 timeout, MS will reinitiate location-updating process (adopting the stored type).

b) If the update status is not "Updated", or the stored LAI is different from the one received from BCCH, or the record in the attempt counter is larger than 4.

After RR connection release, MS will delete LAI, TMSI, ciphering SN in SIM, set the update status as "Not updated", and enter MM idle sub-status "Attempt update". If the

record in attempt counter is smaller than four, T3211 stored in MS will be initiated during RR connection release, otherwise the stored T3212 will be initiated.

6) Abnormality at NSS side a) RR connection failure

If the RR connection failure occurs successively when there is a common program, the network should implement according to the common program description. If RR connection failure occurs successively and there is no common program, the location updating process should be terminated.

b) Protocol error

If protocol error exits in "Location Updating Request", the network should return

"Location Updating Denied". The reject cause is

z Mandatory information unit incorrect

z Information unit not exist or unable to be realized

z Invalid information unit content

z Protocol error, not regulated

When these errors occurs, the network will initialize the process of channel release.

2.1.8 Access