Skip to main content

Currently Skimming:

Appendix E Tactical Information Networks
Pages 429-461

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 429...
... It points out ways in which commercial networking technology could be used within the Navy's tactical networks and those areas in which commercial technology will probably need to be augmented with military-specific technology. The committee does not pretend to design the Navy's tactical information networks.
From page 430...
... E.1.1 Varying Types of Tactical Traffic Earlier sections of this report describe current and planned tactical information network use in some detail. This section briefly recapitulates and then proceeds to translate these traffic considerations into more general architectural demands on the tactical network.
From page 431...
... E.1.2 Conclusions Drawn from the Traffic Requirements This section draws some conclusions based on the tactical traffic mix discussed above. These conclusions help guide the critique here of the Navy's current plans for tactical networks; the committee makes its recommendations in Chapter 4.
From page 432...
... can change the traffic load unpredictably. Distribution of the common tactical picture also seems, initially, to be reasonably predictable.
From page 433...
... E.1.2.3 Future Types of Tactical Traffic The final conclusion that can be drawn is this: There is currently no "strong family resemblance" among the different traffic types in the network, and hence future traffic added to the network will probably look rather different from the traffic types that are well understood today. This should translate to a relatively heavy emphasis on designing a network that is flexible, open ended, and very easy to modify.
From page 434...
... This section briefly reviews the most important of these current or planned tactical data links, with an eye to those technical details that make the data links more or less suited to smooth integration into an overall tactical network architecture. It is interesting to note that the Navy's "canonical view" of the emerging architecture for network-centric warfare is not much more than a relabeling of two of its deployed systems and that a number of other tactically significant naval systems now being planned or envisioned simply do not fit into this canonical view.
From page 435...
... Radio Systems 435 Intended Uses Type Raw Speed Open? JTIDS Force control messages, Time division Up to 115 kbps No common tactical picture, multiple access and so on CEC Data Internal distribution of Special reliable Classified No Distribution CEC tracks and flood System coordination provides a thumbnail sketch of the data-carrying characteristics of these two radio systems.
From page 436...
... Time slots within frames are organized into three distinct sets, labeled A, B
From page 437...
... In other words, it is a group of terminals whose time slots have been defined so that when one member of a net is transmitting, every other member of the net is receiving. Obviously this requires careful planning to ensure that indeed all the other members are receiving at that time, that only a single radio is granted a "transmit" time slot at a given time, and so forth.
From page 438...
... (This assumes that all available spectrum is devoted to JTIDS, that all terminals use the maximum possible data rate, and that all time slots in all channels are used for transmission and ignores the overhead of housekeeping
From page 439...
... program that will develop multiple qualified sources for a lightweight, low-cost, CDL3All information on CDL and TCDL has been derived from two briefings presented to the committee s Tactical Networks and Resources Panels on April 20, 1999: Schuh, CDR Paul, ``cHsDL: common High Bandwidth Data Link,,, Office of the Chief of Naval Operations (N641) , Washington, D.C.; and Preziotti, Gerry, ``common High Bandwidth Data Link Surface Terminal (cHsDL-sT)
From page 440...
... have both determined that their tactical networks will employ Internet technologies, which does provide a clear path toward interworking with the Army and the Marine Corps. The Marine Corps is experimenting heavily as it moves toward using tactical networks.
From page 441...
... The U.S. Army's tactical networks can be divided into a few basic categories: far-forward, highly mobile networks (the Tactical Internet)
From page 442...
... The networks should gracefully adapt to the offered traffic load as it changes from minute to minute, switching automatically from handling heavy imagery flows across its RF links at one moment to handling radar tracks and location information the next. E.3.4 Network Security Tactical networks must be secure against intruders, disruption, and eavesdropping.
From page 443...
... The Navy cannot afford to design and build all its own network technology; and even if it could, the military technology would be obsolete long before it was deployed. E.4 DEFICIENCIES IN THE NAVY'S TACTICAL NETWORKING PLANS The communications links that the Navy plans to acquire do not add up to a coherent network architecture.
From page 444...
... · These systems employ little or no commercial networking technology. As such, they fail to leverage what is possibly the fastest-developing technology of the current era.
From page 445...
... In fact, current commercial networking technology actually introduces new planning problems. Conventional data networks typically involve a good deal of planning (of addresses, names, and so on)
From page 446...
... Such plans would include the following: · A unified addressing and naming plan for nodes in the network; · An overall list of the types of tactical traffic that flow across the nattlespace, the sources and destinations of this traffic, and their required service characteristics; . A routing plan for the network; · Designs for how the tactical network fits into the larger picture of each other Service's tactical network, the Joint Planning Network, and so forth; and .
From page 447...
... · The Navy should explicitly determine the best blend of commercial and military networking technology for its tactical networks, with detailed justifications for why military technology is required for any given part of the design. The committee believes that the commercial Internet Protocol should be the basis for this design.
From page 448...
... None of these features is likely to be implemented to any significant degree in commercial radios, and so it is likely that the lower layers (radios) in the Navy's tactical network will be predominantly military.
From page 449...
... The Navy would not need to develop special training materials to teach its staff how to configure, manage, or troubleshoot its tactical networks. E.5.1.3.2 Weaknesses of the Internet Architecture The Internet architecture does have weaknesses, however, ones that are highlighted in the tactical networking environment.
From page 450...
... radio links, including commercial cellular phone systems and tactical radios. Although some engineering can help to lessen these problems, the wisest course might be to add sufficient forward error correction to higher bandwidth links to make packet loss fairly rare, and to forgo using TCP across low-bandwidth tactical links.
From page 451...
... Table E.5 summarizes the committee's views about opening the Navy's three major tactical data radios. TABLE E.5 Opening the Navy's Major Tactical Data Radio Systems Joint Tactical Common Data Link, Data Information Tactical Common Distribution Distribution System Data Link, etc.
From page 452...
... Some new tactical networking technology is desirable, though, and will require an R&D effort as it will most likely not be developed in the commercial sphere. E.5.3.1 Better Channel Access for,ITIDS The JTIDS waveform defines several channel access mechanisms.
From page 453...
... This obviates the commercial need for such ad hoc networking technology. DARPA and other military agencies, on the other hand, have been funding research into ad hoc networks for some years, and the first or second generation of workable ad hoc networks is now up and running.
From page 454...
... 454 NE7V~ORK-CENTRIC NAVAL FORCES TABLE E.A.1 Imagery/SIGINT Platform Characteristics (Direct) Platform Sensor Data Link Link Data Rate Mode Surface T U-2 SAR CDL 274 Mbps LOS ISIPS-N/l EO/IR CDL 274 Mbps LOS ISIPS-N/l Other CDL 274 Mbps LOS BGPHES SAR ETP 274 Mbps Sat CONUS Global Hawk SAR, EO/IR, MTI CDL 274 Mbps LOS MCE/JSII (HAE UAV)
From page 455...
... Sat Legacy Legacy OBP Data link upgrade planned (TCDL) LOS Legacy Legacy N/A Pioneer, a legacy system, to be phased out when VTUAV becomes operational LOS USMC G/S Legacy N/A Analog 512 kbps data link (control link)
From page 456...
... are useful sources of unclassified data regarding aircraft and related sensor data. DEFINITIONS: AWACS, Aircraft Warning and Control System BGPHES, Battle Group Passive Horizon Extension System CDL, common data link-Navy; formerly called common high bandwidth data link CDL-Navy-ST, common data link-Navy surface terminal; ~29 terminals funded CGSM, Common Ground Station Module, receives JSTARS data CIP, common imagery processor CTT, commander's tactical terminal ETP, Extended Tether program HAE UAV, high-altitude endurance unmanned aerial vehicle (UAV)
From page 457...
... activities NIS, National input segment OBP, on-board processor SHARP, Shared Reconnaissance Pod; previously Super Hornet Airborne Reconnaissance Pod TARPS, Tactical Airborne Reconnaissance Pod System TCDL, tactical common data link TCS, Tactical Control System; tactical UAV ground station; may merge into both JSIPS-N and TEG in future TEG, Tactical Exploitation Group; USMC ground station; 3 funded TGIF, Tactical Ground Intercept Facility TIGDL, tactical interoperable ground data link TIS, tactical input segment; part of JSIPS-N; TIS = CDL-Navy-ST and CIP and screener workstation and support equipment TUAV, tactical UAV VTOL, vertical takeoff and landing SOURCE: Compiled from data courtesy of National Imagery and Mapping Agency, Bethesda, Md., 1999.
From page 458...
... . DE, dissemination element; receive capability hardware and software within the DDS DISN, Defense Information Systems Network: DISA networked communications infrastructure; includes DATMS, SIPRNET, Intelink, JWICS, and other systems DSCS, Defense Satellite Communications System; one of the long-haul components that make up DISN; may also be used by DDS and Trojan Spirit II on a location-by-location, scenario, and deployment-dependent basis GBS, Global Broadcast System
From page 459...
... NIMA will send all imagery to USN JCA in Suitland, Maryland; JCA will then disseminate it to individual ships and user sites. MTACS, Maritime Tactical Communications System; Service-maintained, networked communication infrastructure supporting the USMC and interfaces with the USN; provides a user connection to the DISN and a communications link between command component afloat and ground component ashore POM, program objective memorandum POS, point of service; connection between local networks and DISN, could be SATCOM ground terminals like T-MET, Tri-band, or STEP, or fiber-optic land line STEP, standard tactical entry point; provides tactical communications entry into the DISN via the DSCS; to be upgraded to teleport concept, which also will include expanded capacities, protocol interfaces, and commercial connectivity TS II, Trojan Spirit II; U.S.
From page 460...
... 460 NETV~ORK-CENTRlC NAVAL FORCES Annex 2 ,IPN, ,IDN, and ,ICTN Network Components This annex provides a schematic diagram (Figure E.A.1) of the networks composing the Joint Planning Network, the Joint Data Network, and the Joint Composite Tracking Network.
From page 461...
... oz z~o ~z voy~ v ~: zO o~ <:y ~ ~ - o ~ - ~ oz ~ z ~ cn ~ ° ' ~ I <: _ Z Y Z~O ~,2— ~F _Z o C17 vv o ~IL IL I C17 m I 11]


This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.