Transport Canada
www.tc.gc.ca
Home > Transport Canada > Innovation > Intelligent Transportation Systems > Architecture
> ITS Architecture for Canada Version 2.0
> Physical Architecture
> Entities
>Remote Traveller Support
Innovation
Browse Resources
Innovation Contact Information
Browse By Mode
Browse By Subject
About Us
This subsystem provides access to traveller information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centres, hotels, office complexes, amusement parks, and theaters. Traveller information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops, simple displays providing schedule information and imminent arrival signals can be provided. This basic information may be extended to include multi-modal information including traffic and weather conditions and transit schedules along with business directory information to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveller. The subsystem also supports electronic payment of transit fares.
In addition to the traveller information provisions, this subsystem also supports security and safety monitoring of public areas. This monitoring includes traveller activated silent alarms, as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras) and/or audio systems. The sensor equipment includes threat sensors (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors) and object detection sensors (e.g. metal detectors).
Security Considerations
The Remote Traveller Support subsystem security considerations relate to the potential locations of the types of equipment included in this subsystem. Kiosks and other publicly accessible information access points can be target areas for criminal elements trying to rob or harm travellers. As such the RTS should include appropriate physical security measures including the placement in well-lit areas and the use of video and audio surveillance to secure the use of the equipment. Travellers may be using the RTS to request emergency services and measures should be in place to secure the information and ensure the availability and integrity of the system. Travellers may also be using the RTS to make reservations and trip plans that involve the transmission of personal and financial data. Those transactions should also be secured.
Functionality: Equipment Packages and PSpecs
Inputs/Outputs: Architecture Flows and Data Flows
- alarm acknowledge - Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information.
Data Flows:
- secure area sensor control - Information used to configure and control threat sensors (e.g., thermal, acoustic, radiological, chemical), object, motion and intrusion detection sensors. The provided information controls sensor data collection, aggregation, filtering, and other local processing.
Data Flows:
- secure area surveillance control - Information used to configure and control audio and video surveillance systems used for transportation infrastructure security in secure areas. The provided information controls surveillance data collection, aggregation, filtering, and other local processing.
Data Flows:
- broadcast traveller information - General traveller information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveller information.
Data Flows:
- business directory information - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveller.
Data Flows:
- emergency traveller information - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveller services and shelter information, and reentry times and instructions.
Data Flows:
- interactive traveller information - Traveller information provided in response to a traveller request. The provided information includes traffic and road conditions, advisories, incidents, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations.
Data Flows:
- trip plan - A travel itinerary identifying a route and associated traveller information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
Data Flows:
- map updates - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows:
- alarm notification - Notification of activation of an audible or silent alarm by a traveller in a public area or by a transit vehicle operator using an on-board device.
Data Flows:
- secure area sensor data - Data provided by threat sensors (e.g., thermal, acoustic, radiological, chemical), and intrusion, motion, and object detection sensors in secure areas indicating the sensor's operational status, raw and processed sensor data, and alarm indicators when a threat has been detected.
Data Flows:
- secure area surveillance data - Data collected from surveillance systems used to monitor secure areas. Includes video, audio, processed surveillance data, equipment operational status, and alarm indicators when a threat has been detected.
Data Flows:
- business directory request - Request for travel service information including tourist attractions, lodging, restaurants, service stations, and emergency services. The request identifies the type of service, the area of interest, optional reservation request information, parameters that are used to prioritize or filter the returned information, and sorting preferences.
Data Flows:
- emergency traveller information request - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
Data Flows:
- traveller request - A request for traveller information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences.
Data Flows:
- trip confirmation - Acknowledgement by the driver/traveller of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows:
- trip request - Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include a request for transit and parking reservations and ridesharing options associated with the trip.
Data Flows:
- map update request - Request for a map update which could include a new underlying map or map layer updates.
Data Flows:
- transit fare and passenger status - Information provided from the traveller location that supports fare payments, passenger data, and associated record-keeping.
Data Flows:
- transit information user request - Request for special transit routing, real-time schedule information, and availability information.
Data Flows:
- trip confirmation - Acknowledgement by the driver/traveller of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows:
Remote Traveller Support > Traveller
- traveller interface updates - Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveller.
Data Flows:
- request for payment - Request to deduct cost of service from user's payment account.
Data Flows:
- traveller card update - Information updated concerning traveller's personal data including items such as address, trip records, and profile data.
Data Flows:
- secure area characteristics - The range of physical and environmental characteristics (visual, audible, presence, motion, chemical, biological, radiological, other) that are monitored by surveillance and sensor systems.
Data Flows:
- transit fare information - Information provided by transit management that supports fare payment transactions and passenger data collection.
Data Flows:
- transit traveller information - Transit information prepared to support transit users and other travellers. It contains transit schedules, real-time arrival information, fare schedules, alerts and advisories, and general transit service information.
Data Flows:
- trip plan - A travel itinerary identifying a route and associated traveller information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
Data Flows:
Traveller > Remote Traveller Support
- traveller inputs - User input from a traveller to summon assistance, request travel information, make a reservation, or request any other traveller service.
Data Flows:
- payment - Payment of some kind (e.g., toll, parking, fare) by traveller which, in most cases, can be related to a credit account.
Data Flows:
- traveller card information - The traveller personal information such as name, address, license number, and trip records and profile data.
Data Flows: