## 4.1 General

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

This sub-clause describes the procedures used for mobility management for non-GPRS services and for GPRS-services at the radio interface (Reference Point Um).

The main function of the Mobility Management sublayer is to support the mobility of user terminals, such as informing the network of its present location and providing user identity confidentiality.

A further function of the MM sublayer is to provide connection management services to the different entities of the upper Connection Management (CM) sublayer (see 3GPP TS 04.07).

There are two sets of procedures defined in this chapter:

– MM procedures for non-GPRS services (performed by the MM entity of the MM sublayer); and

– GMM procedures for GPRS services (performed by the GMM entity and GMM-AA entity of the MM sublayer), see 3GPP TS 04.07 [20].

All the MM procedures described in this sub-clause can only be performed if a RR connection has been established between the MS and the network. Else, the MM sublayer has to initiate the establishment of a RR connection according to the procedures specified in sub-clause 3.3. The GMM procedures described in this sub-clause, use services provided by the RR sublayer without prior RR connection establishment.

GMM procedures are mandatory and applicable only for GPRS MSs and networks supporting those MSs. For GPRS MSs which are IMSI attached for both GPRS and non-GPRS services, some MM procedures are replaced by GMM combined procedures provided that the network operates in network operation mode I, i.e. is supporting combined GMM procedures. GMM combined procedures are not applicable for the GPRS MS operation mode C but are mandatory for the GPRS MS operation modes A and B and networks supporting network operation mode I, see 3GPP TS 03.60.

### 4.1.1 MM and GMM procedures

#### 4.1.1.1 Types of MM and GMM procedures

Depending on how they can be initiated, three types of MM procedures can be distinguished:

1) MM common procedures:

A MM common procedure can always be initiated whilst a RR connection exists. The procedures belonging to this type are:

Initiated by the network:

– TMSI reallocation procedure;

– authentication procedure;

– identification procedure;

– MM information procedure;

– abort procedure.

However, abort procedure is used only if an MM connection is being established or has already been established i.e. not during MM specific procedures or during IMSI detach procedure, see sub-clause 4.3.5.

Initiated by the mobile station:

– IMSI detach procedure (with the exceptions specified in sub-clause 4.3.4).

ii) MM specific procedures:

A MM specific procedure can only be initiated if no other MM specific procedure is running or no MM connection exists. The procedures belonging to this type are:

– normal location updating procedure;

– periodic updating procedure;

– IMSI attach procedure.

iii) MM connection management procedures:

These procedures are used to establish, maintain and release a MM connection between the mobile station and the network, over which an entity of the upper CM layer can exchange information with its peer. A MM connection establishment can only be performed if no MM specific procedure is running. More than one MM connection may be active at the same time. Depending on how they can be initiated, two types of GMM procedures can be distinguished:

i) GMM common procedures:

Initiated by the network when a GMM context has been established:

– P-TMSI (re-) allocation;

– GPRS authentication and ciphering;

– GPRS identification;

– GPRS information.

ii) GMM specific procedures:

Initiated by the network and used to detach the IMSI in the network for GPRS services and/or non-GPRS services and to release a GMM context:

– GPRS detach.

Initiated by the MS and used to attach or detach the IMSI in the network for GPRS services and/or non-GPRS services and to establish or release a GMM context:

– GPRS attach and combined GPRS attach;

– GPRS detach and combined GPRS detach.

Initiated by the MS when a GMM context has been established:

– normal routing area updating and combined routing area updating;

– periodic routing area updating.

#### 4.1.1.2 MM-GMM co-ordination for GPRS MS’s

##### 4.1.1.2.1 GPRS MS operating in mode A or B in a network that operates in mode I

If the network operates in mode I, GPRS MSs that operate in mode A or B and wish to be or are simultaneously IMSI attached for GPRS and non-GPRS services, shall use the combined GPRS attach and the combined and periodic routing area updating procedures instead of the corresponding MM specific procedures IMSI attach and normal and periodic location area updating.

NOTE 1: A GPRS MS operating in mode A or B in a network that operates in mode I, shall perform the combined GPRS attach or routing area update procedure regardless the value of the ATT flag.

If a GPRS MS is operating in mode A or B in a network that operates in mode I the IMSI detach shall be performed by the GMM using the combined GPRS detach procedure.

NOTE 2: A GPRS MS operating in mode A or B in a network that operates in mode I, shall perform the combined GPRS detach procedure regardless the value of the ATT flag.

A GPRS MS operating in mode A or B in network that operates in mode I, uses the combined GMM specific procedures in place of the MM specific procedures, so all conditions describing when to trigger a MM specific procedure listed in sub-clauses 4.3 and 4.4 shall not apply.

A GPRS MS operating in mode A or B in a network that operates in mode I should not use any MM timers relating to MM specific procedures, (e.g T3210, T3211, T3212, T3213) except in some error and abnormal cases. If the MM timers are already running, the MS should not react on the expiration of the timers.

NOTE 3: Whenever GMM performs a combined GMM procedure, a GPRS MS enters the MM state MM LOCATION UPDATING PENDING in order to prevent the MM to perform a location update procedure.

If the authentication procedure is performed by MM and the authentication is rejected by the network (i.e upon receive of AUTHENTICATION REJECT), the MS shall in addition set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall, if available, delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number stored. The SIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED.

##### 4.1.1.2.2 GPRS MS operating in mode A or B in a network that operates in mode II or III

If the network operates in mode II or III, a GPRS MSs that operate in mode A or B and wish to be or are simultaneously IMSI attached for GPRS and non-GPRS services, shall use the MM specific procedures listed in sub-clauses 4.3 and 4.4 and the GMM specific procedures listed in sub-clauses 4.7.3, 4.7.4 and 4.7.5. The applicability of periodic location updating is further specified in sub-clause 4.4.2 and the periodic routing area updating is specified in sub-clause 4.7.2.2.

If the authentication procedure is performed by MM and the authentication is rejected by the network (i.e upon receive of AUTHENTICATION REJECT), the MS shall in addition set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall, if available, delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number stored. The SIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED.

### 4.1.2 MM sublayer states

The description of the states for the MM sublayer is organized as follows. The main states for the MS side, related to the procedures, are described in sub-clause 4.1.2.1.1. The MM IDLE state is subdivided in substates for the description of the behaviour in idle mode (sub-clause 4.1.2.1.2). This behaviour depends on an update status, described in 4.1.2.2. The states for the network side are described in 4.1.2.3.

#### 4.1.2.1 MM sublayer states in the mobile station

In this sub-clause, the possible states for the MM sublayer in the mobile station is described. In figure 4.1/3GPP TS 04.08 an overview of the MM sublayer protocol is given.

##### 4.1.2.1.1 Main states

0 NULL

The mobile station is inactive (e.g. power down). Important parameters are stored. Only manual action by the user may transfer the MM sublayer to another state.

3 LOCATION UPDATING INITIATED

A location updating procedure has been started and the MM awaits a response from the network. The timer T3210 is running.

5 WAIT FOR OUTGOING MM CONNECTION

The MM connection establishment has been started, and the MM awaits a response from the network. The timer T3230 is running.

6 MM CONNECTION ACTIVE

The MM sublayer has a RR connection to its peer entity on the network side. One or more MM connections are active.

7 IMSI DETACH INITIATED

The IMSI detach procedure has been started. The timer T3220 is running.

8 PROCESS CM SERVICE PROMPT

The MM sublayer has a RR connection to its peer entity on the network side. The Mobile Station has received a CM SERVICE PROMPT message but has not yet responded $(CCBS)$.

9 WAIT FOR NETWORK COMMAND

The MM sublayer has a RR connection to its peer entity in the network, but no MM connection is established. The mobile station is passive, awaiting further commands from the network. The timer T3240 may be running.

10 LOCATION UPDATE REJECTED

A location updating procedure has been rejected and RR connection release is awaited. The timer T3240 is running.

Figure 4.1a / 3GPP TS 04.08: Overview mobility management protocol / MS Side

Additions to Figure 4.1.a/3GPP TS 04.08

13. WAIT FOR RR CONNECTION (LOCATION UPDATING)

The MM sublayer has requested RR connection establishment for starting the location updating procedure.

14. WAIT FOR RR CONNECTION (MM CONNECTION)

The MM sublayer has requested RR connection establishment for dedicated mode for starting the MM connection establishment.

15. WAIT FOR RR CONNECTION (IMSI DETACH)

The MM sublayer has requested RR connection establishment for starting the IMSI detach procedure.

17. WAIT FOR REESTABLISH

A lower layer failure has occurred and re-establishment may be performed from the disturbed CM layer entities.

18. WAIT FOR RR ACTIVE

The MM sublayer has requested activation of the RR sublayer.

19. MM IDLE

There is no MM procedure running and no RR connection exists except that a local MM context may exist when the RR sublayer is in Group Receive mode. This is a compound state, and the actual behaviour of the mobile station to Connection Management requests is determined by the actual substate as described hereafter.

20. WAIT FOR ADDITIONAL OUTGOING MM CONNECTION.

The MM connection establishment for an additional MM connection has been started, and the MM awaits response from the network.

21. MM CONNECTION ACTIVE (GROUP TRANSMIT MODE)

(Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has a RR connection on the VGCS channel to its peer entity on the network side. Only one MM connection is active.

22. WAIT FOR RR CONNECTION (GROUP TRANSMIT MODE)

(Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has requested to perform an uplink access on the VGCS channel.

23. LOCATION UPDATING PENDING

(Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) A location updating has been started using the combined GPRS routing area updating procedure.

24. IMSI DETACH PENDING

(Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) An IMSI detach for non-GPRS services has been started using the combined GPRS detach procedure at not switching off.

25. RR CONNECTION RELEASE NOT ALLOWED

(Only applicable for mobile stations supporting RRLP procedures). All MM connections are released by their CM entities, but the RR connection is maintained by the network due to an ongoing RRLP procedure (see 3GPP TS 04.31 [23b]).

##### 4.1.2.1.2 Substates of the MM IDLE state

For the description of the behaviour of the MS the MM IDLE state is subdivided in several substates, also called the service states. The service state pertains to the whole MS (ME alone if no SIM is inserted, or ME plus SIM.). The service state depends on the update status (see sub-clause 4.1.2.2) and on the selected cell.

19.1 NORMAL SERVICE

Valid subscriber data are available, update status is U1, a cell is selected that belongs to the LA where the subscriber is registered.

In this state, all requests from the CM layers are treated normally.

19.2 ATTEMPTING TO UPDATE

Valid subscriber data are available, update status is U2 and a cell is selected. Requests from upper layers are accepted. Emergency call requests are treated normally, otherwise the request triggers first a location updating attempt in the selected cell, and then triggers the needed procedure only in case of successful location updating, otherwise the request is rejected.

19.3 LIMITED SERVICE

Valid subscriber data are available, update status is U3, and a cell is selected, which is known not to be able to provide normal service. Only emergency services are offered.

19.4 NO IMSI

No valid subscriber data (no SIM, or the SIM is not considered valid by the ME), and a cell is selected. Only emergency services are offered.

19.5 NO CELL AVAILABLE

No cell can be selected. This state is entered after a first intensive search failed (state 19.7). Cells are searched at a low rhythm. No services are offered.

19.6 LOCATION UPDATE NEEDED

Valid subscriber data are available, and for some reason a location updating must be done as soon as possible (for instance update status is U1 but the selected cell is not in the registered LA, or the timer has expired, …). This state is usually of no duration, but can last, e.g., in the case of access class blocking.

19.7 PLMN SEARCH

The mobile station is searching for PLMNs, and the conditions for state 19.8 are not met. This state is ended when either a cell is selected (the new state is 19.1, 19.3 or 19.6), or when it is concluded that no cell is available for the moment (the new state is 19.5).

19.8 PLMN SEARCH, NORMAL SERVICE

Valid subscriber data are available, update status is U1, a cell is selected which belongs to the LA where the subscriber is registered, and the mobile station is searching for PLMNs. This state is ended when either a cell is selected (the new state is 19.1, 19.3 or 19.6), or when it is concluded that no cell is available for the moment (the new state is 19.5).

19.9 RECEIVING GROUP CALL (NORMAL SERVICE)

Only applicable for mobile stations supporting VGCS listening or VBS listening. Valid subscriber data are available, update status is U1, a VGCS channel or VBS channel is received in a cell that belongs to the LA where the subscriber is registered.

In this state, only requests from the GCC or BCC layers are treated.

19.10 RECEIVING GROUP CALL (LIMITED SERVICE)

Only applicable for mobile stations supporting VGCS listening or VBS listening. Valid subscriber data are available, update status is U3, a VGCS channel or VBS channel is received in a cell which is known not to be able to provide normal service.

In this state, only requests from the GCC or BCC layers for the reception of VGCS or VBS calls are treated and group call emergency services are offered.

#### 4.1.2.2 The update Status

In parallel with the sublayer states described in sub-clause 4.1.2.1 and which control the MM sublayer protocol, an update status exists.

The update status pertains to a specific subscriber embodied by a SIM. This status is defined even when the subscriber is not activated (SIM removed or connected to a switched-off ME). It is stored in a non volatile memory in the SIM. The update status is changed only as a result of a location updating procedure attempt (with the exception of an authentication failure and of some cases of CM service rejection). In some cases, the update status is changed as a result of a GPRS attach, GPRS routing area update, or network initiated GPRS detach procedure.

U1 UPDATED

The last location updating attempt was successful (correct procedure outcome, and the answer was acceptance from the network). With this status, the SIM contains also the LAI of the LA where the subscriber is registered, and possibly valid TMSI, ciphering key and ciphering key sequence number. The "Location update status" stored on the SIM shall be "updated".

U2 NOT UPDATED

The last location updating attempt made failed procedurally (no significant answer was received from the network, including the cases of failures or congestion inside the network).

For this status, the SIM does not contain any valid LAI, TMSI, ciphering key or ciphering key sequence number. For compatibility reasons, all these fields must be set to the "deleted" value at the moment the status is set to NOT UPDATED. However the presence of other values shall not be considered an error by the mobile station. The "Location update status" stored on the SIM shall be "not updated".

U3 ROAMING NOT ALLOWED

The last location updating attempt run correctly, but the answer from the network was negative (because of roaming or subscription restrictions).

For this status, the SIM does not contain any valid LAI, TMSI, ciphering key or ciphering key sequence number. For compatibility reasons, all these fields must be set to the "deleted" value at the moment the status is set to ROAMING NOT ALLOWED. However the presence of other values shall not be considered an error by the mobile station. The "Location update status" stored on the SIM shall be "Location Area not allowed".

#### 4.1.2.3 MM sublayer states on the network side

1. IDLE

The MM sublayer is not active except possibly when the RR sublayer is in Group Receive mode.

2. WAIT FOR RR CONNECTION

The MM sublayer has received a request for MM connection establishment from the CM layer. A RR connection to the mobile station is requested from the RR sublayer (i.e. paging is performed).

3. MM CONNECTION ACTIVE

The MM sublayer has a RR connection to a mobile station. One or more MM connections are active, or no MM connection is active but an RRLP procedure is ongoing.

4. IDENTIFICATION INITIATED

The identification procedure has been started by the network. The timer T3270 is running.

5. AUTHENTICATION INITIATED

The authentication procedure has been started by the network. The timer T3260 is running.

6. TMSI REALLOCATION INITIATED

The TMSI reallocation procedure has been started by the network. The timer T3250 is running.

7. CIPHERING MODE INITIATED

The cipher mode setting procedure has been requested to the RR sublayer.

8a. WAIT FOR MOBILE ORIGINATED MM CONNECTION

A CM SERVICE REQUEST message is received and processed, and the MM sublayer awaits the "opening message" of the MM connection.

8b. WAIT FOR NETWORK ORIGINATED MM CONNECTION

A CM SERVICE PROMPT message has been sent by the network and the MM sublayer awaits the "opening message" of the MM connection $(CCBS)$.

9. WAIT FOR REESTABLISHMENT

The RR connection to a mobile station with one or more active MM connection has been lost. The network awaits a possible re-establishment request from the mobile station.

10. WAIT OF A GROUP CALL

Only applicable in case for mobile station supporting VGCS talking. The MM sublayer has received a request for establishing a VGCS from the GCC sublayer. The request for establishing a VGCS channels is given to the RR sublayer.

11. GROUP CALL ACTIVE

Only applicable in case of mobile station supporting VGCS talking. A VGCS channel is established by the RR sublayer. An RR connection to the talking mobile station can be established by the RR sublayer on the VGCS channel. The MM sublayer is active but no sending of MM message between the network and the mobile station has occurred.

12. MM CONNECTION ACTIVE (GROUP CALL)

Only applicable in case of mobile station supporting VGCS talking. The MM sublayer has a RR connection to the talking mobile station on the VGCS channel. Only one MM connection is active.

Only applicable in case of VBS. The MM sublayer has received a request for a VBS establishment from the BCC sublayer. The request for establishment of VBS channels is given to the RR sublayer.

Only applicable in case of VBS. A VBS channel is established by the RR sublayer. The MM sublayer is active but no explicit MM establishment between the Network and the mobile station has occurred.

### 4.1.3 GPRS mobility management (GMM) sublayer states

In this sub-clause, the GMM protocol of the MS and the network are described by means of two different state machines. In sub-clause 4.1.3.1, the states of the GMM entity in the MS are introduced. The behaviour of the MS depends on a GPRS update status that is described in sub-clause 4.1.3.2. The states for the network side are described in sub-clause 4.1.3.3.

#### 4.1.3.1 GMM states in the MS

In this sub-clause, the possible GMM states are described of a GMM entity in the mobile station. sub-clause 4.1.3.1.1 summarises the main states of a GMM entity, see figure 4.1b/3GPP TS 04.08. The substates that have been defined are described in sub-clause 4.1.3.1.2 and sub-clause 4.1.3.1.3.

However, it should be noted that this sub-clause does not include a description of the detailed behaviour of the MS in the single states and does not cover abnormal cases. Thus, figure 4.1b/3GPP TS 04.08 is rather intended to give an overview of the state transitions than to be a complete state transition diagram. A detailed description of the behaviour of the MS is given in sub-clause 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred to sub-clause 4.7.

##### 4.1.3.1.1 Main states
###### 4.1.3.1.1.1 GMM-NULL

The GPRS capability is disabled in the MS. No GPRS mobility management function shall be performed in this state.

###### 4.1.3.1.1.2 GMM-DEREGISTERED

The GPRS capability has been enabled in the MS, but no GMM context has been established. In this state, the MS may establish a GMM context by starting the GPRS attach or combined GPRS attach procedure.

###### 4.1.3.1.1.3 GMM-REGISTERED-INITIATED

A GPRS attach or combined GPRS attach procedure has been started and the MS is awaiting a response from the network.

###### 4.1.3.1.1.4 GMM-REGISTERED

A GMM context has been established, i.e. the GPRS attach or combined GPRS attach procedure has been successfully performed. In this state, the MS may activate PDP contexts, may send and receive user data and signalling information and may reply to a page request. Furthermore, cell and routing area updating are performed.

###### 4.1.3.1.1.5 GMM-DEREGISTERED-INITIATED

The MS has requested release of the GMM context by starting the GPRS detach or combined GPRS detach procedure. This state is only entered if the MS is not being switched off at detach request.

4.1.3.1.1.6 GMM-ROUTING-AREA-UPDATING-INITIATED

A routing area updating procedure has been started and the MS is awaiting a response from the network.

4.1.3.1.2 Substates of state GMM-DEREGISTERED

The GMM-DEREGISTERED state is subdivided into several substates as explained below. The substates pertain to the whole MS (ME alone if no SIM is inserted, or ME plus SIM). The selection of the appropriate substate depends on the GPRS update status, see sub-clause 4.1.3.2, and on the selected cell.

4.1.3.1.2.1 GMM-DEREGISTERED.NORMAL-SERVICE

Valid subscriber data is available, the GPRS update status is GU1 or GU2, a cell has been selected. In this state, a request for GPRS attach is performed using the stored temporary mobile subscriber identity for GPRS (P-TMSI), routing area identification (RAI) and GPRS ciphering key sequence number in case of GU1. If the GPRS update status is GU2, the IMSI shall be used to attach for GPRS services.

4.1.3.1.2.2 GMM-DEREGISTERED.LIMITED-SERVICE

Valid subscriber data is available, GPRS update status is GU3, and a cell is selected, which is known not to be able to provide normal service.

4.1.3.1.2.3 GMM-DEREGISTERED.ATTACH-NEEDED

Valid subscriber data is available and for some reason a GPRS attach must be performed as soon as possible. This state is usually of no duration, but can last, e.g. if the access class is blocked.

4.1.3.1.2.4 GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH

The GPRS update status is GU2, a cell is selected, a previous GPRS attach was rejected. The execution of further attach procedures depends on the GPRS attach attempt counter. No GMM procedure except GPRS attach shall be initiated by the MS in this substate.

###### 4.1.3.1.2.5 GMM-DEREGISTERED.NO-IMSI

No valid subscriber data is available (no SIM, or the SIM is not considered valid by the ME) and a cell has been selected.

###### 4.1.3.1.2.6 GMM-DEREGISTERED.NO-CELL-AVAILABLE

No cell can be selected. This substate is entered after a first intensive search failed (substate PLMN SEARCH). Cells are searched for at a low rhythm. No services are offered.

###### 4.1.3.1.2.7 GMM-DEREGISTERED.PLMN-SEARCH

The mobile station is searching for PLMNs. This substate is left either when a cell has been selected (the new substate is NORMAL-SERVICE or LIMITED-SERVICE) or when it has been concluded that no cell is available at the moment (the new substate is NO-CELL-AVAILABLE).

###### 4.1.3.1.2.8 GMM-DEREGISTERED.SUSPENDED

The MS shall enter this substate when entering dedicated mode and the MS limitations make it unable to communicate on GPRS channels. The MS shall leave this substate when leaving dedicated mode.

##### 4.1.3.1.3 Substates of state GMM-REGISTERED

The state GMM-REGISTERED is subdivided into several substate as explained below. The substates pertain to the whole MS (ME alone if no SIM is inserted, or ME plus SIM.).

###### 4.1.3.1.3.1 GMM-REGISTERED.NORMAL-SERVICE

User data and signalling information may be sent and received.

###### 4.1.3.1.3.2 GMM-REGISTERED.SUSPENDED

The MS shall enter this substate when entering dedicated mode and when the MS limitations makes it unable to communicate on GPRS channels… In this substate, no user data should be sent and no signalling information shall be sent. The MS shall leave this substate when leaving dedicated mode.

###### 4.1.3.1.3.3 GMM-REGISTERED.UPDATE-NEEDED

The MS has to perform a routing area updating procedure, but its access class is not allowed in the cell. The procedure will be initiated as soon as access is granted (this might be due to a cell-reselection or due to change of the access class of the current cell). No GMM procedure except routing area updating shall be initiated by the MS in this substate. In this substate, no user data and no signalling information shall be sent.

###### 4.1.3.1.3.4 GMM-REGISTERED.ATTEMPTING-TO-UPDATE

A routing area updating procedure failed due to a missing response from the network. The MS retries the procedure controlled by timers and a GPRS attempt counter. No GMM procedure except routing area updating shall be initiated by the MS in this substate. No data shall be sent or received.

###### 4.1.3.1.3.5 GMM-REGISTERED.NO-CELL-AVAILABLE

GPRS coverage has been lost. In this substate, the MS shall not initiate any GMM procedures except of cell (and PLMN) reselection.

Figure 4.1b/3GPP TS 04.08: GMM main states in the MS

4.1.3.1.3.6 GMM-REGISTERED.LIMITED-SERVICE

A cell is selected, which is known not to be able to provide normal service. The MS will remain in this sub-state until a cell is selected which is able to provide normal service.

###### 4.1.3.1.3.7 GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM

A combined routing area updating procedure or a combined GPRS attach procedure was successful for GPRS services only. The MS retries the procedure controlled by timers and a GPRS attempt counter. User data and signalling information may be sent and received.

###### 4.1.3.1.3.8 GMM-REGISTERED.IMSI-DETACH-INITIATED

The MS performs a combined GPRS detach procedure for non-GPRS services only (detach type "IMSI Detach"). This state is entered if the MS is attached for GPRS and non-GPRS services in a network that operates in network mode I and wants to detach for non-GPRS services only. User data and signalling information may be sent and received.

#### 4.1.3.2 GPRS update status

In addition to the GMM sublayer states described so far, a GPRS update status exists.

The GPRS update status pertains to a specific subscriber embodied by a SIM. This status is defined even when the subscriber is not activated (SIM removed or connected to a switched off ME). It is stored in a non volatile memory in the SIM. The GPRS update status is changed only after execution of a GPRS attach, network initiated GPRS detach, authentication procedure, or routing area updating procedure.

GU1: UPDATED

The last GPRS attach or routing area updating attempt was successful (correct procedure outcome, and the answer was accepted by the network). The SIM contains the RAI of the routing area (RA) to which the subscriber was attached, and possibly a valid P-TMSI, GPRS ciphering key and GPRS ciphering key sequence number.

GU2: NOT UPDATED

The last GPRS attach or routing area updating attempt failed procedurally, i.e. no response was received from the network. This includes the cases of failures or congestion inside the network.

In this case, the SIM may contain the RAI of the routing area (RA) to which the subscriber was attached, and possibly also a valid P-TMSI, GPRS ciphering key and GPRS ciphering key sequence number. For compatibility reasons, all these fields shall be set to the "deleted" value if the RAI is deleted. However, the presence of other values shall not be considered an error by the MS.

GU3: ROAMING NOT ALLOWED

The last GPRS attach or routing area updating attempt was correctly performed, but the answer from the network was negative (because of roaming or subscription restrictions).

For this status, the SIM does not contain any valid RAI, P-TMSI, GPRS ciphering key or GPRS ciphering key sequence number. For compatibility reasons, all these fields must be set to the value "deleted" at the moment the status is set to ROAMING NOT ALLOWED. However, the presence of other values shall not be considered an error by the MS.

#### 4.1.3.3 GMM mobility management states on the network side

In this sub-clause, the possible states are described for the GMM on the network side. sub-clause 4.1.3.3.1 summarises the main states. The corresponding substates are described in sub-clause 4.1.3.3.2.

However, it should be noted that this sub-clause does not include a description of the detailed behaviour of the network in the single states and does not cover abnormal cases. Thus, figure 4.1c/3GPP TS 04.08 is rather intended to give an overview of the state transitions than to be a complete state transition diagram. A detailed description of the behaviour of the MS is given in sub-clause 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred to sub-clause 4.7.

##### 4.1.3.3.1 Main States
###### 4.1.3.3.1.1 GMM-DEREGISTERED

The network has no GMM context or the GMM context is marked as detached, the MS is detached. In this state, the network may answer to a GPRS attach or combined GPRS attach procedure initiated by the MS.

###### 4.1.3.3.1.2 GMM-COMMON-PROCEDURE-INITIATED

A common GMM procedure, as defined in sub-clause 4.1.1, has been started. The network is awaiting the answer from the MS.

###### 4.1.3.3.1.3 GMM-REGISTERED

The GMM context has been established and the GPRS attach procedure has been successfully performed.

###### 4.1.3.3.1.4 GMM-DEREGISTERED-INITIATED

The network has started a GPRS detach procedure and is awaiting the answer from the MS.

Figure 4.1c/3GPP TS 04.08: GMM main states on the network side

##### 4.1.3.3.2 Substates of state GMM-REGISTERED

The state GMM-REGISTERED is subdivided into two substates as explained below.

###### 4.1.3.3.2.1 GMM-REGISTERED.NORMAL-SERVICE

User data and signalling information may be sent and received.

###### 4.1.3.3.2.2 GMM-REGISTERED.SUSPENDED

In this substate, the lower layers shall be prevented of sending user data or signalling information.