BOD Service Activation and Deactivation

BOD service activation can be implemented using the RADIUS or Diameter protocol. The RADIUS protocol supports dynamic activation only. That is, COA packets carrying the RADIUS attribute HW-Policy-Name(26-95) are sent upon user access. The packet content is the BOD service policy template name, and the accounting mode is RADIUS accounting. The Diameter protocol supports the sending of CCR-I packets upon user access to activate services or the sending of RAR packets after user access to dynamically activate services.

Format of the HW-Policy-Name (26-95) attribute: <service-name>.

BOD service deactivation involves the following scenarios:

• Service deactivation when a user goes offline: All BOD services of the user are automatically stopped when a user goes offline.
• Dynamic service deactivation: When a user is online:
  • The RADIUS server uses a DM message to delete the BOD service policy.
  • The Diameter server uses an RAR message to delete the BOD service policy.
• Service deactivation after quota exhaustion: After the service duration or traffic volume quota is exhausted, the service can be configured to go offline.

The process for the RADIUS server to use a DM message to delete a BOD service policy is as follows:

1. The RADIUS server sends a BOD service policy deletion message to the BRAS.
2. The BRAS sends the RADIUS server a response message indicating that the BOD service policy is deleted.
3. The BRAS sends an accounting stop request to the RADIUS server.
4. The RADIUS server sends an accounting stop response to the BRAS.

The process for the Diameter server to use an RAR message to delete a BOD service policy is as follows:

1. The Diameter server sends an RAR message to the BRAS to delete a BOD service policy.
2. The BRAS sends the Diameter server a response message indicating that the BOD service policy is deleted.