Type: Mobility
Groups:- Traveler Information
Traveler Information- Smart Parking
The Traveler Information -Smart Parking application provides users with real-time location, availability, type (e.g., street, garage, AFV only), and the price of parking. The parking information can be provided via DSRC or wide area communications. The application reduces time required for drivers to search for a parking space, which can have eco benefits such as reducing emissions. The application also supports dynamic pricing of parking based on factors such as demand, emissions, or vehicle type.
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
Business Interaction Matrix:
| Traveler Information- Smart Parking Operations Stage | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Vehicle Owner | Driver | Vehicle OBE Owner | Roadway Owner | RSE Owner | RSE Operator | Information Service Provider | Vehicle Basic Safety Provider | Traveler | Vehicle Interactive Traveler Information Provider | Vehicle Roadside Information Reception Provider | Parking Manager | Other Information Service Provider | RSE Parking Management Provider | |
| Vehicle Owner | Vehicle Usage Agreement | Vehicle OBE Usage Agreement | Application Usage Agreement | Application Usage Agreement | Application Usage Agreement | |||||||||
| Driver | Vehicle Usage Agreement | Expectation of Information Provision | Expectation of Information Provision | Expectation of Information Provision | ||||||||||
| Vehicle OBE Owner | Vehicle OBE Usage Agreement | Expectation of Information Provision | Expectation of Data Provision | Expectation of Information Provision | ||||||||||
| Roadway Owner | Service Delivery Agreement | |||||||||||||
| RSE Owner | Expectation of Information Provision | Expectation of Data Provision | Service Delivery Agreement | Operations Agreement | Information Exchange and Action Agreement | Information Exchange Agreement | Application Usage Agreement | |||||||
| RSE Operator | Operations Agreement | |||||||||||||
| Information Service Provider | Expectation of Information Provision | Information Exchange and Action Agreement | Expectation of Information Provision | Information Provision Agreement | Information Exchange Agreement | |||||||||
| Vehicle Basic Safety Provider | Application Usage Agreement | |||||||||||||
| Traveler | Expectation of Information Provision | Expectation of Information Provision | ||||||||||||
| Vehicle Interactive Traveler Information Provider | Application Usage Agreement | |||||||||||||
| Vehicle Roadside Information Reception Provider | Application Usage Agreement | |||||||||||||
| Parking Manager | Information Exchange Agreement | Information Provision Agreement | ||||||||||||
| Other Information Service Provider | Information Exchange Agreement | |||||||||||||
| RSE Parking Management Provider | Application Usage 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. |
| 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. |
| 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. |
| Information Service Provider | The "Information Service Provider" represents the owner of the Transportation Information Center. The Information Service Provider is responsible for collecting and disseminating information relevant to the traveling public. |
| 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.) |
| Other Information Service Provider | Representing another Information Service Provider, "Other Information Service Provider" provides the source and destination for agreements and expectations between Information Service Providers, enabling information management activities to be coordinated across jurisdictional boundaries. |
| Parking Management 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. |
| Parking Management 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. |
| Parking Management 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. |
| Parking Manager | The organization that manages parking facilities, including lots, access control, parking meters. |
| 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. |
| Roadway Owner | The owner of the roadway proximate to which roadside equipment will be/is installed. |
| 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 Parking Management 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 Parking Management 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 Parking Management 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 Provider | The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research. |
| 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. |
| TIC Data 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. |
| TIC Data 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. |
| TIC Data 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. |
| TIC 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. |
| TIC 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. |
| TIC 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. |
| 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 Basic Safety 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 Basic Safety 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 Basic Safety 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. |
| Vehicle 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. |
| Vehicle 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. |
| Vehicle 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. |
| 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 Roadside Information Reception 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 Roadside Information Reception 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 Roadside Information Reception 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. |
| 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. |
| 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. |
| 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 Transportation Information Centers | Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant. |
| Parking Management | "Parking Management" detects and classifies vehicles at parking facility entrances, exits, and other designated locations within the facility. Current parking availability is monitored and used to inform drivers through dynamic message signs/displays so that vehicles are efficiently routed to available spaces. Parking facility information, including current parking rates and directions to entrances and available exits, is also provided to drivers. Coordination with traffic management supports local traffic control coordination in and around the parking facility. |
| Parking Management System | The Parking Management System provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. This portion of the functionality must be located in the parking facility where it can monitor, classify, and share information with customers and their vehicles. It also interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region. Note that the latter functionality may be located in a back office, remote from the parking facility. |
| 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 Signal Control | "Roadway Signal Control" includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions. |
| 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 Parking Management | "RSE Parking Management" monitors the basic safety messages generated by connected vehicles to detect vehicles parking and maintain and report spaces that are occupied by connected vehicles. It also uses short range communications to provide parking information to vehicles. |
| TIC Data Collection | "TIC Data Collection" collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. |
| TIC Interactive Traveler Information | "TIC Interactive Traveler Information" disseminates personalized traveler information including traffic and road conditions, transit information, maintenance and construction information, multimodal information, event information, and weather information. Tailored information is provided based on the traveler's request in this interactive service. |
| Transportation Information Center | 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. |
| 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 Basic Safety | "Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. |
| Vehicle Interactive Traveler Information | "Vehicle Interactive Traveler Information" provides drivers with personalized traveler information including traffic and road conditions, transit information, maintenance and construction information, multimodal information, event information, and weather information. The provided information is tailored based on driver requests. Both one-time requests for information and on-going information streams based on a submitted traveler profile and preferences are supported. |
| 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 Roadside Information Reception | "Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. |
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. |
| 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 Agreement | Agreement | An agreement that grants one party permission to install an application component on a device controlled by the other party. |
| 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 Agreement | Agreement | An agreement in which one entity maintains the operational status of a software 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. |
| 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. |
| Expectation of Data Provision | Expectation | An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
| 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. |
| RSE Procurement Agreement | Agreement | An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process. |
| 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:
Includes Data Flows:
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
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| 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. |
| Other Transportation Information Centers | Center | Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant. |
| Parking Management System | Field | The Parking Management System provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. This portion of the functionality must be located in the parking facility where it can monitor, classify, and share information with customers and their vehicles. It also interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region. Note that the latter functionality may be located in a back office, remote from the parking facility. |
| 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. |
| Transportation Information Center | Center | 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. |
| 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 |
|---|---|---|
| Parking Management | "Parking Management" detects and classifies vehicles at parking facility entrances, exits, and other designated locations within the facility. Current parking availability is monitored and used to inform drivers through dynamic message signs/displays so that vehicles are efficiently routed to available spaces. Parking facility information, including current parking rates and directions to entrances and available exits, is also provided to drivers. Coordination with traffic management supports local traffic control coordination in and around the parking facility. | Parking Management System |
| 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 |
| RSE Parking Management | "RSE Parking Management" monitors the basic safety messages generated by connected vehicles to detect vehicles parking and maintain and report spaces that are occupied by connected vehicles. It also uses short range communications to provide parking information to vehicles. | Roadside Equipment |
| TIC Data Collection | "TIC Data Collection" collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. | Transportation Information Center |
| TIC Interactive Traveler Information | "TIC Interactive Traveler Information" disseminates personalized traveler information including traffic and road conditions, transit information, maintenance and construction information, multimodal information, event information, and weather information. Tailored information is provided based on the traveler's request in this interactive service. | Transportation Information Center |
| Vehicle Basic Safety | "Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. | Vehicle OBE |
| Vehicle Interactive Traveler Information | "Vehicle Interactive Traveler Information" provides drivers with personalized traveler information including traffic and road conditions, transit information, maintenance and construction information, multimodal information, event information, and weather information. The provided information is tailored based on driver requests. Both one-time requests for information and on-going information streams based on a submitted traveler profile and preferences are supported. | Vehicle OBE |
| Vehicle Roadside Information Reception | "Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. | Vehicle OBE |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| connected vehicle parking data | Current, aggregate parking data collected from connected vehicles that can be used to monitor parking space usage and availability. This flow identifies spaces that are occupied by connected vehicles. |
| driver information | Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation. |
| 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. |
| interactive traveler information | Traveler information provided in response to a traveler request. The provided information includes traffic and road conditions, advisories, incidents, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations. |
| parking availability | Information on available parking. This flow identifies available spaces with associated information about parking restrictions and location for each available space. |
| parking information | General parking information and status, including current parking availability. |
| parking management application info | Parking management application information including parking lot configuration and status and associated parameters and thresholds that control the algorithms that monitor parking occupancy and the parking information that is delivered. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. |
| traveler request | A request for traveler information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences. |
| vehicle location and motion for surveillance | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications. |
| vehicle signage data | In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, detours, advisories, and warnings). |
| vehicle signage local data | Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, detours, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data. |
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
Requirements
| Need | Requirement | ||
|---|---|---|---|
| N2.207 | Traveler Information -Smart Parking (TI-SP) needs to collect real-time status of parking spaces. | 2.440 | Traveler Information -Smart Parking (TI-SP) shall collect real-time status of parking spaces. |
| N2.208 | TI-SP needs to determine availability of parking spaces. | 2.441 | TI-SP shall determine availability of parking spaces. |
| N2.209 | TI-SP needs to provide real-time status of parking spaces to travelers. | 2.442 | TI-SP shall provide real-time status of parking spaces to travelers. |
Related Sources
- ConOps for Transit Connected Vehicle, Draft, 3/31/2012
- Smart Roadside Initiative ConOps, Draft, 5/21/2012
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 |
| Basis | Basis | Basis | |||
| Security levels have not been defined yet. | |||||