Section: 4.7.13.3 Service request procedure accepted by the network
Content: If the SERVICE REQUEST message was sent in PMM-IDLE mode, the indication from the lower layers that the security mode control procedure is completed shall be treated as a successful completion of the procedure. The service request attempt counter shall be reset, timer T3317 shall be stopped, and the MS enters GMM-REGISTERED state and PMM-CONNECTED mode. If the SERVICE REQUEST message was sent in PMM-CONNECTED mode, then the reception of the SERVICE ACCEPT message shall be treated as a successful completion of the procedure. The timer T3317 shall be stopped and the MS remains in PMM-CONNECTED mode. Upon reception of the SERVICE REQUEST message, if the EMM Combined UE Waiting Flag is 'true', the SGSN shall complete the procedure and perform a detach procedure for non-GPRS services only as described in subclause 4.7.4.2. If the SERVICE REQUEST message was sent in a CSG cell and the CSG subscription has expired or was removed for a MS, but the MS has a PDN connection for emergency bearer services established, the network shall accept the SERVICE REQUEST message and deactivate all non-emergency PDP contexts by initiating PDP context deactivation procedure. The PDP contexts for emergency services shall not be deactivated. At successful completion of a service request procedure with Service type "data", the MS shall start timer T3319. The timer T3319 shall be stopped when the MS returns to PMM-IDLE mode or when the network releases the radio access bearer of any active PDP context. The MS shall not issue another Service Request with service type "data" while timer T3319 is running unless the Service request is being generated from a PDP context for which the flag in the Uplink data status IE has not been set in the last Service Request. The network may indicate a value for timer T3319 in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT messages. The last provided value of T3319 shall be used by the MS. If the information element T3319 value is not included in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT messages, the default value shall be used. If the T3319 value received by the MS contains an indication that the timer is deactivated or the timer value is zero, then the MS shall use the default value. If the PDP context status information element is included in the Service Accept, then the MS shall deactivate locally (without peer to peer signalling between the MS and the network) all that PDP contexts which are not in SM state PDP-INACTIVE on MS side but are indicated by the Network as being in state PDP-INACTIVE. If there is a default PDP context among the PDP contexts to be deactivated, an MS supporting S1 mode shall locally deactivate all PDP contexts associated to the same PDP address and APN as the default PDP context without peer-to-peer SM signalling to the network; an MS not supporting S1 mode may apply the same behaviour. If the MBMS context status information element is included in the SERVICE ACCEPT message, then the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE in the MS, but are indicated by the network as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the MS shall deactivate all those MBMS contexts locally which are not in SM state PDP-INACTIVE in the MS. If a service request is received from an MS with a LIPA PDN connection, and if: - a L-GW Transport Layer Address is provided by the lower layer together with the service request, and the GGSN address associated with the PDP context of the LIPA PDN connection is different from the provided L-GW Transport Layer Address (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ]  [19c]); or - no L-GW Transport Layer Address is provided together with the service request by the lower layer, then the SGSN explicitly deactivates all PDP contexts associated with the LIPA PDN connection by initiating the PDP context deactivation procedure (see subclause 6.1.3.4.2). If a service request is received from an MS with a SIPTO at the local network PDN connection, the following different cases can be distinguished: 1) if the PDN connection is a SIPTO at the local network PDN connection with collocated L-GW and if: - a SIPTO L-GW Transport Layer Address is provided by the lower layer together with the service request, and the GGSN address associated with the PDP context of the SIPTO at the local network PDN connection is different from the provided SIPTO L-GW Transport Layer Address (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ]  [19c]); or - no SIPTO L-GW Transport Layer Address is provided together with the service request by the lower layer, 2) if the PDN connection is a SIPTO at the local network PDN connection with stand-alone GW and if: - a LHN-ID value is provided by the lower layer together with the service request, and the LHN-ID stored in the PDP context of the SIPTO at the local network PDN connection is different from the provided LHN-ID value (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ]  [19c]); or - no LHN-ID value is provided together with the service request by the lower layer, then the SGSN explicitly deactivates all PDP contexts associated with the SIPTO at the local network PDN connection by initiating the PDP context deactivation procedure (see subclause 6.1.3.4.2).