Parking Management Center --> Traffic Management Center:
parking information
Definitions
parking information (Information Flow): General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots.
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.
Traffic Management Center (Destination Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Included In
This Triple is in the following Service Packages:
- CVO05: Commercial Vehicle Parking
- PM01: Parking Space Management
- PM04: Regional Parking Management
- TM09: Integrated Decision Support and Demand Management
This triple is associated with the following Functional Objects:
- Parking Coordination
- TMC Demand Management Coordination
- TMC Multi-Modal Coordination
- TMC Traffic Information Dissemination
This Triple is described by the following Functional View Data Flows:
- dynamic_parking_information_for_traffic
- parking_information_for_dissemination
- parking_lot_charge_change_response
- parking_lot_charge_direct_details
- parking_lot_current_state
- static_parking_information_for_traffic
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: DATEX - DATEX Messaging (3)
- US: CDS - Secure Internet (ITS) (9)
- Parking - Secure Internet (ITS) (19)
- US: ATIS - Secure Internet (ITS) (24)
- (None-Data) - Secure Internet (ITS) (43)
Selected Solution
Solution Description
ITS Application Entity
OMF CDS |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
IETF RFC 7159 IETF RFC 9110 IETF RFC 9112 |
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 | Now |
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 | Moderate | |
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. | Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |