What is moving?
The colored radio peaks are copies of the same device message. Their width is exaggerated so a 100 Hz burst is visible.
Explore 3D-UNB time, frequency, and space diversity with a live spectrum workbench
Use this workbench to see why Sigfox devices can stay simple: a small payload is sent as one or three narrow radio bursts, base stations listen across the band, and the cloud keeps one clean application message.
Adjust payload, radio configuration, copy count, noise, and interference. The spectrum, timeline, base station cards, and diagnosis update together.
Fits inside the 12-byte Sigfox uplink limit.
Shorter payloads reduce radio-on time.
Compared with a 125 kHz reference receiver bandwidth.
Frequency, time, and base-station space improve resilience.
At least one burst reaches at least one base station, so Sigfox Cloud can forward one deduplicated event.
UNB is not high throughput. Its strength is making small, infrequent reports robust with minimal device complexity.
The colored radio peaks are copies of the same device message. Their width is exaggerated so a 100 Hz burst is visible.
A narrow receiver bandwidth captures less noise. That helps tiny battery devices send small messages over long range.
Press Play, then switch to the interferer preset. Watch one copy fail while another frequency or base station still receives.
The application does not receive three messages. Sigfox Cloud deduplicates radio copies and forwards one event.
Sensor data must fit into 0 to 12 uplink bytes. Binary packing matters.
The device selects narrow carrier frequencies inside its regional allocation.
A 100 Hz uplink concentrates energy in a narrow receiver bandwidth.
Optional extra bursts add time and frequency diversity at the cost of energy.
Several base stations can receive the same message with different RSSI/SNR.
The cloud removes duplicate radio copies before the application callback.
| Concept | Teaching value | Accuracy notes | Design consequence |
|---|---|---|---|
| Uplink payload | 0 to 12 bytes excluding protocol headers. | Shorter messages can use shorter predefined frame times. | Pack binary fields; avoid ASCII strings unless the report is tiny. |
| Downlink payload | 8 bytes, device-requested. | The network cannot push whenever it wants; the device must ask during an uplink flow. | Use downlink sparingly for compact configuration or commands. |
| 3D-UNB | Diversity in time, frequency, and receiving base-station space. | Sigfox radio specs allow one or three uplink radio bursts. | Three copies improve resiliency but use more airtime and energy. |
| Duty-cycle region | RC1-style operation commonly maps to 36 s/hour at 1% duty cycle. | For 8 to 12 byte payloads, Sigfox documents about 6 messages/hour or 140/day. | Design for infrequent reports, alarms, or status changes. |
| Frequency hopping region | Some RCs require frequency hopping or listen-before-talk behavior. | Radio configuration, data rate, band, power, and access rules vary by region. | Never hard-code Europe-only radio assumptions into global device firmware. |
Receiver noise scales with bandwidth. A useful teaching comparison is:
10 log10(125000 Hz / 100 Hz) = 31.0 dB
This is a bandwidth comparison, not a guarantee that every deployment gets 31 dB more link margin.
If copy success is independent with probability p, then:
P(any copy) = 1 - (1 - p)^n
Real networks also depend on fading, interference, antenna quality, deployment density, and local rules.
Triple transmission is not an acknowledgment. It is redundancy before the cloud. The application normally sees one deduplicated message, not three commands to process.
Sigfox documentation names the radio protocol 3D-UNB: time diversity, frequency diversity, and space diversity. A device can transmit one burst for lower energy or three bursts for increased resiliency. Regional radio configurations set the center frequencies, uplink data rates, access mechanism, and power guidance. The workbench compresses time and exaggerates spectral width so the learning object is visible; the labels preserve the real units.
For payload size, the platform constrains application data to 12 uplink bytes and 8 downlink bytes. Downlink is device-managed: the device requests the downlink during an uplink exchange, then the network later sends the response if available. That is why this page treats Sigfox as excellent for small reports and poor for large transfers, real-time control, or firmware delivery over the UNB link alone.
Official 3D-UNB, one-or-three burst, security, and uplink content-length reference.
Official RC frequencies, bit rates, power guidance, duty-cycle, FH, and LBT notes.
Official 12-byte uplink, 8-byte downlink, frame-time, and binary-packing examples.
Official explanation that downlink is device-requested and callback-assisted.
Continue with network architecture, backend flow, and integration context.
Compare Sigfox UNB with LoRaWAN, NB-IoT, LTE-M, and other long-range options.