Students on the dorm link WiFi, open browsers, enter account password——This seemingly simple online action is backed up by a complete set of NATSHEL_AUTH_BILLING processes. Dismantling this process will help to understand where the system is located in the school network structure and quickly identify why it is happening.
Step 1: Operators ' access to schools and bandwidth
The agreement will contain key provisions on tolerance, coverage, proportionality, service commitments and so forth.
From a technical point of view, the core action of the operator's entry is to connect export bandwidth to the campus network. The bandwidth and quality stability of this physical link directly determines students' Internet experience. When the operator's bandwidth comes in, it will be connected through BRAS equipment to the campus network core switch and become part of the campus network export.
NatShell V7 Authentication & Billing is deployed on this level to process all BRAS certification requests. Regardless of the operator selected by the student, authentication traffic passes through a system that determines whether the account number works, which operator belongs to, what the current package is, how many traffics remain or how long it lasts.
Step 2: Wireless AP coverage and signal access
The deployment density of AP, frequency selection, and channel planning influence the network’s coverage.
The first request for a mobile phone or computer to send is DHCP access to an IP address before triggering the subsequent authentication process.
The frequent failures of this link include: APP de-linking leading to a lack of signal in some areas, 2.4 G and 5G frequency interference causing slow network speeds and the instability of tunnels between AP and AC leading to frequent downlinks. These problems require network operators to search on floor by floor, not on a billing system, but affect students’ perception of network quality.
Step 3: Portal page and identification
Students can be redirected to the Portal authentication page by opening a browser and entering any site. This is the direct interaction of the billing system with the user.
Portal page design is important. Too simple and unprofessional, too complex to influence user experiences. NatShell V7 supports Portal page customization, where schools can design their own page styles or set different push strategies such as first access pop-ups, regular validation of usage processes, forced jumps after default.
The student enters the account password on Portal page and authenticates that a request is sent to the billing system via RADIUS protocol. When the system validates the account number password, the corresponding operator, package, balance state is checked and the access policy is pushed down to AC or Bras.
A successful student can have regular access to the Internet. Students who fail to do so will continue to stay on Portal page, pointing out the reasons for the error: password errors, account arrears, expired packages, operator arrears, etc.
Step 4: Strategic development and traffic control
After authentication, the system sends out a access policy. This strategy defines user access rights: which segments of the network are accessible, how much bandwidth is ceilingd, how many devices are online and when they are allowed to use.
Different packages correspond to different strategies. Basic sets may be limited to 10 Mbps, and advanced ones will be fast. The monthly and school-time packages are charged differently, and the strategies for flow and time-to-time are not the same.
NatShell V7 strategy engines support a rich configuration option. They can be distributed in combination with multiple dimensions, such as user groups, operators, utensils and time periods. For example, one operator can remove bandwidth restrictions during late nights to attract student renewals.
Step 5: Online state maintenance and abnormal detection
After the certification was successful, students started to access the Internet. But this "online" status is not an end in one certificate but needs to be maintained on a continuous basis.
The system will trigger alarms if an abnormal behavior is detected (e.g., a large amount of traffic in a short time).
Common anomalies include: account numbers are stolen and used online elsewhere; students ' private routers bypass the end limits of the billing system; proxy software is used to try to hide their true identity. V7 identifies these problems through end fingerprinting, behavior analysis, tactical connections etc.
Step 6: Billing deductions and billing
Depending on the type of package, the fee is calculated in two ways: a prepaid set of meals for the school year, which is included in the monthly package and is deducted at one time during the beginning of the month or when it enters school; a paid package that is available on schedule; a system to record usage in real time; and an invoice generated at the end of the month.
In either case, the core logic of the billing is the same: it is time-consuming and traffic-based. When the balance is insufficient, the system alerts students to the charge; when the fee is owed, the system limits access to the Internet or lowers the basic package.
The V7 billing module supports a variety of billing rules and can be configured flexibly.
Step 7: Data reporting and business analysis
Data generated throughout the Authentication & Billing process are aggregated into a database of the billing system. These data include: basic information on users, authentication records, online time frames, traffic usage, bill details, complaint logs, etc.
For students, you can check their Internet records and bill details. For operators, you can analyse user activity, rates of renewal, and the reasons for complaints, which are used to optimize the design of the package.
The V7 Operations Analysis Module provides visualized data reporting to support day, week and month multidimensional statistics.
You know the whole process better than the wiring.
In many schools, the first reaction is that "fee systems are wrong" when students complain about slow or inaccessible Internet access. In practice, billing systems only cover certification, strategy payments, and fee deductions.
Understanding the complete Authentication & Billing process helps to quickly locate those responsible when problems arise: whether it is a billing system or an Internet device; whether it is a operator or a school infrastructure problem. NATSHEL_BRAND will provide web-tapping files and troubleshooting manuals at the time of project delivery, in conjunction with the location of the school transporter team.