The LoRa Alliance™, the global association of companies backing the LoRaWAN™ standard for low-power wide-area IoT (Internet of Things) networks (LPWANs), announced that it has achieved a new milestone, surpassing 500 ecosystem members in just over two years.
Those members, along with their partners and customers, are rapidly deploying the LoRaWAN protocol, with 42 publicly announced operators—a 3.5x increase in one year—and over 250 ongoing trials and city deployments.
“The LoRaWAN protocol is being adopted so quickly because it provides an open standard with 10+ years of node battery operation, a range of 10+ kilometers and an average node bill of materials of less than $10, providing a wide-area alternative to the high cost, complexity and overhead of other network implementations,” said Geoff Mulligan, chairman of the LoRa Alliance.
“We continue to build on these advantages by actively working to extend the global reach of our IoT ecosystem, and by quickly responding to market changes to increase network capabilities.”
As an example of these efforts, the LoRa Alliance just released the latest update to its regional parameters for LoRaWAN 1.0.2 revB.
Some of the many improvements include:
- India: added support for the country’s 865 MHz band, which enabled the recent deployment announced by Tata Communications that includes managing data from 200,000 sensors and gateways using Hewlett Packard Enterprise’s Universal IoT
- Australia: the LoRa Alliance demonstrated its responsiveness to the constantly changing technical landscape by rapidly adding support for Australia’s recent regulatory change to its ISM band. These changes greatly extend the maximum range and payloads of LoRaWAN networks, using even the lowest data
- Korea: expanded Korean band
- Global: added more consistent support for regions where the maximum allowed transmit power is expressed as equivalent isotropic radiated power (EIRP). This EIRP support makes it much easier for network operators to manage heterogeneous devices while ensuring regulatory
Comment on this article below or via Twitter: @IoTNow OR @jcIoTnow
