WO2016145679A1 - 一种终端升级方法及装置 - Google Patents

一种终端升级方法及装置 Download PDF

Info

Publication number
WO2016145679A1
WO2016145679A1 PCT/CN2015/075591 CN2015075591W WO2016145679A1 WO 2016145679 A1 WO2016145679 A1 WO 2016145679A1 CN 2015075591 W CN2015075591 W CN 2015075591W WO 2016145679 A1 WO2016145679 A1 WO 2016145679A1
Authority
WO
WIPO (PCT)
Prior art keywords
upgrade
image file
target
independent
systems
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.)
Ceased
Application number
PCT/CN2015/075591
Other languages
English (en)
French (fr)
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.)
Yulong Computer Telecommunication Scientific Shenzhen Co Ltd
Original Assignee
Yulong Computer Telecommunication Scientific Shenzhen 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 Yulong Computer Telecommunication Scientific Shenzhen Co Ltd filed Critical Yulong Computer Telecommunication Scientific Shenzhen Co Ltd
Publication of WO2016145679A1 publication Critical patent/WO2016145679A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present application relates to the field of automation technologies, and in particular, to a terminal upgrade method and apparatus.
  • a terminal refers to a computer device that can be used in communication.
  • a terminal can include multiple systems, such as a general system, a security system, and an online trusted system.
  • a multi-system terminal includes a common system OS1 (OS is an operating system, an operating system), an online trusted system OS2, and a security system.
  • OS1 is an operating system, an operating system
  • OS2 online trusted system
  • security system OS3, OS3>OS2>OS1 at the security level.
  • the prior art is to set the upgrade content of all systems in one upgrade package.
  • all systems are upgraded at the same time, but the terminal has only one system upgrade mode (hereinafter referred to as recovery mode), and the recovery mode is controlled by the general system OS1, so The normal system OS1 controls the online trusted system OS2 and the security system OS3.
  • the application provides a terminal upgrade method and device, and the upgrade packages of each system are separately upgraded, and the risk of upgrading the security system can be reduced.
  • the present invention provides the following technical means:
  • a terminal upgrade method includes:
  • the terminal in normal operation and the user triggers a system upgrade
  • the target upgrade package includes a boot image file, a system upgrade image file, and a system image file corresponding to the target system
  • the method before the entering the system upgrade mode of the target system, the method further includes: determining whether the preset condition is met, and the determining whether the preset condition is met includes:
  • the verifying that the user identity information is correct includes:
  • the method further includes:
  • the boot image file after the upgrade of the target system, the boot image file after the upgrade of the system to be upgraded, and the boot image files of all the un-upgraded systems are combined to form an overall boot image file of all systems;
  • the overall boot image file is stored in the general system.
  • a terminal upgrade method includes:
  • the system upgrade mode of the at least two systems When the terminal is in the shutdown state and the user triggers the system upgrade, in the system upgrade mode of the at least two systems, the system upgrade mode corresponding to the target system that needs to be upgraded is determined, and the target upgrade corresponding to the target system is determined.
  • a package wherein the target upgrade package includes the target The boot image file, the system upgrade image file, and the system image file corresponding to the standard system;
  • the target upgrade package separately upgrades the independent boot image file, the independent system upgrade image file, and the independent system image file of the target system; wherein, the target The system includes a self-upgrade package independent of other systems, and the self-upgrade package includes the independent boot image file, the independent system upgrade image file, and the independent system image file.
  • the target upgrade package separately upgrades the independent startup image file, the independent system upgrade image file, and the independent system image file of the target system.
  • the independent boot image file of the target system is independently performed according to the target upgrade package. Steps to upgrade the system upgrade image file and the stand-alone system image file;
  • Whether the determining meets the preset condition includes:
  • the verifying that the user identity information is correct includes:
  • the method further includes:
  • the boot image file after the upgrade of the target system, the boot image file after the upgrade of the system to be upgraded, and the boot image files of all the un-upgraded systems are combined to form an overall boot image file of all systems;
  • the overall boot image file is stored in the general system.
  • a terminal upgrading device includes:
  • a first determining unit configured to determine, in at least two systems, a target system that needs to be upgraded, and the target in a situation that the terminal is in a normal running state and the user triggers a system upgrade a target upgrade package corresponding to the system; wherein the target upgrade package includes a boot image file, a system upgrade image file, and a system image file corresponding to the target system;
  • a restarting unit configured to restart the terminal and enter a system upgrade mode of the target system
  • the first upgrade unit upgrades the independent boot image file, the independent system upgrade image file, and the independent system image file in the target system according to the target upgrade package in the system upgrade mode;
  • the target system includes a self-upgrade package independent of other systems, and the self-upgrade package includes the independent boot image file, the independent system upgrade image file, and the independent system image file.
  • the method further includes: a first determining unit configured to determine whether the preset condition is met;
  • the first determining unit is specifically configured to determine whether the target system is an ordinary system; if yes, determining that a preset condition is met; if not, receiving user identity information of the terminal, and verifying the user identity information Whether it is correct; when the user identity information is correct, the determination satisfies the preset condition; when the user identity information is incorrect, the determination does not satisfy the preset condition.
  • the method further includes:
  • the first combination unit is configured to: after the upgrade operation is performed on the system to be upgraded, the boot image file after the target system is upgraded, the boot image file after the upgrade of the system to be upgraded, and the boot image of all the unupgraded systems.
  • File combination forming an overall boot image file for all systems;
  • a first storage unit configured to store the entire boot image file in the common system.
  • a terminal upgrading device includes:
  • a second determining unit configured to determine, in a system upgrade mode of at least two systems, a system upgrade mode corresponding to a target system that needs to be upgraded, and a scenario, when the terminal is in a shutdown state and the user triggers a system upgrade.
  • a target upgrade package corresponding to the target system where the target upgrade package includes a boot image file, a system upgrade image file, and a system image file corresponding to the target system;
  • a second upgrade unit configured to: in the system upgrade mode corresponding to the target system, separate boot image files, independent system upgrade image files, and independent system image files of the target system according to the target upgrade package
  • the upgrade includes: the independent boot image file, the independent system upgrade image file, and the independent system image file included in the self-upgrade package.
  • the present application provides a method and device for upgrading a terminal.
  • This application splits the entire upgrade package of all the original systems, so that each system has its own independent upgrade package.
  • the upgrade package has its own independent startup image file and is independent.
  • the system upgrades the image file and the independent system image file, so that the systems are independent of each other, so each system can be upgraded separately without any system package upgrade when the system is upgraded. Therefore, the application can achieve the purpose of separately upgrading, independent, and non-interference of each system, solving the problem of upgrading the general system control security system, and improving the security of the security system.
  • FIG. 1 is a flowchart of a method for upgrading a terminal according to an embodiment of the present application
  • FIG. 2 is a flowchart of still another method for upgrading a terminal according to an embodiment of the present application
  • FIG. 3 is a flowchart of still another method for upgrading a terminal according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of still another method for upgrading a terminal according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of an apparatus for upgrading a terminal according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of still another apparatus for upgrading a terminal according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of still another apparatus for upgrading a terminal according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of still another apparatus for upgrading a terminal according to an embodiment of the present disclosure.
  • the inventor of the present application found in the research process that the upgrade of the operating system mainly upgrades the system image file system.img, the system upgrade image file recovery.img, and the boot image file boot.img in the operating system.
  • each system requires simultaneous startup at startup, so the boot.img responsible for all system startups is used as a whole for common systems.
  • the general system uses the entire boot.img to start all systems.
  • the system upgrade image file recovery.img depends on the boot image file boot.img, so The system upgrade image recovery.img is also used as a whole for common systems, so all system upgrades must be integrated when performing the upgrade, and all systems are upgraded simultaneously by the normal system.
  • the operation authority of the ordinary system is too low, and the upgrade of the general system control security system will reduce the risk of the security system.
  • the boot image file boot.img and the system upgrade image file recovery.img running in the normal system can be transferred to the security system for operation.
  • This method does not cause problems with the general system control security system, but this will increase the operating system of the security system, reduce the operating speed of the security system, increase the design difficulty of the security system, and this design method does not match the conventional terminal design, even It is also not designed to be suitable for use in existing terminals.
  • a terminal refers to a computer device that can be used in communication, and broadly includes a personal computer, a mobile phone, a notebook, a tablet computer, a POS machine, or even a device such as a car computer.
  • each system has its own independent upgrade package.
  • each system's own upgrade package contains a separate boot image file, a separate system upgrade image file and a separate system image file. Then, each system's own independent upgrade package is stored in each system for use in system upgrade.
  • the first step generate a boot image file for each system.
  • the root cause of the inability of individual systems to be upgraded separately is that the boot image files boot.img for all systems are combined. So split the whole boot image file boot.img.
  • boot image file boot.img some data is shared by all systems. This part of the data is copied into multiple copies when split. Each system has one copy and is stored in each system's boot image file. in.
  • boot.img Some of the data in the boot image file boot.img is used by a system alone. Cut this part of the data directly into the boot image file of the corresponding system until the whole boot.img split is completed.
  • each system After completing the split of the overall boot.img, each system has its own independent boot image file.
  • the terminal includes the general system OS1, the Internet trusted system OS2 and the security system OS3 as examples.
  • the boot image files of the three systems are named system_OS1.img, system_OS2.img, and system_OS3.img.
  • Step 2 Generate a system upgrade image file recovery.img for each system.
  • the terminal includes the general system OS1, the Internet trusted system OS2 and the security system OS3 as examples.
  • the boot image files of the three systems are named recovery_OS1.img, recovery_OS2.img and recovery_OS3.img.
  • Step 3 Generate a system image file for each system.
  • the system image file system.img of each system is originally separated from each other, so the system.img of each system remains independent.
  • the terminal includes the general system OS1, the Internet trusted system OS2, and the security system OS3.
  • the image files of the three systems are named system_OS1.img, system_OS2.img, and system_OS3.img.
  • Each system's own boot image file boot_OSX.img, system upgrade image file recovery_OSX.img and system image file system_OSX.img can form the system's own upgrade package.
  • each system has its own independent upgrade package, and each system upgrade package is independent of each other and does not interfere with each other.
  • each system upgrade package is independent of each other and does not interfere with each other.
  • Each system's own upgrade package contains the boot image file, system upgrade image file, and system image file required for the system upgrade. All system upgrade packages constitute an overall upgrade package, which is stored on the server side or inside the terminal.
  • the terminal upgrade method provided by the present application is described below.
  • the method is mainly applied to the controller of the terminal.
  • the present application provides two terminal upgrade modes, the first one is suitable for the terminal to be in a normal running state, and the second is applicable to the terminal being in a shutdown state.
  • this embodiment provides a method for upgrading a terminal, including:
  • Step S101 In a case where the terminal is in a normal running state and the user triggers the system upgrade, the target system that needs to be upgraded is determined in the at least two systems, and the target upgrade package corresponding to the target system; wherein the target The upgrade package includes a boot image file, a system upgrade image file, and a system image file corresponding to the target system.
  • the terminal includes at least two systems, including at least the general system OS1, the Internet trusted system OS2, and/or the security system OS3, and of course other systems, and details are not described herein.
  • the system is used as the target system.
  • the target system obtains the overall upgrade package on the server side or the terminal, and finds the own upgrade package corresponding to the target system in the overall upgrade package as the target upgrade package, or the target system directly obtains the corresponding target system on the server side or the terminal end.
  • Self-upgrade package as a target upgrade package.
  • each system when the terminal is in the normal running state, each system is in the normal working state, each system has a setting option (hereinafter referred to as "Setting"), and multiple system setting options constitute a setting group (hereinafter referred to as Settings) ).
  • Settings a setting option
  • the system is upgraded to determine that the currently operating system is the target system to be upgraded.
  • Step S102 Restart the terminal and enter a system upgrade mode of the target system.
  • Step S103 In the system upgrade mode, according to the target upgrade package, respectively, separate boot image files, independent system upgrade image files, and independent system mirror files in the target system.
  • the upgrade includes the independent boot image file, the independent system upgrade image file, and the independent system image file. .
  • the upgrade process of the target system is performed with the support of the system upgrade mode.
  • the specific upgrade process is: update the boot image file in the target upgrade package, update the boot image file in the target system upgrade package, upgrade the system upgrade image file in the target upgrade package, and update the system upgrade image file in the target system upgrade package.
  • the system image file in the target upgrade package is updated with the system image file in the target upgrade package.
  • the target system is successfully upgraded.
  • the other systems can be upgraded as described above.
  • the target upgrade is unsuccessful, the operation can continue. The target system is upgraded until the target system is upgraded successfully.
  • the application provides a method for upgrading a terminal.
  • This application splits the entire upgrade package of all the original systems, so that each system has its own independent upgrade package.
  • the upgrade package has its own independent startup image file and independent
  • the system upgrades the image file and the independent system image file, so that the systems are independent of each other, so each system can be upgraded separately without any system package upgrade when the system is upgraded. Therefore, the application can achieve the purpose of separately upgrading, independent, and non-interference of each system, solving the problem of upgrading the general system control security system, and improving the security of the security system.
  • step S102 of FIG. 1 before the entering the system upgrade mode of the target system, a step of determining whether the preset condition is satisfied is further included.
  • the process of determining whether the preset condition is met includes:
  • Step S201 determining whether the target system is a normal system; if yes, proceeding to step S202, otherwise proceeding to step S203.
  • the at least two systems include an online trusted system and/or a security system, and a general system. It can be understood that the authentication of the general system OS1 in this application is also achievable, but when the security level of the general system OS1 is low, the identity verification may not be performed. Therefore, when the target system is a normal system, user authentication is not performed. User authentication is performed when the target system is not a normal system.
  • the security of the common system is the lowest, and the security of the remaining systems is high.
  • the user identity needs to be verified before performing the upgrade.
  • Step S202 It is determined that the preset condition is satisfied.
  • Step S203 Receive user identity information of the terminal, and verify whether the user identity information is correct; if yes, go to step S202, otherwise go to step S204.
  • the controller sends the authentication information to the target user. After the user obtains the authentication information, the authentication information is input to the controller, and the controller inputs the authentication to the user. The information is verified.
  • the controller verifies that the user identity information is correct, including two ways:
  • the first type verifying whether the user identity information is correct in the verification module of the target system
  • the online trusted system OS2 and the security system OS3 have their own authentication modules. Therefore, after receiving the user identity information, the controller can directly verify it in the online trusted system OS2 or the security system OS3. If the verification is correct, the user identity information is correct. . If the controller verifies that the user identity information is correct, it is determined that the current user is a legitimate user and determines that the preset condition is met, and the subsequent upgrade may be performed.
  • the controller In addition to the general system OS1, the Internet trusted system OS2 and the security system OS3, the controller also has the highest level security system Secure OS.
  • the highest level security system Secure OS also has a verification module, and the controller can also use the verification module. verification.
  • This verification can be achieved regardless of whether the verification module of the target system or the verification module in the highest level security system is used. It can be understood that if the authentication module is set in the ordinary system OS1, the normal system OS1 can also be used to verify the user identity information.
  • Step S204 determining that the preset condition is not met
  • controller verifies that the user identity information is incorrect, it determines that the current user is an illegal user, determines that the preset condition is not met, and refuses to perform subsequent upgrade.
  • the method provided by the present application further includes the following steps:
  • Step S301 Perform an upgrade operation on other systems to be upgraded
  • Step S302 Combine the boot image file after the target system is upgraded, the boot image file after the upgrade of the system to be upgraded, and the boot image files of all the un-upgraded systems to form an overall boot image file of all systems;
  • Step S303 Store the entire boot image file in the common system.
  • the boot image files of each system are separate and independent.
  • each system needs to be started at the same time.
  • the startup image files responsible for the startup of each system need to be merged into the overall startup image file. Then, the entire boot image file is stored in the normal operating system, so that the normal operating system can start all the systems together according to the overall boot image file.
  • the above is the first terminal upgrade mode provided by the present application.
  • the following describes the second terminal upgrade mode:
  • the application provides a method for upgrading a terminal, including:
  • Step S401 When the terminal is in the shutdown state and the user triggers the system upgrade, in the system upgrade mode of the at least two systems, determining a system upgrade mode corresponding to the target system that needs to be upgraded, and corresponding to the target system
  • the target upgrade package includes a boot image file, a system upgrade image file, and a system image file corresponding to the target system.
  • the first mode is the upgrade mode when the terminal is in the normal running state.
  • the second mode describes the upgrade mode when the terminal is powered off.
  • the user needs to use the combination key to trigger the upgrade.
  • the combination of keys can be: press the power button and the volume up button at the same time to trigger the upgrade, or press the power button and the volume down button at the same time to trigger the upgrade.
  • the terminal is in the shutdown state, each system is not started, so you cannot directly enter the system to upgrade in the setting. Therefore, you need to select a target system upgrade mode that needs to be upgraded, that is, the target recovery mode. Since one recovery mode corresponds to one system, the system corresponding to the target recovery mode is taken as the target system, and the target upgrade package is obtained in the server segment or terminal.
  • Step S402 In the system upgrade mode corresponding to the target system, upgrade the independent boot image file, the independent system upgrade image file, and the independent system image file of the target system according to the target upgrade package;
  • the target system includes a self-upgrade package independent of other systems, and the self-upgrade package includes the independent boot image file, the independent system upgrade image file, and the independent system image file.
  • the controller upgrades the upgrade package of the target system according to the content of the target upgrade package.
  • the specific implementation mode is the same as that shown in Figure 1.
  • Step S402 in Figure 4 is specifically implemented:
  • the specific execution process of determining whether the preset condition is met is consistent with the content shown in FIG. 2, and the difference between the embodiment and the embodiment of FIG. 2 is only that: in this embodiment, when the user identity information is verified to be correct, there is only one way: Verify that the user identity information is correct in the verification module of the highest level security system. Because the target system has not been started in this embodiment, the target system cannot be used to verify whether the user identity information is correct.
  • the highest level security system starts at the same time as the target recovery mode, and the startup time is earlier than the target system, so the verification using the highest level security system is adopted. The module is verified.
  • the embodiment further includes: performing an upgrade operation on the other system to be upgraded; a boot image file after the target system is upgraded, a boot image file after the upgrade of the system to be upgraded, and all un-upgraded systems.
  • the boot image file combination forms an overall boot image file of all systems; the entire boot image file is stored in the common system.
  • the application provides a method for upgrading a terminal.
  • This application splits the entire upgrade package of all the original systems, so that each system has its own independent upgrade package.
  • the upgrade package has its own independent startup image file and independent
  • the system upgrades the image file and the independent system image file, so that the systems are independent of each other, so each system can be upgraded separately without any system package upgrade when the system is upgraded. Therefore, the application can achieve the purpose of separately upgrading, independent, and non-interference of each system, solving the problem of upgrading the general system control security system, and improving the security of the security system.
  • the application provides a terminal upgrading apparatus, including:
  • a first determining unit 51 configured to determine, in at least two systems, a target system that needs to be upgraded, and a target upgrade package corresponding to the target system, in a case that the terminal is in a normal running state and the user triggers a system upgrade;
  • the target upgrade package includes a boot image file, a system upgrade image file, and a system image file corresponding to the target system.
  • a restarting unit 52 configured to restart the terminal and enter a system upgrade mode of the target system
  • the first upgrading unit 53 upgrades the independent startup image file, the independent system upgrade image file, and the independent system image file in the target system according to the target upgrade package in the system upgrade mode;
  • the target system includes a self-upgrade package independent of other systems, and the self-upgrade package includes the independent boot image file, the independent system upgrade image file, and the independent system image file.
  • the present application provides a terminal upgrading apparatus, as shown in FIG. 6, further comprising: a first determining unit 54 for determining whether a preset condition is met;
  • the first determining unit is specifically configured to determine whether the target system is an ordinary system; if yes, determining that a preset condition is met; if not, receiving user identity information of the terminal, and verifying the user identity information Whether it is correct; when the user identity information is correct, the determination satisfies the preset condition; when the user identity information is incorrect, the determination does not satisfy the preset condition.
  • the first determining unit 54 verifies whether the user identity information is correct in the verification module of the target system when verifying whether the user identity information is correct, or verifying in the verification module of the highest level security system. Whether the user identity information is correct.
  • the first combination unit 55 is configured to: after the upgrade operation is performed on the system to be upgraded, the boot image file after the target system is upgraded, the boot image file after the upgrade of the system to be upgraded, and the startup of all the unupgraded systems.
  • Image file combination forming an overall boot image file for all systems;
  • the first storage unit 56 is configured to store the entire boot image file in the common system.
  • the application provides an upgrade device for a terminal.
  • This application splits the entire upgrade package of all the original systems, so that each system has its own independent upgrade package.
  • the upgrade package has its own independent startup image file and independent
  • the system upgrades the image file and the independent system image file, so that the systems are independent of each other, so each system can be upgraded separately without any system package upgrade when the system is upgraded. Therefore, the application can achieve separate upgrades of each system, independent of each other, and not mutually
  • the purpose of interference solves the problem of upgrading the general system control security system and improves the security of the security system.
  • the application further provides an upgrade apparatus for a terminal, including:
  • a second determining unit 71 configured to determine, in a system upgrade mode of at least two systems, a system upgrade mode corresponding to a target system that needs to be upgraded, and, in a case that the terminal is in a shutdown state and the user triggers a system upgrade.
  • a target upgrade package corresponding to the target system where the target upgrade package includes a boot image file, a system upgrade image file, and a system image file corresponding to the target system;
  • the second upgrading unit 72 is configured to: in the system upgrade mode corresponding to the target system, separate boot image files, independent system upgrade image files, and independent system images of the target system according to the target upgrade package. a file upgrade; wherein the target system includes a self-upgrade package independent of other systems, and the self-upgrade package includes the independent boot image file, the independent system upgrade image file, and the independent system image file. .
  • the present application provides a terminal upgrading apparatus, as shown in FIG. 8, further comprising: a second determining unit 73 for determining whether a preset condition is met;
  • the second determining unit 73 is specifically configured to determine whether the target system is a normal system; if yes, determine that the preset condition is met; if not, receive the user identity information of the terminal, and verify the user identity Whether the information is correct; when the user identity information is correct, the determination meets the preset condition; when the user identity information is incorrect, the determination does not satisfy the preset condition.
  • the second determining unit 73 verifies whether the user identity information is correct, it is specifically: verifying whether the user identity information is correct in the verification module of the highest level security system.
  • the second combination unit 74 is configured to: after the upgrade operation is performed on the other systems to be upgraded, the boot image file after the target system is upgraded, the boot image file after the upgrade of the system to be upgraded, and the startup of all the unupgraded systems. Image file combination, forming an overall boot image file for all systems;
  • the second storage unit 75 is configured to store the entire boot image file in the common system.
  • the application provides an upgrade device for a terminal.
  • This application splits the entire upgrade package of all the original systems, so that each system has its own independent upgrade package.
  • the upgrade package has its own independent startup image file and independent
  • the system upgrades the image file and the independent system image file, so that the systems are independent of each other, so each system can be upgraded separately without any need when the system is upgraded.
  • the system is upgraded. Therefore, the application can achieve the purpose of separately upgrading, independent, and non-interference of each system, solving the problem of upgrading the general system control security system, and improving the security of the security system.
  • the functions described in the method of the present embodiment can be stored in a computing device readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, a portion of the embodiments of the present application that contributes to the prior art or a portion of the technical solution may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a A computing device (which may be a personal computer, server, computing device, or network device, etc.) performs all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

本申请提供了一种终端的升级方法及装置，其中一种方法包括：在终端处于正常运行状态且用户触发系统升级的情况下，在至少两个系统中确定当前需要升级的目标系统，以及，与所述目标系统对应的目标升级包；重启所述终端，进入所述目标系统的系统升级模式中；在所述系统升级模式中按所述目标升级包，分别对所述目标系统中独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级。本申请将原来所有系统的整体升级包进行拆分，使得每个系统有自身独立的升级包，这样各个系统之间便相互独立，所以在系统升级时便可单独升级各个系统而无需所有系统整包升级。解决了普通系统控制安全系统升级的问题，提高了安全系统的安全性。

Description

一种终端升级方法及装置
本申请要求于2015年03月16日提交中国专利局，申请号为201510114265.9、发明名称为“一种终端升级方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及自动化技术领域，尤其涉及一种终端升级方法及装置。
背景技术
目前，终端，或者叫通信终端，是指可以在通讯中使用的计算机设备，一般终端中可以包含多个系统，例如：普通系统、安全系统和上网可信系统。
在一个以上系统并存的终端中，通常情况下各个系统的安全级别是不同的，例如：一个多系统终端中包括普通系统OS1(OS为Operating System，操作系统)、上网可信系统OS2和安全系统OS3，在安全级别上OS3>OS2＞OS1。
现有技术为将所有系统的升级内容设置在一个升级包中，当执行升级时所有系统同时升级，但终端只有一个系统升级模式(以下称recovery模式)，且recovery模式由普通系统OS1控制，所以会产生普通系统OS1控制上网可信系统OS2和安全系统OS3的情况。
对于上网可信系统以及安全系统而言，存在很大安全风险。
发明内容
本申请提供了一种终端升级方法及装置，各个系统的升级包分开升级、能够达到降低安全系统升级风险的目的。
为了实现上述目的，本发明提供了以下技术手段：
一种终端升级方法，包括：
在终端处于正常运行状态且用户触发系统升级的情况下，在至少两个系 统中确定当前需要升级的目标系统，以及，与所述目标系统对应的目标升级包；其中，所述目标升级包包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
重启所述终端，进入所述目标系统的系统升级模式中；
在所述系统升级模式中按所述目标升级包，分别对所述目标系统中独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
优选的，在所述进入所述目标系统的系统升级模式中之前还包括判断是否满足预设条件，所述判断是否满足预设条件的过程包括：
判断所述目标系统是否为普通系统；
如果是，则判定满足预设条件；
如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；
当所述用户身份信息正确的情况下，判定满足预设条件；
当所述用户身份信息不正确的情况下，判定不满足预设条件。
优选的，所述验证所述用户身份信息是否正确，包括：
在所述目标系统的验证模块中验证所述用户身份信息是否正确；或
在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。
优选的，还包括：
对其它待升级系统执行升级操作；
将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
将所述整体启动镜像文件存储于所述普通系统中。
一种终端升级方法，包括：
当终端处于关机状态且用户触发系统升级的情况下，在至少两个系统的系统升级模式中，确定与当前需要升级的目标系统对应的系统升级模式，和，与所述目标系统对应的目标升级包；其中，所述目标升级包中包括与所述目 标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
优选的，所述在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级具体为：判断是否满足预设条件，在满足预设条件情况下，执行在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级的步骤；
所述判断是否满足预设条件包括：
判断所述目标系统是否为普通系统；
如果是，则判定满足预设条件；
如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；
当所述用户身份信息正确的情况下，判定满足预设条件；
当所述用户身份信息不正确的情况下，判定不满足预设条件。
优选的，所述验证所述用户身份信息是否正确，包括：
在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。
优选的，还包括：
对其它待升级系统执行升级操作；
将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
将所述整体启动镜像文件存储于所述普通系统中。
一种终端升级装置，包括：
第一确定单元，用于在终端处于正常运行状态且用户触发系统升级的情况下，在至少两个系统中确定当前需要升级的目标系统，以及，与所述目标 系统对应的目标升级包；其中，所述目标升级包包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
重启单元，用于重启所述终端，进入所述目标系统的系统升级模式中；
第一升级单元，在所述系统升级模式中按所述目标升级包，分别对所述目标系统中独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
优选的，还包括用于判断是否满足预设条件的第一判断单元；
所述第一判断单元，具体用于判断所述目标系统是否为普通系统；如果是，则判定满足预设条件；如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；当所述用户身份信息正确的情况下，判定满足预设条件；当所述用户身份信息不正确的情况下，判定不满足预设条件。
优选的，还包括：
第一组合单元，用于在对其它待升级系统执行升级操作后，将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
第一存储单元，用于将所述整体启动镜像文件存储于所述普通系统中。
一种终端升级装置，包括：
第二确定单元，用于当终端处于关机状态且用户触发系统升级的情况下，在至少两个系统的系统升级模式中，确定与当前需要升级的目标系统对应的系统升级模式，和，与所述目标系统对应的目标升级包；其中，所述目标升级包中包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
第二升级单元，用于在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
与现有相比，本申请具有以下技术手段：
本申请提供了一种终端升级方法及装置，本申请将原来所有系统的整体升级包进行拆分，使得每个系统均有自身独立的升级包，升级包中有自身独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件，这样各个系统之间便相互独立，所以在系统升级时便可单独升级各个系统而无需所有系统整包升级。因此本申请能够达到各个系统分开升级、各自独立、相互不干扰的目的，解决了普通系统控制安全系统升级的问题，提高了安全系统的安全性。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例公开的一种终端的升级方法的流程图；
图2为本申请实施例公开的又一种终端的升级方法的流程图；
图3为本申请实施例公开的又一种终端的升级方法的流程图；
图4为本申请实施例公开的又一种终端的升级方法的流程图；
图5为本申请实施例公开的一种终端的升级装置的结构示意图；
图6为本申请实施例公开的又一种终端的升级装置的结构示意图；
图7为本申请实施例公开的又一种终端的升级装置的结构示意图；
图8为本申请实施例公开的又一种终端的升级装置的结构示意图。
具体实施方式
本申请发明人在研究过程中发现：对操作系统升级主要为对操作系统内的系统镜像文件system.img、系统升级镜像文件recovery.img、启动镜像文件boot.img三个分区进行升级。
在操作系统非升级状态下，各个系统在启动时要求同时启动，所以负责所有系统启动的boot.img作为一个整体供普通系统使用，在启动阶段普通系统使用整体的boot.img启动所有系统。
系统升级镜像文件recovery.img依赖于启动镜像文件boot.img，因此所 有系统的系统升级镜像文件recovery.img也作为一个整体供普通系统使用，所以在执行升级时所有系统的升级内容必须整合在一起，由普通系统对所有系统同时升级。
但普通系统的操作权限过低，由普通系统控制安全系统进行升级，会降低安全系统的风险。理论上可以将运行于普通系统中的启动镜像文件boot.img和系统升级镜像文件recovery.img转移至安全系统运行。该方式不会产生普通系统控制安全系统的问题，但这样会增加安全系统的运行程序，降低安全系统的运行速度，增加安全系统的设计难度，并且这种设计方式与常规的终端设计不符，即便设计出来也无法适用于现有终端中。
因此现在需要一种终端升级方式能够解决能够上述问题。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
目前，终端，或者叫通信终端，是指可以在通讯中使用的计算机设备，广义的讲包括个人计算机、手机、笔记本、平板电脑、POS机甚至包括车载电脑等设备。
目前，所有系统中需要经常升级的系统文件为组合在一个整体升级包内，供所有系统共用的。在本申请执行之前将所有系统共用的整体升级包进行拆分，拆分后每个系统均有独立的自身升级包。并且每个系统的自身升级包中包含独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件。然后将每个系统自身独立的升级包，对应存储至每个系统内部，以供系统升级时使用。
下面对所有系统共用的整体升级包的拆分过程，进行详细介绍：
第一步：生成每个系统的启动镜像文件。
各个系统无法单独升级的根本原因在于：所有系统的启动镜像文件boot.img是结合在一起的。所以将整体的启动镜像文件boot.img进行拆分。
整体的启动镜像文件boot.img中，有些数据是属于所有系统共用的，这部分数据在拆分的时候便复制成多份，每个系统均有一份，分别存储至每个系统的启动镜像文件中。
整体的启动镜像文件boot.img中有些数据是某个系统独自使用的，将这部分数据直接剪切至对应的系统的启动镜像文件中，直到完成整体boot.img的拆分。
在完成整体boot.img的拆分后，每个系统便有自身独立的启动镜像文件。以终端包括普通系统OS1，上网可信系统OS2和安全系统OS3为例，三个系统的启动镜像文件，分别命名为system_OS1.img、system_OS2.img和system_OS3.img。
第二步：生成每个系统的系统升级镜像文件recovery.img。
由于各个系统的所使用的recovery.img是一致的，所以将普通系统的recovery.img复制到每个系统，使得每个系统有自身独立的系统升级镜像文件。以终端包括普通系统OS1，上网可信系统OS2和安全系统OS3为例，三个系统的启动镜像文件，分别命名为recovery_OS1.img、recovery_OS2.img和recovery_OS3.img。
第三步：生成每个系统的系统镜像文件。
各个系统的系统镜像文件system.img原本便是相互分开的，因此各个系统的system.img依然保持独立即可。
以终端包括普通系统OS1，上网可信系统OS2和安全系统OS3为例，三个系统的镜像文件分别命名为system_OS1.img、system_OS2.img和system_OS3.img。
每个系统自身的启动镜像文件boot_OSX.img、系统升级镜像文件recovery_OSX.img和系统镜像文件system_OSX.img，能够组成该系统的自身升级包。
对整体升级包拆分后，每个系统均有自身独立的升级包，各个系统升级包之间相互独立、互不干扰。在系统升级时，各个系统之间无依赖关系，使得各个系统可以分开升级。
在需要升级各个系统时，由技术人员确定需要升级的内容，并将各个系统需要升级的内容，生成各个系统的自身升级包。每个系统的自身升级包中都包含该系统升级所需要的启动镜像文件、系统升级镜像文件和系统镜像文件。所有系统的自身升级包组成整体的升级包，存储于服务器端或者终端内部。
下面介绍本申请提供的终端升级方法，本方法主要应用于终端的控制器中。为了对终端各种状态下的升级方式一一说明，本申请提供两种终端升级方式，第一种适用于终端处于正常运行状态使用，第二种适用于终端处于关机状态使用。
下面针对两种升级方式一一详细介绍，首先介绍第一种升级方式：
如图1所示，本实施例提供了一种终端的升级方法，包括：
步骤S101：在终端处于正常运行状态且用户触发系统升级的情况下，在至少两个系统中确定当前需要升级的目标系统，以及，与所述目标系统对应的目标升级包；其中，所述目标升级包包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件。
终端中包括至少两个系统，至少包括普通系统OS1，上网可信系统OS2和/或安全系统OS3，当然还可以包括其他系统，在此不再赘述。当用户在一个系统内确认进行系统升级时，便将该系统作为目标系统。目标系统在服务器端或者终端内部获得整体升级包，并在整体升级包内查找与目标系统对应的自身升级包，作为目标升级包，或者目标系统在服务器端或者终端内部直接获得与目标系统对应的自身升级包，作为目标升级包。
下面介绍用户触发升级的具体过程：当终端处于正常运行状态时各个系统均处于正常工作状态，每个系统均有设置选项(以下简称Setting)，多个系统的设置选项组成设置组(以下简称Settings)。当用户在某一个系统的Setting中选择升级选项时，便是对该系统进行升级，确定当前进行操作的系统为待升级的目标系统。
不同的终端中用户触发终端升级的方式可能略有不同，在此不再一一赘述。需要说明的是：现有技术中所有用户触发终端进入升级的方式，均包含在本申请的保护范围内。
步骤S102：重启所述终端，进入所述目标系统的系统升级模式中；
对系统升级时需要重启终端才能执行升级，所以在用户触发升级后需要终端会重新启动，由于需要进行升级的为目标系统，所以重启后进入目标系统的系统升级模式中。
步骤S103：在所述系统升级模式中按所述目标升级包，分别对所述目标系统中独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文 件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
由于目标升级包中包含目标系统当前需要的升级内容，所以在系统升级模式的支持下，执行目标系统的升级过程。具体升级过程为：将目标升级包中的启动镜像文件，更新目标系统自身升级包中的启动镜像文件；将目标升级包中的系统升级镜像文件，更新目标系统自身升级包中的系统升级镜像文件；将目标升级包中的系统镜像文件，更新目标系统自身升级包中的系统镜像文件。
为了保证目标系统升级成功，在一次升级操作完成后，判断目标系统是否升级成功；当目标系统升级成功后，则可按上述方法继续对其他系统升级，当目标升级不成功时，则可以继续对目标系统升级，直到目标系统升级成功。
本申请提供了一种终端的升级方法，本申请将原来所有系统的整体升级包进行拆分，使得每个系统均有自身独立的升级包，升级包中有自身独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件，这样各个系统之间便相互独立，所以在系统升级时便可单独升级各个系统而无需所有系统整包升级。因此本申请能够达到各个系统分开升级、各自独立、相互不干扰的目的，解决了普通系统控制安全系统升级的问题，提高了安全系统的安全性。
在图1的步骤S102中，在所述进入所述目标系统的系统升级模式中之前还包括判断是否满足预设条件的步骤。如图2所示，所述判断是否满足预设条件的过程包括：
步骤S201：判断所述目标系统是否为普通系统；若是，则进入步骤S202，否则进入步骤S203。
所述至少两个系统中包括上网可信系统和/或安全系统、以及普通系统。可以理解的是，在本申请中对普通系统OS1进行身份验证也是可以实现的，只是当普通系统OS1的安全级别较低，所以可以不进行身份验证。所以当目标系统为普通系统时，不进行用户身份验证。在目标系统非普通系统时，进行用户身份验证。
在终端的所有系统中，普通系统的安全性最低，其余系统的安全性较高， 为了提高普通系统以外其余系统的安全性，在执行升级之前还需要对用户身份进行验证。
步骤S202：判定满足预设条件。
步骤S203：接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；若是，则进入步骤S202，否则进入步骤S204。
当目标系统为上网安全系统OS2或安全系统OS3时，控制器会向目标用户发送身份验证信息，用户得到身份验证信息后，向控制器输入身份验证信息，并由控制器对用户输入的身份验证信息进行验证。
具体的，控制器验证用户身份信息是否正确包括两种方式：
第一种：在所述目标系统的验证模块中验证所述用户身份信息是否正确；
上网可信系统OS2和安全系统OS3均有自身的验证模块，所以控制器在接收用户身份信息后，直接在上网可信系统OS2或安全系统OS3中验证即可，验证无误则表示用户身份信息正确。如果控制器验证用户身份信息正确时，则判定当前用户为合法用户判定满足预设条件，可以执行后续的升级。
第二种：在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。
控制器中除了有普通系统OS1、上网可信系统OS2和安全系统OS3之外，还有最高级别安全系统Secure OS，最高级别安全系统Secure OS中也有验证模块，控制器也可以采用该验证模块进行验证。
不论采用目标系统的验证模块，还是最高级别安全系统中的验证模块均可实现本验证目的。可以理解的是，如果普通系统OS1中设置有验证模块，还可以采用普通系统OS1验证用户身份信息。
步骤S204：判定不满足预设条件；
如果控制器验证用户身份信息不正确时，则判定当前用户为非法用户，判定不满足预设条件，拒绝执行后续的升级。
在目标系统升级完成后，如图3所示，本申请提供的方法还包括如下操作步骤：
步骤S301：对其它待升级系统执行升级操作；
在目标系统升级后，如若还有其他系统需要升级，则可按如图1所示的 升级方式执行升级，或者按其他方式执行升级。
步骤S302：将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合，形成所有系统的整体启动镜像文件；
步骤S303：将所述整体启动镜像文件存储于所述普通系统中。
在升级模式时由于各个系统需要分开升级，所以各个系统的启动镜像文件是分开独立的。在非升级模式中各个系统需要同时启动，为了保证各个系统同时启动，需要将负责各个系统启动的启动镜像文件，合并为整体的启动镜像文件。然后将整体的启动镜像文件存储至普通操作系统中，以便普通操作系统可以依据整体的启动镜像文件，对所有系统一并启动。
上述为本申请提供的第一种终端升级方式，下面介绍第二种终端升级方式：
如图4所示，本申请提供了一种终端的升级方法，包括：
步骤S401：当终端处于关机状态且用户触发系统升级的情况下，在至少两个系统的系统升级模式中，确定与当前需要升级的目标系统对应的系统升级模式，和，与所述目标系统对应的目标升级包；其中，所述目标升级包中包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件。
第一种方式为终端处于正常运行状态时的升级的方式，第二种方式中详细介绍终端处于关机时的升级的方式，当终端处于关机状态时用户需采用组合键的方式触发升级。组合键的方式可以为：同时按下电源键和音量上键触发升级，或同时按下电源键和音量下键触发升级。
不同的终端在终端关机状态下，触发升级的方式略有不同，需要说明的是：不论采用哪种触发终端升级的方式，均在本申请的保护范围内。
由于终端处于关机状态，各个系统均未启动，所以不能直接进入系统在Setting中进行升级，所以此时需要用户选择一个需要升级的目标系统升级模式，即目标recovery模式。由于一个recovery模式对应一个系统，所以将目标recovery模式对应的系统作为目标系统，并在服务器段或终端内获得目标升级包。
步骤S402：在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
控制器在目标系统的目标recovery模式中，按目标升级包的内容对目标系统内自身升级包进行升级，其具体执行方式图1所示的内容一致，在此不再赘述。
图4中步骤S402在具体实现时为：
判断是否满足预设条件，在满足预设条件情况下，执行在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级的步骤。
其中判断是否满足预设条件的具体执行过程，与如2所示的内容一致，本实施例与图2实施例的区别仅在于：本实施例验证用户身份信息是否正确时只有一种方式：在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。因为在本实施例中目标系统还未启动，不能采用目标系统验证用户身份信息是否正确，最高级别安全系统会与目标recovery模式同时启动，启动时间较目标系统早，所以采用最高级别安全系统的验证模块进行验证。
在系统升级完成后，本实施例还包括：对其它待升级系统执行升级操作；将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；将所述整体启动镜像文件存储于所述普通系统中。具体执行过程与图3所示的内容一致，在此不再赘述。
本申请提供了一种终端的升级方法，本申请将原来所有系统的整体升级包进行拆分，使得每个系统均有自身独立的升级包，升级包中有自身独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件，这样各个系统之间便相互独立，所以在系统升级时便可单独升级各个系统而无需所有系统整包升级。因此本申请能够达到各个系统分开升级、各自独立、相互不干扰的目的，解决了普通系统控制安全系统升级的问题，提高了安全系统的安全性。
如图5所示，本申请提供了一种终端升级装置，包括：
第一确定单元51，用于在终端处于正常运行状态且用户触发系统升级的情况下，在至少两个系统中确定当前需要升级的目标系统，以及，与所述目标系统对应的目标升级包；其中，所述目标升级包包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
重启单元52，用于重启所述终端，进入所述目标系统的系统升级模式中；
第一升级单元53，在所述系统升级模式中按所述目标升级包，分别对所述目标系统中独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
本申请提供了一种终端升级装置，如图6所示，还包括：用于判断是否满足预设条件的第一判断单元54；
所述第一判断单元，具体用于判断所述目标系统是否为普通系统；如果是，则判定满足预设条件；如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；当所述用户身份信息正确的情况下，判定满足预设条件；当所述用户身份信息不正确的情况下，判定不满足预设条件。
其中第一判断单元54在验证所述用户身份信息是否正确时，具体为接在所述目标系统的验证模块中验证所述用户身份信息是否正确；或在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。
第一组合单元55，用于在对其它待升级系统执行升级操作后，将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
第一存储单元56，用于将所述整体启动镜像文件存储于所述普通系统中。
本申请提供了一种终端的升级装置，本申请将原来所有系统的整体升级包进行拆分，使得每个系统均有自身独立的升级包，升级包中有自身独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件，这样各个系统之间便相互独立，所以在系统升级时便可单独升级各个系统而无需所有系统整包升级。因此本申请能够达到各个系统分开升级、各自独立、相互不 干扰的目的，解决了普通系统控制安全系统升级的问题，提高了安全系统的安全性。
如图7所示，本申请还提供了一种终端的升级装置，包括：
第二确定单元71，用于当终端处于关机状态且用户触发系统升级的情况下，在至少两个系统的系统升级模式中，确定与当前需要升级的目标系统对应的系统升级模式，和，与所述目标系统对应的目标升级包；其中，所述目标升级包中包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
第二升级单元72，用于在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
本申请提供了一种终端升级装置，如图8所示，还包括：用于判断是否满足预设条件的第二判断单元73；
所述第二判断单元73，具体用于判断所述目标系统是否为普通系统；如果是，则判定满足预设条件；如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；当所述用户身份信息正确的情况下，判定满足预设条件；当所述用户身份信息不正确的情况下，判定不满足预设条件。
其中第二判断单元73在验证所述用户身份信息是否正确时，具体为：在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。
第二组合单元74，用于在对其它待升级系统执行升级操作后，将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
第二存储单元75，用于将所述整体启动镜像文件存储于所述普通系统中。
本申请提供了一种终端的升级装置，本申请将原来所有系统的整体升级包进行拆分，使得每个系统均有自身独立的升级包，升级包中有自身独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件，这样各个系统之间便相互独立，所以在系统升级时便可单独升级各个系统而无需所有 系统整包升级。因此本申请能够达到各个系统分开升级、各自独立、相互不干扰的目的，解决了普通系统控制安全系统升级的问题，提高了安全系统的安全性。
本实施例方法所述的功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算设备可读取存储介质中。基于这样的理解，本申请实施例对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一台计算设备(可以是个人计算机，服务器，计算设备或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其它实施例的不同之处，各个实施例之间相同或相似部分互相参见即可。
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本申请。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本申请的精神或范围的情况下，在其它实施例中实现。因此，本申请将不会被限制于本文所示的这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。

Claims (12)

  1. 一种终端升级方法，其特征在于，包括：
    在终端处于正常运行状态且用户触发系统升级的情况下，在至少两个系统中确定当前需要升级的目标系统，以及，与所述目标系统对应的目标升级包；其中，所述目标升级包包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
    重启所述终端，进入所述目标系统的系统升级模式中；
    在所述系统升级模式中按所述目标升级包，分别对所述目标系统中独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
  2. 如权利要求1所述的方法，其特征在于，在所述进入所述目标系统的系统升级模式中之前还包括判断是否满足预设条件，所述判断是否满足预设条件的过程包括：
    判断所述目标系统是否为普通系统；
    如果是，则判定满足预设条件；
    如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；
    当所述用户身份信息正确的情况下，判定满足预设条件；
    当所述用户身份信息不正确的情况下，判定不满足预设条件。
  3. 如权利要求2所述的方法，其特征在于，所述验证所述用户身份信息是否正确，包括：
    在所述目标系统的验证模块中验证所述用户身份信息是否正确；或
    在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。
  4. 如权利要求2或3所述的方法，其特征在于，还包括：
    对其它待升级系统执行升级操作；
    将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动 镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
    将所述整体启动镜像文件存储于所述普通系统中。
  5. 一种终端升级方法，其特征在于，包括：
    当终端处于关机状态且用户触发系统升级的情况下，在至少两个系统的系统升级模式中，确定与当前需要升级的目标系统对应的系统升级模式，和，与所述目标系统对应的目标升级包；其中，所述目标升级包中包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
    在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
  6. 如权利要求5所述的方法，其特征在于，所述在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级具体为：判断是否满足预设条件，在满足预设条件情况下，执行在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级的步骤；
    所述判断是否满足预设条件包括：
    判断所述目标系统是否为普通系统；
    如果是，则判定满足预设条件；
    如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；
    当所述用户身份信息正确的情况下，判定满足预设条件；
    当所述用户身份信息不正确的情况下，判定不满足预设条件。
  7. 如权利要求6所述的方法，其特征在于，所述验证所述用户身份信息是否正确，包括：
    在最高级别安全系统的验证模块中验证所述用户身份信息是否正确。
  8. 如权利要求6或7所述的方法，其特征在于，还包括：
    对其它待升级系统执行升级操作；
    将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
    将所述整体启动镜像文件存储于所述普通系统中。
  9. 一种终端升级装置，其特征在于，包括：
    第一确定单元，用于在终端处于正常运行状态且用户触发系统升级的情况下，在至少两个系统中确定当前需要升级的目标系统，以及，与所述目标系统对应的目标升级包；其中，所述目标升级包包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
    重启单元，用于重启所述终端，进入所述目标系统的系统升级模式中；
    第一升级单元，在所述系统升级模式中按所述目标升级包，分别对所述目标系统中独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
  10. 如权利要求9所述的装置，其特征在于，还包括用于判断是否满足预设条件的第一判断单元；
    所述第一判断单元，具体用于判断所述目标系统是否为普通系统；如果是，则判定满足预设条件；如果否，则接收所述终端的用户身份信息，并验证所述用户身份信息是否正确；当所述用户身份信息正确的情况下，判定满足预设条件；当所述用户身份信息不正确的情况下，判定不满足预设条件。
  11. 如权利要求10所述的装置，其特征在于，还包括：
    第一组合单元，用于在对其它待升级系统执行升级操作后，将所述目标系统升级后的启动镜像文件、所述待升级系统升级后的启动镜像文件，以及所有未升级系统的启动镜像文件组合、形成所有系统的整体启动镜像文件；
    第一存储单元，用于将所述整体启动镜像文件存储于所述普通系统中。
  12. 一种终端升级装置，其特征在于，包括：
    第二确定单元，用于当终端处于关机状态且用户触发系统升级的情况下，在至少两个系统的系统升级模式中，确定与当前需要升级的目标系统对应的 系统升级模式，和，与所述目标系统对应的目标升级包；其中，所述目标升级包中包括与所述目标系统对应的启动镜像文件、系统升级镜像文件和系统镜像文件；
    第二升级单元，用于在所述目标系统对应的系统升级模式中，按所述目标升级包分别对所述目标系统的独立的启动镜像文件、独立的系统升级镜像文件和独立的系统镜像文件升级；其中，所述目标系统包括独立于其他系统的自身升级包，所述自身升级包中包含所述独立的启动镜像文件、所述独立的系统升级镜像文件和所述独立的系统镜像文件。
PCT/CN2015/075591 2015-03-16 2015-03-31 一种终端升级方法及装置 Ceased WO2016145679A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510114265.9 2015-03-16
CN201510114265.9A CN104754043B (zh) 2015-03-16 2015-03-16 一种终端升级方法及装置

Publications (1)

Publication Number Publication Date
WO2016145679A1 true WO2016145679A1 (zh) 2016-09-22

Family

ID=53593130

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075591 Ceased WO2016145679A1 (zh) 2015-03-16 2015-03-31 一种终端升级方法及装置

Country Status (2)

Country Link
CN (1) CN104754043B (zh)
WO (1) WO2016145679A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110399153A (zh) * 2019-07-25 2019-11-01 Oppo广东移动通信有限公司 系统升级方法、装置、终端及计算机可读存储介质
CN111857777A (zh) * 2020-07-16 2020-10-30 南方电网数字电网研究院有限公司 基于双芯智能电表的系统更新方法、装置和计算机设备
CN112363742A (zh) * 2020-11-03 2021-02-12 北京牛电科技有限责任公司 一种固件系统升级方法、装置、设备及介质
CN112631626A (zh) * 2020-12-02 2021-04-09 广东中兴新支点技术有限公司 基于双系统的系统升级方法、装置及存储介质
CN116800821A (zh) * 2023-08-23 2023-09-22 Tcl通讯科技（成都）有限公司 系统升级方法、装置、存储介质及电子设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104754043B (zh) * 2015-03-16 2018-07-27 西安酷派软件科技有限公司 一种终端升级方法及装置
CN107809324B (zh) * 2016-09-07 2022-01-25 中兴通讯股份有限公司 一种车载自动诊断系统设备及其升级方法
CN106897100A (zh) * 2017-02-28 2017-06-27 深圳天珑无线科技有限公司 一种固件升级的方法及终端
CN107562439A (zh) * 2017-09-29 2018-01-09 河南职业技术学院 基于计算机的固件升级方法及固件升级装置
CN113703797B (zh) * 2020-05-20 2023-06-09 成都鼎桥通信技术有限公司 一种行业安全终端的系统升级方法
CN112925543A (zh) * 2021-02-25 2021-06-08 广东电网有限责任公司电力调度控制中心 一种密码芯片嵌入式应用升级方法及装置
CN116088914A (zh) * 2022-12-16 2023-05-09 北京经纬恒润科技股份有限公司 多核异构片上系统升级方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102141921A (zh) * 2010-02-03 2011-08-03 华为终端有限公司 一种终端设备系统升级方法及终端设备
CN102346673A (zh) * 2010-07-27 2012-02-08 比亚迪股份有限公司 一种手机系统升级的方法及装置
CN104754043A (zh) * 2015-03-16 2015-07-01 西安酷派软件科技有限公司 一种终端升级方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102141921A (zh) * 2010-02-03 2011-08-03 华为终端有限公司 一种终端设备系统升级方法及终端设备
CN102346673A (zh) * 2010-07-27 2012-02-08 比亚迪股份有限公司 一种手机系统升级的方法及装置
CN104754043A (zh) * 2015-03-16 2015-07-01 西安酷派软件科技有限公司 一种终端升级方法及装置

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110399153A (zh) * 2019-07-25 2019-11-01 Oppo广东移动通信有限公司 系统升级方法、装置、终端及计算机可读存储介质
CN110399153B (zh) * 2019-07-25 2023-11-03 Oppo广东移动通信有限公司 系统升级方法、装置、终端及计算机可读存储介质
CN111857777A (zh) * 2020-07-16 2020-10-30 南方电网数字电网研究院有限公司 基于双芯智能电表的系统更新方法、装置和计算机设备
CN111857777B (zh) * 2020-07-16 2024-02-27 南方电网数字电网科技(广东)有限公司 基于双芯智能电表的系统更新方法、装置和计算机设备
CN112363742A (zh) * 2020-11-03 2021-02-12 北京牛电科技有限责任公司 一种固件系统升级方法、装置、设备及介质
CN112631626A (zh) * 2020-12-02 2021-04-09 广东中兴新支点技术有限公司 基于双系统的系统升级方法、装置及存储介质
CN112631626B (zh) * 2020-12-02 2023-11-14 广东中兴新支点技术有限公司 基于双系统的系统升级方法、装置及存储介质
CN116800821A (zh) * 2023-08-23 2023-09-22 Tcl通讯科技（成都）有限公司 系统升级方法、装置、存储介质及电子设备
CN116800821B (zh) * 2023-08-23 2023-12-15 Tcl通讯科技（成都）有限公司 系统升级方法、装置、存储介质及电子设备

Also Published As

Publication number Publication date
CN104754043A (zh) 2015-07-01
CN104754043B (zh) 2018-07-27

Similar Documents

Publication Publication Date Title
WO2016145679A1 (zh) 一种终端升级方法及装置
US20080215872A1 (en) Method of booting electronic device and method of authenticating boot of electronic device
US10628588B2 (en) Information processing apparatus and computer readable storage medium
US11671379B1 (en) System and method for subscription management using dynamically composed management entities
US11520891B1 (en) Secure boot of an integrated circuit
JP2015055898A (ja) セキュアブート方法、半導体装置、及び、セキュアブートプログラム
CN111353150B (zh) 一种可信启动方法、装置、电子设备及可读存储介质
US12093102B2 (en) System and method for power state enforced subscription management
EP3153968B1 (en) Multi-system terminal system updating method, updating device and terminal
CN103778006B (zh) 一种操作系统进程控制方法
CN111522569A (zh) 基于Hypervisor的嵌入式多系统升级方法及计算机可读存储介质
WO2018024198A1 (zh) 机顶盒的应用程序升级方法、系统及机顶盒
CN113626059B (zh) 系统升级方法、摄像机及计算机可读存储介质
US12045352B2 (en) Electronic control device and control method
CN110895609B (zh) 信息处理设备及其控制方法以及存储介质
CN112612498A (zh) 一种嵌入式设备升级方法和嵌入式设备
CN112307481A (zh) 一种系统可信启动方法、电子设备及计算机可读存储介质
CN100357893C (zh) 一种终端升级方法及系统
JP2014179039A (ja) 情報処理装置、情報処理方法及びプログラム
CN107615293A (zh) 包括期满检测的平台管理方法和装备
CN113312071A (zh) 一种ssd设备固件升级方法及相关装置
CN109284137B (zh) 一种基于Hypervisor的QNX操作系统启动方法及装置
CN114594975B (zh) 固件管理方法、装置、存储介质及电子设备
CN113721959A (zh) 一种信息处理方法、装置及电子设备
WO2016184180A1 (zh) 一种系统安全启动方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15885062

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13/02/2018)

122 Ep: pct application non-entry in european phase

Ref document number: 15885062

Country of ref document: EP

Kind code of ref document: A1