Scope and context

In this section, the scope and context for PELUX is presented. It includes the users and the external interfaces which are used for interacting with the system.

Users and roles

Table 1 presents the PELUX users and their roles.

Table 1 Users and roles

User

Role

Driver

Person in the driver seat, the active user of the Instrument Cluster and the IVI system.

Co-driver

Passenger in the front seat, active user of the IVI system.

Left rear seat passenger

Passenger in the left rear seat, active user of the RSE / RSI system.

Right rear seat passenger

Passenger in the right rear seat, active user of the RSE / RSI system.

Workshop engineer

Performs maintenance, e.g. upgrading the firmware

EOL test engineer

Configures the IVI system at production and deploys the proper firmware on target.

Customer

OEM or Tier-1 which selects PELUX as their development platform

UX developer

Develops UX software on PELUX

Embedded developer

Develops non UX software on PELUX, e.g. application backends and platform services.

External Entities

External entities can be anything from external systems to peripheral devices which PELUX can either receive input from or send output to.

Table 2 External Entities

Entity

Direction

Interface

Touch Panels

IN

I2C, SPI

Hard Buttons

IN

LIN, CAN

Microphones

IN

I2C, SPI

Driver Cameras

IN

HDMI, Ethernet TSN / AVB

Rear/Surround View Cameras

IN

HDMI, Ethernet TSN / AVB

Auxillary Inputs

IN

I2S, I2C, SPI,

GPS Receiver

IN

USB, Ethernet

RDS-TMC Receiver

IN

I2C, SPI

Optical Device

IN

ATAPI IDE

Mass Storage Devices

IN

USB, SD

Center Stack Display

OUT

HDMI, LVDS

Instrument Cluster Display

OUT

HDMI, LVDS

Head-Up Display

OUT

Rear-Seat Displays

OUT

HDMI, LVDS

Loudspeakers

OUT

I2S, I2C, SPI, S/PDIF, MOST

Headphones

OUT

I2S, I2C, SPI, Bluetooth

Mobile Devices

IN / OUT

USB, Bluetooth, WiFi

Vehicle Cloud Server

IN / OUT

Internet

Instrument Cluster

IN / OUT

Hypervisor IPC, APIX

Rear-Seat Entertainment

IN / OUT

Hypervisor IPC, Ethernet TSN / AVB, FlexRay, CAN

Telematics Gateway System

IN / OUT

Hypervisor IPC, Ethernet TSN / AVB, FlexRay, CAN

Vehicle Master ECU

IN / OUT

Ethernet TSN / AVB, FlexRay, CAN

Vehicle-CPU (V-CPU)

IN / OUT

SPI, CAN, Ethernet

Diagnostic Test Equipment

IN / OUT

CAN, Ethernet, OBD, UDS, DoIP

Additional notes:

  • The Driver Camera can be used to capture gestures from the driver to interact with the system. It can also be used for face recognition and user profile detection.

  • NHTSA regulation states that live rear camera video must be displayed in less than two seconds after the driver places the vehicle into reverse gear. This type of video is sometimes called early video.

  • The Vehicle Master ECU is responsible for life-cycle management in the vehicle. It will wake up and shut down the PELUX based system.

  • The Vehicle-CPU is connected to the vehicle backbone, and is responsible for power mode management on the ECU which the PELUX based system is deployed on. The V-CPU will be used as trigger to wake up the system when there is traffic on the vehicle bus.

  • Mass storage devices such as flash memory devices connected via USB or a SD-slot can, aside from being played from, also be used to trigger firmware update procedures of e.g. navigation map data and graphical assets for icons representing radio stations.

  • Optical devices such as CD/DVD/BD disc players may, aside from being played from, also be used as a trigger to wake up the system. For example by inserting a new disc in the slot.