5. • Sigfox: Global LPWA network
Low power,
to provide autonomy
Global,
to be used everywhere
Low cost,
Low power,
to provide autonomy
Global,
to be used everywhere
Low cost,Low cost,
to address everything
Easy to use,
and adopted quickly
Low cost,
to address everything
Easy to use,
and adopted quickly
5
12. WHAT DO WE PROVIDE?
A network for connected objects transporting the data from your device to your IT systems
Customer ITBig Data
analytics
platforms
Object data Transmitted
through its radio
protocol on the
public spectrum
Global
network
SIGFOX
cloud
Partners with
specific
applications for
your business
Data storage
and
intelligence for
verticals
Identification
and
authentication
integrity
0 to 12-byte
messages
optimized for
sensor data
High capacity
network: over 1
million messages
per Base station
per day
0 to 140
messages per
day per device
12
18. Sigfox Uplink data payload
Less is more !
GPS coordinates (lat x lng) : 6 bytes
Temperature: 2 bytes
State reporting : 1 byte
Heartbeat, update request : 0 byte Keep it as simple as possible
18
24. Sigfox Ultra narrow band technology
Anti-jamming capabilities due to UNB intrinsic ruggedness coupled with spatial diversity of the base stations (+20dB)
HIGH RESILIENCE TO INTERFERERS
robust to operate in the public ism band
8 dB needed for
the signal to be
Jamming signal
✓✓
For the same technical reasons as above, UNB is extremely robust in an environment with other spread
spectrum signals. However, Spread spectrum networks are affected by UNB signals. Ultra Narrow Band is
therefore the best choice to operate in the public ISM band
the signal to be
received
✓✓
Interference
impact
24
45. Sigfox backend cloud access interfaces
API, to request, create or alter a specific data
through HTTP request. The originator of the
request is a computer running a computer
program, to do specific tasks. Most of theprogram, to do specific tasks. Most of the
data operations are available through API,
such as group creation, device registration,
callback creation, etc.
45
46. Sigfox backend cloud access interfaces
Following API documentation, the REST principle
(usage of POST, GET, DELETE, PUT HTTP requests) is
use for Sigfox API: any access to APIs is done
through an authenticated HTTPS request, with the
API usage
through an authenticated HTTPS request, with the
URL shown in the documentation, and the
potential parameters as explained in the
documentation.
46
59. Sigfox Uplink messages callback message to HTTP Restful call
Callback types
Each callback type shares a set of common variables :
time (int) :the event timestamp (in seconds since the Unix Epoch)
UPLINK
This subtype does not define any additional variable.
BIDIR
59
ack (bool): true if this message needs to be acknowledged, false else.
The client can decide not to send any answer to the device. There are 2 ways to do so :
respond to the callback with the HTTP NO_CONTENT code (204).
respond with a json data containing the noData field ex :
{ "0CB3" :
{
"noData" : true
}
}
60. Sigfox Uplink messages callback message to HTTP Restful call
DATA
device (string): device identifier (in hexadecimal – up to 8 characters <=> 4 bytes)
duplicate (bool): «true» if the message is a duplicate one, meaning that the backend has already
processed this message from a different base station, «false» otherwise.
snr (float): the signal to noise ratio (in dB – Float value with two maximum fraction digits)
rssi (float): the RSSI (in dBm – Float value with two maximum fraction digits). If there is no data
to be returned, then the value is null.
avgSnr (float): the average signal to noise ratio computed from the last 25 messages (in dB –
Float value with two maximum fraction digits) or «N/A». The device must
60
Float value with two maximum fraction digits) or «N/A». The device must
have send at least 15 messages.
station (string): the base station identifier (in hexadecimal – 4 characters <=> 2 bytes)
data (string): the user data (in hexadecimal)
lat (float): the latitude, rounded to the nearest integer, of the base station which received the
message
lng (float): the longitude, rounded to the nearest integer, of the base station which received the
message
seqNumber (int): the sequence number of the message if available
71. Simply create a SERVICE > GEOLOC callback, and
receive latitude + longitude + accuracy
71
72. • Create a new
Service > Geoloc
callback
• Use following URL
to center the map:
• https://maps.googleapis.com/ma
ps/api/staticmap?center={lat},{ln
Sigfox Geoloc callback
ps/api/staticmap?center={lat},{ln
g}&zoom=13&scale=1&size=600x
300&maptype=roadmap&format
=png&visual_refresh=true
72
75. Monitor break in sequence number
• New Event: Device > Event Configuration > New
• Select Event Type « Out of message sequence »
• Select « EMAIL » as channel and enter your email
address and email contentaddress and email content
75
76. Monitor break in sequence number
• Remove the antenna to simulate a
coverage issue
• Send a message
• Re-attach the antenna and send a new
message
• Check reception of email notification
76
103. Add a New Device:
https://www.youtube.com/watch?v=Kphi4j1JGec&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=5
See The Device Messages:
https://www.youtube.com/watch?v=xJIzvg70UEg&index=6&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb
Add a Callback:
https://www.youtube.com/watch?v=dDNY-xAxECE&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=7
Add a New User:
Sigfox Technology Overview Video summary #2
Add a New User:
https://www.youtube.com/watch?v=-FHk25dfIEA&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=8
Integrate API's:
https://www.youtube.com/watch?v=qqSkoopzoJw&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=9
Check Coverage With The Service Map:
https://www.youtube.com/watch?v=Oike19mLoYU&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=10
103
