Large enterprises or industrial groups often have multiple parks, with a headquarters in Park A, where they develop and produce in Park B, where their employees move between campuses. If each park has an NATSHEL_AUTH_BILLING system, staff members are re-registered to another campus, re-paying fees are extremely poor.
A uniform multi-park certification structure
The central accreditation management centre is deployed at Headquarters, which operates the V7 NATSHEL_AUTH_BILLING system and is responsible for unified user administration, a uniform authentication strategy, a harmonized billing strategy, and a unified data analysis. Each campus deploys distributed access nodes (NATSHEL_AUTH_GATEWAY or AC) to be responsible for local user access and transmission of certification requests. User connects WiFi in any park area, access nodes transmit authentication requests to the accreditation centre at headquarters, authenticates the account number password and returns the result, and access node executors. Users of the entire process were unconscious and did not feel that requests for certification had run to Headquarters.
Trans-campus user roaming
The cross-campus is a central experience of uniform multi-park certification. Staff members are certified online at the headquarters campus, travelling to the R & D park, connecting with WiFi in the R & D campus, and the system recognizes that this account number has been certified at Headquarters, and automatic release does not require reentry of the user code. This is done by maintaining a single user online form at the HQ Accreditation Centre, recording which campus, AC, AP, each user is currently on line. NATSHEL_BRAND V7 supports uniform cross-campus certification and user roaming, which allows direct access by users to any other campus after being certified in any one park.
You have to watch the session syncs.
The technical difficulty of travelling across campuses is real-time synchronization of conversations. Users move from headquarters to the R&D park, and Headquarters online status is synchronized in real time to the R&D park access node, otherwise R&D will not be able to track the user online state, requiring recertification. There are two ways to do this: first, real-time synchronization, where the user immediately sends the status of the headquarters to all park nodes when it comes to line or down, with the advantage that it is good in real time, and the disadvantage is high in network cost and a lot in campus pressure. Second, search on request for authentication node, actively checking the user status at Headquarters when it receives the request for certification, with the advantage of net expense and delayed query per certificate. V7 systems are implemented by real-time synchronizing local caches, which are carried out in real time on a change of status and access node caches the latest user status, check for caches before checking headquarters and balance real-time and network costs.
Harmonized costing strategy
The cost strategy for uniform multi-park certification is to be harmonized, but not all campus prices are the same. Network costs vary between headquarters and remote parks, with a different set of meals, but the costing model and user accounts are to be harmonized. Monthly packages purchased by users at Headquarters are equally valid to R & D parks and do not need to be repurchased. If the prices vary from one park to another, which price will be charged when users cross the campus? Rules should be established in advance: usually charge fees based on the price that the user belongs to the park or on the price of access to the park, as well as write them in the user agreement.
Unified user management
The user register, fees, changes, and write-offs are all operated on the headquarters system, and the data is synchronized to all campuses in real time. At the time of staff entry, accounts will be created at Headquarters and will be available in all campuses on that day; at the time of staff departure, the number will not be valid for any park area at the same time.
Downgrading programmes when the park breaks off the grid
The most feared feature of the unified multi-park certification is that a link between a campus and headquarters has been broken, that requests for accreditation cannot be sent to Headquarters, and that all users cannot. There must be a downgraded system. First is local credential, where park access nodes cache authentication information from recently connected users, which can be released with creaking information when the connection breaks, with a 24 to 72 hour Creculator. Second, local Radius server backup, one lightweight Radius server deployed in each campus, synchronizing the user database at headquarters, and local Radius taking over certification when the link breaks. The third is local Portal authentication, where the access node to the park is switched to local Portal when the link breaks, certified by a local account database, and automatically returned to central certification once the connection has been restored. Destitution options are configured when the programme is designed, and do not wait until the link is broken before they are resolved.
Harmonization of data analysis and reporting
A direct benefit of uniform multi-park certification is centralized analysis. The accreditation centre at Headquarters collects certified logbooks, billing data, traffic statistics for all campuses and produces consolidated statements across the park areas. Managers can see a comparison of user numbers in each park, income comparisons, online ratios, traffic peak comparisons, and provide data support for operational decision-making. For example, it may be found that users in a park are growing fast but have low incomes, possibly with lower prices or higher amounts of unpaid fees; a low online rate of a campus, which may be characterized by poor web quality or blind coverage.
Deployment order and validation
The multi-park unified certification does not require a one-time full switching, starting with the deployment of a validation centre at Headquarters, selecting a campus for pilot access, testing four scenarios for certification, billing, roaming, and downscaling. After the pilot is completed, each campus will be connected to another campus and observe for one week after it has been accessed.
The central focus of the multi-park certification system is centralized management of additional distributed access. Headquarters accreditation centres handle users, strategies, billings, data, local access and transmission of park access node tubes. Cross-campus tours solve the delays in synchronizing sessions, a flat charge that allows price differentials between parks, a local buffer or a backup Radius for network downgrading, and data analysis that supports operational decision making.