![]() |
|||||
|
|
![]() The military envisions a future "network-centric warfare" where unrestricted communication between any allied combatants is possible. It is widely recognized that the military's current wireless communication systems are inadequate for this task. The underlying problem is both pervasive and subtle; it is not one of technology, but one of design. Military systems were notand, largely, are still notdesigned in a way that allows extensibility and reuse. Extensible and reusable communications systems do exist, and a study of their architectures is revealing. One successful architecture is demonstrated in the revolution in phone-line modems. Each generation provided a very precise and very limited function, interfacing an RS-232 digital data port to an analog phone line. These devices "encapsulate" the modem function and present standard interfaces (such as the HAYES modem protocol) to their hosts. Encapsulation and interface standardization allowed developers to innovate, differentiate, upgrade, and interoperate with other products. It is the functional encapsulation and standardized interfaces, not the underlying technology, that afforded this flexibility. In fact, throughout their evolution, phone-line modems have freely changed technology, the most dramatic shift being from a hardware-intensive implementation to the primarily software implementations of today.
Figure 1. Layered Radio The Internet protocols offer a second, larger example. The Internet protocols loosely partition communication into distinct functional layers. This functional encapsulation provides the extensibility and flexibility that have led to new protocols, applications, and hardware. Again, the acceptance of several inter-layer standard interfaces have enabled innovation and competition. As with the modem example above, the Internet protocols show a technology neutrality which, for example, allows hardware and software implementations of routers. While the Internet's layering may be imperfect, the power of the layered approach is obvious; the Internet is a very large, rapidly evolving, heterogeneous, ubiquitous, interoperating communication system. We believe that a functionally encapsulated, layered architecture is a critical requirement for future military communications systems. Are "Software Radios" the Answer? Software radios, while an important part of future military communications, are not the whole answer. We believe that technology neutrality is a far more important architectural goal. Architectural Considerations Conceptually, in a functionally layered architecture, individual functions such as media access, channel coding, and modulation can be selected independently and integrated into a working system. Such flexibility requires clearly defined interfaces in addition to a concise functional decomposition. The functional decomposition and design of these interfaces is not trivial, and several commercial standards are emerging. Standardizing inter-layer interfaces is more problematic than clean functional decomposition. There are two reasons for this. First, the design of the interface affects the complexity and flexibility of components. Second, interface compatibility requires standardization on several levels: one interface may have mechanical, electrical, framing, protocol, and semantic requirements. This is shown in Figure 2.
Figure 2. Several Interface Levels Fortunately, the least abstract levels of interface are both the most
likely to change and the easiest to modify. For example, conversion between
mechanical interfaces (9-pin to a 25-pin connection) is easy and inexpensive.
The adaptation becomes more difficult and costly at the more abstract
levels of interface which, perhaps oddly, are the ones frequently implemented
in software. Thus, the higher levels of interface (command format and
semantics) are the most critical; these are the emphasis of our work at
MITRE in communications layering. Conclusion For more information, please contact Michael Butler using the employee directory. |
Solutions That Make a Difference.® |
|
|