Transportation Information Center --> Parking Management Center:
loading zone reservation request
Definitions
loading zone reservation request (Information Flow): Request for a loading zone space that identifies the requestor and vehicle, the requested date/time, the vehicle type, the estimated duration, and associated identification and payment information.
Transportation Information Center (Source Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
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:
This triple is associated with the following Functional Objects:
- Parking Coordination
- TIC Freight-Specific Travel Planning
- TIC Travel Services Information and Reservation
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Parking Management Center | Transportation Information Center | loading zone reservation confirmation |
Communication Solutions
- US: CDS - Secure Internet (ITS) (3)
- (None-Data) - Secure Internet (ITS) (32)
Selected Solution
Solution Description
ITS Application Entity
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 | Recent |
Spatial Context | Local |
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 | Reservation-related information is likely to have an identifier that can be associated with a specific vehicle and/or driver, compromise of which could affect the driver's privacy, or the operating company's business. | Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused. | Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |