-
Is the system stable enough?
-
Whether functionality really suits the student's usage habits
-
Is it possible to operate in a complex campus network environment for long periods without repeating it?
That's why, in the middle school network,The network Authentication & Billing system itself, often determines the life cycle of the project and ROI ceilings。
I. Investment perspective: system stability ratio“Number of functions”More important.
In secondary schools, the use of the network is highly concentrated on the following scenes:
-
Student dormitory
-
Night peaks
-
Mobile terminals are extremely high (principal cell phones)
This imposes three mandatory requirements on the system.
1-delivering capacity to determine whether the project is or is not“Compliance and sustainability”
In the operation of the network of secondary schools, sub-description is not optional but:
-
Is there a long-term cooperation with the operator?
-
Can you support the real opening rate?
-
Is it possible to stand up in auditing and supervision?
A mature campus network Authentication & Billing system, with the following characteristics to be assigned:
-
Coding with authentication, costing logic
-
The dial-up anomaly does not affect already online users
-
Support account pool schedule to avoid peak periods of failure
-
Dial-up status versus user online status retroactive and auditable
The stability of the sub-dealing means that projects will not be forced to restructure or interrupt due to problems on the side of the operator.
2 x No focus switch during peak period, the bottom line for stability of the system
The most typical problem in middle school is not.“Can you get it online?”But:
The dorms are full of them at night.
A truly mature billing system that is designed to:
-
Distinguishing abnormally and truly offline
-
Maintain user online status using heartbeat
-
Avoiding centralized downlinks due to re-calculation of the billing engine
-
Delays and buffers at nodes such as deduction, renewal, expiration
Stability is not promoted, but through.“It's okay.”Show me.
II. Operationally: functions must be directly related to“Collect.”and“Less luck”
The online payment behaviour of students in secondary schools is quite clear:
-
Price sensitivity
-
I'm very impatient with the complexity of the operation.
-
I'm so dependent on my cell phone.
Therefore, the functionality design of the system must be close to the real use scenario.
1 Multiple forms of contribution, which are central to the improvement of conversion rates
In middle-schools, mature systems usually support:
-
Wet/ Pay Treasure Scrubbing
-
Auto-window alarm due
-
Early reminder due (rather than breakup due)
-
The payment is completed to automatically restore the network without manual intervention
This has two immediate consequences:
-
High self-financing rate of students
-
There's hardly any need for manual fees and manual access.
Operating costs have fallen and are part of ROI in itself.
2 Flexible billing strategy, adapted to real needs in secondary schools
Unlike higher education, secondary schools are more commonly charged:
-
by month/ semester
-
Overall accommodation coverage
-
Limit terminal numbers and avoid extra-account borrowing
The system needs support at the bottom:
-
Accurate terminal recognition
-
Multi-end and distribution management
-
Automatic recognition and processing of abnormal login
These powers are determined directly.Whether or not it will happen“One account for the whole dorm.”♪ The situation of the uncontrollable ♪。
III. THE REALITY OF SETTLEMENTARY SCHOOLS: SYSTEMAL RESOURCES“No equipment, no brands.”
This is one of the things you mentioned.It's a very critical issue, but many articles are afraid to write.。
1 Network environment in secondary schools, natural“Non-standardized”
The reality is:
-
Different buildings, different batches.
-
Core exchange, assembly, AP branding.
-
Some buildings are new, others old.
If the system of costing:
-
I'm relying on a brand.
-
We have to remodel the network.
-
High docking cost
So the project is in middle school.Almost impossible to land.。
2 x mature billing system, required“Device not relevant”
The Authentication & Billing system, which is truly suitable for middle-schools, should:
-
Not dependent on specific switchboards or AP brands
-
Support standard protocol access
-
Possible deployment above existing network structures
-
No forced reversal of reconstruction
This means to investors:
-
Initial input controllable
-
Low risk of adaptation
-
High school acceptance
-
Low resistance to project thrust
IV. THE THROUGH THIS TOPIC, AND WE CAN STILL CUT OUT THE DEPARTMENT OF THE ARTICLE
Based on“Investment in network operation and network fees for middle-school schools”The big theme is:You can keep breaking up into a lot of non-repeated, unsame pieces.e.g.: