Embedded log analysis method and apparatus

Abstract

The embodiment of the present specification provides an embedded log analysis method and device, wherein the embedded log analysis method comprises: acquiring telemetry data source code, determining telemetry analysis data based on the telemetry data source code; 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 fault points, and the tracking data is used for scene reproduction; performing fault analysis based on the fault identification data and a logical association library to obtain fault causes. Through the fault data and the tracking data in the above scheme, the memory and bandwidth consumption of logs in rocket-ground communication can be reduced, and automatic analysis based on the fault data and the tracking data can be realized, thereby improving the accuracy and speed of fault positioning.

Description

TECHNICAL FIELD

[0001] Embodiments of the present specification relate to the field of aerospace technology, and in particular to an embedded log analysis method. BACKGROUND

[0002] In the field of aerospace, as a core component, the flight control system effectively records and analyzes its log data in each test, which is crucial for key technology verification, accumulation and iteration. The existing log system usually records log data in non-volatile memory or sends it to the ground test and control equipment through a wireless link. These log systems have the following disadvantages: the log data structure needs to occupy a large hardware memory resource or wireless link bandwidth resource; the log output to the target medium needs to consume part of the time resource, which may affect the system performance; a large amount of log data usually needs to be analyzed offline by manual; it is difficult to quickly select and comprehensively analyze multiple data sources; it is difficult to quickly locate the system failure cause and give the solution; it is not possible to efficiently reproduce the specific scene and logic branch of the software execution.

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

[0004] Therefore, a better solution is needed. SUMMARY

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

[0006] According to a first aspect of the embodiments of the present specification, an embedded log analysis method is provided, comprising:

[0007] Obtaining a telemetry data source code, and determining telemetry analysis data based on the telemetry data source code;

[0008] Determining fault identification data based on the telemetry analysis data; wherein the fault identification data includes fault data and / or tracking data, the fault data is used to identify fault points, and the tracking data is used for scene reproduction;

[0009] Performing fault analysis based on the fault identification data and a logic association library to obtain fault causes.

[0010] In one possible implementation, determining telemetry analysis data based on the telemetry data source code includes:

[0011] Determine bit source code data based on telemetry data source code;

[0012] Convert the bit source code data into telemetry analysis data according to a preset conversion rule.

[0013] In a possible implementation, determining fault identification data based on the telemetry analysis data comprises:

[0014] Extract a target fault code from the telemetry analysis data; wherein the target fault code is a fault code of a current telemetry period;

[0015] Compare the target fault code with a fault logic association library to determine a fault comparison result; wherein the fault logic association library comprises at least two fault codes, and a logical association relationship between the at least two fault codes and telemetry physical quantities;

[0016] In a case where the fault comparison result is that the target fault code exists in the fault logic association library, take the target fault code as fault data.

[0017] In a possible implementation, determining fault identification data based on the telemetry analysis data comprises:

[0018] Extract a target tracking code from the telemetry analysis data; wherein the target tracking code is a tracking code of a current telemetry period;

[0019] Compare the target tracking code with a tracking logic association library to determine a tracking comparison result; wherein the tracking logic association library comprises at least two tracking codes, and a logical association relationship between the at least two tracking codes and telemetry physical quantities;

[0020] In a case where the tracking comparison result is that the target tracking code exists in the tracking logic association library, take the target tracking code as tracking data.

[0021] In a possible implementation, performing fault analysis based on the fault identification data and the logical association library comprises:

[0022] In a case where the fault identification data comprises fault data, extract fault details from the telemetry analysis data;

[0023] Obtain a corresponding first telemetry physical quantity from the fault logic association library based on the fault data and the fault details;

[0024] Perform fault analysis based on the first telemetry physical quantity to determine a fault cause.

[0025] In a possible implementation, performing fault analysis based on the fault identification data and the logical association library comprises:

[0026] In a case where the fault identification data includes the trace data, or in a case where the fault identification data includes the trace data and the fault analysis is based on the first telemetry physical quantity, the trace details are extracted from the telemetry analysis data; the corresponding second telemetry physical quantity and the expected trace details are obtained based on the trace code and the trace logic association library;

[0027] The historical trace details are generated based on the second telemetry physical quantity;

[0028] The fault cause is determined based on the historical trace details and the expected trace details.

[0029] In a possible implementation, the method further includes:

[0030] After the fault cause is determined, a solution measure is obtained from the logic association library based on the fault cause, and the solution measure is displayed;

[0031] In a case where the fault cause is not determined, the trace data and the fault data are displayed to perform the fault analysis based on the trace data and the fault data.

[0032] According to a second aspect of an embodiment of the present specification, an embedded log analysis apparatus is provided, including:

[0033] A data acquisition module configured to acquire telemetry data source code, and determine telemetry analysis data based on the telemetry data source code;

[0034] 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 a fault point, and the trace data is used to perform scenario reproduction;

[0035] A fault judgment module configured to perform fault analysis based on the fault identification data and a logic association library, to obtain a fault cause.

[0036] According to a third aspect of an embodiment of the present specification, a computing device is provided, including:

[0037] A memory and a processor;

[0038] The memory is configured to store computer executable instructions, and the processor is configured to execute the computer executable instructions, and the computer executable instructions, when executed by the processor, implement the steps of the above-mentioned embedded log analysis method.

[0039] According to a fourth aspect of an embodiment of the present specification, a computer readable storage medium is provided, which stores computer executable instructions, and the instructions, when executed by a processor, implement the steps of the above-mentioned embedded log analysis method.

[0040] According to a fifth aspect of the embodiments of the present specification, a computer program is provided, which, when executed in a computer, causes the computer to perform the steps of the embedded log analysis method described above.

[0041] The embodiments of the present specification provide an embedded log analysis method and device, wherein the embedded log analysis method comprises: obtaining telemetry data source code, determining telemetry analysis data based on the telemetry data source code; 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 to identify fault points, and the tracking data is used to reproduce scenes; performing fault analysis based on the fault identification data and a logical association library to obtain fault causes. Through the fault data and the tracking data in the above scheme, the memory and bandwidth consumption of logs in rocket-ground communication can be reduced, and automatic analysis based on the fault data and the tracking data can be realized, thereby improving the accuracy and speed of fault positioning. BRIEF DESCRIPTION OF DRAWINGS

[0042] Figure 1 is a flowchart of an embedded log analysis method provided by an embodiment of the present specification;

[0043] Figure 2 is a fault code schematic diagram of an embedded log analysis method provided by an embodiment of the present specification;

[0044] Figure 3 is a tracking code schematic diagram of an embedded log analysis method provided by an embodiment of the present specification;

[0045] Figure 4 is a tracking marker code schematic diagram of an embedded log analysis method provided by an embodiment of the present specification;

[0046] Figure 5 is an interface code schematic diagram of an embedded log analysis method provided by an embodiment of the present specification;

[0047] Figure 6 is an architecture schematic diagram of an embedded log analysis method provided by an embodiment of the present specification;

[0048] Figure 7 is a structural schematic diagram of an embedded log analysis device provided by an embodiment of the present specification;

[0049] Figure 8 is a structural block diagram of a computing device provided by an embodiment of the present specification. DETAILED DESCRIPTION

[0050] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. However, the present description can be practiced without the specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the present description.

[0051] The terminology used in this description is for the purpose of describing particular embodiments only and is not intended to be limiting of one or more embodiments of the present description. As used in this description and the appended claims, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0052] It will be understood that, although the terms first, second, etc. can be used herein to describe various information, these terms are not intended to denote a temporal sequence. Rather, these terms are used only as distinguish one from another. For example, without departing from the scope of one or more embodiments, first can be termed second, and similarly, second can be termed first. The word "if' as used herein means "when" or "upon" or "in response to the determination" depending on the context.

[0053] In the present description, an embedded log analysis method is provided, and the present description also relates to an embedded log analysis device, a computing device, and a computer readable storage medium, which are described in detail one by one in the following embodiments.

[0054] Referring to Figure 1 , Figure 1 A flow chart of an embedded log analysis method according to an embodiment of the present description is shown, which specifically includes the following steps.

[0055] Step 101: Obtain telemetry data source code, and determine telemetry analysis data based on the telemetry data source code;

[0056] The telemetry data source code is data source code transmitted by a rocket to the ground according to a period, such as a binary bit stream. The telemetry analysis data is data obtained by analyzing the telemetry data source code according to a set rule, such as converting binary data into decimal data.

[0057] In a possible implementation, the step of determining telemetry analysis data based on the telemetry data source code includes: determining bit source code data based on the telemetry data source code; and converting the bit source code data into telemetry analysis data according to a preset conversion rule.

[0058] wherein the bit source code data can be binary bit stream data.

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

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

[0061] The embodiment of the present specification converts the telemetry data source code into telemetry analysis data, which facilitates subsequent identification and analysis by the staff.

[0062] Step 102: determining fault identification data based on the telemetry analysis data; wherein the fault identification data includes fault data and / or tracking data, the fault data is used to identify fault points, and the tracking data is used for scene reproduction.

[0063] Wherein, the fault identification data is data used for fault identification. The fault data can be data inserted into the telemetry data source code by the rocket in a telemetry period, and correspondingly, the tracking data can be data inserted into the telemetry data source code by the rocket in a telemetry period. The fault data and the tracking data can be in two parts of the telemetry data source code.

[0064] In practical applications, an on-board log recording module can be set up. The log recording module records the fault code (EC: Error Code) and the tracking code (TC: Track Code) of the system running through the bit pattern efficiently, which facilitates quick locking of problems during data analysis; and provides detailed error statistics and state tracking capabilities through the fault details (ErrorInfo_t) and tracking details (TrackInfo_t).

[0065] Further, the on-board log recording module specifically needs to include the following functions: modular classification: classify the fault code and the tracking code according to the function module, which facilitates maintenance and expansion. Bit field compression storage: use bit field (Bit-field) and union (Union) to store the state compactly, saving memory space. State statistics: record the number of triggers of each code through the counting array, which assists in problem positioning and performance analysis. In the design of fault / tracking code, use EC_SET macro to define various fault codes (EC: Error Code), such as the specific fault codes contained in the bottom driver, application protocol, telemetry and control process modules given in Figure 2 . Use TC_SET macro to define various tracking codes (TC: Track Code), such as the specific fault codes contained in the bottom driver, application protocol, telemetry and control process modules given in Figure 3The specific tracking code contained in the initial alignment, composite navigation, and other modules given in the examples.

[0066] Specifically, the EC_SET and TC_SET are expanded into enumeration members by the X(x) macro, the fault enumeration type (ErrorCode_t) and the tracking enumeration type (TrackCode_t) are automatically generated, and the total number of fault codes and the total number of tracking codes are counted by EC_Num and TC_Num respectively. The union body_TRACE_TYPE_BITS defines the fault bit field (ErrorBits_t) and the tracking bit field (TrackBits_t), which combines the bit field with the buffer to realize two access methods:

[0067] a) Bit operation: each fault or tracking code corresponds to a bit, and setting 1 indicates triggering, which supports fast state marking;

[0068] b) Buffer storage: it is convenient to store or transmit the bit field data in the form of a block of memory.

[0069] The fault details (ErrorInfo_t) record specific fault codes (TransInfo_t.code), fault code description information (TransInfo_t.desc), fault bit fields (bits), and fault count arrays (bitCnt), etc. The tracking details (TrackInfo_t) record specific tracking codes (TransInfo_t.code), tracking code description information (TransInfo_t.desc), tracking bit fields (bits), and tracking count arrays (bitCnt), etc.

[0070] Referring to Figure 4 Taking the tracking details as an example (the fault details are the same), the analysis is as follows: in terms of storage resources (hardware memory or communication bandwidth), 1 bit is used to represent 1 logical branch marker, and the maximum number of logical branches that can be marked by a single control cycle tracking details is: N*8 / P, where N represents the number of bytes occupied by a single output cycle tracking details, and P represents the number of control cycles contained in a single output cycle.

[0071] For example, in the rocket flight control system, the control cycle is usually 10 ms, assuming that the flight control software sends 20 bytes of tracking details to the ground measurement and control system at a period of 100 ms, the maximum number of logical branches that can be marked by a single control cycle tracking detail is 16. If the communication bandwidth allows, the flight control software outputs tracking details at the control cycle, the maximum number of logical branches that can be marked increases to 160, which can cover each software running branch. Considering the communication bandwidth and the complexity of the flight control software control logic: in the case of tight communication bandwidth, the tracking details can record the execution of the key software module logical branch first; in the case of sufficient communication bandwidth, the tracking details can record as many software logical branches as possible.

[0072] Further, on the interface, see Figure 5 Taking the tracking log record as an example (the fault log record is the same), in actual use, first, the tracking log initialization interface (TRACK_BEGIN) is called to set the starting state; then the tracking log record interface (TRACK_RECORD) is called to mark the target logical branch. When marking, the target tracking code is used to directly assign values to the tracking bit field corresponding bits, and the system time resources consumed can be ignored.

[0073] It should be noted that the data size of the fault code, the tracking code, the tracking details and the fault details needs to be set according to the actual situation, for example, in a period, the idle communication resources are high, then the data of the fault code, the tracking code, the tracking details and the fault details can be more, and the idle communication resources are less, then the data of the fault code, the tracking code, the tracking details and the fault details need to be reduced, so as not to affect the normal task.

[0074] In a possible implementation, the fault identification data is determined based on the telemetry analysis data, including: extracting a target fault code from the telemetry analysis data; wherein the target fault code is a fault code of a current telemetry period; 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 fault codes and a logical association relationship between the at least two fault codes and telemetry physical quantities; in the case that the fault comparison result is that the target fault code is stored in the fault logic association library, the target fault code is taken as the fault data.

[0075] Wherein, 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 and telemetry physical quantities and fault reasons set on the ground according to artificial experience knowledge.

[0076] In actual application, when there is a fault code in the telemetry analysis data, the data corresponding to the fault code can be extracted, so that the fault identification data can be determined.

[0077] For example, four logical branches A, B, C, and D are included in the rocket, and the corresponding decimal fault codes are 1, 2, 3, and 4. 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.

[0078] In the embodiments of the present specification, the fault code in the telemetry data source code is obtained, and the obtained fault code is matched with the faults in the fault logic association library, so as to determine the fault in the current period, thereby improving the fault positioning speed.

[0079] In a possible implementation, the fault identification data is determined based on the telemetry analysis data, including: extracting a target tracking code from the telemetry analysis data; wherein the target tracking code is a tracking code of a current telemetry period; comparing the target tracking code with a tracking logic association library to determine a tracking comparison result; wherein the tracking logic association library includes at least two tracking codes, and a logical association relationship between the at least two tracking codes and a telemetry physical quantity; in a case where the tracking comparison result is that the target tracking code exists in the tracking logic association library, the target tracking code is taken as tracking data.

[0080] The target tracking code is data used to identify an execution action of the current period, and the tracking logic association library is a database of set tracking codes, telemetry physical quantities, and telemetry physical quantities and fault causes.

[0081] In actual application, when the tracking code exists in the telemetry analysis data, the data corresponding to the tracking code can be extracted, so as to be determined as the fault identification data.

[0082] For example, four logical branches A, B, C, and D are included in the rocket, and the corresponding decimal tracking codes are 1, 2, 3, and 4. The tracking 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 tracking logic association library, and the tracking data is 3.

[0083] In the embodiments of the present specification, the tracking code in the telemetry data source code is obtained, and the obtained tracking code is matched with the tracking logic association library, so as to determine the action being executed in the current period, thereby improving the speed of scene reproduction.

[0084] Step 103: performing fault analysis based on the fault identification data and the logic association library to obtain a fault cause.

[0085] In actual application, referring to Figure 6The log analysis software can be deployed on the ground, and the log analysis software takes the telemetry analysis data and the logical correlation library as input, automatically processes the log data through the fault automatic analysis module and the scene reproduction analysis module (in an online or offline manner), and displays the analysis result to a human-computer interaction interface or stores the analysis result in an analysis document.

[0086] It should be noted that the corresponding logical correlation library can be customized according to the telemetry data protocol agreement and combined with the professional data analysis requirements, and the specific implementation of the logical correlation library is not limited in the embodiments of the present specification.

[0087] In a possible implementation, the fault analysis based on the fault identification data and the logical correlation library includes: in a case where the fault identification data includes fault data, extracting fault details from the telemetry analysis data; obtaining corresponding first telemetry physical quantities from the fault logical correlation library based on the fault data and the fault details; and performing fault analysis based on the first telemetry physical quantities to determine a fault cause.

[0088] The fault details are all fault codes recorded in a current telemetry period. The first telemetry physical quantities are the telemetry physical quantities corresponding to the fault details.

[0089] In actual application, the logical correlation relationship between each fault code and other telemetry physical quantities that can cause the fault is set in the fault logical correlation library. When a certain fault code in the fault details corresponds to bit setting, the log analysis software automatically obtains and processes the associated physical quantities according to the fault correlation relationship set in the correlation library, and gives the specific cause of the fault and possible solutions, wherein the cause and the solutions can be selectively added to the correlation library, and different professional designers can give the a priori conclusions and experience.

[0090] In the above example, four logical branches A, B, C and D are included in the rocket, and the corresponding decimal fault codes are 1, 2, 3 and 4. The fault code in the received telemetry data source code in a certain period is 00000011, which can be analyzed as a decimal number 3. The fault code 3 can be found in the fault logical correlation library, the fault data is 3, the corresponding logical branch is C, the physical quantity corresponding to C is the related physical quantity of power supply conversion, and the fault cause is power supply conversion fault.

[0091] Further, the electrical system designer associates the power conversion failure with the flight control time, the telemetry physical quantity of the launch control flow execution flag, and the on-board thermal battery bus voltage, and the failure association logic is: 1) the thermal battery activation flow completion flag is invalid after the power conversion flow start flag is valid; 2) the time elapsed from the power conversion flow start flag being valid to the thermal battery bus voltage being valid is greater than a given time index, and the possible solution measures are: 1) ensure that the power conversion is performed after the thermal battery is activated; 2) check whether the power conversion circuit is faulty; 3) change the thermal battery bus voltage effective judgment threshold; and 4) change the time index required for power conversion to be completed.

[0092] It should be noted that the analysis process of the failure details is the same as the failure code, for example, the failure details are 00000101, the first position 1 from right to left indicates that A is faulty, and the third position 1 indicates that C is faulty.

[0093] The embodiments of the present specification realize rapid positioning of the failure by means of the failure code and the failure details, realize failure analysis and give a failure solution, and improve the failure solution speed.

[0094] In a possible implementation, the failure analysis is performed based on the failure identification data and the logic association library, including: in the case where the failure identification data includes tracking data, or in the case where the failure identification data includes tracking data and the failure analysis based on the first telemetry physical quantity fails to determine the failure cause, extracting tracking details from the telemetry analysis data; obtaining corresponding second telemetry 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 telemetry physical quantity; and determining the failure cause based on the historical tracking details and the expected tracking details.

[0095] The tracking details are all tracking codes recorded in the current telemetry period, i.e., all 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 be executed under normal circumstances.

[0096] In practical applications, the tracking details record the execution of each control cycle of the flight control software logic branch in detail, and in the actual data analysis process, the designer can select one or several control cycles for scene reproduction. In the tracking logic association library, the value (data value or state value, which can be a secondary calculation value) of one or more telemetry physical quantities is set in association with the tracking details (recorded as an association rule, and the designer can set multiple similar association rules according to the actual analysis requirements to form a professional association rule library). When the log analysis software traverses the telemetry data, it determines in real time whether the selected physical quantity value meets the trigger condition given in the association rule. If it meets, it compares whether the expected tracking details (expected software logic branch execution) given in the association rule and the actual tracking details (actual software logic branch execution) recorded in the current control cycle telemetry data are consistent. If they are not consistent, further comprehensive analysis of the specific reasons is needed.

[0097] It should be noted that the present scheme can directly reproduce the scene through the tracking code, or reproduce the scene when the fault code cannot determine the fault reason.

[0098] In the above example, four logic branches A, B, C, and D are included in the rocket, and the corresponding decimal tracking codes are 1, 2, 3, and 4. The tracking code in the telemetry data source code received in a certain cycle is 00000101, which can be parsed as a decimal number 3. Then, the fault code 3 can be found in the tracking logic association library, and the tracking data is 3, which can determine that the currently executed logic branch is C. In the tracking logic association library, the guidance control designer associates the flight timing state quantity (1 bit corresponds to one flight timing point, such as bit0 corresponds to the start-up time, bit1 corresponds to the engine depletion time, etc.) with the tracking details. From the tracking logic association library, the flight timing state quantity corresponding to C is determined, and according to the flight control model mathematical simulation result, multiple association rules are formed to represent that the software should be able to cover the given logic branch after running to a certain flight stage, i.e., the expected tracking details.

[0099] Further, the tracking 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. Finally, it is judged whether it is consistent with the expected tracking details.

[0100] The embodiments of the present specification determine the executed logic branch of the rocket by setting the tracking code and the tracking details, so that the execution of the rocket can be reproduced on the ground, and the fault analysis can be performed, thereby improving the accuracy of the fault analysis and increasing the data basis for the fault analysis.

[0101] In a possible implementation, the method further includes: after determining the fault cause, obtaining a solution measure from the logical association library based on the fault cause, and displaying the solution measure; and in a case where the fault cause is not determined, displaying the tracking data and the fault data, so that a worker analyzes the fault based on the tracking data and the fault data.

[0102] In actual application, the logical association relationship between each fault code and the tracking details that can cause the fault is set in the fault logical association library. When a fault code in the fault details corresponds to a bit set, the log analysis software automatically obtains the processing of the associated physical quantity according to the fault association relationship set in the association library, and gives the specific cause of the fault and the possible solution measure.

[0103] It should be noted that, in the case of telemetry communication bandwidth, the fault code can be as detailed as possible, that is, the flight control software needs to add fault detail set operation as much as possible in all corresponding fault logic branches, and the log analysis software can give the specific cause of the fault and the possible solution measure without configuring the association library.

[0104] In the above example, the fault association logic is: 1) the hot battery activation process completion flag is invalid after the power conversion process start flag is valid; and 2) the time elapsed from when the power conversion process start flag is valid to when the hot battery bus voltage is valid is greater than a given time index. In the valid branches of the two fault association logics, corresponding fault detail set operations are added, respectively, so that the same analysis effect can be achieved.

[0105] The embodiments of the present specification provide an embedded log analysis method and device, wherein the embedded log analysis method comprises: obtaining telemetry data source code, and determining telemetry analysis data based on the telemetry data source code; 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 to identify a fault point, and the tracking data is used to reproduce a scene; performing fault analysis based on the fault identification data and a logical association library to obtain a fault cause.

[0106] Through the fault data and the tracking data in the above scheme, the memory and bandwidth consumption of logs can be reduced in rocket-ground communication, and automatic analysis based on the fault data and the tracking data can be implemented, so as to improve the accuracy and speed of fault positioning.

[0107] In an overall embodiment, the flight control software of the rocket sends the ground telemetry data source code to the ground launch control system at a period of 100 ms, and the rocket includes four logical branches A, B, C and D, which correspond to the decimal fault codes 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, and 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, and 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 tracking code in the telemetry data source code is 00000011, which can be parsed as the decimal number 3, and then the fault code 3 can be found in the tracking logic association library, and the tracking data is 3. The tracking details are 00000111, and 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.

[0108] After obtaining the fault data and the tracking data, fault analysis can be performed. The physical quantity corresponding to C is the related physical quantity of power supply conversion, and the fault reason of power supply conversion is determined. It can also be determined from the fault details that A has a fault. The fault reasons and solutions of A and C are obtained from the fault logic association library.

[0109] Further, the tracking data is 3, and it can be determined that the currently executed logical branch is C. The tracking details are 00000111, and 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. It is judged whether it is consistent with the expected tracking details. If it is not consistent, the corresponding fault reason and solution are obtained from the fault logic association library.

[0110] In the above steps, if the fault logic association library does not find the corresponding fault code, fault reason or solution, the scene can be reproduced directly through the tracking code and the tracking details, so that the staff can analyze the fault. The scene can also be reproduced directly after obtaining the tracking code and the tracking details.

[0111] Corresponding to the method embodiment, the present specification also provides an embedded log analysis device embodiment, Figure 7 The structure of an embedded log analysis device provided by an embodiment of the present specification is shown. As Figure 7 shown, the device includes:

[0112] The data acquisition module 701 is configured to acquire the telemetry data source code, parse the telemetry data source code to determine the telemetry parsed data;

[0113] The data analysis module 702 is configured to determine 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 to identify a fault point, and the tracking data is used for scenario reproduction;

[0114] The fault judgment module 703 is configured to perform fault analysis based on the fault identification data and the logical association library to obtain a fault cause.

[0115] In a possible implementation, the telemetry analysis data is determined based on telemetry data source code, comprising:

[0116] The bit source code data is determined based on the telemetry data source code;

[0117] The bit source code data is converted into the telemetry analysis data according to a preset conversion rule.

[0118] In a possible implementation, the fault identification data is determined based on the telemetry analysis data, comprising:

[0119] A target fault code is extracted from the telemetry analysis data; wherein the target fault code is a fault code of a current telemetry period;

[0120] The target fault code is compared with a fault logical association library to determine a fault comparison result; wherein the fault logical association library comprises at least two fault codes and a logical association relationship between the at least two fault codes and telemetry physical quantities;

[0121] In a case where the fault comparison result is that the target fault code exists in the fault logical association library, the target fault code is taken as fault data.

[0122] In a possible implementation, the fault identification data is determined based on the telemetry analysis data, comprising:

[0123] A target tracking code is extracted from the telemetry analysis data; wherein the target tracking code is a tracking code of a current telemetry period;

[0124] The target tracking code is compared with a tracking logical association library to determine a tracking comparison result; wherein the tracking logical association library comprises at least two tracking codes and a logical association relationship between the at least two tracking codes and telemetry physical quantities;

[0125] In a case where the tracking comparison result is that the target tracking code exists in the tracking logical association library, the target tracking code is taken as tracking data.

[0126] In a possible implementation, the fault analysis is performed based on the fault identification data and the logical association library, comprising:

[0127] In a case where the fault identification data comprises fault data, fault details are extracted from the telemetry analysis data;

[0128] obtain corresponding first telemetry physical quantity from the fault logic association library based on the fault data and the fault details;

[0129] perform fault analysis based on the first telemetry physical quantity, and determine the fault cause.

[0130] In a possible implementation, performing fault analysis based on the fault identification data and the logic association library comprises:

[0131] In a case where the fault identification data comprises tracking data, or in a case where the fault identification data comprises tracking data and the fault analysis based on the first telemetry physical quantity fails to determine the fault cause, extract tracking details from the telemetry analysis data; obtain corresponding second telemetry physical quantity and expected tracking details based on the tracking code and the tracking logic association library;

[0132] generate historical tracking details based on the second telemetry physical quantity;

[0133] determine the fault cause based on the historical tracking details and the expected tracking details.

[0134] In a possible implementation, the method further comprises:

[0135] after determining the fault cause, obtain a solution measure from the logic association library based on the fault cause, and display the solution measure;

[0136] in a case where the fault cause is not determined, display the tracking data and the fault data, so that a worker performs fault analysis based on the tracking data and the fault data.

[0137] The embodiments of the present specification provide an embedded log analysis method and device, wherein the embedded log analysis device comprises: obtaining telemetry data source code, performing analysis based on the telemetry data source code to determine telemetry 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 to identify a fault point, and the tracking data is used to perform scenario reproduction; performing fault analysis based on the fault identification data and a logic association library to obtain a fault cause. Through the fault data and the tracking data in the above scheme, the memory and bandwidth consumption of logs in rocket-ground communication can be reduced, and automatic analysis based on the fault data and the tracking data can be performed, thereby improving the accuracy and speed of fault positioning.

[0138] The above is a schematic scheme of an embedded log analysis device of the present embodiment. It should be noted that the technical scheme of the embedded log analysis device belongs to the same concept as the technical scheme of the embedded log analysis method described above, and the details of the technical scheme of the embedded log analysis device that are not described in detail can be referred to the description of the technical scheme of the embedded log analysis method.

[0139] Figure 8 A structural block diagram of a computing device 800 is shown, according to one embodiment of the present 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.

[0140] The computing device 800 also includes an access device 840, which enables the computing device 800 to communicate via one or more networks 860. Examples of these networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 840 can include one or more of any type of 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, a Near Field Communication (NFC).

[0141] In one embodiment of the present specification, the above-mentioned components of the computing device 800 and other components not shown in the Figure 8 may be connected to each other, for example, through a bus. It should be understood that Figure 8 The structural block diagram of the computing device shown is only for the purpose of example, and is not a limitation on the scope of the present specification. Other components can be added or replaced as needed by those skilled in the art.

[0142] 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 smart watch, smart glasses, etc.), or other type of mobile device, 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.

[0143] The processor 820 is configured to execute computer-executable instructions to perform the steps of the above-mentioned embedded log analysis method. The above is a schematic solution of a computing device according to an embodiment of the present disclosure. It should be noted that the technical solution of the computing device and the technical solution of the above-mentioned embedded log analysis method belong to the same concept, and the details of the technical solution of the computing device not described in detail can be referred to the description of the technical solution of the above-mentioned embedded log analysis method.

[0144] An embodiment of the present disclosure further provides a computer-readable storage medium, which stores computer-executable instructions. The computer-executable instructions, when executed by a processor, implement the steps of the above-mentioned embedded log analysis method.

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

[0146] An embodiment of the present disclosure further provides a computer program. When the computer program is executed in a computer, the computer program causes the computer to perform the steps of the above-mentioned embedded log analysis method.

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

[0148] The above-described embodiments of the application have several aspects, no single one of which is solely responsible for the application's desirable attributes. Without limiting the scope of this application as to its specific aspects, some advantages thereby are that the application can provide a method and system for providing a user with a more personalized experience.

[0149] The computer readable medium can include any entity or apparatus capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable medium can include appropriate contents according to the requirements of legislation and patent practice in 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.

[0150] It should be noted that for the foregoing method embodiments, the acts described therein can be performed in a different order from the order described, and that certain acts can be performed in parallel or concurrently. In addition, certain acts can be omitted, and other acts can be added. Furthermore, the acts described in the specification can be implemented as a set of computer readable instructions, software, or firmware that is executed by a computer system, such as the computer system 1000. It should be noted that the computer readable instructions, software, or firmware can be loaded into the computer system 1000 from a computer readable medium, such as the computer readable medium 1002.

[0151] In the above embodiments, the description of each embodiment is focused on a certain aspect, and the part not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0152] The preferred embodiments of the present specification disclosed above are only used to help explain the present specification. The alternative embodiments do not describe all the details and do not limit the application to the specific embodiments described. Obviously, according to the content of the embodiments of the present specification, many modifications and changes can be made. The present specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of the present specification, so that those skilled in the art can well understand and use the present specification. The present specification is limited only by the claims and their full scope and equivalents.

Claims

1. An embedded log analysis method, characterized by, The method comprises the following steps: acquiring a telemetry data source code, and determining telemetry analysis data by analyzing the telemetry data source code; 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 to identify fault points, and the tracking data is used to reproduce a scene; performing fault analysis based on the fault identification data and a logical association library to obtain a fault cause; the step of determining 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 a current telemetry period; comparing the target fault code with a fault logical association library to determine a fault comparison result; wherein the fault logical association library comprises at least two fault codes and a logical association relationship between the at least two fault codes and telemetry physical quantities; in a case where the fault comparison result is that the target fault code exists in the fault logical association library, taking the target fault code as the fault data; the step of determining fault identification data based on the telemetry analysis data comprises: extracting a target tracking code from the telemetry analysis data; wherein the target tracking code is a tracking code of a current telemetry period; comparing the target tracking code with a tracking logical association library to determine a tracking comparison result; wherein the tracking logical association library comprises at least two tracking codes and a logical association relationship between the at least two tracking codes and telemetry physical quantities; in a case where the tracking comparison result is that the target tracking code exists in the tracking logical association library, taking the target tracking code as the tracking data.

2. The method of claim 1, wherein, the step of determining telemetry analysis data by analyzing the telemetry data source code comprises: determining bit source code data based on the telemetry data source code; converting the bit source code data into telemetry analysis data according to a preset conversion rule.

3. The method of claim 1, wherein, the step of performing fault analysis based on the fault identification data and the logical association library comprises: in a case where the fault identification data comprises the fault data, extracting fault details from the telemetry analysis data; acquiring corresponding first telemetry physical quantities from a fault logical association library based on the fault data and the fault details; performing fault analysis based on the first telemetry physical quantities to determine a fault cause.

4. The method of claim 3, wherein, the step of performing fault analysis based on the fault identification data and the logical association library comprises: in a case where the fault identification data comprises the tracking data, or in a case where the fault identification data comprises the tracking data and the fault analysis based on the first telemetry physical quantities fails to determine a fault cause, extracting tracking details from the telemetry analysis data; acquiring corresponding second telemetry physical quantities and expected tracking details based on the tracking code and a tracking logical association library; generating historical tracking details based on the second telemetry physical quantities; determining a fault cause based on the historical tracking details and the expected tracking details.

5. The method of claim 1, wherein, The method further comprises the following steps: after determining the fault cause, acquiring a solution measure from the logical association library based on the fault cause, and displaying the solution measure. In the case where the fault cause is not determined, the tracking data and the fault data are displayed to perform fault analysis based on the tracking data and the fault data.

6. An embedded log analysis apparatus, characterized by comprising: Steps for implementing the embedded log analysis method of any one of claims 1 to 5, comprising: a data acquisition module configured to acquire telemetry data source code, and determine telemetry analysis data based on the telemetry data source code; a data analysis module configured to determine 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 to identify fault points, and the tracking data is used to reproduce scenes; a fault judgment module configured to perform fault analysis based on the fault identification data and a logical association library to obtain a fault cause.

7. A computing device, comprising: comprising: 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, which, when executed by the processor, implement the steps of the embedded log analysis method of any one of claims 1 to 5. 8.A computer readable storage medium storing computer executable instructions, which, when executed by a processor, implement the steps of the embedded log analysis method of any one of claims 1 to 5.

Images