+

WO2006136060A1 - Procédé de mise à niveau d'un système multi-logiciel - Google Patents

Procédé de mise à niveau d'un système multi-logiciel Download PDF

Info

Publication number
WO2006136060A1
WO2006136060A1 PCT/CN2005/000921 CN2005000921W WO2006136060A1 WO 2006136060 A1 WO2006136060 A1 WO 2006136060A1 CN 2005000921 W CN2005000921 W CN 2005000921W WO 2006136060 A1 WO2006136060 A1 WO 2006136060A1
Authority
WO
WIPO (PCT)
Prior art keywords
version
software
upgrade
information
module
Prior art date
Application number
PCT/CN2005/000921
Other languages
English (en)
Chinese (zh)
Inventor
Yong Hong Guo
Xu Tong Fan
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to PCT/CN2005/000921 priority Critical patent/WO2006136060A1/fr
Publication of WO2006136060A1 publication Critical patent/WO2006136060A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates

Definitions

  • 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.
  • the multimedia technology in the prior art is developing rapidly, and the technology of the multimedia terminal product is also rapidly updated.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a method for upgrading a 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:
  • 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;
  • 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;
  • the upgrade module completes the upgrade function according to the version description file and the local version information file on the upgrade server.
  • step d) further comprises:
  • the upgrade module acquires the release specification file from the upgrade server;
  • the upgrade module parses the version description file, and obtains an upgrade list
  • 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.
  • step d2) further includes:
  • step d2) further includes:
  • 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 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 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. .
  • 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.
  • Figure 1 is a schematic view of an upgrade apparatus of the method of the present invention
  • FIG. 2 is a schematic structural diagram of a version management module of the method of the present invention.
  • FIG. 3 is a schematic flow chart of an upgrade process of the method of the present invention. detailed description
  • the upgrading apparatus of the method of the present invention 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 specifically includes:
  • 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.
  • 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.
  • 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.
  • the version management module collects version information of each software in the storage module.
  • software in the storage module can be non-executable software, stand-alone executable software, and 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.
  • the version management module proactively obtains version information by pre-agreed.
  • 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.
  • 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.
  • 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 module first obtains a release notes file from the upgrade server.
  • 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.
  • the upgrade module performs software upgrades one by one according to the upgrade list, and reports the upgrade progress in the user interface.
  • FIG. 1 shows the upgrade method of the technical solution.
  • 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.
  • 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.
  • 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.
  • 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.
  • the version management module provides the version active acquisition function.
  • the version information is actively obtained through the approximate method.
  • 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.
  • 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.
  • the software In the second step, once the software is running, it actively reports its version to the version management module.
  • 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.
  • the host software can report the version on its behalf.
  • the upgrade server provides the release notes file and various software, and puts them in a certain location on the server.
  • 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the upgrade module upgrades software by software according to the upgrade list, and reports the upgrade progress in the user interface.
  • 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.
  • 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.

Landscapes

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

Abstract

La présente invention a trait à un procédé de mise à niveau d'un système multi-logiciel qui comprend : a) un module de gestion de versions, qui définit un fichier contenant des informations sur les versions, afin de gérer de manière centralisée les informations de version de différents logiciels dans le module de stockage, b) le module de gestion des versions collecte et conserve les informations de version locales de divers logiciels dans le module de stockage, c) un serveur de mise à niveau fournit un fichier de spécification et chaque nouveau logiciel à mettre à niveau, ledit logiciel étant situé dans une position prédéterminée du serveur de mise à niveau, d) le module de mise à niveau procède à la mise à niveau en fonction du fichier de spécification de version et du fichier local d'informations de version du serveur de mise à niveau. L'invention réalise l'élasticité du procédé de mise à niveau, l'évolutivité du logiciel système. L'interface d'informations de version fournie par le module de gestion des versions est simple et pratique d'accès. Il est très facile de procéder à une requête spéciale de retour en arrière dans les versions, de mise à niveau de version spéciale et d'annulation de mise à niveau de version spéciale.
PCT/CN2005/000921 2005-06-24 2005-06-24 Procédé de mise à niveau d'un système multi-logiciel WO2006136060A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2005/000921 WO2006136060A1 (fr) 2005-06-24 2005-06-24 Procédé de mise à niveau d'un système multi-logiciel

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2005/000921 WO2006136060A1 (fr) 2005-06-24 2005-06-24 Procédé de mise à niveau d'un système multi-logiciel

Publications (1)

Publication Number Publication Date
WO2006136060A1 true WO2006136060A1 (fr) 2006-12-28

Family

ID=37570085

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/000921 WO2006136060A1 (fr) 2005-06-24 2005-06-24 Procédé de mise à niveau d'un système multi-logiciel

Country Status (1)

Country Link
WO (1) WO2006136060A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104331948A (zh) * 2014-10-28 2015-02-04 深圳市华宝电子科技有限公司 行驶记录仪升级信息发送方法、接收方法、装置及系统
CN104346844A (zh) * 2014-10-28 2015-02-11 深圳市华宝电子科技有限公司 一种行驶记录仪升级信息的调用方法及装置
CN105677409A (zh) * 2015-12-31 2016-06-15 中科创达软件股份有限公司 一种系统升级方法及装置
CN110262826A (zh) * 2019-03-05 2019-09-20 上海博泰悦臻网络技术服务有限公司 车载软件配置升级管理方法、服务端、客户端及处理端
CN110377302A (zh) * 2019-06-29 2019-10-25 苏州浪潮智能科技有限公司 一种服务器专用机型多控存储oses的升级方法及系统
CN111124462A (zh) * 2019-12-27 2020-05-08 上海闻泰电子科技有限公司 一种嵌入式多媒体卡更新方法、装置、服务器和存储介质
CN111414185A (zh) * 2020-02-28 2020-07-14 浙江吉利新能源商用车集团有限公司 一种终端升级方法、装置、终端及存储介质
CN113157297A (zh) * 2021-05-10 2021-07-23 成都特来电新能源有限公司 一种充电站设备远程升级方法及系统
CN113961386A (zh) * 2021-10-27 2022-01-21 奇瑞商用车（安徽）有限公司 一种整车软件版本自动管理方法
CN115509597A (zh) * 2022-09-29 2022-12-23 广西电网有限责任公司南宁供电局 继电保护装置软件版本核查比对方法、装置及存储介质
CN115967828A (zh) * 2022-11-17 2023-04-14 广东长虹电子有限公司 一种能够在电视机选择软件版本进行更新的方法及系统
CN116737220A (zh) * 2023-05-23 2023-09-12 广州汽车集团股份有限公司 一种域控制器软件版本信息的获取方法、装置及车辆诊断设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1288199A (zh) * 1999-09-09 2001-03-21 日本电气株式会社 响应用户引发事件更新客户的安装数据的方法
CN1525318A (zh) * 2002-12-31 2004-09-01 鸿富锦精密工业（深圳）有限公司 移动式计算设备远程程序安装系统及方法
US20040261071A1 (en) * 2003-06-23 2004-12-23 Macronix International Co., Ltd. Peer version control system
CN1581077A (zh) * 2003-08-05 2005-02-16 华为技术有限公司 一种提高接入网络的计算机的功能的方法及装置
CN1690961A (zh) * 2004-04-30 2005-11-02 鸿富锦精密工业（深圳）有限公司 客户端程序自动更新系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1288199A (zh) * 1999-09-09 2001-03-21 日本电气株式会社 响应用户引发事件更新客户的安装数据的方法
CN1525318A (zh) * 2002-12-31 2004-09-01 鸿富锦精密工业（深圳）有限公司 移动式计算设备远程程序安装系统及方法
US20040261071A1 (en) * 2003-06-23 2004-12-23 Macronix International Co., Ltd. Peer version control system
CN1581077A (zh) * 2003-08-05 2005-02-16 华为技术有限公司 一种提高接入网络的计算机的功能的方法及装置
CN1690961A (zh) * 2004-04-30 2005-11-02 鸿富锦精密工业（深圳）有限公司 客户端程序自动更新系统及方法

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104346844A (zh) * 2014-10-28 2015-02-11 深圳市华宝电子科技有限公司 一种行驶记录仪升级信息的调用方法及装置
CN104346844B (zh) * 2014-10-28 2018-04-10 深圳市华宝电子科技有限公司 一种行驶记录仪升级信息的调用方法及装置
CN104331948A (zh) * 2014-10-28 2015-02-04 深圳市华宝电子科技有限公司 行驶记录仪升级信息发送方法、接收方法、装置及系统
CN105677409A (zh) * 2015-12-31 2016-06-15 中科创达软件股份有限公司 一种系统升级方法及装置
CN110262826A (zh) * 2019-03-05 2019-09-20 上海博泰悦臻网络技术服务有限公司 车载软件配置升级管理方法、服务端、客户端及处理端
CN110377302A (zh) * 2019-06-29 2019-10-25 苏州浪潮智能科技有限公司 一种服务器专用机型多控存储oses的升级方法及系统
CN111124462A (zh) * 2019-12-27 2020-05-08 上海闻泰电子科技有限公司 一种嵌入式多媒体卡更新方法、装置、服务器和存储介质
CN111124462B (zh) * 2019-12-27 2023-06-30 上海闻泰电子科技有限公司 一种嵌入式多媒体卡更新方法、装置、服务器和存储介质
CN111414185B (zh) * 2020-02-28 2023-01-10 浙江吉利新能源商用车集团有限公司 一种终端升级方法、装置、终端及存储介质
CN111414185A (zh) * 2020-02-28 2020-07-14 浙江吉利新能源商用车集团有限公司 一种终端升级方法、装置、终端及存储介质
CN113157297A (zh) * 2021-05-10 2021-07-23 成都特来电新能源有限公司 一种充电站设备远程升级方法及系统
CN113157297B (zh) * 2021-05-10 2023-12-12 成都特来电新能源有限公司 一种充电站设备远程升级方法及系统
CN113961386A (zh) * 2021-10-27 2022-01-21 奇瑞商用车（安徽）有限公司 一种整车软件版本自动管理方法
CN115509597A (zh) * 2022-09-29 2022-12-23 广西电网有限责任公司南宁供电局 继电保护装置软件版本核查比对方法、装置及存储介质
CN115967828A (zh) * 2022-11-17 2023-04-14 广东长虹电子有限公司 一种能够在电视机选择软件版本进行更新的方法及系统
CN116737220A (zh) * 2023-05-23 2023-09-12 广州汽车集团股份有限公司 一种域控制器软件版本信息的获取方法、装置及车辆诊断设备

Similar Documents

Publication Publication Date Title
US10110506B2 (en) System and method for quota management in a cloud platform environment
JP4907876B2 (ja) ソフトウェア更新に対応するメタデータを通信するための方法
US8255362B2 (en) Methods, systems, and computer program products for provisioning software using local changesets that represent differences between software on a repository and a local system
JP4902120B2 (ja) ソフトウェア更新を配信するためのシステム及び方法
US7600021B2 (en) Delta replication of source files and packages across networked resources
US20060282480A1 (en) Methods, systems, and computer program products for provisioning software using dynamic tags to identify and process files
US8316224B2 (en) Systems and methods for tracking a history of changes associated with software packages and configuration management in a computing system
US20120233299A1 (en) Managing configurations of system management agents in a distributed environment
CN102541596A (zh) 一种操作系统升级方法及装置
WO2006136060A1 (fr) Procédé de mise à niveau d'un système multi-logiciel
US20060288055A1 (en) Methods, systems, and computer program products for provisioning software via a networked file repository in which a parent branch has a shadow associated therewith
US20060288054A1 (en) Methods, systems, and computer program products for provisioning software via a file repository in which a version string is used to identify branches of a tree structure
CN101317381A (zh) 对能力管理对象维护、对能力管理的方法、系统及终端
CN102195804A (zh) 软件自动更新方法及其系统
CN104239439A (zh) 选择性的数据库复制
WO2010145489A1 (fr) Système et procédé de mise à jour de logiciels
CN102132261A (zh) 家庭网络系统、网关装置以及固件更新方法
CN107483250A (zh) 分布式配置管理方法、装置及实现分布式配置管理的系统
CN112748949A (zh) 一种操作系统的软件包管理方法、装置、设备及存储介质
US20100070967A1 (en) Recording medium of network administration program
CN105528205A (zh) 更新控制方法和更新控制系统
CN101877655A (zh) 网络管理系统、网管服务器和方法
US9235437B2 (en) Method and integration component for integrating OSGi environments into a Service-oriented Architecture
CN107193563B (zh) 一种服务器无状态固件版本管理的方法
EP2711836B1 (fr) Système de distribution de données

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 05759560

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载