Personal Information Device --> Transit Management Center:
trip confirmation
Definitions
trip confirmation (Information Flow): Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations. Conversely, this flow may also reject the proposed trip plan. Confirmations include the selected route and subsequent trip confirmation messages will be issued for route changes.
Personal Information Device (Source Physical Object): The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Transit Management Center (Destination Physical Object): The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
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
-
US: TOMP - Secure Wireless Internet (ITS) (6)
-
(None-Data) - Secure Wireless Internet (EU) (43)
Selected Solution
US: TOMP - Secure Wireless Internet (ITS)Solution Description
|
ITS Application Entity
TOMP-API  |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
IETF RFC 7159 IETF RFC 9110 IETF RFC 9112 |
Security
|
|
|
TransNet
|
|||
|
Access
 
|
|||
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 | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| 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 | Moderate | Moderate | Moderate | |
| Basis | This is predictive of traveler location and intent. A third party with hostile intent toward the traveler could use this information against the traveler. | If this data is corrupted, the transit management center may not understand the traveler's intent and not properly serve the traveler. | This acknowledgement is part of the real-time feedback for on-demand travel services. If this doesn't work, the on-demand service doesn't work. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |