Method for the installation of a program component

Translation of description of equivalent WO 2005022382 A2

A method of installing a program component

State of the art

The invention relates to a method for installing a program component according to the preamble of the main claim. It is known to perform arithmetic units so that certain program components can be retrofitted or replaced by newer versions of each program component. For this purpose it is known to check before installation whether the component to be installed is already present on the computer unit in the corresponding version to avoid unnecessary installation costs.

ADVANTAGES OF THE INVENTION

The inventive method for installation of a program component with the features of the main claim has the advantage that also the compatibility of a program component already on the computer unit

Program components are checked before entering. This unnecessary installation process is avoided because the installed software is not capable of running at a incompatibility with other program components. Moreover, it is avoided that a working version of a program component is replaced by a non-running mature version. In addition, it is ensured that the computing unit by installing the program component will continue to operate. Under compatibility is to be understood here that the present in the device and unchanged remaining software component can be run together with the program component newly installed. Two components are particularly considered mutually compatible if all its interfaces are compatible with each other respectively. Underflow ability is to understand that a previously defined functionality is provided even after the installation of a component by the computing unit yet. By installing additional program component functionality may be based on the original function Stand possibly extensive, but also impaired.

The measures specified in the dependent claims, advantageous refinements and improvements of the main claim for the installation of a program component are possible. It is particularly advantageous to determine the compatibility of two program components by ύberprüfung the compatibility of the different interfaces of the program components.

This example can be dispensed with an examination of the codes of the individual Programmlcomponenten itself. This compatibility testing is simplified.

Furthermore, it is advantageous compatibility of Programmlcomponenten by a

Compared to ennitteln of the program components associated version indicators. A comparison of two program components is thus reduced to a comparison of version indicators and thus further simplified. In particular, such a quick comparison is possible, with only a minimum required of memory. In particular, compared with a comparison in which the compatibility of the individual interfaces are reviewed for themselves, a considerable time saving is achieved. It is particularly advantageous to derive a version identifier of a program component from the interface configuration of the program component and thus assign a version identifier, depending on their Sc nittstellenkonfiguration a program component. It is also particularly advantageous to assign the individual program components lists with version indicators, from which the corresponding versions are visible, to which the respective program component is compatible. Since an update possibly future program components are not known, it is also advantageous to demand as a criterion for compatibility only, that it is sufficient if one of the two program components already included in a list of the respective other program component. The program component even has no reference to the other program component comprise more to determine compatibility. The presented method is particularly advantageous when the individual program components include a plurality of independent interfaces, the program components mutual access to the interfaces. It is furthermore advantageous to install the program to install component for exchanging an existing on the computing unit program component. The inventive installation only in the present compatibility ensures that a could be no longer available record a program originally installed component is not replaced by a program component that is not executable with the other program components. The inventive method allows it to perform a compatibility check if on the one hand a program component is replaced by a newer version, and on the other hand, if a program component is replaced with an older version.

It is also advantageous to carry out a compatibility check during the installation of application programs, which are optionally updated frequently in each case during installation.

If an installation is not carried out, as is advantageously an error message, by which a user is drawn to the installation is unsuccessful. The inventive method can be used for behebige processing units and thus for any technical equipment with butterflies. Particularly advantageous is the use of the method according to the invention in a motor vehicle having a computing unit having incorporated therein embedded systems. Since usually programs are developed faster than that

Motor vehicle is replaced, in particular a re-installation of program components with the inventive method can be performed safely without a user runs the risk that the vehicle behind does not work anymore or that z. B. at a occurring spot fault is no longer available data by a incorrect installation will be overwritten.

drawing

Embodiments of the invention are shown in the drawing and explained in more detail in the following description. Show it

1 shows a driver information device in a vehicle with different installed program components,

Figure 2a-2c program components of different versions that communicate with each other, Figure 3 shows a flow of a method for installing a

Program component on a computer unit.

Description of the embodiment

In the following the invention the example of a driver information device is explained in a vehicle. The process is accordingly applicable to any other processing units.

Figure 1 shows a computer unit 1, on the first program component 11, a second Prograrnmkomponente 12 and a third program component are 13 installed. The program components interact here in such a way that they have realized in software interfaces with the data and parameters of a program component to another program component are transferred. The individual interfaces are each run unidirectionally, wherein a plurality of individual interfaces may be provided between two program components. This variety of interfaces can be aligned overall unidirectional, but may also allow data transmission in both directions. Between the third program component 13 and the first program component 11 has a first interface 131 and a second interface 132 are provided with which data can be transferred from the third program component 13 to the first program component 11th Further, a third interface 133 is provided, can be transmitted with the data from the first program component 11 to the third program component. 13 Further, a first interface 121 is provided between the first program component 11 and the second program component 12, which serves to data from the second program component 12 to the first

Program component to transmit 11th A second interface 122 is used for data transport in the reverse direction. The program components 11, 12, 13 are processed by a processor unit, not shown in Figure 1 of the computing unit. 1

The interfaces can thereby comprise for example, function calls that require an execution of the function by the other program component has a certain set of parameters required for the execution of the function in the other program component.

The program components are stored in one of the computer unit 1 associated memory for executing the program components, which is not shown in FIG. 1 The memory may be the one hand, a magnetic memory, for. Example, a hard disk drive, but can also as a rewritable memory cell, eg., An EEPROM may be performed. Under an installation of the program components on the one hand can be understood in the memory of the computing unit a pure copying data. Moreover, it is also possible that the installed program components are integrated into an installed on the computer unit 1 operating system, ie an operating program for providing the basic functions of the computer unit. For this purpose, it is necessary that in addition to the program component system, for example, files are transmitted to the computation unit 1. FIG. Further, it is also possible that the computer unit 1 registration data is also transmitted to manage the program component.

The computation unit 1 is configured in the exemplary embodiment illustrated here, as a navigation device in a vehicle. The first program component in this case serves as an operating system for the computing unit, which still may perform other functions, the program components also stored in the computer unit 1, are not shown in FIG. 1 The second program component 12 serves for example as a Routenbereclmungsfunktion, while the third program component includes a data providing function of road map data on the one hand and multimedia data on the other. Both the Routenbereclmungsfunktion, and in the provision of data function, it is likely that this program components while using the computing unit, ie, during the life of the vehicle, change. Reasons for this could be expanded, be provided information which, for example, the tourist

Note features are enhanced. Further, it is also possible that an optimized route determination algorithm is available which can determine a route to be traveled either faster or as being able to integrate with the current traffic situation in the route calculation, if this was not yet the case.

Will now install such a new program component on the computer unit 1 a user, so this different installation options are available, each exclusively to a computing unit, but can also be implemented for selection. In a first embodiment, the computational unit on an air interface 2, for example, represents an interface to a data network or to a mobile network. The data of the program component are provided to the processing unit 1 via the air interface available. Further, a wireless transmission from a computer inside the vehicle, such as a so-called Bluetooth interface. Further, the arithmetic unit 1 a plug contact 3 for connection of another

On computer, from which the data can be transmitted. In a further embodiment, the computer unit 1, a disk drive 14 in which a disk with a correspondingly updated software component can be inserted to install.

During installation, it is firstly possible that a new, additional program component is installed in the computer unit. 1 For this purpose, for example, could be the third program component 13 comprise a fourth port 134, which is still open at the representation in Figure 1, to which, however, a to-install, additional program component can be added. In a preferred embodiment an existing program component, for example the second program component, replaced for Routenbereclmungsfunktion 12, by a newly installed program component during installation.

An installation of such a program component is shown in the figure. 3

Starting from an initialization step 20, the installation is started, in a determination step 21 both A version identifier of an already installed on the computer unit 1 component, as well as a version identifier of the components to be installed is determined. This version code is determined by the fact that with every change of interface configuration of each

Program component is assigned to a new version of the code. The version code is possible by a simple reading of a corresponding parameter value of each program component. Furthermore, each program component is associated with a list for each connectable with her program component having each all version indicators of compatible to the program component versions of other program component. In a subsequent first check step 22, it is checked whether the version identifier of the component being installed in the list of already existing on the computing unit component is present or if the version code existing on the machine component in the list of components to be installed is available. If just one of these two conditions are fulfilled, the compatibility of the two program components ensures each other. In this case, the method branches to a second test step 23, in which checks whether the component to install except for this first program component must still be compatible with other, already available on the computer program components. This would be the case when, according to the

Exemplary embodiment of Figure 1, the first program component would replace 11 with a newer version, as this interacts with both the second, and the third program component 12. 13 In this case, the method branches back to the determination step 21 and it is performed the same comparison between the features to install component and the other, already available on the computer program component. There are no more to be tested program components, the method branches to an installation step 24, in which the program component to be installed is transferred to the memory of the computer unit 1, the existing there Program component is either overwritten, but at least taken out of the execution of the program.

If it is determined in the first test step 22 that the component to install compatible is not for an already existing in the computer unit 1 component, branching to a termination step 25 and there is a display 4 or via a loudspeaker 5 of the processing unit 1, an acoustic and / or visual warning signal is output to a user. It is pointed out that an installation is not done. Preferably also informed which software version is required for installation.

Should any installation be more extensive, it may be necessary to install certain components in a predetermined sequence so that always exist only mutually compatible program components on the computing unit. If now for example the first and the second program component 11, 12 are replaced, 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, as appropriate, the newly installed second program component to the on the computing unit existing first program component 11 may not be compatible.

In the Figures 2a, 2b and 2c various examples of an update of the first and second program component 11, 12 are shown. 2a shows the first program component and the second component of the Program on the first and the second interface 121, 122 are connected. is in this case the first and second

Program component 11, 12 respectively associated with the version code. 1 The first program component 11 has a version code list 6, in all versions of the second program component are stored, which are compatible with the current version of the first program component 11th In the present embodiment here, this is only the version identifier 1 of the second

Program components. Likewise, the second program component 12 a corresponding version identifier list 7, in those ratios version of the first program component are stored 11 to which the second program component 12 is compatible with the version code. 1 This is here also only the version code. 1 2b shows a more recent version 110 of the first program component 11 and a more recent version 120 of the second program component 12 is now displayed. The program components differ in that the first interface 121 is replaced by a newer interface 123rd The two interfaces can differ in that respect to the first Scl ittstelle 121, an additional parameter of the new first program component 110 is provided for processing by the new second program component 120, for example. The new first program component 110 is replaced so that the version code 2, as well as the new second program component 120. In one version, code list 60 of the new first

Program component 110 is merely contain the version identifier 2, while in the version code list 70 of the new second program component 120 the version indicators are included. 1 and 2 If, starting attempts of the configuration according to the figure 2b, the new second program component to replace 120 by the second program component 12 in the original execution, when comparing the version code lists an incompatibility is detected. Because the version identifier list of the second program component 12 is only the version code 1 exists but the new second program component 110 has the version figure 2. In the version code list 60 of these new first program component 110 also only the version figure 2, however, is stored. Since the other component can be found in either version code lists, an installation will be terminated.

If, however, tried to starting to replace the configuration according to FIG 2a, the second program component 12 by the new second program component 120, it would be possible, as in the version code list 70, the version identifier 1 is present. Based on the configuration in Figure 2a, an exchange of the second program component 12 by the new second program component 120 would be possible. A corresponding configuration is shown in Figure 2c. By the reference numeral 121 'is hereby the interface of the first component 11 referred to the new second program component 120th This could for example be realized by the first program component 11 is not provided, additional parameters will be set to either a default value or is completely ignored. Optionally, it would also be possible by the configuration in Figure 2b also to the configuration in Figure 2c to arrive. Optionally, a Users are still warned against installing warning that a more recent version is to be replaced by an older version of a Program component.

For a comparison, it is therefore sufficient to compare the contents of the version code lists 6, 60, 7, 70 with the version indicators of the other program component.

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 for example to check the compatibility of programs on various computing units which are connected to each other and in which at least is to take place on a processing unit an installation accordingly.

Besides being used for verification at an end user, it is also possible during manufacturing to verify the functionality of the system in that the erfrndungsgemäße stallationsverfahren is considered in the initial installation of software on a device, and compatibility as a on the system existing operating system will be reviewed.