Embedded log analysis method and device

Abstract

The embodiment of the invention provides an embedded log analysis method and device, and the method comprises the steps: obtaining a telemetering data source code, and carrying out the analysis based on the telemetering data source code, and determining telemetering analysis data; determining fault identification data based on the telemetry analysis data; wherein the fault identification data comprises fault data and / or tracking data, the fault data is used for identifying a fault point, and the tracking data is used for scene reproduction; and performing fault analysis based on the fault identification data and the logic association library to obtain a fault reason. Through the fault data and the tracking data in the scheme, the memory and bandwidth consumption of logs can be reduced in communication between the rocket and the ground, and automatic analysis based on the fault data and the tracking data is realized, so that the accuracy and speed of fault positioning are improved.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of aerospace technology, and particularly to an embedded log analysis method. Background Art

[0002] In the field of aerospace, as a core component, the flight control system effectively records and analyzes its previous test log data, which is crucial for key technology verification, accumulation, and iteration. Existing log systems usually record log data in non-volatile memory or send it to ground launch, measurement, control equipment through a wireless link. These log systems have the following deficiencies: the log data structure requires a large amount of hardware memory resources or wireless link bandwidth resources; outputting logs to the target medium consumes some time resources and may affect the system operation performance; usually, a large amount of log data needs to be analyzed offline manually; it is difficult to quickly select and comprehensively analyze multiple data sources; it is difficult to quickly locate the cause of system faults and give solutions; it is impossible to efficiently reproduce the specific scenarios and logical branches of software execution.

[0003] The software supporting the flight control system usually runs on an embedded hardware platform with limited memory resources. After some flight tests, the hardware platform may not be recyclable. In actual tasks, the equipped wireless link usually has limited bandwidth. These all pose great challenges to the efficient expansion and further application optimization of traditional log systems.

[0004] Therefore, there is an urgent need for a better solution. Summary of the Invention

[0005] In view of this, the embodiments of this specification provide an embedded log analysis method. One or more embodiments of this specification simultaneously relate to an embedded log analysis device, a computing device, a computer-readable storage medium, and a computer program to solve the technical defects existing in the prior art.

[0006] According to the first aspect of the embodiments of this specification, an embedded log analysis method is provided, including: Obtain telemetry data source code, and determine telemetry analysis data based on the telemetry data source code through parsing; Determine fault identification data based on the telemetry analysis data; where the fault identification data includes fault data and / or trace data, the fault data is used to identify the fault point, and the trace data is used for scenario reproduction; Conduct fault analysis based on the fault identification data and the logical association library to obtain the cause of the fault.

[0007] In a possible implementation, determining telemetry analysis data based on the telemetry data source code through parsing includes: Determine bit source code data based on the telemetry data source code; Convert the bit source code data into telemetry analysis data according to the preset conversion rules.

[0008] In a possible implementation, determining the fault identification data based on the telemetry analysis data includes: Extract the target fault code from the telemetry analysis data; wherein, the target fault code is the fault code of the current telemetry cycle; Compare the target fault code with the fault logic association library to determine the fault comparison result; wherein, the fault logic association library includes at least two fault codes and the logical association relationship between at least two fault codes and the telemetry physical quantity; In the case that the fault comparison result is that the target fault code exists in the fault logic association library, use the target fault code as the fault data.

[0009] In a possible implementation, determining the fault identification data based on the telemetry analysis data includes: Extract the target tracking code from the telemetry analysis data; wherein, the target tracking code is the tracking code of the current telemetry cycle; Compare the target tracking code with the tracking logic association library to determine the tracking comparison result; wherein, the tracking logic association library includes at least two tracking codes and the logical association relationship between at least two tracking codes and the telemetry physical quantity; In the case that the tracking comparison result is that the target tracking code exists in the tracking logic association library, use the target tracking code as the tracking data.

[0010] In a possible implementation, performing fault analysis based on the fault identification data and the logic association library includes: In the case that the fault identification data includes the fault data, extract the fault details from the telemetry analysis data; Obtain the corresponding first telemetry physical quantity from the fault logic association library based on the fault data and the fault details; Perform fault analysis based on the first telemetry physical quantity to determine the cause of the fault.

[0011] In a possible implementation, performing fault analysis based on the fault identification data and the logic association library includes: In the case that the fault identification data includes the tracking data, or, in the case that the fault identification data includes the tracking data and the fault cause cannot be determined based on the first telemetry physical quantity for fault analysis, extract the tracking details from the telemetry analysis data; obtain the corresponding second telemetry physical quantity and the expected tracking details based on the tracking code and the tracking logic association library; Generate the historical tracking details based on the second telemetry physical quantity; Determine the cause of the fault based on the historical tracking details and the expected tracking details.

[0012] In a possible implementation, it further includes: After determining the cause of the fault, obtain a solution measure from the logical association library based on the cause of the fault, and display the solution measure; In the case where the cause of the fault is not determined, display the trace data and the fault data for fault analysis based on the trace data and the fault data.

[0013] According to the second aspect of the embodiments of the present specification, an embedded log analysis device is provided, including: A data acquisition module configured to acquire the source code of telemetry data and determine telemetry analysis data based on the source code of telemetry data; A data analysis module configured to determine fault identification data based on the telemetry analysis data; wherein the fault identification data includes fault data and / or trace data, the fault data is used to identify the fault point, and the trace data is used for scenario reproduction; A fault judgment module configured to perform fault analysis based on the fault identification data and the logical association library to obtain the cause of the fault.

[0014] According to the third aspect of the embodiments of the present specification, a computing device is provided, including: A memory and a processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above-mentioned embedded log analysis method are implemented.

[0015] According to the fourth aspect of the embodiments of the present specification, a computer-readable storage medium is provided, which stores computer-executable instructions. When the instructions are executed by the processor, the steps of the above-mentioned embedded log analysis method are implemented.

[0016] According to the fifth aspect of the embodiments of the present specification, a computer program is provided. When the computer program is executed on a computer, the computer is made to execute the steps of the above-mentioned embedded log analysis method.

[0017] The embodiments of the present specification provide an embedded log analysis method and device. The embedded log analysis method includes: acquiring the source code of telemetry data, and determining telemetry analysis data based on the source code of telemetry data; determining fault identification data based on the telemetry analysis data; wherein the fault identification data includes fault data and / or trace data, the fault data is used to identify the fault point, and the trace data is used for scenario reproduction; performing fault analysis based on the fault identification data and the logical association library to obtain the cause of the fault. Through the fault data and trace data in the above solution, it is possible to reduce the memory and bandwidth consumption of the log in the rocket-ground communication, and implement automated analysis based on the fault data and trace data, thereby improving the accuracy and speed of fault location. Description of the Drawings

[0018] Figure 1 is a flowchart of an embedded log analysis method provided by an embodiment of this specification; Figure 2 is a schematic diagram of a fault code of an embedded log analysis method provided by an embodiment of this specification; Figure 3 is a schematic diagram of a trace code of an embedded log analysis method provided by an embodiment of this specification; Figure 4 is a schematic diagram of a trace marker code of an embedded log analysis method provided by an embodiment of this specification; Figure 5 is a schematic diagram of an interface code of an embedded log analysis method provided by an embodiment of this specification; Figure 6 is a schematic diagram of an architecture of an embedded log analysis method provided by an embodiment of this specification; Figure 7 is a schematic diagram of the structure of an embedded log analysis device provided by an embodiment of this specification; Figure 8 is a block diagram of the structure of a computing device provided by an embodiment of this specification. Detailed implementation manners

[0019] In the following description, numerous specific details are set forth in order to provide a thorough understanding of this specification. However, this specification can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the connotation of this specification. Therefore, this specification is not limited by the specific implementations disclosed below.

[0020] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and encompasses any or all possible combinations of one or more of the associated listed items.

[0021] It should be understood that although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to a determination".

[0022] In this specification, an embedded log analysis method is provided. This specification also relates to an embedded log analysis device, a computing device, and a computer-readable storage medium, which will be described in detail one by one in the following embodiments.

[0023] See Figure 1 , Figure 1 FIG. shows a flowchart of an embedded log analysis method provided according to an embodiment of this specification, which specifically includes the following steps.

[0024] Step 101: Obtain the telemetry data source code, and parse the telemetry data source code to determine the telemetry analysis data; Among them, the telemetry data source code is the data source code transmitted by the rocket to the ground periodically, such as a binary bit stream. The telemetry analysis data is the data obtained by parsing the telemetry data source code according to a set rule, such as converting binary data to decimal data.

[0025] In a possible implementation manner, parsing the telemetry data source code to determine the telemetry analysis data includes: determining the bit source code data based on the telemetry data source code; converting the bit source code data into the telemetry analysis data according to a preset conversion rule.

[0026] Among them, the bit source code data may be binary bit stream data.

[0027] In practical applications, the rocket transmits the telemetry data source code to the ground periodically, and the transmission period is usually 10 ms.

[0028] For example, the flight control software of the rocket transmits the ground telemetry data source code to the ground launch control system at a period of 100 ms. The ground telemetry data source code is: 00000011, then the telemetry data source code is converted into a decimal number: 3, that is, the telemetry analysis data is obtained.

[0029] The embodiment of this specification facilitates subsequent identification and parsing and is convenient for staff to analyze by converting the telemetry data source code into the telemetry analysis data.

[0030] Step 102: Determine fault identification data based on the telemetry parsing data; among them, the fault identification data includes fault data and / or trace data, the fault data is used to identify the fault point, and the trace data is used for scenario reproduction.

[0031] Among them, the fault identification data is the data used for fault identification. The fault data can be the data inserted into the telemetry data source code by the rocket in a telemetry cycle. Correspondingly, the trace data can be the data inserted into the telemetry data source code by the rocket in a telemetry cycle. The fault data and the trace data can be in two parts of the telemetry data source code.

[0032] In practical applications, an on-board log recording module can be set up. The log recording module efficiently records the error code (EC: Error Code) and the trace code (TC: Track Code) during system operation through bit patterns, facilitating quick problem location during data analysis; and provides detailed error statistics and status tracking capabilities through the error details (ErrorInfo_t) and the trace details (TrackInfo_t).

[0033] Furthermore, the on-board log recording module specifically needs to include the following functions: Modular classification: Classify the error code and the trace code by functional module for easy maintenance and expansion. Bit-field compressed storage: Use bit-field and union to compactly store the status, saving memory space. Status statistics: Record the trigger times of each code through a counting array to assist in problem location and performance analysis. In the design of the fault / trace code, use the EC_SET macro to define various error codes (EC: Error Code), such as Figure 2 the specific fault codes included in modules such as the underlying driver, application protocol, and test launch control process given in Figure 3 Use the TC_SET macro to define various trace codes (TC: Track Code), such as

[0034] a) Bit operation: Each fault or trace code corresponds to a bit, setting it to 1 indicates triggering, supporting fast status marking; b) Buffer storage: Facilitates the storage or transmission of bitfield data in the form of a whole block of memory.

[0035] Record specific fault codes (TransInfo_t.code), fault code description information (TransInfo_t.desc), fault bitfield (bits), and fault count array (bitCnt) through the fault details (ErrorInfo_t). Record specific trace codes (TransInfo_t.code), trace code description information (TransInfo_t.desc), trace bitfield (bits), and trace count array (bitCnt) through the trace details (TrackInfo_t).

[0036] See Figure 4 , taking the trace details as an example (the same applies to the fault details), for analysis in terms of storage resource (hardware memory or communication bandwidth) occupancy: using 1 bit to represent 1 logical branch marker point, the maximum number of logical branches that can be marked by the trace details in a single control cycle is: N * 8 / P, where: N represents the number of bytes occupied by the trace details in a single output cycle, and P represents the number of control cycles included in a single output cycle.

[0037] For example, in a rocket flight control system, the control cycle is usually 10 ms. Assuming that the flight control software sends 20 bytes of trace details to the ground test launch control system at a 100 ms cycle, the maximum number of logical branches that can be marked by the trace details in a single control cycle is 16. When the communication bandwidth permits, if the flight control software outputs the trace details at the control cycle, the maximum number of logical branches that can be marked increases to 160, which can cover every software operation branch. Considering the communication bandwidth and the control logic complexity of the flight control software comprehensively: when the communication bandwidth is tight, the trace details can preferentially record the execution of the logical branches of key software modules; when the communication bandwidth permits, the trace details can try to record and cover all software logical branches.

[0038] Furthermore, in terms of the interface, see Figure 5 , taking the trace log record as an example (the same applies to the fault log record). In actual use, first call the trace log initialization interface (TRACK_BEGIN) to set the starting state; then call the trace log record interface (TRACK_RECORD) to mark the target logical branch. When marking, directly assign values to the corresponding bits of the trace bitfield using the target trace code, and the consumed system time resources can be ignored.

[0039] It should be noted that the data sizes of the fault code, trace code, trace details, and fault details need to be set according to the actual situation. For example, within a period, if the available communication resources are high, the data of the fault code, trace code, trace details, and fault details can be more; if the available communication resources are low, the data of the fault code, trace code, trace details, and fault details need to be reduced so as not to affect normal tasks.

[0040] In one possible implementation, determining fault identification data based on telemetry analysis data includes: extracting a target fault code from the telemetry analysis data; where the target fault code is the fault code of the current telemetry period; comparing the target fault code with a fault logic association library to determine a fault comparison result; where the fault logic association library includes at least two fault codes and the logical association relationships between at least two fault codes and telemetry physical quantities; when the fault comparison result indicates that the target fault code exists in the fault logic association library, using the target fault code as the fault data.

[0041] Among them, the target fault code is data used to identify the fault of the current period, and the fault logic association library is a database of fault codes and telemetry physical quantities, as well as the logical relationships between telemetry physical quantities and fault causes, set on the ground based on manual experience and knowledge.

[0042] In practical applications, when there is a fault code in the telemetry analysis data, the data corresponding to the fault code can be extracted, and thus the fault identification data can be determined.

[0043] For example, in a rocket, there are four logical branches A, B, C, and D, and the corresponding decimal fault codes are 1, 2, 3, and 4 respectively. The fault code in the telemetry data source code received in a certain period is: 00000011, which can be parsed as the decimal number 3. Then, the fault code 3 can be found in the fault logic association library, and the fault data is 3.

[0044] The embodiments of this specification determine the fault of the current period by obtaining the fault code in the telemetry data source code and matching the obtained fault code with the faults in the fault logic association library, thereby improving the fault location speed.

[0045] In one possible implementation, determining trace identification data based on telemetry analysis data includes: extracting a target trace code from the telemetry analysis data; where the target trace code is the trace code of the current telemetry period; comparing the target trace code with a trace logic association library to determine a trace comparison result; where the trace logic association library includes at least two trace codes and the logical association relationships between at least two trace codes and telemetry physical quantities; when the trace comparison result indicates that the target trace code exists in the trace logic association library, using the target trace code as the trace data.

[0046] Among them, the target tracking code is data used to identify the execution action in the current cycle, and the tracking logic association library is a database that sets the tracking code and telemetry physical quantity, as well as the telemetry physical quantity and the cause of the fault.

[0047] In practical applications, when there is a tracking code in the telemetry parsing data, the data corresponding to the tracking code can be extracted, and thus it can be determined as fault identification data.

[0048] For example, in a rocket, there are four logical branches A, B, C, and D, and the corresponding decimal tracking codes are 1, 2, 3, and 4 respectively. The tracking code in the source code of the telemetry data received in a certain cycle is: 00000011, which can be parsed into the decimal number 3. Then, the fault code 3 can be found in the tracking logic association library, and the tracking data is 3.

[0049] The embodiment of this specification determines the action being executed in the current cycle by obtaining the tracking code in the source code of the telemetry data and matching the obtained tracking code with the tracking logic association library, thereby improving the speed of scenario reproduction.

[0050] Step 103: Perform fault analysis based on the fault identification data and the logic association library to obtain the cause of the fault.

[0051] In practical applications, referring to Figure 6 , log analysis software can be deployed on the ground. The log analysis software takes the telemetry parsing data and the logic association library as inputs, automatically processes the log data through the fault automatic analysis module and the scenario reproduction analysis module (in an online or offline manner), and displays the analysis results on the human-computer interaction interface or stores them in the analysis document.

[0052] It should be noted that the corresponding logic association library can be customized and written according to the telemetry data protocol agreement and combined with the data analysis requirements of this specialty. The embodiment of this specification does not limit the specific implementation of the logic association library.

[0053] In a possible implementation manner, performing fault analysis based on the fault identification data and the logic association library includes: when the fault identification data includes fault data, extracting the fault details from the telemetry parsing data; obtaining the corresponding first telemetry physical quantity from the fault logic association library based on the fault data and the fault details; and performing fault analysis based on the first telemetry physical quantity to determine the cause of the fault.

[0054] Among them, the fault details are all the fault codes recorded in the current telemetry cycle. The first telemetry physical quantity is the telemetry physical quantity corresponding to the fault details.

[0055] In practical applications, the logical association relationships between each fault code and other telemetry physical quantities that may cause the fault are set in the fault logic association library. When a bit corresponding to a certain fault code in the fault details is set, the log analysis software automatically obtains and processes the associated physical quantities according to the fault association relationships set in the association library, and gives the specific cause of the fault and possible solutions. Among them, the cause and solutions can be selectively added to the association library and given by different professional designers based on prior conclusions and experience.

[0056] Continuing with the above example, the rocket includes four logical branches A, B, C, and D, and the corresponding decimal fault codes are 1, 2, 3, and 4 respectively. The fault code in the telemetry data source code received in a certain period is: 00000011, which can be parsed as the decimal number 3. Then the fault code 3 can be found in the fault logic association library, the fault data is 3, corresponding to the C logical branch, and the physical quantity corresponding to C is the physical quantity related to power supply conversion. Then the cause of the fault is determined as a power supply conversion fault.

[0057] Furthermore, the electrical system designer associates the power supply conversion fault with three telemetry physical quantities: flight control time, execution flag of the launch and measurement control process, and bus voltage of the on-board thermal battery. The fault association logic is as follows: 1) The completion flag of the thermal battery activation process is invalid after the start flag of the power supply conversion process is valid; 2) The time elapsed from the start flag of the power supply conversion process being valid to the bus voltage of the thermal battery being valid is greater than the given time index. Then the possible solutions are: 1) Ensure that the thermal battery is activated before performing the power supply conversion; 2) Check whether the power supply conversion circuit is faulty; 3) Change the threshold for judging the validity of the bus voltage of the thermal battery; 4) Change the time index required for power transfer completion.

[0058] It should be noted that the analysis process of the fault details is the same as that of the fault code. For example, if the fault details are 00000101, the first bit from the right is set to 1, indicating that A has a fault, and the third bit is set to 1, indicating that C has a fault.

[0059] The embodiment of this specification realizes rapid fault location through fault codes and fault details, realizes fault analysis and gives fault solutions, and improves the speed of fault resolution.

[0060] In a possible implementation manner, fault analysis is performed based on fault identification data and a logical association library, including: when the fault identification data includes trace data, or, when the fault identification data includes trace data and fault analysis is performed based on the first telemetry physical quantity but the cause of the fault cannot be determined, extracting trace details from the telemetry parsing data; obtaining the corresponding second telemetry physical quantity and expected trace details based on the trace code and the trace logic association library; generating historical trace details based on the second telemetry physical quantity; and determining the cause of the fault based on the historical trace details and the expected trace details.

[0061] Among them, the tracking details are all the tracking codes recorded within the current telemetry cycle, that is, all the executed actions. The second telemetry physical quantity is the telemetry physical quantity corresponding to the tracking details. The expected tracking details are the logical branches that should have been executed under normal circumstances.

[0062] In practical applications, the tracking details record in detail the execution of the flight control software's logical branches in each control cycle. During the actual data analysis process, designers can select a local one or several control cycles for scenario reproduction. Set the logical association relationship (recorded as an association rule, and designers can set multiple similar association rules according to actual analysis needs to form an association rule library for this specialty) between the values of a certain or certain telemetry physical quantities (data values or status values, which can be secondary calculation values) and the tracking details in the tracking logic association library. When the log analysis software traverses the telemetry data, it judges in real time whether the values of these selected physical quantities meet the trigger conditions given in the association rules. If they meet, it compares whether the expected tracking details (expected software logical branch execution) given in the association rules are consistent with the actual tracking details (actual software logical branch execution) recorded in the current control cycle's telemetry data. If they are not consistent, further comprehensive analysis of the specific reasons is required.

[0063] It should be noted that this solution can directly reproduce the scenario through the tracking code, or reproduce the scenario when the cause of the fault cannot be determined through the fault code.

[0064] Continuing with the above example, there are four logical branches A, B, C, and D in the rocket, and the corresponding decimal tracking codes are 1, 2, 3, and 4 respectively. The tracking code in the source telemetry data received in a certain cycle is: 00000101, which can be parsed as the decimal number 3. Then the fault code 3 can be found in the tracking logic association library, and the tracking data is 3, so it can be determined that the currently executed logical branch is C. In the tracking logic association library, the guidance and control designers associate the flight timing status quantity (1 bit corresponds to a flight timing point, such as bit0 corresponds to the start control moment, bit1 corresponds to the engine burnout moment, etc.) with the tracking details, determine the flight timing status quantity corresponding to C from the tracking logic association library, and form multiple association rules according to the flight control model mathematical simulation results, indicating that after the software runs to a certain flight stage, it should be able to cover the given logical branch, that is, the expected tracking details.

[0065] Furthermore, the tracking details are 00000111. If the first position from the right is 1, it means that A has been executed. If the second position is 1, it means that B has been executed. If the third position is 1, it means that C has been executed. Finally, it is judged whether it is consistent with the expected tracking details.

[0066] In the embodiments of this specification, the executed logical branches of the rocket are determined by setting trace codes and trace details, so that the execution situation of the rocket can be reproduced on the ground, and thus fault analysis can be carried out, improving the accuracy of fault analysis and increasing the data basis for fault analysis.

[0067] In a possible implementation manner, it further includes: after determining the cause of the fault, obtaining a solution measure from the logical association library based on the cause of the fault and displaying the solution measure; in the case where the cause of the fault is not determined, displaying the trace data and the fault data so that the staff can perform fault analysis based on the trace data and the fault data.

[0068] In practical applications, the logical association relationship between each fault code and the trace details that may cause the fault is set in the fault logic association library. When a certain fault code in the fault details has its corresponding bit set, the log analysis software automatically obtains the associated physical quantities to be processed according to the set fault association relationship in the association library, and gives the specific cause of the fault and possible solution measures.

[0069] It should be noted that when the telemetry communication bandwidth permits, the fault codes can be refined as much as possible, that is, the flight control software needs to add the fault detail setting operation to all corresponding fault logical branches as much as possible, and the log analysis software can give the specific cause of the fault and possible solution measures without configuring the association library.

[0070] Continuing with the above example: the fault association logic is: 1) the completion flag of the hot battery activation process is invalid after the power supply conversion process start flag is valid; 2) the time elapsed from the power supply conversion process start flag being valid to the hot battery bus voltage being valid is greater than the given time index. In the valid branches of the two fault association logics, add the corresponding fault detail setting operations respectively to achieve the same analysis effect.

[0071] The embodiments of this specification provide an embedded log analysis method and device. The embedded log analysis method includes: obtaining the source code of telemetry data, parsing the source code of telemetry data to determine the telemetry analysis data; determining the fault identification data based on the telemetry analysis data; where the fault identification data includes fault data and / or trace data, the fault data is used to identify the fault point, and the trace data is used for scenario reproduction; performing fault analysis based on the fault identification data and the logical association library to obtain the cause of the fault.

[0072] Through the fault data and trace data in the above solution, it is possible to reduce the memory and bandwidth consumption of the log in the rocket - ground communication, and achieve automated analysis based on the fault data and trace data, thereby improving the accuracy and speed of fault location.

[0073] In an overall embodiment, the flight control software of the rocket sends the source code of ground telemetry data to the ground test, launch, and control system at a cycle of 100 ms. There are four logical branches, A, B, C, and D, in the rocket, and the corresponding decimal fault codes are 1, 2, 3, and 4 respectively. The fault code in the source code of the telemetry data received in a certain cycle is: 00000011, which can be parsed as the decimal number 3. Then, the fault code 3 can be found in the fault logic association library, and the fault data is 3. The fault details are 00000101. The first position 1 from right to left indicates that A has a fault, and the third position 1 indicates that C has a fault. The trace code in the source code of the telemetry data is: 00000011, which can be parsed as the decimal number 3. Then, the fault code 3 can be found in the trace logic association library, and the trace data is 3. The trace details are 00000111. The first position 1 from right to left indicates that A has been executed, the second position 1 indicates that B has been executed, and the third position 1 indicates that C has been executed.

[0074] After obtaining the fault data and trace data, fault analysis can be carried out. The physical quantity corresponding to C is the physical quantity related to power supply conversion, so it is determined that the fault cause is power supply conversion failure. It can also be determined from the fault details that A has a fault. Then, obtain the fault causes and solutions corresponding to A and C from the fault logic association library.

[0075] Furthermore, the trace data is 3, and it can be determined that the currently executed logical branch is C. The trace details are 00000111. The first position 1 from right to left indicates that A has been executed, the second position 1 indicates that B has been executed, and the third position 1 indicates that C has been executed. Determine whether it is consistent with the expected trace details. If not, obtain the corresponding fault causes and solutions from the fault logic association library.

[0076] In the above steps, if the corresponding fault code, fault cause, or solution cannot be found in the fault logic association library, the scenario can be reproduced directly through the trace code and trace details, so that the staff can carry out fault analysis. The scenario can also be reproduced directly after obtaining the trace code and trace details.

[0077] Corresponding to the above method embodiment, this specification also provides an embodiment of an embedded log analysis device. Figure 7 It shows a schematic structural diagram of an embedded log analysis device provided by an embodiment of this specification. As Figure 7 shown, the device includes: A data acquisition module 701, configured to acquire the source code of telemetry data and determine the telemetry analysis data based on the source code of telemetry data through parsing; The data parsing module 702 is configured to determine fault identification data based on telemetry parsed data; wherein, the fault identification data includes fault data and / or trace data, the fault data is used to identify the fault point, and the trace data is used for scenario reproduction; The fault judgment module 703 is configured to perform fault analysis based on the fault identification data and the logical association library to obtain the cause of the fault.

[0078] In a possible implementation, parsing the telemetry data source code to determine the telemetry parsed data includes: Determining bit source code data based on the telemetry data source code; Converting the bit source code data into telemetry parsed data according to a preset conversion rule.

[0079] In a possible implementation, determining the fault identification data based on the telemetry parsed data includes: Extracting a target fault code from the telemetry parsed data; wherein, the target fault code is the fault code of the current telemetry cycle; Comparing the target fault code with the fault logic association library to determine the fault comparison result; wherein, the fault logic association library includes at least two fault codes and the logical association relationship between at least two fault codes and telemetry physical quantities; In the case that the target fault code exists in the fault logic association library in the fault comparison result, taking the target fault code as the fault data.

[0080] In a possible implementation, determining the fault identification data based on the telemetry parsed data includes: Extracting a target trace code from the telemetry parsed data; wherein, the target trace code is the trace code of the current telemetry cycle; Comparing the target trace code with the trace logic association library to determine the trace comparison result; wherein, the trace logic association library includes at least two trace codes and the logical association relationship between at least two trace codes and telemetry physical quantities; In the case that the target trace code exists in the trace logic association library in the trace comparison result, taking the target trace code as the trace data.

[0081] In a possible implementation, performing fault analysis based on the fault identification data and the logical association library includes: In the case that the fault identification data includes fault data, extracting fault details from the telemetry parsed data; Obtaining the corresponding first telemetry physical quantity from the fault logic association library based on the fault data and the fault details; Performing fault analysis based on the first telemetry physical quantity to determine the cause of the fault.

[0082] In a possible implementation, fault analysis is performed based on fault identification data and a logical association library, including: When the fault identification data includes trace data, or when the fault identification data includes trace data and fault analysis is performed based on the first telemetry physical quantity but the cause of the fault cannot be determined, extract trace details from the telemetry parsing data; obtain the corresponding second telemetry physical quantity and expected trace details based on the trace code and the trace logical association library; Generate historical trace details based on the second telemetry physical quantity; Determine the cause of the fault based on the historical trace details and the expected trace details.

[0083] In a possible implementation, it further includes: After determining the cause of the fault, obtain the solution measures from the logical association library based on the cause of the fault and display the solution measures; When the cause of the fault is not determined, display the trace data and the fault data so that the staff can perform fault analysis based on the trace data and the fault data.

[0084] The embodiments of this specification provide an embedded log analysis method and apparatus. The embedded log analysis apparatus includes: obtaining the source code of telemetry data, parsing based on the source code of telemetry data to determine telemetry parsing data; determining fault identification data based on the telemetry parsing data; where the fault identification data includes fault data and / or trace data, the fault data is used to identify the fault point, and the trace data is used for scenario reproduction; performing fault analysis based on the fault identification data and the logical association library to obtain the cause of the fault. Through the fault data and trace data in the above solution, it is possible to reduce the memory and bandwidth consumption of the log in the rocket - ground communication, and achieve automated analysis based on the fault data and trace data, thereby improving the accuracy and speed of fault location.

[0085] The above is a schematic solution of an embedded log analysis apparatus according to an embodiment of this specification. It should be noted that the technical solution of this embedded log analysis apparatus and the technical solution of the above - mentioned embedded log analysis method belong to the same concept. For the details not described in detail in the technical solution of this embedded log analysis apparatus, reference can be made to the description of the technical solution of the above - mentioned embedded log analysis method.

[0086] Figure 8 FIG. shows a structural block diagram of a computing device 800 according to an embodiment of this specification. The components of the computing device 800 include but are not limited to a memory 810 and a processor 820. The processor 820 is connected to the memory 810 through a bus 830, and a database 850 is used to store data.

[0087] The computing device 800 also includes an access device 840 that enables the computing device 800 to communicate via one or more networks 860. Examples of such networks include the Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 840 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.

[0088] In one embodiment of the present specification, the above components of the computing device 800, as well as Figure 8 other components not shown, may also be connected to each other, for example, via a bus. It should be understood that Figure 8 the block diagram of the computing device shown is for illustrative purposes only and is not a limitation on the scope of the present specification. Those skilled in the art may add or replace other components as needed.

[0089] The computing device 800 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smartwatch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a Personal Computer (PC). The computing device 800 can also be a mobile or stationary server.

[0090] Among them, the processor 820 is used to execute the following computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above-mentioned embedded log analysis method are implemented. The above is a schematic solution of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the above-mentioned embedded log analysis method belong to the same concept. For the details not described in detail in the technical solution of the computing device, reference can be made to the description of the technical solution of the above-mentioned embedded log analysis method.

[0091] An embodiment of this specification also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above-mentioned embedded log analysis method are implemented.

[0092] The above is a schematic solution of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the above-mentioned embedded log analysis method belong to the same concept. For the details not described in detail in the technical solution of the storage medium, reference can be made to the description of the technical solution of the above-mentioned embedded log analysis method.

[0093] An embodiment of this specification also provides a computer program. Among them, when the computer program is executed on a computer, the computer is made to execute the steps of the above-mentioned embedded log analysis method.

[0094] The above is a schematic solution of a computer program according to this embodiment. It should be noted that the technical solution of this computer program and the technical solution of the above-mentioned embedded log analysis method belong to the same concept. For the details not described in detail in the technical solution of the computer program, reference can be made to the description of the technical solution of the above-mentioned embedded log analysis method.

[0095] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be executed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the specific order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0096] The computer instructions include computer program code, which may be in the form of source code, object code, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice within the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0097] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the embodiments of this specification are not limited by the described action sequence, because according to the embodiments of this specification, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential for the embodiments of this specification.

[0098] In the above embodiments, the descriptions of each embodiment have their own focuses. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0099] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The alternative embodiments do not describe all the details in detail, nor do they limit the invention to the specific embodiments described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments of this specification, so that those skilled in the art can well understand and utilize this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. An embedded log analysis method, characterized in that: include: Obtaining a telemetry data source code, and performing parsing based on the telemetry data source code to determine telemetry parsed data; Determine fault identification data based on the telemetry analysis data; wherein the fault identification data includes fault data and / or tracing data, the fault data is used to identify the fault point, and the tracing data is used to reproduce the scene; Fault analysis is performed based on the fault identification data and the logic association library to obtain the cause of the fault.

2. The method according to claim 1, characterized in that The step of parsing and determining telemetry parsed data based on the telemetry data source code includes: Determining bit source code data based on the telemetry data source code; The bit source code data is converted into telemetry parsed data according to a preset conversion rule.

3. The method according to claim 1, characterized in that The determining of fault identification data based on the telemetry analysis data comprises: Extracting a target fault code from the telemetry analysis data; wherein the target fault code is a fault code of the current telemetry cycle; Comparing the target fault code with a fault logic association library to determine a fault comparison result; wherein the fault logic association library includes at least two of the fault codes and at least two logical associations between the fault codes and telemetry physical quantities; When the fault comparison result is the target fault code in the fault logic association inventory, the target fault code is used as the fault data.

4. The method according to claim 1 or 3, characterized in that: The determining of fault identification data based on the telemetry analysis data comprises: Extracting a target tracking code from the telemetry parsed data; wherein the target tracking code is a tracking code of a current telemetry cycle; Compare the target tracking code with the tracking logic association library to determine the tracking comparison result; wherein the tracking logic association library includes at least two tracking codes and at least two logical associations between the tracking codes and telemetered physical quantities; When the tracking comparison result is that the target tracking code exists in the tracking logic association library, the target tracking code is used as the tracking data.

5. The method according to claim 4, characterized in that The performing fault analysis based on the fault identification data and the logic association library includes: extracting fault details from the telemetry parsed data in the case where the fault identification data includes the fault data; Acquire a corresponding first telemetry physical quantity from a fault logic association library based on the fault data and the fault details; Perform fault analysis based on the first telemetry physical quantity to determine the cause of the fault.

6. The method according to claim 5, characterized in that The performing fault analysis based on the fault identification data and the logic association library includes: In the case where the fault identification data includes the tracking data, or in the case where the fault identification data includes the tracking data and the fault analysis based on the first telemetered physical quantity fails to determine the cause of the fault, extracting tracking details from the telemetered parsed data; acquiring the corresponding second telemetered physical quantity and expected tracking details based on the tracking code and the tracking logic association library; generating historical tracking details based on the second telemetric physical quantity; A cause of a fault is determined based on the historical tracing details and the expected tracing details.

7. The method according to claim 1, characterized in that Also includes: After determining the cause of the fault, obtaining a solution from the logic association library based on the cause of the fault, and displaying the solution; When the cause of the fault is not determined, the tracing data and the fault data are displayed to perform a fault analysis based on the tracing data and the fault data.

8. An embedded log analysis device, characterized in that: include: A data acquisition module is configured to acquire a telemetry data source code, and perform parsing based on the telemetry data source code to determine telemetry parsed data; A data analysis module is configured to determine fault identification data based on the telemetry analysis data; wherein the fault identification data includes fault data and / or tracing data, the fault data is used to identify the fault point, and the tracing data is used to reproduce the scene; The fault judgment module is configured to perform fault analysis based on the fault identification data and the logic association library to obtain the cause of the fault.

9. A computing device, characterized in that include: Memory and processor; The memory is used to store computer executable instructions, and the processor is used to execute the computer executable instructions. When the computer executable instructions are executed by the processor, the steps of the embedded log analysis method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the steps of the embedded log analysis method according to any one of claims 1 to 7.

Images