WO2018228337A1 - 业务数据存储方法、计算机可读存储介质以及电子设备 - Google Patents

业务数据存储方法、计算机可读存储介质以及电子设备 Download PDF

Info

Publication number
WO2018228337A1
WO2018228337A1 PCT/CN2018/090681 CN2018090681W WO2018228337A1 WO 2018228337 A1 WO2018228337 A1 WO 2018228337A1 CN 2018090681 W CN2018090681 W CN 2018090681W WO 2018228337 A1 WO2018228337 A1 WO 2018228337A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
service
service data
blockchain
data type
Prior art date
Application number
PCT/CN2018/090681
Other languages
English (en)
French (fr)
Inventor
郭锐
李茂材
梁军
张建俊
王宗友
屠海涛
赵琦
刘斌华
朱大卫
秦青
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2018228337A1 publication Critical patent/WO2018228337A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/211—Schema design and management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2291—User-Defined Types; Storage management thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries

Definitions

  • the present disclosure relates to the field of network technologies, and in particular, to a service data storage method, a computer readable storage medium, and an electronic device.
  • the electronic device In the process of processing the service data of the terminal, in order to back up the service data involved in the current service process, when receiving the service data of the terminal, the electronic device stores the received service data.
  • an electronic device of an electronic device part service organization usually has a storage requirement of the service data; that is, each electronic device stores service data that meets its own storage requirements, For example, the electronic device A can store the service data A, but since the storage data of the service data B is not required, the service data B is not stored.
  • the stored service data of the above-mentioned electronic device is likely to be maliciously falsified, and if other electronic devices do not have the storage requirement of the service data, that is, the storage is not stored.
  • the service data may cause the electronic device to find that the service data of the electronic device is tampered with by other electronic devices, and the security of the service data is poor.
  • the embodiments of the present disclosure provide a service data storage method, a computer readable storage medium, and an electronic device, which solve the problem of poor security of service data existing in the related art.
  • the present disclosure stores service data by means of a blockchain by using an electronic device, can quickly find out after data on the blockchain is tampered with, and can automatically recover data from other electronic devices configuring the blockchain.
  • the return feature ensures the security of business data.
  • a method of storing a service data comprising:
  • the previous block is used to record the service data.
  • a service data storage device comprising:
  • a receiving module configured to receive service data
  • a determining module configured to determine, according to the data type of the service data, a target blockchain corresponding to the service data from multiple blockchains;
  • a storage module configured to generate a second block on the target blockchain based on the service data and a block header feature value of a first block in the target blockchain, where the first block is a The previous block of the second block is used to record the service data.
  • a computer readable storage medium having stored therein at least one instruction, at least one program, a code set, or a set of instructions, the at least one instruction, the at least one program, the code set Or the set of instructions is loaded and executed by the processor to implement the business data storage method as described above.
  • an electronic device including a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set, or a set of instructions, the at least one instruction, the at least one segment A program, the set of codes, or a set of instructions is loaded and executed by the processor to implement a business data storage method as described above.
  • the embodiment of the present disclosure configures a blockchain corresponding to each type of service data between multiple service organizations according to service requirements, and implements storing each type of service data into a blockchain corresponding to the service data, thereby enabling Multiple blockchains can store service data of different data types respectively, so that any service organization can share one type of service data with a cooperative service organization on a blockchain according to business requirements, and other cooperative service organizations.
  • Another type of service data is shared on another blockchain, and the data on different blockchains do not affect each other, so that data sharing and data isolation can be selectively performed; and, due to the block between the front and rear blocks Correlation, so that any business data in the block can be detected through the next block when it is tampered with, avoiding malicious users tampering or repudiating the processed business data, and ensuring the security of the business data.
  • the service data can be branched into the respective blockchains according to the data type, and then in parallel in each blockchain.
  • the storage of service data makes the performance of the electronic device no longer limited by the chain structure of the blockchain, thereby improving the operating efficiency of the electronic device.
  • FIG. 1 is a schematic diagram of a service data processing system according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a service data storage method according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a service request process according to an embodiment of the present disclosure
  • FIG. 4 is a block diagram of a service data storage apparatus according to an embodiment of the present disclosure.
  • FIG. 5A is a block diagram of a service data storage apparatus according to an embodiment of the present disclosure.
  • FIG. 5B is a block diagram of a service data storage apparatus according to an embodiment of the present disclosure.
  • FIG. 6 is a block diagram of an electronic device 600 according to an embodiment of the present disclosure.
  • FIG. 1 is a schematic structural diagram of a service data processing system according to an embodiment of the present disclosure.
  • the service data processing system may be composed of multiple subsystems, each of which may be configured with multiple blockchains according to the data type of the service data, and the same block may be configured between any two subsystems. Chains may also be configured with different blockchains. Multiple subsystems configured with the same blockchain may reach a consensus on the service data stored in the blockchain, and provide services for users based on the service data.
  • the service data processing system can be a payment service data processing system.
  • the payment service data processing system includes a subsystem 101, a subsystem 102, a subsystem 103, and a subsystem 104.
  • the subsystem 101 may include a node 1011, a node 1012, and a node 1013 deployed by a network service provider, where the three nodes are respectively configured with a blockchain A, a blockchain B, and a blockchain C; the subsystem 102 may include a bank X.
  • the deployed node 1021 and the node 1022 are respectively configured with a blockchain A and a blockchain B;
  • the subsystem 103 may include a node 101 and a node 1032 deployed by the bank Y, and the two nodes are respectively configured with a blockchain A and blockchain C;
  • the subsystem 104 may include a node 1041, a node 1042, and a node 1043 deployed by a supervisory authority, each of which is configured with a blockchain A, a blockchain B, and a blockchain C.
  • a subsystem may include multiple nodes corresponding to one blockchain.
  • the subsystem 101 further includes a node 1014, and the node 1014 is also configured with a blockchain C.
  • Any node in the system can be configured as a computer device. It will be understood that the nodes in the present disclosure are node devices configured as computer devices.
  • the plurality of blockchains may provide data services for the at least one first service organization, and the partial blockchains of the plurality of blockchains may be at least one first service organization and at least one second service organization.
  • Provide data services
  • the at least one first service organization may be a network service provider or a regulatory agency
  • the at least one second service organization may be a bank X and a bank Y.
  • blockchain A, blockchain B and blockchain C can provide data services for network service providers or regulatory agencies
  • blockchain A can provide data services for network service providers, banks X, banks Y and regulatory agencies. .
  • the plurality of blockchains may further provide data services for both the first service organization and the second service organization.
  • bank X can also configure blockchain C
  • bank Y can also configure blockchain B
  • the configuration of other service organizations is unchanged
  • blockchain A, blockchain B, and blockchain C are network service providers.
  • Bank X, Bank Y and regulatory agencies provide data services. That is to say, a part of the plurality of blockchains can be configured on a subsystem deployed by a service organization, and data storage and data query operations are performed based on the blockchains configured on the subsystem.
  • the data types of the service data stored in the blockchain A, the blockchain B, and the blockchain C are different.
  • the blockchain A is used to store the service data of the data types a1 and a2
  • the blockchain B is used to store the service data of the data type b
  • the blockchain C is used to store the service data of the data type c.
  • the data type of the service data is not specifically limited in the embodiment of the present disclosure.
  • a1 may be user relationship chain data
  • a2 may be user preference data
  • b may be a user bill at bank X
  • c may be a user at bank Y. Billing.
  • a plurality of blockchains configured between multiple subsystems may also include a shared blockchain.
  • the shared blockchain is used to store business data shared among multiple service organizations. For example, business data such as user relationship chain data or user preference data with universal sharing requirements can be stored in the shared blockchain.
  • each subsystem may further include at least one logical node, where the logical node is provided with a network connection between each node in the subsystem, and the logical node is configured to receive user service data, and The service data is forwarded to a corresponding node in the subsystem according to the data type of the service data.
  • the node in the subsystem that configures the blockchain is configured to store the received service data into the blockchain and respond based on the service data.
  • multiple nodes corresponding to each blockchain can operate independently, and nodes corresponding to any two blockchains do not affect each other.
  • the node 1011 is a node running in a leader state for indicating how the node corresponding to the blockchain A running in the following state works; the node 1022 is also a node running in the leader state, for A node corresponding to the blockchain B that runs in the following state is indicated.
  • the node running in the leadership state is switching, but does not affect the node work corresponding to other blockchains.
  • the node corresponding to blockchain B may be a node based on the leadership state. normal work.
  • the node 1011 receives the service data of the user as an example, and the node 1011 can redirect the service data to the node configured with the blockchain A and running in the leadership state (assumed to be the node 1021).
  • a service data storage request is broadcast by the node 1021 to each node configured with the blockchain A, the service data storage request for requesting storage of the service data into the blockchain A.
  • the node 1021 may store the service data into its own blockchain A, respond to the user based on the service data, and Each node broadcasts a service data storage instruction such that each node corresponding to the blockchain A also stores the service data in its own blockchain A.
  • the preset number of nodes is a part of all the nodes corresponding to the blockchain A, and the preset number refers to the number of nodes that have been configured and agreed upon.
  • the preset embodiment does not perform the preset number of values. It is not limited in detail.
  • the PBFT Practical Byzantine Fault Tolerance Algorithm
  • the number of all nodes corresponding to a blockchain is 3f+1, and the preset number can be greater than or equal to 2f+1 and less than or equal to The value of 3f+1, where f is any positive integer.
  • the above subsystem may also be a node, that is, multiple blockchains may be configured on the one node, and a function performed by a subsystem may be performed.
  • FIG. 2 is a flowchart of a service data storage method according to an embodiment of the present disclosure. The method may be applied to any one of any subsystems in the service data processing system shown in FIG.
  • the service data storage method includes the following steps:
  • the electronic device receives the service data.
  • the service data refers to data sent by a user served by the electronic device.
  • the service data may be in various forms, for example, the service data may be a request for a user to initiate a service.
  • the user confirms the request for the service, the terminal local data that needs to be uploaded to the electronic device, or the user input data.
  • the service data may be the transfer request initiated by the user A, the confirmation transfer request of the user B, or the payment order information uploaded by the user A.
  • the step 201 may also be specifically: the electronic device receives the service data packet; the electronic device acquires the service data from the service data packet and the signature of the terminal on the service data.
  • the service data packet refers to the complete data sent by the terminal, and the signature may be that the terminal signs the service data based on the user private key, so that the electronic device can verify the signature based on the user public key paired with the user private key.
  • the electronic device may use the user public key to parse the signature, obtain summary information, and calculate summary information of the service data according to an algorithm agreed with the terminal, and match the two summary information. If the matching is successful, determine the signature verification. Passing, proceeding to step 202; if the matching fails, determining that the signature verification fails, indicating that the service data is likely to come from a malicious user or has been tampered with by a malicious user, the electronic device may ignore the service data, or store the service data.
  • the blacklist business database is used to store business data processed by malicious users.
  • the device that receives the service data may also be the logical node shown in FIG. 1 , which is not specifically limited in this embodiment of the present disclosure.
  • the electronic device determines, according to the data type of the service data, a target blockchain corresponding to the service data from the plurality of blockchains.
  • the target blockchain refers to the blockchain used to store the service data.
  • different service organizations of different cooperation have different sharing requirements for business data of different data types, for example, four service organizations cooperate, and three of the service organizations need to share the data data of data type A, and the four service organizations need to share.
  • the service data of the data type B in order to better isolate the service data of different data types, the service data of different data types may be stored in different blockchains according to the data type of the service data.
  • the manner of determining the data type is not specifically limited in the embodiment of the present disclosure. Specifically, refer to the following examples 1 - example 3:
  • the electronic device determines, according to the first determining manner, the data type of the description object that conforms to the service data as the data type of the service data.
  • the service data is generally user identity data or service details.
  • the user identity data is used to describe the user, and the service details are used to describe the service. Therefore, the user identity data is one type of service data, and the service details are another type of service data.
  • the user relationship chain data and the user preference data may be configured as user identity data, and the billing data and the payment password are service details.
  • the electronic device can compare the protocol format of the service data with the protocol format of the two types of service data, and use the data type corresponding to the matched protocol format as the data type of the service data.
  • the protocol format can be the number of fields included in the business data, the length of each field, or a flag bit.
  • the electronic device determines, according to the second determining manner, the data type of the data privacy level that conforms to the service data as the data type of the service data.
  • the data privacy level is used to indicate the degree of privacy of the business data.
  • the business data may be a friend add request, a user bill or a payment password, and the privacy of the three business data is gradually increased, so that the electronic device can be configured.
  • the data privacy level of each business data, and the data type of the data privacy level conforming to the business data is used as the data type of the business data.
  • the data privacy level of the friend deletion request is 1, the data privacy level of the user bill is 2, the data privacy level of the payment password is 3, and the data privacy level of the friend addition request is 1, the friend deletion request and the friend addition request may be Data type A, the user bill can be data type B, and the payment password can be data type C.
  • the electronic device determines, according to the third determining manner, the data type of the service organization corresponding to the service data as the data type of the service data.
  • the electronic device may extract the service organization identifier carried in the service data, and query the data type corresponding to the service organization identifier. For example, the user initiates a refill request for refilling the game currency from the account balance of the bank X. Since the corresponding service institution is the bank X, the refill request may carry the service organization identifier of the bank X, so that the electronic The device may query the data type corresponding to the service organization identifier according to the correspondence between the service organization and the data type according to the service organization identifier.
  • the priority of each data type determination mode may also be set, and the priority of the mode is determined according to each data type, and the priority is the highest.
  • the electronic device may query the preset correspondence according to the data type of the service data, and determine whether there is a blockchain matching the data type of the service data in the preset correspondence, and if yes, the service data may be The blockchain of the data type matching is determined as the target blockchain.
  • the preset correspondence is used to indicate a correspondence between the data type and the blockchain, and the preset correspondence may be manually pre-configured on the electronic device.
  • the preset embodiment does not specifically limit the preset correspondence. For example, see the preset correspondence shown in Table 1:
  • Blockchain Data type a (user's bill on bank X) Blockchain A Data type b (user relationship chain data, user preference data) Blockchain B Data type c (user's bill at bank Y) Blockchain C
  • the electronic device may query, according to the determined data type, whether the data type of the same data type exists in the preset correspondence relationship, and if yes, obtain the blockchain identifier corresponding to the same data type. Determine the target blockchain.
  • the preset correspondence relationship configured by the electronic device may not cover all The data type, but the correspondence between several types of business data and blockchain with special sharing requirements, for example, a type of business data is shared among some subsystems in the business data processing system.
  • the data can be stored in the shared blockchain by default, that is, if there is no blockchain matching the data type of the service data, the electronic device can be in multiple blockchains.
  • the shared blockchain is determined to be the target blockchain.
  • the service data adds a request for a friend
  • the determined data type is user relationship chain data
  • the user relationship chain data can be shared among multiple service organizations deploying the service data processing system, so the shared blockchain can be determined.
  • the target blockchain For the target blockchain.
  • the service data may also be stored to the shared. Blockchain.
  • the device for determining the target blockchain may also be the logical node shown in FIG. 1, and the logical node forwards the service data to the node in the subsystem where the target blockchain is stored.
  • a blockchain may be identified by a node identifier. Therefore, the preset correspondence relationship configured by the logical node may be a correspondence between a data type and a node identifier.
  • the electronic device generates a second block on the target blockchain based on the service data and the block header feature value of the first block in the target blockchain, where the first block is the previous block of the second block,
  • the second block is used to record business data.
  • the electronic device may acquire all the information contained in the block header of the first block from the target blockchain, and obtain the block header feature value of the first block based on all the information included in the block header;
  • the device performs eigenvalue calculation on the service data to be stored in the block body of the second block to obtain the block body feature value of the second block, and further, the electronic device sets the block header feature value of the first block,
  • the block body feature value of the second block (which may further include a version number, a difficulty value, and a time stamp) is stored in the block header of the second block; after that, the electronic device stores the service data to the block body of the second block, Generating the second block, so that the second block is related to the first block by the block header feature value of the first block, thereby achieving the purpose of concatenating the blocks in the block chain, and ensuring the pair of blocks
  • the tampering of any information can be detected by tracing the block header feature value of the previous block stored in the block header, thereby
  • storing the service data to the target blockchain may be a node in the subsystem that configures the target blockchain.
  • the service data may be sent to the node.
  • a node running in a leader state (referred to as a leader node) corresponding to the target block chain, wherein the leader node broadcasts a service data storage request to each node corresponding to the target blockchain; if the leader node can receive a preset number of node pairs
  • the service data storage request confirmation message may store the service data into its own target blockchain, respond to the user based on the service data, and broadcast a service data storage instruction to the respective nodes to make the target blockchain
  • Each corresponding node (including the node) can store the business data into its own target blockchain.
  • the preset number of nodes are some of the nodes in the target blockchain.
  • Each node sends a confirmation message to the node to use the private key to sign the confirmation message, so that the leader node can carry the received signature in the service data storage instruction, thereby receiving the service data storage instruction.
  • the node can verify the service data storage instruction by signature; if the number of signatures matches the preset number, and each signature is verified by the public key of the corresponding node, the service data carried in the service data storage instruction can be stored to In its own target blockchain.
  • an embodiment of the present disclosure provides a service request processing flowchart, in which a logical node receives a service request of a terminal, and selects a region corresponding to the service request according to the configured preset correspondence.
  • a block chain and routing the service request to a local node configuring the blockchain, the local node forwarding the service request to a leader node configuring the blockchain until the leader node receives a preset number of nodes
  • the confirmation message of the service request at which the leader node can confirm that the blockchain reaches a consensus on the service request, and then the leader node can respond to the service request, send the response message to the local node, and then the local node sends a response message.
  • the logical node returns the response message to the terminal.
  • the embodiment of the present disclosure configures a blockchain corresponding to each type of service data between multiple service organizations according to service requirements, and implements storing each type of service data into a blockchain corresponding to the service data, thereby enabling Service data of different data types can be separately stored in multiple blockchains.
  • any service organization can share one type of service data with one cooperative service organization on one blockchain according to business needs, and another service service organization can share another type of service on another blockchain.
  • Data, and the data on different blockchains do not affect each other, so that data sharing and data isolation can be selectively performed.
  • any service data in the block can be detected through the next block when it is tampered with, thereby preventing the malicious user from tampering or refusing the processed service data.
  • the security of business data is guaranteed.
  • the service data can be branched into the respective blockchains according to the data type, and then in parallel in each block.
  • the service data is stored in the chain, so that the performance of the electronic device is no longer limited by the chain structure of the blockchain, which improves the operating efficiency of the electronic device.
  • the blockchain configured by the electronic device may be updated according to current service requirements, and the update may be multiple.
  • the embodiments of the present disclosure are exemplified by the following four cases:
  • the first update instruction carries the configured data type and the blockchain identifier to be configured.
  • the electronic device may extract the two pieces of data from the first update instruction, and query, in the preset correspondence relationship, whether there is the same data as any one of the two pieces of data; if present If the same data type as the configured data type is used, but the same blockchain identifier as the blockchain identifier to be configured is not present, the blockchain corresponding to the configured data type can be modified to the area to be configured. Blockchain.
  • the second update instruction carries the configured data type and the configured blockchain identifier.
  • the electronic device may extract the two pieces of data from the second update instruction, and query, in the preset correspondence relationship, whether there is the same data as any one of the two pieces of data; if present If the same data type as the configured data type and the same blockchain identifier as the to-be-configured blockchain identifier are present, the corresponding relationship between the configured data type and the original blockchain may be deleted, and the relationship is deleted.
  • the configured data type is added as the data type corresponding to the configured blockchain.
  • Case 3 When the electronic device receives the third update instruction, the corresponding relationship between the data type to be configured and the blockchain to be configured is updated based on the third update instruction.
  • the third update instruction carries the data type to be configured and the blockchain identifier to be configured.
  • the electronic device may extract the two data from the third update instruction, and query, in the preset correspondence, whether there is the same data as any one of the two data; if not There is a data type that is the same as the data type to be configured, and there is no blockchain identifier that is the same as the blockchain identifier to be configured. You can add a corresponding relationship between the data type to be configured and the blockchain to be configured.
  • Case 4 When receiving the fourth update instruction, update the correspondence between the data type to be configured and the configured blockchain based on the fourth update instruction.
  • the fourth update instruction carries the data type to be configured and the configured blockchain identifier.
  • the electronic device may extract the two data from the fourth update instruction, and query, in the preset correspondence, whether there is the same data as any one of the two data; There is a data type that is the same as the data type to be configured, but the same blockchain identifier as the blockchain identifier to be configured is added, and the data type to be configured can be added as the data corresponding to the configured blockchain. Types of.
  • the above update process takes the addition of a type of user credit data as an example. If the user credit data is shared with the configured user relationship chain data (the subsystems can be shared among all subsystems), the operator can trigger the fourth update.
  • the instructions cause the electronic device to update based on the received fourth update instruction.
  • the electronic device can store a new type of business data into the new blockchain according to current business requirements; or according to the existing cooperation relationship between the service organizations (configured)
  • the blockchain stores a new type of business data into the configured blockchain; it can also map the configured data type to the new blockchain according to changing sharing requirements; Correspondence between the data type and the configured blockchain enables flexible storage of service data between multiple service organizations according to business needs or sharing requirements.
  • the electronic device may stop the service on the blockchain corresponding to the update instruction when receiving the update instruction.
  • the contract refers to the code running on the blockchain to indicate how to process the business data. Since some contracts may be executed when an update instruction is received, in order to prevent the updated contract from being executed normally, it is possible to wait for the executed contract execution to complete before processing the service data of the blockchain or data type update.
  • FIG. 4 is a block diagram of a service data storage apparatus according to an embodiment of the present disclosure.
  • the device is applied to an electronic device, and specifically includes:
  • the receiving module 401 is configured to receive service data.
  • a determining module 402 configured to determine, according to a data type of the service data, a target blockchain corresponding to the service data from the plurality of blockchains;
  • the storage module 403 is configured to generate a second block on the target blockchain based on the service data and the block header feature value of the first block in the target blockchain, where the first block is the previous block of the second block Block, the second block is used to record business data.
  • the embodiment of the present disclosure can store each type of service data into a blockchain corresponding to the service data by configuring a blockchain corresponding to each type of service data between the plurality of service organizations according to the service requirement, thereby Multiple blockchains can store service data of different data types respectively, so that any service organization can share one type of service data with a cooperative service organization on a blockchain according to business requirements, and other cooperative service organizations.
  • Another type of service data is shared on another blockchain, and data on different blockchains does not affect each other, so that data sharing and data isolation can be selectively performed, and, due to the block between the front and rear blocks. Correlation, so that any service data in the block can be detected through the next block when it is tampered with, avoiding malicious users tampering or repudiating the processed service data, and ensuring the security of the service data.
  • the service data can be divided into the blockchains according to the data type, and then in parallel in each blockchain.
  • the storage of service data enables the performance of the electronic device to be no longer limited by the chain structure of the blockchain, thereby improving the operational efficiency of the electronic device.
  • the determining module 402 is configured to:
  • the preset correspondence is used to indicate a correspondence between the data type and the blockchain; if there is a blockchain matching the data type of the service data in the preset correspondence, The blockchain that matches the data type of the business data is determined as the target blockchain.
  • the determining module 402 is further configured to:
  • the shared blockchain in the plurality of blockchains is determined as the target blockchain, and the shared blockchain is used to store multiple services.
  • the device further includes:
  • the receiving module 401 is configured to receive a service data packet.
  • An obtaining module 404 configured to obtain service data from a service data packet and a signature of the terminal on the service data
  • the determining module 402 is configured to determine a target blockchain corresponding to the service data from the plurality of blockchains according to the data type of the service data if the signature verification of the service data is passed.
  • the device further includes:
  • the update module 405 is configured to: when receiving the first update instruction, update a correspondence between the configured data type and the blockchain to be configured based on the first update instruction; or
  • the update module 405 is configured to: when receiving the second update instruction, update the correspondence between the configured data type and the configured blockchain based on the second update instruction; or
  • the update module 405 is configured to: when receiving the third update instruction, update the correspondence between the data type to be configured and the blockchain to be configured based on the third update instruction; or
  • the updating module 405 is configured to, when receiving the fourth update instruction, update the correspondence between the data type to be configured and the configured blockchain based on the fourth update instruction.
  • the determining module 402 is further configured to determine, according to the first determining manner, a data type of the description object that conforms to the service data as a data type of the service data; and/or,
  • the determining module 402 is further configured to: determine, according to the second determining manner, a data type that meets a data privacy level of the service data as a data type of the service data; and/or,
  • the determining module 402 is further configured to determine, according to the third determining manner, a data type of the service organization corresponding to the service data as a data type of the service data; and/or,
  • the determining module 402 is further configured to: use the data type of the service data determined by the highest priority determining manner according to the priority of each determining manner.
  • the plurality of blockchains provide data services for at least one first service organization, and a part of the plurality of blockchains is the at least one first service organization and at least A second service organization provides a data service; or the plurality of blockchains provide data services for the at least one first service organization and the at least one second service organization.
  • the service data storage device provided by the foregoing embodiment stores the service data
  • only the division of the foregoing functional modules is illustrated.
  • the function distribution may be completed by different functional modules as needed.
  • the internal structure of the device is divided into different functional modules to perform all or part of the functions described above.
  • the service data storage device and the service data storage method embodiment provided by the foregoing embodiments are in the same concept, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • FIG. 6 is a block diagram of an electronic device 600 according to an embodiment of the present disclosure.
  • the electronic device 600 can be provided as a server.
  • electronic device 600 includes a processing component 622 that further includes one or more processors, and memory resources represented by memory 632 for storing instructions executable by processing component 622, such as an application.
  • An application stored in memory 632 can include one or more modules each corresponding to a set of instructions.
  • processing component 622 is configured to execute instructions to perform the business data storage method described above.
  • the electronic device 600 can also include a power supply component 626 configured to perform power management of the electronic device 600, a wired or wireless network interface 650 configured to connect the electronic device 600 to the network, and an input/output (I/O) interface 658 .
  • the electronic device 600 may operate based on an operating system stored in the memory 632, for example, Windows Server TM, Mac OS X TM , Unix TM, Linux TM, FreeBSD TM or the like.
  • a computer readable storage medium such as a memory comprising at least one instruction, at least one program, a code set, or a set of instructions, the at least one instruction, at least one program, code set, or instruction set
  • the business data storage method in the above embodiments may be loaded and executed by a processor in the electronic device.
  • the computer readable storage medium can be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
  • the storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Software Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种业务数据存储方法、计算机可读存储介质以及电子设备，属于网络技术领域。该方法包括：接收业务数据（201）；根据业务数据的数据类型，从多条区块链中确定与业务数据对应的目标区块链（202）；基于业务数据以及目标区块链中第一区块的区块头特征值，在目标区块链上生成第二区块（203），第一区块为第二区块的上一个区块，第二区块用于记录业务数据。该方法可以选择性地进行数据共享和数据隔离，而且，由于区块链中前后区块之间相关联，使得区块中任一业务数据被篡改时都能通过下一区块检测到，避免了恶意用户篡改或抵赖处理过的业务数据，也保证了业务数据的安全性。

Description

业务数据存储方法、计算机可读存储介质以及电子设备
本申请要求于2017年06月12日提交中国国家知识产权局、申请号为201710438943.6、发明名称为“业务数据存储方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及网络技术领域，特别涉及一种业务数据存储方法、计算机可读存储介质以及电子设备。
背景技术
随着网络技术的发展，网络带宽得到大幅优化，电子设备能够快捷地向终端提供业务支持，而为了给终端提供更为丰富的业务，多个服务机构的电子设备往往以联合的方式为终端服务，例如，银行、监管机构和网络服务商的电子设备共同为终端提供支付业务。
在处理终端的业务数据的过程中，为了备份本次业务处理过程涉及的业务数据，当接收到终端的业务数据时，电子设备便对接收到的业务数据进行存储。具体地，由于某些业务数据涉及一个服务机构的商业隐私，因此通常是电子设备部分服务机构的电子设备具备这些业务数据的存储需求；即，每个电子设备存储符合自身存储需求的业务数据，如，电子设备A可以存储业务数据A，但由于不具备业务数据B的存储需求，所以不会存储业务数据B。
在实现本公开的过程中，相关技术至少存在以下问题：
由于电子设备存在被恶意分子侵入的安全隐患，所以对于上述任一个电子设备来讲，其存储的业务数据很可能被恶意篡改，而如果其他电子设备不具备该业务数据的存储需求，即未存储该业务数据，则会导致电子设备很难通过其他电子设备发现该电子设备的业务数据被篡改，业务数据的安全性差。
发明内容
本公开实施例提供了一种业务数据存储方法、计算机可读存储介质以及电子设备，解决了相关技术存在的业务数据的安全性差的问题。详细地，本公开通过电子设备使用区块链的方式存储业务数据，利用区块链上的数据被篡改之后能快速发现，并可以自动从配置该区块链的其他电子设备上将数据正确恢复回来的特性，保证了业务数据的安全性。所述技术方案如下：
一方面，提供了一种业务数据存储方法，所述方法包括：
根据所述业务数据的数据类型，从多条区块链中确定与所述业务数据对应的目标区块链；
基于所述业务数据以及所述目标区块链中第一区块的区块头特征值，在所述目标区块链上生成第二区块，所述第一区块为所述第二区块的上一个区块，所述第二区块用于记录所述业务数据。
一方面，提供了一种业务数据存储装置，所述装置包括：
接收模块，用于接收业务数据；
确定模块，用于根据所述业务数据的数据类型，从多条区块链中确定与所述业务数据对应的目标区块链；
存储模块，用于基于所述业务数据以及所述目标区块链中第一区块的区块头特征值，在所述目标区块链上生成第二区块，所述第一区块为所述第二区块的上一个区块，所述第二区块用于记录所述业务数据。
一方面，提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如上述的业务数据存储方法。
一方面，提供了一种电子设备，所述电子设备包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如上述的业务数据存储方法。
本公开实施例按照业务需求在多个服务机构之间配置每一类业务数据对应的区块链，实现了将每一类业务数据存储到与该类业务数据对应的区块链中，进而使得多条区块链上可以分别存储有不同数据类型的业务数据，使得任一服务机构可以按照业务需求，与一些合作服务机构在一条区块链上共享一类业务数据，与另一些合作服务机构在另一条区块链上共享另一类业务数据，且 不同区块链上的数据互不影响，从而可以选择性地进行数据共享和数据隔离；而且，由于区块链中前后区块之间相关联，使得区块中任一业务数据被篡改时都能通过下一个区块检测到，避免了恶意用户篡改或抵赖处理过的业务数据，也保证了业务数据的安全性。
由于各个区块链生成区块的过程互不影响，即使短期内接收到大量用户的业务数据，也能按照数据类型将业务数据分流至各个区块链中，进而并行地在各个区块链中存储业务数据，使得电子设备的性能不再受限于区块链的链式结构，提高了电子设备的运行效率。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例提供的一种业务数据处理系统的示意图；
图2是本公开实施例提供的一种业务数据存储方法的流程图；
图3是本公开实施例提供的一种业务请求处理流程图；
图4是本公开实施例提供的一种业务数据存储装置的框图；
图5A是本公开实施例提供的一种业务数据存储装置的框图；
图5B是本公开实施例提供的一种业务数据存储装置的框图；
图6是本公开实施例提供的一种电子设备600的框图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
图1是本公开实施例提供的一种业务数据处理系统的结构示意图。如图1所示，该业务数据处理系统可以由多个子系统构成，每个子系统可以按照业务数据的数据类型配置有多条区块链，任意两个子系统之间可能配置了相同的一条区块链，也可能配置了不同的区块链，配置有同一条区块链的多个子系统之间可以针对该区块链所存储的业务数据达成共识，并基于该业务数据为用户提 供服务。
在一个可选的实施方式中，该业务数据处理系统可以为支付业务数据处理系统，如图1所示，该支付业务数据处理系统包括子系统101、子系统102、子系统103和子系统104。其中，子系统101可以包括网络服务商部署的节点1011、节点1012和节点1013，这三个节点分别配置有区块链A、区块链B和区块链C；子系统102可以包括银行X部署的节点1021和节点1022，这两个节点分别配置有区块链A和区块链B；子系统103可以包括银行Y部署的节点1031和节点1032，这两个节点分别配置有区块链A和区块链C；该子系统104可以包括监管机构部署的节点1041、节点1042和节点1043，这三个节点分别配置有区块链A、区块链B和区块链C。
需要说明的是，一个子系统中可以包括一条区块链对应的多个节点，例如，子系统101还包括节点1014，该节点1014也配置有区块链C。系统中的任意一个节点均可以配置为计算机设备。可以理解的是本公开中的节点即为配置为计算机设备的节点设备。
在本公开实施例中，多条区块链可以为至少一个第一服务机构提供数据服务，多条区块链中的部分区块链可以为至少一个第一服务机构和至少一个第二服务机构提供数据服务。例如，该至少一个第一服务机构可以为网络服务商或监管机构，该至少一个第二服务机构可以为银行X和银行Y。其中，区块链A、区块链B和区块链C均可以为网络服务商或监管机构提供数据服务；区块链A可以为网络服务商、银行X、银行Y和监管机构提供数据服务。
在一个可选的实施方式中，该多条区块链还可以为第一服务机构和第二服务机构均提供数据服务。例如，银行X也可以配置区块链C，银行Y也可以配置区块链B，其他服务机构的配置不变，则区块链A、区块链B和区块链C均为网络服务商、银行X、银行Y和监管机构提供数据服务。也就是说，一个服务机构部署的子系统上可以配置多条区块链中的部分或者全部，进而基于子系统上所配置的区块链进行数据存储、数据查询等操作。
其中，区块链A、区块链B和区块链C所存储的业务数据的数据类型各不相同。如，区块链A用于存储数据类型为a1和a2的业务数据，区块链B用于存储数据类型为b的业务数据，区块链C用于存储数据类型为c的业务数据。本公开实施例对业务数据的数据类型不做具体限定，例如，a1可以为用户关系链数据，a2可以为用户偏好数据，b可以为在银行X的用户账单，c可以为在 银行Y的用户账单。
在一个可选的实施方式中，为了便于多个服务机构之间不受数据类型的限制来共享数据，多个子系统之间配置的多条区块链中也可以包括一条共享区块链，该共享区块链用于存储多个服务机构之间共享的业务数据，例如，对于具有普遍共享需求的用户关系链数据或用户偏好数据等业务数据，均可以存储到该共享区块链中。
在一个可选的实施方式中，每个子系统还可以包括至少一个逻辑节点，该逻辑节点与其所在子系统中的各个节点之间设置有网络连接，该逻辑节点用于接收用户的业务数据，并按照该业务数据的数据类型，将该业务数据转发给该子系统中对应的节点。该子系统中配置区块链的节点用于将接收到的业务数据存储至区块链中，并基于该业务数据进行响应。
在本公开实施例中，每条区块链对应的多个节点可以独立运行，任意两条区块链对应的节点互不影响。如，在当前时刻，节点1011为运行于领导(leader)状态的节点，用于指示区块链A对应的运行于跟随状态的节点如何工作；节点1022也为运行于领导状态的节点，用于指示区块链B对应的运行于跟随状态的节点。在区块链A的选举过程中，运行于领导状态的节点正在发生切换，但并不影响其他区块链对应的节点工作，如，此时区块链B对应的节点可能正在基于领导状态的节点正常工作。
在业务数据处理过程中，以节点1011接收到用户的业务数据为例，节点1011可以将该业务数据重定向至配置有区块链A、且运行于领导状态的节点(假设为节点1021)，由节点1021向配置有区块链A的各个节点广播业务数据存储请求，该业务数据存储请求用于请求将该业务数据存储至区块链A中。如果节点1021接收到预设数量的节点对该业务数据存储请求的确认消息，则节点1021可以将该业务数据存储至自身的区块链A中，基于该业务数据对用户进行响应，并向该各个节点广播业务数据存储指令，使得区块链A对应的各个节点将该业务数据也存储至自身的区块链A中。其中，预设数量的节点为区块链A对应的所有节点中的部分节点，预设数量是指已配置且达成共识所要求的节点数量，本公开实施例对该预设数量的值不进行具体不限定。例如，以区块链基于PBFT(Practical Byzantine Fault Tolerance algorithm，拜占庭容错共识算法)为例，一条区块链对应的全部节点数量为3f+1，则预设数量可以为大于等于2f+1小于等于3f+1的数值，f为任意正整数。
需要说明的是，上述子系统也可以为一个节点，也即是，可以在该一个节点上配置多条区块链，并执行一个子系统所执行的功能。
图2是本公开实施例提供的一种业务数据存储方法的流程图，该方法可以应用于图1所示的业务数据处理系统中的任一子系统中的任一节点，以该节点为电子设备为例，参见图2，业务数据存储方法包括以下步骤：
201、电子设备接收业务数据。
该业务数据是指由该电子设备所服务的用户发送的数据，在一个可选的实施方式中，该业务数据可以有多种形式，如，该业务数据可以为用户对某一业务的发起请求、用户对该业务的确认请求、需要上传至电子设备的终端本地数据或用户输入数据等。以支付业务的应用场景为例，用户A向用户B转账时，该业务数据可以是用户A发起的转账请求、用户B的确认转账请求，也可以是用户A上传的支付订单信息。
为了进一步提高业务数据处理过程的安全性，避免接收到恶意用户伪装成正常用户发来的业务数据，还可以验证发送业务数据的用户身份。因此，该步骤201也可以具体为：电子设备接收业务数据包；电子设备从业务数据包中获取业务数据和终端对业务数据的签名。其中，该业务数据包是指终端发送的完整数据，该签名可以是终端基于用户私钥对业务数据的签名，使得电子设备能够基于与该用户私钥配对的用户公钥对该签名进行验证。
具体地，电子设备可以采用该用户公钥解析签名，得到摘要信息，并按照与终端约定的算法计算出业务数据的摘要信息，将两个摘要信息进行匹配，如果匹配成功，则确定该签名验证通过，进行步骤202；如果匹配失败，则确定该签名验证失败，说明该业务数据很可能来自于恶意用户或经过了恶意用户的篡改，则电子设备可以忽略该业务数据，或者将该业务数据存储至黑名单业务数据库，该黑名单业务数据库用于存储恶意用户处理过的业务数据。
需要说明的是，接收业务数据的设备也可以是图1所示的逻辑节点，本公开实施例对此不进行具体限定。
202、电子设备根据业务数据的数据类型，从多条区块链中确定与业务数据对应的目标区块链。
该步骤中，目标区块链是指本次用于存储该业务数据的区块链。考虑到合作的多家服务机构之间对不同数据类型的业务数据的共享需求不同，如，四家 服务机构合作，其中三家服务机构需要共享数据类型A的业务数据，该四家服务机构需要共享数据类型B的业务数据，为了更好地隔离不同数据类型的业务数据，可以按照业务数据的数据类型，将不同数据类型的业务数据存储到不同的区块链上。另外，本公开实施例对数据类型的确定方式不做具体限定，具体地，可以参见以下举例1-举例3：
举例1、电子设备根据第一确定方式，将符合业务数据的描述对象的数据类型确定为业务数据的数据类型。
例如，业务数据一般为用户身份数据或业务详情，该用户身份数据用于描述用户，业务详情用于描述业务，因此用户身份数据为一类业务数据，业务详情为另一类业务数据。例如，电子设备上可以配置用户关系链数据和用户偏好数据为用户身份数据，账单数据和支付密码为业务详情。具体地，电子设备可以将业务数据的协议格式与这两类业务数据的协议格式进行比较，将符合的协议格式对应的数据类型作为该业务数据的数据类型。该协议格式可为业务数据所包括的字段数量、每个字段的长度或标志位。
举例2、电子设备根据第二确定方式，将符合业务数据的数据私密等级的数据类型确定为业务数据的数据类型。
数据私密等级用于指示业务数据的私密程度。如，对于金融业务和理财业务等涉及用户财产的业务处理过程，业务数据可能是好友添加请求、用户账单或支付密码，而这三项业务数据的私密程度逐渐递增，因此，电子设备上可以配置每项业务数据的数据私密等级，并将符合该业务数据的数据私密等级的数据类型作为该业务数据的数据类型。如，好友删除请求的数据私密等级为1，用户账单的数据私密等级为2，支付密码的数据私密等级为3，好友添加请求的数据私密等级为1，则好友删除请求和好友添加请求可以为数据类型A，用户账单可以为数据类型B，支付密码可以为数据类型C。
举例3、电子设备根据第三确定方式，将符合业务数据对应的服务机构的数据类型确定为业务数据的数据类型。
具体地，电子设备可以提取出业务数据中携带的服务机构标识，并查询该服务机构标识对应的数据类型。例如，用户发起充值请求，该充值请求用于从银行X的账户余额中充值游戏币，由于该充值请求对应的服务机构为银行X，则该充值请求可以携带银行X的服务机构标识，使得电子设备可以根据该服务机构标识在服务机构与数据类型的对应关系中，查询该服务机构标识对应的数 据类型。
需要说明的是，由于电子设备接收到的业务数据包中往往包括多项业务数据，因此也可以设置各个数据类型确定方式的优先级，根据各个数据类型确定方式的优先级，将优先级最高的确定方式所确定数据类型作为业务数据的数据类型。如，电子设备可以按照该优先级的顺序，从优先级较高的确定方式开始确定数据类型，如果该确定方式有确定结果，则采用该确定方式所确定的数据类型，如果该确定方式没有确定结果，则继续采用优先级次之的确定方式进行确定。
在该步骤中，电子设备可以根据业务数据的数据类型查询预设对应关系，判断预设对应关系中是否存在与该业务数据的数据类型匹配的区块链，如果存在，则可以将与业务数据的数据类型匹配的区块链确定为目标区块链。其中，该预设对应关系用于指示数据类型与区块链的对应关系，该预设对应关系可以人工地预先配置在电子设备上。本公开实施例对预设对应关系不做具体限定。例如，参见表1所示的预设对应关系：
表1
数据类型 区块链
数据类型a(用户在银行X的账单) 区块链A
数据类型b(用户关系链数据、用户偏好数据) 区块链B
数据类型c(用户在银行Y的账单) 区块链C
上述确定过程中，电子设备可以根据已确定的数据类型，在预设对应关系中查询是否存在与该数据类型相同的数据类型，如果存在，则获取该相同的数据类型对应的区块链标识，确定出目标区块链。
在一个可选的实施方式中，为了减少电子设备侧的参数配置，提高电子设备查询预设对应关系的效率并减少对存储空间的占用，电子设备所配置的预设对应关系也可以不涵盖全部的数据类型，而是配置具有特殊共享需求的几类业务数据与区块链的对应关系，如，一类业务数据在业务数据处理系统中的部分子系统之间共享。而对于其他具有普遍共享需求的业务数据，均可以默认存储至共享区块链，也即是，如果不存在与业务数据的数据类型匹配的区块链，电子设备可以将多条区块链中的共享区块链确定为目标区块链。例如，该业务数据为好友添加请求，确定的数据类型为用户关系链数据，而部署业务数据处理系统的多个服务机构之间均可以共享该用户关系链数据，因此可以将共享区块 链确定为目标区块链。
在一个可选的实施方式中，为了备份已接收到的业务数据，避免用户抵赖或篡改业务处理流程，在电子设备确定业务数据的数据类型失败的情况下，也可以将该业务数据存储至共享区块链。
需要说明的是，确定目标区块链的设备也可以是图1所示的逻辑节点，进而由该逻辑节点将该业务数据转发至其所在子系统中存储该目标区块链的节点。对于逻辑节点来说，可以由节点标识来标识一个区块链，因此逻辑节点所配置的预设对应关系的形式可以为数据类型和节点标识的对应关系。
203、电子设备基于业务数据以及目标区块链中第一区块的区块头特征值，在目标区块链上生成第二区块，第一区块为第二区块的上一个区块，第二区块用于记录业务数据。
在该步骤中，电子设备可以从目标区块链中获取第一区块的区块头包含的所有信息，并基于该区块头包含的所有信息得到第一区块的区块头特征值；之后，电子设备对将要存入第二区块的区块主体中的业务数据进行特征值计算，得到第二区块的区块主体特征值，进而，电子设备将第一区块的区块头特征值、第二区块的区块主体特征值(还可以包括版本号、难度值和时间戳)存储至第二区块的区块头；之后，电子设备将业务数据存储至第二区块的区块主体，生成该第二区块，使得第二区块与第一区块通过第一区块的区块头特征值相关，进而实现了将区块链中的区块串联起来的目的，确保了对区块中任何信息(包括业务数据)的篡改，均能够通过追溯区块头中存储的上一个区块的区块头特征值而检测到，从而保证了业务数据的安全。
需要说明的是，将业务数据存储至目标区块链的可以是子系统中配置该目标区块链的节点，当该节点接收到逻辑节点转发的业务数据时，可以将该业务数据发送至该目标区块链对应的运行于领导状态的节点(简称领导节点)，由该领导节点广播业务数据存储请求至该目标区块链对应的各个节点；如果领导节点能够接收到预设数量的节点对该业务数据存储请求的确认消息，则可以将该业务数据存储至自身的目标区块链中，基于该业务数据对用户进行响应，并向该各个节点广播业务数据存储指令，使得目标区块链对应的各个节点(包括该节点)可以将该业务数据存储至自身的目标区块链中。其中，预设数量的节点为配置该目标区块链的各个节点中的部分节点。
其中，每个节点在发送确认消息时，也发送该节点采用私钥对该确认消息 的签名，使得领导节点能够将接收到的签名携带在业务数据存储指令中，进而使得接收到业务数据存储指令的节点，可以通过签名对业务数据存储指令进行验证；如果签名的数量符合预设数量，且每个签名均通过对应节点的公钥验证，则可以将业务数据存储指令中携带的业务数据存储至自身的目标区块链中。
参见图3，本公开实施例提供了一种业务请求处理流程图，该处理流程中，由逻辑节点接收终端的业务请求，并按照已配置的预设对应关系，选择与该业务请求对应的区块链，并将该业务请求路由至配置该区块链的本地节点，由该本地节点将该业务请求转发至配置该区块链的领导节点，直到领导节点接收到预设数量的节点对该业务请求的确认消息，此时领导节点可以确认该区块链对该业务请求达成共识，接下来领导节点可以对该业务请求进行响应，将响应消息发送至本地节点，之后本地节点将响应消息发送至逻辑节点，进而由逻辑节点将响应消息返回给终端。
本公开实施例按照业务需求在多个服务机构之间配置每一类业务数据对应的区块链，实现了将每一类业务数据存储到与该类业务数据对应的区块链中，进而使得多条区块链上可以分别存储有不同数据类型的业务数据。在该种情形下，任一服务机构可以按照业务需求，与一些合作服务机构在一条区块链上共享一类业务数据，与另一些合作服务机构在另一条区块链上共享另一类业务数据，且不同区块链上的数据互不影响，从而可以选择性地进行数据共享和数据隔离。
而且，由于区块链中前后区块之间相关联，使得区块中任一业务数据被篡改时都能通过下一区块检测到，避免了恶意用户篡改或抵赖处理过的业务数据，也保证了业务数据的安全性。
而且，由于相同区块链的每个节点存储的数据一致，即使某一节点的数据丢失或被篡改都能够根据该区块链对应的其他节点已存储的数据进行恢复，进而也提高了数据的安全性和可恢复性。
而且，由于各个区块链生成区块的过程互不影响，即使短期内接收到大量用户的业务数据，也能按照数据类型将业务数据分流至各个区块链中，进而并行地在各个区块链中存储业务数据，使得电子设备的性能不再受限于区块链的链式结构，提高了电子设备的运行效率。
在一个可选的实施方式中，根据当前的业务需求，电子设备所配置的区块链也可能更新，更新的情况可能有多种，本公开实施例以下述四种情况举例说 明：
情况1、当电子设备接收到第一更新指令时，基于第一更新指令更新已配置的数据类型与待配置的区块链的对应关系。
其中，第一更新指令携带已配置的数据类型和待配置的区块链标识。
当接收到第一更新指令后，电子设备可以从第一更新指令中提取出这两项数据，并在预设对应关系中查询是否存在与这两项数据中任一项相同的数据；如果存在与已配置的数据类型相同的数据类型，但不存在与该待配置的区块链标识相同的区块链标识，则可以将该已配置的数据类型对应的区块链修改为待配置的区块链。
情况2、当电子设备接收到第二更新指令时，基于第二更新指令更新已配置的数据类型与已配置的区块链的对应关系。
其中，第二更新指令携带已配置的数据类型和已配置的区块链标识。
当接收到第二更新指令后，电子设备可以从第二更新指令中提取出这两项数据，并在预设对应关系中查询是否存在与这两项数据中任一项相同的数据；如果存在与已配置的数据类型相同的数据类型，且存在与该待配置的区块链标识相同的区块链标识，则可以删除该已配置的数据类型与原区块链的对应关系，并将该已配置的数据类型添加为该已配置的区块链对应的数据类型。
情况3、当电子设备接收到第三更新指令时，基于第三更新指令更新待配置的数据类型与待配置的区块链的对应关系。
其中，第三更新指令携带待配置的数据类型和待配置的区块链标识。
当接收到第三更新指令后，电子设备可以从第三更新指令中提取出这两项数据，并在预设对应关系中查询是否存在与这两项数据中任一项相同的数据；如果不存在与待配置的数据类型相同的数据类型，也不存在与该待配置的区块链标识相同的区块链标识，可以添加一条待配置的数据类型与待配置的区块链的对应关系。
情况4、当接收到第四更新指令时，基于第四更新指令更新待配置的数据类型与已配置的区块链的对应关系。
其中，第四更新指令携带待配置的数据类型和已配置的区块链标识。
当接收到第四更新指令后，电子设备可以从第四更新指令中提取出这两项数据，并在预设对应关系中查询是否存在与这两项数据中任一项相同的数据；如果不存在与待配置的数据类型相同的数据类型，但存在与已待配置的区块链 标识相同的区块链标识，可以将该待配置的数据类型添加为该已配置的区块链对应的数据类型。
需要说明的是，在更新该电子设备上的数据类型和区块链的对应关系时，为了保证整个业务数据处理系统能够正常工作，涉及更新数据类型或区块链的其他电子设备也会进行同步更新。
上述更新过程以添加一类用户征信数据为例，假设用户征信数据与已配置的用户关系链数据的共享需求相同(各个子系统之间都可以共享)，则运营人员可以触发第四更新指令，使得电子设备可以基于接收到的第四更新指令进行更新。
通过对数据类型和区块链进行更新，电子设备可以按照当前的业务需求将新一类的业务数据存储到新的区块链中；也可以按照服务机构之间已有的合作关系(已配置的区块链)，将新一类的业务数据存储到已配置的区块链中；也可以根据变化的共享需求，将已配置的数据类型与新的区块链对应；还可以变更已配置的数据类型与已配置的区块链的对应关系，使得多个服务机构之间可以按照业务需求或共享需求灵活地存储业务数据。
在上述更新过程中，为了避免正在变化的数据类型与区块链的对应关系影响正常的业务数据处理过程，电子设备可以在接收到更新指令时，停止该更新指令对应的区块链上的业务数据存储过程；直到完成已执行的合约且接收到更新完成消息时，再按照更新后的预设对应关系存储业务数据。其中，合约是指运行在区块链上的代码，用于指示如何处理业务数据。由于接收到更新指令时可能正在执行某些合约，因此为了避免更新后合约无法正常执行，可以等待已执行的合约执行完成，再开始处理区块链或数据类型更新后的业务数据。
图4是本公开实施例提供的一种业务数据存储装置的框图。参见图4，该装置应用于电子设备中，具体包括：
接收模块401，用于接收业务数据；
确定模块402，用于根据业务数据的数据类型，从多条区块链中确定与业务数据对应的目标区块链；
存储模块403，用于基于业务数据以及目标区块链中第一区块的区块头特征值，在目标区块链上生成第二区块，第一区块为第二区块的上一个区块，第二区块用于记录业务数据。
本公开实施例通过按照业务需求在多个服务机构之间配置每一类业务数据对应的区块链，可以将每一类业务数据存储到与该类业务数据对应的区块链中，进而使得多条区块链上可以分别存储有不同数据类型的业务数据，使得任一服务机构可以按照业务需求，与一些合作服务机构在一条区块链上共享一类业务数据，与另一些合作服务机构在另一条区块链上共享另一类业务数据，且不同区块链上的数据互不影响，从而可以选择性地进行数据共享和数据隔离，而且，由于区块链中前后区块之间相关联，使得区块中任一业务数据被篡改时都能通过下一区块检测到，避免了恶意用户篡改或抵赖处理过的业务数据，也保证了业务数据的安全性。
由于各个区块链在生成区块的过程互不影响，即使短期内接收到大量用户的业务数据，也能按照数据类型将业务数据分流至各个区块链中，进而并行地在各个区块链中存储业务数据，使得电子设备的性能不再受限于区块链的链式结构，提高了电子设备的运行效率。
在一种可能实现方式中，确定模块402用于：
根据业务数据的数据类型查询预设对应关系，预设对应关系用于指示数据类型与区块链的对应关系；如果预设对应关系中存在与业务数据的数据类型匹配的区块链，则将与业务数据的数据类型匹配的区块链确定为目标区块链。
在一种可能实现方式中，确定模块402还用于：
如果预设对应关系中不存在与业务数据的数据类型匹配的区块链，则将多条区块链中的共享区块链确定为目标区块链，共享区块链用于存储多个服务机构之间共享的业务数据。
在一种可能实现方式中，基于图4的装置组成，参见图5A，该装置还包括：
接收模块401，用于接收业务数据包；
获取模块404，用于从业务数据包中获取业务数据和终端对业务数据的签名；
确定模块402，用于如果对业务数据的签名验证通过，则根据业务数据的数据类型，从多条区块链中确定与业务数据对应的目标区块链。
在一种可能实现方式中，基于图4的装置组成，参见图5B，该装置还包括：
更新模块405，用于当接收到第一更新指令时，基于第一更新指令更新已配置的数据类型与待配置的区块链的对应关系；或，
更新模块405，用于当接收到第二更新指令时，基于第二更新指令更新已 配置的数据类型与已配置的区块链的对应关系；或，
更新模块405，用于当接收到第三更新指令时，基于第三更新指令更新待配置的数据类型与待配置的区块链的对应关系；或，
更新模块405，用于当接收到第四更新指令时，基于第四更新指令更新待配置的数据类型与已配置的区块链的对应关系。
在一种可能实现方式中，确定模块402还用于：根据第一确定方式，将符合业务数据的描述对象的数据类型确定为业务数据的数据类型；和/或，
确定模块402还用于：根据第二确定方式，将符合业务数据的数据私密等级的数据类型确定为业务数据的数据类型；和/或，
确定模块402还用于：根据第三确定方式，将符合业务数据对应的服务机构的数据类型确定为业务数据的数据类型；和/或，
确定模块402还用于：根据各个确定方式的优先级，采用优先级最高的确定方式所确定的业务数据的数据类型。
在一种可能实现方式中，所述多条区块链为至少一个第一服务机构提供数据服务，所述多条区块链中的部分区块链为所述至少一个第一服务机构和至少一个第二服务机构提供数据服务；或，所述多条区块链为所述至少一个第一服务机构和所述至少一个第二服务机构均提供数据服务。
上述所有可选技术方案，可以采用任意结合形成本公开的可选实施例，在此不再一一赘述。
需要说明的是：上述实施例提供的业务数据存储装置在存储业务数据时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的业务数据存储装置与业务数据存储方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图6是本公开实施例提供的一种电子设备600的框图。例如，电子设备600可以被提供为一服务器。参照图6，电子设备600包括处理组件622，其进一步包括一个或多个处理器，以及由存储器632所代表的存储器资源，用于存储可由处理部件622的执行的指令，例如应用程序。存储器632中存储的应用程 序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件622被配置为执行指令，以执行上述业务数据存储方法。
电子设备600还可以包括一个电源组件626被配置为执行电子设备600的电源管理，一个有线或无线网络接口650被配置为将电子设备600连接到网络，和一个输入输出(I/O)接口658。电子设备600可以操作基于存储在存储器632的操作系统，例如Windows Server TM，Mac OS X TM，Unix TM,Linux TM，FreeBSD TM或类似。
在示例性实施例中，还提供了一种计算机可读存储介质，例如包括至少一条指令、至少一段程序、代码集或指令集的存储器，上述至少一条指令、至少一段程序、代码集或指令集可由电子设备中的处理器加载并执行以完成上述实施例中的业务数据存储方法。例如，计算机可读存储介质可以是ROM、RAM、CD-ROM、磁带、软盘和光数据存储设备等。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上仅为本公开的较佳实施例，并不用以限制本公开，凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (15)

  1. 一种业务数据存储方法，应用于电子设备，其中，所述方法包括：
    接收业务数据；
    根据所述业务数据的数据类型，从多条区块链中确定与所述业务数据对应的目标区块链；
    基于所述业务数据以及所述目标区块链中第一区块的区块头特征值，在所述目标区块链上生成第二区块，所述第一区块为所述第二区块的上一个区块，所述第二区块用于记录所述业务数据。
  2. 根据权利要求1所述的方法，其中，所述根据所述业务数据的数据类型，从多条区块链中确定与所述业务数据对应的目标区块链，包括：
    根据所述业务数据的数据类型查询预设对应关系，所述预设对应关系用于指示数据类型与区块链的对应关系；
    如果所述预设对应关系中存在与所述数据类型匹配的区块链，则将与所述数据类型匹配的区块链确定为所述目标区块链。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    如果所述预设对应关系中不存在与所述数据类型匹配的区块链，则将所述多条区块链中的共享区块链确定为所述目标区块链，所述共享区块链用于存储多个服务机构之间共享的业务数据。
  4. 根据权利要求1所述的方法，其中，所述接收业务数据，包括：
    接收业务数据包；
    从所述业务数据包中获取业务数据和终端对所述业务数据的签名；
    所述根据所述业务数据的数据类型，从多条区块链中确定与所述业务数据对应的目标区块链，包括：
    如果对所述业务数据的签名验证通过，则根据所述业务数据的数据类型，从所述多条区块链中确定与所述业务数据对应的目标区块链。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：
    当接收到第一更新指令时，基于所述第一更新指令更新已配置的数据类型与待配置的区块链的对应关系；或，
    当接收到第二更新指令时，基于所述第二更新指令更新已配置的数据类型与已配置的区块链的对应关系；或，
    当接收到第三更新指令时，基于所述第三更新指令更新待配置的数据类型与待配置的区块链的对应关系；或，
    当接收到第四更新指令时，基于所述第四更新指令更新待配置的数据类型与已配置的区块链的对应关系。
  6. 根据权利要求1所述的方法，其中，所述方法还包括：
    根据第一确定方式，将符合所述业务数据的描述对象的数据类型确定为所述业务数据的数据类型；和/或，
    根据第二确定方式，将符合所述业务数据的数据私密等级的数据类型确定为所述业务数据的数据类型；和/或，
    根据第三确定方式，将符合所述业务数据对应的服务机构的数据类型确定为所述业务数据的数据类型；和/或，
    根据数据类型确定方式的优先级，将优先级最高的确定方式所确定的数据类型作为所述业务数据的数据类型。
  7. 根据权利要求1所述的方法，其中，所述多条区块链为至少一个第一服务机构提供数据服务，所述多条区块链中的部分区块链为所述至少一个第一服务机构和至少一个第二服务机构提供数据服务；或，所述多条区块链为所述至少一个第一服务机构和所述至少一个第二服务机构均提供数据服务。
  8. 一种电子设备，其中，所述电子设备包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或所述指令集由所述处理器加载并执行以下操作：
    接收业务数据；
    根据所述业务数据的数据类型，从多条区块链中确定与所述业务数据对应 的目标区块链；
    基于所述业务数据以及所述目标区块链中第一区块的区块头特征值，在所述目标区块链上生成第二区块，所述第一区块为所述第二区块的上一个区块，所述第二区块用于记录所述业务数据。
  9. 根据权利要求8所述的电子设备，其中，所述处理器加载所述至少一条指令、所述至少一段程序、所述代码集或所述指令集执行以下操作：
    根据所述业务数据的数据类型查询预设对应关系，所述预设对应关系用于指示数据类型与区块链的对应关系；
    如果所述预设对应关系中存在与所述数据类型匹配的区块链，则将与所述数据类型匹配的区块链确定为所述目标区块链。
  10. 根据权利要求9所述的电子设备，其中，所述处理器加载所述至少一条指令、所述至少一段程序、所述代码集或所述指令集执行以下操作：
    如果所述预设对应关系中不存在与所述数据类型匹配的区块链，则将所述多条区块链中的共享区块链确定为所述目标区块链，所述共享区块链用于存储多个服务机构之间共享的业务数据。
  11. 根据权利要求8所述的电子设备，其中，所述处理器加载所述至少一条指令、所述至少一段程序、所述代码集或所述指令集执行以下操作：
    接收业务数据包；
    从所述业务数据包中获取业务数据和终端对所述业务数据的签名；
    所述处理器加载所述至少一条指令、所述至少一段程序、所述代码集或所述指令集还执行以下操作：
    如果对所述业务数据的签名验证通过，则根据所述业务数据的数据类型，从所述多条区块链中确定与所述业务数据对应的目标区块链。
  12. 根据权利要求8所述的电子设备，其中，所述处理器加载所述至少一条指令、所述至少一段程序、所述代码集或所述指令集执行以下操作：
    当接收到第一更新指令时，基于所述第一更新指令更新已配置的数据类型与待配置的区块链的对应关系；或，
    当接收到第二更新指令时，基于所述第二更新指令更新已配置的数据类型与已配置的区块链的对应关系；或，
    当接收到第三更新指令时，基于所述第三更新指令更新待配置的数据类型与待配置的区块链的对应关系；或，
    当接收到第四更新指令时，基于所述第四更新指令更新待配置的数据类型与已配置的区块链的对应关系。
  13. 根据权利要求8所述的电子设备，其中，所述处理器加载所述至少一条指令、所述至少一段程序、所述代码集或所述指令集执行以下操作：
    根据第一确定方式，将符合所述业务数据的描述对象的数据类型确定为所述业务数据的数据类型；和/或，
    根据第二确定方式，将符合所述业务数据的数据私密等级的数据类型确定为所述业务数据的数据类型；和/或，
    根据第三确定方式，将符合所述业务数据对应的服务机构的数据类型确定为所述业务数据的数据类型；和/或，
    根据数据类型确定方式的优先级，将优先级最高的确定方式所确定的数据类型作为所述业务数据的数据类型。
  14. 根据权利要求8所述的电子设备，其中，所述多条区块链为至少一个第一服务机构提供数据服务，所述多条区块链中的部分区块链为所述至少一个第一服务机构和至少一个第二服务机构提供数据服务；或，所述多条区块链为所述至少一个第一服务机构和所述至少一个第二服务机构均提供数据服务。
  15. 一种计算机可读存储介质，其中，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如权利要求1至权利要求7中任一项所述的业务数据存储方法。
PCT/CN2018/090681 2017-06-12 2018-06-11 业务数据存储方法、计算机可读存储介质以及电子设备 WO2018228337A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710438943.6A CN107315786B (zh) 2017-06-12 2017-06-12 业务数据存储方法及装置
CN201710438943.6 2017-06-12

Publications (1)

Publication Number Publication Date
WO2018228337A1 true WO2018228337A1 (zh) 2018-12-20

Family

ID=60182213

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/090681 WO2018228337A1 (zh) 2017-06-12 2018-06-11 业务数据存储方法、计算机可读存储介质以及电子设备

Country Status (2)

Country Link
CN (2) CN110348242B (zh)
WO (1) WO2018228337A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210103923A1 (en) * 2019-10-03 2021-04-08 Titan IO, Inc. Method, apparatus, and computer-readable medium for routing data services over a decentralized network
CN112995226A (zh) * 2021-05-12 2021-06-18 中航信移动科技有限公司 基于区块链的用户数据处理系统
WO2022216204A1 (en) * 2021-04-06 2022-10-13 Rz Capital Holding Ab Method and apparatus for handling secure communication using blockchains in a communications network

Families Citing this family (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110348242B (zh) * 2017-06-12 2021-01-15 腾讯科技（深圳）有限公司 业务请求处理方法及装置
CN108573741A (zh) * 2017-12-25 2018-09-25 北京金山云网络技术有限公司 业务数据记录方法、装置、设备和存储介质
CN110019235B (zh) * 2017-12-29 2021-08-17 百度在线网络技术（北京）有限公司 基于区块链的数据存储、恢复方法、装置、设备及介质
CN108347486A (zh) * 2018-02-12 2018-07-31 众安信息技术服务有限公司 基于区块链的跨链通信方法、装置以及系统
CN108765230B (zh) * 2018-04-10 2020-02-14 平安科技（深圳）有限公司 一种居民户籍信息管理方法及服务器
CN108537642A (zh) * 2018-04-20 2018-09-14 郑勇 一种基于区块链平台的线上线下的全域信用周期服务系统
CN110799966A (zh) * 2018-04-22 2020-02-14 因特比有限公司 用于使用现有区块链节点来托管新区块链的方法和系统
CN108646983B (zh) * 2018-05-08 2021-04-06 北京融链科技有限公司 在区块链上存储业务数据的处理方法和装置
CN110490753A (zh) * 2018-05-10 2019-11-22 触信（厦门）智能科技有限公司 一种区块链人脉管理系统
CN108764797B (zh) * 2018-05-31 2020-06-02 腾讯科技（深圳）有限公司 流通信息查询方法、装置、设备、系统及存储介质
CN110633389A (zh) * 2018-05-31 2019-12-31 阿里巴巴集团控股有限公司 区块链数据的处理方法、装置、系统以及电子设备
CN108932620A (zh) * 2018-07-06 2018-12-04 佛山伊苏巨森科技有限公司 一种区块链系统及其执行方法
CN108965450B (zh) * 2018-07-27 2021-05-28 江西贪玩信息技术有限公司 业务请求响应方法、装置、计算机设备和存储介质
CN108924250B (zh) * 2018-07-27 2022-02-11 江西贪玩信息技术有限公司 基于区块链的业务请求处理方法、装置和计算机设备
CN109040227B (zh) * 2018-07-27 2021-08-03 江西贪玩信息技术有限公司 基于区块链的业务请求响应方法、装置和计算机设备
CN109039750B (zh) * 2018-08-13 2021-06-15 浙商银行股份有限公司 一种提升区块链应用系统多城多园区部署灾备能力的方法
CN109299188A (zh) * 2018-08-21 2019-02-01 平安科技（深圳）有限公司 利用区块链数据存储方法、装置及电子设备
CN109347935B (zh) * 2018-09-30 2021-08-03 珠海信达九州科技有限公司 一种基于区块链实现实时通讯消息同步的方法
CN109284633B (zh) * 2018-10-30 2022-02-11 众安信息技术服务有限公司 用于区块链网络系统的数据处理方法和数据处理装置
CN111224793B (zh) * 2018-11-27 2021-06-01 华为技术有限公司 数据存储方法、装置、计算机设备及可读存储介质
CN109754321B (zh) * 2018-12-27 2022-02-11 石更箭数据科技(上海)有限公司 一种数据处理方法及其装置、介质、终端
JP7071938B2 (ja) * 2019-01-23 2022-05-19 株式会社日立製作所 データベース管理サービス提供システム
CN110071968B (zh) * 2019-04-16 2023-04-07 深圳前海微众银行股份有限公司 一种基于区块链的消息存储方法及装置
CN110222085B (zh) * 2019-05-07 2021-06-22 北京奇艺世纪科技有限公司 一种存证数据的处理方法、装置及存储介质
CN110381116A (zh) * 2019-06-19 2019-10-25 深圳壹账通智能科技有限公司 信息同步系统和信息同步方法
CN110602515B (zh) * 2019-09-16 2021-08-10 腾讯科技（深圳）有限公司 基于区块链的数据处理方法、服务器及存储介质
CN110633323B (zh) * 2019-09-16 2023-10-20 腾讯科技（深圳）有限公司 业务数据存储方法、装置、存储介质和计算机设备
CN110784521B (zh) * 2019-09-30 2022-05-27 远光软件股份有限公司 区块链的共识方法、电子设备和存储介质
CN110708390A (zh) * 2019-10-16 2020-01-17 腾讯科技（深圳）有限公司 基于节点间数据共享的数据处理方法、设备、装置、介质
CN113434550A (zh) * 2019-11-11 2021-09-24 蚂蚁区块链科技(上海)有限公司 一种块链式账本中的聚合计算方法、装置及设备
CN111125187A (zh) * 2019-11-29 2020-05-08 立旃（上海）科技有限公司 基于区块链的数据管理方法及装置
CN111147447A (zh) * 2019-12-03 2020-05-12 苏宁云计算有限公司 一种数据的保护方法及系统
CN110955509A (zh) * 2019-12-11 2020-04-03 深圳迅策科技有限公司 一种金融并发交易处理装置
CN111327457B (zh) * 2020-01-21 2022-07-05 山东公链信息科技有限公司 一种基于通信安全认证的区块链接口配置方法
CN111724169B (zh) * 2020-03-05 2022-10-18 支付宝(杭州)信息技术有限公司 一种业务处理系统、业务处理的方法、装置及设备
CN111460504B (zh) * 2020-03-31 2021-11-05 腾讯科技（深圳）有限公司 业务处理方法、装置、节点设备及存储介质
CN111562947B (zh) * 2020-04-01 2021-08-03 支付宝实验室(新加坡)有限公司 一种业务处理方法、装置及电子设备
CN111507594B (zh) * 2020-04-08 2023-06-09 微民保险代理有限公司 一种数据处理方法以及设备
CN111625593B (zh) * 2020-04-21 2023-09-08 金蝶软件（中国）有限公司 基于区块链的数据处理方法、装置、计算机设备
CN111614731B (zh) * 2020-04-29 2023-04-07 深圳市芯链科技有限公司 物联网设备接入区块链方法、系统、聚合网关及存储介质
CN111885133B (zh) * 2020-07-10 2023-06-09 深圳力维智联技术有限公司 基于区块链的数据处理方法、装置及计算机存储介质
CN114079612B (zh) * 2020-08-03 2024-06-04 阿里巴巴集团控股有限公司 容灾系统及其管控方法、装置、设备、介质
CN111970380B (zh) * 2020-09-02 2022-06-07 广东贤能数字科技有限公司 基于区块链的业务处理方法和系统
CN112434341B (zh) * 2020-11-02 2023-07-11 迅鳐成都科技有限公司 一种防业务篡改的区块链轻节点数据采集方法及装置
CN112465615B (zh) * 2020-12-01 2023-06-30 中国联合网络通信集团有限公司 账单数据的处理方法、装置及系统
CN112561493A (zh) * 2020-12-23 2021-03-26 中国银行股份有限公司 一种银行柜面系统切换方法及装置
CN112738213B (zh) * 2020-12-25 2023-06-30 深圳Tcl新技术有限公司 基于区块链的任务需求响应方法、装置、系统及存储介质
CN112699151B (zh) * 2021-01-04 2022-04-22 腾讯科技（深圳）有限公司 数据处理方法、装置、设备以及介质
CN113326165B (zh) * 2021-08-04 2021-11-16 腾讯科技（深圳）有限公司 基于区块链的数据处理方法、设备及计算机可读存储介质
CN113726758A (zh) * 2021-08-25 2021-11-30 百保(上海)科技有限公司 基于区块链的数据隐私计算方法及系统
CN114416870A (zh) * 2021-12-31 2022-04-29 航天信息股份有限公司 基于区块链的贸运一体化服务系统、数据共享方法和装置
US11606432B1 (en) * 2022-02-15 2023-03-14 Accenture Global Solutions Limited Cloud distributed hybrid data storage and normalization
CN114510736A (zh) * 2022-04-18 2022-05-17 武汉龙津科技有限公司 一种信息处理方法、装置、终端及存储介质
CN115193026A (zh) * 2022-09-16 2022-10-18 成都止观互娱科技有限公司 一种高并发全球同服游戏服务器架构及数据访问方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452785A (zh) * 2016-09-29 2017-02-22 财付通支付科技有限公司 区块链网络、分支节点及区块链网络应用方法
CN106528775A (zh) * 2016-10-28 2017-03-22 山东明和软件有限公司 支持逻辑多链的私有区块链运行支撑系统及其工作方法
CN106682984A (zh) * 2016-10-27 2017-05-17 上海亿账通区块链科技有限公司 基于区块链的交易事务处理方法及系统
US20170163733A1 (en) * 2015-12-02 2017-06-08 Olea Networks, Inc. System and method for data management structure using auditable delta records in a distributed environment
CN107291862A (zh) * 2017-06-12 2017-10-24 腾讯科技（深圳）有限公司 业务数据存储方法、装置、存储介质及电子设备
CN107315786A (zh) * 2017-06-12 2017-11-03 腾讯科技（深圳）有限公司 业务数据存储方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10225196B2 (en) * 2013-02-15 2019-03-05 Nxp Usa, Inc. Apparatus, system and method for controlling packet data flow
CN105488675B (zh) * 2015-11-25 2019-12-24 布比（北京）网络技术有限公司 一种区块链的分布式共享总账构建方法
CN105809062B (zh) * 2016-03-01 2019-01-25 布比（北京）网络技术有限公司 一种合约构建、执行方法及装置
CN106407021A (zh) * 2016-07-01 2017-02-15 厦门易名科技股份有限公司 一种基于队列的业务请求处理方法
CN106339639A (zh) * 2016-08-30 2017-01-18 弗洛格（武汉）信息科技有限公司 基于区块链的学分成绩管理方法及系统
CN106357405A (zh) * 2016-09-19 2017-01-25 弗洛格（武汉）信息科技有限公司 一种基于区块链技术一致性算法的数据管理方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170163733A1 (en) * 2015-12-02 2017-06-08 Olea Networks, Inc. System and method for data management structure using auditable delta records in a distributed environment
CN106452785A (zh) * 2016-09-29 2017-02-22 财付通支付科技有限公司 区块链网络、分支节点及区块链网络应用方法
CN106682984A (zh) * 2016-10-27 2017-05-17 上海亿账通区块链科技有限公司 基于区块链的交易事务处理方法及系统
CN106528775A (zh) * 2016-10-28 2017-03-22 山东明和软件有限公司 支持逻辑多链的私有区块链运行支撑系统及其工作方法
CN107291862A (zh) * 2017-06-12 2017-10-24 腾讯科技（深圳）有限公司 业务数据存储方法、装置、存储介质及电子设备
CN107315786A (zh) * 2017-06-12 2017-11-03 腾讯科技（深圳）有限公司 业务数据存储方法及装置

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210103923A1 (en) * 2019-10-03 2021-04-08 Titan IO, Inc. Method, apparatus, and computer-readable medium for routing data services over a decentralized network
US12008557B2 (en) * 2019-10-03 2024-06-11 Titan IO, Inc. Method, apparatus, and computer-readable medium for routing data services over a decentralized network
WO2022216204A1 (en) * 2021-04-06 2022-10-13 Rz Capital Holding Ab Method and apparatus for handling secure communication using blockchains in a communications network
CN112995226A (zh) * 2021-05-12 2021-06-18 中航信移动科技有限公司 基于区块链的用户数据处理系统
CN112995226B (zh) * 2021-05-12 2021-08-03 中航信移动科技有限公司 基于区块链的用户数据处理系统

Also Published As

Publication number Publication date
CN107315786B (zh) 2020-12-11
CN107315786A (zh) 2017-11-03
CN110348242A (zh) 2019-10-18
CN110348242B (zh) 2021-01-15

Similar Documents

Publication Publication Date Title
WO2018228337A1 (zh) 业务数据存储方法、计算机可读存储介质以及电子设备
WO2018228331A1 (zh) 业务数据存储方法、装置、存储介质及电子设备
US11461773B2 (en) Blockchain-based node management methods and apparatuses
US11895242B2 (en) Data processing method and apparatus in blockchain network, storage medium, and computer device
EP3732857B1 (en) Apparatus and method for decentralized-identifier creation
US20230316273A1 (en) Data processing method and apparatus, computer device, and storage medium
US20200118096A1 (en) System and method for providing privacy and security protection in blockchain-based private transactions
WO2018112940A1 (zh) 区块链节点的业务执行方法、装置及节点设备
CN111010372A (zh) 区块链网络身份认证系统、数据处理方法及网关设备
JP2021524088A (ja) リソース移行データの管理方法及び装置、並びにコンピュータプログラム
CN108769230B (zh) 交易数据存储方法、装置、服务器及存储介质
US20210399900A1 (en) Method and system for a trusted execution environment-based proof of stake protocol
WO2019011179A1 (zh) 证书管理方法、系统、网络设备及计算机可读存储介质
US20230037932A1 (en) Data processing method and apparatus based on blockchain network, and computer device
CN112749969B (zh) 一种数据处理方法、装置、计算机设备及存储介质
CN112702402A (zh) 基于区块链技术实现政务信息资源共享和交换的系统、方法、装置、处理器及其存储介质
US11038685B1 (en) Correcting blockchain transactions with cryptocurrency type mistakes
WO2022193984A1 (zh) 跨链进行数据传输的方法、装置、计算机设备、存储介质和计算机程序产品
CN113255014B (zh) 一种基于区块链的数据处理方法以及相关设备
EP3792855A1 (en) A method and system for executing fast and safe transactions involving a high-latency blockchain
CN117938867A (zh) 一种多区块链数据处理方法、装置、设备、介质及产品
CN116137627A (zh) 一种基于区块链网络的数据处理方法、装置及相关设备
CN118433257A (zh) 基于区块链的节点资源处理方法、装置、设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18818252

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18818252

Country of ref document: EP

Kind code of ref document: A1