download deliverable - AIDE

Deliverable D4.2.1 Dissemination Level PU Contract N. IST-1-507674-IP
• Improves the scalability of the architecture, since applications do not have to be
changed for different system configurations (as well as during the integration phase
and during the runtime (field) phase).
• Application development is independent from the system behaviour and the ICA
module, since no explicit priorities values have to be fed by the application to the ICA
module. Therefore the architecture fulfils the requirement of modularity.
• The applications and the context can be objectively categorized.
• The generalized categorizations of the context and characteristics of application I/O
reduce the complexity to be handled.
Thus, central intelligence module of AIDE recognises an application in an abstract way,
according to the provided action parameters. AMI-C’s intelligent kernel, on the other hand,
has to know exactly the application.
With respect to the dialogues priority class, it was argued that no conflict should be
considered involving dialogues, since a user-initiated action signifies that the driver considers
himself as capable of accomplishing the action. This is more obvious in situations where the
initiator of the action is a passenger instead of the driver.
Commenting on the metafunctions, it was argued that the action scheduling regarding
visual messages should take into account the existence or not of a fellow-passenger in the
front seats. It was also mentioned that most of the cars involve IVIS functions in a passengeroriented
way.
Dialogues should not be confused with output messages. Dialogues represent the
initialization of a driver initiated action. It is when the driver starts a dialogue that the system
should allocate an I/O device and this is the crucial moment for prioritization.
3.9.3. Towards DVE-dependent HMI adaptation within AIDE
In order to adapt the system reaction to different aspects of availability, ability and
traffic/environment conditions, in a personalized way, a Driver-Vehicle-Environment state
was defined based on the considered dimensions of availability, ability and
traffic/environment factors. There is no inherently “correct” set of DVE parameters since the
relevant aspects are dependent on the HMI- and adaptation-strategy of the OEM. Thus, for the
AIDE system, the relevant DVE parameters are those that are needed for implementing the
defined (meta-) functions and scenarios. For example, if AIDE should implement adaptation
of warning timing to driver distraction, we must be able to measure the DVE parameter
distraction (which has to be clearly operationally defined). The selected DVE state
dimensions are the followings: primary task demand, distraction, driver impairment,
traffic/environment risk, driver intent and driver profile.
25/07/2005 32 ICCS