Umts routing area update

The procedure is controlled in the MS by timer T When timer T expires, the periodic routing area updating procedure is started.

Start and reset of timer T is described in subclause 4. The routing area identification is broadcast on the broadcast channel s. A normal routing area updating shall abort any ongoing GMM procedure.

Aborted GMM procedures may be repeated after the normal routing area updating procedure has been successfully performed. The value of the update type IE included in the message shall indicate "RA updating". If the normal routing area updating procedure is initiated due to the reception of the paging indication while timer T is running, the "follow-on request pending" indication shall be set to 1.

If timer T is currently running, the MS shall stop timer T In Iu mode, if the MS wishes to prolong the established PS signalling connection after the normal routing area updating procedure for example, the MS has any CM application request pending , it may set a follow-on request pending indicator on see subclause 4. The network may initiate GMM common procedures, e. NOTE 1: The network needs to store the MS network capability and MS Radio Access Capability exactly as received from the MS and network is not allowed to ignore the "higher" octets sent by the MS even if the network does not support any features indicated in the higher octetst.

If the MS and network continue to use the same ciphering mode, ciphering or no ciphering, the ciphering mode is re-established without the need to run an authentication and ciphering procedure. The network may also prolong the PS signalling connection without any indication from the mobile terminal for example, if user plane radio access bearers have been established for the MS.

The network shall not deactivate the PDP contexts for emergency bearer services. The network shall consider the MS to be attached for emergency bearer services only. If only the PDN connection for emergency bearer services remains established, the MS shall consider itself attached for emergency bearer services only.

The mobile station shall store the list, as provided by the network, and further handle the list as follows:. If no list is contained in the message, then the stored list in the mobile station shall be deleted. The list shall be stored in the mobile station while switched off so that it can be used for PLMN selection after switch on.

NOTE 7: In Iu mode, after a routing area updating procedure, the mobile station can initiate Service Request procedure to request the resource reservation for the active PDP contexts if the resources have been released by the network or send upper layer message e.

The mobile equipment shall store the Local Emergency Numbers List, as provided by the network. The received Local Emergency Numbers List shall be provided to the upper layers. The emergency number s received in the Emergency Number List IE are valid only in networks in the same country as the cell on which this IE is received. NOTE 8: The mobile equipment may use the Local Emergency Numbers List to assist the end user in determining whether the dialled number is intended for an emergency service or for another destination, e.

The possible interactions with the end user are implementation specific. The mobile equipment shall be able to store up to ten local emergency numbers received from the network. If the routing area update request is rejected due to general NAS level mobility management congestion control, the network shall set the GMM cause value to 22 "congestion" and assign a back-off timer T NOTE 1: The possibility to configure a MS so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the MS, is out of scope of the present specification.

If the rejected request was not for initiating a PDN connection for emergency bearer services, then. Additionally, the MS shall initiate a normal or combined GPRS attach procedure depending on whether it is in an ongoing circuit-switched transaction. If the MS is in an ongoing circuit-switched transaction, it shall initiate the appropriate MM specific procedure after the circuit-switched transaction has been released.

The MS should also perform the procedures needed in order to activate any previously active multicast service s ; and. If no RR connection exists, the MS shall perform the following additional actions immediately. The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". If no RR connection exists the MS may perform the action immediately.

The MS stays in the current serving cell and applies the normal cell reselection process. The routing area updating procedure is started, if still necessary, when timer T expires or is stopped.

Other cases are considered as abnormal cases and the specification of the mobile station behaviour is given in subclause 4. Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in subclause 4. If the routing area updating request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the MS shall perform the procedures as described in subclause 4.

NOTE 1: This can result in the upper layers requesting establishment of a CS emergency call if not already attempted in the CS domain or other implementation specific mechanisms, e. If the routing area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal case a in subclause 4. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call if not already attempted in the CS domain or other implementation specific mechanisms, e.

If the routing area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal cases b , c or d in subclause 4. NOTE 3: This can result in the upper layers requesting establishment of a CS emergency call if not already attempted in the CS domain or other implementation specific mechanisms, e.

If the routing area updating procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable. The routing area updating procedure shall not be started. The procedure is started as soon as possible and if still necessary, i. If access is barred because of access class control, the upper layers request PS signalling connection, ACDC is applicable to the request and the MS supports ACDC, then the routing area updating procedure shall be started according to subclause 4.

The procedure shall be aborted and the MS shall proceed as described below, except in the following implementation option cases b. The routing area updating procedure shall be initiated again, if the following conditions apply:. PS authentication procedure, see subclause 4. NOTE 1: The RRC connection release cause that triggers the re-initiation of the routing area update procedure is implementation specific.

The procedure is restarted four times, i. The MS shall proceed as described below. This makes sense as in these states the RNC in the access network is aware of the location anyway and can report location changes to the core network when necessary. Only once the mobile goes to idle state and the mobile makes the decision to go to another cell on its own without reporting back, routing and location area updates come into play if the new cell is outside the current area.

In LTE, the corresponding procedure is called a tracking area update. The first difference to the LAU and RAU of UMTS is that the mobile can have a list of several valid tracking areas and an update only has to be made if the new cell is in a tracking area that is not part of that list. So far so good. TS Quite a surprise to me so I wondered why an update is necessary in the connected state!?

Advertise with us. Search this site:. Posted on