Link Type: Human Interface
Parking Area Equipment --> Driver:
payment transaction status
Definitions
payment transaction status (Information Flow): The status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure.
Parking Area Equipment (Source Physical Object): 'Parking Area Equipment' 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. The two primary approaches to monitoring parking area usage are sensing vehicles within parking spots or counting vehicles as they come in and as they leave the area. This portion of the functionality must be located in the parking area where it can monitor, classify, and share information with customers and their vehicles. See also the separate 'Parking Management Center' physical object that may be located in a back office, remote from the parking area, which interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region.
Driver (Destination Physical Object): 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.
Included In
This Triple is in the following Service Packages:
This Triple is in the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
| None |
Communication Solutions
No communications solutions identified.Characteristics
| None defined |
| Interoperability | Description |
|---|---|
| Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Low | Moderate | Moderate | |
| Basis | Expected to be visually broadcast information between roadway equipment and a driver that includes no PII. If compromised, contains no information that could not be otherwise learned or impacts the driver. | Payment response should be accurate and available so the driver knows what the result of his transaction was. Inaccurate data may lead to his performing other compensatory actions which are inconvenient to that individual driver and may impact those behind him. | Payment response should be accurate and available so the driver knows what the result of his transaction was. Inaccurate data may lead to his performing other compensatory actions which are inconvenient to that individual driver and may impact those behind him. | |
| None defined |