Aspects of IVHS architecture design
Advanced Search
Select up to three search categories and corresponding keywords using the fields to the right. Refer to the Help section for more detailed instructions.

Search our Collections & Repository

For very narrow results

When looking for a specific result

Best used for discovery & interchangable words

Recommended to be used in conjunction with other fields

Dates

to

Document Data
Library
People
Clear All
Clear All

For additional assistance using the Custom Query please check out our Help Page

i

Aspects of IVHS architecture design

Filetype[PDF-208.09 KB]


English

Details:

  • Creators:
  • Subject/TRT Terms:
  • Resource Type:
  • Corporate Publisher:
  • Abstract:
    IVHS systems influence four kinds of decisions that drivers make during their trip. The

    corresponding tasks that IVHS systems carry out are route and flow control, congestion

    control, vehicle coordination, and spacing. A comparison of two scenarios shows how IVHS

    influence over vehicle behavior can range from minor (under a strategy limited to providing

    information and advice) to major (under full automation which preempts driver control).

    The four IVHS tasks have three differentiating features: time scale or the time available to

    carry out the task; spatial scope or the impact of executing the task on the traffic system;

    and information span or the extent of information needed to carry out the task.

    An IVHS architecture organized in a hierarchy of four layers - network, link, coordination.

    and regulation - is proposed. This hierarchy resolves in a natural way the

    three differentiating features. The architecture can accommodate a wide range of automation

    strategies from the simplest, which limits itself to providing driver information. to

    the most complex. which achieves total control of the vehicle. The architecture permits

    the incorporation of new functional capabilities over time, and encourages a decentralized

    implementation of IVHS tasks.

    An open architecture specification is urged as a means to promote rapid development

    of IVHS and to ensure the interworking of independent, subsystem implementations. It is

    also suggested that IVHS standards should be specified in a formal-mathematical language

    to simplify later problems of design validation and conformance testing of products.

  • Format:
  • Collection(s):
  • Main Document Checksum:
  • Download URL:
  • File Type:

Supporting Files

  • No Additional Files
More +

You May Also Like

Checkout today's featured content at rosap.ntl.bts.gov