Data interaction software architecture with foreground and background separated

Abstract

The invention discloses a foreground and background separated data interaction software architecture, which comprises a data interaction foreground process and a data interaction background process, and the data interaction foreground process and the data interaction background process are respectively arranged in different software systems; the data interaction background process comprises a network receiving thread, a data processing thread, a network sending thread, a data statistics thread, a network receiving data recording thread, a network sending data recording thread, a 20Hz processing thread and a 1Hz processing thread, and sends data to the foreground thread. The method is well applied to data interaction software of multiple types of radars, multiple types of computer software and hardware are adapted, stable communication between the radars and center and external equipment is achieved, and basic functions such as track reporting and guide issuing are achieved.

Description

Technical Field

[0001] The present invention belongs to the technical field of display control, and in particular relates to a data interaction software architecture with foreground and background separation. Background Art

[0002] Radar data interaction software has always been an important part of radar equipment. As the only node connecting the command center and the radar, it realizes important functions such as on-demand reporting of radar data and real-time response to central control commands.

[0003] Usually, data interaction software realizes the data receiving and sending control, processing and display functions in one process. With the full popularization of computer CPU, graphics card and operating system domestication in the military field, the machine processing performance has declined to a certain extent. At the same time, with the increasing number of center users and the continuous development of radar technology, data protocols are becoming more diversified and functional requirements are becoming more complex, resulting in the gradual reduction of the reusability of data interaction software. At the same time, there are also different degrees of freezes, abnormal sending and receiving data and other faults. We urgently need to design a set of data interaction software that is both stable and reliable, adaptable to various types of computer hardware and software environments, and meet the different functional requirements of multiple radars and multiple centers. It can quickly adapt to various types of data protocols, which can not only ensure the normal communication of data between radars and centers, but also realize the rapid reuse of software. Summary of the invention

[0004] In order to solve the above problems, the present invention proposes a data interaction software architecture with front-end and back-end separation, including a data interaction foreground process and a data interaction background process, which are respectively established in different software systems; the data interaction background process includes a network receiving thread, a data processing thread, a network sending thread, a data statistics thread, a network receiving data recording thread, a network sending data recording thread, a 20Hz processing thread and a 1Hz processing thread, and a data sending to the foreground thread;

[0005] The network receiving thread, data processing thread and network sending thread are responsible for receiving, processing and sending data; the data statistics thread is responsible for generating statistical information of each site type data; the network receiving and sending data recording threads are responsible for sending data to the external data recording software, and the 20Hz and 1Hz processing threads are used for timing processing to generate track and guide interpolation data, and send data to the foreground thread for communication with the data interaction foreground process;

[0006] The data interaction foreground process is responsible for displaying data and realizing the control functions of track reporting and guidance issuance.

[0007] Furthermore, the data interaction background process also includes a status monitoring thread and a boot file loading thread. The status monitoring thread is used to obtain the status data of the data statistics thread and send it to the foreground thread; the boot file loading thread is used to read the file boot data and generate the boot data after interpolation processing by the 20Hz processing thread.

[0008] Furthermore, the data interaction foreground process specifically includes track data display and reporting control functions, which are used to receive the track data generated by the data interaction background process, display the track data in the form of tables and curves, and realize target reporting control at the same time.

[0009] Furthermore, the data interaction foreground process specifically includes guidance data display and distribution control functions, which is used to receive guidance data generated by the data interaction background process, display center guidance, equipment mutual guidance and theoretical guidance data in the form of tables and curves, and realize guidance distribution control at the same time.

[0010] Furthermore, the data interaction foreground process specifically includes a communication parameter setting function, which is used to set the communication parameters of all communication nodes, including network receiving parameters, network sending parameters, whether messages are sent or received, whether data is interpolated, and the interpolation frequency. After being saved in the configuration file, it is used by the data interaction background process.

[0011] Furthermore, the data interaction foreground process specifically includes a communication status monitoring function, which is used to receive data statistical information generated by the data interaction background process, and display the sending and receiving status of various types of data at each site in real time, including the total number of packets, the number of lost packets, the number of error packets, the total traffic and speed.

[0012] Furthermore, the data interaction foreground process specifically includes an operation log display function, which is used to receive and display in real time the operation log information generated by the data interaction background process, and simultaneously display the operation log information of the data interaction foreground process.

[0013] Furthermore, the communication between the data interaction front and data interaction background processes is realized by sending and receiving data via UDP. The data interface design between the two includes:

[0014] 1) Track data

[0015] The data interaction background process converts various types of track data into a unified track data interface, including the target's time, position, speed, status, and recognition results, and sends it to the data interaction foreground process;

[0016] 2) Bootstrapping Data

[0017] The data interaction background process converts the guidance data of the center and the mutual guidance data of each equipment into a unified guidance data interface, including the time, position, and speed of the target, and sends it to the data interaction foreground process;

[0018] 3) Communication status

[0019] The data interaction background process counts the network receiving data and network sending data respectively, generates unified communication status data, and sends it to the data interaction front-end process. The unified communication status data includes the total number of packets, number of lost packets, number of error packets, total traffic and speed;

[0020] 4) Log information

[0021] The data interaction background process sends the log information generated during the operation to the data interaction foreground process through a unified log information interface;

[0022] 5) Time information

[0023] The data interaction background process sends the local time, T0 time, and relative time to the data interaction front-end process through a unified time information interface;

[0024] 6) Track reporting control instructions

[0025] The track reporting control command interface includes automatic reporting / manual reporting, batch reporting / cancellation reporting. After receiving the command, the data interaction background process updates the local reporting rules.

[0026] 7) Guide and issue control instructions

[0027] The guidance and delivery control command interface includes guidance / cancellation. After receiving the command, the data interaction background process updates the local guidance and delivery rules.

[0028] 8) T0 time setting

[0029] After the data interaction foreground process sets the T0 time, it sends the T0 time setting command to the background. After receiving the command, the background updates the T0 time information.

[0030] 9) Statistics clearing command

[0031] After receiving the statistics clearing command, the data interaction background process clears the statistics.

[0032] Furthermore, the data received by the network receiving thread, data processing thread and network sending thread come from the data interaction foreground process, external sites and local radar.

[0033] Compared with the prior art, the present invention has the following advantages:

[0034] 1. Stable and reliable: Data transmission and reception processing functions and data display functions are implemented in different processes. The data interaction background process is basically not affected by the performance of computer hardware and software such as the operating system, CPU, and graphics card, ensuring normal communication with the center and external equipment. The data interaction foreground process is only responsible for data display and control functions. Compared with previous software, it reduces data analysis packaging, calculation, interpolation, interrupt response and other functions, greatly enhancing the stability of the data interaction software;

[0035] 2. High reusability: The software framework is applicable to various computer hardware and software, and has the ability to communicate with multiple centers at the same time. It also has common track, guidance data display, parameter setting, status monitoring, operation log display and other functions, and can be applied to various radars;

[0036] 3. Perfectly cope with complex and ever-changing display requirements: In the face of different display requirements, you only need to modify the data interaction foreground process, which will not affect the correctness of the external data interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 This is a data flow diagram of the background process of data interaction before data interaction in an embodiment of the present invention.

[0038] Figure 2 This is a diagram of the front data interaction background process communication interface of an embodiment of the present invention.

[0039] Figure 3 This is a configuration diagram of communication parameters of the background process for front-end data interaction according to an embodiment of the present invention.

[0040] Figure 4 This is an example diagram of the basic communication parameter configuration of the radar according to an embodiment of the present invention.

[0041] Figure 5 This is an example diagram of station communication parameter configuration according to an embodiment of the present invention.

[0042] Figure 6 This is a general track display and reporting control interface of an embodiment of the present invention.

[0043] Figure 7 It is a general guidance display and sending control interface of an embodiment of the present invention.

[0044] Figure 8 This is a general parameter configuration interface of an embodiment of the present invention.

[0045] Fig. 9 This is a general status monitoring interface of an embodiment of the present invention. DETAILED DESCRIPTION

[0046] The purpose of the present invention is to design a data interaction software that can adapt to various computer hardware and software environments, meet the different functional requirements of multiple radars and multiple centers, and quickly adapt to various types of data protocols. Through the separation of front-end and back-end design, on the one hand, the software development efficiency is improved, and on the other hand, the decoupling of data reception and transmission processing and data display is realized. The data interaction background process is responsible for realizing key functions such as data reception and transmission, distribution calculation, parsing encapsulation and interpolation calculation. The data interaction foreground process is responsible for data display, parameter setting, status monitoring and control of some instructions, which greatly improves the stability and reusability of the software.

[0047] In order to facilitate understanding of the present application, the present application will be described more fully below with reference to the relevant drawings. Embodiments of the present application are provided in the drawings. However, the present application can be implemented in many different forms and is not limited to the embodiments described herein. On the contrary, the purpose of providing these embodiments is to make the disclosure of the present application more thorough and comprehensive.

[0048] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0049] It can be understood that the terms "first", "second", etc. used in the present application can be used in this article to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from another element.

[0050] Spatially relative terms such as "under," "beneath," "below," "under," "above," "above," and the like may be used herein to describe the relationship of an element or feature shown in the figures to other elements or features. It should be understood that, in addition to the orientations shown in the figures, spatially relative terms also include different orientations of the device in use and operation. For example, if the device in the accompanying drawings is flipped, an element or feature described as "under other elements" or "under it" or "under it" will be oriented as being "above" the other elements or features. Thus, the exemplary terms "under" and "under" may include both upper and lower orientations. In addition, the device may also include additional orientations (e.g., rotated 90 degrees or other orientations), and the spatial descriptors used herein are interpreted accordingly.

[0051] It should be noted that when an element is considered to be "connected" to another element, it can be directly connected to the other element, or connected to the other element through an intermediate element. In addition, the "connection" in the following embodiments should be understood as "electrical connection", "communication connection", etc. if there is transmission of electrical signals or data between the connected objects.

[0052] When used herein, the singular forms "a", "an", and "said / the" may also include plural forms, unless the context clearly indicates otherwise. It should also be understood that the terms "include / comprise" or "have" and the like specify the presence of stated features, wholes, steps, operations, components, parts, or combinations thereof, but do not exclude the possibility of the presence or addition of one or more other features, wholes, steps, operations, components, parts, or combinations thereof. At the same time, the term "and / or" used in this specification includes any and all combinations of the relevant listed items.

[0053] In order to make the purpose, technical solution and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0054] This embodiment provides a data interaction software architecture with separated front-end and back-end. The front-end data interaction and back-end process functions are designed separately, and the processes communicate over the network through fixed data interfaces, providing a basic software framework for data interaction software of multiple types of radars.

[0055] 1. Design of data interaction background process function

[0056] The data communication and data processing functions with the superior center, external equipment and local radar are all implemented in the data interaction background process, which mainly includes the following functions:

[0057] 1) Data Reception

[0058] The function of receiving internal and external network message data and data interaction foreground process control instructions in real time through multi-threading technology.

[0059] 2) Data transmission

[0060] Through multi-threading technology, the function of sending message data to the internal and external networks and sending analysis results and status information to the data interaction foreground process is realized.

[0061] 3) Data processing

[0062] The data parsing and encapsulation functions are realized through multi-threading technology. The data is distributed and calculated according to the forwarding rules generated by the configuration file. The data is interpolated at multiple data rates according to the center's needs. The data is classified and processed according to the data processing type. At the same time, it is determined whether the data is sent to the data interaction foreground process and whether the data needs to be recorded, and the data is placed in the corresponding processing thread queue.

[0063] 4) Data statistics

[0064] Statistics on the sending and receiving of each type of messages at each site.

[0065] The detailed data flow relationship between each functional thread is as follows Figure 1 As shown:

[0066] Figure 1 The general data flow and processing process is shown. The network receiving thread, data processing thread and network sending thread are the main threads, responsible for receiving (from the data interaction foreground process, external sites, local radar), processing and sending data; the data statistics thread is responsible for generating statistical information of each site type data, the network receiving and network sending data recording threads are responsible for sending data to the data recording software, and the 20Hz and 1Hz processing threads are used to periodically process the interpolation data sent by the data processing thread and send data to the foreground thread for communication with the data interaction foreground process. The status monitoring thread is used to obtain the status data of the data statistics thread and send it to the foreground thread; the boot file loading thread is used to read the file boot data, and generate the boot data for sending after interpolation processing by the 20Hz processing thread.

[0067] 2. Functional design of data interaction foreground process

[0068] The data interaction foreground process is mainly responsible for the display of data, and at the same time realizes the control functions of track reporting and guidance issuance, as well as some auxiliary functions such as parameter setting, status display, log display, etc.

[0069] 1) Track data display and reporting control

[0070] Receive the track data generated by the data interaction background process, display the radar detection track data in the form of tables and curves, and realize the reporting control of the target at the same time.

[0071] 2) Guide data display and control

[0072] Receive the guidance data generated by the data interaction background process, display the center guidance, equipment mutual guidance and theoretical guidance data in the form of tables and curves, and realize the guidance issuance control at the same time.

[0073] 3) Communication parameter settings

[0074] The communication parameters of all communication nodes can be flexibly set, including network receiving parameters (dual routing), network sending parameters (dual routing), whether messages are sent and received, whether data is interpolated, interpolation frequency, etc., which can be saved in the configuration file and used by the data interaction background process.

[0075] 4) Communication status monitoring

[0076] The background process of receiving data interaction generates data statistics, which displays the sending and receiving status of various types of data at each site in real time, including the total number of packets, number of lost packets, number of error packets, total traffic and speed, etc.

[0077] 5) Operation log display

[0078] Receive and display in real time the operation log information generated by the data interaction background process, and display the operation log information of the data interaction foreground process.

[0079] 3. Design of front-end and back-end data interfaces

[0080] Because data interaction usually has a master-slave design, the software is deployed on two computers. The communication between the front and back processes of data interaction is realized by sending and receiving data through UDP. The main interfaces of the front and back are as follows: Figure 2 As shown:

[0081] 1) Track data

[0082] The data interaction background process converts the track data of various types of radars into a unified track data interface, including the target's time, position, speed, status, recognition results and other information, and sends it to the data interaction foreground process

[0083] 2) Bootstrapping Data

[0084] The data interaction background process converts the guidance data of the center and the mutual guidance data of each equipment into a unified guidance data interface, including the time, position, speed and other information of the target, and sends it to the data interaction front-end process

[0085] 3) Communication status

[0086] The data interaction background process counts the network receiving data and network sending data respectively, generates unified communication status data, total number of packets, number of lost packets, number of error packets, total traffic and speed, and sends it to the data interaction front-end process

[0087] 4) Log information

[0088] The data interaction background process sends the log information (including operation logs and error logs) generated during the operation to the data interaction front-end process through a unified log information interface.

[0089] 5) Time information

[0090] The data interaction background process sends the local time, T0 time, and relative time to the data interaction front-end process through a unified time information interface.

[0091] 6) Track reporting control instructions

[0092] The track reporting control command interface includes automatic reporting (all reporting) / manual reporting (not all reporting), batch reporting / cancellation reporting. After receiving the command, the data interaction background process updates the local reporting rules.

[0093] 7) Guide and issue control instructions

[0094] The guidance and delivery control command interface includes guidance / cancellation guidance. After the data interaction background process receives the command, it updates the local guidance and delivery rules.

[0095] 8) T0 time setting

[0096] After the data interaction foreground process sets the T0 time, it sends the T0 time setting command to the background. After receiving the command, the background updates the T0 time information

[0097] 9) Statistics clearing command

[0098] After receiving the statistics clear command, the data interaction background process clears the statistics

[0099] 4. Configuration file design

[0100] 1) Communication parameter configuration of the background process for front-end data interaction

[0101] Configure the communication parameters between the front and back ends, such as Figure 3 shown.

[0102] 2) Radar basic communication parameter configuration

[0103] Configure radar location, station number, IP address and other information, such as Figure 4 shown.

[0104] 3) Site communication parameter configuration

[0105] Configure the location of each site, data protocol, station number, communication type, network receiving parameters, network sending parameters, receiving and sending information and other parameters, such as Figure 5 shown.

[0106] 5. Interface design

[0107] Combined with the data interaction software of multiple radars, common display elements are extracted. The data interaction foreground process mainly includes the following interfaces

[0108] 1) General track display and reporting control interface

[0109] The track display interface contains the target's batch number, time, position, speed, reporting status and other basic information. At the same time, the track can be reported in full or in batches, such as Figure 6 shown.

[0110] 2) General guidance data display and distribution control interface

[0111] The guidance data display interface contains basic information such as the source, location and time of the guidance target, and can also control the guidance target, such as Figure 7 shown.

[0112] 3) General parameter configuration interface

[0113] The parameter configuration interface configures the network receiving and sending parameters of each site as well as the data parameter information received and sent, such as Figure 8 shown.

[0114] 4) General log information display interface

[0115] Displays the running log and operation log content of the background process of data interaction before, including basic information such as time, level, content, etc. Fig. 9 shown.

[0116] This embodiment has been well applied in the data interaction software of various radars, adapted to various computer hardware and software, achieved stable communication between radar and center as well as external equipment, and realized basic functions such as track reporting and guidance issuance.

[0117] The final form submitted in this embodiment is data interaction front-end software and data interaction back-end software. The final product form is two complete and independent software projects. If used in different CPUs, operating systems or compilation environments, they can be used by recompiling. The development platform of the data interaction software (front-end and back-end) adopts Qt5.9.0.

[0118] Compared with the prior art, the present invention has the following significant advantages:

[0119] 1. Stable and reliable: Data transmission and reception processing functions and data display functions are implemented in different processes. The data interaction background process is basically not affected by the performance of computer hardware and software such as the operating system, CPU, and graphics card, ensuring normal communication with the center and external equipment. The data interaction foreground process is only responsible for data display and control functions. Compared with previous software, it reduces data analysis packaging, calculation, interpolation, interrupt response and other functions, greatly enhancing the stability of the data interaction software;

[0120] 2. High reusability: The software framework is applicable to various computer hardware and software, and has the ability to communicate with multiple centers at the same time. It also has common track, guidance data display, parameter setting, status monitoring, operation log display and other functions, and can be applied to various radars;

[0121] 3. Perfectly cope with complex and ever-changing display requirements: In the face of different display requirements, you only need to modify the data interaction foreground process, which will not affect the correctness of the external data interface.

[0122] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A data interaction software architecture with front-end and back-end separation, characterized in that: It includes a data interaction foreground process and a data interaction background process, which are respectively established in different software systems; the data interaction background process includes a network receiving thread, a data processing thread, a network sending thread, a data statistics thread, a network receiving data recording thread, a network sending data recording thread, a 20Hz processing thread, a 1Hz processing thread, and a data sending to the foreground thread; The network receiving thread, data processing thread and network sending thread are responsible for receiving, processing and sending data; Data statistics thread, responsible for generating statistical information of each site type data; The network receiving and sending data recording threads are responsible for sending data to the external data recording software. The 20Hz and 1Hz processing threads are used for timing processing to generate track and guide interpolation data. The data is sent to the foreground thread for communication with the data interaction foreground process. The data interaction foreground process is responsible for displaying data and realizing the control functions of track reporting and guidance issuance.

2. According to the data interaction software architecture with front-end and back-end separation in claim 1, it is characterized in that: The data interaction background process also includes a status monitoring thread and a boot file loading thread. The status monitoring thread is used to obtain the status data of the data statistics thread and send it to the sending data to the foreground thread; The boot file loading thread is used to read the file boot data, and generate the boot data for distribution after interpolation processing by the 20Hz processing thread.

3. The data interaction software architecture with front-end and back-end separation according to claim 1 is characterized in that: The data interaction foreground process specifically includes track data display and reporting control functions, which are used to receive the track data generated by the data interaction background process, display the track data in the form of tables and curves, and realize the reporting control of the target at the same time.

4. The data interaction software architecture with front-end and back-end separation according to claim 1 is characterized in that: The data interaction foreground process specifically includes guidance data display and distribution control functions, which is used to receive the guidance data generated by the data interaction background process, display the center guidance, equipment mutual guidance and theoretical guidance data in the form of tables and curves, and realize the distribution control of guidance at the same time.

5. The data interaction software architecture with front-end and back-end separation according to claim 1 is characterized in that: The data interaction foreground process specifically includes a communication parameter setting function, which is used to set the communication parameters of all communication nodes, including network receiving parameters, network sending parameters, whether messages are sent or received, whether data is interpolated, and the interpolation frequency. After being saved in the configuration file, it is used by the data interaction background process.

6. The data interaction software architecture with front-end and back-end separation according to claim 1 is characterized in that: The data interaction foreground process specifically includes a communication status monitoring function, which is used to receive data statistics information generated by the data interaction background process and display the sending and receiving status of various types of data at each site in real time, including the total number of packets, the number of lost packets, the number of error packets, the total traffic and speed.

7. The data interaction software architecture with front-end and back-end separation according to claim 1 is characterized in that: The data interaction foreground process specifically includes an operation log display function, which is used to receive and display in real time the operation log information generated by the data interaction background process, and at the same time display the operation log information of the data interaction foreground process.

8. The data interaction software architecture with front-end and back-end separation according to claim 1 is characterized in that: The communication between the data interaction front and data interaction background processes is realized by sending and receiving data through UDP. The data interface design between the two includes: 1) Track data The data interaction background process converts various types of track data into a unified track data interface, including the target's time, position, speed, status, and recognition results, and sends it to the data interaction foreground process; 2) Bootstrapping Data The data interaction background process converts the guidance data of the center and the mutual guidance data of each equipment into a unified guidance data interface, including the time, position, and speed of the target, and sends it to the data interaction foreground process; 3) Communication status The data interaction background process counts the network receiving data and network sending data respectively, generates unified communication status data, and sends it to the data interaction front-end process. The unified communication status data includes the total number of packets, number of lost packets, number of error packets, total traffic and speed; 4) Log information The data interaction background process sends the log information generated during the operation to the data interaction foreground process through a unified log information interface; 5) Time information The data interaction background process sends the local time, T0 time, and relative time to the data interaction front-end process through a unified time information interface; 6) Track reporting control instructions The track reporting control command interface includes automatic reporting / manual reporting, batch reporting / cancellation reporting. After receiving the command, the data interaction background process updates the local reporting rules. 7) Guide and issue control instructions The guidance and delivery control command interface includes guidance / cancellation. After receiving the command, the data interaction background process updates the local guidance and delivery rules. 8) T0 time setting After the data interaction foreground process sets the T0 time, it sends the T0 time setting command to the background. After receiving the command, the background updates the T0 time information. 9) Statistics clearing command After receiving the statistics clearing command, the data interaction background process clears the statistics.

9. The data interaction software architecture with front-end and back-end separation according to claim 1 is characterized in that: The data received by the network receiving thread, data processing thread and network sending thread comes from the data interaction foreground process, external sites and local radar.

Images