CN113238772B - Program updating method, domain controller, and storage medium - Google Patents

Program updating method, domain controller, and storage medium Download PDF

Info

Publication number
CN113238772B
CN113238772B CN202110472028.5A CN202110472028A CN113238772B CN 113238772 B CN113238772 B CN 113238772B CN 202110472028 A CN202110472028 A CN 202110472028A CN 113238772 B CN113238772 B CN 113238772B
Authority
CN
China
Prior art keywords
partition
program
package
inactive
partitions
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
CN202110472028.5A
Other languages
Chinese (zh)
Other versions
CN113238772A (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.)
United Automotive Electronic Systems Co Ltd
Original Assignee
United Automotive Electronic Systems Co Ltd
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 United Automotive Electronic Systems Co Ltd filed Critical United Automotive Electronic Systems Co Ltd
Priority to CN202110472028.5A priority Critical patent/CN113238772B/en
Publication of CN113238772A publication Critical patent/CN113238772A/en
Application granted granted Critical
Publication of CN113238772B publication Critical patent/CN113238772B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638Organizing or formatting or addressing of data
    • G06F3/0644Management of space entities, e.g. partitions, extents, pools
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • G06F8/654Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories

Abstract

The invention relates to a program updating method, a domain controller and a storage medium. The program updating method comprises the steps of establishing a plurality of program package partitions according to the types of program packages; each package partition comprises a first partition and a second partition; determining one of a first partition and a second partition in each package partition as an active partition; determining that the other of the first partition and the second partition in each package partition is an inactive partition; running all programs in the activated partition; acquiring an upgrade program and storing the upgrade program in an inactive partition in a program package partition with the same type as the upgrade program; and updating the inactive partition stored with the upgrade program into the active partition so as to improve the program upgrade speed, avoid damaging the storage life and ensure that the system is more reliable.

Description

Program updating method, domain controller, and storage medium
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a program update method, a domain controller, and a storage medium.
Background
Program updating generally needs to use two program storage partitions, wherein one program storage partition is a current active partition and is used for storing a current program; the other program storage partition is an inactive area for storing updated programs. FIG. 1 is a diagram illustrating a partition switch of a program memory during a conventional program update process. As shown in fig. 1, the program memory 1 is divided into two to form an a partition 11 and a B partition 12, wherein the a partition 11 is an inactive partition and the B partition 12 is an active partition. When the system is started, the program is run from the B partition 12, and the new program can be updated to the A partition 11 while the program is normally run, and the program in the B partition 12 running currently is not interrupted, so that the availability and reliability of Over-the-Air (OTA) upgrading are improved. After the program in the a partition 11 is updated, the activation flag is switched to restart the system, and the B partition 12 waits for the updated program from the a partition 11. As only half of the program memory is used and the other half is not used at ordinary times, the space of the program memory is wasted.
The domain controller is complex in function and includes micro control unit (Micro Controller Unit, MCU) packages, microprocessor unit (Micro Controller Unit, MPU) basic packages, MPU core packages, and MPU client application packages, among others, all of which require OTA updates. The following describes an example of update of the Kernel package and the App package. FIG. 2 is a schematic diagram of a prior art kernel and app package update. As shown in fig. 2, the program memory 2 is divided into two into a partition 21 and a partition 22. Partition 21 is subdivided into kernel partition 211 and app partition 212; partition 22 is also subdivided into kernel partition 221 and app partition 222. When program memory 2 is in the start state, neither kernel partition 211 nor app partition 212 in partition 21 stores programs, but kernel partition 221 in partition 22 stores program K1 and app partition 222 stores program A1. When the system is started, the partition 22 is switched to an activated partition and the partition 21 is switched to an inactivated partition, and at the moment, a program K1 in a kernel partition in the partition 22 and a program A1 in an app partition 222 are operated; after the system receives the instruction of the program to update both the kernel program and the app program, the updated program K2 is stored in the kernel partition 211 in the partition 21, and the updated program A2 is stored in the app partition 212 in the partition 21. During the program update, the programs K1 and A1 in the partition 22 continue to be run, and even if an abnormality, such as a power failure, occurs during the program update, the running of the programs K1 and A1 in the partition 22 is not affected. After the program is updated, the activation flag is switched, the partition 22 is switched to the inactive partition, the partition 21 is switched to the active partition, and after the system is restarted, the program K2 in the kernel partition in the partition 21 and the program A2 in the app partition start to run. When the system receives an instruction to update the app program, the updated program A3 is stored in the app partition 222 in the partition 22. Since program K1 is stored in kernel partition 221 in current partition 22 and program K2 is stored in kernel partition 211, which is the latest in the system itself, program K2 in kernel partition 211 in partition 21 needs to be copied into kernel partition 221 in partition 22, thereby realizing program update in kernel partition 221 in partition 22. After the system is restarted, partition 21 is switched to the inactive partition and partition 22 is switched to the active partition, at which point the system runs program K2 in kernel partition 221 and program A3 in app partition 222 in partition 22. This update requires an additional "synchronization" step, which increases the OTA time consumption and reduces the lifetime of the memory.
Disclosure of Invention
The invention provides a program updating method, which comprises the following steps:
establishing a plurality of program package partitions according to the types of the program packages; each package partition includes a first partition and a second partition;
determining one of a first partition and a second partition in each package partition as an active partition;
determining that the other of the first partition and the second partition in each package partition is an inactive partition;
running the program in the activated partition;
acquiring an upgrade program and storing the upgrade program in an inactive partition in a program package partition with the same type as the upgrade program;
and updating the inactive partition storing the upgrade program into the active partition.
Further, updating the inactive partition storing the upgrade program to the active partition includes:
restarting the system, and running all programs in the activated partition.
Further, each package partition includes a partition switch identification.
Further, one of the first partition and the second partition in the corresponding package partition is switched to the active partition by the partition switching identification, and the other one of the first partition and the second partition in the corresponding package partition is switched to the inactive partition.
Further, the switching between active and inactive partitions in each package partition is independent of each other.
The application also provides a domain controller, which comprises a storage module and a control module;
the storage module comprises a plurality of program package partitions, and each program package partition comprises a first partition and a second partition;
the control module is used for switching one of the first partition and the second partition in each program package partition to be an activated partition, the other one of the first partition and the second partition in each program package partition to be an inactivated partition, running programs in all the activated partitions, storing the upgrading program in the inactivated partition in the corresponding program package partition, and updating the inactivated partition stored with the upgrading program to be the activated partition.
Further, each package partition includes a partition switch identification.
Further, the control module is configured to switch one of the first partition and the second partition in the corresponding package partition to an active partition according to the partition switch identifier, and switch the other one of the first partition and the second partition in the corresponding package partition to an inactive partition.
Further, the memory module includes a random access memory, or a read only memory.
The present application also provides a storage medium storing a plurality of programs executable by one or more control modules to implement the foregoing program update method.
Drawings
FIG. 1 is a diagram illustrating a partition switch of a program memory during a conventional program update process.
FIG. 2 is a schematic diagram of a prior art kernel and app package update.
FIG. 3 is a flowchart of a program update according to an embodiment of the invention.
FIG. 4 is a schematic diagram of a program update according to an embodiment of the invention.
Fig. 5 is a schematic diagram of a domain controller according to an embodiment of the invention.
Detailed Description
The following description of the embodiments of the present invention will be made more apparent and fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be understood that the present invention may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size of layers and regions, as well as the relative sizes, may be exaggerated for the same elements throughout. It will be understood that when an element or layer is referred to as being "on" …, "" adjacent to "…," "connected to" or "coupled to" another element or layer, it can be directly on, adjacent to, connected to or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on" …, "" directly adjacent to "…," "directly connected to" or "directly coupled to" another element or layer, there are no intervening elements or layers present. It will be understood that, although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the present invention.
Spatially relative terms such as "under …", "under …", "below", "under …", etc.
"over …," "above," etc., may be used herein for convenience of description to describe one element or feature as illustrated in the figures, in relation to another element or feature. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use and operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements or features described as "under" or "beneath" other elements would then be oriented "on" the other elements or features. Thus, the exemplary terms "under …" and "under …" may include both an upper and a lower orientation. The device may be otherwise oriented (rotated 90 degrees or other orientations) and the spatially relative descriptors used herein interpreted accordingly.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term "and/or" includes any and all combinations of the associated listed items.
In an embodiment of the present invention, a flowchart of a program update is provided, and in particular, please refer to a flowchart of a program update of an embodiment of the present invention shown in fig. 3 and a schematic diagram of a program update of an embodiment of the present invention shown in fig. 4. A flowchart of program update according to an embodiment of the present invention includes the steps of:
step S31: establishing a plurality of program package partitions according to the types of the program packages; each of the package partitions includes a first partition and a second partition.
More specifically, as shown in fig. 4, the storage module 4 is divided into a plurality of package partitions according to the types of packages, each package partition including a first partition and a second partition. In some embodiments, the types of packages may include, but are not limited to, a kernel package and an app package. For example, the storage module 4 is divided into a kernel package partition 41 and an app package partition 42 according to the kernel package and the app package. The kernel package partition 41 includes a first partition 411 and a second partition 412, where the first partition 411 stores a program K2 and the second partition 412 stores a program K1.app package partition 42 includes a first partition 421 and a second partition 422, where program A2 is stored within first partition 421 and program A1 is stored within second partition 422.
Step S32: determining that one of the first partition and the second partition in each of the package partitions is an active partition; determining that the other of the first partition and the second partition in each of the package partitions is an inactive partition.
As shown in fig. 4, the first partition 411 in the kernel package partition 41 and the first partition 421 in the app package partition 42 are determined to be active partitions. The second partition 412 in the kernel package partition 41 and the second partition 422 in the app package partition 42 are determined to be inactive partitions.
Step S33: and running all programs in the activated partition.
As shown in fig. 4, when the system is started, the program K2 in the first partition 411 in the kernel package partition 41 and the program A2 in the first partition 421 in the app package partition 42 are run, wherein the first partition 411 in the kernel package partition 41 and the first partition 421 in the app package partition 42 are active partitions.
Step S34: an upgrade program is acquired and stored in the inactive one of the package partitions of the same type as the upgrade program.
As shown in fig. 4, only the app package needs to be updated, the updated program A3 is obtained and the program A3 is stored into the second partition 422 in the app package partition 42, wherein the second partition 422 in the app package partition 42 is an inactive partition. During the program update process, the currently running program is not interrupted, and if an abnormality occurs during the update process, the running of the program K2 in the first partition 411 in the kernel package partition 41 and the running of the program A2 in the first partition 421 in the app package partition 42 are not affected. The embodiment of the invention can upgrade one or more types of program packages, avoids unnecessary synchronization, improves the upgrading speed, avoids the loss of the storage life and ensures that the system is more reliable.
Step 35: updating the inactive partition storing the upgrade program to the active partition.
More specifically, each package partition includes a partition switch identification, as shown in FIG. 4, kernel package partition 41 includes a partition switch identification, and app package partition 42 also includes a switch identification. The first partition 421 in the app package partition 42 is switched to the inactive partition, while the second partition 422 in the app package partition 42 is switched to the active partition by the switch identification.
In some embodiments, after restarting the system, all programs within the active partition are run.
As shown in FIG. 4, after restarting the system, program K2 in first partition 411 in kernel package partition 41 and program A3 in second partition 422 in app package partition 42 are run.
In some embodiments, one of the first partition and the second partition in the corresponding package partition is switched to the active partition and the other of the first partition and the second partition in the corresponding package partition is switched to the inactive partition by the partition switch identification. For example, as shown in fig. 4, the first partition 411 in the kernel package partition 41 and the second partition 422 in the app package partition 42 are switched to active partitions and the second partition 412 in the kernel package partition 41 and the first partition 421 in the app package partition 42 are switched to inactive partitions by partition switch identifications.
In some embodiments, the switching between the active partition and the inactive partition in each of the package partitions is independent of each other.
More specifically, as shown in fig. 4, the switch between the active partition and the inactive partition in the kernel package partition 41 is independent of the switch between the active partition and the inactive partition in the app package partition 42, which is beneficial to the upgrade and rollback of the independent package, is more flexible, and meets the requirements of clients.
In the above embodiment, the active partition and the inactive partition in each of the package partitions are used to store the program
The switching between the two is independent, so that the system starting options are increased and the system is more flexible. For example, the system start-up option of the prior art as shown in fig. 2 is 2 (see table 1).
TABLE 1
System startup options Kernel package app package
1 Partition 21 Partition 21
2 Partition 22 Partition 22
In the embodiment, the system startup options shown in fig. 4 are 4 (see table 2), and compared with the prior art, the system startup options are added, so that the program update is more flexible.
TABLE 2
System startup options Kernel package app package
1 First partition 411 First partition 421
2 First partition 411 Second partition 422
3 Second partition 412 First partition 421
4 Second partition 412 Second partition 422
The present application further provides a domain controller, and in particular, please refer to a schematic diagram of a domain controller according to an embodiment of the present invention shown in fig. 5. The domain controller comprises a storage module 5 and a control module 6. The memory module 5 comprises a plurality of package partitions 51, 52. Package partition 51 includes first partition 511 and second partition 512, and package partition 52 includes first partition 521 and second partition 522.
The control module 6 is configured to switch one of the first partition and the second partition in each of the package partitions to an active partition and the other of the first partition and the second partition in each of the package partitions to an inactive partition, run programs in all of the active partitions, store upgrade programs in the inactive partitions in the corresponding package partitions, and update the inactive partition in which the upgrade programs are stored to the active partition. For example, the control module is configured to switch one of the first partition 511 and the second partition 512 in the package partition 51 to be an active partition, and the other to be an inactive partition; one of first partition 521 and second partition 522 in switch package partition 52 is an active partition, and the other is an inactive partition; running programs within active ones of package partition 51 and package partition 52; and acquiring the upgrade program, storing the upgrade program in an inactive partition in the corresponding program package partition, and updating the inactive partition into an active partition.
In one embodiment, the memory module 5 is a random access memory, or a read only memory
The present application also provides a storage medium storing a plurality of programs executable by one or more control modules to implement the program update method as described above.
The embodiment of the invention can upgrade one or more types of program packages, avoids unnecessary synchronization, improves the upgrading speed, avoids the loss of the storage life and ensures that the system is more reliable. The switch between the active partition and the inactive partition in the program package partitions is mutually independent, so that the upgrade and rollback of the independent program package are facilitated, the system is more flexible, and the system meets the requirements of clients.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.

Claims (7)

1.A program updating method, characterized by comprising the steps of:
establishing a plurality of program package partitions according to the types of the program packages; each package partition comprises a first partition and a second partition;
determining that one of the first partition and the second partition in each of the package partitions is an active partition;
determining that the other of the first partition and the second partition in each of the package partitions is an inactive partition;
each program package partition comprises a partition switching identifier;
the switching between the active partition and the inactive partition in each of the package partitions is independent of each other;
running all programs in the activated partition;
acquiring an upgrade program and storing the upgrade program in the inactive partition in the program package partition with the same type as the upgrade program;
updating the inactive partition storing the upgrade program to the active partition.
2. The program updating method according to claim 1, wherein updating the inactive partition storing the upgrade program to the active partition comprises:
restarting the system, and running all programs in the activated partition.
3. The program update method according to claim 1, wherein one of the first partition and the second partition in the corresponding package partition is switched to the active partition by the partition switch identification, and the other one of the first partition and the second partition in the corresponding package partition is switched to the inactive partition.
4. A domain controller, comprising: a storage module and a control module;
the storage module comprises a plurality of program package partitions, and each program package partition comprises a first partition and a second partition;
the program package partitions are established according to the types of the program packages;
the control module is used for switching one of the first partition and the second partition in each program package partition to be an activated partition and the other of the first partition and the second partition in each program package partition to be a non-activated partition, running programs in all the activated partitions, acquiring upgrading programs, storing the upgrading programs in the non-activated partitions in the corresponding program package partitions with the same type as the upgrading programs, and updating the non-activated partition stored with the upgrading programs to be the activated partition;
each program package partition comprises a partition switching identifier;
the switching between the active partition and the inactive partition in each of the package partitions is independent of each other.
5. The domain controller of claim 4, wherein the control module is to switch one of the first partition and the second partition of the corresponding package partition to the active partition and the other of the first partition and the second partition of the corresponding package partition to the inactive partition according to the partition switch identification.
6. The domain controller of claim 4, wherein the memory module comprises a random access memory, or a read only memory.
7. A storage medium storing a plurality of programs executable by one or more control modules to implement the program update method of any one of claims 1 to 3.
CN202110472028.5A 2021-04-29 2021-04-29 Program updating method, domain controller, and storage medium Active CN113238772B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110472028.5A CN113238772B (en) 2021-04-29 2021-04-29 Program updating method, domain controller, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110472028.5A CN113238772B (en) 2021-04-29 2021-04-29 Program updating method, domain controller, and storage medium

Publications (2)

Publication Number Publication Date
CN113238772A CN113238772A (en) 2021-08-10
CN113238772B true CN113238772B (en) 2024-02-23

Family

ID=77131434

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110472028.5A Active CN113238772B (en) 2021-04-29 2021-04-29 Program updating method, domain controller, and storage medium

Country Status (1)

Country Link
CN (1) CN113238772B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1737769A (en) * 2004-04-15 2006-02-22 美国博通公司 Fault tolerant data storage device
US8074213B1 (en) * 2006-08-11 2011-12-06 Symantec Operating Corporation Automatic software updates for computer systems in an enterprise environment
CN105005492A (en) * 2015-08-17 2015-10-28 上海斐讯数据通信技术有限公司 Embedded equipment and software upgrading method
WO2016101712A1 (en) * 2014-12-22 2016-06-30 小米科技有限责任公司 Firmware recovery method, device and terminal
CN105849697A (en) * 2013-10-24 2016-08-10 三星电子株式会社 Method and apparatus for upgrading operating system of electronic device
CN105912356A (en) * 2016-03-31 2016-08-31 武汉光迅科技股份有限公司 Optical module firmware program online upgrade method supporting version fallback
CN107273160A (en) * 2017-06-09 2017-10-20 青岛海信电器股份有限公司 A kind of method and device of edition upgrading
CN112416388A (en) * 2020-11-10 2021-02-26 联创汽车电子有限公司 Intelligent mobile terminal software upgrading method and upgrading control system thereof
CN112463191A (en) * 2020-11-26 2021-03-09 北京沃东天骏信息技术有限公司 File updating method and device, equipment and storage medium
CN112612524A (en) * 2020-12-22 2021-04-06 西人马(西安)测控科技有限公司 Method, device and equipment for starting Linux system and storage medium

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080276060A1 (en) * 2007-05-01 2008-11-06 Erik Bostrom Pre-Configured Partitions With Use-Rights Limitations
US9058239B2 (en) * 2013-06-20 2015-06-16 International Business Machines Corporation Hypervisor subpartition as concurrent upgrade
US11036494B2 (en) * 2019-03-22 2021-06-15 International Business Machines Corporation Embedded application upgrade

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1737769A (en) * 2004-04-15 2006-02-22 美国博通公司 Fault tolerant data storage device
US8074213B1 (en) * 2006-08-11 2011-12-06 Symantec Operating Corporation Automatic software updates for computer systems in an enterprise environment
CN105849697A (en) * 2013-10-24 2016-08-10 三星电子株式会社 Method and apparatus for upgrading operating system of electronic device
WO2016101712A1 (en) * 2014-12-22 2016-06-30 小米科技有限责任公司 Firmware recovery method, device and terminal
CN105005492A (en) * 2015-08-17 2015-10-28 上海斐讯数据通信技术有限公司 Embedded equipment and software upgrading method
CN105912356A (en) * 2016-03-31 2016-08-31 武汉光迅科技股份有限公司 Optical module firmware program online upgrade method supporting version fallback
CN107273160A (en) * 2017-06-09 2017-10-20 青岛海信电器股份有限公司 A kind of method and device of edition upgrading
CN112416388A (en) * 2020-11-10 2021-02-26 联创汽车电子有限公司 Intelligent mobile terminal software upgrading method and upgrading control system thereof
CN112463191A (en) * 2020-11-26 2021-03-09 北京沃东天骏信息技术有限公司 File updating method and device, equipment and storage medium
CN112612524A (en) * 2020-12-22 2021-04-06 西人马(西安)测控科技有限公司 Method, device and equipment for starting Linux system and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Oracle程序包按自然方式自动维护分区;刘恒学;;电脑编程技巧与维护(第05期);全文 *
基于Linux平台智能电视OTA升级可靠性优化;鲁亚凯;;电子质量(第12期);全文 *

Also Published As

Publication number Publication date
CN113238772A (en) 2021-08-10

Similar Documents

Publication Publication Date Title
US10114655B2 (en) Rapid start up method for electronic equipment
US11354114B2 (en) Updating system, electronic control unit, updating management device, and updating management method
CN109725920B (en) Service instance updating method and device and storage medium
US5905896A (en) Method of changing software version in a computer system comprising a plurality of stations, and a computer system for implementing the method
CN108170451B (en) Method and system for controlling BIOS version upgrading by server BMC
CN102841793A (en) Software upgrading method and terminal
CN102163152A (en) Software upgrading method and device thereof for embedded terminal device
WO2019062576A1 (en) Protection method against abnormal power disconnection during system upgrade and terminal device
CN113238772B (en) Program updating method, domain controller, and storage medium
JP2006252437A (en) Method and procedure for applying patch
CN111026417A (en) Embedded equipment upgrading method and embedded equipment
CN112860291B (en) Firmware upgrading method and device
CN105814545A (en) Electronic device
CN106161086A (en) Control method that master control borad is restarted and device
CN113867807A (en) Method, device, equipment and storage medium for shortening power-on time of server
CN108958757A (en) The upgrade method of complicated embedded device and complicated embedded device
CN110543376A (en) Android system equipment fault self-repairing method and android system equipment
CN106155670A (en) A kind of mobile terminal and brush machine method and apparatus thereof
CN115480806A (en) Upgrading method and device of over-the-air technology OTA
CN107247642B (en) Method and device for determining executable mapping file during system startup
CN104572181A (en) Method and device for starting backup bootstrap program
WO2021117445A1 (en) Information processing device, mobile body, and information processing method
US20090259773A1 (en) Network device and method for setting working modes of line cards
CN115373733B (en) Model version adjusting method and device of model service and electronic equipment
CN112241340A (en) Startup and loading regional data backup method for online upgrade

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