Section: 4.5.1.2 Abnormal cases
Content: Mobile station side: a) RR connection failure without "Extended Wait Time" received from lower layers or IMSI deactivation If an RR connection failure occurs, except in the following implementation option case a.1, or the IMSI is deactivated during the establishment of an MM connection, the MM connection establishment is aborted, timers T3230 is stopped, and an indication is given to the CM entity that requested the MM connection establishment. This shall be treated as a rejection for establishment of the new MM connection, and the MM sublayer shall release all active MM connections. a.1) RR connection failure in Iu mode (i.e. RRC connection release) with, for example, cause "Normal", "User inactivity" or "Directed signalling connection re-establishment" (see 3GPP TS 25.331[ None ]  [23c] and 3GPP TS 44.118[ None ]  [111]) The MM connection establishment procedure shall be initiated again, if the following conditions apply: i) The original MM connection establishment was initiated over an existing RRC connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the CS signalling connection (e.g. CS authentication procedures, see subclause 4.3.2), were received after the CM SERVICE REQUEST message was transmitted. NOTE 1: The RRC connection release cause that triggers the re-initiation of the MM connection establishment procedure is implementation specific. b) T3230 expiry If T3230 expires (i.e. no response is given but a RR connection is available) the MM connection establishment is aborted and the requesting CM sublayer is informed. If no other MM connection exists then the mobile station shall proceed as described in subclause 4.5.3.1 for release of the RR connection. Otherwise the mobile station shall return to the MM sublayer state where the request of an MM connection was received, i.e. to MM sublayer state MM connection active. Other ongoing MM connections (if any) shall not be affected. c) Reject cause values #95, #96, #97, #99, #100, #111 received The same actions as on timer expiry shall be taken by the mobile station. d) Random access failure or RR connection establishment failure without "Extended Wait Time" received from lower layers If the mobile station detects a random access failure or RR connection establishment failure during the establishment of an MM connection, it aborts the MM connection establishment and gives an indication to the CM entity that requested the MM connection establishment. NOTE 2: Further actions of the mobile station depend on the RR procedures and MM specific procedures during which the abnormal situation has occurred and are described together with those procedures. e) Access barred because of access class control or EAB The MM connection establishment shall not be initiated. The MS stays in the current serving cell and applies normal cell reselection process. The MM connection establishment may be initiated by CM layer if it is still necessary, i.e. when access is granted or because of a cell change. f) Indication that a CS fallback to GERAN or UTRAN has failed If EMM indicates that the CS fallback to GERAN or UTRAN failed, the MM sublayer shall abort the MM connection establishment and inform the requesting CM sublayer. g) "Extended wait time" for CS domain from the lower layers The MS shall abort the MM connection establishment and stop timer T3230 if still running. If the CM SERVICE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3246 with the "Extended wait time" value. In other cases the MS shall ignore the "Extended wait time". The MM connection establishment is started, if still necessary, when timer T3246 expires or is stopped. h) Timer T3246 is running The MM connection establishment shall not be initiated unless the MS is establishing an emergency call or the MS is an MS configured to use AC11 – 15 in selected PLMN. The MS stays in the current serving cell and applies normal cell reselection process. The MM connection establishment is started, if still necessary, when timer T3246 expires or is stopped. Network side: a) RR connection failure The actions to be taken upon RR connection failure within a MM common procedure are described together with that procedure. A RR connection failure occurring outside such MM common procedures, shall trigger the release of all active MM connections if any. b) Invalid message or message content Upon reception of an invalid initial message or a CM SERVICE REQUEST message with invalid content, a CM SERVICE REJECT message shall be returned with one of the following appropriate Reject cause indications: # 95: Semantically incorrect message # 96: Mandatory information element error # 97: Message type non-existent or not implemented # 99: Information element non-existent or not implemented # 100: Conditional IE error # 111: Protocol error, unspecified When the CM SERVICE REJECT message has been sent, the network may start RR connection release if no other MM connections exist or if the abnormal condition also has influence on the other MM connections.