Helium Network Overview and Basics
LoRaWAN Networks Versus the Helium Network
LoRaWAN Network Servers Versus Helium Console/Router
Every LoRaWAN network must have a centralized network server and associated join and application servers to operate. The network server is responsible for:
- Securing and authenticating devices in conjunction with the join server(s)
- Routing / forwarding messages to the application server
- Selecting the best gateway for sending downlink messages
- Removing duplicates if the same message is received by multiple gateways
- Encrypting and decrypting messages sent to and from end devices
More background and training information on LoRaWAN network servers can be found at the LoRa Developer Portal.
LoRaWAN networks can be deployed in many different network server configurations including:
LPWAN NaaS options, where the network server function is provided as a service by the network operator.
Private LoRaWAN networks that use a private cloud instance or gateway-hosted network server. For example, the LoRa Developer Portal utilizes an instance of Chirpstack. Amazon Web Services (AWS) also provides for a LoRaWAN network server integration.
Semtech provides a developer LoRaWAN network server.
In LoRaWAN network deployments, a single logical network server is solely responsible for managing all gateways providing coverage for that LoRaWAN network.
Figure 7: All gateways in this LoRaWAN network are managed by one instance of a network server.
Roaming across LoRaWAN networks is achieved by back-end integrations between network servers. More information about roaming across LoRaWAN networks can be found at the LoRa Alliance website.
Figure 8: All Simplified LoRaWAN Roaming example
The Helium network architecture is different from LoRaWAN in that multiple Helium Routers (i.e., network server functionality) coexist on the Helium network at all times. From the perspective of a LoRaWAN end device or sensor, the router provides essentially the same functions listed above as the LoRaWAN network server. However, it also provides Helium Hotspots the ability to “route” packets received from LoRaWAN end devices to their Helium Router.
Figure 9: Helium Network Example
Module two of this series provides detailed examples of LoRaWAN end device onboarding to https://console.helium.com/, the primary developer and DIY instance of a Helium router. More information on running your own router instance and on organizational unique identifiers (OUIs) can be found at https://docs.helium.com.
In summary, the Helium network is compatible with LoRaWAN end devices and sensors. Although the Helium network architecture backend is unique and different from LoRaWAN, the IoT solution deployment process is very similar.