XML-based multi-satellite automatic starting method and device, computer device and storage medium

Abstract

The application provides a multi-satellite automatic command method based on XML, comprising: planning a multi-satellite TT&C task according to a multi-satellite flight control task target and resource constraints; generating an executable instruction sequence according to a flight control program of the multi-satellite in each TT&C arc segment, combining a satellite telemetry parameter table and a remote control instruction table, and converting the instruction sequence into a structured XML file; parsing the structured XML file, performing format checking and logic checking, and generating an executable job plan; and automatically or semi-automatically sending an instruction to a satellite based on a trigger condition defined in the structured XML file and the executable job plan in an actual TT&C arc segment. The application also provides a multi-satellite automatic command device based on XML, a computer device and a computer readable storage medium. Thus, the application realizes standardization and automation of multi-satellite command sequences through an XML structure, and solves the problem of complex configuration of command sequences in multi-satellite flight control tasks.

Description

Technical Field

[0001] This invention relates to the field of satellite flight control technology, and in particular to a multi-satellite automatic command method, device, computer equipment, and storage medium based on XML. Background Technology

[0002] With the development of aerospace technology and the accelerated deployment of low-Earth orbit mega-constellations, multi-satellite launch missions are becoming increasingly common, making the programming and command transmission of multi-satellite flight procedures a crucial aspect of satellite flight control. However, traditional multi-satellite flight control programming and command transmission methods suffer from the following problems: (1) Complex configuration of multi-satellite commands: In a multi-satellite launch mission, the parameters of each satellite are partially consistent and partially inconsistent. It is necessary to configure command parameters for each satellite separately, which is labor-intensive and prone to errors. (2) Inefficient command sending process: Command sending relies on manual judgment and lacks standardized automatic sending rules, resulting in low command sending efficiency; (3) Difficulty in coordinating multi-satellite missions: In multi-satellite missions, the timing, conditions, parameters, etc. of the command transmission of each satellite need to be precisely coordinated, and traditional methods are difficult to achieve automated management.

[0003] In summary, existing technologies lack automatic command methods for multi-satellite flight control missions, and therefore cannot effectively solve the aforementioned problems. Summary of the Invention

[0004] To address the problems of existing technologies, this invention proposes an XML-based multi-satellite automatic command sending method, apparatus, computer equipment, and readable storage medium for the automatic transmission of commands in multi-satellite flight control missions.

[0005] To achieve the above-mentioned technical effects, firstly, the present invention provides a multi-star automatic command sending method based on XML, comprising: Standardized steps for telemetry, tracking, and command (TT&C) missions: Plan multi-satellite TT&C missions based on the objectives and resource constraints of the multi-satellite flight control mission; Command sequence design steps: Based on the flight control programs of multiple satellites in each telemetry and control arc, combined with the satellite telemetry parameter table and remote control command table, generate an executable command sequence and convert the command sequence into a structured XML file; The steps for generating a work plan are as follows: parse the structured XML file, perform format and logic checks, and generate an executable work plan. Operation sequence execution steps: Within the actual telemetry and control arc segment, instructions are automatically or semi-automatically sent to the satellite based on the triggering conditions defined in the structured XML file and the executable operation plan.

[0006] Furthermore, the structured XML file includes a root element, which is a root element model task used to describe relevant information about a specific task; The root element model task includes two types of attributes: attribute task code and attribute task name; the attribute task code is used to describe the task or task group code; the attribute task name is used to describe the task or task group name information; The root element model task includes a sub-element and is defined as a sub-element flight procedure set, which is used to describe the flight control procedure set information.

[0007] Furthermore, the sub-element flight procedure set includes three types of sub-elements at the next level: sub-element key event identifier set, sub-element injected data type set, and sub-element sub-flight procedure; the sub-element key event identifier set is used to describe the key event identifier set information; the sub-element injected data type set is used to describe the injected data corresponding list set information; and the sub-element sub-flight procedure is used to describe the sub-flight control program information.

[0008] Furthermore, the set of key event identifiers for child elements includes key event identifiers for the next level of child elements, and the key event identifiers for child elements are used to describe key events; the key event identifiers for child elements include attribute key event names, and the attribute key event names are used to describe the names of key events; The set of sub-element injected data types includes the sub-element injected data types of the next level. The sub-element injected data types are used to describe the injected data type information. The sub-element injected data types include two types of attributes: attribute injected data name and maximum number of attribute injected data blocks. The attribute injected data name is used to describe the name of the injected data, and the maximum number of attribute injected data blocks is used to describe the maximum number of data blocks injected in one processing. The sub-element sub-flight procedure includes the next-level sub-element normal flight control procedure and the sub-element fault handling procedure. The sub-element normal flight control procedure describes the normal flight control procedure; the sub-element fault handling procedure describes the abnormal flight control procedure; the sub-element sub-flight procedure includes two types of attributes: attribute telemetry and control circle sub-code and attribute satellite code set. The attribute telemetry and control circle sub-code describes the telemetry and control circle sub-code, and the attribute satellite code set describes the satellites to which the sub-flight control procedure is applicable.

[0009] Furthermore, the sub-element normal flight control procedure includes a first sub-element event at the next level, which is used to describe the events in the sub-flight control procedure; the sub-element normal flight control procedure includes an attribute normal flight control procedure name, which is used to describe the event name; The sub-element fault handling procedure further includes a second sub-element event at the next level, which is used to describe events in the sub-flight control procedure; the sub-element fault handling procedure includes two types of attributes: attribute fault handling procedure code and attribute fault handling procedure name. The attribute fault handling procedure code is used to describe the fault handling procedure number, and the fault handling procedure name is used to describe the fault handling procedure name.

[0010] Furthermore, the first sub-element event includes the next-level sub-element execution sending time, the sub-element execution condition criterion set, the sub-element instruction, and the sub-element execution completion criterion set; the sub-element execution sending time is used to describe the event time constraint; the sub-element execution condition criterion set is used to describe the event execution condition criterion set; the sub-element instruction is used to describe the event-related instruction; the sub-element execution completion criterion set is used to describe the event execution result criterion set; the first sub-element event includes three types of attributes: attribute encryption status, attribute blind transmission status, and attribute event name; the attribute encryption status is used to describe the public / confidential status of the sub-flight control program; the attribute blind transmission status is used to describe the event emergency attribute; and the attribute event name is used to describe the event name.

[0011] Furthermore, the set of sub-element execution condition criteria includes the next-level sub-element execution condition criteria. The sub-element execution condition criteria are used to describe the event execution condition criteria. The sub-element execution condition criteria include two types of attributes: the number of telemetry reads of the attribute execution condition and the duration of the telemetry reads of the attribute execution condition. The number of telemetry reads of the attribute execution condition is used to describe the number of frames required for the expression to be successfully judged, and the duration of the telemetry reads of the attribute execution condition is used to describe the longest time required for the expression to be judged. The sub-element instruction includes the next-level sub-element instruction sending conditions, the sub-element remote control instruction code, and the sub-element instruction content; the sub-element instruction sending conditions describe the prerequisites for instruction sending; the sub-element remote control instruction code describes the unique code and instruction sending attributes of the instruction; the sub-element instruction content describes the data content carried by the instruction; the sub-element remote control instruction code includes two types of attributes: attribute remote control instruction name and attribute instruction parameters, the attribute remote control instruction name describes the name of the remote control instruction, and the attribute instruction parameters describe the content of the instruction parameters; the sub-element instruction content includes two types of attributes: attribute applicable satellite and attribute data block identifier, the attribute applicable satellite describes the satellites to which the sub-element instruction content applies, and the attribute data block identifier describes the unique identifier of the sub-element instruction content; The set of criteria for sub-element execution completion includes the criteria for sub-element execution completion at the next level. The criteria for sub-element execution completion are used to describe the basis for determining the completion of instruction execution. The criteria for sub-element execution completion include two types of attributes: the number of telemetry reads for attribute execution completion and the duration of telemetry reads for attribute execution completion. The number of telemetry reads for attribute execution completion is used to describe the number of telemetry reads for instruction execution completion, and the duration of telemetry reads for attribute execution completion is used to describe the duration of telemetry reads for execution completion.

[0012] Secondly, the present invention also provides a multi-satellite automatic command device based on XML, the device comprising: a telemetry and control task planning unit, an execution sequence design unit, a job plan generation unit, and a job sequence execution unit, wherein: The telemetry, tracking, and command (TT&C) mission planning unit is used to plan multi-satellite TT&C missions based on the objectives and resource constraints of the multi-satellite flight control mission. The execution sequence design unit is used to generate specific, executable instruction sequences based on the flight control programs of multiple satellites in each telemetry and control arc, combined with satellite telemetry parameter tables and remote control instruction tables, and convert them into structured XML files. The job plan generation unit is used to parse the structured XML file, perform format and logic checks, and generate an executable job plan. The operation sequence execution unit is used to automatically or semi-automatically send instructions within the actual measurement and control arc segment according to the triggering conditions defined in the structured XML file.

[0013] Thirdly, the present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the XML-based multi-star automatic command method as described above.

[0014] Fourthly, the present invention also provides a computer-readable storage medium for storing a computer program that executes the XML-based multi-star automatic command method as described above.

[0015] Compared with the prior art, the beneficial effects of the present invention include: 1) Improve the efficiency of multi-satellite flight control: By defining multi-satellite flight control mission programs through a standardized XML structure, the tedious work of configuring instructions for each satellite individually is avoided, which greatly improves the efficiency of multi-satellite flight control mission program development. 2) Enhanced accuracy of command transmission: By using automatic command transmission methods and devices, manual intervention is reduced, and command transmission errors caused by human judgment are avoided; 3) Flexible adaptation to differences among multiple satellites: Through different configuration modes, it can flexibly adapt to situations where the command sequences are completely consistent, partially consistent, or completely inconsistent in multi-satellite flight control missions, to meet different mission requirements; 4) Achieve automation of multi-satellite missions: Through automatic command issuance methods and devices defined by XML structure, the sending of commands in multi-satellite flight control missions is automated, improving flight control efficiency; 5) Ensure coordination of multi-satellite missions: Through XML structure standardization, ensure the consistency of command transmission time, conditions, parameters, etc. of each satellite in multi-satellite flight control missions. Attached Figure Description

[0016] Figure 1 A flowchart illustrating the steps of the XML-based multi-star automatic command sending method provided in an embodiment of the present invention; Figure 2 A schematic diagram illustrating the structured XML file elements of the multi-star automatic command method based on XML provided in an embodiment of the present invention; Figure 3 A schematic diagram of the structure of the XML-based multi-star automatic command device provided in another embodiment of the present invention; Figure 4 A schematic diagram of the structure of the computer device provided by the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0018] It should be noted that references to "an embodiment," "embodiment," "example embodiment," etc., in this specification refer to the described embodiment including specific features, structures, or characteristics, but not every embodiment must include these specific features, structures, or characteristics. Furthermore, such expressions do not refer to the same embodiment. Moreover, when describing specific features, structures, or characteristics in conjunction with embodiments, whether or not explicitly described, it is indicated that incorporating such features, structures, or characteristics into other embodiments is within the knowledge of those skilled in the art.

[0019] Furthermore, certain terms are used in the specification and subsequent claims to refer to specific components or parts. Those skilled in the art will understand that manufacturers may use different names or terms to refer to the same component or part. This specification and subsequent claims do not distinguish components or parts by differences in name, but rather by differences in function. The terms "comprising" and "including" used throughout the specification and subsequent claims are open-ended and should be interpreted as "including but not limited to." Additionally, the term "connection" here includes any direct and indirect electrical connection means. Indirect electrical connection means include connections made through other means.

[0020] The core concept of this invention is to uniformly model and transform the multi-satellite flight control program and its related telemetry parameters, remote control commands, execution criteria, and other information into a structured XML file. This standardized format is used to define the control logic as "event-criteria-command". The system can automatically parse this file, complete the format and logic verification, generate an executable work plan, and finally, within the actual telemetry and control arc, automatically or semi-automatically send commands to each satellite according to the predefined trigger conditions in the XML, thereby realizing the standardized and automated management of multi-satellite missions.

[0021] To enable those skilled in the art to reproduce and implement the present invention, the various steps of the XML-based multi-star automatic command generation method will be described in detail below with reference to the accompanying drawings and specific embodiments. These embodiments are specific illustrations of the present invention, and their descriptions are helpful in understanding the present invention, but should not be construed as limiting the present invention.

[0022] Figure 1 This invention illustrates an XML-based multi-satellite automatic command method, applicable to the field of aerospace engineering satellite flight control. The method includes steps S101 (parameter and control mission specification), S102 (command sequence design), S103 (job plan generation), and S104 (job sequence execution). Specifically: S101: Plan multi-satellite telemetry and control missions based on the objectives and resource constraints of multi-satellite flight control missions; In practical applications, the telemetry and control mission planning includes flight procedure design, launch window design, telemetry and control arc design, and orbit change strategy design. The flight procedure generally includes major events such as satellite-rocket separation, solar array unlocking and deployment, satellite switching to Earth-oriented operation mode, antenna deployment, payload health check, and satellite status setting, as exemplified in Table 1 below.

[0023] Table 1:

[0024] S102: Based on the flight control programs of multiple satellites in each telemetry and control arc, combined with the satellite telemetry parameter table and remote control command table, generate an executable command sequence and convert the command sequence into a structured XML file.

[0025] The command sequence refers to the sequence of commands that need to be sent to the satellite in each telemetry and control segment to complete a major event, as well as the pre-command criteria and post-command criteria. For example, the command sequence for unlocking satellite laser terminals 1 and 2 is shown in Table 2 below; where: sequence number 1 is the pre-event judgment, sequence numbers 2 and 3 are the sent commands and post-command criteria, and sequence number 4 is the criterion after the laser terminal finishes execution.

[0026] Table 2:

[0027] For ease of representation and code implementation, this embodiment uses conventional English names to represent the Chinese names of the root element, various child elements, and various attributes in the structured XML file. For example, the English names corresponding to the root element, various child elements, and various attributes appearing in the structured XML file are shown in Table 3 below.

[0028] Table 3:

[0029] like Figure 2 As shown, the structured XML file in this embodiment includes a root element, which is a root element named Satellite used to describe relevant information about a specific mission. The root element Satellite includes two types of attributes: the attribute task code and the attribute task name. The attribute task code is used to describe the task or task group code. The attribute task name is used to describe the name information of the task or task group. The root element Satellite includes a child element and is defined as the child element Flight Procedure Collection Missions, which is used to describe the flight control procedure collection information.

[0030] The attribute "task code" is an optional attribute used to describe the task or task group code; the attribute "task name" is an optional attribute used to describe the task or task group name information; an example usage is shown below.

[0031] <satellite name="XXXX" code=""P01-001”"> <missions> < / missions> < / satellite> In an optional implementation, the sub-element flight procedure set Missions includes three types of sub-elements at the next level: the sub-element key event identifier set Keys, the sub-element injected data type set TcDataTypes, and the sub-element sub-flight procedure Mission; the sub-element key event identifier set Keys is used to describe the key event identifier set information; the sub-element injected data type set TcDataTypes is used to describe the injected data corresponding list set information; and the sub-element sub-flight procedure Mission is used to describe the sub-flight control program information. An exemplary use is shown below.

[0032] <missions> <keys>< / keys> <tcdatatypes>< / tcdatatypes> <mission>< / mission> ...... <mission>< / mission> < / missions> Furthermore, the child element key event identifier set Keys includes the next-level child element key event identifiers Key, which are used to describe key events; the child element key event identifier Key includes the attribute key event name, which is used to describe the name of the key event. An example of its use is shown below.

[0033] <keys> <key name="起飞"> SYS$T0< / key> <key name="星箭分离"> SYS$TF< / key> < / keys> The sub-element injected data type set includes the next-level sub-element injected data type TcDataType, which is used to describe the injected data type information. The sub-element injected data type TcDataType includes two attributes: attribute injected data name (name) and maximum number of attribute injected data blocks (maxNum). The attribute injected data name (name) describes the name of the injected data, and the maximum number of attribute injected data blocks (maxNum) describes the maximum number of data blocks injected in a single processing operation. An example usage is shown below.

[0034] <tcdatatypes> <tcdatatype name="目标星轨道数据" maxnum="36"> MBGD< / tcdatatype> ...... <tcdatatype name="轨控数据"> GK< / tcdatatype> ...... <tcdatatype name="业务数据"> YW< / tcdatatype> < / tcdatatypes> The sub-element sub-flight procedure includes the next-level sub-element normal flight control procedure (NormalMission) and the sub-element fault handling procedure (ErrorMission). The normal flight control procedure (NormalMission) describes the normal flight control procedure; the fault handling procedure (ErrorMission) describes the fault handling flight control procedure. The sub-element sub-flight procedure (Mission) includes two types of attributes: the attribute telemetry and control circle number (qId) and the attribute satellite number set (sates). The attribute telemetry and control circle number (qId) describes the telemetry and control circle number, and the attribute satellite number set (sates) describes the satellites to which the sub-flight control procedure applies. An exemplary use is shown below.

[0035] <mission name="星箭分离相关事件" qid="Q1" sates="01 / 02 / 03 / 04 / 05"> <normalmission>< / normalmission> <errormission>< / errormission> ...... <errormission>< / errormission> < / mission> In an optional implementation, the sub-element NormalMission includes a first sub-element Event (hereinafter referred to as "first" for ease of distinction, but all elements are named Event) at the next lower level, which describes events in the sub-flight control program; the sub-element NormalMission includes the attribute NormalMission Name, which describes the event name; correspondingly, the sub-element ErrorMission further includes a second sub-element Event at the next lower level, which describes events in the sub-flight control program; the sub-element ErrorMission includes two types of attributes: the attribute ErrorMission Code gzindex and the attribute ErrorMission Name name, whereby the attribute ErrorMission Code gzindex describes the errorMission number and the attribute ErrorMission Name name describes the errorMission name.

[0036] In an optional implementation, the first sub-element event includes the next-level sub-element execution and transmission time (ExeTime), the sub-element execution condition criteria set (EventConditions), the sub-element command (Command), and the sub-element execution completion criteria set (EventCompletes). The sub-element execution and transmission time (ExeTime) describes the event's time constraints; the sub-element execution condition criteria set (EventConditions) describes the event's execution condition criteria set; the sub-element command (Command) describes the event-related commands; and the sub-element execution completion criteria set (EventCompletes) describes the event's execution result criteria set. The first sub-element event includes three types of attributes: attribute encryption state (encry), attribute blind transmission state (isEmergency), and attribute event name (name). The attribute encryption state (encry) describes the confidentiality status of the sub-flight control program; the attribute blind transmission state (isEmergency) describes the event's emergency attribute; and the attribute event name (name) describes the event name.

[0037] Furthermore, the sub-element execution condition set EventConditions includes the next-level sub-element execution condition judgment EventCondition, which describes the event execution condition judgment. The sub-element execution condition judgment EventConditions includes two types of attributes: the number of telemetry reads of the attribute execution condition (count) and the duration of the telemetry reads of the attribute execution condition (timeOuts). The number of telemetry reads of the attribute execution condition (count) describes the number of frames required for successful expression judgment, and the duration of the telemetry reads of the attribute execution condition (timeOuts) describes the maximum judgment time for the expression. The sub-element command Command includes the next-level sub-element command sending condition SendCondition, the sub-element remote control command code Code, and the sub-element command content SJContent. The sub-element command sending condition SendCondition describes the preconditions for command sending; the sub-element remote control command code Code describes the unique code and command sending attributes; and the sub-element command content SJContent describes the data content carried by the command. The sub-element remote control command code Code... The `ode` includes two types of attributes: `name` (attribute remote control command name) and `value` (attribute command parameter value). `name` describes the name of the remote control command, and `value` describes the content of the command parameter. The sub-element command content `SJContent` includes two types of attributes: `sate` (attribute applicable satellite) and `sjId` (attribute data block identifier). `sate` describes the satellite to which the sub-element command content applies, and `sjId` describes the unique identifier of the sub-element command content. The sub-element execution completion criterion set `EventCompletes` includes the next-level sub-element execution completion criterion `EventComplete`, which describes the basis for determining command execution completion. The sub-element execution completion criterion `EventComplete` includes two types of attributes: `count` (attribute execution completion telemetry check count) and `timeOuts` (attribute execution completion telemetry check duration). `count` describes the number of telemetry checks required for command execution completion, and `timeOuts` describes the duration of the telemetry check.

[0038] S103: Parse the structured XML file, perform format and logic checks, and generate an executable job plan.

[0039] Specifically, after generating the complex but structurally sound XML file as described in the preceding steps, it is then input into the parsing module. The system first performs format validation on the XML file according to predefined schema rules corresponding to Table 3, ensuring that its elements and attributes conform to the specifications. After successful validation, the system performs logical validation, such as checking whether the satellite designations referenced in the Mission are within a reasonable range and whether the time defined in ExeTime will conflict with other tasks. After passing both validations, the system parses the XML file into internal instruction sequence objects and, combined with the actual telemetry and control plan, finally compiles and generates a work plan with a clear timeline, complete instruction parameters, and the ability to directly drive the commanding equipment.

[0040] S104: Within the actual telemetry and control arc, commands are automatically or semi-automatically sent to the satellite based on the triggering conditions defined in the structured XML file and the executable work plan. That is, after the satellite enters the predetermined telemetry and control arc, the work plan generated in the previous step is loaded through the work sequence execution unit. It monitors mission time or external events in real time. When the triggering condition of a command in the work plan (such as arrival absolute time, telemetry criteria met, etc.) is met, the system can, according to the configuration, either manually confirm (semi-automatic mode) or directly (fully automatic mode) send the command to the satellite, thereby completing the entire closed-loop automatic command sending process.

[0041] Figure 3 This invention illustrates a multi-satellite automatic command device 100 based on XML, according to another embodiment of the present invention. The device 100 includes: a telemetry and control task planning unit 10, an execution sequence design unit 20, a job plan generation unit 30, and a job sequence execution unit 40, wherein: The telemetry and control mission planning unit 10 is used to plan multi-satellite telemetry and control missions based on the multi-satellite flight control mission objectives and resource constraints; the execution sequence design unit 20 is used to generate specific, executable instruction sequences based on the flight control programs of the multi-satellite satellites in each telemetry and control arc segment, combined with the satellite telemetry parameter table and remote control instruction table, and convert them into structured XML files; the job plan generation unit 30 is used to parse the structured XML files, perform format and logic checks, and generate executable job plans; the job sequence execution unit 40 is used to automatically or semi-automatically send instructions within the actual telemetry and control arc segment according to the triggering conditions defined in the structured XML file.

[0042] The specific implementation and operation process of each module in the system 100 described in this embodiment can be understood by referring to the relevant descriptions in the foregoing method embodiments, and all of them can achieve the functions and effects achieved by the corresponding method steps. For the sake of simplicity and to avoid repetition, they will not be described again here.

[0043] In summary, this invention provides a multi-satellite automatic command transmission method, apparatus, computer equipment, and storage medium based on XML. It standardizes and carries the complex "event-criteria-command" control logic in multi-satellite flight control through a carefully defined hierarchical structured XML file. This technique transforms discrete command information, which originally relied on manual judgment and satellite-by-satellite configuration, into a standardized machine language that the system can automatically parse, verify, and execute. This method fundamentally solves the technical problems of high configuration workload and high error rate due to differences in multi-satellite parameters, inefficient command transmission processes lacking automation rules, and difficulty in precise coordination between multiple satellites. Ultimately, it achieves automation, standardization, and high reliability in multi-satellite flight control mission command transmission, significantly improving mission execution efficiency in the aerospace telemetry and control field.

[0044] This invention also provides a computer-readable storage medium for storing a computer program for executing the aforementioned XML-based multi-star automatic command method. For example, computer program instructions, when executed by a computer, can invoke or provide the methods and / or technical solutions according to this application through the operation of the computer. The program instructions for invoking the methods of this application may be stored in a fixed or removable storage medium, and / or transmitted via data streams in broadcast or other signal carrying media, and / or stored in the storage medium of a computer device operating according to the program instructions. Here, according to one embodiment of this application, it includes a... Figure 4 The computer device 400 shown preferably includes a memory 200 for storing computer programs and a processor 300 for executing computer programs. When the computer program is executed by the processor 300, the computer device 400 is triggered to execute the methods and / or technical solutions based on the foregoing embodiments.

[0045] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0046] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of the present invention is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0047] Of course, the present invention may have other various embodiments. Without departing from the spirit and essence of the present invention, those skilled in the art can make various corresponding changes and modifications according to the present invention, but these corresponding changes and modifications should all fall within the protection scope of the appended claims.

Claims

1. A multi-star automatic command sending method based on XML, characterized in that, Including: Standardized steps for telemetry, tracking, and command (TT&C) missions: Plan multi-satellite TT&C missions based on the objectives and resource constraints of the multi-satellite flight control mission; Command sequence design steps: Based on the flight control programs of multiple satellites in each telemetry and control arc, combined with the satellite telemetry parameter table and remote control command table, generate an executable command sequence and convert the command sequence into a structured XML file; The steps for generating a work plan are as follows: parse the structured XML file, perform format and logic checks, and generate an executable work plan. Operation sequence execution steps: Within the actual telemetry and control arc segment, instructions are automatically or semi-automatically sent to the satellite based on the triggering conditions defined in the structured XML file and the executable operation plan.

2. The method according to claim 1, characterized in that, The structured XML file includes a root element, which is a root element model task used to describe relevant information about a specific task; The root element model task includes two types of attributes: attribute task code and attribute task name; the attribute task code is used to describe the task or task group code; the attribute task name is used to describe the task or task group name information; The root element model task includes a sub-element and is defined as a sub-element flight procedure set, which is used to describe the flight control procedure set information.

3. The method according to claim 2, characterized in that, The sub-element flight procedure set includes three types of sub-elements at the next level: sub-element key event identifier set, sub-element injected data type set, and sub-element sub-flight procedure; the sub-element key event identifier set is used to describe the key event identifier set information; the sub-element injected data type set is used to describe the injected data corresponding list set information; and the sub-element sub-flight procedure is used to describe the sub-flight control program information.

4. The method according to claim 3, characterized in that, The set of key event identifiers for child elements includes key event identifiers for the next level of child elements, and the key event identifiers for child elements are used to describe key events; the key event identifiers for child elements include attribute key event names, and the attribute key event names are used to describe the name of the key event; The set of sub-element injected data types includes the sub-element injected data types of the next level. The sub-element injected data types are used to describe the injected data type information. The sub-element injected data types include two types of attributes: attribute injected data name and maximum number of attribute injected data blocks. The attribute injected data name is used to describe the name of the injected data, and the maximum number of attribute injected data blocks is used to describe the maximum number of data blocks injected in one processing. The sub-element sub-flight procedure includes the next-level sub-element normal flight control procedure and the sub-element fault handling procedure. The sub-element normal flight control procedure describes the normal flight control procedure; the sub-element fault handling procedure describes the abnormal flight control procedure; the sub-element sub-flight procedure includes two types of attributes: attribute telemetry and control circle sub-code and attribute satellite code set. The attribute telemetry and control circle sub-code describes the telemetry and control circle sub-code, and the attribute satellite code set describes the satellites to which the sub-flight control procedure is applicable.

5. The method according to claim 4, characterized in that, The sub-element normal flight control procedure includes a first sub-element event at the next level, which describes the events in the sub-flight control procedure; the sub-element normal flight control procedure includes an attribute normal flight control procedure name, which describes the event name; The sub-element fault handling procedure further includes a second sub-element event at the next level, which is used to describe events in the sub-flight control procedure; the sub-element fault handling procedure includes two types of attributes: attribute fault handling procedure code and attribute fault handling procedure name. The attribute fault handling procedure code is used to describe the fault handling procedure number, and the fault handling procedure name is used to describe the fault handling procedure name.

6. The method according to claim 5, characterized in that, The first sub-element event includes the execution and sending time of the next-level sub-element, the set of execution condition criteria for the sub-element, the sub-element instruction, and the set of execution completion criteria for the sub-element. The execution and sending time of the sub-element describes the event's time constraints. The set of execution condition criteria for the sub-element describes the event's execution condition criteria. The sub-element instruction describes the event-related instructions. The set of execution completion criteria for the sub-element describes the event's execution result criteria. The first sub-element event includes three types of attributes: attribute encryption status, attribute blind transmission status, and attribute event name. The attribute encryption status describes the confidentiality status of the sub-flight control program. The attribute blind transmission status describes the event's emergency attributes. The attribute event name describes the event name.

7. The method according to claim 6, characterized in that, The set of sub-element execution condition criteria includes the sub-element execution condition criteria of the next level. The sub-element execution condition criteria are used to describe the event execution condition criteria. The sub-element execution condition criteria include two types of attributes: the number of telemetry readings of the attribute execution condition and the duration of the telemetry readings of the attribute execution condition. The number of telemetry reads for the attribute execution condition is used to describe the number of frames required for the expression to be successfully judged, and the telemetry read duration for the attribute execution condition is used to describe the longest judgment time of the expression. The sub-element instruction includes the next-level sub-element instruction sending conditions, the sub-element remote control instruction code, and the sub-element instruction content; the sub-element instruction sending conditions describe the prerequisites for instruction sending; the sub-element remote control instruction code describes the unique code and instruction sending attributes of the instruction; the sub-element instruction content describes the data content carried by the instruction; the sub-element remote control instruction code includes two types of attributes: attribute remote control instruction name and attribute instruction parameters, the attribute remote control instruction name describes the name of the remote control instruction, and the attribute instruction parameters describe the content of the instruction parameters; the sub-element instruction content includes two types of attributes: attribute applicable satellite and attribute data block identifier, the attribute applicable satellite describes the satellites to which the sub-element instruction content applies, and the attribute data block identifier describes the unique identifier of the sub-element instruction content; The set of criteria for sub-element execution completion includes the criteria for sub-element execution completion at the next level. The criteria for sub-element execution completion are used to describe the basis for determining the completion of instruction execution. The criteria for sub-element execution completion include two types of attributes: the number of telemetry reads for attribute execution completion and the duration of telemetry reads for attribute execution completion. The number of telemetry reads for attribute execution completion is used to describe the number of telemetry reads for instruction execution completion, and the duration of telemetry reads for attribute execution completion is used to describe the duration of telemetry reads for execution completion.

8. A multi-star automatic command issuing device based on XML, characterized in that, The device includes: a measurement and control task planning unit, an execution sequence design unit, a job plan generation unit, and a job sequence execution unit, wherein: The telemetry, tracking, and command (TT&C) mission planning unit is used to plan multi-satellite TT&C missions based on the objectives and resource constraints of the multi-satellite flight control mission. The execution sequence design unit is used to generate specific, executable instruction sequences based on the flight control programs of multiple satellites in each telemetry and control arc, combined with satellite telemetry parameter tables and remote control instruction tables, and convert them into structured XML files. The job plan generation unit is used to parse the structured XML file, perform format and logic checks, and generate an executable job plan. The operation sequence execution unit is used to automatically or semi-automatically send instructions within the actual measurement and control arc segment according to the triggering conditions defined in the structured XML file.

9. A computer device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the XML-based multi-star automatic command method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that executes the XML-based multi-star automatic command method as described in any one of claims 1 to 7.

Images