Spaceflight control coordination work procedure generation method, system, device and storage medium

Abstract

The application discloses a spaceflight measurement and control cooperative work procedure generation method, system, device and storage medium, and comprises the following steps: calling a matched rule for analysis according to an event type contained in each spaceflight measurement and control task implementation file, and extracting cooperative work content in each spaceflight measurement and control task implementation file; based on the rule matched with the event type, establishing an association relationship between the cooperative work content extracted from the plurality of spaceflight measurement and control task implementation files; receiving first user input information for customizing the cooperative work content and feature points, and receiving second user input information for adding an independent new event and corresponding cooperative work content; and according to the association relationship, the first user input information and the second user input information, arranging and generating a cooperative work procedure document in time sequence. The application realizes unified scheduling of multiple types of events and automatic generation of a standardized cooperative work procedure document, and improves the fine and intelligent level of spaceflight measurement and control task execution.

Description

Technical Field

[0001] This invention relates to the field of aerospace telemetry and control technology, and in particular to a method, system, device and storage medium for generating aerospace telemetry and control collaborative work program. Background Technology

[0002] Space telemetry, tracking, and command (TT&C) missions involve various types of mission implementation documents and complex space-ground collaborative operations, encompassing diverse event types and corresponding event reporting and display requirements. To ensure smooth mission execution, all events must be chronologically arranged to generate standardized collaborative work procedure documents as the basis for execution. This process requires: reading and parsing multi-source mission implementation documents, rule-based and custom event reporting and display, manual addition of custom events, and unified scheduling and output of all event types. However, existing technologies struggle to effectively meet these comprehensive requirements, lacking a systematic method for generating collaborative work procedures, resulting in low efficiency, error-proneness, and insufficient flexibility, thus hindering the refinement and intelligent development of space TT&C missions.

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

[0004] To address the aforementioned technical problems, this invention provides a method, system, device, and storage medium for generating aerospace telemetry and control collaborative work programs.

[0005] Firstly, the present invention provides a method for generating aerospace telemetry and control collaborative work procedures, the technical solution of which is as follows: The system acquires multiple aerospace telemetry and control mission implementation documents, and parses them by calling matching rules based on the event types contained in each document, extracting the collaborative work content from each document. Based on rules that match the event type, establish the association between the collaborative work content extracted from the implementation documents of the multiple aerospace telemetry and control missions; Receive first user input information for customizing collaborative work content and feature points, and receive second user input information for adding independent new events and corresponding collaborative work content; Based on the aforementioned relationships, the first user input information, and the second user input information, they are uniformly arranged in chronological order to generate a collaborative work procedure document.

[0006] The beneficial effects of the aerospace telemetry and control collaborative work program generation method of the present invention are as follows: The method of this invention can solve the problems of low efficiency, error-proneness and lack of flexibility of traditional manual scheduling, realize the unified scheduling of multiple types of events and the automatic generation of standardized collaborative work procedure documents, and improve the precision and intelligence of aerospace telemetry and control mission execution.

[0007] Based on the above scheme, the aerospace telemetry and control collaborative work program generation method of the present invention can be further improved as follows.

[0008] In one alternative approach, the step of obtaining multiple aerospace telemetry and control mission implementation documents includes: Receive selection operation for a folder containing implementation files of aerospace telemetry and control missions; In response to the selection operation, the storage path of the folder is determined; Obtain the multiple aerospace telemetry and control mission implementation files from the storage path; wherein, the multiple aerospace telemetry and control mission implementation files include at least one of the following: operational plan files, injection arrangement files, or custom arrangement files.

[0009] The advantages of adopting the above optional methods are: it further clarifies the specific methods for obtaining practical plan files, injection arrangement files, or custom arrangement files through folder selection operations, simplifies the reading process of multi-source task implementation files, and lays the foundation for subsequent unified parsing.

[0010] In one alternative approach, the step of parsing and extracting collaborative work content from each space telemetry and control mission implementation document by invoking matching rules based on the event types contained in each document includes: Identify the event types included in the implementation documents for each aerospace telemetry, tracking, and command mission; From the pre-set rule base, the parsing rule that matches the event type of any space telemetry and control mission implementation document is called to parse the space telemetry and control mission implementation document, extract the collaborative work content from the space telemetry and control mission implementation document, and so on, until the collaborative work content in each space telemetry and control mission implementation document is extracted.

[0011] The advantages of adopting the above optional method are: it further determines the method of calling parsing rules that match the event type from the preset rule base for file parsing, and improves the parsing accuracy and adaptability of task implementation files of different formats.

[0012] In one alternative approach, the step of establishing the association between collaborative work content extracted from the multiple aerospace telemetry and control mission implementation documents based on rules matching event types includes: Based on the event type corresponding to each collaborative work content, at least one association rule suitable for establishing association relationships is selected from the preset rule base; Invoke the at least one association rule to establish the association relationship between collaborative work content extracted from different aerospace telemetry and control mission implementation documents.

[0013] The advantages of adopting the above optional approach are: it further specifies the operation of selecting association rules based on event type and establishing the association relationship between collaborative work content, realizes the automatic association between content extracted from multiple sources, and strengthens the logical integrity of events.

[0014] In one alternative approach, the step of receiving first user input information that customizes the collaborative work content and feature points includes: Receive modification instructions from users through the interactive interface for extracted collaborative work content, and / or receive new collaborative work content from users through the interactive interface. Receive user definition operations for event feature points and / or time feature points through the interactive interface; The modification instructions and / or the newly added collaborative work content, along with the data corresponding to the defined operation, are integrated into the first user input information.

[0015] The advantages of adopting the above optional approach are: it further provides the function of modifying and adding extracted content through an interactive interface, as well as defining event and time feature points, which meets the needs of personalized customization and enhances the flexibility of arrangement.

[0016] In one alternative approach, the step of receiving second user input information for adding independent new events and corresponding collaborative content includes: Receive new events that are independent of the already acquired aerospace telemetry and control mission implementation documents, input by the user through the interactive interface; Receive collaborative work content corresponding to the new event input by the user through the interactive interface; The new event and its corresponding collaborative content are integrated into the second user input information.

[0017] The advantages of adopting the above optional methods are: it further limits the way of receiving new events that are independent of the already acquired files and the corresponding collaborative work content, supports the manual supplementation of special events, and improves the task coverage.

[0018] In one optional approach, the step of generating a collaborative work procedure document by uniformly arranging the information according to the association, the first user input information, and the second user input information in chronological order includes: The customized collaborative work content and feature points contained in the first user input information, and the new events and corresponding collaborative work content contained in the second user input information, are added to the collaborative work content set determined based on the association relationship to form all collaborative work content to be arranged. Based on the logical and temporal order of events represented by the aforementioned relationships, all collaborative work content to be arranged is uniformly sorted. Based on a predetermined document template, all sorted collaborative work content is generated into a collaborative work program document with structured tables and formatted text styles.

[0019] The beneficial effects of adopting the above optional method are as follows: It further describes the process of integrating custom content, new events and related sets into a unified sort and generating a structured table document based on the template, thereby realizing the automated output of standardized collaborative work procedure documents.

[0020] Secondly, this invention provides a space telemetry and control collaborative work procedure generation system, the technical solution of which is as follows: The parsing module is used to obtain multiple aerospace telemetry and control mission implementation documents, and to call matching rules to parse them according to the event types contained in each aerospace telemetry and control mission implementation document, and extract the collaborative work content in each aerospace telemetry and control mission implementation document; The association module is used to establish association relationships between collaborative work content extracted from the multiple aerospace telemetry and control mission implementation documents based on rules that match the event type. The receiving module is used to receive first user input information for customizing collaborative work content and feature points, and to receive second user input information for adding independent new events and corresponding collaborative work content. The generation module is used to generate a collaborative work procedure document by uniformly arranging the information according to the association, the first user input information, and the second user input information in chronological order.

[0021] The beneficial effects of the aerospace telemetry and control collaborative work program generation system of the present invention are as follows: The system of this invention can solve the problems of low efficiency, error-proneness and lack of flexibility of traditional manual scheduling, realize the unified scheduling of multiple types of events and the automatic generation of standardized collaborative work procedure documents, and improve the precision and intelligence level of aerospace telemetry and control mission execution.

[0022] Thirdly, the technical solution of an electronic device according to the present invention is as follows: It includes a memory, a processor, and a program stored in the memory and running on the processor, wherein when the processor executes the program, it implements the steps of the aerospace telemetry and control collaborative work program generation method of the present invention.

[0023] Fourthly, the technical solution of a computer-readable storage medium provided by the present invention is as follows: The computer-readable storage medium stores instructions that, when read, cause the computer-readable storage medium to execute the steps of the aerospace telemetry and control collaborative work program generation method of the present invention.

[0024] 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

[0025] 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: Figure 1 This is a flowchart illustrating an embodiment of a method for generating aerospace telemetry and control collaborative work program according to the present invention. Figure 2 This is an overall flowchart of an embodiment of a method for generating aerospace telemetry and control collaborative work program according to the present invention; Figure 3 This is a schematic diagram of an embodiment of a space telemetry and control collaborative work program generation system according to the present invention; Figure 4 This is a schematic diagram of an embodiment of an electronic device according to the present invention. Detailed Implementation

[0026] 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.

[0027] Figure 1 This diagram illustrates a flowchart of an embodiment of a space telemetry and control collaborative workflow generation method provided by the present invention. This 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 composed of multiple servers. Any electronic device can implement the space telemetry and control collaborative workflow generation method by having its processor call computer-readable instructions stored in its memory. Figure 1 As shown, it includes the following steps: S1. Obtain multiple aerospace telemetry and control mission implementation documents, and parse them according to the event types contained in each aerospace telemetry and control mission implementation document by calling the matching rules, and extract the collaborative work content in each aerospace telemetry and control mission implementation document.

[0028] Among them, the aerospace telemetry and control mission implementation documents refer to formatted electronic documents generated during the preparation and execution of aerospace telemetry and control missions, used to guide, record, or arrange various specific space-ground collaborative tasks. For example, in a satellite launch mission in 2025, the compressed file named "Practical Plan_20250115.zip", the document named "Injection Arrangement_V1.0.docx", and the document named "Meteorological Support Custom Arrangement.docx" generated together constitute the aerospace telemetry and control mission implementation documents for that mission. Event types refer to the categories of various work items or status points recorded in the aerospace telemetry and control mission implementation documents according to their technical attributes and operational purposes. For example, in the aforementioned 2025 satellite launch mission, event types include remote control commands (sending uplink control commands), programmable commands (satellite autonomous execution sequences), injected data (uplink loading data), and important events (status requiring critical notification). Collaborative work content refers to the core information unit extracted from the aerospace telemetry and control mission implementation documents through parsing, which describes the specific occurrence time, execution operation and key parameters of an event; for example, a collaborative work content extracted from "Practical Plan_20250115.zip" is "January 15, 2025, 10:30:00 (Beijing time), send remote control command, command code: ON_SA_001, target: deploy solar cell array".

[0029] S2. Based on rules that match the event type, establish the association between the collaborative work content extracted from the implementation documents of the multiple aerospace telemetry and control missions.

[0030] Among them, the association relationship refers to the logical connection or time constraint relationship automatically established between collaborative work content extracted from different documents according to predefined rules; for example, a "injection orbit control parameters" content extracted from "injection arrangement_V1.0.docx" and a "satellite enters orbit change preparation attitude" content extracted from the actual operation plan document are automatically associated according to the rules, indicating that the injection operation must be completed within 5 minutes after the attitude is established.

[0031] S3. Receive first user input information for customizing collaborative work content and feature points, and receive second user input information for adding independent new events and corresponding collaborative work content.

[0032] Feature points refer to user-defined reference markers used to mark specific event states or absolute / relative time positions in collaborative work procedures; for example, a user might define "satellite-rocket separation" as an event feature point and "T0+120 minutes" as a time feature point. First user input information refers to the data set entered by the user through the graphical interface to modify existing collaborative work content, add new collaborative work content, or define feature points; for example, a user might change the execution time of an instruction in an existing piece of content from "10:30:00" to "10:29:30," add a new collaborative work content item "Check telemetry link lock status," and define "radar acquisition" as an event feature point. These input data, when integrated, constitute the first user input information. New events refer to work items that the user proposes and describes entirely independently of the already entered aerospace telemetry and control mission implementation documents, requiring addition to the program; for example, a user might add a new event named "Conduct on-orbit payload safety mode switching test" based on a temporary instruction. The second user input information refers to the data set entered by the user through the graphical interactive interface, which describes an independent new event and its corresponding collaborative work content. For example, if the user enters a new event "on-orbit payload safety mode switching test" and specifies its collaborative work content as "January 15, 2025, 12:00:00, send a command to switch to safety mode and monitor telemetry parameter XXX", this set of information constitutes the second user input information.

[0033] S4. Based on the aforementioned relationship, the first user input information, and the second user input information, arrange them in chronological order to generate a collaborative work procedure document.

[0034] The collaborative work procedure document refers to the final, standardized output document that guides the implementation of the mission by arranging all collaborative work content in a chronological order. For example, a document named "Collaborative Work Procedure for the 2025 XX Satellite Launch Mission.docx" lists all work items from mission preparation to completion, along with their timelines and job requirements, in tabular form.

[0035] The technical solution of this embodiment can solve the problems of low efficiency, error-proneness and lack of flexibility of traditional manual scheduling, realize the unified scheduling of multiple types of events and the automatic generation of standardized collaborative work procedure documents, and improve the precision and intelligence level of aerospace telemetry and control mission execution.

[0036] In one alternative approach, the step of obtaining multiple aerospace telemetry and control mission implementation documents includes: Receives a selection operation for a folder containing documents related to aerospace telemetry and control missions.

[0037] The selection operation refers to the user's action of specifying a folder containing multiple aerospace telemetry and control mission implementation files through actions such as clicking and browsing in the graphical interactive interface; for example, the user browses and selects the "2025_XX satellite mission" folder in the local path in the file selection dialog box.

[0038] In response to the selection operation, the storage path of the folder is determined.

[0039] The storage path refers to a string that uniquely identifies the location of a folder or file in the computer's file system; for example, the storage path of the "2025_XX Satellite Mission" folder selected by the user is "E:\Space Mission\2025\XX Satellite\First Launch".

[0040] Obtain the multiple aerospace telemetry and control mission implementation files from the storage path; wherein, the multiple aerospace telemetry and control mission implementation files include at least one of the following: operational plan files, injection arrangement files, or custom arrangement files.

[0041] The operational plan document refers to a compressed package or document containing core planning results such as the spacecraft flight event timeline and tracking plans of telemetry and control stations. For example, the "Operational Plan_20250115.zip" file contains a timeline of events accurate to the second for this launch and tracking arc data from each telemetry and control station. The injection arrangement document refers to a mission document specifically planning the timing, content, and procedures for injecting data and commands into the spacecraft. For example, the "Injection Arrangement_V1.0.docx" file details the number of orbital elements to be injected after the satellite enters orbit, the control software patches, and the corresponding injection cycles and times. The custom arrangement document refers to a document using a general format that allows users to freely fill in any non-standard or supplementary work arrangements. For example, the "Meteorological Support Custom Arrangement.docx" file includes work items such as "Two hours before launch, confirm that the cloud cover over the launch site meets the requirements."

[0042] Among the above optional methods, the specific ways to obtain the practical plan file, injection arrangement file or custom arrangement file through folder selection operation are further clarified, which simplifies the reading process of multi-source task implementation files and lays the foundation for subsequent unified parsing.

[0043] In one alternative approach, the step of parsing and extracting collaborative work content from each space telemetry and control mission implementation document by invoking matching rules based on the event types contained in each document includes: Identify the types of events included in the implementation documents for each space telemetry, tracking, and command mission.

[0044] From the pre-set rule base, the parsing rule that matches the event type of any space telemetry and control mission implementation document is called to parse the space telemetry and control mission implementation document, extract the collaborative work content from the space telemetry and control mission implementation document, and so on, until the collaborative work content in each space telemetry and control mission implementation document is extracted.

[0045] The pre-built rule base refers to a set of logical rules stored in a computer-readable medium, corresponding to different event types, to guide file parsing and content association. For example, a rule base may contain rules such as "If the event type is 'remote control command,' then call rule A to parse its time, command code, and parameters," and "An event of type 'injected data' must be associated with an event of type 'station tracking' that overlaps in time." Parsing rules refer to logical instructions in the pre-built rule base specifically designed to guide how to identify and extract collaborative content from files of specific event types. For example, for the "important event" type, a parsing rule specifies that the Beijing time, event description text, and preset notification level code of the event must be extracted.

[0046] Among the above optional methods, a method for parsing files by calling parsing rules that match the event type from a pre-built rule base was further determined, which improved the parsing accuracy and adaptability of task implementation files of different formats.

[0047] In one alternative approach, S2 specifically includes: Based on the event type corresponding to each collaborative work content, at least one association rule suitable for establishing an association relationship is selected from the preset rule base.

[0048] Among them, association rules refer to logical instructions in a pre-built rule base that are specifically used to guide how to establish logical or temporal associations between different collaborative work contents. For example, an association rule stipulates that an event whose content description contains "engine ignition" must be associated with an event of type "track measurement" that is adjacent in time for effect analysis.

[0049] Invoke the at least one association rule to establish the association relationship between collaborative work content extracted from different aerospace telemetry and control mission implementation documents.

[0050] Among the above optional methods, the operation of selecting association rules based on event type and establishing association relationships between collaborative work content is further specified, realizing automatic association between content extracted from multiple sources and strengthening the logical integrity of events.

[0051] In one alternative approach, the step of receiving first user input information that customizes the collaborative work content and feature points includes: Receive modification instructions from users through the interactive interface for extracted collaborative work content, and / or receive new collaborative work content from users through the interactive interface.

[0052] The interactive interface refers to the area presented in the software for users to perform visual operations, browse information, and input parameters; for example, a main software window displaying a list of parsed events, a content editing text box, a feature point management area, and various function buttons. A modification command refers to an input issued by the user through the interactive interface to change the attributes of a specific collaborative work item already displayed in the software interface; for example, a user directly edits the job title of an item in the event list from "Measurement and Control Post" to "Overall Post". Adding collaborative work content refers to a completely new work project description actively entered by the user through the interactive interface, outside of the software's existing event list; for example, a user enters the following in the software's new line: "January 15, 2025, 11:15:00, monitoring the disappearance of the launch vehicle telemetry signal".

[0053] Receive user definition operations for event feature points and / or time feature points through the interactive interface.

[0054] Among them, event feature points refer to user-defined feature points marked by the occurrence of a specific event; for example, a user might define the specific event "satellite antenna deployment and locking" as an event feature point named "antenna locking". Time feature points refer to user-defined feature points marked by an absolute calendar time or a specific time point relative to mission zero (T0); for example, a user might define "January 15, 2025, 10:05:00" or "T0+300 seconds" as a time feature point. Definition operations refer to actions performed by the user on the interactive interface to create or configure specific attributes (such as name, associated event, or time) of a feature point; for example, a user might click the "Add" button in the feature point management panel, enter the feature point name "Heading Correction Start" in the pop-up dialog box, and select its corresponding event ID.

[0055] The modification instructions and / or the newly added collaborative work content, along with the data corresponding to the defined operation, are integrated into the first user input information.

[0056] Among the above optional methods, the system further provides the ability to modify and add extracted content and define event and time feature points through an interactive interface, which meets the needs of personalized customization and enhances the flexibility of arrangement.

[0057] In one alternative approach, the step of receiving second user input information for adding independent new events and corresponding collaborative content includes: Receive new events that are independent of the already acquired aerospace telemetry and control mission implementation documents, which are input by the user through the interactive interface.

[0058] The acquired aerospace telemetry and control mission implementation documents refer to all mission implementation document instances successfully read from the specified storage path through the acquisition steps; for example, the three file instances "Practical Plan_20250115.zip", "Injection Arrangement_V1.0.docx", and "Custom Meteorological Support Arrangement.docx" obtained from the path "E:\Aerospace Missions\2025\XX Satellites\First Launch".

[0059] Receive collaborative work content corresponding to the new event input by the user through the interactive interface.

[0060] The new event and its corresponding collaborative content are integrated into the second user input information.

[0061] The collaborative work content set refers to the overall dataset formed by summarizing all collaborative work content extracted from all acquired aerospace telemetry and control mission implementation documents; for example, a total of 120 collaborative work contents extracted from the above three documents are compiled into an initial data set containing 120 entries.

[0062] Among the above-mentioned optional methods, the methods for receiving new events and corresponding collaborative work content that are independent of the already acquired files are further defined, and special events can be manually supplemented, thus improving the scope of task coverage.

[0063] In one alternative approach, S4 specifically includes: The customized collaborative work content and feature points contained in the first user input information, and the new events and corresponding collaborative work content contained in the second user input information, are added to the collaborative work content set determined based on the association relationship to form all collaborative work content to be arranged.

[0064] The complete set of collaborative work content to be arranged refers to the complete data set including the initial set of collaborative work content, the custom content in the first user input information, and the new event content in the second user input information. For example, the initial 120 items, the 3 items modified by the user, the 2 newly added items, and 1 independent new event "On-orbit payload safety mode switching test" and its content are merged into a complete dataset containing 126 work items for sorting.

[0065] Based on the logical and temporal order of events represented by the aforementioned relationships, all collaborative work content to be arranged is uniformly sorted.

[0066] Among them, the logical and temporal order between events refers to the logical constraints such as causality and dependency between events as defined by the association relationship, as well as the order in which they occur; for example, the association rule defines that the "inject data" event can only be executed after the corresponding "station tracking" event starts, which reflects the logical and temporal constraints between the two.

[0067] Based on a predetermined document template, all sorted collaborative work content is generated into a collaborative work program document with structured tables and formatted text styles.

[0068] The pre-designed document template refers to a pre-designed and stored file that specifies the page layout, title style, table structure, font size, and other formatting requirements for the final collaborative work procedure document. For example, a file named "Standard Collaborative Work Procedure Template.dotx" defines the font of the task title as size 2 boldface, and the tables have columns such as "Serial Number," "Absolute Time," "Relative Time," "Work Content," "Responsible Position," and "Remarks." The sorted collaborative work content refers to an ordered list obtained by strictly sorting all collaborative work content to be arranged from earliest to latest according to the logic and chronological order of events. For example, the aforementioned 126 items to be arranged are ultimately arranged into a timeline sequence from "January 15, 2025, 09:00:00" to "January 15, 2025, 15:00:00" based on their absolute time (Beijing time) and relative time relative to the feature point. Structured tables and formatted text styles refer to the fact that in the final generated document, collaborative work content is presented in the form of tables with clear row and column structures, and the text and cells within the tables are formatted according to a predetermined template with specific font, color, alignment, and other formatting attributes. For example, in the document "Collaborative Work Procedure for the 2025 XX Satellite Launch Mission.docx", all work items are arranged in chronological order in a table, the font color of the "Remote Control Instructions" row is set to red and bold, and the background color of the table rows in different mission stages alternates between light gray and white.

[0069] Among the above optional methods, the process of integrating custom content, new events and related sets and sorting them in a unified manner, and generating a structured table document based on the template is further described, thereby realizing the automated output of standardized collaborative work procedure documents.

[0070] like Figure 2 As shown, the overall logic of the aerospace telemetry and control collaborative work procedure generation method in this embodiment is as follows: 1) Configure status settings according to the documents "Configuration Parameters.docx", "Countersigning Process.docx", and "Report Important Events.docx". Status settings include setting spacecraft target parameters, customizing display colors for different event types, defining global feature points, customizing report content, loading countersigning processes for each target, and specifying important events that need to be reported. Specific spacecraft target parameters involve target code, scheduling code, mission zero time T0, mission end time TF, and operational phase.

[0071] 2) Using folders as input units, the system receives selection operations for folders containing aerospace telemetry and control mission implementation documents, thereby determining the storage path of those folders. Based on this storage path, multiple aerospace telemetry and control mission implementation documents are retrieved. These documents include essential operational plan documents, as well as optional injection arrangement documents and custom arrangement documents. The operational plan documents are stored in ZIP compressed format, while the injection arrangement documents and custom arrangement documents are in DOCX format. The content of the injection arrangement documents can be based on the initial draft output after parsing the operational plan documents, and then supplemented and improved by the relevant personnel. The custom arrangement documents use a general format to support manual input for any type of event.

[0072] 3) Based on the event types contained in each aerospace telemetry and control mission implementation document, the document is parsed using matching parsing rules from a pre-set rule base to extract the collaborative work content. Based on the rules matching the event types, one or more association rules suitable for establishing relationships are selected from the pre-set rule base to establish relationships between the collaborative work content extracted from different aerospace telemetry and control mission implementation documents. The preprocessing step generates all collaborative work program content according to the rules, and the generated data contains specific information for subsequent format configuration. This format configuration information is used to set table levels, fonts, colors, and cell fill colors during the document generation stage.

[0073] 4) Receive first user input information for customizing collaborative work content and feature points, and second user input information for adding independent new events and corresponding collaborative work content. The first user input information integrates modification instructions or newly added collaborative work content entered through the interactive interface for the extracted collaborative work content, as well as definition operations for event feature points or time feature points. The second user input information integrates new events entered through the interactive interface, independent of all acquired aerospace telemetry and control mission implementation documents, and their corresponding collaborative work content. Based on the established relationships, the integrated first user input information, and the second user input information, all collaborative work content is uniformly arranged in chronological order. The arrangement process uniformly sorts all collaborative work content to be arranged according to the logical and chronological order of events represented by the relationships. Based on a predetermined document template, all sorted collaborative work content is generated into a collaborative work program document with structured tables and formatted text styles. The collaborative program generation steps also include setting the task name, output start time, and output end time, and performing operations such as generating a Word version of the collaborative program document, importing the Word version of the collaborative program document, and generating an injection arrangement file.

[0074] To better illustrate the technical solution of this embodiment, the following complete example (a satellite launch mission of a certain type in 2025) is used for explanation, specifically: 1) Based on the initialization documents named "Configuration Parameters.docx", "Countersigning Process.docx", and "Report Important Events.docx", the status settings are configured. Specifically, the spacecraft target parameters are set to code SAT2025-01, mission time T0 is set to June 10, 2025, 08:00:00, customized remote control command events are displayed in red in the final document, important event reports are displayed in blue, and "Star-Rocket Separation" is defined as a global event feature point.

[0075] 2) The system receives the user's selection of the "2025_Launch Mission Data" folder stored locally through the interactive interface, determines its storage path as "D:\Space Mission\2025\SAT2025-01", and retrieves multiple space telemetry and control mission implementation documents from this path, including the essential operational plan file "Operational Plan_20250610.zip", the optional injection arrangement file "Injection Arrangement_V1.5.docx", and the custom arrangement file "Meteorological and Emergency Custom Arrangement.docx". Based on the event type contained in each file, the system calls the matching parsing rules from the pre-set rule base to parse the file: extracting collaborative work content such as "June 10, 2025, 08:05:00, send remote control command, command code: SEP_CMD_01, content: satellite-rocket separation" from the operational plan file; extracting collaborative work content such as "T0+00:45:00, inject orbital control parameter group, data block identifier: ORB_CTL_202" from the injection arrangement file; and extracting collaborative work content such as "T0-01:00:00, confirm that the ground wind speed in the launch site is below 10 m / s" from the custom arrangement file.

[0076] 3) Based on rules that match the event type, select applicable association rules from the pre-set rule base and establish association relationships between collaborative work content extracted from different files. For example, associate the "injection orbit control parameter group" content in the injection arrangement with the "satellite enters orbit change preparation attitude" content in the actual operation plan, and constrain the injection operation to be completed within 2 minutes after attitude establishment.

[0077] 4) Receive the first user input information for customizing collaborative work content and feature points: The user inputs a modification command for an extracted collaborative work content through the interactive interface, changing its time from "June 10, 2025 08:05:00" to "June 10, 2025 08:04:30"; at the same time, a new collaborative work content "T0+00:10:00, check telemetry downlink lock status" is added; and "Radar first acquisition" is defined as a new event feature point. Simultaneously, receive the second user input information for adding independent new events: The user inputs a new event "On-orbit payload rapid functional test" that is completely unrelated to the acquired file, and specifies its corresponding collaborative work content as "June 10, 2025 09:30:00, send command to start payload rapid self-test mode, monitor key parameter P1".

[0078] 5) Add all the customized and newly added content contained in the first user input information and the second user input information to the set of collaborative work content extracted from the initial file based on the aforementioned relationship, forming all collaborative work content to be arranged. Based on the logical and temporal order of events represented by the aforementioned relationship, such as dependencies and temporal constraints, uniformly sort all collaborative work content to be arranged.

[0079] 6) Based on the predefined document template "Standard Collaboration Template.dotx" with defined table structure and font styles, generate the final collaboration document "2025 SAT2025-01 Satellite Launch Collaboration Document.docx" from all sorted collaborative work content. This generated document features structured tables and formatted text styles. The text in the "Remote Control Instructions" row is set to red and bold. Rows for different task phases are filled with different background colors, comprehensively, accurately, and systematically covering all events and work arrangements from multi-source file parsing and automatic fusion to flexible user customization.

[0080] This embodiment lays the foundation for the mission by loading configuration parameters, co-signing procedures, and important event report definitions through the initialization step. Based on the acquisition and event type analysis of various aerospace telemetry and control mission implementation documents, including operational plan documents, injection arrangement documents, and custom arrangement documents, collaborative work content is extracted. Logical and temporal relationships between different document contents are established using association rules in a pre-built rule base. The interactive interface receives user commands to modify existing content, add collaborative work content, customize events, and time feature points as first input information, as well as second input information to add completely independent new events and content. Finally, based on the association relationships and user-defined inputs, all events are uniformly arranged chronologically in multiple formats, including Beijing time, feature point relative time, and associated event relative time. Combined with automatically calculated tracking station, flight phase, orbit number, and lighting conditions, a standardized collaborative work procedure document with formatted tables and text styles is generated according to a predefined template. This achieves fully automated processing of multi-source file reading and parsing, rule-based and custom event notification display, free content expansion, flexible feature point definition, and automatic import of injection arrangements and co-signing procedures.

[0081] Figure 3 A schematic diagram of an embodiment of a space telemetry and control collaborative work procedure generation system 200 provided by the present invention is shown. Figure 3 As shown, the aerospace telemetry, tracking, and command collaborative work procedure generation system 200 includes: The parsing module 201 is used to obtain multiple aerospace telemetry and control mission implementation documents, and to call matching rules to parse them according to the event types contained in each aerospace telemetry and control mission implementation document, and extract the collaborative work content in each aerospace telemetry and control mission implementation document; The association module 202 is used to establish association relationships between collaborative work content extracted from the multiple aerospace telemetry and control mission implementation documents based on rules that match the event type. The receiving module 203 is used to receive first user input information for customizing collaborative work content and feature points, and to receive second user input information for adding independent new events and corresponding collaborative work content; The generation module 204 is used to generate a collaborative work procedure document by uniformly arranging the information according to the association, the first user input information and the second user input information in chronological order.

[0082] In an alternative embodiment, the parsing module 201 is specifically used for: Receive selection operation for a folder containing implementation files of aerospace telemetry and control missions; In response to the selection operation, the storage path of the folder is determined; Obtain the multiple aerospace telemetry and control mission implementation files from the storage path; wherein, the multiple aerospace telemetry and control mission implementation files include at least one of the following: operational plan files, injection arrangement files, or custom arrangement files.

[0083] In an alternative embodiment, the parsing module 201 is specifically used for: Identify the event types included in the implementation documents for each aerospace telemetry, tracking, and command mission; From the pre-set rule base, the parsing rule that matches the event type of any space telemetry and control mission implementation document is called to parse the space telemetry and control mission implementation document, extract the collaborative work content from the space telemetry and control mission implementation document, and so on, until the collaborative work content in each space telemetry and control mission implementation document is extracted.

[0084] In an alternative embodiment, the association module 202 is specifically used for: Based on the event type corresponding to each collaborative work content, at least one association rule suitable for establishing association relationships is selected from the preset rule base; Invoke the at least one association rule to establish the association relationship between collaborative work content extracted from different aerospace telemetry and control mission implementation documents.

[0085] In an alternative embodiment, the receiving module 203 is specifically used for: Receive modification instructions from users through the interactive interface for extracted collaborative work content, and / or receive new collaborative work content from users through the interactive interface. Receive user definition operations for event feature points and / or time feature points through the interactive interface; The modification instructions and / or the newly added collaborative work content, along with the data corresponding to the defined operation, are integrated into the first user input information.

[0086] In an alternative embodiment, the receiving module 203 is specifically used for: Receive new events that are independent of the already acquired aerospace telemetry and control mission implementation documents, input by the user through the interactive interface; Receive collaborative work content corresponding to the new event input by the user through the interactive interface; The new event and its corresponding collaborative content are integrated into the second user input information.

[0087] In an alternative embodiment, the generation module 204 is specifically used for: The customized collaborative work content and feature points contained in the first user input information, and the new events and corresponding collaborative work content contained in the second user input information, are added to the collaborative work content set determined based on the association relationship to form all collaborative work content to be arranged. Based on the logical and temporal order of events represented by the aforementioned relationships, all collaborative work content to be arranged is uniformly sorted. Based on a predetermined document template, all sorted collaborative work content is generated into a collaborative work program document with structured tables and formatted text styles.

[0088] It should be noted that the beneficial effects of the aerospace telemetry and control collaborative work procedure generation system 200 provided in the above embodiments are the same as those of the above aerospace telemetry and control collaborative work procedure generation method, 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.

[0089] The aerospace telemetry and control collaborative work procedure generation system 200 of the present invention can be a computer program (including program code) running on a computer device. For example, the aerospace telemetry and control collaborative work procedure generation system 200 of the present invention is an application software that can be used to execute the corresponding steps in the aerospace telemetry and control collaborative work procedure generation method of the present invention.

[0090] In some embodiments, the aerospace telemetry and control collaborative work program generation system 200 of the present invention can be implemented in a combination of hardware and software. As an example, the aerospace telemetry and control collaborative work program generation system 200 of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the aerospace telemetry and control collaborative work program generation 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.

[0091] 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.

[0092] 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 aerospace telemetry and control collaborative work program generation methods. 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 aerospace telemetry and control collaborative work program generation method shown in any embodiment of the present invention by calling the computer program.

[0093] In one alternative embodiment, an electronic device is provided, such as Figure 4 As shown, Figure 4The 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.

[0094] 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.

[0095] 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 4 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.

[0096] 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.

[0097] 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.

[0098] 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.

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

[0100] 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-mentioned aerospace telemetry and control collaborative work program generation methods.

[0101] 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.

[0102] 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 aerospace telemetry and control collaborative work program generation method.

[0103] 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).

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] 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. A method for generating aerospace telemetry, tracking, and command collaborative work program, characterized in that, include: The system acquires multiple aerospace telemetry and control mission implementation documents, and parses them by calling matching rules based on the event types contained in each document, extracting the collaborative work content from each document. Based on rules matching event types, establish the relationships between collaborative work content extracted from the implementation documents of the multiple aerospace telemetry and control missions; Receive first user input information for customizing collaborative work content and feature points, and receive second user input information for adding independent new events and corresponding collaborative work content; Based on the aforementioned relationship, the first user input information, and the second user input information, they are uniformly arranged in chronological order to generate a collaborative work procedure document; Before the step of obtaining multiple space telemetry and control mission implementation documents, the following is also included: Obtain an initialization document, which includes at least one of a configuration parameter document, a countersigning process document, and a report document for important events. The state is set according to the initialization document; wherein the state setting includes at least one of the following: Set the spacecraft target parameters, which include target code, scheduling code, mission zero time, mission end time and operation phase; Customize the display colors for different event types; Define global feature points; Load the corresponding countersigning processes for each target; Specify the important events that need to be reported; The step of generating a collaborative work procedure document by uniformly arranging the information according to the association, the first user input information, and the second user input information in chronological order includes: The customized collaborative work content and feature points contained in the first user input information, and the new events and corresponding collaborative work content contained in the second user input information, are added to the collaborative work content set determined based on the association relationship to form all collaborative work content to be arranged. Based on the logical and temporal order of events represented by the aforementioned relationships, all collaborative work content to be arranged is uniformly sorted. Based on a predetermined document template, all sorted collaborative work content is combined with automatically calculated tracking stations, flight phases, circle numbers, and lighting conditions to generate the collaborative work program document, which has structured tables and formatted text styles.

2. The method for generating aerospace telemetry and control collaborative work procedures according to claim 1, characterized in that, The steps for obtaining multiple aerospace telemetry and control mission implementation documents include: Receive selection operation for a folder containing implementation files of aerospace telemetry and control missions; In response to the selection operation, the storage path of the folder is determined; Obtain the multiple aerospace telemetry and control mission implementation files from the storage path; wherein, the multiple aerospace telemetry and control mission implementation files include at least one of the following: operational plan files, injection arrangement files, or custom arrangement files.

3. The method for generating aerospace telemetry and control collaborative work procedures according to claim 2, characterized in that, The step of parsing and extracting collaborative work content from each aerospace telemetry and control mission implementation document by calling matching rules based on the event types contained in each document includes: Identify the event types included in the implementation documents for each aerospace telemetry, tracking, and command mission; From the pre-set rule base, the parsing rule that matches the event type of any space telemetry and control mission implementation document is called to parse the space telemetry and control mission implementation document, extract the collaborative work content from the space telemetry and control mission implementation document, and so on, until the collaborative work content in each space telemetry and control mission implementation document is extracted.

4. The aerospace telemetry and control collaborative work program generation method according to claim 3, characterized in that, The step of establishing the correlation between collaborative work content extracted from the multiple aerospace telemetry and control mission implementation documents based on rules matching event types includes: Based on the event type corresponding to each collaborative work content, at least one association rule suitable for establishing an association relationship is selected from the preset rule base; Invoke the at least one association rule to establish the association relationship between collaborative work content extracted from different aerospace telemetry and control mission implementation documents.

5. The method for generating aerospace telemetry and control collaborative work procedures according to any one of claims 1 to 4, characterized in that, The step of receiving first user input information that customizes the collaborative work content and feature points includes: Receive modification instructions from users through the interactive interface for extracted collaborative work content, and / or receive new collaborative work content from users through the interactive interface. Receive user definition operations for event feature points and / or time feature points through the interactive interface; The modification instructions and / or the newly added collaborative work content, along with the data corresponding to the defined operation, are integrated into the first user input information.

6. The method for generating aerospace telemetry and control collaborative work procedures according to claim 5, characterized in that, The step of receiving second user input information for adding independent new events and corresponding collaborative work content includes: Receive new events that are independent of the already acquired aerospace telemetry and control mission implementation documents, input by the user through the interactive interface; Receive collaborative work content corresponding to the new event input by the user through the interactive interface; The new event and its corresponding collaborative content are integrated into the second user input information.

7. A space telemetry, tracking, and command collaborative work procedure generation system, characterized in that, The system, applied to the aerospace telemetry and control collaborative work procedure generation method according to any one of claims 1 to 6, comprises: The parsing module is used to obtain multiple aerospace telemetry and control mission implementation documents, and to call matching rules to parse them according to the event types contained in each aerospace telemetry and control mission implementation document, and extract the collaborative work content in each aerospace telemetry and control mission implementation document; The association module is used to establish association relationships between collaborative work content extracted from the multiple aerospace telemetry and control mission implementation documents based on rules that match the event type. The receiving module is used to receive first user input information for customizing collaborative work content and feature points, and to receive second user input information for adding independent new events and corresponding collaborative work content. The generation module is used to generate a collaborative work procedure document by uniformly arranging the information according to the association, the first user input information, and the second user input information in chronological order.

8. An electronic device, characterized in that, The electronic device includes a processor coupled to a memory, the memory storing at least one computer program, which is loaded and executed by the processor to enable the electronic device to implement the aerospace telemetry and control collaborative work program generation method as described in any one of claims 1 to 6.

9. 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 aerospace telemetry and control collaborative work program generation method as described in any one of claims 1 to 6.

Images