The problem Z-Mesh is solving

TLDR: Interoperability, Scalability & Vendor-neutrality

Z‑Mesh solves fragmentation in IoT connectivity by enabling low‑power devices, IP-connected devices and IP-connected applications from different vendors to communicate directly, in a mesh. It eliminates costly custom protocol bridges and vendor lock‑in, extends network range via multi‑hop routing, and makes integration with cloud and edge systems simpler by using standard, interoperable networking.

The IoT landscape is dominated by fragmented, proprietary, supplier-specific ecosystems. While effective within a particular ecosystem, such an approach limits the ability to scale and integrate, constraining the impact of IoT deployments and driving up costs.
-- McKinsey 2021 report (opens new window)

What is Z-Mesh?

Z‑Mesh is an open wireless layer-3 IoT networking protocol and ecosystem designed for low-power IoT devices, IP-connected devices and IP-connected applications, to interoperate directly (mesh networking) and avoid vendor lock‑in.

Z‑Mesh makes devices interoperable so they can communicate directly. Having a unified namespace enables allow any device or app to retrieve all Content (eg. temperature in the meeting room). The unified namespace and data models enables interoperability and remove the need for expensive integration. Adding devices increases usable network value - this is also called the Network Effect.

Z-Mesh runs on top of any type of physical layer and can be integrated in any type of application. Just like the Internet protocol (IP) - standardization enables interoperability which in turn enables scalability.

IP: The one thing every internet-connected device has in common, is the IP protocol. The IP protocol runs on top of many different types of links, and many different types of applications runs on top of the IP protocol. This means that any IP device can access any other IP device; enabling the network effect.

Z-Mesh: The one thing every IoT device or application has in common, is the Z-Mesh protocol. The Z-Mesh protocol runs on top of many different types of links, and many different types of applications runs on top of the Z-Mesh protocol. This means that any Z-Mesh device can access any other Z-Mesh device; enabling the network effect.

How to achieve interoperability?

Metcalfe’s law (opens new window) when applied to IoT, says, the value of an IoT network (solution) is proportional to the square of the number of addressable pieces of Content Names. That is: If all data produced can be retrieved by any Consumer, you have maximum value.

A Unified Namespace allows Content Producers and Consumers to be properly routed and connected within the network, enabling communication and data exchange between them. Without unique Content Names (addressing), the network would not be able to effectively route and deliver Content, limiting the overall connectivity and value of the network.

As the network grows, the number of connected devices and systems increases exponentially. Robust addressing schemes (a Unified Namespace) are necessary to accommodate this growth and ensure that the network can scale effectively, maintaining the network effect as the number of connected entities expands.

A Unified Namespace enables interoperability between different devices and systems within the network. This interoperability is crucial for realizing the full potential of the network effect, as it allows diverse entities to seamlessly communicate and collaborate.

A Unified Namespace facilitates the management and control of the network, allowing administrators to monitor, configure, and troubleshoot individual devices or systems. Effective network management is essential for maintaining the stability and reliability of the network, which is a key factor in achieving the network effect.

The Network effect - Metcalfe's law

Integrating devices that use different connectivity protocols is a complex task. Issues include; protocol translation complexity, security model differences, management and monitoring fragmentation, no unified namespace (addressing) and discovery inconsistencies, data model and semantic mismatches, vendor lock-in and proprietary extensions. Imagine making an integration between device that use HTTP/CoAP and devices that use MQTT - this integration must define a custom mapping between the two namespaces (addressing) and also define security, data-model, discovery, management and monitoring; Also, every time a new device is added a new mapping and security must be setup. Integrating verticals does not scale!

The value of a telecommunications network is proportional to the square of the number of connected compatible communicating devices
-- Bob Metcalfe (opens new window)

Z-Mesh enables the network effect by providing a universal, vendor‑neutral communication layer that any device, service or application can use - just like the telephone network. A unified namespace lets every new device or service become reachable by all others and applications can access any piece of Content in a secure and controlled manner without custom integration. Because integration cost is low and connectivity scales predictably, each time a new device or service is added, the value of the overall network is increased.

Privacy-by-Design

In Host based communication models, like LoRaWAN and IP, the sensor-data is tunneled in an encrypted channel; Once it reaches it's destination, it resides there unencrypted! Obviously this is a huge security risk.

With Z-Mesh, being an ICN architecture, the sensor-data itself is encrypted and has a name attached to it. This allows any device to ask for sensor-data with that name or to forward or cache the sensor-data. Only devices with the encryption key can decrypt and use the data. With Z-Mesh, data is always transmitted and stored in encrypted form, this provides the network-manager full control over who can use the data.

Why ICN and not IP?

The Internet protocol is successful because it is royalty-free networking layer standard that allows direct communication using the same naming-scheme like sensor.your-domain.org. However, it is 50 years old, designed in the era of the telephone and is therefore host-centric networking architecture in which data exchanged in channels (client calls server). The IP-protocol an is bad fit for IoT as it does not support offline devices, lacks support for mobile data-producers and is too complex for constrained devices.

Z-Mesh is an information-centric networking (ICN) architecture. It focuses on named data (content) rather than host addresses, routing and caching content by name across the network. It enables in-network caching, name-based security, and receiver-driven data retrieval to improve efficiency, mobility, and resilience.