EP1665031A2 - Procede d'installation d'une composante programme - Google Patents

Procede d'installation d'une composante programme

Info

Publication number
EP1665031A2
EP1665031A2 EP04766589A EP04766589A EP1665031A2 EP 1665031 A2 EP1665031 A2 EP 1665031A2 EP 04766589 A EP04766589 A EP 04766589A EP 04766589 A EP04766589 A EP 04766589A EP 1665031 A2 EP1665031 A2 EP 1665031A2
Authority
EP
European Patent Office
Prior art keywords
program
program component
component
computing unit
version
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
EP04766589A
Other languages
German (de)
English (en)
Inventor
Erich Esders
Michael Uelschen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Robert Bosch GmbH
Original Assignee
Robert Bosch GmbH
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 Robert Bosch GmbH filed Critical Robert Bosch GmbH
Publication of EP1665031A2 publication Critical patent/EP1665031A2/fr
Ceased legal-status Critical Current

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/61—Installation

Definitions

  • the invention relates to a method for installing a program component according to the preamble of the main claim. It is known to design computing units in such a way that certain program components can be subsequently installed or replaced by newer versions of the respective program components. For this purpose, it is known to check before installation whether the component to be installed is already present in the corresponding version on the computing unit, in order to avoid unnecessary installation effort.
  • Program components is checked before entering. This avoids an unnecessary installation process, since the installed software cannot run if it is incompatible with other program components. It also prevents an executable version of a program component from being overwritten by a version that is not due to run. It also ensures that the computing unit remains functional after the program component has been installed. Compatibility is understood here to mean that the software component present in the device and remaining unchanged can run together with the newly installed program component. Two components are considered to be compatible with one another in particular if all of their interfaces are compatible with one another. Runnability is understood to mean that a previously defined functionality is still provided by the computing unit even after the installation of a component. By installing the other program components, the functionality may be more extensive, but also more limited in relation to the original functional status.
  • the measures listed in the subclaims permit advantageous developments and improvements to the method for installing a program component specified in the main claim. It is particularly advantageous to determine the compatibility of two program components by checking the compatibility of the individual interfaces of the program components.
  • Comparison of the version key figures assigned to the program components A comparison of two program components is thus traced back to a comparison of version key figures and thus further simplified. In particular, this enables a quick comparison, with only a minimum amount of RAM being required. Especially compared to a comparison in which the compatibility of the individual interfaces are checked individually, considerable time savings are achieved. It is particularly advantageous to derive a version code of a program component from the interface configuration of the program component and thus to assign a version code to a program component as a function of its interface configuration. It is also particularly advantageous to assign lists with version key figures to the individual program components, from which the corresponding versions can be seen, to which the respective program component is compatible.
  • the method according to the invention can be used for remedial computing units and thus for any technical devices with computing units. It is particularly advantageous to use the method according to the invention in a motor vehicle which has a computing unit with embedded systems incorporated therein. Because programs are usually developed faster than that
  • Motor vehicle is replaced, in particular a subsequent installation of program components with the inventive method can be carried out safely without a user running the risk that the vehicle will not work afterwards or that e.g. B.
  • data that is no longer available can be overwritten by an incorrect installation.
  • FIG. 1 shows a driver information device in a vehicle with various program components installed
  • FIG. 3 shows a sequence of a method according to the invention for installing a
  • Program component on a computing unit.
  • the invention is explained below using the example of a driver information device in a vehicle.
  • the method can accordingly be transferred to any other computing units.
  • FIG. 1 shows a computing unit 1 on which a first program component 11, a second program component 12 and a third program component 13 are installed.
  • the program components interact in such a way that they have interfaces implemented in software, in which data and parameters are transferred from one program component to another program component.
  • the individual interfaces are each unidirectional, and a large number of individual interfaces can be provided between two program components. This multitude of interfaces can be unidirectionally aligned overall, but it can also allow data transmission in both directions.
  • a first interface 131 and a second interface 132 are provided between the third program component 13 and the first program component 11, with which data can be transmitted from the third program component 13 to the first program component 11.
  • a third interface 133 is provided, with which data can be transmitted from the first program component 11 to the third program component 13. Furthermore, a first interface 121 is provided between the first program component 11 and the second program component 12, which serves to transfer data from the second program component 12 to the first
  • Transfer program component 11 A second interface 122 is used for data transport in the opposite direction.
  • the program components 11, 12, 13 are processed by a processor unit of the computing unit 1, not shown in FIG. 1.
  • the interfaces can e.g. also include function calls that require a specific parameter set for the execution of the function by the other program component, which is required for processing the function in the other program component.
  • the program components are stored in a memory assigned to the computing unit 1 for the execution of the program components, which is not shown in FIG. 1.
  • the memory can be a magnetic memory, for. B. a hard drive, but can also be used as an overwritable memory cell, e.g. B. an EEPROM.
  • an installation of the program components can be understood as a pure copying of data into the memory of the computing unit.
  • the installed program components can be integrated into an operating system installed on the computing unit 1, that is to say an operating program for providing the basic functions of the computing unit. For this it is necessary that in addition to the program component e.g. System files are transferred to the computing unit 1.
  • the computing unit 1 can be transmitted with registration data for managing the program component.
  • the computing unit 1 is designed as a navigation device in a vehicle.
  • the first program component serves in this case as an operating system for the computing unit, which can also take on further functions, the program components of which are also stored in the computing unit 1, but are not shown in FIG. 1.
  • the second program component 12 serves, for example, as a route calculation function, while the third program component contains a data provision function of road map data on the one hand and multimedia data on the other hand. Both with the route calculation function and with the data provision function, it is likely that these program components will change during the use of the computing unit, that is to say during the lifetime of the vehicle. The reasons for this could be extended data to be provided, for example the tourist
  • the computing unit has an air interface 2, which e.g. represents an interface to a data network or to a mobile radio network.
  • the data of the program component are made available to the computing unit 1 via the air interface.
  • Wireless transmission from a computer in the vehicle is also possible, e.g. via a so-called Bluetooth interface.
  • the computing unit 1 has a plug contact 3 for connecting another one
  • the computing unit 1 has a data carrier drive 14 into which a data carrier with a correspondingly updated software component can be inserted for installation.
  • the third program component 13 could have a fourth interface 134, which is still open in the illustration in FIG. 1, to which, however, a further program component to be installed can be attached.
  • an existing program component, for example the second program component, for the route calculation function 12 is replaced by a newly installed program component during installation.
  • FIG. 3 An installation of such a program component is shown in FIG. 3.
  • a version code of a component already installed on the computing unit 1 is determined.
  • This version key figure is determined by the fact that each time an interface configuration is changed, a respective
  • Program component is assigned a new version number.
  • the version code is possible by simply reading out a corresponding parameter value of the respective program component.
  • each program component is assigned a list for each program component that can be connected to it, each of which has all the version key figures of the versions of the other program component that are compatible with the program component.
  • a subsequent first test step 22 it is checked whether the version code of the component to be installed is present in the list of the component already present on the computing unit or whether the version code of the component present on the computer is present in the list of the component to be installed. If one of these two conditions is already met, the compatibility of the two program components with one another is ensured.
  • a branch is made to a second test step 23, in which it is checked whether the component to be installed must be compatible with other program components already present on the computer in addition to this first program component. This would be e.g. the case if according to
  • a branch is made to an abort step 25 and an acoustic signal is generated via a display 4 or a loudspeaker 5 of the computing unit 1 and / or an optical warning signal is output to a user. It is indicated that an installation has not been carried out. It is also preferably communicated which software version is required for an installation.
  • first and second program components 11, 12 are exchanged, it may be necessary to first install a new version of the first program component and then a new version of the second program component, since the second program component to be installed may already have to be installed on the computing unit existing first program component 11 may not be compatible.
  • FIGS. 2a, 2b and 2c show various examples of an update of the first and second program components 11, 12.
  • the first program component and the second program component are connected via the first and second interfaces 121, 122.
  • Program component 11, 12 each assigned the version number 1.
  • the first program component 11 has a version code number list 6 in which all versions of the second program component are stored which are compatible with the present version of the first program component 11. In the present embodiment, this is only version number 1 of the second
  • the second program component 12 has a corresponding version code list 7, in which those version code numbers of the first program component 11 are stored to which the second program component 12 is compatible with the version code number 1.
  • this is only version number 1.
  • a newer version 110 of the first program component 11 and a newer version 120 of the second program component 12 are now shown in FIG. 2b.
  • the program components differ in that the first interface 121 has been replaced by a newer interface 123.
  • the two interfaces can differ, for example, in that an additional parameter is provided by the new first program component 110 for processing by the new second program component 120 compared to the first interface 121.
  • the new first program component 110 thus receives the version code 2, as does the new second program component 120.
  • Program component 110 only contains the version code 2, while the version code list 70 of the new second program component 120 contains the version codes 1 and 2. If, based on the configuration according to FIG. 2b, an attempt is now made to replace the new second program component 120 with the second program component 12 in the original version, an incompatibility is found when the version code lists are compared. This is because only the version code 1 is present in the version code list of the second program component 12, but the new second program component 110 has the version code 2. However, only the version code 2 is also stored in the version code list 60 of this new first program component 110. Since the other component cannot be found in either of the two version code lists, an installation is canceled.
  • the compatibility comparison is preferably provided for devices in which the various program components are integrated into a single large program package. However, it is also possible e.g. check the compatibility of programs on different computing units that are connected to one another and in which at least one computing unit is to be installed, accordingly.

Abstract

L'invention concerne un procédé d'installation d'une composante programme dans un ordinateur. Ce procédé permet de garantir la compatibilité entre les unités logiciel et les composantes, notamment dans des systèmes intégrés pouvant être actualisés par un procédé de rechargement. Avant l'installation, on vérifie si les composantes programme à installer sont compatibles avec les composantes programme déjà présentes dans l'ordinateur. L'installation est effectuée seulement en cas de compatibilité.
EP04766589A 2003-09-02 2004-08-25 Procede d'installation d'une composante programme Ceased EP1665031A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE10340372A DE10340372A1 (de) 2003-09-02 2003-09-02 Verfahren zur Installation einer Programmkomponente
PCT/EP2004/051894 WO2005022382A2 (fr) 2003-09-02 2004-08-25 Procede d'installation d'une composante programme

Publications (1)

Publication Number Publication Date
EP1665031A2 true EP1665031A2 (fr) 2006-06-07

Family

ID=34202327

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04766589A Ceased EP1665031A2 (fr) 2003-09-02 2004-08-25 Procede d'installation d'une composante programme

Country Status (4)

Country Link
US (1) US8095926B2 (fr)
EP (1) EP1665031A2 (fr)
DE (1) DE10340372A1 (fr)
WO (1) WO2005022382A2 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7735079B1 (en) * 2005-02-04 2010-06-08 Symantec Corporation Securely hooking installations for compatibility with other applications
US7506336B1 (en) * 2005-06-29 2009-03-17 Emc Corporation System and methods for version compatibility checking
WO2007113550A1 (fr) * 2006-03-31 2007-10-11 British Telecommunications Public Limited Company Gestionnaire d'exceptions pour la mise à niveau d'objets java dans un système distribué
WO2007113533A1 (fr) * 2006-03-31 2007-10-11 British Telecommunications Public Limited Company Transfert basé sur xml et stockage local d'objets java
US9032390B2 (en) * 2008-07-29 2015-05-12 Qualcomm Incorporated Framework versioning
US8832676B2 (en) * 2009-09-30 2014-09-09 Zynga Inc. Apparatuses, methods and systems for a social networking application updater
US8631398B2 (en) * 2010-09-20 2014-01-14 Sony Corporation Method and apparatus for facilitating creation of a network interface
US20130042231A1 (en) 2011-08-10 2013-02-14 Ford Global Technologies, Llc Methods and Apparatus for Software Updating
US9342298B2 (en) * 2013-03-14 2016-05-17 Microsoft Technology Licensing, Llc Application compatibility checking in a distributed computing environment
JP7043783B2 (ja) * 2017-10-20 2022-03-30 富士フイルムビジネスイノベーション株式会社 ソフトウエア管理装置、ソフトウエア管理システム及びプログラム

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5579509A (en) 1991-02-08 1996-11-26 International Business Machines Corporation Apparatus and method for verifying compatibility of system components
DE69516634T2 (de) * 1994-11-04 2000-09-21 Canon Information Syst Inc Intelligente Wiederprogrammierung eines Flash-Speichers
US5951639A (en) * 1996-02-14 1999-09-14 Powertv, Inc. Multicast downloading of software and data modules and their compatibility requirements
JP2001067232A (ja) * 1999-08-31 2001-03-16 Hitachi Ltd ソフトウエアの配信システムおよびソフトウエアの受信端末装置
JP2001331324A (ja) 2000-05-19 2001-11-30 Sony Corp 情報処理方法および装置、ならびに、記録媒体
JP2002318692A (ja) * 2001-04-19 2002-10-31 Sony Corp インストール支援システム、インストール支援装置、インストール支援方法、インストールを支援するためのプログラムおよびそのプログラムを記録した記録媒体
US6971093B1 (en) * 2001-05-14 2005-11-29 Cisco Technology, Inc. Techniques for maintaining compatibility of a software core module and an interacting module
US7350207B2 (en) * 2001-05-25 2008-03-25 Tellabs Operations, Inc. Rule-based system and method for downloading computer software over a network
DE10158991A1 (de) * 2001-11-30 2003-06-12 Bosch Gmbh Robert Verfahren und Installation von einem Softwaremodul in einem Gerät

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2005022382A3 *

Also Published As

Publication number Publication date
WO2005022382A3 (fr) 2005-09-29
DE10340372A1 (de) 2005-03-24
WO2005022382A2 (fr) 2005-03-10
US20070234352A1 (en) 2007-10-04
US8095926B2 (en) 2012-01-10

Similar Documents

Publication Publication Date Title
DE102019109672A1 (de) Rückgängigmachung nach einem teilausfall in mehreren elektronischen steuergeräten mittels over-the-air-updates
DE112019002411T5 (de) Fahrzeuggebundene Aktualisierungseinrichtung, Aktualisierungsprozessverfahren und Aktualisierungsprozessprogramm
WO2006100078A1 (fr) Comparaison d'interfaces entre des composants logiciels
WO2012149951A1 (fr) Système destiné à réaliser un diagnostic portant sur un composant dans un véhicule
DE112012003795T5 (de) Fahrzeugnetwerksystem und Fahrzeug-Informationsverarbeitungsverfahren
DE102018103209A1 (de) Verfahren und vorrichtung zur handhabung der übereinstimmung von mehrzyklischen fahrzeugsoftwareaktualisierungen
WO2013171122A2 (fr) Appareil de commande de vehicule a fonctionnalite evolutive et procede permettant d'elargir la fonctionnalite d'un appareil de commande de vehicule
WO2019068375A1 (fr) Procédé et dispositif central de traitement de données destinés à actualiser un logiciel dans une pluralité de véhicules
WO2003003200A1 (fr) Procedes de transmission de modules logiciels
DE102015216265A1 (de) Verfahren und Teilsystem zum Installieren eines Softwareupdates in einem Fahrzeug
DE102018214999A1 (de) Vorrichtung zur Absicherung von Diagnosebefehlen an ein Steuergerät und entsprechendes Kraftfahrzeug
EP1665031A2 (fr) Procede d'installation d'une composante programme
WO2008095518A1 (fr) Utilisation d'une architecture de diagnostic distribué dans autosar
DE112020006441T5 (de) Fahrzeugsteuervorrichtung und Fahrzeugsteuerverfahren
DE102019004612A1 (de) Verfahren zum Betreiben eines Fahrzeugs mit einem Steuergerät
DE102022110251A1 (de) Ota-master, center, system, verfahren, nicht-transitorisches speichermedium und fahrzeug
DE102022113922A1 (de) Ota-master, system, verfahren, nicht-transitorisches speichermedium und fahrzeug
EP3797352B1 (fr) Procédé d'échange d'un premier code de programme exécutable et d'un deuxième code de programme exécutable et unité de commande
DE102009002898A1 (de) Verfahren zur Aktualisierung eines Steuergeräts eines Fahrzeugs
DE102009047974B4 (de) Verfahren zur Programmierung eines Steuergeräts
WO2009103728A1 (fr) Procédé et dispositif de stockage de données d’information
EP1739559A2 (fr) Traitement de résultats erronés pour un support de données portatif
DE102020006031A1 (de) Verfahren zum Erzeugen einer Softwarekomponente für eine elektronische Recheneinrichtung eines Kraftfahrzeugs, Computerprogrammprodukt, computerlesbares Speichermedium sowie kraftfahrzeugexternes Aktualisierungssystem
DE102022110824A1 (de) Ota-master, system, verfahren, nicht-transitorisches speichermedium und fahrzeug
DE102020216481A1 (de) Verfahren zum Betreiben eines Steuergeräts und Steuergerät

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060403

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE FR GB IT

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE FR GB IT

17Q First examination report despatched

Effective date: 20070226

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20100119