SP3-26 Elderly driver discomfort detection -
Context of use (aim)
|
To automatically detect driver discomfort and adapt his/her driving environment and task accordingly.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
| -
Connected UCs
|
Input to A3.4.2 for adaptation.
| -
Priority Level
|
√ Secondary
| -
Scenario(s)
|
The system detects driver discomfort through posture, seat pressure, temperature and other sensors (i.e. body/side camera detecting yawning or characteristic driver actions). The system then adapts automatically the seat position/shape and other elements and provides feedback to A3.4.2 to adapt some driving tasks support levels. No feedback is given to the driver. All adaptations take place when the vehicle is stationary (i.e. at a stop, or traffic light, etc.). No relevance to accidents or connection to pre-crash systems is envisaged.
| -
System output
|
Adaptation of driving environment/task.
| -
Relevant OASIS WP
|
WP3.4 (A3.4.3)
| -
Services involved
|
Driver comfort support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Driver seat, other …
|
11b. Sensor devices & restrictions
|
In-vehicle navigation system (on-board) and/or PDA-based navigation (off-board)
|
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Driver comfort support
|
Over 80% successful detection of driver discomfort.
|
| -
Environmental restrictions
|
Driver driving over 30 minutes, alone in the car.
| -
Interaction level
|
Step 1 – the system detects excessive driver discomfort.
Step 2 – the system adapts the seat and potential other key vehicle comfort elements and provides less/more support to the driving task by A3.4.2 modules.
| -
Personalisation/ adaptation level
|
No
| -
Quality of service indicators
| -
100% reliability of adaptation once the problem is detected
-
80% right detection of driver discomfort (sensitivity over 80%)
-
Less than 10% false detection of driver discomfort (specificity over 90%).
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
| -
Background info/ reason on selection and on assigning the priority level
|
Uncomfortable seat posture may not be detected easily by some elderly drivers (and is not detected at all by some lower limb amputees, paraplegics and tetraplegics), causing driving errors and discomfort on long journeys.
| -
References
|
SAFEGUARD (QLRT-1999-30235) Deliverables 1.1 and 2.1.
TRANSWHEEL (DE 3013/2) Deliverable 5.1.
| -
Comments
|
|
Figure 88: SP3-26 Elderly driver discomfort detection
SP3-27 Task dependent driving environment adaptation
-
Context of use (aim)
|
To automatically (but following user permission) adapt key driving environment status (i.e. lights, mirror, position, windscreen wipers), according to the driving conditions, to enhance elderly driver safety and comfort.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
| -
Connected UCs
|
A3.4.2 module
| -
Priority Level
|
√ Secondary
| -
Scenario(s)
|
The system automatically detects the need for adaptation of key vehicle parameters due to environmental conditions (i.e. turn on lights when in tunnel, turn them off when out of tunnel at day, putting the inside mirror in anti-glare position if a following car uses fog lights, etc.) and suggests them to the elderly driver. If he/she accepts they are changed, if not they remain as they are.
| -
System output
|
Adaptation of key vehicle parameters, according to traffic environment, upon driver permission.
| -
Relevant OASIS WP
|
WP3.4 (A3.4.3)
| -
Services involved
|
Driver comfort support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Car mirrors, lights, …
|
11b. Sensor devices & restrictions
|
External light (front, back) sensors, rain sensor at windscreen, …
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Driver comfort support
|
Over 80% successful detection of driver discomfort.
|
| -
Environmental restrictions
|
-
| -
Interaction level
|
Step 1 – the system detects that a vehicle parameter (lights, mirrors) status must be modified and suggests it to the driver.
Step 2 – the driver accepts/rejects.
Step 3 – the status is changed or remains unchanged
| -
Personalisation/ adaptation level
|
Yes:
static parameters: selecting for which subsystems this function will be allowed/default
| -
Quality of service indicators
| -
100% reliability of suggested change (always rights)
-
100% reliability of following the driver’s choice.
| -
Potential input needed from other UCs (what input, which UCs?)
|
| -
Important accessibility attributes (per UG)
|
| -
Background info/ reason on selection & on assigning the priority level
|
Several elderly drivers react slowly to changes of lighting, gradually emerging darkness, fog, etc.
| -
References
|
AGILE (QLRT2001-00118) Deliverable 2.1.
| -
Comments
|
|
Figure 89: SP3-27 Task dependent driving environment adaptation
-
-
Context of use (aim)
|
To automatically detect the driver stress level and in case of exceeding predefined thresholds to adapt his/her driving environment and task.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Public / private Social security service providers and insurance companies
Service Centre (to potentially call for support)
| -
Connected UCs
|
Input to A3.4.2 and A3.3.4 for adaptation.
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The system monitors unobtrusively key user parameters (such as EMG, ECG, respiration, …) through the seat (and potentially also through steering wheel, wrist or other sensors) and calculates an overall stress level indicator. In case this is above a certain threshold (threshold 1-cautionary) it adapts the driving environment (i.e. seat shape, position, ventilation, …) and task (i.e. interfacing to route guidance of A3.3.4 or other telematic services of A3.4.2). If it overpasses another threshold (threshold 2 – imminent danger), it needs to notify the user and - potentially – also call for assistance, by operating the eCall and service router connection of A3.4.2.
| -
System output
|
Adaptation of driving environment/task, driver warning, call for support or help (depending upon level of stress detected).
| -
Relevant OASIS WP
|
WP3.4 (A3.4.3)
| -
Services involved
|
Driver comfort support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Seat, steering wheel, other….
|
11b. Sensor devices & restrictions
|
Sensing seat (with EEG, GSR, temperature, …), wrist sensor (EMG), temperature, other,…
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Driver comfort support
| -
Over 80% successful detection of stress
-
100% reliability in providing driving environment/task adaptation or call for help, once detection is achieved
|
| -
Environmental restrictions
|
Driver equipped with necessary sensor, driving over 15 minutes
| -
Interaction level
|
Step 1 – the system detects a problem; if it is cautionary and below the imminent danger level it adapts the driving environment/task silently. If it is above the imminent danger level it informs the driver and seeks for driver permission to call for help.
| -
Personalisation/ adaptation level
|
No
| -
Quality of service indicators
| -
100% reliability of reaction once a problem is detected.
-
80% correct detection of positive stress (sensitivity over 80%).
-
Less than 10/5% false detection of cautionary/imminent stress in case of no stress (specificity over 85%).
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
Elderly-friendly warning of high stress levels, to avoid panic or over reaction or further stress creation.
| -
Background info/ reason on selection and on assigning the priority level
|
Several studies have found the lethal connection between stress (acute or chronic) and traffic accident danger, plus the possibility of causing other health related problems, especially to elderly drivers.
| -
References
| -
SENSATION (507231) Deliverable 1.1.2.
-
Brookhuis KA, de Waard D. Assessment of driver’s workload: performance and subjective and physiological indexes. In: Stress, Workload, and Fatigue, edited by Hancock, PA, Desmond PA. Lawrence Erlbaum Ass, Mahwah, New Jersey, 2001; 321-333.
-
Fernandez Raul and Picard Rosalind W.. Modeling drivers’ speech under stress. Speech Comm, 40(1-2):145–159, 2003.
-
Green RG. Stress and accidents. Aviat Space Environ Med 1985:56:638-641.
| -
Comments
|
|
Figure 90: SP3-28 Elderly driver stress detection
Tourism and leisure SP3-29 Get tourist info on POI/event/trip in your city
-
Context of use (aim)
|
The aim is that the elderly user can find information, according to his/her explicit and implicit (according to past selections) preferences, about POIs/events/trips in his/her home city.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Leisure and re-creation service providers
Infotainment service providers
Elderly associations
National, local and regional authorities
Other: public transport content providers
| -
Connected UCs
|
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The user will search for events, POIs and trips in his/her city.
| -
System output
|
The system must provide, according to user preferences:
-
Info on events (both implicit and explicit preferences will be taken into account, e.g. if the user has an interest in operas, info will be given if an opera artist is at the city during, etc.).
-
Info on POIs (if the user has asked for e.g. a restaurant or a sport event, the user’s preferences will be taken into account)
-
Info on trip (multimodal) in order to reach the event/POI (suggested above, taking into account his/her preferences on favourite/less favourite transportation means, cost of the trip, etc.)
The provided information will be: up to 5 solutions for mobile phone, up to 10 for PDA, up to 20 for PC.
| -
Relevant OASIS WP
|
WP3.4 (A3.4.4)
| -
Services involved
|
Transport information
Leisure and social activities support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
OASIS device (PDA, mobile phone, etc.)
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Accuracy of info on the appropriate transportation means to use and combinations and correct timetables
|
Route guidance
|
|
Driver telematic support
|
|
Driver comfort support
|
|
Tourism support
|
|
Leisure and social activities support
|
Reliability of info on POIs and events (regarding correct address, starting time, etc.) in the city
|
Smart workplaces
|
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – the user wants to get info on events/POIs of his/her interest in his/her home town.
Step 2 – the system searches and filters the content of connected providers and gives feedback on alternative solutions (up to 5 for mobile phone, up to 10 for PDA, up to 20 for PC) to the user, taking into account his/her implicit and explicit preferences (including accessibility info, if relevant).
Step 3- the user wants to see info on the optimal transportation to reach this place.
Step 4 – as in step 2, the system gets the info from the connected providers and informs the user accordingly (including accessibility info, if relevant).
| -
Personalisation/ adaptation level
|
Yes:
static parameters
dynamic parameters: user’s preference oh event types, transportation mean, price level, etc.
| -
Quality of service indicators
|
Accuracy of provided info on e.g. event dates and starting times, transportation means timetables, etc.
Reliability of provided info.
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
Accessibility of POIs, events places, transportation, in case the user has a specific problem.
| -
Background info/ reason on selection and on assigning the priority level
|
One of the main activities of autonomous mobility (which is a key issue for independent living) is travelling. All of us want to have a priori info on POIs/events/trips, but this is a need for elderly people, taking into account their physical health problems which put barriers in many activities.
| -
References
|
| -
Comments
|
|
Figure 91: SP3-29 Get tourist info on POI/event/trip in your city
SP3-30 Get tourist info on POI/event/trip to another city/country
-
Context of use (aim)
|
The aim is that the elderly user can find information, according to his/her explicit and implicit (according to past selections) preferences, about another city/country that s/he wishes to visit.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+) - some
| -
Secondary actor(s)
|
Leisure and re-creation service providers
National, local and regional authorities
Other: public transport content providers
| -
Connected UCs
|
Social community UCs of SP2 (i.e. SP2-36 – SP2-43)
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The user will insert in the OASIS device the place he/she wishes to visit.
| -
System output
|
The system must provide, according to user preferences:
-
Info on hotels (implicit preferences will be taken into account on hotel level)
-
Info on transportation and timetables (implicit preferences will be taken into account, e.g. on favourite/less favourite transportation means, preference on time of the day for travelling, etc.)
-
Info on touristic attractions (both implicit and explicit preferences will be taken into account, e.g. if the user is interested on modern art museums only, then info on such museums will be provided)
-
Info on events (both implicit and explicit preferences will be taken into account, e.g. if the user has an interest in operas, info will be given if an opera artist is at the specific city during his/her stay, etc.)
The provided information will be: up to 5 solutions for mobile phone, up to 10 for PDA, up to 20 for PC.
| -
Relevant OASIS WP
|
WP3.4 (A3.4.4)
| -
Services involved
|
Transport information
Tourism support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
OASIS device (PDA, mobile phone, etc.)
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Accuracy of info on the appropriate transportation means to use and correct timetables
|
Tourism support
|
Reliability of info on hotels, touristic POIs (attractions), etc. in cities/countries
|
Leisure and social activities support
|
Reliability of social events info
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – the user wants to find info on a place to visit (as tourist). First he/she asks on hotels of his/her preference.
Step 2 – the system searches and filters the content of connected providers and gives feedback on alternative solutions (up to 5 for mobile phone, up to 10 for PDA, up to 20 for PC) to the user, taking into account his/her implicit and explicit preferences (including accessibility info, if relevant).
Step 3- the user wants to see info on the optimal transportation to reach this place.
Step 4 – as in step 2, the system gets the info from the connected providers and informs the user accordingly.
Step 5 – the users asks for attractions in the specific city.
Step 6 – the system, after connecting to the appropriate content providers, returns to the user filtered info that matches his/her preferences.
Step 7 – in all the above information retrieval, the system stores the user’s selections and takes them into account for future use.
| -
Personalisation/ adaptation level
|
Yes:
static parameters
dynamic parameters: user’s preference oh hotel level, transportation mean, price level, etc.
| -
Quality of service indicators
|
Accuracy of provided info on e.g. hotel prices, transportation means timetables, etc.
Time to retrieve the info below 30sec.
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
Accessibility of hotels, POIs, transportation, in case the user has a specific problem.
| -
Background info/ reason on selection and on assigning the priority level
|
One of the main activities of autonomous mobility (which is a key issue for independent living) is travelling. All of us want to have a priori info on POIs/events/trips, but this is a need for elderly people, taking into account their physical health problems which put barriers in many activities.
| -
References
|
| -
Comments
|
This should also be connected with the social community uce cases from SP2, as this could be pushed through the interface in the community activities.
|
Figure 92: SP3-30 Get tourist info on POI/event/trip to another city/country
SP3-31 Get/give evaluation on a POI/event/trip to your/another city/country
-
Context of use (aim)
|
The aim is that the elderly user can find the opinion of other users or insert his/her opinion regarding the evaluation of a POI/event/trip for his/her or another city/country.
| -
Primary actor
|
Υoung elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
√Elderly associations
| -
Connected UCs
|
| -
Priority Level
|
Supportive
| -
Scenario(s)
|
The user will search the appropriateness of a POI/event/trip, based on the ratings of other users/visitors.
The user will insert his/her opinion about the appropriateness of a POI/event/trip, that he/she recently visited/performed.
In both cases, accessibility attributes will be included.
| -
System output
| -
Info on the evaluation of POIs/events/trips (e.g. hotels, museums, concerts, transportation means, etc.)
-
UI for the insertion of personal evaluation of POIs/events/trips.
| -
Relevant OASIS WP
|
WP3.4 (A3.4.4)
| -
Services involved
|
Tourism support
Leisure and social activities support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
OASIS device (PDA, mobile phone, etc.)
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Tourism support
|
User satisfaction of this service over 70% (against no other user opinion option)
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – the user wants to find info on the evaluation of POI/event/trip by other users and he/she enters the search criteria (town, POI/event/trip name, accessibility attributes, etc.).
Step 2 – the system returns the stored evaluations that match the user’s search criteria.
Step 3- the user wants to insert his/her own evaluation for the POI/event/trip.
Step 4 – the system stores the user’s input.
| -
Personalisation/ adaptation level
|
No
| -
Quality of service indicators
| -
Info retrieved in less than 30 sec.
-
Ability to view all comments of other users in an easy and sequential way (i.e. scrolling) and also get a mean (indicative) score on each POI/transportation//event as a ‘mean’ value of other users opinions.
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
Accessibility info at the evaluation forms (of hotels, events, transportation) in case the user has a specific problem.
| -
Background info/ reason on selection and on assigning the priority level
|
Finding other users’ opinion on the same POI/event/trip that you are interested is a good-to-have service, however, not vital for the everyday autonomous living of the elderly.
| -
References
|
| -
Comments
|
|
Figure 93: SP3-31 Get/give evaluation on a POI/event/trip to your/another city/country
SP3-32 Be informed when a member in the contact list enters an Activity Space
-
Context of use (aim)
|
The aim is that the elderly user is informed when a person he/she knows enters a physical activity space (café, restaurant, cinema, etc.) and start communicating (exchange messages, place VoIP calls, participate in e-games, etc.).
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+) – some people
| -
Secondary actor(s)
|
Family members
Leisure and re-creation service providers
| -
Connected UCs
|
| -
Priority Level
|
√ Secondary
| -
Scenario(s)
|
The user is informed when one of his/her connected friends enters an Activity Space and is able to communicate with him/her through the OASIS-enabled device. Could be also a link between an elderly person and his/her family to boost communication between them.
| -
System output
| -
Notification to the user when a person from the network enters an Activity space.
-
Upon user’s request, placing of a VoIP call with the other person, or/and allowing to share an e-game, or/and allowing message communication.
| -
Relevant OASIS WP
|
WP3.4 (A3.4.5)
| -
Services involved
|
√Leisure and social activities support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
OASIS device (PDA, mobile phone, etc.)
|
11b. Sensor devices & restrictions
|
Tracking devices of OASIS-enabled device, SUN SPOTs.
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Leisure and social activities support
|
Reliability of info when informing on the presence of a connected user to an Activity Space.
Fast transmission of messages and communication
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – a person connected to the network enters an Activity Space.
Step 2 – the system ask this person for permission to inform his/her network about it. If the person agrees:
Step 3 - the system notifies the user (belonging to the network) through his/her OASIS device.
Step 4 – the user sends a message to the connected person, through his/her device.
Step 5 – the system transmits the message to the connected person.
Step 6 – the user initiates a VoIP call to the connected person.
Step 7 – the system establishes the VoIP connection.
Step 8 – the connected person invites the user for an e-game
Step 9 – the system notifies the user and the e-game starts
| -
Personalisation/ adaptation level
|
No
| -
Quality of service indicators
|
On-time notification of the presence of a connected user to an AS.
Fast communication between the users.
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
| -
Background info/ reason on selection and on assigning the priority level
|
Socialising is an important activity for the elderly, however it is not vital for their everyday life. Thus, it is assigned a priority level ‘secondary’.
| -
References
|
| -
Comments
|
|
Figure 94: SP3-32 Be informed when a member in the contact list enters an Activity space
Share with your friends: |
