(ec2) enhancement

Transcription

(ec2) enhancement

TECHNICAL VALIDATION REPORT:
BROADBAND GLOBAL AREA NETWORK
(BGAN) AS AN
EXECUTIVE COMMAND AND CONTROL
(EC2) ENHANCEMENT
15 MARCH 2006
This page intentionally left blank.
Joint Systems Integration Command (JSIC)
Technical Validation Report - BGAN as an EC2 Enhancement
15 March 2006
EXECUTIVE SUMMARY
PURPOSE
The purpose of the technical validation of Inmarsat’s new Broadband Global Area Network
(BGAN) service was:
•
•
•
To ensure the Executive Command and Control (EC2) kits used by operational Combatant
Commanders (COCOMs) and Joint Task Force (JTF) Commanders will continue to function
operationally if the users transition to BGAN service.
To identify additional capability that could be incorporated into future EC2 kits as a result of
the increased bandwidth capability available through the BGAN service.
To conduct a technical validation of a select number of BGAN terminals as potential
replacements for Regional Broadband Global Area Network (RBGAN) terminals currently in
use.
OVERVIEW
Inmarsat is establishing a new BGAN service using a three-satellite constellation to provide
world-wide coverage and increased capability. The EC2 kits currently used in the U.S. Central
Command (USCENTCOM) and U.S. European Command (USEUCOM) area of operations
(AOR) often use Inmarsat’s RBGAN service to reach back to the COCOM or JTF Commander’s
host classified networks. Since this new BGAN service has the potential to offer additional
capability at potentially less cost, the Joint Systems Integration Command (JSIC) conducted a
technical validation to ensure operational commanders using the EC2 kits and RBGAN will
suffer no loss of operational capability should they decide to use the BGAN service. The JSIC
partnered with Inmarsat to perform a technical validation of select BGAN terminals and EC2
kits.
Partnering with Inmarsat, JSIC used Inmarsat-provided prototype BGAN terminals and
conducted a battery of tests to assess performance of the BGAN service in the northwest, center,
and southeast quadrants of the first BGAN satellite coverage area. In addition, JSIC teamed with
USEUCOM Commander’s communications team to ensure the reach back to USEUCOM
classified networks was not adversely affected using the BGAN service.
CONCLUSIONS
The conclusions of this technical validation are:
•
•
There is no loss of EC2 kit functionality using BGAN service.
The increased bandwidth service may enable additional capability and functionality of the
EC2 kit (i.e., video teleconferencing (VTC), streaming media, secure voice, etc.).
i
•
•
15 March 2006
The prototype BGAN terminals used during the tests varied in capability and levels of
maturity. Inmarsat identified technical issues with the terminals and is resolving them with
the BGAN terminal vendors.
BGAN’s increased bandwidth will provide wide ranging benefits for other mobile
government users.
RECOMMENDATIONS
As a result of the technical validation, JSIC recommends:
•
•
•
•
•
COCOM and JTF Commanders using RBGAN services with the EC2 kit should, depending
on user requirements, consider a switch to BGAN.
Users of Inmarsat M4 satellite services should, depending on user requirements, consider a
switch to BGAN.
COCOM Commanders, JTF Commanders, and users of Inmarsat M4 satellite services
switching to BGAN services should analyze their own requirements to determine the most
appropriate BGAN terminal.
BGAN users should consider incorporating the additional functionality (VTC, streaming
media, secure telephone, etc.) made available by the new service and terminals in any future
EC2 kit enhancements.
COCOM and JTF Commanders interested in implementing BGAN service may access this
report and additional information on the JSIC external unclassified web site
(https://extranet.jsic.jfcom.mil/la) and the JSIC Secret Internet Protocol Router Network
(SIPRNet) web site (http://www.jsic.jfcom.smil.mil).
ii
15 March 2006
TECHNICAL VALIDATION REPORT – BGAN AS AN EC2
ENHANCEMENT
DISCLAIMER
The use of trade names in this document does not constitute an official endorsement or approval
for the use of such commercial hardware or software. This document may not be cited for
purposes of advertisement.
DISTRIBUTION
See Appendix G for distribution. Refer questions or other requests for this document to the Joint
Systems Integration Command (JSIC) Advanced System Prototyping (ASP) Directorate, 116B
Lake View Parkway, Suffolk, VA, 23435-2697, Commercial Phone (757) 203-7522 or DSN
668-7522; E-mail jsicoperations@jfcom.mil.
PREPARED BY
David Jones, david.r.jones@jfcom.mil; 116B Lake View Parkway, Suffolk, VA, 23435-2697;
757-203-4525
Tracy Carroll, tracy.carroll@jfcom.mil; 116B Lake View Parkway, Suffolk, VA, 23435-2697;
757-203-4485
Maj James Knapp, james.v.knapp@jfcom.mil; 116B Lake View Parkway, Suffolk, VA, 234352697; 757-203-4557
REVIEWED BY: _____________________________ DATE: ______________
Daniel M. Bryan
Colonel, United States Air Force
Commander, Joint Systems Integration Command
iii
15 March 2006
iv
15 March 2006
TABLE OF CONTENTS
1
INTRODUCTION AND BACKGROUND...................................................................... 1-1
1.1
Scope................................................................................................................................ 1-1
1.2
Background ...................................................................................................................... 1-1
1.3
Systems Descriptions ....................................................................................................... 1-3
1.3.1
EC2 .......................................................................................................................... 1-3
1.3.1.1
EC2 Background...................................................................................................... 1-3
1.3.1.2
EC2 System Architecture......................................................................................... 1-3
1.3.2
Inmarsat.................................................................................................................... 1-6
1.3.2.1
Inmarsat Background ............................................................................................... 1-6
1.3.2.2
Inmarsat Satellites.................................................................................................... 1-7
1.3.3
BGAN Service ......................................................................................................... 1-8
1.3.4
BGAN Terminals ..................................................................................................... 1-9
1.3.4.1
BGAN Terminals Background ................................................................................ 1-9
1.3.4.2
BGAN Terminals’ Descriptions ............................................................................ 1-10
1.3.4.3
MMI ....................................................................................................................... 1-12
2
TEST OBJECTIVES ......................................................................................................... 2-1
2.1
Primary Objectives........................................................................................................... 2-1
2.2
Contingency Objectives ................................................................................................... 2-1
3
TEAM MEMBERS AND ROLES.................................................................................... 3-1
3.1
JSIC Test Team Members................................................................................................ 3-1
3.2
EUCOM Test Team Members ......................................................................................... 3-2
4
UNCLASSIFIED TESTING ............................................................................................. 4-1
4.1
Unclassified Test Environments .............................................................................. 4-1
4.1.1
Unclassified Home Network and Services .............................................................. 4-1
4.1.2
The Unclassified Travel Suite.................................................................................. 4-1
4.1.2.1
Satellite Terminals in the Travel Suite..................................................................... 4-1
4.1.2.2
Laptop Clients and Accessories ............................................................................... 4-2
4.1.3
Unclassified Network Architecture.......................................................................... 4-3
4.1.4
Unclassified Data Flow............................................................................................ 4-5
4.1.4.1
Data Flow Accessing BAND Services .................................................................... 4-5
4.1.4.2
Data Flow Accessing the Internet via Reachback.................................................... 4-5
4.1.4
Geographic Locations .............................................................................................. 4-6
4.2
Unclassified Test Methodology ............................................................................... 4-8
v
15 March 2006
4.2.1
4.2.2
4.2.3
4.2.3.1
4.2.3.2
4.2.3.3
4.2.3.4
4.3
4.3.1
4.3.2
4.3.3
4.3.4
Unclassified Test Procedures................................................................................... 4-8
Unclassified Data Collection ................................................................................... 4-8
Unclassified Methodology per Objective ................................................................ 4-8
Objective 1 ............................................................................................................... 4-8
Objective 2 ............................................................................................................... 4-8
Objective 3 ............................................................................................................... 4-9
Objective 4 ............................................................................................................... 4-9
Unclassified Data and Analysis ............................................................................... 4-9
Objective 1 ............................................................................................................. 4-10
Objective 2 ............................................................................................................. 4-10
Objective 3 ............................................................................................................. 4-11
Objective 4 ............................................................................................................. 4-13
5
5.1
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
Classified Testing ................................................................................................... 5-1
Classified Test Environments .................................................................................. 5-1
Classified Methods and Results per Objective ........................................................ 5-1
Objective 1 ............................................................................................................... 5-1
Objective 2 ............................................................................................................... 5-1
Objective 3 ............................................................................................................... 5-2
Objective 4 ............................................................................................................... 5-2
Objective 5 ............................................................................................................... 5-3
6
6.1
6.2
Conclusions and Recommendations..................................................................... 6-1
Conclusions.............................................................................................................. 6-1
Recommendations.................................................................................................... 6-1
vi
15 March 2006
LIST OF APPENDICES
Appendix A – Manufacturer Specifications for Panasonic CF-29 Toughbook.......................... A-1
Appendix B – Day 1 Procedures..................................................................................................B-1
Appendix C – Day 2 Procedures..................................................................................................C-1
Appendix D – STE Tests Thrane & Thrane................................................................................ D-1
Appendix E – STE Test HNS ......................................................................................................E-1
Appendix F – Acronyms Glossary............................................................................................... F-1
Appendix G – Distribution List .................................................................................................. G-1
LIST OF FIGURES
Figure 1-1 RBGAN Legacy Coverage Footprint (in red)........................................................... 1-2
Figure 1-2 RBGAN Coverage Under I-4 (light area legacy coverage, dark area extended
coverage)
1-2
Figure 1-3 Components of EC2 Block 3 Suite ........................................................................... 1-4
Figure 1-4 Classified Data Flow ................................................................................................ 1-5
Figure 1-5 Data Flow with No Broadband Access ..................................................................... 1-6
Figure 1-6 Unclassified Reachback using EC2 ......................................................................... 1-7
Figure 1-7 LaunchPad Control Panel ....................................................................................... 1-13
Figure 4-1 Unclassified Network Architecture .......................................................................... 4-4
Figure 4-2 Internet Request ....................................................................................................... 4-5
Figure 4-3 Internet Response ..................................................................................................... 4-6
Figure 4-4 Footprints of Satellites F1, F2, and F3 ..................................................................... 4-7
Figure 4-5 FTP 1MB Files ....................................................................................................... 4-11
LIST OF TABLES
Table 1-1
Table 4-1
Table 4-2
Table 4-3
BGAN Terminals Descriptions ................................................................................ 1-10
FTP Results ............................................................................................................. 4-12
Streaming Video Scores .......................................................................................... 4-12
TC Scores ................................................................................................................ 4-13
vii
15 March 2006
viii
1
15 March 2006
INTRODUCTION AND BACKGROUND
The Joint Systems Integration Command (JSIC) is tasked to lead near-term transformation of
Joint Force Command, Control, Communications, Computers, Intelligence, Surveillance, and
Reconnaissance (C4ISR) capabilities through technology assessments. The JSIC then provides
objective recommendations for rapid insertion of solutions to support identified Combatant
Commands’ (COCOMs’) interoperability needs for a Joint Task Force (JTF).
1.1
SCOPE
The testing described in this report was conducted in conjunction with Inmarsat Global Limited
to evaluate its new I-4 Broadband Global Area Network (BGAN) satellite which was launched in
March 2005. The JSIC also evaluated new satellite terminal modems designed to take advantage
of the increased bandwidth anticipated from the I-4. The terminals tested were the Hughes
Network Systems (HNS) 9201, Thrane & Thrane Explorer 500, and Nera WorldPro-1000. The
HNS 9101 RBGAN (Regional Broadband Global Area Network) terminal was tested for
comparison purposes both as a legacy terminal and as an entry level terminal for the new
generation.
The tests, it is important to note, are field tests, without the controls of a laboratory environment.
The JSIC Advanced Systems Prototyping (ASP) Directorate test team tested the terminals in an
unclassified environment in London, England; Manama, Bahrain; and Perth, Australia.
Communications experts from United States European Command (EUCOM), in collaboration
with the ASP test team, tested the terminals in a classified environment, including the use of
Secure Telephone Equipment in England, Belgium; Germany; and Afghanistan.
This report is intended to support possible deployments of the BGAN system within the
Department of Defense (DoD) and possible replacements of the RBGAN systems currently in
use by COCOMs and JTF Commanders as part of the Executive Command and Control (EC2)
kit.
1.2
BACKGROUND
The purpose of the EC2 kit is to make information more readily available to the COCOM, the
JTF Commander, and executive staff by providing them access to classified and unclassified
network services while on temporary duty (TDY) in non-combat situations.
Where available, connectivity is provided by broadband Internet connection. Where broadband
is not available, Internet connectivity is provided using an RBGAN terminal in conjunction with
RBGAN satellite service provided by Inmarsat. RBGAN’s theoretical bandwidth cap is 144
kilobits per second (kbps). The RBGAN service was available only within the footprint of the
Thuraya satellite (see Figure 1-1).
1-1
15 March 2006
Figure 1-1 RBGAN Legacy Coverage Footprint (in red)
RBGAN is now available over about one-third of the earth’s surface, since the launch of the I-4
satellite over the Indian Ocean. See Figure 1-2. In 2007, coverage will be world wide (see
Figure 4-4).
Figure 1-2 RBGAN Coverage Under I-4 (light area legacy coverage, dark area extended
coverage)
1-2
1.3
15 March 2006
SYSTEMS DESCRIPTIONS
1.3.1 EC2
1.3.1.1
EC2 Background
EC2 is in its Block 3 iteration and was approved by the Defense Information Systems Network
(DISN) Security Accreditation Working Group (DSAWG). Block 3 brings support for Internet
Protocol Security (IPSec) and the ability to connect from military aircraft equipped with
Inmarsat capability.
1.3.1.2
EC2 System Architecture
To reach back to the classified domain, the EC2 Block 3 suite creates a National Security
Agency (NSA) Type 1 encrypted tunnel embedded within either an IPSec Virtual Private
Network (VPN) tunnel using Advanced Encryption System (AES) 256-bit encryption, or a
mobile routing tunnel through the Internet/Non-secure Internet Protocol Router Network
(NIPRNet) to the home agent, which is the counterpart Cisco 3251 router on the host unclassified
network. Since the Cisco 3251 router can support either IPSec or mobile routing mode, the
traveling communications expert has the ability to select one mode or the other. One advantage
of the IPSec VPN tunnel over the mobile routing tunnel is that it uses a pre-shared key and
encrypts the IP information. Another is that, unlike mobile routing, IPSec does not require the
use of User Datagram Protocol (UDP) port 434, which is closed by default on DoD networks.
The devices used to create an NSA Type 1 encrypted tunnel are a pair of Sectéra® KG-235 InLine Network Encryptors (INE), one on the mobile kit and one on the host network.
Figure 1-3 shows all of the components of the mobile kit with its travel case. The small black
box at top left is the mobile router, essentially a Cisco 3251 router. The small appliance next to
it is the KG-235 INE, on top of which is a Linksys router. The laptop serves as the mobile client
and can be either classified or unclassified.
1-3
15 March 2006
Figure 1-3 Components of EC2 Block 3 Suite
Figure 1-4 presents a high-level depiction of classified data flow through a tunnel within a
tunnel. The wider cylinder represents the tunnel established between the two mobile routers
using either IPSec or mobile routing technology. Within that tunnel, the narrower cylinder
represents the encrypted tunnel between the two INEs.
Figure 1-4 Classified Data Flow
Figure 1-5 gives a better idea of data flow when an EC2 classified client without broadband
Ethernet access reaches back to the user’s home network. Figure 1-6, on the other hand,
emphasizes unclassified reachback using EC2.
1-4
15 March 2006
A more comprehensive description of EC2 Block 3 with detailed architecture renderings was
published in the EC2 Block 3 CONOPS found at
https://eportal.jsic.jfcom.mil/sites/EC2/Project%20Files/Block%203/EC2%20Block%203%20C
ONOPS.doc.
RBGAN Sample Classified Architecture Absent Broadband
Inmarsat
USJFCOM
I-3 Satellite
Internet
RBGAN
Terminal
Ground
Station
NIPRNet
Premise
Router
DISA NIPRNet
Gateway
Home Agent /
VPN Router
(Cisco 3251)
DHCP Router (Linksys)
Sectera
KG-235 INE
Mobile Router
(CISCO 3251)
ARP
Router
Sectera
KG-235 INE
SIPRNet
Classified Client
LIMS
JFCOM
EC2 Mobile Suite
Figure 1-5 Classified Data Flow with No Broadband Access
1-5
15 March 2006
Sample Unclassified EC2 Architecture Absent Broadband
Inmarsat Provided
JSIC
DISA NIPRNET
Gateway
Premise
Router
Thuraya Satellite
NIPRNet
VPN
Concentrator Firewall
Internet
RBGAN
Terminal
Ground
Station
e
IPs
PN
cV
el
nn
Tu
JSIC Home
Network
- Domain Controller
- E-Mail
- Video Server
- Portal/Doc Management
- IWS
- Home Drive
Unclassified
Client
Classified Client
Mobile Suite
Figure 1-6 Unclassified Reachback using EC2
1.3.2
1.3.2.1
Inmarsat
Inmarsat Background
Inmarsat was originally established as an intergovernmental organization (IGO) in 1979 to
provide global safety and other communications for the maritime community. Starting with a
customer base of 900 ships in the early 1980s, it grew to offer similar services to other users on
land and in the air; in 1999, it became the first IGO to be transformed into a private company.
Inmarsat, now a publicly traded company, supports links for phone, fax, and data
communications to more than 287,000 ship, vehicle, aircraft, and other mobile users.1
1
Inmarsat Web site: http://about.inmarsat.com/business/default.aspx?top_level_id=1&language=EN&textonly=False
1-6
1.3.2.2
15 March 2006
Inmarsat Satellites
The Inmarsat satellites are positioned in geostationary orbit. This means they follow a circular
orbit in the plane of the Equator at a height of 35,600 km, so they appear stationary relative to a
point on the Earth's surface. They are controlled from Inmarsat's headquarters in London,
England, which is also home to Inmarsat PLC, Inmarsat's parent company. London is also the
home to the small IGO, International Mobile Satellite Organization (IMSO), created to supervise
Inmarsat’s public-service duties to support the Global Maritime Distress and Safety System
(GMDSS) and satellite-aided air traffic control for the aviation community. Data on the status of
the Inmarsat satellites is supplied to the Satellite Control Center in London by four tracking,
telemetry, and control (TT&C) stations located at Fucino, Italy; Beijing, China; Lake Cowichan,
western Canada; and Pennant Point, eastern Canada. There are also backup stations at Eik,
Norway and Auckland, New Zealand.
Prior to December 2005, the Thuraya satellite was used for RBGAN services in the Middle East.
Since December 2005, RBGAN service has been operating on Inmarsat’s I-4 satellite over the
Indian Ocean (see Figures 1-1 and 1-2). The new BGAN service will be provided by the I-4
class. With the launch of BGAN, two new gateways, called Satellite Access Stations (SASs), are
being introduced. Both are owned by Inmarsat. The first, in Burum, The Netherlands, will be
operated by Inmarsat’s partner, Xantic; the other, in Fucino, Italy, will be operated by another
partner, Telespazio.
The Inmarsat I-4s, like their predecessor satellites, are equipped with a single global beam that
covers up to one-third of the Earth's surface, apart from the poles. Each satellite also generates
19 wide spot beams that provide continuous coverage across the same region for Inmarsat's
existing high-end services. New to the I-4s are an additional 228 narrow spot beams, designed to
form the backbone of Inmarsat's BGAN.
According to Inmarsat, compared to the I-3 satellites providing M4 service, the I-4 satellites
offer:
•
•
•
•
Greater call capacity than all five I-3s put together
60 times more power than any of its predecessors
12 times greater efficiency in its use of radio spectrum
16 times the capacity
1-7
•
15 March 2006
25 times the receiver sensitivity2
1.3.3
BGAN Service
BGAN supports both circuit-switched and packet-switched voice and data services. Inmarsat
publishes the following specifications for BGAN services.3
Standard IP service
• Variable bit rate service
• Background Class IP 4
• Up to 492 kbps (maximum bearer rate) – send and receive
Streaming IP service5
• Guaranteed bit rate service
• Available on demand
• Streaming Class QoS
• 32, 64, 128, 256 kbps – send and receive
Voice
• 4kbps circuit-switched voice service
• Calls made via a peripheral handset or headset
• Voicemail
• Supplementary services: call waiting, call barring, call hold, call forward
ISDN
• 64 kbps
• UDI/RDI
• Digital and Analogue
• Available on selected satellite terminals
Other Network Data
• Operating Spectrum – L-Band: 1.5 to 1.6 GHz
• Bearer bandwidth – 200 kHz
• Supported operating systems
– Windows – 2000, XP
2
Inmarsat Web site: http://about.inmarsat.com/satellites.aspx?top_level_id=3&language=EN&textonly=False
Inmarsat Web site: http://broadband.inmarsat.com/about/?language=EN&textonly=False
As defined within 3G industry standards
5
Streaming IP service is Inmarsat’s term for guaranteed bandwidth.
3
4
1-8
15 March 2006
– MAC – OS 9.2, OS 10.1
– Linux Red Hat 9
1.3.4 BGAN Terminals
1.3.4.1 BGAN Terminals Background
The RBGAN terminals, while functional on the I-4 satellites, are not able to support the
increased throughput of the I-4 generation, nor do they provide a wide array of features.
Inmarsat, therefore, has partnered with four manufacturers to produce a new generation of
portable satellite terminals. There are three classes of BGAN terminals:
Class 1 - for professional applications
• Used under extremely dusty, rainy, cold, or hot conditions
• Features full BGAN theoretical bandwidth of 492 kbps uplink/492 kbps downlink
• Streaming possibilities of up to 256 kbps guaranteed bandwidth6
Class 2 - the multi-user terminal for professional and semiprofessional uses
• Light and focused on user-friendliness
• Rugged and capable of outdoor use under most conditions
• Theoretical bandwidth of 464 kbps uplink/448 kbps downlink
• Streaming possibilities up to 128 kbps guaranteed bandwidth
• Has more inter-connection features than Class 3 and can be shared by several users
Class 3 - the single-user terminal
• Best suited for light users
• Has fewer features and accessories
• Not waterproof
• Focused on cost-efficiency
• Theoretical bandwidth of 384 kbps uplink/240 kbps downlink and streaming possibilities
up to 64 kbps guaranteed bandwidth7
The HNS 9201 terminal represented Class 1 in testing while the Thrane & Thrane Explorer 500
and the Nera WorldPro-1000 represented Classes 2 and 3, respectively. The HNS 9101, not to
6
7
Guaranteed bandwidth in this context refers to a tiered premium service to be offered by Inmarsat, as contrasted to the basic service of shared bandwidth.
http://www.danimex.com/Default.aspx?ID=238
1-9
15 March 2006
be confused with the 9201, and commonly known as the legacy RBGAN terminal, was also
tested.7
Inmarsat contributed funding to the companies developing the new terminals to guarantee that
the products meet Inmarsat requirements, and to ensure interoperability of a single common
man-machine interface (MMI) for all the new terminals. Inmarsat itself developed the MMI,
called BGAN LaunchPad.
The HNS 9201 terminal was still in beta during testing, whereas the Thrane & Thrane and Nera
terminals were in production and commercial use. A fourth new terminal, the Class 3 Addvalue
(Wideye™) Sabre™ , was not ready for testing and is expected to be released for sale in the
second half of 2006.
1.3.4.2
BGAN Terminals’ Descriptions
There are differences specific to the terminals in addition to the class differences. Table 1-1
compares the features and specifications of the BGAN terminals.
Table 1-1 BGAN Terminals Descriptions
Model
HNS 9101 (RBGAN) Nera WorldPro
1000
Size
300 x 240mm
(2.8kgs)
Standard Up to 144kbps (send
IP
& receive)
Stream- N/A
ing IP
ISDN
N/A
Voice
Via VoIP
Thrane Explorer 500
200 x 140 x 40 mm 217 x 217 x 52 mm
(<1 kg)
(<1.5 kg)
Up to 384/240
Up to 464/448 kbps
kbps (receive/send) (receive/send)
32 & 64 kbps (send 32, 64 and 128 kbps
& receive)
(send & receive),
Multiple IP streaming
sessions
simultaneously
Not available
Via USB
Via Nera
WorldSet, ISDN
phones, Bluetooth
HNS 9201
345 x 275 x 50 mm (2.8
Kg)
Up to 492 kbps (receive
& send)
32, 64, 128 and 256 kbps
(send & receive),
Multiple IP streaming
sessions simultaneously
1 x 64 kbps (3.2 kHz
audio, RDI & UDI)
Via RJ11 or Bluetooth Via ISDN handset
handset; 3.1 kHz audio
1-10
15 March 2006
handset
Data
USB, Bluetooth,
USB, Bluetooth
interfaces Ethernet
(Ethernet planned
for 2nd half of
2006)
Ingress IP 54 - Protection
IP44 - Protection
Protect- from dust that would from entry by
ion
interfere with
objects 1mm in
equipment operation diameter/thickness
and from splashed
and from splashed
water
water
Battery 1h full power
Transmit: 5 hours,
Life
transmit and receive, Stand-by: 36 hours
up to 24h standby
Input
7.2 to 8.4 Volts DC
Voltage
Operating -10 °C to +55 °C (14
Environ- °F to 131 °F)
ment
95% Relative
humidity at 40 °C
(104 °F)
Max.
Radiated
Power
(EIRP)
Other
Key
Features
Options
Unknown
Web page based
graphical user
interface accessible
via standard web
browser.Wizard setup guide for sample
start-up and set-up
operations
External antenna,
carry case and
charger and the
capability to connect
to a cigarette lighter
socket in motor
vehicles for
recharging.
USB, Bluetooth,
Ethernet
USB, Ethernet, WLAN
802.11b (up to 100m),
WEP, DHCP
IP54 - Protection from
dust that would
interfere with
equipment operation
and from splashed
water
Transmit: 1.5 hours @
144 kbps, Stand-by: 36
hours
IP55 - Protection from
dust that would interfere
with equipment
operation and from
jetting water
10.8-15.6 Volts DC 10-16 Volts DC
Transmit: 162 MB via
Ethernet, Receive: 864
MB via Ethernet, Standby: 36 hours
11.1 Volts DC
-20 to +55C from
external DC power
or battery, Relative
humidity 95% noncondensing at
+40C
+10dBW
-25 to +55C from
external DC power, 0
to +55C from battery,
Relative humidity 95%
non-condensing at
+40C
+15.1dBW
+20dBW
Terminal can be
separated into two
parts, for indoor &
outdoor use, with
no need for an
external antenna.
The Thrane terminal
features its built in web
server interface for
your PC.
The HNS terminal
provides the highest
bandwidth and WLAN
connectivity.
Voice handset,
Bluetooth handset,
car charger, solar
charger, pole
mount kit, spare
battery, DC/DC
adaptor, soft
carrying bag
Bluetooth handset, car
charger, solar charger,
external antenna, pole
mount kit, spare
battery, soft carrying
bag
Third party handsets, car
charger, solar charger,
fix mount kit, spare
battery
1-11
-25 to +60C from
external DC power, -5 to
+55C from battery,
Relative humidity 95%
non-condensing at +40C
1.3.4.3
15 March 2006
MMI
Inmarsat has developed a user interface called BGAN LaunchPad, compatible with each of the
new BGAN terminals, though not with the RBGAN terminal. Figure 1-7 shows a control panel
in LaunchPad from which a terminal can be managed and monitored.
Figure 1-7 LaunchPad Control Panel
The test team used LaunchPad Version 2.3.1 to manage the new BGAN terminals. To manage
the RBGAN terminal, the team accessed the terminal’s web-based user interface using
Microsoft® Internet Explorer.
1-12
15 March 2006
1-13
2
TEST OBJECTIVES
2.1
PRIMARY OBJECTIVES
15 March 2006
The following were the primary objectives of the BGAN tests:
1. Confirm that the various BGAN terminals perform the same EC2 functions with the new
I-4 satellites that the RBGAN terminal performs on the older Thuraya satellite, using both
NIPRNet and Secret Internet Protocol Router Network (SIPRNet).
2. Confirm that the RBGAN terminal performs the same EC2 functions on the new I-4
satellite that they perform on the older Thuraya satellite using both NIPRNet and
SIPRNet.
3. Compare the various BGAN terminals’ performances on the I-4 satellite to each other
and also to the RBGAN terminal’s performance on the I-4 satellite.8
4. Determine what, if any, extended capabilities that BGAN technology can provide EC2.
2.2
CONTINGENCY OBJECTIVES
Depending on resources, scheduling, and availability it was determined to:
5. Evaluate the operability of Secure Terminal Equipment (STE) using the various BGAN
terminals.
6. Evaluate the operability of Future Narrow Band Digital Terminal (FNBDT) secure voice
using the various BGAN terminals.
7. Evaluate the operability of Voice over Secure IP (VoSIP) using the various BGAN
terminals, in conjunction with the Defense Information Systems Agency (DISA)
Expanded VoSIP.
The RBGAN terminals are limited to 144 kbps, as is the service provided by the Thuraya satellites. The value, then, in including the RBGAN
terminal for testing on the I-4 satellite is two-fold. Its bandwidth restriction provides a useful approximation of the legacy RBGAN/I-3 service.
Second, Inmarsat includes the RBGAN terminal in its lineup of BGAN terminals.
8
2-1
15 March 2006
2-2
3
TEAM MEMBERS AND ROLES
3.1
JSIC TEST TEAM MEMBERS
15 March 2006
Maj James V. Knapp, USMC
James R. (Bob) Dunn, CTR
David Jones, CTR
Tracy Carroll, CTR
Mike Hron, CTR
Thomas Wasenius, CTR
Paul Outlaw, CTR
Justin Schauf, CTR
Roberto Matos, CTR
EC2 Project Lead
Test Plan Author
Contract Lead
SME
Project Engineer
Network Support
Network Support
Systems Support
Systems Support
Maj Knapp, as Project Lead, is responsible for all aspects of EC2. He was the primary liaison
with Inmarsat, Inc. officials and with team members from EUCOM who conducted testing in the
classified environment. With David Jones and Tracy Carroll, he conducted testing in
unclassified environments in England, Bahrain, and Australia.
James R. (Bob) Dunn is a Subject Matter Expert (SME) and the primary author of the test plan.
Tracy Carroll wrote the procedures to meet the objectives of the test plan. David Jones, along
with Tracy Carroll, refined the test plan in the lab and exposed network and application issues
prior to overseas testing, then worked with the Enterprise Architecture Operations (EAO) team
members to correct them. They conducted testing with Maj. Knapp in London, Bahrain, and
Australia. They were responsible for network traffic data collection and assimilation and are the
primary authors of this report.
Mike Hron coordinated support among the JSIC Directorates to prepare for and execute the tests.
He also provided support for application testing and data collection.
Thomas Wasenius and Paul Outlaw provided network support to prepare for and conduct the
tests.
Justin Schauf and Roberto Matos built and supported services in the unclassified experimental
home network, Black Area Network Distribution (BAND).
3-1
3.2
15 March 2006
EUCOM TEST TEAM MEMBERS
CW2 Kevin Martin
SSG Brian Humann
SSG James Wagner
SSG Paul Allen
The EUCOM test team performed the classified testing. CW2 Martin is responsible for EC2
implementation by the EUCOM Commander’s communications team at Mons, Belgium and
Stuttgart, Germany. In BGAN testing, SSG Humann tested voice calls using the HNS and
Thrane & Thrane terminals. SSG James Wagner and SSG Paul Allen tested secure data
transmission using the KG-235 INE.
3-2
15 March 2006
4
UNCLASSIFIED TESTING
4.1
UNCLASSIFIED TEST ENVIRONMENTS
The unclassified environment comprises:
• The home network and services
• The travel suite, a set of satellite terminals, laptop clients, and accessories that traveled
with the test team to each of the three locations
• The network path between the travel suite and the home network
• The geographic locations in London, England; Manama, Bahrain; and Perth, Australia
4.1.1
Unclassified Home Network and Services
The home network used for unclassified reachback is the BAND enclave at the JSIC, the primary
purpose of which is experimentation. It is a Windows 2003 Active Directory domain. It has
access to the Internet and NIPRNet and provides services typical of a user’s home network. The
following services on the BAND were used for this test.
•
•
•
•
•
•
•
E-mail via Microsoft Exchange
Streaming video
File Transfer Protocol (FTP)
NIPRNet and Internet access
Synchronous collaboration via InfoWorkSpace (IWS)
VTC using Microsoft NetMeeting
Asynchronous collaboration using then JSIC SharePoint 2003 portal and document
management system via NIPRNet
4.1.2
4.1.2.1
The Unclassified Travel Suite
Satellite Terminals in the Travel Suite
Following is information specific to each terminal in the travel suite:
HNS 9201
Manufacture Name:
Software Version:
Firmware:
ASIC:
Hardware Model:
IMEI Number:
IMSI Number:
MSISDN Number(s):
MMI Version:
Hughes Network Systems
Software: 3.4.2.1, 12/17/2005
BGAN FW 8.01 10/19/05
6
BGAN USER TERMINAL, HNS 9201, Ver 2
004400-00-330248-4
901112112100689
Not available
2.3.1
Explorer 500
Manufacturer Name: Thrane & Thrane
4-1
Software Version:
Hardware Model:
IMEI Number:
IMSI Number:
MSISDN Number(s):
MMI Version:
15 March 2006
1.00-1
EXPLORER 500
353150000000618
901112112100688
Not Available
2.3.1
WorldPro 1000
Manufacture Name: NERA SatCom AS, Norway
Software Version:
PUT SW modules:
IDU CSW Version: 1.11.9T2
ODU DSP Version: C1:1.3.39 D1:1.4.19
IDU FPGA Version: C1:1.2.8 D1:1.3.2
BT Version: 0510281736
Boot Version: 1.4.6
Hardware Model:
Inmarsat BGAN type PUT, product version:
IMEI Number:
353735000001242
IMSI Number:
901112112100687
MSISDN Number(s): Not Available
MMI Version:
2.3.1
RBGAN
Software Version:
IOR System Information Version :
AOR System Information Version :
Interface Mode:
Public Network IP Address:
Private Satellite Modem IP Address:
APN Value:
Satellite Modem IMEI:
Satellite Modem MAC Address:
4.1.2.2
3.11.0, 06/09/2005
2
2
Ethernet
10.20.1.49
192.168.128.100
bgan-r.inmarsat.com
350940-00-006257-3
00:80:ae:e5:18:71
Laptop Clients and Accessories
Each of the two clients used to reach back to the home network was a Panasonic CF-29
Toughbook equipped with:
Intel® Pentium® M Processor LV 778:
2MB L2 cache
Processor speed 1.40GHz
400MHz FSB
80GB Hard Drive
512MB SDRAM (DDR2)
Specifications are detailed in Appendix A.
JSIC used a standard load on the clients which included:
4-2
15 March 2006
OS: MS WIN XP Pro, Ver 2002, SP2
Machine Settings:
Standard default settings. Virtual Memory Page File size: 756 MB
Applications:
MS Office 2003 Suite, SP2
MS Internet Explorer 6.0.29002180 SP2
All accessories and utilities loaded with the OS in a standard default installation
FormFLow 2.24 Filler
Intel PROSet Wireless
Placeware add-in for PowerPoint, media plugin, and snapshot plugin
Quicktime 7
Realplayer V10
SnagIt 6
Symantic Antivirus, Program 10.0.1.1000
Winzip 9.0 SR1
Adobe Acrobat Reader 7.0
Real Player
EPSQ 2.2 (US DOD Security Clearance application)
Military Evaluation Programs (NAVFIT 98A, ICS Viewer 6.0, PES Application)
InfoWorkSpace 2.5.1.3
After the standard operating system and software load, JSIC also loaded the following
applications:
Cisco VPN Client 4.6.02.0011
Creative Webcam ver 2.05.4
BGAN LaunchPad ver 2.3.1
Nera WorldPro 1000 USB Drivers (Nera009)
Hardware accessories included a headset with earphones and microphone, and Creative Labs
WebCams for Notebooks, Model PD1170.
4.1.3
Unclassified Network Architecture
Mobile routers and INEs are not required for reachback to an unclassified home network. For
the BGAN tests, JSIC installed Cisco VPN Client 4.6.02.0011 on each laptop to establish tunnels
which terminated at the VPN concentrator, Cisco VPN 3015, on the home network (see Figure 41).
4-3
15 March 2006
EC2 Unclassified BGAN Test Architecture
Inmarsat Provided
I-4 Satellite
DISA NIPRNET
Gateway
JSIC
To JSIC XNET and Portal
Premise
Router
Cisco VPN
Concentrator
Packet
Seeker
NIPRNet
Internet
Satellite
Terminal n
I-4 Ground
Station
ec
IPs
NT
VP
Firewall
u
l
nne
JSIC BAND
• Domain Controllers
• E-Mail
• Streaming Media
• FTP Server
• IWS
• Shared Drive
• VTC
EC2 Unclassified
Client
w / software-based Cisco
VPN client (mobile router
and INE not needed for
unclassified reachback)
Figure 4-1 Unclassified Network Architecture
Figure 4-1 depicts the network architecture used for unclassified testing. The laptop client
requested and received a private IP address from the satellite terminal. The satellite terminal
used the satellite’s global beam for its positioning fix; the regional beam, which is 1/19th of the
global beam, to register a connection; and a narrow spot beam, 1/228th of the global beam, for
the established session. Data passed from the satellite through the Inmarsat ground station where
it entered the Internet. To complete reachback to the JSIC BAND, the data passed through the
NIPRNet.
The logical connection was different. The client laptop was a member of the JSIC BAND
Windows 2003 Active Directory and appeared at the JSIC network as a local node. This was
accomplished through the encrypted IPSec VPN tunnel, represented diagonally across Figure 42, between the laptop and the VPN concentrator. The concentrator assigned the laptop a local
address on the network of which the concentrator itself is a member, and whose network
addresses are allowed to pass through the firewall for communication with the BAND network.
Data from the laptop exited the tunnel at the concentrator where it was decrypted and passed into
the BAND. The laptop client then accessed files and programs on the BAND exactly like a
BAND client sharing physical space with the rest of the BAND.
JSIC placed a network capture device, PacketSeeker, made by the Packeteer Corporation,
described in Section 4.1.2, outside the firewall, in the same network with the VPN concentrator
and firewall, to capture network data for analysis.
4-4
4.1.4
4.1.4.1
15 March 2006
Unclassified Data Flow
Data Flow Accessing BAND Services
The placement of PacketSeeker is such that, when the client in the travel suite uses services on
the BAND, all traffic passes through it. Inbound traffic passes from the client through the
tunnel, the VPN concentrator, PacketSeeker, the firewall, and then into the BAND. Outbound
traffic follows the same path in reverse from the BAND to the laptop client.
4.1.4.2
Data Flow Accessing the Internet via Reachback
Browsing the Internet, requests from the laptop client travel inbound as far as the BAND where
Domain Name Service (DNS) resolution occurred. At this point, the request traveled a different
path from the firewall back out to the Internet and bypassed PacketSeeker. The dotted lines
represent the path of the request from the client (see Figure 4-2).
Internet Request in BGAN Unclassified Test Architecture
Inmarsat Provided
I-4 Satellite
DISA NIPRNET
Gateway
JSIC
Premise
Router
Cisco VPN
Concentrator
Packet
Seeker
NIPRNet
Internet
I-4 Ground
Station
ec
IPs
NT
VP
u
EC2 Unclassified
Client
represents a
request from the client to the
Internet.
DN
SR
JSIC BAND
• E-Mail
• Streaming Media
• FTP Server
• IWS
• Shared Drive
• VTC
eso
lutio
n
Satellite
Terminal n
Firewall
l
nne
Figure 4-2 Internet Request
The response path from the Internet to the client is almost identical, in reverse, to the request
from the client to the Internet. The main difference is that the DNS resolution is not needed so
the response does not flow into the BAND where the local DNS server is. Figure 4-3, contrasted
with Figure 4-2, illustrates the difference in data flow between a request to the Internet from the
laptop and the response from the Internet to the laptop.
4-5
15 March 2006
Internet Response in BGAN Unclassified Test Architecture
Inmarsat Provided
JSIC
DISA NIPRNET
Gateway
I-4 Satellite
Premise
Router
Cisco VPN
Concentrator
Packet
Seeker
NIPRNet
Internet
Satellite
Terminal n
I-4 Ground
Station
ec
IPs
EC2 Unclassified
Client
Firewall
NT
VP
el
unn
JSIC BAND
represents a
response from the Internet to
the client.
• E-Mail
• Streaming Media
• FTP Server
• IWS
• Shared Drive
• VTC
Figure 4-3 Internet Response
4.1.4
Geographic Locations
Figure 4-4 depicts the coverage areas of the three I-4 satellites. JSIC only tested the F1 I-4, over
the Indian Ocean. The F2, which covers the Continental United States (CONUS), will be
available for service by mid-2006. Inmarsat reports that the F3 will be launched in 2007.
4-6
15 March 2006
*
London, UK
*
Manama, Bahrain
Indian
Ocean
*
Perth, Australia
Figure 4-4 Footprints of Satellites F1, F2, and F3
JSIC decided to test locations on the edge of the coverage footprint (London, UK and Perth,
Australia) as well Manama, Bahrain which is near the middle. The Global Positioning System
(GPS) information for each city is described in Section 1.
London, UK:
Latitude: 51-32’N
Longitude: 0-5’ S
Nearest City: London 0958
Recommended Antenna Angle: 10 degrees
Recommended Compass Direction: ESE 109 degrees
Manama, Bahrain:
Latitude: 26º14'N
Longitude: 50º35'E
Nearest City: Ad Dammam
Recommended Antenna angle: 61º
Recommended Compass direction: SSE (149º)
4-7
15 March 2006
Perth, Australia:
Latitude: 31º58'S
Longitude: 115º52'E
Nearest City: Perth
Recommended Antenna angle: 26º
Recommended Compass direction: WNW (291º)
4.2
UNCLASSIFIED TEST METHODOLOGY
4.2.1
Unclassified Test Procedures
JSIC conducted tests for each terminal at every location using procedure subsets titled “Day 1”
and “Day 2.” Testers manually recorded the results and identified them using the location and
terminal name. For example, London Day 1 Nera, London Day 1 Thrane & Thrane, London
Day 1 Nera, and London Day 1 Hughes.
Appendix A contains Day 1 test procedures while Appendix B represents Day 2. Where
objective results could not be recorded, JSIC identified the results as Pass, Fail, or Marginal.
4.2.2
Unclassified Data Collection
While testers manually recorded results, they used PacketSeeker to collect dynamic network
traffic data. The device comprises a proprietary hardware appliance and operating system. The
appliance is a PacketSeeker 2500, Serial # 025-10011549, and the software operating system is
PacketWise 6.2.1. Hereafter, PacketSeeker refers collectively to the hardware appliance and
operating system.
4.2.3
Unclassified Methodology per Objective
All of the methods described below are prescribed in more detail in the procedure subsets
entitled Day 1 and Day 2, Appendices B and C.
4.2.3.1 Objective 1
Confirm that the various BGAN terminals performs the same EC2 functions with the new I-4
satellites that the RBGAN terminal performs on the older Thuraya satellite.
Methods
Use of each BGAN terminal to employ services currently employed with RBGAN: e-mail, IWS,
and document access from home network.
4.2.3.2 Objective 2
Confirm that the RBGAN terminal performs the same EC2 functions on the new I-4 satellite that
it performs on the older Thuraya satellite.
4-8
15 March 2006
Methods
Use of the RBGAN terminal with the I-4 satellite to employ services currently employed with
RBGAN using the I-3 satellite: e-mail, IWS, and document access from home network.
4.2.3.3 Objective 3
Compare the various BGAN terminals’ performances on the I-4 satellite, both to each other and
also to the RBGAN terminal’s performance on the I-4 satellite.
Methods
• Analysis of results from the methods associated with Objectives 1 and 2.
• Analysis of performance results of all terminals in the following activities:
• Bandwidth tests using numion.com
• From a client connection directly to the Internet from the I-4 ground station, as shown
in Figure 4-1
• From a client connection through the VPN tunnel reaching back to the home network,
back out to the NIPRNet, and then to the Internet, as described in Section 4.2.3 and
Figures 4-2 and 4-3
• FTP transfers
• Document management using the JSIC portal and document management system
• Receiving streaming media (i.e., video with sound) from media server
• VTC using Microsoft NetMeeting
4.2.3.4 Objective 4
Determine what, if any, extended capabilities that BGAN technology may provide EC2.
Methods
Analysis of results of methods associated with Objective 3; compare the various BGAN
terminals’ performances on the I-4 satellite, both to each other and also to the RBGAN
terminal’s performance on the I-4 satellite. When the RBGAN terminal fails overall in its
attempts to use a given service, while a BGAN terminal passes overall in its attempt to use that
same service, then that service will be defined as a potential extended capability for EC2.
4.3
UNCLASSIFIED DATA AND ANALYSIS
While the field test results have the advantage of reflecting tester observations in the real world,
they do not have the controls afforded when using a laboratory setting. Therefore, performance
results may vary by location, time of day, amount of Internet traffic at a given time, number of
users on a spot beam, and other factors.
4-9
15 March 2006
Throughout the test period, JSIC was unable to gather some data due to equipment issues. For
example, a Subscriber Information Module (SIM) card failed which negated JSIC’s ability to test
the RBAN terminal in Bahrain. The Nera WorldPro 100 failed in Bahrain but worked in
Australia, and later in the UK after a firmware upgrade. The HNS 9201, the only product tested
while still in beta format, did not work in Australia because it attempted to register on the wrong
regional satellite beam. The Thrane & Thrane Explore 500, when using Network Address
Translation (NAT), could not establish a tunnel with the Cisco concentrator at JSIC from
Bahrain or Australia. In Modem Mode, that is, when the client laptop was given a public IP
address rather than a private address via NAT, the Thrane & Thrane successfully established a
tunnel with the concentrator at JSIC.
Finally, numion.com, a respected site for measuring throughput, changed its methods both of
measuring and reporting data while JSIC was conducting its field tests. Thus, JSIC was unable
to compare and aggregate data reported from the site as described in the test plan.
Fortunately, JSIC collected a high volume of data during the three-week test which enabled them
to make some definitive conclusions.
4.3.1
Objective 1
Confirm that the various BGAN terminals perform the same EC2 functions with the new I-4
satellites that the RBGAN terminal performs on the older Thuraya satellite.
Result
Each terminal received a score of Pass in reaching back to the JSIC home network, browsing the
Internet, participating in IWS sessions, exchanging e-mail with 3 MB attachments, and managing
documents.
Terminal
Score
Nera WorldPro-1000
Thrane & Thrane Explorer 500
HNS 9201
Pass
Pass
Pass
4.3.2 Objective 2
it performs on the older Thuraya satellite.
Result – Pass
The HNS 9101 RBGAN terminal received a score of Pass in connecting to the I-4 satellite and
using the services described above.
4-10
15 March 2006
4.3.3 Objective 3
also to the RBGAN terminal’s performance on the I-4 satellite.
Result
All of the terminals received the subjective score of Pass using basic services from the home
network – e-mail, IWS, and document management. As expected, speeds varied among the
terminals, and there was an acceptable delay for IWS and document management on all four
terminals.
Each of the four terminals took minutes to synchronize Outlook folders with the Exchange
server, transferring a total of 3 MB to the laptop client. Typically, latency was well in excess of
1500 milliseconds (ms), translating into a round trip delay of well over three seconds. The
testers used the full Outlook client, that is, “thick client,” installed on the laptop to communicate
with the home network’s Exchange server. Unlike the “thin client” Outlook Web Access
(OWA), the full Outlook client and Exchange server are designed to work together in a Local
Area Network (LAN) with low latency. Typically, the performance is low when the latency is
high.
Figure 4-5 illustrates the 1 MB files transferred at an average rate of 27 kbs using the Thrane &
Thrane, 17 kbs using both the HNS 9201 and the Nera, and 11 kbs using the RBGAN. The 5MB
files transferred at almost identical rates.
4-11
15 March 2006
1MB FTP times, UK
35
30
25
HNS
20
Thrane
Kbytes/sec (KBps)
Nera
15
RBGAN
10
RBGAN
Nera
5
Thrane
0
HNS
1
2
1:Put 2:Get
Figure 4-5 FTP 1MB Files
Measured file transfers proved to be a differentiator among the terminals. The test procedure
called for a 1 MB file and a 5 MB file to be transferred in succession from the client to a server
on the home network and then back to the client. The testers executed, timed, and documented
transfers with automated scripts using File Transfer Protocol (FTP). Though testing of the
Thrane & Thrane terminal was limited to London, the transfer rate, which was dramatically
superior to the other terminals at the same location, is noteworthy.
Table 4-1 depicts FTP results from all three locations.
4-12
15 March 2006
Table 4-1 FTP Results
Test
Locale
1 MB FTP
Kbytes per sec for each terminal
RBGAN
Nera
Thrane
HNS
UK
BAH
AUS
11.05
15.23
30.9
10.41
24.79
10.9
19.89
UK
BAH
AUS
11.67
11.4
23.77
14.89
19
11.26
22.96
UK
BAH
AUS
10.94
17.02
31.07
13.93
19.6
10.7
9.93
UK
BAH
AUS
11.94
21.44
20.66
11.65
20.87
11.53
19.91
Put
Get
5 MB FTP
Put
Get
Average 1 MB rate by
terminal
Stnd Dev
Average 5 MB rate by
terminal
Stnd Dev
11.22
17.37
27.335
17.2725
0.3343651
5.0930999
5.041671
4.094148
11.2775
0.5627536
17.075
5.1037405
25.865
5.220581
16.5125
4.960647
JSIC testers noted a range of scores for streaming video (see Table 4-2). While the HNS had
superior delivery of streaming media from a server in the home network to the remote client, the
Thrane & Thrane and RBGAN terminals received a failing score overall. JSIC rated the Thrane
& Thrane performance as Marginal at 148 kbs, the lowest transfer rate from the server while the
RBGAN received a score of Fail. The Nera received an overall score of Pass. The HNS was the
only terminal to pass data at rates of 282 kbs and 340 kbs; it also passed data at a rate of 548 kbs.
Table 4-2 Streaming Video Scores
Streaming Media
Overall Score
148kbs
282kbs
340kbs
548kbs
4.3.4
RBGAN
Nera
Thrane
HNS
Fail
Fail
N/A
N/A
N/A
Pass
Pass
Marginal
Fail
N/A
Fail
Marginal
Fail
N/A
N/A
Pass
Pass
Pass
Pass
Marginal
Objective 4
Determine what, if any, extended capabilities that BGAN technology can provide EC2.
Result
BGAN, over RBGAN, provides the extended capabilities of VTC and streaming media
(streaming video and VoIP).
4-13
15 March 2006
Streaming Media
The RBGAN terminal failed to satisfactorily receive streaming media despite setting the media
server at its lowest transmission setting of 148 kbs. Therefore, JSIC gave it an overall score of
Fail. The Thrane & Thrane received an overall score of Fail, but the Nera and HNS terminals
received an overall score of Pass for Streaming Media performance. When a terminal failed at a
given rate, JSIC did not continue testing at the next higher rate.
VTC
Using Netmeeting, Microsoft’s implementation of VTC, the RBGAN terminal delivered
acceptable synchronous audio and video collaborative capability in London, but could not
deliver coherent audio or video in Perth; its overall VTC score is Fail. The HNS and Thrane &
Thrane terminals, however, provided high quality VTC capability using the BGAN technology
with Netmeeting (see Table 4-3). Netmeeting also offers Chat and Whiteboard functions, which
each terminal delivered well.
Table 4-3 VTC Scores
VTC Overall
Score
Netmeeting
Chat:
Whiteboard:
VoIP:
Video:
RBGAN
Fail
Nera
Fail
Thrane
Pass
HNS
Pass
Pass
Pass
Fail
Fail
Pass
Pass
Fail
Fail
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
4-14
15 March 2006
This page intentionally left blank
.
4-15
15 March 2006
5
CLASSIFIED TESTING
5.1
CLASSIFIED TEST ENVIRONMENTS
The EUCOM Commander’s Communications team conducted the classified testing. Unlike
unclassified reachback, classified reachback requires either an IPSec VPN tunnel using AES
256-bit encryption, or a mobile routing tunnel. Each solution originates from the mobile router,
a Cisco 3251, at the EC2 kit. It then moves through the Internet/NIPRNet to the home agent,
which is the counterpart Cisco 3251 router, on the host unclassified network. The EUCOM team
used the mobile routing solution in the BGAN tests.
The EUCOM team tested the HNS 9201 and the Thrane & Thrane Explorer 500, the only
terminals capable of secure telephony.
5.2
CLASSIFIED METHODS AND RESULTS PER OBJECTIVE
5.2.1 Objective 1
Confirm that the various BGAN terminals perform the same EC2 functions with the new I-4
satellites that the RBGAN terminal performs on the older Thuraya satellite, using SIPRNet.
Method
The EUCOM Commander’s communications team used the Transmission Control
Protocol/Internet Protocol (TCP/IP) reachback ability for most e-mail. They used a laptop client
with a full version of Outlook to reach back to the Exchange e-mail server on the EUCOM home
network.
Result
The Outlook client received a score of Pass using both the HNS 9201 and Thrane & Thrane
Explorer 500 terminals.
5.2.2 Objective 2
it performs on the older Thuraya satellite using both NIPRNet and SIPRNet.
Method
The EUCOM team already used the RBGAN terminal operationally with the new I-4 satellite.
Result
Pass
5-1
15 March 2006
5.2.3 Objective 3
also to the RBGAN terminal’s performance on the I-4 satellite.9
Method
The testers used e-mail to download file attachments of various sizes to the client laptop.
Result
The testers noted “The Thrane Explorer 500 and the Hughes HNS 9201 terminal had very similar
performance in our testing through the EC2.”
Observations
HNS 9201
Noticed that download speeds were impacted when making Integrated Services Digital Network
(ISDN) calls. From ~25KB/s to ~16KB/s when calls were made.
Most large file downloads were successful.
Thrane & Thrane Explorer 500
• When registering with the network with the LaunchPad application, the program seemed to
hang. Occasionally
• When registered and standard data connection opened, testers could not access the Internet.
Occasionally
• Testers noticed significant increase in response times in a continuous ping when the
terminal was plugged in and a noticeable decrease in time when operating on battery
power. A ‘Power Supply Error’ message was displayed on the LCD screen of the terminal.
Could not be repeated.
• Downloads of large files would fail after 15-20MB of that file being downloaded.
Repeatable
• Transfer rates would vary greatly during a download. Peak at 60KB/s, drop to ~13KB/s,
plateau ~40KB/s for brief periods.
5.2.4 Objective 4
Determine what, if any, extended capabilities that BGAN technology can provide EC2.
9
The RBGAN terminals are limited to 144 kbps, as is the service provided by the I-3 satellites. The value, then, in including the RBGAN terminal for testing on the I-4 satellite is two-fold. Its
bandwidth restriction provides a useful approximation of the legacy RBGAN/Thuraya service. Second, Inmarsat includes the RBGAN terminal in its lineup of BGAN terminals.
5-2
15 March 2006
Method
Experiment with secure telephony. See Section 5.2.5, Objective 5.
5.2.5 Objective 5
Depending on resources, scheduling, and availability of EUCOM’s secure telephone devices,
JSIC would:
• Evaluate the operability of STE using the various BGAN terminals.
• Evaluate the operability of FNBDT secure voice using the various BGAN terminals.
• Evaluate the operability of VoSIP using the various BGAN terminals, in conjunction with
the DISA Expanded VoSIP.
Due to timing and availability EUCOM’s secure telephone devices, JSIC attempted only the first
of the three contingency objectives.
STE
Background
Secure voice over traditional Inmarsat ISDN service and RBGAN service was successful
although not very robust. Users normally made secure voice calls using the STU-III mode or
FNBDT mode at a reduced data rate. When making a secure voice call, users had to suspend
data transfers until the phone call was completed. As part of the BGAN test, testers attempted
STE calls to determine if BGAN service and terminals provided sufficient bandwidth to conduct
an STE secure voice call in STE mode (64 kbps) while they maintained data communications.
Method
Attempt STE voice calls between the STE equipment, connected in succession to each of the two
BGAN terminals, and GSM, SGSM, and other STE equipment.
Result
The EUCOM team successfully completed secure voice calls using the STE in STE mode talking
to STE and STU-III secure voice terminals. They placed the calls from the BGAN terminal side
as well as from the land-based office environment and successfully maintained simultaneous
voice and data sessions. The only failure occurred when the team used an STE to call a Secure
GSM cell phone. In that instance, the SGSM phone interpreted the call as a Fax call and
prevented the secure voice call from being completed. While there were some inconsistencies,
JSIC rated both BGAN terminals as successful (see Appendices D and E) in tests from London.
Subsequent to the London tests, the EUCOM team was successful operationally in Afghanistan,
using the STE with the HNS 9201 to routinely conduct simultaneous voice and data sessions.
5-3
15 March 2006
The EUCOM team also found in Afghanistan that when using the HNS BGAN terminal, the
Black Box MiniBridge was not needed because the unclassified laptop could be interfaced
directly to the BGAN terminal. The purpose of the MiniBridge is to translate the Ethernet signal
to synchronous serial data. A data connection using STE with a legacy M4 terminal for satellite
access requires a Black Box MiniBridge between the laptop and the STE.
5-4
15 March 2006
5-5
15 March 2006
6
CONCLUSIONS AND RECOMMENDATIONS
6.1
CONCLUSIONS
BGAN extended the EC2 capability set with VTC and streaming media, which is streaming
video with VoIP. Secure voice is more consistent and robust with BGAN compared to
traditional Inmarsat ISDN service. Less equipment is required using secure voice with HNS
9201 and Thrane & Thrane Explorer 500 terminals, as there is no longer a need for a bridge
between the laptop and STE telephone to convert the Ethernet signal to synchronous serial data.
6.2
RECOMMENDATIONS
• Consider BGAN technology in place of RBGAN when fielding new EC2 kits.
• Consider upgrades of existing EC2 kits from RBGAN to BGAN.
• Consider using EC2 in CONUS, South America, and other new coverage areas when
service becomes available from the second Inmarsat I-4 satellite in April 2006.
• Conduct a cost/benefit analysis of BGAN technology to include both the shared bandwidth
and dedicated bandwidth services offered by Inmarsat.
• Implement BGAN as a replacement for the legacy M4 service, both terrestrial and aboard
aircraft, due to price and performance.
6-1
15 March 2006
6-2
15 March 2006
APPENDIX A – MANUFACTURER SPECIFICATIONS FOR PANASONIC CF-29
TOUGHBOOK
DURABILITY FEATURES
• Designed using MIL-STD-810F test procedures
• Full magnesium alloy case with handle
• Moisture- and dust-resistant LCD, keyboard and touchpad
• Sealed port and connector covers
• Shock-mounted, removable HDD in stainless steel case
• Rugged, dust-resistant hinges
• Vibration and drop-shock resistant
• Pre-installed screen film for touchscreen protection
CPU
• Intel® Pentium® M Processor LV 778:
2MB L2 cache
Processor speed 1.40GHz
400MHz FSB
STORAGE & MEMORY
• 80GB HDD
• 512MB SDRAM (DDR2) standard, expandable to 1536MB
DISPLAY
• 13.3" 1024 x 768 (XGA) transmissive, daylight-readable TFT Active Matrix Color LCD with
Touchscreen
• External video support up to 1280 x 1024 at 16 million colors (24 bit color depth)
• Intel® 915GMS graphic controller, UMA (Unified Memory Access) up to 128MB
• 540 Nit LCD brightness (non-touchscreen models), 500 Nit (touchscreen models)
AUDIO
• Sigmatel™ STAC9751T AC-97 v2.1 Compliant Audio Codec
• Integrated speaker
• Convenient keyboard volume and mute controls
EXPANSION SLOTS
• PC Card Type II x 2 or Type III x 1
• Secure Digital (SD) Card
MULTIMEDIA POCKET
• 1.44MB FDD, 3.5" standard
• Will accept optional Combo or Multi Drive, or 2nd Battery
KEYBOARD & INPUT
• 87-key with dedicated Windows® key
• Pressure sensitive touchpad with vertical scrolling support
• Touchscreen LCD (only with Touchscreen version)
A-1
15 March 2006
INTERFACE
• External Video MiniD-sub 15 pin
• Headphones/Speaker Mini-jack Stereo
• Microphone/Line In Mini-jack
• Parallel D-sub 25 pin
• Port Replicator 80 pin (Reinforced)
• Serial D-sub 9 pin
• USB 2.0 4 pin x 2
• 10/100/1000 Ethernet RJ-45
• 56K Modem RJ-11
WIRELESS LAN
• Intel® PRO/Wireless 2915ABG network connection 802.11a/b/g
• Security
– Authentication: LEAP, WPA, 802.1x, EAP-TLS, EAP-FAST, PEAP
– Encryption: CKIP, TKIP, 128-bit and 64-bit WEP, Hardware AES
POWER SUPPLY
• Lithium Ion battery pack (11.1V, 7.65Ah) with overcharge protection
• Battery operation: 5-8 hours (with first battery), up to 12 hours (with second battery)***
• Battery charging time: approximately 4.7 hours/off, 8.2 hours/on***
• AC Adapter: AC 100V-240V 50/60Hz, Auto Sensing/Switching
worldwide power supply
• Pop-up on-screen battery status reporting
POWER MANAGEMENT
• Hibernation, Standby, ACPI Bios
SOFTWARE
• Microsoft® Windows® XP Professional SP2
• Setup, Diagnostics, DMI Viewer, On-line Reference Manual,
Adobe® Acrobat® Reader
SECURITY FEATURES
• Password Security: Supervisor, User, Hard-Disk Lock
• Cable lock slot
DIMENSIONS & WEIGHT
• 2.3"(H) x 11.8"(W) x 9.5"(D)
• 7.9 lbs.
A-2
15 March 2006
APPENDIX B – DAY 1 PROCEDURES
Test
P1
P2
P3
Day 1 Location
Day 1 Setup
Terminal n
Verify
PacketSeeker
measure on
Record :
Environmentals:
Test
time
15
min
Running
time
Actual Actual
Start
End
Amplifying info / notes
5 min
Lat/Long/Location:
1
2
3
4
Look
angle/azimuth:
Terminal Settings:
Inmarsat Term #
Laptop #
Other equip
specifics:
Other adjustments
made or info:
Time to connect
thru the tunnel &
establish
connection
Notes:
extended ping
DNS
(192.168.20.254)
extended ping
www.yahoo.com
Run Numion (5
times)
Numion Settings:
Ensure Cookies
enabled. Run test
settings The
World, 1 minute
capture, 5 frames,
NO auto repeat,
window
maximum
Clear IE cookies
Run FTP script
(1MB, 5 MB)
:30
5 min
5 min
10
min
After the 5th run, screen
capture the graphs and
paste into daily test doc,
and select all copy the
rest of the page below it
and paste following.
15
min
Drop results into the
location & day folder.
B-1
Test
5
Alt 5
6
Day 1 Location
Log into
Exchange email,
sync folders
Record time to
login to outlook
Record time to
synchronize
folders
Test
time
15 March 2006
Running
time
Actual Actual
Start
End
15
min
Time to login: ________
Time for full synch with
all 6 test files:
________________
Alternate test if
needed.
Send in
succession.
Test
1 (20 KB
Excel)Time:__________
___;
Test 2 (36K Word)
Time:_______________
__;
Test 3 (160K Project)
Time:____________;
Test 4 (624 ppt)
Time:____________;
Test 5 (810
Word)Time:__________
__;
Test 6 (1 MB Zip)
Time:_____________
If full synch fails,
then check
individually until
failure: From
client with
landline
connection, send
an email to
INMARSAT
connected client.
Once received,
record download
time, then send
next in
succession.
Access JSIC
ePortal. Modify
and save changes 15
to a doc.
min
Change view to
"BGAN test view"
to see file sizes.
Go to EC2 Project
Files/BGAN/BGA
N Portal Testing
Files. Check out
"BGAN Testing
Objectives" doc.
(Sample word
small file; 30KB.)
Modify, save,
check back in.
Record times.
Retrieval time:
Save back time:
B-2
Test
7
3
Day 1 Location
TX/RX &
housekeeping
back to baseline
Run Numion (5
times)
Numion Settings:
Ensure Cookies
enabled. Run test
settings The
World, 1 minute
capture, 5 frames,
NO auto repeat,
window
maximum
Clear IE cookies
Test
time
15 March 2006
Running
time
Actual Actual
Start
End
Delete sent/received
email, resend test
emails. Change portal
doc to normal, save FTP
script results, Numion
results, et al into folder
location/terminal/day
15
min
10
min
After each run, screen
paste into a word doc,
rest of the page below it.
Save doc as "Numion
date time terminal", save
to location folder.
2:00
B-3
15 March 2006
B-4
15 March 2006
APPENDIX C – DAY 2 PROCEDURES
Test
P1
P2
P3
Day 2 Location
Test
time
Running
time
Actual
Start
Actual
End
Setup w/ Terminal
:30
n
telnet to 192.168.25.254.
Type "measure show".
(Should show engine is
running)
Verify
Packetseeker
measure on
Record :
Environmentals:
Lat/Long/Location:
1
2
3
Look
angle/azimuth:
Terminal Settings:
INMARSAT
Term #
Laptop #
Other equip
specifics:
Other adjustments
made or info:
Time to connect
thru the tunnel &
establish
connection
Notes:
extended ping
DNS
(192.168.20.254) 5 min
extended ping
www.yahoo.com
5 min
Run Numion (5
times)
10 min
Numion Settings:
Ensure Cookies
enabled. Run test
settings The
World, 1 minute
capture, 5 frames,
NO auto repeat,
window
maximum
:30
After the 5th run, screen
paste into daily test doc,
rest of the page below it
and paste following.
C-1
9
10
11
12
7
3
15 March 2006
Clear IE cookies
IWS session
(With JSIC).
(chat, whitebd,
voice,video) with
JSIC (record
quality, delay, etc) 15 min
Streaming Media
(with JSIC).
(Record quality,
delay, etc) Stream
as: 148, 282, 340,
548
45 min
Netmeeting (with
JSIC). (Record
quality, delay,
etc.)
Load until break
point
TX/RX &
housekeeping
back to baseline
Run Numion (3
times)
Numion Settings:
Ensure Cookies
enabled. Run test
settings The
World, 1 minute
capture, 41
frames, NO auto
repeat, window
maximum
Clear IE cookies
Observations:
Chat:
Whiteboard:
Voice:
Video:
Observations:
148:
282:
340:
548:
Observations:
Chat:
Whiteboard:
Voice:
Video:
15 min
15 min
Observations:
Numion results, et al into
folder
location/terminal/day
15 min
10 min
After each run, screen
paste into a word doc, and
select all copy the rest of
the page below it. Save
doc as "Numion date time
terminal", save to location
folder.
2:45
C-2
15 March 2006
APPENDIX D – STE TESTS THRANE & THRANE
Explorer 500
INMARSAT
Terminal Line
Settings
STE
3.1Khz (dial "2*"
first)
PSTN 3.1Khz
Terrestrial
Terminal Line
Autosig to STE
ISDN
STE
PSTN 3.1Khz
Autosig to STE
PSTN Autosig Pass
STE
PSTN 3.1Khz
Autosig to STU
PSTN Autosig Pass
INMARSAT
Terminal Line
Settings
STE
STE
Autosig to STE
Autosig to STE
3.1Khz (dial "2*"
first)
PSTN 3.1Khz
PSTN 3.1Khz
INMARSAT
Terminal Line
Settings Result Comments
Autosig Pass
PSTN Autosig Pass
ISDN Autosig Pass
GSM
Terminal Line
INMARSAT
Terminal Line
Settings
STE
3.1Khz (dial "2*"
first)
PSTN 3.1Khz
Autosig to SGSM
GSM
N/A
Fail
STE
PSTN N/A
Autosig to GSM
GSM
N/A
Pass
D-1
Inmarsat changed routing on their
network to make it work
Dialing into Explorer 500
Dialing into HNS 9201 FAX
number
SGSM identifies call as fax and will
not answer
15 March 2006
D-2
15 March 2006
APPENDIX E – STE TEST HNS
HNS 9201
Voice
INMARSAT
Terminal Line
Settings
STE
3.1Khz (dial
"2*" first)
ISDN N/A
Autosig to STE
ISDN
STE
ISDN N/A
Autosig to STE
PSTN Autosig Pass
Connected at 6.4
STE
ISDN N/A
Autosig to STU
PSTN Autosig Pass
Connected at 2.4
Terrestrial
Terminal Line
Autosig Pass
INMARSAT
Terminal Line
Settings
STE
3.1Khz (dial
"2*" first)
ISDN N/A
Autosig to STE
PSTN Autosig Pass
STE
ISDN N/A
Autosig to STE
ISDN
INMARSAT
Terminal Line
3.1Khz (dial
"2*" first)
Settings
INMARSAT
Terminal Line
GSM
Terminal Line
E-1
Rather than calling and trying to go
secure after establishing connection
Pressed "Autosecure" button before
dialing number
Connected at SV32 (Best Quality
Sound)
Autosig Pass
Dialing into Explorer 500 FAX
number
Dialing into HNS 9201
Pressed "Autosecure" button before
dialing number
Connects after long delay
15 March 2006
STE
ISDN N/A
Autosig to SGSM
GSM
N/A
Fail
Pass
STE
ISDN N/A
Autosig to GSM
GSM
N/A
Fail
Data
INMARSAT
Terminal Line
Settings
STE
Data Rate
Connected
ISDN Async 38.4k
Autosig to STE
ISDN
Autosig Pass
STE
ISDN Sync 64k
Autosig to STE
ISDN
Autosig Pass
STE
ISDN ASync 115k
Autosig to STE
ISDN
Autosig Fail
STE
ISDN Sync 128k
Autosig to STE
ISDN
Autosig Fail
STE
ISDN N/A
Autosig to STE
PSTN Autosig Pass
STE
STE
STE
ISDN N/A
ISDN N/A
ISDN N/A
Autosig to STU
Autosig to WLT
Autosig to WLT
PSTN Autosig
PSTN Autosig Fail
PSTN Autosig Fail
Terrestrial
Terminal Line
SGSM identifies call as fax and will
not answer
Only works when SGSM calls Fax
number for Inmarsat Terminal
Press Autosecure, then Secdata,
then dial #
Press Autosecure, then Secdata,
then dial #
Will not dial with the Scotty I-Split
used to bond
Will not dial with the Scotty I-Split
used to bond
No common operational mode
Everything worked at least once, had many inconsistencies. Firmware upgrades gave mixed results, still inconsistent results
Current location is on edge of IOR footprint. Testing needs to be done with newer version of Firmware and different "Spot
Beam" area,
E-2
15 March 2006
APPENDIX F – ACRONYMS/LOSSARY
AC - Alternating Current
ACPI - Advanced Configuration and Power Interface
AES - Advanced Encryption Standard
AOR - Area of Responsibility
APN - Application Point Node
ASIC - Application Specific Integrated Circuit
ASP - Advanced Systems Prototyping
BAND - Black Area Network Distribution
BGAN - Broadband Global Area Network
BT - Beta Test
C4ISR - Command, Control, Computers, Communications, Intelligence, Surveillance &
Reconnaissance
CKIP - Cisco Key Integrity Protocol
COCOM - Combatant Commander
CONOPS - Concept of Operations
CONUS - Continental United States
CPU - Central Processing Unit
CSW - Client Software
CTR - Contractor
CW2 - Chief Warrant Officer 2 (U.S. Army)
DDR2 - Double Data Rate 2 (memory)
DHCP - Dynamic Host Configuration Protocol
DISA - Defense Information Systems Agency
DISN - Defense Information Systems Network
DITCO - Defense Information Technology Contracting Office
DMI - Desktop Management Interface
DNS - Domain Name Services/Server
DOD - Department of Defense
DSAWG - Defense Information Systems Network (DISN) Security Accreditation Working
Group
DSN - Defense Switched Network
DSP - Digital Signal Processor
EAO - Enterprise Architectures Operations
EAP - Extensible Authentication Protocol
EAPFAST - Ethereal file name
EC2 - Executive Command and Control
EIRP - Effective Isotropic Radiated Power
EPSQ - Electronic Personnel Security Questionnaire
ESE - East South East
EUCOM - European Command
FDD - Floppy Disk Drive
FNBDT - Future Narrowband Digital Terminal
FPGA - Field Programmable Gate Array
FSB - Front Side Bus
F-1
15 March 2006
FTP - File Transfer Protocol
FW - Firmware
GHz - Gigahertz
GMDSS - Global Maritime Distress and Safety System (check context?)
GPS - Global Positioning System
HDD - Hard Disk Drive
HNS - Hughes Network Systems
IDU - Indoor Unit
IE - Internet Explorer
IGO - International Governmental Organization
IMEI - International Mobile Station Equipment Identity
IMSI - International Mobile Subscriber Identity
IMSO - International Maritime Satellite Organization
INE - Inline Network Encryptor
IOR - Indian Ocean Region
IP - Internet Protocol
IPSec - Internet Protocol Security
ISDN - Integrated Services Data/Digital Network
IWS - InfoWorkSpace
JSIC - Joint Systems Integration Command
JTF - Joint Task Force
KB - KiloByte
LAN - Local Area Network
LCD - Liquid Crystal Display
MAC Media Access Control
MB - MegaByte
MMI - Man-Machine Interface
MS - MicroSoft
MSISDN
NAVFIT - Navy Fitness Report Program
NERA - Manufacturer name
NIPRNet - Nonsecure Internet Protocol Router Network
NSA - National Security Agency
ODU - Outdoor Unit
OPS - Operations
OS - Operating System
OWA - Outlook Web Access
PC - Personal Computer
PEAP Protected Extensible Authentication Protocol
PSTN - Public Switched Telephone Network
RBGAN - Regional Broadband Area Network
RDI - Restricted Digital Information
RJ11 - 4-wire Telephone connector
RJ45 - 8-wire Ethernet connector
SAS - Satellite Access Station
SD - Secure Digital
F-2
15 March 2006
SDRAM - Synchronous Dynamic Random Access Memory
SIM - Subscriber Identity Module
SIPRNet - Secret Internet Protocol Routing Network
SME - Subject Matter Expert
SP2 0 - Service Pack 2
SR1 - Service Release 1
SSG - Staff Sergeant
STE - Secure Terminal Equipment PEAP
STU – Secure Telephone Unit
SW - Software
TCPIP - Transmission Control Protocol / Internet Protocol
TDY - Temporary Duty
TFT - Thin Film Transistor (Active Matrix LCD Flat Screen)
TKIP - Temporal Key Integrity Protocol (context?)
TTC - Telemetry, Tracking and Command
TXRX - Transmit/Receive
UDI - Unrestricted Digital Information
UDP - User Datagram Protocol
UK - United Kingdom
UMA - Unified Memory Architecture
US - United States
USB - Universal Serial Bus
VPN - Virtual Private Network
VTC - Video Teleconference
VoIP - Voice Over Internet Protocol
VoSIP - Voice Over Secure Internet Protocol
WEP - Wireless Encryption Protocol
WIN - Windows (Microsoft Operating System)
WLAN - Wireless Local Area Network
WPA - Wi-Fi Protected Access
XGA - Extended Graphics Adaptor
F-3
15 March 2006
F-4
15 March 2006
APPENDIX G – DISTRIBUTION LIST
1. Assistant Secretary of Defense (NII)/DOD CIO
6000 Defense Pentagon
Washington, DC 20301-6000
2. Joint Staff
ATTN: Director, J6
Pentagon, Room 1D773
3. Joint Staff
ATTN: Director, J8
8000 Joint Staff Pentagon
4. U.S. Central Command (USCENTCOM)
ATTN: CCDC
7115 S. Boundary Rd.
MacDill AFB, FL 33621-5101
5. U.S. Central Command (USCENTCOM)
ATTN: J6
7115 S. Boundary Rd.
MacDill AFB, FL 33621-5101
6. U.S. European Command (USEUCOM)
ATTN: ECDC
Unit 30400
APO, AE 09131
7. U.S. European Command (USEUCOM)
ATTN: J6
Unit 30400
APO, AE 09131
8. U.S. Joint Forces Command (USJFCOM)
ATTN: J00
1562 Mitscher Ave., Ste. 200
Norfolk, VA 23551-2488
ATTN: J6
ATTN: J7
G-1
15 March 2006
ATTN: J8
ATTN: J9
13. U.S. Pacific Command (USPACOM)
ATTN: J00
Box 64013
Camp H.M. Smith, HI 96861-4031
14. U.S. Pacific Command (USPACOM)
ATTN: J06
Box 64013
Camp H.M. Smith, HI 96861-4031
15. U.S. Southern Command (USSOUTHCOM)
ATTN: SCJ00
3511 NW 91st St.
Miami, FL 33172
16. U.S. Southern Command (USSOUTHCOM)
ATTN: SCJ06
3511 NW 91st St.
Miami, FL 33172
17. U.S. Northern Command (USNORTHCOM)
ATTN: DC
250 S Peterson Blvd
Suite 116
Peterson AFB CO 80914-3010
18. U.S. Northern Command (USNORTHCOM)
ATTN: J6
250 S Peterson Blvd
Suite 116
Peterson AFB CO 80914-3010
19. U.S. Special Operations Command (USSOCOM)
ATTN: SOJ00
7701 Tampa Point Blvd.
MacDill AFB, FL 33621
20. U.S. Special Operations Command (USSOCOM)
ATTN: SOJ06
7701 Tampa Point Blvd.
G-2
15 March 2006
21. U.S. Strategic Command (USSTRATCOM)
ATTN: J00
901 SAC Blvd., Ste. 1A1
Offutt AFB, NE 68113-6020
22. U.S. Strategic Command (USSTRATCOM)
ATTN: J06
901 SAC Blvd., Ste. 1A1
Offutt AFB, NE 68113-6020
23. U.S. Transportation Command (USTRANSCOM)
ATTN: TCJ00
508 Scott Drive
Scott AFB, IL 62225
24. U.S. Transportation Command (USTRANSCOM)
ATTN: TCJ06
508 Scott Drive
Scott AFB, IL 62225
25. Chief of Naval Operations
ATTN: N6
2000 Navy Pentagon
26. Commandant of the Marine Corps
ATTN: C4
Headquarters Marine Corps
2 Navy Annex (CMC)
27. Army Chief of Staff
ATTN: SAIS-ZA
200 Army Pentagon
28. Air Force Chief of Staff
ATTN: XI
1670 Air Force Pentagon
29. Defense Information Systems Agency
ATTN: DIR
701 South Courthouse Road
Arlington, VA 22204-2199
30. Defense Intelligence Agency
ATTN: DR
200 MacDill Blvd.
Bldg 6000
G-3
15 March 2006
31. Defense Intelligence Agency
ATTN: DH
3100 Clarendon Blvd.
Arlington, VA 22201
32. National Security Agency
ATTN: DIR
9800 Savage Rd.
Fort Meade, MD 20755-6426
33. Defense Advanced Research Projects Agency
ATTN: DIR
3701 North Fairfax Drive
Arlington, VA 22203-1714
34. Electronic Systems Center (ESC)
ATTN: CC
50 Griffiss St.
Hanscom AFB, MA 01731-1625
35. U.S. Army Communications and Electronics Command
ATTN: AMSEL-CG
Bldg 457
Ocean Port Ave.
Fort Monmouth, NJ 07703-5404
36. U.S. Navy Space and Warfare Command
ATTN: 00
4301 Pacific Highway
San Diego, CA 92110-3127
37. Naval Research Laboratory
ATTN: 1000
4555 Overlook Ave. S.W.
Washington, DC 20375
38. Air Force Research Laboratory
ATTN: IF
26 Electronics Parkway, Bldg 106
Rome, NY 13441-4509
39. Air Force Research Laboratory
ATTN: CC
1864 4th Street, Suite 1
Wright-Patterson AFB, OH 45433-7131
40. U.S. Army Research Laboratory
ATTN: AMSRL-D
2800 Powder Mill Road
Adelphi, MD 20782-1197
G-4
15 March 2006
41. U.S. Army Research Laboratory
ATTN: AMSRL-SL
Aberdeen Proving Ground, MD 21005-5067
42. Joint Communications Support Element
ATTN: CC
8532 Marina Bay Drive.
43. Joint Interoperability Test Command
ATTN: JT
Fort Huachuca, AZ 85613-7020
44. Commanding Officer
USAF C2 Battlelab
Building 10
22 Rickenbacker Road
Langley AFB, VA, 23665
Commercial (757) 225-9801
FAX (757) 225-9803
45. Marine Corps Warfighting Lab (MCWL)
ATTN: G6
3255 Meyers Avenue
Quantico, VA 22134-5096
46. Battle Command Battle Lab
ATTN: ATZH-BL/VDIR
Fort Gordon, GA 30905-5299
47. Naval Warfare Development Command
ATTN: N00
686 Cushing Road
Newport, RI 02841
48. Commandant (G-S)
U.S. Coast Guard
2100 Second St SW
Washington, DC 20593
G-5
15 March 2006
G-6

(ec2) enhancement

Transcription

Similar documents

X-Stream - Stratos Global

BGAN for land

Sectéra® BDI Terminal (Type 1) - General Dynamics Mission Systems

Sara Echevarria

Programme - Alexandru Ioan Cuza

ERL-0631-GD PR

Paris Charles de Gaulle Airport (France)

Satcom1 TV-Datasheet

click here to open

BASIC SWITCHES