can accommodate thousands of end nodes, and typical range is 2km in urban areas and around 15km in
rural areas with clear line of sight.
- LoRaWAN server: this is a service provided by a 3rd party company (hence the user needs to subscribe
to such service). As LoRaWAN packets are encrypted, the LoRaWAN server proceeds with deciphering
of LoRaWAN packets and make them available to user’s application server through various
communication protocols (this is totally dependant on the LoRaWAN service provider, but HTTPS,
WebSocket and REST are widely used protocols besides direct integration with IoT platforms like
Microsoft Azure or AWS IoT). An API is then provided to access deciphered data, device EUI and other
radio parameters (usually in JSON or XML format).
10.2 Integrating TBS12B/TBS12S in a LoRaWAN ecosystem
To build a private network of TBS12B/TBS12S, it is first required to choose a LoRaWAN gateway (eg
www.kerlink.com, www.multitech.com, …) and a LoRaWAN services provider (eg www.loriot.io, …).
TBS12B/TBS12S are compatible with any LoRaWAN certified gateway and network service provider.
This choice is dependant on several criteria:
- Geographic area where the sensors will be deployed: this determines the LoRaWAN frequency plan to be
used. The gateway must then have required HW to support these frequencies (eg 868MHz, 915MHz,
etc…)
- Gateway connectivity: depending on where the gateway will be installed, next options need to be
considered,
o Indoor / outdoor model
o Connectivity: Ethernet, cellular, wifi
- The LoRaWAN service provider:
o Needs to support the chosen gateway (because it will be programmed to access the selected
LoRaWAN service provider)
o Must support the frequency plans required by the user
o Must support the LoRaWAN features required by the user (eg LoRaWAN downlink, Class C,
OTAA, etc…)
o Provides a suitable interface for the user so the application server can collect deciphered data (eg
JSON/XML API reachable through Websocket, REST, etc…)
o Must be ideally located in the same region where end nodes are deployed, to avoid latenties (eg
end nodes in Vietnam, LoRaWAN server in Singapore but not in Germany)
o Support of multiple applications/accounts, scalability of the server, …
o Pricing model: subscription based, billing per gateway and end nodes, etc…
The next step is to activate each end node so they are identified and can communicate with the LoRaWAN network.
LoRaWAN standard defines 2 ways of activating end nodes:
- Activation By Personalization (ABP): with this configuration, the end node is bound to a specific LoRaWAN
network. This mode is supported by default in TBS12B/TBS12S, and can be compared to a smartphone
that is SIM-locked to a specific cellular network.