EP3308264A1 - Increasing the reliability of software - Google Patents
Increasing the reliability of softwareInfo
- Publication number
- EP3308264A1 EP3308264A1 EP15771525.1A EP15771525A EP3308264A1 EP 3308264 A1 EP3308264 A1 EP 3308264A1 EP 15771525 A EP15771525 A EP 15771525A EP 3308264 A1 EP3308264 A1 EP 3308264A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- software
- reliability
- patch
- pat
- trust
- 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
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/008—Reliability or availability analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/03—Indexing scheme relating to G06F21/50, monitoring users, programs or devices to maintain the integrity of platforms
- G06F2221/033—Test or assess software
Definitions
- the invention relates to methods and apparatus for increasing reliability of software by means of a patch.
- the invention relates to a method for increasing a reliability of a software by applying a patch to the software, characterized in that the application of the patches is carried out if a predefinable reliability is indicating by a patch to ⁇ overall reliability information transmission status, and by the reliable ⁇ keitsinformation an indicator of a successful increasing the reliability of the software is reproduced by applying the patches.
- An advantage of the invention is that represented by the To ⁇ verundkeitsinformation an indicator of a successful increasing the reliability of the software by applying the patches, thus also automatically be ent ⁇ eliminated if the patch to the software will be angewen- det or not. This decision can be made dependent on expected damage in case of unsuccessful software updates. Is it the software, for example, a control component, the whole
- the reliability status can be assigned a higher value than if the software is part of a controller of a local electric-vehicle charging station.
- another advantage of the invention is that in response to a caused by a failed patches of the software subsequent damage and / or adjusted by a loss of the existing software in non-execution of the patches of the predetermined reliability ⁇ status and in response to a comparison resultant ⁇ Nisses of prescribable reliability status and Zuver ⁇ transmittance information is performed patching or not.
- a particular advantage of the invention is that the reliability information is changed depending on a number of tests already carried out by other operators and / or manufacturers, and thus a risk of discus- sion.
- Patches are parts of a software, for example in the form of libraries, also called libraries, which are used instead of be ⁇ standing software parts of the current software and / or supplement existing software components.
- the reliability information is changed such that the reliability information reflects the successful increase in the reliability of the software. In this way, the reliability information reflects how successfully the patch was used or tested. Thus, a number of users can contribute to notifying users of the reliability of applying the patch.
- the reliability information is changed such that the reliability information ⁇ the non-successful increasing the Reliable ⁇ ness the software.
- the information regarding. the reliability of applying a patch also affected by unsuccessful tests.
- a size of the changes set the reliability information in response to at least one of the following parameters:
- An advantage of this embodiment of the invention is that reliability of the reliability information is strengthened.
- a magnitude of the change in the reliability information is greater in an unsuccessful increase in the reliability of the software than in a successful increase in the reliability of the software. This approach is particularly advantageous because failure to successfully increase reliability is quickly revealed by the greater change in reliability information than in the case of a successful increase, thus quickly warning of potential future application of the patch against potential risks.
- the reliability information is described by a single number or by a multi-dimensional vector space, wherein at least one predefinable configuration of a given dimension of the multidimensional vector space ner hardware component and / or a software component as ⁇ given and the software is executed on the configuration.
- the reliability information can be realized in a simple but effective manner.
- the patch can be realized by at least one of the following alternatives:
- the patch in the form of an executable code fragment in particular a library, designed and replaced in Anwen ⁇ the patch on the software a code fragment of the software by the executing code fragment;
- the patch in the form of a configuration change in particular to increase IT security, designed the software and when applying the patch a Konfigu ⁇ ration of the software to be changed by the configuration change.
- the invention can be used specifically and very effectively in various fields of application.
- the invention also relates to an apparatus for increasing a reliability of a software by using a Pat ⁇ ches the software,
- a first unit for performing the application of the patch if by a reliability information associated with the patch, a predeterminable reliability status is indicated by comparison, wherein by the reliability information an indicator for successfully increasing the reliability of the software by applying the patch is reproduced, a second unit for Determining a comparison of ⁇ ordered reliability information with the predetermined reliability status.
- the device may have a third unit, which is designed such that it contains one or more Steps of the method of the invention can be implemented and executed.
- Figure 1 shows a cascaded generation of a reliable ⁇ keitsinformation a patch with final control of the reliability information for correcting software
- 2 shows evaluation of the reliability information and reliability in a state applying an Pat ⁇ ches in different installations
- a control for a conveyor belt of a beverage filling installation is to be corrected by means of a patch PAT.
- Patches are parts of a soft ⁇ ware, for example in the form of libraries, also called libraries, which are used in place of existing software parts of the cur- rent software.
- libraries also called libraries
- a correction of the software library "Control- conveyor belt" necessary because there is a programming error for a given speed of the conveyor belt was found. Since ⁇ is creates a need for the reliability of the software would be increased SW, because the known bugs reduces reliability.
- a software manufacturer PI software SW first produced a revised library that is to be ⁇ plays in the form of a patch PAT at the bottling plant in the local control.
- the software vendor tests the patch in its software environment and finds out that the correction of the software is successful for him.
- the reliability information TRUST indicates how reliable, that is, how likely the application of the PAT patch can increase the reliability of the software. If, for example, it emerges that after the application of the patch, the software has a new error in the sequence, the reliability of the software can increase or decrease depending on the new error. Applying the patch crashes the software, reducing reliability. However, if the programming error corrected and does not light an indicator light correctly, the system can be correctly sent to Betrie ⁇ ben, so that the reliability increases, however, does not assume a highest value for the reliability.
- a low value for the reliability information means an uncertain prognosis as to whether the increase in reliability can be achieved by applying the patches to the software, and a high value for the reliability information that with a high probability the import of the patch the reliability of the Software will increase.
- the software manufacturer PI sends the patch together with the associated reliability information from him TRUST the manufacturer of the operating system P2 on which the software is to lau ⁇ fen.
- the operating system is a Linux variant.
- the operator checks whether the transmitted more to ⁇ verinkeitsinformation TRUST is equal to the reliability status defined by him. Since in the following case the TRUST> STATUS is the plant operator will update the system software with the help of the patch PAT and correct the error in the conveyor belt control.
- the software in the bottling plant has been corrected with the patch. If the correction has been carried out successfully, ie the known error has been corrected and the updated, ie patched, software of the system works otherwise error-free, then the plant operator can Further increase reliability information, so that other companies who want to correct their software with the help of the patch can get a more reliable reliability information TRUST.
- the invention can thus be used to not only by the manufacturers of individual components of a system, but also by the system operator itself, to exchange mutual Infor ⁇ mation about the reliability of patches.
- the plant operator can return the information that the software has been successfully corrected, that subsequently the plant manufacturer can send the patch with a higher, ie greater reliability information to further plant operators ,
- the patch is sent along with the associated reliability information to one or more manufacturers or operators.
- the patch is sent along with the associated reliability information to one or more manufacturers or operators.
- the associated reliability information can also be transmitted separately from the actual patch.
- the associated transmitted to ⁇ verundkeitsinformation and manufacturing 1er or operator can then decide whether it downloads the matching Patch and which records in its software.
- the respective manufacturer or operator receives only an indication that a new patch with associated reliability information is available for download on a server.
- the manufacturer or operator may first load the associated reliabil ⁇ stechniksinformation TRUST and then download the patch, depending on the height of the associated reliability information and write it into its software.
- the associated information Zuver ⁇ permeability which changes the respective operator to applying the patch, it back to the server, so that further hereinafter operator or manufacturer already access the changed assigned reliability information .
- the use of the patch and the associated reliability information does not have to be sequential according to Figure 1, but can also take place decentralized in that ready at the server, the patch and the associated Reliable ⁇ keitsinformation to download and not synchronized in time by the manufacturers or operators down - loaded and tested or can be played in the respective software ⁇ .
- the reliability information TRUST has been increased upon successfully increasing the reliability of the software within the supplier chain or the plant operator.
- the associated reliability information can also be reduced or reset to zero, so that in the Kayan ⁇ tenkette subsequent companies receive information, that the patch may not work or only partially.
- the plant manufacturer P3 can set the reliability information of TRUST to 1 and inform the previous supplier in the supplier chain so that they withdraw the patch or the software manufacturer PI revises the patch again.
- the failure to increase the reliability of the software can also be due to the fact that different configurations are used on a system.
- the reliability of the software is not clear reduced, the machine manufacturer can still Pass on the patch to its customers, however, in this case, it will reduce the associated reliability information, so that the plant operator can decide for himself whether he takes a risk for deterioration of the reliability of the software by the patch or not.
- the patch affects indeed a very critical security ⁇ complete within the control so that the plant operator is also trying with a lower associated with the patch reliability information, an update of the software with the patch.
- an increased reliability that is a higher probability of a mecanical ⁇ ches applying the patch or a lower risk that applying the patch reduces the reliability of the software after patching, with a higher value of the reliability information rated TRUST .
- a high value for the reliability information may represent a low probability of successfully increasing the reliability of the software after applying the patch, or a higher risk to the smooth operation of the software after patching.
- the procedure for using a patch with the assigned reliability information was displayed using an attachment.
- the patch can be together with the associated reliability information is first sent to a decision module DEC, wel ⁇ ches in response to each system AI, A2, A3 upstream predeterminable Zuver comekeitsstati STATUS1, STATUS2, STATUS3 can separate ⁇ ent whether for the respective plant AI, A2, A3, the software is to be corrected by the patch or not.
- the plants are AI and corrected A3 with the patch, see hooks to ⁇ location A2 not see the cross because the facility A2 a higher reliability status STATUS2 calls than the currently offered by the Zuver ⁇ permeability information TRUST Patches PAT is specified.
- a value has been exemplarily formed as reliability information for each patch.
- patches are created for applications in which the application can run on different platforms.
- a classic example is a JAVA-implemented application, where JAVA can be implemented and executed independently of the operating system as well as hardware-independent.
- the reliability information TRUST and the reliability status STATUS can each be formed in a multi-dimensional space. Each dimension within the multidimensional space can represent a specific configuration for which a particular value is formed.
- the dimensions in the present example according to FIG. 3 mean:
- Each of these dimensions is assigned a value for the reliability information, for example the dimension
- the plant operator may use the Find the appropriate dimension that matches its current configuration. This gives further IMPROVE ⁇ tion in reliability can be achieved with a box office of a patch to correct the software.
- the reliability information with one or more dimensions can be represented by means of an XML description language (XML-Extensible Markup Language).
- the invention can be carried out with the aid of a device VOR, see FIG. 4.
- the device VOR has in this case ei ⁇ ne first unit El for performing the application of the patch PAT, if by a patch PAT assigned Reli ⁇ stechniksinformation TRUST a specifiable reliability status STATUS is indicated by comparison, wherein the reliability information TRUST is an indicator of a successful Increasing the reliability of the software SW by applying the PAT patch reproduces, and a second unit E2 for determining a comparison of the associated reliability information TRUST with the specifiable STATUS reliability status.
- the device may also have a third unit E3, which is designed such that thereby one or more steps of the method according to one or more of the developments of the invention
- the units E1-E3 can be configured in software, hardware or ei ⁇ ner combination of software and hardware. Since ⁇ at the units E1-E3 can be connected via a bus with each other. Further, a processor, a memory module, input and / or task units to Erfas ⁇ sen or sending information or messages may be connected to the bus.
- the invention can be used in the industrial environment and in the private sector, for example for the maintenance of production plants in a production or of control units of a power transmission network.
Abstract
Description
Claims
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2015/070860 WO2017041860A1 (en) | 2015-09-11 | 2015-09-11 | Increasing the reliability of software |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3308264A1 true EP3308264A1 (en) | 2018-04-18 |
Family
ID=54207461
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP15771525.1A Ceased EP3308264A1 (en) | 2015-09-11 | 2015-09-11 | Increasing the reliability of software |
Country Status (3)
Country | Link |
---|---|
US (1) | US10698676B2 (en) |
EP (1) | EP3308264A1 (en) |
WO (1) | WO2017041860A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3308264A1 (en) * | 2015-09-11 | 2018-04-18 | Siemens Aktiengesellschaft | Increasing the reliability of software |
JP6935826B1 (en) * | 2020-04-30 | 2021-09-15 | ダイキン工業株式会社 | Software update method, software update system and software update program |
CN113220548B (en) * | 2021-03-25 | 2024-02-09 | 中国航天系统科学与工程研究院 | Software reliability index distribution method, medium and equipment based on reliability block diagram |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7020875B2 (en) * | 2001-08-08 | 2006-03-28 | Hewlett-Packard Development Company, L.P. | Mechanism for selecting representatives from program patch chains based on user roles |
US6954928B2 (en) * | 2001-08-08 | 2005-10-11 | Hewlett-Packard Development Company, L.P. | Method for selecting a set of patches to update a system of programs |
US7765538B2 (en) * | 2004-10-29 | 2010-07-27 | Hewlett-Packard Development Company, L.P. | Method and apparatus for determining which program patches to recommend for installation |
US8578363B2 (en) * | 2006-05-03 | 2013-11-05 | Microsoft Corporation | Differentiated installable packages |
US9038051B1 (en) * | 2006-10-31 | 2015-05-19 | Hewlett-Packard Development Company, L.P. | Selecting patch solutions based on availability of information regarding patches previously installed on user system |
US7886200B1 (en) * | 2008-03-21 | 2011-02-08 | Symantec Corporation | Measuring catastrophic failure rates in updates |
US20100058317A1 (en) * | 2008-09-02 | 2010-03-04 | Vasco Data Security, Inc. | Method for provisioning trusted software to an electronic device |
US20130055228A1 (en) * | 2011-08-29 | 2013-02-28 | Fujitsu Limited | System and Method for Installing a Patch on a Computing System |
US8812911B2 (en) * | 2012-03-16 | 2014-08-19 | Rackspace Us, Inc. | Distributed testing of a software platform |
CN103853574B (en) * | 2012-12-06 | 2015-09-16 | 腾讯科技(深圳)有限公司 | A kind of method and system of software upgrading |
US8887151B2 (en) * | 2012-12-14 | 2014-11-11 | Google Inc. | Systems and methods for managing updates to applications installed on electronic devices |
US10019255B1 (en) * | 2014-06-20 | 2018-07-10 | Amazon Technologies, Inc. | Incremental software deployment in a service environment |
EP3308264A1 (en) * | 2015-09-11 | 2018-04-18 | Siemens Aktiengesellschaft | Increasing the reliability of software |
-
2015
- 2015-09-11 EP EP15771525.1A patent/EP3308264A1/en not_active Ceased
- 2015-09-11 WO PCT/EP2015/070860 patent/WO2017041860A1/en active Application Filing
- 2015-09-11 US US15/754,302 patent/US10698676B2/en active Active
Non-Patent Citations (2)
Title |
---|
None * |
See also references of WO2017041860A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2017041860A1 (en) | 2017-03-16 |
US10698676B2 (en) | 2020-06-30 |
US20180253295A1 (en) | 2018-09-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3523703B1 (en) | Method for updating software in cloud gateways, computer program with an implementation of the method and processing unit for executing the method | |
DE102014111361A1 (en) | Method for operating a safety control and automation network with such a safety control | |
WO2017008953A1 (en) | Method and arrangement for securely interchanging configuration data for an apparatus | |
EP3355230A1 (en) | Method and apparatus for computer-assisted preparing and running of a control function | |
EP3308264A1 (en) | Increasing the reliability of software | |
WO2014106530A1 (en) | Method for loading an application consisting of a plurality of components onto a device consisting of a plurality of components | |
EP3414632A1 (en) | Method and device for monitoring data processing and transmission in a security chain of a security system | |
EP2707782B1 (en) | Method and system for providing device-specific property data for an automation device in an automation installation | |
EP3207386B1 (en) | Checking a functional module of an automation system | |
EP2770382A1 (en) | Method for commissioning an automation system | |
EP3786739A1 (en) | Comparison of a real system with a digital twin by means of data traffic analysis | |
EP3550748A1 (en) | Method for detecting data falsification in a data transfer over error-proof communication link | |
DE102007015369A1 (en) | Critical functions logical program flow monitoring method for use in measuring device of automation and processing control technique, involves storing actually lying identification symbols as predecessor signature for monitoring cycle | |
CH706968B1 (en) | Detecting faults within a circuit in generator stators. | |
DE10110949A1 (en) | Automated version analysis of software components belonging to a software application | |
EP3599525B1 (en) | Method for secure data communication on a numerically controlled machine tool | |
WO2002071223A1 (en) | Fault-tolerant computer cluster and a method for operating a cluster of this type | |
EP3811203A1 (en) | Method for updating software on a target device | |
EP3876477B1 (en) | Method for checking the current condition of electronic components | |
EP3486825A1 (en) | Method and apparatus for the computer-aided determination of a severity of a breach in integrity | |
DE102019105135A1 (en) | Method for monitoring an industrial network | |
EP3599689B1 (en) | Method for operating an electric network | |
EP3179364B1 (en) | Method and device for developing software for a control/management system of a vehicle | |
EP3557343A1 (en) | Electronic drive system and method for operating the same | |
DE102015209341A1 (en) | Agent for coordinating a distribution of at least one software unit emanating from at least one application distributor device and associated operating method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
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 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20180108 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20190207 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
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: 20220317 |