Transaction verification method and device for shared account, equipment, medium and program product
By receiving transaction verification requests for shared accounts, and using member private keys and certificate signatures to verify transaction instructions, the problem of user information storage is easily leaked, and a high-security transaction verification process is realized.
Patent Information
- Application Number
- CN202310494175.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-04
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2043-05-04
AI Technical Summary
In the prior art, the storage of user information in shared accounts is prone to information leakage, and user information needs to be obtained and stored during the verification process, affecting security.
By receiving transaction verification requests for shared accounts, verify transaction instructions using member private keys and member certificate signatures, query the target account public keys, and verify the legality of transaction requests based on the signature and public keys, allowing shared members to initiate transaction requests to avoid obtaining users information.
Improves user information security during transaction verification, avoids information leakage, and does not need to store additional user information.
Smart Images

Figure CN118898087A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a transaction verification method, apparatus, computer equipment, storage medium and computer program product for a shared account. Background Art
[0002] With the development of Internet technology, shared accounts have provided convenience for people's payment, that is, a shared account can be used by multiple authorized users. In actual use, the transaction service provider needs to verify the user who initiates the transaction in advance. If the user is verified to be an authorized user of the shared account, the user is allowed to conduct the transaction.
[0003] In the related art, each user of a shared account needs to store their information in advance in the transaction service provider, so that the transaction service can verify the authorization of the user who initiated the transaction through the pre-stored information of each user, that is, determine whether the user has the authority to use the shared account. However, storing the information of each user is very likely to cause information leakage, and the security of user information is low. Summary of the invention
[0004] Based on this, it is necessary to provide a shared account transaction verification method, apparatus, computer device, computer-readable storage medium and computer program product that can improve the security of user information of shared members of a shared account in order to address the above technical problems.
[0005] The present application provides a transaction verification method for a shared account. The method comprises:
[0006] Receive a transaction verification request from a shared account; the transaction verification request includes a transaction instruction and a signature, the signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member;
[0007] Querying the target account public key corresponding to the target shared account identifier in the transaction instruction;
[0008] When it is verified based on the queried target account public key and the signature that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier, any sharing member is allowed to initiate a transaction request for the target shared account.
[0009] The present application also provides a transaction verification device for a shared account. The device comprises:
[0010] A receiving module, configured to receive a transaction verification request of a shared account; the transaction verification request includes a transaction instruction and a signature, the signature is obtained by signing the transaction instruction according to a member private key and a member certificate of a shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member;
[0011] A query module, used to query a target account public key corresponding to a target shared account identifier in the transaction instruction;
[0012] The verification module is used to allow any sharing member to initiate a transaction request for the target shared account when it is verified based on the queried target account public key and the signature that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier.
[0013] In some embodiments, the query module is used to extract the target shared account identifier from the transaction instruction; and query the target account public key corresponding to the extracted target shared account identifier based on the pre-stored correspondence between the account public key and the shared account identifier.
[0014] In some embodiments, the device also includes a legitimacy verification module, which is used to perform a legitimacy verification on the signature based on the queried target account public key; if the legitimacy verification passes, it is determined that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier; if the legitimacy verification fails, it is determined that the transaction verification request is not initiated by any shared member of the target shared account corresponding to the target shared account identifier.
[0015] In some embodiments, the legitimacy verification module is also used to obtain the target account public parameters of the target shared account, and determine the verification value corresponding to the account public key of the shared account based on the target account public parameters and the signature; determine a reference value corresponding to the target account public key, and compare the verification value with the reference value; if the reference value is consistent with the verification value, it is determined that the legitimacy verification has passed; if the reference value is inconsistent with the verification value, it is determined that the legitimacy verification has failed.
[0016] In some embodiments, the device also includes an association module, which is used to receive a creation request for a shared account sent by an account creator, the creation request being generated based on a public-private key pair of the account creator; extracting the public key of the account creator from the creation request; using a server private key and the extracted public key of the account creator to issue a creation certificate for the account creator, and sending the creation certificate to the account creator to instruct the account creator to receive and verify the creation certificate and generate an account public-private key pair of the shared account after the verification is passed; receiving the account public key in the account public-private key pair sent by the account creator and an account public key signature generated for the account public key using the private key of the account creator; verifying the account public key signature based on the public key of the account creator, and if the verification is passed, generating a shared account identifier, and associating the account public key with the shared account identifier of the shared account.
[0017] In some embodiments, the device also includes a creation request generation module, which is used to generate a private key through the account creator and determine the corresponding public key based on the private key; through the account creator, sign the public key according to the private key to obtain a signature for creating a shared account; through the account creator, determine the creation request of the shared account based on the public key and the signature for creating a shared account.
[0018] In some embodiments, the device also includes a creation certificate verification module, which is used to verify the creation certificate by the account creator using the server public key; if the verification of the creation certificate is passed, the account creator determines that the creation certificate is issued by the server, and executes the step of generating the account public-private key pair of the shared account; if the verification of the creation certificate fails, the account creator determines that the creation certificate is not issued by the server, and determines that the shared account creation has failed.
[0019] In some embodiments, the device also includes an account public-private key pair generation module, which is used to generate an account private key of the shared account through the account creator and obtain account public parameters; through the account creator, a corresponding account public key is generated according to the account public parameters and the account private key.
[0020] In some embodiments, the device also includes an authorization module, which is used to send an authorization request to the party to be authorized through the account creation party, and the authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and generate a member public key based on the member private key and the account public parameters; after the account creation party receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized based on the account private key of the shared account and the member public key, so as to authorize the party to be authorized as a shared member of the shared account.
[0021] In some embodiments, the device also includes a member public key verification module, which is used to obtain the knowledge signature corresponding to the member public key through the account creator, and verify whether there is a member private key corresponding to the member public key through the knowledge signature; if it exists, the account creator determines that the legitimacy check of the member public key has passed, and returns to the step of issuing a member certificate for the party to be authorized based on the account private key of the shared account and the member public key to continue execution; if it does not exist, the account creator determines that the legitimacy check of the member public key has failed, and determines that the authorization of the party to be authorized has failed.
[0022] In some embodiments, the device also includes a saving module, which is used to store the member public key sent by the party to be authorized and the member certificate issued for the party to be authorized in correspondence through the account creator, and send the member certificate to the party to be authorized to instruct the party to be authorized to verify the member certificate and save the member certificate after the verification is passed.
[0023] In some embodiments, the device also includes a determination module, which is used to receive a transaction request for the target shared account initiated by a shared member of the target shared account through the account creator; obtain a signature of the transaction request through the account creator; query the member public keys of each shared member of the target shared account through the account creator, and determine the shared member identifier of the shared member who initiated the transaction request based on the public keys of each member and the signature of the transaction request.
[0024] The present application also provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the transaction verification method of the shared account when executing the computer program.
[0025] The present application also provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the transaction verification method for the shared account when executed by a processor.
[0026] The present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the transaction verification method of the shared account are implemented.
[0027] The transaction verification method, device, computer equipment, storage medium and computer program product of the above-mentioned shared account can know the transaction instruction and signature included in the transaction verification request by receiving the transaction verification request of the shared account. The signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account. The member certificate is issued to the shared member by the account creator of the shared account according to the account private key of the shared account and the member public key of the shared member. In this way, according to the shared account identifier in the transaction instruction, the target shared account corresponding to the subsequent transaction request can be quickly known, and the target account public key corresponding to the shared account identifier in the transaction instruction can be accurately queried. When it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any shared member of the target shared account corresponding to the shared account identifier, any shared member is allowed to initiate a transaction request for the target shared account. In this way, without obtaining the user information of any user, it is possible to timely and accurately verify whether the member who initiates the transaction verification request belongs to the shared member of the target shared account, effectively avoiding the leakage of user information and improving the security of user information in the transaction verification process.
[0028] The present application provides a method for creating a shared account. The method comprises:
[0029] Receiving a shared account creation request sent by an account creator, wherein the creation request is generated according to a public-private key pair of the account creator;
[0030] Extracting the public key of the account creator from the creation request;
[0031] Using the server private key and the extracted public key of the account creator, a creation certificate is issued to the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the public and private key pair of the shared account after the verification is passed;
[0032] Receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator;
[0033] The account public key signature is verified according to the public key of the account creator. If the verification is successful, a shared account identifier is generated, and the account public key is associated with the shared account identifier of the shared account.
[0034] The present application also provides a device for creating a shared account, the device comprising:
[0035] A creation request module, configured to receive a creation request for a shared account sent by an account creator, wherein the creation request is generated based on a public-private key pair of the account creator;
[0036] An extraction module, used to extract the public key of the account creator from the creation request;
[0037] A sending module, used to use the server private key and the extracted public key of the account creator to issue a creation certificate for the account creator, and send the creation certificate to the account creator to instruct the account creator to receive and verify the creation certificate and generate the public and private key pair of the shared account after the verification is passed;
[0038] A second signature module is used to receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator;
[0039] The association module is used to verify the signature of the account public key according to the public key of the account creator, generate a shared account identifier if the verification is successful, and associate the account public key with the shared account identifier of the shared account.
[0040] The present application also provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of creating the above-mentioned shared account when executing the computer program.
[0041] The present application also provides a computer-readable storage medium, wherein a computer program is stored thereon, and when the computer program is executed by a processor, the steps of the above-mentioned method for creating a shared account are implemented.
[0042] The present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the method for creating a shared account are implemented.
[0043] The above-mentioned shared account creation method, device, computer equipment, storage medium and computer program product can ensure that the public-private key pair of the account creator is obtained by receiving the shared account creation request sent by the account creator, and the creation request is generated according to the public-private key pair of the account creator, so that the public key of the account creator is directly extracted from the creation request; the server private key and the extracted public key of the account creator are used to issue a creation certificate for the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the account public-private key pair of the shared account after the verification is passed, so as to ensure the legitimacy of the creation certificate and improve the effectiveness of the shared account creation. Receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator; verify the account public key signature according to the public key of the account creator to ensure that the account public key is not counterfeited. If the verification is passed, a shared account identifier is generated, and the account public key is associated with the shared account identifier of the shared account. Based on this, in the process of creating a shared account, the user information of additional shared members of the shared account is avoided from being obtained or stored, thereby improving the security of the user information in the process.
[0044] The present application provides an account sharing method, the method comprising:
[0045] Sending an authorization request to the party to be authorized through the account creator, wherein the authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key according to the member private key and the account public parameters;
[0046] After the account creator receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized based on the account private key of the shared account and the member public key to authorize the party to be authorized as a shared member of the shared account.
[0047] The present application also provides an account sharing device, the device comprising:
[0048] An authorization request sending module, used to send an authorization request to a party to be authorized through an account creation direction, wherein the authorization request includes an account public key of a shared account and an account public parameter of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key according to the member private key and the account public parameter;
[0049] The issuing module is used to receive and verify the member public key sent by the party to be authorized through the account creator and after the verification is passed, issue a member certificate to the party to be authorized based on the account private key of the shared account and the member public key to authorize the party to be authorized as a shared member of the shared account.
[0050] The present application also provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above-mentioned account sharing method when executing the computer program.
[0051] The present application also provides a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned account sharing method are implemented.
[0052] The present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned account sharing method are implemented.
[0053] The above-mentioned account sharing method, apparatus, computer equipment, storage medium and computer program product send an authorization request to the party to be authorized through the account creator, and the authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and generate a member public key according to the member private key and the account public parameters, so as to ensure that the party to be authorized has its own member private key and the corresponding member public key. After the account creator receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized according to the account private key and the member public key of the shared account, so as to authorize the party to be authorized as a shared member of the shared account. In this way, in the process of sharing the account, only the interaction between the account creator and the party to be authorized is involved, and there is no need for the server to obtain or store the user information of the additional shared members corresponding to the account, thereby improving the security of user information in the process. BRIEF DESCRIPTION OF THE DRAWINGS
[0054] Figure 1 A diagram of an application environment of a transaction verification method for a shared account in one embodiment;
[0055] Figure 2 A schematic diagram of a flow chart of a transaction verification method for a shared account in one embodiment;
[0056] Figure 3 It is a flowchart of a transaction verification method for a shared account in another embodiment;
[0057] Figure 4 A schematic diagram of a process for generating a shared account identifier in one embodiment;
[0058] Figure 5 A schematic diagram of a flow chart of steps for generating a shared account identifier in another embodiment;
[0059] Figure 6 A flowchart of a shared account authorization step in one embodiment;
[0060] Figure 7 A flowchart of a shared account authorization step in another embodiment;
[0061] Figure 8 A schematic diagram of a flow chart of a method for creating a shared account in an embodiment;
[0062] Fig. 9 A schematic diagram of a flow chart of an account sharing method in one embodiment;
[0063] Fig.10 It is a structural block diagram of a transaction verification device for a shared account in one embodiment;
[0064] Fig.11 It is a structural block diagram of a device for creating a shared account in one embodiment;
[0065] Fig.12 is a structural block diagram of an account sharing device in one embodiment;
[0066] Fig.13 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0067] 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.
[0068] In the related art, in the transaction process involving a shared account, the transaction service provider first needs to verify whether the member to be traded is qualified to initiate a transaction on the shared account, that is, it needs to obtain the user information of the member to be traded, and verify it based on the user information and the pre-acquired authorized user information of the shared account. If the verification is successful, the member to be traded is allowed to initiate a transaction on the shared account. In other words, in order to implement transaction verification, the transaction service provider must pre-store the user information of each authorized user of each shared account and obtain the user information of the member to be traded, which is very likely to cause the leakage of user information and cannot ensure the security of user information.
[0069] The transaction verification method of a shared account provided in the embodiment of the present application can know the transaction instruction and signature included in the transaction verification request by receiving the transaction verification request of the shared account. The signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account. The member certificate is issued by the account creator of the shared account for the shared member according to the account private key of the shared account and the member public key of the shared member. In this way, according to the shared account identifier in the transaction instruction, the target shared account corresponding to the subsequent transaction request can be quickly known, and the target account public key corresponding to the shared account identifier in the transaction instruction can be accurately queried. When it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any shared member of the target shared account corresponding to the shared account identifier, any shared member is allowed to initiate a transaction request for the target shared account. In this way, without obtaining the user information of any user, it is possible to timely and accurately verify whether the member who initiates the transaction verification request belongs to the shared member of the target shared account, effectively avoiding the leakage of user information and improving the security of user information during the transaction verification process.
[0070] The transaction verification method for a shared account provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the client 102 communicates with the server 104 through the network. The server can be a server that provides transaction services. The data storage system can store data that the server needs to process. The data storage system can be integrated on the server, or it can be placed on the cloud or other servers. The server 104 receives a transaction verification request for a shared account sent by the client 102; the transaction verification request includes a transaction instruction and a signature, and the signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member; the server 104 queries the target account public key corresponding to the target shared account identifier in the transaction instruction; when the server 104 verifies that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier based on the queried target account public key and signature, any shared member is allowed to initiate a transaction request for the target shared account.
[0071] The client 102 may be an application that initiates a transaction or an application that initiates the creation of a shared account. The client 102 may be deployed on a terminal, which may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. The server may be implemented as an independent server or a server cluster consisting of multiple servers.
[0072] In one embodiment, Figure 2 As shown, a transaction verification method for a shared account is provided, and the method is applied to Figure 1 The server 104 in the example is used as an example to illustrate, including the following steps:
[0073] Step S202, receiving a transaction verification request from a shared account; the transaction verification request includes a transaction instruction and a signature, the signature is obtained by signing the transaction instruction based on the member private key and member certificate of the shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member based on the account private key of the shared account and the member public key of the shared member.
[0074] Among them, a shared account is a trading account created by the account creator in the trading institution (i.e., the server) and supports multiple shared members authorized by the account creator to control its resources. Optionally, the account creator creates a corresponding shared account for a collective, which includes multiple members, and each member in the collective is a shared member of the shared account, that is, each member belonging to the collective has the right to use the shared account. Therefore, the collective can be understood as a group of members authorized to use the shared account. Of course, the account creator is also a shared member of the shared account corresponding to the collective, and is also the administrator of the collective. For example, the collective can be the family to which the account creator belongs, and the members in the collective are the family members of the account creator; for another example, the collective can be the social circle to which the account creator belongs, and the social circle can be multiple friends followed by the account creator in a certain application.
[0075] The transaction verification request is initiated by the anonymous party to be traded, and is used to verify whether the anonymous party to be traded can initiate a transaction request for the target shared account to be traded. The transaction instruction refers to the instruction for the transaction to be conducted, which includes the target shared account identifier of the target shared account to be traded. The signature refers to the signature of the transaction instruction. Exemplarily, the party to be traded a will use the target shared account P to initiate a transaction request for a certain product. Before this, the party to be traded a needs to anonymously initiate a transaction verification request to the server. At this time, the party to be traded a determines the transaction instruction based on the target shared account identifier of the target shared account P. The server receives the transaction verification request including the transaction instruction and the signature of the transaction instruction sent anonymously by the party to be traded a. For the server, since this transaction verification request is anonymously initiated by the party to be traded a, the server does not know who initiated this transaction verification request and the subsequent transaction request to be conducted.
[0076] The member private key of a shared member refers to the private key of the member of the group corresponding to the shared account. The member certificate is a certificate issued by the account creator to the member of the group corresponding to the shared account. The account private key of a shared account is the collective private key of the group corresponding to the shared account, and the account public key of a shared account is the collective public key of the group corresponding to the shared account.
[0077] For each shared account, the shared account has a unique corresponding collective, the shared account corresponds to an account public key and an account private key, the shared account corresponds to multiple member public-private key pairs, and each member public-private pair corresponds to a shared member.
[0078] Optionally, the server receives a transaction verification request from a shared account, and parses the transaction instruction and the signature of the transaction instruction from the transaction verification request. The signature is obtained by a shared member of the shared account signing the transaction instruction according to the member private key and member certificate corresponding to the shared account. The member private key is randomly generated by the shared member, and the corresponding member public key is determined according to the member private key. The member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member.
[0079] Exemplarily, the server receives a transaction verification request for a shared account sent by an anonymous client (which can be understood as the party to be traded). That is, for the server, it is impossible to determine which client (the party to be traded) sent the transaction verification request. After the server obtains the transaction instruction and signature according to the transaction verification request, it can further obtain the target shared account identifier of the target shared account to be traded according to the transaction instruction. The target shared account identifier and the signature are used to determine whether the anonymous client is a shared member of the target shared account, and there is no need to further determine which shared member it is.
[0080] Step S204, querying the target account public key corresponding to the target shared account identifier in the transaction instruction.
[0081] Optionally, the server determines, according to the target shared account identifier in the transaction instruction, a target account public key corresponding to the target shared account identifier from pre-stored account public keys of multiple shared accounts.
[0082] In one embodiment, querying the target account public key corresponding to the target shared account identifier in the transaction instruction includes: extracting the target shared account identifier from the transaction instruction; and querying the target account public key corresponding to the extracted target shared account identifier based on a pre-stored correspondence between the account public key and the shared account identifier.
[0083] The correspondence between the account public key and the shared account identifier means that each account public key uniquely corresponds to one shared account identifier.
[0084] Optionally, the server extracts the target shared account identifier from the transaction instruction and obtains the pre-stored correspondence between the account public key and the shared account identifier. Based on the correspondence, the server determines the target account public key that is paired with the target shared account identifier, and the target account public key is the account private key of the target shared account.
[0085] Exemplarily, after extracting the target shared account identifier IDm, the server determines that the target account public key corresponding to the target shared account identifier IDm is PKm according to the corresponding relationship between the account public key and the shared account identifier: ID1-PK1, ID1-PK2, ..., IDm-PKm.
[0086] In this embodiment, the target shared account identifier of the target shared account to be traded is parsed through the transaction instruction, and then the corresponding target account public key can be accurately and timely queried based on the correspondence between the pre-stored account public key and the shared account identifier, thereby improving the accuracy of the target account public key search. At the same time, the transaction verification can be directly performed based on the matching target account public key. This process does not require obtaining the user information of any user, thereby improving the security of user information in transaction verification.
[0087] Step S206, when it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier, any sharing member is allowed to initiate a transaction request for the target shared account.
[0088] Among them, the transaction request is a request to initiate a transaction to the server.
[0089] Optionally, the server verifies whether the transaction verification request is initiated by a shared member authorized by the target shared account based on the target account public key and signature. When it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier, the server allows the shared member who initiated the transaction verification request to initiate a transaction request for the target shared account.
[0090] In some embodiments, the method also includes: performing a legitimacy check on the signature based on the queried target account public key; if the legitimacy check passes, determining that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier; if the legitimacy check fails, determining that the transaction verification request is not initiated by any shared member of the target shared account corresponding to the target shared account identifier.
[0091] The legitimacy check is to check whether the signature is obtained by the shared members of the target shared account to sign the transaction instruction. If the transaction instruction is signed by the shared members of the target shared account, it means that the transaction verification request is initiated by the shared members of the target shared account. If the transaction instruction is not signed by the shared members of the target shared account, it means that the transaction verification request is not initiated by the shared members of the target shared account.
[0092] Optionally, the server performs a validity check on the signature based on the queried target account public key. If the validity check passes, the server determines that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier, and allows the shared member who initiated the transaction verification request to initiate a transaction request for the target shared account. If the validity check fails, the server determines that the transaction verification request is not initiated by any shared member of the target shared account corresponding to the target shared account identifier, and prohibits the shared member who initiated the transaction verification request from initiating a transaction request for the target shared account.
[0093] In this embodiment, after determining the target account public key and signature, there is no need to obtain the user information of any user. The target account public key is directly used to verify the legitimacy of the signature to complete whether the transaction verification request is initiated by a shared member authorized by the account creator who created the target shared account. If the legitimacy check passes, it is determined that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier; if the legitimacy check fails, it is determined that the transaction verification request is not initiated by any shared member of the target shared account corresponding to the target shared account identifier. In this way, the security of user information can be greatly improved.
[0094] In some embodiments, the legitimacy of the signature is verified based on the queried target account public key, including: obtaining the target account public parameters of the target shared account, and determining the verification value corresponding to the account public key of the shared account based on the target account public parameters and the signature; determining a reference value corresponding to the target account public key, and comparing the verification value with the reference value; if the reference value is consistent with the verification value, it is determined that the legitimacy check has passed, and if the reference value is inconsistent with the verification value, it is determined that the legitimacy check has failed.
[0095] Among them, for each shared account, in the process of determining the account public key of the shared account, it is necessary to determine it based on the account public parameters corresponding to the shared account. The signature, account public parameters, account private key and account public key can all be regarded as a set of parameters. For example, the signature can be regarded as a set of multiple signature parameters, the account public parameters can be regarded as a set of multiple public parameters, the account public key can be regarded as a set of multiple first account public key parameters and multiple second account public key parameters, and the account private key can be regarded as a set of multiple account private key parameters. Among them, the first account public key parameters are calculated based on certain public parameters, and at the same time, the certain public parameters can be directly used as the second account public key parameters.
[0096] If the reference value is consistent with the verification value, it means that the shared account is the target shared account.
[0097] Optionally, the server obtains the target account public parameters of the target shared account, and obtains the target public parameters for legitimacy verification from the target account public parameters. The server performs hash calculation on the transaction instruction to obtain a summary. The server determines the reference value corresponding to the target account public key based on the first account public key parameter and the summary. The server determines the verification value corresponding to the account public key of the shared account based on the target public parameters and the signature parameters. If the reference value is consistent with the verification value, it is determined that the legitimacy check has passed. If the reference value is inconsistent with the verification value, it is determined that the legitimacy check has failed.
[0098] For example, let the digest be m, the two first account public key parameters be U and Q, and the three target public parameters be α, β, and n. The two signature parameters are f and g. The server uses the product of Q to the power of m and U as the reference value, that is, the reference value is UQ m The server calculates the product of α raised to the power of f and β raised to the power of g, and obtains α f β g . The server is responsible for α f β g Perform a modulo operation on n to obtain the verification value, that is, the verification value is α f β g (modn). Where mod is the modulo function.
[0099] If UQ m=α f β g (modn), then the legality check passes. If UQ m ≠α f β g (modn), the legality check fails.
[0100] In this embodiment, the verification value corresponding to the account public key of the shared account is determined by the target account public parameter and signature of the target shared account. At the same time, the reference value corresponding to the target account public key is determined. If the reference value and the verification value are consistent, it is determined that the shared account is the target shared account, and the legitimacy check passes. If the reference value and the verification value are inconsistent, it is determined that the shared account is not the target shared account, and the legitimacy check fails. In this way, without obtaining the user information of any user, the legitimacy check of the signature can be effectively verified, thereby improving the security of user information.
[0101] In the transaction verification method of the above-mentioned shared account, by receiving the transaction verification request of the shared account, the transaction instruction and signature included in the transaction verification request can be known, and the signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member. In this way, according to the shared account identifier in the transaction instruction, the target shared account corresponding to the subsequent transaction request can be quickly known, and the target account public key corresponding to the shared account identifier in the transaction instruction can be accurately queried. When it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any shared member of the target shared account corresponding to the shared account identifier, any shared member is allowed to initiate a transaction request for the target shared account. In this way, without obtaining the user information of any user, it is possible to timely and accurately verify whether the member who initiates the transaction verification request belongs to the shared member of the target shared account, effectively avoiding the leakage of user information and improving the information security in the transaction verification process.
[0102] In some embodiments, Figure 3As shown, it is a flow chart of a transaction verification method for a shared account in another embodiment. The anonymous client determines the transaction instruction according to the target shared account identifier and the number of resources to be traded, and the anonymous client signs the transaction instruction according to the member private key and member certificate corresponding to the authorized shared account to obtain the signature of the transaction instruction. The anonymous client determines the transaction verification request according to the transaction instruction and the signature of the transaction instruction. The server receives the transaction verification request sent by the anonymous client, and extracts the target shared account identifier from the transaction instruction; according to the correspondence between the pre-stored account public key and the shared account identifier, the target account public key corresponding to the extracted target shared account identifier is queried. The server verifies the legitimacy of the signature through the target account public key, specifically: obtains the target account public parameter of the target shared account, and determines the verification value corresponding to the account public key of the shared account according to the target account public parameter and the signature; determines the reference value corresponding to the target account public key, and compares the verification value with the reference value; if the reference value is consistent with the verification value, it is determined that the legitimacy check is passed, and it is determined that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier. If the reference value is inconsistent with the verification value, it is determined that the legitimacy check fails, and it is determined that the transaction verification request is not initiated by any sharing member of the target shared account corresponding to the target shared account identifier. When it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier, any sharing member is allowed to initiate a transaction request for the target shared account.
[0103] In this embodiment, the verification value corresponding to the account public key of the shared account is determined by the target account public parameter and signature of the target shared account. At the same time, the reference value corresponding to the target account public key is determined. If the reference value and the verification value are consistent, it is determined that the shared account is the target shared account, and the legitimacy check passes. If the reference value and the verification value are inconsistent, it is determined that the shared account is not the target shared account, and the legitimacy check fails. In this way, without obtaining the user information of any user, the legitimacy check of the signature can be effectively verified, thereby improving the security of user information.
[0104] In some embodiments, Figure 4 FIG. 1 is a flow chart of steps for generating a shared account identifier in an embodiment. Before receiving a transaction verification request from a shared account, the method further includes:
[0105] Step S402: receiving a shared account creation request sent by an account creator, where the creation request is generated based on the public-private key pair of the account creator.
[0106] The creation request is used to request the creation of a shared account. The public-private key pair of the account creator refers to the private key and public key of the account creator. Exemplarily, the public-private key pair of the account creator may be a pair of asymmetric keys.
[0107] Optionally, a creation request is generated using the account creator's own private key and public key, and the creation request is sent to the server.
[0108] In some embodiments, Figure 4 As shown, before step S402, the method further includes step S401, that is, generating a creation request for a shared account by the account creator, and step S401 includes:
[0109] Step S401a: Generate a private key through the account creator, and determine the corresponding public key based on the private key.
[0110] Step S401b: The account creator signs the public key according to the private key to obtain a signature for creating a shared account.
[0111] Step S401c: The account creator determines the request for creating a shared account based on the public key and the signature for creating the shared account.
[0112] Optionally, the account creator generates a private key according to random parameters, and determines the corresponding public key according to the private key. The account creator signs the public key of the account creator according to the private key of the account creator to obtain a signature for creating a shared account. The account creator concatenates the signature of the request for creating a shared account and the share of the account creator to generate a creation request including the signature for creating a shared account and the public key of the account creator.
[0113] After executing step S401a, the user can obtain his / her own identity information through the account creator, and obtain additional information by fusing the identity information and the public key of the account creator through the account creator. The account creator signs the additional information according to the private key of the account creator to obtain a signature on the creation of the shared account. Then, the process returns to step S401c to continue.
[0114] In this embodiment, a private key is generated by the account creator, and the corresponding public key is determined based on the private key. Then, the account creator signs the public key based on the private key to obtain a signature for creating a shared account. In this way, the subsequent server can accurately verify whether a pair of public-private key pairs is generated based on the public key of the account creator obtained. The account creator determines the creation request of the shared account based on the public key and the signature for creating the shared account. In this way, the subsequent server can generate a creation certificate for the account creator in a timely manner based on the creation request, so that the creation of the shared account can be completed based on the creation certificate.
[0115] Step S404: extract the public key of the account creator from the creation request.
[0116] Step S406, using the server private key and the extracted public key of the account creator, a creation certificate is issued to the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the public and private key pair of the shared account after the verification.
[0117] Optionally, after obtaining the public key of the account creator, the server can directly use its own server private key and the public key of the account creator to issue a creation certificate for the account creator.
[0118] Optionally, after obtaining the public key of the account creator, the server verifies that the identity of the account creator is legitimate, and then executes step S406. In this way, it is possible to avoid creating a certificate for an account creator with an illegal identity.
[0119] In some embodiments, a creation certificate is issued to the account creator using a server private key and an extracted public key of the account creator, including: using the server private key to sign the extracted public key of the account creator to determine the creation certificate.
[0120] In the above embodiment, the server uses the server private key to sign the public key of the account creator, and issues a creation certificate to the account creator. The shared account can be created based on the creation certificate. There is no need to obtain or store the user information of the additional shared members of the shared account, which improves the security of user information during the shared account creation process.
[0121] In some embodiments, before using the server private key and the extracted public key of the account creator to issue a creation certificate to the account creator, it also includes: obtaining the identity information to be verified of the account creator, and comparing the identity information to be verified with each pre-stored standard identity information, and determining the identity authentication result of the account creator according to each comparison result; if the identity authentication result indicates that the identity authentication is passed, executing the step of using the server private key and the extracted public key of the account creator to issue a creation certificate to the account creator.
[0122] The identity information may be a biometric feature, such as face, fingerprint, fingerprint, iris, etc. Each standard identity information uniquely corresponds to the account creator of a shared account. The identity information is information authorized by the account creator.
[0123] Optionally, the server obtains the identity information to be verified sent by the account creator, and compares the identity information to be verified with each pre-stored standard identity information. If the server verifies that there is a comparison result representation that is consistent, the server determines that the identity authentication result representation of the account creator is a successful identity authentication, and the server executes the step of issuing a creation certificate for the account creator using the server private key and the extracted public key of the account creator. If the server does not verify that a comparison result representation is consistent, the server determines that the identity authentication result representation of the account creator is a failed identity authentication.
[0124] Exemplarily, the server obtains the face to be verified collected by the account creator, and compares the face to be verified with each pre-stored standard face. If there is a standard face that is consistent with the face to be verified, the server determines that the identity authentication result of the account creator is characterized as a successful identity authentication, and the server executes the step of issuing a creation certificate for the account creator using the server private key and the extracted public key of the account creator. If there is no standard face that is consistent with the face to be verified, the server determines that the identity authentication result of the account creator is characterized as a failed identity authentication.
[0125] In this embodiment, by comparing the identity information to be verified of the account creator with each pre-stored standard identity information, the identity of the account creator can be quickly and accurately authenticated. If the identity authentication result indicates that the identity authentication is passed, the step of issuing a creation certificate for the account creator using the server private key and the extracted public key of the account creator is executed to ensure the validity of the subsequent creation certificate. In this way, the creation of a shared account can be completed based on a valid creation certificate without obtaining or storing the user information of the additional shared members of the shared account, thereby improving the security of user information during the shared account creation process.
[0126] In some embodiments, the step of the account creator verifying the creation certificate includes: verifying the creation certificate by the account creator using the server public key; if the verification of the creation certificate passes, determining by the account creator that the creation certificate is issued by the server, and executing the step of generating the public and private key pair of the shared account; if the verification of the creation certificate fails, determining by the account creator that the creation certificate is not issued by the server, and determining that the shared account creation has failed.
[0127] Among them, the server public key is the server's own public key, which is built into the account creator. The server public key and the server private key are a pair of asymmetric public-private key pairs of the server itself. As mentioned above, since the creation of the certificate is determined based on the server private key, only the server public key corresponding to the server private key can make the verification of the creation certificate pass. If the certificate is verified by other public keys that do not match the server private key, the verification of the creation certificate will inevitably fail.
[0128] In the above embodiment, the creation certificate is verified by the account creator using the server public key; if the verification is successful, it can be verified in time whether the received creation certificate is issued by the server, further ensuring the validity of the creation certificate. If the verification of the creation certificate is successful, the account creator determines that the creation certificate is issued by the server, and executes the steps of generating the public and private key pair of the shared account; if the verification of the creation certificate fails, the account creator determines that the creation certificate is not issued by the server, and determines that the creation of the shared account has failed. In this way, after the verification is successful, the creation of the shared account can be completed based on the valid creation certificate, without obtaining or storing the user information of the additional shared members of the shared account, thereby improving the security of user information during the shared account creation process.
[0129] After the verification of the creation certificate is passed, in some embodiments, the step of the account creator generating the public-private key pair of the shared account includes: generating the account private key of the shared account by the account creator and obtaining the account public parameters; generating the corresponding account public key by the account creator according to the account public parameters and the account private key.
[0130] As mentioned above, the account public parameters can be regarded as a collection of multiple public parameters, the account public key can be regarded as a collection of multiple first account public key parameters and multiple second account public key parameters, and the account private key can be regarded as a collection of multiple account private key parameters. Among them, the first account public key parameters are calculated based on certain public parameters, and at the same time, the certain public parameters can be directly used as the second account public key parameters.
[0131] Optionally, the account creator generates an account private key of the shared account, and obtains public parameters for generating the account public key from the account public parameters. The account creator determines the first account public key parameters according to the target public parameters and the private key parameters of the account private key, and determines the corresponding account public key according to the first account public key parameters.
[0132] In this embodiment, the account private key of the shared account is randomly generated by the account creator. Since the account private key is randomly generated, it cannot be ensured that the account private key contains parameters corresponding to the shared account. Since the account public parameters of each shared account are different, in order to ensure that the subsequent server can verify the transaction based on the account public key, the generation of the account public key needs to be combined with the account public parameters. At this time, the account public parameters are obtained, and the account creator can determine the account public key corresponding to the account private key by combining the parameters of the account private key and the parameters of the account public parameters. In this way, in the subsequent transaction verification process, the transaction verification can be directly performed based on the account public key without obtaining additional user information, thereby improving the security of user information.
[0133] Step S408: Receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator.
[0134] Optionally, the server receives the account public key and account public key signature sent by the account creator, wherein the account public key signature is used to verify whether the corresponding account public key is generated by the account creator, that is, whether it is forged by an imposter.
[0135] In some embodiments, the step of the account creator using the creation certificate to generate an account public key signature for the account public key includes: the account creator uses the account creator's private key to sign the account public key to obtain the account public key signature.
[0136] It should be noted that the private key and public key of the account creator are determined in the aforementioned step S401a. Since the account public key signature is required to enable the server to determine that the account public key is generated by the account creator, the account public key needs to be signed with the private key of the account creator. If the account public key signature can be verified based on the public key matching the private key of the account creator, it means that the account public key received by the server is not forged by an imposter.
[0137] In this embodiment, the account creator uses the private key of the account creator to sign the account public key to obtain the account public key signature. In this way, it can be ensured that the account public key received by the server is not counterfeited or tampered by the counterfeiter by verifying the account public key signature, thereby ensuring the validity and accuracy of the subsequent shared account creation.
[0138] Step S410, verify the account public key signature according to the public key of the account creator, if the verification is successful, generate a shared account identifier, and associate the account public key with the shared account identifier of the shared account.
[0139] Optionally, the server verifies the signature of the account public key using the public key of the account creator. If the verification is successful, the server determines that the received account public key is generated by the account creator and generates a shared account identifier for the shared account. The server associates the account public key with the shared account identifier for the shared account. If the verification fails, the server determines that the creation of the shared account has failed.
[0140] Regarding the process of creating a shared account from step S401 to step S410, Figure 5 As shown, it is a flow chart of the steps of generating a shared account identifier in another embodiment. After the account creator and the server are initialized, the account creator generates an asymmetric key pair. The account creator signs the public key according to the private key to obtain a signature for creating a shared account; the account creator determines the creation request of the shared account according to the public key and the signature for creating a shared account, and sends it to the server. The server obtains the identity information to be verified of the account creator, and compares the identity information to be verified with each pre-stored standard identity information, and determines the identity authentication result of the account creator according to each comparison result; if the identity authentication result indicates that the identity authentication is passed, the server uses the server private key to sign the extracted public key of the account creator, determines the creation certificate, and sends the creation certificate to the account creator. The account creator verifies the creation certificate using the server public key; if the verification of the creation certificate fails, the account creator determines that the creation certificate is not issued by the server, and determines that the creation of the shared account fails. If the verification of the creation certificate is passed, the account creator determines that the creation certificate is issued by the server, and generates the public and private key pair of the shared account through the account creator. Specifically: the account creator generates the account private key of the shared account and obtains the account public parameters; the account creator generates the corresponding account public key according to the account public parameters and the account private key. The account creator signs the account public key with the private key of the account creator to obtain the account public key signature. The account creator sends the account public key and the account public key signature to the server. The server verifies the account public key signature according to the public key of the account creator. If the verification passes, it determines that the creation fails. If the verification passes, the server saves the account public key, generates a shared account identifier, and associates the account public key with the shared account identifier of the shared account. At this time, the server determines that the creation is successful.
[0141] In this embodiment, by receiving the creation request of the shared account sent by the account creator, it is possible to ensure that the public-private key pair of the account creator is obtained, and the creation request is generated according to the public-private key pair of the account creator. In this way, the public key of the account creator is directly extracted from the creation request; the service-side private key and the extracted public key of the account creator are used to issue a creation certificate for the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the account public-private key pair of the shared account after the verification is passed, so as to ensure the legitimacy of the creation certificate and improve the effectiveness of the shared account creation. The account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator are received; the account public key signature is verified according to the public key of the account creator to ensure that the account public key is not counterfeited. If the verification is passed, a shared account identifier is generated, and the account public key is associated with the shared account identifier of the shared account. Based on this, in the process of creating a shared account, the user information of the additional shared members of the shared account is avoided from being obtained or stored, thereby improving the security of the user information in the process.
[0142] In some embodiments, Figure 6 FIG. 1 is a flow chart of a shared account authorization step in an embodiment. Before receiving a transaction verification request from a shared account, the method further includes:
[0143] Step S602: Send an authorization request to the party to be authorized through the account creator. The authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and generate a member public key based on the member private key and the account public parameters.
[0144] Among them, the party to be authorized is the mobile terminal that is to be authorized to share the account. As mentioned above, the account creator is the mobile terminal used to create a shared account and authorize the shared account. The party to be authorized and the account creator can be the same mobile terminal or different mobile terminals, and there is no specific limitation.
[0145] Optionally, the account creator sends an authorization request to the party to be authorized, the authorization request including the account public key of the shared account created by the account creator and the account public parameters of the shared account. The party to be authorized generates a member public-private key pair corresponding to the shared account and related to the party to be authorized according to the authorization request.
[0146] For example, if the account creator and the party to be authorized communicate via a local area network, the account creator directly sends an authorization request to the party to be authorized, and the party to be authorized directly receives the authorization request. At this time, the local area network may be wifi (WIreless Fidelity, wireless network transmission technology).
[0147] If the account creator and the party to be authorized communicate through the server, in order to prevent the server from maliciously obtaining information, end-to-end encryption is used to ensure information leakage. At this time, the account creator generates a first public key and a first private key for transmitting the authorization request. At this time, the account creator encrypts the authorization request using the first public key and sends the encrypted authorization request to the party to be authorized. The party to be authorized decrypts the authorization request using the first public key of the account creator to obtain the authorization request.
[0148] In some embodiments, the steps of the party to be authorized generating a member private key in response to an authorization request and generating a member public key based on the member private key and account public parameters include: generating the member private key of the party to be authorized in response to the authorization request; extracting generation parameters for generating the member public key from the account public parameters by the party to be authorized, and generating the member public key of the party to be authorized based on the generation parameters and the member private key.
[0149] As mentioned above, the account public parameters are a set of multiple public parameters, and the generated parameters here can be regarded as public parameters.
[0150] Optionally, the party to be authorized randomly generates a member private key of the party to be authorized in response to the authorization request, and extracts generation parameters for generating the member public key from the account public parameters. The party to be authorized generates a member public key of the party to be authorized that matches the member private key based on the generation parameters and the parameters of the member private key.
[0151] For example, the parameter of the member private key is x, and the three generation parameters for generating the account public key are g, a, and n (where n is also the target public parameter for legitimacy verification, as mentioned above). The authorized party performs a modulo operation on x with respect to n to obtain x(modn), and uses a to the power of x(modn) as one of the parameters y of the member public key, i.e., y=a ∧ x(modn), and use the yth power of g as another parameter z of the member's public key, that is, z = g ∧ y, based on this, determine the corresponding account public key according to y and z.
[0152] In this embodiment, the member private key of the party to be authorized is generated in a timely manner in response to the authorization request, and the party to be authorized extracts the generation parameters for generating the member public key from the account public parameters of the shared account, and based on the generation parameters and the member private key, a member public key that matches the member private key can be accurately generated.
[0153] Step S604, after the account creator receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized based on the account private key and the member public key of the shared account to authorize the party to be authorized as a shared member of the shared account.
[0154] Optionally, the account creator receives the member public key sent by the party to be authorized and verifies the member public key. After the verification is passed, the account creator signs the member public key according to the account private key of the shared account to obtain a member certificate to authorize the party to be authorized as a shared member of the shared account.
[0155] In the process of the account creator obtaining the member public key, illustratively, if the account creator and the party to be authorized communicate through a local area network, the party to be authorized directly sends the member public key to the account creator. At this time, the local area network can be wifi (WIreless Fidelity, wireless network transmission technology).
[0156] If the account creator and the party to be authorized communicate through the server, in order to prevent the server from maliciously obtaining information, end-to-end encryption is used to ensure information leakage. At this time, the party to be authorized generates a second public key and a second private key for transmitting the member public key, and the party to be authorized uses the second private key to encrypt the member public key, and transmits the encrypted member public key to the account creator, and the account creator uses the second public key to decrypt the encrypted member public key to obtain the member public key.
[0157] In some embodiments, the step of the account creator verifying the member public key sent by the party to be authorized includes: obtaining the knowledge signature corresponding to the member public key through the account creator, and verifying whether there is a member private key corresponding to the member public key through the knowledge signature; if it exists, the account creator determines that the legitimacy check of the member public key passes, and returns to the step of issuing a member certificate for the party to be authorized according to the account private key and the member public key of the shared account to continue to execute; if it does not exist, the account creator determines that the legitimacy check of the member public key fails, and determines that the authorization of the party to be authorized fails. Among them, the knowledge signature is used to verify whether the party to be authorized has a member private key corresponding to the member public key. In the process of using the knowledge signature to verify the legitimacy of the member public key, the account creator does not need to know what the member private key of the party to be authorized is, and only needs to determine whether the party to be authorized has a member public-private key pair about the shared account. If the legitimacy check of the member public key passes, it means that the party to be authorized has a member public-private key pair, and the member public key corresponds to the account public parameter of the shared account, that is, the member public-private key pair is used for the shared account.
[0158] In this embodiment, the knowledge signature corresponding to the member public key is obtained by the account creator. Based on the knowledge signature, it can be accurately determined whether there is a member private key matching the member public key. If so, it means that the party to be authorized has the member public-private pair for the shared account, and it can ensure that the member certificate issued subsequently is valid. If not, it is directly determined that the authorization to the party to be authorized has failed.
[0159] In some embodiments, the step of issuing a member certificate for the party to be authorized based on the account private key and member public key of the shared account includes: the account creator uses the account private key of the shared account to sign the member public key to obtain the member certificate of the party to be authorized.
[0160] In this embodiment, the account creator uses the account private key of the shared account to directly sign the member public key to obtain the member certificate of the party to be authorized, so as to complete the authorization of the party to be authorized. Based on this, in the process of transaction verification, the signature of the transaction instruction can be determined based on the member certificate, so that without obtaining the user information of additional members, it is possible to timely and accurately verify whether the member who initiates the transaction verification request belongs to the shared member of the target shared account directly based on the signature and the target account public key, effectively avoiding the leakage of user information and improving the security of user information during the transaction verification process.
[0161] In some embodiments, Figure 6 As shown, after step S604, the method also includes: step S606, the account creator stores the member public key sent by the party to be authorized and the member certificate issued for the party to be authorized in correspondence, and sends the member certificate to the party to be authorized to instruct the party to be authorized to verify the member certificate and save the member certificate after the verification is passed.
[0162] Optionally, after the account creator stores the member public key sent by the party to be authorized and the member certificate issued for the party to be authorized in correspondence, if the account creator and the party to be authorized communicate through a local area network, the member certificate is directly sent to the party to be authorized by the account creator.
[0163] If the account creator and the party to be authorized communicate through the server, in order to prevent the server from maliciously obtaining information, end-to-end encryption is used to ensure information leakage. At this time, the third public key and third private key for transmitting the member certificate are generated by the account creator. The account creator encrypts the member certificate using the third private key and sends the encrypted member certificate to the party to be authorized. The party to be authorized decrypts the encrypted member certificate using the third public key to obtain the authorization certificate.
[0164] Based on the above process, after the party to be authorized receives the member certificate and determines that the verification of the member certificate has passed, the party to be authorized directly saves the member certificate.
[0165] In some embodiments, the step of the party to be authorized verifying the member certificate includes: verifying the member certificate according to the account public key through the party to be authorized; if the verification of the member certificate passes, authorizing the party to be authorized as a shared member of the shared account through the account creator; if the verification of the member certificate fails, not authorizing the party to be authorized as a shared member of the shared account through the account creator.
[0166] Optionally, the party to be authorized calculates the parameters to be verified based on the member certificate, and determines the target parameters for verifying the member certificate from the account public key parameters in the account public key. If the target parameters are consistent with the parameters to be verified, it is determined that the verification of the member certificate has passed; if the target parameters are consistent with the parameters to be verified, it is determined that the verification of the member certificate has failed.
[0167] It should be noted that since the member certificate is obtained by signing the member public key with the account private key, if the member certificate is verified using the account public key of the shared account, if the verification of the member certificate is successful, it means that the member certificate received by the authorized party is issued by the account creator who created the shared account. At this time, after the account creator receives the information that the party to be authorized has passed the verification, the party to be authorized is authorized as a shared member of the shared account. If the verification of the member certificate fails, it means that the member certificate received by the authorized party is not issued by the account creator who created the shared account. After the account creator receives the message that the party to be authorized has failed the verification, the party to be authorized is not authorized as a shared member of the shared account. Based on this, in the process of sharing an account, it only involves the interaction between the account creator and the party to be authorized. There is no need for the server to obtain or store the user information of the additional shared members corresponding to the account, which improves the security of user information in the process.
[0168] For the authorization process of the above shared account, such as Figure 7As shown, it is a flow chart of the shared account authorization step in another embodiment. The account creator sends an authorization request to the party to be authorized, and the authorization request includes the account public key of the shared account created by the account creator and the account public parameters of the shared account. The party to be authorized responds to the authorization request and generates the member private key of the party to be authorized; the party to be authorized extracts the generation parameters for generating the member public key from the account public parameters, and generates the member public key of the party to be authorized according to the generation parameters and the member private key. The party to be authorized sends the member public key to the account creator. The account creator obtains the knowledge signature corresponding to the member public key, and verifies whether there is a member private key corresponding to the member public key through the knowledge signature; if not, the account creator determines that the legitimacy check of the member public key fails, and determines that the authorization of the party to be authorized fails. If it exists, the account creator determines that the legitimacy check of the member public key passes, and the account creator saves the member public key. The account creator signs the member public key with the account private key of the shared account, determines the member certificate issued to the party to be authorized, and sends the member certificate to the party to be authorized. The party to be authorized verifies the member certificate according to the account public key; if the verification of the member certificate is passed, the party to be authorized is authorized by the account creator as a shared member of the shared account; if the verification of the member certificate is not passed, the party to be authorized is not authorized by the account creator as a shared member of the shared account.
[0169] In some embodiments, the method also includes: receiving, through the account creator, a transaction request for the target shared account initiated by a shared member of the target shared account; obtaining, through the account creator, a signature of the transaction request; querying, through the account creator, the member public keys of each shared member of the target shared account, and determining, based on the public keys of each member and the signature of the transaction request, the shared member identifier of the shared member who initiated the transaction request.
[0170] Optionally, a transaction request for a target shared account is received through an account creator, and the transaction request is a request initiated by a shared member of the target shared account. The signature of the transaction request is obtained through the account creator. The member IDs of each shared member of the target shared account are queried through the account creator, and the member public keys of each shared member are determined based on each member ID. Through each member public key and the signature of the transaction request, it is determined whether there is a member public key that successfully opens the signature of the transaction request. If so, it is determined that the shared member corresponding to the successfully opened member public key is the shared member that initiated the transaction request, and the shared member that initiated the transaction request is determined.
[0171] Exemplarily, after the member identification of each shared member is determined, the member public key of each shared member is determined by the account creator using the pre-stored member public keys of the target shared account and the correspondence between the member identification and the member public key. The account creator uses each member public key to open the signature of the transaction request. If it is determined that there is a member public key that successfully opens the signature of the transaction request, the shared member corresponding to the successfully opened member public key is determined to be the shared member that initiated the transaction request.
[0172] In this embodiment, when the account creator stores the member public keys of each shared member corresponding to each shared account, the account creator can quickly query the member public keys of each shared member corresponding to the target shared account for a transaction request of the target shared account, and based on the public keys of each member and the signature of the transaction request, the account creator can quickly and accurately query the shared member who initiated the transaction request.
[0173] In one embodiment, Figure 8 As shown, a method for creating a shared account is provided, and the method is applied to Figure 1 The following steps are taken as an example to illustrate the server:
[0174] Step S802: receiving a shared account creation request sent by an account creator, where the creation request is generated based on the public-private key pair of the account creator.
[0175] In one embodiment, the steps of generating a request to create a shared account include: generating a private key by the account creator, and determining a corresponding public key based on the private key; signing the public key by the account creator based on the private key to obtain a signature for creating a shared account; and determining the request to create a shared account by the account creator based on the public key and the signature for creating a shared account.
[0176] Step S804: extract the public key of the account creator from the creation request.
[0177] Step S806, using the server private key and the extracted public key of the account creator, a creation certificate is issued to the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the public and private key pair of the shared account after the verification.
[0178] In some embodiments, a creation certificate is issued to the account creator using a server private key and an extracted public key of the account creator, including: using the server private key to sign the extracted public key of the account creator to determine the creation certificate.
[0179] In some embodiments, before using the server private key and the extracted public key of the account creator to issue a creation certificate to the account creator, it also includes: obtaining the identity information to be verified of the account creator, and comparing the identity information to be verified with each pre-stored standard identity information, and determining the identity authentication result of the account creator according to each comparison result; if the identity authentication result indicates that the identity authentication is passed, executing the step of using the server private key and the extracted public key of the account creator to issue a creation certificate to the account creator.
[0180] In some embodiments, the step of the account creator verifying the creation certificate includes: through the account creator, using the server public key to verify the creation certificate; if the verification of the creation certificate passes, the account creator determines that the creation certificate is issued by the server, and executes the step of generating the public and private key pair of the shared account; if the verification of the creation certificate fails, the account creator determines that the creation certificate is not issued by the server, and determines that the shared account creation has failed.
[0181] In some embodiments, the step of the account creator generating the public-private key pair of the shared account includes: generating the account private key of the shared account through the account creator and obtaining the account public parameters; and generating the corresponding account public key through the account creator according to the account public parameters and the account private key.
[0182] Step S808: Receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator.
[0183] In some embodiments, the step of the account creator using the creation certificate to generate an account public key signature for the account public key includes: the account creator uses the account creator's private key to sign the account public key to obtain the account public key signature.
[0184] Step S810, verify the account public key signature according to the public key of the account creator. If the verification passes, generate a shared account identifier, and associate the account public key with the shared account identifier of the shared account.
[0185] In the above-mentioned shared account creation method, by receiving the shared account creation request sent by the account creator, it is possible to ensure that the public-private key pair of the account creator is obtained, and the creation request is generated according to the public-private key pair of the account creator. In this way, the public key of the account creator is directly extracted from the creation request; the server private key and the extracted public key of the account creator are used to issue a creation certificate for the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the account public-private key pair of the shared account after the verification is passed, so as to ensure the legitimacy of the creation certificate and improve the effectiveness of the shared account creation. Receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator; verify the account public key signature according to the public key of the account creator to ensure that the account public key is not counterfeited. If the verification is passed, a shared account identifier is generated, and the account public key is associated with the shared account identifier of the shared account. Based on this, in the process of creating a shared account, the user information of additional shared members of the shared account is avoided from being obtained or stored, thereby improving the security of user information in the process.
[0186] In one embodiment, Fig. 9 As shown, an account sharing method is provided, and the method is applied to Figure 1 The following steps are taken as an example:
[0187] Step S902: Send an authorization request to the party to be authorized through the account creator. The authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and generate a member public key based on the member private key and the account public parameters.
[0188] In some embodiments, the steps of the party to be authorized generating a member private key in response to an authorization request and generating a member public key based on the member private key and account public parameters include: generating the member private key of the party to be authorized in response to the authorization request; extracting generation parameters for generating the member public key from the account public parameters by the party to be authorized, and generating the member public key of the party to be authorized based on the generation parameters and the member private key.
[0189] Step S904, after the account creator receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized based on the account private key and the member public key of the shared account to authorize the party to be authorized as a shared member of the shared account.
[0190] In some embodiments, the step of the account creator verifying the member public key sent by the party to be authorized includes: obtaining the knowledge signature corresponding to the member public key through the account creator, and verifying whether there is a member private key corresponding to the member public key through the knowledge signature; if it exists, the account creator determines that the legitimacy check of the member public key has passed, and returns to the step of issuing a member certificate for the party to be authorized based on the account private key and the member public key of the shared account to continue execution; if it does not exist, the account creator determines that the legitimacy check of the member public key has failed, and determines that the authorization of the party to be authorized has failed. In some embodiments, the step of issuing a member certificate for the party to be authorized based on the account private key and the member public key of the shared account includes: through the account creator, using the account private key of the shared account to sign the member public key to obtain the member certificate of the party to be authorized.
[0191] In some embodiments, the method also includes: the account creator stores the member public key sent by the party to be authorized and the member certificate issued for the party to be authorized in correspondence, sends the member certificate to the party to be authorized to instruct the party to be authorized to verify the member certificate and save the member certificate after the verification is passed.
[0192] In some embodiments, the step of the party to be authorized verifying the member certificate includes: verifying the member certificate according to the account public key through the party to be authorized; if the verification of the member certificate passes, authorizing the party to be authorized as a shared member of the shared account through the account creator; if the verification of the member certificate fails, not authorizing the party to be authorized as a shared member of the shared account through the account creator.
[0193] In the above-mentioned account sharing method, the account creator sends an authorization request to the party to be authorized. The authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key according to the member private key and the account public parameters, so as to ensure that the party to be authorized has its own member private key and the corresponding member public key. After the account creator receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized according to the account private key and the member public key of the shared account, so as to authorize the party to be authorized as a shared member of the shared account. In this way, in the process of sharing the account, only the interaction between the account creator and the party to be authorized is involved, and there is no need for the server to obtain or store the user information of the additional shared members corresponding to the account, thereby improving the security of user information in the process.
[0194] The present application also provides an application scenario, which applies the above-mentioned transaction verification method of the shared account. Specifically, the application of the transaction verification method of the shared account in the application scenario is as follows: in the transaction scenario of the e-commerce platform, the server receives a transaction verification request from a shared account sent to the e-commerce platform. The transaction verification request includes a transaction instruction and a signature. The signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account. The member certificate is issued by the account creator of the shared account for the shared member according to the account private key of the shared account and the member public key of the shared member; query the target account public key corresponding to the target shared account identifier in the transaction instruction; when it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier, any shared member is allowed to initiate a transaction request for the target shared account. At this time, the server determines that the person who initiates the transaction verification request in the e-commerce platform is a shared member of the target shared account, and the server receives the transaction request of the shared member to complete the transaction operation of the shared member on the electronic platform. The shared account transaction verification method of the present application can timely and accurately verify whether the member who initiates the transaction verification request is a shared member of the target shared account without obtaining the user information of any user, thereby effectively avoiding the leakage of user information and improving the security of user information during the transaction verification process.
[0195] Of course, it is not limited to this. The transaction verification method for shared accounts provided in this application can also be applied in other application scenarios. For example, in an audio and video platform, it often involves shared members logging into the target shared account to watch or listen to the audio and video works of interest. Therefore, before the transaction, the transaction verification method for shared accounts provided in this application can be used to complete the transaction verification of audio and video product transactions.
[0196] The above application scenarios are merely illustrative. It is to be understood that the application of the transaction verification method for a shared account provided in each embodiment of the present application is not limited to the above scenarios.
[0197] In a specific embodiment, a transaction verification method for a shared account is provided, which involves an account creator, a party to be shared, and a server, wherein the account creator and the party to be shared can be the same client or different clients, without limitation. The specific implementation steps are as follows:
[0198] Step 1 (creation of a shared account): The account creator generates an asymmetric key pair. The account creator signs the public key with the private key to obtain a signature for creating a shared account; the account creator determines the request for creating a shared account based on the public key and the signature for creating a shared account, and sends it to the server. The server obtains the identity information to be verified of the account creator, and compares the identity information to be verified with each pre-stored standard identity information, and determines the identity authentication result of the account creator based on each comparison result; if the identity authentication result indicates that the identity authentication is passed, the server uses the server private key to sign the extracted public key of the account creator, determines the creation certificate, and sends the creation certificate to the account creator. The account creator verifies the creation certificate using the server public key; if the verification of the creation certificate fails, the account creator determines that the creation certificate is not issued by the server, and determines that the creation of the shared account has failed. If the verification of the creation certificate is passed, the account creator determines that the creation certificate is issued by the server, and generates the public and private key pair of the shared account through the account creator. Specifically: the account creator generates the account private key of the shared account and obtains the account public parameters; the account creator generates the corresponding account public key according to the account public parameters and the account private key. The account creator signs the account public key with the private key of the account creator to obtain the account public key signature. The account creator sends the account public key and the account public key signature to the server. The server verifies the account public key signature according to the public key of the account creator. If the verification passes, it determines that the creation fails. If the verification passes, the server saves the account public key, generates a shared account identifier, and associates the account public key with the shared account identifier of the shared account. At this time, the server determines that the creation is successful.
[0199] Step 2 (account sharing): The account creator sends an authorization request to the party to be authorized, and the authorization request includes the account public key of the shared account created by the account creator and the account public parameters of the shared account. The party to be authorized responds to the authorization request and generates the member private key of the party to be authorized; the party to be authorized extracts the generation parameters for generating the member public key from the account public parameters, and generates the member public key of the party to be authorized based on the generation parameters and the member private key. The party to be authorized sends the member public key to the account creator. The account creator obtains the knowledge signature corresponding to the member public key, and verifies whether there is a member private key corresponding to the member public key through the knowledge signature; if it does not exist, the account creator determines that the legitimacy check of the member public key has failed, and determines that the authorization of the party to be authorized has failed. If it exists, the account creator determines that the legitimacy check of the member public key has passed, and the account creator saves the member public key. The account creator signs the member public key with the account private key of the shared account, determines the member certificate issued to the party to be authorized, and sends the member certificate to the party to be authorized. The party to be authorized verifies the member certificate according to the account public key; if the verification of the member certificate is passed, the party to be authorized is authorized by the account creator as a shared member of the shared account; if the verification of the member certificate is not passed, the party to be authorized is not authorized by the account creator as a shared member of the shared account.
[0200] Step 3 (Transaction Verification): The anonymous client determines the transaction instruction according to the target shared account identifier and the number of resources to be traded. The anonymous client signs the transaction instruction according to the member private key and member certificate corresponding to the authorized shared account to obtain the signature of the transaction instruction. The anonymous client determines the transaction verification request according to the transaction instruction and the signature of the transaction instruction. The server receives the transaction verification request sent by the anonymous client and extracts the target shared account identifier from the transaction instruction; according to the correspondence between the pre-stored account public key and the shared account identifier, the target account public key corresponding to the extracted target shared account identifier is queried. The server verifies the legitimacy of the signature through the target account public key, specifically: obtain the target account public parameters of the target shared account, and determine the verification value corresponding to the account public key of the shared account according to the target account public parameters and signature; determine the reference value corresponding to the target account public key, and compare the verification value with the reference value; if the reference value is consistent with the verification value, it is determined that the legitimacy check is passed, and it is determined that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier. If the reference value is inconsistent with the verification value, it is determined that the legitimacy check has failed, and it is determined that the transaction verification request is not initiated by any shared member of the target shared account corresponding to the target shared account identifier. When it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier, any shared member is allowed to initiate a transaction request for the target shared account. The transaction request for the target shared account initiated by the shared member of the target shared account is received through the account creator; the signature of the transaction request is obtained through the account creator; the member public keys of each shared member of the target shared account are queried through the account creator, and the shared member identifier of the shared member who initiated the transaction request is determined based on the public keys of each member and the signature of the transaction request.
[0201] In this embodiment, by receiving a transaction verification request of a shared account, the transaction instruction and signature included in the transaction verification request can be known. The signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account. The member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member. In this way, according to the shared account identifier in the transaction instruction, the target shared account corresponding to the subsequent transaction request can be quickly known, and the target account public key corresponding to the shared account identifier in the transaction instruction can be accurately queried. When it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any shared member of the target shared account corresponding to the shared account identifier, any shared member is allowed to initiate a transaction request for the target shared account. In this way, without obtaining the user information of any user, it is possible to timely and accurately verify whether the member initiating the transaction verification request belongs to the shared member of the target shared account, effectively avoiding the leakage of user information and improving the security of user information during the transaction verification process. At the same time, the server cannot grasp the potential information of the association between the account creator and the shared member.
[0202] 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.
[0203] Based on the same inventive concept, the embodiment of the present application also provides a shared account transaction verification device for implementing the shared account transaction verification 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 the embodiments of the transaction verification device for one or more shared accounts provided below can refer to the limitations of the shared account transaction verification method above, and will not be repeated here.
[0204] In one embodiment, Fig.10 As shown, a transaction verification device 1000 for a shared account is provided, comprising: a receiving module 1902, a query module 1004 and a verification module 1006, wherein:
[0205] The receiving module 1002 is used to receive a transaction verification request of a shared account; the transaction verification request includes a transaction instruction and a signature, the signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member;
[0206] A query module 1004, used to query the target account public key corresponding to the target shared account identifier in the transaction instruction;
[0207] The verification module 1006 is used to allow any sharing member to initiate a transaction request for the target shared account when it is verified based on the queried target account public key and signature that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier.
[0208] In some embodiments, the query module 1004 is used to extract the target shared account identifier from the transaction instruction; and query the target account public key corresponding to the extracted target shared account identifier according to the pre-stored correspondence between the account public key and the shared account identifier.
[0209] In some embodiments, the device also includes a legitimacy verification module, which is used to perform a legitimacy verification on the signature based on the queried target account public key; if the legitimacy verification passes, it is determined that the transaction verification request is initiated by any shared member of the target shared account corresponding to the target shared account identifier; if the legitimacy verification fails, it is determined that the transaction verification request is not initiated by any shared member of the target shared account corresponding to the target shared account identifier.
[0210] In some embodiments, the legitimacy verification module is also used to obtain the target account public parameters of the target shared account, and determine the verification value corresponding to the account public key of the shared account based on the target account public parameters and signature; determine the reference value corresponding to the target account public key, and compare the verification value with the reference value; if the reference value is consistent with the verification value, it is determined that the legitimacy verification has passed; if the reference value is inconsistent with the verification value, it is determined that the legitimacy verification has failed.
[0211] In some embodiments, the device also includes an association module, which is used to receive a creation request for a shared account sent by an account creator, the creation request being generated based on the public-private key pair of the account creator; extracting the public key of the account creator from the creation request; using the server private key and the extracted public key of the account creator to issue a creation certificate for the account creator, and sending the creation certificate to the account creator to instruct the account creator to receive and verify the creation certificate and generate an account public-private key pair of the shared account after the verification is passed; receiving the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator; verifying the account public key signature based on the public key of the account creator, and if the verification is passed, generating a shared account identifier, and associating the account public key with the shared account identifier of the shared account.
[0212] In some embodiments, the device also includes a creation request generation module, which is used to generate a private key through the account creator and determine the corresponding public key based on the private key; through the account creator, sign the public key according to the private key to obtain a signature for creating a shared account; through the account creator, determine the creation request of the shared account based on the public key and the signature for creating a shared account.
[0213] In some embodiments, the device also includes a certificate creation verification module, which is used to verify the creation certificate by the account creator using the server public key; if the verification of the creation certificate is passed, the account creator determines that the creation certificate is issued by the server, and executes the steps of generating the public and private key pair of the shared account; if the verification of the creation certificate fails, the account creator determines that the creation certificate is not issued by the server, and determines that the shared account creation has failed.
[0214] In some embodiments, the device also includes an account public-private key pair generation module, which is used to generate an account private key of a shared account through an account creator and obtain account public parameters; through the account creator, a corresponding account public key is generated based on the account public parameters and the account private key.
[0215] In some embodiments, the device also includes an authorization module, which is used to send an authorization request to the party to be authorized through the account creation party, the authorization request including the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key based on the member private key and the account public parameters; after the account creation party receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized based on the account private key and the member public key of the shared account to authorize the party to be authorized as a shared member of the shared account.
[0216] In some embodiments, the device also includes a member public key verification module, which is used to obtain the knowledge signature corresponding to the member public key through the account creator, and verify whether there is a member private key corresponding to the member public key through the knowledge signature; if it exists, the account creator determines that the legitimacy check of the member public key has passed, and returns to the step of issuing a member certificate for the party to be authorized based on the account private key and the member public key of the shared account to continue execution; if it does not exist, the account creator determines that the legitimacy check of the member public key has failed, and determines that the authorization of the party to be authorized has failed.
[0217] In some embodiments, the device also includes a saving module, which is used to store the member public key sent by the party to be authorized and the member certificate issued for the party to be authorized in correspondence through the account creator, and send the member certificate to the party to be authorized to instruct the party to be authorized to verify the member certificate and save the member certificate after the verification is passed.
[0218] In some embodiments, the device also includes a determination module, which is used to receive a transaction request for a target shared account initiated by a shared member of the target shared account through an account creator; obtain a signature of the transaction request through the account creator; query the member public keys of each shared member of the target shared account through the account creator, and determine the shared member identifier of the shared member who initiated the transaction request based on the public keys of each member and the signature of the transaction request.
[0219] Based on the same inventive concept, the embodiment of the present application also provides a device for creating a shared account for implementing the method for creating a shared account 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 the creation embodiments of one or more shared accounts provided below can refer to the limitations of the method for creating a shared account above, and will not be repeated here.
[0220] In one embodiment, Fig.11 As shown, a device 1100 for creating a shared account is provided, comprising: a creation request module 1102, an extraction module 1104, a sending module 1106, a second signature module 1108 and an association module 1110, wherein:
[0221] A creation request module 1102, configured to receive a creation request for a shared account sent by an account creator, wherein the creation request is generated based on a public-private key pair of the account creator;
[0222] An extraction module 1104, configured to extract the public key of the account creator from the creation request;
[0223] The sending module 1106 is used to issue a creation certificate for the account creator by using the server private key and the extracted public key of the account creator, and send the creation certificate to the account creator to instruct the account creator to receive and verify the creation certificate and generate a public-private key pair of the shared account after the verification is passed;
[0224] The second signature module 1108 is used to receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator;
[0225] The association module 1110 is used to verify the account public key signature according to the public key of the account creator. If the verification is successful, a shared account identifier is generated and the account public key is associated with the shared account identifier of the shared account.
[0226] Based on the same inventive concept, the embodiment of the present application also provides an account sharing device for implementing the account sharing 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 account sharing embodiments provided below can refer to the limitations on the account sharing method above, and will not be repeated here.
[0227] In one embodiment, Fig.12 As shown, an account sharing device 1200 is provided, including: an authorization request sending module 1202 and an issuing module 1204, wherein:
[0228] The authorization request sending module 1202 is used to send an authorization request to the party to be authorized through the account creation direction, wherein the authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key according to the member private key and the account public parameters;
[0229] The issuing module 1204 is used to receive and verify the member public key sent by the party to be authorized through the account creator and after the verification is passed, issue a member certificate to the party to be authorized based on the account private key and the member public key of the shared account to authorize the party to be authorized as a shared member of the shared account.
[0230] Each module in the above-mentioned shared account transaction verification device, shared account creation device and account sharing device can be implemented in whole or in part by software, hardware and their combination. Each of the above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.
[0231] In one embodiment, a computer device is provided. The computer device may be a server (may be the aforementioned server), and its internal structure diagram may be as follows: Fig.13 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, 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, a computer program and a database. 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 through a network connection. When the computer program is executed by the processor, a transaction verification method for a shared account, a method for creating a shared account and an account sharing method are implemented.
[0232] Those skilled in the art will understand that Fig.13 The structure shown in the figure is only a block diagram of a part of the 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 those shown in the figure, or combine certain components, or have a different arrangement of components.
[0233] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.
[0234] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0235] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0236] 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 laws, regulations and standards of relevant countries and regions.
[0237] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods 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 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), magnetoresistive 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, etc., but are not limited to this.
[0238] 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 specification.
[0239] 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. A transaction verification method for a shared account, characterized in that: The method comprises: Receive a transaction verification request from a shared account; the transaction verification request includes a transaction instruction and a signature, the signature is obtained by signing the transaction instruction according to the member private key and member certificate of the shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member; Querying the target account public key corresponding to the target shared account identifier in the transaction instruction; When it is verified based on the queried target account public key and the signature that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier, any sharing member is allowed to initiate a transaction request for the target shared account.
2. The method according to claim 1, characterized in that The querying of the target account public key corresponding to the target shared account identifier in the transaction instruction includes: Extracting a target shared account identifier from the transaction instruction; According to the pre-stored correspondence between the account public key and the shared account identifier, the target account public key corresponding to the extracted target shared account identifier is queried.
3. The method according to claim 1, characterized in that The method further comprises: Perform a validity check on the signature based on the queried target account public key; If the legitimacy check passes, determining that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier; If the legitimacy check fails, it is determined that the transaction verification request is not initiated by any sharing member of the target shared account corresponding to the target shared account identifier.
4. The method according to claim 3, characterized in that The legitimacy verification of the signature according to the queried target account public key includes: Obtaining a target account public parameter of the target shared account, and determining a verification value corresponding to the account public key of the shared account according to the target account public parameter and the signature; Determining a reference value corresponding to the target account public key, and comparing the verification value with the reference value; If the reference value is consistent with the verification value, it is determined that the legality check has passed; If the reference value is inconsistent with the verification value, it is determined that the legality check fails.
5. The method according to claim 1, characterized in that Before receiving the transaction verification request of the shared account, the method further includes: Receiving a shared account creation request sent by an account creator, wherein the creation request is generated according to a public-private key pair of the account creator; Extracting the public key of the account creator from the creation request; Using the server private key and the extracted public key of the account creator, a creation certificate is issued to the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the public and private key pair of the shared account after the verification is passed; Receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator; The account public key signature is verified according to the public key of the account creator. If the verification is successful, a shared account identifier is generated, and the account public key is associated with the shared account identifier of the shared account.
6. The method according to claim 5, characterized in that The steps of generating the creation request of the shared account include: Generate a private key through the account creator, and determine the corresponding public key based on the private key; The account creator signs the public key according to the private key to obtain a signature for creating a shared account; The account creator determines a request to create the shared account based on the public key and a signature on creating the shared account.
7. The method according to claim 5, characterized in that The step of the account creator verifying the creation certificate comprises: The account creator verifies the creation certificate using the server public key; If the verification of the creation certificate is passed, the account creator determines that the creation certificate is issued by the server, and executes the step of generating the public and private key pair of the shared account; If the verification of the creation certificate fails, the account creator determines that the creation certificate is not issued by the server, and determines that the shared account creation fails.
8. The method according to claim 5, characterized in that The step of generating a public and private key pair of the shared account by the account creator includes: Generate the account private key of the shared account through the account creator, and obtain the account public parameters; The account creator generates a corresponding account public key according to the account public parameters and the account private key.
9. The method according to claim 1, characterized in that: Before receiving the transaction verification request of the shared account, the method further includes: Sending an authorization request to the party to be authorized through the account creator, wherein the authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key according to the member private key and the account public parameters; After the account creator receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized based on the account private key of the shared account and the member public key to authorize the party to be authorized as a shared member of the shared account.
10. The method according to claim 9, characterized in that The step of the account creator verifying the member public key sent by the party to be authorized includes: Obtain the knowledge signature corresponding to the member public key through the account creator, and verify whether there is a member private key corresponding to the member public key through the knowledge signature; If it exists, the account creator determines that the legitimacy check of the member public key has passed, and returns to the step of issuing a member certificate for the party to be authorized based on the account private key of the shared account and the member public key to continue the execution; If it does not exist, the account creator determines that the legitimacy check of the member public key has failed, and determines that the authorization of the party to be authorized has failed.
11. The method according to claim 9, characterized in that The method further comprises: The account creator stores the member public key sent by the party to be authorized and the member certificate issued for the party to be authorized in correspondence, and sends the member certificate to the party to be authorized to instruct the party to be authorized to verify the member certificate and save the member certificate after the verification is passed.
12. The method according to claim 1, characterized in that The method further comprises: Receiving, through the account creator, a transaction request for the target shared account initiated by a sharing member of the target shared account; Obtaining a signature of the transaction request through the account creator; The account creator queries the member public keys of each shared member of the target shared account, and determines the shared member identifier of the shared member who initiates the transaction request according to the public keys of each member and the signature of the transaction request.
13. A method for creating a shared account, characterized in that: The method comprises: Receiving a shared account creation request sent by an account creator, wherein the creation request is generated according to a public-private key pair of the account creator; Extracting the public key of the account creator from the creation request; Using the server private key and the extracted public key of the account creator, a creation certificate is issued to the account creator, and the creation certificate is sent to the account creator to instruct the account creator to receive and verify the creation certificate and generate the public and private key pair of the shared account after the verification is passed; Receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator; The account public key signature is verified according to the public key of the account creator. If the verification is successful, a shared account identifier is generated, and the account public key is associated with the shared account identifier of the shared account.
14. An account sharing method, characterized in that: The method comprises: Sending an authorization request to the party to be authorized through the account creator, wherein the authorization request includes the account public key of the shared account and the account public parameters of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key according to the member private key and the account public parameters; After the account creator receives and verifies the member public key sent by the party to be authorized and the verification is passed, a member certificate is issued to the party to be authorized based on the account private key of the shared account and the member public key to authorize the party to be authorized as a shared member of the shared account.
15. A transaction verification device for a shared account, characterized in that: The device comprises: A receiving module, configured to receive a transaction verification request of a shared account; the transaction verification request includes a transaction instruction and a signature, the signature is obtained by signing the transaction instruction according to a member private key and a member certificate of a shared member corresponding to the shared account, and the member certificate is issued by the account creator of the shared account to the shared member according to the account private key of the shared account and the member public key of the shared member; A query module, used to query a target account public key corresponding to a target shared account identifier in the transaction instruction; The verification module is used to allow any sharing member to initiate a transaction request for the target shared account when it is verified based on the queried target account public key and the signature that the transaction verification request is initiated by any sharing member of the target shared account corresponding to the target shared account identifier.
16. A device for creating a shared account, characterized in that: The device comprises: A creation request module, configured to receive a creation request for a shared account sent by an account creator, wherein the creation request is generated based on a public-private key pair of the account creator; An extraction module, used to extract the public key of the account creator from the creation request; A sending module, used to use the server private key and the extracted public key of the account creator to issue a creation certificate for the account creator, and send the creation certificate to the account creator to instruct the account creator to receive and verify the creation certificate and generate the public and private key pair of the shared account after the verification is passed; A second signature module is used to receive the account public key in the account public-private key pair sent by the account creator and the account public key signature generated for the account public key using the private key of the account creator; The association module is used to verify the signature of the account public key according to the public key of the account creator, generate a shared account identifier if the verification is successful, and associate the account public key with the shared account identifier of the shared account.
17. An account sharing device, characterized in that: The device comprises: An authorization request sending module, used to send an authorization request to a party to be authorized through an account creation direction, wherein the authorization request includes an account public key of a shared account and an account public parameter of the shared account, so as to instruct the party to be authorized to generate a member private key in response to the authorization request and to generate a member public key according to the member private key and the account public parameter; The issuing module is used to receive and verify the member public key sent by the party to be authorized through the account creator and after the verification is passed, issue a member certificate to the party to be authorized based on the account private key of the shared account and the member public key to authorize the party to be authorized as a shared member of the shared account.
18. 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 14 are implemented.
19. 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 14 are implemented.
20. 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 14 are implemented.
Citation Information
Patent Citations
Electronic money system and electronic money trading method
CN101652793A
A method and apparatus for authorizing data in organization
CN109995786A
