WO2018032757A1 - 组件升级的方法及装置 - Google Patents

组件升级的方法及装置 Download PDF

Info

Publication number
WO2018032757A1
WO2018032757A1 PCT/CN2017/076543 CN2017076543W WO2018032757A1 WO 2018032757 A1 WO2018032757 A1 WO 2018032757A1 CN 2017076543 W CN2017076543 W CN 2017076543W WO 2018032757 A1 WO2018032757 A1 WO 2018032757A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
upgrade file
upgrade
file
component upgrade
Prior art date
Application number
PCT/CN2017/076543
Other languages
English (en)
French (fr)
Inventor
齐志强
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018032757A1 publication Critical patent/WO2018032757A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating

Definitions

  • the present disclosure relates to system upgrade techniques for mobile terminals, such as a method and apparatus for component upgrade.
  • smart mobile terminals have become an indispensable tool for people.
  • the emergence of smart phones makes mobile phones no longer a single, unchanging communication tool.
  • the ever-rich functions and defects of the operating system of smart phones make the upgrade of the operating system of mobile phones a necessary function of smart phones.
  • the operating system upgrade method of Android Android smartphone includes offline upgrade of Secure Digital (SD) card package and online upgrade of Firmware Over The Air (FOTA); users can download FOTA upgrade package from server side and download directly to smart In the mobile phone, the upgrade package is stored in the SD card and then read by the smart phone.
  • SD Secure Digital
  • FOTA Firmware Over The Air
  • the smart phone When the smart phone performs the operating system upgrade, the smart phone automatically restarts into the recovery mode to write to the system partition, after the operating system upgrade is completed. Restart your smartphone and complete the upgrade.
  • the present disclosure provides a method and apparatus for component upgrade to solve at least one of the following technical problems: independent upgrade of components, no need to upgrade with operating system update upgrade; flexibility of component upgrade; upgrade The risk of operating system failure.
  • a method for component upgrade may include: acquiring a component upgrade file; storing the component upgrade file into a specific partition that includes a component un-upgrade file; and the component is not upgraded file in the specific partition The first component in the component is replaced with the second component in the component upgrade file; and when the operating system is restarted, the second component is loaded in the specific partition.
  • the replacing the first component in the component non-upgrade file with the second component in the component upgrade file in the specific partition may include: extracting the The second component in the component upgrade file and the first component in the component non-upgrade file replaces the first component with the second component.
  • the method may further include: verifying the security and integrity of the component upgrade file, and determining whether the component upgrade file is a secure and complete component upgrade file.
  • the replacing the first component in the component non-upgrade file with the second component in the component upgrade file in the specific partition may The method includes: replacing a first component in the component non-upgrade file with a second component in the secure and complete component upgrade file in the specific partition.
  • the verifying the security and integrity of the component upgrade file, determining whether the component upgrade file is a secure and complete component upgrade file may include: determining a location obtained from the server side The MD5 value of the fifth edition of the information digest algorithm of the component upgrade file is consistent with the MD5 value carried in the component upgrade file.
  • the component upgrade file acquired from the server side is consistent with the MD5 value carried in the component upgrade file, it is determined that the component upgrade file is a secure and complete component upgrade file.
  • the method may further include: determining the component The result of the upgrade is sent to the server side.
  • a device for upgrading components may include: a transceiver module, a read/write module, a control module, and a loading module.
  • the transceiver module is set to obtain the component upgrade file.
  • the read/write module is configured to store the component upgrade file in a particular partition that contains the component's unupgraded file.
  • the control module is configured to replace the first component of the component non-upgrade file with the second component of the component upgrade file in the particular partition.
  • the load module is configured to load the second component in the particular partition after the operating system is restarted.
  • control module may be further configured to control, in the specific partition, the read/write module to extract a second component in the component upgrade file, and a first component in the component unupgraded file,
  • control module is further specifically configured to replace the first component with the second component.
  • the device may further comprise a security module.
  • the security module is configured to verify the security and integrity of the component upgrade file, and determine whether the component upgrade file is a secure and complete component upgrade file;
  • the control module can also be configured to replace the first component of the component non-upgrade file with the second component of the secure and complete component upgrade file in the particular partition.
  • the security module may be further configured to: determine whether the fifth version MD5 value of the information digest algorithm of the component upgrade file acquired from the server side is consistent with the MD5 value carried in the component upgrade file, when The MD5 value of the component upgrade file obtained by the server side is consistent with the MD5 value carried in the component upgrade file, and the component upgrade file is determined to be a secure and complete component upgrade file; when obtained from the server side If the MD5 value of the component upgrade file is inconsistent with the MD5 value carried in the component upgrade file, it is determined that the component upgrade file is an unsafe and incomplete component upgrade file.
  • control module may be further configured to determine an upgrade result of the component.
  • the transceiver module may be further configured to send the upgrade result to the server side.
  • a non-transitory computer readable storage medium storing computer executable instructions for performing any of the above described component upgrade methods.
  • An electronic device comprising one or more processors, a memory, and one or more programs, the one or more programs being stored in a memory, when executed by one or more processors, performing any of the above A method of component upgrade.
  • a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to execute The method of upgrading any of the above components.
  • the device for upgrading components acquires a component upgrade file; and stores the component upgrade file into a specific partition that includes a component unupgraded file; The first component in the component non-upgrade file is replaced with the second component in the component upgrade file; when the operating system is restarted, the second component is loaded in the specific partition.
  • Independent upgrade of components can be implemented without the need to upgrade with the upgrade of the operating system, which can improve the flexibility of component upgrade and reduce the risk of failure to upgrade the operating system.
  • FIG. 1 is a flowchart of Embodiment 1 of a method for upgrading a component.
  • FIG. 2 is a flowchart of Embodiment 2 of a method for component upgrade.
  • FIG. 3 is a schematic structural diagram of an apparatus embodiment for component upgrade.
  • FIG. 4 is a schematic structural diagram of a terminal embodiment of component upgrade.
  • the method for component upgrade of this embodiment can be applied to a smart mobile terminal, such as an intelligent mobile terminal with an Android operating system.
  • FIG. 1 is a flowchart of Embodiment 1 of a method for component upgrade. As shown in FIG. 1 , the method for component upgrade may include Step 110 - Step 140.
  • step 110 a component upgrade file is obtained.
  • the smart mobile terminal of the Android operating system (hereinafter referred to as the mobile terminal) obtains the component upgrade file of the component to be upgraded.
  • the mobile terminal may obtain the component upgrade file of the upgrade component from the SD card, or use the FOTA online upgrade technology to obtain the component upgrade file of the component to be upgraded from the server side.
  • the server side staff can separately establish the upgrade information and the upgrade file corresponding to each component into upgrade packages, and push them to the users of the mobile terminal for users to view and download.
  • the component may include firmware corresponding to each hardware in the smart mobile terminal and a library file in the smart mobile terminal, for example, the firmware may include touch screen firmware, fingerprint firmware, speaker firmware, and the like.
  • step 120 the component upgrade file is stored in a particular partition that contains the component unupgraded file.
  • the mobile terminal stores the obtained component upgrade file of the upgrade component to be needed into a specific partition, which is not a system partition, and only allows specific application processes to have read and write access rights, and other non-specific application processes only read or No access rights.
  • the specific partition and the file of the component in the specific partition may be set when the mobile terminal is shipped from the factory.
  • the mobile terminal may include a system partition and a specific partition, and the file and fingerprint of the touch screen firmware are included in the specific partition.
  • the application process that uses the touch screen firmware will load the file of the touch screen firmware directly in the specific partition for the special partition; when the mobile terminal restores the factory settings, the data in this particular partition will not be erased. .
  • component files that can be included in a specific partition and which application processes can access the specific partition can be set according to actual needs, which is not limited herein.
  • step 130 the first component of the component non-upgrade file is replaced with the second component of the component upgrade file in the particular partition.
  • the mobile terminal replaces the first component in the component non-upgrade file of the upgrade component to be the second component in the obtained component upgrade file in the specific partition.
  • the mobile terminal extracts the second component in the component upgrade file and the first group in the component unupgraded file in the specific partition. And replacing the first component with the second component.
  • the first component may be an old component in the mobile terminal
  • the second component may be a new component in the mobile terminal
  • step 140 the second component is loaded in the particular partition when the operating system is restarted.
  • the application process loads the second component from the specific partition to complete the independent upgrade of the component.
  • the mobile terminal obtains a component upgrade file by storing the component upgrade file into a specific partition that includes the component unupgraded file; and the component is not in the specific partition.
  • the first component in the upgrade file is replaced with the second component in the component upgrade file; when the operating system is restarted, the second component is loaded in the specific partition.
  • FIG. 2 is a flowchart of Embodiment 2 of a component upgrade method.
  • the component upgrade method provided in this embodiment may be applied to a smartphone of an Android operating system (hereinafter referred to as a mobile phone), and the component is FOTA online.
  • the component upgrade method can be run by the component upgrade system in the smart phone.
  • the component upgrade system can include a transceiver subsystem, a file write/write subsystem, a master control subsystem, and a security subsystem.
  • the method can include steps 201-208.
  • step 201 the component upgrade system runs in the background.
  • the component upgrade system of the mobile phone runs in the background.
  • step 202 a component upgrade file is obtained.
  • the transceiver subsystem receives and acquires component upgrade files pushed by the server side.
  • step 203 the component upgrade file is stored in a specific partition that contains the component non-upgrade file.
  • the transceiver subsystem stores the received and acquired component upgrade files into a specific partition that contains the component's unupgraded files.
  • a specific partition in the mobile terminal refer to the related content in the foregoing embodiment in step 120, and the description is not repeated here.
  • step 204 verifying the security and integrity of the component upgrade file, determining Whether the component upgrade file is a secure and complete component upgrade file.
  • the security subsystem verifies the security and integrity of the component upgrade file and determines whether the component upgrade file is a secure and complete component upgrade file.
  • the security subsystem determines whether the value of the message digest algorithm (MD5) of the component upgrade file obtained from the server side is consistent with the MD5 value carried in the component upgrade file.
  • MD5 value of the component upgrade file obtained from the server side is inconsistent with the MD5 value carried in the component upgrade file
  • determining that the component upgrade file is an unsafe and incomplete component upgrade file is performed in step 205. The operation in .
  • step 206 Operation When the MD5 value of the component upgrade file obtained from the server side is consistent with the MD5 value carried in the component upgrade file, determining that the component upgrade file is a secure and complete component upgrade file, and executing in step 206 Operation.
  • step 205 the processing task ends.
  • the security subsystem reports the current component upgrade file to the main control subsystem as an unsafe and incomplete component upgrade file, and the main control subsystem ends the component upgrade task.
  • step 206 the first component of the component non-upgrade file is replaced with the second component of the secure and complete component upgrade file in the particular partition.
  • the security subsystem reports the current component upgrade file to the main control subsystem as a secure and complete component upgrade file, and the main control subsystem sends a command to the file write/write subsystem to indicate that the file write/write subsystem is in the
  • the second component in the secure and complete component upgrade file, the first component in the component non-upgrade file, and the first component are replaced by the second component.
  • the first component may be an old component in a mobile phone
  • the second component may be a new component in a mobile phone.
  • step 207 an upgrade result of the component is determined, and the upgrade result is sent to the server side.
  • the main control subsystem determines whether the upgrade result of the component is a success or a failure, and sends the upgrade result to the transceiver subsystem, and the transceiver subsystem sends the upgrade result to the server side; the server side can successfully count according to the upgrade result. And failed data to improve the security and completion of component upgrade files Integrity and improve the quality of service for users.
  • step 208 the second component is loaded in the particular partition when the operating system is restarted.
  • the main control subsystem loads the security and complete component upgrade files in the specific partition to complete independent upgrade of the components.
  • the method for upgrading a component is run in the background by a component upgrade system of the mobile phone; acquiring a component upgrade file; storing the component upgrade file in a specific partition that includes the component not upgraded file; Verifying the security and integrity of the upgrade file, determining whether the component upgrade file is a secure and complete component upgrade file; replacing the first component in the component non-upgrade file with the specific partition in the specific partition A second component in the secure and complete component upgrade file; determining an upgrade result of the component, transmitting the upgrade result to the server side; loading the second component in the specific partition when the operating system is restarted.
  • Independent upgrade of components can be implemented without the need to upgrade with the upgrade of the operating system, which can improve the flexibility of component upgrade and reduce the risk of failure to upgrade the operating system.
  • the upgrade process of the component does not require user participation, and the user does not perceive it, and can achieve the silent upgrade effect.
  • the device 03 for component upgrade provided in this embodiment may include: a transceiver module 310, a read/write module 320, a control module 330, and a loading module 340.
  • the transceiver module 310 is configured to acquire a component upgrade file.
  • the read/write module 320 is configured to store the component upgrade file into a particular partition that contains a component unupgraded file.
  • the control module 330 is configured to replace the first component of the component non-upgrade file with the second component of the component upgrade file in the particular partition.
  • the load module 340 is configured to load the second component in the particular partition after the operating system is restarted.
  • control module 330 is further configured to control, in the specific partition, the read/write module 32 to extract a second component in the component upgrade file, and a first one of the component unupgraded files. Component.
  • the control module 330 can also be configured to replace the first component with the second component.
  • the device may further include: a security module 350.
  • the security module 350 is configured to verify the security and integrity of the component upgrade file to determine whether the component upgrade file is a secure and complete component upgrade file.
  • the control module 330 can also be configured to replace the first component of the component non-upgrade file with the second component of the secure and complete component upgrade file in the particular partition.
  • the security module 350 is further configured to determine whether the fifth version MD5 value of the information digest algorithm of the component upgrade file acquired from the server side is consistent with the MD5 value carried by the component upgrade file.
  • the security module 350 determines whether the fifth version MD5 value of the information digest algorithm of the component upgrade file acquired from the server side is consistent with the MD5 value carried by the component upgrade file.
  • the MD5 value of the component upgrade file acquired from the server side is consistent with the MD5 value carried in the component upgrade file, it is determined that the component upgrade file is a secure and complete component upgrade file.
  • the MD5 value of the component upgrade file acquired from the server side is inconsistent with the MD5 value carried in the component upgrade file, it is determined that the component upgrade file is an unsafe and incomplete component upgrade file.
  • control module 330 may be further configured to determine an upgrade result of the component.
  • the transceiver module 310 can also be configured to send the upgrade result to the server side.
  • the device upgraded by the component of the embodiment can perform the technical solution of the method embodiment shown above.
  • the transceiver module 310, the read/write module 320, the control module 330, the loading module 340, and the security module 350 may each be a central processing unit (CPU) and a microprocessor located in the device upgraded by the component.
  • CPU central processing unit
  • MPU Micro Processor Unit
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • the component upgraded terminal 04 provided in this embodiment includes: an interface 410, a bus 420, a memory 430 and a processor 440, and the interface 410 and the memory.
  • 430 is coupled to processor 440 via a bus 420 that is configured to store instructions that the processor 440 reads to perform the following operations.
  • Obtaining a component upgrade file storing the component upgrade file in a specific partition that includes a component non-upgrade file; replacing the first component in the component non-upgrade file with the component upgrade file in the specific partition Second component; when the operating system is restarted, loading the specific partition Said second component.
  • the processor 440 reads the instruction, and may extract, in the specific partition, a second component in the component upgrade file, and a first component in the component non-upgrade file, where the The first component is replaced with the second component.
  • the processor 440 reads the instruction to verify the security and integrity of the component upgrade file, and determines whether the component upgrade file is a secure and complete component upgrade file.
  • the first component of the component non-upgrade file is replaced with the second component of the secure and complete component upgrade file in the particular partition.
  • the processor 440 reads the command to determine whether the fifth version MD5 value of the information digest algorithm of the component upgrade file acquired from the server side is consistent with the MD5 value carried by the component upgrade file.
  • the processor 440 reads the command to determine whether the fifth version MD5 value of the information digest algorithm of the component upgrade file acquired from the server side is consistent with the MD5 value carried by the component upgrade file.
  • the MD5 value of the component upgrade file acquired from the server side is consistent with the MD5 value carried in the component upgrade file, it is determined that the component upgrade file is a secure and complete component upgrade file.
  • the MD5 value of the component upgrade file obtained from the server side is inconsistent with the MD5 value carried in the component upgrade file, it is determined that the component upgrade file is an unsafe and incomplete component upgrade file.
  • the processor 440 reads the instruction to determine an upgrade result of the component, and sends the upgrade result to the server side.
  • the terminal upgraded by the component of the embodiment can perform the technical solution of the method embodiment shown in the foregoing.
  • the embodiment further provides a non-transitory computer readable storage medium storing computer executable instructions for performing the method of upgrading any one of the above components.
  • the disclosure can be provided as a method, system, or computer program product.
  • This embodiment may take the form of a hardware embodiment, a software embodiment, or an embodiment in combination with software and hardware.
  • the present embodiments can take the form of a computer program product embodied on one or more computer usable storage media (including but not limited to disk storage and optical storage, etc.) in which computer usable program code is embodied.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the method and device for upgrading a component can implement independent upgrade of components, and can be upgraded without upgrading with an operating system update, which can improve the flexibility of component upgrade and reduce the risk of failure of upgrading the operating system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

一种组件升级的方法和装置，包括：获取组件升级文件；将所述组件升级文件存储到包含有组件未升级文件的特定分区中；在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件；当操作系统重启后，在所述特定分区中加载所述第二组件。

Description

组件升级的方法及装置 技术领域
本公开涉及移动终端的系统升级技术，例如涉及一种组件升级的方法及装置。
背景技术
随着智能移动终端在人们日常生活中越来越广泛的应用，智能移动终端已成为人们必不可少的工具。例如智能手机的出现，使手机不再是单一的、不变的通信工具，智能手机的操作系统不断丰富的功能和缺陷的修复使得手机的操作系统升级成为智能手机必要的一个功能。
安卓Android智能手机的操作系统升级的方法包括安全数字(Secure Digital，SD)卡包离线升级和空中固件(Firmware Over The Air，FOTA)在线升级；用户可以从服务器侧下载FOTA升级包直接下载到智能手机中或者将升级包存储在SD卡中再通过智能手机读取，智能手机进行操作系统升级时会自动重启进入恢复(recovery)模式对系统(system)分区进行写操作，待操作系统升级完成后重启智能手机，完成升级。
但智能手机中的组件如触摸屏(Touch Panel，TP)固件、指纹识别固件、库文件等都不能独立升级，只能采用系统升级的方法，必须随着操作系统更新版本发布的时候升级，而且一次升级中通常包含很多组件的修改，这样不仅缺乏灵活性，而且还加大了升级操作系统失败的风险。
发明内容
本公开提供了一种组件升级的方法及装置，以至少解决以下之一的技术问题：组件的独立升级，无需随着操作系统更新升级时连带升级的问题；组件升级的灵活性的问题；升级操作系统失败的风险问题。
一种组件升级的方法，所述方法可以包括：获取组件升级文件；将所述组件升级文件存储到包含有组件未升级文件的特定分区中；在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件；以及当操作系统重启后，在所述特定分区中加载所述第二组件。
可选地，所述在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件，可以包括：在所述特定分区中提取出所述组件升级文件中的第二组件、及所述组件未升级文件中的第一组件，将所述第一组件替换成所述第二组件。
可选地，在所述将所述组件升级文件存储到包含有组件未升级文件的特定分区中之后，在所述将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件之前，所述方法还可以包括：对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件。
当所述组件升级文件为安全和完整的组件升级文件时，所述在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件，可以包括：在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件。
可选地，所述对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件，可以包括：判断从所述服务器侧获取的所述组件升级文件的信息摘要算法第五版MD5值与所述组件升级文件携带的MD5值是否一致。
当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值一致，则确定所述组件升级文件为安全和完整的组件升级文件。
当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值不一致，则确定所述组件升级文件为不安全和不完整的组件升级文件。
可选地，在在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件之后，所述方法还可以包括：确定所述组件的 升级结果，将所述升级结果发送到服务器侧。
一种组件升级的装置，所述装置可以包括：收发模块、读写模块、控制模块和加载模块。
收发模块设置为获取组件升级文件。
读写模块设置为将所述组件升级文件存储到包含有所述组件未升级文件的特定分区中。
控制模块设置为在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件。
加载模块设置为当操作系统重启后，在所述特定分区中加载所述第二组件。
可选地，所述控制模块还可以设置为在所述特定分区中控制所述读写模块提取出所述组件升级文件中的第二组件、及所述组件未升级文件中的第一组件，所述控制模块，还具体用于将所述第一组件替换成所述第二组件。
可选地，所述装置还可以包括安全模块。
安全模块设置为对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件；
所述控制模块还可以设置为在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件。
可选地，所述安全模块还可以设置为判断从所述服务器侧获取的所述组件升级文件的信息摘要算法第五版MD5值与所述组件升级文件携带的MD5值是否一致，当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值一致，则确定所述组件升级文件为安全和完整的组件升级文件；当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值不一致，则确定所述组件升级文件为不安全和不完整的组件升级文件。
可选地，所述控制模块还可以设置为确定所述组件的升级结果。
所述收发模块还可以设置为将所述升级结果发送到服务器侧。
一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任意一种组件升级的方法。
一种电子设备，该电子设备包括一个或多个处理器、存储器以及一个或多个程序，所述一个或多个程序存储在存储器中，当被一个或多个处理器执行时，执行上述任意一种组件升级的方法。
一种计算机程序产品，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算机程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行上述任意一种组件升级的方法。
本实施例提供的组件升级的方法及装置，组件升级的装置通过获取组件升级文件；将所述组件升级文件存储到包含有组件未升级文件的特定分区中；在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件；当操作系统重启后，在所述特定分区中加载所述第二组件。可以实现组件的独立升级，无需随着操作系统更新升级时连带升级，可以提高组件升级的灵活性，降低升级操作系统失败的风险。
附图说明
图1为组件升级的方法实施例一的流程图。
图2为组件升级的方法实施例二的流程图。
图3为组件升级的装置实施例的结构示意图。
图4为组件升级的终端实施例的结构示意图。
具体实施方式
本实施例的组件升级的方法可以应用在智能移动终端上，例如具有安卓(Android)操作系统的智能移动终端。
下面将结合本实施例中的附图，对本实施例中的技术方案进行清楚、完整地描述。在不冲突的情况下，以下实施例和实施例中的特征可以相互组合。
图1为组件升级的方法实施例一的流程图，如图1所示，组件升级的方法可以包括步骤110-步骤140。
在步骤110中，获取组件升级文件。
Android操作系统的智能移动终端(以下简称移动终端)获取待需要升级组件的组件升级文件。可选地，移动终端可以从SD卡中获取待需要升级组件的组件升级文件，也可以利用FOTA在线升级技术，从服务器侧获取待需要升级组件的组件升级文件。
服务器侧的工作人员可以将每个组件对应的升级信息及升级文件分别单独建立成升级包，推送给移动终端的用户，供用户查看和下载。
可选地，组件可以包括智能移动终端中的每个硬件对应的固件以及智能移动终端中的库文件，例如固件可以包括触摸屏固件、指纹固件、扬声器固件等等。
在步骤120中，将所述组件升级文件存储到包含有组件未升级文件的特定分区中。
移动终端将获取到的待需要升级组件的组件升级文件存储到一个特定分区中，该特定分区并不是系统分区，只允许特定的应用进程具有读写访问权限，其他非特定的应用进程只有读或没有访问权限。该特定分区以及特定分区中具有的组件的文件可以是在移动终端出厂时设置好的，例如，移动终端在出厂时，可以包括系统分区和特定分区，在特定分区中包括触摸屏固件的文件、指纹识别固件的文件等，需要用到触摸屏固件的应用进程会直接在特定分区中加载触摸屏固件的文件供该特别分区使用；在移动终端恢复出厂设置时，不会将这个特定分区中的数据擦除。
可选地，特定分区中可以包含的组件文件以及哪些应用进程能够访问该特定分区可以根据实际需求进行设置，在此不加以限定。
在步骤130中，在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件。
移动终端在该特定分区中将待需要升级组件的组件未升级文件中的第一组件替换成获取到的该组件升级文件中的第二组件。可选地，移动终端在该特定分区中提取出该组件升级文件中的第二组件、及该组件未升级文件中的第一组 件，将该第一组件替换成该第二组件。
可选地，第一组件可以为移动终端中的旧组件，第二组件可以为移动终端中的新组件。
在步骤140中，当操作系统重启后，在所述特定分区中加载所述第二组件。
当移动终端重启后，应用进程从该特定分区中加载该第二组件，完成对组件的独立升级。
本实施例提供的组件升级的方法，移动终端通过获取组件升级文件；将所述组件升级文件存储到包含有所述组件未升级文件的特定分区中；在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件；当操作系统重启后，在所述特定分区中加载所述第二组件。可以实现组件的独立升级，无需随着操作系统更新升级时连带升级，可以提高组件升级的灵活性，降低升级操作系统失败的风险。
图2为组件升级的方法实施例二的流程图，如图2所示，本实施例提供的组件升级的方法可以应用在Android操作系统的智能手机(以下简称手机)上，针对组件进行FOTA在线升级，该组件升级的方法可以通过智能手机中的组件升级系统运行，该组件升级系统可以包括收发子系统、文件写入/写出子系统、主控子系统、安全子系统。该方法可以包括步骤201-步骤208。
在步骤201中，组件升级系统在后台运行。
可选地，手机的组件升级系统在后台运行。
在步骤202中，获取组件升级文件。
收发子系统接收、获取服务器侧推送的组件升级文件。
在步骤203中，将所述组件升级文件存储到包含有组件未升级文件的特定分区中。
收发子系统将接收、获取到的组件升级文件存储到包含有所述组件未升级文件的特定分区中。关于移动终端中特定分区的描述可以参见上述实施例在步骤120中的相关内容，在此不重复描述。
在步骤204中，对所述组件升级文件的安全性和完整性进行校验，确定所 述组件升级文件是否为安全和完整的组件升级文件。
安全子系统对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件。
可选地，安全子系统判断从所述服务器侧获取的所述组件升级文件的信息摘要算法第五版(Message Digest Algorithm 5，MD5)值与所述组件升级文件携带的MD5值是否一致。当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值不一致，则确定所述组件升级文件为不安全和不完整的组件升级文件，执行在步骤205中的操作。
当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值一致，则确定所述组件升级文件为安全和完整的组件升级文件，并执行在步骤206中的操作。
在步骤205中，结束处理任务。
安全子系统向主控子系统上报当前组件升级文件为不安全和不完整的组件升级文件，主控子系统结束组件的升级任务。
在步骤206中，在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件。
安全子系统向主控子系统上报当前组件升级文件为安全和完整的组件升级文件，主控子系统向文件写入/写出子系统发送命令，指示文件写入/写出子系统在所述特定分区中提取出安全和完整的组件升级文件中的第二组件、组件未升级文件中的第一组件，将该第一组件替换成第二组件。
可选地，第一组件可以为手机中的旧组件，第二组件可以为手机中的新组件。
在步骤207中，确定所述组件的升级结果，将所述升级结果发送到服务器侧。
主控子系统确定所述组件的升级结果是成功还是失败，并将所述升级结果发送到收发子系统，收发子系统再将所述升级结果发送给服务器侧；服务器侧根据升级结果可以统计成功和失败的数据，以提高组件升级文件的安全性和完 整性，并改善针对用户的服务质量。
在步骤208中，当操作系统重启后，在所述特定分区中加载所述第二组件。
主控子系统在当操作系统重启后，在所述特定分区中加载所述安全和完整的所述组件升级文件，完成对所述组件的独立升级。
本实施例提供的组件升级的方法，通过手机的组件升级系统在后台运行；获取组件升级文件；将所述组件升级文件存储到包含有所述组件未升级文件的特定分区中；对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件；在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件；确定所述组件的升级结果，将所述升级结果发送到服务器侧；当操作系统重启后，在所述特定分区中加载所述第二组件。可以实现组件的独立升级，无需随着操作系统更新升级时连带升级，可以提高组件升级的灵活性，降低升级操作系统失败的风险。另外，组件的升级过程不需要用户参与，用户也感知不到，还可以达到静默升级效果。
图3为组件升级的装置实施例的结构示意图，如图3所示，本实施例提供的组件升级的装置03可以包括：收发模块310、读写模块320、控制模块330和加载模块340。
所述收发模块310设置为获取组件升级文件。
所述读写模块320设置为将所述组件升级文件存储到包含有组件未升级文件的特定分区中。
所述控制模块330设置为在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件。
所述加载模块340设置为当操作系统重启后，在所述特定分区中加载所述第二组件。
可选地，所述控制模块330还可以设置为在所述特定分区中控制所述读写模块32提取出所述组件升级文件中的第二组件、及所述组件未升级文件中的第一组件。所述控制模块330还可以设置为将所述第一组件替换成所述第二组件。
可选地，所述装置还可以包括：安全模块350。
所述安全模块350设置为对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件。
所述控制模块330还可以设置为在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件。
可选地，所述安全模块350还可以设置为判断从所述服务器侧获取的所述组件升级文件的信息摘要算法第五版MD5值与所述组件升级文件携带的MD5值是否一致。当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值一致，则确定所述组件升级文件为安全和完整的组件升级文件。当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值不一致，则确定所述组件升级文件为不安全和不完整的组件升级文件。
可选地，所述控制模块330还可以设置为确定所述组件的升级结果。
所述收发模块310还可以设置为将所述升级结果发送到服务器侧。
本实施例的组件升级的装置，可以执行上述所示方法实施例的技术方案。
在实际应用中，所述收发模块310、读写模块320、控制模块330、加载模块340、安全模块350均可由位于组件升级的装置中的中央处理器(Central Processing Unit，CPU)、微处理器(Micro Processor Unit，MPU)、数字信号处理器(Digital Signal Processor，DSP)或现场可编程门阵列(Field Programmable Gate Array，FPGA)等实现。
图4为组件升级的终端实施例的结构示意图，如图4所示，本实施例提供的组件升级的终端04包括：接口410，总线420，存储器430与处理器440，所述接口410、存储器430与处理器440通过所述总线420相连接，所述存储器430设置为存储指令，所述处理器440读取该指令以执行如下操作。
获取组件升级文件；将所述组件升级文件存储到包含有组件未升级文件的特定分区中；在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件；当操作系统重启后，在所述特定分区中加载所 述第二组件。
可选地，所述处理器440读取该指令还可以在所述特定分区中提取出所述组件升级文件中的第二组件、及所述组件未升级文件中的第一组件，将所述第一组件替换成所述第二组件。
可选地，所述处理器440读取该指令还可以对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件。在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件。
可选地，所述处理器440读取该指令还可以判断从所述服务器侧获取的所述组件升级文件的信息摘要算法第五版MD5值与所述组件升级文件携带的MD5值是否一致。当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值一致，则确定所述组件升级文件为安全和完整的组件升级文件。当若从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值不一致，则确定所述组件升级文件为不安全和不完整的组件升级文件。
可选地，所述处理器440读取该指令还可以确定所述组件的升级结果，将所述升级结果发送到服务器侧。
本实施例的组件升级的终端，可以执行上述所示方法实施例的技术方案。
本实施例还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任意一种组件升级的方法。
本公开可提供为方法、系统、或计算机程序产品。本实施例可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本实施例的技术方案是根据本实施例的方法、设备(系统)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方 框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
工业实用性
本公开一种组件升级的方法和装置，可以实现组件的独立升级，无需随着操作系统更新升级时连带升级，可以提高组件升级的灵活性，降低升级操作系统失败的风险。

Claims (11)

  1. 一种组件升级的方法，包括：
    获取组件升级文件；
    将所述组件升级文件存储到包含有组件未升级文件的特定分区中；
    在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件；以及
    当操作系统重启后，在所述特定分区中加载所述第二组件。
  2. 根据权利要求1所述的方法，其中，所述在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件，包括：
    在所述特定分区中提取出所述组件升级文件中的第二组件、及所述组件未升级文件中的第一组件，将所述第一组件替换成所述第二组件。
  3. 根据权利要求1所述的方法，在所述将所述组件升级文件存储到包含有组件未升级文件的特定分区中之后，在所述将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件之前，还包括：
    对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件；
    当所述组件升级文件为安全和完整的组件升级文件时，所述在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件，包括：
    在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件。
  4. 根据权利要求3所述的方法，其中，所述对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件，包括：
    判断从所述服务器侧获取的所述组件升级文件的信息摘要算法第五版MD5值与所述组件升级文件携带的MD5值是否一致，当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值一致，则确定所述组件升级文件为安全和完整的组件升级文件；
    当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值不一致，则确定所述组件升级文件为不安全和不完整的组件升级文件。
  5. 根据权利要求1所述的方法，在在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件之后，还包括：
    确定所述组件的升级结果，将所述升级结果发送到服务器侧。
  6. 一种组件升级的装置，包括：
    收发模块，设置为获取组件升级文件；
    读写模块，设置为将所述组件升级文件存储到包含有所述组件未升级文件的特定分区中；
    控制模块，设置为在所述特定分区中将所述组件未升级文件中的第一组件替换成所述组件升级文件中的第二组件；以及
    加载模块，设置为当操作系统重启后，在所述特定分区中加载所述第二组件。
  7. 根据权利要求6所述的装置，其中，所述控制模块还设置为在所述特定分区中控制所述读写模块提取出所述组件升级文件中的第二组件、及所述组件未升级文件中的第一组件，所述控制模块，还设置为将所述第一组件替换成所述第二组件。
  8. 根据权利要求6所述的装置，还包括：
    安全模块，设置为对所述组件升级文件的安全性和完整性进行校验，确定所述组件升级文件是否为安全和完整的组件升级文件；
    所述控制模块，还设置为在所述特定分区中将所述组件未升级文件中的第一组件替换成所述安全和完整的组件升级文件中的第二组件。
  9. 根据权利要求6所述的装置，其中，所述安全模块还设置为判断从所述服务器侧获取的所述组件升级文件的信息摘要算法第五版MD5值与所述组件升级文件携带的MD5值是否一致，当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值一致，则确定所述组件升级文件为安全 和完整的组件升级文件；
    当从所述服务器侧获取的所述组件升级文件的MD5值与所述组件升级文件携带的MD5值不一致，则确定所述组件升级文件为不安全和不完整的组件升级文件。
  10. 根据权利要求6所述的装置，其中，所述控制模块还设置为确定所述组件的升级结果；
    所述收发模块还设置为将所述升级结果发送到服务器侧。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-5任一项所述的组件升级的方法。
PCT/CN2017/076543 2016-08-17 2017-03-14 组件升级的方法及装置 WO2018032757A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610683126.2A CN107766064A (zh) 2016-08-17 2016-08-17 组件升级的方法及装置
CN201610683126.2 2016-08-17

Publications (1)

Publication Number Publication Date
WO2018032757A1 true WO2018032757A1 (zh) 2018-02-22

Family

ID=61196308

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/076543 WO2018032757A1 (zh) 2016-08-17 2017-03-14 组件升级的方法及装置

Country Status (2)

Country Link
CN (1) CN107766064A (zh)
WO (1) WO2018032757A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110007935A (zh) * 2019-03-29 2019-07-12 阿里巴巴集团控股有限公司 一种程序升级的处理方法、装置及设备
CN112055353A (zh) * 2020-09-10 2020-12-08 中煤科工集团重庆研究院有限公司 煤矿人员定位标识卡无线升级系统和方法
CN113641390A (zh) * 2021-10-18 2021-11-12 苏州万店掌软件技术有限公司 一种系统升级方法、装置、设备及存储介质
EP4231142A4 (en) * 2021-07-30 2024-05-29 Honor Device Co Ltd METHOD FOR CONFIGURING OPERATING SYSTEM FORMAT, AND DEVICE AND STORAGE MEDIUM

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109189462A (zh) * 2018-08-07 2019-01-11 南京点触智能科技有限公司 一种具有自动升级功能的触控系统
CN109189451A (zh) * 2018-10-25 2019-01-11 京信通信系统（中国）有限公司 一种固件升级方法及装置
CN113050962B (zh) * 2019-12-27 2024-04-26 华为技术有限公司 移动服务升级方法、装置和终端
CN111787378B (zh) * 2020-06-28 2022-06-28 海信视像科技股份有限公司 应用于遥控装置的软件升级方法及遥控装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102799452A (zh) * 2012-06-29 2012-11-28 深圳市安普尔科技有限公司 系统软件升级方法和装置
CN102929675A (zh) * 2011-11-03 2013-02-13 微软公司 具有安全检查和预览的服务器升级
CN103207800A (zh) * 2013-04-24 2013-07-17 厦门亿联网络技术股份有限公司 一种安全灵活的固件升级方法
CN103517141A (zh) * 2013-10-11 2014-01-15 成都三零凯天通信实业有限公司 基于ip机顶盒分段式数据升级方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014165538A2 (en) * 2013-04-01 2014-10-09 Nebula, Inc. Update management for a distributed computing system
CN105786538B (zh) * 2014-12-24 2019-12-06 深圳市贰陆陆科技有限公司 基于安卓系统的软件升级方法和装置
CN104918114B (zh) * 2015-06-05 2018-05-18 青岛海信电器股份有限公司 一种操作系统升级方法及装置
CN105094913B (zh) * 2015-07-31 2018-06-15 广东欧珀移动通信有限公司 系统、基带固件和系统应用升级方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102929675A (zh) * 2011-11-03 2013-02-13 微软公司 具有安全检查和预览的服务器升级
CN102799452A (zh) * 2012-06-29 2012-11-28 深圳市安普尔科技有限公司 系统软件升级方法和装置
CN103207800A (zh) * 2013-04-24 2013-07-17 厦门亿联网络技术股份有限公司 一种安全灵活的固件升级方法
CN103517141A (zh) * 2013-10-11 2014-01-15 成都三零凯天通信实业有限公司 基于ip机顶盒分段式数据升级方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110007935A (zh) * 2019-03-29 2019-07-12 阿里巴巴集团控股有限公司 一种程序升级的处理方法、装置及设备
CN110007935B (zh) * 2019-03-29 2022-09-16 创新先进技术有限公司 一种程序升级的处理方法、装置及设备
CN112055353A (zh) * 2020-09-10 2020-12-08 中煤科工集团重庆研究院有限公司 煤矿人员定位标识卡无线升级系统和方法
EP4231142A4 (en) * 2021-07-30 2024-05-29 Honor Device Co Ltd METHOD FOR CONFIGURING OPERATING SYSTEM FORMAT, AND DEVICE AND STORAGE MEDIUM
CN113641390A (zh) * 2021-10-18 2021-11-12 苏州万店掌软件技术有限公司 一种系统升级方法、装置、设备及存储介质
CN113641390B (zh) * 2021-10-18 2022-03-22 苏州万店掌网络科技有限公司 一种系统升级方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN107766064A (zh) 2018-03-06

Similar Documents

Publication Publication Date Title
WO2018032757A1 (zh) 组件升级的方法及装置
WO2017166446A1 (zh) 漏洞修复方法和装置
KR102358470B1 (ko) 부트 로더 업데이트 펌웨어, 및 부트 로더 업데이트 방법
US10120672B2 (en) Method for offline updating virtual machine images
US9983790B2 (en) System management controller and method of configuration file backup and recovery
JP5838527B2 (ja) ファームウェアを更新するための方法、装置、および通信デバイス
CN106325929B (zh) 一种固件升级方法、固件升级装置、冰箱和服务端
TWI533216B (zh) 作業系統更新方法
WO2015192608A1 (zh) 安卓系统中app的更新方法、终端及存储介质
CN104052818A (zh) 一种移动终端的版本升级方法及装置
CN107291481B (zh) 一种组件更新方法、装置和系统
US9519786B1 (en) Firmware integrity ensurance and update
CN110543318A (zh) 控制设备程序更新方法、装置、存储介质及控制设备
CN104216719A (zh) 一种android系统的升级方法和装置
CN104395879A (zh) 在运行具有握手的客户端界面时的自动更新
CN105704296B (zh) 一种应用环境克隆方法及装置
TW201704994A (zh) 更新伺服器映像檔的技術
CN103019755A (zh) 嵌入式系统中多cpu的无线程序下载方法
CN112882734A (zh) 升级方法及装置、计算机设备和介质
CN115202686A (zh) 虚拟化系统的升级方法、装置、电子设备及存储介质
WO2018049798A1 (zh) 一种缓存分区重构的方法和装置
CN106293790B (zh) 基于Firefox操作系统的应用程序升级方法和装置
WO2017173924A1 (zh) 切换文件系统的方法及装置
CN104298618A (zh) 一种智能终端的命令处理方法及装置
KR20190021773A (ko) 전자 장치 및 그의 데이터 운용 방법

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: 17840734

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17840734

Country of ref document: EP

Kind code of ref document: A1