Transportation Information Center --> Light Vehicle OBE:
border crossing status information

Definitions

border crossing status information (Information Flow): Port of entry status including current wait-times, lane configuration and status including closures and restrictions, and notification of incidents at the border

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 associated with the following Functional Objects:

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

This Triple has the following triple relationships:

Communication Solutions

  • No communications solutions identified.
  • Characteristics

    CharacteristicValue
    Time Context Recent
    Spatial Context Regional
    Acknowledgement False
    CardinalityUnicast
    InitiatorDestination
    AuthenticableTrue
    EncryptFalse


    InteroperabilityDescription
    RegionalInteroperability 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 This is all public information which is mostly available through public information channels. Some minimal guarantee of data integrity is necessary for all C-ITS flows. A flaw in this information will not cause much, if any harm. A higher integrity will allow this information to be of more use, but is not required for security reasons. DISC: Original V2I analysis classified this as LOW. Without this information there will not be any direct problem. A higher availability will allow this information to be more useful; however it is not a requirement.


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt False