SYSTEM AND METHOD FOR EXECUTING A HIGH-RELIABILITY APPLICATION

• US 20120192017A1
• Filed: 01/20/2011
• Published: 07/26/2012
• Est. Priority Date: 01/20/2011
• Status: Active Grant

• Current Assignee: Aptiv Technologies AG (Aptiv PLC)
• Original Assignee: Delphi Technologies, Inc. (BorgWarner Incorporated)
• Inventors: KADY, MARK A., NEWMAN, TIMOTHY J.
• Granted Patent: US 8,539,283 B2
• Time in Patent Office: Days
• US Class Current: 714/51
• CPC Class Codes: G06F 11/0739 in a data processing system embedded in automotive or aircraft systems
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality

Abstract

A system for executing a high-reliability application and a third party application is provided. The system includes an application module and a second module. The application module has control logic for executing the high reliability application and the third party application. The high reliability application generates a message sequence. The application module includes a normal operating mode, a high reliability mode, and a high reliability boot. The second module is in communication with the application module, and includes a first control logic for monitoring the message sequence when the application module is operating in the normal operating mode. The second module also includes control logic for initiating the high reliability boot in the application module.

Claims

1. A system for executing a high-reliability application and a third party application, comprising:

an application module having control logic for executing the high reliability application and the third party application, the high reliability application generating a message sequence, the application module comprising;

a normal operating mode having the high-reliability application and the third party application executable;

a high reliability mode having only the high-reliability application executable; and

a high reliability boot having the application module re-booted into the high reliability mode;

a second module in communication with the application module, the second module comprising;

a first control logic for monitoring the message sequence of the application module when the application module is operating in the normal operating mode;

a second control logic for determining if the message sequence has generated an indicator that signifies that an error has occurred as the high-priority application executes; and

a third control logic for initiating the high reliability boot in the application module if the message sequence has generated the indicator.

2. The system as recited in claim 1, the second module including a fourth control logic for monitoring an external message source, the second module configurable to receive a notification message from the message source, wherein the notification message indicates that the high-reliability application is to be executed by the application module.

3. The system as recited in claim 2, wherein the message source is at least one of a vehicle bus and an airbag module.

4. The system as recited in claim 2, wherein the second module is in communication with the application module to send the notification message from the second module to the application module.

5. The system as recited in claim 2, wherein the second module includes control logic for determining if the message sequence is generated in a predetermined order and at predetermined time intervals, the indicator being generated if the message sequence is not generated in the predetermined order at predetermined time intervals.

6. The system as recited in claim 2, wherein the second module includes control logic for determining if an error code has been generated, the indicator being the error code.

7. The system as recited in claim 2, wherein the second module communicates a mode flag to the application module through a first data communication line, the mode flag being configured to instruct the application processor to re-boot into one of the normal operation mode and the high-reliability mode.

8. The system as recited in claim 7, wherein the second module communicates a reset signal to the application module through a second data communication line to initiate a change between the normal operation mode and the high-reliability mode.

9. The system as recited in claim 8, wherein the application module includes a normal boot having the application module re-booted to load both the high-reliability application and the third party application.

10. The system as recited in claim 2, wherein the high-reliability application is a notification system that notifies an emergency call center.

11. A method of executing a high-reliability application and a third party application, comprising:

providing an application module, the application module having a control logic for executing the high reliability application and the third party application;

operating the application module at a normal operating mode, the normal operating mode having the high-reliability application and the third party application executable;

monitoring the high-reliability application, the high-reliability application generating a message sequence;

determining if the message sequence has generated an indicator that signifies that an error has occurred as the high-priority application executes; and

initiating a high reliability boot in the application module if the message sequence has generated the indicator, to re-boot the application module into a high reliability mode, the high reliability mode having only the high-reliability application executable.

12. The method as recited in claim 11, including executing the high reliability application until the high reliability application is finished executing.

13. The method as recited in claim 12, including re-booting the application module back into the normal operating mode.

14. The method as recited in claim 11, including monitoring an external message source with a second module, the second module configurable to receive a notification message from the external message source, the notification message indicating that the high-reliability application is to be executed by the application module.

15. The method as recited in claim 14, including sending the notification message from the second module to the application module.

16. The method as recited in claim 14, including determining if the message sequence is generated in a predetermined order and at predetermined time intervals, the indicator being generated if the message sequence is not generated in the predetermined order at predetermined time intervals.

17. The method as recited in claim 14, including determining if an error code has been generated, the indicator being the error code.

18. The method as recited in claim 14, including communicating a mode flag to the application module through a first data communication line, the mode flag instructing the application processor to re-boot into one of the normal operation mode and the high-reliability mode.

19. A system for executing a high-reliability application and a third party application, comprising:

an application module having control logic for executing the high reliability application and the third party application, the high reliability application generating a message sequence, the application module comprising;

a normal operating mode having the high-reliability application and the third party application executable;

a high reliability mode having only the high-reliability application executable; and

a high reliability boot having the application module re-booted into the high reliability mode;

an external message source that generates a notification message indicating the high-reliability application is to be executed by the application module;

a second module in communication with the application module and the external message source, the second module comprising;

a first control logic for monitoring the message sequence of the application module when the application module is operating in the normal operating mode;

a second control logic for receiving the notification message from the external message source and sending the notification message to the application module;

a third control logic for determining if the message sequence is generated in a predetermined order at predetermined time intervals; and

a fourth control logic for initiating the high reliability boot in the application module if the message sequence is not generated in the predetermined order at predetermined time intervals.

20. The system as recited in claim 19, wherein the second module communicates a mode flag to the application module through a first data communication line, the mode flag configured to instruct the application processor to re-boot into one of the normal operation mode and the high-reliability mode, and wherein the second module is configured to communicate a reset signal to the application module through a second data communication line to initiate a change between the normal operation mode and the high-reliability mode.