Domenix

Unified Protocol Architecture (UPA)

Enabling Seamless Sensor Data Integration Across TAK and ISA Ecosystems

www.domenix.com/upa

Executive Summary

The Unified Protocol Architecture (UPA) from Domenix is a software solution that connects two major tactical data ecosystems: the Tactical Assault Kit (TAK) and the Integrated Sensor Architecture (ISA). UPA translates raw sensor data into standardized formats, enabling sensors to publish information to either or both ecosystems. It also provides protocol conversion between CoT and ISA formats, plus a unified mapping system that displays all sensor data in one view.

πŸ“ Note: All UPA software components are referred to as UPA-SE (UPA Software Element). UPA-SE performs translation functions β€” converting raw sensor data to standardized protocols (CoT or ISA) and enabling bidirectional protocol conversion between ecosystems.

1. The Problem: Two Languages, One Battlefield

Imagine you have scouts (sensors) sending reports from the field. The problem? There are two different "clubs" that each speak their own language:

Normally, a scout's report written in TAK language can't be read by ISA members, and vice versa. This creates information silos where valuable sensor data gets trapped in one ecosystem.

🎯 Simple Analogy: Two Highway Systems

Think of TAK and ISA as two separate highway systems built on the same ground. Cars (data) on the TAK highway can't switch to the ISA highway β€” they're stuck in their lane. UPA-SE is like building interchange ramps that let cars cross between highways, plus a control tower that can see traffic on both systems at once.

2. The Layered Architecture

UPA uses a layered approach to solve this problem. Think of it like a building with distinct floors, each serving a specific purpose:

Layer 1: Physical Transport (The Foundation)

At the bottom is the Physical Transport Layer β€” the actual connectivity that carries all data. This includes:

This layer is shared by everyone. All data flows through it, regardless of which protocol it uses. It's protocol-agnostic β€” it just moves bits from point A to point B.

Layer 2: Logical Transport (The Rule Books)

Above the physical layer sit two separate Logical Transport Layers β€” think of them as different rule books for formatting and routing data:

Both logical layers ride on top of the same physical transport but maintain separate protocol rules.

Layer 3: Sensors (The Publishers)

Sensors produce raw data in various proprietary formats. They act as publishers in the system β€” sending out information that others can receive.

Layer 4: Displays (The Subscribers)

Display applications subscribe to receive data from their respective ecosystems:

Figure 1: UPA Layered Architecture Overview

LAYER 4: DISPLAYS (Subscribers) TAK Displays ATAK β€’ WinTAK β€’ TAKX (CoT format only) ISA Displays CPCE (ISA format only) UPA Map Unified View (Subscribes to BOTH) LAYER 3: LOGICAL TRANSPORT (Protocol-Specific) TAK Logical Transport TAK Server Handles CoT Messages ISA Logical Transport ISA Controller Handles ISA Messages UPA-SE Protocol Translator CoT ↔ ISA Conversion LAYER 2: PHYSICAL TRANSPORT (Shared Foundation) Shared Physical Transport Layer Wave Relay β€’ Mesh Networks β€’ Radios β€’ Wired Links All connectivity shared by both ecosystems LAYER 1: SENSOR INTEGRATION UPA-SE Sensor Translator Converts Raw Sensor Data β†’ CoT or ISA (or both) CoT ISA Sensor A Sensor B Sensor C Sensor D Raw/Proprietary Sensor Data

Figure 1: The four-layer UPA architecture showing sensors publishing through UPA-SE translation, shared physical transport (Wave Relay, mesh networks), separate logical transports (TAK/ISA), and ecosystem-specific displays plus the unified UPA Map.

3. How UPA-SE Solves the Problem

3.1 Sensor Translation

UPA-SE plugs directly into sensors. When a sensor produces raw data, UPA-SE:

This means a single sensor can now feed both ecosystems simultaneously β€” no duplicate hardware needed.

3.2 Protocol Conversion

UPA-SE also enables cross-ecosystem communication for existing deployments:

3.3 UPA Map: Unified Situational Awareness

The UPA Map is a specialized display that subscribes to both the TAK Server and ISA Controller. This provides:

Figure 2: Data Flow β€” From Sensor to Display

Sensor Raw Data STEP 1 UPA-SE Translator Raw β†’ CoT or ISA STEP 2 Physical Transport (Wave Relay, Mesh) STEP 3 TAK Server (CoT) Logical Transport STEP 4 ISA Controller (ISA) Logical Transport STEP 4 ATAK CPCE STEP 5 STEP 5 Data Flow Summary: Sensor β†’ UPA-SE translates β†’ Physical layer (Wave Relay) β†’ Logical layer routes (TAK or ISA) β†’ Display receives

Figure 2: Step-by-step data flow from raw sensor input through UPA-SE translation, physical transport (Wave Relay), logical routing, and final display delivery.

Figure 3: Ecosystem Comparison β€” TAK vs ISA

TAK Ecosystem Protocol: Cursor on Target (CoT) Manager: TAK Server Native Displays: ATAK β€’ WinTAK β€’ TAKX (Cannot read ISA format) ISA Ecosystem Protocol: ISA Format Manager: ISA Controller Native Displays: CPCE (Cannot read CoT format) Both share the same Physical Transport Layer (Wave Relay, Mesh Networks)

Figure 3: Side-by-side comparison of the TAK and ISA ecosystems showing their distinct protocols, managers, and native display applications β€” unified at the physical transport layer.

4. Key Benefits

πŸ”Œ Sensor Flexibility

Any sensor can publish to TAK, ISA, or both ecosystems through UPA-SE translation β€” no hardware duplication required.

πŸ”„ Legacy Compatibility

Existing displays (ATAK, CPCE) continue working unchanged. UPA-SE handles all conversion behind the scenes.

πŸ—ΊοΈ Unified Awareness

UPA Map provides a single view of all sensor data, eliminating the need to switch between applications.

🌐 True Interoperability

Break down data silos between ecosystems. Share information freely regardless of native protocol.

⚑ Simplified Deployment

Modular architecture allows incremental adoption. Start with sensor translation, add protocol conversion and mapping as needed.

πŸ›‘οΈ Maintained Separation

Logical transport layers remain distinct. Protocol integrity is preserved while enabling interoperability.

5. Conclusion

The Unified Protocol Architecture (UPA) from Domenix transforms how tactical sensor data moves between ecosystems. By normalizing data at the sensor level via UPA-SE, leveraging shared physical transport (Wave Relay, mesh networks), preserving logical protocol separation, and enabling protocol conversion and unified mapping, UPA delivers:

Whether you need to integrate new sensors, enable cross-ecosystem communication for existing deployments, or create a common operational picture, UPA provides the flexible, layered solution to unify your tactical data infrastructure.