1. July 2017
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Suitability Evaluation of Connectivity]
Date Submitted: [9 July, 2017]
Source: [Joerg ROBERT] Company [Friedrich-Alexander University Erlangen-Nuernberg]
Address [Am Wolfsmantel 33, Erlangen, Germany]
Voice:[ ], FAX: [ ],
Re: []
Abstract: [This document presents the suitability evaluation for different connectivity that may be used for LPWAN.]
Purpose: [Presentation within IG LPWA]
Notice: This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P
Joerg ROBERT, FAU Erlangen-Nuernberg

2. Suitability Evaluation of Connectivity
July 2017
Suitability Evaluation of Connectivity
Joerg Robert, FAU Erlangen-Nuernberg
Joerg Robert, FAU Erlangen-Nuernberg

3. Gateway / Transparent ( I / II )
<month year>
doc.: IEEE <doc#>
July 2017
Gateway / Transparent ( I / II )
Transmission of the data without IP on the LPWAN link
Pros
Very low overhead
Simple support of uni-directional links
Cons
Inflexible
<author>, <company>

4. Transparent ( II / II ) Communication Mode Uplink Downlink
July 2017
Transparent ( II / II )
Communication Mode
Uplink
Downlink
Uplink / Broadcast Downlink
Frequency Regulation
ETSI
FCC
ETSI/FCC
None
Cell Radius
> 50km
< 50km
< 10km
< 5km
< 1km
Data Period
Occasionally, less than 1/day
Occasionally 1/day
Occasionally 1/hour
Occasionally, more than 1/hour
Periodically 1/day
Periodically 1/hour
Periodically, more than 1/hour
Data Length
<= 16 bytes
<= 64 bytes
<= 256 bytes
> 256 bytes
Power Supply
CR 2025
2xAA
Energy Harvesting
External
Joerg Robert, FAU Erlangen-Nuernberg

5. IP w/o Header Compression ( I / II )
<month year>
doc.: IEEE <doc#>
July 2017
IP w/o Header Compression ( I / II )
Transmission of the data without IP on the LPWAN link
Pros
Simple support of uni-directional links
Simple
Cons
Very high overhead
<author>, <company>

6. IP w/o Header Compression ( II / II )
July 2017
IP w/o Header Compression ( II / II )
Communication Mode
Uplink
Downlink
Uplink / Broadcast Downlink
Frequency Regulation
ETSI
FCC
ETSI/FCC
None
Cell Radius
> 50km
< 50km
< 10km
< 5km
< 1km
Data Period
Occasionally, less than 1/day
Occasionally 1/day
Occasionally 1/hour
Occasionally, more than 1/hour
Periodically 1/day
Periodically 1/hour
Periodically, more than 1/hour
Data Length
<= 16 bytes
<= 64 bytes
<= 256 bytes
> 256 bytes
Power Supply
CR 2025
2xAA
Energy Harvesting
External
Joerg Robert, FAU Erlangen-Nuernberg

7. SCHC IP Header Compression ( I / II )
<month year>
doc.: IEEE <doc#>
July 2017
SCHC IP Header Compression ( I / II )
Transmission of IP data with Static Context Header Compression (SCHC)
Pros
Allows for IPv6 connectivity with minimum of additional overhead
Low complexity in sensor nodes
Works for uni- and bi-directional communication
Cons
Additional effort to define and communicate rules
Additional functionality in LPWAN gateways
Maybe not suitable for all configurations
<author>, <company>

8. SCHC IP Header Compression ( II / II )
July 2017
SCHC IP Header Compression ( II / II )
Communication Mode
Uplink
Downlink/Downlink
Uplink / Broadcast Downlink
Frequency Regulation
ETSI
FCC
ETSI/FCC
None
Cell Radius
> 50km
< 50km
< 10km
< 5km
< 1km
Data Period
Occasionally, less than 1/day
Occasionally 1/day
Occasionally 1/hour
Occasionally, more than 1/hour
Periodically 1/day
Periodically 1/hour
Periodically, more than 1/hour
Power Supply
CR 2025
2xAA
Energy Harvesting
External
Data Length
<= 16 bytes
<= 64 bytes
<= 256 bytes
> 256 bytes
Joerg Robert, FAU Erlangen-Nuernberg

9. IP Header Compression ( I / II )
<month year>
doc.: IEEE <doc#>
July 2017
IP Header Compression ( I / II )
IPHC (IP Header Compression RFC 6282)
Joerg will check
<author>, <company>

10. IP Header Compression ( II / II )
July 2017
IP Header Compression ( II / II )
Joerg Robert, FAU Erlangen-Nuernberg

11. Any Questions or Comments?
July 2017
Any Questions or Comments?
Joerg Robert, FAU Erlangen-Nuernberg