CN114827175B - Registration method, electronic device, and readable storage medium - Google Patents
Registration method, electronic device, and readable storage medium Download PDFInfo
- Publication number
- CN114827175B CN114827175B CN202110064962.3A CN202110064962A CN114827175B CN 114827175 B CN114827175 B CN 114827175B CN 202110064962 A CN202110064962 A CN 202110064962A CN 114827175 B CN114827175 B CN 114827175B
- Authority
- CN
- China
- Prior art keywords
- merchant
- account
- address
- key
- management system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Accounting & Taxation (AREA)
- Signal Processing (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Strategic Management (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Power Engineering (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a registration method, electronic equipment and a readable storage medium, aiming at reducing difficulty of business development of merchants based on a blockchain network. The registration method is applied to a middleware system, the middleware system is in communication connection with part of nodes of a blockchain network, the middleware system is used for receiving service messages sent by merchant equipment, analyzing the received service messages into transactions, calling a key management system to sign the analyzed transactions, and submitting the signed transactions to the blockchain network for execution; the registration method comprises the following steps: responding to an account registration request sent by merchant equipment, and calling the key management system to generate a key pair, wherein the key pair comprises a private key, a public key and an account address; receiving an account address returned by the key management system; and returning the account address to the merchant equipment.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a registration method, an electronic device, and a readable storage medium.
Background
The block chain technology is realized on a block chain network, distributed node equipment (hereinafter referred to as nodes for short) in the block chain network realizes generation and consensus of block data by running a block chain program, finally realizes a tamper-proof mechanism of the data, and provides a safe and reliable technical new idea for service development.
The blockchain technology can be applied to various business scenes, such as financial field, electronic commerce field, commodity or raw material tracing field, electronic certificate storing field and the like, and can be used for developing business due to the fact that the blockchain technology realizes a data tamper-proof mechanism, so that the trust crisis among parties involved in the business can be solved.
In a blockchain network, account addresses correspond to user assets, the importance of the account addresses being similar to bank accounts in a centralized system. It can be seen that merchants (e.g., banks, securities companies, trusted companies, etc.) need to register (offer) account addresses for their users in order to conduct business based on a blockchain network. However, for the merchant, in order to realize the account registration function, a large technical resource needs to be input, so that the difficulty of the merchant to develop the service based on the blockchain network is large.
Disclosure of Invention
The embodiment of the invention aims to provide a registration method, electronic equipment and a readable storage medium, aiming at reducing difficulty of business development of merchants based on a blockchain network. The specific technical scheme is as follows:
in a first aspect of the embodiment of the present invention, a registration method is provided, which is applied to a middleware system, where the middleware system is in communication connection with a part of nodes of a blockchain network, and the middleware system is configured to receive a service packet sent by a merchant device, parse the received service packet into a transaction, invoke a key management system to sign the parsed transaction, and submit the signed transaction to the blockchain network for execution; the method comprises the following steps:
responding to an account registration request sent by merchant equipment, and calling the key management system to generate a key pair, wherein the key pair comprises a private key, a public key and an account address;
receiving an account address returned by the key management system;
and returning the account address to the merchant equipment.
Optionally, the number of merchants is multiple, and the account registration request carries a merchant ID; after receiving the account address returned by the key management system, the method further comprises the following steps:
And establishing a corresponding relation between the merchant and the account aiming at the merchant ID carried by the account registration request and the account address returned by the key management system.
Optionally, other nodes of the blockchain network are in communication connection with other middleware systems, the other middleware systems are used for receiving service messages sent by corresponding merchant equipment, analyzing the received service messages into one or more transactions, submitting the one or more transactions to the blockchain network for execution, wherein each transaction in the one or more transactions carries a message identifier of the service message, and a plurality of transactions in the one or more transactions also carry account addresses recorded in the service message and used for participating in the service; the method further comprises the steps of:
obtaining a transaction from the blockchain network;
recombining the service message according to one or more transactions carrying the same message identifier;
inquiring the corresponding relation between the merchant and the account according to the account address recorded in the recombined service message so as to determine the merchant corresponding to the account address;
and sending the recombined business message to the determined merchant equipment of the merchant.
Optionally, the key management system is an encryptor, the number of merchants and the number of encryptors are multiple, and a corresponding relationship exists between the merchants and the encryptors; the account registration request carries a merchant ID; the method for calling the key management system to generate the key pair in response to the account registration request sent by the merchant equipment comprises the following steps:
Responding to an account registration request sent by merchant equipment, and determining an encryption machine address corresponding to a merchant ID according to the merchant ID carried by the account registration request;
and forwarding the account registration request to the determined address of the encryptor so that the corresponding encryptor generates a key pair.
Optionally, before registering the account, the method further comprises:
obtaining an encryptor address corresponding to a merchant to be registered;
and sending a merchant registration request to the obtained encryptor address, so that the corresponding encryptor generates a key pair, wherein the key pair comprises a private key, a public key and a merchant address.
Optionally, the method further comprises:
receiving a merchant address and a public key returned by the encryptor;
establishing a corresponding relation between a merchant ID and the merchant address, wherein the merchant ID is the merchant ID of the merchant to be registered;
and submitting the public key to a gateway corresponding to the middleware system, wherein the middleware system is in communication connection with part of nodes of the blockchain network through the gateway.
Optionally, the method further comprises:
responding to a business message sent by a merchant device, and analyzing the business message into a transaction, wherein the business message carries a merchant ID and an account address;
inquiring the corresponding relation between the merchant ID and the merchant address according to the merchant ID carried by the service message, and determining the merchant address corresponding to the merchant ID;
Determining an encryption machine address corresponding to the merchant ID according to the merchant ID carried by the service message;
the analyzed transaction, the account address carried by the business message and the determined merchant address are sent to the determined encryptor address, so that the corresponding encryptor signs the transaction by utilizing a private key corresponding to the account address to obtain first signature data, and signs the transaction and the first signature data by utilizing the private key corresponding to the merchant address to obtain second signature data;
receiving first signature data and second signature data returned by an encryptor;
and sending the analyzed transaction, the first signature data and the second signature data to a gateway corresponding to the middleware system, so that the gateway performs signature verification on the second signature data by using a corresponding public key, and submitting the transaction and the first signature data to a node of the blockchain network under the condition that the signature verification passes.
Optionally, the number of the merchants and the key management systems are multiple, the multiple key management systems are distributed in different areas, and each key management system is used for managing one or more encryption machines; each merchant corresponds to a key management system and also corresponds to an encryption machine managed by the key management system, and the key management system stores the corresponding relation between the merchant and the encryption machine; the account registration request carries a merchant ID; the method for calling the key management system to generate the key pair in response to the account registration request sent by the merchant equipment comprises the following steps:
Responding to an account registration request sent by merchant equipment, and determining a key management system corresponding to the merchant ID according to the merchant ID carried by the account registration request;
and forwarding an account registration request to the determined key management system, so that the key management system determines an encryption machine corresponding to the merchant ID according to the merchant ID carried by the account registration request, and then sending an account registration command to the determined encryption machine, so that the corresponding encryption machine generates a key pair.
In a second aspect of the embodiment of the present invention, there is provided an electronic device including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete communication with each other through the communication bus;
the memory is used for storing a computer program;
the processor is configured to implement the registration method provided by any embodiment of the present invention when executing the program stored in the memory.
In a third aspect of embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the registration method provided by any of the embodiments of the present invention.
In the invention, the middleware system is in communication connection with part of nodes of the block chain network, and the middleware system can develop services based on the block chain network. The merchant equipment can send the service message to the middleware system, after the middleware system receives the service message, the service message is analyzed into a transaction, the key management system is called to sign the transaction, and the signed transaction is submitted to the blockchain network for execution. Therefore, the business is developed by the merchant through the middleware system, and the merchant does not perceive the complexity of the blockchain technology, so that the difficulty of the business development by the merchant based on the blockchain network can be reduced.
In addition, the merchant device may send an account registration request to the middleware system when the merchant needs to register an account. And the middleware system responds to the account registration request and calls the key management system to generate a private key, a public key and an account address. The middleware system receives the account address returned by the key management system and returns the account address to the merchant equipment. Therefore, the merchant equipment can realize business and account registration through the middleware system, and the difficulty of the merchant in developing the business is greatly simplified.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It is evident that the drawings in the following description are only some embodiments of the present invention and that other drawings may be obtained from these drawings by those of ordinary skill in the art without inventive effort.
FIG. 1 is a schematic diagram of a business processing system according to an embodiment of the present invention;
FIG. 2 is a flow chart of a registration method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a business process according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a registered account according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a middleware system participating in a service according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of a signature according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of a registered account according to another embodiment of the present invention;
fig. 8 is a schematic diagram of an electronic device according to an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The block chain technology is realized on a block chain network, distributed node equipment (hereinafter referred to as nodes for short) in the block chain network realizes generation and consensus of block data by running a block chain program, finally realizes a tamper-proof mechanism of the data, and provides a safe and reliable technical new idea for service development. In a blockchain network, account addresses correspond to user assets, the importance of the account addresses being similar to bank accounts in a centralized system. It can be seen that merchants (e.g., banks, securities companies, trusted companies, etc.) need to register (offer) account addresses for their users in order to conduct business based on a blockchain network. However, for the merchant, in order to realize the account registration function, a large technical resource needs to be input, so that the difficulty of the merchant to develop the service based on the blockchain network is large.
In view of this, the present invention proposes a registration method, an electronic device, and a readable storage medium by the following embodiments, which aim to reduce difficulty of a merchant to develop a service based on a blockchain network.
Referring to fig. 1, fig. 1 is a schematic diagram of a service processing system according to an embodiment of the present invention. As shown in fig. 1, the service processing system includes: a blockchain network, a plurality of middleware systems, and a plurality of merchant devices. The merchant equipment can be in communication connection with a middleware system, and the middleware system can be in communication connection with part of nodes in the blockchain network. In this manner, the merchant device enables indirect communication with the blockchain network through the middleware system.
Specifically, when the merchant needs to develop the service, the merchant can send a service message to the middleware system through the merchant equipment. The middleware system analyzes the business message sent by the merchant equipment into a transaction, invokes the key management system to sign the analyzed transaction, and submits the signed transaction to the blockchain network for execution. In addition, the middleware system synchronizes blocks generated by the blockchain network or synchronizes a ledger database of the blockchain network to obtain information from the blockchain network. The middleware system reassembles the information acquired from the blockchain network into service messages, and then pushes the recombined service messages to the merchant equipment. In this manner, the merchant device enables indirect communication with the blockchain network through the middleware system.
Optionally, in some embodiments, the information transfer between the merchant device and the middleware system is specifically based on the communication message. When the merchant equipment transmits service information to the middleware system, the merchant equipment packages the service message in a message body of the communication message, and the service message is sent to the middleware system along with the communication message by the merchant equipment. Likewise, when the middleware system transmits service information to the merchant device, the middleware system encapsulates the service message in a message body of the communication message, and the service message is sent to the merchant device by the middleware system together with the communication message. Wherein, the communication message can be selected from: hypertext transfer protocol messages (HTTP), user datagram protocol messages (UDP), etc. It should be noted that the present invention does not limit the type of the communication message.
In the invention, the middleware system encapsulates the complex interface of the blockchain network into a simple and standard financial service interface and provides the interface for the merchant equipment, thereby reducing the interaction difficulty between the merchant equipment and the blockchain network.
In the invention, the middleware system can be a software program or a hardware device. In the case where the middleware system is a software program, the middleware system may be deployed in a certain node of the blockchain network, may be deployed in a certain merchant device, and may also be deployed in a certain device or devices between the blockchain network and the merchant device.
As shown in fig. 1, each merchant device corresponds to one middleware system, which may correspond to a plurality of merchant devices. Each merchant device realizes indirect communication with the blockchain network through a corresponding middleware system.
In specific implementation, different merchant groups respectively correspond to different middleware systems. To facilitate understanding, by way of example, multiple branches of a bank and financial institutions cooperating with the bank may be provided as a merchant community, corresponding to a middleware system. For example, a plurality of branches of the bank a, securities companies cooperating with the bank a, trusted companies cooperating with the bank a, and the like are taken as a merchant group, and collectively correspond to the middleware system a, and the middleware system a is operated and maintained by the head office of the bank a. For example, a plurality of branches of the bank B, village banks cooperating with the bank B, and a fund management company cooperating with the bank a are taken as another merchant group, and collectively correspond to the middleware system B, and the middleware system B is operated and maintained by the head office of the bank B. In this scenario, by implementing the following specific embodiments of the present invention, when each merchant processes a service using a blockchain network, service information can be conveniently transferred between different merchants (for example, between a branch of bank a and a branch of bank B) through the blockchain network.
As shown in fig. 1, a merchant may register an account for its customers (also referred to as users), and since a merchant typically has multiple customers, a merchant may have multiple accounts under it.
In the present invention, an account may be characterized by a key pair. One key pair contains a private key, a public key, and an account address, which, as previously described, corresponds to a user asset, the importance of which is similar to a bank account number in a centralized system. While the private key is used to sign transactions involving the account, the importance of the private key is similar to the account password in a centralized system.
In the invention, the key pair is generated by the key management system, and the private key is stored by the key management system so as to ensure the security of the private key. The merchant is used for saving account addresses, and each account address saved by the merchant can be regarded as an account opened by the user at the merchant.
In the above, the present invention has been described with respect to the service processing system shown in fig. 1, which may be used to implement the registration method proposed by the present invention. However, it should be noted that the implementation of the registration method is not dependent on the service processing system shown in fig. 1, and the service processing system shown in fig. 1 should not be construed as limiting the present invention.
Referring to fig. 2, fig. 2 is a flowchart of a registration method according to an embodiment of the present invention, where the registration method is applied to a middleware system. As mentioned above, the middleware system is communicatively connected with a part of nodes of the blockchain network, and is configured to receive a service packet sent by a merchant device, parse the received service packet into a transaction, invoke the key management system to sign the parsed transaction, and submit the signed transaction to the blockchain network for execution. As shown in fig. 2, the registration method includes the steps of:
step S21: responding to an account registration request sent by merchant equipment, and calling the key management system to generate a key pair, wherein the key pair comprises a private key, a public key and an account address;
step S22: receiving an account address returned by the key management system;
step S23: and returning the account address to the merchant equipment.
In the invention, when a merchant develops a new customer and needs to open an account for the new customer, the merchant can send an account registration request to a middleware system through merchant equipment. After receiving the account registration request, the middleware system invokes the key management system to generate a key pair for the new client. The middleware system receives the account address returned by the key management system and returns the account address to the merchant equipment. Thus, when the merchant device receives a new account address, registration of the new account is completed.
Wherein the private key of the new account is stored in the key management system to ensure the security of the private key. The public key and account address of the new account may also be stored in the key management system together with the private key of the new account as a key pair. In addition, the account address of the new account is also saved on the merchant side. In this way, the merchant may subsequently conduct a business associated with the account address based on the account address.
In the invention, the middleware system is in communication connection with part of nodes of the block chain network, and the middleware system can develop services based on the block chain network. The merchant equipment can send the service message to the middleware system, after the middleware system receives the service message, the service message is analyzed into a transaction, the key management system is called to sign the transaction, and the signed transaction is submitted to the blockchain network for execution. Therefore, the business is developed by the merchant through the middleware system, and the merchant does not perceive the complexity of the blockchain technology, so that the difficulty of the business development by the merchant based on the blockchain network can be reduced.
Further, by implementing the above steps S21 to S23, the merchant device may send an account registration request to the middleware system when the merchant needs to register an account. And the middleware system responds to the account registration request and calls the key management system to generate a private key, a public key and an account address. The middleware system receives the account address returned by the key management system and returns the account address to the merchant equipment. Therefore, the merchant equipment can realize business and account registration through the middleware system, and the difficulty of the merchant in developing the business is greatly simplified.
Optionally, in some embodiments, the key management system may invoke a software development kit SDK of the blockchain network, where the software development kit includes a key pair generation algorithm, and a private key, a public key, and an address generated by the key pair generation algorithm meet requirements of the blockchain network on the private key, the public key, and the address. When the key management system receives a calling request of the middleware system, the key management system calls a Software Development Kit (SDK) of the blockchain network, so that a key pair generation algorithm in the Software Development Kit (SDK) is executed, and a private key, a public key, an address and the like meeting the requirements are generated.
Optionally, in other specific embodiments, a key pair generating algorithm is preset in the key management system, and a private key, a public key and an address generated by the key pair generating algorithm meet requirements of the blockchain network on the private key, the public key and the address. After the key management system receives the call request of the middleware system, the key management system executes a preset key pair generation algorithm, and then generates a private key, a public key, an address and the like which meet the requirements.
Optionally, in some embodiments, the number of merchants is multiple, and the account registration request carries a merchant ID. After receiving the account address returned by the key management system, the middleware system can also establish a corresponding relation between the merchant and the account according to the merchant ID carried by the account registration request and the account address returned by the key management system.
In specific implementation, the middleware system stores a merchant table, a plurality of merchant IDs are recorded in the merchant table, and an account address belonging to the merchant is recorded under each merchant ID entry. For ease of understanding, table 1 is an exemplary merchant table, as shown in table 1.
Table 1 illustrates a merchant list
When the middleware system receives an account registration request and receives a new account address returned by the key management system, the middleware system reads a merchant ID from the account registration request, then takes the read merchant ID as an index, searches the merchant ID from a merchant table shown in the table 1, and then adds the received account address to the entry of the merchant ID. In this way, a correspondence between the new account and the merchant is established.
Optionally, in some embodiments, other nodes of the blockchain network are communicatively connected to other middleware systems, and the other middleware systems are configured to receive a service packet sent by a corresponding merchant device, parse the received service packet into one or more transactions, and submit the one or more transactions to the blockchain network for execution, where each transaction of the one or more transactions carries a packet identifier of the service packet, and several transactions of the one or more transactions further carry account addresses recorded in the service packet for participating in a service.
The middleware system may obtain a transaction from the blockchain network; recombining the service message according to one or more transactions carrying the same message identifier; inquiring the corresponding relation between the merchant and the account according to the account address recorded in the recombined service message so as to determine the merchant corresponding to the account address; and sending the recombined business message to the determined merchant equipment of the merchant. Therefore, the middleware system pushes the service message to the merchant participating in the service, so that the merchant can obtain service details according to the service message.
For ease of understanding, referring to fig. 3, fig. 3 is a schematic diagram illustrating a service processing procedure according to an embodiment of the present invention. As shown in fig. 3, the middleware system a is communicatively connected to a part of nodes of the blockchain network through the gateway a, the middleware system b is communicatively connected to another part of nodes of the blockchain network through the gateway b, and the middleware system c is communicatively connected to the rest of nodes of the blockchain network through the gateway c.
As shown in FIG. 3, the merchants corresponding to the middleware system a comprise SHPF-003, SHPF-011 and HTZQ-001 shown in Table 1, the merchants corresponding to the middleware system b comprise HXYH-001, HXYH-002 and HXYH-006, and the merchants corresponding to the middleware system c comprise BHYH-011 and ZXZQ-001. Note that, each merchant ID (i.e., character strings of SHPF-003, SHPF-011, etc.) shown in fig. 3 is merely illustrative.
As shown in FIG. 3, when a customer of merchant HXYH-001 needs to make a batch transfer to multiple accounts, merchant HXYH-001 receives a batch transfer request from its customer. In response thereto, merchant HXYH-001 generates a service message and sends the service message to middleware system b. The service message is recorded with: an asset transfer-out account address, a plurality of asset transfer-in account addresses, an asset amount to be transferred to by each asset transfer-in account address, and a business type identification. Wherein, the service type identifier characterizes the service type of the service message for processing. Because the service message is used for processing batch transfer service, the service type identifier of the service message is used for representing batch transfer service. For example, the service type identification of the service message may be in the form of an SMTBT.
The middleware system b is preset with a plurality of message analysis strategies for analyzing the service messages, each message analysis strategy corresponds to one service type identifier respectively and is used for analyzing the service messages containing the corresponding service type identifiers so as to obtain one or more transactions related to the corresponding service types. In particular, a message parsing policy is actually a section of computer program, and the middleware system b executes the message parsing policy by running the section of computer program. The message analysis strategy is at least used for limiting the message analysis operation as follows:
1. The transaction quantity required to be analyzed by the business message and the transaction type of each transaction;
2. defining transaction data which each transaction needs to carry; and for each transaction data, defining which field of the business message the transaction data is acquired from, and defining which field of the transaction template the transaction data is filled into;
3. and filling the message identification of the service message into each parsed transaction.
As shown in fig. 3, after the middleware system b receives the service message sent by the merchant HXYH-001, the middleware system b reads the service type identifier SMTBT from the service message, uses the read service type identifier SMTBT as an index, searches a message analysis policy corresponding to the service type identifier SMTBT from a plurality of preset message analysis policies, and analyzes the service message into a plurality of transactions based on the found message analysis policy. Each of the plurality of transactions carries a message identifier of the service message, and assuming that the message identifier of the service message is M52f7x20f499, each transaction carries a message identifier M52f7x20f499. The transaction type of a portion of the plurality of transactions is a transfer transaction, each transfer transaction carrying an asset transfer-out account address and an asset transfer-in account address.
It should be noted that the above limitation of the message parsing policy to the message parsing operation is merely an example. Any modifications, equivalent substitutions, improvements, or the like, which are within the spirit and principles of the examples described above, are intended to be included within the scope of the present invention.
As shown in fig. 3, the middleware system b submits the parsed transaction to the blockchain network for execution through the gateway b. It should be noted that the present invention is not limited to the specific manner in which the blockchain network performs the transaction. To simplify the drawing, the specific process by which the blockchain network performs transactions is not shown in fig. 1.
It should also be noted that middleware system b may invoke the key management system to sign the transaction before submitting the transaction to the blockchain network. For how the key management system signs the transaction, reference is made to the following description of the present invention, which is not repeated here.
As shown in fig. 3, the middleware system a continuously synchronizes the blocks generated by the blockchain network through the gateway a and reads the transactions recorded by the blocks from the synchronized blocks. The middleware system a reorganizes the service messages according to one or more transactions carrying the same message identification. And the middleware system a inquires the corresponding relation between the merchant and the account according to the account address recorded in the recombined business message so as to determine the merchant corresponding to the account address, and then sends the recombined business message to the merchant equipment of the determined merchant.
In addition to synchronizing the blocks of the blockchain network, the middleware system a may synchronize the ledger database of the blockchain network to read transactions from ledger data. To simplify the drawing, the manner in which middleware system a synchronizes blocks from the blockchain network is only schematically shown in fig. 3.
In specific implementation, for each read transaction, the middleware system a detects a message identifier carried by the transaction, and uses one or more transactions carrying the same message identifier as a group of transactions.
In specific implementation, a plurality of message reorganization strategies for reorganizing service messages are preset in the middleware system a, each message reorganization strategy corresponds to one service type identifier respectively and is used for assembling a group of transactions carrying the corresponding service type identifier so as to reorganize the corresponding service messages. In particular, a message reassembly policy is actually a section of computer program, and the middleware system a executes the message reassembly policy by running the section of computer program. The message reorganization strategy is at least used for limiting the message reorganization operation as follows:
1. Transaction demand defined for reassembling the traffic message;
2. message data which is needed to be contained in a message header of the reconstituted service message; and for each message data that the message header needs to contain, limiting which field of which transaction is specifically from which to acquire the message data, and limiting which field of the message header is filled with the message data;
3. the service data needed to be contained in the message body of the reconstituted service message; and for each service data that the message body needs to contain, defining which field of which transaction the service data is acquired from, and defining which field of the message body the service data is filled with.
For the limitation of the 1 st point, in a specific implementation, after the middleware system a searches a corresponding message reorganization strategy for a group of transactions, the transaction demand defined by the message reorganization strategy is read. The middleware system a then counts the number of transactions that the set of transactions contains. Finally, the middleware system a compares the transaction quantity contained in the group of transactions with the transaction demand quantity, so as to judge whether the transaction quantity and the transaction demand quantity are equal.
If the two are not equal, the middleware system a pauses the message reorganization operation, counts the transaction quantity contained in the group of transactions again after waiting for the preset time length, and compares the transaction quantity with the transaction demand. It should be noted that, during the suspension of the message reassembly operation, the middleware system a still continuously synchronizes the blocks, reads the transactions from the synchronized blocks, and adds the transactions to a corresponding group of transactions according to the message identifier carried by the read transactions.
If the two are equal, the middleware system a continues to acquire the message data and the service data for recombining the service message from the group of transactions based on the definition of the 2 nd point and the 3 rd point of the message recombination strategy so as to recombine the service message.
In specific implementation, after the middleware system a reassembles the service message, it is detected whether the service message contains an account address. In the case that the service message includes an account address, the middleware system a refers to the merchant table (i.e., the correspondence between merchants and accounts) shown in table 1 for each account address, and determines whether the account address and the corresponding merchant are recorded in table 1. And if so, forwarding the recombined business message to the merchant. If not, repeating the operation for the next account address.
For example, the currently recombined service message of the middleware system a is exactly the service message sent by the merchant HXYH-001 and used for batch transfer. The transferring account addresses of the assets recorded in the service message comprise: YEZYh7 … jkeux, DH07ZE … 9Tyc K, HS3gWZ … SLTTGp. The middleware system a first looks up the merchant table shown in table 1 for the account address YEZYh7 … jkeux. Since the account address YEZYh7 … jkeux is not recorded in the merchant table, the middleware system a will not push the service message to the merchant temporarily.
The middleware system a then proceeds to look up the merchant table shown in table 1 for the account address DH07ZE … 9Tyc 5K. Because the account address DH07ZE … 9Tyc5K and the corresponding merchant SHPF-003 are recorded in the merchant table, the account address DH07ZE … 9Tyc K belonging to the merchant SHPF-003 is described to participate in the batch transfer service. In response, middleware system a pushes the service message to the merchant SHPF-003 device.
The middleware system a then proceeds to look up the merchant table shown in table 1 for the account address HS3gWZ … SLTTGp. Because the account address HS3gWZ … SLTTGp and the corresponding merchant SHPF-011 are recorded in the merchant table, the account address HS3gWZ … SLTTGp belonging to the merchant SHPF-011 is described to participate in batch transfer service. In response, middleware system a pushes the service message to the merchant SHPF-011 device.
It should be noted that, the middleware system b and the middleware system c may acquire the transaction from the blockchain network in the same manner, reorganize the service message according to one or more transactions carrying the same message identifier, and then query the corresponding relationship between the merchant and the account according to the account address recorded in the reorganized service message, so as to determine the merchant corresponding to the account address, and finally send the reorganized service message to the merchant equipment of the determined merchant. This process is not shown in fig. 3 to simplify the drawing.
It should be further noted that, the middleware system a and the middleware system c may also receive the service message sent by the merchant device in the same manner, parse the service message into a transaction, and submit the transaction to the blockchain network signature. This process is not shown in fig. 3 to simplify the drawing.
In the invention, the middleware system creates the corresponding relation between the merchant and the account during the account registration, and the middleware system acquires the transaction and reforms the service message during the service processing, and pushes the reform service message to the corresponding merchant equipment by inquiring the corresponding relation between the merchant and the account, so that each party of the service can acquire the service message, thereby acquiring the service details according to the service message.
Optionally, in some embodiments, referring to fig. 4, fig. 4 is a schematic diagram of a registered account according to an embodiment of the present invention. As shown in fig. 4, the key management system is an encryptor, and the number of merchants and encryptors is multiple. Wherein, there is a correspondence between the merchant and the encryptor.
In particular, as shown in fig. 4, an encryptor may be used by a merchant. Or two or more merchants may share one encryption machine.
In particular implementations, as shown in fig. 4, the encryptor may be deployed on the merchant side, with the merchant managing the encryptor. Or multiple encryptors may be deployed and managed centrally.
When the middleware system receives the account registration request, the middleware system may perform the following substeps in order to invoke the key management system to generate a key pair:
substep S21-1: responding to an account registration request sent by merchant equipment, and determining an encryption machine address corresponding to a merchant ID according to the merchant ID carried by the account registration request; the merchant ID carried by the account registration request is as follows: a merchant ID of the merchant that initiated the account registration request;
substep S21-2: and forwarding the account registration request to the determined address of the encryptor so that the corresponding encryptor generates a key pair.
In specific implementation, the middleware system records the corresponding relation between the merchant ID and the encryptor address. After receiving the account registration request, the middleware system reads the merchant ID from the account registration request, then uses the read merchant ID as an index, queries the encryptor address corresponding to the merchant ID from the corresponding relation between the merchant ID and the encryptor address, and finally forwards the account registration request to the determined encryptor address, so that the corresponding encryptor generates a key pair.
In the invention, by arranging a plurality of encryptors which are respectively used for generating and managing the key pairs for the corresponding merchants, the security of the key pairs can be improved, especially when the encryptors are deployed on the side of the merchants.
Alternatively, in some embodiments, the merchant may be pre-registered prior to registering the account for the merchant. For the process of registering merchants, as shown in FIG. 4: the middleware system obtains the encryptor address corresponding to the merchant to be registered, and then sends a merchant registration request to the obtained encryptor address, so that the corresponding encryptor generates a key pair, wherein the key pair comprises a private key, a public key and a merchant address.
In the specific implementation, the merchant to be registered can be provided with a new encryptor in advance, and after checking the registration data of the merchant to be registered, the auditor inputs the encryptor address of the new encryptor to the middleware system and inputs the merchant registration command to the middleware system. After receiving the encryptor address and the merchant registration command, the middleware system responds to the merchant registration command and sends a merchant registration request to the encryptor address, so that the new encryptor generates a key pair, and the key pair comprises a private key, a public key and an address. Wherein the address is used as the merchant address of the new merchant (i.e., the merchant to be registered).
Optionally, in some embodiments, as shown in fig. 4, after sending the merchant registration request to the encryptor address, the middleware system may further receive a merchant address and a public key returned by the corresponding encryptor, and establish a correspondence between a merchant ID and the merchant address, where the merchant ID is the merchant ID of the merchant to be registered, and submit the public key to a gateway corresponding to the middleware system. As previously described, the middleware system is communicatively coupled to a portion of the nodes of the blockchain network through the gateway.
Optionally, in some embodiments, the middleware system is further configured to execute a service. Referring to fig. 5, fig. 5 is a schematic diagram of a middleware system participating in a service according to an embodiment of the present invention. As shown in fig. 5, during participation in a service, the middleware system performs the steps of:
step S51: responding to a business message sent by a merchant device, and analyzing the business message into a transaction, wherein the business message carries a merchant ID and an account address;
step S52: inquiring the corresponding relation between the merchant ID and the merchant address according to the merchant ID carried by the service message, and determining the merchant address corresponding to the merchant ID;
step S53: determining an encryption machine address corresponding to the merchant ID according to the merchant ID carried by the service message;
Step S54: the analyzed transaction, the account address carried by the business message and the determined merchant address are sent to the determined encryptor address, so that the corresponding encryptor signs the transaction by utilizing a private key corresponding to the account address to obtain first signature data, and signs the transaction and the first signature data by utilizing the private key corresponding to the merchant address to obtain second signature data;
step S55: receiving first signature data and second signature data returned by an encryptor;
step S56: and sending the analyzed transaction, the first signature data and the second signature data to a gateway corresponding to the middleware system, so that the gateway performs signature verification on the second signature data by using a corresponding public key, and submitting the transaction and the first signature data to a node of the blockchain network under the condition that the signature verification passes.
The business message carries a merchant ID which is the merchant ID of the merchant initiating the business message, and the account address carried by the business message is the account address of the user who makes the business request. For ease of understanding, assume, by way of example, that user x of merchant SHPF-003 makes a request to merchant SHPF-003 that is: transfer to an account of merchant HXYH-001. The merchant SHPF-003 generates a service message, wherein the merchant ID carried by the service message is SHPF-003, and the account address carried by the service message is the account address of the user x.
For the specific implementation manner of step S51, reference may be made to fig. 3 and the corresponding description of fig. 3, and in order to avoid repetition, the description is omitted here.
In the invention, the business message carries the merchant ID, and the middleware system stores the corresponding relation between the merchant ID and the merchant address and also stores the corresponding relation between the merchant ID and the encryptor address. And the middleware system determines the merchant address and the encryptor address corresponding to the merchant ID according to the corresponding relation between the merchant ID carried by the service message and the stored merchant ID, and then sends the analyzed transaction, the account address carried by the service message and the determined merchant address to the determined encryptor address.
Referring to fig. 6, fig. 6 is a schematic diagram of signature according to an embodiment of the present invention. When the encryption machine signs, firstly, a private key corresponding to an account address is utilized to sign the transaction, and first signature data (namely, a user signature) is obtained. And then, signing the transaction and the whole first signature data by utilizing the private key of the merchant address to obtain second signature data. The private key corresponding to the user address refers to: a private key belonging to a key pair with the user address. The private key corresponding to the merchant address refers to: a private key belonging to a key pair with the merchant address.
In the invention, the merchant signature is checked by the gateway, and the transaction is submitted to the blockchain network for execution under the condition that the check passes, but the transaction is not submitted to the blockchain network for execution under the condition that the check fails. Thus, illegal transactions can be prevented from flowing into the blockchain network, thereby improving the security of the blockchain network and the business.
In addition, it should be noted that, in the present invention, the corresponding relationship between the merchant ID and the merchant address is disposed outside the encryptor (i.e. disposed in the middleware system), after the middleware system queries the merchant address corresponding to the merchant ID in advance, the transaction, the user address and the queried merchant address are sent to the encryptor, so that the encryptor signs. Therefore, the memory of the encryption machine can be saved because the encryption machine does not need to store the corresponding relation between the merchant ID and the merchant address.
Or alternatively, in some embodiments, referring to fig. 7, fig. 7 is a schematic diagram of a registered account proposed by another embodiment of the present invention. As shown in FIG. 7, the number of merchants and key management systems is multiple, and the multiple key management systems are distributed in different regions, each key management system being used to manage one or more encryption machines. In addition, each merchant corresponds to a key management system and also corresponds to an encryption machine managed by the key management system, and the key management system stores the corresponding relation between the merchant and the encryption machine.
In the invention, by disposing a plurality of key management systems in a plurality of areas, each key management system can be correspondingly configured according to local laws and regulations or business characteristics, such as corresponding statistics function, auditing function and the like. Each merchant can choose to dock a corresponding key management system according to the service requirement. Thus, the invention provides a technical platform for developing complex business for merchants.
When the middleware system receives the account registration request, the middleware system may perform the following substeps in order to invoke the key management system to generate a key pair:
substep 21-a: responding to an account registration request sent by merchant equipment, and determining a key management system corresponding to the merchant ID according to the merchant ID carried by the account registration request;
substep 21-B: and forwarding an account registration request to the determined key management system, so that the key management system determines an encryption machine corresponding to the merchant ID according to the merchant ID carried by the account registration request, and then sending an account registration command to the determined encryption machine, so that the corresponding encryption machine generates a key pair.
In specific implementation, the middleware system records the corresponding relation between the merchant ID and the key management system. After receiving the account registration request, the middleware system reads the merchant ID from the account registration request, then uses the read merchant ID as an index, queries a key management system corresponding to the merchant ID from the corresponding relation between the merchant ID and the key management system, and then forwards the account registration request to the determined key management system. After receiving the account registration request, the corresponding key management system reads the merchant ID from the account registration request, then uses the read merchant ID as an index, queries the encryption machine corresponding to the merchant ID from the corresponding relation between the merchant ID and the encryption machine, and finally forwards the account registration request to the determined encryption machine, so that the encryption machine generates a key pair.
Based on the same inventive concept, the embodiment of the invention also provides an electronic device, as shown in fig. 8, which comprises a processor 801, a communication interface 802, a memory 803 and a communication bus 804, wherein the processor 801, the communication interface 802 and the memory 803 complete communication with each other through the communication bus 804.
The memory 803 is used for storing a computer program;
the processor 801 is configured to implement the following steps when executing a program stored in the memory 803:
responding to an account registration request sent by merchant equipment, and calling the key management system to generate a key pair, wherein the key pair comprises a private key, a public key and an account address; receiving an account address returned by the key management system; and returning the account address to the merchant equipment.
In addition, the following steps are also realized:
receiving a service message sent by merchant equipment; analyzing the received service message into a transaction; invoking a key management system to sign the parsed transaction; submitting the signed transaction to the blockchain network for execution.
Alternatively, the processor 801 is configured to implement the registration method steps provided in the above other method embodiments of the present invention when executing the program stored in the memory 803.
The communication bus mentioned by the above electronic device may be a peripheral component interconnect standard (Peripheral Component Interconnect, abbreviated as PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated as EISA) bus, or the like. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface is used for communication between the electronic device and other devices.
The memory may include random access memory (Random Access Memory, RAM) or non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In yet another embodiment of the present invention, a computer readable storage medium is provided, in which instructions are stored which, when run on a computer, cause the computer to perform the registration method of any of the above embodiments.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.
Claims (9)
1. The registration method is characterized by being applied to a middleware system, wherein the middleware system is in communication connection with part of nodes of a blockchain network, and is used for receiving a service message sent by merchant equipment, analyzing the received service message into a transaction, calling a key management system to sign the analyzed transaction, and submitting the signed transaction to the blockchain network for execution; the method comprises the following steps:
responding to an account registration request sent by merchant equipment, and calling the key management system to generate a key pair, wherein the key pair comprises a private key, a public key and an account address;
receiving an account address returned by the key management system;
returning the account address to the merchant device, wherein the account address is stored at a merchant side;
the key management system is an encryptor, the number of merchants and the number of encryptors are multiple, and the merchants and the encryptors have corresponding relations; the account registration request carries a merchant ID; the method for calling the key management system to generate the key pair in response to the account registration request sent by the merchant equipment comprises the following steps:
Responding to an account registration request sent by merchant equipment, and determining an encryption machine address corresponding to a merchant ID according to the merchant ID carried by the account registration request;
and forwarding the account registration request to the determined address of the encryptor so that the corresponding encryptor generates a key pair.
2. The method of claim 1, wherein the number of merchants is a plurality, and the account registration request carries a merchant ID; after receiving the account address returned by the key management system, the method further comprises the following steps:
and establishing a corresponding relation between the merchant and the account aiming at the merchant ID carried by the account registration request and the account address returned by the key management system.
3. The method of claim 2, wherein other nodes of the blockchain network are communicatively connected to other middleware systems, and the other middleware systems are configured to receive service messages sent by corresponding merchant devices, parse the received service messages into one or more transactions, and submit the one or more transactions to the blockchain network for execution, wherein each transaction of the one or more transactions carries a message identifier of the service message, and a number of transactions of the one or more transactions also carries an account address recorded in the service message for participating in a service; the method further comprises the steps of:
Obtaining a transaction from the blockchain network;
recombining the service message according to one or more transactions carrying the same message identifier;
inquiring the corresponding relation between the merchant and the account according to the account address recorded in the recombined service message so as to determine the merchant corresponding to the account address;
and sending the recombined business message to the determined merchant equipment of the merchant.
4. The method of claim 1, wherein prior to registering the account, the method further comprises:
obtaining an encryptor address corresponding to a merchant to be registered;
and sending a merchant registration request to the obtained encryptor address, so that the corresponding encryptor generates a key pair, wherein the key pair comprises a private key, a public key and a merchant address.
5. The method according to claim 4, wherein the method further comprises:
receiving a merchant address and a public key returned by the encryptor;
establishing a corresponding relation between a merchant ID and the merchant address, wherein the merchant ID is the merchant ID of the merchant to be registered;
and submitting the public key to a gateway corresponding to the middleware system, wherein the middleware system is in communication connection with part of nodes of the blockchain network through the gateway.
6. The method of claim 5, wherein the method further comprises:
responding to a business message sent by a merchant device, and analyzing the business message into a transaction, wherein the business message carries a merchant ID and an account address;
inquiring the corresponding relation between the merchant ID and the merchant address according to the merchant ID carried by the service message, and determining the merchant address corresponding to the merchant ID;
determining an encryption machine address corresponding to the merchant ID according to the merchant ID carried by the service message;
the analyzed transaction, the account address carried by the business message and the determined merchant address are sent to the determined encryptor address, so that the corresponding encryptor signs the transaction by utilizing a private key corresponding to the account address to obtain first signature data, and signs the transaction and the first signature data by utilizing the private key corresponding to the merchant address to obtain second signature data;
receiving first signature data and second signature data returned by an encryptor;
and sending the analyzed transaction, the first signature data and the second signature data to a gateway corresponding to the middleware system, so that the gateway performs signature verification on the second signature data by using a corresponding public key, and submitting the transaction and the first signature data to a node of the blockchain network under the condition that the signature verification passes.
7. A method according to any one of claims 1 to 3, wherein the number of merchants and key management systems is plural, the plural key management systems being distributed in different regions, each key management system being for managing one or more encryption machines; each merchant corresponds to a key management system and also corresponds to an encryption machine managed by the key management system, and the key management system stores the corresponding relation between the merchant and the encryption machine; the account registration request carries a merchant ID; the method for calling the key management system to generate the key pair in response to the account registration request sent by the merchant equipment comprises the following steps:
responding to an account registration request sent by merchant equipment, and determining a key management system corresponding to the merchant ID according to the merchant ID carried by the account registration request;
and forwarding an account registration request to the determined key management system, so that the key management system determines an encryption machine corresponding to the merchant ID according to the merchant ID carried by the account registration request, and then sending an account registration command to the determined encryption machine, so that the corresponding encryption machine generates a key pair.
8. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
The memory is used for storing a computer program;
the processor is configured to implement the method steps of any of claims 1-7 when executing a program stored on a memory.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method steps of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110064962.3A CN114827175B (en) | 2021-01-18 | 2021-01-18 | Registration method, electronic device, and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110064962.3A CN114827175B (en) | 2021-01-18 | 2021-01-18 | Registration method, electronic device, and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114827175A CN114827175A (en) | 2022-07-29 |
| CN114827175B true CN114827175B (en) | 2023-08-22 |
Family
ID=82524124
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110064962.3A Active CN114827175B (en) | 2021-01-18 | 2021-01-18 | Registration method, electronic device, and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114827175B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103188309A (en) * | 2011-12-30 | 2013-07-03 | 上海可鲁系统软件有限公司 | Service acquiring method in distributed type system |
| KR101406530B1 (en) * | 2013-05-30 | 2014-06-11 | 제주대학교 산학협력단 | Method and system for managing secret key service using smart meter |
| CN107294721A (en) * | 2016-03-30 | 2017-10-24 | 阿里巴巴集团控股有限公司 | The method and apparatus of identity registration, certification based on biological characteristic |
| CN108418680A (en) * | 2017-09-05 | 2018-08-17 | 矩阵元技术（深圳）有限公司 | A blockchain key recovery method and medium based on multi-party secure computing technology |
| CN111339571A (en) * | 2020-02-28 | 2020-06-26 | 百度在线网络技术（北京）有限公司 | Block chain key management method, device, equipment and storage medium |
| CN111683083A (en) * | 2020-06-05 | 2020-09-18 | 成都质数斯达克科技有限公司 | Block chain user identity authentication method, device, equipment and medium |
| CN112000976A (en) * | 2020-10-29 | 2020-11-27 | 腾讯科技（深圳）有限公司 | Authentication management method, device, medium and electronic equipment for block chain system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10756883B2 (en) * | 2018-01-19 | 2020-08-25 | Trist Technologies, Inc. | Systems and methods for data collection with blockchain recording |
-
2021
- 2021-01-18 CN CN202110064962.3A patent/CN114827175B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103188309A (en) * | 2011-12-30 | 2013-07-03 | 上海可鲁系统软件有限公司 | Service acquiring method in distributed type system |
| KR101406530B1 (en) * | 2013-05-30 | 2014-06-11 | 제주대학교 산학협력단 | Method and system for managing secret key service using smart meter |
| CN107294721A (en) * | 2016-03-30 | 2017-10-24 | 阿里巴巴集团控股有限公司 | The method and apparatus of identity registration, certification based on biological characteristic |
| CN108418680A (en) * | 2017-09-05 | 2018-08-17 | 矩阵元技术（深圳）有限公司 | A blockchain key recovery method and medium based on multi-party secure computing technology |
| CN111339571A (en) * | 2020-02-28 | 2020-06-26 | 百度在线网络技术（北京）有限公司 | Block chain key management method, device, equipment and storage medium |
| CN111683083A (en) * | 2020-06-05 | 2020-09-18 | 成都质数斯达克科技有限公司 | Block chain user identity authentication method, device, equipment and medium |
| CN112000976A (en) * | 2020-10-29 | 2020-11-27 | 腾讯科技（深圳）有限公司 | Authentication management method, device, medium and electronic equipment for block chain system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114827175A (en) | 2022-07-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112132447B (en) | Block chain-based algorithm for evaluating and guaranteeing trust of computing power network | |
| US20230316273A1 (en) | Data processing method and apparatus, computer device, and storage medium | |
| WO2020258848A1 (en) | Method and apparatus for cross-chain transmission of resources | |
| CN113409047B (en) | Data processing method, device and equipment based on block chain and readable storage medium | |
| WO2018161903A1 (en) | Electronic bill management method, device, and storage medium | |
| EP3889870A1 (en) | Background architecture method and system for aggregation payment, computer device, and storage medium | |
| CN108881187A (en) | A kind of across chain data transferring method and equipment suitable for permitting chain scene | |
| CN108009811A (en) | A cross-chain communication method for inter-cloud computing environment value exchange | |
| CN107315786A (en) | Business datum storage method and device | |
| CN112202564B (en) | Transaction transfer method and device, electronic equipment and readable storage medium | |
| CN113556234A (en) | Block chain cross-chain communication method and system | |
| CN112087502A (en) | Method, device and equipment for processing request and storage medium | |
| CN113271311A (en) | Digital identity management method and system in cross-link network | |
| CN113781230B (en) | Transaction processing method and device based on blockchain | |
| CN113689216A (en) | Cross-chain transaction processing method and device, equipment, storage medium and program product | |
| CN112883117A (en) | Data synchronization method, equipment and computer readable storage medium | |
| WO2018210097A1 (en) | Method and device for execution transaction mode by classification | |
| CN113014556B (en) | Bank-enterprise communication system, communication method and electronic terminal | |
| CN114827175B (en) | Registration method, electronic device, and readable storage medium | |
| CN116708463B (en) | Information processing method, device, equipment and medium based on multi-block chain | |
| CN112150158B (en) | A blockchain transaction delivery verification method and device | |
| WO2024164550A1 (en) | Blockchain data processing method and apparatus, device, and storage medium | |
| CN110852744A (en) | Method, device, terminal equipment and medium for switching transaction channels | |
| CN113643032B (en) | Information processing method, device and data management system based on block chain | |
| CN113836573B (en) | User information processing method and device based on distributed storage |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |