LPWAN to Application standardization within the IETF

By Juan Carlos Zuniga, Sigfox, IETF Internet Area Co-Chair, (edited by Alan J Weissberger)

Introduction:

Amongst the plethora of different Internet of Things (IoT) technologies [see Addendum], Low Power Wide Area Networks (LPWANs) [1] offer mature and well-established solutions for the Industrial Internet of Things (IIoT).

Note 1.  A LPWAN is a type of wireless telecommunication wide area network designed to allow long range communications with low power consumption, low cost interface and a relatively low bit rate for the IIoT.  There are many types of LPWANs.  Some like LTE-M and NB-IoT use licensed spectrum, while others such as Sigfox and LoRaWAN use unlicensed spectrum.

LPWANs enables IoT systems to be designed for use cases that require devices to send small amounts of data periodically over often-remote networks that span many miles and use battery-powered devices that need to last many years.

LPWANs achieve those attributes by having the IoT devices (“things”) send only small packets of information periodically or even infrequently—status updates, reports, etc.—upon waking from an external trigger or at a preprogrammed time interval.

………………………………………………………………………………………………

In order to enable these IIoT connectivity solutions, a common standard is needed to allow the various types of LPWANs to communicate with applications using a common language.  For this to occur, each network must have the ability to connect to the Internet.  However, due to the severely restrictive nature of LPWANs, the abilities of Internet Protocols, specifically IPv6, cannot sufficiently meet the needs of these networks.

To overcome these issues, the Internet Engineering Task Force (IETF) chartered the LPWAN working group (WG) in 2016 to identify common functionality needs across LPWANs and to standardize the protocols that could enable these functionalities across the various networks.

The goal of the IETF LPWAN WG is to converge the diverse LPWAN radio technologies toward a common hourglass model that will provide users with a standard management strategy across networks and enable common Internet-based services to the applications.

To achieve this goal, the IETF LPWAN WG has produced the Static Context Header Compression and Fragmentation (SCHC) [2] specification, an ultralightweight adaptation layer uniquely designed to support the extremely restricted communication resources of LPWAN technologies.

Note 2.  SCHC is expected to become a recognized acronym like several  other IETF protocols (e.g. HTTP, TCP, DHCP, DNS, IP, etc.).  Please see illustration below of SCHC Architecture.

………………………………………………………………………………………………….

SCHC will soon be published as a new IETF RFC.  Again, it’s objective is to achieve interoperability across the leading LPWANs, including Sigfox, LoRaWAN, NB-IoT and IEEE 802.15.4w(LPWA) [3].

Note 3.  IEEE 802.15.4w or LPWA

Low Power Wide Area Network (LPWAN) extension to the IEEE Std 802.15.4 LECIM PHY layer to cover network cell radii of typically 10-15km in rural areas and deep in-building penetration in urban areas. It uses the LECIM FSK (Frequency Shift Keying) PHY modulation schemes with extensions to lower bit-rates (e.g. payload bit-rate typically < 30 kb/s). Additionally, it extends the frequency bands to additional sub-GHz unlicensed and licensed frequency bands to cover the market demand. For improved robustness in channels with high levels of interference, it defines mechanisms for the fragmented transmission of Forward Error Correction (FEC) code-words, as well as time and frequency patterns for the transmission of the fragments. Furthermore, it defines lower code rates of the FEC in addition to the K=7 R=1/2 convolutional code. Modifications to the Medium Access Control (MAC) layer, needed to support this PHY extension, are defined.

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Why do LPWANs need their own interoperability standard?

The common characteristics of LPWANs include a power-optimized radio network, a simple star network topology, frame sizes in the order of tens of bytes transmitted a few times per day at ultra-low speeds, and a mostly upstream transmission pattern that allows devices to spend most of their time in sleep mode. These characteristics lead to ultra-long-range networks that allow for connected devices to have an extremely long battery life and be sold at a very low cost, enabling simple and scalable deployments.

LPWANs are especially well-suited for deployments in environments where battery recharging or swapping is not an option and where only a very low rate of data reporting is required. Also, LPWAN networks are fundamentally different than other networks, as they have been designed to handle infrequent message exchanges of payloads as small as approximately 10 bytes.

To manage these very specific constraints, the IETF has developed the SCHC adaptation layer, which is located between the network layer (e.g. IPv6) and the underlying LPWAN radio technology. SCHC comprises two independent sublayers – header compression and fragmentation – which are critical to meeting the specific characteristics of LPWANs.

The SCHC header compression sublayer has been tailored specifically for LPWAN technologies, and it is capable of compressing protocols such as IPv6, UDP and CoAP. It relies on the infrequent variability of LPWAN applications to define static contexts that are known a priori to both protocol end points.

The SCHC fragmentation sublayer, on the other hand, offers a generic approach to provide both data reliability and the capability of transmitting larger payload sizes over the extremely constrained LPWAN packet sizes and the extremely severe message rate limitations. Even though the fragmentation sublayer mechanisms have been designed to transport long IPv6 packets, they can equally be applied to non-IP data messages and payloads, as the functionality can be implemented independent of the header compression.

In order to be fully operational across LPWAN technologies, SCHC has been developed by the IETF under a generic and flexible approach that aims to address the common and unique requirements of these networks. The SCHC specification offers enough flexibility to optimize the parameter settings that need to be used over each LPWAN technology.

The IETF LPWAN WG is now working on the development of different SCHC profiles optimized for each individual LPWAN technology, including Sigfox, LoRaWAN, NB-IoT and IEEE 802.15.4w. Future work also includes definition of data models to represent the static contexts, as well as operation, administration and management (OAM) tools for LPWANs.

Here’s an illustration of the Sigfox SCHC:

…………………………………………………………………………………………………..

From the early stage IETF Sigfox SCHC profile spec:

The Static Context Header Compression (SCHC) specification describes a header compression scheme and a fragmentation functionality for Low Power Wide Area Network (LPWAN) technologies.
SCHC offers a great level of flexibility that can be tailored for different LPWAN technologies. 
The present (early stage) document provides the optimal parameters and modes of operation when SCHC is implemented over a Sigfox LPWAN.

………………………………………………………………………………..

Addendum –by Alan J Weissberger

IEEE definition of IoT:

“An IoT system is a network of networks where, typically, a massive number of objects, things, sensors or devices are connected through communications and information infrastructure to provide value-added services via intelligent intelligent data processing processing and management management for different different applications (e.g. smart cities, smart health, smart grid, smart home, smart transportation, and smart shopping).”
— IEEE Internet of Things Journal

IoT communications over LPWANs should be:
 Low cost,
 Low power,
 Long battery life duration,
 High number of connections,
 Low bitrate,
 Long range,
 Low processing capacity,
 Low storage capacity,
 Small size devices,
 Simple network architecture and protocols

Also see IETF draft RFC 8376  LPWAN Overview

……………………………………………………………………………………………….

Sigfox Network Characteristics:

 First LPWAN Technology
 The physical layer based on an Ultra-Narrow band wireless modulation
 Proprietary system
 Low throughput ( ~100 bps)
 Low power
 Extended range (up to 50 km)
 140 messages/day/device
 Subscription-based model
 Cloud platform with Sigfox –defined API for server access
 Roaming capability

………………………………………………………………………………………

References:

https://www.ackl.io/blog/ietf-standardization-working-group-enabling-ip-connectivity-over-lpwan

https://techblog.comsoc.org/2017/10/25/lora-wan-and-sigfox-lead-lpwans-interoperability-via-compression/

https://tools.ietf.org/html/draft-ietf-lpwan-schc-over-sigfox-00

 

3 thoughts on “LPWAN to Application standardization within the IETF

  1. IETF draft: Static Context Header Compression (SCHC) over LoRaWAN

    Abstract:
    The Static Context Header Compression (SCHC) specification describes generic header compression and fragmentation techniques for LPWAN (Low Power Wide Area Networks) technologies. SCHC is a generic mechanism designed for great flexibility, so that it can be adapted for any of the LPWAN technologies.

    This IETF draft provides the adaptation of SCHC for use in LoRaWAN networks, and provides elements such as efficient parameterization and modes of operation. This is called a profile.

    Here is a a short overview of Static Context Header Compression (SCHC). For a detailed description, refer to the full specification [I-D.ietf-lpwan-ipv6-static-context-hc].

    Static Context Header Compression (SCHC) avoids context synchronization, based on the fact that the nature of data flows is highly predictable in LPWAN networks, some static contexts may be stored on the Device (Dev). The contexts must be stored in both ends, and it can either be learned by a provisioning protocol or by out-of-band means or it can be pre-provisioned, etc. The way the context is learned on both sides is out of the scope of this document.

    https://tools.ietf.org/html/draft-ietf-lpwan-schc-over-lorawan-01
    ………………………………………………………………………………………………………………..

    Is there an equivalent IETF draft for SCHC over Sigfox or other LP-WANs?

  2. ABI Research says LoRaWAN and Sigfox will hold the leading share of LPWAN networks connections until at least 2024, but by 2026 cellular technologies NB-IoT and LTE-M will account for 60 percent of its estimate of 3.6 billion LPWAN network connections.

    However, ABI Research expect LoRa and Sigfox to account for over 80 percent of the non-cellular LPWAN network connections by 2026.

    The research firm says, in 2018, NB-IoT and LTE-M were plagued by network hardware and connectivity module issues, driving enterprises and OEMs to delay deployment of NB-IoT and LTE-M applications, including eSIM/iSIM.

    It says these uncertainties have delayed the commercial rollout of cellular LPWA IoT solutions by 12 to 18 months, to the benefit of Sigfox and LoRaWAN, both of which have witnessed a substantial increase in adoption from device OEMs and IoT solution vendors.

    “LoRa technology adoption in 2018 was dominated by growth in IoT connections from private networks, with 75 percent year-on-year growth,” ABI says.

    Multivendor LoRaWAN ecosystem
    “LoRa has benefited from a multivendor ecosystem of gateway OEMs such as Multi-tech, Kerlink, Cisco, and Tektelic offering a wide array of gateway solutions which reduced network total cost of ownership for enterprises.”

    According to ABI Research LoRaWAN’s flexibility in network deployment — private or public — has been a decisive factor in its early adoption by utilities and manufacturing companies that have traditionally been advocates of private networks.

    “However, even as LoRa’s private network footprint continues to expand, connection growth in public networks will outpace private networks connecting the majority of LoRa devices by 2026,” it says.

    ABI Research expects LoRaWAN devices to have the majority share of non-cellular LPWA connections by 2026, followed by Sigfox.

    “The main drivers of Sigfox connections were growth in home security, smart metering, and asset tracking applications. With an extensive network footprint in Europe, Sigfox had a leading share of LPWA connections in the region and will continue to have a leading share of European non-cellular LPWA connections,” it says.

    Sigfox gains from roaming support:
    ABI notes that Sigfox, is currently the only commercially available LPWAN network to support tracking of assets across multiple regions. It says there have been several successful implementations from companies such as Groupe PSA, Total SA, Guerlain, BPW Group, Luis Vuitton, and Michelin to track assets from containers, trailers, reusable pallets, boxes, and bags.

    It is tipping Sigfox connections to exceed 430 million end-points by 2026, with significant growth coming from asset tracking applications.

    https://www.iotaustralia.org.au/2019/06/18/iot-facts-and-forecasts/lpwan-tipped-to-top-cellular-for-iot-until-2024/

Comments are closed.