Cisco Cisco Packet Data Gateway (PDG)

Página de 128
  SaMOG Gateway Offline Charging 
Triggers for Generation of Charging Records  ▀   
 
SaMOG Administration Guide, StarOS Release 18  ▄  
 
   
97 
Triggers for Generation of Charging Records 
The following section describes the triggers for the generation of partial and final SaMOG CDRs. 
SaMOG CDRs are updated (not closed) for any of the following conditions: 
 
QoS Change: When a QoS change is detected, the “List of Traffic Data Volumes” is added to the CDR. 
 
Tarrif Time Change: When the tarrif time changes, the “List of Traffic Data Volumes” is added to the CDR.  
 
CDR Closure: The “List of Traffic Data Volumes” is added to the CDR when this event occurs. 
The “List of Traffic Volumes” attribute in the SaMOG CDR consists of a set of containers that are added when specific 
trigger conditions are met. The volume count per IP CAN bearer is also identified and separated for uplink and 
downlink traffic when the trigger condition occurs. 
The SAMOG CDRs are closed as the final record for a subscriber session for the following events: 
 
End of IP-CAN bearer: The CDR is closed when the IP-CAN bearer is deactivated. The trigger condition 
includes:  
 
UE detach 
 
AAA detach 
 
PGW/GGSN detach 
 
any abnormal release 
 
Admin clear 
The following events trigger closure and sending of a partial SaMOG CDR: 
 
Volume Limit: The CDR is partially closed when the configured volume threshold is exceeded. 
 
Time Limit: The CDR is partially closed when the configured interval is reached.  
 
Maximum number of charging condition changes: The CDR is partially closed when the LOTV container 
exceeds its limit.  
 
Management intervention