Abstract-In this paper we provide an architecture for Tactical Information Middleware for bandwidth constrained information management. We propose the ideas of rank-based data dissemination, and the use of a tactical information management query language. These ideas will deal with dynamic changes in bandwidth and explore opportunistic data dissemination. Thus, will lead to a cross layer design of a system capable of handling the dynamic data management issues relevant in many mission critical applications.
1I. INTRODUCTION Air force tactical missions such as collaborative reconnaissance involve Unmanned Air Vehicles (UAVs), ground stations, and dismounted users. Such missions often run applications which disseminate video/imagery, requiring stringent levels of quality of service (QoS). Furthermore, this tactical level QoS for information management needs to be achieved under environmental and operational constraints such as intermittent network connectivity, low bandwidth, limited CPU and battery power. Tactical Information Management (TIM) is the capability of providing QoS in a dynamic topology under bandwidth constraints. Similar conditions will exist in future mobile P2P environments that involve vehicles, mobile devices such as cellular phones carried by pedestrians, and stationary computers.We propose to address the TIM needs by building a Tactical Information Middleware (TIMW) that uses a declarative language like SQL, specifically designed for intermittent and low/dynamic connectivity environments. The TIMW will receive queries from the application layer, and it will collaborate with the Radio-Communication Layer to process them in a mobile, distributed fashion.Current technology such as OMG Data Distribution Service (DDS), used in many DoD applications, promises to deliver the QoS assurances but is limited in its capability to address the resource limitations of tactical missions. The proposed ideas will enhance the current functionality of systems such as AIMS [15].The rest of the paper is organized as follows. In section II we introduce the environment. In section III we describe the architecture of the TIMW. In sections IV to VI we discuss each individual component of TIMW respectively.