A systems tour at 35,000 feet

How a movie
crosses an airplane.

A passenger presses play. What follows is not a trip to the internet, but a precise journey through a small, resilient edge network carried inside the aircraft.

01 — Head-end

It starts in a rack.

Deep in the aircraft, the IFE head-end stores the media library and runs the control software. It is a compact data center designed to fly.

The useful mental model: this is not “a screen with a movie.” It is a distributed computer network inside the fuselage.
storagecontrol
02 — The request

You tap “Play”.

The seat sends a small control request upstream through the cabin network. It identifies a title and a session; the heavy video has not started moving yet.

Direction matters: seat → network → server. The orange pulse makes the return trip only after the service resolves the request.
03 — Backbone

The cabin has a spine.

A high-bandwidth cabin LAN runs the length of the fuselage. The backbone connects the head-end with zonal distribution points; local runs continue towards groups of seats.

The route is physical: head-end → backbone → zone → seats.
04 — Area distribution

Routers fan the cabin out.

Area Distribution Boxes act like zonal switches. One upstream connection becomes many local paths, keeping the cabin organised in manageable sections.

Redundant designs can provide an alternate route if a cable or distribution point is unavailable.
05 — Edge cache

The movie moves closer.

In seat-centric systems, content can be stored near the passenger. Playback can stay local to the seat instead of continuously pulling a film from the central server.

The architectural trick is simple: move compute and storage toward the edge.
06 — Inside the seat

A seat is a computer.

The Smart Display Unit includes a processor, decoder, operating system, storage and passenger UI. Other electronics provide power, audio, connectivity and control.

The screen is only the visible end of a distributed system.
07 — Playback

Now the pixels move.

The local media file is read from storage, decoded in hardware and rendered on the display. Audio follows its own seat-level path.

For local playback, the central server can be nearly irrelevant to the frame-by-frame loop.
08 — Shared streams

One source. Many viewers.

Live television and shared announcements can use multicast. A stream travels through the backbone and switches replicate it only towards seats that joined the channel.

One source → many viewers, rather than a separate full stream for every screen.
09 — Beyond the cabin

Some data comes from space.

Ku- and Ka-band connectivity can bring internet traffic and live services to the aircraft. Once onboard, that traffic joins the cabin distribution system.

Satellite is the bridge to the outside world. The cabin LAN is the network inside the aircraft.
10 — Safety boundary

Entertainment is not flight control.

IFE can ingest selected flight information for maps and respond to cabin events, while remaining electrically and logically separated from flight-critical systems.

The relationship is deliberately asymmetric: read useful aircraft data; never become a control path.
The whole picture

A flying edge network.

Central servers hold content and control. Zonal switches distribute traffic. Seat computers decode it close to passengers. Connectivity reaches outward only when it needs to.

Head-end → backbone → zone → edge → decoder → screen
Scope & sourcesThis is a conceptual cabin-network model: implementations vary by aircraft and supplier. The boundary between passenger systems and flight-critical systems is a certification requirement, not an animation convention. See EASA air-operations guidance and Aviation Today’s IFE systems overview.