The real-land network WiFi Authentication & Billing cannot be used solely for certification. Because the population online is not one type of person. Staff members are one category, visitors are one group, students are one group, and temporary construction and outsourcing are another. In different groups, certification methods and management logic naturally differ. Employees are better suited to account codes, work numbers, business microtrusts, nails, AD domain certifications, with emphasis on long-term stability and less volatility; visitors are more suitable for text message authentication, microcredit certification, temporary visitor documentation, and stress rapid release and control of privileges; Students and tenants are frequently bound to school numbers, room numbers, cell numbers and document information.
And that's why the Web WiFi Natshell system looks like“One page”In the case of a school dormitory, students may log in with a school number or cell phone number, and teachers and visitors cannot follow exactly the same process. Hotels and apartments, where guests may be house numbers plus cell numbers, number numbers plus identification cards, are still internal accounts.
The authentication method is only the first step, and it's really easier to ask how much money you charge. Many clients ask about WiFi Authentication & Billing, but they just ask if they can charge a monthly fee or not. It's just the outermost level.“Is there a charge pattern?”The billing rules are not detailed, but rather a combination of fees. For example, the daily fee is either for natural days or 24 hours; the monthly charge is allowed for early renewals; when short-time packages expire, they are either directly off the net or pre-played; and an account number allows several devices to access the Internet, which can be linked to the package scale. These are part of the fee rule, one less considered, and later may become a point of complaint.
The WiFi Authentication & Billing system usually supports several types of fee-based models. The first category is a charge-in-time, suitable for temporary Internet access, short-term activities, training sites, and temporary guest-in-house scenarios. The second category is a daily fee-based, condo-friendly apartment, hotel management, short-lease property, short-term accommodation. The third category is a monthly, quarterly, school-year fee that is suitable for the dormitories network, long-term rental networks, campus-based accommodation networks, and wireless campus networks. A more mature system, often not only supports one but several forms of fee collection coexist and can be differentiated according to different SSIDs, population groups and regions.
This is where the problem lies. Many projects do not begin with a clear idea of certification and fee collection, but simply make an authentication entrance and then impose a charge on it. In this case, it seems as if the pre-payment period was a little bit more difficult to handle. Because fees are not isolated in themselves, they must be tied to identity management, terminal control, access strategies.
There is also a problem that is particularly common on the ground, namely terminal management. Many clients ask whether an account can be used online for several devices at once. This question is both certified and charged. Because the number of terminals is not just shared, it can be directly part of the package. For example, one basic set of equipment, two standard set of equipment, three advanced suites of equipment, so that the fee rules and regulations are combined.
And then down, the value of the Web WiFi Authentication & Billing system is that it allows users to feel well. The most fear for users is not that they charge fees, but that the rules are not transparent. It does not know when the meal packages will expire; it does not know when the payment will be due; it does not coincide with the backstage status; it has been certified and the equipment cannot be connected; it is replaced by a mobile phone, but it is stuck as a new terminal. These problems look like minor malfunctions, often because authentication and fee logic are not worked out. Real mature systems should let users know what they're doing with the authentication, what packages they buy, how to allow a few devices to access the Internet, when they expire, how to renew fees and how to handle terminal switching. Only if these links go smoothly will there be fewer complaints later on.
From the management perspective, back-office operations are also important. The system is not just for users; it has to be managed by managers. For example, which accounts are falling due, which account numbers are overdue, which user terminals are overbound, which customers have high rates of renewal and which authentication methods are most used, should be able to see quickly behind the backstage. Otherwise, systems are so much surface function that they actually operate with manual double check and process them.
In the end, the question of which authentication and fee-backing methods are supported by the Web Wi NATSHEL_AUTH_BILLING system cannot be viewed solely on a functional sheet. The account password, text message certification, micromail authentication, visitor accreditation, business microcredit certification, billing on time, daily fees, monthly charges, terminal limits, can be written on the promotional page. What really looks at these authentication and charging methods is whether they can be combined with a flexible set of scenarios, running together with terminals, online status, log retention, backstage operation if only.“Looks like everything's in support.”But when actually landing is all isolated, the more chaotic it becomes, the more inevitable. The real mature network WiFi Authentication & Billing should be a complete field management tool, not half-drawn together with authentication and fees.