CN106610839B

Movatterモバイル変換

Info

Publication number: CN106610839B
Application number: CN201510688641.5A
Authority: CN
Inventors: 林海涛; 庞军平; 熊红亮; 傅宇玲; 乔燕曦
Original assignee: Alibaba Group Holding Ltd
Current assignee: Banma Zhixing Network Hongkong Co Ltd
Priority date: 2015-10-21
Filing date: 2015-10-21
Publication date: 2020-10-30
Anticipated expiration: 2035-10-21
Also published as: CN106610839A

Abstract

The application discloses a method and a device for issuing an upgrade package, a method and a device for lightweight upgrade, a lightweight upgrade system, and a method and a device for manufacturing the lightweight upgrade package. The method for issuing the upgrade package comprises the following steps: aiming at an application program to be issued, the coupling degree of which with a system meets a preset requirement, a lightweight upgrade package is manufactured; and sending the lightweight upgrade information to the client so that the client can acquire the lightweight upgrade package and execute corresponding upgrade operation. The method disclosed by the application realizes the quick update and release of the application program, namely: once the application program which is coupled with the system and meets the preset requirement is developed and tested, the application program can be released to the client in a light-weight upgrade package without waiting for the whole software system to be released together. And because the lightweight upgrade package can adapt to multiple models, the models and the partitions do not need to be distinguished in the upgrade process of the client, thereby simplifying the operation and improving the execution efficiency.

Description

Method for issuing upgrade package, lightweight upgrade method, device and system

Technical Field

The present application relates to a firmware upgrading technology, and in particular, to a method and an apparatus for issuing an upgrade package. The application also relates to a light-weight upgrading method and device, a light-weight upgrading system, and a method and device for manufacturing the light-weight upgrading package.

Background

FOTA (Firmware Over-The-Air), an Over-The-Air software upgrade technique, also called remote Firmware upgrade, refers to a device with a networking function by using a cloud upgrade technique: for example, a mobile phone, a tablet computer, a portable media player, a mobile internet device, etc. provide firmware upgrade services, and a user obtains an intelligent terminal system upgrade package in an easily extensible manner as required by using a network, thereby completing functions such as system upgrade, system repair and optimization. For operators and wireless terminal manufacturers, the FOTA technology can avoid equipment recall, reduce customer service calls and reduce operation execution cost; for a user, the terminal equipment with the FOTA function is used, so that upgrading operation can be completed conveniently and quickly, and a complicated process of seeking help by going to a service center is avoided.

There are two main ways for upgrading the existing firmware: full scale upgrade and incremental upgrade. The whole upgrading is to pack and upgrade the whole firmware, the upgrade pack is usually large, and one upgrade pack can only be adapted to one machine type; and incremental upgrading (also called as a difference mode) is realized by comparing the difference between the front version and the back version to make the difference into an upgrading packet, the upgrading packet is smaller, and one upgrading packet can only be adapted to one machine type.

The existing firmware upgrading is carried out aiming at a single machine type regardless of an incremental mode or a full-scale mode, and is based on the upgrading of the whole software system, because the software system of the mobile terminal device is usually complex and comprises an application program layer and various support layers (such as a framework layer, a system operation library layer and a kernel layer) which directly or indirectly provide various services for the application program layer, the upgrading of the whole software system needs relatively long development and test periods, and particularly when the machine type is numerous or the support layer with relatively rich functions (such as the framework layer) needs to be upgraded, the whole system needs more time to be developed, tested and verified. The release period of the application program is usually short, and it is hoped that the application program can be rapidly released to various machine types, and obviously, the firmware updating mode cannot meet the requirement of rapidly updating and releasing the application program.

In addition, the upgrade package of the existing method is usually only for one model and involves updating a plurality of partitions, the model and the partitions need to be distinguished during upgrade, whether settings in the partitions of the upgraded device and the upgrade package are consistent or not, including the size and the starting address of the partitions, needs to be strictly checked, and therefore operation is complicated and execution efficiency is low.

Disclosure of Invention

The embodiment of the application provides a method and a device for issuing an upgrade package, and aims to solve the problem that the conventional full and incremental upgrade mode cannot meet the requirement of quick update and issuance of applications. The embodiment of the application also provides a lightweight upgrading method and device, a lightweight upgrading system, and a method and device for manufacturing the lightweight upgrading package.

The application provides a method for issuing an upgrade package, which comprises the following steps:

aiming at an application program to be issued, the coupling degree of which with a system meets a preset requirement, a lightweight upgrade package is manufactured;

and sending the lightweight upgrade information to the client so that the client can acquire the lightweight upgrade package and execute corresponding upgrade operation.

Optionally, the to-be-released application program whose coupling degree with the system meets the preset requirement includes:

the application to be published of the custom library file is not used.

the method comprises the steps that a user-defined library file is used for an application program to be issued, and the user-defined library file is not integrated with a supporting layer for providing services for the application program;

the method for manufacturing the lightweight upgrade package aiming at the application program to be issued, the coupling degree of which with the system meets the preset requirement, comprises the following steps: and packaging the application program and the used custom library file together to generate a lightweight upgrade package.

Optionally, the client device includes: adopting mobile terminal equipment of an Android system; the support layer includes: and applying a framework layer.

Optionally, before sending the lightweight upgrade information to the client, the following operations are performed:

receiving an upgrade request from a client, wherein the request at least carries a lightweight upgrade version number;

judging whether a lightweight upgrade package with a version number larger than the lightweight upgrade version number exists;

and if so, executing the step of sending lightweight upgrade information to the client, wherein the lightweight upgrade information comprises the related information of the lightweight upgrade package.

Optionally, the request further carries remaining capacity information of a partition for installing the lightweight upgrade package;

when the result of judging whether the lightweight upgrade package with the version number larger than the lightweight upgrade version number exists is yes, the following operations are executed:

judging whether the residual capacity meets the requirement for installing the lightweight upgrade package;

and if so, executing the step of sending the lightweight upgrade information to the client.

Optionally, the request further carries one or a combination of the following information reported by the client: a client firmware version number and a client device model number;

the judging whether a lightweight upgrade package with a version number larger than the lightweight upgrade version number exists includes: and judging whether a lightweight upgrade packet which corresponds to the information reported by the client and has a version number larger than the version number of the lightweight upgrade exists.

Optionally, the making of the lightweight upgrade package for the to-be-released application program whose coupling degree with the system meets the preset requirement includes:

generating a directory structure which is the same as a client partition for installing the lightweight upgrade package;

copying a file to be packaged into a corresponding directory of the directory structure, wherein the file to be packaged at least comprises the application program to be issued, the coupling degree of which with the system meets the preset requirement;

and compressing and packaging the directory to obtain the lightweight upgrade package.

Optionally, after compressing and packaging the directory, performing the following operations:

and signing the compressed package, and taking the signed compressed package as the lightweight upgrade package.

Optionally, before the compressing and packaging the directory, the following operations are performed:

writing an upgrading program for executing upgrading operation on a client, and copying the upgrading program into a directory structure agreed with the client in advance;

the compressing and packaging the directory comprises: and compressing and packaging the directory containing the files to be packaged and the directory containing the upgrading program.

Optionally, the lightweight upgrade information sent to the client includes: and the address information of the lightweight upgrade package is acquired.

Correspondingly, this application still provides a device of issuing the upgrade package, includes:

the light-weight upgrading package manufacturing unit is used for manufacturing a light-weight upgrading package aiming at the application program to be issued, the coupling degree of which with the system meets the preset requirement;

and the upgrade information sending unit is used for sending the lightweight upgrade information to the client so that the client can acquire the lightweight upgrade package and execute corresponding upgrade operation.

Optionally, the apparatus includes:

an upgrade request receiving unit, configured to receive an upgrade request from a client before triggering the upgrade information sending unit, where the upgrade request at least carries a lightweight upgrade version number;

the version judging unit is used for judging whether a lightweight upgrade package with the version number larger than the lightweight upgrade version number exists or not;

the upgrade information sending unit is specifically configured to send lightweight upgrade information to a client, where the lightweight upgrade information includes related information of the lightweight upgrade package.

Optionally, the upgrade request received by the upgrade request receiving unit further carries remaining capacity information of a partition for installing the lightweight upgrade package;

the device further comprises:

and the residual capacity judging unit is used for judging whether the residual capacity meets the requirement of installing the lightweight upgrade package or not when the output of the version judging unit is yes, and triggering the upgrade information sending unit to work when the residual capacity meets the requirement.

Optionally, the upgrade request received by the upgrade request receiving unit further carries one or a combination of the following information reported by the client: a client firmware version number and a client device model number;

the version judging unit is specifically configured to judge whether a lightweight upgrade package exists, where the lightweight upgrade package corresponds to the information reported by the client and has a version number greater than the lightweight upgrade version number.

Optionally, the lightweight upgrade package making unit includes:

the directory structure generation subunit is used for generating a directory structure which is the same as the directory structure of the client partition for installing the lightweight upgrade package;

the file replication sub unit is used for replicating the files to be packaged into corresponding directories of the directory structure, and the files to be packaged at least comprise the application programs to be issued, the coupling degree of which with the system meets the preset requirement;

and the compression and packing subunit is used for compressing and packing the directory to obtain the lightweight upgrade package.

Optionally, the lightweight upgrade package making unit further includes:

and the compressed package signing subunit is used for signing the compressed package after the compressed package subunit completes the compressed package operation, and taking the signed compressed package as the lightweight upgrade package.

Optionally, the lightweight upgrade package making unit further includes:

the upgrading program replication subunit is used for compiling an upgrading program for executing upgrading operation at the client before triggering the compression and packaging subunit, and replicating the upgrading program into a directory structure agreed with the client in advance;

the compression packaging subunit is specifically configured to compress and package a directory containing files to be packaged and a directory containing the upgrade program.

Optionally, the lightweight upgrade information sent by the upgrade information sending unit includes: and the address information of the lightweight upgrade package is acquired.

In addition, the present application also provides a lightweight upgrade method, including:

receiving lightweight upgrade information sent by a server side, and acquiring a lightweight upgrade package;

installing the lightweight upgrade package into a preset partition;

the lightweight upgrade package is generated by packaging the application program, the coupling degree of which with the system meets the preset requirement, by the server side.

Optionally, before receiving the lightweight upgrade information sent by the server, the following operations are performed:

acquiring a local lightweight upgrade version number;

and sending an upgrade request to a server, wherein the upgrade request at least carries the lightweight upgrade version number.

Optionally, before sending the upgrade request to the server, one or a combination of the following information is further obtained: firmware version number, equipment model;

the upgrade request not only carries the lightweight upgrade version number, but also carries the acquired information.

Optionally, the information carried in the upgrade request is obtained by the following method: the information is obtained by reading system attributes.

Optionally, before sending the upgrade request to the server, the following operations are performed:

calculating the residual capacity of the preset partition;

the upgrade request not only carries the lightweight upgrade version number, but also carries the residual capacity information.

Optionally, the lightweight upgrade information includes: the address information of the lightweight upgrade package is acquired;

the acquiring the lightweight upgrade package comprises: and downloading the lightweight upgrade package according to the address information.

Optionally, the installing the lightweight upgrade package into a preset partition includes:

decompressing the lightweight upgrade package;

copying an application program and a related library file in the lightweight upgrade package to a corresponding directory of the preset partition;

and updating the local lightweight upgrade version number.

Optionally, the steps of copying the application program and the related file in the lightweight upgrade package to the corresponding directory of the preset partition, and updating the lightweight upgrade version number are implemented in the following manner:

and executing an upgrading program in the lightweight upgrading packet to finish the operation.

Optionally, the method is implemented on a mobile terminal device adopting an Android system; the preset partition includes: and (5) partitioning the system.

Correspondingly, this application still provides a light weight upgrading device, includes:

the system comprises a lightweight upgrade package acquisition unit, a system management unit and a management unit, wherein the lightweight upgrade package acquisition unit is used for receiving lightweight upgrade information sent by a server and acquiring a lightweight upgrade package, and the lightweight upgrade package is generated by packaging an application program of which the coupling degree with the system meets a preset requirement by the server;

and the light-weight upgrade package installation unit is used for installing the light-weight upgrade package into a preset subarea.

Optionally, the apparatus includes:

a lightweight version number obtaining unit, configured to obtain a local lightweight upgrade version number before the lightweight upgrade package obtaining unit operates;

and the upgrade request sending unit is used for sending an upgrade request to the server side, wherein the upgrade request at least carries the lightweight upgrade version number.

Optionally, the apparatus further comprises:

the device information acquisition unit is used for acquiring one or a combination of the following information before triggering the upgrade request sending unit to work: firmware version number, equipment model;

the upgrade request sent by the upgrade request sending unit not only carries a lightweight upgrade version number, but also carries the information acquired by the device information acquiring unit.

Optionally, the lightweight version number obtaining unit and the device information obtaining unit are specifically configured to obtain the required information by reading a system attribute.

Optionally, the apparatus further comprises:

the residual capacity calculating unit is used for calculating the residual capacity of the preset partition before triggering the upgrading request sending unit to work;

the upgrade request sent by the upgrade request sending unit not only carries a lightweight upgrade version number, but also carries the residual capacity information.

Optionally, the lightweight upgrade information received by the lightweight upgrade package obtaining unit includes: the address information of the lightweight upgrade package is acquired;

the lightweight upgrade package obtaining unit is specifically configured to receive lightweight upgrade information sent by the server side, and download the lightweight upgrade package according to address information therein.

Optionally, the lightweight upgrade package installation unit includes:

a decompression subunit, configured to decompress the lightweight upgrade package;

the file copying and installing subunit is used for copying the application program and the related library files in the lightweight upgrade package to the corresponding directory of the preset partition;

and the version number updating subunit is used for updating the local lightweight upgrade version number.

In addition, the present application also provides a lightweight upgrade system, including: the device for issuing the upgrade package according to any one of the above items, and the lightweight upgrade device according to any one of the above items.

In addition, the present application also provides a method of making a lightweight upgrade package, comprising:

copying the application program to be issued, the coupling degree of which with the system meets the preset requirement, into a corresponding directory of the directory structure;

Correspondingly, the application also provides a device for manufacturing the lightweight upgrade package, which comprises:

the directory creating unit is used for generating a directory structure which is the same as a client partition for installing the lightweight upgrade package;

the file copying unit is used for copying the application program to be issued, the coupling degree of which with the system meets the preset requirement, into a corresponding directory of the directory structure;

and the compression and packaging unit is used for compressing and packaging the directory to obtain the lightweight upgrade package.

Compared with the prior art, the method has the following advantages:

according to the technical scheme, the server side makes a lightweight upgrade package aiming at the application program to be issued, the coupling degree of which with the system meets the preset requirement, and sends lightweight upgrade information to the client side; the client side obtains the lightweight upgrade package according to the lightweight upgrade information provided by the server side, and installs the lightweight upgrade package in the preset partition, so that the application program which is coupled with the system to the extent meeting the preset requirement can be issued to the client side in the form of the lightweight upgrade package after the development and the test are finished, the whole software system does not need to be issued together, and the application program is updated and issued quickly. And because the lightweight upgrade package can adapt to multiple models, the models and the partitions do not need to be distinguished in the upgrade process of the client, the operation can be simplified, and the execution efficiency can be improved.

Drawings

FIG. 1 is a flow diagram of an embodiment of a method of publishing an upgrade package according to the present application;

FIG. 2 is a flowchart of a process for making a lightweight upgrade package according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a process for sending lightweight upgrade information based on a request/response manner according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an embodiment of an apparatus for distributing upgrade packages according to the present application;

FIG. 5 is a flow diagram of an embodiment of a lightweight upgrade method of the present application;

FIG. 6 is a flowchart of a process for obtaining lightweight upgrade information based on a request/response manner according to an embodiment of the present application;

FIG. 7 is a flowchart of a process for installing a lightweight upgrade package into a preset partition according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an embodiment of a lightweight upgrade apparatus of the present application;

FIG. 9 is a schematic diagram of an embodiment of a lightweight upgrade system of the present application;

FIG. 10 is a flow diagram of an embodiment of a method of making a lightweight upgrade package of the present application;

FIG. 11 is a schematic diagram of an embodiment of an apparatus to make a lightweight upgrade package of the present application.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit and scope of this application, and it is therefore not limited to the specific implementations disclosed below.

In the present application, there are provided a method and apparatus for issuing a lightweight upgrade package, a lightweight upgrade method and apparatus, a lightweight upgrade system, and a method and apparatus for making a lightweight upgrade package, respectively, which are described in detail in the following embodiments one by one.

Please refer to fig. 1, which is a flowchart illustrating an embodiment of a method for issuing an upgrade package according to the present application. The method is generally implemented at a server responsible for issuing upgrade packages, and comprises the following steps:

step 101, aiming at an application program to be issued, the coupling degree of which with a system meets a preset requirement, a lightweight upgrade package is manufactured.

The existing client firmware upgrading mode, no matter full upgrading or incremental upgrading, aims at the whole software system to manufacture an upgrading packet, so that the release period is long. According to the technical scheme, the light-weight upgrade package is only manufactured for the application program to be issued, the coupling degree of the application program to the system meets the preset requirement, and therefore the application program is rapidly issued.

The to-be-released application program generally refers to an application program which has completed development, debugging and other stages and can be provided for the client to be updated and used. The to-be-released application program with the coupling degree meeting the preset requirement with the system generally refers to an application program which can be updated and upgraded independently of the whole software system.

For clients using different platforms, the software system architecture may not be identical, but generally a layered architecture is adopted, including not only the application layer, but also the support layers that directly or indirectly provide various services for the application. The to-be-released application program with the coupling degree meeting the preset requirement with the system may include: the application to be published does not use the custom library file, and the application to be published uses the custom library file and the custom library file is not integrated with a support layer for providing services for the application. The following takes a client software architecture using an Android platform as an example for further explanation.

The software architecture based on the Android platform can be divided into four layers from high to low: an application layer, an application framework layer (framework), a system runtime layer and a core layer. The application program layer comprises a series of core application programs and common application programs; the application framework layer comprises functional components necessary for the running of the application, and the application can realize the required functions by using the functional components; the system operation library layer provides various subprograms and a Java core library; the core layer is a Linux kernel and provides core functions such as hardware driving, memory management, process management and the like. It can be understood that the framework layer (framework) is a support layer for directly providing support for the application program, and the system runtime library layer and the core layer are support layers for indirectly providing support for the application program.

Some application programs can realize own functions by using the framework layer components; some application programs need to realize some special functions, and the framework layer does not provide corresponding components, in this case, the application programs can define and develop corresponding libraries by themselves, and integrate the custom library files with the application programs, namely: packaging into a packet; some applications place custom library files at the framework layer, but are not integrated with the framework layer, i.e., are not compiled into a JAR package with the framework layer, but rather package the library files separately.

The three cases listed above all belong to the application program described in this embodiment, in which the coupling degree with the system meets the preset requirement, the first two cases may be considered as not being coupled with the system, and in the third case, although there is coupling with the system, the coupling degree is low, and the application program conforming to the three cases can be updated and upgraded independently of the support layer providing services to the application program, so that this step can make a lightweight upgrade package for the application program to be published meeting the above conditions, thereby implementing quick update and publication of the application program.

When the lightweight upgrade package is created, the application program to be distributed may be added to the lightweight upgrade package for the first case, and for the latter two cases, the application program to be distributed and the library file to be used may be added to the lightweight upgrade package together.

The lightweight upgrade package may only include the file to be updated, and in order to facilitate the client to perform a correct upgrade operation, this embodiment further provides a preferred embodiment: an upgrade program for performing an upgrade operation at a client is written and also added to the lightweight upgrade package.

Based on the above description, the process of making the lightweight upgrade package specifically includes the steps of generating a directory structure, copying a file to be packaged, compressing and packaging, and signing, and the following describes in detail the process of making the lightweight upgrade package by taking the example of making the lightweight upgrade package of the Android client with reference to fig. 2.

Step 101-1, generating a directory structure identical to a client partition for installing the lightweight upgrade package.

Lightweight upgrade packages are typically installed in a pre-provisioned partition of a client, which for clients employing the Android system is typically referred to as a system (system) partition. This step creates a directory structure in the local file system that is the same as the client system partition, namely: a system directory is created first, and then subdirectories of apps, frames, libs, etc. are created under the system directory.

Step 101-2, copying the file to be packaged into a corresponding directory of the directory structure, wherein the file to be packaged at least comprises the application program to be issued, and the application program which is coupled with the system and meets the preset requirement.

The application program needing to be upgraded can be copied to the app directory; if the custom library file used by the application program is placed in the framework layer in the form of an independent JAR package, the corresponding JAR package can be copied to the framework directory.

Step 101-3, writing an upgrading program for executing upgrading operation on the client, and copying the upgrading program into a directory structure agreed with the client in advance.

For a client using an Android system, an upgrade program for performing an upgrade operation is generally called a script file, also called an upgrade script, a server may include the file in a specific directory of a lightweight upgrade package, and the client acquires the file from the specific directory of the lightweight upgrade package (the same directory is agreed in advance by both parties) and executes the file, thereby completing the upgrade operation.

The upgrade script is mainly responsible for writing files in the lightweight upgrade package into the corresponding system partition and rewriting the local lightweight upgrade version number of the client. In this step, an upgrade script for realizing the above functions is written, for example: and then, creating a META-INF directory which is at the same layer as the system directory and a subdirectory com \ custom \ fota of the directory in a local file system, and copying the written upgrading script into the subdirectory.

It should be noted that, if the client needs to call other executable files or function libraries when executing the commands in the upgrade script, these executable files or function libraries may also be copied to the same directory as the upgrade script.

And step 101-4, compressing and packaging the directory.

And compressing and packaging the directory containing the application program (and the related library file) and the directory containing the upgrading program. For example, the system directory and the META-INF directory may be compressed by using a commonly used zip compression tool to generate a lightweight upgrade package update _ signed.

$zip-qry../update_unsigned.zip./

And 101-5, signing the compressed package, and taking the signed compressed package as the lightweight upgrade package.

The client device generally only performs upgrade operations on the approved lightweight upgrade package, and in order to facilitate the client to verify the source and security of the lightweight upgrade package, the lightweight upgrade package generated by compression can be signed. For example: jar or jar may be signed using a signature tool, to generate a final lightweight upgrade package update.

Thus, the lightweight upgrade package is completed through the above steps 101-1 to 101-5. It should be noted that, the above steps are taken to describe the manufacturing process of the lightweight upgrade package by taking a client side of an Android system as an example, in other implementation processes, different partition names, directory names, compression tools, signature tools, and the like may be used, and as long as the lightweight upgrade package described in this application can be manufactured and successfully upgraded at the client side, the core of this application is not deviated, and the method is within the protection scope of this application.

It can be seen from the above description that, in the prior art, it is necessary to obtain an image file capable of being installed in an upgraded manner by performing a build process on the entire software system to be upgraded (full or incremental) through a compiling tool, but in the present technical solution, only a lightweight upgrade package is manufactured in a packing and compressing manner for an application to be issued, for which the coupling degree with the system meets a preset requirement (no coupling or low coupling degree), so that the manufacturing process of the upgrade package is simplified, and the size of the obtained upgrade package is small, and the upgrade package can be adapted to various client machine types, and when the client is installed in an upgraded manner, machine types and partitions do not need to be distinguished.

In specific implementation, when an application program with a coupling degree meeting a preset requirement with a system can be released after the stages of development, debugging and the like are completed, the server side can adopt the steps to manufacture a corresponding lightweight upgrade package.

In order to facilitate distinguishing the generated light-weight upgrade packages, a light-weight upgrade version number may be generally specified for the light-weight upgrade packages, and for application scenarios with diversified firmware versions and numerous device models, a corresponding relationship between the light-weight upgrade packages, the firmware version numbers and the client device models may be established. For example: making 20150801.0111 the version number of the lightweight upgrade package, wherein the lightweight upgrade package can be applied to a plurality of firmware versions, and then establishing the corresponding relation between the lightweight upgrade version number and the plurality of firmware versions; if the lightweight upgrade package is usable across multiple client device models, but is limited in individual models, the lightweight upgrade version number may be mapped to client device models that may be applicable. Therefore, in the subsequent steps, whether the lightweight upgrade package suitable for the client exists can be searched according to the information reported by the client.

And 102, sending lightweight upgrade information to the client so that the client can acquire a lightweight upgrade package and execute corresponding upgrade operation.

After the lightweight upgrade package is created, the lightweight upgrade information may be sent to the client, for example, the lightweight upgrade information may be pushed to the client through a long connection channel with the client, or the lightweight upgrade information may be sent to the client according to an upgrade request from the client.

In specific implementation, the above two ways of sending lightweight upgrade information (push way, request/response way) are feasible, and considering that the latter can select a lightweight upgrade package suitable for client installation according to information carried in the client request and send related information, so as to ensure that the client performs a correct upgrade operation, the method is a preferred embodiment, which is further described with reference to fig. 3, and specifically includes steps 102-1 to 102-3.

Step 102-1, receiving an upgrade request from a client.

The upgrade request at least carries a lightweight upgrade version number, and the version number is the lightweight upgrade version number adopted by the client for updating last time. Considering that in an application scenario with numerous firmware versions and device models, the lightweight upgrade package may not be applicable to all firmware versions or all device models, and the upgrade request from the client may further include a client firmware version number and/or a client device model; in addition, in order to ensure that there is enough space for upgrading, the upgrade request may further include information of the remaining capacity of the partition used by the client to install the lightweight upgrade package. In this step, the above information is obtained from the upgrade request, and in step 102-2, the information reported by the client may be considered comprehensively, and a lightweight upgrade package available for the client to install is selected.

And step 102-2, judging whether a lightweight upgrade package available for the client to install exists, if so, executing step 102-3, otherwise, returning no update response to the client.

Firstly, whether a lightweight upgrade package corresponding to the firmware version number and/or the equipment model exists can be searched according to the firmware version number and/or the equipment model reported by the client; if the number of the lightweight upgrade package is found, whether the lightweight upgrade package with the version number larger than that reported by the client exists in the found lightweight upgrade package is further judged, for example: the version number of the lightweight upgrade reported by the client is 20150801.0111, and if the found version number of the lightweight upgrade package is 20150818.0111, it is determined that a new version of the lightweight upgrade package with a version number greater than the version number of the lightweight upgrade exists, the upgrade package is a lightweight upgrade package for the client to install, and step 102-3 may be continuously executed. And if the lightweight upgrade package meeting the two conditions does not exist, returning no update response to the client.

Preferably, after finding the lightweight upgrade package meeting the condition, before continuing to execute step 102-3, it may be determined whether the client has enough idle partitions to install the lightweight upgrade package according to the partition remaining capacity information reported by the client: and if the difference value of the size of the new version lightweight upgrade package and the size of the lightweight upgrade package installed by the client is larger than the residual partition capacity reported by the client, indicating that the client has enough idle partitions, continuing to execute the step 102-3, otherwise, returning no update response to the client.

It should be noted that, if the information reported by the client in the upgrade request only includes the lightweight upgrade version number, it is sufficient to directly search whether a lightweight upgrade package whose version number is greater than the lightweight upgrade version number exists in this step, and the technical solution of the present application can also be implemented.

And step 102-3, sending the lightweight upgrade information to the client so that the client can acquire the lightweight upgrade package and execute corresponding upgrade operation.

The lightweight upgrade information may directly include the lightweight upgrade package selected in step 102-2, or may include address information for downloading the lightweight upgrade package, so that the client may obtain the lightweight upgrade package according to the received lightweight upgrade information and perform a corresponding upgrade operation.

So far, throughsteps 101 to 102, an embodiment of a method for issuing an upgrade package provided by the present application is described in detail. It can be seen from the description that, since the method does not adopt the traditional way of making a full-volume or incremental upgrade package, it only makes a lightweight upgrade package for an application program which is not coupled with the system or is coupled with the system less, and sends lightweight upgrade information to the client, that is: the lightweight upgrade package aiming at the application program is independently issued without waiting for the whole software system to finish tasks such as development, debugging and the like, thereby meeting the requirement of quick change of the application program and realizing the quick update and issue of the application program.

In the foregoing embodiment, a method for issuing an upgrade package is provided, and correspondingly, the present application also provides an apparatus for issuing an upgrade package. Please refer to fig. 4, which is a schematic diagram of an embodiment of an apparatus for issuing upgrade packages according to the present application. Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for relevant points. The device embodiments described below are merely illustrative.

An apparatus for issuing an upgrade package according to this embodiment includes: a light upgradepackage making unit 401, configured to make a light upgrade package for an application to be issued, of which coupling degree with a system meets a preset requirement; an upgradeinformation sending unit 402, configured to send lightweight upgrade information to the client, so that the client obtains a lightweight upgrade package and performs a corresponding upgrade operation.

Optionally, the apparatus includes:

the device further comprises:

Optionally, the lightweight upgrade package making unit includes:

Optionally, the lightweight upgrade package making unit further includes:

In addition, the application also provides a lightweight upgrading method, which is generally implemented at a client side for updating firmware upgrading by using an upgrading package. Please refer to fig. 5, which is a flowchart illustrating an embodiment of a lightweight upgrade method provided in the present application, and parts of this embodiment that are the same as the steps of the foregoing method embodiment are not repeated, and a difference is mainly described below. The light-weight upgrading method comprises the following steps:

and step 501, receiving lightweight upgrade information sent by a server side, and acquiring a lightweight upgrade package.

The lightweight upgrade package is generated by the server side by packaging the application program whose coupling degree with the system meets the preset requirement, and for the related description, reference is made to the text in the embodiment of the method for issuing the upgrade package provided earlier, and details are not described here.

As a simple and easy implementation manner, after the server side prepares the lightweight upgrade package, the server side can directly push the lightweight upgrade information to the client side, and the client side can acquire the lightweight upgrade package according to the received lightweight upgrade information.

In a specific implementation, the client may also obtain lightweight upgrade information in a request/response manner, which is described below with reference to fig. 6 and specifically includes steps 501-1 to 501-5.

Step 501-1, obtaining a local lightweight upgrade version number, a firmware version number and an equipment model.

This step obtains the basic information of the customer premise equipment, including: a lightweight upgrade version number, a firmware version number, and a device model number. In specific implementation, the information may be obtained by using an interface function provided by the system, for example, in a client device using an Android system, attribute information of the device may be read by using a getprop () function or a similar interface, so as to obtain each piece of information.

Step 501-2, calculating the residual capacity of the preset partition for installing the lightweight upgrade package.

The installation process of the lightweight upgrade package is a process of replacing and updating information in a partition (i.e., a preset partition described in this application) where an application installed in a system manner (e.g., full upgrade or incremental upgrade) is located. In order to ensure that the upgrade operation can be completed correctly and original information in other partitions is not affected, the remaining capacity of the preset partition may be calculated and reported to the server in the subsequent step 501-3, so that the server may make a corresponding judgment. In specific implementation, the relevant information of the preset partition may be obtained through an interface provided by a system or a platform adopted by the client, and the remaining capacity is further calculated.

Taking a smart phone adopting an Android system as an example, the following partitions are generally available: preload, userdata, cache, boot, system, recovery, etc., where the usual system partition, i.e., system partition, is used to install applications and related library files in a lightweight upgrade package. The status of the file system can be obtained through the StatFs classes provided by the Android system, so that in this step, the number of free data blocks of the system partition and the size of the data blocks can be obtained through functions in the StatFs classes, and the size of a free space, namely the residual capacity information, is obtained through calculation.

And step 501-3, sending an upgrading request to the server side, wherein the request carries the information.

And sending an upgrade request to a server end responsible for providing the lightweight upgrade information, wherein the request at least carries a lightweight upgrade version number. In addition, firmware version number, device model number, and remaining capacity information of a preset partition for installing the lightweight upgrade package may also be carried.

If the lightweight upgrade package can be applied to various firmware versions, the firmware version number of the lightweight upgrade package itself may not be acquired, and the upgrade request may not carry the information (the server side does not need to perform screening); in the same way, if the lightweight upgrade package is applicable to various device models, the device model of the lightweight upgrade package itself may not be acquired, and the information may not be carried in the upgrade request. If the capacity of the preset partition of the client is large enough or the function of checking whether the residual capacity of the preset partition is sufficient is completed by the client before upgrading, the residual capacity information may not be reported to the server. These are all specific modifications of the embodiments, and are within the scope of the present application without departing from the core of the present application.

And 501-4, receiving lightweight upgrade information returned by the server side, and acquiring a lightweight upgrade package.

If the lightweight upgrade information returned by the server side contains the lightweight upgrade package, the lightweight upgrade package is directly read from the lightweight upgrade package; if the lightweight upgrade information returned by the server side contains address information for acquiring the lightweight upgrade package, the lightweight upgrade package can be downloaded according to the address information in the step.

In a specific implementation, the server may also return a no-update response (for example, because the remaining capacity of the preset partition is insufficient, the update cannot be performed), in which case thesubsequent step 502 does not need to be executed continuously.

Step 502, installing the lightweight upgrade package into a preset partition.

Installing the lightweight upgrade package obtained instep 501 into the preset partition, checking whether the signature information is correct, for example, using a jarsegner tool to verify, and if the signature information is verified, performing subsequent upgrade operations, specifically including step 502-1 to step 502-3, which is described below with reference to fig. 7.

Step 502-1, uncompress the lightweight upgrade package.

The lightweight upgrade package usually adopts a compressed package format, and can be expanded into an original directory structure by adopting a decompression tool corresponding to a compression tool adopted by the server side.

Step 502-2, copying the application programs and the related library files in the lightweight upgrade package to corresponding directories of the preset partition.

Still taking the client device adopting the Android system as an example, the application program in the system/app directory in the lightweight upgrade package can be copied to the app directory of the system partition, and the jar package file in the system/framework directory can be copied to the framework directory of the system partition.

And step 502-3, updating the local lightweight upgrade version number.

After the copy operation is completed, the local lightweight upgrade version number may be updated, for example, for a client device using an Android system, a setprop () function or a similar interface may be called, and the lightweight upgrade version number in the device attribute information stored locally is updated to the version number of the lightweight upgrade package obtained instep 501.

In particular implementations, if an upgrade program (e.g., an upgrade script-script file) is provided in the lightweight upgrade package, the functions performed by steps 502-2 and 502-3 above may generally be performed by executing the upgrade program.

So far, throughstep 501 to step 502, embodiments of the lightweight upgrade method provided by the present application are described. It can be seen from the above description that, since the lightweight upgrade package is a fast release manner for the application program, the client can shorten the waiting period for the client user to acquire and use the new version application program by acquiring the lightweight upgrade package and executing the corresponding upgrade operation, thereby improving the use experience. Moreover, the lightweight upgrade package can be adapted to various device models and is generally updated only for preset partitions, so that the models and the partitions are not needed to be distinguished in the upgrade process of the client, the operation can be simplified, and the execution efficiency can be improved.

In the embodiment, a lightweight upgrading method is provided, and correspondingly, a lightweight upgrading device is also provided. Please refer to fig. 8, which is a schematic diagram of an embodiment of a lightweight upgrade apparatus of the present application. Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for relevant points. The device embodiments described below are merely illustrative.

A lightweight upgrade device of this embodiment includes: a lightweight upgradepackage obtaining unit 801, configured to receive lightweight upgrade information sent by a server and obtain a lightweight upgrade package, where the lightweight upgrade package is generated by packaging, by the server, an application program whose coupling degree with a system meets a preset requirement; a light-weight upgradepackage installation unit 802, configured to install the light-weight upgrade package into a preset partition.

Optionally, the apparatus includes:

Optionally, the apparatus further comprises:

Optionally, the lightweight upgrade package installation unit includes:

In addition, the present application also provides a lightweight upgrade system, as shown in fig. 9, the system includes anapparatus 901 for issuing an upgrade package and alightweight upgrade apparatus 902 according to the foregoing embodiments. The lightweight upgrading device can be deployed on various client devices such as a smart phone and a tablet personal computer; the device for issuing the upgrade package is generally deployed in a server responsible for issuing the upgrade package to the client, but is not limited to the server, and may be any device capable of implementing the method for issuing the upgrade package described in this application.

For example, a lightweight upgrade device is deployed on a smartphone, and a device that issues an upgrade package is deployed on a server. The server is used for manufacturing a lightweight upgrade package aiming at an application program to be issued, the coupling degree of which with a system meets a preset requirement, sending address information of the corresponding lightweight upgrade package to a client according to an upgrade request of the client, and downloading the lightweight upgrade package and installing the lightweight upgrade package into a preset partition according to the address information by the client, so that the application program is updated and issued quickly.

The above examples are merely illustrative, and in other embodiments, different deployments and embodiments may be adopted, and it is within the scope of the present application as long as the overall function of the lightweight upgrade system described in the present application can be achieved.

In addition, the application also provides a method for manufacturing the lightweight upgrade package. Please refer to fig. 10, which is a flowchart illustrating an embodiment of a method for creating a lightweight upgrade package according to the present application, wherein the same steps as those in the two embodiments of the method are not repeated, and the following description focuses on differences. The method for manufacturing the lightweight upgrade package comprises the following steps:

step 1001, a directory structure identical to a client partition for installing the lightweight upgrade package is generated.

Step 1002, copying the application program to be issued, the coupling degree of which with the system meets the preset requirement, into a corresponding directory of the directory structure.

And if the application program to be issued meeting the preset requirement uses a custom library file, copying the custom library file to a corresponding directory of the directory structure.

And 1003, compressing and packaging the directories to obtain the lightweight upgrade package.

In the embodiment, the application also provides a device for manufacturing the lightweight upgrade package. Please refer to fig. 11, which is a schematic diagram of an embodiment of an apparatus for making a lightweight upgrade package according to the present application. Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for relevant points. The device embodiments described below are merely illustrative.

An apparatus for making a lightweight upgrade package of the present embodiment includes: adirectory creating unit 1101 configured to generate a directory structure identical to that of the client partition in which the lightweight upgrade package is installed; thefile copying unit 1102 is configured to copy an application program to be issued, which is coupled to the system to a degree that meets a preset requirement, to a corresponding directory of the directory structure; and a compressing and packaging unit 1103, configured to compress and package the directory to obtain the lightweight upgrade package.

Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

1. Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.

2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Claims

1. A method for issuing upgrade packages, comprising:

when the development and test of the application program to be issued are finished, sending lightweight upgrade information to the client side so that the client side can obtain a lightweight upgrade package and execute corresponding upgrade operation;

the application program to be released, the coupling degree of which with the system meets the preset requirement, is the application program to be released, which can be updated and upgraded independently and does not depend on the whole software system.

2. The method for issuing the upgrade package according to claim 1, wherein the to-be-issued application program coupled to the system to a degree that meets a preset requirement includes:

the application to be published of the custom library file is not used.

3. The method for issuing the upgrade package according to claim 1, wherein the to-be-issued application program coupled to the system to a degree that meets a preset requirement includes:

4. The method of issuing an upgrade package according to claim 3, wherein said client device comprises: adopting mobile terminal equipment of an Android system; the support layer includes: and applying a framework layer.

5. The method for issuing the upgrade package according to claim 1, wherein before said sending the lightweight upgrade information to the client, the following operations are performed:

6. The method for issuing the upgrade package according to claim 5, wherein the request further carries remaining capacity information of a partition for installing the lightweight upgrade package;

7. The method according to claim 5, wherein the request further carries one or a combination of the following information reported by the client: a client firmware version number and a client device model number;

8. The method for issuing the upgrade package according to claim 1, wherein the making of the lightweight upgrade package for the application to be issued with the coupling degree with the system meeting the preset requirement comprises:

9. The method of claim 8, wherein after the catalog is compressed and packaged, performing the following operations:

10. The method of claim 8, wherein before said compressing and packaging said directory, performing the following operations:

11. The method for issuing the upgrade package according to any one of claims 1 to 10, wherein the lightweight upgrade information sent to the client includes: and the address information of the lightweight upgrade package is acquired.

12. An apparatus for distributing upgrade packages, comprising:

the upgrade information sending unit is used for sending lightweight upgrade information to the client so that the client can acquire a lightweight upgrade package and execute corresponding upgrade operation;

13. The apparatus for issuing an upgrade package according to claim 12, comprising:

14. The apparatus for issuing an upgrade package according to claim 13, wherein the upgrade request received by the upgrade request receiving unit further carries remaining capacity information of a partition for installing a lightweight upgrade package;

the device further comprises:

15. The apparatus according to claim 13, wherein the upgrade request received by the upgrade request receiving unit further carries one or a combination of the following information reported by the client: a client firmware version number and a client device model number;

16. The apparatus for issuing an upgrade package according to claim 12, wherein said lightweight upgrade package making unit comprises:

17. The apparatus for issuing an upgrade package according to claim 16, wherein said lightweight upgrade package making unit further comprises:

18. The apparatus for issuing an upgrade package according to claim 16, wherein said lightweight upgrade package making unit further comprises:

19. The apparatus for issuing an upgrade package according to any one of claims 12 to 18, wherein the lightweight upgrade information transmitted by the upgrade information transmission unit includes: and the address information of the lightweight upgrade package is acquired.

20. A lightweight upgrade method, comprising:

installing the lightweight upgrade package into a preset partition;

the lightweight upgrade package is generated by packaging the application programs, the coupling degree of which with the system meets the preset requirement, by the server, and the application programs, the coupling degree of which with the system meets the preset requirement, are the application programs which can be updated and upgraded independently and do not depend on the whole software system.

21. The lightweight upgrade method according to claim 20, wherein the following operations are performed before the receiving of the lightweight upgrade information sent by the server side:

acquiring a local lightweight upgrade version number;

22. A lightweight upgrade method according to claim 21, wherein before sending an upgrade request to the server, one or a combination of the following information is also obtained: firmware version number, equipment model;

23. A lightweight upgrade method according to claim 21 or 22, wherein the information carried in the upgrade request is obtained as follows: the information is obtained by reading system attributes.

24. A lightweight upgrade method according to claim 21, characterized in that before sending an upgrade request to the server side, the following operations are performed:

calculating the residual capacity of the preset partition;

25. The lightweight upgrade method according to claim 20, wherein the lightweight upgrade information comprises: the address information of the lightweight upgrade package is acquired;

26. The lightweight upgrade method according to claim 20, wherein said installing the lightweight upgrade package into a preset partition comprises:

decompressing the lightweight upgrade package;

and updating the local lightweight upgrade version number.

27. The method for lightweight upgrade according to claim 26, wherein the steps of copying the application programs and related files in the lightweight upgrade package into the corresponding directories of the default partition and updating the lightweight upgrade version number are implemented as follows:

and executing the upgrading program in the lightweight upgrading package to finish the operation.

28. A lightweight upgrade method according to any of claims 21, 22, 24, 25, 26, 27, characterized in that said method is implemented on a mobile terminal device employing the Android system; the preset partition includes: and (5) partitioning the system.

29. The lightweight upgrading method according to claim 23, wherein the method is implemented on a mobile terminal device adopting an Android system; the preset partition includes: and (5) partitioning the system.

30. A lightweight upgrade apparatus, comprising:

the system comprises a lightweight upgrade package obtaining unit, a lightweight upgrade package obtaining unit and a software upgrading unit, wherein the lightweight upgrade package obtaining unit is used for receiving lightweight upgrade information sent by a server and obtaining the lightweight upgrade package, the lightweight upgrade package is generated by packaging an application program of which the coupling degree with a system meets a preset requirement, and the application program of which the coupling degree with the system meets the preset requirement refers to the application program which can be updated and upgraded independently and does not depend on the whole software system;

31. A lightweight upgrade apparatus according to claim 30, comprising:

32. The lightweight upgrade apparatus according to claim 31, further comprising:

33. The lightweight upgrade apparatus according to claim 32, wherein the lightweight version number obtaining unit and the device information obtaining unit are specifically configured to obtain the required information by reading system attributes.

34. The lightweight upgrade apparatus according to claim 31, further comprising:

35. The lightweight upgrade apparatus according to claim 30, wherein the lightweight upgrade information received by the lightweight upgrade package obtaining unit includes: the address information of the lightweight upgrade package is acquired;

36. The lightweight upgrade apparatus according to claim 30, wherein the lightweight upgrade package installation unit comprises:

37. A lightweight upgrade system, comprising: an apparatus for issuing an upgrade package as claimed in claim 12, and a lightweight upgrade apparatus as claimed in claim 30.

38. A method of making a lightweight upgrade package, comprising:

compressing and packaging the directory to obtain the lightweight upgrade package;

39. An apparatus for making a lightweight upgrade package, comprising:

the compression and packaging unit is used for compressing and packaging the directory to obtain the lightweight upgrade package;