A multi-machine hot backup method for track processing based on local autonomous arbitration

Abstract

The present invention proposes a multi-machine hot backup method for track processing based on local autonomous arbitration, which is applied to radar data processing machines or data fusion systems. The present invention performs the following operations on each track processing machine in the access network: initialize the state and data of the machine; when the machine is in working state, perform point track association, filtering, starting and other track processing on the received point tracks, and publish the generated track data to the network; query the state of the remote machine at every interval Δt, and when the state of the remote machine is in working state and the start time of the remote machine is earlier than the start time of the local machine, the state of the local machine is switched to the backup state; when the state of the remote machine is read twice in a row as the backup state, the state of the local machine is switched to the working state; at the same time, publish the state of the local machine to the network at every interval Δt / 2. This method enables the track machine to maintain the continuity of the system track batch number when its internal module or network is abnormal, providing a more stable and reliable hot backup solution for the system.

Description

Technical Field

[0001] The present invention relates to data processing technology in the field of radar technology, and in particular to hot backup technology for track processing functions. Background Art

[0002] In the process of target track tracking, in order to ensure the continuity and stability of the track, there are often extremely high requirements for the track processor and network stability. However, in actual situations, the processor will inevitably malfunction or even freeze due to overheating or other defects. At this time, if other processors are reopened to process the track, the original target of concern will inevitably be lost. Although there are currently software reconstruction function hot backup methods that can solve the problem of processor damage or freeze, the reconstruction solution will lose the original related data. Therefore, the reconstruction solution can only solve the processing function for streaming data and cannot meet the requirement for continuous track without batch change. In this context, there is a need for a design of a track machine hot backup function that can maintain the continuity of track batch numbers.

[0003] The existing functional hot backup method faces the following main problems: 1) The backup function cannot maintain the continuity of the track batch number; 2) The hot backup function cannot be realized in the case of network fluctuations. Summary of the invention

[0004] In view of the shortcomings of the existing hot backup methods of track machine functions, the present invention provides a multi-machine hot backup method for track processing based on local autonomous arbitration, which solves the problems that the traditional hot backup function cannot maintain the continuity of track batch numbers and cannot realize the hot backup function in the case of network fluctuations, and provides a more stable and reliable hot backup method for track machine functions.

[0005] The present invention proposes a method for hot backup of multiple machines for track processing based on local autonomous arbitration, and the technical solution includes:

[0006] Step 1: Connect multiple track processors to the same network;

[0007] Step 2: Open storage space on the local machine for the local track processor state, record the remote machine state, and record the remote machine track backup data, and initialize them. The local track processor state is initialized to the backup state, the remote machine state is initialized to the backup state, and the track backup data space is initialized to 0;

[0008] Step 3: Receive the working status of the remote machine in the network, and use the received working status and start time of the remote machine to update the remote machine status recorded locally;

[0009] Step 4: Receive the remote aircraft track backup data in the network and store it in the opened storage space;

[0010] Step 5: Receive point track data in real time and determine whether the aircraft is in working state. If the aircraft is in backup state, no processing will be done. If the aircraft is in working state, the received point track will be used for point track association, filtering, starting and other track processing, and the generated track backup data will be published and output to the network.

[0011] Step 6: Read the remote machine state recorded locally at every interval Δt, and reset the stored remote machine state to the backup state. Preferably, the interval Δt is selected as 1 second.

[0012] Step 7: Determine whether the current state of the machine is a working state. If the machine is currently in a working state, proceed to step 8; otherwise, proceed to step 9;

[0013] Step 8: Determine whether the working state is converted to the backup state:

[0014] Step 8.1: Determine whether the remote machine is in working state. If the remote machine is in working state, proceed to the next step. Otherwise, do not process.

[0015] Step 8.2: Determine whether the remote machine startup time is earlier than the local machine startup time. If so, switch the local machine state to the backup state and update the local machine state. Otherwise, do not process.

[0016] Step 9: Determine whether the backup status is changed to the working status:

[0017] Step 9.1: Determine whether the remote machine status read twice in succession is in the backup status. If so, switch the local machine status to the working status, otherwise, do not process;

[0018] Step 9.2: Set the startup time of the machine to the current time and update the state of the machine;

[0019] Step 9.3: Restore the recorded remote aircraft track backup data into a track table for use in local track processing;

[0020] Step 10: Publish the local status to the network at intervals of Δt / 2.

[0021] The present invention designs a multi-machine backup mechanism that performs autonomous decision-making and arbitration locally based on network status monitoring, providing users with a solution for multi-machine seamless access function backup, and achieving continuous and stable working performance of the track machine without batch processing, batch change, or batch loss under network and function abnormalities. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a flow chart of the present invention.

[0023] Figure 2 This is an example diagram of the track machine switching from backup status to working status. DETAILED DESCRIPTION

[0024] The preferred implementation process of the present invention is as follows Figure 1 As shown, the steps include:

[0025] Step 1: Connect multiple track processors to the same network;

[0026] Step 2: Perform the same processing on each track machine, subscribe to the remote machine status and remote machine track backup data locally, open storage space for the local track processing machine status, record the remote machine status, and record the remote machine track backup data, and initialize them. The local track processing machine status is initialized to the backup status, the remote machine status is initialized to the backup status, and the track backup data space is initialized to 0;

[0027] Step 3: Receive the working status of the remote machine in the network, and use the received working status and start time of the remote machine to update the remote machine status recorded locally;

[0028] Step 4: Receive the remote aircraft track backup data in the network and store it in the opened storage space;

[0029] Step 5: Receive point track data in real time and determine whether the aircraft is in working state. If the aircraft is in backup state, no processing will be done. If the aircraft is in working state, the received point track will be used for point track association, filtering, starting and other track processing, and the generated track backup data will be published and output to the network.

[0030] Step 6: Set the interval to 1s, read the remote machine status recorded locally every 1s, and reset the stored remote machine status to the backup status;

[0031] Step 7: Determine whether the current state of the machine is a working state. If the machine is currently in a working state, proceed to step 8; otherwise, proceed to step 9;

[0032] Step 8: Determine whether the working state is converted to the backup state:

[0033] Step 8.1: Determine whether the remote machine is in working state. If the remote machine is in working state, proceed to the next step. Otherwise, do not process.

[0034] Step 8.2: Determine whether the remote machine startup time is earlier than the local machine startup time. If so, switch the local machine state to the backup state and update the local machine state. Otherwise, do not process.

[0035] Step 9: When all the track machines in the network are in backup state, switch one of the track machines to working state through the following operations, such as Figure 2 As shown:

[0036] Step 9.1: Determine whether the remote machine status read twice in succession is in the backup status. If so, switch the local machine status to the working status, otherwise, do not process;

[0037] Step 9.2: Set the startup time of the machine to the current time and update the state of the machine;

[0038] Step 9.3: Restore the recorded remote aircraft track backup data into a track table for use in local track processing;

[0039] Step 10: Publish the machine status to the network every 0.5s.

[0040] The above is only a preferred embodiment of the present invention. It should be pointed out that ordinary technicians in this technical field can make several improvements and modifications without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A multi-machine hot backup method for track processing based on local autonomous arbitration, characterized in that: Step 1: Connect multiple track processors to the same network; Step 2: Open up a record storage space for the local track processor state, remote machine state, and remote machine track backup data on the local machine, and initialize them. The local track processor state is initialized to the backup state, the remote machine state is initialized to the backup state, and the track backup data space is initialized to 0; Step 3: Receive the working status of the remote machine in the network, and use the received working status and start time data of the remote machine to update the local status record area corresponding to the remote machine; Step 4: Receive the track data of the remote aircraft in the network and store it in the local track backup storage space corresponding to the track aircraft; Step 5: Receive point track data in real time and determine whether the aircraft is in working state. If the aircraft is in backup state, no processing will be done. If the aircraft is in working state, the received point track will be processed by point track association, filtering, starting, etc., and the generated track data will be published and output to the network. Step 6: query the status of each remote machine recorded locally at every interval Δt, and reset the stored remote machine status to the backup status; Step 7: Determine whether the current state of the machine is a working state. If the machine is currently in a working state, proceed to step 8; otherwise, proceed to step 9; Step 8: Determine whether the working state is converted to the backup state: Step 8.1: Determine whether the remote machine is in working state. If the remote machine is in working state, proceed to the next step. Otherwise, do not process. Step 8.2: Determine whether the remote machine startup time is earlier than the local machine startup time. If so, switch the local machine state to the backup state and update the local machine state. Otherwise, do not process. Step 9: Determine whether the backup status is changed to the working status: Step 9.1: Determine whether the remote machine status read twice in succession is in the backup status. If so, switch the local machine status to the working status, otherwise, do not process; Step 9.2: Set the startup time of the machine to the current time and update the state of the machine; Step 9.3: Restore the recorded remote aircraft track backup data into a track table for use in local track processing; Step 10: Publish the local status to the network at intervals of Δt / 2.

Images