Traffic Restriction

When Traffic Restriction Applies

Traffic restriction comes into effect when:

• The customer has no account balance (no credit)
• There is no available quota from any bundle (all data has been used)

Under normal conditions:

• The system attempts to fall back to the tariff for charging
• If there is no balance, a reservation failure event occurs (indicating no funds are available)
• This would typically result in no data session being allowed

What Traffic Restriction Does

When a traffic restriction policy is applied:

• A data session is still allowed, even if the user has:

  • No balance
  • No remaining bundle data

• Instead of blocking access completely:

  • Traffic is restricted to specific destinations only
  • All other traffic is blocked

For example, users may be granted access to specific whitelisted IP addresses. When configured correctly, this can support scenarios such as allowing customers to top up their balance while roaming abroad, without the need to locate and connect to a Wi‑Fi network.

How It Works (Technical Flow)

Without Traffic Restriction

1. A Create Session Request is received
2. The system checks for:
   • Available balance, or
   • Available bundle quota
3. If neither is available:
   • A reservation failure is returned
   • The data session is rejected

With Traffic Restriction Enabled

1. A Create Session Request is received
2. Even if there is:
   • No balance
   • No bundle quota
3. The system:
   • Allows the data session
   • Applies the traffic restriction policy
4. The user can only access whitelisted destinations
   • All other traffic is blocked

Configuration Steps

To enable traffic restriction, the following must be configured:

1. Create a Traffic Restriction Policy
   • Define the allowed destinations (e.g., IPs, domains)
2. Apply the Policy to a Tariff
   • Assign it as the “balance depleted traffic policy”
3. Assign the Tariff to a Customer
   • Ensure the customer is using the tariff with the policy applied

Key Point

Traffic restriction ensures that:

• Users without balance or data are not fully cut off
• They can still access essential services (like top-up)
• All other internet access remains blocked

Example