Transportation Information Center --> Light Vehicle OBE:
travel services information

Definitions

travel services information (Information Flow): Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveler.

Transportation Information Center (Source 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.

Light Vehicle OBE (Destination Physical Object): The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.

Included In

This Triple is in the following Service Packages:

This Triple is described by the following Functional View Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

US: ATIS - Secure Wireless Internet (ITS)

Solution Description

This solution is used within the U.S.. It combines standards associated with US: ATIS with those for I-M: Secure Wireless Internet (ITS). The US: ATIS standards include upper-layer standards required to implement traveler information communications. The I-M: Secure Wireless Internet (ITS) standards include lower-layer standards that support secure communications between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 or IEEE 1609.2 certificates. A non-mobile (if any) endpoint may connect to the service provider using any Internet connection method.

ITS Application Entity
Mind the gapMind the gapMind the gap

SAE J2353
Click gap icons for more info.

Mgmt
Facilities
Mind the gapMind the gap

SAE J2354
IETF RFC 9110
Presentation Format Alternatives
IETF RFC 9112
Security
Mind the gapMind the gap
TransNet
Access
Mind the gapMind the gapMind the gap
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Destination
Authenticable True
Encrypt False


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 Low Moderate Low
Basis This information is intended for a registry and distribution to interested parties. Obfuscating it will delay and help control the release of the information, but it is difficult to see what advantage might be gained by sniffing this data. Since this data will be used to direct business toward particular travel providers, it must be correct or the provider might be harmed by misrepresentation of its offerings. This could have a substantial financial impact. This information probably does not not need to be updated very often.


Security Characteristics Value
Authenticable True
Encrypt False