Vehicle Operations and Service 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.
Vehicle Operations and Service Center (Source Physical Object): 'Vehicle Operations and Service Center' (VOSC) represents centers that provide telematics services to vehicles using wide-area (e.g. cellular) communications, including traveler information, emergency services, vehicle diagnostics, over-the-air software updates, vehicle maintenance information and warnings, remote vehicle operation, and provision of service options for these vehicles. See also 'Transportation Information Center' that provides traveler information, trip planning, and routing services and 'Emergency Management Center' that provides call-taking and emergency response services that may also be implemented by a VOSC.
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.
This Triple is an instantiation of the more general triple:
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
| None |
This Triple is an instantiation of the more general triple:
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
(None-Data) - Eclipse ZenohSolution Description
|
ITS Application Entity
 
Development needed  |
Click gap icons for more info.
|
||
|
Mgmt
Eclipse Zenoh |
Facilities
 
Development needed 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.
This Triple is an instantiation of the more general triple:
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). |
This Triple is an instantiation of the more general triple:
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 |