CN116405091B - Method and device for analyzing telemetry data, electronic equipment and storage medium - Google Patents
Method and device for analyzing telemetry data, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116405091B CN116405091B CN202310376457.1A CN202310376457A CN116405091B CN 116405091 B CN116405091 B CN 116405091B CN 202310376457 A CN202310376457 A CN 202310376457A CN 116405091 B CN116405091 B CN 116405091B
- Authority
- CN
- China
- Prior art keywords
- telemetry
- source packet
- data
- field
- current
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000004458 analytical method Methods 0.000 claims abstract description 51
- 238000013519 translation Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 3
- 238000012360 testing method Methods 0.000 abstract description 22
- 238000007405 data analysis Methods 0.000 abstract description 12
- 238000012827 research and development Methods 0.000 abstract description 11
- 238000010276 construction Methods 0.000 abstract description 7
- 238000012544 monitoring process Methods 0.000 description 15
- 238000012790 confirmation Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000007667 floating Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000011160 research Methods 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000018109 developmental process Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000001627 detrimental effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007935 neutral effect Effects 0.000 description 1
- 230000001915 proofreading effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/1851—Systems using a satellite or space-based relay
- H04B7/18519—Operations control, administration or maintenance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- Astronomy & Astrophysics (AREA)
- Aviation & Aerospace Engineering (AREA)
- General Physics & Mathematics (AREA)
- Selective Calling Equipment (AREA)
Abstract
The application discloses a telemetry data analysis method, a telemetry data analysis device, electronic equipment and a storage medium; the method comprises the following steps: receiving an analysis command sent by control equipment; responding to the analysis command to obtain data to be analyzed; the data to be analyzed comprises: a file to be parsed or a data stream to be parsed; generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed; and analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet. According to the method and the device for analyzing the telemetry data, the telemetry data can be rapidly analyzed, so that the heavy research and development work of telemetry format comparison, coding, testing and the like can be reduced, and the ground construction work of commercial satellites can be rapidly dealt with.
Description
Technical Field
The embodiment of the application relates to the technical field of aerospace, in particular to a telemetry data analysis method, a telemetry data analysis device, electronic equipment and a storage medium.
Background
Telemetry data of satellites is of great importance for monitoring, analyzing the operating conditions of satellites and loads. With the construction of large-scale constellations, long-term telemetry data storage and querying of multiple satellites poses a serious challenge to commercial satellite companies.
With the continuous development of satellite technology, the autonomous capability of satellite sources is continuously enhanced, and the data occurrence rate and the packet length of generated data packets are also continuously changed. In particular, the recent development of commercial satellites requires rapid iterations of satellite platforms and equipment to preempt the market, with greatly shortened cycles from satellite design, load installation styling, to interface file release, and to ground system development. This requires that ground system developers be able to quickly develop reliable test and control systems, particularly telemetry and remote control modules, based on satellite-to-ground interface files, severely affected by the interfaces of satellites and on-board equipment.
By adopting the traditional coding mode, each time the interface file is released, a great deal of effort is consumed by research personnel to confirm, compare, code and test various telemetry parameters. Even if the interface files released each time are only slightly different, for safety, research and development personnel are required to carry out regression test, and the interface files can be used after strict test and joint debugging confirmation with other ground test software are carried out. This is more obvious for commercial satellites with short development cycle, file standardization, and lack of rigor, and repeated proofreading of the code.
Disclosure of Invention
The application provides a telemetry data analysis method, a telemetry data analysis device, an electronic device and a storage medium, which can rapidly analyze telemetry data, thereby reducing heavy research and development work such as telemetry format comparison, coding, testing and the like and rapidly coping with ground construction work of commercial satellites.
In a first aspect, an embodiment of the present application provides a method for parsing telemetry data, the method including:
receiving an analysis command sent by control equipment;
responding to the analysis command to acquire data to be analyzed; wherein, the data to be parsed comprises: a file to be parsed or a data stream to be parsed;
generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed;
and analyzing each telemetry source packet in the data to be analyzed by using the total source packet analyzer to obtain an analysis result of each telemetry source packet.
In a second aspect, embodiments of the present application further provide a device for parsing telemetry data, where the device includes: the device comprises a receiving module, an acquisition module, a generation module and an analysis module; wherein,
the receiving module is used for receiving the analysis command sent by the control equipment;
the acquisition module is used for responding to the analysis command to acquire data to be analyzed; wherein, the data to be parsed comprises: a file to be parsed or a data stream to be parsed;
the generation module is used for generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed;
and the analysis module is used for analyzing each telemetry source packet in the data to be analyzed by using the total source packet analyzer to obtain analysis results of each telemetry source packet.
In a third aspect, an embodiment of the present application provides an electronic device, including:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the telemetry data resolution method described in any of the embodiments of the present application.
In a fourth aspect, embodiments of the present application provide a storage medium having stored thereon a computer program which, when executed by a processor, implements a method of telemetry data resolution as described in any of the embodiments of the present application.
The embodiment of the application provides a method, a device, electronic equipment and a storage medium for analyzing telemetry data, which are used for receiving an analysis command sent by control equipment; then, responding to the analysis command to obtain data to be analyzed; generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed; and finally, analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet. That is, in the technical solution of the present application, a total source packet parser corresponding to data to be parsed may be quickly generated, and then each telemetry source packet in the data to be parsed is parsed by using the total source packet parser. Because the parsing mode used by the total source packet parser is unified, the parsing result can be used as a shared basis for links such as telemetry format editing, telemetry monitoring and the like. In the prior art, each time an interface file is released, a great deal of effort is spent on the confirmation, comparison, encoding and testing of various telemetry parameters by a developer. Even if the interface files released each time are only slightly different, for safety, research and development personnel are required to carry out regression test, and the interface files can be used after strict test and joint debugging confirmation with other ground test software are carried out. Therefore, compared with the prior art, the method, the device, the electronic equipment and the storage medium for analyzing the telemetry data can quickly analyze the telemetry data, so that the heavy research and development work of telemetry format comparison, coding, testing and the like can be lightened, and the ground construction work of a commercial satellite can be quickly dealt with; in addition, the technical scheme of the embodiment of the application is simple and convenient to realize, convenient to popularize and wider in application range.
Drawings
FIG. 1 is a first flow chart of a method for analyzing telemetry data according to an embodiment of the present disclosure;
FIG. 2 is a second flow chart of a method for parsing telemetry data according to an embodiment of the present disclosure;
FIG. 3 is a third flow chart of a method for analyzing telemetry data according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a telemetry data analysis device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present application are shown in the drawings.
Example 1
Fig. 1 is a schematic flow chart of a first procedure of a telemetry data parsing method provided in an embodiment of the present application, where the method may be performed by a telemetry data parsing apparatus or electronic device, and the apparatus or electronic device may be implemented in software and/or hardware, and the apparatus or electronic device may be integrated into any intelligent device with a network communication function. As shown in fig. 1, the method for parsing telemetry data may include the steps of:
s101, receiving an analysis command sent by the control equipment.
In this step, the electronic device may receive the parsing instruction sent by the control device. The control device in the embodiment of the application may be a client device or a server device.
S102, responding to an analysis command to acquire data to be analyzed; the data to be analyzed comprises: a file to be parsed or a data stream to be parsed.
In this step, the electronic device may acquire data to be parsed in response to the parse command; the data to be analyzed comprises: a file to be parsed or a data stream to be parsed. That is, the data to be parsed in the embodiment of the present application may be a file to be parsed or a data stream to be parsed.
S103, generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed.
In this step, the electronic device may generate a total source packet parser corresponding to the data to be parsed based on the data to be parsed. Specifically, if at least one telemetry source packet exists in the data to be analyzed, the electronic device may first extract one telemetry source packet from the data to be analyzed as a current telemetry source packet; then generating a single source packet analyzer corresponding to the current telemetry source packet based on the current telemetry source packet; repeatedly executing the operations until a single source packet analyzer corresponding to each telemetry source packet is generated; and generating a total source packet analyzer corresponding to the data to be analyzed based on the single source packet analyzer corresponding to each telemetry source packet.
S104, analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet.
In this step, the electronic device may parse each telemetry source packet in the data to be parsed by using the total source packet parser to obtain a parsing result of each telemetry source packet. Specifically, if at least one telemetry source packet exists in the data to be analyzed, the electronic device may extract one telemetry source packet from the data to be analyzed as a current telemetry source packet; then analyzing the current telemetry source package by using a pre-generated total source package analyzer to obtain an analysis result of the current telemetry source package; and repeatedly executing the operation until the analysis result of each telemetry source packet in the telemetry data stream is obtained.
According to the method for analyzing the telemetry data, an analysis command sent by control equipment is received; then, responding to the analysis command to obtain data to be analyzed; generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed; and finally, analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet. That is, in the technical solution of the present application, a total source packet parser corresponding to data to be parsed may be quickly generated, and then each telemetry source packet in the data to be parsed is parsed by using the total source packet parser. Because the parsing mode used by the total source packet parser is unified, the parsing result can be used as a shared basis for links such as telemetry format editing, telemetry monitoring and the like. In the prior art, each time an interface file is released, a great deal of effort is spent on the confirmation, comparison, encoding and testing of various telemetry parameters by a developer. Even if the interface files released each time are only slightly different, for safety, research and development personnel are required to carry out regression test, and the interface files can be used after strict test and joint debugging confirmation with other ground test software are carried out. Therefore, compared with the prior art, the telemetry data analysis method provided by the embodiment of the application can be used for rapidly analyzing the telemetry data, so that the heavy research and development work of telemetry format comparison, coding, testing and the like can be reduced, and the ground construction work of commercial satellites can be rapidly responded; in addition, the technical scheme of the embodiment of the application is simple and convenient to realize, convenient to popularize and wider in application range.
Example two
Fig. 2 is a second flow chart of a method for analyzing telemetry data according to an embodiment of the present application. Further optimization and expansion based on the above technical solution can be combined with the above various alternative embodiments.
As shown in fig. 2, the method for parsing telemetry data may include the steps of:
s201, receiving an analysis command sent by the control equipment.
S202, responding to an analysis command to acquire data to be analyzed; the data to be analyzed comprises: a file to be parsed or a data stream to be parsed.
S203, if at least one telemetry source packet exists in the data to be analyzed, extracting one telemetry source packet from the data to be analyzed as a current telemetry source packet.
In this step, if at least one telemetry source packet exists in the data to be parsed, the electronic device may extract one telemetry source packet from the data to be parsed as the current telemetry source packet. Specifically, the electronic device may extract the current telemetry source packet from the file to be parsed, or may extract the current telemetry source packet from the data stream to be parsed.
S204, generating a single source packet analyzer corresponding to the current telemetry source packet based on the current telemetry source packet; and repeatedly executing the operation until a single source packet parser corresponding to each telemetry source packet is generated.
In this step, the electronic device may generate a single source packet parser corresponding to the current telemetry source packet based on the current telemetry source packet; and repeatedly executing the operation until a single source packet parser corresponding to each telemetry source packet is generated. Specifically, if at least one telemetry field exists in the current telemetry source packet, the electronic device may first extract one telemetry field from the current telemetry source packet as the current telemetry field; then generating a field parser corresponding to the current telemetry field based on the current telemetry field; repeatedly executing the operations until a field analyzer corresponding to each telemetry field is generated; and generating a single source packet parser corresponding to the current telemetry source packet based on the field parsers corresponding to the telemetry fields.
Preferably, before generating the field parser corresponding to the current telemetry field based on the current telemetry field, it may also be determined whether the current telemetry field is a reserved field; if the current telemetry field is not a reserved field, the electronic device may perform an operation of generating a field parser corresponding to the current telemetry field based on the current telemetry field; if the current telemetry field is a reserved field, the electronic device may repeat the above operations with a next field of the current telemetry field as the current telemetry field until the current telemetry field is not the reserved field.
S205, generating a total source packet parser corresponding to data to be parsed based on the single source packet parser corresponding to each telemetry source packet.
In this step, the electronic device may generate a total source packet parser corresponding to the data to be parsed based on the single source packet parser corresponding to each telemetry source packet. Specifically, the electronic device may combine the single source packet resolvers corresponding to all telemetry source packets together to obtain a total source packet resolvers corresponding to the data to be resolved.
S206, analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet.
According to the method for analyzing the telemetry data, an analysis command sent by control equipment is received; then, responding to the analysis command to obtain data to be analyzed; generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed; and finally, analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet. That is, in the technical solution of the present application, a total source packet parser corresponding to data to be parsed may be quickly generated, and then each telemetry source packet in the data to be parsed is parsed by using the total source packet parser. Because the parsing mode used by the total source packet parser is unified, the parsing result can be used as a shared basis for links such as telemetry format editing, telemetry monitoring and the like. In the prior art, each time an interface file is released, a great deal of effort is spent on the confirmation, comparison, encoding and testing of various telemetry parameters by a developer. Even if the interface files released each time are only slightly different, for safety, research and development personnel are required to carry out regression test, and the interface files can be used after strict test and joint debugging confirmation with other ground test software are carried out. Therefore, compared with the prior art, the telemetry data analysis method provided by the embodiment of the application can be used for rapidly analyzing the telemetry data, so that the heavy research and development work of telemetry format comparison, coding, testing and the like can be reduced, and the ground construction work of commercial satellites can be rapidly responded; in addition, the technical scheme of the embodiment of the application is simple and convenient to realize, convenient to popularize and wider in application range.
Example III
Fig. 3 is a third flow chart of a method for analyzing telemetry data according to an embodiment of the present disclosure. Further optimization and expansion based on the above technical solution can be combined with the above various alternative embodiments.
As shown in fig. 3, the method for parsing telemetry data may include the steps of:
s301, receiving an analysis command sent by the control equipment.
S302, responding to an analysis command to acquire data to be analyzed; the data to be analyzed comprises: a file to be parsed or a data stream to be parsed.
S303, if at least one telemetry source packet exists in the data to be analyzed, extracting one telemetry source packet from the data to be analyzed as a current telemetry source packet.
S304, generating a field parser corresponding to the current telemetry field based on the current telemetry field; and repeatedly executing the operations until the field resolvers corresponding to the telemetry fields are generated.
In this step, the electronic device may generate a field parser corresponding to the current telemetry field based on the current telemetry field; and repeatedly executing the operations until the field resolvers corresponding to the telemetry fields are generated. Specifically, the electronic device may firstly translate the current telemetry field in at least one dimension using a predefined telemetry format description language, to obtain a translation result of the current telemetry field in each dimension; wherein at least one dimension includes, but is not limited to: type, size end definition, formula, and enumeration; and then generating a field parser corresponding to the current telemetry field according to the translation result of the current telemetry field in each dimension.
In the embodiment of the application, a telemetry format description language (Telemetry Format Description Language, abbreviated as TFDL) is in a key position, and formally defines a telemetry format of a satellite and a display method thereof, so that the telemetry format of the satellite can be identified and processed by a plurality of modules. The basic components of this language are descriptions of telemetry parameters:
for example, parameter formats for magnetometer states:
for another example, parameter format for temperature telemetry:
in the above example, the magnetometer state is represented by 2 bits (b 2), and if the bits are 00, 01, 10, 11, they represent "normal power down", "power down fault", "normal dotted" and "dotted fault", respectively. This is both an explanation of telemetry and a requirement for telemetry monitoring interfaces. The telemetry monitoring interface may display this status in a polyline and display the 4 specific meanings in text form at the polyline.
Temperature telemetry is expressed in 1 unsigned integer (u 1) and requires conversion according to the formula "y= ((x×1000×4)/255-500)/10". Typically, the above-described type of formula may be calibrated in a laboratory at the surface, and may be repeatedly modified prior to satellite acquisition, in degrees celsius. This need is displayed in the form of a number axis label at the telemetry monitoring interface. In addition, there are other descriptions. For example, a parameter expressed in a plurality of bytes, its byte transmission order, and some parameters for CRC check and the like.
After receiving the updated satellite-ground interface file, ground research personnel edit or update the telemetry format of the satellite by using a UI interface according to the telemetry format and display requirements using text description, generally edit or update the telemetry format of the satellite by using a web page, and convert the telemetry format into a TFDL language format when the telemetry format is stored.
In order to speed up the one-time import of satellite telemetry format and the need for transmission between different systems, a mutual conversion between TFDL language format and Excel's form situational definition can be provided, which can improve efficiency and facilitate replication and transmission. The TFDL can record editors, modification time, versions and corresponding satellite-to-ground file names in the file together, so that standardized management of a telemetry format is realized, and errors are not easy to occur. And loading the active TFDL of the corresponding satellite when the telemetry data is analyzed, generating a telemetry analyzer, and analyzing the telemetry data by using the telemetry analyzer. Therefore, hard coding of telemetry analysis is avoided, the workload of ground research personnel is greatly reduced, and meanwhile, the reliability is improved. The active TFDL referred to herein refers to the currently active format description. Because there may be multiple versions of the format description for a satellite, only the active TFDL will be fetched and a parser generated. The time spent for generating the parser is very short and is generally less than 0.1 seconds, so that the telemetry data are regenerated each time, which means that all the editing of the telemetry format is effective immediately, thus greatly increasing the efficiency of ground research personnel, and the efficiency is updated immediately as long as errors of the telemetry format are found, and omitting the lengthy processes of editing the parsing code, compiling and deploying.
S305, generating a single source packet parser corresponding to the current telemetry source packet based on the field parsers corresponding to the telemetry fields; and repeatedly executing the operation until a single source packet parser corresponding to each telemetry source packet is generated.
S306, generating a total source packet parser corresponding to the data to be parsed based on the single source packet parser corresponding to each telemetry source packet.
S307, analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet.
In a specific embodiment of the present application, a method of generating a total source package parser may include the following operational steps: 1) The telemetry source package description file is loaded and parsed. Typically the primary content of this file is the TFDL description, which is stored in a database or file system and searched via satellite codes and telemetry regimes. 2) Each telemetry source package in the file is fetched. 3) One telemetry field (or telemetry parameter) in the telemetry source packet is taken, and the source packet read-write pointer is set to zero. 4) If it is a reserved field, this field is ignored and the process jumps to step 3), the reserved field being a reserved field for future expansion of the telemetry format, or some field that is detrimental to output to the monitoring interface. These fields do not output, but because of the occupied position, the source packet read-write pointer needs to be modified by the length of the reserved field. 5) The type and size end definitions in TFDL of the telemetry field are translated. Types are generally classified into: integer type, floating point type, and bit type. The integer types are again divided into: signed and unsigned, the two values are different. The floating point type conforms to the IEEE754 standard, defines a specific representation of the sign, exponent and mantissa of a binary floating point number, and is commonly used in single precision and double precision standards. And the bit type is a binary sequence defined by a number of non-8 times the bit length. The size end definition is also used to indicate the order of transmission of the plurality of bytes, in the case of integer types and floating point types. This part is an important part of the process of generating the total source packet parser, which relates to how a segment of the binary stream is truncated from the telemetry data stream, and how the data stream is rearranged after the truncation. In a specific implementation, a language capable of bit manipulation is required, such as nodejs, golang, etc. 6) The formula in TFDL of the telemetry field, such as the formula field in the temperature telemetry parameters in the example, is translated. The source of the equation is mostly that the telemetry parameter is a continuous physical quantity, and a true value representing the telemetry physical quantity within the allowable range is generated by the sensor and analog-to-digital conversion. This formula is a computer representation of the transformation relationship with the actual physical quantity. When a formula is given, it is generally accompanied by a representation of the unit. When generating the total source package parser, the formulas of the text representation need to be converted into a piece of code. Since this code needs to be generated according to text, it can be done using the dynamic language characteristics, such as eval or new Function of nodejs, golang, java, also has its own dynamic language characteristics. The accompanying units are output together to the TFDL for telemetry monitoring. 7) Enumeration in TFDL of telemetry fields is translated. Such as the select field in the magnetometer state parameters in the example. The source of enumeration mostly indicates that the telemetry parameter is a status value of the device. Typically an unsigned integer or bit type. Some enumerations are represented by a range, if greater than 10 is less than 50 indicates normal, greater than 50 is less than 80 indicates timeout, etc. When generating the total source package parser, it is necessary to convert the enumeration into a series of if else judgment statements, or a function in a table look-up manner. 8) Special parameters such as CRC check, second technique and the like are also required to be processed. After completion, a field parser is generated. 9) If the telemetry source packet also has a field, then go to step 3), otherwise continue. 10 Here, parsing functions have been generated for all fields, and all parsing functions are organized together to generate a single source package parser. 11 A single source packet parser is placed into the total source packet parser based on the identity of the source packet. 12 If there are more active packets, go to step 2), otherwise continue. 13 Outputting the total source packet parser.
In a specific embodiment of the present application, a method for parsing each telemetry source packet in data to be parsed includes the following operation steps: 1) Analyzing a command line; 2) And reading the data stream from the file or directly, and completing the function of extracting the complete source packet from the data stream. 3) And (3) putting the analyzed result into a file, a database or a telemetry message queue, and driving the display of telemetry data. The purpose of using telemetry message queues is to smooth out data flow rates, making telemetry monitoring smooth. 4) Invoking the above process generates a source package total parser. 5) And circularly reading the complete source packet and sending the source packet to a source packet total parser. 6) And outputting statistical information after completion.
In a specific embodiment of the present application, a method for monitoring each telemetry source package in data to be parsed includes the following operation steps: 1) TFDL definitions for supported satellites are loaded. 2) Listening to the telemetry message queue. 3) If telemetry is received for a particular satellite, the telemetry message is displayed according to the TFDL definition.
The present application formally describes telemetry formats via a "neutral" telemetry format description language TFDL, which is a common basis for implementing telemetry format editing, telemetry data parsing, and telemetry monitoring. The present application also provides a method of generating a telemetry source package summary parser from a telemetry format description language TFDL. The method mainly comprises the steps of sequentially translating type and size end definitions, formulas and enumeration. The method and the device can simultaneously consider analysis and display of the telemetering physical quantity, the telemetering state quantity and the like. The telemetry parser is dynamically generated based on the TFDL and the display of telemetry monitor pages is also dynamically generated based on the TFDL. This enables modifications to the telemetry format to immediately validate the parsing and monitoring process. Of course, this cannot affect the analysis results that have been put in storage. If this is due to parameter entry errors rather than parameter modification, the binned resolution results need to be invalidated and binned again. TFDL provided herein based on this description language acts on telemetry parsing and telemetry monitoring simultaneously. The method can be expanded to save rules of telemetry analysis and telemetry storage of different telemetry parameters in the future. And takes effect immediately, hard code telemetry analysis and code display are avoided, and efficiency is greatly improved.
According to the method for analyzing the telemetry data, an analysis command sent by control equipment is received; then, responding to the analysis command to obtain data to be analyzed; generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed; and finally, analyzing each telemetry source packet in the data to be analyzed by using a total source packet analyzer to obtain analysis results of each telemetry source packet. That is, in the technical solution of the present application, a total source packet parser corresponding to data to be parsed may be quickly generated, and then each telemetry source packet in the data to be parsed is parsed by using the total source packet parser. Because the parsing mode used by the total source packet parser is unified, the parsing result can be used as a shared basis for links such as telemetry format editing, telemetry monitoring and the like. In the prior art, each time an interface file is released, a great deal of effort is spent on the confirmation, comparison, encoding and testing of various telemetry parameters by a developer. Even if the interface files released each time are only slightly different, for safety, research and development personnel are required to carry out regression test, and the interface files can be used after strict test and joint debugging confirmation with other ground test software are carried out. Therefore, compared with the prior art, the telemetry data analysis method provided by the embodiment of the application can be used for rapidly analyzing the telemetry data, so that the heavy research and development work of telemetry format comparison, coding, testing and the like can be reduced, and the ground construction work of commercial satellites can be rapidly responded; in addition, the technical scheme of the embodiment of the application is simple and convenient to realize, convenient to popularize and wider in application range.
Example IV
Fig. 4 is a schematic structural diagram of a telemetry data analysis device according to an embodiment of the present application. As shown in fig. 4, the telemetry data analyzing device includes: a receiving module 401, an acquiring module 402, a generating module 403 and an analyzing module 404; wherein,
the receiving module 401 is configured to receive an analysis command sent by the control device;
the acquiring module 402 is configured to acquire data to be parsed in response to the parsing command; wherein, the data to be parsed comprises: a file to be parsed or a data stream to be parsed;
the generating module 403 is configured to generate a total source packet parser corresponding to the data to be parsed based on the data to be parsed;
the parsing module 404 is configured to parse each telemetry source packet in the data to be parsed by using the total source packet parser, so as to obtain a parsing result of each telemetry source packet.
The remote measurement data analysis device can execute the method provided by any embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. Technical details not described in detail in this embodiment may be found in the method for parsing telemetry data provided in any embodiment of the present application.
Example five
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Fig. 5 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present application. The electronic device 12 shown in fig. 5 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present application.
As shown in fig. 5, the electronic device 12 is in the form of a general purpose computing device. Components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.
Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Electronic device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 5, commonly referred to as a "hard disk drive"). Although not shown in fig. 5, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments of the present application.
A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods in the embodiments described herein.
The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the electronic device 12, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 over the bus 18. It should be appreciated that although not shown in fig. 5, other hardware and/or software modules may be used in connection with electronic device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing, such as implementing the telemetry data parsing method provided by embodiments of the present application, by running programs stored in the system memory 28.
Example six
Embodiments of the present application provide a computer storage medium.
Any combination of one or more computer readable media may be employed in the computer readable storage media of the embodiments herein. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
Note that the above is only a preferred embodiment of the present application and the technical principle applied. Those skilled in the art will appreciate that the present application is not limited to the particular embodiments described herein, but is capable of numerous obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the present application. Therefore, while the present application has been described in connection with the above embodiments, the present application is not limited to the above embodiments, but may include many other equivalent embodiments without departing from the spirit of the present application, the scope of which is defined by the scope of the appended claims.
Claims (9)
1. A method of parsing telemetry data, the method comprising:
receiving an analysis command sent by control equipment;
responding to the analysis command to acquire data to be analyzed; wherein, the data to be parsed comprises: a file to be parsed or a data stream to be parsed;
generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed;
analyzing each telemetry source packet in the data to be analyzed by using the total source packet analyzer to obtain analysis results of each telemetry source packet;
the generating the total source packet parser corresponding to the data to be parsed based on the data to be parsed includes:
if at least one telemetry source packet exists in the data to be analyzed, extracting one telemetry source packet from the data to be analyzed as a current telemetry source packet;
generating a single source packet parser corresponding to the current telemetry source packet based on the current telemetry source packet; repeatedly extracting a telemetry source packet from the data to be analyzed as a current telemetry source packet, and generating a single source packet analyzer corresponding to the current telemetry source packet based on the current telemetry source packet until generating a single source packet analyzer corresponding to each telemetry source packet;
and generating a total source packet analyzer corresponding to the data to be analyzed based on the single source packet analyzer corresponding to each telemetry source packet.
2. The method of claim 1, wherein generating a single source packet parser corresponding to the current telemetry source packet based on the current telemetry source packet comprises:
if at least one telemetry field exists in the current telemetry source packet, extracting one telemetry field from the current telemetry source packet as a current telemetry field;
generating a field parser corresponding to the current telemetry field based on the current telemetry field; repeating the operation of extracting a telemetry field from the current telemetry source packet as the current telemetry field if at least one telemetry field exists in the current telemetry source packet until a field parser corresponding to each telemetry field is generated;
and generating a single source packet parser corresponding to the current telemetry source packet based on the field parsers corresponding to the telemetry fields.
3. The method of claim 2, wherein prior to generating a field parser corresponding to the current telemetry field based on the current telemetry field, the method further comprises:
judging whether the current telemetry field is a reserved field or not; if the current telemetry field is not a reserved field, executing an operation of generating a field parser corresponding to the current telemetry field based on the current telemetry field; and if the current telemetry field is a reserved field, taking the next field of the current telemetry field as the current telemetry field, and repeatedly executing the operation until the current telemetry field is not the reserved field.
4. The method of claim 2, wherein generating a field parser corresponding to the current telemetry field based on the current telemetry field comprises:
translating the current telemetry field in at least one dimension by using a predefined telemetry format description language to obtain translation results of the current telemetry field in each dimension; wherein the at least one dimension includes, but is not limited to: type, size end definition, formula, and enumeration;
and generating a field parser corresponding to the current telemetry field according to the translation result of the current telemetry field in each dimension.
5. The method of claim 4, wherein translating the current telemetry field in at least one dimension using a predefined telemetry format description language results in translation of the current telemetry field in each dimension, comprising:
extracting in the current telemetry field a base component of at least one original representation of the current telemetry field in each dimension;
translating the base components of each original representation into base components of a telemetry description language representation using the predefined telemetry format description language;
the basic components of all telemetry description language representations are combined into a translation of the current telemetry field in each dimension.
6. The method of claim 1, wherein parsing each telemetry source packet in the data to be parsed using the aggregate source packet parser to obtain a parsing result for each telemetry source packet comprises:
if at least one telemetry source packet exists in the data to be analyzed, extracting one telemetry source packet from the data to be analyzed as a current telemetry source packet;
analyzing the current telemetry source package by using a pre-generated total source package analyzer to obtain an analysis result of the current telemetry source package; repeatedly extracting a telemetry source packet from the data to be analyzed as a current telemetry source packet, and analyzing the current telemetry source packet by using a pre-generated total source packet analyzer to obtain an analysis result of the current telemetry source packet until the analysis result of each telemetry source packet in the telemetry data stream is obtained.
7. A telemetry data resolution apparatus, the apparatus comprising: the device comprises a receiving module, an acquisition module, a generation module and an analysis module; wherein,
the receiving module is used for receiving the analysis command sent by the control equipment;
the acquisition module is used for responding to the analysis command to acquire data to be analyzed; wherein, the data to be parsed comprises: a file to be parsed or a data stream to be parsed;
the generation module is used for generating a total source packet analyzer corresponding to the data to be analyzed based on the data to be analyzed;
the analysis module is used for analyzing each telemetry source packet in the data to be analyzed by using the total source packet analyzer to obtain analysis results of each telemetry source packet;
the generating module is specifically configured to extract a telemetry source packet from the data to be parsed as a current telemetry source packet if at least one telemetry source packet exists in the data to be parsed;
generating a single source packet parser corresponding to the current telemetry source packet based on the current telemetry source packet; repeatedly extracting a telemetry source packet from the data to be analyzed as a current telemetry source packet, and generating a single source packet analyzer corresponding to the current telemetry source packet based on the current telemetry source packet until generating a single source packet analyzer corresponding to each telemetry source packet;
and generating a total source packet analyzer corresponding to the data to be analyzed based on the single source packet analyzer corresponding to each telemetry source packet.
8. An electronic device, comprising:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of resolution of telemetry data as claimed in any one of claims 1 to 6.
9. A storage medium having stored thereon a computer program which, when executed by a processor, implements a method of interpretation of telemetry data as claimed in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310376457.1A CN116405091B (en) | 2023-04-10 | 2023-04-10 | Method and device for analyzing telemetry data, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310376457.1A CN116405091B (en) | 2023-04-10 | 2023-04-10 | Method and device for analyzing telemetry data, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116405091A CN116405091A (en) | 2023-07-07 |
| CN116405091B true CN116405091B (en) | 2023-12-19 |
Family
ID=87013831
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310376457.1A Active CN116405091B (en) | 2023-04-10 | 2023-04-10 | Method and device for analyzing telemetry data, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116405091B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116756217B (en) * | 2023-08-16 | 2023-12-12 | 航天科工火箭技术有限公司 | One-key telemetry data real-time processing and interpretation method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106201643A (en) * | 2016-07-14 | 2016-12-07 | 北京邮电大学 | Data analysis method and device |
| CN111224839A (en) * | 2019-12-26 | 2020-06-02 | 长沙星融元数据技术有限公司 | Verification method and device for in-band network remote control function, storage medium and electronic equipment |
| CN113495730A (en) * | 2020-03-20 | 2021-10-12 | 北京沃东天骏信息技术有限公司 | Resource package generation and analysis method and device |
| CN115544304A (en) * | 2022-10-12 | 2022-12-30 | 东软睿驰汽车技术(大连)有限公司 | File analysis method and device, readable storage medium and file analysis equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7974744B2 (en) * | 2008-04-30 | 2011-07-05 | The United States Of America As Represented By The Secretary Of The Navy | Multiple telemetry stream parsing and reconstruction system |
| US11720434B2 (en) * | 2021-01-25 | 2023-08-08 | Dell Products L.P. | Data collection agent trained for telemetry data collection |
-
2023
- 2023-04-10 CN CN202310376457.1A patent/CN116405091B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106201643A (en) * | 2016-07-14 | 2016-12-07 | 北京邮电大学 | Data analysis method and device |
| CN111224839A (en) * | 2019-12-26 | 2020-06-02 | 长沙星融元数据技术有限公司 | Verification method and device for in-band network remote control function, storage medium and electronic equipment |
| CN113495730A (en) * | 2020-03-20 | 2021-10-12 | 北京沃东天骏信息技术有限公司 | Resource package generation and analysis method and device |
| CN115544304A (en) * | 2022-10-12 | 2022-12-30 | 东软睿驰汽车技术(大连)有限公司 | File analysis method and device, readable storage medium and file analysis equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116405091A (en) | 2023-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR20180122019A (en) | Tools and methods for real-time data flow programming languages | |
| CN110191021B (en) | Protocol testing method and device, electronic equipment and storage medium | |
| CN116405091B (en) | Method and device for analyzing telemetry data, electronic equipment and storage medium | |
| CN113158101B (en) | Visual page rendering method, device, equipment and storage medium | |
| CN110769002A (en) | LabVIEW-based message analysis method, system, electronic device and medium | |
| US8930888B2 (en) | Modelling serialized object streams | |
| US8930923B2 (en) | Generating debugging extension source code utilizing debugging information | |
| US8914482B2 (en) | Translation of technology-agnostic management commands into multiple management protocols | |
| CN113778449A (en) | Avionics interface data adaptation conversion system | |
| US20170131980A1 (en) | Model driven architecture for network management and configuration | |
| CN113238739A (en) | Plug-in development and data acquisition method, device, electronic equipment and medium | |
| CN112286784A (en) | Test case generation method and device, server and storage medium | |
| CN111399901B (en) | State enumeration class generation method, device, server and storage medium | |
| CN115840559A (en) | Dynamically configured heterogeneous interface data conversion method, device, equipment and medium | |
| US11797277B2 (en) | Neural network model conversion method server, and storage medium | |
| CN113138767B (en) | Code language conversion method, device, electronic equipment and storage medium | |
| CN112698825B (en) | Programming building block conversion method, device, processing equipment and storage medium | |
| CN111367791B (en) | Method, device, medium and electronic equipment for generating test case | |
| CN114647568A (en) | Automatic testing method and device, electronic equipment and readable storage medium | |
| CN110737431A (en) | Software development method, development platform, terminal device and storage medium | |
| CN113742225B (en) | Test data generation method, device, equipment and storage medium | |
| CN113792531B (en) | Text editing method and system based on markdown grammar expansion | |
| CN113032003B (en) | Development file export method, development file export device, electronic equipment and computer storage medium | |
| CN117270876A (en) | Code conversion method, device, electronic equipment and storage medium | |
| CN116383317A (en) | Remote measurement data storage method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |