Identity verification method and device, computer equipment and computer readable storage medium

Abstract

The invention relates to an identity verification method and device, computer equipment and a computer readable storage medium. The method comprises the following steps: receiving a data reporting request sent by a request end, wherein the data reporting request comprises a request password; determining a corresponding verification key and a public parameter according to the data reporting request; wherein the public parameters comprise a plurality of hash functions and verification parameters, and the verification key is generated according to at least part of the plurality of hash functions and the verification parameters; and determining an identity verification result of the request end according to the request password, the verification key and the public parameter. By adopting the method, the security of data transmission between the request end and the verification end can be ensured.

Description

Technical Field

[0001] The present application relates to the field of network security technology, and in particular to an identity authentication method, apparatus, computer device and computer-readable storage medium. Background Art

[0002] With the advent of the information age and the comprehensive development of information technology, various services based on network information systems have flourished. However, the security issues brought about by massive service requests have become increasingly prominent, especially in distributed networks. How to ensure secure data transmission between the request end and the verification end is a problem that needs to be solved urgently. Summary of the invention

[0003] Based on this, it is necessary to provide an identity authentication method, device, computer equipment and computer-readable storage medium that can ensure the security of data transmission in response to the above technical problems.

[0004] In a first aspect, the present application proposes an identity authentication method, which is applied to a verification end; the method comprises:

[0005] Receiving a data reporting request sent by a requesting end, wherein the data reporting request includes a request password;

[0006] Determine a corresponding verification key and public parameters according to the data reporting request; wherein the public parameters include multiple hash functions and verification parameters, and the verification key is generated according to at least part of the multiple hash functions and the verification parameters;

[0007] The identity authentication result of the requesting end is determined according to the request password, the verification key and the public parameter.

[0008] In one embodiment, the verification parameters include a time interval, an initial time, and a hash function sequence, and determining the identity authentication result of the requesting end according to the request password, the verification key, and the public parameters includes:

[0009] Determine the number of reports of the request end corresponding to the data reporting request according to the reception time of the data reporting request, the time interval and the initial time;

[0010] The identity authentication result of the requesting end is determined according to the request password, the reporting times, the hash function sequence, the multiple hash functions and the verification key.

[0011] In one embodiment, determining the identity authentication result of the requesting end according to the request password, the reporting number, the hash function order, the plurality of hash functions and the verification key includes:

[0012] Determine a corresponding target hash function from the plurality of hash functions according to the number of reports and the order of the hash functions;

[0013] The identity authentication result of the requesting end is determined according to the request password, the verification key, the verification parameter and the target hash function.

[0014] In one embodiment, determining the identity authentication result of the requesting end according to the request password, the verification key, the verification parameter and the target hash function includes:

[0015] Hash the request password according to the verification parameter and the target hash function, and generate a request key;

[0016] The identity authentication result of the requesting end is determined according to the request key and the verification key.

[0017] In one embodiment, the verification parameters include a target hash chain length, an identification code of the requesting end, and a preset random key, and the hashing of the request password according to the verification parameters and the target hash function to generate a request key includes:

[0018] The request password is hashed according to the number of reports, the identification code of the requesting end, the time interval, the initial time, the target hash chain length, the preset random key and the target hash function, and a request key is generated.

[0019] In one embodiment, the data reporting request also includes data to be reported, and the method further includes:

[0020] If the identity authentication result of the requesting end is successful, the data to be reported is saved, and the verification key is updated according to the request password;

[0021] When the identity authentication result of the requesting end is a verification failure, the data to be reported is discarded.

[0022] In a second aspect, the present application provides an identity authentication device, which is applied to a verification end; the device comprises:

[0023] A first receiving module, configured to receive a data reporting request sent by a requesting end, wherein the data reporting request includes a request password;

[0024] A first determination module, configured to determine a corresponding verification key and a public parameter according to the data reporting request; wherein the public parameter includes a plurality of hash functions and a verification parameter, and the verification key is generated according to at least part of the plurality of hash functions and the verification parameter;

[0025] The second determination module is used to determine the identity authentication result of the requesting end according to the request password, the verification key and the public parameter.

[0026] In a third aspect, the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the identity authentication method described in any of the above embodiments when executing the computer program.

[0027] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the identity authentication method described in any of the above embodiments are implemented.

[0028] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the identity authentication method described in any of the above embodiments.

[0029] The above-mentioned identity authentication method, apparatus, computer device and computer-readable storage medium include that after the verification end receives the data reporting request sent by the requesting end, it first determines the verification key and public parameters corresponding to the data reporting request based on the data reporting request, the public parameters include multiple hash functions and verification parameters, and the verification key is generated based on at least some of the multiple hash functions and verification parameters. Afterwards, the verification end can determine whether the verification key can be obtained based on the request password, multiple hash functions and pre-stored verification parameters based on the request password and pre-stored verification parameters in the data reporting request, and then determine the identity authentication result of the requesting end. The identity authentication method of the present application generates a verification key by using at least some of the hash functions among multiple hash functions, that is, each hash function will randomly participate in the calculation when generating a verification key, so as to ensure the randomness of the verification key, improve the difficulty of cracking the verification key, avoid attackers from cracking and forging the key, and ensure the security of data transmission. In addition, after receiving the request password, the verification end of the present application does not directly compare the request password with the verification key to determine the identity of the request end, but needs to combine the hash functions in the public parameters and the pre-stored verification parameters to see whether the verification key can be obtained. Since the hash calculation is unidirectional, even if the verification key of the verification end is cracked, the attacker cannot know the current correct request password, thereby further improving the security of data transmission. Through the identity authentication method of the present application, it is possible to ensure that the verification end accurately authenticates the identity of the request end, and then the verification end only accepts data sent by the request end that has passed the identity authentication, ensuring that the data can be transmitted safely. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0031] FIG1 is a schematic diagram of a flow chart of an identity authentication method in an embodiment;

[0032] FIG2 is a schematic diagram of a flow chart of step S103 in one embodiment;

[0033] FIG3 is a schematic diagram of a flow chart of step S202 in one embodiment;

[0034] FIG4 is a schematic diagram of a flow chart of step S302 in one embodiment;

[0035] FIG5 is a schematic diagram of a flow chart of an identity authentication method in another embodiment;

[0036] FIG6 is a block diagram of an identity verification device according to an embodiment;

[0037] FIG. 7 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0039] As an emerging technology, cloud computing greatly simplifies the access process of network and computing resources (such as storage and data management services) by providing them on demand, and significantly enhances the overall performance and functionality of the system. Among the various cloud computing architectures, distributed cloud is an important implementation form. Distributed cloud further enhances the advantages of cloud computing by distributing computing, storage, and network resources across multiple geographic locations and data centers instead of concentrating them in a single physical location. In this way, distributed cloud can not only provide higher reliability and scalability, but also significantly improve system performance to meet the needs of different regions and application scenarios.

[0040] Despite the many advantages of distributed cloud, cloud service providers still face a series of security challenges. In recent years, many security issues have been exposed in the field of cloud computing, such as challenges in availability, data confidentiality, data integrity, and permission control. In addition, the Internet, as the main way to access cloud services, has also become a major threat source for infecting cloud systems and resources. These security issues also exist in distributed cloud environments. In particular, these security challenges are particularly significant in the distributed cloud delivery billing system. Subclusters in distributed clouds may come from paid clusters of different providers or local IDC's own clusters. Therefore, in the billing system, it is crucial to verify whether the delivery data comes from a legitimate subcluster.

[0041] In an exemplary embodiment, please refer to FIG. 1 , the present application proposes an identity authentication method, which is applied to a verification end; the identity authentication method includes steps S101 to S103 .

[0042] S101: receiving a data reporting request sent by a requesting end, where the data reporting request includes a request password.

[0043] In the application, the verification end can be understood as a distributed cloud, and the requesting end can be understood as a subcluster corresponding to the distributed cloud. The subcluster needs to send billing data to the distributed cloud regularly. In order to ensure the legitimacy and security of technical data, the distributed cloud needs to authenticate the subcluster that sends the billing data. Therefore, when the subcluster needs to report billing data to the distributed cloud, a request password can be carried in the billing data, so that the distributed cloud can verify whether the identity of the subcluster is legal based on the request password sent by the subcluster, and then decide whether to accept or discard the billing data reported by the subcluster.

[0044] S102: Determine a corresponding verification key and public parameters according to the data reporting request, wherein the public parameters include multiple hash functions and verification parameters, and the verification key is generated according to at least part of the multiple hash functions and the verification parameters.

[0045] In this embodiment, before a sub-cluster sends a data reporting request to a distributed cloud, the distributed cloud may store a verification key and public parameters for verifying whether the identity of the sub-cluster is legitimate. The public parameters may be sent to the distributed cloud by the sub-cluster in advance through a secure channel, wherein the public parameters include multiple hash functions and verification parameters, the verification key is generated based on at least some of the multiple hash functions and the verification parameters, and the request password sent by the sub-cluster is also generated based on at least some of the multiple hash functions and the verification parameters, but the verification key is different from the request password.

[0046] S103: Determine the identity authentication result of the requesting end according to the request password, the verification key and the public parameters.

[0047] Since the verification key is generated based on at least some of the hash functions and the verification parameters in the multiple hash functions, the request password sent by the sub-cluster is also generated based on at least some of the hash functions and the verification parameters in the multiple hash functions. The difference between the verification key and the request password is that they have different hash times, and the hash times of the request password are less than the hash times of the verification key. Therefore, the distributed cloud can perform hash calculation on the request password according to the public parameters, and compare the calculation result with the verification key to determine the identity authentication result of the requesting end. Among them, after a verification is passed, the verification key in the distributed cloud will be updated according to the request key this time.

[0048] It can be understood that the hash algorithm is irreversible. The result of the first hash calculation, that is, the first hash value, is generated according to the corresponding hash function and random number. Each subsequent hash value is generated according to the previous hash value and the corresponding hash function, and it is almost impossible to deduce the previous hash value based on one hash value. Therefore, even if the verification key in the distributed cloud is cracked, the adversary / attacker cannot obtain the request password of the sub-cluster based on the verification key, and it is difficult to disguise as a sub-cluster to attack the distributed cloud, thereby ensuring that the verification end accurately authenticates the identity of the request end, and then the verification end only accepts data sent by the request end that has passed the identity authentication, ensuring that the data can be transmitted securely.

[0049] The above-mentioned identity authentication method includes that after the verification end receives the data reporting request sent by the requesting end, it first determines the verification key and public parameters corresponding to the data reporting request based on the data reporting request, the public parameters include multiple hash functions and verification parameters, and the verification key is generated based on at least some of the multiple hash functions and verification parameters. Afterwards, the verification end can determine whether the verification key can be obtained based on the request password, multiple hash functions and pre-stored verification parameters based on the request password and pre-stored verification parameters in the data reporting request, and then determine the identity authentication result of the requesting end. The identity authentication method of the present application generates a verification key by using at least some of the hash functions among multiple hash functions, that is, each hash function will randomly participate in the calculation when generating a verification key, so as to ensure the randomness of the verification key, improve the difficulty of cracking the verification key, avoid attackers from cracking and forging the key, and ensure the security of data transmission. In addition, after receiving the request password, the verification end of the present application does not directly compare the request password with the verification key to determine the identity of the request end, but needs to combine the hash functions in the public parameters and the pre-stored verification parameters to see whether the verification key can be obtained. Since the hash calculation is unidirectional, even if the verification key of the verification end is cracked, the attacker cannot know the current correct request password, thereby further improving the security of data transmission. Through the identity authentication method of the present application, it is possible to ensure that the verification end accurately authenticates the identity of the request end, and then the verification end only accepts data sent by the request end that has passed the identity authentication, ensuring that the data can be transmitted safely.

[0050] In an exemplary embodiment, the verification parameters include a time interval, an initial time, and a hash function sequence, please refer to FIG. 2 , step S103 , determining the identity authentication result of the requesting end according to the request password, the verification key, and the public parameters, including steps S201 and S202 .

[0051] S201: Determine the number of reports of the requesting end corresponding to the data reporting request according to the receiving time, time interval and initial time of the data reporting request.

[0052] In the application, when using the identity authentication method of the present application, the distributed cloud and sub-cluster need to be initialized first: the sub-cluster determines the hash functions, hash function order, time interval between two adjacent data reports of the sub-cluster, target hash chain length and other parameters to be used when reporting data in this stage. Assuming that the target hash chain length is m, the sub-cluster first randomly determines a value x, and performs m hash calculations on the random number x according to the parameters such as the hash function and the hash function order to obtain the initial verification key, and records the generation time of the initial verification key as the initial time. After that, the sub-cluster can send the initial verification key and public parameters such as the hash function, time interval, initial time and hash function order to the distributed cloud, and the distributed cloud accepts and saves the initial verification key and public parameters. In this way, the initialization processing of the distributed cloud and sub-cluster is completed. In this stage, each time the identity authentication of the sub-cluster is passed, the distributed cloud updates the verification key according to the request password reported by the sub-cluster. In addition, when this stage is over, the sub-cluster can change the hash function, and / or the order of the hash function, and / or the random number again to start the next stage of identity authentication.

[0053] In this embodiment, when the distributed cloud receives a data reporting request, it can first determine the number of times the sub-cluster has requested to report data in this stage, that is, the number of reports of the sub-cluster, based on the reception time of the data reporting request and the time interval and initial time recorded in the pre-stored public parameters.

[0054] S202: Determine the identity authentication result of the requesting end according to the request password, the number of reports, the hash function order, the multiple hash functions and the verification key.

[0055] After determining the number of reports of the sub-cluster, the distributed cloud can perform hash calculation on the request password based on the number of reports of the sub-cluster, combined with the request password, the number of reports, the hash function order, and multiple hash functions, and then determine the identity authentication result of the requesting end based on the hash calculation result and the verification key.

[0056] In an exemplary embodiment, please refer to FIG. 3 , step S202 , determining the identity authentication result of the requesting end according to the request password, the number of reports, the hash function order, multiple hash functions and the verification key, including steps S301 and S302 .

[0057] S301: Determine a corresponding target hash function from multiple hash functions according to the number of reports and the order of the hash functions.

[0058] It can be understood that the distributed cloud can find the hash function order according to the current reporting times of the sub-clusters, thereby determining the target hash function from multiple hash functions, so as to perform hash calculation on the requested password according to the target hash function.

[0059] S302: Determine the identity authentication result of the requesting end according to the request password, the verification key, the verification parameter and the target hash function.

[0060] As described above, the distributed cloud can perform hash calculation on the requested password according to the target hash function and verification parameters, and compare the calculated result with the verification key. If the calculated result is consistent with the verification key, it is judged that the subcluster verification has passed, and the distributed cloud can save the billing data reported by this subcluster; if the calculated result is inconsistent with the verification key, it is judged that the subcluster verification has failed, and the distributed cloud discards the billing data reported by this subcluster.

[0061] In an exemplary embodiment, please refer to FIG. 4 , step S302 , determining the identity authentication result of the requesting end according to the request password, the verification key, the verification parameter and the target hash function, includes steps S401 and S402 .

[0062] S401: Perform hash processing on the request password according to the verification parameters and the target hash function, and generate a request key.

[0063] In this embodiment, after the distributed cloud determines the target hash function from multiple hash functions according to the current reporting times of the sub-cluster, it can perform hash calculation on the request password according to the verification parameters and the target hash function. In one example, assuming that the target hash chain length is m, before the sub-cluster reports the billing data to the distributed cloud for the first time in this stage, the distributed cloud has stored the verification key F(m). When the sub-cluster reports the billing data to the distributed cloud for the first time in this stage, the sub-cluster performs m-1 hash calculations on the random number x according to the parameters such as each hash function and the hash function order to obtain the request password F(m-1). After the distributed cloud receives the request password F(m-1), it determines the target hash function from multiple hash functions according to the current reporting times of the sub-cluster. The target hash function is the hash function required for the mth hash calculation found according to the hash function order. After that, the distributed cloud performs a hash calculation on the request password F(m-1) according to the verification parameters and the target hash function to obtain the request key.

[0064] S402: Determine the identity authentication result of the requesting end according to the request key and the verification key.

[0065] It can be understood that the distributed cloud compares the calculated request key with the verification key. If the request key and the verification key are consistent, the subcluster verification is judged to be successful; if the request key and the verification key are inconsistent, the subcluster verification is judged to have failed.

[0066] In an exemplary embodiment, the verification parameters include a target hash chain length, an identification code of the requesting end, and a preset random key. Step S401, hashing the request password according to the verification parameters and the target hash function, and generating a request key, includes the steps of hashing the request password according to the number of reports, the identification code of the requesting end, the time interval, the initial time, the target hash chain length, the preset random key, and the target hash function, and generating a request key.

[0067] In the application, the following formula can be used for hash calculation:

[0068]

[0069] Among them, H i (x) is the result of the i-th hash calculation, i represents the number of hash calculations, h k represents the hash function used for the i-th hash calculation, x is a random number, It represents the hash value obtained by using the hash function h0 to hash the random number x. Indicates the use of hash function h1 for The hash value obtained by hash calculation, 0<i≤m.

[0070] For a single hash calculation, the following formula can be used:

[0071]

[0072] Hash is the hash function used for the i-th hash calculation, id is the identification code of the requesting end, and t init is the initial time, m is the target hash chain length, I is the time interval, H i-1 (x) is the result of the i-1th hash calculation, and sk is the preset random key.

[0073] After the distributed cloud determines the target hash function from multiple hash functions based on the current number of reports of the sub-cluster, it can perform one-side hash calculation on the request password based on the above formula according to the number of reports, the identification code of the requesting end, the time interval, the initial time, the target hash chain length, the preset random key and the target hash function, and generate a request key.

[0074] In an exemplary embodiment, referring to FIG. 5 , the data reporting request further includes data to be reported, and the identity authentication method further includes step S501 and step S502 .

[0075] S501: When the identity authentication result of the requesting end is successful, the data to be reported is saved, and the verification key is updated according to the request password.

[0076] In the application, assuming that the verification key is F(n) and the request password is F(n-1), the distributed cloud generates a request key after performing a hash calculation on the request password F(n-1) based on the verification parameters and the target hash function. If the request key is equal to the verification key F(n), the authentication result is successful. The distributed cloud waits for the data to be reported and updates the verification key to F(n-1) for the next authentication.

[0077] S502: When the identity authentication result of the requesting end is a verification failure, the data to be reported is discarded.

[0078] If the request key is not equal to the verification key F(n), the identity authentication result is verification failure, and the distributed cloud discards the data to be reported.

[0079] In a detailed embodiment, after the data reporting process of the sub-cluster in the previous stage is completed, the sub-cluster determines the hash functions to be used in the data reporting in this stage, the hash function order o, the time interval I between two adjacent data reports of the sub-cluster, the target hash chain length, the preset random key sk, and the identification code id of the requesting end.

[0080] Assume that the target hash chain length is m=10, the hash functions used are SHA-3-128 and BLAEK3-256, and the hash function order is o={h0=SHA-3-128, h1=BLAEK3-256, h2=BLAEK3-256, h3=SHA-3-128}. The subcluster first determines a random number x, and performs 10 hash calculations on the random number x according to the hash function order and the other parameters mentioned above to obtain the initial verification key F10, and records the generation time of the initial verification key as the initial time t init After that, the sub-cluster can send the verification key F10 and public parameters such as each hash function, time interval, initial time and hash function sequence to the distributed cloud.

[0081] The subcluster reports billing data to the distributed cloud once every time interval I. When the subcluster reports billing data to the distributed cloud for the first time, the subcluster performs 9 hash calculations on the random number x according to the hash function sequence and the other parameters mentioned above to obtain the request password F9. The subcluster sends the request password F9 and the data to be reported to the distributed cloud. After receiving the request password F9, the distributed cloud determines that the subcluster is requesting to report data for the first time based on the receiving time of the data reporting request (the time when the request password F9 is received), the time interval and the initial time. After that, the distributed cloud determines the target hash function to be used for the 10th hash calculation from SHA-3-128 and BLAEK3-256 according to the hash function sequence. The target hash function this time is BLAEK3-256. The distributed cloud performs a hash calculation on the request password F9 according to the target hash function BLAEK3-256 and other parameters to obtain the request password. If the request password is equal to the verification key F10, the verification is successful, and the distributed cloud saves the data to be reported and updates the verification key to F9.

[0082] When the sub-cluster reports the billing data to the distributed cloud for the second time, the sub-cluster performs 8 hash calculations on the random number x according to the hash function sequence and the above other parameters to obtain the request password F8. The sub-cluster sends the request password F8 and the data to be reported to the distributed cloud. After receiving the request password F8, the distributed cloud determines that the sub-cluster is requesting to report data for the second time according to the receiving time of the data reporting request (the time when the request password F8 is received), the time interval and the initial time. After that, the distributed cloud determines the target hash function to be used for the 9th hash calculation from SHA-3-128 and BLAEK3-256 according to the hash function sequence. The target hash function this time is SHA-3-128. The distributed cloud performs a hash calculation on the request password F8 according to the target hash function SHA-3-128 and other parameters to obtain the request password. If the request password is equal to the verification key F9, the verification is passed, and the distributed cloud saves the data to be reported and updates the verification key to F8. ... This cycle is repeated until 10 identity authentications are completed. Afterwards, the sub-cluster can only change the random number x and then initialize the distributed cloud so as to perform identity authentication when receiving the data to be reported later.

[0083] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0084] Based on the same inventive concept, the embodiment of the present application also provides an identity authentication device for implementing the identity authentication method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more identity authentication device embodiments provided below can refer to the limitations on the identity authentication method above, and will not be repeated here.

[0085] In an exemplary embodiment, as shown in FIG6 , an identity authentication device is provided, including: a first receiving module 601, a first determining module 602, and a second determining module 603, wherein:

[0086] The first receiving module 601 is used to receive a data reporting request sent by a requesting end, where the data reporting request includes a request password.

[0087] The first determination module 602 is used to determine the corresponding verification key and public parameters according to the data reporting request; wherein the public parameters include multiple hash functions and verification parameters, and the verification key is generated according to at least part of the multiple hash functions and the verification parameters.

[0088] The second determination module 602 is used to determine the identity authentication result of the requesting end according to the request password, the verification key and the public parameters.

[0089] In one embodiment, the verification parameters include a time interval, an initial time, and a hash function sequence, and the second determination module 602 includes:

[0090] The first determination submodule is used to determine the number of reports of the request end corresponding to the data reporting request according to the receiving time, time interval and initial time of the data reporting request.

[0091] The second determination submodule is used to determine the identity authentication result of the requesting end according to the request password, the number of reports, the hash function sequence, the multiple hash functions and the verification key.

[0092] In one embodiment, the second determining submodule includes:

[0093] The first determining unit is used to determine a corresponding target hash function from multiple hash functions according to the number of reports and the order of the hash functions.

[0094] The second determining unit is used to determine the identity authentication result of the requesting end according to the request password, the verification key, the verification parameter and the target hash function.

[0095] In one embodiment, the second determining unit includes:

[0096] The first determination subunit is used to perform hash processing on the request password according to the verification parameter and the target hash function, and generate a request key.

[0097] The second determining subunit is used to determine the identity authentication result of the requesting end according to the request key and the verification key.

[0098] In one embodiment, the data reporting request further includes data to be reported, and the identity verification device further includes:

[0099] The first execution module is used to save the data to be reported and update the verification key according to the request password when the identity authentication result of the requesting end is successful.

[0100] The second execution module is used to discard the data to be reported when the identity authentication result of the requesting end is a verification failure.

[0101] Each module in the above identity authentication device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0102] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps of the identity authentication method described in any of the above embodiments are implemented.

[0103] The computer device may be a terminal, and its internal structure diagram may be shown in FIG7. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, the memory, and the input / output interface are connected via a system bus, and the communication interface, the display unit, and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, an identity authentication method is implemented. The display unit of the computer device is used to form a visually visible picture, which may be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0104] Those skilled in the art will understand that the structure shown in FIG. 7 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0105] In an exemplary embodiment, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the identity authentication method described in any of the above embodiments are implemented.

[0106] In an exemplary embodiment, the present application provides a computer program product, including a computer program, which implements the steps of the identity authentication method described in any of the above embodiments when executed by a processor.

[0107] 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, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0108] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0109] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0110] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. An identity authentication method, characterized in that: Applied to the verification end; the method comprises: Receiving a data reporting request sent by a requesting end, wherein the data reporting request includes a request password; Determine a corresponding verification key and public parameters according to the data reporting request; wherein the public parameters include multiple hash functions and verification parameters, and the verification key is generated according to at least part of the multiple hash functions and the verification parameters; The identity authentication result of the requesting end is determined according to the request password, the verification key and the public parameter.

2. The identity authentication method according to claim 1, characterized in that: The verification parameters include a time interval, an initial time, and a hash function sequence, and determining the identity authentication result of the requesting end according to the request password, the verification key, and the public parameters includes: Determine the number of reports of the request end corresponding to the data reporting request according to the receiving time of the data reporting request, the time interval and the initial time; The identity authentication result of the requesting end is determined according to the request password, the reporting times, the hash function sequence, the multiple hash functions and the verification key.

3. The identity authentication method according to claim 2, characterized in that: The determining the identity authentication result of the requesting end according to the request password, the reporting number, the hash function order, the plurality of hash functions and the verification key comprises: Determine a corresponding target hash function from the plurality of hash functions according to the number of reports and the order of the hash functions; The identity authentication result of the requesting end is determined according to the request password, the verification key, the verification parameter and the target hash function.

4. The identity authentication method according to claim 3, characterized in that: The determining the identity authentication result of the requesting end according to the request password, the verification key, the verification parameter and the target hash function comprises: Hash the request password according to the verification parameter and the target hash function, and generate a request key; The identity authentication result of the requesting end is determined according to the request key and the verification key.

5. The identity authentication method according to claim 4, characterized in that: The verification parameters include a target hash chain length, an identification code of the requesting end, and a preset random key, and the request password is hashed according to the verification parameters and the target hash function to generate a request key, including: The request password is hashed according to the number of reports, the identification code of the requesting end, the time interval, the initial time, the target hash chain length, the preset random key and the target hash function, and a request key is generated.

6. The identity authentication method according to claim 1, characterized in that: The data reporting request also includes data to be reported, and the method further includes: If the identity authentication result of the requesting end is successful, the data to be reported is saved, and the verification key is updated according to the request password; When the identity authentication result of the requesting end is a verification failure, the data to be reported is discarded.

7. An identity verification device, characterized in that: Applied to the verification end; the device comprises: A first receiving module, configured to receive a data reporting request sent by a requesting end, wherein the data reporting request includes a request password; A first determination module, configured to determine a corresponding verification key and a public parameter according to the data reporting request; wherein the public parameter includes a plurality of hash functions and a verification parameter, and the verification key is generated according to at least part of the plurality of hash functions and the verification parameter; The second determination module is used to determine the identity authentication result of the requesting end according to the request password, the verification key and the public parameter.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images