CN113515772A - Method for querying log information uplink by database based on RPCA (resilient packet access) consensus mechanism - Google Patents
Method for querying log information uplink by database based on RPCA (resilient packet access) consensus mechanism Download PDFInfo
- Publication number
- CN113515772A CN113515772A CN202110425803.1A CN202110425803A CN113515772A CN 113515772 A CN113515772 A CN 113515772A CN 202110425803 A CN202110425803 A CN 202110425803A CN 113515772 A CN113515772 A CN 113515772A
- Authority
- CN
- China
- Prior art keywords
- query
- transaction
- database
- processing
- data
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000007246 mechanism Effects 0.000 title claims abstract description 15
- 238000012545 processing Methods 0.000 claims abstract description 34
- 238000002360 preparation method Methods 0.000 claims description 6
- 238000003672 processing method Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 claims description 5
- 238000013475 authorization Methods 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000009191 jumping Effects 0.000 claims description 3
- 239000007787 solid Substances 0.000 abstract description 2
- 238000005516 engineering process Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/217—Database tuning
-
- 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/242—Query formulation
- G06F16/2433—Query languages
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Bioethics (AREA)
- Quality & Reliability (AREA)
- Health & Medical Sciences (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method for querying log information uplink by a database based on an RPCA (resilient packet access) consensus mechanism, belonging to the technical field of block chains. The invention defines a new transaction type for processing the uplink operation of the query log; secondly, defining an access class which can be compatible with the on-chain database and the off-chain database and is used for checking the validity of the query statement; and finally, storing the query log on a block chain network in a mode of first consensus and then query, and simultaneously returning the queried actual data. By the method provided by the invention, the commonly recognized actual database query logs can be stored in the block chain, and more solid guarantee is provided for the non-tampering property, the auditing property and the openness of the traditional database.
Description
Technical Field
The invention relates to the technical field of block chains, in particular to a method for querying an uplink of log information by a database based on an RPCA (resilient packet access) consensus mechanism.
Background
The block chain technology is developed vigorously, and the block chain technology has already entered the third generation block chain technology development stage. Blockchain technology moves from the financial stage into the multi-industry development stage. In the process, many new demands are made, and new solutions are called. In a medical scene, storing patient information through logs on and off a chain is a generally accepted method, and the method puts logs of a traditional database into a block chain network, so that original data of a hospital does not need to be greatly changed while the non-tamper property, auditability and openness of a high system are improved.
From a demand perspective, due to financial scenario limitations, there is already a blockchain network and there is no need to chain up query logs. The inquiry is to inquire the local account book information, because the copy of each node in the network is the same and all the transaction records are public, that is, each account can inquire the transaction information of all other accounts. However, in the medical scenario, the information of the patient is extremely sensitive, and a complete access record is required, so that it is necessary to put the query log into the block chain.
From the technical point of view, the addition, deletion, and modification of transaction transactions (hereinafter referred to as transactions) in the existing blockchain system are recorded on the blockchain. The operations of inserting, deleting and modifying belong to writing data into the block chain network, and only a small amount of information is needed, such as success or failure, the number of affected data bases and the like. Different queries involve reading data from the blockchain network, and writing data (query conditions, etc.) into the blockchain. However, the currently-seen blockchain network is a blockchain ledger book for querying the node, and has no function of putting any query log information into a blockchain log.
The ripper (Ripple) is the first open payment network in the world, and the ripper blockchain network is a validated excellent golden blockchain network, and the Consensus mechanism rpca (Ripple Consensus algorithm) used by the ripper blockchain network is a low-delay Consensus mechanism besides PBFT (practical byzantine fault-tolerant algorithm). In blockchain networks in medical scenarios, RPCA has greater flexibility than PBFT. Based on the RPCA consensus protocol, we propose a specific method for data query log information uplink to solve the problems occurring at present.
Disclosure of Invention
In view of the above-mentioned drawbacks and deficiencies of the prior art, the present invention provides a method for querying log uplink in a database based on RPCA consensus protocol. The method carries out innovative reconstruction on the flow of the block chain network under the RPCA protocol mechanism, so that the block chain network can realize the chain link of the inquiry log.
In order to implement the function of data query and chaining the logs, new commands, transaction types and related processing classes need to be defined. In this scenario, not the patient's data but the log of the conventional database is stored in the blockchain, and the blockchain log database and the patient database are referred to as D respectively hereinlogAnd Ddata。
The invention firstly defines a new transaction type for processing the operation of chaining in the query log; secondly, defining access classes compatible with the on-chain database and the off-chain database, and checking the validity of the query statement; and finally, storing the query log on a block chain network in a mode of first consensus and then query, and simultaneously returning the queried actual data.
Further, the method comprises the following specific steps:
step1, defining a new transaction type in the Rake wave network, and processing the new type of transaction; specifically, a transaction type RecordQueryLog is defined and used for processing an uplink of the query log;
step2, define transaction convert to SQL statement query processing class, named Tx2SQLOp, for compatible read-write access database DlogAnd database Ddata(ii) a The definition method analyzes the affairs into database operation; the definition method checks the query condition;
step3, define (remote procedure call) RPC service command r _ get _ on _ chain, is a client operation that can be used to chain logs while data is being queried; adding an r _ get _ on _ chain command in an RPC command list, and adding a processing method, namely, DoGetRecordOnChain, pointed by the command;
step4, process the data query by using the processing method of r _ get _ on _ chain command, DoGetRecordOnChain, and store the database query log information into the zone chain while processing the data query.
Further, the specific steps of Step1 are as follows:
step1.1, defining a method for processing 'preparation for takeoff', and checking whether relevant fields including a data owner, a database table to be operated and query conditions are provided in a transaction; filling a transaction sequence number and a previous account book sequence number;
step1.2, defining a method for processing 'declaration preparation', and checking whether an account name is legal or not and whether a database table name is legal or not;
step1.3, defining a method for processing 'application transaction', generating Hash for the transaction, and using the Hash as a unique mark of the subsequent transaction; calling the currently opened account book and updating the relevant state;
step1.4, define the processing class of calling Step2, proceed database DdataThe trial SQL statement is executed to obtain the result of whether the execution is successful or not.
Further, the specific steps of Step4 are as follows:
step4.1, checking the identity of a caller; in a medical scene, the authority needs to be strictly controlled, a patient can only inquire the record of the patient, and only an authorized doctor can inquire the record of the corresponding patient; this step requires ensuring that the sender's account and key have the records required for authorization queries;
step4.2, according to the transaction of Step1, after verifying that the inquiry log information passes, submitting the transaction to an RPCA (resilient packet access) consensus mechanism for consensus processing, wherein the transaction comprises the serialization information of the inquiry log besides the normal transaction meta information, and the information is sent to a consensus network to wait for consensus to be achieved; after the consensus is successful, the transaction is stored in the block chain database, and the next step is carried out; otherwise, jumping to Step4.6;
step4.3, deserializing the uplink transaction, and extracting the content information of the transaction; here, the query condition information of the transaction type RecordQueryLog is defined;
step4.4, analyzing the query log information, organizing the query log information into query SQL statements, calling a global database to connect and query data;
step4.5, inquiring to obtain a result, and sorting the result into a format suitable for RPC network transmission;
step4.6, adding Hash check of a return result, and organizing the return result of RPC; if the data is inquired, returning the corresponding data; otherwise, returning error information and error type.
The invention has the beneficial effects that:
the invention firstly defines a new transaction type for processing the operation of chain link in the query log; secondly, defining an access class which can be compatible with the on-chain database and the off-chain database to check the validity of the query statement; and finally, storing the query log on a block chain network in a mode of first consensus and then query, and simultaneously returning the queried actual data. By the method provided by the invention, the commonly recognized patient database query logs can be stored into the block chain, and more solid guarantee is provided for the non-tamper property, the auditability and the openness of the traditional database.
Drawings
Other features, objects, and advantages of the present application will become apparent upon reading the following detailed description and upon reference to the drawings in which:
FIG. 1 is a process of a Rayleigh-Blockchain network node serving RPC requests in accordance with the present invention;
FIG. 2 is a flowchart of a method for processing a chain in a query log according to the present invention, DOGetRecordOnChain;
FIG. 3 is a diagram illustrating the procedure of checking the uplink information for the Tx2SQLOp according to the present invention;
FIG. 4 is an exemplary query RPC request in accordance with the present invention;
FIG. 5 is an RPC response to an exemplary query of the present invention.
Detailed Description
Example 1: as shown in fig. 1-3, a method for querying uplink of log information in a database based on an RPCA consensus mechanism first defines a new transaction type for processing uplink operation of query log; secondly, defining access classes compatible with the on-chain database and the off-chain database, and checking the validity of the query statement; and finally, storing the query log on a block chain network in a mode of first consensus and then query, and simultaneously returning the queried actual data.
Further, the method comprises the following specific steps:
step1, defining a new transaction type in the Rake wave network, and processing the new type of transaction; specifically, a transaction type RecordQueryLog is defined and used for processing an uplink of the query log;
step1.1, defining a method for processing 'preparation for takeoff', and checking whether relevant fields including a data owner, a database table to be operated and query conditions are provided in a transaction; filling a transaction sequence number and a previous account book sequence number;
step1.2, defining a method for processing 'declaration preparation', and checking whether an account name is legal or not and whether a database table name is legal or not;
step1.3, defining a method for processing 'application transaction', generating Hash for the transaction, and using the Hash as a unique mark of the subsequent transaction; calling the currently opened account book and updating the relevant state;
step1.4, define the processing class of calling Step2, proceed database DdataThe trial SQL statement is executed to obtain the result of whether the execution is successful or not.
Step2, define transaction convert to SQL statement query processing class, named Tx2SQLOp, for compatible read-write access database DlogAnd database Ddata(ii) a The definition method analyzes the affairs into database operation; the definition method checks the query condition;
step3, define (remote procedure call) RPC service command r _ get _ on _ chain, is a client operation that can be used to chain logs while data is being queried; adding an r _ get _ on _ chain command in an RPC command list, and adding a processing method, namely, DoGetRecordOnChain, pointed by the command;
step4, process the data query by using the processing method of r _ get _ on _ chain command, DoGetRecordOnChain, and store the database query log information into the zone chain while processing the data query.
Step4.1, checking the identity of a caller; in a medical scene, the authority needs to be strictly controlled, a patient can only inquire the record of the patient, and only an authorized doctor can inquire the record of the corresponding patient; this step requires ensuring that the sender's account and key have the records required for authorization queries;
step4.2, according to the transaction of Step1, after verifying that the inquiry log information passes, submitting the transaction to an RPCA (resilient packet access) consensus mechanism for consensus processing, wherein the transaction comprises the serialization information of the inquiry log besides the normal transaction meta information, and the information is sent to a consensus network to wait for consensus to be achieved; after the consensus is successful, the transaction is stored in the block chain database, and the next step is carried out; otherwise, jumping to Step4.6;
step4.3, deserializing the uplink transaction, and extracting the content information of the transaction; here, the query condition information of the transaction type RecordQueryLog is defined;
step4.4, analyzing the query log information, organizing the query log information into query SQL statements, calling a global database to connect and query data;
step4.5, inquiring to obtain a result, and sorting the result into a format suitable for RPC network transmission;
step4.6, adding Hash check of a return result, and organizing the return result of RPC; if the data is inquired, returning the corresponding data; otherwise, returning error information and error type.
After the steps are defined, the client can call the r _ get _ on _ chain command and input related parameters to perform query. Fig. 4 and 5 show an example of a successful query that accesses a blockchain network using Postman software via RPC mode calls. Fig. 4 shows the RPC request issued, and fig. 5 shows the RPC return result obtained.
In fig. 4, it can be seen that the calling method is r _ get _ on _ chain, and the incoming parameters include participation consensus offline, account private key secret, and transaction content tx _ json. The transaction content comprises a transaction type RecordQueryLog, an Account of a RPC requester, an Account Owner to which the data authority belongs, a lookup table Tables and a lookup condition Raw. The request queries a table with table _ test2 as long as id is 1or name is "alice" and is described in JSON format.In FIG. 5 can It is seen that the correct result is obtainedContaining 0 representing a check diff, representing a check pass; representing the queried data lines meeting the conditions and representing the data arrays; success indicating the status of RPC communication, stands forSuccess is achieved; the tx _ hash representing the serial number of the current uplink transaction represents the hash serial number of the uplink transaction, and the serial number can be used for viewing the details of the transaction by using the original tx command.
While the present invention has been described in detail with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, and various changes can be made without departing from the spirit of the present invention within the knowledge of those skilled in the art.
Claims (4)
1. A method for querying log information uplink by a database based on RPCA (resilient packet access) consensus mechanism is characterized in that: firstly, defining a new transaction type for processing uplink operation of the query log; secondly, defining access classes compatible with the on-chain database and the off-chain database, and checking the validity of the query statement; and finally, storing the query log on a block chain network in a mode of first consensus and then query, and simultaneously returning the queried actual data.
2. The method for database query of uplink log information based on RPCA consensus mechanism as claimed in claim 1, wherein: the method comprises the following specific steps:
step1, defining a new transaction type in the Rake wave network, and processing the new type of transaction; specifically, a transaction type RecordQueryLog is defined and used for processing an uplink of the query log;
step2, define transaction convert to SQL statement query processing class, named Tx2SQLOp, for compatible read-write access database DlogAnd database Ddata(ii) a The definition method analyzes the affairs into database operation; the definition method checks the query condition;
step3, defining Remote Procedure Call (RPC) service command r _ get _ on _ chain, which is a client operation that can be used to chain logs while data is being queried; adding an r _ get _ on _ chain command in an RPC command list, and adding a processing method, namely, DoGetRecordOnChain, pointed by the command;
step4, process the data query by using the processing method of r _ get _ on _ chain command, DoGetRecordOnChain, and store the database query log information into the zone chain while processing the data query.
3. The method for database query of uplink log information based on RPCA consensus mechanism as claimed in claim 2, wherein: the specific steps of Step1 are as follows:
step1.1, defining a method for processing 'preparation for takeoff', and checking whether relevant fields including a data owner, a database table to be operated and query conditions are provided in a transaction; filling a transaction sequence number and a previous account book sequence number;
step1.2, defining a method for processing 'declaration preparation', and checking whether an account name is legal or not and whether a database table name is legal or not;
step1.3, defining a method for processing 'application transaction', generating Hash for the transaction, and using the Hash as a unique mark of the subsequent transaction; calling the currently opened account book and updating the relevant state;
step1.4, define the processing class of calling Step2, proceed database DdataThe trial SQL statement is executed to obtain the result of whether the execution is successful or not.
4. The method for database query of uplink log information based on RPCA consensus mechanism as claimed in claim 2, wherein: the specific steps of Step4 are as follows:
step4.1, checking the identity of a caller; this step requires ensuring that the sender's account and key have the records required for authorization queries;
step4.2, according to the transaction of Step1, after verifying that the inquiry log information passes, submitting the transaction to an RPCA (resilient packet access) consensus mechanism for consensus processing, wherein the transaction comprises the serialization information of the inquiry log besides the normal transaction meta information, and the information is sent to a consensus network to wait for consensus to be achieved; after the consensus is successful, the transaction is stored in the block chain database, and the next step is carried out; otherwise, jumping to Step4.6;
step4.3, deserializing the uplink transaction, and extracting the content information of the transaction; here, the query condition information of the transaction type RecordQueryLog is defined;
step4.4, analyzing the query log information, organizing the query log information into query SQL statements, calling a global database to connect and query data;
step4.5, inquiring to obtain a result, and sorting the result into a format suitable for RPC network transmission;
step4.6, adding Hash check of a return result, and organizing the return result of RPC; if the data is inquired, returning the corresponding data; otherwise, returning error information and error type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110425803.1A CN113515772B (en) | 2021-04-20 | 2021-04-20 | Database query log information uplink method based on RPCA consensus mechanism |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110425803.1A CN113515772B (en) | 2021-04-20 | 2021-04-20 | Database query log information uplink method based on RPCA consensus mechanism |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113515772A true CN113515772A (en) | 2021-10-19 |
| CN113515772B CN113515772B (en) | 2024-05-28 |
Family
ID=78061466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110425803.1A Active CN113515772B (en) | 2021-04-20 | 2021-04-20 | Database query log information uplink method based on RPCA consensus mechanism |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113515772B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114969214A (en) * | 2021-12-30 | 2022-08-30 | 昆明理工大学 | Relational database tamper-proofing method based on super book Fabric |
| CN115051807A (en) * | 2022-06-02 | 2022-09-13 | 昆明理工大学 | Zero-knowledge identity authentication method based on super book Fabric |
| CN115062094A (en) * | 2021-12-30 | 2022-09-16 | 昆明理工大学 | Fabric-based relational database content synchronization method |
| CN115357664A (en) * | 2022-10-21 | 2022-11-18 | 北京航空航天大学 | Multidirectional trusted system based on block chain and data query method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108390891A (en) * | 2018-03-28 | 2018-08-10 | 电子科技大学天府协同创新中心 | Information protecting method based on privately owned block chain |
| WO2019205860A1 (en) * | 2018-04-27 | 2019-10-31 | 腾讯科技（深圳）有限公司 | Blockchain-based data query method, server and storage medium |
| US20210019728A1 (en) * | 2019-07-18 | 2021-01-21 | Mastercard International Incorporated | Electronic Transaction Method and Device Using a Flexible Transaction Identifier |
-
2021
- 2021-04-20 CN CN202110425803.1A patent/CN113515772B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108390891A (en) * | 2018-03-28 | 2018-08-10 | 电子科技大学天府协同创新中心 | Information protecting method based on privately owned block chain |
| WO2019205860A1 (en) * | 2018-04-27 | 2019-10-31 | 腾讯科技（深圳）有限公司 | Blockchain-based data query method, server and storage medium |
| US20210019728A1 (en) * | 2019-07-18 | 2021-01-21 | Mastercard International Incorporated | Electronic Transaction Method and Device Using a Flexible Transaction Identifier |
Non-Patent Citations (1)
| Title |
|---|
| 吕建富 等: "基于链上链下相结合的日志安全存储与检索", 计算机科学, vol. 47, no. 3, pages 298 - 303 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114969214A (en) * | 2021-12-30 | 2022-08-30 | 昆明理工大学 | Relational database tamper-proofing method based on super book Fabric |
| CN115062094A (en) * | 2021-12-30 | 2022-09-16 | 昆明理工大学 | Fabric-based relational database content synchronization method |
| CN115062094B (en) * | 2021-12-30 | 2024-03-29 | 昆明理工大学 | Relational database content synchronization method based on Fabric |
| CN115051807A (en) * | 2022-06-02 | 2022-09-13 | 昆明理工大学 | Zero-knowledge identity authentication method based on super book Fabric |
| CN115051807B (en) * | 2022-06-02 | 2024-05-24 | 昆明理工大学 | Zero-knowledge identity authentication method based on super account book Fabric |
| CN115357664A (en) * | 2022-10-21 | 2022-11-18 | 北京航空航天大学 | Multidirectional trusted system based on block chain and data query method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113515772B (en) | 2024-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113515772A (en) | Method for querying log information uplink by database based on RPCA (resilient packet access) consensus mechanism | |
| US11811769B2 (en) | Systems, methods, and apparatuses for implementing a declarative, metadata driven, cryptographically verifiable multi-network (multi-tenant) shared ledger | |
| US11824864B2 (en) | Systems, methods, and apparatuses for implementing a declarative and metadata driven blockchain platform using distributed ledger technology (DLT) | |
| US11469886B2 (en) | System or method to implement record level access on metadata driven blockchain using shared secrets and consensus on read | |
| US11743137B2 (en) | Systems, methods, and apparatuses for implementing a metadata driven rules engine on blockchain using distributed ledger technology (DLT) | |
| US11824970B2 (en) | Systems, methods, and apparatuses for implementing user access controls in a metadata driven blockchain operating via distributed ledger technology (DLT) using granular access objects and ALFA/XACML visibility rules | |
| US20220021711A1 (en) | Security Platform and Method for Efficient Access and Discovery | |
| US6377950B1 (en) | Integrated directory services | |
| CA2538506C (en) | A directory system | |
| US7673323B1 (en) | System and method for maintaining security in a distributed computer network | |
| CN109286676B (en) | Electric power data safety information system based on block chain | |
| US8086650B1 (en) | Method for transforming and consolidating fields in log records from logs generated on different operating systems | |
| US8745088B2 (en) | System and method of performing risk analysis using a portal | |
| US20070074158A1 (en) | Method and system for creating reusable software components through a uniform interface | |
| US6751618B1 (en) | Method and apparatus for a web application server to upload multiple files and invoke a script to use the files in a single browser request | |
| CN110765484B (en) | Credit data processing method and electronic equipment | |
| WO2007059534A9 (en) | Distributed transaction history management system | |
| JP2004538574A (en) | Workflow system capable of document version management and document version management method using the same | |
| US20230289782A1 (en) | Smart contract-based data processing | |
| CN111309454B (en) | Method and system for realizing service arrangement data context sharing and management control under micro-service architecture | |
| CN111431867B (en) | Node access method based on block chain BaaS platform | |
| CN114169887A (en) | Reconciliation system based on distributed data nodes | |
| CN113111125A (en) | Business evidence storage method based on block chain | |
| CN112529674A (en) | Tax data service method and system adopting block chain | |
| RU2324974C1 (en) | System of interaction automatic control system databases |
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 |