Army Digitization Master Plan '96
6. IMPLEMENTATION STRATEGY
The digitization implementation strategy is comprised of four thrusts.
These thrusts, which are conducted in accordance with the Technical, Operational, and System Architectures, are in full compliance with DoD architectural guidance and will be executed in the three phase process described in Section 7, Acquisition Strategy. The intent is to quickly digitize by employing current technologies to acquire, exchange, and process critical information throughout the battlespace and to evolve this capability to reflect insights gained from AWEs and opportunities for technology enhancements.
6.1 Thrust 1 - Force XXI Battle Command, Brigade-and-Below (FBCB2)
FBCB2 provides near-term C2 capabilities to Force XXI units at brigade and subordinate echelons. The FBCB2 system is comprised of hardware, software, and databases being acquired under the Applique and other programs. FBCB2 interfaces with:
- Items already found at brigade-and-below echelons. Examples of these are components of ATCCS and C4I capabilities embedded in weapons systems/platforms.
- The Army Tactical Internet, which is Thrust 2 of the Army's Implementation Strategy and is discussed in Section 6.2.
One of the most important aspects of this effort is the development of software and database capabilities which are common and seamlessly interoperable across all systems at these echelons. The FBCB2 software suite, which re–uses and incorporates existing commercial and government software wherever practical, will meet the open systems standards found in the ATA. The FBCB2 software suite is also being developed for forward compatibility with the mainstream of commercial hardware and software developments in order to facilitate the insertion of new technology as the Army evolves to Force XXI. FBCB2 software will incorporate essential functions from the M1A2’s Inter-Vehicular Information System (IVIS) and from the Brigade-and-Below Command and Control (B2C2) prototype. New functionality is being concurrently developed, based on requirements contained in the FBCB2 UFDs.
6.1.1 FBCB2 Software Functionality
FBCB2 software functionality is contained in operating system, utility, and mission applications software. This software will be modular; have formally defined and openly published APIs; and will be scaleable across a range of host hardware platforms.
6.1.1.1 Common Operating Environment Compliance
FBCB2 will have an operating environment that is compliant with the DII COE. It will consist of operating system and support software modules which are either reused directly from the DII COE discussed in Section 4, or are functionally compatible with it. The Army will re–use COE modules where possible. Work has begun to determine if necessary COE modules can be scaled-down to function satisfactorily on man-portable digitized systems—such as the Dismounted Soldier System Unit (DSSU)—and selected embedded weapons system processors. All software developed by the FBCB2 Program will be DII COE-compliant to the extent possible; designed for use by either strap-on or embedded programs; and used as necessary to extend the COE through the formal COE extension process.
6.1.1.2 Situation Awareness
Situation awareness is provided by collecting, integrating and displaying a common picture of the battlefield that is consistent in both time and space at each user display. MA software being developed for FBCB2 situation awareness allows the geographical location of individual soldiers, weapons/platforms, command posts, and other operational facilities to be collectively presented on a display. Because the Army Tactical Internet is a true, seamless internet based on the world-wide Internet model, it is possible to communicate each individual geolocation to every FBCB2-equipped user within the Tactical Internet. Addressing mechanisms allow geolocations to be flexibly and selectively communicated, and situation awareness software functionality will contain the necessary filters and roll-up mechanisms for each user to be able to selectively display only the locations of units of interest.
6.1.1.3 Operational Control
One of the methods by which operational control is achieved is through the transmission and receipt of orders, reports, and data in a timely manner. The VMF messaging function of FBCB2 software provides a key mechanism for effecting that exchange, using a set of 51 joint-approved VMF messages. Each FBCB2-capable system will have the ability to automatically or manually compose, edit, transmit, receive, and process either the full set of these messages or a subset which is specific to the mission profile of that system. The initial VMF message set of 21 messages was developed specifically for the TF XXI AWE and will be expanded for use in the Division XXI and Corps XXI AWEs. It provides the ability to communicate orders, reports, and data in near real-time over the bandwidth-restricted networks found at brigade-and-below echelons. The VMF messaging software also provides the ability to insert and extract data from these messages for automatic insertion or update of tactical databases.
6.1.1.4 System Management and Control
FBCB2 will be a complex system involving over 1,000 computers in each maneuver brigade, all tied together in a single seamless network. Since it is not possible for this system to start up, operate, and gracefully degrade of its own accord under all conditions without human intervention, FBCB2 software will provide the capability to initialize, control, and conduct an orderly shut-down of the FBCB2 system. Capabilities will be provided in the areas of:
6.1.2 Functionality Implementation of FBCB2
6.1.2.1 Applique
Use of appliques is intended to provide C2 capabilities to platforms that either have no embedded C2 capability or whose existing capability is inadequate to meet emerging user requirements. For a platform lacking an embedded digital capability, it will be appliqued with:
6.1.2.2 Army Tactical Command and Control Systems
As discussed in Section 5, ATCCS systems are in the process of migrating to the DII COE. Since FBCB2 functionality is also based on use of the COE, selected FBCB2 functional components will be provided for incorporation into ATCCS systems in the near–term. In the far–term, core FBCB2 functionality and other mission applications will be migrated to ATCCS systems.
6.1.2.3 Embedded Systems
Many Army systems have an embedded C4I capability, including the M1A2 Abrams, the M2A3 Bradley, the AH-64D Longbow Apache, and the OH-58D Kiowa Warrior. At a minimum, the Army plans to integrate FBCB2 software functionality into these platforms sufficient to generate and receive an appropriate subset of the VMF message set.
6.1.2.4 Other Systems
The Army is working with the Navy, Air Force, and Marine Corps to provide interface documentation, FBCB2 software modules, and/or complete applique sets for use in various warfighting experiments, as appropriate to the needs of the user.
6.2 Thrust 2 - Tactical Internet
One of the top priorities of the Army in digitizing the battlespace is to provide command and control capability throughout the force. This requires a horizontally and vertically integrated digital information network that supports warfighting systems and assures command and control decision cycle superiority. The network must provide reliable, seamless, and secure communications- connectivity for all Army tactical users
The Tactical Internet is the term used to describe this integrated battlespace communications network The term is appropriate due to functional similarities to the commercial Internet and because the Tactical Internet communications
Figure 6-1 Integrated Digital Information Network
infrastructure is based on Internet technology. A key feature is the ability to exchange VMF messages using the commercially-based Internet Protocol (IP), which is mandated in the ATA and is common across all segments of the Tactical Internet.
As depicted in Figures 6-1 and 6-2, the initial digital communications system will consist of a space-based segment, an EPLRS-based backbone, a SINCGARS CNR segment, and a Mobile Subscriber Equipment/Tactical Packet Network (MSE/TPN) segment—all integrated via routers. The integrated digital transport capability of these communications segments is key to moving information among the Force XXI nodes and platforms. The communications infrastructure is focused on achieving seamless information transfer horizontally and vertically across the battlespace. This is achieved through the employment of commercial Internet technology (e.g., IP routers) and open standards protocols (e.g., TCP/IP). COTS IP-based routers (e.g., Tactical Multinet Gateways (TMGs) and Local Area Network (LAN) routers) and Internet Controllers (INCs)—which are single circuit card, militarized Internet-based routers—provide the ability to send messages between any segment of the tactical battlespace network. While INCs are physically incorporated into a SINCGARS mount, they provide a host and an EPLRS interface, as well as a SINCGARS interface.
Enhanced versions of the three primary Army tactical communications system segments—EPLRS, SINCGARS, and MSE/TPN-will move the ever-increasing amount of digital data associated with command and control applications employed within the modern battlespace. Capabilities will also exist to interface the Tactical Internet to commercial and military satellite communications (SATCOM), providing unprecedented capacity and access to lower–echelon units.
The Tactical Internet supports several key services. These services include functions such as electronic messaging, directory, network management, and security. These services are integral to the value of the Tactical Internet in support of the warfighter. As new host-based services are added—such as DMS electronic mail service—their supporting system components will be folded into the Tactical Internet.
Figure 6-2 Simplified Tactical Internet Components at Brigade Level
Security is an important service within the Tactical Internet. Because of the concern for security, the Tactical Internet will initially be operated as a SECRET High system. Since all directly-connected host computers will be capable of operating up to the Secret level, direct connections to the commercial Internet cannot be permitted. There is, however, a great deal of interest in the new end-to-end encryption devices that will permit Unclassified users to use the SECRET High Tactical Internet to access Unclassified computers connected to the commercial Internet. This capability is of particular importance to CSS users, who typically use Unclassified applications and data, and need to communicate in a split-based mode with large computer systems in CONUS. The availability of multi-level security services will enable greater network flexibility. As these services are realized and integrated into the Tactical Internet, the issue of a SECRET High network infrastructure will be revisited.
Another key component of the Tactical Internet is technical control. The Integrated Systems Control (ISYSCON) program is developing the capability to technically control networks at brigade-and-above level. Since TMGs and INCs must also be technically controlled, additional ISYSCON capabilities in the form of Automatic Network Managers (ANMs) are being added to control the Tactical Internet at brigade-and-below. The management protocol for the ANM will be Simple Network Management Protocol (SNMP), with SNMP agents implemented by communications elements. In some cases, however, proxy agents will be used (e.g., SINCGARS and EPLRS proxy agents will be hosted on the applique).
The Signal Center (SIGCEN), in conjunction with CECOM, is investigating the operational and training impact of the Tactical Internet. A series of BLWEs, AWEs, and Joint Warfighter Interoperability Demonstrations (JWIDs) will provide an experimental basis to:
PEO C3S, with the support of CECOM and SIGCEN, is responsible for developing the Tactical Internet in accordance with the SA.
Improvements to components comprising the SA are needed to make the Tactical Internet viable. The use of commercial Internet protocols provides the required level of seamless connectivity between the different networks, but Internet protocols increase data capacity requirements because additional header information must be added to each message. The Internet routers exchange routing and status information, which also increases data capacity requirements. Even with the improved data capacity of SINCGARS, EPLRS, and MSE, these systems provide relatively small communications trunks compared to fixed-site commercial systems. A comprehensive modeling and simulation effort is therefore required to determine the optimum parameters for the use of Internet protocols in a dynamic military environment featuring relatively few communication links.
6.3 Thrust 3 - Integration of Battlefield Operating Systems
The integration effort will link the components of ABCS to individual weapons systems, creating a seamless network from the soldier through the tactical and operational levels to the sustaining and strategic level. Technical integration of legacy systems and embedded and non-embedded digital capabilities into a system-of-systems presents many challenges.
6.3.1 Embedded Systems
Embedded systems are digital system components providing functions and processes which are integrated into a hardware platform to such an extent that they can not be considered as discrete entities during development, testing, or production of a system. Examples include fire control, position/navigation, diagnostics, and communications equipment installed on the M1A2 Abrams, AH-64D Longbow Apache, and OH-58D Kiowa Warrior. The software and hardware of these platforms may also perform common battle command functions such as providing situation awareness, using common digital terrain data, and receiving/transmitting digital messages.
Some embedded digital systems are wholly contained within a platform, with standards and protocols for their internal connectivity defined by the PEO. The PEO must consider cost when applying standard development concepts such as growth, open system architectures, flexibility, and interoperability with other platforms.
Modular, multi-function hardware designs are being adopted. Emerging technology affords the opportunity for a significant shift away from single-purpose designs toward multi-purpose alternatives in which functions are implemented on removable, upgradable circuit cards, microchips, or in the software.
Embedded digital systems that interact with dissimilar weapon systems or C2 nodes must at least use common message sets. Digital communications, standard data protocols, icons, and applications are required to pass the same information for applications such as overlays, calls-for-fire, and spot reports. The ATA provides specific requirements in this area, which will be documented in Interface Control Documents (ICDs).
Embedded digital systems already in the inventory or programmed for future fielding are part of the SA. The primary integration challenge resides at the lower echelons, where existing legacy systems were originally developed to provide vertical stovepipe information flows in support of specific battlefield functional areas. As such, the Applique contractor has developed system/subsystem segment ICDs for platforms to be digitized. The ICDs will document interfaces to existing platform power, MIL-STD 1553 data bus, communications, navigation, and sensor subsystems as appropriate.
The AAE has mandated compliance with the ATA by all PEOs and PMs, to include those who are developing platforms with embedded digital systems. In practice, this mandate requires the PEOs and PMs to:
6.3.2 Legacy Systems
Many legacy systems will be a part of the digital battlespace. They present a wide range of integration issues associated with protocols, data standards and message exchange. For example:
To reduce the risk associated with development of FBCB2 software and the Tactical Internet, both will be baselined on the world-wide Internet protocol suite (i.e., TCP/IP). Additional baseline elements include the TF XXI VMF TIDP and its associated data communications protocols, such as MIL-STD 188-220A.
The ADO is working with the various legacy PEOs and PMs to obtain forward compatibility with FBCB2 software and the Tactical Internet. For example:
SINCGARS SIP radios, applique hardware, and FBCB2 software may be provided as an interim capability for cases in which schedules, funding or technical considerations do not allow near-term integration and interoperability. Backward compatibility will be selectively implemented.
6.3.3 Sustaining Base Systems and Intelligence Systems
Although the initial focus of digitization has been on C2 systems, the Army is also digitizing its Army battlefield personnel and logistics processes—the sustaining base systems—and is taking steps to more fully integrate these systems and the tactical intelligence systems into the digitized force. This poses two unique challenges. The first is associated with security, and the second with split base operations.
6.3.3.1 Multi–Level Security
While the Army’s tactical communications backbone and other battlefield automated systems generally operate at the SECRET level, sustaining base systems normally operate at the UNCLASSIFIED level, while certain intelligence systems operate at levels more restrictive than SECRET.
In the far–term, the Army plans to address this multi–level security challenge by migrating its communications backbone to the Defense Goal Security Architecture (DGSA) in harmony with the Defense Information System Network (DISN), using components (e.g., Fortezza) developed under the Multilevel Information Systems Security Initiative (MISSI). In the near–term, the Army plans to use In-Line Encryptors (INEs)—such as the Network Encryption System (NES) and the Tactical End-to-end Encryption Device (TEED)—that will allow sustaining base and intelligence systems to use the Tactical Internet by tunneling through.
6.3.3.2 Split Base Operations
The evolving split base concept envisions some portion of sustaining base and/or intelligence assets either remaining at their normal peacetime location or deploying to a safe haven some distance from the battlefield. The success of this concept hinges, in part, on the ability of forward-deployed units to reach back via responsive communications to their stay-behind elements, and this implies a communications capability able to support this reach back requirement.
When connected to the DISN through a Standardized Tactical Entry Point (STEP), the Tactical Internet will provide seamless data communications from the forward deployed to the stay-behind elements. The Army also plans to exploit commercial communications capabilities using Trojan Spirit II and Tri-band satellite communications terminals, as well as the high-data rate capacity now emerging under the Battlefield Awareness and Data Dissemination (BADD) program. The Army must also modernize its power projection platforms—the fixed installations at the stay–behind end of split base operations.
6.4 Thrust 4 - Battlefield Information Transmission System (BITS)
As more users and increasingly-complex systems are added to the battlespace array, the Tactical Internet will be unable to handle the data transmission load. In the next 2–5 years, this shortfall will be absorbed by adding a Near Term Digital Radio (NTDR) to replace EPLRS. For the far–term, the BITS program is developing technologies for much greater information throughput.
The technology programs being pursued by the BITS program are described below. Proposed product availability dates for insertion into the major AWEs are shown in Figure 6-3.
TF DIV Corps
PRODUCT QUANTITY XXI XXI * XXI* FY 99
Near-Term Data 24 SDR X
Radio/Surrogate Up to 400 NTDR (option)
Data Radio Up to 900 NTDR (option) [X]
Asynchronous 11 ATM Switch (MSE) X
Transfer Mode 4 Low Rate ATM Switch X
7 Multimedia Workstation X
Tactical 30 TEED X
End-to-End
Encryption
Devices
Terrestrial LMR:1Base Station/50 X
Personal Handsets X X
Communications 2 MSE Interface (each) X
Systems Hybrid CDMA: 2BS/50
Handsets
Global Broadcast 1 Uplink, 8 Downlinks X
Service 1 Program Center (X)
1 UAV Payload X
1 OTM Antenna (X)
High-Capacity 4 HCTR (10 Mbps) X
Trunk Radio 4 Static HCTR (45 Mbps) X
4 OTM Antenna X
Airborne Relay 1 Abn Relay (45 Mbps) X
1 Abn Relay (155 Mbps) X
Satellite 1 UAV Payload, 25 X
Personal Handsets X
Communications Up to 100 Universal
System Handsets
On-the-Move 1 OTM Antenna (45 Mbps) X
Antenna
Radio Access 1 Static RAP X
Point 1 OTM Antenna (Mobile X
RAP)
(X) Development complete, but not funded for AWE
* Subject to change based on Oct 95 decision on downscoping Division and Corps AWEs
Figure 6-3 BITS AWE Product Insertions
The strategy for acquiring a BITS capability is based on the following three-phase program:
6.4.1 Surrogate/ Near–Term Digital Radios (SDR/NTDR)
Under the SDR BAA, CECOM will provide approximately 24 SDR systems. The concept of operations for the TF XXI AWE is to equip a portion of the brigade with the SDR BAA field models to form a small digital radio net. The goal of the experiment will be to determine its effectiveness in passing high-volume digital traffic through a network in a battlefield situation.
The NTDR system will have an open hardware, software, and system architecture. An NTDR testbed will be established in the DIL at CECOM for inserting technology from SPEAKEASY and other programs. Through the process of technology insertion, the NTDR may ultimately provide the full range of functions and capabilities required of the SDR.
6.4.2 Asynchronous Transfer Mode (ATM) Technology Integration
Emerging high-data-rate services and applications (e.g., video) cannot be effectively supported by the existing MSE/Tri-Service Tactical (TRITAC) system. ATM technology has the potential to support these and other wideband services, but was designed for use in low bit-error-rate, fiber optic-based static networks. Effective use of ATM technology in a tactical environment will require that forward error correction, low-rate survivable protocols, bandwidth allocation, signaling, and wireless ATM areas each be adequately addressed before ATM is ready for use with the new High-Capacity Trunk Radios (HCTR).
ATM experiments conducted during Unified Endeavor in April 1995 will serve as the program baseline. In that exercise, seven ATM switches were installed into MSE shelters, enabling MSE voice traffic to be combined with data traffic over the existing MSE backbone network.
This and other field trials have shown that while ATM technology can be used in certain tactical applications, many technical issues must be resolved before ATM technology can be deployed effectively in a tactical network.
6.4.3 Tactical End-to-End Encryption Device (TEED)
TEED is an encryption device used to provide end-to-end security for Force XXI data users. As long as the MSE/TPN remains at its current SECRET High security level, TEED would be used by:
In the first instance, TEED is used to protect the base-level Secret users from users working at lower classifications. In the second, TEED protects the higher-level Top Secret users from the base network. TEED is designed to protect both of these applications. Further development is needed to produce a TEED that will encrypt ATM and IP traffic. The National Security Agency (NSA) is investigating the new BATON encryption algorithm for this use.
6.4.4 Terrestrial Personal Communications Systems (PCS)
Research and development performed in the area of terrestrial PCS is a cooperative effort between the ARPA-funded Commercial Communications Technology Testbed (C2T2) program and the CECOM Commercial Communications Technology Laboratory (C2TL) and Digital Battlefield Communications (DBC) ATD programs. PCS capabilities developed under these programs will be demonstrated during the TF XXI AWE.
The Land Mobile Radio (LMR) system provides intermixed digital voice and data transmission over multiple 9,600 baud, half-duplex channels. Handheld Personal Digital Assistants (PDAs) and generic laptop x486 computers are interconnected via this system. GPS receivers and heads-up displays are also integrated with the computing devices.
Hybrid PCS is the second-phase system under the C2T2 program. It is expected that this second system will have smaller (transportable) base stations; better hand-off and peer forwarding; more users per channel; higher data rates; and lower transmit power. Broadband code-division multiple access (CDMA) technology is being explored for this system.
A key piece of the demonstrations scheduled in conjunction with the TF XXI and Division XXI AWEs is the interface to MSE. Because current LMRs only have an interface to the public switched telephone network, a more complex interface is needed for MSE. This interface will be developed under the DBC ATD.
6.4.5 Army Direct Broadcast Satellite (DBS)
Commercial DBS systems offer the potential for low-cost, wideband data and video dissemination. Unfortunately, these systems are geographically limited to CONUS; are designed specifically for the home user; use commercial frequency bands; and are nearly at maximum capacity. This project, in coordination with the Joint Global Broadcasting System (GBS), will develop an Army DBS system providing the flexibility required to support operations while maximizing the benefit of low-cost commercial developments.
Three commercial DBS terminals will be acquired, modified to work with standard Ku-band antennas, and integrated with Sun workstations to provide an uplink/downlink capability. A single Army DBS programming center will be established to consolidate, schedule, and control data/video dissemination. An airborne DBS transponder will be developed and demonstrate a global capability for in-theater data dissemination under direct control of the theater commander. Finally, the capability to receive DBS data on a moving platform will be explored.
6.4.6 High-Capacity Trunk Radio (HCTR)
HCTR will serve as the next-generation line-of-sight radio for MSE. It will provide a trunk radio capable of a minimum data rate of 45 Mbps to support ATM switching. As an integral part of the Radio Access Point (RAP), the HCTR will also extend wideband integrated communications services to highly mobile forces.
The HCTR program is a technology-based, advanced development initiative to explore and develop technologies supporting a wideband trunk radio with the capability of operating while on-the-move. The program will include the evaluation of a COTS synchronous optical network (SONET)-based radio, starting with the delivery of the radio in November 1996 and concluding with a report in September 1997. Concurrent with the COTS SONET radio experiment, an accelerated procurement will be conducted to provide a near-term wideband radio, HCTR(-), with a performance goal of 10 Mbps and 20 Km range for near-term ATM upgrades to MSE. The objective HCTR will be capable of providing 155 Mbps operation in a static mode, and 45 Mbps in an on-the-move mode. Four on-the-move HCTRs are planned for delivery in early FY99.
In the stationary mode, the HCTR will provide a wideband multi-channel trunking capability for MSE. It will act as an upgrade replacement for the current AN/GRC-226, providing wideband backbone and extension links for ATM-equipped MSE switching assemblages. In the on-the-move mode, the HCTR will be operated as an integral part of the mobile RAP. As part of the RAP, the HCTR will connect various narrowband tactical systems—including SINCGARS, EPLRS, NTDR, and MSE—to the wideband point-to-point backbone network.
6.4.7 Airborne Relay
Current extended-range communications are heavily dependent on satellite links and terrestrial networks, presenting a number of operational limitations in many parts of the world. This project will develop an airborne relay capability providing a wideband communications range extension, supporting the HCTR and RAP programs. The wideband airborne relay will also be part of the UAV communications payload suite.
6.4.8 Satellite Personal Communications Systems (PCS)
Satellite PCS will provide worldwide communications via networks of low–earth orbiters using handheld units. Systems are expected to support voice, facsimile, data and paging communications. This program will investigate commercial satellite-based systems to develop an autonomous battlefield personal communications capability. This will include development of a UAV-based system and universal handsets. The current strategy is to work with industry toward developing cooperative research and development agreements.
6.4.9 On-the-Move Antenna
This program will develop a wideband communications on-the-move antenna to support RAP HCTR communications. The antenna will be capable of operating in line-of-sight mode and via an airborne relay. Phased-array antenna technology is being pursued because these antennas are generally lower in profile and more agile than reflectors. There are, however, technical limitations that impact their effectiveness, particularly at low and varying look angles. The RAP antenna program will address these concerns by developing an on-the-move capability for the Common Ground Station antenna and adapting that technology to support the HCTR.
6.4.10 Radio Access Point (RAP)
RAP is a vehicular-mounted self-contained communications center that contains an ATM switch, an HCTR, an on-the-move antenna, a controlling workstation, and interfacing equipment for narrowband tactical systems, to include SINCGARS, EPLRS, NTDR, and the MSE Mobile Subscriber Radio Terminal (MSRT). RAP allows mobile narrowband tactical users to access wide bandwidth networks for voice, data, and video communications.
RAP will seamlessly extend wideband trunks from the tactical point-to-point backbone to lower echelons with support for integrated voice, data, and video access to/from users located on mobile platforms or foot-mobile. A phased approach of developing and demonstrating a RAP capability will be used. It will involve developing, acquiring and integrating the required interfaces, protocols, and software, as well as assembling the system hardware.
The specification phase will develop a high-level system documentation/specification with detailed RAP functional and performance specifications. A laboratory RAP prototype phase (RAP V1) will demonstrate connectivity in a static, laboratory environment. The data rate of the wideband trunk will be a maximum of T1. During RAP V2, a mobile RAP host will be demonstrated in a laboratory environment, using mobile IP with low to medium (2.4 kbps to 56 kbps) data-rate channels. A static RAP field demonstration will incorporate a static version of the HCTR radio provided by the HCTR program. Finally, communications on-the-move will be demonstrated in 1999 using a mobile RAP.
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
