Sierra Wireless Technology & Research

Deep-dive technical resources: protocol comparisons, standards compliance documentation, white papers, and engineering reference material.

IoT Connectivity Protocol Comparison

Selecting the right wireless protocol is critical for deployment success. Compare key parameters across the protocols we support.

Parameter LTE Cat-M1 NB-IoT LoRaWAN 5G NR (RedCap) Wi-Fi 6
Max Data Rate (DL) 1 Mbps 127 kbps 50 kbps 220 Mbps 9.6 Gbps
Latency 10-15 ms 1.6-10 s 1-5 s 5-10 ms < 5 ms
Range (Urban) 5-10 km 3-10 km 2-5 km 1-5 km 50-100 m
Battery Life 5-10 years 10+ years 10-15 years 1-3 years N/A (mains)
Spectrum Licensed Licensed Unlicensed (ISM) Licensed Unlicensed
Best For Asset tracking, metering Sensors, smart meters Agriculture, buildings Video, industrial AR Indoor enterprise

Technical White Papers

In-depth engineering resources authored by our protocol and RF design teams.

LTE Cat-M1 vs NB-IoT: Protocol Selection Framework

Decision matrix for selecting between Cat-M1 and NB-IoT based on data rate, latency, mobility, and power requirements.

Download PDF

Edge Computing Architecture for Industrial IoT

Reference architecture for deploying ML inference at the network edge, reducing cloud dependency and meeting latency requirements.

Download PDF

5G RedCap: Bridging the IoT Bandwidth Gap

Technical analysis of 3GPP Release 17 Reduced Capability devices and their role in industrial IoT applications.

Download PDF

Antenna Design Guidelines for IoT Modules

PCB antenna layout, matching network design, and radiation pattern optimization for LTE-M and NB-IoT applications.

Download PDF

OTA Update Security Best Practices

Secure firmware delivery architecture: code signing, TLS transport, rollback protection, and attestation mechanisms.

Download PDF

LoRaWAN Network Planning for Enterprise

Gateway placement strategies, link budget calculations, and capacity planning for campus-scale LoRaWAN deployments.

Download PDF

Technology Selection Trade-offs

Informed deployment decisions require understanding the engineering trade-offs behind each architecture choice.

5G mmWave vs. Sub-6 GHz Deployment Strategy

5G infrastructure planning forces a fundamental trade-off between capacity and coverage. mmWave deployments (24-39 GHz) deliver massive bandwidth — up to 800 MHz channel widths — with ultra-low latency suitable for industrial IoT control loops and high-density venue coverage. However, mmWave signals attenuate rapidly: typical urban range is 200-500 meters with poor building penetration, requiring dense small cell infrastructure at approximately 10x the cost per square kilometer compared to sub-6 GHz.

Sub-6 GHz deployments (e.g., 3.5 GHz n78 band) offer 1-5 km urban range with moderate building penetration, making nationwide rollout economically feasible. The trade-off is reduced peak throughput (100-400 Mbps vs. multi-Gbps for mmWave) and higher latency floor (8-12 ms vs. 1-4 ms). For most industrial IoT applications requiring sensor data collection rather than video streaming, sub-6 GHz provides sufficient bandwidth at significantly lower infrastructure cost. Our modules support both bands — the optimal choice depends on your deployment density and latency budget.

Single-Vendor Stack vs. Open/Disaggregated Networking

IoT platform architecture choices present a vendor lock-in vs. integration simplicity dilemma. Single-vendor integrated stacks deliver a unified management plane, pre-validated interoperability, and a single support contact — reducing deployment time by 30-40% for standard use cases. The cost is limited flexibility: migrating away from a vendor ecosystem typically requires 12-18 months of re-engineering.

Open/disaggregated approaches (OpenConfig, SONiC-based switches, multi-vendor module sourcing) enable best-of-breed component selection and reduce hardware costs by 20-35% through white-box alternatives. However, integration testing burden shifts to the customer, and multi-vendor troubleshooting increases mean-time-to-resolution by 2-3x. Sierra Wireless modules are designed for protocol-level interoperability across both approaches: our AT command interface and standard Linux driver stack integrate with proprietary platforms (AWS IoT, Azure IoT Hub) and open-source frameworks (Eclipse Hono, ThingsBoard) without vendor-specific lock-in.

Standards & Compliance

Our products are designed, tested, and certified to meet or exceed international telecommunications and safety standards.

3GPP

3GPP Release 14/15/16/17

Full compliance with LTE Cat-M1, NB-IoT, and 5G NR RedCap specifications.

IEEE

IEEE 802.11ax (Wi-Fi 6)

Certified Wi-Fi 6 modules with OFDMA, MU-MIMO, and TWT power saving.

LoRa

LoRa Alliance Certified

LoRaWAN 1.0.3 and 1.0.4 certified devices with Class A, B, and C support.

IEC

IEC 62443 Cybersecurity

Industrial cybersecurity framework compliance for device hardening and secure communication.

Operating Boundaries & Design Considerations

Transparent disclosure of performance boundaries helps engineers make informed design-in decisions.

Performance Boundaries
Temperature Derating RF output power derated by up to 2 dB at temperature extremes (-40C and +85C). Maximum continuous transmit duty cycle limited to 50% at +85C ambient to prevent thermal shutdown.
NB-IoT Latency NB-IoT uplink latency can exceed 10 seconds in deep coverage enhancement (CE Level 2) mode due to repetition-based transmission. Not suitable for time-critical control applications requiring sub-second response.
LoRaWAN Duty Cycle ISM band regulations (ETSI EN 300.220) impose a 1% transmit duty cycle in the EU 868 MHz band, limiting maximum payload throughput to approximately 440 bytes per hour for SF12 configurations.
Environmental & Deployment Constraints
RF Interference Co-located LTE and Wi-Fi modules require minimum 20 dB isolation between antenna ports. Industrial environments with heavy electrical machinery may require external filtering to mitigate EMI above -70 dBm.
Carrier Dependency LTE Cat-M1 and NB-IoT availability varies by carrier and geography. Some carriers have announced NB-IoT sunset timelines (e.g., T-Mobile US targeting 2030). Module selection should account for carrier roadmap alignment.
OTA Update Size Delta firmware updates over NB-IoT are limited to approximately 256 KB per session due to bandwidth constraints. Full firmware images (typically 2-8 MB) require LTE Cat-M1 or Wi-Fi backhaul connectivity.

Need Technical Guidance?

Our protocol and RF engineers provide detailed technical consultation to help you select the optimal connectivity solution.

Access Engineering Support

Ready to Engineer Your IoT Deployment?

Our application engineers are standing by with technical specifications, reference designs, and carrier certification guidance.

Schedule Technical Consultation