A high-precision software timing sending system time mark and data synchronization method

Abstract

The application provides a high-precision software timing sending system time mark and data synchronization method. Under the condition that timing cannot be avoided and time intervals are close to the sending rule, a timing design strategy is used to take the relatively independent post-sending equipment in timing management as a base point, organize all measured data in the same communication cycle, and mark the method of the related time mark with the time mark of the central control equipment as a reference, so that the time mark and the data are completely synchronized.

Description

Technical Field

[0001] This invention belongs to the field of timing design for multi-device Ethernet software timed transmission, and specifically relates to a method for synchronizing time stamps and data in a high-precision software timed transmission system. Background Technology

[0002] An integrated system comprising multiple devices communicates via Ethernet using a timed transmission mechanism. Under the control of a unified clock pulse signal, each device sends its message at a predetermined time according to specified timing requirements. Generally, once the system timing is established, constrained by the unified clock pulse and the time-sharing agreement among the devices, the transmitted data and the timestamps contained in the corresponding messages will not be out of sync. However, in certain special cases, where multiple messages are required to be sent simultaneously at the arrival of a unified clock signal (time synchronization signal) or at close intervals, differences in the hardware reception of the time synchronization signal by each device, as well as resource allocation and task scheduling during software operation, can cause message transmission time drift, ultimately leading to asynchrony between the transmitted data and the timestamps contained in the corresponding messages.

[0003] This phenomenon occurs when the message data is correct but the timestamp is incorrect. It will not cause system task abnormalities, but it will directly affect the subsequent data processing and accuracy evaluation results of the system.

[0004] For example: A weapon system includes fire control equipment, optoelectronic equipment, radar equipment, artillery equipment, and timing equipment. Each device establishes timing communication based on Ethernet and timing pulses. The connection relationships between the devices in the system are as follows: Figure 1 As shown. Among them, the timing equipment provides the system with quasi-second pulses and Beijing time, and the fire control equipment receives the quasi-second pulses and Beijing time, and provides the system's various devices with time synchronization pulse signals and time stamp data at fixed intervals of 10ms through its internal time synchronization unit.

[0005] According to the communication protocol requirements of this weapon system, the fire control equipment, optoelectronic equipment, radar equipment, and artillery equipment adopt a 10ms timed transmission mechanism. The fire control equipment and artillery equipment are controlled by a timing pulse signal for synchronized transmission. Every 10ms, the fire control equipment sends control message data to the artillery, optoelectronic, and radar equipment at time 0, assigning the message the fire control time stamp of time 0. Every 10ms, the artillery equipment sends a status message (target position) data to the fire control equipment at time 0, assigning the message the current fire control time stamp received. Every 10ms, the optoelectronic equipment sends a status message (target deviation) data at time 0 to the fire control equipment at time 1ms, assigning the message the current fire control time stamp received. Every 5ms, the radar equipment sends a status message (target tracking) data at time 0 to the fire control equipment, assigning the message the current fire control time stamp received. See the specific timing sequence for details. Figure 2 As shown.

[0006] However, during the experiment, it was found that the message sending time of each device's hardware timing board exhibited a slight drift, which varied with changes in external environmental factors and device batch status. Additionally, message sending time drift was also caused by resource allocation and task scheduling during software operation. When organizing time stamp information in optoelectronic and artillery equipment, the slight variations in message sending time caused system timing changes, along with the critical time taken to process the time stamp information, resulted in the time stamp sometimes being assigned the current period's fire control time stamp and sometimes the previous period's fire control time stamp, leading to a time stamp and data asynchrony. This negatively impacted subsequent system data processing and accuracy assessment. The following is the timing relationship recorded by third-party monitoring software, such as... Figure 3 , Figure 4 As shown, where Figure 3 This is a normal time-scaled diagram; the time scales for photoelectric equipment, artillery, and radar within each cycle are the same as the time scales for fire control equipment within that cycle. Figure 4 The diagram shows abnormal timescales. The radar timescales are correct. At 0ms, the timescales of the photoelectric and artillery are the same as the timescales of the fire control equipment within the same period, which is a normal timescale state. At 10ms and 20ms, the fire control message transmission time is shifted relative to the photoelectric and artillery timescales. The timescales of the photoelectric and artillery are different from the timescales of the fire control equipment within the same period, which is an abnormal timescale state.

[0007] To address the aforementioned issue of time stamp and data asynchrony, the traditional method involves using third-party software to monitor the data, followed by manually reading the measured data timing sequence containing the time stamp. The differences between the timing sequence of most of the data and the specified transmission timing are calculated to obtain the time stamp deviation. Then, the time stamps of all data from each device are roughly corrected according to this deviation. For example... Figure 4 The timescales for the electro-optical system and artillery at 10ms and 20ms differed from the specified timescale by 10ms, but the timescale at 0ms was correct. During the correction process, most data were similar to the 10ms and 20ms timestamps, so a uniform 10ms increment was added to the original timescale. After correction, the timescales for the electro-optical system and artillery at 10ms and 20ms were correct, but the timescale at 0ms was incorrectly corrected. Using this synchronization method for subsequent system data processing and accuracy evaluation resulted in poor accuracy and ease of use. Summary of the Invention

[0008] To address the issue of timescale and data synchronization and achieve complete synchronization between them, thereby ensuring the accuracy and effectiveness of subsequent data processing and precision assessment, this paper proposes a method that, under conditions where timing synchronization rules and closely spaced time intervals are unavoidable, uses a relatively independent post-transmission device in timing management as a base point. All measured data is organized within the same communication cycle, and the relevant timescales are based on the timescale of the central control device, thus ensuring complete synchronization between the timescale and data. This method effectively and conveniently solves problems related to precision assessment caused by timescale and data asynchrony within the system.

[0009] The technical solution of this invention is: a method for synchronizing time stamps and data in a high-precision software-timed transmission system, comprising the following steps:

[0010] Step 1: Based on the system timing relationship, select the last transmitted data packet within a period as the base point marker;

[0011] Step 2: Starting from the base point marker in Step 1, package all data packets after the base point marker, and take the data packet that is received again at the base point marker as the endpoint to complete the data collection for one cycle interval; Step 3: Within this cycle, use the time stamp of the central control device as the time stamp of all data within this cycle;

[0012] Step 4: Repeat steps 1 to 3 to complete the time stamp and data synchronization of all periodic measured data reports.

[0013] Furthermore, in step 2, the data packets packaged after the base point marker do not include the base point marker of the starting point.

[0014] Furthermore, in step 2, the data packets packaged after the base point marker include the base point marker of the destination.

[0015] Invention Effects

[0016] The technical effect of this invention is that, under the condition that timing synchronization rules and close time intervals cannot be avoided, this method organizes all the measured data within the same communication cycle based on the timing design strategy, taking the relatively independent post-transmission device in timing management as the base point, and the relevant time stamp is marked with the time stamp of the central control device as the reference, so that the time stamp and the data are completely synchronized.

[0017] In this invention, during the data processing and parsing phase, based on the system's timing relationship, a data frame is started by using the data packet sent by the radar to the fire control equipment as a base point marker. Subsequent data packets are then packaged together, and the process ends with the receipt of the same data packet, completing a 10ms cycle of data acquisition. The timestamp of the fire control equipment sending data to the artillery equipment is used as the timestamp for all data within this record. This cycle is repeated for each period, synchronizing the timestamps of all measured data packets with the data for all cycles.

[0018] This method can effectively solve the problem of time stamp and data asynchrony caused by factors such as equipment batch status, environmental changes, and software message transmission time drift.

[0019] This invention is also applicable to integrated systems consisting of multiple Ethernet devices in civilian applications. Attached Figure Description

[0020] Figure 1Connection diagram of main equipment of a certain weapon system

[0021] Figure 2 Data transmission timing management diagram of a certain weapon system

[0022] Figure 3 Normal time scale diagram of a certain weapon system

[0023] Figure 4 Anomaly timescale annotation diagram of a certain weapon system

[0024] Figure 5 Time series and time scale relationship diagram after time scale and data synchronization of a certain weapon system

[0025] Figure 6 Error curves for two methods of electro-optical data accuracy processing in a certain weapon system are shown in Figure (a) for range error, (b) for azimuth error, and (c) for elevation error. Detailed Implementation

[0026] The following section continues to use the aforementioned weapon system as an example. By refining the technical solution and from a software engineering perspective, specific implementation methods are proposed. These methods are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.

[0027] This invention is a high-precision software-timed transmission system time stamp and data synchronization method, specifically including the following steps:

[0028] Step 1: Based on the system timing relationship, fire control equipment, artillery equipment, and optoelectronic equipment transmit data when they approach the timing signal within a 10ms cycle, with the radar equipment transmitting data last. Figure 2 As shown, the last relatively independent message sent within the cycle, i.e. the data message sent by the radar equipment to the fire control equipment, is selected as the base point marker.

[0029] Step 2: Package all data packets after the radar sends the message, and complete a 10ms periodic data acquisition with the receipt of the data packet as the endpoint. This includes fire control messages sent by the artillery, fire control messages sent by the electro-optical system, and fire control messages sent by the radar.

[0030] Step 3: Assign the timestamp sent by the fire control equipment to all data packets within this period, that is, to the fire control messages sent by the artillery, the fire control messages sent by the optoelectronic equipment, and the fire control messages sent by the radar (endpoint). This timestamp will overwrite the timestamp in the original message.

[0031] Repeat steps one through three in a loop to complete the time-stamp and data synchronization of all periodic measured data reports. The time sequence and time-stamp relationship after synchronization are shown in [link to documentation]. Figure 5 As shown. From Figure 5 and Figure 4The comparison shows that both methods exhibit the following issues: the radar time stamp is correct, the fire control message sent at 0ms is before the electro-optical and artillery signals (normal state), and the fire control message sent at 10ms and 20ms is delayed relative to the electro-optical and artillery signals (abnormal state). However, after adopting the time stamp and data synchronization method of this invention, Figure 5 The photoelectric and artillery timescales at 10ms and 20ms are the same as the fire control equipment timescales within that cycle, which is normal. That is, the photoelectric, artillery, radar, and fire control timescales are identical within each cycle. Therefore, it can be seen that... Figure 5 and Figure 3 This represents a consistent normal time scale, meaning that the time scales of all devices are the same within each cycle.

[0032] Invention effect verification status:

[0033] The system time stamp and data synchronization are mainly used in later data processing and system accuracy assessment. The following uses accuracy assessment as an example to verify the effectiveness and accuracy of the invention.

[0034] For weapon systems, accuracy assessment is a crucial step, primarily achieved by comparing measured data with true data at the same timescale to obtain the system's first-order difference. This necessitates synchronization between the measured data and the timescale. In the aforementioned weapon system, the first-order difference calculated using traditional, complex manual processing of optoelectronic data is compared with the first-order difference calculated using this invention. The error is as follows: Figure 6 As shown in Table 1, the error statistics are as follows.

[0035] Depend on Figure 6 It can be seen that:

[0036] 1) In the "distance error" curve, the horizontal axis represents the true distance of the target when the weapon system uses electro-optical tracking, and the vertical axis represents the difference between the first difference calculated using traditional methods after complex manual processing of the electro-optical data and the first difference calculated by this invention. This value is within ±0.01m, indicating that the difference between the two methods is very small.

[0037] 2) In the "azimuth error" curve, the horizontal axis represents the true distance of the target when the weapon system uses electro-optical tracking, and the vertical axis represents the difference between the first azimuth error calculated using traditional methods and the first azimuth error calculated by this invention. This value is within ±0.015 mrad (milliradians), indicating that the difference between the two methods is very small.

[0038] 3) In the "Pitch Angle Error" curve, the horizontal axis represents the true distance of the target when the weapon system uses electro-optical tracking, and the vertical axis represents the difference between the pitch angle error calculated using traditional methods and the pitch angle error calculated by this invention. This value is within ±0.02 mrad (milliradians), indicating that the difference between the two methods is very small.

[0039] Table 1. Error statistics of two methods for processing optoelectronic data of a certain weapon system.

[0040] error Total points System difference Standard deviation Distance error (m) 12846 1.58353E-6 0.00298 Azimuth error (mrad) 12846 -8.16908E-7 0.00198 Pitch angle error (mrad) 12846 -9.90198E-5 0.00343

[0041] Depend on Figure 6 As shown in Table 1, the difference between the method of the present invention and the traditional method is very small. It can effectively replace the traditional method and avoid the problems of complex processing, poor accuracy, and poor ease of use brought about by the traditional method.

[0042] The method of this invention is based on a timing design strategy. Under the condition that there are unavoidable timing synchronization rules and short intervals in a high-precision software timing transmission system, all the measured data are organized within the same communication cycle based on the relatively independent post-transmission device in timing management. The relevant time stamps are marked with the time stamps of the central control device as the reference, so that the time stamps and data are completely synchronized.

[0043] This method can effectively solve the problem of time stamp and data asynchrony caused by factors such as equipment batch status, environmental changes, and software message transmission time drift.

[0044] This method is based on timing design and is suitable for high-precision fixed-period transceiver systems. It provides a novel approach for synchronizing the time stamp of measured data, allowing designers to avoid excessive consideration of the time stamp and data synchronization issues in later data processing when performing timing design.

[0045] This invention is applicable not only to weapon systems, but also to integrated systems composed of multiple Ethernet devices in civilian applications.

[0046] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention without departing from the principles and spirit of the present invention.

Claims

1. A method for synchronizing time stamps and data in a high-precision software-timed transmission system, characterized in that, Includes the following steps: Step 1: Based on the system timing relationship, that is, the fire control equipment, artillery equipment, and optoelectronic equipment send data when they are close to the timing signal within a 10ms cycle, and the radar equipment sends data last, select the last data report sent within a cycle as the base point marker. Step 2: Starting from the base point marker in Step 1, package all data packets after the base point marker into a single packet, and take the data packet that is received again from the base point marker as the endpoint to complete a 10ms periodic data acquisition; including fire control messages sent by artillery, fire control messages sent by electro-optical systems, and fire control messages sent by radar. Step 3: Within this cycle, use the time stamp of the central control equipment as the time stamp of all data within this cycle; assign the time stamp sent by the fire control equipment to the artillery equipment to all data packets within this cycle, that is, assign it to the fire control messages sent by the artillery, the fire control messages sent by the optoelectronic equipment, and the fire control messages sent by the radar. This time stamp covers the time stamp in the original message; Step 4: Repeat steps 1 to 3 to complete the time stamp and data synchronization of all measured data packets in all cycles.

2. The method for synchronizing time stamps and data in a high-precision software-timed transmission system as described in claim 1, characterized in that, In step 2, the data packets packaged after the base point marker do not include the base point marker of the starting point.

3. The method for synchronizing time stamps and data in a high-precision software-timed transmission system as described in claim 1, characterized in that, In step 2, the data packets following the base point marker are packaged together, including the base point marker of the destination.

Images