CN115002104A - Data transaction method, equipment and system - Google Patents

Data transaction method, equipment and system Download PDF

Info

Publication number
CN115002104A
CN115002104A CN202110192805.0A CN202110192805A CN115002104A CN 115002104 A CN115002104 A CN 115002104A CN 202110192805 A CN202110192805 A CN 202110192805A CN 115002104 A CN115002104 A CN 115002104A
Authority
CN
China
Prior art keywords
transaction
blockchain
information
management module
transaction request
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.)
Pending
Application number
CN202110192805.0A
Other languages
Chinese (zh)
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.)
Petal Cloud Technology Co Ltd
Original Assignee
Petal Cloud Technology 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 Petal Cloud Technology Co Ltd filed Critical Petal Cloud Technology Co Ltd
Priority to CN202110192805.0A priority Critical patent/CN115002104A/en
Publication of CN115002104A publication Critical patent/CN115002104A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2471—Distributed queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Data Mining & Analysis (AREA)
  • Finance (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Fuzzy Systems (AREA)
  • Software Systems (AREA)
  • Probability & Statistics with Applications (AREA)
  • Computing Systems (AREA)
  • Mathematical Physics (AREA)
  • Computer Hardware Design (AREA)
  • Computational Linguistics (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application relates to the technical field of block chains, and discloses a data transaction method which is applied to intermediate equipment, wherein the intermediate equipment maintains transaction records related to a service scene. After a transaction request initiated by a user is obtained, a transaction record matched with the transaction request is searched from the transaction records, and then whether the transaction information of the corresponding transaction record is consistent with the transaction information of the transaction request is detected. If the two block chains are consistent, the transaction is initiated to the corresponding block chain. Since the transaction request may indicate a data writing pattern and a data structure, i.e. the transaction request characterizes a kind of data source. Therefore, according to the technical scheme of the embodiment of the application, the historical transaction information matched with the transaction request is obtained through the transaction record maintained under the line, and then the corresponding transaction is executed under the condition that the credibility of the data source is ensured, so that the consistency of the same service data in different block chains can be ensured, and the credibility of the system is further ensured.

Description

Data transaction method, equipment and system
Technical Field
The embodiment of the application relates to the technical field of block chains, in particular to a data transaction method, equipment and system.
Background
A blockchain (blockchain) is a distributed database of a chained data structure that combines blocks of data in a sequential manner. Since the block chain has the characteristics of distributed fault tolerance, non-tamper resistance, privacy protection and the like, the block chain technology can be applied to various business fields such as currency, securities, patents, copyright, digital goods, internet of things and the like.
A service scenario may involve multiple blockchains, and some or all of the blockchains may be developed based on different underlying architectures. The transaction processing modes related to different underlying architectures may be different, and therefore, data interaction cannot be performed between block chains related to different underlying architectures, so that data islands are formed. Because it is difficult to determine whether a data source is trusted, if different blockchains respectively receive different transaction requests for the same service data, the service data is easily inconsistent in the different blockchains, and thus the system reliability related to a service scene is poor.
Disclosure of Invention
The embodiment of the application provides a data transaction method, equipment and a system, which are used for solving the problem that whether a data source is credible cannot be ensured under the scene that at least two block chains cannot carry out data interaction.
In a first aspect, embodiments of the present application provide a data transaction method, which may be executed by an electronic device, and may also be executed by a component (e.g., a chip, a system-on-chip, or a processor) of the electronic device. The method comprises the following steps: obtaining a transaction request input by a user; inquiring a first transaction record matched with the transaction request from prestored transaction records; obtaining first transaction information from a first blockchain associated with the first transaction record; and if the transaction information related to the transaction request is consistent with the first transaction information, submitting the transaction request to at least one second blockchain related to the transaction request.
Wherein the transaction request may indicate a data writing pattern and a data structure, i.e. the transaction request characterizes one data source. The transaction record may include information such as blockchain identification, node identification, transaction mode, etc. associated with the transaction. In the technical solution of the embodiment of the application, for example, the electronic device may use a transaction record in which a data writing mode in the transaction record is the same as a data writing mode related to the transaction request as a first transaction record matched with the transaction request, and may use data structure information of the first transaction information and structure information of data to be written in the transaction request as the transaction information related to the transaction request and the first transaction information as the same. Based on this, it can be seen that, by adopting the implementation manner of the embodiment of the present application, in a scenario where a blockchain cannot perform data interaction, historical transaction information matched with a transaction request can be obtained through a transaction record maintained under a line, and then, under a condition that a data source is ensured to be credible, a corresponding transaction is executed, so that consistency of the same service data in different blockchains can be ensured, and further, the credibility of a system is ensured.
In an alternative design, submitting the transaction request to at least one second blockchain associated with the transaction request includes: obtaining identity certificate key information of each second blockchain in the at least one second blockchain and routing address information of nodes in each second blockchain; packaging the transaction request based on the identity certificate key information of each second blockchain; and writing the packaged transaction request into the corresponding second blockchain based on the routing address information of the nodes in each second blockchain.
In an optional design, after submitting the transaction request to at least one second blockchain associated with the transaction request, the method further includes: storing a transaction record associated with the transaction request. Therefore, by adopting the implementation mode, the transaction records can be updated in time according to the transaction change of the block chain, so that reliable detection information is provided.
In an alternative design, the method further comprises: and if the pre-stored transaction record does not comprise the first transaction record matched with the transaction request, submitting the transaction request to at least one second blockchain related to the transaction request.
In an alternative design, the method further comprises: and if the transaction information related to the transaction request is inconsistent with the first transaction information, submitting transaction request failure information.
In an alternative design, further comprising: obtaining a query request input by a user, wherein the query request indicates second transaction information; if the pre-stored transaction record comprises a second transaction record, obtaining at least one block chain related to the second transaction record; reading the second transaction information from one of the at least one blockchain.
In an alternative design, reading the second transaction information from one of the at least one blockchain includes: obtaining a node of a block chain with a nearest route in the at least one block chain; reading the second transaction information from a node of the blockchain closest to the route.
In an alternative design, further comprising: receiving identity certificate key information and transaction records of each block chain in at least two block chains, and routing address information of all nodes in each block chain; and periodically detecting the connectivity of the routing address information of each node.
In a second aspect, an embodiment of the present application provides a data transaction apparatus, where the apparatus includes an agent module, a data management module, and an uplink management module, where the agent module is configured to obtain a transaction request input by a user; the data management module is used for inquiring a first transaction record matched with the transaction request from prestored transaction records; the data management module is further configured to obtain first transaction information from a first blockchain associated with the first transaction record; and the uplink management module is used for submitting the transaction request to at least one second block chain related to the transaction request if the transaction information related to the transaction request is consistent with the first transaction information.
In an optional design, the device further includes an identity management module and a routing management module, where the identity management module is configured to store identity certificate key information of the block chain; the routing management module is used for storing the routing address information of the nodes in the block chain; the uplink management module is further configured to obtain, from the identity management module, identity certificate key information of each second blockchain in the at least one second blockchain, and obtain, from the routing management module, routing address information of a node in each second blockchain; the uplink management module is further configured to encapsulate the transaction request based on the identity certificate key information of each second blockchain; the uplink management module is further configured to write the encapsulated transaction request into the corresponding second blockchain based on the routing address information of the node in each second blockchain.
In an optional design, the data management module is further configured to store a transaction record associated with the transaction request.
In an optional design, the agent module is further configured to submit transaction request failure information if the transaction information related to the transaction request is inconsistent with the first transaction information.
In an optional design, the agent module is further configured to obtain a query request input by a user, where the query request indicates the second transaction information; the data management module is configured to, if the pre-stored transaction record includes a second transaction record, obtain at least one block chain related to the second transaction record; the data management module is further configured to read the second transaction information from one of the at least one blockchain.
In an optional design, the data management module is further configured to obtain, from the route management module, a node of a blockchain closest to a route in the at least one blockchain; the data management module is further configured to read the second transaction information from a node of the blockchain closest to the route.
In an optional design, the identity management module is further configured to receive identity certificate key information of each of at least two blockchains; the routing management module is further configured to receive routing address information of all nodes in each block chain; the routing management module is further configured to periodically detect connectivity of the routing address information of each node.
In a third aspect, embodiments of the present application provide a data transaction system, the system including at least two blockchains between which cross-chain interaction is not supported, and an electronic device as described in the second aspect or any possible design of the second aspect.
In a fourth aspect, an embodiment of the present application provides an electronic device, including: a processor coupled to a memory for storing a program or instructions which, when executed by the processor, cause the apparatus to perform the method of the first aspect or any possible design of the first aspect.
In a fifth aspect, an embodiment of the present application provides a computer storage medium, where instructions are stored, and when the instructions are executed on a computer, the instructions cause the computer to perform part or all of the steps of the data transaction method in the first aspect and various possible implementations of the first aspect.
In a sixth aspect, the present application provides a computer program product, which when run on a computer, causes the computer to perform some or all of the steps of the data transaction method in the first aspect and various possible implementations of the first aspect.
Drawings
In order to more clearly describe the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments are briefly described below, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic diagram of an exemplary structure of a data transaction system 1 provided in an embodiment of the present application;
FIG. 2A is a method flow diagram of a data trafficking method 100 provided by an embodiment of the application;
FIG. 2B is a flowchart of a method of querying data 200 according to an embodiment of the present disclosure;
FIG. 2C is a method flow diagram of a data storage method 300 provided by an embodiment of the present application;
fig. 3 is an exemplary structural diagram of the electronic device 30 provided in the embodiment of the present application.
Detailed Description
The technical solutions of the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The terminology used in the following examples of the present application is for the purpose of describing alternative embodiments and is not intended to be limiting of the present application. As used in the specification of the present application and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well. It should also be understood that although the terms first, second, etc. may be used in the following embodiments to describe a class of objects, the objects are not limited to these terms. These terms are used to distinguish between particular objects of that class of objects. For example, the terms first, second, etc. may be used in the following embodiments to describe blockchains, but blockchains should not be limited to these terms. The following embodiments may adopt the terms first, second, etc. to describe other class objects in the same way, and are not described herein again.
The embodiment of the application provides a data transaction method, which maintains transaction records related in a service scene under a chain. And further, after a transaction request initiated by a user is obtained, a first transaction record matched with the transaction request is determined according to the transaction record, and then transaction information of the first transaction record is obtained. And if the transaction information of the first transaction record is consistent with the transaction information of the transaction request, initiating a transaction to the corresponding blockchain. Wherein the transaction request may indicate a data writing pattern and a data structure, i.e. the transaction request characterizes one data source. Therefore, according to the technical scheme of the embodiment of the application, under the scene that the block chain cannot carry out data interaction, historical transaction information matched with the transaction request can be obtained through the transaction records maintained under the line, and then corresponding transactions are executed under the condition that the credibility of the data source is ensured, so that the consistency of the same service data in different block chains can be ensured, and the credibility of the system is further ensured.
The "service scenario" related to the embodiment of the present application refers to a transaction scenario of a specific service, for example, a scenario of copyright transaction, a scenario of security transaction, a scenario of patent transaction, and the like. A service scenario may correspond to a blockchain network, for example, a copyright bureau may form a blockchain network with a plurality of copyright owners. In some embodiments, the blockchain network of a business scenario is also referred to as the data trafficking system of the business scenario.
The embodiments of the present application refer to "transaction request" in which an item of data is written to a blockchain by a data write mode. The data writing modes corresponding to different types of transactions are different, and the structures of the written data are different. Based on this, the transaction request may also be considered as a data source for the blockchain.
In some embodiments, a "transaction record matching a transaction request" may refer to a transaction record that is identical to the data writing pattern of the transaction request. In other embodiments, the "transaction record matching the transaction request" may refer to the same transaction record as the preset content in the data writing pattern of the transaction request.
Fig. 1 shows a schematic structural diagram of a data transaction system 1. The data trafficking system 1 may include an intermediate device 10 and at least two blockchains 20. The intermediate apparatus 10 may include an agent module 11, an identity management module 12, a route management module 13, a data management module 14, and a uplink management module 15. The blockchain 21 and the blockchain 22 of the at least two blockchains 20 do not support inter-chain interaction, for example, and both the blockchain 21 and the blockchain 22 can perform data interaction with the intermediate device 10. The blockchain 21 and the blockchain 22 may each include a plurality of nodes, and each node stores therein service data.
It is to be understood that the structure illustrated in fig. 1 does not constitute a specific limitation to the data transaction system 1 in the embodiment of the present application. Alternatively, in other embodiments, the data transaction system 1 according to the embodiment of the present application may include more or less components than those shown, or combine some components, or split some components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
The agent module 11 may be configured to implement an information interaction function of the intermediate device 10 with each of the at least two blockchains 20, and may call other modules in the intermediate device 10 to perform the functions of the corresponding modules.
The identity management module 12 may be configured to obtain the identity certificate key information of each blockchain illustrated in fig. 1, so as to provide the identity certificate key information of the corresponding blockchain when the agent module 11 and the uplink management module 15 perform information interaction with each blockchain.
The route management module 13 may be configured to maintain the route address information of the node in each blockchain illustrated in fig. 1, so as to provide the route address information of the corresponding node when the agent module 11 and the uplink management module 15 perform information interaction with the nodes of the blockchain.
The data management module 14 may be used to maintain a transaction record for each transaction in the data transaction system 1. The transaction record may include information such as a blockchain identifier, a node identifier, a transaction mode, etc. associated with the transaction. The data management module 14 may also be configured to obtain a user-triggered transaction request and to detect whether data associated with the transaction request is authentic based on the transaction record. Optionally, the data management module 14 may maintain transaction information of the business data in the form of a database. The database may be, for example, a relational database management system (mySQL).
The uplink management module 15 may be configured to, in response to the triggering of the agent module 11, obtain, from the identity management module 12, the identity certificate key information of the blockchain corresponding to the transaction request and the routing address information of the node corresponding to the transaction request, so as to send the transaction request to the node of the requested blockchain, so as to write data related to the transaction request into the corresponding node.
It is to be understood that the embodiments of the present application are also applicable to future-oriented blockchain techniques. The data transaction system and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the present application, and do not constitute a limitation to the technical solution provided by the present application, and it can be known by those skilled in the art that the technical solution provided by the present application is also applicable to similar technical problems with the evolution of the blockchain technology and the appearance of new service scenarios.
Fig. 2A illustrates a data transaction method 100 (hereinafter referred to as method 100). The method 100 is applied to the intermediate apparatus 10 in fig. 1, and includes: a transaction request input by a user is obtained (S101). Whether the transaction record contains the first transaction record matched with the transaction request is judged (S102). If the transaction record includes a first transaction record matching the transaction request, first transaction information is obtained from a first blockchain associated with the first transaction record (S103), and whether the transaction information associated with the transaction request is consistent with the first transaction information is determined (S104). If the transaction record does not include the first transaction record matching the transaction request, the transaction request is submitted to at least one second blockchain associated with the transaction request (S105). If the transaction information related to the transaction request is consistent with the first transaction information, the operation of S105 is executed. If the transaction information related to the transaction request is inconsistent with the first transaction information, transaction request failure information is submitted (S106).
The transaction request may indicate a blockchain to which data is written, and the transaction request may indicate to write data into at least one blockchain, which is not limited by the technical solution of the embodiment of the present application.
In connection with the data transaction system 1 shown in fig. 1, after obtaining the transaction request input by the user, the data management module 14 may query whether there is a transaction record matching the transaction request from the transaction records maintained in advance. The data management module 14 may, for example, query transaction records that have the same data write pattern as the transaction request according to the data write pattern. After querying that the first transaction record is a transaction record matching the transaction request, the data management module 14 may obtain information such as a first blockchain identifier, a transaction identifier, and a node identity associated with the first transaction record. Thereafter, the data management module 14 obtains the identity certificate key information of the first block chain from the identity management module 12, and obtains the routing address information related to the node identity of the first block chain from the routing management module 13. And then, initiating a query request to the first blockchain to obtain first transaction information corresponding to the first transaction record. Therefore, the situations that the transaction records of the data management module have errors and the transaction records of the data management module and the blockchain are not updated synchronously can be avoided.
Illustratively, the first transaction information may include, for example, data structure information of the first transaction data. After obtaining the first transaction information, the data management module 14 may detect whether the data structure information of the first transaction information is consistent with the structure information of the data to be written in the transaction request. When the data structure information of the first transaction information is consistent with the structure information of the data to be written in the transaction request, it can be stated that the data to be written in the transaction request is authentic, that is, the data is not forged, so that it can be determined that the data source related to the transaction request is authentic. Furthermore, the uplink management module 15 may obtain at least one second block chain related to the transaction request, obtain the identity certificate key information of each second block chain from the identity management module 12, and obtain the routing address information related to the node identity of each second block chain from the routing management module 13, encapsulate the transaction request according to the encapsulation method corresponding to the second block chain, and then write the encapsulated transaction request into the second block chain. Further, the data management module 14 stores a transaction record corresponding to the transaction request.
In other embodiments, if the data management module 14 does not query the same transaction record as the data writing mode of the transaction request, it may be considered that the transaction request is to write data into the block chain in this mode for the first time, and the written data may be trusted by default. The uplink management module 15 then triggers the transaction request.
In one possible implementation, the data transaction method may be a data query method. FIG. 2B illustrates a data query method 200 (hereinafter method 200). The method 200 comprises the following steps: a query request input by a user is obtained, the query request indicating second transaction information. And judging whether the transaction record contains a second transaction record matched with the second transaction information. If the transaction record contains a second transaction record, at least one block chain related to the second transaction record is obtained, and second transaction information is read from the at least one block chain. And if the transaction record does not contain the second transaction record, submitting query failure information.
In the method 200, the data management module 14 determines whether the transaction record includes a second transaction record, and when the transaction record includes the second transaction record, obtains the identity certificate key information of the block chain related to the second transaction record from the identity management module 12, and obtains the routing address information related to the node identity related to the second transaction record from the routing management module 13, so as to read the second transaction information.
In some embodiments, if the blockchain associated with the second transaction record includes at least two blockchains, the data management module 14 may determine a node of a closest blockchain of the at least two blockchains to route, and further, read the second transaction information from the node of the closest blockchain.
In other embodiments, when the database in the data management module 14 contains the second transaction information, the data management module 14 may read the second transaction information from the database.
Therefore, the embodiment of the application maintains the transaction records on different block chains through the offline database, and is more convenient for transaction data query.
It is noted that intermediary 10 may also pre-store data associated with the blockchain prior to performing methods 100 and 200. Fig. 2C illustrates a data storage method 300 (hereinafter referred to as method 300). The method 300 includes: the intermediate device 10 may also receive identity certificate key information for each of the at least two blockchains 20, as well as routing address information for all nodes in each blockchain. Thereafter, the intermediate device 10 periodically detects the connectivity of each node routing address information.
Illustratively, after deployment of the blockchain and the nodes of the blockchain, the blockchain may register the identity certificate key information to the identity management module 12, the routing address information of each node to the routing management module 13, and each transaction record to the data management module 14.
In addition, the route management module 13 may periodically send a heartbeat packet to each node according to the route address information, for example, to determine the connectivity of each node.
It is understood that the methods 100 to 300 are all schematically described and do not limit the embodiments of the present application. In the embodiment of the present application, information stored in the data management module may be flexibly deployed based on different service scenarios, which is not limited in the embodiment of the present application.
In summary, by adopting the implementation manner of the embodiment of the present application, the intermediate device is deployed in the blockchain network, and maintains the transaction records related to the service scene. Furthermore, after the transaction request initiated by the user is obtained, the intermediate device searches the transaction record matched with the transaction request, and then detects whether the transaction information of the corresponding transaction record is consistent with the transaction information of the transaction request. And if the transaction information of the transaction record is consistent with the transaction information of the transaction request, initiating a transaction to the corresponding blockchain. Therefore, under the scene that the block chain cannot carry out data interaction, historical transaction information matched with the transaction request can be obtained through the transaction records maintained under the line, and then corresponding transactions are executed under the condition that the credibility of the data source is ensured, so that the consistency of the same service data in different block chains can be ensured, and the credibility of the system is further ensured.
Corresponding to the method provided by the above method embodiment, the embodiment of the present application further provides a corresponding intermediate device, which includes a module for executing the above embodiment. The module may be software, hardware, or a combination of software and hardware.
Fig. 3 shows a schematic structural diagram of an electronic device 30. The electronic device 30 may be an intermediate device, or may be a chip, a chip system, or a processor that supports the intermediate device to implement the method. The apparatus may be configured to implement the method described in the foregoing method embodiment, and specific reference may be made to the description in the foregoing method embodiment.
The electronic device 30 may include one or more processors 301, where the processors 301 may also be referred to as processing units and may implement certain control functions. The processor 301 may be a general purpose processor or a special purpose processor, etc. The processor 301 may execute a software program, for example, and process data of the software program.
In an alternative design, the processor 301 may also store instructions and/or data 303, and the instructions and/or data 303 may be executed by the processor, so that the electronic device 30 performs the method described in the above method embodiment.
In an alternative design, processor 301 may include a transceiver unit to perform receive and transmit functions. The transceiving unit may be, for example, a transceiving circuit, or an interface circuit. The transceiver circuitry, interface or interface circuitry for implementing the receive and transmit functions may be separate or integrated. The transceiver circuit, the interface circuit or the interface circuit may be used for reading and writing code/data, or the transceiver circuit, the interface circuit or the interface circuit may be used for transmitting or transferring signals.
In yet another possible design, the electronic device 30 may include circuitry that may implement the functionality of transmitting or receiving or communicating in the foregoing method embodiments.
Optionally, the electronic device 30 may include one or more memories 302, on which instructions 304 may be stored, and the instructions may be executed on the processor, so that the electronic device 30 performs the method described in the above method embodiment. Optionally, the memory may further store the above blockchain information and transaction information. Optionally, instructions and/or data may also be stored in the processor. The processor and the memory may be provided separately or may be integrated together. For example, the correspondence described in the above method embodiments may be stored in a memory or in a processor.
Optionally, the electronic device 30 may further include a transceiver 305 and/or an antenna 306. The processor 301, which may be referred to as a processing unit, controls the electronic device 30. The transceiver 305 may be referred to as a transceiver unit, a transceiver circuit, a transceiver device, a transceiver module, or the like, and is used for implementing a transceiving function.
Optionally, the electronic device 30 in the embodiment of the present application may be configured to execute the method described in fig. 2A, fig. 2B, or fig. 2C in the embodiment of the present application, or may be configured to execute a method in which the methods described in the above three or more diagrams are combined with each other.
The processors and transceivers described herein may be implemented on Integrated Circuits (ICs), analog ICs, Radio Frequency Integrated Circuits (RFICs), mixed signal ICs, Application Specific Integrated Circuits (ASICs), Printed Circuit Boards (PCBs), electronic devices, and the like. The processor and transceiver may also be fabricated using various IC process technologies, such as Complementary Metal Oxide Semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), Bipolar Junction Transistor (BJT), Bipolar CMOS (bicmos), silicon germanium (SiGe), gallium arsenide (GaAs), and the like.
The scope of the electronic apparatus in the description of the above embodiment is not limited thereto, and the structure of the apparatus may not be limited by fig. 3. The electronic device may be a stand-alone device or may be part of a larger device. For example, the electronic device may be:
(1) a stand-alone integrated circuit IC, or chip, or system-on-chip or subsystem;
(2) having a set of one or more ICs, which may optionally also include storage means for storing data and/or instructions;
(3) an ASIC, such as a modem (MSM);
(4) a module that may be embedded within other devices;
(5) receivers, terminals, smart terminals, cellular phones, wireless devices, handsets, mobile units, in-vehicle devices, network devices, cloud devices, artificial intelligence devices, machine devices, home devices, medical devices, industrial devices, and the like;
(5) others, and so forth.
In a specific implementation, corresponding to an electronic device, an embodiment of the present application further provides a computer storage medium, where the computer storage medium disposed in the electronic device may store a program, and when the program is executed, part or all of the steps in each embodiment of the method provided in fig. 2A to 2C may be implemented. The storage medium in the electronic device may be a magnetic disk, an optical disk, a read-only memory (ROM), a Random Access Memory (RAM), or the like.
It should be understood that, in the various embodiments of the present application, the size of the serial number of each process does not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic thereof, and should not constitute any limitation to the implementation process of the embodiments.
It is understood that some optional features in the embodiments of the present application may be implemented independently without depending on other features in some scenarios, such as a currently-based solution, to solve corresponding technical problems and achieve corresponding effects, or may be combined with other features according to requirements in some scenarios. Accordingly, the apparatuses provided in the embodiments of the present application may also implement these features or functions, which are not described herein again.
It is understood that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.
The solution described in the present application can be implemented in various ways. For example, these techniques may be implemented in hardware, software, or a combination of hardware and software. For a hardware implementation, the processing units used to perform these techniques at a communication device (e.g., a base station, terminal, network entity, or chip) may be implemented in one or more general-purpose processors, DSPs, digital signal processing devices, ASICs, programmable logic devices, FPGAs, or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combinations of the above. A general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.
Reference in the present application to an element using the singular is intended to mean "one or more" rather than "one and only one" unless specifically stated otherwise. In the present application, unless otherwise specified, "at least one" is intended to mean "one or more" and "a plurality" is intended to mean "two or more".
The term "and/or" herein is merely an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A can be singular or plural, and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The values of the information in each table in the present application are only examples, and may be configured to other values, and the present application is not limited thereto. When the correspondence between the information and each parameter is configured, it is not always necessary to configure all the correspondences indicated in each table. For example, in the table in the present application, the correspondence shown in some rows may not be configured. For another example, appropriate modification adjustments, such as splitting, merging, etc., can be made based on the above tables. The names of the parameters in the tables may be other names understandable by the communication device, and the values or the expression of the parameters may be other values or expressions understandable by the communication device. When the above tables are implemented, other data structures may be used, for example, arrays, queues, containers, stacks, linear tables, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables may be used.
Predefinition in this application may be understood as defining, predefining, storing, pre-negotiating, pre-configuring, curing, or pre-firing.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (16)

1. A method of data transaction, the method comprising:
obtaining a transaction request input by a user;
inquiring a first transaction record matched with the transaction request from pre-stored transaction records;
obtaining first transaction information from a first blockchain associated with the first transaction record;
and if the transaction information related to the transaction request is consistent with the first transaction information, submitting the transaction request to at least one second blockchain related to the transaction request.
2. The method of claim 1, wherein submitting the transaction request to at least one second blockchain associated with the transaction request comprises:
obtaining identity certificate key information of each second blockchain in the at least one second blockchain and routing address information of nodes in each second blockchain;
packaging the transaction request based on the identity certificate key information of each second blockchain;
and writing the packaged transaction request into the corresponding second blockchain based on the routing address information of the nodes in each second blockchain.
3. The method of claim 1, after submitting the transaction request to at least one second blockchain associated with the transaction request, further comprising:
storing a transaction record associated with the transaction request.
4. The method of claim 1, further comprising:
and if the pre-stored transaction record does not comprise the first transaction record matched with the transaction request, submitting the transaction request to at least one second blockchain related to the transaction request.
5. The method of claim 1, further comprising:
and if the transaction information related to the transaction request is inconsistent with the first transaction information, submitting transaction request failure information.
6. The method of claim 1, further comprising:
obtaining a query request input by a user, wherein the query request indicates second transaction information;
if the pre-stored transaction record comprises a second transaction record, obtaining at least one block chain related to the second transaction record;
reading the second transaction information from one of the at least one blockchain.
7. The method of claim 6, wherein reading the second transaction information from one of the at least one blockchain comprises:
obtaining a node of a block chain with a nearest route in the at least one block chain;
reading the second transaction information from a node of the blockchain closest to the route.
8. The method of any one of claims 1-7, further comprising:
receiving identity certificate key information and transaction records of each block chain in at least two block chains, and routing address information of all nodes in each block chain;
and periodically detecting the connectivity of the routing address information of each node.
9. A data transaction device is characterized in that the device comprises an agent module, a data management module and a uplink management module, wherein,
the agent module is used for obtaining a transaction request input by a user;
the data management module is used for inquiring a first transaction record matched with the transaction request from prestored transaction records;
the data management module is further used for obtaining first transaction information from a first block chain related to the first transaction record;
and the uplink management module is used for submitting the transaction request to at least one second block chain related to the transaction request if the transaction information related to the transaction request is consistent with the first transaction information.
10. The apparatus of claim 9, wherein the apparatus further comprises an identity management module and a route management module, wherein,
the identity management module is used for storing the identity certificate key information of the block chain;
the routing management module is used for storing the routing address information of the nodes in the block chain;
the uplink management module is further configured to obtain, from the identity management module, identity certificate key information of each second blockchain in the at least one second blockchain, and obtain, from the routing management module, routing address information of a node in each second blockchain;
the uplink management module is further configured to encapsulate the transaction request based on the identity certificate key information of each second blockchain;
the uplink management module is further configured to write the encapsulated transaction request into the corresponding second blockchain based on the routing address information of the node in each second blockchain.
11. The apparatus of claim 9,
the data management module is also used for storing the transaction record related to the transaction request.
12. The apparatus of claim 9,
the agent module is further used for submitting transaction request failure information if the transaction information related to the transaction request is inconsistent with the first transaction information.
13. The apparatus of claim 9,
the agent module is further used for obtaining a query request input by a user, wherein the query request indicates second transaction information;
the data management module is configured to, if the pre-stored transaction record includes a second transaction record, obtain at least one block chain related to the second transaction record;
the data management module is further configured to read the second transaction information from one of the at least one blockchain.
14. The apparatus of claim 13,
the data management module is further configured to obtain, from the route management module, a node of a blockchain closest to a route in the at least one blockchain;
the data management module is further configured to read the second transaction information from a node of the blockchain closest to the route.
15. The apparatus as recited in claim 10,
the identity management module is further configured to receive identity certificate key information of each of the at least two block chains;
the routing management module is further configured to receive routing address information of all nodes in each block chain;
the routing management module is further configured to periodically detect connectivity of the routing address information of each node.
16. A data transaction system, the system comprising at least two blockchains between which cross-chain interaction is not supported and an electronic device as claimed in any one of claims 9 to 15.
CN202110192805.0A 2021-02-20 2021-02-20 Data transaction method, equipment and system Pending CN115002104A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110192805.0A CN115002104A (en) 2021-02-20 2021-02-20 Data transaction method, equipment and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110192805.0A CN115002104A (en) 2021-02-20 2021-02-20 Data transaction method, equipment and system

Publications (1)

Publication Number Publication Date
CN115002104A true CN115002104A (en) 2022-09-02

Family

ID=83018788

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110192805.0A Pending CN115002104A (en) 2021-02-20 2021-02-20 Data transaction method, equipment and system

Country Status (1)

Country Link
CN (1) CN115002104A (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107832626A (en) * 2017-11-30 2018-03-23 中国人民解放军国防科技大学 Structured data right confirming method oriented to data circulation
CN108846752A (en) * 2018-06-06 2018-11-20 北京京东金融科技控股有限公司 Data processing method, system, block platform chain and readable storage medium storing program for executing
CN110222529A (en) * 2019-05-21 2019-09-10 平安普惠企业管理有限公司 Assets management method, electronic equipment and computer storage medium based on alliance's chain
US20190311357A1 (en) * 2018-04-04 2019-10-10 Vijay Madisetti Method and System for Exchange of Value or Tokens Between Blockchain Networks
EP3605376A1 (en) * 2018-08-03 2020-02-05 Siemens Healthcare GmbH Blockchain-based distribution of medical data records
CN110941647A (en) * 2019-11-11 2020-03-31 华中科技大学 Block chain cross-chain interaction method and system based on DAG
CN111047318A (en) * 2019-09-16 2020-04-21 腾讯科技（深圳）有限公司 Transaction record storage method and device and computer equipment

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107832626A (en) * 2017-11-30 2018-03-23 中国人民解放军国防科技大学 Structured data right confirming method oriented to data circulation
US20190311357A1 (en) * 2018-04-04 2019-10-10 Vijay Madisetti Method and System for Exchange of Value or Tokens Between Blockchain Networks
US20200151716A1 (en) * 2018-04-04 2020-05-14 Vijay Madisetti Method and System for Exchange of Value or Tokens Between Blockchain Networks
CN108846752A (en) * 2018-06-06 2018-11-20 北京京东金融科技控股有限公司 Data processing method, system, block platform chain and readable storage medium storing program for executing
EP3605376A1 (en) * 2018-08-03 2020-02-05 Siemens Healthcare GmbH Blockchain-based distribution of medical data records
CN110222529A (en) * 2019-05-21 2019-09-10 平安普惠企业管理有限公司 Assets management method, electronic equipment and computer storage medium based on alliance's chain
CN111047318A (en) * 2019-09-16 2020-04-21 腾讯科技（深圳）有限公司 Transaction record storage method and device and computer equipment
CN110941647A (en) * 2019-11-11 2020-03-31 华中科技大学 Block chain cross-chain interaction method and system based on DAG

Similar Documents

Publication Publication Date Title
CN112099972B (en) Office file processing method, device and equipment based on RPA robot
CN111651467B (en) Block chain node interface issuing and calling method and device
CN112738881B (en) Network registration method and device
US20220272171A1 (en) Method and apparatus for subscribing to resource
CN115237952A (en) Method and device for realizing dynamic desensitization of application system based on JDBC driver agent
CN112445841B (en) Account query method, device, system, server and medium
CN115002104A (en) Data transaction method, equipment and system
CN110806979A (en) Interface return value checking method, device, equipment and storage medium
CN108563514B (en) Method for accessing application configuration service, application and electronic equipment
US20030236744A1 (en) Connection information management system for managing connection information used in communications between IC cards
CN113259437B (en) Method and device for determining vehicle network protocol and storage medium
US20170353818A1 (en) Method for deleting notification resource, and common service entity
CN112068899A (en) Plug-in loading method and device, electronic equipment and storage medium
CN111917572B (en) Transaction request processing method and device, electronic equipment and readable storage medium
CN111641580B (en) Wind power plant service calling method, device, equipment and medium
CN116501448B (en) Container packaging method and device applied to multiple virtual machines
CN112748981B (en) Processing method and device for software mirror image of virtual network function
CN114567644B (en) Data synchronization method and device and electronic equipment
CN117850753B (en) Method, device, equipment and medium for generating interface code based on someip matrix
WO2022116081A1 (en) Methods, apparatuses, and computer readable media for binding and de-binding neighboring apparatuses
WO2023231038A1 (en) Ranging method and apparatus
CN111131414B (en) Back-end platform, service calling method, first service module and server
CN117424938A (en) TSCTSF service calling method, TSCTSF entity, communication system and storage medium
CN115904537A (en) Switch management method, system, computer device and storage medium
CN117424939A (en) Method for calling TSCTSF service, NEF entity, communication system and storage medium

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