Section: 4.7.13.5 Abnormal cases in the MS
Content: The following abnormal cases can be identified: a) Access barred because of access class control, EAB or ACDC If the service request procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable. The service request procedure shall not be started. The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started by CM layer if it is still necessary, i.e. when access is granted or because of a cell change. If access is barred because of access class control, the service request is initiated due to a request from upper layers for PS signalling connection, ACDC is applicable to the request and the MS supports ACDC, then the service request procedure shall be started. If access is barred for a certain ACDC category, and if the service request is initiated due to a request from upper layers for PS signalling connection for a higher ACDC category and the MS supports ACDC, then the service request procedure shall be started. If an access request for an uncategorized application is barred due to ACDC , and if the service request is initiated due to a request from upper layers for PS signalling connection for a certain ACDC category and the MS supports ACDC, then the service request procedure shall be started. b) Lower layer failure without "Extended Wait Time" received from lower layers before the security mode control procedure is completed, SERVICE ACCEPT or SERVICE REJECT message is received The procedure shall be aborted except in the following implementation option cases b.1, b.2 and b.3. b.1) Release of PS signalling connection in Iu mode (i.e. RRC connection release) before the completion of the service request procedure The service request procedure shall be initiated again, if the following conditions apply: i) The original service request procedure was initiated over an existing PS signalling connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection were received after the SERVICE REQUEST message was transmitted. b.2) RR release in Iu mode (i.e. RRC connection release) with cause different than "Directed signalling connection re-establishment", for example, "Normal", or "User inactivity" (see 3GPP TS 25.331[ None ]  [23c] and 3GPP TS 44.118[ None ]  [111]) The service request procedure shall be initiated again, if the following conditions apply: i) The original service request procedure was initiated over an existing RRC connection and, ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection were received after the SERVICE REQUEST messge was transmitted. NOTE: The RRC connection release cause different than "Directed signalling connection re-establishment" that triggers the re-initiation of the service request procedure is implementation specific. b.3) RR release in Iu mode (i.e. RRC connection release) with cause "Directed signalling connection re-establishment" (see 3GPP TS 25.331[ None ]  [23c] and 3GPP TS 44.118[ None ]  [111]) The routing area updating procedure shall be initiated followed by a rerun of the service request procedure if the following condition applies: i) The service request procedure was not due to a rerun of the procedure due to "Directed signalling connection re-establishment". c) T3317 expired The MS shall enter GMM-REGISTERED state. If the MS is in PMM-IDLE mode then the MS shall increment the service request attempt counter, abort the procedure and release locally any resources allocated for the service request procedure. If the service request procedure is initiated to establish a PDN connection for emergency bearer services or the MS has a PDN connection for emergency bearer services established or the MS is an MS configured to use AC11 – 15 in selected PLMN, the service request counter shall not be incremented. If the service request attempt counter is greater than or equal to 5, the MS shall start timer T3325. The MS shall not attempt service request until expiry of timer T3325 unless: - the service request is in response to paging from the network; - the MS is an MS configured to use AC11 – 15 in selected PLMN; - the service request is initiated to establish a PDN connection for emergency bearer services; - the MS has a PDN connection for emergency bearer services established; or - the MS is registered in a new PLMN. If the MS is in PMM-CONNECTED mode, then the procedure shall be aborted. d) SERVICE REJECT received, other causes than those treated in subclause 4.7.13.4, and cases of GMM cause values #22 and #25, if considered as abnormal cases according to subclause 4.7.13.4 The procedure shall be aborted. e) Routing area update procedure is triggered If a cell change into a new routing area occurs and the necessity of routing area update procedure is determined before the security mode control procedure is completed, a SERVICE ACCEPT or SERVICE REJECT message has been received, the Service request procedure shall be aborted and the routing area updating procedure is started immediately. Follow-on request pending may be indicated in the ROUTING AREA UPDATE REQUEST for the service, which was the trigger of the aborted Service request procedure, to restart the pending service itself or the Service request procedure after the completion of the routing area updating procedure. If the Service type of the aborted SERVICE REQUEST was indicating "data", then the routing area update procedure may be followed by a re-initiated Service request procedure indicating "data", if it is still necessary. If the Service type was indicating "MBMS multicast service reception", or "MBMS broadcast service reception" the Service request procedure shall be aborted. f) Power off If the MS is in state GMM-SERVICE-REQUEST-INITIATED at power off, the GPRS detach procedure shall be performed. g) Detach procedure collision GPRS detach containing detach type "re-attach required" or "re-attach not required": If the MS receives a DETACH REQUEST message from the network in state GMM-SERVICE-REQUEST-INITIATED, the GPRS detach procedure shall be progressed and the Service request procedure shall be aborted. If the GMM cause IE, in the DETACH REQUEST message, indicated a "re-attach required", the GPRS attach procedure shall be performed. If the DETACH REQUEST message contains detach type "re-attach not required" and GMM cause #2 "IMSI unknown in HLR", the MS will follow the procedure as described below for the detach type "IMSI detach". GPRS detach containing detach type "IMSI detach": If the MS receives a DETACH REQUEST message from the network in state GMM-SERVICE-REQUEST-INITIATED, the network and the MS shall progress both procedures. h) "Extended wait time" for PS domain from the lower layers The MS shall abort the service request procedure, enter state GMM-REGISTERED, and stop timer T3317 if still running. If the SERVICE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3346 with the "Extended wait time" value. In other cases the MS shall ignore the "Extended wait time". The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. m) Timer T3346 is running The MS shall not start the service request procedure unless: - the MS receives a paging; or - the MS is an MS configured to use AC11 – 15 in selected PLMN; or - the MS has a PDN connection for emergency bearer services established; or - the MS is establishing a PDN connection for emergency bearer services; or - the MS has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication, the timer T3302 and the timer T3311 are not running and the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority". The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped.