Оглавление |
---|
Description
Problem: a client should be provided with an opportunity to use a service for 2 hours on weekdays and download 1 Gb of traffic within the allotted time. Access should be denied when time or traffic quota is exceeded. Block should be cancelled at 7:00 (a client's timezone), a client is in Yekaterinburg. When access is blocked, https://eltex-co.com should be available. Other HTTP/HTTPS requests should be redirected to "Access denied" page.
To solve the problem, PCRF scenarios should be used. A scenario is a sequence of services. Services used in a scenario should be finite and have a condition for transition to next step.
A condition may be:
...
Информация |
---|
Software version: SoftWLC 1.13 |
Creating URL lists
To solve the problem, two lists should be created: welcome and white_list. Welcome list is used during client re-authorisation and created when the initial SoftWLC setting is done to work with BRAS.
Select PCRF settings → URL lists tab in the Admin Panel.
Creating a welcome list
The list should contain the address of the portal
Без форматирования |
---|
http://10.10.5.50:9000/eltex_portal/ |
Creating white_list
The list should contain the address of the resource that will be available when access is blocked. For convenience, enter the address as a regular expression
Без форматирования |
---|
^(https|http):\/\/eltex-co\.com\/ |
Creating services
Select Services and tariffs → PCRF services in the Admin Panel
Creating limit2h1Gb service
The service will be the 0th step of our scenario. Set Time's quota and Traffic's quota in accordance with the problem statement
...
- Time's quota — 2 hours according to the problem statement;
- Traffic's class — 1 Gb according to the problem statement;
- Account interim interval — 300 seconds;
- Priority — 10, services with a lower number are processed first;
- Default action — permit.
Creating the blocking service
The service will be the first step of our scenario. The service will block Internet access, all HTTP/HTTPS requests will be redirected to "Access denied" page, https://eltex-co.com/ will be accessible via HTTP/HTTPS.
...
Предупреждение |
---|
Block reset takes into account a client's timezone that should be defined in EMS service domain settings. If a timezone is not defined in a client's domain, a bottom-up tree search will be conducted. If a timezone is not found in parent domains, block reset will take UTC ± 0:00. Timezone is set in EMS domain settings |
Creating a PCRF scenario
Select Services and tariffs → PCRF scenarios tab in the Admin Panel.
Creating a limit scenario
Add the created services to the scenario, the services will be displayed from the top down
At the zeroth step, a client gets the service with quota (limit2h1Gb). When quota is exceeded, the first step with the blocking service will be available. The service will be operating until the reset. After the reset, a client moves to the second step and switches back to the zeroth one.
Creating a tariff
Select Services and tariffs → Tariffs tab in the Admin Panel, change the filter to PCRF/BRAS
Creating a limitTP tariff
Add a new tariff and select a previously created limit scenario
...
Информация |
---|
When a tariff is created, it should be assigned to a client's portal. For L2, a portal is selected in PCRF settings → L2 subnets tab of the Admin Panel. For L3, a portal is selected in EMS (SSID Manager). |
CheckCronBrasVerticle update interval
CheckCronBrasVerticle update interval is set in bras.cron.update.interval block of PCRF configuration
...
Блок кода | ||
---|---|---|
| ||
"bras.cron.update.interval": { "interval" : 1800, "unit": "Seconds" }, |
How it works
A client passes the registration and gets a configured scenario. To see which step a client is at and which services does he have, Mongo can be used:
...
When a client returns, updated services consistent with the problem stated will be available for him.
Constraints
If there are two or more services with quota within a scenario, and a client has not reached the blocking service, he will remain at the current service with quota, i.e. he will not be switched to the zeroth step. Once a client is reconnected, a service will not be fully provided, as the work will start from the mid-way point.