Source: http://www.google.com/patents/US7096394?dq=6,243,373
Timestamp: 2017-03-25 17:06:04
Document Index: 293445627

Matched Legal Cases: ['art.\n2', 'art.\n3', 'Application No. 196', 'Application No. 923', 'art 14', 'art 15', 'art 15', 'art 14', 'art 15', 'art 15', 'art 14', 'art 15', 'art 14', 'art 15', 'art 15', 'art 15', 'art 24', 'art 25', 'art 25', 'art 24', 'art 25', 'art 25', 'art 25', 'art 25', 'art 25', 'art 25', 'art 25', 'art 25', 'art 24', 'art 25', 'art 24', 'art 25']

Patent US7096394 - Method for protecting software programs from inadvertent execution - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA method of safeguarding program parts which are critical to safety against inadvertent execution is described. In this method, at least one program part is executed in a predetermined chronological sequence. At a certain time in the execution, a pattern is generated. At least at one later time, a check...http://www.google.com/patents/US7096394?utm_source=gb-gplus-sharePatent US7096394 - Method for protecting software programs from inadvertent executionAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS7096394 B2Publication typeGrantApplication numberUS 10/091,057Publication dateAug 22, 2006Filing dateMar 4, 2002Priority dateMar 2, 2001Fee statusPaidAlso published asDE10110050A1, US7725644, US20020174361, US20060248589Publication number091057, 10091057, US 7096394 B2, US 7096394B2, US-B2-7096394, US7096394 B2, US7096394B2InventorsMartin Hurich, Wolfgang Grimm, Harry FriedmannOriginal AssigneeRobert Bosch GmbhExport CitationBiBTeX, EndNote, RefManPatent Citations (12), Referenced by (1), Classifications (12), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetMethod for protecting software programs from inadvertent execution
US 7096394 B2Abstract
A method of safeguarding program parts which are critical to safety against inadvertent execution is described. In this method, at least one program part is executed in a predetermined chronological sequence. At a certain time in the execution, a pattern is generated. At least at one later time, a check is then performed to determine whether the pattern is present. If the pattern is not present, the execution of the respective program part is terminated. A memory device for executing such a method is also described.
1. A method of safeguarding at least one safety-critical program part against inadvertent execution in a processor, comprising:
providing a first memory sector and a second memory sector in a program memory, wherein the at least one safety-critical program part is contained in the second memory sector, and wherein at least one further program part is contained in the first memory sector, and wherein the first memory sector is configured to be executed prior to the second memory sector;
executing the at least one further program part, wherein the at least one further program part includes a routine for generating a pattern; and
at least at one point in time after the pattern is configured to be generated, checking whether the pattern is present;
wherein a program code for resetting the processor is stored in a section of the program memory corresponding to a chronological execution point prior to the safety-critical program part.
2. The method of claim 1, wherein the pattern is generated at a beginning of the execution of the at least one further program part.
3. The method of claim 1, wherein the pattern is stored in a volatile memory element.
checking an external boundary condition at the time of pattern generation and pattern checking.
5. The method of claim 4, wherein a state of a hardware component serves as the external boundary condition.
6. A method of safeguarding a safety-critical program part against inadvertent execution in a processor, comprising:
providing a first memory sector and a second memory sector in a program memory, wherein the safety-critical program part is contained in the second memory sector, and wherein at least one further program part is contained in the first memory sector, and wherein the first memory sector is configured to be executed prior to the second memory sector;
performing a check at least at one point in time to determine a presence of a pattern representing a proper sequence of execution, the pattern being configured to be generated using code that is included in the at least one further program part; and
terminating program execution if the pattern is determined to be not present, wherein a program code for resetting the processor is stored in a section of the program memory corresponding to a chronological execution point prior to the safety-critical program part.
The present invention relates to a method of safeguarding program parts which are critical to safety, and to a memory device for implementing the method.
The software used in controllers and motor vehicles, for example, is becoming increasingly more complex because of constantly rising demands made on such software. This and the increasingly differentiated boundary conditions have led to a characterization of a wide variety of operating states of the software system.
It is problematic that some of these operating states are highly incompatible with one another. If program parts which are assigned to different operating states are stored at the same memory locations, inadvertent execution of a program part in the wrong operating state may lead to a condition that is critical to safety.
One example of this is the existence of an endless loop, which may be appropriate in anticipation of an external shutdown but should never be executed in the normal program sequence. During execution of such program parts, basic monitoring mechanisms such as a hardware or software watchdog are shut down or at least rendered ineffective.
It is no longer possible today to guarantee complete avoidance of the existence of such program structures. Therefore, these program parts must be protected virtually 100% against inadvertent execution.
Methods of preventing inadvertent alteration of memory contents, in particular the contents of flash EEPROM memories are widespread.
German Published Patent Application No. 196 16 053 describes a method of operating a controller having a programmable memory device. The memory device is programmed by successive execution of a plurality of memory programming control operations.
This should largely prevent in a simple manner interference-triggered, interference-influenced deletion and/or overwriting of data stored in the programmable memory device.
This is achieved by providing a check step which determines whether all the selected individual or several memory programming control operations to be carried out by then have been executed, and by a decision step in which a decision is made, taking account the result of the check, as to whether the programming operation is to be continued as intended with the execution of additional memory programming control operations.
It is, thus, possible to ascertain at any desired time whether the control operations to be carried out by then have in fact been carried out.
European Published Patent Application No. 923 081 describes methods of writing to and erasing a flash EEPROM.
In this method, a programming voltage or deletion voltage 35 corresponds to a read voltage. To differentiate the programming or erase voltage from the read voltage, the programming or deletion algorithms are to be processed in a specific sequence using specific addresses and specific data. The programming and deletion algorithms are shifted to a volatile memory allocated logically to the flash EEPROM.
This achieves an increased security of the memory information stored in this flash EEPROM with respect to accidental overwriting or deletion.
This prevents inadvertent overwriting or deletion of stored content caused by accidental exposure of the flash EEPROM to an electromagnetic discharge, programming errors, hardware defects and/or voltage pulses.
In addition, an embodiment is also described in which the address information and data information needed for processing the programming and deletion algorithms is made available only by an external programming device.
There are no known comparable methods of protecting any desired safety-critical program parts, however.
It is the aim of the method according to the present invention to safeguard program parts, which are critical to safety, against inadvertent execution. In this method, a program having at least one program part is executed in a predetermined chronological sequence. At a certain time in the execution, a pattern is generated and a check is performed at least at one later point in time to determine whether the pattern is present. If the pattern is not present, the execution of the respective program part is terminated.
The pattern may be a single bit which is set, or a bit pattern.
The pattern is preferably generated in a volatile memory, e.g., a RAM module. This ensures that a pattern generated in a previous program run will have been deleted again after a program start.
In the method according to the present invention, it is important that in the execution of safety-critical program parts, a check is performed at least at one point in time to determine whether a pattern is present. If the pattern is not present, e.g., because the program has jumped to the safety-critical area because of a mistake in the program pointer, execution of the program part is terminated.
The memory device according to the present invention for execution of the method according to the present invention is divided into one or more sectors. A program part is stored in each sector. The program part(s) is (are) executable in a predetermined chronological sequence. The memory device according to the present invention is characterized in that an arrangement is provided for causing a pattern to be generated in execution of the program part at a certain point in time and at least one other arrangement is provided which causes a check to be performed at a later point in time to determine whether the pattern is present.
The program stored in the memory device is processed by a microprocessor.
It is advantageous for the pattern generation to be performed at the earliest possible point in time.
In addition, a program routine which causes the processor to be reset may be provided in the memory device. In the case of a defective run through the program, the program pointer skips this program routine. However, if the program pointer jumps because of an error in the program routine, the processor is reset.
Suitable data media such as EEPROMs, flash memories, as well as CD ROMs, diskettes or hard drives may be used as the memory device for executing the method according to the present invention.
FIG. 1 is a schematic diagram showing a conventional memory device.
FIG. 2 is a schematic diagram showing an embodiment of the memory device according to the present invention.
FIG. 3 is a flow chart showing the sequence of an embodiment of the method according to the present invention.
FIG. 1 shows a schematic diagram of a conventional memory device 10. Memory device 10 has a first area 11 and a second sector 12. An arrow 13 indicates the direction of execution. A first program part 14 is contained in first sector 11 and a second program part 15 is contained in second sector 12. In addition, data is stored in a data field 16 in second sector 12.
The second program part 15 which is provided in memory device 10 contain safety-critical routines and execution of these routines at a certain time (i.e., in a certain operating mode) is avoided.
First program part 14 and second program part 15 are designed so that second program part 15 is called up directly by first program part 14 or at least there is a fixed causal linkage between the two.
FIG. 1 shows a first critical area 17 and a second critical area 18. Critical areas 17, 18 include the parts of the memory into which inadvertent jumping of the program pointer could result in complete execution of safety-critical second program part 15.
Reasons for the extent of the critical area include:
1. If the program pointer jumps to first program part 14, this results directly or indirectly in further execution of second program part 15 and thus the safety-critical routines. 2. If the program pointer jumps to data field 16, this first results in execution of inoperative commands (data as op code) but it need not necessarily result in resetting of the processor. Therefore, there is the possibility that the program pointer might continue running up to the area of executable second program part 15, and thus the safety-critical routines might be executed. 3. If the program pointer jumps directly into second program part 15, this results in complete execution of the safety-critical routines. This may result in execution of an endless loop here, for example. To prevent this, the following procedure is used according to the present invention. FIG. 2 shows a memory device according to the present invention, diagramed schematically with reference number 20.
Memory device 20 according to the present invention has a first sector 21 and a second sector 22. An arrow 23 illustrates the direction of execution. A first program part 24 is provided in first area 21, and a second program part 25 is provided in second area 22. The second program part contains safety-critical routines.
In addition, second sector 22 includes a data field 26.
In first sector 21, a first arrangement 27 is provided, causing a pattern to be generated. First arrangement 27 may be, for example, a program routine which sets a bit or a bit pattern.
Accordingly, an arrangement 28 which performs a pattern check is provided in second sector 22. Second arrangement 28 may be, for example, a program routine which checks on whether the corresponding bit or bit pattern has been set.
In addition, a program routine 29 which causes a reset of the processor is also shown in second sector 22.
In the case of memory device 20 according to the present invention, measures are thus taken, as explained below, to prevent inadvertent execution of safety-critical second program part 25.
First, at the beginning of first program part 24, a pattern which is required for execution of second program part 25 is generated in the volatile RAM by first arrangement 27. If the program pointer jumps to first sector 21 behind first arrangement 27, initially this results directly or indirectly in further execution of second program part 25. However, execution of second program part 25 is terminated because of the absence of the pattern, which is ascertained via the check performed by arrangement 28. Inadvertent generation of the pattern is possible only if the program pointer jumps to the program sequence before execution of the pattern generation by first arrangement 27.
Thus, it is advantageous for the first arrangement 27 to generate the pattern at the earliest possible point in time in the program execution.
Furthermore, the command for resetting the processor is stored at the physical beginning of second sector 22 where safety-critical second program part 25 is located. If the program pointer jumps to data field 26, this first results in execution of inoperative commands (data as op code), as in the unprotected case, but then it need not necessarily result in resetting of the processor. Therefore, there is also the possibility that the program pointer will continue to run. On reaching program routine 29, the processor is then automatically reset, and further execution of safety-critical second program part 25 is prevented.
In the case of a faulty program run, the program pointer jumps out of first sector 21 into second sector 22 behind program routine 29.
In addition, if the program pointer jumps directly into second sector 22, this results in execution of the following safety-critical second program part 25 until the next stored check of the required pattern. Since no pattern has been generated at position 27 in sector 21, the execution of safety-critical second program part 25 at this position is terminated.
Fields 30 and 31 illustrate the critical area which has been reduced considerably in comparison with critical fields 17 and 18 from FIG. 1. Fields 32 and 33 show the protected area, and field 34 indicates the area protected from repeated execution.
If external boundary conditions (e.g., states of hardware components) are checked when the pattern is checked and when the pattern is generated, then it is possible to achieve 100% prevention of inadvertent execution of second program part 25 by a jump into this first sector 21.
For example, if execution of first program part 24 and second program part 25 depend on an external condition, then this condition, e.g., a voltage value, is additionally checked once again.
FIG. 3 illustrates the sequence of an embodiment of the method according to the present invention in a flow chart.
Execution of the program begins with a step 40. The program pointer jumps into first area 27.
In a step 41, a pattern is generated. First program part 24 which is stored in first sector 21 is executed. After the end of this program part, the program pointer jumps to second sector 22 in step 42.
In step 43, second program part 25 in second sector 22 is executed, and, in addition, a check is performed at various times to determine whether the pattern generated in first sector 21 has been stored in the RAM. If this is not the case, program is terminated in step 44. If there is a pattern, as is the case in an error-free program run, the program is executed further in step 45.
With the help of the method according to the present invention, the probability of inadvertent execution of the safety-critical program parts and the resulting malfunction of the controller may be reduced to a great extent, i.e., by orders of magnitude.
The method described here is suitable, above all, for preventing the execution of program parts which are critical to safety which are carried out cyclically. Cyclic execution may be prevented by storing a single check of the relevant pattern.
Program parts which are critical to safety, even given a single execution, may also be broken down into the smallest possible parts by performing repeated checks.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4000460 *Jul 1, 1974Dec 28, 1976Xerox CorporationDigital circuit module test systemUS4221176 *Jul 14, 1978Sep 9, 1980Quality Mills, Inc.Profile stitching apparatus and methodUS5591916 *Feb 10, 1993Jan 7, 1997Byrne; Frederick N.Foreign object detector for vehicles and other machineryUS5819025 *Sep 16, 1996Oct 6, 1998Texas Instruments IncorporatedMethod of testing interconnections between integrated circuits in a circuitUS5913022 *Dec 15, 1995Jun 15, 1999Schlumberger Technologies, Inc.Loading hardware pattern memory in automatic test equipment for testing circuitsUS6195776 *Nov 2, 1998Feb 27, 2001Synopsys, Inc.Method and system for transforming scan-based sequential circuits with multiple skewed capture events into combinational circuits for more efficient automatic test pattern generationUS6205407 *Feb 26, 1998Mar 20, 2001Integrated Measurement Systems, Inc.System and method for generating test program code simultaneously with data produced by ATPG or simulation pattern capture programUS6421773 *Nov 21, 1997Jul 16, 2002Advantest CorporationSequence control circuitUS6499126 *Jun 29, 2000Dec 24, 2002Advantest CorporationPattern generator and electric part testing apparatusUS6769083 *Nov 10, 1999Jul 27, 2004Advantest CorporationTest pattern generator, a testing device, and a method of generating a plurality of test patternsDE19616053A1Apr 23, 1996Oct 30, 1997Bosch Gmbh RobertVerfahren zum Betreiben eines Steuergerätes mit einer programmierbaren SpeichereinrichtungEP0923081A2Nov 16, 1998Jun 16, 1999Robert Bosch GmbhMethod for writing and/or erasing a flash EPROM* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS20100125830 *Nov 20, 2008May 20, 2010Lockheed Martin CorporationMethod of Assuring Execution for Safety Computer Code* Cited by examinerClassifications U.S. Classification714/720, 714/719, 714/718, 714/E11.178, 714/E11.144International ClassificationG06F11/28, G06F12/16, G06F11/00Cooperative ClassificationG06F11/004, G06F11/28European ClassificationG06F11/28, G06F11/00HLegal EventsDateCodeEventDescriptionJul 3, 2002ASAssignmentOwner name: ROBERT BOSCH GMBH, GERMANYFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HURICH, MARTIN;GRIMM, WOLFGANG;FRIEDMANN, HARRY;REEL/FRAME:013057/0322;SIGNING DATES FROM 20020418 TO 20020517Jul 10, 2007CCCertificate of correctionFeb 15, 2010FPAYFee paymentYear of fee payment: 4Feb 17, 2014FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services