Overview#
A forward observer streaming live video from a phone should appear on the command map exactly where they are standing, labelled with their callsign, right next to their position track. TAK ICU Mobile Video Streaming makes that happen.
The capability connects the TAK ICU ATAK plugin to Argus, so that live mobile video feeds originating from field devices are registered, persisted, and managed inside the operational picture. Every feed carries a callsign, a geolocation, a streaming address, and a classification level, which means commanders and situation-room operators can pull live imagery from personnel in the field without leaving the map they are already working in. The same field element that reports a position track also delivers a moving picture, and both sit side by side on a single pane.
Key Features#
-
Live Stream Registration: Field devices running the TAK ICU plugin register a video feed with a single call, supplying a unique stream identifier, callsign, streaming address, protocol, resolution, bitrate, and geolocation. The feed becomes immediately discoverable to cleared operators in the same organisation.
-
Callsign and Geolocation Labelling: Every registered feed carries the originating callsign and a latitude/longitude position, so operators can find a stream by who is sending it and where they are, rather than by an opaque connection address.
-
Clearance-Aware Visibility: Each stream carries a secrecy classification, and the feed list returned to an operator is filtered against that operator's clearance level. Streams above a viewer's clearance never appear in their results.
-
Organisation Scoping: Streams are scoped to the registering organisation. Operators see only the feeds belonging to their own tenant, keeping field imagery isolated between organisations sharing the platform.
-
Operational Picture Entity Emission: On registration, each stream is published into the unified operational picture as a geolocated entity of type UNIT, placing the live feed on the same map as position tracks, sensor coverage, and alerts.
-
Aggregate Stream Statistics: A statistics view reports total registered streams and the count of active feeds for the organisation, giving command a quick read on how much live imagery is flowing from the field.
-
RTSP-First Video Delivery: Feeds default to RTSP delivery, the established protocol for low-latency live video, while the protocol field allows other transport types to be recorded against a stream.
-
Audit-Logged Lifecycle: Every registration is written to an immutable audit trail through the shared interoperability bridge, recording who registered which feed, for which organisation, at what classification.
Use Cases#
Command and Control#
Commanders and situation-room operators pull live video from personnel in the field directly through the Argus interface, watching a forward element's feed alongside its position track without switching tools.
Forward Observation#
A forward observer streaming through the TAK ICU plugin appears as a geolocated, callsign-labelled feed. Command sees both the observer's position data and the live picture from the same field element on one map.
Multi-Agency Operations#
Each participating organisation registers and views its own feeds under tenant scoping, so a joint operation can run live imagery from several agencies on the platform without crossing organisational boundaries.
Classified Operations#
Sensitive feeds are registered with a higher secrecy classification and remain invisible to operators below the required clearance, allowing a single picture to carry feeds of mixed sensitivity safely.
Situation Rooms#
Operators monitoring a fast-moving incident enumerate every active feed by callsign and location, selecting the imagery most relevant to the decision at hand from a single live roster.
Integration#
The capability is reached through the Argus GraphQL endpoint, authenticated with OAuth2 and bearer JWT, with the same organisation scoping applied to every request. Operators enumerate feeds for their organisation, read aggregate statistics, and register new feeds from field devices.
- Listing feeds returns the stream identifier, callsign, video address, protocol, resolution, bitrate, position, status, and classification for each active stream, already filtered to the viewer's clearance.
- The statistics view returns total and active stream counts for the organisation.
- Registering a stream accepts the originating field device's callsign, streaming address, protocol, resolution, bitrate, geolocation, and classification, then persists the record and publishes it to the operational picture.
The benefit to a customer is a single normalised model: whatever field device sends the feed, the platform stores it the same way, places it on the same map, and exposes it through the same authenticated endpoint as every other operational layer. The TAK ICU ATAK plugin is what the customer plugs in at the field-device end; the streamed video is delivered over standard RTSP, so existing players and recorders consume it without bespoke tooling.
Open Standards#
- Cursor-on-Target (CoT) XML: The TAK ICU plugin runs inside the ATAK ecosystem, where position and status are carried as Cursor-on-Target XML messages. Streams registered from ATAK-equipped devices sit alongside CoT position tracks from the same field element in the unified operational picture, the shared standard of the TAK and MIL-STD-2525 community.
- RTSP (Real Time Streaming Protocol, RFC 7826): Mobile video feeds default to RTSP, the standard protocol for establishing and controlling low-latency live media sessions, letting standard players and recorders consume registered feeds directly.
- OAuth2 and JSON Web Tokens (JWT): Access is authenticated with OAuth2 bearer tokens in JWT form, the standard mechanism for delegated, scoped authorisation across the platform.
- GraphQL: Feed enumeration, statistics, and registration are exposed through a single typed GraphQL endpoint, giving callers a self-describing contract over the streaming capability.
- WGS 84 / EPSG:4326: Stream geolocations are expressed as latitude and longitude in the WGS 84 geographic coordinate reference system, the default across the platform's geospatial layers.
Security & Compliance#
Every operation requires authentication, and resolvers are scoped to the caller's organisation, so feeds never cross tenant boundaries. Stream visibility is governed by classification: each feed carries a secrecy level, and lists are filtered against the viewer's clearance so that imagery above their level is never returned. Registrations are recorded on an immutable audit trail through the shared interoperability bridge, capturing the registering user, the organisation, the affected feed, and its classification, giving operators a complete and reviewable history of how live imagery entered the operational picture.
Last Reviewed: 2026-05-26 Last Updated: 2026-05-26