BOD Service Accounting

BOD service accounting is classified as individual or non-individual accounting. In individual accounting mode, after a BOD service is generated, accounting stop is triggered; after a BOD service is deleted, accounting start is triggered. The configuration determines whether the BOD service accounting mode is individual accounting. By default, non-individual accounting is used. When a BOD service is generated or deleted, user accounting remains unchanged.

BOD traffic is user traffic. The total traffic volume of a user is stored separately from the total BOD traffic volume of the user. The user traffic volume displayed in AAA entries is the difference between the two traffic volumes. The BOD traffic increment is not counted into the value-added service.

After a BOD service is installed, service entries store the total user traffic volume on the AAA server during BOD service installation. When the BOD service exists and its traffic volume needs to be obtained, the system obtains the total current traffic volume from the AAA server. The current BOD traffic volume can be obtained by subtracting the initial traffic volume during BOD service installation from the total current traffic volume.

BOD services support RADIUS accounting and non-accounting. RADIUS accounting is classified into the following types:

• Accounting start: After a service is activated and a forwarding channel is established, accounting start is immediately triggered for the service.
• Accounting stop: After a service is deactivated and a forwarding channel is deleted, accounting stop is immediately triggered for the service.
• Real-time accounting: To ensure the timeliness and accuracy of user service accounting, the BRAS can send service accounting packets to the AAA server in real-time.