When sharing can't fail:
what public safety expects from network sharing

From dedicated radio to shared broadband

For decades, emergency services ran on their own dedicated radio networks — purpose-built systems like TETRA, engineered for one thing: staying up when everything else fails. Those networks did their job well, but they were designed for voice, not for the data-driven reality of modern incident response: live video from the scene, drone feeds, connected sensors, shared situational awareness. The successor is mission-critical broadband over 4G and 5G, standardised by 3GPP as mission-critical services (MCX), with the priority, pre-emption and security features that emergency work demands.

What is striking is how countries are building it. Very few are constructing standalone national networks from scratch. Instead, the pattern across Europe is a combination: a dedicated, government-controlled core, running over the radio networks of commercial operators — often several of them at once. Belgium's ASTRID programme shares commercial operators' radio networks through multi-operator core network (MOCN) arrangements with priority and pre-emption. Sweden's emergency network runs a dedicated core over MOCN-enabled commercial coverage. France's mission-critical network roams nationally across multiple public radio networks. In each case, the same design decision: public safety does not build its own radio layer — it shares.

The most demanding tenant on the network

This makes emergency services something new in the sharing ecosystem: a tenant that cannot accept best effort. When a network slice carries a concert livestream, a missed service level is an annoyance. When it carries the communications of a rescue operation, it is not. Public safety therefore arrives with the strictest requirements sharing has ever had to meet: guaranteed performance defined in explicit, standardized parameters; priority and pre-emption over other traffic; continuous proof — not periodic reassurance — that the agreed service levels are actually being delivered; and all of this across more than one operator's network at once.

Ultra-reliable low-latency slices make the point concrete: an URLLC slice is defined by a specific set of guaranteed quality-of-service parameters — standardized 5QI characteristics covering priority level, packet delay budget, packet error rate, guaranteed bit rates and more. A precise SLA commitment cannot be managed with a spreadsheet and quarterly review meetings. It has to be expressed, agreed and monitored in a structured, automated way.

Why this is the real test of network sharing

Here is the uncomfortable question the public safety case puts to the whole industry: if sharing arrangements today are mostly bespoke bilateral contracts, negotiated from scratch, verified by hand and difficult to repeat — how do they hold up when the tenant is one for whom failure is not an option? The honest answer is that they don't, not at scale. What the mission-critical world needs from sharing is exactly what makes sharing hard in general, only with the tolerance turned to zero: structured expression of demand, clear matching to available capacity, terms and service levels that are explicit and auditable, and monitoring that runs continuously across every party involved.

That is the layer TEASOL works on. TEASOL Exchange is built for structured demand-to-capacity matching between parties: a capacity need expressed in a structured form, matched to demand on another network, agreed under explicit terms, and monitored against its service-level agreement, transparent, repeatable and operationally realistic. The platform aligns with the same standards this world is built on, including the MOCN sharing model that public safety programmes across Europe already rely on.

And because trust in sharing stands or falls with proof, the TEASOL rApp monitors utilization of shared capacity and SLA-relevant KPIs per cell, per slice and per sharing party — turning “is the agreement being met?” from a periodic discussion into a continuous signal.

To be clear about where we stand: we are in the validation phase, testing whether structured demand-to-capacity matching holds up in real telecom environments. TEASOL does not carry any traffic, mission-critical or otherwise — the platform coordinates the sharing arrangement and monitors its service levels, not the traffic itself. But we do believe the direction of travel is unmistakable: the requirements that public safety brings to network sharing, structure, guarantees, proof, repeatability — are the requirements every serious sharing arrangement will converge on. Building for the strictest tenant is simply building properly.

Sharing as critical infrastructure

There is a larger point behind the technology. When emergency services, and increasingly other essential users, depend on shared commercial networks, the sharing arrangements themselves become part of a country's critical infrastructure and their resilience becomes a matter of public interest, not just commercial convenience. That theme, digital resilience through collaboration, also runs through the Future Network Services program in which TEASOL participates. If you work in mission-critical communications, network sharing or slicing assurance and recognize the gap between today's bespoke arrangements and tomorrow's requirements, we would be glad to compare notes.