CN110474673B - Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission - Google Patents

Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission Download PDF

Info

Publication number
CN110474673B
CN110474673B CN201910778871.9A CN201910778871A CN110474673B CN 110474673 B CN110474673 B CN 110474673B CN 201910778871 A CN201910778871 A CN 201910778871A CN 110474673 B CN110474673 B CN 110474673B
Authority
CN
China
Prior art keywords
file
hot
orbit
patch
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910778871.9A
Other languages
Chinese (zh)
Other versions
CN110474673A (en
Inventor
白亮
韦杰
田文波
钱丰
邱源
陆灵君
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai aerospace computer technology research institute
Original Assignee
Shanghai aerospace computer technology research institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai aerospace computer technology research institute filed Critical Shanghai aerospace computer technology research institute
Priority to CN201910778871.9A priority Critical patent/CN110474673B/en
Publication of CN110474673A publication Critical patent/CN110474673A/en
Application granted granted Critical
Publication of CN110474673B publication Critical patent/CN110474673B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851Systems using a satellite or space-based relay
    • H04B7/18519Operations control, administration or maintenance
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Radio Relay Systems (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a dynamic on-orbit thermal updating method supporting breakpoint continuous transmission, which comprises the following basic steps of: the first step is as follows: remotely controlling the upstream injection patch data packet; the second step is as follows: checking the integrity and the validity of the data of the upper patch package; the third step: generating a new check file; the fourth step: generating an MD5 check value file corresponding to the on-track hot update patch package data file; the fifth step: modifying the newly generated on-track hot update patch package data file and the MD5 check value file name; a sixth step: and informing the corresponding process to restart or remap the function information in the hot updating patch package. The invention aims at the satellite-borne software system which is based on the operating system and runs in the virtual address space, can carry out dynamic hot update on the functions of the satellite-borne software module or a single function, and has great expandability and convenience.

Description

Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission
Technical Field
The invention relates to the technical field of satellite-borne embedded software, in particular to a dynamic on-orbit thermal updating method supporting breakpoint continuous transmission.
Background
With the function complication of the satellite-borne integrated electronic system, the satellite-borne system software mode developed by the traditional 'bare engine' becomes very popular, the development of the satellite-borne software by using a real-time embedded operating system is the trend of the satellite-borne integrated electronic system at present and in the future, and after the satellite-borne embedded operating system is used, numerous functional modules and complex program logic are brought, so that all functional modules cannot be completely covered when the satellite-borne system software is tested and verified on the ground, functional defects still exist after the satellite-borne system software is in orbit, the logic flow does not accord with the design intention and needs to be corrected, even the functions of some modules are not completely realized, and after the in-orbit data is complete, corresponding supplement and improvement are carried out, namely the satellite-borne system software needs to be expanded in-orbit.
After the satellite operates in orbit, when the satellite can not be verified by a ground experiment, the program in the storage device or the file system is directly replaced through the serial port or the network port, and the program is reloaded and executed. For an on-orbit satellite system, the ground can only change the behavior of the on-orbit satellite system through remote control uplink injection data, and an on-orbit programming method is characterized in that the on-orbit thermal updating and function upgrading maintenance of the software function of the satellite-borne system are realized through taking the remote control uplink injection data as the excitation of the on-orbit satellite system, so that the on-orbit service life and the reliability of the satellite are greatly improved.
The in-orbit programming technology is widely applied to the existing aerospace engineering, and in the prior art, the in-orbit programming implementation method comprises the following steps: 1. the method comprises the steps of performing lookup type replacement aiming at a set replacement function, namely specifying functions needing on-track programming before the last day of satellite-borne software, filling the functions into an on-track programming table, searching the table to determine whether on-track updating content exists or not when a program needs to access the corresponding functions, if so, using the on-track updating content, and otherwise, calling and executing the original content; 2. and modifying instruction jump on any address needing to be updated, and realizing modification of any statement. However, for the method 1, because the content of the on-track programming must be specified in advance, the flexibility of software implementation is reduced, the significance of the on-track programming is greatly reduced, and when the software defect occurs in an unspecified function sequence, the on-track programming cannot function; although the method 2 is flexible to implement and can modify and jump for any statement, the method is only available in a real address mode, and for application software running on an operating system in a virtual address, the operation of the method can cause failure of on-track hot update, so that the expected purpose cannot be achieved.
Disclosure of Invention
Aiming at the problem that the application software running on the real-time embedded operating system in the virtual address space can not jump randomly, the embodiment of the invention provides a dynamic on-track hot updating method supporting breakpoint continuous transmission by utilizing the dynamic loading characteristic provided by the embedded operating system so as to solve the problems that the existing on-track replacement of a set function module can only be carried out on the track, the application program running in the virtual address space can not realize random address jumping, the on-track programming data injected after the system is powered off can not be recovered and the like, thereby further improving the flexibility of software design of the satellite-borne system and the on-track upgradability and maintainability.
The embodiment of the invention provides a dynamic on-orbit thermal updating method supporting breakpoint continuous transmission, which comprises the following steps: the first step is as follows: the satellite-borne software receives all on-orbit hot updating patch packet data from the ground in a remote control uplink injection mode and sends the on-orbit hot updating patch packet data to an on-orbit hot updating module; the second step is as follows: after all the on-track hot update patch package data are received, performing MD5 verification on the on-track hot update patch package, and if the verification is correct, entering a third step; the third step: firstly, storing in-orbit hot update patch packet data injected in a remote control uplink manner in a memory, then generating a file in a main partition of a NorFlash file system, and writing the patch packet data in the memory into the file; the fourth step: generating MD5 check value files corresponding to a plurality of patch package files under the directory where the on-track hot updating patch package data files are located; the fifth step: respectively modifying the names of the newly generated on-track hot update patch package data file and the corresponding MD5 check value file into the names of the file needing to be hot updated and the corresponding MD5 check value file; a seventh step of: and according to the information in the on-track hot update patch package, sending a signal to the process to which the patch package belongs, informing the process to perform corresponding processing, and performing process reset or remapping operation on functions in the on-track hot update patch package.
Preferably, in the second step, if the verification is incorrect, the ground determines the lost patch packet data through remote measurement, and remotely injects the lost packet data upstream.
Preferably, after the fifth step, a sixth step is further included: according to the method from the third step to the fifth step, the file to be updated and the corresponding MD5 check value file, the on-track hot update patch package data file and the corresponding MD5 check value file are backed up to the same file system as the partition, and the file name is consistent with the name of the corresponding file in the main partition.
Preferably, after the seventh step, an eighth step is further included: and the ground judges whether the on-orbit thermal updating is successful according to the downlink remote measurement and the memory unloading function, and if the on-orbit thermal updating is unsuccessful, the ground can organize the remote control command with a corresponding format and return to the previous version or the initial safe version.
Preferably, the patch package data format is different from other remote control packages, including: the first MD5 check value, the hot update process ID, the hot update file number and the hot update data, wherein the first MD5 check value is obtained by ground calculation aiming at a newly generated file and is used for checking when complete patch package data is received on a satellite.
Preferably, the integrity check in the second step has two layers of checks, including: firstly, each packet of remote control data contains verification, which can be used for ensuring the integrity of the packet of remote control data; and secondly, performing MD5 value calculation on the received patch packet data stored in the memory to obtain a second MD5 check value, and comparing the second MD5 check value with a first MD5 check value generated on the ground to ensure the integrity of all patch packet data injected in the remote control uplink.
Preferably, the NorFlash is divided into two regions: a primary partition and a redundant partition.
Preferably, the fifth step further comprises: characters are added after the names of the file which needs to be updated at this time and the corresponding MD5 check value file respectively so as to keep the original file, and the original file can be used as the basis for version rollback after the hot update fails.
Preferably, the remote control packet format organized when reverting to the previous version or the initial secure version includes: a process ID of the rollback, a file number of the rollback.
Preferably, when the in-orbit hot update patch packet requiring remote control uplink injection is large, if the in-orbit hot update patch packet cannot be completed in the period of one-orbit or two-orbit satellite injection, the in-orbit hot update patch packet can be divided into multiple in-orbit hot update patch packets until all the patch packet data requiring in-orbit hot update are injected.
The embodiment of the invention can provide the on-orbit hot updating method for the operating system satellite-borne application software of the operating ground virtual address space, has positive reference significance for improving the on-orbit operation reliability and maintainability of the satellite-borne system software, and has better practical engineering application value in the aerospace field.
Drawings
FIG. 1 is a flowchart illustrating a dynamic on-track hot-update method supporting breakpoint resumption according to an embodiment of the present invention;
FIG. 2 is a functional structure diagram of a dynamic on-track hot-update method supporting breakpoint resumption according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a dynamic on-track hot update process supporting breakpoint resumption according to an embodiment of the present invention.
Detailed Description
The following provides a detailed technical solution of the embodiment of the present invention with reference to the accompanying drawings.
Referring to fig. 1-3, the method for dynamically programming an intelligent on-track thermal update according to the present invention includes the following steps:
first step S1: the satellite-borne software receives all on-orbit hot updating patch packet data from the ground in a remote control uplink injection mode and sends the patch packet data to an on-orbit hot updating module; before the on-orbit hot updating patch packet data is injected into the satellite-borne software in a remote control uplink mode, firstly, the ground semi-physical simulation platform verifies and completes the whole process of the on-orbit hot updating, and then the data is organized according to the on-orbit hot updating patch packet data format by the ground to carry out remote control uplink injection;
the on-orbit hot patch package from the ground is different from other remote control packages, is specially used for on-orbit hot updating and comprises a first MD5 check value, a hot updating process ID, a hot updating file number and hot updating data, wherein the first MD5 check value in the patch package is obtained by calculation of the ground aiming at a newly generated file and is used for checking when complete patch package data is received on the satellite.
Second step S2: after all the on-track hot update patch package data are received, performing MD5 verification on the on-track hot update patch package, and if the verification is correct, entering a third step S3; if the verification is incorrect, the patch packet data on the on-orbit hot updating is incomplete, the ground judges the lost patch packet data through remote measurement, and the lost data packet is injected in a remote control uplink mode;
here, MD5 checks have two layers of checks, including: firstly, each packet of remote control data contains verification, which can be used for ensuring the integrity of the packet of remote control data; and secondly, performing MD5 value calculation on the received patch packet data stored in the memory to obtain a second MD5 check value, and comparing the second MD5 check value with a first MD5 check value generated on the ground to ensure the integrity of all patch packet data injected in the remote control uplink.
Third step S3: firstly, storing in-orbit hot update patch packet data injected in a remote control uplink manner in a memory, then generating a file in a main partition of a NorFlash file system, and writing the patch packet data in the memory into the file; in this embodiment, the name of the file may be a name of a file that needs to be updated by hot, and then a character "0" or other characters may be added;
fourth step S4: generating MD5 check value files corresponding to a plurality of patch package files under the directory where the patch package files are located;
in the embodiment, after the patch file is generated, the 3 parts of the MD5 check value files corresponding to the patch file are generated, and when the patch file is operated, the consistency of the patch file can be checked by using the 3 parts of the check value files, so that the data in NorFlash is prevented from being modified due to single event upset, and the consistency of the file is further influenced.
Fifth step S5: respectively modifying the names of the newly generated patch package file and the corresponding MD5 check value file into the names of the file needing to be updated by heat and the corresponding MD5 check value file; meanwhile, characters are added after the names of the file which needs to be updated at the time and the corresponding MD5 check value file respectively so as to keep the original file, and the original file can be used as the basis for version rollback after the hot update fails;
sixth step S6: according to the method from the third step to the fifth step, files needing to be updated and the corresponding MD5 check value files, on-track hot update patch package data files and the corresponding MD5 check value files are backed up to the same file system as the partition, and the file names are consistent with the names of the corresponding files in the main partition;
here, the NorFlash is divided into two regions: the system comprises a main partition and a redundant partition, wherein the two partitions are two different physical areas, and all application program files, dynamic library files and important configuration files are stored in each partition to keep the reliability and the robustness of the system.
Seventh step S7: according to the information in the on-orbit hot updating patch package, sending a signal to the process to which the patch package belongs, informing the process to perform corresponding processing, and performing process resetting or remapping operation on functions in the patch package;
eighth step S8: and the ground judges whether the on-orbit thermal updating is successful according to the downlink remote measurement and the memory unloading function, and if the on-orbit thermal updating is unsuccessful, the ground can organize the remote control command with a corresponding format and return to the previous version or the initial safe version.
In this embodiment, the format of the remote control packet organized when the previous version or the initial security version is returned to includes: a process ID of the rollback, a file number of the rollback. And the on-track hot updating module updates the file names and the MD5 check value file names of the files corresponding to the process numbers in the main partition and the redundant partition according to the two pieces of information, deletes the currently used file and the corresponding MD5 check value file, sends a signal to the corresponding process, actively informs the process of finishing the rollback of the version, makes a specific action by the process, and performs process reset or remapping operation on functions in the patch package.
The method has the function of breakpoint continuous transmission, when the in-orbit hot update patch packet needing to be injected is large, the in-orbit hot update patch packet cannot be injected in the period of one orbit or two orbits of a satellite, the multi-orbit hot update can be divided into multiple orbits until all patch packet data needing to be subjected to in-orbit hot update are injected, and in the injecting process, if a plurality of packet data are lost due to a channel or a transmission reason, all data packets do not need to be injected again, the number of the lost packets is judged only according to downlink telemetering, and according to the information, only the lost packet needs to be injected, and one-time in-orbit hot update operation can be completed.
The design principle and the design idea of the embodiment of the invention mainly comprise the following three parts:
(1) by using the dynamic loading characteristic and the file system provided by the operating system, the modules which have the on-orbit hot update requirement, relatively independent functions and capability of decoupling are independently made into dynamic link library files or an independent application program, and then are linked into the main program or the main program is used for starting the independent application process. If the dynamic library file form is adopted, when the function in the dynamic library file is required to be called and executed, the function in the dynamic library file is respectively mapped to the process space (by using a standard interface provided by posix), and when the specific function is required to be called, the mapped pointer is called, so that the function in the dynamic library file is called and executed; if the data is compiled into a single application program, corresponding data interaction is completed by an interprocess communication means;
(2) when the on-track module needs to be updated hot, the newly generated dynamic library link library file needs to be suffixed with ". so" or an application program file generated independently, a standard remote control package is generated by using tool software without suffixes, the remote control package comprises a module index to be replaced, a process index to which the module belongs, and an MD5 code of the on-track hot update file at this time, the integrity of data verification and the reliability of on-track hot update are ensured by the information, and the packet data format content of the on-track hot update is noted as shown in table 1:
Figure BDA0002175937690000071
means of …… Remote control packet sequence number …… File data
Number of bytes …… 2 (tundish) …… 247
Figure BDA0002175937690000072
TABLE 1
At a certain determined moment, a dynamic library file used in an application program or a started application program is determined, but the on-orbit hot update can be performed in an on-orbit hot updated dynamic library file or application program according to the function and task requirements, aiming at the dynamic library file or application program with function defects or function expansion upgrading, so that the robustness and reliability of the on-board software system are ensured. The MD5 check code in the remote control package of the upper note can ensure the integrity of the upper note file, when the check fails, the function repair and the function expansion of the current time can be abandoned, and the old version is still used, so that the satellite-borne software system can be prevented from system crash caused by wrong on-orbit hot update patch packages, and the satellite loses control. After the on-orbit hot update module is checked, a new module file is generated, and according to information provided in the on-orbit hot update module first package data file, a corresponding process is actively informed in a semaphore naming mode; after receiving the corresponding signal, the process maps the function in the new dynamic library file to the process space of the process according to the selected mode, or restarts the corresponding application program to start a new function;
(3) the module that completes the on-track hot update may be rolled back to the previous version or the initial safe version according to the remote command. When on-orbit hot update is carried out on a certain module, a newly injected on-orbit hot update patch package is regenerated into a file, and a mode of modifying the file name is utilized, so that not only is the newly injected patch package replaced by the currently used file name, but also the mode of modifying the original file into the existing file name and adding suffix is realized, the original version is reserved, the condition that the on-orbit hot update fails at this time due to abnormity can be ensured, a certain correct version can be returned, and controllability is realized. In addition, after the replacement is successful, if the system is started again after power failure, the patch package which is updated on the track newly is still used, but the previous version is not used continuously.
In summary, on one hand, the embodiment of the present invention can perform dynamic on-track hot update on a functional module or an application program of a satellite-borne embedded system that enables an MMU component and uses an operating system as a running platform, and has strong flexibility and self-maintainability; on the other hand, the version is supported to be returned to the version before the current on-track hot update, and the method has stronger expandability; moreover, function expansion or defect repair can be easily realized based on a dynamic library or an application program, and the method is not limited by the size of space, so that the maintainability of the satellite-borne software is greatly improved. Compared with the traditional on-orbit programming implementation mode of the satellite-borne software, the on-orbit programming method has the advantages of being easy to implement, reliable, flexible and the like, and has a strong engineering practice value.
The above description is only exemplary of the present invention, but the scope of the present invention is not limited thereto, and any modification, replacement, or improvement made by those skilled in the art within the spirit and principle of the present invention should be included in the protection scope of the claims described in the present invention.

Claims (6)

1. A dynamic on-orbit hot updating method supporting breakpoint continuous transmission is characterized by comprising the following steps:
the first step is as follows: the satellite-borne software receives all on-orbit hot updating patch packet data from the ground in a remote control uplink injection mode and sends the on-orbit hot updating patch packet data to an on-orbit hot updating module;
wherein, the patch package data format is different from other remote control packages, and comprises: the method comprises the steps that a first MD5 check value, a hot updating process ID, a hot updating file number and hot updating data are obtained, wherein the first MD5 check value is obtained by ground calculation aiming at a newly generated file and is used for checking when complete patch package data are received on a satellite;
the second step is as follows: after all on-orbit hot updating patch packet data are received, performing MD5 verification on the on-orbit hot updating patch packet, if the verification is incorrect, judging lost patch packet data through remote measurement on the ground, and remotely controlling uplink injection of lost data; if the verification is correct, entering a third step; wherein, the integrality check has two layers of checks, include: firstly, each packet of remote control data contains verification, which can be used for ensuring the integrity of the packet of remote control data; performing MD5 value calculation on the received patch packet data stored in the memory to obtain a second MD5 check value, and comparing the second MD5 check value with a first MD5 check value generated on the ground to ensure the integrity of all patch packet data injected in the remote control uplink;
the third step: firstly, storing in-orbit hot update patch packet data injected in a remote control uplink manner in a memory, then generating a file in a main partition of a NorFlash file system, and writing the patch packet data in the memory into the file;
the fourth step: generating MD5 check value files corresponding to a plurality of patch package files under the directory where the on-track hot update patch package data files are located, and checking the consistency of the patch files through a plurality of MD5 check files to prevent data in NorFlash from being modified due to single event upset;
the fifth step: respectively modifying the names of the newly generated on-track hot update patch package data file and the corresponding MD5 check value file into the names of the file needing to be hot updated and the corresponding MD5 check value file;
a sixth step: according to the method from the third step to the fifth step, files needing to be updated and corresponding MD5 check value files, on-track hot update patch package data files and corresponding MD5 check value files are backed up to a redundant partition of the file system, and the file names are consistent with the names of the corresponding files in the main partition;
a seventh step of: and according to the information in the on-track hot update patch package, sending a signal to the process to which the patch package belongs, informing the process to perform corresponding processing, and performing process reset or remapping operation on functions in the on-track hot update patch package.
2. The dynamic on-track hot-update method supporting breakpoint resume according to claim 1, further comprising, after the seventh step, an eighth step of: and the ground judges whether the on-orbit thermal updating is successful according to the downlink remote measurement and the memory unloading function, and if the on-orbit thermal updating is unsuccessful, the ground can organize the remote control command with a corresponding format and return to the previous version or the initial safe version.
3. The dynamic on-track hot-update method supporting breakpoint resume according to claim 1, wherein the NorFlash is divided into two regions: a primary partition and a redundant partition.
4. The dynamic on-track hot-update method supporting breakpoint resume according to claim 1, wherein in the fifth step, the method further comprises: characters are added after the names of the file which needs to be updated at this time and the corresponding MD5 check value file respectively so as to keep the original file, and the original file can be used as the basis for version rollback after the hot update fails.
5. The dynamic on-track hot-update method supporting breakpoint resume according to claim 2, wherein the remote control packet format organized when rolling back to the previous version or the initial secure version comprises: a process ID of the rollback, a file number of the rollback.
6. The method as claimed in claim 1, wherein when the in-orbit hot update patch packet to be remotely injected in uplink is large, if the in-orbit hot update patch packet cannot be injected in one or two orbit of the satellite, the method can be divided into multiple in-orbit hot update packets until all the patch packet data to be updated in-orbit hot are injected.
CN201910778871.9A 2019-08-22 2019-08-22 Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission Active CN110474673B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910778871.9A CN110474673B (en) 2019-08-22 2019-08-22 Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910778871.9A CN110474673B (en) 2019-08-22 2019-08-22 Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission

Publications (2)

Publication Number Publication Date
CN110474673A CN110474673A (en) 2019-11-19
CN110474673B true CN110474673B (en) 2022-02-25

Family

ID=68513634

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910778871.9A Active CN110474673B (en) 2019-08-22 2019-08-22 Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission

Country Status (1)

Country Link
CN (1) CN110474673B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111796850B (en) * 2020-07-20 2021-05-11 上海航天电子通讯设备研究所 Satellite load software on-orbit maintenance equipment and method

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101976322A (en) * 2010-11-11 2011-02-16 清华大学 Safety metadata management method based on integrality checking
CN102609326A (en) * 2012-01-17 2012-07-25 大唐移动通信设备有限公司 Data downloading processing method and data downloading processing device
CN103777983A (en) * 2014-01-24 2014-05-07 航天东方红卫星有限公司 Satellite-borne software in-orbit maintaining and upgrading method
US8726267B2 (en) * 2006-03-24 2014-05-13 Red Hat, Inc. Sharing software certification and process metadata
CN103942066A (en) * 2014-03-25 2014-07-23 中国科学院长春光学精密机械与物理研究所 Satellite-borne embedded software module on-orbit updating method
CN106155651A (en) * 2015-03-31 2016-11-23 广州四三九九信息科技有限公司 The method and system that the automation of application version is issued and updated
CN107391189A (en) * 2017-07-17 2017-11-24 上海卫星工程研究所 The On-board programming method of On-board software
CN109710296A (en) * 2018-12-14 2019-05-03 上海航天控制技术研究所 A kind of sky and space plane inertial navigation embedded software on-line updating method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090133097A1 (en) * 2007-11-15 2009-05-21 Ned Smith Device, system, and method for provisioning trusted platform module policies to a virtual machine monitor
WO2017185253A1 (en) * 2016-04-27 2017-11-02 华为技术有限公司 Patch upgrade-based file processing method and device, terminal, and storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8726267B2 (en) * 2006-03-24 2014-05-13 Red Hat, Inc. Sharing software certification and process metadata
CN101976322A (en) * 2010-11-11 2011-02-16 清华大学 Safety metadata management method based on integrality checking
CN102609326A (en) * 2012-01-17 2012-07-25 大唐移动通信设备有限公司 Data downloading processing method and data downloading processing device
CN103777983A (en) * 2014-01-24 2014-05-07 航天东方红卫星有限公司 Satellite-borne software in-orbit maintaining and upgrading method
CN103942066A (en) * 2014-03-25 2014-07-23 中国科学院长春光学精密机械与物理研究所 Satellite-borne embedded software module on-orbit updating method
CN106155651A (en) * 2015-03-31 2016-11-23 广州四三九九信息科技有限公司 The method and system that the automation of application version is issued and updated
CN107391189A (en) * 2017-07-17 2017-11-24 上海卫星工程研究所 The On-board programming method of On-board software
CN109710296A (en) * 2018-12-14 2019-05-03 上海航天控制技术研究所 A kind of sky and space plane inertial navigation embedded software on-line updating method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于增量链接的可回滚星载软件在轨更新方法;汪宏浩 等;《浙江大学学报(工学版)》;20150430;第49卷(第4期);第724-731页 *

Also Published As

Publication number Publication date
CN110474673A (en) 2019-11-19

Similar Documents

Publication Publication Date Title
CN106569847B (en) Method for vehicle-mounted system to realize IAP remote upgrade based on mobile network
CN107391189B (en) On-orbit programming method of satellite-borne software
CN108089876B (en) On-orbit updating method for satellite-borne DSP software
CN105930236A (en) Application program version returning method based on BMS Bootloaderupgrade
CN104820586B (en) A kind of in-orbit maintaining method of spacecraft embedded software
CN109062598B (en) Safe OTA (over the air) upgrading method and system
CN107957874B (en) Recoverable resident type on-orbit programming method for satellite-borne software
CN102799502A (en) On-orbit maintenance method of satellite-borne embedded software
CN101826027A (en) Embedded system and updating method thereof
CN103942066A (en) Satellite-borne embedded software module on-orbit updating method
CN108874582A (en) A kind of system recovery method, device and terminal
CN107220097B (en) On-orbit programming and overloading method for large-scale complex structure software
WO2014183557A1 (en) Star sensor in-orbit maintenance method
CN105786510A (en) Upgrading and partitioning system and security upgrading method for single-chip microcomputer
CN111176890A (en) Data storage and exception recovery method for satellite-borne software
CN110474673B (en) Dynamic on-orbit thermal updating method supporting breakpoint continuous transmission
CN103019111A (en) Electronic control unit for vehicle and method of executing program
CN103257869A (en) Method for intelligently downloading ECU (electronic control unit) programs
CN101802793A (en) Method for processing the volume of information handled during the debugging phase of operational software onboard an aircraft and device for implementing the same
CN108920168B (en) Bootloader method supporting simultaneous upgrading of multiple similar ECUs and having function of preventing program mismatching
CN109766207A (en) Restoration methods, device, monitoring device and the storage medium of firmware remote upgrade
CN103067499A (en) Data processing method and processing device
CN111338661A (en) Method for reversely upgrading BOOT of application program and storage medium
CN100359485C (en) Testing device and method for flush-bonding system
CN108958737A (en) A kind of On-board software On-board programming method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant