The campus WiFi Authentication & Billing system is on the line, with a wrong billing model and a whole lot of trouble behind it. Some park maps are all wrapped up for months, and as a result short-term visitors feel expensive, long-term residents feel comfortable but not in the operator’s income; others use flow-based charges, users check traffic daily, and complaints continue to be heard. The billing mode is not just one, but rather a custom configuration based on the use of different user groups in the park so that each class can feel reasonable and operators can earn money.
Monthly: stabilize revenue to prevent sharing
The monthly package is the most common model for a park, with users paying one month at a time and running for an unlimited period of time. Users who work or reside in a park on a permanent basis, such as company employees, residents of campus accommodation, are suitable. The advantage of the month is that they have stable income, no need to worry about traffic, and simple operations. But the biggest problem is account sharing, where one person has a monthly account, which is used by all office staff to access the Internet, and operators receive a single fee for 10 people. The MAC was also to be tied in conjunction with the first authentication of the monthly account number and the other equipment was denied certification using this account number.
Days: preference for short-term visitors
The daily billing fee is paid on a daily basis, and the user buys one day’s service for short-term visitors to the campus, participants in meetings, temporary construction workers. The price is more expensive than the monthly package because of the higher cost of services provided by short-term users (account opening, NATHELL_LOG_AUDIT, equipment access is subject to resource). The package account must have a clear expiry time, automatic shutdown due to maturity, and no manual intervention is required. The day-span bill is also to be matched with visitor accreditation, and visitors register by text messages and jump directly to the contribution page, and the package is to be opened as soon as payment is made.
Hourly fee: temporary use of the Internet
The technical difficulty of time-based fees is to calculate them accurately, when the user stops counting after disconnecting them, and whether they continue to accumulate or recalculate. V7 supports long-time billing, which is done online for hours or hours through Radius ' real-time reporting. Minimum consumption, such as a minimum of one hour, would also be required to avoid the increased complexity of the system owing to 10 minutes for users and 10 minutes for fees.
Flow-by-flow: fair patterns for large-volume users
The flow-based charge is based on the up-to-down traffic charges actually used by users, and is fair to small-flow users. It is higher for large-flow users (often watching videos, downloading large files). The technology requirement for traffic-by-flow counts is highest, requires accurate traffic statistics, cannot be missed or counted. The V7 system, in conjunction with NE-80 current-control gateways, can achieve precision traffic recognition, support more than 3600 application identifications, distinguishing between user page views and video downloads, and even application-specific fees. The excess traffic alert is also set up, with text messages sent at 80 per cent and automatic downtime or speed at 100 per cent.
Portfolio: combined sales raise the unit price
The package is a combination of hours, traffic, bandwidth, for example."50-pack month 100 Mbps bandwidth + 50 G traffic"The advantage of the package is flexibility to design different packages for different user groups: basic set for ordinary workers, high-speed package for R&D and overvalue package for residential households. V7 supports a wide range of meals available at backstages with different lengths, flow, bandwidth and co-payment, and users choose their own set when paying for themselves. The package also provides a promotional period, first half month price for new users, 90% rate for old customers, and increases in retention and income through price strategies.
How to combine the billing patterns of different user groups
The company’s employees: no limit on the amount of money per month, with a bandwidth of 100 Mbps, paid by the enterprise and not withheld from the individual employee. The residents of the campus’s dormitory: monthly or meal packages, personal fees, and a bandwidth of 50 to 100 Mbps. Different user groups use different costing strategies, distinguishing on V7 through user groups, each group binds a different billing template and automatically applies the accrual strategy according to its own user group for authentication purposes.
Attention to fee-forwarding model
The user changes the amount of the package month to flow, or the amount of the package to be changed from day to month, and then shifts the unused resources to one. The user changes the amount of the remaining days to traffic, which is converted into a volume level or refund, without any direct clean-up. The traffic has been repackaged for months, the remaining traffic can be cleared, the rest may be brought in through a monthly period or rendered obsolete, and the rules are written in the user agreement. The user should not be allowed to switch the billing model at random on the self-service page, which is prone to cost disputes and recommended changes in the billing pattern require approval by managers or allow switching only after the package expires.
The campus WiFi Authentication & Billing system has a choice of costing models that are centred on matching user groups. Long-term users use the month of wrapping, short-term visitors take day or hour, and large traffic users pursue flexible holsters using traffic-by-flow. A park is usually a combination of modes that differentiate between different population groups through user groups.