download deliverable - AIDE

Deliverable D4.2.1 Dissemination Level PU Contract N. IST-1-507674-IP
• Adaptation to the driver state and /or the driving situation (DVE);
• Integration of nomad devices.
Considering those aspects the system has to offer central functionality which coordinates the
I/O events and interacts with the main known components of the system (applications, I/O
devices, etc.). Within AIDE this central functionality is called AIDE meta functions and are
listed below:
• Derive action priority;
• Conflict recognition depending on actions / conditions (not I/O devices);
• Scheduling according to the driver/environment model;
• Channel and modality selection and device allocation;
• Changing information strategy depending on conditions.
Results in:
- Terminate actions;
- Interrupt actions and resumption of actions;
- Include pauses.
- Delay actions;
- Modality/channel selection;
- Modality/channel alteration;
- Change spatial layout (location of output);
- Change physical layout (volume, size, form, colour).
Thus the applications have to make available some additional functions like delaying
or interrupting outputs or choosing a subset of the possible output modalities.
These additional functions must be integrated in the in-vehicle information system
taking into account a variety of crucial requirements. The HMI is a strong competitive factor
for the car manufacturers and there is no "best" in-vehicle HMI strategy. Therefore the HMI
strategy is OEM specific.
In addition to that, the amount of applications (IVIS and ADAS) and also the amount
of I/O devices depends on the vehicle segment and differs much.
As a conclusion, the most important requirements for such a system are flexibility in
terms of the HMI strategy and scalability in terms of the amount of applications and I/O
devices.
In order to concentrate on the discussions on the architecture no more requirement
issues were considered in this session.
3.10.2. AIDE architecture:
Within the AIDE project a HMI software architecture will be developed which focus
on I/O management and adaptive assistance for the driver. The results should be used to
initiate or to support a standardisation initiative like AUTOSAR or ISO. Additionally the
architecture has to be harmonised with other running IP's like EASIS, GST, Prevent, etc.
Thus, as a result of the architecture work the following can be expected:
25/07/2005 34 ICCS