METHOD FOR THE TRANSPARENT REPLICATION OF A SOFTWARE COMPONENT OF A SOFTWARE SYSTEM

• US 20100192164A1
• Filed: 06/05/2008
• Published: 07/29/2010
• Est. Priority Date: 07/20/2007
• Status: Abandoned Application

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Golm, Michael, Schmitt, Klaus Jürgen, Schwarz, Konrad
• Application Number:
  US12/669,823
• Publication Number:
  US 20100192164A1
• Time in Patent Office: Days
• US Class Current: 719/319
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: G06F 11/1687 at event level, e.g. by interrupt or result of polling
• CPC Class Codes: G06F 11/187 Voting techniques
• CPC Class Codes: G06F 11/2007 using redundant communication media
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores

Abstract

In a method for the transparent replication of a software component (SWC1) of a software system (SWC1, SWC2), in particular according to the AUTOSAR standard, in a computation system with two or more processing units (VEA, VEB), the processing units (VEA, VEB) are connected to one another, by one or more communication channels (KK1, KK2), for the purpose of interchanging data. Each of the processing units (VEA, VEB) has a runtime environment (RTE) in which respective runtime environments (RTE) of the processing units (VEA, VEB), which are to be replicated, are provided with a synchronization and selection functionality (Sync, Voting).

Claims

1. A method for the transparent replication of a software component of a software system in a data processing system with two or more processing units, the method comprising the steps of:

interconnecting the processing units via one or more communication channels for the exchange of data, and

providing each of the processing units with a runtime environment in which runtime environments to be replicated for the processing units are provided with a synchronization and voting functionality.

2. The method according to claim 1, comprising the step of providing a virtual communication channel between the replicated runtime environments.

3. The method according to claim 1, wherein to implement a functionality of the software component a number of components are interconnected virtually, irrespective of the assignment of the components to the runtime environments to be replicated.

4. The method according to claim 3, wherein the components of a functionality are interconnected for exchanging data across communications interfaces comprising send and receive ports, data being fed to the receive ports on an event-driven basis or by polling.

5. The method according to claim 4, wherein reception of data at one of the receive ports triggers the initiation of code sequences which are executed on the redundant processing units.

6. The method according to claim 5, wherein the code sequences can use a runtime environment code for communicating with other components or for invoking services.

7. The method according to claim 5, wherein the code sequences use the runtime environment or environments as middleware in order to exchange data with other components or to make remote procedure calls.

8. The method according to claim 1, wherein the components are duplicated on redundant processing units and the signal processing steps are synchronized by the runtime environments of the redundant processing units.

9. The method according to claim 8, wherein runtime environment calls are performed synchronously.

10. The method according to claim 9, wherein synchronization takes place via the communication channel between the runtime environments to be replicated.

11. The method according to claim 1, wherein all the signals are fed to input ports of compositions, comprising a plurality of communicatively interconnected components, and simultaneously to the input ports of the redundant compositions.

12. The method according to claim 1, wherein prior to the outputting of a signal all the output ports are compared with the result of the redundant component and combined into a common result.

13. The method according to claim 1, wherein at the time of runtime environment generation it is determined which of the processing units has been assigned which components and which of the processing units has been assigned the associated redundant components, from which information the runtime environments determine physical synchronization paths for all the synchronization points and generate corresponding runtime environment code.

14. The method according to claim 1, wherein the replication is defined by the AUTOSAR standard.

15. A system for the transparent replication of a software component of a software system according to the AUTOSAR standard, in a data processing system comprising two or more processing units, wherein the processing units are interconnected via one or more communication channels for the exchange of data, and each of the processing units comprises a runtime environment in which runtime environments to be replicated for the processing units are provided with a synchronization and voting functionality.

16. The system according to claim 15, wherein a virtual communication channel is provided between the replicated runtime environments.

17. The system according to claim 15, wherein to implement a functionality of the software component a number of components are interconnected virtually, irrespective of the assignment of the components to the runtime environments to be replicated.

18. The system according to claim 17, wherein the components of a functionality are interconnected for exchanging data across communications interfaces comprising send and receive ports, data being fed to the receive ports on an event-driven basis or by polling.

19. The system according to claim 18, wherein reception of data at one of the receive ports triggers the initiation of code sequences which are executed on the redundant processing units.

20. The system according to claim 19, wherein the code sequences can use a runtime environment code for communicating with other components or for invoking services.