Satellite-borne radar software real-time health monitoring method

Abstract

The invention discloses a satellite-borne radar software real-time health monitoring method which comprises the following steps: step 1, designing a main process and an auxiliary process, the main process is used for realizing software functions and collecting monitoring data, the auxiliary process is used for organizing and sending monitoring information and judging program reset, and the main process and the auxiliary process exchange data through a shared memory; 2, a multi-angle monitoring data structure is set, and the host process acquires monitoring parameters and stores the monitoring parameters in a shared memory by adding monitoring points in the monitoring data structure; step 3, organizing and reporting the monitoring data, acquiring real-time monitoring parameters of the software running state by the auxiliary process by reading the shared memory, and organizing and reporting the monitoring data by adopting a method of combining two triggering modes of periodic reporting and current frame data processing ending triggering reporting; and step 4, fault positioning and reset judgment: the auxiliary process triggers a software reset function through a multi-angle parameter combined fault positioning method when the software crashes or falls into an endless loop.

Description

Technical Field

[0001] The present invention belongs to the technical field of radar data processing, and in particular relates to a real-time health monitoring method for satellite-borne radar software. Background Art

[0002] As software is increasingly used in various fields, the complexity of software operation increases, and its quality is difficult to be effectively controlled and guaranteed. Once a fault occurs, in the absence of effective monitoring methods, manual troubleshooting is inefficient, affecting the user experience and even causing economic losses.

[0003] Real-time software health monitoring collects internal information generated during software operation to understand the real-time operating status of the software and assist in quickly locating faults. The use of real-time health monitoring not only provides an important basis for evaluating whether the software is running well, but also lays a solid foundation for the subsequent online adjustment of software and improvement of software quality.

[0004] Spaceborne radar software is real-time embedded software with high real-time and precision requirements, and is affected by the radiation of the space environment. Real-time health monitoring can improve the safety and reliability of the software. Secondly, the resources for storing and transmitting data on the satellite computer are limited. How to collect and transmit monitoring information without affecting the original software function is the key to implementing the online monitoring technology of spaceborne radar software. Summary of the invention

[0005] The purpose of the present invention is to provide a real-time health monitoring technology for satellite-borne radar software, so as to realize the rapid location of radar software anomalies while the satellite is in orbit, and to reset and restart the software in time when serious anomalies occur, so as to improve the security and reliability of the software.

[0006] In order to achieve the above object, the technical solution adopted by the present invention is a real-time health monitoring method for satellite-borne radar software, comprising the following steps:

[0007] Step 1: Design a main and auxiliary dual process. The main process is used to implement software functions and collect monitoring data, and the auxiliary process is used to organize and send monitoring information and determine program reset. The main process and the auxiliary process exchange data through shared memory.

[0008] Step 2: Set up a multi-angle monitoring data structure. The main process adds monitoring points to the monitoring data structure, collects monitoring parameters and stores them in shared memory.

[0009] Step 3: Organization and reporting of monitoring data. The auxiliary process obtains the real-time monitoring parameters of the software running status by reading the shared memory, and organizes and reports the monitoring data by combining the two triggering modes of periodic reporting and reporting triggered by the end of processing the current frame data.

[0010] Step 4: Fault location and reset judgment: The auxiliary process uses a fault location method that combines multi-angle parameters to trigger the software reset function when the software crashes or falls into an infinite loop.

[0011] As a preferred embodiment of the present invention, in step 1, in the memory where the satellite-borne radar software runs, a separate area is provided inside the shared memory space as the storage address of the monitoring data. When the main process of the software crashes or falls into an infinite loop, the fault site information is still stored in the shared memory and can be transmitted through the auxiliary process.

[0012] As a preferred embodiment of the present invention, in step 2:

[0013] The main process monitors the software running position by setting monitoring points in the running position parameter structure, and can locate the specific position of the specific function where the problem occurs; the running position parameters include the function position pile number, file name, function name, line number and function input parameters.

[0014] The main process monitors the software entering the abnormal branch by setting a monitoring point in the abnormal branch parameter structure. The abnormal branch parameters include recording the number of times the program enters the abnormal branch, the number of the abnormal branch entered, and the abnormal branch entered when processing a certain frame of data.

[0015] The main process monitors the key nodes of software execution by setting monitoring points in the key information parameter structure. The key information parameter structure includes routine monitoring and exception monitoring. Routine monitoring is to monitor the parameters of key functional functions when the software is working normally, and to implement fixed records. Abnormal monitoring is to add monitoring information where the software is abnormal or needs protection or attention, and implement event-triggered recording.

[0016] The main process monitors the software's data reception and transmission by setting monitoring points in the data transmission and reception status parameter structure. The data transmission and reception status parameters include the number of correct data reception, the number of incorrect data reception, the type of received data error, the number of received data waiting timeouts, and the number of data transmission.

[0017] As a preferred embodiment of the present invention, in step 3:

[0018] The periodic reporting method is: at a fixed time period, the monitoring data of the software running status is transmitted to the ground through telemetry;

[0019] The method for triggering reporting after processing the current frame data is as follows: after processing the current frame data, the software processing information of the current frame is transmitted and stored in the data transmission module, and finally the monitoring data is transmitted to the ground in real time through the data transmission channel.

[0020] As a preferred embodiment of the present invention, in step 4, the fault location method combining multiple angle parameters includes:

[0021] Determine whether the software is running normally based on the software heartbeat count;

[0022] Monitor data based on data receiving and sending status parameters to determine whether the software receives data and the status of receiving data is normal;

[0023] Based on the running position parameter monitoring data, determine whether the software running position changes regularly, whether the software freezes or falls into / enters an infinite loop;

[0024] Based on the abnormal branch parameter monitoring data, determine whether the software has entered an abnormal branch and which abnormal branch it has entered;

[0025] Based on the key information parameter monitoring data, determine whether the function parameters of the software executing key functions are abnormal and whether abnormal monitoring records are triggered.

[0026] Compared with the prior art, the technical solution adopted by the present invention has the following beneficial effects:

[0027] The original satellite-borne radar software did not have a health monitoring function for the software's operating status, and was unable to grasp the specific circumstances of the software's operation. During the software's operation, it was impossible to determine whether an abnormal situation had occurred. After a fault occurred, the problem could not be located in time, and the fault site could not be reproduced, increasing the uncertainty of software use and the risk of software maintenance.

[0028] The present invention realizes the real-time monitoring function of the software without affecting the realization of the software function through the design of the main and auxiliary dual processes; sets a multi-angle monitoring data structure to cover multi-angle parameter information such as the running position, abnormal branches, and key information; and adopts a combination of periodic reporting and trigger reporting after the processing of the current frame data to ensure that the monitoring data is not lost while saving on-board data transmission and storage resources. Finally, through the fault location method combined with multi-angle parameters, it is judged whether the software is reset, which reduces the difficulty of fault location and improves the reliability and security of the software. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 It is a schematic diagram of the main and auxiliary dual process flow of the real-time health monitoring method of the spaceborne radar software in this embodiment.

[0030] Figure 2 It is a schematic diagram of the organization and reporting process of monitoring data of the real-time health monitoring method of space-borne radar software in this embodiment. DETAILED DESCRIPTION

[0031] The technical solution of the present invention is further explained below in conjunction with the accompanying drawings and specific embodiments.

[0032] This embodiment discloses a method for real-time health monitoring of satellite-borne radar software, comprising the following steps:

[0033] (10) Design the main and auxiliary dual processes.

[0034] like Figure 1 As shown in the figure, the main function of the software and the collection of monitoring data are implemented by the main process, and the organization and transmission of monitoring information and program reset judgment are implemented by the auxiliary process. Data is exchanged between processes through shared memory.

[0035] The design of main and auxiliary dual processes can prevent the failure of the monitoring function from affecting the execution of the main function of the software. In the memory where the onboard software runs, a separate area is allocated in the shared memory space as the storage address of the monitoring data. When the main process of the software crashes or falls into an infinite loop, the fault site information is still stored in the shared memory and can be transmitted through the auxiliary process, which facilitates the completion of fault problem analysis.

[0036] (20) Set up a multi-angle monitoring data structure.

[0037] According to the internal information generated during the software operation, a monitoring data structure including operation location, abnormal branch, key information, data receiving and sending status and other parameters is set up, which can comprehensively understand the software operation status from multiple angles and grasp the real-time dynamics of the software. Once an abnormality occurs, parameter information from multiple angles of the software failure site can be recorded to improve the efficiency of troubleshooting.

[0038] The multi-angle monitoring data structure of this embodiment includes the following aspects:

[0039] 1) Operation position parameter structure

[0040] The present invention constructs a running position parameter structure to monitor the software running position, and can locate the position of a specific function where a problem occurs. In addition to the function position stake number, the running position parameter structure also includes the file name, function name, line number, function input parameters or other important parameter information, etc., which records more on-site information and further facilitates problem troubleshooting.

[0041] 2) Abnormal branch parameter structure

[0042] The present invention constructs an abnormal branch parameter structure to monitor the software entering an abnormal branch. The abnormal branch parameter structure can record the number of times the program enters an abnormal branch, the number of the abnormal branch entered, the parameters related to the abnormal branch, and the abnormal branch entered when processing a certain frame of data.

[0043] 3) Key information parameter structure

[0044] The present invention constructs a key information parameter structure to monitor the key nodes of software execution. The key information parameter structure includes regular monitoring and abnormal monitoring. Regular monitoring is to monitor the parameters of certain key functions under normal software operation and implement fixed records; abnormal monitoring is to add monitoring information to places where the software may be abnormal, need protection or attention, and implement event triggering records.

[0045] 4) Data transmission and reception status parameter structure

[0046] The present invention constructs a data receiving and sending state parameter structure to monitor the software receiving and sending data. The data receiving and sending state parameter structure includes the number of correct data received, the number of wrong data received, the type of received data error, the number of received data waiting timeouts, the number of sent data, etc.

[0047] (30) Organization and reporting of monitoring data.

[0048] The auxiliary process obtains the real-time monitoring parameters of the software running status by reading the shared memory, and organizes and reports the monitoring data using two types of triggering methods.

[0049] 1) Periodic reporting method

[0050] The monitoring data of the software operation status is transmitted to the ground through telemetry at a fixed time cycle.

[0051] 2) Method for processing the end trigger report of the current frame data

[0052] After processing the current frame data, the software processing information of the current frame is transmitted and stored in the data transmission module, and finally the monitoring data is transmitted to the ground in real time through the data transmission channel.

[0053] The periodic telemetry time interval is long, which cannot reflect the real-time operation of the satellite-borne radar software, and may result in the loss of some processing frame states and parameters. The present invention designs a method combining periodic reporting and triggering reporting after the processing of the current frame data is completed, which can not only ensure that the processing state and parameter information of each frame of data is not lost, but also save the limited data storage and transmission resources on the satellite.

[0054] Specifically, the periodic reporting method mainly collects parameters such as the heartbeat message of the main program and the state of sending and receiving data, focusing on judging whether the software is running normally. The method of triggering reporting after processing the end of the current frame data focuses on the specific situation of processing each frame of data, and can judge whether there is an abnormal state during the software operation, especially the abnormal situation that does not affect the software operation and is easy to be ignored.

[0055] (40) Fault location and reset judgment.

[0056] The present invention realizes the functions of simple fault location and reset judgment in the auxiliary process. By monitoring the heartbeat message to judge whether the software is running normally, combining the running position parameter structure, understanding the current state of the software running, as well as the abnormal position parameters and key information parameters, the specific location and abnormal type of the fault can be located after the software fails, thereby improving the efficiency of software fault troubleshooting. The specific steps are as follows:

[0057] Step 1: Determine whether the software is running normally based on the software heartbeat count.

[0058] Step 2: Monitor data based on data receiving and sending status parameters to determine whether the software receives data and whether the data receiving status is normal.

[0059] Step three: Based on the running position parameter monitoring data, determine whether the software running position changes regularly, whether the software freezes or falls into an infinite loop.

[0060] Step 4: Based on the abnormal branch parameter monitoring data, determine whether the software enters an abnormal branch and which abnormal branches it enters.

[0061] Step 5: Based on the key information parameter monitoring data, determine whether the function parameters of the software executing key functions are abnormal and whether abnormal monitoring records are triggered.

[0062] Through the above analysis, when the auxiliary process determines that the software has crashed or fallen into an infinite loop based on the monitoring information, the software reset function is triggered.

[0063] The present invention realizes the real-time monitoring function of the software without affecting the realization of the software function through the design of the main and auxiliary dual processes; sets a multi-angle monitoring data structure to cover multi-angle parameter information such as the running position, abnormal branches, and key information; and adopts a combination of periodic reporting and trigger reporting after the processing of the current frame data to ensure that the monitoring data is not lost while saving on-board data transmission and storage resources. Finally, through the fault location method combined with multi-angle parameters, it is judged whether the software is reset, which reduces the difficulty of fault location and improves the reliability and security of the software.

[0064] Although the invention has been disclosed as above in terms of preferred embodiments, the embodiments and drawings are not intended to limit the invention. Anyone familiar with the art can make various changes or modifications without departing from the spirit and scope of the invention, but they are also within the scope of protection of the invention. Therefore, the scope of protection of the invention shall be based on the scope of protection of the claims of this application.

Claims

1. A method for real-time health monitoring of satellite-borne radar software, characterized in that: The steps include: Step 1: Design a main and auxiliary dual process. The main process is used to implement software functions and collect monitoring data, and the auxiliary process is used to organize and send monitoring information and determine program reset. The main process and the auxiliary process exchange data through shared memory. Step 2: Set up a multi-angle monitoring data structure. The main process adds monitoring points to the monitoring data structure, collects monitoring parameters and stores them in shared memory. Step 3: Organization and reporting of monitoring data. The auxiliary process obtains the real-time monitoring parameters of the software running status by reading the shared memory, and organizes and reports the monitoring data by combining the two triggering modes of periodic reporting and reporting triggered by the end of processing the current frame data. Step 4: Fault location and reset judgment: The auxiliary process uses a fault location method that combines multi-angle parameters to trigger the software reset function when the software crashes or falls into an infinite loop.

2. A method for real-time health monitoring of satellite-borne radar software according to claim 1, characterized in that: In step 1, in the memory where the satellite-borne radar software runs, a separate area is provided inside the shared memory space as the storage address of the monitoring data. When the main process of the software crashes or falls into an infinite loop, the fault site information is still stored in the shared memory and can be transmitted through the auxiliary process.

3. A method for real-time health monitoring of satellite-borne radar software according to claim 1, characterized in that: In step 2, the multi-angle monitoring data structure includes an operation position parameter structure, an abnormal branch parameter structure, a key information parameter structure and a data transmission and reception state parameter structure.

4. A method for real-time health monitoring of satellite-borne radar software according to claim 3, characterized in that: The main process monitors the software running position by setting monitoring points in the running position parameter structure, and can locate the specific position of the specific function where the problem occurs; the running position parameters include the function position pile number, file name, function name, line number and function input parameters.

5. A method for real-time health monitoring of satellite-borne radar software according to claim 3, characterized in that: The main process monitors the software entering the abnormal branch by setting monitoring points in the abnormal branch parameter structure. The abnormal branch parameters include recording the number of times the program enters the abnormal branch, the number of the abnormal branch entered, and the abnormal branch entered when processing a certain frame of data.

6. A method for real-time health monitoring of satellite-borne radar software according to claim 3, characterized in that: The main process monitors the key nodes of software execution by setting monitoring points in the key information parameter structure. The key information parameter structure includes regular monitoring and abnormal monitoring; Routine monitoring is to monitor the parameters of key functions when the software is working normally, and to implement fixed records; abnormal monitoring is to add monitoring information where the software has abnormalities, requires protection or attention, and implement event-triggered records.

7. A method for real-time health monitoring of satellite-borne radar software according to claim 3, characterized in that: The main process monitors the software's data reception and transmission by setting monitoring points in the data transmission and reception status parameter structure. The data transmission and reception status parameters include the number of correct data reception, the number of incorrect data reception, the type of received data error, the number of received data waiting timeouts, and the number of data transmission.

8. A method for real-time health monitoring of satellite-borne radar software according to claim 1, characterized in that: In step 3: The periodic reporting method is: at a fixed time period, the monitoring data of the software running status is transmitted to the ground through telemetry; The method for triggering reporting after processing the current frame data is as follows: after processing the current frame data, the software processing information of the current frame is transmitted and stored in the data transmission module, and finally the monitoring data is transmitted to the ground in real time through the data transmission channel.

9. A method for real-time health monitoring of satellite-borne radar software according to claim 1, characterized in that: In step 4, the fault location method combining multi-angle parameters includes: Determine whether the software is running normally based on the software heartbeat count; Monitor data based on data receiving and sending status parameters to determine whether the software receives data and the status of receiving data is normal; Based on the running position parameter monitoring data, determine whether the software running position changes regularly, whether the software freezes or falls into / enters an infinite loop; Based on the abnormal branch parameter monitoring data, determine whether the software has entered an abnormal branch and which abnormal branch it has entered; Based on the key information parameter monitoring data, determine whether the function parameters of the software executing key functions are abnormal and whether abnormal monitoring records are triggered.

Images