Web login method and system based on wireless authentication

Abstract

This invention provides a web login system and method based on wireless authentication, comprising: Step S1: Selecting the login option on the web login page, adding a wireless authentication login method; when wireless authentication is selected, the system checks whether a client has been bound before; Step S2: The page redirects to a guide page for downloading the APP and provides operation instructions to guide the user to successfully bind the client; Step S3: Logging into the web system on the PC, the login page provides a wireless authentication login option; clicking wireless authentication starts the authentication process; Step S4: When the PC and mobile APP receive a start verification signal sent by the wireless authentication server, they perform a comparison authentication; Step S5: A forced logout function button is provided through the mobile APP; after successful login and the mobile APP receives a login success message, the user can open the mobile APP and access all online user login-related information. This invention can solve the cumbersome problems of entering passwords and verification codes, as well as the security problems of web system login.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically, to a web login method and system based on wireless authentication. Background Technology

[0002] Wireless technology is a short-range wireless transmission technology. Due to its fast transmission speed and relatively long effective distance, it is widely used in offices and homes. After a wireless-enabled terminal connects to a wireless access point (AP), the AP authenticates the wireless terminal. Once authentication is successful, the wireless terminal is allowed to access the Internet.

[0003] The invention patent with publication number CN106850401A discloses a wireless authentication device, system, and authentication method, comprising: S1 The wireless authentication device receives an internet access request sent by a terminal and sends the URL address of a Portal page to the terminal based on the internet access request; S2 The Portal server pushes the Portal page to the terminal based on the page request sent by the terminal according to the URL address; S3 The wireless authentication device randomly generates an authentication code based on the email address entered by the user on the Portal page and sends it to the corresponding email address; S4 The wireless authentication device receives the verification authentication code obtained by the user from the email address and entered on the Portal page to realize the user's identity authentication.

[0004] The existing technology has the following problems: the method of users manually entering password verification codes is cumbersome and the user experience is poor; there are also problems with multiple web systems managing multiple passwords, which is cumbersome to remember and complicated to input; and the login security of web systems is low. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides a web login method and system based on wireless authentication.

[0006] According to the present invention, a web login method and system based on wireless authentication is provided, the solution of which is as follows:

[0007] Firstly, a web login method based on wireless authentication is provided, the method comprising:

[0008] Step S1: Select the login option on the web login page and add a wireless authentication login method. When wireless authentication is selected, the system checks whether a client has been bound.

[0009] If no client is bound, the logged-in user will be prompted to bind first, and the process will proceed to step S2; if the user has already successfully bound the client, the process will proceed to step S3.

[0010] Step S2: The page redirects to the app download guide page and provides operation instructions to guide the user to successfully bind the app;

[0011] Step S3: Log in to the web system on your PC. The login page offers a wireless authentication login option. Click on wireless authentication to start the authentication process.

[0012] Step S4: When the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, they will perform comparison authentication. If the authentication is successful, the web system page will log in successfully and redirect to the login success page. A login success message will be sent to the mobile APP. The mobile APP will receive the message and notify the user that the login was successful.

[0013] If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile APP respectively;

[0014] Step S5: Provide a forced logout function button through the mobile APP. After successful login and the mobile APP receives the login success message, the user can open the mobile APP and access all online user login-related information.

[0015] Preferably, step S2 includes:

[0016] Step S2.1: The user successfully downloaded the mobile app and installed it on their phone.

[0017] Step S2.2: Open the APP and prompt the user to log in to their account. If the user is not logged in, prompt them to log in. If the user does not have an account, prompt them to register an account. Then check whether the user has bound their account. If the user has bound their account, proceed to step S2.4. If the user has not bound their account, guide them to start the binding process.

[0018] Step S2.3: Both the mobile APP and the PC device host that needs to log in to the web enter the binding process. They broadcast via Bluetooth or other secure wireless protocols. The main control unit of the wireless device receives and records the broadcast. The mobile APP and the PC device page select the corresponding wireless device for authentication and binding.

[0019] Step S2.4: After successful authentication and binding, the mobile APP will have an additional binding item, and the web login page on the PC device will return to the wireless authentication login page with a button that can be clicked for wireless authentication login;

[0020] Step S2.5: If binding fails, proceed to step S2.3 to restart the binding process.

[0021] Preferably, step S3 specifically includes: when the web system is ready to log in on a PC device, the login page provides a wireless authentication login option. When the user clicks on wireless authentication, the web system sends a message to the background wireless authentication server to prepare for verification. After the server receives this message, the database records the relevant information, and the background wireless authentication server sends a signal to start verification to both the mobile APP user who has been authenticated with this web system and the web login page system, thus starting the authentication process.

[0022] Preferably, step S4 includes: when the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, both the PC device and the mobile phone start broadcasting and sending secure wireless signals. After the PC device and the mobile phone receive each other's wireless signals, they start comparing whether there is a device that has been bound in step S2.4.

[0023] If a PC device and a mobile device are matched, a verification success message is returned to the wireless authentication server. The wireless authentication server receives the message and compares it with the information in the database during the binding process in step S2.4. If the comparison is successful, the authentication is successful, the web system page login is also successful, and the user is redirected to the login success page. A login success message is also sent to the mobile APP. The mobile APP receives the message and notifies the user that the login is successful.

[0024] If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile app respectively.

[0025] Preferably, step S5 further includes: when the user clicks the forced offline button, the APP sends a forced offline message to the wireless authentication server, the wireless authentication server notifies the system's main authentication server, notifies the web to force offline, and notifies the wireless authentication server, and the wireless authentication server notifies the mobile APP and sends a successful exit message.

[0026] Secondly, a web login system based on wireless authentication is provided, the system comprising:

[0027] Module M1: Select the login option on the web login page and add a wireless authentication login method. When wireless authentication is selected, the system checks whether a client has been bound.

[0028] If no client is bound, the user will be prompted to bind it first and then redirected to module M2; if the user has already successfully bound the client, the user will be redirected to module M3.

[0029] Module M2: The page redirects to the app download guide page and provides operation instructions to guide the user to successfully bind the app;

[0030] Module M3: Log in to the web system on the PC device. The login page provides a wireless authentication login option. Click on wireless authentication to start the authentication process.

[0031] Module M4: When the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, they will perform comparison authentication. If the authentication is successful, the web system page will log in successfully and redirect to the login success page. A login success message will be sent to the mobile APP. The mobile APP will receive the message and notify the user that the login was successful.

[0032] If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile APP respectively;

[0033] Module M5: Provides a forced logout function button via the mobile app. After successful login and the mobile app receives a login success message, the user can open the mobile app and access all online user login-related information.

[0034] Preferably, the module M2 includes:

[0035] Module M2.1: The user has successfully downloaded the mobile app and installed it on their phone.

[0036] Module M2.2: Open the APP and prompt the user to log in to their account. If the user is not logged in, prompt them to log in. If the user does not have an account, prompt them to register an account. Then check whether the user has bound their account. If the user has bound their account, redirect to module M2.4. If the user has not bound their account, guide them to start the binding process.

[0037] Module M2.3: Both the mobile app and the PC device host that needs to log in to the web enter the binding process. A broadcast is sent via Bluetooth or other secure wireless protocols. The main control unit of the wireless device receives and records the broadcast. The mobile app and the PC device page select the corresponding wireless device for authentication and binding.

[0038] Module M2.4: After successful authentication and binding, the mobile APP will have an additional binding item, and the PC device's web login page will return to the wireless authentication login page with a button that can be clicked for wireless authentication login;

[0039] Module M2.5: If binding fails, it will redirect to module M2.3 to restart the binding process.

[0040] Preferably, module M3 specifically includes: when the web system is ready to log in on a PC device, the login page provides a wireless authentication login option. When the user clicks on wireless authentication, the web system sends a message to the background wireless authentication server to prepare for verification. After the server receives this message, the database records the relevant information, and the background wireless authentication server sends a signal to start verification to both the mobile APP user who has been authenticated with this web system and the web login page system, thus initiating the authentication process.

[0041] Preferably, module M4 includes: when the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, both the PC device and the mobile phone start broadcasting and sending secure wireless signals. After the PC device and the mobile phone receive each other's wireless signals, they start comparing whether there are any devices that have been bound in module M2.4.

[0042] If a PC device and a mobile device are matched, a successful verification message is returned to the wireless authentication server. The wireless authentication server receives the message and compares it with the information when the module M2.4 was bound in the database. If the comparison is successful, the authentication is successful, the web system page login is also successful and the user is redirected to the login success page. A login success message is also sent to the mobile APP. The mobile APP receives the message and notifies the user that the login is successful.

[0043] If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile app respectively.

[0044] Preferably, module M5 further includes: when the user clicks the forced offline button, the APP sends a forced offline message to the wireless authentication server, the wireless authentication server notifies the system's main authentication server, notifies the web to force offline, and notifies the wireless authentication server, and the wireless authentication server notifies the mobile APP and sends a successful exit message.

[0045] Compared with the prior art, the present invention has the following beneficial effects:

[0046] 1. This invention uses a C / S architecture and a web system for wireless login authentication, solving the cumbersome problems of entering passwords and verification codes;

[0047] 2. In this invention, the web system login authentication and the mobile APP are not in a one-to-one relationship, but rather an n-to-1 relationship. The mobile APP can manage and perform corresponding management of multiple web system wireless authentications for a user. One APP manages and authenticates multiple web login authentications, solving the problems of managing multiple passwords for multiple web systems, the cumbersome process of remembering passwords, and the complexity of inputting passwords.

[0048] 3. This invention manages wireless authentication through a secure wireless protocol and a dedicated wireless authentication server, thus solving the problem of web system login security. Attached Figure Description

[0049] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0050] Figure 1 This is a schematic diagram of the overall process of the present invention. Detailed Implementation

[0051] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the scope of protection of the present invention.

[0052] This invention provides a web login method based on wireless authentication, referring to... Figure 1 As shown, the method specifically includes the following steps:

[0053] Step S1: Open the web login page. Users can select login options and add the wireless authentication login method of this invention. When wireless authentication is selected, the system checks whether a client (an app installed on the mobile phone) has been bound. If no client is bound, the user is prompted to bind it first, and the process proceeds to step S2. If the user has already successfully bound the client, the process proceeds to step S3.

[0054] Step S2: The page redirects to the app download guide page and provides operation instructions to guide the user to successfully bind the app.

[0055] Specifically, step S2.1: The user successfully downloads the mobile app and installs it on the phone.

[0056] Step S2.2: After the user opens the APP, prompt the user to log in to their account. If the user is not logged in, prompt them to log in. If the user does not have an account, prompt them to register an account. Then check whether the user has bound their account. If the user has bound their account, proceed to step S2.4. If the user has not bound their account, guide them to start the binding process.

[0057] Step S2.3: Both the mobile app and the PC host device that needs to log in to the web interface enter the binding process (both the mobile phone and the PC host device need to support wireless communication protocols). A broadcast is sent via Bluetooth or other secure wireless protocols. The main control unit of the wireless device receives and records the broadcast. The mobile app and PC device pages select the corresponding wireless device for authentication and binding. Binding requires entering the web system login password and recording relevant detailed information in the database (including: date, PC device model, PC device system software version, PC device account information, mobile device model, mobile device system version, mobile app user information, mobile app software version, and whether binding was successful).

[0058] Step S2.4: After successful authentication and binding, the mobile APP will have an additional binding item, and the PC device's web login page will return to the wireless authentication login page with a button that can be clicked for wireless authentication login.

[0059] Step S2.5: If binding fails, proceed to step S2.3 to restart the binding process.

[0060] Step S3: When the web system is ready to log in on the PC, the login page provides a wireless authentication login option. When the user clicks on wireless authentication, the web system will send a message to the backend wireless authentication server to prepare for verification. After the server receives this message, the database records the relevant information, and the backend wireless authentication server will simultaneously send a signal to start verification to the mobile APP user who has been bound and authenticated to this web system and the web login page system, thus starting the authentication process.

[0061] Step S4: When the PC device and mobile app receive the start verification signal from the wireless authentication server, both the PC device and the mobile app begin broadcasting secure wireless signals. After receiving each other's wireless signals, the PC device and mobile app compare whether there is a device that was bound in step S2.4. If a match is found, the PC device and mobile app respectively return a verification success message to the wireless authentication server. The wireless authentication server receives the message and compares it with the information in the database from when the device was bound in step S2.4. If the comparison is successful, authentication is successful, the web system page login is successful, and the user is redirected to the login success page. A login success message is also sent to the mobile app, which receives the message and notifies the user that login was successful. If the comparison fails, the corresponding error message is returned to the web page on the PC device and the mobile app respectively.

[0062] Step S5: The mobile app provides a forced logout button. After successful login and the app receiving a login success message, the user can open the mobile app and view all login-related information. When the user clicks the forced logout button, the app sends a forced logout message to the wireless authentication server. The wireless authentication server notifies the system's main authentication server, instructs the web server to force logout, and also notifies the wireless authentication server. The wireless authentication server then notifies the mobile app and sends a logout success message.

[0063] This invention also provides a web login system based on wireless authentication, the system specifically comprising:

[0064] Module M1: Select the login option on the web login page and add wireless authentication login method. When wireless authentication is selected, the system checks whether a client has been bound. If no client is bound, the login user is prompted to bind it first and is redirected to module M2. If the user has already successfully bound the client, the system redirects to module M3.

[0065] Module M2: The page redirects to the app download guide page and provides operation instructions to guide the user to successfully bind the app.

[0066] Module M3: Log in to the web system on your PC. The login page offers a wireless authentication login option. Click on wireless authentication to begin the authentication process.

[0067] Module M4: When the PC device and mobile APP receive the start verification signal sent by the wireless authentication server, they will perform a comparison authentication. If the authentication is successful, the web system page will log in successfully and redirect to the login success page, and send a login success message to the mobile APP. The mobile APP will receive the message and notify the user that the login was successful. If the comparison fails, the corresponding error information will be returned to the web page of the PC device and the mobile APP respectively.

[0068] Module M5: Provides a forced logout button via the mobile app. After successful login and the mobile app receiving a login success message, the user can open the app and view all online user login-related information. When the user clicks the forced logout button, the app sends a forced logout message to the wireless authentication server. The wireless authentication server notifies the system's main authentication server, instructs the web server to force logout, and also notifies the wireless authentication server. The wireless authentication server then notifies the mobile app and sends a logout success message.

[0069] In module M2, the module specifically includes:

[0070] Module M2.1: The user has successfully downloaded the mobile app and installed it on their phone.

[0071] Module M2.2: Open the APP and prompt the user to log in to their account. If the user is not logged in, prompt them to log in. If the user does not have an account, prompt them to register an account. Then check whether the user has bound their account. If the user has bound their account, redirect to module M2.4. If the user has not bound their account, guide them to start the binding process.

[0072] Module M2.3: Both the mobile app and the PC host device requiring web login enter the binding process (both the mobile phone and the PC host need to support wireless communication protocols). A broadcast is sent via Bluetooth or other secure wireless protocols. The main control unit of the wireless device receives and records the broadcast. The mobile app and PC device pages select the corresponding wireless device for authentication and binding. Binding requires entering the web system login password and recording relevant detailed information in the database (including: date, PC device model, PC device system software version, PC device account information, mobile device model, mobile system version, mobile app user information, mobile app software version, and whether binding was successful).

[0073] Module M2.4: After successful authentication and binding, the mobile APP will have an additional binding item, and the PC device's web login page will return to the wireless authentication login page with a button that can be clicked for wireless authentication login;

[0074] Module M2.5: If binding fails, it will redirect to module M2.3 to restart the binding process.

[0075] Module M3 specifically includes: When the web system is ready to log in on a PC device, the login page provides a wireless authentication login option. When the user clicks on wireless authentication, the web system sends a message to the backend wireless authentication server to prepare for verification. After the server receives this message, the database records the relevant information, and the backend wireless authentication server simultaneously sends a signal to start verification to the mobile APP user who has been bound and authenticated to this web system and the web login page system, thus initiating the authentication process.

[0076] Module M4 includes: When the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, both the PC device and the mobile phone start broadcasting and sending secure wireless signals. After the PC device and the mobile phone receive each other's wireless signals, they start comparing whether there are any devices that have been bound in module M2.4.

[0077] If a match is found between a PC device and a mobile device, a successful verification message is returned to the wireless authentication server. The wireless authentication server receives the message and compares it with the information in the database when the module M2.4 was bound. If the comparison is successful, authentication is successful, the web system page login is successful, and the user is redirected to the login success page. A login success message is also sent to the mobile app, which receives the message and notifies the user that the login was successful. If the comparison fails, the corresponding error message is returned to the web page on the PC device and the mobile app respectively.

[0078] This invention provides a web login method and system based on wireless authentication, comprising a web interface and a client interface. During authentication login on the web system, web authentication login is achieved through wireless interaction with a pre-bound client (if not bound, a binding prompt is given; once bound, no further action is required, and there is no disturbance). It mainly includes a client-side wireless authentication management APP, a web page wireless authentication login system, and a backend wireless authentication server; it solves the problems of managing multiple passwords across multiple web systems, the cumbersome process of remembering multiple passwords, and the complex input required. It also addresses the security issues of web system login.

[0079] Those skilled in the art will understand that, besides implementing the system and its various devices, modules, and units provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices, modules, and units of this invention function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices, modules, and units provided by this invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices, modules, and units for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0080] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A web login method based on wireless authentication, characterized in that, include: Step S1: Select the login option on the web login page and add a wireless authentication login method. When wireless authentication is selected, the system checks whether a client has been bound. If no client is bound, the logged-in user will be prompted to bind first, and the process will proceed to step S2; if the user has already successfully bound the client, the process will proceed to step S3. Step S2: The page redirects to the app download guide page and provides operation instructions to guide the user to successfully bind the app; Step S3: Log in to the web system on your PC. The login page offers a wireless authentication login option. Click on wireless authentication to start the authentication process. Step S4: When the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, they will perform a comparison authentication. If the PC device and the mobile device match, they will return a verification success message to the wireless authentication server. The wireless authentication server receives the message and compares it with the information bound in step S2 in the database. If the comparison is successful, the authentication is successful. The web system page logs in successfully and redirects to the login success page. A login success message is sent to the mobile APP. The mobile APP receives the message and notifies the user that the login is successful. If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile APP respectively; Step S5: Provide a forced logout function button through the mobile APP. After successful login and the mobile APP receives the login success message, the user can open the mobile APP and the online user can access all relevant information. The step S2 comprises: Step S2.1: The user successfully downloaded the mobile app and installed it on their phone. Step S2.2: Open the APP and prompt the user to log in to their account. If the user is not logged in, prompt them to log in. If the user does not have an account, prompt them to register an account. Then check whether the user has bound their account. If the user has bound their account, proceed to step S2.

4. If the user has not bound their account, guide them to start the binding process. Step S2.3: Both the mobile APP and the PC device host that needs to log in to the web enter the binding process. They broadcast via the wireless protocol. The main control unit of the wireless device receives and records the broadcast. The mobile APP and the PC device page select the corresponding wireless device for authentication and binding. Step S2.4: After successful authentication and binding, the mobile APP will have an additional binding item, and the web login page on the PC device will return to the wireless authentication login page with a button that can be clicked for wireless authentication login; Step S2.5: If binding fails, proceed to step S2.3 to restart the binding process.

2. The web login method based on wireless authentication according to claim 1, characterized in that, Step S3 specifically includes: when the web system is ready to log in on a PC device, the login page provides a wireless authentication login option. When the user clicks on wireless authentication, the web system sends a message to the backend wireless authentication server to prepare for verification. After the server receives this message, the database records the relevant information, and the backend wireless authentication server sends a signal to start verification to both the mobile APP user who has been authenticated with this web system and the web login page system, thus starting the authentication process.

3. The web login method based on wireless authentication according to claim 1, characterized in that, Step S4 includes: when the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, both the PC device and the mobile phone start broadcasting and sending secure wireless signals. After the PC device and the mobile phone receive each other's wireless signals, they start comparing whether there is a device that has been bound in step S2.

4. If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile app respectively.

4. The web login method based on wireless authentication according to claim 1, characterized in that, Step S5 further includes: when the user clicks the forced offline button, the APP sends a forced offline message to the wireless authentication server, the wireless authentication server notifies the system's main authentication server, notifies the web to force offline, and notifies the wireless authentication server, the wireless authentication server notifies the mobile APP and sends a successful exit message.

5. A web login system based on wireless authentication, characterized in that, include: Module M1: Select the login option on the web login page and add a wireless authentication login method. When wireless authentication is selected, the system checks whether a client has been bound. If no client is bound, the logged-in user will be prompted to bind it first, and then redirected to module M2; If the user has already successfully bound their account, the system will redirect to module M3. Module M2: The page redirects to the app download guide page and provides operation instructions to guide the user to successfully bind the app; Module M3: Log in to the web system on the PC device. The login page provides a wireless authentication login option. Click on wireless authentication to start the authentication process. Module M4: When the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, they will perform a comparison authentication. If the PC device and the mobile device match, they will return a verification success message to the wireless authentication server. The wireless authentication server receives the message and compares it with the information when module M2 was bound in the database. If the comparison is successful, the authentication is successful. The web system page logs in successfully and redirects to the login success page. A login success message is sent to the mobile APP. The mobile APP receives the message and notifies the user that the login is successful. If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile APP respectively; Module M5: Provides a forced logout function button via the mobile APP. After successful login and the mobile APP receives a login success message, the user can open the mobile APP and access all relevant information. The module M2 includes: Module M2.1: The user has successfully downloaded the mobile app and installed it on their phone. Module M2.2: Open the APP and prompt the user to log in to their account. If the user is not logged in, prompt them to log in. If the user does not have an account, prompt them to register an account. Then check whether the user has bound their account. If the user has bound their account, redirect to module M2.

4. If the user has not bound their account, guide them to start the binding process. Module M2.3: Both the mobile app and the PC device host that needs to log in to the web enter the binding process. A broadcast is sent through the wireless protocol. The main control unit of the wireless device receives and records the broadcast. The mobile app and the PC device page select the corresponding wireless device for authentication and binding. Module M2.4: After successful authentication and binding, the mobile APP will have an additional binding item, and the PC device's web login page will return to the wireless authentication login page with a button that can be clicked for wireless authentication login; Module M2.5: If binding fails, it will redirect to module M2.3 to restart the binding process.

6. The web login system based on wireless authentication according to claim 5, characterized in that, The module M3 specifically includes: when the web system is ready to log in on a PC device, the login page provides a wireless authentication login option. When the user clicks on wireless authentication, the web system sends a message to the backend wireless authentication server to prepare for verification. After the server receives this message, the database records the relevant information, and the backend wireless authentication server simultaneously sends a signal to start verification to the mobile APP user who has been bound and authenticated to this web system and the web login page system, thus starting the authentication process.

7. The web login system based on wireless authentication according to claim 5, characterized in that, The module M4 includes: when the PC device and the mobile APP receive the start verification signal sent by the wireless authentication server, both the PC device and the mobile phone start broadcasting and sending secure wireless signals. After the PC device and the mobile phone receive each other's wireless signals, they start comparing whether there are any devices that have been bound in module M2.

4. If the comparison fails, the corresponding error message will be returned to the web page on the PC device and the mobile app respectively.

8. The web login system based on wireless authentication according to claim 5, characterized in that, The module M5 further includes: when the user clicks the forced offline button, the APP sends a forced offline message to the wireless authentication server, the wireless authentication server notifies the system's main authentication server, notifies the web to force offline, and notifies the wireless authentication server, the wireless authentication server notifies the mobile APP and sends a successful exit message.

Images