1221 - Arhip Gabriel Daniel - Laborator - Vfinal

Definirea USERS NEEDS
Număr grup Denumire activitate
2 Management Activities
2.1 Transportation Planning support
2.1.2 Planning
The system shall be able to model the

road network for strategic planning
2.1.2.1
calculations, e.g. to make best use of the
existing road infrastructure.
The system shall be able to model the
road network for strategic planning
2.1.2.1
calculations, e.g. to make best use of the
existing road infrastructure.
The system shall be able to develop and
implement traffic environmental
2.1.2.2
management strategies based on current
and predicted traffic conditions.
The system shall be able to develop and
implement traffic environmental
2.1.2.2
management strategies based on current
and predicted traffic conditions.
2.1.2.3 The system shall be able to assist in the
planning of (inter-modal) routes.
2.1.2.3 The system shall be able to assist in the
planning of (inter-modal) routes.
The system shall be able to simulate a
2.1.2.4 demand management strategy on the road
network.
The system shall be able to simulate a
2.1.2.4 demand management strategy on the road
network.
The system shall be able to simulate
2.1.2.5 potential capacity reduction, e.g. due to
road works.
The system shall be able to simulate
2.1.2.5 potential capacity reduction, e.g. due to
road works.
3 Policing / Enforcing
3.1 Policing/Enforcing Traffic Regulations
Evidence Collection
3.1.1
The system shall be able to collect
3.1.1.1 evidence on vehicles that commit traffic
signal violations.
The system shall be able to collect
3.1.1.2 evidence on vehicles that exceed a local
(variable) speed limit.
The system shall be able to measure
the characteristics, e.g. length,
3.1.1.3
weight etc., of a vehicle
automatically, whilst the vehicle is in
motion ("Weigh in Motion").
The system shall be able to identify the
3.1.1.4 cargo being carried by a heavy goods
vehicle automatically.
Financial Transactions
4
4.1 Electronic Financial Transactions
4.1.2 Revenue Sharing

The system shall be able to share
4.1.2.1 revenues between road network
operators.
The system shall be able to share
4.1.2.1 revenues between road network
operators.
The system shall enable a single payment
4.1.2.2 to be paid for services offered by different
related transport systems (e.g. metro, bus,
train, road and parking).
5. Emergency Services
5.2.0 Basic Services
The system shall support a green wave for

5.2.0.1
emergency vehicles.
The system shall inform the TCC about
5.2.0.2
the route that is intended for each green
wave before it is used.
The system shall provide the identity of
each traffic signal at which priority is
5.2.0.3
needed, and the 'timing window' in which
priority is to be given.
The system shall receive an indication
from the emergency vehicle of its need to
5.2.0.4 be given priority at each set of traffic
signals before its arrival in the immediate
vicinity.
6. Travel Information
6.1.2 Information Handling

The system shall inform the User when
6.1.2.1 changes occur to the criteria upon which
the pre trip information had been given.
The system shall be able to provide

access information for those travellers
with special needs (e.g. physical access,
6.1.2.10
lifts, escalators, parking & toilets, nappy
changing rooms, access for (guide) dogs,
etc.) at relevant areas, e.g. transit areas.
6.1.2.11 information about "Points of Interest",
e.g. location, opening times, price of
service, nearest transport service points.
The system shall be able to receive
information about a point of interest from
6.1.2.12
the providers/owners/managers of that
"Point of Interest".
information to travellers so as to
influence their choice of destination
6.1.2.13 and/or mode of travel, e.g. to protect the
environment of a "Point of Interest", or
geographic area.
6.1.2.13 and/or mode of travel, e.g. to protect the
environment of a "Point of Interest", or
geographic area.
6.1.2.14 information to travellers about the
personal support services, e.g. doctor, in
a specific locality.
The system shall be able to receive

information about a personal support
6.1.2.15 service, e.g. doctor, from the
providers/owners/managers of that
service.
information on the cancellation of
departures from an inter-modal
6.1.2.2 interchange (e.g. railway station, an
airport , a port or a coach station) due to
the weather; strikes or other reasons.
information to all drivers including route
6.1.2.3
restrictions, travel times, etc.
The system shall be able to support a

database of events with links between
6.1.2.4 events that occur concurrently and at the
same or adjacent locations.
The system shall be able to analyse,
process and retrieve data from different
6.1.2.5
combinations of sources (including
floating car)
The system shall be able to provide road
The system shall be able to provide road
and traffic information adapted to
6.1.2.6 different classes of users, e.g. travellers,
radio broadcasters, service operators.
The system shall provide information

6.1.2.7 using graphical representation or text.
Graphical form shall include the use of
maps as well as text.
The system shall provide information
6.1.2.7 using graphical representation or text.
Graphical form shall include the use of
maps as well as text.
The system shall provide information in

the native language at the output
location, and/or from a user selected
6.1.2.8
choice of other appropriate foreign
languages.
The system shall provide Information
6.1.2.9 Management tools for the operator.
Traffic
7 Manag
ement
7.1 Traffic Control
Lane
7.1.10 Management
The system shall be able to reserve

certain traffic lanes exclusively to specific
7.1.10.1 classes of vehicles (e.g. high occupancy
vehicles, or buses) and to detect violators.
.
The system shall be able to reserve
certain traffic lanes exclusively to specific
7.1.10.1 classes of vehicles (e.g. high occupancy
vehicles, or buses) and to detect violators.
.
8.2
Autom
In-
ated
Vehicl
e
Vehicl
Syste
e
8 Operat
ms
ion
8.2.2 Lane
Keeping
The system shall provide support to
control the lateral dynamic behaviour of
the vehicle automatically, and keep the
8.2.2.1
vehicle within its current lane of the
carriageway.
The system shall provide support to the
8.2.2.2 driver with information, or active steering
support, to assist him/her to keep within
the current lane of the carriageway.
GRUPA : SRTIM 1221
Student : Arhip Gabriel Daniel
Functii asociate (Low level Parent Higher Level

function) Function
3.1.6.1 Process Road Network 3.1.6 Provide Traffic

Static Data Predictions
3.1.6.4 Manage Traffic Prediction
3.1.6.4 Manage Traffic Prediction Data Store
Data Store
3.1.1.5 Provide
3.1.1.5.17 Implement Urban Traffic Urban Traffic
Commands Management
Facilities
3.1.2.5 Provide Inter-
3.1.2.5.16 Implement Inter-urban urban Traffic
Traffic Commands Management
Facilities
3.1.1.7 Urban Traffic Data 3.1.1 Provide Urban
Management Traffic Management
3.1.2 Provide Inter-
Provide Inter-urban Traffic Data urban Traffic
Management Management
3.1.6.3 Create Traffic Predictions 3.1.6 Provide Traffic
with Simulation Methods Predictions
3.1.6.4 Manage Traffic Prediction 3.1.6 Provide Traffic
Data Store Predictions
3.1.6.5 Provide Traffic Predictions 3.1.6 Provide Traffic
Operator Interface Predictions
3.3.11 Simulate Demand
3.3 Manage Demand
Management Strategy
3.3.8 Produce Demand
3.3 Manage Demand
Management Strategy
3.3.11 Simulate Demand
3.3 Manage Demand
Management Strategy
3.3.8 Produce
3.3.8 Produce Demand Demand
Management Strategy Management
Strategy
7.2.1 Analyse Image 7.2 Identify Violator
7.2.2 Determine Violator ID 7.2 Identify Violator
7.3 Process Fraud

7.3.5 Sort Fraud Notifications
Notifications
7.3.6 Create File for use in 7.3 Process Fraud
Prosecution Notifications
7.2.1 Analyse Image 7.2 Identify Violator

7.2.2 Determine Violator ID 7.2 Identify Violator
7.3.5 Sort Fraud Notifications 7.3 Process Fraud Notifications

7.3.6 Create File for use in 7.3 Process Fraud
Prosecution Notifications
7.1.3 Get Vehicle Information 7.1 Detect Fraud
7.1.3 Get Vehicle Information 7.1 Detect Fraud
1.1.1 Create EP Contract 1.1 Set up Contract
1.1.2 Establish Contract Statistics 1.1 Set up Contract
1.4 Manage Operators'

1.4.1 Distribute Fees Revenue
Revenue
1.4.2 Credit Operator's Account
Revenue
1.4.3 Inform Operators on 1.4 Manage

Transactions Operators' Revenue
1.6 Manage Tariffs

1.6.1 Manage Tariffs
and Access Rights
1.1.1 Create EP Contract 1.1 Set up Contract
1.1.2 Establish Contract

1.1 Set up Contract
Statistics
1.1.3 Manage
1.1.3 Manage Service Data
Service Data
1.2 Manage User's
1.2.1 Load User's Account
Account
1.2.2 Debit User's

1.2.2 Debit User's Account
Account
1.3 Perform Electronic

1.3.3 Check User's Contract
Payment Transaction
1.3 Perform Electronic
1.3.4 Inform and Guide User
Payment Transaction
1.3.5 Compute Service

1.3.5 Compute Service Fee
Fee
1.4.2 Credit Operator's

1.3.7 Recover Fee
Account
1.4.1 Distribute Fees Revenue
Revenue
1.4.2 Credit Operator's Account pepf_operator_revenue
2.1.2 Manage
2.1.2.3 Plan Emergency
Emergency
Intervention
Intervention
2.1.7 Manage use of Emergency 2.1 Manage

Vehicle Emergencies
Vehicle Emergencies
2.1.2.3 Plan
Emergency
Intervention
Intervention
3.1.1.5 Provide Urban

3.1.1.5.17 Implement Urban
Traffic Management
Traffic Commands
Facilities

3.1.2.5.16 Implement Inter-urban
urban Traffic
Traffic Commands
Management Facilities
3.1.2.5.16 Implement Inter-urban
urban Traffic
Traffic Commands
2.1.2 Manage
Emergency
Intervention
Intervention

3.1.1.5.17 Implement Urban
Traffic Management
Traffic Commands
Facilities
Vehicle Emergencies
6.3.11 Monitor Trip Plan
6.3 Support Trip
Implementation for Traveller
6.5.7 Provide Traveller with Trip 6.5 Prepare Trip

Planning Interface Plan
6.6.1 Provide Traveller 6.6 Provide Traveller

Information Interface Information
6.5.3 Trip Planning
6.5.3.9 Plan Trip Details
6.5.7 Provide Traveller with Trip 6.5 Prepare Trip

Planning Interface Plan
6.6.1 Provide
6.6.1 Provide Traveller
Traveller Information
Information Interface
Interface
6.5.3.9 Plan Trip Details 6.5.3 Trip Planning
3.4 Provide
3.4.10 Output Environmental
Environmental
Information
Information
6.5.3.8 Collect Data About Road
6.5.3 Trip Planning
Traffic

6.6.1 Provide Traveller Information 6.6 Provide Traveller
Interface Information
6.6 Provide Traveller

6.6.2 Produce Travel Information
Information

6.6.3 Output Travel Information
Information
6.6.3 Output Travel Information
Information

6.3.11 Monitor Trip Plan
6.3 Support Trip
Implementation for Traveller
6.5.7 Provide Traveller with Trip

6.5 Prepare Trip Plan
Planning Interface
6.6.2 Produce Travel 6.6 Provide Traveller

Information Information
6.3.13 Provide Traveller Trip
6.3 Support Trip
Interface
3.2.11 Provide Operator

Interface for Incident 3.2 Manage Incidents
Management

6.5.3 Trip Planning
Traffic
5.13.7 Prepare Extended 5.13 Provide Vehicle
Floating Car Data Data and ISA
6.5.3.13 Provide Data & Routes

6.5.3 Trip Planning
to Fleet Operators & Drivers
6.5.3.3 Collect PT Data 6.5.3 Trip Planning

6.5.3 Trip Planning
Traffic
3.1.1.7 Urban Traffic Data Management

3.1.1 Provide Urban Traffic Management
3.1.2 Provide Inter-
3.1.2.9 Output Inter-urban Traffic Data
urban Traffic
Management

6.6.1 Provide Traveller Information Interface
Information
6.5.8 Enable Final Approval of Trip

6.5
Plan
Prepare Trip Plan
Information

Information
6.7 Manage General

6.7.1 Define Traveller's General Trip Preferences
Trip Preferences
6.5.3.7 Enable Operator Access to6.5.3
Tip Planning
Trip Planning
Data
6.7 Manage General

6.7.3 Enable Operator Access to Trip Information
Trip Preferences
6.8.2 Provide Trip Plan Management
6.8 Manage
OperatorTrip
Interface
Plans

3.1.1.5.19 Manage Urban Road Network
Traffic Management
Lanes
Facilities
3.1.1.5.8 Detect Urban Traffic Violations
Traffic Management
Facilities

3.1.2.5.17 Manage Inter-urban Road
urban
Network
TrafficLanes

3.1.2.5.8 Detect Inter-urban Traffic Violations
urban Traffic
5.12 Provide Vehicle
5.12.12 Collect Road Network Information
Communications
Interfaces
5.12 Provide Vehicle

5.12.7 Communicate with In-vehicle
Communications
Systems
Interfaces
Descriere functie
This Function shall receive road network static data from

both urban and inter-urban functionality and shall process it
so that it can be used as the road network model by the
Provide Traffic Simulation Engine Function. When the data
has been processed it shall be sent to the Manage Traffic
Simulation Data Store Function from where it can be
obtained by the Simulation Engine Function.
This Function shall manage the use of the store of Road
Traffic Simulation Data. It shall be able to load road network
model and traffic data from other functionality into the store
in a way that keeps the data consistent. For example there
may be more than one model of the same road network to
enable various road configurations to be assessed for the
effect on traffic. In addition the Function shall enable the
Provide Traffic Simulation Engine Function to obtain the data
it needs to run simulations for each road network model and
to store the results. The Function shall enable the Transport
Planner to have access to the data in the store in a
controlled manner so that changes can be made to the road
network model and the results extracted for output to other
functionality, either by specific request or following the
automatic generation of new results by the Provide Traffic
Simulation Engine Function. If necessary the Function shall
be able to exchange data from the store with similar
functionality in another instance of the System.
This Function shall provide traffic control facilities that
enable the most efficient use to be made of the urban road
network. The Function shall be able to implement control
strategies in a planned sequence according to the time of
day and day of week. It shall provide facilities to enable
these strategies to be overridden by the Road Network
Operator, by inputs requiring green wave routes to be
implemented for selected vehicles and by requests for
changes to the way that traffic is managed received from the
incident and demand management functionality. The
Function shall be able to use current, historic and predicted
traffic data from the urban network and to change its actual
control commands to take account of this data in real-time.
This shall enable the Function to continuously adapt its
control of the urban road network to suit the actual traffic
conditions, i.e. adaptive traffic control. The Function shall be
able to provide details of the current and previous modes of
control on some or all parts of the urban road network to
other functionality for output to the Road Network Operator.
Feedback of the results of commands sent to the output
actuation functionality shall be monitored by the Function so
that if necessary corrective action can be taken if commands
are not followed.
enable the traffic to be managed so that the most efficient
use is made of the inter-urban road network. The Function
shall be able to implement management strategies in a
planned sequence according to the time of day and day of
week. It shall be possible for these strategies to include
control of access to the inter-urban network (ramp metering),
plus commands to manage the use of lanes in the
carriageway (including the hard shoulder) and the maximum
speeds for vehicles in each lane. The Function shall enable
Operator, as well as by inputs from the incident, demand
and access management Functions and by requests for
access or use of particular lanes as part of a green wave
route request for Emergency Vehicles. The Function shall be
able to use current, historic and predicted traffic data from
the inter-urban network and to change its actual control
commands to take account of variations in this data in real-
time. This shall enable the Function to continuously adapt its
control of the inter-urban road network to suit the actual
traffic conditions. The Function shall be able to provide
details of the current and previous modes of control on some
or all parts of the inter-urban road network to other
functionality for output to the Road Network Operator.
actuation functionality shall be monitored so that if
necessary corrective action can be taken if commands are
not followed.
This Function shall manage the store of Urban Traffic Data.
It shall receive data about traffic conditions (e.g. traffic flows
and journey times) in the urban road network and car park
data from other Functions in the Manage Traffic Functional
Area and from other parts of the System. Where necessary,
the Function shall use the urban road network static data to
enable the traffic data to be collated, fused and stored in a
coherent way that makes it easy to retrieve it for particular
road segments, or larger parts of the urban road network.
Once the received data has been processed, it shall be
loaded into the store and distributed to other functionality in
the Manage Traffic Functional Area. Part of this other
functionality shall be responsible for the output of the
processed data to other parts of the System and to entities
outside the System.
This Function shall manage the store of Inter-urban Traffic
Data. It shall receive data about traffic conditions (e.g. traffic
flows and journey times) in the inter-urban road network and
service area data from other Functions in the Manage Traffic
Functional Area and from other parts of the System. The
Function shall use the inter-urban road network static data to
enable the traffic data to be collated, fused and stored in a
coherent way that makes it easy to retrieve it for particular
road segments, or larger parts of the inter-urban road
network. Once the received data has been processed, it
shall be loaded into the store and distributed to other
functionality in the Manage Traffic Functional Area. Part of
this other functionality shall be responsible for the output of
the processed data to other parts of the System and entities
outside the System.
This Function shall use a road network model and traffic
data to provide predictions of traffic conditions for the road
network. It shall use current and historical traffic data plus
road network data obtained on request from the Manage
Traffic Simulation Data Store Function. This data shall be
used as input to a simulation engine that will predict what the
traffic conditions shall be like as a result of various traffic
management strategies that are provided by the Transport
Planner, or have been used in the past in all or part of the
road network. These predictions may also include the need
for car park spaces and shall be produced at the request of
the Transport Planner or at regular intervals that the Planner
may specify. When completed the predicted traffic conditions
and associated strategies shall be sent back to the Data
Store management Function.
This Function shall manage the use of the store of Road
Traffic Simulation Data. It shall be able to load road network
model and traffic data from other functionality into the store
in a way that keeps the data consistent. For example there
may be more than one model of the same road network to
enable various road configurations to be assessed for the
effect on traffic. In addition the Function shall enable the
Provide Traffic Simulation Engine Function to obtain the data
it needs to run simulations for each road network model and
to store the results. The Function shall enable the Transport
Planner to have access to the data in the store in a
controlled manner so that changes can be made to the road
network model and the results extracted for output to other
functionality, either by specific request or following the
automatic generation of new results by the Provide Traffic
Simulation Engine Function. If necessary the Function shall
be able to exchange data from the store with similar
functionality in another instance of the System.
This Function shall provide an interface through which the
Transport Planner can perform various tasks. These include
the management of the operation of Provide Traffic
Simulation Engine Function and the modification of the road
network model through the Manage Traffic Simulation Data
Store Function. On request the Function shall enable the
Transport Planner to view both the simulation results and the
current road network data for all or any of the models plus in
the case of traffic data for varying periods of time and parts
of the road network.
This Function shall simulate the imposition of a demand
management strategy. It shall run at the request of the
Transport Planner who must specify the existing strategy
that is to be simulated. The Function shall provide the
results of its analysis to the Transport Planner Interface
Function.
This Function shall produce new demand management
strategies at the request of the Transport Planner. These
strategies shall be designed to encourage a re-distribution of
the use of travel modes away from the current highly used
mode(s). The Function shall use data about the current
usage of different modes. It shall assess these against
"rules" for distribution provided by the Transport Planner.
The resulting strategy shall be sent to the Manage Demand
Management Data Store Function for later use.
This Function shall simulate the imposition of a demand
management strategy. It shall run at the request of the
Transport Planner who must specify the existing strategy
that is to be simulated. The Function shall provide the
results of its analysis to the Transport Planner Interface
Function.
This Function shall produce new demand management
strategies at the request of the Transport Planner. These
strategies shall be designed to encourage a re-distribution of
the use of travel modes away from the current highly used
mode(s). The Function shall use data about the current
usage of different modes. It shall assess these against
"rules" for distribution provided by the Transport Planner.
The resulting strategy shall be sent to the Manage Demand
Management Data Store Function for later use.
This Function shall analyse the image sent by the Process
Fraud Notifications or Detect Fraud Functions. The analysis
shall be to determine the ID of the violator vehicle, and the
type of fraud (violation) involved. The Function shall then
send these elements to the Determine Violator ID Function.
This Function shall be charged with obtaining the identity of

the violator, i.e. the person who has committed the fraud
(violation). It shall do this by extracting data from the store
of User's Registration Data using the identification of the
violating Vehicle as the reference for the data. The Vehicle
identification shall be provided by another Function as input
to this Function.
This Function shall carry out the classification of the fraud

notifications received from the functionality in other Areas or
directly from the Detect Fraud Function. If the violator's
identity is not included in the notification, the Function shall
send the elements to the Identify Violator Function to get it.
The classification shall be done according to different
criteria: level of seriousness, field (road, financial,
commercial...) and repeat offence. All the elements
available on the fraud, with the parameters corresponding to
the different criteria, shall then be sent to the Establish
Prosecution File Function.
This Function shall send the file containing all the elements
necessary for the prosecution of the violator to the right Law
Enforcement Agency. As part of the process of preparing
the file, the Function shall check that the violation is not the
result of an instruction that has been given to and
acknowledged by a Driver. The Function shall also send the
resulting file, plus all the elements received, to the
functionality that stores fraud notifications. For violations
detected directly by other functionality in this Area, and
concerning freight vehicles, the Function shall also send a
fraud notification, including all the elements to functionality in
the Manage Freight and Fleet Operations Area.
This Function shall analyse the image sent by the

Process Fraud Notifications or Detect Fraud
Functions. The analysis shall be to determine the ID
of the violator vehicle, and the type of fraud
(violation) involved. The Function shall then send
these elements to the Determine Violator ID
Function.
This Function shall be charged with obtaining the identity of
the violator, i.e. the person who has committed the fraud
(violation). It shall do this by extracting data from the store
of User's Registration Data using the identification of the
violating Vehicle as the reference for the data. The Vehicle
identification shall be provided by another Function as input
to this Function.
This Function shall carry out the classification of the fraud

notifications received from the functionality in other Areas or
directly from the Detect Fraud Function. If the violator's
identity is not included in the notification, the Function shall
send the elements to the Identify Violator Function to get it.
The classification shall be done according to different
criteria: level of seriousness, field (road, financial,
commercial...) and repeat offence. All the elements
available on the fraud, with the parameters corresponding to
the different criteria, shall then be sent to the Establish
Prosecution File Function.
This Function shall send the file containing all the elements
necessary for the prosecution of the violator to the right Law
Enforcement Agency. As part of the process of preparing
the file, the Function shall check that the violation is not the
result of an instruction that has been given to and
acknowledged by a Driver. The Function shall also send the
resulting file, plus all the elements received, to the
functionality that stores fraud notifications. For violations
detected directly by other functionality in this Area, and
concerning freight vehicles, the Function shall also send a
fraud notification, including all the elements to functionality in
the Manage Freight and Fleet Operations Area.
This Function shall collect or measure some
information about a Vehicle to check that it is
complying with the rules enacted for the System. The
information shall be either that collected by
functionality in the other Functional Areas, or that
collected by other Functional Areas, but which is not
systematically checked. For example, the Function
shall collect information such as "weight in motion",
recording the weight per axle and total weight for
Freight Vehicles, and it shall ask the Manage Freight
and Fleet Operations Area to provide Freight
Vehicle's' speed records. It shall be possible for
information to be directly collected by the Function,
or received from the roadside actuators. The
information can be continuous (video record for
example), or discrete (weigh in motion). The
Function shall ask for the identification of the vehicle.
The Function shall receive guidelines about the way
to perform the controls from Functions in the Manage
Traffic Area.
This Function shall collect or measure some information
about a Vehicle to check that it is complying with the rules
enacted for the System. The information shall be either that
collected by functionality in the other Functional Areas, or
that collected by other Functional Areas, but which is not
systematically checked. For example, the Function shall
collect information such as "weight in motion", recording the
weight per axle and total weight for Freight Vehicles, and it
shall ask the Manage Freight and Fleet Operations Area to
provide Freight Vehicle's' speed records. It shall be possible
for information to be directly collected by the Function, or
received from the roadside actuators. The information can
be continuous (video record for example), or discrete (weigh
in motion). The Function shall ask for the identification of the
vehicle. The Function shall receive guidelines about the way
to perform the controls from Functions in the Manage Traffic
Area.
This Function shall allow the traveller to establish a contract
with an Electronic Fee Collection Operator, or a Service
Provider. It shall present the traveller with information about
the different types of services available, and record the
choices that have been made.
This Function shall process the different contracts made by

the travellers to produce statistical information for the
corresponding Electronic Fee Collection Operators, or
Service Providers.
This Function shall apportion the payments received

amongst the operators according to rules defined in the
store of Service Information Data.
This Function shall credit the accounts of the operators by
the amount that has already been calculated.
This Function shall allow the Operators, and Service

Providers to view all the transactions concerning the
services that they provide.
This Function shall maintain the store of "tariffs" Data with

information from the (Public Transport) Operators or Service
Providers. It shall be able to modify these tariffs with
messages from the Manage Traffic Area.
This Function shall allow the traveller to establish a contract
with an Electronic Fee Collection Operator, or a Service
Provider. It shall present the traveller with information about
the different types of services available, and record the
choices that have been made.
This Function shall process the different contracts made by

the travellers to produce statistical information for the
corresponding Electronic Fee Collection Operators, or
Service Providers.
This Function shall maintain the content of the store of

Service Information Data. It shall enable an Operator to
review the contents of the store, to add, delete, or amend
the contents. The Function shall also enable the contents of
the store to be updated by Service Providers.
This Function shall allow the traveller to credit his or her
Electronic Payment account. It shall display to the traveller
the different contracts available to that person, read the
information related to the desired transaction and check the
credit rating of the source account. If this account is credit
worthy, it shall credit the Electronic Payment account, and
notify this to the Financial Clearinghouse terminator, and to
the store of Transaction Data. If an attempt is made to credit
an account previously included in the black list, and if the
new balance is sufficient, a message shall be sent to the
“Credit Control” Function to remove this account from the
black-list.
This Function shall debit the traveller's Electronic Payment

account according to the recently performed transaction. If
the account becomes overdrawn a message is sent to the
“Credit Control” function.
This Function shall read the corresponding contracts, and

verify the access rights, based on the user's ID. In case of a
free ride request, the rest of the transaction shall be given
up.
This Function shall guide the traveller or driver to get the
precise definition of the service that he or she wants, and
the way that he or she wishes to pay for it. It shall enable
them to select the appropriate contract, inform them about
their rights to use the service, and display the associated
price. This Function may be activated by Functions in either
the Manage Public Transport Operations Area or the Provide
Traveller Journey Assistance Area, or even directly for
simple operations. If necessary, the function shall ask for a
credit check to be done on the traveller or driver, it may also
check to see whether an advance payment has been made.
If the fee is known then initiate its recovery, otherwise initiate
the computation of the fee.
This Function shall calculate the fee corresponding to the

service required by the user, based on the characteristics of
this service, and on the contract established by the user.
The general tariffs for the service are held in a store of data,
and the Function may vary the fee depending on the current
situation.
This Function shall ask the traveller or driver for payment for
the selected service. Once this has been done, it shall
check with “Credit Control” for the transaction to be
validated. If the transaction is not valid for some reason the
Function shall register a violation.
This Function shall apportion the payments received
amongst the operators according to rules defined in the
store of Service Information Data.
This Function shall credit the accounts of the operators by

the amount that has already been calculated.
This Function shall be in charge of defining/building the

emergency intervention. As input, it shall get an emergency
as well defined as possible. Using pre-defined procedures
and information, it shall select the needed emergency
services, contact them, establish with them the action plans,
computes emergency road and prevent emergency drivers.
This Function shall provide facilities for the Emergency

Vehicle Driver whilst they are using an Emergency Vehicle.
This shall include the ability to receive and present to the
Driver details of the requested emergency route, to request
for individual priority at signalised junctions for the
Emergency Vehicle that is being driven, guidance along the
emergency route, and to give and to receive the emergency
intervention progress report. It shall also enable the
Emergency Vehicle Driver to deploy "virtual cones" around
the location of an accident.


ableThis
to provide
Functiondetails
shall of the current
provide trafficand previous
control modes
facilities that of
control on some or all parts of the urban road network
enable the traffic to be managed so that the most efficient to
other
use isfunctionality
made of the forinter-urban
output to the
roadRoad Network
network. TheOperator.
Function
Feedback
shall beofable
the to
results of commands
implement managementsent to the output
strategies in a
actuation
planned functionality
sequence accordingshall be monitored
to the timebyof the
dayFunction
and day so of
thatweek.
if necessary corrective
It shall be possibleaction can strategies
for these be taken iftocommands
include
are not of
control followed.
access to the inter-urban network (ramp metering),
plus commands to manage the use of lanes in the
carriageway (including the hard shoulder) and the maximum
or all parts of the inter-urban road network to other
functionality for output to the Road Network Operator.
actuation functionality shall be monitored so that if
necessary corrective action can be taken if commands are
not followed.


able to provide details of the current and previous modes of
control on some or all parts of the urban road network to
other functionality for output to the Road Network Operator.
actuation functionality shall be monitored by the Function so
that if necessary corrective action can be taken if commands
are not followed.
This Function shall provide facilities for the Emergency
Vehicle Driver whilst they are using an Emergency Vehicle.
This shall include the ability to receive and present to the
Driver details of the requested emergency route, to request
for individual priority at signalised junctions for the
Emergency Vehicle that is being driven, guidance along the
emergency route, and to give and to receive the emergency
intervention progress report. It shall also enable the
This Function shall monitor the progress that the Traveller is
making with the trip plan that they have requested to be
implemented. It shall continuously evaluate the data it
receives about travel conditions such as current and
predicted traffic flows, road works, weather, incidents and
PT services. If the Function determines that there will be
benefit to the Traveller from changing the trip plan it shall
request that this is done but continue monitoring the use of
the current trip plan until it is replaced. As the trip
progresses, the Function shall collect O-D and journey time
data for the road network segments that are used in the trip
and send them to the Inter-urban and Urban Traffic Data
Collection functionality. At the end of the trip, the Function
shall collect the data about the complete performance of the
trip and send it to the Performance Evaluation functionality.
This Function shall initiate the actual trip planning process

using parameters provided by the Traveller. It shall use
these parameters, together with data from the store of
General Trip Preferences Data to produce the requirements
for the proposed trip. The requirements shall comprise but
not be limited to the destination, and places to be visited
during the trip before the destination is reached (way points),
any bookings that are to be made, the schedule, the modes
the Traveller wants to use, and whatever else is deemed
interesting for trip satisfaction. When complete, the Function
shall send the requirements to the Trip Planning functionality
so that the trip plan can be prepared.
When the trip planning process has been completed, the

Function shall present the results to the Traveller. If
necessary the Function shall initiate the trip planning
process several times so that it can present a number of
alternative itineraries to the Traveller. These alternatives
may comprise but not be limited to possible perturbations of
the schedules, journey times and costs. The Function shall
provide the Traveller
This Function with the
shall provide anopportunity to refine
interface through the the
which
current parameters
Traveller may obtaintoinformation
produce alternative
about traveltrip conditions.
plans. It shall
work information
This in an iterative way
shall betoavailable
producefor more and more
all current accurate
modes of
trip plans.
travel in theSuccessive
area served tripbyplans shall be including
the System, stored internally
those not so
that they can
managed by thebe re-called
System, e.g.by the Traveller
heavy if later
rail, air versions
and maritime.
turn out
The to be must
Traveller unsatisfactory.
request theOnce outputa trip plan has been
of information and of
accepted
desired by the
may Traveller,
select criteria the Function
for its output.shall
Once sendthe the details
request
to the
has Function
been responsible
received, for producing
the Function will obtainthe thetravel itinerary
relevant
or to the Function
information from the responsible for making
store of Travel any bookings
Information Data. that
are included
Should in the trip plan.
the information not be in the store then the Function
can request it from the Produce Travel Information Function.
IfIfan
theinput is received
Function knowsto itssay that the
current Traveller
location then has rejected
it may filter
final trip plan,
the information thethe
from Function
store ofshall delete
Travel the trip plan
Information Data
details output,
before and shall butre-initiate
this shallthebe trip planning process.
configurable by the Traveller.
It shall be possible for the Traveller to configure the output
so that it can be provided against a map background, or in
different languages. The output shall be in a form that is
easy to understand and be suitable for those with
disabilities.
This Function shall manage the production of trip plans
based on data provided by the Traveller through other
Functions. These trip plans may be one way or for a return
trip (including weeks/months ahead), and take advantage of
late opening hours, special facilities etc. The Function shall
check the criteria provided by the Traveller and obtain
information for the specified modes to be used in the
requested trip, but taking account of the trip planning criteria
that have been set up by the Travel Information Operator.
This may require the Function to use data from the store of
Road Trip Planning Data and/or the store of PT Trip
Planning Data, plus also to collect information about Points
of Interest (POI) and Personal Services (PS) from External
Service Providers. The Function may also request
information about the services provided by other transport
modes where specified by the Traveller and obtain
information about tolls and other charges if they will need to
This
be paid Function
in order shall initiate thethe
to complete actual trip planning
proposed trip. Any process
using parameters
information that the provided
Function byreceives
the Traveller.
in this It shall
way willuse
be
these
passedparameters,
on to the Provide together with data
Traveller from the store
Information of
functionality.
General
Road trips TripforPreferences
cyclists and Data to produce
pedestrians shallthe berequirements
produced by
for
the the proposed
Function using trip.
theThe roadrequirements
network datashall and comprise
related but
not be limited to
perturbations, butthe destination,traffic
disregarding and places
incidenttoinformation.
be visited
during
The Functionthe tripshall
before alsothebedestination
able to reviseis reached (way points),
a part completed
any bookings
trip plan whenthat are to be
a Traveller made,inthe
departs anyschedule,
way fromthe itsmodes
the Traveller
contents, wantsconditions
or travel to use, and whatever
change. else is deemed
In these
interesting
circumstances for trip
thesatisfaction.
Function willWhen perform complete,
processing the similar
Function to
shall
that for senda newthe trip
requirements
plan, but start to the Tripthe
from Planning
current functionality
Traveller
so that the
location andtrip planof
mode can be prepared.
travel. The Function shall also be able
to exchange journey time data for each segment of the road
When
network the tripits
with planning process has
implementation beendevices
in other completed, and to theplan
Function
trips whenshall the present
only traffic therelated
resultsdatato the Traveller.
that is availableIf this
necessary
journey time the Function shall initiate the trip planning
data.
alternative
This Function itineraries to the an
shall provide Traveller.
interface These
throughalternatives
which the
may comprise
Traveller but notinformation
may obtain be limited to possible
about travelperturbations
conditions. of
the schedules,
This informationjourney shall be times and costs.
available for allThe
currentFunction
modes shall
of
provide
travel in the
the Traveller
area served withby thethe
opportunity to refine those
System, including the not
current
managed parameters
by the System, to produce alternative
e.g. heavy tripand
rail, air plans. It shall
maritime.
workTraveller
The in an iterative way to produce
must request the output more and more accurate
of information and of
trip plans.
desired may Successive
select criteria trip plans
for itsshall be stored
output. Once the internally
request so
that been
has they can be re-called
received, by the Traveller
the Function will obtainifthelater versions
relevant
turn out to be
information unsatisfactory.
from the store of Travel Once Information
a trip plan has been
Data.
accepted
Should thebyinformation
the Traveller, not the Function
be in the store shall
then send
the the details
Function
to the Function responsible for producing
can request it from the Produce Travel Information Function. the travel itinerary
or to the
If the Function
Function knowsresponsible
its currentfor location
making thenany bookings
it may filter that
are information
the included in the fromtrip theplan.
store of Travel Information Data
before output, but this shall be configurable by the Traveller.
If
It an
shallinput is received
be possible for to
thesay that thetoTraveller
Traveller configure has therejected
output
the final trip plan, the Function shall
so that it can be provided against a map background, delete the trip planor in
details and
different shall re-initiate
languages. the tripshall
The output planning
be in a process
form that is
disabilities.
be paid in order to complete the proposed trip. Any
information that the Function receives in this way will be
passed on to the Provide Traveller Information functionality.
Road trips for cyclists and pedestrians shall be produced by
the Function using the road network data and related
perturbations, but disregarding traffic incident information.
The Function shall also be able to revise a part completed
trip plan when a Traveller departs in any way from its
contents, or travel conditions change. In these
circumstances the Function will perform processing similar to
that for a new trip plan, but start from the current Traveller
This Function shall be responsible for the output of
location and mode of travel. The Function shall also be able
information to Drivers and/or Travellers about environmental
conditions. Details of what the information output should
network with its implementation in other devices and to plan
contain and to which group(s) of users the information
trips when the only traffic related data that is available this
should be output will be provided to this Function by the
journey time data.
Decide on Environmental Conditions Action Function.
This Function shall collect road based travel data for use in
the preparation of trip plans for Travellers, as well as for
Freight and Emergency Vehicles. The data shall be
collected as it arrives from functionality in the Manage Traffic
Functional Area and entered into the store of Road Trip
Planning Data.

network with its implementation in other devices and to plan
trips when the only traffic related data that is available this
journey time data.
Traveller may obtain information about travel conditions.
This information shall be available for all current modes of
travel in the area served by the System, including those not
managed by the System, e.g. heavy rail, air and maritime.
The Traveller must request the output of information and of
desired may select criteria for its output. Once the request
has been received, the Function will obtain the relevant
information from the store of Travel Information Data.
Should the information not be in the store then the Function
If the Function knows its current location then it may filter
the information from the store of Travel Information Data
disabilities.
This Function shall produce travel information using inputs it

receives from other Functional Areas. The Function shall
modify the inputs according to filters set by the Travel
Information Operator, so that for example certain types of
services, travel modes, Personal Services, or Points of
Interest are not included. Thus it shall be possible for the
Operator to restrict the information according to policy and
other factors. When ready, the Operator shall request that
the information is sent to a particular Output Travel
Information Function, which may be at a specific location.
The Operator may also request that the information is sent
to the store of Travel Information Data for use by the Provide
Traveller Information Interface Function when the Traveller
requests travel information.

information about road conditions, PT services, conditions of
other transport modes, Points of Interest (POI) and Personal
Services (PS) to Travellers. This information shall be
provided by the Travel Information Operator through the
Produce Traveller Information Function. The output shall be
in a form that is easy to understand and be suitable for those
with disabilities. It shall be continuously displayed until
replaced or cancelled by the Operator.
information about road conditions, PT services, conditions of
other transport modes, Points of Interest (POI) and Personal
Services (PS) to Travellers. This information shall be
provided by the Travel Information Operator through the
Produce Traveller Information Function. The output shall be
in a form that is easy to understand and be suitable for those
with disabilities. It shall be continuously displayed until
replaced or cancelled by the Operator.

This Function shall monitor the progress that the Traveller is
making with the trip plan that they have requested to be
implemented. It shall continuously evaluate the data it
receives about travel conditions such as current and
predicted traffic flows, road works, weather, incidents and
PT services. If the Function determines that there will be
benefit to the Traveller from changing the trip plan it shall
request that this is done but continue monitoring the use of
the current trip plan until it is replaced. As the trip
progresses, the Function shall collect O-D and journey time
data for the road network segments that are used in the trip
and send them to the Inter-urban and Urban Traffic Data
Collection functionality. At the end of the trip, the Function
shall collect the data about the complete performance of the
trip and send it to the Performance Evaluation functionality.
This Function shall initiate the actual trip planning process

using parameters provided by the Traveller. It shall use
these parameters, together with data from the store of
General Trip Preferences Data to produce the requirements
for the proposed trip. The requirements shall comprise but
not be limited to the destination, and places to be visited
during the trip before the destination is reached (way points),
any bookings that are to be made, the schedule, the modes
the Traveller wants to use, and whatever else is deemed
interesting for trip satisfaction. When complete, the Function
shall send the requirements to the Trip Planning functionality
so that the trip plan can be prepared.
When the trip planning process has been completed, the

Function shall present the results to the Traveller. If
necessary the Function shall initiate the trip planning
alternative itineraries to the Traveller. These alternatives
may comprise but not be limited to possible perturbations of
the schedules, journey times and costs. The Function shall
provide the Traveller
This Function with thetravel
shall produce opportunity to refine
information using theinputs it
current parameters
receives from other to produce Areas.
Functional alternativeThetrip plans. shall
Function It shall
work in the
modify an iterative way to produce
inputs according to filtersmore
set byandthemore
Travelaccurate
trip plans. Successive
Information Operator, so tripthat
plansfor shall be stored
example certain internally
types ofso
that they can
services, travelbemodes,
re-called by the Traveller
Personal Services,ifor later versions
Points of
turn out are
Interest to benotunsatisfactory.
included. Thus Once a trip
it shall be plan has been
possible for the
accepted to
Operator byrestrict
the Traveller, the Function
the information shall send
according the details
to policy and
to the factors.
other FunctionWhenresponsible
ready, for
theproducing the travel
Operator shall requestitinerary
that
or toinformation
the the Function responsible
is sent for making
to a particular OutputanyTravel
bookings that
are includedFunction,
Information in the tripwhich
plan. may be at a specific location.
The Operator may also request that the information is sent
If an
to theinput
storeisofreceived to say that the
Travel Information DataTraveller
for use by hastherejected
Provide
the final trip
Traveller plan, the Interface
Information Function Function
shall deletewhenthethetripTraveller
plan
details and
requests shallinformation.
travel re-initiate the trip planning process.
This Function shall provide the interface through which the
Traveller can request the implementation of a trip plan, be
given trip navigation instructions or manage changes to the
trip plan that is currently being implemented. The
instructions shall be provided to the Function by other
functionality and shall simply be output in whatever form
best suits the Traveller. If a proposal is received for revising
the trip plan that is being implemented, the Function shall
display details of the proposed changes to the Traveller and
send back the response that is received. It shall also be
possible for the Function to receive requests for changes to
the trip plan from the Traveller, in which case they shall be
sent to other functionality for implementation.
This Function shall provide the interface through which the

Road Network Operator can control the management of
incidents and the implementation of incident strategies. It
shall enable the Operator to confirm the implementation if
needed, to input and update incident data, and to provide
incident strategies. The Function shall also enable statistical
reports on the occurrence of incidents and the use strategies
to be provided to the Operator on request.
Planning Data.
This Function shall produce data about the Vehicle such as
its current speed, location, identity plus other information
such road and traffic states. It shall 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. The Function shall transmit this
data either at periodic intervals or event triggered depending
on how often the input (raw) data changes so that the
Vehicles become probes within the road network. If data
about such things as road friction, aquaplaning, Vehicle
breakdown and traffic incidents are not provided by the
Vehicle systems, the Function shall attempt to determine
them from the data that it has received. It shall also
compose and send acknowledgement messages resulting
from instructions received by Vehicles and displayed to
Drivers. These shall be sent by the Function to the Law
Enforcement functionality in case there is a violation is
detected as a result of instructions sent to Drivers.
This Function shall provide data and routes to functionality

serving Fleet Operators and Drivers at their request and
contribute information about freight and hazardous goods
that may be relevant to general trip planning. The data that
can be requested by Fleet Operators and Drivers shall
comprise specific items such as pollution, traffic and weather
conditions, for which the Function shall obtain the current
values from the store of Road Trip Planning Data. When
data is received from the Manage Freight and Fleet
Operations functionality, it shall be stored in the store of
Road Trip Planning Data by the Function. On request from
functionality connected to the Freight Operator and
Hazardous Goods Vehicle Driver the Functions shall prepare
routes using the parameters provided in the request and
data from the store of Road Trip Planning Data.
This Function shall collect Public Transport travel data for

use in the preparation of trip plans for Travellers. The data
shall be collected as it arrives from functionality in the
Manage Public Transport Operations Functional Area and
entered into the store of PT Trip Planning Data.
Planning Data.

Road trips for cyclists
This Function shall manageand pedestrians
the store ofshallUrbanbe Traffic
produced by
Data.
the
It Function
shall receive using
datathe roadtraffic
about network data and
conditions (e.g.related
traffic flows
perturbations,
and journey times) but disregarding
in the urban traffic incident and
road network information.
car park
The Function
data from other shall also beinable
Functions theto revise aTraffic
Manage part completed
Functional
trip plan
Area andwhen
from aotherTraveller
parts departs in any way
of the System. Where fromnecessary,
its
contents,
the Function or travel conditions
shall use the urban change. In thesestatic data to
road network
circumstances
enable the trafficthedata
Function will perform
to be collated, fusedprocessing
and stored similar
in a to
that for a way
coherent new that
trip plan,
makes butit start
easy from the current
to retrieve Traveller
it for particular
location
road and mode
segments, of travel.
or larger parts The Function
of the urbanshall
roadalso be able
network.
to exchange
Once journey
the received datatime data
has for processed,
been each segment of the
it shall be road
networkinto
loaded withthe
itsstore
implementation
and distributed in other devices
to other and to plan
functionality in
tripsManage
the when the only Functional
Traffic traffic related dataPart
Area. thatofis this
available
other this
journey time shall
functionality data.be responsible for the output of the
processed data to other parts of the System and to entities
outside the System.
This Function shall output the data that it receives about
current traffic conditions in the inter-urban road network to
other parts of the System or to entities that are outside of the
System. It shall immediately output the data which shall be
periodically sent by the functionality that manages the store
of Inter-urban Traffic Data, plus the functionality that
manages lane use and maximum speeds within the inter-
urban road network. When the Function receives a request
from the Broadcaster it shall output the latest set of data that
it has about inter-urban traffic conditions.

disabilities.
This Function shall enable the Traveller to give final approval

to the trip plan that has just been prepared. It shall provide
the Traveller with the trip itinerary encompassing travel
modes, schedules, bookings, payments made and further
information coming out of the Trip Planning functionality. If
so desired, the Function may include any maps for road trips
or route descriptions, as well as safety advice concerning all
conditions en route that have been produced as part of the
trip planning process. The Function shall enable the
Traveller to give final approval to the trip plan after which it
will be sent to the Manage Store of Trip Plan Data for
implementation when so requested by the Traveller. It shall
also be possible for the Traveller to cancel the trip at this
stage, in which case the Function shall send a "cancel
bookings" command to the Make Bookings and Payments
for Trip Function and initiate the trip planning process again
from the beginning.
disabilities.

disabilities.
This Function shall enable the Traveller to specify a set of

factual data to be used as General Trip Preferences (GTP)
for use each time they want to plan a trip. This shall be done
once as a preparation to full personalisation. Once a
planned trip has been completed, the Function shall ask the
Traveller for any comments on the performance of the trip
and any changes that are needed to the GTP data. The
Function shall also enable the Traveller to have an output of
their current GTP data and to amend that data, even if this is
not the result of the performance of a planned trip.
This Function shall provide an interface that enables the
Travel Information Operator to have access to the contents
of the stores of Road Trip Planning Data and PT Trip
Planning Data. It shall be possible for the Operator to review
and update the data in the stores including the provision of
static data for the urban and inter-urban road networks car
parks and service areas, where this is not available from the
Manage Traffic Functional Area. Apart from general data
management, the interface shall provide reports to the
Travel Information Operator on the current contents of the
stores, including in particular details of any active events or
incidents that are affecting Travellers trip plans.
This Function shall provide an interface that enables the

Travel Information Operator to have access to the contents
of the General Trip Preferences (GTP) Data Store and to
output reports on the performance of planned trips. The
reports shall be produced by this Function as a result of data
it receives from other functionality.
This Function shall provide a management interface or the
Travel Information Operator. It shall enable the Operator to
collect data from the store of Private Trip Plan Data about
the content of the trip plans that are being produced. This
data shall be formatted and presented to the Operator as a
management report, with the identities and other personal
details about the Travellers removed.
This Function shall provide management of the lanes on

roads in the urban network. The Function shall enable the
management of the lanes so that the most efficient use can
be made of the available road space. It shall enable the use
of lanes to be changed in a way that is safe for vehicle
operation and that causes the minimum disruption to all
forms of urban road traffic. Implementation of commands to
alter the use of lanes shall be sent to the urban output
actuation Function.
This Function shall detect violations of urban traffic control
commands and report them to functionality in the Provide
Support for Law Enforcement Area. Reporting of a violation
shall only occur when it is detected that a vehicle does not
follow the current urban traffic commands. Details of these
commands shall be provided by the urban traffic
management Function.
This Function shall provide management of the lanes on

roads in the inter-urban network. The Function shall enable
the management of the lanes so that the most efficient use
can be made of the available road space. It shall enable the
use of lanes to be changed in a way that is safe for vehicle
operation and that causes the minimum disruption to all
forms of inter-urban road traffic. The Function shall support
lane management comments that can ban the use of one or
several lanes in some or the entire road network, for all or
specific types of Vehicles, provide keep-in-lane advice to
stabilise traffic flow for all or specific types of vehicles and
where available, make the auxiliary lane (sometimes called
the hard shoulder) available for use. Implementation of
commands to alter the use of lanes shall be sent to the
functionality that is responsible for the output of messages to
Drivers, both at the roadside and in the Vehicle.
This Function shall detect violations of inter-urban traffic

control commands and report them to functionality in the
Provide Support for Law Enforcement Area. Reporting of a
violation shall only occur when it is detected that a Vehicle
does not follow the current inter-urban traffic commands.
Details of these commands shall be provided by the inter-
urban traffic management functionality.
This Function shall collect data from the road network in the
form of guidance signals. These shall be received from the
road pavement, together with an indication of their integrity,
and passed on to the relevant in-vehicle systems.
This Function shall provide an interface between the

systems inside the Vehicle and the functionality contained
within the System. A variety of data is extracted by the
Function from the Vehicle systems through a "read only"
interface, so that the integrity and safety of the systems
themselves and the Vehicle cannot be compromised. The
Function sends this data to functionality within its own
Functional Area.
Cerinte functionale
(a) continuously monitor for the arrival of the data flows containing static data for the inter-
urban and/or urban road network
(b)when either of the data flows in (a) is received, process the data into a coherent set that
represents the road network managed by the system, integrating the new data with any that
was received previously
(c) when (b) is complete, send include the data in the network data for simulation data flow
and send it to the store of Manage Traffic Simulation Data.
(a) when the road network data for simulation data flow is received load the data into the store
of Road Traffic Simulation Data using the data flow load simulation data
(b) use the data received in (a) in the road network data for collection data flow and send it to
the Process Road Traffic Data function
(c) when the processed road traffic data flow is received, load the data it contains into the
store of Road Traffic Simulation Data using the data flow load simulation data
(d) when either the inter-urban or urban strategies in use are received, again load their
contents into the store of Road Traffic Simulation Data using the data flow road simulation
data
(e) when the request road data for simulation data flow is received collect all the relevant data
from the store of Road Traffic Simulation Data using the data flow read simulation data
(f) put the data collected in (e) into the road data for simulation data flow and send it to the
Provide Traffic Simulation Engine function
(g) when as a result of (f) the simulation results data flow is received, load the data into the
store of Road Traffic Simulation Data using the data flow road simulation data
(h) if the traffic simulation results data flow is received from other systems, load the data into
the store of Road Traffic Simulation Data using the data flow load simulation data
(i) if the send traffic simulation results for output data flow is received, collect the relevant
simulation results plus the data about the traffic model itself from the store of Road Traffic
Simulation Data using the data flow for read simulation data and send it to the Process Traffic
Simulation Results function in the traffic simulation results for processing data flow and also to
the other systems using the traffic simulation results data flow
(j) if the request road network data flow is received, collect the requested data from the store
of Road Traffic Simulation Data using the data flow read simulation data and send it to the
Provide Traffic Simulation Operator Interface function in the data flow containing requested
road network data
(k) if the updated road network data flow is received, amend the data in the store of Road
Traffic Simulation Data using the data flow load simulation data
(l) if the request traffic simulations results data flow is received, collect the requested data
from the store of Road Traffic Simulation Data using the data flow read simulation data and
send it to the Provide Traffic Simulation Operator Interface function in the data flow containing
requested traffic simulation results.
(a) continuously monitor for receipt of the operator urban traffic management request, planned
urban traffic management request, urban environmental inputs, urban demand management
strategy and urban incident strategy request data flows
(b) when any of the data flows in (a) is received, implement the traffic management
commands that they contain using the contents of the data flow containing urban static data to
determine which are the appropriate section(s) if the urban road network to which the
commands apply
(c) the commands in (b) shall be implemented using some or all of the urban bridge inputs,
urban tunnel inputs, urban lane management, urban speed setting, urban traffic management
s&g request, urban traffic management msg requests and urban recommended routes data
flows, plus data sent to the Traffic Simulation functionality in the urban strategies in use data
flow
(d) the commands being implemented in (b) shall be filtered for applicability and sent to any
other adjacent urban traffic management systems in the urban traffic management strategies
data flow and to any relevant inter-urban traffic management systems in the urban to inter-
urban traffic commands data flow
(e) if the urban zoning strategy data flow is received, whichever is necessary of the data flows
in (c) shall be sent plus the urban zone access vehicle list data flow
(f) it shall be possible for the data flows containing current urban traffic conditions, urban traffic
flow management data, predicted urban network data, bridge urban inputs and tunnel urban
inputs to be continuously monitored and for their contents to be used to revise the detail of the
commands being implemented in (b) thus providing adaptive traffic control
(g) if the operator urban traffic management request was received in (a) and had led to the
implementation of (b) and (c) then the operator urban traffic management response data flow
shall be sent to the Provide Operator Interface function
(h) as a result of (c) the receipt of the urban traffic management s&g response, urban traffic
management l&s response and urban traffic management c&i response data flows shall be
monitored
(i) when any of the data flows in (h) is received their contents shall be checked to see if the
commands in (c) are being followed
(j) if the result of (i) is that the commands are not being followed, this shall be communicated
to the Provide Operator Interface function in the operator urban management response data
flow and to the Maintenance Management functionality in the urban response fault data flow
(k) if the requirement is included in the contents of the data flows in (b) the contents of the
data flows in (i) shall be used to revise the commands being sent in (c)
(l) if either the inter-urban to urban traffic commands or urban traffic management strategy
data flows is received, their contents shall be analysed if necessary new commands
implemented as in (c) with the addition that requests may be sent to any relevant multi-modal
management systems in the urban crossing inhibit data flow
(m) if any of the urban emergency route request, green wave request, vehicle priority request
and request demand vehicle priority data flows is received, its contents shall be implemented
as in (b) and (c) above and shall take priority over any of the other inputs received in (a), (l)
and (m)
(n) of the data flows in (m) the contents of the urban emergency route request shall take
priority over all the others, with the contents of the vehicle priority request data flow being the
next highest in priority, followed by the contents of the demand vehicle priority data flow
(o) if the inter-urban virtual coned area request data flow is received, implement the necessary
lane closures and speed restrictions as in (b) and (c) above in order to prevent vehicles from
entering the area around an accident
(p) the commands in the operator urban traffic management request data flow received in (a)
shall take precedence over all the inputs in (a) and (l) but not the inputs in (m) and (o)
(q) the commands in the planned urban traffic management request data flow received in (a)
shall take the lowest priority after all the other inputs in (a), (l), (m) and (o)
(r) implementation of all the outputs in (c) shall be checked to ensure that the comments being
implemented are consistent and coherent and do not contradict each other.
(a) continuously monitor for receipt of the operator inter-urban management request, planned
inter-urban traffic management request, inter-urban environmental inputs, inter-urban demand
management strategy and inter-urban incident strategy request data flows
commands that they contain using the contents of the data flow containing inter-urban static
data to determine which are the appropriate section(s) if the inter-urban road network to which
the commands apply
(c) the commands in (b) shall be implemented using some or all of the inter-urban bridge
inputs, inter-urban tunnel inputs, inter-urban lane requests, inter-urban speed setting, inter-
urban traffic management l&s request, inter-urban traffic management c&i requests and inter-
urban recommended routes data flows, plus through data sent to the Traffic Simulation
functionality in the inter-urban strategies in use data flow
other adjacent inter-urban traffic management systems in the inter-urban traffic management
strategy data flow and to any relevant urban traffic management systems in the inter-urban to
(e) if the inter-urban zoning strategy data flow is received, whichever is necessary of the data
flows in (c) shall be sent plus the inter-urban zone access vehicle list data flow
(f) it shall be possible for the contents of the data flows containing current inter-urban traffic
conditions, inter-urban traffic flow management data, predicted inter-urban network data,
bridge inter-urban inputs and tunnel inter-urban inputs to be used to revise the detail of the
commands being implemented in (b)
(g) if the operator inter-urban management request was received in (a) and had led to the
implementation of (b) and (c) then the operator inter-urban management response data flow
(h) as a result of (c) the receipt of the inter-urban traffic management l&s response and inter-
urban traffic management c&i response data flows shall be monitored
(i) when either of the data flows in (h) is received their contents shall be checked to see if the
(j) if the result of (i) is that the commands are not being followed (or either of the data flows is
not received within a given time frame), this shall be communicated to the Provide Operator
Interface function in the operator inter-urban management response data flow and to the
Maintenance Management functionality in the inter-urban response fault data flow
(l) if either the urban to inter-urban traffic commands or inter-urban traffic management
strategy data flows is received, their contents shall be analysed if necessary new commands
implemented as in (c) with the addition that requests may be sent to any relevant multi-modal
management systems in the inter-urban crossing inhibit data flow
(m) if the inter-urban emergency route request data flow is received, its contents shall be
implemented as in (b) and (c) above and shall take priority over any of the other inputs
received in (a) and (l)
(n) if the inter-urban virtual coned area request data flow is received, implement the necessary
lane closures and speed restrictions as in (b) and (c) above in order to prevent vehicles from
entering the area around an accident
(o) the commands in the operator inter-urban traffic management request data flow received in
(a) shall take precedence over all the inputs in (a) and (l) but not those in (m) and (n)
(p) the commands in the planned inter-urban traffic management request data flow received in
(a) shall take the lowest priority after all the other inputs in (a), (l), (m) and (n)
(q) implementation of all the outputs in (c) shall be checked to ensure that the commands
being implemented are consistent and coherent and do not contradict each other.
(a) continuously monitor for receipt of any of the input data flows
(b) when any of the data flows containing data about traffic using the urban road network is
received, process the data, applying data fusion where the data relates to the same part of the
road network
(c) use the data received in the urban static data for traffic conditions data flow to determine
the location and characteristics of the part of the urban road network to which the received
data applies
(d) convert the contents of data flow containing urban infrastructure usage data into actual
traffic flows and apply it to the correct part(s) of the urban road network
(e) load the results of (b) to (d) into the store of Urban Traffic Data, to provide the current
traffic flow data and fusing it with data already in the store to provide a coherent set of historic
traffic data for the urban network
(f) also use the results of (b) to (d) to provide traffic data for other urban traffic management
systems
(g) analyse the results of (b) to (d) to determine where traffic queues are present and from use
successive collections of data to determine the speed of propagation of the tail end of the
queue
(h) use the data received in the urban static data for traffic conditions data flow to determine
the locations of the queues
(i) send the results of (g) and (h) to the output warnings to the driver in the vehicle functionality
(j) analyse the results of (b) to (d) to determine the current journey time for each segment of
the urban road network store it in the store of Urban Traffic Data, fusing it with similar data
already in the store to provide a historical record of journey times
(k) use the results of (b) to (d) to provide the output data flows containing current traffic data
that shall be sent directly to other functionality and to the function for transmission to other
entities and functionality in other functional areas
(l) periodically read the journey times from the store of Urban Traffic Data and use them to
update the default urban road segment journey times using the default urban journey time
update data flow
(m) when the urban data updates data flow is received in (a) from other urban traffic systems,
store it in its own part of the store of Urban Traffic Data to provide a coherent historical record
of urban traffic data in other relevant geographic areas
(n) when the inter-urban to urban traffic data transfer data flow is received in (a), store it in its
own part of the store of Urban Traffic Data to provide a coherent historical record of inter-
urban traffic data in relevant areas
(o) when the data flow containing urban traffic predicted data is received in (a), store it in its
own part of the store of Urban Traffic Data and delete any data that is no longer predicted, i.e.
the time for which it is predicted in now current or in the past
(p) when either of the data flows containing car park data is received in (a) store their contents
in the car park part of the store of Urban Traffic Data to provide a coherent historical record of
car park use
(q) when the data flow containing journey times from a cellular communications network
provider is received, filter the data to remove travel times that are not between locations in the
urban road network, e.g. for pedestrian routes and the inter-urban road network and check for
consistency, i.e. does it fit with other data for road vehicles, or is it perhaps a cyclist
(r) add the data that does pass the tests in (q) to the store of journey times in the store of
Urban Traffic Data.
(b) when any of the data flows containing data about traffic using the inter-urban road network
is received, process the data, applying data fusion where the data relates to the same part of
the road network
(c) use the data received in the inter-urban static data for traffic conditions data flow to
determine the location and characteristics of the part of the inter-urban road network to which
the received data applies
(d) convert the contents of data flow containing inter-urban infrastructure usage data into
actual traffic flows and apply it to the correct part(s) of the inter-urban road network
(e) load the results of (b) to (d) into the store of Inter-urban Traffic Data, to provide the current
traffic flow data and fusing it with data already in the store to provide a coherent set of historic
traffic data for the inter-urban network
(f) also use the results of (b) to (d) to provide traffic data for other inter-urban traffic
management systems
(g) analyse the results of (b) to (d) to determine where traffic queues are present and from use
successive collections of data to determine the speed of propagation of the tail end of the
queue
(h) use the data received in the inter-urban static data for traffic conditions data flow to
determine the locations of the queues
(j) send the results of (g) and (h) to the output warnings to the driver in the vehicle functionality
(j) analyse the results of (b) to (d) to determine the current journey time for each segment of
the inter-urban road network and store it in the store of Inter-urban Traffic Data, fusing it with
similar data already in the store to provide a coherent historical record of journey times
(k) use the results of (b) to (d) and (j) to provide the output data flows containing current traffic
data that shall be sent directly to other functionality and to the function for transmission to
other entities and functionality in other functional areas
(l) periodically read the journey times from the store of Inter-urban Traffic Data and use them
to update the default inter-urban road segment journey times using the default inter-urban
journey time update data flow
(m) when the inter-urban data updates data flow is received in (a) from other inter-urban traffic
systems, store it in its own part of the store of Inter-urban Traffic Data to provide a coherent
historical record of inter-urban traffic data in other relevant geographic areas
(n) when the urban to inter-urban traffic data transfer data flow is received in (a), store it in its
own part of the store of Inter-urban Traffic Data to provide a coherent historical record of
urban traffic data in relevant urban areas
(o) when the data flow containing inter-urban traffic predicted data is received in (a), store it in
its own part of the store of Inter-urban Traffic Data and delete any data that is no longer
predicted, i.e. the time for which it is predicted in now current or in the past
(p) when the data flow containing service area occupancy data is received in (a) store its
contents in the service area part of the store of Inter-urban Traffic Data to provide a coherent
historical record of service area use
(q) when the data flow containing journey times from a cellular communications network
provider is received, filter the data to remove travel times that are not between locations in the
inter-urban road network, e.g. for pedestrian routes and the urban road network and check for
consistency, i.e. does it fit with other data for road vehicles, or is it perhaps a cyclist
(r) add the data that does pass the tests in (q) to the store of journey times in the store of
Inter-urban Traffic Data.
(a) continuously monitor for the arrival of the operator simulation commands data flow
(b) when the data flow in (a) arrives, start to carryout the instructions that it contains
(c) send the request road data for simulation data flow to the Manage Traffic Simulation Data
Store function
(d) when as a result of (c) the road data for simulation data flow is received, produce a
simulation of the traffic conditions that will exist in the road network according to the static and
collected road data plus the traffic management strategies currently being used, and the traffic
management and/or road network scenario(s) included in the operator simulation commands
(e) when (d) is complete, send the simulation results back to the Manage Traffic Simulation
Data Store function and send the simulation responses data flow to the Provide Operator
Interface function.
(a) when the road network data for simulation data flow is received load the data into the store
of Road Traffic Simulation Data using the data flow load simulation data
(b) use the data received in (a) in the road network data for collection data flow and send it to
the Process Road Traffic Data function
(c) when the processed road traffic data flow is received, load the data it contains into the
store of Road Traffic Simulation Data using the data flow load simulation data
(d) when either the inter-urban or urban strategies in use are received, again load their
contents into the store of Road Traffic Simulation Data using the data flow road simulation
data
(e) when the request road data for simulation data flow is received collect all the relevant data
from the store of Road Traffic Simulation Data using the data flow read simulation data
(f) put the data collected in (e) into the road data for simulation data flow and send it to the
Provide Traffic Simulation Engine function
(g) when as a result of (f) the simulation results data flow is received, load the data into the
store of Road Traffic Simulation Data using the data flow road simulation data
(h) if the traffic simulation results data flow is received from other systems, load the data into
the store of Road Traffic Simulation Data using the data flow load simulation data
(i) if the send traffic simulation results for output data flow is received, collect the relevant
simulation results plus the data about the traffic model itself from the store of Road Traffic
Simulation Data using the data flow for read simulation data and send it to the Process Traffic
Simulation Results function in the traffic simulation results for processing data flow and also to
the other systems using the traffic simulation results data flow
(j) if the request road network data flow is received, collect the requested data from the store
of Road Traffic Simulation Data using the data flow read simulation data and send it to the
Provide Traffic Simulation Operator Interface function in the data flow containing requested
road network data
(k) if the updated road network data flow is received, amend the data in the store of Road
Traffic Simulation Data using the data flow load simulation data
(l) if the request traffic simulations results data flow is received, collect the requested data
from the store of Road Traffic Simulation Data using the data flow read simulation data and
send it to the Provide Traffic Simulation Operator Interface function in the data flow containing
requested traffic simulation results.
(a) when any of the input data flows are received from the transport planner, process them
and send the relevant data flow to either the Manage Traffic Simulation Data Store function or
the Provide Traffic Simulation Engine function
(b) when as a result of sending one of the data flows in (a) the response is received from the
appropriate destination function, output the received data to the transport planner using the
appropriate output data flow.
(a) when the run demand strategy simulation data flow is received, send the request for data
and strategies for simulation data flow tot he Manage Demand Management Data Store
function
(b) when the data and strategy for simulation data flows have been received, run the
simulation to show what is expected to happen when the strategy is implemented
(c) when (b) is completed, send the results in the demand strategy simulation results data flow
to the Provide Transport Planner Interface function
(d) if the new demand strategy for simulation data flow is received, send the request for data
for simulation data flow tot he Manage Demand Management Data Store function
(e) repeat (b) and (c).
(a) when the first trigger input data flow is received, the current mode use data shall be
requested from the Manage Demand Management Data Store function, using the second
trigger output data flow
(b) when the response is received (via a second trigger input data flow) a new demand
management strategy shall be produced according to the previously defined "rules"
(c) when (b) is complete, the new demand management strategy shall be sent to the Manage
Demand Management Data Store function(
d) if included in the data flow received in (a), the strategy produced in (c) shall also be sent to
the Demand Management Strategy Implementation function
(e) if the second trigger input data flow is received, the internal data store shall be updated
with the data that it contains so that it can be used in future strategy development
(f) the data provided in (d) may include "rules" for a re-distribution of the demand from
travellers away from the current highly loaded mode(s).
(a) when the run demand strategy simulation data flow is received, send the request for data
and strategies for simulation data flow tot he Manage Demand Management Data Store
function
(b) when the data and strategy for simulation data flows have been received, run the
simulation to show what is expected to happen when the strategy is implemented
(c) when (b) is completed, send the results in the demand strategy simulation results data flow
to the Provide Transport Planner Interface function
(d) if the new demand strategy for simulation data flow is received, send the request for data
for simulation data flow tot he Manage Demand Management Data Store function
(e) repeat (b) and (c).
(a) when the first trigger input data flow is received, the current mode use data shall be
requested from the Manage Demand Management Data Store function, using the second
trigger output data flow
(b) when the response is received (via a second trigger input data flow) a new demand
management strategy shall be produced according to the previously defined "rules"
(c) when (b) is complete, the new demand management strategy shall be sent to the Manage
Demand Management Data Store function(
d) if included in the data flow received in (a), the strategy produced in (c) shall also be sent to
the Demand Management Strategy Implementation function
(e) if the second trigger input data flow is received, the internal data store shall be updated
with the data that it contains so that it can be used in future strategy development
(f) the data provided in (d) may include "rules" for a re-distribution of the demand from
travellers away from the current highly loaded mode(s).
(a) when the second trigger input data flow is received, get the image recorded by the other
Functions
(b) alternatively, if the first trigger input data flow is received, extract the relevant elements
from the fraud notification
(c) analyse the image received in (a) to determine the type of fraud involved and the vehicle ID
(d) as a result of (c), send the vehicle ID back to the requesting Function using the first trigger
output data flow
(e) also send the same data plus the fraud type to the Determine Violator Function using the
first trigger input data flow and the other output data flow.
(a) when the trigger input data flow is received extract the identity of the violating vehicle
(b) do not change the type of fraud in the other input data flow that will also be received in (a)
(c) search in the store of User's Registration Data for the identity of the owner or recorded
driver of the vehicle using the second other output data flow
(d) receive the data resulting from (c) in the second other input data flow
(e) send the result of (d) to the Sort Fraud Notifications Function, using the first trigger output
data flow
(f) include with the data flow in (e) the first other output data flow containing the type of fraud,
which must be a copy of the first other input data flow received in (b).
(a) continuously monitor for the receipt of any fraud (violation) notification sent by the other
functionality
(b) when any of the data flows in (a) is received, process it and extract the violator ID
(b) if the violator ID is not in the notification received in (b), extract any elements useful for this
identification, and send them to the Identify Violator Function, using the first other output data
flow
(c) await receipt of the data resulting from (b) which will arrive in the fifth trigger input data flow
(d) note that the data flow in (c) will be accompanied by the fourth other input data flow
(e) extract from the store of Violations Data the seriousness of the fraud, receiving the data in
the third other input data flow
(f) also search in the store of Violations Data to see if the violator has already committed other
similar offences before, receiving the data in the second other input data flow
(g) dispatch the notifications according to the format of the fraud in the first trigger output data
flow to the Establish Prosecution File Function
(h) send all the data about the fraud (violation) to the Fraud Function, using the second trigger
output data flow
(i) where the driver and/or vehicle ID is known, send the data to the Manage Traffic Area,
using the appropriate of the first and second trigger output data flows, depending on whether
the fraud (violation) was committed in the inter-urban or urban road network.
Diagrams
This Function shall send the file containing all the elements necessary for the prosecution of
the violator to the right Law Enforcement Agency. As part of the process of preparing the file,
the Function shall check that the violation is not the result of an instruction that has been given
to and acknowledged by a Driver. The Function shall also send the resulting file, plus all the
elements received, to the functionality that stores fraud notifications. For violations detected
directly by other functionality in this Area, and concerning freight vehicles, the Function shall
also send a fraud notification, including all the elements to functionality in the Manage Freight
and Fleet Operations Area.
(a) when the second trigger input data flow is received, get the image recorded by the other
Functions
(b) alternatively, if the first trigger input data flow is received, extract the relevant elements
from the fraud notification
(c) analyse the image received in (a) to determine the type of fraud involved and the vehicle ID
(d) as a result of (c), send the vehicle ID back to the requesting Function using the first trigger
output data flow
(e) also send the same data plus the fraud type to the Determine Violator Function using the
first trigger input data flow and the other output data flow.
a) when the trigger input data flow is received extract the identity of the violating vehicle
(b) do not change the type of fraud in the other input data flow that will also be received in (a)
(c) search in the store of User's Registration Data for the identity of the owner or recorded
driver of the vehicle using the second other output data flow
(d) receive the data resulting from (c) in the second other input data flow
(e) send the result of (d) to the Sort Fraud Notifications Function, using the first trigger output
data flow
(f) include with the data flow in (e) the first other output data flow containing the type of fraud,
which must be a copy of the first other input data flow received in (b).
(a) continuously monitor for the receipt of any fraud (violation) notification sent by the other
functionality
(b) when any of the data flows in (a) is received, process it and extract the violator ID
(b) if the violator ID is not in the notification received in (b), extract any elements useful for this
identification, and send them to the Identify Violator Function, using the first other output data
flow
(c) await receipt of the data resulting from (b) which will arrive in the fifth trigger input data flow
(d) note that the data flow in (c) will be accompanied by the fourth other input data flow
(e) extract from the store of Violations Data the seriousness of the fraud, receiving the data in
the third other input data flow
(f) also search in the store of Violations Data to see if the violator has already committed other
similar offences before, receiving the data in the second other input data flow
(g) dispatch the notifications according to the format of the fraud in the first trigger output data
flow to the Establish Prosecution File Function
(h) send all the data about the fraud (violation) to the Fraud Function, using the second trigger
output data flow
(i) where the driver and/or vehicle ID is known, send the data to the Manage Traffic Area,
using the appropriate of the first and second trigger output data flows, depending on whether
the fraud (violation) was committed in the inter-urban or urban road network.
(a) receive all the elements related to the fraud (violation) in the first trigger input data flow
(b) select the Law Enforcement Agency(ies) concerned by the fraud (violation) from the data
received in (a)
(c) if necessary extract information on previous offences from the store of Violations Data,
receiving the data in the first other input data flow
(d) send a data flow to check that the detected violation is not the result of instructions sent to
Drivers, and abandon the creation of the prosecution file at this point
(e)fill the prosecution file using to the format required by the Law Enforcement Agency
identified in (b)
(f) send the prosecution file to the Law Enforcement Agency using the third trigger output data
flow
(g) send the prosecution file and all the associated elements to the Fraud Function, using the
second trigger output data flow
(h) if the fraud concerns freight vehicles and has been detected by the functionality in this
Area, send the elements to the Manage Freight and Fleet Operations Area, using the first
trigger output data flow.
(a) if the second trigger input data flow is received, carry out the measure of the parameter to
be checked based on its contents
(b) if the third or fourth trigger input data flows are received, collect the measure from the
Manage Traffic Area
(c) ask the Driver for the delivery of the record to be controlled using the third trigger output
data flow
(d) receive the record to be controlled from the Driver using the first other input data flow
(e) ask the vehicle for its identification using the first trigger output data flow and wait for a
response
(f) receive the identification from the vehicle, if available using the second other input data flow
(g) extract the useful information from the measure so that it can be analysed
(h) send the measure to the Check Compliance Function using the second trigger output data
flow.
(a) if the second trigger input data flow is received, carry out the measure of the parameter to
be checked based on its contents
(b) if the third or fourth trigger input data flows are received, collect the measure from the
Manage Traffic Area
(c) ask the Driver for the delivery of the record to be controlled using the third trigger output
data flow
(d) receive the record to be controlled from the Driver using the first other input data flow
(e) ask the vehicle for its identification using the first trigger output data flow and wait for a
response
(f) receive the identification from the vehicle, if available using the second other input data flow
(g) extract the useful information from the measure so that it can be analysed
(h) send the measure to the Check Compliance Function using the second trigger output data
flow.
(a) read user's request : type of service on which information is required,
(b) receive corresponding elements from the "Provide Traveller Journey Assistance" Function.
(c) display corresponding information to the user
(d) read user's choice
(e) write contract
(f) display the contract to the user, record it in the store of "EP contract" Data.
(a) process the different contracts (sent on a regular basis) to extract different kinds of
information : e.g. number per service, chosen modes of payment, locations of contract set-
up ...
(b) send the resulting statistics to the corresponding operators and/or service providers
(a) read the information about the transaction, and extract the operators ID and service
concerned
(b) extract from the store of "service information" Data the rules to be followed concerning the
allocation of revenue for this service
(c) compute the corresponding revenue for each operator
(d) send the result to the Credit Operator's Account function
(a) read the different elements included in the message coming from "Distribute Fee
Revenues".
(b) sends the credit order to the financial clearinghouse, including the fee, the originating
account, and the account to be credited,
(c) load the transaction into the store of "transactions" Data.
(a) get the request from the operator or service provider, including its ID, services of interest,
period, ...
(b) extract the corresponding transactions from the store of "transactions" Data. These
transactions are those concerning directly the Operator or Service Provider, or those that
resulted in some revenue for them,
(c) process them to obtain the desired information
(d) present the results to the Operator or Service Provider
(a) receive updates of tariff grids from the different operators, service providers, Public
Transport operator, or demand management Function
(b) reformat them,
(c) fill the store of "tariffs" Data with the new tariff grids
(a) read user's request : type of service on which information is required,
(b) receive corresponding elements from the "Provide Traveller Journey Assistance" Function.
(c) display corresponding information to the user
(d) read user's choice
(e) write contract
(f) display the contract to the user, record it in the store of "EP contract" Data.
(a) process the different contracts (sent on a regular basis) to extract different kinds of
information : e.g. number per service, chosen modes of payment, locations of contract set-
up ...
(b) send the resulting statistics to the corresponding operators and/or service providers
(a) when the trigger input data flow is received, check to see if a review command or data has
been sent
(b) if a review comment is received in (a), collect all of the current data from the store of
Service Information Data using the other input data flow
(c) send the data obtained in (b) to the Operator using the second other output data flow
(d) if data was received in (a), send it to the store of Service Information Data using the first
other output data flow, to add to, or amend the data the store currently contains
(e) if a "delete" command was received in (a) then use the first other output data flow to send
an appropriate delete command to the store of Service Information Data.
(a) read traveller's ID
(b) extract from the store of Contract Data the contracts that have already been established for
that person
(c) present the traveller with this list of contracts
(d) read the traveller's selection and the loading parameters
(e) check the balance of the "source" account at the financial clearing-house
(f) if source account does not have sufficient funds, display an error message to the traveller,
(g) else, record loading transaction in the store of "transaction" Data, load the Electronic
Payment account, and send the notification message to the financial clearing-house
(a) read the transaction message, and extract the user's ID, account ID, corresponding fee
(b) get the balance of the EP account
(c) debit the balance by the amount of the transaction, and record the operation in the stores
of "transactions" Data and "user's account" Data
(d) if the "user's account" is now overdrawn, send an overdraft message to the traveller and to
"Credit Control".
(a) receive user ID and service request

(b) extract corresponding contract from the store of "contract" Data
(c) check the access rights by asking the "Access Control" Function,
(d) sends the contract information back to the "inform and guide user" Function
(e) in case of reception of a "free ride request", no further checks are performed
(a) get the information about the service requested from the MPTO or PTJA areas, or directly
from the user.
(b) if these areas just ask for a tariff (and not a transaction), go to (g)
(c) get user's ID
(d) obtain the corresponding contracts
(e) get user's choice of contract
(f) check with "Access" and/or "Credit Control" and, if necessary, register a violation.
(g) send the choice and contract to 1.3.6 to check if advanced payment has been made
(h) send the different elements to 1.3.5 to initiate the computation of the corresponding fee
(i) if payment has already been completely made, send an agreement to the "Access Control"
system
(j) if not, reduce the fee by the amount already paid, send the elements to 1.3.7 to recover
fees
(a) analyse the contract to determine the tariff included for the specified service, taking into
account the vehicle's position.
(b) extract from the store of "tariffs" Data the corresponding fees
(c) compute the exact fee, taking into account elements from the contract (rebates.…), and
from the traffic conditions
(a) receive payment elements from 1.3.4 or 1.3.5: amount, payment mode,
(b) ask the user for payment,
(c) check the payment. If an account number is given, and if the number is on the black list,
register a violation.
if payment is correct :
(d) confirm with "Credit Control"
(e) in case of a payment made by a freight vehicle, send a receipt to the MFFO area.
(f) send an acceptance message to the user
(a) read the information about the transaction, and extract the operators ID and service
concerned
(b) extract from the store of "service information" Data the rules to be followed concerning the
allocation of revenue for this service
(c) compute the corresponding revenue for each operator
(d) send the result to the Credit Operator's Account function
(a) read the different elements included in the message coming from "Distribute Fee
Revenues".
(b) sends the credit order to the financial clearinghouse, including the fee, the originating
account, and the account to be credited,
(c) load the transaction into the store of "transactions" Data.
(a) wait for an emergency to be planned

(b) load all information on emergency
(c) choose the right procedure for the emergency
(d) inside the procedure:
- contact emergency services
- plan their intervention : select the emergency route (pre-defined route or new computed one
if needed)
- send the selected route to emergency driver
- store the plan
- request for emergency processing.
(b) when the planned emergency route data flow is received in (a) implement the route that it
contains
(c) use the data in the digital map data for emergency vehicle and location data flows to
determine which part of the emergency route is to be implemented next and for which
guidance will be needed
(d) using the results from (c), provide route guidance instructions to the emergency vehicle
driver using the emergency route guidance data flow
(e) use the data in (c) to determine which are the next road segments and use this data in the
emergency vehicle approaching data flow which shall be sent to the Mange Infrastructure to
Vehicle Communications function
(f) the activities in (d) and (e) shall stop when the data in (b) and (c) shows that the emergency
vehicle has reached the end of the green wave route
(g) when the green wave request data flow is received in (a) from the emergency vehicle
driver, use the data in the digital map data for emergency vehicle and location data flows to
determine the location and identity of the next signalised junction in the direction of travel of
the vehicle
(h) put the data obtained in (g) into the emergency local priority request data flow and send it
to the Output Stop & Go Commands function so that local priority can be provided
(i) repeat (g) and (h) until the green wave request data flow contains a null indicating that
priority is not longer required
(j) when the deploy virtual cones data flow is received in (a) from the emergency vehicle
driver, use the use the data in the digital map data for emergency vehicle and location data
flows to determine where the virtual cones need to be deployed
(k) put the data obtained in (j) into whichever is appropriate of the inter-urban virtual coned
area request and/or urban virtual coned area request data flows and send them the
the vehicle
appropriate Implement Traffic Control function
(l) when the global emergency progress report data flow is received in (a) output its contents
to the emergency vehicle driver in the global emergency data flow
(m) when the individual emergency progress report data flow is received in (a) from the
(a) emergency
wait for an emergency to be
vehicle driver, useplanned
its contents to create the report and send it to the Process
(b) load all information
Emergency Progress on emergency
Reports function in the individual emergency progress report data flow
(c) choose the right procedure for the emergency
(d) inside the procedure:
- contact emergency services
- plan their intervention : select the emergency route (pre-defined route or new computed one
if needed)
- send the selected route to emergency driver
- store the plan
- request for emergency processing.
(a) continuously monitor for receipt of the operator urban traffic management request, planned
urban traffic management request, urban environmental inputs, urban demand management
strategy and urban incident strategy request data flows
commands apply
flow
(e)
(a)ifcontinuously
the urban zoning monitor strategy data of
for receipt flowtheisoperator
received,inter-urban
whichevermanagement
is necessary request,
of the data flows
planned
in (c) shall be sent plus the urban zone access vehicle list
inter-urban traffic management request, inter-urban environmental inputs, inter-urban demand data flow
(f) it shall be possible forstrategy
management the dataand flows containing
inter-urban currentstrategy
incident urban trafficrequestconditions,
data flows urban traffic
flow management
(b) when anydata, of thepredicted
data flows urbanin (a) network data, implement
is received, bridge urban theinputs
trafficand tunnel urban
management
inputs
commands to be continuously
that they contain monitoredusing and for their contents
the contents of the data to be
flowused to revise
containing the detail static
inter-urban of the
commands
data to determine being implemented
which are theinappropriate
(b) thus providing section(s)adaptive traffic control
if the inter-urban road network to which
(g) if the operator urban traffic management the commandsrequest apply
was received in (a) and had led to the
implementation
(c) the commands of (b) in and (b)(c) thenbethe
shall operator urban
implemented usingtraffic
somemanagement response data
or all of the inter-urban bridgeflow
shall be sent
inputs, to the Provide
inter-urban Operator
tunnel inputs, Interface lane
inter-urban function
requests, inter-urban speed setting, inter-
(h) as atraffic
urban resultmanagement
of (c) the receipt of the urban
l&s request, traffic management
inter-urban traffic management s&g response, urbanand
c&i requests traffic
inter-
management l&s response and urban traffic management
urban recommended routes data flows, plus through data sent to the Traffic Simulation c&i response data flows shall be
monitored functionality in the inter-urban strategies in use data flow
(i)(d)
whenthe any of the data
commands being flows in (h) is received
implemented theirbe
in (b) shall contents
filtered shall be checkedand
for applicability to see
sentiftotheany
commands
other adjacent in (c)inter-urban
are being followedtraffic management systems in the inter-urban traffic management
(j) if the result
strategy data of (i) and
flow is that the commands
to any relevant urban are traffic
not being followed, this
management shall in
systems bethe
communicated
inter-urban to
to the Provide Operator Interface function
urban trafficincommands
the operator data urban
flowmanagement response data
flow
(e) ifandtheto the Maintenance
inter-urban Management
zoning strategy data flowfunctionality
is received, in the urban response
whichever fault data
is necessary of theflowdata
(k) if theflowsrequirement
in (c) shallis included
be sent in plusthethe contents of thezone
inter-urban dataaccess
flows invehicle
(b) thelist
contents
data flow of the
data
(f) itflows
shallinbe(i)possible
shall befor used thetocontents
revise the commands
of the data flows being sent in (c)
containing current inter-urban traffic
(l) ifconditions,
either the inter-urban
inter-urban to urban
traffic flow traffic commands
management or urban
data, trafficinter-urban
predicted management strategy
network data,
data flows is received, their contents shall be analysed if necessary
bridge inter-urban inputs and tunnel inter-urban inputs to be used to revise the detail of the new commands
implemented as in (c) with thecommands addition that requests
being may bein
implemented sent
(b) to any relevant multi-modal
management systems in the urban crossing inhibit data flow
urban traffic management l&s request, inter-urban traffic management c&i requests and inter-
urban recommended routes data flows, plus through data sent to the Traffic Simulation
functionality in the inter-urban strategies in use data flow
other adjacent inter-urban traffic management systems in the inter-urban traffic management
strategy data flow and to any relevant urban traffic management systems in the inter-urban to
(e) if the inter-urban zoning strategy data flow is received, whichever is necessary of the data
flows in (c) shall be sent plus the inter-urban zone access vehicle list data flow
(f) it shall be possible for the contents of the data flows containing current inter-urban traffic
conditions, inter-urban traffic flow management data, predicted inter-urban network data,
bridge inter-urban inputs and tunnel inter-urban inputs to be used to revise the detail of the
commands being implemented in (b)
(g) if the operator inter-urban management request was received in (a) and had led to the
implementation of (b) and (c) then the operator inter-urban management response data flow
(h) as a result of (c) the receipt of the inter-urban traffic management l&s response and inter-
urban traffic management c&i response data flows shall be monitored
(i) when either of the data flows in (h) is received their contents shall be checked to see if the
(j) if the result of (i) is that the commands are not being followed (or either of the data flows is
not received within a given time frame), this shall be communicated to the Provide Operator
Interface function in the operator inter-urban management response data flow and to the
Maintenance Management functionality in the inter-urban response fault data flow
Functional Requirements
(l) if either the urban to inter-urban traffic commands or inter-urban traffic management
(a) wait fordata
strategy an emergency to be planned
flows is received, their contents shall be analysed if necessary new commands
(b) load all information
implemented on emergency
as in (c) with the addition that requests may be sent to any relevant multi-modal
(c) choose the managementright procedure for the in
systems emergency
the inter-urban crossing inhibit data flow
(d) (m) inside the procedure:
if the inter-urban emergency route request data flow is received, its contents shall be
- contact emergency
implemented services
as in (b) and (c) above and shall take priority over any of the other inputs
- plan their intervention : select the emergency received inroute (pre-defined
(a) and (l) route or new computed one
if(n)needed)
if the inter-urban virtual coned area request data flow is received, implement the necessary
- lane
sendclosures
the selected route to
and speed emergency
restrictions asdriver
in (b) and (c) above in order to prevent vehicles from
- store the plan entering the area around an accident
-(o)request for emergency
the commands in the processing.
operator inter-urban traffic management request data flow received in
(a) shall take precedence over all the inputs in (a) and (l) but not those in (m) and (n)
(a)
(p) continuously
the commands monitor
in the for receiptinter-urban
planned of the operator
trafficurban traffic management
management request datarequest, planned
flow received in
urban traffic management request, urban environmental inputs, urban demand
(a) shall take the lowest priority after all the other inputs in (a), (l), (m) and (n) management
strategy and urban incident
(q) implementation strategy
of all the outputsrequest
in (c) data
shall flows
be checked to ensure that the commands
(b) when any of the data flows in (a) is received,
being implemented are consistent and coherent implement
and dothenot
traffic management
contradict each other.
commands apply
flow
(e) if the urban zoning strategy data flow is received, whichever is necessary of the data flows
in (c) shall be sent plus the urban zone access vehicle list data flow
(f) it shall be possible for the data flows containing current urban traffic conditions, urban traffic
flow management data, predicted urban network data, bridge urban inputs and tunnel urban
inputs to be continuously monitored and for their contents to be used to revise the detail of the
commands being implemented in (b) thus providing adaptive traffic control
(g) if the operator urban traffic management request was received in (a) and had led to the
implementation of (b) and (c) then the operator urban traffic management response data flow
(h) as a result of (c) the receipt of the urban traffic management s&g response, urban traffic
management l&s response and urban traffic management c&i response data flows shall be
monitored
(i) when any of the data flows in (h) is received their contents shall be checked to see if the
(j) if the result of (i) is that the commands are not being followed, this shall be communicated
to the Provide Operator Interface function in the operator urban management response data
flow and to the Maintenance Management functionality in the urban response fault data flow
(l) if either the inter-urban to urban traffic commands or urban traffic management strategy
data flows is received, their contents shall be analysed if necessary new commands
(b) when the planned emergency route data flow is received in (a) implement the route that it
contains
(c) use the data in the digital map data for emergency vehicle and location data flows to
determine which part of the emergency route is to be implemented next and for which
guidance will be needed
(d) using the results from (c), provide route guidance instructions to the emergency vehicle
driver using the emergency route guidance data flow
the vehicle
appropriate Implement Traffic Control function
(l) when the global emergency progress report data flow is received in (a) output its contents
to the emergency vehicle driver in the global emergency data flow
(m) when the individual emergency progress report data flow is received in (a) from the
emergency vehicle driver, use its contents to create the report and send it to the Process
Emergency Progress Reports function in the individual emergency progress report data flow.
(a) continuously monitor for arrival of all the input data flows
(b) when any of the data flows containing updates of travel conditions or the location of
vehicles carrying hazardous goods is received in (a), store their contents locally for future use,
replacing any data received previously unless it is from a different traffic control centre, or
service provider
(c) when the trip plan for monitoring data flow is received in (a), store the trip plan data locally
for use in monitoring the progress of the traveller as the trip is implemented
(d) when the traveller location data flow is received in (a), compare this with the expected
location according to the trip plan data to determine if the traveller has deviated from following
the trip plan
(e) use the data in (b) and (d) to calculate the predicted arrival times at the trip destination and
any way points to be encountered before the destination is reached
(f) also use the data in (b) and (d) to assess whether the conditions under which the trip was
planned have significantly changed
(g) if the answer to either (e) or (f) is that the trip plan needs to be changed, then send the
revise implementing trip plan request data flow to the Manage Production of the Revised Trip
Plan function
(h) continue with (b) plus (d) to (f) until the trip plan for monitoring data flow is again received
in (a), after which (c) to (g) should be repeated
(i) as the trip progresses, collect journey times for each segment of the road network that is
used
(a) in the trip monitor for the receipt of the receipt of the basic trip parameters data flow
continuously
(j) usethe
from thepre-trip
data intraveller
(i) to produce journey times and O-D data for segments in the inter-urban
andwhen
(b) urbanthe road
datanetwork
flow inused (a) isinreceived,
the trip plan
if required send the request applicable GTP
(k) as soon as
parameters datait isflow
available, i.e. before
to the function andthewaitendforofthe
theresponse
trip, put the data
in the from (j) into
requested the inter-
applicable
urban road use data
GTP parameters datafrom flowtrip and urban road use data from trip data flows, and send them to
the send
(c) Inter-urban
the requestTrafficpreferences
Data Management data flowand Urban Traffic
requesting Data Management
any changes to the General functions
Trip
respectively (GTP) data to the pre-trip traveller and wait for the response in the additional trip
Preferences
(l) when the data
parameters trip hasflowbeen completed, collect data about its implementation, remove the
Traveller
(d) when identity
the response and any dataother
flowpersonal
is received data inand
(c), send
use itsit contents
to the Evaluate
and allTrip After data
the other
Completion
provided by functionthe traveller in the to trip completion
prepare the tripreport for evaluation put
plan requirements, datathem
flow.in the traveller trip
requirement data flow and send it to the Trip Planning function
(e) as a result of (c) wait for the receipt of the traveller trip description data flow from the Trip
Planning function and when it is received, store the trip plan description internally for later use
(f) output the trip plan description received in (e) to the pre-trip traveller in the initial trip plan
data flow
(g) as a result of (f) wait for a response from the pre-trip traveller in the modified trip
parameters data flow
(h) use the data provided by the data flow in (g to modify the original trip parameters, put them
in the modified trip plan requirements data flow and send it to the Trip Planning function
(i) as a result of (h) await receipt of the traveller trip description data flow from the Trip
Planning functionmonitor
(a) continuously and when it isreceipt
for the received of store
the inputthe data
trip plan
flowsdescription internally for later use
(j) output
(b) use the the alternative
map data for trip travelplan description
information and received
location infor
(i) to the pre-trip
information traveller
data in the tripin
flows received
alternatives
(a) to provided data flow map
digital and waitdatafor onawhich
response
to base frominformation
the pre-triprequested
traveller inbythe
themodified
travellertrip
and
parameters
the data flow
current location of the traveller
(k) when
(c) continue repeating
in (a) the traveller (e) through
information(i) until no modified
request parameters
data flow arerequest
is received, provided thebyinformation
the pre-trip
traveller
from the in the of
store modified trip parameters
Travel Information Datadata
using flow,
thebut givingtravel
request each information
revised trip data
plan flow
description
a new
(d) identity
collect so that it can
the requested be retrieved
information frominstead
the read of travel
the other trip plan data
information descriptions
flow when it is
(l) output and
received the select
process tripit data
readyflow for to the pre-trip
output traveller and await a response through the
to the traveller
input
(e) whenof theall trip
the selection
information data flow
is present in (d) send the requested information to the traveller
(m) use
using thethe input in (l)
requested to select
travel the required
information trip plan description from the internal store and
data flow.
check to see if any bookings need to be made and paid for, or the trip plan service needs to
be paid for
(n) if the answer in (m) is YES, send the selected trip plan description to the Make Bookings
and Payments for Trip function in the full trip description for bookings data flow
(o) if the answer in (m) is NO, send the selected trip plan description to the Enable Final
Approval of Trip Plan function in the full trip description no bookings data flow
(a) continuously monitor for the receipt of the traveller trip requirements and vehicle trip plan
request data flows
(b) when the traveller trip requirements data flow is received in (a), use the trip planning
information to fulfil the traveller's trip request from the stores of Road Trip Planning Data
and/or PT Trip Planning Data and produce a trip plan
(c) in addition to (b) include in the trip plan a choice from different routes for the road part of
the trip that use the motorway networks, secondary road networks, scenic routes and so forth
depending on the criteria provided by the traveller and the travel information operator, plus
recommendations received from TCC's in the inter-urban recommended routes and urban
recommended routes data flows
(d) in addition to (b) and (c) include in the trip plan a choice of travel modes, where they
provide sensible alternatives, or have been requested by the traveller
(e) if required by the traveller details of both single and return trips, including those where the
date of the return part of the trip may be some time ahead of that for the outward part shall be
included in the trip plan
(f) when the preparation of a new/revised trip plan is completed, it shall be sent back to the
traveller interface in the traveller trip description data flow
(a)
(g) continuously
as a result of monitor (f) continuously for the receipt
monitor offor
thereceipt
receiptofofthe themodified
basic triptripparameters data flowdata
plan requirements
from
flow andthe pre-trip
if received traveller
within a short time, repeat (b) to (g) using the revised requirements
(b)
(h) when the data vehicle flow tripinplan
(a) isrequest
received, dataif required send the
flow is received in request
(a), useapplicable
the data it GTP contains to
parameters
produce a vehicle data flow based to the tripfunction and wait
plan, fulfilling thefor the response
requirements of in(c)the
andrequested applicable
(e) but include other
GTP parameters
information such as data theflowneed to book parking places for freight vehicles so that goods can be
(c) sendorthe
loaded request preferences data flow requesting any changes to the General Trip
unloaded
Preferences (GTP) data of
(i) when the preparation to a the pre-trip traveller
new/revised trip planandiswait for the response
completed, it shall beinsentthe back
additional
to thetrip
parameters
vehicle interface data in flow the vehicle trip plan response data flow
(d) when
(j) all the response
trip plans shall include data flow is received in
any appropriate (c), use about
warnings its contents and allconditions,
the existing the other data safety
provided
recommendationsby the traveller and the to expected
prepare the trip planat
conditions requirements,
the planned time put them in the traveller
of travelling trip
on the route(s)
requirement
that they include data flow and send it to the Trip Planning function
(e) as a result
(k) when revising of (c)a partwaitcompleted
for the receipt of thepropose
trip plan, travelleralternative
trip description modes data flow times
and/or from the Trip
of travel
Planning
to those infunction
the remainder and when it is plan
of the received, store the trip plan description internally for later use
(f) output
(l) all the trip
trip plans planbedescription
shall produced receivedaccordinginto(e) to thethat
criteria pre-trip
are settraveller
up and in modified
the initial by tripthe
plan
data
travelflowinformation operator so that trips conform to the current travel and/or traffic
(g) as a resultpolicies
management of (f) wait for a response from the pre-trip traveller in the modified trip
parameters
(m) it shall be data flow to prepare trip plans with a minimum set of road traffic data that only
possible
(h)
(a) use
includes the datatimes
travel
continuously provided
monitor for each bythe
for the data flow
segment
receipt in (g
of the to modify
road
input network
data flowsthe original trip parameters, put them
in
(n)the
(b) use modified
the maptrip
continuously plan
monitor
data forrequirements
for
travelreceipt of data
information any of flow
and and
datasend
thelocation forit information
flows to
fromthetheTrip Planning
Provide Tripfunction
data flows Planning
received in
(i) as
to aprovided
Operator
(a) result ofdigital
Interface (h)function
await
mapreceipt data on of which
the traveller
to basetrip description
information data flowby
requested fromthethe Trip and
traveller
Planning
(o) when
the current function
the request
location and oftripwhen
the it is received
planning
traveller criteria store
data flowthe trip plan description
is received internally
in (n), collect for later
the criteria use
from
(j)
theoutput
(c) internal
when the(a)
in alternative
store theoftraveller
criteria tripusedplan indescription
information (c) andrequest received
send it back
data in the
flow (i)isto
toethe pre-trip
Provide
received, traveller
Trip
request Planning in the trip
Operator
the information
alternatives
Interface
from the store data
function flow
in the
of Travel and wait for atrip
requested
Information response
Data usingfrom
planning the pre-trip
criteria
the request datatravel
flow traveller in the data
information modified
flow trip
parameters
(p) collect
(d) when the thedata
update flowtrip planning
requested information criteria
fromdata flow travel
the read is received in (n), use
information dataitsflowcontents
when ittoisupdate
(k)
the continue
internal
received repeating
andstore process it(e)
of criteria through
ready used for in(i)(c)
outputuntiltono themodified
travellerparameters are provided by the pre-trip
traveller
(q) when
(e) inallthe
continuously themodified
monitortrip
information for parameters
receipt
is present indata
of the flow,trip
vehicle
(d) send butplan
the giving
requested each
criteria revised trip
changes
information toplan
data theflow description
traveller
a
(r)new
when
using identity
the the data
requestedso that
flow itincan
travel be retrieved
(q)information
is received, instead
update
data flow.theof thepartother
of the trip plan descriptions
internal store of criteria used in
(l)
(c)output
that is the used select trip data
to prepare flow to
vehicle tripthe pre-trip traveller and await a response through the
plans.
input of the trip selection data flow
(m) use the input in (l) to select the required trip plan description from the internal store and
check to see if any bookings need to be made and paid for, or the trip plan service needs to
be paid for
request data flows
(g) as a result of (f) continuously monitor for receipt of the modified trip plan requirements data
flow and if received within a short time, repeat (b) to (g) using the revised requirements
(h) when the vehicle trip plan request data flow is received in (a), use the data it contains to
produce a vehicle based trip plan, fulfilling the requirements of (c) and (e) but include other
information such as the need to book parking places for freight vehicles so that goods can be
loaded or unloaded
(i) when the preparation of a new/revised trip plan is completed, it shall be sent back to the
vehicle interface in the vehicle trip plan response data flow
(j) all trip plans shall include any appropriate warnings about the existing conditions, safety
recommendations and the expected conditions at the planned time of travelling on the route(s)
that they include
(a) when the environment information data flow is received, send the appropriate parts of its
(k) when revising a part completed trip plan, propose alternative modes and/or times of travel
contents to the driver and the traveller.
to those in the remainder of the plan
(l) all trip plans shall be produced according to criteria that are set up and modified by the
travel information operator so that trips conform to the current travel and/or traffic
management policies
(m) it shall be possible to prepare trip plans with a minimum set of road traffic data that only
includes travel times for each segment of the road network
(n) continuously monitor for receipt of any of the data flows from the Provide Trip Planning
Operator Interface function
(o) when the request trip planning criteria data flow is received in (n), collect the criteria from
the internal store of criteria used in (c) and send it back the toe Provide Trip Planning Operator
Interface function in the requested trip planning criteria data flow
(p) when the update trip planning criteria data flow is received in (n), use its contents to update
the internal store of criteria used in (c)
(q) continuously monitor for receipt of the vehicle trip plan criteria changes data flow
(r) when the data flow in (q) is received, update the part of the internal store of criteria used in
(c) that is used to prepare vehicle trip plans.
(a) continuously monitor for the receipt of the data flows from functionality in the Manage
Traffic Functional Area
(b) when any of the data flows in (a) arrive, their contents shall be immediately loaded into the
store of Road Trip Planning Data and fused with any data that is already present to provide a
coherent set of current and historic traffic data
(c) if the road network traffic predictions data flow is not received, predicted travel time data for
every segment of the road network shall be calculated based on the current and historic travel
data received in the other data flows
(d) the results from (c) shall be loaded into the store of Road Trip Planning Data to take the
place of the data that would have been received in the road network traffic predictions data
flow
(e) the journey time data from (b) or (d) shall be sent to the Other Navigation Device in the
data flow containing traffic data
(f) continuously monitor for the receipt of traffic data from the Other Navigational Device in the
(g) when the data flow in (f) is received, load the data it contains into a separate part of the
store of Road Trip Planning Data that is reserved for data from Other Navigation Devices.
request data flows
loaded or unloaded
that they include
to those in the remainder of the plan
(l) all trip plans shall be produced according to criteria that are set up and modified by the
travel information operator so that trips conform to the current travel and/or traffic
management policies
includes travel times for each segment of the road network
(n) continuously monitor for receipt of any of the data flows from the Provide Trip Planning
(o) when the request trip planning criteria data flow is received in (n), collect the criteria from
the internal store of criteria used in (c) and send it back the toe Provide Trip Planning Operator
Interface function in the requested trip planning criteria data flow
(p) when the update trip planning criteria data flow is received in (n), use its contents to update
(a) continuously monitor for the receipt of the input data flows
(b) use the map data for travel information and location for information data flows received in
(a) to provided digital map data on which to base information requested by the traveller and
the current location of the traveller
(c) when in (a) the traveller information request data flow is received, request the information
from the store of Travel Information Data using the request travel information data flow
(d) collect the requested information from the read travel information data flow when it is
received and process it ready for output to the traveller
(e) when all the information is present in (d) send the requested information to the traveller
using the requested travel information data flow.
(a) continuously monitor for the receipt of the input data flows that contain information that
might be requested by the traveller
(b) when any of the data flows in (a) is received, process its contents applying the filters (if
any) that have been defined by the travel information operator
(c) when (b) is complete, send the information to the Manage Travel Information Data Store
function using the updated travel information data flow
(d) if the request travel information filters data flow is received, respond to the Provide Travel
Information Operator Interface function with the a copy of the current filters using the
requested travel information filters data flow
(e) if the updated travel information filters data flow is received, store the new filters internally
for use in the generation of future travel information
(a) continuously monitor for the receipt of the travel information for output data flow
(b) when the data flow in (a) is received, output the travel information directly to the travellers
using the travel information data flow
(a) continuously monitor for the receipt of the travel information for output data flow
(b) when the data flow in (a) is received, output the travel information directly to the travellers
using the travel information data flow
request data flows
loaded or unloaded
request data flows
loaded or unloaded
that they include
(a) continuously monitor for arrival of all the input data flows
(b) when any of the data flows containing updates of travel conditions or the location of
vehicles carrying hazardous goods is received in (a), store their contents locally for future use,
replacing any data received previously unless it is from a different traffic control centre, or
service provider
(c) when the trip plan for monitoring data flow is received in (a), store the trip plan data locally
for use in monitoring the progress of the traveller as the trip is implemented
(d) when the traveller location data flow is received in (a), compare this with the expected
location according to the trip plan data to determine if the traveller has deviated from following
the trip plan
(e) use the data in (b) and (d) to calculate the predicted arrival times at the trip destination and
any way points to be encountered before the destination is reached
(f) also use the data in (b) and (d) to assess whether the conditions under which the trip was
planned have significantly changed
(g) if the answer to either (e) or (f) is that the trip plan needs to be changed, then send the
revise implementing trip plan request data flow to the Manage Production of the Revised Trip
Plan function
(h) continue with (b) plus (d) to (f) until the trip plan for monitoring data flow is again received
in (a), after which (c) to (g) should be repeated
(i) as the trip progresses, collect journey times for each segment of the road network that is
used
(a) in the trip monitor for the receipt of the receipt of the basic trip parameters data flow
continuously
(j) usethe
from thepre-trip
data intraveller
(i) to produce journey times and O-D data for segments in the inter-urban
andwhen
(b) urbanthe roaddatanetwork
flow inused (a) isinreceived,
the trip planif required send the request applicable GTP
(k) as soon as
parameters data it isflow
available, i.e. before
to the function andthewaitendforofthe
theresponse
trip, put the data
in the from (j) into
requested the inter-
applicable
urban road use data
GTP parameters datafrom flowtrip and urban road use data from trip data flows, and send them to
the send
(c) Inter-urban
the requestTrafficpreferences
Data Management data flowand Urban Traffic
requesting Data Management
any changes to the General functions
Trip
respectively (GTP) data to the pre-trip traveller and wait for the response in the additional trip
Preferences
(l) when the data
parameters trip has flowbeen completed, collect data about its implementation, remove the
Traveller
(d) when identity
the response and any data other
flowpersonal
is received data inand
(c), send
use itsit contents
to the Evaluate
and allTrip After data
the other
Completion
provided by function
the traveller in the to trip completion
prepare the tripreport for evaluation put
plan requirements, datathem
flow in the traveller trip
requirement data flow and send it to the Trip Planning function
(e) as a result of (c) wait for the receipt of the traveller trip description data flow from the Trip
Planning function and when it is received, store the trip plan description internally for later use
(f) output the trip plan description received in (e) to the pre-trip traveller in the initial trip plan
data flow
(g) as a result of (f) wait for a response from the pre-trip traveller in the modified trip
parameters data flow
(h) use the data provided by the data flow in (g to modify the original trip parameters, put them
in the modified trip plan requirements data flow and send it to the Trip Planning function
(i) as a result of (h) await receipt of the traveller trip description data flow from the Trip
Planning functionmonitor
(a) continuously and when it isreceipt
for the received of store
the inputthe data
trip plan
flowsdescription
that contain internally for later
information thatuse
(j) output
might the alternative
be requested by the triptraveller
plan description received in (i) to the pre-trip traveller in the trip
alternatives
(b) when anydata of the flow andflows
data wait infor(a)
a response
is received, from the pre-trip
process traveller
its contents in the modified
applying the filterstrip
(if
parameters
any) that have data been flowdefined by the travel information operator
(k) when
(c) continue (b) repeating
is complete, (e) send
through the (i) until no modified
information parameters
to the Manage areInformation
Travel provided byData the Store
pre-trip
traveller using
function in the themodified
updated trip travel
parameters data flow,
information data butflowgiving each revised trip plan description
a new
(d) if theidentity
request so travel
that it information
can be retrieved filtersinstead
data flow of is
thereceived,
other triprespond
plan descriptions
to the Provide Travel
(l) output theOperator
Information select trip data flow
Interface to the with
function pre-trip
the traveller
a copy ofand theawait
currenta response
filters usingthrough
the the
input of thetravel
requested trip selection
information datafilters
flow data flow
(m)ifuse
(e) thethe input in
updated (l) toinformation
travel select the required
filters data tripflow
planisdescription
received, storefromthethenewinternal store
filters and
internally
check
for usetoinsee the ifgeneration
any bookings needtravel
of future to be information
made and paid for, or the trip plan service needs to
be paid for
(a) continuously monitor for receipt of the trip plan implementation data flow
(b) when the data flow in (a) is received, put the contents in the implement trip plan data flow
and send it to the Manage Store of Trip Plan Data function
(c) as a result of (b) continuously monitor for receipt of the trip guidance instructions data flow
(d) when the data flow in (c) is received, output the instructions to the Traveller in the most
appropriate form using the route guidance information data flow
(e) continuously monitor for receipt of the trip plan changes for traveller data flow
(f) when the data flow in (e) is received, output the details of the changes to the Traveller in
the implement trip plan changes data flow
(g) as a result of (f), continuously monitor for receipt of the trip plan change data flow
(h) when the data flow in (g) is received put the contents in the trip plan changes response
data flow and send it to the Manage Production of Revised Trip Plan function
(i) continuously monitor for receipt of the request implementing trip plan change data flow
(j) when the data flow in (i) is received, put the contents on the trip plan changes request data
flow and send it to the Manage Production of Revised Trip Plan function
(k) repeat (d) and (f)
(l) continuously monitor for receipt of the GTP data updates data flow
(m) when the data flow in (l) is received, send the data to the Evaluate Trip After Completion
function in the trip results from traveller data flow.
(a) when the first trigger input data flow is received, the command shall be checked for syntax
and consistency
(b) when (a) is complete, the action needed shall be determined
(c) if the result of (b) is that the action needed is to output incident data or produce a statistical
report, the request for the retrieval of the data and preparation of the report shall be sent to
the Manage Store of Incident Data function using the first trigger output data flow
(d) when the result of (c) is received through the third trigger input data flow, the contents shall
be output directly to the Operator
(e) if the result of (b) is that implementation of an incident management strategy is to be
confirmed, or a new strategy is being provided, the data shall be sent to the incident
assessment Function using the second trigger output data flow
(f) if the result of (b) is that new incident data or assessment "rules" are being provided then
the data shall be sent to the Identification and Classification function using the third trigger
output data flow
(g) when the third trigger input data flow is received, the contents shall be output to the
operator using the other output data flow.
flow
store of Road Trip Planning Data that is reserved for data from Other Navigation Devices.
(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.
(a) continuously monitor for receipt of the freight and hazardous goods information plus on-
board information and requests data flows
(b) when either of the data flows in (a) is received, send their contents to the store of Road
Trip Planning Data in the data flow containing store ffm and hazardous goods data
(c) continuously monitor for receipt of any of the "request....situation" data flows
(d) when any of the data flows in (c) is received, obtain the required data from the store of
Road Trip Planning Data using the data flows called store ffm and hazardous goods data and
retrieve road situation data
(e) when the data in (d) has been retrieved, send it back to the Manage Freight and Fleet
Operations (mffo) functionality that requested it using the "answer....situation" data flow that
corresponds to the request
(f) continuously monitor for receipt of the route optimisation request data flow from the
Manage Freight and Fleet Operations (mffo) functionality and the hazardous goods vehicle
route request data flow from the Provide Support for Cooperative Systems (pscs) functionality
(g) when either of the data flows in (f) is received, prepare a route according to the parameters
contains in the request and data that is retrieved from the store of Road Trip Planning Data
using the data flows called store ffm and hazardous goods data and retrieve ffm route
planning data
(h) when the route has been prepared in (g) send it back to the Manage Freight and Fleet
Operations (mffo) functionality and the Provide Support for Cooperative Systems (pscs)
functionality in the
(a) the Function route
shall and data
collect hazardous goodsfrom
as it arrives vehicle route response
functionality data flows
in the Manage respectively.
Public
Transport Operations Functional Area
(b) the Function shall load the data into the store of PT Trip Planning Data as soon as it is
received
flow
store of Road Trip Planning Data that is reserved for data from Other Navigation Devices
request data flows
produce a vehicle
(a) continuously based for
monitor tripreceipt
plan, fulfilling
of any ofthethe
requirements
input data flows of (c) and (e) but include other
information
(b) when any such
of theas data
the needflowstocontaining
book parking dataplaces
about for freight
traffic using vehicles
the urbanso that
roadgoods
networkcanisbe
loaded or process
received, unloadedthe data, applying data fusion where the data relates to the same part of the
(i) when
road the preparation of a new/revised trip plan is completed, it shall be sent back to the
network
vehicle
(c) use theinterface in the vehicle
data received in thetripurbanplanstatic
response
data for data flowconditions data flow to determine
traffic
(j) alllocation
the trip plans andshall include anyofappropriate
characteristics the part of warnings
the urbanabout the existing
road network conditions,
to which safety
the received
recommendations
data applies and the expected conditions at the planned time of travelling on the route(s)
thatconvert
(d) they include
the contents of data flow containing urban infrastructure usage data into actual
(k) when
traffic flowsrevising
and applya partit completed
to the correct trippart(s)
plan, propose
of the urban alternative modes and/or times of travel
road network
to those
(e) load the in the remainder
results of (b) to of (d)
theinto
planthe store of Urban Traffic Data, to provide the current
(l) all trip
traffic flowplans
data shall be produced
and fusing according
it with data alreadyto in
criteria
the store that to areprovide
set up aand modified
coherent setbyof the
historic
travel data
traffic information
for the operator
urban network so that trips conform to the current travel and/or traffic
management
(f) also use thepoliciesresults of (b) to (d) to provide traffic data for other urban traffic management
systems
includes
(g) analyse travel
the times
results forofeach
(b) tosegment of the road
(d) to determine wherenetwork traffic queues are present and from use
(n) continuously
successive monitor
collections offor
datareceipt of any ofthe
to determine thespeed
data flows from the Provide
of propagation Trip
of the tail Planning
end of the
queue
(o) use
(h) whenthe thedata
request
receivedtrip planning
in the urban criteria data
static dataflow foristraffic
received in (n), collect
conditions data flowthetocriteria from
determine
internal store
the locations of the of queues
criteria used in (c) and send it back the toe Provide Trip Planning Operator
Interface
(i) send the function
resultsinofthe (g)requested
and (h) to trip theplanning criteria data
output warnings to the flow
driver in the vehicle functionality
(p)analyse
(j) when the theupdate
resultstrip of planning
(b) to (d) criteria data flow
to determine the is received
current in (n),
journey usefor
time itseach
contents to update
segment of
internalroad
the urban store of criteria
network store used
it ininthe(c)store of Urban Traffic Data, fusing it with similar data
(q) continuously
already in the store monitor for receipt
to provide of the vehicle
a historical record of tripjourney
plan criteria
times changes data flow
(r) when
(k) use the theresults
data flowof (b) in to
(q)(d)is received,
to provideupdate
the outputthe partdataof the internal
flows containingstore of criteria
current trafficused
datain
(c) that
that is be
shall usedsentto directly
preparetovehicle trip plans. and to the function for transmission to other
other functionality
entities and functionality in other functional areas
(l) periodically read the journey times from the store of Urban Traffic Data and use them to
update the default urban road segment journey times using the default urban journey time
(a) continuously monitor for the receipt of the any of the input data flows
(b) when the data flow inter-urban traffic information request is received in (a), output the
current traffic information to the broadcaster using the data flow containing inter-urban traffic
data
(c) when the inter-urban traffic data for output data flow is received in (a), store its contents
locally updating any previously received data that has been changed
(d) when (c) is complete, output the revised version of the inter-urban traffic data to
functionality in other Functional Areas, the broadcaster and the traffic and travel information
provide in the appropriate output data flows
(e) when either the inter-urban lane instructions or the inter-urban speed limit changes data
flows are received in (a), repeat (c) and (d) for the data that they contain.
using the requested travel information data flow
(a) continuously monitor for the receipt of the full trip description no bookings and full trip
description with bookings data flows
(b) when either of the data flows in (a) is received, put the trip plan details into the itinerary
initial data flow and send it to the pre-trip traveller
(c) continuously monitor for receipt of the final approval data flow from the pre-trip traveller
(d) when the data flow in (c) is received, check to see if the traveller has given final approval
(e) if the approval has been received in (d), send all of the trip plan data to the Manage Store
of Trip Plan Data function in the trip plan ready for implementation data flow
(f) if a rejection has been received in (d), send the trip plan rejected data flow to the Provide
Traveller with Trip Planning Interface function so that the trip plan can be deleted and the trip
planning process re-initiated, plus the cancel bookings for trip data flow to the Make Bookings
and Payments for Trip function so that all bookings can be cancelled.
This Function shall enable the Traveller to specify a set of factual data to be used as General
Trip Preferences (GTP) for use each time they want to plan a trip. This shall be done once as
a preparation to full personalisation. Once a planned trip has been completed, the Function
shall ask the Traveller for any comments on the performance of the trip and any changes that
are needed to the GTP data. The Function shall also enable the Traveller to have an output
of their current GTP data and to amend that data, even if this is not the result of the
performance of a planned trip.
(a) when the trigger input data flow is received, check its contents
(b) if it contains new data for either of the stores of Road Trip Planning Data or PT Trip
Planning Data, then update the appropriate store
(c) if the command in (a) contains a request for a report on the data that is in either of the
stores in (b), then retrieve the data from the appropriate store
(d) format the data from (c) into the required report format and content
(e) when (d) is complete, output the data to the Travel Information Operator using the trigger
output data flow.
(a) when GTP request data flow is received from the Travel Information Operator, check its
contents
(b) if the command in (a) contains a request for a report on the data that is in the store of
General Trip Preferences (GTP) Data, then request the data from the store using the data flow
request copy of GTP data
(c) when the data flow requested copy of GTP data is received in response to (b) format the
data resulting from (b) into the required report format and content
(d) when (c) is complete, output the data to the Travel Information Operator using the GTP
responses data flow
(e) when the trip evaluation report for output data flow is received, format its contents and
output them to the Travel Information Operator in the performance evaluation report data flow.
(a) continuously monitor for receipt of the trip plan management report request data flow from
the travel information operator
(b) when the data flow in (a) is received, put the request into the trip plan data request data
flow and send it to the Manage Store of Trip Plan Data function
(c) as a result of (b) continuously monitor for receipt of the trip plan data output data flow
(d) when the data flow in (c) is received, produce a report about the requested trip plans,
making sure that the identities of the travellers who created and use the trip plans are not
included
(e) output the result of (d) tot he travel information operator in the trip plan management report
data flow.
(a) when either the first or second trigger input data flows is received, the commands shall be
produced to change the use of the lanes as requested
(b) the commands in (a) shall make the change of lane use in an orderly way such that the
safety of vehicle and travellers is not reduced or compromised
(c) the commands in (a) and (b) shall be sent to the urban output actuation Function using the
first trigger output data flow
(d) implementation of the first trigger input data flow in (b) and (c) shall take priority over the
second trigger input data flow
(e) the new use of the lanes implemented in (c) shall also be sent to the Detect Urban
Violation Function using the second trigger output data flow.
(a) when the second or third trigger input data flows are received, the internal data describing
the permitted vehicle movements within the urban road network shall be updated
(b) the first trigger input data flow shall be continuously monitored and converted into vehicle
presence and speed data
(c) the positions of vehicles produced by (b) shall be compared against that required by (a)
(d) if a vehicle is found in an illegal position by (c), details of the vehicle, the time, date. place
and nature of the violation shall be sent to functionality in the Provide Support for Law
Enforcement Area using the trigger output data flow
(e) when the fourth trigger input data flow is received, the internal data describing the
permitted vehicle speed shall be updated
(f) if the vehicle speed obtained from (b) exceeds that specified in (e), details of the vehicle,
the time, date. place plus allowed and actual speeds shall be sent to functionality in the
Provide Support for Law Enforcement Area using the trigger output data flow.
(a) when either the first or second trigger input data flows is received, the commands shall be
produced to change the use of the lanes as requested
(b) the commands in (a) shall make the change of lane use in an orderly way such that the
safety of vehicle and travellers is not reduced or compromised
(c) the commands in (a) and (b) shall be sent to the inter-urban output actuation Function
using the first trigger output data flow
(d) implementation of the second trigger input data flow in (b) and (c) shall take priority over
the first trigger input data flow
(e) the new use of the lanes implemented in (c) shall also be sent to the Detect Urban
Violation function using the second trigger output data flow.
(f) keep-in-lane advice is triggered by operator or automatically at critical traffic levels
(g) the operator is asked to check and confirm that whole auxiliary lane is non-occupied before
making it available
(h) details of changes in lane use shall be sent to other functionality so that it can be access
by the Broadcaster and sent to other Areas of the System.
(a) when the second or third trigger input data flows are received, the internal data describing
the permitted vehicle movements within the inter-urban road network shall be updated
(b) the first trigger input data flow shall be continuously monitored and converted into vehicle
presence data
(c) the positions of vehicles produced by (b) shall be compared against that required by (a)
(d) if a vehicle is found in an illegal position by (c), details of the vehicle, the time, date. place
and nature of the violation shall be sent to functionality in the Provide Support for Law
Enforcement Area using the trigger output data flow
(e) when the fourth trigger input data flow is received, the internal data describing the
permitted vehicle speed shall be updated
(f) if the vehicle speed obtained from (b) exceeds that specified in (e), details of the vehicle,
the time, date. place plus allowed and actual speeds shall be sent to functionality in the
Provide Support for Law Enforcement Area using the trigger output data flow.
(a) continuously monitor for receipt of guidance data from the road pavement and the road
pavement diagnostics from the maintenance organisation
(b) when the first data flow in (a) is received, it shall be stored locally until the second data
flow in (a) is received
(c) the second data flow in (a) shall be used to establish the integrity of the first data flow in (a)
(d) if the data from the first data flow in (a) passes the integrity test, the data from both shall be
sent to the Communicate with In-vehicle Systems function in the guidance data and road
network diagnostics data flows.
(a) continuously monitor for the receipt of the data flows from vehicle systems, the data flows
from other functionality in the Provide Advanced Driver Assistance Functional Area containing
data that is to be sent to vehicle systems and data flows containing inputs to vehicle systems
from other functionality outside the Provide Advanced Driver Assistance Functional Area
(b) when in (a) the input data flow from the vehicle systems is received, analyse its contents
and send it in the appropriate data flows to other functionality in the system
(c) when in (a) any of the input data flows from other functionality in the system are received,
collate the data and send it to the vehicle systems in the output data flow
(d) when in (a) any of the input data flows from other functionality outside the Provide
Advanced Driver Assistance Functional Area are received, collate the data and send it to the
vehicle systems in the output data flow.
Date de intrare (Input logical dataflows)
mt_inter-urban_road_static_data_for_prediction
mt_urban_road_static_data_for_prediction
fors.tss-traffic_prediction_results
mt_inter-urban_strategies_in_use
mt_processed_road_traffic_data
mt_read_prediction_data
mt_request_road_data_for_predictions
mt_request_road_nework_data
mt_request_traffic_prediction_results
mt_road_network_data_for_predictions
mt_send_traffic_prediction_results_for_output
mt_traffic_prediction_results
mt_updated_road_nework_data
mt_urban_strategies_in_use
fors.utms-urban_traffic_management_strategies
mpto.mt_request_demand_vehicle_priority
mpto.mt_vehicle_priority_request
mt_bridge_urban_inputs
mt_current_urban_traffic_conditions
mt_inter-urban_to_urban_traffic_commands
mt_operator_urban_traffic_management_request
mt_planned_urban_traffic_management_request
mt_predicted_urban_network_data
mt_tunnel_urban_inputs
mt_urban_demand_management_strategy
mt_urban_environmental_inputs
mt_urban_incident_strategy_request
mt_urban_static_data
mt_urban_traffic_flow_management_data
mt_urban_traffic_management_c&i_response
mt_urban_traffic_management_l&s_response
mt_urban_traffic_management_s&g_response
mt_urban_zoning_strategy
pscs.mt_green_wave_request
psef.mt_urban_emergency_route_request
psef.mt_urban_virtual_coned_area_request
fors.iutms-inter-urban_traffic_management_strategy
mt_bridge_inter-urban_inputs
mt_current_inter-urban_traffic_conditions
mt_inter-urban_demand_management_strategy
mt_inter-urban_environmental_inputs
mt_inter-urban_incident_strategy_request
mt_inter-urban_static_data
mt_inter-urban_traffic_flow_management_data
mt_inter-urban_traffic_management_c&i_response
mt_inter-urban_traffic_management_l&s_response
mt_inter-urban_zoning_strategy
mt_operator_inter-urban_management_request
mt_planned_inter-urban_traffic_management_request
mt_predicted_inter-urban_network_data
mt_tunnel_inter-urban_inputs
mt_urban_to_inter-urban_traffic_commands
psef.mt_inter-urban_emergency_route_request
psef.mt_inter-urban_virtual_coned_area_request
fesp.ccp-urban_network_journey_time_data
fors.utms-urban_data_updates
mt_carpark_occupancy_data
mt_carpark_status_for_store
mt_collected_urban_traffic_data
mt_collected_urban_vehicle_data
mt_inter-urban_to_urban_traffic_data_transfers
mt_read_urban_traffic_data
mt_urban_static_data_for_traffic_conditions
mt_urban_traffic_predicted_data
padas.mt_urban_road_use_data_from_trip
pepf.mt_urban_infrastructure_usage_data
ptja.mt_urban_road_use_data_from_trip
fesp.ccp-inter-urban_network_journey_time_data
fors.iutms-inter-urban_data_updates
mt_collected_inter-urban_traffic_data
mt_collected_inter-urban_vehicle_data
mt_inter-urban_static_data_for_traffic_conditions
mt_inter-urban_traffic_prediction_data
mt_read_inter-urban_traffic_data
mt_service_area_occupancy_for_store
mt_service_area_status_for_store
mt_urban_to_inter-urban_traffic_data_transfers
padas.mt_inter-urban_road_use_data_from_trip
pepf.mt_inter-urban_infra_usage_info
ptja.mt_inter-urban_road_use_data_from_trip
mt_operator_traffic_prediction_commands
mt_road_data_for_predictions
fors.tss-traffic_prediction_results
mt_processed_road_traffic_data
mt_read_prediction_data
mt_request_road_data_for_predictions
mt_traffic_prediction_results
ftp-process_traffic_prediction_results
ftp-request_road_network_data
ftp-request_traffic_prediction_results
ftp-run_traffic_prediction_creation
ftp-updates_to_road_network_data
mt_operator_traffic_prediction_responses
mt_requested_road_nework_data
mt_requested_traffic_prediction_results
mt_current_demand_strategy_for_simulation
mt_network_use_data_for_simulation
mt_new_demand_strategy_for_simulation
mt_run_demand_strategy_simulation
mt_create_new_demend_strategy
mt_data_for_demand_strategy_development
mt_demand_management_operator_commands
mt_current_demand_strategy_for_simulation
mt_network_use_data_for_simulation
mt_run_demand_strategy_simulation
mt_create_new_demend_strategy
mt_data_for_demand_strategy_development
mt_demand_management_operator_commands
psle_user_image
psle_violator_data_for_image_analysis
psle_user_data_read
psle_vehicle_ID_DV
mffo.psle_fraud_notification
mt.psle_illegal_carpark_space_occupancy
mt.psle_inter-urban_fraud_vehicle_identity
mt.psle_inter-urban_vehicle_identity_error
mt.psle_urban_fraud_vehicle_identity
mt.psle_urban_vehicle_identity_error
mt.psle_vehicle_entering_inter-urban_zone
mt.psle_vehicle_entering_urban_zone
pepf.psle_fraud_notification_DAV
pepf.psle_fraud_notification_DPV
pscs.psle_bus_lane_violation
psle_fraud_classification
psle_fraud_type_from_compliance_check
psle_fraud_type_from_image_analysis
psle_fraud_type_from_violator_determination
psle_violation_history_for_notification
psle_violation_seriousness
psle_violator_ID
psle_violator_ID_from_violator_determination
psle_check_instructions_results
psle_fraud_characteristics
psle_violation_history_for_prosecution
psle_user_image
psle_user_data_read
psle_vehicle_ID_DV
mffo.psle_fraud_notification
mt.psle_illegal_carpark_space_occupancy
mt.psle_inter-urban_vehicle_identity_error
mt.psle_urban_vehicle_identity_error
mt.psle_vehicle_entering_inter-urban_zone
mt.psle_vehicle_entering_urban_zone
pepf.psle_fraud_notification_DAV
pepf.psle_fraud_notification_DPV
pscs.psle_bus_lane_violation
psle_fraud_classification
psle_fraud_type_from_compliance_check
psle_violation_history_for_notification
psle_violation_seriousness
psle_violator_ID
psle_check_instructions_results
psle_violation_history_for_prosecution
fd-psle_record
fv-psle_characteristics
fv-psle_vehicle_image
mt.psle_inter-urban_enforcement_guidelines_PF
mt.psle_urban_enforcement_guidelines_PF
padas.psle_vehicle_ID
fd-psle_record
fv-psle_characteristics
fv-psle_vehicle_image
mt.psle_inter-urban_enforcement_guidelines_PF
mt.psle_urban_enforcement_guidelines_PF
padas.psle_vehicle_ID
ft-pepf_contract_data
pepf_requested_service_data
ptja.pepf_service_contract_info
pepf_contract_ECS
pepf_service_definition
pepf_transaction_information
pepf_operator_revenue
fesp-pepf_trans_info_request
fo-pepf_trans_info_request
pepf_op_transaction_history
fesp-pepf_tariff_grids
fo-pepf_tariff_grids
mpto.pepf_fare_schemes
mt.pepf_inter-urban_charge_update_request
mt.pepf_urban_charge_update_request
ft-pepf_contract_data
pepf_contract_ECS
fesp-pepf_services_available
fo-pepf_services_available
pepf_current_service_information
ffc-pepf_account_status
ft-pepf_contract_selection
ft-pepf_loading_parameters
ft-pepf_user_ID
pepf_contract_LUA
pepf_account_status_for_debiting
pepf_transaction_information_R2
mt.pepf_inter-urban_free_ride_request
mt.pepf_urban_free_ride_request
pepf_contract_CUC
pepf_user_access_rights_CUC
fd-pepf_contract_selection
fd-pepf_selected_service
ft-pepf_contract_selection_2
ft-pepf_selected_service
pepf_contract_IGU
pepf_payment_status
pepf_user_access_rights_IGU
ptja.pepf_service_data
mt.pepf_inter-urban_traffic_conditions_CSF
mt.pepf_urban_traffic_conditions_CSF
padas.pepf_vehicle_position
pepf_contract_CSF
pepf_selected_service_data_CSF
pepf_service_tariff
fd-pepf_payment
ft-pepf_payment
pepf_access_refused
pepf_contract_RF
pepf_service_fee_CSF
pepf_service_fee_IGU
pepf_service_definition
fes-intervention_answer
psef_common_data_for_emergency_intervention_plans
psef_control_intervention_planning
psef_emergency_description_PEI
psef_emergency_id_for_planning
psef_emergency_id_for_re-planning
ptja.psef_emergency_route_plan
fd.e-deploy_virtual_cones
fd.e-green_wave_request
fd.e-individual_emergency_progress_report
fesp.g-digital_map_data_for_emergency_vehicle
flds-psef_location_data
psef_global_emergency_progress_report
psef_planned_emergency_route
fors.iutms-inter-urban_traffic_management_strategy
mt_bridge_inter-urban_inputs
mt_inter-urban_demand_management_strategy
mt_inter-urban_environmental_inputs
mt_inter-urban_incident_strategy_request
mt_inter-urban_static_data
mt_inter-urban_traffic_flow_management_data
mt_inter-urban_traffic_management_c&i_response
fd.e-deploy_virtual_cones
fd.e-green_wave_request
fd.e-individual_emergency_progress_report
fesp.g-digital_map_data_for_emergency_vehicle
flds-psef_location_data
psef_global_emergency_progress_report
mffo.ptja_hazardous_goods_monitoring_information
mpto.ptja_pt_services_for_trip_monitoring
mt.ptja_de-icing_data_for_trip_monitoring
mt.ptja_forecast_traffic_to_monitor_trip
mt.ptja_incident_information_for_trip_monitoring
mt.ptja_inter-urban_network_perturbations
mt.ptja_roadworks_information_for_trip_monitoring
mt.ptja_urban_network_perturbations
mt.ptja_weather_information_for_trip_monitoring
ptja_traveller_location_for_trip_monitoring
ptja_trip_plan_for_monitoring
ft.ptt-additional_trip_parameters
ft.ptt-basic_trip_parameters
ft.ptt-modified_trip_parameters
ft.ptt-trip_selection
ptja_requested_applicable_GTP_parameters
ptja_traveller_trip_description
ptja_trip_plan_rejected
fesp.g-map_data_for_travel_information
flds-ptja_location_for_information
ft-traveller_information_request
ptja_travel_information_response
fesp.gip-poi_information
fesp.gip-ps_information
fesp.mmtip-requested_travel_information
mt.ptja_inter-urban_recommended_routes
mt.ptja_urban_recommended_routes
padas.ptja_revised_vehicle_trip_plan_requirements
padas.ptja_vehicle_trip_plan_criteria_changes
padas.ptja_vehicle_trip_plan_request
pepf.ptja_service_price
ptja_modified_trip_plan_requirements
ptja_request_trip_planning_criteria
ptja_retrieve_PT_trip_planning_data
ptja_retrieve_road_trip_planning_data
ptja_revised_trip_plan_requirements
ptja_traveller_trip_requirement
ptja_update_trip_planning_criteria
mt_environmental_information
fors.ond-traffic_data
mt.ptja_carpark_occupancy
mt.ptja_incident_information_PRT
mt.ptja_inter-urban_network_conditions
mt.ptja_inter-urban_road_network_data
mt.ptja_pollution
mt.ptja_road_network_traffic_predictions
mt.ptja_service_area_occupancy
mt.ptja_urban_network_conditions
mt.ptja_urban_road_network_data
mt.ptja_walking_and_cycling_info
mt.ptja_weather_information_PRT
ptja_other_mode_data_for_travel_information
ptja_pos/pi_data_for_travel_information
ptja_PT_information
ptja_request_travel_information_filters
ptja_road_information
ptja_toll_data_for_travel_information
ptja_updated_travel_information_filters
ptja_travel_information_for_output
ptja_travel_information_for_output
mffo.ptja_hazardous_goods_monitoring_information
mpto.ptja_pt_services_for_trip_monitoring
mt.ptja_de-icing_data_for_trip_monitoring
mt.ptja_forecast_traffic_to_monitor_trip
mt.ptja_incident_information_for_trip_monitoring
mt.ptja_roadworks_information_for_trip_monitoring
mt.ptja_urban_network_perturbations
mt.ptja_weather_information_for_trip_monitoring
ptja_traveller_location_for_trip_monitoring
ptja_trip_plan_for_monitoring
ptja_PT_information
ptja_request_travel_information_filters
ptja_road_information
ptja_updated_travel_information_filters
ft-GTP_data_updates
ft-requested_implementing_trip_plan_change
ft-request_trip_plan_implementation
ft-trip_plan_change_approval
ptja_trip_guidance_instructions
ptja_trip_plan_changes_for_traveller
fo.rno-create_incident_strategy
fo.rno-implement_incident_strategy
fo.rno-request_incident_data_analysis
fo.rno-request_incident_statistics
mt_confirm_incident_strategy_implementation
mt_incident_command_response
mt_incident_statistics_response
mt_incident_strategies_removed
mt_incident_strategy_created
mt_incident_strategy_implemented
mt.ptja_pollution
padas_current_time_2
padas_ISA_acknowledgement
padas_lane_command_response
padas_legal_speed_acknowledgement
padas_route_information_for_xfcd
padas_status_data_for_fcd
padas_vehicle_ID_for_fcd
padas_vehicle_position_for_fcd
mffo.ptja_freight_and_hazardous_goods_information
mffo.ptja_on_board_informations_and_requests
mffo.ptja_request_on_pollution_situation
mffo.ptja_request_on_traffic_situation
mffo.ptja_request_on_weather_situation
mffo.ptja_route_optimisation_request
pscs.ptja_hazardous_goods_vehicle_route_request
ptja_retrieve_ffm_route_planning_data
ptja_retrieve_road_situation_data
mpto.ptja_available_pt_services
mpto.ptja_current_fares
mpto.ptja_pt_journey_time_prediction
mt.ptja_pollution
fesp.ccp-urban_network_journey_time_data
fors.utms-urban_data_updates
mt_carpark_occupancy_data
mt_carpark_status_for_store
mt_collected_urban_traffic_data
mt_collected_urban_vehicle_data
mt_read_urban_traffic_data
mt_urban_static_data_for_traffic_conditions
mt_urban_traffic_predicted_data
padas.mt_urban_road_use_data_from_trip
pepf.mt_urban_infrastructure_usage_data
fesp.b-inter-urban_traffic_information_request
mt_inter-urban_lane_instructions
mt_inter-urban_speed_limit_changes
mt_inter-urban_traffic_data_for_output
ft.ptt-final_approval
ptja_full_trip_description_no_bookings
ptja_full_trip_description_with_bookings
ft-general_trip_preferences
ft-post_trip_preferences
ft-request_general_trip_preferences
ptja_requested_GTP_data
ptja_request_post_trip_preferences
fo.tio-inter-urban_road_network_data_update
fo.tio-trip_planning_data_requests
fo.tio-urban_road_network_data_update
ptja_read_PT_trip_planning_data
ptja_read_road_trip_planning_data
fo.tio-GTP_requests
ptja_requested_copy_of_GTP_data
ptja_trip_evaluation_report_for_output
fo.tio-trip_plan_management_report_request
ptja_trip_plan_data_output
mt_operator_urban_lane_override
mt_urban_lane_management
trfc-urban_vehicle_identity_for_violations
mt_urban_c&i_device_status
mt_urban_device_s&g_status
mt_urban_l&s_device_status
mt_urban_lane_status
mt_urban_speed_value
mt_inter-urban_lane_management_requests
mt_inter-urban_operator_lane_override
mt_operator_inter-urban_auxlane_check_response
ftrfc-inter-urban_vehicle_identity_for_violations
mt_inter-urban_c&i_device_status
mt_inter-urban_l&s_device_status
mt_inter-urban_lane_status
mt_inter-urban_speed_value
fmo.rmo-infrastructure_diagnostics
frp-guidance_data
fv.vs-input_data
mt.padas_vehicle_s&g_input
padas_driver_impaired
padas_eCall_information
padas_guidance_data
padas_platooning_data_from_other_vehicles
padas_road_network_diagnostics
padas_status_data_from_other_vehicles
padas_stop_stolen_vehicle
padas_suggested_speeds_and_headways_from_ISA
padas_warnings_from_other_vehicles
Date de iesire (Output logical dataflows)
mt_load_prediction_data
mt_road_network_data_for_collection
mt_traffic_prediction_results_for_processing
tors.tss-traffic_prediction_results
mt.pscs_green_wave_result
mt_operator_urban_traffic_management_response
mt_urban_bridge_inputs
mt_urban_response_fault
mt_urban_speed_and_headway_settings
mt_urban_traffic_management_c&i_request
mt_urban_traffic_management_s&g_requests
mt_urban_tunnel_inputs
mt_urban_zone_access_vehicle_list
tmms.mmc-urban_crossing_inhibit
tors.utms-urban_traffic_management_strategies
mt_inter-urban_bridge_inputs
mt_inter-urban_response_fault
mt_inter-urban_speed_and_headway_settings
mt_inter-urban_traffic_management_c&i_request
mt_inter-urban_traffic_management_l&s_request
mt_inter-urban_tunnel_inputs
mt_inter-urban_zone_access_vehicle_list
mt_operator_inter-urban_management_response
tmms.mmc-inter-urban_crossing_inhibit
tors.iutms-inter-urban_traffic_management_strategy
mt_default_urban_journey_time_update
mt_load_urban_traffic_data
mt_urban_data_for_traffic_predictions
mt_urban_road_use_data
mt_urban_traffic_data_for_demand
mt_urban_traffic_data_for_incidents
mt_urban_traffic_data_for_output
mt_urban_traffic_maintenance_conditions
tors.utms-urban_data_updates
mt_default_inter-urban_journey_time_update
mt_inter-urban_data_for_traffic_predictions
mt_inter-urban_road_use_data
mt_inter-urban_traffic_data_for_demand
mt_inter-urban_traffic_data_for_incidents
mt_inter-urban_traffic_data_for_output
mt_inter-urban_traffic_maintenance_conditions
mt_load_inter-urban_traffic_data
tors.iutms-inter-urban_data_updates
mt_load_prediction_data
mt_road_network_data_for_collection
mt_traffic_prediction_results_for_processing
tors.tss-traffic_prediction_results
ttp-requested_road_network_data
ttp-requested_traffic_prediction_results
mt_demand_strategy_simulation_results
mt_request_data_&_strategies_for_simulation
mt_created_new_demand_strategy
mt_demand_management_operator_responses
mt_developed_demand_strategy
mt_demand_strategy_simulation_results
mt_request_data_&_strategies_for_simulation
mt_created_new_demand_strategy
mt_demand_management_operator_responses
mt_developed_demand_strategy
psle_vehicle_ID_CC
psle_vehicle_ID_DV
psle_user_data_request
psle_inter-urban_violator_ID
psle_urban_violator_ID
psle_violation_notification_SF
psle.mffo_fraud_notification
psle_check_insructions_recieved
psle_prosecution_file
tlea-psle_prosecution_file
psle_vehicle_ID_CC
psle_vehicle_ID_DV
psle_user_data_request
psle_inter-urban_violator_ID
psle_urban_violator_ID
psle_violation_notification_SF
psle.mffo_fraud_notification
psle_check_insructions_recieved
psle_prosecution_file
tlea-psle_prosecution_file
psle.padas_vehicle_ID_request
psle_measure
td-psle_record_request
psle.padas_vehicle_ID_request
psle_measure
td-psle_record_request
tt-pepf_contract
tt-pepf_service_information
tesp-pepf_contract_statistics
to-pepf_contract_statistics
pepf_credit_operator_transaction_order_L
tfc-pepf_transaction
tesp-pepf_transaction_analysis
to-pepf_transaction_analysis
pepf_tariff_grids
tt-pepf_contract
tt-pepf_service_information
tesp-pepf_contract_statistics
to-pepf_contract_statistics
pepf_changed_service_information
to-pepf_service_data
pepf-load_account_order_transactions
pepf_load_account_order_for_user
pepf_supplied_account
tfc-pepf_account_status_request
tfc-pepf_load_account_order
tt-pepf_account_loading_problem
tt-pepf_contract_list
pepf_debit_account_order_for_user
pepf_debit_account_order_transactions
pepf_overdraft_notification
tt-pepf_overdraft_notification
pepf_contract_DPV
pepf_contract_IGU
pepf_illegal_action_notification_DAV2
pepf_service_ID_DPV
pepf_user_ID_DPV
pepf_vehicle_data_CUC
pepf_agreement_IGU
pepf_contract_CAP
pepf_contract_CSF
pepf_contract_RF
pepf_illegal_action_notification_DAV
pepf_selected_service_data_CAP
pepf_selected_service_data_CSF
pepf_service_fee_IGU
pepf_service_ID_CUR
pepf_user_ID_for_guidance
pepf_vehicle_data_IGU
td-pepf_payment_info_guidance
tt-pepf_payment_info_guidance
pepf_service_fee_CSF
pepf.mffo_payment_receipt_MOT
pepf.mffo_payment_receipt_MTO
pepf_agreement_RF
pepf_illegal_action_notification_DPV
pepf_transaction_information_L
td-pepf_payment_acceptance
td-pepf_payment_request
tt-pepf_payment_acceptance
tt-pepf_payment_request
pepf_credit_operator_transaction_order_L
tfc-pepf_transaction
psef.ptja_emergency_intervention_route_request
psef_control_intervention_planning_response
psef_emergency_id_for_processing
psef_selected_emergency_plan_description
tes-intervention_request
psef.mt_emergency_local_priority_request
psef.padas_emergency_vehicle_approaching
psef_individual_emergency_progress_report
td.e-emergency_route_guidance
td.e-global_emergency
mt_inter-urban_bridge_inputs
mt_inter-urban_response_fault
mt_inter-urban_speed_and_headway_settings
mt_inter-urban_traffic_management_c&i_request
psef.mt_emergency_local_priority_request
psef.padas_emergency_vehicle_approaching
psef_individual_emergency_progress_report
td.e-emergency_route_guidance
td.e-global_emergency
ptja.mt_trip_plan_o-d_data
ptja_revise_trip_plan_request
ptja_trip_completion_report_for_evaluation
ptja_request_travel_information
tt-requested_travel_information
ptja.padas_revised_vehicle_trip_plan_for_approval
ptja.padas_vehicle_trip_plan_response
ptja_requested_trip_planning_criteria
ptja_revised_trip_plan_for_approval
tesp.gip-request_poi_information
tesp.gip-request_ps_information
tesp.mmtip-request_travel_information
ptja_full_trip_description_for_bookings
ptja_request_applicable_GTP_parameters
tt.ptt-initial_trip_plan
tt.ptt-request_preferences
tt.ptt-select_trip
tt.ptt-trip_alternatives
td-environmental_information
tt-environmental_information
ptja_store_road_trip_planning_data
tors.ond-traffic_data
ptja_requested_travel_information_filters
ptja_updated_travel_information
tt-travel_information
tt-travel_information
ptja.mt_trip_plan_o-d_data
ptja_revise_trip_plan_request
ptja_trip_completion_report_for_evaluation
ptja_full_trip_description_for_bookings
ptja_request_applicable_GTP_parameters
tt.ptt-initial_trip_plan
tt.ptt-request_preferences
tt.ptt-select_trip
tt.ptt-trip_alternatives
ptja_requested_travel_information_filters
ptja_updated_travel_information
ft-GTP_data_updates
ft-requested_implementing_trip_plan_change
ft-request_trip_plan_implementation
ft-trip_plan_change_approval
ptja_trip_guidance_instructions
ptja_trip_plan_changes_for_traveller
mt_implement_requested_strategy
mt_incident_command_request
mt_incident_statistics_request
mt_incident_strategy_implementation_confirmed
mt_operator_incident_data
mt_request_incident_strategy_creation
to.rno-confirm_incident_strategy_implementation
to.rno-incident_strategies_removed
to.rno-incident_strategy_details
to.rno-requested_incident_data_analysis
to.rno-requested_incident_statistics
padas.mt_inter-urban_floating_car_data
padas.mt_inter-urban_xfcd
padas.mt_urban_floating_car_data
padas.mt_urban_xfcd
padas.psle_service_notification
padas_vehicle_speed_for_safety_behaviour
padas_xfcd_for_fusing
padas_xfcd_for_other_vehicle
ptja.mffo_answer_on_pollution_situation
ptja.mffo_answer_on_traffic_situation
ptja.mffo_answer_on_weather_situation
ptja.mffo_route
ptja.pscs_hazardous_goods_vehicle_route_response
ptja_store_ffm_and_hazardous_goods_data
ptja_store_PT_trip_planning_data
mt_default_urban_journey_time_update
mt_load_urban_traffic_data
mt_urban_data_for_traffic_predictions
mt_urban_road_use_data
mt_urban_traffic_data_for_demand
mt_urban_traffic_data_for_incidents
mt_urban_traffic_data_for_output
mt_urban_traffic_maintenance_conditions
tors.utms-urban_data_updates
mt.padas_inter-urban_network_perturbations
mt.padas_inter-urban_queue_information
mt.pepf_inter-urban_traffic_conditions_CSF
mt.pepf_inter-urban_traffic_conditions_CUR
mt.pscs_current_inter-urban_traffic_conditions
tesp.b-inter-urban_traffic_data
tesp.ttip-inter-urban_traffic_data
ptja_cancel_bookings_for_trip
ptja_trip_plan_ready_for_implementation
tt.ptt-itinerary_initial
ptja_GTP_data
ptja_GTP_update
ptja_post_trip_preferences
tt-output_GTP_data
tt-post_trip_preferences_request
ptja_update_PT_trip_planning_data
ptja_update_road_trip_planning_data
to.tio-trip_planning_data_responses
ptja_request_copy_of_GTP_data
to.tio-GTP_responses
to.tio-trip_performance_evaluation_report
ptja_trip_plan_data_request
to.tio-trip_plan_management_report
mt.padas_urban_lane_commands
mt_urban_lane_commands
mt_urban_lane_instructions
mt_urban_lane_status
mt.padas_inter-urban_lane_commands
mt.padas_inter-urban_lane_use_information
mt_inter-urban_lane_instructions
mt_inter-urban_lane_l&s_commands
mt_inter-urban_lane_status
mt_operator_inter-urban_auxlane_check_request
padas_guidance_data
padas_road_network_diagnostics
padas.mffo_vehicle_data
padas.mt_data_for_vehicles_as_incidents
padas.pscs_hazarduous_goods_vehicle_data_for_route
padas.pscs_vehicle_data_for_sensitive_areas
padas_accident_detected
padas_dead_reckoning
padas_goods_being_carried_by_host_vehicle
padas_illegal_use
padas_platooning_data_to_other_vehicles
padas_status_data_for_fcd
padas_status_data_to_other_vehicles
padas_vehicle_data
padas_vehicle_data_for_determining_speed_&_headway
padas_vehicle_data_for_trajectory
padas_vehicle_data_for_trip_planning
padas_vehicle_ID
padas_vehicle_speed
padas_warnings_to_other_vehicles
tv.vs-output_data

1221 - Arhip Gabriel Daniel - Laborator - Vfinal

Uploaded by

Copyright:

Available Formats

You might also like

1221 - Arhip Gabriel Daniel - Laborator - Vfinal

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1221 - Arhip Gabriel Daniel - Laborator - Vfinal

Uploaded by

Copyright:

Available Formats

Definirea USERS NEEDS

Număr grup Denumire activitate

The system shall be able to model the

4.1 Electronic Financial Transactions

4.1.2 Revenue Sharing

5.2.0 Basic Services

The system shall support a green wave for

6.1.2 Information Handling

The system shall be able to provide

The system shall be able to receive

The system shall be able to support a

The system shall provide information

The system shall provide information in

The system shall be able to reserve

Functii asociate (Low level Parent Higher Level

3.1.6.1 Process Road Network 3.1.6 Provide Traffic

7.2.2 Determine Violator ID 7.2 Identify Violator

7.3 Process Fraud

7.2.1 Analyse Image 7.2 Identify Violator

7.3.5 Sort Fraud Notifications 7.3 Process Fraud Notifications

1.1.2 Establish Contract Statistics 1.1 Set up Contract

1.4 Manage Operators'

1.4.3 Inform Operators on 1.4 Manage

1.6 Manage Tariffs

1.1.2 Establish Contract

1.2.2 Debit User's

1.3 Perform Electronic

1.3.5 Compute Service

1.4.2 Credit Operator's

1.4.2 Credit Operator's Account pepf_operator_revenue

2.1.7 Manage use of Emergency 2.1 Manage

3.1.1.5 Provide Urban

3.1.2.5 Provide Inter-

3.1.1.5 Provide Urban

6.5.7 Provide Traveller with Trip 6.5 Prepare Trip

6.6.1 Provide Traveller 6.6 Provide Traveller

6.5.7 Provide Traveller with Trip 6.5 Prepare Trip

6.5.3.9 Plan Trip Details 6.5.3 Trip Planning

6.6 Provide Traveller

6.6 Provide Traveller

6.5.3.9 Plan Trip Details 6.5.3 Trip Planning

6.5.3.9 Plan Trip Details 6.5.3 Trip Planning

6.5.7 Provide Traveller with Trip

6.6.2 Produce Travel 6.6 Provide Traveller

3.2.11 Provide Operator

6.5.3.8 Collect Data About Road

6.5.3.13 Provide Data & Routes

6.5.3.3 Collect PT Data 6.5.3 Trip Planning

6.5.3.9 Plan Trip Details 6.5.3 Trip Planning

3.1.1.7 Urban Traffic Data Management

6.6 Provide Traveller

6.5.8 Enable Final Approval of Trip

6.6 Provide Traveller

6.7 Manage General

6.7 Manage General

3.1.1.5 Provide Urban

3.1.2.5 Provide Inter-