Section: 4.7.3.1.4a GPRS attach for emergency bearer services not accepted by the network (UTRAN Iu mode only)
Content: If the attach request for emergency bearer services cannot be accepted by the network, an ATTACH REJECT message is transferred to the MS. The ATTACH REJECT message includes GMM cause #5 "IMEI not accepted" or one of the GMM cause values as described in subclause 4.7.3.1.4. NOTE 1: If GMM cause #11 is sent to a MS of a roaming subscriber attaching for emergency bearer services and the MS is in automatic network selection mode, it cannot obtain normal service provided by this PLMN. Upon receiving the ATTACH REJECT message including GMM cause #5, the MS shall enter the state GMM-DEREGISTERED.NO-IMSI. Upon receiving the ATTACH REJECT message including one of the other GMM cause values, the MS shall perform the actions as described in subclause 4.7.3.1.4 with the following addition: the MS shall inform the upper layers of the failure of the procedure. 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.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [13D] can result in the emergency call being attempted to another IP-CAN. If the attach request for emergency bearer services fails due to abnormal case a) in subclause 4.7.3.1.5, the MS shall perform the actions as described in subclause 4.7.3.1.5 and inform the upper layers of the failure to access the network. 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.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [13D] can result in the emergency call being attempted to another IP-CAN. If the attach request for emergency bearer services fails due to abnormal cases b), c) or d) in subclause .1.5, the MS shall perform the actions as described in subclause 4.7.3.1.5 with the following addition: the MS shall inform the upper layers of the failure of the procedure. NOTE 4: 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.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [13D] can result in the emergency call being attempted to another IP-CAN. In a shared network, upon receiving the ATTACH REJECT message, the MS shall perform the actions as described in subclause 4.7.3.1.4, and shall: a) inform the upper layers of the failure of the procedure; or NOTE 5: 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.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt the attach for emergency bearer services to another PLMN in the shared network. In a shared network, if the attach request for emergency bearer services fails due to abnormal case a) in subclause 4.7.3.1.5, the MS shall perform the actions as described in subclause 4.7.3.1.5 and shall: a) inform the upper layers of the failure to access the network; or NOTE 6: 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.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt the attach for emergency bearer services to another PLMN in the shared network. In a shared network, if the attach request for emergency bearer services fails due to abnormal cases b), c) or d) in subclause .1.5, the MS shall perform the actions as described in subclause .1.5, and shall: a) inform the upper layers of the failure of the procedure; or NOTE 7: 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.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt the attach for emergency bearer services to another PLMN in the shared network.