Craig: Included varying opinions on LTE-M MCL figure.

2017-05-15T10:26:25Z

Included varying opinions on LTE-M MCL figure.

Craig: capitalisation

2017-05-15T10:09:26Z

capitalisation

Craig: Based on the features table from our recent LPWAN security white paper

2017-05-15T10:06:40Z

Based on the features table from our recent LPWAN security white paper

New page

Table of features for various Low-Power Wide Area Networking technologies, extracted from the [https://fhcouk.files.wordpress.com/2017/05/lpwa-technology-security-comparison.pdf LPWA Technology Security Comparison] white paper.

The first few rows (with <span style="color:grey;font-weight:bold">Grey Titles</span>) are not security features as such, but are included as they may be significant factors in choosing one technology over another.

{| class="wikitable" style="text-align:center"
| style="width:20%" |
! style="width:16%" | LTE-M
! style="width:16%" | NB-IoT
! style="width:16%" | EC-GSM-IoT
! style="width:16%" | LoRaWAN
! style="width:16%" | Sigfox
|-
! style="text-align:left;color:gray" | Bandwidth
|1.08MHz
|180kHz
|600kHz
|125kHz (500kHz d/l)
|100Hz (1.5kHz d/l)
|-
! style="text-align:left;color:gray" | Maximum Coupling Loss
|approx. 160dB <ref name="mcl">These figures are provided as a guide only; precise comparisons may be misleading as link budget assumptions vary in the calculations for each technology</ref>
|164dB <ref name="mcl" />
|164dB <ref name="mcl" />
|157dB <ref name="mcl" />
|153dB <ref name="mcl" />
|-
! style="text-align:left;color:gray" | Typical Frequency Bands
|Below or above 1GHz
|Below or above 1GHz
|Below or above 1GHz
|Below 1GHz
|Below 1GHz
|-
! style="text-align:left;color:gray" | Maximum Downlink Peak Data Rate
|1Mbps
|250kbps
|74kbps
|50kbps
|600bps
|-
! style="text-align:left;color:gray" | Maximum Uplink Peak Data Rate
|1Mbps
|250kbps
|74kbps
|50kbps
|100bps
|-
! style="text-align:left;color:gray" | Typical Downlink Daily Throughput
|Limited only by battery power
|Limited only by battery power
|Limited only by battery power
|~200B <ref name="ttn">Based on [https://www.thethingsnetwork.org/forum/c/nodes The Things Network Fair Access Policy]</ref>
|24B
|-
! style="text-align:left;color:gray" | Typical Uplink Daily Throughput
|Limited only by battery power
|Limited only by battery power
|Limited only by battery power
|~200kB <ref name="ttn" />
|1.64kB
|-
! style="text-align:left;color:gray" | Typical Module Cost
|Medium
|Low
|Low
|Low
|Very low
|-
! style="text-align:left" | Globally Unique Identifiers
|IMSI
|IMSI
|IMSI
|Optional (DevEUI)
|Yes (32 bits)
|-
! style="text-align:left" | Device/Subscriber Authentication
|UICC or eUICC <ref name="uicc">UICC and eUICC both authenticate the mobile subscription, for a non-removable eUICC the EID also serves to uniquely identify the device</ref>
|UICC or eUICC <ref name="uicc" />
|UICC or eUICC <ref name="uicc" />
|Device or Subscriber <ref>Pre-provisioned NwkSKey authenticates the device, or default AppKey (permitted by The Things Network) authenticates the subscriber, or unique AppKey authenticates both</ref>
|Device
|-
! style="text-align:left" | Network Authentication
|LTE AKA
|LTE AKA
|UMTS AKA
|Optional
|No
|-
! style="text-align:left" | Identity Protection
|TMSI
|TMSI
|TMSI
|Partial (DevAddr)
|No
|-
! style="text-align:left" | Data Confidentiality
|Yes (EEAx)
|Yes (EEAx)
|Optional (GEA4/5)
|Yes (AppSKey)
|No
|-
! style="text-align:left" | End-to-Middle Security
|No
|No <ref>Under discussion for a future 3GPP release (SA3 work item “Battery Efficient Security for Very-Low-Throughput MTC Devices”)</ref>
|To visited network
|Yes (AppSKey)
|No
|-
! style="text-align:left" | Forward Secrecy
|No
|No
|No
|No
|No
|-
! style="text-align:left" | Data Integrity
|Limited <ref name="blind">Where data encryption is in use, modifying ciphertext will corrupt the data unpredictably</ref>
|Optional (with DoNAS)
|Limited <ref name="blind" />
|Limited <ref name="blind" />
|Variable <ref>A 16-byte Message Authentication Code is truncated to fit within a fixed size packet: only 2 to 5 bytes are transmitted, depending on the space available in each packet</ref>
|-
! style="text-align:left" | Control Integrity
|Yes (EIAx)
|Yes (EIAx)
|Optional (GIA4/5)
|Yes
|unknown <ref>Sigfox does not disclose the algorithm for calculating the Message Authentication Code, thus it is unknown how much of the control information (if any) is covered</ref>
|-
! style="text-align:left" | Replay Protection
|Yes
|Optional (with DoNAS)
|Limited <ref name="ctr">Where data encryption is in use, replaying ciphertext will not result in the same plaintext</ref>
|Yes
|Yes
|-
! style="text-align:left" | Reliable Delivery
|Yes
|Yes
|Yes
|No
|No
|-
! style="text-align:left" | Critical Infrastructure Class
|Access Classes 11-15
|Access Classes 11-15
|Access Classes 11-15
|No
|No
|-
! style="text-align:left" | Updatability (Device)
|Possible
|Possible
|Possible
|Limited <ref>Firmware update broadcast capability is under discussion for a future LoRaWAN version</ref>
|No
|-
! style="text-align:left" | Updatability (Keys/Algorithms)
|Optional (SIM OTA)
|Optional (SIM OTA)
|Optional (SIM OTA)
|Limited
|No
|-
! style="text-align:left" | Network Monitoring and Filtering
|Yes
|Yes
|Yes
|Limited
|Monitoring only
|-
! style="text-align:left" | Key Provisioning
|Pre-provisioned or RSP
|Pre-provisioned or RSP
|Pre-provisioned or RSP
|Pre-provisioned (ABP) or OTAA
|Pre-provisioned
|-
! style="text-align:left" | Algorithm Negotiation
|Yes
|Yes
|Yes
|No
|No
|-
! style="text-align:left" | Class Break Resistance
|Yes <ref name="cb">No private or secret keys are shared between devices</ref>
|Yes <ref name="cb" />
|Yes <ref name="cb" />
|Optional <ref>Devices may share a default AppKey, which would then be a potential class break</ref>
|Yes <ref name="cb" />
|-
! style="text-align:left" | Certified Equipment
|Required
|Required
|Required
|Optional
|Required
|-
! style="text-align:left" | IP Network
|Optional
|Optional
|Yes
|No
|No
|}
<references />

@@ Line 19: / Line 19: @@
 |-
 ! style="text-align:left;color:gray" | Maximum Coupling Loss
-|~160dB <ref name="mcl">These figures are provided as a guide only; precise comparisons may be misleading as link budget assumptions vary in the calculations for each technology</ref>
+| >155.7dB <ref>According to [ftp://www.3gpp.org/Information/presentations/presentations_2016/2016_11_3gpp_Standards_for_IoT.pdf 3GPP target]</ref> 164dB <ref>According to [https://www.sierrawireless.com/iot-blog/iot-blog/2017/01/new_research_reveals_ltem_catm1_is_ideal_for_deep_coverage_iot_applications/ Sierra Wireless]</ref>
-|164dB <ref name="mcl" />
+|164dB <ref name="mcl">These figures are provided as a guide only; precise comparisons may be misleading as link budget assumptions vary in the calculations for each technology</ref>
 |164dB <ref name="mcl" />
 |157dB <ref name="mcl" />

@@ Line 19: / Line 19: @@
 |-
 ! style="text-align:left;color:gray" | Maximum Coupling Loss
-|approx. 160dB <ref name="mcl">These figures are provided as a guide only; precise comparisons may be misleading as link budget assumptions vary in the calculations for each technology</ref>
+|~160dB <ref name="mcl">These figures are provided as a guide only; precise comparisons may be misleading as link budget assumptions vary in the calculations for each technology</ref>
 |164dB <ref name="mcl" />
 |164dB <ref name="mcl" />
@@ Line 128: / Line 128: @@
 |Optional (GIA4/5)
 |Yes
-|unknown <ref>Sigfox does not disclose the algorithm for calculating the Message Authentication Code, thus it is unknown how much of the control information (if any) is covered</ref>
+|Unknown <ref>Sigfox does not disclose the algorithm for calculating the Message Authentication Code, thus it is unknown how much of the control information (if any) is covered</ref>
 |-
 ! style="text-align:left" | Replay Protection

LPWAN Security Features - Revision history

Craig: Included varying opinions on LTE-M MCL figure.

Craig: capitalisation

Craig: Based on the features table from our recent LPWAN security white paper