During
Two networks.
Public events
At an event one cell holds many phones. A drone over a sector can have an image that looks live and is late. The centre needs a number, not an impression.
Needs: Fleet from one centreTwo networks at onceEvidence after the flight

Illustrative case study
This is not a customer and not a flight that happened. It is a description of how this area would read if the image carried its age.
An event perimeter, an illustration
Before opening the drones take their sectors. During the concert the cells hold visitors' phones. The image can look live and be late.
In the example sector C jumps over the target. The operator does not treat it as checked. The screen does not show a frozen crowd. It shows state and age.
After an alarm a pack goes to the organiser: what the centre saw in that minute. The cameras in the stands stay.
Two networks.
Age before the patrol.
An export, not a coverage promise.
AKIZU is not event security and has no visitor list.
The chart requires JavaScript.
The chart is a simulation. Move the slowdown and see when the example stops being under the 50 ms target. The target is not a measured result.
Deployment schematic
The schematic is not to scale and is not a design for a specific site. It shows where the drone is, which two networks carry the frame and where the decision is made.
Red and blue beacons: police, state, the military in training. Orange: everyone else. The blink is only on screen. Schematic, design. The list beside it explains the codes in the drawing. The beacon is a payload from another maker, not an AKIZU product.
Concrete case
The same illustrative case as above, written out in time. The times are an example. It is not a record of a flight that happened.
An illustration, not a deployment record. N
Use options
Each row is a separate use. The Parts column says which AKIZU parts it would involve. Status N is a design, C is a target, U is unknown.
| Use | Who uses it | What AKIZU supplies | Parts | Status |
|---|---|---|---|---|
| A concert or a match | Organiser and police | Age of each sector | Brain, SIM, Platform, Direct | N |
| A square during celebrations | City | A visible state on a congested network | Brain, SIM, Direct | N |
| Crowd arrival and departure | Police | An image of routes to the gates with age | Brain, Direct | N |
| An export for the organiser | Organiser | What the centre saw and when | Platform | N |
| Entry control | — | Not AKIZU | — | U |
None of these uses is deployed today. A row is not an offer and not an authorisation to fly.
01
Visitors and the drone share the same cell.
The operator can watch a frame that is no longer valid for a long time.
Without a state on every sector the one that dropped out is easy to miss.
You need to show what the centre saw in that minute.
The same situation, different information on the screen. Proposed behaviour, to be verified in a pilot.
| Situation | Without AKIZU | With AKIZU |
|---|---|---|
| The image is late | The image looks live; the pilot does not know how old it is. | Frame age is on the screen and the state changes to Reduced freshness. N |
| Several drones, one team | The operator does not know which image is current. | Every drone has its own age and state. An old image is not treated as confirmation. N |
| One network fails | The image freezes or breaks up. | The frame arrives over the second network; the switch is logged. N |
| You need to explain what happened | Video without exposure time and without commands. | Evidence package with image age, states and commands. N |
02
The flow is illustrative. AKIZU is in development.
03
How many metres further the drone is than the image shows. Pick a scenario or set the speed and image age.
The interactive calculation requires JavaScript.
Scenario speeds are examples. 87.4 ms is the p99 measured internally over WiFi with a phone as transmitter, not on a drone.
04
| Requirement | How AKIZU answers it | Status |
|---|---|---|
| A congested event network | Two networks and a state when neither keeps up | N |
| Several sectors on one panel | Age and state of every sector | N |
| Record for the organiser | A pack for the sector and the alarm | N |
| Replacing site cameras | Not the aim. AKIZU adds a view from height | N |
05
Knows which sector is checked and which is not.
Has a record of what the centre saw.
Gets an export after the event, not a coverage promise.
06

07
Deutsche Telekom and Nokia demonstrated a temporary rise in drone priority at flight altitude. It is not an AKIZU service.
Source: Nokia
SORA 2.5 describes the control loop including delay. AKIZU can supply evidence, not an authorisation.
LTE and 5G. The Brain Duo concept sends every frame through two operators at once. The 3GPP standard expects the network to recognise a drone in the air, so we plan AKIZU SIM cards with an aerial profile at the operator.
Network latency is only part of the journey. Image age is the time from frame exposure on the drone to its display to the operator. VERA attaches the exposure time to every frame and the station verifies it before display.
No. BVLOS flights need an authorisation in the Specific category based on a SORA 2.5 risk assessment. AKIZU Platform is meant to give the operator an image-age record as evidence for that assessment.
The design sends the frame over two operators and shows when neither keeps up. Whether that is enough at a given stadium is what a pilot shows.
No. It adds a view from height with known age. The cameras in the stands stay.
09
The three image states in this area. Proposed behaviour, to be verified in a pilot.
The sector is treated as checked.
The sector is marked. The patrol is not guided by an impression.
Not a frozen crowd. A blank screen with the reason.
10
Illustrative layout. Drone and station counts are an example, not an offer.
Perimeter
Holds a slice. The network is full of phones.
Entrance
Another cell, another age. The panel does not hide the difference.
Control room
One team, all sectors, each with a state.
11
Times are an example. They show when image age decides.
12
AKIZU does not send stewards or police.
We have no visitor list and do not control entrances.
We show when it does not. Whether it holds is what a pilot on site shows.
A pilot in this area
We are looking for first partners. The application is pre-filled for this area.
Other areas
Example deployments are illustrative. AKIZU is in development and does not replace a BVLOS authorisation.
In more detail
Phones in the cells are not our subject. Image age is.
During a concert the image can look live and be late. A sector over the target is not treated as checked.
We are not event security and we have no visitor list. The cameras in the stands stay.
Explore
Twelve solution areas and the sections that belong with them. The case studies are illustrations, not completed deployments.