You are on page 1of 34

Gn Interface and GTP

overview V1026
Contents

 Gn Interface
 GTP protocol
 GTP’ protocol

2
Gn/Gp Interface

 Gn/Gp : Between the GSN nodes


 Gn : Between the GSN nodes within the same PLMN
 Gp : Between the GSN nodes in two different PLMNs.
 The two interfaces adopt GTP for communication

3
© ZTE Corporation. All rights reserved
Gn/Gp Interface

SGSN GGSN

GTP-C GTP-C

UDP UDP
Control Plane
IP IP
L2 L2
Gn/Gp L1 L1

GTP-U GTP-U
User
Plane UDP UDP
IP IP
L2 L2
L1 L1
Gn 、 Gp
4
© ZTE Corporation. All rights reserved
Contents

 Gn Interface
 GTP protocol
 GTP’ protocol

5
GTP protocol

 GTP - GPRS Tunneling Protocol


 Function: Encapsulate the network layer packet( IP packet) in order to add
current user information (such as IMSI and TEID etc.) add source GSN IP and
destination GSN IP to tunnel the packet to destination GSN.

6
© ZTE Corporation. All rights reserved
GTP PACKEGE FORMAT

IP UDP GTP Payload (IP or PPP)

Data flows from end mobile OS stack to host/server

Identify the GTP session

Identify the GTP’s well known port

Route between the SGSN and GGSN

7
© ZTE Corporation. All rights reserved
GTP head format

Label Message Length TEID Sequence N-PDN Extension


type number header
8 8 16 32 16

version PT reserved E Flag S Flag PN

Must have part Optional part

Port 2123 for GTP-C


Port 2152 for GTP-U
8
© ZTE Corporation. All rights reserved
GTP protocol

 GTP protocol is made up of :


 Path management
 Tunnel management
 Location management
 Mobility management

9
© ZTE Corporation. All rights reserved
Path management

 Echo Request: find out if the peer GSN or RNC is alive


 Echo Response: a response to a received Echo Request
 Version Not Support: indicates the latest GTP version that the GTP entity on
the identified UDP/IP address can support
 Supported Extension Headers Notification: indicates a list of supported
Extension Headers that the GTP entity on the identified IP address can
support

10
© ZTE Corporation. All rights reserved
Echo Request

 Echo Request
 An Echo Request may be sent on a path to another GSN or RNC to find out if
the peer GSN or RNC is alive (see section Path Failure). Echo Request
messages may be sent for each path in use.
 A path is considered to be in use if at least one PDP context uses the path to
the other GSN. When and how often an Echo Request message may be sent is
implementation specific but an Echo Request shall not be sent more often
than every 60 seconds on each path.

11
© ZTE Corporation. All rights reserved
Echo Response

 Echo Response
 The message shall be sent as a response to a received Echo Request.

12
© ZTE Corporation. All rights reserved
Echo Request / Echo Response

SGSN GGSN

Echo Request

Echo Response

13
© ZTE Corporation. All rights reserved
Version Not Support

 Version Not Support


 This message contains only the GTP header and indicates the latest GTP
version that the GTP entity on the identified UDP/IP address can support.

14
© ZTE Corporation. All rights reserved
Supported Extension Headers Notification

 Supported Extension Headers Notification


 This message indicates a list of supported Extension Headers that the GTP
entity on the identified IP address can support. This message is sent only in
case a GTP entity was required to interpret a mandatory Extension Header but
the GSN or RNC was not yet upgraded to support that extension header. The
GTP endpoint at the GSN or RNC sending this message is marked as not
enabled to support some extension headers (as derived from the supported
extension header list).

15
© ZTE Corporation. All rights reserved
Tunnel management

 Tunnel management
 Create PDP Context Request
 Create PDP Context Response
 Update PDP Context Request
 Update PDP Context Response
 Delete PDP Context Request
 Delete PDP Context Response

16
© ZTE Corporation. All rights reserved
Tunnel management (cont.)

 Tunnel Management
 PDU Notification Request
 PDU Notification Response
 PDU Notification Reject Request
 PDU Notification Reject Response

17
© ZTE Corporation. All rights reserved
Create PDP Context Request /response

SGSN GGSN

Create PDP Context Request


(MSISDN, PDP address, APN, QoS, SGSN
address etc.)

Create PDP Context Response


(reason etc.)

18
© ZTE Corporation. All rights reserved
PDP Update

19
© ZTE Corporation. All rights reserved
PDP Delete

20
© ZTE Corporation. All rights reserved
PDU Notification Request /Response

21
© ZTE Corporation. All rights reserved
PDU Notification Request /Response - MS
Detached

SGSN HLR GGSN

Send Routeing Info for GPRS


(IMSI etc )

Send Routeing Info for GPRS Ack


( reason , IMSI etc)

PDU Notification Request


( PDPaddress)

PDU Notification Response


( reason )

22
© ZTE Corporation. All rights reserved
Location Management

 Location Management
 Send Routing Information for GPRS Request
 Send Routing Information for GPRS Response
 Failure Report Request
 Failure Report Response
 Note MS GPRS Present Request
 Note MS GPRS Present Response

23
© ZTE Corporation. All rights reserved
Send Routing Information for GPRS
Request/Response

24
© ZTE Corporation. All rights reserved
Failure Report Request /Response

25
© ZTE Corporation. All rights reserved
Note MS GPRS Present Request /Response—MS
send attach request

26
© ZTE Corporation. All rights reserved
Mobility Management

 Mobility Management
 Identification Request
 Identification Response
 SGSN Context Request
 SGSN Context Response
 SGSN Context Acknowledge
 Forward Relocation Request
 Forward Relocation Response
 Forward Relocation Complete

27
© ZTE Corporation. All rights reserved
Identification Request /Response

SGSN-B SGSN-A

Identification Request
( RAI , P-TMSI etc )

Identification Response
( reason etc )

28
© ZTE Corporation. All rights reserved
SGSN Context Request /Response/Acknowledge

SGSN-B SGSN-A

SGSN Context Request


( RAI,TLLI etc )

SGSN Context Response


( reason etc )

SGSN Context Acknowledge


( reason etc )

29
© ZTE Corporation. All rights reserved
Contents

 Gn Interface
 GTP protocol
 GTP’ protocol

30
GTP’ protocol

 GTP’ protocol - used between GSN and CG to transfer billing


data
 Path management: Provide two signals to detect if the path between GSN
and CG is available or not; provide a pair of redirection signal to establish
redundant billing channel
 CDR transfer: provide a pair of signal for normal CDR transfer (request and
response).

31
© ZTE Corporation. All rights reserved
Redirection Req/Resp

 When CG notifies GSN to send CDR


to another CG (within the same
GSN CG
PLMN), when CG needs to conduct
software or hardware maintenance Redirection Request
or when CG discovers system error,
Redirection Response
Redirection Command is needed.
 Redirection Request message
carries IE cause code and
suggested CG address

32
© ZTE Corporation. All rights reserved
Data Record Transfer Req/Resp

 When GSN sends CDRs to CG


or supporting repeated CDR GSN CG

prevention mechanism, Data


Data Record Transfer Request
Record Transfer command will
be activated.
Data Record Transfer Response

33
© ZTE Corporation. All rights reserved

You might also like