Tech-
invite
3GPP
space
IETF
RFCs
SIP
Quick
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TS 24.301
Word version: 17.4.1
1…
3…
4…
4.3…
5…
5.4…
6…
7…
8…
8.3…
9…
10…
5.4
EMM common procedures
5.4.1
GUTI reallocation procedure
5.4.2
Authentication procedure
5.4.3
Security mode control procedure
5.4.4
Identification procedure
5.4.5
EMM information procedure
5.5
EMM specific procedures
5.5.1
Attach procedure
5.5.2
Detach procedure
5.5.3
Tracking area updating procedure (S1 mode only)
5.5.4
eCall inactivity procedure
5.5.5
Tracking area update request message (for N1 mode only)
5.5.6
Attach request message (for N1 mode only)
5.6
EMM connection management procedures (S1 mode only)
5.6.1
Service request procedure
5.6.2
Paging procedure
5.6.3
Transport of NAS messages procedure
5.6.4
Generic transport of NAS messages procedure
5.7
Reception of an EMM STATUS message by an EMM entity
...
5.4
EMM common procedures
Word‑p. 97
5.4.1
GUTI reallocation procedure
Word‑p. 97
5.4.1.1
General
Word‑p. 97
5.4.1.2
GUTI reallocation initiation by the network
Word‑p. 97
5.4.1.3
GUTI reallocation completion by the UE
Word‑p. 98
5.4.1.4
GUTI reallocation completion by the network
Word‑p. 98
5.4.1.5
Abnormal cases in the UE
Word‑p. 98
5.4.1.6
Abnormal cases on the network side
Word‑p. 98
5.4.2
Authentication procedure
Word‑p. 100
5.4.2.1
General
Word‑p. 100
5.4.2.2
Authentication initiation by the network
Word‑p. 100
5.4.2.3
Authentication response by the UE
Word‑p. 101
5.4.2.4
Authentication completion by the network
Word‑p. 102
5.4.2.5
Authentication not accepted by the network
Word‑p. 102
5.4.2.6
Authentication not accepted by the UE
Word‑p. 103
5.4.2.7
Abnormal cases
Word‑p. 103
5.4.3
Security mode control procedure
Word‑p. 108
5.4.3.1
General
Word‑p. 108
5.4.3.2
NAS security mode control initiation by the network
Word‑p. 109
5.4.3.3
NAS security mode command accepted by the UE
Word‑p. 112
5.4.3.4
NAS security mode control completion by the network
Word‑p. 113
5.4.3.5
NAS security mode command not accepted by the UE
Word‑p. 113
5.4.3.6
Abnormal cases in the UE
Word‑p. 113
5.4.3.7
Abnormal cases on the network side
Word‑p. 114
5.4.4
Identification procedure
Word‑p. 115
5.4.4.1
General
Word‑p. 115
5.4.4.2
Identification initiation by the network
Word‑p. 115
5.4.4.3
Identification response by the UE
Word‑p. 115
5.4.4.4
Identification completion by the network
Word‑p. 115
5.4.4.5
Abnormal cases in the UE
Word‑p. 115
5.4.4.6
Abnormal cases on the network side
Word‑p. 116
5.4.5
EMM information procedure
Word‑p. 117
5.4.5.1
General
Word‑p. 117
5.4.5.2
EMM information procedure initiation by the network
Word‑p. 117
5.4.5.3
EMM information procedure in the UE
Word‑p. 117
5.4.5.4
Abnormal cases on the network side
Word‑p. 117
5.5
EMM specific procedures
Word‑p. 118
5.5.1
Attach procedure
Word‑p. 118
5.5.1.1
General
Word‑p. 118
5.5.1.2
Attach procedure for EPS services
Word‑p. 119
5.5.1.2.1
General
Word‑p. 119
5.5.1.2.2
Attach procedure initiation
Word‑p. 119
5.5.1.2.3
EMM common procedure initiation
Word‑p. 123
5.5.1.2.4
Attach accepted by the network
Word‑p. 123
5.5.1.2.4A
Attach successful for EPS services and not accepted for SMS services
|R13|
Word‑p. 129
5.5.1.2.5
Attach not accepted by the network
Word‑p. 130
5.5.1.2.5A
Attach for emergency bearer services not accepted by the network
|R9|
Word‑p. 136
5.5.1.2.5B
Attach for initiating a PDN connection for emergency bearer services not accepted by the network
|R9|
Word‑p. 137
5.5.1.2.5B1
Attach by a UE transferring an emergency PDU session using a standalone PDN CONNECTIVITY REQUEST message
|R16|
Word‑p. 138
5.5.1.2.5C
Attach for access to RLOS not accepted by the network
|R16|
Word‑p. 139
5.5.1.2.6
Abnormal cases in the UE
Word‑p. 139
5.5.1.2.6A
Abnormal cases in the UE, SMS services not accepted
|R13|
Word‑p. 143
5.5.1.2.7
Abnormal cases on the network side
Word‑p. 143
5.5.1.3
Combined attach procedure for EPS services and non-EPS services (S1 mode only)
Word‑p. 145
5.5.1.3.1
General
Word‑p. 145
5.5.1.3.2
Combined attach procedure initiation
Word‑p. 145
5.5.1.3.3
EMM common procedure initiation
Word‑p. 146
5.5.1.3.4
Combined attach accepted by the network
Word‑p. 146
5.5.1.3.4.1
General
Word‑p. 146
5.5.1.3.4.2
Combined attach successful
Word‑p. 146
5.5.1.3.4.3
Combined attach successful for EPS services only
Word‑p. 147
5.5.1.3.5
Combined attach not accepted by the network
Word‑p. 148
5.5.1.3.6
Abnormal cases in the UE
Word‑p. 154
5.5.1.3.7
Abnormal cases on the network side
Word‑p. 155
5.5.2
Detach procedure
Word‑p. 155
5.5.2.1
General
Word‑p. 155
5.5.2.2
UE initiated detach procedure
Word‑p. 156
5.5.2.2.1
UE initiated detach procedure initiation
Word‑p. 156
5.5.2.2.2
UE initiated detach procedure completion for EPS services only
Word‑p. 157
5.5.2.2.3
UE initiated combined detach procedure completion
Word‑p. 157
5.5.2.2.4
Abnormal cases in the UE
Word‑p. 158
5.5.2.2.5
Abnormal cases on the network side
Word‑p. 160
5.5.2.3
Network initiated detach procedure
Word‑p. 160
5.5.2.3.1
Network initiated detach procedure initiation
Word‑p. 160
5.5.2.3.2
Network initiated detach procedure completion by the UE
Word‑p. 161
5.5.2.3.3
Network initiated detach procedure completion by the network
Word‑p. 165
5.5.2.3.4
Abnormal cases in the UE
Word‑p. 165
5.5.2.3.5
Abnormal cases on the network side
Word‑p. 166
5.5.3
Tracking area updating procedure (S1 mode only)
Word‑p. 167
5.5.3.1
General
Word‑p. 167
5.5.3.2
Normal and periodic tracking area updating procedure
Word‑p. 169
5.5.3.2.1
General
Word‑p. 169
5.5.3.2.2
Normal and periodic tracking area updating procedure initiation
Word‑p. 169
5.5.3.2.3
EMM common procedure initiation
Word‑p. 175
5.5.3.2.4
Normal and periodic tracking area updating procedure accepted by the network
Word‑p. 176
5.5.3.2.4A
Tracking area updating successful for EPS services and not accepted for SMS services
|R13|
Word‑p. 186
5.5.3.2.5
Normal and periodic tracking area updating procedure not accepted by the network
Word‑p. 187
5.5.3.2.5A
Tracking area updating procedure for initiating a PDN connection for emergency bearer services not accepted by the network
|R9|
Word‑p. 194
5.5.3.2.5B
Tracking area updating for access to RLOS not accepted by the network
|R16|
Word‑p. 194
5.5.3.2.6
Abnormal cases in the UE
Word‑p. 195
5.5.3.2.6A
Abnormal cases in the UE, SMS services not accepted
|R13|
Word‑p. 201
5.5.3.2.7
Abnormal cases on the network side
Word‑p. 201
5.5.3.3
Combined tracking area updating procedure
Word‑p. 203
5.5.3.3.1
General
Word‑p. 203
5.5.3.3.2
Combined tracking area updating procedure initiation
Word‑p. 203
5.5.3.3.3
EMM common procedure initiation
Word‑p. 206
5.5.3.3.4
Combined tracking area updating procedure accepted by the network
Word‑p. 206
5.5.3.3.4.1
General
Word‑p. 206
5.5.3.3.4.2
Combined tracking area updating successful
Word‑p. 206
5.5.3.3.4.3
Combined tracking area updating successful for EPS services only
Word‑p. 207
5.5.3.3.5
Combined tracking area updating procedure not accepted by the network
Word‑p. 209
5.5.3.3.6
Abnormal cases in the UE
Word‑p. 217
5.5.3.3.7
Abnormal cases on the network side
Word‑p. 218
5.5.4
eCall inactivity procedure
|R14|
Word‑p. 218
5.5.5
Tracking area update request message (for N1 mode only)
|R15|
Word‑p. 218
5.5.6
Attach request message (for N1 mode only)
|R16|
Word‑p. 219
5.6
EMM connection management procedures (S1 mode only)
Word‑p. 219
5.6.1
Service request procedure
Word‑p. 219
5.6.1.1
General
Word‑p. 219
5.6.1.2
Service request procedure initiation
Word‑p. 224
5.6.1.2.1
UE is not using EPS services with control plane CIoT EPS optimization
|R13|
Word‑p. 224
5.6.1.2.2
UE is using EPS services with control plane CIoT EPS optimization
|R13|
Word‑p. 225
5.6.1.3
EMM common procedure initiation
Word‑p. 225
5.6.1.4
Service request procedure accepted by the network
Word‑p. 225
5.6.1.4.1
UE is not using EPS services with control plane CIoT EPS optimization
|R13|
Word‑p. 225
5.6.1.4.2
UE is using EPS services with control plane CIoT EPS optimization
|R13|
Word‑p. 228
5.6.1.5
Service request procedure not accepted by the network
Word‑p. 232
5.6.1.5A
Service request procedure for initiating a PDN connection for emergency bearer services not accepted by the network
|R9|
Word‑p. 241
5.6.1.5B
Service request procedure for UE attached for access to RLOS not accepted by the network
|R16|
Word‑p. 241
5.6.1.6
Abnormal cases in the UE
Word‑p. 242
5.6.1.7
Abnormal cases on the network side
Word‑p. 249
5.6.2
Paging procedure
Word‑p. 250
5.6.2.1
General
Word‑p. 250
5.6.2.2
Paging for EPS services
Word‑p. 250
5.6.2.2.1
Paging for EPS services through E-UTRAN using S-TMSI
Word‑p. 250
5.6.2.2.1.1
General
Word‑p. 250
5.6.2.2.1.2
Abnormal cases on the network side
Word‑p. 252
5.6.2.2.1.3
Abnormal cases in the UE
Word‑p. 252
5.6.2.2.2
Paging for EPS services through E-UTRAN using IMSI
Word‑p. 252
5.6.2.3
Paging for CS fallback to A/Gb or Iu mode
Word‑p. 253
5.6.2.3.1
General
Word‑p. 253
5.6.2.3.2
Abnormal cases in the UE
Word‑p. 254
5.6.2.3.3
Abnormal cases on the network side
|R12|
Word‑p. 254
5.6.2.4
Paging for SMS
Word‑p. 254
5.6.3
Transport of NAS messages procedure
Word‑p. 255
5.6.3.1
General
Word‑p. 255
5.6.3.2
UE initiated transport of NAS messages
Word‑p. 255
5.6.3.3
Network initiated transport of NAS messages
Word‑p. 255
5.6.3.4
Abnormal cases in the UE
|R9|
Word‑p. 255
5.6.3.5
Abnormal cases on the network side
|R9|
Word‑p. 256
5.6.4
Generic transport of NAS messages procedure
|R9|
Word‑p. 256
5.6.4.1
General
Word‑p. 256
5.6.4.2
UE initiated generic transport of NAS messages
Word‑p. 256
5.6.4.3
Network initiated transport of NAS messages
Word‑p. 256
5.6.4.4
Abnormal cases in the UE
Word‑p. 257
5.6.4.5
Abnormal cases on the network side
Word‑p. 257
5.7
Reception of an EMM STATUS message by an EMM entity
Word‑p. 257