Real name certification can be performed, and the billing cannot be done; or it can run, and the real name certification cannot pass through public security checks.
We have to do it next time in the light-in-house structure. WiFi issue of authenticated certification and billing, the key is not functional stacking but the correctness of network control points.
I. Why do you have to do this with the real name certification and billing?
Under the dual pressure of public security inspection and operation management, when a light-in-house hotel is certified only as WiFi, without consideration for billing and control, the following problems usually arise:
-
Real name authentication is only a front page, and it's not really binding online behavior
-
Network exports are uncontrollable, authentication cannot be tied to release
-
Log exists but cannot match the real billing traffic
-
The network of tenants, employees and outsiders is mixed.
In such cases, public security is more easily judged to be:
“Certification is not linked to actual network behaviour and there are management risks.”
So, in the light-in-house hotel scene,WiFi actual name certification and billing must be centrally planned and settled。
II. Preconditions for one step to be achieved: the need to regain control over network exports
The only underlying reasons why hotel alone cannot be certified and billed are:
There is no cyber export control on the side of the hotel.
One light cat per room, directly connected to the operator, means:
-
The authentication system is not able to intercept traffic.
-
The billing system cannot count real usage
-
Audit logs cannot be centrally generated
The only right direction to solve a problem one by one is:
Let the certification and billing system be in a position of real export.
III. Operator equipment sinking is the only viable path to a hotel with light access
In physically accessible projects, a key condition for real name certification and billing in the light-in-house hotel must be met:
The operator agreed to deploy network control equipment to the hotel room.
In this context, there has been a fundamental change in the structure of the network:
-
The light cat traffic first gathers in the hotel room.
-
Reunification of the UA operator
-
The hotel has de facto export control points.
At this point, the basis for implementation is available through real name certification and billing.
IV. NatShell × Connected: Full programme for the certification and billing of physical names in households on light
Based on the cooperation with connectivity, NatShell formed a set of light-in hotels.One deployment to address the issue of authenticated certification and billing。
The core of the architecture is three points:
-
Export harmonization
-
Authentication prefix
-
Billing and release binding
V. Practical modalities for the implementation of the certification of real names in the light-in-house hotel
In this program, WiFi's actual name is no longer authenticated“Page Actions”But the conditions for export release:
-
Residents access the network, auto-jumping real name authentication
-
Export strategy is effective immediately after certification has been completed
-
Uncertified or invalid, direct offline
Flexible support for real name certification:
-
Text message authentication
-
Room number + mobile phone number authentication
-
Room number + identification of the back of the document
-
Foreign guest room number + the last few passports certified
All authenticated certification results are directly tied to export strategies.
VI. How the bill actually landed in the HOUSE
The bill is no longer a matter of export control.“Statistical Presentation”But it's real control:
-
- It's on the room.
-
Charges by account
-
Long-term charges on time
-
Cost per set.
The billing strategy can be linked to the authentication results:
-
Entry is effective.
-
Checking out is invalid.
-
Automatically cut off the network over time
-
AutoCustoms due
Avoid manual intervention and resolve the problem of miscalculation.
VII. How the physical name certification, billing and logs form closed rings
In the light-in-house hotel, the NATSHEL_BRAND programme has achieved three-fold unification:
-
Authentication of real name: confirmation“Who's using it?”
-
Costing system: confirmation“How long? How much?”
-
NATSHEL_LOG_AUDIT: Confirm“What did you do?”
All data are harmonized from export control points and have:
-
Time consistency
-
Consistency of conduct
-
Data traceability
This is the key to public security recognition.
VIII. WHY, IN THE PERSPECTIVE OF PUBLIC SECURITY, PROBLEMS OF THIS PROGRAMME ARE SO EXCESSABLE TO BE CHECKED
In practice, public security has more than accepted the following features:
-
Could not close temporary folder: %s
-
Billing and release as source
-
Logs can be pushed back to specific rooms and people
-
Clear network structure to illustrate
The light-in-house hotel, once under uniform export control, can provide a clear answer:
-
Who's using the net?
-
Which room is it?
-
How long did it take?
-
Where's the flow going?
This is...“Form programme”It's impossible.
IX. The real value of one step: avoiding re-engineering
The actual experience of the large number of light-in-house hotels is:
-
The first set of options can only display authentication pages
-
Second Log-plus Server
-
Third re-engineering export
Not only are costs high, but there is also a compliance risk.
Through one-off introduction Export-level real name certification and billing programme, avoid:
-
Re-input
-
Networks are down and out.
-
Public security checks are repeatedly named.
X. LINK IN HOUSE, ACTIVITY CERTAINING AND COSTS HAVE TO BE BASED FROM THE STRUCTURE
The Hotel of Light Intake is not incapable of authenticating and billing, but rather:
Must be done in the right place.
NATSHEL_BRAND, through deep collaboration with connectivity, has made the Hare House Hotel a reality without disrupting the three-net structures:
-
WiFi Real Name Authentication
-
Precision
-
Log Audit
-
Public security compliance
I really do. One deployment, long-term。