EN
Book a demo

Technology

VERA: an image with proven age.

VERA is our own protocol. The name comes from the Latin verus, meaning true. Today’s systems leave the last frame on screen during an outage, looking live. VERA either proves every frame or rejects it.

Camera view in the Direct cockpit, visualisation
38 msValid
Visualisation

01

Latency is not enough

01

Network latency

The time a packet takes to cross the network. It is only one leg of the journey, and vendors measure it differently.

02

Image age

The time from frame exposure on the drone to its display to the operator. This is the number that matters when flying.

03

Proof of age

An age the station verifies for every single frame and records. Not an average from a datasheet.

02

The time contract

Every frame carries two pieces of information: when it was created and until when it is valid. From these the station determines one of three states.

Valid

Frame age is below the deadline. The operator sees the present.

Reduced freshness

The image is still verified but ageing. The cockpit shows it and recommends more careful flight.

Unavailable

Age cannot be guaranteed. A neutral screen with the reason instead of a frozen frame.

03

Three mechanisms

01

Two networks at once

With the Brain Duo concept every frame travels through two operators. The copy that arrives first counts.

02

Deadline for commands

A command carries the number of the frame the operator saw. The drone computes the loop age and does not execute a late command.

03

Neutral screen

When the age exceeds the deadline, the station switches to a neutral screen with the reason. Measured internally within 2.72 ms.

Try the interactive diagrams →

04

Time budget

Frame age is the sum of steps from light on the sensor to light on the display. Example for the 240 fps profile, 5G and a 240 Hz panel.

Image profile
Network
Display

Change profile, network and display →

Transmitter: sensor, ISP, encoder10.0 msO
Network 5G, one way12.0 msO
Receiver and decoder0.5 msO
Path to the 240 Hz display3.2 msO
Waiting for the next frame, average2.1 msO
Total, average27.8 msO

At 20 m/s the drone covers in this time 0.56 m.

Calculated from the VERA v1.1 protocol plan. All values are estimates; the network figure is a working one-way latency. Real values will come from measurement.

05

A 20-byte header

Every video packet starts with a 160-bit VERA header. Three fields carry time.

FieldBitsPurpose
Version4Protocol version. Lets the format evolve without confusing the receiver.
Type4Packet type: video, parity, ping, feedback or command.
Flags8Last fragment, key frame, start of a recovery wave and path A or B.
Stream ID8Distinguishes several cameras and the second network path.
Frame number16Frame order. The operator command is bound to this number.
Fragment4Fragment order within the frame.
Count4How many fragments make up the frame.
FEC8Parity group and index. Repairs losses within one frame without waiting.
t_exp32Mid-exposure time in µs on the drone clock. Age is counted from it.
t_send − t_exp16How long the transmitter took, for every frame.
GDR wave8Recovery wave position. The receiver knows when the image is whole again after a loss.
Band8Image band index. Lets only the damaged part be hidden.
Profile8Profile and deadline ID. The deadline travels with the frame and is never extended.
CRC-1616Header check. A damaged packet is rejected immediately.
Reserved16Room for future fields without a version change.

We share the detailed protocol plan with partners on request.

06

Measured and target

We show the real state. Every number is labelled.

  • Zmeasured internally
  • Mmanufacturer data, not verified by AKIZU
  • NAKIZU design
  • Ctarget
  • Pplan
  • Odesign estimate
  • Unot yet known
ItemValueType
Full chain, median (WiFi, phone as transmitter)64.6 msZ
Full chain, p99 (WiFi, phone as transmitter)87.4 msZ
Switch to neutral screen after stream loss≤ 2.72 msZ
Receiver: frame → GPU, p500.3 msZ
LET-1: p99 image age on a real drone≤ 50 msC
KVAL-1: qualification target≤ 25 msC
3GPP: video for BVLOS control140 ms3GPP standard requirement
3GPP: C2 commands40 ms3GPP standard requirement

3GPP TS 22.125

Image-age measurement methodology →

07

Qualification gates

  1. Q4 2026Optical measurementImage age verified with an independent optical instrument.
  2. Q1 2027LET-1 on VOXL 2p99 image age under 50 ms on a real drone.
  3. Q2 2027Stability on 5GAt least 95 % of time in the Valid state.
  4. Q3 2027First paid pilotDeployment with a partner.

In more detail

When the image is not valid

A failure should be visible. Silence is not a state.

If age passes the contract, Direct does not keep the last frame. It shows a neutral screen and the reason. An old image that looks live is worse than an empty screen.

When one network fails, the frame goes via the other. When neither is valid, a command from that frame should not be executed. A radio backup that would remain after both networks fail is not yet in the design.

The header carries the frame number. A command should be joinable to what the operator saw. Without that the record is a video, not evidence.

Bring to the meeting

  • Valid, or not.
  • A reason, not a frozen scene.
  • A log of the switch.

This is not

  • Resistance to every kind of jamming.
  • A weapon system.
  • A replacement for the pilot.

In more detail

What VERA is not yet

VERA is a protocol design, not an approved standard.

It carries age from exposure to the panel. It is not network latency and not the average delay of a codec.

We do not have a place in an EASA or 3GPP standard. An ambition is not a confirmation.

Licensing for other makers is a plan for 2028. Until that day the chain is our design, checked at the gates, not a product on a shelf.

Bring to the meeting

  • Frame age.
  • State.
  • The number a command is tied to.

This is not

  • An approved standard.
  • A guarantee of 50 ms on every network.
  • A replacement for the C2 link.

Book a demo

See how old your image really is.

We will show the system live or measure the image age on your drone.