The University WiFi co-operates as a clear trend in these years. Schools provide basic networks, operators offer integrated food packages and export routes, and platforms provide NATSHEL_AUTH_BILLING systems and technical wiring, sharing of benefits. For schools, large investment in export construction is avoided; for students, the integration package is cheaper than buying cellular traffic and a campus network alone; and for operators, campuses are a high-quality user pool. The three parties take what they need, but the combined operations are more complex than sounds. Accounts synchronize, authentication processes, split reconciliations, each link relies on Authentication & Billing to keep the accounts clear.
NATSHEL_BRAND's role in the joint operation of WiFi at the University of Higher Education is to provide the platform: NATSHEL_AUTH_BILLING system, dial-up gateway, Radius Proxy, and, if necessary, 5G dedicated network systems and technical support services. The co-operation of the Campus WiFi Authentication & Billing system involves certification, billing, account synchronization, NATSHEL_LOG_AUDIT as core functions.
Three-way division of labour and revenue split
The three-way responsibility for joint operations is clear: schools provide the basic network of POE+AP or POL+AP, manage student users and participate in revenue splits; operators provide integrated package accounts (cell phone plus campus WiFi) and export lines to be divided into agreed proportions to schools; platforms provide Authentication & Billing systems, dialling gateways and technical lifts.
The typical splits are 40-60% for schools, 40-60% for operators, and the platform receives a technical support service fee. Three patterns are common in practice: school dominance (60% for schools, 30% for operators, 10% for platforms), operator dominance (40% for schools, 50% for operators, 10% for platforms), tripartite balance (50% for schools, 40% for operators, 10% for platforms). There is no uniform criteria based on size of schools, competition among operators, negotiations, and there is no single standard. It needs to be stressed that the split ratio is the result of business negotiations and not the decision of the technical system; the system is supposed to keep the score properly accounted and allow the score to be valid.
Synchronise account with authentication process
The joint system of accounts is the core. Operators provide integrated package accounts, students open and pay in operators, campus network billing systems synchronize with operator backstage docking, and students authenticate access to the Internet via mobile phone numbers such as Portal, 802.1X. New openings require a coordinated interface with the operator backoffice to ensure synchronization of accounts, which has a smooth or unwieldy connection that directly affects the opening experience.
When authenticating the Internet, the dial-up gateway automatically selects the operator line to be used for PPPOE proxy dialling based on the type of operator that the student binds. V7 supports multi-operator access, auto-selection, load balance, failure switch, DNS intelligent re-direction, ensuring that the student flow is connected and experience stable.
Joint operations technical support and boundaries
The joint operation of the Authentication & Billing system, in addition to NATSHEL_AUTH_BILLING itself, includes three types of evidence that separates accounts are dependent on authentication logs, dial-up logs and billing logs; a pro-agent, Anti-Sharing, flow control, real name audits, etc., which are to be coordinated with an operator control network; and multi-operability business scenarios where user data and clearing calibres are differentiated between operators.
The boundaries of joint operations are clear: access to the three networks is a prerequisite and not a guarantee of operating benefits; technical programmes address the technical aspects of certification, billing, split-in-accounts, but whether the project is operational or profitable depends on commercial conditions such as operator resources, account systems, interface agreements and clearing calibres. Technology matching and operation are two things that are necessary, and programme communication should be separated from business.
Typical patterns and concerns of joint operations
Joint operations can also be superimposed on the 5G-net model: through a unified certification programme of 5G CPE, multi-operator 5G access is supported, campus in-networks are available under 5G networks, four network integration (wireline, wireless, 5G, object networking) is centralized and certified controls are implemented to meet the needs of Intranet office, intranet teaching, etc. These projects are large and wide-ranging and generally apply to larger schools, with separate assessments when selected.
In joint operations, several concerns are to be implemented in advance: the account synchronisation mechanism needs to identify those responsible (who is responsible for synchronization and how it fails to be handled); the split-account cycle and the basis for writing in the agreement (by certification log, dial-up log or billing log); the quality of exports and fault liability boundaries need to be agreed upon (whether schools switch and who bears the cost of switching when operators fail); and the student package design needs to balance appeal with sustainability.
The Authentication & Billing system transmits the certification request to the operator AAAS via Radius Proxy, which applies to areas where operators cannot provide a wide home account; it assumes the function of requesting forwarding, protocol transliteration, strategic bridging and matching the school’s certification system with the multi-operator's AAAA system. At docking, authentication attribute mapping, billing field consistency, failure retreat path must be verified, and the AAA interface and fields requirements of different operators may differ from one household to another.
The joint operations site also requires that the school informer and operator, the platform, communicate their needs: marketing and pre-sale in depth with the school informer department to understand the exact requirements and then enter project implementation management and operation services.
The school must implement the rules on splits, account-synchronous responsibility, export quality assurance, fault liability boundaries before moving forward.