Type: Mobility

Groups:

Electronic Payment

Diagrams are based on the most recently available application concepts that the CVRIA team has access to, and do not necessarily reflect prototypes or other in-development activities.

Electronic Toll Collection

The Electronic Toll Collection application provides toll operators with the ability to collect tolls electronically and detect and process violations. The fees that are collected may be adjusted to implement demand management strategies. Field-Vehicle Communication between the roadway equipment and the vehicle is required as well as Fixed Point-Fixed Point interfaces between the toll collection equipment and transportation authorities and the financial infrastructure that supports fee collection. Toll violations are identified and electronically posted to vehicle owners. Standards, inter-agency coordination, and financial clearinghouse capabilities enable regional, and ultimately national interoperability for these services.

Enterprise
Functional
Physical
A-Interconnect
Communications
Requirements
Sources
Security

Enterprise

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

The enterprise diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification

Display Legend in SVG or PNG

Business Interaction Matrix:

Electronic Toll Collection Operations Stage
	Vehicle Owner	Driver	Vehicle OBE Owner	Roadway Owner	RSE Owner	RSE Operator	ITS Roadway Equipment Owner	ITS Roadway Operator	Traveler	Payment Institution	Financial Manager	DMV Owner	Enforcement	Other Payment Institution	RSE Toll Collection Provider	Vehicle Toll/Parking Payment Provider	Payment Administrator
Vehicle Owner		Vehicle Usage Agreement	Vehicle OBE Usage Agreement						Information Exchange and Action Agreement							Application Usage Agreement
Driver	Vehicle Usage Agreement		Expectation of Information Provision
Vehicle OBE Owner	Vehicle OBE Usage Agreement	Expectation of Information Provision			Expectation of Information Provision
Roadway Owner					Service Delivery Agreement
RSE Owner			Expectation of Information Provision	Service Delivery Agreement		Operations Agreement		Information Exchange and Action Agreement							Application Usage Agreement
RSE Operator					Operations Agreement
ITS Roadway Equipment Owner								Operations Agreement		Information Exchange and Action Agreement
ITS Roadway Operator					Information Exchange and Action Agreement		Operations Agreement			Information Exchange and Action Agreement
Traveler	Information Exchange and Action Agreement									Information Exchange and Action Agreement
Payment Institution							Information Exchange and Action Agreement	Information Exchange and Action Agreement	Information Exchange and Action Agreement		Information Exchange Agreement	Information Exchange Agreement	Information Provision Agreement	Information Exchange Agreement			Employment Agreement
Financial Manager										Information Exchange Agreement
DMV Owner										Information Exchange Agreement
Enforcement										Information Provision Agreement
Other Payment Institution										Information Exchange Agreement
RSE Toll Collection Provider					Application Usage Agreement
Vehicle Toll/Parking Payment Provider	Application Usage Agreement
Payment Administrator										Employment Agreement

Includes Enterprise Objects:

Enterprise Object	Description
Application Certification Entity	The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications.
Device Certification Entity	The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type.
DMV Owner	The DMV Owner is the agency charged with registering vehicles.
Driver	The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Enforcement	Agencies that are responsible for identifying and reporting violations of roadway regulations, including emissions, traffic violations, toll violations, etc.
Federal Regulatory	Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation.
Financial Manager	The organization that accepts and processes payment requests and other funds transfers through the Financial Center.
ITS Certification Entity	The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.)
ITS Roadway Equipment Owner	The entity that owns the Roadway ITS equipment.
ITS Roadway Operator	The entity that operates the Roadway ITS equipment.
ITS Roadway Payment Equipment Operator	Personnel that operate ITS roadway payment field infrastructure. This includes everything from operators accepting payment in toll booths to those controlling ITS roadway payment equipment remotely.
Other Payment Institution	Representing another Payment Institution, "Other Payment Institution" provides the source and destination for agreements and expectations between Payment Institutions, enabling payment administration activities to be coordinated across jurisdictional boundaries.
PAC Payment Administration Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
PAC Payment Administration Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
PAC Payment Administration Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Payment Administrator	The 'Payment Administrator' represents the person(s) that manage the back office payment administration systems for electronic toll, VMT road use payment, and other services paid for from a vehicle. It monitors the systems that support the electronic transfer of funds from the customer to the system operator. It monitors customer enrollment and supports the establishment of escrow accounts depending on the clearinghouse scheme and the type of payments involved. It also establishes and administers the pricing structures and policies.
Payment Device Manufacturer	The entity responsible for the design, manufacture and distribution of the Payment Device.
Payment Institution	The 'Payment Administrator' represents the person(s) that manage the back office payment administration systems for electronic toll, VMT road use payment, and other services paid for from a vehicle. It monitors the systems that support the electronic transfer of funds from the customer to the system operator. It monitors customer enrollment and supports the establishment of escrow accounts depending on the clearinghouse scheme and the type of payments involved. It also establishes and administers the pricing structures and policies.
Personal Interactive Traveler Information Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Personal Interactive Traveler Information Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Personal Interactive Traveler Information Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
PID Provider	The entity that designs, manufacturers and provides (either to the end user or to a reseller) the personal information device, including its hardware and base operating software.
Roadway Owner	The owner of the roadway proximate to which roadside equipment will be/is installed.
Roadway Toll Collection Support Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Toll Collection Support Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Toll Collection Support Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Deployer	The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Operator	The entity that operates roadside equipment in the transportation environment.
RSE Owner	The owner of roadside equipment.
RSE Provider	The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research.
RSE Toll Collection Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Toll Collection Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Toll Collection Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
State Regulatory	State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies.
Traffic Manager	The entity responsible for the management of traffic, both freeway and arterial.
Traveler	The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
Vehicle Manufacturer	The entity that builds, assembles, verifies and validates the Vehicle in which the Vehicle OBE will eventually operate.
Vehicle OBE Manufacturer	The entity that builds, assembles, verifies and validates the Vehicle OBE. This can be an OEM-equipped OBE, retrofit or aftermarket equipment.
Vehicle OBE Owner	The entity, individual, group or corporation that owns the Vehicle On-Board equipment. This could be the same as the Vehicle Owner, but it could be a third part that licenses the use of the OBE to the Owner.
Vehicle Owner	The individual, group of individuals or corporate entity that is identified as the registered owner of the Vehicle under state law.
Vehicle Toll/Parking Payment Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Toll/Parking Payment Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Toll/Parking Payment Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.

Includes Resources:

Resource	Description
Application Component Certification Requirements	The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE.
Backoffice Service Development System	The systems used to develop backoffice (center) hardware and software components of applications.
Backoffice Service Installation System	The systems used to install and configure backoffice (center) hardware and software components.
Backoffice Service Maintenance System	The systems used to maintain and upgrade backoffice (center) hardware and software components.
Device Certification Requirements	The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment.
DMV	The 'DMV' is a specific (state) public organization responsible for registering vehicles, e.g., the Department of Motor Vehicles.
Enforcement Center	The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
Field Component Development System	The system used in a backoffice environment to develop and test the field component of the application.
Field Component Installation System	The system used to install a field component of a connected vehicle application.
Field Component Maintenance System	The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Financial Center	The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are subsumed by this entity.
ITS Certification Requirements	The requirements that define the functionality, performance and operational environment of an ITS device or ITS application. Applicability varies with jurisdictions, but typically devices and applications must meet pre-defined acceptance criteria prior to usage in the transportation environment.
ITS Field Component Development System	The system used in a backoffice environment to develop and test the ITS field component of the application.
ITS Field Component Installation System	The system used to install a field component of a connected vehicle application.
ITS Field Component Maintenance System	The system used to install and configure changes and updates to the ITS field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Roadway Payment Equipment	'ITS Roadway Payment Equipment' represents the roadway components of a toll collection system. It provides the capability for vehicle operators to pay tolls without stopping their vehicles. It supports use of locally determined pricing structures and includes the capability to implement various variable pricing policies. Typically, transactions are accompanied by feedback to the customer and a record of the transactions is provided to a back office system (e.g., the Payment Administration Center).
Mobile Component Development System	The system used in a backoffice environment to develop and test the mobile component of the application.
Mobile Component Installation System	The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application.
Mobile Component Maintenance System	The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Other Payment Administration	Representing another Payment Administration Center, 'Other Payment Administration' is intended to provide a source and destination for ITS information flows between payment administration functions. This interface allows reconciliation of toll charges and other payments across different agencies by allowing the exchange of information about clients who have incurred charges in jurisdictions other than their own (billing) customer service center. This interface enables apportioning charges and 'reciprocity' between participating customer service centers.
PAC Payment Administration	"PAC Payment Administration" enables payment for road use based on VMT, vehicle type, vehicle emissions, or other parameters. It establishes a price schedule based on these parameters that may vary by time, location or zone, vehicle type, and/or vehicle behavior. Pricing strategies may also include incentives that allow reimbursement of fees previously paid for good behavior (e.g., VMT reductions, economical driving behavior, avoidance of peak periods or congested zones). It receives vehicle data (e.g., time stamped roadways used by the vehicle since the last transmission) and computes the total cost to the vehicle owner for payment. Based on owner preference, this cost is either billed to the owner or requested from an in-vehicle payment instrument. Payment for use of roadways not operated by the specific instance of the VMT Payment Administration that the vehicle is registered with, will be reconciled. Payment violations can be reported to Enforcement Agencies when appropriate. Finally, vehicle owners can interact with this object using personal devices or public terminals to setup and edit account preferences for owned vehicles, get account reports, and make payments.
Payment Administration Center	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.
Payment Device	The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
Personal Information Device	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment.
Personal Interactive Traveler Information	"Personal Interactive Traveler Information" provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones.
PID Component Development System	The system used in a backoffice environment to develop and test the PID component of the application.
PID Component Installation System	The system used to install the PID component of a connected vehicle application.
PID Component Maintenance System	The system used to configure changes and updates to the PID component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Roadside Equipment	'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Roadway Toll Collection Support	"Roadway Toll Collection Support" provides toll plazas the capability to identify properly equipped vehicles, collect electronic tolls, and provide a positive indication to the driver that a toll was collected. Violators are identified and images are collected. Toll transactions are stored and reported to the Payment Administration Center. For CVRIA, this object represents the equipment that supports electronic payment transactions that are actually performed by the RSE (see "RSE Toll Collection") using V2I communications.
RSE Development System	The system used in a backoffice environment to develop and test the roadside equipment.
RSE Installation System	The system used to install and configure the roadside equipment.
RSE Maintenance System	The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance.
RSE Toll Collection	"RSE Toll Collection" collects electronic tolls using V2I communications in toll plazas and other designated toll collection locations. The RSE is connected with other field equipment that detects vehicles, identifies violators, and provides other toll plaza functionality.
Vehicle	The conveyance that provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel. These functions reside in general vehicles including personal automobiles, commercial vehicles, emergency vehicles, transit vehicles, or other vehicle types.
Vehicle OBE	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.
Vehicle Toll/Parking Payment	"Vehicle Toll/Parking Payment" includes the on-board systems that pay for tolls and parking electronically. It includes in-vehicle equipment that communicates with the toll/parking plaza and an optional interface to a carry-in payment device. See also "Vehicle Payment Services", which provides a broader range of payment services.

Includes Roles:

Role	Description
Certifies	An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements.
Constrains	A Resource or Enterprise applies requirements, constraints and associated tests to another Resource.
Develops	An Enterprise creates the target Resource or Document.
Installs	An Enterprise performs the initial delivery, integration and configuration of the target Resource.
Maintains	An Enterprise administers the hardware and software that comprise the target Resource.
Member	An Enterprise is part of another larger, target Enterprise.
Operates	An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible.
Owns	An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable.

Includes Coordination:

Coordination	Type	Description
Application Installation Data	Information Sharing	Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow.
Application Interface Specification	Agreement	The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Application Maintenance Data	Information Sharing	Data used to facilitate the upgrade, patching and general health maintenance of an application component.
Application Performance Data	Information Sharing	Data used to characterize application performance, including such measures as availability, known errors and known uses.
Application Procurement Agreement	Agreement	An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process.
Application Usage Agreement	Agreement	An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Backoffice Component Installation Agreement	Agreement	An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party.
Backoffice Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Device Placement and Operations Agreement	Agreement	An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity.
Employment Agreement	Agreement	An agreement between an individual and a corporation or government entity, whereupon the individual agrees to provide labor to the corporation/agency, which in turn compensates the employee. Stipulates level of compensation, working conditions, necessary equipment and training and expectations of employee performance.
Expectation of Information Provision	Expectation	An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Field Component Installation Agreement	Agreement	An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party.
Field Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the field component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Includes	Includes	Indicates that one component is entirely contained within another component.
Information Exchange Agreement	Agreement	An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Information Exchange and Action Agreement	Agreement	An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Information Provision Agreement	Agreement	An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Installation Agreement	Agreement	An agreement whereupon one entity installs an application component on a device controlled by another entity.
Interface Description	Agreement	Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator.
Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Maintenance Data Exchange Agreement	Agreement	An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Mobile Component Installation Agreement	Agreement	An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application.
Mobile Component License Agreement	Agreement	An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question.
Mobile Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Operations Agreement	Agreement	An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
RSE Deployment Agreement	Agreement	Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions.
RSE Installation Data	Information Sharing	Data necessary to configure and make RSE operational. Uni-directional.
RSE Maintenance Data	Information Sharing	Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional.
RSE Performance Data	Information Sharing	Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures.
Service Delivery Agreement	Agreement	A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications.
Vehicle Data Access Agreement	Agreement	An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data.
Vehicle OBE Usage Agreement	Agreement	An agreement that grants one entity permission to use a Vehicle OBE that the other party controls.
Vehicle Procurement Agreement	Agreement	The exchange of a vehicle for compensation. One entity purchases the vehicle from the other.
Vehicle Usage Agreement	Agreement	An agreement between the owner of a vehicle and a prospective operator, whereupon the owner allows the operator to use the vehicle.
Warranty	Agreement	A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component.

Functional

Includes Processes:

Level	Name	Type	Allocated to Application Object
5.4	Provide Law Enforcement Allocation	Collection
5.4.2	Process Violations for Tolls	Pspec	- PAC Payment Administration
6.7	Provide Driver Personal Services	Collection
6.7.1	Provide On-line Vehicle Guidance	Collection
6.7.1.2	Provide Driver Guidance Interface	Pspec
6.7.3	Provide Traveler Services in Vehicle	Collection
6.7.3.3	Provide Driver Information Interface	Pspec
7.1	Provide Electronic Toll Payment	Collection
7.1.1	Process Electronic Toll Payment	Collection
7.1.1.1	Read Vehicle Payment Data for Tolls	Pspec
7.1.1.2	Calculate Vehicle Toll	Pspec
7.1.1.3	Manage Bad Toll Payment Data	Pspec	- PAC Payment Administration
7.1.1.5	Bill Driver for Tolls	Pspec
7.1.1.7	Update Toll Price Data	Pspec	- PAC Payment Administration
7.1.1.8	Register for Advanced Toll Payment	Pspec	- PAC Payment Administration
7.1.1.9	Manage Toll Processing	Pspec	- PAC Payment Administration
7.1.1.10	Determine Advanced Toll Bill	Pspec
7.1.1.11	Manage Toll Archive Data	Pspec	- PAC Payment Administration
7.1.2	Produce Roadside Displays	Pspec	- Roadway Toll Collection Support
7.1.3	Obtain Toll Violator Image	Pspec
7.1.4	Provide Driver Toll Payment Interface	Pspec
7.1.7	Provide Payment Device Interface for Tolls	Pspec	- Vehicle Toll/Parking Payment
7.1.8	Exchange Data with Other Payment Administration	Pspec	- PAC Payment Administration
7.2	Provide Electronic Parking Payment	Collection
7.2.7	Provide Payment Device Interface for Parking	Pspec
7.4	Carry-out Centralized Payments Processing	Collection
7.4.1	Collect Advanced Payments	Collection
7.4.1.8	Process Electric Charging Payments	Pspec	- PAC Payment Administration
7.4.1.9	Process Roadside Electric Charging Payments	Pspec
7.4.1.10	Process Vehicle Electric Charging Payments	Pspec
7.5.1	Provide Vehicle Payment Device Interface	Pspec
7.5.3	Provide Personal Payment Device Interface	Pspec	- Personal Interactive Traveler Information
7.6.1	Process VMT Payment	Collection
7.6.1.1	Collect Road Use Charging Data	Pspec
7.6.1.3	Bill Driver for Road Use Charges	Pspec	- RSE Toll Collection
7.6.1.4	Manage Road Use Charging Price Data	Pspec	- PAC Payment Administration
7.6.1.5	Manage Road Use Charges Processing	Pspec	- PAC Payment Administration
7.6.2	Support Road Use Charging	Pspec
7.6.3	Provide Driver Road Use Charging Payment Interface	Pspec
7.6.4	Provide Payment Device Interface for Road Use Charging	Pspec
7.6.5	Exchange Road Use Charging Data with Other Payment Administration	Pspec	- PAC Payment Administration
7.6.6	Provide VMT User Interface	Collection
7.6.6.1	Provide Road Use Charging Services User Interface	Pspec	- PAC Payment Administration
7.6.6.3	Provide Road Use Charging Services Personal Interface	Pspec	- Personal Interactive Traveler Information
7.6.7	Collect Road Use Charging Equipment Status	Pspec
7.6.8	Provide Road Use Charging Enforcement Interface	Pspec	- PAC Payment Administration
7	Provide Electronic Payment Services	Collection
7.7	Administer Multimodal Payments	Pspec	- PAC Payment Administration

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
Administer Multimodal Payments	multimodal_payment_request_to_field	Bill Driver for Road Use Charges
Administer Multimodal Payments	multimodal_toll_payment_data	Manage Toll Processing
Administer Multimodal Payments	traveler_personal_multimodal_payment_request	Provide Personal Payment Device Interface
Administer Multimodal Payments	traveler_personal_multimodal_account_reports	Provide Personal Payment Device Interface
Bill Driver for Road Use Charges	multimodal_payment_confirmation_from_field	Administer Multimodal Payments
Bill Driver for Road Use Charges	current_toll_transactions_from_roadside	Bill Driver for Tolls
Bill Driver for Road Use Charges	road_use_payment_collected_from_field	Manage Road Use Charges Processing
Bill Driver for Road Use Charges	road_use_payment_confirmation_from_field	Manage Road Use Charges Processing
Bill Driver for Road Use Charges	road_use_cost_data_from_roadside	Provide Driver Road Use Charging Payment Interface
Bill Driver for Road Use Charges	road_use_payment_request	Provide Payment Device Interface for Road Use Charging
Bill Driver for Road Use Charges	road_use_vehicle_payment_data_clear	Provide Payment Device Interface for Road Use Charging
Bill Driver for Road Use Charges	toll_vehicle_payment_data_request	Provide Payment Device Interface for Tolls
Bill Driver for Road Use Charges	toll_payment_debited	Provide Payment Device Interface for Tolls
Bill Driver for Road Use Charges	toll_payment_request	Provide Payment Device Interface for Tolls
Bill Driver for Road Use Charges	toll_vehicle_payment_data_clear	Provide Payment Device Interface for Tolls
Bill Driver for Road Use Charges	toll_vehicle_payment_data_update	Provide Payment Device Interface for Tolls
Bill Driver for Road Use Charges	toll_payments_from_roadside	Read Vehicle Payment Data for Tolls
Bill Driver for Tolls	toll_roadside_payment_billing	Bill Driver for Road Use Charges
Bill Driver for Tolls	toll_bad_payment_check_request	Manage Bad Toll Payment Data
Bill Driver for Tolls	toll_payment_violator_data	Manage Bad Toll Payment Data
Bill Driver for Tolls	current_toll_transactions	Manage Toll Processing
Bill Driver for Tolls	get_toll_payment_violator_image	Obtain Toll Violator Image
Bill Driver for Tolls	toll_payment_pull_in_message	Produce Roadside Displays
Bill Driver for Tolls	confirm_advanced_tolls_payment	Register for Advanced Toll Payment
Calculate Vehicle Toll	toll_price_data_for_roadside	Bill Driver for Road Use Charges
Collect Road Use Charging Data	road_use_payment_vehicle_detection_status_for_field	Collect Road Use Charging Equipment Status
Collect Road Use Charging Data	road_use_payment_vehicle_detection_for_field	Support Road Use Charging
Collect Road Use Charging Equipment Status	vmt_vehicle_image_for_enforcement	Provide Road Use Charging Enforcement Interface
Collect Road Use Charging Equipment Status	vmt_equipment_fault	Provide Road Use Charging Enforcement Interface
Exchange Data with Other Payment Administration	other_toll_data_input	Manage Toll Processing
Exchange Road Use Charging Data with Other Payment Administration	vmt_coordination_data_from_other_admin_sys	Manage Road Use Charges Processing
Manage Bad Toll Payment Data	toll_bad_payment_check_response	Bill Driver for Tolls
Manage Road Use Charges Processing	road_use_payment_request_to_field	Bill Driver for Road Use Charges
Manage Road Use Charges Processing	road_use_vehicle_payment_data_clear_to_field	Bill Driver for Road Use Charges
Manage Road Use Charges Processing	vmt_coordination_data_to_other_admin_sys	Exchange Road Use Charging Data with Other Payment Administration
Manage Road Use Charges Processing	road_use_payment_request_from_admin	Provide Payment Device Interface for Road Use Charging
Manage Road Use Charges Processing	road_use_vehicle_payment_data_clear_from_admin	Provide Payment Device Interface for Road Use Charging
Manage Road Use Charges Processing	road_use_payment_violation_information	Provide Road Use Charging Enforcement Interface
Manage Road Use Charges Processing	vmt_account_reports_to_travelers	Provide Road Use Charging Services User Interface
Manage Road Use Charges Processing	vmt_payment_request_to_travelers	Provide Road Use Charging Services User Interface
Manage Road Use Charges Processing	road_use_payment_field_configuration_data	Support Road Use Charging
Manage Toll Processing	toll_multimodal_payment_data	Administer Multimodal Payments
Manage Toll Processing	other_toll_data_output	Exchange Data with Other Payment Administration
Manage Toll Processing	toll_operational_data	Manage Toll Archive Data
Obtain Toll Violator Image	toll_violation_information	Process Violations for Tolls
Process Electric Charging Payments	electric_charging_roadside_payment_request	Process Roadside Electric Charging Payments
Process Roadside Electric Charging Payments	electric_charging_payment_collected_from_field	Process Electric Charging Payments
Process Roadside Electric Charging Payments	electric_charging_payment_confirmation_from_field	Process Electric Charging Payments
Process Roadside Electric Charging Payments	electric_charging_payment_request	Process Vehicle Electric Charging Payments
Process Vehicle Electric Charging Payments	electric_charging_payment_collected	Process Roadside Electric Charging Payments
Process Vehicle Electric Charging Payments	electric_charging_payment_confirmation	Process Roadside Electric Charging Payments
Provide Driver Guidance Interface	driver_advanced_payment_for_map	Provide Vehicle Payment Device Interface
Provide Driver Toll Payment Interface	driver_advanced_payment_at_toll	Provide Payment Device Interface for Tolls
Provide Payment Device Interface for Road Use Charging	road_use_payment_collected	Bill Driver for Road Use Charges
Provide Payment Device Interface for Road Use Charging	road_use_payment_confirmation	Bill Driver for Road Use Charges
Provide Payment Device Interface for Road Use Charging	road_use_payment_collected_for_admin	Manage Road Use Charges Processing
Provide Payment Device Interface for Road Use Charging	road_use_payment_confirmation_for_admin	Manage Road Use Charges Processing
Provide Payment Device Interface for Road Use Charging	driver_vmt_payment_confirmation	Provide Driver Road Use Charging Payment Interface
Provide Payment Device Interface for Tolls	toll_payment_confirmation	Bill Driver for Road Use Charges
Provide Payment Device Interface for Tolls	toll_vehicle_payment_data_collect	Bill Driver for Road Use Charges
Provide Payment Device Interface for Tolls	driver_toll_payment_credit_identity	Provide Driver Toll Payment Interface
Provide Personal Payment Device Interface	traveler_personal_multimodal_payment_info	Administer Multimodal Payments
Provide Personal Payment Device Interface	traveler_personal_multimodal_payment_account_setup_info	Administer Multimodal Payments
Provide Road Use Charging Services Personal Interface	traveler_personal_road_use_payment_info	Provide Road Use Charging Services User Interface
Provide Road Use Charging Services Personal Interface	traveler_personal_road_use_payment_account_setup_info	Provide Road Use Charging Services User Interface
Provide Road Use Charging Services User Interface	vmt_payment_info_from_travelers	Manage Road Use Charges Processing
Provide Road Use Charging Services User Interface	vmt_account_setup_info_from_travelers	Manage Road Use Charges Processing
Provide Road Use Charging Services User Interface	traveler_personal_road_use_payment_account_reports	Provide Road Use Charging Services Personal Interface
Provide Road Use Charging Services User Interface	traveler_personal_road_use_payment_request	Provide Road Use Charging Services Personal Interface
Provide Vehicle Payment Device Interface	vehicle_personal_multimodal_payment_info	Administer Multimodal Payments
Provide Vehicle Payment Device Interface	driver_credit_identity	Provide Driver Guidance Interface
Read Vehicle Payment Data for Tolls	toll_collection_roadside_data	Bill Driver for Road Use Charges
Read Vehicle Payment Data for Tolls	vehicle_type_for_tolls	Calculate Vehicle Toll
Read Vehicle Payment Data for Tolls	vehicle_payment_data_for_tolls	Calculate Vehicle Toll
Read Vehicle Payment Data for Tolls	get_toll_vehicle_payment_violator_image	Obtain Toll Violator Image
Read Vehicle Payment Data for Tolls	toll_vehicle_payment_problem_message	Produce Roadside Displays
Register for Advanced Toll Payment	advanced_toll_needed	Determine Advanced Toll Bill
Support Road Use Charging	road_use_data_for_roadside	Bill Driver for Road Use Charges
Support Road Use Charging	vehicle_detection_for_road_use_payment	Collect Road Use Charging Data
Support Road Use Charging	vmt_vehicle_image	Collect Road Use Charging Equipment Status
Support Road Use Charging	road_use_payment_images	Manage Road Use Charges Processing
Update Toll Price Data	toll_price_data_for_vehicle_toll	Calculate Vehicle Toll
Update Toll Price Data	toll_price_data_for_advanced_toll	Determine Advanced Toll Bill
Update Toll Price Data	toll_prices_for_archive	Manage Toll Archive Data

Physical

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram

Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object	Class	Description
DMV	Center	The 'DMV' is a specific (state) public organization responsible for registering vehicles, e.g., the Department of Motor Vehicles.
Driver	Vehicle	The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Enforcement Center	Center	The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
Financial Center	Center	The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are subsumed by this entity.
ITS Roadway Payment Equipment	Field	'ITS Roadway Payment Equipment' represents the roadway components of a toll collection system. It provides the capability for vehicle operators to pay tolls without stopping their vehicles. It supports use of locally determined pricing structures and includes the capability to implement various variable pricing policies. Typically, transactions are accompanied by feedback to the customer and a record of the transactions is provided to a back office system (e.g., the Payment Administration Center).
Other Payment Administration	Center	Representing another Payment Administration Center, 'Other Payment Administration' is intended to provide a source and destination for ITS information flows between payment administration functions. This interface allows reconciliation of toll charges and other payments across different agencies by allowing the exchange of information about clients who have incurred charges in jurisdictions other than their own (billing) customer service center. This interface enables apportioning charges and 'reciprocity' between participating customer service centers.
Payment Administration Center	Center	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.
Payment Administrator	Center	The 'Payment Administrator' represents the person(s) that manage the back office payment administration systems for electronic toll, VMT road use payment, and other services paid for from a vehicle. It monitors the systems that support the electronic transfer of funds from the customer to the system operator. It monitors customer enrollment and supports the establishment of escrow accounts depending on the clearinghouse scheme and the type of payments involved. It also establishes and administers the pricing structures and policies.
Payment Device	Traveler	The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
Personal Information Device	Traveler	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment.
Roadside Equipment	Field	'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Vehicle OBE	Vehicle	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Includes Application Objects:

Application Object	Description	Physical Object
PAC Payment Administration	"PAC Payment Administration" enables payment for road use based on VMT, vehicle type, vehicle emissions, or other parameters. It establishes a price schedule based on these parameters that may vary by time, location or zone, vehicle type, and/or vehicle behavior. Pricing strategies may also include incentives that allow reimbursement of fees previously paid for good behavior (e.g., VMT reductions, economical driving behavior, avoidance of peak periods or congested zones). It receives vehicle data (e.g., time stamped roadways used by the vehicle since the last transmission) and computes the total cost to the vehicle owner for payment. Based on owner preference, this cost is either billed to the owner or requested from an in-vehicle payment instrument. Payment for use of roadways not operated by the specific instance of the VMT Payment Administration that the vehicle is registered with, will be reconciled. Payment violations can be reported to Enforcement Agencies when appropriate. Finally, vehicle owners can interact with this object using personal devices or public terminals to setup and edit account preferences for owned vehicles, get account reports, and make payments.	Payment Administration Center
Personal Interactive Traveler Information	"Personal Interactive Traveler Information" provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones.	Personal Information Device
Roadway Toll Collection Support	"Roadway Toll Collection Support" provides toll plazas the capability to identify properly equipped vehicles, collect electronic tolls, and provide a positive indication to the driver that a toll was collected. Violators are identified and images are collected. Toll transactions are stored and reported to the Payment Administration Center. For CVRIA, this object represents the equipment that supports electronic payment transactions that are actually performed by the RSE (see "RSE Toll Collection") using V2I communications.	ITS Roadway Payment Equipment
RSE Toll Collection	"RSE Toll Collection" collects electronic tolls using V2I communications in toll plazas and other designated toll collection locations. The RSE is connected with other field equipment that detects vehicles, identifies violators, and provides other toll plaza functionality.	Roadside Equipment
Vehicle Toll/Parking Payment	"Vehicle Toll/Parking Payment" includes the on-board systems that pay for tolls and parking electronically. It includes in-vehicle equipment that communicates with the toll/parking plaza and an optional interface to a carry-in payment device. See also "Vehicle Payment Services", which provides a broader range of payment services.	Vehicle OBE

Includes Information Flows:

Information Flow	Description
driver input	Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver updates	Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
license request	Request supporting registration data based on license plate read during violation.
payment	Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
payment administration requests	Personnel inputs that control system operations, including requests to change toll fees, confirmation that alerts should be provided to toll operators, management of VMT charge policies and management of VMT account processing, etc.
payment coordination	Coordinate apportionment charges between jurisdictions (e.g. federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies
payment device information	The traveler personal information such as name, address, license number, user account information, trip records and profile data.
payment device update	Information updated concerning traveler's personal data including name, address, user account information, trip records, and profile data.
payment information presentation	Presentation of information to personnel including revenues, reports, operational status information, and alert information.
payment instructions	Information provided to configure and support fixed point payment operations including pricing information.
payment request	Request for payment from financial institution.
payment transaction status	The status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure.
payment transactions	Detailed list of transactions including violations.
payment violation notification	Notification to enforcement agency of a toll, parking, or transit fare payment violation.
registration	Registered owner of vehicle and associated vehicle information.
request for payment	Request to deduct cost of service from user's payment account.
transaction status	Response to transaction request. Normally dealing with a request for payment.
user account reports	Reports on charges
user account setup	Billing information, vehicle information (or registration information), and requests for reports.
vehicle entries and exits	Information exchanged between an RSE and ITS Roadway Equipment that supports detection of non-equipped vehicles in an automated lane, low emissions zone, or other facility where V2I communications is used to monitor vehicles at entry or exit points. This exchange also supports identification of non-equipped vehicles where an RSE is used for payment collection. This generic exchange can be implemented by any approach that compares vehicle detections with V2I communications by the RSE to identify vehicles that are not equipped or are otherwise unable to communicate with the RSE.
vehicle payment information	Information provided for payment of tolls or parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives.
vehicle payment request	Request for information supporting payments. For fee structures that include incentives, the request may support either an account debit or an account credit or reimbursement.
vehicle payment update	Data written to vehicle equipment to support electronic toll collection or parking payment.

Application Interconnect Diagram

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

The application interconnect diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram

Application Triples

Communications Diagram(s)	Source	Destination	Information Flow
	DMV	Payment Administration Center	registration
None: Human interface	Driver	Vehicle OBE	driver input
	Financial Center	Payment Administration Center	transaction status
	ITS Roadway Payment Equipment	Roadside Equipment	payment instructions
None: Human interface	ITS Roadway Payment Equipment	Driver	payment transaction status
	ITS Roadway Payment Equipment	Payment Administration Center	payment transactions
	ITS Roadway Payment Equipment	Roadside Equipment	vehicle entries and exits
	Other Payment Administration	Payment Administration Center	payment coordination
	Payment Administration Center	DMV	license request
	Payment Administration Center	Other Payment Administration	payment coordination
None: Human interface	Payment Administration Center	Payment Administrator	payment information presentation
	Payment Administration Center	ITS Roadway Payment Equipment	payment instructions
	Payment Administration Center	Financial Center	payment request
	Payment Administration Center	Enforcement Center	payment violation notification
	Payment Administration Center	Personal Information Device	user account reports
None: Human interface	Payment Administrator	Payment Administration Center	payment administration requests
	Payment Device	Vehicle OBE	payment
	Payment Device	Vehicle OBE	payment device information
	Personal Information Device	Payment Administration Center	user account setup
	Roadside Equipment	ITS Roadway Payment Equipment	payment transactions
	Roadside Equipment	ITS Roadway Payment Equipment	vehicle entries and exits
	Roadside Equipment	Vehicle OBE	vehicle payment request
	Roadside Equipment	Vehicle OBE	vehicle payment update
None: Human interface	Vehicle OBE	Driver	driver updates
	Vehicle OBE	Payment Device	payment device update
	Vehicle OBE	Payment Device	request for payment
	Vehicle OBE	Roadside Equipment	vehicle payment information

Requirements

Need		Requirement
N2.213	Electronic Toll Collection needs to allow toll payment without the vehicle stopping at a toll plaza.	2.445	Electronic Toll Collection shall allow a connected vehicle to pay an electronic toll based on a payment request from the roadside equipment.
N2.214	Electronic Toll Collection needs to allow users to set up and maintain a user account.	2.446	Electronic Toll Collection shall allow a user to set up an account for the electronic toll payment.
N2.214		2.447	Electronic Toll Collection shall allow a user to update their account for electronic toll payment.
N2.215	Electronic Toll Collection needs to be able to detect, process, and notify users of toll violations.	2.448	Electronic Toll Collection shall detect if users have not properly paid their toll.
N2.215		2.449	Electronic Toll Collection shall notify user of the toll violation.
N2.216	Electronic Toll Collection needs to support interagency coordination and financial clearinghouse operations	2.450	Electronic Toll Collection shall support coordination of services and payments between peer toll agencies.
N2.216		2.451	Electronic Toll Collection shall support a regional toll clearinghouse capability.

Related Sources

National ITS Architecture Services

Security

In order to participate in this application, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Security levels have not been defined yet.

In order to participate in this application, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source	Destination	Information Flow	Confidentiality	Integrity	Availability
Source	Destination	Information Flow	Basis	Basis	Basis
Security levels have not been defined yet.