DAA Service Quota Management

DAA services support a duration quota, a traffic volume quota, or a combination of duration and traffic volume quotas. If both duration and traffic volume quotas are delivered, they take effect together. An action is triggered if either of the quotas is exhausted. When the RADIUS server delivers a new quota, DAA services use the new quota; when the RADIUS server delivers zero quotas, DAA services go offline; when the RADIUS server does not deliver a quota, the BRAS determines whether to log out DAA services based on the configuration. By default, DAA services remain online.

After a user goes online, the RADIUS server uses a CoA message to deliver Huawei No. 95 attribute carrying a DAA service policy name. The standard No. 27 attribute is used to deliver a duration quota, and Huawei No. 15 attribute is used to deliver a traffic volume quota.

After a DAA service goes online successfully, the process for quota exhaustion is as follows:

• A new quota is delivered after quota exhaustion.

  1. When a user's quota is exhausted, the BRAS sends a real-time accounting request to the RADIUS server.
  2. The RADIUS server delivers a new quota to the BRAS, and the user continues to use the new quota.

• Zero quotas are delivered after quota exhaustion.

  1. When a user's quota is exhausted, the BRAS sends a real-time accounting request to the RADIUS server.
  2. The RADIUS server delivers zero quotas to the BRAS.
  3. In uniform accounting mode, when the service goes offline, the BRAS sends an accounting stop request to the RADIUS server. In non-uniform accounting mode, when the user bandwidth parameter is updated to 0, traffic fails to be forwarded.
  4. In uniform accounting mode, the RADIUS server sends an accounting stop response to the BRAS.

• In uniform accounting mode, no quota is delivered after quota exhaustion.

  1. When a user's quota is exhausted, the BRAS sends a real-time accounting request to the RADIUS server.
  2. The RADIUS server does not deliver a quota, and the BRAS determines whether to log out the service based on the configuration. By default, the service remains online.
  3. In uniform accounting mode, if the service is configured to go offline, the BRAS sends an accounting stop request to the RADIUS server. In non-uniform accounting mode, when the user bandwidth parameter is updated to 0 through a configuration, traffic fails to be forwarded.
  4. In uniform accounting mode, the RADIUS server sends an accounting stop response to the BRAS.