You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Background

Hypervisor is a well known hardware virtualization technique that allows multiple virtual machines called guests identified by their OS to run on a host system. The virtual guests have access (exclusive or shared) to underlying hardware resources including CPU, memory and peripherals. In the context of the virtual guest, it appears as if all of the allocated hardware is natively available exclusively to that machine. Hypervisor in most cases also provides a means of controlling the execution state of the virtual guests. Hypervisors are increasingly being used in modern automotive software systems for combining safety critical and safety agnostic platforms as well as for consolidating multiple ECU functions into one.

Purpose

The purpose of this document is to capture the critical use cases that needs to be considered for using an Hypervisor in the context of automotive in vehicle infotainment. As Instrument clusters functions fall in adjacent yet very close domain, some of the cross functional aspects between clusters and infotainment needs to be considered as well. The objective of defining these critical use cases is to create a sounding base for defining candidate system requirements and model architecture covering the type of hypervisor as well as resource sharing

Assumption

The following are the assumptions that the reader needs to make while going through the use cases. Eventually, it may be possible to challenge the assumption itself and arrive at contradictory architectures that may be even better and well suited for all practical purposes. 

IDAssumption
A1The overall system involves at least one instance of Hypervisor software
A2The overall system involves at least one instance of vehicle domain running AUTOSAR compliant software


Use cases 

IDTitleDescription / Flow of eventsPertinent Challenges / Key pointsRemarks/Comments
HVS-UC-01Rear view Camera at Startup
  1. User inserts the key in the key fob
  2. (Possibly)System initialization begins in the background
  3. User engages the reverse gear within 1 second
  4. User turns the key to crank the vehicle within 2 seconds of key insertion
  5. Full system initialization begins and system beings to show the boot up animation / splash screen / boot up audio
  6. System displays the Rear View Camera output on screen along with park distance guide
  1. Which domain/virtual guest controls the first camera stream?
  2. Which domain/virtual guest controls the first display output?
  3. If there is a need for handover between virtual guests, what is the underlying protocol for handover?
  4. What happens if the user immediately turns off the engine?
  1. Consider the scenario when the RVC output and park distance guide are being displayed on Instrument Cluster as well.
  2. Extending #1, what if the Instrument Cluster logic is actually from a virtual guest? Would the safety critical aspects of cluster apply? What are the limitations with respect to timing?
HVS-UC-02Entry into vehicle with an active call over Bluetooth
  1. User inserts the key in the fob
  2. (Possibly)System initialization begins in the background
  3. User turns the key to crank the vehicle
  4. Full system initialization begins and system beings to show the boot up animation / splash screen / boot up audio
  5. Immediately a Bluetooth call is detected and audio path is routed to cabin speakers and microphone is used for audio input
  1. Which domain/virtual guest controls the first audio such as boot up audio?
  2. How is the handover of audio channel performed between the first audio source and call audio?
  3. What if the LUC was USB media and the USB media is still connected and if the USB media playback is coming from another domain/virtual guest other than the one with active call

HVS-UC-03Entry into vehicle with an active call over Bluetooth + External amplifier over Ethernet AVB


HVS-UC-03Entry into vehicle with an active telematics call + Reverse Gear




  • No labels