Mobile devices performing mission-critical functions at the tactical edge, such as those employed by first responders, military personnel, and law enforcement, operate in environments that are vastly different from enterprise computing environments. In spite of the differences in resource availability, threat models, vulnerabilities, information formats, and communication protocols, there is a great advantage to (and great demand for) enabling information exchange between the tactical edge and

more »

... nterprise environments. Creating a specialized mobile version of each desired service that incorporates an appropriate level of security protection and quality of service (QoS) for the tactical users is one possibility. Such an approach is not cost effective, however, as the market for a given tactical application is small compared to the commercial user base for mobile applications and services. Furthermore, the need for information or services from the enterprise by tactical users can be too ad hoc and time critical, e.g., during disaster response, to support developing a specialized version. Finally, service specialization for mobile web access covers only one of multiple information dissemination and access patterns that arise in tactical operations. This paper presents the design and a prototype implementation of a gateway solution that provides secure tactical-enterprise information exchange and handles the differences in resource availability, QoS requirements, communication formats, and protocols. Keywords-gateway; middleware service; tactical and enterprise environments; quality of service; security; information management I. Report Documentation Page Form Approved OMB No. 0704-0188 Public reporting burden for the 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 the 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 Washington Headquarters Services, Directorate for Information Operations and Reports, 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 a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. 17th IEEE Symposium on Object/Component/Service-oriented Real-time Distributed Computing, Reno, NV, June 10-12 2014. ABSTRACT Mobile devices performing mission-critical func-tions at the tactical edge, such as those employed by first re-sponders, military personnel, and law enforcement, operate in environments that are vastly different from enterprise computing environments. In spite of the differences in resource availability, threat models, vulnerabilities, information formats, and commu-nication protocols, there is a great advantage to (and great de-mand for) enabling information exchange between the tactical edge and enterprise environments. Creating a specialized mobile version of each desired service that incorporates an appropriate level of security protection and quality of service (QoS) for the tactical users is one possibility. Such an approach is not cost ef-fective, however, as the market for a given tactical application is small compared to the commercial user base for mobile applica-tions and services. Furthermore, the need for information or services from the enterprise by tactical users can be too ad hoc and time critical, e.g., during disaster response, to support devel-oping a specialized version. Finally, service specialization for mobile web access covers only one of multiple information dis-semination and access patterns that arise in tactical operations. This paper presents the design and a prototype implementation of a gateway solution that provides secure tactical-enterprise information exchange and handles the differences in resource availability, QoS requirements, communication formats, and protocols. 15 . SUBJECT TERMS 16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as Report (SAR) 18. NUMBER OF PAGES 9 19a. NAME OF RESPONSIBLE PERSON a. REPORT unclassified b. ABSTRACT unclassified c. THIS PAGE unclassified Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18