Coordinating UAV information for executing national security-oriented collaboration

PDF

Authors
  1. Isenor, A.W.
  2. Allard, Y.
  3. Lapinski, A-L.S.
  4. Demers, H.
  5. Radulescu, D.
Corporate Authors
Defence Research and Development Canada, Atlantic Research Centre, Halifax NS (CAN);OODA Technologies Inc., Montreal, QUE. (CAN)
Abstract
Unmanned Aerial Vehicles (UAVs) are being used by numerous nations for defence-related missions. In some cases, the UAV is considered a cost-effective means to acquire data such as imagery over a location or object. Considering Canada’s geographic expanse, UAVs are also being suggested as a potential platform for use in surveillance of remote areas, such as northern Canada. However, such activities are typically associated with security as opposed to defence. The use of a defence platform for security activities introduces the issue of information exchange between the defence and security communities and their software applications. This paper explores the flow of information from the system used by the UAVs employed by the Royal Canadian Navy. Multiple computers are setup, each with the information system used by the UAVs, including appropriate communication between the systems. Simulated data that may be expected from a typical maritime UAV mission is then fed into the information system. The information structures common to the Canadian security community are then used to store and transfer the simulated data. The resulting data flow from the defence-oriented UAV system to the security-oriented information structure is then displayed using an open source geospatial application. Use of the information structures and applications relevant to the security community avoids the distribution restrictions often associated with defence-specific applications.
Keywords
maritime;information flow;security
Report Number
DRDC-RDDC-2015-P001 — External Literature
Date of publication
15 Jan 2015
Number of Pages
12
DSTKIM No
CA039912
CANDIS No
800817
Format(s):
Electronic Document(PDF)

Permanent link

Document 1 of 1

Date modified: