Engineering Reference

Protocols & Packet Framing Hub

Over-the-air radio frequency frames begin as electromagnetic waveforms before silicon frontends, correlators, and microcontrollers translate them into actionable data. Understanding how modulation, framing, and routing interact prevents silent packet loss, RF congestion, and depleted batteries.

01 · Master Protocol Comparison Matrix

Unlicensed spectrum supports a wide variety of wireless protocols, each engineered around specific compromises between throughput, range, battery longevity, and topology:

ProtocolSpectrum BandTopologyThroughputRange (LOS)Frame SizeEncryption / SecurityBest Field Role
LoRa P2P433 / 868 / 915 MHzPoint-to-Point / Star0.3 – 22 kbps5 – 15+ km1 – 255 BCustom / AES-128Ultra-low-power remote sensors, point-to-point telemetry links, borehole monitors
Meshtastic433 / 868 / 915 MHzManaged Flood Mesh0.5 – 5.5 kbps3 – 10+ km / hopUp to 237 BAES-128 / AES-256-CTROff-grid ad-hoc tactical group messaging, outdoor community backcountry grids
MeshCore433 / 868 / 915 MHzStructured Role Mesh0.5 – 5.5 kbps5 – 15+ km / hopUp to 255 BEnd-to-End EncryptedScalable metropolitan backbones, leaf client battery savings, store-and-forward Room Servers
ReticulumAny (LoRa, HF, IP, Packet)Cryptographic Mesh0.1 kbps – 100+ MbpsMedium-independentUp to 500 BCurve25519, AES-128-CBCUnbreakable sovereign off-grid networking, asynchronous resilient data pipes
LoRaWANEU868 / US915 / AS923Star-of-Stars (Gateways)0.3 – 50 kbps2 – 15 km51 – 222 BDual AES-128 (NwkSKey & AppSKey)Municipal utility meters, agricultural smart soil probes, smart city logistics
Wi-Fi 4 / 6 / 72.4 / 5 / 6 GHzBSS Infrastructure AP54 Mbps – 40+ Gbps15 – 70 mUp to 2,304 BWPA2/WPA3 (CCMP / GCMP-256)High-speed local networking, streaming 4K video, bulk wireless data backhaul
Wi-Fi HaLowSub-1GHz (850–950 MHz)Star BSS (Up to 8,191 STA)150 kbps – 15+ Mbps1 – 3 kmUp to 2,304 BWPA3-SAE / WPA3-OWELong-range battery IP security cameras, agricultural drones, large-acreage farm sensors
ESP-NOW2.4 GHz (802.11 Action)Direct Peer-to-Peer~1 Mbps50 – 200 mUp to 250 BOptional CCMP AES-128Sub-10ms latency sensor-to-relay triggers, local microcontrollers without Wi-Fi AP
Z-Wave ClassicSub-1GHz (868 / 908 MHz)4-Hop Repeating Mesh9.6 – 100 kbps30 – 100 m / hopUp to 64 BSecurity 2 (S2 Curve25519 + AES-CCM)Zero-Wi-Fi-interference residential smart home sensors, wall switches, and deadbolts
Z-Wave Long RangeSub-1GHz (912 / 920 MHz)Direct Star (4,000 Nodes)100 kbps DSSS-OQPSK1.6+ km (1 mile)Up to 64 BSecurity 2 (S2 Access Control)Commercial multi-tenant properties, perimeter gates, large residential acreage
Bluetooth LE2.4 GHz ISMStar / Point-to-Point125 kbps – 2 Mbps10 – 50 m27 – 251 B (LE 4.2+)AES-128-CCMSmartphone sensor pairing, low-duty wearable devices, location asset tags
Thread / Zigbee2.4 GHz (802.15.4)Self-Healing Mesh250 kbps10 – 30 m / hopUp to 127 BAES-128-CCM (IPv6 6LoWPAN)Matter-compatible smart bulbs, radiator valves, local low-power sensor fabrics

02 · Universal Anatomy of an RF Packet

Regardless of frequency band or manufacturer, nearly all digital wireless protocols organize physical-layer transmissions into standard sequential functional blocks:

01 · Preamble

1–24 Bytes (or 8–12 symbols)

Known bit pattern (01010101 in FSK/OOK, unmodulated chirps in LoRa). Gives receiver Automatic Gain Control (AGC) time to settle and phase-locked loop (PLL) time to lock on carrier.

02 · Sync Word / SFD

1–4 Bytes (or 2 chirps)

Hardware start-of-frame delimiter (e.g., 0x12 for private LoRa, 0x34 for LoRaWAN, 0xF055 for Z-Wave, 0x2DD4 for FSK). Correlator triggers receiver interrupt and begins packet assembly.

03 · Physical Header

1–4 Bytes

Contains physical frame parameters: payload length in bytes, forward error correction coding rate, header presence, and explicit/implicit mode flags.

04 · Transport / MAC Header

4–30 Bytes

Source address, destination address, packet sequence numbers, hop limits, encryption initialization vectors (IV/nonce), and frame control bits.

05 · Application Payload

1 to 2,000+ Bytes

The actual user data: serialized C structs, Protocol Buffers (Meshtastic), BCD sensor values (weather stations), or encrypted JSON/CBOR objects.

06 · Frame Check Sequence (FCS)

1–4 Bytes

Cyclic Redundancy Check (CRC-8, CRC-16, CRC-32) or Cryptographic Message Authentication Code (MIC). Invalid bits caused by RF noise or collisions result in silicon-level packet rejection.


03 · Diagnostic Protocol Sniffing & Engineering Verification

In RF field engineering, you cannot fix what you cannot measure. When nodes fail to join a network, drop telemetry, or drain batteries prematurely, passive protocol analysis reveals the root cause:

Duty Cycle & Airtime Audits

Passive logging confirms whether a sensor firmware bug is spamming packets and violating regional duty-cycle caps (e.g. ETSI 1% in EU868) or burning battery prematurely.

Co-Channel Collision Tracking

Measuring CRC error rates across channels reveals when uncoordinated nodes (e.g. multiple weather sensors or uncoordinated LoRa meshes) are trampling each other’s packets.

ACK & Retransmission Audits

Examining sequence numbers and retry flags highlights asymmetric link margins where a battery sensor hears an AP cleanly but lacks the output power to return ACKs.

Defensive Engineering & Diagnostic Charter

All monitoring workflows documented on OpenRF Note are strictly passive and non-intrusive. We cover protocol analysis, site surveying, open telemetry decoding, and RF health diagnostics. We do not cover packet injection, jammer circuits, deauthentication attacks, replay vulnerabilities, or penetration testing tools. Unlicensed radio operation relies on mutual technical compliance under FCC Part 15 and international rules.

Site search