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.
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:
- TAK Club speaks "Cursor on Target" (CoT) β used by apps like ATAK, WinTAK, and TAKX
- ISA Club speaks "ISA format" β used by systems like CPCE
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:
- Wave Relay and other mesh networks (MANET radios)
- Wireless links and radio connections
- Wired ethernet or fiber connections
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:
- TAK Logical Transport: Managed by the TAK Server, which handles Cursor on Target (CoT) formatted messages. Sensors publish CoT reports here; TAK displays subscribe.
- ISA Logical Transport: Managed by the ISA Controller, which handles ISA formatted messages. Same publish-subscribe pattern for ISA ecosystem.
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:
- TAK Displays: ATAK, WinTAK, TAKX β only read CoT data from TAK Server
- ISA Displays: CPCE β only reads ISA data from ISA Controller
Figure 1: UPA Layered Architecture Overview
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:
- Normalizes the proprietary format into a standard structure
- Translates it into CoT format for TAK ecosystem, ISA format for ISA ecosystem, or both
- Publishes the translated data through the physical transport layer
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:
- Subscribes to the TAK Server (receiving CoT data)
- Converts CoT β ISA and republishes to ISA Controller
- Works in reverse: ISA β CoT conversion
- Bidirectional, allowing full interoperability
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:
- A single unified view of all sensor data regardless of source ecosystem
- No need to switch between ATAK and CPCE to see the full picture
- Operates as a standard subscriber β no special protocol needed
Figure 2: Data Flow β From Sensor to Display
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
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:
- Enhanced situational awareness through the UPA Map's unified view
- Faster decision-making with all sensor data accessible regardless of source
- True plug-and-play integration for sensors across both TAK and ISA ecosystems
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.