Payment Administration Center --> Transportation Information Center:
toll probe data

Definitions

toll probe data (Information Flow): Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.

Payment Administration Center (Source Physical Object): The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.

Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

Included In

This Triple is in the following Service Packages:

• TM02: Vehicle-Based Traffic Surveillance
• TM10: Electronic Toll Collection

This triple is associated with the following Functional Objects:

• PAC Payment Administration
• TIC Data Collection
• TIC Situation Data Management

This Triple is described by the following Functional View Data Flows:

• toll_probe_data

This Triple has the following triple relationships:

Communication Solutions

• US: TMDD - NTCIP Messaging (10)
• (None-Data) - Secure Internet (ITS) (32)
• Data for Distribution (TBD) - Apache Kafka (36)
• Data for Distribution (TBD) - OMG DDS (36)
• (None-Data) - OASIS MQTT (42)
• Data for Distribution (TBD) - OASIS MQTT (42)
• (None-Data) - OASIS AMQP (45)
• Data for Distribution (TBD) - OASIS AMQP (45)

Selected Solution

Data for Distribution (TBD) - OASIS AMQP

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Development needed	Facilities OASIS AMQP	Security IP Security Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Internet Subnet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Security