While the number of connected devices continues to rise (and is expected to reach 125 billion by 2030), the maturing wireless technologies that support them are also continuing to get a good deal of attention globally. NB-IOT (Narrowband IOT), LoRa, and Sigfox, all low-power, wide-area network (LPWAN) technologies, are often pitted against one another in what’s portrayed as a race to the top. But that’s not necessarily an accurate picture of the connectivity ecosystem. Each of these technologies (or at least LoRa and NB-IoT) will likely play an important role in the IoT space depending on the use case, so understanding the features and differences of each is critical.
NB-IoT is the “clean sheet” initiative by the Third Generation Partnership Project (3GPP), the organization behind the standardization of cellular systems, to address the needs of very low data rate devices that need to connect to mobile networks, often powered by batteries. As a cellular standard, the goal of NB-IoT is to standardize IoT devices to be interoperable and more reliable.
Because NB-IoT is a cellular-grade wireless technology that uses OFDM modulation, the chips are more complex, but the link budgets are better. That means users get the high performance level associated with cellular connections, but at the cost of more complexity and greater power consumption.
NB-IoT is meant to be used to send and receive small amounts of data—a few tens or hundreds of bytes per day generated by low data-producing IoT devices. It is message-based, similar to Sigfox and LoRa, but with a much faster modulation rate that can handle a lot more data than those technologies. But NB-IoT is not an IP-based communication protocol like LTE-M (another LPWA cellular technology associated with IoT applications). You can’t actually connect to an IP network and expect to use it as you would with a smartphone. It was made for simple IoT applications and is more power efficient than LTE-M (which is better suited for higher bandwidth or mobile and roaming applications) but designed for more infrequent communication purposes.
There are fascinating geo-corporate-political elements at play in the development of NB-IoT; for more on that read Nick Hunn’s excellent piece, NB-IoT is Dead. Long Live NB-IoT. Nick points out that the 3GPP specification for NB-IoT has two competing variants, Huawei/Vodafone vs. Ericsson/Nokia/Intel. Additionally, Ericsson has stated that older 4G infrastructure based on Alcatel will not be backwards compatible with NB-IoT. This means that thousands of base stations would have to be changed in the US for carriers to support NB-IoT. In light of that, most U.S.-based carriers will stick to LTE-M.
So NB-IoT will be for simple devices that need to connect to an operator network via licensed spectrum. It is currently being piloted and tested only in Europe, and is not widely available except through a small number of operators in Europe that are doing some trials. If you follow the company Sigfox, you will recognize this as the 3GPP community’s attempt to address the market space created by networks like Sigfox.
Read here for more information on the NB-IoT Physical Layer.
NB-IoT is definitely a watch-and-see technology. To sum up the current situation:
If NB-IOT existed and was deployed:
LoRa is a non-cellular modulation technology for LoRaWAN. (Just like BPSK or QPSK is the modulation of NB-IoT.) Those two terms—LoRa and LoRaWAN—are not interchangeable: LoRaWAN is the standard protocol for WAN communications and LoRa is used as a wide area network technology.
LoRa is used primarily in two ways:
LoRa represents a good radio network for IoT solutions and has better link budgets than other comparable radio technologies. But outside of a few markets in Europe, if you want to connect to LoRaWAN networks—or use LoRa at all—you need to deploy your own network gateway.
That may seem like a downside, but it actually makes LoRa a good alternative to WiFi for low power devices that need to be connected throughout a building, like a factory or a hospital. (It’s hard to find an IT department that would approve of putting a third-party device on its own network due to security concerns. Setting up your own gateway creates a completely separate and secure network.) Of the three technologies discussed in this article, it’s the only one capable of being used as a “do-it yourself” technology; any company can build and use their own connected device wherever they can put up the gateway.
The most important differences between NB-IoT and LoRaWAN are:
To sum up LoRa:
No LPWAN article would be complete without mentioning Sigfox, which is the company that awoke the world to the potential for IOT devices to use very low bandwidth connections. Sigfox is the most basic of the three technologies, with the key differences being:
For Sigfox, however, it seems to be the beginning of the end. It has not deployed significant networks in the U.S. as of this time, and is struggling as a company. Its business model is somewhat aspirational, as the company has already spent hundreds of millions of dollars to deploy a network that people are paying pennies to access. Sigfox thinks that keeping the application cost low is the way to drive people to its market, but this line of thinking has made it difficult to earn sufficient revenue. In the end, it seems that Sigfox is failing (or at least struggling) in its efforts to deploy an alternative cellular network for IoT devices.
Each of these technologies offers an interesting set of capabilities, though it should be stressed that today none are available at scale in most of the world. In 2017, LTE Cat-M1 was the first nationwide LPWAN technology to be deployed in the U.S.
Technologies like LoRa will most likely be best used for “discrete” applications like smart buildings or campuses, where mobile network connectivity is not needed. If your use case would benefit from LoRa technology, take a look at Symphony Link. Symphony Link was designed to overcome the limitations associated with LoRa but is based on LoRa technology. It was specifically designed for enterprise and industrial customers who need a solution that is scalable and reliable, but also flexible—Symphony Link users have the option of adding functionality directly into the gateway through an API. Read more about Symphony Link, or talk to us about how it can solve your IoT connectivity challenge.