The Integrated Topside (INTOP) Program is an Innovative Naval Prototype effort initiated by the Office of Naval Research (ONR) to develop wideband multifunction RF system technology that will enable increased functionality through the employment of shared hardware and software resources to execute the mission objectives. An Electronic Warfare/Information Operations/Communications (EW/IO/ Comm) Advanced Development Model (ADM) is one of the prototypes being developed under the INTOP program. ONR is also developing low cost narrow band phased arrays as part of the High Throughput Networking Infrastructure (HTNI) program to support communications in the Common Data Link (CDL) frequency range. This paper explores the challenges and benefits that could be achieved through an integration of both technologies. The INTOP EW/IO/Comm program effort functionality encompasses the existing CDL spectrum with broader frequency coverage. Both the narrowband CDL array and the wideband INTOP array provide multi-beam array technology. However, the INTOP array provides greater flexibility in beam forming, interference nulling, and frequency coverage. Depending on the specific requirement for the communications link support, the CDL array set (four per ship) may provide as many as eight receive beams when used individually, or four beams when used in an elevation diversity configuration to mitigate multipath and other atmospheric effects. The INTOP receive array set (4 per ship) has the potential to support as many as 16 communication links or as few as four, when supporting the most distant communication links. As a combined asset, the receive antenna capacity addresses the Navy projections for the number of links to support Intelligence, Surveillance, and Reconnaissance (ISR) platforms. The transmit array is sized to similarly support the required number of links. In addition to the combined link support, the integration of the two arrays provides redundancy, multipath mitigation, frequency diversity, the potential to employ spatial separation to achieve the desired number of links within the existing frequency constraints, and the ability to allocate receive assets to enhance the frequency management of the ship to prevent interference and contention.!

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std. Z39.18 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing this collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS.

Standard Form 298 (Rev. 8-98)Prescribed by ANSI Std. Z39.18Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing this collection of information. This report describes the development and test of processing and transponding payload configurations for the High Altitude Relay and Router (HARR) project. This work was performed by the U.S. Naval Research Laboratory (NRL) to support a viable long-range end-to-end mobile ad hoc wireless network in a tactical environment. HARR has the potential to provide closed network communications and other tactical capabilities between nodes separated by up to 200 miles at a reduced cost as compared to other existing technologies. HARR achieves these results by flying its payloads in untethered balloons at near-space altitudes around 20,000 m (approximately 65,000 ft), providing a relay capability over a substantial area of operation. The report describes the design and integration of the airborne and ground node systems that make up this network, and analyzes test data collected using unicast and multicast transport protocols in an IP-based environment. The field test data discussed in this report was collected at Lubbock, Texas, in June 2006. Additional followup testing was conducted through the summer and fall of 2006 at NRL in Washington, DC. REPORT TYPE 1. REPORT DATE (DD-MM-YYYY) TITLE AND SUBTITLE AUTHOR(S) PERFORMING ORGANIZATION REPORT NUMBER PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) SPONSOR / MONITOR'S ACRONYM(S) 9. SPONSORING / MONITORING AGENCY NAME(S) AND ADDRESS(ES) SPONSOR / MONITOR'S REPORT NUMBER(S) Network relay RF communicationsTransponder 802.11b

Current naval satellite-based networks allocate physical layer resources to users based on predetermined requirements analyses.Once the requirements are determined and resources allocated, they cannot be easily changed to adapt as actual situations warrant. A dynamic allocation process allows satellite resources to be reallocated based on the current requirements of the network users. Proposals and designs for next generation satellite systems are beginning to incorporate dynamic resource allocation features into their architectures. In this paper we present a methodology that automatically directs the use of physical layer resources for a satellitebased network according to network demands. The proposed methodology utilizes an "executive" to optimize and control the overall system utilization by incorporating information from transponder load, user prioritization, and real-time network requirements. To demonstrate our methodology we have implemented a non-propriety testbed based on COTS hardware and equipment currently being utilized by the fleet. We also present results from tests that show the benefits of a dynamic architecture over a traditional static architecture.