CN115952237A - Multi-terminal data fusion system - Google Patents
Multi-terminal data fusion system Download PDFInfo
- Publication number
- CN115952237A CN115952237A CN202310102461.9A CN202310102461A CN115952237A CN 115952237 A CN115952237 A CN 115952237A CN 202310102461 A CN202310102461 A CN 202310102461A CN 115952237 A CN115952237 A CN 115952237A
- 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.)
- Granted
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: accounting terminals, target execution terminals and execution terminals of the same block chain; the accounting terminal is used for acquiring user operation requests of at least one terminal in a synchronization period, selecting user operation to be executed in each user operation request, selecting a target execution terminal in each execution terminal to execute the user operation, forming block data of the period according to the user operation sent by the target execution terminal and a corresponding operation result and broadcasting the block data to each terminal, and determining different terminals as the accounting terminals in different synchronization periods; the target execution terminal is used for executing the 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, decentralized data synchronization 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 minimum composition unit of a cluster, namely a central server is installed into two servers which are mutually backed up, and only one server runs at the same time. When one of the running servers fails and cannot be started, the other backup server can be quickly and automatically started and run (generally about several minutes), so that the normal running of the whole network system is ensured. The working mechanism of multi-machine hot standby actually provides a fault automatic recovery capability for the 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 outputs a system processing result depending on a controller. 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, multi-machine redundancy fails, the system cannot normally operate.
Disclosure of Invention
In order to realize decentralized data synchronization and improve the operational reliability of the system, the invention provides a multi-end data fusion system.
In a first aspect, the present invention provides a multi-end data fusion system, including: the accounting terminal, the target execution terminal and the execution terminal are positioned in the same block chain;
the accounting terminal is used for acquiring user operation requests of at least one terminal in a synchronization period, selecting user operation to be executed in each user operation request, selecting a target execution terminal in each execution terminal to execute the user operation, forming block data of the period according to the user operation sent by the target execution terminal and a corresponding operation result and broadcasting the block data to each terminal, and determining different terminals as the accounting terminals in different synchronization periods;
the target execution terminal is used for executing the 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, all the terminals are in the same block chain, different terminals are determined as the accounting terminals in different synchronization periods, and the data synchronization without centralization is realized without depending on any fixed terminal, and when the multi-terminal simultaneously receives the user operation requests, the target execution terminal executes the user operations only after the accounting terminal selects the user operations to be executed, even if the user operation requests received by the multi-terminal have conflicts, the conflicting user requests cannot be confirmed by the accounting terminal, and further cannot be executed by the target execution terminal, so that the data conflicts cannot be generated under the condition that the multi-terminal simultaneously operates.
With reference to the first aspect, in a first embodiment of the first aspect, each terminal in the system corresponds to an effective terminal list, the effective terminal list records information of normal terminals, and the accounting terminal specifies an accounting terminal in a next period according to the effective 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, 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 result of the rest terminals to the synchronous signal, deletes the fault terminal in the effective terminal list, and judges the terminal which does not respond to the synchronous signal in a 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 block height,
each terminal in the system updates the respective effective terminal list according to the block heights of other terminals, judges the terminal smaller than the block height as a fault terminal, judges the terminal consistent with the block height as a normal terminal, deletes the fault terminal in the respective 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 a synchronization period, when an accounting terminal does not broadcast block data of the synchronization period, it is determined that the accounting terminal is faulty, 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 the fifth embodiment of the first aspect, after the fault of the terminal in the fault state is recovered, the historical blockchain data is obtained by any normal terminal until the height of the block of the fault terminal is consistent with the height of the block of the normal terminal, and then the historical blockchain data is added into 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 sums the checksum of the block data of the last cycle and the accumulated sum of the received new block data, the block data passing the checksum verification is valid block data, and each terminal updates its respective block chain 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, when multiple accounting terminals exist in the system, compare the voted votes of the block data of the previous cycle of each accounting terminal, and select the accounting terminal with the highest votes as the final accounting terminal.
With reference to the first aspect, in an eighth embodiment of the first aspect, the block chain data of each terminal in the system includes a creation block, which is used to record 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 used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic structural diagram of a multi-port data fusion system according to an exemplary embodiment;
FIG. 2 is a diagram of a system networking with synchronization by a synchronization pulse signal in one example;
FIG. 3 is a diagram of a system networking scheme with GPS time service synchronization, in one example;
FIG. 4 is a diagram of a system networking 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 system, in one example.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
Furthermore, the technical features involved in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
The block chain is a chain formed by blocks. Each block holds certain information, which are linked in a chain according to the respective generated time sequence. This chain is kept in all servers, and the entire blockchain is secure as long as one terminal can work in the entire system. 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 decentralized data synchronization and improve the running reliability of the system, the invention provides a multi-end data fusion system. As shown in fig. 1, the system comprises a billing terminal 101, a target executive terminal 102 and an executive terminal 103 of the same blockchain;
the accounting terminal 101 is used for acquiring a user operation request of at least one terminal in a synchronization period, selecting user operation to be executed in each user operation request, selecting a target execution terminal 102 in each execution terminal 103 to execute the user operation, forming block data of the period according to the user operation sent by the target execution terminal 102 and a corresponding operation result and broadcasting the block data to each terminal, and determining different terminals as the accounting terminal 101 in different synchronization periods;
the target execution terminal 102 is used for executing the user operation to obtain an operation result and sending the user operation and the corresponding operation result to the accounting terminal 101;
the execution terminal 103 is used for updating the local block chain data according to the block data broadcast by the accounting terminal 101.
Specifically, the accounting terminal 101 and the target execution terminal 102 both belong to the execution terminal 103, the operation capabilities of the execution terminals may be the same or different, the accounting terminal 101 selects the target execution terminal 102 with the operation capability from the terminals according to the user operation request to execute the user operation, and of course, the accounting terminal 101 may also designate itself as the target execution terminal 102, which is not limited specifically here.
Through the system, all the terminals are in the same block chain, different terminals are determined as the accounting terminal 101 in different synchronization periods, decentralized data synchronization is realized without depending on any fixed terminal, and when multiple terminals receive user operation requests at the same time, the target execution terminal 102 executes the user operation only after the accounting terminal 101 selects the user operation required to be executed, even if the user operation requests received by the multiple terminals have conflicts, the conflicting user requests cannot be confirmed by the accounting terminal 101 and further cannot be executed by the target execution terminal 102, so that data conflicts cannot be generated under the condition that the multiple terminals operate at the same time.
In one 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, and the like, and the random number is used as an identification code in the system and is called a terminal ID.
In yet another example, the blockchain data for each terminal in the system includes a founder block for recording an initial state of the system.
Specifically, the created block may be generated by a user operating any terminal, and the initial state of the system is recorded in the created block, which is used as the starting point of the task and is broadcast to all terminals in the system. All user actions are thereafter incrementally changed from this basis.
In an alternative embodiment, the terminal that produces the founder block naturally has the accounting right of 1 st (founder block is 1) and 2 nd. At the accounting 2 time, if there are other terminals in the system, the valid terminal list is not empty at this time, and 1 valid terminal is randomly selected from the valid terminal list as the accounting terminal 101 of the next time. From the 3 rd time onwards, the accounting terminals 101 of the system are each designated by the last accounting terminal. Illustratively, the accounting terminal 101 in the last synchronization period randomly selects a terminal from the terminals as the accounting terminal 101 in the current synchronization period, and then the terminals do not need to compete for the accounting terminal 101 by means of workload or the like, but determine the accounting terminal 101 by means of a 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, it is also possible to select a terminal in the system as the accounting terminal 101 by other means, such as workload certification, right and interest certification, etc., or adopt a manner of taking turns as the accounting 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 effective terminal list, the effective terminal list records information of normal terminals, and the accounting terminal specifies an accounting terminal of a next period according to the effective terminal list.
In one example, each terminal in the system is further configured to receive a synchronization signal, and the terminal receiving the synchronization signal broadcasts a respective user operation request and local blockchain data.
And each terminal determines a fault terminal according to the response result of the rest terminals to the synchronous signal, deletes the fault terminal in the effective terminal list, and judges the terminal which does not respond to the synchronous signal in a synchronous period as the fault terminal.
In the embodiment of the invention, a synchronous signal is added to change an asynchronous system operated by a block chain in the prior art into a synchronous system capable of supporting the operation of the block chain, so that the processing speed of the system is increased, the data can be processed at a millisecond level, people cannot feel delay or pause, and equipment with high real-time requirement can be met.
In an alternative embodiment, the block chain 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 the terminal. After receiving the synchronization signal, each terminal broadcasts a user operation request and local block chain data, and when receiving new block information broadcast by other terminals, each terminal broadcasts its own terminal ID.
For the accounting terminal 101, the broadcasted block data may be each user operation request sent by each terminal, may be a result of the user operation, and may also be a null operation result when there is no user operation and operation result.
In one example, in one synchronization period, when the accounting terminal 101 does not broadcast the block data of this period, it is determined that the accounting terminal 101 is faulty, and the accounting terminal in the previous synchronization period is taken as a new accounting terminal. At this time, the accounting terminal in the previous period should be in the valid terminal list, if the accounting terminal in the previous period is not in the valid terminal list, the accounting terminal in the valid terminal list in the last synchronization period is taken as a new accounting terminal, and the new block in the current period is replaced by a null operation null result.
In an example, the blockchain data includes blockheight, system state, user actions, state changes.
The block height of the system block chain data is consistent with the number of the synchronous signals, each synchronous period forms block data by user operation and corresponding operation results, when no user operation exists or no operation result exists, a null operation null result is used for replacing the user operation null result, the block height is increased by 1 after each synchronous period, and each terminal judges whether the block data are the latest 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 state change generated by the user operation on the system is recorded in the block data to update the system state.
In one example, each terminal in the system updates its respective valid terminal list according to the block height of the other terminals, determines a terminal smaller than the block height of itself as a faulty terminal, determines a terminal consistent with the block height of itself as a normal terminal, deletes the faulty terminal in the respective valid terminal list, and adds the normal terminal to the valid terminal list.
In an optional embodiment, after receiving the block height of the terminal a, the terminal B updates the fault 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 consistent with the block height of the terminal B, and adds the terminal a to the valid terminal list while setting the fault count value of the terminal a to 0 if the terminal a does not exist in the valid terminal list, 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 own effective terminal list; for a terminal whose failure count value exceeds 1, the terminal is considered to be failed, and the failed terminal is removed from the valid 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 another example, after the fault of the terminal in the fault state is recovered, the historical block chain data is obtained by any normal terminal until the block height of the fault terminal is consistent with the block height of the normal terminal, and then the historical block chain data is added into the valid terminal list of each terminal again.
In one example, each terminal in the system performs sum check on the sum of the sum check value of the block data of the last period and 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 the block data is checked through the Hash value, and the validity of the block data is verified by checksum verification in the embodiment of the invention, so that the workload of the system is reduced. The well-known block chain technology needs to use a workload certificate to compete for the accounting right, so an algorithm of 'difficult finding and easy verification' needs to be used, and the accounting terminal 101 in the system is determined in advance without competing for, so that the purpose of verification only needs to be achieved without providing the workload certificate; the block chain operation network set 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 certification, and the data is not required to be worried about falsification; the block chain operation network is set to be a synchronous network, and the bifurcation is avoided without using an algorithm of 'difficult finding and easy verification'; only the block data that passes the sum check is added to the block chain data of each terminal.
In an example, the block chain data further includes a number of votes for the first valid block data, and each terminal in the system is further configured to vote for the first valid block data received, and when a plurality of accounting terminals are present in the system, compare the votes for the block data of one period at each accounting terminal, and select the accounting terminal with the highest votes for the vote number as the final accounting terminal. The number of votes approved is used for the selection of the plurality of accounting terminals 101.
Illustratively, when it is assumed that the terminal a is in an offline state due to a data transmission problem in the system, the terminal a is only in the valid terminal list of the terminal a, and then the terminal a serves as its accounting terminal.
When the execution terminal A recovers the normal state and accesses the system, two accounting terminals, namely an accounting terminal B and an accounting terminal A, of the system appear, and when the two accounting terminals send new block data to the rest terminals in the system in the current synchronization period, the rest terminals in the system compare the votes approved by the user operation of the two accounting terminals in the previous synchronization period, and select the accounting terminal with the larger votes approved as the final accounting terminal. And if the votes are approved to be the same, comparing the currently received user operation number, and selecting the accounting terminal with the large user operation number as the final accounting terminal.
In an example, after receiving the new block data sent by the accounting terminal B, the accounting terminal a detects a conflict, acquires the data of the previous block from the accounting terminal B, compares the data with the data of the previous local block, wins the number of votes approved for the winning, and records the wins of the user operation and the number of votes approved for the winning when the votes approved for the winning are consistent. Illustratively, the number of votes voted for by a block on the bookkeeping terminal B is greater than that of the block on the bookkeeping terminal a, the bookkeeping terminal a gives up the identity of the bookkeeping terminal, acquires historical block data from the bookkeeping terminal B, and rolls back all local data until the local block chain data is consistent with the block chain data at the bookkeeping terminal B. Illustratively, the number of votes complied for in the last block at the accounting terminal a is greater than that in the last block at the accounting terminal B, and the accounting terminal a ignores the new block data from the accounting terminal B.
In an example, after receiving new block data sent by the accounting terminal a, the accounting terminal B and other terminals all detect conflicts, acquire data of a previous block from the accounting terminal a, compare the data with the data of the previous block locally, approve winning with a large number of votes, and record winning with a large number of user operations and results when the approve votes are consistent. Illustratively, the number of votes favored by a block on the accounting terminal a is greater than that of the votes favored by a block on the accounting terminal B, the accounting terminal B gives up the identity of the accounting terminal, acquires the historical block data from the accounting terminal a, and rolls back all local data until the local block chain data is consistent with the block chain data of the accounting terminal a. Illustratively, the number of votes complied for in the last block of the accounting terminal B is greater than that in the last block of the accounting terminal a, and the accounting terminal B ignores the new block data from the accounting terminal a. Illustratively, the number of votes voted for by the last block at the remaining terminal is greater than that of the last block at the accounting terminal a, and the new block data from the accounting terminal a is ignored.
Illustratively, when the number of votes in favor is the same, the user of the accounting terminal a operates to press the button 1 and to press the button 2, and the user of the accounting terminal B operates to press the button 2, the accounting terminal a is selected as the final accounting terminal.
In another example, the operation process of the system can be played back, that is, all user operations are recorded in the blockchain data, and the playback operation process only needs to read 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 of the terminals includes, but is not limited to, using reflective memory cards, ethernet, CAN bus, RS422, RS485, RS232, and like transmission means.
In one example, the synchronization signal received by each terminal includes, but is not limited to, a synchronization pulse signal and a GPS time-service synchronization signal. It should be noted that, no additional synchronization signal may be added, and the local timing of each terminal is relied on, for example, every 1 second, that is, the local second signal plays a role of a synchronization signal, and the embodiment of the present invention is not particularly limited herein.
Fig. 2 is a system networking diagram for synchronizing with a synchronization pulse signal. The physical link in the system adopts a primary-secondary mode, the primary link user communicates normally, and the secondary link is used for block recovery of a fault terminal or backup communication when the primary link fails.
Fig. 3 is a system networking mode diagram for synchronization by GPS time service, and the above diagram CAN be considered when ethernet, CAN bus, and other forms having collision detection and retransmission mechanisms are connected.
Fig. 4 is a diagram of a networking mode of a system with data transmission monitoring, and if the networking mode is considered in an RS422, RS485, RS232 or similar transmission mode, the state of a data line is monitored when each terminal needs to transmit data, and the data is guaranteed to be completely transmitted by software without 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-port data fusion system with differences between executing 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 block chain.
The common terminal 501 is used for collecting user operations, displaying system states, and feeding back operation results to the user. When the user clicks a button or sets a parameter, the general terminal 501 writes the user operation in the operation buffer and broadcasts it to other terminals in the system. When receiving the valid block data from the accounting terminal 504, the general terminal 501 updates the system state and displays the updated system state on the interface. If the operation of setting the parameters by the user is confirmed in the received valid block, the general terminal 501 successfully sets the feedback parameters, and if the parameters set by the user are not confirmed in the valid block, the general terminal 501 fails to set the feedback parameters.
The special operation execution terminal 502 has, in addition to all functions of the general terminal 501, a specific hardware interface that supports the completion of tasks that can be completed by the general terminal 501. Illustratively, the hardware interface includes a serial port, an IO card, a reflective memory card, a power board, and the like, which is not limited herein.
When the system needs to control the external device through the serial port, the system needs to have the serial port communication capability and be connected to the special operation execution terminal 502 of the external device to complete the control successfully, and the ordinary 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 a special operation execution terminal that bears the task of executing the user special operation in one synchronization cycle, and is used for executing the user special operation to obtain an operation result.
Illustratively, the system needs to turn on the 28V power output at the k-th cycle, which is designated to be performed by the target special operation performing terminal 503; the target special operation execution terminal 503 executes a power supply output instruction of turning on 28V in the k +1 th cycle; the 28V power supply outputs stably in the k +3 th period, and the opening output operation is completed; the target special operation execution terminal 503 broadcasts the operation result to other terminals in the k +4 th cycle.
And the accounting terminal 504 is configured to acquire user operation requests from the normal terminal 501, the special operation execution terminal 502, the target special operation execution terminal 503 and the accounting terminal 504 in one synchronization cycle, select and execute a user normal operation to be executed in each user operation request, specify the target special operation execution terminal 503 for executing the user special operation from the special operation execution terminal 502, and generate the block data of the cycle according to the selected user operation and operation result.
The user may send an operation request, such as a request of clicking a button, setting system parameters, etc., at any terminal, each user operation request is stored in an operation buffer area of the system, after the selection confirmation of the accounting terminal 504, the non-special operation is executed by the accounting terminal 504, and the special operation is executed 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 and 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, an accounting terminal 504 generates new block data from the user operation and operation result selected to be executed, and broadcasts the block data to a general terminal 501, a special operation execution terminal 502, and a target special operation execution terminal 503, each terminal updates local block chain data according to the valid block data, and different terminals are determined as the accounting terminal 504 in different synchronization periods.
Fig. 6 is a multi-machine hot standby test and launch 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 accounting terminal is generated in each computer, and the accounting terminal selects a corresponding target execution terminal according to different user operations (namely, the front-end computer or the back-end computer is selected according to different user operations) to execute the user operations.
The front-end computer and the back-end computer equipment A1 to the equipment An are a plurality of computers arranged at the back end, and can be An industrial personal computer, a common computer, or a handheld PDA equipment or a mobile phone (hardware synchronization signals cannot be used when the mobile phone is used), and the equipment B1 to the equipment Bn are a plurality of computers arranged at the front end, and can be An industrial personal computer, a common computer or An embedded equipment. WiFi, ethernet, CAN bus, serial ports in various forms, reflective memory cards and the like CAN be used for networking inside the back-end computers, inside the front-end computers and between the back-end computers and the front-end computers. The cable, optical fiber, wireless data transmission and the like can be selected on the line. The front-end computer, the power distribution transfer box and the power supply combined module CAN be communicated with each other by Ethernet, a CAN bus, serial ports in various forms and the like. The bullet/arrow respectively communicates with the ground telemetering equipment and the power distribution transfer box through ground cables. The communication between the ground telemetering equipment and the front-end computer can adopt Ethernet, serial ports in various forms and the like. When the requirement on the system reliability is strict, a communication link can be added for emergency communication when the network is blocked.
When the real-time performance requirement of the system is higher, the equipment A1 to An and the equipment B1 to Bn can select real-time system expansion and add synchronous signals. The response speed of the system can be reduced to below 50 ms. The user does not feel the time delay when operating. The form of the synchronous signal can be a pulse signal, beidou/GPS time service and the like. When the requirement on the real-time performance of the system is not high, if a user can endure the operation delay of more than 200ms, the hardware synchronization signal can not be added. When the hardware synchronization signal is not added, the timing is started by receiving the block information, and the timing is 200ms as a period, namely the synchronization signal of the software. Generally, the packing and other operations of the blocks can be completed within 100 ms.
It is 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. Also, 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 phrases "comprising a component of' 8230; \8230;" does not exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present 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. A multi-terminal data fusion system is characterized by comprising a billing terminal, a target execution terminal and an execution terminal which are positioned in the same block chain;
the accounting terminal is used for acquiring user operation requests of at least one terminal in a synchronization period, selecting user operations to be executed in the user operation requests, selecting target execution terminals in the execution terminals to execute the user operations, forming block data of the period according to the user operations and corresponding operation results sent by the target execution terminals and broadcasting the block data to the terminals, and determining different terminals as the 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 block chain data according to the block data broadcast by the accounting terminal.
2. The system of claim 1,
each terminal in the system corresponds to an effective terminal list respectively, and the effective terminal list records the information of normal terminals;
and the accounting terminal designates an accounting terminal of the next period according to the effective terminal list.
3. The system of claim 2,
each terminal in the system is also used for receiving a synchronous signal, and the terminal receiving the synchronous signal broadcasts a 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 signal, deletes the fault terminal in the effective terminal list, and judges the terminal which does not respond to the synchronous signal in a synchronous period as the fault terminal.
4. The system of claim 3 wherein the local blockchain data includes a block height,
each terminal in the system updates the respective effective terminal list according to the block heights of other terminals, judges the terminal smaller than the block height of the terminal as a fault terminal, judges the terminal consistent with the block height of the terminal as a normal terminal, deletes the fault terminal in the respective effective terminal list, and adds the normal terminal into the effective terminal list.
5. The system of claim 1,
and in a synchronization period, when the accounting terminal does not broadcast the block data of the period, judging that the accounting terminal is in fault, and taking the accounting terminal in the previous synchronization period as a new accounting terminal.
6. The system of claim 4,
and after the fault of the terminal in the fault state is recovered, acquiring historical block data through any normal terminal, and adding the historical block data into the effective terminal list of each terminal again until the block height of the fault terminal is consistent with the block height of the normal terminal.
7. The system of claim 1,
and each terminal in the system performs sum check on the sum check value of the block data of 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 respective block chain data based on the effective block data.
8. The system of claim 7,
each terminal in the system is also used for approving the received first effective block data, when a plurality of accounting terminals appear in the system, the approving votes of the block data in one period on each accounting terminal are compared, and the accounting terminal with the most approving votes is selected as the final accounting terminal.
9. The system of claim 1, wherein the blockchain data for each terminal in the system comprises a founder block for recording 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 true CN115952237A (en) | 2023-04-11 |
| CN115952237B 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 (14)
| 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 |
| US20210209567A1 (en) * | 2020-05-22 | 2021-07-08 | Baidu Online Network Technology (Beijing) Co., Ltd. | Method and apparatus for processing transaction requests in blockchain, device and medium |
| 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 |
-
2023
- 2023-01-28 CN CN202310102461.9A patent/CN115952237B/en active Active
Patent Citations (14)
| 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 |
| US20210209567A1 (en) * | 2020-05-22 | 2021-07-08 | Baidu Online Network Technology (Beijing) Co., Ltd. | Method and apparatus for processing transaction requests in blockchain, device and medium |
| 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 (3)
| Title |
|---|
| VICTOR ALLOMBERT等: "Introduction to the Tezos Blockchain", 《2019 INTERNATIONAL CONFERENCE ON HIGH PERFORMANCE COMPUTING & SIMULATION (HPCS)》, pages 1 - 10 * |
| 朱涵仪: "提升事务处理能力的共识算法设计与研究", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 1, pages 138 - 859 * |
| 蔚1: "深入浅出区块链", pages 1, Retrieved from the Internet <URL:《https://blog.csdn.net/valada/article/details/79910130》> * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115952237B (en) | 2023-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103199972B (en) | The two-node cluster hot backup changing method realized based on SOA, RS485 bus and hot backup system | |
| CN104335159B (en) | Method, system and the equipment replicated for Separation control | |
| CN107105032B (en) | Node device operation method and node device | |
| CN106878473B (en) | Message processing method, server cluster and system | |
| CN108616566B (en) | Main selection method of raft distributed system, related equipment and system | |
| CN110431533B (en) | Method, equipment and system for fault recovery | |
| CN101098260A (en) | Distributed equipment monitor management method, equipment and system | |
| CN105224362A (en) | Host computer carries out the method and system of program upgrade to slave computer | |
| CN110896356B (en) | Battery management system and communication method in system | |
| CN114268532B (en) | Games method based on Raft protocol, distributed system and storage medium | |
| CN112486740B (en) | Master-slave relationship confirmation method and system among multiple controllers and related device | |
| CN108243031B (en) | Method and device for realizing dual-computer hot standby | |
| CN102387210B (en) | Distribution type file system monitoring method based on rapid synchronization network | |
| CN115952237B (en) | Multi-terminal data fusion system | |
| CN114726867A (en) | Hot standby multi-master method based on Raft | |
| KR102285882B1 (en) | Blockchain consensus method based on variable quorum, blockcahin node device and program using the same | |
| CN106712887A (en) | Network clock protocol-based master-slave state synchronization method | |
| CN100530106C (en) | Method for implementing kernel of multi-machine fault-tolerant system | |
| CN115987999A (en) | Master-slave competition method and device for multi-machine system, ARM and storage medium | |
| CN112433968B (en) | Controller sharing synchronization method and device | |
| CN111475440A (en) | Communication control method and device based on asynchronous transmission protocol and electronic equipment | |
| CN115208712B (en) | Control method, cell stack management system, device and medium | |
| CN116909759B (en) | Information processing method, device and equipment, medium and controller cluster | |
| CN117555688A (en) | Data processing method, system, equipment and storage medium based on double active centers | |
| KR100771915B1 (en) | Digital protection relay and communication duplex method |
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 |