Personal Information Device --> Transit Management Center:
transit information user request
Definitions
transit information user request (Information Flow): Request for special transit routing, real-time schedule information, and availability information.
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:
- PT08: Transit Traveler Information
- PT16: Route ID for the Visually Impaired
- PT17: Transit Connection Protection
This triple is associated with the following Functional Objects:
- Personal Interactive Traveler Information
- Personal Trip Planning and Route Guidance
- Transit Center Connection Protection
- Transit Center Information Services
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Request-Response | Transit Management Center | Personal Information Device | personal transit information |
Request-Response | Transit Management Center | Personal Information Device | trip plan |
Communication Solutions
- (None-Data) - Secure Wireless Internet (EU) (32)
- (None-Data) - Secure Wireless Internet (ITS) (32)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
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 | Contains a personalized request by an individual traveler, so should not be readable by anyone except the intended recipient. | If corrupted this would result in failed connection protection. If modified intentionally would cause either failed protection or unnecessary protection. In any case these affect the efficacy and efficiency of the transit system, but the scope of the effects are limited, thus MODERATE and not HIGH. | If unavailable that transit connection protection will not function. Given the scope of the application, this affects only those riders requiring protection, which should be limited scope, thus MODERATE and not HIGH. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |