Skip to content

TS 29.274 — Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3⚓︎

Release: Rel 15 · Version assessed: 15.3.0 · Network: 4G · Applies to: MME, SGW, PGW · Interfaces: S11, S5/S8

Mandatory items: 155, of which 155 supported. A further 190 clauses of the specification carry no conformance requirement and are not listed.

Mandatory items⚓︎

Ref. Item Status Support Remarks
4.0 General Mandatory Supported MBMS is not supported.
4.1 GTP Tunnel Mandatory Supported
4.2 Protocol stack Mandatory Supported
4.2.0 General Mandatory Supported
4.2.1 UDP header and port numbers Mandatory Supported
4.2.1.0 General Mandatory Supported
4.2.1.1 Initial Messages Mandatory Supported
4.2.1.2 Triggered Messages Mandatory Supported
4.2.2 IP header and IP addresses Mandatory Supported
4.2.2.1 Initial Messages Mandatory Supported
4.2.2.2 Triggered Messages Mandatory Supported
4.2.2.3 Piggybacked Messages Mandatory Supported
4.2.5 Messages with GTPv2 defined replies: Classification of Initial and Triggered Messages Mandatory Supported
4.3 Transmission Order and Bit Definitions Mandatory Supported
5.0 GTP Header for Control Plane Mandatory Supported
5.1 General format Mandatory Supported
5.3 GTP-C header for Echo and Version Not Supported Indication messages Mandatory Supported
5.4 EPC specific GTP-C header Mandatory Supported
5.5 Usage of the GTPv2-C Header Mandatory Supported
5.5.1 General Mandatory Supported
5.5.2 Conditions for sending TEID=0 in GTPv2-C header Mandatory Supported
5.6 Format of the GTPv2-C Message Mandatory Supported
6.0 GTP-C Message Types and Message Formats Mandatory Supported
6.0 General Mandatory Supported
6.1 Message Format and Type values Mandatory Supported Details of list of messages supported is mentioned later.
6.1.0 Message Type Mandatory Supported
6.1.2 Grouped Information Elements Mandatory Supported
6.1.3 Information Element instance Mandatory Supported
7.1.0 General Mandatory Supported
7.1.1 Echo Request Mandatory Supported
7.1.2 Echo Response Mandatory Supported
7.1.3 Version Not Supported Indication Mandatory Supported
7.2 Tunnel Management Messages Mandatory Supported
7.2.0 General Mandatory Supported
7.2.1 Create Session Request Mandatory Supported
7.2.2 Create Session Response Mandatory Supported
7.2.3 Create Bearer Request Mandatory Supported
7.2.4 Create Bearer Response Mandatory Supported
7.2.5 Bearer Resource Command Mandatory Supported
7.2.6 Bearer Resource Failure Indication Mandatory Supported
7.2.7 Modify Bearer Request Mandatory Supported
7.2.8 Modify Bearer Response Mandatory Supported
7.2.9 Delete Session Request and Delete Bearer Request Mandatory Supported
7.2.9.1 Delete Session Request Mandatory Supported
7.2.9.2 Delete Bearer Request Mandatory Supported
7.2.10 Delete Session Response and Delete Bearer Response Mandatory Supported
7.2.10.1 Delete Session Response Mandatory Supported
7.2.10.2 Delete Bearer Response Mandatory Supported
7.2.11 Downlink Data Notification messages Mandatory Supported
7.2.11.1 Downlink Data Notification Mandatory Supported
7.2.11.2 Downlink Data Notification Acknowledge Mandatory Supported
7.2.11.3 Downlink Data Notification Failure Indication Mandatory Supported
7.2.12 Delete Indirect Data Forwarding Tunnel Request Mandatory Supported
7.2.13 Delete Indirect Data Forwarding Tunnel Response Mandatory Supported
7.2.14 Modify Bearer Command and Failure Indication Mandatory Supported
7.2.14.1 Modify Bearer Command Mandatory Supported
7.2.14.2 Modify Bearer Failure Indication Mandatory Supported
7.2.15 Update Bearer Request Mandatory Supported
7.2.16 Update Bearer Response Mandatory Supported
7.2.17 Delete Bearer Command and Failure Indication Mandatory Supported
7.2.17.1 Delete Bearer Command Mandatory Supported
7.2.17.2 Delete Bearer Failure Indication Mandatory Supported
7.2.18 Create Indirect Data Forwarding Tunnel Request Mandatory Supported
7.2.19 Create Indirect Data Forwarding Tunnel Response Mandatory Supported
7.2.21 Release Access Bearers Request Mandatory Supported
7.2.22 Release Access Bearers Response Mandatory Supported
7.2.23 Stop Paging Indication Mandatory Supported
7.2.24 Modify Access Bearers Request Mandatory Supported
7.2.25 Modify Access Bearers Response Mandatory Supported
7.3.1 Forward Relocation Request Mandatory Supported SRVCC is not supported
7.3.2 Forward Relocation Response Mandatory Supported
7.3.3 Forward Relocation Complete Notification Mandatory Supported
7.3.4 Forward Relocation Complete Acknowledge Mandatory Supported
7.3.5 Context Request Mandatory Supported
7.3.6 Context Response Mandatory Supported
7.3.7 Context Acknowledge Mandatory Supported
7.3.8 Identification Request Mandatory Supported
7.3.9 Identification Response Mandatory Supported
7.3.10 Forward Access Context Notification Mandatory Supported
7.3.11 Forward Access Context Acknowledge Mandatory Supported
7.6 Reliable Delivery of Signalling Messages Mandatory Supported
7.7 Error Handling Mandatory Supported
7.7.0 Handling Piggybacked Messages Mandatory Supported Receiving piggy backed messages is handled.
7.7.1 Protocol Errors Mandatory Supported
7.7.2 Different GTP Versions Mandatory Supported
7.7.3 GTP Message of Invalid Length Mandatory Supported
7.7.4 Unknown GTP Message Mandatory Supported
7.7.5 Unexpected GTP Message Mandatory Supported
7.7.6 Missing Information Elements Mandatory Supported
7.7.7 Invalid Length Information Element Mandatory Supported
7.7.8 Semantically incorrect Information Element Mandatory Supported
7.7.9 Unknown or unexpected Information Element Mandatory Supported
7.7.10 Repeated Information Elements Mandatory Supported
7.8 Path Failure Mandatory Supported
7.9 Restoration and Recovery Mandatory Supported
7.9.0 General Mandatory Supported
7.9.1 Delete PDN Connection Set Request Mandatory Supported
7.9.2 Delete PDN Connection Set Response Mandatory Supported
7.9.3 Update PDN Connection Set Request Mandatory Supported
7.9.4 Update PDN Connection Set Response Mandatory Supported
7.9.5 PGW Restart Notification Mandatory Supported
7.9.6 PGW Restart Notification Acknowledge Mandatory Supported
7.10 Fallback to GTPv1 mechanism Mandatory Supported
7.12 Trace Management Messages Mandatory Supported
7.12.1 Trace Session Activation Mandatory Supported
7.12.2 Trace Session Deactivation Mandatory Supported
8.1 Information Element Types Mandatory Supported
8.2 Information Element Format; Mandatory Supported
8.2.1 General Mandatory Supported
8.2.2 Handling ASN.1/PER encoded parameters Mandatory Supported
8.3 International Mobile Subscriber Identity (IMSI) Mandatory Supported
8.4 Cause Mandatory Supported
8.5 Recovery (Restart Counter) Mandatory Supported
8.6 Access Point Name (APN) Mandatory Supported
8.7 Aggregate Maximum Bit Rate (AMBR) Mandatory Supported
8.8 EPS Bearer ID (EBI) Mandatory Supported
8.9 IP Address Mandatory Supported
8.10 Mobile Equipment Identity (MEI) Mandatory Supported
8.11 MSISDN Mandatory Supported
8.12 Indication Mandatory Supported
8.13 Protocol Configuration Options (PCO) Mandatory Supported
8.14 PDN Address Allocation (PAA) Mandatory Supported
8.15 Bearer Quality of Service (Bearer QoS) Mandatory Supported
8.16 Flow Quality of Service (Flow QoS) Mandatory Supported
8.17 RAT Type Mandatory Supported
8.18 Serving Network Mandatory Supported
8.19 EPS Bearer Level Traffic Flow Template (Bearer TFT) Mandatory Supported
8.20 Traffic Aggregate Description (TAD) Mandatory Supported
8.21 User Location Information (ULI) Mandatory Supported
8.21.4 TAI field Mandatory Supported
8.21.5 ECGI field Mandatory Supported
8.22 Fully Qualified TEID (F-TEID) Mandatory Supported
8.28 Bearer Context Mandatory Supported
8.30 Charging Characteristics Mandatory Supported
8.31 Trace Information Mandatory Supported
8.34 PDN Type Mandatory Supported
8.35 Procedure Transaction ID (PTI) Mandatory Supported
8.38 MM Context Mandatory Supported
8.39 PDN Connection Mandatory Supported
8.45 Trace Reference Mandatory Supported
8.46 Complete Request Message Mandatory Supported
8.47 GUTI Mandatory Supported
8.48 Fully Qualified Container (F-Container) Mandatory Supported
8.51 Target Identification Mandatory Supported
8.57 APN Restriction Mandatory Supported
8.58 Selection Mode Mandatory Supported
8.62 Fully qualified PDN Connection Set Identifier (FQ-CSID) Mandatory Supported
8.68 Transaction Identifier (TI) Mandatory Supported
8.75 User CSG Information(UCI) Mandatory Supported
8.76 CSG Information Reporting Action Mandatory Supported
8.78 CSG ID Mandatory Supported
8.79 CSG Membership Indication (CMI) Mandatory Supported
8.82 Local Distinguished Name (LDN) Mandatory Supported
8.83 Node Features Mandatory Supported
8.86 Allocation/Retention Priority (ARP) Mandatory Supported

Optional items⚓︎

The specification leaves these 65 items to the implementation; 19 are supported or partially supported. An item marked Not applicable belongs to an area the platform does not provide, named in the Support column. Expand for the full list.

65 optional items
Ref. Item Support Remarks
4.2.1.3 Piggybacked Messages Not supported Receiving piggy backed messages is supported
7.2.26 Remote UE Report Notification Not supported
7.2.27 Remote UE Report Acknowledge Not supported
7.3.14 Change Notification Request Supported
7.3.15 Change Notification Response Supported
7.3.16 Relocation Cancel Request Supported
7.3.17 Relocation Cancel Response Supported
7.3.18 Configuration Transfer Tunnel Not supported
7.3.20 ISR Status Indication Not supported
7.3.21 UE Registration Query Request Not supported
7.3.22 UE Registration Query Response Not supported
7.4 CS Fallback and SRVCC related messages Supported
7.4.1 Suspend Notification Supported
7.4.2 Suspend Acknowledge Supported
7.4.3 Resume Notification Supported
7.4.4 Resume Acknowledge Supported
7.4.5 CS Paging Indication Not supported
7.4.6 Alert MME Notification Not supported
7.4.7 Alert MME Acknowledge Not supported
7.4.8 UE Activity Notification Not supported
7.4.9 UE Activity Acknowledge Not supported
7.9.7 PGW Downlink Triggering Notification Not supported
7.9.8 PGW Downlink Triggering Acknowledge Not supported
7.13 MBMS Messages Not supported
7.13.1 MBMS Session Start Request Not supported
7.13.2 MBMS Session Start Response Not supported
7.13.3 MBMS Session Update Request Not supported
7.13.4 MBMS Session Update Response Not supported
7.13.5 MBMS Session Stop Request Not supported
7.13.6 MBMS Session Stop Response Not supported
8.2.1.A Information Element with an IE Type Extension field Not supported
8.21.1 CGI field Not supported
8.21.2 SAI field Not supported
8.21.3 RAI field Not supported
8.21.6 LAI field Not supported
8.21.7 Macro eNodeB ID field Not supported
8.21.8 Extended Macro eNodeB ID field Not supported
8.24 Global CN-Id Not supported
8.32 Bearer Flags Not supported
8.49 Fully Qualified Cause (F-Cause) Not supported It is transparently passed from eNodeB to target MME, but does not get interpreted at target MME.
8.54 RAB Context Not supported
8.59 Source Identification Not supported
8.61 Change Reporting Action Supported
8.66 Fully Qualified Domain Name (FQDN) Not supported
8.67 Private Extension Not supported
8.87 EPC Timer Not supported
8.88 Signalling Priority Indication Supported
8.130 Counter Not supported
8.131 Mapped UE Usage Type Not supported
8.132 Secondary RAT Usage Data Report Not supported
8.133 UP Function Selection Indication Flags Supported
9.0 Security Not supported
10.0 IP - The Networking Technology used by GTP Not supported
10.1 IP Version Not supported
10.2 IP Fragmentation Not supported
10.3 DSCP Not supported
11.2 Dynamic discovery of supported features Supported
11.2.2 Features supported by direct peer GTP-C entities Supported
12.0 GTP-C load & overload control mechanism Not supported
12.1 General Not supported
Annex B (Informative): Transparent copying of RANAP/S1AP IEs into GTP IEs Supported
B.1 General Supported
B.2 Handover/Relocation related generic transparent Containers over RANAP, S1-AP and GTP Supported
B.3 Other RANAP and S1-AP IEs Supported
Annex C (Normative): MME/S4-SGSN mapping table between S11/S4 and NAS Cause values Supported

Assessed 2026-09-15 against TS 29.274 version 15.3.0.