LoRa Server implements all regional bands that are defined by the ISM bands specified by the LoRa Alliance LoRaWAN Regional Parameters 1.0 document. Note that each region has different frequencies and settings on which the LoRaWAN protocol operates, to comply to local regulations.
LoRa Server implements LoRaWAN Class-A, Class-B and Class-C, making it ideal for different purposes. Note that for all supported device-classes both unconfirmed as confirmed data is supported (in the latter case an acknowledgment will be sent by the receiving party).
End-devices of Class A allow for bi-directional communications whereby each end-device‘s uplink transmission is followed by two short downlink receive windows. The transmission slot scheduled by the end-device is based on its own communication needs with a small variation based on a random time basis (ALOHA-type of protocol).
End-devices of Class B allow for more receive slots. In addition to the Class A random receive windows, Class B devices open extra receive windows at scheduled times. In order for the End-device to open it receive window at the scheduled time it receives a time synchronized Beacon from the gateway.
End-devices of Class C have nearly continuously open receive windows, only closed when transmitting. Class C end-device will use more power to operate than Class A or Class B but they offer the lowest latency for server to end-device communication.
LoRa Server implements adaptive data-rate. For devices that support ADR, this will make sure that they are operating at the best data-rate possible with the least transmission power. This not only saves battery power, but uses the network in the most ideal way as airtime of the node decreases.
For networks where only a sub-set of channels is used of the channels defined by the LoRaWAN Regional Parameters (e.g. for the US region), LoRa Server supports channel re-configuration. It will automatically disable channels on the node that are not being used by the network.
LoRa App Server offers a web-interface to manage your nodes per application, per organization. By being able to assigning users to organizations and / or applications, The LoRa Server project is ideal for multi-team or multi-organization setups.
Both LoRa Server (the network-server) and LoRa App Server (the application-server) provide APIs to make them integratable in your own infrastructure. By using the LoRa Server API, you could even implement your own node inventory management system and fully replace LoRa App Server if needed.
LoRa Server offers gateway management so that you are able to manage your gateways and their GPS location and exposes statistics to track their performance.