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

    exclude (Trigger Profiles)

    Syntax

    exclude {ms-timezone-change;plmn-change;qos-change;rat-change;sgsn-sgw-change;user-location-change;}

    Hierarchy Level

    [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-name offline]

    Release Information

    Statement introduced in Junos OS Mobility Release 11.2W.

    Description

    Certain signal message updates to the packet data protocol (PDP) context or bearer trigger charging updates. However, using the statements in this hierarchy, you can choose not to record these updates in the CDR.

    For example, a quality of service (QoS) change results in a container being added to the CDR. However, the container does not get added if you configure to ignore this change, using the following command:
    set unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-name exclude qos-change

    You may have configured certain IEs to be excluded from the CDR using the statements under the cdr-profiles > exclude-ie-options hierarchy. Irrespective of this configuration, some of the IEs get added to the CDR, if the corresponding triggering event is not disabled. The following table lists the triggers and the corresponding IEs.

    Table 1: Triggers and corresponding IEs

    Trigger

    IE

    ms-timezone-change

    MS time zone

    plmn-change

    Serving node PLMN identifier

    rat-change

    RAT type

    user-location-change

    User location information

    Options

    • ms-timezone-change—Usually, an MS time zone change results in the CDR getting updated with the charging information and the CDR getting closed. However, by configuring this statement, you can exclude charging data updates to the CDR when there is a change in the mobile station (MS) time zone.
    • plmn-change—Usually, a public land mobile network (PLMN) change results in the CDR getting updated with the charging information and the CDR getting closed. However, by configuring this statement, you can exclude charging data updates to the CDR when there is a PLMN change.
    • qos-change—Usually, a container gets added to the CDR when there is a QoS change. However, by configuring this statement, you can exclude charging data updates to the CDR when there is a QoS change.
    • rat-change—Usually, a RAT change results in the CDR getting updated with the charging information and the CDR getting closed. However, by configuring this statement, you can exclude charging data updates to the CDR when there is a RAT change.
    • sgsn-sgw-change—Usually, when the SGSN or SGW changes reaches the maximum configuration limit (determined by the value set for the sgsn-sgw-change-limit parameter), the CDR gets updated and closed. However, by configuring this statement, you can exclude charging data updates to the CDR when this limit is reached.
    • user-location-change—Usually, a change in the user location information (such as ECGI, TAI, RAI, SAI, LAI, or CGI) results in the open containers getting closed and added to the CDR. However, by configuring this statement, you can exclude charging data updates to the CDR when there is a change in user location.

    Required Privilege Level

    interface—To view this statement in the configuration.

    interface-control—To add this statement to the configuration.

    Published: 2011-11-16