Do you really need fiber everywhere for private 5G?

When people picture a private 5G network, they usually picture large infrastructure. Trenches dug across a site, fiber pulled from a central hub to every antenna, months of civil works before a single device connects. It is a reasonable assumption: public mobile networks have relied on fiber backhaul for decades, so private 5G should work the same way, right? Not anymore, or at least not entirely.

Take a large infrastructure site under construction, a temporary military outpost, or an industrial plant being built from the ground up. These sites rarely stay still. New areas open, others close, and crews follow the progress of the works. Every time the site expands, the network is expected to follow along.

Relying solely on fiber means new trenches, new permits, equipment moved, and operations paused while cables are laid. Meanwhile, connected vehicles, drones, smart cameras, and sensors still need to transmit data without interruption. The same pattern shows up in emergency response or defense operations, where crews cannot always wait for a wired connection before they need to communicate.

In all these cases, the constraint is rarely the radio coverage itself. It is the cable that is supposed to carry that coverage back to the core. Think of fiber as a heavy freight train: incredibly powerful, but useless if the tracks haven't been laid yet.

The short version? A private 5G network does not need a fiber run to every single antenna.

This is made possible by Integrated Access and Backhaul (IAB). In simple terms, IAB lets a base station carry its own backhaul traffic over the same radio link it already uses to serve devices. Picture a relay race instead of a single long-distance runner: data passes wirelessly from node to node until it reaches the core, instead of traveling the whole distance on one cable. Where continuity matters most, this can be arranged with highly resilient, redundant paths (topology adaptation) rather than a single fragile chain, providing mesh-like reliability.

But the more useful question is a different one: once wireless backhaul is on the table, how do you actually decide where to still run fiber, and where not to bother?

A wireless hop is not a free substitute for a cable. Each IAB node splits its radio time and capacity between serving its own devices and relaying the traffic of every node further down the chain.

The node closest to the donor, the one wired point in the setup, ends up carrying its own load plus everything behind it. Add a few hops and that first link can become the actual bottleneck. This is also why wireless backhaul adds a small amount of latency at every hop: usually not enough to matter for standard private network traffic, but worth accounting for if a specific edge-computing use case depends on microsecond response times.

So the real question is not "fiber or no fiber". It is how much load, and how many hops, a given wireless path can realistically absorb before a wired connection becomes the better answer.

This is where the same technology earns very different verdicts depending on the scenario.

• The permanent hub: a fixed, high-traffic control room, an on-site data center, or a location carrying a lot of consistent traffic is still worth a direct fiber connection.
• The dynamic footprint: a construction site expanding section by section, a temporary deployment area for a military exercise, or a disaster zone gets far more value from wireless backhaul. The alternative is redoing civil works every time the map changes.

A single private deployment, like our NGCI (Next-Generation Communication Infrastructure), rarely needs one rigid answer. Keeping fiber at high-load fixed points and letting IAB extend the rest, with meshed paths only where interruption is strictly forbidden, is often the right call.

One detail often missed in the "fiber vs. wireless" debate: IAB does not lock you in forever.

A node connected through IAB today can be connected to fiber tomorrow, if its load grows past what the wireless link can comfortably carry, without redesigning the rest of the network around it. Choosing IAB is not a bet against fiber. It is a way to get connected now, and revisit the decision once actual field usage provides real data.

If you are responsible for connectivity on a site that keeps changing shape, the fiber question is usually the invisible anchor slowing down deployment and driving up costs.

Knowing that a private 5G network can extend itself wirelessly, dynamically, and securely changes what is realistic to ask for. It means demanding an infrastructure that grows with the site, instead of being rebuilt every time the site does.

This pragmatic approach is exactly what SMA-RTY works through with each customer: starting from a deep analysis of the operational area to decide where fiber is an investment, and where a wireless hop is the smarter tactical choice.