Transit Management Center --> Transit Vehicle OBE:
transit traveler information
Definitions
transit traveler information (Information Flow): Transit information prepared to support transit users and other travelers. It contains transit schedules, real-time arrival information, fare schedules, alerts and advisories, and general transit service information.
Transit Management Center (Source 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.
Transit Vehicle OBE (Destination Physical Object): The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Included In
This Triple is in the following Service Packages:
- PS10: Wide-Area Alert
- PT08: Transit Traveler Information
- PT16: Route ID for the Visually Impaired
- PT17: Transit Connection Protection
This triple is associated with the following Functional Objects:
- Transit Center Connection Protection
- Transit Center Information Services
- Transit Vehicle On-Board Connection Protection
- Transit Vehicle On-Board Information Services
This Triple is described by the following Functional View Data Flows:
- individual_transit_user_trip_plan
- other_services_vehicle_response
- secure_transit_vehicle_broadcast_message
- transit_traveler_wide_area_alert_info
- transit_vehicle_advisory_eta
- traveler_transit_information
- traveler_transit_information_for_transit_advisories
This Triple has the following triple relationships:
None |
Communication Solutions
- US: GTFS - Secure Wireless Internet (ITS) (10)
- US: TCIP - Secure Wireless Internet (ITS) (16)
- (None-Data) - Secure Wireless Internet (EU) (32)
- Data for Distribution (TBD) - Apache Kafka over Wireless (36)
- Data for Distribution (TBD) - OMG DDS over Wireless (36)
- (None-Data) - OASIS MQTT over Wireless (42)
- Data for Distribution (TBD) - OASIS MQTT over Wireless (42)
- (None-Data) - OASIS AMQP over Wireless (45)
- Data for Distribution (TBD) - OASIS AMQP over Wireless (45)
Selected Solution
Solution Description
ITS Application Entity
GTFS GTFS Realtime |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
IETF RFC 7159 ISO 21320-1 IETF RFC 4180 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 | Local |
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 | Moderate | Moderate | |
Basis | This information is not sensitive. It is generally made public, to support transit system functionality. | Accuracy of this data is important for decision making purposes. Corruption of this data could lead to revenue loss and confusion. | Does not happen often, but when this information is needed its use is imminent. Consequently the flow needs to be reliable for those limited times. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |