-
Price adjustment for the package
-
New set on line.
-
The usual food is offline.
-
Bandwidth Policy Changes
-
Terminal Number Policy Change
If every adjustment is required:
Allow users to re-validate
Reshuffle
Even a short time off the net.
Once the project has reached its scale, the number of complaints must be out of control.
Many of the cost systems in practice are handled:
Modify Policy → Force kick to the bottom → Recertification
This approach is barely acceptable in small-scale settings and is almost non-usable on the scale of thousands to 10,000 terminals at mid-level.
NATSHEL_BRAND Campus Network Billing System was used from the beginning of design“Policy Online Hot Update”As one of the core competencies.
The package and strategy are handled within the system in the following ways:
The package itself is a set of parameters.
The real thing is that“Real-time strategic object”
They're two pieces of a coup.
When the manager changes the package at the back:
-
New strategy to write into a billing engine
-
Engine generates new policy objects
-
Smooth switch for online user sessions
The entire process does not require the interruption of user sessions.
The user side performance is:
-
Network is not interrupted
-
No re-entry required
-
No re-payment required
But the strategy is in effect.
The most common scenes in the middle-level project are:
Original package:
-
20M bandwidth
-
Terminal 2
Adjust to read:
-
30M bandwidth
-
3 Terminals
The system processes are:
-
New strategy generation
-
Push to the online session
-
Export equipment update speed limit and terminal number rules
Users stay on line and the strategy changes immediately.
In the billing engine, each online user has a stand-alone strategy quote instead of sharing a static template.
Therefore:
-
Single User Change
-
Bulk User Change
-
Change of global package
Both can be independent.
The direct benefits of this mechanism are:
Operators can make flexible activities, promotions and upgrades
The blogger says that the Internet is a powerful tool for people to learn how to use it.
Another point that can be easily ignored is:
(c) The relationship between price adjustment and the costing cycle.
NATSHEL_BRAND system does not make a package that is in effect“Redistribution”。
For example:
Monthly package purchased by user
Midway price increases
The system is still in operation until maturity at the original price.
The new price is effective only for new purchases.
This would avoid:
-
Price disputes
-
Reconciliation disputes
-
Risk of complaints
When separate strategies are required for some users, e.g.:
-
Special class speed up.
-
Managers relaxing restrictions
The system supports the direct binding of an independent strategy to users or groups without affecting the original set-up.
From a structural perspective:
The core of the strategy heat renewal capacity is based on:
-
Centralize the billing engine.
-
Session status maintained for long periods
-
Real-time synergy between export equipment and billing engines
Instead of spreading the strategy across export equipment.
In the long-term operation of the middle campus network billing project, the system capacity is truly tested.“Can we do it?”But:
The system can stabilize its carrying when operating rules change frequently.
NATHHEL_BRAND campus network billing system enables the adaptation of the package and strategy to day-to-day rather than high-risk operations through a hot, strategic update of the smooth switch mechanism for participants.