Transport Canada
www.tc.gc.ca
Home > Transport Canada > Innovation > Intelligent Transportation Systems > Architecture
> ITS Architecture for Canada Version 2.0
> Physical Architecture
> Entities
>Personal Information Access
Innovation
Browse Resources
Innovation Contact Information
Browse By Mode
Browse By Subject
About Us
This subsystem provides the capability for travellers to receive formatted traffic advisories from their homes, place of work, major trip generation sites, personal portable devices, over multiple types of electronic media. These capabilities also provide basic routing information and allow users to select those transportation modes that allow them to avoid congestion, or more advanced capabilities to allow users to specify those transportation parameters that are unique to their individual needs and receive travel and weather information. This subsystem provides travellers with the capability to receive route planning from the infrastructure at fixed locations such as in their homes, their place of work, and at mobile locations using personal portable devices and vehicle-based devices. In addition to end user devices, this subsystem may also represent a device that is used by a merchant or other service provider to receive traveller information and relay important information to their customers. This subsystem also provides the capability to initiate a distress signal and cancel a prior-issued manual request for help.
Security Considerations
Security considerations for Personal Information Access include the measures necessary to safeguard the personal and financial information that may be entered by individual users. Personal Information Access subsystem equipment is typically privately owned and operated, and includes the use of portable or handheld devices. Devices such as these are prone to theft and misuse. Information coming from these personal devices should be authenticated to verify that the requester is who they say they are and that the information they are given is limited to the information requested or to information that is available to the public. In general, the Personal Information Access Subsystem handles personal and financial information that needs a relatively low degree of confidentiality to safeguard the information. In addition, it is important but not essential that the information is available. The integrity of the information is also important in order to prevent improper financial transactions and accessibility to unauthorized information.
Functionality: Equipment Packages and PSpecs
Inputs/Outputs: Architecture Flows and Data Flows
- emergency acknowledge - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
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:
- traveller alerts - Traveller information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveller. Relevant alerts are provided based on traveller-supplied profile information including trip characteristics and preferences.
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:
- position fix - Information which provides a traveller's or vehicle's geographical position.
Data Flows:
- map updates - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows:
- driver registration - Driver registration for border clearance.
Data Flows:
- traveller registration - Application for traveller programs such as NEXUS, Includes electronic filing of forms and associated payment.
Data Flows:
- emergency notification - An emergency request for assistance automatically initiated by a vehicle or originated by a traveller using an in-vehicle or personal device.
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 profile - Information about a traveller including equipment capabilities, personal preferences, and traveller alert subscriptions.
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 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:
Personal Information Access > Traveller
- traveller interface updates - Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveller.
Data Flows:
Personal Information Access > Traveller Card
- 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:
- personal transit information - General and personalized transit information for a particular fixed route, flexible route, or paratransit system.
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 > Personal Information Access
- traveller inputs - User input from a traveller to summon assistance, request travel information, make a reservation, or request any other traveller service.
Data Flows:
Traveller Card > Personal Information Access
- 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: