When communication systems fail during an emergency, it’s rarely because everything stops working at once. More often, individual pieces break down: cellular networks become overloaded, internet backhaul disappears, or power becomes unreliable.
The lesson learned from decades of emergency communications is simple:
Resilience comes from layered systems, not a single perfect tool.
At EmergencyHam.net we are experimenting with a practical messaging bridge architecture that connects local mesh radio networks, amateur radio messaging systems, and everyday devices such as smartphones.
The goal is straightforward: allow messages and telemetry to move across whatever networks remain available.
A Layered Communication Model
Instead of building a single monolithic communications system, the EmergencyHam gateway acts as a message exchange point between multiple networks.
These networks may include:
- Meshtastic LoRa mesh
- MeshCore LoRa mesh
- Phone text messaging (SMS-style interfaces)
- APRS messaging
- Winlink store-and-forward email
Each network connects through an adapter that translates between its native format and a common internal message structure called EMP (Emergency Message Protocol).
EMP provides a unified message model that allows different communication subsystems to interoperate by exchanging a limited set of common message types, independent of the specific requirements or limitations of any individual network.
Rather than attempting to reproduce the full capabilities of every system, EMP focuses on the small set of message behaviors that can be shared across them all.
This design allows traffic to move between networks depending on availability, priority, and delivery requirements.
EMP as the Interoperability Layer
EMP is intentionally minimal.
It defines only the message primitives needed to support interoperable communications across heterogeneous networks.
In that sense, EMP plays a role similar to other foundational interoperability layers:
- IP unified many different physical network technologies
- SMTP allowed email systems to exchange messages
- MQTT enables distributed message systems to communicate through simple publish/subscribe semantics
EMP applies the same principle to emergency communications.
Instead of tying applications to a specific radio technology, EMP represents message intent.
For example, a simple “wellness check” or “sensor alert” can be represented as a standard EMP message. Each network adapter then translates that intent into its own native format.
This approach allows new communication systems to be added without redesigning the application layer.
Development Roadmap
Rather than trying to connect every communications system at once, the bridge is being built in stages.
Phase 1 — Meshtastic and Phone Messaging
The first stage links Meshtastic mesh messaging with simple phone text messaging.
Both transports connect to the gateway through EMP adapters.
The gateway:
- Receives a message from Meshtastic
- Converts it into an EMP frame
- Routes it to the phone messaging adapter
- Sends responses back through the mesh
Importantly, the phone interface is not simply a user console for the mesh.
It is treated as another network transport operating at the same EMP level.
This phase validates the core EMP message model and routing logic.
Phase 2 — MeshCore Integration
The second stage introduces support for MeshCore mesh networking.
Adding MeshCore demonstrates that the system can support multiple mesh ecosystems simultaneously.
Messages from either mesh network can be normalized into EMP frames and routed across other available transports.
Phase 3 — Amateur Radio Messaging Systems
Once the mesh adapters are stable, the next step is connecting to established amateur radio messaging systems such as:
- APRS messaging
- Winlink email relay
These networks provide long-distance store-and-forward capability, allowing information originating on a local mesh network to travel beyond the immediate radio coverage area.
Practical Examples
Two simple examples illustrate how this layered messaging model might work in practice.
Wellness Check
During emergency operations or public service events, maintaining awareness of team status is essential.
A simple workflow might look like this:
- Field operators send periodic check-in messages over a mesh network.
- The gateway tracks acknowledgements from command stations.
- If several check-ins are missed, the system generates an escalation alert.
Routine traffic remains lightweight, while the system still provides accountability and exception awareness.
Water Leak Alert
Sensors provide another valuable application.
For example, a water leak sensor deployed in a remote building might trigger an alert when a leak is detected.
- The sensor sends a telemetry message across the local mesh network.
- Nearby operators receive immediate notification.
- The gateway can later forward a richer incident report through long-distance messaging systems such as Winlink.
This combination provides fast local awareness with resilient escalation paths.
Educational Value
One of the primary goals of EmergencyHam.net is hands-on learning.
Projects like this allow students and new operators to explore multiple technical disciplines at once:
- radio communications
- networking and distributed systems
- embedded electronics and sensors
- software development
- resilient system design
A student might deploy a sensor, watch its telemetry move across a LoRa mesh network, pass through a gateway, and appear on a remote dashboard.
At the same time, experienced amateur radio operators can mentor students on:
- propagation and antenna design
- interference mitigation
- operating practices
- regulatory considerations
This kind of intergenerational collaboration is central to the EmergencyHam.net mission.
The EMP V1 Protocol
The technical details of the EMP messaging model are described in the EmergencyHam Message Protocol (EMP) V1 Draft.
EMP defines:
- compact message frames for low-bandwidth radio links
- structured message types such as
TXT,CMD,ACK, andTLM - duplicate suppression and retry behavior
- fragmentation rules for larger messages
EMP is designed to be simple enough for embedded systems while still supporting reliable communication workflows.
The full draft specification is available here:
EmergencyHam Message Protocol (EMP) V1 Draft
Why This Matters
Emergency communications shouldn’t depend on a single network or technology.
They should be built from interoperable layers that support each other.
By connecting mesh networks, amateur radio systems, and everyday devices like smartphones through a common messaging model, we can create systems that remain useful even when normal infrastructure fails.
Just as importantly, we can use these systems to teach the next generation how resilient communications actually work.
Get Involved
If you are interested in:
- reviewing the EMP protocol
- developing gateway software
- experimenting with mesh networks
- field testing sensors and telemetry
we would welcome your input.
EmergencyHam.net is built through collaboration between radio operators, developers, educators, and makers.
Leave a Reply