To really understand how the billing system collects money, one has to see what happens once when WebPortal accesss. Users go to WiFi and then go out through a redirection, local certification, under-addressing, dialling, several steps in NAT, with each step tied to the billing and strategy.
WiFi web billing systemWhat happened to a WebPortal access?
Standard links are: users have wireless or cable access to the inner network, reoriented to a single authentication Portal Portal and enter account password submission. Authentication devices are authenticated locally, user identification and tied operator types are verified, and corresponding address pools are sent down. Next, NATSHEL_AUTH_BILLING platform starts PPOE proxy dialling by addressing pool to select the corresponding operator line, so that one-to-one NAT is successfully established and the user is actually online. Any step is broken and the user is stuck on the login page or wrongly.
Each step is marked: local authentication records, address pool records, PPOE session records exports, and NAT records internal and external web mapping. The billing system calculates "time" traffic, which is not empty at all points in the chain. The drain follows this chain, and quickly locates it as being untriggered, uncertified or unredial.
WiFi web billing systemWhat's the local certification and address pool doing?
Local certification is the first step: it determines whether "this account is valid and bound to which operator". The address pool that follows determines which operator line the traffic behind this terminal will follow. For example, students tie telecommunications, send out their telecommunication addresses and use telephonic dials; tie them up and go through connections. The address pool is a bridge between billing and export strategies.
So local certification is not just about "let go" but also about "how to count and which way to go." That's why the account numbers and operator types, MAC, NAS, VLAN are tied up at opening accounts, and cannot wait for the net to be refilled. The chain is right once in the open, and the whole chain follows it, otherwise every time you get out of the network can be miscounted or blocked by a missing link.
WiFi web billing systemIs the school self-built and dialled a chain?
The school self-built and PPPoE is assigned the same WebPortal chain, which is different from the one in export. School self-built schools are completely autonomous, fee-paying strategies are freely aligned, and a cascading system can be used to provide uniform identification and flat fees with a campus calibration, with students being certified by Portal, 802.1X, PPOE, IpoE.
Both models share the same accounts, packages, strategic engines at the expense of the billing, but they are different from export implementation. Understanding this, a campus or park programme can be used to re-apply the same billing configurations, with only differences between the dialling gateway and the address pool. The WiFi network billing system is really valuable, so that each access chain and the billing book is closely aligned and made clear.
WiFi web billing systemRedirection without triggering which floor to start.
The most commonly reported malfunction in the WebPortal chain is "no page, no page." The barrier looks at the orientation layer first: the first HTTP request after the terminal has been connected to WiFi was stopped by authentication equipment for 302, either the authentication device and AP were not connected or Portal services were left unconnected; the page could not be opened but it was Portal server or template load problem; it was only local certification and billing that enabled the page to be played but failed.
The other is "better accounting": users leave the network but have no time flow, or are recorded in another household, mostly with a faulty address pool, miscalculation of account numbers, or a misdirection of NAT maps. Such problems avoid half the problem by matching the binding and address pool during opening accounts. Understanding the whole WebPortal chain, decomposition and programming is exactly the same thing: righting the chain and allowing each jump to be traceable and cost-effective.
WiFi web billing systemI'm not gonna be able to tell you until we get the access chain into the plan.
The first thing about campus or park programmes is to draw the webPortal access chain: redirection, local certification, address pool, dialling, and every NAT jump mark. It's a chain that allows clients to match their understanding and implement them, and later discharges are tracked, so that they don't talk.
Each jump of the chain corresponds to a configuration: local certified counter and operator tied, address pool corresponding to export lines, NAT matching sessions retroactively. The opening phase sets these together once, and the whole chain follows. Many miscalculations, page popping, roots are all part of the chain with undefined, undetermined configurations, rather than lack of system capacity.
So, evaluating a WiFi network billing system, not only "can we verify it, can charge it," but also "no traceable and uncostable jumps in the access chain." The value of NatShell is being matched with the billing book, so that each time you get online, you can both get out and account for it.
WiFi web billing systemThe access chain is to be visualized.
The WebPortal access chain is painted in the program and has to be seen as a visual drain: each jump is of a state, time-consuming, successful or not, with no redirection trigger, no authentication, no replacement. The operator ' s dyke is turned from log to panel, much faster, and less miscalculation is passed to the system. Visualization is a long-term good guarantee for this chain.
Visualization also requires a visualization: one user cannot access the net to see what jump and hit strategy he has. This way, both the carrier and the customer service, can be positioned in seconds when users complain without having to move. By making the access chain observable and drillingable, WiFi network billing system is upgraded from "calculation" to "good luck", which is the end line of the programme's delivery.