An operated communication network
Dedicated to the | oT: low power / long range
Another communication protocol ?
We already have plenty !
WiFi, Bluetooth Low Energy, GSM, Zigbee, ..
No need for yet another technology !
WiFi, BLE : Rely on a hub connected to the Internet.
Short/ medium range
Zigbee : Private networks
GSM : High energy consumption (TX ~450mA) + Expensive
Quick video presentation
WDRLDWILDE ROLL 0UT_*‘_~‘_
“-1._1‘/ ex’ 1/1_. =1_
https: //www. youtube. com/ watch? v=AiaGO| cB7zY
1’ omme version
Nationwide coverage in
France, Spain, Netherlands & UK
Ongoing rollout in Portugal & US
Test cities : Antwerp, Dublin, Milan, Munich, Graz, San
Francisco, Seoul, Singapore,
SIGFOX operates in the ISM bands (868/915 MHz)
Sub-Ghz + Ultra Narrow Band
Focus on energy efficiency rather than bandwith increase
12 bytes max per message
140 messages per day max
12 bytes ! ?
Yes, twelve bytes
JSON, XML, .. forget it
12 bytes is 96 bits, meaning 2"96 values.
140 messages per day
ISM bands are regulated, and every device
must respect a 1% duty cycle use
1% means 36 secs per hour
A SIGFOX message takes up to 6 sec to emit
~6 messages per hour max
SIGFOX is not a hardware vendor
Plenty of partners offering SIGFOX-ready solutions
Adeunis, Atmel, Snootlab, ST, Telecom Design/ Avnet,
Telit/ Rutronik, TI,
Arduino shields (Snootlab, Atmel)
Dev Kits (Atmel, TD, Telit, Snootlab)
Modules (Telit, TD, .. )
System on chip & RF transceivers
Protocol specifics are handled by embedded libs
All you have to do is send commands over serial
Either AT commands or higher-level methods provided by the
When sending a message, you can request a downlink
In this case, your device will stay in Rx mode ~20 secs
The downlink message can be set
as a auto message (~ack)
or be sent an instant response from your own SI
Where are my messages ?
Operated network = don't deal with RF communication issues
Once your message is sent & processed by the SIGFOX
cloud, you can retrieve it using a REST API or an HTTP
Assume a few seconds between
emission start & callback to your platform
Data pushed by callback
You'll receive the raw payload you sent
(up to 12 bytes of hex)
And various metadata : deviceld, timestamp, the station
which received the message, signal/ noise & rssi values