Device authentication method, device, electronic device and storage medium

Abstract

The present application provides a device authentication method, apparatus, electronic device and storage medium, which are applied to the field of information security technology. The method includes: receiving a device authentication request for a terminal device; obtaining the target device attribute corresponding to the first authentication server from the attribute correspondence, and generating the current device fingerprint of the terminal device according to the target device attribute, wherein the attribute correspondence includes the correspondence between each authentication server and different device attributes; comparing the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain, and confirming whether the terminal device is authenticated according to the comparison result, wherein the historical device fingerprint is generated by the second authentication server and stored in the trusted blockchain. The present application can improve the efficiency and accuracy of device identity authentication.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a device authentication method, apparatus, electronic device and storage medium. Background Art

[0002] With the development of network technology, many information security risks have also been brought about. Therefore, for various data platforms, authenticating the identity of devices accessing the platform is a necessary measure to prevent the platform from being maliciously attacked.

[0003] In the prior art, the candidate server usually generates a device fingerprint that can uniquely identify the terminal device based on the device attributes reported by the terminal device to authenticate the device identity. However, this method is overly dependent on a single backend server. If the user maliciously tampers with certain device attributes, the device fingerprint may become unstable, affecting the accuracy of device authentication. In addition, as the dimensions of device attributes increase, the amount of data processing required by the backend server for identity authentication also increases, reducing the efficiency of identity authentication. Summary of the invention

[0004] The embodiments of the present application provide a device authentication method, apparatus, electronic device, and computer-readable storage medium, which are intended to solve as much as possible the technical problems in the related art of over-reliance on a single backend server to generate device fingerprints based on device attributes, resulting in poor accuracy and low efficiency in device identity authentication.

[0005] The present application provides a device authentication method, which is applied to a first authentication server, and the method includes:

[0006] Receiving a device authentication request for a terminal device;

[0007] Acquire a target device attribute corresponding to the first authentication server from an attribute correspondence relationship, and generate a current device fingerprint of the terminal device according to the target device attribute, wherein the attribute correspondence relationship includes a correspondence relationship between each authentication server and different device attributes;

[0008] The current device fingerprint is compared with the historical device fingerprint of the terminal device in the trusted blockchain, and whether the terminal device is authenticated is confirmed based on the comparison result. The historical device fingerprint is generated by a second authentication server and stored in the trusted blockchain.

[0009] Optionally, comparing the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain, and confirming whether the terminal device is authenticated according to the comparison result, includes:

[0010] Obtaining a historical device fingerprint of the terminal device from a trusted blockchain;

[0011] If the similarity between the current device fingerprint and the historical device fingerprint does not meet the preset similarity requirement, confirming that the terminal device authentication fails;

[0012] When the similarity between the current device fingerprint and the historical device fingerprint meets the preset similarity requirement, it is confirmed that the terminal device authentication is passed.

[0013] Optionally, after confirming that the terminal device authentication fails, the method further includes:

[0014] Send a device authentication request for the terminal device to a second authentication server.

[0015] Optionally, after confirming that the terminal device authentication is passed, the method further includes:

[0016] When the current device fingerprint does not exist in the local trusted blockchain, the current device fingerprint is stored in the local trusted blockchain.

[0017] Optionally, after generating the current device fingerprint of the terminal device according to the target device attributes, the method further includes:

[0018] If there is no historical device fingerprint of the terminal device in the trusted blockchain, storing the current device fingerprint in the trusted blockchain;

[0019] Sending a device authentication request for the terminal device to the second authentication server.

[0020] Optionally, the target device attributes include at least: basic device attributes and device environment attributes;

[0021] The step of obtaining, from the terminal device according to the attribute correspondence, the target device attribute corresponding to the first authentication server includes:

[0022] According to the hardware configuration of the terminal device, the basic attributes of the device are obtained, and according to the environment in which the device is located, the device environment attributes are obtained.

[0023] Optionally, after comparing the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain and confirming whether the terminal device has been authenticated according to the comparison result, the method further includes:

[0024] In the trusted blockchain corresponding to each authentication server, when the credibility of the device fingerprint of the terminal device meets the authentication requirements, the device identity of the terminal device is confirmed to be legal.

[0025] The present application embodiment provides a device authentication apparatus, which is applied to a first authentication server, and the device includes:

[0026] A receiving module, configured to receive a device authentication request for a terminal device;

[0027] a generating module configured to obtain a target device attribute corresponding to the first authentication server from an attribute correspondence relationship, and generate a current device fingerprint of the terminal device according to the target device attribute, wherein the attribute correspondence relationship includes a correspondence relationship between each authentication server and different device attributes;

[0028] The authentication module is configured to compare the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain, and confirm whether the terminal device is authenticated based on the comparison result, wherein the historical device fingerprint is generated by a second authentication server and stored in the trusted blockchain.

[0029] Optionally, the authentication module is further configured to:

[0030] Obtaining a historical device fingerprint of the terminal device from a trusted blockchain;

[0031] If the similarity between the current device fingerprint and the historical device fingerprint does not meet the preset similarity requirement, confirming that the terminal device authentication fails;

[0032] When the similarity between the current device fingerprint and the historical device fingerprint meets the preset similarity requirement, it is confirmed that the terminal device authentication is passed.

[0033] Optionally, the authentication module is further configured to:

[0034] Send a device authentication request for the terminal device to a second authentication server.

[0035] Optionally, the authentication module is further configured to:

[0036] When the current device fingerprint does not exist in the local trusted blockchain, the current device fingerprint is stored in the local trusted blockchain.

[0037] Optionally, the generating module is further configured to:

[0038] If there is no historical device fingerprint of the terminal device in the trusted blockchain, storing the current device fingerprint in the trusted blockchain;

[0039] Sending a device authentication request for the terminal device to the second authentication server.

[0040] Optionally, the target device attributes include at least: basic device attributes and device environment attributes;

[0041] The generation module is further configured to:

[0042] According to the hardware configuration of the terminal device, the basic attributes of the device are obtained, and according to the environment in which the device is located, the device environment attributes are obtained.

[0043] Optionally, the authentication module is further configured to:

[0044] In the trusted blockchain corresponding to each authentication server, when the credibility of the device fingerprint of the terminal device meets the authentication requirements, the device identity of the terminal device is confirmed to be legal.

[0045] An embodiment of the present application provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the above-mentioned device authentication method when executed by the processor.

[0046] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the device authentication method as described above are implemented.

[0047] The embodiments of the present application provide a device authentication method, apparatus, electronic device, and computer-readable storage medium. By introducing multiple authentication servers that use different device attributes to generate device fingerprints, the terminal devices connected to the blockchain are collaboratively authenticated. This not only reduces the amount of data required for the authentication server to generate device fingerprints, reduces the amount of data processing required to generate device fingerprints, and improves the efficiency of device fingerprint generation, but also avoids the situation where device fingerprint drift is caused by tampering with device attributes through a trusted blockchain, thereby improving the accuracy of device authentication. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 A flowchart schematically shows a method for authenticating a device in an embodiment of the present application;

[0049] Figure 2 A flowchart schematically illustrating another method for authenticating a device in an embodiment of the present application;

[0050] Figure 3 A logic flow chart of a device authentication method in an embodiment of the present application is schematically shown;

[0051] Figure 4 A schematic diagram schematically illustrates a principle diagram of a device authentication method in an embodiment of the present application;

[0052] Figure 5 The following schematically shows a structural block diagram of a device authentication apparatus in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0054] Figure 1 A flowchart of the steps of a device authentication method provided in an embodiment of the present application is schematically shown. The execution subject of the method can be any electronic device, for example, it can be applied to an application with functions such as information display, information transmission and data processing. The method can be executed by a server or a terminal device of the application. Optionally, the method can be executed by a first authentication server. The method includes:

[0055] Step 101: Receive a device authentication request for a terminal device.

[0056] In the embodiments of the present application, a terminal device refers to an electronic device that can access a blockchain and may have functions such as data transmission, data storage, and data display. The terminal device may be authenticated when it needs to access a blockchain or after it has already accessed a blockchain to ensure the legitimacy of the device that has been connected to the blockchain network and identify malicious behaviors such as tampering with the device information of the terminal device by the user.

[0057] In some embodiments of the present application, after the terminal device accesses the blockchain or has already accessed the blockchain, the terminal device can automatically or periodically send a device authentication request to the authentication server in the blockchain for authenticating the device identity, so as to trigger the authentication server to perform the authentication process for its identity. The first authentication server can be any authentication server in the blockchain, and refers to the destination device to which the terminal device sends the device authentication request. It can be understood that since multiple authentication servers can be set in the blockchain to improve the efficiency of device authentication, the terminal device can send the device authentication request to any authentication server in the blockchain according to the pre-settings, or distribute the device authentication request to any authentication server through an intermediate forwarding device, and the authentication server that receives and is responsible for processing the device authentication request will perform the subsequent device authentication process as the first authentication server.

[0058] Step 102, obtaining target device attributes corresponding to the first authentication server from attribute correspondences, and generating a current device fingerprint of the terminal device according to the target device attributes, wherein the attribute correspondences include correspondences between each authentication server and different device attributes.

[0059] In the embodiment of the present application, the attribute correspondence refers to the correspondence stored in the form of a contract in the blockchain. The attribute correspondence includes the correspondence between different device attributes used for device authentication and each authentication server. The attribute correspondence can be negotiated and determined in advance between the authentication servers through interaction, or it can be set by the user. It can be set according to actual needs and is not limited here. The device fingerprint refers to the device feature or unique device identification used to uniquely identify the device. The device fingerprint can be generated based on all or part of the device attributes. Since there is a correlation between device data, the number of dimensions of the device attributes used will not affect the consistency of the device fingerprint. In other words, the device fingerprint generated using different device attributes of the same terminal device is also the same. For details, refer to the device fingerprint generation method in the relevant technology. As long as the device identity of the terminal device can be identified, it can be applied to the embodiment of the present application and is not limited here.

[0060] In some embodiments of the present application, in order to reduce the amount of data required by each authentication server when generating device fingerprints, and to avoid the device attributes of the user terminal device being tampered with, resulting in fingerprint drift in the device fingerprint generation process of the authentication server, the embodiments of the present application arrange multiple authentication servers in the blockchain, and the device attributes required by each authentication server to generate device fingerprints are distinguished by attribute correspondence, so that the device attributes required by each authentication server to generate device fingerprints are different, which means that the authentication server does not need to use the full amount of device attributes to generate device fingerprints when generating device fingerprints, reducing the amount of data processing required for the authentication server to generate device fingerprints. And because the device attributes required by each authentication server to generate device fingerprints are different, even if some device attributes of the terminal device are tampered with, it will only affect the device fingerprint generation process of some authentication servers, and other authentication servers can still generate device fingerprints normally. This difference in the selection of device attributes for generating device fingerprints between authentication servers can also improve the stability of device authentication in the blockchain.

[0061] Step 103, compare the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain, and confirm whether the terminal device is authenticated based on the comparison result, wherein the historical device fingerprint is generated by the second authentication server and stored in the trusted blockchain.

[0062] In the embodiment of the present application, the current device fingerprint refers to the device fingerprint generated by the first authentication server based on the target device attributes obtained in the current time period, and the historical device fingerprint stored in the trusted blockchain refers to the device fingerprint generated by the first authentication server or the second authentication server other than the first authentication server based on the previously obtained device attributes. It can be seen that the first authentication server and the second authentication server can be the same authentication server or different authentication servers, and the basis for division is the time period for generating the device fingerprint. The trusted blockchain is a node in the blockchain used to store data resources. The data resources stored in the trusted blockchain can be obtained by other nodes and cannot be tampered with by a single blockchain node.

[0063] For example, refer to Figure 2 When the user operates an application with device fingerprint authentication function, the terminal device will send device attributes such as device hardware, operating system, protocol stack, etc. to the authentication server. After receiving the data, the authentication server first determines whether the device is a new device. If it is not a new device, it will compare the similarity between the historical device fingerprint generated based on the existing device information and the current device fingerprint generated based on the device information reported this time to see if it meets the similarity requirements. If the similarity requirements are met, it will broadcast the message that the device fingerprint already exists to other authentication servers. Otherwise, the device attributes are extracted according to the contract and the device fingerprint is generated in combination with the machine learning algorithm. Secondly, the authentication server broadcasts the device fingerprint of this device to the entire network and writes it into the trusted blockchain. After receiving the message, the authentication server receiving the broadcast determines whether it has mutual trust with this authentication service. If it trusts, it writes the device fingerprint into the trusted blockchain according to the contract and broadcasts it to the entire network. Otherwise, the authentication service receiving the broadcast needs to authenticate this device. If the authentication passes, it will write it into the mutual trust blockchain, otherwise it will refuse to write.

[0064] In some embodiments of the present application, if the terminal device has been connected to the blockchain before, it indicates that the terminal device has passed the identity authentication process of the second authentication server, and the second authentication server will store the historical device fingerprint of the terminal device in the trusted blockchain for the first authentication server to obtain when the terminal device is connected again, so that the first authentication server can compare the current device fingerprint generated this time with the historical device fingerprint to authenticate the identity of the terminal device. If the device attributes of the terminal device have not been tampered with, then the comparison similarity between the current device fingerprint and the historical device fingerprint will meet the authentication requirements, and it can be determined that the terminal device has passed the authentication this time. If the device attributes have been tampered with, then the comparison similarity between the current device fingerprint and the historical device fingerprint will not meet the authentication requirements, and it can be determined that the terminal device has failed the authentication this time.

[0065] The embodiment of the present application introduces multiple authentication servers that use different device attributes to generate device fingerprints to collaboratively authenticate the terminal devices connected to the blockchain. This not only reduces the amount of data required for the authentication server to generate device fingerprints, reduces the amount of data processing to generate device fingerprints, and improves the efficiency of device fingerprint generation, but also avoids the situation where device fingerprint drift is caused by tampering with device attributes through a trusted blockchain, thereby improving the accuracy of device authentication.

[0066] Figure 3 A flowchart of a device authentication method provided in an embodiment of the present application is schematically shown, and the method includes:

[0067] Step 201: Receive a device authentication request for a terminal device.

[0068] This step can refer to the detailed description of step 101 and will not be repeated here.

[0069] Step 202, according to the hardware configuration of the terminal device, obtain the basic attributes of the device, and according to the environment in which the device is located, obtain the device environment attributes, and generate the current device fingerprint of the terminal device according to the target device attributes, and the attribute correspondence includes the correspondence between each authentication server and different device attributes.

[0070] In the embodiment of the present application, the basic attributes of the device may refer to but not limited to the hardware configuration of the terminal device, such as the brand, model, manufacturer, device instruction set, processor model, etc., and the device environment attributes may refer to but not limited to the environment-related attributes such as the location environment, network environment, and device environment. The basic attributes of the device obtained based on the hardware configuration of the terminal device can be used to identify whether the hardware configuration of the terminal device has been tampered with, and the current device fingerprint generated based on the device environment attributes can authenticate the legitimacy of the environment currently used by the terminal device, thereby improving the accuracy of device authentication.

[0071] Step 203: If the historical device fingerprint of the terminal device does not exist in the trusted blockchain, the current device fingerprint is stored in the trusted blockchain.

[0072] In an embodiment of the present application, if the terminal device is accessing the blockchain for the first time, the historical device fingerprint of the terminal device will not exist in the trusted blockchain. Therefore, the first authentication server can store the current device fingerprint in the trusted blockchain for further authentication by other authentication servers.

[0073] Step 204: Send a device authentication request for the terminal device to the second authentication server.

[0074] In an embodiment of the present application, the device authentication request is issued by a first authentication server and received and processed by a second authentication server other than the first authentication server. The second authentication server can continue to authenticate the terminal device by executing any device authentication method provided in the present application until all authentication servers complete the device authentication process for the terminal device.

[0075] Step 205, obtaining the historical device fingerprint of the terminal device from the trusted blockchain.

[0076] In the embodiment of the present application, if the terminal device has previously accessed the blockchain, the trusted blockchain of the second authentication server to which the terminal device previously accessed the blockchain will store the historical device fingerprint generated by the second authentication server when it previously accessed the blockchain. It should be noted that if the terminal device previously accessed the blockchain from the first authentication server, the second authentication server and the first authentication server can be the same authentication server, that is, the trusted blockchain corresponding to the first authentication server will store the historical device fingerprint of the terminal device.

[0077] Step 206 , when the similarity between the current device fingerprint and the historical device fingerprint does not meet the preset similarity requirement, confirm that the terminal device authentication fails.

[0078] In an embodiment of the present application, a first authentication server pre-stores an association relationship table between multiple historical device fingerprints generated by the terminal device through different device attributes and the terminal device. Therefore, the similarity between the current device fingerprint and each historical device fingerprint in the table can be confirmed by querying the association relationship table, and the calculated similarity is compared with the similarity threshold. When the similarity between the current device fingerprint and any historical device fingerprint in the table is not greater than the similarity threshold, it is confirmed that the terminal device authentication has failed.

[0079] Step 207: Send a device authentication request for the terminal device to a second authentication server.

[0080] In an embodiment of the present application, in order to avoid inaccurate device authentication due to data fingerprint drift, the first authentication server will continue to broadcast a device authentication request to the second authentication server to further verify the device identity of the terminal device.

[0081] Step 208: If the similarity between the current device fingerprint and the historical device fingerprint meets the preset similarity requirement, confirm that the terminal device authentication is successful.

[0082] In an embodiment of the present application, when the similarity between the current device fingerprint and any historical device fingerprint in the table is greater than the similarity threshold, it is confirmed that the terminal device authentication has failed, indicating that the device attributes of the terminal device have not been tampered with, and the terminal device authentication is confirmed to have passed.

[0083] Step 209: When the current device fingerprint does not exist in the local trusted blockchain, the current device fingerprint is stored in the local trusted blockchain.

[0084] In the embodiment of the present application, the local trusted blockchain refers to a data node for storing shared data maintained locally by the first authentication server. Accordingly, each authentication server connected to the blockchain has its own corresponding local trusted blockchain. Specifically, if the current device fingerprint does not exist in the historical device fingerprint stored in the local trusted blockchain of the first authentication server, the first authentication server updates the historical device fingerprint stored in the local trusted blockchain by storing the current device fingerprint in the local trusted blockchain, so that the terminal device can be extracted by the authentication server to authenticate the terminal device when the terminal device accesses the blockchain later. It should be noted that since the authentication servers will periodically synchronize the historical fingerprint data stored in their respective local trusted blockchains, the historical device fingerprints stored in the local trusted blockchain of the first authentication server may be generated by other authentication servers and then synchronized to the local trusted blockchain of the first authentication server.

[0085] Step 210: In the trusted blockchain corresponding to each authentication server, when the credibility of the device fingerprint of the terminal device meets the authentication requirements, the device identity of the terminal device is confirmed to be legal.

[0086] In an embodiment of the present application, each authentication server will generate its own credibility for the terminal device based on the difference between the generated device fingerprint and the historical device fingerprint. The credibility can be summarized to obtain a total credibility value. When the total credibility value is greater than the credibility threshold, it can be confirmed that the terminal device corresponding to the current device fingerprint is legal, and the terminal device is allowed to access the blockchain.

[0087] For example, refer to Figure 4 In the process of building a mutual-trust blockchain, the consensus algorithm between different authentication services is the consensus algorithm (RPCA, Ripple Protocol Consensus Algorithm). When different authentication servers reach a consensus, the new block is added to the blockchain, and the device fingerprint is also added to it.

[0088] The embodiment of the present application comprehensively determines whether the device identity of the terminal device is legal based on the credibility of each authentication server for the terminal device, thereby avoiding inaccurate device identity authentication due to device attribute fingerprint drift and improving the accuracy of device identity authentication.

[0089] The embodiment of the present application introduces multiple authentication servers that use different device attributes to generate device fingerprints to collaboratively authenticate the terminal devices connected to the blockchain. This not only reduces the amount of data required for the authentication server to generate device fingerprints, reduces the amount of data processing to generate device fingerprints, and improves the efficiency of device fingerprint generation, but also avoids the situation where device fingerprint drift is caused by tampering with device attributes through a trusted blockchain, thereby improving the accuracy of device authentication.

[0090] Figure 5 A device authentication device 30 provided in an embodiment of the present application is schematically shown, which is applied to a first authentication server, and the device includes:

[0091] The receiving module 301 is configured to receive a device authentication request for a terminal device;

[0092] The generating module 302 is configured to obtain the target device attribute corresponding to the first authentication server from the attribute correspondence relationship, and generate the current device fingerprint of the terminal device according to the target device attribute, wherein the attribute correspondence relationship includes the correspondence relationship between each authentication server and different device attributes;

[0093] The authentication module 303 is configured to compare the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain, and confirm whether the terminal device is authenticated based on the comparison result. The historical device fingerprint is generated by the second authentication server and stored in the trusted blockchain.

[0094] Optionally, the authentication module 303 is further configured to:

[0095] Obtaining a historical device fingerprint of the terminal device from a trusted blockchain;

[0096] If the similarity between the current device fingerprint and the historical device fingerprint does not meet the preset similarity requirement, confirming that the terminal device authentication fails;

[0097] When the similarity between the current device fingerprint and the historical device fingerprint meets the preset similarity requirement, it is confirmed that the terminal device authentication is passed.

[0098] Optionally, the authentication module 303 is further configured to:

[0099] Send a device authentication request for the terminal device to a second authentication server.

[0100] Optionally, the authentication module 303 is further configured to:

[0101] When the current device fingerprint does not exist in the local trusted blockchain, the current device fingerprint is stored in the local trusted blockchain.

[0102] Optionally, the generating module 302 is further configured to:

[0103] If there is no historical device fingerprint of the terminal device in the trusted blockchain, storing the current device fingerprint in the trusted blockchain;

[0104] Sending a device authentication request for the terminal device to the second authentication server.

[0105] Optionally, the target device attributes include at least: basic device attributes and device environment attributes;

[0106] The generating module 302 is further configured to:

[0107] According to the hardware configuration of the terminal device, the basic attributes of the device are obtained, and according to the environment in which the device is located, the device environment attributes are obtained.

[0108] Optionally, the authentication module 303 is further configured to:

[0109] In the trusted blockchain corresponding to each authentication server, when the credibility of the device fingerprint of the terminal device meets the authentication requirements, the device identity of the terminal device is confirmed to be legal.

[0110] The embodiment of the present application introduces multiple authentication servers that use different device attributes to generate device fingerprints to collaboratively authenticate the terminal devices connected to the blockchain. This not only reduces the amount of data required for the authentication server to generate device fingerprints, reduces the amount of data processing to generate device fingerprints, and improves the efficiency of device fingerprint generation, but also avoids the situation where device fingerprint drift is caused by tampering with device attributes through a trusted blockchain, thereby improving the accuracy of device authentication.

[0111] An embodiment of the present application provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the above-mentioned device authentication method when executed by the processor.

[0112] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the device authentication method as described above are implemented.

[0113] The embodiment of the present application adjusts the index content in the index bar by adapting to the layout size of the list control and the navigation control in the navigation interface, so that the index content can still be fully displayed when the layout size of the navigation control and the list control changes.

[0114] Preferably, an embodiment of the present application also provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned information processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0115] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, each process of the above-mentioned information processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0116] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0117] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0118] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0119] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the present application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0120] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0121] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0122] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0123] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0124] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0125] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A device authentication method, characterized in that: Applied to a first authentication server, the method comprises: Receiving a device authentication request for a terminal device; Acquire a target device attribute corresponding to the first authentication server from an attribute correspondence relationship, and generate a current device fingerprint of the terminal device according to the target device attribute, wherein the attribute correspondence relationship includes a correspondence relationship between each authentication server and different device attributes; The current device fingerprint is compared with the historical device fingerprint of the terminal device in the trusted blockchain, and whether the terminal device is authenticated is confirmed according to the comparison result, including: obtaining the historical device fingerprint of the terminal device from the trusted blockchain, and confirming that the terminal device authentication is not passed when the similarity between the current device fingerprint and the historical device fingerprint does not meet the preset similarity requirement, and confirming that the terminal device authentication is passed when the similarity between the current device fingerprint and the historical device fingerprint meets the preset similarity requirement; the historical device fingerprint is generated by a second authentication server and stored in the trusted blockchain, and the historical device fingerprint is a device fingerprint generated by a second authentication server other than the first authentication server based on the acquired device attributes.

2. The method according to claim 1, characterized in that After confirming that the terminal device authentication fails, the method further includes: Send a device authentication request for the terminal device to a second authentication server.

3. The method according to claim 1, characterized in that After confirming that the terminal device has passed authentication, the method further includes: When the current device fingerprint does not exist in the local trusted blockchain, the current device fingerprint is stored in the local trusted blockchain.

4. The method according to claim 1, characterized in that: After generating the current device fingerprint of the terminal device according to the target device attributes, the method further includes: If there is no historical device fingerprint of the terminal device in the trusted blockchain, storing the current device fingerprint in the trusted blockchain; Sending a device authentication request for the terminal device to the second authentication server.

5. The method according to claim 1, characterized in that: The target device attributes include at least: basic device attributes and device environment attributes; The acquiring the target device attribute corresponding to the first authentication server from the attribute correspondence relationship includes: According to the hardware configuration of the terminal device, the basic attributes of the device are obtained, and according to the environment in which the device is located, the device environment attributes are obtained.

6. The method according to claim 1, characterized in that After comparing the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain and confirming whether the terminal device has been authenticated according to the comparison result, the method further includes: In the trusted blockchain corresponding to each authentication server, when the credibility of the device fingerprint of the terminal device meets the authentication requirements, the device identity of the terminal device is confirmed to be legal.

7. A device authentication apparatus, characterized in that: Applied to a first authentication server, the device comprises: A receiving module, configured to receive a device authentication request for a terminal device; a generating module configured to obtain a target device attribute corresponding to the first authentication server from an attribute correspondence relationship, and generate a current device fingerprint of the terminal device according to the target device attribute, wherein the attribute correspondence relationship includes a correspondence relationship between each authentication server and different device attributes; The authentication module is configured to compare the current device fingerprint with the historical device fingerprint of the terminal device in the trusted blockchain, and confirm whether the terminal device has been authenticated based on the comparison result. The authentication module is also configured to: obtain the historical device fingerprint of the terminal device from the trusted blockchain, and if the similarity between the current device fingerprint and the historical device fingerprint does not meet the preset similarity requirement, confirm that the terminal device has been authenticated; if the similarity between the current device fingerprint and the historical device fingerprint meets the preset similarity requirement, confirm that the terminal device has been authenticated; the historical device fingerprint is generated by a second authentication server and stored in the trusted blockchain, and the historical device fingerprint is a device fingerprint generated by a second authentication server other than the first authentication server based on the acquired device attributes.

8. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the device authentication method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the device authentication method according to any one of claims 1 to 6 are implemented.

Images