On-orbit reconstruction method for satellite-borne software supporting interface multiplexing

Abstract

According to the satellite-borne software on-orbit reconstruction method and system supporting interface multiplexing, the working mode of a communication interface is expanded and designed, compatibility of normal data communication and a software reconstruction function is achieved, a set of complete load software on-orbit processing flow is provided, and the compatibility between the normal data communication and the software reconstruction function is improved. A load software reconstruction function is realized under the condition that large-scale development and modification are not carried out, so that satellite software in-orbit reconstruction is not limited to reconstruction of satellite service platform software. The method supports satellite-borne software parameter modification, dynamic library updating, software version replacement and multi-stage reconstruction, supports interface reuse, does not need a load to have a special code reconstruction channel, saves resources, simplifies design, and improves the flexibility, safety and reliability of the satellite load.

Description

Technical Field

[0001] The present invention relates to space technology, and particularly to an on-orbit reconfiguration method for on-board software that supports interface reuse. Background Art

[0002] In the current space technology field, the on-orbit reconfiguration technology of on-board software is still in the development stage, and its maturity and standardization need to be improved. Most of the existing reconfiguration schemes are limited to the update of the on-board platform software. For on-board software, usually only the adjustment of basic parameters can be achieved. More complex operations such as the function upgrade and fault repair of on-orbit software have not been fully considered in the design, which limits the flexibility and reliability of the system. Although some payload devices have the ability of on-orbit software reconfiguration, these schemes are often complex in design. The payload needs to add a dedicated software reconfiguration channel, and there is a lack of unified standards and specifications, which increases the implementation cost and complexity and is not conducive to practical application and popularization. Summary of the Invention

[0003] The present invention provides an on-orbit reconfiguration method for on-board software that supports interface reuse, which is characterized by including:

[0004] When on-orbit reconfiguration of payload software is required, the ground measurement and control system sends an instruction to start software upload to the satellite;

[0005] After receiving the instruction, the on-board measurement and control data transmission system forwards the instruction to the platform computer;

[0006] After receiving the instruction, the platform computer switches the working mode of the data transmission interface connected to the payload from the normal working mode to the software upload mode, pauses the normal data transmission with the payload, and forwards the instruction to the payload through the control bus;

[0007] After receiving the instruction, the payload switches the current working mode from the normal working mode to the software upload mode. In the software upload mode, the data transmission interface of the payload is only used to receive program package data, and sends telemetry data through the control bus to return the current program package upload status to the ground measurement and control system, where the program package upload status includes the number of uploaded data packets, the writing status, the program package verification status, the program version number, and the update time;

[0008] The ground measurement and control system divides the program package into multiple data packets for upload. The data packets are spliced on the satellite and correctness verification is performed. If there are missing program packages, the missing program packages are re-uploaded;

[0009] After the program package upload is completed and passes the verification, the ground measurement and control system sends a software reconfiguration instruction to the satellite, and the payload performs software update after receiving the software reconfiguration instruction; and

[0010] The ground TT&C system sends a command to upload the shutdown software, enabling the payload and the platform computer to resume their normal operating modes and conducting functional verification.

[0011] In an embodiment of the present invention, the step in which the ground TT&C system divides the program package into multiple data packets for uploading includes:

[0012] The ground TT&C system sends the payload software package to the satellite, dividing the program package into multiple data packets for uploading;

[0013] The on-board TT&C and data transmission system sends the data packets to the payload through the platform computer via the data transmission interface;

[0014] The payload receives, splices, stores, and verifies the data packets. Among them, the splicing work of the data packets can also be completed by the platform software, which is not limited in the present invention; and

[0015] The reception status of each data packet, the verification status of the program package, etc. are transmitted to the ground TT&C system through telemetry.

[0016] In another embodiment of the present invention, if some of the data packets fail to be transmitted, they are re-uploaded separately.

[0017] In another embodiment of the present invention, the method further has a code version rollback function. If a version rollback is required, a version rollback command is sent to implement the version rollback of the on-board payload software.

[0018] The present invention also provides an on-board software on-orbit reconfiguration system supporting interface multiplexing, which is characterized by including:

[0019] A control bus, connecting the payload, the platform computer, and the on-board TT&C and data transmission system, for transmitting telecommand and telemetry information;

[0020] A data transmission channel, connecting the platform computer to the payload and the platform computer to the on-board TT&C and data transmission system, for transmitting data;

[0021] A ground TT&C system, configured to send telecommand instructions and data packets, and receive telemetry data to monitor the satellite status;

[0022] An on-board TT&C and data transmission system, configured to receive and forward the telecommand instructions and data packets uploaded by the ground TT&C system to the platform computer, and send telemetry data and data transmission data to the ground TT&C system;

[0023] The platform computer is configured to receive the remote control instructions and data packets uploaded by the ground TT&C system and relayed by the on-satellite TT&C and data transmission system. When it receives the software upload instruction, it switches the data transmission working mode to the software upload mode, and forwards the instruction to the payload through the control bus. After receiving the software data packet, it sends the data packet to the payload through the data transmission interface; and,

[0024] The payload is configured to receive control instructions and data. When it is in the software upload mode, the data transmission interface is only used to receive the software upload data packets from the platform computer; when it is in the normal working mode, it conducts normal data transmission with the platform computer.

[0025] In an embodiment of the present invention, when the payload receives the software upload start instruction, the payload switches to the software upload working mode and pauses the normal payload data transmission. When it is in the software upload mode, the data transmission interface of the payload is only used to receive the program package data.

[0026] In another embodiment of the present invention, it is characterized in that the remote control instructions include:

[0027] The software upload start instruction, which is configured to make the central computer and the payload switch to the software upload mode, and the data transmission channel stops normal data transmission and is used to transmit software reconstruction data packets;

[0028] The software upload stop instruction, which is configured to make the central computer and the payload switch to the normal working mode, and the data transmission channel resumes normal data transmission;

[0029] The program loading and start instruction, which is configured to make the payload load and start a new version of the program, and the program version to be loaded and started can be set through parameters;

[0030] The version rollback instruction, which is configured to make the payload load and start the previous version of the program; and

[0031] The data packet upload instruction: which is configured to upload data packets through the satellite uplink TT&C link.

[0032] In another embodiment of the present invention, there is a remote control and telemetry link between the on-satellite TT&C and data transmission system and the ground TT&C system.

[0033] In another embodiment of the present invention, the data transmission interface has a normal working mode and a software upload mode, and switches according to the remote control instruction. In the software upload mode, the original data transmission interface of the payload is used for the on-orbit reconstruction of the payload software.

[0034] In another embodiment of the present invention, the payload does not need to set a dedicated software reconstruction hardware interface, but realizes the on-orbit reconstruction of the payload software by reusing the original data transmission channel.

[0035] The present invention proposes a set of general on-orbit software code refactoring solutions, which support multi-level refactoring such as on-orbit software parameter modification, dynamic library update, and software version replacement, support interface reuse, and do not require the payload to have a dedicated code refactoring channel, and have the following beneficial effects:

[0036] (1) A complete set of on-orbit processing procedures for payload software is proposed, which realizes the function of payload software refactoring without large-scale development and modification, enabling on-orbit refactoring of satellite software not only limited to the refactoring of the satellite bus platform software, but also facilitating the refactoring of important payload software quickly and conveniently, improving the reliability and functional expandability of the satellite.

[0037] (2) This solution does not require adding dedicated software refactoring interfaces, but realizes the reuse of data communication interfaces that are commonly available in important payload software, expands the design of the working mode of the communication interface, and realizes the compatibility of normal data communication and software refactoring functions. The solution is simple and efficient and easy to implement.

[0038] (3) This solution comprehensively considers different software refactoring methods, including partial program update of the dynamic library, complete software refactoring, etc., is applicable to various software and hardware platforms, and has strong versatility and scalability. A complete set of relevant telecommand instructions, telemetry quantities, and complete processing procedures are designed, providing important reference for the formulation of on-orbit refactoring solutions for payload software in specific satellite models quickly and conveniently. Brief Description of the Drawings

[0039] Figure 1 Shows a schematic diagram of an on-orbit software refactoring system in an embodiment of the present invention;

[0040] Figure 2 Shows a block diagram of software module composition in an embodiment of the present invention;

[0041] Figure 3 Shows a processing flow chart of the payload software end in an embodiment of the present invention; and

[0042] Figure 4 Shows a composition diagram of a satellite system in an embodiment of the present invention. Detailed Embodiments

[0043] In the following description, the present invention is described with reference to the embodiments. However, those skilled in the art will recognize that the embodiments can be implemented without one or more specific details or in combination with other alternative and / or additional methods, materials, or components. In other cases, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring the inventive points of the present invention. Similarly, for the purpose of explanation, specific quantities, materials, and configurations are set forth to provide a comprehensive understanding of the embodiments of the present invention. However, the present invention is not limited to these specific details.

[0044] In this specification, the reference to "one embodiment" or "the embodiment" means that the specific features, structures, or characteristics described in connection with the embodiment are included in at least one embodiment of the present invention. The phrase "in one embodiment" appearing throughout this specification does not necessarily refer to the same embodiment.

[0045] Figure 1 The schematic diagram of the on-orbit reconfiguration system of the spaceborne software in one embodiment of the present invention is shown.

[0046] As Figure 1 shown, the present invention provides an on-orbit reconfiguration system of spaceborne software that supports interface reuse, including:

[0047] Payload, platform computer, on-board TT&C data transmission system, and ground TT&C system. The payload, platform computer, and TT&C data transmission system on the satellite are all connected to the control bus. In the embodiment of the present invention, the CAN bus is used, but obviously, it is not limited to the CAN bus, and the present invention does not make any restrictions here. The platform computer is connected to the payload and the on-board TT&C data transmission system through data transmission interfaces.

[0048] The on-orbit reconfiguration of the spaceborne software of the present invention is mainly divided into the following stages:

[0049] (1) Instruction sending stage: The ground TT&C system sends the upload instruction of the payload software to the satellite through the telecommand and telemetry link. As Figure 1 shown in ①, the on-board TT&C data transmission system and the ground TT&C system form a telecommand and telemetry link through the antenna, and data interaction is carried out therefrom.

[0050] (2) Instruction reception and forwarding: After receiving the instruction, the on-board TT&C data transmission system forwards the instruction to the platform computer. As Figure 1 shown in ②. In this embodiment, the instruction is processed by the platform computer; in other embodiments, it can also be processed by a dedicated payload management unit, and the present invention does not make any restrictions on this.

[0051] (3) Data transmission interface working mode switching: The platform computer switches the working mode of the data transmission interface connected to the payload from the "normal working mode" to the "software upload mode", pauses the normal data transmission with the payload, and forwards the software upload start instruction to the payload through the control bus, as Figure 1 shown in ③.

[0052] (4) Payload mode switching: After receiving the software upload instruction, the payload switches its working mode to the "software upload mode", pauses the normal data transmission, and the data transmission interface is only used to receive the program package at this time, prepares to receive the program package, and returns the current state through the telemetry data.

[0053] (5) Software package uploading note: The ground divides the program package into multiple data packets for uploading. The data packets are sent to the payload through the TT&C system and the platform computer (or payload processing unit) via the data transmission interface. The payload software receives, splices, stores, and verifies the data packets, and at the same time transmits the status to the ground TT&C system via telemetry, including the number of uploaded data packets, writing status, program package verification status, program version number, and update time. For data packets with unsuccessful transmission, separate re-uploading is supported. As shown in ①②④ in Figure 1 . Figure 1 As shown in ①②④ in Figure 1 .

[0054] (6) Software update: After the program package verification passes, the ground uploading software reconstructs the instruction. After receiving this instruction, the payload performs software update and reloads or restarts according to different reconstruction methods to complete the on-orbit software reconstruction. As shown in ①②③ in Figure 1 . Figure 1 As shown in ①②③ in Figure 1 .

[0055] (7) Working state restoration or software version rollback: Referring to the above process, the ground sends a remote control instruction to turn off the code reconstruction mode, and the payload and the platform computer restore the normal working mode for function verification. If a version rollback is required, a software version rollback instruction is sent to perform the software version rollback of the payload.

[0056] In this embodiment, through interface multiplexing, the data transmission interface performs normal payload data transmission in the normal mode and data packet transmission in the software uploading mode. There is no need for the payload to have a dedicated code reconstruction channel, which saves resources, simplifies the design, and improves the flexibility, safety, and reliability of the satellite payload.

[0057] The software data packet format and the telecommand and telemetry data format in the present invention use the general satellite uploading large data packet format and the TT&C protocol, which are not elaborated in the present invention.

[0058] Figure 2 The block diagram of the software module composition in an embodiment of the present invention is shown.

[0059] The software implementing this solution includes payload software, on-board (or payload management) platform software (hereinafter referred to as platform software), and ground TT&C system. The payload software receives control instructions and program packages to implement software update and loading; the platform software receives telecommand instructions and large data packets uploaded from the ground (received and forwarded by the TT&C system) to control the working modes of the payload and data transmission and send data packets, etc. The ground TT&C system can follow the current general mode and functions without special modifications for the present invention.

[0060] The payload software mainly includes: a communication interface module for realizing data transmission functions; a telecommand and telemetry module for parsing and processing telecommand instructions, performing corresponding operations, and returning payload telemetry information; a code refactoring and loading module for realizing software refactoring-related functions such as splicing, storing, verifying software data packets, and software loading; and a payload function module, i.e., the original function module of the payload single machine. The splicing of software data packets can also be completed by the platform computer, and there is no mandatory constraint in the present invention.

[0061] The platform computer software mainly includes: a communication interface module for realizing data transmission functions, having two working modes of software uploading mode and normal mode, and switching according to telecommand instructions; a big data processing module for receiving and processing data packets uploaded from the ground; a telecommand and telemetry module for realizing telecommand instruction processing, telemetry data packet assembly, etc., and other function modules, such as conventional function modules like satellite bus management and payload management.

[0062] Figure 3 Fig. shows the processing flow chart of the payload software end in an embodiment of the present invention.

[0063] As can be seen from the figure, during the on-orbit refactoring of the on-board software, the instructions received by the payload are divided into the following categories:

[0064] A software uploading start instruction, which is configured to switch the payload to the software uploading mode and stop normal payload data transmission;

[0065] A software uploading stop instruction, which is configured to switch the payload to the normal working mode and resume normal payload data transmission;

[0066] A program loading and start instruction, which is configured to enable the payload to load and start a new version program, supporting software versions started through parameter settings; and

[0067] A version rollback instruction, which is configured to enable the payload to load and start the previous version program;

[0068] A data packet uploading instruction: which is configured to upload data packets through the satellite uplink TT&C link.

[0069] Figure 4 Fig. shows the composition diagram of the satellite system in an embodiment of the present invention.

[0070] The present invention is applicable to the on-orbit refactoring of satellite payload software with high importance, complex functions, and data transmission interfaces, and is described by taking the on-orbit refactoring of CPU software as an example. Next, for a specific system, the feasibility of the present invention is verified. In an embodiment of the present invention, the inventor used this solution to complete the development and implementation of the on-orbit refactoring function of the GNC control board software of a certain type of satellite. For the composition of the satellite system, see Figure 4Among them, the central machine and the GNC control board use an RS422 interface for data transmission, and at the same time, it is multiplexed as a code refactoring interface, and the code refactoring function verification is realized by this solution. The test verification shows that this solution is feasible and has practical value.

[0071] Although the embodiments of the present invention have been described above, it should be understood that they are presented only as examples and not as limitations. It will be apparent to those skilled in the relevant art that various combinations, variations, and changes can be made without departing from the spirit and scope of the present invention. Therefore, the width and scope of the present invention disclosed herein should not be limited by the exemplary embodiments disclosed above, but should be defined only by the appended claims and their equivalents.

Claims

1. A on-orbit reconfiguration method for on-board software supporting interface reuse, characterized in that Including: When on-orbit reconstruction of the payload software is required, the ground TT&C system sends an instruction to start software uploading to the satellite; The on-board TT&C and data transmission system forwards the instruction to the platform computer after receiving the instruction; After receiving the instruction, the platform computer switches the working mode of the data transmission interface connected to the payload from the normal working mode to the software uploading mode, pauses the normal data transmission with the payload, and forwards the instruction to the payload through the control bus; After receiving the instruction, the payload switches its current working mode from the normal working mode to the software uploading mode. In the software uploading mode, the data transmission interface of the payload is only used to receive program package data, and sends telemetry data through the control bus to return the current program package uploading status to the ground TT&C system, where the program package uploading status includes the number of uploaded data packets, writing status, program package verification status, program version number, and update time; The ground TT&C system divides the program package into multiple data packets for uploading. The data packets are spliced on the satellite and correctness verification is performed. If there are missing program packages, the missing program packages are re-uploaded; After the program package uploading is completed and passes the verification, the ground TT&C system sends a software reconstruction instruction to the satellite, and the payload performs software update after receiving the software reconstruction instruction; And The ground TT&C system sends an instruction to close software uploading, so that the payload and the platform computer resume the normal working mode and perform function verification.

2. The on-orbit reconfiguration method of the spaceborne software supporting interface reuse according to claim 1, characterized in that The step in which the ground TT&C system divides the program package into multiple data packets for uploading includes: The ground TT&C system sends the payload software package to the satellite and divides the program package into multiple data packets for uploading; The on-board TT&C and data transmission system sends the data packets to the payload through the data transmission interface via the platform computer; The payload receives, splices, stores, and verifies the data packets. Among them, the splicing work of the data packets can also be completed by the platform software, which is not limited in the present invention; and The reception status of each data packet, the program package verification status, etc. are transmitted to the ground TT&C system through telemetry.

3. The on-orbit reconfiguration method of the spaceborne software supporting interface reuse according to claim 2, characterized in that, If some of the data packets fail to be transmitted, they are re-uploaded separately.

4. The on-orbit reconfiguration method of the spaceborne software supporting interface reuse according to claim 1, characterized in that The method also has a function of rolling back the code version. If a version rollback is required, a version rollback instruction is sent to implement the rollback of the on-board payload software version.

5. A on-orbit reconstruction system for on-board software that supports interface reuse, characterized in that, Including: The control bus connects the payload, the platform computer, and the on-board TT&C and data transmission system for transmitting telecommand and telemetry information; The data transmission channel connects the platform computer to the payload and the platform computer to the on-board TT&C and data transmission system for transmitting data; The ground TT&C system is configured to send telecommand instructions and data packets and receive telemetry data to monitor the satellite status; The on-board TT&C and data transmission system is configured to receive and forward the telecommand instructions and data packets uploaded by the ground TT&C system to the platform computer, and send telemetry data and data transmission data to the ground TT&C system; The platform computer is configured to receive the remote control instructions and data packets uploaded by the ground TT&C system and relayed by the on-board TT&C and data transmission system. When it receives the software upload instruction, it switches the data transmission working mode to the software upload mode, forwards the instruction to the payload through the control bus, and sends the data packet to the payload through the data transmission interface after receiving the software data packet; And, The payload is configured to receive control instructions and data. When it is in the software upload mode, the data transmission interface is only used to receive the software upload data packet from the platform computer; when it is in the normal working mode, it conducts normal data transmission with the platform computer.

6. The on-orbit reconfiguration system of spaceborne software supporting interface reuse as claimed in claim 5, wherein When the payload receives the software upload start instruction, the payload switches to the software upload working mode and pauses the normal payload data transmission. When it is in the software upload mode, the data transmission interface of the payload is only used to receive the program package data.

7. The on-orbit reconfiguration system of spaceborne software supporting interface multiplexing according to claim 5, characterized in that The remote control instructions include: The software upload start instruction, which is configured to make the central computer and the payload switch to the software upload mode, and the data transmission channel stops normal data transmission and is used to transmit software reconstruction data packets; The software upload stop instruction, which is configured to make the central computer and the payload switch to the normal working mode, and the data transmission channel resumes normal data transmission; The program loading start instruction, which is configured to make the payload load and start a new version of the program, and the program version to be loaded and started can be set through parameters; The version rollback instruction, which is configured to make the payload load and start the previous version of the program; and The data packet upload instruction: which is configured to upload data packets through the satellite uplink TT&C link.

8. The on-orbit reconfiguration system of spaceborne software supporting interface reuse according to claim 5, characterized in that, There is a remote control and telemetry link between the on-board TT&C and data transmission system and the ground TT&C system.

9. The on-orbit reconfiguration system of spaceborne software supporting interface reuse as claimed in claim 5, wherein The data transmission interface has a normal working mode and a software upload mode, and is switched according to the remote control instruction. In the software upload mode, the original data transmission interface of the payload is used for on-orbit reconstruction of the payload software.

10. The on-orbit reconfiguration system of spaceborne software supporting interface reuse as claimed in claim 5, characterized in that, The payload does not need to set a dedicated software reconstruction hardware interface, but realizes on-orbit reconstruction of the payload software by reusing the original data transmission channel.

Images