CN112559635B - Service processing method, device, equipment and medium for Ethernet alliance chain node - Google Patents

Service processing method, device, equipment and medium for Ethernet alliance chain node Download PDF

Info

Publication number
CN112559635B
CN112559635B CN202011556624.3A CN202011556624A CN112559635B CN 112559635 B CN112559635 B CN 112559635B CN 202011556624 A CN202011556624 A CN 202011556624A CN 112559635 B CN112559635 B CN 112559635B
Authority
CN
China
Prior art keywords
service
request
business
service request
contract
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202011556624.3A
Other languages
Chinese (zh)
Other versions
CN112559635A (en
Inventor
赖奕宇
曹崇瑞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Netease Hangzhou Network Co Ltd
Original Assignee
Netease Hangzhou Network Co Ltd
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 Netease Hangzhou Network Co Ltd filed Critical Netease Hangzhou Network Co Ltd
Priority to CN202011556624.3A priority Critical patent/CN112559635B/en
Publication of CN112559635A publication Critical patent/CN112559635A/en
Application granted granted Critical
Publication of CN112559635B publication Critical patent/CN112559635B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03Credit; Loans; Processing thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

The application provides a service processing method, device, equipment and medium for Ethernet alliance chain nodes, and relates to the technical field of block chains. The method comprises the following steps: acquiring a service identifier corresponding to the service request according to the service request sent by the client; searching business data corresponding to the business request from a contract account of the intelligent contract stored in the Ethernet alliance link point cache according to the business identifier; if business data corresponding to the business request exists in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the business data in the contract account of the intelligent contract; and executing the service request according to the service data. In the technical scheme, in the process of processing the service by using the Ethernet virtual machine, the service data corresponding to the service request can be acquired by storing the service data in the contract account of the intelligent contract in the link point cache of the Ethernet alliance, so that the service processing performance is improved to some extent, and the service processing efficiency is accelerated.

Description

Service processing method, device, equipment and medium for Ethernet alliance chain node
Technical Field
The invention relates to the technical field of blockchains, in particular to a business processing method, a business processing device, business processing equipment and business processing media for Ethernet alliance chain nodes.
Background
Smart contracts are very significant features of blockchain 2.0, with one typical representation being Ethernet. Ethernet is an open-source public blockchain platform with intelligent contract functionality. Ethernet workshops handle point-to-point contracts through ethernet virtual machines (EVM, ethereum Virtual Machine) ". EVM supports execution of various high-level languages such as Sodility, LISP-Like Language (LLL), and the Like, and provides a good infrastructure for developing intelligent contracts.
In the prior art, when the EVM needs to acquire service data corresponding to a service request in the process of executing a service, the EVM needs to load the service data corresponding to each service request from a disk into a contract account in sequence, so that the EVM executes the service corresponding to the service data according to the service data stored in the contract account.
Because the service data is required to be read from the disk once for each service request, when the service requests are more, the service data reading efficiency is lower, and the service processing performance is reduced.
Disclosure of Invention
The invention aims to provide a service processing method, device, equipment and medium for Ethernet alliance chain nodes, aiming at the defects in the prior art, so as to solve the problem of lower processing performance in the prior art when the service processing is performed based on an Ethernet virtual machine.
In order to achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:
in a first aspect, an embodiment of the present application provides a service processing method of an ethernet factory alliance chain node, which is applied to the ethernet factory alliance chain node, where the ethernet factory alliance chain node compiles and runs an intelligent contract using an ethernet virtual machine, and the method includes:
acquiring a service identifier corresponding to a service request according to the service request sent by a client;
searching business data corresponding to the business request from a contract account of the intelligent contract stored in the Ethernet alliance chain link point cache according to the business identifier;
if the business data corresponding to the business request exists in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the business data in the contract account of the intelligent contract;
And executing the service request according to the service data.
Optionally, after searching the service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance according to the service identifier, the method further includes:
and if the business data corresponding to the business request does not exist in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the hard disk of the Ethernet alliance chain node.
Optionally, before the searching the service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance according to the service identifier, the method further includes:
acquiring service data corresponding to each service request from a service list stored in a hard disk of the Ethernet alliance chain node according to the service data key value corresponding to the acquired at least one service request;
storing the business data corresponding to each business request into a contract account of the intelligent contract corresponding to the business request.
Optionally, the service identifier includes: and the service data key value corresponding to the service request and the service type.
Optionally, the obtaining the service data corresponding to the service request from the service data in the contract account of the intelligent contract includes:
and acquiring service data corresponding to the service request from a contract account of the intelligent contract corresponding to the service request according to the service data key value.
Optionally, the service data includes: a service initiator identifier, a service receiver identifier and a service value; the executing the service request according to the service data includes:
and executing the service request according to the service type according to the service initiator identifier, the service receiver identifier and the service value included in the service data.
Optionally, according to the service identifier, the searching the service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance includes:
and searching the business data corresponding to the business request from the contract account of the intelligent contract stored in the link point cache of the Ethernet alliance by using the business data key value.
In a second aspect, an embodiment of the present application further provides a service processing device of an ethernet factory alliance chain node, which is applied to the ethernet factory alliance chain node, where the ethernet factory alliance chain node compiles and runs an intelligent contract using an ethernet virtual machine, and the device includes: the device comprises an acquisition module, a search module and an execution module;
The acquisition module is used for acquiring a service identifier corresponding to the service request according to the service request sent by the client;
the searching module is used for searching service data corresponding to the service request from a contract account of the intelligent contract stored in the Ethernet alliance link point cache according to the service identifier;
the acquiring module is configured to acquire service data corresponding to the service request from service data in a contract account of the intelligent contract if the service data corresponding to the service request exists in the contract account of the intelligent contract;
and the execution module is used for executing the service request according to the service data.
Optionally, the obtaining module is further configured to obtain, if the service data corresponding to the service request does not exist in the contract account of the intelligent contract, the service data corresponding to the service request from the hard disk of the ethernet alliance chain node.
Optionally, the apparatus further comprises: a storage module;
the acquiring module is used for acquiring service data corresponding to each service request from a service list stored in a hard disk of the Ethernet alliance chain node according to the service data key value corresponding to the acquired at least one service request;
The storage module is used for storing the service data corresponding to each service request into the contract account of the intelligent contract corresponding to the service request.
Optionally, the service identifier includes: and the service data key value corresponding to the service request and the service type.
Optionally, the obtaining module is specifically configured to obtain, according to the service data key value, service data corresponding to the service request from a contract account of the intelligent contract corresponding to the service request.
Optionally, the service data includes: a service initiator identifier, a service receiver identifier and a service value; the execution module is specifically configured to execute the service request according to the service type according to the service initiator identifier, the service receiver identifier, and the service value included in the service data.
Optionally, the searching module is specifically configured to use the service data key value to search service data corresponding to the service request from a contract account of the intelligent contract stored in the link point cache of the ethernet alliance.
In a third aspect, an embodiment of the present application provides an electronic device, including: the system comprises a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, when the electronic device is running, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to execute the steps of the service processing method of the ethernet alliance chain node as provided in the first aspect.
In a fourth aspect, embodiments of the present application provide a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method for traffic handling of ethernet alliance chain nodes as provided in the first aspect.
The beneficial effects of this application are:
the application provides a service processing method, device, equipment and medium for an Ethernet alliance chain node, wherein the service processing method for the Ethernet alliance chain node can comprise the following steps: acquiring a service identifier corresponding to the service request according to the service request sent by the client; searching business data corresponding to the business request from a contract account of the intelligent contract stored in the Ethernet alliance link point cache according to the business identifier; if business data corresponding to the business request exists in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the business data in the contract account of the intelligent contract; and executing the service request according to the service data. In the technical scheme, in the process of processing the service by using the Ethernet virtual machine, the service data corresponding to the service request can be acquired by storing the service data in the contract account of the intelligent contract in the link point cache of the Ethernet alliance, the service data is not required to be acquired from the hard disk by triggering under the current service request, and larger CPU processing capacity is occupied, so that more services can be processed in a limited time, the service processing performance is improved to some extent, and the service processing efficiency is accelerated.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a service processing method of an ethernet alliance chain node according to an embodiment of the present application;
fig. 2 is a flow chart of another service processing method of an ethernet alliance chain node according to an embodiment of the present application;
fig. 3 is a flow chart of another service processing method of an ethernet alliance chain node according to an embodiment of the present application;
fig. 4 is a schematic diagram of a service processing device of an ethernet alliance chain node according to an embodiment of the present application;
fig. 5 is a schematic diagram of a service processing device of another ethernet alliance chain node according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it should be understood that the accompanying drawings in the present application are only for the purpose of illustration and description, and are not intended to limit the protection scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. A flowchart, as used in this application, illustrates operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be implemented out of order and that steps without logical context may be performed in reverse order or concurrently. Moreover, one or more other operations may be added to the flow diagrams and one or more operations may be removed from the flow diagrams as directed by those skilled in the art.
In addition, the described embodiments are only some, but not all, of the embodiments of the present application. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, are intended to be within the scope of the present application.
To enable one skilled in the art to use the present disclosure, the following embodiments are presented in connection with a specific application scenario "ethernet alliance chain". It will be apparent to those having ordinary skill in the art that the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present application.
It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the presence of the features stated hereinafter, but not to exclude the addition of other features.
First, before developing a specific description of the solution provided in the present application, some terms that may be related will be briefly described:
1. ethernet: ethernet (ethernet) is an open source, intelligent contract-enabled public blockchain platform through which dedicated cryptocurrency Ethernet (ETH) provides a decentralised EVM (Ethereum Virtual Machine, ethernet virtual machine) to handle point-to-point contracts.
2. EVM: EVM is a lightweight virtual machine designed to run smart contracts on ethernet networks. As a virtual machine, EVM functions slightly differently than a conventional operating system (e.g., windows). In general, virtual Machines (VMs) are high-level abstractions built on native operating systems that emulate physical machines. They allow the same platform to run on many different hardware architectures and operating systems, which makes Virtual Machines (VMs) well suited for distributed networks like ethernet. The EVM is built to simulate the operations that can be performed by the physical CPU, which is also responsible for many of the key functions of the ethernet.
3. Alliance chain: the generation of each block is determined by all preselected nodes together, and other access nodes can participate in the transaction, but no accounting process is performed, and other third parties can perform limited inquiry through the open API of the blockchain. For better performance, the federation chain has certain requirements for the configuration of consensus or authentication nodes and the network environment. With the admission mechanism, transaction performance can be improved more easily, and problems caused by participants with irregular participation are avoided.
A federated chain remains a private chain in nature, except that it is larger than a private chain developed by a single small organization, but not as large as a public chain, and is understood to be a blockchain that is intermediate between the private and public chains.
4. Intelligent contract: is a computer protocol that aims to propagate, verify or execute contracts in an informative manner. Smart contracts allow trusted transactions to be made without third parties, which transactions are traceable and irreversible.
5. Contract account: is an account controlled by a code, and the transaction of the contract account is not controlled by a private key, but rather the execution of the contract code is triggered by the invocation of a transaction or other smart contract, thereby generating a related transaction.
Next, the background related to the present method will be briefly described.
Blockchain (blockchain) refers to a solution that collectively maintains a reliable database by means of decentralization and de-trust. The participants can establish trust in the technical layer, connect members in the alliance ecology, and construct a point-to-point value transmission network. Including common chains, federated chains, private chains. Public chain (publicblockchain) is completely decentralised, the data on the chain is public and transparent and can not be changed, and anyone can read and write the data through transaction or mining. A coalition chain (confusing chain) refers to a blockchain that has several organizations or organizations that participate in management together, each organization or organization controls one or more nodes, records transaction data together, and only those organizations or organizations can read, write, and send transactions to data in the coalition chain. The private chain (private blockchain) is simply called a private chain, and the private chain is similar to the alliance chain and refers to a blockchain with writing authority in only one organization hand.
Typically, a transaction (service request) needs to undergo several stages of authentication, packaging into blocks, block consensus, etc., before being processed. When the client requests the trade from the alliance chain, each node in the alliance chain independently verifies the trade record according to the comprehensive standard, and adds the verified trade record into a memory pool, which is also called a trade pool, for temporarily storing the trade record which is not packaged into the block. After each node competes with the packing authority, the node obtaining the packing authority packs the packable transaction records recorded in the transaction pool into blocks, the whole network broadcasts a new block for packing, and other nodes synchronize the transaction records of the new block when receiving the new block broadcast, so as to complete the consensus of the transaction. The node then compiles and runs the smart contract using the ethernet virtual machine to execute the transactions in the new block in sequence.
In the prior art, in the process of using the ethernet alliance chain node in the ethernet virtual machine to execute a service, for any service, service data loading is required by using an ethernet virtual machine instruction SSLOAD, and the implementation core of the SSLOAD instruction is to read specified service data from a level db (kv database) through hard disk input/output (IO).
The common ethernet virtual machine instruction is CPU intensive, but since the SSLOAD instruction requires a hard disk IO, the time required for the hard disk IO is a multiple of several orders of magnitude of the pure CPU operation, and it is quite time-consuming to acquire service data through the hard disk IO, so that the performance of executing the service is reduced.
According to the technical scheme, the service data are obtained from the hard disk in batches in advance and stored in the contract account in the cache, so that hard disk IO is not needed in the process of executing the service by using the Ethernet virtual machine, more transactions are executed in unit time, in other words, the service execution performance is greatly improved.
In the following, the implementation principle and the generated beneficial effects of the service processing method of the ethernet alliance chain node provided in the present application will be described through a plurality of specific embodiments.
Fig. 1 is a flow chart of a service processing method of an ethernet alliance chain node according to an embodiment of the present application; the method can be applied to the Ethernet alliance chain nodes, the Ethernet alliance chain nodes compile and operate intelligent contracts by using the Ethernet virtual machine, wherein the Ethernet alliance chain can comprise a plurality of nodes, and the method provided by the application can be applied to any node in the alliance chain. Optionally, as shown in fig. 1, the method may include:
S101, according to a service request sent by a client, acquiring a service identifier corresponding to the service request.
Each node in the federation chain corresponds to each computer or server terminal storing all block data. The generation of all new blocks, and the verification and billing of transactions (traffic) and broadcasting them to the whole network for synchronization are done by the nodes.
Optionally, the client sends a service request to the federation link node, where the service request may refer to a transaction request, and by analyzing the service request, a service identifier corresponding to the service request may be obtained. In this embodiment, the service identifier may be used to distinguish the current service from other services, so as to accurately execute the current service request.
In some embodiments, the service request may be a transfer request, a receipt, a borrowing request, etc., and the embodiment does not limit the specific service request type.
S102, searching service data corresponding to the service request from a contract account of the intelligent contract stored in the link point cache of the Ethernet alliance according to the service identifier.
Note that, the contract account of the intelligent contract stored in the link point cache of the ethernet alliance, that is, the contract account of the intelligent contract stored in the cache of the link point of the ethernet alliance.
Optionally, the contract account may store service data corresponding to the service request, and before executing the service, the service data corresponding to the service request needs to be acquired first to call the corresponding intelligent contract code, and the service data is used as an input parameter of the code, so as to execute the service request.
In one implementation manner, service data corresponding to the service request may be searched from a contract account of the intelligent contract stored in the link point cache of the ethernet alliance by using the service identifier corresponding to the acquired service request.
Correspondingly, in the contract account, the service data corresponding to the service request can be stored in a list form and correspondingly stored in a mapping relation between the service identifier and the service data, and when the service data corresponding to the service request is searched from the contract account of the intelligent contract in the cache, the matched service identifier can be found in the contract account according to the service identifier, so that the service data corresponding to the service request is obtained according to the mapping relation between the service identifier and the service data.
S103, if business data corresponding to the business request exists in the contract account of the intelligent contract, the business data corresponding to the business request is obtained from the business data in the contract account of the intelligent contract.
Optionally, when service data corresponding to the service request can be found from the contract account of the intelligent contract according to the service identifier, the service data can be directly acquired.
S104, executing the service request according to the service data.
Optionally, the service identifier is used to obtain service data corresponding to the service request, where the service data is used to indicate a specific execution parameter of the current service, that is, indicate an action performed by the current service, and the ethernet alliance chain node may compile and operate a specified contract code in the intelligent contract by using the ethernet virtual machine, so that the obtained service data is used as an input parameter of the method to perform the service request.
In summary, this embodiment provides a service processing method for an ethernet alliance link node, including: acquiring a service identifier corresponding to the service request according to the service request sent by the client; searching business data corresponding to the business request from a contract account of the intelligent contract stored in the Ethernet alliance link point cache according to the business identifier; if business data corresponding to the business request exists in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the business data in the contract account of the intelligent contract; and executing the service request according to the service data. In the technical scheme, in the process of processing the service by using the Ethernet virtual machine, the service data corresponding to the service request can be acquired by storing the service data in the contract account of the intelligent contract in the link point cache of the Ethernet alliance, the service data is not required to be acquired from the hard disk by triggering under the current service request, and larger CPU processing capacity is occupied, so that more services can be processed in a limited time, the service processing performance is improved to some extent, and the service processing efficiency is accelerated.
Fig. 2 is a flow chart of another service processing method of an ethernet alliance chain node according to an embodiment of the present application; optionally, as shown in fig. 2, in step S102, after searching, according to the service identifier, service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance, a method of the present application may further include:
s201, if service data corresponding to the service request does not exist in the contract account of the intelligent contract, the service data corresponding to the service request is obtained from the hard disk of the Ethernet alliance chain node.
In some embodiments, due to possible data omission or data error in the data storage process, no service data currently being searched exists in the contract account of the intelligent contract stored in the link point cache of the ethernet alliance, and then the service data corresponding to the service request may be obtained from the hard disk of the link point of the ethernet alliance according to the obtained service identifier.
In this embodiment, service data corresponding to the service request is obtained from the hard disk of the ethernet alliance link node, and is only executed when the service data does not exist in the contract account of the intelligent contract in the ethernet alliance link point cache, and under normal conditions, various possible service data corresponding to the service request exists in the contract account of the intelligent contract in the ethernet alliance link point cache.
Fig. 3 is a flow chart of another service processing method of an ethernet alliance chain node according to an embodiment of the present application; optionally, as shown in fig. 3, in step S102, before searching, according to the service identifier, service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance, a method of the present application may further include:
s301, according to the acquired service data key value corresponding to at least one service request, acquiring service data corresponding to each service request from a service list stored in a hard disk of an Ethernet alliance chain node.
In step S102, the service data stored in the contract account of the intelligent contract in the link point cache of the ethernet alliance is preloaded into the contract account before the service request is blocked.
Alternatively, the service data corresponding to each service request may be obtained from the service list stored in the hard disk of the ethernet alliance chain node through at least one service data key (store_key), and stored into the contract account.
The information contained in a conventional service request is enumerated by a specific code as follows:
Figure BDA0002855872430000101
Figure BDA0002855872430000111
Wherein, "from": "exj" may represent a service originator identity; "to": "exj1132" may identify the service recipient identity; "method": "addMoney (unit)" means the smart contract method to be invoked; input ": [ "user1",12] represents parameters required for the execution of the smart contract method; userBalanceMap [ userid ] represents a service value.
In this embodiment, in order to obtain, in advance, service data corresponding to the service request from the hard disk according to the service data key value of the service request, corresponding attribute information needs to be added to the service request sent by the client. The first is "preLoad" indicating whether or not a preLoad needs to be performed, and the second is "storekey structlist", i.e. a list of key calculation items of business data key values that need to be loaded.
Likewise, the information contained in a service request acquired in the present application is listed by a specific code:
Figure BDA0002855872430000112
Figure BDA0002855872430000121
the service request code according to the present embodiment further includes the above-mentioned two attribute information, compared with the conventional service request code. Thus, by analyzing the service request, the service data key value corresponding to the service request can be obtained. Therefore, the service data corresponding to each service request can be obtained from the service list stored in the hard disk of the Ethernet alliance chain node according to the service data key value.
In addition, in this embodiment, a simple description will be given of a calculation method of the service data key value store_key. store_key=keccak 256 (bytes 32 (key) +bytes32 (position)). The key in the formula, the use case refers to "user1", the business_value is a service value stored by a contract code, the use case refers to a token value corresponding to "user1", namely a service value represented by userbalanceMap [ userid ], the position is a position of a class attribute, and in the code, the [ userbalanceMap ] is 0, the [ uservalidMap ] is 1, and the keccak256 is a built-in hash algorithm. Thus, the service data key value corresponding to the service request can be obtained through analysis.
S302, storing the business data corresponding to each business request into a contract account of the intelligent contract corresponding to the business request.
In general, a service request corresponds to creating a contract account, that is, a service request corresponds to a contract account, and the acquired service data is stored in the contract account of the intelligent contract corresponding to each service request, that is, the contract account corresponding to the service request is created.
The service data corresponding to each service request obtained from the hard disk can be respectively stored in the contract account of the intelligent contract corresponding to each service request, so that the service request can be executed according to the service data stored in the contract account by calling the corresponding intelligent contract method by using the Ethernet virtual machine.
Optionally, in the step S101, the acquired service identifier may include: service data key value and service type corresponding to service request.
Alternatively, by parsing the service request, the above-mentioned service data key value may be obtained, and the service type may be obtained, where the service type may refer to a type of service to be processed currently, for example: transfer, loan, etc. The service type may be based on the inclusion in the service request: "method": "addMoney (unit)", i.e., the called smart contract method.
The specific method for obtaining the service data key value is described in the above example related to step S201, and will not be described herein.
Optionally, in the step S103, the obtaining the service data corresponding to the service request from the service data in the contract account of the smart contract may include: and acquiring service data corresponding to the service request from the contract account of the intelligent contract corresponding to the service request according to the service data key value.
In some embodiments, although all service data corresponding to the service request is stored in the hot contract account, one service request may correspond to an independent contract account, and to obtain service data from the contract account corresponding to the service request, matching is performed in all contract accounts through the obtained service data key value, so as to determine the contract account corresponding to the service request, thereby obtaining the service data corresponding to the service request.
When the contract account is created, the service data key value corresponding to the service request is used as the identification of the account, so that the contract account corresponding to the current service request can be determined from a plurality of contract accounts according to the service data key value, and service data can be acquired.
Alternatively, the service data may include: a service initiator identifier, a service receiver identifier and a service value; in the step S104, executing the service request according to the service data may include: and executing the service request according to the service type and the service value according to the service initiator identifier, the service receiver identifier and the service value included in the service data.
Optionally, the ethernet alliance chain node may invoke an intelligent contract method corresponding to the service type, and execute the service request by using a service initiator identifier, a service receiver identifier, and a service value included in the service data as input parameters of the method.
The service request performed may be, for example: and transferring the money from the service initiator A to the service receiver B, wherein the transfer amount is a numerical value corresponding to the service value.
The core code of the technical scheme is provided as follows: the business data is preloaded from the hard disk and stored into a contract account of the smart contract.
Figure BDA0002855872430000141
The account is a data structure of an account model in the contract account. And traversing all specified preloaded items under the business, namely analyzing parameters such as the key 256, the key, the position and the like required by acquiring the key value store_key of the calculated business data. And the service data key value pair are read from the hard disk according to the acquired service data key value, and the service data key value pair are stored in a contract account (the service data key value and the service data are stored in the contract account in the form of key value pair, for example, the service data key value is the service data, so that the service data corresponding to the service request is acquired from the contract account according to the service data key value).
Based on the above-mentioned business data corresponding to a plurality of business requests obtained from the hard disk in advance, store into the contract account, in the course of using the Ethernet virtual machine to process the business request, do not need to carry on the hard disk IO once to each business request, obtain the business data once from the hard disk, but can obtain the corresponding business data from the corresponding contract account according to the business data key value corresponding to the business request directly, thus has saved the time consumption to carry on disk IO greatly, has reduced CPU's occupation, has raised the business processing efficiency.
Optionally, in the step S102, according to the service identifier, searching the service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance may include: and searching the business data corresponding to the business request from the contract account of the intelligent contract stored in the link point cache of the Ethernet alliance by using the business data key value.
Similarly, when the service data corresponding to the service request is searched from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance according to the service identifier, the matched service data key value may be found from the contract account according to the service data key value obtained by parsing, so as to obtain the service data corresponding to the matched service data key value, and the service data is used as the service data corresponding to the service request.
In summary, the embodiment of the present application provides a service processing method for an ethernet alliance link node, including: acquiring a service identifier corresponding to the service request according to the service request sent by the client; searching business data corresponding to the business request from a contract account of the intelligent contract stored in the Ethernet alliance link point cache according to the business identifier; if business data corresponding to the business request exists in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the business data in the contract account of the intelligent contract; and executing the service request according to the service data. In the technical scheme, in the process of processing the service by using the Ethernet virtual machine, the service data corresponding to the service request can be acquired by storing the service data in the contract account of the intelligent contract in the link point cache of the Ethernet alliance, the service data is not required to be acquired from the hard disk by triggering under the current service request, and larger CPU processing capacity is occupied, so that more services can be processed in a limited time, the service processing performance is improved to some extent, and the service processing efficiency is accelerated.
The following describes a device, an electronic device, a storage medium, etc. for executing the service processing method of the ethernet alliance chain node provided in the present application, and specific implementation processes and technical effects of the device and the electronic device are referred to above, which are not described in detail below.
Fig. 4 is a schematic diagram of a service processing device of an ethernet alliance link node according to an embodiment of the present application, where the service processing device of the ethernet alliance link node may be applied to the ethernet alliance link node, and the ethernet alliance link node compiles and runs an intelligent contract using an ethernet virtual machine, and a function implemented by the service processing device of the ethernet alliance link node corresponds to a step executed by the above method. The device can be understood as the ethernet alliance chain node described above.
Alternatively, as shown in fig. 4, the apparatus may include: an acquisition module 401, a search module 402 and an execution module 403;
an obtaining module 401, configured to obtain, according to a service request sent by a client, a service identifier corresponding to the service request;
the searching module 402 is configured to search, according to the service identifier, service data corresponding to the service request from a contract account of the intelligent contract stored in the link point cache of the ethernet alliance;
the obtaining module 401 is configured to obtain, if service data corresponding to the service request exists in the contract account of the intelligent contract, service data corresponding to the service request from the service data in the contract account of the intelligent contract;
An execution module 403, configured to execute the service request according to the service data.
Optionally, the obtaining module 401 is further configured to obtain, if service data corresponding to the service request does not exist in the contract account of the intelligent contract, service data corresponding to the service request from the hard disk of the ethernet alliance chain node.
Fig. 5 is a schematic diagram of another service processing apparatus of an ethernet alliance chain node according to an embodiment of the present application, and optionally, as shown in fig. 5, the apparatus may further include: a storage module 404;
an obtaining module 401, configured to obtain, according to the obtained service data key value corresponding to the at least one service request, service data corresponding to each service request from a service list stored in a hard disk of the ethernet alliance chain node;
and the storage module 404 is configured to store the service data corresponding to each service request into the contract account of the intelligent contract corresponding to the service request.
Optionally, the service identifier includes: service data key value and service type corresponding to service request.
Optionally, the obtaining module 401 is specifically configured to obtain, according to the service data key value, service data corresponding to the service request from a contract account of the intelligent contract corresponding to the service request.
Optionally, the service data includes: a service initiator identifier, a service receiver identifier and a service value; the execution module 403 is specifically configured to execute a service request according to a service type according to a service initiator identifier, a service receiver identifier, and a service value included in the service data.
Optionally, the searching module 402 is specifically configured to use the service data key value to search the service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance.
The foregoing apparatus is used for executing the method provided in the foregoing embodiment, and its implementation principle and technical effects are similar, and are not described herein again.
The above modules may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more microprocessors (digital singnal processor, abbreviated as DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), or the like. For another example, when a module above is implemented in the form of a processing element scheduler code, the processing element may be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke the program code. For another example, the modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
The modules may be connected or communicate with each other via wired or wireless connections. The wired connection may include a metal cable, optical cable, hybrid cable, or the like, or any combination thereof. The wireless connection may include a connection through a LAN, WAN, bluetooth, zigBee, or NFC, or any combination thereof. Two or more modules may be combined into a single module, and any one module may be divided into two or more units. It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system and apparatus may refer to corresponding procedures in the method embodiments, which are not described in detail in this application.
It should be noted that these above modules may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more microprocessors (Digital Singnal Processor, abbreviated as DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), or the like. For another example, when a module above is implemented in the form of a processing element scheduler code, the processing element may be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke the program code. For another example, the modules may be integrated together and implemented in the form of a System-on-a-chip (SOC).
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application, where the electronic device may include: processor 601, memory 602.
The memory 602 stores therein program code that, when executed by the processor 601, causes the processor 601 to perform the various steps of the traffic handling method of an ethernet alliance chain node according to various exemplary embodiments of the present application described in the "exemplary methods" section of the present description above. For example, the processor 601 may perform steps S101-S104 as shown in fig. 1 to implement the processing of the service request.
The processor 601 may be a general purpose processor such as a Central Processing Unit (CPU), digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.
The memory 602 is a non-volatile computer readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs, and modules. The Memory may include at least one type of storage medium, which may include, for example, flash Memory, hard disk, multimedia card, card Memory, random access Memory (Random Access Memory, RAM), static random access Memory (Static Random Access Memory, SRAM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read-Only Memory (ROM), charged erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), magnetic Memory, magnetic disk, optical disk, and the like. The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 602 in the present embodiment may also be circuitry or any other device capable of implementing a memory function for storing program instructions and/or data.
In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (english: processor) to perform some of the steps of the methods according to the embodiments of the invention. And the aforementioned storage medium includes: u disk, mobile hard disk, read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.

Claims (8)

1. A business processing method of an ethernet alliance chain node, which is characterized in that the business processing method is applied to the ethernet alliance chain node, wherein the ethernet alliance chain node compiles and runs intelligent contracts by using an ethernet virtual machine, and the method comprises the following steps:
according to a service request sent by a client, acquiring a service identifier corresponding to the service request, wherein the service identifier comprises: a service data key value corresponding to the service request and a service type;
searching business data corresponding to the business request from a contract account of the intelligent contract stored in the Ethernet alliance chain link point cache according to the business identifier;
if the business data corresponding to the business request exists in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the business data in the contract account of the intelligent contract;
executing the service request according to the service data;
before searching the service data corresponding to the service request from the contract account of the intelligent contract stored in the link point cache of the ethernet alliance according to the service identifier, the method further includes:
acquiring service data corresponding to each service request from a service list stored in a hard disk of the Ethernet alliance chain node according to the service data key value corresponding to the acquired at least one service request;
Storing the business data corresponding to each business request into a contract account of the intelligent contract corresponding to the business request.
2. The method according to claim 1, wherein after searching the service data corresponding to the service request from the contract account of the intelligent contract stored in the ethernet alliance link point cache according to the service identifier, the method further comprises:
and if the business data corresponding to the business request does not exist in the contract account of the intelligent contract, acquiring the business data corresponding to the business request from the hard disk of the Ethernet alliance chain node.
3. The method according to claim 1, wherein the obtaining the service data corresponding to the service request from the service data in the contract account of the smart contract includes:
and acquiring service data corresponding to the service request from a contract account of the intelligent contract corresponding to the service request according to the service data key value.
4. The method of claim 1, wherein the traffic data comprises: a service initiator identifier, a service receiver identifier and a service value; the executing the service request according to the service data includes:
And executing the service request according to the service type according to the service initiator identifier, the service receiver identifier and the service value included in the service data.
5. The method according to claim 1, wherein the searching the service data corresponding to the service request from the contract account of the intelligent contract stored in the ethernet alliance link point cache according to the service identifier includes:
and searching the business data corresponding to the business request from the contract account of the intelligent contract stored in the link point cache of the Ethernet alliance by using the business data key value.
6. A service processing device for an ethernet alliance chain node, the service processing device being applied to the ethernet alliance chain node, the ethernet alliance chain node compiling and running an intelligent contract using an ethernet virtual machine, the device comprising: the device comprises an acquisition module, a search module and an execution module;
the obtaining module is configured to obtain, according to a service request sent by a client, a service identifier corresponding to the service request, where the service identifier includes: a service data key value corresponding to the service request and a service type;
The searching module is used for searching service data corresponding to the service request from a contract account of the intelligent contract stored in the Ethernet alliance link point cache according to the service identifier;
the acquiring module is configured to acquire service data corresponding to the service request from service data in a contract account of the intelligent contract if the service data corresponding to the service request exists in the contract account of the intelligent contract;
the execution module is used for executing the service request according to the service data;
wherein the apparatus further comprises: a storage module;
the acquiring module is used for acquiring service data corresponding to each service request from a service list stored in a hard disk of the Ethernet alliance chain node according to the service data key value corresponding to the acquired at least one service request;
the storage module is used for storing the service data corresponding to each service request into the contract account of the intelligent contract corresponding to the service request.
7. An electronic device, comprising: a processor, a storage medium, and a bus, the storage medium storing program instructions executable by the processor, the processor and the storage medium communicating through the bus when the electronic device is running, the processor executing the program instructions to perform the steps of the traffic processing method of the ethernet alliance chain node according to any of claims 1 to 5 when executed.
8. A computer readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when executed by a processor, performs the steps of the method for traffic handling of ethernet alliance chain nodes according to any of claims 1 to 5.
CN202011556624.3A 2020-12-23 2020-12-23 Service processing method, device, equipment and medium for Ethernet alliance chain node Active CN112559635B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011556624.3A CN112559635B (en) 2020-12-23 2020-12-23 Service processing method, device, equipment and medium for Ethernet alliance chain node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011556624.3A CN112559635B (en) 2020-12-23 2020-12-23 Service processing method, device, equipment and medium for Ethernet alliance chain node

Publications (2)

Publication Number Publication Date
CN112559635A CN112559635A (en) 2021-03-26
CN112559635B true CN112559635B (en) 2023-06-16

Family

ID=75033969

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011556624.3A Active CN112559635B (en) 2020-12-23 2020-12-23 Service processing method, device, equipment and medium for Ethernet alliance chain node

Country Status (1)

Country Link
CN (1) CN112559635B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113283987A (en) * 2021-05-17 2021-08-20 网易(杭州)网络有限公司 Service processing method, device, block chain gateway, block chain node and storage medium
CN113595732B (en) * 2021-06-11 2024-03-19 上海淇玥信息技术有限公司 Intelligent contract interaction method and device and electronic equipment
CN115203747A (en) * 2022-07-29 2022-10-18 蚂蚁区块链科技(上海)有限公司 Data account creation method and device

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109034814A (en) * 2018-09-14 2018-12-18 百度在线网络技术(北京)有限公司 Intelligent contract treating method and apparatus based on ether mill virtual machine
CN110597837A (en) * 2019-09-19 2019-12-20 腾讯科技(深圳)有限公司 Service data processing method, device, storage medium and computer equipment
CN110599169A (en) * 2019-09-16 2019-12-20 腾讯科技(深圳)有限公司 Data processing method, device, terminal and medium
CN111047321A (en) * 2019-12-27 2020-04-21 支付宝实验室(新加坡)有限公司 Service processing method and device, electronic equipment and storage medium
CN111260469A (en) * 2020-01-10 2020-06-09 杭州溪塔科技有限公司 Block chain-based evidence storing method, block chain-based evidence storing query method, corresponding device and electronic equipment
CN111340470A (en) * 2020-02-24 2020-06-26 中国工商银行股份有限公司 Block chain transaction processing method, node and contract container
CN111625593A (en) * 2020-04-21 2020-09-04 金蝶软件(中国)有限公司 Data processing method and device based on block chain and computer equipment
CN111630830A (en) * 2020-04-15 2020-09-04 支付宝(杭州)信息技术有限公司 Distributed blockchain data storage under account model
CN111967995A (en) * 2020-10-20 2020-11-20 支付宝(杭州)信息技术有限公司 Intelligent contract creating method and device

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107025559B (en) * 2017-01-26 2020-09-18 创新先进技术有限公司 Service processing method and device
US11195180B2 (en) * 2019-01-25 2021-12-07 International Business Machines Corporation Virtual blockchain
CN110008738B (en) * 2019-02-21 2021-06-25 网易(杭州)网络有限公司 Caching method, device, medium and computing equipment for block chain contract data
US11410168B2 (en) * 2019-04-03 2022-08-09 Acronis International Gmbh Method for user management for blockchain-based operations
AU2019204729B2 (en) * 2019-04-03 2021-03-11 Advanced New Technologies Co., Ltd. Processing blockchain data based on smart contract operations executed in a trusted execution environment
US11556923B2 (en) * 2019-05-24 2023-01-17 Visa International Service Association Blockchain enabled service request system
CN111090697A (en) * 2019-11-13 2020-05-01 中国地质大学(北京) Ticket system based on alliance chain

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109034814A (en) * 2018-09-14 2018-12-18 百度在线网络技术(北京)有限公司 Intelligent contract treating method and apparatus based on ether mill virtual machine
CN110599169A (en) * 2019-09-16 2019-12-20 腾讯科技(深圳)有限公司 Data processing method, device, terminal and medium
CN110597837A (en) * 2019-09-19 2019-12-20 腾讯科技(深圳)有限公司 Service data processing method, device, storage medium and computer equipment
CN111047321A (en) * 2019-12-27 2020-04-21 支付宝实验室(新加坡)有限公司 Service processing method and device, electronic equipment and storage medium
CN111260469A (en) * 2020-01-10 2020-06-09 杭州溪塔科技有限公司 Block chain-based evidence storing method, block chain-based evidence storing query method, corresponding device and electronic equipment
CN111340470A (en) * 2020-02-24 2020-06-26 中国工商银行股份有限公司 Block chain transaction processing method, node and contract container
CN111630830A (en) * 2020-04-15 2020-09-04 支付宝(杭州)信息技术有限公司 Distributed blockchain data storage under account model
CN111625593A (en) * 2020-04-21 2020-09-04 金蝶软件(中国)有限公司 Data processing method and device based on block chain and computer equipment
CN111967995A (en) * 2020-10-20 2020-11-20 支付宝(杭州)信息技术有限公司 Intelligent contract creating method and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于区块链的智能合约技术与应用综述;贺海武;延安;陈泽华;;计算机研究与发展(第11期);全文 *

Also Published As

Publication number Publication date
CN112559635A (en) 2021-03-26

Similar Documents

Publication Publication Date Title
CN112559635B (en) Service processing method, device, equipment and medium for Ethernet alliance chain node
US11514191B2 (en) Weighted source data secured on blockchains
US11074245B2 (en) Method and device for writing service data in block chain system
CN110046023B (en) Data processing method and system based on intelligent contract of block chain
KR102024694B1 (en) Decentralized service platform using multiple service nodes based on block chain
CN109933404B (en) Encoding and decoding method and system based on block chain intelligent contract
CN110968437A (en) Method, device, equipment and medium for parallel execution of single contract based on Java intelligent contract
CN109934712A (en) Account checking method, account checking apparatus and electronic equipment applied to distributed system
CN112631924A (en) Automatic testing method and device, computer equipment and storage medium
WO2022267769A1 (en) Method and apparatus for generating graph data
CN112561690A (en) Method, system, equipment and storage medium for testing credit card staging service interface
US9747448B2 (en) Cryptographic mechanisms to provide information privacy and integrity
CN116955148A (en) Service system testing method, device, equipment, storage medium and product
CN115203746A (en) Data account access authorization method and device
CN115203747A (en) Data account creation method and device
KR20230132878A (en) Reduce transaction cancellations in execute-order-verify blockchain models
CN113010115A (en) Data processing method in block chain node and related equipment
CN110650063A (en) Centralized bank third-party software simulation system and method
CN112948480B (en) Data extraction method, device, electronic equipment and storage medium
CN117574320B (en) Data processing method, device, computer readable medium and electronic equipment
CN115250231B (en) Application configuration method and device
CN104519096A (en) Service deployment method and system used for cloud calculating system
CN112541764B (en) Asset management method, device and system based on intelligent contract
CN117408687A (en) Block chain-based service processing method, device, equipment, medium and product
CN117335976A (en) Block chain-based key processing method, device, equipment, medium and product

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant