Most private 5G conversations begin in the same place, focusing on automation, AGVs, robotics, connected workers, deterministic control, and industrial performance. It’s where the technical and financial case is clearest.
However, once private 5G is live within a facility, a second, often unexpected, problem tends to surface. “Our machines are connected, but our people still don’t have mobile coverage.”
This isn’t a fringe issue. In many enterprise environments, such as factories, warehouses, distribution centres, hospitals, campuses, and retail stores, public cellular coverage indoors can be weak or non-existent.
This is because steel structures, thick walls, large floorplates, and remote geographies all interfere with operator signals:
- Employees can’t reliably make voice calls
- Collaboration apps struggle
- Two-factor authentication apps fail
- Visitors lose service
- Emergency calling becomes a concern
That last point is particularly concerning. If someone needs to call emergency services and there’s no signal, it becomes a liability issue.
When Private 5G Solves One Problem, But Exposes Another
Looking at a practical customer example, Del Conca (a tile manufacturer) successfully deployed private 5G to support AGVs, forklifts, and factory automation. Operationally, the network performed extremely well, but after deployment, leadership raised concerns that employees inside the facility still lacked reliable public cellular coverage. Emergency calling remained a risk, and from their perspective, that was unacceptable.
This is the moment many enterprises reach an architectural crossroads.
The traditional solution would be to deploy a Distributed Antenna System (DAS) or some parallel indoor carrier system. But that means:
- A second physical infrastructure
- Additional cost
- Additional operational overhead
- Additional integration complexit
In other words, duplication.
A Unified Infrastructure Model
The alternative is a Neutral Host approach. Rather than building one system for private enterprise traffic and another for public carrier traffic, a single private 5G infrastructure can support both while keeping traffic completely separate.
At a high level the same access point broadcasts:
- A private enterprise network identity
- One or more public operator network identities
This is conceptually similar to broadcasting multiple SSIDs from a Wi-Fi access point.
Devices behave as they normally would:
- Enterprise tablets, scanners, and private 5G devices attach to the private network.
- Smartphones with mobile network operator SIMs attach to their operator network.
From there, traffic separation is strict.
- Private traffic routes directly into the enterprise LAN.
- Carrier traffic is kept completely separate and tunnelled securely through a Multi-Operator Exchange Gateway to the respective mobile operator.
There is no mixing of traffic domains, and from the end user’s perspective, it’s seamless. Employees and visitors walk into the building, and their phones simply work. Voice calls, messaging, video streaming, collaboration apps, and emergency services all operate normally. They don’t know they’re using shared infrastructure, and they don’t need to.
Why This Matters Strategically
This model does more than fix signal bars; it:
- Eliminates the need for a separate DAS deployment
- Avoids parallel cellular systems
- Consolidates indoor coverage under a single infrastructure
- Preserves strict traffic separation
It also aligns with a broader principle that runs through this entire series: private 5G becomes enterprise infrastructure when it consolidates complexity rather than multiplying it.
If you’ve already invested in private 5G for operations, extending that infrastructure to address indoor public coverage can significantly improve the overall value equation, addressing both productivity and privacy concerns.
A Practical Evaluation Framework
If indoor coverage is a known issue, ask:
- Is poor public cellular coverage affecting productivity or safety?
- Are we planning to deploy a separate DAS or a parallel system?
- Can our private 5G infrastructure support both private and public identities?
- Can we enforce complete traffic separation between enterprise and carrier traffic?
If the answer to the second question is “yes,” it’s worth challenging that assumption, as duplication is often inherited from older architectures but is not always required.
The Bigger Picture
Private 5G isn’t just about connecting machines. It’s about creating a unified cellular fabric within the enterprise that serves operations, employees, visitors, and safety requirements at the same time. When done correctly, it’s not private versus public; it’s one infrastructure, two domains, fully separated yet working together.
What to do next:
If your facility struggles with indoor mobile coverage, don’t treat it as a separate telecom issue. Evaluate whether your private 5G design can extend to public cellular support, safely, securely, and without duplicating infrastructure.
