Traveler Information Voice System --> Transportation Information Center:
voice-based traveler request
Definitions
voice-based traveler request (Information Flow): The electronic traveler information request from the telecommunications systems for traveler information terminator. It may be specifically formatted for voice-based traveler requests. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Traveler Information Voice System (Source Physical Object): The 'Traveler Information Voice System' provides the caller interface and voice processing (voice recognition/synthesis) that supports voice-enabled traveler telephone information systems. It provides wireline and wireless caller access to 511 systems and other telephone access mechanisms like 7 or 10 digit local access numbers. It represents the boundary of the architecture where a call is received and processed and includes voice portal capabilities in scenarios where a distinct voice portal exists between ITS Centers and telecommunications providers. The terminator gathers traveler information, alerts, and advisories from information service provider(s) and uses this information to support voice-based interactions with a traveler.
Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
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:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Transportation Information Center | Traveler Information Voice System | voice-based alert notification |
Request-Response | Transportation Information Center | Traveler Information Voice System | voice-based traveler information |
Communication Solutions
- (None-Data) - Secure 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
Internet Subnet Alternatives |
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 | False |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | Moderate | Low | |
Basis | All of this is information eventually intended for public dissemination. Intercepting all of this information without going through the traditional interface would not provide a significant threat vector. | Since the information in this flow will eventually provide traveler information, and travelers are likely to use this information to make travel decisions, there must be some assurance the information is correct and not tampered with. If modified, it could lead to negatively-affected travel experiences. | Since the information in this flow will eventually provide traveler information, and travelers are likely to use this information to make travel decisions, it must be delivered promptly or travelers are likely to have less effective (overall) mobility. However, there are many avenues for receiving traveler information in most cases, which lowers this to LOW, typically. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |