In this paper we present an approach for enabling the formation of a Joint Service, heterogeneous Airborne Network. Central to this approach will be the definition of a Joint Airborne Network Services Suite (JANSS). The JANSS will consist of a common set of integrated features and functions that can be implemented on all airborne platforms to enable those platforms to participate in the future IP-based airborne network. The JANSS will include the functionality necessary to enable the exchange of IP-based data using either existing legacy voice/data radios, network-enabled commercial terminals, or emerging network-enabled military radios. Although integrated, the JANSS will be modular in nature, capable of being adapted, expanded, or enhanced, as needed, to support a particular platform's needs. Also, it will allow for implementation using various possible hardware and software solutions. The JANSS will incorporate a set of user application services to include: (I) collaboration tools such as text chat, email, and voice over IP (VoIP); (2) file transfers; (3) video streaming; and (4) Web services. It will also include security and networking services such as: access control, authentication, intrusion detection, routing, quality of service (QoS), and network management. The services provided by the JANSS will be capable of being implemented incrementally and will allow for compatibility with legacy and future military communication systems
[1]
Ryuji Wakikawa,et al.
Network Mobility (NEMO) Basic Support Protocol
,
2005,
RFC.
[2]
Charles E. Perkins,et al.
IP Mobility Support
,
1996,
RFC.
[3]
M. Tummala,et al.
Testing of DiffServ performance over a U.S. Navy satellite communication network
,
2004,
IEEE MILCOM 2004. Military Communications Conference, 2004..
[4]
M. Keaton,et al.
Fielding mobile IP on joint stars: challenges and solutions enabling IP connectivity via concurrent use of legacy communications links
,
2004,
IEEE MILCOM 2004. Military Communications Conference, 2004..
[5]
Pekka Nikander,et al.
Host Identity Protocol (HIP) Architecture
,
2006,
RFC.