WO2006136060A1

WO2006136060A1 - Multi-software system upgrading method

Info

Publication number: WO2006136060A1
Application number: PCT/CN2005/000921
Authority: WO
Inventors: Yong Hong Guo; Xu Tong Fan
Original assignee: Zte Corporation
Priority date: 2005-06-24
Filing date: 2005-06-24
Publication date: 2006-12-28

Abstract

A multi-software system upgrading method of the present invention comprises: a) a version management module sets a version information file storing version information, for centralized managing the version information of various software in the storage module; b) the version management module collects and stores the local version information of various software in the storage module; c) an upgrading server provides a version specification file and every new version software to be upgraded, said software located in a predetermination position of the upgrading server; d) the upgrading module realizes the upgrading function based on the version specification file and the local version information file in the upgrading server. The present invention realizes elasticity of upgrade process, expandability of system function software. The version information interface provided by the version management module is simply, is convenient for accessing. It is very easily to realize the special request of the version backspacing, the special version upgrading, and the special version un-upgrading.

Description

A method for upgrading multiple software systems Technical Field ■

The invention relates to a method for separately upgrading a plurality of softwares in a software system, in particular to a method for upgrading multiple softwares in a software system of a multimedia terminal product. Background technique

The multimedia technology in the prior art is developing rapidly, and the technology of the multimedia terminal product is also rapidly updated. For the terminal product that has been released to the user, 'such as the set-top box terminal system, it is necessary to involve the function update and upgrade.

There are two ways to upgrade existing multimedia terminal products:

The first upgrade method divides the software system into multiple parts. When upgrading, separately obtain the version of each part of the software, and then go to the upgrade server to query the updated version of the apricot, and decide whether each part of the software needs to be downloaded. upgrade. The disadvantages of this method are: You must know which software parts are in advance, and get the versions one by one. It is not convenient to add new software in the middle, and it is not scalable. For the version rollback, Lang upgrades from the high version to the lower version. _ and specific version upgrade, that is, only for a specific version upgrade, other versions are not difficult to meet the upgrade requirements, the upgrade process is not flexible.

Another upgrade method is to provide the entire software system as a whole with only one version number. When the system is upgraded, the latest software version is obtained directly from the server, replaced as a whole, and the upgrade is completed. The disadvantage of this method is that when the software system of the product needs to be changed only in one part, the total version number will be changed. When the level is changed, only part of the software upgrade cannot be performed, and only the whole upgrade can be performed together. The upgrade process is time consuming. Not flexible.

Therefore, the prior art has drawbacks that need to be improved and developed. Summary of the invention

The object of the present invention is to overcome the problems of the non-extensible, inflexible, and inflexible upgrade methods of the prior art multi-software system, and propose an upgrade method with flexibility, scalability, and flexibility.

The technical solution of the present invention is as follows:

A method for upgrading a multi-software system, the multi-software system comprising a storage module storing multiple software, a version management module for recording the multi-software version information, and an upgrade module for upgrading operations, the method comprising:

a), the version management module is provided with a version information file for saving version information, for centrally managing version information of each software in the storage module;

1

Confirmation b), the version management module collects local version information of each software in the storage module and saves; c), an upgrade server provides a version description file and each new version of software to be upgraded through the network, and the new version software Depositing the upgrade server in a predetermined location;

d) The upgrade module completes the upgrade function according to the version description file and the local version information file on the upgrade server.

The method, wherein the step d) further comprises:

Dl), the upgrade module acquires the release specification file from the upgrade server;

D2), the upgrade module parses the version description file, and obtains an upgrade list;

D3) The upgrade module performs upgrade of the corresponding software according to the item-by-item information of the upgrade list, and reports the upgrade progress on the user interface.

The method, wherein the step d2) further includes:

D21) clearing the upgrade list, parsing each line of information in the obtained version description file one by one; d22) obtaining local information from the version management module according to each software name in the version specification file The software version number is compared with the upgrade rule. If the local version meets the upgrade rules and needs to be upgraded, add a message to the upgrade list.

The method, wherein the step d2) further includes:

D23), for the software that has the backup upgrade request, the upgrade module obtains the software from the corresponding location of the upgrade server through the network and saves the file to the local temporary path, and performs version verification and check on it, and if the check passes, approves the Software upgrade, replace the old version; Apricot, give up the upgrade of the software; For software without backup upgrade requirements, . Download directly over the old version of the software, and let it report the latest version to the version management module, update the The version record in the version information file.

The method of checking is: running the new software, causing it to report the version to the version management module, and the upgrade module obtains the version from the version management module, and compares whether the version number is consistent with the version number of the upgrade server. Pass, otherwise the check does not pass.

The method, wherein the software in the storage module comprises three types: non-executable software, independent executable software, and/or accessory software.

The method, wherein the version management module provides a version setting interface, configured to update corresponding version information of the version information file according to a software name and a version number; and when the executable software is running, the interface is set to the The version management module reports its own version.

The method, wherein the version management module further provides a single version acquisition interface, configured to obtain version information of the software from the version information file according to a software name. The method, wherein the version management module further provides a version active acquisition function for actively acquiring the version information of the special software that does not have the executable attribute by using an agreed manner.

The method described, wherein, for the affiliate software, the version is reported by the host software using it.

In the method, the version description file is used to record the software name to be upgraded, the storage location of the upgrade server, the latest version information, the installation location of the terminal product, the upgrade rule, and whether the backup is upgraded. .

Compared with the existing upgrade technology for multimedia terminal products, the flexibility of the upgrade process and the scalability of the system function software are realized. The version management module provides a simple version interface and convenient access. The upgrade rule is defined on the server side. It is very easy to implement special requirements such as version rollback, specific version upgrade, and specific version not upgrade. The software parts of the method of the present invention can be independently upgraded, and the flexibility is good. When only some software is improved, Greatly improved the upgrade speed, shortened the upgrade time, reduced the redundant access to the storage device, improved the stability of the terminal product system, and extended the service life of the device. DRAWINGS

Figure 1 is a schematic view of an upgrade apparatus of the method of the present invention;

2 is a schematic structural diagram of a version management module of the method of the present invention;

3 is a schematic flow chart of an upgrade process of the method of the present invention. detailed description

Specific embodiments of the method of the present invention will be described in detail below with reference to the accompanying drawings.

The upgrading apparatus of the method of the present invention, as shown in FIG. 1, comprises four parts: a storage module, a version management module, an upgrade module, and an upgrade server.

The storage module is composed of a plurality of software components, which may be non-executable software, independent executable software, and accessory software; the storage module is an upgraded object.

The version management module centrally manages each software version in the storage module for use by the upgrade module for selection.

The upgrade module completes the upgrade function of part or all of the software in the storage module according to the upgrade server information and the local version information.

The multi-software upgrade method of the present invention, as shown in FIG. 2 and FIG. 3, specifically includes:

In the first step, the version management module provides a text file that stores version information of each software, that is, a version information file, and centrally manages version information of each software in the storage module. among them, 1. The version management module provides a version setting interface, and the version setting interface updates the corresponding version in the text file according to the software name and the version number: φ information.

2. The version management module provides a single version acquisition 0, and obtains version information of the software from the text file according to the software name.

3. The version management module provides the version active acquisition function. For special software that does not have executable attributes, the version information can be obtained actively by the agreed method.

In the second step, the version management module collects version information of each software in the storage module. There are three types of software in the storage module: it can be non-executable software, stand-alone executable software, and affiliate software. .

1. When each executable software runs, it must report its version to the version management module through the version setting interface; when a new software is newly added to the set-top box system, it must give an opportunity to report the version.

2. For an inconvenient report version of the affiliate software, the host software that uses it can report the version on its behalf; the host software here is a normal stand-alone executable software, but the affiliate software is only used by it.

3. For non-executable software, the version management module proactively obtains version information by pre-agreed.

In the third step, the upgrade server provides a version description file and each new version of the software to be upgraded. The new version of the software is stored in the predetermined location on the server as a normal file.

1. The release notes file indicates the name of each software, the location where the server is stored, the latest version information, the location where the terminal product is installed, the upgrade rules, and whether the backup is upgraded. Each line of information indicates information about a piece of software that can be expanded to multiple lines.

The upgrade rules can indicate which rules are eligible to be upgraded and what rules are met without upgrading the two parts. Two parts can be combined, and each part can also define more rules in a logical relationship. The development of reasonable upgrade rules makes it easy to implement version rollback and specific version upgrades, and specific versions without upgrades.

2. Each software is stored in the server's publishing path and is consistent with the storage location indicated in the release notes file. If you use http to publish, it will be stored in the http release path.

In the fourth step, the upgrade module completes the upgrade function according to the version description file information and the local version information on the upgrade server.

1. The upgrade module first obtains a release notes file from the upgrade server.

2. The upgrade module parses the release notes file to obtain an upgrade list.

This upgrade list is used to record which software needs to be upgraded, and the software name is recorded, stored in the server. Place location, installation location, latest version number, backup upgrade, etc. The operation steps of the upgrade list are as follows: first clearing the upgrade list; parsing each line of information in the obtained version description file one by one; obtaining the local software version number from the version management module according to the name of each software, according to the upgrade rule In contrast, if the local version meets the upgrade rules, the software needs to be upgraded, and a message is added to the upgrade list.

3. The upgrade module performs software upgrades one by one according to the upgrade list, and reports the upgrade progress in the user interface.

For software with backup upgrade requirements, obtain the software from the corresponding location of the upgrade server through the network and save it to the local temporary path. Verify and check the version, if the check is approved, approve the upgrade of the software, replace the old version; otherwise, give up the upgrade of the software. This will ensure the security of the backup upgrade. .

For software without backup upgrade requirements. After downloading, directly overwrite the old version of the software, and let it report the latest version to the version management module, updating its version record in the version management module. The following is a further detailed description of the implementation of the technical solution of the method of the present invention in a network set-top box terminal system.

It can be seen from FIG. 1 that the upgrade method of the technical solution depends on the centralized version management of the version management module, and the version information of each software is uniformly managed by the version management module, and is saved in the version information file ^ ^ . Figure 2 shows the flow chart of version management.

In the first step, the version management module provides a version information file for saving version information, and centrally manages version information of each software in the storage module.

1. The version management module provides a version setting interface that updates the corresponding version information in the text file according to the software name and version number.

2. The version management module provides a single version acquisition interface, and obtains version information of the software from the text file according to the software name.

3. The version management module provides the version active acquisition function. For special software that does not have executable attributes, the version information is actively obtained through the approximate method. For example, the boot screen logo is placed in the specific partition mtd3 of the flash. The image does not have executable attributes and is displayed by other software. You can agree on the first 16 bytes of the logo image to put the version information of the logo, and then put the image information of the logo. According to this convention, the version management module actively reads the first 16 bytes of the mtd3 partition of the flash, thereby obtaining the version information of the logo. In the second step, once the software is running, it actively reports its version to the version management module.

1. Each software runtime must report its version to the version management module through the interface. If the parameter " version" is run, only the version is logged out.

2. When a new software is added to the set-top box system, it must be run with the parameter "version", specifically reporting the version.

3. For affiliate software that is not convenient for reporting versions, the host software can report the version on its behalf. In the third step, the upgrade server provides the release notes file and various software, and puts them in a certain location on the server.

1. The release notes are used to indicate the name of each software, where it is stored on the server, the latest version information, where to install the terminal product, upgrade rules, whether to back up and upgrade, etc. Each line of information indicates information about a piece of software that can be expanded to multiple lines. The following specific examples:

AppName=VPl a er Location="vplayer. jpg" Version=l. 10

Destination= 7bin/vplayer" Backup=Yes Rules= {Y(<l. 1&>0. 3) &N (=0. 9) } The upgrade rule Rules can indicate the upgrade rule and the non-upgrade rule. The "Y" section indicates The version number of the Vplayer in the terminal product is upgraded according to the rule. The "N" part indicates that the version number of the Vplayer in the terminal product does not upgrade according to the rule.

The "Y" and "N" parts can be combined, and each part can define more rules in a logical relationship. The development of reasonable upgrade rules makes it easy to implement version rollback and specific version upgrades, and specific versions are not upgraded.

2. Each software is stored on the upgrade server and is consistent with the storage location indicated in the release notes ^^. In the fourth step, the upgrade module completes the upgrade function according to the version description file information and the local version information on the upgrade server. The upgrade flow chart is shown in Figure 3.

1. The upgrade module first obtains a release notes file from the upgrade server. The transmission process can be http, and the address and file path of the upgrade server are set by the user of the terminal product.

2. Parse the release notes file to get an upgrade list. The upgrade list is used to record which software needs to be upgraded, and records the software name, where the upgrade server is stored, the installation location, the latest version number, and whether the backup is upgraded.

First clear the upgrade list. Each line of information in the obtained version description text # is parsed one by one. According to the name of each software, obtain the local software version number from the version management module. If there is no version of the software locally, the default is 0 version, and then according to the upgrade rule, if the local version meets the upgrade rule, the software needs Upgrade to add a message to the upgrade list. This can implement software Expansion.

3. The upgrade module upgrades software by software according to the upgrade list, and reports the upgrade progress in the user interface.

For software with backup upgrade requirements, the software is saved from the corresponding location of the upgrade server to the local temporary path through the network. The new software is run with the parameter "version", which causes it to report the version to the version management module, and the upgrade module obtains its version from the version management module, and compares whether the version number is consistent with the version number claimed by the upgrade server. If they are consistent, recognize the upgrade of the software and replace the old version; otherwise, abandon the upgrade of the software. For no backup

The software required by the + level, after downloading, directly overwrite the old version of the software, and run the new software, let it report the latest version to the version management module, and update the version record.

4. After the list is empty, end the upgrade process.

After the solution of the method of the present invention is used in the network set-top box system, the versions of various types of software implement single management, and the logic is simple and clear. At the same time, the authenticity and scalability of the software version information are guaranteed. It also provides flexibility for automatic upgrades. When some software changes, the upgrade speed is greatly improved; the upgrade time is shortened, the redundant access of the flash is reduced, and the flash life is prolonged. And improve the stability of the set-top box system.

It is to be understood that the above description of the specific embodiments is intended to be illustrative and not restrictive of the scope of the invention.

Claims

Rights request

A method for upgrading a multi-software system, the multi-software system comprising a storage module storing multiple software, a version management module for recording the multi-software version information, and an upgrade module for upgrading operations, the method comprising a version management file is provided with a version information file for storing version information, for centrally managing version information of each software in the storage module;

b), the version management module collects local version information of each software in the storage module and saves; c), an upgrade server provides a version description file and each new version of software to be upgraded through the network, and the new version software Depositing the upgrade server in a predetermined location;

2. The method according to claim 1, wherein the step d) further comprises:

3. The method according to claim 2, wherein the step d2) further comprises:

4. The method according to claim 3, wherein the step d2) further comprises:

D23), for the software having the backup upgrade requirement, the upgrade module obtains the software from the corresponding location of the upgrade server through the network and saves the file to the local temporary path, and performs version verification and check on the software. If the check passes, the software is approved. Upgrade, replace the old version; otherwise, give up the upgrade of the software; for the software without backup upgrade requirements, directly overwrite the old version of the software after downloading, and let it report the latest version to the version management module, update the version information file The version in the record.

The method according to claim 4, wherein the checking method is: running the new software, causing it to report the version to the version management module, and the upgrading module obtains the version from the version management module, and compares the version. Whether the number is the same as the version number of the upgrade server. If they are consistent, the check is passed. Otherwise, the check fails.

6. The method according to claim 1, wherein the software in the storage module comprises three types: Non-executable software, stand-alone executable software, and/or affiliate software.

The method according to claim 1, wherein the version management module provides a version setting interface for updating corresponding version information of the version information file according to a software name and a version number; The version is set to report the version of the version to the version management module.

The method according to claim 1, wherein the version management module further provides a single version acquisition interface, configured to obtain version information of the software from the version information file according to a software name.

The method according to claim 1, wherein the version management module further provides a version active acquisition function for actively acquiring the version information of the special software that does not have the executable attribute by using an agreed manner.

10. The method according to claim 1, characterized in that, for the affiliated software, the version is reported by the host software using it.

The method according to claim 1, wherein the version description file is used to record each software name to be upgraded, a storage location of the upgrade server, latest version information, an installation location of the terminal product, and an upgrade rule. Whether to back up the upgrade information.