CN109558064B - Electronic invoice data chain synchronization method, device, medium and electronic equipment - Google Patents
Electronic invoice data chain synchronization method, device, medium and electronic equipment Download PDFInfo
- Publication number
- CN109558064B CN109558064B CN201710875650.4A CN201710875650A CN109558064B CN 109558064 B CN109558064 B CN 109558064B CN 201710875650 A CN201710875650 A CN 201710875650A CN 109558064 B CN109558064 B CN 109558064B
- Authority
- CN
- China
- Prior art keywords
- electronic invoice
- invoice data
- backup
- data chain
- chain
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000002159 abnormal effect Effects 0.000 claims abstract description 82
- 238000012795 verification Methods 0.000 claims description 79
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 6
- 238000011084 recovery Methods 0.000 abstract description 6
- 230000001360 synchronised effect Effects 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 12
- 238000012216 screening Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0626—Reducing size or complexity of storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Human Computer Interaction (AREA)
- Quality & Reliability (AREA)
- Accounting & Taxation (AREA)
- Economics (AREA)
- Finance (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method, a device, a medium and electronic equipment for synchronizing an electronic invoice data chain, which specifically comprise the following steps: each node records data information of an electronic invoice through an electronic invoice data chain, when an abnormal electronic invoice data chain exists in the electronic invoice data chain of the node, a backup electronic invoice data chain is obtained through a business-related node, and a legal backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains, so that the abnormal electronic invoice data chain is synchronized into the legal backup electronic invoice data chain, and the legality of the recovered electronic invoice data chain is ensured while the recovery of the abnormal electronic invoice data chain is realized.
Description
Technical Field
The invention relates to the technical field of application block chains, in particular to a method, a device, a medium and electronic equipment for synchronizing an electronic invoice data chain.
Background
In the prior art, each enterprise generally adopts a database or a folder mode to store expenditure information, income information and the like of the electronic invoice on a computer or cloud equipment, the expenditure information and the income information of the electronic invoice are centrally managed and recorded through the computer or the cloud equipment, the circulation information of the electronic invoice is generally reported to a tax bureau website by each enterprise, and the circulation information of the electronic invoice is centrally managed and recorded by the tax bureau website.
Based on the analysis, the management and recording method for the data information such as the expenditure information, the income information and the circulation information of the electronic invoice in the prior art has lower safety and is not beneficial to disaster backup, moreover, the data information such as the expenditure information, the income information and the circulation information of the electronic invoice is centrally managed and recorded through the computer, the cloud equipment and the tax bureau website, so that the computer, the cloud equipment and the tax bureau website have heavier loads and occupy a large amount of storage space.
Disclosure of Invention
The embodiment of the invention provides a method, a device, a medium and electronic equipment for synchronizing an electronic invoice data chain, which are used for solving the problem that the data information of an electronic invoice is not easy to recover when the data information of the electronic invoice is abnormal in the prior art.
The embodiment of the invention provides the following specific technical scheme:
a synchronization method of an electronic invoice data chain comprises the following steps:
when an abnormal electronic invoice data chain exists in the electronic invoice data chain of the first node, selecting a backup node from all business related nodes of the first node, wherein the electronic invoice data chain is formed by linking all data blocks for recording data information of an electronic invoice;
respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and performing validity verification on the target electronic invoice data chain;
if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification;
and if the target electronic invoice data chain is legal, synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain.
Preferably, the obtaining of the backup electronic invoice data chain of the abnormal electronic invoice data chain from each backup node includes:
determining the data chain type of the abnormal electronic invoice data chain;
and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
Preferably, selecting one backup electronic invoice data chain as the target electronic invoice data chain from all the obtained backup electronic invoice data chains comprises:
selecting the backup electronic invoice data chain with the shortest time interval between the creation time of the last backup data block and the current time from all the obtained backup electronic invoice data chains as a target electronic invoice data chain; or,
and selecting the backup electronic invoice data chain with the largest number of contained backup data blocks from all the obtained backup electronic invoice data chains as a target electronic invoice data chain.
Preferably, the validity verification of the target electronic invoice data chain includes:
selecting a consensus node from all service related nodes of a first node, and indicating each consensus node to carry out validity verification on the last N backup data blocks in a target electronic invoice data chain, wherein N is a positive integer greater than or equal to 1;
if the last N backup data blocks are determined to be legal based on the verification result returned by each common identification node, the target electronic invoice data link is determined to be legal; otherwise, the target electronic invoice data chain is determined to be illegal.
Preferably, after determining that the last N backup data blocks are all legal based on the verification result returned by each consensus node and before determining that the target electronic invoice data link is legal, the method further includes:
and optionally selecting M backup data blocks from all the rest backup data blocks except the last N backup data blocks in the target electronic invoice data chain, and indicating each common identification node to carry out validity verification on the M backup accounting blocks, wherein M is a positive integer greater than or equal to 1.
Preferably, if the M backup data blocks are all determined to be legal, the target electronic invoice data link is determined to be legal.
A synchronization apparatus for an electronic invoice data chain, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for selecting backup nodes from all business related nodes of a first node when an abnormal electronic invoice data chain exists in the electronic invoice data chain of the first node, and the electronic invoice data chain is formed by linking data blocks for recording data information of an electronic invoice;
the verification module is used for respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and performing validity verification on the target electronic invoice data chain; if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification;
and the synchronization module is used for synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain if the target electronic invoice data chain is legal.
Preferably, when the backup electronic invoice data chain of the abnormal electronic invoice data chain is acquired from each backup node, the acquiring module is specifically configured to:
determining the data chain type of the abnormal electronic invoice data chain;
and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
Preferably, when one backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains as the target electronic invoice data chain, the verification module is specifically configured to:
selecting the backup electronic invoice data chain with the shortest time interval between the creation time of the last backup data block and the current time from all the obtained backup electronic invoice data chains as a target electronic invoice data chain; or,
and selecting the backup electronic invoice data chain with the largest number of contained backup data blocks from all the obtained backup electronic invoice data chains as a target electronic invoice data chain.
Preferably, when the validity of the target electronic invoice data chain is verified, the verification module is specifically configured to:
selecting a consensus node from all service related nodes of a first node, and indicating each consensus node to carry out validity verification on the last N backup data blocks in a target electronic invoice data chain, wherein N is a positive integer greater than or equal to 1;
if the last N backup data blocks are determined to be legal based on the verification result returned by each common identification node, the target electronic invoice data link is determined to be legal; otherwise, the target electronic invoice data chain is determined to be illegal.
Preferably, after determining that the last N backup data blocks are all legal based on the verification result returned by each common identification node, before determining that the target electronic invoice data link is legal, the verification module is further configured to:
and optionally selecting M backup data blocks from all the rest backup data blocks except the last N backup data blocks in the target electronic invoice data chain, and indicating each common identification node to carry out validity verification on the M backup accounting blocks, wherein M is a positive integer greater than or equal to 1.
Preferably, the verification module is further configured to: and if the M backup data blocks are determined to be legal, determining that the target electronic invoice data link is legal.
A non-volatile computer storage medium having stored thereon an executable program for execution by a processor to perform the steps of implementing the synchronization method described above.
An electronic device, comprising: a memory, a processor and a computer program stored on the memory, the steps of the synchronization method being implemented when the computer program is executed by the processor.
The embodiment of the invention has the following beneficial effects:
in the embodiment of the invention, the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the centralized management and recording of the data information of the electronic invoice are not needed, a large amount of storage space of a computer, cloud equipment and a tax bureau website is saved, the loads of the computer, the cloud equipment and the tax bureau website are reduced, and the data blocks are not easy to be distorted once being created, so that the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the safety is high, the reliability is strong, in addition, when the electronic invoice data chain is abnormal, a backup electronic invoice data chain can be obtained through business related nodes, and a legal backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains, so that the abnormal electronic invoice data chain is synchronized into the legal backup electronic invoice data chain, therefore, the recovery of the abnormal electronic invoice data chain is realized, and meanwhile, the legality of the recovered electronic invoice data chain is ensured.
Drawings
FIG. 1A is a schematic structural diagram of a distributed node network according to an embodiment of the present invention;
FIG. 1B is a schematic diagram illustrating an overview of a synchronization method for an electronic invoice data chain according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a method for synchronizing an electronic invoice data link according to a second embodiment of the present invention;
FIG. 3 is a functional block diagram of a synchronization apparatus for an electronic invoice data chain according to a third embodiment of the present invention;
fig. 4 is a schematic diagram of a hardware structure of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In order to solve the problem that the data information of the electronic invoice is not easy to recover when the data information of the electronic invoice is abnormal in the prior art, in the embodiment of the invention, each enterprise is linked to a distributed node network as shown in fig. 1A as a node, each node in the distributed node network uses a digital certificate public key as a unique identity (wherein, if the node has a unified social credit code, the digital certificate public key and the unified social credit code can also be used as the unique identity, and the purpose of using the digital certificate public key and the unified social credit code as the identity is that when the digital certificate public key of the node is unavailable, the data information of the node can be recovered by using the unified social credit code, for example, an electronic invoice data link and the like are recovered), selecting backup nodes from all service related nodes of the node, respectively obtaining backup electronic invoice data chains corresponding to the abnormal electronic invoice data chain from each backup node, selecting one backup electronic invoice data chain from all obtained backup electronic invoice data chains as a target electronic invoice data chain, and carrying out validity verification on the target electronic invoice data chain; and if the target electronic invoice data chain is legal, synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain. Thus, the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the data information of the electronic invoice is not managed and recorded in a centralized manner, a large amount of storage space of a computer, cloud equipment and a tax bureau website is saved, the loads of the computer, the cloud equipment and the tax bureau website are reduced, and the data blocks are not easy to be distorted once being created, so that the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the safety is high, the reliability is strong, in addition, when the electronic invoice data chain of any node is abnormal, a backup electronic invoice data chain can be obtained through a service related node, and a legal backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains, so that the abnormal electronic invoice data chain is synchronized into the legal backup electronic invoice data chain, therefore, the recovery of the abnormal electronic invoice data chain is realized, and meanwhile, the legality of the recovered electronic invoice data chain is ensured.
The present invention will be described in detail with reference to specific examples, but it is to be understood that the present invention is not limited to the examples.
Example one
The embodiment of the invention provides a method for synchronizing an electronic invoice data chain, wherein the electronic invoice data chain can be a sales item accounting chain formed by linking various sales item accounting blocks for recording expenditure information of an electronic invoice, an entry accounting chain formed by linking various entry accounting blocks for recording income information of the electronic invoice, an electronic invoice circulation recording chain formed by linking various recording blocks which are created in various circulation stages of the electronic invoice and used for recording circulation information of the electronic invoice in the corresponding circulation stage, and the like. In addition, the execution subject of the synchronization method may be any one node in the distributed node network as shown in fig. 1A, and each node in the distributed node network stores the above-mentioned electronic invoice flow record chain, its own sales item accounting chain and entry accounting chain, and its own sales item accounting chain and entry accounting chain of each service-related node, based on which, as shown in fig. 1, the flow of the synchronization method for the electronic invoice data chain provided by the embodiment of the present invention is as follows:
step 101: when an abnormal electronic invoice data chain exists in the electronic invoice data chain of the first node, a backup node is selected from all business related nodes of the first node, wherein the electronic invoice data chain is formed by linking all data blocks for recording data information of an electronic invoice.
Step 102: and respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and verifying the legality of the target electronic invoice data chain.
Step 103: and if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all the backup electronic invoice data chains which are not subjected to validity verification.
Step 104: and if the target electronic invoice data chain is legal, synchronizing the abnormal electronic invoice data chain as a target.
In the first embodiment of the invention, the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the data information of the electronic invoice is not managed and recorded in a centralized manner any more, a large amount of storage space of a computer, cloud equipment and a tax bureau website is saved, and simultaneously, the load of the computer, the cloud equipment and the tax bureau website is reduced, and the data blocks are not easy to be distorted once being created, so that the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the safety is high, the reliability is strong, in addition, when the electronic invoice data chain is abnormal, the backup electronic invoice data chain can be obtained through business related nodes, and the legal backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains, so that the abnormal electronic invoice data chain is synchronized into the legal backup electronic invoice data chain, therefore, the recovery of the abnormal electronic invoice data chain is realized, and meanwhile, the legality of the recovered electronic invoice data chain is ensured.
Example two
Referring to fig. 2, the method for synchronizing the electronic invoice data chain in the first embodiment of the present invention is described in further detail below, and in the second embodiment of the present invention, the specific process of the method for synchronizing the electronic invoice data chain is as follows:
step 201: and when the abnormal electronic invoice data chain exists in the electronic invoice data chain of the first node, selecting a backup node from all service related nodes of the first node.
In specific implementation, all the second nodes may be selected as backup nodes, or a part of the second nodes may be selected as backup nodes from all the second nodes, and specifically, when a part of the second nodes are selected as backup nodes from all the second nodes, the following manner (where the following operations 1 to 3 are not in sequence) may be adopted, but is not limited to:
and in the operation 1, screening out second nodes meeting a first preset invoicing condition from all second nodes taking the first node as a receiver based on the number of electronic invoices paid out to the first node by the second nodes. For example, the first node screens out, from all second nodes of which the first node serves as a ticket receiver, second nodes of which the number of electronic invoices paid out to the first node is larger than a preset threshold value, or, for example, the first node screens out, from all second nodes of which the first node serves as a ticket receiver, the first N second nodes in the sequence from high to low of the number of electronic invoices paid out to the first node, and so on.
And 2, screening out second nodes meeting a second preset billing condition from all second nodes taking the first node as a billing party based on the billing amount of the first node. For example, the first node screens out, from all second nodes in which the first node serves as the invoicing party, second nodes in which the number of electronic invoices paid out for the second nodes is greater than a preset threshold value, and for example, the first node screens out, from all second nodes in which the first node serves as the invoicing party, the first N second nodes in the order from high to low in the number of electronic invoices paid out for the second nodes, and so on.
And operation 3, screening out the second nodes meeting the preset regional conditions from all the second nodes based on the distance between the second nodes and the first nodes. For example, the first node screens out, from all the second nodes, second nodes whose distance from the first node is greater than a preset threshold, and for example, the first node selects the first N second nodes from all the second nodes in order of decreasing distance from the first node, and so on.
And 4, taking all the screened second nodes as backup nodes.
Step 202: and respectively acquiring the backup electronic invoice data chain of the abnormal electronic invoice data chain from each backup node.
In performing step 202, the following may be employed, but is not limited to: determining the data chain type of the abnormal electronic invoice data chain; and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
Step 203: and selecting one backup electronic invoice data chain as a target electronic invoice data chain from all the obtained backup electronic invoice data chains.
Preferably, in order to ensure that the selected target backup electronic invoice data chain is the latest backup electronic invoice data chain, the following two ways can be adopted when selecting the target electronic invoice data chain, but not limited to:
the first mode is as follows: and selecting the backup electronic invoice data chain with the shortest time interval between the creation time of the last backup data block and the current time from all the obtained backup electronic invoice data chains as a target electronic invoice data chain.
The second mode is as follows: and selecting the backup electronic invoice data chain with the largest number of contained backup data blocks from all the obtained backup electronic invoice data chains as a target electronic invoice data chain.
Step 204: and selecting a consensus node from all service-related nodes of the first node.
In a specific implementation, all the second nodes may be selected as consensus nodes, or a part of the second nodes may be selected as consensus nodes from all the second nodes, and specifically, when a part of the second nodes are selected as consensus nodes from all the second nodes, the following manner (where the following operations 1 to 3 are not in sequence) may be adopted:
and operation 1, screening out second nodes meeting a first preset invoicing condition from all second nodes of which the first nodes serve as the invoicers based on the number of electronic invoices paid from the second nodes to the first nodes. For example, the first node screens out, from all second nodes of which the first node serves as the ticket receiver, second nodes of which the number of electronic invoices paid out to the first node is greater than a preset threshold value, and for example, the first node screens out, from all second nodes of which the first node serves as the ticket receiver, the first N second nodes in the order from high to low of the number of electronic invoices paid out to the first node, and so on.
And 2, screening out second nodes meeting a second preset billing condition from all second nodes taking the first node as a billing party based on the billing amount of the first node. For example, the first node screens out, from all second nodes in which the first node serves as the invoicing party, second nodes in which the number of electronic invoices paid out for the second nodes is greater than a preset threshold value, and for example, the first node screens out, from all second nodes in which the first node serves as the invoicing party, the first N second nodes in the order from high to low in the number of electronic invoices paid out for the second nodes, and so on.
And operation 3, screening out the second nodes meeting the preset regional conditions from all the second nodes based on the distance between the second nodes and the first nodes. For example, the first node screens out, from all the second nodes, second nodes whose distance from the first node is greater than a preset threshold, and for example, the first node selects the first N second nodes from all the second nodes in order of decreasing distance from the first node, and so on.
And 4, taking all the screened second nodes as consensus nodes.
Step 205: and indicating each consensus node to carry out validity verification on the last N backup data blocks in the target electronic invoice data chain, wherein N is a positive integer greater than or equal to 1.
It is worth saying that the purpose of selecting the last N backup data blocks in the target electronic invoice data chain for validity verification is as follows:
(1) because the electronic invoice data chain is not easy to be tampered, an illegal person usually attacks the electronic invoice data chain by adding the electronic invoice data block at the tail of the electronic invoice data chain, and on the basis, the last N backup data blocks are selected for validity verification, so that whether the target electronic invoice data chain is legal or not is easily verified.
(2) In order to ensure that the selected target backup electronic invoice data chain is the latest backup electronic invoice data chain, when the target electronic invoice data chain is selected, the backup electronic invoice data chain with the shortest time interval between the creation time of the last backup data block and the current time is generally selected as the target electronic invoice data chain, or the backup electronic invoice data chain with the largest number of the backup data blocks is selected as the target electronic invoice data chain, so that the selected target electronic invoice data chain possibly contains redundant backup electronic invoice data blocks relative to other backup electronic invoice data chains, on the basis of the selection, the last N backup data blocks are selected from the target electronic invoice data chain for legality verification, and the wrong deletion of the legal latest electronic invoice data blocks in the target electronic invoice data chain can be avoided, thereby improving the reliability of the electronic invoice data chain synchronization.
Step 206: judging whether the last N backup data blocks are legal or not based on the verification result returned by each consensus node, and if so, executing the step 207; otherwise, step 211 is executed.
It is worth mentioning that, when it is determined that the last N backup data blocks selected are all legal based on the verification result returned by each common identification node, the target electronic invoice data chain may be directly determined to be legal, and certainly, in order to further ensure the validity of the target electronic invoice data chain, step 207 may be further performed to verify whether other backup data blocks in the target electronic invoice data chain except the last N backup data blocks are legal.
Step 207: and optionally selecting M backup data blocks from all the rest backup data blocks except the last N backup data blocks in the target electronic invoice data chain, wherein M is a positive integer greater than or equal to 1.
Step 208: and indicating each common identification node to carry out validity verification on the selected M backup accounting blocks.
Step 209: judging whether the selected M backup data blocks are legal or not based on the verification result returned by each consensus node, if so, executing step 210; otherwise, step 211 is executed.
Step 210: and confirming that the target electronic invoice data chain is legal, and synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain.
Step 211: and deeming that the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all the backup electronic invoice data chains which are not subjected to validity verification, and returning to the step 205.
In the second embodiment of the invention, the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the data information of the electronic invoice is not managed and recorded in a centralized manner any more, a large amount of storage space of a computer, cloud equipment and a tax bureau website is saved, and simultaneously, the load of the computer, the cloud equipment and the tax bureau website is reduced, and the data blocks are not easy to be distorted once being created, so that the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the security is high, the reliability is strong, in addition, when the electronic invoice data chain is abnormal, the backup electronic invoice data chain can be obtained through business related nodes, and the legal backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains, so that the abnormal electronic invoice data chain is synchronized into the legal backup electronic invoice data chain, therefore, the recovery of the abnormal electronic invoice data chain is realized, meanwhile, the legality of the recovered electronic invoice data chain is ensured, in the process of legality verification, the legality of the backup electronic invoice data chain can be quickly and accurately verified through the legality verification of the last N backup electronic invoice data blocks, the latest electronic invoice data block in the backup electronic invoice data chain can be prevented from being deleted by mistake, and the reliability of electronic invoice data chain synchronization is improved.
EXAMPLE III
An embodiment of the present invention provides a synchronization apparatus for an electronic invoice data chain, as shown in fig. 3, the synchronization apparatus for the electronic invoice data chain at least includes:
an obtaining module 301, configured to select a backup node from all service-related nodes of a first node when an abnormal electronic invoice data chain exists in an electronic invoice data chain of the first node, where the electronic invoice data chain is formed by linking data blocks that record data information of an electronic invoice;
the verification module 302 is configured to obtain backup electronic invoice data chains of the abnormal electronic invoice data chain from each backup node, select one backup electronic invoice data chain from all the obtained backup electronic invoice data chains as a target electronic invoice data chain, and perform validity verification on the target electronic invoice data chain; if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification;
and the synchronization module 303 is configured to synchronize the abnormal electronic invoice data chain into the target electronic invoice data chain if the target electronic invoice data chain is legal.
Preferably, when the backup electronic invoice data chain of the abnormal electronic invoice data chain is acquired from each backup node, the acquiring module 301 is specifically configured to:
determining the data chain type of the abnormal electronic invoice data chain;
and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
Preferably, when one backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains as the target electronic invoice data chain, the verification module 302 is specifically configured to:
selecting the backup electronic invoice data chain with the shortest time interval between the creation time of the last backup data block and the current time from all the obtained backup electronic invoice data chains as a target electronic invoice data chain; or,
and selecting the backup electronic invoice data chain with the largest number of contained backup data blocks from all the obtained backup electronic invoice data chains as a target electronic invoice data chain.
Preferably, when performing validity verification on the target electronic invoice data chain, the verification module 302 is specifically configured to:
selecting consensus nodes from all service related nodes of the first node, and indicating each consensus node to carry out validity verification on the last N backup data blocks in the target electronic invoice data chain, wherein N is a positive integer greater than or equal to 1;
if the last N backup data blocks are determined to be legal based on the verification result returned by each common identification node, the target electronic invoice data link is determined to be legal; otherwise, the target electronic invoice data chain is determined to be illegal.
Preferably, after determining that the last N backup data blocks are all legal based on the verification result returned by each consensus node, before determining that the target electronic invoice data link is legal, the verification module 302 is further configured to:
and optionally selecting M backup data blocks from all the rest backup data blocks except the last N backup data blocks in the target electronic invoice data chain, and indicating each common identification node to carry out validity verification on the M backup accounting blocks, wherein M is a positive integer greater than or equal to 1.
Preferably, the verification module 302 is further configured to: and if the M backup data blocks are determined to be legal, determining that the target electronic invoice data link is legal.
Example four
Having described the method and apparatus of exemplary embodiments of the present invention, a non-volatile computer storage medium for electronic invoice data chain synchronization of exemplary embodiments of the present invention is described next. A fourth embodiment of the present invention provides a non-volatile computer storage medium, where an executable program is stored in the non-volatile computer storage medium, and the executable program is executed by a processor to implement the steps of the synchronization method for the electronic invoice data chain, such as implementing step 101 shown in fig. 1: when an abnormal electronic invoice data chain exists in the electronic invoice data chain of the first node, selecting a backup node from all business related nodes of the first node, wherein the electronic invoice data chain is formed by linking all data blocks for recording data information of an electronic invoice; step 102: respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and performing validity verification on the target electronic invoice data chain; step 103: if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification; step 104: and if the target electronic invoice data chain is legal, synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain.
EXAMPLE five
Having described the method, apparatus, and non-volatile computer storage media of exemplary embodiments of the present invention, the electronic device for electronic invoice data chain synchronization of exemplary embodiments of the present invention is described next. An embodiment of the present invention provides an electronic device, where the electronic device may be, but is not limited to, a personal computer device, a fiscal disc, and the like, and specifically, the electronic device may include: memory 401, processor 402 and a computer program stored on memory 401, which when executed by processor 402 implements the steps of the above-described method for synchronizing an electronic invoice data chain, such as implementing step 101 as shown in fig. 1: when an abnormal electronic invoice data chain exists in the electronic invoice data chain of the first node, selecting a backup node from all business related nodes of the first node, wherein the electronic invoice data chain is formed by linking all data blocks for recording data information of an electronic invoice; step 102: respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and performing validity verification on the target electronic invoice data chain; step 103: if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification; step 104: and if the target electronic invoice data chain is legal, synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain.
Preferably, the memory 401 may include Read Only Memory (ROM) and Random Access Memory (RAM), and the processor 402 may be a parallel processor.
Further, the electronic device in the fifth embodiment of the present invention may further include an input device 403, an output device 404, and the like. The input device 403 may include a stylus, keyboard, mouse, touch screen, etc.; the output device 404 may include a Display device such as a Liquid Crystal Display (LCD), a Cathode Ray Tube (CRT), a touch screen, and the like. The memory 401, processor 402, input device 403, and output device 404 may be connected by a bus or other means, and are illustrated in fig. 4 as being connected by a bus.
In summary, in the embodiment of the present invention, when an abnormal electronic invoice data chain exists in an electronic invoice data chain of a first node, a backup node is selected from all business-related nodes of the first node, where the electronic invoice data chain is formed by linking data blocks for recording data information of an electronic invoice; respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and performing validity verification on the target electronic invoice data chain; if the target electronic invoice data chain is illegal, reselecting a backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification; and if the target electronic invoice data chain is legal, synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain. Thus, the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the data information of the electronic invoice is not managed and recorded in a centralized manner, a large amount of storage space of a computer, cloud equipment and a tax bureau website is saved, the loads of the computer, the cloud equipment and the tax bureau website are reduced, and the data blocks are not easy to be distorted once being created, so that the data information of the electronic invoice is recorded through each data block in the electronic invoice data chain, the safety is high, the reliability is strong, in addition, when the electronic invoice data chain is abnormal, a backup electronic invoice data chain can be obtained through a service related node, and a legal backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains, so that the abnormal electronic invoice data chain is synchronized into the legal backup electronic invoice data chain, therefore, the recovery of the abnormal electronic invoice data chain is realized, and meanwhile, the legality of the recovered electronic invoice data chain is ensured.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (14)
1. A synchronization method of an electronic invoice data chain is characterized by comprising the following steps:
when an abnormal electronic invoice data chain exists in an electronic invoice data chain of a first node, selecting a backup node from all business related nodes of the first node, wherein the electronic invoice data chain is formed by linking data blocks for recording data information of an electronic invoice;
respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and performing validity verification on the target electronic invoice data chain;
if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification;
if the target electronic invoice data link is legal, synchronizing the abnormal electronic invoice data link as the target electronic invoice data link;
wherein the obtaining of the backup electronic invoice data chain of the abnormal electronic invoice data chain from each backup node comprises:
determining a data chain type of the abnormal electronic invoice data chain;
and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
2. The synchronization method according to claim 1, wherein the obtaining of the backup electronic invoice data chain of the abnormal electronic invoice data chain from each backup node respectively comprises:
determining a data chain type of the abnormal electronic invoice data chain;
and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
3. The synchronization method according to claim 1, wherein selecting one backup electronic invoice data chain as a target electronic invoice data chain from all the obtained backup electronic invoice data chains comprises:
selecting the backup electronic invoice data chain with the shortest time interval between the creation time of the last backup data block and the current time from all the obtained backup electronic invoice data chains as the target electronic invoice data chain; or,
and selecting the backup electronic invoice data chain with the largest number of backup data blocks from all the obtained backup electronic invoice data chains as the target electronic invoice data chain.
4. The synchronization method of claim 1, wherein performing legitimacy verification on the target electronic invoice data chain comprises:
selecting a consensus node from all service related nodes of the first node, and indicating each consensus node to carry out validity verification on the last N backup data blocks in the target electronic invoice data chain, wherein N is a positive integer greater than or equal to 1;
if the last N backup data blocks are determined to be legal based on the verification result returned by each common identification node, the target electronic invoice data link is determined to be legal; otherwise, the target electronic invoice data chain is determined to be illegal.
5. The synchronization method according to claim 4, wherein after determining that the last N backup data blocks are all legal based on the verification result returned by each consensus node, and before determining that the target electronic invoice data chain is legal, further comprising:
and selecting M backup data blocks from all the rest backup data blocks except the last N backup data blocks in the target electronic invoice data chain, and indicating each common identification node to carry out validity verification on the M backup data blocks, wherein M is a positive integer greater than or equal to 1.
6. The synchronization method of claim 5, wherein the target electronic invoice data link is deemed valid if it is determined that all of the M backup data blocks are valid.
7. A synchronization apparatus for an electronic invoice data chain, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for selecting backup nodes from all business related nodes of a first node when an abnormal electronic invoice data chain exists in the electronic invoice data chain of the first node, and the electronic invoice data chain is formed by linking data blocks for recording data information of an electronic invoice;
the verification module is used for respectively acquiring backup electronic invoice data chains of the abnormal electronic invoice data chains from each backup node, selecting one backup electronic invoice data chain from all the acquired backup electronic invoice data chains as a target electronic invoice data chain, and performing validity verification on the target electronic invoice data chain; if the target electronic invoice data chain is illegal, reselecting one backup electronic invoice data chain as the target electronic invoice data chain for validity verification from all backup electronic invoice data chains which are not subjected to validity verification;
the synchronization module is used for synchronizing the abnormal electronic invoice data chain into the target electronic invoice data chain if the target electronic invoice data chain is legal;
the verification module is specifically used for determining the data chain type of the abnormal electronic invoice data chain; and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
8. The synchronization apparatus according to claim 7, wherein when the backup electronic invoice data chain of the abnormal electronic invoice data chain is acquired from each backup node, the acquisition module is specifically configured to:
determining a data chain type of the abnormal electronic invoice data chain;
and selecting a backup electronic invoice data chain with the corresponding data chain type being the same as the data chain type of the abnormal electronic invoice data chain from all backup electronic invoice data chains of the first node stored by the backup node as the backup electronic invoice data chain of the abnormal electronic invoice data chain for each backup node.
9. The synchronization apparatus according to claim 7, wherein when one backup electronic invoice data chain is selected from all the obtained backup electronic invoice data chains as a target electronic invoice data chain, the verification module is specifically configured to:
selecting the backup electronic invoice data chain with the shortest time interval between the creation time of the last backup data block and the current time from all the obtained backup electronic invoice data chains as the target electronic invoice data chain; or,
and selecting the backup electronic invoice data chain with the largest number of backup data blocks from all the obtained backup electronic invoice data chains as the target electronic invoice data chain.
10. The synchronization apparatus according to claim 7, wherein when performing validity verification on the target electronic invoice data chain, the verification module is specifically configured to:
selecting a consensus node from all service related nodes of the first node, and indicating each consensus node to carry out validity verification on the last N backup data blocks in the target electronic invoice data chain, wherein N is a positive integer greater than or equal to 1;
if the last N backup data blocks are determined to be legal based on the verification result returned by each common identification node, the target electronic invoice data link is determined to be legal; otherwise, the target electronic invoice data chain is determined to be illegal.
11. The synchronization apparatus according to claim 10, wherein after determining that the last N backup data blocks are all legal based on the verification result returned by each consensus node, before considering that the target electronic invoice data chain is legal, the verification module is further configured to:
and selecting M backup data blocks from all the rest backup data blocks except the last N backup data blocks in the target electronic invoice data chain, and indicating each common identification node to carry out validity verification on the M backup data blocks, wherein M is a positive integer greater than or equal to 1.
12. The synchronization apparatus of claim 11, wherein the verification module is further to: and if the M backup data blocks are determined to be legal, determining that the target electronic invoice data link is legal.
13. A non-volatile computer storage medium storing an executable program for execution by a processor to perform the steps of implementing the synchronization method of any of claims 1-6.
14. An electronic device, comprising: memory, processor and computer program stored on the memory, the processor implementing the steps of the synchronization method of any of claims 1-6 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710875650.4A CN109558064B (en) | 2017-09-25 | 2017-09-25 | Electronic invoice data chain synchronization method, device, medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710875650.4A CN109558064B (en) | 2017-09-25 | 2017-09-25 | Electronic invoice data chain synchronization method, device, medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109558064A CN109558064A (en) | 2019-04-02 |
| CN109558064B true CN109558064B (en) | 2022-06-07 |
Family
ID=65861915
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710875650.4A Active CN109558064B (en) | 2017-09-25 | 2017-09-25 | Electronic invoice data chain synchronization method, device, medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109558064B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111931247A (en) * | 2020-07-04 | 2020-11-13 | 华电联合(北京)电力工程有限公司 | Verification method, verification device, verification system and computer-readable storage medium for verification data |
| CN116760632B (en) * | 2023-08-10 | 2023-11-03 | 腾讯科技（深圳）有限公司 | Data processing method, device, equipment and readable storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106295406A (en) * | 2016-08-13 | 2017-01-04 | 深圳市樊溪电子有限公司 | A kind of block chain that is used for is from safe storage system and method thereof |
| CN106383754A (en) * | 2016-09-19 | 2017-02-08 | 北京众享比特科技有限公司 | Database backup and recovery system based on block chain technology, and database backup method based on block chain technology, and database recovery method based on block chain technology |
| CN106412037A (en) * | 2016-09-19 | 2017-02-15 | 中国银联股份有限公司 | Security electronic file processing system and method based on block link structure |
| CN106547648A (en) * | 2016-10-21 | 2017-03-29 | 杭州嘉楠耘智信息科技有限公司 | Backup data processing method and device |
| CN106713412A (en) * | 2016-11-09 | 2017-05-24 | 弗洛格（武汉）信息科技有限公司 | Block chain system and construction method of block chain system |
| CN106775497A (en) * | 2017-01-19 | 2017-05-31 | 郑志超 | Distributed storage method and equipment based on block chain |
| CN106952124A (en) * | 2017-03-16 | 2017-07-14 | 北京牛链科技有限公司 | Electronic bill management system and method based on distribution book keeping operation |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8966200B1 (en) * | 2014-09-30 | 2015-02-24 | Storagecraft Technology Corporation | Pruning free blocks out of a decremental backup chain |
-
2017
- 2017-09-25 CN CN201710875650.4A patent/CN109558064B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106295406A (en) * | 2016-08-13 | 2017-01-04 | 深圳市樊溪电子有限公司 | A kind of block chain that is used for is from safe storage system and method thereof |
| CN106383754A (en) * | 2016-09-19 | 2017-02-08 | 北京众享比特科技有限公司 | Database backup and recovery system based on block chain technology, and database backup method based on block chain technology, and database recovery method based on block chain technology |
| CN106412037A (en) * | 2016-09-19 | 2017-02-15 | 中国银联股份有限公司 | Security electronic file processing system and method based on block link structure |
| CN106547648A (en) * | 2016-10-21 | 2017-03-29 | 杭州嘉楠耘智信息科技有限公司 | Backup data processing method and device |
| CN106713412A (en) * | 2016-11-09 | 2017-05-24 | 弗洛格（武汉）信息科技有限公司 | Block chain system and construction method of block chain system |
| CN106775497A (en) * | 2017-01-19 | 2017-05-31 | 郑志超 | Distributed storage method and equipment based on block chain |
| CN106952124A (en) * | 2017-03-16 | 2017-07-14 | 北京牛链科技有限公司 | Electronic bill management system and method based on distribution book keeping operation |
Non-Patent Citations (1)
| Title |
|---|
| 基于区块链的电子发票系统研究;张庆胜等;《信息安全研究》;20170605(第06期);第516-522页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109558064A (en) | 2019-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107239954B (en) | Method and device for increasing block generation speed | |
| CN106326219B (en) | Method, device and system for checking business system data | |
| CN110061843B (en) | Block height creating method, device and equipment in chain type account book | |
| CN112422341B (en) | Fault detection method of block chain network and related equipment | |
| CN108959374B (en) | Data storage method and device and electronic equipment | |
| CN109117314B (en) | Anti-misoperation data rapid recovery method and system | |
| CN107423163B (en) | Error surveying method and system for block chain of overall serial added blocks | |
| CN109558064B (en) | Electronic invoice data chain synchronization method, device, medium and electronic equipment | |
| CN111931172A (en) | Financial system business process abnormity early warning method and device | |
| CN108470039A (en) | Data processing method and device in block chain | |
| CN109284331B (en) | Certificate making information acquisition method based on service data resources, terminal equipment and medium | |
| CN103440460A (en) | Application system change validation method and system | |
| CN105183648A (en) | Visualized automatic dial testing method and system | |
| CN107451011B (en) | Error correction method and system for block chain of parallel added blocks | |
| CN112541823A (en) | Transaction risk control method, device and equipment based on block chain and storage medium | |
| CN108304569B (en) | Test data accumulation method and device | |
| CN110019972A (en) | The restoration methods and electronic device of the storage method of electronic invoice, chain of keeping accounts | |
| CN112215693A (en) | Voucher generation method and related device | |
| CN116756129A (en) | Data complement method and device, storage medium and electronic equipment | |
| CN107426293B (en) | Error correction method and system for block chain of single serial added block | |
| CN110059087A (en) | Data attribute identification method, device and equipment in a kind of piece of chain type account book | |
| CN112507014B (en) | Data storage method, device and system based on credible account book database | |
| CN106570065B (en) | Method and system for verifying whether timestamp of file in database is forged | |
| CN102831547B (en) | A kind of method and system of settling interests in real time and processing of realizing | |
| CN114255134A (en) | Account number disassembling method and device 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |