Telemetry control system and telemetry communication system

Abstract

The application provides a telemetry control system and a telemetry communication system, and relates to the technical field of telemetry. The telemetry control system comprises an application layer and a data management layer. The application layer collects telemetry data and outputs the telemetry data to the data management layer. The data management layer is configured to store the telemetry data as first type data in an operating memory area in a coverage storage mode when detecting that a recording switch interface is closed; and store received telemetry data as second type data in the operating memory area when detecting that the recording switch interface is opened. The data management layer is further configured to store the first type data and the second type data as sentinel data in a storage memory area, so as to facilitate subsequent distribution of the sentinel data to ground equipment. On the one hand, telemetry data before and after the occurrence of a fault or a key event is recorded, and more comprehensive telemetry recording is achieved. On the other hand, telemetry data before the occurrence of a fault or a key event is stored in a coverage mode, which can reduce the occupation of storage space.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of telemetry, and in particular to a telemetry control system and a telemetry communication system. BACKGROUND

[0002] During the operation of space equipment (such as satellites, spacecraft, etc.), it is easy to fail due to the influence of the harsh space environment. After the failure occurs, telemetry data needs to be issued for fault analysis and disposal. Taking a satellite as an example, the current satellite telemetry data usually adopts two modes of detailed recording and sampling recording. For detailed recording, about 10KB of data is generated per second, and about 0.8GB of data is generated per day. When the data is downloaded, a dedicated high-speed channel is usually required, and a large amount of storage space is also required on the ground. A large amount of telemetry data is invalid data. For sampling storage, sampling is performed at a fixed interval for each telemetry packet, such as 4 seconds / time, 16 seconds / time, and 512 seconds / time. The data is sparse, and there is often no telemetry data at the time of failure, which increases the difficulty of troubleshooting. There is also a technical solution that records some key telemetry after a failure occurs, but the telemetry data is usually the fault detected after the failure, which may have been a period of time since the failure occurred, and the recorded telemetry may not be comprehensive and is not conducive to troubleshooting. SUMMARY

[0003] Therefore, the present application provides a telemetry control system and a telemetry communication system, which can record telemetry data before and after a failure or a key event under the condition of acceptable storage space occupation.

[0004] In a first aspect, the present application provides a telemetry control system, which comprises an application layer and a data management layer. The application layer comprises a telemetry remote control module, a collection module, and a fault event detection module. A recording switch interface is arranged between the data management layer and the application layer. When the fault event detection module detects a failure or a key event, the recording switch interface is opened. The data management layer comprises a running memory area and a storage memory area, wherein:

[0005] The application layer is configured to collect telemetry data through the collection module and output the telemetry data to the data management layer.

[0006] The data management layer is configured to store the telemetry data as first type data in the running memory area through an overlay storage mode when detecting that the recording switch interface is closed, and store the received telemetry data as second type data in the running memory area when detecting that the recording switch interface is opened.

[0007] The data management layer is further configured to acquire the first type data and the second type data, and store the first type data and the second type data as sentinel data in the storage memory area.

[0008] The telemetry remote control module is configured to send the sentinel data to the ground equipment.

[0009] In an embodiment, the running memory area includes a first storage area configured to store the first type of data, and a second storage area configured to store the second type of data. After the data management layer acquires the first type of data and the second type of data, the data management layer is further configured to add a sentinel tag to each data packet in the first type of data and the second type of data, and store the first type of data and the second type of data with the added sentinel tag as sentinel data in the storage memory area.

[0010] In an embodiment, the recording switch interface is opened when the telemetry remote control module receives a recording trigger instruction from the ground equipment.

[0011] In an embodiment, the running memory area includes a de-framing buffer and a sending buffer. The data management layer is further configured to backup the sentinel data from the storage memory area to the de-framing buffer for analysis, and store the analyzed sentinel data in the sending buffer. When the telemetry remote control module performs the step of sending the sentinel data to the ground equipment, the telemetry remote control module is further configured to acquire the analyzed sentinel data from the sending buffer, and send the acquired data to the ground equipment.

[0012] In an embodiment, the telemetry control system is deployed on a space equipment. The fault includes one or more of the following: a system-level fault, a component-level fault, and a single-machine-level fault. The critical event includes one or more of the following: a satellite-rocket separation, a sailboard deployment, an antenna deployment, a load switch-on, a measurement and control entry and exit, and the like.

[0013] In an embodiment, the data management layer is further configured to trigger the step of acquiring the stored first type of data and the stored second type of data when it is detected that the second storage area configured to store the second type of data is full, or when the recording switch interface has been opened for more than a time t, and adjust the recording switch interface to be closed.

[0014] In an embodiment, the telemetry data collected by the collection module is full-scene telemetry data, including one or more of the following: equipment status, attitude parameters, and environmental status.

[0015] In a second aspect, the present application provides a telemetry communication system, including a space equipment and a ground equipment. The space equipment is deployed with the system of the first aspect. The space equipment is configured to send the sentinel data to the ground equipment after entry. The ground equipment is configured to determine an abnormal condition of the space equipment according to the sentinel data.

[0016] In an embodiment, each data packet in the sentinel data is added with a sentinel tag; the ground equipment is further configured to, after receiving the data sent by the aerospace equipment, detect whether the data includes the sentinel tag; if the sentinel tag is included, the data is stored in the sentinel data area; if the sentinel tag is not included, the data is stored in other data area.

[0017] In an embodiment, the ground equipment is further configured to acquire the sentinel data from the sentinel data area, and train a fault event detection model by using the sentinel data.

[0018] The telemetry control system provided in the present application can store the telemetry data as first type data in the running memory area by the overlay storage mode when detecting that the recording switch interface is closed, and store the received telemetry data as second type data in the running memory area when detecting that the recording switch interface is opened. The first type data and the second type data are subsequently sent to the ground equipment as sentinel data. On the one hand, the telemetry data before and after the occurrence of a fault or a key event is recorded, so that more comprehensive telemetry recording is realized; on the other hand, the telemetry data before the occurrence of a fault or a key event is stored in an overlay form, so that the occupation of the storage space can be reduced. BRIEF DESCRIPTION OF DRAWINGS

[0019] The accompanying drawings are included to provide a further understanding of the present application, and are incorporated in and constitute a part of this application, illustrate embodiments of the present application, and together with the description serve to explain the principles of the present application. In the drawings:

[0020] Figure 1 is a schematic diagram of a telemetry communication system provided by an embodiment of the present application;

[0021] Figure 2 is a schematic diagram of a telemetry control system provided by an embodiment of the present application;

[0022] Figure 3 is a structural schematic diagram of an aerospace equipment provided by an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some examples or embodiments of the present application, and for those skilled in the art, the present application can also be applied to other similar scenarios without creative labor. Unless it is obvious from the language environment or otherwise stated, the same reference numbers in the drawings represent the same structure or operation.

[0024] As used in this application, the terms "comprise", "comprising", "include", "including", "contain", "containing", "have", "having", "may" and "may have" shall be construed as non- limiting terms, and thus the interpretation "comprises at least" should be taken into account. As used in this application, the terms "one", "a", "an", and / or "the" shall not be construed as specific terms, and can include plural referents unless the context clearly dictates otherwise. In general, the terms "include", "including", "contain", and / or "containing" shall not be construed to mean an exhaustive listing of the steps and elements included in the process or device.

[0025] Also, the present application uses specific terminology in describing the embodiments of the present application. As used in this application, the terms "one embodiment", "an embodiment", and / or "some embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. The appearances of the phrase "in one or more embodiments" in various places in the specification are not necessarily all referring to the same embodiment, and the appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the application can be combined in any suitable manner.

[0026] The relative arrangement of parts and steps, numerical expressions, and numerical values set forth in the examples are not intended to limit the scope of the application unless otherwise specifically stated. Also, it is to be understood that the drawings are not necessarily drawn to scale of the actual proportions of the parts being depicted. Techniques, methods, and apparatus known to those of ordinary skill can not be discussed in detail because such techniques, methods, and apparatus are considered to be part of the base art. In all examples shown and discussed herein, any specific values are to be interpreted as merely illustrative and not as a limitation of the examples. Thus, other examples of example embodiments can have different values. It is noted that like numbers and letters on the attached drawings illustrate like parts, and therefore, once one part is defined in one drawing, it is not necessary to further discuss it in further drawings.

[0027] Furthermore, although the terms used in the present application are selected from generally known and used terms, some of the terms mentioned in the description of the present application can be created by the applicant in his or her own judgment. Accordingly, the detailed meaning of the terms can be determined by the description in the relevant part of the description of the present application. Furthermore, the application should not be limited merely to the preferred embodiments described herein, but should be given the widest scope based on the appended claims.

[0028] Flow diagrams have been used herein to illustrate the operation of apparatus or devices in accordance with embodiments of the present application. It should be understood that the operations need not necessarily be performed in the precise order shown. Rather, various steps can be handled in reverse order, or at the same time, or other operations can be added, or steps or operations removed, from these processes.

[0029] In order to better understand the telemetry control system disclosed by the embodiments of the present disclosure, the telemetry communication system to which the embodiments of the present disclosure are applicable is described first as follows.

[0030] Figure 1 is a schematic diagram of an architecture of a telemetry communication system according to the embodiments of the present disclosure. The telemetry communication system includes a space device 100 and a ground device 101, which are deployed with a telemetry control system. The space device can be a satellite or a spacecraft, and the satellite can be a high-orbit satellite, a low-orbit satellite, or a medium-orbit satellite, etc. Figure 1 Taking the space device 100 as a satellite as an example, the satellite can detect the occurrence of a fault (such as a system-level fault, a component-level fault, and a single-machine-level fault, etc.) or a key event (such as satellite-rocket separation, sailboard deployment, antenna deployment, measurement and control entry and exit, and load switching, etc.) during operation through the telemetry control system carried by itself, and collect telemetry data before and after the occurrence of the fault or the key event. When the satellite enters, the telemetry data is downloaded to the ground device 101, and the ground device 101 can determine abnormal conditions occurring in the satellite during operation based on the telemetry data.

[0031] It can be understood that the telemetry communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed by the embodiments of the present disclosure. Those skilled in the art can know that the technical solutions proposed by the embodiments of the present disclosure are also applicable to similar technical problems as the system architecture evolves and new business scenarios appear.

[0032] The following embodiments of the present disclosure can be applied to Figure 1 the telemetry communication system or part of the subjects therein, but are not limited thereto. Figure 1 The subjects shown in are examples, and the telemetry communication system can include Figure 1 all or part of the subjects in Figure 1 other subjects, the number and form of each subject is arbitrary, each subject can be an entity or a virtual entity, the connection relationship between each subject is an example, each subject can be connected or not connected, and the connection can be in any way, can be direct connection or indirect connection, can be wired connection or wireless connection.

[0033] The telemetry control system proposed by the embodiments of the present disclosure is described in detail as follows. The telemetry control system can be deployed in the space device 100 in FIG. 1, or can be deployed in a device (such as a satellite product) carried in the space device 100, which is not limited in the present application.

[0034] Figure 2 is a schematic diagram of a telemetry control system according to the embodiments of the present disclosure. As Figure 2As shown, the telemetry control system comprises an application layer 200 and a data management layer 201, the application layer 200 comprising a telemetry remote control module 2001, a collection module 2002 and a fault event detection module 2003.

[0035] A record switch interface 203 is disposed between the data management layer 201 and the application layer 200, and the record switch interface is opened when the fault event detection module 2003 detects a fault or a critical event.

[0036] In one embodiment, the above-mentioned fault comprises one or more of the following of the space device: a system-level fault, a component-level fault and a single-machine-level fault; and the critical event comprises one or more of the following of the space device: a satellite-rocket separation, a sailboard deployment, an antenna deployment, a telemetry in-out, and a load switch-off. The system-level fault is, for example, a satellite entering an attitude safety mode, an energy safety mode, etc.; the component-level fault is, for example, a solar sailboard driving structure SADA or the like rotating component actively detecting a step loss, a locked-rotor, an abnormal current, an abnormal load system, etc.; and the single-machine-level fault is, for example, a star-sensitive fault, a gyro fault, a satellite conventional single-machine detecting an abnormality, such as a heartbeat loss, an abnormal voltage and current, an invalid sensor, etc.

[0037] In one embodiment, the record switch interface 203 is in a closed state by default, and the application layer 200 controls the record switch interface to be opened when the fault event detection module 2003 detects a fault or a critical event. Alternatively, in another embodiment, when there is a record requirement on the ground, a record triggering instruction can also be sent by a ground device, and the application layer 200 controls the record switch interface to be opened when the telemetry remote control module 2001 receives the record triggering instruction from the ground device.

[0038] The data management layer 201 comprises a running memory area 2010 and a storage memory area 2011.

[0039] In one embodiment, the running memory area 2010 described above generally stores a small space, which can be SRAM (Static Random Access Memory); the storage memory area generally stores a large space, which can be NVM (Non-Volatile Memory), such as NOR Flash (NOR-type Flash Memory), NAND Flash (NAND-type Flash Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), MRAM (Magnetoresistive Random Access Memory), ReRAM (Resistive Random Access Memory), FRAM (Ferroelectric Random Access Memory), and the like. The running memory area 2010 includes a first storage area for storing first type data, and a second storage area for storing second type data.

[0040] The application layer 200 is configured to collect telemetry data through the collection module, and output the telemetry data to the data management layer 201.

[0041] In one embodiment, the telemetry data collected by the collection module is full-scene telemetry data, which can be understood as all telemetry data associated with the spaceflight equipment that can be collected by the collection module, including one or more of the following data: equipment state, attitude parameter, and environment state.

[0042] The data management layer 201 is configured to, when detecting that the recording switch interface is closed, store the telemetry data as first type data to the running memory area 2010 through an overwriting storage manner, and when detecting that the recording switch interface is opened, store the received telemetry data as second type data to the running memory area 2010.

[0043] Exemplarily, taking the first storage area for storing the first type data as an example, the first storage area includes storage area 1 to storage area 99, and the overwriting storage manner is that the obtained first type data is stored from the storage area 1 to the storage area 99 in sequence, if the first storage area is full, the newly obtained first type data overwrites the storage area 1 to the storage area 99 in sequence, and the same is true for the subsequent storage areas, which keeps the fixed storage space size of the telemetry record.

[0044] The data management layer 201 is also configured to acquire the first type of data and the second type of data, and store the first type of data and the second type of data as sentinel data to a storage memory area.

[0045] The telemetry remote control module 2001 is configured to send the sentinel data to a ground device.

[0046] In an embodiment, the acquisition module continuously acquires telemetry data in a timing manner (for example, once per second). When the recording switch interface is closed, the data management layer 201 stores the continuously acquired telemetry data as the first type of data to the first storage area in an overwriting manner, so that the first storage area maintains telemetry records of a fixed storage space size, and reduces the occupation of the running memory by a large amount of useless telemetry data. Further, when the recording switch interface is opened (the opening of the recording switch interface is triggered when a fault is detected, a critical event occurs, or a recording trigger instruction is received), the data management layer 201 stores the received telemetry data as the second type of data to the second storage area when the opening of the recording switch interface is detected. Each time the telemetry data is acquired, a plurality of data packets are included, for example, N1 (N1 is an integer greater than 0) data packets.

[0047] Further, when the second storage area for storing the second type of data is full, or the recording switch interface has been opened for more than 0 time t, the data management layer 201 adjusts the recording switch interface to be closed, and triggers the step of acquiring the stored first type of data and the second type of data, and stores the first type of data and the second type of data as sentinel data to the storage memory area.

[0048] The storage manner of the second type of data to the second storage area can be overwriting or non-overwriting (that is, the storage space is full, and new data does not overwrite old data for storage), which is not limited in the present application.

[0049] In an embodiment, since the second type of data stored in the second storage area is telemetry data acquired after a fault is detected, a critical event occurs, or a recording trigger instruction is received, it is of great help for subsequent ground judgment of abnormal situations during the operation of the space device. The storage space of the second storage area can be divided to be greater than that of the first storage area. The specific storage space size can be pre-configured according to experimental data.

[0050] In an embodiment, after the data management layer 201 acquires the first type of data and the second type of data, the data management layer 201 is further configured to add a sentinel label to each data packet in the first type of data and the second type of data, and store the first type of data and the second type of data after the sentinel label is added as sentinel data to the storage memory area.

[0051] The sentinel tag can be an identification field indicating whether it is ordinary telemetry or critical telemetry (such as fault, critical event, or record trigger instruction triggered telemetry), or an identification field indicating a specific fault type, critical event type, and record trigger instruction type, which is not limited in the present application.

[0052] In one embodiment, the running memory area 2010 includes a deframing buffer and a delivery buffer. The data management layer 201 is also configured to backup the sentinel data from the storage memory area to the deframing buffer for analysis, and store the analyzed sentinel data to the delivery buffer. Subsequently, the telemetry control module 2001 can obtain the analyzed sentinel data from the delivery buffer, and deliver the obtained sentinel data to the ground equipment.

[0053] For better understanding, the above telemetry control system will be further described in combination with specific examples.

[0054] The telemetry control system is deployed on a space device, and the application layer in the telemetry control system collects telemetry data every second through the collection module, and outputs the telemetry data to the data management layer. The telemetry data, record switch interface state, and processing mode received by the data management layer at each time point are shown in Table 1. Assuming that t is set to 3 seconds, at 07:03, when the data management layer detects that the record switch interface has been opened for 3 seconds, it can obtain telemetry data 1 from the first storage area as first class data 1, and obtain telemetry data 2, telemetry data 3, and telemetry data 4 from the second storage area as second class data 1. The sentinel tag is added to each data packet in the first class data 1 and the second class data 1, the first class data 1 and the second class data 1 after adding the sentinel tag are combined to form sentinel data 1, and the record switch interface is adjusted to be closed. Thus, a complete telemetry record is obtained.

[0055] Alternatively, still taking Table 1 as an example, assuming that the data management layer stores telemetry data 4 in the second storage area, and then finds that the second storage area is full, it can obtain telemetry data 1 from the first storage area as first class data 1, and obtain telemetry data 2, telemetry data 3, and telemetry data 4 from the second storage area as second class data 1. The sentinel tag is added to each data packet in the first class data 1 and the second class data 1, the first class data 1 and the second class data 1 after adding the sentinel tag are combined to form sentinel data 1, and the record switch interface is adjusted to be closed. Thus, a complete telemetry record is obtained.

[0056] By analogy, the same method can be used for the second, N2th (N2 is an integer greater than 3) complete telemetry record to obtain sentinel data 2, sentinel data N2, and the like.

[0057] Table 1

[0058] Time point Telemetry data Recording switch interface state Processing mode 07:00 Telemetry data 1 Off Telemetry data 1 is stored as first class data overwriting to a first storage area 07:01 Telemetry data 2 On Telemetry data 2 is stored as second class data overwriting to a second storage area 07:02 Telemetry data 3 On Telemetry data 3 is stored as second class data overwriting to a second storage area 07:03 Telemetry data 4 On Telemetry data 4 is stored as second class data overwriting to a second storage area

[0059] Further, when the telemetry enters the border, the data management layer backs up the unissued sentinel data in the storage memory area to the de-framing buffer according to the existing situation of the sentinel data, analyzes the sentinel data after de-framing, and stores the analyzed sentinel data to the issued buffer until all the sentinel data is analyzed. Subsequently, the telemetry and remote control module obtains data from the issued buffer and issues the obtained data to the ground equipment until all the data in the issued buffer is issued. The ground equipment can determine the abnormal situation of the satellite during operation according to all the received sentinel data.

[0060] In one embodiment, the present application also provides a telemetry communication system, which comprises a space device and a ground equipment, and the space device is provided with a telemetry module and a remote control module. Figure 2 The telemetry control system corresponding to the embodiment, the space device is used for issuing the sentinel data to the ground equipment after entering the border, and the ground equipment is used for determining the abnormal situation of the space device according to the sentinel data.

[0061] As a feasible implementation, each data packet in the above-mentioned sentinel data is added with a sentinel label. The ground equipment is also used for detecting whether the data includes the sentinel label after receiving the data issued by the space device, storing the data to the sentinel data area if the data includes the sentinel label, and storing the data to other data areas, such as a normal telemetry area used for storing normal telemetry data, if the data does not include the sentinel label. The normal telemetry data refers to telemetry data collected by a trigger instruction triggered by a non-fault, a key event or a record.

[0062] As a feasible implementation, when the sentinel label can indicate a specific fault type (system level fault, component level fault, single machine level fault, etc.), a key event type (star-rocket separation, sailboard unfolding, antenna unfolding, load switching on and off, telemetry entering and exiting the border, etc.), the ground equipment can store the sentinel data to each area of the sentinel data area according to the specific type represented by the sentinel label. For example, the sentinel label of the single machine level fault is stored to area 1 of the sentinel data area, the sentinel label of the component level fault is stored to area 2 of the sentinel data area, the sentinel data of the star-rocket separation event is stored to area 3 of the sentinel data area, and so on. In this way, subsequent analysis or model training based on these sentinel data does not need to be re-labeled and re-stored.

[0063] As a feasible implementation, the ground equipment can subsequently obtain the sentinel data from the sentinel data area and train a fault detection model through the sentinel data. The fault detection model can be a neural network model. Figure 3 is a structural schematic diagram of a space device provided by an embodiment of the present application. As shown in Figure 3As shown, the space device includes one or more processors 301, one or more memories 302 coupled to the processors 301, and one or more communication modules 300 coupled to the processors 301.

[0064] The communication module 300 is used for bidirectional communication. The communication module 300 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements.

[0065] The processor 301 can be of any type suitable to the local technical network and can include, by way of non-limiting example, one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples. The space device can have multiple processors such as application specific integrated circuit chips that are time slaved to a clock that synchronizes the main processor.

[0066] The processor 301 can be used to perform the following steps: when a fault or a critical event is detected, opening a recording switch interface; collecting telemetry data, storing the telemetry data as first type data to a running memory area by an overlay storage mode when it is detected that the recording switch interface is closed; obtaining the first type data and second type data, and storing the first type data and second type data as sentinel data to the storage memory area; and issuing the sentinel data to a ground device through the communication module 300.

[0067] In one embodiment, the running memory area includes a first storage area for storing the first type data, and a second storage area for storing the second type data. After the processor 301 obtains the first type data and the second type data, the processor 301 can further add a sentinel label to each data packet in the first type data and the second type data, and store the first type data and the second type data with the added sentinel label as sentinel data to the storage memory area.

[0068] In one embodiment, when the telemetry remote control module receives a recording trigger instruction from the ground device, the processor 301 controls the recording switch interface to open.

[0069] In one embodiment, the running memory area includes a de-framing buffer area and a delivery buffer area. The processor 301 can backup the sentinel data from the storage memory area to the de-framing buffer area for analysis, and store the analyzed sentinel data to the delivery buffer area. When performing the step of issuing the sentinel data to the ground device, the processor 301 is further used to obtain the analyzed sentinel data from the delivery buffer area, and issue the obtained data to the ground device.

[0070] In one embodiment, the telemetry control system is deployed on a space device, the fault comprises one or more of the following of the space device: a system-level fault, a component-level fault, and a single-machine-level fault; the critical event comprises one or more of the following of the space device: a satellite-rocket separation, a sailboard deployment, an antenna deployment, and a load switch-off.

[0071] In one embodiment, the processor 301 is further configured to trigger the step of acquiring the stored first type of data and the stored second type of data when it is detected that the second storage area for storing the second type of data is full, or when the recording switch interface has been turned on for more than 0 time t, and adjust the recording switch interface to be turned off.

[0072] In one embodiment, the telemetry data collected by the collection module is full-scene telemetry data, including one or more of the following: device status, attitude parameters, and environmental status.

[0073] The memory 302 can include the above-mentioned running memory area and the above-mentioned storage memory area.

[0074] The computer program includes computer executable instructions executed by the relevant processor 301. The computer program can be stored in the memory 302. The processor 301 can perform any appropriate actions and processes by loading the computer program into the memory 302.

[0075] Embodiments of the present application can be implemented by a computer program, so that the space device can perform any process discussed in the disclosure. Figure 2 Embodiments of the present application can also be implemented by hardware or by a combination of software and hardware.

[0076] In some embodiments, the computer program can be tangibly embodied in a computer readable medium, which can be included in the space device (for example, included in the memory 302 of the space device) or other storage devices accessible to the space device. The computer readable medium can include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The computer program is stored on the computer readable medium.

[0077] In general, the various embodiments of the application can be implemented in hardware or special-purpose circuits, software, logic or any combination thereof. Some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software which can be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the application are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein can be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controler or other computing devices, or some combination thereof.

[0078] The application also provides at least one computer program product which is tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, for example, instructions in a programming language that are executed by a device on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules can be combined or split between program modules as desired in various embodiments. Machine executable instructions for program modules can be executed within a local or distributed device. In a distributed device, program modules can be located in local and remote storage media.

[0079] Program code for carrying out methods of the application can be written in any combination of one or more programming languages. This program code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, when executed by the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / acts specified in the flow diagrams and / or block diagrams. The program code can execute entirely on a machine, partly on the machine, partly on a remote machine, or entirely on the remote machine or server.

[0080] In the context of the present application, computer program code or related data can be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0081] A computer readable medium can be a computer readable signal medium or a computer readable storage medium. A computer readable medium can include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer readable storage medium include 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.

[0082] Moreover, while operations have been described in a particular order, this should not be understood as requiring that such operations be performed in the particular order described, or in sequential order, or that all described operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Likewise, while a few particular implementations have been described in some detail, this has been done for illustration purposes only and is in no way intended to be limiting in scope, or to limit the scope of the application. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Accordingly, the application as set forth in the claims is not intended to be limited by the foregoing description, but encompasses all embodiments falling within the scope of the appended claims.

[0083] Although the application has been described in language specific to structural features and / or methodological acts, it is to be understood that the application defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A telemetry control system, characterized by, The system comprises an application layer and a data management layer, the application layer comprises a telemetry remote control module, a collection module and a fault event detection module; a record switch interface is arranged between the data management layer and the application layer; when the fault event detection module detects a fault or a critical event, the record switch interface is opened; the data management layer comprises a running memory area and a storage memory area, wherein: The application layer is configured to collect telemetry data through the collection module and output the telemetry data to the data management layer. The data management layer is configured to store the telemetry data as first type data in the running memory area through an overlay storage mode when detecting that the record switch interface is closed, and store received telemetry data as second type data in the running memory area when detecting that the record switch interface is opened. The data management layer is further configured to acquire the first type data and the second type data when detecting that a second storage area for storing the second type data is full or the record switch interface has been opened for more than 0 time t, adjust the record switch interface to be closed, and store the first type data and the second type data as sentinel data in the storage memory area. The telemetry remote control module is configured to send the sentinel data to a ground device.

2. The system of claim 1, wherein, The running memory area comprises a first storage area for storing the first type data and a second storage area for storing the second type data, and after the data management layer acquires the first type data and the second type data, the data management layer is further configured to: add a sentinel label in each data packet in the first type data and the second type data, and store the first type data and the second type data after adding the sentinel label as sentinel data in the storage memory area.

3. The system of claim 1 or 2, wherein, When the telemetry remote control module receives a record trigger instruction from a ground device, the record switch interface is opened.

4. The system of claim 1, wherein, The running memory area comprises a de-framing buffer and a sending buffer; the data management layer is further configured to, after entering a measurement and control, according to a sending situation of existing sentinel data, backup un-sent sentinel data from the storage memory area to the de-framing buffer for analysis, and store the analyzed sentinel data in the sending buffer; When the telemetry remote control module performs the step of sending the sentinel data to a ground device, the telemetry remote control module is further configured to acquire the analyzed sentinel data from the sending buffer and send the acquired data to the ground device.

5. The system of claim 1, wherein, The telemetry control system is arranged in a space device, the fault comprises one or more of the following of the space device: a system level fault, a component level fault and a single machine level fault; the critical event comprises one or more of the following of the space device: a satellite-rocket separation, a sailboard unfolding, an antenna unfolding, a load switching on and off and a measurement and control entering and leaving.

6. The system of claim 1, wherein, The telemetry data collected by the collection module is full-scene telemetry data, comprising one or more of the following data: a device state, an attitude parameter and an environment state.

7. A telemetry communication system characterized by, The telemetry communication system comprises a space device and a ground device, the space device is provided with the system according to any one of claims 1-6, and the space device is used to issue the sentinel data to the ground device after entering the country; the ground device is used to determine the abnormal condition of the space device according to the sentinel data.

8. The telemetry communication system of claim 7, wherein, Each data packet in the sentinel data is added with a sentinel label; the ground device is further used to detect whether the data issued by the space device includes the sentinel label after receiving the data; if the sentinel label is included, the data is stored in the sentinel data area, and if the sentinel label is not included, the data is stored in other data areas.

9. The telemetry communication system of claim 7, wherein, The ground device is further used to acquire the sentinel data from the sentinel data area, and train a fault detection model through the sentinel data.

Images