EN
Book a demo

Public events

The crowd congests the network. The image has to admit it.

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

Stadium exterior at night from an empty plaza, illustrative scene, visualisation
Visualisation

Illustrative case study

A stadium, a network full of phones

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.

During

Two networks.

Alarm

Age before the patrol.

After

An export, not a coverage promise.

AKIZU is not event security and has no visitor list.

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.

ABCDBS1S2D1D2D3D4AKIZU PlatformPAKIZU DirectO123456
Schematic, not to scale. A design, not a deployment plan. N

Numbers in the schematic

  1. 1Before opening the drones take their sectors around the stadium.
  2. 2Sector C: cells full of visitors' phones.
  3. 3Two networks for each sector.
  4. 4Platform holds the age of each sector.
  5. 5The operations centre sees state and age, not a frozen crowd.
  6. 6After an alarm an export goes to the organiser.

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.

  1. 17:00Drones in sectors A to D.
  2. 18:30The gates open. The network fills.
  3. 20:15Sector C over the target. The operator does not treat it as checked.
  4. 20:16An alarm at sector B. Age is on screen before the patrol.
  5. 20:20The organiser's patrol on scene.
  6. 23:30Export: what the centre saw in which minute.

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.

UseWho uses itWhat AKIZU suppliesPartsStatus
A concert or a matchOrganiser and policeAge of each sectorBrain, SIM, Platform, DirectN
A square during celebrationsCityA visible state on a congested networkBrain, SIM, DirectN
Crowd arrival and departurePoliceAn image of routes to the gates with ageBrain, DirectN
An export for the organiserOrganiserWhat the centre saw and whenPlatformN
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

The problem today

01

The network is congested exactly during the event

Visitors and the drone share the same cell.

02

A frozen crowd looks live

The operator can watch a frame that is no longer valid for a long time.

03

Several sectors, one team

Without a state on every sector the one that dropped out is easy to miss.

04

After an incident the organiser and the police both ask

You need to show what the centre saw in that minute.

Without AKIZU and with AKIZU

The same situation, different information on the screen. Proposed behaviour, to be verified in a pilot.

SituationWithout AKIZUWith AKIZU
The image is lateThe 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 teamThe 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 failsThe image freezes or breaks up.The frame arrives over the second network; the switch is logged. N
You need to explain what happenedVideo without exposure time and without commands.Evidence package with image age, states and commands. N

02

How it would work

  1. Before openingDrones take their sectors. Platform records the baseline image state.
  2. During the eventBrain sends the image over two operators.
  3. Alarm in a sectorThe operator sees the image age before deciding on a patrol.
  4. Reduced freshnessDirect warns. The sector is not treated as checked.
  5. OutageA neutral screen with the reason, not the last frame of the crowd.
  6. After the eventA pack for every sector and alarm.

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.

Test this scenario in a pilot →

04

Requirements and answers

RequirementHow AKIZU answers itStatus
A congested event networkTwo networks and a state when neither keeps upN
Several sectors on one panelAge and state of every sectorN
Record for the organiserA pack for the sector and the alarmN
Replacing site camerasNot the aim. AKIZU adds a view from heightN
  • Zmeasured internally
  • Mmanufacturer data, not verified by AKIZU
  • NAKIZU design
  • Ctarget
  • Pplan
  • Odesign estimate
  • Unot yet known

05

Who works with it

01

Centre operator

Knows which sector is checked and which is not.

02

Event security manager

Has a record of what the centre saw.

03

Organiser

Gets an export after the event, not a coverage promise.

What we will measure in the pilot

  • Frame age p99 in a sector≤ 50 ms C
  • Sectors treated as checked during an outage0 C
  • Alarms with a pack100 % C

06

What you get after every flight

  • Frame age p99 for every sector
  • Time in Valid during the event
  • Alarms with the image state at that moment
  • Network switches under congestion
  • Sectors that were not valid
  • Export for the organiser

Recommended products

Open the selector with answers filled in →

AKIZU Platform interface, simulated data
Simulated data

07

Context

Data priority on demand has been demonstrated

Deutsche Telekom and Nokia demonstrated a temporary rise in drone priority at flight altitude. It is not an AKIZU service.

Source: Nokia

Risk assessment stays with the operator

SORA 2.5 describes the control loop including delay. AKIZU can supply evidence, not an authorisation.

Source: EASA, AirHub

08

Questions about this area

FAQ →

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.

How does image age differ from latency?

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.

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.

Can AKIZU handle a congested stadium network?

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.

Does it replace the site camera system?

No. It adds a view from height with known age. The cameras in the stands stay.

09

What the operator sees

The three image states in this area. Proposed behaviour, to be verified in a pilot.

Valid

The sector is treated as checked.

Reduced freshness

The sector is marked. The patrol is not guided by an impression.

Unavailable

Not a frozen crowd. A blank screen with the reason.

10

How the fleet is laid out

Illustrative layout. Drone and station counts are an example, not an offer.

01

Sector drone

Perimeter

Holds a slice. The network is full of phones.

02

Second drone

Entrance

Another cell, another age. The panel does not hide the difference.

03

Event centre

Control room

One team, all sectors, each with a state.

11

How a response runs

Times are an example. They show when image age decides.

  1. before openingBaselineImage state of every sector.
  2. duringWatchTwo networks.
  3. alarmDecisionAge before the patrol.
  4. afterExportFor the organiser.

12

What we do not do in this area

Not event security

AKIZU does not send stewards or police.

Not a ticketing system

We have no visitor list and do not control entrances.

Not a promise that the network will hold

We show when it does not. Whether it holds is what a pilot on site shows.

A pilot in this area

The crowd congests the network. The image has to admit it.

We are looking for first partners. The application is pre-filled for this area.

In more detail

Before a meeting on an event

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.

Bring to the meeting

  • How many sectors.
  • Who holds the alarm.
  • What the centre today treats as live.

This is not

  • Entry control.
  • A list of people.
  • Replace the security staff.