F5.13.7 Prepare Extended Floating Car Data

Frame Repository / Frame Functional View / Functionality / Functional Area F5 - Provide Support for Host Vehicle Systems / F5. Provide Support for Host Vehicle Services / F5.13 Provide Vehicle Data and ISA / F5.13.7 Prepare Extended Floating Car Data

Project:

F5.13 Provide Vehicle Data and ISA

F5.13.7 Prepare Extended Floating Car Data : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:35
Modified:	08.09.2021 14:47:00

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{F8A8D2D4-3882-4eb5-9ACB-1D0D2F3403D0}
Appears In:	DFD F5.13 Provide Vehicle Data and ISA, Functional Tree of Area F5 Provide Support for Host Vehicle Services

This Function shall be capable of providing the following facilities: (1) The ability to use the inputs received from other functionality to produce data about the Vehicle such as its current speed, location, identity plus other information such as road and traffic states, location on a Vehicle Trip Plan, e.g. at a way point. (2) The ability to send this data to the Manage Traffic and Provide Traveller Journey Assistance functionality in the System, as well as to the Monitor Vehicle Safety Behaviour Function. (3) The ability to send the data to the Monitor Vehicle Safety Behaviour Function either at periodic intervals or triggered by events, depending on how often the input (raw) data changes so that Vehicles become probes within the road network. (4) If data about such things as road friction, aquaplaning, Vehicle breakdown and traffic incidents are not provided by the Vehicle systems, the ability to attempt to determine them from the data that it has received. (5) The ability to compose and send acknowledgement messages resulting from instructions received by Vehicles and displayed to Drivers. (6) The ability to send acknowledgement messages resulting from instructions received by Vehicles and displayed to Drivers to the Law Enforcement functionality in case there is a violation is detected as a result of instructions sent to Drivers.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» pshvs.mt_inter-urban_floating_car_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_xfcd_for_other_vehicle FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.mt_urban_floating_car_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_xfcd_for_fusing FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.mt_urban_xfcd FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_speed_for_safety_behaviour FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F5.13 Provide Vehicle Data and ISA FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.psle_service_notification FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.mt_inter-urban_xfcd FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.5.1.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_lane_command_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.6.2.14 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.10 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.15 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_current_vehicle_time_for_fcd FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_legal_speed_acknowledgement FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 8.5.3.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_route_information_for_xfcd FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_status_data_for_fcd FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_ID_for_fcd FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_position_for_fcd FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_ISA_acknowledgement FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously monitor for the receipt of each of the input data flows;<br/>(b) use the contents of the vehicle position for fcd, vehicle ID for fcd, status data for fcd and current time 2 data flows to prepare the eXtended Floating Car Data (XFCD);<br/>(c) check the location with each of the acknowledgement data flows received in (a);<br/>(d) if the status data for fcd data flow does not include sufficient data to provide what is expected to be contained in extended floating car data, review the data and deduce such things as road conditions, such as reduced road friction or aquaplaning and traffic conditions, such vehicle breakdown, traffic incident (i.e. congestion);<br/>(e) when (b), (c) and (d) are complete, use the data they have provided in each of the output data flows and send them to their respective functions in the other Functional Areas and to the Monitor Vehicle Safety Behaviour function.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0