Attach

If an ATTACH REQUEST has EPS attach type not set to "EPS emergency attach", the RRC establishment cause shall be set to MO signalling except when the UE initiates attach procedure to establish emergency bearer services.
(See Note 1, Note 6)

"originating signalling"

If an ATTACH REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to Delay tolerant.
(See Note 1, Note 6)

"originating signalling"

If an ATTACH REQUEST has EPS attach type set to "EPS emergency attach", or if the ATTACH REQUEST has EPS attach type not set to "EPS emergency attach" but the UE initiates the attach procedure either on receiving request from upper layer to establish emergency bearer services or with a PDN CONNECTIVITY REQUEST that has request type set to "handover of emergency bearer services", the RRC establishment cause shall be set to Emergency call.
(See Note 1, Note 4)

"emergency calls"

If the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368 [15A] or the USIM file EF_NASCONFIG in 3GPP TS 31.102 [17]) and the attach procedure has been initiated upon receiving a request from upper layers to transmit user data related to an exceptional event, the RRC establishment cause shall be set to MO exception data.
(See Note 1)

"originating signalling"

Tracking Area Update

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and MO MMTEL voice call is not started, MO MMTEL video call is not started, MT MMTEL voice call is not started, MT MMTEL video call is not started, MO SMSoIP is not started, MT SMSoIP is not started, MO SMS over NAS or MO SMS over S102 is not requested, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 5, Note 6)

"originating signalling"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and an MO MMTEL voice call is started, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 3, Note 5, Note 6)

"originating MMTEL voice"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and an MO MMTEL video call is started, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 3, Note 5, Note 6)

"originating MMTEL video"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and an MT MMTEL voice call is started, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 6)

"originating MMTEL voice"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and an MT MMTEL video call is started, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 6)

"originating MMTEL video"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and an MO SMSoIP is started, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 5, Note 6)

"originating SMSoIP"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and an MT SMSoIP is started, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 6)

"originating SMSoIP"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and an MO SMS over NAS or MO SMS over S102 is requested, the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 5, Note 6)

"originating SMS"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", the tracking area updating procedure is not triggered due to paging, a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", and MO MMTEL voice call is not started, MO MMTEL video call is not started, MT MMTEL voice call is not started, MT MMTEL video call is not started, MO SMSoIP is not started, MT SMSoIP is not started, MO SMS over NAS or MO SMS over S102 is not requested, the RRC establishment cause shall be set to Delay tolerant.
(See Note 1, Note 6)

"originating signalling"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", an MO MMTEL voice call is started, and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 3, Note 5, Note 6)

"originating MMTEL voice"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", an MO MMTEL video call is started, and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 3, Note 5, Note 6)

"originating MMTEL video"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", an MT MMTEL voice call is started, and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 6)

"originating MMTEL voice"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", an MT MMTEL video call is started, and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 6)

"originating MMTEL video"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", an MO SMSoIP is started, and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 5, Note 6)

"originating SMSoIP"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", an MT SMSoIP is started, and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 6)

"originating SMSoIP"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", an MO SMS over NAS or MO SMS over S102 is requested, and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to MO signalling.
(See Note 1, Note 5, Note 6)

"originating SMS"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and a TRACKING AREA UPDATE REQUEST is a response to paging where the CN domain indicator is set to "PS" or "CS", the RRC establishment cause shall be set to MT access.
(See Note 1, Note 6)

"terminating calls"

If the UE does not have a PDN connection established for emergency bearer services and is not initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", and a TRACKING AREA UPDATE REQUEST is triggered upon receiving a "call-pull-initiated" indication from the upper layers (see 3GPP TS 24.174 [13F]), the RRC establishment cause shall be set to MT access.
(See Note 1)

"terminating calls"

If the UE has CS fallback emergency call or 1xCS fallback emergency call pending, the RRC establishment cause shall be set to Emergency call.
(See Note 1)

"emergency calls"

If the UE has a PDN connection established for emergency bearer services or is initiating a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", the RRC establishment cause shall be set to Emergency call.
(See Note 1)

"emergency calls"

If the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368 [15A] or the USIM file EF_NASCONFIG in 3GPP TS 31.102 [17]) and there is a pending request from upper layers to transmit user data related to an exceptional event, the RRC establishment cause shall be set to MO exception data.

"originating signalling"

If the UE is requesting resources for V2X communication over PC5, the RRC establishment cause shall be set to MO signalling.
(See Note 1)

"originating signalling"

If the UE is requesting resources for V2X communication over PC5 and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to Delay tolerant.
(See Note 1)

"originating signalling"

If the UE is requesting resources for ProSe direct discovery or ProSe direct communication as specified in 3GPP TS 36.331 [22], the RRC establishment cause shall be set to MO signalling.
(See Note 1)

"originating signalling"

If the UE is requesting resources for ProSe direct discovery or ProSe direct communication as specified in 3GPP TS 36.331 [22] and a TRACKING AREA UPDATE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to Delay tolerant.
(See Note 1)

"originating signalling"

Detach

MO signalling
(See Note 1)

"originating signalling"

Service Request

If a SERVICE REQUEST is to request user plane radio resources and MO MMTEL voice call is not started, MO MMTEL video call is not started, MT MMTEL voice call is not started, MT MMTEL video call is not started, MO SMSoIP is not started, and MT SMSoIP is not started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating calls"

If a SERVICE REQUEST is to request user plane radio resources and an MO MMTEL voice call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL voice"

If a SERVICE REQUEST is to request user plane radio resources and an MO MMTEL video call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL video

If a SERVICE REQUEST is to request user plane radio resources and an MT MMTEL voice call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL voice"

If a SERVICE REQUEST is to request user plane radio resources and an MT MMTEL video call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL video

If a SERVICE REQUEST is to request user plane radio resources and an MO SMSoIP is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If a SERVICE REQUEST is to request user plane radio resources and an MT SMSoIP is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If a SERVICE REQUEST is to request user plane radio resources for emergency bearer services, the RRC establishment cause shall be set to Emergency call.
(See Note 1)

"emergency calls"

If a SERVICE REQUEST is to request resources for UL signalling and not for MO SMS over NAS or MO SMS over S102, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating calls"

If a SERVICE REQUEST is to request resources for UL signalling for MO SMS over NAS or MO SMS over S102, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMS"

If a SERVICE REQUEST is to request user plane radio resources or to request resources for UL signalling and the UE is configured for dual priority and the NAS signalling low priority indicator is overridden, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating calls"

If a SERVICE REQUEST is triggered by a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", the RRC establishment cause shall be set to Emergency call.
(See Note 1)

"emergency calls"

If a SERVICE REQUEST is to request user plane radio resources or to request resources for UL signalling, the UE is configured for NAS signalling low priority, and MO MMTEL voice call is not started, MO MMTEL video call is not started, MT MMTEL voice call is not started, MT MMTEL video call is not started, and MO SMSoIP is not started, MT SMSoIP is not started, MO SMS over NAS or MO SMS over S102 is not requested, the RRC establishment cause shall be set to Delay tolerant.
(See Note 1, Note 6)

"originating calls"

If a SERVICE REQUEST is to request user plane radio resources, an MO MMTEL voice call is started, and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL voice"

If a SERVICE REQUEST is to request user plane radio resources, an MO MMTEL video call is started, and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL video"

If a SERVICE REQUEST is to request user plane radio resources, an MT MMTEL voice call is started, and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL voice"

If a SERVICE REQUEST is to request user plane radio resources, an MT MMTEL video call is started, and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL video"

If a SERVICE REQUEST is to request user plane radio resources, an MO SMSoIP is started, and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If a SERVICE REQUEST is to request user plane radio resources, an MT SMSoIP is started, and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If a SERVICE REQUEST is to request resources for UL signalling for MO SMS over NAS or MO SMS over S102 and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMS"

If a SERVICE REQUEST is a response to paging where the CN domain indicator is set to "PS", the RRC establishment cause shall be set to MT access.
(See Note 1, Note 6)

"terminating calls"

If a SERVICE REQUEST is triggered upon receiving a "call-pull-initiated" indication from the upper layers (see 3GPP TS 24.174 [13F]), the RRC establishment cause shall be set to MT access.
(See Note 1)

"terminating calls"

If a SERVICE REQUEST is triggered to request resources for ProSe direct discovery or ProSe direct communication as specified in 3GPP TS 36.331 [22], the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating calls"

If a SERVICE REQUEST is triggered to request resources for ProSe direct discovery or ProSe direct communication as specified in 3GPP TS 36.331 [22] and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to Delay tolerant.
(See Note 1, Note 6)

"originating calls"

If a SERVICE REQUEST is triggered to request resources for V2X communication over PC5, the RRC establishment cause shall be set to MO data.
(See Note 1)

"originating calls"

If a SERVICE REQUEST is triggered to request resources for V2X communication over PC5 and the UE is configured for NAS signalling low priority, the RRC establishment cause shall be set to Delay tolerant.
(See Note 1)

"originating calls"

If an EXTENDED SERVICE REQUEST has service type set to "packet services via S1" and is to request user plane radio resources for emergency bearer services, the RRC establishment cause shall be set to Emergency call.
(See Note 1)

"emergency calls"

If an EXTENDED SERVICE REQUEST has service type set to "packet services via S1" and is triggered by a PDN CONNECTIVITY REQUEST that has request type set to "emergency" or "handover of emergency bearer services", the RRC establishment cause shall be set to Emergency call.
(See Note 1)

"emergency calls"

If an EXTENDED SERVICE REQUEST has service type set to "packet services via S1" and is a response to paging where the CN domain indicator is set to "PS", the RRC establishment cause shall be set to MT access.
(See Note 1, Note 6)

"terminating calls"

If an EXTENDED SERVICE REQUEST has service type set to "mobile originating CS fallback or 1xCS fallback" and is to request mobile originating 1xCS fallback, or if an EXTENDED SERVICE REQUEST is a response to paging for 1xCS fallback received over cdma2000^® 1xRTT and has service type set to "mobile terminating CS fallback or 1xCS fallback", the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6).

"originating calls"

If an EXTENDED SERVICE REQUEST has service type set to "mobile originating CS fallback or 1xCS fallback" and is to request mobile originating CS fallback, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6).

"mobile originating CS fallback"

If an EXTENDED SERVICE REQUEST is a response to paging for CS fallback, service type set to "mobile terminating CS fallback or 1xCS fallback", the RRC establishment cause shall be set to MT access.
(See Note1, Note 2, Note 6).

"terminating calls"

If an EXTENDED SERVICE REQUEST has service type set to "mobile originating CS fallback emergency call or 1xCS fallback emergency call", the RRC establishment cause shall be set to Emergency call.
(See Note 1).

"emergency calls"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority", and MO MMTEL voice call is not started, MO MMTEL video call is not started, MT MMTEL voice call is not started, MT MMTEL video call is not started, and MO SMSoIP is not started, MT SMSoIP is not started, MO SMS over NAS or MO SMS over S102 is not requested, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating calls"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and an MO MMTEL voice call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL voice"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and an MO MMTEL video call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL video"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and an MT MMTEL voice call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL voice"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and an MT MMTEL video call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL video"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and an MO SMSoIP is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and an MT SMSoIP is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and an MO SMS over NAS or MO SMS over S102 is requested, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMS"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", and MO MMTEL voice call is not started, MO MMTEL video call is not started, MT MMTEL voice call is not started, MT MMTEL video call is not started, and MO SMSoIP is not started, MT SMSoIP is not started, MO SMS over NAS or MO SMS over S102 is not requested, the RRC establishment cause shall be set to Delay tolerant.
(See Note 1, Note 6).

"originating calls"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and an MO MMTEL voice call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL voice"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and an MO MMTEL video call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 3, Note 6)

"originating MMTEL video"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and an MT MMTEL voice call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL voice"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and an MT MMTEL video call is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating MMTEL video"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and an MO SMSoIP is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and an MT SMSoIP is started, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMSoIP"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and an MO SMS over NAS or MO SMS over S102 is requested, the RRC establishment cause shall be set to MO data.
(See Note 1, Note 6)

"originating SMS"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and is triggered to request resources for ProSe direct discovery or ProSe direct communication, the RRC establishment cause shall be set to MO data.
(See Note 1)

"originating calls"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and is triggered to request resources for ProSe direct discovery or ProSe direct communication, the RRC establishment cause shall be set to Delay tolerant.
(See Note 1)

"originating calls"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is not configured for NAS signalling low priority" and is triggered to request resources for V2X communication over PC5, the RRC establishment cause shall be set to MO data.
(See Note 1)

"originating calls"

If an EXTENDED SERVICE REQUEST contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority" and is triggered to request resources for V2X communication over PC5, the RRC establishment cause shall be set to Delay tolerant.
(See Note 1)

"originating calls"

If a CONTROL PLANE SERVICE REQUEST is a response to paging where the Control plane service type is set to "mobile terminating request", the RRC establishment cause shall be set to MT access. (see Note 1, Note 6)

"terminating calls"

If a CONTROL PLANE SERVICE REQUEST is to transfer user data or to request resources for UL signalling, the RRC establishment cause shall be set to MO data.
(see Note 1, Note 6)

"originating calls"

If a CONTROL PLANE SERVICE REQUEST is to transfer user data or to request resources for UL signalling and contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to Delay tolerant.
(see Note 1, Note 6)

"originating calls"

In WB-S1 Mode, if a CONTROL PLANE SERVICE REQUEST is to transfer MO SMS, the RRC establishment cause shall be set to MO data.
(see Note 1, Note 6)

"originating SMS"

In NB-S1 Mode, if a CONTROL PLANE SERVICE REQUEST is to transfer MO SMS, the RRC establishment cause shall be set to MO data.

"originating calls"

In NB-S1 Mode, if a CONTROL PLANE SERVICE REQUEST is to transfer MO SMS and contains the Device properties IE with low priority indicator set to "MS is configured for NAS signalling low priority", the RRC establishment cause shall be set to Delay tolerant.

"originating calls"

If the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368 [15A] or the USIM file EF_NASCONFIG in 3GPP TS 31.102 [17]) and a CONTROL PLANE SERVICE REQUEST is to perform initial data transfer related to an exceptional event, the RRC establishment cause shall be set to MO exception data.

"originating calls"

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Old

New

2008-02

Draft skeleton provided

0.0.0

2008-02

CT1#51 bis

Includes the following contributions agreed by CT1:
C1-080690, C1-080743, C1-080769

0.0.0

0.1.0

2008-03

e-mail review

Correction of references that were not updated during the implementation of C1-080769

0.1.0

0.1.1

2008-04

CT1#52

Includes the following contributions agreed by CT1:
C1-080943, C1-081020, C1-081037, C1-081057, C1-081058, C1‑081268, C1-081269, C1-081272, C1-081273, C1-081278, C1‑081280, C1-081289, C1-081290, C1-081291, C1-081292, C1‑081296, C1-081301, C1-081302, C1-081387, C1-081407, C1‑081409, C1-081417, C1-081418, C1-081436, C1-081437, C1‑081438, C1-081439, C1-081440, C1-081442

0.1.1

0.2.0

2008-05

CT1#53

Includes the following contributions agreed by CT1:
C1-081650, C1-081651, C1-081878, C1-081886, C1-081887, C1‑081888, C1-081889, C1-081890, C1-081971, C1-081972, C1‑081973, C1-081974, C1-081975, C1-081978, C1-081979, C1‑081988, C1-081989, C1-081990, C1-081991, C1-081992, C1‑081993, C1-081994, C1-081996, C1-081997, C1-081998, C1‑081999, C1-082000, C1-082062, C1-082095, C1-082097, C1‑082099, C1-082100, C1-082101, C1-082111

0.2.0

0.3.0

2008-07

CT1#54

Includes the following contributions agreed by CT1:
C1-082125, C1-082126, C1-082282, C1-082415, C1-082432, C1‑082485, C1-082487, C1-082510, C1-082572, C1-082573, C1‑082574, C1-082577, C1-082578, C1-082579, C1-082580, C1‑082586, C1-082588, C1-082589, C1-082633, C1-082634, C1‑082635, C1-082636, C1-082701, C1-082702, C1-082703, C1‑082705, C1-082719, C1-082720, C1-082722, C1-082723, C1‑082724, C1-082725, C1-082726, C1-082727, C1-082728, C1‑082729, C1-082791, C1-082794, C1-082795, C1-082797, C1‑082802, C1-082807, C1-082811, C1-082816, C1-082819, C1‑082820

0.3.0

0.4.0

2008-08

CT1#55

Includes the following contributions agreed by CT1:
C1-082981, C1-082995, C1-082997, C1-083013, C1-083030, C1‑083031, C1-083032, C1-083056, C1-083131, C1-083139, C1‑083140, C1-083146, C1-083151, C1-083168, C1-083442, C1‑083445, C1-083450, C1-083452, C1-083453, C1-083454, C1‑083456, C1-083457, C1-083461, C1-083462, C1-083463, C1‑083465, C1-083468, C1-083471, C1-083472, C1-083473, C1‑083474, C1-083476, C1-083477, C1-083517, C1-083522, C1‑083580, C1-083581, C1-083582, C1-083583, C1-083584, C1‑083588, C1-083591, C1-083592, C1-083593, C1-083597, C1‑083598, C1-083599, C1-083605, C1-083606, C1-083607, C1‑083609, C1-083616, C1-083619, C1-083629, C1-083630, C1‑083635, C1-083636, C1-083638

0.4.0

0.5.0

2008-09

–

–

–

–

Version 1.0.0 created for presentation to TSG CT#41 for information

0.5.0

1.0.0

2008-10

CT1#55 bis

Includes the following contributions agreed by CT1:
C1-083788, C1-083789, C1-083948, C1-083949, C1-083953, C1‑084002, C1-084012, C1-084104, C1-084143, C1-084144, C1‑084146, C1-084308, C1-084310, C1-084316, C1-084329, C1‑084332, C1-084333, C1-084335, C1-084337, C1-084338, C1‑084340, C1-084341, C1-084343, C1-084344, C1-084346, C1‑084348, C1-084349, C1-084351, C1-084352, C1-084353, C1‑084355, C1-084357, C1-084358, C1-084359, C1-084360, C1‑084362, C1-084381, C1-084475, C1-084478, C1-084479, C1‑084480, C1-084484, C1-084490, C1-084491, C1-084492, C1‑084499, C1-084551, C1-084554

1.0.0

1.1.0

2008-10

e-mail review

Correction of implementation of C1-084492

1.1.0

1.1.1

2008-10

e-mail review

Correction of implementation of C1-084353

1.1.1

1.1.2

2008-11

CT1#56

Includes the following contributions agreed by CT1:
C1-084592, C1-084610, C1-084624, C1-084627, C1-084666, C1‑084668, C1-084747, C1-084785, C1-084925, C1-084926, C1‑084976, C1-084977, C1-085167, C1-085170, C1-085171, C1‑085172, C1-085174, C1-085175, C1-085178, C1-085180, C1‑085199, C1-085304, C1-085310, C1-085312, C1-085313, C1‑085315, C1-085317, C1-085356, C1-085372, C1-085381, C1‑085385, C1-085387, C1-085388, C1-085390, C1-085392, C1‑085394, C1-085396, C1-085398, C1-085399, C1-085505, C1‑085506, C1-085508, C1-085509, C1-085510, C1-085511, C1‑085512, C1-085513, C1-085514, C1-085515, C1-085518, C1‑085520, C1-085521, C1-085528, C1-085533, C1-085539, C1‑085540, C1-085541, C1-085542, C1-085545, C1-085550, C1‑085551, C1-085552, C1-085553

1.1.2

1.2.0

2008-11

review

Correction of implementation of C1-084926, C1-085180

1.2.0

1.2.1

2008-11

Version 2.0.0 created for presentation to TSG CT#42 for approval

1.2.1

2.0.0

2008-12

CT-42

Version 8.0.0 created after approval in CT#42

2.0.0

8.0.0

2009-03

CT-43

CP-090153

0003

2

Clarification of the timer T3413 in paging procedure for CSFB

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0004

2

Clarification of the abnormal case in UE requested PDN connectivity procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0006

1

Clarification on expiration of T3417

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0010

1

Clean up the unuseful definition and complete sentence

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0011

1

Cleanup the definition of the TAI list

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0015

1

Updating the identities of forbidden tracking areas

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0017

2

the handling of the UE after the EPS detach only

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0019

2

Resolve editors’notes for NAS security

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0022

1

APN-AMBR Clarifications

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0023

2

State change to EMM-DEREGISTERED for non-3GPP access

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0025

2

Updating the APN-AMBR of the UE after inter-system handover to S1 mode

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0027

2

Provision of RRC establishment cause values by EPS NAS

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0034

2

Update to Paging using IMSI procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0035

1

Update the PDN address IE to Mandatory

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0037

1

Update to the detach procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0039

3

Security and inter RAT mobility to E-UTRAN

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0040

1

KSI inclusion in Detach Request

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0044

1

Editorials on security issues

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0045

2

Behaviour on Service Reject(cause#10), relationship between SM and ESM state machines, inclusion of PDP context parameters

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0046

2

Clarifications on issues for bearer context states

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0050

Remove Editors Note for TAI length

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0051

1

Correct use of cdma terminology

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0059

1

Addition of actions on receiving an ESM STATUS message

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0060

1

Addition of the definition of casue value #47 (PTI mismatch)

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0061

1

Editorial corrections on the definition of default bearer and the ESM message names

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0062

2

Correction to error cause value #9 and integrity check failure

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0064

IPv6 interface identifier coding

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0066

3

Clarification for local release of bearers

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0068

1

Corrections for Attach failure procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0069

2

Re-transmission of EMM DL NAS message handling due to handover

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0070

2

Re-transmission of ESM DL NAS message handling due to handover

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0071

Paging for EPS services using IMSI and DRX

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0075

2

Coordination of ESM and EMM sublayers for supporting ISR

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0076

1

Handling of TAI list at the UE

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0078

2

UE specific DRX Parameter handling in ATTACH/TAU procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0081

1

Handling of security context during state transitions

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0082

2

Trigger for initiating ciphering protection

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0085

2

UE action related to ISR local deactivation

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0088

3

Clarification on CLI usage

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0092

1

Abnormal case handling for Extended Service request

8.0.0

8.1.0

2009-03

CT-43

CP-090259

0093

4

UE behaviour when UE support of CSG selection is optional

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0094

2

Conditions for initiating TAU and combined TAU

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0095

1

Corrections for attach and TAU attempt counters

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0096

1

Network initiated detach procedure corrections

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0097

1

EMM states cleanup

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0099

2

Supervision timer and corrections for the extended service request procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0100

1

Corrections for combined attach procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0102

2

Definition of NAS Message Container and Removal of Editor’s Note

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0103

1

Adding missing procedure figure to Service Request

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0104

1

Introduction of the Local Emergency Numbers List

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0105

2

New cause value for separation bit failure in authentication

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0106

3

Solving editor’s notes in Annex A.3

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0109

2

Update on security procedure section

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0112

1

Clarification on Dedicated bearer setup procedure failure

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0116

1

New ESM cause value for collision with network initiated request

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0117

1

Populating PDN type IE value in PDN CONNECTIVITY REQUEST message

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0119

2

Extended service request for 1xCSFB

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0125

1

ODB Error Cause Clarification

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0128

NAS recovery on/off mechanism(LTE)

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0129

1

Introduce definition of EPS services and non-EPS services

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0131

1

Proposal of UE GMM and MM behavior on reception of error cause #9 when UE executed TAU, combined TAU and Service Request

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0135

1

Clarifications on IP address handling

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0136

1

Unsuccessful cases for pre-registration

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0137

2

Use of P-TMSI for the attach procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0138

Cleanup of editor’s notes

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0139

1

Correction of the paging procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0140

1

Cleanup of editor’s notes for ESM abnormal cases

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0141

Definition of ESM cause #54

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0142

Definition of security related IEs for inter-system handover

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0143

Removal of ISR bit from UE network capability

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0144

Correction of detach procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0145

1

Addition of text for clause 4.1, Overview

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0146

1

Addition of text for clause 6.1.1, General

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0147

1

Addition of text for clause 6.1.2, Types of ESM procedures

8.0.0

8.1.0

2009-03

CT-43

CP-090157

0152

Correction of cause#25 handling

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0153

Description of procedure transaction states for the network

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0154

1

Moving the description of the eKSI to clause 4.4

8.0.0

8.1.0

2009-03

CT-43

CP-090129

0155

3

CS Service Notification

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0158

1

E9.04, removal of Editor’s note in 9.5

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0159

E4.03 and E9.05, removal of Editor’s notes in 4.3.3.1 and 9.6

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0160

2

Inclusion of APN in PDN connectivity request

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0162

2

Clarification on local EPS bearer context deactivation

8.0.0

8.1.0

2009-03

CT-43

CP-090131

0163

2

Unciphered network operation

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0164

ESM cause value #53 missing in 6.5.1.4

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0165

1

Reservation of "reserved" and "unused" code points

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0166

Editorial modification to add a "new line" character

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0167

2

Activation of dedicated bearers during attach procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0168

2

Additions to " EPS bearer context deactivation initiated by the network"

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0170

Removal of EN for TAU reject (cause #12)

8.0.0

8.1.0

2009-03

CT-43

CP-090130

0171

2

Security Terminolgy Change to Reflect 33.401

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0172

1

Alignment of cause representation

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0173

Correction of fields within Detach type IE

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0174

Deletion of editor’s note for 2 digit MNC

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0176

2

Clarification of the network behaviour on SMC rejection

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0178

1

Add an abnormal case in the dedicated EPS bearer context activation procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0181

3

Clarify the collison between detach and service request procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090127

0186

1

Correction of QCI

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0187

Clarifications related to the use of "active flag"

8.0.0

8.1.0

2009-03

CT-43

CP-090153

0189

1

Corrections for CS/PS mode 1 and CS/PS mode 2 of operation

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0195

1

ESM information transfer flag

8.0.0

8.1.0

2009-03

CT-43

CP-090125

0198

Attach attempt counter

8.0.0

8.1.0

2009-03

CT-43

CP-090128

0199

1

Error correction in reference for timer T3412 in TAU procedure

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0201

1

Clarifications for request type

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0203

1

Clarification of the use of NAS security header

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0205

1

Proposal of UE GMM and MM behavior on reception of error cause #10 when UE executed TAU, combined TAU and Service Request

8.0.0

8.1.0

2009-03

CT-43

CP-090126

0206

Definition of T3480, T3485, T3486, T3495 timer duration; Corrections on EPS bearer identity checking

8.0.0

8.1.0

2009-03

CT-43

CP-090215

0207

3

Clarification of UE requested ESM procedures

8.0.0

8.1.0

2009-03

CT-43

CP-090157

0208

Corrections to CSG related NAS behavior

8.0.0

8.1.0

2009-06

CT-44

CP-090421

0190

1

Cleanup for transport of NAS messages procedure

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0210

1

TAU handling

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0214

NAS security parameters for inter system handovers

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0216

2

Transmission failure of EMM messages

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0217

1

Clarifications on protocol discriminator for security protected NAS message

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0219

1

Clarifications related PDN disconnect request, ESM information request, EPS bearer context modification request and bearer resource allocation request procedures

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0220

Service Reject(cause #12)

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0227

1

Security context cleanup at Security Mode Reject

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0228

2

Removal of KSIASME from TAU accept

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0229

Add missing LV-E format

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0230

New value for ESM timer T3482

8.1.0

8.2.0

2009-06

CT-44

CP-090410

0231

EPS mobile identity octet numbering

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0232

2

PDN connectivity reject cause value corrections

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0233

1

MME handling of lower layer failure during the attach procedure

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0239

1

Null ciphering algorithm

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0242

1

EPS security modification

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0243

2

Clarification regarding bearer resource allocation procedure, EPS bearer identity and PTI in several ESM messages.

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0244

1

Removal of default PDN

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0245

2

Add description of cause #40 in Annex A

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0246

2

Correct the UE behavior of handling ESM message

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0247

1

Clarify the UE behavior upon reception of some reject messages

8.1.0

8.2.0

2009-06

CT-44

CP-090498

0251

5

eKSI definition in NAS messages

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0252

1

eKSI in Service Request message

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0257

Remove unused ESM cause value #40 – "Feature not supported"

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0260

1

Abnormal case handling for Extended Service request in 1xCSFB

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0269

1

Resolution of Editor’s Note in clause 5.4.4.2

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0272

Update the cause of start and stop of T3413

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0274

The collison handling for Extended Service Request

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0275

Handling of undefined QCI values

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0276

1

Relation between HNP and HA delivered through PCO

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0277

Corrections on abnormal case in UE requested PDN connectivity procedure

8.1.0

8.2.0

2009-06

CT-44

CP-090411

0280

1

Correction of UE requested resource procedures

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0282

1

More precise general text for UE requested PDN connectivity procedure

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0283

Alignment of cause representation

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0284

Text clean up in 24.301

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0292

1

Correction for the main state change in the UE

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0293

1

Correction for implicit detach timer

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0296

1

Clarification on Local Network initiated detach procedure without EMM signalling

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0300

2

Correction for the EPS mobile identity

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0301

Impacts of successful combined registration on forbidden LAs lists

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0302

CS/PS mode 1 UE behaviour on reception of cause #18

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0303

Corrections on handling of UE network capability

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0304

Cleanup for EMM procedures

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0306

1

Handling of non-semantical mandatory information element errors in the PDN DISCONNNECT REQUEST message.

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0309

2

Clarification on the registered PLMN for Network Sharing

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0312

1

Definition of kbps

8.1.0

8.2.0

2009-06

CT-44

CP-090421

0315

2

Sending UE Id in the CS Service Notification

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0318

1

Clarification of EPS QoS length

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0319

Removal of unnecessary TAU procedure after abnormal bearer allocation failure

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0320

1

Set of minor corrections to TS 24.301

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0321

2

Clarifications to 24.301

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0322

1

Set of corrections to security procedure

8.1.0

8.2.0

2009-06

CT-44

CP-090412

0328

Clarification on access class applicability

8.1.0

8.2.0

2009-06

CT-44

Correction of minor typo

8.2.0

8.2.1

2009-09

CT-45

CP-090650

0226

7

Correcting ESM and SM coordination

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0255

4

Definition of valid GUTI

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0266

3

Clarification of T3212

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0310

6

TFT for default bearer

8.2.1

8.3.0

2009-09

CT-45

CP-090630

0329

9

Corrections in TFT checks

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0330

4

Resynchronization of EPS bearer contexts on TAU without active flag

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0333

2

Inclusion of GERAN/UTRAN parameters in ESM messages

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0337

1

Clarifications on usage of EPS security context

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0338

1

BCM mode notification for LTE UE

8.2.1

8.3.0

2009-09

CT-45

CP-090677

0340

Update to the CSG ID definition

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0344

Replacing "MS" by "UE"

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0345

1

Correction of error handling

8.2.1

8.3.0

2009-09

CT-45

CP-090677

0346

1

Clarifications related to manual CSG selection

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0358

2

Handling of UE’s usage setting, voice setting and VoIMS indicator – 24.301

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0362

2

Storing EPS security parameters

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0370

2

Clarification on CSFB using redirection

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0372

5

Disabling E-UTRAN capability for the voice centric UE

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0374

2

Detach procedure for the last PDN disconnect by the network

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0375

1

Correction for network abnormal case – Attach and TAU procedures collision

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0376

2

Correction for abnormal case on network side due to lower layer failure

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0379

4

Inclusion of Old P-TMSI signature IE in ATTACH REQUEST and TRACKING AREA UPDATE REQUEST

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0380

1

Interaction between S1 mode and A/Gb or Iu mode

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0381

1

Selected PLMN identity at NAS signalling connection establishment

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0382

4

Aligning UE modes of operation definition with stage 2 principles for CS domain and IM CN Subsystem selection

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0388

2

Corrections for abnormal case of GUTI REALLOCATION procedure

8.2.1

8.3.0

2009-09

CT-45

CP-090677

0389

1

The abnormal case of detach for CSG

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0391

2

Handling of unknown QCI in the network

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0393

1

Corrections for TAU complete initiation

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0395

1

Corrections for Combined TAU procedure initiation

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0396

1

NAS COUNT estimation correction

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0397

2

Security protection of Security mode reject

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0398

1

Rename of ESM cause #30 and #31

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0400

2

Abnormal case of combined default bearer and dedicated bearer

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0405

1

Clarification of behavior upon reception of ESM cause #43

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0407

1

Correcting service type and EPS update type

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0408

Addition of missing LV-E format

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0409

1

Clarification on APN-AMBR IE description

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0411

2

Clarification on abnormal cases in the UE for a few ESM procedures

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0413

1

Correction for the misplaced ESM message

8.2.1

8.3.0

2009-09

CT-45

CP-090733

0415

1

Additional triggers for tracking area update procedure

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0417

2

Deletion of mapped context after detach

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0419

1

Corrections to EPS security context handling

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0425

2

Providing the MSISDN to the MS

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0426

Correction QCI within EPS quality of service information

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0428

Removal of inclusion of cause#46 in some ESM reject messages

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0429

Correction of definition of Linked EPS bearer identity IE

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0430

1

MME and network synchronisation during TAU

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0439

2

Clarification to UE requested bearer modification procedure

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0442

Dependency between transport of NAS messages procedure and other EMM procedures

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0447

1

Correction for EPS update status change

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0448

2

Security handling of TAU

8.2.1

8.3.0

2009-09

CT-45

CP-090651

0449

1

Correction for the usage of Additional GUTI IE

8.2.1

8.3.0

2009-09

CT-45

CP-090674

0452

1

Corrections for detach procedure

8.2.1

8.3.0

2009-09

CT-45

CP-090675

0459

1

Paging for SMS messages

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0461

1

Clarification of the abnormal case in the attach procedure

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0469

1

Miscelleneous corrections to references and incorrect aspects of the specification

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0479

2

Radio capability handling

8.2.1

8.3.0

2009-09

CT-45

CP-090653

0481

3

UE handling unknown QCI value received from the network

8.2.1

8.3.0

2009-09

CT-45

CP-090652

0482

1

Local deactivation of GBR EPS bearer context at MME during RLF

8.2.1

8.3.0

2009-09

CT-45

CP-090682

0487

1

Graphs for paging procedures

8.2.1

8.3.0

2009-09

CT-45

CP-090650

0490

Clarification of bearer context deactivation procedure and correction for ESM cause name

8.2.1

8.3.0

2009-09

CT-45

CP-090675

0494

1

Parameters for SMS over SGs charging

8.2.1

8.3.0

2009-09

CT-45

CP-090682

0331

2

Clarifications related to security mode control procedure

8.3.0

9.0.0

2009-09

CT-45

CP-090694

0341

2

Paging Optimization

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0342

1

Including call type "emergency calls"

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0343

1

Introducing reject cause value for emergency service over EPS

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0347

3

Bearer resource allocation for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0348

4

PDN Connection for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0349

3

Types of EMM procedures for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0351

3

Authentication failure for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0352

2

Limited service state attach for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0353

4

Emergency service security

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0356

2

Emergency service authentication

8.3.0

9.0.0

2009-09

CT-45

CP-090682

0366

2

Clarify terminology of PTI assignment in bearer context

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0422

1

Null algorithm for integrity protection

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0433

2

UE states and attach for emergency services

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0440

1

Update the forbidden TAI list in the limited state

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0441

1

Bearer resource modification for emergency bearer

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0444

1

Support indications for IMS Voice over PS session and emergency call

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0456

2

Clarification about the UE handling with the TAI list in the forbidden TA

8.3.0

9.0.0

2009-09

CT-45

CP-090690

0464

1

GUTI allocation for the UE without USIM

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0466

2

Handling of attach rejection for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0468

2

Deactivating non-emergency bearers

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0473

3

Limited service state attach for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0474

1

Detach on timeout for emergency service

8.3.0

9.0.0

2009-09

CT-45

CP-090689

0476

1

HSS detach request and deactivate non-emergency bearers

8.3.0

9.0.0

2009-09

CT-45

CP-090694

0483

1

Update of allowed CSG list after successful manual selection of a CSG cell in a different PLMN

8.3.0

9.0.0

2009-09

CT-45

CP-090682

0493

1

Discard unencrypted NAS messages

8.3.0

9.0.0

2009-12

CT-46

CP-090922

0485

5

ESM retransmission and PTI mismatch issue

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0496

2

Stop paging optimization for emergency attached UE

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0497

4

RRC establishment cause for Emergency Service

9.0.0

9.1.0

2009-12

CT-46

CP-090935

0498

3

Clarification on the Closed mode CSG cell

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0499

2

Corrections for description of UE behaviour in state EMM-REGISTERED

9.0.0

9.1.0

2009-12

CT-46

CP-090935

0500

3

Operator CSG List

9.0.0

9.1.0

2009-12

CT-46

CP-090899

0505

1

Mapped QCI Handling in UE

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0507

1

Correction on Timer handling

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0512

Correction of criterion to trigger TAU

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0513

1

Specification of EPS emergency bearer services attach rules

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0515

4

TAU authentication while attached for emergency services

9.0.0

9.1.0

2009-12

CT-46

CP-090915

0518

3

UE mode of operation selection corrections and additions

9.0.0

9.1.0

2009-12

CT-46

CP-090935

0521

4

Processing the reject cause code #25 for the Operator CSG List

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0523

Deactivating non-emergency bearers

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0524

3

Clarification for TAU trigger for NAS recovery

9.0.0

9.1.0

2009-12

CT-46

CP-090916

0526

4

Correction to the SMS paging procedure

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0529

1

Correction to conditions for EMM initiating service request

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0530

EMM state machine on the UE side for emergency attach

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0534

4

EPS security context storage while emergency EPS security context exists

9.0.0

9.1.0

2009-12

CT-46

CP-090899

0540

2

From MBR of default PDP context to APN-AMBR of default EPS bearer

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0542

1

Correction of length values for ESM message container IEIs

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0546

1

Correction to SMC procedure for establishment of mapped EPS security context in EMM-IDLE

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0548

1

Correction to establishment of mapped EPS security context during inter-sytem handover

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0550

1

Correction to the storage of the EPS security context

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0552

4

Correction to the EPS security context handling

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0554

2

Correction to the EPS authentication procedure

9.0.0

9.1.0

2009-12

CT-46

CP-090899

0556

4

Transition to the EMM-DEREGISTERED state and EPS security context actions

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0562

4

Clarification of local detach

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0563

2

Clarifications on EPS security and minor corrections

9.0.0

9.1.0

2009-12

CT-46

CP-090916

0564

4

Combined Attach and TAU for "SMS only" and "CS fallback not preferred", and related UE behaviour

9.0.0

9.1.0

2009-12

CT-46

CP-090916

0569

2

Ignoring paging for CS fallback to A/Gb or Iu mode by an SMS only UE

9.0.0

9.1.0

2009-12

CT-46

CP-090899

0571

3

Default value for T3412

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0574

2

Enhanced CS fallback to 1xRTT

9.0.0

9.1.0

2009-12

CT-46

CP-090900

0576

5

NAS count handling in idle mode inter-RAT mobility

9.0.0

9.1.0

2009-12

CT-46

CP-090900

0578

2

NAS count handling on inter-RAT mobility

9.0.0

9.1.0

2009-12

CT-46

CP-090899

0580

Integrity protection of DETACH REQUEST

9.0.0

9.1.0

2009-12

CT-46

CP-090926

0581

4

Generic Transport of NAS messages

9.0.0

9.1.0

2009-12

CT-46

CP-090915

0584

1

Clarification of disabling E-UTRAN capabilities

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0585

1

Handling of only Emergency Bearers existing scenarios

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0588

1

Remove Support of Emergency HO from HRPD to E-UTRAN

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0589

1

EMM context handling for emergency attach

9.0.0

9.1.0

2009-12

CT-46

CP-090916

0590

2

Detach for "SMS only"

9.0.0

9.1.0

2009-12

CT-46

CP-090915

0592

1

1xCSFB triggers for RRC establishment

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0593

2

Detach with re-attach required

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0594

Paging cycles for EPS using S-TMSI

9.0.0

9.1.0

2009-12

CT-46

CP-090900

0598

1

Defining the value of NAS COUNTs

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0602

Correcting the handling of multiple authentication failures in the UE

9.0.0

9.1.0

2009-12

CT-46

CP-090899

0604

1

Handling of missing NAS Securirty Mode Complete when generating mapped context

9.0.0

9.1.0

2009-12

CT-46

CP-090900

0606

1

Security handling when NAS COUNT wrap around

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0607

2

Deactivate non-EMC bearers with CSG ID not in allowed CSG list

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0611

1

Introduction of generic notification procedure

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0615

1

Clarifications on security

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0618

1

Rules for integrity protection with NULL algorithm

9.0.0

9.1.0

2009-12

CT-46

CP-090899

0620

1

TFT corrections

9.0.0

9.1.0

2009-12

CT-46

CP-090922

0621

2

Interpretation of GPRS timer value of 0

9.0.0

9.1.0

2009-12

CT-46

CP-090930

0625

1

Handling authentication failure during TAU

9.0.0

9.1.0

2009-12

CT-46

CP-090935

0626

1

Removal of definition of Allowed CSG list

9.0.0

9.1.0

2009-12

CT-46

CP-090916

0629

1

Abnormal cases in the UE for "SMS only" and "CS Fallback not preferred"

9.0.0

9.1.0

2009-12

CT-46

CP-090898

0633

2

Correction to the NAS security mode control procedure

9.0.0

9.1.0

2009-12

CT-46

CP-091054

0637

2

Alignment with TS23.401 caused by changing the term CSFB to "CSFB and SMS over SGs".

9.0.0

9.1.0

2009-12

CT-46

CP-090919

0567

5

Protecting the allowed CSG list

9.0.0

9.1.0

2010-03

CT-47

CP-100144

0587

3

Deactive ISR for UE attached for emergency bearer services

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0624

3

EPS Bearer Context Synchronization during Extended Service Request

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0639

1

Correction of MME DL NAS COUNT at handover

9.1.0

9.2.0

2010-03

CT-47

CP-100139

0640

1

Inclusion of routing identifier for generic NAS transport

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0641

Tracking Area Update Procedure

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0642

1

UE Initiated Detach Procedure

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0643

UE Substate PLMN Search

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0647

2

Security at idle mobility from E-UTRAN to UTRAN/GERAN

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0657

UE behavior after EPS bearer context deactivation

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0660

2

Correction of used parameter in coordination between ESM and SM

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0664

1

Store EPS security context at state transition to EMM-DEREGISTERED

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0665

1

Definition of attached for emergency bearer service

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0667

2

Defining Selective camping capability IE

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0668

1

Security handling when NAS COUNT wrap around

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0670

1

Deletion of RAND and RES in the UE

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0671

1

Add packet filters to existing TFT

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0672

1

CSG subcription expiration and non-emergency bearer deactivation

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0673

Clarification of IMEI used for EMC attach

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0674

1

Correction on the security protection of the NAS message

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0675

1

Handling of authentication failure in EMC cases

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0677

2

EPS security context handling in detach procedure

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0679

1

Re-Authentication after intergity check failure of TAU Request

9.1.0

9.2.0

2010-03

CT-47

CP-100148

0682

Use of Cause #25 when UE’s subscription to CSG has expired – 24.301

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0685

Correction on E-UTRAN Deactivate ISR timer

9.1.0

9.2.0

2010-03

CT-47

CP-100139

0686

1

Retransmission of non-transmistted LPP PDUs

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0693

2

TAU request and ciphering in connected mode

9.1.0

9.2.0

2010-03

CT-47

CP-100139

0696

2

CS Fallback for MO-LR in Rel9

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0700

1

Add reactivation requested cause code to EPS

9.1.0

9.2.0

2010-03

CT-47

CP-100106

0702

1

Deletion of mapped EPS security context when I-RAT HO fails

9.1.0

9.2.0

2010-03

CT-47

CP-100126

0704

UE behaviour corrections for ‘SMS only’

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0705

Definition of non-emergency EPS bearer context

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0711

2

Pre Rel8 QoS mapping when this QoS is not received while on E-UTRAN

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0713

1

Clarification of Integrity protection of Service Request in section 4.4.3.3

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0714

1

No reset of DL NAS Count on Security Mode Command accepted by the UE

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0716

2

Attach for emergency bearer services to a network not supporting EM BS

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0718

1

Security Mode Command using NULL algos during TAU for normal attached UE

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0720

1

Retransmission of PDN connectivity request for emergency bearer services

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0724

Correction of access class bit 10 handling

9.1.0

9.2.0

2010-03

CT-47

CP-100144

0725

2

Mobility aspects of Emergency attached UEs

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0726

1

Arrange definitions in alphabetical order

9.1.0

9.2.0

2010-03

CT-47

CP-100062

0708

3

Authentication Procedure after Inter PLMN Handover

9.1.0

9.2.0

2010-03

CT-47

CP-100134

0727

3

Alignment of TAI list boundary with 2G/3G LA boundary

9.1.0

9.2.0

2010-03

CT-47

CP-100210

0730

2

Correct terminating domain selection for IMS voice UEs

9.1.0

9.2.0

2010-06

CT#48

CP-100354

0722

3

Avoiding rejection of a CS fallback due to CSG subscription expiry

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0735

1

eKSI value setting for no valid EPS security context

9.2.0

9.3.0

2010-06

CT#48

CP-100360

0736

4

Authentication procedure for emergency services

9.2.0

9.3.0

2010-06

CT#48

CP-100360

0746

2

Handover to EUTRAN including NULL algos

9.2.0

9.3.0

2010-06

CT#48

CP-100360

0748

1

Authentication failure by UE while it has a PDN connection for emergency bearer services

9.2.0

9.3.0

2010-06

CT#48

CP-100362

0749

3

Add HeNB name

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0751

1

Correction on request type

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0752

1

Correction of conditions for TAU and ISR deactivation for T-ADS

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0753

2

CSFB corrections in Service request procedure

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0754

1

No NAS retransmission of SMS messages

9.2.0

9.3.0

2010-06

CT#48

CP-100348

0757

1

Voice domain preference alignments

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0759

Update status for cause #9 and #10

9.2.0

9.3.0

2010-06

CT#48

CP-100349

0761

1

Combined TAU trigger after SRVCC

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0763

1

Cause #39

9.2.0

9.3.0

2010-06

CT#48

CP-100360

0767

3

Clarification to establishment cause used by a UE in case of EMC procedure.

9.2.0

9.3.0

2010-06

CT#48

CP-100360

0768

2

Clarifications to expirey of Periodic RAU and mobile Reachable timer in case of EMC

9.2.0

9.3.0

2010-06

CT#48

CP-100350

0770

2

Clarification to network initiated detach procedure with cause #25

9.2.0

9.3.0

2010-06

CT#48

CP-100360

0771

1

Handling EPS Security Contexts

9.2.0

9.3.0

2010-06

CT#48

CP-100348

0775

2

Correction to UE mode of operation

9.2.0

9.3.0

2010-06

CT#48

CP-100339

0777

3

Correction to mapping of EPS QoS to pre-Rel-8 QoS

9.2.0

9.3.0

2010-06

CT#48

CP-100354

0783

1

Correction of selective camping IE inclusion requirement for 1x CS fallback capable UE

9.2.0

9.3.0

2010-06

CT#48

CP-100360

0784

2

Emergency attach reject from EMM in shared networks

9.2.0

9.3.0

2010-09

CT#49

CP-100501

0739

4

Corrections to UE mode of operation selection taking into account the UE’s availability for voice calls in the IMS

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0786

2

Handling of Detach Procedure for non-EPS services on a CSG cell which is no longer valid for the UE.and IMS EMG call is active.

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0787

1

Emergency security context creation at standalone SMC

9.3.0

9.4.0

2010-09

CT#49

CP-100501

0789

1

Adding spec reference to ensure QoS alignment

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0794

2

Skip Authentication for Emergency Services

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0797

1

Clarification to timer T3418 and T3420 timer description in EMC case.

9.3.0

9.4.0

2010-09

CT#49

CP-100501

0812

2

On UE handling of 1xCSFB failure due to lower layer failure

9.3.0

9.4.0

2010-09

CT#49

CP-100501

0820

1

Allowing the UE to send a request for emergency call when the timer T3442 is running

9.3.0

9.4.0

2010-09

CT#49

CP-100495

0832

3

Correction on CS Fallback procedure using Release with Redirection

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0842

1

Clarification to an emergency PDN connection establishment procedure.

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0844

1

Handling of collision of Network Initiated Detach procdure with Service Request procedure and TAU procedure.

9.3.0

9.4.0

2010-09

CT#49

CP-100495

0850

1

No EPS bearer context activated during combined tracking area update

9.3.0

9.4.0

2010-09

CT#49

CP-100485

0852

1

Context transfer on inter-system change from A/Gb mode or Iu mode

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0854

1

Skip authentication during TAU in EMC cases

9.3.0

9.4.0

2010-09

CT#49

CP-100506

0859

1

Local bearer deactivation and UE status

9.3.0

9.4.0

2010-09

CT#49

CP-100501

0868

1

Inclusion of transaction identifier

9.3.0

9.4.0

2010-09

CT#49

CP-100501

0871

1

Alignment with 23.401 for ESM cause value #52 "single address bearers only allowed"

9.3.0

9.4.0

2010-09

CT#49

CP-100517

0758

2

Local ISR deactivation in the UE when T3312 has expired

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0773

2

Correcting ISR handling in UE

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0788

1

Adding a definition of the term "Lower layer failure"

9.4.0

10.0.0

2010-09

CT#49

CP-100514

0799

1

PDN connection redirection in SIPTO scenario

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0800

3

CSFB rejected by network without inter system change

9.4.0

10.0.0

2010-09

CT#49

CP-100514

0801

1

Clarification on PDN connection re-activation

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0802

1

Correction for value setting of the mobile reachable timer

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0804

2

Abnormal case handling for SMC procedure

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0807

1

Clarifying the presence of APN IE

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0808

CS fallback alignments

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0815

1

Editorial corrections in definitions

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0817

2

Fix ambiguity in the UE security capability information element

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0819

Editorial corrections to 24.301

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0823

1

Clarification to set TIN parameter in Attach, Tracking,Detach and PDN connectivity procedure.

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0835

1

Correction of EMM main states in the UE

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0837

2

Correction of network initiated detach procedure with EMM cause #2

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0845

1

Clarification of TAI list assignment for network sharing

9.4.0

10.0.0

2010-09

CT#49

CP-100520

0847

2

Handling of cause #27 (missing or unknown APN)

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0853

1

Removal of ESM cause #46

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0855

1

Combined attached UE’s behavior during PTAU with reject cause #7 or #14

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0856

1

Correction on LIMITED-SERVIC substate

9.4.0

10.0.0

2010-09

CT#49

CP-100514

0857

1

Network initiated Detach procedure completion by the UE

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0858

2

Support of IPv6 Prefix Delegation

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0862

1

Collision of UE requested bearer resource allocation and EPS bearer context deactivation

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0863

1

Establish radio bearer due to downlink ESM signaling pending

9.4.0

10.0.0

2010-09

CT#49

CP-100517

0866

1

EMM state transitions in MME

9.4.0

10.0.0

2010-09

CT#49

CP-100520

0872

Editorial correction of security context handling for network initiated detach procedure initiation

9.4.0

10.0.0

2010-12

CT#50

CP-100760

0877

1

Attach with IMSI

10.0.0

10.1.0

2010-12

CT#50

CP-100760

0878

5

Extended Tracking Area Update Timer

10.0.0

10.1.0

2010-12

CT#50

CP-100760

0879

4

Rejection due to per APN congestion