◆ DATUM 000%
INSIGHTS
Ref. AMI-2026-021Connectivity Strategy6 min readSmart Metering & Grid ModernisationFor architecture & network teams

The Rise of Multi-Bearer Connectivity in Utilities

How cellular, RF mesh, satellite and LPWAN technologies can work together to improve resilience.

SHARE THIS BRIEFING

For most of AMI's history, a utility picked one communications technology and built the estate around it. Multi-bearer connectivity — combining cellular, RF mesh, LPWAN and, for the hardest-to-reach assets, satellite — treats that choice as a resilience decision rather than a one-time procurement.

No single bearer covers every part of a modern estate well. Cellular offers broad, flexible coverage but depends on a carrier's own infrastructure and roadmap. RF mesh is efficient and self-healing in dense clusters but needs node density to work. LPWAN reaches deep indoors and sips power but trades away speed. Satellite reaches almost anywhere, at a cost and latency that only make sense for the assets nothing else can reach.

This briefing sets out how the bearers compare, how utilities are matching them to different parts of the estate, and the technical and commercial risks that come with running more than one network at once.


01THE LANDSCAPE

Four bearers, four trade-offs

BearerCoverage profilePower useTypical fit
Cellular (LTE-M / legacy)Broad, carrier-dependentModerateUrban & suburban, flexible deployment
RF meshDense, self-forming; needs node densityLowDense urban / suburban clusters
LPWAN (NB-IoT)Broad, deep indoor penetrationVery lowDistributed, infrequent reads
SatelliteGlobal, independent of terrestrial towersHighRemote / off-grid assets, backup path
02THE MAP

Matching bearer to estate segment

The right bearer mix tends to follow geography — density and remoteness, more than any other single factor, determine what actually works reliably.

URBAN CORE Cellular + RF mesh SUBURBAN Cellular + LPWAN RURAL LPWAN + cellular fallback REMOTE / OFF-GRID satellite backup

Figure 1. Illustrative pattern — the exact mix depends on real terrain, density and existing infrastructure, but the underlying logic (matching bearer to geography rather than deploying one network everywhere) holds broadly.

03WHY IT MATTERS

Resilience needs more than one path

A single-bearer network inherits that bearer's single point of failure across the entire estate — a point made elsewhere in this series about the multi-year erosion that precedes a 2G/3G switch-off, but the same logic applies to any bearer: a carrier outage, a spectrum re-farm, or a regional coverage gap doesn't just degrade performance, it can take out communications for every device that depends on it at once.

Multi-bearer design spreads that exposure. A device or a segment of the estate with a genuine secondary path — a different carrier, a different technology entirely — keeps reporting through an event that would otherwise leave it dark, which matters most for exactly the telemetry a utility can least afford to lose.

04TECHNICAL VIEW

Six risk points worth naming

RISK-01

Single-bearer dependency

A network built on one technology inherits that technology's single point of failure across the whole estate.

RISK-02

Bearer-switching complexity

Dynamically routing a device between bearers adds logic and failure modes to the HES a single-bearer network never had.

RISK-03

Multiplied commercial overhead

Every additional bearer is a separate carrier relationship, tariff structure and renewal cycle to manage.

RISK-04

Inconsistent security posture

Each bearer has its own authentication and encryption model; a unified policy has to be engineered, not assumed.

RISK-05

Module cost & size trade-offs

Multi-bearer hardware costs more, draws more power, and complicates a device's physical design and battery budget.

RISK-06

Multiplied certification burden

Every bearer combination a device supports needs its own certification and field trial before it's trusted at scale.

05WHAT TO DO ABOUT IT

Building a multi-bearer strategy

1

Segment the estate by geography and criticality first

Choose bearers to fit the segment, not the other way round.

2

Treat backup bearers as tested failover paths

Exercise them, don't just provision them.

3

Centralise bearer management in the HES

So switching logic is visible and auditable, not buried in device firmware.

4

Negotiate carrier contracts with whole-estate resilience in mind

Not bearer by bearer in isolation.

5

Budget certification time for every combination deployed

Not just the primary bearer.


Multi-bearer connectivity isn't about chasing the newest network technology — it's about not letting the estate's resilience depend on a single carrier's coverage map or a single technology's roadmap. The utilities getting the most from it are matching bearers deliberately to geography and criticality, and treating the redundancy as something to test, not just something to provision.

✦INTERACTIVE · ESTATE CONNECTIVITY FLOW

How a read moves across the estate

01→
DEVICE
meter / grid asset
02→
BEARER
cellular · mesh · LPWAN
03→
HEAD-END
ingest · join · command
04→
DATA PLATFORM
MDM · analytics · billing
05◆
OPERATIONS
billing · grid · customer

HOVER OR TAP A STAGE TO EXPAND TECHNICAL SPECS

+DEEPER CONTEXT

Why no single bearer is enough

Each bearer fails a different segment of the estate: cellular thins at the rural edge, RF mesh struggles in dense urban interference, PLC degrades with grid topology. A single-bearer design optimises one failure mode and ignores the others.

Multi-bearer is now an architecture decision — where the fallback sits, how the estate fails over, and how reads are deduplicated across paths — not a bolt-on resilience feature.

HEAD-ENDCELLULARRF MESHPLC
Figure. Each bearer covers a different gap; the architecture decides how they combine.
§ABOUT THE AUTHOR
Chris Gales
CEHG · CONNECTIVITY CONSULTANCY

Chris Gales

Chris Gales leads CEHG. He converts complex technical and commercial choices into clear decisions and dependable outcomes for utilities running connected device estates at scale.

He writes these field notes from the practice — on bearer migration, smart metering architecture, procurement and operations — to help estates start counting down early.

CONNECT ON LINKEDIN
Prepared for utility architecture, network, and grid-modernisation teams.
SHARE THIS BRIEFING
READER SURVEY · 30 SECONDS

Was this briefing useful?

A quick signal helps us write sharper field notes. Your responses are anonymous.

HOW USEFUL? (1–5)
WAS IT CLEAR?
WOULD YOU RECOMMEND CEHG?
DELIVERED QUARTERLY

Get the field notes in your inbox

Bearer migration, architecture and procurement commentary from our practice — no marketing fluff.

§05 — THE CONTRACT

Talk to us about
your device estate

Most engagements start with a short conversation about the estate, the deadline and the decision you need to make. We will tell you plainly whether we can help.

BASEUnited Kingdom
Hover the footer — the button follows your cursor.
CEHG — Connectivity Consultancy Throughout the Enterprise
© 2026 CEHGCONTACTCONNECTIVITY EXPERTISEAMI STRATEGYINDEPENDENT · SENIOR-LED · UK◆ STRUCTURAL KINETICISMv1.0.0
§ COOKIE NOTICE

This site stores a small set of essential cookies to remember your preferences, and uses analytics cookies to understand how the site is used. No advertising cookies are set. See our contact page to ask about the data we hold.