WO2018161478A1 - Support d'informations, serveur, dispositif et procédé de traitement de fragmentation destiné à être utilisé avec des chaînes multi-blocs - Google Patents

Support d'informations, serveur, dispositif et procédé de traitement de fragmentation destiné à être utilisé avec des chaînes multi-blocs Download PDF

Info

Publication number
WO2018161478A1
WO2018161478A1 PCT/CN2017/091269 CN2017091269W WO2018161478A1 WO 2018161478 A1 WO2018161478 A1 WO 2018161478A1 CN 2017091269 W CN2017091269 W CN 2017091269W WO 2018161478 A1 WO2018161478 A1 WO 2018161478A1
Authority
WO
WIPO (PCT)
Prior art keywords
blockchain
identifier
application client
transaction request
service type
Prior art date
Application number
PCT/CN2017/091269
Other languages
English (en)
Chinese (zh)
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 上海亿账通区块链科技有限公司
Priority to SG11201907939VA priority Critical patent/SG11201907939VA/en
Publication of WO2018161478A1 publication Critical patent/WO2018161478A1/fr

Links

Classifications

    • 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • 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
    • 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1014—Server selection for load balancing based on the content of a request
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present application relates to the field of Internet technologies, and in particular, to a fragment processing method, apparatus, server, and storage medium for a multi-block chain.
  • the application-level code of the blockchain refers to the application-level code called in the application domain of the blockchain.
  • the application areas of blockchain include smart contracts, securities trading and e-commerce.
  • the application-level code can be used to trade on the blockchain, and the transaction result is saved in the blockchain.
  • In the traditional blockchain platform there is usually only one blockchain, and the blockchain covers a variety of business types, through which electronic transactions of multiple business types can be performed. If a large number of transaction requests are initiated to this blockchain at the same time, it will undoubtedly have a great impact on the performance of the blockchain, and may even lead to a blockchain platform downtime.
  • a method, an apparatus, a server, and a storage medium for a slice processing of a multi-block chain are provided.
  • a fragmentation processing method for a multi-block chain comprising:
  • the transaction request is assigned to a blockchain corresponding to the selected blockchain identity such that the application level code deployed on the blockchain completes the transaction in accordance with the application client parameters.
  • a fragment processing device for a multi-block chain comprising:
  • An application-level code fragmentation server is configured to receive a transaction request of an application client, where the transaction request carries an application client parameter, the application client parameter includes a service type, and acquires a blockchain identifier of multiple blockchains.
  • the blockchain has a corresponding service type, and the application level code is deployed on the blockchain; the application client parameter is parsed, and the blockchain identifier corresponding to the service type carried by the transaction request is selected. ;and
  • An application level code fragmentation client configured to allocate the transaction request to a blockchain corresponding to the selected blockchain identity, such that the application level code deployed on the blockchain is based on the application client parameter Seal the deal.
  • a server comprising a memory and a processor, the memory storing computer executable instructions, the computer executable instructions being executed by the processor, such that the processor performs the following steps:
  • the transaction request is assigned to a blockchain corresponding to the selected blockchain identity such that the application level code deployed on the blockchain completes the transaction in accordance with the application client parameters.
  • One or more non-volatile readable storage media storing computer-executable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:
  • the transaction request is assigned to a blockchain corresponding to the selected blockchain identity such that the application level code deployed on the blockchain completes the transaction in accordance with the application client parameters.
  • FIG. 1 is an application scenario diagram of a fragment processing method of a multi-block chain in an embodiment
  • FIG. 2 is a flow chart of a method for processing a multi-block chain in an embodiment
  • FIG. 3 is a block diagram of a fragmentation processing system of a multi-block chain in one embodiment
  • Figure 4 is a block diagram of a server in one embodiment
  • Figure 5 is a block diagram of a fragment processing apparatus of a multi-block chain in one embodiment
  • Figure 6 is a block diagram of a slice processing apparatus of a multi-block chain in another embodiment.
  • the fragment processing processing method of the multi-block chain provided in the embodiment of the present application can be applied to the application scenario shown in FIG. 1.
  • the client terminal 102 is connected to the server 104 via a network.
  • An application client is installed on the client terminal 102.
  • Each application client can be used to conduct a type of transaction.
  • An application level code fragmentation server and a plurality of application level code fragmentation clients are run on the server 104.
  • the application-level code fragment client has a one-to-one correspondence with the blockchain.
  • the application level code fragmentation server receives the transaction request sent by the application client.
  • the application client parameters are carried in the transaction request.
  • the application-level code fragmentation server parses the application client parameters to obtain the service type, service identifier, and transaction data it contains.
  • the application level code fragmentation server obtains the blockchain identifier of the plurality of blockchains, and selects the blockchain identifier corresponding to the service type carried in the transaction request among the plurality of blockchain identifiers.
  • the blockchain and the application-level code fragmentation client are in one-to-one correspondence, and the application-level code fragmentation server selects the corresponding application-level code fragmentation client according to the selected blockchain identifier, and forwards the transaction request to the application.
  • Level code fragmentation client The application-level code fragmentation client invokes the external interface of the corresponding blockchain according to the transaction request, thereby calling the application-level code deployed on the blockchain to execute the transaction according to the application client parameters. Since the blockchain has a corresponding service type, the transaction request is assigned to the blockchain corresponding to the service type, and in the face of the massive transaction request, the transactions of different service types can be performed in different blockchains, effectively improving The performance of the blockchain.
  • a multi-block chain fragmentation processing method is provided. It should be understood that although the steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these The steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and may be performed in other sequences. Moreover, at least some of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, and the order of execution thereof is not necessarily This may be performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
  • the method is applied to the server in FIG. 1 as an example, and specifically includes:
  • Step 202 Receive a transaction request sent by an application client, where the transaction request carries an application client parameter, where the application client parameter includes a service type.
  • Step 204 Obtain a blockchain identifier of multiple blockchains, the blockchain has a corresponding service type, and an application-level code is deployed on the blockchain.
  • Step 206 Parse the application client parameter, and select a blockchain identifier corresponding to the service type carried by the transaction request.
  • Step 208 Assign the transaction request to the blockchain corresponding to the selected blockchain identifier, so that the application level code deployed on the blockchain completes the transaction according to the application client parameter.
  • the application client is installed on the client terminal. Each application client can be used to conduct a type of transaction.
  • the client terminal can conduct transactions of different service types through different application clients.
  • An application client can be installed on the same client terminal, or multiple application clients can be installed.
  • Each blockchain has a corresponding service type, and the same service type can also correspond to multiple blockchains.
  • Each blockchain can have a corresponding blockchain identity.
  • the blockchain identifier can be the number of the blockchain.
  • Application-level code can be deployed on each blockchain according to preset rules.
  • the blockchain provides multiple types of external interfaces for application-level code.
  • the external interface includes an initialization interface, a transaction call interface, a transaction result query interface, and a blockchain status query interface.
  • the user of the blockchain can call the application-level code deployed on the specified blockchain when the application client and the server call these external interfaces, so that each blockchain can execute the transaction corresponding to its business type. This can also be called fragmentation of application-level code.
  • An application-level code fragmentation server and multiple application-level code fragmentation clients are running on the server.
  • the application-level code fragment client has a one-to-one correspondence with the blockchain.
  • the application level code fragmentation server and multiple application level code fragment clients are started, the application level code fragmentation server establishes a connection with multiple application clients, and the application level code fragmentation client and the one-to-one corresponding area are connected.
  • the application-level code deployed on the blockchain establishes a connection.
  • the application-level code fragmentation server running on the server receives the transaction request sent by the application client.
  • the application client parameters are carried in the transaction request.
  • the application-level code fragmentation server parses the application client parameters to obtain the service type, service identifier, and transaction data it contains. Among them, the transaction data includes the transaction object, the transaction amount and the transaction date.
  • the application level code fragmentation server obtains the blockchain identifier of the plurality of blockchains, and selects the blockchain identifier corresponding to the service type carried in the transaction request among the plurality of blockchain identifiers. Specifically, if there is only one blockchain identifier corresponding to the service type carried in the transaction request, the blockchain identifier is recorded as the selected blockchain identifier.
  • the application-level code fragmentation server performs load balancing processing according to the blockchain identifier, and is in the blockchain identifier of multiple the same service types. Select one of them and record the selected blockchain ID as the selected blockchain ID.
  • the application-level code fragmentation server selects the corresponding application-level code fragmentation client according to the selected blockchain identifier, and forwards the transaction request to Application level code fragmentation client. In this way, based on the blockchain load balancing and data consistency, the appropriate application-level code client can be selected to process the transaction request.
  • the application-level code fragmentation client invokes the external interface of the corresponding blockchain according to the transaction request, thereby calling the application-level code deployed on the blockchain to execute the transaction according to the application client parameters. It can effectively avoid the problem of migrating data between different blockchains and the extra load due to data migration.
  • the transaction request of the application client after receiving the transaction request of the application client, parsing the application client parameter carried in the transaction request, and selecting a blockchain identifier corresponding to the service type carried in the transaction request in the plurality of blockchain identifiers. , thereby allocating the transaction request to the blockchain corresponding to the selected blockchain identifier, so that the application level code deployed on the blockchain completes the transaction according to the application client parameter. Since the blockchain has a corresponding service type, the transaction request is assigned to the blockchain corresponding to the service type, and in the face of the massive transaction request, the transactions of different service types can be performed in different blockchains, effectively improving The performance of the blockchain.
  • the step of parsing the application client parameter and selecting the blockchain identifier corresponding to the service type carried in the transaction request includes: if the blockchain identifier corresponding to the service type carried in the transaction request is multiple Then, hash calculation is performed according to the service type, the service identifier, and each blockchain identifier to obtain a corresponding hash result set; and the blockchain identifier corresponding to the transaction request is selected according to the hash result set.
  • the server establishes a connection with multiple blockchains, and establishes a connection with multiple application clients.
  • the server needs to ensure that data between the blockchains does not migrate, and it is necessary to ensure load balancing and data consistency of the blockchain. That is, the server needs to ensure that multiple blockchains can be called evenly, and all transaction requests sent by the same application client are assigned to the same blockchain.
  • the application-level code fragmentation server running on the server parses the application client parameters to obtain a corresponding service type and service identifier. If the blockchain identifier corresponding to the service type carried in the transaction request is multiple, the application-level code fragmentation server obtains multiple blockchain identifiers of the same service type. The application-level code fragmentation server performs hash calculation using the service type, the service identifier, and each blockchain identifier to obtain a corresponding hash result set. For example, the hash algorithm with the highest random weight is used to perform consistent hash calculation on the service type, service identifier, and blockchain identifier, and the corresponding hash result is obtained.
  • the application-level code fragmentation server parses the application client parameters carried in each transaction request to obtain each application client.
  • the service type and service identifier entered by the terminal.
  • the application-level code fragmentation server performs hash calculation on each application client input service type, service identifier, and each blockchain identifier to a corresponding hash result set.
  • the server selects the corresponding blockchain identifier of each transaction request in the hash result set by means of load balancing mode and hash result consistency.
  • the application level code fragmentation server performs load balancing processing on the hash result, and selects the blockchain identifier corresponding to the transaction request among the plurality of blockchain identifiers of the same service type. Thereby, the balanced use of multiple blockchains can be realized, and the load balance of the blockchain can be effectively ensured. Moreover, it is possible to allocate transaction requests of the same application client to the same blockchain, thereby effectively ensuring data consistency of the blockchain. By selecting a suitable blockchain for the transaction request sent by the application client, it can ensure that the number of blockchains does not change, regardless of whether the data volume of the application client changes, it will not cause data migration between the blockchains. That is, there is no case where the transaction data of one blockchain migrates to another blockchain.
  • the step of parsing the application client parameter and selecting the blockchain identifier corresponding to the service type carried in the transaction request includes: if the blockchain identifier corresponding to the service type carried in the transaction request is more The blockchain of the same service type is taken as a physical blockchain, and the physical blockchain is divided into multiple virtual blockchains; the virtual blockchain identifier corresponding to multiple virtual blockchains is obtained; according to the service type The service identifier and each virtual blockchain identifier are respectively hashed to obtain a corresponding hash result set; and the virtual blockchain identifier corresponding to the transaction request is selected according to the hash result set.
  • the application-level code fragment server running on the server receives multiple transaction requests of the same service type, and the number of transaction requests of the same service type is greater than the number of blockchains of the same service type, the application level runs on the server.
  • the code fragmentation server can use the blockchain of the same service type as a physical blockchain.
  • the application level code fragmentation server divides each physical blockchain into multiple virtual blockchains, and generates a corresponding virtual blockchain identifier for each virtual blockchain.
  • the application-level code fragmentation server performs hash calculation according to the service type, the service identifier, and each virtual blockchain identifier, and obtains a corresponding hash result set.
  • the server selects the corresponding blockchain identifier of each transaction request in the hash result set by means of load balancing mode and hash result consistency.
  • the application level code fragmentation server performs load balancing processing on the hash result, and selects a virtual blockchain identifier corresponding to the transaction request among the plurality of virtual blockchain identifiers of the same service type.
  • the selected virtual blockchain identifier is recorded as the selected virtual blockchain identifier.
  • the application level code fragmentation server forwards the plurality of transaction requests to the application level code fragmentation client one-to-one corresponding to the selected virtual blockchain identifier.
  • the transaction request is allocated to the corresponding virtual blockchain identifier by the application level code fragmentation client, and the physical blockchain mapped by the virtual blockchain is accessed according to the virtual blockchain identifier.
  • the transaction request of the same application client can be allocated to the same blockchain, which effectively ensures the data consistency of the blockchain.
  • the step of parsing the application client parameter and selecting the blockchain identifier corresponding to the service type carried by the transaction request includes: when the number of the blockchain changes, acquiring a mapping table, where the mapping table includes an application.
  • the number of blockchains connected to the server may change.
  • the connection between the blockchain and the server may be faulty, resulting in the blockchain being unavailable and the number of blockchains being reduced.
  • the server may pre-establish a mapping relationship between the application client parameters and the blockchain identifier, where the application client parameters include a service type and a service identifier.
  • the application-level code fragmentation server running on the server receives the transaction request sent by the application client, the corresponding blockchain identifier is retrieved in the mapping table according to the mapping relationship and the service type and the service identifier carried in the transaction request, and the search is performed.
  • the obtained blockchain identifier is recorded as the selected blockchain identifier.
  • the transaction request is thus assigned to the selected blockchain identity.
  • the load balancing and data consistency of the blockchain are realized.
  • mapping table is stored in the disk storage of the server, and can be cached in the memory, so that it can be quickly read when selecting a suitable blockchain identifier for the transaction request. If application client parameters and/or blockchain identifiers are added, the application-level code fragmentation server running on the server can update the mapping table according to the newly added application client parameters and/or the blockchain identifier. And the updated mapping table can be cached into memory.
  • the method further comprises: receiving an event message flow acquisition request sent by the application client; sending the event message flow acquisition request to the blockchain allocated by the transaction request; and executing the transaction by the blockchain through the application level code The corresponding event message flow is obtained, and the event message flow is returned to the application client.
  • the server in addition to running the application level code fragmentation server and the application level code fragmentation client, the server also runs an event message server and an event message client.
  • the event message client may be multiple, and may have a one-to-one correspondence with the blockchain.
  • the application level code fragmentation server, the application level code fragmentation client, the event message server, and the event message client running on the server may be collectively referred to as a multi-block chain fragmentation processing system.
  • the application-level code fragmentation server establishes a connection with multiple application clients
  • the event message server establishes a connection with multiple application clients
  • the application-level code deployed on a corresponding blockchain establishes a connection
  • the event message client establishes a connection with the application-level code deployed on the one-to-one blockchain, as shown in FIG.
  • Each blockchain can have a one-to-one correspondence with the application level code fragment client and the event message client, respectively.
  • the multi-block chain fragmentation processing system establishes the above connection after startup, avoiding the extra network connection burden caused by establishing the connection when executing application level code and event processing.
  • the multi-block chain fragmentation processing system monitors the connection between the blockchain and the application-level code fragmentation client and the connection between the blockchain and the event message client.
  • the connection between the blockchain and the application-level code fragmentation client or the event message client is broken, the disconnected blockchain is not available and cannot handle transactions and event message flows. After the network connection of the blockchain is restored, it can be used as an available blockchain again.
  • Events include events that are triggered when the application client communicates with the application-level code fragment server, events that are triggered when the application client communicates with the event message server, and triggers when the application-level code deployed on the blockchain is executed. event. For example, registration, logout and rejection, etc., as well as transaction status and blockchain status.
  • the application-level code deployed on the blockchain can return information about communication events such as registration, logout, and rejection to the server in a synchronous or asynchronous manner.
  • the transaction status and other events of interest to the user need to be actively obtained by the user through the application client.
  • multiple application clients communicate with multiple blockchains through an event message flow.
  • the application client can register events of interest, such as transaction status and blockchain status, with the event message server.
  • the event message flow acquisition request may be sent to the event message server, and the application-level code fragmentation server selects the corresponding service type and service identifier carried in the transaction request.
  • Blockchain The application-level code sharding client distributes the application client's transaction request to the selected blockchain.
  • the event message server forwards the event message flow acquisition request sent by the application client to the event message client, and the event message client sends the event message flow acquisition request to the blockchain that processes the transaction request. That is, the transaction request and event message flow get request are assigned to the same blockchain.
  • the event client invokes the external interface of the application-level code in a synchronous or asynchronous manner to obtain an event message flow.
  • the event client returns the obtained event message flow to the event server, and the event server sends the event message stream to the corresponding application client. Therefore, it is no longer necessary to query the event of interest through the application client, and the message of the event of interest to the user can be directly learned, which provides convenience for the user.
  • the event server can concurrently read event message flows of multiple application clients, and send the read event message stream to the corresponding blockchain through the event client.
  • the event client can also read the event message stream of the blockchain in a concurrent form, and send the event message stream to the application client through the event server.
  • Concurrency includes process concurrency processing, thread concurrency processing, and coroutine concurrency processing.
  • a plurality of multi-block chain fragmentation processing systems can be run on the server, and multiple multi-block chain fragmentation processing systems can form a multi-block chain fragmentation processing cluster.
  • the application client and blockchain can establish a connection with a multi-block chain fragmentation processing system in a multi-block chain fragmentation processing cluster.
  • the connected multi-block chain fragmentation processing system fails, it can switch to other multi-block chain fragmentation processing systems in the multi-blockchain fragmentation processing cluster to continue to perform transaction and event message stream processing.
  • the single-point failure of the multi-block chain fragmentation processing system is eliminated by the cluster mode, and the performance of the multi-block chain fragmentation processing is effectively improved.
  • a server 400 includes a processor 401, an internal memory 402, a non-volatile storage medium 403, and a network interface 404 that are coupled by a system bus.
  • the processor 401 is configured to provide computing and control capabilities.
  • An operating system 4031 and computer executable instructions 4032 are stored in the non-volatile storage medium 403.
  • the internal memory 402 provides an environment for the operation of computer executable instructions 4032 in a non-volatile storage medium, and when the computer executable instructions 4032 are executed by the processor 401, the processor 401 can be caused to perform the aforementioned multi-block chain fragmentation processing. method.
  • the computer executable instructions 4032 are used to achieve time-consuming reduction of the customer data masking process and improve the shielding processing efficiency.
  • the network interface 404 is configured to communicate with an external client terminal via a network connection, such as receiving a transaction request uploaded by the client terminal, sending an event message stream to the client terminal, and the like.
  • the server 400 can be implemented by a stand-alone server or a server cluster composed of a plurality of servers. It will be understood by those skilled in the art that the structure shown in FIG. 4 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. Specifically, the server may include More or fewer components than shown in the figure, or some components combined, or with different component arrangements.
  • a multi-block chain fragmentation processing apparatus 500 including: an application level code fragmentation server 502 and an application level code fragmentation client 504, wherein:
  • the application-level code fragmentation server 502 is configured to receive a transaction request of the application client, where the transaction request carries an application client parameter, the application client parameter includes a service type, and acquires a blockchain identifier of multiple blockchains, and the block
  • the chain has a corresponding service type, and application level code is deployed on the blockchain; the application client parameters are parsed, and the blockchain identifier corresponding to the service type carried by the transaction request is selected.
  • An application level code fragmentation client 504 is configured to assign a transaction request to a blockchain corresponding to the selected blockchain identity such that the application level code deployed on the blockchain completes the transaction based on the application client parameters.
  • the application client parameter further includes a service identifier
  • the application-level code fragmentation server 502 is further configured to: if the blockchain identifier corresponding to the service type carried in the transaction request is multiple, according to the service type, The service identifier and each blockchain identifier are separately hashed to obtain a corresponding hash result set; and the blockchain identifier corresponding to the transaction request is selected according to the hash result set.
  • the application client parameter further includes a service identifier
  • the application-level code fragmentation server 502 is further configured to: if the blockchain identifier corresponding to the service type carried in the transaction request is multiple, the same service type is used.
  • the blockchain is used as a physical blockchain, and the physical blockchain is divided into a plurality of virtual blockchains; the virtual blockchain identifier corresponding to the plurality of virtual blockchains is obtained; according to the service type, the service identifier, and each virtual The blockchain identifiers are respectively hashed to obtain a corresponding hash result set; and the virtual blockchain identifier corresponding to the transaction request is selected according to the hash result set.
  • the application level code fragmentation server 502 is further configured to: when the number of the blockchain changes, obtain a mapping table, where the mapping table includes a mapping relationship between the application client parameter and the blockchain identifier, and the application The client parameter includes a service type and a service identifier.
  • the corresponding blockchain identifier is retrieved in the mapping table according to the mapping relationship and the service type and the service identifier carried in the transaction request, and the retrieved blockchain identifier is recorded as the selected region.
  • Blockchain identification when the number of the blockchain changes, obtain a mapping table, where the mapping table includes a mapping relationship between the application client parameter and the blockchain identifier, and the application The client parameter includes a service type and a service identifier.
  • the corresponding blockchain identifier is retrieved in the mapping table according to the mapping relationship and the service type and the service identifier carried in the transaction request, and the retrieved blockchain identifier is recorded as the selected region.
  • the apparatus further includes an event message server 506 and an event message client 508, wherein:
  • the event message server 506 is configured to receive an event message flow acquisition request sent by the application client, and send the event message flow acquisition request to the blockchain allocated by the transaction request.
  • the event message client 508 is configured to: when the blockchain executes the transaction through the application level code, obtain a corresponding event message flow, and return the event message flow to the application client.
  • Each of the modules in the multi-block chain fragmentation processing apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof.
  • the application level code fragmentation server 502 is configured to receive a transaction request sent by an application client through a network interface.
  • the network interface may be an Ethernet card or a wireless network card.
  • the above modules may be embedded in the hardware of the base station or may be stored in the memory of the base station in a software form, so that the processor can call the corresponding operations of the above modules.
  • the processor may be a central processing unit (CPU) or a microprocessor.
  • the program can be stored in a non-transitory computer readable storage medium, which, when executed, can include the flow of an embodiment of the methods described above.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Computer And Data Communications (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Debugging And Monitoring (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé de traitement de fragmentation destiné à être utilisé avec des chaînes multi-blocs, comprenant les étapes consistant : à recevoir une demande de transaction qui est envoyée par un client d'application, la demande de transaction portant des paramètres de client d'application en son sein, et les paramètres de client d'application comprenant un type de service; à obtenir des identifiants de chaîne de blocs pour une pluralité de chaînes de blocs, une chaîne de blocs ayant un type de service correspondant et la chaîne de blocs déployant un code de niveau d'application en son sein; à analyser les paramètres de client d'application, et à sélectionner un identifiant de chaîne de blocs correspondant au type de service porté par la demande de transaction; à attribuer la demande de transaction à une chaîne de blocs correspondant à l'identifiant de chaîne de blocs sélectionné de telle sorte que le code de niveau d'application qui est déployé sur la chaîne de blocs achève une transaction conformément aux paramètres de client d'application.
PCT/CN2017/091269 2017-03-09 2017-06-30 Support d'informations, serveur, dispositif et procédé de traitement de fragmentation destiné à être utilisé avec des chaînes multi-blocs WO2018161478A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
SG11201907939VA SG11201907939VA (en) 2017-03-09 2017-06-30 Fragmentation processing method for use with multi-blockchains, device, server and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710139277.6A CN106899680B (zh) 2017-03-09 2017-03-09 多区块链的分片处理方法和装置
CN201710139277.6 2017-03-09

Publications (1)

Publication Number Publication Date
WO2018161478A1 true WO2018161478A1 (fr) 2018-09-13

Family

ID=59184470

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/091269 WO2018161478A1 (fr) 2017-03-09 2017-06-30 Support d'informations, serveur, dispositif et procédé de traitement de fragmentation destiné à être utilisé avec des chaînes multi-blocs

Country Status (3)

Country Link
CN (1) CN106899680B (fr)
SG (1) SG11201907939VA (fr)
WO (1) WO2018161478A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110147942A (zh) * 2019-04-29 2019-08-20 阿里巴巴集团控股有限公司 一种基于区块链的业务配置方法、装置以及电子设备
CN110428329A (zh) * 2019-07-01 2019-11-08 扬州腾邮大数据网络科技有限公司 一种多区块链的分片处理方法和装置
CN110633323A (zh) * 2019-09-16 2019-12-31 腾讯科技（深圳）有限公司 业务数据存储方法、装置、存储介质和计算机设备
EP3496370A4 (fr) * 2017-09-30 2020-02-19 One Connect Smart Technology Co., Ltd. (Shenzhen) Procédé de chargement amont de données de chaîne de blocs, système, système informatique, et support de stockage
CN111275553A (zh) * 2020-01-20 2020-06-12 联动优势(北京)数字科技有限公司 一种区块链的数据存储方法及区块链系统
CN111444445A (zh) * 2020-03-25 2020-07-24 平安医疗健康管理股份有限公司 一种数据传输方法、系统、计算机设备和可读存储介质
CN111489256A (zh) * 2019-01-25 2020-08-04 京东数字科技控股有限公司 用于多链区块链系统中的跨链处理方法、设备及系统
CN112651044A (zh) * 2020-12-29 2021-04-13 杭州趣链科技有限公司 基于区块链技术的业务交易方法、系统及存储介质
CN112769943A (zh) * 2021-01-15 2021-05-07 河北蜂之巢互联网技术有限公司 一种业务处理的方法及装置
CN112988738A (zh) * 2019-12-16 2021-06-18 北京百度网讯科技有限公司 用于区块链的数据分片方法和装置
CN114741066A (zh) * 2022-06-09 2022-07-12 天聚地合(苏州)科技股份有限公司 区块链应用的生成方法及生成系统
CN117294757A (zh) * 2023-11-27 2023-12-26 山东省计算中心（国家超级计算济南中心） 基于区块链的复杂业务拆分执行方法、系统、设备及介质

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106682984B (zh) * 2016-10-27 2019-09-10 深圳壹账通智能科技有限公司 基于区块链的交易事务处理方法及系统
CN106899680B (zh) * 2017-03-09 2019-07-30 深圳壹账通智能科技有限公司 多区块链的分片处理方法和装置
CN107562775B (zh) 2017-07-14 2020-04-24 创新先进技术有限公司 一种基于区块链的数据处理方法及设备
CN107423124A (zh) * 2017-07-27 2017-12-01 中链科技有限公司 一种用于对交易数据进行并行处理的方法
CN108540536B (zh) * 2018-03-16 2021-07-23 深圳前海微众银行股份有限公司 基于区块链的网络海量业务处理方法、设备及存储介质
CN108616578A (zh) * 2018-04-09 2018-10-02 上海点融信息科技有限责任公司 跨区块链平台的业务处理方法、设备及计算机可读存储介质
EP3782387B1 (fr) * 2018-04-16 2022-03-02 BC Development Labs GmbH Réseau de noeuds distants incitatif sans état sans confiance utilisant des clients de vérification minimale
CN108924175A (zh) * 2018-05-02 2018-11-30 北京链链信息技术有限公司 一种区块链间的通信方法和装置
CN108846749B (zh) * 2018-05-31 2021-09-07 杭州溪塔科技有限公司 一种基于区块链技术的分片化的交易执行系统及方法
CN108777712B (zh) * 2018-05-31 2020-04-07 中国联合网络通信集团有限公司 区块链节点通信方法、装置及区块链节点
CN110557416B (zh) * 2018-05-31 2022-02-18 本无链科技(深圳)有限公司 一种多节点协同打块的方法及系统
CN109191287B (zh) * 2018-06-27 2020-08-04 浙江超脑时空科技有限公司 一种区块链智能合约的分片方法、装置及电子设备
CN109064327B (zh) * 2018-06-29 2021-01-08 浙江超脑时空科技有限公司 一种智能合约处理方法、装置及设备
CN108881274B (zh) * 2018-07-06 2019-10-01 众安信息技术服务有限公司 一种基于应用的区块链分片方法及装置
CN109146447B (zh) * 2018-07-09 2022-07-05 矩阵元技术（深圳）有限公司 区块链透明分片方法、装置及系统
CN109088954B (zh) * 2018-07-13 2021-09-28 中国电子科技集团公司第十五研究所 一种分布式物体标识信息注册与解析的方法
WO2020022957A1 (fr) * 2018-07-27 2020-01-30 Aioz Pte Ltd Procédé et appareil de vérification de transactions dans un réseau de chaînes de blocs
CN109034809B (zh) * 2018-08-16 2021-08-17 北京京东尚科信息技术有限公司 区块链的生成方法、装置、区块链节点及存储介质
CN109063179A (zh) * 2018-08-23 2018-12-21 靳芯 区块链平台的扩展方法及相关装置
WO2020056570A1 (fr) * 2018-09-18 2020-03-26 柯宾汉数位金融科技有限公司 Procédé de génération de bloc basé sur un mécanisme de fragmentation pour un réseau de blocs, et système de réseau de blocs
CN109284119B (zh) * 2018-09-27 2021-12-28 维沃移动通信有限公司 一种应用功能控制参数处理方法、装置及设备
CN109413175B (zh) * 2018-10-19 2021-07-20 北京奇艺世纪科技有限公司 一种信息处理方法、装置及电子设备
CN109462641B (zh) * 2018-10-30 2021-12-10 深圳市元征科技股份有限公司 一种用户通信方法及系统、设备、计算机可读存储介质
CN109685488A (zh) * 2018-12-24 2019-04-26 杭州复杂美科技有限公司 转账交易分片处理方法、设备和存储介质
CN109687953B (zh) * 2018-12-24 2021-12-31 杭州复杂美科技有限公司 交易分类方法、设备和存储介质
CN109617992B (zh) * 2018-12-29 2021-08-03 杭州趣链科技有限公司 一种基于区块链的边缘计算节点动态选举方法
US11195180B2 (en) * 2019-01-25 2021-12-07 International Business Machines Corporation Virtual blockchain
CN111612452A (zh) * 2019-02-22 2020-09-01 中细软集团有限公司 一种基于区块链的知识产权管理系统及方法
CN109951537B (zh) * 2019-03-06 2021-09-10 上海共链信息科技有限公司 一种面向区块链的负载均衡分发方法
CN110032602B (zh) * 2019-04-17 2021-04-27 中国联合网络通信集团有限公司 一种产品信息存储、查询和管理系统及方法
CN110336853A (zh) * 2019-05-08 2019-10-15 重庆天蓬网络有限公司 一种大数据量的区块链水平扩展解决方法
CN111865558A (zh) * 2019-05-19 2020-10-30 北京骑胜科技有限公司 服务数据处理方法、装置、电子设备及存储介质
CN110209681A (zh) * 2019-05-22 2019-09-06 深圳壹账通智能科技有限公司 区块链数据入链方法、装置、计算机设备和存储介质
CN110166565A (zh) * 2019-05-30 2019-08-23 中国联合网络通信集团有限公司 区块链分域触发方法及系统
US11115189B2 (en) 2019-06-03 2021-09-07 Advanced New Technologies Co., Ltd. Verifying a blockchain-type ledger
CN110349019B (zh) * 2019-06-03 2020-11-10 创新先进技术有限公司 一种块链式账本中的验证方法、装置及设备
CN110598446A (zh) * 2019-09-16 2019-12-20 腾讯科技（深圳）有限公司 基于区块链的测试方法、装置、存储介质和计算机设备
CN110958324B (zh) * 2019-12-12 2023-12-19 度小满科技(北京)有限公司 一种区块链网络的数据处理方法及装置
CN111078700A (zh) * 2019-12-13 2020-04-28 山东众阳健康科技集团有限公司 一种基于区块链的数据同步方法及系统
CN112019603B (zh) * 2020-08-10 2022-04-08 中国联合网络通信集团有限公司 一种交易数据的处理方法及装置
CN112001801A (zh) * 2020-10-28 2020-11-27 支付宝(杭州)信息技术有限公司 在区块链系统中进行资源转移的方法和装置
CN113110936A (zh) * 2021-04-14 2021-07-13 区块动力(广州)科技有限公司 一种对区块链节点运行性能的调节方法
CN113312427B (zh) * 2021-05-24 2023-04-28 网易（杭州）网络有限公司 区块链调用方法、装置、管理服务平台及存储介质
CN113535432B (zh) * 2021-07-20 2023-12-15 西安力传智能技术有限公司 数据分流方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056333A (zh) * 2009-11-05 2011-05-11 中国移动通信集团河南有限公司 Wap网关及其业务处理方法和wap代理服务器
CN105607951A (zh) * 2015-12-17 2016-05-25 北京奇虎科技有限公司 处理数据请求及获取服务器信息的方法及装置
WO2017021155A1 (fr) * 2015-07-31 2017-02-09 British Telecommunications Public Limited Company Fourniture de ressource commandée dans des environnements informatiques distribués
KR101701131B1 (ko) * 2016-04-28 2017-02-13 주식회사 라피 이종간 블록체인 연결을 이용한 데이터 기록/검증 방법 및 시스템
CN106899680A (zh) * 2017-03-09 2017-06-27 上海亿账通区块链科技有限公司 多区块链的分片处理方法和装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104079630A (zh) * 2014-06-09 2014-10-01 中国建设银行股份有限公司 一种业务服务端负载均衡方法、客户端、服务端以及系统
WO2016022864A2 (fr) * 2014-08-06 2016-02-11 Blockchain Technologies Corporation Système et procédé permettant de recevoir et compter soigneusement des votes lors d'une élection
EP3317775B1 (fr) * 2015-07-02 2022-02-16 Nasdaq, Inc. Systèmes et procédés de provenance sécurisée pour des bases de données de transactions distribuées
CN105553724A (zh) * 2015-12-17 2016-05-04 北京奇虎科技有限公司 处理数据请求及获取服务器信息的方法及装置
CN112950381A (zh) * 2016-01-24 2021-06-11 杭州复杂美科技有限公司 区块链撮合交易所
CN106327191B (zh) * 2016-08-09 2020-06-19 联动优势科技有限公司 一种交易信息记录的方法与装置
CN106372868B (zh) * 2016-09-06 2020-02-18 联动优势科技有限公司 一种对写入区块链的交易数据的验证方法和装置
CN106383754A (zh) * 2016-09-19 2017-02-08 北京众享比特科技有限公司 一种基于区块链技术的数据库备份、恢复方法和系统
CN106452785B (zh) * 2016-09-29 2019-05-17 财付通支付科技有限公司 区块链网络、分支节点及区块链网络应用方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056333A (zh) * 2009-11-05 2011-05-11 中国移动通信集团河南有限公司 Wap网关及其业务处理方法和wap代理服务器
WO2017021155A1 (fr) * 2015-07-31 2017-02-09 British Telecommunications Public Limited Company Fourniture de ressource commandée dans des environnements informatiques distribués
CN105607951A (zh) * 2015-12-17 2016-05-25 北京奇虎科技有限公司 处理数据请求及获取服务器信息的方法及装置
KR101701131B1 (ko) * 2016-04-28 2017-02-13 주식회사 라피 이종간 블록체인 연결을 이용한 데이터 기록/검증 방법 및 시스템
CN106899680A (zh) * 2017-03-09 2017-06-27 上海亿账通区块链科技有限公司 多区块链的分片处理方法和装置

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3496370A4 (fr) * 2017-09-30 2020-02-19 One Connect Smart Technology Co., Ltd. (Shenzhen) Procédé de chargement amont de données de chaîne de blocs, système, système informatique, et support de stockage
CN111489256A (zh) * 2019-01-25 2020-08-04 京东数字科技控股有限公司 用于多链区块链系统中的跨链处理方法、设备及系统
CN110147942A (zh) * 2019-04-29 2019-08-20 阿里巴巴集团控股有限公司 一种基于区块链的业务配置方法、装置以及电子设备
CN110428329A (zh) * 2019-07-01 2019-11-08 扬州腾邮大数据网络科技有限公司 一种多区块链的分片处理方法和装置
CN110633323A (zh) * 2019-09-16 2019-12-31 腾讯科技（深圳）有限公司 业务数据存储方法、装置、存储介质和计算机设备
CN110633323B (zh) * 2019-09-16 2023-10-20 腾讯科技（深圳）有限公司 业务数据存储方法、装置、存储介质和计算机设备
CN112988738A (zh) * 2019-12-16 2021-06-18 北京百度网讯科技有限公司 用于区块链的数据分片方法和装置
CN112988738B (zh) * 2019-12-16 2024-05-07 北京百度网讯科技有限公司 用于区块链的数据分片方法和装置
CN111275553A (zh) * 2020-01-20 2020-06-12 联动优势(北京)数字科技有限公司 一种区块链的数据存储方法及区块链系统
CN111275553B (zh) * 2020-01-20 2023-08-11 联动优势科技有限公司 一种区块链的数据存储方法及区块链系统
CN111444445A (zh) * 2020-03-25 2020-07-24 平安医疗健康管理股份有限公司 一种数据传输方法、系统、计算机设备和可读存储介质
CN112651044A (zh) * 2020-12-29 2021-04-13 杭州趣链科技有限公司 基于区块链技术的业务交易方法、系统及存储介质
CN112651044B (zh) * 2020-12-29 2024-03-01 杭州趣链科技有限公司 基于区块链技术的业务交易方法、系统及存储介质
CN112769943A (zh) * 2021-01-15 2021-05-07 河北蜂之巢互联网技术有限公司 一种业务处理的方法及装置
CN114741066A (zh) * 2022-06-09 2022-07-12 天聚地合(苏州)科技股份有限公司 区块链应用的生成方法及生成系统
CN117294757A (zh) * 2023-11-27 2023-12-26 山东省计算中心（国家超级计算济南中心） 基于区块链的复杂业务拆分执行方法、系统、设备及介质
CN117294757B (zh) * 2023-11-27 2024-02-20 山东省计算中心（国家超级计算济南中心） 基于区块链的复杂业务拆分执行方法、系统、设备及介质

Also Published As

Publication number Publication date
SG11201907939VA (en) 2019-09-27
CN106899680A (zh) 2017-06-27
CN106899680B (zh) 2019-07-30

Similar Documents

Publication Publication Date Title
WO2018161478A1 (fr) Support d'informations, serveur, dispositif et procédé de traitement de fragmentation destiné à être utilisé avec des chaînes multi-blocs
WO2018161479A1 (fr) Système et procédé de traitement de grappe de chaînes de blocs, dispositif informatique et support de stockage
WO2018014582A1 (fr) Procédé de traitement de données de police d'assurance, dispositif, administrateur et support de stockage
US11500670B2 (en) Computing service with configurable virtualization control levels and accelerated launches
US11438255B2 (en) Automated route propagation among networks attached to scalable virtual traffic hubs
CN110865867B (zh) 应用拓扑关系发现的方法、装置和系统
US10797989B2 (en) Scalable virtual traffic hub interconnecting isolated networks
US11218364B2 (en) Network-accessible computing service for micro virtual machines
US8942236B1 (en) Stateless packet segmentation and processing
WO2016190476A1 (fr) Procédé destiné à la gestion de clé de chiffrement pour service en nuage et appareil correspondant
WO2014005501A1 (fr) Procédé et système pour qu'un compte d'utilisateur conserve un état de connexion et un support de stockage
US20130107881A1 (en) Distributed Address Resolution Service for Virtualized Networks
US11928514B2 (en) Systems and methods providing serverless DNS integration
EP3564835A1 (fr) Procédé et appareil de redistribution de données et groupe de bases de données
WO2014069827A1 (fr) Système et procédé pour fournir un service d'analyse de données dans un environnement en nuage
WO2021063028A1 (fr) Procédé et appareil pour fournir un service de réseau pour un service, et dispositif informatique
WO2021143351A1 (fr) Procédé, appareil et système de récupération distribuée, dispositif informatique et support de stockage
US9043638B1 (en) Method for enhancing memory fault tolerance
WO2018036168A1 (fr) Procédé et dispositif d'exécution de tâche de traitement de données, serveur d'exécution et support de stockage
WO2018233372A1 (fr) Procédé, dispositif et appareil de programmation de lvs prenant en charge une politique de programmation de hachage, et support de stockage
WO2019153880A1 (fr) Procédé de téléchargement de fichier miroir dans un groupe, nœud et serveur d'interrogation
WO2013176431A1 (fr) Système et procédé pour allouer un serveur à un serveur et pour une messagerie efficace
EP3853708B1 (fr) Service extensible de traitement de paquets à base de cellules utilisant des métadonnées de décision fournies par le client
EP3970006A1 (fr) Procédé et appareil de gestion d'application
WO2016127315A1 (fr) Procédé et appareil de partage de ressource pour un système en nuage privé

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: 17900210

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13/01/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17900210

Country of ref document: EP

Kind code of ref document: A1