Centralized management method and device for satellite attitude and orbit control system parameters and readable medium

Abstract

The invention provides a centralized management method and device for satellite attitude and orbit control system parameters and a readable medium. The method comprises the following steps: dividing parameters of a satellite attitude and orbit control system into three types of parameters, wherein the three types of parameters comprise parameters with different ground configurations, parameters with the same ground configuration but reserved adjustable in orbit, and parameters required to be maintained for resetting and generator tripping; creating a global structure variable for each type of parameters, and taking each parameter in each type of parameters as a member variable of the global structure variable; according to the characteristics of each type of parameters, assigning a global structure variable by adopting different checking and modifying modes; and respectively mapping the global structure body variables into parameter variables of different modules of the satellite. According to the method, the parameters of the satellite attitude and orbit control system are divided into three types of parameters, different types of parameters are checked and modified by using different strategies, and a global structure variable is created for each type of parameters, so that efficient centralized management and online modification of the parameters are realized.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of satellite parameter processing, and in particular to a centralized management method, device and readable medium for satellite attitude and orbit control system parameters. Background Art

[0002] The satellite attitude and orbit control system (SATOC) primarily performs orbit transfer and insertion tasks, including ascent and orbital inclination changes, to eliminate static attitude errors, ensuring the satellite's flight within the desired attitude and orbit, ensuring satellite performance, and completing the mission. The software for SATOCs is typically designed and implemented in multiple modules, each of which independently manages its own parameters, ensuring strong internal cohesion and independence from external dependencies. This characteristic can make parameter verification and adjustment quite challenging.

[0003] When designing a single satellite, designers typically spend time reviewing and verifying parameters to ensure they are correct. However, this process takes a long time because parameters are scattered across various modules. Today, to meet the networking needs of satellite constellations, satellite development is increasing in number and on shorter schedules. Using traditional methods is time-consuming and prone to errors. Furthermore, for mass-produced satellites, different satellites must be packaged with both identical and different parameters. Therefore, a method is needed that can handle these differences and quickly assist designers in parameter review and verification. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a centralized management method, device and readable medium for satellite attitude and orbit control system parameters, so as to solve the problems of decentralized parameter management, low modification efficiency and easy error in existing satellite attitude and orbit control system parameters.

[0005] To solve the above technical problems, the present invention provides a centralized management method for satellite attitude and orbit control system parameters, including: dividing satellite attitude and orbit control system parameters into three categories of parameters, the three categories of parameters including parameters with different ground configurations, parameters with the same ground configuration but reserved for in-orbit adjustment, and parameters that need to be maintained during reset and shutdown; creating a global structure variable for each category of parameters, and using each parameter in each category as a member variable of the global structure variable; assigning values to the global structure variables using different inspection and modification methods according to the characteristics of each category of parameters; and mapping the global structure variables to parameter variables of different satellite modules.

[0006] Optionally, different checking and modification methods are used to assign values to the global structure variables according to the characteristics of each type of parameter, including: recording the different ground configuration parameters as first-type parameters; for the first-type parameters, before each batch of satellites is launched, the parameter binding table of each satellite is checked, and different satellites have different corresponding parameter binding tables. After the inspection is correct, the parameter binding table is bound into the satellite by annotation; after the satellite makes a secondary judgment on the validity of the parameter binding table, the parameter binding table is written into the global structure variable corresponding to the first-type parameter.

[0007] Optionally, different checking and modification methods are used to assign values to the global structure variables according to the characteristics of each type of parameters, including: recording parameters that have the same ground configuration but are reserved for in-orbit adjustment as second-type parameters; for the second-type parameters, before each batch of satellites is launched, checking the unified parameter table, and after checking that it is correct, storing the unified parameter table in the first non-volatile memory of multiple satellites in the same batch; when the global structure variables corresponding to the second-type parameters are initialized, obtaining the values of the member variables from the unified parameter table in the first non-volatile memory.

[0008] Optionally, it also includes: the satellite determines whether a parameter modification instruction is received, and if so, modifies the global structure variables corresponding to the second type of parameters according to the parameter modification instruction; and maps the global structure variables corresponding to the modified second type of parameters to the parameter variables of different modules of the satellite respectively.

[0009] Optionally, different checking and modification methods are used to assign values to the global structure variables according to the characteristics of each type of parameter, including: recording the parameters that need to be maintained during reset and power-off as third-type parameters; for the third-type parameters, the satellite calculates the values of each parameter in the third-type parameters in real time, checks whether the calculated values of each parameter are valid, and if valid, writes the calculated values of each parameter into the global structure variables corresponding to the third-type parameters and the second non-volatile memory.

[0010] Optionally, the second non-volatile memory is a ferroelectric memory.

[0011] Optionally, the method further includes: when the satellite attitude and orbit control system is reset or shut down, the global structure variable corresponding to the third type of parameter obtains the value of the member variable from the second non-volatile memory.

[0012] Optionally, the member variables of the global structure variable are all stored using single-precision floating-point numbers.

[0013] In order to solve the above technical problems, the present invention provides a centralized management device for satellite attitude and orbit control system parameters, including: a memory for storing instructions executable by a processor; a processor for executing the instructions to implement the centralized management method of satellite attitude and orbit control system parameters as described in any of the above items.

[0014] In order to solve the above technical problems, the present invention provides a computer-readable medium storing computer program code, which, when executed by a processor, implements the centralized management method of satellite attitude and orbit control system parameters as described in any one of the above items.

[0015] Compared with the prior art, the present invention has the following advantages: The centralized management method, device and readable medium of the satellite attitude and orbit control system parameters of the present application divide the satellite attitude and orbit control system parameters into three categories of parameters. Different categories of parameters are checked and modified using different strategies, and a global structure variable is created for each category of parameters. The parameters originally scattered in different functional modules are unified into the corresponding single variable, realizing efficient centralized management and online modification of the parameters. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings are included to provide a further understanding of the present application. They are incorporated into and constitute a part of this application. The accompanying drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the accompanying drawings: Figure 1 It is a schematic diagram of a centralized management method of satellite attitude and orbit control system parameters according to an embodiment of the present application.

[0017] Figure 2 This is a flow chart of a centralized management method for satellite attitude and orbit control system parameters according to an embodiment of the present application.

[0018] Figure 3 This is a flowchart of the assignment of global structure variables corresponding to the first type of parameters in an embodiment of the present application.

[0019] Figure 4 This is a flow chart of the assignment of global structure variables corresponding to the second type of parameters in an embodiment of the present application.

[0020] Figure 5 This is a flowchart of the assignment of global structure variables corresponding to the third type of parameters in an embodiment of the present application.

[0021] Figure 6 This is a system block diagram of a centralized management device for satellite attitude and orbit control system parameters according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] To more clearly illustrate the technical solutions of the embodiments of this application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, the drawings described below are merely examples or embodiments of this application. Those skilled in the art can apply this application to other similar scenarios based on these drawings without inventive effort. Unless otherwise apparent from the context or otherwise noted, the same reference numerals in the figures represent the same structure or operation.

[0023] This application aims to address the decentralized parameter management, inefficient modification, and error-prone nature of existing satellite attitude and orbit control systems. By proposing a satellite attitude and orbit control parameter management method based on structured storage and centralized management, this approach integrates parameters previously distributed across various functional modules (such as the attitude determination module, attitude control module, and orbit control module) into corresponding single variables. This approach utilizes different strategies for checking and modifying these parameters, and utilizes a standardized single-precision floating-point format for storage, enabling efficient centralized management and online modification of these parameters.

[0024] This application is applicable to attitude and orbit control systems of various spacecraft, and is particularly suitable for the management and modification of attitude and orbit control parameters of mass-produced satellites. It can provide efficient and reliable parameter management solutions for scenarios such as autonomous satellite control and multi-satellite collaborative management.

[0025] Figure 1 It is a schematic diagram of a centralized management method of satellite attitude and orbit control system parameters according to an embodiment of the present application. Figure 2 This is a flow chart of a centralized management method for satellite attitude and orbit control system parameters according to an embodiment of the present application. Figures 1 and 2 As shown, the centralized management method 100 of satellite attitude and orbit control system parameters includes: Step S1: Divide the satellite attitude and orbit control system parameters into three categories, including parameters with different ground configurations, parameters with the same ground configuration but reserved for on-orbit adjustment, and parameters that need to be maintained during reset and shutdown.

[0026] Step S2: Create a global structure variable for each type of parameter, and use each parameter in each type of parameter as a member variable of the global structure variable.

[0027] The following describes steps S1 and S2 in detail.

[0028] For multiple satellites launched from the same carrier in the same batch, some parameters of the satellite attitude and orbit control system must be configured the same, some must be configured differently, and some parameters must be maintained during reset and shutdown. This application divides the satellite attitude and orbit control system parameters into three categories.

[0029] The first type of parameters are: parameters with different ground configurations.

[0030] These parameters are usually configured during the satellite development phase based on the actual conditions of each satellite and generally do not change during in-orbit operation (unless there are special circumstances, such as hardware reconfiguration). The different parameters configured on the ground include: Hardware characteristic parameters. Due to manufacturing and installation errors, the actual hardware characteristics of each satellite will vary. Hardware characteristic parameters include but are not limited to star sensor installation matrix, gyro installation deviation, solar panel installation angle, thruster installation matrix, and magnetorectron position.

[0031] Satellite structural parameters are parameters related to the satellite's physical structure. These parameters are determined after the satellite is manufactured. Satellite structural parameters include but are not limited to satellite mass, center of mass position, moment of inertia matrix, solar panel area, and reflection coefficient.

[0032] System identification parameters, each satellite has a different identification. System identification parameters include satellite ID, mission code and satellite platform model.

[0033] Create a first global structure variable aocs_ctrl_data_class1 for the first type of parameters. The following is an embodiment of the first global structure variable aocs_ctrl_data_class1: typedef struct { / / Type 1: Different ground configuration parameters struct { float solar_panel_angle; / / Solar panel installation angle float star_sensor_offset[3]; / / star sensor installation matrix float thruster_map

[12] [4]; / / thruster installation matrix } aocs_ctrl_data_class1; Among them, the solar panel installation angle variable solar_panel_angle, the star sensor installation matrix variable star_sensor_offset[3] and the thruster installation matrix variable thruster_map

[12] [4] are all member variables of the first global structure variable aocs_ctrl_data_class1.

[0034] The second type of parameters are: parameters that are the same as the ground configuration but reserved for in-orbit adjustment.

[0035] These parameters are initially configured uniformly for satellites before launch but can be dynamically adjusted during orbit based on mission requirements and system status. Parameters that are configured identically on the ground but remain adjustable in orbit have the following characteristics: all satellites of the same model have the same initial values; some parameters require hot updates to take effect immediately; and they support both ground-based commands and autonomous onboard adjustments.

[0036] Parameters that are the same as the ground configuration but reserved for in-orbit adjustment include: control algorithm parameters, actuator parameters, sensor processing parameters, mode management parameters, health management parameters, etc.

[0037] Among them, the control algorithm parameters include but are not limited to attitude PID proportional gain, attitude PID integral gain, attitude PID differential gain, orbit control threshold and magnetic control damping coefficient.

[0038] Actuator parameters include but are not limited to the maximum flywheel speed, the maximum current of the magnetic torquer, the minimum pulse of the thruster, etc.

[0039] Sensor processing parameters include but are not limited to star sensor noise threshold, sun sensor sensitivity, and gyro filter time constant.

[0040] Mode management parameters include but are not limited to safety mode triggering threshold, momentum wheel unloading threshold and attitude keeping accuracy.

[0041] Health management parameters include but are not limited to temperature alarm thresholds, current abnormality thresholds, and gyroscope zero drift alarm values.

[0042] A second global structure variable aocs_ctrl_data_class2 is created for the second type of parameters. The following is an embodiment of the second global structure variable aocs_ctrl_data_class2: typedef struct { / / Type 2: Same ground configuration but with in-orbit adjustable parameters struct { float attitude_pid_kp[3]; / / attitude PID proportional gain float star_tracker_noise_th; / / Star noise threshold float wheel_max_rpm; / / maximum flywheel speed float temp_alert_th[3]; / / temperature alarm threshold } aocs_ctrl_data_class2; The third type of parameters are: parameters that need to be maintained during reset and shutdown Such parameters usually include key information such as system operating status, equipment life information, calibration data, etc. This information needs to remain unchanged after the system is restarted to ensure system continuity and status traceability.

[0043] The parameters that need to be maintained during reset and shutdown include but are not limited to the satellite's cumulative operating time, the flywheel's cumulative operating time, the number of thruster ignitions, and on-orbit calibration parameters.

[0044] A third global structure variable aocs_ctrl_data_class3 is created for the third type of parameters. The following is an embodiment of the third global structure variable aocs_ctrl_data_class3: typedef struct { / / Type 3: Parameters that need to be maintained during reset and shutdown struct { float total_operation_time; / / cumulative operation time (seconds) float wheel_operating_hours[4]; / / Flywheel operating hours (four flywheels) float thruster_fire_count

[12] ; / / Number of thruster firings (12 thrusters) float mag_calib_matrix[3][3]; / / magnetometer calibration matrix } aocs_ctrl_data_class3; Step S3: Assign values to global structure variables using different checking and modification methods according to the characteristics of each type of parameter.

[0045] Figure 3 This is a flow chart of the assignment of global structure variables corresponding to the first type of parameters in one embodiment of the present application. Figure 3 As shown in the figure, the different parameter assignments for the first type of parameters - ground configuration include: Step S311: Ground preparation stage: Generate a unique parameter binding table for each satellite (mainly including different ground configuration parameters).

[0046] Step S312: Ground check: Check the parameter binding table of each satellite.

[0047] A three-level inspection system can be used during ground inspections. First, the automated software is verified, then it is manually reviewed by experts, and then compared with other satellites to see if there are any abnormalities. If all three levels of inspection are passed, a certificate of conformity for the parameter binding table will be issued.

[0048] Step S313: Annotation: Bind the parameter binding table that has been checked to be correct to the corresponding satellite by annotating it.

[0049] Step S314: Secondary determination on board: After receiving the parameter binding table, the satellite performs validity verification, which includes but is not limited to CRC check and range check.

[0050] Step S315: writing into the global structure: after verification, the data in the parameter binding table is written into the global structure variables corresponding to the first type of parameters (different parameters configured on the ground) in the satellite attitude and orbit control system.

[0051] The centralized management method of satellite attitude and orbit control system parameters in this application supports differentiated configuration of multiple satellites. In order to solve the problem of differentiated parameters of different satellites in mass-produced models, a separate binding method is adopted to realize online modification of parameters, and the parameters are automatically updated to the full attitude and orbit control parameter variables after verification, thereby improving the flexibility and adaptability of the system.

[0052] Figure 4 This is a flow chart of the assignment of global structure variables corresponding to the second type of parameters in one embodiment of the present application. Figure 4 As shown, the assignment process of the global structure variables corresponding to the second type of parameters includes: Step S321: Ground preparation stage: Generate a unified parameter table for satellites of the same model (same ground configuration).

[0053] Step S322: Check the unified parameter table. If the unified parameter table is correct, store it in the first non-volatile memory of the plurality of satellites in the same batch.

[0054] Step S323: when initializing the global structure variables corresponding to the second type of parameters, the values of the member variables are obtained from the unified parameter table in the first non-volatile memory.

[0055] In addition, since the second type of parameters are adjustable on-track, when the values of the second type of parameters in multiple modules need to be adjusted, the following steps are also included: Step S324: The satellite determines whether a parameter modification instruction is received. If so, the satellite modifies the global structure variables corresponding to the second type of parameters according to the parameter modification instruction.

[0056] The global structure variables corresponding to the modified second type of parameters are mapped to the parameter variables of different modules of the satellite.

[0057] Figure 5 This is a flow chart of the assignment of global structure variables corresponding to the third type of parameters in one embodiment of the present application. Figure 4 As shown, the assignment process of the global structure variables corresponding to the second type of parameters includes: Step S331: The satellite calculates the value of each parameter in the third category in real time.

[0058] Step S332: Check whether the calculated values of each parameter are valid. If valid, proceed to step S333.

[0059] Step S333: writing the calculated values of the parameters into the global structure variables corresponding to the third type of parameters and the second non-volatile memory.

[0060] Taking the thruster ignition count as an example, the thruster ignition count is refreshed periodically. Determine whether the updated thruster ignition count is within the specified range. For example, the specified range of the thruster ignition count is 0-50,000 times. If it is out of range, the updated thruster ignition count is invalid. If it is within the range, the rate of change of the thruster ignition count can be checked. For example, the rate of change constraint range of the thruster ignition count is <10 times / second. If the rate of change of the thruster ignition count exceeds the rate constraint range, the updated thruster ignition count is invalid. Otherwise, the updated thruster ignition count is valid. Write the updated thruster ignition count into the global structure variable corresponding to the third type of parameter and the second non-volatile memory.

[0061] As can be seen from the above, the third type of parameters are updated frequently and need to be saved after power failure. Preferably, the second non-volatile memory is a ferroelectric memory. Ferroelectric memory has the characteristics of unlimited write and low power consumption, which is very suitable for storing the third type of parameters.

[0062] Optionally, the method further includes: when the satellite attitude and orbit control system is reset or shut down, the global structure variable corresponding to the third type of parameter obtains the value of the member variable from the second non-volatile memory.

[0063] Step S4: Map the global structure variables to the parameter variables of different satellite modules.

[0064] It's important to understand that each module in the satellite attitude and orbit control system doesn't directly access global structure variables. Instead, it obtains pointers to the parameters it needs. This way, when parameters need to be updated, simply update the global structure variables, and each module automatically obtains the latest values through the pointers. This approach avoids duplicate parameter definitions across multiple modules, ensuring consistency; centralizes data updates, reducing errors; and provides clear module interfaces, allowing each module to focus solely on the parameters it needs.

[0065] like Figure 1As shown in the figure, the satellite attitude and orbit control system includes a sensor processing module, an attitude control module, and an orbit control module. During initialization, the parameter pointer of each module is pointed to the corresponding member variable in the global structure variable. For example, the attitude PID proportional gain parameter kp in the attitude control module is pointed to the member variable attitude_pid_kp[3] of the second global structure variable aocs_ctrl_data_class2. When the attitude PID proportional gain parameter kp in multiple modules needs to be updated, only the member variable attitude_pid_kp[3] of the second global structure variable aocs_ctrl_data_class2 needs to be updated.

[0066] Optionally, all member variables of the global structure are stored as single-precision floating-point numbers. Integer parameters are forcibly converted to single-precision floating-point type for storage, and double-precision floating-point parameters are also forcibly converted to single-precision floating-point type for storage.

[0067] Parameter storage uses a standardized single-precision floating-point format, ensuring consistent data storage and optimizing memory usage. For a typical satellite attitude and orbit control system, the global parameter structure contains 300-500 parameters. Using single-precision floating-point numbers for storage saves memory and reduces bandwidth requirements for satellite-to-ground communications.

[0068] This application proposes a method for centralized management and modification of satellite attitude and orbit control parameters. This method categorizes the parameters of various modules in the attitude and orbit control system into three main categories and centralizes them into three variables for management. This allows the value of only one variable to be modified and mapped to the corresponding modules.

[0069] At the same time, corresponding inspection and modification methods have been designed for each different parameter category, which not only improves the efficiency of parameter modification and verification, but also maintains module cohesion. For the first type of parameters, for each different satellite, only an Excel spreadsheet needs to be checked and modified. The parameters are then added to the satellite's storage area through binding, and then mapped to the corresponding modules through a secondary mapping process. For the second type of parameters, only the values in the corresponding parameter variables need to be checked and modified, and the modified variable values are then mapped to the corresponding modules. For the third type of parameters, only specific instructions need to be sent to complete the inspection and modification. The parameters are also distributed to each module through a secondary mapping process.

[0070] The present application also provides a centralized management device for satellite attitude and orbit control system parameters.

[0071] Figure 6 This is a system block diagram of a centralized management device for satellite attitude and orbit control system parameters according to an embodiment of the present application. Figure 6As shown, the centralized management device 600 for satellite attitude and orbit control system parameters may include an internal communication bus 601, a processor 602, a read-only memory (ROM) 603, a random access memory (RAM) 604, and a communication port 605. When used on a personal computer, the centralized management device 600 for satellite attitude and orbit control system parameters may also include a hard disk 606. The internal communication bus 601 enables data communication between the components of the centralized management device 600. The processor 602 can make judgments and issue prompts. In some embodiments, the processor 602 may be composed of one or more processors. The communication port 605 enables data communication between the centralized management device 600 and the external environment. In some embodiments, the centralized management device 600 can send and receive information and data from a network via the communication port 605. The centralized management device 600 for satellite attitude and orbit control system parameters may also include various forms of program storage units and data storage units, such as a hard disk 606, a read-only memory (ROM) 603, and a random access memory (RAM) 604. These can store various data files used for computer processing and / or communication, as well as possible program instructions executed by the processor 602. The processor executes these instructions to implement the main part of the method. The results of the processor processing are transmitted to the user device via a communication port and displayed on the user interface.

[0072] The above-mentioned operating method can be implemented as a computer program, stored in the hard disk 606, and loaded into the processor 602 for execution to implement the centralized management method of satellite attitude and orbit control system parameters of the present application.

[0073] The present application also includes a computer-readable medium storing computer program code, which, when executed by a processor, implements the aforementioned method for centralized management of satellite attitude and orbit control system parameters.

[0074] When the centralized management method of satellite attitude and orbit control system parameters is implemented as a computer program, it can also be stored in a computer-readable storage medium as a product. For example, a computer-readable storage medium may include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs)), smart cards, and flash memory devices (e.g., electrically erasable programmable read-only memories (EPROMs), cards, sticks, key drives). In addition, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media (and / or storage media) that can store, contain, and / or carry code and / or instructions and / or data.

[0075] The basic concepts have been described above. It will be apparent to those skilled in the art that the above disclosures are merely illustrative and do not constitute limitations on this application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and amendments to this application. Such modifications, improvements, and amendments are suggested in this application and remain within the spirit and scope of the exemplary embodiments of this application.

[0076] At the same time, this application uses specific terms to describe the embodiments of this application. For example, "one embodiment," "an embodiment," and / or "some embodiments" refer to a certain feature, structure, or characteristic related to at least one embodiment of this application. Therefore, it should be emphasized and noted that "one embodiment," "an embodiment," or "an alternative embodiment" mentioned twice or multiple times in different locations in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this application may be appropriately combined.

[0077] Some aspects of this application may be implemented entirely in hardware, entirely in software (including firmware, resident software, microcode, etc.), or a combination of hardware and software. These hardware and software components may be referred to as "data blocks," "modules," "engines," "units," "components," or "systems." A processor may be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. Furthermore, various aspects of this application may be embodied as computer products embodied in one or more computer-readable media, including computer-readable program code. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact disks, digital versatile disks, DVDs), smart cards, and flash memory devices (e.g., cards, sticks, key drives, etc.).

[0078] A computer-readable medium may include a propagated data signal embodying computer program code, for example, in baseband or as part of a carrier wave. The propagated signal may be in a variety of forms, including electromagnetic, optical, etc., or a suitable combination thereof. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium that can be connected to an instruction execution system, apparatus, or device to communicate, propagate, or transmit the program for use. The program code on the computer-readable medium may be transmitted via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above.

[0079] Similarly, it should be noted that, in order to simplify the presentation of this disclosure and thereby facilitate understanding of one or more embodiments of the invention, the foregoing descriptions of the embodiments of this application sometimes combine multiple features into a single embodiment, figure, or description thereof. However, this disclosure method does not imply that the subject matter of this application requires more features than those mentioned. In fact, an embodiment may have fewer features than all of the features of a single embodiment disclosed above.

[0080] As used herein, unless the context clearly indicates otherwise, the terms "a," "an," "an," and / or "the" are not intended to refer to the singular but may include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements specifically identified, and these steps and elements do not constitute an exclusive list. A method or apparatus may also include other steps or elements.

[0081] Unless otherwise specified, the relative arrangement of the parts and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present application. Meanwhile, it should be understood that, for ease of description, the sizes of the various parts shown in the accompanying drawings are not drawn according to actual proportional relationships. Technology, methods and equipment known to those of ordinary skill in the relevant art may not be discussed in detail, but in appropriate cases, the technology, methods and equipment should be considered as a part of the specification. In all examples shown and discussed here, any specific value should be interpreted as being merely exemplary, rather than as a limitation. Therefore, other examples of exemplary embodiments can have different values. It should be noted that similar numbers and letters represent similar items in the following drawings, and therefore, once an item is defined in an accompanying drawing, it does not need to be further discussed in subsequent drawings.

[0082] Furthermore, it should be noted that the use of terms such as "first" and "second" to define components is solely for the purpose of distinguishing the corresponding components. Unless otherwise stated, these terms have no special meaning and therefore should not be construed as limiting the scope of protection of this application. Furthermore, while the terms used in this application are selected from commonly known and commonly used terms, some terms mentioned in this specification may have been selected by the applicant at his or her discretion, and their detailed meanings are explained in the relevant sections of this description. Furthermore, this application should be understood not only by the actual terms used, but also by the meaning implied by each term.

[0083] Flowcharts are used in this application to illustrate the operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, the various steps may be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0084] Although the present application has been described with reference to the current specific embodiments, ordinary technicians in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions can be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the scope of the essential spirit of the present application, they will fall within the scope of the present application.

Claims

1. A method for centralized management of satellite attitude and orbit control system parameters, characterized in that: include: The satellite attitude and orbit control system parameters are divided into three categories: parameters that are different in ground configuration, parameters that are the same in ground configuration but reserved for on-orbit adjustment, and parameters that need to be maintained during reset and shutdown; Create a global structure variable for each type of parameter, and use each parameter in each type of parameter as a member variable of the global structure variable; Assigning values to the global structure variables using different checking and modification methods according to the characteristics of each type of parameter; The global structure variables are mapped to parameter variables of different modules of the satellite respectively.

2. The method for centralized management of satellite attitude and orbit control system parameters according to claim 1, wherein: Different checking and modification methods are used to assign values to the global structure variables according to the characteristics of each type of parameter, including: Record the different parameters of the ground configuration as first-category parameters; For the first type of parameters, before launching each batch of satellites, the parameter binding table of each satellite is checked. Different satellites have different corresponding parameter binding tables. After checking that they are correct, the parameter binding table is bound to the satellite by annotation. After the satellite performs a second judgment on the parameter binding table and determines that the parameter binding table is valid, the satellite writes the parameter binding table into the global structure variable corresponding to the first type of parameters.

3. The method for centralized management of satellite attitude and orbit control system parameters according to claim 1, wherein: Different checking and modification methods are used to assign values to the global structure variables according to the characteristics of each type of parameter, including: The parameters that are identical to the ground configuration but reserved for on-orbit adjustment are recorded as the second type of parameters; For the second type of parameters, before launching each batch of satellites, a unified parameter table is checked. After the check is correct, the unified parameter table is stored in the first non-volatile memory of multiple satellites in the same batch; When the global structure variables corresponding to the second type of parameters are initialized, the values of the member variables are obtained from the unified parameter table in the first non-volatile memory.

4. The method for centralized management of satellite attitude and orbit control system parameters according to claim 3, wherein: Also includes: The satellite determines whether a parameter modification instruction is received, and if so, modifies the global structure variable corresponding to the second type of parameter according to the parameter modification instruction; The global structure variables corresponding to the modified second type of parameters are mapped to the parameter variables of different modules of the satellite.

5. The method for centralized management of satellite attitude and orbit control system parameters according to claim 1, wherein: Different checking and modification methods are used to assign values to the global structure variables according to the characteristics of each type of parameter, including: The parameters that need to be maintained during reset and shutdown are recorded as the third type of parameters; For the third type of parameters, the satellite calculates the value of each parameter in the third type of parameters in real time, checks whether the calculated value of each parameter is valid, and if valid, writes the calculated value of each parameter into the global structure variable corresponding to the third type of parameters and the second non-volatile memory.

6. The centralized management method of satellite attitude and orbit control system parameters according to claim 5, characterized in that: The second non-volatile memory is a ferroelectric memory.

7. The centralized management method for satellite attitude and orbit control system parameters according to claim 6, characterized in that: Also includes: When the satellite attitude and orbit control system is reset or shut down, the global structure variables corresponding to the third type of parameters obtain the values of the member variables from the second non-volatile memory.

8. The method for centralized management of satellite attitude and orbit control system parameters according to claim 1, wherein: The member variables of the global structure variable are all stored using single-precision floating-point numbers.

9. A centralized management device for satellite attitude and orbit control system parameters, characterized in that: include: a memory for storing instructions executable by the processor; A processor, configured to execute the instructions to implement the centralized management method for satellite attitude and orbit control system parameters as described in any one of claims 1 to 8.

10. A computer-readable medium storing computer program code, wherein when the computer program code is executed by a processor, the method for centralized management of satellite attitude and orbit control system parameters according to any one of claims 1 to 8 is implemented.

Images