Map Update System --> Parking Area Equipment:
parking facility geometry
This triple is bi-directional. See also
Parking Area Equipment --> Map Update System: parking facility geometry
Definitions
parking facility geometry (Information Flow): Precise spatial description of a parking facility that locates each parking space and the ingress and egress routes that are used to travel to and from the spaces.
Map Update System (Source Physical Object): The 'Map Update System' represents a provider of map databases used to support ITS services. It supports the provision of the map data that are used directly by vehicles (e.g., roadway and intersection geometry data sets), travelers (e.g., navigable maps used for route guidance and display maps used at traveler information points), system operators (e.g., map data used by Traffic Operators to monitor and manage the road network, and map data used by Fleet Managers to manage a vehicle fleet). It may represent a third-party provider or an internal organization that produces map data for agency use. In the latter case, the 'Map Update System' is typically included as part of the center (e.g., a Traffic Management Center) of the infrastructure owner/operator that manages map data. Products may include simple display maps, map data sets that define detailed road network topology and geometry, or full geographic information system databases that are used to support planning and operations.
Parking Area Equipment (Destination 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.
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:
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (32)
- (None-Data) - Apache Kafka (36)
- (None-Data) - OMG DDS (36)
- (None-Data) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
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 | False |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | High | Moderate | |
Basis | Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. | Map data is used for a host of parking-related application processes. This widespread use means that any corruption in the data has a widespread and far reaching effect. | Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |