Method for validating new software versions in redundant systems - Patent Application 20070122633

Abstract

To provide a method capable of verifying a software version and tracing back to old data and records without limit when switching software versions with almost no cost or effort. The present invention relates to a method for verifying the software version of a vehicle in a system and a computer program product including code devices suitable for carrying out the steps of the method, the system controlling the vehicle according to input data and recording output data of the vehicle, in which the software is checked on the vehicle, a side-by-side comparison of an old and a new software version, each of which is non-productive, is carried out in an inactive state of the system, and a switchover to the productive software version is carried out by transitioning the system to an active state.

Description

Technical Field

[0001] The present invention relates to a method for verifying a software version of a vehicle, and a computer program product including a code device suitable for executing steps of the method when the method is executed on a computer.

Background Art

[0002] According to Patent Document 1 below, a method for evaluating an application for controlling a process inside an automation system and a control device of such an automation system is known. The application is stored in a controller, and at least two versions thereof exist in the controller. This method includes the steps of inputting an input signal received from a process into various versions of the application, executing a task based on this input signal in the control for various versions, creating a report including a comparison of outputs from various versions of the application, and determining a version (s) not used for controlling the process based on the generated report.

[0003] The functions of software or a system are important in terms of security. Therefore, the cost of ensuring security becomes enormous by continuously developing software and systems for automatically ensuring the security of software and by the existence of multiple overlapping generations.

[0004] In such cases, to ensure this security, vehicles to which the new software is checked must be provided as needed. When a "closed-loop system," that is, a system that controls the vehicle in response to input data, is operated and checked, it is extremely difficult to go back to old data and records, and therefore, in practice, new data must be input or incorporated. This involves high costs and relatively significant effort. Typically, one attempts to record data during software development and re-simulate with the new software only if changes occur during its availability period. This works well as long as the system's response does not change. [Prior art documents] [Patent Documents]

[0005] [Patent Document 1] International Publication No. 2007 / 100292(A1) [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] The object of this invention is to provide a method for verifying software versions with minimal cost and effort, and for retrospectively accessing an unlimited number of older data and records when switching software versions. [Means for solving the problem]

[0007] This problem is solved by the subject matter of the independent patent claim. Advantageous embodiments and variations become apparent, in particular, from the dependent claims of the independent claim.

[0008] According to a first aspect of the present invention, the problem is solved by a method for verifying the software version of a vehicle in a system that controls a vehicle according to input data, subsequently records output data of the vehicle, and checks the software on the vehicle, wherein, in an inactive state of the system, a parallel comparison of an unproductive old software version and a new software version is performed, and when the system transitions to an active state, a switch to a productive software version is performed.

[0009] The concept of the present invention is to compare an old software version with a new software version when switching software versions. In this case, preferably, the ability for parallel execution of software and the comparison of multiple software paths are used to compare the old software version with the new software version.

[0010] According to a preferred embodiment of the present invention, in the first of a plurality of software paths, information obtained from recording vehicle output data is processed by an older software version.

[0011] According to a preferred embodiment of the present invention, in a second of a plurality of software paths, a new software version is applied based on vehicle input data, and in a comparison path, the differences between the old and new software versions are detected and saved. Preferably, the above application, detection, and saving are performed while the vehicle is running in an inactive state of the system. In particular, the system is installed but not activated; in other words, the system is not actually used.

[0012] When the system switches to an active state, the software components checked are preferably configured to the current version (production series status), and the system becomes available after a predetermined time interval. If an existing algorithm is used, this process can be performed quickly, within a few seconds, as it only requires reloading the neural network weights.

[0013] According to another preferred embodiment of the present invention, the system responses of older and newer software versions are matched to the responses of the vehicle's driver. This advantageously provides further input for "natural" or proper driving.

[0014] According to a second aspect of the present invention, the problem is solved by a computer program product that includes a code device suitable for performing each step of the method according to the first aspect of the present invention when the method is performed on a computer.

[0015] Advantageously, the present invention allows for the comparison of older and newer software versions on existing hardware. This is preferably performed while connected to a network, thereby checking for new scenes. This prevents "overfitting" of existing data. Furthermore, such security can be achieved by customer fleets where hardware is installed but not activated, or where the hardware is not actually being used.

[0016] Furthermore, field comparisons with known quality are directly available by comparing with known older software versions. Preferably, only the differences can be transmitted from the new software version to the old software version, thereby enabling automatic selection of critical or of interest scenes.

[0017] Thereby, it becomes possible to verify software versions with little cost and effort, and to trace back to old data and records without limitation when switching software versions.

[0018] Hereinafter, the present invention will be described in more detail with reference to the drawings using preferred embodiments.

Brief Description of the Drawings

[0019] [Figure 1] It is a diagram of a software-based implementation according to a preferred embodiment of the present invention.

Mode for Carrying Out the Invention

[0020] In a system for checking software on a vehicle, in a preferred embodiment of the present invention for verifying the software version of the vehicle, software parallel execution and comparison of multiple software paths are performed to compare an old software version with a new software version. The system controls the vehicle according to input data, and subsequently, the output data of the vehicle is recorded.

[0021] Information on the old software version is processed within the path of the control device. Based on the input data of the vehicle, a new software version is applied on another path among the multiple software paths, then differences are detected and saved in the comparison path.

[0022] In a preferred embodiment of the present invention, this is done without activating the system during vehicle operation. If the customer wishes to activate the system, the software part to be positively checked is reset to the current version, and the system is provided to the vehicle driver again after a short time.

[0023] Figure 1 is a schematic block diagram of a software-based implementation according to another preferred embodiment of the present invention. According to this preferred embodiment of the present invention, the provided unit 1 includes a processing unit (PU) 2 located on an individual chip or chip module. The processing unit 2 includes any processor unit or any computer body, which includes a control unit that performs control using software routines of a control program. The software routines are stored in a memory unit 3, also referred to as memory (MEM). Program code instructions are retrieved from MEM3 and read into the control unit of PU2 to execute individual process steps of the method according to the present invention. The processing steps of blocks 1 and 2 can be executed based on data input (DI) and can generate data output (DO). The input data DI corresponds to data or signals that are communicated and / or detected, and the output data DO corresponds to data or signals that are communicated to or to be communicated to another unit.

Claims

1. 1. A method for verifying a software version of a vehicle in a system that controls a vehicle in response to input data, records output data of the vehicle, and in which software is checked on the vehicle, comprising: A side-by-side comparison of the old and new software versions, each of which is non-productive, is performed in the inactive state of the system, and a transition to the active state of the system results in a switchover to the productive software version. A method characterized by:

2. In a first of a plurality of software passes, information obtained from the record of the output data of the vehicle is processed by an older software version.

2. The method of claim 1 .

3. In a second pass of the plurality of software passes, a new software version is applied based on the input data of the vehicle, and in a comparison pass, differences between the old software version and the new software version are detected and stored.

3. The method of claim 2.

4. The applying, detecting, and storing are performed while the vehicle is operating in the inactive state of the system.

4. The method of claim 3.

5. Upon transition of the system to the active state, the software portions to be checked are configured to their current versions; The system becomes available after a predefined time interval.

5. The method of claim 4.

6. The system responses of the old and new software versions are tailored to the responses of the vehicle's driver. The method according to any one of claims 1 to 5.

7. A computer program product including a code device, A computer program product, said code device being suitable for carrying out the method according to any one of claims 1 to 6 when said method is carried out on a computer.

Images