Spacecraft nominal plan automation design method, system, device, and storage medium

Abstract

This invention discloses an automated design method, system, device, and storage medium for spacecraft nominal plans. The method includes: automatically converting the spacecraft's flight program into an initial nominal plan based on an instruction and injection database; selecting a corresponding nominal plan from a pre-established set of nominal plans according to the spacecraft's actual operating conditions, and fusing it with the initial nominal plan to generate a fused nominal plan; reading the spacecraft's telemetry, tracking, and command (TT&C) arc segments and arc segment obstruction times, and automatically generating instruction transmission times within the TT&C and TT&C arc segments based on the instruction transmission intervals and instruction attributes in the fused nominal plan, while avoiding arc segment obstruction times, to obtain an updated nominal plan; and verifying the correctness of the instruction codes, instruction names, and offsets in the updated nominal plan. This invention improves the efficiency and accuracy of nominal plan design, better meets the needs of spacecraft flight control missions, and provides strong technical support for the stable operation of spacecraft.

Description

Technical Field

[0001] This invention relates to the field of spacecraft telemetry and control technology, and in particular to an automated design method, system, equipment and storage medium for spacecraft nominal plans. Background Technology

[0002] In space station flight control missions, nominal plan design is a crucial step, serving as the foundation for the spacecraft to execute various commands and operations. The formulation of the nominal plan requires comprehensive consideration of various factors, including the telemetry and control requirements of each mission system, the mission implementation requirements of the overall flight control scheme, the status of space-based telemetry and control network resources, and the theoretical orbit. This results in a set of flight control events and their implementation constraints during the mission. By combining the nominal plan with actual orbital information, a detailed operational plan can be further generated to guide the space station's flight control operations.

[0003] However, as the complexity and scale of space station missions continue to increase, the limitations of traditional nominal plan design methods are becoming increasingly apparent. Currently, the generation of nominal plans typically relies on manual conversion of flight procedures into plans, combined with the scheduling of command transmissions using telemetry and control resources. This approach is not only inefficient but also prone to introducing errors through manual operation, thus affecting the accuracy and reliability of the plans.

[0004] Furthermore, space station missions include numerous repetitive flight control tasks, such as orbit control and solar panel activation. While the flight procedures for these tasks exhibit certain regularities, the significant differences in flight procedures for different engine orbit control systems necessitate the design of separate nominal plans. Currently, fine-tuning of these nominal plans still requires manual intervention, necessitating a reconsideration of all constraints each time the mission is used. Manual fine-tuning is not only time-consuming and labor-intensive but also prone to errors due to incomplete or inadequate considerations, thereby affecting the accuracy of space station flight control missions.

[0005] Therefore, there is an urgent need to provide a technical solution to address the above problems. Summary of the Invention

[0006] To address the aforementioned technical problems, this invention provides an automated design method, system, device, and storage medium for spacecraft nominal plans.

[0007] In a first aspect, the present invention provides an automated design method for spacecraft nominal plans, the technical solution of which is as follows:

[0008] Establish an instruction and injection database to store and manage remote control instructions, programmable instructions, instruction chains, and injection data;

[0009] Based on the instructions and the injected database, the spacecraft's flight program is automatically converted into an initial nominal plan. The automatic conversion includes: converting the instruction information format in the flight program, filling in the instruction duration according to the instructions and the injected database, converting the instruction sending interval into an offset, and automatically filling in the event type, target identifier, number of commands, and relay identifier.

[0010] Based on the actual operating conditions of the spacecraft, a corresponding nominal operating condition plan is selected from a pre-established set of nominal plans, and the nominal operating condition plan is merged with the initial nominal plan to generate a merged nominal plan;

[0011] The telemetry, tracking, and command (TT&C) arc and arc blockage time of the spacecraft are read. Based on the command transmission interval and command attributes in the fusion nominal plan, and under the condition of avoiding the arc blockage time, the command transmission time is automatically generated within the TT&C arc to obtain the updated nominal plan.

[0012] The updated nominal plan is automatically compared with the instructions and the injected database to verify the correctness of the instruction code, instruction name and offset in the updated nominal plan.

[0013] The beneficial effects of the spacecraft nominal plan automated design method of the present invention are as follows:

[0014] The method of this invention can solve the problems of low efficiency and error-proneness of traditional manual methods. At the same time, it optimizes the generation of nominal plans for repetitive tasks, reduces the complexity and workload of manual fine-tuning, and improves the efficiency and accuracy of nominal plan design, thereby better meeting the needs of spacecraft flight control missions and providing strong technical support for the stable operation of spacecraft.

[0015] Based on the above scheme, the spacecraft nominal plan automated design method of the present invention can be further improved as follows.

[0016] In one alternative embodiment, the instruction and injection database includes: an instruction database and an injection database; the step of establishing the instruction and injection database for storing and managing remote control instructions, programmable instructions, instruction chains, and injection data includes:

[0017] Establish an instruction database for storing remote control instructions and programmable instructions, the instruction database including instruction chain duration;

[0018] An injection database is established for storing injection data, and the injection database is used to receive and manage newly generated injection data.

[0019] In one alternative approach, the step of automatically converting the spacecraft's flight procedure into an initial nominal plan based on the instructions and the injected database includes:

[0020] Read the instruction codes and instruction numbers from the spacecraft's flight program, and convert the format of the instruction codes and instruction numbers into the instruction information format required by the nominal plan;

[0021] The instruction chain duration is obtained from the instruction database according to the instruction code, and the instruction chain duration is filled with the nominal planned instruction duration;

[0022] Read the command transmission interval in the flight procedure and convert the command transmission interval into an offset identified by the nominal plan;

[0023] The instruction type is identified based on the instruction code, and the event type of the nominal plan is filled in based on the instruction type;

[0024] Fill in the target identifier of the nominal plan according to the instruction code;

[0025] The number of commands to be issued in the nominal plan is filled based on the command type;

[0026] According to the current working section filling nominal plan, the replacement identification mark;

[0027] The initial nominal plan is generated by integrating the converted instruction information format, the filled instruction duration, the converted offset, and the filled event type, target identifier, number of commands issued, and proxy identifier.

[0028] In one optional approach, the step of selecting a corresponding nominal operating condition plan from a pre-established set of nominal plans based on the actual operating conditions of the spacecraft, and merging the nominal operating condition plan with the initial nominal plan to generate a merged nominal plan includes:

[0029] Identify the repetitive flight control mission currently being performed by the spacecraft, and obtain the pre-established set of nominal plans corresponding to the repetitive flight control mission;

[0030] Select a matching nominal plan for the operating condition from the set of nominal plans based on the actual operating conditions of the spacecraft;

[0031] The nominal working condition plan and the initial nominal plan are fused together using instruction sequences and parameter configurations to generate the fused nominal plan.

[0032] In one alternative approach, the step of reading the spacecraft's telemetry, tracking, and command (TT&C) arc segment and arc segment blocking time, and automatically generating command transmission times within the TT&C arc segment while avoiding the arc segment blocking time, to obtain an updated nominal plan, includes:

[0033] Obtain each tracking and control arc segment of the spacecraft and the corresponding arc segment blocking time;

[0034] Calculate the available time period for each tracking arc segment after deducting the corresponding arc segment's obstruction time;

[0035] The command timing relationship for each flight control event is determined based on the command transmission interval in the fusion nominal plan;

[0036] Identify the command attributes of each flight control event in the fusion nominal plan;

[0037] Based on all available time periods and the command attributes of each flight control event, the command sequence of each flight control event is assigned to the corresponding telemetry and tracking arc segment, and the arc segment blockage time in each telemetry and tracking arc segment is avoided during the assignment process to obtain the assignment result;

[0038] Adjust the offset of the corresponding instruction according to the allocation result, and generate the updated nominal plan based on the adjusted instruction timing relationship and offset.

[0039] In an optional approach, the step of allocating the instruction sequence of each flight control event to the corresponding telemetry and tracking arc segment based on all available time periods and the instruction attributes of each flight control event, and avoiding the arc blockage time in each telemetry and tracking arc segment during the allocation process, to obtain the allocation result, includes:

[0040] The instruction sequence of flight control events with the instruction attribute of splittable mode is allocated in chronological order to the available time periods of multiple consecutive telemetry and tracking arcs;

[0041] Assign the complete command sequence of a flight control event with an indivisible command attribute to the available time period of a single telemetry and tracking arc;

[0042] During the allocation process, ensure that the sending time of all instructions avoids the arc occlusion time in each telemetry and tracking arc segment;

[0043] When the total duration of the command sequence of a flight control event exceeds the available time period of a single telemetry and tracking arc, the command sequence of the splittable mode is segmented across arcs.

[0044] Record the final assigned telemetry and tracking arc segment for each instruction and the specific transmission time within the corresponding telemetry and tracking arc segment to form the allocation result.

[0045] In one alternative approach, the step of automatically comparing the updated nominal plan with the instructions and the injection database to verify the correctness of the instruction codes, instruction names, and offsets in the updated nominal plan includes:

[0046] Using the instruction codes in the updated nominal plan, obtain the corresponding instruction name and instruction chain duration from the instruction database;

[0047] Verify whether the instruction code in the updated nominal plan has a corresponding record in the instruction database; compare and verify the instruction name in the updated nominal plan with the corresponding instruction name obtained from the instruction database; check whether the offset in the updated nominal plan meets the instruction chain duration requirement of the corresponding instruction obtained from the instruction database;

[0048] When the instruction code in the updated nominal plan does not have a corresponding record in the instruction database, an instruction code error message is generated; when the instruction name in the updated nominal plan is inconsistent with the corresponding instruction name obtained from the instruction database, an instruction name error message is generated; when the offset in the updated nominal plan does not meet the instruction chain duration requirement of the corresponding instruction obtained from the instruction database, an offset error message is generated.

[0049] Secondly, this invention provides an automated design system for spacecraft nominal plans, the technical solution of which is as follows:

[0050] It includes: a creation module, a transformation module, a fusion module, a generation module, and a verification module;

[0051] The establishment module is used to: establish an instruction and injection database for storing and managing remote control instructions, program control instructions, instruction chains and injection data;

[0052] The conversion module is used to: automatically convert the spacecraft's flight program into an initial nominal plan based on the instructions and the injection database. The automatic conversion includes: converting the instruction information format in the flight program, filling in the instruction duration according to the instructions and the injection database, converting the instruction sending interval into an offset, and automatically filling in the event type, target identifier, number of commands, and relay identifier.

[0053] The fusion module is used to: select the corresponding nominal operating plan from the pre-established nominal plan set according to the actual operating conditions of the spacecraft, and fuse the nominal operating plan with the initial nominal plan to generate a fused nominal plan;

[0054] The generation module is used to: read the telemetry, tracking, and command (TT&C) arc segment and arc segment obstruction time of the spacecraft; and, based on the command transmission interval and command attributes in the fused nominal plan, automatically generate command transmission time within the TT&C and tracking arc segment while avoiding the arc segment obstruction time, thereby obtaining an updated nominal plan.

[0055] The verification module is used to automatically compare the updated nominal plan with the instructions and the injected database to verify the correctness of the instruction code, instruction name and offset in the updated nominal plan.

[0056] The beneficial effects of the spacecraft nominal plan automated design system of the present invention are as follows:

[0057] The system of this invention can solve the problems of low efficiency and error-proneness of traditional manual methods. At the same time, it optimizes the generation of nominal plans for repetitive tasks, reduces the complexity and workload of manual fine-tuning, and improves the efficiency and accuracy of nominal plan design, thereby better meeting the needs of spacecraft flight control missions and providing strong technical support for the stable operation of spacecraft.

[0058] Thirdly, the technical solution of an electronic device according to the present invention is as follows:

[0059] It includes a memory, a processor, and a program stored in the memory and running on the processor, wherein the processor executes the program to implement the steps of the spacecraft nominal plan automated design method of the present invention.

[0060] Fourthly, the technical solution of a computer-readable storage medium provided by the present invention is as follows:

[0061] The computer-readable storage medium stores instructions that, when read, cause the computer-readable storage medium to perform the steps of the spacecraft nominal plan automated design method of the present invention.

[0062] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0063] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0064] Figure 1 This is a flowchart illustrating an embodiment of an automated design method for spacecraft nominal plans according to the present invention.

[0065] Figure 2 This is a schematic diagram of the initial nominal plan;

[0066] Figure 3 A schematic diagram of the page for selecting the nominal plan of the operating condition corresponding to the point frequency power-on flight control event;

[0067] Figure 4 This is a schematic diagram of the interface for the nominal plan automation design;

[0068] Figure 5 This is a schematic diagram of an embodiment of the automated design system for spacecraft nominal planning according to the present invention;

[0069] Figure 6 This is a schematic diagram of an embodiment of an electronic device according to the present invention. Detailed Implementation

[0070] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0071] Figure 1 This diagram illustrates a flowchart of an embodiment of an automated design method for spacecraft nominal plans provided by the present invention. This automated design method can be executed by electronic devices such as terminal devices or servers. The terminal device can be any fixed or mobile terminal, such as user equipment (UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, vehicle-mounted device, or wearable device. The server can be a single server or a server cluster consisting of multiple servers. Any electronic device can implement the automated design method for spacecraft nominal plans by having its processor call computer-readable instructions stored in its memory. Figure 1 As shown, it includes the following steps:

[0072] S1. Establish an instruction and injection database to store and manage remote control instructions, programmable instructions, instruction chains, and injection data.

[0073] The instruction and injection database refers to a database used for centralized storage and management of various instructions and data required for spacecraft flight control. Remote control instructions are sent from ground control stations to the spacecraft to trigger immediate action; for example, the "equipment power-on" instruction used to start equipment in a frequency-based power-on mission. Programmed instructions are programmed instructions automatically executed by the spacecraft according to predetermined times or conditions; for example, the engine ignition instruction automatically executed by the spacecraft according to predetermined times in an orbital control mission. Instruction chains are sequences of instructions composed of multiple remote control or programmed instructions combined in a specific order and timing; for example, a sequence of instructions sent sequentially in an orbital control mission, such as "engine pre-charge," "ignition preparation," and "engine ignition." Injected data refers to data blocks sent to the spacecraft to update its internal parameters or programs; for example, the code rate parameter data packets that need to be injected before frequency-based power-on.

[0074] S2. Based on the instructions and the injected database, the spacecraft's flight program is automatically converted into an initial nominal plan. The automatic conversion includes: converting the instruction information format in the flight program, filling in the instruction duration according to the instructions and the injected database, converting the instruction sending interval into an offset, and automatically filling in the event type, target identifier, number of commands, and relay identifier.

[0075] Here, "spacecraft" refers to a man-made spacecraft operating in space orbit; for example, a space station complex. "Flight procedure" refers to a text or document describing all operations and timing relationships required for a specific mission phase of the spacecraft; for example, a Word document describing the entire process of a point-frequency power-on mission, including command codes, instructions, and transmission intervals. "Initial nominal plan" refers to a draft nominal plan generated automatically from the flight procedure, before operational condition adaptation and telemetry and control resource orchestration; for example, an Excel plan table containing basic instruction information but without specific code rate instructions, obtained by converting the point-frequency power-on flight procedure. "Instruction information format" refers to the standardized representation of command codes and instructions specified in the nominal plan; for example, converting the "DPKJ" code in the flight procedure to the "DP_KJ_001" format required by the nominal plan. "Instruction duration" refers to the total time required for the instruction chain to execute from start to finish; for example, a point-frequency power-on instruction chain requires 2.5 seconds from transmission to completion. Command transmission interval refers to the time interval between two adjacent commands specified in the flight procedure; for example, in a frequency-based power-on mission, the interval between the commands "equipment power-on" and "set code rate" is 30 seconds. Offset refers to the relative time difference based on a reference time in the nominal plan; for example, using the flight control event start time T0 as a reference, a 30-second command transmission interval is converted to an offset of "+30". Event type refers to the classification of flight control events according to command characteristics; for example, a frequency-based power-on event is classified as "equipment control". Target identifier refers to the code in the nominal plan that identifies the target of the command; for example, the target identifier for a frequency-based power-on command is "core module communication system". Command number refers to the number of times the same command needs to be transmitted as specified in the nominal plan; for example, to ensure reliability, the number of times a frequency-based power-on command needs to be transmitted is set to 2. Relay identifier refers to a marker indicating whether a command needs to be transmitted via a relay satellite; for example, based on the visibility of the current working module and the tracking station, the relay identifier for a frequency-based power-on command is set to "relay required".

[0076] S3. Select the corresponding nominal operating plan from the pre-established nominal plan set according to the actual operating conditions of the spacecraft, and merge the nominal operating plan with the initial nominal plan to generate a merged nominal plan.

[0077] Here, "actual operating condition" refers to the actual working state and parameter configuration of the spacecraft during mission execution; for example, the code rate parameter X1 actually used by the spacecraft in a point-frequency power-on mission. "Nominal plan set" refers to a set of pre-generated nominal plans covering various possible operating conditions for a specific repetitive flight control mission; for example, a set of point-frequency power-on nominal plans including code rates X1 and X2. "Operating condition nominal plan" refers to the nominal plan in the nominal plan set corresponding to a specific actual operating condition; for example, the nominal plan corresponding to code rate X1 in a point-frequency power-on mission. "Fused nominal plan" refers to the nominal plan formed by integrating the initial nominal plan with the operating condition nominal plan; for example, the complete plan generated by fusing the initial point-frequency power-on nominal plan with the code rate X1 operating condition nominal plan.

[0078] S4. Read the telemetry, tracking, and command (TT&C) arc segment and arc segment obstruction time of the spacecraft. Based on the command transmission interval and command attributes in the fusion nominal plan, and under the condition of avoiding the arc segment obstruction time, automatically generate the command transmission time within the TT&C and tracking arc segment to obtain the updated nominal plan.

[0079] The tracking and control arc segment refers to the continuous time period during which the ground tracking and control station can track and control the spacecraft; for example, the visible arc segment H1 of the space station from 14:00 to 14:40 Beijing time. The arc segment obscuring time refers to the time period within the tracking and control arc segment during which communication is interrupted due to the spacecraft being obscured by celestial bodies; for example, during 14:10 to 14:12 within arc segment H1, communication is impossible because the space station's tracking antenna is obscured by the solar array of a certain module. The command attribute refers to the characteristic that indicates whether a command sequence can be split between different arc segments; for example, marking a frequency-based power-on command sequence as "indivisible". The command transmission time refers to the absolute transmission time determined for each command in the nominal plan after considering tracking and control resource constraints; for example, considering arc segment H1 and obscuring time, scheduling the frequency-based power-on command to be transmitted at 14:05:00. The updated nominal plan refers to the final nominal plan after the completion of the telemetry and control resource orchestration and the determination of the transmission time of all instructions; for example, the executable plan version in the point frequency power-on task where the time of all instructions has been determined.

[0080] S5. Automatically compare the updated nominal plan with the instructions and the injected database to verify the correctness of the instruction code, instruction name and offset in the updated nominal plan.

[0081] The technical solution of this embodiment can solve the problems of low efficiency and error-proneness of traditional manual methods. At the same time, it optimizes the generation of nominal plans for repetitive tasks, reduces the complexity and workload of manual fine-tuning, and improves the efficiency and accuracy of nominal plan design, thereby better meeting the needs of spacecraft flight control missions and providing strong technical support for the stable operation of spacecraft.

[0082] In one optional embodiment, the instruction and injection database includes: an instruction database and an injection database; S1 specifically includes:

[0083] S11. Establish the instruction database for storing remote control instructions and programmable instructions, the instruction database including the duration of the instruction chain.

[0084] The instruction database refers to a database specifically used to store remote control instructions and programmable instructions; for example, a database that stores instructions such as "device power on" and "set code rate" required for point-frequency power-on.

[0085] S12. Establish the injection database for storing injection data, the injection database being used to receive and manage newly generated injection data.

[0086] The injection database refers to a database specifically used to store injection data; for example, a database that stores the point frequency power-on code rate parameters X1 and X2.

[0087] Among the above-mentioned optional methods, further standardization of instruction data management and improvement of query and usage efficiency are achieved by dividing the instruction and injection database into an instruction database and an injection database, thereby optimizing the data classification and storage structure.

[0088] In one alternative approach, S2 specifically includes:

[0089] S21. Read the instruction code and instruction number from the spacecraft's flight program, and convert the format of the instruction code and instruction number into the instruction information format required by the nominal plan.

[0090] In this context, the instruction code refers to the simplified name used in the flight procedure to identify a specific instruction; for example, the instruction code for "device power-on" in a frequency-based power-on mission is "DP_SBKJ". The instruction code refers to the unique encoding of the instruction in the database; for example, the code for the "device power-on" instruction in a frequency-based power-on mission is "OC_DEV_START" in the instruction database.

[0091] S22. Obtain the instruction chain duration from the instruction database according to the instruction code, and fill the instruction chain duration with the nominal planned instruction duration.

[0092] The instruction chain duration refers to the total time required for a specific instruction chain to execute from start to finish; for example, the duration of the frequency power-on instruction chain recorded in the instruction database is 5.2 seconds.

[0093] S23. Read the instruction transmission interval in the flight procedure and convert the instruction transmission interval into an offset identified by the nominal plan.

[0094] S24. Identify the instruction type according to the instruction code, and fill in the event type of the nominal plan based on the instruction type.

[0095] S25. Fill in the target identifier of the nominal plan according to the instruction code, fill in the number of orders issued in the nominal plan according to the instruction type, and fill in the transmission identifier of the nominal plan according to the current working segment.

[0096] The currently working module refers to the module in a spacecraft that is currently responsible for establishing communication with the ground and executing commands; for example, the "core module" currently on duty in a space station mission.

[0097] S26. The initial nominal plan is generated by integrating the converted instruction information format, the filled instruction duration, the converted offset, and the filled event type, the target identifier, the number of commands issued, and the proxy identifier.

[0098] Specifically: 1) Read the command codes and instruction symbols from the spacecraft's flight program, convert them into the command information format required by the nominal plan, and fill them into the corresponding positions in the nominal plan. 2) Read the command transmission intervals from the flight program, convert them into the offset format recognized by the nominal plan, and fill them into the offset positions in the nominal plan; set the offset corresponding to the start time T0, T1...Tn of each flight control event to 0, and convert the remaining interval times into the offset format recognized by the nominal plan and fill them into the offset positions. 3) Obtain the command chain duration from the command database according to the command code, and fill the command chain duration with the command duration of the nominal plan; fill the remote control commands with fixed values, and for programmable commands and injected data, distinguish between high-pass injected data and serial injected data and fill them with the corresponding fixed values ​​respectively. 4) Identify the command type based on the command symbol, and fill the event type of the nominal plan according to the command type; fill the target identifier of the nominal plan according to the command symbol; fill the number of commands issued in the nominal plan according to the command type; fill the transmission identifier of the nominal plan according to the current working module. 5) By integrating the converted instruction information format, the filled instruction duration, the converted offset, and the filled event type, target identifier, command issuance count, and proxy identifier, an initial nominal plan is generated, such as... Figure 2 As shown.

[0099] Among the above-mentioned optional methods, the initial nominal plan can be generated through an automated process to reduce manual intervention, improve the efficiency of plan generation, and ensure the uniformity of instruction information format and data integrity.

[0100] In one alternative approach, S3 specifically includes:

[0101] S31. Identify the repetitive flight control mission currently being performed by the spacecraft, and obtain the pre-established nominal plan set corresponding to the repetitive flight control mission.

[0102] Among them, repetitive flight control missions refer to similar flight control operations that need to be repeatedly performed during the operation of a spacecraft; for example, the orbit maintenance control missions that the space station performs regularly.

[0103] S32. Select a matching nominal plan for the operating condition from the set of nominal plans based on the actual operating conditions of the spacecraft.

[0104] like Figure 3 As shown, taking the point-frequency power-on flight control event as an example: it is identified that there are two operating conditions in the point-frequency power-on nominal plan, namely, the code rate setting after power-on includes two parameter configurations: X1 and X2; the instructions corresponding to the two code rate settings are added to the point-frequency power-on nominal plan set, with the instruction corresponding to X1 being XXXX1 and the instruction corresponding to X2 being XXXX2; when in use, if the actual power-on code rate is X1, the operating condition nominal plan corresponding to the code rate parameter X1 is selected from the point-frequency power-on nominal plan set.

[0105] S33. The nominal working condition plan and the initial nominal plan are fused together by the instruction sequence and parameter configuration to generate the fused nominal plan.

[0106] In this context, the instruction sequence refers to a group of instructions arranged in a specific order within a flight control event; for example, the "equipment power-on - self-test - parameter setting - power-on" instruction sequence in a point-frequency power-on flight control event. Parameter configuration refers to the specific parameter values ​​that need to be set when executing a flight control task; for example, configuring the code rate parameter to X1 in a point-frequency power-on task.

[0107] Among the above-mentioned optional methods, the ability of the nominal plan to adapt to complex working conditions can be further improved by merging the initial nominal plan with the nominal plan corresponding to the actual working conditions to generate a more accurate merged nominal plan.

[0108] In one alternative approach, S4 specifically includes:

[0109] S41. Obtain each tracking arc segment of the spacecraft and the corresponding arc segment obscuring time.

[0110] S42. Calculate the available time period for each tracking arc segment after deducting the corresponding arc segment's obstruction time.

[0111] The available time period refers to the actual time range that can be used for command transmission after deducting the arc segment obstruction time from the measurement and control tracking arc segment; for example, after deducting the 14:10-14:12 obstruction time from 14:00-14:40 of arc segment H1, we get two available time periods: 14:00-14:10 and 14:12-14:40.

[0112] S43. Determine the command timing relationship for each flight control event based on the command transmission interval in the fusion nominal plan.

[0113] In this context, a flight control event refers to a complete operational unit within the spacecraft's flight control; for example, frequency boosting is considered an independent flight control event. Command timing relationships refer to the relative time relationships between commands within a single flight control event; for example, in a frequency boosting event, the "set code rate" command is executed 30 seconds after the "power on device" command.

[0114] S44. Identify the instruction attributes of each flight control event in the fusion nominal plan.

[0115] The instruction attributes include: splittable mode and non-splittable mode.

[0116] S45. Based on all available time periods and the instruction attributes of each flight control event, the instruction sequence of each flight control event is assigned to the corresponding telemetry and tracking arc segment, and the arc segment blocking time in each telemetry and tracking arc segment is avoided during the assignment process to obtain the assignment result.

[0117] The allocation result refers to the arrangement scheme formed after assigning the command sequence of flight control events to specific telemetry and tracking arcs; for example, all the point frequency power-on command sequences are assigned to the time period of 14:05-14:08 in arc H1.

[0118] S46. Adjust the offset of the corresponding instruction according to the allocation result, and generate the updated nominal plan based on the adjusted instruction timing relationship and offset.

[0119] Among the above-mentioned optional methods, the scheduling of telemetry and control resources can be further optimized by avoiding the obscuration time and allocating the command sequence to the telemetry and control tracking arc in combination with the command attributes, thereby improving the reliability of the command sending arrangement.

[0120] In one alternative approach, S45 specifically includes:

[0121] The instruction sequence of flight control events with the instruction attribute of splittable mode is allocated chronologically into the available time periods of multiple consecutive telemetry and tracking arcs.

[0122] Assign the complete command sequence of a flight control event with an indivisible command attribute to the available time period of a single telemetry and tracking arc.

[0123] During the allocation process, ensure that the sending time of all instructions avoids the arc occlusion time in each telemetry and tracking arc segment.

[0124] When the total duration of the instruction sequence of a flight control event exceeds the available time period of a single telemetry and tracking arc, the instruction sequence of the splittable mode is segmented across arcs.

[0125] Record the final assigned telemetry and tracking arc segment for each instruction and the specific transmission time within the corresponding telemetry and tracking arc segment to form the allocation result.

[0126] like Figure 4 As shown in the example:

[0127] 1) Read the spacecraft's telemetry and tracking arc segments and arc segment obstruction time, and calculate the available time period for each telemetry and tracking arc segment after deducting the corresponding arc segment obstruction time.

[0128] 2) Each flight control event contains a sequence of instructions. Each flight control event has a start time T0, T1...Tn. The instruction transmission time within the flight control event is determined based on the start time and instruction transmission interval, namely T0, T0+x1...T0+xn; T1, T1+y1...T1+yn; Tn, Tn+z1...Tn+zn.

[0129] 3) Identify the command attributes of each flight control event. Command attributes are divided into splittable and non-splittable modes. Splittable mode indicates that the command sequence has low correlation and can be sent separately in different telemetry and tracking arcs. Non-splittable mode indicates that the command sequence has high correlation and must be sent completely in one telemetry and tracking arc.

[0130] 4) For flight control events with a splittable command attribute, allocation begins from the first telemetry and tracking arc H1. The available time period Q1 of arc H1 is compared with the total duration xn of the flight control event F1 command sequence. If Q1 is less than xn, the commands within the Q1 time period are arranged within arc H1, while avoiding the obstruction time of arc H1. The total duration of the remaining command sequence becomes xn minus Q1. The available time period Q2 of the next arc H2 is then compared with the total duration of the remaining command sequence. If Q2 is less than the total duration of the remaining command sequence, the commands within the Q2 time period are arranged within arc H2, while avoiding the obstruction time of arc H2. The command offset is adjusted, setting the offset of the first command within arc H2 to 0, and adjusting the offsets of subsequent commands based on the relative time difference. This process is repeated until all commands are allocated.

[0131] 5) For flight control events with a splittable instruction attribute, if the available time period Q1 of arc H1 is greater than or equal to the total duration xn of the instruction sequence of flight control event F1, then all instructions of flight control event F1 are arranged within arc H1, while avoiding the obstruction time of arc H1; then compare the remaining available time period Q1-xn of arc H1 with the total duration yn of the instruction sequence of the next flight control event F2. If Q1-xn is greater than or equal to yn, then all instructions of flight control event F2 are arranged within the remaining time period of arc H1, while avoiding the obstruction time of arc H1; if Q1-xn is less than yn, then the instruction sequence of flight control event F2 continues to be allocated according to the splittable mode logic described above.

[0132] 6) For flight control events with non-separable command attributes, allocation begins from the first telemetry and tracking arc H1. The available time period Q1 of arc H1 is compared with the total duration xn of the command sequence of flight control event F1. If Q1 is greater than or equal to xn, all commands of flight control event F1 are arranged within arc H1, while avoiding the obstruction time of arc H1. Then, the remaining available time period Q1-xn of arc H1 is compared with the total duration yn of the command sequence of the next flight control event F2. If Q1-xn is greater than or equal to yn, all commands of flight control event F2 are arranged within the remaining time period of arc H1, while avoiding the obstruction time of arc H1. If Q1-xn is less than yn, the available time period Q2 of the next arc H2 is compared with the total duration yn of the command sequence of flight control event F2. If Q2 is greater than or equal to yn, all commands of flight control event F2 are arranged within arc H2, while avoiding the obstruction time of arc H2. This process is repeated until all commands are allocated.

[0133] 7) During the allocation process, the transmission time of all commands avoids the arc blockage time within each telemetry and tracking arc segment. The final telemetry and tracking arc segment allocated to each command and the specific transmission time within that arc segment are recorded to form the allocation result.

[0134] 8) Adjust the offset of the corresponding instruction according to the allocation result, and generate an updated nominal plan based on the adjusted instruction timing relationship and offset.

[0135] Among the above optional methods, the instruction sequence allocation logic is further improved to support cross-segment segmentation and allocation of instruction sequences, ensuring the efficient execution of complex instruction sequences under the constraints of measurement and control resources.

[0136] In one alternative approach, S5 specifically includes:

[0137] S51. Obtain the corresponding instruction name and instruction chain duration from the instruction database using the instruction code in the updated nominal plan.

[0138] S52. Verify whether the instruction code in the updated nominal plan has a corresponding record in the instruction database; compare and verify the instruction name in the updated nominal plan with the corresponding instruction name obtained from the instruction database; check whether the offset in the updated nominal plan meets the instruction chain duration requirement of the corresponding instruction obtained from the instruction database.

[0139] S53. When the instruction code in the updated nominal plan does not have a corresponding record in the instruction database, an instruction code error message is generated; when the instruction name in the updated nominal plan is inconsistent with the corresponding instruction name obtained from the instruction database, an instruction name error message is generated; when the offset in the updated nominal plan does not meet the instruction chain duration requirement of the corresponding instruction obtained from the instruction database, an offset error message is generated.

[0140] The following are alarm messages generated by the system: **Instruction Code Error:** This refers to an alarm message generated when an instruction code in the nominal plan does not exist in the instruction database. For example, if the instruction code "OC_XXX_ERR" has no matching record in the database, the system will display "Instruction Code Error." **Name Error:** This refers to an alarm message generated by the system when the instruction name in the nominal plan does not match the corresponding instruction code record in the instruction database. For example, if the instruction code "OC_DEV_START" is named "Device Shutdown" in the plan but not "Device Power On" in the database, the system will display "Instruction Name Error." **Offset Error:** This refers to an alarm message generated by the system when the offset setting in the nominal plan does not meet the instruction chain duration requirement. For example, if an instruction offset is set to +2 seconds, but its preceding instruction chain requires 3 seconds to complete, the system will display "Insufficient Offset."

[0141] Among the above-mentioned optional methods, the nominal plan verification mechanism is further strengthened. By automatically comparing the updated nominal plan with the database, the correctness and consistency of the command code, name and offset are ensured, thereby guaranteeing the execution accuracy of the flight control mission.

[0142] The overall technical solution of this embodiment has the following technical effects:

[0143] 1) By establishing an instruction and injection database and realizing the automatic conversion of flight procedures to initial nominal plans based on the database, the problems of low efficiency and error-proneness in the traditional manual conversion process are solved. The automatic conversion process includes the standardized conversion of instruction information format, automatic filling of instruction duration, accurate conversion of instruction sending interval to offset, and automatic filling of event type, target identifier, number of commands and relay identifier, thus eliminating the error risk introduced by manual operation from the source.

[0144] 2) To address the challenge of frequent fine-tuning of nominal plans for repetitive flight control missions, a pre-established set of nominal plans and a working condition selection mechanism were constructed to achieve rapid response to different actual working conditions of spacecraft. The system can automatically select the matching working condition nominal plan based on the actual working conditions and integrate it with the initial nominal plan, which significantly improves the efficiency and adaptability of nominal plan generation and effectively reduces the workload and error probability of manual fine-tuning.

[0145] 3) In terms of the utilization of measurement and control resources, by reading the measurement and control tracking arc segment and arc segment occlusion time, and combining the command transmission interval and command attributes in the fusion nominal plan, the automatic generation and optimized arrangement of command transmission time are realized. Among them, the intelligent identification of command attributes ensures the reasonable allocation of command sequence in splittable and non-splittable modes, while automatically avoiding all arc segment occlusion times, making command time planning more intuitive and accurate, and greatly improving the utilization efficiency of measurement and control resources.

[0146] 4) By automating the comparison and verification of the updated nominal plan with the instructions and the injected database, a complete nominal plan verification mechanism has been established. This mechanism can perform multi-dimensional checks on the existence of instruction codes, the consistency of instruction names, and the matching degree between offsets and instruction chain durations, and generate corresponding error prompts. This achieves quality control throughout the nominal plan design process, fundamentally ensuring the accuracy and reliability of the nominal plan and providing solid technical support for the safe execution of spacecraft flight control missions.

[0147] Figure 5 A schematic diagram of an embodiment of an automated design system 200 for spacecraft nominal planning provided by the present invention is shown. Figure 5 As shown, the spacecraft nominal plan automated design system 200 includes: a creation module 201, a conversion module 202, a fusion module 203, a generation module 204, and a verification module 205;

[0148] The establishment module 201 is used to: establish an instruction and injection database for storing and managing remote control instructions, program control instructions, instruction chains and injection data;

[0149] The conversion module 202 is used to: automatically convert the spacecraft's flight program into an initial nominal plan based on the instructions and the injection database. The automatic conversion includes: converting the instruction information format in the flight program, filling in the instruction duration according to the instructions and the injection database, converting the instruction sending interval into an offset, and automatically filling in the event type, target identifier, number of commands, and relay identifier.

[0150] The fusion module 203 is used to: select the corresponding nominal plan for the operating condition from the pre-established nominal plan set according to the actual operating condition of the spacecraft, and fuse the nominal plan for the operating condition with the initial nominal plan to generate a fused nominal plan;

[0151] The generation module 204 is used to: read the telemetry, tracking, and command (TT&C) arc segment and arc segment obstruction time of the spacecraft; and, based on the command transmission interval and command attributes in the fused nominal plan, automatically generate the command transmission time within the TT&C and tracking arc segment while avoiding the arc segment obstruction time, thereby obtaining an updated nominal plan.

[0152] The verification module 205 is used to: automatically compare the updated nominal plan with the instructions and the injection database to verify the correctness of the instruction code, instruction name and offset in the updated nominal plan.

[0153] In an alternative embodiment, the establishment module 201 is specifically used for:

[0154] Establish an instruction database for storing remote control instructions and programmable instructions, the instruction database including instruction chain duration;

[0155] An injection database is established for storing injection data, and the injection database is used to receive and manage newly generated injection data.

[0156] In an alternative embodiment, the conversion module 202 is specifically used for:

[0157] Read the instruction codes and instruction numbers from the spacecraft's flight program, and convert the format of the instruction codes and instruction numbers into the instruction information format required by the nominal plan;

[0158] The instruction chain duration is obtained from the instruction database according to the instruction code, and the instruction chain duration is filled with the nominal planned instruction duration;

[0159] Read the command transmission interval in the flight procedure and convert the command transmission interval into an offset identified by the nominal plan;

[0160] The instruction type is identified based on the instruction code, and the event type of the nominal plan is filled in based on the instruction type;

[0161] Fill in the target identifier of the nominal plan according to the instruction code;

[0162] The number of commands to be issued in the nominal plan is filled based on the command type;

[0163] According to the current working section filling nominal plan, the replacement identification mark;

[0164] The initial nominal plan is generated by integrating the converted instruction information format, the filled instruction duration, the converted offset, and the filled event type, target identifier, number of commands issued, and proxy identifier.

[0165] In one alternative embodiment, the fusion module 203 is specifically used for:

[0166] Identify the repetitive flight control mission currently being performed by the spacecraft, and obtain the pre-established set of nominal plans corresponding to the repetitive flight control mission;

[0167] Select a matching nominal plan for the operating condition from the set of nominal plans based on the actual operating conditions of the spacecraft;

[0168] The nominal working condition plan and the initial nominal plan are fused together using instruction sequences and parameter configurations to generate the fused nominal plan.

[0169] In an alternative embodiment, the generation module 204 is specifically used for:

[0170] Obtain each tracking and control arc segment of the spacecraft and the corresponding arc segment blocking time;

[0171] Calculate the available time period for each tracking arc segment after deducting the corresponding arc segment's obstruction time;

[0172] The command timing relationship for each flight control event is determined based on the command transmission interval in the fusion nominal plan;

[0173] Identify the command attributes of each flight control event in the fusion nominal plan;

[0174] Based on all available time periods and the command attributes of each flight control event, the command sequence of each flight control event is assigned to the corresponding telemetry and tracking arc segment, and the arc segment blockage time in each telemetry and tracking arc segment is avoided during the assignment process to obtain the assignment result;

[0175] Adjust the offset of the corresponding instruction according to the allocation result, and generate the updated nominal plan based on the adjusted instruction timing relationship and offset.

[0176] In an alternative embodiment, the generation module 204 is specifically used for:

[0177] The instruction sequence of flight control events with the instruction attribute of splittable mode is allocated in chronological order to the available time periods of multiple consecutive telemetry and tracking arcs;

[0178] Assign the complete command sequence of a flight control event with an indivisible command attribute to the available time period of a single telemetry and tracking arc;

[0179] During the allocation process, ensure that the sending time of all instructions avoids the arc occlusion time in each telemetry and tracking arc segment;

[0180] When the total duration of the command sequence of a flight control event exceeds the available time period of a single telemetry and tracking arc, the command sequence of the splittable mode is segmented across arcs.

[0181] Record the final assigned telemetry and tracking arc segment for each instruction and the specific transmission time within the corresponding telemetry and tracking arc segment to form the allocation result.

[0182] In an alternative embodiment, the verification module 205 is specifically used for:

[0183] Using the instruction codes in the updated nominal plan, obtain the corresponding instruction name and instruction chain duration from the instruction database;

[0184] Verify whether the instruction code in the updated nominal plan has a corresponding record in the instruction database; compare and verify the instruction name in the updated nominal plan with the corresponding instruction name obtained from the instruction database; check whether the offset in the updated nominal plan meets the instruction chain duration requirement of the corresponding instruction obtained from the instruction database;

[0185] When the instruction code in the updated nominal plan does not have a corresponding record in the instruction database, an instruction code error message is generated; when the instruction name in the updated nominal plan is inconsistent with the corresponding instruction name obtained from the instruction database, an instruction name error message is generated; when the offset in the updated nominal plan does not meet the instruction chain duration requirement of the corresponding instruction obtained from the instruction database, an offset error message is generated.

[0186] It should be noted that the beneficial effects of the spacecraft nominal plan automated design system 200 provided in the above embodiments are the same as those of the spacecraft nominal plan automated design method described above, and will not be repeated here. Furthermore, the system provided in the above embodiments is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the system can be divided into different functional modules according to the actual situation to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process is detailed in the method embodiments, and will not be repeated here.

[0187] The spacecraft nominal plan automated design system 200 of the present invention can be a computer program (including program code) running on a computer device. For example, the spacecraft nominal plan automated design system 200 of the present invention is an application software that can be used to execute the corresponding steps in the spacecraft nominal plan automated design method of the present invention.

[0188] In some embodiments, the spacecraft nominal plan automated design system 200 of the present invention can be implemented in a combination of hardware and software. As an example, the spacecraft nominal plan automated design system 200 of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the spacecraft nominal plan automated design method of the present invention. For example, the processor in the form of a hardware decoding processor can be one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0189] The modules described in the embodiments of this invention can be implemented in software or hardware. The names of the modules are not, in some cases, limiting the scope of the module itself.

[0190] An electronic device according to an embodiment of the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements any of the above-mentioned automated design methods for spacecraft nominal plans. That is, an electronic device according to an embodiment of the present invention may include, but is not limited to: a processor and a memory; the memory is used to store the computer program; the processor is used to execute the automated design method for spacecraft nominal plans shown in any embodiment of the present invention by calling the computer program.

[0191] In one alternative embodiment, an electronic device is provided, such as Figure 6 As shown, Figure 6The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present invention.

[0192] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this invention. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0193] Bus 4002 may include a path for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus 4002 is represented by only one thick line, but this does not mean that there is only one bus or one type of bus.

[0194] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0195] The memory 4003 stores application code (computer program) for executing the present invention, and its execution is controlled by the processor 4001. The processor 4001 executes the application code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.

[0196] Among them, electronic devices can also be terminal devices. A terminal device can be any terminal device that can install applications and access web pages through applications, including at least one of smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, smart TVs, and smart in-vehicle devices.

[0197] It should be noted that, Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present invention.

[0198] An embodiment of the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-described automated design methods for spacecraft nominal plans.

[0199] Alternatively, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, a floppy disk, and an optical data storage device, etc.

[0200] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the aforementioned spacecraft nominal plan automated design method.

[0201] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0202] It should be understood that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0203] The computer-readable storage medium provided in this invention can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0204] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.

[0205] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.

[0206] It should be noted that the terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and represent a limitation on a specific order or sequence. Where appropriate, the order of use for similar objects can be interchanged so that the embodiments of this application described herein can be implemented in an order other than that shown or described.

[0207] Those skilled in the art will recognize that this invention can be implemented as a system, method, or computer program product. Therefore, this invention can be specifically implemented in the following forms: it can be entirely hardware, entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software, generally referred to herein as a "circuit," "module," or "system." Furthermore, in some embodiments, this invention can also be implemented as a computer program product contained in one or more computer-readable media, which includes computer-readable program code.

[0208] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. An automated design method for spacecraft nominal plans, characterized in that, include: Establish an instruction and injection database to store and manage remote control instructions, programmable instructions, instruction chains, and injection data; Based on the instructions and the injected database, the spacecraft's flight program is automatically converted into an initial nominal plan. The automatic conversion includes: converting the instruction information format in the flight program, filling in the instruction duration according to the instructions and the injected database, converting the instruction sending interval into an offset, and automatically filling in the event type, target identifier, number of commands, and relay identifier. Based on the actual operating conditions of the spacecraft, a corresponding nominal operating condition plan is selected from a pre-established set of nominal plans, and the nominal operating condition plan is merged with the initial nominal plan to generate a merged nominal plan; The telemetry, tracking, and command (TT&C) arc and arc blockage time of the spacecraft are read. Based on the command transmission interval and command attributes in the fusion nominal plan, and under the condition of avoiding the arc blockage time, the command transmission time is automatically generated within the TT&C arc to obtain the updated nominal plan. The updated nominal plan is automatically compared with the instructions and the injected database to verify the correctness of the instruction code, instruction name and offset in the updated nominal plan.

2. The automated design method for spacecraft nominal plans according to claim 1, characterized in that, The instruction and injection database includes: an instruction database and an injection database; the step of establishing the instruction and injection database for storing and managing remote control instructions, programmable instructions, instruction chains, and injection data includes: Establish an instruction database for storing remote control instructions and programmable instructions, the instruction database including instruction chain duration; An injection database is established for storing injection data, and the injection database is used to receive and manage newly generated injection data.

3. The automated design method for spacecraft nominal plans according to claim 2, characterized in that, The step of automatically converting the spacecraft's flight program into an initial nominal plan based on the instructions and the injected database includes: Read the instruction codes and instruction numbers from the spacecraft's flight program, and convert the format of the instruction codes and instruction numbers into the instruction information format required by the nominal plan; The instruction chain duration is obtained from the instruction database according to the instruction code, and the instruction chain duration is filled with the nominal planned instruction duration; Read the command transmission interval in the flight procedure and convert the command transmission interval into an offset identified by the nominal plan; The instruction type is identified based on the instruction code, and the event type of the nominal plan is filled in based on the instruction type; Fill in the target identifier of the nominal plan according to the instruction code; The number of commands to be issued in the nominal plan is filled based on the command type; According to the current working section filling nominal plan, the replacement identification mark; The initial nominal plan is generated by integrating the converted instruction information format, the filled instruction duration, the converted offset, and the filled event type, target identifier, number of commands issued, and proxy identifier.

4. The automated design method for spacecraft nominal plans according to claim 1, characterized in that, The step of selecting a corresponding nominal operating plan from a pre-established set of nominal operating plans based on the actual operating conditions of the spacecraft, and merging the nominal operating plan with the initial nominal plan to generate a merged nominal plan includes: Identify the repetitive flight control mission currently being performed by the spacecraft, and obtain the pre-established set of nominal plans corresponding to the repetitive flight control mission; Select a matching nominal plan for the operating condition from the set of nominal plans based on the actual operating conditions of the spacecraft; The nominal working condition plan and the initial nominal plan are fused together using instruction sequences and parameter configurations to generate the fused nominal plan.

5. The automated design method for spacecraft nominal plans according to claim 1, characterized in that, The steps of reading the spacecraft's telemetry, tracking, and command (TT&C) arc segment and arc segment blocking time, and automatically generating command transmission times within the TT&C arc segment based on the command transmission interval and command attributes in the fused nominal plan, while avoiding the arc segment blocking time, to obtain an updated nominal plan, include: Obtain each tracking and control arc segment of the spacecraft and the corresponding arc segment blocking time; Calculate the available time period for each tracking arc segment after deducting the corresponding arc segment's obstruction time; The command timing relationship for each flight control event is determined based on the command transmission interval in the fusion nominal plan; Identify the command attributes of each flight control event in the fusion nominal plan; Based on all available time periods and the command attributes of each flight control event, the command sequence of each flight control event is assigned to the corresponding telemetry and tracking arc segment, and the arc segment blockage time in each telemetry and tracking arc segment is avoided during the assignment process to obtain the assignment result; Adjust the offset of the corresponding instruction according to the allocation result, and generate the updated nominal plan based on the adjusted instruction timing relationship and offset.

6. The automated design method for spacecraft nominal plans according to claim 5, characterized in that, The step of allocating the instruction sequence of each flight control event to the corresponding telemetry and tracking arc segment based on all available time periods and the instruction attributes of each flight control event, and avoiding the arc segment blockage time in each telemetry and tracking arc segment during the allocation process, to obtain the allocation result includes: The instruction sequence of flight control events with the instruction attribute of splittable mode is allocated in chronological order to the available time periods of multiple consecutive telemetry and tracking arcs; Assign the complete command sequence of a flight control event with an indivisible command attribute to the available time period of a single telemetry and tracking arc; During the allocation process, ensure that the sending time of all instructions avoids the arc occlusion time in each telemetry and tracking arc segment; When the total duration of the command sequence of a flight control event exceeds the available time period of a single telemetry and tracking arc, the command sequence of the splittable mode is segmented across arcs. Record the final assigned telemetry and tracking arc segment for each instruction and the specific transmission time within the corresponding telemetry and tracking arc segment to form the allocation result.

7. The automated design method for spacecraft nominal plans according to claim 2 or 3, characterized in that, The step of automatically comparing the updated nominal plan with the instructions and the injection database to verify the correctness of the instruction code, instruction name, and offset in the updated nominal plan includes: Using the instruction codes in the updated nominal plan, obtain the corresponding instruction name and instruction chain duration from the instruction database; Verify whether the instruction code in the updated nominal plan has a corresponding record in the instruction database; compare and verify the instruction name in the updated nominal plan with the corresponding instruction name obtained from the instruction database; check whether the offset in the updated nominal plan meets the instruction chain duration requirement of the corresponding instruction obtained from the instruction database; When the instruction code in the updated nominal plan does not have a corresponding record in the instruction database, an instruction code error message is generated; when the instruction name in the updated nominal plan is inconsistent with the corresponding instruction name obtained from the instruction database, an instruction name error message is generated; when the offset in the updated nominal plan does not meet the instruction chain duration requirement of the corresponding instruction obtained from the instruction database, an offset error message is generated.

8. An automated design system for spacecraft nominal plans, characterized in that, include: The module includes a creation module, a transformation module, a fusion module, a generation module, and a verification module. The establishment module is used to: establish an instruction and injection database for storing and managing remote control instructions, program control instructions, instruction chains and injection data; The conversion module is used to: automatically convert the spacecraft's flight program into an initial nominal plan based on the instructions and the injection database. The automatic conversion includes: converting the instruction information format in the flight program, filling in the instruction duration according to the instructions and the injection database, converting the instruction sending interval into an offset, and automatically filling in the event type, target identifier, number of commands, and relay identifier. The fusion module is used to: select the corresponding nominal operating plan from the pre-established nominal plan set according to the actual operating conditions of the spacecraft, and fuse the nominal operating plan with the initial nominal plan to generate a fused nominal plan; The generation module is used to: read the telemetry, tracking, and command (TT&C) arc segment and arc segment obstruction time of the spacecraft; and, based on the command transmission interval and command attributes in the fused nominal plan, automatically generate command transmission time within the TT&C and tracking arc segment while avoiding the arc segment obstruction time, thereby obtaining an updated nominal plan. The verification module is used to automatically compare the updated nominal plan with the instructions and the injected database to verify the correctness of the instruction code, instruction name and offset in the updated nominal plan.

9. An electronic device, characterized in that, The electronic device includes a processor coupled to a memory storing at least one computer program, which is loaded and executed by the processor to enable the electronic device to implement the spacecraft nominal plan automated design 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 stores at least one computer program, which, when executed by a processor, implements the spacecraft nominal plan automated design method as described in any one of claims 1 to 7.

Images