WO2017215088A1 - Ota开机加速方法及系统 - Google Patents

Ota开机加速方法及系统 Download PDF

Info

Publication number
WO2017215088A1
WO2017215088A1 PCT/CN2016/092526 CN2016092526W WO2017215088A1 WO 2017215088 A1 WO2017215088 A1 WO 2017215088A1 CN 2016092526 W CN2016092526 W CN 2016092526W WO 2017215088 A1 WO2017215088 A1 WO 2017215088A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
update
core
updated
core application
Prior art date
Application number
PCT/CN2016/092526
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 WO2017215088A1 publication Critical patent/WO2017215088A1/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
    • 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/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • 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 the field of system upgrades, for example, to an over-the-air OTA boot acceleration method and system.
  • OTA Over-the-Air Technology
  • GSM Global System for Mobile communications
  • CDMA Code Division Multiple Access
  • Odex is a runnable file extracted from the application apk on Android.
  • the classes.dex file in the apk is optimized by the dex optimization process to generate an odex file separately, and the classes.dex in the original apk.
  • the file will be retained. This can speed up the software startup speed, pre-fetch, reduce the occupation of RAM, because there is no odex file, the system should extract the dex file from the apk package and run.
  • the machine code cache odex file of the application apk file needs to be generated to speed up the application execution speed; however, as the user installs more applications on the mobile phone, the booting time is longer; and the user does not boot after booting. All applications need to be available immediately, but wait for all applications to be updated before they can enter the desktop to use the system, wasting user time.
  • the present disclosure provides an OTA boot acceleration method and system, which reduces the waiting time of the OTA boot and improves the user experience.
  • An on-air acceleration method for downloading an OTA over the air including:
  • the Android system is started;
  • the update task thread of the preset non-core application is started in the background to update the non-core application.
  • the core application includes a system application that is included in the Android system;
  • the non-core application includes a third-party application downloaded and installed by a user.
  • the method further includes:
  • the application When the application is not updated, it is determined whether the application is being updated, when the application is being updated, the user is prompted to update the application, and when the application is not being updated, the application is executed in bytecode.
  • the updating the task thread of the preset core application to update the core application includes:
  • the update task thread of the preset core application is started to update the odex file corresponding to the Apk file of the core application.
  • the updating the task thread of the preset non-core application in the background to update the non-core application includes:
  • the update task thread of the preset non-core application is started in the background to update the odex file corresponding to the Apk file of the non-core application.
  • An over-the-air download OTA boot acceleration system including:
  • the system startup module is configured to start the Android system after the OTA upgrades the Android Android system;
  • a first update module configured to start an update task thread of the preset core application to update the core application
  • a desktop launch module set to launch the desktop application
  • the second update module is configured to start an update task thread of the preset non-core application in the background to update the non-core application.
  • the core application includes a system application that is included in the Android system;
  • the non-core application includes a third-party application downloaded and installed by a user.
  • it also includes:
  • An instruction receiving module configured to receive a user startup instruction of the application after the desktop application is started
  • a first determining module configured to determine whether the application has been updated, and when the application has been updated, execute the application with a machine code
  • a second determining module configured to determine, when the first determining module determines that the application is not updated Whether the application is being updated, when the application is being updated, the user is prompted to update the application, and when the application is not being updated, the application is executed in bytecode.
  • the first update module is further configured to:
  • the update task thread of the preset core application is started to update the odex file corresponding to the Apk file of the core application.
  • the second update module is further configured to:
  • the update task thread of the preset non-core application is started in the background to update the odex file corresponding to the Apk file of the non-core application.
  • a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the OTA boot acceleration method of any of the above.
  • the present invention provides an OTA boot acceleration method and system, the method comprising: starting the Android system after the OTA upgrades the Android system; starting an update task thread of the preset core application to update the core application; and starting the desktop application
  • the update task thread of the preset non-core application is started in the background to update the non-core application.
  • the user does not need all the applications to be immediately available. Therefore, only the core application is updated at the time of booting, and the desktop application is not blocked. After entering the desktop, the non-core application is updated through the background, and the OTA can be quickly booted. It is not affected by the number of applications installed by users, improving system performance, reducing boot time, and improving user experience.
  • FIG. 1 is a flowchart of a method of a first embodiment of an OTA boot acceleration method according to an alternative embodiment of the present disclosure.
  • FIG. 2 is a flowchart of a method of a second embodiment of an OTA boot acceleration method according to an alternative embodiment of the present disclosure.
  • FIG. 3 is a structural block diagram of a first embodiment of an OTA boot acceleration system provided by an alternative embodiment of the present disclosure.
  • FIG. 4 is a structural block diagram of a second embodiment of an OTA boot acceleration system provided by an alternative embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of a hardware structure of an apparatus for performing an OTA boot acceleration method according to an alternative embodiment of the present disclosure.
  • FIG. 1 is a flowchart of a method of a first embodiment of an OTA boot acceleration method according to an alternative embodiment of the present disclosure.
  • an OTA boot acceleration method includes the following steps:
  • the system is restarted and the OTA is booted.
  • the core application is updated.
  • the core applications described herein include system applications that are included in the system, such as system applications such as a dial pad and a short message.
  • the desktop application is launched, so that the icons of the applications installed in the system are presented on the desktop and arranged in a certain manner.
  • the update thread of the non-core application is run in the background.
  • the non-core application here includes third-party applications installed by the user, including today's headlines, Taobao, and Ctrip.
  • This embodiment provides an OTA boot acceleration method. After the OTA upgrades the system, the user does not need all the applications to be immediately available. Therefore, only the core application is updated when the system is powered on, and the desktop application is not blocked. After entering the desktop, the non-core is updated through the background.
  • the application can realize the rapid startup of the OTA, which is not affected by the number of applications installed by the user, improves the system performance, reduces the boot time, and improves the user experience.
  • FIG. 2 is a flowchart of a method for a second embodiment of an OTA boot acceleration method according to an alternative embodiment of the present disclosure. This embodiment adds several steps to the first embodiment of the foregoing method.
  • an OTA boot acceleration method includes the following steps:
  • an update task thread of the preset core application is started to update an odex file corresponding to the apk file of the core application.
  • the desktop application is launched, so that the icons of the applications installed in the system are presented on the desktop. And arranged in a certain way.
  • the update task thread of the preset non-core application is started in the background to update the odex file corresponding to the apk file of the non-core application.
  • the core application includes a system application that is included in the Android system; and the non-core application includes a third-party application that the user downloads and installs.
  • the odex file is a runnable file extracted from the application apk of the Android system, and the classes.dex file in the apk is optimized by the dex optimization process to generate an odex file separately, which is stored in the original apk.
  • the classes.dex file will be kept. This can speed up the software startup speed, pre-fetch, reduce the occupation of RAM, because there is no odex, the system should extract dex from the apk package and then run. After the OTA upgrade of the Android system, the odex files corresponding to all applications are also updated.
  • the system automatically determines whether the application that the user wants to start has been updated, that is, whether the odex file corresponding to the application apk file is The update has been completed.
  • the application can be executed normally in machine code, and the application can be run through the odex file.
  • the application When the application has not completed the update, it is determined whether the system is performing the update task thread of the application. When the application is being updated, the user is prompted to update the application, and the application can be started later, and the screen can be reminded. The user can also display the progress bar of the application update to the user; when the application has not started to update, the application is executed in bytecode, and the dex file can be extracted from the apk file, and then the application is run.
  • This embodiment provides an OTA boot acceleration method. After the OTA upgrades the system, only the core application is updated when the OTA is upgraded, and the desktop application is not blocked. After the desktop is accessed, the non-core application is updated through the background, and the OTA can be quickly booted.
  • the system automatically determines whether the application has been updated. When the application has been updated, the application is run with the machine code; when the application has not completed the update, it detects whether the application is being updated. Remind users that they are updating Applications that are not yet updated are run in bytecode.
  • the method only updates the core application when the OTA is powered on, it is not affected by the number of applications installed by the user, and can realize fast booting, and processes the update thread of the non-core application in the background after booting, thereby improving the performance of the system while improving the performance of the user. Use experience.
  • the following is an embodiment of the OTA boot acceleration system provided by the technical solution.
  • the embodiment of the system is implemented based on an embodiment of the OTA boot acceleration method. For details not described in the embodiment of the system, refer to the embodiment of the foregoing method. .
  • FIG. 3 is a structural block diagram of a first embodiment of an OTA boot acceleration system according to an alternative embodiment of the present disclosure.
  • an OTA boot acceleration system includes:
  • the system startup module 310 is configured to start the Android system after the OTA upgrades the Android system.
  • the first update module 320 is configured to start an update task thread of the preset core application to update the core application.
  • the desktop launch module 330 is configured to launch a desktop application.
  • the second update module 340 is configured to start an update task thread of the preset non-core application in the background to update the non-core application.
  • the embodiment provides an OTA boot acceleration system.
  • the above modules work together.
  • the Android system is started by the system startup module 310, and the boot system is started.
  • the first update module 320 updates the core application
  • the desktop is updated.
  • the startup module 330 starts the desktop, so that the application icon installed in the system is displayed on the desktop.
  • the second update module 340 can update the non-core application through the background, so that the OTA can be quickly booted, and is not affected by the number of applications installed by the user. Improve system performance, reduce boot time, and improve user experience.
  • FIG. 4 is a structural block diagram of a second embodiment of an OTA boot acceleration system according to an alternative embodiment of the present disclosure. This embodiment adds several steps to the first embodiment of the system.
  • an OTA boot acceleration system includes:
  • the system startup module 310 is configured to start the Android system after the OTA upgrades the Android system.
  • the first update module 320 is further configured to start an update task thread of the preset core application to update the odex file corresponding to the Apk file of the core application.
  • the desktop launch module 330 is configured to launch a desktop application.
  • the second update module 340 is further configured to start an update task thread of the preset non-core application in the background to update the odex file corresponding to the Apk file of the non-core application.
  • the core application includes a system application that is included in the Android system; and the non-core application includes a third-party application that the user downloads and installs.
  • the instruction receiving module 450 is configured to receive a user startup instruction of the application after the desktop startup module 430 starts the desktop application.
  • the first determining module 460 is configured to determine whether the application has been updated, and when the application has been updated, execute the application with a machine code.
  • the second determining module 470 is configured to
  • the first determining module 460 determines that the application is not updated, whether the application is being updated, when the application is being updated, prompting the user that the application is being updated; when the application is not being updated, the word is The section code executes the application.
  • the first determining module 460 automatically determines whether the application that the user wants to start has been updated, that is, the odex corresponding to the application apk file. Whether the file has been updated or not, when the application has completed the update, the application can be executed normally with the machine code, and the application can be run through the odex file.
  • the second determining module 470 determines whether the system is performing the update task thread of the application.
  • the user is prompted to update the application, and the application can be started later.
  • the user can be prompted to play the screen, or the progress bar of the application update can be displayed to the user; when the application has not started to update, the application is executed in bytecode, and the dex file can be extracted from the apk file, and then run.
  • the app is prompted to update the application, and the application can be started later. The user can be prompted to play the screen, or the progress bar of the application update can be displayed to the user; when the application has not started to update, the application is executed in bytecode, and the dex file can be extracted from the apk file, and then run. The app.
  • This embodiment provides an OTA boot acceleration system.
  • the modules in the system work together. After the OTA upgrades the system, only the core application is updated when the system is booted, and the desktop application is not blocked. After entering the desktop, the non-core is updated through the background.
  • the application can realize the quick start of the OTA.
  • the system automatically determines whether the application has been updated. When the application has been updated, the application is run by the machine code; when the application has not completed the update, Then, it is detected whether the application is being updated, the user is reminded that the application is being updated, and the application that has not been updated is operated in the form of bytecode.
  • the technical solution only updates the core application when the OTA is powered on, it is not affected by the number of applications installed by the user, and can realize fast booting, and processes the update thread of the non-core application in the background after booting, thereby improving the performance of the system while improving the user performance.
  • the experience of using because the technical solution only updates the core application when the OTA is powered on, it is not affected by the number of applications installed by the user, and can realize fast booting, and processes the update thread of the non-core application in the background after booting, thereby improving the performance of the system while improving the user performance. The experience of using.
  • Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the OTA boot acceleration method of any of the above.
  • the embodiment of the invention further provides an apparatus for performing an OTA boot acceleration method.
  • the device includes:
  • One or more processors 510, one processor 510 is taken as an example in FIG. 5;
  • the device may also include an input device 530 and an output device 540.
  • the processor 510, the memory 520, the input device 530, and the output device 540 in the device may be connected by a bus or other means, and the connection is made by way of a bus connection in FIG.
  • the memory 520 is used as a computer readable storage medium, and can be used to store a software program, a computer executable program, such as a program instruction/module corresponding to the OTA boot acceleration method in the embodiment of the present invention.
  • the processor 510 executes the function application and the data processing of the server by running the software program, the instruction and the module stored in the memory 520, that is, the OTA boot acceleration method in the foregoing method embodiment.
  • the memory 520 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 520 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other nonvolatile solid state storage device. In some examples, memory 520 can include memory remotely located relative to processor 510, which can be connected to the terminal device over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Input device 530 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal.
  • the output device 540 can include a display device such as a display screen.
  • the at least one module is stored in the memory 520, and when executed by the at least one processor 510, performs the steps of the above method embodiments.
  • the present invention provides an OTA boot acceleration method. After the OTA upgrades the system, the user does not need all the applications to be immediately available. Therefore, only the core application is updated when booting, the desktop application is not blocked, and the non-core application is updated through the background after entering the desktop. It can realize OTA fast booting, is not affected by the number of users installed, improve system performance, reduce boot time, and improve user experience.

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

一种OTA开机加速方法，包括在OTA升级Android系统后，启动所述Android系统；启动预置的核心应用的更新任务线程，以更新所述核心应用；启动桌面应用；在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。

Description

OTA开机加速方法及系统
本申请要求在2016年6月15日提交中国专利局、申请号为201610422342.1、发明名称为“一种OTA开机加速方法及系统”的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开涉及系统升级领域，例如涉及一种空中下载OTA开机加速方法及系统。
背景技术
空中下载技术(Over-the-Air Technology，OTA)是通过移动通信(GSM或CDMA)的空中接口对SIM卡数据及应用进行远程管理的技术。空中接口可以采用WAP、GPRS、CDMA1X及短消息技术。OTA技术的应用，使得移动通信不仅可以提供语音和数据服务，而且还能提供新业务下载。
Odex是安卓上的应用程序apk中提取出来的可运行文件，即将apk中的classes.dex文件通过dex优化过程将所述classes.dex文件优化生成一个odex文件单独存放，原apk中的classes.dex文件会保留。这样做可以加快软件的启动速度，预先提取，减少对RAM的占用，因为没有odex文件的话，系统要从apk包中提取dex文件再运行。
一般的OTA开机方案，需要生成应用apk文件的机器码缓存odex文件以加快应用执行速度；但随着用户在手机上安装的应用越多，开机等待的时间就越长；而且开机后用户并不需要所有应用立即可用，却要等待所有应用更新完才能进入桌面使用系统，浪费了用户的时间。
发明内容
本公开提供了一种OTA开机加速方法及系统，减少了OTA开机的等待时间，提高了用户体验。
一种空中下载OTA的开机加速方法，包括：
在OTA升级安卓Android系统后，启动所述Android系统；
启动预置的核心应用的更新任务线程，以更新所述核心应用；
启动桌面应用；以及
在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。
可选的，所述核心应用包括Android系统自带的系统应用；
所述非核心应用包括用户下载安装的第三方应用。
可选的，所述启动桌面应用之后，还包括：
接收到应用的用户启动指令；
判断所述应用是否已更新，当所述应用已更新，则以机器码执行该应用；
当所述应用没有更新，判断所述应用是否正在更新，当所述应用正在更新，则提示用户该应用正在更新，当所述应用不是正在更新，则以字节码执行该应用。
可选的，所述启动预置的核心应用的更新任务线程，以更新所述核心应用，包括：
启动预置的核心应用的更新任务线程，以更新所述核心应用的Apk文件对应的odex文件。
可选的，所述在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用，包括：
在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用的Apk文件对应的odex文件。
一种空中下载OTA开机加速系统，包括：
系统启动模块，设置为在OTA升级安卓Android系统后，启动所述Android系统；
第一更新模块，设置为启动预置的核心应用的更新任务线程，以更新所述核心应用；
桌面启动模块，设置为启动桌面应用；以及
第二更新模块，设置为在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。
可选的，所述核心应用包括Android系统自带的系统应用；
所述非核心应用包括用户下载安装的第三方应用。
可选的，还包括：
指令接收模块，设置为在所述启动桌面应用之后，接收到应用的用户启动指令；
第一判断模块，设置为判断所述应用是否已更新，当所述应用已更新，则以机器码执行该应用；以及
第二判断模块，设置为在第一判断模块判断所述应用没有更新时，判断所 述应用是否正在更新，当所述应用正在更新，则提示用户该应用正在更新，当所述应用不是正在更新，则以字节码执行该应用。
可选的，所述第一更新模块，还设置为：
启动预置的核心应用的更新任务线程，以更新所述核心应用的Apk文件对应的odex文件。
可选的，所述第二更新模块，还设置为：
在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用的Apk文件对应的odex文件。
一种非瞬时性计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述任一项的OTA开机加速方法。
本公开提供的一种OTA开机加速方法及系统，该方法包括在OTA升级Android系统后，启动所述Android系统；启动预置的核心应用的更新任务线程，以更新所述核心应用；启动桌面应用；在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。本公开中，在OTA升级系统后用户不需要所有应用立即可用，故在开机时只更新核心应用，不阻塞桌面应用启动，在进入桌面之后，通过后台更新非核心应用，可实现OTA快速开机，不受用户安装应用数的影响，提升系统性能，减少开机时间，提高用户的使用体验。
附图概述
为了更清楚地说明本公开实施例中的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单的介绍，下面描述中的附图仅仅是本公开的一些实施例的附图。
图1是本公开可选实施方式提供的一种OTA开机加速方法的第一实施例的方法流程图。
图2是本公开可选实施方式提供的一种OTA开机加速方法的第二实施例的方法流程图。
图3是本公开可选实施方式提供的一种OTA开机加速系统的第一实施例的结构方框图。
图4是本公开可选实施方式提供的一种OTA开机加速系统的第二实施例的结构方框图；
图5是本公开可选实施方式提供的执行OTA开机加速方法的设备的硬件结构示意图。
实施方式
下面结合附图并通过实施方式来说明本公开的技术方案。
图1为本公开可选实施方式提供的一种OTA开机加速方法的第一实施例的方法流程图。
参照图1，一种OTA开机加速方法，包括以下步骤：
在S110中，在OTA升级Android系统后，启动所述Android系统。
本实施例中，在OTA升级Android系统后，会重启系统，进行OTA开机。
在S120中，启动预置的核心应用的更新任务线程，以更新所述核心应用。
可选的，在OTA开机的过程中，更新核心应用，这里所述的核心应用包括系统自带的系统应用，如拨号盘、短信等系统应用。
在S130中，启动桌面应用。
可选的，启动桌面应用程序，使得系统中安装的应用的图标呈现在桌面上，并按照一定的方式排布。
在S140中，在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。
本实施例中，在进入桌面系统之后，在后台运行非核心应用的更新线程，这里的非核心应用包括用户自行安装的第三方应用，包括今日头条、淘宝以及携程旅行等应用。
本实施例提供了一种OTA开机加速方法，在OTA升级系统后用户不需要所有应用立即可用，故在开机时只更新核心应用，不阻塞桌面应用启动，在进入桌面之后，通过后台更新非核心应用，可实现OTA快速开机，不受用户安装应用数的影响，提升系统性能，减少开机时间，提高了用户的使用体验。
图2为本公开可选的实施方式提供的一种OTA开机加速方法的第二实施例的方法流程图，本实施例在上述方法的第一实施例的基础上增加了几个步骤。
参照图2，一种OTA开机加速方法，包括以下步骤：
在S210中，在OTA升级Android系统后，启动所述Android系统。
在S220中，启动预置的核心应用的更新任务线程，以更新所述核心应用的apk文件对应的odex文件。
在S230中，启动桌面应用。
可选的，启动桌面应用程序，使得系统中安装的应用的图标呈现在桌面上， 并按照一定的方式排布。
在S240中，在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用的apk文件对应的odex文件。
本实施例中，所述核心应用包括Android系统自带的系统应用；所述非核心应用包括用户下载安装的第三方应用。
其中，odex文件是Android系统的应用程序apk中提取出来的可运行文件，即将apk中的classes.dex文件通过dex优化过程将所述classes.dex文件优化生成一个odex文件单独存放，原apk中的classes.dex文件会保留。这样做可以加快软件的启动速度，预先提取，减少对RAM的占用，因为没有odex的话，系统要从apk包中提取dex再运行。在Android系统进行OTA升级之后，所有应用程序对应的odex文件也要进行更新。
在S250中，接收到应用的用户启动指令。
在S260中，判断所述应用是否已更新。
在S270中，当所述应用已更新，则以机器码执行该应用。
在S280中，当所述应用没有更新，判断所述应用是否正在更新。
在S290中，当所述应用正在更新，则提示用户该应用正在更新。
在S2000中，当所述应用没有在更新，则以字节码执行该应用。
可选的，当用户在桌面上点击应用程序对应的桌面图标，以启用该应用程序时，系统会自动判断用户想要启动的应用是否已经完成更新，即所述应用apk文件对应的odex文件是否已经完成更新，当该应用已经完成更新，则可以正常以机器码执行该应用，可以为通过odex文件来运行该应用。
当该应用还没有完成更新，则判断系统是否正在进行该应用的更新任务线程，当应用正在更新，则提示用户该应用正在更新中，可稍后再启动该应用，可以弹屏的方式来提醒用户，也可以向用户显示该应用更新的进度条；当该应用还没有开始更新，则以字节码执行该应用，可以为从apk文件中提取dex文件，再运行该应用。
本实施例提供一种OTA开机加速方法，该方法在OTA升级系统后，在开机时只更新核心应用，不阻塞桌面应用启动，在进入桌面之后，通过后台更新非核心应用，可实现OTA快速开机，在用户进入桌面选择要启动的应用时，系统自动判断该应用是否已更新，当应用已更新，则以机器码运行该应用；当应用还没有完成更新，则检测判断该应用是否正在更新，提醒用户正在更新的应 用，而还没有进行更新的应用则以字节码的形式运行。该方法因为在OTA开机时只更新核心应用，故不受用户安装应用数的影响，能实现快速开机，且在开机后后台处理非核心应用的更新线程，在提升系统性能的同时提高了用户的使用体验。
以下为本技术方案提供的OTA开机加速系统的实施例，该系统的实施例基于OTA开机加速方法的实施例来实现，在该系统的实施例中未详细描述的内容请参考上述方法的实施例。
图3为本公开可选实施方式提供的一种OTA开机加速系统的第一实施例的结构方框图。
参照图3，一种OTA开机加速系统，包括：
系统启动模块310，设置为在OTA升级Android系统后，启动所述Android系统。
第一更新模块320，设置为启动预置的核心应用的更新任务线程，以更新所述核心应用。
桌面启动模块330，设置为启动桌面应用。
第二更新模块340，设置为在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。
本实施例提供了一种OTA开机加速系统，以上各模块协同工作，在OTA升级系统后，通过系统启动模块310启动所述Android系统，进入开机系统，第一更新模块320更新核心应用后，桌面启动模块330启动桌面，使得系统中安装的应用图标显示在桌面上，在进入桌面之后，第二更新模块340通过后台更新非核心应用，可实现OTA快速开机，不受用户安装应用数的影响，提升系统性能，减少开机时间，提高了用户的使用体验。
图4为本公开可选实施方式提供的一种OTA开机加速系统的第二实施例的结构方框图，本实施例在上述系统的第一实施例的基础上增加了几个步骤。
参照图4，一种OTA开机加速系统，包括：
系统启动模块310，设置为在OTA升级Android系统后，启动所述Android系统。
第一更新模块320，还设置为启动预置的核心应用的更新任务线程，以更新所述核心应用的Apk文件对应的odex文件。
桌面启动模块330，设置为启动桌面应用。
第二更新模块340，还设置为在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用的Apk文件对应的odex文件。
本实施例中，所述核心应用包括Android系统自带的系统应用；所述非核心应用包括用户下载安装的第三方应用。
指令接收模块450，设置为在所述桌面启动模块430启动桌面应用之后，接收到应用的用户启动指令。
第一判断模块460，设置为判断所述应用是否已更新，当所述应用已更新，则以机器码执行该应用。
第二判断模块470，设置为
设置为在第一判断模块460判断所述应用没有更新时，判断所述应用是否正在更新，当所述应用正在更新，则提示用户该应用正在更新；当所述应用不是正在更新，则以字节码执行该应用。
可选的，当指令接收模块450检测到用户在桌面上点击应用程序对应的桌面图标时，第一判断模块460会自动判断用户想要启动的应用是否已经完成更新，即应用apk文件对应的odex文件是否已经完成更新，当该应用已经完成更新，则可以正常以机器码执行该应用，可以是通过odex文件来运行该应用。
当该应用还没有完成更新，则通过第二判断模块470判断系统是否正在进行该应用的更新任务线程，当该应用正在更新，则提示用户该应用正在更新中，可稍后再启动该应用，可以弹屏的方式来提醒用户，也可以向用户显示该应用更新的进度条；当该应用还没有开始更新，则以字节码执行该应用，可以是从apk文件中提取dex文件，再运行该应用。
本实施例提供一种OTA开机加速系统，该系统中的各模块协同工作，在OTA升级系统后，在开机时只更新核心应用，不阻塞桌面应用启动，在进入桌面之后，通过后台更新非核心应用，可实现OTA快速开机，在用户进入桌面选择要启动的应用时，系统自动判断该应用是否已更新，当该应用已更新，则以机器码运行该应用；当该应用还没有完成更新，则检测判断该应用是否正在更新，提醒用户正在更新的应用，而还没有进行更新的应用则以字节码的形式运行。本技术方案因为在OTA开机时只更新核心应用，故不受用户安装应用数的影响，能实现快速开机，且在开机后后台处理非核心应用的更新线程，在提升系统性能的同时提高了用户的使用体验。
以上结合可选实施例描述了本公开的技术原理。这些描述只是为了解释本 公开的原理，而不能以任何方式解释为对本公开保护范围的限制。基于此处的解释，本领域的技术人员不需要付出创造性的劳动即可联想到本公开的其它实施方式，这些方式都将落入本公开的保护范围之内。
本公开实施例还提供了一种非瞬时性计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述任一项的OTA开机加速方法。
本发明实施例还提供了一种执行OTA开机加速方法的设备。参见图5，该设备包括：
一个或者多个处理器510，图5中以一个处理器510为例；
存储器520。
所述设备还可以包括：输入装置530和输出装置540。所述设备中的处理器510、存储器520、输入装置530和输出装置540可以通过总线或其他方式连接，图5中以通过总线连接为例进行连接。
存储器520作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如本发明实施例中的OTA开机加速方法对应的程序指令/模块。处理器510通过运行存储在存储器520中的软件程序、指令以及模块，从而执行服务器的功能应用以及数据处理，即实现上述方法实施例中的OTA开机加速方法。
存储器520可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器520可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器520可包括相对于处理器510远程设置的存储器，这些远程存储器可以通过网络连接至终端设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置530可设置为接收输入的数字或字符信息，以及产生与终端的用户设置以及功能控制有关的键信号输入。输出装置540可包括显示屏等显示设备。
所述至少一个模块存储在所述存储器520中，当被所述至少一个处理器510执行时，执行上述方法实施例的步骤。
工业实用性
本公开提供的一种OTA开机加速方法，在OTA升级系统后用户不需要所有应用立即可用，故在开机时只更新核心应用，不阻塞桌面应用启动，在进入桌面之后，通过后台更新非核心应用，可实现OTA快速开机，不受用户安装应用数的影响，提升系统性能，减少开机时间，提高用户的使用体验。

Claims (11)

  1. 一种空中下载OTA开机加速方法，包括：
    在OTA升级安卓Android系统后，启动所述Android系统；
    启动预置的核心应用的更新任务线程，以更新所述核心应用；
    启动桌面应用；以及
    在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。
  2. 根据权利要求1所述的开机加速方法，其中，
    所述核心应用包括Android系统自带的系统应用；
    所述非核心应用包括用户下载安装的第三方应用。
  3. 根据权利要求1所述的开机加速方法，所述启动桌面应用之后，还包括：
    接收到应用的用户启动指令；
    判断所述应用是否已更新，当所述应用已更新，则以机器码执行该应用；
    当所述应用没有更新，判断所述应用是否正在更新，当所述应用正在更新，则提示用户该应用正在更新；当所述应用不是正在更新，则以字节码执行该应用。
  4. 根据权利要求1所述的开机加速方法，其中，所述启动预置的核心应用的更新任务线程，以更新所述核心应用，包括：
    启动预置的核心应用的更新任务线程，以更新所述核心应用的Apk文件对应的odex文件。
  5. 根据权利要求1所述的开机加速方法，其中，所述在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用，包括：
    在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用的Apk文件对应的odex文件。
  6. 一种空中下载OTA开机加速系统，包括：
    系统启动模块，设置为在OTA升级安卓Android系统后，启动所述Android系统；
    第一更新模块，设置为启动预置的核心应用的更新任务线程，以更新所述核心应用；
    桌面启动模块，设置为启动桌面应用；以及
    第二更新模块，设置为在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用。
  7. 根据权利要求6所述的开机加速系统，其中，
    所述核心应用包括Android系统自带的系统应用；
    所述非核心应用包括用户下载安装的第三方应用。
  8. 根据权利要求6所述的开机加速系统，还包括：
    指令接收模块，设置为在所述启动桌面应用之后，接收到应用的用户启动指令；
    第一判断模块，设置为判断所述应用是否已更新，当所述应用已更新，则以机器码执行该应用；以及
    第二判断模块，设置为在第一判断模块判断所述应用没有更新时，判断所述应用是否正在更新，当所述应用正在更新，则提示用户该应用正在更新；当所述应用不是正在更新，则以字节码执行该应用。
  9. 根据权利要求6所述的开机加速系统，其中，所述第一更新模块，还设置为：
    启动预置的核心应用的更新任务线程，以更新所述核心应用的Apk文件对应的odex文件。
  10. 根据权利要求6所述的开机加速系统，其中，所述第二更新模块，还设置为：
    在后台启动预置的非核心应用的更新任务线程，以更新所述非核心应用的Apk文件对应的odex文件。
  11. 一种非瞬时性计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-5任一项的方法。
PCT/CN2016/092526 2016-06-15 2016-07-31 Ota开机加速方法及系统 WO2017215088A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610422342.1 2016-06-15
CN201610422342.1A CN106126203B (zh) 2016-06-15 2016-06-15 一种ota开机加速方法及系统

Publications (1)

Publication Number Publication Date
WO2017215088A1 true WO2017215088A1 (zh) 2017-12-21

Family

ID=57270707

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/092526 WO2017215088A1 (zh) 2016-06-15 2016-07-31 Ota开机加速方法及系统

Country Status (2)

Country Link
CN (1) CN106126203B (zh)
WO (1) WO2017215088A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113076119A (zh) * 2021-03-25 2021-07-06 北京车和家信息技术有限公司 一种车机程序的更新方法、装置、介质和电子设备
CN116643778A (zh) * 2023-07-27 2023-08-25 荣耀终端有限公司 一种应用程序优化方法及电子设备

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106604141A (zh) * 2016-12-28 2017-04-26 北京风行在线技术有限公司 一种双升级方法
CN107015816A (zh) * 2017-05-25 2017-08-04 微鲸科技有限公司 操作系统升级方法、装置及一种智能终端
CN107341052A (zh) * 2017-06-07 2017-11-10 努比亚技术有限公司 一种消息处理方法及装置
CN107368343B (zh) * 2017-08-21 2021-03-26 创维集团智能科技有限公司 一种基于安卓系统的终端开机方法、终端及存储介质
CN110058890A (zh) * 2019-02-28 2019-07-26 努比亚技术有限公司 一种安卓系统启动方法、终端及计算机可读存储介质
CN111142948A (zh) * 2019-12-26 2020-05-12 湖南快乐阳光互动娱乐传媒有限公司 基于Android系统的开机优化方法、系统、Android系统及终端设备
CN112181517A (zh) * 2020-09-24 2021-01-05 北京达佳互联信息技术有限公司 一种应用软件的启动方法、装置、设备和介质
CN117478943A (zh) * 2023-09-08 2024-01-30 荣耀终端有限公司 加载桌面界面的方法和终端设备
CN117093315B (zh) * 2023-10-11 2024-03-15 荣耀终端有限公司 一种升级内容显示方法、电子设备和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040210752A1 (en) * 2003-02-11 2004-10-21 Rao Bindu Rama Electronic device supporting multiple update agents
CN102163150A (zh) * 2010-02-24 2011-08-24 腾讯科技（深圳）有限公司 一种系统启动方法及装置
CN102298532A (zh) * 2011-09-15 2011-12-28 奇智软件（北京）有限公司 一种基于启动项的管理方法及装置
CN104581362A (zh) * 2014-12-25 2015-04-29 四川金网通电子科技有限公司 从云端管理ott智能机顶盒的系统及方法
CN105426214A (zh) * 2015-12-08 2016-03-23 惠州Tcl移动通信有限公司 一种应用程序启动方法、系统及移动终端
CN105530130A (zh) * 2015-12-17 2016-04-27 青岛海信电器股份有限公司 一种空中下载技术的升级方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040210752A1 (en) * 2003-02-11 2004-10-21 Rao Bindu Rama Electronic device supporting multiple update agents
CN102163150A (zh) * 2010-02-24 2011-08-24 腾讯科技（深圳）有限公司 一种系统启动方法及装置
CN102298532A (zh) * 2011-09-15 2011-12-28 奇智软件（北京）有限公司 一种基于启动项的管理方法及装置
CN104581362A (zh) * 2014-12-25 2015-04-29 四川金网通电子科技有限公司 从云端管理ott智能机顶盒的系统及方法
CN105426214A (zh) * 2015-12-08 2016-03-23 惠州Tcl移动通信有限公司 一种应用程序启动方法、系统及移动终端
CN105530130A (zh) * 2015-12-17 2016-04-27 青岛海信电器股份有限公司 一种空中下载技术的升级方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113076119A (zh) * 2021-03-25 2021-07-06 北京车和家信息技术有限公司 一种车机程序的更新方法、装置、介质和电子设备
CN113076119B (zh) * 2021-03-25 2023-12-12 北京车和家信息技术有限公司 一种车机程序的更新方法、装置、介质和电子设备
CN116643778A (zh) * 2023-07-27 2023-08-25 荣耀终端有限公司 一种应用程序优化方法及电子设备
CN116643778B (zh) * 2023-07-27 2024-03-19 荣耀终端有限公司 一种应用程序优化方法及电子设备

Also Published As

Publication number Publication date
CN106126203B (zh) 2018-05-15
CN106126203A (zh) 2016-11-16

Similar Documents

Publication Publication Date Title
WO2017215088A1 (zh) Ota开机加速方法及系统
US9606791B2 (en) Controlled method and apparatus to securely install and update software
US9032383B2 (en) Automatically updating applications on a client's device without interrupting the user's experience
US8583907B2 (en) Electronic device having an alterable configuration and methods of manufacturing and configuring the same
US9690561B2 (en) Preinstalled application management method for mobile terminal and mobile terminal
WO2017185253A1 (zh) 基于补丁升级的文件处理方法、装置、终端以及存储介质
CN107992308B (zh) 一种安卓终端应用程序的插件化管理方法
WO2012109781A1 (zh) 应用图标的处理方法及通信终端
CN110913015A (zh) 一种云手机app的分布式快捷安装方法、系统及介质
TW200818017A (en) Update-startup apparatus and update-startup control method
CN107368343B (zh) 一种基于安卓系统的终端开机方法、终端及存储介质
CN110543321A (zh) Ota升级方法、装置、终端以及计算机可读存储介质
EP3657326B1 (en) Broadcast event processing method and device
WO2017219861A1 (zh) 系统启动模式的控制方法及装置
WO2017186066A1 (zh) 软件管理方法及装置
WO2011095108A1 (zh) 应用程序界面的动态显示方法及装置
CN108038010A (zh) 安卓系统启动阶段广播发送方法、装置和终端
CN107729042A (zh) 移动应用升级方法及装置、存储介质、电子设备
CN108459868A (zh) 一种软件启动方法、装置、终端和存储介质
CN112035132A (zh) 应用程序的语言切换方法及装置
CN106293790B (zh) 基于Firefox操作系统的应用程序升级方法和装置
CN113157337A (zh) 应用程序启动方法、装置、终端设备及存储介质
CN106445601A (zh) 一种插件升级的方法及装置
US20140137092A1 (en) Information processing apparatus, information processing system, non-transitory computer-readable storage medium having stored therein information processing program, and information processing method
CN113821264A (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: 16905201

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

Country of ref document: EP

Kind code of ref document: A1