SIST EN 301 347 V7.1.1:2003
(Main)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 7.1.1 Release 1998)
- Abstract
SUBJECT GPRS Charging enhancements to GTP Introduction of the PDP-type PPP Introduction of the PDP type OSH:IHOSS GTP/GTP Protocol Type bit
- Status
- Published
- Publication Date
- 30-Nov-2003
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-2003
- Due Date
- 01-Dec-2003
- Completion Date
- 01-Dec-2003
- Mandate
- BC-T-330
SIST EN 301 347 V7.1.1:2003 is the Slovenian adoption of ETSI EN 301 347 Version 7.1.1 for GSM Release 1998. It specifies the GPRS Tunnelling Protocol (GTP) across the Gn and Gp interfaces, for use by GPRS network engineers, implementers, and testers working on SGSN and GGSN interworking. It also covers GPRS charging enhancements to GTP, the PDP type PPP, the PDP type OSP:IHOSS, and the GTP/GTP Protocol Type bit.
What does SIST EN 301 347 V7.1.1:2003 specify?
SIST EN 301 347 V7.1.1:2003 defines the protocol between GSN nodes in the GPRS backbone network. The document covers both signalling and user-data tunnelling, and it names the messages and information elements used by the GTP-based charging protocol GTP’.
The document is organized into clauses for scope, references, definitions, general principles, header coding, signalling plane, transmission plane, path protocols, error handling, inter-PLMN GTP communication over Gp, IP as the network technology, and GTP parameters. Annex A gives a naming convention, Annex B gives a method for sequence number checking, and Annex C gives the document change history.
| Annex | What it covers |
|---|---|
| A | Naming convention |
| B | Method for sequence number checking |
| C | Document change history |
What are the key requirements of SIST EN 301 347 V7.1.1:2003?
SIST EN 301 347 V7.1.1:2003 sets a fixed 20-octet GTP header for all GTP messages, with field meanings that change between signalling messages and tunnelled T-PDUs. In practice, implementers must fill the header differently depending on whether the message sets up control information or carries user data.
Signalling plane and tunnel control
Clause 7 defines the signalling procedures used to create, update, and delete GTP tunnels. The key message families are Path Management, Tunnel Management, Location Management, and Mobility Management. For an engineer, this means the SGSN and GGSN must exchange the right request and response messages at each PDP context procedure, and must keep the TID, FlowLabel, and address fields consistent.
EchoRequest and EchoResponse provide keep-alive handling for a path, and EchoRequest shall not be sent more often than every 60 seconds on each path. That matters because path failure detection is part of operational stability, not just packet forwarding.
PDP context procedures
CreatePDPContextRequest/Response, UpdatePDPContextRequest/Response, and DeletePDPContextRequest/Response control ordinary PDP context activation, modification, and deactivation. The corresponding AA versions do the same for anonymous access. These procedures carry QoS, APN, address, charging, and recovery information, so a system designer must preserve those fields across the SGSN-GGSN exchange.
Charging and network-requested activation
The document includes charging-related messages and information elements for GTP’. It also defines PDUNotificationRequest/Response/Reject and the GTP-MAP related Location Management messages used when network-requested PDP context activation is supported through a GTP-MAP protocol-converting GSN. In practice, this is the part that links packet delivery with charging and with HLR-driven reachability procedures.
Transmission plane and path protocols
Clause 8 defines tunnelling of T-PDUs between SGSN and GGSN. Clause 9 states that UDP/IP is the only path protocol defined for GTP signalling in this version, and it is also the recommended choice for connection-less T-PDUs. TCP/IP is the recommended choice for connection-oriented T-PDUs. This means the implementer must choose the path protocol according to whether the payload protocol needs connection-less or connection-oriented delivery.
Error handling and information coding
Clause 10 defines protocol error handling, including unsupported versions, short messages, missing mandatory information elements, invalid lengths, and unexpected messages. Clause 7.9 defines information elements using TLV or TV coding, with ascending Type order in messages. For compliance and interoperability, these coding rules are critical because peers reject malformed requests and may stop a procedure when a response is invalid.
What terms does SIST EN 301 347 V7.1.1:2003 define?
- G-PDU - A T-PDU plus a GTP header, carried in a path between GSN nodes.
- GTP tunnel - A tunnel defined by two associated PDP Contexts in different GSN nodes and identified by a Tunnel ID.
- PDP Context - The information set held in the MS and GSNs for a PDP address.
- T-PDU - The original packet being tunnelled, such as an IP datagram.
- TID - The Tunnel ID, made from a MMContextID and an NSAPI.
- QoS - Quality of Service, used in the backbone when the path media supports it.
- MMContext - The mobility management information set held for a GPRS subscriber.
Who uses SIST EN 301 347 V7.1.1:2003?
SIST EN 301 347 V7.1.1:2003 is used by SGSN and GGSN implementers, core-network engineers, protocol testers, and interoperability labs. It is also used by operators planning GPRS backbone behaviour, especially where path selection, context transfer, charging, and recovery handling must match between nodes.
In networks that use GTP-MAP protocol conversion, the standard also matters to teams working on GGSN-to-HLR signalling through a GTP-MAP protocol-converting GSN. Charging and operations teams use the charging-related fields and recovery behaviour when they validate CDR handling and restart recovery.
Which standards are used with SIST EN 301 347 V7.1.1:2003?
| Reference | What it contributes |
|---|---|
| GSM01.04 | Abbreviations and acronyms |
| GSM03.03 | Numbering, addressing, identification |
| GSM03.07 | Restoration procedures |
| GSM03.20 | Security-related network functions |
| GSM03.60 | GPRS service description and procedures |
| GSM03.64 | Overall description of the GPRS radio interface |
| GSM04.08 | Mobile radio interface layer 3, plus coding used by several information elements |
| GSM04.64 | LLC layer specification |
| GSM09.02 | MAP procedures and messages |
| STD0005 / STD0006 / STD0007 | IP, UDP, and TCP |
| RFC1700 / RFC2181 | Assigned numbers and DNS clarifications |
| ITU-T X.25 / X.121 | Packet-mode interface and numbering plan used for X.25-related addressing |
What does the SIST EN 301 347 V7.1.1:2003 document contain?
The document contains message tables for signalling, path management, tunnel management, location management, and mobility management, together with information-element tables for each message. It also gives the GTP header layout, the TID format, and the coding of important fields such as Cause, IMSI, RAI, TLLI, P-TMSI, QoS Profile, ChargingID, EndUserAddress, GSNAddress, and PrivateExtension.
Clause 8 provides the transmission-plane rules for tunnelling and sequence numbers, including how received T-PDUs are validated and reordered. Clause 9 describes UDP/IP and TCP/IP header use for GTP, while clause 10 defines the handling of version mismatches, missing mandatory data, invalid lengths, and other protocol errors.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 301 347 V7.1.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "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 7.1.1 Release 1998)". This standard covers: SUBJECT GPRS Charging enhancements to GTP Introduction of the PDP-type PPP Introduction of the PDP type OSH:IHOSS GTP/GTP Protocol Type bit
SUBJECT GPRS Charging enhancements to GTP Introduction of the PDP-type PPP Introduction of the PDP type OSH:IHOSS GTP/GTP Protocol Type bit
SIST EN 301 347 V7.1.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.50 - Global System for Mobile Communication (GSM). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 347 V7.1.1:2003 is associated with the following European legislation: Standardization Mandates: BC-T-330. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST EN 301 347 V7.1.1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
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 7.1.1 Release 1998)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 7.1.1SIST EN 301 347 V7.1.1:2003en01-december-2003SIST EN 301 347 V7.1.1:2003SLOVENSKI
STANDARD
ETSIEN301347V7.1.1(2000-01)EuropeanStandard(Telecommunicationsseries)Digitalcellulartelecommunicationssystem(Phase2+);GeneralPacketRadioService(GPRS);GPRSTunnellingProtocol(GTP)acrosstheGnandGpInterface(GSM09.60version7.1.1Release1998)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRSIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)2(GSM09.60version7.1.1Release1998)ReferenceREN/SMG-030960Q7KeywordsDigitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM)ETSIPostaladdressF-06921SophiaAntipolisCedex-FRANCEOfficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88Internetsecretariat@etsi.frIndividualcopiesofthisETSIdeliverablecanbedownloadedfromhttp://www.etsi.orgIfyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frImportantnoticeThisETSIdeliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.CopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)3(GSM09.60version7.1.1Release1998)ContentsIntellectualPropertyRights.6Foreword.61Scope.72References.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.94General.95Transmissionorderandbitdefinitions.106GTPheader.107SignallingPlane.127.1Signallingprotocol.127.2SignallingMessageFormats.137.3UsageoftheGTPHeader.137.4PathManagementmessages.147.4.1EchoRequest.147.4.2EchoResponse.157.4.3VersionNotSupported.157.5TunnelManagementmessages.157.5.1CreatePDPContextRequest.157.5.2CreatePDPContextResponse.177.5.3UpdatePDPContextRequest.197.5.4UpdatePDPContextResponse.197.5.5DeletePDPContextRequest.217.5.6DeletePDPContextResponse.217.5.7CreateAAPDPContextRequest.227.5.8CreateAAPDPContextResponse.237.5.9DeleteAAPDPContextRequest.247.5.10DeleteAAPDPContextResponse.257.5.11ErrorIndication.257.5.12PDUNotificationRequest.267.5.13PDUNotificationResponse.267.5.14PDUNotificationRejectRequest.277.5.15PDUNotificationRejectResponse.277.6LocationManagementmessages.287.6.1SendRouteingInformationforGPRSRequest.287.6.2SendRouteingInformationforGPRSResponse.297.6.3FailureReportRequest.297.6.4FailureReportResponse.307.6.5NoteMSGPRSPresentRequest.307.6.6NoteMSGPRSPresentResponse.317.7MobilityManagementmessages.317.7.1IdentificationRequest.317.7.2IdentificationResponse.327.7.3SGSNContextRequest.327.7.4SGSNContextResponse.337.7.5SGSNContextAcknowledge.347.8Reliabledeliveryofsignallingmessages.357.9Informationelements.357.9.1Cause.367.9.2InternationalMobileSubscriberIdentity(IMSI).38SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)4(GSM09.60version7.1.1Release1998)7.9.3RouteingAreaIdentity(RAI).387.9.4TemporaryLogicalLinkIdentity(TLLI).397.9.5PacketTMSI(P-TMSI).397.9.6QualityofService(QoS)Profile.407.9.7Spare.407.9.8ReorderingRequired.407.9.9AuthenticationTriplet.407.9.10Spare.417.9.11MAPCause.417.9.12P-TMSISignature.417.9.13MSValidated.417.9.14Recovery.427.9.15Selectionmode.427.9.16FlowLabelDataI.437.9.17FlowLabelSignalling.437.9.18FlowLabelDataII.437.9.19ChargingID.447.9.20EndUserAddress.447.9.21MMContext.477.9.22PDPContext.487.9.23AccessPointName.517.9.24ProtocolConfigurationOptions.517.9.25GSNAddress.517.9.26ChargingGatewayAddress.527.9.27PrivateExtension.528TransmissionPlane.528.1ProtocolStack.538.1.1UsageoftheGTPHeader.538.1.1.1UsageoftheSequenceNumber.538.2TunnellingbetweenSGSNs.548.3TunnellingbetweenGGSNs.549PathProtocols.549.1UDP/IP.549.1.1UDPHeader.549.1.1.1Signallingrequestmessages.549.1.1.2Signallingresponsemessages.549.1.1.3EncapsulatedT-PDUs.549.1.2IPHeader.549.1.2.1SignallingrequestmessagesandEncapsulatedT-PDUs.559.1.2.2Signallingresponsemessages.559.2TCP/IP.559.2.1TCPHeader.559.2.2IPHeader.5510Errorhandling.5510.1Protocolerrors.5510.1.1DifferentGTPversions.5610.1.2GTPMessagetooshort.5610.1.3UnknownGTPsignallingmessage.5610.1.4UnexpectedGTPsignallingmessage.5610.1.5Missingmandatorilypresentinformationelement.5610.1.6InvalidLength.5610.1.7Invalidmandatoryinformationelement.5610.1.8Invalidoptionalinformationelement.5710.1.9Unknowninformationelement.5710.1.10Outofsequenceinformationelements.5710.1.11Unexpectedinformationelement.5710.1.12Repeatedinformationelements.5710.1.13Incorrectoptionalinformationelements.57SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)5(GSM09.60version7.1.1Release1998)10.2Pathfailure.5710.3MSdetach.5710.4RestorationandRecovery.5811Inter-PLMNGTPcommunicationovertheGpinterface.5812IP,thenetworkingtechnologyusedbyGTP.5812.1IPversion.5812.2IPfragmentation.5812.2.1MOdirection.5812.2.2MTdirection.5912.2.3TunnellingfromoldtonewSGSN.5913GTPparameters.5913.1Timers.5913.2Others.59AnnexA(informative):Namingconvention.64AnnexB(informative):Amethodforsequencenumberchecking.65AnnexC(informative):Documentchangehistory.66History.67SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)6(GSM09.60version7.1.1Release1998)IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbytheSpecialMobileGroup(SMG).ThepresentdocumentdefinestheGnandGpinterfacesfortheGeneralPacketRadioService(GPRS)withinthedigitalcellulartelecommunicationssystem(Phase2+).ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithinSMGandmaychangefollowingformalSMGapproval.ShouldSMGmodifythecontentsofthepresentdocument,itwillthenbere-submittedforOAPbyETSIwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:Version7.x.ywhere:7indicatesRelease1998ofGSMPhase2+xtheseconddigitisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.ythethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthespecification.NationaltranspositiondatesDateofadoptionofthisEN:7January2000DateoflatestannouncementofthisEN(doa):30April2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31October2000DateofwithdrawalofanyconflictingNationalStandard(dow):31October2000SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)7(GSM09.60version7.1.1Release1998)1ScopeThepresentdocumentdefinestheGnandGpinterfacesfortheGeneralPacketRadioService(GPRS).2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.•Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.•Foraspecificreference,subsequentrevisionsdonotapply.•Foranon-specificreference,thelatestversionapplies.•Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.•ForthisRelease1998document,referencestoGSMdocumentsareforRelease1998versions(version7.x.y).[1]GSM01.04:"Digitalcellulartelecommunicationssystem(Phase2+);Abbreviationsandacronyms".[2]GSM03.03:"Digitalcellulartelecommunicationssystem(Phase2+);Numbering,addressingandidentification".[3]GSM03.07:"Digitalcellulartelecommunicationssystem(Phase2+);RestorationProcedures".[4]GSM03.20:"Digitalcellulartelecommunicationssystem(Phase2+);Securityrelatednetworkfunctions".[5]GSM03.60:"Digitalcellulartelecommunicationssystem(Phase2+);GeneralPacketRadioService(GPRS);ServiceDescription;Stage2".[6]GSM03.64:"Digitalcellulartelecommunicationssystem(Phase2+);GeneralPacketRadioService(GPRS);OveralldescriptionoftheGPRSRadioInterface;Stage2".[7]GSM04.08:"Digitalcellulartelecommunicationssystem(Phase2+);Mobileradiointerfacelayer3-specification".[8]GSM04.64:"Digitalcellulartelecommunicationssystem(Phase2+);MobileStation-ServingGPRSSupportNode(MS-SGSN)LogicalLinkControl(LLC)LayerSpecification".[9]GSM09.02:"Digitalcellulartelecommunicationssystem(Phase2+);MobileApplicationPart(MAP)specification".[10]STD0005:"InternetProtocol",J.Postel.[11]STD0006:"UserDatagramProtocol",J.Postel.[12]STD0007:"TransmissionControlProtocol",J.Postel.[13]RFC1700:"AssignedNumbers",J.ReynoldsandJ.Postel.[14]RFC2181:"ClarificationstotheDNSSpecification",R.ElzandR.Bush.[15]ITU-TRecommendationX.25:"Interfacebetweendataterminalequipment(DTE)anddatacircuit-terminatingequipment(DCE)forterminalsoperatinginthepacketmodeandconnectedtopublicdatanetworksbydedicatedcircuit".SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)8(GSM09.60version7.1.1Release1998)[16]ITU-TRecommendationX.121:"InternationalNumberingPlanforPublicDataNetworks".3Definitionsandabbreviations3.1DefinitionsForthepurposeofthepresentdocument,thefollowingdefinitionsapply:ConditionalWhenthepresencerequirementfortheinformationelementisconditional,thereceivingprotocollevelcancheckthepresenceorabsenceofanIEbasedonthereceivedinformation.G-PDU:AT-PDUplusaGTPheader.AG-PDUissentinapath.GTP-Flow:AGTPflowisdefinedbytheunidirectionalvirtualaggregationofG-PDUsand/orsignallingmessagesrelatedtooneormoreGTPtunnels.AGTPflowisidentifiedbyaFlowLabelincludedintheGTPheader.ThemeaningoftheFlowLabelistransparentforthetransmitterside,onlythereceivermayevaluatetheFlowLabel.GTPtunnel:AGTPtunnelisdefinedbytwoassociatedPDPContextsindifferentGSNnodesandisidentifiedwithaTunnelID.AGTPtunnelisnecessarytoforwardpacketsbetweenanexternalpacketdatanetworkandaMSuser.MMContext:TheinformationsetsheldinMSandGSNsforaGPRSsubscriberrelatedtomobilitymanagement(MM)(pleaserefertotheMMContextInformationElement).MMContextID:IMSIorequivalentforuseinconjunctionwithAnonymousAccess(pleaserefertosectionGTPHeader).NSAPI:NetworkServiceAccessPointIdentifier.Anintegervalueintherange[0;15],identifyingacertainPDPContext.ItidentifiesaPDPcontextbelongingtoaspecificMMContextID.Path:TheUDP/IPpathandTCP/IPpathareexamplesofpathsthatmaybeusedtomultiplexGTPtunnels.PathProtocol:ThePathProtocolistheprotocol(s)usedasabearerofGTPbetweenGSNs.PDP:APacketDataProtocol(PDP)isanetworkprotocolusedbyanexternalpacketdatanetworkinterfacingtoGPRS.PDPContext:TheinformationsetsheldinMSandGSNsforaPDPaddress(pleaserefertothePDPContextInformationElement).QualityofService:QualityofServicemaybeapplicablefortheGPRSbackboneifthepathmediasupportsit.SeparatepathswithdifferentprioritiesmaybedefinedbetweenaGSNpair.However,thepossibleuseofQoSintheGGSNisoutsidethescopeoftheGTPspecification.Signallingmessage:GTPsignallingmessagesareexchangedbetweenGSNpairsinapath.ThesignallingmessagesareusedtotransferGSNcapabilityinformationbetweenGSNpairsandtocreate,updateanddeleteGTPtunnels.TCP/IPpath:ATCP/IPpathisareliableconnection-orientedpathdefinedbytwoend-pointsandanend-pointisdefinedbyanIPaddressandaTCPportnumber.TCP/IPpathsshouldbeusedwhentheT-PDUsarebasedonconnection-orientedprotocols,suchastheX.25packetlayerprotocol.T-PDU:Anoriginalpacket,forexampleanIPdatagram,fromaMSoranetworknodeinanexternalpacketdatanetwork.AT-PDUisthepayloadthatistunnelledintheGTPtunnel.TID:ATunnelID(TID)consistsofaMMContextIDandaNSAPI.SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)9(GSM09.60version7.1.1Release1998)UDP/IPpath:AUDP/IPpathisaconnection-lesspathdefinedbytwoend-pointsandanend-pointisdefinedbyanIPaddressandaUDPportnumber.AUDP/IPpathcarriesG-PDUsbetweenGSNnodesrelatedtooneormoreGTPtunnels.AUDP/IPpathshouldbeusedwhentheT-PDUsarebasedonconnection-lessprotocols,suchasIP.3.2AbbreviationsAbbreviationsusedinthepresentdocumentarelistedinGSM01.04.Forthepurposeofthepresentdocumentthefollowingadditionalabbreviationsapply:BBBackboneBearerDFDon’tFragmentFFSForFurtherStudyGTPGPRSTunnelingProtocolIANAInternetAssignedNumberAuthorityICMPInternetControlMessageProtocolIPInternetProtocolIPv4InternetProtocolversion4IPv6InternetProtocolversion6MTUMaximumTransmissionUnitQoSQualityofServiceTIDTunnelIDentifierTCPTransmissionControlProtocolUDPUserDatagramProtocolGninterfaceInterfacebetweenGPRSSupportNodes(GSNs)withinaPLMNGpinterfaceInterfacebetweenGPRSSupportNodes(GSNs)indifferentPLMNs4GeneralThisdocumentdefinestheGPRSTunnellingProtocol(GTP),i.e.theprotocolbetweenGSNnodesintheGPRSbackbonenetwork.ItincludesboththeGTPsignallinganddatatransferprocedures.ItalsoliststhemessagesandinformationelementsusedbytheGTPbasedchargingprotocolGTP’,whichisdescribedinGSM12.15.GTPisdefinedbothfortheGninterface,i.e.theinterfacebetweenGSNswithinaPLMN,andtheGpinterfacebetweenGSNsindifferentPLMNs.GTP’isdefinedfortheinterfacebetweenCDRgeneratingfunctionalnetworkelementsandChargingGateway(s)withinaPLMN.ChargingGateway(s)andGTP’protocolareoptional,astheChargingGatewayFunctionalitiesmayeitherbelocatedinseparatenetworkelements(ChargingGateways),oralternativelybeembeddedintotheCDRgeneratingnetworkelements(GSNs)whentheGSN-CGFinterfaceisnotnecessarilyvisibleoutsidethenetworkelement.TheseinterfacesrelevanttoGTParebetweenthegreyboxesshowninthefigurebelow.SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)10(GSM09.60version7.1.1Release1998)GiGnGcGpSignallingandDataTransferInterfaceSignallingInterfaceTEPDNUmGbTEMTBSSRGrorGcHLROtherPLMNSGSNGGSNSGSNGTP-MAPprotocolconvertingGSNGnUmGbTEMTBSSRSGSNGnFigure1:GPRSLogicalArchitecturewithinterfacenamedenotationsGTPallowsmultiprotocolpacketstobetunnelledthroughtheGPRSBackbonebetweenGPRSSupportNodes(GSNs).Inthesignallingplane,GTPspecifiesatunnelcontrolandmanagementprotocolwhichallowstheSGSNtoprovideGPRSnetworkaccessforaMS.Signallingisusedtocreate,modifyanddeletetunnels.Inthetransmissionplane,GTPusesatunnellingmechanismtoprovideaserviceforcarryinguserdatapackets.Thechoiceofpathisdependentonwhethertheuserdatatobetunnelledrequiresareliablelinkornot.TheGTPprotocolisimplementedonlybySGSNsandGGSNs.NoothersystemsneedtobeawareofGTP.GPRSMSsareconnectedtoaSGSNwithoutbeingawareofGTP.Itisassumedthattherewillbeamany-to-manyrelationshipbetweenSGSNsandGGSNs.ASGSNmayprovideservicetomanyGGSNs.AsingleGGSNmayassociatewithmanySGSNstodelivertraffictoalargenumberofgeographicallydiversemobilestations.5TransmissionorderandbitdefinitionsThemessagesinthisdocumentshallbetransmittedinnetworkoctetorderstartingwithoctet1.ThemostsignificantbitofanoctetinaGTPmessageisbit8.IfavalueinaGTPmessagespansseveraloctetsandnothingelseisstated,themostsignificantbitisbit8oftheoctetwiththelowestnumber.6GTPheaderTheGTPheadershallbeafixedformat20-octetheaderusedforallGTPmessages.-Versionbits:IfthePTbitis‘1’(indicatingaGTPmessage),theVersionshallbesetto0toindicatethis,thefirstversionofGTP.Forthetreatmentofotherversions,seesection10.1.1,"DifferentGTPversions".SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)11(GSM09.60version7.1.1Release1998)-PT(ProtocolType)bitindicateswhetherthemessageisaGTPmessage(whenPTis‘1’)oraGTP’message(whenPTis‘0’).GTPisdescribedinthisdocumentandtheGTP’protocolinGSM12.15.NotethattheinterpretationoftheheaderfieldsmaybedifferentinGTP’thaninGTP.-Spare‘1’:Theseunusedbitsshallbesetto‘1’bythesendingsideandshallnotbeevaluatedbythereceivingside.-SNNisaflagindicatingifSNDCPN-PDUNumberisincludedornot.-MessageTypeindicatesthetypeofGTPmessage.-LengthindicatesthelengthinoctetsoftheGTPmessage(G-PDU),excludingtheGTPheader.Bit8ofoctet3isthemostsignificantbitandbit1ofoctet4istheleastsignificantbitofthelengthfield.-SequenceNumberisatransactionidentityforsignallingmessagesandanincreasingsequencenumberfortunnelledT-PDUs.-SNDCPN-PDUNumberisusedattheInterSGSNRouteingAreaUpdateproceduretoco-ordinatethedatatransmissionbetweentheMSandSGSN.-TIDisthetunnelidentifierthatpointsoutMMandPDPcontexts(seeFigure3:TunnelID(TID)format).-TheflowlabelidentifiesunambiguouslyaGTPflow.AllfieldsintheGTPheadershallalwaysbepresentbutthecontentofthefieldsdiffersdependingoniftheheaderisusedforsignallingmessages(seethesub-sectionUsageoftheGTPHeaderinthesectionSignallingPlane)orT-PDUs(seethesub-sectionUsageoftheGTPHeaderinthesectionTransmissionPlane).BitsOctets876543211VersionPTSpare‘111‘SNN2MessageType3-4Length5-6SequenceNumber7-8FlowLabel9SNDCPN-PDULLCNumber10Spare‘11111111‘11Spare‘11111111‘12Spare‘11111111‘13-20TID1)LLCframenumber(continued)Figure2:OutlineofGTPheaderSIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)12(GSM09.60version7.1.1Release1998)MNCdigit1MCCdigit287643215BitsOctets24531678MCCdigit1MCCdigit3MSINdigit1MNCdigit2MSINdigit3MSINdigit2MSINdigit5MSINdigit4MSINdigit7MSINdigit6MSINdigit9MSINdigit8NSAPIMSINdigit10NOTE1:TheMCC,MNCandMSINarepartsoftheIMSIdefinedinGSM03.03.ForAnonymousAccess,theMSINshallbereplacedbyanumberassignedbytheparticularPLMN.TheassignednumbershallnotcollidewithanyMSINusedinthePLMNandshallbeuniquewithinthePLMN.NOTE2:MSINdigitsnotusedshallbesettoF(HEX).Figure3:TunnelID(TID)format7SignallingPlaneThesignallingplaneinthiscaserelatestoGPRSMobilityManagementfunctionslikeforexampleGPRSAttach,GPRSRouteingAreaUpdateandActivationofPDPContexts.ThesignallingbetweenGSNnodesshallbeperformedbytheGPRSTunnellingProtocol(GTP).GSNGn,GpGSNGTPPathProtocolGTPPathProtocolFigure4:SignallingPlane-Protocolstack7.1SignallingprotocolTheGTPsignallingflowshallbelogicallyassociatedwith,butseparatefrom,theGTPtunnels.ForeachGSN-GSNpaironeormorepathsexist.Oneormoretunnelsmayuseeachpath.GTPshallbethemeansbywhichtunnelsareestablished,used,managedandreleased.Apathmaybemaintainedbykeep-aliveechomessages.ThisensuresthataconnectivityfailurebetweenGSNscanbedetectedinatimelymanner.SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)13(GSM09.60version7.1.1Release1998)7.2SignallingMessageFormatsGTPdefinesasetofsignallingmessagesbetweentwoassociatedGSNs.Thesignallingmessagestobeusedaredefinedinthetablebelow.Table1:SignallingmessagesMessageTypevalue(Decimal)SignallingmessageReference0Forfutureuse.Shallnotbesent.Ifreceived,shallbetreatedasanUnknownmessage.1EchoRequest7.4.12EchoResponse7.4.23VersionNotSupported7.4.34NodeAliveRequestGSM12.155NodeAliveResponseGSM12.156RedirectionRequestGSM12.157RedirectionResponseGSM12.158-15Forfutureuse.Shallnotbesent.Ifreceived,shallbetreatedasanUnknownmessage.16CreatePDPContextRequest7.5.117CreatePDPContextResponse7.5.218UpdatePDPContextRequest7.5.319UpdatePDPContextResponse7.5.420DeletePDPContextRequest7.5.521DeletePDPContextResponse7.5.622CreateAAPDPContextRequest7.5.723CreateAAPDPContextResponse7.5.824DeleteAAPDPContextRequest7.5.925DeleteAAPDPContextResponse7.5.1026ErrorIndication7.5.1127PDUNotificationRequest7.5.1228PDUNotificationResponse7.5.1329PDUNotificationRejectRequest7.5.1430PDUNotificationRejectResponse7.5.1531Forfutureuse.Shallnotbesent.Ifreceived,shallbetreatedasanUnknownmessage.32SendRouteingInformationforGPRSRequest7.6.133SendRouteingInformationforGPRSResponse7.6.234FailureReportRequest7.6.335FailureReportResponse7.6.436NoteMSGPRSPresentRequest7.6.537NoteMSGPRSPresentResponse7.6.638-47Forfutureuse.Shallnotbesent.Ifreceived,shallbetreatedasanUnknownmessage.48IdentificationRequest7.7.149IdentificationResponse7.7.250SGSNContextRequest7.7.351SGSNContextResponse7.7.452SGSNContextAcknowledge7.7.553-239Forfutureuse.Shallnotbesent.Ifreceived,shallbetreatedasanUnknownmessage.240DataRecordTransferRequestGSM12.15241DataRecordTransferResponseGSM12.15242-254Forfutureuse.Shallnotbesent.Ifreceived,shallbetreatedasanUnknownmessage.255T-PDU8.1.17.3UsageoftheGTPHeaderForsignallingmessagestheGTPheadershallbeusedasfollows:SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)14(GSM09.60version7.1.1Release1998)-SNNshallbesetto0.-MessageTypeshallbesettotheuniquevaluethatisusedforeachtypeofsignallingmessage.-Lengthshallbethelength,inoctets,ofthesignallingmessageexcludingtheGTPheader.-SNDCPN-PDUNumber:thisfieldisnotyetusedinsignallingmessages.Itshallbesetto255bythesenderandshallbeignoredbythereceiver.-SequenceNumbershallbeamessagenumbervalidforapathoratunnel.WithinagivensetofcontiguousSequenceNumbersfrom0to65535,agivenSequenceNumbershall,ifused,unambiguouslydefineaGTPsignallingrequestmessagesentonthepathortunnel(seesectionReliabledeliveryofsignallingmessages).TheSequenceNumberinasignallingresponsemessageshallbecopiedfromthesignallingrequestmessagethattheGSNisreplyingto.-TID(seeFigure3:TunnelID(TID)format)shallbesetto0inallPathManagementmessages(seesectionPathManagementmessages),LocationManagementmessages(seesectionLocationManagementmessages)andMobilityManagementmessages(seesectionMobilityManagementmessages).IntheTunnelManagementmessages(seesectionTunnelManagementmessages),TIDshallbeusedtopointouttheMMandPDPContextsinthedestinationGSN.-InallPathManagementmessages(seesectionPathManagementmessages)andLocationManagementmessages(seesectionLocationManagementmessages)theFlowLabelisnotusedandshallbesetto0.IncaseofTunnelManagementmessageandMobilityManagementmessagestheFlowLabelissettotherequestedvalueandpointsouttheGTPflowexceptfortheCreatePDPContextRequestmessageaswellasIdentificationRequest/ResponseandSGSNContextRequestmessage(seesectionMobilityManagementmessages).TheGTPheadermaybefollowedbysubsequentinformationelementsdependentonthetypeofsignallingmessage.Onlyoneinformationelementofeachtypeisallowedinasinglesignallingmessage,exceptfortheAuthenticationTriplet,thePDPContextandtheFlowLabelDataIIinformationelementwhereseveraloccurrencesofeachtypeareallowed.BitsOctets876543211-20GTPheader21-nInformationElement(s)Figure5:GTPheaderfollowedbysubsequentInformationElements7.4PathManagementmessagesThePathManagementmessagesmaybesentbetweenanytypeofGSNpair.7.4.1EchoRequestAnEchoRequestmaybesentonapathtoanotherGSNtofindoutifthepeerGSNisalive(seesectionPathFailure).EchoRequestmessagesmaybesentforeachpathinuse.ApathisconsideredtobeinuseifatleastonePDPcontextusesthepathtotheotherGSN.WhenandhowoftenanEchoRequestmessagemaybesentisimplementationspecificbutanEchoRequestshallnotbesentmoreoftenthanevery60secondsoneachpath.AGSNshallbepreparedtoreceiveanEchoRequestatanytimeanditshallreplywithanEchoResponse.AGSNmayoptionallysendEchoRequestmessages.SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)15(GSM09.60version7.1.1Release1998)TheoptionalPrivateExtensioncontainsvendororoperatorspecificinformation.Table2:InformationelementsinanEchoRequestInformationelementPresencerequirementReferencePrivateExtensionOptional7.9.277.4.2EchoResponseThemessageshallbesentasaresponseofareceivedEchoRequest.TheRecoveryinformationelementcontainsthelocalRestartCounter(seesectionRestorationandRecovery)valuefortheGSNthatsendstheEchoResponsemessage.TheGSNthatreceivesanEchoResponsefromapeerGSNshallcomparetheRestartCountervaluereceivedwiththepreviousRestartCountervaluestoredforthatpeerGSN.Ifnopreviousvaluewasstored,theRestartCountervaluereceivedintheEchoResponseshallbestoredforthepeerGSN.IfthevalueofaRestartCounterpreviouslystoredforapeerGSNdiffersfromtheRestartCountervaluereceivedintheEchoResponsefromthatpeerGSN,theGSNthatsenttheEchoResponseshallbeconsideredasrestartedbytheGSNthatreceivedtheEchoResponse.ThenewRestartCountervaluereceivedshallbestoredbythereceivingentity,replacingthevaluepreviouslystoredforthesendingGSN.IfthesendingGSNisaGGSNandthereceivingGSNisaSGSN,theSGSNshallnotifyanaffectedMSnexttimetheMScontactstheSGSN.AnaffectedMSisanMSthathasatleastoneactivatedPDPcontextthatwasusingtherestartedGGSN.TheSGSNshallconsiderallPDPcontextsusingthepathasinactive.TheoptionalPrivateExtensioncontainsvendororoperatorspecificinformation.Table3:InformationelementsinanEchoResponseInformationelementPresencerequirementReferenceRecoveryMandatory7.9.14PrivateExtensionOptional7.9.277.4.3VersionNotSupportedThismessagecontainsonlytheGTPheaderandindicatesthelatestGTPversionthattheGTPentityontheidentifiedUDP/IPaddresscansupport.7.5TunnelManagementmessagesTheTunnelManagementmessagesarethecontrolandmanagementmessages,definedinGSM03.60,usedtocreate,updateanddeletetunnelstobeabletorouteT-PDUsbetweenaMSandanexternalpacketdatanetworkviaSGSNandGGSN.TheGMM/SMmessagesthatmaytriggerthesendingoftheTunnelManagementmessagesaredefinedinGSM04.08.7.5.1CreatePDPContextRequestACreatePDPContextRequestshallbesentfromaSGSNnodetoaGGSNnodeasapartoftheGPRSPDPContextActivationprocedure.TheGGSNIPaddresswheretheSGSNsendstheCreatePDPContextRequestisthefirstIPaddressinthelistofIPaddressesprovidedbytheDNSserver.AftersendingtheCreatePDPContextRequestmessage,theSGSNmarksthePDPcontextas‘waitingforresponse’.InthisstatetheSGSNshallacceptG-PDUsfromtheGGSNbutshallnotsendtheseG-PDUstotheMS.AvalidrequestinitiatesthecreationofatunnelbetweenaPDPContextinaSGSNandaPDPContextinaGGSN.Iftheprocedureisnotsuccessfullycompleted,theSGSNrepeatstheCreatePDPContextRequestmessagetothenextGGSNaddressinthelistofIPaddresses,ifthereisone.Ifthelistisexhaustedtheactivationprocedurefails.TheFlowLabelDataIfieldspecifiesadownlinkflowlabelforG-PDUswhichischosenbytheSGSN.TheGGSNshallincludethisflowlabelintheGTPheaderofallsubsequentdownlinkG-PDUswhicharerelatedtotherequestedPDPcontext.SIST EN 301 347 V7.1.1:2003
ETSIETSIEN301347V7.1.1(2000-01)16(GSM09.60version7.1.1Release1998)TheFlowLabelSignallingfieldspecifiesadownlinkflowlabelforsignallingmessageswhichischosenbytheSGSN.TheGGSNshallincludethisflowlabelintheGTPheaderofallsubsequentdownlinksignallingmessageswhicharerelatedtotherequestedPDPcontext.TheMSISDNoftheMSispassedtotheGGSNinsidetheCreatePDPContextRequest;Thisadditionalinformationcanbeusedwhenasecureaccesstoaremoteapplicationresidingonaserverisneeded.TheGGSNwouldbeinfactabletoprovidetheuseridentity(i.e.theMSISDN)totheremoteapplicationserver,providingitwiththeleveloftrustgrantedtousersthroughsuccessfullyperformingtheGPRSauthenticationprocedures,withouthavingtore-authenticatetheuserattheapplicationlevel.IftheMSrequestsadynamicPDPaddressandadynamicPDPaddressisallowed,thenthePDPAddressfieldintheEndUserAddressinformationelementshallbeempty.IftheMSrequestsastaticPDPAddressthenthePDPAddressfieldintheEndUserAddressinformationelementshallcontainthestaticPDPAddress.IncasethePDPaddressescarriedintheEndUserAddressandoptionallyintheProtocolConfigurationOptioninformationelementcontaincontradictinginformation,thePDPaddresscarriedintheEndUserAddressinformationelementtakesthehigherprecedence.TheQualityofServiceProfileinformationelementshallbetheQoSvaluestobenegotiatedbetweentheMSandtheSGSNatPDPContextactivation.TheSGSNshallincludeanSGSNAddressforsignallingandanSGSNaddressforusertraffic,whichmaydifferfromthatprovidedbytheunderlyingnetworkservice(e.g.IP).TheGGSNshallstoretheseSGSNAddressesandusethemwhensendingsignallingonthisGTPtunnelorG-PDUstotheSGSNfortheMS.TheSGSNshallincludeaRecoveryinformationelementintotheCreatePDPContextRequestiftheSGSNisincontactwiththeGGSNfortheveryfirsttimeoriftheSGSNhasrestartedrecentlyandthenewRestartCountervaluehasnotyetbeenindicatedtotheGGSN.TheGGSNthatreceivesaRecoveryinformationelementintheCreatePDPContextRequestmessageelementshallhandleitinthesamewayaswhenreceivinganEchoResponsemessage.TheCreatePDPContextRequestmessageshallbeconsideredasavalidactivationrequestforthePDPcontextincludedinthemessage.TheSGSNshallincludeeithertheMSprovidedAPN,asubscribedAPNoranSGSNselectedAPNinthemessage;theAccessPointNamemaybeusedbytheGGSNtodifferentiateaccessestodifferentexternalnetworks.TheSelectionModeinformationelementshallindicatetheoriginoftheAPNinthemessage.TheoptionalProtocolConfigurationOptionsinformationelementisapplicablefortheenduserprotocol‘IP’only.TheSGSNshallselectoneGGSNbasedontheuserprovidedorSGSNselectedAPN.TheGGSNmayhavealogicalnamethatisconvertedtoanaddress.Theconversionmaybeperformedwithanyname-to-addressfunction.Theconvertedaddressshallbestoredinthe"GGSNAddressinUse"fieldinthePDPcontextandbeusedduringtheentirelifetimeofthePDPcontext.NOTE:ADNSquerymaybeusedasthename-to-IPaddressmappingoftheGGSN.TheIPaddressreturnedintheDNSresponseisthenstoredinthe"GGSNAddressinUse"fieldinthePDPcontext.TheSGSNmaysendaCreatePDPContextRequestevenifthePDPcontextisalreadyactive.TheGGSNshallcheckifaPDPcontextalreadyexistsfortheTID.TheexistingparametersinthePDPcontextshallthenbereplacedwiththeparametersintheCreatePDPContextRequestmessage.IfadynamicPDPaddresshasalreadybeenallocatedfortheexistingcontext,thisaddressshouldbeusedandcopiedtotheCreatePDPContextResponsemessage.IftheGGSNusestheMNRGflagandtheflagisset,theGGSNshouldtreattheCreatePDPContextRequestasaNoteMSPresentRequestandclear
...