Go to Main Contents

:: Industry developments

Deployment of the campus wireless WiFi system under unified multi-school management

There are several campuses in one school.——This is common in higher education schools, where new and old campuses are used simultaneously, and some have branches located elsewhere. The campus wireless wifi system has been deployed to single campuses enough.

Your position:Home > Content Centre > Industry News > > Text

There are several campuses in one school.——This is common in higher education institutions, where new and old campuses are used simultaneously, and some schools have branches elsewhere. The wireless wifi system on campus has become complicated enough to be deployed in single campuses, and the unified management of multi-schools is more difficult: data should be centralized, strategies harmonized, and authority divided. These problems can not be solved by adding a server; they involve structural decision-making and management model selection.

Centralized or distributed deployment

The campus wireless wifi system has two basic models for deployment in multi-school settings: centralized and distributed. The central approach is to place all the core billing (certificated servers, billing databases, strategy management backboards) in one data centre (usually the main campus), while other campus certification requests are processed through dedicated lines or VPNs. The benefits are data concentration, strategic harmonization, and maintenance only need to manage a single system.——If the special line between the main campus and the sub-campaign is interrupted, users in the campus cannot authenticate access to the Internet. The distribution is that each campus has a separate billing system, which does not synchronize data between schools in real time.

The choice of the two models depends on the size and quality of the campus. If the number of users in the sub-campaign is small (for example, there are only a few hundred), it makes sense to concentrate.——It is not worth deploying a full billing system for hundreds of people.——A frequent break in the line leads to poor centralization. There is also a compromise solution: centralized management strategy, distributed processing certification. The strategy is developed and sent to the certified servers of each campus in the main campus, which is completed in the local campus and whose billing data are regularly aggregated to the main campus. Such a program requires a heterogeneous mechanism for distributing and synthesizing data under the system support strategy, not all of the systems with that capability.

Balance between strategy alignment and local differences

One of the objectives of integrated multi-school management is strategic coherence.——The same package name, the same price, the same speed limit, and the same user has the same experience of accessing the Internet in any school district. But the actual scenes vary widely from campus to campus. The new campus exports bandwidth 4G, high AP density, good wireless coverage; the old campus is only 1G, older AP, and uneven. If two schools use exactly the same speed-limit strategy, the new campus experience is excellent, and the old campus peak time is not fast enough.

The right thing to do is..."Strategy framework alignment, local differentiation of parameter values"The policy framework, such as the name of the package, the authentication method, and the payment process, is consistent across campuses, but parameters like speed limit values, time configurations, bandwidth pool size are configured separately according to the actual resource conditions in each campus."Frame Harmonization+Dalithration": Sets a strategy template for managing the backstage of the main campus, and each campus fine-tunes its parameters on the basis of a template. If the billing system is only one-size-fits-all (all schools must have identical parameters), the diversity needs of multiple campuses cannot be met.

Relay of user-wide travel across campus

The students run around the main campus and the sub-campus (schools are taught in the main campus, in the sub-campus or vice versa), which is a typical model of multi-school settings.——The automatic continuation of the balance and the cumulative flow is uninterrupted. A centralized deployment naturally supports this continuity, as all data are in the same database. For a distributed deployment to be cost-based, real-time synchronization between school district billing systems for user data is required——Changes in balances, changes in the suite of meals, and changes in authentication status require real-time transmission between campuses. Real-time synchronization technology is not difficult to achieve, but requires sufficient stability in network connectivity among campuses. If a dedicated line is unstable, real-time synchronization can be delayed or even failed, resulting in users seeing it when they log into subdistricts."Insufficient balance"The main campus is just full, and the data hasn't been synchronized.

The compromise is to add one in the certification process"Real-time balance query"Step: When processing certification requests, the campus authentication server first searches the main campus database for a real-time balance and confirms that there is sufficient balance before it can be accessed. Even if there are delays in synchronization, users will not be unable to access the Internet because of inconsistent balances. The cost is that each certificate requires crossline search once, and if the line is delayed significantly, authentication takes more time.

Tier management of the permissions for the transport

The problem is how to divide the shipping lines in multi-school settings. If all the functions are concentrated in the main campus information centre, daily problems (user complaints, tactical adjustments, reboots) in the campus must be handled by people from the main school area, and they are slow to respond. If each campus has independent dimensions, there may be inconsistent strategy configurations and inconsistent operating practices. The wireless Wifi system on campus should support layered authority management: the main campus information centre has high competence for global strategy configuration, systems upgrades, data aggregation, etc.; the principle of low competency allocation among the various campus operators is that local policy refinements, user complaint processing, local equipment administration etc."Local problem resolution, global decision-making"。

The difficulty of stratification is that the area’s security capacity is limited to the sub-school. Some campuses have no dedicated personnel, only part-time administrators occasionally look at the system. In this case, local authority for carrying out a service is not useful and all problems are returned to the main school complex.

Emergency preparedness for the disruption of line lines

Multi-school deployments must take into account the disruption of the special circuit. After the break, centralized deployed campus users cannot verify (a certification request cannot reach the main campus), distributed distribution of assigned campus users can access normal Internet (but the strategy and data in the main campus cannot be synchronized)."Emergency authentication server"——The emergency authentication server only creaks basic authentication strategies and user balance data, without the need for a complete billing database, but ensures that the campus will have access to at least one of its users during the break.

Data aggregation and harmonization of statements

In the multi-school setting, school management needs to see global operating data: billing revenue, bandwidth usage, user distribution, and complaints from each campus. These data need to be aggregated from the school district billing system to the main campus, generating a uniform operating report. The campus WiFi reporting function should support automatic aggregation of multi-school data, instead of combining Excel when the carrier manually exports the reports from each campus.——The same set of meals, the same unit of account, the same report field."Frame Harmonization+Dalithration") The presentation of the report should be summarized by indicating the difference points for management to see"Why do the average user income differ between the two campuses?"。

Multi-school unified management is not"Simple magnification of the single campus programme"It has its own problems with independent structural decision-making and management models. These issues do not arise when a single campus is deployed, but must be seen in the multi-school landscape. The structure is wrong, and the costs of subsequent transportation and management are multiplied."The system doesn't support multi-school campuses."Change the system too much.

Access Program I'll be right back. Telephone counselling