Motor Vehicle Control Device

• US 20100292867A1
• Filed: 12/19/2008
• Published: 11/18/2010
• Est. Priority Date: 12/21/2007
• Status: Abandoned Application

• Current Assignee: Opensynergy GmbH (Panasonic Holdings Corporation)
• Original Assignee: Opensynergy GmbH (Panasonic Holdings Corporation)
• Inventors: Mitschke, Robert, Sonck Thiebaut, Stefaan, Morich, Rolf, Hergenhan, André, Böhm, Frank-Peter
• Application Number:
  US12/809,511
• Publication Number:
  US 20100292867A1
• Time in Patent Office: Days
• US Class Current: 701/1
• CPC Class Codes: B60W 50/06 Improving the dynamic response of the control system, e.g. improving the speed of regulation or avoiding hunting or overshoot
• CPC Class Codes: B60W 50/14 Means for informing the driver, warning the driver or prompting a driver intervention
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

According to the invention, a motor vehicle control device is provided, comprising: a microkernel; several entities; and a software bus, via which the entities can communicate with each other and with the kernel, wherein one or more of the entities represent respectively one or more modules of the AUTOSAR base software. The present invention is based inter alia on the idea of representing the AUTOSAR architecture on a microkernel-based architecture. Thereby, the motor vehicle control device according to the invention makes it possible for example to link infotainment applications with AUTOSAR-based applications.

Claims

1. Motor vehicle control device, comprising:

a microkernel;

several entities; and

a software bus, via which the entities can communicate with each other and with the microkernel,

wherein one or more of the entities respectively represent one or more modules of the AUTOSAR base software.

2. Motor vehicle control device according to claim 1, wherein each entity is embodied as a server, in order to make access possible for the other entities to the services thereof.

3. Motor vehicle control device according to claim 1, wherein the APIs of modules of the AUTOSAR base software are represented by corresponding IPC mechanisms between the entities.

4. Motor vehicle control device according to claim 1, wherein at least one of the entities provides a time-controlled system and at least one other of the entities provides an event-controlled system.

5. Motor vehicle control device according to claim 4, wherein the time-controlled system is formed by a FlexRay bus and the event-controlled system is formed by a CAN bus.

6. Motor vehicle control device according to claim 1, wherein the modules are represented on the entities according to one of the AUTOSAR conformance classes.

7. Motor vehicle control device according to claim 1, wherein the modules of the memory stack of the AUTOSAR base software are represented by one of the entities.

8. Motor vehicle control device according to claim 1, wherein the I/O-relevant modules of the AUTOSAR base software are represented by one of the entities.

9. Motor vehicle control device according to claim 1, comprising at least one guest operating system, which is assigned to one of the entities and is thereby integrated into the motor vehicle control device.

10. Motor vehicle control device according to claim 9, wherein the guest operating system is integrated into the motor vehicle control device as a virtualized guest operating system by means of a hypervisor implemented by one of the entities.

11. Motor vehicle control device according to claim 1, wherein one or more of the entities implement the AUTOSAR operating system.

12. Motor vehicle control device according to claim 1, comprising one or more drivers that can be used in real time, which are implemented jointly or respectively through one of more of the entities.

13. Motor vehicle control device according to claim 1, wherein one or more of the entities implement automotive infotainment services.

14. Motor vehicle control device according to claim 1, wherein one or more of the entities provide a MOST, Ethernet, Bluetooth and/or USB interface.

15. Tool for the representation of modules of the AUTOSAR base software on the entities of a motor vehicle control device according to one of the preceding claims, comprising:

means for determining how the modules of the AUTOSAR base software are to be represented on the entities;

means for the production of IPC interfaces of the entities; and

means for the production of the bus and of a base software scheduler module.

16. Motor vehicle control device, comprising software for controlling a plurality of applications, wherein the software has the following layers:

an application layer with the plurality of applications;

a base software layer with a first plurality of AUTOSAR-based base services and a second plurality of AUTOSAR-independent base services, to carry out the applications;

an adaption layer with at least a first run time environment, which is assigned to the first plurality of base services, and a second run time environment, which is assigned to the second plurality of base services, wherein the adaption layer connects the application layer with the base software layer; and

an operating system layer with a microkernel.

17. Motor vehicle control device according to claim 16, wherein the run time environments for communication with each other are embodied via IPC mechanisms of the microkernel.

18. Motor vehicle control device according to claim 17, wherein a first part of the applications is assigned to the first run time environment, and a second part of the applications is assigned to the second run time environment, and wherein the applications can communicate with each other via the first and second run time environments.

19. Motor vehicle control device according to claim 16, wherein the first plurality of base services is embodied for carrying out control applications which can be used in real time.

20. Motor vehicle control device according to claim 16, wherein the second plurality of base services is embodied for carrying out infotainment applications.