Ts 129274v130400p

ETSI TS 1
129 274 V13.4.0 (2016

16-03)
TECHNICAL SPECIFICATION
ION
Universal Mobile Tel

elecommunications System ((UMTS);
LTE;
3GPP Evolv
olved Packet System (EPS);
Evolved Generaral Packet Radio Service (GPR
PRS)
Tunnelling Protoc
tocol for Control plane (GTPv2
v2-C);
Stage 3
(3GPP TS 29.2.274 version 13.4.0 Release 13)
13
3GPP TS 29.274 version 13.4.0 Release 13 1 ETSI TS 129 274 V13.4.0 (2016-03)
Reference
RTS/TSGC-0429274vd40
Keywords
LTE, UMTS
ETSI
650 Route des Lucioles

F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C

Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:

http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2016.

All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
Intellectual Property Rights

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Modal verbs terminology....................................................................................................................................2
Foreword...........................................................................................................................................................10
1 Scope ......................................................................................................................................................11
2 References ..............................................................................................................................................11
3 Definitions, symbols and abbreviations .................................................................................................14
3.1 Definitions ........................................................................................................................................................ 14
3.2 Symbols ............................................................................................................................................................ 15
3.3 Abbreviations ................................................................................................................................................... 15
4 General ...................................................................................................................................................16
4.1 GTP Tunnel ...................................................................................................................................................... 16
4.2 Protocol stack ................................................................................................................................................... 16
4.2.0 General........................................................................................................................................................ 16
4.2.1 UDP header and port numbers .................................................................................................................... 17
4.2.1.0 General .................................................................................................................................................. 17
4.2.1.1 Initial Messages..................................................................................................................................... 18
4.2.1.2 Triggered Messages .............................................................................................................................. 18
4.2.1.3 Piggybacked Messages.......................................................................................................................... 18
4.2.2 IP header and IP addresses.......................................................................................................................... 18
4.2.2.1 Initial Messages..................................................................................................................................... 18
4.2.2.2 Triggered Messages .............................................................................................................................. 19
4.2.2.3 Piggybacked Messages.......................................................................................................................... 19
4.2.3 Layer 2 ........................................................................................................................................................ 19
4.2.4 Layer 1 ........................................................................................................................................................ 19
4.2.5 Messages with GTPv2 defined replies: Classification of Initial and Triggered Messages ......................... 19
4.3 Transmission Order and Bit Definitions ........................................................................................................... 20
5 GTP Header for Control Plane ...............................................................................................................20
5.1 General format.................................................................................................................................................. 20
5.2 Control Plane GTP Extension Header .............................................................................................................. 21
5.3 GTP-C header for Echo and Version Not Supported Indication messages ...................................................... 21
5.4 EPC specific GTP-C header ............................................................................................................................. 21
5.5 Usage of the GTPv2-C Header ......................................................................................................................... 22
5.5.1 General........................................................................................................................................................ 22
5.5.2 Conditions for sending TEID=0 in GTPv2-C header ................................................................................. 23
5.6 Format of the GTPv2-C Message ..................................................................................................................... 24
6 GTP-C Message Types and Message Formats .......................................................................................25
6.0 General ...................................................................................................................................................25
6.1 Message Format and Type values .................................................................................................................... 25
6.1.0 Message Type ............................................................................................................................................. 25
6.1.1 Presence requirements of Information Elements ........................................................................................ 28
6.1.2 Grouped Information Elements................................................................................................................... 29
6.1.3 Information Element instance ..................................................................................................................... 30
6.2 Message Granularity......................................................................................................................................... 30
7 GTP-C messages ....................................................................................................................................31
7.1 Path Management Messages............................................................................................................................. 31
7.1.0 General........................................................................................................................................................ 31
7.1.1 Echo Request .............................................................................................................................................. 31
7.1.2 Echo Response ............................................................................................................................................ 32
7.1.3 Version Not Supported Indication .............................................................................................................. 32
ETSI
7.2 Tunnel Management Messages ........................................................................................................................ 32

7.2.0 General........................................................................................................................................................ 32
7.2.1 Create Session Request ............................................................................................................................... 32
7.2.2 Create Session Response ............................................................................................................................ 48
7.2.3 Create Bearer Request ................................................................................................................................ 58
7.2.4 Create Bearer Response .............................................................................................................................. 63
7.2.5 Bearer Resource Command ........................................................................................................................ 68
7.2.6 Bearer Resource Failure Indication ............................................................................................................ 71
7.2.7 Modify Bearer Request ............................................................................................................................... 73
7.2.8 Modify Bearer Response ............................................................................................................................ 87
7.2.9 Delete Session Request and Delete Bearer Request ................................................................................... 95
7.2.9.1 Delete Session Request ......................................................................................................................... 95
7.2.9.2 Delete Bearer Request ......................................................................................................................... 100
7.2.10 Delete Session Response and Delete Bearer Response ............................................................................. 105
7.2.10.1 Delete Session Response ..................................................................................................................... 105
7.2.10.2 Delete Bearer Response ...................................................................................................................... 110
7.2.11 Downlink Data Notification messages ...................................................................................................... 114
7.2.11.1 Downlink Data Notification ................................................................................................................ 114
7.2.11.2 Downlink Data Notification Acknowledge ......................................................................................... 118
7.2.11.3 Downlink Data Notification Failure Indication ................................................................................... 119
7.2.12 Delete Indirect Data Forwarding Tunnel Request .................................................................................... 120
7.2.13 Delete Indirect Data Forwarding Tunnel Response .................................................................................. 120
7.2.14 Modify Bearer Command and Failure Indication ..................................................................................... 121
7.2.14.1 Modify Bearer Command ................................................................................................................... 121
7.2.14.2 Modify Bearer Failure Indication ........................................................................................................ 123
7.2.15 Update Bearer Request ............................................................................................................................. 125
7.2.16 Update Bearer Response ........................................................................................................................... 132
7.2.17 Delete Bearer Command and Failure Indication ....................................................................................... 137
7.2.17.1 Delete Bearer Command ..................................................................................................................... 137
7.2.17.2 Delete Bearer Failure Indication ......................................................................................................... 139
7.2.18 Create Indirect Data Forwarding Tunnel Request .................................................................................... 141
7.2.19 Create Indirect Data Forwarding Tunnel Response .................................................................................. 144
7.2.20 Void .......................................................................................................................................................... 145
7.2.21 Release Access Bearers Request ............................................................................................................... 145
7.2.22 Release Access Bearers Response ............................................................................................................ 146
7.2.23 Stop Paging Indication .............................................................................................................................. 148
7.2.24 Modify Access Bearers Request ............................................................................................................... 148
7.2.25 Modify Access Bearers Response ............................................................................................................. 150
7.2.26 Remote UE Report Notification................................................................................................................ 153
7.2.27 Remote UE Report Acknowledge ............................................................................................................. 153
7.3 Mobility Management Messages .................................................................................................................... 154
7.3.1 Forward Relocation Request ..................................................................................................................... 154
7.3.2 Forward Relocation Response .................................................................................................................. 162
7.3.3 Forward Relocation Complete Notification .............................................................................................. 166
7.3.4 Forward Relocation Complete Acknowledge ........................................................................................... 166
7.3.5 Context Request ........................................................................................................................................ 167
7.3.6 Context Response ..................................................................................................................................... 169
7.3.7 Context Acknowledge............................................................................................................................... 177
7.3.8 Identification Request ............................................................................................................................... 178
7.3.9 Identification Response............................................................................................................................. 179
7.3.10 Forward Access Context Notification ....................................................................................................... 180
7.3.11 Forward Access Context Acknowledge .................................................................................................... 181
7.3.12 Detach Notification ................................................................................................................................... 181
7.3.13 Detach Acknowledge ................................................................................................................................ 182
7.3.14 Change Notification Request .................................................................................................................... 182
7.3.15 Change Notification Response .................................................................................................................. 185
7.3.16 Relocation Cancel Request ....................................................................................................................... 186
7.3.17 Relocation Cancel Response ..................................................................................................................... 187
7.3.18 Configuration Transfer Tunnel ................................................................................................................. 187
7.3.19 RAN Information Relay............................................................................................................................ 187
7.3.20 ISR Status Indication ................................................................................................................................ 188
7.3.21 UE Registration Query Request ................................................................................................................ 188
ETSI
7.3.22 UE Registration Query Response ............................................................................................................. 189

7.4 CS Fallback and SRVCC related messages .................................................................................................... 189
7.4.1 Suspend Notification................................................................................................................................. 189
7.4.2 Suspend Acknowledge .............................................................................................................................. 191
7.4.3 Resume Notification ................................................................................................................................. 191
7.4.4 Resume Acknowledge .............................................................................................................................. 192
7.4.5 CS Paging Indication ................................................................................................................................ 192
7.4.6 Alert MME Notification ........................................................................................................................... 193
7.4.7 Alert MME Acknowledge ........................................................................................................................ 193
7.4.8 UE Activity Notification ........................................................................................................................... 193
7.4.9 UE Activity Acknowledge ........................................................................................................................ 194
7.5 Non-3GPP access related messages ............................................................................................................... 194
7.5.1 Create Forwarding Tunnel Request .......................................................................................................... 194
7.5.2 Create Forwarding Tunnel Response ........................................................................................................ 194
7.6 Reliable Delivery of Signalling Messages...................................................................................................... 195
7.7 Error Handling................................................................................................................................................ 196
7.7.0 Handling Piggybacked Messages ............................................................................................................. 196
7.7.1 Protocol Errors .......................................................................................................................................... 196
7.7.2 Different GTP Versions ............................................................................................................................ 197
7.7.3 GTP Message of Invalid Length ............................................................................................................... 197
7.7.4 Unknown GTP Message ........................................................................................................................... 197
7.7.5 Unexpected GTP Message ........................................................................................................................ 197
7.7.6 Missing Information Elements .................................................................................................................. 198
7.7.7 Invalid Length Information Element ........................................................................................................ 198
7.7.8 Semantically incorrect Information Element ............................................................................................ 199
7.7.9 Unknown or unexpected Information Element ......................................................................................... 199
7.7.10 Repeated Information Elements ................................................................................................................ 199
7.7.11 TFT Error Handling .................................................................................................................................. 200
7.8 Path Failure .................................................................................................................................................... 200
7.9 Restoration and Recovery .............................................................................................................................. 200
7.9.0 General...................................................................................................................................................... 200
7.9.1 Delete PDN Connection Set Request ........................................................................................................ 200
7.9.2 Delete PDN Connection Set Response ..................................................................................................... 200
7.9.3 Update PDN Connection Set Request ....................................................................................................... 201
7.9.4 Update PDN Connection Set Response .................................................................................................... 201
7.9.5 PGW Restart Notification ......................................................................................................................... 202
7.9.6 PGW Restart Notification Acknowledge .................................................................................................. 202
7.9.7 PGW Downlink Triggering Notification .................................................................................................. 203
7.9.8 PGW Downlink Triggering Acknowledge ............................................................................................... 203
7.10 Fallback to GTPv1 mechanism ...................................................................................................................... 204
7.11 Fallback to GTPv0.......................................................................................................................................... 204
7.12 Trace Management Messages......................................................................................................................... 205
7.12.1 Trace Session Activation .......................................................................................................................... 205
7.12.2 Trace Session Deactivation ....................................................................................................................... 205
7.13 MBMS Messages ........................................................................................................................................... 206
7.13.1 MBMS Session Start Request ................................................................................................................... 206
7.13.2 MBMS Session Start Response ................................................................................................................ 207
7.13.3 MBMS Session Update Request ............................................................................................................... 208
7.13.4 MBMS Session Update Response ............................................................................................................ 208
7.13.5 MBMS Session Stop Request ................................................................................................................... 209
7.13.6 MBMS Session Stop Response................................................................................................................. 209
8 GTP-C Information Elements ..............................................................................................................210
8.1 Information Element Types ............................................................................................................................ 210
8.2 Information Element Format .......................................................................................................................... 213
8.2.1 General...................................................................................................................................................... 213
8.2.1A Information Element with an IE Type Extension field ............................................................................. 213
8.2.2 Handling ASN.1/PER encoded parameters .............................................................................................. 214
8.3 International Mobile Subscriber Identity (IMSI) ............................................................................................ 214
8.4 Cause .............................................................................................................................................................. 214
8.5 Recovery (Restart Counter) ............................................................................................................................ 220
8.6 Access Point Name (APN) ............................................................................................................................. 221
ETSI
8.7 Aggregate Maximum Bit Rate (AMBR) ........................................................................................................ 221

8.8 EPS Bearer ID (EBI) ...................................................................................................................................... 221
8.9 IP Address ...................................................................................................................................................... 222
8.10 Mobile Equipment Identity (MEI).................................................................................................................. 222
8.11 MSISDN ......................................................................................................................................................... 222
8.12 Indication........................................................................................................................................................ 222
8.13 Protocol Configuration Options (PCO) .......................................................................................................... 226
8.14 PDN Address Allocation (PAA) .................................................................................................................... 226
8.15 Bearer Quality of Service (Bearer QoS) ......................................................................................................... 227
8.16 Flow Quality of Service (Flow QoS).............................................................................................................. 228
8.17 RAT Type ....................................................................................................................................................... 228
8.18 Serving Network ............................................................................................................................................ 229
8.19 EPS Bearer Level Traffic Flow Template (Bearer TFT) ................................................................................ 229
8.20 Traffic Aggregate Description (TAD) ............................................................................................................ 230
8.21 User Location Information (ULI) ................................................................................................................... 230
8.21.1 CGI field ................................................................................................................................................... 230
8.21.2 SAI field ................................................................................................................................................... 231
8.21.3 RAI field ................................................................................................................................................... 231
8.21.4 TAI field ................................................................................................................................................... 232
8.21.5 ECGI field ................................................................................................................................................. 232
8.21.6 LAI field ................................................................................................................................................... 232
8.22 Fully Qualified TEID (F-TEID) ..................................................................................................................... 232
8.23 TMSI .............................................................................................................................................................. 234
8.24 Global CN-Id .................................................................................................................................................. 235
8.25 S103 PDN Data Forwarding Info (S103PDF) ................................................................................................ 235
8.26 S1-U Data Forwarding (S1UDF).................................................................................................................... 235
8.27 Delay Value .................................................................................................................................................... 236
8.28 Bearer Context................................................................................................................................................ 236
8.29 Charging ID .................................................................................................................................................... 236
8.30 Charging Characteristics ................................................................................................................................ 237
8.31 Trace Information ........................................................................................................................................... 237
8.32 Bearer Flags.................................................................................................................................................... 237
8.33 Void ................................................................................................................................................................ 238
8.34 PDN Type ....................................................................................................................................................... 238
8.35 Procedure Transaction ID (PTI) ..................................................................................................................... 238
8.36 Void ................................................................................................................................................................ 239
8.37 Void ................................................................................................................................................................ 239
8.38 MM Context ................................................................................................................................................... 239
8.39 PDN Connection ............................................................................................................................................ 247
8.40 PDU Numbers ................................................................................................................................................ 247
8.41 Packet TMSI (P-TMSI) .................................................................................................................................. 247
8.42 P-TMSI Signature........................................................................................................................................... 248
8.43 Hop Counter ................................................................................................................................................... 248
8.44 UE Time Zone ................................................................................................................................................ 248
8.45 Trace Reference .............................................................................................................................................. 249
8.46 Complete Request Message ............................................................................................................................ 249
8.47 GUTI .............................................................................................................................................................. 249
8.48 Fully Qualified Container (F-Container) ........................................................................................................ 250
8.49 Fully Qualified Cause (F-Cause) .................................................................................................................... 251
8.50 PLMN ID........................................................................................................................................................ 252
8.51 Target Identification ....................................................................................................................................... 253
8.52 Void ................................................................................................................................................................ 254
8.53 Packet Flow ID ............................................................................................................................................... 254
8.54 RAB Context .................................................................................................................................................. 255
8.55 Source RNC PDCP context info..................................................................................................................... 255
8.56 Port Number ................................................................................................................................................... 255
8.57 APN Restriction ............................................................................................................................................. 256
8.58 Selection Mode ............................................................................................................................................... 256
8.59 Source Identification ...................................................................................................................................... 257
8.60 Void ................................................................................................................................................................ 257
8.61 Change Reporting Action ............................................................................................................................... 257
8.62 Fully qualified PDN Connection Set Identifier (FQ-CSID) ........................................................................... 258
ETSI
8.63 Channel needed .............................................................................................................................................. 259

8.64 eMLPP Priority .............................................................................................................................................. 259
8.65 Node Type ...................................................................................................................................................... 259
8.66 Fully Qualified Domain Name (FQDN) ......................................................................................................... 260
8.67 Private Extension............................................................................................................................................ 260
8.68 Transaction Identifier (TI) .............................................................................................................................. 260
8.69 MBMS Session Duration................................................................................................................................ 261
8.70 MBMS Service Area ...................................................................................................................................... 261
8.71 MBMS Session Identifier ............................................................................................................................... 261
8.72 MBMS Flow Identifier ................................................................................................................................... 262
8.73 MBMS IP Multicast Distribution ................................................................................................................... 262
8.74 MBMS Distribution Acknowledge................................................................................................................. 263
8.75 User CSG Information (UCI) ......................................................................................................................... 263
8.76 CSG Information Reporting Action ............................................................................................................... 264
8.77 RFSP Index .................................................................................................................................................... 264
8.78 CSG ID ........................................................................................................................................................... 265
8.79 CSG Membership Indication (CMI) ............................................................................................................... 265
8.80 Service indicator ............................................................................................................................................. 265
8.81 Detach Type ................................................................................................................................................... 266
8.82 Local Distinguished Name (LDN) ................................................................................................................. 266
8.83 Node Features ................................................................................................................................................. 266
8.84 MBMS Time to Data Transfer ....................................................................................................................... 267
8.85 Throttling........................................................................................................................................................ 267
8.86 Allocation/Retention Priority (ARP) .............................................................................................................. 268
8.87 EPC Timer ...................................................................................................................................................... 269
8.88 Signalling Priority Indication ......................................................................................................................... 269
8.89 Temporary Mobile Group Identity (TMGI) ................................................................................................... 270
8.90 Additional MM context for SRVCC .............................................................................................................. 270
8.91 Additional flags for SRVCC .......................................................................................................................... 270
8.92 Void ................................................................................................................................................................ 271
8.93 MDT Configuration........................................................................................................................................ 271
8.94 Additional Protocol Configuration Options (APCO) ..................................................................................... 272
8.95 Absolute Time of MBMS Data Transfer ........................................................................................................ 272
8.96 H(e)NB Information Reporting ...................................................................................................................... 272
8.97 IPv4 Configuration Parameters (IP4CP) ........................................................................................................ 273
8.98 Change to Report Flags .................................................................................................................................. 273
8.99 Action Indication ............................................................................................................................................ 273
8.100 TWAN Identifier ............................................................................................................................................ 274
8.101 ULI Timestamp .............................................................................................................................................. 275
8.102 MBMS Flags .................................................................................................................................................. 276
8.103 RAN/NAS Cause ............................................................................................................................................ 276
8.104 CN Operator Selection Entity......................................................................................................................... 277
8.105 Trusted WLAN Mode Indication ................................................................................................................... 278
8.106 Node Number ................................................................................................................................................. 278
8.107 Node Identifier ............................................................................................................................................... 279
8.108 Presence Reporting Area Action .................................................................................................................... 279
8.109 Presence Reporting Area Information ............................................................................................................ 281
8.110 TWAN Identifier Timestamp ......................................................................................................................... 281
8.111 Overload Control Information ........................................................................................................................ 281
8.112 Load Control Information .............................................................................................................................. 282
8.113 Metric ............................................................................................................................................................. 282
8.114 Sequence Number........................................................................................................................................... 282
8.115 APN and Relative Capacity ............................................................................................................................ 283
8.116 WLAN Offloadability Indication ................................................................................................................... 283
8.117 Paging and Service Information ..................................................................................................................... 284
8.118 Integer Number .............................................................................................................................................. 284
8.119 Millisecond Time Stamp ................................................................................................................................ 284
8.120 Monitoring Event Information ....................................................................................................................... 285
8.121 ECGI List ....................................................................................................................................................... 285
8.122 Remote UE Context........................................................................................................................................ 286
8.123 Remote User ID .............................................................................................................................................. 286
8.124 Remote UE IP Information............................................................................................................................. 286
ETSI
9 Security.................................................................................................................................................286
10 IP - The Networking Technology used by GTP ...................................................................................287
10.1 IP Version....................................................................................................................................................... 287
10.2 IP Fragmentation ............................................................................................................................................ 287
11 Notification of supported features between peer GTP-C entities .........................................................287
11.1 General ........................................................................................................................................................... 287
11.1.1 Introduction............................................................................................................................................... 287
11.1.2 Defining a feature ..................................................................................................................................... 287
11.2 Dynamic discovery of supported features ...................................................................................................... 288
11.2.1 General...................................................................................................................................................... 288
11.2.2 Features supported by direct peer GTP-C entities .................................................................................... 288
12 GTP-C load & overload control mechanism ........................................................................................288
12.1 General ........................................................................................................................................................... 288
12.1.1 GTP-C overload problem.......................................................................................................................... 288
12.1.2 Scenarios leading to overload ................................................................................................................... 289
12.1.3 Load & overload control concepts ............................................................................................................ 289
12.2 Load control solution...................................................................................................................................... 290
12.2.1 Principles of load control .......................................................................................................................... 290
12.2.2 Applicability to 3GPP and non-3GPP access based interfaces ................................................................. 290
12.2.3 Node level load control ............................................................................................................................. 291
12.2.4 APN level load control ............................................................................................................................. 291
12.2.4.1 General ................................................................................................................................................ 291
12.2.4.2 Justifications for APN load control support ........................................................................................ 291
12.2.4.3 Elements of APN load control ............................................................................................................ 292
12.2.5 Load Control Information ......................................................................................................................... 292
12.2.5.1 Definition ............................................................................................................................................ 292
12.2.5.1.1 General description ........................................................................................................................ 292
12.2.5.1.2 Parameters ..................................................................................................................................... 293
12.2.5.1.2.1 Load Control Sequence Number .............................................................................................. 293
12.2.5.1.2.2 Load Metric.............................................................................................................................. 294
12.2.5.1.2.3 List-of-APN_and_Relative Capacity ....................................................................................... 294
12.2.5.1.3 Handling of parameters ................................................................................................................. 295
12.2.5.2 Frequency of inclusion ........................................................................................................................ 295
12.2.5.3 Limit on maximum number of instances ............................................................................................. 296
12.2.6 Discovery of the support of the feature by the peer node ......................................................................... 296
12.2.7 Issues in the network with partial support of the feature .......................................................................... 296
12.3 Overload control solution ............................................................................................................................... 296
12.3.1 Principles of overload control ................................................................................................................... 296
12.3.2 Applicability to 3GPP and non-3GPP access based interfaces ................................................................. 297
12.3.3 Node level overload control ...................................................................................................................... 298
12.3.4 APN level overload control ...................................................................................................................... 298
12.3.4.1 General ................................................................................................................................................ 298
12.3.4.2 Elements of APN overload control ..................................................................................................... 299
12.3.5 Overload Control Information .................................................................................................................. 299
12.3.5.1 Definition ............................................................................................................................................ 299
12.3.5.1.1 General description ........................................................................................................................ 299
12.3.5.1.2 Parameters ..................................................................................................................................... 300
12.3.5.1.2.1 Overload Control Sequence Number ....................................................................................... 300
12.3.5.1.2.2 Period of Validity..................................................................................................................... 300
12.3.5.1.2.3 Overload Reduction Metric...................................................................................................... 301
12.3.5.1.2.4 List of APNs ............................................................................................................................ 301
12.3.5.1.3 Handling of parameters ................................................................................................................. 302
12.3.5.2 Frequency of inclusion ........................................................................................................................ 302
12.3.5.3 Limit on maximum number of instances ............................................................................................. 303
12.3.6 Propagating the MME/S4-SGSN identity to the PGW ............................................................................. 303
12.3.7 Updating the PGW with overload control information of the target MME/S4-SGSN ............................. 303
12.3.8 The interaction with APN congestion control using the PGW Back-Off Time ........................................ 304
12.3.9 Message throttling .................................................................................................................................... 304
12.3.9.1 General ................................................................................................................................................ 304
12.3.9.2 Throttling algorithm – "Loss" ............................................................................................................. 305
ETSI
12.3.9.2.1 Description .................................................................................................................................... 305

12.3.9.3 Message prioritization ......................................................................................................................... 305
12.3.9.3.1 Description .................................................................................................................................... 305
12.3.9.3.2 Based on procedures ...................................................................................................................... 306
12.3.9.3.3 Based on session parameters ......................................................................................................... 307
12.3.10 Enforcement of overload control .............................................................................................................. 307
12.3.10.1 General ................................................................................................................................................ 307
12.3.10.2 Aspects related to enforcement of the overload control ...................................................................... 307
12.3.10.2.1 Good throughput of the network.................................................................................................... 307
12.3.10.2.2 Message processing efficiency at the source GTP-C entity........................................................... 307
12.3.10.2.3 Self-protection by the overloaded GTP-C entity ........................................................................... 308
12.3.10.3 Enforcement of overload control between GTP-C entities in direct contact ....................................... 308
12.3.10.4 Enforcement of overload control between remote GTP-C entities ..................................................... 308
12.3.10.4.1 Description .................................................................................................................................... 308
12.3.11 Discovery of the support of the feature by the peer node ......................................................................... 308
12.3.12 Issues in the network with partial support of the feature .......................................................................... 309
12.3.13 Implicit overload control mechanisms ...................................................................................................... 309
13 Detection and handling of late arriving requests ..................................................................................309
13.1 General ........................................................................................................................................................... 309
13.2 Detection and handling of requests which collide with an existing session context ...................................... 309
13.2.1 General...................................................................................................................................................... 309
13.2.2 Principles .................................................................................................................................................. 310
13.3 Detection and handling of requests which have timed out at the originating entity ....................................... 310
13.3.1 General...................................................................................................................................................... 310
13.3.2 Principles .................................................................................................................................................. 310
Annex A (Informative): Backward Compatibility Guidelines for Information Elements .............312

Annex B (Informative): Transparent copying of RANAP/S1AP IEs into GTP IEs .......................313
B.1 General ........................................................................................................................................................... 313
B.2 Handover/Relocation related generic transparent Containers over RANAP, S1-AP and GTP ...................... 313
B.3 Other RANAP and S1-AP IEs ........................................................................................................................ 315
Annex C (Normative): MME/S4-SGSN mapping table between S11/S4 and NAS Cause
values .............................................................................................................316
Annex D (Informative): GTP-C load and overload control mechanism ..........................................321
D.1 GTP-C interfaces not supporting Load Control.............................................................................................. 321
D.2 GTP-C interfaces not supporting Overload Control ....................................................................................... 321
D.3 "Loss" throttling algorithm ............................................................................................................................. 322
D.3.1 Example of possible implementation ............................................................................................................. 322
D.4 Enforcement of overload control between remote GTP-C entities ................................................................. 322
D.4.1 Example of possible implementation ............................................................................................................. 322
Annex E (Normative): TWAN mapping table between GTPv2 S2a Cause and non-3GPP
access Cause values ......................................................................................324
Annex F (Informative): Change History ............................................................................................327
History ............................................................................................................................................................345
ETSI
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
1 Scope
The present document specifies the stage 3 of the control plane of the GPRS Tunnelling Protocol, Version 2 for
Evolved Packet System interfaces (GTPv2-C).
In this document, unless otherwise specified, the S2a, S2b, S5 and S8 interfaces refer always to the GTP-based S2a,
S2b, S5 and S8 interfaces respectively .
GTPv2-C shall be used across the following EPC signalling interfaces: S2a, S2b, S3, S4, S5, S8, S10, S11 and S16.
GTPv2-C shall be used across the Sm and Sn interfaces for MBMS in EPS.
GTPv2-C based protocols shall also be used across Sv (3GPP TS 29.280 [15]) and S101/S121 (3GPP TS 29.276 [14])
interfaces.
The procedures supported between the TWAN and the PGW on the S2a interface, and between the ePDG and the PGW
on the S2b interface are specified in 3GPP TS 23.402 [45].
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However,
functionality related to GERAN Iu mode is neither maintained nor enhanced.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.003: "Numbering, addressing and identification".
[3] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access".
[4] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP)
across the Gn and Gp interface".
[5] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[6] IETF RFC 791 (STD 0005): "Internet Protocol", J. Postel.
[7] IETF RFC 768 (STD 0006): "User Datagram Protocol", J. Postel.
[8] 3GPP TS 32.251: "Telecommunication Management; Charging Management; Packet Switched

(PS) domain charging.
[9] 3GPP TS 32.298: "Telecommunication Management; Charging Management; Charging Data

Record (CDR) parameter classification.
[10] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP)".
[11] 3GPP TS 33.102: "3G security; Security architecture".
ETSI
[12] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[13] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane
(GTPv1-U)".
[14] 3GPP TS 29.276: "3GPP Evolved Packet System (EPS); Optimized handover procedures and
protocols between E-UTRAN Access and cdma2000 HRPD Access; Stage 3".
[15] 3GPP TS 29.280: "Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN
to MSC) for SRVCC".
[16] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".
[17] 3GPP TS 23.007: "Restoration procedures".
[18] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace
control and configuration management ".
[19] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[20] 3GPP TS 36.414: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 data
transport".
[21] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[22] 3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs
interface specification".
[23] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".
[24] void
[25] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[26] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage
3".
[27] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[28] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3
specification".
[29] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[30] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General Aspects".
[31] IETF RFC 1035: "Domain Names - Implementation and Specification".
[32] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3".
[33] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP)
signalling".
[34] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving
GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP)".
[35] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
ETSI
[36] 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data

Record (CDR) transfer".
[37] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional
description".
[38] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN) ".
[39] IETF RFC 3588: "Diameter Base Protocol ".
[40] IETF RFC 4607: "Source-Specific Multicast for IP".
[41] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[42] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System
(MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling
procedures and the Mobile Application Part (MAP)".
[43] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[44] 3GPP TS 32.423: "Telecommunication management; Subscriber and equipment trace: Trace data
definition and management".
[45] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses.
[46] 3GPP TR 25.999: "HSPA Evolution (FDD)".
[47] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services".
[48] 3GPP TS 23.203: "Policy and charging control architecture; Stage 2".
[49] ITU-T Recommendation X.691 (07/2002): "Information technology – ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[50] 3GPP TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP
accesses".
[51] 3GPP TS 23.139: "3GPP system - fixed broadband access network interworking; Stage 2".
[52] IEEE Std 802.11-2012: "IEEE Standard for Information technology - Telecommunications and
information exchange between systems - Local and metropolitan area networks - Specific
requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
[53] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification".
[54] 3GPP TS 32.299: "Telecommunication Management; Charging Management; Diameter charging

applications.
[55] 3GPP TS 23.251: " Network Sharing; Architecture and Functional Description".
[56] 3GPP TS 23.271: "Location Services".
[57] 3GPP TS 29.173: "Diameter-based SLh interface for Control Plane LCS".
[58] IETF RFC 5453: "Reserved IPv6 Interface Identifiers".
[59] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for
Civic Addresses Configuration Information".
[60] IETF RFC 3046: "DHCP Relay Agent Information Option".
[61] 3GPP TS 23.380: "IMS Restoration Procedures".
[62] 3GPP TS 22.153: "Multimedia Priority Service".
ETSI
[63] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC)
via non-3GPP access networks; stage 3".
[64] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and
mobile users".
[65] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6
Headers".
[66] 3GPP TS 24.244: "Wireless LAN control plane protocol for trusted WLAN access to EPC".
[67] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2)".
[68] 3GPP TS 29.273: "3GPP EPS AAA Interfaces".
[69] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with
packet data networks and applications".
[70] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node
(SGSN) related interfaces based on Diameter protocol".
[71] 3GPP TS 23.161: "Network-Based IP Flow Mobility (NBIFOM); Stage 2".
[72] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
GTP-PDU: GTP Protocol Data Unit is either a GTP-C Message or a GTP-U Message. GTP-U Message may be either a
signalling message across the user plane tunnel, or a G-PDU (see clause 6).
• Signalling Message: any GTP-PDU (GTP-C or GTP-U) except the G-PDU.
• G-PDU: GTP user plane message, which carries the original packet (payload). G-PDU consists of GTP-U
header and a T-PDU.
• T-PDU: original packet, for example an IP datagram, from an UE or a network node in an external packet data
network. A T-PDU is the payload that is tunnelled in the GTP-U tunnel.
• GTP-C Message: GTP control plane message type of a GTP-PDU. GTP-C message consists of GTP-C
header, which is followed by zero or more information elements.
• GTP-U Message: GTP user plane message. The user plane messages are used to carry user data packets, and
also signalling messages e.g. for path management and error indication. Therefore, GTP-U message consists of
GTP-U header, which is followed by either a T-PDU, or zero or more information elements.
GTP Tunnel: A GTP tunnel is a communication tunnel between two GTP nodes (see subclause 4.1 "GTP Tunnel").
Tunnel Endpoint: A tunnel endpoint is identified with a TEID, an IP address and a UDP port number (see subclause
4.1 "GTP Tunnel").
Tunnel Endpoint Identifier (TEID): unambiguously identifies a tunnel endpoint in scope of a path (see subclause 4.1
"GTP Tunnel").
ETSI
3.2 Symbols
For the purposes of the present document, the following symbols apply:
S1-U Interface between SGW and eNodeB

X2 Interface between eNodeBs
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
AMBR Aggregate Maximum Bit Rate

APN Access Point Name
APN-NI Access Point Name Network Identifier
APN-OI Access Point Name Operator Identifier
C-MSISDN Correlation MSISDN
EBI EPS Bearer ID
eNodeB Evolved Node B
EPC Evolved Packet Core
ePDG Evolved Packet Data Gateway
EPS Evolved Packet System
F-TEID Fully Qualified Tunnel Endpoint Identifier
G-PDU GTP-U non-signalling PDU
GPRS General Packet Radio Service
GTP GPRS Tunnelling Protocol
GTP-PDU GTP-C PDU or GTP-U PDU
GTPv2-C GTP version 2, control plane
GTPv2-U GTP version 2, user plane
IMSI International Mobile Subscriber Identity
IP Internet Protocol
LBI Linked EPS Bearer ID
L1 Layer 1
L2 Layer 2
LGW Local Gateway
LIPA Local IP Access
MBMS Multimedia Broadcast/Multicast Service
MEI Mobile Equipment Identity
MSISDN Mobile Subscriber ISDN Number
NBIFOM Network-based IP Flow Mobility
NTP Network Time Protocol
PAA PDN Address Allocation
PCO Protocol Configuration Options
PDU Protocol Data Unit
PDN Packet Data Network or Public Data Network
PGW PDN Gateway
PTI Procedure Transaction Id
QoS Quality of Service
RAT Radio Access Technology
RIM RAN Information Management
SGW Serving Gateway
SPID Subscriber Profile ID for RAT/Frequency Priority
STN-SR Session Transfer Number for SRVCC
TEID Tunnel Endpoint Identifier
TEID-C Tunnel Endpoint Identifier, control plane
TEID-U Tunnel Endpoint Identifier, user plane
TFT Traffic Flow Template
TLIV Type Length Instance Value
TWAN Trusted WLAN Access Network
UDP User Datagram Protocol
ULI User Location Information
ETSI
4 General
4.1 GTP Tunnel

GTP tunnels are used between two nodes communicating over a GTP based interface, to separate traffic into different
communication flows.
A GTP tunnel is identified in each node with a TEID, an IP address and a UDP port number. The receiving end side of a
GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID values are exchanged between
tunnel endpoints using GTP-C or S1-MME or Iu-PS messages. The GTPv2 entity communicates to the peer GTPv2
entity the TEID value at which it expects to receive all subsequent control plane messages related to that GTP tunnel via
the:
- "Sender F-TEID for Control Plane" IE,
- "PGW S5/S8/S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface" IE,
- "MSC Server Sv TEID for Control Plane" IE,
- "S3/S16/S10 Address and TEID for Control Plane" IE, or
- "MME/SGSN Sv TEID for Control Plane" IE.
The criteria defining when the same or different GTP tunnels shall be used between the two nodes differs between the
control and the user plane, and also between interfaces.
For the control plane, for each end-point of a GTP-C tunnel:
- The TEID-C shall be unique per PDN-Connection on GTP based S2a, S2b, S5 and S8 interfaces. The same
tunnel shall be shared for the control messages related to all bearers associated to the PDN-Connection. A TEID-
C on the S2a/S2b/S5/S8 interface shall be released after all its associated EPS bearers are deleted.
- There shall be only one pair of TEID-Cs per UE on each of the S3, S10 and the S16 interfaces. The same tunnel
shall be shared for the control messages related to the same UE operation. A TEID-C on the S3/S10/S16
interface shall be released after its associated UE context is removed or the UE is detached. For the S3 interface,
when ISR is active for the UE, during I-RAT handover between the ISR associated nodes, the existing S3 TEID-
C may be re-used or new S3 TEID-C may be allocated. During this scenario, if the node decides to allocate new
S3 TEID-C, it shall release its own old S3 TEID-C.
- There shall be only one pair of TEID-C per UE over the S11 and the S4 interfaces. The same tunnel shall be
shared for the control messages related to the same UE operation. A TEID-C on the S11/S4 interface shall be
released after all its associated EPS bearers are deleted.
- There shall be only one pair of TEID-C per MBMS Bearer Service (i.e. per TMGI and MBMS Flow Identifier, if
the MBMS Flow Identifier is provided; or per TMGI, if the MBMS Flow Identifier is not provided) over the Sm
and Sn interfaces respectively. The same tunnel shall be shared for the control messages related to the same
MBMS Bearer Service. A TEID-C on the Sm/Sn interface shall be released after the MBMS Bearer Session is
stopped.
For GTP-U, a TEID-U is used according to 3GPP TS 29.281 [13].
NOTE: GTP-U is based on GTP version 1 (GTPv1).
4.2 Protocol stack

4.2.0 General
The protocol stack for GTPv2 shall be as depicted in Figure 4.2.0-1.
ETSI
GTP GTP
UDP UDP
IP IP
L2 L2
L1 L1
GTPv2 entity GTPv2 entity

GTPv2 based
interface
Figure 4.2.0-1: GTPv2 stack
The GTPv2 headers are specified in the respective clauses of this specification.
The source and destination IP addresses and UDP ports used for each GTP-C message depend on the role that the
message plays in a message exchange. A message can be an Initial message, or a Triggered message, or a Triggered
Reply message to Triggered message. An Initial message is sent to a peer GTP entity with a sequence number chosen
by the sending entity (see subclause 7.6). A Triggered message is sent in response to an Initial message. Triggered
Reply message may be sent in response to a Triggered message. See subclause 7.6 for the sequence number usage.
Typically, a Request message is an Initial message, but a Request message may be a Triggered messages in certain
procedures where they are triggered by an Initial Command message. See subclause 4.2.5 for classification of the Initial
messages and their possible Triggered messages, as well as cases where there are Triggered Reply messages to the
Triggered messages.
Piggybacking is an optional feature, which is described in Annex F of 3GPP TS 23.401 [3]. If the feature is supported,
then the piggybacking of the initial messages on triggered response messages for EUTRAN Initial Attach, a Handover
from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN (see sub-clauses 8.6 and 16.11 of 3GPP TS 23.402 [45])
and UE-requested PDN Connectivity procedures shall be implemented as per requirements in subclauses 4.2.0 and
5.5.1 of this specification .When piggybacking is used, a common IP header and a common UDP header shall be used
for the triggered response message and the piggybacked initial message as depicted in Figure 4.2.0-2. Immediately
following the triggered response message is the piggybacked initial message, following which no additional information
shall be present. The subclause 5.5 specifies the usage of piggybacking-specific fields in the GTP-C header.
IP header UDP header Triggered response message Piggybacked initial message

(P=1) (P=0)
Figure 4.2.0-2: Packet Format for the Piggybacking of messages
4.2.1 UDP header and port numbers
4.2.1.0 General
A User Datagram Protocol (UDP) compliant with IETF RFC 768 [7] shall be used.
ETSI
4.2.1.1 Initial Messages

The UDP Destination Port number for GTPv2 Initial messages shall be 2123. It is the registered port number for GTP-
C.
The UDP Source Port for a GTPv2 Initial message is a locally allocated port number at the sending GTP entity.
If GTPv2 and GTP' v2 modules are using the same IP address for sending messages, the implementation shall ensure
that while some source port number is used by GTPv2 messages, the same source port number shall not be used by
GTP' v2 messages. Otherwise, the IP interface may have difficulty to delivering a response message to the right
protocol entity.
4.2.1.2 Triggered Messages

The UDP Destination Port value of a GTPv2 Triggered message and for a Triggered Reply message shall be the value
of the UDP Source Port of the corresponding message to which this GTPv2 entity is replying, except in the case of the
SGSN pool scenario.
The UDP Source Port of a GTPv2 Triggered message and for a Triggered Reply message shall be the value from the
UDP Destination Port of the corresponding message to which this GTPv2 entity is replying, except in the case of the
SGSN pool scenario.
In the SGSN pool scenario, if the Identification Request, the Context Request or the Suspend Notification messages
have been forwarded by another SGSN in the pool, the UDP Destination Port for the Identification Response, the
Context Response or the Suspend Acknowledge message shall be determined in the following way. The value from the
information element "UDP Source Port Number", which was sent in the corresponding forwarded request, shall be
copied into the UDP Destination Port field. The UDP Source Port for the Identification Response, the Context Response
or the Suspend Acknowledge message may be a locally allocated port number at the sending GTP entity.
4.2.1.3 Piggybacked Messages

A piggybacked initial message is carried as a concatenation after a triggered response message and they share a
common UDP header (see Figure 4.2.0-2).
The UDP Destination port for the IP packet containing both the triggered response message and the piggybacked initial
message shall be the same as the port number used for the triggered response message.
The UDP Source port for the IP packet containing both the triggered response message and the piggybacked initial
message shall be the same as the port number used for the triggered response message.
4.2.2 IP header and IP addresses
4.2.2.1 Initial Messages

The IP Destination Address of a GTPv2 Initial message shall be an IP address of the destination GTPv2 entity.
During the establishment of the GTP tunnel, the GTPv2 entity selects and communicates to the peer GTPv2 entity the
IP Destination Address at which it expects to receive subsequent control plane Initial messages related to that GTP
tunnel via the:
- "Sender F-TEID for Control Plane" IE,
- "PGW S5/S8/S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface" IE,
- "MSC Server Sv Address for Control Plane" IE,
- "S3/S16/S10 Address and TEID for Control Plane" IE, or
- "MME/SGSN Sv Address for Control Plane" IE.
During the network triggered service restoration procedure (see 3GPP TS 23.007 [17]), if an MME/S4-SGSN sends a
Downlink Data Notification Failure Indication message to the SGW, then the destination address for this message shall
be the SGW IP address signalled via the Sender F-TEID for Control Plane IE in the Downlink Data Notification
ETSI
message (if present in the message), otherwise the source IP address of the Downlink Data Notification message
received earlier.
The IP Source Address of a GTPv2 Initial message shall be an IP address of the source GTPv2 entity from which the
Initial message is originating.
4.2.2.2 Triggered Messages

The IP Destination Address of a GTPv2 Triggered message and for a Triggered Reply message shall be copied from the
IP Source Address of the message to which this GTPv2 entity is replying, except in the case of the SGSN pool scenario.
The IP Source Address of a GTPv2 Triggered message and for a Triggered Reply message shall be copied from the IP
destination address of the message to which this GTPv2 entity is replying, except in the case of SGSN pool scenario.
In the SGSN pool scenario, if the Identification Request, the Context Request or the Suspend Notification messages
have been forwarded by another SGSN in the pool, the IP Source address for the Identification Response, the Context
Response or the Suspend Acknowledge messages shall be locally allocated by the sending GTP entity. The IP
Destination Address for the Identification Response, the Context Response or the Suspend Acknowlegde messages shall
be determined in the following way. The value from the information element "Address for Control Plane", which was
sent in the corresponding Identification Request or the Suspend Notification message; or the value from the information
element "S3/S16/S10 Address and TEID for Control Plane", which was sent in the corresponding Context Request
message, shall be copied into the IP Destination Address field.
4.2.2.3 Piggybacked Messages

A piggybacked initial message is carried as a concatenation after a triggered response message and they share a
common IP header (see Figure 4.2.0-2).
The IP Source Address for the IP packet containing both the triggered response message and the piggybacked initial
message shall be the same as the IP Address used for the triggered response message.
The IP Destination Address for the IP packet containing both the triggered response message and the piggybacked
initial message shall be the same as the IP Address used for the triggered response message.
4.2.3 Layer 2
Typically Ethernet should be used as a Layer 2 protocol, but operators may use any other technology.
4.2.4 Layer 1
Operators may use any appropriate Layer 1 technology.
4.2.5 Messages with GTPv2 defined replies: Classification of Initial and

Triggered Messages
An Initial message is a GTPv2 message that is not triggered as a response to another GTPv2 message across the given
interface.
The expected reply to a Request message is a Triggered message and the reply has the same message name as the
Request but with "Response" replacing "Request".
NOTE 1: If the SGW receives a "Create Session Request" on S11/S4, this can trigger either of the following
GTPv2 messages across S5/S8: "Create Session Request" or "Modify Bearer Request". However, neither
of these messages across S5/S8 is considered to be a Triggered message.
If a Request message is a reply to a Command message, then the Request message is a Triggered message; otherwise
the Request message is an Initial message. Responses do not have replies except when a "Context Acknowledge" is
required as a reply to "Context Response" message as specified in relevant Stage 2 procedures. Context Acknowledge is
always triggered message and does not have a reply.
ETSI
NOTE 2: The "Context Acknowledge" message is sent only if the "Context Response" message is received with the
acceptance cause.
A message whose name ends in "Command" is always an initial message. If a "Command" message fails, the name of
the reply message is constructed by replacing "Command" with "Failure Indication". Apart from "Downlink Data
Notification Failure Indication" message, a "Failure Indication" is a Triggered message. The "Failure Indication"
message does not have a reply. If a "Command" message is successful, its reply will be a Request as specified in
relevant Stage 2 procedures.
A message whose name ends in "Notification" is always an Initial message, The expected Triggered message in reply
has the same message name but with "Acknowledge" replacing "Notification", except for the case of the message
"Downlink Data Notification" which has the reply "Downlink Data Notification Acknowledge" and "PGW Resart
Notification" which has the reply "PGW Restart Notification Acknowledge". An "Acknowledge" message does not
have a reply.
CS Paging Indication, Stop Paging Indication, RAN Information Relay, Configuration Transfer Tunnel, Trace Session
Activation, Trace Session Deactivation, ISR Status Indication and Downlink Data Notification Failure Indication
messages are Initial messages that do not have a reply.
A Version Not Supported Indication message is a Triggered message.
4.3 Transmission Order and Bit Definitions

The messages in this document shall be transmitted in network octet order starting with octet 1 with the Most
Significant Bit sent first.
The most significant bit of an octet in a GTP message is bit 8. If a value in a GTP message spans several octets and
nothing else is stated, the most significant bit is bit 8 of the octet with the lowest number.
5 GTP Header for Control Plane
5.1 General format

Control Plane GTP uses a variable length header. Control Plane GTP header length shall be a multiple of 4 octets.
Figure 5.1-1 illustrates the format of the GTPv2-C Header.
Bits
Octets 8 7 6 5 4 3 2 1
1 Version P T Spare Spare Spare
2 Message Type
st
3 Message Length (1 Octet)
nd
m to If T flag is set to 1, then TEID shall be placed into octets 5-
k(m+3) 8. Otherwise, TEID field is not present at all.
n to (n+2) Sequence Number
(n+3) Spare
Figure 5.1-1: General format of GTPv2 Header for Control Plane
Where:
- if T = 0, TEID field is not present, k = 0, m = 0 and n = 5;
- if T = 1, TEID field is present, k = 1, m = 5 and n = 9.
The usage of GTPv2-C header across the EPC specific interfaces is defined in the subclause 5.5 "Usage of the GTPv2-C
Header". Octet 1 bits shall be coded as follows:
- Bits 6-8 represent the Version field.
- Bit 5 represents the Piggybacking flag (P).
ETSI
- Bit 4 represents the TEID flag (T).
- Bits 3-1 are spare, the sender shall set them to "0" and the receiving entity shall ignore them.
5.2 Control Plane GTP Extension Header

The legacy Extension Header mechanism is not used for the GTP version 2 control plane (GTPv2-C). Future extensions
will be implemented by adding Information Elements in the message body if new parameters are needed.
5.3 GTP-C header for Echo and Version Not Supported

Indication messages
The GTPv2-C message header for the Echo Request, Echo Response and Version Not Supported Indication messages
shall not contain the TEID field, but shall contain the Sequence Number fields, followed by one spare octet as depicted
in figure 5.3-1. The spare bits shall be set to zero by the sender and ignored by the receiver. For the Version Not
Supported Indication message header, the Sequence Number may be set to any number and shall be ignored by the
receiver.
Bits
Octets 8 7 6 5 4 3 2 1
1 Version P T=0 Spare Spare Spare
2 Message Type
st
nd
st
5 Sequence Number (1 Octet)
nd
rd
8 Spare
Figure 5.3-1: The format of Echo and Version Not Supported Indication messages Header
5.4 EPC specific GTP-C header

Apart from the Echo Request, Echo Response and Version Not Supported Indication messages, the GTP-C message
header shall contain the TEID and Sequence Number fields followed by one spare octet. A typical GTP-C header is
depicted in figure 5.4-1. The spare bits shall be set to zero by the sender and ignored by the receiver.
Bits
Octets 8 7 6 5 4 3 2 1
1 Version P T=1 Spare Spare Spare
2 Message Type
st
nd
st
5 Tunnel Endpoint Identifier (1 Octet)
nd
rd
th
st
nd
rd
12 Spare
Figure 5.4-1: The format of EPC specific GTPv2 Control Plane message Header
ETSI
5.5 Usage of the GTPv2-C Header

5.5.1 General
The format of the GTPv2-C header is specified in subclause 5.1 "General format". The usage of the GTP-C header
across e.g. S101/S121 (3GPP TS 29.276 [14]) and Sv (3GPP TS 29.280 [15]) interfaces are defined in their respective
specifications.
The usage of the GTPv2-C header for EPC specific interfaces shall be as defined below.
The first octet of the header shall be used is the following way:
- Bits 8 to 6, which represent the GTP-C version, shall be set to decimal 2 ("010").
- Bit 5 represents a "P" flag. If the "P" flag is set to "0", no piggybacked message shall be present. If the "P" flag
is set to "1", then another GTPv2-C message with its own header and body shall be present at the end of the
current message.
When present, a piggybacked message shall have its "P" flag set to "0" in its own header. If a Create Session
Response message (as part of EUTRAN initial attach, a Handover from Trusted or Untrusted Non-3GPP IP
Access to E-UTRAN (see sub-clauses 8.6 and 16.11 of 3GPP TS 23.402 [45]) or UE-requested PDN
connectivity procedure) has the "P" flag set to "1", then a single Create Bearer Request message shall be present
as the piggybacked message. As a response to the Create Bearer Request message, if the Create Bearer Response
has the "P" flag set to "1", then a single Modify Bearer Request (as part of EUTRAN initial attach, a Handover
from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN (see sub-clauses 8.6 and 16.11 of 3GPP TS
23.402 [45]) or UE-requested PDN connectivity procedure) shall be present as the piggybacked message. A
Create Bearer Response with "P" flag set to "1" shall not be sent unless a Create Session Response with "P" flag
set to "1" has been received for the same procedure. Apart from Create Session Response and Create Bearer
Response messages, all the EPC specific messages shall have the "P" flag set to "0".
- Bit 4 represents a "T" flag, which indicates if TEID field is present in the GTP-C header or not. If the "T" flag is
set to 0, then the TEID field shall not be present in the GTP-C header. If the "T" flag is set to 1, then the TEID
field shall immediately follow the Length field, in octets 5 to 8. Apart from the Echo Request, Echo Response
and Version Not Supported Indication messages, in all EPC specific messages the value of the "T" flag shall be
set to "1".
- Bit 3 is a spare bit. The sending entity shall set it to "0" and the receiving entity shall ignore it.
The usage of the fields in octets 2 - n of the header shall be as specified below.
- Octet 2 represents the Message type field, which shall be set to the unique value for each type of control plane
message. Message type values are specified in Table 6.1-1 "Message types for GTPv2".
- Octets 3 to 4 represent the Message Length field. This field shall indicate the length of the message in octets
excluding the mandatory part of the GTP-C header (the first 4 octets). The TEID (if present) and the Sequence
Number shall be included in the length count. The format of the Length field of information elements is specified
in subclause 8.2 "Information Element Format".
- A piggybacked initial message and the preceding triggered response message present in the common IP/UDP
packet shall have their own length and sequence number in their respective GTP-C headers. The overall length
of the IP/UDP packet shall indicate the total length of the two GTP-C messages.
- For EPC specific interfaces, T=1, and therefore octets 5 to 8 represent the Tunnel Endpoint Identifier (TEID)
field. This field shall unambiguously identify a tunnel endpoint in the receiving GTP-C entity. The Tunnel
Endpoint Identifier is set by the sending entity in the GTP header of all control plane messages to the TEID
value provided by the corresponding receiving entity (see subclause 4.1). If a peer's TEID is not available the
TEID field shall be present in a GTPv2-C header, but its value shall be set to "0", as specified in subclause 5.5.2
"Conditions for sending TEID=0 in GTPv2-C header".
ETSI
NOTE: The TEID in the GTP header of a Triggered (or Triggered Reply) message is set to the TEID value
provided by the corresponding receiving entity regardless of whether the source IP address of the Initial
(or Triggered) message and the IP Destination Address provided by the receiving entity for subsequent
control plane Initial messages (see subclause 4.2.2.1) are the same or not.
- Octets 9 to 11 represent GTP Sequence Number field.
5.5.2 Conditions for sending TEID=0 in GTPv2-C header

If a peer's TEID is not available, the TEID field still shall be present in the header and its value shall be set to "0" in the
following messages:
- Create Session Request message on S2a/S2b/S5/S8
- Create Session Request message on S4/S11, if for a given UE, the SGSN/MME has not yet obtained the Control
TEID of the SGW.
- Create Indirect Data Forwarding Tunnel Request message on S4/S11, if the SGW selected by the MME/S4-
SGSN for indirect data forwarding is different from the SGW used as anchor.
- Identification Request/Response messages.
- Forward Relocation Request message: over S10, S16 interfaces, over S3 interface during I-RAT handover when
ISR is not active.
- Forward Relocation Request message over S3 interface during I-RAT handover between ISR associated nodes,
when ISR is active for the UE, and if the node decides to allocate new S3 TEID-C.
- Context Request message.
- Relocation Cancel Request message except for the case where the old SGSN/MME has already been assigned
the Tunnel Endpoint Identifier Control Plane of the new SGSN/MME.
- Relocation Cancel Response message if the new SGSN/MME does not have the Tunnel Endpoint Identifier
Control Plane of the old SGSN/MME.
- Delete PDN Connection Set Request/Response messages.
- Configuration Transfer Tunnel message.
- RAN Information Relay message.
- If a node receives a message and the TEID-C in the GTPv2 header of the received message is not known, it shall
respond with "Context not found" Cause in the corresponding response message to the sender, the TEID used in
the GTPv2-C header in the response message shall be then set to zero.
- If a node receives a request message containing protocol error, e.g. Mandatory IE missing, which requires the
receiver to reject the message as specified in clause 7.7, it shall reject the request message. For the response
message, the node should look up the remote peer"s TEID and accordingly set the GTPv2-C header TEID and
the message cause code. As an implementation option, the node may not look up the remote peer"s TEID and set
the GTPv2-C header TEID to zero in the response message. However in this case, the cause code shall not be set
to "Context not found".
- MBMS Session Start Request message.
- PGW Restart Notification / PGW Restart Notification Acknowledge messages.
- Downlink Data Notification message sent on S11/S4 as part of the Network Triggered Service Restoration
procedure (see 3GPP TS 23.007 [17]), and corresponding Downlink Data Notification Acknowledge and
Downlink Data Notification Failure Indication if the SGW did not include the Sender F-TEID for Control Plane
IE in the Downlink Data Notification message.
- Stop Paging Indication message is sent to the the restarted CN node (or another node in the same pool) as part of
the Network Triggered Service Restoration procedure with ISR (see 3GPP TS 23.007 [17]).
ETSI
- Suspend Notification and Suspend Acknowledge messages: over S16 interface; over S3 interface when ISR is
not active.
- PGW Downlink Triggering Notification message on S5 and S11/S4, PGW Downlink Triggering Acknowledge
message on S11/S4, and PGW Downlink Triggering Acknowledge message on S5 if the PGW did not include
the Sender F-TEID for Control Plane IE in the PGW Downlink Triggering Notification message.
- UE Registration Query Request and UE Registration Query Response messages over S3 interface.
NOTE: Legacy implementation conforming to earlier versions of this specification can send the Change
Notification Request/Response messages on the TEID zero in spite of the peer"s node TEID being
available.
5.6 Format of the GTPv2-C Message

The GTP-C header may be followed by subsequent information elements dependent on the type of control plane
message.
Bits
Octets 8 7 6 5 4 3 2 1
1 to m GTP-C header
m+1 to n Zero or more Information Element(s)
Figure 5.6-1: GTP-C Header followed by subsequent Information Elements
ETSI
6 GTP-C Message Types and Message Formats
6.0 General
A GTP-C message is sent across a GTP control plane tunnel. In a message, the GTP-C header is followed by zero or
more information elements. The GTP-C messages are used for the control plane path management, for the control plane
tunnel management and for mobility management.
A T-PDU is an original packet, for example an IP datagram, from an UE, or from a network node in an external packet
data network.
6.1 Message Format and Type values

6.1.0 Message Type
GTP defines a set of messages between two associated EPC network elements. The messages to be used shall be as
defined in Table 6.1-1.
ETSI
Table 6.1-1: Message types for GTPv2
Message Type Message Reference Initial Triggered

value (Decimal)
0 Reserved
1 Echo Request X
2 Echo Response X
3 Version Not Supported Indication X
4 to 16 Reserved for S101 interface TS 29.276 [14]
17 to 24 Reserved for S121 interface TS 29.276 [14]
25 to 31 Reserved for Sv interface TS 29.280 [15]
SGSN/MME/ TWAN/ePDG to PGW (S4/S11, S5/S8, S2a,
S2b)
32 Create Session Request X
33 Create Session Response X
36 Delete Session Request X
37 Delete Session Response X
SGSN/MME/ePDG to PGW (S4/S11, S5/S8, S2b)
34 Modify Bearer Request X
35 Modify Bearer Response X
MME to PGW (S11, S5/S8)
40 Remote UE Report Notification X
41 Remote UE Report Acknowledge X
SGSN/MME to PGW (S4/S11, S5/S8)
38 Change Notification Request X
39 Change Notification Response X
42 to 63 For future use
164 Resume Notification X
165 Resume Acknowledge X
Messages without explicit response
64 Modify Bearer Command X
(MME/SGSN/ TWAN/ePDG to PGW – S11/S4, S5/S8, S2a,
S2b)
65 Modify Bearer Failure Indication X
(PGW to MME/SGSN/ TWAN/ePDG – S5/S8, S11/S4, S2a,
S2b)
66 Delete Bearer Command X
(MME/SGSN to PGW – S11/S4, S5/S8)
67 Delete Bearer Failure Indication X
(PGW to MME/SGSN – S5/S8, S11/S4))
68 Bearer Resource Command X
(MME/SGSN/TWAN/ePDG to PGW – S11/S4, S5/S8, S2a,
S2b)
69 Bearer Resource Failure Indication X
(PGW to MME/SGSN/TWAN/ePDG – S5/S8, S11/S4, S2a,
S2b)
70 Downlink Data Notification Failure Indication X
(SGSN/MME to SGW – S4/S11)
71 Trace Session Activation X
S2b)
72 Trace Session Deactivation X
S2b)
73 Stop Paging Indication X
(SGW to MME/SGSN – S11/S4)
PGW to SGSN/MME/ TWAN/ePDG (S5/S8, S4/S11, S2a,
S2b)
95 Create Bearer Request X X
96 Create Bearer Response X
97 Update Bearer Request X X
98 Update Bearer Response X
99 Delete Bearer Request X X
100 Delete Bearer Response X
PGW to MME, MME to PGW, SGW to PGW, SGW to MME,
ETSI

value (Decimal)
PGW to TWAN/ePDG, TWAN/ePDG to PGW (S5/S8, S11,
S2a, S2b)
101 Delete PDN Connection Set Request X
102 Delete PDN Connection Set Response X
PGW to SGSN/MME(S5, S4/S11)
103 PGW Downlink Triggering Notification X
104 PGW Downlink Triggering Acknowledge X
MME to MME, SGSN to MME, MME to SGSN, SGSN to
SGSN (S3/S10/S16)
128 Identification Request X
129 Identification Response X
130 Context Request X
131 Context Response X
132 Context Acknowledge X
133 Forward Relocation Request X
134 Forward Relocation Response X
135 Forward Relocation Complete Notification X
136 Forward Relocation Complete Acknowledge X
137 Forward Access Context Notification X
138 Forward Access Context Acknowledge X
139 Relocation Cancel Request X
140 Relocation Cancel Response X
141 Configuration Transfer Tunnel X
152 RAN Information Relay X
SGSN to MME, MME to SGSN (S3)
149 Detach Notification X
150 Detach Acknowledge X
151 CS Paging Indication X
153 Alert MME Notification X
154 Alert MME Acknowledge X
155 UE Activity Notification X
156 UE Activity Acknowledge X
157 ISR Status Indication X
158 UE Registration Query Request X
159 UE Registration Query Response X
SGSN/MME to SGW, SGSN to MME (S4/S11/S3)
SGSN to SGSN (S16), SGW to PGW (S5/S8)
162 Suspend Notification X
163 Suspend Acknowledge X
SGSN/MME to SGW (S4/S11)
160 Create Forwarding Tunnel Request X
161 Create Forwarding Tunnel Response X
166 Create Indirect Data Forwarding Tunnel Request X
167 Create Indirect Data Forwarding Tunnel Response X
168 Delete Indirect Data Forwarding Tunnel Request X
169 Delete Indirect Data Forwarding Tunnel Response X
170 Release Access Bearers Request X
171 Release Access Bearers Response X
SGW to SGSN/MME (S4/S11)
176 Downlink Data Notification X
177 Downlink Data Notification Acknowledge X
179 PGW Restart Notification X
180 PGW Restart Notification Acknowledge X
SGW to SGSN (S4)
178 Reserved. Allocated in earlier version of the specification.
SGW to PGW, PGW to SGW (S5/S8)
200 Update PDN Connection Set Request X
201 Update PDN Connection Set Response X
ETSI

value (Decimal)
MME to SGW (S11)
211 Modify Access Bearers Request X
212 Modify Access Bearers Response X
MBMS GW to MME/SGSN (Sm/Sn)
231 MBMS Session Start Request X
232 MBMS Session Start Response X
233 MBMS Session Update Request X
234 MBMS Session Update Response X
235 MBMS Session Stop Request X
236 MBMS Session Stop Response X
Other
240 to 247 Reserved for Sv interface (see also types 25 to 31) TS 29.280 [15]
6.1.1 Presence requirements of Information Elements

There are four different presence requirements (Mandatory, Conditional, Optional, or Conditional-Optional) for an IE
within a given GTP-PDU:
- Mandatory means that the IE shall be included by the sending side, and that the receiver diagnoses a "Mandatory
IE missing" error, when detecting that the IE is not present. A response including a "Mandatory IE missing"
cause, shall include the type of the missing IE.
- Conditional means:
- that the IE shall be included by sending entity if the conditions specified in the relevant protocol specification
are met;
- the receiver shall check the conditions as specified in the corresponding message type description, based on
the parameter combination in the message and/or on the state of the receiving node, to infer if a conditional
IE shall be expected. Only if a receiver has sufficient information the following applies. A conditional IE,
which is absolutely necessary for the receiving entity to complete the procedure, is missing, then the receiver
shall abort the procedure.
- Conditional-Optional means:
- that the IE shall be included by the up-to-date sending entity, if the conditions specified in the relevant
protocol specification are met. An entity, which is at an earlier version of the protocol and therefore is not up-
to-date, obviously cannot send such new IE.
- the receiver need not check the presence of the IE in the message. If the receiver checks the presence of the
Conditional-Optional IE, then the IE's absence shall not trigger any of the error handling procedures. The
handling of an absence or erroneous such IEs shall be treated as Optional IEs as specified in subclause 7.7
"Error Handling".
- Optional means:
- that the IE shall be included as a service option. Therefore, the IE may be included or not in a message. The
handling of an absent optional IE, or an erroneous optional IE is specified in subclause 7.7 "Error Handling".
For conditional IEs, the clause describing the GTP-PDU explicitly defines the conditions under which the inclusion of
each IE becomes mandatory or optional for that particular GTP-PDU. These conditions shall be defined so that the
presence of a conditional IE only becomes mandatory if it is critical for the receiving entity. The definition might
reference other protocol specifications for final terms used as part of the condition.
For grouped IEs, the presence requirement of the embedded IE shall follow the rules:
- The grouped IE is Mandatory within a given message: the presence requirements of individual embedded IEs are
as stated within the Mandatory grouped IE for the given message.
ETSI
- The grouped IE is Conditional within a given message: if the embedded IE in the grouped IE is Mandatory or
Conditional, this embedded IE is viewed as Conditional IE by the receiver. If the embedded IE in the grouped IE
is Conditional-Optional, this embedded IE is viewed as Optional IE by the receiver. If the embedded IE in the
grouped IE is Optional, this embedded IE is viewed as Optional IE by the receiver.
- The grouped IE is Conditional-Optional within a given message: if the embedded IE in the grouped IE is
Mandatory or Conditional, this embedded IE is viewed as Conditional-Optional IE by the receiver. If the
embedded IE in the grouped IE is Conditional-Optional, this embedded IE is viewed as Optional IE by the
receiver. If the embedded IE in the grouped IE is Optional, this embedded IE is viewed as Optional IE by the
receiver.
- The grouped IE is Optional within a given message: all embedded IEs in the grouped IE are viewed as Optional
IEs by the receiver.
In all of the above cases, appropriate error handling as described in subclause 7.7 shall be applied for protocol errors of
the embedded IEs.
Only the Cause information element at message level shall be included in the response if the Cause contains a value that
indicates that the request is not accepted regardless of whether there are other mandatory or conditional information
elements defined for a given response message.
The following are exceptions:
- Optionally, the Protocol Configuration Options, Recovery, User Location Information (ULI), Load Control
Information, Overload Control Information, Bearer Context and Local Distinguished Name (LDN) information
elements may be included.
- For the rejection response of a Forward Relocation Request, the Forward Relocation Response message may also
include an F-Cause IE as specified in clause 7.3.2.
- For the rejection response of a SRVCC PS to CS Request, the SRVCC PS to CS Response message may also
include an SRVCC Cause IE as specified in clause 5.2.3 in 3GPP TS 29.280 [15].
- A Downlink Data Notification Acknowledge (with or) without an indication of success may also include a DL
low priority traffic Throttling IE and the IMSI IE.
- The PGW Back-Off Time IE may also be returned when rejecting a Create Session Request with the cause "APN
Congestion".
- Change Notification Response message may also include the IMSI and MEI information elements.
- Failure Indication type messages do not have "Accept" types of Cause values, i.e. all used values indicate the
rejection, therefore for Failure Indication type of triggered messages, other information elements, other than the
Cause IE, shall also be included according to the conditions of presence specified in the respective message, if
they are available.
- The Context Response message (sent by an SGSN or MME) should also include the IMSI IE if the Cause IE
contains the value "P-TMSI Signature mismatch", except if the UE is emergency attached and the UE is
UICCless.
- The Create Bearer Response message, the Update Bearer Response message and the Delete Bearer Response
message shall include the RAN/NAS Cause IE according to the conditions specified in subclauses 7.2.4, 7.2.16
and 7.2.10.2.
- The UE Registration Query Response message shall include IMSI to allow the SGSN to correlate the response
message with the corresponding request.
If the Cause information element at Grouped IE level contains a value that indicates that the Grouped IE is not handled
correctly, e.g. "Context Not Found" at Bearer Context IE level, the other information elements in this Grouped IE, other
than the Cause IE, may not be included.
6.1.2 Grouped Information Elements

Information elements can contain other IEs. This type of IE is called "Grouped IEs".
ETSI
Grouped IEs have a length value in the TLIV encoding, which includes the added length of all the embedded IEs.
Overall coding of a grouped information element with 4 octets long IE header is defined in subclause 8.2 "Information
Element Format". Each information element within a grouped IE also shall also contain 4 octets long IE header.
Grouped IEs are not marked by any flag or limited to a specific range of IE type values. The clause describing an IE in
this specification shall explicitly state if it is grouped.
NOTE 1: Each entry into each Grouped IE creates a new scope level. Exit from the grouped IE closes the scope
level. The GTPv2 message level is the top most scope. This is analogous to the local scope of a
subroutine/function.
If more than one grouped information elements of the same type, but for a different purpose are sent with a message,
these IEs shall have different Instance values.
If more than one grouped information elements of the same type and for the same purpose are sent with a message,
these IEs shall have exactly the same Instance value to represent a list.
NOTE 2: For instance, all "Bearer Contexts Modified" IEs of the type "Bearer Context" in a "Modify Bearer
Response" message shall have the Instance value of 0, while all "Bearer Contexts Marked for Removal"
IEs of the type "Bearer Context" in the same message shall have the Instance value of 1.
6.1.3 Information Element instance

Every GTPv2 message and grouped IE within a message in this specification has a column documenting the instance
value of each IE.
When a GTPv2 message is encoded for use the instance value of each included IE is encoded in the Instance field of the
IE for the message scope. See clause 7 and subclause 8.2 for details of that encoding.
An Information Element in an encoded GTPv2 message or encoded grouped IE is identified by the pair of IE Type and
Instance values and described by a specific row in the corresponding tables in subclauses of 7 in the present document.
If several Information Elements with the same Type and Instance values are included in an encoded GTPv2 message,
they represent a list for the corresponding IE name and row identified in the message grammar in subclauses of clause
7.
If several Information Elements with the same Type and Instance values are included in an encoded grouped IE, they
represent a list for the corresponding IE name and row identified in the grouped IE grammar in subclauses of clause 7.
In tables in this document the instance value for "Private Extension" is marked as VS (Vendor Specific). While an
instance value must be encoded by the sender the value can be Vendor and even Private Extension specific.
The same IE name might be used in different messages (on the top level or within grouped IEs) in this specification.
The instance value and name of an IE is only meaningful within the scope of the message definition . The combination
of Type value and Instance value uniquely identifies a specific row in a message description table.
6.2 Message Granularity

The GTPv2-C messages shall be sent per UE on the S3, S10 and S16 interfaces.
The GTPv2-C messages shall be sent per PDN-Connection on the S2a, S2b, S4, S11, S5 and S8 interfaces apart from
the following exclusion.
The following GTPv2-C messages are sent per UE on the S4 and S11 interfaces:
- Downlink Data Notification / Acknowledge / Failure Indication;
- Stop Paging Indication;
- Delete Indirect Data Forwarding Tunnel Request/Response;
- Delete Session Request/Response with Scope Indication set to 1 during following procedures with SGW change:
- Tracking Area Update procedure;
ETSI
- Routing Area Update procedure;
- Handover procedure;
- SRNS Relocation Cancel Using S4;
- Inter RAT handover Cancel procedure;
- S1 based handover cancel procedure;
- Delete Bearer Request/Response during a TAU/RAU/Handover procedure if the Cause value "ISR deactivation"
is included in the Delete Session Request message, or when it is sent to delete the bearer resources on the other
ISR associated CN node if the ISRAI flag is not set in the Modify Bearer Request/Modify Access Bearers
Request message.
- Release Access Bearers Request/Response;
- Create Indirect Data Forwarding Tunnel Request/Response;
- Trace Session Activation;
- Trace Session Deactivation;
- Create Forwarding Tunnel Request/Response.
The following GTPv2-C messages are sent per UE on the S11 interface:
- Modify Access Bearers Request/Response.
The following GTPv2-C messages are sent per GTP-C entity on the S2a, S2b, S5, S8, and S11 interfaces:
- Delete PDN Connection Set Request/Response.
The following GTPv2-C messages are sent per GTP-C entity on the S5 and S8 interfaces:
- Update PDN Connection Set Request/Response.
The following GTPv2-C messages are sent per GTP-C entity on the S4 and S11 interfaces:
- PGW Restart Notification/Acknowledge.
The following GTPv2-C path management messages are sent per GTP-C entity on all GTPv2-C interfaces:
- Echo Request/Response;
- Version Not Supported Indication.
7 GTP-C messages
7.1 Path Management Messages

7.1.0 General
Three path management messages are specified for GTP-C: Echo Request, Echo Response and Version Not Supported
Indication.
The usage of Echo Request / Response procedure is specified in 3GPP TS 23.007 [17].
7.1.1 Echo Request

Table 7.1.1-1 specifies the information elements included in the Echo Request message.
ETSI
The Recovery information element contains the local Restart Counter, which is specified in 3GPP TS 23.007 [17])
The optional Private Extension contains vendor or operator specific information.
Table 7.1.1-1: Information Elements in Echo Request
Information P Condition / Comment IE Type Ins.

elements
Recovery M Recovery 0
Sending Node CO This IE shall be sent towards a peer node on any GTPv2 Node Features 0
Features interface if the sending node supports at least one feature
on this interface or if the sending node supports at least
one feature and does not know the interface type towards
the peer node. This IE may be present otherwise.
Private Extension O Private Extension VS
7.1.2 Echo Response

Table 7.1.2-1 specifies the information elements included in the Echo Response message.
The Recovery information element contains the local Restart Counter, which is specified in 3GPP TS 23.007 [17])
The optional Private Extension contains vendor or operator specific information.
Table 7.1.2-1: Information Elements in Echo Response

elements
Recovery M Recovery 0
Sending Node CO This IE shall be sent towards a peer node on any GTPv2 Node Features 0
Features interface if the sending node supports at least one feature
on this interface or if the sending node supports at least
one feature and does not know the interface type towards
the peer node. This IE may be present otherwise.
NOTE: Having no Cause IE in the Echo Response message is an exceptional case for a triggered message. Hence,
a GTP entity that detects a GTP protocol error, e.g Mandatory IE missing, in the Echo Request message,
ignores the IE(s) that are in error and sends Echo Response. In addition it can log the error.
7.1.3 Version Not Supported Indication

This message contains only the GTPv2 header and indicates the latest GTP version that the sending entity supports.
7.2 Tunnel Management Messages

7.2.0 General
A node shall include the Recovery information element if it is in contact with the node's peer for the first time, or if the
node or the node's peer has restarted recently and the new Restart Counter value has not yet been indicated to the peer.
The peer receiving the Recovery information element shall handle it as when an Echo Response message is received but
shall consider the rest of the message in accordance with the message semantics and parameters.
7.2.1 Create Session Request

The direction of this message shall be from MME/S4-SGSN to SGW and from SGW to PGW, and from ePDG/TWAN
to the PGW (see Table 6.1-1).
ETSI
The Create Session Request message shall be sent on the S11 interface by the MME to the SGW, and on the S5/S8
interface by the SGW to the PGW as part of the procedures:
- E-UTRAN Initial Attach
- Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with GTP on S5/S8 interface (see sub-
clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402 [45])
- UE requested PDN connectivity
- Addition of a 3GPP access of NBIFOM procedure as specified by 3GPP TS 23.161 [71]
The message shall also be sent on S4 interface by the SGSN to the SGW, and on the S5/S8 interface by the SGW to the
PGW as part of the procedures:
- PDP Context Activation
- Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with GTP on S5/S8 interface
(see sub-clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402 [45])
- Addition of a 3GPP access of the NBIFOM procedure as specified by 3GPP TS 23.161 [71]
The message shall also be sent on the S11 interface by the MME to the SGW as part of the procedures:
- Tracking Area Update procedure with Serving GW change
- S1/X2-based handover with SGW change
- UTRAN Iu mode to E-UTRAN Inter RAT handover with SGW change
- GERAN A/Gb mode to E-UTRAN Inter RAT handover with SGW change
- 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure
- Gn/Gp SGSN to MME Tracking Area Update procedure
- Restoration of PDN connections after an SGW failure if the MME and PGW support these procedures as
specified in 3GPP TS 23.007 [17]
- MME triggered Serving GW relocation
- Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with PMIP on S5/S8 interface (see sub-
clauses 8.2 and 16.11 of 3GPP TS 23.402 [45])
and on the S4 interface by the SGSN to the SGW as part of the procedures:
- Routing Area Update with MME interaction and with SGW change
- Gn/Gp SGSN to S4 SGSN Routing Area Update
- Inter SGSN Routeing Area Update Procedure and Combined Inter SGSN RA / LA Update using S4 with SGW
change
- Iu mode RA Update Procedure using S4 with SGW change
- E-UTRAN to UTRAN Iu mode Inter RAT handover with SGW change
- E-UTRAN to GERAN A/Gb mode Inter RAT handover with SGW change
- Serving RNS relocation using S4 with SGW change
- Combined hard handover and SRNS relocation using S4 with SGW change
- Combined Cell / URA update and SRNS relocation using S4 with SGW change
- Enhanced serving RNS relocation with SGW relocation
ETSI
- Restoration of PDN connections after an SGW failure if the SGSN and PGW support these procedures as
- S4-SGSN triggered Serving GW relocation
- Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with PMIP on S5/S8 interface
(see sub-clauses 8.2 and 16.11 of 3GPP TS 23.402 [45])
and on the S2b interface by the ePDG to the PGW as part of the procedures:
- Initial Attach with GTP on S2b
- UE initiated Connectivity to Additional PDN with GTP on S2b
- Handover to Untrusted Non-3GPP IP Access with GTP on S2b (See sub-clause 8.6 of 3GPP TS 23.402 [45])
- Initial Attach for emergency session (GTP on S2b)
- Addition of an access using S2b of NBIFOM procedure as specified by 3GPP TS 23.161 [71]
and on the S2a interface by the TWAN to the PGW as part of the procedure:
- Initial Attach in WLAN on GTP S2a
- UE initiated Connectivity to Additional PDN with GTP on S2a
- Handover to TWAN with GTP on S2a (See sub-clause 16.10 of 3GPP TS 23.402 [45])
- Addition of an access using S2a of NBIFOM procedure as specified by 3GPP TS 23.161 [71].
If the new Create Session Request received by the SGW collides with an existing active PDN connection context (the
existing PDN connection context is identified with the tuple [IMSI, EPS Bearer ID], whereas IMSI shall be replaced by
TAC and SNR part of ME Identity for emergency attached UE without UICC or authenticated IMSI), this Create
Session Request shall be treated as a request for a new session. Before creating the new session, the SGW should delete:
- the existing PDN connection context locally, if the Create Session Request is received with the TEID set to zero
in the header, or if it is received with a TEID not set to zero in the header and it collides with the default bearer
of an existing PDN connection context;
- the existing dedicated bearer context locally, if the Create Session Request collides with an existing dedicated
bearer context and the message is received with a TEID not set to zero in the header.
In the former case, if the PGW S5/S8 IP address for control plane received in the new Create Session Request is
different from the PGW S5/S8 IP address for control plane of the existing PDN connection, the SGW should also delete
the existing PDN connection in the corresponding PGW by sending a Delete Session Request message.
NOTE 1: The SGW can send the Create Session Request and Delete Session Request over S5/S8 asynchronously,
e.g. the SGW can send the Delete Session Request and then the Create Session Request without having to
wait for the Delete Session Response. It does not matter if the PGW happens to receive the Delete Session
Request after the Create Session Request since the PGW assigns a different S5/S8 F-TEID for control
plane to the new PDN connection.
If the new Create Session Request received by the PGW collides with an existing PDN connection context (the existing
PDN connection context is identified with the triplet [IMSI, EPS Bearer ID, Interface type], whereas applicable
Interface type here is S2a TWAN GTP-C interface or S2b ePDG GTP-C interface or S5/S8 SGW GTP-C interface, and
where IMSI shall be replaced by TAC and SNR part of ME Identity for emergency attached UE without UICC or
authenticated IMSI), this Create Session Request shall be treated as a request for a new session. Before creating the new
session, the PGW should delete:
- the existing PDN connection context , if the Create Session Request collides with the default bearer of an
existing PDN connection context;
- the existing dedicated bearer context, if the Create Session Request collides with a dedicated bearer of an
existing PDN connection context.
ETSI
The PGW shall allocate a new PGW S5/S8 F-TEID for control plane to the new PDN connection, i.e. not the same F-
TEID value as the one which was assigned to the existing PDN connection.
NOTE 2: With GTP based S2a and S2b, the EPS Bearer IDs assigned for specific UE over S2a between the TWAN
and PGW and over S2b between an ePDG and PGW are independent of the EPS Bearer IDs assigned for
the same UE over S5/S8 and may overlap in value (see 3GPP TS 23.402 [45] subclause 4.6.2).
NOTE 3: Only the TAC and SNR part of the ME Identity is used to identify an emergency attached UE without
UICC or authenticated IMSI.
ETSI
Table 7.2.1-1: Information Elements in a Create Session Request

elements
C The IMSI shall be included in the message on the S4/S11
interface, and on S5/S8 interface if provided by the
MME/SGSN, except for the case:
- If the UE is emergency attached and the UE is
UICCless.
The IMSI shall be included in the message on the S4/S11

IMSI interface, and on S5/S8 interface if provided by the IMSI 0
MME/SGSN, but not used as an identifier
- if UE is emergency attached but IMSI is not
authenticated.
The IMSI shall be included in the message on the S2a/S2b

interface.
C For an E-UTRAN Initial Attach and a Handover from

Trusted or Untrusted Non-3GPP IP Access to E-UTRAN
the IE shall be included when used on the S11 interface, if
provided in the subscription data from the HSS.
For a PDP Context Activation procedure and a Handover
from Trusted or Untrusted Non-3GPP IP Access to
UTRAN/GERAN the IE shall be included when used on the
S4 interface, if provided in the subscription data from the
HSS.
The IE shall be included for the case of a UE Requested
PDN Connectivity, if the MME has it stored for that UE.
It shall be included when used on the S5/S8 interfaces if
provided by the MME/SGSN.
MSISDN MSISDN 0
The ePDG shall include this IE on the S2b interface during
an Attach with GTP on S2b , UE initiated Connectivity to
Additional PDN with GTP on S2b and a Handover to
Untrusted Non-3GPP IP Access with GTP on S2b, Initial
Attach for emergency session (GTP on S2b), if provided by
the HSS/AAA.
The TWAN shall include this IE on the S2a interface during

an Initial Attach in WLAN on GTP S2a, UE initiated
Connectivity to Additional PDN with GTP on S2a and a
Handover to TWAN with GTP on S2a, if provided by the
HSS/AAA.
C The MME/SGSN shall include the ME Identity (MEI) IE on
the S11/S4 interface:
UICCless
- If the UE is emergency attached and the IMSI is not

authenticated
ME Identity (MEI) MEI 0
For all other cases the MME/SGSN shall include the ME
Identity (MEI) IE on the S11/S4 interface if it is available.
CO If the SGW receives this IE, it shall forward it to the PGW
on the S5/S8 interface.
CO The TWAN/ePDG shall include the ME Identity (MEI) IE on
the S2a/S2b interface, if it is available.
C This IE shall be included on the S11 interface for E-
UTRAN Initial Attach, a Handover from Trusted or
Untrusted Non-3GPP IP Access to E-UTRAN and UE-
requested PDN Connectivity procedures. It shall include
User Location ECGI and TAI. The MME/SGSN shall also include it on the ULI
0
Information (ULI) S11/S4 interface for TAU/RAU/X2-Handover/Enhanced (NOTE 10)
SRNS Relocation procedure if the PGW/PCRF has
requested location information change reporting and
MME/SGSN support location information change reporting.
CO This IE shall also be included on the S4 interface for PDP
ETSI
Context Activation procedure. It shall include CGI/SAI,

together with RAI.
CO This IE shall also be included on the S4/S11 interface for a
TAU/RAU/X2-Handover/Enhanced SRNS Relocation
procedure if
- the level of support (User Location Change
Reporting and/or CSG Information Change
Reporting) changes; or
- the target MME/S4-SGSN can not derive the level

of support (User Location Change Reporting and/or
CSG Information Change Reporting) for the source
Gn/Gp SGSN. See NOTE 9.
The MME shall include the ECGI and /or TAI in the ULI,
the S4-SGSN shall include either the CGI or SAI or RAI, or
CGI/SAI together with RAI in the ULI.
CO This IE shall also be included on the S4/S11 interface for:
- a TAU procedure with an S4-SGSN interaction, if
the MME supports location information change
reporting;
- a RAU procedure with an MME interaction, if the

S4-SGSN supports location information change
reporting.
The MME shall include the ECGI and TAI in the ULI, the
S4-SGSN shall include the CGI/SAI together with RAI in
the ULI.
CO The SGW shall include this IE on S5/S8 if it receives the
ULI from MME/SGSN.
C This IE shall be included on the S4/S11, S5/S8 and S2b
interfaces for an E-UTRAN initial attach, a Handover from
Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, a
PDP Context Activation, a Handover from Trusted or
Untrusted Non-3GPP IP Access to UTRAN/GERAN, a UE
requested PDN connectivity, an Attach with GTP on S2b, a
UE initiated Connectivity to Additional PDN with GTP on
0
S2b, a Handover to Untrusted Non-3GPP IP Access with
GTP on S2b and an Initial Attach for emergency session
(GTP on S2b).
See NOTE 10.
Serving Network CO This IE shall be included on S4/S11 for Serving Network
RAU/TAU/Handover with SGW relocation procedures.
See NOTE 10.
CO This IE shall be included on the S2a interface for an Initial
Attach in WLAN on GTP S2a, a UE initiated Connectivity to
Additional PDN with GTP on S2a and a Handover to
TWAN with GTP on S2a.
The TWAN shall set this IE to the PLMN identity of the
selected PLMN used for 3GPP-based access
authentication. The selected PLMN is the PLMN of the
3GPP AAA Proxy in roaming case and the PLMN of the
3GPP AAA Server in non-roaming case.
M This IE shall be set to the 3GPP access type or to the value
matching the characteristics of the non-3GPP access the
UE is using to attach to the EPS.
The ePDG may use the access technology type of the

RAT Type untrusted non-3GPP access network if it is able to acquire RAT Type 0
it; otherwise it shall indicate Virtual as the RAT Type.
The TWAN shall set the RAT Type value to "WLAN" on

the S2a interface.
See NOTE 3, NOTE 4.
C This IE shall be included if any one of the applicable flags
Indication Flags Indication 0
is set to 1.
ETSI
Applicable flags are:

- S5/S8 Protocol Type: This flag shall be set to 1 on
the S11/S4 interfaces according to the protocol
chosen to be used on the S5/S8 interfaces.
- Dual Address Bearer Flag: This flag shall be set to

1 on the S2b, S11/S4 and S5/S8 interfaces when
the PDN Type, determined based on UE request
and subscription record, is set to IPv4v6 and all
SGSNs which the UE may be handed over to
support dual addressing. This shall be determined
based on node pre-configuration by the operator.
(see also NOTE 5).
The TWAN shall set this flag to 1 on the S2a
interface if it supports IPv4 and IPv6 and the PDN
Type determined from the UE request if single-
connection mode or multi-connection mode is used
(see 3GPP TS 23.402 [45]) and the user
subscription data is set to IPv4v6.
- Handover Indication: This flag shall be set to 1 on

the S11/S4 and S5/S8 interface during a Handover
E-UTRAN, or a Handover from Trusted or
Untrusted Non-3GPP IP Access to
UTRAN/GERAN procedures, or an Addition of a
3GPP access of NBIFOM procedure.
This flag shall be set to 1 on the S2b interface
during a Handover from 3GPP access to Untrusted
Non-3GPP IP Access with GTP on S2b and IP
address preservation is requested by the UE, or an
Addition of an access using S2b of NBIFOM
procedure.
This flag shall be set to 1 on the S2a interface
during a Handover from 3GPP access to TWAN
with GTP on S2a and IP address preservation is
requested by the UE, or an Addition of an access
using S2a of NBIFOM procedure.
- Operation Indication: This flag shall be set to 1 on

the S4/S11 interface for a TAU/RAU procedure
with SGW relocation, Enhanced SRNS Relocation
with SGW relocation, X2-based handovers with
SGW relocation and MME triggered Serving GW
relocation.
- Direct Tunnel Flag: This flag shall be set to 1 on

the S4 interface if Direct Tunnel is used.
- Piggybacking Supported: This flag shall be set to 1

on the S11 interface only if the MME supports the
piggybacking feature as described in Annex F of
3GPP TS 23.401 [3]. This flag shall be set to 1 on
S5/S8 only if both the MME and the SGW support
piggybacking.
- Change Reporting support Indication: This flag

shall be set to 1 on S4/S11 and S5/S8 interfaces if
the SGSN/MME supports location Info Change
Reporting and if the SGSN/MME's operator policy
permits reporting of location change to the
operator of the PGW with which the session is
being established. See NOTE2.
- CSG Change Reporting Support Indication: This

flag shall be set to 1 on S4/S11 and S5/S8
interfaces if the SGSN/MME supports CSG
Information Change Reporting and if the
SGSN/MME's operator policy permits reporting of
ETSI
CSG Information change to the operator of the

PGW with which the session is being established.
See NOTE 2.
- Unauthenticated IMSI: This flag shall be set to 1

on the S4/S11 and S5/S8 interfaces if the IMSI
present in the message is not authenticated and is
for an emergency attached UE.
- PDN Pause Support Indication: this flag shall be

set to 1 on the S5/S8 interface if the SGW
supports the PGW Pause of Charging procedure.
- NBIFOM Support Indication: This flag shall be set

to 1 on S11/S4 if the MME/SGSN supports
NBIFOM.
This flag shall be set to 1 on S5/S8 if both the
SGW and the MME/SGSN support NBIFOM. See
NOTE 12.
This flag shall be set to 1 on S2a/S2b if the
TWAN/ePDG supports NBIFOM.
- WLCP PDN Connection Modification Support

Indication: This flag shall be set to 1 on the S2a
interface if the TWAN supports the WLCP PDN
Connection Modification procedure.
- UE Not Authorised Cause Code Support

Indication: This flag shall be set to 1 on S4/S11
and S5/S8 interface if the SGSN/MME supports
the "UE not authorised by OCS or external AAA
Server" Cause Code.
- UE Available for Signalling Indication: this flag

shall be set to 1 on S11/S4 during a TAU/RAU with
SGW relocation procedure if there is pending
network initiated PDN connection signalling for this
PDN connection. The SGW shall include this IE
on S5/S8 if it receives the flag from the
MME/SGSN.
ETSI
Sender F-TEID for M

F-TEID 0
Control Plane
C This IE shall be sent on the S11 / S4 interfaces. The TEID
or GRE Key is set to "0" in the E-UTRAN initial attach, a
PGW S5/S8 Address Handover from Trusted or Untrusted Non-3GPP IP Access
for Control Plane or to E-UTRAN, the PDP Context Activation, a Handover from F-TEID 1
PMIP Trusted or Untrusted Non-3GPP IP Access to
UTRAN/GERAN and the UE requested PDN connectivity
procedures.
Access Point Name M
APN 0
(APN)
C This IE shall be included on the S4/S11 and S5/S8
Untrusted Non-3GPP IP Access to UTRAN/GERAN and a
UE requested PDN connectivity.
This IE shall be included on the S2b interface for an Initial

Attach with GTP on S2b, a Handover to Untrusted Non-
3GPP IP Access with GTP on S2b, a UE initiated
Connectivity to Additional PDN with GTP on S2b and an
Initial Attach for emergency session (GTP on S2b).
Selection Mode Selection Mode 0
It shall indicate whether a subscribed APN or a non
subscribed APN chosen by the
UE/MME/SGSN/ePDG/TWAN was selected.
This IE shall be included on the S2a interface for an Initial

Attach in WLAN on GTP S2a, a Handover to TWAN with
GTP on S2a and a UE initiated Connectivity to Additional
PDN with GTP on S2a. The value shall be set to "MS or
network provided APN, subscription verified".
CO When available, this IE shall be sent by the MME/SGSN on
the S11/S4 interface during TAU/RAU/HO with SGW
relocation.
Untrusted Non-3GPP IP Access to UTRAN/GERAN and a
PDN Type UE requested PDN connectivity. PDN Type 0
This IE shall be set to IPv4, IPv6 or IPv4v6. This is based
on the UE request and the subscription record retrieved
from the HSS (for MME see 3GPP TS 23.401 [3], clause
5.3.1.1, and for SGSN see 3GPP TS 23.060 [35], clause
9.2.1). See NOTE 1.
C This IE shall be included the S4/S11, S5/S8 and S2a/S2b
Untrusted Non-3GPP IP Access to UTRAN/GERAN, a UE
requested PDN connectivity, an Attach with GTP on S2b, a
S2b, a Handover to Untrusted Non-3GPP IP Access with
GTP on S2b, an Initial Attach for emergency session (GTP
on S2b, an Initial Attach in WLAN on GTP S2a, a UE
PDN Address
initiated Connectivity to Additional PDN with GTP on S2a PAA 0
Allocation (PAA)
and a Handover to TWAN with GTP on S2a. For PMIP-
based S5/S8, this IE shall also be included on the S4/S11
interfaces for TAU/RAU/Handover cases involving SGW
relocation.
The PDN type field in the PAA shall be set to IPv4, or IPv6
or IPv4v6 by MME, based on the UE request and the
subscription record retrieved from the HSS (see subclause
8.12 and also NOTE 5).
ETSI
The TWAN shall set the PDN type field in the PAA to IPv4,
or IPv6 or IPv4v6 based on the UE request if single-
connection mode or multi-connection mode is used (see
3GPP TS 23.402 [45]), the IP versions the TWAN supports
and the PDN type received in the user subscription data
from the HSS/3GPP AAA Server.
The ePDG shall set the PDN type field in the PAA to IPv4,
or IPv6 or IPv4v6 based on the UE request and the
subscription record retrieved from the HSS/3GPP AAA
Server, or based on the UE request and the ePDG
Emergency Configuration Data for an Initial Attach for
emergency session (GTP on S2b).
For static IP address assignment (for MME see 3GPP TS

23.401 [3], clause 5.3.1.1, for SGSN see 3GPP TS 23.060
[35], clause 9.2.1, for ePDG see 3GPP TS 23.402 [45]
subclause 4.7.3, and for TWAN see 3GPP TS 23.402 [45]
subclause 16.1.5), the MME/SGSN/ePDG/TWAN shall set
the IPv4 address and/or IPv6 prefix length and IPv6 prefix
and Interface Identifier based on the subscribed values
received from HSS, if available. For PDN Type IPv4v6,
either one of the IP versions (i.e. IPv4 address or IPv6
prefix and Interface Identifier) or both the IP versions may
be statically provisioned in the HSS. If only one of the IP
versions is statically provisioned in the HSS, the
MME/SGSN/ePDG/TWAN shall set the other IP version as
all zeros. The value of PDN Type field shall be consistent
with the value of the PDN Type IE, if present in this
message.
For a Handover to Untrusted Non-3GPP IP Access with

GTP on S2b, the ePDG shall set the IPv4 address and/or
IPv6 prefix length and IPv6 prefix and Interface Identifier
based on the IP address(es) received from the UE.
If static IP address assignment is not used (e.g. static

address is not received from the HSS), and for scenarios
other than a Handover to Untrusted Non-3GPP IP Access
with GTP on S2b, the IPv4 address shall be set to 0.0.0.0,
and/or the IPv6 Prefix Length and IPv6 prefix and Interface
Identifier shall all be set to zero.
CO This IE shall be sent by the MME/SGSN on S11/S4
interface during TAU/RAU/HO with SGW relocation.
interfaces in the E-UTRAN initial attach, a Handover from
Trusted or Untrusted Non-3GPP IP Access to E-UTRAN,
Maximum APN Untrusted Non-3GPP IP Access to UTRAN/GERAN and
APN Restriction 0
Restriction UE Requested PDN connectivity procedures.
This IE denotes the most stringent restriction as required
by any already active bearer context. If there are no
already active bearer contexts, this value is set to the least
restrictive type.
C This IE represents the APN-AMBR. It shall be included on
the S4/S11, S5/S8 and S2a/S2b interfaces for an E-
UTRAN initial attach, a Handover from Trusted or
Untrusted Non-3GPP IP Access to E-UTRAN, UE
requested PDN connectivity, PDP Context Activation
procedure using S4, a Handover from Trusted or Untrusted
Aggregate Maximum Non-3GPP IP Access to UTRAN/GERAN,
AMBR 0
Bit Rate (APN-AMBR) TAU/RAU/Handover from the Gn/Gp SGSN to the S4
SGSN/MME procedures, Attach with GTP on S2b, a
Handover to Untrusted Non-3GPP IP Access with GTP on
S2b, UE initiated Connectivity to Additional PDN with GTP
on S2b, an Initial Attach for emergency session (GTP on
S2b), Initial Attach in WLAN on GTP S2a, a Handover to
TWAN with GTP on S2a and UE initiated Connectivity to
ETSI
Additional PDN with GTP on S2a.

C This IE shall be included on S4/S11 in RAU/TAU/HO
except in the Gn/Gp SGSN to MME/S4-SGSN
Linked EPS Bearer ID EBI 0
RAU/TAU/HO procedures with SGW change to identify the
default bearer of the PDN Connection
CO The TWAN shall include this IE on S2a interface (during
initial attach, handover to TWAN with GTP on S2a
procedure, UE-initiated additional PDN connectivity
procedures), if the single-connection mode or multiple-
Trusted WLAN Mode
connection mode is used. TWMI 0
Indication
The TWAN shall not include this IE if transparent single-
connection mode is used. The PGW shall assume that
transparent single-connection mode is used if it receives
this message without this IE from the TWAN.
C If MME/SGSN receives PCO from the UE during the
Attach, PDN connectivity or Handover to 3GPP access
procedures, the MME/SGSN shall forward the PCO IE to
SGW. The SGW shall also forward it to PGW.
Protocol
CO If the TWAN receives a PCO from the UE during: an initial
Configuration Options PCO 0
attach, handover to TWAN or UE-initiated additional PDN
(PCO)
connectivity with GTP on S2a procedures (in multi-
connection mode or single connection mode), the TWAN
shall forward the PCO IE to the PGW, see 3GPP TS
23.402 [45].
M S Several IEs with the same type and instance value shall
be included on the S4/S11 and S5/S8 interfaces as
necessary to represent a list of Bearers. One single IE
shall be included on the S2a/S2b interface.
One bearer shall be included for E-UTRAN Initial Attach,
PDP Context Activation, UE requested PDN Connectivity,
Attach with GTP on S2b, UE initiated Connectivity to
Additional PDN with GTP on S2b, Handovers between
Bearer Contexts to be
Untrusted Non-3GPP IP Access with GTP on S2b and Bearer Context 0
created
3GPP Access, Initial Attach for emergency session (GTP
on S2b), Initial Attach in WLAN on GTP S2a, Handovers
between TWAN with GTP on S2a and 3GPP Access and
S2a.
One or more bearers shall be included for a
Handover/TAU/RAU with an SGW change.
See NOTE 6.
C This IE shall be included on the S4/S11 interfaces for the
TAU/RAU/Handover cases where any of the bearers
existing before the TAU/RAU/Handover procedure will be
Bearer Contexts to be deactivated as consequence of the TAU/RAU/Handover
Bearer Context 1
removed procedure.
For each of those bearers, an IE with the same type and
instance value shall be included.
See NOTE 6.
C This IE shall be included on the S4/S11 interface if an
SGW trace is activated, and/or on the S5/S8 and S2a/2b
Trace Information Trace Information 0
interfaces if a PGW trace is activated. See 3GPP TS
32.422 [18].
C This IE shall be included on the S4/S11, S5/S8 and S
Recovery S2a/2b interfaces if contacting the peer node for the first Recovery 0
time.
C This IE shall be included by the MME on the S11 interface
MME-FQ-CSID and shall be forwarded by an SGW on the S5/S8 interfaces FQ-CSID 0
according to the requirements in 3GPP TS 23.007 [17].
C This IE shall included by the SGW on the S5/S8 interfaces
SGW-FQ-CSID FQ-CSID 1
C This IE shall be included by the ePDG on the S2b interface
ePDG-FQ-CSID FQ-CSID 2
TWAN-FQ-CSID C This IE shall be included by the TWAN on the S2a FQ-CSID 3
interface according to the requirements in 3GPP TS
23.007 [17].
CO This IE shall be included by the MME over S11 during
UE Time Zone UE Time Zone 0
Initial Attach, a Handover from Trusted or Untrusted Non-
ETSI
3GPP IP Access to E-UTRAN and UE Requested PDN

Connectivity procedure.
This IE shall be included by the SGSN over S4 during PDP
Context Activation procedure and a Handover from Trusted
or Untrusted Non-3GPP IP Access to UTRAN/GERAN.
This IE shall be included by the MME/SGSN over S11/S4
TAU/RAU/Handover with SGW relocation.
C If SGW receives this IE, SGW shall forward it to PGW
across S5/S8 interface.
O This IE shall be included by the TWAN on the S2a
interface for Initial Attach in WLAN procedure, UE-initiated
Connectivity to Additional PDN with GTP on S2a and
handover to TWAN with GTP on S2a procedure as
specified in 3GPP TS 23.402 [45].
CO This IE shall be included on the S4/S11 interface for E-
UTRAN Initial Attach, a Handover from Trusted or
Untrusted Non-3GPP IP Access to E-UTRAN, UE-
requested PDN Connectivity, PDP Context Activation and
a Handover from Trusted or Untrusted Non-3GPP IP
Access to UTRAN using S4 procedures, if the UE is
accessed via CSG cell or hybrid cell.
User CSG The MME/SGSN shall also include it for
UCI 0
Information (UCI) TAU/RAU/Handover procedures with SGW relocation if the
UE is accessed via a CSG cell or hybrid cell or leaves a
CSG or hybrid cell and the PGW/PCRF has requested
CSG info reporting and MME/SGSN support CSG info
reporting. NOTE 11.
The SGW shall include this IE on S5/S8 if it receives the
User CSG information from MME/SGSN.
See NOTE 10.
Charging C This IE shall be included on the S4/S11, S5/S8 and Charging
0
Characteristics S2a/S2b interfaces according to 3GPP TS 32.251 [8] Characteristics
O This IE is optionally sent by the MME to the SGW on the
Local
S11 interface and by the S4-SGSN to the SGW on the S4
MME/S4-SGSN LDN Distinguished 0
interface (see 3GPP TS 32.423 [44]), when communicating
Name (LDN)
the LDN to the peer node for the first time.
O This IE is optionally sent by the SGW to the PGW on the Local
SGW LDN S5/S8 interfaces (see 3GPP TS 32.423 [44]), when Distinguished 1
communicating the LDN to the peer node for the first time. Name (LDN)
O This IE is optionally sent by the ePDG to the PGW on the Local
ePDG LDN S2b interfaces (see 3GPP TS 32.423 [44]), when Distinguished 2
contacting the peer node for the first time. Name (LDN)
TWAN LDN O This IE may be sent by the TWAN to the PGW on the S2a Local 3
interfaces (see 3GPP TS 32.423 [44]), when contacting the Distinguished
peer node for the first time. Name (LDN)
CO The SGSN/MME shall include this IE on the S4/S11
interface if the UE indicates low access priority when
Signalling Priority requesting to establish the PDN connection. Signalling Priority
0
Indication The SGW shall forward this IE in the Create Session Indication
Request message on the S5/S8 interfaces if received from
the MME/SGSN.
UE Local IP Address CO The ePDG shall include this IE on the S2b interface during IP Address 0
an Initial Attach for emergency session (GTP on S2b).
Otherwise the ePDG shall include this IE on the S2b
interface based on local policy.
UE UDP Port CO The ePDG shall include this IE on the S2b interface if NAT Port Number 0
is detected and the UE Local IP Address is present.
CO If multiple authentications are supported by the ePDG, the
ePDG shall include this IE on the S2b interface and
perform the corresponding procedures as specified for
PAP and CHAP authentication of the UE with external
Additional
Additional Protocol networks in 3GPP TS 33.402 [50].
Protocol
Configuration Options O If the UE requests the DNS IPv4/IPv6 address in the 0
Configuration
(APCO) Configuration Payload (CFG_REQ) during the IPsec tunnel
Options (APCO)
establishment procedure (as specified in 3GPP TS 33.402
[50]), and if the ePDG supports the Additional Protocol
Configuration Options IE, the ePDG may include this IE
over S2b interface and correspondingly set the "DNS
ETSI
Server IPv4/v6 Address Request" parameter as defined in

3GPP TS 24.008 [5].
CO If the UE includes the P-CSCF_IP6_ADDRESS attribute,
or the P-CSCF_IP4_ADDRESS attribute or both in the
CFG_REQUEST configuration payload during the IPsec
tunnel establishment procedure as specified in 3GPP TS
24.302 [63]), and if the ePDG supports these IKEv2
attributes and the Additional Protocol Configuration
Options IE, the ePDG shall include this IE over the S2b
interface and correspondingly set the P-CSCF IPv6
Address Request, or P-CSCF IPv4 Address Request, or
both parameters as defined in 3GPP TS 24.008 [5].
CO If the UE includes the P-
CSCF_RESELECTION_SUPPORT attribute in the
CFG_REQUEST configuration payload during the IPsec
tunnel establishment procedure as specified in 3GPP TS
24.302 [63], and if the ePDG supports the P-CSCF
restoration extension procedure for the untrusted WLAN
access (see 3GPP TS 23.380 [61]), the ePDG shall include
this IE over the S2b interface and correspondingly set the
P-CSCF_RESELECTION_SUPPORT, as defined in 3GPP
TS 24.008 [5].
O The TWAN may include this IE on the S2a interface to
retrieve additional IP configuration parameters from the
PGW (e.g. DNS server) if the transparent single-
connection mode is used as specified in
3GPP TS 23.402 [45].
CO The MME/SGSN shall include this IE on S11/S4 interface if
the MME/SGSN receives this information from H(e)NB in
UE associated S1/Iu signalling according (see 3GPP TS
23.139 [51]) during:
- E-UTRAN Initial Attach, a Handover from Trusted
or Untrusted Non-3GPP IP Access to E-UTRAN,
UE-requested PDN Connectivity, PDP Context
Activation and a a Handover from Trusted or
H(e)NB Local IP
Untrusted Non-3GPP IP Access to UTRAN using IP Address 1
Address
S4;
- TAU/RAU/X2-based handover/Enhanced Serving
RNS Relocation Procedure with SGW change, if
the PGW/PCRF has requested H(e)NB information
reporting for the PDN connection.
The SGW shall forward this IE on S5/S8 interface if the

SGW receives it from the MME/SGSN.
CO The MME/SGSN shall include this IE on S11/S4 interface if
the MME/SGSN receives this information from H(e)NB in
UE associated S1/Iu signalling according (see 3GPP TS
23.139 [51]) during:
- E-UTRAN Initial Attach, a Handover from Trusted
or Untrusted Non-3GPP IP Access to E-UTRAN,
UE-requested PDN Connectivity, PDP Context
Activation and a Handover from Trusted or
H(e)NB UDP Port Untrusted Non-3GPP IP Access to UTRAN using Port Number 1
S4;
- TAU/RAU/X2-based handover/Enhanced Serving
RNS Relocation Procedure with SGW relocation, if
reporting for the PDN connection.
The SGW shall forward this IE on S5/S8 interface if the

CO If the PGW triggered SGW restoration procedure is
supported, the MME/S4-SGSN shall include this IE on
S11/S4 interface and the SGW shall forward this IE on S5
MME/S4-SGSN
interface in the existing signalling as specified in 3GPP TS IP Address 2
Identifier
23.007 [17].
If the overload control feature is supported by the MME/S4-
SGSN and is activated for the PLMN to which the PGW
ETSI
belongs (see subclause 12.3.11), the MME/S4-SGSN shall

include this IE on the S11/S4 interface. In that case, the
SGW shall forward this IE on the S5/S8 interface.
CO This IE shall be included on the S2a interface for Initial
Attach in WLAN procedure, UE-initiated Connectivity to
TWAN Identifier Additional PDN with GTP on S2a and handover to TWAN TWAN Identifier 0
with GTP on S2a procedure as specified in 3GPP TS
23.402 [45].
O This IE may be included on the S2b interface based on
local policy for Fixed Broadband access network
ePDG IP Address interworking, see 3GPP TS 23.139 [51]. If present, it shall IP Address 3
contain the ePDG IP address which is used as IKEv2
tunnel endpoint with the UE.
CO In shared networks, the SGSN shall include this IE on the
S4 interface for a PDP Context Activation, a Handover
CN Operator CN Operator
UTRAN/GERAN and RAU with SGW relocation 0
Selection Entity Selection Entity
procedures, if the information is available, to indicate
whether the Serving Network has been selected by the UE
or by the network.
CO The MME/SGSN shall include this IE in the following
procedures, if the PGW/PCRF requested reporting
changes of UE presence in a Presence Reporting Area
and the MME/SGSN supports such reporting:
- TAU/RAU/Handover procedures with SGW

relocation and MME/SGSN change. The new Presence
Presence Reporting MME/SGSN shall then indicate whether the UE is Reporting Area 0
Area Information inside or outside the Presence Reporting Area; Information
- TAU/RAU/Handover procedures with SGW
relocation and without MME/SGSN change, if the
UE enters or leaves the Presence Reporting Area.

Presence Reporting Area information from MME/SGSN.
O During an overload condition, the MME/S4-SGSN may
include this IE on the S11/S4 interface if the overload
control feature is supported by the MME/S4-SGSN and is
activated for the PLMN to which the PGW belongs (see
MME/S4-SGSN's clause 12.3.11).
Overload Control
Overload Control 0
Information
Information When present, the MME/S4-SGSN shall provide only one
instance of this IE, representing its overload information.
CO If the SGW receives this IE and if it supports the overload
control feature, it shall forward it to the PGW on the S5/S8
interface.
O During an overload condition, the SGW may include this IE
over the S5/S8 interface if the overload control feature is
supported by the SGW and is activated for the PLMN to
SGW's Overload Overload Control
which the PGW belongs (see clause 12.3.11). 1
Control Information Information
When present, the SGW shall provide only one instance of
this IE, representing its overload information.
O During an overload condition, the TWAN/ePDG may
include this IE over the S2a/S2b interface if the overload
control feature is supported by the TWAN/ePDG and is
TWAN/ePDG's
activated for the PLMN to which the PGW belongs (see Overload Control
Overload Control 2
clause 12.3.11). Information
Information
When present, the TWAN/ePDG shall provide only one
CO The MME/SGSN and the TWAN/ePDG shall include this IE
on the S11/S4 and S2a/S2b interface respectively, in the
Origination Time conditions specified in subclause 13.2. Millisecond Time
0
Stamp Stamp
When present, the Origination Time Stamp shall contain
the UTC time when the originating entity initiated the
ETSI
request.
CO The SGW shall include this IE on the S5/S8 interface if it
receives the Origination Time Stamp from the MME/SGSN
and if it supports the procedure specified in subclause
13.2.
CO The MME/SGSN and the TWAN/ePDG shall include this IE
on the S11/S4 and S2a/S2b interface respectively, in the
conditions specified in subclause 13.3.
Maximum Wait Time Integer Number 0
When present, the Maximum Wait Time shall contain the
duration (number of milliseconds since the Origination
Time Stamp) during which the originator of the request
waits for a response.
WLAN Location CO This IE shall be included on the S2b interface if the WLAN
TWAN Identifier 1
Information Location Information is available.
WLAN Location CO This IE shall be included on the S2b interface, if the WLAN TWAN Identifier
0
Timestamp Location Timestamp is available. Timestamp
CO This IE shall be included on the S11/S4 or S2a/S2b
interfaces if the MME/S4-SGSN or the TWAN/ePDG
receives an NBIFOM Container from the UE as specified in
TS 23.161 [71]. The Container Type shall be set to 4.
NBIFOM Container F-Container 0
CO If the SGW receives an NBIFOM Container from the
MME/S4-SGSN, the SGW shall forward this IE to the PGW
on the S5/S8 interface.
CO The MME shall include this IE on the S11 interface during
a SGW relocation procedure if such information is
Remote UE Context available. Remote UE
0
Connected Several IEs with the same type and instance value may be Context
included as necessary to represent a list of remote UEs
connected.
O This IE may be sent on the S5/S8, S4/S11 and S2a/S2b
Private Extension Private Extension VS
interfaces.
NOTE 1: The conditional PDN Type IE is redundant on the S4/S11 and S5/S8 interfaces (as the PAA IE
contains exactly the same field). The receiver may ignore it. This IE is never sent on the S2a/S2b
interface.
NOTE 2: 3GPP TS 23.401 [3] (e.g. subclause 5.3.2.1) and 3GPP TS 23.060 [35] (e.g. subclause 9.2.2.1)
defines the MME/SGSN shall send the MS Info Change Reporting Support Indication to the PGW. In
such case MME/SGSN shall use the Change Reporting Support Indication and/or CSG Change
Reporting Support Indication (whichever is applicable), even if stage 2 refers to MS Info Change
Reporting Support Indication.
NOTE 3: The methods that the ePDG may use to acquire the RAT type of the untrusted non-3GPP IP access
network are not specified in this release.
NOTE 4: The PDN-GW can be informed about the type of access network used by the UE over several
reference points, see 3GPP TS 29.212 [30] for the mapping between the code values for the
different access network types.
NOTE 5: 3GPP TS 23.401 [3] (see subclause 5.3.1.1) and 3GPP TS 23.060 [35] (see subclause 9.2.1) specify
the handling of the cases when UE has requested IPv4v6 PDN Type, but MME does not set the Dual
Address Bearer Flag due to the MME operator using single addressing per bearer to support
interworking with nodes of earlier releases.
NOTE 6: The Bearer Context to be created IE and Bearer Context to be removed IE, together, shall contain all
the bearers belonging to the given PDN connection with each bearer appearing in only one of these
IEs.
NOTE 7: During S1 based handover/ Inter RAT handover/TAU/RAU with S4-SGSN/MME and SGW
change,and handover/RAU/TAU from Gn/Gp SGSN to S4-SGSN/MME, if the target MME/S4-SGSN
cannot accept one or more PDN connection(s) but can accept at least one or more remaining PDN
Connection(s) of the UE, the target MME/SGSN shall indicate all the non GBR bearers of the
unaccepted PDN Connection in the Bearer Contexts to be created IE. The target MME/SGSN shall
indicate all the GBR bearers of the unaccepted PDN connection in the Bearer Contexts to be
removed IE.
NOTE 8: The conditions of presence of the IEs in the Create Session Request for the MME and S4-SGSN
triggered Serving GW relocation (see subclause 5.10.4 of 3GPP TS 23.401 [3] and subclause 9.2.2.4
of 3GPP TS 23.060 [35]) are identical to those specified respectively for X2 handover with SGW
relocation and for Enhanced Serving RNS Relocation with SGW relocation.
NOTE 9: During the TAU/RAU/Handover from Gn/Gp SGSN, the target MME/S4-SGSN can not derive the
level of support for User Location Change Reporting and/or CSG Information Change Reporting at
ETSI
the source Gn/Gp SGSN.

NOTE 10: In shared networks, when the message is sent from the VPLMN to the HPLMN, the PLMN ID that is
communicated in this IE shall be that of the selected Core Network Operator for supporting UEs, or
that of the allocated Core Network Operator for non-supporting UEs. As an exception, based on
inter-operator roaming/sharing agreement, if the information on whether the UE is a supporting or
non-supporting UE is available, the PLMN ID that is communicated to the HPLMN for non-supporting
UEs shall be the Common PLMN ID.
In shared networks, when the MME/S4-SGSN and PGW pertain to the same PLMN, the Primary
PLMN ID shall be communicated in the ECGI to the PGW, and the Common PLMN ID shall be
communicated in SAI/CGI to the PGW, for both supporting and non-supporting UEs. The Core
Network Operator PLMN ID (selected by the UE for supporting UEs or allocated by the network for
non-supporting UEs) shall be communicated in the TAI, RAI, UCI and the Serving Network.
See subclause 4.4 of 3GPP TS 23.251 [55].
NOTE 11: If the UE initiates a TAU or RAU procedure back to the old MME/old S4 SGSN before completing the
ongoing TAU or RAU procedure and the UE is not accessed via a CSG cell or hybrid cell, the old
MME/old S4-SGSN shall treat this case as the UE leaves a CSG or hybrid cell. .
NOTE 12: The SGW shall ignore the NBIFOM Support Indication flag received in the Create Session Request
when sending a Modify Bearer Request to the PGW, e.g. during the TAU with SGW relocation
procedure.
Table 7.2.1-2: Bearer Context to be created within Create Session Request
Octet 1 Bearer Context IE Type = 93 (decimal)

Octets 2 and 3 Length = n
Octet 4 Spare and Instance fields
elements
EPS Bearer ID M EBI 0
TFT O This IE may be included on the S4/S11 interfaces. Bearer TFT 0
S1-U eNodeB F-TEID C This IE shall be included on the S11 interface for X2-based F-TEID 0
handover with SGW relocation.
S4-U SGSN F-TEID C This IE shall be included on the S4 interface if the S4-U F-TEID 1
interface is used.
S5/S8-U SGW F- C This IE shall be included on the S5/S8 interface for an "E- F-TEID 2
TEID UTRAN Initial Attach", a Handover from Trusted or
Untrusted Non-3GPP IP Access to E-UTRAN, a "PDP
Context Activation", a Handover from Trusted or Untrusted
Non-3GPP IP Access to UTRAN/GERAN or a "UE
Requested PDN Connectivity".
S5/S8-U PGW F- C This IE shall be included on the S4 and S11 interfaces for F-TEID 3
TEID the TAU/RAU/Handover cases when the GTP-based
S5/S8 is used.
CO For PMIP-based S5/S8, this IE shall be included on the
S11/S4 interface for the TAU/RAU/Handover cases if the
PGW provided an alternate address for user plane, i.e. an
IP address for user plane which is different from the IP
address for control plane.
When present, this IE shall contain the alternate IP
address for user plane and the uplink GRE key.
See NOTE 1.
S12 RNC F-TEID CO This IE shall be included on the S4 interface if the S12 F-TEID 4
interface is used in the Enhanced serving RNS relocation
with SGW relocation procedure.
S2b-U ePDG F-TEID C This IE shall be included on the S2b interface for an Attach F-TEID 5
with GTP on S2b, a UE initiated Connectivity to Additional
PDN with GTP on S2b, a Handover to Untrusted Non-
3GPP IP Access with GTP on S2b and an Initial Attach for
emergency session (GTP on S2b).
S2a-U TWAN F-TEID C This IE shall be included on the S2a interface for an Initial F-TEID 6
Attach in WLAN on GTP S2a, a UE initiated Connectivity to
Additional PDN with GTP on S2a and a Handover to
TWAN with GTP on S2a.
Bearer Level QoS M Bearer QoS 0
NOTE 1: The capability to receive from the LMA an alternate LMA address for user plane shall be supported
homogeneously across all the SGWs, when supported over PMIP-based S5/S8.
ETSI
Table 7.2.1-3: Bearer Context to be removed within Create Session Request

elements
S4-U SGSN F-TEID C This IE shall be sent on the S4 interface if the S4-U F-TEID 0
interface is used. See NOTE 1.
NOTE 1: The conditional S4-U SGSN F-TEID IE is redundant.
Table 7.2.1-4: Overload Control Information within Create Session Request
Octet 1 Overload Control Information IE Type = 180 (decimal)

elements
Overload Control M See clause 12.3.5.1.2.1 for the description and use of this Sequence 0
Sequence Number parameter. Number
Overload Reduction M See clause 12.3.5.1.2.3 for the description and use of this Metric 0
Metric parameter.
Period of Validity M See clause 12.3.5.1.2.2 for the description and use of this EPC Timer 0
parameter.
This IE should be set to "0" if the "Overload Reduction
Metric" is null. This IE shall be ignored by the receiver if the
"Overload Reduction Metric" is null.
Table 7.2.1-5: Remote UE Context Connected within Create Session Request
Octets 1 Remote UE Context IE Type = ooo (decimal)

Octets 4 Spare and Instance fields
elements
Remote User ID M See subclause 8.123 for the description and use of this Remote User ID 0
parameter
Remote UE IP M See subclause 8.124 for the description and use of this Remote UE IP 0
Information parameter Information
7.2.2 Create Session Response

The Create Session Response message shall be sent on the S11/S4 interfaces by the SGW to the MME/S4-SGSN, on the
S5/S8 interfaces by the PGW to the SGW, on the S2b interface by the PGW to the ePDG, and on the S2a interface by
the PGW to the TWAN as part of the procedures listed for the Create Session Request (see subclause 7.2.1).
If handling of default bearer fails, then cause at the message level shall be a failure cause.
Possible Cause values are specified in Table 8.4-1. Message specific cause values are:
- "Request accepted".
- "Request accepted partially".
- "New PDN type due to network preference".
- "New PDN type due to single address bearer only".
- "Missing or unknown APN".
- "GRE key not found".
ETSI
- "Preferred PDN type not supported".
- "All dynamic addresses are occupied".
- "Remote peer not responding".
- "Semantic error in the TFT operation".
- "Syntactic error in the TFT operation".
- "Semantic errors in packet filter(s)".
- "Syntactic errors in packet filter(s)".
- "User authentication failed".
- "APN access denied – no subscription".
- "APN Restriction type incompatibility with currently active PDN Connection".
- "Version not supported by next peer".
- "Denied in RAT".
- "Protocol type not supported".
- "APN congestion".
- "Multiple PDN connections for a given APN not allowed".
- "Multiple accesses to a PDN connection not allowed".
- "Context not found".
- "UE not authorised by OCS or external AAA Server".
ETSI
Table 7.2.2-1: Information Elements in a Create Session Response

elements
Cause M See NOTE 2 and NOTE 4. Cause 0
Change Reporting interfaces with the appropriate Action field if the location Change Reporting
0
Action Change Reporting mechanism is to be started or stopped Action
for this subscriber in the SGSN/MME.
CO This IE shall be included on the S5/S8 and S4/S11
CSG Information interfaces with the appropriate Action field if the CSG Info CSG Information
0
Reporting Action reporting mechanism is to be started or stopped for this Reporting Action
subscriber in the SGSN/MME.
H(e)NB Information CO This IE shall be included on the S5/S8 and S4/S11 H(e)NB 0
Reporting interfaces with the appropriate Action field if H(e)NB Information
information reporting is to be started or stopped (during a Reporting
TAU/RAU with SGW change if started earlier) for the PDN
connection in the SGSN/MME.
C This IE shall be sent on the S11/S4 interfaces. For the
S5/S8/ S2a/S2b interfaces it is not needed because its
Sender F-TEID for
content would be identical to the IE PGW S5/S8/ S2a/S2b F-TEID 0
Control Plane
F-TEID for PMIP based interface or for GTP based Control
Plane interface.
C The PGW shall include this IE on the S5/S8 interfaces
during the Initial Attach, a Handover from Trusted or
Untrusted Non-3GPP IP Access to E-UTRAN, UE
requested PDN connectivity, PDP Context Activation and a
Handover from Trusted or Untrusted Non-3GPP IP Access
to UTRAN/GERAN procedures.
If the SGW receives this IE it shall forward the IE to
MME/S4-SGSN on the S11/S4 interface.
This IE shall include the TEID for GTP based S5/S8 case
and the uplink GRE key in the PMIP based S5/S8 case.
For PMIP based S5/S8, this IE shall be included on the

PGW S5/S8/ S2a/S2b S11/S4 interface and shall contain the PGW S5/S8 IP
F-TEID for PMIP address for control plane; the same IP address shall be
based interface or for used for both control plane and the user plane F-TEID 1
GTP based Control communication if the Bearer Context IE does not contain a
Plane interface S5/S8-U PGW F-TEID IE. See NOTE 7.
The PGW shall include this IE on the S2b interface during

the Attach with GTP on S2b, UE initiated Connectivity to
Additional PDN with GTP on S2b, Handover to Untrusted
Non-3GPP IP Access with GTP on S2b procedures and
Initial Attach for emergency session (GTP on S2b).
The PGW shall include this IE on the S2a interface during

the Initial Attach in WLAN on GTP S2a, UE initiated
Connectivity to Additional PDN with GTP on S2a and
Handover to TWAN with GTP on S2a procedures
See NOTE 6.
C This IE shall be included on the S5/S8, S4/S11 and
S2a/S2b interfaces for the E-UTRAN initial attach, a
to E-UTRAN, PDP Context Activation, a Handover from
Trusted or Untrusted Non-3GPP IP Access to
UTRAN/GERAN, UE requested PDN connectivity, Attach
with GTP on S2b, UE initiated Connectivity to Additional
PDN Address PDN with GTP on S2b, Handover to Untrusted Non-3GPP
PAA 0
Allocation (PAA) IP Access with GTP on S2b, Initial Attach for emergency
session (GTP on S2b), Initial Attach in WLAN on GTP S2a
procedures, UE initiated Connectivity to Additional PDN
with GTP on S2a and Handover to TWAN with GTP on
S2a.
The PDN type field in the PAA shall be set to IPv4, or IPv6
or IPv4v6 by the PGW. See NOTE4.
For the S4/S11 and S5/S8 interfaces, if the PGW uses
ETSI
DHCPv4 for IPv4 address allocation, the IPv4 address field

shall be set to 0.0.0.0; otherwise, the IPv4 address field
shall be set to non-zero value as specified in 3GPP TS
23.401 [3] and 3GPP TS 23.402 [45].
When assigning an IPv6 address the PGW shall send a
non-zero Interface Identifier. See NOTE 8.
interfaces in the E-UTRAN initial attach, a Handover from
Trusted or Untrusted Non-3GPP IP Access to E-UTRAN,
Untrusted Non-3GPP IP Access to UTRAN/GERAN and
APN Restriction UE Requested PDN connectivity procedures. APN Restriction 0
This IE shall also be included on S4/S11 during the Gn/Gp
SGSN to S4 SGSN/MME RAU/TAU procedures.
This IE denotes the restriction on the combination of types
of APN for the APN associated with this EPS bearer
Context.
C This IE represents the APN-AMBR. It shall be included on
Aggregate Maximum
the S5/S8, S4/S11 and S2a/S2b interfaces if the received AMBR 0
Bit Rate (APN-AMBR)
APN-AMBR has been modified by the PCRF.
C This IE shall be sent on the S4/S11 interfaces during
Gn/Gp SGSN to S4-SGSN/MME RAU/TAU procedure to
Linked EPS Bearer ID EBI 0
identify the default bearer the PGW selects for the PDN
Connection.
C If PGW decides to return PCO to the UE during the Attach,
PDN connectivity or Handover to 3GPP access
Protocol procedures, PGW shall send PCO to SGW. If SGW
Configuration Options receives the PCO IE, SGW shall forward it to MME/SGSN. PCO 0
(PCO) CO For trusted WLAN access, if single-connection mode or
multiple-connection mode is used, the PGW may include
this IE over the S2a interface to send PCO to the UE.
M EPS bearers corresponding to Bearer Contexts sent in
request message. Several IEs with the same type and
instance value may be included on the S5/S8 and S4/S11
as necessary to represent a list of Bearers. One single IE
shall be included on the S2a/S2b interface.
One bearer shall be included for E-UTRAN Initial Attach, a
to E-UTRAN, PDP Context Activation, a Handover from
Bearer Contexts Trusted or Untrusted Non-3GPP IP Access to
Bearer Context 0
created UTRAN/GERAN, UE Requested PDN Connectivity , Attach
with GTP on S2b, UE initiated Connectivity to Additional
PDN with GTP on S2b, Handover to Untrusted Non-3GPP
IP Access with GTP on S2b, Initial Attach for emergency
session (GTP on S2b), Initial Attach in WLAN on GTP S2a,
S2a and Handover to TWAN with GTP on S2a.
One or more created bearers shall be included for a
Handover/TAU/RAU with an SGW change. See NOTE 2.
C EPS bearers corresponding to Bearer Contexts to be
removed that were sent in the Create Session Request
Bearer Contexts
message. Bearer Context 1
marked for removal
For each of those bearers an IE with the same type and
instance value shall be included on the S4/S11 interfaces.
C This IE shall be included on the S4/S11, S5/S8 and
Recovery Recovery 0
S2a/S2b interfaces if contacting the peer for the first time
C When Charging Gateway Function (CGF) Address is
Charging Gateway
configured, the PGW shall include this IE on the S5 FQDN 0
Name
interface. See NOTE 1.
C When Charging Gateway Function (CGF) Address is
Charging Gateway
configured, the PGW shall include this IE on the S5 IP Address 0
Address
interface. See NOTE 1.
C This IE shall be included by the PGW on the S5/S8 and
S2a/S2b interfaces and, when received from S5/S8 be
PGW-FQ-CSID FQ-CSID 0
forwarded by the SGW on the S11 interface according to
the requirements in 3GPP TS 23.007 [17].
C This IE shall be included by the SGW on the S11 interface
SGW-FQ-CSID FQ-CSID 1
ETSI
O This IE is optionally sent by the SGW to the MME/SGSN

Local
on the S11/S4 interfaces (see 3GPP TS 32.423 [44]),
SGW LDN Distinguished 0
when communicating the LDN to the peer node for the first
Name (LDN)
time.
O This IE is optionally included by the PGW on the S5/S8 Local
PGW LDN and S2a/S2b interfaces (see 3GPP TS 32.423 [44]), when Distinguished 1
communicating the LDN to the peer node for the first time. Name (LDN)
O This IE may be included on the S5/S8 and S4/S11
interfaces when the PDN GW rejects the Create Session
Request with the cause "APN congestion". It indicates the
time during which the MME or S4-SGSN should refrain
PGW Back-Off Time EPC Timer 0
from sending subsequent PDN connection establishment
requests to the PGW for the congested APN for services
other than Service Users/emergency services.
See NOTE 3.
CO If multiple authentications are supported by the PGW and if
PGW received the Additional Protocol Configuration
Options IE in the Create Session Request, the PGW shall
include this IE on the S2b interface and perform the
corresponding procedures as specified for PAP and CHAP
authentication of the UE with external networks in 3GPP
TS 33.402 [50].
O If the PGW supports the Additional Protocol Configuration
Options IE and if the PGW has received the Additional
Protocol Configuration Options IE with the "DNS IPv4/IPv6
Server Address Request" parameter in the Create Session
Request over S2b interface, the PGW may include this IE
over the S2b interface with the "DNS IPv4/IPv6 Server Additional
Additional Protocol
Address" parameter as specified in 3GPP TS 24.008 [5]. Protocol
Configuration Options 0
Configuration
(APCO)
If the PGW supports the Additional Protocol Configuration Options (APCO)
Options IE and if the PGW has received the Additional
Protocol Configuration Options IE with the P-CSCF IPv4
Address Request, or P-CSCF IPv6 Address Request or
both parameters in the Create Session Request over the
S2b interface, the PGW may include this IE over the S2b
interface with the P-CSCF IPv4 Address, or P-CSCF IPv6
Address, or both parameters respectively as specified in
3GPP TS 24.008 [5].
O The PGW may include this IE on the S2a interface to
provide the TWAN with additional IP configuration
parameters (e.g. DNS server), if a corresponding request
was received in the Create Session Request message.
Trusted WLAN IPv4 CO The PGW shall include this IE on the S2a interface to a IPv4 0
Parameters Trusted WLAN Access if PDN Type in the PAA is set to Configuration
IPv4 or IPv4v6 and the transparent single-connection Parameters
mode is used as specified in 3GPP TS 23.402 [45]. (IP4CP)
This IE shall include:
- The Subnet Prefix Length of the subnet from which
the PGW allocates the UE"s IPv4 address.
- The IPv4 Default Router Address which belongs to

the same subnet as the IPv4 address allocated to
the UE.
Indication Flags CO This IE shall be included if any one of the applicable flags Indication 0
is set to 1.

set to 1 on the S5/S8 interface if the PGW
supports the PGW Pause of Charging procedure.
- PDN Pause Enable Indication: this flag shall be set

to 1 on the S5/S8 interface if the PGW enables the
SGW to use the PGW Pause of Charging
procedure for this PDN connection.
- Associate OCI with PGW node's identity: The
ETSI
PGW shall set this flag to 1 on the S5/S8 interface

or S2a/S2b interface if it has included the "PGW's
Overload Control Information" and if this
information is to be associated with the node
identity (i.e. FQDN or the IP address received from
the HSS or DNS during the PGW selection) of the
serving PGW. This flag shall be set to 1 by the
PGW if the "PGW's Overload Control Information"
is included and the Cause IE is set to a rejection
cause code. The SGW shall set this flag on the
S11/S4 interface if it supports the overload control
feature and if the flag is set on the S5/S8 interface.
- Associate OCI with SGW node's identity: The

SGW shall set this flag to 1 on the S11/S4
interface if it has included the "SGW's Overload
Control Information" and if this information is to be
associated with the node identity (i.e. FQDN or the
IP address received from the HSS or DNS during
the SGW selection) of the serving SGW. This flag
shall be set to 1 by the SGW if the "SGW's
Overload Control Information" is included and the
Cause IE is set to a rejection cause code.
- Delay Tolerant Connection Indication: the flag shall

be set to 1 on the S5/S8 and S11/S4 interface if
the PDN connection is "Delay Tolerant" (see
subclause 8.12).
ETSI

interfaces with the appropriate Action field if reporting Presence
Presence Reporting
changes of UE presence in a Presence Routing Area is to Reporting Area 0
Area Action
be started or stopped for this subscriber in the Action
MME/SGSN.
PGW's node level O The PGW may include this IE on the S5/S8 or S2a/S2b Load Control 0
Load Control interface, providing its node level load information, if the Information
Information load control feature is supported by the PGW and is
activated for the PLMN to which the access network node,
i.e. MME/S4-SGSN for 3GPP access network,
ePDG/TWAN for non-3GPP access network, belongs (see
clause 12.2.6).
CO If the SGW receives this IE and if it supports the load
control feature, it shall forward it to the MME/S4-SGSN on
the S11/S4 interface.
PGW's APN level O The PGW may include this IE on the S5/S8 or S2a/S2b Load Control 1
Load Control interface, providing APN level load information, if the APN Information
Information level load control feature is supported by the PGW and is
ePDG/TWAN for non-3GPP access based network,
belongs (see clause 12.2.6).
When present, the PGW shall provide one or more

instances of this IE, up to maximum of 10, with the same
type and instance value, each representing the load
information for a list of APN(s).
See NOTE 9, NOTE 11.
CO If the SGW receives this IE and if it supports APN level
load control feature, it shall forward it to the MME/S4-
SGSN on the S11/S4 interface.
SGW's node level O The SGW may include this IE, over the S11/S4 interface if Load Control 2
Load Control the load control feature is supported by the SGW and is Information
Information activated in the network (see clause 12.2.6).

this IE, representing its node level load information.
PGW's Overload O During an overload condition, the PGW may include this IE Overload Control 0
Control Information on the S5/S8 or S2a/S2b interface, if the overload control Information
feature is supported by the PGW and is activated for the
PLMN to which the access network node, i.e. MME/S4-
SGSN for 3GPP access based network, ePDG/TWAN for
non-3GPP access based network, belongs (see clause
12.3.11).
When present, the PGW shall provide at least one instance

of this IE, representing its overload information.
Additionally, the PGW may indicate APN level overload
control by providing, one or more instances of this IE, up to
maximum of 10, with the same type and instance value,
each representing the overload information for a list of
APN(s).
See NOTE 10, NOTE 12.
SGW's Overload O During an overload condition, the SGW may include this IE Overload Control 1
Control Information over the S11/S4 interface if the overload control feature is Information
supported by the SGW and is activated in the network (see
clause 12.3.11).

CO This IE shall be included on the S5/S8 or S2a/S2b
interfaces if the PGW needs to send NBIFOM
NBIFOM Container informationas specified in 3GPP TS 23.161 [71]. F-Container 0
The Container Type shall be set to 4.
ETSI
CO If the SGW receives an NBIFOM Container from the PGW,

the SGW shall forward this IE to the MME/S4-SGSN on the
S11/S4 interface.
Private Extension O This IE may be sent on the S5/S8, S4/S11 and S2a/S2b
Private Extension VS
interfaces.
NOTE1: Both Charging Gateway Name and Charging Gateway Address shall not be included at the same
time. When both are available, the operator configures a preferred value.
NOTE2: If the SGW cannot accept any of the "Bearer Context Created" IEs within Create Session Request
message, the SGW shall send the Create Session Response with appropriate reject Cause value.
NOTE 3: The last received value of the PGW Back-Off Time IE shall supersede any previous values received
from that PGW and for this APN in the MME/SGSN.
NOTE4: 3GPP TS 23.401 [3] (see subclause 5.3.1.1) and 3GPP TS 23.060 [35] (see subclause 9.2.1) specify
the handling of the cases when UE has requested IPv4v6 PDN Type, but PGW restricts the usage of
IPv4v6 PDN Type.
NOTE 5: The conditions of presence of the IEs in the Create Session Response for the MME and S4-SGSN
NOTE 6: The IP address and TEID/GRE key in "PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for
GTP based Control Plane interface" IE are only provided for the subsequent GTP-C initial messages
related to this PDN connection and shall NOT be used for other PDN connections.
NOTE 7: For PMIP based S5/S8, the 'S5/S8-U PGW F-TEID' IE and the 'PGW S5/S8/ S2a/S2b F-TEID for
PMIP based interface or for GTP based Control Plane interface' IE shall contain the same uplink
GRE key; the Interface Type in these IEs shall be set to the value 9 (S5/S8 PGW PMIPv6 interface).
NOTE 8: The Interface Identifier value of zero is a reserved value (see IETF RFC 5453 [58]). Subclause
5.3.1.2.2 of 3GPP TS 23.401 [3] specifies the mechanism for preventing UE"s link-local address
collision with the PGW"s link-local address.
NOTE 9: The receiver, not supporting the APN level load control feature, shall ignore all the occurrence(s) of
this IE, i.e. "Load Control Information" IE with instance number "1". The receiver, supporting the APN
level load control feature and supporting the APN level load information for the maximum of 10
APNs, shall handle the APN level load information for the first 10 APNs and ignore any more APN
level load information.
NOTE 10: The receiver, supporting the APN level overload information for the maximum of 10 APNs, shall
handle the APN level overload information for the first 10 APNs and ignore any more APN level
overload information.
NOTE 11: The APN level load information, provided within and across different instances of the "PGW's APN
level Load Control Information" IE(s) shall be limited to 10 different APNs.
NOTE 12: The APN level overload information, provided within and across different instances of the "PGW's
Overload Control Information" IE(s) shall be limited to 10 different APNs.
ETSI
Table 7.2.2-2: Bearer Context Created within Create Session Response
Octets 1 Bearer Context IE Type = 93 (decimal)

elements
Cause M This IE shall indicate if the bearer handling was successful, Cause 0
and if not, it gives information on the reason. (NOTE 1,
NOTE 2, NOTE 3)
S1-U SGW F-TEID C This IE shall be included on the S11 interface if the S1-U F-TEID 0
interface is used.
S4-U SGW F-TEID C This IE shall be included on the S4 interface if the S4-U F-TEID 1
interface is used.
S5/S8-U PGW F- C For GTP-based S5/S8, this User Plane IE shall be included F-TEID 2
TEID on S4/S11 and S5/S8 interfaces during the "E-UTRAN
Initial Attach", a Handover from Trusted or Untrusted Non-
3GPP IP Access to E-UTRAN, a "PDP Context Activation",
a Handover from Trusted or Untrusted Non-3GPP IP
Access to UTRAN/GERAN or a "UE Requested PDN
Connectivity".
For PMIP-based S5/S8, this IE shall be included on the
S4/S11 interface during the "E-UTRAN Initial Attach", a
to E-UTRAN, a "PDP Context Activation", a Handover from
Trusted or Untrusted Non-3GPP IP Access to
UTRAN/GERAN or a "UE Requested PDN Connectivity" if
the PGW provided an alternate address for user plane, i.e.
an IP address for user plane which is different from the IP
See NOTE 4 and NOTE 5.
S12 SGW F-TEID C This IE shall be included on the S4 interface if the S12 F-TEID 3
interface is used.
S2b-U PGW F-TEID C This IE (for user plane) shall be included on the S2b F-TEID 4
interface during the Attach with GTP on S2b, UE initiated
Connectivity to Additional PDN with GTP on S2b,
Handover to Untrusted Non-3GPP IP Access with GTP on
S2b, and Initial Attach for emergency session (GTP on
S2b).
S2a-U PGW F-TEID C This IE (for user plane) shall be included on the S2a F-TEID 5
interface during the Initial Attach in WLAN on GTP S2a,
S2a, and Handover to TWAN with GTP on S2a.
Bearer Level QoS C This IE shall be included on the S5/S8, S4/S11 and Bearer QoS 0
S2a/S2b interfaces if the received QoS parameters have
been modified.
C This IE shall be included on the S5/S8 interface for an E-
UTRAN initial attach, a Handover from Trusted or
Untrusted Non-3GPP IP Access to E-UTRAN, a PDP
Context Activation, a Handover from Trusted or Untrusted
Non-3GPP IP Access to UTRAN/GERAN and a UE
requested PDN connectivity.
O If the S5/S8 interface is GTP, this IE may be included on
the S4 interface, in order to support CAMEL charging at
the SGSN, for a PDP Context Activation, a Handover from
Charging Id Trusted or Untrusted Non-3GPP IP Access to Charging Id 0
UTRAN/GERAN, inter S4-SGSN RAU with SGW change
and Gn/Gp to S4-SGSN RAU.
CO This IE shall be included on the S2a/S2b interface for an
Initial Attach in WLAN on GTP S2a, Attach with GTP on
on S2b, Handover to Untrusted Non-3GPP IP Access with
GTP on S2b, Initial Attach for emergency session (GTP on
on S2a, and Handover to TWAN with GTP on S2a.
ETSI
Bearer Flags O Applicable flags are: Bearer Flags 0

- PPC (Prohibit Payload Compression) : this flag
may be set on the S5/S8 and S4 interfaces.
NOTE 1: According to 3GPP TS 23.401 [3] e.g. subclause 5.5.1.2.2 "S1-based handover, normal" and 3GPP
TS 23.060 [35], during the handover procedure with an SGW change, except in the case of X2-
handover (NOTE2 addresses X2 based HO with SGW change case), the target MME/S4-SGSN
initiates the Create Session Request/Response and Modify Bearer Request/Response procedures
one after the other. After receiving the "Bearer Context to be Created" IEs within Create Session
Request message, the SGW may not accept some of these bearers. The SGW however shall return
all bearers with the "Bearer Context Created" IEs within Create Session Response message (this
table), but with different Cause values. Bearers that were not accepted by the SGW shall have an
appropriate rejection value in the Cause IE. The target MME/S4-SGSN shall send these non-
accepted bearers to the target SGW within the "Bearer Context to be removed" IE in a subsequent
Modify Bearer Request message. Therefore, the SGW shall allocate the DL S5/S8 SGW F-TEIDs
also for the non-accepted bearers. MME/S4-SGSN should remove all of the non-accepted bearers by
separate procedures (e.g. an MME/S4-SGSN initiated Dedicated Bearer Deactivation procedure).
NOTE 2: According to 3GPP TS 23.401 [3] subclause 5.5.1.1.3, "X2-based handover with Serving GW
relocation", and 3GPP TS 23.060 [35] subclause 6.9.2.2.5A "Enhanced Serving RNS Relocation
Procedure using S4", during the X2-handover procedure with an SGW change and Enhanced
Serving RNS Relocation Procedure with an SGW change, the target MME/S4-SGSN shall initiate
only the Create Session Request/Response procedure. The SGW shall return all bearers (including
those not accepted by the SGW) with a "Bearer Context Created" IE within Create Session
Response message (this table), but with different Cause values. Bearers that were not accepted by
the SGW shall have an appropriate rejection value in the Cause IE, The MME/S4-SGSN should
remove these non-accepted bearers by separate procedures as well.
NOTE 3: According to 3GPP TS 23.401 [3] e.g. subclause 5.3.3.1 "Tracking Area Update procedure with
Serving GW change" and 3GPP TS 23.060 [35], during the RAU/TAU procedure with an SGW
change, the target MME/S4-SGSN shall initiate only the Create Session Request/Response
procedure. The SGW shall return all bearers (including those not accepted by the SGW) with a
"Bearer Context Created' IE within Create Session Response message (this table), but with different
Cause values. Bearers that were not accepted by the SGW shall have an appropriate rejection value
in the Cause IE. When Active Flag or Follow-on request is set during TAU/RAU procedure, MME/S4-
SGSN should not establish user plane tunnel over S1 or Iu for those bearer contexts which were not
accepted by the target SGW, while in the corresponding Modify Bearer Request message, the
MME/S4-SGSN shall include all accepted bearer contexts in the "Bearer Context to be modified" IE
and include all non-accepted bearer contexts in the "Bearer Context to be removed" IE. The
MME/S4-SGSN should remove the bearers non-accepted by either SGW or eNB/RNC by separate
procedures as well.
NOTE 4: The capability to receive from the LMA an alternate LMA address for user plane shall be supported
homogeneously across all the SGWs, when supported over PMIP-based S5/S8.
NOTE 5: For PMIP based S5/S8, the 'S5/S8-U PGW F-TEID' IE and the 'PGW S5/S8/ S2a/S2b F-TEID for
PMIP based interface or for GTP based Control Plane interface' IE shall contain the same uplink
GRE key; the Interface Type in these IEs shall be set to the value 9 (S5/S8 PGW PMIPv6 interface).
Table 7.2.2-3: Bearer Context marked for removal within a Create Session Response

elements
and if not, gives the information on the reason.
ETSI
Table 7.2.2-4: Load Control Information within Create Session Response
Octet 1 Load Control Information IE Type = 181 (decimal)

elements
Load Control M See clause 12.2.5.1.2.1 for the description and use of this Sequence 0
Load Metric M See clauses 12.2.5.1.2.2 and 12.2.5.1.2.3 for the Metric 0
description and use of this parameter.
List of APN and CO The IE shall (only) be present in the "PGW's APN level APN and Relative 0
Relative Capacity Load Control Information" IE. Capacity
For indicating the APN level load, the PGW shall include
one or more instances of this IE, up to maximum of 10,
with the same type and instance value, representing a list
of APN(s) & its respective "Relative Capacity" (sharing the
same "Load Metric").
See clause 12.2.5.1.2.3 for the description and use of this
parameter.
See NOTE 1.
NOTE 1: If more than 10 occurrences of "APN and Relative Capacity" IE are received within one instance of
the Load Control Information IE, the receiver shall treat it as a protocol error and ignore the entire
Load Control Information IE instance.
Table 7.2.2-5: Overload Control Information within Create Session Response

elements
Overload Reduction M See clauses 12.3.5.1.2.3 and 12.3.5.1.2.4 for the Metric 0
Metric description and use of this parameter.
parameter.
List of Access Point CO The IE may (only) be present in the "PGW's Overload APN 0
Name (APN) Control Information" IE.
For indicating the APN level overload, the PGW shall
include one or more instances of this IE, up to maximum of
10, with the same type and instance value, representing a
list of APN(s) (sharing the same "Overload Reduction
Metric" and "Period of Validity"). See NOTE 1.
NOTE 1: If more than 10 occurrences of APNs are received within one instance of the Overload Control
Information IE, the receiver shall treat it as a protocol error and ignore the entire Overload Control
Information IE instance.
7.2.3 Create Bearer Request

The direction of this message shall be from PGW to SGW and from SGW to MME/S4-SGSN, and from PGW to
TWAN/ePDG (see Table 6.1-1).
The Create Bearer Request message shall be sent on the S5/S8 interface by the PGW to the SGW and on the S11
interface by the SGW to the MME as part of the Dedicated Bearer Activation procedure.
The message shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to
the SGSN as part of the Secondary PDP Context Activation procedure or the Network Requested Secondary PDP
Context Activation procedure.
ETSI
The message shall also be sent on the S2a interface by the PGW to the TWAN as part of the Dedicated bearer activation
in WLAN on GTP S2a, and on the S2b interface by the PGW to the ePDG as part of the Dedicated S2b bearer
activation with GTP on S2b.
The message shall also be sent on the S5/S8 or S2a/S2b interface by the PGW to the SGW or to the TWAN/ePDG and
on the S11/S4 interface by the SGW to the MME/S4-SGSN as part of the Network-initiated IP flow mobility procedure
or the UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161 [71].
ETSI
Table 7.2.3-1: Information Elements in a Create Bearer Request

elements
Procedure C This IE shall be sent on the S5/S8 and S4/S11 interfaces PTI 0
Transaction Id (PTI) when the procedure was initiated by a UE Requested
Bearer Resource Modification Procedure or UE Requested
Bearer Resource Allocation Procedure (see NOTE 1) or
Secondary PDP Context Activation Procedure.
The PTI shall be the same as the one used in the
corresponding Bearer Resource Command.
Linked EPS Bearer ID M This IE shall be included to indicate the default bearer EBI 0
(LBI) associated with the PDN connection.
Protocol O This IE may be sent on the S5/S8 and S4/S11 interfaces. PCO 0
Configuration Options
(PCO)
Bearer Contexts M Several IEs with this type and instance values shall be Bearer Context 0
included as necessary to represent a list of Bearers.
PGW-FQ-CSID C This IE shall be included by the PGW on the S5/S8 and FQ-CSID 0
S2a/S2b interfaces and, when received from S5/S8 be
SGW-FQ-CSID C This IE shall be included by the SGW on the S11 interface FQ-CSID 1
Change Reporting C This IE shall be included on the S5/S8 and S4/S11 Change Reporting 0
Action interfaces with the appropriate Action field If the location Action
Change Reporting mechanism is to be started or stopped
CSG Information CO This IE shall be included on the S5/S8 and S4/S11 CSG Information 0
Reporting Action interfaces with the appropriate Action field if the CSG Info Reporting Action
reporting mechanism is to be started or stopped for this
information reporting is to be started or stopped for the Reporting
PDN connection in the SGSN/MME.
Presence Reporting
Area Action
MME/SGSN.
is set to 1.

serving PGW. The SGW shall set this flag on the

the SGW selection) of the serving SGW.
ETSI

clause 12.2.6).

See NOTE 2, NOTE 4.

12.3.11).

APN(s).
See NOTE 3, NOTE 5.
clause 12.3.11).

NBIFOM Container CO This IE shall be included on the S5/S8 and S2a/S2b F-Container 0
interfaces if the PGW needs to send NBIFOM information
as specified in 3GPP TS 23.161 [71]. The Container Type
shall be set to 4.
CO If the SGW receives a NBIFOM Container IE from the
PGW, the SGW shall forward it to the MME/S4-SGSN on
Private Extension O This IE may be sent on the S5/S8, S4/S11 and S2a/S2b Private Extension VS
interfaces.
NOTE 1: This message refers to the UE requested bearer resource allocation procedure and UE requested
bearer resource modification procedures defined in 3GPP TS 24.301 [23], both are specified in
3GPP TS 23.401 [3] in the clause "UE requested bearer resource modification".
ETSI
NOTE: In the case that the procedure was initiated by a UE Requested Bearer Resource Modification Procedure
or a UE Requested Bearer Resource Allocation Procedure or Secondary PDP Context Activation
Procedure, then there will be only one instance of the Bearer Contexts IE in the Create Bearer Request.
Table 7.2.3-2: Bearer Context within Create Bearer Request

elements
EPS Bearer ID M This IE shall be set to 0. EBI 0
TFT M This IE can contain both uplink and downlink packet filters Bearer TFT 0
to be sent to the UE or the TWAN/ePDG.
S1-U SGW F-TEID C This IE shall be sent on the S11 interface if the S1-U F-TEID 0
S5/8-U PGW F-TEID C This IE shall be sent on the S4, S5/S8 and S11 interfaces F-TEID 1
for GTP-based S5/S8 interface. The MME/SGSN shall
ignore the IE on S11/S4 for PMIP-based S5/S8 interface.
S12 SGW F-TEID C This IE shall be sent on the S4 interface if the S12 F-TEID 2
S4-U SGW F-TEID C This IE shall be sent on the S4 interface if the S4-U F-TEID 3
S2b-U PGW F-TEID C This IE (for user plane) shall be sent on the S2b interface. F-TEID 4
S2a-U PGW F-TEID C This IE (for user plane) shall be sent on the S2a interface. F-TEID 5
C This IE shall be sent on the S5/S8 interface.
O If the S5/S8 interface is GTP, this IE may be sent on the
Charging Id S4 interface, in order to support CAMEL charging at the Charging Id 0
SGSN.
CO This IE shall be sent on the S2a/S2b interface.
Bearer Flags O Applicable flags are: Bearer Flags 0
- PPC (Prohibit Payload Compression) : this flag
may be set on the S5/S8 and S4 interfaces.
- vSRVCC indicator: This IE may be included by the

PGW on the S5/S8 interface according to 3GPP
TS 23.216 [43]. When received from S5/S8, SGW
shall forward on the S11 interface.
Protocol O This IE may be sent on the S5/S8 and S4/S11 interfaces. PCO 0
Configuration Options This bearer level IE takes precedence over the PCO IE in
(PCO) the message body if they both exist.
NOTE 1: The SGW shall use the same F-TEID IP address and TEID values for S1-U, S4-U and S12
interfaces.
ETSI
Table 7.2.3-3: Load Control Information within Create Bearer Request

elements
parameter.
See NOTE 1.
Table 7.2.3-4: Overload Control Information within Create Bearer Request

elements
parameter.
Metric" and "Period of Validity").
See NOTE 1.
7.2.4 Create Bearer Response

The Create Bearer Response message shall be sent on the S5/S8 interface by the SGW to the PGW, and on the S11
interface by the MME to the SGW as part of the Dedicated Bearer Activation procedure.
The message shall also be sent on the S5/S8 interface by the SGW to the PGW and on the S4 interface by the SGSN to
the SGW as part of Secondary PDP Context Activation procedure or the Network Requested Secondary PDP Context
Activation procedure.
ETSI
The message shall also be sent on the S2a interface by the TWAN to the PGW as part of the Dedicated bearer activation
in WLAN on GTP S2a and on the S2b interface by the ePDG to the PGW as part of the Dedicated S2b bearer activation
with GTP on S2b.
The message shall also be sent on the S5/S8 or S2a/S2b interface by the SGW or the TWAN/ePDG to the PGW and on
the S11/S4 interface by the MME/S4-SGSN to the SGW as part of the Network-initiated IP flow mobility procedure or
UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161 [71].
- "Unable to page UE".
- "UE not responding".
- "Unable to page UE due to Suspension".
- "UE refuses".
- "Denied in RAT".
- "Temporarily rejected due to handover/TAU/RAU procedure in progress".
- "MME/SGSN refuses due to VPLMN Policy".
- "UE is temporarily not reachable due to power saving".
ETSI
Table 7.2.4-1: Information Elements in a Create Bearer Response

elements
Cause M Cause 0
Bearer Contexts M All the bearer contexts included in the corresponding Bearer Context 0
Create Bearer Request shall be included. Several IEs with
this type and instance value shall be included on the
S4/S11, S5/S8 and S2a/S2b interfaces as necessary to
represent a list of Bearers.
Recovery C This IE shall be included on the S4/S11, S5/S8 and Recovery 0
MME-FQ-CSID C This IE shall be included by the MME on the S11 FQ-CSID 0
interfaceand shall be forwarded by the SGW on the S5/S8
interfaces according to the requirements in 3GPP TS
23.007 [17].
SGW-FQ-CSID C This IE shall be included by the SGW on the S5/S8 FQ-CSID 1
interfaces according to the requirements in 3GPP TS
23.007 [17].
ePDG-FQ-CSID C This IE shall be included by the ePDG on the S2b interface FQ-CSID 2
23.007 [17].
Protocol C If the UE includes the PCO IE, then the MME/SGSN shall PCO 0
Configuration Options copy the content of this IE transparently from the PCO IE
(PCO) included by the UE. If the SGW receives PCO from
MME/SGSN, SGW shall forward it to the PGW.
O This IE is optionally included by the MME on the S11
interface or by the SGSN on the S4 interface.
CO The SGW shall forward this IE on the S5/S8 interface if the
CO This IE shall be included by the TWAN on the S2a
interface.
CO This IE shall be included by the MME on the S11 interface
or by the SGSN on the S4 interface. The CGI/SAI shall be
included by SGSN and the ECGI shall be included by
User Location
MME. ULI 0
Information (ULI)
See NOTE 1.
CO The SGW shall forward this IE on the S5/S8 interface if it
receives it from the MME/SGSN.
TWAN Identifier TWAN Identifier 0
interface as specified in 3GPP TS 23.402 [45].
Overload Control
Overload Control 0
Information
interface.
Presence Reporting CO The MME/SGSN shall include this IE on S11/S4 if the Presence 0
Area Information PGW/PCRF has requested to start reporting changes of Reporting Area
UE presence in a Presence Reporting Area in the Information
corresponding Create Bearer Request message and the
MME/SGSN supports such reporting. The MME/SGSN
shall then indicate whether the UE is inside or outside the
Presence Reporting Area.
ETSI

Presence Reporting Area Information from the
MME/SGSN.
CO If the overload control feature is supported by the MME/S4-
include this IE on the S11/S4 interface if the PGW has not
MME/S4-SGSN
been updated with the identity of the currently serving IP Address 0
Identifier
MME/S4-SGSN, i.e. if no other message carrying
MME/S4-SGSN identity has been sent to the PGW
during/after an inter-MME/S4-SGSN intra-SGW mobility
procedure.
TWAN/ePDG's
Overload Control 2
Information
WLAN Location CO The ePDG shall include this IE on the S2b interface if the
TWAN Identifier 1
Information WLAN Location Information is available.
WLAN Location CO The ePDG shall include this IE on the S2b interface, if the TWAN Identifier
1
Timestamp WLAN Location Timestamp is available. Timestamp
UE Local IP Address CO The ePDG shall include this IE on the S2b interface. IP Address 0
is detected.
NBIFOM Container CO This IE shall be included on the S11/S4 or S2a/S2b F-Container 0
receives a NBIFOM Container from the UE as specified in
3GPP TS 23.161 [71]. The Container Type shall be set to
4.
MME/S4-SGSN, the SGW shall forward it to the PGW on
interfaces.
ETSI
Table 7.2.4-2: Bearer Context within Create Bearer Response

elements
and if not, it gives information on the reason.
S1-U eNodeB F-TEID C This IE shall be sent on the S11 interface if the S1-U F-TEID 0
interface is used.
S1-U SGW F-TEID C This IE shall be sent on the S11 interface. It shall be used F-TEID 1
to correlate the bearers with those in the Create Bearer
Request.
S5/8-U SGW F-TEID C This IE shall be sent on the S5/S8 interfaces. F-TEID 2
S5/8-U PGW F-TEID C This IE shall be sent on the S5/S8 interfaces. It shall be F-TEID 3
used to correlate the bearers with those in the Create
Bearer Request.
S12 RNC F-TEID C This IE shall be sent on the S4 interface if the S12 F-TEID 4
interface is used. See NOTE1.
S12 SGW F-TEID C This IE shall be sent on the S4 interface. It shall be used to F-TEID 5
correlate the bearers with those in the Create Bearer
Request. See NOTE1.
S4-U SGSN F-TEID C This IE shall be sent on the S4 interface if the S4-U F-TEID 6
interface is used. See NOTE1.
S4-U SGW F-TEID C This IE shall be sent on the S4 interface. It shall be used to F-TEID 7
correlate the bearers with those in the Create Bearer
Request. See NOTE1.
S2b-U ePDG F-TEID C This IE shall be sent on the S2b interface. F-TEID 8
S2b-U PGW F-TEID C This IE shall be sent on the S2b interface. It shall be used F-TEID 9
Request.
S2a-U TWAN F-TEID C This IE shall be sent on the S2a interface. F-TEID 10
S2a-U PGW F-TEID C This IE shall be sent on the S2a interface. It shall be used F-TEID 11
Request.
Protocol CO If the UE includes the PCO IE in the corresponding PCO 0
Configuration Options message, then the MME/SGSN shall copy the content of
(PCO) this IE transparently from the PCO IE included by the UE.
If the SGW receives PCO from MME/SGSN, SGW shall
forward it to the PGW. This bearer level IE takes
precedence over the PCO IE in the message body if they
both exist.
RAN/NAS Cause CO If the bearer creation failed, the MME shall include this IE RAN/NAS Cause 0
on the S11 interface to indicate the RAN cause and/or the
NAS cause of the bearer creation failure, if available and if
this information is permitted to be sent to the PGW
operator according to MME operator's policy.
If both a RAN cause and a NAS cause are generated, then
several IEs with the same type and instance value shall be
included to represent a list of causes.
The SGW shall include this IE on the S5/S8 interface if it
receives it from the MME.
CO If the bearer creation failed, the TWAN shall include this IE
on the S2a interface to indicate the cause of the bearer
creation failure, if available and if this information is
permitted to be sent to the PGW operator according to the
TWAN operator's policy. When present, the IE shall be
encoded as a Diameter or an ESM cause. See NOTE 2.
CO If the bearer creation failed, the ePDG shall include this IE
on the S2b interface to indicate the cause of the bearer
creation failure, if available and if this information is
ePDG operator's policy. When present, the IE shall be
encoded as a Diameter or an IKEv2 cause. See NOTE 3.
ETSI
interfaces. However, when sending a Create Bearer Request message to an S4-SGSN for a UE in
idle mode, the SGW can not know whether the S4-SGSN will establish a direct user plane tunnel
between the RNC and the SGW. The SGW may include either the S4-U SGW F-TEID IE or the S12
SGW F-TEID IE in the Create Bearer Request message. The S4-SGSN will decide whether to
establish a direct user plane tunnel or not and will provide accordingly either a S12 RNC F-TEID or a
S4-U SGSN F-TEID in the Create Bearer Response message, where the interface type of the
provided F-TEID may differ from the interface type of the SGW F-TEID used for bearer correlation,
e.g. if the SGW includes the S4-U SGW F-TEID in the Create Bearer Request message, and if the
SGSN decides to use Direct Tunnelling, the S4-SGSN shall provide the S12 RNC F-TEID in the
Create Bearer Response message, together with S4-U SGW F-TEID. The SGW should not treat this
as an error.
NOTE 2: The TWAN does not exchange signalling with the 3GPP AAA Server nor with the UE in this
procedure. The TWAN may include an internal failure cause for the bearer creation failure. The
protocol type used to encode the internal failure cause is implementation specific.
NOTE 3: The ePDG does not exchange signalling with the 3GPP AAA Server in this procedure. The ePDG
may include an internal failure cause for the bearer creation failure. The protocol type used to encode
the internal failure cause is implementation specific.
Table 7.2.4-3: Overload Control Information within Create Bearer Response

elements
Metric parameter.
parameter.
7.2.5 Bearer Resource Command

A Bearer Resource Command message shall be sent from a MME to a SGW and forwarded to PGW as a part of the UE
requested bearer resource allocation procedure or UE requested bearer resource modification procedure (which is used
also for a dedicated bearer deactivation) , as specified by 3GPP TS 24.301 [23].
The message shall also be sent on the S4 interface by a SGSN to a SGW and on the S5/S8 interface by a SGW to a
PGW as part of the MS initiated PDP Context modification procedure, or secondary PDP context activation procedure.
The message shall also be sent on the S11/S4 interface by an MME/S4-SGSN to a SGW and on the S5/S8 or S2a/S2b
interface by a SGW or a TWAN/ePDG to a PGW as part of the UE-initiated IP flow mobility procedure and the UE
requested IP flow mapping procedure, as specified by 3GPP TS 23.161 [71].
Table 7.2.5-1 specifies the presence of the IEs in the message.
ETSI
Table 7.2.5-1: Information Elements in a Bearer Resource Command

elements
Linked EPS Bearer ID M EBI 0
(LBI)
Procedure M PTI 0
Transaction Id (PTI)
Flow Quality of C This IE shall be included on the S4/S11 interface if the Flow QoS 0
Service (Flow QoS) "Requested New QoS"/"Required QoS" is included in the
corresponding NAS message (see section 9.5.10 and
section 9.5.4 in 3GPP TS 24.008 [5]) or the "Required
traffic flow QoS" is included in the corresponding NAS
message (see section 8.3.8 and section 8.3.10 in 3GPP
TS 24.301 [23]).
If SGW receives this IE, SGW shall forward it to PGW
M The TAD consists of the description of the packet filter(s)
for a traffic flow aggregate.
MME shall include this IE over S11 interface.
Traffic Aggregate
CO If S4-SGSN receives this IE from the UE, it shall include it TAD 0
Description (TAD)
over S4 interface.
CO If SGW receives this IE, the SGW shall forward it to PGW
over S5/S8 interface. See NOTE 2.
RAT Type C This IE shall be included for MS initiated PDP Context RAT Type 0
modification procedure and Secondary PDP context
activation procedure.
Serving Network O This IE may be included in the MS initiated PDP Context Serving Network 0
modification procedure.
See NOTE 3.
User Location O This IE may be included in the MS initiated PDP Context ULI 0
Information (ULI) modification procedure.
See NOTE 3.
EPS Bearer ID C This IE indicates the EPS Bearer that needs to be EBI 1
modified. It shall be included for MS initiated PDP Context
modification procedure. For EUTRAN this IE shall be
present if it is triggered by the NAS Bearer Resource
Modification Request message and its value shall be set to
the value of the "EPS bearer identity for packet filter" IE
received in that NAS message.
is set to 1.
Applicable flags:
- Change Reporting Support Indication: this flag
may be set to 1 in the MS initiated PDP Context
modification procedure if the SGSN/MME supports
location Info Change Reporting and if the
SGSN/MME's operator policy permits reporting of
location change to the operator of the PGW with
which the session is established.
- Direct Tunnel Flag: this flag shall be set to 1 on the

S4 interface, if Direct Tunnel is used in the MS
initiated PDP Context Modification procedure.
S4-U SGSN F-TEID C This IE shall be included on the S4 interface when direct F-TEID 0
tunnel is not established in the MS initiated PDP Context
modification procedure See NOTE 1
S12 RNC F-TEID C This IE shall be included on the S4 interface when direct F-TEID 1
tunnel flag is set to 1 in the MS initiated PDP Context
modification procedure. See NOTE 1
Protocol O PCO 0
Configuration Options
(PCO)
Signalling Priority CO The SGSN/MME shall include this IE on the S4/S11 Signalling Priority 0
Indication interface if the UE indicates low access priority during the Indication
procedure.
The SGW shall forward this IE on the S5/S8 interfaces if
ETSI
received from the MME/SGSN.

Overload Control
Overload Control 0
Information
interface.
receives an NBIFOM Container from the UE as specified in
4.
CO If the SGW receives an NBIFOM Container IE from the
NOTE 1: The conditional S4-U SGSN F-TEID and S12 RNC F-TEID IE are redundant (as the IEs will be
included in Update Bearer Response message in the MS initiated PDP Context modification
procedure). The receiver may ignore it.
NOTE 2: In the secondary PDP context activation procedure, if the Bearer Resource Command message
without TAD IE is received, the PGW shall reject the message with cause "UE context without TFT
already activated".
Editor's Note: Possible impact on the setting of TAD is FFS for NBIFOM.
NOTE: Depending on the protocol type on the S5/S8 interface, the SGW or the PGW will determine if the UE is
requesting an Allocation/Modification operation of bearer resources for a traffic flow aggregate based on
the TFT operation code and the packet filter ID value in the Traffic Aggregate (TAD) IE and/or the
presence of the EPS Bearer ID IE.
ETSI
Table 7.2.5-2: Overload Control Information within Bearer Resource Command

elements
Metric parameter.
parameter.
7.2.6 Bearer Resource Failure Indication

A Bearer Resource Failure Indication shall be sent by the PGW to an SGW and forwarded to the MME to indicate
failure of the UE requested bearer resource allocation procedure or UE requested bearer resource modification
procedure, as specified by 3GPP TS 24.301 [23].
The message shall also be sent by a PGW to an SGW and forwarded to an SGSN as part of the failure of an MS
initiated PDP Context modification procedure or secondary PDP context activation procedure.
The message shall also be sent on the S5/S8 or S2a/S2b interface by a PGW to a SGW or to a TWAN/ePDG and the
S11/S4 interface by a SGW to an MME/S4-SGSN as part of the UE-initiated IP flow mobility procedure and the UE
requested IP flow mapping procedure, as specified by 3GPP TS 23.161 [71].
- "Semantic error in the TAD operation".
- "Syntactic error in the TAD operation".
- "Collision with network initiated request".
- "Service denied".
- "Bearer handling not supported".
- "UE context without TFT already activated".
ETSI
Table 7.2.6-1: Information Elements in a Bearer Resource Failure Indication

elements
Cause M Cause 0
Linked EPS Bearer ID M See subclause 6.1.1 "Presence requirements of EBI 0
Information Elements".
Procedure M See subclause 6.1.1 "Presence requirements of PTI 0
Transaction ID (PTI) Information Elements".
is set to 1.


Control Information on the S5/S8, if the overload control feature is supported Information
by the PGW and is activated for the PLMN to which the
access network node, i.e. MME/S4-SGSN for 3GPP
access based network, belongs (see clause 12.3.11).

APN(s).
See NOTE 1, NOTE 2.
clause 12.3.11).

Recovery O Recovery 0
shall be set to 4.
CO If the SGW receives an NBIFOM Container IE from the
ETSI
Table 7.2.6-2: Overload Control Information within Bearer Resource Failure Indication

elements
parameter.
See NOTE 1.
7.2.7 Modify Bearer Request

The direction of this message shall be from MME/S4-SGSN to SGW and/or from SGW to PGW (see Table 6.1-1).
The Modify Bearer Request message shall only be sent on the S11 interface by the MME to the SGW and on the S5/S8
interfaces by the SGW to the PGW as part of the procedures:
- E-UTRAN Tracking Area Update without SGW Change
- UE triggered Service Request
- S1-based Handover
- UTRAN Iu mode to E-UTRAN Inter RAT handover
- GERAN A/Gb mode to E-UTRAN Inter RAT handover
- E-UTRAN Initial Attach
- Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with GTP on S5/S8 interface (see sub-
clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402 [45])
- UE requested PDN connectivity
- 3G SGSN to MME combined hard handover and SRNS relocation procedure
- X2-based handover without SGW relocation
- UTRAN/GERAN to E-UTRAN SRVCC
- HSS-based P-CSCF restoration for 3GPP access (see 3GPP TS 23.380 [61])
It shall also only be sent on the S11 interface by the MME to the SGW as part of the procedure:
ETSI
- E-UTRAN Initiated E-RAB modification procedure
- Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with PMIP on S5/S8 interface (see sub-
clauses 8.2 and 16.11 of 3GPP TS 23.402 [45])
- Tracking Area Update procedure with Serving GW change and data forwarding
It shall also only be sent on the S4 interface by the SGSN to the SGW and on the S5/S8 interfaces by the SGW to the
PGW as part of the procedures:
- Routeing Area Update with MME interaction and without SGW change
- E-UTRAN to UTRAN Iu mode Inter RAT handover
- E-UTRAN to GERAN A/Gb mode Inter RAT handover
- Inter SGSN Routeing Area Update Procedure and Combined Inter SGSN RA / LA Update to S4 SGSNs without
SGW change
- Iu mode RA Update Procedure without SGW change
- Serving RNS Relocation Procedure
- Combined Hard Handover and SRNS Relocation Procedure
- Combined Cell / URA Update and SRNS Relocation Procedure
- Enhanced Serving RNS Relocation without SGW relocation
- UE Initiated Service Request Procedure
- Iu mode to A/Gb mode Intra SGSN Change
- A/Gb mode to Iu mode Intra SGSN Change
- Iu mode to A/Gb mode Inter-SGSN Change
- A/Gb mode to Iu mode Inter-SGSN Change
- Paging Response with no established user plane on S4
- PDP Context Activation Procedure
- Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with GTP on S5/S8 interface
(see sub-clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402 [45])
- UTRAN/GERAN to UTRAN (HSPA) SRVCC
- HSS-based P-CSCF restoration for 3GPP access (see 3GPP TS 23.380 [61])
It shall also only be sent on the S4 interface by the SGSN to the SGW as part of the procedures:
- RAB Assignment Procedure
- SRVCC from E-UTRAN to UTRAN or GERAN with DTM HO support procedures and SRVCC from UTRAN
(HSPA) to UTRAN or GERAN with DTM HO support.
- Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with PMIP on S5/S8 interface
(see sub-clauses 8.2 and 16.11 of 3GPP TS 23.402 [45])
- Routeing Area Update procedure with Serving GW change and data forwarding
and only on the S5/S8 interfaces by the SGW to the PGW as part of the procedures:
- Tracking Area Update procedure with SGW change
- Gn/Gp SGSN to S4 SGSN Routing Area Update
ETSI
- X2 based handover with SGW relocation
- Gn/Gp SGSN to MME Tracking Area Update
- Enhanced Serving RNS Relocation with SGW relocation
- Routeing Area Update with MME interaction and with SGW change
- Inter SGSN Routeing Area Update Procedure and Combined Inter SGSN RA / LA Update using S4 with SGW
change
- Iu mode RA Update Procedure using S4 with SGW change
- Restoration of PDN connections after an SGW failure if the MME/SGSN and PGW support these procedures as
- PGW Pause of Charging procedure
and on the S2b interface by the ePDG to the PGW as part of the procedures:
- UE initiated IPsec tunnel update procedure
If the optional network triggered service restoration feature is supported by the MME, SGSN and SGW, then the
Modify Bearer Request message shall also be sent as part of the network triggered service restoration procedure with
ISR during an intra MME TAU and an intra S4-SGSN RAU procedure for UEs that had ISR active before either the
MME or the S4-SGSN has restarted, as specified in 3GPP TS 23.007 [17]:
- on the S11 interface by the MME to the SGW, if the MME detected that the ISR associated S4-SGSN has
restarted and UE performs a TAU procedure;
- on the S4 interface by the S4-SGSN to the SGW, if the S4-SGSN detected that the ISR associated MME has
restarted and UE performs a RAU procedure.
This message can be used as an implicit resume of the suspended bearers in the SGW and in the PGW (see 3GPP TS
23.216 [43] sections 6.2.2.1 and 6.3.2.1, 3GPP TS 23.272 [21] sections 6.3, 6.5 and 7.4). A Modify Bearer Request used
as an implicit resume can contain zero or more IE(s), depending on the conditions of presence of the IEs specified in
table 7.2.7-1. The PGW should not consider a Modify Bearer Request with zero IE as an error.
The Modify Bearer Request message may also be sent in the following cases from the S4-SGSN to the SGW/PGW to
report a change of Serving Network, User CSG Information or/and UE Time Zone which occured during a previous
RAU procedure without SGSN change but which has not been reported yet to the SGW/PGW, or to indicate to the
PGW that the UE is available for signalling if the PDN connection is delay tolerant and if there is pending network
initiated PDN connection signalling:
- during a Service Request procedure to establish data radio bearers for the corresponding PDP context for a UE in
UTRAN with an existing S4-U tunnel;
- when the SGSN receives an uplink LLC PDU for user data or any valid LLC frame serving as a paging response
from a UE in GERAN with an existing S4-U tunnel.
The Modify Bearer Request message may also be sent in the following cases from the S4-SGSN to the SGW/PGW to
report a change of User Location Information which occured during a previous RAU procedure without SGSN change
but which has not been reported yet to the SGW/PGW, if the S4-SGSN is configured to defer the reporting of ULI
change until a RAB/user plane is established:
- during a Service Request procedure to establish data radio bearers for the corresponding PDP context for a UE in
UTRAN with an existing S4-U tunnel;
- when the SGSN receives an uplink LLC PDU for user data or any valid LLC frame serving as a paging response
for a UE in GERAN with an existing S4-U tunnel.
ETSI
NOTE 1: the S4-SGSN can alternatively send a Change Notification Request message in the above cases, if no
other information which requires the sending of a Modify Bearer Request, needs to be reported to the
PGW.
When requesting the PGW to pause or unpause charging for a PDN connection, the SGW shall wait for the PGW
acknowledgement (i.e. Modify Bearer Response) before sending a new pause or unpause request.
NOTE 2: this ensures that the PGW always act per the most recent SGW request in particular in scenarios where
the SGW would need to request the PGW to pause and unpause charging in a row (or vice-versa) and the
Modify Bearer Request messages would arrive out of order at the PGW.
Upon receipt of a request from the PGW/PCRF in a message other than Create Bearer Request and Update Bearer
Request to report changes of UE presence in a Presence Reporting Area, the MME/S4-SGSN shall immediately send a
Modify Bearer Request message or a Change Notification Request message to report to the PGW whether the UE is
inside or outside the Presence Reporting Area.
The MME/S4-SGSN shall also send a Modify Bearer Request message or a Change Notification Request message to
report any subsequent change of UE presence in the Presence Reporting Area, as specified in 3GPP TS 23.401 [3] and
3GPP TS 23.060 [35].
If the Modify Bearer Request message is sent from the old MME/SGSN as part of Tracking/Routeing Area Update
procedure with SGW change and data forwarding as specified in subclause 5.3.3.1A of 3GPP TS 23.401 [3], the old
MME/SGSN shall only include the Bearer Contexts to be modified IE.
NOTE 3: Since the UE has left the old MME/SGSN, some information related to the UE, e.g. ULI, UE Time Zone,
CSG, RAT Type in the old MME/SGSN are not valid any more.
Upon receipt of a Modify Bearer Request message that includes the Presence Reporting Area Information from the
MME/S4-SGSN, the SGW shall send a Modify Bearer Request message on the S5/S8 interface if any of the following
condition is met:
- ISR is not active;
- ISR is active, and the RAT Type has changed since last reported or the CPRAI flag has been set to 1.
ETSI
Table 7.2.7-1: Information Elements in a Modify Bearer Request

elements
ME Identity (MEI) C If an SGW receives this IE from an MME/SGSN during a MEI 0
TAU/RAU/Handover procedure, the SGW shall forward it
across the S5/S8 interface to the PGW.
User Location C The MME/SGSN shall include this IE for the ULI 0
Information (ULI) TAU/RAU/Handover procedures if the PGW/PCRF has (NOTE 15)
requested location information change reporting and
MME/SGSN support location information change reporting.
An MME/SGSN which supports location information
change shall include this IE for UE-initiated Service
Request procedure if the PGW/PCRF has requested
location information change reporting and the UE"s
location info has changed. See NOTE 5, NOTE 17.
When ISR is active, the MME/SGSN which supports

location information change shall include this IE for UE-
initiated Service Request procedure, if the PGW/PCRF has
requested location information change reporting.
TAU/RAU/Handover with MME/SGSN change without
SGW change procedure, if the level of support (User
Location Change Reporting and/or CSG Information
Change Reporting) changes.
CGI/SAI together with RAI in the ULI. See NOTE 10.
handover procedure with SGW change procedure if
- the level of support (User Location Change
Reporting and/or CSG Information Change
Reporting) changes; or
- the target MME/S4-SGSN can not derive the level

of support (User Location Change Reporting and/or
CSG Information Change Reporting) for the source
Gn/Gp SGSN. See NOTE 14.
CGI/SAI together with RAI in the ULI. See NOTE 10.
CO This IE shall also be included on the S11/S4 interface
during the following procedures if the MME/SGSN is
configured to defer the reporting of ULI change until an E-
RAB/RAB/ user plane is established, the ULI has changed
during previous mobility procedures i.e. intra MME/S4-
SGSN TAU/RAU, and the change has not been reported to
the PGW yet:
- UE initiated Service Request, TAU or RAU with a
request to establish data radio bearers;
- when the SGSN receives an uplink LLC PDU for

user data or any valid LLC frame serving as a
paging response for a UE in GERAN with an
existing S4-U tunnel.
CO This IE shall also be included on the S4/S11 interface for:

- a TAU/Handover procedure with an S4-SGSN
interaction, if the MME supports location information
change reporting;
- a RAU/Handover procedure with an MME

interaction, if the SGSN supports location
information change reporting.
The MME shall include the ECGI and TAI in the ULI. The
S4-SGSN shall include the RAI and, if available, the
ETSI
CGI/SAI information, in the ULI.

CO When ISR is not active, the SGW shall include this IE on
S5/S8 if it receives the ULI from MME/SGSN.
When ISR is active, the SGW shall include this IE on

S5/S8 if
- it receives the ULI from MME/S4-SGSN and the
RAT Type has changed since last reported; or
- it receives the ULI from MME/S4-SGSN and the

CLII flag has been set to 1.
CO This IE shall be included on S11/S4 interface during the

following procedures:
- TAU/RAU/handover if Serving Network is changed.
- TAU/RAU when the UE was ISR activated which is

indicated by ISRAU flag.
- UE triggered Service Request when UE is ISR

activated.
- UE initiated Service Request if ISR is not active, but

the Serving Network has changed during previous
mobility procedures, i.e. intra MME/S4-SGSN
TAU/RAU and the change has not been reported to
Serving Network the PGW yet.
Serving Network
0
- TAU/RAU procedure as part of the optional network (NOTE 15)
triggered service restoration procedure with ISR, as
specified by 3GPP TS 23.007 [17].

during a TAU/RAU/Handover with MME/SGSN change if
the source MME/SGSN has set the SNCR bit in the
Change to Report Flags IE in the Forward Relocation
Request or Context Response message.
CO This IE shall be included on S5/S8 if the SGW receives this
IE from MME/SGSN and if ISR is not active.
This IE shall be included on S5/S8 if the SGW receives this
IE from MME/SGSN and ISR is active and the Modify
Bearer Request message needs to be sent to the PGW as
specified in the 3GPP TS 23.401 [3].
RAT Type C This IE shall be sent on the S11 interface for a TAU with RAT Type 0
an SGSN interaction, UE triggered Service Request or an
I-RAT Handover.
This IE shall be sent on the S4 interface for a RAU with
MME interaction, a RAU with an SGSN change, a UE
Initiated Service Request or an I-RAT Handover.
This IE shall be sent on the S5/S8 interface if the RAT type
changes.
CO If SGW receives this IE from MME/SGSN during a
TAU/RAU/Handover with SGW change procedure, the
SGW shall forward it across S5/S8 interface to PGW. See
NOTE 10.
CO The IE shall be sent on the S11/S4 interface during the
following procedures:
- an inter MME TAU or inter SGSN RAU when UE
was ISR activated which is indicated by ISRAU flag.
- TAU/RAU procedure as part of optional network

triggered service restoration procedure with ISR, as
specified by 3GPP TS 23.007 [17].
If ISR is active, this IE shall also be included on the S11

interface in the S1-U GTP-U tunnel setup procedure during
an intra-MME intra-SGW TAU procedure.
Indication Flags C This IE shall be included if any one of the applicable flags Indication 0
is set to 1.
ETSI

- Idle mode Signalling Reduction Activation
Indication: This flag shall be set to 1 on S4/S11
interface, if the ISR is established between the
MME and the S4 SGSN.
- Handover Indication: This flag shall be set to 1 on

the S4/S11 and S5/S8 interfaces during a
Handover from Trusted or Untrusted Non-3GPP IP
Access to E-UTRAN or a Handover from Trusted
or Untrusted Non-3GPP IP Access to
UTRAN/GERAN procedures..

the S4 interface, if Direct Tunnel is used.
- Change Reporting Support Indication: shall be set

to 1 on S4/S11, S5/S8 interfaces, if the
SGSN/MME supports location Info Change
Reporting and if the SGSN/MME's operator policy
permits reporting of location change to the
established. This flag should be ignored by SGW if
no message is sent on S5/S8. See NOTE 4.
- CSG Change Reporting Support Indication: shall

be set to 1 on S4/S11, S5/S8, if the SGSN/MME
supports CSG Information Change Reporting and
if the SGSN/MME's operator policy permits
reporting of the CSG Information change to the
established. This flag shall be ignored by SGW if
no message is sent on S5/S8. See NOTE 4.
- Change F-TEID support Indication: This flag shall

be set to 1 on S4/S11 for an IDLE state UE
initiated TAU/RAU procedure to allow the SGW
changing the GTP-U F-TEID.
- Propagate BBAI Information Change:

The MME/SGSN shall set this flag to 1 on S11/S4
in procedures without MME/SGSN change if the
PGW has requested H(e)NB information reporting
and the H(e)NB local IP address or UDP port
number information from H(e)NB in UE associated
S1/Iu signalling has changed.
(NOTE 8)
The MME/SGSN shall set this flag to 1 on S11/S4
during TAU/RAU/Handover with MME/SGSN
change procedures if the PGW has requested
H(e)NB information reporting.
See 3GPP TS 23.139 [51].
- CS to PS SRVCC indication: This flag shall be set

to 1 on S4/S11 and on S5/S8 during
UTRAN/GERAN to E-UTRAN/UTRAN (HSPA)
SRVCC procedure as specified in 3GPP TS
23.216 [43].
- Change of Location Information Indication (CLII):

This flag shall be set to 1 on S4/S11 interface only
when the ISR is active for the UE. This flag shall
be set to 1 by the MME/S4-SGSN if the ULI IE is
included in the Modify Bearer Request message
and the location information has changed since
last reported by the MME/S4-SGSN. See NOTE 9.
.
ETSI
set to 1 on the S5/S8 interface during the

TAU/RAU/handover with SGW relocation
procedures if the new SGW supports the PGW
Pause of Charging procedure.
- PDN Pause On Indication: this flag shall be set to

1 on the S5/S8 interface if the SGW requests the
PGW to pause the charging for the PDN
connection as specified in 3GPP TS 23.401 [3].
(NOTE 13).
- PDN Pause Off Indication: this flag shall be set to

1 on the S5/S8 interface if the SGW requests the
PGW to unpause the charging for the PDN
connection as specified in 3GPP TS 23.401 [3].
(NOTE 13).
- Change of Presence Reporting Area information

Indication (CPRAI): this flag shall be set to 1 on
the S4/S11 interface if ISR is active for the UE and
if the Presence Reporting Area Information IE is
included in the Modify Bearer Request message
and the Presence Reporting Area information has
changed since last reported by the MME/S4-
SGSN. See NOTE 9.
- P-CSCF Restoration Indication: this flag shall be

set to 1 on the S11/S4 and S5/S8 interfaces, for
the IMS PDN connection, if the MME/S4-SGSN
has received the indication from the HSS that a P-
CSCF restoration is required for this user.
- UE Available for Signalling Indication: this flag

shall be set to 1 on S11/S4 by the MME/SGSN
during a TAU/RAU or a Service Request
procedure for E-UTRAN/UTRAN, or at receipt of
an uplink LLC PDU for user data or any valid LLC
frame serving as a paging response for GERAN, if
the PDN connection is delay tolerant and if there is
pending network initiated PDN connection
signalling. The SGW shall include this IE on
S5/S8 if it receives the flag from the MME/SGSN.
ETSI
Sender F-TEID for C The new MME/SGSN shall include this IE on the S11 and F-TEID 0
Control Plane S4 interfaces for a TAU/RAU/ Handover with an
MME/SGSN change and without any SGW change. See
NOTE 10.
If the SGW receives this IE and if it finds that its value is
the same as the earlier received value of this IE for this
UE, it should interpret this to mean that the MME/SGSN
has not changed.
The new SGW shall include this IE on the S5 and S8

interfaces for a TAU/RAU/Handover with a SGW change.
See NOTE 10.
If the PGW receives this IE and if it finds that its value is
PDN connection, it should interpret this to mean that the
SGW has not changed.
Aggregate Maximum C The APN-AMBR shall be sent for TAU/RAU/Handover from AMBR 0
Bit Rate (APN-AMBR) the Gn/Gp SGSN to the S4 SGSN/MME procedures.
Delay Downlink C This IE shall be sent on the S11 interface for a UE Delay Value 0
Packet Notification triggered Service Request.
Request CO This IE shall be sent on the S4 interface for a UE triggered
Service Request.
Bearer Contexts to be C This IE shall be sent on the S4/S11 interface and S5/S8 Bearer Context 0
modified interface, except
- on the S5/S8 interface for a UE triggered Service
Request.
- on the S5/S8 interface for a TAU/RAU/HO without
SGW change procedure. See NOTE 10. .
- on the S5/S8 interface when requesting the PGW
to pause or unpause charging for the PDN
connection.
- on the S5/S8 interface for any other procedure
without SGW change which requires to send a
Modify Bearer Request to the PGW, e.g. HSS-
based P-CSCF restoration for 3GPP access,
reporting of UE presence in a Presence Reporting
Area, implicit resume of suspended bearers.
(see NOTE 6).
When Handover Indication flag is set to 1 (i.e., for a
to E-UTRAN or a Handover from Trusted or Untrusted
Non-3GPP IP Access to UTRAN/GERAN procedures), the
PGW shall ignore this IE. See NOTE 1.
Several IEs with the same type and instance value may be
included as necessary to represent a list of Bearers to be
modified.
During a TAU/RAU/Handover procedure with an SGW
change, the SGW includes all bearers it received from the
MME/SGSN (Bearer Contexts to be created, or Bearer
Contexts to be modified and also Bearer Contexts to be
removed) into the list of 'Bearer Contexts to be modified'
IEs, which are then sent on the S5/S8 interface to the
PGW (see NOTE 2, see NOTE 10).
During an E-UTRAN Initiated E-RAB modification

procedure the MME shall send a Modify Bearer Request,
including all the bearers (those modified and those not
modified), per PDN connection for which at least one
bearer has changed. See NOTE 11.
Bearer Contexts to be C This IE shall be included on the S4 and S11 interfaces for Bearer Context 1
removed the TAU/RAU/Handover and Service Request procedures
where any of the bearers existing before the
TAU/RAU/Handover procedure and Service Request
procedures will be deactivated as consequence of the
TAU/RAU/Handover procedure and Service Request
procedures. See NOTE 3 and NOTE 6.
instance value, shall be included.
ETSI
See NOTE 11.

Recovery C This IE shall be included if contacting the peer for the first Recovery 0
time
UE Time Zone CO This IE shall be included by the MME/SGSN on the S11/S4 UE Time Zone 0
interfaces if the UE Time Zone has changed in the case of
TAU/RAU/Handover or UE initiated Service Request
procedure. See NOTE 5.
during a TAU/RAU/Handover with MME/SGSN change if
the source MME/SGSN has set the TZCR bit in the
Change to Report Flags IE in the Forward Relocation
Request or Context Response message.
C If SGW receives this IE, SGW shall forward it to PGW
MME-FQ-CSID C This IE shall be included by MME on S11 and shall be FQ-CSID 0
forwarded by SGW on S5/S8 according to the
requirements in 3GPP TS 23.007 [17].
SGW-FQ-CSID C This IE shall be included by SGW on S5/S8 according to FQ-CSID 1
User CSG CO The MME/SGSN shall include this IE for Handover UCI 0
Information (UCI) procedures and UE-initiated Service Request procedure if
the PGW/PCRF has requested CSG Info reporting and the
MME/SGSN support the CSG information reporting and
the User CSG information has changed (i.e. the UE is
accessed via a new CSG cell or hybrid cell or leaves a
CSG or hybrid cell).
In TAU/RAU procedure without SGW change, this IE shall
also be sent if the PGW/PCRF has requested CSG info
reporting and MME/SGSN supports CSG info reporting
and the User CSG information has changed (i.e. the UE is
accessed via a new CSG cell or hybrid cell or leaves a
CSG or hybrid cell) when UE requested to activate E-RAB
for all the active EPS bearers in TAU procedure or to keep
the Iu connection after the completion of the RAU
procedure. See NOTE 5. See NOTE 10. See NOTE 16.
User CSG Information from MME/SGSN.
See NOTE 15.
UE Local IP Address CO If the UE local IP Address has changed, the ePDG shall IP Address 1
include this IE on S2b interface based on local policy for
Fixed Broadband access network interworking (see 3GPP
TS 23.139 [51]).
UE UDP Port CO The ePDG shall include this IE on S2b interface if NAT is Port Number 1
detected and UE Local IP Address is present for Fixed
Broadband access network interworking (see 3GPP TS
23.139 [51]).
MME/S4-SGSN LDN O This IE is optionally sent by the MME to the SGW on the Local 0
S11 interface and by the SGSN to the SGW on the S4 Distinguished
interface (see 3GPP TS 32.423 [44]), when communicating Name (LDN)
the LDN to the peer node for the first time.
SGW LDN O This IE is optionally sent by the SGW to the PGW on the Local 1
S5/S8 interfaces (see 3GPP TS 32.423 [44]), for inter- Distinguished
SGW mobity, when communicating the LDN to the peer Name (LDN)
node for the first time.
H(e)NB Local IP CO The MME/SGSN shall include this IE on S11/S4 interface if IP Address 0
Address the PGW/PCRF has requested H(e)NB information
reporting and the MME/SGSN has received this
information from H(e)NB in UE associated S1/Iu signalling
(see 3GPP TS 23.139 [51]).
The SGW shall forward this IE on S5/S8 interface if it is

received from the MME/SGSN and
- the Modify Bearer Request message needs to be
sent to the PGW as specified in the 3GPP TS
23.401 [3]; or
- the Propagate BBAI information change flag is
ETSI
(NOTE 7)
H(e)NB UDP Port CO The MME/SGSN shall include this IE on S11/S4 interface if Port Number 0
reporting and the MME/SGSN has received this
information from H(e)NB in UE associated S1/Iu signalling
(see 3GPP TS 23.139 [51]).
The SGW shall forward this IE on S5/S8 interface if it is

received from the MME/SGSN and
- the Modify Bearer Request message needs to be
sent to the PGW as specified in the 3GPP TS
23.401 [3]; or
- the Propagate BBAI information change flag is
(NOTE 7)
CO If the PGW triggered SGW restoration procedure is
supported, the MME/S4-SGSN shall include this IE on
S11/S4 interface and the SGW shall forward this IE on S5
interface in the existing signalling as specified in 3GPP TS
23.007 [17].
If the overload control feature is supported by the MME/S4-

MME/S4-SGSN
belongs(see subclause 12.3.11), the MME/S4-SGSN shall IP Address 2
Identifier
include this IE on the S11/S4 interface during mobility
procedures with MME/S4-SGSN change.
CO If the overload control feature is supported by the SGW
and if the currently serving MME/S4-SGSN has provided
this IE (in this message or in earlier message), the SGW
shall include this IE on the S5/S8 interface and shall set it
to the last received value of the serving MME/S4-SGSN
identity.
CO In shared networks, the SGSN shall include this IE on the
S4 interface for the RAU procedure, if the information is
CN Operator available, and if the Serving Network IE is present in the CN Operator
0
Selection Entity message or if the CN Operator Selection Entity has Selection Entity
changed, to indicate whether the Serving Network has
been selected by the UE or by the network.
Presence Reporting CO The MME/SGSN shall include this IE: Presence 0
Area Information - if the PGW/PCRF has just requested to start Reporting Area
reporting changes of UE presence in a Presence Information
Reporting Area and the MME/SGSN supports such
reporting. The MME/SGSN shall then indicate
whether the UE is inside or outside the Presence
Reporting Area.
The MME/SGSN shall also include this IE in the following

procedures, if the PGW/PCRF requested to report changes
of UE presence in a Presence Reporting Area and the
MME/SGSN supports such reporting:
- TAU/RAU/Handover procedures without SGW

change and with MME/SGSN change. The
MME/SGSN shall then indicate whether the UE is
inside or outside the Presence Reporting Area.
- TAU/RAU/Handover/Cell Update procedures

without MME/SGSN change and UE-initiated
Service Request procedure if the UE enters or
leaves the Presence Reporting Area. See NOTE 5,
NOTE 10.
- UE initiated Service Request, if ISR is active;
CO When ISR is not active, the SGW shall include this IE on

S5/S8 if it receives the Presence Reporting Area
Information from MME/SGSN.
ETSI
When ISR is active, the SGW shall include this IE on

S5/S8 if it receives the Presence Reporting Area
Information from MME/S4-SGSN and
- the RAT Type has changed since last reported; or
- the CPRAI flag has been set to 1.

Overload Control
Overload Control 0
Information
interface.
O During an overload condition, the ePDG may include this
IE over the S2b interface if the overload control feature is
supported by the ePDG and is activated for the PLMN to
ePDG's Overload Overload Control
When present, the ePDG shall provide only one instance
NOTE1: This requirement is introduced for backwards compatibility reasons. If Bearer Contexts to be modified
IE(s) is received in the Modify Bearer Request message, the PGW shall include corresponding
Bearer Contexts modified IE(s) in the Modify Bearer Response message.
NOTE2: According to the description in 3GPP TS 23.401 [3] e.g. subclause 5.3.3.1 "Tracking Area Update
procedure with Serving GW change" and 3GPP TS 23.060 [35], during a TAU/RAU/Handover
procedure with an SGW change, if the SGW receives 'Bearer Context to be removed' IEs, the SGW
shall allocate the S5/8-U SGW F-TEID for those bearers and include also these bearers in the
'Bearer contexts to be modified' IE, which is then sent within this message on the S5/S8 interface to
the PGW.
NOTE3: The 'Bearer Contexts to be removed' IE signals to the SGW that these bearers will be removed by
the MME/SGSN later on by separate procedures (e.g. MME/S4-SGSN initiated Dedicated Bearer
Deactivation procedure). Therefore, the SGW will not delete these bearers during the ongoing
TAU/RAU/Handover procedure (without an SGW change), a Handover procedure (with an SGW
change except for an X2-Handover) and a Service Request procedure.
NOTE 5: In TAU/RAU procedure, if the UE requested to activate E-RAB for all the active EPS bearers in TAU
procedure or to keep the Iu connection after the completion of the RAU procedure, the User Location
Info/User CSG Information/UE Time Zone/Presence Reporting Area Information shall not be sent in
S1-U GTP-U tunnel setup procedure during the TAU procedure when the "active flag" is set (see
3GPP TS 24.301 [23] and 3GPP TS 23.401 [3]) or in the Service Request procedure after the
completion of the RAU procedure.
NOTE 6: 3GPP TS 23.401 [3] specifies that the target MME/SGSN shall send the Modify Bearer Request
message to the SGW in the S1 based handover/ Inter RAT handover for an unaccepted PDN
Connection when at least one PDN Connection of the UE was accepted by the RAN. In this case, the
target MME shall indicate the reserved IP address to the SGW in the S1 eNodeB F-TEID and the
target SGSN shall indicate the reserved IP address to the SGW in the S12 RNC F-TEID for all the
non GBR bearers of the unaccepted PDN Connection in the Bearer Contexts to be modified IE. An
implementation may provide the mentioned reserved IP address e.g. from one of the reserved IP
address ranges (see RFC5735 or http://www.iana.net/assignments/ipv4-address-space/ipv4-
address-space.xml), or the IP address may be provisioned by a configuration. The target
MME/SGSN shall indicate all the GBR bearers of the unaccepted PDN connection in the Bearer
ETSI
Contexts to be removed IE.

NOTE 7: This IE is sent on S11/S4 in the specified conditions regardless of whether the H(e)NB local IP
address and UDP port number information has changed or not to enable the SGW to propagate this
IE in Modify Bearer Request over S5/S8 when required for reasons other than reporting a change in
the H(e)NB local IP address and UDP port number information.
NOTE 8: H(e)NB local IP address and UDP port number information changes when the UE moves from an
(e)NB to an H(e)NB, or from one H(e)NB to another H(e)NB with a change in the fixed network
backhaul, or from one H(e)NB to a (e)NB.
The SGW shall send a Modify Bearer Request on S5/S8 if any of the following condition is met:
a) the Propagate BBAI Information Change flag is received from the MME/SGSN;
b) ISR is active and the RAT type has changed.
NOTE 9: When ISR is active, the CLII and CPRAI flags allow the SGW to avoid sending Modify Bearer
Request message over S5/S8 interface during UE-initiated Service Request procedure, when the ULI
IE and/or the Presence Reporting Area Information IE is included over S11/S4 Modify Bearer
Request message but the location information and/or the Presence Reporting Area information and
the RAT Type has not changed since last reported by the SGW.
NOTE 10: The RAU/TAU/Handover procedure which requires an SGW selection for the first time, e.g. a Gn/Gp
SGSN to an S4 SGSN/MME RAU/TAU/Handover procedure, shall be handled in a similar manner to
the RAU/TAU/Handover with an SGW change procedure.
NOTE 11: The Bearer Context to be modified IE and Bearer Context to be removed IE, together, shall contain
all the bearers belonging to the given PDN connection with each bearer appearing in only one of
these IEs.
NOTE 12: The conditions of presence of the IEs in the Modify Bearer Request for the MME and S4-SGSN
NOTE 13: If this flag is set in the message, the PGW shall not interpret the absence of other IEs (e.g. MME-FQ-
CSID, H(e)NB Local IP Address) as bearing any significance. The message may contain either the
PDN Pause On Indication or the PDN Pause Off Indication, not both.
NOTE 14: During the TAU/RAU/Handover from Gn/Gp SGSN, the target MME/S4-SGSN can not derive the
level of support for User Location Change Reporting and/or CSG Information Change Reporting at
the source Gn/Gp SGSN.
NOTE 16: If the UE initiates a TAU or RAU procedure back to the old MME/old S4 SGSN before completing the
ongoing TAU or RAU procedure and the UE is not accessed via a CSG cell or hybrid cell, the old
MME/old S4-SGSN shall treat this case as the UE leaves a CSG or hybrid cell.
NOTE 17: The MME/S4-SGSN may be configured to defer the reporting of ULI change until an E-RAB, RAB or
user plane is established. In that case, the MME/S4-SGSN shall not send a Modify Bearer Request,
unless this is required for other reasons, during TAU/RAU without MME/SGSN change or Service
Request (for UTRAN) procedures not requesting to activate data radio bearer(s). For GERAN, the
SGSN shall defer the reporting of ULI changes, if so configured in the SGSN, until receipt of an
uplink LLC PDU for user data or any valid LLC frame serving as a paging response.
The MME/S4-SGSN shall report ULI changes as soon as detected if it is not configured to defer the
reporting of ULI changes until an E-RAB, RAB or user plane is established, or if an E-RAB, RAB or
user plane is established.
ETSI
Table 7.2.7-2: Bearer Context to be modified within Modify Bearer Request

elements
EPS Bearer ID M See NOTE 1, NOTE 2.. EBI 0
S1 eNodeB F-TEID C This IE shall be sent on the S11 interface if the S1-U is F-TEID 0
being used:
- for an E-UTRAN initial attach
- for a Handover from Trusted or Untrusted Non-

3GPP IP Access to E-UTRAN
- for an UE triggered Service Request
- in all S1-U GTP-U tunnel setup procedure during a

TAU procedure (see 3GPP TS 24.301 [23])
/handover cases;
- in all procedures where the UE is already in ECM-

CONNECTED state, e.g. E-UTRAN Initiated E-
RAB modification procedure, possibly HSS-based
P-CSCF restoration for 3GPP access. See NOTE
4.
If an MME is aware that the eNodeB supports both IP

address types, the MME shall send both IP addresses
within an F-TEID IE. If only one IP address is included,
then the SGW shall assume that the eNodeB does not
support the other IP address type.
See NOTE 2, NOTE 5, NOTE 6.
S5/8-U SGW F-TEID C This IE shall be sent on the S5/S8 interfaces for a F-TEID 1
Handover or a TAU/RAU with a SGW change.
S12 RNC F-TEID C If available, this IE shall be included if the message is sent F-TEID 2
on the S4 interface if S12 interface is being used. If an S4-
SGSN is aware that the RNC supports both IP address
types, the S4-SGSN shall send both IP addresses within
an F-TEID IE. If only one IP address is included, then the
SGW shall assume that the RNC does not support the
other IP address type.
See NOTE 2, NOTE 6.
S4-U SGSN F-TEID C If available, this IE shall be included if the message is sent F-TEID 3
on the S4 interface, if S4-U is being used. If an S4-SGSN
supports both IP address types, the S4-SGSN shall send
both IP addresses within an F-TEID IE. If only one IP
address is included, then the SGW shall assume that the
S4-SGSN does not support the other IP address type. See
, NOTE 6
NOTE 1: If only EPS Bearer ID IE is included in the Bearer Context to be modified IE during the TAU/RAU
without SGW change procedure, the SGW shall remove the stored SGSN/RNC/eNodeB userplane
F-TEID locally.
NOTE 2: When Direct Tunnel is used in 3G, e.g. during a Service Request procedure if the UE requests to
establish a partial set of radio access bearers and if the SGSN accepts it, or during an SRNS
relocation procedure with some bearer contexts being preserved, the SGSN shall provide EBI(s)
without S12 RNC F-TEID(s) for these bearer context(s) without corresponding radio access bearer(s)
being established. The SGW shall be able to handle these bearer context(s). However, in earlier
releases this behaviour may not be supported by the SGW and hence for such SGW, the SGSN shall
provide EBI together with S12 RNC F-TEID for each of the bearer context(s) in the Bearer Context to
be modified IE.
NOTE 3: It is not possible to establish or release a partial set of radio access bearers in E-UTRAN. The MME
shall provide in the Bearer Contexts to be modified IE, for a UE entering or being in CONNECTED
state, the EBI together with the S1 eNodeB F-TEID for all the bearers of the PDN connection affected
by the Modify Bearer Request other than those possibly indicated in the Bearer Context to be
removed IE.
NOTE 4: When the PCO-based extension of the HSS based P-CSCF restoration for 3GPP access is
supported as specified in subclause 5.4.3 of 3GPP TS 23.380 [61], the MME shall store the S1
eNodeB F-TEID(s) of the IMS PDN connection for UEs with an IMS PDN connection in ECM-
ETSI
CONNECTED state, so that the MME can include all the S1 eNodeB F-TEID(s) of the IMS PDN
connection for such a UE in ECM-CONNECTED state in the Modify Bearer Request message.
NOTE 5: When the PCO-based extension of the HSS based P-CSCF restoration for 3GPP access is
supported as specified in subclause 5.4.3 of 3GPP TS 23.380 [61], the S4-SGSN shall store the S12
RNC F-TEID(s) (if Direct Tunneling is used) for all the bearers of the IMS PDN connection with
corresponding radio access bearers established, for UEs with an IMS PDN connection in PMM-
CONNECTED state, so that the S4-SGSN can include all the S4-U SGSN F-TEID(s) (if Direct
Tunneling is not used) or S12 RNC F-TEID(s) (if Direct Tunneling is used) for all the bearers of the
IMS PDN connection with corresponding radio access bearers established, for such a UE in PMM-
CONNECTED state in the Modify Bearer Request message.
NOTE 6: During a TAU/RAU with SGW change procedure and data forwarding of DL data buffered in the old
SGW (see subclause 5.3.3.1A of 3GPP TS 23.401 [3]), the old MME/SGSN shall provide the old
SGW with the Forwarding F-TEID received in the Context Acknowledge message (or in the SGSN
Context Acknowledge message when a Gn/Gp SGSN is involved) and encode it as either an eNB F-
TEID (for an old MME), or an S12 RNC F-TEID or S4-U SGSN F-TEID (for an old SGSN), regardless
the interface type set in the F-TEID received from the new MME/SGSN. This is to make the downlink
data forwarding appear as a regular downlink data transmission for the old SGW, i.e. like a Service
Request procedure.
Table 7.2.7-3: Bearer Context to be removed within Modify Bearer Request

elements
Table 7.2.7-4: Overload Control Information within Modify Bearer Request

elements
Metric parameter.
parameter.
7.2.8 Modify Bearer Response

The Modify Bearer Response message shall be sent on the S11/S4 interfaces by the SGW to the MME/S4-SGSN, on the
S5/S8 interfaces by the PGW to the SGW and on the S2b interface by the PGW to the ePDG as part of the procedures
listed for the Modify Bearer Request (see subclause 7.2.7).
If handling of default bearer fails, then Cause at the message level shall be a failure cause.
ETSI
- "Service not supported".
ETSI
Table 7.2.8-1: Information Elements in a Modify Bearer Response

elements
Cause M Cause 0
MSISDN C This IE shall be included on S5/S8 interfaces by the PGW MSISDN 0
if it is stored in its UE context and if this message is
triggered due to TAU/RAU/HO with SGW relocation.
Linked EPS Bearer ID C This IE shall be sent on S5/S8 when the UE moves from a EBI 0
Gn/Gp SGSN to the S4 SGSN or MME to identify the
default bearer the PGW selects for the PDN Connection.
This IE shall also be sent by SGW on S11, S4 during
Gn/Gp SGSN to S4-SGSN/MME HO procedures to identify
the default bearer the PGW selects for the PDN
Connection.
APN Restriction C This IE denotes the restriction on the combination of types APN Restriction 0
Context. This IE shall be included over S5/S8 interfaces,
and shall be forwarded over S11/S4 interfaces during
Gn/Gp SGSN to MME/S4-SGSN handover procedures.
This IE shall also be included on S5/S8 interfaces during
the Gn/Gp SGSN to S4 SGSN/MME RAU/TAU
procedures.
The target MME or SGSN determines the Maximum APN
Restriction using the APN Restriction.
Protocol C If SGW receives this IE from PGW on GTP or PMIP based PCO 0
Configuration Options S5/S8, the SGW shall forward PCO to MME/S4-SGSN
(PCO) during Inter RAT handover from the UTRAN or from the
GERAN to the E-UTRAN. See NOTE 2.
Bearer Contexts C EPS bearers corresponding to Bearer Contexts to be Bearer Context 0
modified modified that were sent in Modify Bearer Request
message. Several IEs with the same type and instance
value may be included as necessary to represent a list of
the Bearers which are modified.
marked for removal removed sent in the Modify Bearer Request message.
Shall be included if request message contained Bearer
Contexts to be removed.
Change Reporting C This IE shall be included with the appropriate Action field If Change Reporting 0
Action the location Change Reporting mechanism is to be started Action
or stopped for this subscriber in the SGSN/MME.
CSG Information CO This IE shall be included with the appropriate Action field if CSG Information 0
Reporting Action the location CSG Info change reporting mechanism is to be Reporting Action
started or stopped for this subscriber in the SGSN/MME.
Charging Gateway C When Charging Gateway Function (CGF) Address is FQDN 0
Name configured, the PGW shall include this IE on the S5
interface during SGW relocation and when the UE moves
from Gn/Gp SGSN to S4-SGSN/MME. See NOTE 1.
Charging Gateway C When Charging Gateway Function (CGF) Address is IP Address 0
Address configured, the PGW shall include this IE on the S5
interface during SGW relocation and when the UE moves
from Gn/Gp SGSN to S4-SGSN/MME. See NOTE 1.
PGW-FQ-CSID C This IE shall be included by PGW on S5/S8and shall be FQ-CSID 0
forwarded by SGW on S11 according to the requirements
in 3GPP TS 23.007 [17].
SGW-FQ-CSID C This IE shall be included by SGW on S11 according to the FQ-CSID 1
time.
SGW LDN O This IE is optionally sent by the SGW to the MME/SGSN Local 0
on the S11/S4 interfaces (see 3GPP TS 32.423 [44]), Distinguished
when communicating the LDN to the peer node for the first Name (LDN)
ETSI
time.
PGW LDN O This IE is optionally sent by the PGW to the SGW on the Local 1
S5/S8 interfaces (see 3GPP TS 32.423 [44]), when Distinguished
communicating the LDN to the peer node for the first time. Name
(LDN)Name
is set to 1.
- Static IPv4 Address Flag: This flag shall be set to 1
on the S5/S8 interface in the TAU/RAU/Handover
with SGW change procedure if the PDP/PDN IPv4
address is static as specified in 3GPP TS 32.251
[8]. See NOTE 3.
- Static IPv6 Address Flag: This flag shall be set to 1

on the S5/S8 interface in the TAU/RAU/Handover
with SGW change procedure if the PDP/PDN IPv6
address is static as specified in 3GPP TS 32.251
[8]. See NOTE 3.

set to 1 on the S5/S8 interface during the
procedures if the PGW supports the PGW Pause
of Charging procedure.
- PDN Pause Enable Indication: this flag shall be set

to 1 on the S5/S8 interface during the
procedures if the PGW enables the new SGW to
use the PGW Pause of Charging procedure for this
PDN connection.


- Delay Tolerant Connection Indication: the flag shall

be set to 1 on the S5/S8 interface during a SGW
relocation procedure and when the UE moves from
Gn/Gp SGSN to S4-SGSN/MME if the PDN
connection is "Delay Tolerant" (see subclause
8.12). See NOTE 9.

Presence Reporting
Area Action
MME/SGSN.
ETSI

clause 12.2.6).

See NOTE 5, NOTE 7.

Control Information on the S5/S8 or S2b interface, if the overload control Information
SGSN for 3GPP access based network, ePDG for non-
3GPP access based network, belongs (see clause
12.3.11).

APN(s).
See NOTE 6, NOTE 8.
clause 12.3.11).

NOTE 1: Both Charging Gateway Name and Charging Gateway Address shall not be included at the same
time. When both are available, the operator configures a preferred value.
NOTE 2: If MME receives the IE, but no NAS message is sent, MME discards the IE.
NOTE 3: Static IPv4/IPv6 Address Flag is used by SGW to provide dynamic IPv4/v6 address flag information
as specified in 3GPP TS 32.251 [8].
NOTE 4: The conditions of presence of the IEs in the Modify Bearer Response for the MME and S4-SGSN
ETSI
NOTE 9: The SGW may use the DTCI during a Network Triggered Service Restoration procedure as specified
in the subclause 25.2.1 of 3GPP TS 23.007 [17].
ETSI
Table 7.2.8-2: Bearer Context modified within Modify Bearer Response

elements
and if not, gives information on the reason.
S1-U SGW F-TEID C This IE shall be used on the S11 interface, if the S1 F-TEID 0
interface is used. If the 'Change F-TEID support Indication'
flag was set to 1 in the Modify Bearer Request and the
SGW needs to change the F-TEID, the SGW shall include
the new GTP-U F-TEID value. Otherwise, the SGW shall
return the currently allocated GTP-U F-TEID value. See
NOTE 1
S12 SGW F-TEID C This IE shall be included on the S4 interface if the S12 F-TEID 1
interface is being used. If the 'Change F-TEID support
Indication' flag was set to 1 in the Modify Bearer Request
and the SGW needs to change the F-TEID, the SGW shall
include the new GTP-U F-TEID value. Otherwise, the SGW
shall return the currently allocated GTP-U F-TEID value.
See NOTE 1
S4-U SGW F-TEID C This IE shall be present if used on the S4 interface if the F-TEID 2
S4-U interface is being used. If the 'Change F-TEID
support Indication' flag was set to 1 in the Modify Bearer
Request and the SGW needs to change the F-TEID, the
SGW shall include the new GTP-U F-TEID value.
Otherwise, the SGW shall return the currently allocated
GTP-U F-TEID value. See NOTE 1
C This IE shall be present on the S5/S8 interface if this
message is triggered due to one of the following
procedures:
- TAU/RAU/HO with SGW relocation
- TAU/RAU/HO from Gn/Gp SGSN to MME/S4-

SGSN
Charging ID Charging ID 0
O If S5/S8 interface is GTP, this IE may be sent on the S4
interface, in order to support CAMEL charging at the
SGSN, for the following procedures:
- inter-SGSN RAU/Handover/SRNS Relocation
without SGW change.
- inter-SGSN Handover/SRNS Relocation with SGW
change.
Bearer Flags CO Applicable flags are: Bearer Flags 0
- PPC (Prohibit Payload Compression): This flag
shall be sent on the S5/S8 and the S4 interfaces at
S4-SGSN relocation.
interfaces.The SGW shall not change its F-TEID for a given interface during the Handover, Service
Request, E-UTRAN Initial Attach, Handover from Trusted or Untrusted Non-3GPP IP Access to E-
UTRAN, UE Requested PDN connectivity, PDP Context Activation, Handover from Trusted or
Untrusted Non-3GPP IP Access to UTRAN/GERAN and E-UTRAN Initiated E-RAB modification
procedures.
During Handover and Service Request the target eNodeB/RNC/SGSN may use a different IP type
than the one used by the source eNodeB/RNC/SGSN. In order to support such a scenario, the SGW
F-TEID should contain both an IPv4 address and an IPv6 address (see also subclause 8.22 "F-
TEID").
ETSI
Table 7.2.8-3: Bearer Context marked for removal within Modify Bearer Response

elements
Table 7.2.8-4: Load Control Information within Modify Bearer Response

elements
parameter.
See NOTE 1.
Table 7.2.8-5: Overload Control Information within Modify Bearer Response

elements
parameter.
ETSI
7.2.9 Delete Session Request and Delete Bearer Request
7.2.9.1 Delete Session Request

The direction of this message shall be from MME/S4-SGSN to SGW, from SGW to PGW and from TWAN/ePDG to
PGW (see Table 6.1-1).
A Delete Session Request message shall be sent on the S11 interface by the MME to the SGW and on the S5/S8
interface by the SGW to the PGW as part of the procedures:
- EUTRAN Initial Attach
- UE, HSS or MME Initiated Detach
- UE or MME Requested PDN Disconnection
It shall also be sent on the S4 interface by the SGSN to the SGW, and on the S5/S8 interface by the SGW to the PGW
as part of
- MS, HLR or SGSN initiated detach procedure
- Combined GPRS/IMSI Attach
- MS and SGSN Initiated PDN connection Deactivation Procedure using S4
On the S11 interface by the MME to the SGW as part of the procedures:
- Tracking Area Update with SGW Change
- S1 Based Handover with SGW Change
- X2 Based Handover with SGW Relocation
- Inter RAT handover cancel with SGW change
- MME to 3G Gn/Gp SGSN combined hard handover and SRNS relocation procedure
- MME to SGSN Routing Area Update
- E-UTRAN to Gn/Gp SGSN Inter RAT handover
- S1 Based handover cancel with SGW change
- Optimised Active Handover: E-UTRAN Access to CDMA2000 HRPD Access
And on the S4 interface by the SGSN to the SGW as part of
- Enhanced Serving RNS Relocation with SGW relocation using S4
- Routing Area Update with SGW change
- SGSN to MME Tracking Area Update with SGW change
- SRNS Relocation Cancel Procedure Using S4
- Inter RAT with SGW change handover cancel
- Serving RNS relocation with SGW change
ETSI
- S4 SGSN to Gn/Gp SGSN Routeing Area Update
- S4 SGSN to Gn/Gp SGSN Serving RNS Relocation Procedures
- S4 SGSN to Gn/Gp SGSN PS handover Procedures
The message shall also be sent on the S2b interface by the ePDG to the PGW as part of procedures:
- UE/ePDG Initiated Detach with GTP on S2b
- UE Requested PDN Disconnection with GTP on S2b
- HSS/AAA Initiated Detach with GTP on S2b
The message shall also be sent on the S2a interface by the TWAN to the PGW as part of procedures:
- UE/TWAN Initiated Detach and UE/TWAN Requested PDN Disconnection in WLAN on GTP S2a
- HSS/AAA Initiated Detach in WLAN on GTP S2a
This message may also be sent on S5/S8 interface by the SGW to the PGW:
- If Downlink Data Notification Acknowledge message with Context not found cause value is received.
During the detach procedure, if ISR is active and SGW receives a Delete Session Request, the SGW shall deactivate the
ISR.
NOTE: The SGW can determine if it is a detach procedure based on e.g. it receives a Delete Session Request
message for the last PDN Connection.
When ISR is active, during the Detach procedure the SGW shall forward the Delete Session Request message to the
PGW on the S5/S8 interface after receiving both of the messages sent from the MME and the SGSN for the same PDN
Connection.
If there are any procedure collisions, the Delete Session Request shall have precedence over any other Tunnel
Management message.
During the handover procedure the Delete Session Request message shall not release the indirect data forwarding
tunnels.
Possible Cause values are:
- "ISR deactivation ".
- "Network Failure".
- "QoS parameter mismatch".
Table 7.2.9.1-1 specifies the presence of the IEs in the message.
ETSI
Table 7.2.9.1-1: Information Elements in a Delete Session Request

elements
Cause C If ISR is being de-activated, the Cause IE shall be included Cause 0
on the S4/S11 interface with the value "ISR deactivation",
which indicates that the SGW shall delete the bearer
resources by sending Delete Bearer Request to the
MME/SGSN on which ISR was activated with the same
Cause value "ISR deactivation". See NOTE 3
CO The MME/SGSN shall include this IE if the message is
sent due to a network failure as specified in subclause 15.7
of 3GPP TS 23.060 [35] and subclause 5.18 of 3GPP TS
23.401 [3]. It indicates to the PGW the reason of the
failure.

Cause from the MME/SGSN.
Linked EPS Bearer ID C This IE shall be included on the S4/S11, S5/S8 and EBI 0
(LBI) S2a/S2b interfaces to indicate the default bearer
associated with the PDN being disconnected unless in the
handover/TAU/RAU with SGW relocation procedures.
User Location C The MME/SGSN shall include this IE on the S4/S11 ULI 0
Information (ULI) interface for the Detach procedure. The MME shall include (NOTE 7)
ECGI, SGSN shall include CGI/SAI. The SGW shall
include this IE on S5/S8 if it receives the ULI from
MME/SGSN. See NOTE 4.
CO The MME/SGSN shall include this IE on the S4/S11
interface for the UE or MME Requested PDN
Disconnection procedure/MS and SGSN Initiated PDN
connection Deactivation Procedure using S4.
The MME shall include ECGI, SGSN shall include
CGI/SAI.
ULI from the MME/SGSN.
is set to 1.
Applicable flags:
- Operation Indication: This flag shall be set to 1
over S4/S11 interface, if the SGW needs to
forward the Delete Session Request message to
the PGW. This flag shall not be set if the ISR
associated GTP entity sends this message to the
SGW in the Detach procedure. This flag shall also
not be set to 1 in the SRNS Relocation Cancel
Using S4 (6.9.2.2.4a in 3GPP TS 23.060 [4]), Inter
RAT handover Cancel procedure with SGW
change TAU with Serving GW change, Gn/Gb
based RAU (see 5.5.2.5, 5.3.3.1, D.3.5 in 3GPP
TS 23.401 [3], respectively), S1 Based handover
Cancel procedure with SGW change.
This flag shall also not be set to 1 for, e.g., X2

based handover procedure with SGW change(see
subclause 5.5.1.1.3 in 3GPP TS 23.401 [3]), or S1
based handover procedure with SGW change (see
subclause 5.5.1.2.2 in 3GPP TS 23.401 [3]).
- Scope Indication: This flag shall be set to 1 on the

S4/S11 interface, if the request corresponds to
TAU/RAU/Handover with SGW change/SRNS
Relocation Cancel Using S4 with SGW change,
Inter RAT handover Cancel procedure with SGW
change, S1 Based handover Cancel procedure
with SGW change.
See NOTE 1.
ETSI
Protocol C If the UE includes the PCO IE, then the MME/SGSN shall PCO 0
Configuration Options copy the content of this IE transparently from the PCO IE
(PCO) included by the UE.
If SGW receives the PCO IE, SGW shall forward it to
PGW.
CO For the multi-connection mode, if the TWAN receives the
PCO from the UE, the TWAN shall forward the PCO IE to
the PGW.
Originating Node C This IE shall be included on the S4/S11 interface if the ISR Node Type 0
is active in MME/SGSN to denote the type of the node
originating the message.
The SGW shall release the corresponding Originating
Node related EPS Bearer contexts information in the PDN
Connection identified by the LBI.
Sender F-TEID for O This IE may be included on the S4/S11 interfaces. F-TEID 0
Control Plane If the Sender F-TEID for Control Plane is received by the
SGW, the SGW shall only accept the Delete Session
Request message when the Sender F-TEID for Control
Plane in this message is the same as the Sender F-TEID
for Control Plane that was last received in either the Create
Session Request message or the Modify Bearer Request
message on the given interface.
If the ISR is activated, two F-TEIDs exist: one for the MME
and the other for the SGSN. See NOTE 2.
O This IE may be included on the S5/S8 interfaces.
If the Sender F-TEID for Control Plane is received by the
PGW, the PGW shall only accept the Delete Session
Request message when the Sender F-TEID for Control
Plane in this message is the same as the Sender F-TEID
for Control Plane that was last received in either the Create
Session Request message or the Modify Bearer Request
message on the given interface. See NOTE 6.
CO The SGW shall include this IE on the S5/S8 interface if the
Delete Session Request is sent to clean up a hanging PDN
connection context in the PGW, i.e. as a result of receiving
a Create Session Request at the SGW colliding with an
existing PDN connection context (see subclause 7.2.1).
UE Time Zone CO This IE shall be included by the MME on the S11 interface UE Time Zone 0
or by the SGSN on the S4 interface, for Detach and PDN
Disconnection procedures, if the UE Time Zone has
changed.
SGW receives it from the MME/SGSN, and if the Operation
Indication bit received from the MME/SGSN is set to 1.
interface.
ULI Timestamp CO This IE shall be included on the S4/S11 interface if the ULI ULI Timestamp 0
IE is present. It indicates the time when the User Location
Information was acquired.
The SGW shall include this IE on S5/S8 if the SGW
receives it from the MME/SGSN. See NOTE 4.
RAN/NAS Release CO The MME shall include this IE on the S11 interface to RAN/NAS Cause 0
Cause indicate the NAS release cause to release the PDN
connection, if available and this information is permitted to
be sent to the PGW operator according to MME operator's
policy.

receives it from the MME and if the Operation Indication bit
received from the MME is set to 1.
CO The TWAN shall include this IE on the S2a interface to
indicate the TWAN release cause to release the PDN
connection, if this information is available and is permitted
to be sent to the PGW operator according to the TWAN
operator's policy. When present, the IE shall be encoded
as a Diameter or an ESM cause. See NOTE 8.
ETSI
CO The ePDG shall include this IE on the S2b interface to

indicate the release cause to release the PDN connection,
if this information is available and is permitted to be sent to
the PGW operator according to the ePDG operator's
policy. When present, the IE shall be encoded as a
Diameter or an IKEv2 cause.
TWAN Identifier CO This IE shall be included by the TWAN on the S2a if the TWAN Identifier 0
Timestamp TWAN Identifier IE is present. It shall indicate the time Timestamp
when the TWAN acquired the TWAN Identifier information.
Overload Control
Overload Control 0
Information
interface.
TWAN/ePDG's
Overload Control 2
Information
TWAN Identifier 1
1
is detected.
interfaces.
NOTE 1: For the Indication Flags, the combination (Operation Indication, Scope Indication) = 1,1 shall be
considered an error if received.
NOTE 2: Following an inter RAT TAU/RAU failure, the target MME/SGSN may mistakenly initiate the implicit
detach procedure while the UE is managed by the other MME/SGSN. In this case, the SGW will
reject the Delete Session Request message with the cause "Invalid peer".
NOTE 3: If the UE has multiple PDN connections and only one of these is being deactivated, the MME/S4-
SGSN shall not send the Cause IE with the value "ISR deactivation".
NOTE 4: If ISR is active, after receiving both the Delete Session Request messages from the MME and the
SGSN, the SGW shall include the most recent ULI timestamp and the related User Location
Information in the Delete Session Request message on S5/S8 interface.
NOTE 5: The conditions of presence of the IEs in the Delete Session Request for the MME and S4-SGSN
NOTE 6: In some scenarios, e.g. during an S11/S4 path failure, the old SGW may send a Delete Session
Request towards the PGW for a PDN connection which has already been relocated to a new SGW.
In this case, the PGW shall reject the Delete Session Request message with the cause "Invalid
peer".
ETSI
NOTE 8: This IE corresponds to the TWAN Release Cause IE specified in 3GPP TS 23.402 [45].
Table 7.2.9.1-2: Overload Control Information within Delete Session Request

elements
Metric parameter.
parameter.
7.2.9.2 Delete Bearer Request

The direction of this message shall be from PGW to SGW, from SGW to MME/S4-SGSN and from PGW to
A Delete Bearer Request message shall be sent on the S5/S8 and S4/S11 interfaces as part of the following procedures:
- PGW or MME initiated bearer deactivation procedures,
- UE requested Bearer Resource Modification,
- MS and SGSN Initiated Bearer Deactivation procedure using S4 or
- PGW initiated bearer deactivation procedure using S4.
In the above cases, this Request is sent by the PGW to the SGW and shall be forwarded to the MME or S4-SGSN.
The message shall also be sent on the S4/S11 interface by the SGW to the SGSN/MME to delete the bearer resources on
the other ISR associated CN node if the ISRAI flag is not set in the Modify Bearer Request/Modify Access Bearers
Request message.
The message shall also be sent on the S4/S11 interface by the SGW to the SGSN/MME to delete the bearer resources on
the other ISR associated CN node in the TAU/RAU/Handover procedures if the ISR related Cause IE is included in the
Delete Session Request message.
The message shall also be sent on the S2b interface by the PGW to the ePDG as part of PGW Initiated Bearer Resource
Allocation Deactivation procedure with GTP on S2b.
The message shall also be sent on the S2a interface by the PGW to the TWAN as part of the PGW Initiated Bearer
Resource Allocation Deactivation in WLAN on GTP on S2a procedure.
The message may also be sent on the S11/S4 interface by the SGW to the MME/S4 SGSN when the SGW receives the
Error Indication from PGW for the default bearer or the ICMP message from a PGW that indicates the UE specific error
indication as specified in 3GPP TS 23.007 [17].
ETSI
on the S11/S4 interface by the SGW to the MME/S4-SGSN as part of the Network-initiated IP flow mobility procedure,
as specified by 3GPP TS 23.161 [71].
- "RAT changed from 3GPP to Non-3GPP",
- "ISR deactivation",
- "Access changed from Non-3GPP to 3GPP",
- "Reactivation requested",
- "PDN reconnection to this APN disallowed",
- "PDN connection inactivity timer expires".
Table 7.2.9.2-1 specifies the presence of IEs in this message.
ETSI
Table 7.2.9.2-1: Information Elements in a Delete Bearer Request

elements
Linked EPS Bearer ID C If the request corresponds to the bearer deactivation EBI 0
(LBI) procedure in case all bearers belonging to a PDN
connection shall be released, then this IE shall be included
on the S5/S8, S4/S11 and S2a/S2b interfaces to indicate
the default bearer associated with the PDN being
disconnected.
This IE shall be included only when the EPS Bearer ID is
not present in the message.
CO During a TAU/RAU/HO if the Cause value is set to "ISR
deactivation" in the Delete Session Request message, or
when this message is used to delete the bearer resources
on the other ISR associated CN node if the ISRAI flag is
not set in the Modify Bearer Request/Modify Access
Bearers Request message, an SGW shall send all LBIs for
a given UE with the message on S4/S11 interface. All LBI
IEs shall have the same type and instance value to
represent a list of IEs (see NOTE 1 and NOTE 2).
EPS Bearer IDs C This IE shall be included on S5/S8, S4/S11 and S2a/S2b EBI 1
interfaces for deleting bearers different from the default
one, i.e. for dedicated bearers. In this case at least one
dedicated bearer shall be included.
This IE shall be included only when the Linked EPS Bearer
ID is not present in the message.
Several IEs with this type and instance values shall be
Failed Bearer O This IE may be included on the S5/S8 and S11 interfaces if Bearer Context 0
Contexts the request corresponds to MME initiated bearer
deactivation procedure. This IE shall contain the list of
failed bearers if partial Bearer Contexts included in the
Delete Bearer Command message could not be deleted.
Procedure C If the request corresponds to UE requested bearer PTI 0
Transaction Id (PTI) resource modification procedure for an E-UTRAN, this IE
shall be included on the S5/S8 and S11 interfaces.
Protocol C PGW shall include Protocol Configuration Options (PCO) PCO 0
Configuration Options IE on the S5/S8 interface, if available.
(PCO) If SGW receives this IE, SGW shall forward it to
SGSN/MME on the S4/S11 interface.
CO For trusted WLAN access, if the default bearer of the PDN
connection is being deleted and if the multi-connection
mode is used, the PGW may include this IE over the S2a
interface to send PCO to the UE.
PGW-FQ-CSID C This IE shall be included by the PGW on the S5/S8 and FQ-CSID 0
S2a/S2b interfaces, and when received from S5/S8 be
SGW-FQ-CSID C This IE shall be included by the SGW on the S11 interface FQ-CSID 1
Cause C This IE shall be sent on S5/S8 and S11/S4 interfaces if the Cause 0
message is caused by a handover with or without
optimization from 3GPP to non-3GPP (see subclause 9.3.2
in 3GPP TS 23.402 [45] and subclause 5.4.4.1 in 3GPP TS
23.401 [3], respectively). In this case the Cause value shall
be set to "RAT changed from 3GPP to Non-3GPP".
This IE shall also be sent on S11/S4 interfaces when the
SGW requests to delete all bearer contexts for the given
UE in an MME or S4-SGSN due to ISR deactivation, and
the Cause value shall be set to "ISR deactivation".
This IE shall be sent on the S2a/S2b interface if the
message is caused by handover from non-3GPP to 3GPP.
In this case the Cause value shall be set to "Access
changed from Non-3GPP to 3GPP".
O This IE may be sent by a PGW on S5/S8 during PGW
initiated bearer deactivation procedures for the default
bearer with values of "Reactivation requested" or " PDN
ETSI
reconnection to this APN disallowed " (see section 8.4 for

details).
O This IE may be sent by a PGW on S5 during PGW initiated
bearer deactivation procedures for the default bearer with
values of "PDN connection inactivity timer expires" (see
section 8.4 for details).
CO The IE shall be relayed by the SGW to the MME/S4-SGSN
if received from the PGW.
CO This IE shall be sent by the PGW on S5/S8 or S2a/S2b
with the value "Reactivation requested", when the PGW
initiates the bearer deactivation procedure for the default
bearer as part of the P-CSCF restoration procedure over
3GPP access or WLAN access, as specified in 3GPP TS
23.380 [61].
is set to 1.


clause 12.2.6).

See NOTE 3, NOTE 5.
ETSI

12.3.11).

APN(s).
See NOTE 4, NOTE 6.
clause 12.3.11).

NBIFOM Container CO This IE shall be included on the S5/S8 and S2a/S2b F-Container 0
shall be set to 4.
interfaces.
NOTE 1: If the SGW has sent multiple LBIs to MME/SGSN, but have received only one LBI within the Delete
Bearer Response message, this indicates that the MME/SGSN is pre Rel-10. In such case, the SGW
shall send separate individual Delete Bearer Request message(s) for each of remaining LBIs.
NOTE 2: If the SGW has received Delete Session Request with Cause value set to "ISR deactivation" and has
subsequently sent a Delete Bearer Request to the MME/SGSN with Cause value set to "ISR
deactivation", then the MME/SGSN shall delete all PDN connections corresponding to all of the LBIs
received in the Delete Bearer Request message for this UE. The MME/SGSN shall ignore any LBIs
for which there are no matching PDN connections corresponding to these LBIs.
for an E-UTRAN as specified by 3GPP TS 24.301 [23], then there will be only one instance of the EPS
Bearer IDs IE in the Delete Bearer Request.
Table 7.2.9.2-2: Bearer Context within Delete Bearer Request

elements
Cause M This IE shall indicate the reason of the unsuccessful Cause 0
handling of the bearer.
ETSI
Table 7.2.9-3: Load Control Information within Delete Bearer Request

elements
parameter.
See NOTE 1.
Table 7.2.9-4: Overload Control Information within Delete Bearer Request

elements
parameter.
7.2.10 Delete Session Response and Delete Bearer Response
7.2.10.1 Delete Session Response

A Delete Session Response message shall be sent on the S11 interface by the SGW to the MME and on the S5/S8
interface by the PGW to the SGW as part of the following procedures:
- EUTRAN Initial Attach
- UE, HSS or MME Initiated Detach
ETSI
- UE or MME Requested PDN Disconnection
It shall also be sent on the S4 interface by the SGW to the SGSN and on the S5/S8 interface by the PGW to the SGW as
part of the procedures:
- MS, HLR or SGSN initiated detach procedure
- Combined GPRS/IMSI Attach
- MS and SGSN Initiated Default Bearer Deactivation Procedure using S4
On the S11 interface by the SGW to the MME as part of the procedures:
- Tracking Area Update with SGW Change
- S1 Based Handover with SGW Change
- X2 Based Handover with SGW Relocation
- Inter RAT handover cancel with SGW change
- MME to 3G Gn/Gp SGSN combined hard handover and SRNS relocation procedure
- MME to SGSN Routing Area Update
- E-UTRAN to Gn/Gp SGSN Inter RAT handover
- S1 Based handover cancel with SGW change
And on the S4 interface by the SGW to the SGSN as part of the procedures:
- Enhanced Serving RNS Relocation with SGW relocation using S4
- Routing Area Update with SGW change
- SGSN to MME Tracking Area Update with SGW change
- Serving RNS relocation with SGW change
- S4 SGSN to Gn/Gp SGSN Routeing Area Update
- S4 SGSN to Gn/Gp SGSN Serving RNS Relocation Procedures
- S4 SGSN to Gn/Gp SGSN PS handover Procedures
The message shall also be sent on the S2b interface by the PGW to the ePDG as part of procedures:
- UE/ePDG Initiated Detach with GTP on S2b
- UE Requested PDN Disconnection with GTP on S2b
- HSS/AAA Initiated Detach with GTP on S2b
The message shall also be sent on the S2a interface by the PGW to the TWAN as part of procedures:
ETSI
- UE/TWAN Initiated Detach and UE/TWAN Requested PDN Disconnection in WLAN on GTP S2a
- HSS/AAA Initiated Detach in WLAN on GTP S2a
This message may also be sent on S5/S8 interface by the PGW to the SGW:
- If Downlink Data Notification Acknowledge message with Context not found cause value is received.
The sending entity shall include Cause IE in the Delete Session Response message. The IE indicates if the peer has
deleted the bearer, or not.
- "Invalid peer".
ETSI
Table 7.2.10.1-1: Information Elements in a Delete Session Response

elements
Cause M Cause 0
Protocol C PGW shall include Protocol Configuration Options (PCO) PCO 0
Configuration Options IE on the S5/S8 interface, if available.
(PCO) If SGW receives this IE, SGW shall forward it to
CO For trusted WLAN access, if the multi-connection mode is
used, the PGW may include this IE over the S2a interface
to send PCO to the UE.
is set to 1.


clause 12.2.6).

See NOTE 1, NOTE 3.
ETSI

12.3.11).

APN(s).
See NOTE 2, NOTE 4.
clause 12.3.11).

interfaces.
ETSI
Table 7.2.10.1-2: Load Control Information within Delete Session Response

elements
Load Metric M See clause 12.2.5.1.2.2 for the description and use of this Metric 0
parameter.
parameter.
See NOTE 1.
Table 7.2.10.1-3: Overload Control Information within Delete Session Response

elements
parameter.
See NOTE 1.
7.2.10.2 Delete Bearer Response

The Delete Bearer Response shall be sent as a response of Delete Bearer Request.
ETSI
ETSI
Table 7.2.10.2-1: Information Elements in Delete Bearer Response

elements
Cause M Cause 0
Linked EPS Bearer ID C If the response corresponds to the bearer deactivation EBI 0
(LBI) procedure in case all the bearers associated with the
default bearer of a PDN connection shall be released, this
IE shall be included on the S4/S11, S5/S8 and S2a/S2b
interfaces to indicate the default bearer associated with the
PDN being disconnected.
CO During a TAU/RAU/HO, if an MME/SGSN has received a
Delete Bearer Request message with Cause value "ISR
deactivation" and multiple LBIs, the MME/SGSN shall
include all these LBIs in the response message on S4/S11
interface. All LBI IEs shall have the same type and
instance value to represent a list of IEs.
Bearer Contexts C It shall be used on the S4/S11, S5/S8 and S2a/S2b Bearer Context 0
interfaces for bearers different from default one. In this
case at least one bearer shall be included.
Used for dedicated bearers. When used, at least one
dedicated bearer shall be present. All the bearer contexts
included in the EPS Bearer IDs IE of the corresponding
Delete Bearer Request shall be included.
MME-FQ-CSID C This IE shall be included by MME the on S11 interface and FQ-CSID 0
shall be forwarded by the SGW on S5/S8 interface
SGW-FQ-CSID C This IE shall be included by the SGW on the S5/S8 FQ-CSID 1
23.007 [17].
23.007 [17].
Protocol CO An MME/SGSN shall include the PCO IE if such PCO 0
Configuration Options information was received from the UE.
(PCO) If the SGW receives this IE, the SGW shall forward it to
PGW on the S5/S8 interface.
CO For the multi-connection mode, if the default bearer of the
PDN connection is being deleted and if the TWAN receives
the PCO from the UE, the TWAN shall forward the PCO IE
to the PGW.
CO This IE shall be included, if available, by the MME on the
S11 interface or by the SGSN on the S4 interface.
interface.
User Location
MME. ULI 0
Information (ULI)
See NOTE 2.
ETSI
TWAN Identifier CO This IE shall be included by the TWAN on the S2a TWAN Identifier 0
Timestamp interface if the TWAN Identifier IE is present. It shall Timestamp
indicate the time when the TWAN acquired the TWAN
Identifier information.
Overload Control
Overload Control 0
Information
interface.
include this IE on the S11/S4 interface when there is at
MME/S4-SGSN least one bearer remaining for the given PDN connection
IP Address 0
Identifier after the bearer deletion, and the PGW has not been
updated with the identity of the currently serving MME/S4-
SGSN, i.e. if no other message carrying MME/S4-SGSN
identity has been sent to the PGW during/after an inter-
MME/S4-SGSN intra-SGW mobility procedure.
TWAN/ePDG's
Overload Control 2
Information
TWAN Identifier 1
1
is detected.
4.
interfaces.
NOTE 1: If ISR is active, after receiving both the Delete Bearer Response messages from the MME and the
SGSN, the SGW shall include the most recent time and the related User Location Information in the
Delete Bearer Response message on S5/S8 interface.
ETSI
Table 7.2.10.2-2: Bearer Context within Delete Bearer Response

elements
This bearer level IE takes precedence over the PCO IE in
the message body if they both exist.
RAN/NAS Cause CO The MME shall include this IE on the S11 interface to RAN/NAS Cause 0
indicate the RAN release cause and/or NAS release cause
to release the bearer, if this information is available and is
MME operator's policy.
If both a RAN release cause and a NAS release cause are

generated, then several IEs with the same type and
instance value shall be included to represent a list of
causes.
Table 7.2.10.2-3: Overload Control Information within Delete Bearer Response

elements
Metric parameter.
parameter.
7.2.11 Downlink Data Notification messages
7.2.11.1 Downlink Data Notification

A Downlink Data Notification message shall be sent:
- on the S11 interface by the SGW to the MME as a part of the network triggered service request procedure;
ETSI
- on the S4 interface by the SGW to the S4-SGSN as part of Paging with no established user plane on S4, SGW
triggered paging with S4;
- on the S4 interface by the SGW to the S4-SGSN to re-establish all the previous released bearer(s) for a UE, upon
receipt of downlink data for a UE in connected mode but without corresponding downlink bearer available;
NOTE: This may occur e.g. if the S4-SGSN releases some but not all the bearers of the UE as specified in
subclause 12.7.2.2 of 3GPP TS 23.060 [35].
- on S11/S4 interface by SGW to MME/S4-SGSN if the SGW has received an Error Indication (see 3GPP TS
29.281 [13]) from eNodeB/RNC across S1-U/S12 interface. Respective SGW and MME/S4-SGSN functionality
is specified in 3GPP TS 23.007 [17].
- on the S11/S4 interface by SGW to the MME/S4-SGSN as part of the network triggered service restoration
procedure if both the SGW and the MME/S4-SGSN support this optional feature (see 3GPP TS 23.007 [17]).
A Downlink Data Notification message may be sent:
- on the S4 by the SGW to the S4-SGSN if the SGW has received an Error Indication from S4-SGSN across S4-U
interface.
ETSI
Table 7.2.11.1-1: Information Elements in a Downlink Data Notification

elements
Cause CO If SGW receives an Error Indication from eNodeB/RNC/S4- Cause 0
SGSN, the SGW shall send the Cause IE with value "Error
Indication received from RNC/eNodeB/S4-SGSN" to
MME/S4-SGSN as specified in 3GPP TS 23.007 [17].
EPS Bearer ID CO This IE shall be included on the S11 and S4 interfaces and EBI 0
shall be set as follows:
- If the Downlink Data Notification is triggered by
the arrival of downlink data packets at the SGW,
the SGW shall include the EPS Bearer ID stored
in the EPS bearer context of the bearer on which
the downlink data packet was received;
the receipt of an Error Indication from the
eNodeB, RNC or S4-SGSN, the SGW shall
include the EPS Bearer ID stored in the EPS
bearer context of the bearer for which the Error
Indication was received;
- If the ISR is active and the Downlink Data
Notification is triggered by the arrival of control
plane signalling, the SGW shall include the EPS
Bearer ID present in the control plane signalling
or derived from the control plane signaling (for
PMIP based S5/S8), See NOTE 3). For a
Downlink Data Notification triggered by a Create
Bearer Request message, the SGW shall include
the EPS Bearer ID of the corresponding PDN
connection's default bearer.
- If both the SGW and the MME/S4-SGSN support
the network triggered service restoration
procedure (see 3GPP TS 23.007 [17]), and if the
Downlink Data Notification is triggered by the
arrival of control plane signalling, the SGW shall
include the EPS Bearer ID present in the control
plane signalling or derived from the control plane
signaling (for PMIP based S5/S8). (See 3GPP TS
23.401[3], section 5.3.4.3).
More than one IE with this type and instance values may
be included to represent multiple bearers having received
downlink data packets or being signalled in the received
control plane message.
See NOTE 1.
Allocation/Retention CO This IE shall be included on the S11 and S4 interfaces and ARP 0
Priority shall be set as follows:
the arrival of downlink data packets at the SGW,
the SGW shall include the ARP stored in the EPS
bearer context of the bearer on which the
downlink data packet was received;
the receipt of an Error Indication from the
eNodeB, RNC or S4-SGSN, the SGW shall
include the ARP stored in the EPS bearer context
of the bearer for which the Error Indication was
received.
- If the ISR is active and the Downlink Data
Notification is triggered by the arrival of control
plane signalling, the SGW shall include the ARP if
present in the control plane signalling. If the ARP
is not present in the control plane signalling, the
SGW shall include the ARP in the stored EPS
bearer context. See NOTE 3.
- If both the SGW and the MME/S4-SGSN support
the network triggered service restoration
ETSI
procedure (see 3GPP TS 23.007 [17]), and if the

Downlink Data Notification is triggered by the
arrival of control plane signalling, the SGW shall
include the ARP if present in the control plane
signalling. If the ARP is not present in the control
plane signalling, the SGW shall include the ARP
from the stored EPS bearer context.
(See 3GPP TS 23.401[3], section 5.3.4.3).
If multiple EPS Bearers IDs are reported in the message,
the SGW shall include the ARP associated with the bearer
with the highest priority (i.e. the lowest ARP Priority Level
value).
See NOTE 1.
IMSI CO This IE shall be included on the S11/S4 interface as part of IMSI 0
the network triggered service restoration procedure if both
the SGW and the MME/S4-SGSN support this optional
feature (see 3GPP TS 23.007 [17]).
Sender F-TEID for O This IE may be included on the S11/S4 interface towards F-TEID 0
Control Plane the restarted CN node or an alternative CN node (same
type of mobility node as the failed one) as part of the
network triggered service restoration procedure with or
without ISR if both the SGW and the MME/S4-SGSN
support this optional feature (see 3GPP TS 23.007 [17]).
This IE shall not be included otherwise.
(NOTE 2)
is set to 1.

O The SGW may include this IE, over the S11/S4 interface if 0
the load control feature is supported by the SGW and is
SGW's node level
activated in the network (see clause 12.2.6). Load Control
Load Control
Information
Information
Paging and Service CO This IE shall be included on the S11 and S4 interfaces, if Paging and 0
Information the SGW supports the Paging Policy Differentiation feature Service
(see subclause 4.9 of 3GPP TS 23.401 [3]) and if the Information
Downlink Data Notification is triggered by the arrival of
downlink data packets at the SGW. If the preceding
conditions are fulfilled, then for each bearer and for each
packet that triggers a Downlink Data Notification, the SGW
shall copy, into the Paging Policy Indication value within
this IE, the value of the DSCP in TOS (IPv4) or TC (IPv6)
information received in the IP payload of the GTP-U packet
from the PGW (see IETF RFC 2474 [65]).
One IE with this type and instance value shall be included

per EPS Bearers ID reported in the message,
See NOTE 1.
NOTE 1: The usage of this parameter at the S4-SGSN is not specified in this release.
NOTE 2: In this version of the specification, the MME/S4-SGSN shall set the header TEID value in subsequent
ETSI
Downlink Data Notification Acknowledge or/and Downlink Data Notification Failure Indication to that
of the SGW"s Control Plane TEID if the Sender F-TEID for Control Plane IE is present in the
Downlink Data Notification message. However the SGW shall be prepared to receive messages in
which the header TEID value is set to zero from implementation conforming to earlier versions of this
specification. When that is the case, the receiver identifies the subscriber context based on the
included IMSI IE.
NOTE 3: For PMIP based S5/S8, if the SGW cannot derive the EPS bearer ID/ARP from the control plane
signalling (received over Gxx interface) the SGW should use the corresponding PDN connection"s
(for which the control plane signalling is received) default EPS bearer"s EPS bearer ID/ARP.
Table 7.2.11.1-2: Load Control Information within Downlink Data Notification

elements
parameter.
Table 7.2.11.1-3: Overload Control Information within Downlink Data Notification

elements
Metric parameter.
parameter.
7.2.11.2 Downlink Data Notification Acknowledge

A Downlink Data Notification Acknowledge shall be sent from a MME/SGSN to a SGW in response to Downlink Data
Notification with an indication of success, or failure when MME/SGSN has reachability or abnormal conditions.
- "UE already re-attached".
ETSI
Table 7.2.11.2-1: Information Elements in a Downlink Data Notification Acknowledge

elements
Cause M Cause 0
Data Notification C The MME/SGSN shall include an adaptive delay indication Delay Value 0
Delay to the SGW to delay the number of Data Notification
indications, if the rate of Downlink Data Notification event
occurrence in the MME/SGSN becomes significant (as
configured by the operator) and the MME/SGSN's load
exceeds an operator configured value.
time
DL low priority traffic O The MME/SGSN may send this IE to the SGW to request Throttling 0
Throttling the SGW to reduce the number of Downlink Data
Notification requests it sends for downlink low priority traffic
received for UEs in idle mode served by that MME/SGSN
in proportion to the Throttling Factor and during the
Throttling Delay.
See NOTE 1, NOTE 2, NOTE 3.

IMSI CO 3GPP TS 23.007 [17] specifies conditions for sending this IMSI 0
IE on the S11/S4 interface as part of the network triggered
service restoration procedure, if both the SGW and the
MME/S4-SGSN support this optional feature.
DL Buffering Duration CO The MME/SGSN shall include this IE on the S11/S4 EPC Timer 0
interface to indicate the duration during which the SGW
shall buffer DL data for this UE without sending any further
Downlink Data Notification message, if extended buffering
in the SGW is required as specified in subclause 5.3.4.3 of
3GPP TS 23.401 [3].
DL Buffering O The MME/SGSN may include this IE on the S11/S4 Integer Number 0
Suggested Packet interface, if the DL Buffering Duration IE is included, to
Count suggest the maximum number of downlink data packets to
be buffered in the SGW for this UE.
NOTE 1: The last received value of the Throttling Factor and Throttling Delay shall supersede any previous
values received from that MME/SGSN. The reception of a Throttling Delay shall restart the SGW
timer associated with that MME/SGSN. The SGW shall determine whether a bearer is for low priority
traffic or not on the basis of the bearer's ARP priority level and operator policy (i.e. operator's
configuration in the SGW of the ARP priority levels to be considered as prioritary or non-prioritary
traffic).
NOTE 2: For instance, if the DL low priority traffic Throttling IE indicates a Throttling Factor of 40% and a
Throttling Delay of 180 seconds, the SGW drops by 40% the number of Downlink Data Notification
requests it sends for downlink low priority traffic received for UEs in idle mode served by that
MME/SGSN, during a period of 180 seconds.
NOTE 3: The DL low priority traffic Throttling IE may be present whatever the value of the Cause IE.
7.2.11.3 Downlink Data Notification Failure Indication

A Downlink Data Notification Failure indication shall be sent from an MME/SGSN to a SGW indicating that the UE
did not respond to paging. It shall also be sent in the case that the UE responded to the page with a Service Request but
that the MME has rejected the request by sending a Service Reject to the UE. It may happen, for example, because the
requested service is not supported or there is a bearer context mismatch.
This message should not be used after an MME/SGSN successfully receives the Service Request message from the UE
in the Network Triggered Service Request procedure as defined in the 3GPP TS 23.401 [3].
NOTE: Either the Modify Bearer Request message or the Delete Bearer Command message is used by the
MME/SGSN to indicate a possible failure case after an MME/SGSN successfully receives the Service
Request message from the UE.
ETSI
- "Service denied".
- "UE already re-attached".
Table 7.2.11.3-1: Information Elements in a Downlink Data Notification Failure Indication

elements
Cause M Cause 0
Originating Node CO This IE shall be included on the S4/S11 interface if the ISR Node Type 0
associated GTP entities i.e. MME, S4-SGSN, send this
message to the SGW during the Network Triggered
Service Request procedure to denote the type of the node
originating the message.
IMSI CO 3GPP TS 23.007 [17] specifies conditions for sending this IMSI 0
IE on the S11/S4 interface as part of the network triggered
service restoration procedure, if both the SGW and the
MME/S4-SGSN support this optional feature.
7.2.12 Delete Indirect Data Forwarding Tunnel Request

The Delete Indirect Data Forwarding Tunnel Request message is sent on the S4/S11 interface by the SGSN/MME to the
SGW to delete the Indirect Forwarding Tunnels in the Source SGW/Target SGW as part of the following procedures:
- S1-based handover
- MME to 3G SGSN combined hard handover and SRNS relocation procedure
- Inter RAT handover Cancel
- S1-based handover Cancel
Table 7.2.12-1: Information Element in Delete Indirect Data Forwarding Tunnel Request

elements
Private Extension O Vendor or operator specific information Private Extension VS
7.2.13 Delete Indirect Data Forwarding Tunnel Response

The Delete Indirect Data Forwarding Tunnel Response message is sent on the S4/S11 interface by the SGW to the
SGSN/MME as part of the following procedures:
- S1-based handover
ETSI
- MME to 3G SGSN combined hard handover and SRNS relocation procedure
- Inter RAT handover Cancel
- S1-based handover Cancel
- "Request accepted partially"
Table 7.2.13-1: Information Element in Delete Indirect Data Forwarding Tunnel Response

elements
Cause M This IE shall indicate if the deletion of indirect tunnel is Cause 0
successful, and if not, gives information on the reason.
time.
7.2.14 Modify Bearer Command and Failure Indication
7.2.14.1 Modify Bearer Command

The Modify Bearer Command shall be sent on the S11 interface by the MME to the SGW and on the S5/S8 interface by
the SGW to the PGW as part of the HSS Initiated Subscribed QoS Modification procedure, or when the SQCI flag or
the PSCI flag is set to 1 in the Context Response message.
It shall also be sent on the S4 interface by the SGSN to the SGW and on the S5/S8 interface by the SGW to the PGW as
part of the HSS Initiated subscribed QoS modification procedure, or when the SQCI flag or the PSCI flag is set to 1 in
the Context Response message.
When deferred reporting of subscription change procedure is homogenously supported by MMEs and SGSNs in the
serving network, the MME shall defer sending Modify Bearer Command if the related UE is not reachable by the
MME, e.g. when the UE is suspended, when the UE has entered into power saving mode or when the PPF is cleared in
the MME, until the UE becomes reachable again as specified in 3GPP TS 23.401 [3].
NOTE: SGSNs do not defer the reporting of subscription change but need to support reporting the subscription
change when receiving the PSCI flag in the Context Response message.
It shall also be sent on the S2a/S2b interface by the TWAN/ePDG to the PGW as part of the HSS Initiated Subscribed
QoS Modification procedure.
ETSI
Table 7.2.14.1-1: Information Elements in a Modify Bearer Command

elements
APN-Aggregate M This IE shall contain the APN-AMBR value received by the AMBR 0
Maximum Bit Rate MME/SGSN/ TWAN/ePDG from the HSS.
(APN-AMBR)
Bearer Context M Only one IE with this type and instance value shall be Bearer Context 0
included and this shall represent the Default Bearer.
Overload Control
Overload Control 0
Information
interface.
TWAN/ePDG's
Overload Control 2
Information
interfaces.
Table 7.2.14.1-2: Bearer Context within Modify Bearer Command

elements
EPS Bearer ID M This IE shall contain the default bearer ID. EBI 0
Bearer Level QoS C Mandatory if other parameters than the APN-AMBR have Bearer QoS 0
been changed
CO This IE shall also be included if the SQCI flag or PSCI flag
is set to 1 in the Context Response message.
ETSI
Table 7.2.14-3: Overload Control Information within Modify Bearer Command

elements
Metric parameter.
parameter.
7.2.14.2 Modify Bearer Failure Indication

The Modify Bearer Failure Indication shall be sent on the S5/S8 interface by the PGW to the SGW and on the S11
interface by the SGW to the MME as part of failure of HSS Initiated Subscribed QoS Modification procedure, or when
the SQCI flag or the PSCI flag is set to 1 in the Context Response message.
It shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to the SGSN as
part of failure of HSS Initiated subscribed QoS modification, or when the SQCI flag or the PSCI flag is set to 1 in the
Context Response message.
It shall also be sent on the S2a/S2b interface by the PGW to the TWAN/ePDG as part of failure of HSS Initiated
Subscribed QoS Modification procedure.
Cause IE indicates that an EPS bearer has not been updated in the PGW.
- "Context not found"
- "Service denied".
ETSI
Table 7.2.14.2-1: Information Elements in a Modify Bearer Failure Indication

elements
Cause M Cause 0
is set to 1.


12.3.11).

APN(s).
See NOTE 1, NOTE 2.
supported by the SGW and and is activated in the network
(see clause 12.3.11).

interfaces.
ETSI
Table 7.2.14-2: Overload Control Information within Modify Bearer Failure Indication

elements
Metric parameter.
parameter.
Metric").
See NOTE 1.
7.2.15 Update Bearer Request

The direction of this message shall be from PGW to SGW and/or from SGW to MME/S4-SGSN, and/or from PGW to
For GTP based S5/S8, the Update Bearer Request shall be sent by the PGW to the SGW and forwarded to the MME as
part of the following procedures:
- PGW Initiated Bearer Modification with Bearer QoS Update
- HSS Initiated Subscribed QoS Modification
- PGW Initiated Bearer Modification without Bearer QoS Update
- UE Request Bearer Resource Modification procedure (see 3GPP TS 24.301 [23])
- UE requested bearer resource allocation procedure (see 3GPP TS 24.301 [23])
- P-CSCF restoration for 3GPP access (see 3GPP TS 23.380 [61])
the SGSN as part of the following procedures:
- PGW Initiated EPS Bearer Modification
- Execution part of MS-Initiated EPS Bearer Modification
- SGSN-Initiated EPS Bearer Modification Procedure using S4
- P-CSCF restoration for 3GPP access (see 3GPP TS 23.380 [61])
The message shall also be sent on the S2a/S2b interface by the PGW to the TWAN/ePDG as part of the following
procedures:
- PGW Initiated Bearer Modification
- HSS Initiated Subscribed QoS Modification
ETSI
- P-CSCF restoration for WLAN access (see 3GPP TS 23.380 [61])
For PMIP based S5/S8, the Update Bearer Request shall be sent on the S11 interface by the SGW to the MME and on
the S4 interface by the SGW to the SGSN.
on the S11/S4 interface by the SGW to the MME/S4-SGSN as part of the Network-initiated IP flow mobility procedure
or the UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161 [71].
Table 7.2.15-1 specifies the presence requirements and the conditions of the IEs in the message.
ETSI
Table 7.2.15-1: Information Elements in an Update Bearer Request

elements
Bearer Contexts M This IE shall contain contexts related to bearers that need Bearer Context 0
QoS/TFT modification. Several IEs with this type and
instance values shall be included as necessary to
If there is no QoS/TFT modification, only one IE with this
type and instance value shall be included.
Procedure C If the request corresponds to UE requested bearer PTI 0
Transaction Id (PTI) resource modification procedure or the UE requested
bearer resource allocation procedure for an E-UTRAN (see
NOTE 1) or MS initiated EPS bearer modification
procedure, this IE shall be included.
PTI shall be the same as the one used in the
corresponding Bearer Resource Command
Protocol C The PGW shall include the Protocol Configuration Options PCO 0
Configuration Options (PCO) IE on the S5/S8 interface, if available. The PCO IE
(PCO) shall carry a P-CSCF address list only when the UE is
required to perform an IMS registration, e.g during the P-
CSCF restoration procedure as defined in clause 5 of
3GPP TS 23.380 [61].
If SGW receives this IE, SGW shall forward it to
CO The PGW shall include the Prococol Configuration Options
(PCO) IE on the S2a interface, including the list of
available P-CSCF addresses, as part of the P-CSCF
restoration extension procedure for the TWAN access, as
Aggregate Maximum M APN-AMBR AMBR 0
Bit Rate (APN-AMBR)
Change Reporting C This IE shall be included on the S5/S8 and S4/S11 Change Reporting 0
Action interfaces with the appropriate Action field If the location Action
Change Reporting mechanism is to be started or stopped
CSG Information CO This IE shall be included on the S5/S8 and S4/S11 CSG Information 0
Reporting Action interfaces with the appropriate Action field if the CSG Info Reporting Action
reporting mechanism is to be started or stopped for this
Indication flags CO This IE shall be included if any one of the applicable flags Indication 0
is set to 1.
- Retrieve Location Indication: This flag shall be set
to 1 on the S5/S8, S4/S11, S2a and S2b interfaces
in the PGW Initiated Bearer Modification procedure
if the location information is requested.


ETSI

ETSI
PGW-FQ-CSID C This IE shall be included by PGW on the S5/S8 and FQ-CSID 0

S2a/S2b interfaces, and when received from S5/S8 be
forwarded by SGW on S11 according to the requirements
in 3GPP TS 23.007 [17].
SGW-FQ-CSID C This IE shall be included by SGW on S11 according to the FQ-CSID 1
Presence Reporting
Area Action
MME/SGSN.
clause 12.2.6).

See NOTE 2, NOTE 4.

12.3.11).

APN(s).
See NOTE 3, NOTE 5.
clause 12.3.11).
ETSI

shall be set to 4.
interfaces.
NOTE 1: This message refers to the UE requested bearer resource allocation procedure and UE requested
bearer resource modification procedures defined in 3GPP TS 24.301 [23], both are specified in
3GPP TS 23.401 [3] in the clause "UE requested bearer resource modification".
or UE Requested Bearer Resource Allocation Procedure for an E-UTRAN or MS initiated EPS bearer
modification procedure, then there will be only one instance of the Bearer Contexts IE in the Update
Bearer Request.
ETSI
Table 7.2.15-2: Bearer Context within Update Bearer Request

elements
TFT C This IE shall be included on the S5/S8, S4/S11 and Bearer TFT 0
S2a/S2b interfaces if message relates to Bearer
Modification and TFT change.
Bearer Level QoS C This IE shall be included on the S5/S8, S4/S11 and Bearer QoS 0
S2a/S2b interfaces if QoS modification is requested
Bearer Flags O Applicable flags: Bearer Flags 0
- PPC (Prohibit Payload Compression): this flag may
be set on the S5/S8 and S4 interfaces.
- vSRVCC indicator: This IE may be included by the

PGW on the S5/S8 interface according to 3GPP
TS 23.216 [43]. When received from S5/S8, SGW
shall forward on the S11 interface.
Protocol CO PGW shall include Protocol Configuration Options (PCO) PCO 0

Configuration Options IE on the S5/S8 interface, if available. The PCO IE shall
(PCO) carry a P-CSCF address list only when the UE is required
to perform an IMS registration, e.g during the P-CSCF
restoration procedure as defined in sub-clause 5.1 of
3GPP TS 23.380 [61].
If the SGW receives this IE, the SGW shall forward it to the
CO The PGW shall include the Prococol Configuration Options
(PCO) IE on the S2a interface, including the list of
available P-CSCF addresses, as part of the P-CSCF
restoration extension procedure for the TWAN access, as
CO The PGW shall include the Additional Prococol
Configuration Options (APCO) IE on the S2b interface, Additional
Additional Protocol
including the list of available P-CSCF addresses, as part of Protocol
Configuration Options 0
the P-CSCF restoration extension procedure for the Configuration
(APCO)
untrusted WLAN access, as specified in 3GPP TS 23.380 Options (APCO)
[61].
ETSI
Table 7.2.15-3: Load Control Information within Update Bearer Request

elements
parameter.
See NOTE 1.
Table 7.2.15-4: Overload Control Information within Update Bearer Request

elements
parameter.
See NOTE 1.
7.2.16 Update Bearer Response

An Update Bearer Response shall be sent from a MME/SGSN to a SGW and forwarded to the PGW, and from
TWAN/ePDG to the PGW as a response to an Update Bearer Request message.
Cause IE indicates if an EPS bearer has been modified in the MME/SGSN/TWAN/ePDG or not. The EPS Bearer has
not been modified in the MME/SGSN/TWAN/ePDG if the Cause IE value differs from "Request accepted" or "Request
accepted partially". Possible Cause values are specified in Table 8.4-1. Message specific cause values are:
ETSI
- "Request accepted partially"
- "Denied in RAT".
- "UE refuses".
- "MME/SGSN refuses due to VPLMN Policy".
- "UE is temporarily not reachable due to power saving"
ETSI
Table 7.2.16-1: Information Elements in an Update Bearer Response

elements
Cause M Cause 0
Bearer Contexts M This IE shall contain all the bearer contexts included in the Bearer Context 0
corresponding Update Bearer Request. Several IEs with
this type and instance values shall be included as
necessary to represent a list of Bearers.

MME-FQ-CSID C This IE shall be included by MME on S11and shall be FQ-CSID 0
forwarded by SGW on S5/S8 according to the
SGW-FQ-CSID C This IE shall be included by SGW on S5/S8 according to FQ-CSID 1
23.007 [17].
is set to 1.
Applicable flags:
the S4 interface, if Direct Tunnel is used.
O This IE is optionally included by the MME on the S11
interface or by the SGSN on the S4 interface.
interface.
User Location
MME. ULI 0
Information (ULI)
See NOTE 1.
Overload Control
Overload Control 0
Information
interface.
Presence Reporting CO The MME/SGSN shall include this IE on S11/S4 if the Presence 0
Area Information PGW/PCRF has requested to start reporting changes of Reporting Area
UE presence in a Presence Reporting Area in the Information
corresponding Update Bearer Request message and the
ETSI
MME/SGSN supports such reporting. The MME/SGSN

shall then indicate whether the UE is inside or outside the

Presence Reporting Area Information from the
MME/SGSN.
include this IE on the S11/S4 interface if the PGW has not
been updated with the identity of the currently serving
MME/S4-SGSN
MME/S4-SGSN, i.e. if no other message carrying IP Address 0
Identifier
MME/S4-SGSN identity has been sent to the PGW
during/after an inter-MME/S4-SGSN intra-SGW mobility
procedure.
CO If the overload control feature is supported by the SGW,
the SGW shall forward this IE on the S5/S8 interface.
TWAN/ePDG's
Overload Control 2
Information
TWAN Identifier 1
1
is detected.
4.
interfaces.
ETSI
Table 7.2.16-2: Bearer Context within Update Bearer Response

elements
Cause M This IE Indicates if the bearer handling was successful, Cause 0
S4-U SGSN F-TEID C This IE shall be included on the S4 interface when direct F-TEID 0
tunnel is not established. See NOTE 1.
S12 RNC F-TEID C This IE shall be included on the S4 interface when direct F-TEID 1
tunnel flag is set to 1. See NOTE 1.
RAN/NAS Cause CO If the bearer modification failed, the MME shall include this RAN/NAS Cause 0
IE on the S11 interface to indicate the RAN cause and/or
the NAS cause of the bearer modification failure, if
available and if this information is permitted to be sent to
the PGW operator according to MME operator's policy.
If both a RAN cause and a NAS cause are generated, then
several IEs with the same type and instance value shall be
included to represent a list of causes.
CO If the bearer modification failed, the TWAN shall include
this IE on the S2a interface to indicate the cause of the
bearer modification failure, if available and if this
information is permitted to be sent to the PGW operator
according to the TWAN operator's policy. When present,
the IE shall be encoded as a Diameter or an ESM cause.
See NOTE 2.
CO If the bearer modification failed, the ePDG shall include
this IE on the S2b interface to indicate the cause of the
bearer modification failure, if available and if this
information is permitted to be sent to the PGW operator
according to the ePDG operator's policy. When present,
the IE shall be encoded as a Diameter or an IKEv2 cause.
See NOTE 3.
NOTE 1: In some scenarios, the SGSN is unable to provide neither the S12 RNC F-TEID nor the S4-U SGSN
F-TEID in the Update Bearer Response message, e.g. when Direct Tunnel is used in 3G and the UE
is in IDLE mode, for a network requested user location retrieval procedure, the SGSN is unable to
provide S12 RNC F-TEID. In those scenarios, the SGSN shall provide EBI(s) without S12 RNC F-
TEID(s) and S4-U SGSN F-TEID. The SGW shall be able to handle these bearer context(s).
However, in earlier releases this behaviour may not be supported by the SGW and hence for such an
SGW, in order to be backward compatible, the SGSN shall provide EBI(s) together with either the
S4-U SGSN F-TEID or the S12 RNC F-TEID.
NOTE 2: The TWAN does not exchange signalling with the 3GPP AAA Server nor with the UE in this
procedure. The TWAN may include an internal failure cause for the bearer modification failure. The
protocol type used to encode the internal failure cause is implementation specific.
NOTE 3: The ePDG does not exchange signalling with the 3GPP AAA Server in this procedure. The ePDG
may include an internal failure cause for the bearer modification failure. The protocol type used to
encode the internal failure cause is implementation specific.
ETSI
Table 7.2.16-3: Overload Control Information within Update Bearer Response

elements
Metric parameter.
parameter.
7.2.17 Delete Bearer Command and Failure Indication
7.2.17.1 Delete Bearer Command

A Delete Bearer Command message shall be sent on the S11 interface by the MME to the SGW and on the S5/S8
interface by the SGW to the PGW as a part of the eNodeB requested bearer release or MME-Initiated Dedicated Bearer
Deactivation procedure.
The message shall also be sent on the S4 interface by the SGSN to the SGW and on the S5/S8 interface by the SGW to
the PGW as part of the MS and SGSN Initiated Bearer Deactivation procedure using S4.
ETSI
Table 7.2.17.1-1: Information Elements in Delete Bearer Command

elements
Bearer Contexts M This IE shall be used to indicate dedicated bearers. When Bearer Context 0
used, at least one dedicated bearer shall be present.
included as necessary to represent a list of Bearers
User Location CO This IE shall be included by the MME on the S11 interface ULI 0
Information (ULI) or by the SGSN on the S4 interface. The CGI/SAI shall be
MME.
The SGW shall forward this IE on the S5/S8 interface if it
See NOTE 1.
UE Time Zone CO This IE shall be included, if available, by the MME on the
S11 interface or by the SGSN on the S4 interface.
UE Time Zone 0
Overload Control
Overload Control 0
Information
interface.
ETSI
Table 7.2.17.1-2: Bearer Context within Delete Bearer Command

elements
Bearer Flags CO Applicable flags are: Bearer Flags 0
- VB (Voice Bearer) indicator shall be set to
indicate a voice bearer for PS-to-CS (v)SRVCC
handover.
- Vind (vSRVCC indicator) indicator shall be set to
indicate a video bearer for PS-to-CS vSRVCC
handover.
RAN/NAS Release CO The MME shall include this IE on the S11 interface to RAN/NAS Cause 0
Cause indicate the RAN release cause and/or NAS release cause
to release the bearer, if available and this information is
permitted to be sent to the PGW operator according to
MME operator's policy.
If both a RAN release cause and a NAS release cause are
generated, then several IEs with the same type and
instance value shall be included to represent a list of
causes.
Table 7.2.17.1-3: Overload Control Information within Delete Bearer Command

elements
Metric parameter.
parameter.
7.2.17.2 Delete Bearer Failure Indication

A Delete Bearer Failure Indication shall be sent on the S5/S8 interface by the PGW to the SGW and on the S11
interface by the SGW to the MME as part of failure of eNodeB requested bearer release or MME Initiated Dedicated
Bearer Deactivation procedure.
the SGSN as part of failure of MS and SGSN Initiated Bearer Deactivation procedure using S4.
This message shall be sent back if none of the bearers (not even a single one) included in the Delete Bearer Command
message could be deleted.
The Cause IE indicates that the EPS bearer has not been deleted in the PGW.
When the SGW receives a Delete Bearer Failure Indication message from the PGW with the TEID set to zero in the
GTPv2 header and the Cause IE is set to "Context Not Found", which implies that the PDN connection does not exist in
the PGW, the SGW may send a Delete Bearer Request message to delete the PDN connection towards the MME/SGSN
after sending the Delete Bearer Failure Indication message.
ETSI
Table 7.2.17.2-1: Information Elements in a Delete Bearer Failure Indication

elements
Cause M Cause 0
Bearer Context M This IE shall contain the list of failed bearers. See Bearer Context 0
subclause 6.1.1 "Presence requirements of Information
Elements".
Recovery C This IE shall be included If contacting the peer for the first Recovery 0
time.
is set to 1.


Control Information on the S5/S8, if the overload control feature is supported Information
by the PGW and is activated for the PLMN to which the
access network node, i.e. MME/S4-SGSN for 3GPP
access based network belongs (see clause 12.3.11).

APN(s).
See NOTE 1, NOTE 2.
clause 12.3.11).

ETSI
Table 7.2.17.2-2: Bearer Context within Delete Bearer Failure Indication

elements
EPS Bearer ID M See subclause 6.1.1 "Presence requirements of EBI 0
Information Elements".
Cause M This IE shall indicate the reason of the unsuccessful Cause 0
handling of the bearer.
Table 7.2.17-3: Overload Control Information within Delete Bearer Failure Indication

elements
parameter.
See NOTE 1.
7.2.18 Create Indirect Data Forwarding Tunnel Request

The Create Indirect Data Forwarding Tunnel Request message shall be sent on the S11/S4 interface by the MME/SGSN
to the SGW as part of the Handover procedures or TAU/RAU procedure with Serving GW change and data forwarding
as specified in subclause 5.3.3.1A of 3GPP TS 23.401 [3].
ETSI
Table 7.2.18-1: Information Elements in a Create Indirect Data Forwarding Tunnel Request

elements
IMSI C This IE shall be included by the MME/SGSN if the SGW IMSI 0
that the MME/SGSN selects for indirect data forwarding is
different from the SGW already in use for the UE as the
anchor point except for the case:
UICCless
When the IMSI is included in the message, it is not used as

an identifier
authenticated.
See NOTE1.
ME Identity (MEI) C This IE shall be included by the MME/SGSN if the SGW MEI 0
that the MME/SGSN selects for indirect data forwarding is
anchor point and if one of the following condition satisfies:
UICCless

authenticated
is set to 1.
- Unauthenticated IMSI: This flag shall be set to 1 if
the IMSI present in the message is not
authenticated and is for an emergency attached
UE.
Sender F-TEID for C This IE shall be included by the MME/SGSN if the SGW F-TEID 0
Control Plane that the MME/SGSN selects for indirect data forwarding is
anchor point.
See NOTE1.
Bearer Contexts M Several IEs with this type and instance value may be Bearer Context 0
Recovery CO This IE shall be included if contacting the peer for the first Recovery 0
time.
NOTE 1: The SGW which is hosting the UE's bearer(s) is considered as the (local) anchor point. Unlike the
PGW, the SGW may change due to mobility between eNodeBs, or E-UTRAN and GERAN/UTRAN
supported with S4 based architecture. In these cases the new SGW where the UE's bearer(s) are
moved, becomes the new local anchor point. A source MME/SGSN may select an SGW for indirect
data forwarding which is different than the source (anchor) SGW. Similarly, a target MME/SGSN may
select an SGW for indirect data forwarding which is different than the target (anchor) SGW.
ETSI
Table 7.2.18-2: Bearer Context within Create Indirect Data Forwarding Tunnel Request

elements
eNodeB F-TEID for C Target eNodeB F-TEID. F-TEID 0
DL data forwarding This IE shall be present in the message sent from the
target MME to the SGW selected by the target MME for
indirect data forwarding, or shall be included in the
message sent from the source SGSN/MME to the SGW
selected by the source MME for indirect data forwarding if
the eNodeB F-TEID for DL data forwarding is included in
the Forward Relocation Response message.
CO Target eNodeB F-TEID.
This IE shall be present in the message sent from the
target MME to the SGW selected by the target MME for
indirect data forwarding of the DL data buffered in the old
SGW during a TAU with SGW change procedure and data
forwarding, as specified in subclause 5.3.3.1A of 3GPP TS
23.401 [3].
SGW F-TEID for DL C Target SGW F-TEID F-TEID 1
data forwarding This IE shall be present in the message sent from the
source MME/SGSN to the SGW selected by the source
MME for indirect data forwarding if SGW F-TEID for DL
data forwarding is included in the Forward Relocation
Response message. This F-TEID is assigned by the SGW
that the target MME/SGSN selects for indirect data
forwarding.
SGSN F-TEID for DL C Target SGSN F-TEID F-TEID 2
target SGSN to the SGW selected by the target SGSN for
indirect data forwarding in E-UTRAN to GERAN/UTRAN
inter RAT handover with SGW relocation procedure, or
shall be included in the message sent from the source
MME to the SGW selected by the source MME for indirect
data forwarding if the SGSN F-TEID for DL data forwarding
is included in the Forwarding Relocation Response
message.
CO This IE shall also be present in the message sent from the
source MME to the SGW selected by the source MME for
indirect data forwarding if the SGSN Address for User
Traffic and the Tunnel Endpoint Identifier Data II are
included in the GTPv1 Forward Relocation Response
message as specified in D.3.7 of 3GPP TS 23.401 [3]. .
This IE shall also be present, when Direct Tunnel is not

used, in the message sent from the target SGSN to the
SGW selected by the target SGSN for indirect data
forwarding of the DL data buffered in the old SGW during a
RAU with SGW change procedure and data forwarding, as
specified in subclause 5.3.3.1A of 3GPP TS 23.401 [3].
RNC F-TEID for DL C Target RNC F-TEID F-TEID 3
target SGSN to the SGW selected by the target SGSN for
indirect data forwarding in E-UTRAN to UTRAN inter RAT
handover with SGW relocation procedure, or shall be
included in the message sent from the source MME to the
SGW selected by the source MME for indirect data
forwarding if the RNC F-TEID for DL data forwarding is
included in the Forwarding Relocation Response message.
CO This IE shall also be present in the message sent from the
source MME to the SGW selected by the source MME for
indirect data forwarding if the RNC IP address and TEID
are included in the RAB Setup Information and/or the
Additional RAB Setup Information in the GTPv1
ETSI
Forwarding Relocation Response message as specified in

D.3.3 of 3GPP TS 23.401 [3].
This IE shall be present, when Direct Tunnel is used, in the

message sent from the target SGSN to the SGW selected
by the target SGSN for indirect data forwarding of the DL
data buffered in the old SGW during a RAU with SGW
change procedure and data forwarding as specified in
subclause 5.3.3.1A of 3GPP TS 23.401 [3].
eNodeB F-TEID for O Target eNodeB F-TEID. F-TEID 4
UL data forwarding If available this IE may be present in the message, which is
sent during the intra-EUTRAN HO from the target MME to
the SGW selected by the target MME for indirect data
forwarding, or may be included in the message sent from
the source MME to the SGW selected by the source MME
for indirect data forwarding if the eNodeB F-TEID for data
UL forwarding is included in the Forward Relocation
Response message.
SGW F-TEID for UL O Target SGW F-TEID F-TEID 5
data forwarding If available this IE may be present in the message, which is
sent during the intra-EUTRAN HO from the source MME to
the SGW selected by the source MME for indirect data
forwarding if SGW F-TEID for UL data forwarding is
included in the Forward Relocation Response message.
This F-TEID is assigned by the SGW that the target MME
selects for indirect data forwarding.
7.2.19 Create Indirect Data Forwarding Tunnel Response

A Create Indirect Data Forwarding Tunnel Response message shall be sent by the SGW to the MME/SGSN as a
response to a Create Indirect Data Forwarding Tunnel Request message.
The Cause value indicates if the Indirect Data Forwarding Tunnels has been created in the SGW or not. No Indirect
Data Forwarding Tunnels have been created in the SGW if the Cause differs from "Request accepted" or "Request
accepted partially". Possible Cause values are specified in Table 8.4-1. Message specific cause values are:
- "Data forwarding not supported".
Table 7.2.19-1: Information Elements in a Create Indirect Data Forwarding Tunnel Response

elements
Cause M Cause 0
Sender F-TEID for C This IE shall be included by an SGW if the SGW receives a F-TEID 0
Control Plane Sender F-TEID for Control Plane IE from an MME/SGSN in
a Create Indirect Data Forwarding Tunnel Request
message.
See also NOTE 1 in Table 7.2.18-1.
Bearer Contexts M Several IEs with this type and instance value may be Bearer Context 0
time
ETSI
Table 7.2.19-2: Bearer Context within Create Indirect Data Forwarding Tunnel Response

elements
Cause M This IE shall indicate if the tunnel setup was successful, Cause 0
S1-U SGW F-TEID C This IE shall be included in the response sent from the F-TEID 0
for DL data SGW selected by the source MME for indirect data
forwarding forwarding to the source MME. See NOTE 3.
S12 SGW F-TEID for C S12 usage only. F-TEID 1
DL data forwarding This IE shall be included in the response sent from the
SGW selected by the source SGSN for indirect data
forwarding to the source SGSN. See NOTE 3.
S4-U SGW F-TEID C S4-U usage only. F-TEID 2
for DL data This IE shall be included in the response sent from the
forwarding SGW selected by the source SGSN for indirect data
forwarding to the source SGSN. See NOTE 3.
SGW F-TEID for DL C This IE shall be included in the response message sent F-TEID 3
data forwarding from the SGW selected by the target MME/SGSN for
indirect data forwarding to the target MME/SGSN. See
NOTE 3.
S1-U SGW F-TEID O If available this IE may be included in the response sent F-TEID 4
for UL data during the intra-EUTRAN HO from the SGW selected by
forwarding the source MME for indirect data forwarding to the source
MME. See NOTE 4.
SGW F-TEID for UL O If available this IE may be included in the response F-TEID 5
data forwarding message sent during the intra-EUTRAN HO from the SGW
selected by the target MME for indirect data forwarding to
the target MME. See NOTE 4.
NOTE 1: For DL data forwarding if the SGW does not have enough information to decide which of the F-TEID
instance from S1-U, S12, S4-U and SGW to include in the message, it may include all of them.
NOTE 2: For UL data forwarding if the SGW does not have enough information to decide which of the F-TEID
instance from S1-U and SGW to include in the message, it may include both of them.
NOTE 3: For DL data forwarding the SGW shall set the interface type in the F-TEID to 23, i.e 'SGW GTP-U
interface for DL data forwarding' for S1-U/S4-U/S12/SGW.
NOTE 4: For UL data forwarding the SGW shall set the interface type in the F-TEID to 28, i.e 'SGW GTP-U
interface for UL data forwarding' for S1-U/SGW.
7.2.20 Void
7.2.21 Release Access Bearers Request

The Release Access Bearers Request message shall sent on the S11 interface by the MME to the SGW as part of the S1
release procedure.
The message shall also be sent on the S4 interface by the SGSN to the SGW as part of the procedures:
- RAB release using S4
- Iu Release using S4
- READY to STANDBY transition within the network
ETSI
Table 7.2.21-1: Information Element in Release Access Bearers Request

elements
List of RABs C Shall be present on S4 interface when this message is EBI 0
used to release a subset of all active RABs according to
the RAB release procedure.
included as necessary to represent a list of RABs to be
released.
Originating Node CO This IE shall be sent on S11 interface, if ISR is active in the Node Type 0
MME.
This IE shall be sent on S4 interface, if ISR is active in the
SGSN
See NOTE 1.
is set to 1.
- Abnormal Release of Radio Link: This flag shall be
set to 1 on the S11 interface if the S1 release is
due to an abnormal release of the radio link, e.g.
when the MME receives UE CONTEXT RELEASE
REQUEST with the cause value set to Radio
Connection With UE Lost.

NOTE 1: If SGW has the S1-U F-TEIDs for the UE, but the Originating Node IE contains value "SGSN", then
the SGW shall not release the user plane and shall send a positive response to the SGSN.
If SGW has the S12 RNC TEIDs or S4-U SGSN TEIDs for the UE, but the Originating Node IE
contains value "MME", then the SGW shall not release the user plane and shall send a positive
response to the MME.
7.2.22 Release Access Bearers Response

The Release Access Bearers Response message is sent on the S11 interface by the SGW to the MME as part of the S1
release procedure.
The message shall also be sent on the S4 interface by the SGW to the SGSN as part of the procedures:
- RAB release using S4
- Iu Release using S4
- READY to STANDBY transition within the network
ETSI
Table 7.2.22-1: Information Element in Release Access Bearers Response

elements
Cause M Cause 0
Recovery O This IE shall be included if contacting the peer for the first Recovery 0
time
is set to 1.

O The SGW may include this IE, over the S11/S4 interface if Load Control 0
the load control feature is supported by the SGW and is Information
SGW's node level
activated in the network (see clause 12.2.6).
Load Control
Information
clause 12.3.11). 0
Table 7.2.22-2: Load Control Information within Release Access Bearers Response

elements
parameter.
Table 7.2.22-3: Overload Control Information within Release Access Bearers Response

elements
Metric parameter.
parameter.
ETSI
7.2.23 Stop Paging Indication

A Stop Paging Indication message shall be sent on the S11/S4 interface by the SGW to the MME/SGSN as a part of the
network triggered service request procedure.
Table 7.2.23-1: Information Elements in a Stop Paging Indication

elements
IMSI CO This IE shall be included on the S11/S4 interface when the IMSI 0
Stop Paging Indication message is sent to the restarted
CN node (or another node in the same pool) as part of the
network triggered service restoration procedure with ISR
(see 3GPP TS 23.007 [17]).
7.2.24 Modify Access Bearers Request

The direction of this message shall be from MME to SGW (see Table 6.1-1).
If both the SGW and the MME support the MABR feature (see subclause 8.83), an MME may send a Modify Access
Bearer Request message on the S11 interface to an SGW as part of the following procedures:
- UE triggered Service Request if there is no suspended bearer for that UE,
- S1-based Handover without SGW relocation,
- X2-based handover without SGW relocation,
- Inter-MME E-UTRAN Tracking Area Update without SGW Change,
- Intra-MME E-UTRAN Tracking Area Update without SGW Change with Active Flag;
- E-UTRAN Initiated E-RAB modification procedure
if all the following conditions are fulfilled:
- the RAT type has not changed;
- the Serving Network has not changed;
- the MME does not need to report a H(e)NB local IP address and UDP port number information change;
- the MME does not need to send UE's location and/or User CSG information or/and UE Time Zone and/or
Presence Reporting Area information to the PDN GW;
- the MME does not need to send an MME-FQ-CSID as per the requirements specified in 3GPP TS 23.007 [17];
- ISR is not activated, if the Modify Access Bearers Request is sent as part of a UE triggered Service Request;
- ISR was not activated in the old MME which is indicated by the ISRAU flag in the Context Response, if the
Modify Access Bearers Request is sent as part of an Inter-MME E-UTRAN Tracking Area Update without
SGW change.
The Modify Access Bearers Request message shall include all the bearer contexts of all the PDN connections of the UE.
Support of this message is optional for the MME and SGW.
ETSI
Table 7.2.24-1: Information Elements in a Modify Access Bearers Request

elements
is set to 1.
- ISRAI: This flag shall be set to 1 if ISR is
established between the MME and the S4 SGSN
for an S1-based Handover without SGW relocation
and for an X2-based Handover without SGW
relocation.
- Change F-TEID support Indication: This flag shall

be set to 1 for an IDLE state UE initiated TAU
procedure to allow the SGW changing the GTP-U
F-TEID.
Sender F-TEID for C The new MME shall include this IE on the S11 interface for F-TEID 0
Control Plane a TAU/Handover with MME change and without any SGW
change.
If the SGW receives this IE and if it finds that its value is
UE, it should interpret this to mean that the MME has not
changed.
Delay Downlink C This IE shall be sent for a UE triggered Service Request. Delay Value 0
Packet Notification
Request
Bearer Contexts to be C Several IEs with the same type and instance value may be Bearer Context 0
modified included as necessary to represent a list of Bearers to be
modified.
See NOTE 1.
Bearer Contexts to be C This IE shall be included for the TAU/Handover and Bearer Context 1
removed Service Request procedures where any of the bearers
existing before the TAU/Handover procedure and Service
Request procedures will be deactivated as consequence of
the TAU/Handover procedure and Service Request
procedures.
For the Service Request procedure, all unaccepted
bearers for this UE shall be included.
instance value, shall be included.
See NOTE 1.
time.
NOTE 1: The Bearer Context to be modified IE and Bearer Context to be removed IE, together, shall contain
all the bearers of all the existing PDN connections of the UE, with each bearer appearing in only one
of these IEs.
ETSI
Table 7.2.24-2: Bearer Context to be modified within Modify Access Bearers Request

elements
S1-U eNodeB F-TEID C This IE shall be sent for F-TEID 0
- an UE triggered Service Request
- S1-based Handover without SGW relocation
- X2-based handover without SGW relocation
- in S1-U GTP-U tunnel setup procedure during an

Inter-MME E-UTRAN Tracking Area Update
without SGW Change procedure or Intra-MME E-
UTRAN Tracking Area Update without SGW
Change procedure with Active Flag (see 3GPP
TS 24.301 [23]).
- an E-UTRAN Initiated E-RAB modification

procedure.
If an MME is aware that the eNodeB supports both IP

address types, the MME shall send both IP addresses
within an F-TEID IE. If only one IP address is included,
then the SGW shall assume that the eNodeB does not
support the other IP address type.
Table 7.2.24-3: Bearer Context to be removed within Modify Access Bearers Request

elements
7.2.25 Modify Access Bearers Response

If an SGW supports the MABR feature (see subclause 8.83), the SGW shall send a Modify Access Bearers Response
message on the S11 interface to an MME as a response to a Modify Access Bearers Request message.
If handling of all default bearers to be modified fails, then Cause at the message level shall be a failure cause.
- "Service not supported".
- "Modifications not limited to S1-U bearers"
The SGW shall send the cause value "Modifications not limited to S1-U bearers" if
- it can not serve the MME Request without corresponding S5/S8 signalling other than to unpause charging in
the PGW, or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, or
- if there are suspended non-GBR bearers for that UE in the SGW (NOTE 3).
ETSI
Upon receipt of that cause value, the MME shall repeat its request using Modify Bearer Request message per PDN
connection.
NOTE 1: This cause value is introduced for forward compatibility between an MME implementing this version of
the specification and an SGW implementing a more recent version requiring the SGW to send S5/S8
signalling.
NOTE 2: During an Inter-MME Intra-SGW handover/TAU, if the SGW, PGW and the old MME support the partial
failure handling feature but the new MME doesn't, the SGW needs to inform the PGW about the change
of FQ-CSID (see subclause 16.2.5 of 3GPP TS 23.007 [17]). If the SGW receives a Modify Access
Bearers Request from the new MME, it can force the MME to send individual Modify Bearer Request
message per PDN connection by returning the cause value "Modifications not limited to S1-U bearers".
NOTE 3: There may be some suspended non-GBR bearers in the SGW during an Inter-MME Intra-SGW Tracking
Area Update without SGW Change when the UE is coming back to E-UTRAN via a different MME than
the MME serving the UE before the CSFB or SRVCC call.
Table 7.2.25-1: Information Elements in a Modify Access Bearers Response

elements
Cause M Cause 0
modified modified that were sent in Modify Access Bearers Request
message. Several IEs with the same type and instance
value may be included as necessary to represent a list of
the Bearers which are modified.
marked for removal removed that were sent in the Modify Access Bearers
Request message. Shall be included if request message
contained Bearer Contexts to be removed.
time.
is set to 1.

O The SGW may include this IE, over the S11/S4 interface if Load Control 0
the load control feature is supported by the SGW and is Information
SGW's node level
activated in the network (see clause 12.2.6).
Load Control
Information
clause 12.3.11). 0
ETSI
Table 7.2.25-2: Bearer Context modified within Modify Access Bearers Response

elements
S1-U SGW F-TEID M The SGW may change the GTP-U F-TEID value if the F-TEID 0
'Change F-TEID support Indication' flag was set to 1 in the
Modify Access Bearers Request. Otherwise, the SGW
shall return the currently allocated GTP-U F-TEID value.
See NOTE 1.
NOTE 1: The SGW shall not change its F-TEID for a given interface during the Handover, Service Request
and E-UTRAN Initiated E-RAB modification procedures.
During Handover and Service Request the target eNodeB may use a different IP type than the one
used by the source eNodeB. In order to support such a scenario, the SGW F-TEID should contain
both an IPv4 address and an IPv6 address (see also subclause 8.22 "F-TEID").
Table 7.2.25-3: Bearer Context marked for removal within Modify Access Bearers Response

elements
Table 7.2.25-4: Load Control Information within Modify Access Bearers Response

elements
parameter.
Table 7.2.25-5: Overload Control Information within Modify Access Bearers Response

elements
Metric parameter.
parameter.
ETSI
7.2.26 Remote UE Report Notification

The direction of this message shall be from MME to SGW and from SGW to the PGW (see Table 6.1-1).
This message is used by an MME to notify that at least one remote UE is newly connected to or disconnected from a
ProSe UE-to-Network Relay when the MME receives such notification from the ProSe UE-to-Network Relay via the
PDN connection established by the ProSe UE-to-Network Relay as specified in 3GPP TS 23.303 [72].
Table 7.2.26-1 specifies the presence of IEs in this message.
Table 7.2.26-1: Information Elements in Remote UE Report Notification

elements
Remote UE Context C This IE shall be sent on the S11 interface and S5/S8 Remote UE 0
Connected interface when the MME receives a report from the ProSe Context
UE-to-Network Relay that a remote UE is newly
connected.
The SGW shall forward this IE to the PGW.
newly connected.
Remote UE Context C This IE shall be sent on the S11 interface and S5/S8 Remote UE 1
Disconnected interface when the MME receives a report from the ProSe Context
UE-to-Network Relay that a remote UE is newly
disconnected.
The SGW shall forward this IE to the PGW.
newly disconnected.
Table 7.2.26-2: Remote UE Context Connected within Remote UE Report Notification
Octets 1 Remote UE Context IE Type = 191 (decimal)

elements
parameter
Table 7.2.26-3: Remote UE Context Disconnected with Remote UE Report Notification

elements
parameter
7.2.27 Remote UE Report Acknowledge

The Remote UE Report Acknowledge message shall be sent as the response to a Remote UE Report Notification, to
acknowledge the information related to the remote UE(s) is received.
ETSI
Possible Cause values are specified in Table 8.4-1.
Table 7.2.27-1: Information Elements in Remote UE Report Acknowledge

elements
Cause M Cause 0
7.3 Mobility Management Messages

7.3.1 Forward Relocation Request
A Forward Relocation Request message shall be sent from the source MME to the target MME over S10 interface as
part of S1-based handover relocation procedure from the source MME to the target SGSN, or from the source SGSN to
the target MME over S3 interface as part of Inter RAT handover and combined hard handover and SRNS relocation
procedures, or from source SGSN to the target SGSN over S16 interface as part of SRNS Relocation and PS handover
procedures.
A Forward Relocation Request message shall also be sent from the source MME to the target SGSN over S3 interface
as part of SRVCC from E-UTRAN to UTRAN or GERAN with DTM HO support procedures and from source SGSN
to the target SGSN over S16 interface as part of SRVCC from UTRAN (HSPA) to UTRAN or GERAN with DTM HO
support.
Forward Relocation procedure across S10 interface (when KASME is taken into use) shall be performed according to the
Rules on Concurrent Running of Security Procedures, which are specified in 3GPP TS 33.401 [12].
Table 7.3.1-1 specifies the presence requirements and conditions of the IEs in the message.
ETSI
Table 7.3.1-1: Information Elements in a Forward Relocation Request

elements
IMSI C The IMSI shall be included in the message except for the IMSI 0
case:
UICCless.
The IMSI shall be included in the message but not used as

an identifier
authenticated.
Sender's F-TEID for M F-TEID 0

Control Plane
MME/SGSN UE EPS C This IE shall be present, except over the S16 interface if PDN Connection 0
PDN Connections there is no active PDP context and the source and target
SGSNs supports SRNS relocation w/o PDN connection
over GTPv2 (see NOTE 2). Several IEs with this type and
instance values shall be included as necessary to
represent a list of PDN Connections
SGW S11/S4 IP C This IE shall be present, except over the S16 interface if F-TEID 1
Address and TEID for there is no active PDP context and the source and target
Control Plane SGSNs supports SRNS relocation w/o PDN connection
over GTPv2 (see NOTE 2).
SGW node name C This IE identifies the SGW that was used by the old FQDN 0
MME/S4-SGSN. It shall be included by the source
MME/S4-SGSN, except over the S16 interface if there is
no active PDP context and the source and target SGSNs
supports SRNS relocation w/o PDN connection over
GTPv2 (see NOTE 2).
MME/SGSN UE MM M MM Context 0
Context
Indication Flags C This IE shall be included if any of the flags are set to 1. Indication 0
- Direct Forwarding Indication: This flag shall be set
to 1 if direct forwarding is supported in the S1
based handover procedure. This flag shall not be
set to 1 if the message is used for other handover
procedures.
- Idle mode Signalling Reduction Supported

Indication flag: This flag shall be set to 1 if the
source MME/SGSN and associated SGW are
capable to establish ISR for the UE.

UE.
- Change Reporting support indication flag: This

flag shall be set to 1 if the Source S4-SGSN/MME
supports Location Change Reporting mechanism.
See NOTE1. See NOTE 3.
- CSG Change Reporting Support Indication flag:

This flag shall be set to 1 if the Source S4-
SGSN/MME supports CSG Information Change
Reporting mechanism. See NOTE1. See NOTE 3.
- Management Based MDT allowed flag: This flag

shall be set to 1 for the S1 based inter-MME
handover procedure over the S10 interface, if
Management Based Minimization of Drive Tests
(MDT) is allowed. See 3GPP TS 36.413 [10] and
3GPP TS 32.422 [18].
- CSFB Indication: when configured to support the
ETSI
return to the last used PLMN after CSFB, the

MME shall set this flag to 1 on the S3 interface if
the PS handover procedure is due to CSFB (see
subclause 4.3.2 of 3GPP TS 23.272 [21]). See
NOTE 5.
ETSI
E-UTRAN C This IE shall be included to contain the "Source to Target F-Container 0

Transparent Transparent Container", if the message is used for
Container UTRAN/GERAN to E-UTRAN inter RAT handover
procedure, E-UTRAN intra RAT handover procedure and
3G SGSN to MME combined hard handover and SRNS
relocation procedure. The Container Type shall be set to 3.
UTRAN Transparent C This IE shall be included to contain the "Source to Target F-Container 1
Container Transparent Container", if the message is used for PS
handover to UTRAN Iu mode procedures, SRNS relocation
procedure and E-TURAN to UTRAN inter RAT handover
procedure. The Container Type shall be set to 1.
BSS Container C This IE shall be included to contain the "Source BSS to F-Container 2
Target BSS Transparent Container" if the message is used
for PS handover to GERAN A/Gb mode and E-UTRAN to
GERAN A/Gb mode inter RAT handover procedure. The
Container Type shall be set to 2.
Target Identification C This IE shall be included if the message is used for SRNS Target 0
relocation procedure and handover to UTRAN/E-UTRAN Identification
procedures.
CO This IE shall be included on the S3 interface if the
message is used for PS handover from E-UTRAN to
GERAN A/Gb mode.
HRPD access node C This IE shall be included only if the HRPD pre registration IP-Address 0
S101 IP address was performed at the source MME
1xIWS S102 IP C This IE shall be included only if the 1xRTT CS fallback pre IP-Address 1
address registration was performed at the source MME
S1-AP Cause C This IE is the information received from the source F-Cause 0
eNodeB, and the source MME shall include this IE in the
message. Refer to the 3GPP TS 29.010 [42] for the
mapping of cause values between S1AP, RANAP and
BSSGP.
RANAP Cause C This IE is the information from the source RNC, the source F-Cause 1
SGSN shall include this IE in the message. Refer to the
3GPP TS 29.010 [42] for the mapping of cause values
between S1AP, RANAP and BSSGP.
BSSGP Cause C This IE is the information received from source BSS, and F-Cause 2
the source SGSN shall include this IE in the message.
Refer to the 3GPP TS 29.010 [42] for the mapping of
cause values between S1AP, RANAP and BSSGP.
Source Identification C This IE shall be included on the S16 interface if the Source 0
message is used for PS handover from GERAN/UTRAN to Identification
GERAN A/Gb mode.
Selected PLMN ID C The old MME/SGSN shall include this IE if the selected PLMN ID 0
PLMN identity is available. The Selected PLMN ID IE
indicates the target core network operator selected for the
UE in a shared network.
Recovery C If contacting the peer for the first time Recovery 0
Trace Information C This IE shall be included when session trace is active for Trace Information 0
this IMSI/IMEI.
Subscribed RFSP CO This IE shall be included during inter-MME/SGSN mobility RFSP Index 0
Index procedures, if the source MME/SGSN receives it from an
HSS.
RFSP Index in Use CO This IE shall be included only during inter-MME/SGSN RFSP Index 1
mobility procedures, if the source MME/SGSN supports the
feature.
CSG ID CO This IE shall be included on the S3/S10/S16 interfaces if CSG ID 0
the source MME/SGSN receives it from the source
eNodeB/RNC. It indicates the target CSG ID in case of a
handover to a CSG cell or hybrid cell.
CSG Membership CO This IE shall be included on the S3/S10/S16 interfaces by CMI 0
Indication the source MME/SGSN if the CSG access mode is
received from the source eNodeB/RNC and indicates the
target cell is a hybrid cell, or if the UE has emergency
bearer(s) and the target cell is a CSG cell.
UE Time Zone CO When available, this IE shall be included by the source UE Time Zone 0
MME/S4-SGSN.
Serving Network CO This IE shall be included to indicate the current Serving
Serving Network 0
Network.
ETSI
MME/S4-SGSN LDN O This IE is optionally sent by the MME/S4-SGSN to the peer Local 0
MME/S4-SGSN on the S3/S10/S16 interfaces (see 3GPP Distinguished
TS 32.423 [44]), when communicating the LDN to the peer Name (LDN)
Additional MM CO This IE shall be sent by the source MME/S4-SGSN to the Additional MM 0
context for SRVCC target MME/S4-SGSN on the S3/S10/S16 interfaces if MS context for
Classmark2, MS Classmark3 and the Supported Codec SRVCC
are available in the source MME/S4-SGSN.
Additional flags for CO This IE shall be included if any one of the applicable flags Additional flags 0
SRVCC needs to be forwarded. for SRVCC
Applicable flags:
- ICS Indicator: This IE shall be sent by the source
MME/S4-SGSN to the target MME/S4-SGSN on
the S3/S10/S16 interfaces if ICS Indicator is
available in the source MME/S4-SGSN.
- vSRVCC flag: This IE shall be sent by the source

MME to the target MME on the S10 interface if
vSRVCC flag is available in the source MME.
STN-SR CO This IE shall be sent by the source MME/S4-SGSN to the STN-SR 0

target MME/S4-SGSN on the S3/S10/S16 interfaces if
STN-SR is available in the source MME/S4-SGSN.
C-MSISDN CO This IE shall be sent by the source MME/S4-SGSN to the MSISDN 0
target MME/S4-SGSN on the S3/S10/S16 interfaces if C-
MSISDN is available in the source MME/S4-SGSN. The C-
MSISDN is defined in 3GPP TS 23.003 [2].
MDT Configuration CO This IE shall be sent by the source MME to the target MME MDT 0
on the S10 interface for the S1-based handover relocation Configuration
procedure, if the Job Type indicates Immediate MDT. See
3GPP TS 32.422 [18] subclause 4.2.6.
SGSN node name CO This IE shall be sent by the source SGSN on the S3 FQDN 1
interface if both source SGSN and associated SGW
support ISR. See NOTE 4.
MME node name CO This IE shall be sent by the source MME on the S3 FQDN 2
interface if both source MME and associated SGW support
ISR. See NOTE 4.
User CSG CO This IE shall be sent by the source MME/S4-SGSN on the UCI 0
Information (UCI) S3/S10/S16 interfaces if the source MME/SGSN has
reported to the PGW that the UE is in a CSG or hybrid cell.
It shall then contain the last User CSG information that the
source MME/S4-SGSN has reported to the PGW.
The absence of this IE indicates that the UE has not been
reported to the PGW as being in a CSG or hybrid cell.
See NOTE 6.
Monitoring Event CO This IE shall be sent by the source MME/S4-SGSN on the Monitoring Event 0
Information S3/S10/S16 interfaces if monitoring events are to be Information
continued in the target MME/S4-SGSN.
be included to represent multiple monitoring events.
UE Usage Type CO This IE shall be sent by the old MME/SGSN on the Integer Number 0
S3/S10/S16 interfaces if the old MME/SGSN supports the
Dedicated Core Networks specified in TS 23.401 [3].
If the UE Usage Type is not available in the old
MME/SGSN, the length field of this IE shall be set to 0.
See NOTE 7.
NOTE 2: GTPv2 shall be used for SRNS relocation w/o PDN connection if all the S4-SGSNs (between which
SRNS relocation can take place) support this optional GTPv2 procedure. Otherwise GTPv1 shall be
used for that procedure (see subclause 7.10). The S4-SGSN can know by local configuration
whether all peer S4-SGSNs support this procedure.
NOTE 3: The receiver shall ignore the per UE Change Reporting Support Indication and CSG Change
Reporting Support Indication flags, as included within the Indication Flags IE above, if these flags are
ETSI
included per PDN connection i.e. within the Indication Flags IE of the MME/SGSN UE EPS PDN
Connections IE.
NOTE 4: According to the 3GPP TS 23.401 [3], during an inter-RAT handover procedure for a UE with ISR
activated, the source MME/SGSN should select the ISR associated CN node for this UE as the target
CN node for the inter RAT HO when the ISR associated CN node can serve the target access. This
parameter is exchanged when ISR is being activated and used in the source MME/SGSN for this
decision upon subsequent inter-RAT handover.
NOTE 5: If the SGSN needs to include the last used LTE PLMN ID in the Equivalent PLMN list it sends to the
UE (see 3GPP TS 23.272 [21]), the SGSN shall derive the last used LTE PLMN ID from the Serving
Network IE.
NOTE X: A UE Usage Type IE with the length field equal to 0 is used for the receiver to differentiate the case
where the sender does not support the Dedicated Core Network feature from the case where the
sender supports the Dedicated Core Network feature but no UE Usage type was received in UE's
subscription.
The PDN Connection grouped IE shall be coded as depicted in Table 7.3.1-2.
ETSI
Table 7.3.1-2: MME/SGSN UE EPS PDN Connections within Forward Relocation Request
Octet 1 PDN Connection IE Type = 109 (decimal)

elements
APN M APN 0
Context. The target MME or SGSN determines the
Maximum APN Restriction using the APN Restriction.
If available, the source MME/S4SGSN shall include this IE.
Selection Mode CO When available, this IE shall be included by the source Selection Mode 0
MME/S4-SGSN
IPv4 Address C This IE shall not be included if no IPv4 Address is IP Address 0
assigned. See NOTE 1.
assigned.
Linked EPS Bearer ID M This IE identifies the default bearer of the PDN EBI 0
Connection.
PGW S5/S8 IP M This IE shall include the TEID in the GTP based S5/S8 F-TEID 0
Address for Control case and the uplink GRE key in the PMIP based S5/S8
Plane or PMIP case.
See NOTE 4.
PGW node name C This IE shall be included if the source MME or SGSN has FQDN 0
the PGW FQDN.
Bearer Contexts C Several IEs with this type and instance values may be Bearer Context 0
Aggregate Maximum M AMBR 0
Bit Rate (APN-AMBR)
Charging C This IE shall be present if charging characteristics was Charging 0
characteristics supplied by the HSS to the MME/SGSN as a part of characteristics
subscription information.
Change Reporting C This IE shall be included whenever available at the source Change Reporting 0
Action MME/SGSN. See NOTE 5. Action
CSG Information CO This IE shall be included whenever available at the source CSG Information 0
Reporting Action MME/SGSN. Reporting Action
H(e)NB Information CO This IE shall be included whenever available at the source H(e)NB 0
Reporting MME/SGSN. Information
Reporting
Indication Flags CO This IE shall be included if any of the flags are set to 1. Indication 0
- Change Reporting support indication flag: This
flag shall be set to 1 if the Source S4-SGSN/MME
supports Location Change Reporting mechanism
and if the S4-SGSN/MME has indicated the
support for the Location Change Reporting
mechanism to the PGW, during the session
establishment and/or modification procedures.
See NOTE 2.

Reporting mechanism and if the S4-SGSN/MME
has indicated the support for the CSG Informatoin
Change Reporting to the PGW, during the
session establishment and/or modification
procedures. See NOTE 2.
- Delay Tolerant Connection Indication flag: This

flag shall be set to 1 on the S3/S10/S16 interface
by the source MME/SGSN if the PGW indicated
that this PDN Connection is delay tolerant.
Signalling Priority CO The source SGSN/MME shall include this IE if the UE Signalling Priority 0
Indication indicated low access priority when establishing the PDN Indication
connection.
ETSI
Change to Report CO This IE shall be included by the SGSN if any one of the Change to Report 0
Flags applicable flags is set to 1. See NOTE3. Flags
Applicable flags:
- Serving Network Change to Report: This flag shall
be set to 1 if the source SGSN has detected a
Serving Network change during a RAU procedure
without SGSN change but has not yet reported this
change to the PGW.
- Time Zone Change to Report: This flag shall be set

to 1 if the source SGSN has detected a UE Time
Zone change during a RAU procedure without
SGSN change but has not yet reported this change
to the PGW .
Local Home Network CO This IE shall be sent over the S3/S10/S16 interface if FQDN 1
ID SIPTO at the Local Network is active for the PDN
connection in the SIPTO at the Local Network architecture
with stand-alone GW.
Presence Reporting CO This IE shall be included if the PGW requested the source Presence 0
Area Action MME/SGSN to report changes of UE presence in a Reporting Area
Presence Reporting Area. The source MME/SGSN shall Action
include the Presence Reporting Area Identifier and, if
received from the PGW, the list of the Presence Reporting
Area elements.
WLAN Offloadability CO If the MME/SGSN supports WLAN/3GPP Radio WLAN 0
Indication Interworking with RAN rules then this IE shall be included Offloadability
on S3/S10/S16 if the UE has been authorized to perform Indication
WLAN offload for at least one RAT .
Remote UE Context CO The source MME shall include this IE on the S10 interface Remote UE 0
Connected during an inter MME mobility procedure if such information Context
is available.
connected.
NOTE 1: For deferred IPv4 address allocation, if the MME/S4-SGSN receives the PDN address "0.0.0.0" from
PGW during "eUTRAN Initial Attach", "PDP Context Activation", "UE requested PDN Connectivity",
then the MME/S4-SGSN shall include this IPv4 address "0.0.0.0".
NOTE 3: When UE is camping on the 3G and performs a Service Request procedure, as specified in the
subclause 6.12.1 of 3GPP TS 23.060 [35], if Service Type indicates Signalling, the signalling
connection is established between the MS and the SGSN for sending upper-layer signalling
messages, e.g. Activate PDP Context Request, but the resources for active PDP context(s) are not
allocated, therefore the change of Serving Network or UE Time zone may not be reported to
SGW/PGW for the existing PDP Contexts.
NOTE 4: For PMIP based S5/S8, the 'PGW S5/S8 IP Address and TEID for user plane' IE and the 'PGW
S5/S8 IP Address for Control Plane or PMIP' IE shall contain the same uplink GRE key; the Interface
Type in these IEs shall be set to the value 9 (S5/S8 PGW PMIPv6 interface).
NOTE 5: The target MME (respectively S4-SGSN) shall ignore this IE if it is received from an S4-SGSN
(respectively an MME), i.e. over the S3 interface. In this case, the target serving node shall consider
that no ULI change reporting is requested by the PGW for the target RAT, and the PGW shall
request the target serving node to start ULI change reporting for the target RAT if so desired.
The Bearer Context grouped IE shall be coded as depicted in Table 7.3.1-3.
ETSI
Table 7.3.1-3: Bearer Context within MME/SGSN UE EPS PDN Connections within Forward Relocation
Request

elements
TFT C This IE shall be present if a TFT is defined for this bearer. Bearer TFT 0
SGW S1/S4/S12 IP M F-TEID 0
Address and TEID for
user plane
PGW S5/S8 IP C This IE shall be present for GTP based S5/S8 F-TEID 1
Address and TEID for CO For PMIP-based S5/S8, this IE shall be included if the
user plane PGW provided an alternate address for user plane, i.e. an
See NOTE 1.
BSS Container CO The MME/S4 SGSN shall include the Packet Flow ID, F-Container 0
Radio Priority, SAPI, PS Handover XID parameters in the
TAU/RAU/Handover procedure, if available. See Figure
8.48-2. The Container Type shall be set to 2.
Transaction Identifier C This IE shall be sent over S3/S10/S16 if the UE supports TI 0
A/Gb and/or Iu mode.
Bearer Flags CO Applicable flags: Bearer Flags 0
- vSRVCC indicator: This IE shall be sent by the
source MME to the target MME on the S10
interface if vSRVCC indicator is available in the
source MME.
- ASI (Activity Status Indicator): the source S4-

SGSN shall set this indicator to 1 on the S16
interface if the bearer context is preserved in the
CN without an associated RAB.
Table 7.3.1-4: Remote UE Context Connected within MME/SGSN UE EPS PDN Connections within
Forward Relocation Request

elements
parameter
7.3.2 Forward Relocation Response

A Forward Relocation Response message shall be sent as a response to Forward Relocation Request during S1-based
handover procedure, Inter RAT handover procedures, SRNS Relocation procedure and PS handover procedures.
ETSI
Cause IE indicates if the relocation has been accepted, or not. The relocation has not been accepted by the target
MME/SGSN if the Cause IE value differs from "Request accepted". Possible Cause values are specified in Table 8.4-1.
Message specific cause values are:
- "Relocation failure".
ETSI
Table 7.3.2-1: Information Elements in a Forward Relocation Response

elements
Cause M Cause 0
Sender's F-TEID for C If the Cause IE contains the value "Request accepted", the F-TEID 0
Control Plane target MME/SGSN shall include this IE in Forward
Relocation Response message.
SGW Change Indication:
- This flag shall be set to 1 if the target MME/SGSN
has selected a new SGW.
List of Set-up Bearers C The list of set-up Bearers IE contains the EPS bearer Bearer Context 0
Identifiers of the Bearers that were successfully allocated
in the target system during a handover procedure. This IE
shall be included if the source and target access type is
EUTRAN and the Cause IE contains the value "Request
accepted".
See NOTE 1.
List of Set-up RABs C The list of set-up RABs IE contains the RAB Identifiers of Bearer Context 1
the RABs that were successfully allocated in the target
system. This IE shall be included if the Cause IE contains
the value "Request accepted" and
- If the source access type is UTRAN and the
target access type is E-UTRAN/UTRAN,
- If the source access type is E-UTRAN and the
target access type is UTRAN,
except over the S16 interface if the Forward Relocation
Request did not include the MME/SGSN UE EPS PDN
Connections IE.
See NOTE 1.
List of Set-up PFCs O The list of set-up PFCs IE contains the Packet Flow Bearer Context 2
Identifies of the PFCs that were successfully allocated in
the target system during a PS handover to/from GERAN or
inter RAT handover to/from GERAN. If the Cause IE
contains the value "Request accepted", this IE may be
included.
See NOTE 1.
S1-AP Cause C This IE is included if cause value is contained in S1-AP F-Cause 0
BSSGP.
RANAP Cause C This IE is included if cause value is contained in RANAP F-Cause 1
BSSGP.
BSSGP Cause C For handover to GERAN, if a cause value is received from F-Cause 2
the Target BSC, the BSSGP Cause IE shall be included
and shall be set to the cause value received from the
target BSC. Refer to the 3GPP TS 29.010 [42] for the
BSSGP.
E-UTRAN C This IE shall be included to contain the "Target to Source F-Container 0
Transparent Transparent Container" during a handover to E-UTRAN. If
Container the Cause IE contains the value "Request accepted". The
UTRAN Transparent C This IE shall be included to contain the "Target to Source F-Container 1
Container Transparent Container" during a handover to UTRAN. If
the Cause IE contains the value "Request accepted". The
BSS Container C This IE shall be included to contain the Target BSS to F-Container 2
ETSI
Source BSS Transparent Container during a handover to

GERAN. If the Cause IE contains the value "Request
accepted". The Container Type shall be set to 2
SGSN node name CO This IE shall be sent by the target SGSN on the S3 FQDN 0
interface if both target SGSN and associated SGW support
ISR. See NOTE 2.
MME node name CO This IE shall be sent by the target MME on the S3 interface FQDN 1
if both target MME and associated SGW support ISR. See
NOTE 2.
SGSN Number O This IE may be sent by the target S4-SGSN to the source Node Number 0
SGSN Identifier O This IE may be sent by the target S4-SGSN to the source Node Identifier 0
MME Identifier O This IE may be sent by the target MME to the source Node Identifier 1
NOTE 1: In the Forward Relocation Request message, the inclusion of "RAN Cause" indicates that the source
access type is E-UTRAN. In the Forward Relocation Request message, the inclusion of "RANAP
Cause" indicates that the source access type is UTRAN. In the Forward Relocation Request
message, the inclusion of "BSSGP Cause" indicates that the source access type is GERAN.
Bearer Context IE in this message is specified in Table 7.3.2-2, the source system shall use this IE for data forwarding
in handover.
ETSI
Table 7.3.2-2: Bearer Context

elements
EPS Bearer ID C This IE shall be included if the message is used for S1- EBI 0
Based handover procedure.
This IE shall be included if the message is used for SRNS
relocation procedure and Inter RAT handover to/from Iu
mode procedures.
Packet Flow ID C This IE shall be included if the message is used for PS Packet Flow ID 0
handover and Inter RAT handover to/from A/Gb mode
procedures.
eNodeB F-TEID for C This IE shall be included for the message sent from the F-TEID 0
DL data forwarding target MME, if the DL Transport Layer Address and DL
GTP TEID are included in the "SAE Bearers Admitted List"
of the S1AP: HANDOVER REQUEST ACKNOWLEDGE
and direct forwarding or indirect forwarding without SGW
change is applied.
eNodeB F-TEID for O This IE may be included for the message sent from the F-TEID 1
UL data forwarding target MME during the intra-EUTRAN HO, if the UL
Transport Layer Address and UL GTP TEID are included in
the "SAE Bearers Admitted List" of the S1AP: HANDOVER
REQUEST ACKNOWLEDGE and direct forwarding or
indirect forwarding without SGW change is applied.
SGW F-TEID for DL C This SGW F-TEID shall be included when indirect data F-TEID 2
data forwarding forwarding with SGW change is applied.
RNC F-TEID for DL C This RNC F-TEID shall be included in the message sent F-TEID 3
data forwarding from SGSN, if the target system decides using RNC F-
TEID for data forwarding.
SGSN F-TEID for DL C This SGSN F-TEID shall be included in the message sent F-TEID 4
data forwarding from SGSN, if the target system decides using SGSN F-
TEID for data forwarding.
SGW F-TEID for UL O If available this SGW F-TEID may be included when F-TEID 5
data forwarding indirect data forwarding with SGW change is applied,
during the intra-EUTRAN HO.
7.3.3 Forward Relocation Complete Notification

A Forward Relocation Complete Notification message shall be sent to the source MME/SGSN to indicate the handover
has been successfully finished.
Table 7.3.3-1: Information Elements in a Forward Relocation Complete Notification

elements
Idle mode Signalling Reduction Activation Indication: This
flag shall be set to 1 if the message is used for inter RAT
handover and the UE has ISR capability. This flag is set to
indicate to the source MME/SGSN whether it shall
maintain the UE's context and whether it shall activate ISR.
7.3.4 Forward Relocation Complete Acknowledge

A Forward Relocation Complete Acknowledge message shall be sent as a response to Forward Relocation Complete
Notification during inter eNodeB handover with MME relocation procedure, SRNS Relocation with SGSN change
procedures using S4 or Inter RAT Handover with MME/S4 SGSN interaction procedures.
ETSI
Table 7.3.4-1: Information Elements in a Forward Relocation Complete Acknowledge

elements
Cause M Cause 0
7.3.5 Context Request

The new MME/SGSN shall send the Context Request message to the old MME/SGSN on S3/S16/S10 interface as a
part of TAU/RAU procedure and UTRAN/GERAN to E-UTRAN/UTRAN (HSPA) SRVCC procedure to get the MM
and EPS bearer Contexts for the UE.
NOTE 1: During UTRAN/GERAN to E-UTRAN/UTRAN (HSPA) SRVCC procedure as specified in 3GPP TS

23.216 [43], the GUTI, RAI IE, P-TMSI IE and P-TMSI Signature IE, are not received directly from the
UE but from the MSC Server over Sv interface.
If the sending/new node is a MME, it shall include in the Context Request message:
- the GUTI IE and Complete TAU Request Message IE, if the GUTI or the indication of mapped or native GUTI
received from UE indicates the old node is a MME, as specified in subclause 2.8.2.2.2 of 3GPP TS 23.003 [2].
- the RAI IE and the P-TMSI IE, which are derived from the GUTI received from UE, and the P-TMSI Signature
that was received intact from the UE, if the GUTI or the indication of mapped or native GUTI indicates the old
node is an SGSN as specified in subclause 2.8.2.2.2 of 3GPP TS 23.003 [2].
If the sending/new node is an SGSN, it shall include RAI IE, P-TMSI IE and P-TMSI Signature IE in the Context
Request message. If the receiving/old node is an MME, it shall construct GUTI according to the RAI IE, P-TMSI IE
and P-TMSI Signature IE (see the mapping relationship between RAI, P-TMSI, P-TMSI signature and GUTI defined in
3GPP TS23.003[2]), and find UE context via this GUTI.
The new MME differentiates the type of the old node as specified in subclause 2.8.2.2.2 of 3GPP TS 23.003 [2]. If the
old node is an SGSN, the GUTI shall be mapped to RAI and P-TMSI by the new MME; if the old node is a MME, the
new MME include GUTI IE and Complete TAU Request Message IE in the Context Request message. The Mapping
between temporary and area identities is defined in 3GPP TS 23.003 [2].
The Target PLMN ID IE shall be used in old SGSN/MME in order to decide whether un-used authentication vectors to
be distributed to new SGSN/MME or not. Distribution and use of authentication vectors between different serving
network domains are specified in 3GPP TS 33.401 [12].
ETSI
Table 7.3.5-1: Information Elements in a Context Request

elements
IMSI C IMSI shall be included if the UE has been successfully IMSI 0
authenticated.
C The New MME shall include this IE over S10 interface.
CO This IE shall be included over S10 interface if available
GUTI GUTI 0
during UTRAN/GERAN to E-UTRAN/UTRAN (HSPA)
SRVCC procedure as specified in 3GPP TS 23.216 [43].
C This IE shall be included over S3/S16 interface, if the GUTI
or the indication of mapped or native GUTI indicates the
old node is an SGSN, the new MME maps this IE from
Routeing Area
GUTI. ULI (NOTE 4) 0
Identity(RAI)
CO This IE shall be included over S3/S16 interface if available
C This IE shall be included over S3/S16 interface. For the S3
interface, if sent by the MME, this IE is derived by the MME
from the GUTI received from the UE.
Packet TMSI(P-TMSI) P-TMSI 0
CO This IE shall be included over S3/S16 interface if available
C This IE shall be included over S3/S16 interface if it is
received from the UE.
P-TMSI Signature CO This IE shall be included over S3/S16 interface if available P-TMSI Signature 0
Complete TAU C The new MME shall include this IE if available, and the old Complete 0
request message MME may use this IE for integrity check. See NOTE 3. Request Message
S3/S16/S10 Address C This IE specifies the address and the TEID for control F-TEID 0
and TEID for Control plane message which is chosen by the new MME/SGSN.
Plane In case of SGSN pool, the IPv4 or the IPv6 address field
shall be set to the same value of the Source IP address of
the IP packet carrying this message, and the relaying
SGSN shall not change the content of this IE when
sending it to the old SGSN. See NOTE 1.
UDP Source Port C If an SGSN within the same SGSN pool as the old SGSN Port Number 0
Number receives this message, the SGSN shall include the UDP
Source Port number of the received message in this
parameter if this IE is not present and relay the message to
the old SGSN. The old SGSN shall use this UDP port as
the UDP destination port of the Context Response
message.
RAT Type C The RAT Type indicates the Radio Access Technology RAT Type 0
which is used in the new system.
Indication CO his IE shall be included if any one of the applicable flags is Indication 0
set to 1.
Applicable Flags are:
- The MS Validated (MSV) flag, when set to 1,
indicates that the new system has successfully
authenticated the UE, or the new system has
validated the integrity protection of the TAU request
message. See NOTE 3.
Hop Counter O If an SGSN within the same SGSN pool with the old SGSN Hop Counter 0
receives this message, the SGSN shall decrement the Hop
Counter if this IE is present in the received message;
otherwise, the SGSN may include a Hop Counter with a
value of max-1, and may relay the message to the old
SGSN.
Target PLMN ID CO If available, this IE shall be included in order to allow old Serving Network 0
MME/SGSN to make a judgment whether un-used
authentication vectors to be distributed or not.
ETSI
SGSN node name CO This IE shall be sent by the new SGSN on the S3 interface FQDN 0
if both new SGSN and associated SGW support ISR. See
NOTE 2.
MME node name CO This IE shall be sent by the new MME on the S3 interface if FQDN 1
both new MME and associated SGW support ISR. See
NOTE 2.
SGSN Number O This IE may be sent by the target S4-SGSN to the source Node Number 0
SGSN Identifier O This IE may be sent by the target S4-SGSN to the source Node Identifier 0
MME Identifier O This IE may be sent by the target MME to the source Node Identifier 1
NOTE 1: The relaying SGSN shall forward the Context Request message to the interface of the old SGSN,
where the interface type is matching what is indicated in the IE S3/S16/S10 Address and TEID for
Control Plane.
NOTE 3: The Complete TAU request message IE is available except during UTRAN/GERAN to E-
UTRAN/UTRAN (HSPA) SRVCC procedure as specified in 3GPP TS 23.216 [43]. In these
procedures, the new MME shall set the Indication IE MSV (MS Validated) flag to 1.
NOTE 4: Only RAI field in the ULI IE type shall be present in the Routeing Area Identity (RAI) IE.
7.3.6 Context Response

A Context Response message shall be sent as a response to a previous Context Request message during TAU/RAU
procedure and UTRAN/GERAN to E-UTRAN/UTRAN (HSPA) SRVCC procedure.
- "IMSI/IMEI not known"
- "P-TMSI Signature mismatch"
- "User authentication failed"
- "Target access restricted for the subscriber"
Based on the subscription profile, when the access to the target RAT is prohibited for the subscriber, the old
MME/SGSN may reject the Context Request message with the cause "Target access restricted for the subscriber".
ETSI
Table 7.3.6-1: Information Elements in a Context Response

elements
Cause M Cause 0
case:
UICCless.

an identifier
authenticated.
MME/SGSN UE MM C This IE shall be included if the Cause IE has the value " MM Context 0
Context Request Accepted ".
MME/SGSN UE EPS C This IE shall be included if there is at least a PDN PDN Connection 0
PDN Connections connection for this UE on the sending MME/SGSN.
included as necessary to represent a list of PDN
Connections.
Sender F-TEID for C This IE shall be included if the Cause IE has the value F-TEID 0
Control Plane "Request Accepted".
SGW S11/S4 IP C This IE shall be included if a SGW is being used by the old F-TEID 1
Address and TEID for MME/SGSN, except if:
Control Plane - the source and target MME/S4-SGSN support the
MME/S4-SGSN triggered SGW restoration
procedure, and the source MME/S4-SGSN has not
performed the SGW relocation procedure after the
source SGW has failed as specified in 3GPP TS
23.007 [17].
- across the S16 interface if there is no active PDP
context
SGW node name C This IE identifies the SGW that was used by the old FQDN 0
MME/SGSN and it shall be included by the source
MME/S4-SGSN with the following exceptions:
- the source and target MME/S4-SGSN support the
MME/S4-SGSN triggered SGW restoration
source SGW has failed as specified in 3GPP TS
23.007 [17].
- across the S16 interface if there is no active PDP
context
Idle mode Signalling Reduction Supported Indication:

- This flag shall be set to 1 if the Cause IE value
indicates "Request accepted" and the old system
(including old MME/SGSN and the associated
SGW) has the ISR capability.
Unauthenticated IMSI:
- This flag shall be set to 1 if the IMSI present in the
message is not authenticated and is for an
emergency attached UE.
Change Reporting support indication flag:

- This flag shall be set to 1 if the Source S4-
SGSN/MME supports Location Change Reporting
mechanism. See NOTE 1. See NOTE 2.
CSG Change Reporting support indication flag:

- This flag shall be set to 1 if the Source S4-
Reporting mechanism. See NOTE 1. See NOTE 2.
ISRAU:
ETSI
- This flag shall be set to 1 on S10/S16 interface if

the ISR is activated for the UE before the UE
moving to the new SGSN/MME.
Management Based MDT allowed flag:

- This flag shall be set to 1 for the inter-MME TAU
procedure over the S10 interface, if Management
Based Minimization of Drive Tests (MDT) is
allowed. See 3GPP TS 36.413 [10] and 3GPP TS
32.422 [18].
SGW Restoration Needed Indication (SRNI):

- This flag shall be set to 1 if both source and target
MME/S4-SGSN support the MME/S4-SGSN
triggered SGW restoration procedure and the
source MME/S4-SGSN has not performed the
SGW relocation procedure after the source SGW
has failed as specified in 3GPP TS 23.007 [17].
CSFB Indication (CSFBI):

- when configured to support the return to the last
used PLMN after CSFB, the MME shall set this
flag to 1 on the S3 interface if the UE has been
subject to CSFB recently (see subclause 4.3.2 of
3GPP TS 23.272 [21]). See NOTE 4.
Buffered DL Data Waiting Indication (BDWI):

- This flag shall be set to 1 on the S3/S10/S16
interface, during TAU/RAU with or without SGW
change procedures, when it is required to forward
to the UE DL data buffered in the (old) SGW, i.e.
when the DL Data Buffer Expiration Time has not
expired yet in the old MME/SGSN, as specified in
ETSI
Trace Information C This IE shall be included when session trace is active for Trace Information 0
this IMSI/IMEI.
HRPD access node C This IE shall be included only if the HRPD pre registration IP-Address 0
S101 IP address was performed at the old MME
1xIWS S102 IP C This IE shall be included only if the 1xRTT CS fallback pre IP-Address 1
address registration was performed at the old MME
Subscribed RFSP CO This IE shall be included only during inter-MME/SGSN RFSP Index 0
Index mobility procedures, if the source MME/SGSN receives it
from an HSS.
RFSP Index in Use CO This IE shall be included only during inter-MME/SGSN RFSP Index 1
mobility procedures, if the source MME/SGSN supports the
feature.
UE Time Zone CO When available, this IE shall be included by the source UE Time Zone 0
MME/S4-SGSN.
MDT Configuration CO This IE shall be sent by the source MME to the target MME MDT 0
on the S10 interface for inter-MME TAU procedure, if the Configuration
Job Type indicates Immediate MDT. See 3GPP TS 32.422
[18] subclause 4.2.6.
SGSN node name CO This IE shall be sent by the old SGSN on the S3 interface if FQDN 1
both old SGSN and associated SGW support ISR. See
NOTE 3.
MME node name CO This IE shall be sent by the old MME on the S3 interface if FQDN 2
both old MME and associated SGW support ISR. See
NOTE 3.
User CSG CO This IE shall be sent by the source MME/S4-SGSN on the UCI 0
Information (UCI) S3/S10/S16 interfaces if the source MME/SGSN has
reported to the PGW that the UE is in a CSG or hybrid cell.
It shall then contain the last User CSG information that the
source MME/S4-SGSN has reported to the PGW.
The absence of this IE indicates that the UE has not been
reported to the PGW as being in a CSG or hybrid cell.
See NOTE 5.
Dedicated Core Networks feature specified in TS 23.401
[3].
See NOTE 6.
NOTE 2: The receiver shall ignore the per UE Change Reporting Support Indication and CSG Change
Reporting Support Indication flags, as included within the Indication Flags IE above, if these flags are
included per PDN connection i.e. within the Indication Flags IE of the MME/SGSN UE EPS PDN
Connections IE.
NOTE 4: If the SGSN needs to include the last used LTE PLMN ID in the Equivalent PLMN list it sends to the
UE (see 3GPP TS 23.272 [21]), the SGSN shall derive the last used LTE PLMN ID from the Old RAI
IE received in the RAU request message.
ETSI
NOTE 6: A UE Usage Type IE with the length field equal to 0 is used for the receiver to differentiate the case
subscription.
ETSI
Table 7.3.6-2: MME/SGSN UE EPS PDN Connections within Context Response

elements
APN M APN 0
Context. The target MME or SGSN determines the
Maximum APN Restriction using the APN Restriction.
If available, the source MME/S4 SGSN shall include this
IE.
Selection Mode CO When available, this IE shall be included by the source Selection Mode 0
MME/S4-SGSN
assigned. See NOTE 1.
assigned.
Linked EPS Bearer ID M This IE identifies the default bearer of the PDN EBI 0
Connection.
PGW S5/S8 IP M This IE shall include the TEID in the GTP based S5/S8 F-TEID 0
Address for Control case and the uplink GRE key in the PMIP based S5/S8
Plane or PMIP case.
See NOTE 3.
PGW node name C This IE shall be included if the source MME or SGSN has FQDN 0
the PGW FQDN.
Bearer Contexts M Several IEs with this type and instance values may be Bearer Context 0
Aggregate Maximum M AMBR 0
Bit Rate (APN-AMBR)
Charging C This IE shall be present if charging characteristics was Charging 0
characteristics supplied by the HSS to the MME/SGSN as a part of characteristics
subscription information.
Change Reporting C This IE shall be included whenever available at the source Change Reporting 0
Action MME/SGSN. See NOTE 4. Action
CSG Information CO This IE shall be included whenever available at the source CSG Information 0
Reporting Action MME/SGSN. Reporting Action
H(e)NB Information CO This IE shall be included whenever available at the source H(e)NB 0
Reporting MME/SGSN. Information
Reporting
Indication flags CO This IE shall be included if any one of the applicable flags Indication 0
is set to 1.
Applicable flags:
- Subscribed QoS Change Indication: This flag shall
be set to 1 if the subscribed QoS profile of the
related PDN connection has changed in the old
MME/SGSN when the UE is in ECM-IDLE state
and ISR is activated.
- Change Reporting support indication flag: This flag

shall be set to 1 if the Source S4-SGSN/MME
supports Location Change Reporting mechanism
and if the S4-SGSN/MME has indicated the
support for the Location Change Reporting
mechanism to the PGW, during the session
establishment and/or modification procedures. See
NOTE 2.

Reporting mechanism and if the S4-SGSN/MME
has indicated the support for the CSG Information
Change Reporting to the PGW, during the session
establishment and/or modification procedures. See
ETSI
NOTE 2.
- Pending Subscription Change Indication flag: This

flag shall be set to 1 on the S3/S10 interface if the
source MME has received Subscribed QoS profile
updates for QCI/ARP/APN-AMBR from the HSS
but has deferred the reporting of these updates to
the PGW/PCRF because the UE was not
reachable.
- Pending Network Initiated PDN Connection

Signalling Indication flag: This flag shall be set to 1
on the S3/S10/S16 interface by the source
MME/SGSN if there is pending network initiated
signalling for the PDN connection.
- Delay Tolerant Connection Indication flag: This flag

shall be set to 1 on the S3/S10/S16 interface by
the source MME/SGSN if the PGW indicated that
this PDN Connection is delay tolerant.
ETSI
Signalling Priority CO The source SGSN/MME shall include this IE if the UE Signalling Priority 0
Indication indicated low access priority when establishing the PDN Indication
connection.
Change to Report CO This IE shall be included by the MME/SGSN if any one of Change To 0
Flags the applicable flags is set to 1. Report Flags
Applicable flags:
- Serving Network Change to Report: This flag shall
be set to 1 if the source MME/SGSN has detected
a Serving Network change during a TAU/RAU
procedure without MME/SGSN change but has not
yet reported this change to the PGW.
- Time Zone Change to Report: This flag shall be set

to 1 if the source MME/SGSN has detected a UE
Time Zone change during a TAU/RAU procedure
without MME/SGSN change but has not yet
reported this change to the PGW .
Local Home Network CO This IE shall be sent over the S3/S10/S16 interface if FQDN 1
ID SIPTO at the Local Network is active for the PDN
connection in the SIPTO at the Local Network architecture
with stand-alone GW.
Presence Reporting CO This IE shall be included if the PGW requested the source Presence 0
Area Action MME/SGSN to report changes of UE presence in a Reporting Area
Presence Reporting Area. The source MME/SGSN shall Action
include the Presence Reporting Area Identifier and, if
received from the PGW, the list of the Presence Reporting
Area elements.
WLAN Offloadability CO If the MME/SGSN supports WLAN/3GPP Radio WLAN 0
Indication Interworking with RAN rules then this IE shall be included Offloadability
on S3/S10/S16 if the UE has been authorized to perform Indication
WLAN offload for at least one RAT.
Remote UE Context CO The source MME shall include this IE on the S10 interface Remote UE 0
Connected during an inter MME mobility procedure if such information Context
is available.
connected.
NOTE 1: For deferred IPv4 address allocation, if the MME/S4-SGSN receives the PDN address "0.0.0.0" from
PGW during "eUTRAN Initial Attach", "PDP Context Activation", "UE requested PDN Connectivity",
then the MME/S4-SGSN shall include this IPv4 address "0.0.0.0".
NOTE 4: The target MME (respectively S4-SGSN) shall ignore this IE if it is received from an S4-SGSN
(respectively an MME), i.e. over the S3 interface. In this case, the target serving node shall consider
that no ULI change reporting is requested by the PGW for the target RAT, and the PGW shall
request the target serving node to start ULI change reporting for the target RAT if so desired.
The Bearer Context shall be coded as depicted in Table 7.3.6-3.
ETSI
Table 7.3.6-3: Bearer Context within MME/SGSN UE EPS PDN Connections within Context Response
Octet 1 Bearer Context IE Type = 93

Octet 4 Sparae and Instance fields
elements
TFT C This IE shall be present if a TFT is defined for this bearer. Bearer TFT 0
SGW S1/S4/S12 IP C The IE shall be present except if: F-TEID 0
Address and TEID for - the source and target MME/S4-SGSN support the
user plane MME/S4-SGSN triggered SGW restoration
SGW has failed as specified in 3GPP TS 23.007
[17].
PGW S5/S8 IP C This IE shall be included for GTP based S5/S8. F-TEID 1
Address and TEID for CO For PMIP-based S5/S8, this IE shall be included if the
user plane PGW provided an alternate address for user plane, i.e. an
See NOTE 1.
BSS Container CO The MME/S4 SGSN shall include the Packet Flow ID, F-Container 0
Radio Priority, SAPI, PS Handover XID parameters in the
TAU/RAU/Handover procedure, if available. The Container
Type shall be set to 2.
Transaction Identifier C This IE shall be sent over S3/S10/S16 if the UE supports TI 0
A/Gb and/or Iu mode.
Table 7.3.6-4: Remote UE Context Connected within MME/SGSN UE EPS PDN Connections within
Context Response

elements
parameter
7.3.7 Context Acknowledge

A Context Acknowledge message shall be sent as a response to a previous Context Response message, only if the
previous Context Response message is received with the acceptance cause.
Possible cause values are specified in Table 8.4-1. Message specific cause values are:
- "User authentication failed".
- "Relocation failure due to NAS message redirection".
Upon receiving cause value other than the request was accepted, the old MME/S4-SGSN shall continue as if the
Context Request was never received.
ETSI
Table 7.3.7-1: Information Elements in a Context Acknowledge

elements
Cause M Cause 0
Indication flags C This IE shall be included if any one of the applicable flags Indication 0
is set to 1.
Applicable Flags are:
- SGW Change Indication: This flag shall be set to 1
on the S3/S10/S16 interfaces if a new SGW has
been selected. The old MME/old SGSN marks in
its context that the information in the GWs and the
HSS are invalid.
- Idle mode Signalling Reduction Activation

Indication: If set to 1, this flag indicates to the old
system that it shall maintain the UE's contexts.
This flag shall be set to 1 on the S3 interface if the
Cause IE value indicates "Request accepted" and
ISR is activated as specified in 3GPP TS 23.401
[3].
See NOTE1.
Forwarding F-TEID CO This IE shall be included when data forwarding of DL data F-TEID 0
buffered in the old SGW is required, i.e. when the BDWI
flag is set in the Context Response message and the SGW
is changed, during TAU/RAU procedure with SGW change
and data forwarding as specified in the subclause 5.3.3.1A
of 3GPP TS 23.401 [3].
The interface type of the Forwarding F-TEID should be set
to either:
- 23 ("SGW GTP-U interface for DL data
forwarding") for indirect forwarding,
- 0 (" S1-U eNodeB GTP-U interface") or 3 ("S12

RNC GTP-U interface"), if the eNB or RNC
supports such forwarding, or
- 15 ("S4 SGSN GTP-U interface").

NOTE1: For the Indication Flags, the combination (SGW Change Indication, Idle mode signalling Activation
Indication) = 1,1 shall be considered as an error if received.
7.3.8 Identification Request

If the UE identifies itself with temporary identity and it has changed SGSN/MME since detach in Attach procedure, the
new MME/SGSN shall send an Identification Request message to the old SGSN/MME over S3, S16 or S10 interface to
request IMSI.
If the sending/new node is a MME, it shall include in the Identification Request message:
- the GUTI IE and Complete Attach Request Message IE, if the GUTI or the indication of mapped or native GUTI
received from UE indicates the old node is a MME, as specified in subclause 2.8.2.2.2 of 3GPP TS 23.003 [2].
- the RAI P-TMSI, which was derived from the GUTI received from UE, and the P-TMSI Signature that was
received intact from the UE, if the GUTI or the indication of mapped or native GUTI indicates the old node is an
SGSN as specified in subclause 2.8.2.2.2 of 3GPP TS 23.003 [2].
If the sending/new node is an SGSN, it shall include RAI IE, P-TMSI IE and P-TMSI Signature IE in the Identification
Request message. If the receiving/old node is an MME, it shall construct GUTI according to the RAI IE, P-TMSI IE
and P-TMSI Signature IE (see the mapping relationship between RAI, P-TMSI, P-TMSI signature and GUTI defined in
3GPP TS23.003[2]), and find UE context via this GUTI.
ETSI
The new MME differentiates the type of the old node as specified in subclause 2.8.2.2.2 of 3GPP TS 23.003 [2]. If the
old node is an SGSN, the GUTI shall be mapped to RAI and P-TMSI by the new MME; if the old node is a MME, the
new MME include GUTI IE and Complete Attach Request Message IE in the Identification Request message. The
Mapping between temporary and area identities is defined in 3GPP TS 23.003 [2].
The GUTI IE shall not coexist with any of the RAI IE, P-TMSI IE and P-TMSI Signature IE in an Identification
Request message. If this occurs, the receiving node shall return a corresponding cause value in the response message.
The Target PLMN ID IE shall be used in old SGSN/MME in order to decide whether un-used authentication vectors to
be distributed to new SGSN/MME or not. Distribution and use of authentication vectors between different serving
network domains are specified in 3GPP TS 33.401 [12].
Table 7.3.8-1: Information Elements in an Identification Request

elements
GUTI C The new MME shall include this IE over S10 interface. GUTI 0
Routeing Area C This IE shall be included over S3/S16 interface, if the GUTI ULI (NOTE 1) 0
Identity(RAI) or the indication of mapped or native GUTI received from
the UE indicates the old node is an SGSN, the new MME
maps this IE from GUTI.
Packet TMSI(P-TMSI) C This IE shall be included over S3/S16 interface. For the S3 P-TMSI 0
interface, if sent by the MME, this IE is derived by the MME
from the GUTI received from the UE.
P-TMSI Signature C This IE shall be included over S3/S16 interface, if it is P-TMSI Signature 0
Complete Attach C The new MME shall include this IE over S10 interface, and Complete 0
Request Message the old MME may use this IE for integrity check. Request Message
Address for Control O If an SGSN within the same SGSN pool with the old SGSN IP Address 0
Plane receives this message, the SGSN shall include the old IP
address of the received message in this optional
the old SGSN.
UDP Source Port C If an SGSN within the same SGSN pool as the old SGSN Port Number 0
the UDP destination port of the Identification Response
message.
SGSN.
Target PLMN ID CO If available, this IE shall be included in order to allow old Serving Network 0
MME/SGSN to make a judgment whether un-used
authentication vectors to be distributed or not.
Private Extension O None Private Extension VS
7.3.9 Identification Response

The old SGSN/MME shall send an Identification Response message to the new MME/SGSN as a response to a previous
Identification Request message over S3/S10/S16 interface.
For Intra Domain Connection of RAN Nodes to Multiple CN Nodes, if an old SGSN within an SGSN pool receives an
Identification Request message that contains the optional parameter Address for Control Plane, the old SGSN shall use
this address as destination IP address of the Identification Response message.
ETSI
- "P-TMSI Signature mismatch"
- "User authentication failed"
Only the Cause information element shall be included in the response if the Cause contains another value than "Request
accepted".
Table 7.3.9-1: Information Elements in an Identification Response

elements
Cause M Cause 0
IMSI C This IE shall be included over the S10/S3/S16 interface if IMSI 0
the Cause contains the value "Request accepted".
MME/SGSN UE MM C This IE shall be included over the S10/S3/S16 interface if MM Context 0
Context the integrity check or the P-TMSI signature check for the
Attach Request succeeds.
Trace Information CO This IE shall be included over the S10/S3/S16 interface Trace Information 0
when session trace is active for this IMSI/IMEI.
Dedicated Core Networks specified in TS 23.401 [3].
See NOTE 1.
NOTE 1: A UE Usage Type IE with the length field equal to 0 is used for the receiver to differentiate the case
subscription.
7.3.10 Forward Access Context Notification

A Forward Access Context Notification message shall be sent from the Old SGSN to the New SGSN over the S16
interface to forward the RNC contexts to the target system, or sent from the Old MME to the New MME over the S10
interface to forward the RNC/eNodeB contexts to the target system.
When the old SGSN receives the RANAP message Forward SRNS Context, the old SGSN shall send a Forward Access
Context Notification message to the new SGSN. The new SGSN shall forward the message to the target RNC using the
corresponding RANAP message.
When the old SGSN receives a BSSGP message PS handover Required and the acknowledged peer-to-peer LLC
operation is used for the Bearer Context or when "delivery order" is set in the Bearer Context QoS profile, the old
SGSN shall send a Forward Access Context Notification message with the PDU Number IE to the new SGSN. The new
SGSN shall forward the message to the target RNC/ target BSS using the corresponding RANAP message only for PS
handover to Iu mode.
When the old SGSN receives a BSSGP message PS handover Required from source BSS/RNC for PS handover to
A/Gb mode, the value part of RAB Context IE shall be empty according to its defined minimum length.
Table 7.3.10-1 specifics the presence requirements and conditions of the IEs in the message.
ETSI
Table 7.3.10-1: Information Elements in a Forward Access Context Notification

elements
RAB Contexts C This IE shall be included for S16 only. Several IEs with this RAB Context 0
type and instance values shall be included as necessary to
For each RAB context in the received RANAP message,
the old SGSN shall include this IE in the message.
Source RNC PDCP C If available, the old SGSN shall include an Source RNC Source RNC 0
context Info PDCP context info in the message. PDCP context
Info
PDU Numbers C This IE only applies to S16. The old SGSN shall include PDU Numbers 0
this IE in the message if the acknowledged peer-to-peer
LLC operation is used for the Bearer Context or when
"delivery order" is set in the Bearer Context QoS profile in
A/Gb mode to Iu/A/Gb mode PS handover.
E-UTRAN C This IE shall be included over S10 to contain the "eNB F-Container 0
Transparent Status Transfer Transparent Container" as specified
Container in3GPP TS 36.413 [10].
7.3.11 Forward Access Context Acknowledge

A Forward Access Context Acknowledge message shall be sent to the old MME/SGSN as a response to Forward
Access Context Notification.
Table 7.3.11-1 specifics the presence requirements and conditions of the IEs in the message.
Table 7.3.11-1: Information Elements in a Forward Access Context Acknowledge

elements
Cause M Cause 0
7.3.12 Detach Notification

A Detach Notification message shall be sent from an MME to the associated SGSN, or from an SGSN to the associated
MME as a part of Detach procedure if the ISR is activated between the MME and SGSN for the UE.
- "Local Detach".
- "Complete Detach".
A Detach Notification message shall also be sent from an SGSN to the associated MME as a part of Detach procedure if
the ISR is activated between the MME and SGSN for the UE.
- "IMSI Detach only".
"Local Detach" indicates that this detach is local to the MME/SGSN and so the associated SGSN/MME registration
where the ISR is activated shall not be detached. The MME/SGSN that receives this message including this Cause value
of "Local Detach" only deactivates the ISR. This Cause value shall be included in the procedures:
- MME/SGSN-initiated Detach Procedure in case of implicit detach.
ETSI
"Complete Detach" indicates both the MME registration and the SGSN registration that the ISR is activated for, shall be
detached. This "Complete Detach" Cause value shall be included in the procedures:
- UE-initiated Detach Procedure.
- MME/SGSN-initiated Detach Procedure in case of explicit detach.
For the purpose of SGs handling, the SGSN shall include Detach Type in the Detach Notification message for
"Complete Detach" when the UE is combined IMSI/EPS attached and the ISR is activated.
Possible Detach Type values are:
- "PS Detach".
- "Combined PS/CS Detach".
"PS Detach" indicates that the MME shall perform explicit IMSI detach from EPS service as specified in section 5.4,
3GPP TS 29.118 [22]. "Combined PS/CS detach" indicates that the MME shall perform explicit IMSI detach from non-
EPS service as specified in section 5.5, 3GPP TS 29.118 [22].
"IMSI Detach only" indicates that combined IMSI/EPS attached UE initiates IMSI only GPRS detach from non-GPRS
service as specified in section 4.7.4.1, 3GPP TS 24.008 [5], and both the SGSN/MME registration shall be remained.
The MME shall perform explicit IMSI detach from non-EPS service for the SGs handling purpose, which is specified in
section 5.5, 3GPP TS 29.118 [22]. This "IMSI Detach only" Cause value shall be included in the procedures:
- UE-initiated Detach Procedure for GERAN/UTRAN for "IMSI Detach only".
Table 7.3.12-1 specifics the presence of the IEs in the message.
Table 7.3.12-1: Information Elements in a Detach Notification

elements
Cause M Cause 0
Detach Type CO This IE shall be included by SGSN when the Cause Detach Type 0
indicates "Complete Detach" for the combined IMSI/EPS
attached UE.
7.3.13 Detach Acknowledge

A Detach Acknowledge message shall be sent as a response to a Detach Notification message during Detach procedure.
Table 7.3.13-1: Information Elements in a Detach Acknowledge

elements
Cause M Cause 0
7.3.14 Change Notification Request

3GPP TS 23.401 [3] and 3GPP TS 23.060 [4] specify that if PGW has requested ECGI/TAI/CGI/SAI/RAI Change
Reporting or reporting of change of UE presence in a Presence Reporting Area or User CSG information Change
Reporting and if MME/S4-SGSN supports the feature, then MME/S4-SGSN shall send the Change Notification Request
message on the S11/S4 interface to the SGW. If SGW supports the feature, the SGW forwards the message on the GTP
based S5/S8 interface to the PGW as part of location dependent charging related procedures.
ETSI
In this version of the specification, the sender shall set the header TEID value to that of the peer node"s Control Plane
TEID on S11/S4 interface or to the peer node"s Control Plane TEID on S5/S8 interface. However a receiver shall be
prepared to receive messages in which the header TEID value is set to zero from implementation conforming to earlier
versions of this specification. When that is the case, the receiver identifies the subscriber context based on the included
LBI, IMSI, and/or MEI IEs.
ETSI
Table 7.3.14-1: Information Element in Change Notification Request

elements
IMSI C The MME/SGSN shall include IMSI in the message except IMSI 0
for the case:
UICCless.

an identifier
authenticated.
If the SGW receives this IE, it shall forward it to the PGW

on S5/S8.
ME Identity (MEI) C The MME/SGSN shall include the ME Identity (MEI) IE: MEI 0
UICCless

authenticated

on S5/S8.
is set to 1.
UE.
RAT Type M See NOTE 2. RAT Type 0

User Location C The SGSN shall include the User Location Information IE if ULI 0
Information (ULI) the MS is located in a RAT Type of GERAN, UTRAN or (NOTE 1)
GAN and shall include the CGI, SAI and/or RAI.
CO The MME shall include the User Location Information IE if
the UE is located in a RAT Type of E-UTRAN and shall
include the ECGI and/or TAI.
CO If the SGW receives this IE it shall forward it to the PGW, if
it supports this feature.
User CSG CO The SGSN/MME shall include the User CSG Information UCI 0
Information (UCI) IE if the MS is located in the CSG cell or the hybrid cell and
the P-GW/PCRF decides to receive the CSG Information.
If the SGW receives this IE it shall forward it to the PGW, if
it supports this feature.
PGW S5/S8 GTP-C C This IE shall be sent on S4. IP Address 0
IP Address CO This IE shall be sent on S11.
LBI CO This IE, identifying the PDN connection, shall be sent by EBI 0
the MME/SGSN on S11/S4.
on S5/S8.
Presence Reporting CO The MME/SGSN shall include this IE on the S11/S4 Presence 0
Area Information interface if the PGW/PCRF requested to start reporting of Reporting Area
change of UE presence in a Presence Reporting Area and Information
the UE enters or leaves the Presence Reporting Area.
Presence Reporting Area Information from MME/SGSN.
Private Extension O Vendor or operator specific information Private Extension VS
ETSI
NOTE 2: The PGW may ignore RAT Type as the MME/SGSN always informs the PGW about RAT Type
change with the Modify Bearer Request message.
7.3.15 Change Notification Response

The Change Notification Response message may be sent on the S11/S4 interface by the SGW to the MME/SGSN and is
sent on the S5/S8 interface by the PGW to the SGW as part of location dependent charging related procedures to
acknowledge the receipt of a Change Notification Request.
If SGW does not support the feature (see subclause 7.3.14 "Change Notification Request"), SGW may silently discard
Change Notification Request message from MME/SGSN. If the MME/ SGSN does not receive Change Notification
Response, the MME/SGSN may either send Change Notification Request to the same SGW next time UE location
changes, or not (marking SGW as not supporting the feature).
The Cause value indicates whether or not the Change Notification Request was received correctly. Possible Cause
values are specified in Table 8.4-1. Message specific cause values are:
- "IMSI/IMEI not known".
In this version of the specification, the sender shall set the header TEID value to that of the peer node"s Control Plane
TEID on S11/S4 interface or to the peer node"s Control Plane TEID on S5/S8 interface. However a receiver shall be
prepared to receive messages in which the header TEID value is set to zero from implementation conforming to earlier
versions of this specification. When that is the case, the receiver identifies the subscriber context based on the included
LBI, IMSI, and/or MEI IEs.
If the IMSI is unknown, or the IMEI is unknown when the UE is emergency attached and UICCless or the UE is
emergency attached but the IMSI is not authenticated for the receiving GTP-C entity, then the message shall be silently
discarded and no further processing of the IEs shall continue.
If the MME/SGSN receives Change Notification Response containing a Cause value of "IMSI/IMEI not known" and
CS bit set to 1, this indicates that the associated PDN connection does not exist within the PGW. The Change Reporting
mechanism shall be stopped in the receiving SGSN/MME for all Bearers of the associated PDN connection. The
SGSN/MME shall then initiate PDN disconnection for all of these PDN Connections.
If the PDN Connection associated of the Change Notification Request message received by the SGW does not exist
within the SGW, the SGW shall return Change Notification Response with the CS bit set to 0 to the MME/SGSN. The
Change Reporting mechanism shall be stopped in the receiving SGSN/MME for all Bearers of the associated PDN
connection, and the MME/SGSN shall then locally delete the PDN connection and release all associated resources.
If the location Change Reporting mechanism is to be stopped or modified for this subscriber in the SGSN/MME, then
the PGW shall include the Change Reporting Action IE in the message and shall set the value of the Action field
appropriately.
ETSI
Table 7.3.15-1: Information Element in Change Notification Response

elements
IMSI C The IMSI shall be included in the message if it is received IMSI 0
in the Change Notification Request message.
ME Identity (MEI) C The ME Identity (MEI) shall be included in the message if it MEI 0
is received in the Change Notification Request message.
Cause M Cause 0
Change Reporting C This IE shall be included with the appropriate Action field If Change Reporting 0
Action the location Change Reporting mechanism is to be started Action
CSG Information CO This IE shall be included with the appropriate Action field if CSG Information 0
Reporting Action the location CSG Info reporting mechanism is to be started Reporting Action
Presence Reporting CO This IE shall be included on the S5/S8 and S11/S4 Presence 0
Area Action interfaces with the appropriate Action field if reporting Reporting Area
changes of UE presence in a Presence Routing Area is to Action
be started or stopped for this subscriber in the
MME/SGSN.
7.3.16 Relocation Cancel Request

A Relocation Cancel Request message shall be sent from the source MME/SGSN to the target MME/SGSN on
S3/S10/S16 interface as part of the Inter RAT handover Cancel procedure/S1 Based handover Cancel procedure and on
the S16 interface as part of the SRNS Relocation Cancel Procedure.Table 7.3.16-1 specifics the presence of the IEs in
the message.
Table 7.3.16-1: Information Elements in Relocation Cancel Request

elements
case:
UICCless.

an identifier
authenticated.
ME Identity (MEI) C The MME/SGSN shall include the ME Identity (MEI) IE: MEI 0
UICCless

authenticated
is set to 1.
UE.
RANAP Cause C This IE shall be present in the case of SRNS relocation F-Cause 0
cancel procedure. It shall contain the cause value received
from the source RNC in the Relocation Cancel message
received over the Iu interface.
ETSI
7.3.17 Relocation Cancel Response

A Relocation Cancel Response message shall be sent as a response to a previous Relocation Cancel Request message
during the Inter RAT handover Cancel procedure/S1 Based handover Cancel procedure/SRNS Relocation Cancel
Procedure.
- "IMSI/IMEI not known".
Table 7.3.17-1: Information Elements in Relocation Cancel Response

elements
Cause M Cause 0
7.3.18 Configuration Transfer Tunnel

A Configuration Transfer Tunnel message shall be used to tunnel eNodeB Configuration Transfer messages from a
source MME to a target MME over the S10 interface. The purpose of the eNodeB Direct Configuration Transfer is to
transfer information from an eNodeB to another eNodeB in unacknowledged mode (see 3GPP TS 36.413 [10]).
Table 7.3.18-1: Information Elements in a Configuration Transfer Tunnel Message

elements
E-UTRAN M This IE shall contain the "SON Configuration Transfer" as F-Container 0
Transparent specified in 3GPP TS 36.413 [10].
Container Container Type shall be set to 3.
Target eNodeB ID M This IE shall contain the ID of the target eNodeB Target 0
Identification
7.3.19 RAN Information Relay

The RAN Information Relay message shall be sent on S3 interface between SGSN and MME to transfer the RAN
information received by an SGSN from BSS or RNS (or GERAN Iu mode) or by an MME from eNodeB. The
procedures are specified in 3GPP TS 23.401 [3].
This message shall also be sent on S16 interface to transfer the RAN information between GERAN or GERAN Iu mode
or UTRAN.
For handling of protocol errors the RAN Information Relay message is treated as a Response message.
ETSI
Table 7.3.19-1: Information Elements in a RAN Information Relay

elements
BSS Container M All information elements from the BSSGP RIM PDU, F-Container 0
starting from and including the BSSGP "PDU type", shall
be contained within the BSS Container and forwarded to
the destination MME/SGSN in the RAN Information Relay
message. The Container Type shall be set to 2.
RIM Routing Address C This IE shall be included if the RIM Routing Address Target 0
information is included in the message sent from the Identification
source RAN node.
This IE identifies the destination RAN node where the RAN
Information needs to be relayed to. It contains:
- the destination RNC Identity when the target is
GERAN Iu mode or UTRAN; or
- the destination Cell Identity when the target is

GERAN; or
- the Target eNodeB ID when the target is E-

UTRAN.
Private Extension O None Private Extension VS
7.3.20 ISR Status Indication

A ISR Status Indication message shall be sent on the S3 interface by the MME/SGSN to the ISR associated
SGSN/MME as part of the following procedures:
- the Restoration of PDN connections after an SGW failure for UEs with ISR as specified in 3GPP TS 23.007
[17];
- the HSS Based P-CSCF restoration procedure for 3GPP access (for both basic and PCO extension) as specified
in 3GPP TS 23.380 [61].
Table 7.3.20-1: Information Elements in an ISR Status Indication

elements
Action Indication M This IE shall include one of the applicable Values: Action Indication 0
- Deactivation Indication: If the value is set to 1, this
indicates a request to the ISR associated
MME/SGSN to deactivate ISR and remove the UE
resource locally. See 3GPP TS 23.007 [17].
- Paging Indication: If the value is set to 2, this

indicates a request to the ISR associated
MME/SGSN to page the UE in IDLE state. See
3GPP TS 23.007 [17].
- Paging Stop Indication: If the value is set to 3, this

indicates to the ISR associated MME/SGSN to
stop paging the UE. See 3GPP TS 23.380 [61].
7.3.21 UE Registration Query Request

The direction of this message shall be from S4-SGSN to MME (see Table 6.1-1).
ETSI
This message shall be used to support CS/PS coordination for shared UTRAN and GERAN access. When an S4-SGSN
receives a UE Registration Query from a RAN node, including an indication to also query MMEs, and if the UE
(identified by IMSI) is not registered in the S4-SGSN, the S4-SGSN shall send a UE Registration Query Request
message to all MMEs that may hold the UE"s context, as specified in the subclause 7.1.6 of 3GPP TS 23.251 [55].
NOTE: How the S4-SGSN determines which MMEs it will query, is based on local configuration.
Table 7.3.21-1: Information Elements in UE Registration Query Request

elements
IMSI M IMSI 0
7.3.22 UE Registration Query Response

The UE Registration Query Response message shall be sent as a response to a UE Registration Query Request, to report
whether the inquired UE is registered in the MME and if so, with which Core Network Operator, as specified in the
subclause 7.1.6 of 3GPP TS 23.251 [55].
- "Request accepted", to be used when the UE is registered in the MME
- "IMSI/IMEI not known", to be used when the UE is not registered in the MME.
The IMSI received in the UE Registration Query Request message shall be included in the response, to allow
correlation in the SGSN.
The Selected Core Network Operator Identifier identifies the core network operator currently serving the UE, and shall
be included if the inquired UE is registered in the MME.
Table 7.3.22-1: Information Elements in UE Registration Query Response

elements
Cause M Cause 0
IMSI M IMSI 0
Selected Core M PLMN ID 0
Network Operator
Identifier
7.4 CS Fallback and SRVCC related messages

7.4.1 Suspend Notification
The Suspend Notification message shall be sent on the S11 interface by the MME to the SGW and on the S5/S8
interface by the SGW to the PGW as part of the 1xRTT CS fallback procedures in 3GPP TS 23.272 [21].
The Suspend Notification message shall be sent on the S3 interface by the SGSN to the MME, on the S11 interface by
the MME to the SGW, and on the S5/S8 interface by the SGW to the PGW as part of the SRVCC procedures in 3GPP
TS 23.216 [43] or the CS fallback from E-UTRAN access to UTRAN/GERAN CS domain access related procedures in
3GPP TS 23.272 [21].
The Suspend Notification message shall be sent on the S16 interface as per the inter-SGSN suspend procedures in 3GPP
TS 23.060 [35].
ETSI
The Suspend Notification message shall be sent on the S16, the S4 and the S5/S8 interfaces as part of the SRVCC from
UTRAN (HSPA) to GERAN without DTM support procedure in 3GPP TS 23.216 [43].
The Suspend Notification message shall be sent on the S4 and the S5/S8 interfaces as part of the CS fallback from E-
UTRAN to GERAN CS domain related procedures in 3GPP TS 23.272 [21].
After receiving a Suspend Notification message, the SGW/PGW marks all the non-GBR bearers as suspended status.
The PGW should discard packets it receives for the suspended UE.
Table 7.4.1-1: Information Element in Suspend Notification

elements
IMSI C This IE shall be included only on the S11 interface. IMSI 0
See NOTE 2.
Routeing Area C This IE shall be included only on the S3 interface. ULI (NOTE 3) 0
Identity(RAI) See NOTE 1.
CO This IE shall be included on the S16 interface.
Linked EPS Bearer ID CO This IE shall be included on the S11/S4 interface to EBI 0
(LBI) indicate the default bearer associated with the PDN
connection.
Packet TMSI(P-TMSI) C This IE shall be included only on the S3 interface. P-TMSI 0
See NOTE 1.
CO This IE shall be included on the S16 interface.
Originating Node CO This IE shall be sent on S11 interface, if before MME Node Type 0
initiates a Detach procedure (a) ISR was active in the MME
and (b) the MME was in EMM-Connected state (see also
8.65).
This IE shall be sent on S4 interface, if before S4-SGSN
initiates a Detach procedure (a) ISR was active in the
SGSN and (b) the SGSN was in PMM-Connected state
(see also 8.65).
Address for Control CO If an SGSN within the same SGSN pool with the old SGSN IP Address 0
Plane receives this message, the SGSN shall include the source
IP address of the received message in this optional
the old SGSN.
UDP Source Port CO If an SGSN within the same SGSN pool as the old SGSN Port Number 0
the UDP destination port of the Suspend Acknowledge
message.
SGSN.
NOTE 1: If the ISR is not active, the MME can not suspend the bearers after receving the Suspend Notification
message from the SGSN, the GUTI can not be derived from the P-TMSI and RAI pair as the P-TMSI
Signature is not included in the message. The MME shall still reply the Suspend Acknowledge to the
SGSN. Suspend procedure on MME, SGW and PGW are triggered by the S1 UE Context Release
message sent from the eNodeB to the MME. Refer to section 6.3 and section 7.4 in 3GPP TS 23.272
[21] for detail.
NOTE 2: The IMSI is present only for backward compatibility reasons since the SGW can derive the context
from the TEID in the header. In scenarios where IMSI is not present (e.g. UICCless UE during an
Emergency call) a dummy IMSI shall be provided.
ETSI
7.4.2 Suspend Acknowledge

The Suspend Acknowledge message shall be sent on the S11 interface by the SGW to the MME and on the S5/S8
interface by the PGW to the SGW as part of the 1xRTT CS fallback procedures in 3GPP TS 23.272 [21].
The Suspend Acknowledge message shall be sent on the S3 interface by the MME to the SGSN, on the S11 interface by
the SGW to the MME and on the S5/S8 interface by the PGW to SGW as part of the SRVCC procedures in 3GPP TS
23.216 [43] or the CS fallback from E-UTRAN access to UTRAN/GERAN CS domain access related procedures in
3GPP TS 23.272 [21].
The Suspend Acknowledge message shall be sent on the S16 interface as per the inter-SGSN suspend procedures in
3GPP TS 23.060 [35].
The Suspend Acknowledge message shall be sent on the S16, the S4 and the S5/S8 interfaces as part of the SRVCC
from UTRAN (HSPA) to GERAN without DTM support procedure in 3GPP TS 23.216 [43].
The Suspend Acknowledge message shall be sent on the S4 and the S5/S8 interfaces as part of the CS fallback from E-
UTRAN to GERAN CS domain related procedures in 3GPP TS 23.272 [21].
For backward compatibility, if the IMSI IE is missing in the Suspend Notification message that is received on the S11
interface, the cause value "Mandatory IE missing" shall be used.
Table 7.4.2-1: Information Element in Suspend Acknowledge

elements
Cause M Cause 0
7.4.3 Resume Notification

The Resume Notification message should be sent on the S11 interface by the MME to the SGW and forwarded on the
S5/S8 interface by the SGW to the PGW as part of the resume procedure returning back to E-UTRAN in the case of CS
fallback or SRVCC.
The Resume Notification message should also be sent on the S4 interface by the SGSN to the SGW and forwarded on
the S5/S8 interface by the SGW to the PGW as part of the resume procedure returning from SRVCC to HSPA if there is
no Modify Bearer Request message sent to the SGW and PGW as specified in 3GPP TS 23.216 [43].
The SGW may also send a Resume Notification message to the PGW on the S5/S8 interface upon receipt from the
MME/S4-SGSN of a (non-empty) Modify Bearer Request used as an implicit resume of the suspended bearers in the
SGW and in the PGW (see 3GPP TS 23.216 [43] sections 6.2.2.1 and 6.3.2.1, 3GPP TS 23.272 [21] sections 6.3, 6.5
and 7.4) if the conditions of presence of the IEs in the Modify Bearer Request specified in table 7.2.7-1 do not require
any IE to be sent over S5/S8 to the PGW.
NOTE: This is an alternative to sending over S5/S8 a Modify Bearer Request used as an implicit resume with
zero IE(s), see subclause 7.2.7.
After receiving a Resume Notification message or a Modify Bearer Request used as an implicit resume of the
suspended bearers, the SGW/PGW clears suspended status for all the non-GBR bearers. The PGW shall forward
packets it receives for the UE. If the suspended bearers are of the type S4-U GTP-U, the SGW shall forward over the
S4-U interface, packets it receives for the UE, upon receipt of Resume Notification.
ETSI
Table 7.4.3-1: Information Element in Resume Notification

elements
IMSI M See NOTE1. IMSI 0
Linked EPS Bearer ID CO This IE shall be included on the S11/S4 interface to EBI 0
(LBI) indicate the default bearer associated with the PDN
connection.
Originating Node CO This IE shall be sent on S11 interface, if before MME Node Type 0
initiates a Detach procedure (a) ISR was active in the MME
and (b) the MME was in EMM-Connected state (see also
8.65).
This IE shall be sent on S4 interface, if before S4-SGSN
initiates a Detach procedure (a) ISR was active in the
SGSN and (b) the SGSN was in PMM-Connected state
(see also 8.65).
NOTE 1: The IMSI is present only for backward compatibility reasons since the receiver can derive the context
from the TEID in the header. In scenarios where IMSI is not present (e.g. UICCless UE during an
Emergency call) a dummy IMSI shall be provided.
7.4.4 Resume Acknowledge

The Resume Acknowledge message should be sent on the S11 interface by the SGW to the MME and on the S5/S8 by
the PGW to the SGW as part of the resume procedure returning back to E-UTRAN in the case of CS fallback or
SRVCC.
The Resume Acknowledge message should also be sent on the S4 interface by the SGW to the SGSN and on the S5/S8
interface by the PGW to the SGW as part of the resume procedure returning from SRVCC to HSPA if there is no
Modify Bearer Request message sent to the SGW and PGW as specified in 3GPP TS 23.216 [43].
The PGW shall also send a Resume Acknowledge message to the SGW on the S5/S8 interface as a response to a
Resume Notification message sent by the SGW upon receipt from the MME/S4-SGSN of a (non-empty) Modify Bearer
Request used as an implicit resume of the suspended bearers in the SGW and in the PGW (see 3GPP TS 23.216 [43]
sections 6.2.2.1 and 6.3.2.1, 3GPP TS 23.272 [21] sections 6.3, 6.5 and 7.4) if the conditions of presence of the IEs in
the Modify Bearer Request specified in table 7.2.7-1 do not require any IE to be sent to the PGW.
Table 7.4.4-1: Information Element in Resume Acknowledge

elements
Cause M Cause 0
7.4.5 CS Paging Indication

The CS Paging Indication shall be sent on the S3 interface by the MME to the associated SGSN when ISR is activated
as part of mobile terminated CS services. The MME gets the related information from SGsAP-PAGING-REQUEST
message as specified in 3GPP TS29.118 [21].Table 7.4.5-1 specifies the presence requirements and the conditions of
the IEs in the message.
NOTE: The SS code received on the SGs interface is not transferred to the SGSN because it is not used by the
SGSN.
ETSI
Table 7.4.5-1: Information Element in CS Paging Indication

elements
IMSI M IMSI 0
VLR Name M FQDN 0
TMSI O TMSI 0
Location area O ULI 0
identifier
Global CN-Id O Global CN-Id 0
Channel needed O Channel needed 0
eMLPP Priority O eMLPP Priority 0
Service Indicator CO This IE shall be sent if the service type for the paging is Service Indicator 0
available.
7.4.6 Alert MME Notification

An Alert MME Notification message shall be sent on the S3 interface by the MME to the associated SGSN as part of an
SGs Non-EPS alert procedure (see 3GPP TS 29.118 [22]) when ISR is activated, except under the conditions specified
in 3GPP TS 23.272 [21], to request to receive a notification when any activity from the UE is detected.
Table 7.4.6-1: Information Element in Alert MME Notification

elements
7.4.7 Alert MME Acknowledge

An Alert MME Acknowledge message shall be sent as a response to an Alert MME Notification message.
NOTE: An SGSN implemented according to an earlier version of the specification will silently discard the Alert
MME Notification message. An MME which does not receive an Alert MME Acknowledge message may
not send further Alert MME Notification message to this SGSN.
Table 7.4.7-1: Information Elements in Alert MME Acknowledge

elements
Cause M Cause 0
7.4.8 UE Activity Notification

A UE Activity Notification message shall be sent on the S3 interface by the SGSN to the associated MME as part of an
SGs Non-EPS alert procedure (see 3GPP TS 29.118 [22]) when ISR is activated, except under the conditions specified
in 3GPP TS 23.272 [21], to indicate that activity from a UE has been detected. Table 7.4.8-1 specifies the presence
requirements and the conditions of the IEs in the message.
ETSI
Table 7.4.8-1: Information Element in UE Activity Notification

elements
7.4.9 UE Activity Acknowledge

A UE Activity Acknowledge message shall be sent as a response to a UE Activity Notification message.
Table 7.4.9-1 specifics the presence requirements and the conditions of the IEs in the message.
Table 7.4.z-1: Information Elements in UE Activity Acknowledge

elements
Cause M Cause 0
7.5 Non-3GPP access related messages

7.5.1 Create Forwarding Tunnel Request
A Create Forwarding Tunnel Request message shall be sent by a MME to a Serving GW as a part of the MME
configures resources for indirect data forwarding during active handover procedure from E-UTRAN to CDMA 2000
HRPD access.
Table 7.5.1-1: Information Elements in a Create Forwarding Tunnel Request

elements
S103 PDN Data M The MME shall include the forwarding Infomation for all S103PDF 0
Forwarding Info PDN connections of the UE requesting data forwarding
towards the HSGW in the message as S103 PDN Data
Forwarding Info information elements. For each of those
PDN Connections, an IE with the same type and instance
value shall be included.
The Serving GW shall forward downlink data to the HSGW
via the GRE tunnel identified by the HSGW Address and
HSGW GRE Key included in this information element when
it receives downlink data forwarded from the eNodeB
belonging to the corresponding EPS bearers of the PDN
connection.
7.5.2 Create Forwarding Tunnel Response

A Create Forwarding Tunnel Response message shall be sent by a Serving GW to a MME as a response to a Create
Forwarding Tunnel Request message.
The Cause value indicates if Data Forwarding Resources has been created in the Serving GW or not. Data Forwarding
Resources have not been created in the Serving GW if the Cause differs from "Request accepted". Possible Cause
values are specified in Table 8.4-1.
ETSI
Only the Cause IE shall be included in the response if the Cause IE contains another value than "Request accepted".
Table 7.5.2-1: Information Elements in a Create Forwarding Tunnel Response

elements
Cause M Cause 0
S1-U Data C S1-U Data Forwarding Info shall be included in the S1UDF 0
Forwarding Info message if the Cause contains the value "Request
accepted". For each EPS bearer requesting data
forwarding which is included in the S103 PDN Data
Forwarding Info fields of corresponding Create Forwarding
Tunnel Request message, the Serving GW shall assign a
Serving GW S1-U Address and Serving GW S1-U TEID
pair and included it in the response message as S1-U Data
Forwarding Info information element. For each of those
EPS bearers, an IE with the same type and instance value
shall be included.
The eNodeB shall forward downlink data of the EPS bearer
to the Serving GW via the GTP-U tunnel identified by the
Serving GW S1-U Address and Serving GW S1-U TEID.
7.6 Reliable Delivery of Signalling Messages

Retransmission requirements in the current subclause do not apply to the Initial messages that do not have Triggered
messages.
Reliable delivery in GTPv2 messages is accomplished by retransmission of these messages. A message shall be
retransmitted if and only if a reply is expected for that message and the reply has not yet been received. There may be
limits placed on the total number of retransmissions to avoid network overload.
Initial messages and their Triggered messages, as well as Triggered messages and their Triggered Reply messages are
matched based on the Sequence Number and the IP address and port rules in subclause 4.2 "Protocol stack". Therefore,
an Initial message and its Triggered message, as well as a Triggered message and its Triggered Reply message shall
have exactly the same Sequence Number value. A retransmitted GTPv2 message (an Initial or a Triggered) has the
exact same GTPv2 message content, including the GTP header, UDP ports, source and destination IP addresses as the
originally transmitted GTPv2 message.
For each triplet of local IP address, local UDP port and remote peer's IP address a GTP entity maintains a sending queue
with signalling messages to be sent to that peer. The message at the front of the queue shall be sent with a Sequence
Number, and if the message has an expected reply, it shall be held in a list until a reply is received or until the GTP
entity has ceased retransmission of that message. The Sequence Number shall be unique for each outstanding Initial
message sourced from the same IP/UDP endpoint. A node running GTP may have several outstanding messages waiting
for replies. Not counting retransmissions, a single GTP message with an expected reply shall be answered with a single
GTP reply, regardless whether it is per UE, per APN, or per bearer
A piggybacked initial message (such as a Create Bearer Request message or Modify Bearer Request message) shall
contain a Sequence Number that is assigned by sending GTP entity and the message shall be held in a list until a
response is received. The response message to a piggybacked initial message may arrive without piggybacking (e.g.,
Create Bearer Response at PGW).
The Sequence Number in the GTP header of the triggered response message shall be copied from the respective request
message.
If a request message (e.g., Create Session Request) triggers piggybacking (i.e., Create Bearer Request piggybacked on
Create Session Response), re-transmission of the request message shall also trigger piggybacking. A Sequence Number
used for a Command message shall have the most significant bit set to 1. A Sequence Number in a message, which was
triggered by a Command message, as well as respective Triggered Reply message shall have the same Sequence
Number as the Command message (i.e. shall also have the most significant bit set to 1). This setting of the most
significant bit of the Sequence Number is done to avoid potential clashes between the Sequence Number selected for a
Command message, and the Sequence Number selected by a GTPv2 peer for a Request message, which was not
triggered by a Command message.
ETSI
A Sequence Number used for a Request message, which was not triggered by a Command message shall have the most
significant bit set to 0.
A timer, denoted T3-RESPONSE, shall be started when a signalling message (for which a reply is expected) is sent. A
signalling message or the triggered message has probably been lost if a reply has not been received before the T3-
RESPONSE timer expires.
Once the T3-RESPONSE timer expires, the message corresponding to the T3-RESPONSE timer is then retransmitted if
the total number of retry attempts is less than N3-REQUESTS times. The expiry of the timer for piggybacked request
messages shall result in re-transmission of the original IP/UDP packet containing both the triggered response message
and the piggybacked initial message. T3-RESPONSE timer and N3-REQUESTS counter setting is implementation
dependent. That is, the timers and counters may be configurable per procedure. Multileg communications (e.g. Create
Session Requests and Responses) however require longer timer values and possibly a higher number of retransmission
attempts compared to single leg communication.
All received GTPv2 messages with an expected reply shall be replied to and all reply messages associated with a certain
message shall always include the same information. Duplicated reply messages shall be discarded by the receiver unless
the reply needs a reply. A received reply message without a matching outstanding message that is waiting for a reply
should be discarded.
If a GTPv2 node is not successful with the transfer of a non-Echo signalling message, e.g. a Create Bearer Request
message, it shall inform the upper layer of the unsuccessful transfer so that the controlling upper entity may take the
necessary measures.
7.7 Error Handling

7.7.0 Handling Piggybacked Messages
For piggybacked initial messages, the following general rule shall apply: the triggered response message carrying the
piggybacked message shall be processed first, according to the following sections. Subsequently, the piggybacked
initial message shall be processed independently. If the processing of dedicated bearer activation message results in an
error, this shall not affect the default bearer establishment. If the default bearer establishment fails, the dedicated bearer
activation related message shall be discarded.
7.7.1 Protocol Errors

A protocol error is defined as a message or an Information Element received from a peer entity with unknown type, or if
it is unexpected, or if it has an erroneous content.
The term silently discarded is used in the following subclauses to mean that the receiving GTP entity's implementation
shall discard such a message without further processing, or that the receiving GTP entity discards such an IE and
continues processing the message. The conditions for the receiving GTP entity to silently discard an IE are specified in
the subsequent subclauses.
The handling of unknown, unexpected or erroneous GTP messages and IEs shall provide for the forward compatibility
of GTP. Therefore, the sending GTP entity shall be able to safely include in a message a new conditional-optional or an
optional IE. Such an IE may also have a new type value. Any legacy receiving GTP entity shall, however, silently
discard such an IE and continue processing the message.
If a protocol error is detected by the receiving GTP entity, it should log the event including the erroneous message and
may include the error in a statistical counter.
For Request messages and Response messages without a rejection Cause value, the following applies:
- An information element with "Mandatory" in the "Presence requirement" column of a message definition shall
always be present in that message.
- An information element with "Conditional" in the "Presence requirement" column of a message definition shall
be sent when the conditions detailed in the "Condition / Comment" column are met.
For Response messages containing a rejection Cause value, see subclause 6.1.1.
ETSI
The Version Not Supported Indication message shall be considered as a Triggered message as specified in subclause
4.2.5 "Messages with GTPv2 defined replies: Classification of Initial and Triggered Messages".
The receiving GTP entity shall apply the error handling specified in the subsequent subclauses in decreasing priority.
If the received erroneous message is a reply to an outstanding GTP message, the GTP transaction layer shall stop
retransmissions and notify the GTP application layer of the error even if the reply is silently discarded.
7.7.2 Different GTP Versions

If a GTPv2 entity receives a message of an unsupported GTP version, higher than GTPv2, it shall return a Version Not
Supported Indication message and silently discard the received message.
If a GTPv2 entity listens to the GTPv0 port, the entity shall silently discard any received GTPv0 message.
If a GTPv2 entity does not support GTPv1 and receives a GTPv1 message, it shall silently discard the received
message.
7.7.3 GTP Message of Invalid Length

If a GTP entity receives a message, which is too short to contain the respective GTPv2 header, the GTP-PDU shall be
silently discarded.
Apart from a piggybacked GTP message or an Echo Request message, if a GTP entity receives a Request message
within an IP/UDP packet of a length that is inconsistent with the value specified in the Length field of the GTP header,
then the receiving GTP entity should log the error and shall send the Response message with Cause IE value set to
"Invalid Length".
Apart from a piggybacked GTP message, if a GTP entity receives a Response message within an IP/UDP packet of a
length that is inconsistent with the value specified in the Length field of the GTP header, then the receiving GTP entity
should log the error and shall silently discard the message.
If a GTP entity receives two GTP messages (triggered response message and a piggybacked initial message) within an
IP/UDP packet of a length that is inconsistent with the total length of the two concatenated messages as indicated by
Length fields of the GTP headers, then the receiving GTP entity should log the error and return an appropriate Response
message with Cause IE value set to "Invalid overall length of the triggered response message and a piggybacked initial
message". That is:
- for a Create Session Response message together with a piggybacked Create Bearer Request message, a Create
Bearer Response message should be returned with the above Cause value.
- for a Create Bearer Response message together with a piggybacked Modify Bearer Request message, a Modify
Bearer Response message should be returned with the above Cause value.
7.7.4 Unknown GTP Message

If a GTP entity receives a message with an unknown Message Type value, it shall silently discard the message.
7.7.5 Unexpected GTP Message

If a GTP entity receives an unexpected initial message (see subclause 4.2 "Protocol stack"), for example a known
message that is sent over an interface for which the message is not defined, or a message that is sent over an interface
for which the message is defined, but the direction is incorrect, then the GTP entity shall silently discard the message
and shall log an error.
If a GTP entity receives an unexpected triggered message which is not a request message (see subclause 4.2 "Protocol
stack"), for example a message for which there is no corresponding outstanding request, it shall discard the message and
may log an error.
When a GTP entity receives an unexpected triggered message, which is a request message, triggered by a command
message, i.e. the MSB of the sequence number is set "1", e.g. in Create/Update/Delete Bearer Request messages, the
GTP entity may continue to handle the request, e.g. to accept the Delete Bearer Request message.
ETSI
NOTE: Whether to accept or reject such a message is implementation specific.
7.7.6 Missing Information Elements

A GTP entity shall check if all mandatory IEs are present in the received Request message. Apart from Echo Request
message, if one or more mandatory information elements are missing in the received Request message, the GTP entity
should log the error and shall send a Response message with Cause IE value set to "Mandatory IE missing" together
with the type and instance of the missing mandatory IE.
If a GTP entity receives a Response message with Cause IE value set to "Mandatory IE missing", it shall notify its
upper layer.
A GTP entity shall check if all mandatory IEs are present in the received Response message without a rejection Cause
value. If one or more mandatory information elements are missing, the GTP entity shall notify the upper layer and
should log the error.
A GTP entity shall check if conditional information elements are present in the received Request message, if possible
(i.e. if the receiving entity has sufficient information available to check if the respective conditions were met). If one or
more conditional information elements are missing, a GTP entity should log the error and shall send a Response
message with Cause IE value set to "Conditional IE missing" together with the type and instance of the missing
conditional IE.
A GTP entity shall check if conditional information elements are present in the received Response message without a
rejection Cause value, if possible (i.e. if the receiving entity has sufficient information available to check if the
respective conditions were met). If one or more conditional information elements are missing, a GTP entity shall notify
the upper layer and should log the error.
For Response messages containing a rejection Cause value, see subclause 6.1.1.
If the Indication IE is applicable for the message as a conditional IE and if it is not present, the GTP entity shall not
reject the message unless there are other reasons to reject the message.
If the Indication IE is applicable for the message as conditional IE and if it is present with the value of all the applicable
flags set to "0", the GTP entity shall not reject the message unless there are other reasons to reject the message.
Absence of an optional information element shall not trigger any of the error handling processes.
7.7.7 Invalid Length Information Element

An information element has invalid length when the actual length of the IE is different from the value of the Length
field in the IE header. Here, the actual length of the IE means the length of the content field of the received IE.
If a GTP message contains more than one information elements and one or more of them have invalid length, the
receiving GTP entity can detect which of the IEs have invalid length only in the following cases:
- If the Length value in the IE header is greater than the overall length of the message;
- If the invalid length IE is the last one in the message.
Apart from Echo Request message, if a receiving GTP entity detects information element with invalid length in a
Request message, it shall send an appropriate error response with Cause IE value set to "Invalid length" together with
the type and instance of the offending IE.
Other Length field handling cases are specified below:
- If the received value of the Length field and the actual length of the fixed length IE are consistent, but the length
is greater than that expected by the fixed number of octets, then the extra octets shall be discarded.
- If the received value of the Length field and the actual length of the fixed length IE are consistent, but the length
is less than that expected by the fixed number of octets, this shall be considered an error, IE shall be discarded
and if the IE was received as a Mandatory IE or a verifiable Conditional IE in a Request message, an appropriate
error response with Cause IE value set to "Invalid length" together with the type and instance of the offending IE
shall be returned to the sender.
ETSI
- If the received value of the Length field and the actual length of the extendable length IE are consistent, but the
length is greater than that expected by the fixed number of octets preceding the extended field(s), then the extra
unknown octets shall be discarded.
- If the received value of the Length field and the actual length of the extendable length IE are consistent, but the
length is less than the number of fixed octets defined for that IE, preceding the extended field(s), this shall be
considered an error, IE shall be discarded and if the IE was received as a Mandatory IE or a verifiable
Conditional IE in a Request message, an appropriate error response with Cause IE value set to "Invalid length"
together with the type and instance of the offending IE shall be returned to the sender. Please refer to Table 8.1-1
for determining the number of fixed octets of an IE.
7.7.8 Semantically incorrect Information Element

Apart from Echo Request message, the receiver of a GTP signalling message Request including a mandatory or a
verifiable conditional information element with a semantically invalid Value shall discard the request, should log the
error, and shall send a response with Cause set to "Mandatory IE incorrect" together with a type and instance of the
offending IE.
The receiver of a GTP signalling message Response including a mandatory or a verifiable conditional information
element with a semantically invalid Value shall notify the upper layer that a message with this sequence number has
been received and should log the error.
If a GTP entity receives an information element with a value which is shown as reserved, it shall treat that information
element as invalid and should log the error. If the invalid IE is received in a Request, and it is a mandatory IE or a
verifiable conditional IE, the GTP entity shall send a response with Cause set to "Mandatory IE incorrect " together with
a type and instance of the offending IE.
The principle is: the use of reserved values invokes error handling; the use of spare values can be silently discarded and
so in the case of IEs with spare values used, processing shall be continued ignoring the spare values.
The receiver of a GTP signalling message including an optional information element with a Value that is not in the
range defined for this information element value shall discard this IE, but shall treat the rest of the message as if this IE
was absent and continue processing. The receiver shall not check the content of an information element field that is
defined as 'spare".
All semantically incorrect optional information elements in a GTP signalling message shall be treated as not present in
the message.
7.7.9 Unknown or unexpected Information Element

The receiver of a GTP message including an unexpected information element with known Type value, but with the
instance value that is not defined for this message shall discard the IE and log an error. The receiver shall process the
message.
An information element with a Type value which is defined in section 8.1 of the present specification but whose
Instance Value is not expected in the received GTP signalling message according to the grammar defined in section 7
of the present specification shall be silently discarded (skipped) and the rest of the message processed as if this
information element was not present.
NOTE: An Information Element in an encoded GTPv2 message or grouped IE is identified by the pair of IE Type
and Instance value.
7.7.10 Repeated Information Elements

An Information Element is repeated if there is more than one IE with the same IE Type and Instance in the scope of the
GTP message (scope of the grouped IE). Such an IE is a member in a list.
If an information element is repeated in a GTP signalling message in which repetition of the information element is not
specified, only the contents of the information element appearing first shall be handled and all subsequent repetitions of
the information element shall be ignored. When repetition of information elements is specified, only the contents of
specified repeated information elements shall be handled and all subsequent repetitions of the information element shall
be ignored.
ETSI
7.7.11 TFT Error Handling

TFT related error handling for EUTRAN is specified in 3GPP TS 24.301 [23] and for UTRAN/GERAN in 3GPP TS
24.008 [5].
7.8 Path Failure

Path failure handling procedures are specified in 3GPP TS 23.007 [17].
7.9 Restoration and Recovery

7.9.0 General
Restoration and Recovery procedures are specified in 3GPP TS 23.007 [17].
7.9.1 Delete PDN Connection Set Request

This message may be sent on the S2a, S2b, S5, S8, or S11 interfaces as specified in 3GPP TS 23.007 [17].
Table 7.9.1-1: Information Elements in a Delete PDN Connection Set Request

elements
MME-FQ-CSID C This IE shall be included when a MME reports a partial FQ-CSID 0
fault according to the requirements in 3GPP TS 23.007
[17]. More than one FQ-CSID may appear.
SGW-FQ-CSID C This IE shall be included when a SGW reports a partial FQ-CSID 1
PGW-FQ-CSID C Shall be included when a PGW reports a partial fault. More FQ-CSID 2
than one FQ-CSID may appear
ePDG-FQ-CSID C This IE shall be included when an ePDG reports a partial FQ-CSID 3
TWAN-FQ-CSID C This IE shall be included when a TWAN reports a partial FQ-CSID 4
Private Extension O This IE may be sent on the S2a, S2b, S5, S8 and S11 Private Extension VS
interfaces.
TEID of 0 shall be used for the Delete PDN Connection Set Request.
Only one type of FQ-CSID shall be included in each Delete PDN Connection Set Request, A mix of different types,
such as SGW-FQ-CSID and PGW-FQ-CSID shall not be used. A combined node, such as a collocated PGW/SGW,
shall send separate Delete PDN Connection Set Request for the PGW role and one for the SGW role if a partial fault
impacts more than one role.
7.9.2 Delete PDN Connection Set Response

This message is sent as a response to the Delete PDN Connection Set Request.
ETSI
Table 7.9.2: Information Elements in a Delete PDN Connection Set Response

elements
Cause M Cause 0
time
Private Extension O This IE may be sent on the S2a, S2b, S5, S8 and S11 Private Extension VS
interfaces.
TEID of 0 shall be used for the Delete PDN Connection Set Response.
The following Cause values are defined:
- "Request Accepted"
- "Request rejected"
- "System failure".
- "Mandatory IE incorrect".
- "Conditional IE missing".
- "Invalid message format".
"Request Accepted" indicates the receiving node was capable of storing a CSID value for each PDN connection for the
type of node (MME, SGW, PGW, TWAN or ePDG) in the Delete PDN Connection Set Request and has marked, or will
mark immediately, the PDN connections for deletion as specified in 3GPP TS 23.007 [17]. "Request Accepted" shall be
returned even if there are no PDN connections that match.
"Request rejected" shall be used when the receiver of the Delete PDN Connection Set Request is not capable of storing
at least one CSID value per PDN connection for the type of node (MME, SGW, PGW, TWAN or ePDG) received in the
Delete PDN Connection Set Request.
The SGW shall respond to the Delete PDN Connection Set Request independently, i.e. without waiting for replies.
7.9.3 Update PDN Connection Set Request

The SGW shall send this message to the PGW on S5/S8 according to the requirements in TS 23.007 [17].
Table 7.9.3-1: Information Elements in a Update PDN Connection Set Request

elements
MME-FQ-CSID C This IE shall be included for MME relocation without SGW FQ-CSID 0
relocation according to the requirements in 3GPP TS
23.007 [17].
SGW-FQ-CSID C This IE shall be included for MME relocation without SGW FQ-CSID 1
23.007 [17].
7.9.4 Update PDN Connection Set Response

This message is sent by the PGW to the SGW on S5/S8 in response to the Update PDN Connection Set Request
message.
ETSI
Table 7.9.4-1: Information Elements in a Update PDN Connection Set Response

elements
Cause M Cause 0
PGW-FQ-CSID C This IE shall be included for MME relocation without SGW FQ-CSID 0
23.007 [17].
time
The following Cause values are defined:
- "Request accepted"
- "Request rejected"
- "System failure".
- "Mandatory IE incorrect".
- "Conditional IE missing".
- "Invalid message format".
7.9.5 PGW Restart Notification

The direction of this message shall be from SGW to MME/S4-SGSN (see Table 6.1-1).
If both the SGW and the MME/S4-SGSN support the PRN feature (see subclause 8.83), a PGW Restart Notification
shall be sent when the SGW detects that the peer PGW has restarted, and a PGW Restart Notification may be sent when
the SGW detects that the peer PGW has failed and not restarted, as specified in 3GPP TS 23.007 [17].
Table 7.9.5-1: Information Elements in PGW Restart Notification

elements
PGW S5/S8 IP M IP Address 0
Address for Control
Plane or PMIP
SGW S11/S4 IP M IP Address 1
Address for Control
Plane
Cause CO The SGW shall send the Cause IE with the value "PGW Cause 0
not responding" if it sends the PGW Restart Notification to
notify that the peer PGW has failed and not restarted.
7.9.6 PGW Restart Notification Acknowledge

The PGW Restart Notification Acknowledge shall be sent as a response of PGW Restart Notification to indicate that the
MME/S4-SGSN deletes all the relevant PDN connections as specified in 3GPP TS 23.007 [17] if the Cause IE includes
an acceptance cause.
ETSI
Table 7.9.6-1: Information Elements in PGW Restart Notification Acknowledge

elements
Cause M Cause 0
7.9.7 PGW Downlink Triggering Notification

The direction of this message shall be from PGW to SGW and from SGW to MME(s)/S4-SGSN(s).
The PGW Downlink Triggering Notification shall be sent as part of the PGW triggered SGW restoration procedure if
the MME/S4-SGSN, SGW and PGW support this optional feature as specified in 3GPP TS 23.007 [17].
Table 7.9.7-1: Information Elements in PGW Downlink Triggering Notification

elements
IMSI M IMSI 0
MME/S4-SGSN C This IE shall be included over S5 /S11/S4 interface as IP Address 0
identifier specified in 3GPP TS 23.007 [17].
PGW S5 F-TEID for O This IE may be included over the S5 interface. If present, it F-TEID 0
GTP or PMIP Control shall contain the PGW S5 F-TEID value assigned during
Plane (NOTE 2) the PDN connection establishment.
(NOTE 1)
CO The PGW shall include this IE over the S5 interface
according to the conditions specified in subclauses
20.2.7.1 of 3GPP TS 23.007 [17].
CO If the SGW receives this IE it shall forward the IE to the
MME/S4-SGSN over the S11/S4 interface.
This IE shall include the PGW S5 IP address for control
plane and TEID for GTP based S5 case or the uplink GRE
key for control plane in the PMIP based S5 case.
NOTE 1: The SGW shall set the header TEID value in the PGW Downlink Triggering Acknowledge to the
PGW's Control Plane TEID if the 'PGW S5 F-TEID for GTP or PMIP Control Plane' IE is present in
the PGW Downlink Triggering Notification message.
NOTE 2: In earlier versions of this specification, the name of this IE was 'Sender F-TEID for Control Plane'.
The name was changed when extending the applicability of the IE to S4/S11.
7.9.8 PGW Downlink Triggering Acknowledge

The PGW Downlink Triggering Acknowledge message shall be sent as a response to a PGW Downlink Triggering
Notification message if the MME/S4-SGSN, SGW and PGW support the PGW triggered SGW restoration feature as
ETSI
Table 7.9.8-1: Information Elements in PGW Downlink Triggering Acknowledge

elements
Cause M Cause 0
IMSI C This IE shall be included on S11/S4 interface if the Cause IMSI 0
is indicating the rejection value "Context Not Found" and if
the MME/S4-SGSN identifier is included in the
corresponding PGW Downlink Triggering Notification
message.
MME/S4-SGSN C This IE shall be included on S11/S4 interface if the Cause IP Address 0
identifier is indicating the rejection value "Context Not Found" and if
the MME/S4-SGSN identifier is included in the
corresponding PGW Downlink Triggering Notification
message.
7.10 Fallback to GTPv1 mechanism

An EPC entity shall assume that each GTP processing node that it is about to communicate with is GTPv2 capable.
Before the first GTP tunnel is setup for a given UE/node, the EPC node shall always send a version 2 (GTPv2) message
to a peer node. As an exception, during an inter-SGSN handover, even if the target SGSN is GTPv2 capable, the source
SGSN shall send a GTPv1 message "Forward Relocation Request" to the target SGSN if the PDP Context(s) for this UE
were established to GGSN(s), or if there is no active PDP context and the source or target SGSN does not support
SRNS relocation w/o PDN connection over GTPv2 (see subclause 7.3.1).
A GTPv2 entity shall fallback to GTPv1 only if either a "Version Not Supported" message in GTPv1 format as
specified in 3GPP TS 29.060 [4] is received from the peer node (this indicates that the peer GTP entity does not support
GTPv2), or if a GTPv2 message is received with Cause value "Fallback to GTPv1".
If a GTPv1 "Version Not Supported" message in received, a GTPv2 entity may fallback to GTPv1. 3GPP TS 23.401 [3]
(see annex D) and 3GPP TS 23.060 [35] specify GTP version usage during the mobility between a UTRAN/GERAN
and an E-UTRAN.
A GTPv2 entity may receive a GTPv2 message with a Cause value "Fallback to GTPv1" in the following cases:
- an S4 SGSN receives the Cause code "Fallback to GTPv1" in a GTPv2 Context Response message over S16
interface. When an UE has activated a PDP context via S4 SGSN to GGSN and inter-SGSN RAU is underway,
the old S4 SGSN shall include the Cause value "Fallback to GTPv1" in a GTPv2 Context Response message
over S16 interface. In this case, the new S4 SGSN shall abort the ongoing GTPv2 procedure and send a GTPv1
"SGSN Context Request" message to the old S4 SGSN. The fallback to GTPv1 is performed only for this UE in
the current procedure.
- an MME receives the Cause code "Fallback to GTPv1" in a GTPv2 Context Response message over the S3
interface. When an UE has active PDP context(s) via an S4 SGSN and a TAU is underway, the old S4 SGSN
may include the Cause value "Fallback to GTPv1" in a GTPv2 Context Response message over the S3 interface.
In this case, the MME shall abort the ongoing GTPv2 procedure and should send a GTPv1 "SGSN Context
Request" message to the old S4 SGSN. The fallback to GTPv1 is performed only for this UE.
Fallback to GTPv1 shall not occur on already established GTP tunnels without change of the peer nodes of the
communication bearer.
7.11 Fallback to GTPv0

Fallback from GTPv2 to GTPv0 shall not be supported. Therefore, GTPv2 entity should not listen to the well-known
GTPv0 port 3386.
ETSI
7.12 Trace Management Messages

7.12.1 Trace Session Activation
The Trace Session Activation message shall be sent on S11/S4 by the MME/SGSN to the SGW, on S2a/S2b by the
TWAN/ePDG to the PGW, and on S5/S8 by the SGW to the PGW when session trace is activated for a particular IMSI
or IMEI for a UE that is attached and active or attached and idle.
Table 7.12.1-1: Information Elements in a Trace Session Activation

elements
IMSI C The MME/SGSN shall include the IMSI in the message on IMSI 0
the S11/S4 interface except for the case:
UICCless.
The IMSI shall be included in the message on the S11/S4

interface but not used as an identifier
authenticated.
The SGW shall forward this IE to the PGW on S5/S8 if

received on S11/S4.
The TWAN/ePDG shall include this IE on the S2a/S2b

interface.
Trace Information M Trace Information 0
ME Identity (MEI) C The MME/SGSN shall include the ME Identity (MEI) IE on MEI 0
the S11/S4 interface:
UICCless

authenticated
In other cases, the MME shall include the ME Identity

(MEI) IE on the S11 interface, if available.
The SGW shall forward this IE to the PGW on S5/S8 if

received on S11/S4.
CO The TWAN/ePDG shall include the ME Identity (MEI) IE on
the S2a/S2b interface, if it is available.
7.12.2 Trace Session Deactivation

The Trace Session Deactivation message shall be sent on S11/S4 by the MME/SGSN to the SGW, on S2a/S2b by the
TWAN/ePDG to the PGW, and on S5/S8 by the SGW to the PGW when session trace is deactivated for a particular
IMSI or IMEI for a UE that is attached and active or attached and idle.
Table 7.12.2-1: Information Elements in a Trace Session Deactivation

elements
Trace Reference M Trace Reference 0
ETSI
7.13 MBMS Messages

7.13.1 MBMS Session Start Request
The MBMS Session Start Request message shall be sent on the Sm/Sn interface by the MBMS GW to the MME/SGSN
as specified in 3GPP TS 23.246 [37] and 3GPP TS 23.007 [13].
ETSI
Table 7.13.1-1: Information Elements in a MBMS Session Start Request

elements
Sender F-TEID for M F-TEID 0
Control Plane
Temporary Mobile M TMGI 0
Group Identity (TMGI)
MBMS Session M MBMS Session 0
Duration Duration
MBMS Service Area M MBMS Service 0
Area
MBMS Session C This IE shall be forwarded to MME/SGSN if it is provided MBMS Session 0
Identifier by the BM-SC. Identifier
MBMS Flow Identifier C This IE shall be forwarded to MME/SGSN if it is provided MBMS Flow 0
by the BM-SC. Identifier
QoS profile M See NOTE 1. Bearer QoS 0
MBMS IP Multicast M See NOTE 2. MBMS IP 0
Distribution Multicast
Distribution
time.
MBMS Time to Data CO This IE shall be forwarded to MME/SGSN if it is received MBMS Time to 0
Transfer from the BM-SC. Data Transfer
MBMS Data Transfer CO This IE shall be forwarded to the MME if it is received from Absolute Time of 0
Start the BM-SC. MBMS Data
Transfer
MBMS Flags CO This IE shall be included if any one of the applicable flags MBMS Flags 0
is set to 1.
Applicable flags:
- MBMS Session Re-establishment Indication: this
flag shall be set to 1 on the Sm/Sn interfaces if the
MBMS Session Start Request message is used to
re-establish an MBMS session (see 3GPP TS
23.007 [13]).
MBMS Alternative IP CO If the MBMS GW supports both IPv4 and IPv6 M1 MBMS IP 1
Multicast Distribution multicast address types, the MBMS GW may include this Multicast
IE on the Sm interface to provide an alternative MBMS IP Distribution
Multicast Distribution Address with a different address type
(i.e. IPv4 or IPv6) than the one provided in the MBMS IP
Multicast Distribution IE.
See NOTE 2.
MBMS Cell List CO The MBMS GW shall include this IE on the Sm interface if ECGI-List 0
a MBMS Cell List was received from the BM-SC.
See NOTE 3.
NOTE 1: The uplink GBR and uplink MBR shall be ignored by MME/SGSN as specified in Section 20.5 of
3GPP TS 29.061 [38].
NOTE 2: If the MBMS GW supports both IPv4 and IPv6 M1 multicast address types, the MBMS GW may
provide both IPv4 and IPv6 MBMS IP Multicast Distribution addresses on the Sm interface by
including the MBMS IP Multicast Distribution IE and the MBMS Alternative IP Multicast Distribution IE
in the MBMS Session Start Request. In this case, one of these IEs shall carry an IP Multicast
Distribution Address and an IP Multicast Source Address for IPv6 and the other IE shall carry IPv4
addresses. Both IEs shall contain the same C-TEID value.
NOTE 3: The MBMS Cell List can contain from 1 up to 4096 cells (see 3GPP TS 29.061 [38]).
7.13.2 MBMS Session Start Response

The MBMS Session Start Response message shall be sent as a response to the MBMS Session Start Request message
on the Sm/Sn interface by the MME/SGSN to the MBMS GW.
ETSI
Table 7.13.2-1: Information Elements in a MBMS Session Start Response

elements
Cause M Cause 0
Sender F-TEID for M F-TEID 0
Control Plane
MBMS Distribution C This IE shall be included on the Sn interface. MBMS 0
Acknowledge Distribution
Acknowledge
Sn-U SGSN F-TEID C This IE shall be included on the Sn interface if some RNCs F-TEID 1
have not accepted IP multicast distribution.
time.
7.13.3 MBMS Session Update Request

The MBMS Session Update Request message shall be sent on the Sm/Sn interface by the MBMS GW to the
MME/SGSN as specified in 3GPP TS 23.246 [37] and 3GPP TS 23.007 [13].
Table 7.13.3-1: Information Elements in a MBMS Session Update Request

elements
MBMS Service Area C This IE shall be forwarded to MME/SGSN if it is provided MBMS Service 0
by the BM-SC. Area
Temporary Mobile M TMGI 0
Group Identity (TMGI)
Sender F-TEID for O F-TEID 0
Control Plane
MBMS Session M MBMS Session 0
Duration Duration
QoS profile M See NOTE 1. Bearer QoS 0
MBMS Session C This IE shall be forwarded to MME/SGSN if it is provided MBMS Session 0
Identifier by the BM-SC. Identifier
MBMS Flow IdentifierC This IE shall be forwarded to MME/SGSN if it is provided MBMS Flow 0
by the BM-SC. Identifier
MBMS Time to Data CO This IE shall be forwarded to MME/SGSN if it is provided MBMS Time to 0
Transfer by the BM-SC. Data Transfer
Start the BM-SC. MBMS Data
Transfer
MBMS Cell List CO The MBMS GW shall include this IE on the Sm interface if ECGI List0
a MBMS Cell List was received from the BM-SC.
See NOTE 2.
NOTE 1: The uplink GBR and uplink MBR shall be ignored by MME/SGSN as specified in Section 20.5 of
3GPP TS 29.061 [38].
NOTE 2: The MBMS Cell List can contain from 1 up to 4096 cells (see 3GPP TS 29.061 [38]).
7.13.4 MBMS Session Update Response

The MBMS Session Update Response message shall be sent as a response to the MBMS Session Update Request
message on the Sm/Sn interface by the MME/SGSN to the MBMS GW.
ETSI
Table 7.13.4-1: Information Elements in a MBMS Session Update Response

elements
Cause M Cause 0
MBMS Distribution C This IE shall be included on the Sn interface if service area MBMS 0
Acknowledge is changed. Distribution
Acknowledge
Sn-U SGSN F-TEID C This IE shall be included on the Sn interface if any of the F-TEID 0
newly added RNCs have not accepted IP multicast
distribution.
time.
7.13.5 MBMS Session Stop Request

The MBMS Session Stop Request message shall be sent on the Sm/Sn interface by the MBMS GW to the MME/SGSN
as specified in 3GPP TS 23.246 [37] and 3GPP TS 23.007 [13].
Table 7.13.5-1: Information Elements in a MBMS Session Stop Request
Info specified in P Condition / Comment IE Type Ins.

Table 8.4-1.rmation
elements
MBMS Flow IdentifierC This IE shall be forwarded to MME/SGSN if it is provided MBMS Flow 0
by the BM-SC. See NOTE 1. Identifier
Stop the BM-SC. MBMS Data
Transfer
MBMS Flags CO This IE shall be included if any one of the applicable flags MBMS Flags 0
is set to 1.
Applicable flags:
- Local MBMS Bearer Context Release Indication:
this flag shall be set to 1 on the Sm/Sn interfaces if
the MBMS Session Stop Request message is used
to release the MBMS bearer context locally in the
MME/SGSN (see 3GPP TS 23.007 [13]).

NOTE 1: The conditional MBMS Flow Identifier IE is redundant as MBMS Session Stop Request message is
sent over non-zero TEID header. The receiver may ignore the MBMS Flow Identifier IE.
7.13.6 MBMS Session Stop Response

The MBMS Session Stop Response message shall be sent as a response to the MBMS Session Stop Request message on
the Sm/Sn interface by the MME/SGSN to the MBMS GW.
Possible Cause values are are specified in Table 8.4-1.
Table 7.13.6-1: Information Elements in a MBMS Session Stop Response

elements
Cause M Cause 0
time.
ETSI
8 GTP-C Information Elements
8.1 Information Element Types

A GTP control plane (signalling) message may contain several information elements. In order to have forward
compatible type definitions for the GTPv2 information elements, all of them shall be TLIV (Type, Length, Instance,
Value) coded. GTPv2 information element type values are specified in the Table 8.1-1. The last column of this table
indicates whether the information element is:
- Fixed Length: the IE has a fixed set of fields, and a fixed number of octets.
- Variable Length: the IE has a fixed set of fields, and has a variable number of octets.
For example, the last octets may be numbered similar to "5 to (n+4)". In this example, if the value of the length
field, n, is 0, then the last field is not present.
- Extendable: the IE has a variable number of fields, and has a variable number of octets.
The last fields are typically specified with the statement: "These octet(s) is/are present only if explicitly
specified". The legacy receiving entity shall ignore the unknown octets.
In order to improve the efficiency of troubleshooting, it is recommended that the information elements should be
arranged in the signalling messages as well as in the grouped IEs, according to the order the information elements are
listed in the message definition table or grouped IE definition table in section 7. However the receiving entity shall be
prepared to handle the messages with information elements in any order.
Within information elements, certain fields may be described as spare. These bits shall be transmitted with the value set
to 0. To allow for future features, the receiver shall not evaluate these bits. GTPv2-C information elements that have
similar semantics in GTPv1-C shall be converted into GTPv1-C format, as specified in TS 29.060 [4], before sending
them to a pre-R8 GSN.
ETSI
Table 8.1-1: Information Element types for GTPv2
IE Type Information elements Comment / Reference Number of Fixed Octets

value
(Decimal)
0 Reserved
1 International Mobile Subscriber Identity (IMSI) Variable Length / 8.3 Not Applicable
2 Cause Variable Length / 8.4 Not Applicable
3 Recovery (Restart Counter) Variable Length / 8.5 Not Applicable
4 to 34 Reserved for S101 interface See 3GPP TS 29.276 [14] See 3GPP TS 29.276 [14]
35 to 50 Reserved for S121 interface See 3GPP TS 29.276 [14] See 3GPP TS 29.276 [14]
51 STN-SR See 3GPP TS 29.280 [15] See 3GPP TS 29.280 [15]
52 to 70 Reserved for Sv interface See 3GPP TS 29.280 [15] See 3GPP TS 29.280 [15]
71 Access Point Name (APN) Variable Length / 8.6 Not Applicable
72 Aggregate Maximum Bit Rate (AMBR) Fixed Length / 8.7 8
73 EPS Bearer ID (EBI) Extendable / 8.8 1
74 IP Address Variable Length / 8.9 Not Applicable
75 Mobile Equipment Identity (MEI) Variable Length / 8.10 Not Applicable
76 MSISDN Variable Length / 8.11 Not Applicable
77 Indication Extendable / 8.12 2
78 Protocol Configuration Options (PCO) Variable Length / 8.13 Not Applicable
79 PDN Address Allocation (PAA) Variable Length / 8.14 Not Applicable
80 Bearer Level Quality of Service (Bearer QoS) Extendable / 8.15 22
81 Flow Quality of Service (Flow QoS) Extendable / 8.16 21
82 RAT Type Extendable / 8.17 1
83 Serving Network Extendable / 8.18 3
84 EPS Bearer Level Traffic Flow Template (Bearer TFT) Variable Length / 8.19 Not Applicable
85 Traffic Aggregation Description (TAD) Variable Length / 8.20 Not Applicable
86 User Location Information (ULI) Extendable / 8.21 "f+4-4" (See Figure 8.21-1)
87 Fully Qualified Tunnel Endpoint Identifier (F-TEID) Extendable / 8.22 9/21/25
88 TMSI Variable Length / 8.23 Not Applicable
89 Global CN-Id Variable Length / 8.24 Not Applicable
90 S103 PDN Data Forwarding Info (S103PDF) Variable Length / 8.25 Not Applicable
91 S1-U Data Forwarding Info (S1UDF) Variable Length/ 8.26 Not Applicable
92 Delay Value Extendable / 8.27 1
93 Bearer Context Extendable / 8.28 Not Applicable
94 Charging ID Extendable / 8.29 4
95 Charging Characteristics Extendable / 8.30 2
96 Trace Information Variable Length / 8.31 Not Applicable
97 Bearer Flags Extendable / 8.32 1
98 Reserved
99 PDN Type Extendable / 8.34 1
100 Procedure Transaction ID Extendable / 8.35 1
101 Reserved
102 Reserved
103 MM Context (GSM Key and Triplets) Extendable / 8.38 "r+1-4" (See Figure 8.38-1)
104 MM Context (UMTS Key, Used Cipher and Extendable / 8.38 "r+1-4" (See Figure 8.38-2)
Quintuplets)
105 MM Context (GSM Key, Used Cipher and Quintuplets) Extendable / 8.38 "r+1-4" (See Figure 8.38-3)
106 MM Context (UMTS Key and Quintuplets) Extendable / 8.38 "r+1-4" (See Figure 8.38-4)
107 MM Context (EPS Security Context, Quadruplets and Extendable / 8.38 "s+64-4" (See Figure 8.38-5)
Quintuplets)
108 MM Context (UMTS Key, Quadruplets and Extendable / 8.38 "r+1-4" (See Figure 8.38-6)
Quintuplets)
109 PDN Connection Extendable / 8.39 Not Applicable
110 PDU Numbers Extendable / 8.40 9
111 P-TMSI Variable Length / 8.41 Not Applicable
112 P-TMSI Signature Variable Length / 8.42 Not Applicable
113 Hop Counter Extendable / 8.43 1
114 UE Time Zone Extendable / 8.44 2
115 Trace Reference Fixed Length / 8.45 6
116 Complete Request Message Variable Length / 8.46 Not Applicable
117 GUTI Variable Length / 8.47 Not Applicable
118 F-Container Variable Length / 8.48 Not Applicable
119 F-Cause Variable Length / 8.49 Not Applicable
120 PLMN ID Variable Length / 8.50 Not Applicable
121 Target Identification Variable Length / 8.51 Not Applicable
122 Reserved
123 Packet Flow ID Variable Length / 8.53 Not Applicable
124 RAB Context Fixed Length / 8.54 9
125 Source RNC PDCP Context Info Variable Length / 8.55 Not Applicable
126 UDP Source Port Number Extendable / 8.56 2
127 APN Restriction Extendable / 8.57 1
ETSI

value
(Decimal)
128 Selection Mode Extendable / 8.58 1
129 Source Identification Variable Length / 8.59 Not Applicable
130 Reserved
131 Change Reporting Action Variable Length / 8.61 Not Applicable
132 Fully Qualified PDN Connection Set Identifier (FQ- Extendable / 8.62 "q+1-4" (See Figure 8.62-1)
CSID)
133 Channel needed Variable Length / 8.63 Not Applicable
134 eMLPP Priority Variable Length / 8.64 Not Applicable
135 Node Type Extendable / 8.65 1
136 Fully Qualified Domain Name (FQDN) Variable Length / 8.66 Not Applicable
137 Transaction Identifier (TI) Variable Length / 8.68 Not Applicable
138 MBMS Session Duration Extendable / 8.69 3
139 MBMS Service Area Variable Length / 8.70 Not Applicable
140 MBMS Session Identifier Extendable / 8.71 1
141 MBMS Flow Identifier Extendable / 8.72 2
142 MBMS IP Multicast Distribution Extendable / 8.73 "m+1-4" (See Figure 8.73-1)
143 MBMS Distribution Acknowledge Extendable / 8.74 1
144 RFSP Index Fixed Length / 8.77 2
145 User CSG Information (UCI) Extendable / 8.75 8
146 CSG Information Reporting Action Extendable / 8.76 1
147 CSG ID Extendable / 8.78 4
148 CSG Membership Indication (CMI) Extendable / 8.79 1
149 Service indicator Fixed Length / 8.80 1
150 Detach Type Fixed Length / 8.81 1
151 Local Distiguished Name (LDN) Variable Length / 8.82 Not Applicable
152 Node Features Extendable / 8.83 1
153 MBMS Time to Data Transfer Extendable / 8.84 1
154 Throttling Extendable / 8.85 2
155 Allocation/Retention Priority (ARP) Extendable / 8.86 1
156 EPC Timer Extendable / 8.87 1
157 Signalling Priority Indication Extendable / 8.88 1
158 Temporary Mobile Group Identity (TMGI) Extendable / 8.89 6
159 Additional MM context for SRVCC Extendable / 8.90 "e-4" (See Figure 8.90-1)
160 Additional flags for SRVCC Extendable / 8.91 1
161 Reserved
162 MDT Configuration Extendable / 8.93 "q-4" (See Figure 8.93-1)
163 Additional Protocol Configuration Options (APCO) Extendable / 8.94 "m-4" (See Figure 8.94-1)
164 Absolute Time of MBMS Data Transfer Extendable / 8.95 8
165 H(e)NB Information Reporting Extendable / 8.96 1
166 IPv4 Configuration Parameters (IP4CP) Extendable / 8.97 5
167 Change to Report Flags Extendable / 8.98 1
168 Action Indication Extendable / 8.99 1
169 TWAN Identifier Extendable / 8.100 "k+6-4" (See Figure 8.100-1)
170 ULI Timestamp Extendable / 8.101 4
171 MBMS Flags Extendable / 8.102 1
172 RAN/NAS Cause Extendable / 8.103 "m-4" (See Figure 8.103-1)
173 CN Operator Selection Entity Extendable / 8.104 1
174 Trusted WLAN Mode Indication Extendable / 8.105 1
175 Node Number Extendable / 8.106 "p-4" (See Figure 8.106-1)
176 Node Identifier Extendable / 8.107 "q-4" (See Figure 8.107-1)
177 Presence Reporting Area Action Extendable / 8.108 "t-4" (See Figure 8.108-1)
178 Presence Reporting Area Information Extendable / 8.109 4
179 TWAN Identifier Timestamp Extendable / 8.110 4
180 Overload Control Information Extendable / 8.111 Not Applicable
181 Load Control Information Extendable / 8.112 Not Applicable
182 Metric Fixed Length / 8.113 1
183 Sequence Number Fixed Length / 8.114 4
184 APN and Relative Capacity Extendable / 8.115 "m-4" (See Figure 8.115
185 WLAN Offloadability Indication Extendable / 8.116 1
186 Paging and Service Information Extendable / 8.117 m-4 (See Figure 8.117-1)
187 Integer Number Variable / 8.118 Not Applicable
188 Millisecond Time Stamp Extendable / 8.119 6
189 Monitoring Event Information Extendable / 8.120 "k+2-4" (See Figure 8.120-1)
190 ECGI List Extendable / 8.121 "m*7+2" (See Figure 8.121-1)
191 Remote UE Context Extendable / 8.122 Not Applicable
192 Remote User ID Variable Length / 8.123 Not Applicable
193 Remote UE IP information Variable Length / 8.124 Not Applicable
194 to 253 Spare. For future use.
ETSI

value
(Decimal)
254 Special IE type for IE Type Extension See NOTE 2 Not Applicable
255 Private Extension Variable Length / 8.67 Not Applicable
256 to 65535 Spare. For future use.
NOTE 1: The size of the TLI (Type, Length and Instance) fields, i.e "4" octets, has been subtracted from the number of
the fixed octets of the "Fixed Length" and "Extendable" IEs. Hence for some of the "Extendable" IEs, for which
the length is defined in terms of variable number of octets, "4" is explicitly subtracted while defining the fixed
number of octets. E.g. Length of User Location Information is defined as "f+4" and fixed number of octets for
the same is defined as "f+4-4".
NOTE 2: The IE Type value 254 indicates that the IE Type shall be further identified by an IE Type Extension field; see
subclause 8.2.1A. A GTP-C entity which does not support any IE Type encoded with an IE Type Extension
field shall ignore an IE received with the IE Type value 254.
8.2 Information Element Format

8.2.1 General
Figure 8.2-1 depicts the format of an information element.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = xxx (decimal)
2 to3 Length = n
4 Spare Instance
5 to (n+4) IE specific data or content of a grouped IE
Figure 8.2-1: Information Element Format
An IE has the following mandatory fields:
- Type field: This field indicates the type of Information Element. The valid values of the IE type are defined in
clause 8.1.
- Length: This field contains the length of the information element excluding the first four octets, which are
common for all information elements (Type, Length and the contents of octet 4) and is denoted "n" in Figure 8.2-
1. For all the length fields, bit 8 of the lowest numbered octet is the most significant bit and bit 1 of the highest
numbered octet is the least significant bit.
- Instance: This field shall be used to differentiate amongst different parameters in one specific message which use
the same information element type (see also subclause 6.1.3 "Information Element Instance").
An IE is said to be TLIV (Type, Length, Instance, Value) encoded.
8.2.1A Information Element with an IE Type Extension field

Figure 8.2.1A-1 depicts the format of an information element with an IE Type Extension field.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 254 (decimal)
2 to 3 Length = n
4 Spare Instance
5 to 6 IE Type Extension
7 to n+4 IE specific data or content of a group IE
Figure 8.2.1A-1: Information Element with an IE Type Extension field
The IE Type in octet 1 of an information element with an IE Type Extension field shall be set to 254. Such IE shall be
further identified by the value encoded in the IE Type Extension field in octets 5 and 6.
ETSI
The value of the IE Type Extension shall be encoded in full hexadecimal representation from 256 up to 65535. This
field indicates the type of the Information Element and the valid values of the IE type Extension field are defined in
subclause 8.1.
The semantics of the Length and Instance field remain the same as specified in subclause 8.2.1.
8.2.2 Handling ASN.1/PER encoded parameters

During the TAU/RAU/HO procedures MME/S4-SGSN GTPv2 entities send some of the RANAP/S1AP/BSSGP
parameters to a GTPv2 peer. Copying of the BSSGP parameters into GTPv2 IEs is straightforward. RANAP and S1AP,
however, use ASN.1/PER encoding, which is different from GTPv2 specific TLV encoding.
Transparent copying of RANAP/S1AP parameters across GTPv2 interfaces:
- a GTPv2 entity shall transparently copy the respective information into one or more octets of the GTPv2 IE as
specified in Annex B and clause 8.48. With this approach, GTPv2 will not be impacted if the contents of such
RANAP/S1AP parameter changes over the time.
Non-transparent copying of RANAP/S1AP parameters across GTPv2 interfaces:
- GTPv2 entity decodes ASN.1/PER parameter and shall encode the value(s) into one or more octets of the GTPv2
IE according to what is specified in the present document.
8.3 International Mobile Subscriber Identity (IMSI)

International Mobile Subscriber Identity (IMSI) is transferred via GTP tunnels. The sending entity copies the value part
of the IMSI into the Value field of the IMSI IE. IMSI is defined in 3GPP TS 23.003 [2].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Number digit 2 Number digit 1
… … …
n+4 Number digit m Number digit m-1
Figure 8.3-1: IMSI
Octets 5 to (n+4) represent the IMSI value in international number format as described in ITU-T Rec E.212 [64],
encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of
digits, bits 8 to 5 of the last octet are encoded with the filler "1111". The maximum number of digits is 15.
8.4 Cause
Cause IE is coded as depicted in Figure 8.4-1.
. Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Cause value
6 Spare PCE BCE CS
a(n+1) Type of the offending IE
a(n+2) to Length of the offending IE = 0
a(n+3)
a(n+4) Spare Instance
Figure 8.4-1: Cause
Cause is a variable length IE, which may have either of the following two lengths values:
ETSI
- If n = 2, a = 0 and the Cause IE shall be 6 octets long. Therefore, octets "a(n+1) to a(n+4)" will not be present.
- If n = 6, a = 1 and the Cause IE will be 10 octets long.
For PMIP based S5/S8, the SGW/MAG shall do the mapping between GTPv2 Cause IE and respective PMIPv6 IE as
The following bits within Octet 6 indicate:
- Bits 8 to 4: Spare, for future use and set to zero
- Bit 1 – CS (Cause Source): If this bit is set to 1, it indicates that the corresponding error cause is originated by
the remote node (i.e., the MME/SGSN to a PGW, or the PGW to an MME/SGSN). This bit is set to 0 to denote
that the corresponding error cause is originated by the node sending the message.
The CS should be set to 1 by the SGW when the SGW relay a response message with cause value from the
MME/SGSN to the PGW or from the PGW to the MME/SGSN. For PMIP based S5/S8, the SGW shall set the
CS bit to 1 when the SGW/MAG relay a response message with the cause value from the PGW/LMA to the
MME/SGSN.
- Bit 2 – BCE (Bearer Context IE Error): If this bit is set to 1, it indicates that the corresponding rejection cause is
due to the error in the Bearer Context IE. This bit shall be discarded if the cause value is one of Acceptance
cause value as given in table 8.4-1.
- Bit 3 – PCE (PDN Connection IE Error): If this bit is set to 1, it indicates that the corresponding rejection cause
is due to the error in the PDN Connection IE. This bit shall be discarded if the cause value is one of Acceptance
cause value as given in table 8.4-1.
The Cause value shall be included in a response message. In a response message, the Cause value indicates the
acceptance or the rejection of the corresponding request message. The Cause value indicates the explicit reason for the
rejection.
If the rejection is due to a mandatory IE or a verifiable conditional IE is faulty or missing, the offending IE shall be
included within an additional field "a(n+1) to a(n+4)". Only Type and Instance fields of the offending IE that caused the
rejection have a meaning. The length in the Octet 8-9 and spare bits in the Octet 10 shall be set to "0". In this case, the
value of "n" shall be "6". Otherwise, the value of "n" is equal to "2".
The Cause may also be included in the request message. In a request message, the Cause value indicates the reason for
the request.
"Request accepted" is returned when the GTPv2 entity has accepted a control plane request.
"Context Not Found" is used in the response message by a GTP entity when it receives a message for which it does not
have context, e.g. TEID-C or EBI is not known. When "Context Not Found" is received at Bearer Context IE level, it
means the bearer context is unknown in the peer. When "Context Not Found" is received at message level together with
a known TEID-C in the GTPv2-C header in the response message, this indicates some bearer contexts are not known in
the peer; the sender of the request message should further determine, based on the bearer context(s) included in the
request message, that:
- if the default bearer is unknown, this means the PDN connection is not known in the peer;
- if one or more dedicated bearers are unknown, this means only those dedicated bearer contexts are not known in
the peer.
"Context Not Found" may be used by the PGW in the Create Session Response message during the non-3GPP to 3GPP
access handover procedures, if the request corresponds to the handover of a PDN connection which does not exist in the
PGW.
"Context Not Found" may be used by the PGW in the Create Session Response message during the 3GPP to non-3GPP
access handover procedures, if the request corresponds to the handover of a PDN connection which does not exist in the
PGW.
"Service not supported" is used by the GTP entity when it receives a message, which corresponds to a feature or a
service which is not supported by the node.
"Service denied" is used when the requested service cannot be granted.
ETSI
"System failure" is used by the GTP entity to indicate a generic error condition.
"No resources available" is used by the GTP entity to indicate the temporary unavailability of the resource(s) to process
the received request.
"Semantic error in the TFT operation", "Syntactic error in the TFT operation", "Semantic errors in packet filter(s)",
"Syntactic errors in packet filters(s)", "UE context without TFT already activated", "Semantic error in the TAD
operation" and "Syntactic error in the TAD operation" are indications of error cases involving TFT(s)/TAD(s) as
specified in subclause 7.7.11 in this specification.
"Missing or unknown APN" is used by the PGW when it does not support the Access Point Name, received in Create
Session Request message.
"Relocation failure" is used by the target MME/S4-SGSN to indicate the source MME/S4-SGSN that the relocation has
failed.
"Relocation failure due to NAS message redirection" is used by the new MME/S4-SGSN to indicate to the old
MME/S4-SGSN that the TAU/RAU procedure is not successful due to NAS message redirection as described in 3GPP
TS 23.401 [3].
"Denied in RAT" is used by the GTP entity to indicate that the requested service is not accepted in the RAT.
"Preferred PDN type not supported" is used by the PGW to indicate that the PDN type received in the Create Session
Request message is not supported by the PGW for the PDN corresponding to the received Access Point Name.
"Protocol type not supported" is used by the SGW to indicate that the S5/S8 protocol type requested by the MME/S4-
SGSN is not supported by it.
"UE not responding" is used by the MME/S4-SGSN to indicate that the UE is not responding to the request initiated by
the network, e.g. Paging.
"UE refuses" is used by the GTP entity to indicate that the UE, without specifying further detail, rejected the request
from the network.
"Unable to page UE" is used by the MME/S4-SGSN to indicate its inability to page the UE, temporarily.
"User authentication failed" is used by the GTP entity to indicate that the request is rejected due to failure in
authentication/security procedure.
"APN access denied – no subscription" is used to indicate that the PGW has denied the user access to an APN because a
subscription is required, but the subscriber does not have the necessary subscription.
"Remote peer not responding" is used by the SGW for the messages spanning through two interfaces. This cause value
is returned by the SGW to the MME/S4-SGSN or PGW in a response message where no response message is received
from the PGW or MME/S4-SGSN.
"Collision with network initiated request" is used by the PGW to indicate that the UE-initiated bearer resource
allocation/modification request is rejected since the PGW has requested a bearer resource allocation/modification for
the same service using a network-initiated procedure.
"Unable to page UE due to Suspension" is used by the MME/S4-SGSN to indicate that the UE has not been paged
because the bearers of the UE are in a suspended state.
"APN Restriction type Incompatible with currently active PDN connection" is used by the PGW to indicate that the
newly requested PDN connection has APN restriction value that is not compatible with the currently active PDN
connection(s)'s APN restriction value(s).
"Invalid peer" is used by the SGW to indicate that currently the UE is being managed by the different node (e.g.
MME/S4-SGSN) than the node (e.g. S4-SGSN/MME) which has sent the Delete Session Request message.
"Invalid Reply from remote peer" is used by the SGW for the messages spanning through two interfaces. This cause
value is returned by the SGW to the MME/SGSN or PGW in a reply message where the corresponding reply message
on S5/S8 or S11/S4 from the PGW or MME/SGSN is not decoded as valid.
"Temporarily rejected due to handover/TAU/RAU procedure in progress" is used by the MME/S4-SGSN for the bearer
related procedure initiated by the PGW. When the handover/TAU/RAU with/without SGW change and/or MME/S4-
ETSI
SGSN change is in progress, the MME/S4-SGSN may receive Create / Update / Delete Bearer request message for the
bearer creation, modification or deletion initiated by the PGW. If the handover/TAU/RAU procedure results in the
SGW and/or MME/S4-SGSN change, then the bearer related procedure cannot be handled temporarily by the MME/S4-
SGSN till the handover/TAU/RAU procedure is completed. In that case the MME/S4-SGSN shall reject the bearer
related procedure with this rejection cause. This cause is also used to indicate that the Downlink Data Notification
message is rejected temporarily due to the mobility procedures with MME or SGSN change in progress as specified in
sub-clause 5.3.4.3 in 3GPP TS 23.401 [3].
The usage of "Fallback to GTPv1" is specified in subclause 7.10 "Fallback to GTPv1 mechanism".
In the PGW initiated bearer deactivation procedure for the default bearer, the PGW may include the Cause IE in the
Delete Bearer Request with values "RAT changed from 3GPP to Non-3GPP", "Reactivation requested" or "Reactivation
disallowed to APN".
"APN Congestion" is used by the PGW and it indicates that the PGW has detected congestion for the requested APN
and performs overload control for that APN which does not allow the PDN connection to be established.
"GTP-C Entity Congestion" is used to indicate that the GTP-C entity has detected node level congestion and performs
overload control at the node level, which does not allow the request to be processed.
"UE already re-attached" is used by MME/S4-SGSN for the network triggered service restoration procedure as
specified in 3GPP TS 23.007 [17]. The MME/S4-SGSN may send the Downlink Data Notification Acknowledge or
Downlink Data Notification Failure Indication with this cause as part of the network triggered service restoration
procedure.
"PDP connection inactivity timer expires" is used by the PGW in Delete Bearer Request(s) to indicate that all the
bearer(s) for the emergency PDN connection are deleted upon the inactivity timer expiry as specified in 3GPP TS
23.203 [48].
"Network failure" is used by the SGSN or MME in the Delete Session Request to indicate that the message is sent due
to a network problem.
"QoS parameter mismatch" is used by the SGSN or MME in the Delete Session Request to indicate that the PDN
connection can not be established due to a QoS parameter mismatch.
"MME/SGSN refuses due to VPLMN policy" is used by the MME/SGSN in the VPLMN to indicate to the PGW in the
Create Bearer Response or Update Bearer Response that it does not allow the establishment or modification of the
bearer due to VPLMN operator's policy.
The listed cause values for rejection response message descriptions in clause 7 are not meant to be exhaustive lists.
Therefore a GTPv2 node shall use the most appropriate matching rejection response cause value that is listed in Table
8.4-1.
If a Bearer Resource Command message is related to an established PDN connection for LIPA or for SIPTO at the local
network, the LGW shall reject the Bearer Resource Command with the cause value of "Bearer handling not supported".
"Multiple PDN connections for a given APN not allowed" is used by SGW for reply message to the MME/S4-SGSN
when PMIP-based S5/S8 is used. If either SGW or PGW does not support the multiple PDN connections to the same
APN function, the SGW shall reject the PDN connectivity request procedure with this rejection cause when receiving
Create Session Request for additional PDN connectivity to the given APN from the same UE.
As specified in sub-clause 5.3.1.1 in 3GPP TS 23.401 [3] and sub-clause 9.2.1 in 3GPP TS 23.060 [35], the cause value
"New PDN type due to network preference" indicates that the UE has requested PDN type IPv4v6 and only IPv4 or
IPv6 address is allowed for the PDN based on PGW operator policy.
As specified in sub-clause 5.3.1.1 in 3GPP TS 23.401 [3] and sub-clause 9.2.1 in 3GPP TS 23.060 [35], the cause value
"New PDN type due to single address bearer only" indicates that the MS has requested PDN type IPv4v6 and both IPv4
and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag of the Indication IE is set to 0 or the
Indication IE is absent, or only single IP version addressing is possible in the PDN.
"PGW not responding" is used by the SGW in PGW Restart Notification to indicate that the peer PGW has failed and
not restarted as specified in subclause 7.9.5.
ETSI
"UE context without TFT already activated" is used by the PGW in the Bearer Resource Failure Indication message to
indicate that the PGW has received the Bearer Resource Command message without TAD IE in the secondary PDP
Context Activation procedure.
"Target access restricted for the subscriber" is used by the MME/SGSN in the Context Response message to indicate
that the target access is prohibited for the subscriber, based on the subscription profile.
"P-TMSI Signature mismatch" is used by the SGSN or MME in the Identification Response and Context Response
message if the P-TMSI Signature stored in the old SGSN or MME does not match the value sent by the UE via the new
SGSN or MME.
"Late Overlapping Request" is used by the PGW in the Create Session Response to indicate that the incoming request
collides with an existing session which has a more recent time stamp than the time stamp of the new request, as
specified in subclause 13.2.
"Timed Out Request" is used by the SGW and PGW in the Create Session Response to indicate that the incoming
request is known to have already timed out at the originating entity, as specified in subclause 13.3.
"UE is temporarily not reachable due to power saving" is used by the MME/SGSN in the Create/Update Bearer
Response message to reject the corresponding network initiated procedures for a Delay Tolerant PDN connection and
also request the PGW to hold the network initiated procedure until it receives the subsequent Modify Bearer Request
message with the UASI flag indicating that the UE is available for end to end signalling.
"UE not authorised by OCS or external AAA Server" is used by the PGW in the Create Session Response to reject the
corresponding UE initiated procedures when the OCS or an external AAA Server on SGi did not authorise it and the
support of the Cause Code was indicated by the SGSN/MME within the Create Session Request.
If a Create Session Request message requests the addition of an access to a PDN connection, and NBIFOM is not
supported by the MME/SGSN, SGW or TWAN, the PGW should reject the request with the cause value of "Multiple
accesses to a PDN connection not allowed".
ETSI
Table 8.4-1: Cause values
Message Type Cause value Meaning

(decimal)
0 Reserved. Shall not be sent and if received the Cause shall be treated as an
invalid IE
Request / Initial 1 Reserved
message 2 Local Detach
3 Complete Detach
4 RAT changed from 3GPP to Non-3GPP
5 ISR deactivation
6 Error Indication received from RNC/eNodeB/S4-SGSN
7 IMSI Detach Only
8 Reactivation Requested
9 PDN reconnection to this APN disallowed
10 Access changed from Non-3GPP to 3GPP
11 PDN connection inactivity timer expires
12 PGW not responding
13 Network Failure
14 QoS parameter mismatch
15 Spare. This value range shall be used by Cause values in an initial/request
message. See NOTE 5.
16 Request accepted
Acceptance in a
17 Request accepted partially
Response /
18 New PDN type due to network preference.
triggered
19 New PDN type due to single address bearer only.
message. See
NOTE 1. 20 to 63 Spare. This value range shall be used by Cause values in an acceptance
response/triggered message
Rejection in a 64 Context Not Found
Response / 65 Invalid Message Format
triggered 66 Version not supported by next peer
message. See 67 Invalid length
NOTE 1. 68 Service not supported
69 Mandatory IE incorrect
70 Mandatory IE missing
71 Shall not be used. See NOTE 2 and NOTE 3.
72 System failure
73 No resources available
74 Semantic error in the TFT operation
75 Syntactic error in the TFT operation
76 Semantic errors in packet filter(s)
77 Syntactic errors in packet filter(s)
78 Missing or unknown APN
80 GRE key not found
81 Relocation failure
82 Denied in RAT
83 Preferred PDN type not supported
84 All dynamic addresses are occupied
85 UE context without TFT already activated. See NOTE 6.
86 Protocol type not supported
87 UE not responding. See NOTE 7.
88 UE refuses
89 Service denied. See NOTE 7.
90 Unable to page UE
91 No memory available
92 User authentication failed
93 APN access denied – no subscription
94 Request rejected (reason not specified)
95 P-TMSI Signature mismatch
96 IMSI/IMEI not known
97 Semantic error in the TAD operation
98 Syntactic error in the TAD operation
100 Remote peer not responding
101 Collision with network initiated request
ETSI
102 Unable to page UE due to Suspension

103 Conditional IE missing
104 APN Restriction type Incompatible with currently active PDN connection
105 Invalid overall length of the triggered response message and a piggybacked initial
message
106 Data forwarding not supported
107 Invalid reply from remote peer
108 Fallback to GTPv1
109 Invalid peer
110 Temporarily rejected due to handover/TAU/RAU procedure in progress
111 Modifications not limited to S1-U bearers
112 Request rejected for a PMIPv6 reason (see 3GPP TS 29.275 [26]).
113 APN Congestion
114 Bearer handling not supported
115 UE already re-attached. See NOTE 7.
116 Multiple PDN connections for a given APN not allowed
117 Target access restricted for the subscriber
119 MME/SGSN refuses due to VPLMN Policy
120 GTP-C Entity Congestion
121 Late Overlapping Request
122 Timed out Request
123 UE is temporarily not reachable due to power saving
124 Relocation failure due to NAS message redirection
125 UE not authorised by OCS or external AAA Server
126 Multiple accesses to a PDN connection not allowed
127 to 239 Spare. For future use in a triggered/response message See NOTE 4.
Request / Initial 240 to 255 Spare. For future use in an initial/request message. See NOTE 5.
message
NOTE 1: The listed cause values for rejection in a response/triggered message can be also used for request
messages if the request message is triggered by a command message.
NOTE 2: Subclause 7.7.8 "Semantically incorrect Information Element" specifies quite strict handling of the reserved
values and therefore this table shall not contain any reserved values.
NOTE 3: This value was used in earlier versions of the spec. If received, it shall be interpreted as unspecified
rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause
value 94 "Request rejected (reason not specified)".
NOTE 4: This value is or may be used in the newer versions of the spec. If the receiver cannot comprehend the
value, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall
be treated in the same ways as the cause value 94 "Request rejected (reason not specified)".
NOTE 5: This value is or may be used in the newer versions of the spec. If the receiver cannot comprehend the
value, it shall be interpreted as an unspecified request/initial message cause. Unspecified/unrecognized
cause handling in a request/initial message shall be implementation dependent (e.g. may be ignored).
NOTE 6: This Cause value is only used over the S4, S5 and S8 interface in the secondary PDP Context Activation
procedure (see 9.2.2.1.1A in 3GPP TS 23.060 [4]).
NOTE 7: This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial
message.
The mapping at the MME/S4-SGSN between GTP cause values received over the S11/S4 interface and the NAS cause
values sent to the UE is specified in Annex C.
8.5 Recovery (Restart Counter)

Recovery IE is coded as depicted in Figure 8.5-1.
The Recovery (Restart Counter) is encoded as 1 octet.
. Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Recovery (Restart Counter)
Figure 8.5-1: Recovery (Restart Counter)
ETSI
8.6 Access Point Name (APN)

Access Point Name (APN) is transferred via GTP tunnels. The sending entity copies the value part of the APN into the
Value field of the APN IE.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Access Point Name (APN)
Figure 8.6-1: Access Point Name (APN)
The encoding the APN field follows 3GPP TS 23.003 [2] subclause 9.1. The content of the APN field shall be the full
APN with both the APN Network Identifier and APN Operator Identifier being present as specified in 3GPP TS 23.003
[2] subclauses 9.1.1 and 9.1.2, 3GPP TS 23.060 [35] Annex A and 3GPP TS 23.401 [3] subclauses 4.3.8.1.
NOTE: The APN field is not encoded as a dotted string as commonly used in documentation.
8.7 Aggregate Maximum Bit Rate (AMBR)

Aggregate Maximum Bit Rate (AMBR) is transferred via GTP tunnels. The sending entity copies the value part of the
AMBR into the Value field of the AMBR (APN-AMBR) IE.
AMBR is defined in clause 9.9.4.2 of 3GPP TS 24.301 [23], but shall be formatted as shown in Figure 8.7-1 as
Unsigned32 binary integer values in kbps (1000 bits per second).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 8
4 Spare Instance
5 to 8 APN-AMBR for uplink
9 to 12 APN-AMBR for downlink
Figure 8.7-1: Aggregate Maximum Bit Rate (AMBR)
The APN-AMBR for uplink and the APN-AMBR for downlink may require converting values in bits per second to kilo
bits per second when the APN-AMBR for uplink and the APN-AMBR for downlink are received from an interface
other than GTPv2 interface. If such conversions result in fractions, then the value of APN-AMBR for uplink and the
APN-AMBR for downlink shall be rounded upwards.
8.8 EPS Bearer ID (EBI)

EPS Bearer ID (EBI) is coded as depicted in Figure 8.8-1.
The overall length of the IE is 5 octets. In future releases of the spec additional octets may be specified and new
semantic for the spare bits may be defined.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare (all bits set to 0) EPS Bearer ID (EBI)
6 to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.8-1: EPS Bearer ID (EBI)
The coding of EBI field and its value range is specified in 3GPP TS 24.007 [30], subclause 11.2.3.1.5, bits 5 to 8.
ETSI
8.9 IP Address
IP Address is coded as depicted in Figure 8.9-1. The Length field may have only two values (4 or 16) that determine if
the Value field contains IPv4 or IPv6 address.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) IPv4 or IPv6 Address
Figure 8.9-1: IP address
8.10 Mobile Equipment Identity (MEI)

Mobile Equipment Identity (MEI) is coded as depicted in Figure 8.10-1. MEI is defined in subclause 6.2 of 3GPP TS
23.003 [2].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Mobile Equipment (ME) Identity
Figure 8.10-1: Mobile Equipment (ME) Identity (MEI)
The ME Identity field contains either the IMEI or the IMEISV as defined in subclause 6.2 of 3GPP TS 23.003 [2]. It is
encoded as specified in subclause 7.7.53 of 3GPP TS 29.060 [4], beginning with octet 4 of Figure 7.7.53.1.
The IMEI(SV) digits are encoded using BCD coding where IMEI is 15 BCD digits and IMEISV is 16 BCD digits. For
IMEI, bits 5 to 8 of the last octet shall be filled with an end mark coded as '1111'.
8.11 MSISDN
MSISDN is transferred via GTP tunnels. The sending entity copies the value part of the MSISDN into the Value field of
the MSISDN IE. MSISDN is defined in 3GPP TS 23.003 [2].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
… … …
n+4 Number digit m Number digit m-1
Figure 8.11-1: MSISDN
Octets 5 to (n+4) represent the MSISDN value is in international number format as described in ITU-T Rec E.164 [25]
and 3GPP TS 29.002 [41]. MSISDN value contains only the actual MSISDN number (does not contain the "nature of
address indicator" octet, which indicates "international number" as in 3GPP TS 29.002 [41]) and is encoded as TBCD
digits, i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of
the last octet are encoded with the filler "1111".
8.12 Indication
Indication is coded as depicted in Figure 8.12-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 DAF DTF HI DFI OI ISRSI ISRAI SGW
CI
6 SQCI UIMSI CFSI CRSI P PT SI MSV
7 RetLo PBIC SRNI S6AF S4AF MBM ISRA CCRS
c DT U I
8 CPRA PPOF PPON PPSI CSFBI CLII CPSR
I ARRL /PPEI
9 NSI UASI DTCI BDWI PSCI PCRI AOSI AOPI
10 Spare Spare Spare Spare Spare PNSI UNAC WPM
CSI SI
Figure 8.12-1: Indication
For each message the applicable flags of the Indication IE shall be clearly specified in the individual message sub
clause. The remaining flags of the Indication IE not so indicated shall be discarded by the receiver.
The receiver shall consider the value of the applicable flags as "0", if the Indication IE is applicable for the message but
not included in the message by the sender.
The following bits within Octet 5 shall indicate:
- Bit 8 – DAF (Dual Address Bearer Flag): This bit shall be set when the PDN Type, determined based on UE
request and subscription record, is set to IPv4v6 and all SGSNs which the UE may be handed over to are
Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the
operator..
- Bit 7 – DTF (Direct Tunnel Flag): This bit shall be set when the UE is in UTRAN and Direct Tunnel is selected
- Bit 6 – HI (Handover Indication): If this bit is set to 1 over S11/S4 and S5/S8 interfaces, it shall indicate a UE
handover from Trusted or Untrusted non-3GPP access to 3GPP access. This bit is applicable during the
Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN or a Handover from Trusted or
Untrusted Non-3GPP IP Access to UTRAN/GERAN procedures (see sub-clauses 8.2, 8.6 and 16.11 of 3GPP TS
23.402 [45]). . If this bit is set to 1 over GTP based S2a interface, it shall indicate a UE handover from 3GPP
access to Trusted Non-3GPP access and UE requested IP address preservation. If this bit is set to 1 over GTP
based S2b interface, it shall indicate a UE handover from 3GPP access to Untrusted Non-3GPP Access and UE
requested IP address preservation.
- Bit 5 – DFI (Direct Forwarding Indication): If this bit is set to 1, it shall indicate that the direct forwarding
between the source eNodeB and the target eNodeB during the S1 based handover procedure is applied.
- Bit 4 – OI (Operation Indication):
- If this bit is set to 1, it shall denote that the receiving SGW of a "Create Session Request" shall send a Modify
Bearer Request immediately to the PGW. This allows the SGW to differentiate if the "Create Session
Request" received on S4/S11 interface belongs to a TAU/RAU with an SGW relocation (OI = 1), or X2-
based handover with SGW relocation (OI = 1) or Enhanced SRNS Relocation with SGW relocation (OI=1)
or MME triggered Serving GW relocation (OI = 1) or S1-based handover with SGW relocation (OI = 0).
- It shall be set to 1 on S4/S11 interface if the SGW needs to forward the Delete Session Request message to
PGW.
- Bit 3 – ISRSI (Idle mode Signalling Reduction Supported Indication): If this is set to 1, it shall indicate that the
old/source SGSN/MME and the associated SGW are capable to activate ISR.
- Bit 2 – ISRAI (Idle mode Signalling Reduction Activation Indication): If this bit is set to 1, it shall indicate that
the ISR is established between the MME and the S4 SGSN during a TAU/RAU without an SGW change
procedure or during an Inter RAT handover without an SGW change procedure. The SGW shall retain the
ETSI
resources for the other CN node that has its bearer resources on the SGW reserved. The old/source SGSN/MME
shall maintain the UE's contexts and activate ISR.
- Bit 1 – SGWCI (SGW Change Indication): If this bit is set to 1, it shall indicate that the target MME/SGSN has
selected a new SGW during a TAU/RAU or handover with an SGW change procedure.
- Bit 8 – SQCI (Subscribed QoS Change Indication): If this bit is set to 1, it indicates that the subscribed QoS
profile of the related PDN connection has changed in the old MME/SGSN when the UE is in ECM-IDLE state
and ISR is activated. The new MME/SGSN shall trigger the Subscribed QoS Modification procedure. See 3GPP
TS 23.401 [3], clause 5.3.9.2.
- Bit 7 – UIMSI (Unauthenticated IMSI): If this bit is set to 1, it indicates that the IMSI present in the message is
not authenticated and is for emergency attached UE.
- Bit 6 – CFSI (Change F-TEID support indication): if this bit is set to 1, it indicates that the SGW can change the
assigned GTP-U F-TEID in the current procedure. If the SGW needs to modify the GTP-U F-TEID and the CFSI
flag is set to 1 in the corresponding request message, the SGW shall include the new F-TEID in the Modify
Bearer Response/Modify Access Bearers Response message.
- Bit 5 – CRSI (Change Reporting support indication): if this bit is set to 1, it indicates that the MME/S4 SGSN
supports Location Change Reporting mechanism for the corresponding session.
- Bit 4 – PS (Piggybacking Supported). This bit denotes whether the MME/SGW support piggybacking feature as
described in Annex F of 3GPP TS 23.401 [3]. If set to 1, it indicates that the node is capable of processing two
different GTP-C messages appearing back to back in a single UDP payload.
- Bit 3 – PT (Protocol Type) If this bit set to 1, it shall indicate that the protocol type for the S5/S8 interface is
PMIP; this bit is set to 0 to indicate that the protocol type for the S5/S8 interface is GTP.
- Bit 2 – SI (Scope Indication): If this bit is set to 1, it indicates that all bearer resources of the UE shall be
released by the SGW. This flag is set in messages during TAU/RAU/Handover with SGW change /SRNS
Relocation Cancel Using S4 with SGW change/Inter RAT handover Cancel procedure with SGW change/S1
Based handover Cancel procedure with SGW change.
- Bit 1 – MSV (MS Validated): If this bit is set to 1, it shall indicate that the new MME/SGSN has successfully
authenticated the UE.
The following bits within Octet 7shall indicate:
- Bit 8 – RetLoc (Retrieve Location Indication Flag): if this bit is set to 1, it indicates that the PGW requests the
MME/SGSN or TWAN/ePDG to provide the User Location Information.
Bit 7 – PBIC (Propagate BBAI Information Change): if this bit is set to 1, it indicates a change in the H(e)NB
local IP address and/or UDP port number, i.e. the UE moves from an (e)NB to a H(e)NB, or from one H(e)NB to
another H(e)NB with the fixed network backhaul changed, or the UE moves from a H(e)NB to a (e)NB.
- Bit 6 – SRNI (SGW Restoration Needed Indication): if this bit is set to 1, it indicates that the source MME/S4-
SGSN has not performed the SGW relocation procedure after the source SGW has failed with or without restart,
when the source and target MME/S4-SGSN support the MME/S4-SGSN triggered SGW restoration procedure as
- Bit 5 – S6AF (Static IPv6 Address Flag): if this bit is set to 1, it indicates that PDP/PDN IPv6 address is static.
- Bit 4 – S4AF (Static IPv4 Address Flag): if this bit is set to 1, it indicates that PDP/PDN IPv4 address is static.
- Bit 3 – MBMDT (Management Based MDT allowed flag): if this bit is set to 1, it indicates that management
based MDT is allowed.
- Bit 2 – ISRAU (ISR is activated for the UE): if this bit is set to 1, it indicates that ISR is activated for the UE
before the UE moving to the new SGSN/MME.
- Bit 1 – CCRSI (CSG Change Reporting support indication): if this bit is set to 1, it indicates that the MME/S4
SGSN supports CSG Information Change Reporting mechanism for the corresponding session.
ETSI
- Bit 8 – CPRAI (Change of Presence Reporting Area information Indication): when ISR is active if this bit is set
to 1, it indicates that the Presence Reporting Area information, which is provided as a part of the Presence
Reporting Area Information IE, has changed since last reported by the MME/S4-SGSN. The SGW shall ignore
this flag when ISR is not active.
- Bit 7 – ARRL (Abnormal Release of Radio Link): if this bit is set to 1 by the MME, it indicates to the SGW that
the access bearers are released due to an abnormal release of the radio link. Based on operator policy, this
indication may be used by the SGW in subsequent decisions to trigger PDN charging pause if the PGW Pause of
Charging feature has been enabled on that PDN connection.
- Bit 6 – PPOFF (PDN Pause Off Indication): if this bit is set to 1 by the SGW, it indicates to the PGW that the
charging for the PDN connection shall be unpaused.
- Bit 5 – PPON (PDN Pause On Indication) / PPEI (PDN Pause Enabled Indication): if this bit is set to 1 by the
SGW, it indicates to the PGW that the charging for the PDN connection shall be paused; if it is set to 1 by the
PGW, it indicates that PGW enables the SGW to use the PGW Pause of Charging procedure for the PDN
connection.
- Bit 4 – PPSI (PDN Pause Support Indication): if this bit is set to 1 by the SGW, it indicates that the SGW
supports the PGW Pause of Charging procedure; if it is set to 1 by the PGW, it indicates that the PGW supports
the PGW Pause of Charging procedure.
- Bit 3 – CSFBI (CSFB Indication): if this bit is set to 1, it indicates that the UE has been subject to CSFB.
- Bit 2 – CLII (Change of Location Information Indication): when ISR is active if this bit is set to 1, it indicates
that the location information, which is provided as a part of ULI IE, has changed since last reported by the
MME/S4-SGSN. The SGW shall ignore this flag when ISR is not active.
- Bit 1 – CPSR (CS to PS SRVCC indication): if this bit is set to 1, it indicates that a UTRAN/GERAN to E-
UTRAN/UTRAN (HSPA) SRVCC procedure is underway and the associated message, i.e. Modify Bearer
Request shall be forwarded to the PGW from the SGW as specified in 3GPP TS 23.216 [43].
- Bit 8 – NSI (NBIFOM Support Indication): if this bit is set to 1, it indicates to the PGW that the NBIFOM is
supported (see subclause 5.10 of 3GPP TS 23.161 [71]).
- Bit 7 – UASI (UE Available for Signaling Indication): if this bit is set to 1, it indicates that the UE is available
for end to end signalling and that the PGW should re-attempt the pending network initiated procedure.
- Bit 6 – DTCI (Delay Tolerant Connection Indication): if this bit is set to 1, it indicates that the PDN connection
is delay tolerant according to the local policies in the PGW, e.g. per APN.For this PDN connection the PGW
supports receiving the rejection cause "UE is temporarily not reachable due to power saving" from the
MME/SGSN via the SGW during a network initiated procedure and holding the network initiated procedure,
until the PGW receives the subsequent Modify Bearer Request message with the UASI flag indicating that the
UE is available for end to end signalling.
Bit 5 – BDWI (Buffered DL Data Waiting Indication): if this bit is set to 1, it indicates that there is DL data buffered
in the (old) SGW, i.e. that the new MME/SGSN shall invoke data forwarding if there is an SGW change as
specified in subclause 5.3.3.1A of 3GPP TS 23.401 [3], and that it shall setup the user plane in conjunction with
the TAU/RAU procedure for delivery of the buffered DL data to the UE.
- Bit 4 – PSCI (Pending Subscription Change Indication): If this bit is set to 1, it indicates that there is a pending
report of the changed subscribed QoS profile of the related PDN connection in the old MME, so that the new
MME/SGSN shall trigger the HSS Initiated Subscribed QoS Modification procedure towards the PGW. See
- Bit 3 – PCRI (P-CSCF Restoration Indication): if this bit is set to 1, it indicates a request to trigger a P-CSCF
restoration for the corresponding user (see 3GPP TS 23.380 [61]).
- Bit 2 – AOSI (Associate OCI with SGW node's Identity): if this bit is set to 1, it indicates that the SGW provided
"SGW's Overload Control Information" which shall be associated with the node identity (i.e. FQDN or the IP
address received from the HSS or DNS during the SGW selection) of the serving SGW.
ETSI
- Bit 1 – AOPI (Associate OCI with PGW node's Identity): if this bit is set to 1, it indicates that the PGW provided
"PGW's Overload Control Information" which shall be associated with the node identity (i.e. FQDN or the IP
address received from the HSS or DNS during the PGW selection) of the serving PGW.
- Bit 4 to 8 – Spare, for future use and set to zero.
- Bit 3 – PNSI (Pending Network Initiated PDN Connection Signalling Indication): if this bit is set to 1, it
indicates to the target MME/SGSN that there is pending network initiated PDN connection signalling for the
PDN connection, i.e. the target MME/SGSN shall set UASI flag in the Create Session Request or Modify Bearer
Request message to indicate to the PGW that the UE is available for end to end signalling.
- Bit 2 – UNACCSI (UE Not Authorised Cause Code Support Indication): If this bit is set to 1, it indicates that the
Cause Code for "UE not authorized by OCS or external AAA Server" is supported by the S4-SGSN/MME.
- Bit 1 - WLCP PDN Connection Modification Support Indication (WPMSI): if this bit is set to 1, it indicates that
the TWAN supports the WLCP PDN Connection Modification procedure. This indication is used by the P-CSCF
restoration extension procedure for TWAN access (see 3GPP TS 23.380 [61]).
8.13 Protocol Configuration Options (PCO)

Protocol Configuration Options (PCO) is transferred via GTP tunnels. The sending entity copies the value part of the
PCO into the Value field of the PCO IE. The detailed coding and maximum length of the PCO field from octets 5 to
(n+4) shall be specified as per clause 10.5.6.3 of 3GPP TS 24.008 [5], starting with octet 3.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Protocol Configuration Options (PCO)
Figure 8.13-1: Protocol Configuration Options (PCO)
8.14 PDN Address Allocation (PAA)

The PDN Address Allocation is coded as depicted in Figure 8.14-1.
NOTE: The Prefix Length within PAA IE has a fixed value of /64.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare PDN Type
6 to (n+4) PDN Address and Prefix
Figure 8.14-1: PDN Address Allocation (PAA)
ETSI
Table 8.14-1: PDN Address Allocation
PDN type value (octet 5)

Bits
3 2 1
0 0 1 IPv4
0 1 0 IPv6
0 1 1 IPv4v6
All other values are reserved.
Bits 8-4 of octet 5 are spare and shall be coded as zero.
PDN Address and Prefix (octet 6 to n+4)
If PDN type value indicates IPv4, an IPv4 address is present in the PDN Address and
Prefix from octet 6 to octet 9. Bit 8 of octet 6 represents the most significant bit of the
IPv4 address and bit 1 of octet 9 the least significant bit.
If PDN type value indicates IPv6, octet 6 contains the IPv6 Prefix Length. Octets 7
through 22 contain an IPv6 Prefix and Interface Identifier. Bit 8 of octet 7 represents
the most significant bit of the IPv6 Prefix and Interface Identifier and bit 1 of octet 22
the least significant bit.
If PDN type value indicates IPv4v6, octet 6 contains the IPv6 Prefix Length. Octets 7
through 22 contain an IPv6 Prefix and Interface Identifier. Bit 8 of octet 7 represents
the most significant bit of the IPv6 Prefix and Interface Identifier and bit 1 of octet 22
the least significant bit. Octets 23 through 26 contain an IPv4 address. Bit 8 of octet 23
represents the most significant bit of the IPv4 address and bit 1 of octet 26 the least
significant bit.
8.15 Bearer Quality of Service (Bearer QoS)

Bearer Quality of Service (Bearer QoS) is transferred via GTP tunnels. The sending entity copies the value part of the
Bearer l QoS into the Value field of the Bearer QoS IE.
Bits
Octets 8 7 6 5 4 3 2 1
2-3 Length = n
4 Spare Instance
5 Spare PCI PL Spare PVI
6 Label (QCI)
7 to 11 Maximum bit rate for uplink
12 to 16 Maximum bit rate for downlink
17 to 21 Guaranteed bit rate for uplink
22 to 26 Guaranteed bit rate for downlink
Figure 8.15-1: Bearer Quality of Service (Bearer QoS)
Octet 5 represents the Allocation/Retention Priority (ARP) parameter. The meaning and value range of the parameters
within the ARP are defined in 3GPP TS 29.212 [29]. The bits within the ARP octet are:
- Bit 1 – PVI (Pre-emption Vulnerability): See 3GPP TS 29.212[29], clause 5.3.47 Pre-emption-Vulnerability
AVP.
- Bit 2 – spare
- Bits 3 to 6 – PL (Priority Level): See 3GPP TS 29.212[29], clause 5.3.45 Priority-Level AVP. PL encodes each
priority level defined for the Priority-Level AVP as the binary value of the priority level.
- Bit 7 – PCI (Pre-emption Capability): See 3GPP TS 29.212[29], clause 5.3.46 Pre-emption-Capability AVP.
ETSI
- Bit 8 – spare.
Octet 6 contains the "QCI" value, as specified in 3GPP TS 23.203 [48].
The UL/DL MBR and GBR fields are encoded as kilobits per second (1 kbps = 1000 bps) in binary value. The UL/DL
MBR and GBR fields may require converting values in bits per second to kilobits per second when the UL/DL MBR
and GBR values are received from an interface other than GTPv2 interface. If such conversions result in fractions, then
the value of UL/DL MBR and GBR fields shall be rounded upwards. For non-GBR bearers, both the UL/DL MBR and
GBR should be set to zero. The range of QCI, Maximum bit rate for uplink, Maximum bit rate for downlink,
Guaranteed bit rate for uplink and Guaranteed bit rate for downlink are specified in 3GPP TS 36.413 [10].
NOTE: The encoding in 3GPP TS 24.301 [23] and 3GPP TS 36.413 [10] is different from the encoding within
this specification.
8.16 Flow Quality of Service (Flow QoS)

Flow Quality of Service (Flow QoS) is transferred via GTP tunnels. The sending entity copies the value part of the Flow
QoS into the Value field of the Flow QoS IE.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Label (QCI)
6 to 10 Maximum bit rate for uplink
11 to 15 Maximum bit rate for downlink
16 to 20 Guaranteed bit rate for uplink
21 to 25 Guaranteed bit rate for downlink
Figure 8.16-1: Flow Quality of Service (Flow QoS)
Octet 5 contains the "QCI" value, as specified in 3GPP TS 23.203 [48].
The UL/DL MBR and GBR fields are encoded as kilobits per second (1 kbps = 1000 bps) in binary value. For non-GBR
bearers, both the UL/DL MBR and GBR should be set to zero. The range of QCI, Maximum bit rate for uplink,
Maximum bit rate for downlink, Guaranteed bit rate for uplink and Guaranteed bit rate for downlink are specified in
3GPP TS 36.413 [10].
NOTE: The encoding in 3GPP TS 24.301 [23] and 3GPP TS 36.413 [10] is different from the encoding within
this specification.
8.17 RAT Type

RAT Type is coded as depicted in Figure 8.17-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 RAT Type
Figure 8.17-1: RAT Type
ETSI
Table 8.17-1: RAT Type values
RAT Types Values (Decimal)

<reserved> 0
UTRAN 1
GERAN 2
WLAN 3
GAN 4
HSPA Evolution 5
EUTRAN 6
Virtual 7
<spare> 8-255
NOTE 1: For S4-SGSN, currently it is only possible to detect the difference between GERAN and UTRAN when
GERAN Gb mode is used. If GERAN Iu mode is used, then an S4-SGSN may not be able to detect the
difference between GERAN and UTRAN. Across the Gb interface, the SGSN may also not be able to
detect the difference between GERAN and GAN. If S4-SGSN cannot detect that the HSPA Evolution
3GPP TR 25.999 [46] network is behind the Iu interface, the S4-SGSN will send the "UTRAN" RAT
Type.
NOTE 2: For the Iu interface case, if the SGSN detects UTRAN or HSPA, it sets the RAT-Type to "UTRAN". If
the SGSN detects HSPA+, it sets the RAT-Type to "HSPA Evolution", otherwise the SGSN will send the
"UTRAN" RAT Type.
8.18 Serving Network

Serving Network is coded as depicted in Figure 8.18-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 MCC digit 2 MCC digit 1
6 MNC digit 3 MCC digit 3
7 MNC digit 2 MNC digit 1
Figure 8.18-1: Serving Network
If an Administration decides to include only two digits in the MNC, then bits 5 to 8 of octet 6 are coded as "1111".
Unless specified otherwise in the specification, this IE contains the serving core network operator ID provided by the
MME, S4-SGSN or ePDG, or the PLMN identity of the selected PLMN used for 3GPP-based access authentication
provided by the TWAN.
NOTE: The serving core network operator ID is the PLMN ID of the MME, S4-SGSN or ePDG which is
currently serving the UE. An S4-SGSN/MME which supports multiple PLMN IDs is considered as
logically different S4-SGSNs/MMEs.
8.19 EPS Bearer Level Traffic Flow Template (Bearer TFT)

EPS Bearer Level Traffic Flow Template (Bearer TFT) is transferred via GTP tunnels. The sending entity copies the
value part of the EPS Bearer Level TFT into the Value field of the EPS Bearer Level TFT IE. The detailed coding and
maximum length of the EPS Bearer Level TFT IE is specified in 3GPP TS 24.008 [5], clause 10.5.6.12, beginning with
octet 3.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) EPS Bearer Level Traffic Flow Template (TFT)
Figure 8.19-1: EPS Bearer Level Traffic Flow Template (Bearer TFT)
8.20 Traffic Aggregate Description (TAD)

The Traffic Aggregate Description IE is coded as depicted in Figure 8.20-1. The detailed coding and maximum length
of Traffic Aggregate Description is specified in 3GPP TS 24.008 [5], clause 10.5.6.12, beginning with octet 3..
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 85 (Decimal)
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Traffic Aggregate Description
Figure 8.20-1 Traffic Aggregate Description
8.21 User Location Information (ULI)

User Location Information (ULI) is a extendable IE that is coded as depicted in Figure 8.21-1. The CGI, SAI, RAI,
TAI, ECGI and LAI identity types are defined in 3GPP TS 23.003 [2].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare LAI ECGI TAI RAI SAI CGI
a to a+6 CGI
b to b+6 SAI
c to c+6 RAI
d to d+4 TAI
e to e+6 ECGI
f to f+4 LAI
g to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.21-1: User Location Information
The ULI IE shall contain only one identity of the same type (e.g. more than one CGI cannot be included), but ULI IE
may contain more than one identity of a different type (e.g. ECGI and TAI). The flags LAI, ECGI, TAI, RAI, SAI and
CGI in octet 5 indicate if the corresponding type shall be present in a respective field or not. If one of these flags is set
to "0", the corresponding field shall not be present at all. If more than one identity of different type is present, then they
shall be sorted in the following order: CGI, SAI, RAI, TAI, ECGI, LAI.
The following subclauses specify the coding of the fields representing different identities.
For each identity, if an Administration decides to include only two digits in the MNC, then "MNC digit 3" field of
corresponding location shall be coded as "1111".
8.21.1 CGI field

The coding of CGI (Cell Global Identifier) is depicted in Figure 8.21.1-1. Only zero or one CGI field shall be present in
ULI IE.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
a MCC digit 2 MCC digit 1
a+1 MNC digit 3 MCC digit 3
a+2 MNC digit 2 MNC digit 1
a+3 to a+4 Location Area Code (LAC)
a+5 to a+6 Cell Identity (CI)
Figure 8.21.1-1: CGI field
The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet a+3 is the most significant bit and bit 1 of Octet a+4
the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using
full hexadecimal representation shall be used.
The Cell Identity (CI) consists of 2 octets. Bit 8 of Octet a+5 is the most significant bit and bit 1 of Octet a+6 the least
significant bit. The coding of the cell identity is the responsibility of each administration. Coding using full hexadecimal
representation shall be used.
8.21.2 SAI field

The coding of SAI (Service Area Identifier) is depicted in Figure 8.21.2-1. Only zero or one SAI field shall be present
in ULI IE.
Bits
Octets 8 7 6 5 4 3 2 1
b MCC digit 2 MCC digit 1
b+1 MNC digit 3 MCC digit 3
b+2 MNC digit 2 MNC digit 1
b+3 to b+4 Location Area Code (LAC)
b+5 to b+6 Service Area Code (SAC)
Figure 8.21.2-1: SAI field
The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet b+3 is the most significant bit and bit 1 of Octet b+4
The Service Area Code (SAC) consists of 2 octets. Bit 8 of Octet b+5 is the most significant bit and bit 1 of Octet b+6
the least significant bit. The SAC is defined by the operator. See 3GPP TS 23.003 [2] section 12.5 for more information.
8.21.3 RAI field

The coding of RAI (Routing Area Identity) is depicted in Figure 8.21.3-1. Only zero or one RAI field shall be present in
ULI IE.
Bits
Octets 8 7 6 5 4 3 2 1
c MCC digit 2 MCC digit 1
c+1 MNC digit 3 MCC digit 3
c+2 MNC digit 2 MNC digit 1
c+3 to c+4 Location Area Code (LAC)
c+5 to c+6 Routing Area Code (RAC)
Figure 8.21.3-1: RAI field
The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet c+3 is the most significant bit and bit 1 of Octet c+4
full hexadecimal representation shall be used (see 3GPP TS 23.003 [2]).
The Routing Area Code (RAC) consists of 2 octets. Only Octet c+5 contains the RAC. Octet c+6 is coded as all 1's
(11111111). The RAC is defined by the operator. Coding using full hexadecimal representation shall be used (see 3GPP
TS 23.003 [2]).
ETSI
8.21.4 TAI field

The coding of TAI (Tracking Area Identity) is depicted in Figure 8.21.4-1. Only zero or one TAI field shall be present
in ULI IE.
Bits
Octets 8 7 6 5 4 3 2 1
d MCC digit 2 MCC digit 1
d+1 MNC digit 3 MCC digit 3
d+2 MNC digit 2 MNC digit 1
d+3 to d+4 Tracking Area Code (TAC)
Figure 8.21.4-1: TAI
The Tracking Area Code (TAC) consists of 2 octets. Bit 8 of Octet d+3 is the most significant bit and bit 1 of Octet d+4
the least significant bit. The coding of the tracking area code is the responsibility of each administration. Coding using
8.21.5 ECGI field

The coding of ECGI (E-UTRAN Cell Global Identifier) is depicted in Figure 8.21.5-1. Only zero or one ECGI field
shall be present in ULI IE.
Bits
Octets 8 7 6 5 4 3 2 1
e MCC digit 2 MCC digit 1
e+1 MNC digit 3 MCC digit 3
e+2 MNC digit 2 MNC digit 1
e+3 Spare ECI
e+4 to e+6 ECI (E-UTRAN Cell Identifier)
Figure 8.21.5-1: ECGI field
The E-UTRAN Cell Identifier (ECI) consists of 28 bits. The ECI field shall start with Bit 4 of octet e+3, which is the
most significant bit. Bit 1 of Octet e+6 is the least significant bit. The coding of the E-UTRAN cell identifier is the
responsibility of each administration. Coding using full hexadecimal representation shall be used.
8.21.6 LAI field

The coding of LAI (Location Area Identifier) is depicted in Figure 8.21.6-1.
Bits
Octets 8 7 6 5 4 3 2 1
f MCC digit 2 MCC digit 1
f+1 MNC digit 3 MCC digit 3
f+2 MNC digit 2 MNC digit 1
f+3 to f+4 Location Area Code (LAC)
Figure 8.21.6-1: LAI field
The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet f+3 is the most significant bit and bit 1 of Octet f+4
8.22 Fully Qualified TEID (F-TEID)

Fully Qualified Tunnel Endpoint Identifier (F-TEID) is coded as depicted in Figure 8.22-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2to 3 Length = n
4 Spare Instance
5 V4 V6 Interface Type
6 to 9 TEID / GRE Key
m to (m+3) IPv4 address
p to (p+15) IPv6 address
k to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.22-1: Fully Qualified Tunnel Endpoint Identifier (F-TEID)
The following flags are coded within Octet 5:
- Bit 8 – V4: If this bit is set to "1", then IPv4 address field exists in the F-TEID, otherwise the IPv4 address field
is not present at all.
- Bit 7 – V6: If this bit is set to "1", then IPv6 address field exists in the F-TEID, otherwise the IPv6 address field
is not present at all.
At least one of V4 and V6 shall be set to "1", and both may be set to "1".
- Bit 6 to Bit 1 – Interface Type: This 6 bit wide integer can take the following values representing interface type
and endpoint:
0: S1-U eNodeB GTP-U interface
1: S1-U SGW GTP-U interface
2: S12 RNC GTP-U interface
3: S12 SGW GTP-U interface
4: S5/S8 SGW GTP-U interface
5: S5/S8 PGW GTP-U interface
6: S5/S8 SGW GTP-C interface
7: S5/S8 PGW GTP-C interface
8: S5/S8 SGW PMIPv6 interface (the 32 bit GRE key is encoded in 32 bit TEID field)
9: S5/S8 PGW PMIPv6 interface (the 32 bit GRE key is encoded in the 32 bit TEID field, see subclause 6.3 in
3GPP TS 29.275 [26])
10: S11 MME GTP-C interface
11: S11/S4 SGW GTP-C interface
14: S3 SGSN GTP-C interface
15: S4 SGSN GTP-U interface
16: S4 SGW GTP-U interface
ETSI
19: eNodeB GTP-U interface for DL data forwarding
20: eNodeB GTP-U interface for UL data forwarding
21: RNC GTP-U interface for data forwarding
22: SGSN GTP-U interface for data forwarding
23: SGW GTP-U interface for DL data forwarding
24: Sm MBMS GW GTP-C interface
25: Sn MBMS GW GTP-C interface
26: Sm MME GTP-C interface
27: Sn SGSN GTP-C interface
28: SGW GTP-U interface for UL data forwarding
29: Sn SGSN GTP-U interface
30: S2b ePDG GTP-C interface
31: S2b-U ePDG GTP-U interface
32: S2b PGW GTP-C interface
33: S2b-U PGW GTP-U interface
34: S2a TWAN GTP-U interface
35: S2a TWAN GTP-C interface
36: S2a PGW GTP-C interface
37: S2a PGW GTP-U interface
Other values of "Interface Type" are spare and reserved for future use.
"Interface type" values with bit "6" set to 1 shall only be used between Rel-10 onwards GTPv2-C nodes.
NOTE 1: "Interface type" IE is defined with 5 bits only in the earlier releases of this specification, thus pre-Rel-10
GTPv2-C nodes can ignore bit "6" which is marked as "Spare" in earlier releases, allowing backward
compatibility.
NOTE 2: Interface Type 8 is not used in this Release and in earlier Releases.
Octet 6 to 9 (TEID/GRE field) represent either a TEID or a GRE key. If both IPv4 and IPv6 addresses are present in F-
TEID IE, then the TEID value shall be shared by both addresses.
Octets "m to (m+3)" and/or "p to (p+15)" (IPv4 address / IPv6 address fields), if present, contain respective address
values.
8.23 TMSI
The TMSI, unambiguously associated with a given UE and Location area, is given by:
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) TMSI
The TMSI is defined in 3GPP TS 23.003 [2].
Figure 8.23-1: TMSI
ETSI
8.24 Global CN-Id

The Global CN-Id is coded as depicted in Figure 8.24-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
8 to (n+4) CN-Id
The CN-Id is defined in 3GPP TS 23.003 [2].
Figure 8.24-1: Global CN-Id
8.25 S103 PDN Data Forwarding Info (S103PDF)

The HSGW Address and GRE Key identify a GRE Tunnel towards a HSGW over S103 interface for a specific PDN
connection of the UE. The EPS Bearer IDs specify the EPS Bearers which require data forwarding that belonging to this
PDN connection. The number of EPS bearer Ids included is specified by the value of EPS Bearer ID Number.
The spare bits indicate unused bits, which shall be set to 0 by the sending side and which shall not be evaluated by the
receiving side.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 HSGW Address for forwarding Length = m
6 to (m+5) HSGW Address for forwarding [4..16]
(m+6)- to GRE Key
(m+9)
(m+10) EPS Bearer ID Number = k
(m+11) to Spare EPS Bearer ID
(m+10+k)
Figure 8.25-1: S103 PDN Data Forwarding Info
8.26 S1-U Data Forwarding (S1UDF)

The Serving GW Address and Serving GW S1-U TEID consists of the S1-U Tunnel information allocated by the
Serving GW for an EPS Bearer identified by the EPS Bearer ID which requires data forwarding during active handover
from E-UTRAN Access to cdma2000 HRPD Access.
receiving side.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare EPS Bearer ID
6 Serving GW Address Length = m
7 to (m+6) Serving GW Address [4..16]
(m+7) to Serving GW S1-U TEID
(m+10)
Figure 8.26-1: S1-U Data Forwarding Info
8.27 Delay Value

Delay Value is coded as depicted in Figure 8.27-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Delay Value in integer multiples of 50 millisecs, or zero
Figure 8.27-1: Delay Value
Delay Value is set to zero in order to clear a previously set delay condition.
8.28 Bearer Context

Bearer Context is a grouped IE containing a number of other IEs. Which of those IEs are mandatory, optional or
conditional and the conditions that apply are GTP message specific, and described in the corresponding subclause under
clause 7.
Bearer Context may be repeated within a message with exactly the same Type and Instance values to represent a list of
Bearer Contexts.
Bearer Context is coded as depicted in Table 8.28-1.
Table 8.28-1: Bearer Context Grouped Type

Information elements P Condition / Comment IE Type Ins.
NOTE: This table uses a 5-column format in order to match the format used in subclauses of clause 7, where
the usage of this IE is further detailed for each specific GTP message including it.
8.29 Charging ID
The Charging ID is coded as depicted in Figure 8.29-1. It is defined in 3GPP TS 32.251[8].
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5-8 Charging ID value
9-(n+4) These octet(s) is/are present only if explicitly specified
Figure 8.29-1: Charging ID
8.30 Charging Characteristics

The charging characteristics information element is defined in 3GPP TS 32.251 [8] and is a way of informing both the
SGW and PGW of the rules for producing charging information or informing the PGW to inhibit the establishment of
the Gx session based on operator configured triggers. For the encoding of this information element see
3GPP TS 32.298 [9].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 6 Charging Characteristics value
Figure 8.30-1: Charging Characteristics
8.31 Trace Information

Trace Information is coded as depicted in Figure 8.31-1. See 3GPP TS 32.422 [18] for details on trace related
information.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 96(decimal)
2 to 3 Length = n
4 Spare Instance
8 to10 Trace ID
11 to 19 Triggering Events
20 to 21 List of NE Types
22 Session Trace Depth
23 to 34 List of Interfaces
35 to (n+4) IP Address of Trace Collection Entity
Figure 8.31-1: Trace Information
Octets 5 to 10 represent the Trace Reference parameter as defined in 3GPP TS 32.422 [18], clause 5.6.
Triggering Events, List of NE Types, Session Trace Depth are specified in 3GPP TS 32.422 [18].
List of Interfaces shall be encoded as the first 12 octets in the subclause 5.5 of 3GPP TS 32.422 [18].
See 3GPP TS 24.008 [5], clause 10.5.1.4, Mobile Identity, for the coding of MCC and MNC, whose values are obtained
from the serving PLMN that the EM/NM is managing. If MNC is 2 digits long, bits 5 to 8 of octet 6 are coded as
"1111".
8.32 Bearer Flags

Bearer Flags is coded as depicted in Figure 8.32-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare ASI Vind VB PPC
Figure 8.32-1: Bearer Flags
- Bit 1 – PPC (Prohibit Payload Compression): This flag is used to determine whether an SGSN should attempt to
compress the payload of user data when the users asks for it to be compressed (PPC = 0), or not (PPC = 1).
- Bit 2 – VB (Voice Bearer): This flag is used to indicate a voice bearer when doing PS-to-CS (v)SRVCC
handover.
- Bit 3 – Vind (vSRVCC indicator): This flag is used to indicate that this bearer is an IMS video bearer and is
candidate for PS-to-CS vSRVCC handover.
- Bit 4 - ASI (Activity Status Indicator): When set to 1, this flag indicates that the bearer context is preserved in
the CN without corresponding Radio Access Bearer established. The target S4-SGSN shall keep the bearer
context associated with this indicator preserved. When the target S4-SGSN sends Relocation Request message
towards the target RNC, the target S4-SGSN may not request to setup the RABs for those bearer contexts
associated with this indicator.
8.33 Void
8.34 PDN Type

The PDN Type is coded as depicted in Figure 8.34-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare PDN Type
6 to n+4) These octet(s) is/are present only if explicitly specified
Figure 8.34-1: PDN Type
Table 8.34-1: PDN Type
PDN type value (octet 5)

Bits
3 2 1
0 0 1 IPv4
0 1 0 IPv6
0 1 1 IPv4v6
All other values are reserved.
Bits 8-4 of octet 5 are spare and shall be coded as zero.
8.35 Procedure Transaction ID (PTI)

Procedure Transaction Id is coded as depicted in Figure 8.35-1. It is defined in 3GPP TS 24.301 [23], clause 9.4 and is
coded as specified in 3GPP TS 24.007 [30], clause 11.2.3.1a Procedure transaction identity.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Procedure Transaction ID
Figure 8.35-1: Procedure Transaction ID
8.36 Void
8.37 Void
8.38 MM Context
The MM Context information element contains the Mobility Management, UE security parameters that are necessary to
transfer over S3/S16/S10 interface.
All Spare bits are set to zeros by the sender and ignored by the receiver. Spare bits in MM Context IE shall be set to 1's
before sending MM Context IE to Gn/Gp SGSN.
NOTE: The encoding of Spare bits in MM Context IE is different between GTPv1 and GTPv2. Spare bits in
GTPv1 in MM Context IE there are set to 1s.
Security Mode indicates the type of security keys (GSM/UMTS/EPS) and Authentication Vectors (quadruplets
/quintuplets/triplets) that are passed to the new MME/SGSN.
The DRX parameter coding is specified in clause 10.5.5.6 of 3GPP TS 24.008 [5]. If DRXI (DRX Indicator), bit 4 of
octet 5, is set to "1", then the DRX parameter field is present, otherwise its octets are not present.
Uplink/downlink Subscribed UE AMBR (Aggregate Maximum Bit Rate) is coded as Unsigned32 integer values in kbps
(1000 bps) for all non-GBR bearers according to the subscription of the user. The uplink/downlink Subscribed UE
AMBR requires converting values in bits per second to kilobits per second when it is received from the HSS. If such
conversions result in fractions, then the uplink/downlink Subscribed UE AMBR values shall be rounded upwards. If
SAMBRI (Subscribed UE AMBR Indicator), bit 1 of octet 6, is set to "1", then the Uplink/downlink Subscribed UE
AMBR parameter field is present, otherwise these parameters are not present. If no Subscribed UE AMBR is received
from the HSS, the SAMBRI shall be set to "0".Uplink/downlink Used UE AMBR (Aggregate Maximum Bit Rate) is
coded as Unsigned32 integer values in kbps (1000 bps) for all non-GBR bearers currently being used by the UE. If
UAMBRI (Used UE AMBR Indicator), bit 2 of octet 6, is set to "1", then the Uplink/downlink Used UE AMBR
parameter field is present, otherwise these parameters are not present.
The encoding of Mobile Equipment Identity (MEI) field shall be same as specified in clause 8.10 of this specification. If
Length of Mobile Equipment Identity is zero, then the Mobile Equipment Identity parameter shall not be present. If the
UE is emergency attached and the UE is UICCless or the IMSI is unauthenticated, Mobile Equipment Identity (MEI)
shall be used as the UE identity.
The UE Network Capability coding is specified in clause 9.9.3.34 of 3GPP TS 24.301 [23]. If Length of UE Network
Capability is zero, then the UE Network Capability parameter shall not be present.
The MS Network Capability coding is specified in clause 10.5.5.12 of 3GPP TS 24.008 [5]. If Length of MS Network
Caapability is zero, then the MS Network Capability parameter shall not be present.
The Voice Domain Preference and UE's Usage Setting coding is specified in clause 10.5.5.28 of 3GPP TS 24.008 [5]. If
Length of Voice Domain Preference and UE's Usage Setting is zero, then the Voice Domain Preference and UE's Usage
Setting parameter shall not be present.
Used Cipher indicates the GSM ciphering algorithm that is in use.
Used NAS Cipher indicates the EPS ciphering algorithm that is in use.
ETSI
The Access restriction data is composed of UNA(UTRAN Not Allowed), GENA(GERAN Not Allowed), GANA(GAN
Not Allowed), INA(I-HSPA-Evolution Not Allowed), ENA(E-UTRAN Not Allowed) and HNNA(HO-To-Non-3GPP-
Access Not Allowed).
If the SGSN support the Higher bitrates than 16 Mbps flag, the Higher bitrates than 16 Mbps flag shall be included in
the MM Context if:
- the source S4-SGSN has received "Higher bitrates than 16 Mbps flag" in the RANAP Initial UE Message or in
RANAP Relocation Complete as defined in TS 25.413 [33] from the RNC, or
- the source S4-SGSN has stored the "Higher bitrates than 16 Mbps flag" (received from an SGSN via the
Identification Response, Context Response or Forward Relocation Request during earlier procedures).
The S4-SGSN shall set the "Higher bitrates than 16 Mbps flag" to "1" if "Higher bitrates than 16 Mbps flag" is
"allowed" and to "0" if it is "not allowed". The Length of Higher bitrates than 16 Mbps flag shall be set to zero if the
S4-SGSN has not received the "Higher bitrates than 16 Mbps flag".
As depicted in Figure 8.38-1, the GSM Key, Used Cipher and Authentication Triplets that are unused in the old SGSN
shall be transmitted to the new SGSN for the GSM subscribers. An array of at most 5 Authentication Triplets may be
included. The field 'Number of Triplet' shall be set to the value '0' if no Authentication Triplet is included (i.e. octets '16
to h' are absent).
The Authentication Triplet coding is specified in Figure 8.38-7.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Security Mode Spare DRXI CKSN
6 Number of Triplet Spare UAMB SAMB
RI RI
7 Spare Used Cipher
8 to 15 Kc
16 to h Authentication Triplet [1..5]
(h+1) to DRX parameter
(h+2)
j to (j+3) Uplink Subscribed UE AMBR
(j+4) to (j+7) Downlink Subscribed UE AMBR
i to (i+3) Uplink Used UE AMBR
(i+4) to (i+7) Downlink Used UE AMBR
q Length of UE Network Capability
(q+1) to k UE Network Capability
k+1 Length of MS Network Capability
(k+2) to m MS Network Capability
m+1 Length of Mobile Equipment Identity (MEI)
(m+2) to r Mobile Equipment Identity (MEI)
r+1 Spare HNNA ENA INA GANA GENA UNA
r+2 Length of Voice Domain Preference and UE's Usage
Setting
(r+3) to s Voice Domain Preference and UE's Usage Setting
(s+1) to These octet(s) is/are present only if explicitly specified
(n+4)
Figure 8.38-1: GSM Key and Triplets
As depicted in Figure 8.38-2, the UMTS Key, Used Cipher and Authentication Quintuplets that are unused in the old
SGSN shall be transmitted to the new SGSN when the UMTS subscriber is attached to a GSM BSS in the old system, in
case the user has a ME capable of UMTS AKA. An array of at most 5 Authentication Quintuplets may be included. The
field 'Number of Quintuplets' shall be set to the value '0' if no Authentication Quintuplet is included (i.e. octets '40 to h'
are absent).
The Authentication Quintuplet coding is specified in Figure 8.38-8.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Security Mode Spare DRXI CKSN/KSI
6 Number of Spare UAMB SAMB
Quintuplets RI RI
7 Spare Used Cipher
8 to 23 CK
24 to 39 IK
40 to h Authentication Quintuplet [1..5]
(h+2)
(j+12) to Downlink Used UE AMBR
(i+4)
Setting
s+1 Length of Higher bitrates than 16 Mbps flag
s+2 Higher bitrates than 16 Mbps flag
(n+4)
Figure 8.38-2: UMTS Key, Used Cipher and Quintuplets
As depicted in Figure 8.38-3, the GSM Key, Used Cipher and Authentication Quintuplets that are unused in the old
SGSN shall be transmitted to the new SGSN when the UMTS subscriber is attached to a GSM BSS in the old system, in
case the user has a ME no capable of UMTS AKA. An array of at most 5 Authentication Quintuplets may be included.
The field 'Number of Quintuplets' shall be set to the value '0' if no Authentication Quintuplet is included (i.e. octets '16
to h' are absent).
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Security Mode Spare DRXI CKSN/KSI
Quintuplets RI RI
7 Spare Used Cipher
8 to 15 Kc
16 to h Authentication Quintuplets [1..5]
(h+2)
Setting
(n+4)
Figure 8.38-3: GSM Key, Used Cipher and Quintuplets
As depicted in Figure 8.38-4, the UMTS Key, KSI and unused Authentication Quintuplets in the old SGSN may be
transmitted to the new SGSN/MME when the UMTS subscriber is attached to UTRAN/GERAN in the old system, but
it is not allowed to send quintuplets to an MME in a different serving network domain (see 3GPP TS 33.401 [12] clause
6.1.6). The MME may forward the UMTS Key, KSI and unused Authentication Quintuplets which were previously
stored back to the same SGSN, for further details, refer to 3GPP TS 33.401 [12]. An array of at most 5 Authentication
Quintuplets may be included. The field 'Number of Quintuplets' shall be set to the value '0' if no Authentication
Quintuplet is included (i.e. octets '40 to h' are absent).
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Security Mode Spare DRXI KSI
Quintuplets RI RI
7 Spare
8 to 23 CK
24 to 39 IK
40 to h Authentication Quintuplet [1..5]
(h+2)
Setting
(n+4)
Figure 8.38-4: UMTS Key and Quintuplets
As depicted in Figure 8.38-5, the current EPS Security Context, a non-current EPS Security Context (if available), and
unused Authentication Quadruplets in the old MME may be transmitted to the new MME. If the new MME is not in the
same serving network domain then only the current EPS Security Context may be transmitted. An array of at most 5
Authentication Quadruplets may be included. The field 'Number of Quadruplets' shall be set to the value '0' if no
Authentication Quadruplet is included (i.e. octets '46 to g' are absent). Authentication Quintuplets shall not be
transmitted to the new MME (i.e. octets 'g+1 to h' shall be absent) even if the old MME has the Authentication
Quintuplets for this UE. The field 'Number of Quintuplets' shall be set to the value '0'. The reasons for not sending
Quintuplets are specified in3GPP TS 33.401 [12] clause 6.1.6.
The Authentication Quintuplet and Authentication Quadruplet codings are specified in Figure 8.38-8 and Figure 8.38-9
respectively.
The value of the NAS Downlink Count shall be set to the value that shall be used to send the next NAS message.
The value of the NAS Uplink Count shall be set to the largest NAS Uplink Count that was in a successfully integrity
verified NAS message.
In Figure 8.38-5, the fields for the Old EPS Security Context (i.e. octets from s to s+64) may be present only in S10
Forward Relocation Request message according to the Rules on Concurrent Running of Security Procedures, which are
specified in 3GPP TS 33.401 [12]. The octets for Old EPS Security Context shall be present if the OSCI (Old Security
Context Indicator), bit 1 of octet 6) is set to "1"; otherwise they shall not be present.
If NHI_old (Next Hop Indicator for old EPS Security Context), bit 1 of octet s, is set to "1", then the parameters old NH
(Next Hop) and old NCC (Next Hop Chaining Count) shall be present; otherwise the octets for old NH parameter shall
not be present and the value of old NCC parameter shall be ignored by the receiver.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Security Mode NHI DRXI KSIASME
6 Number of Number of UAMB OSCI
Quintuplets Quadruplet RI
7 SAMB Used NAS integrity Used NAS Cipher
RI protection algorithm
8 to 10 NAS Downlink Count
11 to 13 NAS Uplink Count
14 to 45 KASME
46 to g Authentication Quadruplet [1..5]
(g+1) to h Authentication Quintuplet [1..5]
(h+2)
p to (p+31) NH
p+32 Spare NCC
s NHI_o Spare old KSIASME old NCC
ld
(s+1) to old KASME
(s+32)
(s+33) to old NH
(s+64)
s+65 Length of Voice Domain Preference and UE's Usage
Setting
(s+66) to t Voice Domain Preference and UE's Usage Setting
(t+1) to (t+2) Length of UE Radio Capability for Paging information
(t+3) to u UE Radio Capability for Paging information
u+1 to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.38-5: EPS Security Context and Quadruplets
If NHI (Next Hop Indicator), bit 5 of octet 5, is set to "1", then the optional parameters NH (Next Hop) and NCC (Next
Hop Chaining Count) are both present, otherwise their octets are not present.
The UE Radio Capability for Paging information is specified in the subclause 9.2.1.98 of 3GPP TS 36.413 [10]. If
Length of UE Radio Capability for Paging information is zero, then the UE Radio Capability for Paging information
shall not be present. The old MME shall, when available, include UE Radio Capability for Paging information to the
new MME as specified in the subclause 5.11.4 of 3GPP TS 23.401 [4].
As depicted in Figure 8.38-6, the old MME will derive CK' and IK' from KASME and transmit the CK' and IK' to the new
SGSN. Authentication Quintuplets, if available, shall be transmitted to the SGSN if, and only if the MME received
them from this SGSN earlier, according to 3GPP TS 33.401 [12] clause 6.1.5. An array of at most 5 Authentication
Quintuplets may be included. The field 'Number of Quintuplets' shall be set to the value '0' if no Authentication
Quintuplet is included (i.e. octets 'g+1 to h' are absent). An array of at most 5 Authentication Quadruplets may be
included. The field 'Number of Quadruplets' shall be set to the value '0' if no Authentication Quadruplet is included (i.e.
octets '40 to g' are absent). A key KASME shall never be transmitted to an SGSN according to 3GPP TS 33.401 [12]
clause 6.4.
The Authentication Quintuplet and Authentication Quadruplet codings are specified in Figure 8.38-8 and Figure 8.38-9
respectively.
ETSI
The old SGSN/MME may deliver both Authentication Quadruplets and Authentication Quintuplets it holds to the peer
combo node to optimize the procedure.
NOTE: 3GPP TS 33.401 [12] states that "EPS authentication data shall not be forwarded from an MME towards
an SGSN". The statement above assumes that the old MME can determine by local configuration that the
peer node is a combo SGSN/MME (as opposed to a single SGSN).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Security Mode Spare DRXI KSIASME
6 Number of Number of UAMB SAMB
Quintuplets Quadruplet RI RI
7 Spare
8 to 23 CK
24 to 39 IK
40 to g Authentication Quadruplet [1..5]
(g+1) to h Authentication Quintuplet [1..5]
(h+2)
Setting
(n+4)
Figure 8.38-6: UMTS Key, Quadruplets and Quintuplets
Bits
Octets 8 7 6 5 4 3 2 1
1 to 16 RAND
17 to 20 SRES
21 to 28 Kc
Figure 8.38-7: Authentication Triplet
Bits
Octets 8 7 6 5 4 3 2 1
1 to 16 RAND
17 XRES Length
18 to m XRES
(m+1) to CK
(m+16)
(m+17) to IK
(m+32)
m+33 AUTN Length
(m+34) to n AUTN
Figure 8.38-8: Authentication Quintuplet
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
1 to 16 RAND
17 XRES Length
18 to k XRES
k+1 AUTN Length
(k+2) to m AUTN
(m+1) to KASME
(m+32)
Figure 8.38-9: Authentication Quadruplet
Table 8.38-1: Security Mode Values
Security Type Value (Decimal)

GSM Key and Triplets 0
UMTS Key, Used Cipher and Quintuplets 1
GSM Key, Used Cipher and Quintuplets 2
UMTS Key and Quintuplets 3
EPS Security Context and Quadruplets 4
UMTS Key, Quadruplets and Quintuplets 5
<spare> 6-7
Table 8.38-2: Used NAS Cipher Values
Cipher Algorithm Value (Decimal)

No ciphering 0
128-EEA1 1
128-EEA2 2
128-EEA3 3
EEA4 4
EEA5 5
EEA6 6
EEA7 7
<spare> 8-15
Table 8.38-3: Used Cipher Values
Cipher Algorithm Value (Decimal)

No ciphering 0
GEA/1 1
GEA/2 2
GEA/3 3
GEA/4 4
GEA/5 5
GEA/6 6
GEA/7 7
Table 8.38-4: Used NAS integrity protection algorithm Values
Integrity protection Value (Decimal)

Algorithm
No integrity protection 0
128-EIA1 1
128-EIA2 2
128-EIA3 3
EIA4 4
EIA5 5
EIA6 6
EIA7 7
ETSI
8.39 PDN Connection

The PDN connection is a grouped IE containing a number of other IEs and shall be coded as depicted in Table 8.39-1.
The PDN Connection IE may be repeated within a message when more than one PDN Connection is required to be sent.
If so, the repeated IEs shall have exactly the same Instance values to represent a list of grouped IEs.
Table 8.39-1: PDN Connection Grouped Type

elements
8.40 PDU Numbers

The PDU Numbers information element contains the sequence number status corresponding to a Bearer context in the
old SGSN. This information element shall be sent only when acknowledged peer-to-peer LLC operation is used for the
Bearer context or when the "delivery order" QoS attribute is set in the Bearer context QoS profile.
NSAPI identifies the Bearer context for which the PDU Number IE is intended.
DL GTP-U Sequence Number is the number for the next downlink GTP-U T-PDU to be sent to the UE when "delivery
order" is set.
UL GTP-U Sequence Number is the number for the next uplink GTP-U T-PDU to be tunnelled to the S-GW when
"delivery order" is set.
The Send N-PDU Number is used only when acknowledged peer-to-peer LLC operation is used for the Bearer context.
Send N-PDU Number is the N-PDU number to be assigned by SNDCP to the next down link N-PDU received from the
S-GW.
The Receive N-PDU Number is used only when acknowledged peer-to-peer LLC operation is used for the Bearer
context. The Receive N-PDU Number is the N-PDU number expected by SNDCP from the next up link N-PDU to be
The PDU Number IE will be repeated for each Bearer Context for which this IE is required.
PDU Numbers IE is coded as depicted in Figure 8.40-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare(0 0 0 0) NSAPI
6-7 DL GTP-U Sequence Number
8-9 UL GTP-U Sequence Number
10-11 Send N-PDU Number
12-13 Receive N-PDU Number
Figure 8.40-1: PDU Numbers
8.41 Packet TMSI (P-TMSI)

The P-TMSI, unambiguously associated with a given UE and routeing area, is given by:
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Packet TMSI (P-TMSI)
The P-TMSI is defined in 3GPP TS 23.003 [2].
Figure 8.41-1: Packet TMSI (P-TMSI)
8.42 P-TMSI Signature

The content and the coding of the P-TMSI Signature information element are defined in 3GPP TS 24.008 [5].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) P-TMSI Signature
Figure 8.42-1: P-TMSI Signature
8.43 Hop Counter

Where Intra Domain Connection of RAN Nodes to Multiple CN Node is applied, the Hop Counter may be used to
prevent endless loops when relaying Identification Request messages and Context Request messages. The maximum
value is operator specific and shall not be lower than 1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Hop Counter
Figure 8.43-1: Hop Counter
8.44 UE Time Zone

UE Time Zone is used to indicate the offset between universal time and local time in steps of 15 minutes of where the
UE currently resides. The "Time Zone" field uses the same format as the "Time Zone" IE in 3GPP TS 24.008 [5].
UE Time Zone is coded as this is depicted in Figure 8.44-1. The value of the Time Zone field represents the time zone
adjusted for daylight saving time. The value of the Daylight Saving Time field specifies the adjustment that has been
made.
receiving side.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Time Zone
6 Spare Daylight
Saving Time
Figure 8.44-1: UE Time Zone
ETSI
Table 8.44-2 Possible values for the "Daylight Saving Time" field and their meanings.
Daylight Saving Time Value (binary)

Bit 2 Bit 1
No adjustment for Daylight Saving Time 0 0
+1 hour adjustment for Daylight Saving Time 0 1
+2 hours adjustment for Daylight Saving Time 1 0
Spare 1 1
8.45 Trace Reference

Trace Reference shall be coded as depicted in Figure 8.45-1. See 3GPP TS 32.422 [18], clause 5.6, for the definition of
Trace Reference.
See 3GPP TS 24.008 [5], clause 10.5.1.4, Mobile Identity, for the coding of MCC and MNC, whose values are obtained
from the serving PLMN that the EM/NM is managing. If MNC is 2 digits long, bits 5 to 8 of octet 6 are coded as
"1111".
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 6
4 Spare Instance
8 to10 Trace ID
Figure 8.45-1: Trace Reference
8.46 Complete Request Message

The Complete Request Message is coded as depicted in Figure 8.46-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Complete Request Message Type
6 to (n+4) Complete Request Message
Figure 8.46-1: Complete Request Message
Complete Request Message type values are specified in Table 8.46-1.
Table 8.46-1: Complete Request Message type values and their meanings
Location Types Values (Decimal)

Complete Attach Request Message 0
Complete TAU Request Message 1
<spare> 2-255
8.47 GUTI
The GUTI is coded as depicted in Figure 8.47-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
8 to 9 MME Group ID
10 MME Code
11 to (n+4) M-TMSI
Figure 8.47-1: GUTI
The "MME Group ID", "MME Code" and "M-TMSI" are specified in 3GPP TS 23.003 [2].
8.48 Fully Qualified Container (F-Container)

Fully Qualified Container (F-Container) is coded as depicted in Figure 8.48-1.
All Spare bits are set to zeros by the sender and ignored by the receiver.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare Container Type
6 to (n+4) F-Container field
Figure 8.48-1: Full Qualified Container (F-Container)
The F-Container field shall contain one of the following information, depending of the contents of the container
transported by the specific GTP Information Element:
- transparent copy of the corresponding IEs (see subclause 8.2.2):
- the "Source to Target Transparent Container" or the "Target to Source Transparent Container" as specified in
3GPP TS 25.413 [33]; or
- the "SON Configuration Transfer" as specified in 3GPP TS 36.413 [10]; or
- the "eNB Status Transfer Transparent Container" as specified in 3GPP TS 36.413 [10]; or
- "Source BSS to Target BSS Transparent Container" or "Target BSS to Source BSS Transparent Container" as
specified in 3GPP TS 48.018 [34] or 3GPP TS 25.413 [33], which contains the value part of the "Source BSS
to Target BSS Transparent Container" IE or the value part of the "Target BSS to Source BSS Transparent
Container" IE defined in 3GPP TS 48.018 [34], i.e. octets 3 to n, excluding octet 1 (Element ID) and octet 2,
2a (Length) ; or
- transparent copy of the value part of the "NBIFOM Container" as specified in 3GPP TS 24.301 [23].
- transparent copy of the octets of the encoded OCTET STRING of the "Source to Target Transparent Container"
or the "Target to Source Transparent Container" specified in 3GPP TS 36.413 [10]; or
- transparent copy of the BSSGP RIM PDU as specified in 3GPP TS 48.018 [34]; or
- the Packet Flow ID, Radio Priority, SAPI, PS Handover XID parameters as specified in figure 8.42-2.
NOTE 1: Annex B.2 provides further details on the encoding of Generic Transparent Containers over RANAP, S1-
AP and GTP. See also Annex C of 3GPP TS 36.413 [10] for further details on how the MME constructs
the F-Container field from the Source to Target Transparent Container or Target to Source Transparent
Container IEs received from S1-AP.
ETSI
Container Type values are specified in Table 8.48-2.
Table 8. 48-2: Container Type values
Container Types Values (Decimal)

Reserved 0
UTRAN Transparent Container 1
BSS Container 2
E-UTRAN Transparent Container 3
NBIFOM Container 4
<spare> 5-255
NOTE 2: For any other new future F-Container content types, new Container Type values may be needed, although
use of RAT agnostic containers should be used whenever possible.
The BSS Container IE in the Bearer Context IE in Forward Relocation Request and Context Response messages is
coded as depicted in Figure 8.48-3.
Bits
Octets 8 7 6 5 4 3 2 1
6 Spare PHX SAPI RP PFI
a Packet Flow ID
b SAPI Spare Radio Priority
c XiD parameters length
d to n XiD parameters
Figure 8.48-3: BSS Container
The flags PFI, RP, SAPI and PHX in octet 6 indicate the corresponding type of parameter (Packet FlowID, Radio
Priority, SAPI and PS handover XID parameters) shall be present in a respective field or not. If one of these flags is set
to "0", the corresponding field shall not be present at all. The Spare bit shall be set to zero by the sender and ignored by
the receiver.
If PFI flag is set, Packet Flow ID shall be present in Octet a.
If RP flag is set, Radio Priority shall be present in Octet b.
If SAPI flag is set, SAPI shall be present in Octet b.
If PHX flag is set:
- XiD parameters length is present in Octet c.
- XiD parameters are present in Octet d to n.
8.49 Fully Qualified Cause (F-Cause)

Fully Qualified Cause (F- Cause) is coded as depicted in Figure 8.49-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare Cause Type
6 to (n+4) F-Cause field
Figure 8.49-1: Full Qualified Cause (F-Cause)
The value of Instance field of the F-Cause IE in a GTPv2 message shall indicate whether the F-Cause field contains
RANAP Cause, BSSGP Cause or S1-AP Cause.
All spare bits shall be set to zeros by the sender and ignored by the receiver.
ETSI
F-Cause field is coded as follows:
- For RANAP Cause, the F-Cause field shall contain a non-transparent copy of the cause value of the
corresponding IE (see subclause 8.2.2), "Cause", as defined in clause 9.2.1.4 in 3GPP TS 25.413 [33].
Cause Type field shall be ignored by the receiver. The value of F-Cause field (which has a range of 1..512) is
transferred over the Iu interface and encoded into two octet as binary integer.
- For BSSGP Cause, the F-Cause field shall contain a non-transparent copy of the cause value of the
corresponding IE (see subclause 8.2.2), "Cause", as defined in clause 11.3.8 in 3GPP TS 48.018 [34].
Cause Type field shall be ignored by the receiver. The value of F-Cause field (which has a range of 0..255) is
transferred over the Gb interface and encoded into one octet as binary integer.
- For S1-AP Cause, the F-Cause field shall contain a non-transparent copy of the cause value of the corresponding
IE (see subclause 8.2.2), "Cause", as defined in clause 9.2.1.3 in 3GPP TS 36.413 [10].
Cause Type field shall contain the RAN Cause subcategory as specified in 3GPP TS 36.413 [10] and it shall be
encoded as in Table 8.49-1. The value of F-Cause field (and the associated RAN cause subcategory) is
transferred over the S1-AP interface and encoded into one octet as binary integer.
Table 8.49-1: Cause Type values and their meanings
Cause Type Values (Decimal)

Radio Network Layer 0
Transport Layer 1
NAS 2
Protocol 3
Miscellaneous 4
<spare> 5 to15
8.50 PLMN ID
Octets 5-7 shall contain a non-transparent copy of the " PLMN Identity" parameter in 3GPP TS 36.413 [10].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) PLMN ID
Figure 8.50-1: PLMN ID
The encoding of the PLMN ID field is shown in Figures 8.50-2 and 8.50-3.
If three digits are included in the MNC, octets 5 to 7 shall be encoded as shown in Figure 8.50-2.
Bits
Octets 8 7 6 5 4 3 2 1
Figure 8.50-2: PLMN ID Parameter with 3-digit MNC
If only two digits are included in the MNC, octets 5 to 7 shall be encoded as shown in Figure 8.50-3 with bits 5 to 8 of
octet 6 (MNC digit 3) coded as "1111".
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
6 1111 MCC digit 3
Figure 8.50-3: PLMN ID Parameter with 2-digit MNC
NOTE: The encoding is different from elsewhere in this document and is specified according to 3GPP TS 36.413
[10].
8.51 Target Identification

The Target Identification information element is coded as depicted in Figure 8.51-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Target Type
6 to (n+4) Target ID
Figure 8.51-1: Target Identification
Target Type values are specified in Table 8.51-1.
The Target Type is RNC ID for SRNS relocation procedure, handover to UTRAN and RAN Information Relay towards
UTRAN or GERAN operating in GERAN Iu mode. In this case the "Target ID" field shall contain a non-transparent
copy of the corresponding IEs (see subclause 8.2.2) and be encoded as specified in Figure 8.51-1a below. The "Target
RNC-ID" part of the "Target ID" parameter is specified in 3GPP TS 25.413 [33].
NOTE 1: The ASN.1 parameter "Target ID" is forwarded non-transparently in order to maintain backward
compatibility.
NOTE 2: The preamble of the "Target RNC-ID" (numerical value of e.g. 0x20) shall not be included into octets 6
to (n+4). Also, the optional "iE-Extensions" parameter shall not be included into the GTP IE.
Bits
Octets 8 7 6 5 4 3 2 1
9 to 10 LAC
11 RAC (see NOTE 3)
12 to 13 RNC-ID
a to (a+1) Extended RNC-ID (optional)
Figure 8.51-1a: Target ID for Type RNC ID
If only two digits are included in the MNC, then bits 5 to 8 of octet 7 (MNC digit 3) shall be coded as "1111".
The location area code (LAC) consists of 2 octets. Bit 8 of octet 9 is the most significant bit and bit 1 of octet 10 is the
least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full
hexadecimal representation shall be used.
The RNC-ID consists of 2 octets and contains 12 bits long value (see 3GPP TS 25.413 [7]). Bit 4 of octet 12 is the most
significant bit and bit 1 of octet 13 is the least significant bit (bits 8 to 5 of octet 12 are set to 0). The coding of the
RNC-ID is the responsibility of each administration. Coding using full hexadecimal representation shall be used.
The Extended RNC-ID consists of 2 octets and contains 16 bits long value within the range 4096 to 65535. Bit 8 of
octet a is the most significant bit and bit 1 of octet (a+1) is the least significant bit. The coding of the Extended RNC-ID
is the responsibility of each administration. Coding using full hexadecimal representation shall be used. If the optional
Extended RNC-ID is included, then the receiver shall ignore the RNC-ID.
ETSI
If the optional Extended RNC-ID is not included, then the length variable 'n' = 8 and the overall length of the IE is 13
octets. Otherwise, 'n' = 10 and the overall length of the IE is 15 octets.
NOTE 3: In the "TargetRNC-ID" ASN.1 type definition in 3GPP TS 25.413 [7] the "RAC" parameter is marked as
optional. RAC is however always available at an SGSN/MME when it sends the RAC in e.g. a GTPv2
Forward Relocation Request message.
The Target Type is Macro eNodeB ID for handover to E-UTRAN Macro eNodeB and RAN Information Relay towards
E-UTRAN. In this case the coding of the Target ID field shall be coded as depicted in Figure 8.51-2.
Bits
Octets 8 7 6 5 4 3 2 1
9 Spare Macro eNodeB ID
10 to 11 Macro eNodeB ID
12 to 13 Tracking Area Code (TAC)
Figure 8.51-2: Target ID for Type Macro eNodeB
The Macro eNodeB ID consists of 20 bits. Bit 4 of Octet 9 is the most significant bit and bit 1 of Octet 11 is the least
significant bit. The coding of the Macro eNodeB ID is the responsibility of each administration. Coding using full
hexadecimal representation shall be used.
The Target Type is Home eNodeB ID for handover to E-UTRAN Home eNodeB. In this case the coding of the Target
ID field shall be coded as depicted in Figure 8.51-3.
Bits
Octets 8 7 6 5 4 3 2 1
9 Spare Home eNodeB ID
10 to 12 Home eNodeB ID
13 to 14 Tracking Area Code (TAC)
Figure 8.51-3: Target ID for Type Home eNodeB
The Home eNodeB ID consists of 28 bits. See 3GPP TS 36.413 [10]. Bit 4 of Octet 9 is the most significant bit and bit
1 of Octet 12 is the least significant bit. The coding of the Home eNodeB ID is the responsibility of each administration.
Coding using full hexadecimal representation shall be used.
The Target Type is Cell Identifier for E-UTRAN handover to GERAN and RAN Information Relay towards GERAN.
In this case the coding of the Target ID field shall be same as the Octets 3 to 10 of the Cell Identifier IEI in 3GPP TS
48.018 [34].
Table 8.51-1: Target Type values and their meanings
Target Types Values (Decimal)

RNC ID 0
Macro eNodeB ID 1
Cell Identifier 2
Home eNodeB ID 3
<spare> 4 to 255
8.52 Void
8.53 Packet Flow ID

The Packet Flow Id information element contains the packet flow identifier assigned to an EPS Bearer context as
identified by EPS Bearer ID.
ETSI
The spare bits 8 to 5 in octet 5 indicate unused bits, which shall be set to 0 by the sending side and which shall not be
evaluated by the receiving side.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare EBI
6 to (n+4) Packet Flow ID
Figure 8.53-1: Packet Flow ID
8.54 RAB Context

The RAB Context shall be coded as is depicted in Figure 8.54-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 9
4 Spare Instance
5 Spare NSAPI
6 to 7 DL GTP-U Sequence Number
8 to 9 UL GTP-U Sequence Number
10 to 11 DL PDCP Sequence Number
12 to 13 UL PDCP Sequence Number
Figure 8.54-1: RAB Context
The RAB Context IE may be repeated within a message with exactly the same Type and Instance to represent a list.
The RAB context information element contains sequence number status for one RAB in RNC, which corresponds to
one PDP context. The RAB contexts are transferred between the RNCs via the SGSNs at inter SGSN hard handover.
NSAPI identifies the PDP context and the associated RAB for which the RAB context IE is intended.
DL GTP-U Sequence Number is the number for the next downlink GTP-U T-PDU to be sent to the UE.
UL GTP-U Sequence Number is the number for the next uplink GTP-U T-PDU to be tunnelled to the SGW.
DL PDCP Sequence Number is the number for the next downlink PDCP-PDU to be sent to the UE.
UL PDCP Sequence Number is the number for the next uplink PDCP-PDU to be received from the UE.
8.55 Source RNC PDCP context info

The purpose of the Source RNC PDCP context info IE is to transfer RNC PDCP context information from a source
RNC to a target RNC during an SRNS relocation.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) RRC Container
Figure 8.55-1: Source RNC PDCP context info
8.56 Port Number

Port Number is coded as depicted in Figure 8.56-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 2
4 Spare Instance
5 to 6 Port Number
Figure 8.56-1: UDP Source Port Number
8.57 APN Restriction

The APN Restriction information element contains an unsigned integer value indicating the level of restriction imposed
on EPS Bearer Contexts created to the associated APN.
The APN Restriction IE is coded as depicted in Figure 8.57-1:
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Restriction Type value
Figure 8.57-1: APN Restriction Type Information Element
An APN Restriction value may be configured for each APN in the PGW. It is used to determine, on a per UE basis,
whether it is allowed to establish EPS bearers to other APNs.
Table 8.57-1: Valid Combinations of APN Restriction
Maximum Type of APN Application Example APN Restriction Value allowed to be

APN established
Restriction
Value
0 No Existing Contexts or Restriction All
1 Public-1 MMS 1, 2, 3
2 Public-2 Internet 1, 2
3 Private-1 Corporate (e.g. who use 1
MMS)
4 Private-2 Corporate (e.g. who do not None
use MMS)
8.58 Selection Mode

The Selection mode information element indicates the origin of the APN in the message.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare
Selec. Mode
Figure 8.58-1: Selection Mode Information Element
ETSI
Table 8.58-1: Selection Mode Values

Selection mode value Value (Decimal)
MS or network provided APN, subscription verified 0
MS provided APN, subscription not verified 1
Network provided APN, subscription not verified 2
For future use. Shall not be sent. If received, shall be interpreted as the value "2". 3
8.59 Source Identification

The Source Identification information element is coded as depicted in Figure 8.59-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 12 Target Cell ID
13 Source Type
14 to (n+4) Source ID
Figure 8.59-1: Source Identification
The Target Cell ID shall be same as the Octets 3 to 10 of the Cell Identifier IEI in 3GPP TS 48.018 [34].
Source Type values are specified in Table 8.59-1.
If the Source Type is Cell ID, this indicates PS handover from GERAN A/Gb mode. In this case the coding of the
Source ID field shall be same as the Octets 3 to 10 of the Cell Identifier IEI in 3GPP TS 48.018 [34].
If the Source Type is RNC ID, this indicates PS handover from GERAN Iu mode or for inter-RAT handover from
UTRAN. In this case the Source ID field shall include a transparent copy of the corresponding parameter (see subclause
8.2.2), the Source RNC-ID as specified within the "Source ID" parameter in 3GPP TS 25.413 [33].
NOTE: In fact, the ASN.1/PER encoded binary value of the "Source RNC ID" shall be copied into octets 14 to
(n+4).
Table 8.59-1: Source Type values and their meanings
Source Types Values (Decimal)

Cell ID 0
RNC ID 1
reserved (NOTE) 2
<spare> 3-255
NOTE: This value was allocated in an earlier version of the protocol and
shall not be used.
8.60 Void
8.61 Change Reporting Action

Change Reporting Action IE is coded as depicted in Figure 8.61-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Action
Figure 8.61-1: Change Reporting Action
ETSI
Table 8.61-1: Action values

Action Value (Decimal)
Stop Reporting 0
Start Reporting CGI/SAI 1
Start Reporting RAI 2
Start Reporting TAI 3
Start Reporting ECGI 4
Start Reporting CGI/SAI and RAI 5
Start Reporting TAI and ECGI 6
<spare> 7-255
Stop Reporting stops all reporting action types.
8.62 Fully qualified PDN Connection Set Identifier (FQ-CSID)

A fully qualified PDN Connection Set Identifier (FQ-CSID) identifies a set of PDN connections belonging to an
arbitrary number of UEs on a MME, SGW, TWAN, ePDG or PGW. The FQ-CSID is used on S5, S8, S2a, S2b and S11
interfaces.
The size of CSID is two octets. The FQ-CSID is coded as follows:
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Node-ID Type Number of CSIDs= m
6 to p Node-ID
(p+1) to First PDN Connection Set Identifier (CSID)
(p+2)
(p+3) to Second PDN Connection Set Identifier (CSID)
(p+4)
... ...
q to q+1 m-th PDN Connection Set Identifier (CSID)
(q+2) to These octet(s) is/are present only if explicitly specified
(n+4)
Figure 8.62-1: FQ-CSID
Where Node-ID Type values are:
0 indicates that Node-ID is a global unicast IPv4 address and p = 9.
1 indicates that Node-ID is a global unicast IPv6 address and p = 21.
2 indicates that Node-ID is a 4 octets long field with a 32 bit value stored in network order, and p= 9. The coding
of the field is specified below:
- Most significant 20 bits are the binary encoded value of (MCC * 1000 + MNC).
- Least significant 12 bits is a 12 bit integer assigned by an operator to an MME, SGW, TWAN, ePDG or PGW.
Other values of Node-ID Type are reserved.
Values of Number of CSID other than 1 are only employed in the Delete PDN Connection Set Request.
The node that creates the FQ-CSID, (i.e. MME for MME FQ-CSID, SGW for SGW FQ-CSID, TWAN for TWAN FQ-
CSID, ePDG for ePDG FQ-CSID and PGW for PGW FQ-CSID), is responsible for making sure the Node-ID is
globally unique and the CSID value is unique within that node.
When a FQ-CSID is stored by a receiving node, it is stored on a PDN basis even for messages impacting only one
bearer (i.e. Create Bearer Request). See 3GPP TS 23.007 [17] for further details on the CSID and what specific
requirements are placed on the PGW, TWAN, ePDG, SGW and MME.
ETSI
8.63 Channel needed

The Channel needed shall be coded as depicted in Figure 8.63-1. Channel needed is coded as the IEI part and the value
part of the Channel Needed IE defined in 3GPP TS 44.018[28]
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Channel Needed
Figure 8.63-1: Channel needed
8.64 eMLPP Priority

The eMLPP-Priority shall be coded as depicted in Figure 8.64-1. The eMLPP Priority is coded as the value part of the
eMLPP-Priority IE defined in 3GPP TS 48.008 [29] (not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 [29]
length indicator).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) eMLPP-Priority
Figure 8.64-1: eMLPP Priority
8.65 Node Type

Node Type is coded as this is depicted in Figure 8.65-1.
Bits
Octets 8 7 6 5 4 3 2 1
2-3 Length = n (decimal)
4 Spare Instance
5 Node Type
Figure 8.65-1: Node Type
Node type values are specified in Table 8.65-1.
Table 8. 65-1: Node Type values
Node Types Values (Decimal)

MME 0
SGSN 1
<spare> 2-255
If with a Release Access Bearers Request, or Suspend Notification, or Resume an SGW receives a semantically
erroneus/unexpected Originating Node, then the following applies:
- If SGW has an active connection to an MME, but the Originating Node IE contains value "SGSN", then the
SGW shall not release the user plane and shall send a response to the SGSN with some appropriate cause value.
- If SGW has an active connection to an S4-SGSN, but the Originating Node IE contains value "MME", then the
SGW shall not release the user plane and shall send a response to the MME with some appropriate cause value.
ETSI
8.66 Fully Qualified Domain Name (FQDN)

Fully Qualified Domain Name (FQDN) is coded as depicted in Figure 8.66-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) FQDN
Figure 8.66-1: Fully Qualified Domain Name (FQDN)
The FQDN field encoding shall be identical to the encoding of a FQDN within a DNS message of section 3.1 of IETF
RFC 1035 [31] but excluding the trailing zero byte.
NOTE 1: The FQDN field in the IE is not encoded as a dotted string as commonly used in DNS master zone files.
A "PGW node name" IE in S3/S10/S16 GTP messages shall be a PGW host name as per subclause 4.3.2 of 3GPP TS
29.303 [32] when the PGW FQDN IE is populated from 3GPP TS 29.303 [32] procedures. Specifically, the first DNS
label is either "topon" or "topoff", and the canonical node name of the PGW starts at the third label. The same rules
apply to "SGW node name" IE on S3/S10/S16.
NOTE 2: The constraint of subclause 4.3.2 of 3GPP TS 29.303 format is on populating the IE by 3GPP nodes for
3GPP nodes, the receiver shall not reject an IE that is otherwise correctly formatted since the IE might be
populated for a non-3GPP node.
An "MME node name" IE and an "SGSN node name" IE in S3 GTP messages indicate the associated ISR node when
the ISR becomes active.
8.67 Private Extension

Private Extension is coded as depicted in Figure 8.Figure 8.67-1.
Enterprise ID can be found at IANA web site (http://www.iana.org/assignments/enterprise-numbers).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 6 Enterprise ID
7 to (n+4) Proprietary value
Figure 8.67-1. Private Extension
8.68 Transaction Identifier (TI)

Transaction Identifier is coded as depicted in Figure 8.68-1. It is defined in 3GPP TS 24.301 [23], clause 9.9.4.17 and is
coded as specified in 3GPP TS 24.007 [30], clause 11.2.3.1.3 Transaction identifier.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) Transaction Identifier
Figure 8.68-1: Transaction Identifier
ETSI
8.69 MBMS Session Duration

The MBMS Session Duration is defined in 3GPP TS 23.246 [37]. The MBMS Session Duration information element
indicates the estimated session duration of the MBMS service data transmission if available. The payload shall be
encoded as per the MBMS-Session-Duration AVP defined in 3GPP TS 29.061 [38], excluding the AVP Header fields
(as defined in IETF RFC 3588 [39], section 4.1).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 7 MBMS Session Duration
Figure 8.69-1: MBMS Session Duration
8.70 MBMS Service Area

The MBMS Service Area is defined in 3GPP TS 23.246 [37]. The MBMS Service Area information element indicates
the area over which the Multimedia Broadcast Multicast Service is to be distributed. The payload shall be encoded as
per the MBMS-Service-Area AVP defined in 3GPP TS 29.061 [38], excluding the AVP Header fields (as defined in
IETF RFC 3588 [39], section 4.1).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) MBMS Service Area
Figure 8.70-1: MBMS Service Area
8.71 MBMS Session Identifier

The MBMS Session Identifier information element contains a Session Identifier allocated by the BM-SC. The MBMS
Session Identifier value part consists of 1 octet. The content and the coding are defined in 3GPP TS 29.061 [38].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 MBMS Session Identifier
Figure 8.71-1: MBMS Session Identifier
8.72 MBMS Flow Identifier

The MBMS Flow Identifier is defined in 3GPP TS 23.246 [37]. In broadcast mode, the MBMS Flow Identifier
information element is included in MBMS Session Management messages to differentiate the different sub-sessions of
an MBMS user service (identified by the TMGI) providing location-dependent content. The payload shall be encoded as
per the MBMS-Flow-Identifier AVP defined in 3GPP TS 29.061 [38], excluding the AVP Header fields (as defined in
IETF RFC 3588 [39], section 4.1).
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 6 MBMS Flow Identifer
Figure 8.72-1: MBMS Flow Identifier
8.73 MBMS IP Multicast Distribution

The MBMS IP Multicast Distribution IE is sent by the MBMS GW to the MME/SGSN in the MBMS Session Start
Request. Source Specific Multicasting is used according to IETF RFC 4607 [40].
The IP Multicast Distribution Address and the IP Multicast Source Address fields contain the IPv4 or IPv6 address. The
Address Type and Address Length fields shall be included in each field:
- The Address Type, which is a fixed length code (of 2 bits) identifying the type of address that is used in the
Address field.
- The Address Length, which is a fixed length code (of 6 bits) identifying the length of the Address field.
- The Address, which is a variable length field shall contain either an IPv4 address or an IPv6 address.
Address Type 0 and Address Length 4 shall be used when Address is an IPv4 address.
Address Type 1 and Address Length 16 shall be used when Address is an IPv6 address.
Other combinations of values are not valid.
MBMS HC Indicator represents an indication if header compression should be used for MBMS user plane data, as
specified in 3GPP TS 25.413 [33]. MBMS HC Indicator field is encoded as a one octet long enumeration.
NOTE: Currently, 3GPP TS 25.413 [33] specifies two enumeration values: 0 (indicates "uncompressed-header")
and 1 (indicates "compressed-header").
Common Tunnel Endpoint Identifier is allocated at the source Tunnel Endpoint and signalled to the destination Tunnel
Endpoint. There is one Common Tunnel Endpoint Identifier allocated per MBMS bearer service. The recommendations
on how to set the value of C-TEID are provided in 3GPP TS 23.246 [37].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length=n
4 Spare Instance
5 to 8 Common Tunnel Endpoint Identifier
9 Address Type Address Length
10 to K IP Multicast Distribution Address (IPv4 or IPv6)
K+1 Address Type Address Length
(k+2) to m IP Multicast Source Address (IPv4 or IPv6)
m+1 MBMS HC Indicator
(m+2) to n These octet(s) is/are present only if explicitly specified
Figure 8.73-1: MBMS IP Multicast Distribution
8.74 MBMS Distribution Acknowledge

The MBMS Distribution Acknowledge IE is sent by the SGSN to the MBMS GW in the MBMS Session Start Response
and MBMS Session Update Response. It is used by the MBMS GW to decide if an IP Multicast Distribution user plane
shall be established, or a normal point-to-point user plane, or both.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare Distr Ind
6 to n+4 These octet(s) is/are present only if explicitly specified
Figure 8.74-1: MBMS Distribution Acknowledge
Table 8.74-1: Distribution Indication values
Distribution Indication Value (Decimal)

No RNCs have accepted IP multicast distribution 0
All RNCs have accepted IP multicast distribution 1
Some RNCs have accepted IP multicast distribution 2
Spare. For future use. 3
8.75 User CSG Information (UCI)

User CSG Information (UCI) is coded as depicted in Figure 8.75-1. The CSG ID is defined in 3GPP TS 23.003 [2].
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 145
2 to 3 Length = n
4 Spare Instance
8 spare CSG ID
9 to11 CSG ID
12 Access mode spare LCSG CMI
Figure 8.75-1: User CSG Information
For two digits in the MNC, bits 5 to 8 of octet 6 are coded as "1111".
The CSG ID consists of 4 octets. Bit 3 of Octet 8 is the most significant bit and bit 1 of Octet 11 is the least significant
bit. The coding of the CSG ID is the responsibility of the operator that allocates the CSG ID by administrative means.
Access mode values are specified in Table 8.75-1.
Table 8.75-1: Access mode values and their meanings
Access Mode Values (Decimal)

Closed Mode 0
Hybrid Mode 1
Reserved 2-3
Leave CSG flag (LCSG) shall be set to "1" if UE leaves CSG cell/Hybrid cell, and in this case, the receiving node shall
ignore the rest information in the IE.
CSG Membership Indication (CMI) values are specified in Table 8.75-2. CMI shall be included in the User CSG
Information if the Access mode is Hybrid Mode. For the other values of Access Mode, the CMI shall be set to 0 by the
sender and ignored by the receiver.
ETSI
Table 8.75-2: CSG Membership indication (CMI)
CMI Values (Decimal)

Non CSG membership 0
CSG membership 1
NOTE: Due to a specification oversight, the CMI values in the above table are reversed from the values of the
CMI IE (see subclause 8.79). Furthermore, the encoding is different between GTPv1 and GTPv2.
8.76 CSG Information Reporting Action

CSG Information Reporting Action is coded as depicted in Figure 8.76-1.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 146
2 to 3 Length = n
4 Spare Instance
5 Spare UCIU UCIS UCIC
HC HC SG
Figure 8.76-1: CSG Reporting Action
• Bit 1 – UCICSG: When set to "1", shall indicate to start reporting User CSG Info when the UE
enters/leaves/access through the CSG Cell.
• Bit 2 – UCISHC: When set to "1", shall indicate to start reporting User CSG Info when the UE
enters/leaves/access through Subscribed Hybrid Cell.
• Bit 3 – UCIUHC: When set to "1", shall indicate to start Reporting User CSG Info when the UE
enters/leaves/access through Unsubscribed Hybrid Cell.
All the bits 1 to 3 shall be set to 0 to stop reporting User CSG Info.
8.77 RFSP Index

Index to RAT/Frequency Selection Priority (RFSP Index) is coded as depicted in Figure 8.77-1, and contains a non-
transparent copy of the corresponding IE (see subclause 8.2.2), "Subscriber Profile ID for RAT/Frequency Priority
(SPID)" as specified in 3GPP TS 36.413 [10]. The SPID is an integer between 1 and 256 and is encoded as an unsigned
integer, which requires the two octets specified for the RFSP Index parameter.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 2
4 Spare Instance
5 to 6 RFSP Index
Figure 8.77-1. RFSP Index
8.78 CSG ID
CSG ID is coded as depicted in Figure 8.78-1. The CSG ID is defined in 3GPP TS 23.003 [2].
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 147
2 to 3 Length = n
4 Spare Instance
5 Spare CSG ID
6 to 8 CSG ID
Figure 8.78-1: CSG ID
The CSG ID consists of 4 octets. Bit 3 of Octet 5 is the most significant bit and bit 1 of Octet 8 is the least significant
bit. The coding of the CSG ID is the responsibility of the operator that allocates the CSG ID by administrative means.
8.79 CSG Membership Indication (CMI)

CSG Membership Indication is coded as depicted in Figure 8.79-1.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 148
2 to 3 Length = n
4 Spare Instance
5 Spare CMI
Figure 8.79-1: CSG Membership Indication
Table 8.79-1: void
CSG Membership Indication (CMI) values are specified in Table 8.79-2.
Table 8.79-2: CSG Membership indication (CMI)
CMI Values (Decimal)

CSG membership 0
Non CSG membership 1
NOTE: Due to a specification oversight, the CMI values in the above table are reversed from the values of the
CSG-Membership-Indication AVP in 3GPP TS 32.299 [54], as well as from the values of the CMI in the
UCI IE (see subclause 8.75). Therefore, when the above CMI values are sent over the charging interface,
the values are encoded as specified in 3GPP TS 32.299 [54].
8.80 Service indicator

Service indicator is coded as depicted in Figure 8.80-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 1
4 Spare Instance
5 Service indicator
Figure 8.80-1. Service indicator
Service indicator values are specified in Table 8.80-1.
ETSI
Table 8.80-1: Service indicator values
Service indicator Values (Decimal)

<spare> 0
CS call indicator 1
SMS indicator 2
<spare> 3-255
8.81 Detach Type

Detach Type is coded as depicted in Figure 8.81-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 1
4 Spare Instance
5 Detach Type
Figure 8.81-1: Detach Type
Table 8.81-1: Detach Type values
Detach Types Values (Decimal)

<reserved> 0
PS Detach 1
Combined PS/CS Detach 2
<spare> 3-255
8.82 Local Distinguished Name (LDN)

Represents the Local Distinguished Name (LDN) of the network element (see 3GPP TS 32.423 [44]).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to (n+4) LDN
Figure 8.82-1: Local Distinguished Name (LDN)
The LDN field consists of 1 up to a maximum of 400 ASCII characters, i.e., from 1 up to a maximum of 400 octets.
8.83 Node Features

Node Features IE is coded as depicted in Figure 8. 83-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Supported-Features
Figure 8.83-1: Node Features IE
ETSI
The Node Features IE takes the form of a bitmask where each bit set indicates that the corresponding feature is
supported. Spare bits shall be ignored by the receiver. The same bitmask is defined for all GTPv2 interfaces.
The following table specifies the features defined on GTPv2 interfaces and the interfaces on which they apply.
Table 8.83-1: Node Features on GTPv2 interfaces
Feature Octet / Bit Feature Interface Description

5/1 PRN S11, S4 PGW Restart Notification.
If both the SGW and the MME/S4-SGSN support
this feature, the SGW shall send PGW Restart
Notification message to the MME/S4-SGSN when
the SGW detects that the peer PGW has restarted,
and the SGW may send PGW Restart Notification
message when the SGW detects that the peer PGW
has failed and not restarted, as specified in
subclause 7.9.5.
5/2 MABR S11 Modify Access Bearers Request.
If both the SGW and the MME support this feature,
the MME may modify the S1-U bearers of all the
PDN connections of the UE by sending a Modify
Access Bearers Request message as specified in
subclause 7.2.24.
5/3 NTSR S11/S4 Network Triggered Service Restoration procedure.
If both the SGW and the MME/S4-SGSN support
this feature (see 3GPP TS 23.007 [17]), the SGW
shall send a Downlink Data Notification message
including the IMSI to the MME/S4-SGSN on the
TEID 0 as part of a network triggered service
restoration procedure.
Feature Octet / Bit: The octet and bit number within the Supported-Features IE, e.g. "5 / 1".
Feature: A short name that can be used to refer to the octet / bit and to the feature.
Interface: A list of applicable interfaces to the feature.
Description: A clear textual description of the feature.
No features have been defined on the following GTPv2 interfaces in this version of the specification: S2a, S2b, S5, S8,
S10, S3, S16, Sv, S101, S121, Sm, Sn.
8.84 MBMS Time to Data Transfer

The MBMS Time to Data Transfer indicates the minimum time occurring between the transmission of the MBMS
SESSION START REQUEST message and the actual start of the data transfer. It is coded as shown in figure 8.84-1.
Octet 5 is coded as the value part of the Time to MBMS Data Transfer IE defined in 3GPP TS 48.018 [34] (not
including the IEI and length indicator octets specified in 3GPP TS 48.018 [34]).
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 MBMS Time to Data Transfer value part
Figure 8.84-1: MBMS Time to Data Transfer
8.85 Throttling
Throttling is coded as depicted in Figure 8.85-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Throttling Delay Unit Throttling Delay Value
6 Throttling Factor
Figure 8.85-1: Throttling
Table 8.85.1: Throttling information element
Throttling Delay (octet 5)
Bits 5 to 1 represent the binary coded timer value.
Bits 6 to 8 defines the timer unit for the timer as follows:

Bits
876
0 0 0 value is incremented in multiples of 2 seconds
0 0 1 value is incremented in multiples of 1 minute
0 1 0 value is incremented in multiples of 10 minutes
0 1 1 value is incremented in multiples of 1 hour
1 0 0 value is incremented in multiples of 10 hours
1 1 1 value indicates that the timer is deactivated.
Other values shall be interpreted as multiples of 1 minute.
Throttling Factor (octet 6)
The Throttling Factor indicates a percentage and may take binary coded integer
values from and including 0 up to and including 100. Other values shall be
considered as 0.
8.86 Allocation/Retention Priority (ARP)

Allocation/Retention Priority (ARP) is coded as depicted in Figure 8.86-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare PCI PL Spare PVI
Figure 8.86-1: Allocation/Retention Priority (ARP)
The meaning and value range of the parameters within the ARP are defined in 3GPP TS 29.212 [29]. The bits within the
octet 5 are:
- Bit 1 – PVI (Pre-emption Vulnerability): See 3GPP TS 29.212[29], clause 5.3.47 Pre-emption-Vulnerability
AVP.
- Bit 2 – spare
- Bits 3 to 6 – PL (Priority Level): See 3GPP TS 29.212[29], clause 5.3.45 Priority-Level AVP. PL encodes each
priority level defined for the Priority-Level AVP as the binary value of the priority level.
- Bit 7 – PCI (Pre-emption Capability): See 3GPP TS 29.212[29], clause 5.3.46 Pre-emption-Capability AVP.
- Bit 8 – spare.
ETSI
8.87 EPC Timer

The purpose of the EPC Timer information element is to specify EPC specific timer values.
The EPC Timer information element is coded as shown in figure 8.87-1 and table 8.87.1
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Timer unit Timer value
Figure 8.87-1: EPC Timer
Table 8.87.1: EPC Timer information element
Timer value
Bits 5 to 1 represent the binary coded timer value.
Timer unit
Bits 6 to 8 defines the timer value unit for the EPC timer as follows:
Bits
876
0 0 0 value is incremented in multiples of 2 seconds
0 0 1 value is incremented in multiples of 1 minute
0 1 0 value is incremented in multiples of 10 minutes
0 1 1 value is incremented in multiples of 1 hour
1 0 0 value is incremented in multiples of 10 hours
1 1 1 value indicates that the timer is infinite
Other values shall be interpreted as multiples of 1 minute in this version of the

protocol.
Timer unit and Timer value both set to all "zeros" shall be interpreted as an
indication that the timer is stopped.
8.88 Signalling Priority Indication

The Signalling Priority Indication information element contains signalling priority indications received from the UE for
a specific PDN connection.
The Signalling Priority Indication information element is coded as shown in figure 8.88-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare LAPI
Figure 8.88-1: Signalling Priority Indication
ETSI
- Bit 1 – LAPI (Low Access Priority Indication): This bit defines if the UE indicated low access priority when
establishing the PDN connection. It shall be encoded as the Low Priority parameter of the Device Properties IE
in 3GPP TS 24.008 [5]. The receiver shall assume the value "0" if the Signalling Priority Indication IE is
applicable for a message but not included in that message by the sender. The low access priority indication may
be included in charging records.
8.89 Temporary Mobile Group Identity (TMGI)

The TMGI contains the Temporary Mobile Group Identity allocated to the MBMS Bearer Service. The BM-SC always
includes the MCC and MNC when allocating the TMGI, see 3GPP TS 29.061 [38].
It is coded as specified in Figure 8.89-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5-10 TMGI
Figure 8.89-1: TMGI
Octets 5 to 10 shall be encoded as octets 3 to octet 8 in the figure 10.5.154 of 3GPP TS 24.008 [5].
8.90 Additional MM context for SRVCC

The additional MM Context for SRVCC information element contains mobile station classmarks, supported codec list
that are necessary for the MME/S4-SGSN to perform SRVCC as defined in 3GPP TS 23.216 [43]. The coding of
Mobile Station Classmarks and Supported Codec List fields include the IE value part as it is specified in 3GPP TS
24.008 [5].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Length of the Mobile Station Classmark 2
6 to a Mobile Station Classmark 2
b Length of the Mobile Station Classmark 3
(b+1) to c Mobile Station Classmark 3
d Length of the Supported Codec List
(d+1) to e Supported Codec List
(e+1) to These octet(s) is/are present only if explicitly specified
(n+4)
Figure 8.90-1: Additional MM context for SRVCC
For each of the Mobile Station Classmark 2, Mobile Station Classmark 3 and Supported Codec List parameters, if they
are not available, then the associated length field shall be set to zero, and the particular parameter field shall not be
present.
8.91 Additional flags for SRVCC

Additional flags for SRVCC is coded as depicted in Figure 8.91-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare VF ICS
Figure 8.91-1: Additional flags for SRVCC
- Bit 1 – ICS (IMS Centralized Service): This flag indicates that UE supports ICS specific service as specified in
3GPP TS 23.292 [47].
- Bit 2 – VF (vSRVCC Flag): This flag indicates that the user is subscribed to the vSRVCC.
8.92 Void
8.93 MDT Configuration

MDT Configuration is coded as depicted in Figure 8.93-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Job Type
6 to 9 List of Measurements
10 Reporting Trigger
11 Report Interval
12 Report Amount
13 Event Threshold for RSRP
14 Event Threshold for RSRQ
15 Length of Area Scope
p to q Area Scope
s Spare PLI PMI MPI CRR
MI
u Collection period for RRM measurements LTE
v Measurement Period LTE
w Positioning Method
x Number of MDT PLMNs
y to z MDT PLMN List
r to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.93-1: MDT Configuration
Parameters in octets 5 to 14, p to q, u, v, w and y to z shall be encoded as specified in 3GPP TS 32.422 [18]. If Length
of Area Scope equals zero, then Area Scope octets p to q shall not be present.
If CRRMI (Collection period for RRM measurements LTE Indicator), bit 1 of octet 's', is set to "1", then the Collection
period for RRM measurements LTE parameter field shall be present, otherwise octet 'u' shall not be present.
If MPI (Measurement period LTE Indicator), bit 2 of octet 's', is set to "1", then the Measurement period LTE parameter
field shall be present, otherwise octet 'v' shall not be present.
If PMI (Positioning Method Indicator), bit 3 of octet 's', is set to "1", then the Positioning Method parameter field shall
be present, otherwise octet 'w' shall not be present.
If PLI (PLMN List Indicator), bit 4 of octet 's', is set to "1", then the Number of MDT PLMNs and MDT PLMN List
parameters shall be present, otherwise octet 'x' and octets 'y to z' shall not be present.
ETSI
The value of the Number of MDT PLMNs represents the number of 3-octet PLMNs contained within the MDT PLMN
List parameter and shall be a number from 1 to 16. Each PLMN ID in the list shall be encoded as defined for octets 5 to
7 in subclause 8.18.
8.94 Additional Protocol Configuration Options (APCO)

The Additional Protocol Configuration Options (APCO) information element is used to exchange additional protocol
configuration options between the TWAN/ePDG and the PGW.
The Additional Protocol Configuration Options information element is specified in 3GPP TS 29.275 [26] and its GTPv2
coding is shown in figure 8.94-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to m Additional Protocol Configuration Options (APCO)
(m+1) to These octet(s) is/are present only if explicitly specified
(n+4)
Figure 8.94-1: Additional Protocol Configuration Options
Octets (5 to m) of the Additional Protocol Configuration Options IE are encoded as specified in 3GPP TS 29.275 [26].
8.95 Absolute Time of MBMS Data Transfer

The Absolute Time of MBMS Data Transfer indicates the absolute time of the actual start, update or stop of the MBMS
data transfer to ensure a synchronized session control and facilitate a graceful reallocation of resources for the MBSFN
(MBMS Single Frequency Network) when needed for E-UTRAN access.
It is coded as shown in figure 8.95-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 12 Absolute Time of MBMS Data Transfer value part
Figure 8.95-1: Absolute Time of MBMS Data Transfer
Octets 5 to 12 are coded as the time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time
without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the 32
most significant bits and binary encoding of the fraction part in the 32 least significant bits. The fraction part is
expressed with a granularity of 1 /2**32 second.
8.96 H(e)NB Information Reporting

H(e)NB number Information Reporting is coded as depicted in Figure 8.96-1.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 165
2 to 3 Length = n
4 Spare Instance
5 Spare FTI
Figure 8.96-1: H(e)NB Information Reporting
ETSI
• Bit 1 – FTI: When set to "1", shall indicate to start reporting H(e)NB local IP address and UDP port number
information change when the UE moves from (e)NB to H(e)NB, from H(e)NB to another H(e)NB with a fixed
network backhaul change, or from H(e)NB to (e)NB.
The bit 1 shall be set to 0 to stop reporting H(e)NB local IP address and UDP port number information change.
8.97 IPv4 Configuration Parameters (IP4CP)

The IPv4 Configuration Parameters (IP4CP) is coded as depicted in Figure 8.97-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Subnet Prefix Length
6 to 9 IPv4 Default Router Address
Figure 8. 97-1: IPv4 Configuration Parameters (IP4CP)
8.98 Change to Report Flags

Change to Report Flags IE is coded as depicted in Figure 8.98-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare TZCR SNCR
Figure 8.98-1: Change to Report Flags
For each message the applicable flags of the Change to Report Flags IE shall be clearly specified in the individual
message sub clause. The remaining flags of the Change to Report Flags IE not so indicated shall be discarded by the
receiver.
The receiver shall consider the value of the applicable flags as "0", if the Change to Report Flags IE is applicable for the
message but not included in the message by the sender.
- Bit 2 – TZCR (Time Zone Change to Report): When set to 1, this bit indicates that a UE Time Zone change still
needs to be reported to the SGW/PGW.
- Bit 1 – SNCR (Serving Network Change to Report): When set to 1, this bit indicates that a Serving Network
change still need to be reported to the SGW/PGW.
8.99 Action Indication

Action Indication is coded as depicted in Figure 8.99-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare Indication
Figure 8.99-1: Action Indication
Table 8.99-1: Indication
Indication Values (Decimal)

No Action 0
Deactivation Indication 1
Paging Indication 2
Paging Stop Indication 3
<spare> 4 to7
If "deactivation indication" is set, it indicates that the receiving entity shall deactivate ISR and remove the UE resource
locally as specified in 3GPP TS 23.007 [17] subclause 27.3.1.2.
If "paging indication" is set, it indicates that the receiving entity shall page the IDLE state UE as specified in 3GPP TS
23.007 [17] subclause 27.3.2.2.
If "paging stop indication" is set, it indicates that the receiving entity shall stop paging the UE as specified in 3GPP TS
23.380 [61] subclause 5.4.2.1 and subclause 5.4.3.2.
8.100 TWAN Identifier

The TWAN Identifier is used for reporting UE location in a Trusted WLAN Access Network (TWAN). See 3GPP TS
23.402 [45].
TWAN Identifier shall be coded as depicted in Figure 8.100-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare LAII OPN PLM CIVAI BSSIDI
AI NI
6 SSID Length
7 to k SSID
(k+1) to BSSID
(k+6)
q Civic Address Length
(q+1) to Civic Address Information
(q+r)
s to (s+3) TWAN PLMN-ID
t TWAN Operator Name Length
(t+1) to (t+u) TWAN Operator Name
v Relay Identity Type
(v+1) Relay Identity Length
(v+2) to Relay Identity
(v+w)
X Circuit-ID Length
(x+1) to Circuit-ID
(x+y)
p to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.100-1: TWAN Identifier
The BSSID and SSID shall be encoded as described in IEEE Std 802.11-2012 [52].
ETSI
The TWAN identifier shall contain the SSID and, unless otherwise determined by the TWAN operator"s policies, it
shall contain at least the BSSID, the civic address of the access point to which the UE is attached or the Circuit-ID with
the identity of the relay which has allocated it. It may also contain the identifier of the TWAN operator, i.e. either the
TWAN PLMN-ID if the TWAN is operated by a mobile operator or the TWAN Operator Name otherwise.
The SSID Length in octet '6' indicates the length of the SSID field. The SSID is an Octet String which shall have a
maximum length of 32 octets (see IEEE Std 802.11-2012 [52]).
The BSSIDI flag in octet 5 indicates whether the BSSID in octets 'k+1' to 'k+6' shall be present. If BSSIDI is set to '1',
then the BSSID shall be present. If BSSIDI is set to '0', then the BSSID shall not be present. The BSSID is an Octet
String which shall be 6 octets long (see IEEE Std 802.11-2012 [52]).
The CIVAI flag in octet 5 indicates whether the Civic Address Length and Civic Address Information in octets 'q' and
'q+1' to 'q+r' shall be present. The Civic Address Length and Information shall be present if and only if the CIVAI flag
is set to 1. When present, the Civic Address Information shall contain the civic address of the Access Point to which the
UE is attached and it shall be encoded as defined in subclause 3.1 of IETF RFC 4776 [59] excluding the first 3 octets.
The PLMNI flag in octet 5 indicates whether the TWAN PLMN-ID in octets 's' to 's+3' shall be present. The TWAN
PLMN-ID shall be present if and only if the PLMNI flag is set to 1. The TWAN PLMN-ID shall be encoded as octets 5
to 7 of the Serving Network IE in subclause 8.18. When present, the TWAN PLMN-ID shall indicate the PLMN-ID of
the TWAN operator.
NOTE: the PLMN ID contained in the TWAN PLMN-ID can differ from the PLMN ID in the Serving Network
IE.
The OPNAI flag in octet 5 indicates whether the TWAN Operator Name Length and TWAN Operator Name in octets 't'
and 't+1' to 't+u' shall be present. The TWAN Operator Name Length and TWAN Operator Name shall be present if and
only if the OPNAI flag is set to 1. The TWAN Operator Name shall be encoded as specified in subclause 19. 8 of 3GPP
TS 23.003 [2]. When present, the TWAN Operator Name shall indicate the identifier of the TWAN operator.
The LAII flag in octet 5 indicates whether the Logical Access ID information is present in the TWAN Identifier IE. The
Logical Access ID is encoded by the Relay Identity information in octets 'v' to 'v+w' and the Circuit-ID information in
octets 'x' to 'x+y'. The Relay Identity information and the Circuit-ID information shall be present if the LAII flag is set
to '1'. The Relay Identity Type indicates the type of identity as described in Table 8.100-1. The Relay Identity Length
indicates the length of the Identity. In case the Relay Identity Type indicates an IP address, the length indicates if it is
IPv4 or IPv6 address of the Relay. The length is 4 octets for IPv4 and 16 octets for IPv6. If the Relay Identity type is set
to 1 (i.e. an FQDN), it is encoded as described in section 3.1 of IETF RFC 1035 [31] but excluding the trailing zero
byte. The Circuit-ID length indicates the length of the Circuit-ID. The Circuit-ID is as defined in IETF RFC 3046 [60],
it is encoded as an Octetstring and provided by the Relay.
Table 8.100-1: Relay Identity Type
Relay Identity Type Values (Decimal)

IPv4 or IPv6 Address 0
FQDN 1
8.101 ULI Timestamp

The ULI Timestamp IE is coded as shown in Figure 8.101-1. It indicates the UTC time when the user location
information was acquired. Octets 5 to 8 are encoded in the same format as the first four octets of the 64-bit timestamp
format as defined in section 6 of IETF RFC 5905 [53].
NOTE: The encoding is defined as the time in seconds relative to 00:00:00 on 1 January 1900.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5-8 ULI Timestamp value
Figure 8.101-1: ULI Timestamp
8.102 MBMS Flags

MBMS Flags is coded as depicted in Figure 8.102-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare LMRI MSRI
Figure 8.102-1: MBMS Flags
- Bit 1 – MSRI (MBMS Session Re-establishment Indication): if set to 1, this flag indicates that the MBMS
Session Start Request message is used to re-establish an MBMS session (see 3GPP TS 23.007 [13])
- Bit 2 – LMRI (Local MBMS Bearer Context Release Indication): if set to 1, this flag indicates that the MBMS
Session Stop Request message is used to release the MBMS Bearer Context locally in the MME/SGSN (see
3GPP TS 23.007 [13]);
8.103 RAN/NAS Cause

RAN/NAS Cause is coded as depicted in Figure 8.103-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Protocol Type Cause Type
6 to m Cause Value
(n+4)
Figure 8.103-1: RAN/NAS Cause
The Protocol Type field shall be encoded as per Table 8.103 -0:
Table 8.103-0: Protocol Type values
Protocol Type Values (Decimal)

S1AP Cause 1
EMM Cause 2
ESM Cause 3
Diameter Cause 4
IKEv2 Cause 5
<spare> 6-15
ETSI
All spare bits shall be set to zeros by the sender and ignored by the receiver.
The Cause Value field shall be coded as follows:
- For S1-AP Cause, the Cause Value field shall contain a non-transparent copy of the cause value of the
corresponding IE (see subclause 8.2.2), "Cause", as defined in clause 9.2.1.3 in 3GPP TS 36.413 [10].
The Cause Type field shall contain the RAN Cause subcategory as specified in 3GPP TS 36.413 [10] and it shall
be encoded as in Table 8.103-1. The value of the Cause Value field (and the associated RAN cause subcategory)
is transferred over the S1-AP interface and encoded into one octet as binary integer.
Table 8.103-1: Cause Type values and their meanings
Cause Type Values (Decimal)

Radio Network Layer 0
Transport Layer 1
NAS 2
Protocol 3
Miscellaneous 4
<spare> 5 to15
- For EMM and ESM Causes, the Cause Value field shall contain the cause value as specified respectively for the
"EMM Cause" IE and "ESM Cause" IE in subclauses 9.9.3.9 and 9.9.4.4 of 3GPP TS 24.301 [23], or for the
"Cause" IE in subclause 8.11 of 3GPP TS 24.244 [66].
The value of the Cause Value field (which has a range of 0..255) shall be transferred encoded into one octet as
binary integer.
The Cause Type field shall be ignored by the receiver.
- For Diameter Cause, the Cause Value field shall contain the cause value as specified for the Diameter
Termination-Cause AVP in IETF RFC 3588 [39]. The Cause Value field shall be encoded into 2 octets as binary
integer of the Termination-Cause AVP value.
The currently assigned values for the Termination-Cause AVP can be found in the IANA registry for
Termination-Cause AVP Values, IANA, "Termination-Cause AVP Values (code 295)",
http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml#aaa-parameters-16.
- For IKEv2 Cause, the Cause Value field shall contain the cause value as specified for the Internet Key Exchange
Version 2 (IKEv2) Parameters, Notify message error type, in IETF RFC 7296 [67]. The Cause Value field shall
be encoded into 2 octets as binary integer of the IKEv2 notify message error type value.
The currently assigned values for the IKEv2 notify message error type can be found in the IANA registry for
"Internet Key Exchange Version 2 (IKEv2) Parameters",
http://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#ikev2-parameters-14
8.104 CN Operator Selection Entity

CN Operator Selection Entity is coded as depicted in Figure 8.104-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare Selection
Entity
Figure 8.104-1: CN Operator Selection Entity
ETSI
Table 8.104-1: Selection Entity values

Selection mode value Value (Decimal)
The Serving Network has been selected by the UE 0
The Serving Network has been selected by the network 1
For future use. Shall not be sent. If received, shall be interpreted as the value "1". 2, 3
8.105 Trusted WLAN Mode Indication

The purpose of the Trusted WLAN Mode Indication information element is to convey the selected trusted WLAN
Mode.
The content and encoding of the Trusted WLAN Mode Indication is depicted on Figure 8.105-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Spare MCM SCM
Figure 8.105-1: Trusted WLAN Mode Indication
- Bit 2 – MCM (Multiple-connection mode Indication): if this bit is set to 1, it indicates that the Multiple-
connection mode is used.
- Bit 1 – SCM (Single-connection mode Indication): if this bit is set to 1, it indicates that the Single-connection
mode is used.
8.106 Node Number

Node Number shall be coded as depicted in Figure 8.106-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Length of Node Number
6 to p Node Number
(p+1) to These octet(s) is/are present only if explicitly specified
(n+4)
Figure 8.106-1: Node Number
The Node number shall carry an ISDN number. If the Node Number carries the SGSN Number, then the SGSN number
shall be coded according to the contents of ISDN-AddressString data type defined in 3GPP TS 29.002 [41]. The SGSN
Number shall be in international format and the "nature of address indicator" shall indicate "international number". The
SGSN Number is defined in 3GPP TS 23.003 [2]. The Length of Node Number shall not be zero.
8.107 Node Identifier

Node Identifier shall be coded as depicted in Figure 8.107-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Length of Node Name
6 to p Node Name
(p+1) Length of Node Realm
(p+2) to q Node Realm
(q+1) to These octet(s) is/are present only if explicitly specified
(n+4)
Figure 8.107-1: Node Identifier
The Node Identifier shall contain the Diameter Identity of the node.
If the Node Identifier contains a SGSN Identifier then:
- the Node Name shall be coded as the Diameter identity of the SGSN as defined in clause 6.4.13 of 3GPP TS
29.173 [57] and;
- the Node Realm shall be coded as the Diameter realm identity of the SGSN and as defined in clause 6.4.14 of
3GPP TS 29.173 [57] and;
- Both the Node Name and the Node Realm shall be present and neither the Length of Node Name nor the Length
of Node Realm shall be zero.
If the Node Identifier contains a MME Identifier then:
- the Node Name shall be coded as the Diameter identity of the MME as defined in clause 6.4.4 of 3GPP TS
29.173 [57] and;
- the Node Realm shall be coded as the Diameter realm identity of the MME as defined in clause 6.4.12 of 3GPP
TS 29.173 [57] and;
- Both the Node Name and the Node Realm shall be present and neither the Length of Node Name nor the Length
of Node Realm shall be zero.
8.108 Presence Reporting Area Action

Presence Reporting Area Action is coded as depicted in Figure 8.108-1.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 177
2 to 3 Length = n
4 Spare Instance
5 Spare Action
6 to 8 Presence Reporting Area Identifier
9 Number of TAI Number of RAI
10 Spare Number of Macro eNodeB
11 Spare Number of Home eNodeB
12 Spare Number of ECGI
13 Spare Number of SAI
14 Spare Number of CGI
15 to k TAIs [1..15]
(k+1) to m Macro eNB IDs [1..63]
(m+1) to p Home eNB IDs [1..63]
(p+1) to q ECGIs [1..63]
(q+1) to r RAIs [1..15]
(r+1) to s SAIs [1..63]
(s+1) to t CGIs [1..63]
u to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.108-1: Presence Reporting Area Action
Table 8.108-1: Action values

Action Value (Decimal)
Start Reporting changes of UE 1
presence in the PRA
Stop Reporting changes of UE 2
presence in the PRA
<spare> 0, 3-7
The Action value 1 (Start Reporting change) shall be used to request to start reporting changes of UE presence in the
Presence Reporting Area identified by the Presence Reporting Area Identifier and, if present, the Presence Reporting
Area elements composing the Presence Reporting Area.
The Action value 2 (Stop Reporting change) shall be used to request to stop reporting changes or UE presence in a
The Presence Reporting Area Identifier shall be present if the Action value requests to start or to stop reporting changes
of UE presence in a Presence Reporting Area. If so, the Presence Reporting Area Identifier shall contain an identifier of
the Presence Reporting Area and be encoded using full hexadecimal representation. The Presence Reporting Area
Identifier is defined in subclause 19.10 of 3GPP TS 23.003 [2].
Octets 9 to 14 shall be present if and only if the Action value requests to start reporting change of UE presence in a
Presence Reporting Area and the Presence Reporting Area is not pre-configured in the MME/SGSN. If so, these octets
shall indicate the number of TAI (15 at most), Macro eNodeB ID (63 at most), Home eNodeB ID (63 at most), ECGI
(63 at most), RAI (15 at most), SAI (63 at most) and CGI (63 at most) which compose the PRA.
TAIs in octets 15 to 'k', if any, shall be encoded as per the TAI field in subclause 8.21.4. Octets 15 to 'k' shall be absent
if the field 'Number of TAI' is set to the value '0'.
Macro eNB IDs in octets 'k+1' to 'm', if any, shall be encoded as per octets 6 to 11 of the Target ID for type Macro
eNodeB in figure 8.51-2. Octets 'k+1' to 'm' shall be absent if the field 'Number of Macro eNodeB' is set to the value '0'.
Home eNB IDs in octets 'm+1' to 'p', if any, shall be encoded as per octets 6 to 12 of the Target ID for type Home
eNodeB in figure 8.51-3. Octets 'm+1' to 'p' shall be absent if the field 'Number of Home eNodeB' is set to the value '0'.
ECGIs in octets 'p+1' to 'q', if any, shall be encoded as per the ECGI field in subclause 8.21.5. Octets 'p+1' to 'q' shall be
absent if the field 'Number of ECGI' is set to the value '0'.
RAIs in octets 'q+1' to 'r', if any, shall be encoded as per the RAI field in subclause 8.21.3. Octets 'q+1' to 'r' shall be
absent if the field 'Number of RAI' is set to the value '0'.
ETSI
SAIs in octets 'r+1' to 's', if any, shall be encoded as per the SAI field in subclause 8.21.2. Octets 'r+1' to 's' shall be
absent if the field 'Number of SAI' is set to the value '0'.
CGIs in octets 's+1' to 't', if any, shall be encoded as per the CGI field in subclause 8.21.1. Octets 's+1' to 't' shall be
absent if the field 'Number of CGI' is set to the value '0'.
8.109 Presence Reporting Area Information

Presence Reporting Area Information is coded as depicted in Figure 8.109-1.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 178
2 to 3 Length = n
4 Spare Instance
5 to 7 Presence Reporting Area Identifier
8 Spare OPRA IPRA
Figure 8.109-1: Presence Reporting Area Information
The Presence Reporting Area Identifier in octets 5 to 7 shall be present and shall contain the identifier of the Presence
Reporting Area the UE is entering or leaving. It shall be encoded using full hexadecimal representation. The Presence
Reporting Area Identifier is defined in subclause 19.10 of 3GPP TS 23.003 [2].
The Inside PRA flag (IPRA) in octet 8 shall be set to 1 if the UE is inside or enters the Presence Reporting Area
identified by the PRA Identifier.
The Outside PRA flag (OPRA) in octet 8 shall be set to 1 if the UE is outside or leaves the Presence Reporting Area
identified by the PRA Identifier.
Either the IPRA or the OPRA flag shall be set to 1, not both.
8.110 TWAN Identifier Timestamp

The TWAN Identifier Timestamp IE is coded as shown in Figure 8.110-1. It indicates the UTC time when the TWAN
Identifier information was acquired. Octets 5 to 8 shall be encoded in the same format as the first four octets of the 64-
bit timestamp format as defined in section 6 of IETF RFC 5905 [53].
NOTE: The encoding is defined as the time in seconds relative to 00:00:00 on 1 January 1900.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5-8 TWAN Identifier Timestamp value
Figure 8.110-1: TWAN Identifier Timestamp
8.111 Overload Control Information

Overload Control Information is a grouped IE containing a number of other IEs. Which of those IEs are mandatory,
optional or conditional and the conditions that apply are GTP message specific, and described in the corresponding
subclause under clause 7.
ETSI
Overload Control Information may be repeated within a message with exactly the same Type and Instance values to
represent a list of Overload Control Information.
Overload Control Information is coded as depicted in Table 8.111-1.
Table 8.111-1: Overload Control Information Grouped Type

8.112 Load Control Information

Load Control Information is a grouped IE containing a number of other IEs. Which of those IEs are mandatory, optional
or conditional and the conditions that apply are GTP message specific, and described in the corresponding subclause
under clause 7.
Load Control Information may be repeated within a message with exactly the same Type and Instance values to
represent a list of Load Control Information.
Load Control Information is coded as depicted in Table 8.112-1.
Table 8.112-1: Load Control Information Grouped Type

8.113 Metric
The Metric IE is coded as shown in Figure 8.113-1. It indicates a percentage and may take binary coded integer values
from and including 0 up to and including 100. Other values shall be considered as 0.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 1
4 Spare Instance
5 Metric
Figure 8.113-1: Metric
8.114 Sequence Number

The Sequence Number IE is coded as shown in Figure 8.114-1 and it contains Unsigned32 binary integer value.
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = 4
4 Spare Instance
5 to 8 Sequence Number
Figure 8.114-1: Sequence Number
8.115 APN and Relative Capacity

The APN and Relative Capacity IE is coded as shown in Figure 8.115-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 Relative Capacity
6 APN Length
7 to m Access Point Name (APN)
(n+4)
Figure 8.115-1: APN and Relative Capacity
The Relative Capacity represents the resources configured for the given APN as compared to the total resources of the
target PGW, in percentage. It shall take binary coded integer values from 1 up to 100. Other values shall be considered
as 0.
The APN Length in octet '6' indicates the length of the APN field.
The APN field, from octet 7 to 'm' shall be encoded as octet 5 to '(n+4)' defined in clause 8.6.
8.116 WLAN Offloadability Indication

WLAN Offloadability Indication IE is coded as depicted in Figure 8.116-1.
Bits
Octets 8 7 6 5 5 3 2 1
1 Type = yyy (decimal)
2 to 3 Length = n
4 Spare Instance
5 Spare EUTR UTRA
AN N
indicat indicat
ion ion
Figure 8.116-1: WLAN Offloadability Indication
Octet 5 indicates if WLAN Offload has been authorized for the UE:
- Bit 8 to 3 Spare, for future use and set to zero.
- Bit 2 – reflects the information available at the UE regarding E-UTRAN Offloadability. When set to '1', this
indicates that the UE has been authorized to perform WLAN offload from E-UTRAN. When set to '0', this
indicates that the UE has not been authorized to perform WLAN offload from E-UTRAN.
ETSI
- Bit 1 – reflects the information available at the UE regarding UTRAN Offloadability. When set to '1', this
indicates that the UE has been authorized to perform WLAN offload from UTRAN. When set to '0', this
indicates that the UE has not been authorized to perform WLAN offload from UTRAN.
8.117 Paging and Service Information

The Paging and Service Information IE is used to carry per bearer paging and service information. It is coded as shown
in Figure 8.117-1.
Bits
Octets 8 7 6 5 4 3 2 1
1 Type 186 (decimal)
2 to 3 Length = n
4 Spare Instance
5 Spare (all bits set to 0) EPS Bearer ID (EBI)
6 Spare PPI
m Spare Paging Policy Indication value
p to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.117-1: Paging and Service Information
The EBI value, in octet 5, indicates the EPS Bearer ID for which the Paging and Service Information is provided. The
EBI field shall be encoded as the EBI field in the EPS Bearer ID (EBI) IE type (see subclause 8.8).
The PPI flag in octet 6 indicates whether the Paging Policy Indication value in octet 'm' shall be present. If PPI is set to
'1', then the Paging Policy Indication value shall be present. If PPI is set to '0', then octet 'm' shall not be present.
The Paging Policy Indication value, in octet 'm', shall be encoded as the DSCP in TOS (IPv4) or TC (IPv6) information
received in the IP payload of the GTP-U packet from the PGW (see IETF RFC 2474 [65]).
8.118 Integer Number

Integer Number is coded as depicted in Figure 8.118-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to n+4 Integer Number Value
Figure 8.118-1: Integer Number
The Integer Number value is encoded with the number of octets defined in the Length field, e.g. when n=2, the range of
the integer number value is from 0 to 65535.
The Integer Number value shall be encoded as further described below for the following information elements:
- Maximum Wait Time IE: the length shall be set to 2, i.e. the integer number value shall be encoded as a 16 bit
unsigned integer.
- DL Buffering Suggested Packet Count IE: the length shall be set to 1 or 2;
- UE Usage Type IE: the length shall be set to 1, i.e. the integer number value shall be encoded as a 8 bit unsigned
integer as specified in subclause 7.3.Y of 3GPP TS 29.272 [70].
8.119 Millisecond Time Stamp

The Millisecond Time Stamp IE is coded as shown in Figure 8.119-1. Octets 5 to 10 represent a 48 bit unsigned integer
in network order format and are encoded as the number of milliseconds since 00:00:00 January 1, 1900 00:00 UTC, i.e.
as the rounded value of 1000 x the value of the 64-bit timestamp (Seconds + (Fraction / (1<<32))) defined in section 6
of IETF RFC 5905 [53].
ETSI
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5-10 Millisecond Time Stamp value
Figure 8.119-1: Millisecond Time Stamp
8.120 Monitoring Event Information

The Monitoring Event Information contains the monitoring event parameters that are necessary to transfer over the
S3/S16/S10 interface.
The Monitoring Event Information is coded as depicted in Figure 8.120-1.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 8 SCEF Reference ID
9 SCEF ID Length
10 to k SCEF ID
(k+1) to Remaining Number of Reports
(k+2)
(k+3) to These octet(s) is/are present only if explicitly specified
(n+4)
Figure 8.120-1: Monitoring Event Information
The SCEF Reference ID, the SCEF ID shall be encoded as specified in subclause 8.4.4 and 8.4.5 of 3GPP TS 29.336
[69].
The SCEF ID Length indicates the length of the SCEF ID in octets.
The Remaining Number of Reports indicates the number of reports which are outstanding to be sent to the SCEF. It
shall be encoded as specified in subclause 8.4.8 of 3GPP TS 29.336 [69],
8.121 ECGI List

MBMS Cell List is an extendable IE that is coded as depicted in Figure 8.120-1. The ECGI identity types are defined in
3GPP TS 23.003 [2].
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to 6 Number of ECGI Fields = m
7 to (m*7+6) ECGI List of m ECGI Fields
(m*7+7) to (n+4) These octet(s) is/are present only if explicitly specified
Figure 8.121-1: ECGI List
The Number of ECGI Fields shall indicate the number of ECGI fields in the ECGI List.
In the present version of this specification, the Length n shall be set to m times 7 plus 2.
The ECGI List shall consist of m ECGI fields. Each ECGI field shall be encoded as specified in subclause 8.21.5 and
thus is 7 octets long.
ETSI
8.122 Remote UE Context

Remote UE Context is a grouped IE containing a number of other IEs. Which of those IEs are mandatory, optional or
conditional and the conditions that apply are GTP message specific, and described in the corresponding subclause under
clause 7.
Remote UE Context may be repeated within a message with exactly the same Type and Instance values to represent a
list of Remote UE Context.
Remote UE Context is coded as depicted in Table 8.122-1.
Table 8.122-1: Remote UE Context Grouped Type

8.123 Remote User ID

Remote User ID is transferred via GTP tunnels and is coded as depicted in Figure 8.123-1.
Editor's Note: It is FFS for the detail encoding.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to n+4 Remote User ID
Figure 8.123-1: Remote User ID
8.124 Remote UE IP Information

Remote UE IP Information is transferred via GTP tunnels and is coded as depicted in Figure 8.124-1.
Editor's Note: It is FFS for the detail encoding.
Bits
Octets 8 7 6 5 4 3 2 1
2 to 3 Length = n
4 Spare Instance
5 to n+4 Remote UE IP Information
Figure 8.124-1: Remote UE IP Information
9 Security
GTPv2-C communications shall be protected according to security mechanisms defined in 3GPP TS 33.401 [12].
ETSI
10 IP - The Networking Technology used by GTP
10.1 IP Version
GTPv2 entities shall support both versions of the Internet Protocol, version 4 (IPv4) as defined by IETF RFC 791 [6],
and version 6 (IPv6) as defined by IETF RFC 2460 [16].
10.2 IP Fragmentation
It is specified here how the fragmentation mechanism shall work with GTP-C.
Fragmentation should be avoided if possible. Examples of fragmentation drawbacks are:
- Fragmentation is inefficient, since the complete IP header is duplicated in each fragment.
- If one fragment is lost, the complete packet has to be discarded. The reason is that no selective retransmission of
fragments is possible.
Path MTU discovery should be used, especially if GTPv2-C message is encapsulated with IPv6 header. The application
should find out the path MTU, and thereby utilise more efficient fragmentation mechanisms.
11 Notification of supported features between peer

GTP-C entities
11.1 General
11.1.1 Introduction
New functionality, i.e. functionality beyond the Rel-9 standard, which can not be specified without backward
incompatible changes (e.g. requiring support of a new message or a specific receiver node's behaviour) should be
introduced as a feature, see subclause 11.1.2.
A GTP-C entity should verify that a backward incompatible feature is supported by its peer GTP entities before starting
to use it.
NOTE: GTPv2 does not support a Comprehension Required mechanism allowing a sender to force the receiver to
support comprehension of some specific IEs as a precondition to process a backward incompatible
message.
Features may be generic node capabilities supported homogeneously for all GTP tunnels, UEs and PDN connections.
Such features are referred in this specification as "Node Features". They are signalled with the granularity of a node on
all GTPv2 interfaces (i.e. S11, S4, S5, S8, S10, S3, S16, Sv, S101, S121, Sm, Sn, S2a, S2b). A GTP-C entity may
discover the features supported by a peer GTP-C entity with which it is in direct contact as specified in subclause
11.2.1.
11.1.2 Defining a feature

A feature is a function extending the base GTPv2 functionality that has a significant meaning to the operation of
GTPv2, i.e. a single new parameter without a substantial meaning to the functionality of the GTPv2 endpoints should
not be defined to be a new feature.
A functionality requiring the definition of a new GTPv2 message or extending the use of an existing message over a
new interface should be defined as a feature.
NOTE: Features are ultimately defined on a case-by-case basis on the merits of defining an extension as a feature.
ETSI
Features should be defined so that they are independent from each other. A GTP-C entity may support the same feature
over different interfaces, e.g. an SGW may support a feature over both S11 and S4 interface, however support of a
feature on a given interface shall not depend on the support of the same or another feature on another interface.
11.2 Dynamic discovery of supported features

11.2.1 General
A node supporting at least one feature defined in the Node Features IE shall support dynamic discovery of supported
features as specified in the following subclauses.
11.2.2 Features supported by direct peer GTP-C entities

A node shall signal to a direct peer node the list of features it supports by sending the Sending Node Features IE in the
Echo Request and Echo Response messages.
An exception to this is where the sending node does not support or use any features towards the peer node and is not
prepared to accept a message which is constructed by making use of any features.
The peer receiving the Sending Node Features IE shall store the list of features supported by the sending node per IP
address and only update this list based on the Sending Node Features IE in the Echo Request and Echo Response
messages, and it shall only use common supported features to initiate subsequent GTPv2 messages towards this IP
address.
12 GTP-C load & overload control mechanism
12.1 General
12.1.1 GTP-C overload problem
GTP-C entities can communicate with other GTP-C peers in direct contact (e.g. MME and SGW) or remote GTP-C
peers through intermediate GTP-C entities (e.g. MME and PGW via the SGW). In normal conditions, requests sent by a
GTP-C entity can be processed by the receiving GTP-C entity which can send back a message indicating the result of
the request (success/failure).
Overload situations in a GTP-C entity occur when the number of incoming requests exceeds the maximum request
throughput supported by the receiving GTP-C entity, e.g. when the internal available resources of the GTP-C entity,
such as processing power or memory, are not sufficient to serve the number of incoming requests. As a consequence of
the overload situation, the receiving GTP-C entity cannot successfully process the exceeding proportion of requests.
These requests can be either simply dropped or extremely delayed in the processing. At best, the GTP-C entity may
have enough internal resources to send back to the request initiator a message indicating that the requests cannot be
successfully processed. Whatever the behaviour of the overloaded GTP-C entities, the rate of successfully processed
requests and consequently the overall performances of the network decrease.
NOTE: GTP-C overload control does not target to address transport network congestion. It assumes a transport
network that is still capable to exchange signalling traffic.
Given the nature of GTP-C protocol in how it relies on retransmissions of unacknowledged requests (GTP-C is carried
over UDP transport), when a GTP-C entity experiences overload (or severe overload) the number of unacknowledged
GTP-C messages compounds exponentially and can lead to a node congestion or even collapse. An overload or failure
of a node can lead to an increase of the load on the other nodes in the network and, in the worst case, turn into a
complete network issue via a snowball effect.
The impact of GTP-C overload to services can be such as:
- loss of PDN connectivity (IMS, Internet …) and associated services;
ETSI
- loss of ability to setup and release radio and core network bearers necessary to support services e.g. GBR bearers
for VoLTE or dedicated bearers for Voice over WLAN;
- loss of ability to report to the PGW/PCRF user's information changes, e.g. location information for emergency
services and lawful intercept, changes in RAT or QoS;
- and billing errors and a loss of revenue.
12.1.2 Scenarios leading to overload

Reasons for these temporary overload cases can be many and various in an operational network, such as insufficient
internal resource capacity of a GTP-C entity faced with a sudden burst of requests, e.g. after network failure/restart
procedures affecting a large number of users, deficiency of a GTP-C entity component leading to a drastic reduction of
the overall performances of the GTP-C entity.
Examples of GTP-C signalling based scenarios which can cause GTP-C overload are:
- a traffic flood resulting from the failure of a network element, inducing a signalling spike, e.g. when the network
needs to re-establish the PDN connections affected by the failure of an EPC node;
- a traffic flood resulting from a large number of users performing TAU/RAU or from frequent transitions
between idle and connected mode;
- an exceptional event locally generating a traffic spike, e.g. a large amount of calls (and dedicated bearers) being
setup almost simultaneously upon a catastrophic event or an exceptional but predictable event (e.g. Christmas,
New year) via a 3GPP access or a WLAN access;
- Frequent RAT-reselection due to scattered non-3GPP (e.g. WiFi) coverage or massive mobility between 3GPP
and non-3GPP coverage may potentially cause frequent or massive intersystem change activities, i.e. UEs trying
to either create PDN connections over the new access or moving PDN connections between 3GPP and non-
3GPP coverage.
Besides, GTP-C load balancing based only on semi-static DNS weights can lead to a load imbalance and thus GTP-C
signalling scenarios, such as those mentioned above, may result in an overload of the SGWs or PGWs with the highest
load while there is still remaining capacity on other SGWs or PGWs.
12.1.3 Load & overload control concepts

Load control refers to "GTP-C signalling based Load Control" as defined in subclause 4.3.7.1a.1 of 3GPP TS 23.401 [3]
and subclause 5.3.6.1a of 3GPP TS 23.060 [35].
Overload control refers to "GTP-C signaling based Overload Control" as defined in subclause 4.3.7.1a.2 of 3GPP TS
23.401 [3] and subclause 5.3.6.1a of 3GPP TS 23.060 [35].
Load control and overload control are two distinct but complementary concepts:
- load control enables a GTP-C entity (e.g. an SGW/PGW) to send its load information to a GTP-C peer (e.g. an
MME/SGSN, ePDG, TWAN) to adaptively balance the session load across entities supporting the same function
(e.g. an SGW cluster) according to their effective load. The load information reflects the operating status of the
resources of the GTP-C entity.
- overload control enables a GTP-C entity becoming or being overloaded to gracefully reduce its incoming
signalling load by instructing its GTP-C peers to reduce sending traffic according to its available signalling
capacity to successfully process the traffic. A GTP-C entity is in overload when it operates over its signalling
capacity which results in diminished performance (including impacts to handling of incoming and outgoing
traffic).
Load control allows for better balancing of the session load, so as to attempt to prevent overload in the first place
(preventive action). Overload control aims at shedding the incoming traffic as close to the traffic source as possible
generally when an overload has occurred (reactive action), so to avoid spreading the problem inside the network and to
avoid using resources of intermediate nodes in the network for signalling that would anyhow be discarded by the
overloaded node.
Load control does not trigger overload mitigation actions even if the GTP-C entity reports a high load.
ETSI
Load control and overload control may be supported and activated independently in the network.
12.2 Load control solution

12.2.1 Principles of load control
The stage 2 requirements on GTP-C load control solution are defined in clause 4.3.7.1a.1 of 3GPP TS 23.401 [3] and
clause 5.3.6.1a of 3GPP TS 23.060 [35]. The high level principles are summarized below:
a) Load Control is an optional feature;
b) a GTP-C node may signal its Load Control Information to reflect the operating status of its resources, allowing
the receiving GTP-C peer node to use this information to augment the existing GW selection procedures;
c) the calculation of the Load Control Information is implementation dependent and its calculation and transfer
shall not add significant additional load to the node itself and to its corresponding peer nodes;
d) the Load Control Information may provide load information of a GTP-C node (e.g. a PGW) or, if the APN level
load control feature is supported, may provide the load information about specific APN(s);
e) the SGW may send its Load Control Information to the MME/S4-SGSN. The PGW may send its Load Control
Information to the MME/S4-SGSN via the SGW. For non-3GPP access based interfaces, the PGW may send its
Load Control Information to the ePDG and TWAN;
f) the Load Control Information shall be piggybacked in GTP-C request or response messages such that the
exchange of Load Control Information does not trigger extra signalling;
NOTE: The inclusion of Load Control Information in existing messages means that the frequency of transmission
of load control information increases as the session load increases, allowing for faster feedback and thus
better regulation of the load.
g) a node supporting Load Control sends Load Control Information to a peer GTP-C node based on local
configuration (see clause 12.2.6);
h) the format of the Load Control Information shall be specified with enough precision to guarantee a common
interpretation of this information allowing interoperability between nodes of different vendors;
i) for the inter-PLMN case, local configuration may restrict the exchange and use of Load Control Information
across PLMNs;
j) the GTP-C node may decide to send different values of Load Control Information on inter-network (roaming)
and on intra-network (non-roaming) interfaces based on local configuration, i.e. the values sent on intra-network
interfaces may differ from the values sent on inter-network interfaces. However, on intra-network interfaces, the
node should send the same values between the 3GPP and non-3GPP access based interfaces.
k) the Load Control Information received via GTP-C signalling shall be used in conjunction with the information
received from the DNS, during the node selection procedure. Refer to 3GPP TS 29.303 [32] for further details.
12.2.2 Applicability to 3GPP and non-3GPP access based interfaces

Load Control may be supported on the 3GPP & non-3GPP access based interfaces and nodes as summarized by the
Table 12.2.2-1.
ETSI
Table 12.2.2-1: Applicability of Load Control to GTP-C interfaces and nodes
Originator Consumer Applicable Interfaces

PGW MME S5/S8, S11
SGW relays Load Control Information from S5/S8 to S11 interface.
PGW S4-SGSN S5/S8, S4
SGW relays Load Control Information from S5/S8 to S4 interface.
SGW MME S11
SGW S4-SGSN S4
PGW ePDG S2b
PGW TWAN S2a
NOTE: Refer to Annex D.1 for information on the GTP-C interfaces for which Load Control is not supported.
12.2.3 Node level load control

Node level load control refers to advertising of the load information at node level – i.e. load information at node level
granularity – and selection of the target node based on this information. It helps to achieve an evenly load balanced
network by the use of the dynamic load information provided within the Load Control Information.
12.2.4 APN level load control
12.2.4.1 General
APN level load control refers to advertising of the load information at APN level granularity and selection of the target
node based on this information. It helps to achieve an evenly load balanced network at APN granularity by the use of
the dynamic load information provided within the Load Control Information with the APN scope. Only a PGW may
advertise APN level load information.
APN level load control is an optional feature that may be supported when the following pre-condition is applicable.
Pre-Condition:
In the given network, when the ratio of the configured APN resource to the overall capacity of the PGW is not
the same across all the PGWs in the network.
NOTE: In other cases, e.g. when all the resources of the PGW are available for all the APNs served by that PGW,
the node level load information is exactly the same as APN level load information, for each of its APNs,
and hence performing node load control is sufficient.
If APN load control is supported and activated at the PGW, the PGW should advertise the APN load information. If the
APN level load control feature is supported at the node performing the PGW selection, i.e. an MME, S4-SGSN, ePDG,
TWAN, the node shall utilize this information when selecting the PGW.
12.2.4.2 Justifications for APN load control support

Following are the justifications to support the APN level load control in the network when the pre-condition specified in
12.2.3.1 is applicable:
1) To achieve load balancing at the APN level granularity: The PGW may be configured to handle more than
one APN in the network. In such a case, the PGW may be additionally configured to allocate different resources
for each of the configured APNs, e.g. the PGW may be configured to handle "X" number of sessions for the
"consumer" APN and to handle "Y" number of session for the "corporate" APN. The ratio of this limit, i.e. "X"
and "Y", to the PGW's capacity may not be the same across all the PGWs in the network. In this case, the load
information with node level granularity is not sufficient and could result in a network where one PGW has more
sessions for the "consumer" APN while another PGW has more sessions for the "corporate" APN. Thus, an
evenly load balanced network at APN level load granularity cannot be realized.
2) To ensure effective overload control in the network: If the distribution of sessions at APN level is uneven,
then there is a higher risk of overload of some PGWs, as compared to other PGWs, e.g. the PGW handling more
sessions for "consumer" APN may have to handle more messages, (e.g. generated due to mobility events
ETSI
resulting from a change of ULI, RAT type, Serving GW, etc.) as compared to the PGW handling more sessions
for the "stationary-machine" APN. Hence, the PGW handling "consumer" APN sessions may be at higher risk of
overload, as compared to the other PGWs in the network, and hence, this situation may result in poor overload
control of the network.
3) To ensure an efficient node selection algorithm: Based on the node level load information, the source node,
(e.g. the MME) may end-up selecting the PGW for a new session for the given APN. However, the selected
PGW may reject the new session request, if it is running at 100% load capacity for the given APN, or the new
session request may be throttled by the source node based on the overload information of the APN for the given
PGW. Thus the new session request may be denied, (i.e. rejected by the selected PGW or throttled by the source
node based on PGW's APN level overload information) while the other PGW may have the capacity to handle
the same. Thus, the lack of APN level load information may result in inefficient node selection algorithm by the
source node.
12.2.4.3 Elements of APN load control

To allow for an effective APN load control, at least the following information (in addition to the other applicable
information for load control as defined in clause 12.2.5.1.2) is required to be advertised by the PGW, as part of the APN
level load information:
APN: The APN for which the PGW wants to advertise the load information.
APN-Load-Metric: It indicates the current resource utilization for a particular APN, as a percentage, compared to the
total resources reserved for that APN at the target PGW. Its computation is implementation dependent and it has same
characteristics as "Load-Metric", as described in clause 12.2.5.1.2.2, when applied at the APN level.
APN-relative-capacity: It indicates the total resources configured for a given APN, compared to the total resources of
the target PGW, as a percentage. It is a static parameter and does not change unless the resources configured for the
APN change. Using APN-relative-capacity and the DNS weight-factor of the given PGW, the source node can judge the
PGW's APN related resources as compared other PGWs in the network, i.e. the PGW's APN-weight-factor can be
calculated by multiplying the APN-relative-capacity and DNS-weight-factor of the PGW (PGW's-APN-weight-factor =
PGW's-APN-relative-capacity X DNS-weight-factor).
For the following example configuration:
PGW1-APN1-relative-capacity = 50%; PGW2-APN1- relative-capacity = 20%; PGW3-APN1- relative-capacity =

10%
PGW1-weight-factor = 20; PGW2-weight-factor = 20; PGW3-weight-factor = 60;
The APN level weight-factor for each of the PGWs can be calculated as below:
PGW1-APN1-weight-factor = 50% X 20 = 10.
Thus, based on the APN-weight-factor it can be concluded that the PGW1 has highest APN1 related resources reserved,
as compared to the other PGWs in the network. Hence the source node should use this information to favour PGW1
over other PGWs for APN1 related new session requests.
12.2.5 Load Control Information
12.2.5.1 Definition
12.2.5.1.1 General description

Within a message, one or multiple instances of the Load Control Information (LCI) IE may be included by the same
GTP-C entity.
When providing load control information in a message for the first time or subsequently, the GTP-C entity shall always
include the full set of load control information, i.e. all the node level and APN Level applicable instances of the Load
ETSI
Control Information, even if only a subset of the load control information has changed. All the instances of the LCI IE
provided by a given GTP-C entity in a message shall contain the same Load-Control-Sequence-Number. The Load
Control Sequence Number shall be incremented whenever the load control information is changed (see subclause
12.2.5.1.2.1).
The receiver shall overwrite any stored load control information of a peer with the newly received load control
information (via one or multiple instances) from the same peer node if the new load control information is more recent
than the old information as indicated by the Load Control Sequence Number, e.g. if the receiver has stored 'X' instances
of the load control information for a peer node, it overwrites those 'X' instances with the new set of 'Y' instances
received in a message from the same peer node, where X, Y are any integer number.
The receiver shall consider all the parameters received in the same instance of the LCI IE in conjunction while using
this information for node selection. When more than one instance of the LCI IE is received, the receiver shall consider
the parameters included in each instance independently, when using this information for node selection.
The parameters are further defined in subclauses 12.2.5.1.2 and 12.2.5.1.3.
Load control information may be extended with new parameters in future versions of the specification. Any new
parameter will have to be categorized as:
- Non-critical optional parameters: the support of these parameters is not critical for the receiver. The receiver
can successfully and correctly comprehend the load control information instance, containing one or more of
these parameters, by using the other parameters and ignoring the non-critical optional parameter.
- Critical optional parameters: the support of these parameters is critical for the receiver to correctly
comprehend the instance of the load control information containing one or more of these parameters.
The sender may include one or more non-critical optional parameters within any instance of the LCI IE without having
the knowledge of the receiver's capability to support the same. However, the sender shall only include one or more
critical optional parameter in any instance of the LCI IE towards a receiver if the corresponding receiver is known to
support those parameters. The sender may be aware of this either via signalling methods or by configuration; (this will
have to be defined when introducing any such new parameter in future).
Each instance of the LCI IE shall be associated to the node identity (FQDN or IP address of the GW node received from
the HSS or the DNS) of the serving SGW or PGW, i.e. the identity determined during the SGW or PGW selection.
NOTE: The Node type is derived based on the instance number of the LCI IE.
12.2.5.1.2 Parameters
12.2.5.1.2.1 Load Control Sequence Number
The Load Control Sequence number contains a value that indicates the sequence number associated with the LCI IE.
This sequence number shall be used to differentiate any two LCI IEs generated at two different instances by the same
GTP-C entity. The Load Control Sequence Number shall be supported (if load control is supported) and shall always be
present in the LCI IE.
The GTP-C entity generating this information shall increment the Load Control Sequence Number whenever
modifying some information in the Load Control Information IE. The Load Control Sequence Number shall not be
incremented otherwise. The node may use the time, represented in an unsigned integer format, of the generation of the
Load Control Information to populate the Load Control Sequence Number.
When multiple instances of the LCI IE are provided in a message by a given GTP-C node, each of them shall contain
the same Load Control Sequence Number value.
This parameter shall be used by the receiver of the Load Control Information IE to properly collate out-of-order load
control information, e.g. due to GTP-C retransmissions. This parameter shall also be used by the receiver of the LCI IE
to determine whether the newly received load control information has changed compared to load control information
previously received from the same node earlier.
NOTE: The GTP-C sequence number cannot be used for collating out-of-order load control information as e.g.
load control information may be sent in both GTP-C requests and responses, using independent GTP-C
sequence numbering.
ETSI
If the receiving entity has already received and stored load control information from the peer GTP-C entity, the
receiving entity shall update its load control information only if the Load Control Sequence Number received in the new
load control information is higher than the stored value of the Load Control Sequence Number associated with the peer
GTP-C entity. However due to roll-over of the Load Control Sequence Number or restart of the node, the Load Control
Sequence Number may be reset to an appropriate base value by the peer GTP-C entity, hence the receiving entity shall
be prepared to receive (and process) a Load Control Sequence Number parameter whose value is less than the previous
value.
12.2.5.1.2.2 Load Metric
The Load Metric parameter shall indicate the current load level of the originating node. The computation of the Load
Metric is left to implementation. The node may consider various aspects, such as: the used capacity of the node based
on activated bearers in relationship to maximum number of bearers the node can handle, the load that these active
bearers produce in the node (e.g. memory/CPU usage in relationship to the total memory/CPU available, etc.).
The Load Metric represents the current load level of the sending node as a percentage within the range of 0 to100,
where 0 means no or 0% load and 100 means maximum or 100% load reached (i.e. no further load is desirable).
The Load Metric shall be supported (if load control is supported). The Load Metric shall always be included in the Load
Control Information.
Considering the processing requirement of the receiver of the Load Control Information (e.g. handling of the new
information, tuning the node selection algorithm to take the new information into account), the sender should refrain
from advertising every small variation (e.g. with the granularity of 1 or 2), in the Load Metric which does not result in
useful improvement in node selection logic at the receiver. During the typical operating condition of the sender, a larger
variation in the Load Metric, e.g. 5 or more units, should be considered as reasonable enough for advertising the new
Load Control Information and thus justifying the processing requirement (to handle the new information) of the
receiver.
NOTE: The range of the Load Metric, i.e. 0 to 100, does not mandate the sender to collect its own load
information at every increment/decrement and hence to advertise the change of Load Metric with a
granularity of 1%. Based on various implementation specific criteria, such as: the architecture, session
and signalling capacity, the current load and so on, the sender is free to define its own logic and
periodicity with which its own load information is collected.
12.2.5.1.2.3 List-of-APN_and_Relative Capacity
The List-of-APN_and_Relative Capacity parameter contains a list of the tuple (APN, Relative Capacity) and this
indicates one or more APNs for which the Load Control Information is applicable. The "APN" contains the name of the
APN and the Relative Capacity indicates the resources configured for a given APN, compared to the total resources
configured at the target PGW, as a percentage.
When present in the LCI IE, the scope of the load information shall be the list of indicated APNs for the PGW that
sends the load control information. In that case, the "Load Metric" shall be interpreted as an "APN-Load-Metric" and
shall indicate the current resource utilization for the indicated APNs, as a percentage, as compared to the total resources
configured for the indicated APNs at the target PGW.
Its computation is implementation dependent and it has the same characteristics as "Load Metric". Only one instance of
the List-Of-APN_and_Relative Capacity IE may be included within one Load Control Information instance.
NOTE 1: The maximum number of tuples (APN, Relative Capacity) in the List-of-APN_and_Relative Capacity IE
is set to 10. More than 10 occurrences of (APN, Relative Capacity), within one single instance of the List-
of-APN_and_Relative Capacity IE is treated as protocol error by the receiver.
If the List-of-APN_and_Relative Capacity IE has not been included, the scope of the Load Control Information shall be
the entire PGW node (unless restricted by other parameters in the LCI IE).
This parameter may be supported (if load control is supported) and shall be supported when APN level load control is
supported.
The receiver shall handle this parameter, when it is received, if it supports APN level load control. The receiver shall
ignore a Load Control Information instance applicable for an APN, if it does not support APN level load control.
ETSI
NOTE 2: The PGW encodes the APN level load information and node level load information using different
instance numbers in the message, so that the receiver will ignore the APN level load information, if it
does not support the APN level load control feature.
The maximum number of APNs, for which the PGW may advertise the Load Control Information, shall be limited to
10, i.e. the maximum number of occurrences of the tuple (APN, Relative Capacity) within and across various instances
of the LCI IE shall be limited to 10, for a given PGW. Hence, if the PGW supports more than 10 APNs, it shall
advertise the load control information for at most 10 of the most important APNs. In future, if needed, this limit may be
increased to allow the PGW to advertise the load information for more APNs. In that case, the receiver not supporting
the higher limit shall handle the first 10 APNs and shall ignore the load information for the remaining APNs.
NOTE 3: The limit of the number of APN's takes into account various aspects such as: the processing and storage
requirements at the overloaded node and the receiver, the number of important APNs for which load
control advertisement will be necessary and interoperability between the nodes.
When including load control information for some APN(s), the PGW shall also provide node level load control
information by providing one instance of the Load Control Information without the List-of-APN_and_Relative Capacity
parameter.
A node selecting a PGW for a given APN shall apply the APN level load information, if available for that APN. If this
parameter is not received for a given APN but it has been received for other APN(s) from the same PGW, then for this
given APN, the node performing PGW selection shall calculate the load metric, as described in 3GPP TS 29.303 [32],
for the target PGW.
12.2.5.1.3 Handling of parameters

If the PLMN supports the Load Control feature (see subclause 12.2.6), the support, inclusion and handling of the
parameters, within Load Control Information, is summarized in table 12.2.5.1.3-1.
Table 12.2.5.1.3-1: Parameters of the Load Control Information
Parameter Support by the Support by the Inclusion by the Handling by the

sender receiver sender receiver
Load Control sequence Mandatory Mandatory Mandatory Mandatory
number (as defined in
clause 12.2.5.1.2.1)
Load Metric (as defined Mandatory Mandatory Mandatory Mandatory
in clause 12.2.5.1.2.2)
List-of- Optional Optional Optional Conditional
APN_and_Relative (NOTE 1) (NOTE 1) (NOTE 2) (NOTE 3)
Capacity (as defined in
clause 12.2.5.1.2.3)
NOTE 1: This is an optional parameter that shall be supported, if APN level load control is supported.
NOTE 2: The PGW shall send this parameter whilst providing APN level load control information, if the APN level load
control feature is supported and enabled.
NOTE 3: If this parameter is received, the receiver supporting the APN load control feature shall handle and process
APN load control information.
12.2.5.2 Frequency of inclusion

How often the sender includes the load control information is implementation specific. The sender shall ensure that
new/updated load control information is propagated to the target receivers within an acceptable delay, such that the
purpose of the information (i.e. effective load balancing) is achieved. The sender may include the LCI IE e.g. as
follows:
- the sender may include Load Control Information towards a peer only when the new/changed value has not
already been provided to that peer;
- the sender may include the Load Control Information in each and every message (extended with LCI IE) towards
the peer;
- the sender may include Load Control Information periodically, i.e. include the information during a first period
then cease to do so during a second period.
ETSI
The sender may also implement a combination of one or more of the above approaches. Besides, the sender may also
decide to include the Load Control Information only in a subset of the applicable GTP-C messages.
The receiver shall be prepared to receive the load control information in any of the GTP-C messages extended with an
LCI IE and upon such reception, shall be able act upon the received load control information.
12.2.5.3 Limit on maximum number of instances

A GTP-C entity may signal one or multiple instances of the LCI IE, with each providing load control information for a
different scope. In order to limit the processing of the message on the receiver side and the size of the message on
transport level, the number of load control information instances shall be limited:
- at message level: there shall be at most one instance of node level LCI IE per node (i.e. per SGW or PGW) and
at most 10 APN level instances.
- at node level: the maximum number of instances of LCI IE which may be provided across multiple messages by
a given node shall be the same as the maximum number of instances of LCI IE at message level.
12.2.6 Discovery of the support of the feature by the peer node

A GTP-C entity shall determine whether to use the load control feature (i.e. provide or handle load control information)
- within the PLMN, based on the operator's policy (local PLMN-wide configuration);
- across the PLMN boundaries, based on the operator's policy (local configuration per PLMN).
NOTE: The feature may be activated when all or some of the nodes in the PLMN support the feature. The GTP-C
entity assumes that all of the peer nodes support this feature when the feature is activated, i.e. it does not need
to determine which peers support the feature.
The above operator policy/local configuration may allow the use of load control at node level, load control at node level
and APN level, or none.
12.2.7 Issues in the network with partial support of the feature

The Load Control feature should be supported homogenously across all the SGWs and PGWs in the network. Not
supporting this feature homogeneously across the SGWs and PGWs may result in poor load balancing in the network
such that the SGWs or PGWs not supporting the feature may operate near their maximum capacity (thus being more
vulnerable to overload conditions) while SGWs or PGWs supporting the feature have free capacity.
The Load Control feature should be supported homogenously across all the MMEs, S4-SGSNs, ePDGs and TWANs.
However, use of the feature when not all of these nodes support the feature may not necessarily create a problem since
the load may remain fairly balanced across the SGWs and PGWs assuming that the network imbalance caused by the
non-supporting node may get rectified by the supporting nodes making use of dynamic load information while selecting
the SGWs and PGWs.
12.3 Overload control solution

12.3.1 Principles of overload control
The stage 2 requirements on GTP-C overload control are defined in clause 4.3.7.1a.2 of 3GPP TS 23.401 [3] and clause
5.3.6.1a of 3GPP TS 23.060 [35]. The high level principles are summarized below:
a) Overload control is an optional feature;
b) a GTP-C entity may signal its overload to its GTP-C peers by including Overload Control Information in GTP-C
signalling which provides guidance to the receiving GTP-C entity to decide actions which lead to signalling
traffic mitigation towards the sender of the information;
c) the Overload Control Information may provide the overload information of a GTP-C entity, e.g. a PGW, or a
specific APN(s) associated with the GTP-C entity;
ETSI
d) an MME/S4-SGSN may signal an overload to the PGW, via the SGW. An SGW may signal an overload to the
MME/S4-SGSN and to the PGW. A PGW may signal an overload to the MME/S4-SGSN, via the SGW. For
non-3GPP access based interfaces, a PGW may signal an overload to the ePDG and the TWAN; the ePDG and
the TWAN may signal an overload to the PGW.
NOTE 1: An MME/S4-SGSN will not signal an overload to the SGW (i.e. the SGW will not perform overload
control towards the MME/S4-SGSN), as this is redundant with DDN throttling (see subclause 12.3.3).
e) the overload control feature should continue to allow for preferential treatment of priority users (eMPS) and
emergency services;
f) the Overload Control Information is piggybacked in GTP control plane request or response messages such that
the exchange of the Overload Control Information does not trigger extra signalling;
NOTE 2: The inclusion of Overload Control Information in existing messages means that the frequency increases
as the signalling load increases, thus allowing faster feedback and better regulation.
g) the computation and transfer of the Overload Control Information shall not add significant additional load to the
GTP-C entity itself and to its corresponding peer GTP-C entities. The calculation of Overload Control
Information should not severely impact the resource utilization of the GTP-C entity, especially considering the
overload situation;
h) clause 4.3.7.1a.2 of 3GPP TS 23.401 [3] and clause 4.5 of 3GPP TS 23.402 [45] provides examples of various
potential overload mitigation actions based on the reception of the overload related information exchanged
between GTP-C entities, for 3GPP access based interfaces and non-3GPP access based interfaces, respectively.
However, the exact internal processing logics of a GTP-C entity will not be standardized;
i) for the inter-PLMN case, local configuration may restrict the exchange and use of Overload Control Information
across PLMNs;
j) the GTP-C entity may decide to send different values of Overload Control Information on inter-network
(roaming) and on intra-network (non-roaming) interfaces based on local configuration, i.e. the values sent on
intra-network interfaces may differ from the values sent on inter-network interfaces. However, on intra-network
interfaces, the GTP-C entity should send the same values between the 3GPP and non-3GPP access based
interfaces;
12.3.2 Applicability to 3GPP and non-3GPP access based interfaces

The Overload Control feature may be supported on the 3GPP & non-3GPP access based interfaces and nodes as
summarized by the Table 12.3.2-1.
ETSI
Table 12.3.2-1: Applicability of overload control to 3GPP & non-3GPP access based GTP-C interfaces
and nodes
Originator Consumer Applicable Interfaces

MME PGW S11, S5/S8
SGW relays Overload Control Information from S11 to S5/S8
interface.
S4-SGSN PGW S4, S5/S8
SGW relays Overload Control Information from S4 to S5/S8
interface.
SGW MME S11
SGW S4-SGSN S4
SGW PGW S5/S8
(in MME/S4-SGSN originated signalling towards the PGW)
PGW MME S5/S8, S11
SGW relays Overload Control Information from S5/S8 to S11
interface.
PGW S4-SGSN S5/S8, S4
SGW relays Overload Control Information from S5/S8 to S4
interface.
PGW TWAN S2a (Trusted WLAN access)
PGW ePDG S2b (Untrusted WLAN access)
TWAN PGW S2a (Trusted WLAN access)
ePDG PGW S2b (Untrusted WLAN access)
NOTE: Refer to Annex D.2 for information on the GTP-C interfaces for which Overload Control is not
supported.
12.3.3 Node level overload control

Node level overload control refers to advertising of the overload information at node level, i.e. overload information at
node level granularity, and applying the mitigation policies towards the target node based on this information. This
helps in preventing severe overload and hence potential breakdown of the GTP-C node.
When a GTP-C entity determines that the offered incoming signalling traffic is growing (or is about to grow) beyond its
nominal capacity, it may signal an Overload Control Information IE to instruct its GTP-C peers to reduce the offered
load accordingly.
Overload Control is performed independently for each direction between two GTP-C entities. Overload Control may
run concurrently, but independently, for each direction between the two GTP-C entities.
Overload control of SGW originated traffic towards the MME/S4-SGSN shall rely on Downlink Data Notification
throttling, as specified in subclause 4.3.7.4.1a of 3GPP TS 23.401 [3] and 5.3.6.5 of 3GPP TS 23.060 [35], with the
addition that the SGWs should be allowed, by configuration, to throttle DDN requests for low priority, as well as
normal priority traffic (the SGW shall then throttle by priority DDN requests for low priority traffic).
12.3.4 APN level overload control
12.3.4.1 General
APN level overload control refers to advertising of the overload information at APN level granularity and hence
applying the mitigation policies based on this information to the signalling traffic related to this APN only. Only a PGW
may advertise APN level overload information when it detects overload for certain APNs, e.g. based on shortage of
internal or external resources for an APN (e.g. IP address pool).
NOTE: When all the internal and external resources, applicable to the APNs, are available for all the APNs
served by a PGW, the node level overload information is exactly the same as APN level overload
information of that PGW, for each of its APNs, and hence, performing node overload control can be
sufficient.
ETSI
12.3.4.2 Elements of APN overload control

For allowing the effective APN overload control, at least the following information (in addition to the other applicable
information for overload control as defined in clause 12.3.5.1.2) are required to be advertised by the source node, as
part of the APN level overload information:
APN: The APN for which the source node wants to advertise the overload information;
APN-Overload-Reduction-Metric: It indicates the requested overload reduction for the signalling traffic
corresponding to a particular APN, as a percentage. Its computation is implementation dependent and it has the same
characteristics as the "Overload-Reduction-Metric", described in clause12.3.5.1.2.1, when applied at APN level.
12.3.5 Overload Control Information
12.3.5.1 Definition
12.3.5.1.1 General description

Within a message, one or multiple instances of the Overload Control Information (OCI) IE may be included by the
same GTP-C entity. Each instance shall provide information about the overload condition to allow the receiver to apply
mitigation actions which will result in an efficient alleviation of the overload condition at the sender.
The GTP-C entity shall always include the full set of overload control information, i.e. all the node level and APN level
applicable instances of the OCI IE, when signalling overload control information in a message for the first time or
subsequently towards the receiver, even when only a subset of the overload control information has changed. All the
instances of the OCI IE provided by a given GTP-C entity in a message shall contain the same Overload Control
Sequence Number. The Overload Control Sequence Number shall be incremented whenever the overload control
information is modified (see subclause 12.3.5.1.2.1).
When including overload control information for some APN(s), the PGW should not provide any node level Overload
Control Information unless the node level information is also applicable.
The receiver shall overwrite any stored overload control information of a peer with the newly received overload control
information (received via one or multiple instances of OCI IE) from the same GTP-C peer entity, if the new information
is more recent than the old information as indicated by the Overload Control Sequence Number, e.g. if the receiver has
stored 'X' instances of the OCI IE for a peer GTP-C entity, it shall overwrite those 'X' instances with the new set of 'Y'
instances received in a message from the same GTP-C peer entity, where X, Y are any integer numbers.
The receiver shall consider all the parameters received in the same instance of the OCI IE in conjunction while applying
the overload mitigation action. When more than one instance of the OCI IE is included, the receiver shall consider the
parameters included in each instance independently, while applying the overload mitigation action.
The parameters are further described in subclauses 12.3.5.1.2 and 12.3.5.1.3.
Overload control information may be extended with new parameters in future versions of the specification. Any new
parameter will have to be categorized as:
- Non-critical optional parameters: the support of these parameters is not critical for the receiver. The receiver can
successfully and correctly comprehend the Overload Control Information instance, containing one or more of
these parameters, by using the other parameters and ignoring the non-critical optional parameters.
- Critical optional parameters: the support of these parameters is critical for the receiver to correctly comprehend
the instance of the Overload Control Information containing one or more of these parameters.
The sender may include one or more non-critical optional parameter(s) within any instance of Overload Control
Information, without having the knowledge of the receiver's capability to support the same. However, the sender shall
only include one or more critical optional parameter(s) in any instance of Overload Control Information towards a
receiver, if the corresponding receiver is known to support these parameter(s). The sender may be aware of this either
via signalling methods or by configuration; this will have to be defined when introducing any such new parameter in the
future.
Each instance of the OCI shall be associated by default to the GTP-C entity corresponding to the peer node's IP address
of the PDN connection, over which the OCI IE is received, i.e. to the IP address received within the "Sender F-TEID for
ETSI
control plane" IE, the "PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane
interface" IE or within the "MME/S4-SGSN Identifier" IE.
Alternatively, the GW (i.e. SGW and PGW) nodes may send Overload Control Information which is associated with the
GW node's identity, i.e. the FQDN or IP address of the GW node received from the HSS or the DNS, the identity
determined during the GW selection. In that case, the GW node shall provide an explicit indication that the OCI IE
included in the message belongs to the GW node's identity.
12.3.5.1.2 Parameters
12.3.5.1.2.1 Overload Control Sequence Number
The GTP-C protocol requires retransmitted messages to have the same contents as the original message (see clause 7.6).
Due to GTP-C retransmissions, the overload control information received by a GTP-C entity at a given time may be less
recent than the overload control information already received from the same GTP-C entity. The Overload Control
Sequence Number aids in sequencing the overload control information received from an overloaded GTP-C entity. The
Overload Control Sequence Number contains a value that indicates the sequence number associated with the Overload
Control Information IE. This sequence number shall be used to differentiate between two OCI IEs generated at two
different instants, by the same GTP-C entity.
The Overload Control Sequence Number parameter shall be supported (when supporting the overload control feature)
and shall always be present in the Overload Control Information IE.
The GTP-C entity generating this information shall increment the Overload Control Sequence Number whenever
modifying some information in the OCI IE. The Overload Control Sequence Number shall not be incremented
otherwise. The GTP-C entity may use the time, represented in an unsigned integer format, of the generation of the
overload control information, to populate the Overload Control Sequence Number.
When multiple instances of the OCI IE are provided in the same message by a given GTP-C entity, each of the
Overload Control Sequence Numbers shall have the same value.
This parameter shall be used by the receiver of the OCI IE to properly collate out-of-order OCI IEs, e.g. due to GTP-C
retransmissions. This parameter shall also be used by the receiver of the OCI IE to determine whether the newly
received overload control information has changed compared to the overload control information previously received
from the same GTP-C entity. If the newly received overload control information has the same Overload Control
Sequence Number as the previously received overload control information from the same GTP-C peer, then the receiver
may simply discard the newly received overload control information whilst continuing to apply the overload abatement
procedures, as per the previous value.
NOTE 1: The timer corresponding to the Period of Validity (see 12.3.5.1.2.2) is not restarted if the newly received
overload control information has the same Overload Control Sequence Number as the previously received
overload control information. If the overload condition persists and the overloaded GTP-C entity needs to
extend the duration during which the overload information applies, the sender needs to provide a new
overload control information with an incremented Overload Control Sequence Number (even if the
parameters within the overload control information have not changed).
NOTE 2: The GTP-C Sequence Number cannot be used for collating out-of-order overload information as e.g.
overload control information may be sent in both GTP-C requests and responses, using independent GTP-
C sequence numbering.
If the receiving GTP-C entity already received and stored overload control information, which is still valid, from the
overloaded GTP-C entity, the receiving entity shall update its overload control information, only if the Overload-
Sequence-Number received in the new overload control information is larger than the value of the Overload Control
Sequence Number associated with the stored information. However due to roll-over of the Overload Control Sequence
Number or restart of the GTP-C entity, the Overload Control Sequence Number may be reset to an appropriate base
value by the peer GTP-C entity, hence the receiving entity shall be prepared to receive (and process) an Overload
Control Sequence Number parameter whose value is less than the previous value.
12.3.5.1.2.2 Period of Validity
The Period of Validity indicates the length of time during which the overload condition specified by the OCI IE is to be
considered as valid (unless overridden by subsequent new overload control information).
ETSI
An overload condition shall be considered as valid from the time the OCI IE is received until the period of validity
expires or until another OCI IE with a new set of information (identified using the Overload Control Sequence Number)
is received from the same GTP-C entity (at which point the newly received overload control information shall prevail).
The timer corresponding to the period of validity shall be restarted each time an OCI IE with a new set of information
(identified using the Overload Control Sequence Number) is received. When this timer expires, the last received
overload control information shall be considered outdated and obsolete, i.e. any associated overload condition shall be
considered to have ceased.
The Period of Validity parameter shall be supported (when supporting overload control).
The Period of Validity parameter achieves the following:
- it avoids the need for the overloaded GTP-C entity to include the Overload Control Information IE in every
GTP-C messages it signals to its GTP-C peers when the overload state does not change; thus it minimizes the
processing required at the overloaded GTP-C entity and its GTP-C peers upon sending/receiving GTP-C
signalling;
- it allows to reset the overload condition after some time in the GTP-C peers having received an overload
indication from the overloaded GTP-C entity, e.g. if no signalling traffic takes place between these GTP-C
entities for some time due to overload mitigation actions. This also removes the need for the overloaded GTP-C
entity to remember the list of GTP-C entities to which it has sent a non-null overload reduction metric and to
which it would subsequently need to signal when the overload condition ceases, if the Period of Validity
parameter was not defined.
12.3.5.1.2.3 Overload Reduction Metric
The Overload Reduction Metric shall have a value in the range of 0 to 100 (inclusive) which indicates the percentage of
traffic reduction the sender of the overload control information requests the receiver to apply. An Overload Reduction
Metric of "0" always indicates that the GTP-C entity is not in overload (that is, no overload abatement procedures need
to be applied) for the indicated scope.
Considering the processing requirement of the receiver of the Overload Control Information, e.g. to perform overload
control based on the updated Overload Reduction Metric, the sender should refrain from advertising every small
variation, e.g. with the granularity of 1 or 2, in the Overload Reduction Metric which does not result in useful
improvement for mitigating the overload situation. During the typical operating condition of the sender, a larger
variation in the Overload Reduction Metric, e.g. 5 or more units, should be considered as reasonable enough for
advertising a new Overload Reduction Metric Information and thus justifying the processing requirement (to handle the
new information) of the receiver.
NOTE: The range of Overload Reduction Metric, i.e. 0 to 100, does not mandate the sender to collect its own
overload information at every increment/decrement and hence to advertise the change of Overload
Reduction Metric with a granularity of 1%. Based on various implementation specific criteria, such as the
architecture, session and signalling capacity, the current load/overload situation and so on, the sender is
free to define its own logic and periodicity with which its own overload control information is collected.
The computation of the exact value for this parameter is left as an implementation choice at the sending GTP-C entity.
The Overload Reduction Metric shall be supported (when supporting overload control) and shall always be present in
the OCI IE.
The inclusion of the OCI IE signals an overload situation is occuring, unless the Overload Reduction Metric is set to 0,
which signals that the overload condition has ceased. Conversely, the absence of the OCI IE in a message does not
mean that the overload has abated.
12.3.5.1.2.4 List of APNs
The List of APNs IE indicates one or more APNs for which the Overload Control Information is applicable. When
present in the OCI IE, the scope of the overload control information shall be the list of the indicated APNs for the PGW
that sends the overload control information. At most one instance of the List of APNs IE shall be included within one
Overload Control Information instance.
NOTE 1: The maximum number of APNs in the List of APNs is set to 10. More than 10 occurrences of APN
within one single instance of the List of APNs IE is treated as a protocol error by the receiver.
ETSI
If the List of APNs IE has not been included, the scope of the Overload Control Information shall be the entire GTP-C
entity (unless restricted by other parameters in the Overload Control Information IE).
The List of APNs parameter shall be supported (when supporting overload control). The List of APNs may be present
or absent in the Overload Control Information IE (depending on the scope of the reported overload control information).
NOTE 2: The instance number of both the node-level and APN-level overload control information is "0" and the
instance number is therefore not used to indicate if the scope of the overload control information is on
PGW node level or APN level.
This parameter may be provided by the PGW only and it shall be used by the MME/S4-SGSN and the TWAN/ePDG
only.
The maximum number of APNs, for which the PGW may advertise the Overload Control Information, shall be limited
to 10, i.e. the maximum number of occurrences of APNs within and across various instances of the Overload Control
Information IE shall be limited to 10 for a given PGW. Hence, if the PGW supports more than 10 APNs, it shall
advertise the overload control for at most 10 of the most important APNs. In future, if needed, this limit may be
increased to allow the PGW to advertise the overload information for more APNs. In that case, the receiver that does
not support the higher limit shall only handle the first 10 APNs and ignore the overload information for the remaining
APNs to enable future compatibility.
NOTE 3: Considering various aspects such as: the processing and storage requirements at the overloaded GTP-C
entity and the receiver, the number of important APNs for which overload control advertisement could be
necessary, interoperability between the nodes of various vendors, etc. it was decided to define a limit on
maximum number of APNs for advertising the overload control information. It was decided to fix this
limit to 10 whilst also ensuring that the mechanism exists to extend this limit in future releases, if
required.
12.3.5.1.3 Handling of parameters

If the PLMN supports the Overload Control feature (see subclause 12.3.11), the support, inclusion and handling of the
parameters, within overload control information, is summarized in table 12.3.5.1.3-1.
Table 12.3.5.1.3-1: Parameters of the Overload Control Information
Parameter Support by the Support by the Inclusion by the Handling by the

sender receiver sender receiver
Overload Control Mandatory Mandatory Mandatory Mandatory
Sequence Number (as
defined in clause
12.3.5.1.2.1)
Period of Validity (as Mandatory Mandatory Mandatory Mandatory
defined in clause
12.3.5.1.2.2)
Overload Reduction Mandatory Mandatory Mandatory Mandatory
Metric (as defined in
clause 12.3.5.1.2.3)
List of APNs (as Mandatory Mandatory Optional Conditional
defined in clause (NOTE 1) (NOTE 2)
12.3.5.1.2.4)
NOTE 1: The PGW shall send this parameter whilst providing APN level overload control information.
NOTE 2: If this parameter is received, the receiver shall handle and process APN level overload control information.
12.3.5.2 Frequency of inclusion

How often or when the sender includes the overload control information is implementation specific. The sender shall
ensure that new/updated overload control information is propagated to the target receivers with an acceptable delay,
such that the purpose of the information, (i.e. the effective overload control protection) is achieved. The following are
some of the potential approaches the sender may implement for including the OCI IE:
- the sender may include OCI IE towards a receiver only when the new/changed value has not already been
provided to the given receiver;
ETSI
- the sender may include the OCI IE in a subset of the messages towards the receiver;
- the sender may include the OCI IE periodically, i.e. include the information during a first period then cease
to do so during a second period.
The sender may also implement a combination of one or more of the above approaches. Besides, the sender may also
include the OCI IE only in a subset of the applicable GTP-C messages.
The receiver shall be prepared to receive the overload control information received in any of the GTP-C messages
extended with an OCI IE and upon such reception, shall be able act upon the received information.
12.3.5.3 Limit on maximum number of instances

A GTP-C entity may signal one or multiple instances of the OCI IE, each instance providing overload control
information for a different scope. The receiver shall handle all these instances, from each of the peer GTP-C entities, by
processing, storing and acting upon the same foroverload control. In order to limit the processing of the message on the
receiver side and the size of the message, the number of overload control information instances shall be limited:
- at message level: there shall be at most one instance of node-level Overload Control Information IE per node and
at most 10 APN-level instances.
- at node level: the maximum number of instances of the OCI IE which may be provided across multiple messages
by a given node shall be the same as the maximum number of instances of the OCI IE at message level.
12.3.6 Propagating the MME/S4-SGSN identity to the PGW

When the Overload Control feature is supported by the MME/S4-SGSN and the SGW, and it is also activated for the
PLMN to which the PGW belongs (see subclause 12.3.11), the following shall apply:
- The MME/S4-SGSN shall include the MME/S4-SGSN identity towards the SGW during:
- the PDN connection establishment, any mobility with an MME/S4-SGSN change or any SGW change
procedures;
- the dedicated bearer activation procedure, PGW initiated bearer modification procedure and PGW initiated
bearer deactivation procedure as per the conditions specified in the corresponding messages.
- The SGW shall forward the MME/S4-SGSN identifier to the PGW if it is received in the Create/Update/Delete
Bearer Response messages. When it is received in other GTP-C messages, the SGW shall store the received
MME/S4-SGSN identity and shall include the currently serving MME/S4-SGSN's identity in subsequent
Modify Bearer Request messages which are sent over the S5/S8 interface, whenever there is signalling over the
S5/S8 interface.
NOTE: This allows updating of the PGW with the identity of the new MME/S4-SGSN during inter-MME/SGSN
mobility scenarios as early as possible and without generating extra signalling over the S5/S8 interface.
Inter-MME/inter-SGSN intra SGW mobility scenarios not requiring to send any S5/S8 signalling could
result in the PGW not being updated with the currently serving MME/S4-SGSN's identity, for a given
subscriber, until subsequent S5/S8 signalling takes place for the same PDN connection. However,
considering these scenarios are not so frequent and considering that several features anyway require
S5/S8 signalling during these scenarios (e.g. for user location reporting), the PGW will most often get the
identity of the currently serving MME/S4-SGSN. Hence the risk that the PGW wrongly throttles PGW
initiated signalling for that PDN connection, if the old MME/S4-SGSN is in overload, is low.
- The PGW shall store the currently serving MME/S4-SGSN identity, received from the SGW, to be able to
reduce the PGW initiated signalling messages for the PDN connections during an overload situation at the
serving MME/S4-SGSN.
12.3.7 Updating the PGW with overload control information of the target
MME/S4-SGSN
During inter-MME/S4-SGSN mobility without SGW change scenarios, the SGW shall forward the MME/S4-SGSN's
overload control information over the S5/S8 interface only if the Modify Bearer Request message needs to be sent over
ETSI
the S5/S8 for another reason, e.g. if the ULI, CGI, Serving Network, needs to be reported to the PGW, i.e. the SGW
shall not generate a Modify Bearer Request message over the S5/S8 interface for the sole purpose of reporting the
MME/S4-SGSN's overload control information. This avoids generating extra signalling over the S5/S8 interface.
NOTE: If the MME/S4-SGSN provides overload control information during the scenarios which do not result in
S5/S8 signaling, e.g. during an inter MME/S4-SGSN and intra SGW mobility, when no other information
such as: the ULI, CGI or Serving Network, needs to be reported to the PGW, the overload information
will not be relayed on to the PGW. Hence, the MME/S4-SGSN needs consider this when including
overload control information.
12.3.8 The interaction with APN congestion control using the PGW Back-
Off Time
When detecting that a given APN is congested, the PGW shall either use the PGW Back-Off Time mechanism (see
subclause 4.3.7.5 of 3GPP TS 23.401 [3]) or the APN level overload control mechanism (i.e. providing an Overload
Control Information IE with an APN-List included) for that APN, but not both together for the same APN, e.g. if the
PGW provides an Overload Control Information IE with an APN-List set to "APN1", it shall not reject Create Session
Request messages for "APN1" with a PGW Back-Off Time until the Period-Of-Validity of the overload information
previously sent has expired.
The PGW may however use both mechanisms concurrently for different APNs, e.g. the PGW may reject Create Session
Request messages for the"APN2" with a PGW Back-Off Time IE, if the APN2 is also congested and if there is no on-
going APN-level overload control mechanism for that APN.
When rejecting a Create Session Request due to APN congestion, the PGW shall set the "APN Congestion" cause,
regardless of the aforementioned mechanisms.
If the MME/S4-SGSN or ePDG/TWAN has one mechanism active for a given APN and PGW, (e.g. an MME has
received a PGW Back-Off Time) and if subsequently it receives information for the same APN and PGW for another
mechanism, (e.g. the MME receives an Overload Control Info IE with APN-List included for the same APN), then it
shall deactivate/stop the earlier mechanism and consider only the information received for the latter mechanism.
Different PGWs may use concurrently different mechanisms for the same APN.
12.3.9 Message throttling
12.3.9.1 General
As part of the overload mitigation, a GTP-C entity shall reduce the total number of messages, which would have been
sent otherwise, towards the overloaded peer based on the information received within the Overload Control
Information. This shall be achieved by discarding a fraction of the messages in proportion to the overload level of the
target peer. This is called message throttling.
Message throttling shall only apply to initial messages. Triggered request or response messages should not be throttled
since that would result in the retransmission of the corresponding request message by the sender.
Before piggybacking the initial message over a response message, the initial message should be subject to the message
throttling in the similar manner as any other non-piggybacked initial message. If the node decides to throttle this initial
message then the response message should be sent without any piggyback message.
ETSI
A GTP-C entity supporting GTP-C overload control shall support and use the "Loss" algorithm as specified in this
clause, for message throttling.
12.3.9.2 Throttling algorithm – "Loss"
12.3.9.2.1 Description
An overloaded GTP-C entity shall ask its peers to reduce the number of requests they would ordinarily send by
signalling Overload Control Information including the requested traffic reduction, as a percentage, within the
"Overload-Reduction-Metric", as specified in clause 12.3.5.1.2.1.
The recipients of the "Overload-Reduction-Metric" shall reduce the number of requests sent by that percentage, either
by redirecting them to an alternate destination if possible (e.g. the Create Session Request message may be redirected to
an alternate SGW/PGW), or by failing the request and treating it as if it was rejected by the destination GTP-C entity.
For example, if a sender requests another peer to reduce the traffic it is sending by 10%, then that peer shall throttle
10% of the traffic that would have otherwise been sent to this GTP-C entity.
The overloaded GTP-C entity should periodically adjust the requested traffic reduction based e.g. on the traffic
reduction factor that is currently in use, the current system utilization (i.e. the overload level) and the desired system
utilization (i.e. the target load level), and/or the rate of the current overall received traffic.
Annex D.3.1 provides an (informative) example of a possible implementation of the "Loss" algorithm, amongst other
possible methods.
NOTE 1: This algorithm does not guarantee that the future traffic towards the overloaded GTP-C entity will be less
than the past traffic but it ensures that the total traffic sent towards the overloaded GTP-C entity is less
than what would have been sent without any throttling in place. If after requesting a certain reduction in
traffic, the overloaded GTP-C entity receives more traffic than in the past, whilst still in overload, leading
to the worsening rather than an improvement in the overload level, then the overloaded GTP-C entity can
request for more reduction in traffic. Thus, by periodically adjusting the requested traffic reduction, the
overloaded node can ensure that it receives, approximately, the amount of traffic which it can handle.
NOTE 2: Since the reduction is requested as a percentage, and not as an absolute amount, this algorithm achieves a
good useful throughput towards the overloaded node when the traffic conditions vary at the source nodes
(depending upon the events generated towards these source nodes by other entities in the network), as a
potential increase of traffic from some source nodes can possibly be compensated by a potential decrease
of traffic from other source nodes.
12.3.9.3 Message prioritization
When performing message throttling:
- GTP requests related to priority traffic (i.e. eMPS as described in 3GPP TS 22.153 [62]) and emergency have the
highest priority. Depending on regional/national requirements and network operator policy, these GTP requests
shall be the last to be throttled, when applying traffic reduction, and the priority traffic shall be exempted from
throttling due to GTP overload control up to the point where the requested traffic reduction cannot be achieved
without throttling the priority traffic;
- for other types of sessions, messages throttling should consider the relative priority of the messages so that the
messages which are considered as low priority are considered for throttling before the other messages. The
relative priority of the messages may be derived from the relative priority of the procedure for which the
message is being sent (as specified in subclause 12.3.9.3.2) or may be derived from the session parameters (as
specified in subclause 12.3.9.3.3).
NOTE: A random throttling mechanism, i.e. discarding the messages without any special consideration, could
result in an overall poor congestion mitigation mechanism and bad user experience.
An overloaded node may also apply these message prioritization schemes when handling incoming initial messages
during an overloaded condition, as part of the self-protection mechanism (see subclause 12.3.10.2.3).
ETSI
12.3.9.3.2 Based on procedures

Message prioritization may be performed based on the relative priority of the procedure for which the message is being
sent. Procedures are grouped into various categories and each of these categories is assigned a priority. Additionally,
within a given category of procedures, messages may be further prioritized based on session parameters such as: APN,
QCI, ARP and/or LAPI (as described in subclause 12.3.9.3.3).
Subsequently, messages with a high priority shall be given lower preference to throttle and messages with low priority
shall be given higher preference to throttle.
The grouping of the procedures is not performed based on an individual GTP-C entity but whilst considering all the
procedures in general. A GTP-C entity should consider the procedures applicable to it and apply prioritized message
throttling based on the category of the procedure, as described below. The categories are listed in decreasing order of
priority with category 1 having the highest priority. For each category a non-exhaustive list of messages is provided.
Any existing or newly defined message in future should be considered based on the category (as specified below) of the
procedure for which the message is sent.
1. UE session mobility within and across 3GPP or non-3GPP access: Procedures involving active or idle mode
UE mobility, such that GTP-C signalling is involved, shall be classified under this category. Some examples are
X2/S1 based handover with/without an SGW change, TAU/RAU with a change of MME/SGSN with/without an
SGW change, 3GPP access to trusted non-3GPP access handover, etc. Throttling of these messages, during the
procedures related to UE session mobility, would result in the failure of the corresponding procedures. This
could result potentially in the loss of the PDN connection and/or the interruption of the services. Hence, the
messages, as identified below, when sent during the procedures belonging to this category, shall be considered
with the highest priority and hence, shall be given the lowest preference to throttle.
- Create Session Request,
- Create Session Request with "handover" indication bit set,
- Modify Bearer Request,
- Modify Bearer Request with "handover" indication bit set,
- Modify Access Bearer Request.
2. Release of PDN connection or bearer resources: Procedures resulting in the deactivation of an existing PDN
connection, the deactivation of bearer(s) or of data forwarding tunnel of an UE leads to freeing up of the
resources at the overloaded node and hence, can potentially ease the overload situation, since the freed up
resources can be used for serving the remaining of the UEs. Thus, the messages belonging to this category
resulting in the deactivation of PDN connection or bearer(s) or data forwarding tunnel(s), as identified below,
shall be treated with the next lower level of priority and hence shall be given the corresponding preference whilst
throttling:
- Delete Session Request,
- Delete Bearer Request,
- Delete Bearer Command,
- Delete Indirect Data Forwarding Tunnel Request.
3. Miscellaneous session management procedures: This category shall consist of the session management
procedures, except PDN connection creation and bearer creation/modification procedures. Some examples are
location reporting, when it is not combined with other mobility procedures, Service request and S1 release
procedure. These procedures do not severely impact the on-going service of the UE. Hence, the messages, as
identified below, when sent during the procedures identified under this category, shall be treated with the next
lower level of priority and hence, shall be given the corresponding preference whilst throttling:
- Release Access Bearer Request,
- Modify Bearer Request,
- Change Notification,
- Suspend Notification,
ETSI
- Resume Notification.
4. Request for new PDN Connection or bearer resources: Procedures requesting the creation of PDN
connection, creation or modification of bearer(s) or creation of data forwarding tunnel shall be classified in this
category. Throttling of the messages belonging to this category would result in denial of new services while
continuing with the existing services. However, this is the natural outcome of an overload condition, i.e. the
overloaded node, due to lack of resources, is not able to provision new services while the trying to maintain the
existing services and hence, the messages, as identified below, when sent during the procedures belonging to this
category, shall be considered with the lowest level of priority and hence shall be given highest preference to
throttle:
- Create Session Request during PDN connection request,
- Create Bearer Request,
- Update Bearer Request,
- Bearer Resource Command,
- Modify Bearer Command,
- Create Indirect Data Forwarding Tunnel Request.
12.3.9.3.3 Based on session parameters

Message prioritization may be performed based on the session parameters, such as: APN, QCI, ARP and/or Low Access
Priority Indicator (LAPI). The procedures and messages associated with the higher priority sessions shall be given
lesser preference whilst throttling, as compared to the procedures and messages associated with the lower priority
sessions. Within each group of sessions, the messages may be further prioritized based on the category of the procedure
for which the message is being sent (as described in subclause 12.3.9.3.2).
NOTE: This type of prioritization scheme ensures a good handling of all the messages and procedures related to
higher priority sessions but can lead to throttle messages related to a critical procedure, e.g. UE mobility,
for lower priority sessions over messages related to less critical procedures, e.g. location reporting, for a
higher priority session.
12.3.10 Enforcement of overload control
12.3.10.1 General
When a GTP-C entity receives Overload Control Information from its peer, it shall apply the overload abatement
algorithm, based on the received information, for the messages sent towards the peer GTP-C entity. This is called
"enforcement of overload control" and it involves throttling of the messages targeted for the overloaded peer.
12.3.10.2 Aspects related to enforcement of the overload control
12.3.10.2.1 Good throughput of the network

A source GTP-C entity should avoid any mechanism resulting in over throttling of the messages. Enforcement of the
overload control whilst ensuring that good throughput (i.e. measured in terms of the rate of total number of messages
the overloaded GTP-C entity can successfully process) of the network remains consistent to that when no overload
control is applied, should be one of the prime objective of the source GTP-C entity.
NOTE: Over throttling of messages would negatively affect end user services and cause potential additional
signalling in the network e.g. if the corresponding procedure is retried at a later time.
12.3.10.2.2 Message processing efficiency at the source GTP-C entity

Enforcement of overload control requires extra logic and extra processing at the source GTP-C entity. This is an
overhead since the source GTP-C entity has to spend its resources in an activity other than processing of the messages.
Hence, the implementation as well as the processing complexity of the enforcement of the overload control, should not
result in a significantly poorer efficiency of the source GTP-C entity.
ETSI
12.3.10.2.3 Self-protection by the overloaded GTP-C entity

A source GTP-C entity enforcing the overload control cannot ensure that the overloaded peer will not receive more
messages than what it can handle during the overload condition, e.g. the "loss" algorithm does not guarantee that the
future traffic reaches perfectly that requested by the overloaded GTP-C entity. Hence, the overloaded target GTP-C
entity shall protect itself from the risk of meltdown even in a network where all the sending GTP-C entities support the
overload control mechanism. As a part of this self-protection, the overloaded target GTP-C entity may reject the
messages which it cannot handle during an overloaded state. A GTP-C entity which decides to not process an incoming
request message due to overload should still send a reject response message, if possible, indicating the temporary
unavailability of the resources; otherwise the request message may be dropped.
NOTE: Without a response message, the source GTP-C entity cannot determine whether the request did not reach
the target GTP-C entity due to a network error or whether the target GTP-C entity was in overload and
not able to process the request and send a response message. This will cause the source GTP-C entity to
retransmit the request message and hence will increase further the overload at the target node.
While rejecting the message due to overload, the GTP-C entity shall set the cause to "GTP-C Entity Congestion" or
"APN congestion" (for node level or APN level overload respectively) and may include the Overload Control
Information in the rejection response as specified in subclauses 12.3.5.1.1 and 12.3.11.
12.3.10.3 Enforcement of overload control between GTP-C entities in direct contact

A source GTP-C entity shall enforce overload control for traffic destined to a GTP-C entity in direct contact based on
the overload reduction metric received from that peer, e.g. the MME applies the overload control for the messages
targeted for the SGW based on the overload information of the SGW.
12.3.10.4 Enforcement of overload control between remote GTP-C entities
For messages destined to a remote GTP-C entity (i.e. a GTP-C entity not in direct contact but reached via an
intermediate GTP-C entity), the source GTP-C entity shall enforce the overload control based on the overload
information of the target of the message, as well as the overload information of the intermediate GTP-C entity, e.g. the
MME applies the overload control for messages targeted for the PGW based on the overload information of the SGW
and PGW.
For the received messages, the intermediate GTP-C entity shall not further enforce any overload control and hence,
shall not reject any message towards the source GTP-C entity.
Annex D.4.1 provides an (informative) example of a possible implementation.
NOTE 1: This approach ensures the overload protection of the Target as well as Intermediate GTP-C entities.
NOTE 2: The source GTP-C entity may be connected to the same Target GTP-C entity via multiple different
Intermediate GTP-C entities. The exact algorithm used at the source GTP-C entity to enforce the overload
control, as per the aforementioned requirements, is implementation specific.
12.3.11 Discovery of the support of the feature by the peer node

A GTP-C entity shall determine whether to use the overload control feature:
- within the PLMN, based on operator's policy (local PLMN-wide configuration);
- across the PLMN boundaries, based on operator's policy (local configuration per PLMN).
NOTE: The feature can be activated when all or some of the nodes in the PLMN support the feature. The GTP-C
entity assumes that all the peer nodes support this feature when the feature is activated, i.e. it does not need to
determine which peers support the feature.
The above operator policy/local configuration may allow the use of overload control at node level and APN level, or
none.
ETSI
12.3.12 Issues in the network with partial support of the feature

The Overload Control feature should be supported homogenously across the nodes in the network, otherwise:
- an overloaded node will get messages beyond its acceptable processing capacity, even after announcing its
overload status. This may result in severe overload and possibly a breakdown of the node;
- a non-supporting node will get an unfair advantage in sending all the messages to an overloaded node, whereas a
supporting node, would be requested to throttle more messages.
12.3.13 Implicit overload control mechanisms

Implicit overload control mechanisms are mechanisms used between GTP-C entities when GTP-C overload control is
not supported or not enabled between them, e.g. across PLMN boundary based on operator's policy, to help reducing the
overload at the overloaded node:
- a GTP-C entity which decides to not process an incoming request message due to overload should still send a
reject response message, if possible, indicating the temporary unavailability of the resources, e.g. No resources
available; otherwise the GTP-C entity may drop the incoming request message.
NOTE: Without a response message, the source GTP-C entity cannot determine whether the request did not reach
the target GTP-C entity due to a network error or whether the target GTP-C entity was in overload and
not able to process the request and send a response message. This will cause the source GTP-C entity to
retransmit the request message and hence will increase further the overload at the target node.
- a GTP-C entity in overload may support messages throttling as a self protection mechanism and may apply
message prioritization as described in subclause 12.3.9 when selecting the incoming request messages to be
throttled;
- based on the number and rate of reject responses indicating temporary unavailability of resources, e.g. No
resources available, a source GTP-C entity should try to assess the overload level of the target GTP-C entity and
apply correspondingly message throttling as described in subclause 12.3.9 to reduce the amount of traffic sent
towards the overloaded GTP-C entity.
13 Detection and handling of late arriving requests
13.1 General
The procedures specified in this clause aim at handling more efficiently requests which may arrive late at upstreams
entities, e.g. in networks experiencing processing or transport delays.
These procedures are optional to support. When supported, the use of these procedures is dependent on operator policy.
The procedure specified in subclause 13.2 may be used with or without the procedure specified in subclause 13.3. The
procedure specified in subclause 13.3 shall only be used in conjunction with the procedure specified in subclause 13.2.
13.2 Detection and handling of requests which collide with an

existing session context
13.2.1 General
This procedure enables an entity, which receives a request colliding with an existing session context, to know the time
at which the new request and the existing session were originated, and to accept the new request only if it is more recent
than the existing session.
The originating entities within the PLMN (i.e. MME, SGSN, TWAN and ePDG) shall be NTP synchronized.
ETSI
13.2.2 Principles
The following principles shall apply if this procedure is supported and enabled by operator policy.
A GTP-C entity originating a Create Session Request (i.e. MME, SGSN, TWAN or ePDG) shall include in the message
the Origination Time Stamp indicating the absolute time at which the request is initiated.
The SGW shall forward this parameter over the S5/S8 interface, if it is received from the MME/SGSN.
Upon receipt of a session establishment request which collides with an existing session context, the PGW shall accept
the new session establishment request only if it contains a more recent time stamp than the time stamp stored for the
existing session. An incoming session request shall be considered as more recent than an existing session and be
accepted if no Origination Time Stamp information was provided for at least one of the two sessions. The PGW shall
reject an incoming request whose time stamp is less recent than the time stamp of the existing session with the cause
'Late Overlapping Request'.
3GPP TS 29.212 [29] and 3GPP TS 29.273 [68] further specify:
- the PGW requirements regarding the forwarding of the Origination Time Stamp parameter over the Gx and/or
S6b interfaces, when received from the SGW or TWAN/ePDG;
- the handling of the Origination Time Stamp parameter by the PCRF and 3GPP AAA Server for an incoming
request colliding with an existing session context.
An originating entity which detects a NTP failure shall not include the Origination Time Stamp towards other entities.
13.3 Detection and handling of requests which have timed out at

the originating entity
13.3.1 General
This procedure enables an entity which receives a request to know when the request times out at the originating entity,
and to stop further processing, at the receiver and further upstream entities, a request which has timed out at the
originating entity.
The originating entities (i.e. MME, SGSN, TWAN and ePDG) and the receiving entities (i.e. SGW, PGW, PCRF, 3GPP
AAA Server) shall be NTP synchronized. This procedure may be used between entities pertaining to the same PLMN,
and if allowed by operator policy, between entities pertaining to different PLMNs.
This procedure shall not affect the setting of the retransmission timers by intermediate entities. E.g. the SGW shall set
its T3 and N3 retransmission parameters as specified in this specification, irrespective of the time at which the request
times out at the originating entity.
13.3.2 Principles
The following principles shall apply if this procedure is supported, enabled by operator policy and if the PGW pertains
to the same PLMN as the originating entity or if the PGW pertains to a different PLMN and operator policy in the
originating entity allows to use this procedure towards this PLMN.
A GTP-C entity originating a Create Session Request (i.e. MME, SGSN, TWAN or ePDG) shall include in the message
the Origination Time Stamp indicating the absolute time at which the request is initiated, as specified in subclause
13.2.2, and the Maximum Wait Time indicating the maximum time period to complete the processing of the request.
The Maximum Wait Time, together with the Origination Time Stamp, indicates the absolute time at which the request
times out at the originating entity.
The MME/SGSN shall set the Maximum Wait Time to a value smaller or equal to (N3+1) x T3 set in the SGW, to
avoid upstream entities continuing to process requests which would have ceased to be processed by the SGW, which
could result in hanging contexts in upstream entities.
ETSI
NOTE 1: If the Maximum Wait Time is set to a value smaller than N3 x T3 set in the SGW, the SGW actually stops
retransmitting a given GTP-C Create Session Request as soon as it receives a rejection response from the
PGW due to the expiry of the Maximum Wait Time. I.e. the Maximum Wait Time actually leads to
shorten the duration during which the SGW retransmits the GTP-C request.
The SGW shall forward the Origination Time Stamp over the S5/S8 interface as specified in subclause 13.2.2. The
SGW shall also forward the Maximum Wait Time over the S5 interface, if received from the MME/SGSN.
Upon receipt of a request which contains the Origination Time Stamp and the Maximum Wait Time parameters, the
receiving entity should check that the request has not already timed out at the originating entity. The receiving entity
may perform additional similar checks during the processing of the request, e.g. upon receipt of a response from the
next upstream entity.
The receiving entity should reject a request that is known to have timed out with the cause 'Timed Out Request'; it may
alternatively drop the request. Besides, the receiving entity should initiate the release of any session it may have
successfully created towards an upstream entity, to avoid hanging sessions in the network.
NOTE 2: Sending a rejection response over the last hop towards the originating node, i.e. over S11/S4 or S2a/S2b,
is not useful as the request has timed out at the originated entity.
In the context of this specification, the receiving entity refers to an SGW or PGW.
3GPP TS 29.212 [29] and 3GPP TS 29.273 [68] further specify:
- the PGW requirements regarding the forwarding of the Maximum Wait Time parameter over the Gx and/or S6b
interfaces, when received from the SGW or TWAN/ePDG;
- the handling of the Maximum Wait Time parameter by the PCRF and 3GPP AAA Server.
An originating entity which detects a NTP failure shall not insert the Origination Time Stamp and the Maximum Wait
Time parameters towards other entities. A receiving entity which detects a NTP failure shall ignore the the Maximum
Wait Time parameter.
ETSI
Annex A (Informative):
Backward Compatibility Guidelines for Information Elements
In order to preserve backward compatibility, the following rules should apply when adding or modifying information
elements for existing messages.
- No new mandatory (M) information elements should be added.
- No new conditional (C) information elements should be added.
- Any new IEs should be either:
optional (O), having no conditions on their presence, or
conditional-optional (CO), having conditions that should apply only to the sender and not to the receiver.
Such conditions should be worded generally as follows: "This IE shall be sent over the xxx interface
<condition>. The receiving entity need not check the IE's presence."
- If any new conditions are added to a previously specified conditional (C) information element, these new
conditions should apply only to the sender and not to the receiver.
Such additional conditions should be worded generally as follows: "This IE shall be sent over the xxx interface
<condition>. For this optional condition, the receiving entity need not check the IE's presence."
Existing conditions for such conditional (C) IEs should be treated as before, and the presence of the IEs should
remain conditional (C).
ETSI
Annex B (Informative):
Transparent copying of RANAP/S1AP IEs into GTP IEs
B.1 General
This annex provides details on how a GTPv2 entity transparently copies information received from RANAP or S1AP
into GTPv2 IE or IE field.
RANAP and S1AP ASN.1 encoding details in this annex are informative. The reference specifications are 3GPP TS
25.413 [33] and 3GPP TS 36.413 [10] respectively.
The respective RANAP/S1AP Information Elements are transported on the Iu/S1 interface within a "protocol-IE
container" which is composed of:
- an Information Element Identity (referred to below as "IE-ID"),
- an indication how the receiver shall react if the Information Element is not comprehended (referred to below as
"criticality"),
- and an "open type field" which consists of a length indication ("OT-LI") and the Information Element itself
(referred to below as "IE").
RANAP/S1AP PDUs and the contained IEs are defined by means of ASN.1, the specified encoding is PER (packed
encoding rule), Octet aligned variant:
- PER minimises the information sent on the respective interface to the absolute minimum;
- Hence, type definitions of fixed length are encoded without any type or length indication, only type definitions
of variable length contain a length indication, e.g.
- an OCTET STRING with indefinite length would need to contain a length indication (referred to below as
"OCT-LI") followed by the actual octets (referred to below as "octets");
- a SEQUENCE neither contains a type, nor a length-indication. Only in case of optional elements it contains a
kind of bit string with each position of this bitstring indicating the presence of an OPTIONAL element (an
encoded SEQUENCE type is referred to below as "sequence").
B.2 Handover/Relocation related generic transparent

Containers over RANAP, S1-AP and GTP
Handover/Relocation related generic transparent containers are defined in 3GPP TS 25.413 [33] and 3GPP TS 36.413
[10] ("Source to Target Transparent Container" IE and "Target to Source Transparent Container" IE) to carry UTRAN,
E-UTRAN or GERAN specific information via CN interfaces in a RAT-agnostic way.
The encoding of these handover/relocation related generic transparent containers is different in RANAP and S1-AP. See
3GPP TS 36.413 [10] Annex C. The difference is that the "Source to Target Transparent Container" IE and "Target to
Source Transparent Container" IE are ASN.1 encoded over RANAP as "IE-ID||criticality||OT-LI||octets" (i.e. one length
field only for the open type field) and over S1AP as "IE-ID||criticality||OT-LI||OCT-LI||octets" (i.e. with 2 length fields,
one for the open type field ("OT-LI"), one for the octet string encoding ("OCT-LI")), while "octets" contain the actual
RAT specific handover/relocation information.
This gives the following chain of encodings (represented in the notation introduced in the Notes above) end-to-end.
LTE to LTE
ETSI
eNB S-MME T-MME eNB
Handover Required
“F-Container field” Handover Request
“SourceToTargetTransparent Container” transported via an contains “sequence” only

“SourceToTargetTransparent Container” transported via an
IE container == (IE-ID|criticality||OT-LI||IE)
IE == OCT-LI||octets
octets == sequence ==”Source eNB to Target eNB
octets == sequence == “Source eNB to Target eNB
Transparent Container”
Figure B.2-1: LTE to LTE - Encoding of Generic Transparent Containers
In the case of LTE-LTE handover, the "octets" contain the "Source eNB to Target eNB Transparent Container" (defined
as an ASN.1 SEQUENCE in 3GPP TS 36.413[10]).
The source MME, after decoding the HO REQUIRED message of S1AP, passes transparently the "sequence" to the
target MME.
The target MME encodes similarly at target side with the same definitions: it feeds the received "sequence" into the
S1AP ASN.1 encoder in order to encode the HO REQUEST message towards the target eNB. The "sequence" is then
extracted from the S1AP ASN.1 of eNB and given to application part of eNB.
LTE to 3G
eNB S-MME SGSN RNC
Handover Required
“F-Container field” Relocation Request

IE == sequence == “Source RNC to Target RNC
octets == sequence ==”Source RNC to Target RNC
Figure B.2-2: LTE to 3G - Encoding of Generic Transparent Containers
At source side, the same encoding is done but for LTE to 3G handover, this time the "octets" on the line is the "Source
RNC to Target RNC Transparent Container" (encoded according to the target system RANAP i.e. as an ASN.1
SEQUENCE in 3GPP TS 25.413 [33]).
Again the source MME passes transparently the "sequence" to the target MME i.e. the "Source RNC to Target RNC
Transparent Container".
At the target side, the RANAP RELOCATION REQUEST message was not upgraded: the "sequence" received from
the Gn or S3 interface ("Source RNC to Target RNC Transparent Container") is not encoded as an OCTET STRING as
on S1, but directly represent the "Source To Target Transparent Container" within the RANAP:RELOCATION
REQUEST message, which in case of inter-RAT handover to 3G represent the "Source RNC to Target RNC
Transparent Container", transported on the Iu interface as the "IE" part of the "IE container". There is no additional
length field added as on the S1 interface ("OCT-LI").
The target side remains therefore fully backwards compatible with UMTS release 7.
3G to LTE
ETSI
RNC R8 SGSN (R7) T-MME eNB
Relocation Required
“F-Container field” Handover Request

IE == sequence ==”Source eNB to Target eNB Transparent
Container”
octets == sequence ==”Source eNB to Target eNB
Figure B.2-3: 3G to LTE - Encoding of Generic Transparent Containers
The RELOCATION REQUIRED message was upgraded from release 8 onwards renaming the previously contained
"Source RNC to Target RNC Transparent Container" to "Source to Target Transparent Container", being able to
transport also a "Source eNB to Target eNB Transparent Container".
Despite being defined as an octet string, in order to not impact the R7 SGSN, the octet string was specified as "to be
replaced" by either the UTRAN or E-UTRAN specific container. This fact is explained e.g. within the NOTE in the
ASN.1 of 3GPP TS 25.413 [33] ], as shown in this excerpt:
Source-ToTarget-TransparentContainer ::= OCTET STRING
-- This IE is a transparent container, the IE shall be encoded not as an OCTET STRING but according
to the type specifications of the target system.
-- Note: In the current version of this specification, this IE may either carry the Source RNC to
-- Target RNC Transparent Container or the Source eNB to Target eNB Transparent Container IE as
-- defined in [49]
By so doing, the Release 7 source SGSN receives only one length field (the "OT-LI") instead of two (the "OT-LI and
the "OCT-LI") as if it would receive an "Source RNC to Target RNC Transparent Container" from a Release 7 RNC,
ensuring fully Release 7 backwards compatibility as requested by 3GPP TS 23.401 [3] Annex D. This is illustrated in
Figure B.1-3 above.
As explained above, this Release 7 backwards compatibility constraint only applies to RANAP to cope with Release 7
SGSN nodes and does NOT apply to LTE. This is why the note is NOT present in the ASN.1 of 3GPP TS 36.413 [10]
for LTE i.e. the S1AP octet string does not need "to be replaced".
Then "sequence" is passed transparently to the target MME. The target MME encodes the "sequence" within an OCTET
STRING resulting in two length fields as expected by target eNB ASN.1 S1AP decoder.
B.3 Other RANAP and S1-AP IEs

When transparently copying a RANAP/S1AP IE, other than the handover/relocation related generic transparent
containers (see Annex B.1) into GTP IE, or GTP IE field the following applies:
- a transparent copy of a RANAP/S1AP IE, which is transported on the Iu/S1 interface within a "protocol-IE
container", neither includes the Information Element Identity ("IE-ID") nor the "criticality" nor the open type
field related length indication ("OT-LI"), but only the Information Element itself ("IE").
- "IE" refers to all parts of the encoded type of the Information Element, i.e. including also any related length
indication (in case of types with variable length) and preamble (see ITU-T X.691 [49] for the definition of the
term "preamble").
ETSI
Annex C (Normative):
MME/S4-SGSN mapping table between S11/S4 and NAS
Cause values
The MME/S4-SGSN initiates session management requests towards the SGW and PGW or mobility management
requests towards the source/target MME/S4-SGSN. If this operation is not successful, there are several possible cause
codes, which need to be mapped to the appropriate cause codes over NAS to the UE.
Additionally, the MME/S4-SGSN initiates session management requests towards the UE. If this operation is not
successful, there are several possible NAS cause codes which need to be mapped to the appropriate GTP cause codes
over S11/S4 interface towards the SGW.
The MME/S4-SGSN should map these cause codes as defined in tables C.1 to C.5 unless specified otherwise in the
tables.
ETSI
Table C.1: Mapping from S11/S4 to NAS Cause values – Rejection indication from SGW
Reject indication from SGW to NAS ESM Cause to UE SM Cause to UE

MME/S4-SGSN (NOTE 1, NOTE 2, NOTE 3) (NOTE 1, NOTE 2, NOTE 3)
over S11/S4
#64 "Context not found" (during #54 "PDN connection does not exist" #30 "Activation rejected by GGSN,
UE initiated PDN connectivity Serving GW or PDN GW"
request for non-3GPP to 3GPP #31 "Activation rejected, unspecified"
handover procedure)
#64 "Context not found" (during all #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
other procedures) or PDN GW"#38 "Network failure" Serving GW or PDN GW"
#43 "Invalid EPS bearer identity" #38 "Network failure"
#43 "Unknown PDP Context"
#65 Invalid Message Format #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
or PDN GW" Serving GW or PDN GW"
#38 "Network failure" #38 "Network failure"
#66 "Version not supported by next #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
peer" or PDN GW" Serving GW or PDN GW"
#67 "Invalid length" #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#68 "Service not supported" #32 "Service option not supported" #32 "Service option not supported"
#69 "Mandatory IE incorrect" #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#70 "Mandatory IE missing" #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#72 "System Failure" #34 "Service option temporarily out of #34 "Service option temporarily out of
order" order"
#38 "Network Failure" #38 "Network failure"
#30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#73 "No Resources available" #34 "Service option temporarily out of #34 "Service option temporarily out of
order" order"
#26 "Insufficient resources" #26 "Insufficient resources"
#76 "Semantic errors in packet #44 "Semantic errors in packet filter(s)" #44 "Semantic errors in packet filter(s)"
filter(s)"
#77 "Syntactic errors in packet #45 "Syntactical error in packet filter(s)" #45 "Syntactical error in packet filter(s)"
filter(s)"
#78 "Missing or unknown APN" # 27 "Missing or unknown APN" # 27 "Missing or unknown APN"
#80 "GRE key not found" #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#83 "Preferred PDN type not #32 "Service option not supported" #32 "Service option not supported"
supported" #50 "PDN type IPv4 only allowed" #50 "PDP type IPv4 only allowed"
#51 "PDN type IPv6 only allowed" #51 "PDP type IPv6 only allowed"
#84 "All dynamic addresses are #26 "Insufficient resources" #26 "Insufficient resources"
occupied"
#85 "UE context without TFT NA #46 "PDP context without TFT already
already activated" activated"
#86 "Protocol type not supported" #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#89 "Service denied" #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#31 "Request rejected, unspecified" #31 "Activation rejected, unspecified"
#91 "No memory available" #34 "Service option temporarily out of #34 "Service option temporarily out of
order" order"
#92 "User authentication failed" #29 "User authentication failed" #29 "User authentication failed"
NOTE
#93 "APN access denied – no #33 "Requested service option not #33 "Requested service option not
subscription" subscribed" subscribed"
ETSI
# 27 "Missing or unknown APN" # 27 "Missing or unknown APN"

#94 "Request rejected (reason not #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
specified)" or PDN GW" Serving GW or PDN GW"
#97 "Semantic error in the TAD #41 "Semantic error in the TFT #41 "Semantic error in the TFT
operation" operation" operation"
#98 "Syntactic error in the TAD #42 "Syntactical error in the TFT #42 "Syntactical error in the TFT
#100 "Remote peer not #34 "Service option temporarily out of #34 "Service option temporarily out of
responding" order" order"
#101 "Collision with network #56 "Collision with network initiated #56 "Collision with network initiated
initiated request" request" request"
#103 "Conditional IE missing" #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
#104 "APN Restriction type #112 "APN restriction value #112 "APN restriction value
Incompatible with currently active incompatible with active EPS bearer incompatible with active PDP context"
PDN connection" context"
#107 "Invalid reply from remote #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
peer" or PDN GW" Serving GW or PDN GW"
#31 "Request rejected, unspecified" #31 "Activation rejected, unspecified"
#112 "Request rejected for a #30 "Request rejected by Serving GW #30 "Activation rejected by GGSN,
PMIPv6 reason (see 3GPP TS or PDN GW" Serving GW or PDN GW"
29.275 [26])." #38 "Network Failure" #38 "Network failure"
#113 "APN Congestion" #26 "Insufficient resources" #26 "Insufficient resources"
#120 "GTP-C Entity Congestion"
#114 "Bearer handling not #60 "Bearer handling not supported" #60 "Bearer handling not supported"
supported"
#116 "Multiple PDN connections #55 "Multiple PDN connections for a #30 "Activation rejected by GGSN,
for a given APN not allowed" given APN not allowed" Serving GW or PDN GW"
#31 "Activation rejected, unspecified"
#126 "Multiple accesses to a PDN #113 "Multiple accesses to a PDN #113 "Multiple accesses to a PDN
connection not allowed" connection not allowed" connection not allowed"
NOTE 1: See 3GPP TS 24.301 [23] and 3GPP TS 24.008 [5] for NAS ESM and SM causes respectively.
NOTE 2: The MME/S4-SGSN may for certain GTP cause codes trigger a new GTP procedure instead of rejecting the
NAS request.
NOTE 3: When multiple NAS Cause values are defined for a given GTP cause value, any of those NAS Cause values
may be sent to the UE based on implementation choice.
NOTE: The MME can send the EMM cause set to #15 "No suitable cells in tracking area" to the UE, if the PDN
connectivity request is rejected due to the ESM cause #29, which is mapped from the GTPv2 cause code
#92 or XXX, based on operator policies. See 3GPP TS 24.301 [23]. This enables a roamer to get service
in a VPLMN even when being rejected via LTE access due to e.g. no credit authorisation from the OCS.
ETSI
Table C.2: Mapping from S11/S4 to NAS Cause values – Acceptance indication from SGW
Acceptance indication from SGW to NAS ESM Cause to UE SM Cause to UE

MME/S4-SGN
over S11/S4
#18 "New PDN type due to network #50 "PDN type IPv4 only allowed" #50 "PDP type IPv4 only allowed"
preference" #51 "PDN type IPv6 only allowed" #51 "PDP type IPv6 only allowed"
(NOTE 1) (NOTE 1)
#19 "New PDN type due to single #52 "single address bearers only #52 "single address bearers only
address bearer only" allowed" allowed"
NOTE 1: The actual NAS cause sent to the UE depends on the allocated IP address type.
Table C.3: Mapping from S11/S4 to NAS Cause values – Indication in request from SGW
Indication in a request / initial NAS ESM Cause to UE SM Cause to UE

message from SGW to MME/S4-
SGSN over S11/S4
#8 "Reactivation Requested" Shall be mapped to: Shall be mapped to:
(NOTE 1) #39 "Reactivation requested" in the #39 "Reactivation requested" in the
NAS bearer context deactivation NAS bearer context deactivation
procedure. procedure.
For the last PDN connection in E-
UTRAN, "Reactivation requested"
shall be mapped to "re-attach
required" in the NAS detach type IE.
#9 "PDN reconnection to this APN Implementation specific NAS cause Implementation specific NAS cause
disallowed" value indicating to the UE that the value indicating to the UE that the
(NOTE 1) APN is not currently available. APN is not currently available.
For the last PDN connection, NAS
detach type IE should be set to "re-
attach not required".
NOTE 1: In Delete Bearer Request during the PGW initiated bearer deactivation procedure for the default bearer.
Table C.4: Mapping from NAS to S11/S4 Cause values – Rejection indication from MME/S4-SGSN
NAS ESM Cause from UE SM Cause from UE Reject indication from MME/S4-
(NOTE 1) (NOTE 1) SGSN to SGW
over S11/S4
(NOTE 2)
#26 "Insufficient Resources" #26 "Insufficient Resources" #73 "No Resources available"
#88 "UE refuses"
#31 "Request rejected, unspecified" #31 "Activation rejected, unspecified" #94 "Request rejected"
#88 "UE refuses"
#41 "Semantic error in the TFT #41 "Semantic error in the TFT #74 "Semantic error in the TFT
#42 "Syntactical error in the TFT #42 "Syntactical error in the TFT #75 "Syntactical error in the TFT
#43 "Invalid EPS bearer identity" #43 "Unknown PDP Context" #64 "Context not found"
#88 "UE refuses"
#44 "Semantic errors in packet #44 "Semantic errors in packet #76 "Semantic errors in packet
filter(s)" filter(s)" filter(s)"
#45 "Syntactical error in packet #45 "Syntactical error in packet #77 "Syntactical error in packet
filter(s)" filter(s)" filter(s)"
#47 "PTI mismatch" NA #94 "Request rejected"
#88 "UE refuses"
NA #48 "Request rejected, Bearer Control #94 "Request rejected"
Mode violation" #88 "UE refuses"
#81 "Invalid PTI value" NA #94 "Request rejected"
#88 "UE refuses"
NOTE 2: When multiple GTPv2 Cause values are defined for a given NAS Cause value, any of those GTPv2 Cause
values may be sent to the SGW based on implementation choice.
ETSI
Table C.5: Mapping from S3/S16 to NAS Cause values – Rejection indication from MME/S4-SGSN
Reject indication from MME/S4- NAS ESM Cause to UE SM Cause to UE

SGSN to MME/S4-SGSN (NOTE 1, NOTE 2) (NOTE 1, NOTE 2)
over S3/S16
#117 "Target access restricted for
#15 "No suitable cells in tracking area", #15 "No suitable cells in tracking area",
the subscriber" or or
#13 "Roaming not allowed in this #13 "Roaming not allowed in this
tracking area", or tracking area", or
#12 "Tracking area not allowed" #12 "Tracking area not allowed"
NOTE 2: When multiple NAS Cause values are defined for a given GTP cause value, any of those NAS Cause values
may be sent to the UE based on implementation choice.
ETSI
Annex D (Informative):
GTP-C load and overload control mechanism
D.1 GTP-C interfaces not supporting Load Control

Load Control has been designed as a generic mechanism possibly applicable to any GTP-C node. However, for the
reasons clarified below, in the current release, Load Control is not supported for the following GTP-C based interfaces:
- S3, S10, S16 (limited GTP-C signalling traffic, to minimize impact to the MME/S4-SGSN);
- Sm, Sn (limited GTP-C signalling traffic, to avoid impact to the MBMS GW);
- Sv (limited GTP-C signalling traffic, to avoid impact to the legacy CS products);
- S101, S121 (to avoid impacts to the legacy HRPD products);
- Gn/Gp (to avoid impact to the legacy Gn-SGSN/GGSN products and GTPv1-C protocol).
D.2 GTP-C interfaces not supporting Overload Control

Overload Control has been designed as a generic mechanism possibly applicable to any GTP-C based interface and any
direction. However for the reasons clarified below, in the current release, Overload Control is not supported for the
following GTP-C based interfaces:
- S3, S10, S16 (see considerations below, to minimize impact to MME and S4-SGSN);
- most of the S3 traffic would remain internal to the combo-node with the deployment of combo-MME/S4-
SGSN nodes. The traffic over S10/S16 is also reduced with the deployment of MME and SGSN pools. It is
therefore not essential to throttle the traffic on these interfaces when an MME or S4-SGSN experiences
overload;
- throttling signalling on these interfaces resulting from a user's mobility (inter-MME/S4-SGSN TAU, RAU
and Handover) would result in bad end user's perception (handover failure, loss of PDN connections) and so
needs to be avoided as far as possible;
- an MME or S4-SGSN in overload may drop locally incoming RIM messages without causing GTP-C
retransmissions (although this may cause the RAN to retransmit the message).
- S11/S4 (from an MME/S4-SGSN to an SGW, with SGW as consumer; see consideration below);
- by allowing the SGW to throttle DDN requests for normal priority traffic, the overload control of the
messages originated by the SGW towards the MME/S4-SGSN is covered and hence, an SGW performing
overload control towards the MME/S4-SGSN using Overload Control Information would be redundant.
- S5/S8 (from a PGW to an SGW, with the SGW as a consumer; no signalling message, originated by the SGW
towards the PGW, that is identified as requiring overload control);
- Sm, Sn (no overload scenario identified, limited GTP-C traffic, to avoid impact to the MBMS GW);
- Sv (no overload scenario identified, to avoid impact to the legacy CS products);
- S101, S121 (no overload scenario identified, to avoid impact to the legacy HRPD products);
- Gn/Gp (to avoid impact to the legacy Gn-SGSN/GGSN products and GTPv1-C protocol);
ETSI
3GPP TS 29.274 version 13.4.0 Release 13 322 ETSI TS 129 274
74 V13.4.0 (2016-03)
D.3 "Loss" throttling al

algorithm
D.3.1 Example of possib

sible implementation
This subclause provides an example of a poss
ossible implementation of the "Loss" algorithm, amongst
st oother possible
methods.
It is possible to make use of a statistical losss ffunction (e.g., random selection of messages to throttle
le based
b on the
indicated percentage) to decide if the given m message can be sent or need to be throttled. For example,le, the source node
generates a random number between (0, 100) 0) for each message which is a potential candidate for thro
hrottling. To realize
10% throttling, messages with a random num mber 10 or less are throttled and hence this achieves apprproximately a 10%
reduction in the overall traffic. The actual traf
traffic reduction might vary slightly from the requested per
percentage, albeit by
an insignificant amount.
The algorithm can select certain messages to throttle in priority. For example, implementations can distinguish
d between
higher-priority and lower-priority messages,s, aand drop the lower-priority messages in favour of dropp
pping the higher
priority messages, as long as the total reductio
ction in traffic conforms to the requested reduction in effec
fect at the time. For
example, in the 50-50 distribution of high prio
priority and low priority messages, 20% reduction to low ppriority messages
and 0% reduction to high priority messagess nneed to be applied in order to achieve the effective reduc
uction in traffic by
10% towards the overloaded node.
D.4 Enforcement of ov
overload control between remote
te GTP-C
entities
D.4.1 Example of possib

sible implementation
This subclause provides an example of a poss
ossible implementation of the enforcement of overload control
con between
remote GTP-C entities, amongst other possibl
ible methods, considering the example network topologyy ddescribed in Figure
D.4.1-1.
Figure D
D.4.1-1: Example network topology
The source GTP-C entity can apply messagee tthrottling according to the maximum of the overload reduction
red metric
reported by the intermediate and target GTP--C entities, i.e. max (Intermediate_Overload-Metric, Targ
arget_Overload-
Metric), for each of the path between the sour
ource and the target GTP-C entities. Each path is considere
ered independently
whilst performing the message throttling.
Considering the following example overload

ad condition for the topology above:
Target_Overload-Metric = 30%
IntermediateA_Overload-Metric = 10%
0%
ETSI
IntermediateB_Overload-Metric = 20%
IntermediateC_Overload-Metric = 40%
Target_Terminated-Messages = 100
IntermediateA-Target_Messages = 20
IntermediateB-Target_Messages = 50
IntermediateC-Target_Messages = 30
the source GTP-C entity applies message throttling as follows:
Source-IntermediateA_Messages = 14 (message throttling of 30% applied)
Source-IntermediateB_Messages = 35 (message throttling of 30% applied)
Source-IntermediateC_Messages = 18 (message throttling of 40% applied)
Source-Target_Messages = 67 (the Target GTP-C entity receives 67 messages although it could have handled 70
messages in the overloaded condition).
ETSI
Annex E (Normative):
TWAN mapping table between GTPv2 S2a Cause and non-
3GPP access Cause values
The TWAN initiates session establishment requests or mobility management requests towards the PGW. If this
operation is not successful, there are several possible cause codes, which need to be mapped to the appropriate cause
codes over non-3GPP access to the UE.
The TWAN should map these cause codes as defined in Table E.1, Table E.2, Table E.3 and Table E.4.
ETSI
Table E.1: Mapping from GTPv2 S2a to non-3GPP access Cause values – Rejection indication from
PGW
Reject indication from WLCP Cause to UE for MCM Diameter Cause to 3GPP
PGW to TWAN over S2a AAA Server for SCM
#64 "Context not found" #54 "PDN connection does not FFS
(during UE initiated PDN exist"
connectivity request for
3GPP to non-3GPP
handover procedure)
#65 Invalid Message #30 "Request rejected by PDN #30 "Request rejected by PDN
Format GW" GW"
#67 "Invalid length" #30 "Request rejected by PDN #30 "Request rejected by PDN
GW" GW"
#68 "Service not #32 "Service option not #32 "Service option not
supported" supported" supported"
#69 "Mandatory IE #30 "Request rejected by PDN #30 "Request rejected by PDN
incorrect" GW" GW"
#70 "Mandatory IE missing" #30 "Request rejected by PDN #30 "Request rejected by PDN
GW" GW"
#72 "System Failure" #34 "Service option temporarily #34 "Service option temporarily
out of order" out of order"
#38 "Network Failure" #38 "Network Failure"
#30 "Request rejected by PDN #30 "Request rejected by PDN
GW" GW"
#73 "No Resources #34 "Service option temporarily #34 "Service option temporarily
available" out of order" out of order"
#78 "Missing or unknown # 27 "Missing or unknown # 27 "unknown APN"
APN" APN"
#83 "Preferred PDN type #32 "Service option not #32 "Service option not
not supported" supported" supported"
#50 "PDN type IPv4 only #50 "PDN type IPv4 only
allowed" allowed"
#51 "PDN type IPv6 only #51 "PDN type IPv6 only
allowed" allowed"
#84 "All dynamic #26 "Insufficient resources" #26 "Insufficient resources"
addresses are occupied"
#89 "Service denied" #30 "Request rejected by PDN #30 "Request rejected by PDN
GW" GW"
#31 "Request rejected, #31 "Request rejected,
unspecified" unspecified"
#91 "No memory available" #34 "Service option temporarily #34 "Service option temporarily
out of order" out of order"
#92 "User authentication FFS FFS
failed"
#93 "APN access denied – #33 "Requested service option #33 "Requested service option
no subscription" not subscribed" not subscribed"
# 27 "Missing or unknown # 27 "unknown APN"
APN"
#94 "Request rejected #30 "Request rejected by PDN #30 "Request rejected by PDN
(reason not specified)" GW" GW"
#100 "Remote peer not #34 "Service option temporarily #34 "Service option temporarily
responding" out of order" out of order"
#101 "Collision with FFS FFS
network initiated request"
#103 "Conditional IE #30 "Request rejected by PDN #30 "Request rejected by PDN
missing" GW" GW"
ETSI
#113 "APN Congestion" #26 "Insufficient resources" #26 "Insufficient resources"

#120 "GTP-C Entity
Congestion"
#116 "Multiple PDN #55 "Multiple PDN connections NA
connections for a given for a given APN not allowed"
APN not allowed"
#126 "Multiple accesses to #113 "Multiple accesses to a #113 "Multiple accesses to a
a PDN connection not PDN connection not allowed" PDN connection not allowed"
allowed"
NOTE 1: See 3GPP TS 24.244 [66] for WLCP causes.
NOTE 2: When multiple non-3GPP access cause values are defined for a given GTP cause
value, any of those cause values may be sent to the UE based on implementation
choice.
Table E.2: Mapping from GTPv2 S2a to non-3GPP access Cause values – Acceptance indication from
PGW
Acceptance indication from WLCP Cause to UE for MCM Diameter Cause to 3GPP AAA
PGW to TWAN over S2a Server for SCM
#18 "New PDN type due to #50 "PDN type IPv4 only FFS
network preference" allowed"
#51 "PDN type IPv6 only
allowed"
#19 "New PDN type due to #52 "single address bearers only FFS
single address bearer only" allowed"
NOTE 1: The actual WLCP cause sent to the UE depends on the allocated IP address type.
Table E.3: Mapping from GTPv2 S2a to WLCP Cause values – Indication in request from PGW
Indication in disconnection WLCP Cause to UE for MCM

message from PGW to TWAN over
S2a
#8 'Reactivation Requested' #39 'Reactivation requested'
#9 "PDN reconnection to this APN Implementation specific WLCP cause
disallowed" value indicating to the UE that the
(NOTE 1) APN is not currently available.
NOTE 1: In Delete Bearer Request during the PGW initiated bearer
deactivation procedure for the default bearer
Table E.4: Mapping from WLCP to GTP Cause values – Rejection indication from TWAN
WLCP Cause from UE Reject indication from TWAN to

PGW
#31 'request rejected, unspecified" #94 "Request rejected"
#88 "UE refuses"
NOTE 1: See 3GPP TS 24.244 [66] for WLCP causes.
NOTE 2: When multiple GTPv2 Cause values are defined for a given WLCP
Cause value, any of those GTPv2 Cause values may be sent to the
PGW based on implementation choice.
ETSI
Annex F (Informative):
Change History
Date TSG # TSG Doc CT4 Doc CR Rev Cat Subject/Comment Old New
2008-12 CT#42 CP-080717 V2.0.0 approved in CT#42 2.0.0 8.0.0
Delete Indirect Data Forwarding Tunnel
2009-03 CT#43 CP-090050 C4-090922 0001 2 C Request/Response 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090520 0003 1 C Relocation Cancel Req/Res 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090834 0004 2 C Path Failure 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090878 0005 4 F Sections 1 through 6 Editorial Clean-up 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090879 0006 2 C Delete Session and Delete Bearer messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090902 0008 2 C Update User Plane messages 8.0.0 8.1.0
Cleanup in path management and bearer
2009-03 CT#43 CP-090050 C4-090880 0017 2 B command messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090526 0018 1 C Create Session/Bearer Messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090901 0019 2 C Modify Bearer messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090991 0020 2 C IEs in CSFB related messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090570 0021 1 C Command Messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090939 0022 3 C Data Forwarding Info 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090970 0023 3 C Delete Bearer messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090941 0024 2 C Delete Session messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090574 0025 1 F Downlink Data Notification 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090942 0026 2 F Update Bearer messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090952 0027 2 C Secondary PDP Activation 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090874 0028 2 C Stop Paging 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090577 0030 1 F EPS Bearer Contexts Prioritization 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090875 0032 2 F Linked EPS Bearer ID 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090578 0034 1 F AMBR IE encoding 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090157 0035 - F Authentication Failure Cause Code 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090580 0040 1 F Forward SRNS Context Notification 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090581 0041 1 F F-TEID IE clarification 8.0.0 8.1.0
SGW Selection during TAU and corrections to
2009-03 CT#43 CP-090214 - 0043 4 F Grouped IEs 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090583 0043 1 F Identification Response algorithm information 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090798 0044 2 F IE Type ordering 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090945 0045 2 F Indication IE corrections 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090588 0048 1 F MM Context enhancements 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090590 0050 1 F Removal of Bearer ID List IE 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090591 0051 1 F Remove unused IP Address IEs 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090592 0052 1 F Selection Mode bits 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090593 0053 1 F Corrections to Trace Information IE 8.0.0 8.1.0
Trace Information IE to be included in S11 and
2009-03 CT#43 CP-090050 C4-090946 0054 2 F S5/S8 messages 8.0.0 8.1.0
Trace Session Activation/Deactivation when
2009-03 CT#43 CP-090050 C4-090947 0055 3 F UE is attached 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090691 0059 1 B New UE Time Zone IE Type 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090692 0060 1 C Release Access Bearers Request/Response 8.0.0 8.1.0
2009-03 CT#43 CP-090256 C4-090935 0061 3 B Piggybacking of Dedicated Bearer Messages 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090933 0063 4 C Finalizing GTPv2 Error Handling clause 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090598 0064 1 F GTPv2 clause 9 and 10 cleanup 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090977 0066 4 B RAN Information Relay message 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090975 0067 2 F Bearer QoS encoding 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090694 0068 1 F Modify Bearer Response 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090932 0075 3 C Location Change Reporting 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090976 0077 2 F Cleanup on Cause Values 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090811 0080 1 F Non-3GPP Requests in GTPv2 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090938 0082 3 F Support of IP address retrieval for ANRF 8.0.0 8.1.0
Support for error response for conflicting
2009-03 CT#43 CP-090050 C4-090814 0083 1 F resource request 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090817 0085 1 F Clarification of Target ID vs Cell ID 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090936 0089 2 F TEID Value of the GTP header 8.0.0 8.1.0
Header for the Format of the GTPv2-C
2009-03 CT#43 CP-090050 C4-090826 0093 3 B message 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090871 0094 3 C Finalization of Partial fault handling in GTPv2 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090822 0095 1 F MSISDN encoding 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090823 0096 1 F IMSI encoding 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090829 0097 1 C PMIP error code reservation 8.0.0 8.1.0
Removal of Comprehension Required from
2009-03 CT#43 CP-090050 C4-090549 0098 - F messages 7.3.1 to 7.3.13 8.0.0 8.1.0
ETSI
2009-03 CT#43 CP-090050 C4-090550 0099 - F Cause value for PGW not responding 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090551 0100 - F Traffic Aggregate Description IE encoding 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090980 0101 3 F Protocol Stack 8.0.0 8.1.0
2009-03 CT#43 CP-090050 C4-090831 0102 1 C Reliable delivery for EPC 8.0.0 8.1.0
Removal of reservation for message types of
2009-03 CT#43 CP-090050 C4-090915 0104 - F GTP-U 8.0.0 8.1.0
2009-03 CT#43 CP-090239 - 0105 1 F Essential correction to grouped IE type coding 8.0.0 8.1.0
2009-03 - - - - - - Some of the table formats corrected 8.1.0 8.1.1
2009-06 CT#44 0107 Suspend and Resume are also used for 8.1.1 8.2.0
CP-090288 C4-091020 - F 1xRTT CS Fallback
2009-06 CT#44 0108 Support for new cause code of "Unable to 8.1.1 8.2.0
page UE due to CSFB" in Downlink Data
CP-090288 C4-091459 1 F Notification Acknowledgement.
2009-06 CT#44 CP-090288 C4-091460 0109 1 F Corrections on GTPv2 for 1x IWS IP address 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091461 0110 1 F Clarification of Operation Indication (OI) 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091463 0111 1 F Usage of User Location Information (ULI) IE 8.1.1 8.2.0
2009-06 CT#44 0112 PGW S5/S8 IP Address in Context Response 8.1.1 8.2.0
CP-090288 C4-091465 1 F message
2009-06 CT#44 0114 Delete Indirect Data Forwarding Tunnel 8.1.1 8.2.0
CP-090288 C4-091471 1 F Response
2009-06 CT#44 CP-090288 C4-091537 0115 2 F Error_Handling. Withdrawn 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091473 0117 1 F PCO Extensions added to messages 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091474 0118 1 F Clarifications to message directions 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091103 0119 - F Removal of specification drafting hints 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091475 0120 1 F ISR related alignments 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091476 0122 1 F Clarifications to grouped IE usage 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091586 0125 2 F Clarification to Recovery IE type 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091478 0127 1 F Missing conditions 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091480 0128 1 F Clarification of ARP encoding 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091115 0129 - F Units for APN-AMBR 8.1.1 8.2.0
2009-06 CT#44 0131 Clarification of Mobile Equipment Identity IE 8.1.1 8.2.0
CP-090288 C4-091481 2 F encoding
2009-06 CT#44 CP-090288 C4-091120 0134 - F EPS Bearer Level TFT encoding 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091587 0136 2 F UE-initiated procedures with one bearer only 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091510 0137 2 F Combine UL and DL TFT IEs 8.1.1 8.2.0
2009-06 CT#44 0142 PGW S5/S8 IP Address and TEID for user 8.1.1 8.2.0
CP-090288 C4-091512 1 F plane
2009-06 CT#44 CP-090288 C4-091513 0143 1 F Transaction Identifier information element 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091515 0147 1 F Delete Bearer Request 8.1.1 8.2.0
2009-06 CT#44 0149 Modify Bearer Request for TAU without MME 8.1.1 8.2.0
CP-090288 C4-091516 2 F or SGW change
2009-06 CT#44 0150 Use of APN, PAA in Create Session Request, 8.1.1 8.2.0
and S5/S8-U PGW F-TEID in Create Session
CP-090288 C4-091538 2 F Response
2009-06 CT#44 CP-090288 C4-091540 0151 1 F Message table corrections 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091162 0153 - F Presence requirement for IEs in response 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091537 0154 2 F Offending IE in the Cause IE 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091541 0156 1 F Minor corrections 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091542 0157 1 F FQ-CSID corrections 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091167 0158 - F APN and FQDN encoding clarifications 8.1.1 8.2.0
2009-06 CT#44 0159 Removal of Trace Information IE from Update 8.1.1 8.2.0
CP-090288 C4-091168 - F Bearer Request
2009-06 CT#44 CP-090288 C4-091467 0160 1 F Corrections in PDN Connection group IE 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091543 0161 1 F Missing IEs in "Update Bearer Response" 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091548 0164 2 F PDN Type 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091549 0168 1 F IE corrections in Modify Bearer signalling 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091550 0169 2 F Create Session Request Clarification 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091202 0175 - F TEID in Detach Notification/ACK 8.1.1 8.2.0
2009-06 CT#44 0176 Condition of bearer context in Modify Bearer 8.1.1 8.2.0
CP-090288 C4-091203 - F messages
2009-06 CT#44 CP-090288 C4-091544 0177 1 F Delete Session Request granularity 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091205 0178 - F Deletion of IMSI in the Update Bearer Request 8.1.1 8.2.0
2009-06 CT#44 0180 Delete Session Request/Response and Delete 8.1.1 8.2.0
CP-090288 C4-091546 1 F Bearer Request
2009-06 CT#44 CP-090288 C4-091551 0181 1 F Detach Notification 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091234 0183 - F SGSN Info for Data Forwarding 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091462 0184 1 F Delete Session Request 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091561 0185 1 F APN AMBR clarification 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091552 0186 1 F Delete Bearer Request when ISR activated 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091553 0187 1 F Clarify the usage of the MS validated IE 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091557 0189 1 F UDP Source port and IP Source Address 8.1.1 8.2.0
ETSI
2009-06 CT#44 CP-090288 C4-091241 0190 - F Recovery IE 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091539 0192 1 F APN Information 8.1.1 8.2.0
2009-06 CT#44 CP-090500 - 0193 3 F Cause value 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091547 0195 1 F Cleanup indication 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091556 0196 1 F Cleanup the usage of some messages 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091545 0198 1 F Linked EPS Bearer ID 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091514 0199 1 F PCO parameter 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091558 0200 1 F PDP Context Activation 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091464 0201 1 F User Location Info 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091559 0202 2 F F-Cause IE correction 8.1.1 8.2.0
2009-06 CT#44 CP-090288 C4-091560 0206 1 F Message granularity 8.1.1 8.2.0
2009-06 CT#44 Bearer Context in the Modify Bearer 8.1.1 8.2.0
CP-090321 - 0209 - F Command
2009-06 CT#44 CP-090493 - 0210 1 F Sequence Number Extension 8.1.1 8.2.0
2009-06 CT#44 CP-090355 - 0212 - F Bearer Resource Command clarification 8.1.1 8.2.0
2009-06 CT#44 CP-090485 - 0213 1 F Piggybacked message clarifications 8.1.1 8.2.0
2009-06 CT#44 Corrections on handling Charging ID IE and 8.1.1 8.2.0
CP-090472 - 0214 1 F Charging Characteristics IE
2009-09 CT#45 CP-090533 C4-091625 0215 - F Usage of GTPv2-C Header 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-092004 0216 1 F Create Session Request and Response 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-092005 0217 1 F Cleanup Editors Note 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-092008 0218 1 F Message format and Type values 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-091630 0220 - F S16 Influence 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-092012 0222 1 F MM Context 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-091633 0223 - F F-Container 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-091635 0225 - F Change Reporting Action 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-092013 0226 1 F Procedure names 8.2.0 8.3.0
2009-09 CT#45 Changes to Create-Session-Request and 8.2.0 8.3.0
CP-090533 C4-092134 0228 3 F Create-Session-Response messages
2009-09 CT#45 CP-090533 C4-092017 0229 1 F Changes to Modify-Bearer-Response 8.2.0 8.3.0
2009-09 CT#45 CP-090533 C4-092014 0232 2 F Piggybacking Clarifications 8.2.0 8.3.0
2009-09 CT#45 Delete Bearer Request Cause value for ISR 8.2.0 8.3.0
CP-090533 C4-092018 0236 1 F deactivation
2009-09 CT#45 CP-090533 C4-092019 0237 2 F Modify Bearer Request Bearer Level QoS 8.2.0 8.3.0
2009-09 CT#45 Possible reject response Cause values in 8.2.0 8.3.0
CP-090533 C4-092020 0239 1 F GTPv2 message descriptions
2009-09 CT#45 SGW F-TEID for S1-U, S12 and S4 for User 8.2.0 8.3.0
CP-090533 C4-092002 0241 1 F Plane
2009-09 CT#45 Clarification on the usage of Version Not 8.2.0 8.3.0
CP-090533 C4-092103 0243 2 F Supported Indication
2009-09 CT#45 Clarifications on Sender-F-TEID for CP and 8.2.0 8.3.0
CP-090533 C4-092074 0244 1 F S3/S10/S16 CP IP Addr and TEID IEs
2009-09 CT#45 CP-090533 C4-092076 0245 1 F Cause Value in Echo Response 8.2.0 8.3.0
2009-09 CT#45 Corrections in ULI IE and PDN Connection IE 8.2.0 8.3.0
CP-090533 C4-091722 0246 - F definitions
2009-09 CT#45 GTPv2 Initial and Triggered Message 8.2.0 8.3.0
CP-090533 C4-092656 0247 3 F definition and Sequence Number handling
2009-09 CT#45 Missing Cause values in some message 8.2.0 8.3.0
CP-090533 C4-092078 0249 1 F descriptions
2009-09 CT#45 CP-090533 C4-092711 0250 4 F Add TAC to Target Identification IE 8.2.0 8.3.0
2009-09 CT#45 IMSI and Sender F-TEID in Create Indirect 8.2.0 8.3.0
CP-090533 C4-092081 0256 1 F Data Forwarding Tunnel Messages
2009-09 CT#45 CP-090534 C4-092009 0258 1 F Indication in Forward Relocation messages 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092082 0259 1 F Paging cause 8.2.0 8.3.0
2009-09 CT#45 Correlate the bearers in the Create Bearer 8.2.0 8.3.0
CP-090534 C4-091784 0260 - F Response
2009-09 CT#45 CP-090534 C4-092651 0261 3 F Cleanup cause values 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092104 0262 2 F Delete Bearer Failure Indication 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092083 0263 1 F Cleanup Modify Bearer Request 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092085 0264 2 F IEs in Response 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-091790 0266 - F CS Paging Indication 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092086 0267 2 F Serving Network 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092636 0268 3 F Service Handover support 8.2.0 8.3.0
2009-09 CT#45 Fix incorrect interface name, incorrect 8.2.0 8.3.0
CP-090534 C4-092105 0269 3 F reference and other misreading texts
2009-09 CT#45 Clarification on cause value for Downlink Data 8.2.0 8.3.0
CP-090534 C4-092106 0270 1 F Notification Failure Indication
2009-09 CT#45 Clarification on the Authentication Vector 8.2.0 8.3.0
CP-090534 C4-092710 0271 2 F handling
2009-09 CT#45 CP-090534 C4-092043 0276 1 F Clarification on Authentication Vector encoding 8.2.0 8.3.0
ETSI
2009-09 CT#45 Clarification on Error indication for EPC and 8.2.0 8.3.0
CP-090535 C4-092751 0278 5 F DT
2009-09 CT#45 CP-090534 C4-092112 0279 3 F Aligning MBR units to kbps 8.2.0 8.3.0
2009-09 CT#45 Clarification to the PGW's UP address in 8.2.0 8.3.0
CP-090534 C4-092108 0281 1 F Create Session Response
2009-09 CT#45 Modify Bearer procedure for X2 and S1 based 8.2.0 8.3.0
CP-090534 C4-092686 0282 4 F handovers
2009-09 CT#45 Add necessary cause value to the Update 8.2.0 8.3.0
CP-090534 C4-092109 0290 1 F Bearer Response
2009-09 CT#45 Update on Concurrent Running of Security 8.2.0 8.3.0
CP-090534 C4-092000 0292 - F Procedures
2009-09 CT#45 CP-090534 C4-092642 0295 2 F APN Restriction IE 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092644 0296 1 F Change Reporting IE 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092646 0297 1 F ULI Clarification 8.2.0 8.3.0
2009-09 CT#45 CP-090534 C4-092189 0301 - F Charging ID 8.2.0 8.3.0
2009-09 CT#45 Delete Indirect Data Forwarding Tunnel 8.2.0 8.3.0
CP-090534 C4-092647 0302 1 F Request/Response
2009-09 CT#45 CP-090535 C4-092648 0303 1 F SGW F-TEID 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092649 0304 1 F BCM 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092652 0307 3 F Charging Gateway Address 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092653 0308 1 F LBI Clarifications for Gn/Gp Handovers 8.2.0 8.3.0
2009-09 CT#45 Trace management messages and IE related 8.2.0 8.3.0
CP-090535 C4-092654 0309 1 F clarifications
2009-09 CT#45 CP-090535 C4-092655 0310 1 F Indirect Data Forwarding Tunnel clarifications 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092635 0311 2 F Concurrent Running of Security Procedures 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092657 0315 1 F Cause value corrections 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092659 0316 1 F Identification Response 8.2.0 8.3.0
2009-09 CT#45 NSAPI and EBI in Forward Relocation 8.2.0 8.3.0
CP-090535 C4-092677 0317 1 F Response
2009-09 CT#45 CP-090535 C4-092678 0318 1 F Cause in the CSFB related messages 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092650 0320 1 F Update Bearer Complete 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092679 0321 1 F PCO IE 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092368 0322 - F Cleanup Trace Management messages 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092369 0323 - F Cleanup section 5.3 and 8.12 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092680 0324 1 F APN AMBR in the Create Bearer Request 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092681 0325 1 F UDP Source Port Number 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092372 0326 - F Presence Requirments for grouped IE 8.2.0 8.3.0
2009-09 CT#45 Making PCO conditional for the Attach 8.2.0 8.3.0
CP-090535 C4-092709 0330 1 F procedure
2009-09 CT#45 CP-090535 C4-092388 0332 - F Echo usage alignment with stage 2 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092397 0334 - F Trace Depth per session 8.2.0 8.3.0
2009-09 CT#45 Backward compatibility requirements for 8.2.0 8.3.0
CP-090535 C4-092740 0335 4 F presence
2009-09 CT#45 CP-090535 C4-092712 0338 1 F ECGI encoding correction 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092713 0339 1 F Consistant PDN type setting 8.2.0 8.3.0
2009-09 CT#45 CP-090535 C4-092714 0340 1 F GTP Cause value usage 8.2.0 8.3.0
2009-09 CT#45 CP-090729 C4-092626 0341 1 F Partial failure handling alignment with stage 2 8.2.0 8.3.0
2009-09 CT#45 Partial failure handling for MME relocation w/o 8.2.0 8.3.0
CP-090729 C4-092738 0342 2 F SGW relocation
2009-09 CT#45 CP-090535 C4-092634 0346 1 F Security Specification for GTPV2-C 8.2.0 8.3.0
2009-09 CT#45 Avoiding Source Port Overlap between 8.2.0 8.3.0
CP-090535 C4-092715 0349 1 F GTPv2-C and GTPv2-C'
2009-09 CT#45 CP-090535 C4-092478 0350 - F Delete Bearer Command PCO removal 8.2.0 8.3.0
2009-09 CT#45 CP-090559 C4-092061 0253 2 B Scope of GTP-C protocol 8.2.0 9.0.0
2009-09 CT#45 CP-090559 C4-092603 0254 4 B MBMS session management messages 8.2.0 9.0.0
2009-09 CT#45 CP-090562 C4-091934 0285 1 C IMEI based GTP Changes 8.2.0 9.0.0
2009-09 CT#45 CP-090745 - 0286 4 B Unauthenticated IMSI for emergency in GTP 8.2.0 9.0.0
2009-09 CT#45 CP-090562 C4-092500 0343 1 B IMEI based Id in GTP messages 8.2.0 9.0.0
2009-09 CT#45 CP-090562 C4-092501 0344 1 B Unauthenticated IMSI in GTP messages 8.2.0 9.0.0
Editorial correction. Wrong style was used in 9.0.0 9.0.1
2009-10 CT#46 Paragraph character 7.1.3.
2009-12 CT#46 CP-090769 C4-093160 0356 1 A Selection Mode IE 9.0.1 9.1.0
2009-12 CT#46 CP-090798 C4-093288 0357 2 B PTP bearer fallback 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-092830 0359 - A Bearer QoS in Modify Bearer Request 9.0.1 9.1.0
2009-12 CT#46 CP-090769 C4-093705 0361 1 A Release Access Bearer Request 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-092834 0363 - A Bearer context in Create Session messages 9.0.1 9.1.0
ISRAI flag in the Forward Relocation Complete 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-092857 0365 - A Notification
Mapping between RAI, P-TMSI, P-TMSI 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-092861 0369 - A signature and GUTI
2009-12 CT#46 CP-090770 C4-093329 0371 1 A APN IE encoding 9.0.1 9.1.0
ETSI
Correction on the condition for resource 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093331 0373 1 A release of other CN node
2009-12 CT#46 CP-090970 - 0375 2 APN Restriction 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093335 0377 1 A Cause value "Invalid reply from remote peer" 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093337 0380 1 A Indication Flags in Delete Session Request 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093339 0382 1 A Suspend 9.0.1 9.1.0
Removal of forwarding Charging Gateway 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-092893 0386 A Address/Name to S4-SGSN
2009-12 CT#46 CP-090770 C4-092893 0388 2 A Charging ID in S4-SGSN 9.0.1 9.1.0
Correction of Message Direction for Create 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-092899 0390 - A Session Response
PPC (Prohibit Payload Compression) 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093345 0392 1 A alignment with Stage-2
UE TimeZone and ULI included in Bearer 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093397 0393 3 A Response messages
2009-12 CT#46 CP-090804 C4-094229 0395 4 B Support for CSG based charging 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093278 0397 3 A User Location Information 9.0.1 9.1.0
2009-12 CT#46 CP-090769 C4-094051 0399 2 A PDN type 9.0.1 9.1.0
Removal of ULI from Release Access Bearer 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093004 0403 - A Req
2009-12 CT#46 CP-090770 C4-093006 0405 - A Removal of NSAPI IE 9.0.1 9.1.0
2009-12 CT#46 CP-090770 C4-093270 0407 2 A Indication IE clarification 9.0.1 9.1.0
Addition of uplink, downlink F-TEIDs in Create 9.0.1 9.1.0
Indirect Data Forwarding Tunnel Request and
2009-12 CT#46 CP-090770 C4-093262 0409 3 A Response messages
CT#46 Clarifications on use of the Sender-F-TEID for 9.0.1 9.1.0
2009-12 CP-090770 C4-093351 0411 2 A CP in HO procedure
2009-12 CT#46 CP-090770 C4-093034 0417 - A Clarifications to MSISDN coding 9.0.1 9.1.0
CT#46 Enhanced handling of RFSP index at the 9.0.1 9.1.0
2009-12 CP-090769 C4-094038 0419 2 A SGSN/MME
2009-12 CT#46 CP-090769 C4-094040 0423 2 A TFT related error handling 9.0.1 9.1.0
CT#46 Essential correction to the Indirect Data 9.0.1 9.1.0
2009-12 CP-090769 C4-094036 0425 4 A Forwarding procedure
CT#46 Correcting misaligned IE presence type 9.0.1 9.1.0
2009-12 CP-090769 C4-094042 0434 - A statements
CT#46 Correcting PCO conditions in Modify Bearer 9.0.1 9.1.0
2009-12 CP-090769 C4-094044 0438 1 A Response
CT#46 Delete Indirect Data Forwarding Tunnel 9.0.1 9.1.0
2009-12 CP-090769 C4-094184 0442 2 A messages
CT#46 SRVCC - voice bearer handling in PS HO / 9.0.1 9.1.0
2009-12 CP-090777 C4-094094 0448 1 A DTM scenarios
2009-12 CT#46 CP-090975 - 0450 2 A NAS Count value 9.0.1 9.1.0
CT#46 Charging Characteristics value for active PDN 9.0.1 9.1.0
2009-12 CP-090769 C4-094049 0452 1 A connections
CT#46 eNodeB Cause and RANAP Cause 9.0.1 9.1.0
2009-12 CP-090786 C4-094071 0453 1 F corrections
2009-12 CT#46 CP-090769 C4-093647 0455 - A Change the NSAPI to EBI in the PFI IE 9.0.1 9.1.0
2009-12 CT#46 CP-090769 C4-093649 0457 - A Enhanced SRNS Relocation Procedure 9.0.1 9.1.0
2009-12 CT#46 CP-090769 C4-093651 0459 - A Forward Access Context Acknowledge 9.0.1 9.1.0
2009-12 CT#46 CP-090769 C4-093668 0461 - A Correct the message Modify Bearer Request 9.0.1 9.1.0
2009-12 CT#46 CP-090769 C4-094059 0471 1 A Cleanup Suspend Notification message 9.0.1 9.1.0
CT#46 Forward Relocation Request: Selected PLMN 9.0.1 9.1.0
2009-12 CP-090769 C4-094059 0475 1 A ID
CT#46 9.0.1 9.1.0
2009-12 CP-090770 C4-094074 0484 1 A Change Reporting Action
CT#47 Essential clarification to MME executed TAU 9.1.0 9.2.0
2010-03 CP-100021 C4-100767 0493 1 A procedure
2010-03 CT#47 CP-100022 C4-100972 0495 5 A Essential correction to the MM context IE type 9.1.0 9.2.0
2010-03 CT#47 Resolving ambiguity for Target Identification IE 9.1.0 9.2.0
CP-100021 C4-100142 0497 1 A coding
2010-03 CT#47 CP-100021 C4-100276 0504 A PCO 9.1.0 9.2.0
2010-03 CT#47 CP-100021 C4-100788 0506 1 A RFSP Index 9.1.0 9.2.0
2010-03 CT#47 Include CSG ID and CSG Membership 9.1.0 9.2.0
CP-100049 C4-100836 0508 1 B Indication in S3 and S10
2010-03 CT#47 CP-100035 C4-100970 0510 2 F Location change reporting in EPS 9.1.0 9.2.0
2010-03 CT#47 CP-100019 C4-100318 0512 A The encoding of APN IE 9.1.0 9.2.0
2010-03 CT#47 CP-100021 C4-100793 0514 1 A Indirect Data Forwarding 9.1.0 9.2.0
2010-03 CT#47 HSS/PGW initiated Bearer QoS Modification 9.1.0 9.2.0
CP-100021 C4-100800 0516 2 A procedure
2010-03 CT#47 CP-100022 C4-100856 0518 1 A APN IE description correction 9.1.0 9.2.0
2010-03 CT#47 CP-100022 C4-100960 0520 2 A P-TMSI Signature 9.1.0 9.2.0
ETSI
2010-03 CT#47 Corrections to the RAN Information 9.1.0 9.2.0
CP-100035 C4-100756 0521 1 F Management procedures
2010-03 CT#47 Source Identification for E-UTRAN to GERAN 9.1.0 9.2.0
CP-100021 C4-100396 0523 A handover
2010-03 CT#47 CP-100049 C4-100839 0524 1 B Handovers to HeNB cells 9.1.0 9.2.0
2010-03 CT#47 CP-100022 C4-100866 0530 1 A Granularity 9.1.0 9.2.0
2010-03 CT#47 CP-100021 C4-100720 0533 2 A Change Reporting Support Indicator 9.1.0 9.2.0
2010 CT#47 CP-100021 C4-100416 0535 A MM Context IE type correction 9.1.0 9.2.0
2010-03 CT#47 Removal of TEIDs for PS voice bearer UP in 9.1.0 9.2.0
CP-100027 C4-100992 0537 2 A Bearer Context for SRVCC
2010-03 CT#47 Correction on the presence condition of 9.1.0 9.2.0
CP-100021 C4-100420 0539 A Charging ID IE on S4
2010-03 CT#47 CP-100035 C4-100995 0541 3 F Suspend 9.1.0 9.2.0
2010-03 CT#47 Modify Octets Sequence Number of RAB 9.1.0 9.2.0
CP-100022 C4-100876 0548 1 A Context IE
2010-03 CT#47 Revive the cause value "User Authentication 9.1.0 9.2.0
CP-100022 C4-100878 0550 1 A Failed" in the Create Session Response
2010-03 CT#47 CP-100035 C4-100883 0554 1 F Fix PCO handling by defining it per bearer 9.1.0 9.2.0
2010 CT#47 CP-100022 C4-100974 0556 2 A Fix PDN Connection Grouped Type 9.1.0 9.2.0
2010-03 CT#47 Correction on the down link notification failure 9.1.0 9.2.0
CP-100022 C4-100976 0558 2 A procedure
2010-03 CT#47 CP-100022 C4-100979 0565 2 A Correction of the presence condtion of IEs 9.1.0 9.2.0
2010-03 CT#47 Figure number, Information element and 9.1.0 9.2.0
CP-100021 C4-100784 0567 1 A message usage
2010-03 CT#47 2G related parameters in the Forward 9.1.0 9.2.0
CP-100022 C4-100981 0569 2 A Relocation Request and Context Response
2010-03 CT#47 Essential correction to the Create Bearer 9.1.0 9.2.0
CP-100022 C4-100983 0577 2 A Request message
2010-03 CT#47 CP-100022 C4-100906 0581 1 A Essential correction to FTEID IE 9.1.0 9.2.0
2010-03 CT#47 Essential correction to Modify Bearer Request 9.1.0 9.2.0
CP-100022 C4-100985 0583 2 A for non-3GPP to 3GPP handover
2010-03 CT#47 Removal of unncessary cause "Unexpected 9.1.0 9.2.0
CP-100021 C4-100601 0585 A repeated IE"
2010-03 CT#47 Removal of indirect uplink data forwarding 9.1.0 9.2.0
CP-100022 C4-100913 0587 1 A from Inter RAT handovers
2010-03 CT#47 CP-100021 C4-100778 0591 1 A Trace alignment with TS 32.422 9.1.0 9.2.0
2010-06 CT#48 CP-100266 C4-101479 0599 1 A Essential corrections to M-TMSI mapping 9.2.0 9.3.0
2010-06 CT#48 CP-100266 C4-101580 0603 3 A Change Notification 9.2.0 9.3.0
2010-06 CT#48 Fix missing conditional description for IEs in 9.2.0 9.3.0
CP-100266 C4-101480 0605 1 F the context response message
2010-06 CT#48 CP-100266 C4-101486 0614 1 A Change Reporting Support Indication 9.2.0 9.3.0
2010-06 CT#48 CP-100266 C4-101489 0618 1 A Handover/Relocation cancel procedure 9.2.0 9.3.0
2010-06 CT#48 CP-100266 C4-101491 0624 1 A ULI in the Modify Bearer Request message 9.2.0 9.3.0
2010-06 CT#48 CP-100266 C4-101495 0626 1 A MM context IE encoding 9.2.0 9.3.0
2010-06 CT#48 CP-100266 C4-101583 0635 2 A MBR in handover from non-3GPP to 3GPP 9.2.0 9.3.0
2010-06 CT#48 CP-100266 C4-101537 0637 1 F Suspend over S16 9.2.0 9.3.0
2010-06 CT#48 Adding Service indicator to CS Paging 9.2.0 9.3.0
CP-100266 C4-101504 0642 1 A Indication
2010-06 CT#48 CP-100266 C4-101599 0647 3 A Fallback to GTPv1 9.2.0 9.3.0
2010-06 CT#48 Essential correction to ULI IE condition in 9.2.0 9.3.0
CP-100266 C4-101553 0650 2 A Modify Bearer Request message
2010-06 CT#48 CP-100266 C4-101555 0657 1 A TEID in Change Notification 9.2.0 9.3.0
2010-06 CT#48 CP-100266 C4-101558 0659 1 A Charging ID 9.2.0 9.3.0
2010-06 CT#48 Alert MME Notification / UE Activity 9.2.0 9.3.0
CP-100266 C4-101291 0664 A Notification procedure on S3 interface
2010-06 CT#48 CP-100281 C4-101585 0540 4 F Leave CSG Cell indication 9.2.0 9.3.0
2010-06 CT#48 CP-100281 C4-101484 0609 1 F Use of Rejection Cause values 9.2.0 9.3.0
2010-06 CT#48 Flow QoS in the Bearer Resource Command 9.2.0 9.3.0
CP-100281 C4-101597 0616 2 F message
2010-06 CT#48 Correction to the reference in Create indirect 9.2.0 9.3.0
CP-100281 C4-101498 0633 1 F DF Tunnel Request
2010-06 CT#48 CP-100281 C4-101459 0638 1 F Removal of FFS 9.2.0 9.3.0
2010-06 CT#48 CP-100281 C4-101465 0673 1 F Message type table 9.2.0 9.3.0
2010-06 CT#48 CP-100281 C4-101609 0639 3 F Implicit resume 9.2.0 9.3.0
2010-06 CT#48 CP-100281 C4-101463 0670 1 F Cause IE type 9.2.0 9.3.0
2010-06 CT#48 CP-100281 C4-101593 0667 2 F Clarifications to redundant IEs 9.2.0 9.3.0
2010-06 CT#48 CP-100281 C4-101462 0669 1 F EBI value range and coding 9.2.0 9.3.0
2010-06 CT#48 Cause IE enhacements to distinguish errors in 9.2.0 9.3.0
the message level IE versus errors in the
CP-100281 C4-101461 0651 1 F grouped IE within the message
2010-06 CT#48 CP-100281 C4-101464 0672 1 F Bearer Resource Command usage 9.2.0 9.3.0
2010-06 CT#48 CP-100287 C4-101259 0654 F Sn-U SGSN F-TEID 9.2.0 9.3.0
ETSI
2010-06 CT#48 Allocation and Retention Priority for MBMS E- 9.2.0 9.3.0
CP-100287 C4-101608 0640 2 F RAB
2010-06 CT#48 Handling of Create Session Request message 9.2.0 9.3.0
CP-100266 C4-101601 0678 1 F on TEID 0 for existing PDN connection
2010-06 CT#48 Essential correction for the Initial Attach 9.2.0 9.3.0
CP-100298 0680 A procedure
2010-06 CT#48 Transferring of UE's usage setting and voice 9.2.0 9.3.0
CP-100276 C4-101157 0612 F capability between CN nodes
2010-06 CT#48 Clarifying the bearers to be deactivated on the 9.2.0 9.3.0
CP-100408 0544 6 F S5/S8 interface
2010-09 CT#49 Fix Sudden disconnection after the inter RAT 9.3.0 9.4.0
CP-100452 C4-101932 0607 5 F MM attempt
2010-09 CT#49 CP-100445 C4-101921 0630 4 A IP Address IE clarification 9.3.0 9.4.0
2010-09 CT#49 CP-100451 C4-101926 0681 2 F Serving Network semantics 9.3.0 9.4.0
2010-09 CT#49 CP-100444 C4-101678 0685 A Originating Node 9.3.0 9.4.0
2010-09 CT#49 CP-100444 C4-101876 0687 1 A Condition of ISRAI Flag 9.3.0 9.4.0
2010-09 CT#49 PDN Connection for Subscription Data 9.3.0 9.4.0
CP-100444 C4-101878 0689 1 A Change
2010-09 CT#49 CP-100580 C4-102309 0690 4 F Clarification for Create Session Response 9.3.0 9.4.0
2010-09 CT#49 CP-100452 C4-101922 0693 2 F An exception to use GTPv2 9.3.0 9.4.0
2010-09 CT#49 IEs to be included in rejection response 9.3.0 9.4.0
CP-100452 C4-101713 0694 F messages
2010-09 CT#49 CP-100452 C4-101927 0695 2 F Ambiguity for encoding MBR/GBR 9.3.0 9.4.0
2010-09 CT#49 CP-100452 C4-101715 0696 F Wrong reference to DRX parameter 9.3.0 9.4.0
2010-09 CT#49 CP-100452 C4-101716 0697 F Selection Mode 9.3.0 9.4.0
2010-09 CT#49 CP-100452 C4-101930 0701 2 F Stop CSG Information Reporting 9.3.0 9.4.0
2010-09 CT#49 Create Session Request/Response and 9.3.0 9.4.0
Modify Bearer Request/Response for RAU
CP-100452 C4-101747 0702 F procedure
2010-09 CT#49 CP-100452 C4-101748 0703 F Suspend message on S3 interface 9.3.0 9.4.0
2010-09 CT#49 CP-100445 C4-101884 0705 1 A Cause value in Detach Notification 9.3.0 9.4.0
2010-09 CT#49 CP-100445 C4-101886 0707 1 A S1 based handover cancel 9.3.0 9.4.0
2010-09 CT#49 CP-100445 C4-101904 0709 1 A Used NAS integrity protection algorithm values 9.3.0 9.4.0
2010-09 CT#49 CP-100452 C4-101923 0711 2 F TAU with Active Flag 9.3.0 9.4.0
2010-09 CT#49 CP-100452 C4-101905 0716 1 F Trace Report File LDNs 9.3.0 9.4.0
2010-09 CT#49 CP-100445 C4-101891 0718 1 A Change Notification Response 9.3.0 9.4.0
2010-09 CT#49 Presence rules and error handling for 9.3.0 9.4.0
CP-100451 C4-102319 0723 1 F embedded IEs
2010-09 CT#49 CP-100451 C4-102305 0724 1 F Dual Address Bearer Flag 9.3.0 9.4.0
2010-09 CT#49 Rejecting the dedicated bearer related 9.3.0 9.4.0
CP-100451 C4-102306 0726 1 F procedure from MME to SGW and PGW
2010-09 CT#49 Correction to condition of sending Context 9.3.0 9.4.0
CP-100636 - 0727 2 F Acknowledge message
2010-09 CT#49 Clarification to the OI flag usage in Delete 9.3.0 9.4.0
CP-100451 C4-102310 0729 2 F Session Request
2010-09 CT#49 CP-100451 C4-102320 0732 1 F Correcting non-existent Cause value 9.3.0 9.4.0
2010-09 CT#49 CP-100444 C4-102324 0736 1 A Resume messages 9.3.0 9.4.0
2010-09 CT#49 CP-100444 C4-102318 0738 1 A LAI field 9.3.0 9.4.0
2010-09 CT#49 CP-100444 C4-102326 0740 1 A P-TMSI Signature 9.3.0 9.4.0
2010-09 CT#49 CP-100453 C4-102384 0744 2 F Change Reporting Support Indication 9.3.0 9.4.0
2010-09 CT#49 CP-100451 C4-102353 0745 1 F Error handling 9.3.0 9.4.0
2010-09 CT#49 CP-100451 C4-102354 0746 1 F Flow QoS IE 9.3.0 9.4.0
2010-09 CT#49 PDN Connection for Subscription Data 9.3.0 9.4.0
CP-100444 C4-102329 0748 1 A Change
2010-09 CT#49 CP-100444 C4-102331 0750 1 A E-UTRAN to HRPD handover 9.3.0 9.4.0
2010-09 CT#49 Correcting type value of the MBMS Session 9.3.0 9.4.0
CP-100451 C4-102208 0751 F Start Response message
2010-09 CT#49 CP-100451 C4-102229 0754 F GTP protocol errors 9.3.0 9.4.0
2010-09 CT#49 Essential Clarification in Forward Relocation 9.3.0 9.4.0
CP-100451 C4-102357 0755 1 F Response message
2010-09 CT#49 CP-100469 C4-102302 0662 4 B New Modify Access Bearers procedure 9.4.0 10.0.0
2010-09 CT#49 Notification of supported features between 9.4.0 10.0.0
CP-100469 C4-102382 0698 6 B peer GTP-C entities
2010-09 CT#49 CP-100469 C4-102300 0734 1 B Length of IPv6 Prefix 9.4.0 10.0.0
2010-12 CT#50 OI flag in Delete Session Request alignment 10.0.0 10.1.0
CP-100695 C4-102766 0758 1 F with stage
2010-12 CT#50 CP-100695 C4-102836 0762 3 B ISR in Delete Bearer Request 10.0.0 10.1.0
2010-12 CT#50 CP-100695 C4-103277 0787 4 B PGW Restart Notification 10.0.0 10.1.0
2010-12 CT#50 Feature definition for the Modify Access 10.0.0 10.1.0
CP-100695 C4-102912 0798 2 F Bearers procedure
2010-12 CT#50 Modify Access Bearers procedure during Inter- 10.0.0 10.1.0
CP-100695 C4-102771 0799 1 F MME Intra-SGW TAU
ETSI
2010-12 CT#50 Clarifications to Failure Indication type of 10.0.0 10.1.0
CP-100695 C4-103274 0812 1 F messages
2010-12 CT#50 EPS Bearer ID in Downlink Data Notification 10.0.0 10.1.0
CP-100695 C4-103362 0817 2 B message
2010-12 CT#50 CP-100695 C4-103276 0818 1 F Clarifying possible cause value sets 10.0.0 10.1.0
2010-12 CT#50 CP-100695 C4-103343 0823 2 F SGSN Failure handling 10.0.0 10.1.0
2010-12 CT#50 CP-100695 C4-103283 0835 1 F Handover Indication 10.0.0 10.1.0
2010-12 CT#50 CP-100695 C4-103288 0842 1 F Cause values for Delete Bearer Request 10.0.0 10.1.0
2010-12 CT#50 MME/SGSN overload control by throttling of 10.0.0 10.1.0
CP-100688 C4-103315 0848 2 B DL low priority traffic
2010-12 CT#50 CP-100675 C4-102779 0773 1 A Suspend and Resume procedure 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-102781 0775 1 A Range for BSSGP Cause 10.0.0 10.1.0
2010-12 CT#50 RAT Type in the Modify Bearer Request 10.0.0 10.1.0
CP-100675 C4-102783 0777 1 A message
2010-12 CT#50 CP-100675 C4-102514 0781 - A ISR for SGW 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-102787 0783 1 A ISR in the Detach procedure 10.0.0 10.1.0
2010-12 CT#50 Missing Cause Code mapping for IRAT 10.0.0 10.1.0
CP-100675 C4-102789 0789 1 A Handover between GERAN and EUTRAN
2010-12 CT#50 CP-100675 C4-102556 0794 - A Voice bearer flag 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-102794 0801 1 A MBMS corrections 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-103238 0821 1 A CSG Reporting 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-102938 0825 - A Target Identification 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-103322 0830 2 A Reporting UE Time Zone changes 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-103249 0838 1 A Essential correction for UE Timezone reporting 10.0.0 10.1.0
2010-12 CT#50 CP-100675 C4-103331 0846 2 A ISR activated flag 10.0.0 10.1.0
2010-12 CT#50 Determination of type of source node during 10.0.0 10.1.0
CP-100672 C4-103294 0851 1 F TAU/RAU
2010-12 CT#50 Essential correction to Create Indirect Data 10.0.0 10.1.0
CP-100674 C4-102775 0765 1 A Forwarding Tunnel Response
2010-12 CT#50 GTP-C Information Elements for GTP based 10.0.0 10.1.0
CP-100686 C4-102796 0767 1 B S2b interface
2010-12 CT#50 CP-100686 C4-102539 0786 - B Delete PDN Connection Set 10.0.0 10.1.0
2010-12 CT#50 CP-100686 C4-102560 0796 - B Addition of GTP over S2b to clauses 1 to 6 10.0.0 10.1.0
2010-12 CT#50 Create Session Request/Response & Create 10.0.0 10.1.0
CP-100686 C4-103135 0797 3 B Bearer Request/Response
2010-12 CT#50 CP-100686 C4-102599 0802 - B Delete Session and Bearer messages 10.0.0 10.1.0
2010-12 CT#50 Modify Bearer Command/Failure Indication 10.0.0 10.1.0
CP-100686 C4-102629 0804 - B and Update Bearer Req/Rsp
2010-12 CT#50 Trace Session Activation/Deactivation for 10.0.0 10.1.0
CP-100686 C4-102650 0807 - B GTP-S2b
2010-12 CT#50 Handling of Create Session Request message 10.0.0 10.1.0
CP-100686 C4-103300 0839 1 B on header TEID = 0
2010-12 CT#50 Downlink data notification information for MPS 10.0.0 10.1.0
CP-100687 C4-102928 0769 2 B services
2010-12 CT#50 CP-100667 C4-102970 0828 - A UE Time Zone adjustments 10.0.0 10.1.0
2010-12 CT#50 CP-100669 C4-103340 0816 2 F Essential alignment with PMIP spec 10.0.0 10.1.0
2011-03 CT#51 CP-110064 C4-110875 0921 1 B Data Delay Notification 10.1.0 10.2.0
2011-03 CT#51 CP-110064 C4-110585 0916 - F Clean up with GTP-C Information Elements 10.1.0 10.2.0
2011-03 CT#51 Inclusion of Node Type in DDN Failure 10.1.0 10.2.0
CP-110064 C4-110831 0911 1 F Indication when the ISR is active
2011-03 CT#51 CP-110064 C4-110828 0897 1 F Create Session Response 10.1.0 10.2.0
2011-03 CT#51 CP-110064 C4-110479 0896 - F UE Network Capability IE 10.1.0 10.2.0
2011-03 CT#51 Adding "Initial", "Triggered" and "Initial or 10.1.0 10.2.0
triggered by a Command" attributes to the
CP-110064 C4-110955 0895 2 F messages in table 6.1
2011-03 CT#51 CP-110064 C4-110826 0894 1 D Adding a separate subclause for TEID=0 10.1.0 10.2.0
2011-03 CT#51 Removing optional Cause IE from Echo 10.1.0 10.2.0
CP-110064 C4-110825 0893 1 F Response
2011-03 CT#51 CP-110064 C4-110830 0875 2 F RAT type clarification for S4-SGSN 10.1.0 10.2.0
2011-03 CT#51 Essential correction to the table NOTE for the 10.1.0 10.2.0
CP-110064 C4-110331 0874 1 F Create Session Response message
2011-03 CT#51 CP-110064 C4-110369 0872 1 F Error Indication for SGW 10.1.0 10.2.0
2011-03 CT#51 CP-110064 C4-110257 0871 1 D Cleanup for GTPv2 10.1.0 10.2.0
2011-03 CT#51 CP-110064 C4-110392 0870 2 F RAT Type in Modify Access Bearers Request 10.1.0 10.2.0
2011-03 CT#51 CP-110064 C4-110112 0869 - F Bearer context in Modify Bearer Request 10.1.0 10.2.0
2011-03 CT#51 S1-U eNodeB F-TEID IE in the Modify Access 10.1.0 10.2.0
CP-110064 C4-110062 0860 - F Bearers Request
2011-03 CT#51 CP-110064 C4-110322 0855 1 F Correction for VNSI 10.1.0 10.2.0
2011-03 CT#51 CP-110064 C4-110882 0844 6 F Serving Network IE 10.1.0 10.2.0
2011-03 CT#51 CP-110061 C4-110548 0856 2 B APN based congestion control 10.1.0 10.2.0
2011-03 CT#51 CP-110061 C4-110310 0858 1 B Low access priority indicator 10.1.0 10.2.0
2011-03 CT#51 CP-110060 C4-110348 0859 1 B EBI and ARP IEs in Downlink Data Notification 10.1.0 10.2.0
ETSI
2011-03 CT#51 Protocol Configuration Options (PCO) in 10.1.0 10.2.0
CP-110049 C4-110994 0918 2 A Delete Bearer Response
2011-03 CT#51 UE Time Zone condition Delete Session 10.1.0 10.2.0
CP-110049 C4-110889 0901 1 A Request
2011-03 CT#51 CP-110049 C4-10971 0889 3 A Subscribed UE-AMBR in mobility procedure 10.1.0 10.2.0
2011-03 CT#51 Essential correction to the fallback to GTPv1 10.1.0 10.2.0
CP-110049 C4-110990 0884 5 A feature
2011-03 CT#51 RAT Type in the Modify bearer request 10.1.0 10.2.0
CP-110049 C4-110333 0881 1 A message
2011-03 CT#51 Missed procedures for the Delete Session 10.1.0 10.2.0
CP-110049 C4-110170 0879 - A Request and Response messages
2011-03 CT#51 CP-110049 C4-110330 0866 1 A Correction to passing of LDN 10.1.0 10.2.0
2011-03 CT#51 CP-110049 C4-110074 0862 - A S103 resource release 10.1.0 10.2.0
2011-03 CT#51 Essential correction to the to GTPv2 cause 10.1.0 10.2.0
CP-110049 C4-110186 0886 - A table
2011-03 CT#51 Essential correction to the encoding of Target 10.1.0 10.2.0
CP-110042 C4-110979 0914 1 A RNC-ID
2011-03 CT#51 CP-110056 C4-111009 0887 5 B Unsupported Bearer Handling for LIPA 10.1.0 10.2.0
2011-03 CT#51 CP-110083 C4-110952 0892 3 B Adding IMSI to DDN 10.1.0 10.2.0
2011-03 CT#51 CP-110053 C4-110824 0899 1 A Temporary Mobile Group Identity 10.1.0 10.2.0
2011-03 CT#51 Correcting IE Type for Bearer QoS IE from 10.1.0 10.2.0
CP-110042 C4-110365 0867 1 A Variable to Extendable
2011-03 CT#51 UE Time Zone condition in Modify Bearer 10.1.0 10.2.0
CP-110266 - 0903 2 A Request
2011-03 CT#51 Serving network in the Create Session 10.1.0 10.2.0
CP-110059 C4-110583 0915 - B Request message
2011-03 CT#51 CP-110072 C4-110887 0923 - B CS BIT to be available for initial message 10.1.0 10.2.0
2011-05 Editorial correction in section 7.10 because of 10.2.0 10.2.1
misimplentation of CT#51 agreed CR C4-
110990
2011-06 CT#52 Mapping of ASN.1/PER parameters to GTPv2 10.2.1 10.3.0
CP-110355 C4-111629 0927 2 A IEs
2011-06 CT#52 CP-110355 C4-111630 0940 3 F Downlink Data Notification for S4 10.2.1 10.3.0
2011-06 CT#52 CP-110355 C4-111551 0964 1 A IE Type Extendable Corrections 10.2.1 10.3.0
2011-06 CT#52 Fix SRVCC related data transfer between 10.2.1 10.3.0
CP-110366 C4-111596 0930 2 A MMEs/SGSNs
2011-06 CT#52 UE Time Zone IE in Delete Session Request 10.2.1 10.3.0
CP-110366 C4-111529 0932 1 A message
2011-06 CT#52 CP-110366 C4-111409 0943 1 A Higher bitrates than 16 Mbps flag 10.2.1 10.3.0
2011-06 CT#52 CP-110366 C4-111545 0953 1 A Temporary Rejection Cause 10.2.1 10.3.0
2011-06 CT#52 CP-110366 C4-111556 0958 1 A Cause IE in DDN message 10.2.1 10.3.0
2011-06 CT#52 Alignment with stage 2 for EPC node restart 10.2.1 10.3.0
CP-110378 C4-111656 0928 2 B with active ISR
2011-06 CT#52 CP-110374 C4-111434 0924 1 F Setting a sequence number in a Command 10.2.1 10.3.0
2011-06 CT#52 CP-110374 C4-111487 0941 1 F Clarification for Create Session Response 10.2.1 10.3.0
2011-06 CT#52 CP-110374 C4-111488 0944 2 F Max MBR/APN-AMBR 10.2.1 10.3.0
2011-06 CT#52 CP-110374 C4-111613 0947 3 F Inactive Emergency PDN Handling 10.2.1 10.3.0
2011-06 CT#52 CP-110374 C4-111236 0948 B ARP supporting on M3 interface for MBMS 10.2.1 10.3.0
2011-06 CT#52 CP-110374 C4-111237 0949 F Downlink Data Notification message 10.2.1 10.3.0
2011 CT#52 CP-110374 C4-111495 0950 1 F Serving Network 10.2.1 10.3.0
2011-06 CT#52 CP-110374 C4-111593 0956 2 F Serving Network IE in Modify Bearer Request 10.2.1 10.3.0
2011-06 CT#52 LAPI during UE initiated bearer resource 10.2.1 10.3.0
CP-110369 C4-111164 0945 B allocation / modification procedures
2011-08 Editorial correction in section 7.10 because of 10.3.0 10.3.1
misimplentation of CT#51 agreed CR C4-
110990
2011-09 CT#53 CP-110721 - 0969 1 A Additional MM context for SRVCC 10.3.1 10.4.0
2011-09 CT#53 Condition for sending Cause IE with DBReq 10.3.1 10.4.0
CP-110557 C4-112158 0977 1 A during a HO from 3GPP to non-3GPP
2011-09 CT#53 CP-110557 C4-112160 0986 1 A Essential Clarification for SGSN pool 10.3.1 10.4.0
2011-09 CT#53 Essential correction to handling of EPDN 10.3.1 10.4.0
CP-110557 C4-112162 0994 1 A session for UICCless UE
2011-09 CT#53 Correction to ULI and UCI IE inclusion 10.3.1 10.4.0
CP-110557 C4-112169 0996 1 A condition in Change Notification Req
2011-09 CT#53 Correction to header TEID of Suspend 10.3.1 10.4.0
CP-110557 C4-112191 1000 1 A Notification over S3/S16
2011-09 CT#53 Extended IE handling when received fields are 10.3.1 10.4.0
CP-110557 C4-112195 1002 1 A less than expected fields
2011-09 CT#53 CP-110557 C4-112199 1016 1 A Cause Code for DDN 10.3.1 10.4.0
2011-09 CT#53 CP-110574 C4-112225 0975 3 F MDT configuration information 10.3.1 10.4.0
2011-09 CT#53 Correction to Create Session Response LDN 10.3.1 10.4.0
CP-110567 C4-111754 0980 F IEs
ETSI
2011-09 CT#53 CP-110567 C4-112204 0982 2 F IP address parameter 10.3.1 10.4.0
2011-09 CT#53 CP-110567 C4-112136 0967 1 F Signalling path failure handling 10.3.1 10.4.0
2011-09 CT#53 CP-110567 C4-112145 0983 1 F Node Type 10.3.1 10.4.0
2011-09 CT#53 CP-110567 C4-112146 0987 1 F Clarification for Context Not Found 10.3.1 10.4.0
2011-09 CT#53 Recovery IE in MBMS Session Stop Response 10.3.1 10.4.0
CP-110567 C4-112147 0988 1 F message
2011-09 CT#53 Removal of PCO from Failed Bearer Context 10.3.1 10.4.0
CP-110567 C4-111839 1001 F of Delete Bearer Request
2011-09 CT#53 CP-110567 C4-111906 1006 F Downlink Data Notification for S4 10.3.1 10.4.0
2011-09 CT#53 CP-110557 C4-112193 1010 1 F MEI in Modify Bearer Request 10.3.1 10.4.0
2011-09 CT#53 CP-110577 C4-112130 0972 1 F OI flag in Delete Session Request 10.4.0 11.0.0
2011-09 CT#53 CP-110577 C4-112131 0973 1 F Clarification to DAF PAA usage 10.4.0 11.0.0
2011-09 CT#53 CP-110577 C4-111715 0974 F Correcting Port Number IE type definition 10.4.0 11.0.0
2011-09 CT#53 Add vSRVCC updates to the GTP based 10.4.0 11.0.0
CP-110584 C4-112231 0989 3 B interfaces
2011-09 CT#53 Clarification on the Bearer Contexts to be 10.4.0 11.0.0
removed IE in Modify Access Bearers Request
CP-110577 C4-112132 0990 1 F message
2011-09 CR 0914r1 title in history table corrected as in 11.0.0 11.0.1
CR database.
2011-12 CT#54 CP-110810 C4-112268 1026 F Delete Session Response 11.0.1 11.1.0
2011-12 CT#54 CP-110810 C4-112506 1037 1 F Bearer Resource Command 11.0.1 11.1.0
2011-12 CT#54 Clarification on the length restriction of PCO, 11.0.1 11.1.0
CP-110810 C4-112318 1049 F TFT IE
2011-12 CT#54 CP-110810 C4-112462 1035 1 F Correction on SGW-FQ-CSID 11.0.1 11.1.0
2011-12 CT#54 Correction to Downlink Data Notification 11.0.1 11.1.0
CP-110790 C4-112551 1051 3 A message due to control plane signalling
2011-12 CT#54 CP-110790 C4-112547 1048 2 A MBMS IP Multicast Distribution IE 11.0.1 11.1.0
2011-12 CT#54 Defining the fixed number of octets for 11.0.1 11.1.0
CP-110784 C4-112486 1054 2 A extendable IEs
2011-12 CT#54 CP-110790 C4-112363 1063 A Delete Session Request granularity 11.0.1 11.1.0
2011-12 CT#54 Essential correction to the TAD IE inclusion in 11.0.1 11.1.0
CP-110782 C4-112523 1058 2 A Bearer Resource Command over S4
2011-12 CT#54 Fix inconsistency within the specification for 11.0.1 11.1.0
CP-110810 C4-112515 1059 2 F GTP version handling
2011-12 CT#54 CP-110810 C4-112298 1036 F IE conditions in some message 11.0.1 11.1.0
2011-12 CT#54 CP-110790 C4-112498 1065 1 A Indirect Data Forwarding messages 11.0.1 11.1.0
2011-12 CT#54 Referencing Information Elements defined 11.0.1 11.1.0
CP-110790 C4-112477 1019 2 A outside GTP
2011-12 CT#54 CP-110810 C4-112461 1033 1 F Scope Indication IE in Delete Session Request 11.0.1 11.1.0
2011-12 CT#54 CP-110810 C4-112511 1061 1 F ULI in the Create Session Request 11.0.1 11.1.0
2011-12 CT#54 CP-110810 C4-112507 1038 1 F Update PDN Connection Set Request 11.0.1 11.1.0
2011-12 CT#54 Essential clarification on F-TEID in Create 11.0.1 11.1.0
CP-110784 C4-112900 1022 2 A Bearer Response
2011-12 CT#54 CP-110784 C4-113164 1030 3 Modify Bearer Request as implicit resume 11.0.1 11.1.0
2011-12 CT#54 User CSG Information in TAU/RAU 11.0.1 11.1.0
CP-110784 C4-113167 1080 2 A procedures
2011-12 CT#54 Missing Originating Node IE when ISR is 11.0.1 11.1.0
CP-110784 C4-113143 1083 2 A active
2011-12 CT#54 Correction to the Sender F-TEID IE description 11.0.1 11.1.0
CP-110784 C4-113069 1088 1 A of the Forward Relocation Request
2011-12 CT#54 CP-110784 C4-113113 1103 2 A Missing Cause Value for MUPSAP 11.0.1 11.1.0
2011-12 CT#54 Downlink bearers release during mobility 11.0.1 11.1.0
CP-110784 C4-113139 1106 2 A procedure
2011-12 CT#54 CP-110810 C4-113086 1027 2 F SRNS relocation w/o PDN connection 11.0.1 11.1.0
2011-12 CT#54 CP-110810 C4-113144 1066 3 F PDN Type and DAF dependency case 11.0.1 11.1.0
2011-12 CT#54 TFT in the SGW for PMIP based S5/S8 11.0.1 11.1.0
CP-110810 C4-113087 1072 1 F interface
2011-12 CT#54 MBMS Flow ID in the MBMS Session Stop 11.0.1 11.1.0
CP-110810 C4-113088 1073 1 F message
2011-12 CT#54 Change Notification Reporting with Non-Zero 11.0.1 11.1.0
CP-110810 C4-113145 1085 2 C TEID
2011-12 CT#54 CP-110810 C4-113093 1090 1 F LBI in the Delete Bearer Request 11.0.1 11.1.0
2011-12 CT#54 CP-110810 C4-112753 1091 - F DRX parameter 11.0.1 11.1.0
2011-12 CT#54 CP-110810 C4-112754 1092 - B ZUC based EEA3 and EIA3 security algorithm 11.0.1 11.1.0
2011-12 CT#54 CP-110810 C4-113116 1098 2 F Suspend Notification 11.0.1 11.1.0
2011-12 CT#54 PCO IE in the Modify Bearer Request 11.0.1 11.1.0
CP-110790 C4-113064 1075 1 A message
2011-12 CT#54 CP-110790 C4-113071 1094 1 A IMEI not known cause 11.0.1 11.1.0
2011-12 CT#54 Correction on the bearer context for 11.0.1 11.1.0
CP-110790 C4-113077 1096 2 A modification procedure
ETSI
2011-12 CT#54 UE Time Zone condition in Modify Bearer 11.0.1 11.1.0
CP-110790 C4-112883 1108 - A Request
2011-12 CT#54 CP-110815 C4-112975 1067 1 B PGW restoration upon PGW failure w/o restart 11.0.1 11.1.0
2011-12 CT#54 Authentication with external networks over 11.0.1 11.1.0
CP-110792 C4-113160 1070 3 A GTP S2b
2011-12 CT#54 Add vSRVCC indicator to Delete Bearer 11.0.1 11.1.0
CP-110816 C4-112698 1086 - B Command
2012-03 CT#55 CP-120017 C4-120016 1117 - A Handover to CSG cell with emergency bearer 11.1.0 11.2.0
2012-03 CT#55 CP-120017 C4-120022 1120 - A Pre-Rel-7 QoS description correction 11.1.0 11.2.0
2012-03 CT#55 CP-120017 C4-120426 1126 2 A Reserved Bearer Context at SRNS Relocation 11.1.0 11.2.0
2012-03 CT#55 CP-120017 C4-120429 1146 2 A Higher bitrates than 16 Mbps flag 11.1.0 11.2.0
2012-03 CT#55 CP-120017 C4-120435 1180 1 A ULI reporting for S4 11.1.0 11.2.0
2012-03 CT#55 UE Requested Bearer Resource Modification 11.1.0 11.2.0
CP-120026 C4-120520 1133 6 A Procedure
2012-03 CT#55 Presence requirements of Information 11.1.0 11.2.0
CP-120026 C4-120041 1135 - A Elements
2012-03 CT#55 Max MBR/APN-AMBR in enhanced SRNS 11.1.0 11.2.0
CP-120026 C4-120161 1141 2 A relocation procedure
2012-03 CT#55 CP-120026 C4-120085 1147 1 A Clarification of Echo Response 11.1.0 11.2.0
2012-03 CT#55 Location change reporting support indication 11.1.0 11.2.0
CP-120026 C4-120095 1152 1 A related correction
2012-03 CT#55 CP-120026 C4-120101 1154 1 A Fix Inter RAT HO issue when ISR active 11.1.0 11.2.0
2012-03 CT#55 Bearer Context to be modified in the Modify 11.1.0 11.2.0
CP-120036 C4-120573 1077 4 F Bearer Request message
2012-03 CT#55 Mapping between S11/S4 and NAS Cause 11.1.0 11.2.0
CP-120036 C4-120500 1113 2 F values
2012-03 CT#55 Absolute time for MBMS data transfer start 11.1.0 11.2.0
CP-120036 C4-120078 1114 1 C and stop
2012-03 CT#55 CP-120036 C4-120083 1155 1 F Cause code description 11.1.0 11.2.0
2012-03 CT#55 CP-120036 C4-120142 1158 - F SRVCC PS to CS Response 11.1.0 11.2.0
2012-03 CT#55 CP-120036 C4-120503 1170 1 F Charging ID for Non-3GPP IP Access 11.1.0 11.2.0
2012-03 CT#55 CP-120036 C4-120504 1171 1 F Sender's F-TEID for Control Plane 11.1.0 11.2.0
2012-03 CT#55 Clean up of the irrelevant cause codes from 11.1.0 11.2.0
CP-120036 C4-120505 1173 1 F the GTPv2 triggered messages
2012-03 CT#55 PGW based provisioning of the DNS server 11.1.0 11.2.0
CP-120036 C4-120510 1175 2 F address for the S2b interface
2012-03 CT#55 CP-120036 C4-120354 1177 - F GTPv2 header 11.1.0 11.2.0
2012-03 CT#55 CP-120042 C4-120584 1159 2 B New IEs for ePDG scenario 11.1.0 11.2.0
2012-03 CT#55 CP-120041 C4-120168 1161 - F Voice/Video bearer for vSRVCC 11.1.0 11.2.0
2012-03 CT#55 CP-120045 C4-120232 1163 - B Addition of GTP based S2a in clauses 1 to 6 11.1.0 11.2.0
2012-03 CT#55 CP-120045 C4-120457 1164 1 B Create Session Request on GTP based S2a 11.1.0 11.2.0
2012-03 CT#55 CP-120045 C4-120459 1165 1 B Create Bearer Request on GTP based S2a 11.1.0 11.2.0
2012-03 CT#55 Delete Session Request & Delete Bearer 11.1.0 11.2.0
CP-120045 C4-120460 1166 1 B Request on GTP based S2a
2012-03 CT#55 Modify Bearer Command & Update Bearer 11.1.0 11.2.0
CP-120045 C4-120461 1167 1 B Request on GTP based S2a
2012-03 CT#55 Trace Session Activation & Deactivation on 11.1.0 11.2.0
CP-120045 C4-120462 1168 1 B GTP based S2a
2012-03 CT#55 Delete PDN Connection Set on GTP based 11.1.0 11.2.0
CP-120045 C4-120238 1169 - B S2a
2012-06 CT#56 CSR and MBR message for SGW restoration 11.2.0 11.3.0
CP-120230 C4-120671 1156 1 B procedure
2012-06 CT#56 CP-120230 C4-120964 1157 3 B Context Response message 11.2.0 11.3.0
2012-06 CT#56 CP-120233 C4-120892 1162 2 F Reporting of H(e)NB local IP address and port 11.2.0 11.3.0
2012-06 CT#56 CP-120228 C4-121239 1182 5
2012-06 CT#56 Adding Originating Node IE to the Delete 11.2.0 11.3.0
CP-120228 C4-121327 1183 5 F Session Request for ISR cases
2012-06 CT#56 CP-120233 C4-120891 1186 1 B Updated UE local IP in S2b procedure 11.2.0 11.3.0
2012-06 CT#56 CP-120240 C4-120926 1187 2 B Network provided Location Information 11.2.0 11.3.0
2012-06 CT#56 CP-120224 C4-120847 1191 1 A CFSI in the modify access bearers request 11.2.0 11.3.0
2012-06 CT#56 CP-120228 C4-120860 1194 - F The usage of TEID0 11.2.0 11.3.0
2012-06 CT#56 CP-120230 C4-120696 1195 - B Inclusion of MME/S4-SGSN Identifier 11.2.0 11.3.0
2012-06 CT#56 PGW Downlink Triggering 11.2.0 11.3.0
CP-120230 C4-120888 1196 1 B Notification/Acknowledge
2012-06 CT#56 CP-120234 C4-120945 1197 2 B Additions for CS to PS SRVCC 11.2.0 11.3.0
2012-06 CT#56 Mapping of NAS ESM/SM Cause codes to 11.2.0 11.3.0
CP-120228 C4-120861 1198 1 F S11/S4 Cause codes
2012-06 CT#56 Release of old S3 GTP-C TEIDs during I-RAT 11.2.0 11.3.0
CP-120228 C4-121236 1199 3 F HO with ISR active
2012-06 CT#56 ULI inclusion condition during Service Request 11.2.0 11.3.0
CP-120228 C4-120963 1200 2 F procedure when ISR is active
ETSI
2012-06 CT#56 Addition of Subnet Mask and Default Router 11.2.0 11.3.0
Address in Create Session Response for
CP-120238 C4-120881 1201 1 B Trusted WLAN Access over S2a
2012-06 CT#56 Clarify mandatory/conditional IE inclusion in 11.2.0 11.3.0
CP-120228 C4-120867 1202 1 F error response msg
2012-06 CT#56 TAD in the Bearer Resource Command 11.2.0 11.3.0
CP-120228 C4-121335 1210 2 F message
2012-06 CT#56 More choices of mapping between GTPv2 11.2.0 11.3.0
CP-120228 C4-121078 1211 - F cause code to the NAS ESM/SM Cause codes
2012-06 CT#56 CP-120228 C4-121237 1213 1 F Extended RNC ID in Target Identification IE 11.2.0 11.3.0
2012-06 CT#56 Clarification to "SGW node name" & "SGW 11.2.0 11.3.0
S11/S4 IP Address and TEID for Control
CP-120228 C4-121242 1214 1 F Plane" IE presence conditions
2012-09 CT#57 SGW DL/UL F-TEID for data forwarding in 11.3.0 11.4.0
CP-120448 C4-121552 1230 - A Forward Relocation Response message
2012-09 CT#57 CP-120477 C4-121718 1216 1 B RAT Type for EPC access via TWAN 11.3.0 11.4.0
2012-09 CT#57 Encoding of Absolute Time of MBMS Data 11.3.0 11.4.0
CP-120457 C4-121370 1217 - F Transfer
2012-09 CT#57 Sender"s F-TEID in the Forward Relocation 11.3.0 11.4.0
CP-120457 C4-121778 1219 2 F Response
2012-09 CT#57 Presence condition of APN-AMBR in the 11.3.0 11.4.0
CP-120457 C4-121431 1221 - F Modify Bearer Response message
2012-09 CT#57 CP-120457 C4-121700 1222 2 F GTP Tunnel 11.3.0 11.4.0
2012-09 CT#57 Delete Session Request usage in SGW with 11.3.0 11.4.0
CP-120457 C4-121739 1224 1 F active ISR
2012-09 CT#57 CP-120457 C4-121495 1226 - F Context Request note error 11.3.0 11.4.0
2012-09 CT#57 CP-120457 C4-121549 1228 - PAA clarification for PDN type IPv4v6 11.3.0 11.4.0
2012-09 CT#57 CP-120457 C4-121779 1232 2 F F-TEID interface types for Indirect Forwarding 11.3.0 11.4.0
2012-09 CT#57 Zero TEID Usage In Relocation Cancel 11.3.0 11.4.0
CP-120457 C4-121780 1233 2 F Response
2012-09 CT#57 CP-120457 C4-121753 1235 1 F PDP connection inactivity timer expires 11.3.0 11.4.0
2012-09 CT#57 CP-120475 C4-121725 1220 1 B MSV flag in rSRVCC procedure 11.3.0 11.4.0
2012-09 CT#57 CP-120475 C4-121729 1236 - B Selected PLMN ID 11.3.0 11.4.0
2012-09 CT#57 Reference list correction to align with the 11.3.0 11.4.0
CP-120656 - 1237 1 F corrected TS 29.212 title
2012-12 CT#58 CP-120718 C4-122178 1240 1 A Removal of Maximum MBR/APN-AMBR 11.4.0 11.5.0
2012-12 CT#58 Change to Report Flags for delayed reporting 11.4.0 11.5.0
of change of SN/TZ during inter-CN node
CP-120718 C4-122560 1243 3 A mobility
2012-12 CT#58 Additional MBR for delayed reporting of 11.4.0 11.5.0
CP-120718 C4-122227 1270 1 A change of SN/TZ/UCI
2012-12 CT#58 CP-120718 C4-122672 1291 3 A Delete Bearer Request with ISR deactivation 11.4.0 11.5.0
2012-12 CT#58 Adding a Cause Value in Delete Session 11.4.0 11.5.0
CP-120744 C4122224 1231 4 F Request message
2012-12 CT#58 Forward Relocation Request over the S3 11.4.0 11.5.0
CP-120744 C4-121883 1238 - F interface
2012-12 CT#58 Corrections to reference titles and octet 11.4.0 11.5.0
CP-120744 C4-121896 1244 - F numbering of IE definitions
2012-12 CT#58 Clarifications on sending/new node and 11.4.0 11.5.0
receiving/old node about Identification
CP-120744 C4-121897 1245 - F Request message
2012-12 CT#58 CP-120744 C4-121910 1246 - F Multiple CSID 11.4.0 11.5.0
2012-12 CT#58 TEID of the Change Notification Request and 11.4.0 11.5.0
CP-120744 C4-121911 1247 - F Response messages
2012-12 CT#58 Suspend Notification/Acknowledge message 11.4.0 11.5.0
CP-120744 C4-122557 1253 3 F in SGSN pool
2012-12 CT#58 Sender F-TEID IE in Modify Bearer Request 11.4.0 11.5.0
CP-120744 C4-121937 1254 - F message
2012-12 CT#58 CP-120744 C4-122171 1262 1 F Clarification of Delete Bearer Failure Indication 11.4.0 11.5.0
2012-12 CT#58 CP-120744 C4-122225 1263 2 F Cause value 'ISR deactivation' 11.4.0 11.5.0
2012-12 CT#58 CP-120744 C4-122173 1264 1 F IPv4 address allocation 11.4.0 11.5.0
2012-12 CT#58 Sender F-TEID in DDN msg (network triggered 11.4.0 11.5.0
CP-120744 C4-122174 1265 1 C service restoration procedure)
2012-12 CT#58 Correction to IP Address Instance values in 11.4.0 11.5.0
CP-120744 C4-122047 1268 - F CSReq & MBReq
2012-12 CT#58 Clarifications on value definitions of PDN 11.4.0 11.5.0
CP-120744 C4-122290 1273 - F Type, Security Mode and Used NAS Cipher IE
2012-12 CT#58 Clarification on UCI in Create Session 11.4.0 11.5.0
CP-120744 C4-122558 1276 1 F Request message during SGW relocation
2012-12 CT#58 CP-120744 C4-122566 1283 1 F Change reporting requested by PCRF 11.4.0 11.5.0
2012-12 CT#58 CP-120744 C4-122556 1294 1 F Selected PLMN ID 11.4.0 11.5.0
ETSI
2012-12 CT#58 Sender F-TEID in PGW Downlink Triggering 11.4.0 11.5.0
CP-120739 C4-122575 1271 1 C Notification
2012-12 CT#58 CP-120739 C4-122615 1278 2 B SGW failure when ISR is active enhancement 11.4.0 11.5.0
2012-12 CT#58 TWAN operator identification for EPC access 11.4.0 11.5.0
CP-120733 C4-122601 1272 2 F charging
2012-12 CT#58 CP-120733 C4-122654 1286 3 F Trusted WLAN AP identity over GTP S2a 11.4.0 11.5.0
2012-12 CT#58 H(e)NB local IP address/port in create session 11.4.0 11.5.0
CP-120726 C4-122563 1279 1 F request
2012-12 CT#58 Removal of TFT IE from Create Session 11.4.0 11.5.0
CP-120710 C4-122565 1257 2 A Response message
2012-12 CT#58 Clarifications on RAT Type Values 'UTRAN' 11.4.0 11.5.0
CP-120744 C4-122168 1258 1 F and 'HSPA evolution'
2013-03 CT#59 CP-130021 C4-130405 1306 2 F Populating Serving Network 11.5.0 11.6.0
2013-03 CT#59 IMSI in Suspend Notification for UICCless 11.5.0 11.6.0
CP-130021 C4-130406 1307 2 F Emergency Call
2013-03 CT#59 User CSG Information reporting during inter- 11.5.0 11.6.0
CP-130018 C4-130410 1310 2 A MME/SGSN mobility
2013-03 CT#59 CP-130027 C4-130218 1320 - F Sending SSID for SaMOG in GTP 11.5.0 11.6.0
2013-03 CT#59 CP-130029 C4-130371 1296 1 F Bearer QoS 11.6.0 12.0.0
2013-03 CT#59 CP-130029 C4-130372 1297 1 F Clarificatyion of term 'PS mobility' 11.6.0 12.0.0
2013-03 CT#59 Corrections to abbreviation of Radio Access 11.6.0 12.0.0
CP-130029 C4-130376 1302 1 F Technology and definition of cause value
2013-03 CT#59 CP-130029 C4-130374 1303 1 F Corrections to descriptions of RFSP Index 11.6.0 12.0.0
2013-03 CT#59 CP-130029 C4-130384 1311 1 F Correct the NOTE for Cause value 11.6.0 12.0.0
2013-03 CT#59 Corrections to Table Content, IE and Text 11.6.0 12.0.0
CP-130029 C4-130385 1312 1 F Color
2013-03 CT#59 Cause value in Update PDN Connection Set 11.6.0 12.0.0
CP-130029 C4-130368 1316 1 F Response
2013-03 CT#59 EPS bearer ID derived for Downlink Data 11.6.0 12.0.0
CP-130029 C4-130369 1318 1 F Notification
2013-03 CT#59 Correcting the Flow QoS IE reference for 11.6.0 12.0.0
CP-130029 C4-130392 1319 1 F Bearer Resource Command
2013-03 CT#59 CP-130031 C4-130400 1308 1 F Clarification of Resume when S4-U is enabled 11.6.0 12.0.0
2013-03 CT#59 Stop Paging Indication in service restoration 11.6.0 12.0.0
CP-130031 C4-130399 1313 1 F procedure
2013-06 CT#60 CP-130304 C4-130935 1324 1 F Direct Tunnel Flag 12.0.0 12.1.0
2013-06 CT#60 CP-130304 C4-130549 1322 - F Handling ASN.1/PER encoded parameters 12.0.0 12.1.0
2013-06 CT#60 CP-130304 C4-130933 1321 2 F Presence requirements clarification 12.0.0 12.1.0
2013-06 CT#60 CR on Unaccepted PDN connection during 12.0.0 12.1.0
CP-130304 C4-131049 1330 3 F TAU and Handover
2013-06 CT#60 CP-130304 C4-130948 1343 1 F TWAN Identifier 12.0.0 12.1.0
2013-06 CT#60 CP-130304 C4-130946 1339 1 F Missing Recovery IE 12.0.0 12.1.0
2013-06 CT#60 The setting EPS bearer ID/ARP for MME 12.0.0 12.1.0
CP-130304 C4-131007 1337 2 F paging strategy
2013-06 CT#60 Delete Bearer Request triggered by PMIP 12.0.0 12.1.0
CP-130304 C4-130943 1336 2 F error indication message
2013-06 CT#60 Prohibit Payload Compression Indication 12.0.0 12.1.0
CP-130304 C4-130947 1332 1 F Corrections
2013-06 CT#60 CP-130296 C4-131024 1341 2 A ULI Timestamp 12.0.0 12.1.0
2013-06 CT#60 CP-130378 C4-130918 1323 1 B SIPTO at the local network 12.0.0 12.1.0
2013-06 CT#60 Removal of TFT IE from Create Session 12.0.0 12.1.0
CP-130282 C4-130791 1346 - A Response message
2013-06 CT#60 Bearer Context to be modified in Modify 12.0.0 12.1.0
CP-130290 C4-131035 1329 2 A Bearer Request
2013-09 CT#61 Reporting ULI and TimeZone at MME-initiated 12.1.0 12.2.0
CP-130449 C4-131335 1350 1 A bearer related procedures
2013-09 CT#61 CP-130454 C4-131412 1347 1 B New MBMS flags for eMBMS restoration 12.1.0 12.2.0
2013-09 CT#61 CP-130467 C4-131456 1348 1 F Serving Network IE definition 12.1.0 12.2.0
2013-09 CT#61 CP-130467 C4-131528 1354 3 F Indication Flags 12.1.0 12.2.0
2013-09 CT#61 CP-130467 C4-131519 1355 2 F Sending Recovery IE in GTPv2-C messages 12.1.0 12.2.0
2013-09 CT#61 Enforcing access restriction during I-RAT 12.1.0 12.2.0
CP-130467 C4-131500 1361 2 B RAU/TAU procedures
2013-09 CT#61 Modify Access Bearer for Intra TAU w/o SGW 12.1.0 12.2.0
CP-130467 C4-131466 1371 1 F change
2013-09 CT#61 CP-130467 C4-131458 1372 1 D GTP-C message types for rSRVCC 12.1.0 12.2.0
2013-09 CT#61 CP-130446 C4-131342 1352 1 A Returning to former LTE PLMN after CSFB 12.1.0 12.2.0
2013-09 CT#61 Inclusion of ePDG IP address of IKEv2 tunnel 12.1.0 12.2.0
CP-130443 C4-131473 1363 1 A endpoint on S2b-GTP
2013-09 CT#61 CP-130453 C4-131417 1364 1 B SIPTO at the Local Network 12.1.0 12.2.0
2013-09 CT#61 CP-130462 C4-131447 1365 1 F GERAN Iu Mode 12.1.0 12.2.0
2013-09 CT#61 CP-130470 C4-131234 1366 - B Update to cover the S121 12.1.0 12.2.0
2013-09 CT#61 CP-130583 - 1368 4 A ULI Timestamp IE format 12.1.0 12.2.0
ETSI
2013-12 CT#62 Reporting the RAN/NAS release cause during 12.2.0 12.3.0
CP-130626 C4-131891 1374 3 B bearer release procedures
2013-12 CT#62 CP-130626 C4-131598 1375 - F MM Context IE in Identification Response 12.2.0 12.3.0
2013-12 CT#62 CP-130626 C4-132262 1376 4 B Core Network Operator selection origin 12.2.0 12.3.0
2013-12 CT#62 Correct Presence requirement for Conditional 12.2.0 12.3.0
CP-130626 C4-131857 1378 1 F IE
2013-12 CT#62 CP-130626 C4-131837 1382 1 F Delete Session Request/Response 12.2.0 12.3.0
2013-12 CT#62 CP-130626 C4-131838 1383 1 F Correction the ULI for RAI IE 12.2.0 12.3.0
2013-12 CT#62 Correct the Message Type value reserved for 12.2.0 12.3.0
CP-130626 C4-131839 1384 1 F S101
2013-12 CT#62 CP-130626 C4-131840 1385 1 F Harmonisation of the abbreviation LBI 12.2.0 12.3.0
2013-12 CT#62 CP-130626 C4-132187 1391 1 F Variable length parameters in GTPv2 IEs 12.2.0 12.3.0
2013-12 CT#62 Removing APN-AMBR from Modify Bearer 12.2.0 12.3.0
CP-130626 C4-132188 1392 1 F Response
2013-12 CT#62 Clarification on encoding of bit rates when 12.2.0 12.3.0
converting bits per second received over
Diameter interfaces to kilo bits per second
CP-130626 C4-132189 1393 1 F over GTPv2.
2013-12 CT#62 CP-130626 C4-132247 1396 2 F Correct the value of the Selection Mode IE 12.2.0 12.3.0
2013-12 CT#62 Cause IE condition in the Delete Session 12.2.0 12.3.0
CP-130626 C4-132193 1397 1 F Request
2013-12 CT#62 S1-U eNodeB F-TEID in Create Bearer 12.2.0 12.3.0
CP-130626 C4-132280 1398 2 F Response
2013-12 CT#62 CP-130626 C4-132285 1400 2 F SS code used in the Paging message 12.2.0 12.3.0
2013-12 CT#62 CP-130626 C4-132224 1405 1 F PGW IP Addresses in Initial Messages 12.2.0 12.3.0
2013-12 CT#62 PGW and SGW Charging alignment in 12.2.0 12.3.0
CP-130626 C4-132249 1406 2 B downlink
2013-12 CT#62 ULI reporting in the Create Session Request 12.2.0 12.3.0
CP-130613 C4-131881 1387 2 A and Modify Bearer Request message
2013-12 CT#62 CP-130604 C4-132222 1390 1 A Correction on Trace information 12.2.0 12.3.0
2013-12 CT#62 Support HO indication and additional PDN 12.2.0 12.3.0
CP-130633 C4-132250 1394 2 B request on the S2a GTP interface
2014-03 CT#63 CP-140029 C4-140294 1409 1 F F-TEID Interface Type 8 12.3.0 12.4.0
2014-03 CT#63 CP-140029 C4-140377 1410 2 F S12, S4-U, S1-U F-TEID values 12.3.0 12.4.0
2014-03 CT#63 CP-140029 C4-140378 1411 2 F Triggered messages 12.3.0 12.4.0
2014-03 CT#63 CP-140029 C4-140419 1413 2 F F-Container Definition Correction 12.3.0 12.4.0
2014-03 CT#63 CP-140029 C4-140387 1417 2 F CSG Membership Indication values 12.3.0 12.4.0
2014-03 CT#63 CP-140029 C4-140330 1418 1 F Dummy IMSI in Resume Notification 12.3.0 12.4.0
2014-03 CT#63 Sender F-TEID in the Delete Session Request 12.3.0 12.4.0
CP-140029 C4-140379 1419 2 F message
2014-03 CT#63 PLMN ID communicated to the HPLMN in 12.3.0 12.4.0
CP-140029 C4-140332 1423 1 F network sharing
2014-03 CT#63 TWAN-ID reporting extensions for NPLI for 12.3.0 12.4.0
CP-140030 C4-140319 1421 1 B TWAN access
2014-03 CT#63 TWAN-ID contents extensions for NPLI for 12.3.0 12.4.0
CP-140030 C4-140320 1422 1 B TWAN access
2014-03 CT#63 TWAN location retrieval in Update Bearer 12.3.0 12.4.0
CP-140030 C4-140318 1436 - B Request
2014-03 CT#63 CP-140031 C4-140414 1429 3 B Trusted WLAN mode indication 12.3.0 12.4.0
2014-03 CT#63 CP-140022 C4-140368 1431 1 A Update the ULI Timestamp IE format 12.3.0 12.4.0
2014-03 CT#63 Bearer context in Update Bearer Response 12.3.0 12.4.0
CP-140022 C4-140385 1435 2 A when DTF is set
2014-03 CT#63 Temporarily rejected due to mobility procedure 12.3.0 12.4.0
CP-140021 C4-140358 1433 1 A in progress
2014-03 CT#64 Introduction of Node Number and Node 12.4.0 12.5.0
Identifier (to carry SGSN Lgd Identifier and
CP-140261 C4-141109 1438 3 F MME SLg identifier)
2014-06 CT#64 Number of authentication vectors in the MM 12.4.0 12.5.0
CP-140261 C4-140739 1443 1 F Context IE
2014-06 CT#64 Context Response with P-TMSI Signature 12.4.0 12.5.0
CP-140261 C4-140885 1444 2 F mismatch
2014-06 CT#64 Including CSG change reporting for Change 12.4.0 12.5.0
CP-140261 C4-140774 1448 1 F Notification procedure
2014-06 CT#64 CP-140261 C4-140787 1452 1 F Spare bits in MM Context 12.4.0 12.5.0
2014-06 CT#64 User CSG Information reporting in rollback 12.4.0 12.5.0
CP-140261 C4-140790 1455 1 F case
2014-06 CT#64 CP-140261 C4-140791 1456 1 F Corrections to Node Type 12.4.0 12.5.0
2014-06 CT#64 CP-140261 C4-140792 1457 1 F Update the condition of the UE Time Zone IE 12.4.0 12.5.0
2014-06 CT#64 A new Cause Value for the case where an 12.4.0 12.5.0
MME in the VPLMN refuses to setup/modify a
CP-140261 C4-140796 1460 1 F Bearer
2014-06 CT#64 CP-140261 C4-141205 1478 2 B Alternate LMA address for user plane 12.4.0 12.5.0
ETSI
2014-06 CT#64 PLMN ID communicated in the VPLMN in 12.4.0 12.5.0
CP-140261 C4-141142 1479 1 F network sharing
2014-06 CT#64 CP-140261 C4-141143 1482 1 F Version Not Supported Indication 12.4.0 12.5.0
2014-06 CT#64 CP-140261 C4-141224 1489 3 F IPv6 address allocation 12.4.0 12.5.0
2014-06 CT#64 CP-140261 C4-141225 1490 3 F Context Request Indication flags 12.4.0 12.5.0
2014-06 CT#64 Update cause to indicate downlink message 12.4.0 12.5.0
CP-140235 C4-141191 1445 5 A delivery failure due to crash with mobility event
2014-06 CT#64 CP-140235 C4-140809 1447 2 A MDT configuration during inter-MME handover 12.4.0 12.5.0
2014-06 CT#64 Reporting changes of UE presence in 12.4.0 12.5.0
CP-140242 C4-141173 1441 3 B Presence Reporting Area
2014-06 CT#64 CP-140247 C4-140567 1451 - F PCO in the HO to TWAN procedures 12.4.0 12.5.0
2014-06 CT#64 CP-140247 C4-151219 1487 2 F PCO in handover to 3GPP access 12.4.0 12.5.0
2014-06 CT#64 CP-140252 C4-140746 1439 1 B TWAN Identifier Timestamp 12.4.0 12.5.0
2014-06 CT#64 CP-140252 C4-140477 1440 - B Civic address encoding 12.4.0 12.5.0
2014-06 CT#64 Extension to the TWAN Identifier contents: 12.4.0 12.5.0
CP-140252 C4-141201 1459 4 B new Line Identifier (Logical Access ID)
2014-06 CT#64 CP-140252 C4-141200 1481 2 F SSID not sufficient for TWAN location 12.4.0 12.5.0
2014-06 CT#64 Propagation of MME/S4-SGSN identity to 12.4.0 12.5.0
CP-140241 C4-141129 1461 1 B PGW
2014-06 CT#64 Updating PGW with overload control 12.4.0 12.5.0
CP-140241 C4-141130 1462 1 B information of target MME/S4-SGSN
2014-06 CT#64 Interaction with congestion control using APN 12.4.0 12.5.0
CP-140241 C4141131 1463 1 B back-off timer
2014-06 CT#64 Discovery of the support of the GTP signalling 12.4.0 12.5.0
CP-140241 C4-141119 1464 1 B based Load Control feature by the peer node
2014-06 CT#64 Discovery of the support of the GTP signalling 12.4.0 12.5.0
based Overload Control feature by the peer
CP-140241 C4-141134 1465 1 B node
2014-06 CT#64 Issues in the network with partial support of 12.4.0 12.5.0
CP-140241 C4-141120 1466 1 B the GTP Load Control feature
2014-06 CT#64 Issues in the network with partial support of 12.4.0 12.5.0
CP-140241 C4-141135 1467 1 B the GTP Overload Control feature
2014-06 CT#64 CP-140241 C4-141136 1468 1 B Implicit overload control mechanisms 12.4.0 12.5.0
2014-06 CT#64 CP-140241 C4-141116 1469 2 B Load control solution: General aspects 12.4.0 12.5.0
2014-06 CT#64 CP-140241 C4-141196 1470 3 B Overload control solution: General aspects 12.4.0 12.5.0
2014-06 CT#64 Addition of Load & Overload Control Info IEs in 12.4.0 12.5.0
CP-140241 C4-141137 1471 1 B session mgmt. messages
2014-06 CT#64 Definition of new IEs for Load & Overload 12.4.0 12.5.0
CP-140241 C4-141198 1472 2 B Control feature
2014-06 CT#64 Overload problem, scenarios, load and 12.4.0 12.5.0
CP-140241 C4-141117 1475 1 B overload control concepts
2014-06 CT#64 CP-140241 C4-141132 1476 1 B Overload control: message throttling 12.4.0 12.5.0
2014-06 CT#64 CP-140241 C4-141197 1477 2 B Enforcement of overload control 12.4.0 12.5.0
2014-06 CT#64 CP-140241 C4-141199 1480 2 B Load control information 12.4.0 12.5.0
2014-06 CT#64 CP-140241 C4-141218 1488 2 B Overload Control Information 12.4.0 12.5.0
2014-09 CT#65 Handovers between non-3GPP and 3GPP 12.5.0 12.6.0
CP-140512 C4-141254 1492 - F access
2014-09 CT#65 CP-140512 C4-141643 1493 2 F Setting Handover Indication flag 12.5.0 12.6.0
2014-09 CT#65 Reporting the RAN/NAS cause during bearer 12.5.0 12.6.0
CP-140512 C4-141600 1507 2 B creation/modification failure scenarios
2014-09 CT#65 Correct procedure name for PDN connection 12.5.0 12.6.0
CP-140512 C4-141551 1510 1 F deactivation
2014-09 CT#65 CP-140512 C4-141535 1512 1 F Repeated procedure description 12.5.0 12.6.0
2014-09 CT#65 Create Session Request received for an 12.5.0 12.6.0
CP-140512 C4-141394 1514 - F existing PDN connection
2014-09 CT#65 Deferred SN/CSG/Time zone change reporting 12.5.0 12.6.0
CP-140512 C4-141539 1515 2 F in GERAN
2014-09 CT#65 CP-140502 C4-141606 1495 2 A MDT PLMN List configuration parameter 12.5.0 12.6.0
2014-09 CT#65 Bearer contexts in Modify Access Bearers 12.5.0 12.6.0
CP-140502 C4-141542 1509 1 A Request
2014-09 CT#65 Inclusion of MME/S4-SGSN Identifier in the 12.5.0 12.6.0
Create/Update/Delete Bearer Response
CP-140505 C4-141624 1496 3 B message
2014-09 CT#65 CP-140505 C4-141546 1498 1 B Addition of missing changes 12.5.0 12.6.0
2014-09 CT#65 Inclusion PRA information in the 12.5.0 12.6.0
CP-140522 C4-141577 1497 1 B Create/Update Bearer Response message
2014-09 CT#65 Reporting changes of UE presence in a 12.5.0 12.6.0
CP-140522 C4-141321 1500 - B Presence Reporting Area
2014-09 CT#65 ULI change reporting when E-RAB/RAB/user 12.5.0 12.6.0
CP-140522 C4-141578 1501 2 B plane is established
2014-09 CT#65 CP-140506 C4-141317 1499 - B P-CSCF Restoration Indication 12.5.0 12.6.0
2014-09 CT#65 CP-140521 C4-141659 1511 3 B Introduction of Dual Connectivity Function 12.5.0 12.6.0
ETSI
2014-09 CT#65 PGW F-TEID in the PGW Downlink Triggering 12.5.0 12.6.0
CP-140518 C4-141602 1513 2 B Notification
2014-09 CT#65 BSS container in Forward Relocation Request 12.5.0 12.6.0
CP-140501 C4-141560 1518 - A / Response
2014-12 CT#66 Target Cell Identification in E-UTRAN to 12.6.0 12.7.0
CP-140758 C4-142256 1505 3 A GERAN PS Handover
2014-12 CT#66 P-CSCF Address Inclusion in PCO IE of 12.6.0 12.7.0
CP-140761 C4-142125 1540 2 A Update Bearer Request
2014-12 CT#66 Handling of load control and overload control 12.6.0 12.7.0
CP-140795 C4-142070 1519 2 F parameters
2014-12 CT#66 CP-140795 C4-142098 1520 3 F Overload control message prioritization 12.6.0 12.7.0
2014-12 CT#66 Propagating the MME/S4-SGSN identity to the 12.6.0 12.7.0
CP-140795 C4-142072 1521 2 F PGW
2014-12 CT#66 Overload/Load Control Information IE on 12.6.0 12.7.0
CP-140795 C4-142396 1542 1 F S2a/S2b/S4/S11
2014-12 CT#66 EBI value to use in Downlink Data Notification 12.6.0 12.7.0
Triggered by a Dedicated Bearer Activation
CP-140972 C4-141993 1523 1 F procedure when ISR is active
2014-12 CT#66 Essential clarification on the usage of cause 12.6.0 12.7.0
CP-140972 C4-142099 1526 3 F code 'Context Not Found'
2014-12 CT#66 CP-140972 C4-142075 1528 2 F Pending subscription change 12.6.0 12.7.0
2014-12 CT#66 Handovers from non-3GPP IP access to 3GPP 12.6.0 12.7.0
CP-140972 C4-142132 1532 3 F IP access
2014-12 CT#66 Removal of Optimized HO procedure from 12.6.0 12.7.0
CP-140972 C4-142051 1534 1 F HRPD to EUTRAN
2014-12 CT#66 Type value of the BSS Container IE in Context 12.6.0 12.7.0
CP-140972 C4-141851 1535 - F Response
2014-12 CT#66 CP-140972 C4-142134 1536 1 F Length of Recovery IE 12.6.0 12.7.0
2014-12 CT#66 Additional cause code mapping for non- 12.6.0 12.7.0
CP-140972 C4-142154 1541 3 F availability of Services due to LTE-Roaming
2014-12 CT#66 CP-140972 C4-142223 1544 - F Missing Value definition of GUTI 12.6.0 12.7.0
2014-12 CT#66 CP-140972 C4-142469 1545 3 F Message piggybacking clarification 12.6.0 12.7.0
2014-12 CT#66 Paging stop indication for ISR during P-CSCF 12.6.0 12.7.0
CP-140794 C4-142061 1525 1 B restoration procedure
2014-12 CT#66 CP-140972 C4-142074 1527 2 F MEI in Create Session Request 12.6.0 12.7.0
2014-12 CT#66 Bearer Contexts to be modified IE in 'Modify 12.6.0 12.7.0
CP-140794 C4-141945 1529 1 B Bearer Request
2014-12 CT#66 CP-140779 C4-141971 1530 1 F TWAN PLMN ID 12.6.0 12.7.0
2014-12 CT#66 WLAN Offloadability transfer during mobilitiy 12.6.0 12.7.0
CP-140780 C4-142133 1533 5 B procedures
2014-12 CT#66 No change S1 SGW F-TEID in E-UTRAN 12.6.0 12.7.0
CP-140789 C4-142390 1543 1 F Initiated E-RAB modification procedure
2014-12 CT#66 Inclusion of PCO in Delete Session/Bearer 12.6.0 12.7.0
CP-140784 C4-142398 1548 1 F Request for TWAN access
2014-12 CT#66 Provisioning of P-CSCF address via APCO for 12.7.0 13.0.0
CP-140796 C4-142069 1524 2 B S2b
2014-12 CT#66 GTP-C overload control from TWAN/ePDG to 12.7.0 13.0.0
CP-140760 C4-142397 1546 1 B PGW
2015-03 CT#67 MBMS Alternative IP Multicast Distribution 13.0.0 13.1.0
CP-150037 C4-150275 1547 3 B Address
2015-03 CT#67 CP-150037 C4-150243 1550 1 F Clarification of RAC encoding 13.0.0 13.1.0
2015-03 CT#67 CP-150037 C4-150244 1551 1 F MBMS Flow Identifier clarification 13.0.0 13.1.0
2015-03 CT#67 CP-150037 C4-150245 1554 1 F Unexpected GTP message clarification 13.0.0 13.1.0
2015-03 CT#67 CP-150037 C4-150268 1556 1 C UE Registration Query 13.0.0 13.1.0
2015-03 CT#67 CP-150037 C4-150348 1557 3 F Correction on definition of IMSI 13.0.0 13.1.0
2015-03 CT#67 Bearer Contexts in Create Bearer Response, 13.0.0 13.1.0
Update Bearer Response and Delete Bearer
Response for partial failure and success
CP-150037 C4-150274 1559 1 F cases.
2015-03 CT#67 CP-150037 C4-150264 1561 1 F Cause IMSI not known 13.0.0 13.1.0
2015-03 CT#67 CP-150037 C4-150277 1566 1 B TWAN Release Cause 13.0.0 13.1.0
2015-03 CT#67 ULI IE condition in Create session Request 13.0.0 13.1.0
CP-150025 C4-150351 1553 2 A message
2015-03 CT#67 CP-150025 C4-150297 1563 1 A PDN Type in PAA IE for S2b case 13.0.0 13.1.0
2015-03 CT#67 CP-150025 C4-150304 1568 1 A ULI change reporting upon inter-RAT mobility 13.0.0 13.1.0
2015-03 CT#67 Paging Policy Indication in Downlink Data 13.0.0 13.1.0
CP-150041 C4-150218 1565 1 B Notification message
2015-06 CT#68 ARP Value in Downlink Data Notification 13.1.0 13.2.0
CP-150254 C4-150519 1589 - A message
2015-06 CT#68 Contents of ULI IE in the Modify Bearer 13.1.0 13.2.0
CP-150254 C4-150997 1594 1 A Request during Handovers to UTRAN
ETSI
2015-06 CT#68 TEID-C header value not known / Failure 13.1.0 13.2.0
CP-150270 C4-150714 1570 3 F Indication message Cause value rules
2015-06 CT#68 CP-150270 C4-150427 1573 - F RAT Type in Change Notification Request 13.1.0 13.2.0
2015-06 CT#68 PCO in CSReq for handover to TWAN with 13.1.0 13.2.0
CP-150270 C4-150709 1575 2 F GTP over S2a
2015-06 CT#68 Correction to ULI inclusion for PDP activation 13.1.0 13.2.0
CP-150270 C4-150697 1576 2 C procedure
2015-06 CT#68 IE inclusion for non-3GPP to 3GPP handover 13.1.0 13.2.0
CP-150270 C4-150698 1577 3 F case
2015-06 CT#68 Inclusion of EBI in Delete Bearer Request 13.1.0 13.2.0
CP-150270 C4-150458 1578 - F message
2015-06 CT#68 User CSG Information in TAU/RAU with SGW 13.1.0 13.2.0
CP-150270 C4-150648 1581 2 F change procedure
2015-06 CT#68 CP-150270 C4-150700 1582 2 B Session/bearer release cause over S2a 13.1.0 13.2.0
2015-06 CT#68 CP-150270 C4-150701 1583 2 B Session/bearer release cause over S2b 13.1.0 13.2.0
2015-06 CT#68 At receiving Delete Bearer Failure Indication 13.1.0 13.2.0
CP-150270 C4-150978 1599 1 F sent on zero-TEID
2015-06 CT#68 UCI condition in Modify Bearer Request 13.1.0 13.2.0
CP-150270 C4-150983 1600 1 F message
2015-06 CT#68 Upon receiving unexpected triggered 13.1.0 13.2.0
CP-150270 C4-151063 1601 2 C messages
2015-06 CT#68 CP-150270 C4-150985 1603 1 F Correction to ULI for the S5/S8 interface 13.1.0 13.2.0
2015-06 CT#68 Presence condition of embedded IEs in a 13.1.0 13.2.0
CP-150270 C4-150986 1604 1 F Grouped IE
2015-06 CT#68 EBI and ARP in DDN message sent to S4- 13.1.0 13.2.0
CP-150270 C4-150987 1605 1 F SGSN
2015-06 CT#68 Message Granularity of Restoration/Recovery 13.1.0 13.2.0
CP-150270 C4-150988 1606 1 F and Path Management messages
2015-06 CT#68 IMEI(SV) signalling over GTP based S2a and 13.1.0 13.2.0
CP-150274 C4-150990 1595 1 B S2b
2015-09 CT#69 Modify Access Bearers Request leading to 13.2.0 13.3.0
CP-150433 C4-151183 1615 - A unpause charging in the PGW
2015-09 CT#69 Receipt of a Create Session Request at SGW 13.2.0 13.3.0
colliding with an existing PDN connection
CP-150442 C4-151305 1608 1 B context
2015-09 CT#69 Detection and handling of late arriving 13.2.0 13.3.0
CP-150442 C4-151389 1609 2 B requests
2015-09 CT#69 eDRX impact on GTPv2 for network originated 13.2.0 13.3.0
CP-150439 C4-151321 1610 1 B control plane procedure
2015-09 CT#69 Enhancement in Downlink Data Notification 13.2.0 13.3.0
Acknowledgement for extended buffering in
CP-150454 C4-151384 1611 2 B the SGW
2015-09 CT#69 Data forwarding for buffered DL data during 13.2.0 13.3.0
CP-150454 C4-151385 1612 2 B TAU/RAU with SGW change
2015-09 CT#69 Usage of Charging Characteristics for 13.2.0 13.3.0
CP-150448 C4-151323 1613 1 B activating PCC function
2015-09 CT#69 CP-150448 C4-151199 1616 - F SSID and BSSID encoding clarification 13.2.0 13.3.0
2015-09 CT#69 CP-150448 C4-151417 1619 2 B Monitoring Event Information 13.2.0 13.3.0
2015-09 CT#69 UE Usage Type for Dedicated Core Network 13.2.0 13.3.0
CP-150440 C4-151435 1620 3 B Feature
2015-09 CT#69 Reject Cause in Context Acknowledge for 13.2.0 13.3.0
CP-150440 C4-151393 1621 2 B Dedicated Core Network Feature
2015-09 CT#69 MME/SGSN/SGW/TWAN/ePDG NBIFOM 13.2.0 13.3.0
CP-150451 C4-151428 1625 2 B support indication
2015-12 CT#70 CP-150761 C4-151777 1626 1 B Cell List in MBMS Session Requests 13.3.0 13.4.0
2015-12 CT#70 Extensions for P-CSCF restoration for trusted 13.3.0 13.4.0
CP-150780 C4-151534 1627 - B and untrusted WLAN access
2015-12 CT#70 Emergency PDN connection over untrusted 13.3.0 13.4.0
CP-150770 C4-151721 1628 1 B WLAN access
2015-12 CT#70 User Location Information reporting extensions 13.3.0 13.4.0
CP-150770 C4-152184 1660 1 B over S2b
2015-12 CT#70 CP-150760 C4-151878 1631 2 F Load and overload metrics on APN level 13.3.0 13.4.0
2015-12 CT#70 CP-150760 C4-151879 1633 2 F Load and overload IE Instances 13.3.0 13.4.0
2015-12 CT#70 Load and overload sequence numbers per 13.3.0 13.4.0
CP-150760 C4-151880 1635 2 F node
2015-12 CT#70 CP-150760 C4-151881 1636 2 F Load and overload Sequence Number check 13.3.0 13.4.0
2015-12 CT#70 Modify Bearer Request when "Active flag" is 13.3.0 13.4.0
CP-150752 C4-151891 1637 3 F set
2015-12 CT#70 PCO in Create Session Request and 13.3.0 13.4.0
CP-150752 C4-151833 1639 2 F Response
2015-12 CT#70 CP-150752 C4-151834 1641 2 F Context not found in handovers 13.3.0 13.4.0
2015-12 CT#70 CP-150752 C4-151595 1645 - F Correct the wrong IE name 13.3.0 13.4.0
ETSI
2015-12 CT#70 CP-150752 C4-151596 1646 - F Coding of CSG ID 13.3.0 13.4.0
2015-12 CT#70 CP-150752 C4-151760 1651 1 B Extension of GTPv2 IE type 13.3.0 13.4.0
2015-12 CT#70 Addition of new GTPv2 Cause Code for Credit 13.3.0 13.4.0
CP-150752 C4-152361 1653 3 F Check
2015-12 CT#70 Inclusion of RAN/NAS Cause in Delete Bearer 13.3.0 13.4.0
CP-150752 C4-152219 1663 1 B Response
2015-12 CT#70 CP-150752 C4-152311 1665 2 F F-Container Type Value 13.3.0 13.4.0
2015-12 CT#70 CP-150773 C4-151859 1642 2 B Network-initiated IP flow mobility 13.3.0 13.4.0
2015-12 CT#70 UE-initiated IP Flow Mobility and IP Flow 13.3.0 13.4.0
CP-150773 C4-151865 1643 2 B Mapping
2015-12 CT#70 Addition of one access to a PDN connection in 13.3.0 13.4.0
CP-150773 C4-151866 1644 2 B NBIFOM
2015-12 CT#70 Define a cause value for the rejection of 13.3.0 13.4.0
CP-150773 C4-151819 1650 1 B additional access to a PDN connection
2015-12 CT#70 CP-150773 C4-152291 1669 1 F NBIFOM support indication 13.3.0 13.4.0
2015-12 CT#70 CP-150751 C4-151748 1648 1 A UE Radio Capability for Paging Information 13.3.0 13.4.0
2015-12 CT#70 Mapping table between GTPv2 S2a and 13.3.0 13.4.0
CP-150751 C4-152347 1658 3 F WLCP/Diameter
2015-12 CT#70 Operation Indication in MME triggered Serving 13.3.0 13.4.0
CP-150751 C4-152208 1667 1 A GW relocation procedure
2015-12 CT#70 Transferring DTCI and PNSI during inter 13.3.0 13.4.0
CP-150776 C4-151829 1649 2 B MME/SGSN mobility procedure
2015-12 CT#70 CP-150776 C4-151736 1652 1 B Delay Tolerant Connection Indication 13.3.0 13.4.0
2015-12 CT#70 CP-150776 C4-152197 1655 1 B DTCI in SGW 13.3.0 13.4.0
2015-12 CT#70 CP-150772 C4-152295 1656 2 B Remote UE Report Notification 13.3.0 13.4.0
2015-12 CT#70 CP-150756 C4-152222 1662 1 A Presence Reporting Area Identifier 13.3.0 13.4.0
2015-12 CT#70 Handling of Create Session Request without 13.3.0 13.4.0
CP-150782 C4-152185 1659 1 F Origination Timestamp
2015-12 CT#70 CP-150781 C4-152231 1668 1 F UE Usage Type Coding 13.3.0 13.4.0
2015-12 CT#70 CP-150778 C4-152060 1670 - B Monitoring Events in Identification Response 13.3.0 13.4.0
2015-12 CT#70 Remove Editor's Note on the Monitoring Event 13.3.0 13.4.0
CP-150778 C4-152365 1671 3 F Information
2015-12 CT#70 Instance numbers for overload control 13.3.0 13.4.0
CP-150765 C4-152220 1680 1 F information
ETSI
History
Document history
V13.4.0 March 2016 Publication
ETSI

Ts 129274v130400p

Uploaded by

Copyright:

Available Formats

Ts 129274v130400p

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ts 129274v130400p

Uploaded by

Copyright:

Available Formats

ETSI TS 1

129 274 V13.4.0 (2016

Universal Mobile Tel

650 Route des Lucioles

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C

The present document can be downloaded from:

© European Telecommunications Standards Institute 2016.

Intellectual Property Rights

Modal verbs terminology

7.2 Tunnel Management Messages ........................................................................................................................ 32

7.3.22 UE Registration Query Response ............................................................................................................. 189

8.7 Aggregate Maximum Bit Rate (AMBR) ........................................................................................................ 221

8.63 Channel needed .............................................................................................................................................. 259

12.3.9.2.1 Description .................................................................................................................................... 305

Annex A (Informative): Backward Compatibility Guidelines for Information Elements .............312

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

• For a specific reference, subsequent revisions do not apply.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 23.003: "Numbering, addressing and identification".

[6] IETF RFC 791 (STD 0005): "Internet Protocol", J. Postel.

[8] 3GPP TS 32.251: "Telecommunication Management; Charging Management; Packet Switched

[9] 3GPP TS 32.298: "Telecommunication Management; Charging Management; Charging Data

[11] 3GPP TS 33.102: "3G security; Security architecture".

[16] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".

[17] 3GPP TS 23.007: "Restoration procedures".

[31] IETF RFC 1035: "Domain Names - Implementation and Specification".

[32] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3".

[36] 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data

[39] IETF RFC 3588: "Diameter Base Protocol ".

[40] IETF RFC 4607: "Source-Specific Multicast for IP".

[41] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".

[45] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses.

[46] 3GPP TR 25.999: "HSPA Evolution (FDD)".

[47] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services".

[54] 3GPP TS 32.299: "Telecommunication Management; Charging Management; Diameter charging

[56] 3GPP TS 23.271: "Location Services".

[58] IETF RFC 5453: "Reserved IPv6 Interface Identifiers".

[60] IETF RFC 3046: "DHCP Relay Agent Information Option".

[61] 3GPP TS 23.380: "IMS Restoration Procedures".

[62] 3GPP TS 22.153: "Multimedia Priority Service".

[68] 3GPP TS 29.273: "3GPP EPS AAA Interfaces".

[71] 3GPP TS 23.161: "Network-Based IP Flow Mobility (NBIFOM); Stage 2".

[72] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".

3 Definitions, symbols and abbreviations

• Signalling Message: any GTP-PDU (GTP-C or GTP-U) except the G-PDU.

S1-U Interface between SGW and eNodeB

AMBR Aggregate Maximum Bit Rate

4.1 GTP Tunnel

- "Sender F-TEID for Control Plane" IE,

- "MSC Server Sv TEID for Control Plane" IE,

- "S3/S16/S10 Address and TEID for Control Plane" IE, or

- "MME/SGSN Sv TEID for Control Plane" IE.

For the control plane, for each end-point of a GTP-C tunnel:

For GTP-U, a TEID-U is used according to 3GPP TS 29.281 [13].

NOTE: GTP-U is based on GTP version 1 (GTPv1).