This document provides an overview of Sigfox and its low-power wide-area network technology for connecting IoT devices. Sigfox uses an ultra-narrowband radio technology that allows low-cost, low-power devices to transmit small amounts of data over long ranges. Key aspects include its public network architecture, security features to authenticate devices and messages, and the ability for devices to connect directly to Sigfox's cloud platform without any pairing or additional infrastructure. The document outlines how to build Sigfox-compatible devices, connect them to the global Sigfox network, and manage devices and data through Sigfox's cloud services.
3. THE NEXT MAJOR
TECHNOLOGICAL
REVOLUTION
BIGGER THAN SMARTPHONES
CONNECTING EVERYTHING SO
BATTERY POWERED
USE CASES ARE SENSING AND
TRACKING SO SMALL MESSAGES
NEED FOR LOW COST, LOW POWER
WIRELESS PUBLIC NETWORK
5. IN A
NUTSHELL
VALUE PROPOSITION
CHECKLIST
端錫 Public
network
professionally
managed
端錫 Out
of
the
box
connec<vity
-足
no
pairing
with
hub
端錫 Low
power
connec<vity
-足
ba?ery
powered
device
端錫 Low
upfront
cost
hardware
10
x
cheaper
than
cellular
端錫 Low
subscrip<on
cost
端錫 Jamming
very
complex
端錫 Sensing,
monitoring
and
tracking
use
cases
X Private
network
X Real-足<me
remote
control
use
cases
(<1s)
X Frequent
soKware
update
OTA
X Low
latency
(<1s)
6. SAMPLE B2B
CUSTOMERS
Smart
Ci<es
Public
parking
monitoring
Asset
management
Billboard
monitoring
Asset
tracking
Waste
management
U<li<es
Water
metering
Healthcare
Fall
detec8on
Distress
bu:ons
Medicine
dispensers
Home
care
management
7. SAMPLE B2C
CUSTOMERS
Pet
tracking
Pet
health
monitoring
Pet
loca8on
services
Security
Remote
alarm
transmissions
Bike
&
car
security
Bicycle
recovery
services
Car
recovery
services
Climate
monitoring
Indoor
air
monitoring
Climate
monitoring
8. Country covered (80% of population & light indoor)
City coverage
FRANCE
SPAIN
UK
NL
PORTUGAL
Korea
Singapore
Mumbai
Ume奪
Warsaw
Munich
ITALY
IRELAND
CZECH REPUBLICBELGIUM
Santiago
Bogota
COVERAGE AT Q1 2016
DENMARK
USA NYC
SF
LA
Seattle
Denver
Houston
Dallas
Austin
San Jose
Boston
Atlanta
Chicago
> 1 MILLION SQ MILES
60 COUNTRIES DEPLOYED
WITHIN 5Y
+ $150M RAISED
10. PHILOSOPHY
OF SIGFOX
NETWORK
THE TECHNOLOGY TO
MEET THE IOT
STRATEGY:
- LOWEST TCO
- OUT OF THE BOX
CONNECTIVITY
- LOWEST ENERGY
- GLOBAL REACH
FARTHEST SATELLITE
FROM EARTH USES
UNB BPSK
Lowest TCOLowest Energy
Bidir is device initiated
Sleep time maximized
Small messages
14 bytes of header + 12
bytes max of payload
Use existing chipsets
Global reach
Unlicensed spectrum
ISM band: ETSI 868Mhz / FCC 902Mhz
No synchronization with base stations
Sleep time maximized Simple processing
Long range to reduce number of base stations
Large link budget = 160dB
High capacity network for scalability
Low radiated power
25mW @ 100bps ETSI
150mW @ 600bps FCC
Out of the box
connectivity
No pairing
Public network
Strong resistance to interference
Ultra Narrow Band BPSK is the way to go
12. UNB
RESISTANCE TO
INTERFERENCE
UNB BEST
TECHNOLOGY
AGAINST INTERFERER
UNB CONCENTRATES THE ENERGY
At equal power UNB concentrates energy in a very small
bandwidth = higher power spectral density
UNB REDUCES CHANCES OF COLLISION WITH INTERFERER
Small bandwidth reduces probability of collision with high power
interferer
SIGFOX + conventional signals at same spectrum and power no loss
COLLABORATIVE NETWORK MITIGATES INTERFERER IMPACT
Having 3 base stations at 3 different locations reduces the impact of
interferers in the message delivery
13. HIGH
CAPACITY
CAPACITY MEASURED ON
THE FIELD
UNB IS BEST SUITED FOR
HIGH CAPACITY
ULTRA NARROW BAND ALLOWS HIGH CAPACITY
@ 10message/day/device = 1.8M devices per base station
200 simultaneous messages within a 200kHz channel
Future
proof
:
2M
messages
per
base
sta8on
and
aGer
:
cell
size
reduc8on,
add
another
200kHz
channel
14. UNB VS
SPREAD
SPECTRUM
(SS)
BETTER RESISTANCE TO
INTERFERER
NO COLLABORATIVE
NETWORK
HIGHER CAPACITY
UNB BETTER RESISTANCE TO INTERFERER
Interferers in ISM band :
SS CANNOT BENEFIT OF THE COLLABORATIVE NETWORK
SS has to be a point to point communication
Different devices using the same spreading code with different base stations will interfere
each other
UNB HAS HIGHER CAPACITY
- Can be very high power FCC req
is P<4W
- Are hoping fast FCC req is less
than 400ms
Chances of having a blocking
interferer in SS are higher than UNB
UNB vs SS
For same bandwidth more capacity
16. Customer IT
UPLINK
MESSAGE
NO NETWORK
SYNCHRONIZATION
MOST SIMPLE DESIGN
PROTOCOL
Each uplink message is self contained less than 26 bytes
UPLINK TRANSMISSION
preamble
frame
sync
device ID
payload container
0 - 4 - 8 12 bytes
authentication
hash
CRC
Base
stations
SIGFOX
CLOUD
1. Device sends
message when
needed
2. SIGFOX base
stations collect the
message
3. SIGFOX cloud
authenticates the message
and regroup the duplicates
4. SIGFOX cloud
pushes the message to
the customer IT
17. BI DIRECTIONAL
MESSAGE
DEVICE INITIATED MAXIMIZE SLEEPING
MODE
Customer ITBase
stations
SIGFOX
CLOUD
1. Device sends message
when needed with
bidirectional request
2. SIGFOX base
stations collect the
message
3. SIGFOX cloud
authenticates the message
and regroup the duplicates
4. SIGFOX cloud
pushes the message to
the customer IT
5. Customer IT replies
to the bidirectional
request
6. SIGFOX cloud requests
the base station close by to
send the reply
7. SIGFOX base
station send the
message
8. Device gets the
reply and
acknowledges it
19. RADIO
SECURITY
IDENTIFICATION
AUTHENTICATION
RESISTANCE TO
SPOOFING AND
JAMMERS
IDENTIFICATION AND AUTHENTICATION
Each device contains a unique ID and secure key
- Identification is done with the ID
- Authentication is done with an AES encrypted signature sent in the
header
RESISTANCE TO SPOOFING
Each message contains a sequence number
SIGFOX cloud detects differences in the sequence number
RESISTANCE TO JAMMING
No synchronization is required to send messages on the SIGFOX network
So jamming the device receiver will not affect the delivery of the uplink
message
22. BUILD A SIGFOX READY DEVICE
端錫 Choose your FCC SIGFOX Ready technological block
端錫 Sign the relevant SIGFOX Ready certification program agreement
端錫 Get access to SIGFOX cloud and support to build your device
端錫 Submit your final product to the SIGFOX certification team
MINIMUM INTEGRATION
EFFORT
OUT-OF-THE BOX
CONNECTIVITY
BUILD A SIGFOX
PRODUCT
No coverage yet?
SIGFOX can loan base stations
23. TYPICAL
HARDWARE
ARCHITECTURE
Microcontroller
Runs SIGFOX stack.
MCU can be dedicated to
SIGFOX stack or run the
application and the SIGFOX stack
Transceiver Generates
and decodes RF signals
RF front end
Amplifies signals for
longer range.
ETSI spec SIGFOX
radios do not need a PA
PA/
LNA
Tx/Rx MCU
App
MCU
App microcontroller
Runs the application of the device
Optional if the module MCU is powerful
enough for the application
Communication module
Sensors
Sensors
Provides the data to
your device
Battery
Battery
Sourcing the good battery for your
device is key to guarantee its longevity
24. TYPICAL
SOFTWARE
ARCHITECTURE
Application stack
SIGFOX library
Modulation
Transceiver interface
Full stack provided and
supported by chip
manufacturers partner on their
reference design
Have to be
implemented by the
customer if they do not
use the chip
manufacturer ref design
Provided by SIGFOX
free of charge after
signature of a P1
certification program
Customers
responsibility
SIGFOX uses BPSK modulation for uplink. This is implemented on the micro
controller closely controlling the transceiver
SIGFOX uses GFSK modulation for downlink. This is a standard modulation
available on most sub Ghz chip on the market.
25. UPLINK
MESSAGE
EXAMPLE
12 BYTES ENOUGH
FOR SENSING AND
TRACKING
From 0 to 12 bytes, max 140 messages per day:
≒ 6 bytes: GPS coordinates
Location report with below 3m precision (GPS technical accuracy is
above 3m)
≒ 2 bytes: temperature reporting
Lab thermometer with -100属/+200属 range, 0.004属 precision
≒ 1 byte: speed reporting
Speed Radar up to 255km/h
≒ 1 byte: object state reporting
Up to 8 switches report like set in day/night, hot/cold, on/off
≒ 0 byte: heartbeat
Object is in working state, battery is OK....
≒ 0 byte: Request for duplex operation
Do you have some information for me?
26. BIDIRECTIONAL
MESSAGE
EXAMPLE
CONFIGURATION
UPDATE POSSIBLE
8 bytes, max 4 messages per day:
≒ Change configuration (4 billion possibilities)
Change operational mode, add color indicator of danger probability...
≒ Adjust sensor scale
Change sensor vibration sensibility of seismograph if too many
reports...
≒ Adjust messages frequency
Request close surveillance of water lever after rain...
≒ Request additional data
Request status of solar panel if battery drain is too high...
≒ Request firmware upgrade (through high throughput
connection)
Ask object to perform an update using GSM because of outdated
version...
28. MANAGE YOUR
DEVICE
MANAGE YOUR DEVICES
Users are attached to groups and have user rights associated to each
group
Devices are attached to a device type which is attached to a group and a
contract
29. CREATE YOUR
DEVICE TYPE
CREATE YOUR DEVICE TYPE
Device type is necessary for the device to be created. Callbacks are
managed at the device type level
30. CREATE YOUR
CALLBACKS
CREATE YOUR CALLBACKS
Callbacks are actions that will be performed when a message (or an
event) arrives on the SIGFOX cloud