Cisco Cisco Packet Data Interworking Function (PDIF)
GTPP Accounting Overview
GTPP Interface Overview ▀
GTPP Interface Administration and Reference, StarOS Release 18 ▄
15
The GTPP charging support is currently available for the following core multimedia gateway products:
Evolved Packet Data Gateway (ePDG)
Gateway GPRS Support Node (GGSN)
IP Services Gateway (IPSG)
Packet Data Gateway/Tunnel Termination Gateway (PDG/TTG)
Packet Data Network (PDN) Gateway (P-GW)
Serving Gateway (S-GW)
Serving GPRS Support Node (SGSN)
S2a Mobility Over GTP (SaMOG) Gateway
CDR Transport by GTPP
GTPP has been designed to deliver the CDR(s) from the CDF to the CGF(s). This protocol is required if the CGF
resides outside the CDFs. It utilizes some aspects of GTPP, which is used for packet data tunneling in the backbone
network.
resides outside the CDFs. It utilizes some aspects of GTPP, which is used for packet data tunneling in the backbone
network.
GTPP operates on the Ga interface and does not imply the use of any specific backbone network.
GTPP performs the following functions:
CDR transfer between the CDF and the CGF
Redirection of CDRs to another CGF
Advertise to peers about its CDR transfer capability (for example, after a period of service downtime)
Prevents duplicate CDRs that might arise during redundancy operations. If so configured, the CDR duplication
prevention function may also be carried out by marking potentially duplicated CDR packets, and, delegating
the final duplicate deletion task to a CGF or the Billing Domain (instead of handling the possible duplicates
solely by GTPP messaging).
the final duplicate deletion task to a CGF or the Billing Domain (instead of handling the possible duplicates
solely by GTPP messaging).
CDR Push Functionality
This feature facilitates sending of local CDR (G-CDR, eGCDR, PGW/SGW CDR, or any other GTPP CDR) files to a
remote host using the CLI command
remote host using the CLI command
gtpp storage-server local file push
in context configuration mode or
GTPP group configuration mode.
When the push is enabled in a GTPP group then the AAA proxy registers with the HD controller for the push. If the
registration is successful then the controller periodically (~1 min) checks to see if any of the registered clients have files,
in the CDR_DIR (/records/cdr/<gtpp-group>-<vpnid>/*), to be pushed to the configured remote host URLs. If yes, it
will start the PUSH process for that particular client. After pushing all the files of this client, the requests for the next
client will be serviced in sequence.
registration is successful then the controller periodically (~1 min) checks to see if any of the registered clients have files,
in the CDR_DIR (/records/cdr/<gtpp-group>-<vpnid>/*), to be pushed to the configured remote host URLs. If yes, it
will start the PUSH process for that particular client. After pushing all the files of this client, the requests for the next
client will be serviced in sequence.
If the registration fails, the client will re-attempt to register indefinitely in intervals unless the configuration is removed.
Upon each failure an error log will be printed.
Upon each failure an error log will be printed.
Important:
The push framework does not support FTP or TFTP for pushing CDR files but it supports only
SFTP.