Center --> Parking Management Center:
parking maneuver status
Definitions
parking maneuver status (Information Flow): Current status of the vehicle during a parking maneuver, including the vehicle's location in three dimensions, heading, speed, acceleration, and braking status.
Center (Source Physical Object): This general physical object is used to model core capabilities that are common to any center.
Parking Management Center (Destination 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.
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
-
(None-Data) - Secure Internet (ITS) (43)
-
(None-Data) - OMG DDS (44)
-
(None-Data) - Apache Kafka (44)
-
(None-Data) - Eclipse Zenoh (45)
-
(None-Data) - OASIS MQTT (50)
-
(None-Data) - OASIS AMQP (61)
Selected Solution
Solution Description
|
ITS Application Entity
![]()
Development needed ![]() |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
![]() ![]()
|
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 | National |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| Interoperability | Description |
|---|---|
| National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Low | Moderate | Moderate | |
| Basis | Vehicle status will be directly observable. There may be instances where remote monitoring of this status enables a nefarious use case, which suggests a LOW level of obfuscation is reasonable, as the impact is likely limited to a single vehicle with no safety impact. | If this flow is incorrect or unavailable, the vehicle owner/operator may be inconvenienced. It is unlikely there is a serious impact. | If this flow is incorrect or unavailable, the vehicle owner/operator may be inconvenienced. It is unlikely there is a serious impact. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |


