A bid evaluation phase that is more likely to be ignored than the functional checklist, but which has been frequently validated during the operational phase, isWhether the system architecture is fit for a real network environment in middle-level schools。
The general lack of uniformity in the construction phase, the mixing of equipment brands and the diversity of export structures in secondary schools have made clear the requirements for the structure of the deployment of NATSHEL_AUTH_BILLING system on campus:High-level coupling, centralized, low-intrusive and scalability is required。
I. Objective constraints on the deployment structure of the network environment for secondary schools
In practical projects, the network of secondary schools usually has the following characteristics:
-
There are significant differences in the network structure of the teaching and dormitories areas
-
Core, assembly, access from different manufacturers
-
Wire-to-line mixed deployment
-
Export may be a single operator or multi-operator
In this environment, resistance is often encountered during deployment and later expansion costs are constantly magnified if the campus network Authentication & Billing system relies heavily on a particular type of equipment or network to boost.
Therefore, the campus network in the middle school project Authentication & Billing system, which is not the first to be addressed by deployment architecture“Is the function rich?”But...How to complete access without re-engineering existing networks。
ii. Campus Networks: typical deployment location of Authentication & Billing system
In the middle school project, a mature campus network Authentication & Billing system is not usually deployed directly in access or convection layers equipment but rather usedIndependent system deployment model。
Authentication & Billing System and Network Device Decoupling Deployment
Common deployment patterns are:
-
Campus network Authentication & Billing system as a stand-alone logical node
-
Access between core networks and exports, or by bypass roads
-
Private functions not dependent on switches, ACs or APs
The core advantages of this deployment approach are:
-
Without prejudice to the original network forwarding logic
-
Not dependent on specific manufacturer functions
-
At a later stage, it can be upgraded or expanded independently.
For a long-term phased environment such as secondary schools, uncoupled deployment is a more sound option.
2. Centralization of cloud deployment into mainstream form
In the context of multi-school or future expansions in secondary schools, the campus network Authentication & Billing system is increasingly deployed on cloud lines:
-
Core authentication, billing, strategy, data module deployed on cloud end
-
Only necessary access and transmission equipment will be maintained at the school
-
Schools access the unified platform through safe passages
The advantages of such a structure are:
-
Integrated multi-school area management
-
System central maintenance
-
Harmonised storage and analysis of data
In actual projects, even where there is currently only a single campus, cloud access capacity is usually reserved to accommodate subsequent expansion.
III. THE REAL WAY OF THE CERTAINING PROCESS IN THE ARRANGEMENT STRUCTURE
In the middle school project, the campus network Authentication & Billing certification process usually follows the following path:
-
Terminal access to campus network
-
Network device directs authentication requests to Authentication & Billing
-
System verification of user identification information (symbol, cell phone, etc.)
-
Verify terminal numbers, user policies, billing status
-
Generate user sessions and send access rights
Throughout the process, network equipment is responsible only for forwarding and access control and does not participate in costing logic judgements.
-
Overloading of network equipment
-
The authentication strategy is spread across a variety of devices.
-
Increased complexity of maintenance at a later stage
IV. Position and role of billing engines in the architecture of the system
In the middle school project, the fee-based engine is not an auxiliary module but a core component that goes alongside the certification module.
1. Cost engines run independently to avoid collusive risks
A mature campus network, Authentication & Billing system, will independently design the billing engine as:
-
Independent processes or services
-
Decoupling with authentication status
-
Separately extended computing capacity
The billing engine is primarily responsible for:
-
User-based cycle calculation
-
Cost deductions
-
Due Judgement
-
Anomalous state of affairs
This design avoids disruption of the authentication chain due to abnormality of the costing module.
2. Cost-processing mechanisms for peak periods
At night peaks in dormitories, users of middle-level schools are concentrated online.
A reasonable deployment structure usually has the following characteristics:
-
Counting asymmetrical
-
Deduction operations batch processing
-
Postponement of change in status effective
This would avoid centralized network break-ups or system shaking at fixed points of time.
V. THE REAL PLACE OF DRAGGING METHODOLOGY IN THE ARRANGEMENT STRUCTURE
In middle-school projects involving the export of operators, dialling modules are usually available as independent subsystems in the campus network NATSHEL_AUTH_BILLING system.
1. De-installing of dialling modules without authentication process
In a rational structure:
-
User authentication successful ≠ Call immediately.
-
The dial is triggered by a strategy.
-
dialling status is associated with user sessions, but not tied
This structure can be used when substituting anomalies:
-
Keep User Authentication Status
-
Avoiding the online user-consortization
-
Provide automatic switching and retrying capability
2. Sub-designation in a multi-export environment
The NATSHEL_AUTH_BILLING system of campuses generally supports:
-
dial-up pool
-
Grouping by export
-
Planted by strategy
The role of the dialling module in the architecture is:Export Resource SchedulerThe role of the person, not a simple dial-up tool.
VI. CENTRALIZATION OF USE DATA IN THE RESOURCES FOR DISTRIBUTION STRUCTURE
In the middle school project, user data are usually:
-
Authentication Log
-
Online Session
-
Recording of fees
-
dialling status
The mature campus network Authentication & Billing will centralize these data in a unified data layer rather than scattered over the network equipment.
This concentration could be achieved:
-
School view real user size in real time
-
Operator reconciliation of fee data
-
Post-audit and issue retroactive
VII. Structure for system expansion and access to new campuses
In the course of their operation, secondary schools often appear:
-
Construction of new accommodation building
-
New school areas are operational
-
Original network upgrade
A reasonable campus network, Authentication & Billing deployment architecture, should support:
-
New access area is only network-side configuration
-
No change to the core costing logic
-
Without affecting the original user running
The cloud-end centralized deployment + light access patterns within schools have a clear advantage in such expansion.
VIII. NatShell EXPERIENCE OF USE RESPONSIBILITY IN THE SCHOOL STANDARDS PROJECT
In the context of the physical secondary school project, the campus network provided by NATSHEL_BRAND is usually used in the following:
-
Clouds are concentrated.
-
Certification, billing, dialling module decoupling
-
Multi-brand network devices compatible access
-
Integrated multi-school management structure
The system is not dependent on specific network vendor equipment capabilities and can be rapidly deployed on the basis of existing campus networks, and supports later smooth expansion to reduce duplication of construction costs.