CODE:https://cdn.rawgit.com/samliew/4f6aec0c65e4dbe5c7fd782ea0953a3b/raw/0d928b52b69aef81b1bf5da50cbfb26ba3b4e71e/countries.js

Free email course on building IoT with Cloud IoT CoreCloud IoT Core
Free email course on  
Connectivity in IoT
Thanks for signing up! You'll get the first email soon.
Oops! Something went wrong while submitting the form.
< Back to Blog

All of the information presented in this blog post is based on publicly available research and should not be taken as a recommendation for using one service over another. Given the pace of change within this sector, I recommend that any technical questions be directed to the vendors mentioned below.

LoRa + LoRaWAN = LPWAN

A telecommunication system, LPWAN technologies included, is composed of several components. The physical (PHY) layer, at the hardware level, defines the electrical specifications for data transfer. The data link layer is responsible for detecting changes in the PHY layer and establishing a protocol to send data.

While LoRa is often misused to describe the entire LPWAN communication system, strictly speaking, LoRa is a proprietary modulation format owned by Semtech. SX1272 and SX1276 LoRa chips use a modulation technique called chirp spread spectrum (CSS) to make up the physical (PHY) layer of the technology stack.

LoRaWAN is an open-standard that defines the communication protocol for LPWAN technology based on a LoRa chip. LoRaWAN defines the media access control (MAC) in the data link layer and is maintained by the LoRa Alliance. This distinction between LoRa and LoRaWAN is important because other companies such as Link Labs use a proprietary MAC layer on top of a LoRa chip to create a better performing, hybrid design — called Symphony Link in Link Labs’ case.

So in summary,

LoRa = PHY Layer

LoRaWAN or Symphony Link = MAC Layer

LoRa + LoRaWAN = LPWAN technology stack

Image Credit: IOP Institute of Physics

Star Topology

Many websites list LoRaWAN as a star or star-on-star topology and note that it is better than a mesh network for preserving battery power and increasing the communication range.

Image Credit: Rootsaid

A star topology describes the network architecture: messages are relayed to a central server via gateways. Each end node transmits the data to multiple gateways. The gateway will then forward the data to the network server where redundancy detection, security checks, and message scheduling are performed.

This design choice has the following implications:

● Easier asset tracking: Since the end node sends data to multiple gateways, there is no need for gateway-to-gateway communication. This simplifies the logic for asset tracking applications where the end nodes are mobile.

● Better for public networks: Having a central server mitigating collision issues means that LoRaWAN might not be better for public networks than private/customer-deployed networks.

Image Credit: 3glteinfo.comImage Credit: 3glteinfo.comImage Credit: SemtechImage CreditImage Credit: 3glteinfo.comImage CreditImage Credit: 3glteinfo.com

Three Device Classes

LoRaWAN actually has three classes to cover a wide range of applications. The intended usage for each of the device classes are summarized below by SAGEMCOM:

Image Credit: Sagemcom

Business Model

SigFox and LoRa/LoRaWAN have completely different business models. SigFox is not an open-protocol but allows vendors (STMicroelectronic, Texas Instruments, Atmel) to manufacture SigFox-compatible radios. SigFox’s focus is on deploying its own network, giving away cheap hardware, and selling its network as a service.

LoRa/LoRaWAN, on the other hand, is an open-protocol, but users are limited to Semtech’s LoRa chips. The open standard leads to flexibility and custom options (e.g. Symphony Link), but slower development.

Both networks claim that more than 100 US cities are covered by its network. With cellular IoT options set to commercialize in 2017, it will be interesting to monitor which business model wins out in the end.

If you want a more technical overview of LoRa/LoRaWAN, check out our white papers.

Have Questions? Talk to an Expert

Yitaek Hwang

From traveling the world solving vision issues in underserved regions through ViFlex to building software to diagnose autism using machine learning, I realized that I like building things. So currently I’m on a path to build an Internet of Things (IoT) platform at Leverege as a Venture for America Fellow.

SHARE

Liked this post? You're gonna love these!

Smart Home Technologies: Zigbee, Z-Wave, Thread and Dotdot
February 8, 2019
Top 3 Best Practices for Designing IoT Data Visualizations
January 18, 2019
LTE Triangulation for Indoor Asset Tracking
December 26, 2018

Talk with Leverege

What type of use case are you building for? Whichever it is we are looking forward to learning more about your needs.

Have Questions?

Our team of experts is here to help!

Thanks for your submission! Our team is looking forward to connecting with you and will be in touch very soon!
Oops! Something went wrong while submitting the form.