Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
GTPP Messages ▀
GTPP Interface Administration and Reference, StarOS Release 19 ▄
21
GTPP Messages
This section provides the detailed information on the GTPP message types.
Node Alive Request
The Node Alive Request message may be used to inform that a node in the network has started its service (e.g. after a
service break due to software or hardware maintenance or data service interruption after an error condition). A node
may send a different Node Address than its own in the Information Element, e.g. informing the “next node in the chain”
that the “previous node in the chain” (which is located on the other side of the sender of this message) is now ready for
service.
service break due to software or hardware maintenance or data service interruption after an error condition). A node
may send a different Node Address than its own in the Information Element, e.g. informing the “next node in the chain”
that the “previous node in the chain” (which is located on the other side of the sender of this message) is now ready for
service.
The Node Alive Request message allows a quicker reconnect capability than the Echo Request message based polling
can provide, and its usage will have a reduced load effect on the network, particularly when the number of network
nodes using GTPP is high. It may also be used to inform when a new network node has become available for service. If
the Echo Request message is also used, then the usage of the Node Alive Request message allows the interval of Echo
Requests to be longer, thus reducing network load by reducing number of Echo Requests.
can provide, and its usage will have a reduced load effect on the network, particularly when the number of network
nodes using GTPP is high. It may also be used to inform when a new network node has become available for service. If
the Echo Request message is also used, then the usage of the Node Alive Request message allows the interval of Echo
Requests to be longer, thus reducing network load by reducing number of Echo Requests.
Important:
Node Alive request messages are not supported if the transport layer protocol is TCP.
The Information elements in a Node Alive Request message are shown in the following table:
Table 3. Node Alive Request Message
Information Element
Presence Requirement
Node Address
Mandatory
Alternative Node Address Optional
Private Extension
Optional
The Node Address format is the same as for the Charging Gateway Address format described in TS 29.060.
The format definition for the Node Address information element is the same as the format of the source and destination
address of the IP packet that transports the GTPP messages. The optional Alternative Node Address IE can be used in
the Node Alive Request if the message sender wants to advertise an IP address that is different from the node address
format. This way both the IPv4 and IPv6 node address formats can be supported simultaneously in the messaging,
regardless of whether IPv4 or IPv6 is used in the underlying transport.
address of the IP packet that transports the GTPP messages. The optional Alternative Node Address IE can be used in
the Node Alive Request if the message sender wants to advertise an IP address that is different from the node address
format. This way both the IPv4 and IPv6 node address formats can be supported simultaneously in the messaging,
regardless of whether IPv4 or IPv6 is used in the underlying transport.
The optional Private Extension IE contains vendor- or operator-specific information.
Node Alive Response
The Node Alive Response message, shown in the following table, shall be sent as a response to a received Node Alive
Request.
Request.