If both of these are not possible simultaneously, the network billing software will eventually have one of two outcomes: either a continuous complaint, heavy pressure on the carrier or a serious failure and erosion of project benefits.
That's why many projects appear early on.“It's a charge.”After a while, it's been found that the profits are far below expectations. The problem is not price setting, but web-based billing software.“Contributions paid”and“Unpaid contributions”(c) State separation and control capacity.
It is first necessary to clarify the premise that the so-called lack of perception is not non-certification, but rather pre-certification and internalization.
A mature network billing software does not allow users to enter a password at every connection. The real effective way is to hide the authentication action from the network and session levels. Users only see it.“Can you get it online?”Not“The certification process itself”。
To do so, network billing software usually creates a system of identification for paid users from three dimensions.
First, the account dimensions.
In the network billing software, the account number is not a simple user name and password, but a logical object that binds a suite, length, number of simultaneous distributions, terminal numbers, and area. As long as the account number is still active, the network billing software will be released directly when connection requests enter, rather than triggering the charge page again.
The key to this design is that judgement occurs at the portal of the network, not on the web layer. Whether wireless APs, ACs or wire exchanges, ultimate release decisions are made by a single web-based billing software.
Second, the terminal dimension.
Real mature network billing software must have terminal recognition. The endpoint here, not just IP addresses, is identified by MAC, device fingerprints, session features and so on in multi-dimensional terms.
When a paid account is used within the permitted number of terminals, the network billing software automatically completes the connection to the terminal and then reconnects to the network without having to repeat any information. This is what users feel.“It's like it's connected to the machine.”Source.
When the terminal quantity limits are exceeded, network billing software will switch to a new terminal triggering authentication or charge-back processes. For operators, this is a key tool for controlling costs and preventing extra-account borrowing.
Third, the session dimension.
In the actual network environment, terminals are not always online. Power outages, hibernations, signal switching all lead to interruption of sessions. If every session is re-enacted, so-called unconsciousness cannot be said.
A mature network billing software that allows users who have paid their contributions to do so within reasonable limits through mechanisms such as session maintenance, quick recertification and short-term offline security“It's broken and it's gone.”. Such designs do not affect the logic of charging charges, but significantly reduce the frequency of user operations.
The real challenge after completing the non-emotional knowledge of the users who have paid their contributions is to ensure that those who do not pay are intercepted.
One point that must be emphasized here is that interception by non-contributory users is not simply a page.
If interception occurs only on the web level, users can bypass it in a variety of ways, such as using specific applications, direct IPs, and caches with existing connections.
In actual deployment of network billing software, interceptions by non-contributory users are usually coordinated in several ways.
First, cyber-entry intercepts.
Whether through external Portal of AC or through independent Authentication Gateway, network billing software will judge the status of a full network access before the terminal is given complete access. Unpaid accounts are directly restricted and only fee pages or white list addresses are allowed.
Such interceptions occur at the data forwarding level, rather than at the browser level, and therefore bypassing costs are extremely high.
Second, time node intercepts.
The failure to pay does not necessarily occur for the first time.
A mature network billing software automatically triggers the intercept strategy at these time nodes.“Pin it.”。
Thirdly, the act triggers an interception.
In some projects, the web billing software can also trigger interceptions based on access behaviour. For example, it is only when you first visit an out-of-the-net, generate a very effective flow for the first time, and when you first visit non-white list resources.
A frequently overlooked fact is that unconsciousness and strong interception do not conflict, but rather that the key lies in the difference of target.
Insight is prepared for those who have paid; strong interception is prepared for those who do not.
The network billing software will eventually appear if it does not clearly divide the boundaries between these two categories of users.“You're gonna stop me, you're gonna let me go.”The chaos.
In actual projects, this capacity often depends on a clear division of labour between network billing software and bottom network equipment.“Let it go.”, the harmonization is done by web-based billing software.
NATSHEL_BRAND has long experience in the area of network billing software. Whether it is to match the existing network environment that supports Portal or, in old projects, achieves uniform control through export gateways, it can achieve uninsensitive and non-contributory interception by users who have paid without disrupting existing network structures.
The value of such capabilities for the integrated firm is not reflected in“Function List”Up, and in turn, is reflected in the stability, complaint rates, and real repayments after the project has been online. A truly reliable network billing software often maintains revenue boundaries for project parties where users hardly feel it.