Equipment certification methods, apparatus, equipment and storage media

By scanning the QR code of the device to be authenticated with an authenticated device and combining it with server verification, the problem of easily compromised account passwords is solved, enabling more complex and secure device authentication and improving the effectiveness of authentication.

CN116226830BActive Publication Date: 2026-11-17INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310293531.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-03-23
Publication Date
2026-11-17
Estimated Expiration
2043-03-23

AI Technical Summary

Technical Problem

In existing technologies, the method of verifying electronic devices by directly entering account passwords is highly susceptible to password compromise, resulting in low effectiveness of security authentication for electronic devices.

Method used

By scanning the device QR code of the device to be authenticated with an authenticated device, the server verifies the scan result and confirms that the device to be authenticated is a trusted device when the verification is successful. This establishes the binding information between the first user's envoy identity and the trusted device, thus achieving dual authentication.

Benefits of technology

This improves the security and effectiveness of certification for devices under certification, avoids invalid certifications, and increases the complexity of device certification.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116226830B_ABST
    Figure CN116226830B_ABST
Patent Text Reader

Abstract

This application provides a device authentication method, apparatus, device, and storage medium, applicable to information security, the Internet of Things (IoT), and other technical fields, or to fintech or other related fields. It includes: responding to a request to add an envoy from a device to be authenticated; obtaining device information of the device to be authenticated, the envoy addition request including a first user requesting to add an envoy identity; generating a device QR code based on the device information of the device to be authenticated; controlling the device to be authenticated to display the device QR code; receiving scanning information sent by an authenticated device; if the scanning information is successfully verified, receiving device authorization information sent by the authenticated device; and based on the device authorization information, determining that the device to be authenticated is a trusted device and that the first user possesses an envoy identity, thereby generating binding information between the first user's envoy identity and the trusted device. The method of this application can achieve scanning verification of the device to be authenticated through an authenticated device, improving the authentication security of the device to be authenticated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the technical fields of information security and the Internet of Things, and in particular to a device authentication method, apparatus, device and storage medium. Background Technology

[0002] Currently, electronic devices can install applications such as mobile banking and order transaction software, thus providing corresponding financial transactions for the primary user. To ensure transaction security, the electronic device executing the transaction generally needs to undergo security authentication. A common authentication method for electronic devices is that the application on the device allows the primary user to enter their account password; after successful verification of the primary user's account password, the electronic device is confirmed to be secure.

[0003] However, relying on directly entering account passwords to verify electronic devices makes it highly susceptible to password compromise, resulting in low security and ineffective security authentication for electronic devices. Summary of the Invention

[0004] This application provides a device authentication method, apparatus, device, and storage medium to address the problem of low effectiveness of security authentication for electronic devices.

[0005] In a first aspect, this application provides a device authentication method applied to a server, wherein the server connects a device to be authenticated and an authenticated device, and the method includes:

[0006] In response to a messenger addition request sent by the device to be authenticated, obtain the device information of the device to be authenticated. The messenger addition request includes the first user who requests to add messenger identity.

[0007] Generate a device QR code based on the device information of the device to be certified;

[0008] The device to be certified displays the device's QR code, which is then scanned by the certified device to obtain the corresponding scanning information.

[0009] Receive scan information sent by certified devices;

[0010] If the scan information verification is successful, the device authorization information sent by the authenticated device will be received.

[0011] Based on the device authorization information, the device to be authenticated is determined to be a trusted device, and the first user is determined to have the identity of an envoy, so as to generate the binding information between the first user's envoy identity and the trusted device.

[0012] Secondly, this application provides a device authentication method applied to a device to be authenticated, the method comprising:

[0013] The system detects that the first user performs a triggering operation on the "Add Messenger" notification page, generating a "Add Messenger" request.

[0014] Send a messenger add request to the server, which instructs the server to initiate a device information read request;

[0015] In response to a device information read request sent by the server, the device information is sent to the server, and the device information instructs the server to generate a device QR code;

[0016] Receive and display the device QR code fed back by the server. The device QR code indicates that the authenticated device can be scanned and verified, and the device can be authorized.

[0017] The server receives feedback confirming that the device to be authenticated is a trusted device, along with the first user's envoy identity and the binding information of the trusted device.

[0018] Thirdly, this application provides a device authentication method applied to authenticated devices, the method comprising:

[0019] In response to a scanning request initiated by a second user, the device QR code displayed by the device to be authenticated is scanned to obtain scanning information. The device QR code is generated by the server based on the device information of the device to be authenticated. The device information is obtained by the server from the device to be authenticated when it receives a request to add an envoy initiated by the device to be authenticated.

[0020] The system sends scan information to the server, which instructs the server to perform a scan verification. Upon successful verification, the system displays the device authorization page.

[0021] Display the device authorization page, which includes authorization prompts for the device to be authenticated. These prompts are used to remind the second user to authorize the device to be authenticated.

[0022] In response to the second user's confirmation operation on the authorization prompt information, device authorization information is sent to the server. The device authorization information instructs the server to determine whether the device to be authenticated is a trusted device and the binding information between the first user's messenger identity and the trusted device.

[0023] Fourthly, this application provides a device authentication apparatus located on a server, the server connecting a device to be authenticated and an already authenticated device, the apparatus comprising:

[0024] The first response unit is used to respond to the envoy addition request sent by the device to be authenticated, and to obtain the device information of the device to be authenticated. The envoy addition request includes the first user who requests to add envoy identity.

[0025] The first generation unit is used to generate a device QR code based on the device information of the device to be certified;

[0026] The first display unit is used to control the device to be authenticated to display the device QR code. The device QR code is scanned by the authenticated device to obtain the corresponding scanning information.

[0027] The first receiving unit is used to receive scanning information sent by the authenticated device;

[0028] The second receiving unit is used to receive device authorization information sent by the authenticated device if the scanning information verification is successful.

[0029] The device authorization unit is used to determine, based on the device authorization information, whether the device to be authenticated is a trusted device and whether the first user has an envoy identity, so as to generate binding information between the first user's envoy identity and the trusted device.

[0030] Fifthly, this application provides a device authentication apparatus located on the device to be authenticated, the apparatus comprising:

[0031] The first detection unit is used to detect when the first user performs a trigger operation on the prompt page for adding a messenger and to generate a request to add a messenger.

[0032] The first sending unit is used to send a messenger addition request to the server, which instructs the server to initiate a device information reading request.

[0033] The second response unit is used to respond to the device information read request sent by the server, send device information to the server, and instruct the server to generate a device QR code.

[0034] The third receiving unit is used to receive and display the device QR code fed back by the server. The device QR code indicates that the authenticated device should be scanned and verified, and the device should be authorized.

[0035] The fourth receiving unit is used to receive the authentication information from the server, which confirms that the device to be authenticated is a trusted device, as well as the binding information between the first user's envoy identity and the trusted device.

[0036] Sixthly, this application provides a device authentication apparatus located on an authenticated device, the apparatus comprising:

[0037] The third response unit is used to respond to the scanning request initiated by the second user, scan the device QR code displayed by the device to be authenticated, and obtain the scanning information. The device QR code is generated by the server based on the device information of the device to be authenticated. The device information is obtained by the server from the device to be authenticated when it receives the envoy addition request initiated by the device to be authenticated.

[0038] The second sending unit is used to send scanning information to the server. The scanning information instructs the server to perform scanning verification and displays the device authorization page when the verification is successful.

[0039] The second display unit is used to display the device authorization page, which includes authorization prompt information for the device to be authenticated. The authorization prompt information is used to prompt the second user to authorize the device to be authenticated.

[0040] The third response unit is used to respond to the confirmation operation performed by the second user on the authorization prompt information, and send device authorization information to the server. The device authorization information instructs the server to determine that the device to be authenticated is a trusted device and the binding information between the first user's messenger identity and the trusted device.

[0041] In a seventh aspect, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0042] The memory stores instructions that the computer executes;

[0043] The processor executes computer-executable instructions stored in memory to implement the method of any one of the first, second, or third aspects.

[0044] Eighthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method of any one of the first, second, or third aspects.

[0045] The technical solution provided in this application allows a server to obtain device information from a request to add an envoy to a device to be authenticated. This envoy addition request can include a first user requesting to add an envoy identity. The server can also generate a device QR code, which can be displayed for scanning by already authenticated devices. The authenticated device can be a secure device. Receiving the scan information sent by the authenticated device allows for information verification. Successful verification instructs the device to initiate authentication and receive device authorization information from the authenticated device. Based on the device authorization information, the device to be authenticated can be determined as a trusted device, and an envoy identity can be set for the first user. Binding the first user's envoy identity to the trusted device enables device authentication. Combining scanning and verification methods allows for more complex authentication of the device to be authenticated, improving the authentication security of the device. Attached Figure Description

[0046] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0047] Figure 1 A schematic diagram of a communication system architecture for implementing a device authentication method is provided in an embodiment of this application;

[0048] Figure 2 A flowchart illustrating one embodiment of a device authentication method provided in this application;

[0049] Figure 3 A signaling diagram for a device authentication method provided in an embodiment of this application;

[0050] Figure 4 Another signaling diagram for a device authentication method provided in an embodiment of this application;

[0051] Figure 5 An example diagram of a device binding prompt page provided for an embodiment of this application;

[0052] Figure 6 An example diagram of a display device licensing page provided for an embodiment of this application;

[0053] Figure 7 Another signaling diagram for a device authentication method provided in an embodiment of this application;

[0054] Figure 8 A flowchart illustrating yet another embodiment of a device authentication method provided in this application;

[0055] Figure 9 A flowchart illustrating yet another embodiment of a device authentication method provided in this application;

[0056] Figure 10 A schematic diagram of one embodiment of a device authentication apparatus provided in this application;

[0057] Figure 11 A schematic diagram of another embodiment of a device authentication apparatus provided in this application;

[0058] Figure 12 A schematic diagram of another embodiment of a device authentication apparatus provided in this application;

[0059] Figure 13 This is a block diagram of a terminal device for implementing a device authentication method, provided as an embodiment of this application.

[0060] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0061] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0062] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0063] The device authentication method, apparatus, equipment, and medium provided in this application can be applied to technical fields such as information security and the Internet of Things, as well as fintech or other related fields. By using an already authenticated device to scan the QR code of the device to be authenticated, and then verifying the scanned QR code information through a server, the device to be authenticated is determined to be a trusted device if the verification is successful. This method, using an already authenticated device, enables the scanning and verification of the device to be authenticated, thereby improving the authentication security of the device.

[0064] In related technologies, to ensure transaction security, it is generally necessary to authenticate the electronic devices executing the transactions. A common authentication method for electronic devices is that the device's application allows the first user to enter their account password. Once the first user's account password is successfully verified, the electronic device is considered secure. However, relying on directly entering an account password to verify an electronic device makes the password vulnerable to compromise, thus directly managing accounts on electronic devices is not very secure, resulting in low effectiveness of electronic device security authentication.

[0065] The device certification method provided in this application aims to solve the above-mentioned technical problems of the prior art.

[0066] This application embodiment adds an authenticated device, which can specifically be a device in a bank branch or a bank-approved security device. The device to be authenticated can be any device. The device to be authenticated can display a QR code. The authenticated device can scan the QR code of the device to be authenticated and send the scan result back to the server. The server verifies the scan result, and if the verification is successful, confirms the device to be authenticated as a trusted device. When the first user of the device to be authenticated requests to add an envoy, the server assigns an envoy identity to the first user. A binding information is established between the first user's envoy identity and the trusted device. By having the authenticated device scan and authenticate the device to be authenticated, dual authentication—scanning and verification—can be achieved, increasing the authentication complexity of the device to be authenticated, thereby improving the authentication security of the device to be authenticated, promoting the effectiveness of device authentication, and avoiding invalid authentication.

[0067] The equipment certification method provided in this application is applicable to... Figure 1 The diagram shows a schematic of the communication system architecture. Figure 1 As shown, the communication system may include: a server 11, a device to be authenticated 12 connected to the server 11, and an authenticated device 13 connected to the server 11. Both the device to be authenticated 12 and the authenticated device 13 can be terminal devices. In practical applications, the number of devices to be authenticated and the number of authenticated devices can be configured according to usage requirements; this embodiment does not impose excessive limitations.

[0068] The device to be authenticated, 12, can initiate a envoy addition request under the operation of the first user and send the envoy addition request to the server, 11. For example, the envoy addition prompt page can display a prompt message "Do you want to be added as an envoy?" and a "confirm" control associated with the prompt message. When the first user clicks the confirmation control, the envoy addition request can be sent to the server, 11.

[0069] Server 11 can obtain device information of device 12 to be authenticated based on the device authentication method of this application, and generate a device QR code. The device QR code can be displayed by device 12 to be authenticated.

[0070] The authenticated device 13 can scan the device QR code displayed on the device to be authenticated 12 to obtain the scan information. The scan information can then be sent back to the server 11 by the authenticated device 13.

[0071] Server 11 can perform verification based on the scan information returned by the authenticated device 13. If the verification is successful, it can notify the authenticated device 13 to authorize the device, and then receive the device authorization information sent by the authenticated device 13. Based on the device authorization information, it determines that the device to be authenticated is a trusted device and that the first user has the identity of an envoy, so as to generate the binding information between the first user's envoy identity and the trusted device.

[0072] It should be noted that, Figure 1 The communication system shown can be applied to different network standards, such as Global System for Mobile communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE) systems, and future 5G network standards. Optionally, the above communication system can be used in scenarios involving Ultra-Reliable and Low Latency Communications (URLLC) transmission within 5G communication systems.

[0073] Therefore, optionally, the aforementioned base station can be a base station (BTS) and / or base station controller in GSM or CDMA, a base station (NodeB, NB) and / or radio network controller (RNC) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a base station (gNB) in future 5G networks, etc., which are not limited herein.

[0074] The aforementioned terminal equipment can be either a wireless terminal or a wired terminal. A wireless terminal can be a device that provides voice and / or other service data connectivity to a first user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The wireless terminal can communicate with one or more core network devices via a Radio Access Network (RAN). The wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) or a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device, which exchanges voice and / or data with the RAN. Furthermore, a wireless terminal can also be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or other similar devices. A wireless terminal can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, access terminal, user terminal, user agent, user device, or user equipment, without limitation. Optionally, the aforementioned terminal devices can also be smartwatches, tablets, or other similar devices.

[0075] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0076] like Figure 2 The diagram shown is a flowchart of one embodiment of a device authentication method provided in this application. This method can be configured as a device authentication device, which can be located in a server. The server can connect to both the device to be authenticated and the already authenticated device. The device authentication method may include:

[0077] S201: In response to a messenger addition request sent by the device to be authenticated, obtain the device information of the device to be authenticated. The messenger addition request includes the first user who requests to add messenger identity.

[0078] Optionally, the envoy can be a user identity corresponding to the application service provided when the device to be authenticated is successfully authenticated. The envoy addition request can include a first user, specifically including the first user's user information, which may include user identity, identifier, name, account information, order transaction information, facial image, etc. The device information of the device to be authenticated can include at least one of the following: device identifier, device model, device name, etc. Different devices can be distinguished through this device information. The device to be authenticated can include a device that provides envoy functionality to the user, specifically a device capable of performing transaction processing based on the trader's account information.

[0079] S202: Generate a device QR code based on the device information of the device to be certified.

[0080] Step 202 may include: generating a device QR code based on the device information of the device to be authenticated and a QR code generation function. The device information can be directly input into the QR code generation function to obtain the device QR code. Alternatively, the device information can be optimized or converted according to the format requirements of the QR code generation function to obtain processed device information, which is then input into the QR code generation function to obtain the device QR code. Step 202: Alternatively, the device information of the device to be authenticated can be encrypted to obtain encrypted device information, and a device QR code can be generated based on the encrypted device information.

[0081] For example, in step 202, the string corresponding to the device information of the device to be authenticated can be determined, and a device QR code can be generated based on the string. The device information of the device to be authenticated can be directly concatenated into a string, or the device information can be converted into a string according to a certain information expression format.

[0082] For example, the data format of a QR code may include the QR code type and device information of the device to be authenticated. Information such as QR code generation time, encrypted identifier of device information, and relative path of the authorization page URL (Uniform Resource Locator) is included. For example, in the T+P type, ... <t>It's a broad category. It's a subcategory. The authorization page can refer to the confirmation page displayed when the QR code of the device to be authenticated is generated and confirmed.

[0083] S203: Control the device to be certified to display the device QR code, which is then scanned by the certified device to obtain the corresponding scanning information.

[0084] Optionally, step 203 may specifically include: sending the device QR code to the device to be authenticated. The device QR code may be displayed by the device to be authenticated. The device to be authenticated may receive the device QR code sent by the server and display the device QR code.

[0085] Certified devices can be secure electronic devices certified by financial institutions, such as internal equipment distributed in bank branches. Certified devices offer higher security. By scanning the device to be certified with a certified device, it is possible to use certified security equipment to scan and authenticate uncertified electronic devices, thereby improving the effectiveness of authentication.

[0086] A certified device can scan the device QR code displayed on the device to be certified to obtain the scanning information.

[0087] S204: Receive scan information sent by an authenticated device.

[0088] The scan information can be the scan result of the device QR code displayed by the authenticated device to the device to be authenticated, and can specifically be the string obtained from the scan.

[0089] Optionally, the scan information may include the generation time of the QR code. Verification of the scan information may also include verification of the QR code generation time. The time difference between the current time and the QR code generation time can be calculated; if the time difference is less than a time difference threshold, the time verification of the QR code is deemed successful. Furthermore, in addition to time verification, the verification of the scan information may also include verification of the device information to be authenticated, as described in the following embodiments.

[0090] S205: If the scan information verification is successful, receive the device authorization information sent by the certified device.

[0091] Optionally, step 205 may include: parsing the scan information to obtain the device information to be authenticated from the scan information, the device information to be authenticated may include the device identifier of the device to be authenticated. The device information to be authenticated is compared with the device information of the device to be authenticated received in step 202. If the information comparison is successful, the scan information verification is determined to be successful. For example, the scanned string can be compared with the string used to generate the device QR code. If the strings match, the information comparison is successful, and the scan information verification is determined to be successful.

[0092] S206: Based on the device authorization information, determine that the device to be authenticated is a trusted device and determine that the first user has the identity of an envoy, so as to generate the binding information between the first user's envoy identity and the trusted device.

[0093] Optionally, step 206 may include: if it is determined that device authorization information has been received, then the device to be authenticated can be determined to be a trusted device. Determining that the first user has an envoy identity can refer to adding an envoy identity tag to the first user. When the first user performs transaction processing as an envoy, the specific user of the transaction can be another user besides the first user. After generating the binding information between the first user's envoy identity and the trusted device, this binding information can be stored in the envoy table to realize the binding between the first user's envoy identity and the trusted device. This allows the first user's envoy identity to be verified when the trusted device initiates a transaction request.

[0094] In practical applications, the envoy can act as an intermediary between the actual trader and the backend server. The actual trader can be a user with limited experience using internet products, such as a farmer. The envoy can initiate authentication of the device to be authenticated and, upon successful authentication, execute corresponding transaction processing on the trader's account. For example, the envoy could be a merchant familiar with the farmer. After successful authentication of the device to be authenticated and its corresponding first user possessing the envoy's identity, the trusted device can collect the trader's account information entered on the account input interface. After successful verification of the trader's account information, the trusted device can directly execute transaction processing on the trader's account information. Transaction processing can include, for example, withdrawals or deposits, electronic order processing, and financial product transactions.

[0095] In this embodiment, the server can obtain device information of the device to be authenticated by responding to a messenger addition request sent by the device to be authenticated. The messenger addition request may include a first user requesting to add a messenger identity. The server obtains device information of the device to be authenticated through the messenger addition request. The server can also generate a device QR code, which can be displayed for scanned by authenticated devices. The authenticated device can be a certified secure device. Obtaining the scan information sent by the authenticated device allows for information verification. If the verification is successful, the device to be authenticated can initiate authentication and receive device authorization information sent by the authenticated device. Based on the device authorization information, the device to be authenticated can be determined as a trusted device, and a messenger identity can be set for the first user. Binding the first user's messenger identity to the trusted device enables device authentication. Combining scanning and verification methods allows for more complex authentication of the device to be authenticated, improving the authentication security of the device to be authenticated.

[0096] Furthermore, based on the above embodiments, in response to a messenger addition request sent by the device to be authenticated, the device information of the device to be authenticated is obtained, including:

[0097] In response to a request to add an envoy sent by a device to be authenticated, real-name authentication is performed on the first user who initiated the request, and a real-name authentication result is obtained, which may be either successful or unsuccessful.

[0098] If the real-name authentication result is successful, then receive the QR code display request sent by the device to be authenticated;

[0099] In response to the QR code display request, obtain the device information of the device to be authenticated.

[0100] Optionally, the envoy request may include the user information of the first user. When performing real-name authentication on the first user who initiated the envoy request, the server may collect the first user's real-name information and perform authentication processing based on the first user's real-name information to obtain the real-name authentication result. The real-name information may include the first user's name, financial account, and other information.

[0101] Figure 3 A signaling diagram illustrating a device authentication method provided in an embodiment of this application. (Reference) Figure 3 The device to be authenticated 31 can perform step 301: send a messenger addition request to the server 32.

[0102] After receiving the request to add an envoy, server 32 can initiate the real-name authentication process for the first user. Specifically, step 302 can be executed: send a real-name authentication command to the device to be authenticated 31.

[0103] The device 32 to be authenticated can execute step 303: In response to the real-name authentication command, display the real-name authentication page, which may include prompts for collecting the user's real-name information. Step 304: Detect the confirmation operation performed by the first user in response to the prompts for collecting real-name information, and initiate the collection of the first user's real-name information. Specifically, it may collect at least one type of real-name information such as the first user's name and real-name account information. Step 305: The collected real-name information of the first user can be sent to the server 32.

[0104] Server 32 can execute step 306: receive the real-name information of the first user sent by the device to be authenticated 31, perform information authentication on the real-name information of the first user, and obtain a real-name authentication result. The information authentication of the first user's real-name information can include various methods, such as calling the historical real-name information of the first user in a third-party system and matching it with the received real-name information of the first user to obtain a real-name authentication result. Furthermore, the real-name information of the first user can also be information encrypted using an encryption algorithm. Server 32 can also use a decryption algorithm to decrypt the received real-name information; if decryption is successful, the real-name authentication is considered successful as a real-name authentication result. The encryption algorithm and decryption algorithm can be MD5 (Message-Digest Algorithm), etc., and can be specifically set according to usage requirements.

[0105] After server 32 successfully authenticates the first user's real name, it can execute step 307: send a successful real-name authentication notification to the device 31 to be authenticated. Then, it can execute step 308: receive a QR code display request from the device 32 to be authenticated. Then, it executes step 309: in response to the QR code display request, it collects the device information of the device 32 to be authenticated.

[0106] For example, the device to be authenticated can display a QR code scanning prompt control, detect the click operation performed by the first user on the prompt control, generate a QR code display request, and send the QR code display request to the server.

[0107] Further, optionally, server 32 can also perform step 310: generate a device QR code based on device information. Step 311 can be performed: send the generated device QR code to the device to be authenticated 31. Device to be authenticated 31 can perform step 312: display the device QR code. Then, authenticated device 33 can perform step 313: scan the device QR code displayed by device to be authenticated 31 to obtain scan information. Then, authenticated device 33 can perform step 314: send the scan information to server 32. Server 32 can receive the scan information sent by the authenticated device and perform step 315: verify the scan information. Device to be authenticated 33 can perform step 316: if the scan information verification is successful, send device authorization information to server 32 for server 32 to receive. Server 32 can perform step 317: based on the device authorization information, determine that the device to be authenticated is a trusted device and that the first user has an envoy identity, to generate binding information between the first user's envoy identity and the trusted device.

[0108] In this embodiment, before generating the device QR code for the device to be authenticated, real-name authentication can be performed on the first user to obtain the authentication result. After successful real-name authentication, a QR code display request from the device to be authenticated is received, and device information of the device to be authenticated is obtained based on the QR code display request. Real-name authentication allows for the verification of the operator of the device to be authenticated, i.e., the first user, thereby achieving secure real-name verification of the device and improving the security and effectiveness of device authentication.

[0109] Furthermore, based on any of the above embodiments, if the scan information verification is successful, device authorization information sent by the authenticated device is received, including:

[0110] If the scan information verification is successful, the authenticated device will be controlled to display an authorization prompt message. The authorization prompt message instructs the authenticated device to generate device authorization information when it detects a second user performing a click operation.

[0111] Receive device authorization information sent by certified devices.

[0112] Optionally, to further illustrate the implementation process of this application, when an authenticated device authorizes a device to be authenticated, the process may include: displaying an authorization prompt message; detecting the click operation performed by the second user in response to the authorization prompt message, generating device authorization information, and sending the device authorization information to the server.

[0113] Optionally, device information of the device to be authenticated and / or user information of the first user can be obtained based on the scan information. Device information may include, for example, device identifier, device name, and device type. User information may include user name and communication account. Authorization prompt information can be generated based on the device information of the device to be authenticated and / or the user information of the first user. The authorization prompt information may include the device information of the device to be authenticated and / or the user information of the first user. By displaying the device information of the device to be authenticated and / or the user information of the first user, the authorized object of the second user can be effectively prompted. This allows the second user to control the authorized object through the authorization prompt information displayed on the authenticated device, improving the security and effectiveness of authorization.

[0114] In this embodiment, when the scanned information is successfully verified, the authenticated device can be controlled to display an authorization prompt. This prompt instructs the authenticated device to generate device authorization information when it detects a click operation performed by a second user. By displaying the authorization prompt again upon successful scan verification, the second user can authorize the operation through the authenticated device, thus achieving manual authorization of the device to be authenticated and improving authorization security.

[0115] Furthermore, based on any of the above embodiments, determining that the first user possesses the identity of an envoy includes:

[0116] Perform biometric authentication on the first user and obtain the biometric authentication result, which may be authentication success or authentication failure.

[0117] Perform CAPTCHA authentication on the first user and obtain the CAPTCHA authentication result, which may be authentication success or authentication failure.

[0118] If both the biometric authentication result and the verification code authentication result are successful, then the first user is confirmed to have the identity of an envoy.

[0119] Optionally, biometric authentication processing may include face authentication processing, iris authentication processing, fingerprint authentication processing, etc. In this embodiment, the specific type of biometric authentication processing is not limited.

[0120] In this embodiment, before determining that the first user possesses the identity of an envoy, biometric authentication and verification code authentication can be performed on the first user. Biometric authentication allows for detailed verification of the first user's identity, while verification code authentication allows for communication authentication of the first user's device. This enables dual authentication using both biometric and communication features, achieving efficient and secure authentication of the first user. Furthermore, if both biometric and verification code authentication results are successful, the first user is determined to possess the identity of an envoy, thus improving the security and effectiveness of envoy identity authentication.

[0121] Furthermore, based on any of the above embodiments, performing biometric authentication processing on the first user to obtain a biometric authentication result includes:

[0122] Receive the target video sent by the device to be authenticated. The target video is the video captured by the device to be authenticated from the user's head.

[0123] The first user is subjected to facial authentication processing based on the target video, and the facial authentication result of the first user is used as the biometric authentication result.

[0124] For example, a face image can be extracted from the target video, and face features can be extracted from the face image. By matching the face features with the face features pre-associated with the first user, a face similarity can be obtained. If the face similarity is greater than the similarity threshold, the authentication is determined to be successful as a face authentication result; otherwise, the authentication is determined to be unsuccessful as a face authentication result.

[0125] In this embodiment, when performing biometric authentication on a user, a target video corresponding to the user's head can be captured by the device to be authenticated. Face authentication processing is then performed on the first user based on the target video to obtain the authentication result corresponding to the first user's face. By capturing the target video corresponding to the user's head in real time by the device to be authenticated, real-time authentication of the user's facial features can be achieved, resulting in more timely face authentication and improving the efficiency and accuracy of face authentication.

[0126] Furthermore, based on any of the above embodiments, performing verification code authentication processing on the first user to obtain the verification code authentication result includes:

[0127] Obtain the communication account associated with the first user;

[0128] Generate a verification code and send it to the instant messaging application associated with the first user's communication account. The instant messaging application is used to display the verification code.

[0129] The device to be authenticated is controlled to display a verification code input page, which instructs the first user to enter the verification code to be verified.

[0130] Receive the verification code to be verified from the input page of the device to be authenticated;

[0131] The verification code is processed to obtain the verification result.

[0132] Optionally, the communication account can be any of the following: the mobile phone number, instant messaging account, social media account, or profile picture account entered by the first user during registration. The verification code can be sent to the mobile phone number corresponding to the user's communication account via message or notification.

[0133] Optionally, after sending the verification code, controlling the device to be authenticated to display the verification code input page may include: if it is confirmed that the verification code has been received normally, a display instruction for the verification code input page may be sent to the device to be authenticated. The device to be authenticated may display the verification input page based on the received display instruction for the verification code input page.

[0134] In this embodiment, when performing verification code authentication on a user, the instant messaging program corresponding to the communication account associated with the first user can be obtained first. The verification code is then sent through the instant messaging program and displayed. The verification code is available for the user to view. By displaying a verification code input page on the device to be authenticated, the first user can be instructed to input the verification code, achieving real-time collection of the verification code. The real-time collected verification code can be verified against the generated verification code to obtain the verification result. Through interaction with the device to be authenticated, secure verification of the user's verification code is achieved, improving the verification effect and security.

[0135] Furthermore, based on any of the above embodiments, obtaining the device information of the device to be authenticated includes:

[0136] Send a device information read request to the device to be authenticated. The information read request instructs the device to be authenticated to provide device information.

[0137] Receive device information sent by the device to be authenticated.

[0138] Optionally, sending a device information read request to the device to be authenticated may include: calling a device bridging method and sending a parameter retrieval request for the device bridging method to the device to be authenticated. The parameter retrieval request may include parameters related to the device information to be read. The device to be authenticated may respond to the parameter retrieval request, assign values ​​to the parameters in the parameter retrieval request, obtain the device information, and then feed the device information back to the server. When the device to be authenticated feeds back the device information, it may encrypt the device information using an encryption algorithm to obtain encrypted device information. The device information received by the server may include the encrypted device information, which may be decrypted using a decryption algorithm to obtain the device information displayed on the interface. The encryption and decryption algorithms can be pre-set algorithms; this embodiment does not impose excessive limitations on the specific types of encryption and decryption algorithms.

[0139] In this embodiment of the application, when reading the device information of the device to be authenticated, the device information can be transmitted between the device to be authenticated and the server by sending an information reading request to the device to be authenticated, thereby improving the efficiency and security of the server in obtaining the device information of the device to be authenticated.

[0140] Furthermore, based on any of the above embodiments, in response to a envoy addition request sent by the device to be authenticated, real-name authentication processing is performed on the first user who initiated the envoy addition request. Before obtaining the real-name authentication result, the process further includes:

[0141] Receive the envoy addition request sent by the device to be authenticated. The envoy addition request is generated when the device to be authenticated detects that the first user has performed a trigger operation on the envoy addition prompt page.

[0142] After generating the first user's messenger identity and the binding information of the trusted device, it also includes:

[0143] Based on the binding information, generate a confirmation message for the messenger;

[0144] Send a messenger confirmation message to the device to be authenticated. The messenger confirmation message is used to instruct the device to output.

[0145] The envoy addition request can be detected by the device to be authenticated after the first user logs in. The envoy addition request can include the first user's login information.

[0146] In this embodiment, the server can receive a messenger addition request sent by the device to be authenticated. This request can be generated when the device to be authenticated detects a triggering operation performed by the first user on the messenger addition page, and can be initiated actively by the first user. Therefore, after the first user has a messenger identity and the binding information between the first user's messenger identity and the trusted device is generated, a messenger confirmation prompt can be generated based on the binding information and sent to the device to be authenticated. After the device to be authenticated outputs the messenger confirmation prompt, a similar prompt can be generated based on the binding information and sent to the device to be authenticated. The device to be authenticated then outputs the messenger confirmation prompt. Through information interaction and display interaction between the server and the device to be authenticated, accurate binding of messenger authentication information can be achieved, improving the security of identity and device binding.

[0147] Furthermore, based on any of the above embodiments, receiving a messenger addition request sent by the device to be authenticated includes:

[0148] Receive the login information of the first user sent by the device to be authenticated;

[0149] Perform login verification on the login information to obtain the login result;

[0150] If the login result is confirmed as successful, the device to be authenticated will be controlled to display the Messenger Addition Page. The Messenger Addition Page is used to instruct the first user to initiate a Messenger Addition Request through the device to be authenticated.

[0151] Receive a messenger addition request sent by the device to be authenticated.

[0152] For ease of understanding, Figure 4 This is yet another signaling diagram for a device authentication method provided in an embodiment of this application. (See reference) Figure 4 Before detecting the envoy addition request, the device to be authenticated 41 can perform step 401: detect the login request initiated by the first user and collect the login information entered by the first user. Step 402: send the login information to the server. After receiving the login information, the server 42 performs step 403: perform login verification processing on the login information and obtain the login result. After successful login and passing the login success message through step 404 on the device to be authenticated 41, the device to be authenticated 41 can also perform step 405: display the envoy addition page and pass step 406: detect the envoy addition request initiated by the first user through the device to be authenticated. After that, the device to be authenticated 41 can perform the above steps. Figure 3 Step 301: Send the messenger addition request to server 42. Server 42 can perform the above-mentioned steps. Figure 3 The steps are shown.

[0153] In this embodiment, the system can receive login information of a first user sent by the device to be authenticated. By performing login verification on the login information, a login result can be obtained. The login result represents the login effect of the first user on the device to be authenticated, and can include login success or login failure. When the login result is successful, the device to be authenticated can be controlled to display a envoy addition page. After displaying the envoy addition page, the device to be authenticated can display the envoy addition request initiated by the first user and send the envoy addition request back to the server. The server can receive the envoy addition request sent by the device to be authenticated. Through the envoy addition request, the server and the device to be authenticated can synchronize the envoy addition request of the first user, enabling the server to respond quickly to the envoy addition request of the first user in a timely manner, thereby improving the binding efficiency of user identity and device.

[0154] Furthermore, based on any of the above embodiments, if the scan information verification is successful, device authorization information sent by the authenticated device is received, including:

[0155] If the scan information verification is successful, the authenticated device will display the device authorization page. The device authorization page includes authorization prompts for the device to be authenticated. The authorization prompts are used to prompt the second user to authorize the device to be authenticated.

[0156] Receive device authorization information sent by an authenticated device. The device authorization information is generated based on the confirmation operation performed by the second user on the authorization prompt information.

[0157] To facilitate explanation of the device authentication process, after the device to be authenticated displays its QR code, the already authenticated device can also be used to: display scanning prompts for scanning the QR code of the device to be authenticated. The system can detect user actions triggered by these prompts, such as activating the camera to scan the QR code displayed on the device to be authenticated and obtain the scan information.

[0158] For example, the QR code scanning prompts can be from a prompt page associated with the device. Figure 5 As shown, the device binding prompt page 501 may include: a scan prompt message 5011 and a "Scan to Bind Device" prompt control 5012. The scan prompt message 5011 may include a scan prompt icon and the scan prompt text "Scan". When the authenticated device detects that the user clicks "Scan to Bind Device", it can activate its camera and scan the device's QR code to obtain the scan information.

[0159] After the scanned information is successfully verified, such as Figure 6 As shown, an authenticated device can also display a device authorization page 601, which may include authorization prompt information. (See reference) Figure 6 The authorization prompt message may include, for example, the text message 6011 stating, "The first user is applying for ambassador status on ** device. Please click 'Authorize' below after confirming that everything is correct," as well as an "Authorize" control 6012 and a "Cancel Authorization" control 6013. Here, "**" can refer to the device name or user information. After the authenticated device detects that the second user has clicked the "Authorize" control 6012, it can display a "Authorized" page prompt, indicating that the device to be authenticated has been authorized.

[0160] In this embodiment, upon successful verification of the scanned information, the authenticated device can be controlled to display a device authorization page. The device authorization page may include authorization prompts for the device to be authenticated. These prompts can be used to prompt a second user to authorize the envoy of the device to be authenticated. By having the second user confirm the envoy's authorization, the security of authorizing the envoy's identity as the first user can be improved, thus increasing device authorization efficiency. The server can receive device authorization information sent by the authenticated device. This device authorization information can be generated when the second user performs a confirmation operation on the authorization information, enabling the server to promptly determine the authorization confirmation process for the device to be authenticated by the authenticated device, thereby improving authorization processing efficiency and security.

[0161] Furthermore, based on any of the above embodiments, after generating the binding information between the first user's messenger identity and the trusted device, the method further includes:

[0162] Based on the first user's messenger identity and the binding information of the trusted device, the account information of the third user provided by the trusted device is obtained. The account information of the third user is obtained by the trusted device performing input detection on the account input control. The third user is different from the first user.

[0163] Perform security verification on the third user's account information and obtain the account verification result;

[0164] If the account verification result is successful, the system receives an account transaction request from the trusted device. The account transaction request is generated by a transaction operation to be performed on the account information of a third user.

[0165] In response to an account transaction request, execute the corresponding account transaction on the third user's account information and obtain the account transaction result;

[0166] Send the account transaction results to a trusted device, and the trusted device will display the account transaction results.

[0167] Optionally, the third user can be a user different from the first user and the second user. In this embodiment, the names first, second, third, etc. are used to distinguish different users and do not have any meaning of order or size.

[0168] The third user can be a user who needs to execute account transactions through the trusted device corresponding to the first user.

[0169] For ease of understanding, after determining that the device to be authenticated is a trusted device, confirming that the first user possesses the identity of an envoy, and generating the binding information between the first user's envoy identity and the trusted device, as follows: Figure 7 As shown, the device to be authenticated is designated as trusted device 71, which can communicate with server 72. Trusted device 71 can execute step 701: collect the account information of a third user. Then, it executes step 702: send the third user's account information to server 72. Server 72 can execute step 703: perform security verification on the third user's account information and obtain the account verification result. Then, it executes step 704: send the account verification result to trusted device 71. When the account verification result is successful, trusted device 71 can execute step 705: collect an account transaction request for the third user's account information. Then, trusted device 71 can execute step 706: send the account transaction request for the third user's account information to server 72. Server 72 can receive the account transaction request sent by trusted device. Then, it executes step 707: responding to the account transaction request, performs the corresponding account transaction on the third user's account information, and obtains the account transaction result. Then, it executes step 708: send the account transaction result to trusted device 71. After receiving the account transaction result, trusted device 71 can execute step 709: display the account transaction result.

[0170] In this embodiment, after binding the first user's envoy identity to the trusted device, the account information of the third user provided by the trusted device can be obtained based on the binding information of the first user's envoy identity and the trusted device. The third user's account information can be obtained by the trusted device performing input detection on the account input control. The third user is different from the first user. After successfully verifying the third user's account information, an account verification result can be obtained. If the account verification result is determined to be successful, an account transaction request sent by the trusted device can be received, and the corresponding account transaction can be performed on the third user's account information to obtain the account transaction result, which can be displayed by the trusted device. After the first user authorizes the envoy identity and completes the binding of the trusted device, the account information of the third user can be processed for transactions, that is, transactions can be processed for the second user through the trusted device of the first user, thereby improving transaction efficiency.

[0171] Furthermore, based on any of the above embodiments, before generating the binding information between the first user's messenger identity and the trusted device, the method further includes:

[0172] Obtain the Messenger Table, which includes at least one Messenger user who has already been identified as a Messenger and each Messenger user has been associated with a historically trusted device.

[0173] Check if the first user is included in at least one of the messenger users in the messenger table;

[0174] If so, then remove the binding relationship between the first user and its associated historical trusted device.

[0175] Optionally, the envoy table may include at least one envoy user with envoy identity, and each envoy user may be associated with a historical trusted device. The envoy user may include envoy information such as envoy identifier and number. Trusted devices may include device information such as device number, device model, device name, and binding status.

[0176] If the first user is not included in at least one of the messenger users in the messenger table, then new association information between the messenger user and the trusted device can be generated and stored based on the first user's user information, trusted device, and their binding relationship. The messenger table can include at least one association record, each corresponding to a messenger user, who can be associated with a historical trusted device.

[0177] Optionally, unbinding the first user from its associated historical trusted devices may include: generating and storing a temporary messenger table based on the first user's user information, the first user's associated historical trusted devices, and the authorized devices to be authenticated. After updating the messenger table according to the first user's messenger identity and the binding information of trusted devices, the binding relationship between the first user and its associated historical trusted devices is unbound. The temporary messenger table records the alternating bindings of old and new devices, enabling accurate recording and querying of information.

[0178] In this embodiment, an envoy table can be obtained, which may include at least one envoy user who already possesses envoy identity, and each envoy user is associated with a historically trusted device. The envoy table can be used to query whether the first user is among the at least one envoy user. If so, the binding relationship between the first user and its associated historically trusted device can be removed. By removing the binding relationship between the first user and its associated historically trusted device, the device bound to the first user can be switched, ensuring that the device to be bound can establish an identity binding with the first user.

[0179] Furthermore, based on any of the above embodiments, after generating the binding information between the first user's messenger identity and the trusted device, the method further includes:

[0180] Based on the binding information between the first user's envoy identity and the trusted device, the envoy table is updated to obtain the updated envoy table. In the updated envoy table, the trusted device associated with the first user is changed to the device to be authenticated.

[0181] Optionally, if the first user is associated with a previously trusted device, the binding information associated with the first user can be updated based on the device identifier of the device to be authenticated. For example, the binding information may include the device identifier of the new trusted device, the QR code string corresponding to the device information, the device model, the device name, a flag indicating whether the scan was successful (default is no), the scanning device identifier (default is 0, initial value), a flag indicating whether authorization has been obtained from an authenticated device (default is 0, pending authorization), the messenger's name, the messenger's mobile phone number, the previously trusted device number, the previously trusted device model, and the previously trusted device name, etc.

[0182] Optionally, a polling mechanism can be initiated to update the identifiers or flags of each binding record in the messenger table. For example, it can poll to check whether the authenticated device has scanned the QR code of the device to be authenticated. If the scan is successful, the scanning device identifier can be updated to 1; otherwise, it remains at 0. The polling frequency (queryInterval) can be set according to usage requirements and can be controlled through the system's polling parameters. The default is once per second, and log information can be recorded after each poll.

[0183] In this embodiment of the application, after the binding information is established, the messenger table can be updated so that the messenger users and the historical trusted devices associated with the messenger users stored in the messenger table are updated in a timely manner, thereby improving the timeliness of the messenger table.

[0184] Furthermore, based on any of the above embodiments, before receiving the scanning information sent by the authenticated device, the method further includes:

[0185] Receive a login request sent by an authenticated device, the login request including the login information of the second user;

[0186] Perform login verification on the second user's login information in the login request and obtain the login verification result;

[0187] If the login verification result is successful, the network login request sent by the authenticated device is received. The network login request includes the target network selected by the second user in at least one candidate network.

[0188] If the network point bound to the second user is determined to be the target network point, the authenticated device is controlled to display the device scanning page, which instructs the authenticated device to start scanning the QR code of the device to be authenticated.

[0189] Optionally, the second user's login information may include: a login username and password. The username can be an employee account or a branch account set up for the branch. Employee accounts or branch accounts can be used to ensure the security of authenticated devices.

[0190] At least one candidate site can be set based on the device location and site name of the certified device, specifically including site identifier, site name, location, and other information. The certified device can be a portable Android device or a certified tablet terminal device.

[0191] In this embodiment, a login request sent by an authenticated device can be received. The login request may include the login information of a second user. By verifying the second user's login information, the authenticated device can be logged in and used. Upon successful verification, at least one candidate service point is displayed for the user to select a target service point. Using the target service point, a service point scan can be performed on the second user, improving the security of the authenticated device.

[0192] like Figure 8 The diagram shown is a flowchart of a device authentication method provided in an embodiment of this application. This method can be applied to a device to be authenticated and includes:

[0193] S801: Detects the first user's trigger operation on the "Add Messenger" prompt page and generates a "Add Messenger" request.

[0194] S802: Send a messenger addition request to the server. The messenger addition request instructs the server to initiate a device information read request.

[0195] S803: In response to a device information read request sent by the server, send device information to the server. The device information instructs the server to generate a device QR code.

[0196] S804: Receives and displays the device QR code fed back by the server. The device QR code indicates that the authenticated device can be scanned and verified, and the device can be authorized.

[0197] S805: Receives feedback from the server that the device to be authenticated is a trusted device, as well as the first user's messenger identity and the binding information of the trusted device.

[0198] It should be noted that, in the embodiments of this application, the specific steps performed by the device to be authenticated and the device as a trusted device after successful authentication can be referred to the above. Figures 2-7 The descriptions of the embodiments are omitted here.

[0199] In this embodiment, the device to be authenticated can initiate a messenger addition request to the server. The server can obtain device information from the request, which may include a first user requesting to add a messenger identity. The server can also generate a device QR code for display and scanning by an already authenticated device. The authenticated device can be a certified secure device. The server can verify the scanned information sent by the authenticated device; successful verification indicates that the device to be authenticated can initiate authentication and receive device authorization information from the authenticated device. Based on the device authorization information, the device to be authenticated can be determined as a trusted device, and a messenger identity can be set for the first user. Binding the first user's messenger identity to the trusted device enables device authentication. Combining scanning and verification methods allows for more complex authentication of the device to be authenticated, improving authentication security.

[0200] like Figure 9 The diagram shown is a flowchart of a device authentication method provided in an embodiment of this application. This method can be applied to authenticated devices and includes:

[0201] S901: In response to a scanning request initiated by the second user, scan the device QR code displayed on the device to be authenticated to obtain scanning information. The device QR code is generated by the server based on the device information of the device to be authenticated. The device information is obtained by the server from the device to be authenticated when it receives a messenger addition request initiated by the device to be authenticated.

[0202] S902: Send scan information to the server. The scan information instructs the server to perform a scan verification and displays the device authorization page upon successful verification.

[0203] S903: Displays the device authorization page, which includes authorization prompts for the device to be authenticated. These prompts are used to remind the second user to authorize the device to be authenticated.

[0204] S904: In response to the confirmation operation performed by the second user on the authorization prompt information, device authorization information is sent to the server. The device authorization information instructs the server to determine that the device to be authenticated is a trusted device and the binding information between the first user's messenger identity and the trusted device. The first user is the user who logs in to the device to be authenticated.

[0205] It should be noted that, in the embodiments of this application, the specific steps performed by the certified device can be referred to the above. Figures 2-7 The descriptions of the embodiments are omitted here.

[0206] In this embodiment, the server can obtain device information of the device to be authenticated by responding to a messenger addition request sent by the device to be authenticated. The messenger addition request may include a first user requesting to add a messenger identity. The server obtains device information of the device to be authenticated through the messenger addition request. The server can also generate a device QR code, which can be displayed for scanned by authenticated devices. The authenticated device can be a certified secure device. Obtaining the scan information sent by the authenticated device allows for information verification. If the verification is successful, the device to be authenticated can initiate authentication and receive device authorization information sent by the authenticated device. Based on the device authorization information, the device to be authenticated can be determined as a trusted device, and a messenger identity can be set for the first user. Binding the first user's messenger identity to the trusted device enables device authentication. Combining scanning and verification methods allows for more complex authentication of the device to be authenticated, improving the authentication security of the device to be authenticated.

[0207] like Figure 10 The diagram shown is a structural schematic of one embodiment of a device authentication apparatus provided in this application. The apparatus can be located on a server, which connects the device to be authenticated and the authenticated device. The device authentication apparatus 1000 may include:

[0208] First Response Unit 1001: Used to respond to a envoy addition request sent by the device to be authenticated, and obtain device information of the device to be authenticated. The envoy addition request includes a first user requesting to add envoy identity.

[0209] First generation unit 1002: used to generate a device QR code based on the device information of the device to be certified.

[0210] First display unit 1003: Used to control the device to be authenticated to display the device QR code, the device QR code is scanned by the authenticated device to obtain the corresponding scanning information.

[0211] First receiving unit 1004: Used to receive scanning information sent by the authenticated device.

[0212] The second receiving unit 1005 is used to receive device authorization information sent by the authenticated device if the scanning information verification is successful.

[0213] Device authorization unit 1006: Based on device authorization information, it determines that the device to be authenticated is a trusted device and that the first user has an envoy identity, so as to generate binding information between the first user's envoy identity and the trusted device.

[0214] As one embodiment, the first response unit may include:

[0215] The real-name authentication module is used to respond to the envoy addition request sent by the device to be authenticated, perform real-name authentication processing on the first user who initiated the envoy addition request, and obtain the real-name authentication result, which includes real-name authentication success or real-name authentication failure.

[0216] The first receiving module is used to receive the QR code display request sent by the device to be authenticated if the real-name authentication result is successful.

[0217] The display response module is used to respond to QR code display requests and obtain device information of the device to be authenticated.

[0218] As another embodiment, the second receiving unit includes:

[0219] The authorization display module is used to control the authenticated device to display authorization prompt information if the scan information verification is successful. The authorization prompt information instructs the authenticated device to generate device authorization information when it detects a second user performing a click operation.

[0220] The authorization receiving module is used to receive device authorization information sent by certified devices.

[0221] As another embodiment, the device authorization unit includes:

[0222] The biometric authentication module is used to perform biometric authentication processing on the first user and obtain the biometric authentication result, which includes authentication success or authentication failure.

[0223] The verification and authentication module is used to perform verification code authentication processing on the first user and obtain the verification code authentication result, which includes authentication success or authentication failure.

[0224] The identity authorization module is used to determine that the first user has the identity of an envoy if both the biometric authentication result and the verification code authentication result are successful.

[0225] As yet another embodiment, the biometric authentication module includes:

[0226] The video capture submodule is used to receive the target video sent by the device to be authenticated. The target video is the video captured by the device to be authenticated from the user's head.

[0227] The face authentication module is used to perform face authentication processing on the first user based on the target video, and obtain the face authentication result of the first user as the biometric authentication result.

[0228] As another embodiment, the verification and authentication module includes:

[0229] The account retrieval submodule is used to retrieve the communication account associated with the first user;

[0230] The verification sending submodule is used to generate a verification code and send the verification code to the instant messaging program corresponding to the communication account associated with the first user.

[0231] The verification input submodule is used to control the device to be authenticated to display the verification code input page, which instructs the first user to enter the verification code to be verified.

[0232] The verification receiving submodule is used to receive the verification code collected from the verification code input page of the device to be authenticated;

[0233] The verification submodule is used to verify the verification code to be verified and obtain the verification result.

[0234] As another embodiment, the first response unit may include:

[0235] The request sending module is used to send a device information read request to the device to be authenticated. The information read request instructs the device to be authenticated to provide device information.

[0236] The information receiving module is used to receive device information sent by the device to be authenticated.

[0237] As yet another embodiment, it also includes:

[0238] An additional receiving unit is added to receive the envoy addition request sent by the device to be authenticated. The envoy addition request is generated when the device to be authenticated detects that the first user has performed a trigger operation on the envoy addition prompt page.

[0239] The binding confirmation unit is used to generate a messenger confirmation prompt message based on the binding information.

[0240] The authentication prompt unit is used to send a messenger confirmation prompt message to the device to be authenticated. The messenger confirmation prompt message is used to instruct the device to be authenticated to output.

[0241] As another embodiment, a receiving unit is added, including:

[0242] The login receiving module is used to receive the login information of the first user sent by the device to be authenticated;

[0243] The login verification module is used to verify login information and obtain the login result.

[0244] Add a display module to control the device to be authenticated to display the envoy addition page if the login result is confirmed as successful. The envoy addition page is used to instruct the first user to initiate an envoy addition request through the device to be authenticated.

[0245] The second receiving module is used to receive messenger addition requests sent by the device to be authenticated.

[0246] As another embodiment, the second receiving unit includes:

[0247] The page display module is used to control the certified device to display the device authorization page if the scan information verification is successful. The device authorization page includes authorization prompt information for the device to be certified. The authorization prompt information is used to prompt the second user to authorize the device to be certified.

[0248] The device authorization module is used to receive device authorization information sent by the authenticated device. The device authorization information is generated based on the confirmation operation performed by the second user on the authorization prompt information.

[0249] As yet another embodiment, it also includes:

[0250] The account acquisition unit is used to obtain the account information of the third user provided by the trusted device based on the binding information between the first user's envoy identity and the trusted device. The account information of the third user is obtained by the trusted device performing input detection on the account input control. The third user is different from the first user.

[0251] The account verification unit is used to perform security verification on the account information of third-party users and obtain the account verification result.

[0252] The transaction request unit is used to receive an account transaction request sent by a trusted device if the account verification result is determined to be successful. The account transaction request is generated by a transaction operation to be performed on the account information of a third user.

[0253] The account transaction unit is used to respond to an account transaction request, execute the corresponding account transaction on the account information of a third user, and obtain the account transaction result;

[0254] The result display unit is used to send account transaction results to a trusted device, and the trusted device displays the account transaction results.

[0255] As yet another embodiment, it also includes:

[0256] The table acquisition unit is used to acquire the messenger table, which includes at least one messenger user who has already acquired messenger identity, and each messenger user has been associated with a historical trusted device.

[0257] The user query unit is used to query whether the first user is included in at least one of the envoy users in the envoy table.

[0258] The binding release unit is used to release the binding relationship between the first user and its associated historical trusted device if the condition is met.

[0259] As yet another embodiment, it also includes:

[0260] The table update unit is used to update the messenger table based on the binding information between the first user's messenger identity and the trusted device, and obtain the updated messenger table. In the updated messenger table, the trusted device associated with the first user is changed to the device to be authenticated.

[0261] As yet another embodiment, it also includes:

[0262] The second login unit is used to receive login requests sent by authenticated devices, and the login requests include the login information of the second user.

[0263] The login verification unit is used to verify the login information of the second user in the login request and obtain the login verification result.

[0264] The site determination unit is used to receive a site login request sent by an authenticated device if the login verification result is determined to be successful. The site login request includes the target site selected by the second user from at least one candidate site.

[0265] The branch login unit is used to control the authenticated device to display the device scanning page if it is determined that the branch bound to the second user is the target branch. The device scanning page instructs the authenticated device to start scanning the QR code for the device to be authenticated.

[0266] like Figure 11 The diagram shown is a structural schematic of one embodiment of a device authentication apparatus provided in this application. The apparatus can be located on the device to be authenticated. The device authentication apparatus 1100 may include:

[0267] First detection unit 1101: used to detect when the first user performs a trigger operation on the prompt page for adding a messenger and generate a request to add a messenger.

[0268] First sending unit 1102: used to send a messenger addition request to the server, the messenger addition request instructing the server to initiate a device information reading request.

[0269] Second response unit 1103: Used to respond to the device information reading request sent by the server, send device information to the server, and instruct the server to generate a device QR code.

[0270] The third receiving unit 1104 is used to receive and display the device QR code fed back by the server. The device QR code indicates that the authenticated device should be scanned and verified, and the device should be authorized.

[0271] Fourth receiving unit 1105: Used to receive the authentication information from the server, indicating that the device to be authenticated is a trusted device, as well as the messenger identity of the first user and the binding information of the trusted device.

[0272] like Figure 12 The diagram shown is a structural schematic of one embodiment of a device authentication apparatus provided in this application. This apparatus can be located on an authenticated device, and the device authentication apparatus 1200 may include:

[0273] The third response unit 1201 is used to respond to the scanning request initiated by the second user, scan the device QR code displayed by the device to be authenticated, and obtain the scanning information. The device QR code is generated by the server based on the device information of the device to be authenticated. The device information is obtained by the server from the device to be authenticated when it receives the envoy addition request initiated by the device to be authenticated.

[0274] The second sending unit 1202 is used to send scanning information to the server. The scanning information instructs the server to perform scanning verification, and displays the device authorization page when the verification is successful.

[0275] The second display unit 1203 is used to display a device authorization page, which includes authorization prompt information for the device to be authenticated. The authorization prompt information is used to prompt the second user to authorize the device to be authenticated.

[0276] The third response unit 1204 is used to respond to the confirmation operation performed by the second user on the authorization prompt information, and send device authorization information to the server. The device authorization information instructs the server to determine that the device to be authenticated is a trusted device and the binding information between the first user's messenger identity and the trusted device.

[0277] The apparatus of this application can be used to perform the above method. The specific steps performed by each unit, module and sub-module can be referred to the embodiments of the above method, and will not be repeated here.

[0278] Figure 13 This is a block diagram illustrating a terminal device for implementing a device authentication method according to an exemplary embodiment. The device may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.

[0279] Device 1300 may include one or more of the following components: processing component 1302, memory 1304, power supply component 1306, multimedia component 1308, audio component 1310, input / output (I / O) interface 1312, sensor component 1314, and communication component 1316.

[0280] Processing component 1302 typically controls the overall operation of device 1300, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1302 may include one or more processors 1320 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 1302 may include one or more modules to facilitate interaction between processing component 1302 and other components. For example, processing component 1302 may include a multimedia module to facilitate interaction between multimedia component 1308 and processing component 1302.

[0281] Memory 1304 is configured to store various types of data to support the operation of device 1300. Examples of such data include instructions for any application or method operating on device 1300, contact data, phonebook data, messages, pictures, videos, etc. Memory 1304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0282] Power supply component 1306 provides power to various components of device 1300. Power supply component 1306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 1300.

[0283] Multimedia component 1308 includes a screen that provides an output interface between device 1300 and a first user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the first user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 1308 includes a front-facing camera and / or a rear-facing camera. When device 1300 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0284] Audio component 1310 is configured to output and / or input audio signals. For example, audio component 1310 includes a microphone (MIC) configured to receive external audio signals when device 1300 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1304 or transmitted via communication component 1316. In some embodiments, audio component 1310 also includes a speaker for outputting audio signals.

[0285] I / O interface 1312 provides an interface between processing component 1302 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0286] Sensor assembly 1314 includes one or more sensors for providing state detection of various aspects of device 1300. For example, sensor assembly 1314 may detect the on / off state of device 1300, the relative positioning of components, such as the display and keypad of device 1300, changes in position of device 1300 or a component of device 1300, the presence or absence of contact between a first user and device 1300, orientation or acceleration / deceleration of device 1300, and temperature changes of device 1300. Sensor assembly 1314 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1314 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0287] Communication component 1316 is configured to facilitate wired or wireless communication between device 1300 and other devices. Device 1300 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 1316 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1316 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0288] In an exemplary embodiment, the apparatus 1300 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0289] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1304 including instructions, which can be executed by a processor 1320 of the device 1300 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0290] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the above-described device authentication method.

[0291] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described device authentication method.

[0292] This application also provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform any of the device authentication methods of this application. The electronic device may include the server, authenticated device, and device to be authenticated as described in the above embodiments.

[0293] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims. It should be understood that this application is not limited to the precise structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims. < / t>

Claims

1. A device authentication method, characterized in that, Applied to a server, the server connecting a device to be authenticated and an authenticated device, the method includes: In response to a request to add an envoy sent by a device to be authenticated, the device information of the device to be authenticated is obtained. The request to add an envoy includes a first user requesting to add an envoy identity. The envoy is a user identity corresponding to the application service provided when the device to be authenticated is successfully authenticated. Generate a device QR code based on the device information of the device to be authenticated; The device to be authenticated is controlled to display the device QR code, and the device QR code is scanned by the authenticated device to obtain the corresponding scanning information; Receive scanning information sent by the authenticated device; If the scan information is successfully verified, the device authorization information sent by the authenticated device is received; Based on the device authorization information, the device to be authenticated is determined to be a trusted device, and the first user is determined to have an envoy identity, so as to generate binding information between the first user's envoy identity and the trusted device.

2. The method according to claim 1, characterized in that, The step of responding to a messenger addition request sent by the device to be authenticated, and obtaining the device information of the device to be authenticated, includes: In response to the envoy addition request sent by the device to be authenticated, real-name authentication processing is performed on the first user who initiated the envoy addition request to obtain a real-name authentication result, which includes real-name authentication success or real-name authentication failure. If the real-name authentication result is successful, then receive the QR code display request sent by the device to be authenticated; In response to the QR code display request, the device information of the device to be authenticated is obtained.

3. The method according to claim 1, characterized in that, If the scan information is successfully verified, then the device authorization information sent by the authenticated device is received, including: If the scan information is successfully verified, the authenticated device is controlled to display an authorization prompt message. The authorization prompt message instructs the authenticated device to generate device authorization information when it detects a second user performing a click operation. Receive device authorization information sent by the certified device.

4. The method according to claim 1, characterized in that, The determination that the first user has the identity of an envoy includes: Perform biometric authentication processing on the first user to obtain a biometric authentication result, which includes authentication success or authentication failure. Perform verification code authentication on the first user and obtain the verification code authentication result, which includes authentication success or authentication failure. If both the biometric authentication result and the verification code authentication result are successful, then the first user is determined to have the identity of an envoy.

5. The method according to claim 4, characterized in that, The step of performing biometric authentication processing on the first user to obtain a biometric authentication result includes: Receive the target video sent by the device to be authenticated, wherein the target video is a video captured by the device to be authenticated of the user's head; The first user is subjected to facial authentication processing based on the target video, and the facial authentication result of the first user is obtained as the biometric authentication result.

6. The method according to claim 4, characterized in that, The step of performing verification code authentication on the first user and obtaining the verification code authentication result includes: Obtain the communication account associated with the first user; Generate a verification code and send the verification code to the instant messaging program corresponding to the communication account associated with the first user; The device to be authenticated is controlled to display a verification code input page, which instructs the first user to input the verification code to be verified. Receive the verification code to be verified from the verification code input page sent by the device to be authenticated; The verification code to be verified is processed according to the verification code to obtain the verification code verification result.

7. The method according to claim 1, characterized in that, The step of obtaining the device information of the device to be authenticated includes: A device information read request is sent to the device to be authenticated, and the information read request instructs the device to be authenticated to provide device information. Receive device information sent by the device to be authenticated.

8. The method according to claim 1, characterized in that, Before performing real-name authentication processing on the first user who initiated the envoy addition request in response to the envoy addition request sent by the device to be authenticated, and before obtaining the real-name authentication result, the process further includes: Receive the envoy addition request sent by the device to be authenticated, the envoy addition request being generated by the device to be authenticated when it detects that the first user performs a trigger operation on the envoy addition prompt page; After generating the binding information between the first user's messenger identity and the trusted device, the process further includes: Based on the binding information, a messenger confirmation prompt message is generated; The envoy confirmation message is sent to the device to be authenticated, and the envoy confirmation message is used to instruct the device to be authenticated to output.

9. The method according to claim 8, characterized in that, The process of receiving the messenger addition request sent by the device to be authenticated includes: Receive the login information of the first user sent by the device to be authenticated; The login information is verified to obtain a login result; If the login result is determined to be a successful login, the device to be authenticated is controlled to display the envoy addition page, which is used to instruct the first user to initiate an envoy addition request through the device to be authenticated. Receive the messenger addition request sent by the device to be authenticated.

10. The method according to claim 1, characterized in that, If the scan information is successfully verified, then the device authorization information sent by the authenticated device is received, including: If the scan information is successfully verified, the authenticated device is controlled to display a device authorization page. The device authorization page includes authorization prompt information for the device to be authenticated. The authorization prompt information is used to prompt the second user to authorize the device to be authenticated. The device authorization information sent by the authenticated device is received, and the device authorization information is generated based on the confirmation operation performed by the second user on the authorization prompt information.

11. The method according to claim 1, characterized in that, After generating the binding information between the first user's messenger identity and the trusted device, the process further includes: Based on the binding information between the first user's envoy identity and the trusted device, the account information of the third user provided by the trusted device is obtained. The account information of the third user is obtained by the trusted device performing input detection on the account input control. The third user is different from the first user. The account information of the third user is verified for security purposes, and the account verification result is obtained. If the account verification result is determined to be successful, then the trusted device sends an account transaction request, which is generated by a transaction operation performed on the account information of the third user. In response to the account transaction request, perform the corresponding account transaction on the third user's account information and obtain the account transaction result; The account transaction result is sent to the trusted device, and the account transaction result is displayed on the trusted device.

12. The method according to claim 1, characterized in that, Before generating the binding information between the first user's messenger identity and the trusted device, the process also includes: Obtain the envoy table, which includes at least one envoy user who has already obtained envoy identity, and each envoy user has been associated with a historical trusted device; Query whether the first user is included in at least one of the envoy users in the envoy table; If so, then the binding relationship between the first user and its associated historical trusted device is removed.

13. The method according to claim 12, characterized in that, After generating the binding information between the first user's messenger identity and the trusted device, the process further includes: Based on the binding information between the first user's envoy identity and the trusted device, the envoy table is updated to obtain an updated envoy table. In the updated envoy table, the trusted device associated with the first user is changed to the device to be authenticated.

14. The method according to claim 1, characterized in that, Before receiving the scan information sent by the authenticated device, the method further includes: Receive a login request sent by the authenticated device, the login request including the login information of the second user; The login information of the second user in the login request is verified to obtain the login verification result; If the login verification result is determined to be successful, then the network login request sent by the authenticated device is received. The network login request includes the target network selected by the second user from at least one candidate network. If it is determined that the network point bound to the second user is the target network point, then the authenticated device is controlled to display a device scanning page, and the device scanning page instructs the authenticated device to start scanning the QR code for the device to be authenticated.

15. A device authentication method, characterized in that, Applied to a device to be authenticated, the method includes: The detection process involves the first user triggering an operation on the prompt page for adding an envoy, generating an envoy addition request. The envoy is a user identity corresponding to the application service provided when the device to be authenticated is successfully authenticated. The messenger addition request is sent to the server, and the messenger addition request instructs the server to initiate a device information read request; In response to a device information read request sent by the server, device information is sent to the server, and the device information instructs the server to generate a device QR code; Receive and display the device QR code fed back by the server, the device QR code instructs an authenticated device to scan and perform scanning verification and device authorization; The server receives feedback that the device to be authenticated is a trusted device, as well as the first user's envoy identity and the binding information of the trusted device.

16. A device authentication method, characterized in that, Applied to certified devices, the method includes: In response to a scanning request initiated by a second user, the device QR code displayed on the device to be authenticated is scanned to obtain scanning information. The device QR code is generated by the server based on the device information of the device to be authenticated. The device information is obtained by the server from the device to be authenticated when it receives a request to add an envoy. The envoy is a user identity corresponding to the application service provided when the device to be authenticated is successfully authenticated. The scan information is sent to the server, which instructs the server to perform a scan verification and displays a device authorization page upon successful verification. Display device authorization page, the device authorization page includes authorization prompt information for the device to be authenticated, the authorization prompt information is used to prompt the second user to authorize the device to be authenticated; In response to the confirmation operation performed by the second user on the authorization prompt information, device authorization information is sent to the server. The device authorization information instructs the server to determine that the device to be authenticated is a trusted device and the binding information between the first user's messenger identity and the trusted device. The first user is the user who logs in to the device to be authenticated.

17. A device authentication apparatus, characterized in that, Located on a server, the server connects the device to be authenticated and the device already authenticated, the device includes: The first response unit is used to respond to a envoy addition request sent by the device to be authenticated, and to obtain the device information of the device to be authenticated. The envoy addition request includes a first user requesting to add an envoy identity. The envoy is a user identity corresponding to the application service provided when the device to be authenticated is successfully authenticated. The first generation unit is used to generate a device QR code based on the device information of the device to be authenticated; The first display unit is used to control the device to be authenticated to display the device QR code, and the device QR code is scanned by the authenticated device to obtain the corresponding scanning information. The first receiving unit is used to receive the scanning information sent by the authenticated device; The second receiving unit is used to receive device authorization information sent by the authenticated device if the scanning information is successfully verified. The device authorization unit is used to determine, based on the device authorization information, that the device to be authenticated is a trusted device and that the first user has an envoy identity, so as to generate binding information between the first user's envoy identity and the trusted device.

18. A device authentication apparatus, characterized in that, Located in the device to be authenticated, the device includes: The first detection unit is used to detect when the first user performs a trigger operation on the envoy addition prompt page and generates an envoy addition request. The envoy is a user identity corresponding to the application service provided when the device to be authenticated is successfully authenticated. The first sending unit is used to send the messenger addition request to the server, wherein the messenger addition request instructs the server to initiate a device information reading request; The second response unit is used to respond to the device information reading request sent by the server, and send device information to the server, wherein the device information instructs the server to generate a device QR code; The third receiving unit is used to receive and display the device QR code fed back by the server. The device QR code indicates that the authenticated device should scan and perform scanning verification and device authorization. The fourth receiving unit is used to receive the authentication information from the server, which indicates that the device to be authenticated is a trusted device, as well as the envoy identity of the first user and the binding information of the trusted device.

19. A device authentication apparatus, characterized in that, Located in a certified device, the apparatus includes: The third response unit is used to respond to the scanning request initiated by the second user, scan the device QR code displayed by the device to be authenticated, and obtain the scanning information. The device QR code is generated by the server based on the device information of the device to be authenticated. The device information is obtained by the server from the device to be authenticated when it receives a request to add an envoy initiated by the device to be authenticated. The envoy is a user identity corresponding to the application service provided when the device to be authenticated is successfully authenticated. The second sending unit is used to send the scanning information to the server, the scanning information instructing the server to perform scanning verification, and to display the device authorization page when the verification is successful. The second display unit is used to display a device authorization page, which includes authorization prompt information for the device to be authenticated. The authorization prompt information is used to prompt the second user to authorize the device to be authenticated. The third response unit is used to respond to the confirmation operation performed by the second user on the authorization prompt information, and send device authorization information to the server. The device authorization information instructs the server to determine that the device to be authenticated is a trusted device and the binding information between the first user's messenger identity and the trusted device.

20. An electronic device, comprising: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-14, 15, or 16.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-14, 15, or 16.

Citation Information

Patent Citations

  • Method, device and system for realizing authentication between devices

    CN106992956A

  • Code scanning authentication method, server, fixed terminal and mobile terminal

    CN110474958A