Multi-channel Real-name Authentication: Engineering Details for SMS, ID Document, WeChat & Passport Verification

Since the enforcement of Ministry of Public Security Order No.176, venue real-name authentication has shifted from “basic availability” to “full channel coverage”. Inspectors no longer only check whether a Portal login page pops up; they will input a mobile number on-site and require a complete record of the user’s full online activity history.

If only SMS authentication is enabled, foreign visitors without Chinese mobile numbers cannot pass verification, and elderly guests without WeChat will be locked out. Missing authentication channels will directly create gaps in authentication records.

It is easy to add multiple login buttons on a Portal page. The real engineering difficulty lies in ensuring every channel remains stable under extreme network conditions.
AINOPOL Dream Series Secure Optical Gateways come with built-in Portal authentication, supporting more than 10 real-name methods including SMS verification, WeChat login, and ID document scanning智慧光迅A.... Below we break down implementation points and common pitfalls for the four core channels.

1. SMS Channel: Delivery Rate Is the Top Priority

This is the primary authentication channel for domestic venues. Three key engineering rules:

1. Deploy dual SMS gateway vendors with automatic failover if one provider goes offline.
2. Restrict verification code validity period and maximum retry attempts to prevent brute-force attacks.
3. Support international SMS roaming for overseas visitors; otherwise foreign guests will fail at the first step.
4. Differentiate error prompts clearly: display “network failure” instead of vague text when SMS delivery fails, to reduce customer complaints.

2. ID Document Channel: Mandatory for Foreign-related Venues

Passport and Mainland Travel Permit verification is a compliance must for hotels receiving overseas guests.

• Adopt OCR scanning + manual secondary validation: check ID number digit length and expiry date format; pure OCR recognition leads to high error rates.
• Strictly protect personal data: encrypt all stored ID information, and strictly control data retention periods in line with privacy regulations. ID data is more sensitive than internet access logs under personal information protection laws.

3. WeChat Channel: Smooth Experience with Automatic Fallback

WeChat one-click authentication reuses the real-name data bound to user WeChat accounts, delivering the best user experience and high success rate. Two major pitfalls must be avoided:

1. The service relies on third-party WeChat open APIs. Set automatic fallback to SMS verification when the WeChat interface fluctuates.
2. Keep the ID document entry clearly visible on the page to accommodate minors and elderly travelers without WeChat accounts.

4. Channel Collaboration: Unified Session & Centralized Archiving

All authentication channels must converge into one unified authentication session, recording account ID (mobile number or ID number), timestamp, channel type and bound terminal MAC address.
Log association relies solely on the Session ID instead of the login channel. This prevents identity drift caused by switching authentication methods, reconnection after Wi-Fi dropouts, or cross-day online access.

Two Deployment Models

Self-built Networks

The multi-channel capability runs on the Dream Gateway under AINOPOL’s Integrated Access & Security Solution. The Portal module is preconfigured with four channels (SMS, ID document, WeChat quick login, passport & Mainland Travel Permit), with automatic channel fallback. Authentication sessions and access logs are stored in the same database for direct correlation.

Carrier-managed Networks

Multi-channel authentication is undertaken by the Cloud Portal plug-in deployed on ONTs. The same channel policies and fallback rules apply; the only difference is that the authentication service runs on the optical modem instead of the on-site gateway.

Acceptance Tip for System Integrators: Add combined test scenarios: four authentication channels + network interruption recovery + high-concurrency guest check-in. Most authentication bugs only emerge under cross-scenario stress testing.

FAQ

Q1: Which authentication channels are required for hotel Wi-Fi real-name compliance?
A1: At minimum, SMS verification and ID document scanning. Foreign-related hotels must support passports and Mainland Travel Permits for Hong Kong, Macao and Taiwan residents. WeChat one-click login improves user experience, but ID document authentication must remain as a fallback option.

Q2: How should passport data be stored and protected?
A2: ID information counts as sensitive personal data. It must be stored with strong encryption, access permissions strictly limited, and retention periods strictly matched to business purposes to comply with personal information protection laws.

Q3: How to avoid user identity drift across different authentication channels?
A3: Unify all login results into a single authentication session. Logs are correlated only by Session ID, so switching channels or reconnecting Wi-Fi will not create new user identities.