The implementation of the campus network Authentication & Billing is a system engineering project involving multiple links such as network re-engineering, system interfaces, user migration, and testing to go live. Deployment is well done, the system can be smooth and steady; failure of certification, billing errors, user complaints etc. may occur and affect normal use of the campus network.
Pre-deployment preparations
Pre-deployment preparations are important and adequate preparation will avoid a number of subsequent problems. The first is to develop detailed status studies on existing network structures in schools, brands and solid versions of access equipment (AC, BRAS, switchboards, etc.), the functioning of existing certification systems, user size and usage habits, an interfacing of a cartoon and a learning engineering system; The second is the design of a programme, based on current status studies, to design the deployment architecture of systems (by-pass or by-link deployment, single or double, and whether or not), network re-engineering programmes (VLAN division, IP address planning, route configuration), docking programmes (to be interfaced with AC/BRAS, one cartoon, pedagogic systems), user migration programmes (how existing user data are migrated to new systems); the third is environmental readiness, preparation of server hardware, operating systems, databases, web environments to ensure server performance and network connectivity meet requirements; and the fourth is personnel preparedness to define project leaders and technicians from school and factory sectors, and to develop detailed project plans and communication mechanisms. The more thorough the preparations, the smoother the follow-up.
System installation and basic configuration
The main tasks at this stage include: first, the installation and optimization of operating systems, the installation of server operating systems, the improvement of system parameters (document description, memory parameters, network parameters, etc.), the closure of unnecessary services, the configuration of firewall rules; second, database installation and configuration, the installation of databases (MySQL, PostgreSQL, etc.), the improvement of database parameters (connection, cache size, log configuration, etc.); and the creation of databases and users; Third, application system installation, deployment of the campus network Authentication & Billing applications, configuration of system parameters (ports, log path, database connection etc.); fourth, Liicense activation, generating Licenense requests based on server hardware information and activating the system ' s official Liicence; fifth, base configuration, configuration of basic parameters of the system (school name, time zone, language etc.), administrator account number and permission, system backup strategy. System implementation and configuration are the basis for deployment implementation, and require strict compliance with the manufacturer ' s installed document operation to ensure that each chain is correct. Once installed, a system health check should be performed to confirm that all services are functioning properly, the database is connected normally and the system logs are not abnormal.
Network docking and equipment connection
Networking and equipment connectivity is the most critical and problematic link in deployment. The main tasks at this stage include: AC/BRAS configuration, equipping the access device with RADIFUS server addresses, shared keys, authentication ports, billing ports, positioning Portal recalibration rules and Portal server addresses; and connectivity testing, testing of network connectivity between AC/BRAS and Authentication & Billing systems to ensure normal communication at RADIUS ports (1812/1813) and Portal ports; Third is authentication combinations, which use test accounts to perform certification tests to verify whether the authentication request can be sent properly, whether the authentication results are correctly returned and that users can access the Internet; fourth, a costing combination, which verifies whether the billing request can be sent normally, whether the billing record is generated correctly and whether the cost calculation is accurate; fifth, a downlink link, which validates whether the user's access equipment can send the downline request correctly, whether the system can properly close the session and stop the billing; and sixth, a strategic combination, which validates the policies of bandwidth limitation, duration limit, VLAN. The interface process should be gradually validated by linking connectivity, authentication, counting, recalculation and strategy (certification failure, time-consuming, network interruptions, etc.). Problems identified in the interface should be recorded and resolved in a timely manner, often including inconsistencies in RADIFUS keys, Portal recalibration configuration errors, mismatch of attribute mapping, firewall interception, etc.
System docking and data migration
In addition to the network equipment interface, the campus network Authentication & Billing system also requires interfacing with a school ' s cartoon, engineering and financial systems and migration of existing user data. The main tasks at this stage include: first, a cartoon docking, configuration of a toon payment interface, testing of fees, charges, reconciliations etc., ensuring safe and accurate payments; second, an engineering system interface, configuration of the UNU data interface, testing student information synchronization, automatic opening and decommissioning functions, ensuring that data are synchronized accurately and in a timely manner; third, finance system matching, configuration of the finance system interface, testing web fee revenue reconciliations, invoice issuance, etc. The fourth is the migration of user data to move existing authentication systems (accounts, passwords, packages, balances, etc.) to new systems, where data are migrated for reconciliation and data integrity; the fifth is the configuration of a package with various packages (package months, traffic, daily etc.) and billing rules in the new system, based on school operating strategies. The system interface and data migration involve multiple collaborations, requiring adequate communication with a cartoon manufacturer, SAS vendor, finance department, etc., to confirm interface conditions and operational rules. Data migration is a high-risk operation, which should be backed up before migration and comprehensive data checks should be performed after migration, and problems identified and issues recovered or repaired in a timely manner.
Test and Run
The main tasks at this stage will include: first, functional testing, which will provide a comprehensive test of all system functionalities, including certification, billing, package, self-service services, administrator backstage, system interface, etc., to ensure that each function works normally; secondly, performance testing, pressure testing of the system, simulation of accreditation requests under high and simultaneous scenarios, validation of systems ' co-processing capacity, response time and stability, ensuring that the system is able to withstand school peaks and releases; thirdly, safety testing, security scanning and penetration tests of the system to check for safety gaps and ensure system security; The fourth is user acceptance testing, which invites selected students and teachers to be tested, collects feedback from users and identifies and fixes problems; the fifth is trial operation, running on a small scale (e.g. in some accommodation buildings), observing system performance and user feedback, gradually expanding the scope of test operations. Testing and commissioning are the last stop before the system officially gets online. They must be fully tested and strictly closed and cannot be lined with questions. The issues identified during the tests should be recorded in a disaggregated manner, with clear priority levels, high priority issues must be repaired before they go up, and low priority issues can be optimized over the upper lines.
Officially online and cut.
After testing and commissioning, the main tasks of this phase are to prepare students for upgrades through a school bulletin, micro-letters or text message. The first is to develop a detailed online cutting programme that clearly identifies the time, steps, division of labour, rollback pre-clication etc., which usually takes place at a late hour or during leave with fewer users; the second is to notify users of the timing and impact of the upgrade of the system in advance by informing students of the timing and impact of the system through school announcements, micro-message public, SMS, etc.; and the third is to synchronize the data eventually and to do the last data synchronization before the cut to ensure consistency between the new system and the old system; The fourth is a cut-off, which is implemented in step with the cutting programme: the old system is discontinued, network configurations are switched, new systems are activated, authentication and billing functions are validated, observation systems are operational; fifth is an on-line guarantee that after-line cuts are completed, a live or remote duty of the operator is arranged, close monitoring of the system's functioning is maintained, user complaints and system anomalies are processed in a timely manner, usually requiring safeguards for 3-7 days. Formal up-linking and slicing are high-risk operations, and there must be a perfect rollback pre: if serious problems arise during the cutting process, it can quickly roll back to the old system and avoid long-term impacts on students' access to the Internet.
Common problems and approaches
Campus network Authentication & Billing deployment and operation, with several types of problems common to the following: first, certification failure, students' inability to certify access to the Internet properly, often due to inconsistent RADIFUS keys, code errors in accounts, AC/BRAS configuration errors, network failures, system service anomalies etc., by checking progressively by link: network connectivity first, AC/BRAS configuration then, systems services and logs again, and final check of account number status; Second, the calculation of fees was incorrect or abnormally withheld, often due to errors in the configuration of costing rules, inaccurate traffic statistics, non-inforcement of package changes and delays in data synchronization, inter alia, by checking billing rules and user packages, checking traffic statistics logs and making cost adjustments and refunds where necessary; third, performance problems, peak time periods for certification of Carton or slow system response, frequently caused by inadequate hardware configuration, slow database querying, system parameters not optimized and over-design capacity through optimization of databases and systems parameters, upgrading hardware configurations and using distributed deployments when required; Fourth, there are problems of connection with a cartoon, the interface with the engineering system, and common reasons include interface changes, mismatches in data formats, network interruptions, other systems malfunctions etc. by communicating with the other manufacturer, confirming the interface status, checking data formats and network connectivity; fifth, user complaints, students' dissatisfaction with billing, speed, services etc., through patient listening, timely response, identification of causes, proper resolution while collecting feedback for system optimization. In case of problem, the problem should be identified and then targeted treatment measures taken to avoid blind re-opening or modifying configurations and avoiding any proliferation of problems.
The implementation of the Authentication & Billing system is a system engineering process that requires several stages, such as preparation, installation, network interface, system docking, testing and commissioning, with clear work content and attention at each stage. Common problems in deployment implementation include certification failures, bill errors, performance issues, match-over problems and user complaints, which need to be progressively checked and targeted according to the chain. The selection of a mature and stable campus network, Authentication & Billing system, the development of detailed deployment implementation programmes that are strictly process-based, fully tested and then re-lined, and the provision of security and wiring after being online, will ensure smooth connectivity and steady operation of the system, provide quality Internet access for students and create good operational benefits for schools.