Microsatellite data processing rule engine and device
By designing a micro satellite data processing rule engine, the problem of complex configuration and poor maintenance of micro satellite data processing is solved, flexible configuration and efficient data processing are realized, adapting to the protocol and load requirements of different micro satellites, and supporting efficient field testing and on-orbit maintenance.
Patent Information
- Application Number
- CN202510334514.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-20
- Publication Date
- 2025-07-18
AI Technical Summary
There are problems such as complex configuration, high resource requirements and poor maintenance during the processing of micro satellite data, resulting in low development efficiency, protocol adjustment and on-orbit fault location require modification of software, and field testing and on-orbit maintenance are limited by the environment.
A micro satellite data processing rule engine is designed, including protocol, scrambling, routing, monitoring and scheduling rule engine modules. Combined with the executor, the data processing is automated and flexible configuration through conditions, comparison and action rules, and supports simplified versions of CCSDS-AOS and PDXP protocols, and adopts national secret SM4 encryption and decryption and polynomial verification rules to support a variety of network and storage methods.
It realizes that without modifying the system software, adapting to the data processing needs of different micro satellites, reducing configuration complexity and resource requirements, improving maintainability, and supporting efficient field testing and on-orbit maintenance.
Smart Images
Figure CN120336376A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of satellite aerospace technology, and particularly relates to a microsatellite data processing rule engine and device.
Background Art
[0002] The rule engine plays an important role in the microsatellite data processing system and is used for configuring data processing of different microsatellites in different application scenarios. Its main functions are to define, execute, and manage rules so as to trigger specific operations, decisions, and alarms according to the received telemetry and data transmission data. The microsatellite data processing rule engine allows users to achieve automated and real-time data processing and control in scenarios such as the comprehensive testing of satellites, on-orbit operation and control, and post-processing of payload data, so as to meet the requirements of satellite development, operation and control, and the production of payload data products.
[0003] CCSDS (Consultative Committee for Space Data Systems) is the abbreviation of the U.S. Space Data Systems Advisory Committee, which is responsible for formulating a series of standards for space communication. Among them, the AOS (Autonomous Orbital Services) communication protocol is part of the CCSDS standard and is mainly used for autonomous services and data transmission between satellites in Earth orbit and ground stations.
[0004] The PDXP protocol is a data transmission protocol used in the aerospace measurement and control system. It is defined based on the hierarchical structure of the TCP / IP protocol model and belongs to the data exchange protocol at the application layer. In the PDXP protocol, the two communication parties exchange data in the form of structured data packets and adopt the method of active data push. The data packets of this protocol consist of a fixed-byte header data and a variable-length data field. The header data contains information such as version, data identifier, time stamp, and data field length, while the data field contains the valid data to be transmitted. The data field can transmit various real-time information such as takeoff zero point, device status, telemetry parameters, optical data, radar data, and orbit data according to the corresponding frame format.
[0005] At present, during the data processing of microsatellites, due to the small size and flexible design of the satellites, there are a wide variety of payloads carried, large differences in the main satellite interfaces carried, and different launch vehicle interfaces carried. Different from traditional large spacecraft that generally adopt the standard CCSDS-AOS communication protocol, the telemetry and data transmission network communication protocols of different models of microsatellites vary greatly. Technicians often need to configure parameters such as the satellite's protocols, fault handling plans, and alarm fields for different satellites by modifying XML files. Once there is a protocol adjustment or on-orbit fault location, developers often need to modify and test the data processing software, which affects the overall satellite development efficiency. At the same time, during on-site testing and later on-orbit maintenance, different from traditional large spacecraft that generally perform tasks at large tracking and control stations and satellite tracking and control centers, considering cost and mission implementation, microsatellites generally use smaller commercial ground stations and tracking and control centers. Limited by the mission execution environment, data processing equipment with high maintainability is required.
[0006] In view of the technical problems of complex configuration, excessive resource requirements and costs, and poor maintainability in the data processing scenario during the development of microsatellites in the prior art, the present invention has made technical improvements to the microsatellite data processing rule engine and device.
Summary of the Invention
[0007] The object of the present invention is to propose a microsatellite data processing rule engine with simple configuration, low resource requirements and costs, and good maintainability.
[0008] To achieve the above object, the technical solution adopted by the present invention is a microsatellite data processing rule engine, including a protocol rule engine program module, a scrambling rule engine program module, a routing rule engine program module, a monitoring and display rule engine program module, a scheduling rule engine program module, and an execution machine program module;
[0009] The protocol rule engine program module is used to store the processing rules for the telemetry raw data and data transmission raw data received by the microsatellite from the ground station;
[0010] The scrambling rule engine program module is used to store the encryption and decryption rules, scrambling and descrambling rules, and verification rules of the microsatellite;
[0011] The routing rule engine program module is used to store the network routing rules of the microsatellite;
[0012] The monitoring and display rule engine program module is used to store the conversion rules for the physical quantities corresponding to the source packets of the microsatellite and the physical quantity monitoring and alarm rules;
[0013] The scheduling rule engine program module is used to store the rule management and scheduling methods of the microsatellite;
[0014] The execution engine program module is used to obtain rules from the protocol rule engine, the scrambling rule engine, the routing rule engine, and the monitoring and display rule engine, obtain the rule management scheduling method in the scheduling rule engine, and then execute the rules.
[0015] Preferably, the microsatellite data processing rule engine further includes a storage rule engine program module for storing microsatellite data storage rules.
[0016] Preferably, the protocol rules include metadata rules and structure data rules; the metadata rules include the name, unit, length, data type, data value, parsing type, and subsystem field to which the custom metadata belongs; the structure data rules are used to encapsulate the metadata rules and generate data structures at different levels. The structure data rules loop and apply the metadata to form data configurations of frames, packets, and blocks at different levels according to usage requirements, so that data protocols applicable to microsatellites can be generated without changing the system software.
[0017] Preferably, the protocol rule engine program module formulates protocol conversion and parsing rules through conditional rules, comparison rules, and action rules.
[0018] Preferably, the protocol rules are the simplified version of the CCSDS-AOS protocol rules and PDXP protocol rules for microsatellites.
[0019] Preferably, the microsatellite encryption and decryption rule is the national secret SM4, and the microsatellite scrambling and descrambling rule is the polynomial scrambling and descrambling rule h(X)=X 8 +X 6 +X 4 +X 3 +X 2 +X + 1, and the microsatellite check rule is the polynomial CRC check rule G(X)=X 16 +X 12 +X 5 + 1, sum check rule, and parity check rule.
[0020] Preferably, the routing rules are the source, destination, and configuration parameter rules of the UDP and TCP / IP network protocols, including input network configuration, output network configuration, and data processing software client / server configuration.
[0021] Preferably, the monitoring and display rule engine program module formulates physical quantity monitoring and alarm rules through conditional rules, comparison rules, and action rules.
[0022] Preferably, the scheduling rules include telemetry source packet periodic scheduling rules, asynchronous packet definition rules, and monitoring and display subscription and publishing rules.
[0023] Another object of the present invention is to provide a microsatellite data processing rule engine with simple configuration, low resource requirements and cost, and good maintainability.
[0024] To achieve the above object, the technical solution adopted by the present invention is a microsatellite data processing device, including a processor, a memory, and a computer program stored on the memory and operable on the processor. When the computer program is executed by the processor, it implements the above-mentioned microsatellite data processing rule engine.
[0025] The microsatellite data processing rule engine and device of the present invention have the following beneficial effects: it is used to solve the problems of complex configuration, excessive resource requirements and cost, and poor maintainability in the current microsatellite development data processing scenarios; when there is a protocol adjustment or on-orbit fault location, it does not require developers to modify and test the data processing software, and does not affect the overall satellite development efficiency; during the microsatellite field test and later on-orbit maintenance, a smaller commercial ground station and TT&C center are adopted, and it is not limited by the mission execution environment, and the data processing equipment has high maintainability.
Description of the Drawings
[0026] Figure 1 It is an architecture diagram of a microsatellite data processing rule engine.
[0027] Figure 2 It is a flowchart of setting metadata for downlinking telemetry data from a ground station by the protocol rule engine using a simplified version of the CCSDS protocol.
[0028] Figure 3 It is a flowchart of configuring structured data for downlinking telemetry data from a ground station by the protocol rule engine using a simplified version of the CCSDS protocol.
[0029] Figure 4 It is a flowchart of formulating parsing rules for downlinking telemetry data from a ground station by the protocol rule engine using a simplified version of the CCSDS protocol.
[0030] Figure 5 It is a flowchart of the monitoring and display rule engine calculating to obtain the real-time status of the newly added on-orbit maintenance first aid kit and simultaneously linking the satellite bus to define the first aid kit status function.
[0031] Figure 6 It is a flowchart of the monitoring and display rule engine calculating to obtain the real-time status of the newly added on-orbit maintenance first aid kit and simultaneously linking the satellite bus to define the first aid kit status value judgment rule.
[0032] Figure 7 It is a flowchart of the monitoring and display rule engine calculating to obtain the real-time status of the newly added on-orbit maintenance first aid kit and simultaneously linking the satellite bus to define the linkage rule.
[0033] Figure 8It is a structural diagram of a microsatellite data processing device.
Specific Embodiment
[0034] The present invention will be further described below in conjunction with embodiments and with reference to the accompanying drawings.
[0035] Embodiment 1
[0036] This embodiment implements a microsatellite data processing rule engine.
[0037] A microsatellite data processing rule engine in this embodiment is used to solve problems such as complex configuration, excessive resource requirements and costs, and poor maintainability in the current microsatellite development data processing scenarios.
[0038] Figure 1 It is a structural diagram of a microsatellite data processing rule engine. As Figure 1 shown, a microsatellite data processing rule engine in this embodiment includes: a protocol rule engine, a scrambling rule engine, a routing rule engine, a monitoring and display rule engine, a storage rule engine, a scheduling rule engine, and an execution machine.
[0039] Among them, the protocol rule engine stores the processing rules for the original data of telemetry and data transmission received by the microsatellite from the ground station, and the default rules are the simplified version of the CCSDS-AOS protocol rules and PDXP (Packet Data Exchange Protocol) protocol rules for the microsatellite.
[0040] The scrambling rule engine stores the encryption and decryption rules, scrambling and descrambling rules, and check rules in the microsatellite. The default stored encryption and decryption rules are the national secret SM4, and the polynomial scrambling and descrambling rule h(X)=X 8 +X 6 +X 4 +X 3 +X 2 +X+1, the default polynomial CRC check rule G(X)=X 16 +X 12 +X 5 +1, the default sum check and parity check rules.
[0041] The routing rule engine stores the network routing rules in the microsatellite. The default stored source, destination, and configuration parameter rules for the UDP and TCP / IP network protocols.
[0042] The storage rule engine stores the data storage rules in the microsatellite. The default storage types include database type, local disk type, and cloud disk type.
[0043] The monitoring and display rule engine stores the conversion rules for the physical quantities corresponding to the source packets in the microsatellite and the physical quantity monitoring and alarm rules.
[0044] The execution machine is used to execute each meta-rule.
[0045] It should be noted that the rule engine in this embodiment is a rule engine for data processing, especially for the data processing scenario of microsatellites. Specifically:
[0046] Among them, the protocol rule engine stores the processing rules for the original data of telemetry and data transmission received by the microsatellite from the ground station. The default rules include metadata rules and structure data rules. Among them, the metadata rules include fields such as the name, unit, length, data type, data value, parsing type, and affiliated subsystem of the custom metadata. The structure data rule is an encapsulation of the metadata rule and is used to generate structures at different levels. The structure data rule includes the structure data name and the sub-data name. Among them, the sub-data can be metadata rules and structure data rules. The design of the structure data rule can loop and apply metadata to form data configurations of frames, packets, and blocks at each level according to the usage requirements, so that various data protocols suitable for microsatellites can be generated without changing the system software.
[0047] The protocol rule engine formulates protocol conversion and parsing rules through condition (Condition) rules (by default including and, or, not, if, else, elif, then), comparison rules (by default including equal to, not equal to, less than, less than or equal to, greater than, greater than or equal to, exists, does not exist), and action rules (by default including in and out).
[0048] For example, when the data transmission data sent from the ground station uses a simplified version of the CCSDS protocol and it is necessary to obtain effective remote sensing camera payload data from the data, without changing the parsing software, it is necessary to add the parsing of the on-orbit maintenance first aid kit data. Figure 2 It is a flowchart for setting metadata when the protocol rule engine uses the simplified CCSDS protocol to send data transmission data from the ground station. As Figure 2 shown, first, set the metadata in the human-machine interface. The metadata includes the metadata name, metadata unit, metadata length, metadata type, metadata value, and metadata parsing flag, and configure all the basic field attributes of the whole satellite into the rule engine. Figure 3 It is a flowchart for configuring structured data when the protocol rule engine uses the simplified CCSDS protocol to send data transmission data from the ground station. As Figure 3 shown, subsequently, configure the structured data, encapsulate the metadata or structure data into the structure data, and define the components of the structure data through the parent-child structure. Figure 4 It is a flowchart for formulating parsing rules when the protocol rule engine uses the simplified CCSDS protocol to send data transmission data from the ground station. As Figure 4As shown, finally, parsing rules are formulated to parse the input meta or structured data into new meta / structured data according to the parsing process defined by the rule engine. After defining multiple protocol rules, finally, each engineering parameter to be parsed is output to the corresponding defined name.
[0049] The scrambling rule engine stores the encryption / decryption rules, scrambling / descrambling rules, and verification rules in the microsatellite. The encryption / decryption rules include the encryption / decryption name, encryption / decryption key, encryption / decryption type, and encryption / decryption parameters. The commonly used SM4 encryption / decryption algorithm is configured by default. The scrambling / descrambling rules include the scrambling / descrambling name, scrambling / descrambling type, and scrambling / descrambling parameters. The commonly used polynomial scrambling / descrambling algorithm, h(X)=X 8 +X 6 +X 4 +X 3 +X 2 +X + 1. The verification rules include CRC verification, sum verification, and parity verification. The default polynomial CRC verification rule G(X)=X 16 +X 12 +X 5 +1, and the sum verification is single-word and double-word verification.
[0050] The routing rule engine stores the network routing rules in the microsatellite. The routing rule engine includes input network configuration, output network configuration, and data processing software client / server configuration. The input network configuration includes the input network type (by default, including UDP, TCP, and HTTP) and the input network data source type (by default, including point-to-point, broadcast, and data bus). The output network configuration includes the output network type (same as the input network configuration) and the output network data source type (same as the input network data source type). The data processing software client / server configuration includes the source and destination address configuration of the input and output networks, and whether the input and output networks are servers or clients.
[0051] The monitoring and display rule engine stores the conversion rules for the physical quantities corresponding to the source packets in the microsatellite and the physical quantity monitoring and alarm rules. Since there are many types of microsatellite payloads, there are many types of conversion formulas for converting the source code of the corresponding single machine into physical quantities. The traditional processing method is to modify the corresponding formula library and software to adapt to the new payload. The monitoring and display rule engine formulates custom rules for monitoring and alarm through conditional (Condition) rules (by default, including and, or, not, if, else, elif, then, and express), comparison rules (by default, including equal to, not equal to, less than, less than or equal to, greater than, greater than or equal to), and action rules (by default, including in and out).
[0052] For example, it is necessary to calculate the status formula of the newly added on-orbit maintenance first aid kit, obtain its real-time status, and at the same time link the bus voltage of the satellite. When the bus voltage is normal but the status of the on-orbit maintenance first aid kit is abnormal, an alarm is triggered. Figure 5 It is a function flow chart of the monitoring and display rule engine for calculating and obtaining the real-time status of the newly added on-orbit maintenance first aid kit and linking the satellite bus to define the first aid kit status. As Figure 5 shown, first, define the first aid kit status function through the monitoring and display rule engine, and introduce the source code in express to convert it into the definition of physical quantities. Figure 6 It is a function flow chart of the monitoring and display rule engine for calculating and obtaining the real-time status of the newly added on-orbit maintenance first aid kit and linking the satellite bus to define the judgment rule of the first aid kit status value. As Figure 6 shown, subsequently, define the judgment rule of the first aid kit status value through the monitoring and display rule engine, and obtain the physical quantity of the first aid kit status according to the rule after parsing the source code of the first aid kit status. Figure 7 It is a function flow chart of the monitoring and display rule engine for calculating and obtaining the real-time status of the newly added on-orbit maintenance first aid kit and linking the satellite bus to define the linkage rule. As Figure 7 shown, finally, define the linkage rule through the monitoring and display rule engine. When the bus voltage is normal and the first aid kit status is 0, trigger the alarm action.
[0053] The storage rule engine stores the data storage rules in the microsatellite. The default storage types include database type, local disk type, and cloud disk type. Among them, the database type is default to InfluxDB, which is used to store telemetry and data transmission timing data. The local disk type is default to localDisk, which is used to store payload data. The cloud disk type is remote storage, such as Nas, which is used to periodically migrate payload data. Through the storage rule engine, the data storage scheme for the microsatellite can be flexibly defined. For example, define the action of migration or deletion when the storage capacity in a certain area reaches the warning.
[0054] The scheduling rule engine stores the data scheduling rules in the microsatellite. The default scheduling rules include periodic scheduling of telemetry source packets, asynchronous packet definition, and monitoring and display subscription and publishing rules. The scheduling rule engine introduces a communication mechanism similar to the Internet of Things, defines each on-board single machine and payload as an IoT device, and monitors the parameters of each single machine and payload according to the rules defined by the engine through the Mqtt protocol. For example, when a certain client needs to view all the parameters of the on-orbit first aid data packet, the format and display period of the on-orbit first aid data packet that the client can subscribe to can be defined in the scheduling rule engine according to the permissions.
[0055] The execution machine is the computing service of the data processing rule engine. The execution machine obtains the meta-rules from each rule engine. In the scheduling rule engine, obtain the rule management scheduling method, and then execute the rules.
[0056] Embodiment 2
[0057] This embodiment implements a microsatellite data processing device. The device in this embodiment is used to execute a microsatellite data processing rule engine described in Embodiment 1.
[0058] Figure 8 It is a structural diagram of a microsatellite data processing device. As Figure 8 shown, the device in this embodiment includes a processor, a memory, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the method for implementing a microsatellite data processing rule engine for microsatellite data processing described in Embodiment 1 above.
[0059] Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware or by a program instructing relevant hardware. The program can be stored in a computer-readable storage medium, where the storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM), etc.
[0060] The above are only the preferred embodiments of the present invention. It should be noted that for those of ordinary skill in the art of this technology, without departing from the principle of the present invention, several improvements and supplements can be made, and these improvements and supplements should also be regarded as the protection scope of the present invention.
Claims
1. A microsatellite data processing rule engine, characterized in that: It includes a protocol rule engine program module, a scrambling rule engine program module, a routing rule engine program module, a monitoring and display rule engine program module, a scheduling rule engine program module, and an execution machine program module; The protocol rule engine program module is used to store the telemetry raw data received by the microsatellite from the ground station and the processing rules for the data transmission raw data; The scrambling rule engine program module is used to store the encryption and decryption rules, scrambling and descrambling rules, and verification rules of the microsatellite; The routing rule engine program module is used to store the microsatellite network routing rules; The monitoring and display rule engine program module is used to store the conversion rules for the physical quantities corresponding to the microsatellite source packets and the physical quantity monitoring and alarm rules; The scheduling rule engine program module is used to store the microsatellite rule management and scheduling methods; The execution machine program module is used to obtain rules from the protocol rule engine, the scrambling rule engine, the routing rule engine, and the monitoring and display rule engine, obtain the rule management and scheduling methods in the scheduling rule engine, and then execute the rules.
2. The micro-satellite data processing rule engine according to claim 1, wherein: It also includes a storage rule engine program module, which is used to store the microsatellite data storage rules.
3. The micro-satellite data processing rule engine according to claim 1, wherein: The protocol rules include metadata rules and structure data rules; the metadata rules include the name, unit, length, data type, data value, parsing type, and subsystem fields to which they belong for custom metadata; The structure data rules are used to encapsulate the metadata rules and generate data structures at different levels. The structure data rules loop and apply the metadata to form data configurations of frames, packets, and blocks at different levels according to the usage requirements, so that a data protocol applicable to the microsatellite can be generated without changing the system software.
4. The micro-satellite data processing rule engine according to claim 3, wherein: The protocol rule engine program module formulates protocol conversion and parsing rules through conditional rules, comparison rules, and action rules.
5. The micro-satellite data processing rule engine according to claim 4, characterized in that: The protocol rules are the simplified version of the CCSDS-AOS protocol rules and PDXP protocol rules for the microsatellite.
6. The microsatellite data processing rule engine according to claim 1, wherein: The encryption and decryption rules of the microsatellite are the national cryptographic SM4, and the scrambling and descrambling rules of the microsatellite are the polynomial scrambling and descrambling rules h(X)=X 8 +X 6 +X 4 +X 3 +X 2 +X+1. The verification rules of the microsatellite are the polynomial CRC verification rules G(X)=X 16 +X 12 +X 5 +1, the sum verification rule and the parity verification rule.
7. A microsatellite data processing rule engine according to claim 1, characterized in that: The routing rules are the source, destination, and configuration parameter rules of the UDP and TCP / IP network protocols, including input network configuration, output network configuration, and data processing software client / server configuration.
8. A micro-satellite data processing rules engine according to claim 1, characterized in that: The monitoring and display rule engine program module formulates physical quantity monitoring and alarm rules through conditional rules, comparison rules, and action rules.
9. The micro-satellite data processing rule engine according to claim 1, characterized in that: The scheduling rules include the periodic scheduling rules for telemetry source packets, asynchronous packet definition rules, and monitoring and display subscription and publishing rules.
10. A microsatellite data processing device, comprising a processor, a memory, and a computer program stored on the memory and executable on the processor, characterized in that: When the computer program is executed by the processor, it implements a microsatellite data processing rule engine according to any one of claims 1 to 9.