具有 master/slave 设置的网状网络

Mesh networks with master/slave setup

想象一下,有一个很大的物理空间 space 有 100 多个物联网设备。所有这些都通过网状网络(adhoc wifi)相互连接,每个设备都有自己的数据。由于它很大 space,wifi router/access 点只能到达 100 个节点的 10%,即 10 个节点。这 10 个节点被视为主要主节点,其余作为从节点。奴隶可以拥有自己的奴隶,也称为二级主人。所以层次结构就像任何典型的组织一样。每个人都有一个主节点,只有 10% 的主节点可以访问互联网。

目标是从所有节点收集数据并将其推送到可以托管在 AWS 或任何其他云服务上的中央数据库。这意味着每个从服务器都必须将其数据传输给它的主服务器,并最终传输给可以将其推送到云端的前 10 个主服务器。

网状网络是否支持数据重传,或者是否有任何开源网状网络软件可用于此类目的?

通常网状网络的网络堆栈会处理这个问题。网状网络的一个例子是 Zigbee。它的规范描述了三种设备类型:

来源:Wikipedia Zigbee

Zigbee devices are of three kinds:

Zigbee Coordinator (ZC): The most capable device, the Coordinator forms the root of the network tree and might bridge to other networks. There is precisely one zigbee Coordinator in each network since it is the device that started the network originally (the zigbee LightLink specification also allows operation without a zigbee Coordinator, making it more usable for off-the-shelf home products). It stores information about the network, including acting as the Trust Center & repository for security keys.[32][33]

Zigbee Router (ZR): As well as running an application function, a Router can act as an intermediate router, passing on data from other devices.

Zigbee End Device (ZED): Contains just enough functionality to talk to the parent node (either the Coordinator or a Router); it cannot relay data from other devices. This relationship allows the node to be asleep a significant amount of the time thereby giving long battery life. A ZED requires the least amount of memory, and, therefore, can be less expensive to manufacture than a ZR or ZC.

在您的情况下,您将拥有多个 Zigbee 终端设备、十个 Zigbee 路由器和一个连接互联网的 Zigbee 协调器。

维基百科页面记录了这个开源 Zigbee 实现: http://zboss.dsr-wireless.com/