Overview

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.

Functional Requirements

(a) continuously monitor for the receipt of each of the input data flows
(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
(c) check the location with each of the acknowledgement data flows received in (a)
(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)
(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.

Diagrams

Parent Higher Level Function

• 5.13 Provide Vehicle Data and ISA

Input logical dataflows

• pshvs_current_vehicle_time_for_fcd
• pshvs_ISA_acknowledgement
• pshvs_lane_command_response
• pshvs_legal_speed_acknowledgement
• pshvs_route_information_for_xfcd
• pshvs_status_data_for_fcd
• pshvs_vehicle_ID_for_fcd
• pshvs_vehicle_position_for_fcd

Output logical dataflows

• pshvs.mt_inter-urban_floating_car_data
• pshvs.mt_inter-urban_xfcd
• pshvs.mt_urban_floating_car_data
• pshvs.mt_urban_xfcd
• pshvs.psle_service_notification
• pshvs_vehicle_speed_for_safety_behaviour
• pshvs_xfcd_for_other_vehicle
• pshv_xfcd_for_fusing

User needs