CN115952237B - Multi-terminal data fusion system - Google Patents
Multi-terminal data fusion system Download PDFInfo
- Publication number
- CN115952237B CN115952237B CN202310102461.9A CN202310102461A CN115952237B CN 115952237 B CN115952237 B CN 115952237B CN 202310102461 A CN202310102461 A CN 202310102461A CN 115952237 B CN115952237 B CN 115952237B
- Authority
- CN
- China
- Prior art keywords
- terminal
- accounting
- data
- block
- terminals
- 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
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a multi-terminal data fusion system. The system comprises: billing terminal, target execution terminal, execution terminal of the same block chain; the accounting terminal is used for acquiring user operation requests of at least one terminal in one synchronization period, selecting user operations to be executed in each user operation request, selecting a target execution terminal to execute the user operations in each execution terminal, forming block data of the period according to the user operations sent by the target execution terminal and corresponding operation results, broadcasting the block data to each terminal, and determining different terminals as accounting terminals in different synchronization periods; the target execution terminal is used for executing user operation to obtain an operation result and sending the user operation and the corresponding operation result to the accounting terminal; and the execution terminal is used for updating the local block chain data according to the block data broadcast by the accounting terminal. By the invention, the data synchronization of decentralization is realized, and data conflict is not generated when multiple terminals operate simultaneously.
Description
Technical Field
The embodiment of the invention relates to the field of computers, in particular to a multi-terminal data fusion system.
Background
The multi-machine hot standby system is the smallest component unit of a cluster, namely, a central server is installed into two servers which are mutually backed up, and only one server operates at the same time. When one of the running servers fails and cannot be started, the other backup server can be started and run automatically and rapidly (generally about a few minutes), so that the normal running of the whole network system is ensured. The working mechanism of the multi-machine hot standby is to provide a fault automatic recovery capability for a central server of the whole network system.
In the prior art, a multi-machine hot standby system performs redundant acquisition and processing by configuring a plurality of servers, and a controller is relied on to output a system processing result. In the multi-machine hot standby system, a plurality of servers process acquired data to obtain a plurality of processing results, a controller is utilized to select a final system processing result from the plurality of processing results, and once the controller fails, the multi-machine redundancy fails, so that the system cannot normally operate.
Disclosure of Invention
In order to realize the data synchronization of decentralization and improve the running reliability of the system, the invention provides a multi-terminal data fusion system.
In a first aspect, the present invention provides a multi-terminal data fusion system comprising: accounting terminals, target execution terminals and execution terminals which are positioned in the same block chain;
the accounting terminal is used for acquiring user operation requests of at least one terminal in one synchronization period, selecting user operations to be executed in each user operation request, selecting a target execution terminal to execute the user operations in each execution terminal, forming block data of the period according to the user operations sent by the target execution terminal and corresponding operation results, broadcasting the block data to each terminal, and determining different terminals as accounting terminals in different synchronization periods;
the target execution terminal is used for executing user operation to obtain an operation result and sending the user operation and the corresponding operation result to the accounting terminal;
and the execution terminal is used for updating the local block chain data according to the block data broadcast by the accounting terminal.
Through the system, each terminal is in the same blockchain, different terminals are determined to be accounting terminals in different synchronization periods, the data synchronization without depending on any fixed terminal is realized, and when the multi-terminal receives the user operation request at the same time, the target execution terminal executes the user operation only after the accounting terminal selects the user operation to be executed, even if the user operation requests received by the multi-terminal have conflict, the conflicting user request cannot be confirmed by the accounting terminal, and further the accounting terminal cannot be executed by the target execution terminal, so that the data conflict cannot occur under the condition of the simultaneous operation of the multi-terminal.
With reference to the first aspect, in a first embodiment of the first aspect, each terminal in the system corresponds to an active terminal list, where the active terminal list records information of normal terminals, and the billing terminal specifies a billing terminal of a next period according to the active terminal list.
With reference to the first embodiment of the first aspect, in a second embodiment of the first aspect, each terminal in the system is further configured to receive a synchronization signal, where the terminal that receives the synchronization signal broadcasts a respective user operation request and local blockchain data;
and each terminal determines a fault terminal according to the response results of the other terminals to the synchronous signals, deletes the fault terminal in the effective terminal list, and judges the terminal which does not respond to the synchronous signals in one synchronous period as the fault terminal.
With reference to the second embodiment of the first aspect, in a third embodiment of the first aspect, the local blockchain data includes a blockheight therein,
and each terminal in the system updates the respective effective terminal list according to the block heights of the rest terminals, judges the terminal with the block height smaller than the terminal to be a fault terminal, judges the terminal with the block height consistent with the terminal to be a normal terminal, deletes the fault terminal in each effective terminal list, and adds the normal terminal into the effective terminal list.
With reference to the first aspect, in a fourth embodiment of the first aspect, in one synchronization period, when the accounting terminal does not broadcast the block data of the present period, it is determined that the accounting terminal fails, and the accounting terminal in the previous synchronization period is taken as a new accounting terminal.
With reference to the third embodiment of the first aspect, in a fifth embodiment of the first aspect, after the terminal in the failure state is failed and recovered, historical blockchain data is obtained by any normal terminal until the block height of the failed terminal is consistent with the block height of the normal terminal, and then the historical blockchain data is added to the valid terminal list of each terminal again.
With reference to the first aspect, in a sixth embodiment of the first aspect, each terminal in the system performs sum check on the sum check value of the block data in the previous period and the accumulated sum of the received new block data, the block data passing the sum check is valid block data, and each terminal updates the respective blockchain data based on the valid block data.
With reference to the sixth embodiment of the first aspect, in a seventh embodiment of the first aspect, each terminal in the system is further configured to vote for the received first valid block data, and when the system presents a plurality of billing terminals, compare the number of votes for the block data in a period on each billing terminal, and select the billing terminal with the highest number of votes as the final billing terminal.
With reference to the first aspect, in an eighth embodiment of the first aspect, the blockchain data of each terminal in the system includes an creation block for describing an initial state of the system.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a multi-terminal data fusion system according to an exemplary embodiment;
FIG. 2 is a diagram of a system networking scheme for synchronizing with a synchronization pulse signal in one example;
FIG. 3 is a diagram of a system networking mode for synchronization with GPS timing in one example;
FIG. 4 is a diagram of a system networking scheme with transmit data monitoring in one example;
FIG. 5 is a schematic diagram of a multi-port data fusion system in another example;
FIG. 6 is a block diagram of a multi-machine hot standby control system in an example.
Detailed Description
The following description of the embodiments of the present invention will be made apparent and fully in view of the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In addition, the technical features of the different embodiments of the present invention described below may be combined with each other as long as they do not collide with each other.
A blockchain is a chain of blocks one by one. Each block holds certain information which is linked in a chain according to the time sequence of their respective generation. The chain is stored in all servers, and the whole blockchain is safe as long as one terminal in the whole system can work. These terminals, referred to as nodes in the blockchain system, provide storage space and computational support for the entire blockchain system.
In order to realize the data synchronization of decentralization and improve the running reliability of the system, the invention provides a multi-terminal data fusion system. As shown in fig. 1, the system includes a billing terminal 101, a target execution terminal 102, and an execution terminal 103 of the same blockchain;
a billing terminal 101, configured to obtain a user operation request of at least one terminal in one synchronization period, select a user operation to be performed in each user operation request, select a target execution terminal 102 to perform the user operation in each execution terminal 103, form block data of a period according to the user operation and a corresponding operation result sent by the target execution terminal 102, and broadcast the block data to each terminal, and determine different terminals as the billing terminal 101 in different synchronization periods;
the target execution terminal 102 is configured to execute a user operation to obtain an operation result, and send the user operation and the corresponding operation result to the accounting terminal 101;
the executing terminal 103 is used for updating the local blockchain data according to the blockdata broadcast by the accounting terminal 101.
Specifically, the accounting terminal 101 and the target execution terminal 102 belong to the execution terminal 103, and the operation capability of each execution terminal may be the same or different, and the accounting terminal 101 selects the target execution terminal 102 having the operation capability from the respective terminals to execute the user operation according to the user operation request, which of course, the accounting terminal 101 may designate itself as the target execution terminal 102, and the specific limitation is not restricted herein.
Through the system, each terminal is in the same blockchain, different terminals are determined to be the accounting terminal 101 in different synchronization periods, the data synchronization of decentralization is realized without depending on any fixed terminal, and when the multi-terminal receives the user operation request at the same time, the target execution terminal 102 executes the user operation only after the accounting terminal 101 selects the user operation to be executed, even if the user operation requests received by the multi-terminal have conflict, the user request causing the conflict cannot be confirmed by the accounting terminal 101, and further cannot be executed by the target execution terminal 102, so that the data conflict cannot be generated under the condition of the multi-terminal simultaneous operation.
In an example, each terminal may generate a random number with a length of 32 bits according to its own network card address, a hard disk serial port, etc., and use the random number as an identification code in the system, which is called a terminal ID.
In yet another example, the blockchain data for each terminal in the system includes an creation block for documenting an initial state of the system.
Specifically, the creation block can be generated by any terminal operated by a user, and the initial state of the system is recorded in the creation block, so that the creation block is used as the starting point of the task and is broadcasted to all terminals in the system. All user operations thereafter are incrementally changed on the basis thereof.
In an alternative embodiment, the terminal that produces the creation block naturally has the 1 st (creation block 1), 2 nd billing rights. At the time of billing for the 2 nd time, if there are other terminals in the system, the effective terminal list is not empty at this time, and 1 effective terminal is randomly selected from the effective terminal list as the billing terminal 101 for the next time. From time 3, the billing terminal 101 of the system is designated by the billing terminal last time. Illustratively, the accounting terminal 101 in the last synchronization period randomly selects one terminal from the terminals as the accounting terminal 101 in the current synchronization period, and at this time, the terminals do not need to compete for the accounting terminal 101 by workload or the like, but determine the accounting terminal 101 by the manner specified by the accounting terminal in the last period, so that time and resources are not consumed, and the processing speed of the system is faster.
Of course, a certain terminal in the system may be selected as the billing terminal 101 by other manners, such as workload certification, rights certification, etc., or alternatively, may be used as the billing terminal 101, which is not particularly limited in the embodiment of the present invention.
In an example, each terminal in the system corresponds to an active terminal list, the active terminal list records information of normal terminals, and the billing terminal designates the billing terminal of the next period according to the active terminal list.
In an example, each terminal in the system is further configured to receive a synchronization signal, and the terminal that receives the synchronization signal broadcasts a respective user operation request and local blockchain data.
And each terminal determines a fault terminal according to the response results of the other terminals to the synchronous signals, deletes the fault terminal in the effective terminal list, and judges the terminal which does not respond to the synchronous signals in one synchronous period as the fault terminal.
The existing blockchain technology achieves consistency through workload certification, so that the block-out time of the block data is the fastest in the second level, and in the embodiment of the invention, an asynchronous system operated by the blockchain in the prior art is changed into a synchronous system capable of supporting the blockchain operation by adding a synchronous signal, so that the processing speed of the system is increased, the data can be processed in the millisecond level, no delay or blocking is felt by a person, and the equipment with high real-time requirements can be met.
In an alternative embodiment, the blockchain data for each terminal includes a respective terminal ID. Each terminal needs to add itself into an effective terminal list, and the effective terminal list at least comprises one effective terminal, namely, the terminal is itself. After receiving the synchronization signal, each terminal broadcasts a user operation request and local blockchain data, and when receiving new blockinformation broadcasted by other terminals, each terminal broadcasts its own terminal ID.
For the accounting terminal 101, the broadcast block data may be a request for each user operation sent from each terminal, or may be a result of the user operation, or may be a null result when there is no user operation or operation result.
In one example, in one synchronization period, when the accounting terminal 101 does not broadcast the block data of the present period, it is determined that the accounting terminal 101 fails, and the accounting terminal in the last synchronization period is taken as a new accounting terminal. At this time, the accounting terminal of the previous period should be in the valid terminal list, if the accounting terminal of the previous period is not in the valid terminal list, the accounting terminal in the valid terminal list with the last synchronization period is used as a new accounting terminal, and the new block of the current period is replaced by a null result.
In one example, the blockchain data includes blockheight, system status, user operation, status change.
The block height of the system block chain data is consistent with the number of the synchronous signals, each synchronous period is formed into one block data by the user operation and the corresponding operation result, the idle operation result is used for replacing the system block chain data when the user operation or the operation result is not used, the block height is increased by 1 after each synchronous period, and each terminal judges whether the block data is up-to-date or not. The block height of each terminal is consistent with the block height of the blockchain data of the system.
The state change means that after the user operation is confirmed by the accounting terminal 101 and executed by the target execution terminal 102, the block data describes the state change generated by the user operation to the system for updating the system state.
In an example, each terminal in the system updates its own valid terminal list according to the block heights of the remaining terminals, determines a terminal smaller than its own block height as a faulty terminal, determines a terminal identical to its own block height as a normal terminal, deletes the faulty terminal in its own valid terminal list, and adds the normal terminal to the valid terminal list.
In an alternative embodiment, after receiving the block height of the terminal a, the terminal B updates the failure count value of the terminal a in the valid terminal list of the terminal B to 0 if the block height of the terminal a is identical to the block height of the terminal B, adds the terminal a to the valid terminal list if the terminal a does not exist in the valid terminal list, sets the failure count value of the terminal a to 0 at the same time, and otherwise does not update the information of the terminal a in the valid terminal list; after each synchronization signal arrives, the terminal B adds 1 to the member fault count value in the effective terminal list; for terminals whose failure count value exceeds 1, the terminal is considered to be failed, and the failed terminal is removed from the active terminal list of terminal B.
When any terminal fails, the terminal is removed from the effective terminal list, the failed terminal is automatically isolated, and other normal terminals continue to operate according to the effective terminal list without being influenced by the failed terminal.
In yet another example, when a terminal in a failed state fails to recover, historical blockchain data is obtained by any normal terminal until the block height of the failed terminal is consistent with the block height of the normal terminal, and then the terminal is added back to the list of valid terminals of each terminal.
In one example, each terminal in the system performs sum check on the sum check value of the block data in the previous period and the accumulated sum of the received new block data, the block data passing the sum check is valid block data, and each terminal updates the respective block chain data based on the valid block data.
In the prior art, the validity of block data is checked through a Hash value, and the validity of the block data is checked and verified in the embodiment of the invention, so that the workload of the system is reduced. The known blockchain technology needs to use workload certification to contend for accounting rights, so that an algorithm of 'finding difficulty and easy verification' needs to be used, and the accounting terminal 101 in the system is determined in advance without contending, so that only the verification purpose is needed, and the workload certification is not needed to be provided; the set blockchain operation network in the embodiment of the invention is an equipment local area network, no malicious node exists, the agreement can be achieved without the need of workload verification, and the worry of data tampering is avoided; the set blockchain operation network is a synchronous network, and an algorithm of 'difficult searching and easy verification' is not required to be used for avoiding bifurcation; only the block data that passes the checksum verification is added to the blockchain data of each terminal.
In one example, the blockchain data further includes a number of endorsements, each terminal in the system is further configured to endorse the received first valid blockdata, and when the system presents a plurality of accounting terminals, compare the number of endorsements of the blockdata of a period on each accounting terminal, and select the accounting terminal with the highest number of endorsements as the final accounting terminal. The number of endorsed tickets is used for the selection of a plurality of accounting terminals 101.
For example, when it is assumed that the terminal a is offline due to a data transmission problem in the system, only the terminal a is used as its own billing terminal in the active terminal list of the terminal a.
When the execution terminal A is restored to a normal state and is accessed to the system, two accounting terminals of an accounting terminal B and an accounting terminal A of the system appear, and when the two accounting terminals send new block data to other terminals in the system in the current synchronization period, the other terminals in the system compare the number of endorsements operated by users in the previous synchronization period of the two accounting terminals, and the accounting terminal with larger number of endorsements is selected as the final accounting terminal. If the number of the votes is the same, comparing the number of the user operations received currently, and selecting the billing terminal with a large number of the user operations as the final billing terminal.
In one example, after receiving new block data from accounting terminal B, accounting terminal a detects a conflict, obtains the data of the last block from accounting terminal B, compares the data with the local last block data, and records the winning of the number of votes and the winning of the number of votes when the number of votes is consistent. Illustratively, accounting terminal B has a greater number of block votes than accounting terminal a, accounting terminal a gives up accounting terminal identity, obtains historical block data from accounting terminal B, and rolls back all local block chain data until the local block chain data remains consistent with the block chain data at accounting terminal B. Illustratively, the last block at accounting terminal a has a greater number of votes than the last block at accounting terminal B, accounting terminal a ignores the new block data from accounting terminal B.
In one example, after receiving new block data from accounting terminal a, accounting terminal B and other terminals detect a conflict, acquire the data of the previous block from accounting terminal a, compare with the local previous block data, and register the winning with more votes, and when the votes agree, register the winning with more votes. Illustratively, accounting terminal a has more of its last block in favor of the number of tickets than accounting terminal B, accounting terminal B gives up accounting terminal identity, obtains historical block data from accounting terminal a, and rolls back all local data until the local blockchain data remains consistent with the blockchain data of accounting terminal a. Illustratively, accounting terminal B has more votes in favor of one block than accounting terminal a, and accounting terminal B ignores the new block data from accounting terminal a. Illustratively, the last block at the remaining terminals has a greater number of votes than the last block at billing terminal a, new block data from billing terminal a is ignored, illustratively, the last block at billing terminal a has a greater number of votes than the last block at the remaining terminals, the remaining terminals obtain historical block data from billing terminal a and rollback all data locally until the local block chain data remains consistent with the block chain data at billing terminal a.
Illustratively, when the number of votes is the same, the user of billing terminal a operates to press button 1 and press button 2, and the user of billing terminal B operates to press button 2, billing terminal a is selected as the final billing terminal.
In another example, the system's operation may be played back, i.e., all user operations are recorded in the blockchain data, and the playback operation may only require reading of the blockchain data.
In an example, each user operation request may not be selectively confirmed by the billing terminal, or may be confirmed by the user himself or the like, which is not limited herein.
In yet another example, the networking form of each terminal includes, but is not limited to, transmission modes using reflective memory cards, ethernet, CAN bus, RS422, RS485, RS232, and the like.
In one example, the synchronization signals received by each terminal include, but are not limited to, synchronization pulse signals and GPS time service synchronization signals. It should be noted that, no additional synchronization signal may be added, and the local timing of each terminal may be relied on, for example, every 1 second, that is, the local second signal plays a role of the synchronization signal, which is not limited in particular in the embodiment of the present invention.
Fig. 2 is a diagram of a system networking scheme for synchronizing with a synchronization pulse signal. The physical link in the system adopts a main-standby mode, and the main link is normally communicated by a user, and the standby link is used for block recovery of a fault terminal or standby communication when the main link is in fault.
Fig. 3 is a diagram of a system networking scheme for synchronizing GPS timing, and the above diagram CAN be considered when the system networking scheme is connected in a form of an ethernet, a CAN bus, or the like having a collision detection and retransmission mechanism.
Fig. 4 is a diagram of a system networking mode with data transmission monitoring, and if the networking mode is considered by using RS422, RS485, RS232 or similar transmission modes, the state of a data line is monitored when each terminal is required to transmit data, and software ensures that the data is completely transmitted and has no conflict.
When the operation capabilities of the execution terminals are different, the accounting terminal selects the execution terminal with the corresponding operation capability as the target execution terminal. Fig. 5 is a diagram of a multi-terminal data fusion system when there is a difference between execution terminals. As shown in fig. 5, the system includes a general terminal 501, a special operation execution terminal 502, a target special operation execution terminal 503, and a billing terminal 504 of the same blockchain.
The common terminal 501 is used for collecting user operations, displaying system states and feeding back operation results to users. When the user clicks a button or sets a parameter, the ordinary terminal 501 broadcasts the user operation write operation buffer to other terminals in the system. When receiving the valid block data from the billing terminal 504, the ordinary terminal 501 updates the system state, and displays the updated system state on the interface. If the operation of setting parameters by the user is confirmed in the received valid block, the general terminal 501 feeds back that the parameter setting is successful, and if the parameters set by the user are not confirmed in the valid block, the general terminal 501 feeds back that the parameter setting is failed.
The special operation execution terminal 502 has a specific hardware interface supporting completion of tasks that can be completed by the ordinary terminal 501, in addition to all functions of the ordinary terminal 501. Illustratively, the hardware interface includes a serial port, an IO card, a reflective memory card, a power strip, etc., without specific limitation herein.
When the system needs to control the external device through the serial port, the special operation execution terminal 502 having the serial port communication capability and being connected to the external device is required to successfully complete the control, and the common terminal 501 cannot complete the control because it does not have the serial port communication capability or is not connected to the external device.
The target special operation execution terminal 503 is used for carrying out the special operation of the user and obtaining the operation result.
Illustratively, the system needs to turn on the 28V power supply output during the kth period, which is designated to be executed by the target special operation execution terminal 503; the target special operation execution terminal 503 executes the 28V power supply output instruction to be turned on in the k+1th cycle; the 28V power supply is stable in output in the k+3 period, and the operation of opening the output is completed; the target special operation execution terminal 503 broadcasts the operation result to other terminals in the k+4 cycle.
And a billing terminal 504 for acquiring user operation requests from the general terminal 501, the special operation execution terminal 502, the target special operation execution terminal 503, and the billing terminal 504 in one synchronization period, selecting a user general operation to be executed from the user operation requests, and executing, designating the target special operation execution terminal 503 for executing the user special operation from the special operation execution terminal 502, and generating the present period block data according to the selected user operation and operation result.
The user may send an operation request to any terminal, such as a request of clicking a button, setting a system parameter, etc., where each user operation request is stored in an operation buffer of the system, and after the accounting terminal 504 selects and confirms, the non-special operation is performed by the accounting terminal 504, and the special operation is performed by the target special operation execution terminal 503 selected by the accounting terminal 504 from the special operation execution terminals 502.
When the terminal which collects the user operation waits for 2 synchronization periods, the user operation request is not confirmed, the user operation request is considered to be invalid, the user operation request is ended, or the user initiates the operation request again.
In the system, the accounting terminal 504 generates new block data from the user operation and operation result selected to be performed, and broadcasts the block data to the general terminal 501, the special operation execution terminal 502, and the target special operation execution terminal 503, each terminal updates the local blockchain data according to the valid block data, and in different synchronization periods, different terminals are determined as the accounting terminal 504.
FIG. 6 is a multi-machine thermal backup test initiation control system. As shown in fig. 6, a front-end computer, a back-end computer, and a front-end device are included in the system. The front-end computer and the back-end computer belong to execution terminals, the billing terminal is generated in each computer, and the billing terminal selects a corresponding target execution terminal according to different user operations (i.e. selects the front-end computer or the back-end computer according to different user operations) to execute the user operations.
The front-end computer and the back-end computer devices A1-An are a plurality of computers arranged at the back end, can be industrial computers, ordinary computers, or hand-held PDA devices or mobile phones (hardware synchronous signals cannot be used when the mobile phones are used), and the devices B1-Bn are a plurality of computers arranged at the front end, and can be industrial computers, ordinary computers or embedded devices. WiFi, ethernet, CAN bus, various serial ports, reflective memory card and other networking CAN be used in the back-end computers, the front-end computers and between the back-end computers and the front-end computers. The wires can be selected from cables, optical fibers, wireless data transmission and the like. The communication between the front-end computer and the distribution switching box and between the front-end computer and the power supply combination module CAN be Ethernet, CAN bus, various serial ports and the like. The bullet/arrow communicates with the ground telemetry equipment and the distribution switching box through ground cables respectively. The communication between the ground telemetry equipment and the front-end computer can be Ethernet, various forms of serial ports and the like. When the system reliability requirement is strict, a communication link can be added for emergency communication when the network is blocked.
When the real-time requirement on the system is high, the devices A1-An and the devices B1-Bn can select real-time system expansion and add synchronous signals. At this time, the response speed of the system can be reduced to below 50 ms. The user does not feel the delay in operation. The form of the synchronizing signal can be pulse signal, beidou/GPS time service and the like. When the real-time requirement on the system is not high, for example, the user can tolerate the operation delay of more than 200ms, the hardware synchronous signal can not be added. When the hardware synchronizing signal is not added, the timing is started by receiving the block information, and 200ms is a period, namely the synchronizing signal of the software. Typically, the packing and other operations of the blocks can be completed within 100 ms.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The foregoing is merely exemplary of embodiments of the present invention to enable those skilled in the art to understand or practice the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. The multi-terminal data fusion system is characterized by comprising an accounting terminal, a target execution terminal and an execution terminal which are positioned in the same blockchain;
the accounting terminal is used for acquiring user operation requests of at least one terminal in one synchronization period, selecting user operations to be executed in each user operation request, selecting a target execution terminal to execute the user operations in each execution terminal, forming block data of the period according to the user operations sent by the target execution terminal and corresponding operation results, broadcasting the block data to each terminal, and determining different terminals as accounting terminals in different synchronization periods;
the target execution terminal is used for executing user operation to obtain an operation result and sending the user operation and the corresponding operation result to the accounting terminal;
and the execution terminal is used for updating local blockchain data according to the blockdata broadcast by the accounting terminal.
2. The system of claim 1, wherein the system further comprises a controller configured to control the controller,
each terminal in the system is respectively corresponding to an effective terminal list, and the effective terminal list records the information of a normal terminal;
the billing terminal designates the billing terminal of the next period according to the valid terminal list.
3. The system of claim 2, wherein the system further comprises a controller configured to control the controller,
each terminal in the system is also used for receiving a synchronous signal, and the terminal receiving the synchronous signal broadcasts respective user operation request and local block chain data;
and each terminal determines a fault terminal according to the response result of the rest terminals to the synchronous signals, deletes the fault terminal in the effective terminal list, and judges the terminal which does not respond to the synchronous signals in one synchronous period as the fault terminal.
4. The system of claim 3, wherein the local blockchain data includes a blockheight,
and each terminal in the system updates the respective effective terminal list according to the block heights of the rest terminals, judges the terminal with the block height smaller than the terminal as a fault terminal, judges the terminal with the block height consistent with the terminal as a normal terminal, deletes the fault terminal in each effective terminal list, and adds the normal terminal into the effective terminal list.
5. The system of claim 1, wherein the system further comprises a controller configured to control the controller,
in one synchronization period, when the accounting terminal does not broadcast the block data of the period, the accounting terminal is judged to be faulty, and the accounting terminal in the last synchronization period is taken as a new accounting terminal.
6. The system of claim 4, wherein the system further comprises a controller configured to control the controller,
and after the terminal in the fault state is recovered, acquiring historical block data through any normal terminal until the block height of the fault terminal is consistent with the block height of the normal terminal, and then adding the block height of the fault terminal into the effective terminal list of each terminal again.
7. The system of claim 1, wherein the system further comprises a controller configured to control the controller,
and each terminal in the system performs sum check on the sum check value of the block data in the previous period and the accumulated sum of the received new block data, the block data passing the sum check is effective block data, and each terminal updates the respective block chain data based on the effective block data.
8. The system of claim 7, wherein the system further comprises a controller configured to control the controller,
each terminal in the system is also used for approving the received first effective block data, when a plurality of billing terminals appear in the system, the approval ticket number of the block data in a period of each billing terminal is compared, and the billing terminal with the highest approval ticket number is selected as the final billing terminal.
9. The system of claim 1, wherein the blockchain data for each terminal in the system includes an creation block for documenting an initial state of the system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310102461.9A CN115952237B (en) | 2023-01-28 | 2023-01-28 | Multi-terminal data fusion system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310102461.9A CN115952237B (en) | 2023-01-28 | 2023-01-28 | Multi-terminal data fusion system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115952237A CN115952237A (en) | 2023-04-11 |
| CN115952237B true CN115952237B (en) | 2023-06-09 |
Family
ID=85892736
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310102461.9A Active CN115952237B (en) | 2023-01-28 | 2023-01-28 | Multi-terminal data fusion system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115952237B (en) |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105706047A (en) * | 2013-11-11 | 2016-06-22 | 亚马逊科技公司 | Partition-based data stream processing framework |
| CN108776929A (en) * | 2018-04-02 | 2018-11-09 | 成都云创智融科技有限公司 | Bill processing method, system based on block chain database and readable storage medium storing program for executing |
| CN109391684A (en) * | 2018-09-25 | 2019-02-26 | 莆田市烛火信息技术有限公司 | A kind of block chain accounting nodes selection method and system being associated with related chain |
| CN109636492A (en) * | 2018-12-07 | 2019-04-16 | 深圳市智税链科技有限公司 | Tax administration method, apparatus, medium and electronic equipment based on block catenary system |
| CN110851496A (en) * | 2018-12-07 | 2020-02-28 | 深圳市智税链科技有限公司 | Method, apparatus, accounting node and medium for querying transaction information in blockchain network |
| CN111222963A (en) * | 2020-01-16 | 2020-06-02 | 腾讯科技（深圳）有限公司 | Bidding information processing method and device based on block chain |
| CN111769639A (en) * | 2020-06-22 | 2020-10-13 | 积成电子股份有限公司 | Block chain-based power monitoring system key operation record processing method |
| CN112529703A (en) * | 2020-11-23 | 2021-03-19 | 中国联合网络通信集团有限公司 | Accounting node selection method and device for block chain |
| KR102299030B1 (en) * | 2021-06-04 | 2021-09-07 | 라이트브라더스 주식회사 | Apparatus, method and computer-readable storage medium for tracking usage history vehicle based on blockchain |
| CN114218776A (en) * | 2021-12-03 | 2022-03-22 | 北京星途探索科技有限公司 | Distributed simulation implementation method based on block chain |
| CN114971879A (en) * | 2022-06-17 | 2022-08-30 | 北京极致车网科技有限公司 | Information processing system and information processing method |
| CN115373795A (en) * | 2020-09-18 | 2022-11-22 | 英特尔公司 | Geofence-based edge service control and authentication |
| CN115473908A (en) * | 2022-11-03 | 2022-12-13 | 山东区块链研究院 | Block chain link point fault recovery method and block chain system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111640020B (en) * | 2020-05-22 | 2023-09-19 | 百度在线网络技术（北京）有限公司 | Transaction request processing method, device, equipment and medium in blockchain |
-
2023
- 2023-01-28 CN CN202310102461.9A patent/CN115952237B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105706047A (en) * | 2013-11-11 | 2016-06-22 | 亚马逊科技公司 | Partition-based data stream processing framework |
| CN108776929A (en) * | 2018-04-02 | 2018-11-09 | 成都云创智融科技有限公司 | Bill processing method, system based on block chain database and readable storage medium storing program for executing |
| CN109391684A (en) * | 2018-09-25 | 2019-02-26 | 莆田市烛火信息技术有限公司 | A kind of block chain accounting nodes selection method and system being associated with related chain |
| CN109636492A (en) * | 2018-12-07 | 2019-04-16 | 深圳市智税链科技有限公司 | Tax administration method, apparatus, medium and electronic equipment based on block catenary system |
| CN110851496A (en) * | 2018-12-07 | 2020-02-28 | 深圳市智税链科技有限公司 | Method, apparatus, accounting node and medium for querying transaction information in blockchain network |
| CN111222963A (en) * | 2020-01-16 | 2020-06-02 | 腾讯科技（深圳）有限公司 | Bidding information processing method and device based on block chain |
| CN111769639A (en) * | 2020-06-22 | 2020-10-13 | 积成电子股份有限公司 | Block chain-based power monitoring system key operation record processing method |
| CN115373795A (en) * | 2020-09-18 | 2022-11-22 | 英特尔公司 | Geofence-based edge service control and authentication |
| CN112529703A (en) * | 2020-11-23 | 2021-03-19 | 中国联合网络通信集团有限公司 | Accounting node selection method and device for block chain |
| KR102299030B1 (en) * | 2021-06-04 | 2021-09-07 | 라이트브라더스 주식회사 | Apparatus, method and computer-readable storage medium for tracking usage history vehicle based on blockchain |
| CN114218776A (en) * | 2021-12-03 | 2022-03-22 | 北京星途探索科技有限公司 | Distributed simulation implementation method based on block chain |
| CN114971879A (en) * | 2022-06-17 | 2022-08-30 | 北京极致车网科技有限公司 | Information processing system and information processing method |
| CN115473908A (en) * | 2022-11-03 | 2022-12-13 | 山东区块链研究院 | Block chain link point fault recovery method and block chain system |
Non-Patent Citations (2)
| Title |
|---|
| Introduction to the Tezos Blockchain;Victor Allombert等;《2019 International Conference on High Performance Computing & Simulation (HPCS)》;第1-10页 * |
| 提升事务处理能力的共识算法设计与研究;朱涵仪;《中国优秀硕士学位论文全文数据库 信息科技辑》(第1期);第I138-859页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115952237A (en) | 2023-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107105032B (en) | Node device operation method and node device | |
| CN106878473B (en) | Message processing method, server cluster and system | |
| CN108847982B (en) | Distributed storage cluster and node fault switching method and device thereof | |
| CN103199972B (en) | The two-node cluster hot backup changing method realized based on SOA, RS485 bus and hot backup system | |
| CN110431533B (en) | Method, equipment and system for fault recovery | |
| CN101098260A (en) | Distributed equipment monitor management method, equipment and system | |
| CN106656624B (en) | Optimization method based on Gossip communication protocol and Raft election algorithm | |
| CN100458707C (en) | Method, system and master core and slave core for realizing user configuration | |
| CN109688012A (en) | A kind of method of alliance's chain node hot standby switch | |
| US7124151B1 (en) | Database synchronization apparatus in element management system and method therefor | |
| CN104679796A (en) | Selecting method, selecting device and database mirror image cluster node | |
| CN105224362A (en) | Host computer carries out the method and system of program upgrade to slave computer | |
| CN103530200A (en) | Server hot backup system and method | |
| CN110221938A (en) | The method and storage medium of electronic device, block chain common recognition | |
| CN114268532A (en) | Raft protocol-based election method, distributed system and storage medium | |
| CN105511987A (en) | Distributed task management system with high consistency and availability | |
| CN110162428A (en) | Method of data synchronization and device, electronic equipment and computer readable storage medium | |
| CN107124305A (en) | node device operation method and node device | |
| CN112073250B (en) | Controller cluster fault processing method and device, controller and controller cluster | |
| CN102843259A (en) | Middleware self-management hot backup method and middleware self-management hot backup system in cluster | |
| CN112506702A (en) | Data center disaster tolerance method, device, equipment and storage medium | |
| CN110635941A (en) | Database node cluster fault migration method and device | |
| CN108243031B (en) | Method and device for realizing dual-computer hot standby | |
| CN115952237B (en) | Multi-terminal data fusion system | |
| CN102387210B (en) | Distribution type file system monitoring method based on rapid synchronization network |
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 |