GPRS Tunnelling Protocol

<h2 id="general-features">General features</h2>
<p>All variants of GTP have certain features in common.  The structure of the messages is the same, with a GTP header following the UDP/TCP header.
</p>
<h3>Header</h3>
<h4>GTP version 1</h4>
<p>GTPv1 headers contain the following fields:<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a>
</p>
<table><tbody><tr><th>+</th><th colspan="3">0-2</th><th colspan="1">3</th><th colspan="1">4</th><th colspan="1">5</th><th colspan="1">6</th><th colspan="1">7</th><th colspan="8">8-15</th><th colspan="8">16-23</th><th colspan="8">24-31</th></tr><tr><th>0</th><td colspan="3">Version</td><td colspan="1">Protocol type</td><td colspan="1">Reserved</td><td colspan="1">Extension Header Flag</td><td colspan="1">Sequence Number Flag</td><td colspan="1">N-PDU Number Flag</td><td colspan="8">Message Type</td><td colspan="16">Message length</td></tr><tr><th>32</th><td colspan="32">TEID</td></tr><tr><th>64</th><td colspan="16">Sequence number</td><td colspan="8">N-PDU number</td><td colspan="8">Next extension header type</td></tr></tbody></table>
Version
It is a 3-bit field.  For GTPv1, this has a value of 1.
Protocol Type (PT)
a 1-bit value that differentiates GTP (value 1) from GTP' (value 0).
Reserved
a 1-bit reserved field (must be 0).
Extension header flag (E)
a 1-bit value that states whether there is an extension header optional field.
Sequence number flag (S)
a 1-bit value that states whether there is a Sequence Number optional field.
N-PDU number flag (PN)
a 1-bit value that states whether there is a N-PDU number optional field.
Message Type
an 8-bit field that indicates the type of GTP message. Different types of messages are defined in 3GPP TS 29.060 section 7.1
Message Length
a 16-bit field that indicates the length of the payload in bytes (rest of the packet following the mandatory 8-byte GTP header). Includes the optional fields.
Tunnel endpoint identifier (TEID)
A 32-bit(4-octet) field used to multiplex different connections in the same GTP tunnel.
Sequence number
an (optional) 16-bit field. This field exists if any of the E, S, or PN bits are on. The field must be interpreted only if the S bit is on.
N-PDU number
an (optional) 8-bit field. This field exists if any of the E, S, or PN bits are on. The field must be interpreted only if the PN bit is on.
Next extension header type
an (optional) 8-bit field. This field exists if any of the E, S, or PN bits are on. The field must be interpreted only if the E bit is on.
<p>Next Extension Headers are as follows:
</p>
<table><tbody><tr><th>+</th><th colspan="8">Bits 0-7</th><th colspan="16">8-23</th><th colspan="8">24-31</th></tr><tr><th>0</th><td colspan="8">Extension length</td><td colspan="24">Contents</td></tr><tr><th>...</th><td colspan="32">...</td></tr><tr><th>...</th><td colspan="24">Contents</td><td colspan="8">Next extension header</td></tr></tbody></table>
Extension length
an 8-bit field. This field states the length of this extension header, including the length, the contents, and the next extension header field, in 4-octet units, so the length of the extension must always be a multiple of 4.
Contents
extension header contents.
Next extension header
an 8-bit field. It states the type of the next extension, or 0 if no next extension exists. This permits chaining several next extension headers.
<h4>GTP version 2</h4>
<p>It is also known as evolved-GTP or eGTP. GTPv2-C headers contain the following fields:<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> 
</p>
<table><tbody><tr><th>+</th><th colspan="3">Bit 0-2</th><th colspan="1">3</th><th colspan="1">4</th><th colspan="3">5-7</th><th colspan="8">8-15</th><th colspan="8">16-23</th><th colspan="8">24-31</th></tr><tr><th>0</th><td colspan="3">Version</td><td colspan="1">Piggybacking flag (P)</td><td colspan="1">TEID flag (T)</td><td colspan="3">Spare</td><td colspan="8">Message Type</td><td colspan="16">Message length</td></tr><tr><th>32</th><td colspan="32">TEID (only present if T=1)</td></tr><tr><th>64 (32 if TEID not present)</th><td colspan="24">Sequence number</td><td colspan="8">Spare</td></tr></tbody></table>
<p>There is no GTPv2-U protocol, GTP-U in LTE also uses GTPv1-U.
</p>
Version
It is a 3-bit field.  For GTPv2, this has a value of 2.
Piggybacking flag
If this bit is set to 1 then another GTP-C message with its own header shall be present at the end of the current message. There are restrictions as to what type of message can be piggybacked depending on what the toplevel GTP-C message is.
TEID flag
If this bit is set to 1 then the TEID field will be present between the message length and the sequence number. All messages except Echo and Echo reply require TEID to be present.
Message length
This field shall indicate the length of the message in octets excluding the mandatory of the GTP-C header (the first 4 octets). The TEID (if present) and the Sequence Number shall be included in the length count.
<h3>Connectivity mechanisms</h3>
<p>Apart from the common message structure, there is also a common mechanism for verifying connectivity from one GSN to another GSN. This uses two messages.
</p>
<ul><li>echo request</li>
<li>echo response</li></ul>
<p>As often as every 60 seconds, a GSN can send an echo request to every other GSN with which it has an active connection.  If the other end does not respond it can be treated as down and the active connections to it will be deleted.
</p><p>Apart from the two messages previously mentioned, there are no other messages common across all GTP variants<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> meaning that, for the most part, they effectively form three completely separate protocols.
</p>
<h2 id="gtp-c---gtp-control">GTP-C - GTP control</h2>
<p>The GTP-C protocol is the control section of the GTP standard.  When a subscriber requests a <a href="/facts/PDP_context/Ju1sjTls">PDP context</a>, the SGSN will send a <i>create PDP context request</i> GTP-C message to the GGSN giving details of the subscriber's request.  The GGSN will then respond with a <i>create PDP context response</i> GTP-C message which will either give details of the PDP context actually activated or will indicate a failure and give a reason for that failure.  This is a UDP message on port 2123.
</p><p>The eGTP-C (or, GTPv2-C)  protocol is responsible for creating, maintaining and deleting tunnels on multiple Sx interfaces. It is used for the control plane path management, tunnel management and mobility management. It also controls forwarding relocation messages; SRNS context and creating forward tunnels during inter LTE handovers.
</p>
<h2 id="gtp-u---gtp-user-data-tunneling">GTP-U - GTP user data tunneling</h2>
<p>GTP-U is, in effect a relatively simple IP based tunnelling protocol which permits many tunnels between each set of end points.  When used in the UMTS, each subscriber will have one or more tunnel, one for each PDP context that they have active, as well as possibly having separate tunnels for specific connections with different quality of service requirements.
</p><p>The separate tunnels are identified by a TEID (Tunnel Endpoint Identifier) in the GTP-U messages, which should be a dynamically allocated random number.  If this random number is of <a href="/facts/Cryptography/e94PEVau">cryptographic</a> quality, then it will provide a measure of security against certain attacks.  Even so, the requirement of the 3GPP standard is that all GTP traffic, including user data should be sent within secure private networks, not directly connected to the Internet.  This happens on UDP port 2152.
</p><p>The GTPv1-U protocol is used to exchange user data over GTP tunnels across the Sx interfaces. An IP packet for a UE (user endpoint) is encapsulated in an GTPv1-U packet and tunnelled between the P-GW and the eNodeB for transmission with respect to a UE over S1-U and S5/S8 interfaces.
</p>
<h2 id="gtp---charging-transfer">GTP' - charging transfer</h2>
<p>The <a href="/facts/GTP%27/58eG8tmJ">GTP'</a> protocol is used to transfer charging data to the Charging Gateway Function.  GTP' uses TCP/UDP port 3386.
</p>
<h2 id="within-the-gprs-core-network">Within the GPRS core network</h2>
<p class="note">See also: <a href="/facts/GPRS_core_network/Ju1sjTls">GPRS core network</a></p>
<p>GTP is the primary protocol used in the GPRS core network. It is the protocol which allows end users of a GSM or UMTS network to move from place to place whilst continuing to connect to the Internet as if from one location at the GGSN.  It does this by carrying the subscriber's data from the subscriber's current SGSN to the GGSN which is handling the subscriber's session.  Three forms of GTP are used by the GPRS core network.
</p>
<ul><li>GTP-U for transfer of user data in separated tunnels for each PDP context</li>
<li>GTP-C for control reasons including:
<ul><li>setup and deletion of PDP contexts</li>
<li>verification of GSN reachability</li>
<li>updates; e.g., as subscribers move from one SGSN to another.</li></ul></li>
<li>GTP' for transfer of charging data from GSNs to the charging function.</li></ul>
<p>GGSNs and SGSNs (collectively known as GSNs) listen for GTP-C messages on UDP port 2123 and for GTP-U messages on port 2152.  This communication happens within a single network or may, in the case of international roaming, happen internationally, probably across a <a href="/facts/GPRS_Roaming_Exchange/URM4p6bh">GPRS roaming exchange</a> (GRX).
</p><p>The <i>Charging Gateway Function</i> (CGF) listens to <a href="/facts/GTP%27/58eG8tmJ">GTP'</a> messages sent from the GSNs on TCP/UDP port 3386.  The core network sends charging information to the CGF, typically including PDP context activation times and the quantity of data which the end user has transferred.  However, this communication which occurs within one network is less standardized and may, depending on the vendor and configuration options, use proprietary encoding or even an entirely proprietary system.
</p>
<h2 id="use-on-the-iups-interface">Use on the IuPS interface</h2>
<p>GTP-U is used on the IuPS between the GPRS core network and the RAN, however the GTP-C protocol is not used.  In this case, <a href="/facts/RANAP/LBmEFKYe">RANAP</a> is used as a control protocol and establishes GTP-U tunnels between the SGSN and the <a href="/facts/Radio_Network_Controller/kHofdQGC">radio network controller</a> (RNC).
</p>
<h2 id="protocol-stack">Protocol Stack</h2>
<table><tbody><tr><td>Application Protocols</td></tr><tr><td>IP (user)</td></tr><tr><td>GTP</td></tr><tr><td>UDP</td></tr><tr><td>IP</td></tr><tr><td>Layer 2 (e.g., WAN or Ethernet)</td></tr><tr><td>GTP-U protocol stack</td></tr></tbody></table>
<p>GTP can be used with <a href="/facts/User_Datagram_Protocol/dxLU0D6q">UDP</a> or <a href="/facts/Transmission_Control_Protocol/WW4sPrt9">TCP</a>. GTP version 1 is used only on UDP.
</p><p>As of 2018<a href="https://en.wikipedia.org/w/index.php?title=GPRS_Tunnelling_Protocol&action=edit">[update]</a> there are three versions defined, versions 0, 1 and 2. Version 0 and version 1 differ considerably in structure. In version 0, the signalling protocol (the protocol which sets up the tunnels by activating the PDP context) is combined with the tunnelling protocol on one port. Versions 1 and 2 are each effectively two protocols, one for <i>control</i> (called GTP-C) and one for <i>user</i> data tunneling (called GTP-U).  GTP version 2 is different to version 1 only in GTP-C.  This is due to 3GPP defining enhancements to GTP-C for EPS in version 2 to improve bearer handling.
</p><p>GTP-U is also used to transport user data from the RNC to the SGSN in UMTS networks.  However, in this case signalling is done using RANAP instead of GTP-C.
</p>
<h2 id="historical-gtp-versions">Historical GTP versions</h2>
<p>The original version of GTP (version 0) had considerable differences from the current versions (versions 1,2):
</p>
<ul><li>the tunnel identification was non-random;</li>
<li>options were provided for transporting <a href="/facts/X.25/yaGPqw2Y">X.25</a>;</li>
<li>the fixed port number 3386 was used for all functions (not just charging as in GTPv1);</li>
<li>TCP was allowed as a transport option instead of UDP, but support for this was optional;</li>
<li>subscription-related fields such as quality of service were more limited.</li></ul>
<p>The non-random TEID in version 0 represented a security problem if an attacker had access to any roaming partner's network, or could find some other way to remotely send packets to the GPRS backbone.  Version 0 is going out of use and being replaced by version 1 in almost all networks.  Fortunately, however the use of different port numbers allows easy blocking of version 0 through simple IP access lists.
</p>
<h2 id="gtp-standardization">GTP standardization</h2>
<p>GTP was originally standardized within <a href="/facts/ETSI/8rJbbhPg">ETSI</a> (GSM standard 09.60 <a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a>).  With the creation of the UMTS standards this was moved over to the <a href="/facts/3GPP/TBrQYKFF">3GPP</a> which, as of 2005<a href="https://en.wikipedia.org/w/index.php?title=GPRS_Tunnelling_Protocol&action=edit">[update]</a> maintains it as 3GPP standard 29.060.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a>  GTP' uses the same message format, but its special uses are covered in standard 32.295 along with the standardized formats for the charging data it transfers.
</p><p>Later versions of TS 29.060 deprecate GTPv1/v0 interworking <a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> such that there is no fallback in the event that the GSN does not support the higher version.
</p><p>GTPv2 (for evolved packet services) went into draft in early 2008 and was released in December of that year. GTPv2 offers fallback to GTPv1 via the earlier "Version Not Supported" mechanism but explicitly offers no support for fallback to GTPv0.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Proxy_Mobile_IPv6/mj9K5Ewh">Proxy Mobile IPv6</a></li>
<li><a href="/facts/Mobile_IP/55FC9Exv">Mobile IP</a></li>
<li><a href="/facts/PFCP/2GR8sQ6g">PFCP</a></li>
<li><a href="/facts/RANAP/LBmEFKYe">RANAP</a></li></ul>
<h2 id="notes">Notes</h2>

<ul><li>GSM standard 09.60, ETSI, 1996–98, this standard covers the original version 0 of GTP.</li>
<li><i>3GPP TS 29.060 V6.9.0 (2005-06)</i>, 3rd Generation Partnership Project, 650 Route des Lucioles - Sophia Antipolis, Valbonne - FRANCE, 2005–06.  This is the primary standard defining all of the GTP variants for GTP version 1.</li>
<li><i>3GPP TS 32.295 V6.1.0 (2005-06)</i>, 3rd Generation Partnership Project, 650 Route des Lucioles - Sophia Antipolis, Valbonne - FRANCE, 2005–06.  This standard covers using GTP for charging.</li>
<li><i>3GPP TS 29.274 V8.1.0 (2009-03)</i>, 3rd Generation Partnership Project, 650 Route des Lucioles - Sophia Antipolis, Valbonne - FRANCE, 2009–03.  GTPv2 for evolved GPRS.</li></ul>
<h2 id="external-links">External links</h2>
<ul><li><a href="http://www.3gpp.org">The 3GPP web site, home of the GTP standard</a></li>
<li><a href="http://sourceforge.net/projects/nwgtpv2">Free and open source implementation of GPRS Tunnelling Protocol version 2 (GTPv2) or Evolved GTP (eGTP)</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>3GPP TS 29.060 section 6 <a href="http://www.3gpp.org/ftp/Specs/html-info/29060.htm" target="_blank">http://www.3gpp.org/ftp/Specs/html-info/29060.htm</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>3GPP TS 29.274 section 5 <a href="http://www.3gpp.org/ftp/Specs/html-info/29274.htm" target="_blank">http://www.3gpp.org/ftp/Specs/html-info/29274.htm</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>3GPP TS 29.060 section 7 <a href="http://www.3gpp.org/ftp/Specs/html-info/29060.htm" target="_blank">http://www.3gpp.org/ftp/Specs/html-info/29060.htm</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>"3GPP TS 09.60 version 7.10.0 Release 1998" (PDF). etsi.org. <a href="https://www.etsi.org/deliver/etsi_ts/101300_101399/101347/07.10.00_60/ts_101347v071000p.pdf" target="_blank">https://www.etsi.org/deliver/etsi_ts/101300_101399/101347/07.10.00_60/ts_101347v071000p.pdf</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>"3GPP TS 29.060 v16.0.0" (PDF). etsi.org. <a href="https://www.etsi.org/deliver/etsi_ts/129000_129099/129060/16.00.00_60/ts_129060v160000p.pdf" target="_blank">https://www.etsi.org/deliver/etsi_ts/129000_129099/129060/16.00.00_60/ts_129060v160000p.pdf</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
<li id="fn:6"><p>"3GPP TS 29.060 v16.0.0 Section 4.2" (PDF). etsi.org. <a href="https://www.etsi.org/deliver/etsi_ts/129000_129099/129060/16.00.00_60/ts_129060v160000p.pdf" target="_blank">https://www.etsi.org/deliver/etsi_ts/129000_129099/129060/16.00.00_60/ts_129060v160000p.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li>
</ol>

GPRS Tunnelling Protocol open-in-new

GPRS Tunnelling Protocol