FromOverall architecture perspectiveComplete dismantling of the deployment of a mature campus network Authentication & Billing system.
I. What exactly should the NATHHELL_AUTH_BILLING system be deployed to the network?
The campus network Authentication & Billing system in the real university networkYou can't just find a server.。
A stable deployment location must meet three points simultaneously:
-
You can see the real flow of users.
-
Do Not become a Internet Bottle
-
Without compromising core transmission stability
1 Main deployment location: between exports and convergence
Most of the higher education institutions, Authentication & Billing systems are usually deployed at:
-
Before the campus network exits,
-
Or between the core exchange and export gateways.
-
Access by bypass or serial
The benefits of this are:
-
All traffic that requires authentication, billing and accurate identification.
-
No net forward capacity to affect core exchange
-
The network still has a controlled downgrade when the system is abnormal
2 ⁇ Difference in the deployment of accommodation and wireless scenes
In the dormitory wireless scene, it is common practice to:
-
AP → Gather → Core → NATHHELL_AUTH_BILLING System → Exports
-
NATHHELL_AUTH_BILLING System Unified Processing Hostel Users
-
Teaching, office traffic can be done by strategy.
This approach would facilitate:
-
Exact control accommodation billing
-
Without affecting the stability of teaching and office networks
II. WHY MAKING SYSTEMS VERY PROMOTING TO BE AROUND THE CURRENT OVERSIGHT
Many universities will deploy the campus network Authentication & Billing system in local office rooms at an early stage.
But as the scale increases,Cloud deployment is becoming the mainstream choice.The core reason is not“New Tide”But...Stability and transport costs。
1 cloud deployment is not about performance, but reliability
In real operations, cloud deployments are mainly addressed by:
-
Single point failure risk
-
Local engine room power, environmental issues
-
Aging and maintenance costs of hardware
NATHHELL_AUTH_BILLING is not a compulsive system, butExtremely dependent on continuous steady operation。
Cloud deployment can:
-
Multiple Nodes Redundancy
-
Quick down switch
-
Trans-geographical response
This is particularly important for the long-run campus network NATSHEL_AUTH_BILLING system.
2 ⁇ Cloud ≠ All traffic is cloudy.
The mature campus network Authentication & Billing system is usedClouds on the control surface, data localStructure:
-
Authentication, billing, strategy control on cloud end
-
Actual user traffic is still being transmitted locally
-
The clouds don't become a traffic bottle.
Such a structure would guarantee system stability without sacrificing performance.
This stratification, balancing stability and efficiency, is being used in the design of NATSHEL_AUTH_BILLING on campus network.
III. The core of integrated multi-school administration, not“- Get in line.”But...“I can handle it.”
The real challenge for educational groups or multi-school colleges is not network, but management.
1 Base premises for integrated multi-school area management
The mature campus network Authentication & Billing system must, in the multi-school landscape:
-
A unified Authentication & Billing platform
-
Multi-school strategy centralization
-
Centralized storage and analysis of data
At the same time, however, support:
-
School-level strategy differences
-
Independent exports and link conditions
2 x Common multi-school deployment pattern
The typical structure is as follows:
-
Cloudy Authentication & Billing Centre
-
Local access devices for schools
-
Strategy is sent out. Status implemented locally.
This would enable:
-
User-wide campus Seamless Authentication
-
Harmonization of the rules on costing
-
Data concentration statistics
It does not affect the global system because of a school district link problem.
How the inter-school Seamless Authentication is actually realized
So-called“No sense of it.”Not without authentication, but...Authentication does not interrupt the experience。
In multi-school environments, Seamless Authentication usually relies on:
-
Unified identity system (symbol / work number / cell phone number, etc.)
-
Unified account database
-
Session status is consistent with cloud
When users access different campuses:
-
System rapid identification
-
Auto Match Original Permissions
-
No need to repeat authentication information
This capacity is particularly critical for cross-school teaching, hands-on training and rotation.
V. The real way of being implemented by operators on the campus network
In many colleges, export networks are not simple.“A broadband.”。
Common scenes include:
-
Multi-operator exports
-
Hostel line billing
-
Different users go different exits
1 ⁇ What's a operator dialling?
Operators' referrals are essentially:
-
Completion of user certification on campus web side
-
Launch operator dialling by Authentication & Billing
-
Export accounts are managed centrally by the system
This would enable:
-
Multi-user shared export resources
-
Harmonized billing and strategic control
-
Avoid manual maintenance of large number dial accounts
2 ⁇ Synergy between the transfer and the system of costing
A mature campus network Authentication & Billing system, which usually includes the following:
-
User-lined dialling
-
Users release resources
-
The billing state is strongly associated with dial-up status
The system will not appear:
-
Users are offline but dialing is still in use
-
Or dialing interrupted but the bill continues.
It's a lot of systems.“Looks like it's a good proxy. It's not working.”Fundamental differences.
VI. The ultimate goal of the overall architecture: stability, concentration, scalability
From a holistic deployment perspective, the complex nature of the Authentication & Billing system, which ultimately seeks not to be complicated but rather:
-
Clear structure
-
Clear lines of responsibility
-
Easily expanded, easily maintained
-
It's not going to work for long.
NATHHEL_BRAND, IN THE PRACTICE OF 21 YEARS OF HIGH SCHOOL PROJECTCloud deployment, integrated management of multi-school areas and stabilization of the transfer mechanismThe product architecture is constantly being optimized, resulting in the current system of a stable, functional and cost-effective campus network NATSHEL_AUTH_BILLING.