WO2023221002A1 - 基于ota的系统更新方法、装置、电子设备及存储介质 - Google Patents

基于ota的系统更新方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2023221002A1
WO2023221002A1 PCT/CN2022/093696 CN2022093696W WO2023221002A1 WO 2023221002 A1 WO2023221002 A1 WO 2023221002A1 CN 2022093696 W CN2022093696 W CN 2022093696W WO 2023221002 A1 WO2023221002 A1 WO 2023221002A1
Authority
WO
WIPO (PCT)
Prior art keywords
storage partition
update
target storage
partition
dependency relationship
Prior art date
Application number
PCT/CN2022/093696
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 北京小米移动软件有限公司
Priority to CN202280004209.8A priority Critical patent/CN117441159A/zh
Priority to PCT/CN2022/093696 priority patent/WO2023221002A1/zh
Publication of WO2023221002A1 publication Critical patent/WO2023221002A1/zh

Links

Images

Classifications

    • 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

Definitions

  • the present disclosure relates to the technical field of the Internet of Things, and in particular to a system update method, device, electronic device and storage medium based on over-the-air download technology OTA.
  • the present disclosure provides an OTA-based system update method, device, electronic device, and storage medium.
  • the present disclosure provides an OTA-based system update method, including:
  • the storage partitions are divided according to the dependencies of the storage partitions in the system.
  • each partition does not have to be updated in one restart process, but can be divided into multiple independent updates, which reduces the number of user errors due to system updates. Unusable storage space to improve user experience.
  • an OTA-based system update device including:
  • the first acquisition module is used to obtain an OTA update request.
  • the OTA update request includes partial update data of the configuration file;
  • the second acquisition module is used to obtain the dependencies between storage partitions in the system, where the system configuration files are stored in the storage partitions;
  • the independent update module is used to determine the target storage partition requested for update based on dependencies and update data, and independently update the target storage partition.
  • the present disclosure provides an electronic device, including a memory and a processor
  • the processor reads the executable program code stored in the memory to run a program corresponding to the executable program code, so as to implement the OTA-based system update method according to the embodiment of the first aspect of the present disclosure.
  • the present disclosure provides a computer-readable storage medium on which a computer program is stored.
  • the program is executed by a processor, the OTA-based system update method of the embodiment of the first aspect of the present disclosure is implemented.
  • the present disclosure provides a computer program product, including a computer program.
  • the computer program When executed by a processor, the computer program implements the OTA-based system update method of the embodiment of the first aspect of the present disclosure.
  • Figure 1 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure
  • Figure 2 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure
  • Figure 3 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure
  • Figure 4 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure
  • Figure 5 is a structural diagram of an OTA-based system update device according to an embodiment of the present disclosure.
  • FIG. 6 is a block diagram of an electronic device used to implement an OTA-based system update method according to an embodiment of the present disclosure.
  • OTA is a data value-added service based on the short message mechanism that enables dynamic downloading, deletion and updating of the business menu in the SIM card through mobile phone terminals or servers, allowing users to obtain personalized information services. It is a data value-added service that uses the air interface of mobile communications to Technology for remote management of card data and applications.
  • the application of OTA technology enables mobile communications to not only provide voice and data services, but also provide new business downloads. In this way, application and content service providers can continue to develop more personalized services close to user needs without being limited by the platform, such as information on demand, interactive entertainment, location services, and bank transactions.
  • OTA over-the-air download technology mobile phone users can download various service menus provided by the network to their mobile phones according to their personal preferences using the OTA mechanism with simple operations, and can also customize specific services according to their own wishes.
  • OTA technology is used for system update.
  • each partition of the system needs to be updated during a restart process.
  • the user must wait during the OTA process and cannot continue to use it, resulting in a poor user experience.
  • This disclosure proposes an OTA-based system update method, which can divide the system update process into multiple independent updates, bringing a good user experience.
  • Figure 1 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure. As shown in Figure 1, the method includes the following steps:
  • the OTA update request includes partial update data of the configuration file.
  • the terminal device sends a system update request to the network device.
  • the network device After receiving the system update request sent by the terminal device, the network device sends an OTA update request to the terminal device, where the OTA update request includes partial update data of the configuration file.
  • the configuration file includes data required for system operation, such as instructions that need to be executed by the processor, etc.
  • the configuration file needs to be updated.
  • the entire system update process can be divided into multiple independent updates, so the OTA update request can only include partial update data of the configuration file.
  • the terminal device can obtain multiple OTA update requests during the system update process, and each OTA update request includes a part of the update data of the configuration file.
  • the update data includes identification information used to indicate which configuration file the update data is.
  • part of the update data in any OTA update request can be used as update data for an independent update.
  • partial update data in multiple OTA update requests can be combined as update data for an independent update.
  • Dependencies between buckets can indicate the logical dependencies of content in a configuration file. For example, if there is a dependency relationship between storage partition 1 and storage partition 2, the execution of a certain instruction may require the contents of the configuration file in storage partition 1 and the contents of the configuration file in storage partition 2 at the same time.
  • the system includes multiple storage partitions, and each storage partition includes one or more configuration files. Based on the contents of the configuration files, the dependencies between storage partitions can be obtained.
  • the system can also obtain the dependencies between storage partitions synchronously when obtaining the configuration file, and store the dependencies in the specified storage location.
  • the dependencies between storage partitions can be obtained from the specified storage location of the system. relation.
  • S103 Determine the target storage partition requested for update based on the dependency relationship and update data, and independently update the target storage partition.
  • configuration files that have logical dependencies on multiple storage partitions need to be updated synchronously.
  • the configuration files that need to be updated can be determined; based on the dependencies, the configuration files that need to be updated synchronously can be determined.
  • the target bucket for the requested update can be determined and independently updated on the target bucket.
  • the content in the target storage partition must be logically self-consistent. For example, if there is a dependency relationship between storage partition 1 and storage partition 2, in a single update, neither storage partition can be updated independently. Therefore, on the basis of the storage partition determined based on the updated data, it is also necessary to obtain the corresponding configuration files in the storage partitions that are dependent on the storage partition, and together form the target storage partition, and independently update the target storage partition.
  • one update is divided into multiple independent updates. After one independent update is completed, the system can obtain the OTA update request again, repeatedly determine the target storage partition for the requested update, and perform operations on the target storage partition. Independent updates and other operations until the system update is completed.
  • an OTA update request is obtained.
  • the OTA update request includes part of the update data of the configuration file, and the dependency relationship between the storage partitions in the system is obtained.
  • the configuration file of the system is stored in the storage partition. According to the dependency relationship and the update data , determine the target storage partition for which the update is requested, and perform independent updates to the target storage partition.
  • the storage partitions are divided according to the dependencies of the storage partitions in the system. When the system is updated, each partition does not have to be updated in one restart process, but can be divided into multiple independent updates, which reduces the number of user errors due to system updates. Unusable storage space to improve user experience.
  • Figure 2 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure. As shown in Figure 2, the dependency acquisition process also includes the following steps:
  • the configuration file stored in each storage partition where the configuration file includes data required for system operation, such as instructions that need to be executed by the processor, etc., and read the contents of the configuration file.
  • the logical dependencies between the contents can be obtained based on the contents in the configuration file. For example, when the processor executes a certain instruction, a piece of logic is required. The logic includes three parts: A, B, and C. Then A, B, and C in the configuration file The content has logical dependencies. By analogy, all content in the configuration file that has logical dependencies can be obtained, and the remaining content is content that does not have logical dependencies.
  • the storage partition can be determined There is a dependency relationship between 1 and storage partition 2, and by analogy, all storage partitions with dependencies in the system can be obtained, and the remaining storage partitions are storage partitions without dependencies.
  • any second storage partition may have a dependency relationship with one storage partition or multiple storage partitions.
  • the system classifies and stores the content in the configuration file, and stores all the logic required for application management instructions in application instruction file 1, application instruction file 2, application instruction file 3 and other files.
  • the content in the configuration file stored in each storage partition is obtained, and the dependency relationship between the storage partitions is obtained according to the logical dependency relationship between the contents.
  • the method in the embodiment of the present disclosure obtains the dependency relationship between storage partitions based on the content in the configuration file, so that the system can be independently updated based on the dependency relationship in subsequent steps, so that the content in a single update satisfies logical self-consistency.
  • Figure 3 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure. As shown in Figure 3, the target storage partition requested for update is determined based on dependencies and update data, and the target storage partition is independently updated. Also includes the following steps:
  • S301 Determine the target storage partition from the storage partitions of the system according to the updated data.
  • the update data includes identification information used to indicate which configuration file the update data is.
  • the target storage partition can be determined from the storage partitions of the system, where the configuration file indicated by the identification information is the configuration file in the target storage partition, and the update data at this time is the update data of the configuration file in the target storage partition.
  • S302 Determine the target storage partition as the first storage partition according to the dependency relationship, and then directly update the target storage partition based on the update data.
  • the configuration file in the target storage partition has no logical dependency relationship with the configuration files in the other storage partitions, and can be directly compared based on the updated data.
  • the target bucket is updated.
  • configuration files in the target storage partition have logical dependencies with configuration files in other storage partitions.
  • configuration files with logical dependencies need to be updated synchronously.
  • the logic includes three parts: A, B, and C. That is, content A, B, and C have logical dependencies.
  • the configuration file to which content A belongs is stored in storage partition 1.
  • the configuration files to which content B and C belong are stored in storage partition 2. If storage partition 1 is updated separately, content A will change at this time.
  • the instruction is executed again, the updated A does not match the unupdated B and C, and an error occurs in the instruction. Therefore, configuration files that have logical dependencies on multiple storage partitions need to be updated simultaneously.
  • logical dependencies can be identified, configuration files corresponding to the logical dependencies can be backed up, and configuration files with logical dependencies can be updated synchronously.
  • the content stored on the target bucket is backed up and the target bucket is updated based on the updated data.
  • obtaining a configuration file that is logically dependent on the configuration file in the target storage partition, and the response to the updated data includes updated data of the configuration file in the target storage partition, and updated data of the configuration file that is logically dependent on it.
  • the target storage partition is determined from the storage partitions of the system according to the update data, and the target storage partition is determined to be the first storage partition according to the dependency relationship. Then the target storage partition is directly updated based on the update data, and the target storage partition is determined according to the dependency relationship. If the target storage partition is the second storage partition, the content stored in the target storage partition is backed up, and the target storage partition is updated based on the updated data.
  • the method of the embodiment of the present disclosure can ensure that configuration files with logical dependencies can be updated synchronously to avoid system operation errors.
  • FIG. 4 is a flow chart of an OTA-based system update method according to an embodiment of the present disclosure. As shown in Figure 4, independently updating the target storage partition also includes the following steps:
  • update abnormalities or failures may occur, such as a power outage on the terminal device.
  • the target storage partition during the update needs to be restored to avoid that part of the configuration file content in the target storage area is updated, and part of the configuration file is not updated. It has not been updated, causing errors when the system is running.
  • the content stored in the target storage partition is backed up, and in response to an exception or failure in updating the target storage partition, the update is stopped and the target storage partition is restored based on the backup.
  • the content stored in the target storage partition is rolled back.
  • a failure protection mechanism is started for the target storage partition.
  • the method of the embodiment of the present disclosure can restore the original storage content of the target storage area when the update is abnormal or fails, thereby avoiding errors during system operation.
  • FIG. 5 is a structural diagram of an OTA-based system update device according to an embodiment of the present disclosure. As shown in Figure 5, the OTA-based system update device 500 includes:
  • the first acquisition module 510 is used to acquire an OTA update request, where the OTA update request includes partial update data of the configuration file;
  • the second acquisition module 520 is used to acquire dependencies between storage partitions in the system, where the system configuration files are stored in the storage partitions;
  • the independent update module 530 is used to determine the target storage partition requested for update based on dependencies and update data, and perform independent updates to the target storage partition.
  • the storage partitions are divided according to the dependencies of the storage partitions in the system.
  • each partition does not have to be updated in one restart process, but can be divided into multiple independent updates, which reduces the number of user errors due to system updates. Unusable storage space to improve user experience.
  • the second acquisition module 520 is also configured to: acquire dependency relationships from a designated storage location of the system.
  • the second acquisition module 520 is also used to: acquire the content in the configuration file stored in each storage partition; obtain the content according to the logical dependency relationship between the content. Dependencies between buckets.
  • the second acquisition module 520 is also used to: determine the storage partition where the file content without logical dependence is located as having no dependence on any storage partition. The first storage partition of the relationship; determine the storage partition with a logical dependency relationship as the second storage partition.
  • the independent update module 530 is also used to: determine the target storage partition from the storage partitions of the system according to the update data; determine the target storage partition as the first storage partition according to the dependency relationship. storage partition, directly update the target storage partition based on the update data; determine the target storage partition as the second storage partition based on the dependency relationship, back up the content stored in the target storage partition, and update the target storage partition based on the update data .
  • the independent update module 530 is also configured to repeatedly determine the target storage partition requested for update, and perform independent updates on the target storage partition until the system update is completed. .
  • the independent update module 530 is also used to: back up the content stored in the target storage partition, and in response to an abnormality or failure in the target storage partition update, stop the update and perform the update based on The backup restores the target storage partition.
  • the independent update module 530 is also configured to roll back the content stored in the target storage partition in response to an exception or failure in updating the target storage partition.
  • the present disclosure also provides an electronic device, a readable storage medium, and a computer program product.
  • FIG. 6 illustrates a schematic block diagram of an example electronic device 60 that may be used to implement embodiments of the present disclosure.
  • Electronic devices are intended to refer to various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers.
  • Electronic devices may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices.
  • the components shown herein, their connections and relationships, and their functions are examples only and are not intended to limit implementations of the disclosure described and/or claimed herein.
  • FIG. 6 it includes a memory 61, a processor 62, and a computer program stored in the memory 61 and executable on the processor 62.
  • the processor 62 executes the program, the aforementioned OTA-based system update method is implemented.
  • a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing.
  • machine-readable storage media would include one or more wire-based electrical connections, laptop disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • RAM random access memory
  • ROM read only memory
  • EPROM or flash memory erasable programmable read only memory
  • CD-ROM portable compact disk read-only memory
  • magnetic storage device or any suitable combination of the above.
  • the systems and techniques described herein may be implemented on a computer having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user ); and a keyboard and pointing device (eg, a mouse or a trackball) through which a user can provide input to the computer.
  • a display device eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • a keyboard and pointing device eg, a mouse or a trackball
  • Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and may be provided in any form, including Acoustic input, voice input or tactile input) to receive input from the user.
  • the systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., A user's computer having a graphical user interface or web browser through which the user can interact with implementations of the systems and technologies described herein), or including such backend components, middleware components, or any combination of front-end components in a computing system.
  • the components of the system may be interconnected by any form or medium of digital data communication (eg, a communications network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.
  • Computer systems may include clients and servers.
  • Clients and servers are generally remote from each other and typically interact over a communications network.
  • the relationship of client and server is created by computer programs running on corresponding computers and having a client-server relationship with each other.
  • the server can be a cloud server, a distributed system server, or a server combined with a blockchain.
  • first and second are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as “first” and “second” may explicitly or implicitly include one or more of these features.
  • “plurality” means two or more than two, unless otherwise explicitly and specifically limited.
  • references to the terms “one embodiment,” “some embodiments,” “an example,” “specific examples,” or “some examples” or the like means that specific features are described in connection with the embodiment or example. , structures, materials or features are included in at least one embodiment or example of the invention. In this specification, the schematic expressions of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and combine different embodiments or examples and features of different embodiments or examples described in this specification unless they are inconsistent with each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本公开提出了一种基于空中下载技术OTA的系统更新方法、装置、电子设备及存储介质，涉及物联网技术领域。该方法包括：获取OTA更新请求，OTA更新请求包括配置文件的部分更新数据；获取系统内存储分区之间的依赖关系，其中系统的配置文件存储于存储分区中；根据依赖关系和更新数据，确定请求更新的目标存储分区，并对目标存储分区进行独立更新。本公开中根据系统内存储分区的依赖关系对存储分区进行划分，在系统更新时，每个分区不必在一次重启过程中更新，而可以分成多次独立更新，减少了因系统更新导致用户不能使用的存储空间，提升用户体验。

Description

基于OTA的系统更新方法、装置、电子设备及存储介质 技术领域
本公开涉及物联网技术领域，尤其涉及一种基于空中下载技术OTA的系统更新方法、装置、电子设备及存储介质。
背景技术
相关技术中，为了让空中下载技术(Over-the-Air Technology，OTA)升级过程中用户无感知，需要占用和当前分区相同大小的存储空间用于系统OTA升级，导致这部分存储空间用户不能再使用，造成空间浪费。对于存储空间有限的终端设备，就必需在OTA过程中让用户等待，不能继续使用，造成不良的用户体验。
发明内容
本公开提供了一种基于OTA的系统更新方法、装置、电子设备及存储介质。
第一方面，本公开提供了一种基于OTA的系统更新方法，包括：
获取OTA更新请求，OTA更新请求包括配置文件的部分更新数据；
获取系统内存储分区之间的依赖关系，其中系统的配置文件存储于存储分区中；
根据依赖关系和更新数据，确定请求更新的目标存储分区，并对目标存储分区进行独立更新。
本公开实施例中根据系统内存储分区的依赖关系对存储分区进行划分，在系统更新时，每个分区不必在一次重启过程中更新，而可以分成多次独立更新，减少了因系统更新导致用户不能使用的存储空间，提升用户体验。
第二方面，本公开提供了一种基于OTA的系统更新装置，包括：
第一获取模块，用于获取OTA更新请求，OTA更新请求包括配置文件的部分更新数据；
第二获取模块，用于获取系统内存储分区之间的依赖关系，其中系统的配置文件存储于存储分区中；
独立更新模块，用于根据依赖关系和更新数据，确定请求更新的目标存储分区，并对目标存储分区进行独立更新。
第三方面，本公开提供了一种电子设备，包括存储器、处理器；
其中，处理器通过读取存储器中存储的可执行程序代码来运行与可执行程序代码对应的程序，以用于实现本公开第一方面实施例的基于OTA的系统更新方法。
第四方面，本公开提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现本公开第一方面实施例的基于OTA的系统更新方法。
第五方面，本公开提供了一种计算机程序产品，包括计算机程序，计算机程序在被处理器执行时实现本公开第一方面实施例的基于OTA的系统更新方法。
应当理解，本部分所描述的内容并非旨在标识本公开的实施例的关键或重要特征，也不用于限制本公开的范围。本公开的其它特征将通过以下的说明书而变得容易理解。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所 需要使用的附图进行说明。
图1是根据本公开一个实施例的基于OTA的系统更新方法的流程图；
图2是根据本公开一个实施例的基于OTA的系统更新方法的流程图；
图3是根据本公开一个实施例的基于OTA的系统更新方法的流程图；
图4是根据本公开一个实施例的基于OTA的系统更新方法的流程图；
图5是根据本公开一个实施例的基于OTA的系统更新装置的结构图；
图6是用来实现本公开实施例的基于OTA的系统更新方法的电子设备的框图。
具体实施方式
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。
下面结合参考附图描述本公开的基于OTA的系统更新方法、装置、电子设备及存储介质。需要说明的是，下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
为了便于理解，首先介绍本申请涉及的术语。
OTA是一项基于短消息机制，通过手机终端或服务器方式实现SIM卡内业务菜单的动态下载、删除与更新，使用户获取个性化信息服务的数据增值业务，是通过移动通信的空中接口对SIM卡数据及应用进行远程管理的技术。OTA技术的应用，使得移动通信不仅可以提供语音和数据服务，而且还能提供新业务下载。这样，应用及内容服务商可以不受平台的局限，不断开发出更具个性化的贴近用户需求的服务，如信息点播、互动娱乐、位置服务以及银行交易等。通过OTA空中下载技术，手机用户只要进行简单操作，就可以按照个人喜好把网络所提供的各种业务菜单利用OTA机制下载到手机中，并且还可以根据自己的意愿定制具体业务。
在系统更新中，用户没有权限访问系统的配置文件，只有系统自身才能有权限访问并对其进行操作，因此，本公开中使用OTA技术进行系统更新。相关技术中，需要在一次重启过程中对系统的每个分区进行更新，对于存储空间有限的设备上，就必需在OTA过程中让用户等待，不能继续使用，造成不良用户体验。本公开中提出一种基于OTA的系统更新方法，可以将系统更新的过程分成多次独立更新，带来良好的用户体验。
图1是根据本公开一个实施例的基于OTA的系统更新方法的流程图，如图1所示，该方法包括以下步骤：
S101，获取OTA更新请求，OTA更新请求包括配置文件的部分更新数据。
可选地，终端设备向网络设备发送系统更新请求，在接收到终端设备发送的系统更新请求之后，网络设备向终端设备发送OTA更新请求，其中，OTA更新请求包括配置文件的部分更新数据。
配置文件中包括系统运行所需要的数据，如需要处理器执行的指令等等，在系统更新时，需要对配置文件进行更新。本公开实施例中可以将整个系统更新过程分成多次独立更新，因此OTA更新请求中可以只包括配置文件的部分更新数据。
作为一种可能的实现方式，终端设备可以在系统更新的过程中获取多个OTA更新请求，每个OTA 更新请求包括配置文件的一部分更新数据。可选地，更新数据中包括标识信息，用于指示该更新数据为哪一配置文件的更新数据。
可选地，任一OTA更新请求中的部分更新数据可以作为一次独立更新的更新数据。可选地，多个OTA更新请求中的部分更新数据可以组合作为一次独立更新的更新数据。
S102，获取系统内存储分区之间的依赖关系，其中系统的配置文件存储于存储分区中。
存储分区之间的依赖关系可以指示配置文件中内容的逻辑依赖关系。例如，若存储分区1和存储分区2之间存在依赖关系，则某一指令的执行可能同时需要存储分区1中配置文件的内容和存储分区2中配置文件的内容。
系统中包括多个存储分区，每个存储分区中包括一个或多个配置文件，基于配置文件中的内容，可以获取存储分区之间的依赖关系。
可选地，系统还可以在获取配置文件时同步获取存储分区之间的依赖关系，并将依赖关系存储在指定存储位置中，此时可以从系统的指定存储位置，获取存储分区之间的依赖关系。
S103，根据依赖关系和更新数据，确定请求更新的目标存储分区，并对目标存储分区进行独立更新。
本公开实施例中，需要对多个存储分区上存在逻辑依赖关系的配置文件同步更新。根据更新数据，可以确定需要更新的配置文件；根据依赖关系，可以确定需要同步更新的配置文件。根据依赖关系和更新数据，可以确定请求更新的目标存储分区，并对目标存储分区进行独立更新。
在对目标存储分区进行独立更新时，目标存储分区中的内容需满足逻辑自洽。例如，若存储分区1和存储分区2存在依赖关系，则在单次更新中，不能针对其中任一存储分区进行单独更新。因此，在基于更新数据确定的存储分区的基础上，还需要获取与该存储分区存在依赖关系的存储分区中的相应配置文件，共同组成目标存储分区，并对目标存储分区进行独立更新。
需要说明的是，本公开实施例中将一次更新分成多次独立更新，在一次独立更新完成后，系统可以再次获取OTA更新请求，重复执行确定请求更新的目标存储分区，并对目标存储分区进行独立更新等操作，直至系统更新完毕。
本公开实施例中，获取OTA更新请求，OTA更新请求包括配置文件的部分更新数据，获取系统内存储分区之间的依赖关系，其中系统的配置文件存储于存储分区中，根据依赖关系和更新数据，确定请求更新的目标存储分区，并对目标存储分区进行独立更新。本公开实施例中根据系统内存储分区的依赖关系对存储分区进行划分，在系统更新时，每个分区不必在一次重启过程中更新，而可以分成多次独立更新，减少了因系统更新导致用户不能使用的存储空间，提升用户体验。
图2是根据本公开一个实施例的基于OTA的系统更新方法的流程图，如图2所示，依赖关系的获取过程，还包括以下步骤：
S201，获取每个存储分区所存储的配置文件中的内容。
获取每个存储分区所存储的配置文件，其中，配置文件中包括系统运行所需要的数据，如需要处理器执行的指令等等，并读取配置文件中的内容。
S202，根据内容之间的逻辑依赖关系，获取存储分区之间的依赖关系。
根据配置文件中的内容可以获取内容之间的逻辑依赖关系，例如，处理器执行某指令时需要一段逻辑，逻辑中包括A、B、C三个部分，则配置文件中的A、B、C内容存在逻辑依赖关系。以此类推， 可以获取配置文件中所有存在逻辑依赖关系的内容，则其余内容为不存在逻辑依赖关系的内容。
相应地，若内容A、B、C存在逻辑依赖关系，但内容A所属的配置文件存储于存储分区1中，而内容B、C所属的配置文件存储于存储分区2中，则可以判定存储分区1和存储分区2存在依赖关系，以此类推，可以获取系统中所有存在依赖关系的存储分区，则其余存储分区为不存在依赖关系的存储分区。
可选地，将未存在逻辑依赖关系的文件内容所在的存储分区，确定为与任一存储分区未存在依赖关系的第一存储分区，将存在逻辑依赖关系的存储分区，确定为第二存储分区。需要说明的是，任一第二存储分区可以与一个存储分区存在依赖关系，也可以与多个存储分区存在依赖关系。
可选地，还可以根据配置文件的文件名称，获取存储分区之间的依赖关系。例如，系统对配置文件中的内容进行分类存储，对于应用管理指令所需要的所有逻辑，将其固定存储于应用指令文件1、应用指令文件2、应用指令文件3等文件中。获取存储分区中各配置文件的文件名称，可以根据文件名称获取配置文件之间的逻辑依赖关系，进而将未存在逻辑依赖关系的配置文件所在的存储分区，确定为与任一存储分区未存在依赖关系的第一存储分区，将存在逻辑依赖关系的存储分区，确定为第二存储分区。
本公开实施例中，获取每个存储分区所存储的配置文件中的内容，根据内容之间的逻辑依赖关系，获取存储分区之间的依赖关系。本公开实施例的方法基于配置文件中的内容获取存储分区之间的依赖关系，以使后续步骤中可以根据依赖关系对系统进行独立更新，使单次更新中的内容满足逻辑自洽。
图3是根据本公开一个实施例的基于OTA的系统更新方法的流程图，如图3所示，根据依赖关系和更新数据，确定请求更新的目标存储分区，并对目标存储分区进行独立更新，还包括以下步骤：
S301，根据更新数据，从系统的存储分区中确定目标存储分区。
可选地，更新数据中包括标识信息，用于指示该更新数据为哪一配置文件的更新数据。基于标识信息，可以从系统的存储分区中确定目标存储分区，其中，标识信息指示的配置文件为目标存储分区中的配置文件，此时更新数据为目标存储分区中的配置文件的更新数据。
S302，根据依赖关系确定目标存储分区为第一存储分区，则基于更新数据直接对目标存储分区进行更新。
当确定目标存储分区为与任一存储分区未存在依赖关系的第一存储分区，则证明目标存储分区中的配置文件与其余存储分区中的配置文件不存在逻辑依赖关系，可以基于更新数据直接对目标存储分区进行更新。
S303，根据依赖关系确定目标存储分区为第二存储分区，则对目标存储分区上所存储内容进行备份，并基于更新数据对目标存储分区进行更新。
当确定目标存储分区为存在逻辑依赖关系的第二存储分区，则证明目标存储分区中的配置文件与其余存储分区中的配置文件存在逻辑依赖关系。需要说明的是，存在逻辑依赖关系的配置文件需要同步更新。举例说明，假设处理器执行某指令时需要一段逻辑，逻辑中包括A、B、C三个部分，即内容A、B、C存在逻辑依赖关系，内容A所属的配置文件存储于存储分区1中，而内容B、C所属的配置文件存储于存储分区2中。若对存储分区1单独进行更新，此时内容A会发生变化，当再次执行该指令时，更新后的A与未更新的B、C不匹配，则指令出现错误。因此，需要对多个存储分区上存在逻辑依赖关系的配置文件同步更新。
本实施例中可以识别逻辑依赖关系，备份逻辑依赖关系对应的配置文件，并将存在逻辑依赖关系的 配置文件同步更新。
在一些实现中，对目标存储分区上所存储内容进行备份，并基于更新数据对目标存储分区进行更新。
在另一些实现中，获取与目标存储分区中的配置文件存在逻辑依赖关系的配置文件，响应于更新数据包括目标存储分区中配置文件的更新数据，和与其存在逻辑依赖关系的配置文件的更新数据，对目标存储分区中的配置文件和存在逻辑依赖关系的配置文件进行同步更新。
本公开实施例中，根据更新数据，从系统的存储分区中确定目标存储分区，根据依赖关系确定目标存储分区为第一存储分区，则基于更新数据直接对目标存储分区进行更新，根据依赖关系确定目标存储分区为第二存储分区，则对目标存储分区上所存储内容进行备份，并基于更新数据对目标存储分区进行更新。本公开实施例的方法通过对目标存储分区进行分类识别，可以保证存在逻辑依赖关系的配置文件可以同步更新，避免系统运行出错。
图4是根据本公开一个实施例的基于OTA的系统更新方法的流程图，如图4所示，对目标存储分区进行独立更新，还包括以下步骤：
S401，响应于目标存储分区更新异常或失败，对目标存储分区启动失败保护机制。
在系统更新的过程中可能出现更新异常或失败的情况，例如终端设备发生断电，此时需要对更新中的目标存储分区进行恢复，避免目标存储区域中配置文件的内容一部分进行了更新，一部分还未更新，导致系统运行时发生错误。
在一些实现中，对目标存储分区所存储的内容进行备份，响应于目标存储分区更新异常或失败，停止更新并基于备份对目标存储分区进行恢复。
在另一些实现中，响应于目标存储分区更新异常或失败，对目标存储分区所存储的内容进行回滚。
本公开实施例中，响应于目标存储分区更新异常或失败，对目标存储分区启动失败保护机制。本公开实施例的方法可以在目标存储区域更新异常或失败时恢复其原本的存储内容，避免系统运行时发生错误。
图5是根据本公开一个实施例的基于OTA的系统更新装置的结构图，如图5所示，基于OTA的系统更新装置500包括：
第一获取模块510，用于获取OTA更新请求，OTA更新请求包括配置文件的部分更新数据；
第二获取模块520，用于获取系统内存储分区之间的依赖关系，其中系统的配置文件存储于存储分区中；
独立更新模块530，用于根据依赖关系和更新数据，确定请求更新的目标存储分区，并对目标存储分区进行独立更新。
本公开实施例中根据系统内存储分区的依赖关系对存储分区进行划分，在系统更新时，每个分区不必在一次重启过程中更新，而可以分成多次独立更新，减少了因系统更新导致用户不能使用的存储空间，提升用户体验。
需要说明的是，前述对基于OTA的系统更新方法实施例的解释说明也适用于该实施例的基于OTA的系统更新装置，此处不再赘述。
进一步地，在本公开实施例一种可能的实现方式中，第二获取模块520，还用于：从系统的指定存储位置，获取依赖关系。
进一步地，在本公开实施例一种可能的实现方式中，第二获取模块520，还用于：获取每个存储分 区所存储的配置文件中的内容；根据内容之间的逻辑依赖关系，获取存储分区之间的依赖关系。
进一步地，在本公开实施例一种可能的实现方式中，第二获取模块520，还用于：将未存在逻辑依赖关系的文件内容所在的存储分区，确定为与任一存储分区未存在依赖关系的第一存储分区；将存在逻辑依赖关系的存储分区确定为第二存储分区。
进一步地，在本公开实施例一种可能的实现方式中，独立更新模块530，还用于：根据更新数据，从系统的存储分区中确定目标存储分区；根据依赖关系确定目标存储分区为第一存储分区，则基于更新数据直接对目标存储分区进行更新；根据依赖关系确定目标存储分区为第二存储分区，则对目标存储分区上所存储内容进行备份，并基于更新数据对目标存储分区进行更新。
进一步地，在本公开实施例一种可能的实现方式中，独立更新模块530，还用于：重复执行确定请求更新的目标存储分区，并对目标存储分区进行独立更新等操作，直至系统更新完毕。
进一步地，在本公开实施例一种可能的实现方式中，独立更新模块530，还用于：对目标存储分区所存储的内容进行备份，响应于目标存储分区更新异常或失败，停止更新并基于所述备份对目标存储分区进行恢复。
进一步地，在本公开实施例一种可能的实现方式中，独立更新模块530，还用于：响应于目标存储分区更新异常或失败，对目标存储分区所存储的内容进行回滚。
根据本公开的实施例，本公开还提供了一种电子设备、一种可读存储介质和一种计算机程序产品。
图6示出了可以用来实施本公开的实施例的示例电子设备60的示意性框图。电子设备旨在表示各种形式的数字计算机，诸如，膝上型计算机、台式计算机、工作台、个人数字助理、服务器、刀片式服务器、大型计算机、和其它适合的计算机。电子设备还可以表示各种形式的移动装置，诸如，个人数字处理、蜂窝电话、智能电话、可穿戴设备和其它类似的计算装置。本文所示的部件、它们的连接和关系、以及它们的功能仅仅作为示例，并且不意在限制本文中描述的和/或者要求的本公开的实现。
如图6所示，包括存储器61、处理器62及存储在存储器61上并可在处理器62上运行的计算机程序，处理器62执行程序时，实现前述的基于OTA的系统更新方法。
在本公开的上下文中，机器可读介质可以是有形的介质，其可以包含或存储以供指令执行系统、装置或设备使用或与指令执行系统、装置或设备结合地使用的程序。机器可读介质可以是机器可读信号介质或机器可读储存介质。机器可读介质可以包括但不限于电子的、磁性的、光学的、电磁的、红外的、或半导体系统、装置或设备，或者上述内容的任何合适组合。机器可读存储介质的更具体示例会包括基于一个或多个线的电气连接、便携式计算机盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或快闪存储器)、光纤、便捷式紧凑盘只读存储器(CD-ROM)、光学储存设备、磁储存设备、或上述内容的任何合适组合。
为了提供与用户的交互，可以在计算机上实施此处描述的系统和技术，该计算机具有：用于向用户显示信息的显示装置(例如，CRT(阴极射线管)或者LCD(液晶显示器)监视器)；以及键盘和指向装置(例如，鼠标或者轨迹球)，用户可以通过该键盘和该指向装置来将输入提供给计算机。其它种类的装置还可以用于提供与用户的交互；例如，提供给用户的反馈可以是任何形式的传感反馈(例如，视觉反馈、听觉反馈、或者触觉反馈)；并且可以用任何形式(包括声输入、语音输入或者、触觉输入)来接收来自用户的输入。
可以将此处描述的系统和技术实施在包括后台部件的计算系统(例如，作为数据服务器)、或者包 括中间件部件的计算系统(例如，应用服务器)、或者包括前端部件的计算系统(例如，具有图形用户界面或者网络浏览器的用户计算机，用户可以通过该图形用户界面或者该网络浏览器来与此处描述的系统和技术的实施方式交互)、或者包括这种后台部件、中间件部件、或者前端部件的任何组合的计算系统中。可以通过任何形式或者介质的数字数据通信(例如，通信网络)来将系统的部件相互连接。通信网络的示例包括：局域网(LAN)、广域网(WAN)和互联网。
计算机系统可以包括客户端和服务器。客户端和服务器一般远离彼此并且通常通过通信网络进行交互。通过在相应的计算机上运行并且彼此具有客户端-服务器关系的计算机程序来产生客户端和服务器的关系。服务器可以是云服务器，也可以为分布式系统的服务器，或者是结合了区块链的服务器。
此外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本发明的描述中，“多个”的含义是两个或两个以上，除非另有明确具体的限定。
在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或者特点包含于本发明的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不必须针对的是相同的实施例或示例。而且，描述的具体特征、结构、材料或者特点可以在任一个或多个实施例或示例中以合适的方式结合。此外，在不相互矛盾的情况下，本领域的技术人员可以将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
尽管上面已经示出和描述了本发明的实施例，可以理解的是，上述实施例是示例性的，不能理解为对本发明的限制，本领域的普通技术人员在本发明的范围内可以对上述实施例进行变化、修改、替换和变型。

Claims (19)

  1. 一种基于空中下载技术OTA的系统更新方法，其特征在于，包括：
    获取OTA更新请求，所述OTA更新请求包括配置文件的部分更新数据；
    获取系统内存储分区之间的依赖关系，其中所述系统的配置文件存储于所述存储分区中；
    根据所述依赖关系和所述更新数据，确定请求更新的目标存储分区，并对所述目标存储分区进行独立更新。
  2. 根据权利要求1所述的方法，其特征在于，所述获取系统内存储分区之间的依赖关系，包括：
    从所述系统的指定存储位置，获取所述依赖关系。
  3. 根据权利要求1或2所述的方法，其特征在于，所述依赖关系的获取过程，包括：
    获取每个所述存储分区所存储的所述配置文件中的内容；
    根据所述内容之间的逻辑依赖关系，获取所述存储分区之间的依赖关系。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述内容之间的逻辑依赖关系，获取所述存储分区之间的依赖关系，包括：
    将未存在逻辑依赖关系的所述内容所在的存储分区，确定为与任一存储分区未存在依赖关系的第一存储分区；
    将存在逻辑依赖关系的存储分区确定为第二存储分区。
  5. 根据权利要求4所述的方法，其特征在于，所述根据所述依赖关系和所述更新数据，确定请求更新的目标存储分区，并对所述目标存储分区进行独立更新，包括：
    根据所述更新数据，从所述系统的存储分区中确定所述目标存储分区；
    根据所述依赖关系确定所述目标存储分区为所述第一存储分区，则基于所述更新数据直接对所述目标存储分区进行更新；
    根据所述依赖关系确定所述目标存储分区为所述第二存储分区，则对所述目标存储分区上所存储内容进行备份，并基于所述更新数据对所述目标存储分区进行更新。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    重复执行确定请求更新的目标存储分区，并对所述目标存储分区进行独立更新等操作，直至所述系统更新完毕。
  7. 根据权利要求1-4中任一项所述的方法，其特征在于，所述对所述目标存储分区进行独立更新，包括：
    对所述目标存储分区所存储的内容进行备份，响应于所述目标存储分区更新异常或失败，停止更新并基于所述备份对所述目标存储分区进行恢复。
  8. 根据权利要求1-4中任一项所述的方法，其特征在于，所述对所述目标存储分区进行独立更新，包括：
    响应于所述目标存储分区更新异常或失败，对所述目标存储分区所存储的内容进行回滚。
  9. 一种基于空中下载技术OTA的系统更新装置，其特征在于，包括：
    第一获取模块，用于获取OTA更新请求，所述OTA更新请求包括配置文件的部分更新数据；
    第二获取模块，用于获取系统内存储分区之间的依赖关系，其中所述系统的配置文件存储于所述存储分区中；
    独立更新模块，用于根据所述依赖关系和所述更新数据，确定请求更新的目标存储分区，并对所述目标存储分区进行独立更新。
  10. 根据权利要求9所述的装置，其特征在于，所述第二获取模块，还用于：
    从所述系统的指定存储位置，获取所述依赖关系。
  11. 根据权利要求9或10所述的装置，其特征在于，所述第二获取模块，还用于：
    获取每个所述存储分区所存储的所述配置文件中的内容；
    根据所述内容之间的逻辑依赖关系，获取所述存储分区之间的依赖关系。
  12. 根据权利要求11所述的装置，其特征在于，所述第二获取模块，还用于：
    将未存在逻辑依赖关系的所述内容所在的存储分区，确定为与任一存储分区未存在依赖关系的第一存储分区；
    将存在逻辑依赖关系的存储分区确定为第二存储分区。
  13. 根据权利要求12所述的装置，其特征在于，所述独立更新模块，还用于：
    根据所述更新数据，从所述系统的存储分区中确定所述目标存储分区；
    根据所述依赖关系确定所述目标存储分区为所述第一存储分区，则基于所述更新数据直接对所述目标存储分区进行更新；
    根据所述依赖关系确定所述目标存储分区为所述第二存储分区，则对所述目标存储分区上所存储内容进行备份，并基于所述更新数据对所述目标存储分区进行更新。
  14. 根据权利要求9所述的装置，其特征在于，所述独立更新模块，还用于：
    重复执行确定请求更新的目标存储分区，并对所述目标存储分区进行独立更新等操作，直至所述系统更新完毕。
  15. 根据权利要求9-12中任一项所述的装置，其特征在于，所述独立更新模块，还用于：
    对所述目标存储分区所存储的内容进行备份，响应于所述目标存储分区更新异常或失败，停止更新 并基于所述备份对所述目标存储分区进行恢复。
  16. 根据权利要求9-12中任一项所述的装置，其特征在于，所述独立更新模块，还用于：
    响应于所述目标存储分区更新异常或失败，对所述目标存储分区所存储的内容进行回滚。
  17. 一种电子设备，其特征在于，包括存储器、处理器；
    其中，所述处理器通过读取所述存储器中存储的可执行程序代码来运行与所述可执行程序代码对应的程序，以用于实现如权利要求1-8中任一项所述的方法。
  18. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求1-8中任一项所述的方法。
  19. 一种计算机程序产品，包括计算机程序，所述计算机程序在被处理器执行时实现如权利要求1-8中任一项所述的方法。
PCT/CN2022/093696 2022-05-18 2022-05-18 基于ota的系统更新方法、装置、电子设备及存储介质 WO2023221002A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280004209.8A CN117441159A (zh) 2022-05-18 2022-05-18 基于ota的系统更新方法、装置、电子设备及存储介质
PCT/CN2022/093696 WO2023221002A1 (zh) 2022-05-18 2022-05-18 基于ota的系统更新方法、装置、电子设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/093696 WO2023221002A1 (zh) 2022-05-18 2022-05-18 基于ota的系统更新方法、装置、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023221002A1 true WO2023221002A1 (zh) 2023-11-23

Family

ID=88834195

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/093696 WO2023221002A1 (zh) 2022-05-18 2022-05-18 基于ota的系统更新方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN117441159A (zh)
WO (1) WO2023221002A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105893076A (zh) * 2015-12-25 2016-08-24 乐视致新电子科技（天津）有限公司 一种空中升级方法与装置
CN106406903A (zh) * 2016-09-30 2017-02-15 美的智慧家居科技有限公司 设备中系统更新的方法和装置
US20180211044A1 (en) * 2016-05-09 2018-07-26 Boe Technology Group Co., Ltd. Method and apparatus for upgrading embedded memory and terminal associated therewith
CN111263354A (zh) * 2020-01-08 2020-06-09 苏宁智能终端有限公司 一种ota差分升级方法及装置
CN112667266A (zh) * 2021-01-22 2021-04-16 百度在线网络技术（北京）有限公司 固件升级方法、装置、设备和存储介质
CN113900699A (zh) * 2021-05-26 2022-01-07 荣耀终端有限公司 一种系统升级方法和电子设备
CN114143197A (zh) * 2021-11-29 2022-03-04 武汉天喻信息产业股份有限公司 物联网设备ota升级方法、装置、设备及可读存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105893076A (zh) * 2015-12-25 2016-08-24 乐视致新电子科技（天津）有限公司 一种空中升级方法与装置
US20180211044A1 (en) * 2016-05-09 2018-07-26 Boe Technology Group Co., Ltd. Method and apparatus for upgrading embedded memory and terminal associated therewith
CN106406903A (zh) * 2016-09-30 2017-02-15 美的智慧家居科技有限公司 设备中系统更新的方法和装置
CN111263354A (zh) * 2020-01-08 2020-06-09 苏宁智能终端有限公司 一种ota差分升级方法及装置
CN112667266A (zh) * 2021-01-22 2021-04-16 百度在线网络技术（北京）有限公司 固件升级方法、装置、设备和存储介质
CN113900699A (zh) * 2021-05-26 2022-01-07 荣耀终端有限公司 一种系统升级方法和电子设备
CN114143197A (zh) * 2021-11-29 2022-03-04 武汉天喻信息产业股份有限公司 物联网设备ota升级方法、装置、设备及可读存储介质

Also Published As

Publication number Publication date
CN117441159A (zh) 2024-01-23

Similar Documents

Publication Publication Date Title
US9459856B2 (en) Effective migration and upgrade of virtual machines in cloud environments
US20190065165A1 (en) Automated deployment of applications
US10445186B1 (en) Associating a guest application within a virtual machine to create dependencies in backup/restore policy
WO2014084922A1 (en) High availability for cloud servers
WO2015097583A1 (en) Configuration updates across peer storage systems
MX2014007678A (es) Tomas de pantalla consistentes con aplicacion de un volumen compartido.
WO2021139224A1 (zh) 云场景下的文件备份方法、装置、介质、电子设备
US20200233698A1 (en) Client controlled transaction processing involving a plurality of participants
US11231919B2 (en) Live updates of stateful components
US11068327B1 (en) API manager
US10628070B2 (en) Selecting and compressing target files to obtain additional free data storage space to perform an operation in a virtual machine
US20160371071A1 (en) Account-based software upgrades in a multi-tenant ecosystem
CN110413369B (zh) 用于虚拟化环境中的备份的系统和方法
US10698719B2 (en) System and method for virtual machine restoration
US10503428B2 (en) System and method for concurrent multipoint backup
KR101638689B1 (ko) 클라이언트 단말에 대한 사용자 맞춤형 동기화 서비스 제공 방법 및 시스템
US11288133B2 (en) System and method for resilient data protection
WO2023221002A1 (zh) 基于ota的系统更新方法、装置、电子设备及存储介质
US11599422B2 (en) System and method for device independent backup in distributed system
CN113761075A (zh) 切换数据库的方法、装置、设备和计算机可读介质
CN109101253B (zh) 云计算系统中主机的管理方法和装置
US10666721B2 (en) Resource management device and method
JP5317182B2 (ja) Ｐｏｓ端末、モジュールアップデート方法およびモジュールアップデートプログラム
CN113868679B (zh) 一种集群的加密方法及装置
US20220342686A1 (en) Virtual machine file management using file-level snapshots

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280004209.8

Country of ref document: CN

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

Ref document number: 22942044

Country of ref document: EP

Kind code of ref document: A1