Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Charging Trigger Events

    A trigger profile defines the charging events that cause Charging Data Record (CDR) changes.

    To configure trigger profiles:

    1. Specify the name of the trigger profile that you are configuring for the gateway called MBG1.
      [edit unified-edge gateways ggsn-pgw MBG1 charging]user@host# edit trigger-profiles profile-name
    2. Specify a description for the profile.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name]user@host# set description string
    3. Configure offline charging in the trigger profile.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name]user@host# edit offline
    4. Specify a time limit for closing the container. A value of zero (0) disables this trigger.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name offline]user@host# set time-limit seconds
    5. Specify the bearer information change that does not trigger charging data updates. All of these changes trigger a container or CDR closure by default.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name offline]user@host# set exclude bearer-information-change

      The following table describes the bearer information changes that can be ignored for charging data updates.

      Bearer Information Change

      Description

      ms-timezone-change

      MS time zone

      plmn-change

      Public Land Mobile Network (PLMN)

      qos-change

      Quality of service (QoS)

      rat-change

      Radio Access Technology (RAT)

      sgsn-sgw-change

      SGSN or S-GW limit

      user-location-change

      User location information

      For example:

      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name offline]user@host# set exclude user-location-change
    6. Specify a volume limit trigger for bandwidth, in bytes.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name offline]user@host# set volume-limit value
    7. Specify the direction for the volume limit trigger. If you specify both, the volume limit applies to the combined amount of uplink and downlink traffic.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name offline]user@host# set volume-limit direction (both | uplink)
    8. Specify the maximum number of containers to limit for each CDR.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name offline]user@host# set container-limit value
    9. Specify the number of SGSN or S-GW changes that can occur before the CDR is updated and closed. A value of zero (0) disables this trigger.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name offline]user@host# set sgsn-sgw-change-limit value
    10. Configure the list of times to update CDRs when the tariffs change within a day. These times can be specified in a minimum of 15-minute increments. Specify the tariff time changes in the format hh:mm, where hh is 00 through 23 (00 is midnight) and mm is 00 through 59. The specified time is local time.
      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name]user@host# set tariff-time-list hh:mm

      For example:

      [edit unified-edge gateways ggsn-pgw MBG1 charging trigger-profiles profile-name tariff-time-list]user@host# set tariff-time-list 21:00user@host# set tariff-time-list 07:00

    Published: 2011-11-16