Home Support Blog

IATA Smart Airport Roadmap 2030: 2026 Large-Scale Implementation, Global Airport Network Upgrade Trends & Key Projects

Release date:2026-11-10

Airport networks stopped being a utility and became operational infrastructure: once identity checks, baggage tracking and stand-side operations all depend on the network, a slow link is a queue at security rather than a slow web page. Rayin (Shenzhen Rayin Technology) is a manufacturer of GPON OLTs and industrial Ethernet switches. The driver is not one document but a set of IATA programmes for identity and processing that all assume the terminal has a network capable of moving identity, video and operational data reliably and separately.

KEY TAKEAWAYS
  • IATA's One ID framework replaces repeated document checks with a single verified identity, which turns the check-in, security and boarding touchpoints into network endpoints that must stay up.

  • NEXTT describes where the work moves: off-airport processing, advanced processing in the terminal, and interactive decision making. Each one adds network endpoints outside the building.

  • Segmentation is the design decision that matters. Passenger Wi-Fi, operational systems and safety-related traffic should not share a broadcast domain, however convenient that is to build.

What do the IATA programmes actually require of a network?

The programmes are worth reading as network requirements rather than as passenger-experience slides.

ProgrammeWhat it doesNetwork implication
Single-token identityOne verified identity across check-in, bag drop, security and boardingEvery touchpoint becomes a latency-sensitive endpoint
Ready to FlyIdentity verified before arrival at the terminalProcessing moves off-site, adding remote endpoints
NEXTT — off-airport activitiesProcesses happen outside the terminalCity check-in sites need secure connectivity back
NEXTT — advanced processingAutomation and biometrics in the terminalCamera density and uplink capacity rise sharply
NEXTT — interactive decision makingReal-time tracking of flights, bags and shipmentsOperational data becomes time-sensitive

IATA has published forecasts of air travel demand roughly doubling over the coming decades, with several billion passengers a year by the mid-2030s. Whether or not any individual airport hits those numbers, the planning conclusion is the same: terminals cannot physically expand fast enough, so throughput has to come from processing efficiency, and processing efficiency is a network problem.

The participating airports in the NEXTT work — including Dubai, London Heathrow, Bangalore, Amsterdam Schiphol and Shenzhen — are instructive because they are all doing the same three things: adding cameras, adding identity endpoints, and moving some of the processing away from the terminal.

Where does the traffic actually go?

An airport network is really several networks that happen to share a building.

DomainTrafficDesign requirement
OperationalBaggage, stands, ground handling, AODBHigh availability, own VLAN, priority queuing
Safety and securityCCTV, access control, screeningBandwidth-heavy, retention-driven, isolated
Passenger-facingWi-Fi, wayfinding, digital signageHigh density, untrusted, throttled
Airline and handlingDCS, gate systems, load controlSegmented per tenant

Camera count is the number that surprises people. A terminal upgrade routinely adds hundreds of cameras, each contributing a few megabits, and enforcement-grade recording pushes per-camera bitrates up again. That is an uplink and aggregation problem, not an access-layer one — which is where 10G fibre uplinks and a proper aggregation design earn their cost.

How do you phase the work without closing a terminal?

Airport upgrades run alongside live operations, which makes phasing the hard part rather than the technology. The sequence that tends to work:

  1. Build the operational network first. Operational and safety systems move onto the new core before any passenger-facing change, so the critical domains are on new hardware while the old network still carries the rest.

  2. Migrate tenant by tenant. Airlines and handlers move on their own windows, which argues for per-tenant VLANs or VRFs from the start rather than a flat network.

  3. Cut passenger services last. Wi-Fi and signage are visible but not safety-critical, so they absorb the remaining risk.

  4. Keep the old network alive for a full season. Running both in parallel through one peak period costs less than an outage during one.

The physical constraint that shapes all of this is cable route availability. Lifting floors and ceilings in an operating terminal is slow and expensive, which is one reason passive optical designs attract interest: a single fibre can replace a copper chain and free up containment for the next decade of changes.

What should be specified for a 2026 upgrade?

  1. Separate VLANs per domain, enforced at the port. Operational, security and passenger traffic should not be able to flood each other. Private VLAN or port isolation helps where tenants share hardware.

  2. Protected uplinks. Dual fibre on physically separate routes, or a ring protocol with sub-50 ms recovery. A cut uplink should not silence a pier.

  3. PoE budgeting by camera count. Add the draw of every camera and AP, then leave headroom for the day all of them run at full bitrate.

  4. Industrial hardware outside the terminal. Aprons, baggage halls and perimeter cabinets are not conditioned equipment rooms: wide temperature, fanless, DIN-rail or wall-mount, with surge protection on long copper runs.

  5. Manageability. SNMP, CLI, configuration backup and a documented firmware baseline — a network that cannot be audited cannot be run at airport scale.

Airplanes on an airport apron

FAQs

Is the IATA Smart Airport Roadmap a single document with deadlines? Not in the way a regulation is. These are programmes with published frameworks and participating airports; implementation timing is set by each airport and its regulators.

Why does a single-token identity matter to the network? Because it removes paper fallbacks. Once identity is verified at a networked touchpoint, that touchpoint has to stay up, and its latency becomes passenger queue time.

How much bandwidth does airport video need? Scale by camera count and resolution rather than by a rule of thumb: hundreds of cameras at several megabits each, more for enforcement-grade recording, all hitting the same aggregation point.

Should passenger Wi-Fi share the operational network? No. Keep them on separate VLANs with the passenger side treated as untrusted and rate-limited. Convenience in cabling is not worth a shared failure domain.

Do apron and perimeter cabinets need industrial switches? Yes. Those locations have temperature extremes, dust, long cable runs and no cooling, which is exactly what industrial hardware is specified for.

Related Reading

  1. How to size PoE ports and power by camera count

  2. Wi-Fi 7 backhaul: PoE and switch requirements

  3. PoE switch power and bandwidth for IP cameras

  4. Network segmentation: VLANs and IP subnets for campuses

  5. F5G all-optical campus: PON vs switch

  6. Dual uplink protection when one link fails

  7. Managed industrial switch TCO: the real five-year cost

About the author: Sara is a Customer Manager at Rayin with over 10 years of experience in the communications field. In her free time, she enjoys badminton and swimming.

Connect with Sara on LinkedIn


About Rayin: Shenzhen Rayin Technology Co., Ltd. — company profile


Get A Quote

You have agreed to this website’s《Privacy Policy》