Vehicle system, vehicle and method for operating such a vehicle system
By running the first operating system and the second operating system in parallel on the hardware layer of the vehicle system and placing the second operating system in suspended to memory operation mode, the long start time and security problems of the vehicle system are solved, and rapid Availability and safe operation effects.
Patent Information
- Application Number
- CN202010165958.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-03-13
- Filing Date
- 2020-03-11
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-03-11
AI Technical Summary
The existing vehicle system takes a long time to start, causing users to wait, and putting the entire system in suspended to memory operation mode to accelerate startup cannot guarantee safe operation, which poses a risk of error startup and memory leakage.
By running the first operating system and the second operating system in parallel on the hardware layer, the second operating system is configured to run in suspended to memory operation mode using the hypervisor, while the first operating system is shut down, only non-critical applications are placed In suspend mode, ensures security and rapid availability of critical applications.
Fast availability and safe operation of vehicle systems, reduce current consumption, and ensure robustness of critical applications and rapid start-up of non-critical applications.
Smart Images

Figure CN111767115B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a vehicle system, comprising: a hardware layer; a first operating system; a virtual machine with a second operating system, wherein the virtual machine is integrated on the hardware layer; and a hypervisor, which is configured to enable the virtual machine to run on the hardware layer, so that the first operating system and the second operating system can run in parallel on the hardware layer. The present invention also relates to a vehicle, a method for operating such a vehicle system, and a computer-readable storage medium. Background Art
[0002] Many vehicles include such a vehicle system that enables the vehicle to run a variety of different applications, such as infotainment system functions (such as audio) or navigation functions. In order to control the vehicle system, a CPU with a standard operating system, such as a Linux operating system, is run.
[0003] If the vehicle system is started up, the CPU needs a considerable amount of time, for example, to start up the Linux operating system. Therefore, after starting the vehicle, the user has to wait a long time until the desired devices have completed their commissioning process and the vehicle system is ready for use. This prevents the user from being able to immediately use the functions of the reversing camera or other important applications in the vehicle, for example. A faster startup process can be achieved by placing the entire vehicle system in the suspend-to-RAM operating mode. However, this does not guarantee a safe operating state.
[0004] DE 10 2014 215 410 A1 discloses a vehicle system of a vehicle, which includes: an on-board computer system having a first processor and a second processor, wherein the first processor runs an operating system and the second processor is connected to a vehicle control system; a computer-readable memory storing instructions executable by the first processor so as to: operate the on-board computer system in a suspended mode and place a volatile memory in standby mode when the vehicle is shut down; determine whether a restart can be completed before a selected event; and if it is determined that the restart can be completed before the selected event, restart the on-board computer system.
[0005] DE 11 20160 013 77 T5 discloses a vehicle onboard system, which comprises: a primary CPU, which is placed in the vehicle and operates with a general-purpose operating system; and peripheral devices controlled by the primary CPU, wherein the vehicle onboard system also has a secondary CPU, which operates with a real-time operating system, wherein the secondary CPU initializes the peripheral devices at the start of operation and then assigns control of the peripheral devices to the primary CPU.
[0006] DE 10 2014 224 485 A1 discloses an on-board power supply system for a vehicle, comprising a power supply and at least one scanning control device, which is configured to scan status signals of at least one other control device and / or at least one switching unit in a clocked manner with a predetermined cycle time, wherein the on-board power supply system is configured such that it can switch from a first operating state (so-called normal operating state) to a second operating state (so-called standby operating state), in which the on-board power supply system consumes less energy than in the normal operating state, and is also configured to detect status signals in the normal operating state with a shorter cycle time than in the standby operating state, wherein the scanning control device is configured such that, in the standby operating state, the cycle time is automatically changed from a first standby cycle time to a second standby cycle time by means of predetermined switching parameters.
[0007] DE 10 2012 205 301 A1 discloses a computer system structure for controlling electronic data processing in a vehicle, comprising: a computing device for performing electronic data processing; at least two virtual machines, wherein a first virtual machine of the virtual machines comprises a first operating system, and a second virtual machine of the virtual machines comprises a second operating system; and a virtual layer configured to enable the first operating system and the second operating system to run in parallel in the computing device, wherein the second operating system meets higher security requirements than the first operating system. Summary of the invention
[0008] Based on this prior art, the object of the present invention is to provide a vehicle system, a vehicle and a method which are improved with regard to the waiting time for operational readiness and safe operation.
[0009] This object is achieved by providing a vehicle system having the features of claim 1 and a vehicle having the features of claim 14. Furthermore, this object is further achieved by providing a method for operating a vehicle system having the features of claim 16. Furthermore, this object is also achieved by providing a computer-readable storage medium having the features of claim 21.
[0010] Further advantageous measures are listed in the dependent claims and can be combined with one another as desired to achieve further advantages.
[0011] The object is achieved by providing a vehicle system, the vehicle system comprising:
[0012] hardware layer, and
[0013] first operating system, and
[0014] A virtual machine having a second operating system, wherein the virtual machine is integrated on a hardware layer, and
[0015] a hypervisor configured to cause the virtual machine to run on the hardware layer so that the first operating system and the second operating system can run in parallel on the hardware layer,
[0016] wherein at least one first application can be implemented on the first operating system, and at least one second application can be implemented on the second operating system,
[0017] and wherein at least one first application has a higher security standard than at least one second application,
[0018] In this case, the second operating system is configured to run in a suspend-to-RAM operating mode, while the first operating system is shut down.
[0019] The hardware layer is often also referred to as a computing system or computing unit and preferably comprises a processor, a working memory and interfaces.
[0020] In this case, the hypervisor is constructed as an abstraction layer between the hardware layer and the virtual machines, wherein the virtual machines are implemented on the hardware layer. The embodiments can be implemented completely based on hardware, completely based on software or by a combination of the two. The hypervisor is particularly designed to provide virtual machines and to manage virtual machines. The virtual machines preferably emulate the computing structure of a computer that actually exists in the form of hardware or a hypothetical computer. The operating system of the virtual machine is also often referred to as a client operating system. The hypervisor usually allows multiple virtual machines to be run simultaneously on a physical computer system. The hypervisor can also be referred to as a virtualization layer.
[0021] The hypervisor may be a Type-0 (Typ-0), Type-1 (Typ-1), or Type-2 (Typ-2) hypervisor, and other virtual machines may be provided in addition to the first virtual machine, for example.
[0022] Type-1 hypervisors are directly integrated on the hardware layer and do not require a complete operating system. The allocation of virtual machines and their resources (also called resources, such as working memory, CPU) is dynamically supported by a minimal operating system or no operating system at all. Representatives of Type-1 hypervisors are, in particular, Microsoft Hyper-V or Citrix XenServer, or Sysgos PikeOS, Green Hills Integrity, Freescales Topaz for embedded systems.
[0023] The hypervisor is configured so that virtual machines can be implemented simultaneously on the hardware layer.
[0024] The Type-2 hypervisor is integrated into the complete main operating system, which takes care of the final allocation of resources requested by the virtual machines, and the Type-2 hypervisor controls the virtual machines from there. Known representatives are VMware Workstation, VirtualBox or Linux Kernel-based Virtual Machine (KVM).
[0025] Type-0 hypervisors are integrated directly at the hardware level without a supporting operating system.
[0026] Safety-relevant first functions or applications with a high safety standard are, for example, instrument cluster applications, such as monitoring and control functions in a vehicle.
[0027] Non-critical second applications, ie applications with low safety standards, are provided, for example, by infotainment applications. Infotainment applications are functions of an infotainment system. An infotainment system includes, for example, a car radio or multimedia system, a navigation system and a hands-free telephone system.
[0028] Such infotainment systems typically have NAND memory cells, which require a complex boot process.
[0029] For example, with the aid of the ISO 26262 (“Road vehicles—Functional safety”) ISO standard for safety-related electrical / electronic systems in motor vehicles, a distinction can be made between applications with high or low safety standards.
[0030] According to the invention, it is recognized that the suspend to memory operating mode for the entire vehicle system is dangerous because the probability of an erroneous or ambiguous start is very high. The persistent open state of the hardware (e.g. memory) and the persistent open state of the operating system at the hardware level causes memory leaks and memory fragmentation, which can non-deterministically affect the behavior of the vehicle system.
[0031] Instead of placing the entire vehicle system in the suspend-to-ram operating mode, the system is partitioned in such a way that the second operating system is configured to run in the suspend-to-ram operating mode and the first operating system is shut down, wherein at least one first application can be implemented on the first operating system and at least one second application can be implemented on the second operating system, and wherein the at least one first application has a higher security standard than the at least one second application.
[0032] That is, only the non-critical parts of the system are put into the suspend-to-RAM operation mode, and the critical parts of the system are restarted, thereby ensuring safe startup and safe operation.
[0033] In particular, robustness and rapid availability of the operating system on which the safety-critical application runs is thus ensured, while the non-safety-critical operating system with the non-critical applications is rapidly available by means of the suspend-to-RAM operating mode. Thus, on the one hand, rapid availability of the vehicle system is ensured, and on the other hand, safe operation of the vehicle system is ensured.
[0034] Current consumption by vehicle systems is minimized.
[0035] Preferably, the first operating system has a higher security standard than the second operating system. Therefore, the first operating system can be designed as a certifiable, real-time, fast-startable first operating system for safety-critical functions / applications. The first operating system can be designed, for example, as an AUTOSAR (AUTomotive Open System Architecture) operating system. Here, AUTOSAR is a software architecture for electronic controllers. In addition, the first operating system can be, for example, PikeOS. This is a real-time operating system that provides a separate kernel-based hypervisor with multiple partition types for many other operating systems. The PikeOS real-time operating system is designed for safety-critical applications with certification requirements. Another example of such an operating system is QNX, which constitutes a proprietary Unix-like real-time operating system that supports POSIX.
[0036] The second operating system used for non-critical functions / applications is, for example, a high-level OS (Operation System), and can be, for example, a Linux, Genivi, Windows, or Android operating system.
[0037] Preferably, when the vehicle system starts to operate, the first operating system can be restarted, and the second operating system can be enabled from the suspend to memory operation mode.
[0038] Preferably, the vehicle system comprises at least one first application and at least one second application, wherein the at least one first application is closed and at least the second application is in a suspended-to-memory operating mode.
[0039] Therefore, preferably, when the vehicle system starts to operate, at least one first application can be restarted, and at least one second application can be enabled from the suspended to the memory operation mode, thereby achieving the safe implementation of the safety-critical first application / multiple first applications and the rapid implementation of the non-critical second application / multiple second applications.
[0040] In a preferred design, the management program is configured to be shut down when the vehicle system stops running, and to be restarted when the vehicle system starts running, thereby ensuring a safe operation mode of the management program.
[0041] Preferably, the hardware layer is constructed as a system-on-chip (SoC). Preferably, the system-on-chip includes at least one microprocessor, a working memory, an interface and a bus. System-on-chip is essentially understood as integrating all or most of the functions of a programmable electronic system onto a chip, i.e., an integrated circuit on a semiconductor substrate, also known as a monolithic integrated circuit.
[0042] Preferably, the hardware layer has resources / operating tools / working media, wherein the hypervisor is configured to allocate resources to the first operating system and the second operating system so that the first operating system and the second operating system can run independently of each other. Preferably, the hypervisor is configured to partition at least one of the resources in the following way, that is, the hypervisor allocates a first sub-area of at least one resource to the first operating system and allocates a second sub-area of at least one resource to the second operating system. In addition, the hypervisor is preferably configured to provide at least one first application and at least one second application in the first operating system partition and the second operating system partition on the hardware layer. Therefore, the two operating systems can run on the same hardware. Therefore, security-critical and non-critical applications can use the same hardware.
[0043] Preferably, the vehicle system includes a first virtual machine having a first operating system, and
[0044] a second virtual machine having a second operating system, wherein the first virtual machine and the second virtual machine are integrated on a hardware layer so that the first virtual machine and the second virtual machine can run in parallel on the hardware layer,
[0045] wherein at least one first application can be implemented on the first operating system, and at least one second application can be implemented on the second operating system, wherein the at least one first application has a higher security standard than the at least one second application,
[0046] a hypervisor designed to enable the first virtual machine and the second virtual machine to run on a hardware layer,
[0047] The second virtual machine is designed to run in a suspend-to-memory running mode, while the first virtual machine is shut down.
[0048] In this case, in particular a Type-1 (TYP-1) or Type-0 (TYP-0) hypervisor is used. This allows efficient use of multi-core processors. The cores of the multi-core processor can be assigned to different virtual machines.
[0049] Preferably, the hardware layer comprises at least one resource, wherein the hypervisor is configured to partition at least one of the resources by allocating a first sub-region of the at least one resource to a first virtual machine and a second sub-region of the at least one resource to a second virtual machine. Thus, the two virtual machines can simply run in parallel with each other.
[0050] In another preferred design, when the vehicle system starts to operate, the first operating system of the first virtual machine can be restarted, and the second operating system of the second virtual machine can be enabled from the suspend to memory operation mode.
[0051] Furthermore, the object is achieved by providing a vehicle having a vehicle system as described above. In a preferred embodiment, the vehicle system has at least one component, wherein the vehicle system has an interface for communication between the vehicle system and the at least one component. The component may be, for example, an infotainment system or a camera for the driver.
[0052] Furthermore, the object is achieved by providing a method for operating a vehicle system, the method comprising the steps of:
[0053] - providing a first operating system on the hardware layer,
[0054] - Provides a hypervisor on the hardware layer,
[0055] - providing a virtual machine with a second operating system via a hypervisor, so that the first operating system and the second operating system can run in parallel on a hardware layer, wherein at least one first application can be implemented on the first operating system and at least one second application can be implemented on the second operating system, wherein the at least one first application has a higher security standard than the at least one second application,
[0056] -Running the second operating system in a suspend-to-ram mode while shutting down the first operating system.
[0057] Advantages of the vehicle system may also be transferred to the method.
[0058] Preferably, the method comprises the steps of:
[0059] - Provides a hypervisor on the hardware layer,
[0060] - providing, by the hypervisor, a first virtual machine having a first operating system,
[0061] - providing a second virtual machine with a second operating system via the hypervisor, so that the first virtual machine and the second virtual machine can run in parallel on the hardware layer, wherein at least one first application can be implemented on the first operating system and at least one second application can be implemented on the second operating system, wherein the at least one first application has a higher security standard than the at least one second application,
[0062] -Running the second virtual machine in a suspend-to-ram operation mode and shutting down the first virtual machine.
[0063] Preferably, the method comprises the further steps of:
[0064] - Provide vehicle systems in operation,
[0065] -Put the second operating system in a suspend-to-RAM mode and shut down the first operating system.
[0066] Preferably, the method comprises the further steps of:
[0067] - Provide vehicle systems in operation,
[0068] - placing the second operating system in suspend-to-ram mode and shutting down the first operating system,
[0069] - Shutdown and close the hypervisor.
[0070] In another preferred design, the method includes the following steps:
[0071] - providing the first operating system in a closed state,
[0072] - provide a second operating system in suspend-to-ram mode,
[0073] - starting the first operating system by restarting when the vehicle system starts to operate,
[0074] -Starting a second operating system from a suspended to RAM mode when the vehicle system starts running.
[0075] In another preferred design, the method includes the following steps:
[0076] - Provide vehicle systems in operation,
[0077] - Closing at least one first application and placing at least one second application in a suspend-to-memory execution mode.
[0078] Preferably, the partitioning of the at least one resource of the hardware layer is performed by the hypervisor allocating a first sub-region of the at least one resource to a first operating system and a second sub-region of the at least one resource to a second operating system.
[0079] Preferably, the method is configured to be performed on a vehicle system as described above.
[0080] Furthermore, the object is achieved by providing a computer-readable storage medium having a computer program stored thereon, wherein the computer program comprises instructions which cause the vehicle system as described above to execute the method steps as described above.
[0081] Furthermore, the object is achieved by providing a computer program, which comprises instructions which cause a vehicle system as described above to carry out the method steps as described above. Thus, the method can also be subsequently deployed simply in a vehicle suitable for this purpose. BRIEF DESCRIPTION OF THE DRAWINGS
[0082] Further features, properties and advantages of the invention emerge from the following description with reference to the accompanying drawings.
[0083] in:
[0084] Figure 1 A first vehicle system according to the prior art is schematically shown,
[0085] Figure 2 A second vehicle system according to the prior art is schematically shown.
[0086] Figure 3 A third vehicle system according to the prior art is schematically shown.
[0087] Figure 4 Schematically shows an activation method according to the prior art,
[0088] Figure 5 A first vehicle system according to the present invention is schematically shown,
[0089] Figure 6 A second vehicle system according to the present invention is schematically shown,
[0090] Figure 7 The activation method according to the invention is schematically illustrated. DETAILED DESCRIPTION
[0091] Although the invention has been further illustrated and described by preferred embodiments, the invention is not limited to the disclosed examples. Variations may be made by those skilled in the art without departing from the scope of the invention as defined by the appended claims.
[0092] Figure 1A vehicle system 100 according to the prior art is shown. The vehicle system 100 used in a vehicle comprises a first hardware layer 101 having a first operating system 102. The first operating system 102 is designed for a safety-critical first function / application 103, ie for applications with high safety standards in the vehicle.
[0093] Furthermore, the vehicle system 100 comprises a second hardware layer 111 having a second operating system 112. The second operating system 112 is designed for non-critical second functions / applications 113, ie for applications in the vehicle with low safety standards.
[0094] In this case, each of the hardware layers 101 , 111 preferably includes at least one microprocessor, a basic input and output system (BIOS), a working memory (RAM) and / or a flash memory, a clock generator, and various interfaces and a plurality of buses.
[0095] Furthermore, hardware layer 101 , 111 may have a start / boot memory unit or a start / boot ROM memory, for example as a flash memory or an OTP memory, in which program elements responsible for the start process are stored.
[0096] The hardware layers 101 , 111 are physically separated from each other, for example they are on different integrated circuits.
[0097] In this case, first operating system 102 is designed for safety-critical functions or safety-critical applications 103 , and second operating system 112 is designed for non-critical functions or non-critical applications 113 .
[0098] The second hardware layer 111 has a high-level OS (operating system) as a second operating system 112 for non-critical functions / applications 113. The second operating system 112 can be, for example, Linux, Genivi, Windows or Android. Non-critical functions are provided, for example, by a vehicle infotainment system. In this case, the vehicle infotainment system can have functions for an onboard radio or multimedia system, a navigation system and / or a hands-free telephone system.
[0099] Such vehicle infotainment systems typically have NAND memory cells, which require a complex activation process.
[0100] The first hardware layer 101 has as first operating system 102 a first operating system 102 that can be authenticated, run-time and quickly started for safety-critical functions / applications 103 .
[0101] Therefore, the operating systems 102 , 112 and their applications 103 , 113 are implemented independently of one another, ie, the operating systems 102 , 112 are run and exited independently of one another.
[0102] Activation of the vehicle system 100 is performed as follows:
[0103] The entire vehicle system 100 , ie, all two operating systems 102 , 112 , is restarted and initialized. The startup performance is optimized for all individual operating systems 102 , 112 .
[0104] Figure 2 Another example of a vehicle system 200 according to the prior art is shown. The vehicle system 200 has a hardware layer 201, which has a hypervisor (Virtualisierungsschicht, virtualized layer) 202 arranged thereon, which installs at least two virtual machines on the hardware layer 201. Here, the first virtual machine includes a first operating system 102 for a safety-critical first application 103. The first operating system 102 can be designed as a certifiable, real-time, fast-startable first operating system 102 as described above. The first operating system 102 can be, for example, AUTOSAR (Automotive Open System Architecture). Here, AUTOSAR is a software architecture for electronic controllers. Alternatively, the first operating system 102 can be constructed as PikeOS. It is a real-time operating system. The PikeOS real-time operating system is created for a safety-critical first application 103 with certification requirements. In addition, the first virtual machine can include an input / output driver and a real-time scheduler. In addition, a safety-critical first application 103 can be implemented on the first virtual machine. This can be, for example, a combination instrument / dashboard application with a higher safety standard.
[0105] The second virtual machine has a second operating system 112 for a non-critical second application 113, such as a high-level OS (operating system), in particular Linux, Genivi, Windows or Android. In addition, the second virtual machine can also include input / output drivers and a scheduler. The non-critical second application 113 can be, for example, an infotainment application with low safety standards. Through the hypervisor 202, the virtual machines and therefore the two operating systems 102, 112 can be decoupled from each other and from the hardware layer 201 of the vehicle system 200. For this purpose, a Type-1 (Typ-1) or Type-0 (Typ-0) hypervisor is used.
[0106] When the vehicle is shut down, the entire vehicle system 200 enters a suspend-to-RAM operating mode (STR) in the RAM (data memory). The suspend-to-RAM operating mode is also called a standby operating mode (Standby Mode, Standby Mode, Sleep Mode). This allows the vehicle system 200 to be quickly available.
[0107] Figure 3 Another vehicle system 300 according to the prior art is shown.
[0108] In this case, a hardware layer 201 is provided, on which a first operating system 102 is directly integrated for a safety-critical first application 103. The first operating system 102 can be designed as a certifiable, real-time, fast-startable first operating system 102 as described above.
[0109] The vehicle system 300 includes a hypervisor 301, which is configured in such a way that a virtual machine with a second operating system 112 for a non-critical second application 113 installed by the hypervisor 301 on the hardware layer 201 can be implemented simultaneously on the hardware layer 201. In this case, the first operating system 102 can create a virtual machine on which the second operating system 113 is hosted. The first operating system 102 can create such a virtual machine, for example, with the aid of an API (Anwendungsprogrammschnittstelle, application program interface), such as a Hypercall-API. A Type-2 hypervisor is used for this purpose. Such a Type-2 hypervisor is integrated into a complete main operating system, which takes over the final allocation of resources requested by the virtual machine, such as a CPU. From there, the hypervisor controls the virtual machine. Known representatives are VMware Workstation, VirtualBox or Linux kernel-based virtual machines (KVM).
[0110] Thus, the vehicle systems 200 , 300 according to the prior art run on the same hardware layer 201 with a single memory. However, the applications are implemented in different operating systems: the critical first application 103 runs on an ASIL (Automotive Safety Integrity Level) certified operating system (OS), here the first operating system 102 , and the non-critical second application 113 runs on a higher-level operating system (OS), here the second operating system 112 (e.g. Android / Linux / Windows), wherein the separation is ensured by the hypervisor 202 , 301 .
[0111] When the vehicle is shut down, the entire vehicle system 200 , 300 enters a suspend-to-remote operating mode (STR) in the RAM (data memory).
[0112] Figure 4 A method of enabling a vehicle system 300 according to the prior art is shown.
[0113] All operating systems 102, 112 and applications 103, 113 and hypervisors are acquired from a suspend to run-in-memory mode in RAM.
[0114] In a first step S1, the first operating system 102 on the hardware 201 provided in step S0 is started from the RAM, where the first operating system 102 waits in the RAM in a suspend-to-memory operating mode. The first operating system 102 can be designed as AUTOSAR (Automotive Open System Architecture), PikeOS, or QNX Integrity, for example.
[0115] In a second step S2, a safety-critical application 103 stored in the RAM in the suspended-to-memory operating mode is started in the first operating system 102. Applications with high safety standards / safety requirements are, for example, instrument cluster / dashboard applications. They are preferably assigned to the instrument cluster.
[0116] In a third step S3, a hypervisor 301 is started, which is stored in the RAM in the suspended-to-memory operating mode. The hypervisor installs the virtual machine on the hardware layer 201. The hypervisor 301 is preferably designed as a Type-2 hypervisor, which is integrated in the first operating system 102. The hypervisor is responsible for the allocation of resources (e.g., CPU, etc.) of the hardware layer 201. Therefore, the hypervisor 301 allocates resources (Resourcen) to the virtual machine. The hypervisor allocates resources in such a way that all resources are available to the second operating system 112 when needed, just as if there were only one operating system.
[0117] Finally, in the fourth step S4, the second operating system 112, a high-level operating system such as Linux, Windows, Android, which runs in a virtual machine, is started on the hardware layer 201 by the hypervisor 301. The second operating system 112 stored in the RAM in the suspended-to-memory operation mode is started from the RAM.
[0118] The hypervisor 301 is configured to decouple the first operating system 103 and the second operating system 112 from each other and to execute them in parallel. Through the hypervisor 301 , a non-critical second application 113 can be integrated into an independent operating system partition on the hardware layer 201 .
[0119] In a fifth step S5, non-critical second applications 113 stored in the RAM in the suspend-to-memory operating mode are started. These may be infotainment applications, for example.
[0120] The entire vehicle system 300 is thereby started from the system-wide RAM in which the vehicle system is stored in a suspend-to-ram operating mode.
[0121] However, it has been recognized that using the suspend to memory operating mode for safety-critical applications 103 and the associated operating system 102 is dangerous because the possibility of false or ambiguous startup is very high. Memory leaks and memory fragmentation caused by a persistently open vehicle system 300 (e.g., a persistently open memory) can non-deterministically affect the behavior of the vehicle system 300. Using the suspend to memory operating mode for the entire vehicle system 300 can jeopardize the reliability of the critical first application 103 and the non-critical second application 113.
[0122] There is a risk that the RAM content has defects after waking up (ie, for example, by starting the vehicle and the vehicle system 200, 300), whereby the entire vehicle system 300 may crash. In addition, the problem of memory leaks and memory fragmentation is aggravated during activation.
[0123] The same applies to vehicle system 200 according to the prior art.
[0124] Figure 5 A vehicle system 1 according to the invention is shown. The vehicle system 1 comprises a hardware layer 2, which preferably comprises at least one microprocessor, a working memory (RAM, main memory) and a flash memory, a clock generator as well as various interfaces and a plurality of buses. In addition, the hardware layer 2 comprises a first operating system 3. The first operating system 3 is preferably designed as a certifiable, real-time, fast-startable, automotive safety integrity level (ASIL) first operating system 3. The first operating system 3 is preferably selected in accordance with the ISO standard for safety-related electrical / electronic applications in motor vehicles ("Road vehicles-Functional safety"). Preferably, safety-critical first applications 4 are implemented on the first operating system 3. These applications are preferably instrument cluster applications and are preferably assigned to the instrument cluster.
[0125] In addition, the vehicle system 1 includes a hypervisor 5, which is equipped with a virtual machine. The hypervisor 5 is preferably designed as a Type-2 hypervisor. Such a Type-2 hypervisor is integrated into a complete main operating system, which is responsible for the final allocation of resources requested by the virtual machine, such as the CPU, etc. The hypervisor 5 controls the virtual machine from there. Known representatives are VMware Workstation, VirtualBox or Linux kernel-based virtual machines (KVM).
[0126] The hypervisor 5 installs a virtual machine with a second operating system 6 on the hardware layer 2. In this case, a first application 4 is executed on the first operating system 3, and a second application 7 is executed on the second operating system 6, wherein the safety-critical first application 4 has a higher safety standard than the non-critical second application 7. In this case, the non-critical second application 7 can be assigned to a vehicle infotainment system.
[0127] This means that the safety-relevant first application 4 and the non-critical second application 7 are executed on the hardware layer 2 with a common memory.
[0128] The hardware layer 2 is preferably designed as a system-on-chip (SoC) having a multi-core processor, ie, a high-performance multi-core system.
[0129] In this case, the second operating system 6 is designed to be run in a suspend-to-ram operating mode, while the first operating system 3 is shut down.
[0130] Instead of placing the entire vehicle system 1 in the suspend-to-ram operating mode, the vehicle system 1 is partitioned by means of the hypervisor 5 so that only a second part 9 of the vehicle system 1 is placed in the suspend-to-ram operating mode, wherein the second part includes a second operating system 6 with non-critical applications 7. A first part 8 of the vehicle system 1 is restarted, which first part includes a first operating system 3 with a safety-related first application 4 and the hypervisor 5.
[0131] The entire vehicle system 1 according to the invention can thus be activated reliably and quickly.
[0132] This ensures the robustness of the safety-related first application 4 and the rapid availability of the second application 7. The second application 7 of the second operating system 6 (e.g., infotainment functions) is not critical. All operating systems, namely the first operating system 3 and the second operating system 6 with their applications 4, 7, are rapidly available in the vehicle system 1 according to the invention.
[0133] Figure 6 Another vehicle system 10 according to the invention is shown. The vehicle system comprises the same hardware layer 2. In addition, a hypervisor 12 is provided on the hardware layer 2. The hypervisor 12 is designed as a Type-1 or Type-0 hypervisor. A Type-1 hypervisor is directly integrated into the hardware and does not require a complete operating system or even an operating system. The allocation of virtual machines and their resources (Betriebsmittel, such as working memory) is dynamically supported by a minimal operating system or even without operating system support. Representatives are in particular Microsoft Hyper-V or Citrix XenServer, or for embedded systems, representatives are Sysgos PikeOS, Green Hills Integrity, Freescales Topaz.
[0134] The hypervisor 12 installs a first virtual machine with a first operating system 3. The first operating system 3 can be designed as a certifiable, real-time, fast-bootable automotive safety integrity level (ASIL) first operating system 3 as described above. A safety-critical first application 4 is implemented on the first operating system 3.
[0135] The hypervisor 12 installs a second virtual machine with a second operating system 6. A second non-critical application 7 is implemented on the second operating system.
[0136] Instead of placing the entire vehicle system 10 in the suspend-to-RAM operating mode, the vehicle system 10 is partitioned by means of the hypervisor 12 so that only a second part 18 of the vehicle system 10, which includes the second virtual machine, is placed in the suspend-to-RAM operating mode. The first part 17 of the vehicle system 10, which includes the first operating system 3 with the safety-related application 7 and the hypervisor 12, is restarted.
[0137] Figure 7 A vehicle system 1 ( Figure 5 ) according to the present invention. Here, in step A0, a hardware layer 2 ( Figure 5 ).
[0138] First, the vehicle system 1 is restarted by a so-called cold start ( Figure 5 )Part 18( Figure 5 ). During a cold start, the vehicle systems are started from a shut-down state and placed into normal operating conditions.
[0139] To this end, in step A1, the first operating system 3 is first restarted ( Figure 5 ).
[0140] Then, in step A2, the management program 5 is restarted ( Figure 5 ), which is at hardware layer 2 ( Figure 5 ) to set up a virtual machine.
[0141] Then, in step A3, the safety-critical application 4 is restarted ( Figure 5 ).
[0142] The vehicle system 1 is then started by a so-called warm start ( Figure 5 ) in the second part 9. Here, the function / application is obtained from the suspended to the memory running mode.
[0143] For this purpose, in step A4 , the second operating system 6 is first acquired from the suspend-to-ram operating mode.
[0144] Subsequently, in a further step A5 , a non-critical application 7 is started and executed in the second operating system 6 .
[0145] The invention can be used in all areas where both safety-related and non-safety-related applications are implemented in a hypervisor environment.
[0146] Reference numerals list
[0147] 100 Vehicle system according to the prior art
[0148] 101 Hardware layer of vehicle system 100
[0149] 102 A first operating system of the vehicle system 100
[0150] 111 Second hardware layer of vehicle system 100
[0151] 112 Second operating system of vehicle system 100
[0152] 103 First application of vehicle system 100
[0153] 113 Second Application of Vehicle System 100
[0154] 200 Vehicle system according to the prior art 200
[0155] 201 Hardware layer 201 of vehicle system 200
[0156] 202 Management program of vehicle system 200
[0157] 300 Vehicle system according to the prior art
[0158] 301 Management program of vehicle system 300
[0159] 1 Vehicle System
[0160] 2 Hardware Layer
[0161] 3 The first operating system
[0162] 4 Safety-critical applications
[0163] 5 Management Program
[0164] 6 Second operating system
[0165] 7 Non-critical Secondary Applications
[0166] 8 Part 1
[0167] 9 Part 2
[0168] 10. Second vehicle system according to the present invention
[0169] 12 Hypervisor
[0170] 17 Part 1
[0171] 18 Part 2
[0172] S.A Method Steps
Claims
1. A vehicle system (1, 10), comprising: Hardware layer (2); A first operating system (3); A virtual machine having a second operating system (6), wherein the virtual machine is integrated on the hardware layer (2); a hypervisor (5, 12) configured to enable a virtual machine to run on the hardware layer (2), so that the first operating system (3) and the second operating system (6) can run in parallel on the hardware layer (2), It is characterized in that At least one first application (4) can be executed on the first operating system (3), and at least one second application (7) can be executed on the second operating system (6), wherein the at least one first application (4) has a higher security standard than the at least one second application (7), wherein the second operating system (6) is configured to run in a suspend-to-memory operation mode, and the first operating system (3) is shut down, The second operating system (6) is configured to be acquired from the suspend to memory operation mode after the first operating system (3) is restarted.
2. The vehicle system (1, 10) according to claim 1, characterized in that When the vehicle system (1, 10) starts to operate, the first operating system (3) can be restarted and the second operating system (6) can be enabled from the suspend to memory operation mode.
3. The vehicle system (1, 10) according to claim 1 or 2, characterized in that: The system comprises at least one first application (4) and at least one second application (7), wherein the at least one first application (4) is closed and the at least one second application (7) is in a suspended to memory operation mode.
4. The vehicle system (1, 10) according to claim 3, characterized in that When the vehicle system (1, 10) starts to operate, the at least one first application (4) can be restarted and the at least one second application (7) can be enabled from the suspended to memory operation mode.
5. The vehicle system (1, 10) according to claim 1 or 2, characterized in that: The management program (5, 12) is configured to shut down when the vehicle system (1, 10) stops operating, and is configured to restart when the vehicle system (1, 10) starts operating.
6. The vehicle system (1, 10) according to claim 1 or 2, characterized in that: The first operating system (3) has a higher security standard than the second operating system (6).
7. The vehicle system (1, 10) according to claim 1 or 2, characterized in that: The hardware layer (2) is constructed as a system chip.
8. The vehicle system (1, 10) according to claim 1 or 2, characterized in that: The hardware layer (2) has resources, wherein the hypervisor (5, 12) is configured to allocate the resources to the first operating system (3) and the second operating system (6) so that the first operating system (3) and the second operating system (6) can run independently of each other.
9. The vehicle system (1, 10) according to claim 8, characterized in that The hypervisor (5, 12) is configured to perform partitioning of at least one of the resources in such a manner that the hypervisor (5, 12) allocates a first sub-region of at least one resource to the first operating system (3) and allocates a second sub-region of at least one resource to the second operating system (6).
10. The vehicle system (1, 10) according to claim 1 or 2, characterized in that: The hypervisor (5, 12) is configured to provide the at least one first application (4) and the at least one second application (7) in a first operating system partition and a second operating system partition on the hardware layer (2).
11. The vehicle system (10) according to claim 1 or 2, comprising: a first virtual machine having the first operating system (3), and a second virtual machine having the second operating system (6), in, The first virtual machine and the second virtual machine are integrated on the hardware layer (2), so that the first virtual machine and the second virtual machine can run in parallel on the hardware layer (2), wherein at least one first application (4) can be implemented on the first operating system (3), and at least one second application (7) can be implemented on the second operating system (6), wherein the at least one first application has a higher security standard than the at least one second application, a hypervisor (12) configured to cause the first virtual machine and the second virtual machine to run on the hardware layer (2), The second virtual machine is configured to run in a suspend-to-memory operation mode, and the first virtual machine is shut down.
12. The vehicle system (10) according to claim 11, characterized in that The hardware layer (2) includes at least one resource, wherein the hypervisor (12) is configured to perform partitioning of at least one of the resources in the following manner, namely, the hypervisor (12) assigns a first sub-region of the at least one resource to the first virtual machine, and assigns a second sub-region of the at least one resource to the second virtual machine.
13. The vehicle system (10) according to claim 11, characterized in that When the vehicle system (10) starts to operate, the first operating system (3) of the first virtual machine can be restarted, and the second operating system (6) of the second virtual machine can be enabled from the suspended to memory operation mode.
14. A vehicle having a vehicle system (1, 10) according to any one of the preceding claims 1 to 13.
15. The vehicle according to claim 14, characterized in that The vehicle system (1, 10) has at least one component, wherein the vehicle system (1, 10) has an interface for communication between the vehicle system (1, 10) and the at least one component.
16. A method for operating a vehicle system (1, 10), characterized in that There are steps: - providing a first operating system (3) on the hardware layer (2); - providing a hypervisor (5, 12) on said hardware layer (2); - providing a virtual machine with a second operating system (6) by means of the hypervisor (5, 12), so that the first operating system (3) and the second operating system (6) can be run in parallel on the hardware layer (2), wherein at least one first application (4) can be implemented on the first operating system (3) and at least one second application (7) can be implemented on the second operating system (6), wherein the at least one first application (4) has a higher security standard than the at least one second application (7); - operating the second operating system (6) in a suspend-to-memory operating mode and shutting down the first operating system (3), - After the first operating system (3) is restarted, the second operating system (6) is acquired from the suspend to memory operation mode.
17. The method according to claim 16, characterized in that There are steps: - providing a hypervisor (12) on the hardware layer (2); - providing a first virtual machine having the first operating system (3) through the hypervisor (12); - providing a second virtual machine having the second operating system (6) by means of the hypervisor (12), so that the first virtual machine and the second virtual machine can run in parallel on the hardware layer (2), wherein at least one first application (4) can be implemented on the first operating system (3), and the at least one second application (7) can be implemented on the second operating system (6), wherein the at least one first application (4) has a higher security standard than the at least one second application (7); -Run the second virtual machine in a suspend-to-memory operation mode and shut down the first virtual machine.
18. The method according to claim 16 or 17, characterized in that There are steps: - providing a vehicle system (1, 10) in operation; - placing the second operating system (6) in a suspend-to-RAM operating mode and shutting down the first operating system (3).
19. The method according to claim 18, characterized in that There are steps: - providing said first operating system (3) in a closed state; - providing said second operating system (6) in a suspend-to-RAM operating mode; - starting the first operating system (3) by restarting when the vehicle system (1, 10) starts to operate; - When the vehicle system (1, 10) starts to operate, the second operating system (6) is started from the suspended to memory operation mode.
20. The method according to claim 16 or 17, characterized in that There are steps: - providing a vehicle system (1, 10) in operation; - placing the at least one second application (7) in a suspended-to-memory operating mode and shutting down the at least one first application (4).
21. A computer-readable storage medium having a computer program stored thereon, wherein the computer program comprises instructions for causing the vehicle system (1, 10) according to any one of claims 1 to 13 to implement the method steps according to any one of claims 16 to 20.
