7.1 Message Formats

29.0603GPPGeneral Packet Radio Service (GPRS)GPRS Tunnelling Protocol (GTP) across the Gn and Gp interfaceRelease 17TS

GTP defines a set of messages between two associated GSNs or an SGSN and an RNC. The messages to be used are defined in the table below. The three columns to the right define which parts (GTP-C, GTP-U or GTP’) that send or receive the specific message type.

Table 1: Messages in GTP

Message Type value (Decimal)

Message

Reference

GTP-C

GTP-U

GTP’

0

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

1

Echo Request

7.2.1

X

X

x

2

Echo Response

7.2.2

X

X

x

3

Version Not Supported

7.2.3

X

x

4

Node Alive Request

3GPP TS 32.295 [33]

X

5

Node Alive Response

3GPP TS 32.295 [33]

X

6

Redirection Request

3GPP TS 32.295 [33]

X

7

Redirection Response

3GPP TS 32.295 [33]

X

8-15

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

16

Create PDP Context Request

7.3.1

X

17

Create PDP Context Response

7.3.2

X

18

Update PDP Context Request

7.3.3

X

19

Update PDP Context Response

7.3.4

X

20

Delete PDP Context Request

7.3.5

X

21

Delete PDP Context Response

7.3.6

X

22

Initiate PDP Context Activation Request

7.3.12

X

23

Initiate PDP Context Activation Response

7.3.13

X

24-25

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

26

Error Indication

3GPP TS 29.281 [41]

X

27

PDU Notification Request

7.3.8

X

28

PDU Notification Response

7.3.9

X

29

PDU Notification Reject Request

7.3.10

X

30

PDU Notification Reject Response

7.3.11

X

31

Supported Extension Headers Notification

7.2.4

X

X

32

Send Routeing Information for GPRS Request

7.4.1

X

33

Send Routeing Information for GPRS Response

7.4.2

X

34

Failure Report Request

7.4.3

X

35

Failure Report Response

7.4.4

X

36

Note MS GPRS Present Request

7.4.5

X

37

Note MS GPRS Present Response

7.4.6

X

38-47

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

48

Identification Request

7.5.1

X

49

Identification Response

7.5.2

X

50

SGSN Context Request

7.5.3

X

51

SGSN Context Response

7.5.4

X

52

SGSN Context Acknowledge

7.5.5

X

53

Forward Relocation Request

7.5.6

X

54

Forward Relocation Response

7.5.7

X

55

Forward Relocation Complete

7.5.8

X

56

Relocation Cancel Request

7.5.9

X

57

Relocation Cancel Response

7.5.10

X

58

Forward SRNS Context

7.5.13

X

59

Forward Relocation Complete Acknowledge

7.5.11

X

60

Forward SRNS Context Acknowledge

7.5.12

X

61

UE Registration Query Request

7.5.15

X

62

UE Registration Query Response

7.5.16

X

63-69

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

70

RAN Information Relay

7.5.14.1

X

71-95

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

96

MBMS Notification Request

7.5A.1.1

X

97

MBMS Notification Response

7.5A.1.2

X

98

MBMS Notification Reject Request

7.5A.1.3

X

99

MBMS Notification Reject Response

7.5A.1.4

X

100

Create MBMS Context Request

7.5A.1.5

X

101

Create MBMS Context Response

7.5A.1.6

X

102

Update MBMS Context Request

7.5A.1.7

X

103

Update MBMS Context Response

7.5A.1.8

X

104

Delete MBMS Context Request

7.5A.1.9

X

105

Delete MBMS Context Response

7.5A.1.10

X

106 – 111

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

112

MBMS Registration Request

7.5A.2.1

X

113

MBMS Registration Response

7.5A.2.2

X

114

MBMS De-Registration Request

7.5A.2.3

X

115

MBMS De-Registration Response

7.5A.2.4

X

116

MBMS Session Start Request

7.5A.2.5

X

117

MBMS Session Start Response

7.5A.2.6

X

118

MBMS Session Stop Request

7.5A.2.7

X

119

MBMS Session Stop Response

7.5A.2.8

X

120

MBMS Session Update Request

7.5A.2.9

X

121

MBMS Session Update Response

7.5A.2.10

X

122-127

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

128

MS Info Change Notification Request

7.5B.1.1

X

129

MS Info Change Notification Response

7.5B.1.2

X

130-239

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

240

Data Record Transfer Request

3GPP TS 32.295 [33]

X

241

Data Record Transfer Response

3GPP TS 32.295 [33]

X

242-252

For future use. Shall not be sent. If received, shall be treated as an Unknown message.

253

Tunnel Status

3GPP TS 29.281 [41]

X

254

End Marker

3GPP TS 29.281 [41]

X

255

G-PDU

3GPP TS 29.281 [41]

X

7.1.1 Presence requirements of Information Elements

There are three different presence requirements (Mandatory, Conditional, or Optional) for an IE within a given GTP-PDU:

– Mandatory means that the IE shall be included by the sending side, and that the receiver diagnoses a "Mandatory IE missing" error when detecting that the IE is not present.

– Conditional means:

– that inclusion of the IE by the sender depends on conditions specified in the relevant protocol specification;

– that the receiver can expect that the IE is present based on its parameter combination in the message and/or on the state of the receiving node.

– Optional means that the IE shall be included as a service option. Therefore, the IE may be included or not in a message.

For error handling, refer to clause 11.