Cover Image

Not for Sale

View/Hide Left Panel
Click for next page ( 379

The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 378
A.2.7 ITS Communication Network Topology Once We communication loads of an ITS system have been defined, these loads must be geographically placed and an interconnecting communication infrastructure topology must be developed based on Me architecture goals. Topology refers to geographic placement of field equipment, communication nodes and hubs, TOCs, and interconnecting communication links (i.e., mediums) to implement Me required communication infrastructure. The steps in this process include: I. Physical location of data sources and sinks on maps, tables, schematics, etc., so that the data loads are geographically defined. ITS data sources and sinks include controllers, VMS, ramp meters, primary and alternate TOCs, etc. 2. Consideration of repeaterIess distances of alternative communication mediums versus the required interconnect distances of He geographic network. 3. Identification of potential cost-effec~ve multiplexing alternatives and backbone communication network and topology altemadves. It should be noted that some systems (usually smaller systems) may be cost-effectively implemented without multiplexing;and backbone links. 4. Consideration of data load capacities of alternative communication mediums versus local and backbone link load requirements. Overhead for network protocol(s), network management, etc., should be considered. 5. Development of possible interconnecting network topologies that can Interconnect sources, sinks, and backbone nodes~ubs as required. Careful consideration should be given to right of-way and site acquisition requirements and costs. 6. Consideration of redundancy and fault tolerant goals, costs, and impact on the above. 7. Evaluation of cost trade-offs of Me reasonable promising altemadves. u\NCH~pr\ NCHRP3-51 Phase2F'nalReport A2-34 i