Deployment
Four drones, four beacons, four ages.
Corridors and convoys
You are holding an intersection. The image must be from this second.
On a convoy or a closure it is not enough that a drone hovers over an entry with a beacon on. The operator must know whether they see the entry now, or a frame from hundreds of milliseconds ago.
Needs: Fleet from one centreTwo networks at onceControl from a centre
Illustrative case study
Four intersections ahead of a convoy
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.
A city avenue, an illustration
The picture shows four drones with red and blue beacons at the intersection entries. The blink is only on screen. The beacon is not an AKIZU product.
The commander has four intersections. A drone with a beacon from another maker holds each entry. The beacon is on. That does not mean the image in the centre is valid.
In the example an entry is held only when the image is Valid. Drones hold the side streets. The avenue in the middle is clear only while age stays under the target. When one drone loses its image, that entry is not marked clear and Direct shows a neutral screen.
The convoy moves on a confirmed avenue. After the passage every intersection has a record: age, state, network switch, commands. This is not a closure plan and not a replacement for people at the intersection.
Ahead of the convoy
Only Valid entries are clear.
Outage
The beacon can be on. The entry is still not clear.
AKIZU does not supply the beacon, does not stop cars and does not run the intersection.
Image age through the example
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
Where everything stands and how the image travels
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.
Numbers in the schematic
- 1The drones are at positions set by the police plan, not by AKIZU.
- 2The convoy moves on an avenue that is clear only with a valid image.
- 3Each drone sends its frame over two networks.
- 4Platform holds the age of every entry.
- 5The commander in Direct sees which entry is held and which is not clear.
- 6After the passage every intersection has a record.
Symbols in the schematic
- BStation or launch point
- DDrone with AKIZU Brain
- S1 · S2Two mobile networks at once
- PAKIZU Platform: fleet and pack
- OAKIZU Direct: operator and image state
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
Minute by minute
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.
- T−20Drones at their positions. Every beacon is on, age not yet confirmed.
- T−10All entries in Valid. The commander sees it in Direct.
- T−5The network congests. Age at two entries rises, they stay under the target.
- T−2The drone at entry D1 loses its image. The beacon is on, the entry is not clear.
- T−1The commander decides by their own procedure. AKIZU only shows the state.
- T+3The convoy has passed. Record: age, state and network switch for every entry.
An illustration, not a deployment record. N
Use options
Everything it can be used for in this area
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 government motorcade | Police | Age and state of every entry on one screen | Brain, SIM, Platform, Direct | N |
| An emergency convoy passage | Police and rescue | A visible image loss at an entry | Brain, SIM, Direct | N |
| An oversize load | Police and haulier | An image of intersections ahead of the load | Brain, Direct | N |
| A cycling or running race | Organiser and police | Entries with age along the course | Brain, Platform, Direct | N |
| A debrief after the passage | Commander | A record for every intersection | Platform | N |
| The beacon and stopping cars | — | Not an AKIZU product | — | U |
None of these uses is deployed today. A row is not an offer and not an authorisation to fly.
Corridor schematic
Corridor schematic
Move the convoy and drop the image from one drone. An entry whose image is not valid is not marked clear.
The interactive schematic requires JavaScript.
Simulation. A beacon on the drone is a payload from another maker, not an AKIZU product. The schematic does not replace a closure plan or an authorisation.
01
The problem today
01
Several images, one pair of eyes
The operator switches between drones and does not know which image is current.
02
An entry changes before the frame arrives
A car can enter while the image still shows an empty road.
03
A beacon is not proof of freshness
The light on the drone can be on while the image in the centre has frozen.
04
The city centre congests the network
The convoy goes exactly where cells are full of phones.
05
Afterwards you need to know what was valid
Without a record it is hard to show which entry was confirmed at the time.
Without AKIZU and with AKIZU
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 |
| The pilot is in a centre far from the drone | Latency changes and the pilot cannot see it. | The deadline guard warns when a command arrives late. N |
02
How it would work
- PlanThe commander names the intersections. Platform shows which drone holds which entry.
- DeploymentDrones take their places. Each has image age and state on the panel.
- Ahead of the convoyAn entry is clear only if its image is Valid.
- During the passageWhen age exceeds the deadline, Direct shows a neutral screen at that place.
- One network failsThe frame goes via the second operator and the switch is logged.
- After the passagePlatform stores a pack for every drone and intersection.
The flow is illustrative. AKIZU is in development.
03
Mission scenario
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
Requirements and answers
| Requirement | How AKIZU answers it | Status |
|---|---|---|
| The commander sees every entry at once | Age and state of every drone on one panel | N |
| An entry with an old image is not clear | Past the deadline Direct shows a neutral screen, not the last frame | N |
| A congested city centre | Brain Duo sends every frame over two operators | N |
| A beacon on the drone | A payload from another maker. AKIZU does not control or supply it | U |
| Convoy record | A pack with image age, states and commands for every intersection | N |
| Authorisation for the closure and the flight | AKIZU does not replace it. It can supply evidence on image age | N |
- Zmeasured internally
- Mmanufacturer data, not verified by AKIZU
- NAKIZU design
- Ctarget
- Pplan
- Odesign estimate
- Unot yet known
05
Who works with it
01
Convoy commander
Sees which entry is confirmed and which is not.
02
Fleet operator
Holds the drones in place and is warned when the image stops being valid.
03
Pilot at the station
Prepares the next drone while one goes to the battery.
04
Review
Has a record after the passage of what each drone saw.
What we will measure in the pilot
- Frame age p99 at an entry≤ 50 ms C
- Entries marked clear on an invalid image0 C
- Commands executed past deadline0 C
06
What you get after every flight
- Image age and state of every drone during the convoy
- Entries that were not confirmed, and why
- Network switches at the intersections
- Commands with a frame number
- Time each entry spent in Valid
- A pack for the convoy review
Recommended products
07
Context
Beyond-line-of-sight control under SORA 2.5
EASA introduced SORA 2.5 in September 2025. A road closure and a drone flight each need their own authorisation. AKIZU does not replace them.
Latency has a numerical limit
3GPP allows 140 ms for video in beyond-line-of-sight control. The AKIZU LET-1 target is 50 ms.
Source: 3GPP TS 22.125
U-space
EU Regulation 2021/664 on U-space applies from 26 January 2023. A city corridor may fall inside such airspace.
Source: EUR-Lex 2021/664
What happens when the network fails?
The station does not show an old frame as current. When the age exceeds the deadline it switches to a neutral screen and shows the reason. We measured the switch internally within 2.72 ms.
Which networks will AKIZU use?
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.
Does AKIZU replace a BVLOS authorisation?
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.
Does the drone replace an officer at the intersection?
No. The drone gives command an image of known age. The closure decision and the people on the ground stay with the service.
Does AKIZU supply beacons?
No. A beacon, if the operation wants one, is a payload from another maker. AKIZU handles image age, not light signals.
What if one drone loses its image?
That entry is not marked clear. Direct shows a neutral screen with the reason and command knows not to treat it as confirmed.
09
What the operator sees
The three image states in this area. Proposed behaviour, to be verified in a pilot.
The entry can be marked confirmed. Age is on the panel.
The entry is not clear. Command knows the image is late.
A neutral screen. This entry is not treated as clear, even if the beacon is on.
10
How the fleet is laid out
Illustrative layout. Drone and station counts are an example, not an offer.
Drone on the entry
North entry of the intersection
Holds the place. Its image decides whether the entry is confirmed.
Drone ahead of the convoy
The next intersection
Goes ahead. Until it has a valid image, the intersection is not passed.
Spare
Command vehicle
Takes over when the first one's battery drops. The record does not break in silence.
11
How a response runs
Times are an example. They show when image age decides.
- T−20 minDeploymentDrones take the entries. The panel shows four states.
- T−5 minCheckOnly Valid entries are clear.
- T+0PassageThe convoy moves. Every drone's age is recorded.
- T+15 minPackEvery intersection has a record.
12
What we do not do in this area
Not a road closure
AKIZU does not stop cars and does not run the intersection.
Not a beacon
A light on the drone, if the operation wants one, comes from another maker.
Not a replacement for people at the intersection
The drone gives an image. The decision and the people stay with the service.
Not a response manual
The schematic on the page is a simulation of image behaviour, not a convoy plan.
A pilot in this area
You are holding an intersection. The image must be from this second.
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
Before a meeting on a corridor
The beacon can be on and the entry is still not clear.
Bring the number of entries, not a closure plan. We can show how each drone's age would hold or release an entry in a demonstration.
The red and blue beacon is not our product. The blink on the site is only on screen. The people at the intersection stay.
Bring to the meeting
- How many entries.
- Who says today that the road is clear.
- What should happen when one drone loses its image.
This is not
- Authorisation to close a road.
- Stopping cars.
- A replacement for the patrol at the entry.
Explore
Explore every area and the other sections
Twelve solution areas and the sections that belong with them. The case studies are illustrations, not completed deployments.
Solutions
01Public safety02Infrastructure inspection03Drone manufacturers04Defence and resilience05Logistics and medical transport06Industrial sites and ports07Crisis management and civil protection08Mobile operators10Search and rescue11Public events12Perimeters and airports