Multi-device assistive identity verification method and system
View Patent ↗The present disclosure provides a multi-device assistive identity verification method and system. The method includes: receiving an identity key allocation request and an identity key sharing request of a user; and allocating and storing an identity key, and sending the identity key to the user and a sharer. The method further includes: when a transaction request of the user is received, inviting the user and the sharer to assist in confirmation, and comparing tokens to perform identity verification.
1 . A multi-device assistive identity verification method, wherein the method comprises:
receiving an identity key allocation request and an identity key sharing request of a user;
allocating, in response to the identity key allocation request, an identity key for the user, and storing the identity key in a server, wherein the allocated identity key is bound to a user identifier and a device identifier of the user and a user identifier and a device identifier of a sharer, to form a contract;
sending the identity key to the user and the sharer;
receiving a transaction request of the user, and inviting, based on the transaction request, the user and the sharer to send confirmation;
in response to the confirmation of the user and the sharer, separately calculating a first token of the user and a second token of the sharer based on a time-based one-time password (TOTP) algorithm, the identity key and a current timestamp;
comparing the first token and the second token;
in response to determining that the first token and the second token are the same, obtaining a third token calculated by a server;
comparing the first token and the third token; and
returning an identity verification result based on the comparison of the first token and the third token.
2 . The method according to claim 1 , wherein the allocated identity key is stored on a blockchain in an encrypted manner.
3 . The method according to claim 2 , wherein inviting, based on the transaction request, the user and the sharer to send confirmation further comprises:
obtaining a corresponding identity key from the blockchain based on the transaction request and the user identifier and the device identifier of the user; and
inviting the user and the sharer bound to the obtained identity key to send the confirmation.
4 . The method according to claim 1 , wherein the third token calculated in the server is calculated in the server based on an identity key obtained from a blockchain.
5 . The method according to claim 1 , further comprising:
in response to that the transaction request of the user is received, performing password verification, SMS message verification, or biometric verification before inviting the user and the sharer to send confirmation.
6 . A non-transitory computer-readable storage medium storing instructions which when executed by a processor, cause the processor to:
receive an identity key allocation request and an identity key sharing request of a user;
allocate, in response to the identity key allocation request, an identity key for the user, and store the identity key in a server, wherein the allocated identity key is bound to a user identifier and a device identifier of the user and a user identifier and a device identifier of a sharer, to form a contract;
send the identity key to the user and the sharer;
receive a transaction request of the user, and inviting, based on the transaction request, the user and the sharer to send confirmation;
in response to the confirmation of the user and the sharer, separately calculate a first token of the user and a second token of the sharer based on a time-based one-time password (TOTP) algorithm, the identity key and a current timestamp;
compare the first token and the second token;
in response to determining that the first token and the second token are the same, obtain a third token calculated by a server;
compare the first token and the third token; and
return an identity verification result based on the comparison of the first token and the third token.
7 . The non-transitory computer-readable storage medium according to claim 6 , wherein the allocated identity key is stored on a blockchain in an encrypted manner.
8 . The non-transitory computer-readable storage medium according to claim 7 , wherein the processor being caused to invite, based on the transaction request, the user and the sharer to send confirmation further comprises being caused to:
obtain a corresponding identity key from the blockchain based on the transaction request and the user identifier and the device identifier of the user; and
invite the user and the sharer bound to the obtained identity key to send the confirmation.
9 . The non-transitory computer-readable storage medium according to claim 6 , wherein the third token calculated in the server is calculated in the server based on an identity key obtained from a blockchain.
10 . The non-transitory computer-readable storage medium according to claim 6 , wherein the processor further comprises being caused to:
in response to that the transaction request of the user is received, perform password verification, SMS message verification, or biometric verification before inviting the user and the sharer to send confirmation.
11 . A computing device, comprising a memory and a processor, wherein the memory stores executable code, and wherein the processor is configured to execute the executable code to cause the computing device to:
receive an identity key allocation request and an identity key sharing request of a user;
allocate, in response to the identity key allocation request, an identity key for the user, and store the identity key in a server, wherein the allocated identity key is bound to a user identifier and a device identifier of the user and a user identifier and a device identifier of a sharer, to form a contract;
send the identity key to the user and the sharer;
receive a transaction request of the user, and inviting, based on the transaction request, the user and the sharer to send confirmation;
in response to the confirmation of the user and the sharer, separately calculate a first token of the user and a second token of the sharer based on a time-based one-time password (TOTP) algorithm, the identity key and a current timestamp;
compare the first token and the second token;
in response to determining that the first token and the second token are the same, obtain a third token calculated by a server;
compare the first token and the third token; and
return an identity verification result based on the comparison of the first token and the third token.
12 . The computing device according to claim 11 , wherein the allocated identity key is stored on a blockchain in an encrypted manner.
13 . The computing device according to claim 12 , wherein the computing device being caused to invite, based on the transaction request, the user and the sharer to send confirmation further comprises being caused to:
obtain a corresponding identity key from the blockchain based on the transaction request and the user identifier and the device identifier of the user; and
invite the user and the sharer bound to the obtained identity key to send the confirmation.