ETSI EN 301 347 V6.4.0 (1999-08)
Digital cellular telecommunications system (Phase 2+) (GSM); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface; (GSM 09.60 version 6.4.1 Release 1997)
Digital cellular telecommunications system (Phase 2+) (GSM); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface; (GSM 09.60 version 6.4.1 Release 1997)
DEN/SMG-030960Q6
Digitalni celični telekomunikacijski sistem (faza 2+) – Splošna radijska storitev s paketiranimi podatki (GPRS) – Protokol tuneliranja v GPRS (GTP) prek vmesnika Gn in Gp – (GSM 09.60, različica 6.4.1, izdaja 1997)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital cellular telecommunications system (Phase 2+) (GSM); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface; (GSM 09.60 version 6.4.1 Release 1997)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:EN 301 347 Version 6.4.1SIST EN 301 347 V6.4.1:2003en01-december-2003SIST EN 301 347 V6.4.1:2003SLOVENSKI
STANDARD
SIST EN 301 347 V6.4.1:2003
ETSI EN 301 347 V6.4.1 (1999-11)European Standard (Telecommunications series)Digital cellular telecommunications system (Phase 2+);General Packet Radio Service (GPRS);GPRS Tunnelling Protocol (GTP)across the Gn and Gp Interface;(GSM 09.60 version 6.4.1 Release 1997)GLOBAL SYSTEM
FOR MOBILE COMMUNICATIONSRSIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)2(GSM 09.60 version 6.4.1 Release 1997)ReferenceDEN/SMG-030960Q6 (ch0031co.PDF)KeywordsDigital cellular telecommunications system,Global System for Mobile communications (GSM)ETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frImportant noticeThis ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing orperceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).In case of dispute, the reference should be the printing on ETSI printers of the PDF version kept on a specific networkdrive within ETSI Secretariat.Copyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)3(GSM 09.60 version 6.4.1 Release 1997)ContentsIntellectual Property Rights.6Foreword.61Scope.72References.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.94General.95Transmission order and bit definitions.106GTP header.117Signalling Plane.127.1Signalling protocol.127.2Signalling Message Formats.137.3Usage of the GTP Header.147.4Path Management messages.147.4.1Echo Request.147.4.2Echo Response.157.4.3Version Not Supported.157.5Tunnel Management messages.157.5.1Create PDP Context Request.157.5.2Create PDP Context Response.177.5.3Update PDP Context Request.197.5.4Update PDP Context Response.207.5.5Delete PDP Context Request.217.5.6Delete PDP Context Response.217.5.7Create AA PDP Context Request.227.5.8Create AA PDP Context Response.237.5.9Delete AA PDP Context Request.247.5.10Delete AA PDP Context Response.257.5.11Error Indication.257.5.12PDU Notification Request.267.5.13PDU Notification Response.267.5.14PDU Notification Reject Request.277.5.15PDU Notification Reject Response.277.6Location Management messages.287.6.1Send Routeing Information for GPRS Request.287.6.2Send Routeing Information for GPRS Response.297.6.3Failure Report Request.297.6.4Failure Report Response.307.6.5Note MS GPRS Present Request.307.6.6Note MS GPRS Present Response.317.7Mobility Management messages.317.7.1Identification Request.317.7.2Identification Response.327.7.3SGSN Context Request.327.7.4SGSN Context Response.337.7.5SGSN Context Acknowledge.347.8Reliable delivery of signalling messages.357.9Information elements.357.9.1Cause.367.9.2International Mobile Subscriber Identity (IMSI).38SIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)4(GSM 09.60 version 6.4.1 Release 1997)7.9.3Routeing Area Identity (RAI).387.9.4Temporary Logical Link Identity (TLLI).397.9.5Packet TMSI (P-TMSI).397.9.6Quality of Service (QoS) Profile.407.9.7Spare.407.9.8Reordering Required.407.9.9Authentication Triplet.407.9.10Spare.417.9.11MAP Cause.417.9.12P-TMSI Signature.417.9.13MS Validated.417.9.14Recovery.427.9.15Selection mode.427.9.16Flow Label Data I.437.9.17Flow Label Signalling.437.9.18Flow Label Data II.437.9.19Charging ID.447.9.20End User Address.447.9.21MM Context.467.9.22PDP Context.477.9.23Access Point Name.507.9.24Protocol Configuration Options.507.9.25GSN Address.507.9.26Private Extension.518Transmission Plane.518.1Protocol Stack.528.1.1Usage of the GTP Header.528.1.1.1Usage of the Sequence Number.528.2Tunnelling between SGSNs.538.3Tunnelling between GGSNs.539Path Protocols.539.1UDP/IP.539.1.1UDP Header.539.1.1.1Signalling request messages.539.1.1.2Signalling response messages.539.1.1.3Encapsulated T-PDUs.539.1.2IP Header.539.1.2.1Signalling request messages and Encapsulated T-PDUs.539.1.2.2Signalling response messages.549.2TCP/IP.549.2.1TCP Header.549.2.2IP Header.5410Error handling.5410.1Protocol errors.5410.1.1Different GTP versions.5510.1.2GTP Message too short.5510.1.3Unknown GTP signalling message.5510.1.4Unexpected GTP signalling message.5510.1.5Missing mandatorily present information element.5510.1.6Invalid Length.5510.1.7Invalid mandatory information element.5510.1.8Invalid optional information element.5510.1.9Unknown information element.5610.1.10Out of sequence information elements.5610.1.11Unexpected information element.5610.1.12Repeated information elements.5610.1.13Incorrect optional information elements.5610.2Path failure.56SIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)5(GSM 09.60 version 6.4.1 Release 1997)10.3MS detach.5610.4Restoration and Recovery.5711Inter-PLMN GTP communication over the Gp interface.5712IP, the networking technology used by GTP.5712.1IP version.5712.2IP fragmentation.5712.2.1MO direction.5712.2.2MT direction.5812.2.3Tunnelling from old to new SGSN.5813GTP parameters.5813.1Timers.5813.2Others.58Annex A (informative):Naming convention.63A.1Routing Area Identities.63A.2GPRS Support Nodes.63Annex B (Informative):A method for sequence number checking.64Annex C (Informative):Document change history.65History.66SIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)6(GSM 09.60 version 6.4.1 Release 1997)Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server(http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee Special MobileGroup (SMG).The present document defines the Gn and Gp interfaces for the General Packet Radio Service (GPRS) within the digitalcellular telecommunications system (Phase 2+).The contents of the present document are subject to continuing work within SMG and may change following formalSMG approval. Should SMG modify the contents of the present document, it will then be re-submitted for OAP by ETSIwith an identifying change of release date and an increase in version number as follows:Version 6.x.ywhere:6indicates Release 1997 of GSM Phase 2+xthe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,etc.ythe third digit is incremented when editorial only changes have been incorporated in the specification.National transposition datesDate of adoption of this EN:5 November 1999Date of latest announcement of this EN (doa):29 February 2000Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 August 2000Date of withdrawal of any conflicting National Standard (dow):31 August 2000SIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)7(GSM 09.60 version 6.4.1 Release 1997)1ScopeThe present document defines the Gn and Gp interfaces for the General Packet Radio Service (GPRS).2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.• References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.• For a specific reference, subsequent revisions do not apply.• For a non-specific reference, the latest version applies.• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.• For this Release 1997 document, references to GSM documents are for Release 1997 versions (version 6.x.y).[1]GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations andacronyms".[2]GSM 03.03: “Digital cellular telecommunications system (Phase 2+); Numbering, addressing andidentification”.[3]GSM 03.07: “Digital cellular telecommunications system (Phase 2+); Restoration Procedures”[4]GSM 03.20: “Digital cellular telecommunications system (Phase 2+); Security related networkfunctions”[5]GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet RadioService (GPRS); Service Description; Stage 2".[6]GSM 03.64: “Digital cellular telecommunications system (Phase 2+); General Packet RadioService (GPRS); Overall description of the GPRS Radio Interface; Stage 2”[7]GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer3 - specification".[8]GSM 04.64: “Digital cellular telecommunications system (Phase 2+); Mobile Station - ServingGPRS Support Node (MS-SGSN) Logical Link Control (LLC) Layer Specification”[9]GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part(MAP) specification”.SIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)8(GSM 09.60 version 6.4.1 Release 1997)[10]STD 0005: “Internet Protocol”, J. Postel.[11]STD 0006: “User Datagram Protocol”, J. Postel.[12]STD 0007: “Transmission Control Protocol”, J. Postel.[13]RFC 1700: “Assigned Numbers”, J. Reynolds and J. Postel.[14]RFC 2181: “Clarifications to the DNS Specification”, R. Elz and R. Bush.[15]ITU-T Recommendation X.25: "Interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for terminals operating in the packet mode and connected to publicdata networks by dedicated circuit".[16]ITU-T Recommendation X.121: "International Numbering Plan for Public Data Networks".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following terms and definitions apply:ConditionalWhen the presence requirement for the information element is conditional, the receivingprotocol level can check the presense or absence of an IE based on the receivedinformation.G-PDU: A T-PDU plus a GTP header. A G-PDU is sent in a path.GTP-Flow:A GTP flow is defined by the unidirectional virtual aggregation of G-PDUs and/orsignalling messages related to one or more GTP tunnels. A GTP flow is identified by a FlowLabel included in the GTP header. The meaning of the Flow Label is transparent for thetransmitter side, only the receiver may evaluate the Flow Label.GTP tunnel:A GTP tunnel is defined by two associated PDP Contexts in different GSN nodes and isidentified with a Tunnel ID. A GTP tunnel is necessary to forward packets between anexternal packet data network and a MS user.MM Context:The information sets held in MS and GSNs for a GPRS subscriber related to mobilitymanagement (MM) (please refer to the MM Context Information Element).MM Context ID:IMSI or equivalent for use in conjunction with Anonymous Access (please refer to sectionGTP Header).NSAPI:Network Service Access Point Identifier. An integer value in the range [0; 15], identifying acertain PDP Context. It identifies a PDP context belonging to a specific MM Context ID.Path:The UDP/IP path and TCP/IP path are examples of paths that may be used to multiplexGTP tunnels.Path Protocol:The Path Protocol is the protocol(s) used as a bearer of GTP between GSNs.PDP:A Packet Data Protocol (PDP) is a network protocol used by an external packet datanetwork interfacing to GPRS.PDP Context:The information sets held in MS and GSNs for a PDP address (please refer to the PDPContext Information Element).Quality of Service :Quality of Service may be applicable for the GPRS backbone if the path media supports it.Separate paths with different priorities may be defined between a GSN pair. However, thepossible use of QoS in the GGSN is outside the scope of the GTP specification.SIST EN 301 347 V6.4.1:2003
ETSIETSI EN 301 347 V6.4.1 (1999-11)9(GSM 09.60 version 6.4.1 Release 1997)Signalling message:GTP signalling messages are exchanged between GSN pairs in a path. The signallingmessages are used to transfer GSN capability information between GSN pairs and to create,update and delete GTP tunnels.TCP/IP path:A TCP/IP path is a reliable connection-oriented path defined by two end-points and an end-point is defined by an IP address and a TCP port number. TCP/IP paths should be usedwhen the T-PDUs are based on connection-oriented protocols, such as the X.25 packet layerprotocol.T-PDU: An original packet, for example an IP datagram, from a MS or a network node in anexternal packet data network. A T-PDU is the payload that is tunnelled in the GTP tunnel.TID:A Tunnel ID (TID) consists of a MM Context ID and a NSAPI.UDP/IP path:A UDP/IP path is a connection-less path defined by two end-points and an end-point isdefined by an IP address and a UDP port number. A UDP/IP path carries G-PDUs between
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.