Data Aggregation Unit for LP-WAN

The existing pilot deployments of LP-WANs have shown the huge potential and the industrial interest in their capabilities, such as in control and monitoring applications. Examples of LPWAN technologies include LoRa, SigFox, IEEE 802.15.4k LECIM, DASH-7, Weightless, etc. [I-D.minaburo-lp-wan-gap-analysis]. Connecting these LP-WANs to the Internet is expected to provide significant benefits to these networks in terms of interoperability, application deployment, and management, among others. For these reasons, more and more LP-WAN owners are connecting their own LP-WANs to the Internet. It is generally desirable that a given Data Unit(DU) generated by any LP-WANs can be sent through the Internet efficiently and quickly. However, the intrinsic characteristics of LP-WANs, very limited DU size and large-scale DU sets make the data transmission through Internet more complex. In a nutshell, that may be a terrible waste of bandwidth if use one IP packet to send one LP-WAN Data Unit(LDU), because the packet header is much bigger than payload.And what's more, the LP-WAN usually consists of many nodes, so the large-scale data may increase the Internet burden. This is the motivation for aggregating these small-size LDUs into a bigger data chain to improve the percentage of the payload in IP packet to make the information retrieval and dissemination more efficient. For example,a ZigBee Cluster can aggregate several LDUs into a LDU chain and send them together as an atomic payload of the IP packet. By doing this, the ZigBee Cluster doesn't need to initiate the transmission for every LDU as well as improve the proportion of the payload in the IP packet to increase the transmission efficiency. During transmission, the aggregator cannot do any processing on the LDUs and just encapsulates them into an aggregation chain. During reception, the de-aggregator just opens the data chain and separately forwards them to the applications. This arrangement provides numerous benefits for LP-WAN applications(both transmitter and receiver): increased delivery efficiency, reduced transmission/receiving times, and improved quality of experience for LP-WAN Users. Considering that a vast number of LP-WAN devices are,as of today,battery-powered,the DAU is also helpful for saving battery consumption.

This document uses the following terms: Aggregator: Software entity which resides either in the system kernel or hardware aggregating one or more LDUs into an aggregation chain, the payload of the IP packet that is sent through the internet. The aggregator is usually placed into transmitter device with cache capacity. De-aggregator: Software entity which resides either in the system kernel or hardware de-aggregating the LDU chain into seperate LDU, which comes from aggregator. De-aggregator is usually placed into receiving device with cache capacity. Data Unit: Refers to data packets generated by LP-WANs in general, for example generated by LoRa, SigFox, IEEE 802.15.4k LECIM, etc.

DU:Data Unit LDU: LP-WAN Data Unit L-DAU: LP-WAN Data Aggregation Unit

LP-WAN technologies are a kind of constrained and challenged networks [RFC7228]. very small frame payload as low as 12 bytes. Typical traffic patterns are composed of a large majority of frames with payload size around 15 bytes and a small minority of up to 100 byte frames. ultra dense networks with thousands to tens of thousands of nodes. On the other side, the existing Internet technologies have their specific characteristics: IP header is usually more than 20 bytes[RFC6864],[RFC6973], and the Ethernet header is at least 14 bytes[RFC7796]. TCP is a reliable and connection oriented transport mechanism[RFC7661]. Therefore, it is obviously unwise to just encapsulate one LDU into the IP packet. That's a waste of bandwidth and also increases Internet burdens. However, no standards or open specifications currently exist to solve above problems. In the terminology of [RFC7228], these characteristics put LP-WANs into the "challenged network" category, and the intrinsic characteristics, current usages and architectures will allow the group to make and justify the design choices. However, there also some desired properties: preserve the end-to-end communication principle. maintain independence from L2 technology. use or adapt protocols defined by IETF to this new environment that could be less responsive. use existing addressing spaces and naming schemes defined by IETF. small message size, with potentially no L2 fragmentation. optimize the protocol stack in order to limit the number of duplicated functionalities; for instance acknowledgements should not be done at several layers. So,the L-DAU is proposed in this document to make the information retrieval and dissemination of LP-WANs more efficient as well as fully conforms to the principles proposed in [RFC7228].

The L-DAU service architecture is shown in Figure 1. During transmission, a LDU is passed down from LPWAN application, and stored temporarily by the aggregator, then aggregated into a L-DUA. During reception, a received L-DAU is de-aggregated into seperate LDUs and forwarded to the LP-WAN application.

| application | | e| +--------------------+ +--------------------+ |g n| | L-DAU | | L-DAU | | d| | Aggregation | | Aggregation | |i i| +--------------------+ +--------------------+ |v n| | Network | | Network | |i g| | Layer | | Layer | |e | +--------------------+ +--------------------+ |c | | PHY | | PHY | |e | | Layer | | Layer | |R V +--------------------+ +--------------------+ Figure 1 L-DAU service architecture ]]>

A L-DAU consists of a sequence of one or more L-DAU subframes as shown in Figure 2.

Each L-DAU subframe consists of a LDU delimiter followed by a LDU. Except when a L-DAU subframe is the last one in a L-DAU. The L-DAU length should be less than 65535 octets. The LDU delimiter is 2 octets in length and the structure of the LDU delimiter is defined in Figure 3.

variable 2 Figure 3 L-DAU subframe format ]]> The fields of the L-DAU delimiter are defined in Table 1.

The purpose of the L-DAU delimiter is to locate the LDUs within the L-DAU.

This document focuses on approach and the motivational for L-DUA, and does not analyze the associated threats. Those threats will be discussed in future.

The authors wish to thank Linlin Zhou for her invaluable comments.