Content for  TS 29.060  Word version:  17.4.0

Top   Top   None   None   Next
1…   6…   8…


1  Scopep. 10

The present document defines the second version of GTP used on:
  • the Gn and Gp interfaces of the General Packet Radio Service (GPRS);
  • the Iu, Gn and Gp interfaces of the UMTS system.
From release 8 onwards, the normative specification of the user plane of GTP version 1 is TS 29.281. All provisions about GTPv1 user plane in the present document shall be superseded by TS 29.281.
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  Referencesp. 10

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.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 23.003: "Numbering, addressing and identification".
TS 23.007: "Restoration procedures".
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
TS 29.002: "Mobile Application Part (MAP) specification".
TS 25.413: "UTRAN Iu interface RANAP signalling".
TS 33.102: "3G security; Security architecture".
TS 43.020: " Security related network functions".
[10]  Void.
TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification".
RFC 791  (STD 0005): "Internet Protocol", J. Postel.
RFC 768  (STD 0006): "User Datagram Protocol", J. Postel.
RFC 3232:  "Assigned numbers", J. Reynolds.
[15]  Void.
[16]  Void.
TS 23.121: "Architectural requirements for Release 1999".
TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
TS 23.236: "Intra domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS protocol".
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
TS 25.414: "UTRAN Iu interface data transport and transport signalling".
TS 23.271: " Technical Specification Group Services and System Aspects; Functional stage 2 description of LCS".
[25]  Void.
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS) Architecture and Functional Description".
TS 29.061: "Interworking beween the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN) "
TS 23.040: "Technical realization of the Short Message Service (SMS)".
[29]  Void.
[30]  Void.
TS 32.422: "Subscriber and equipment trace: Trace Control and Configuration Management".
TS 32.423: "Subscriber and equipment trace: Trace data definition and management".
TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer".
TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR) parameter description".
TS 23.251: "Network Sharing; Architecture and Functional Description".
RFC 3588:  "Diameter Base Protocol"
TS 43.129: " Packet-switched handover for GERAN A/Gb mode; Stage 2".
TS 44.065: "Mobile Station (MS) - Serving GPRS Support Node (SGSN);Subnetwork Dependent Convergence Protocol (SNDCP)".
TS 23.203: "Policy and charging control architecture; Stage 2".
TR 25.999: " HSPA Evolution (FDD)".
TS 29.281: "GPRS Tunnelling Protocol User Plane (GTPv1-U)".
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
TS 29.212: "Policy and Charging Control (PCC); Reference points".
RFC 4607:  "Source-Specific Multicast for IP".
RFC 1035:"Domain  Names - Implementation and Specification".
TS 29.303: "Domain Name System Procedures; Stage 3".
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
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)".
TS 23.292: "IP Multimedia Subsystem (IMS) centralized services".
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
RFC 2460:  "Internet Protocol, Version 6 (IPv6) Specification".
RFC 5735:  "Special Use IPv4 Addresses".
RFC 5905:  "Network Time Protocol Version 4: Protocol and Algorithms Specification".
TS 32.299: "Telecommunication management; Charging management; Diameter charging application".
TS 23.380: "IMS Restoration Procedures".
TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
TS 29.272: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes; stage 3".
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".

3  Definitions and abbreviationsp. 12

3.1  Definitionsp. 12

For the purposes of the present document, the following terms and definitions apply:
Enhanced Network Service Access Point Identifier (Enhanced NSAPI):
integer value in the range [128; 255], identifying a certain Multimedia Broadcast/Multicast Service (MBMS) UE Context. G-PDU: is a user data message, It consists of a T-PDU plus a GTP header
GTP Tunnel:
in the GTP-U plane is defined for each PDP Context or each MBMS service in the GSNs and/or each RAB in the RNC. A GTP tunnel in the GTP-C plane is defined for all PDP Contexts with the same PDN Connection (for Tunnel Management messages and UE Specific MBMS message), for each MBMS service (for Service Specific MBMS messages) or for each MS (for other types of messages). A GTP tunnel is identified in each node with a TEID, an IP address and a UDP port number. A GTP tunnel is necessary to forward packets between an external packet data network and an MS user.
MBMS Bearer Context:
contains all information describing a particular MBMS bearer service.
MBMS UE Context:
contains UE-specific information related to a particular MBMS service that the UE has joined.
MM Context:
information sets held in MS and GSNs for a GPRS subscriber related to Mobility Management (MM) (please refer to the MM Context Information Element)
Network Service Access Point Identifier (NSAPI):
integer value in the range [0; 15], identifying a certain PDP Context. It identifies a PDP context belonging to a specific MM Context ID
UDP/IP path is used to multiplex GTP tunnels
Path Protocol:
protocol used as a bearer of GTP between GSNs or between a GSN and a RNC
Packet Data Protocol (PDP):
network protocol used by an external packet data network interfacing to GPRS
PDP Context:
information sets held in MS and GSNs for a PDP address or two IP addresses (one IPv4 and one IPv6 if PDP Type IPv4v6 is supported and used) (please refer to the PDP Context Information Element)
PDN Connection:
the association between a MS represented by one IPv4 address and/or one IPv6 prefix and a PDN represented by an APN. In this specification, "PDN connection" refers to a PDN connection through a GGSN.
PS Handover procedure:
used to enable MS with one or more packet flows to be moved between two cells with minimal service interruption through allocation of radio resources in the target cell while the MS is still in the source cell.
PS Handover XID Parameters:
contains LLC XID parameters (with SNDCP XID parameters contained within) that need to be transferred between SGSNs during the PS handover procedure.
Quality of Service (QoS):
may be applicable for the GPRS backbone and the Iu interface if the path media supports it. Separate paths with different priorities may be defined between a GSN pair or between a GSN and an RNC.
GTP-C Message:
GTP-C or control plane messages are exchanged between GSN/RNC pairs in a path. The control plane messages are used to transfer GSN capability information between GSN pairs, to create, update and delete GTP tunnels and for path management.
GTP-U Message:
GTP-U or user plane messages are exchanged between GSN pairs or GSN/RNC pairs in a path. The user plane messages are used to carry user data packets, and signalling messages for path management and error indication.
GTP Protocol Data Unit is either a GTP-C message or a GTP-U message
Signalling Message:
any GTP-PDU except the G-PDU
original packet, for example an IP datagram, from an MS or a network node in an external packet data network. A T-PDU is the payload that is tunnelled in the GTP-U tunnel.
Traffic Flow Template (TFTs):
used by GGSN to distinguish between different user payload packets and transmit packets with different QoS requirements via different PDP context but to the same PDP address or two IP addresses (one IPv4 and one IPv6 if PDP Type IPv4v6 is supported and used)
Tunnel Endpoint IDentifier (TEID):
unambiguously identifies a tunnel endpoint in the receiving GTP-U or GTP-C protocol entity. 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 RANAP, over the Iu) messages.
UDP/IP Path:
connection-less unidirectional or bidirectional path defined by two end-points. An IP address and a UDP port number define an end-point. A UDP/IP path carries GTP messages between GSN nodes, and between GSN and RNC nodes related to one or more GTP tunnels.
SCEF PDN Connection:
The PDN connection to the SCEF. Unless otherwise indicated in a clause or clause, "PDN Connection" does not refer to any SCEF PDN Connection.

3.2  Abbreviationsp. 14

Abbreviations used in the present document are listed in TR 21.905
For the purposes of the present document, the following additional abbreviations apply:
Automatic Device Detection
APN-Aggregate Maximum Bit Rate
Backbone Bearer
Correlation MSISDN
Don't Fragment
Direct Tunnel Indication
For Further Study
GPRS CAMEL Subscription Information
Gateway Mobile Location Centre
Gn interface
Interface between GPRS Support Nodes (GSNs) within a PLMN
Gp interface
Interface between GPRS Support Nodes (GSNs) in different PLMNs
GPRS Tunnelling Protocol
GTP Control
GTP User
Internet Assigned Number Authority
Internet Control Message Protocol
Information Element
Internet Group Management Protocol
Internet Protocol
Internet Protocol version 4
Internet Protocol version 6
Local Gateway
Local IP Access
MultiMedia Broadcast/Multicast Service
Multicast Listener Discover
Maximum Transmission Unit
Network Assisted Cell Change
Network Requested Support Network
Provision of User Equipment Specific Behaviour Information to Network Entities
Quality of Service
Radio Access Network
Radio Access Network Application Part
RAN Information Management
Radio Network Controller
Subscriber Profile ID for RAT/Frequency Priority
Session Transfer Number for SRVCC
Tunnel Endpoint IDentifier
Traffic Flow Template
User Datagram Protocol
UE- Aggregate Maximum Bit Rate
UMTS Terrestrial Radio Access Network

4  Generalp. 14

4.1  General Description |R8|p. 14

From release 8 onwards, the normative specification of the user plane of GTP version 1 is TS 29.281. All provisions about GTPv1 user plane in the present document shall be superseded by TS 29.281.
The present document defines the GPRS Tunnelling Protocol (GTP), i.e. the protocol between GPRS Support Nodes (GSNs) in the UMTS/GPRS backbone network. It includes both the GTP control plane (GTP-C) and data transfer (GTP-U) procedures. GTP also lists the messages and information elements used by the GTP based charging protocol GTP', which is described in TS 32.295.
GTP (GTP-C and GTP-U) is defined for the Gn interface, i.e. the interface between GSNs within a PLMN, and for the Gp interface between GSNs in different PLMNs. Only GTP-U is defined for the Iu interface between Serving GPRS Support Node (SGSN) and the UMTS Terrestrial Radio Access Network (UTRAN).
GTP-C is also used for roaming and inter access mobility between Gn/Gp SGSNs and MMEs as specified in Annex D of TS 23.401.
On the Iu interface, the Radio Access Network Application Part (RANAP) protocol and signalling part of GTP-U are performing the control function for user plane (GTP-U).
GTP' is defined for the interface between CDR generating functional network elements and Charging Gateway(s) within a PLMN. Charging Gateway(s) and GTP' protocol are optional, as the Charging Gateway Functionality may either be located in separate network elements (Charging Gateways), or alternatively be embedded into the CDR generating network elements (GSNs) when the GSN-CGF interface is not necessarily visible outside the network element. These interfaces relevant to GTP are between the grey boxes shown in Figure 1.
Copy of original 3GPP image for 3GPP TS 29.060, Fig. 1: GPRS Logical Architecture with interface name denotations
GTP allows multi-protocol packets to be tunnelled through the UMTS/GPRS Backbone between GSNs and between SGSN and UTRAN.
In the control plane, GTP specifies a tunnel control and management protocol (GTP-C) which allows the SGSN to provide packet data network access for an MS. Control Plane signalling is used to create, modify and delete tunnels. GTP also allows creation, and deletion of a single multicast service tunnel, that can be used for delivering packets to all the users who have joined a particular multicast service.
In the user plane, GTP uses a tunnelling mechanism (GTP-U) to provide a service for carrying user data packets.
The GTP-U protocol is implemented by SGSNs and GGSNs in the UMTS/GPRS Backbone and by Radio Network Controllers (RNCs) in the UTRAN. SGSNs and GGSNs in the UMTS/GPRS Backbone implement the GTP-C protocol. No other systems need to be aware of GTP. UMTS/GPRS MSs are connected to an SGSN without being aware of GTP.
It is assumed that there will be a many-to-many relationship between SGSNs and GGSNs. A SGSN may provide service to many GGSNs. A single GGSN may associate with many SGSNs to deliver traffic to a large number of geographically diverse mobile stations.

4.2  Removing support for GTPv1 to GTPv0 interworking |R8|p. 16

Support for GTPv1 to GTPv0 interworking is removed from 3GPP Rel-8 GTPv1 specification. Therefore, 3GPP Rel-8 and onwards GTPv1 entity may or may not listen to the well-known GTPv0 port 3386. If GTPv1 entity listens to the GTPv0 port, the entity should silently discard any received GTPv0 message.

5  Transmission Order and Bit Definitionsp. 16

The messages in this document shall be transmitted in network octet order starting with octet 1. Where information elements are repeated within a message the order shall be determined by the order of appearance in the table defining the information elements in the message.
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.

Up   Top   ToC