F5.11.7 Provide In-vehicle eCall Facilities

Header Image
Project:
F5.11.7 Provide In-vehicle eCall Facilities : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:35
Modified: 08.09.2021 14:46:59
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to provide facilities that enable an eCall message to be automatically sent to the Public Safety Answering Point (PSAP) by the Host Vehicle that has detected that it has been involved in an accident.<br/>(2) The ability to include the following data objects in the eCall message: VIN, current and previous Host Vehicle locations, Host Vehicle position can be trusted, direction in which the Host Vehicle is moving, fuel type, number of occupants, some basic information on the reason for the call, e.g. it is a real call, or a test call<br/>(3) The ability to check the current location of the Host Vehicle based on its own input from the Location Data Source.<br/>(4) The ability to send an eCall message to the PSAP either as a result of input from a Host Vehicle occupant, or automatically by the Driver monitoring system.<br/>(5) The ability for the Driver to cancel the automatic initiation of the eCall message.<br/>(6) The ability to display call acknowledgement messages from the Mobile Network functionality and the PSAP to the Driver and other occupants (if any) in the Host Vehicle.<br/>(7) The ability to re-send the eCall message if the Mobile Network functionality returns a "message failed" indication.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
  • Other Links
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» pshvs.psef_eCall_message
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F5.11 Provide Driver Monitoring and eCall
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tv.hmi-eCall_response
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_eCall_information
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_request_driver_condition
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 7.6.1.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_driver_failed
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_driver_condition
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 8.5.1.3
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 5.1.0.6
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fv.hmi-initiate_eCall
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psef.pshvs_eCall_first_acknowledgement
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 5.3.0.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 8.5.1.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psef.pshvs_eCall_message_failure
FRAME_Low_Level_Data_Flow «owned by»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 5.3.1.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 5.3.1.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.6.1.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psef.pshvs_eCall_responses
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 8.5.1.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 8.5.1.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» flds-vehicle_position_for_eCall
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_data_for_eCall
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 5.3.0.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) when one of the accident detection data flows is received, the information on the reason for the call, and the current location of the vehicle is collected;<br/>(b) a request is made to the Operational Data Store management Function for data objects about the condition of the Driver;<br/>(c) check the location of the Host Vehicle provided in (a) above against the data objects received from the Location Data Source and if similar add a high confidence rating for the position of the Host Vehicle to the data.<br/>(d) check for any "cancellation" input data objects from the Driver's HMI.<br/>(e) a data flow containing the eCall message is sent to the eCall Management functionality;<br/>(f) a data flow is sent to the Vehicle Systems in the Host Vehicle via the Vehicle Communications functionality;<br/>(g) when the first reply is received from the PSAP, an acknowledgement that the call is being processed is output via the Driver's HMI in the eCall information data flow;<br/>(h) when the final reply is received from the PSAP, again a response is output via the driver's HMI in the eCall information data flow<br/>(i) if as a result of (e) a "message failed" response is received from the PSAP, repeat (e).<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0
Object Type Connection Direction Notes
Send out eCall Object Realization To  
Recieve eCall Call Object Realization To