In the ATPM, the trigger to start accounting for interesting traffic is configured using the accounting trigger interesting-traffic command. Accounting Start is triggered on arrival of interesting traffic, or change in airlink parameters conveyed through active-start airlink record. If an active-start record was included in the initial connection setup, Accounting Start is not triggered. But if the active-start comes separately and is the first one for the session, it is treated as airlink change and an Accounting Start is sent.
Optionally, timeout can be triggered when there is no data traffic for the interim accounting timeout interval using the accounting trigger inactivity-timeout stop command. On timeout, the accounting session is terminated and an Accounting Stop message is sent. A new accounting session is created if interesting traffic resumes.
name must be the name of a class map, and must be a string of 1 through 15 characters in length.
volume is the value in bytes, and must be an integer from 1 through 4294967295.
bytes must be an integer from 0 through 4294967295.
Important: It is recommended that this parameter be configured to at least the greater of the following two values: 1) 3 times greater than packet MTU for the subscriber connection, OR 2) 3 seconds worth of token accumulation within the “bucket” for the configured peak-data-rate.
bps must be an integer from 0 through 4294967295).
lower-ip-precedence: Transmit the packet after lowering the ip-precedence
bps must be an integer from 0 through 4294967295.
lower-ip-precedence: Transmit the packet after lowering the IP precedence
any allows any profile identifier matching with in this policy map.
id profile_id allows specific profile identifier matching with in this policy map.
profile_id must be either a value in hexidecimal format from 0x0 to 0xFFFF or an integer from 0 to 65535.
range low_value to high_value: identifies a range in which a profile identifier must fall within to be considered a match.
low_value and
high_value must be either a value in hexidecimal format from 0x0 to 0xFFFF or an integer from 0 to 65535.
any allows any flow identifier matching with in this policy map.
id flow_id allows specific flow identifier matching with in this policy map.
flow_id must be either a value in hexidecimal format from 0x0 to 0xFFFF or an integer from 0 to 65535.
range low_value to high_value: identifies a range in which a flow identifier must fall within to be considered a match.
low_value and
high_value must be either a value in hexidecimal format from 0x0 to 0xFFFF or an integer from 0 to 65535.
any: Allows any ASN Service Profile Identifier matching within this policy map.
id service_id: Allows specific Service Profile matching to a specified identifier.
service_id must be an integer from 1 to 65535 and must match a service ID that was configured in the Subscriber Configuration Mode.
any: Allows any ASN Packet Data Flow Identifier matching within this policy map.
id pdf_id: Allows specific Packet Data Flow matching to a specified identifier.
pdf_id must be an integer from 1 to 255 and must match a PDF ID that was configured in the Subscriber Configuration Mode.