WO2020140649A1 - 区块链智能合约管理方法与装置、电子设备、存储介质 - Google Patents

区块链智能合约管理方法与装置、电子设备、存储介质 Download PDF

Info

Publication number
WO2020140649A1
WO2020140649A1 PCT/CN2019/120958 CN2019120958W WO2020140649A1 WO 2020140649 A1 WO2020140649 A1 WO 2020140649A1 CN 2019120958 W CN2019120958 W CN 2019120958W WO 2020140649 A1 WO2020140649 A1 WO 2020140649A1
Authority
WO
WIPO (PCT)
Prior art keywords
smart contract
computing resource
resource configuration
blockchain node
request
Prior art date
Application number
PCT/CN2019/120958
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 WO2020140649A1 publication Critical patent/WO2020140649A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Definitions

  • the present disclosure relates to the technical field of blockchain and smart contracts, and in particular to a blockchain smart contract management method and blockchain smart contract management device, electronic equipment, and computer-readable storage media.
  • Blockchain is an Internet database technology. Its essence is that multiple blockchain nodes participate together. Through multi-party storage and calculation, the data cannot be tampered with and the results are open and reliable. Distributed ledger technology. The development of blockchain makes smart contracts possible. Its essence is to publish a piece of computer code with the rights and obligations of a smart terminal device in accordance with the signed contract on the blockchain, without intermediary participation in the blockchain. Automatic execution on the Internet not only improves the execution efficiency of smart contracts, but also ensures that the contract terms cannot be tampered with.
  • the purpose of the present disclosure is to provide a blockchain smart contract management method, a blockchain smart contract management device, an electronic device, and a computer-readable storage medium, so as to overcome, at least to a certain extent, the response time due to the limitations of related technologies Changhe and data processing requirements are large.
  • a blockchain smart contract management method comprising: receiving a smart contract conclusion request, and acquiring a business type corresponding to the smart contract in the smart contract conclusion request; according to the The business type establishes computing resource configuration conditions, and obtains the computing resource configuration information corresponding to the computing resource configuration conditions in the current blockchain node; determines whether the computing resource configuration information meets the computing resource configuration conditions; if the If the computing resource configuration information meets the computing resource configuration conditions, the smart contract is concluded and saved at the current blockchain node; if the computing resource configuration information does not satisfy the computing resource configuration conditions, the smart The contract conclusion request is sent to the big data processing system, and the smart contract is concluded and saved by the big data processing system.
  • a blockchain smart contract management device comprising: a request receiving module configured to receive a smart contract conclusion request and obtain a business type in the smart contract conclusion request; conditions The establishment module is configured to establish computing resource configuration conditions according to the business type; the information judgment module is configured to obtain computing resource configuration information corresponding to the computing resource configuration conditions in the current blockchain node and judge the Whether the computing resource configuration information meets the corresponding computing resource configuration condition; the first conclusion module is configured to: if the computing resource configuration information of the current blockchain node meets the corresponding computing resource configuration condition, then The current blockchain node concludes and saves a smart contract; the second conclusion module is configured to, if the computing resource configuration information of the current blockchain node does not satisfy the corresponding computing resource configuration conditions, The smart contract conclusion request is sent to the big data processing system, and the big data processing system signs and saves the smart contract.
  • a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements the blockchain smart contract management method in any of the above exemplary embodiments.
  • the computer-readable storage medium may be a computer non-volatile storage medium.
  • an electronic device including: a processor and a memory; wherein the computer stores computer-readable instructions stored on the memory, the computer-readable instructions being executed by the processor to implement any of the above exemplary implementations Examples of blockchain smart contract management methods.
  • the classification processing method of the present disclosure is beneficial to integrating computing resources and improving the business processing speed and efficiency of the blockchain.
  • FIG. 1 schematically shows a flowchart of a method for blockchain smart contract management in an exemplary embodiment of the present disclosure
  • FIG. 2 schematically shows a partial flow chart of a method for blockchain smart contract management in an embodiment of the present disclosure
  • FIG. 3 schematically shows a partial flow chart of a method for blockchain smart contract management in an embodiment of the present disclosure
  • FIG. 4 schematically shows a partial flow chart of a method for blockchain smart contract management in an embodiment of the present disclosure
  • FIG. 5 schematically shows a partial flow chart of a method for blockchain smart contract management in an embodiment of the present disclosure
  • FIG. 6 schematically shows a structural schematic diagram of a blockchain smart contract management device in an exemplary embodiment of the present disclosure
  • FIG. 7 schematically shows an electronic device for a blockchain smart contract management method in an exemplary embodiment of the present disclosure
  • FIG. 8 schematically shows a computer-readable storage medium for a blockchain smart contract management method in an exemplary embodiment of the present disclosure.
  • a blockchain smart contract management method is provided, which is applied to a smart terminal device that has a certain storage space, can be connected to a network, and participates in a blockchain.
  • the smart terminal device may be a variety of electronic terminal devices such as mobile phones, tablet computers, notebook computers, PDAs, and mining machines that have a certain storage space, can be connected to the network, and participate in the blockchain.
  • the blockchain smart contract management method may mainly include the following steps:
  • Step S101 Receive a smart contract conclusion request and obtain a service type corresponding to the smart contract in the smart contract conclusion request.
  • a smart contract conclusion request may be sent, and the request may include one or more business types associated with the smart contract. Determining the business type is to determine the business after obtaining the business data, and then determine the business type corresponding to the business data. For example, the business types are divided according to business functions, which can be divided into bookkeeping types, statistical analysis types, logical calculation types, query types, payment types, etc.
  • the bookkeeping type is the business type corresponding to the business data generated by the business and the bookkeeping;
  • the statistical analysis type is to count and analyze the complex business data and the business type corresponding to the business data;
  • the logical calculation type is to perform complex business
  • the query type is the business type corresponding to the business data including simple accounting query, logical calculation result or statistical analysis query;
  • the payment type is the business type corresponding to the business data including payment information.
  • business types can be divided according to business content, which can be divided into card issuing types, transaction types, and so on.
  • the card issuance type is the business type corresponding to the business data containing the card issuance information;
  • the transaction type is the business type corresponding to the business data containing the transaction information. There are no specific restrictions on the division of business types.
  • the service type may be determined by clustering or other methods to determine a service type with a larger coverage as the service type corresponding to the obtained service data.
  • the business types corresponding to the acquired business data include both the bookkeeping type and the payment type. According to the business content, these business data are all transaction types, and then the business type corresponding to these business data is determined to be the transaction type.
  • Step S102 Establish computing resource configuration conditions according to the type of business, and obtain computing resource configuration information corresponding to the computing resource configuration conditions in the current blockchain node.
  • the business type associated with the smart contract can be obtained through step S101.
  • different corresponding computing resource configuration conditions can be established for the associated business type.
  • Computing resources refer to resources used for computing, including CPU performance resources, memory resources, and hard disk resources.
  • Computing resource configuration conditions are conditions for arranging the use of computing resources to meet the different needs of various business types, and the conditions are different standards for computing resources set for each business type.
  • the computing resource configuration information of each blockchain node is the numerical parameter information and non-numeric parameter information of the central processor performance resources, memory resources, and hard disk resources corresponding to the blockchain node.
  • the non-numeric parameter information in the computing resource configuration information of each blockchain node should be set when the blockchain node is generated, and may only change when the terminal device changes; and the numeric parameter information It has been determined when the blockchain node was generated and will not change.
  • obtaining its computing resource configuration information can be used as the computing resource configuration information corresponding to the computing resource configuration conditions of the current blockchain node.
  • Step S103 Determine whether the computing resource configuration information satisfies the computing resource configuration conditions.
  • step S102 the computing resource configuration information of the current blockchain node has been obtained, and whether the computing resource configuration information of these blockchain nodes conforms to the node set of the blockchain node, and which node set meets the need to use computing resource configuration conditions judgment.
  • Corresponding computing resource configuration conditions have been established according to the business type, so it is necessary to compare the computing resource configuration information of the blockchain nodes with the computing resource configuration conditions of each business type, and then judge.
  • Step S104 If the computing resource configuration information meets the computing resource configuration conditions, the smart contract is concluded and saved at the current blockchain node.
  • this step lists scenarios when it is determined that the computing resource configuration information of the current blockchain node meets the computing resource configuration conditions.
  • the computing resource allocation condition of a business type is that the type of the central processor is Intel, then if the type of the central processor of the blockchain node is a series of Intel, whether it is a Celeron series, Pentium series, Core series or Atom series, etc. , All can conclude and save smart contracts at the current blockchain node according to the computing resource configuration conditions.
  • the computing resource configuration information corresponding to the computing resource configuration conditions of a business type is not only this one, but other computing resource configuration information can also be used to continue the judgment until a smart contract required by a business type is concluded.
  • Step S105 If the computing resource configuration information does not satisfy the computing resource configuration conditions, the smart contract conclusion request is sent to the big data processing system, and the big data processing system concludes and saves the smart contract.
  • the computing resource configuration information of the current blockchain node is determined.
  • This step lists scenarios when it is determined that the computing resource configuration information of the current blockchain node does not satisfy the computing resource configuration conditions.
  • the computing resource configuration condition of a business type is that the type of central processor is Celeron series in Intel, then if the type of the central processor of the current blockchain node is other than the series of Celeron series, the computing resource can be determined If the configuration information does not satisfy the computing resource allocation conditions, the smart contract conclusion request of the current blockchain node is sent to the big data processing system, and the big data processing system concludes and saves the smart contract.
  • the big data processing system is a computer with strong storage and computing capabilities, which can be a central server capable of data communication with various nodes.
  • the external big data processing system is responsible for logical calculation or statistical analysis of new bookkeeping transactions, and records the processing results inside the big data processing system; the external big data processing system can also write the calculation results back to the chain where the smart contract is located In this case, all query transactions are queried by the smart contract and the result is returned.
  • the current blockchain node that does not satisfy the computing resource configuration conditions of one business type should continue to judge the computing resource configuration conditions of other business types.
  • This condition can be used to measure the computing power of blockchain nodes. If the computing power of blockchain nodes meets the conditions, then the blockchain nodes can directly sign and manage smart contracts ; And if the computing power of the blockchain nodes does not meet the conditions, the big data processing system can be used to conclude and manage smart contracts.
  • This classification processing method is conducive to integrating computing resources and improving the business processing speed and efficiency of the blockchain.
  • the establishment of computing resource configuration conditions according to the service type in step S102 includes the following steps:
  • Step S201 One or more computing resource configuration parameters are preset.
  • the computing resource configuration conditions corresponding to each service type may be setting conditions for one or more computing resource configuration parameters.
  • the computing resource configuration parameters may be related parameters of the CPU's performance resources, memory resources, and hard disk resources. Presetting one or more computing resource configuration parameters means presetting the relevant parameters of the central processor performance resources, memory resources, and hard disk resources.
  • Step S202 Select at least one computing resource configuration parameter according to the service type, and establish computing resource configuration conditions for the selected computing resource configuration parameter.
  • the computing resource configuration parameters have been preset in step S201. Further, computing resource configuration conditions need to be established. Computing resource configuration conditions set different standards for computing resources for each business type. Specifically, the computing resource configuration condition is to select and preset computing resource configuration parameters. Therefore, different computing resource configuration conditions are established for different business types, that is, corresponding computing resource configuration parameters are set. According to different business types, different computing resource configuration parameters can be selected, then these related computing resource configurations.
  • the parameter is the computing resource configuration condition corresponding to the business type. Among them, the number of computing resource configuration parameters selected in the computing resource configuration conditions corresponding to different service types varies, and should include at least one.
  • corresponding computing resource configuration parameters are established as computing resource configuration conditions for different business types, which not only can match the three well, which is convenient for setting and viewing, but also preset different computing resource configuration conditions Different computing resource configuration parameters avoid the unsuitability of uniform setting, and are more targeted and accurate.
  • the computing resource configuration parameters in the blockchain smart contract management method include numerical parameters and/or non-numeric parameters; where the numerical parameters include the central processor's main frequency, memory capacity, and hard disk capacity And/or network bandwidth; non-numeric parameters include CPU type, memory type, and/or hard disk type.
  • the central processor's main frequency is an aspect of the performance of the central processor, indicating the speed of the central processor's operations and processing data;
  • the memory capacity is the amount of data that temporarily stores the data processed while the machine is running, and the size depends on the memory bar The amount of data, so it is not the greater the better;
  • the hard disk capacity is the amount of data that the hard disk can store permanently, the size depends on its own;
  • the network bandwidth is the largest bit of data that can be passed in a fixed time, which is a measure of network usage An important indicator. It can be seen that the numerical parameters can all use data to indicate their relative usage, so data operations can be performed to determine whether they meet the computing resource configuration conditions.
  • CPUs there are two main types of CPUs: Intel and AMD. Different types of CPUs have different data processing capabilities; memory types include SDRAM, DDR, SDRAM, and RDRAM. Different types of memory transfer types are different; hard disk types There are mainly four kinds of IDE, SATA, SCSI and Fibre Channel. Different hard disk interfaces have different connection speeds between the hard disk and the computer, which affects the program running speed and system performance. It can be known that the non-numerical parameters are determined by the blockchain nodes themselves.
  • the computing resource configuration parameters in the computing resource configuration conditions of the business type are set and explained, so that the computing resource configuration conditions involve more detailed parameters, which is convenient for setting and understanding, and can also make many different
  • the service type selects the computing resource configuration parameters more targeted, more diverse, more adaptable, and less prone to wrong correspondence.
  • the blockchain smart contract management method further includes the following steps:
  • Step S301 Receive a smart contract call request, and determine whether the smart contract to be called is saved on the current blockchain node or big data processing system according to the smart contract call request.
  • the smart contract invocation request can be generated and sent through the trigger script of the business layer, which is a global LAN type business layer.
  • the blockchain parses the smart contract call request, thereby judging whether the smart contract to be called is saved on the current blockchain node or big data processing system.
  • the smart contract call request carries the name of the smart contract to be called, the calling port, the business type and the transaction parameters.
  • the name of the target smart contract to be called refers to the smart to be called Contract
  • the smart contract to be called is one of the smart contracts that have been concluded and saved.
  • this step lists the situation when it is determined that the smart contract to be called is saved on the current blockchain node.
  • the smart contract to be invoked is successfully invoked and executed by the current blockchain node that holds the smart contract to be invoked.
  • Business processing will be performed according to the smart contract invocation request to generate business data and execution results, and the execution result of the smart contract to be invoked Return to the sender of the smart contract call request.
  • Step S303 If it is determined that the smart contract to be called is saved on the big data processing system, the big data processing system executes the smart contract and returns the execution result of the smart contract to the sender of the smart contract call request through the current blockchain node .
  • this step lists the situation when it is determined that the smart contract to be called is stored on the big data processing system.
  • the smart contract to be invoked is successfully invoked and executed by the big data system that holds the smart contract to be invoked.
  • Business processing is performed according to the smart contract invocation request to generate business data and execution results, and the execution result of the smart contract to be invoked is passed through the current
  • the blockchain node returns to the sender of the smart contract call request.
  • the smart contract call request is used to determine the storage location of the smart contract to be called, and the target smart contract is executed accordingly to obtain and return the execution result.
  • the smart contract in the blockchain it is not necessary to know the address and the address of the smart contract.
  • Interface description information you only need to know the associated storage information of the smart contract, you can successfully call and execute the smart contract in different storage, not only simplifies the calling process of calling smart contracts in the blockchain, but also reduces the calling of smart contracts Difficulty, avoiding the occurrence of smart contract call errors caused by incorrect interface descriptions, and ensuring the accuracy of smart contract execution and the reliability of results.
  • receiving the smart contract call request in step S301 includes the following steps:
  • Step S401 Obtain the utilization rates of multiple computing resources of the current blockchain node.
  • Computing resource usage refers to the usage of computing resources, including CPU performance resources, memory resources, and hard disk resources, such as CPU usage, memory usage, hard disk usage, and/or network usage. Since the usage of computing resources is constantly changing with the operation and operation of the current blockchain node, the instantaneous value of multiple computing resources at a certain moment should be obtained as the current moment of the current blockchain node Utilization of multiple computing resources.
  • Step S402. Perform an operation on the calculation resource usage rate, and obtain an operation result as a calculation resource score.
  • a plurality of computing resource usage rates of the current blockchain node can be obtained.
  • a corresponding operation can be performed on the obtained computing resource usage rates.
  • the computing resource usage rate needs to be calculated. For example, different computing resource usage rates may be assigned unequal weights according to their proportions, and weighted and summed. The obtained calculation result is used as the computing resource score.
  • the weight of the allocation of each computing resource usage rate can be obtained by the inventor according to a large number of statistical experiments or the computing power requirements of each blockchain node.
  • step S402 a plurality of computing resource usage rates are calculated and a computing resource score is obtained.
  • a result judgment is performed on the computing resource score.
  • a preset threshold can be set. If the computing resource score of the current blockchain node is less than the preset threshold, it indicates that the computing power of the current blockchain node may not meet the needs of the smart contract to be called, so the received smart contract call request can be transmitted to the next The blockchain node continues to judge until it finds a blockchain node that can meet the needs of the smart contract to be called.
  • the computing resource score obtained by computing multiple computing resource utilization ratios can be judged.
  • the normal call and execution of the smart contracts concluded and saved are guaranteed, and the results of the utilization rate of the computing resources of each blockchain can be obtained, and the computing power of each blockchain node can be mastered.
  • the method for managing a smart contract on a blockchain also includes sending an early warning message if the computing resource score of the current blockchain node is less than a preset threshold.
  • a warning message should also be sent to the user associated with the current blockchain node.
  • the early warning information may include the utilization rate of the computing resources of the current blockchain node and its grade and type.
  • the content contained in the early warning information can be sent to the user to facilitate the corresponding user on the blockchain node to grasp the situation of calculating the resource score and adjust the corresponding resource.
  • returning the execution result of the smart contract to the sender of the smart contract call request through the current blockchain node in step S303 includes the following steps:
  • Step S501 Save the execution result of the smart contract on the current blockchain node.
  • the smart contract to be called When the smart contract to be called is executed, it can perform business processing according to its business type to generate relevant business data and execution results.
  • the execution process is completed by the big data processing system, so it cannot be directly returned to the sending of the smart contract call request
  • the party can save the execution result on the current blockchain node first.
  • Step S502 Return the execution result of the smart contract saved on the current blockchain node to the sender of the smart contract call request.
  • step S501 the execution result of the smart contract has been saved on the current blockchain node, and this step can return the execution result to the sender of the smart contract call request.
  • the execution result can be obtained by the central processor and fed back.
  • This embodiment describes how to return the execution result of the smart contract when the smart contract is executed by the big data processing system, which not only enables the sender of the smart contract call request to grasp the execution result of the smart contract, but also saves the location of the smart contract Different ways of returning have been improved.
  • the blockchain smart contract management device 600 may include: a request receiving module 601, a condition establishment module 602, an information judgment module 603, a first conclusion module 604, and a second conclusion module 605. among them:
  • the request receiving module 601 is configured to receive a smart contract conclusion request and obtain the business type in the smart contract conclusion request;
  • the condition establishment module 602 is configured to establish a computing resource configuration condition according to the business type;
  • the information judgment module 603 Configured to obtain computing resource configuration information corresponding to the computing resource configuration conditions in the current blockchain node, and determine whether the computing resource configuration information meets the corresponding computing resource configuration conditions;
  • the first conclusion module 604 Configured to enter and save a smart contract at the current blockchain node if the computing resource configuration information of the current blockchain node meets the corresponding computing resource configuration condition;
  • the second conclusion module 605, Is configured to send the smart contract conclusion request to the big data processing system if the computing resource configuration information of the current blockchain node does not satisfy the corresponding computing resource configuration condition, and the big data processing system concludes And save the smart contract.
  • modules or units of the blockchain smart contract management device 600 are mentioned in the above detailed description, this division is not mandatory.
  • the features and functions of the two or more modules or units described above may be embodied in one module or unit.
  • the features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.
  • an electronic device capable of implementing the above method is also provided.
  • the electronic device 700 according to this embodiment of the present application is described below with reference to FIG. 7.
  • the electronic device 700 shown in FIG. 7 is only an example, and should not bring any limitation to the functions and usage scope of the embodiments of the present application.
  • the electronic device 700 is represented in the form of a general-purpose computing device.
  • Components of the electronic device 700 may include, but are not limited to: the at least one processing unit 710, the at least one storage unit 720, a bus 730 connecting different system components (including the storage unit 720 and the processing unit 710), and a display unit 740.
  • the storage unit stores a program code
  • the program code may be executed by the processing unit 710, so that the processing unit 710 executes various exemplary according to the present application described in the “exemplary method” section of the above description of this specification Example steps.
  • the storage unit 720 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 7201 and/or a cache storage unit 7202, and may further include a read-only storage unit (ROM) 7203.
  • RAM random access storage unit
  • ROM read-only storage unit
  • the storage unit 720 may further include a program/utility tool 7204 having a set of (at least one) program modules 7205.
  • program modules 7205 include but are not limited to: an operating system, one or more application programs, other program modules, and program data. Each of these examples or some combination may include an implementation of the network environment.
  • the bus 730 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any of a variety of bus structures bus.
  • the electronic device 700 may also communicate with one or more external devices 900 (eg, keyboard, pointing device, Bluetooth device, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 700, and/or This enables the electronic device 700 to communicate with any device (eg, router, modem, etc.) that communicates with one or more other computing devices. Such communication may be performed through an input/output (I/O) interface 750.
  • the electronic device 700 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through a network adapter 760.
  • networks such as a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet
  • the network adapter 740 communicates with other modules of the electronic device 700 through the bus 730. It should be understood that although not shown in the figure, other hardware and/or software modules may be used in conjunction with the electronic device 700, including but not limited to: microcode, device driver, redundant processing unit, external disk drive array, RAID system, tape drive And data backup storage system.
  • the example embodiments described here can be implemented by software, or can be implemented by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, U disk, mobile hard disk, etc.) or on a network , Including several instructions to enable a computing device (which may be a personal computer, server, terminal device, or network device, etc.) to execute the method according to an embodiment of the present disclosure.
  • a computing device which may be a personal computer, server, terminal device, or network device, etc.
  • a computer-readable storage medium on which a program product capable of implementing the above method of this specification is stored.
  • various aspects of the present application may also be implemented in the form of a program product, which includes program code, and when the program product runs on a terminal device, the program code is used to enable the The terminal device executes the steps according to various exemplary embodiments of the present application described in the "Exemplary Method" section of this specification.
  • a program product 800 for implementing the above method according to an embodiment of the present application may use a portable compact disk read-only memory (CD-ROM) and include a program code, and may be included in a terminal device. For example running on a personal computer.
  • the program product of the present application is not limited to this.
  • the readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, apparatus, or device.
  • the program product may employ any combination of one or more readable media.
  • the readable medium may be a readable signal medium or a readable storage medium.
  • the readable storage medium may be, for example but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of readable storage media (non-exhaustive list) include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
  • the computer-readable signal medium may include a data signal that is transmitted in baseband or as part of a carrier wave, in which readable program code is carried. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device.
  • the program code contained on the readable medium may be transmitted on any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • the program code for performing the operations of the present application can be written in any combination of one or more programming languages, which includes object-oriented programming languages such as Java, C++, etc., and also includes the conventional procedural formula Programming language-such as "C" language or similar programming language.
  • the program code may be executed entirely on the user computing device, partly on the user device, as an independent software package, partly on the user computing device and partly on the remote computing device, or entirely on the remote computing device or server To execute.
  • the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (for example, using Internet service provision Business to connect via the Internet).
  • LAN local area network
  • WAN wide area network
  • Internet service provision Business for example, using Internet service provision Business to connect via the Internet.

Abstract

本公开属于区块链与智能合约技术领域，涉及一种区块链智能合约管理方法及装置、电子设备、计算机可读存储介质。该方法包括：接收智能合约订立请求，并获取其中与智能合约相对应的业务类型；根据业务类型建立计算资源配置条件，并获取当前区块链节点中与其相对应的计算资源配置信息；判断计算资源配置信息是否满足计算资源配置条件；若满足计算资源配置条件，则在当前区块链节点订立并保存智能合约；若不满足计算资源配置条件，则将智能合约订立请求发送至大数据处理系统，并由大数据处理系统订立并保存智能合约。本公开不仅可以衡量出区块链节点的计算能力，并且这种分类处理的方式有利于整合计算资源，提高区块链的业务处理速度和效率。

Description

区块链智能合约管理方法与装置、电子设备、存储介质
本申请要求于2019年01月03日提交中国专利局、申请号为201910003252.2、申请名称为“区块链智能合约管理方法与装置、电子设备、存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及区块链与智能合约技术领域，尤其涉及一种区块链智能合约管理方法与区块链智能合约管理装置、电子设备及计算机可读存储介质。
背景技术
区块链是一种互联网数据库技术，其本质是由多个区块链节点共同参与，通过多方存储与计算的方式来实现数据不可篡改、结果公开可靠的分布式账本技术。区块链的发展使得智能合约成为可能，其本质是将一段具有一台智能终端设备按照所签署的合约的权利和义务的计算机代码发布到区块链上，无需中介的参与即在区块链上自动执行，不仅提高了智能合约的执行效率，而且保证了合约条款的不可篡改。
对于大多数简单的业务处理过程，区块链节点上的智能合约都可以快速得到响应。区块链单一节点的处理能力决定了智能合约不能过于复杂。当业务逻辑过于复杂时，将导致智能合约运行时间变长，进而导致区块链响应时间变长，与中心化系统相比变得越来越没有优势。而且，随着账本数据的不断增加，也存在着智能合约对账本数据进行统计分析或大数据处理的需求，这对区块链节点的处理能力提出了较高的要求。
需要说明的是，在上述背景技术部分公开的信息仅用于加强对本公开的背景的理解，因此可以包括不构成对本领域普通技术人员已知的现有技术的信息。
发明内容
本公开的目的在于提供一种区块链智能合约管理方法与区块链智能合约管理装置、电子设备及计算机可读存储介质，进而至少在一定程度上克服由于相关技术的限制而导致的响应时间长和数据处理需求大等问题。
根据本公开的一个方面，提供一种区块链智能合约管理方法，所述方法包括：接收智能合约订立请求，并获取所述智能合约订立请求中与智能合约相对应的业务类型；根据所述业务类型建立计算资源配置条件，并获取当前区块链节点中与所述计算资源配置条件相对应的计算资源配置信息；判断所述计算资源配置信息是否满足所述计算资源配置条件；若所述计算资源配置信息满足所述计算资源配置条件，则在所述当前区块链节点订立并保存所述智能合约；若所述计算资源配置信息不满足所述计算资源配置条件，则将所述智能合约订立请求发送至大数据处理系统，并由所述大数据处理系统订立并保存所述智能合约。
根据本公开的一个方面，提供一种区块链智能合约管理装置，所述装置包括：请求接收模块，被配置为接收智能合约订立请求，并获取所述智能合约订立请求中的业务类型；条件建立模块，被配置为根据所述业务类型建立计算资源配置条件；信息判断模块，被配置为获取当前区块链节点中与所述计算资源配置条件相对应的计算资源配置信息，并判断所述计算资源配置信息是否满足对应的所述计算资源配置条件；第一订立模块，被配置为若所述当前区块链节点的所述计算资源配置信息满足所述对应的计算资源配置条件，则在所述当前区块链节点订立并保存智能合约；第二订立模块，被配置为若所述当前区块链节点的所述计算资源配置信息不满足所述对应的计算资源配置条件，则将所述智能合约订立请求发送至大数据处理系统，由大数据处理系统订立并保存智能合约。
根据本公开的一个方面，提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述任意示例性实施例中的区块链智能合约管理方法。可选的，该计算机可读存储介质可以为计算机非易失性可读存储介质。
根据本公开的一个方面，提供一种电子设备，包括：处理器和存储器；其中，存储器上存储有计算机可读指令，所述计算机可读指令被所述处理器执行时实现上述任意示例性实施例的区块链智能合约管理方法。
本公开的分类处理的方式有利于整合计算资源，提高区块链的业务处理速度和效率。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1示意性示出本公开示例性实施例中一种区块链智能合约管理方法的流程图；
图2示意性示出本公开实施例中一种区块链智能合约管理方法的部分步骤流程图；
图3示意性示出本公开实施例中一种区块链智能合约管理方法的部分步骤流程图；
图4示意性示出本公开实施例中一种区块链智能合约管理方法的部分步骤流程图；
图5示意性示出本公开实施例中一种区块链智能合约管理方法的部分步骤流程图；
图6示意性示出本公开示例性实施例中一种区块链智能合约管理装置的结构示意图；
图7示意性示出本公开示例性实施例中一种用于区块链智能合约管理方法的电子设备；
图8示意性示出本公开示例性实施例中一种用于区块链智能合约管理方法的计算机可读存储介质。
具体实施方式
现在将参考附图更全面地描述示例性实施方式。
图中相同的附图标记表示相同或类似的部分，因而将省略对它们的重复描述。附图中所示的一些方框图是功能实体，不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
在本公开(本申请)的示例性实施例中，首先提供了一种区块链智能合约 管理方法，应用于具有一定存储空间、可连接网络和参与区块链的智能终端设备。具体而言，该智能终端设备可以是手机、平板电脑、笔记本电脑、PDA、矿机等各种具有一定存储空间、可连接网络和参与区块链的电子终端设备。
参考图1中所示，该区块链智能合约管理方法主要可以包括以下步骤：
步骤S101.接收智能合约订立请求，并获取智能合约订立请求中与智能合约相对应的业务类型。
当需要订立智能合约时，可以发送一智能合约订立请求，该请求中可以包含一种或者多种与智能合约相关联的业务类型。确定业务类型是通过获取到业务数据后，确定其业务，进而确定业务数据对应的业务类型。例如，将业务类型按照业务功能进行划分，可以分为记账类型、统计分析类型、逻辑计算类型、查询类型、支付类型等。其中，记账类型是业务生成并进行记账产生的业务数据对应的业务类型；统计分析类型是将复杂的业务数据进行统计并分析该业务数据对应的业务类型；逻辑计算类型是对复杂业务进行逻辑处理产生的业务数据对应的业务类型；查询类型是包含简单记账查询、逻辑计算结果或者统计分析查询业务数据对应的业务类型；支付类型是包含支付信息的业务数据对应的业务类型。又比如，在银行行业，可以将业务类型按照业务内容进行划分，可以分为发卡类型、交易类型等。其中，发卡类型是包含发卡信息的业务数据对应的业务类型；交易类型是包含交易信息的业务数据对应的业务类型。这里对于业务类型的划分原则不做具体限制。
在获取到业务数据之后，确定智能合约订立请求中的业务类型时，可能会出现业务类型交叉的情形。此时，确定业务类型可采用聚类或者其他方式确定一个覆盖范围较大的业务类型作为获取到的业务数据对应的业务类型。例如，获取到的业务数据对应的业务类型既有记账类型又有支付类型，根据业务内容来说，这些业务数据均属于交易类型，那么确定这些业务数据对应的业务类型为交易类型。
步骤S102.根据业务类型建立计算资源配置条件，并获取当前区块链节点中与计算资源配置条件相对应的计算资源配置信息。
通过步骤S101可以获取到与智能合约相关联的业务类型，本步骤可以对相关联的业务类型建立不同的相对应的计算资源配置条件。计算资源是指用于 计算的资源，包括中央处理器性能资源、内存资源和硬盘资源等。计算资源配置条件是为满足各个业务类型的不同需求对计算资源的使用作出安排的条件，该条件是针对各业务类型定出的计算资源的不同标准。针对不同的业务类型建立不同的计算资源配置条件，就可以根据业务类型得出相关的计算资源配置条件，那么这些相关的计算资源配置条件即为该业务类型相对应的计算资源配置条件。
每个区块链节点的计算资源配置信息是该区块链节点对应的中央处理器性能资源、内存资源和硬盘资源的各数值型参数信息和非数值型参数信息。各区块链节点的计算资源配置信息中的非数值型参数信息应该是在区块链节点生成的时候已经设定好的，当终端设备发生变化时，可能才会发生变化；而数值型参数信息在该区块链节点生成时已经确定，不会变化。针对某一区块链节点，获取其计算资源配置信息可以作为当前区块链节点的计算资源配置条件相对应的计算资源配置信息。
步骤S103.判断计算资源配置信息是否满足计算资源配置条件。
根据步骤S102已经获取到当前区块链节点的计算资源配置信息，而这些区块链节点的计算资源配置信息是否符合区块链节点的节点集合，符合哪一节点集合需要用计算资源配置条件进行判断。根据业务类型已经建立相对应的计算资源配置条件，所以需要将区块链节点的计算资源配置信息分别与每一业务类型的计算资源配置条件进行比较，进而判断。
步骤S104.若计算资源配置信息满足计算资源配置条件，则在当前区块链节点订立并保存所述智能合约。
根据步骤S103对当前区块链节点的计算资源配置信息进行判断，本步骤列出当判定当前区块链节点的计算资源配置信息满足计算资源配置条件时的情景。例如，一业务类型的计算资源配置条件是中央处理器类型为Intel，那么若区块链节点的中央处理器的类型不论是赛扬系列、奔腾系列、酷睿系列或者凌动系列等属于Intel的系列，都可以根据该计算资源配置条件在当前区块链节点订立并保存智能合约。当然，一业务类型的计算资源配置条件相对应的计算资源配置信息并不仅仅只有这一种，还可以用其他的计算资源配置信息继续判断，直至订立一业务类型所需要的智能合约。
步骤S105.若计算资源配置信息不满足计算资源配置条件，则将智能合约订立请求发送至大数据处理系统，并由大数据处理系统订立并保存智能合约。
根据步骤S103对当前区块链节点的计算资源配置信息进行判断，本步骤列出当判定当前区块链节点的计算资源配置信息不满足计算资源配置条件时的情景。例如，一业务类型的计算资源配置条件是中央处理器类型为Intel中的赛扬系列，那么若当前区块链节点的中央处理器的类型是除赛扬系列的其他系列，可以判断该计算资源配置信息不满足计算资源配置条件，则将当前区块链节点的智能合约订立请求发送至大数据处理系统，由该大数据处理系统订立并保存智能合约。其中，大数据处理系统就是一个存储和计算能力很强的计算机，可以是一个能够与各个节点进行数据通信的中心服务器。外部大数据处理系统负责对新的记账交易进行逻辑计算或数据统计分析，并将处理结果记录到大数据处理系统内部；外部大数据处理系统也可将计算结果写回到智能合约所在的链中，在这种情况下所有的查询交易全部由智能合约查询并返回结果。并且，对于不满足一业务类型的计算资源配置条件的当前区块链节点应继续针对其他业务类型的计算资源配置条件进行判断。
根据业务类型建立相应的计算资源配置条件，该条件可用于衡量区块链节点的计算能力，如果区块链节点的计算能力满足条件，则可以由区块链节点直接进行智能合约的订立和管理；而如果区块链节点的计算能力不满足条件，则可以由大数据处理系统进行智能合约的订立和管理。这种分类处理的方式有利于整合计算资源，提高区块链的业务处理速度和效率。
在以上实施例的基础上，如图2所示，步骤S102中根据业务类型建立计算资源配置条件，包括以下步骤：
步骤S201.预设一种或者多种计算资源配置参数。
各业务类型相对应的计算资源配置条件可以是对一种或者多种计算资源配置参数的设定条件。其中，计算资源配置参数可以是中央处理器性能资源、内存资源和硬盘资源的相关参数。预设一种或者多种计算资源配置参数即对中央处理器性能资源、内存资源和硬盘资源的相关参数进行预设。
步骤S202.根据业务类型选择至少一种计算资源配置参数，并为选定的计算资源配置参数建立计算资源配置条件。
在步骤S201中已经预设计算资源配置参数，进一步，还需建立计算资源配置条件。计算资源配置条件针对各业务类型制定计算资源的不同标准。具体的，计算资源配置条件是对计算资源配置参数进行选定和预设。因此，针对不同的业务类型建立不同的计算资源配置条件，亦即设定相对应的计算资源配置参数，根据不同的业务类型，可以选定不同的计算资源配置参数，那么这些相关的计算资源配置参数即为该业务类型相对应的计算资源配置条件。其中，不同业务类型对应的计算资源配置条件中选定的计算资源配置参数个数不等，应至少包含一种。
根据本实施例，针对不同的业务类型，建立对应的计算资源配置参数作为计算资源配置条件，不仅可以很好地将三者进行匹配，方便设定和查看，而且不同的计算资源配置条件预设不同的计算资源配置参数，避免了统一设定的不适用性，更具针对性和准确性。
在以上实施例的基础上，区块链智能合约管理方法中的计算资源配置参数包括数值型参数和/或非数值型参数；其中，数值型参数包括中央处理器主频、内存容量、硬盘容量和/或网络带宽；非数值型参数包括中央处理器类型、内存类型和/或硬盘类型。
其中，中央处理器主频是中央处理器性能表现的一个方面，表示中央处理器的运算和处理数据的速度；内存容量是暂时存放机器运行时处理数据的数据量，大小取决于内存条可存储的数据量，所以并不是越大越好；硬盘容量是硬盘可永久存储的数据量，大小取决于其自身；网络带宽是在固定的时间内，能通过的最大位数据，是衡量网络使用情况的一个重要指标。可以看出，数值型参数均可用数据来表示其相关使用情况，所以可以进行数据运算来确定其是否符合计算资源配置条件。
其中，中央处理器主要有Intel和AMD两大类，不同的中央处理器类型对数据的处理能力不同；内存类型主要有SDRAM、DDR SDRAM和RDRAM三种，不同类型的内存传输类型不同；硬盘类型主要有IDE、SATA、SCSI和光纤通道四种，不同的硬盘接口在硬盘与计算机之间的连接速度不同，影响程序运行速度和系统性能。可以知道，非数值型参数是区块链节点自身确定的参数。
根据本实施例，对业务类型的计算资源配置条件中的计算资源配置参数进行设定和说明，使计算资源配置条件涉及到参数更加细化，方便设定和理解，也可使多种不同的业务类型更有针对性地选择计算资源配置参数，更加具有多样性，适配性更高，不容易出现错误对应的情形。
在本公开的另一示例性实施例中，如图3所示，区块链智能合约管理方法，还包括以下步骤：
步骤S301.接收智能合约调用请求，并根据智能合约调用请求判断待调用的智能合约是否保存在当前区块链节点或者大数据处理系统上。
智能合约调用请求可以通过业务层触发脚本生成并发送，该业务层是一全球局域网类型的业务层。当接收到该智能合约调用请求，区块链对该智能合约调用请求进行解析，由此判断待调用的智能合约是否保存在当前区块链节点或者大数据处理系统上。其中，智能合约调用请求中携带有所需调用的智能合约的名称、调用端口、业务类型和交易参数，本实施例中的所需调用的目标智能合约的名字所指代的就是待调用的智能合约，且待调用的智能合约是已订立和保存的智能合约中的一种。
步骤S302.若判定待调用的智能合约保存在当前区块链节点上，则由当前区块链节点执行智能合约，并将智能合约的执行结果返回给智能合约调用请求的发送方。
根据步骤S301对待调用的智能合约的保存处进行判断，本步骤列出当判定待调用的智能合约保存在当前区块链节点上的情景。待调用的智能合约成功调用，由保存待调用的智能合约的当前区块链节点执行，会根据智能合约调用请求进行业务处理，生成业务数据及执行结果，并将待调用的智能合约的执行结果返回给智能合约调用请求的发送方。
步骤S303.若判定待调用的智能合约保存在大数据处理系统上，则由大数据处理系统执行智能合约，并将智能合约的执行结果通过当前区块链节点返回给智能合约调用请求的发送方。
根据步骤S301对待调用的智能合约的保存处进行判断，本步骤列出当判定待调用的智能合约保存在大数据处理系统上的情景。待调用的智能合约成功调用，由保存待调用的智能合约的大数据系统执行，会根据智能合约调用请求 进行业务处理，生成业务数据及执行结果，并将待调用的智能合约的执行结果通过当前区块链节点返回给智能合约调用请求的发送方。
本实施例通过获取智能合约调用请求判断待调用智能合约的保存处，相应执行目标智能合约，得到并返回执行结果，实现了在调用区块链中的智能合约时，无需知道智能合约的地址和接口描述信息，只需知道该智能合约的相关联的保存信息，即可在不同保存处成功调用并执行智能合约，不仅简化了调用区块链中智能合约的调用流程，降低了智能合约的调用难度，避免了由于接口描述错误而导致的智能合约调用错误的情况发生，而且保证了智能合约执行的准确性和结果的可靠性。
在本实施例的基础上，如图4所述，步骤S301中的接收智能合约调用请求，包括以下步骤：
步骤S401.获取当前区块链节点的多个计算资源使用率。
对于当前区块链节点接收到的智能合约调用请求进行解析，可以获取到当前区块链节点中的多个计算资源使用率。计算资源使用率是指对于计算资源，包括中央处理器性能资源、内存资源和硬盘资源等的使用情况，例如中央处理器使用率、内存使用率、硬盘使用率和/或网络使用率。由于计算资源的使用情况是随着当前区块链节点中的运算及运行等的情况不断发生变化的，所以应获得某一时刻的多个计算资源的瞬时值来作为当前区块链节点当前时刻的多个计算资源使用率。
步骤S402.对计算资源使用率进行运算，并得到一运算结果作为计算资源评分。
根据步骤S401可以获取当前区块链节点的多个计算资源使用率，本步骤可以对已获得的计算资源使用率进行相对应的运算。为了对计算资源进行评估，需要对计算资源使用率进行运算，例如，可以对不同的计算资源使用率根据其比重分配不等的权重，并进行加权求和，得到的计算结果作为计算资源评分。其中，各计算资源使用率分配的权重可以是发明人根据大量的统计实验或者是对各区块链节点的运算能力要求得出。
步骤S403.若当前区块链节点的计算资源评分小于预设阈值，则将接收到的智能合约调用请求传送至下一区块链节点。
在步骤S402中对多个计算资源使用率进行运算并得到计算资源评分，本步骤对该计算资源评分进行结果判定。为方便对当前区块链节点的计算资源评分进行评判，可以设置一预设阈值。若当前区块链节点的计算资源评分小于该预设阈值，则表明当前区块链节点的计算能力可能无法满足待调用的智能合约需求，所以可以将接收到的智能合约调用请求传送至下一区块链节点，继续进行评判，直至查找到一可以满足待调用智能合约的需求的区块链节点。
本实施例为使待调用的智能合约找到一满足智能合约调用请求的区块链节点，通过设置一预设阈值，对多个计算资源使用率运算得到的计算资源评分进行评判得到，不仅对已订立和保存的智能合约的正常调用和执行有了保证，而且可以获得各区块链的计算资源使用率结果，对各个区块链节点的计算能力有所掌握。
在以上实施例的基础上，区块链智能合约管理方法，还包括若当前区块链节点的计算资源评分小于预设阈值，则发送一预警信息。
当前区块链节点的资源评分小于设置的预设阈值时，还应向当前区块链节点相关联的用户发送一预警信息。该预警信息可以包括当前区块链节点的计算资源使用率及其等级、类型等。并且，可以将该预警信息所包含的内容发送给用户，方便区块链节点上对应的用户对其计算资源评分的情况进行掌握，并进行对应的资源调整。
在以上实施例的基础上，如图5所示，步骤S303中的将智能合约的执行结果通过当前区块链节点返回给智能合约调用请求的发送方，包括以下步骤：
步骤S501.将智能合约的执行结果保存在当前区块链节点上。
在将待调用的智能合约执行时，可以根据其业务类型，进行业务处理，生成相关的业务数据和执行结果，该执行过程由大数据处理系统完成，因此无法直接返回给智能合约调用请求的发送方，可以先将该执行结果保存在当前区块链节点上。
步骤S502.将当前区块链节点上保存的智能合约的执行结果返回给智能合约调用请求的发送方。
根据步骤S501已经将智能合约的执行结果保存在当前区块链节点上，本步骤可以将该执行结果返回给智能合约调用请求的发送方。该执行结果可以由 中央处理器获取，并进行反馈。
本实施例是对当智能合约由大数据处理系统执行时，将其执行结果的返回方式进行说明，不仅可以使智能合约调用请求的发送方掌握智能合约的执行结果，还对当智能合约保存位置不同，返回方式的不同进行了完善。
需要说明的是，虽然以上示例性实施例的实施方式以特定顺序描述了本公开中方法的各个步骤，但是，这并非要求或者暗示必须按照该特定顺序来执行这些步骤，或者必须执行全部的步骤才能实现期望的结果。附加地或者备选地，可以省略某些步骤，将多个步骤合并为一个步骤执行，以及/或者将一个步骤分解为多个步骤执行等。
此外，在本公开的示例实施例中，还提供了一种窗口界面交互装置。参照图6所示，区块链智能合约管理装置600可以包括：请求接收模块601、条件建立模块602、信息判断模块603、第一订立模块604、第二订立模块605。其中：
请求接收模块601，被配置为接收智能合约订立请求，并获取所述智能合约订立请求中的业务类型；条件建立模块602，被配置为根据所述业务类型建立计算资源配置条件；信息判断模块603，被配置为获取当前区块链节点中与所述计算资源配置条件相对应的计算资源配置信息，并判断所述计算资源配置信息是否满足对应的所述计算资源配置条件；第一订立模块604，被配置为若所述当前区块链节点的所述计算资源配置信息满足所述对应的计算资源配置条件，则在所述当前区块链节点订立并保存智能合约；第二订立模块605，被配置为若所述当前区块链节点的所述计算资源配置信息不满足所述对应的计算资源配置条件，则将所述智能合约订立请求发送至大数据处理系统，由大数据处理系统订立并保存智能合约。
上述区块链智能合约管理装置的具体细节已经在对应的区块链智能合约管理方法中进行了详细的描述，因此此处不再赘述。
应当注意，尽管在上文详细描述中提及了区块链智能合约管理装置600的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本公开的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一 步划分为由多个模块或者单元来具体化。
此外，在本公开的示例性实施例中，还提供了一种能够实现上述方法的电子设备。
下面参照图7来描述根据本申请的这种实施例的电子设备700。图7显示的电子设备700仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图7所示，电子设备700以通用计算设备的形式表现。电子设备700的组件可以包括但不限于：上述至少一个处理单元710、上述至少一个存储单元720、连接不同系统组件(包括存储单元720和处理单元710)的总线730、显示单元740。
其中，所述存储单元存储有程序代码，所述程序代码可以被所述处理单元710执行，使得所述处理单元710执行本说明书上述“示例性方法”部分中描述的根据本申请各种示例性实施例的步骤。
存储单元720可以包括易失性存储单元形式的可读介质，例如随机存取存储单元(RAM)7201和/或高速缓存存储单元7202，还可以进一步包括只读存储单元(ROM)7203。
存储单元720还可以包括具有一组(至少一个)程序模块7205的程序/实用工具7204，这样的程序模块7205包括但不限于：操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。
总线730可以为表示几类总线结构中的一种或多种，包括存储单元总线或者存储单元控制器、外围总线、图形加速端口、处理单元或者使用多种总线结构中的任意总线结构的局域总线。
电子设备700也可以与一个或多个外部设备900(例如键盘、指向设备、蓝牙设备等)通信，还可与一个或者多个使得用户能与该电子设备700交互的设备通信，和/或与使得该电子设备700能与一个或多个其它计算设备进行通信的任何设备(例如路由器、调制解调器等等)通信。这种通信可以通过输入/输出(I/O)接口750进行。并且，电子设备700还可以通过网络适配器760与一个或者多个网络(例如局域网(LAN)，广域网(WAN)和/或公共网络， 例如因特网)通信。如图所示，网络适配器740通过总线730与电子设备700的其它模块通信。应当明白，尽管图中未示出，可以结合电子设备700使用其它硬件和/或软件模块，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
通过以上的实施例的描述，本领域的技术人员易于理解，这里描述的示例实施例可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本公开实施例的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、终端装置、或者网络设备等)执行根据本公开实施例的方法。
在本公开的示例性实施例中，还提供了一种计算机可读存储介质，其上存储有能够实现本说明书上述方法的程序产品。在一些可能的实施例中，本申请的各个方面还可以实现为一种程序产品的形式，其包括程序代码，当所述程序产品在终端设备上运行时，所述程序代码用于使所述终端设备执行本说明书上述“示例性方法”部分中描述的根据本申请各种示例性实施例的步骤。
参考图8所示，描述了根据本申请的实施例的用于实现上述方法的程序产品800，其可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码，并可以在终端设备，例如个人电脑上运行。然而，本申请的程序产品不限于此，在本文件中，可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
所述程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以为但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了可读程序代码。这种传播的数据信号可以采用多种形式，包 括但不限于电磁信号、光信号或上述的任意合适的组合。可读信号介质还可以是可读存储介质以外的任何可读介质，该可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于无线、有线、光缆、RF等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言的任意组合来编写用于执行本申请操作的程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、C++等，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络，包括局域网(LAN)或广域网(WAN)，连接到用户计算设备，或者，可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。

Claims (20)

  1. 一种区块链智能合约管理方法，其特征在于，包括：
    接收智能合约订立请求，并获取所述智能合约订立请求中与智能合约相对应的业务类型；
    根据所述业务类型建立计算资源配置条件，并获取当前区块链节点中与所述计算资源配置条件相对应的计算资源配置信息；
    判断所述计算资源配置信息是否满足所述计算资源配置条件；
    若所述计算资源配置信息满足所述计算资源配置条件，则在所述当前区块链节点订立并保存所述智能合约；
    若所述计算资源配置信息不满足所述计算资源配置条件，则将所述智能合约订立请求发送至大数据处理系统，并由所述大数据处理系统订立并保存所述智能合约。
  2. 根据权利要求1所述的区块链智能合约管理方法，其特征在于，所述根据所述业务类型建立计算资源配置条件，包括：
    预设一种或者多种计算资源配置参数；
    根据所述业务类型选择至少一种所述计算资源配置参数，并为选定的所述计算资源配置参数建立所述计算资源配置条件。
  3. 根据权利要求2所述的区块链智能合约管理方法，其特征在于，所述计算资源配置参数包括数值型参数和/或非数值型参数；其中，所述数值型参数包括中央处理器主频、内存容量、硬盘容量和/或网络带宽；所述非数值型参数包括中央处理器类型、内存类型和/或硬盘类型。
  4. 根据权利要求1所述的区块链智能合约管理方法，其特征在于，所述方法还包括：
    接收智能合约调用请求，并根据所述智能合约调用请求判断待调用的所述智能合约是否保存在当前区块链节点或者大数据处理系统上；
    若判定所述待调用的智能合约保存在所述当前区块链节点上，则由所述当前区块链节点执行所述智能合约，并将所述智能合约的执行结果返回给所述智能合约调用请求的发送方；
    若判定所述待调用的智能合约保存在所述大数据处理系统上，则由所述大 数据处理系统执行所述智能合约，并将所述智能合约的执行结果通过所述当前区块链节点返回给所述智能合约调用请求的发送方。
  5. 根据权利要求4所述的区块链智能合约管理方法，其特征在于，所述接收智能合约调用请求，包括：
    获取所述当前区块链节点的多个计算资源使用率；
    对所述计算资源使用率进行运算，并得到一运算结果作为计算资源评分；
    若所述当前区块链节点的所述计算资源评分小于预设阈值，则将接收到的所述智能合约调用请求传送至下一区块链节点。
  6. 根据权利要求4所述的区块链智能合约管理方法，其特征在于，所述方法还包括：
    若所述当前区块链节点的所述计算资源评分小于所述预设阈值，则发送一预警信息。
  7. 根据权利要求4所述的区块链智能合约管理方法，其特征在于，所述将所述智能合约的执行结果通过所述当前区块链节点返回给所述智能合约调用请求的发送方，包括：
    将所述智能合约的所述执行结果保存在所述当前区块链节点上；
    将所述当前区块链节点上保存的所述智能合约的所述执行结果返回给所述智能合约调用请求的发送方。
  8. 一种区块链智能合约管理装置，其特征在于，包括：
    请求接收模块，被配置为接收智能合约订立请求，并获取所述智能合约订立请求中的业务类型；
    条件建立模块，被配置为根据所述业务类型建立计算资源配置条件；
    信息判断模块，被配置为获取当前区块链节点中与所述计算资源配置条件相对应的计算资源配置信息，并判断所述计算资源配置信息是否满足对应的所述计算资源配置条件；
    第一订立模块，被配置为若所述当前区块链节点的所述计算资源配置信息满足所述对应的计算资源配置条件，则在所述当前区块链节点订立并保存智能合约；
    第二订立模块，被配置为若所述当前区块链节点的所述计算资源配置信息 不满足所述对应的计算资源配置条件，则将所述智能合约订立请求发送至大数据处理系统，由大数据处理系统订立并保存智能合约。
  9. 根据权利要求8所述的区块链智能合约管理装置，其特征在于，所述条件建立模块具体用于：
    预设一种或者多种计算资源配置参数；
    根据所述业务类型选择至少一种所述计算资源配置参数，并为选定的所述计算资源配置参数建立所述计算资源配置条件。
  10. 根据权利要求9所述的区块链智能合约管理装置，其特征在于，所述计算资源配置参数包括数值型参数和/或非数值型参数；其中，所述数值型参数包括中央处理器主频、内存容量、硬盘容量和/或网络带宽；所述非数值型参数包括中央处理器类型、内存类型和/或硬盘类型。
  11. 根据权利要求8所述的区块链智能合约管理装置，其特征在于，
    所述请求接收模块，还用于接收智能合约调用请求，并根据所述智能合约调用请求判断待调用的所述智能合约是否保存在当前区块链节点或者大数据处理系统上；若判定所述待调用的智能合约保存在所述当前区块链节点上，则由所述当前区块链节点执行所述智能合约，并将所述智能合约的执行结果返回给所述智能合约调用请求的发送方；若判定所述待调用的智能合约保存在所述大数据处理系统上，则由所述大数据处理系统执行所述智能合约，并将所述智能合约的执行结果通过所述当前区块链节点返回给所述智能合约调用请求的发送方。
  12. 根据权利要求11所述的区块链智能合约管理装置，其特征在于，所述请求接收模块在接收智能合约调用请求时，具体用于：
    获取所述当前区块链节点的多个计算资源使用率；
    对所述计算资源使用率进行运算，并得到一运算结果作为计算资源评分；
    若所述当前区块链节点的所述计算资源评分小于预设阈值，则将接收到的所述智能合约调用请求传送至下一区块链节点。
  13. 根据权利要求11所述的区块链智能合约管理装置，其特征在于，
    所述请求接收模块，还用于若所述当前区块链节点的所述计算资源评分小于所述预设阈值，则发送一预警信息。
  14. 根据权利要求11所述的区块链智能合约管理装置，其特征在于，所述请求接收模块在将所述智能合约的执行结果通过所述当前区块链节点返回给所述智能合约调用请求的发送方时，具体用于：
    将所述智能合约的所述执行结果保存在所述当前区块链节点上；
    将所述当前区块链节点上保存的所述智能合约的所述执行结果返回给所述智能合约调用请求的发送方。
  15. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1-7中任意一项所述的区块链智能合约管理方法。
  16. 一种电子设备，其特征在于，包括：
    处理器；
    存储器，用于存储所述处理器的可执行指令；
    其中，所述处理器被配置为经由执行所述可执行指令来执行以下步骤：
    接收智能合约订立请求，并获取所述智能合约订立请求中与智能合约相对应的业务类型；
    根据所述业务类型建立计算资源配置条件，并获取当前区块链节点中与所述计算资源配置条件相对应的计算资源配置信息；
    判断所述计算资源配置信息是否满足所述计算资源配置条件；
    若所述计算资源配置信息满足所述计算资源配置条件，则在所述当前区块链节点订立并保存所述智能合约；
    若所述计算资源配置信息不满足所述计算资源配置条件，则将所述智能合约订立请求发送至大数据处理系统，并由所述大数据处理系统订立并保存所述智能合约。
  17. 根据权利要求16所述的电子设备，其特征在于，所述处理器在执行所述根据所述业务类型建立计算资源配置条件时，具体执行以下步骤：
    预设一种或者多种计算资源配置参数；
    根据所述业务类型选择至少一种所述计算资源配置参数，并为选定的所述计算资源配置参数建立所述计算资源配置条件。
  18. 根据权利要求16所述的电子设备，其特征在于，所述处理器还执行 以下步骤：
    接收智能合约调用请求，并根据所述智能合约调用请求判断待调用的所述智能合约是否保存在当前区块链节点或者大数据处理系统上；
    若判定所述待调用的智能合约保存在所述当前区块链节点上，则由所述当前区块链节点执行所述智能合约，并将所述智能合约的执行结果返回给所述智能合约调用请求的发送方；
    若判定所述待调用的智能合约保存在所述大数据处理系统上，则由所述大数据处理系统执行所述智能合约，并将所述智能合约的执行结果通过所述当前区块链节点返回给所述智能合约调用请求的发送方。
  19. 根据权利要求18所述的电子设备，其特征在于，所述处理器在执行所述接收智能合约调用请求时，具体执行以下步骤：
    获取所述当前区块链节点的多个计算资源使用率；
    对所述计算资源使用率进行运算，并得到一运算结果作为计算资源评分；
    若所述当前区块链节点的所述计算资源评分小于预设阈值，则将接收到的所述智能合约调用请求传送至下一区块链节点。
  20. 根据权利要求18所述的电子设备，其特征在于，所述处理器在执行所述将所述智能合约的执行结果通过所述当前区块链节点返回给所述智能合约调用请求的发送方时，具体执行以下步骤：
    将所述智能合约的所述执行结果保存在所述当前区块链节点上；
    将所述当前区块链节点上保存的所述智能合约的所述执行结果返回给所述智能合约调用请求的发送方。
PCT/CN2019/120958 2019-01-03 2019-11-26 区块链智能合约管理方法与装置、电子设备、存储介质 WO2020140649A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910003252.2 2019-01-03
CN201910003252.2A CN109803004B (zh) 2019-01-03 2019-01-03 区块链智能合约管理方法与装置、电子设备、存储介质

Publications (1)

Publication Number Publication Date
WO2020140649A1 true WO2020140649A1 (zh) 2020-07-09

Family

ID=66558407

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/120958 WO2020140649A1 (zh) 2019-01-03 2019-11-26 区块链智能合约管理方法与装置、电子设备、存储介质

Country Status (2)

Country Link
CN (1) CN109803004B (zh)
WO (1) WO2020140649A1 (zh)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112200672A (zh) * 2020-09-30 2021-01-08 上海翌派科技有限公司 一种智能合约处理方法及装置
CN112348552A (zh) * 2020-09-27 2021-02-09 北京淇瑀信息科技有限公司 基于预警业务的计算机辅助资源投放管理方法及平台
CN112465117A (zh) * 2020-11-25 2021-03-09 平安科技（深圳）有限公司 合约生成模型构建方法、装置、设备及存储介质
CN112632121A (zh) * 2020-12-15 2021-04-09 京东数字科技控股股份有限公司 区块链数据获取方法和装置
CN113595732A (zh) * 2021-06-11 2021-11-02 上海淇玥信息技术有限公司 一种智能合约交互方法、装置和电子设备
CN114140075A (zh) * 2021-11-30 2022-03-04 平安银行股份有限公司 业务处理方法、装置、介质及电子设备
CN114257383A (zh) * 2020-09-10 2022-03-29 中国电信股份有限公司 数据的处理方法、区块链节点和计算机可读存储介质
CN114584940A (zh) * 2020-11-30 2022-06-03 华为技术有限公司 切片服务处理方法及装置
CN115422262A (zh) * 2022-10-31 2022-12-02 国网浙江省电力有限公司金华供电公司 基于区块链智能合约下全链物资采供数据处理方法及系统
CN114140075B (zh) * 2021-11-30 2024-05-14 平安银行股份有限公司 业务处理方法、装置、介质及电子设备

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109803004B (zh) * 2019-01-03 2021-06-01 深圳壹账通智能科技有限公司 区块链智能合约管理方法与装置、电子设备、存储介质
CN110740057B (zh) * 2019-09-16 2022-03-18 中国联合网络通信集团有限公司 一种业务部署方法以及区块链平台
CN110688677B (zh) * 2019-09-24 2020-12-22 北京海益同展信息科技有限公司 用于执行智能合约的方法和装置
CN112685496B (zh) * 2019-10-18 2024-04-23 阿里巴巴集团控股有限公司 分布式系统及其数据处理方法
CN111026429A (zh) * 2019-11-29 2020-04-17 成都四方伟业软件股份有限公司 一种基于区块链的多后台管理方法及系统
CN112131252A (zh) * 2020-08-16 2020-12-25 中信银行股份有限公司 业务处理方法、装置、电子设备及可读存储介质
CN114125020B (zh) * 2020-09-11 2023-08-29 京东方科技集团股份有限公司 实时数据通信的方法、电子设备和系统
US11736456B2 (en) 2020-09-29 2023-08-22 International Business Machines Corporation Consensus service for blockchain networks
CN113222757A (zh) * 2021-05-06 2021-08-06 永旗(北京)科技有限公司 一种区块链智能合约管理方法及系统
CN113988787B (zh) * 2021-10-22 2022-11-29 中国电信股份有限公司 网络配置方法及装置、存储介质
CN114285848B (zh) * 2021-12-20 2024-03-19 上海简苏网络科技有限公司 区块链资源的可计量方法、系统、电子设备和可读介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8606920B1 (en) * 2010-05-28 2013-12-10 Amazon Technologies, Inc. Providing notification of computing resource availability for on-demand allocation
CN107450981A (zh) * 2017-05-31 2017-12-08 阿里巴巴集团控股有限公司 一种区块链共识方法及设备
CN108323200A (zh) * 2018-01-25 2018-07-24 深圳前海达闼云端智能科技有限公司 基于区块链的数据训练方法、装置、存储介质及区块链节点
CN109803004A (zh) * 2019-01-03 2019-05-24 深圳壹账通智能科技有限公司 区块链智能合约管理方法与装置、电子设备、存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10607285B2 (en) * 2016-02-22 2020-03-31 Bank Of America Corporation System for managing serializability of resource transfers in a process data network
CN107784546B (zh) * 2016-08-31 2020-11-10 北京明朝万达科技股份有限公司 一种基于区块链的数据交易方法和系统
CN107491915A (zh) * 2017-08-03 2017-12-19 迅鳐成都科技有限公司 一种钢铁行业仓储管理系统中基于区块链的货权管理系统
CN108650647A (zh) * 2018-04-27 2018-10-12 深圳市元征科技股份有限公司 一种无线网络资源共享方法以及无线网络资源共享装置
CN108696594A (zh) * 2018-05-27 2018-10-23 佛山市虚拟现实大数据产业研究院有限公司 一种市场监管区块链的大数据传输负载均衡方法及装置
CN108833161B (zh) * 2018-06-11 2020-09-15 北京航空航天大学 一种建立基于雾计算的智能合约微服务模型的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8606920B1 (en) * 2010-05-28 2013-12-10 Amazon Technologies, Inc. Providing notification of computing resource availability for on-demand allocation
CN107450981A (zh) * 2017-05-31 2017-12-08 阿里巴巴集团控股有限公司 一种区块链共识方法及设备
CN108323200A (zh) * 2018-01-25 2018-07-24 深圳前海达闼云端智能科技有限公司 基于区块链的数据训练方法、装置、存储介质及区块链节点
CN109803004A (zh) * 2019-01-03 2019-05-24 深圳壹账通智能科技有限公司 区块链智能合约管理方法与装置、电子设备、存储介质

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114257383A (zh) * 2020-09-10 2022-03-29 中国电信股份有限公司 数据的处理方法、区块链节点和计算机可读存储介质
CN114257383B (zh) * 2020-09-10 2024-04-12 中国电信股份有限公司 数据的处理方法、区块链节点和计算机可读存储介质
CN112348552A (zh) * 2020-09-27 2021-02-09 北京淇瑀信息科技有限公司 基于预警业务的计算机辅助资源投放管理方法及平台
CN112200672A (zh) * 2020-09-30 2021-01-08 上海翌派科技有限公司 一种智能合约处理方法及装置
CN112200672B (zh) * 2020-09-30 2023-03-17 上海翌派科技有限公司 一种智能合约处理方法
CN112465117A (zh) * 2020-11-25 2021-03-09 平安科技（深圳）有限公司 合约生成模型构建方法、装置、设备及存储介质
CN112465117B (zh) * 2020-11-25 2024-05-07 平安科技（深圳）有限公司 合约生成模型构建方法、装置、设备及存储介质
CN114584940B (zh) * 2020-11-30 2023-09-01 华为技术有限公司 切片服务处理方法及装置
CN114584940A (zh) * 2020-11-30 2022-06-03 华为技术有限公司 切片服务处理方法及装置
CN112632121A (zh) * 2020-12-15 2021-04-09 京东数字科技控股股份有限公司 区块链数据获取方法和装置
CN112632121B (zh) * 2020-12-15 2024-04-16 京东科技控股股份有限公司 区块链数据获取方法和装置
CN113595732B (zh) * 2021-06-11 2024-03-19 上海淇玥信息技术有限公司 一种智能合约交互方法、装置和电子设备
CN113595732A (zh) * 2021-06-11 2021-11-02 上海淇玥信息技术有限公司 一种智能合约交互方法、装置和电子设备
CN114140075A (zh) * 2021-11-30 2022-03-04 平安银行股份有限公司 业务处理方法、装置、介质及电子设备
CN114140075B (zh) * 2021-11-30 2024-05-14 平安银行股份有限公司 业务处理方法、装置、介质及电子设备
CN115422262B (zh) * 2022-10-31 2023-01-24 国网浙江省电力有限公司金华供电公司 基于区块链智能合约下全链物资采供数据处理方法及系统
CN115422262A (zh) * 2022-10-31 2022-12-02 国网浙江省电力有限公司金华供电公司 基于区块链智能合约下全链物资采供数据处理方法及系统

Also Published As

Publication number Publication date
CN109803004B (zh) 2021-06-01
CN109803004A (zh) 2019-05-24

Similar Documents

Publication Publication Date Title
WO2020140649A1 (zh) 区块链智能合约管理方法与装置、电子设备、存储介质
CN109710405B (zh) 区块链智能合约管理方法、装置、电子设备及存储介质
WO2021259013A1 (zh) 数据处理方法、装置、电子设备及计算机可读介质
US11582130B2 (en) Performance monitoring in a distributed storage system
US9158650B2 (en) Mobile application performance management
US9389936B2 (en) Monitoring the responsiveness of a user interface
US9384114B2 (en) Group server performance correction via actions to server subset
JP2019525334A (ja) リスク識別方法、クライアントデバイス及びリスク識別システム
CN103970587B (zh) 一种资源调度的方法、设备和系统
CN111045911B (zh) 性能测试方法、性能测试装置、存储介质与电子设备
US7634561B2 (en) Application usage metering management system
CN111352806A (zh) 日志数据监控方法及装置
WO2022120995A1 (zh) 一种基于PoW共识机制的设备算力评价方法及系统
WO2021190659A1 (zh) 系统的数据获取方法、装置、介质及电子设备
CN114564435A (zh) 异构多核芯片的核间通信方法、装置及介质
CN115118777A (zh) 基于业务类型的报文转换方法、装置、设备及存储介质
US20140089341A1 (en) Coordinating data collection among system components
CN112631800A (zh) 面向kafka的数据传输方法、系统、计算机设备及存储介质
CN116150054B (zh) 一种基于pcie的中断信息处理方法
WO2020238131A1 (zh) 网络爬虫系统的测试方法及装置、存储介质、电子设备
CN111858656A (zh) 一种基于分布式架构的静态数据的查询方法和设备
WO2017180186A1 (en) Task management system for a modular electronic device
WO2023066258A1 (zh) 隐私数据的数据处理方法、装置、计算机设备及介质
US11005746B1 (en) Stack group merging system
CN114598705B (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: 19906768

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 20/10/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19906768

Country of ref document: EP

Kind code of ref document: A1