Parking Management Center --> Center:
parking area information
Definitions
parking area information (Information Flow): Current status for the parking area. This includes information on general parking area status (operating hours, open entrances and exits, entrance queue status, parking operator information, current parking occupancy and availability).
Parking Management Center (Source Physical Object): The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.
Center (Destination Physical Object): This general physical object is used to model core capabilities that are common to any center.
Included In
This Triple is in the following Service Packages:
- None
This triple is associated with the following Functional Objects:
- None
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
| None |
Communication Solutions
-
Parking - Secure Internet (ITS) (19)
-
(None-Data) - Secure Internet (ITS) (43)
-
Data for Distribution (TBD) - OMG DDS (44)
-
Data for Distribution (TBD) - Apache Kafka (44)
-
Data for Distribution (TBD) - Eclipse Zenoh (45)
-
Data for Distribution (TBD) - OASIS MQTT (50)
-
(None-Data) - OASIS MQTT (50)
-
Data for Distribution (TBD) - OASIS AMQP (61)
-
(None-Data) - OASIS AMQP (61)
Selected Solution
Solution Description
|
ITS Application Entity
 
Development needed  |
Click gap icons for more info.
|
||
|
Mgmt
Eclipse Zenoh |
Facilities
 
Eclipse Zenoh |
Security
|
|
|
TransNet
|
|||
|
Access
Internet Subnet Alternatives |
|||
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Regional |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | Moderate | Low | |
| Basis | Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |