ly, and every terminal performs identical algorithms to ensure that the pooled time slots are apportioned according to the needs. The committee believes that this access scheme has not yet been implemented in practice, but—as will be seen below—it is one of PMW 159’s projects.
B.1.3 JTIDS Data Rates
Each JTIDS time slot has the following components: The time slot begins with a variable-start jitter delay; then, synchronization and time-refinement pat- terns; the payload (message header and data); and, finally, dead time to allow for RF propagation. This discussion will concentrate on the message data portion of a time slot. Each data portion can contain 3, 6, or 12 75-bit words, depending on the exact encoding of the message. Thus, each time slot can carry anywhere from 225 to 900 bits of data payload, giving an aggregate data rate for a given JTIDS net of between 28,800 and 115,200 bps. Some of this raw capacity is used for housekeeping and so is not available for tactical traffic, but these num- bers give an idea of the approximate capacity of a JTIDS net.
By comparison, current commercial phone-line modems run at roughly 53,000 bits per second in the downstream direction. Thus, one JTIDS net has a raw capacity ranging from one half to twice the capacity of a phone-line modem.
Since JTIDS divides its available L-band spectrum into 51 channels, the extreme upper bound on the number of bits per second that can be transmitted simulta- neously from all JTIDS terminals in a tactical arena is 51 × 115,200, or 5,875,200 bps. 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 chan- nels are used for transmission, and it ignores the overhead of housekeeping bits.
Working from the previous calculation, JTIDS achieves 5,875,200 bps in 51 × 3 MHz of RF spectrum, for an aggregate spectral efficiency of 0.0384 bps/Hz.
Partly, of course, this is driven by the tactical need for very robust antijam features. To a noticeable extent, though, it is driven by the basic short-frame TDMA structure of the JTIDS waveform, where rather short payloads are sur- rounded by the dead times of synchronization patterns and propagation allow- ances.
B.2 ASSESSMENT OF PMW 159’S PLANNED IMPROVEMENTS
APPENDIX B 155
B.2.1 Dynamic Network Management System for Link 16
These are a set of interrelated changes to the JTIDS channel access proto- cols that should allow more flexible use of JTIDS networks. Key technical features are improvements in the methods used for late net entry, for reallocating time slots as demand changes, and for varying the throughput rate dynamically.
In passing, it is noted that many of these techniques have already been used in a wide variety of other radio systems and hence pose relatively little technical risk.
Assessment. These incremental improvements will probably succeed and will make JTIDS somewhat more flexible than with its current (highly rigid) architec- ture. As a result, there is potential to make JTIDS easier to use in practice. This is important and useful work and should be supported. On the other hand, to a large extent these improvements are merely Band-Aids for a fundamentally unsuitable network architecture. They will allow more flexibility in the use of JTIDS net- works, but the improved system can be considered “flexible” only in comparison with classic JTIDS; it is by no means as flexible as modern commercial systems.
In addition, of course, JTIDS will remain a closed system. The final judgment, therefore, is that this work should be supported—it is certainly better than classic JTIDS—but that it will not in the end provide the degree of flexibility required for today’s or tomorrow’s tactical communication needs.
TABLE B.2 Planned Improvements and Potential Benefits
Planned Improvement Potential Benefit
Dynamic network management system Incremental increases in the flexibility of (DNMS) for Link 16 Link 16 networks, perhaps coupled with
greater ease of planning and configuring for such networks
Enhanced throughput Higher bandwidth communications across Link 16 radio channels
Optimized relative navigation More accurate relative position and time information for Link 16 platforms Joint range extension, S-TADIL J Increased ability to transmit J-series
messages across non-JTIDS radio channels Link 16/JVMF advanced concept Gateways between Link 16 radios and their technology demonstration messages, on the one hand, and the Army’s
messaging system on the other Link 16 missile and tactical terminal Tactical command and position/location (LMT2)/TacLink weapons links to guided munitions
xx
B.2.2 Enhanced Throughput
This program aims to increase JTIDS’s bandwidth by employing modern channel encoding techniques to achieve more bits per second per hertz. The upper bound on the improved speed is claimed to be 1.1 Mbps, which is nearly 10 times the current maximum rate.
Assessment. This program is a low-risk incremental improvement to JTIDS that may well have practical utility. As such, it should be supported. It would be unwise, however, to assume that the new maximal rate of 1.1 Mbps will in fact be achieved often in practice. Maximum rates for wireless communications are usually achieved only for stationary objects that are quite close to each other in a clear RF environment, because performance degrades quickly with Doppler ef- fects, distance, and interference. Since JTIDS is generally employed between mobile platforms across relatively long distances, the actual data rates may be well below maximal. In addition, since most JTIDS time slots are received by a number of different platforms, the transmitted data rate must reflect the lowest common denominator among the receivers (e.g., the farthest away, the fastest moving, the one with the oldest equipment). Again, the reader is reminded that the commercial wireless world is in a creative foment at the moment and that a large number of very-high-speed wireless technologies are now appearing in the market. On the whole, these technologies are likely to deliver significantly higher overall throughput than enhanced JTIDS since they do not suffer from JTIDS’ very short time slots, which ensure that a very high percentage of poten- tial transmission time is in fact sacrificed to dead time between bursts. This is, therefore, a good incremental enhancement to JTIDS, but the Navy should also look elsewhere for high-bandwidth wireless technology.
B.2.3 Optimized Relative Navigation
This program plans to improve the relative navigation capabilities of Link 16 so that it will deliver position/location information with an accuracy that equals or exceeds that of the current GPS system (≤3 m circular error probability) and time synchronization to the nanosecond level. It will do so by transmitting raw, uncor- rected pseudo ranges and employing new algorithms on these data.
Assessment. Higher-level functions of battle management such as the SIAP rely on highly accurate position and time information. Thus, any effort to im- prove these data could have a significant payoff. This particular method has the additional virtue of being independent of GPS and thus providing a robust back- up capability for position and time services and should be supported.
APPENDIX B 157
B.2.4 Joint Range Extension, S-TADIL J
Joint Range Extension, S-Tadil J combines two distinct programs, both of which aim to add a capability to transmit J-series messages across non-Link-16 communications channels.
Assessment. This is a highly desirable goal, but the approach is fundamen- tally misguided. The key problem here is that JTIDS has confounded the distinct problems of message formats and RF channel architecture. The proper solu- tion—and one that has been universally adopted in the commercial communica- tions world, both in the Internet and in all telephone technology, for decades—
has been to use a layered protocol stack so that any type of message can flow across any type of communications medium. Rather than sort out how J-series messages should be conveyed across any type of medium, these programs are attempting minor incremental “kludges” to work across satellites and so on. The committee believes that this entire approach will ultimately reach a dead end. A program that determined how J-series messages could sent using the Internet Protocol suite would better serve the Navy.3 They could then be transmitted across virtually every known type of communications channel with no additional effort on the Navy’s part.
B.2.5 Link 16/Joint Variable Message Format ACTD
This advanced concept technology demonstration (ACTD) will show that the J-series messages conveyed across Link 16 can be translated to the messages formats employed in the Army’s digitized battlefield.
Assessment. From a high-level viewpoint, it is unfortunate that the Army message formats are not compatible with those used in Link 16, but since this is the case it is clearly better to gateway the two systems together with translators than to have no connection between them at all.
B.2.6 Link 16 Missile and Tactical Terminal/TacLink Weapons This concept envisions a small tactical radio, based on Link 16 technology, that can be installed in cruise missiles and other guided munitions to give them (1) a precise positioning system, (2) a command link for updates on mobile target locations, and (3) improved potential for battle damage assessment. This concept would also enhance overall situational awareness since it would allow all missiles and guided munitions to be included in the SIAP.
Assessment. Judgment is reserved on this concept. It seems to be a for- ward-thinking idea that is well aligned with the necessary future direction of
3There have been some limited experiments along these lines.
BMC3. And JTIDS certainly does have good antijam properties, which would be essential in such tasks. On the other hand, JTIDS provides a poor starting point for this concept, partly because JTIDS networks have proven extremely difficult to plan and configure, but mainly because thus far JTIDS radios are extremely expensive. It is certainly possible that both problems could be over- come, but the solution would certainly be much easier if a different starting point were adopted.
159
C
Obtaining More Flexible BMC3 Configurations
The main body of this report makes the important point that greater flexibil- ity in establishing missile defense BMC3 configurations is necessary and that commercial wireless communications technology provides a critical ingredient in obtaining this flexibility. This appendix elaborates on that point by first discussing a system engineering process that would lead to greater flexibility and then providing some detail on commercial wireless communications technology.
C.1 SYSTEMS ENGINEERING FOR BMC3