This document provides an overview of Sigfox technology, including Sigfox networks, protocols, modules, services, security features, and backend APIs. Key points covered include Sigfox's ultra narrow band technology, lightweight protocol supporting small payload messages, global network coverage, and web-based backend interfaces for accessing device and message data through APIs. Examples are given of configuring callbacks and using REST clients to test the Sigfox backend APIs.

1. 1

2. Sigfox technology
Backend
Callback & API
Speaker：MakerPRO Consulter Tiger Ko (柯大)
E-mail ：kochingchang@gmail.com
Mobile Phone： 0928226125
2

3. https://goo.gl/c9SA35
3

4. Network Standards Landscape
Source of information:keysight.com 4

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

6. IoT Low Power WA Network
6

7. Sigfox vs LoRa technology compare
7

8. Sigfox vs LoRa technology compare
8

9. Sigfox protocol stack
9

10. Sigfox protocol stack
10

11. Sigfox protocol stack
11

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

13. Sigfox IoT data transport services
13

14. Sigfox Uplink and Downlink small messages
14

15. Sigfox Lightweight protocol
15

16. Sigfox Lightweight protocol
16

17. Sigfox Small message carry
17

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

19. Sigfox Uplink and Downlink message 8 bytes
19

20. Sigfox Bi-directional communication transport
20

21. Sigfox Hight energy efficiency
21

22. Sigfox Ultra narrow band technology
The network currently monitors a 192KHz part of the spectrum
Each message is ~100Hz wide
22

23. Sigfox Ultra narrow band technology
23

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

25. Sigfox Ultra narrow band technology
25

26. Sigfox Ultra narrow band technology
26

27. Sigfox Ultra narrow band technology
27

28. Sigfox Ultra narrow band technology
28

29. Sigfox Security technology
29

30. Sigfox Security technology
30

31. Sigfox Security technology
31

32. Sigfox Security technology
32

33. Sigfox Worldwide radio zones
33

34. Sigfox Modules architectures
Check out http://partners.sigfox.com for the full details.
34

35. Sigfox Modules architectures
35

36. Sigfox Modules architectures
36

37. Start using Sigfox IoT devices
37

38. Activie Sigfox modules
38

39. Activie Sigfox modules
39

40. Buy Sigfox connectivity
40

41. Sigfox backend cloud services architecture
41

42. Sigfox backend cloud access interfaces
42

43. Sigfox backend cloud access interfaces
43

44. Sigfox backend cloud access interfaces
44

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

47. Sigfox backend webbase
Platform AccessPlatform Access
47

48. Sigfox backend webbase platform interfaces access
https://backend.sigfox.com/
48

49. Sigfox backend webbase platform interfaces access
49

50. Sigfox backend webbase platform interfaces access
50

51. Sigfox backend webbase platform interfaces access
51

52. Sigfox backend webbase platform interfaces access (GROUP)
52

53. Sigfox backend webbase platform interfaces access (USER)
53

54. Sigfox backend webbase platform interfaces access (DEVICE TYPE)
54

55. Sigfox backend webbase platform interfaces access (DEVICE)
55

56. Sigfox backend webbase platform interfaces access (DEVICE MESSAGE)
56

57. Callback Access
57

58. Sigfox Uplink messages callback message to your webservices
58

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

61. Sigfox Uplink messages callback message to your webservices
61

62. Sigfox Uplink messages callback message to your webservices
62

63. Sigfox Uplink messages callback message to EMAIL
63

64. Sigfox Uplink messages callback message to HTTP Restful call
64

65. Sigfox Uplink messages callback message to HTTP Restful call
Payload deconding
65

66. Sigfox Uplink messages callback message to HTTP Restful call
Payload deconding example
66

67. Sigfox Uplink messages callback message to HTTP Restful call
Payload deconding example
Format Message (in hex) Result
int1::uint:8 int2::uint:8 1234 { int1: 0x12, int2: 0x34 }
b1::bool:7 b2::bool:6
i1:1:uint:16
C01234 { b1: true, b2: true, i1: 0x1234 }
b1::bool:7 b2::bool:6
i1:1:uint:16:little-endian
801234 { b1: true, b2: false, i1: 0x3412 }
67
i1:1:uint:16:little-endian
b1::bool:7 b2::bool:6
i1:1:uint:16:little-endian
i2::uint:8
80123456
{ b1: true, b2: false, i1: 0x3412,
i2:0x56 }
str::char:6 i1::uint:16 i2::uint:32 41424344454601234567890A
{ str: “ABCDEF”, i1: 0x123,
i2:0x4567890A }
str::char:6 i1::uint:16
i2::uint:27:2
41424344454601234567890A
{ str: “ABCDEF”, i1: 0x123,
i2:0x0567890A }

68. Sigfox Downlink messages
68

69. Sigfox Downlink messages
69

70. Sigfox Downlink messages
70

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

73. Sigfox Geoloc callback
73

74. 74

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

77. https://support.sigfox.com/
https://support.sigfox.com/docs
https://support.sigfox.com/apidocs#section/Introduction
77

78. Sigfox backend API access
78

79. Sigfox backend API access
79

80. Sigfox backend API access
Backend user roles
Read-only roles
CUSTOMER[R], DEVICE MANAGER[R]
Write rolesWrite roles
CUSTOMER[W], DEVICE MANAGER[W]
Role inheritance
80

81. Sigfox backend API access
81

82. Sigfox backend API access
82

83. Sigfox backend API access – Create credentials
83

84. Sigfox backend API access – Create credentials
84

85. Sigfox backend API access – GET
85

86. Sigfox backend API access – GET
86

87. Sigfox backend API access – GET
87

88. Sigfox backend API access – using programming to get message
88

89. Sigfox backend API access – using REST client application tools
89

90. Sigfox backend API access – using REST client application tools
RestMan Http client
90

91. Sigfox backend API access – using RestMan client test GET API
91

92. Sigfox backend API access – using RestMan client test GET API
92

93. https://support.sigfox.com/apidocs#
https://support.sigfox.com/apidocs#tag/Groups
https://support.sigfox.com/apidocs#tag/DeviceTypes
Sigfox backend API access function call
93

94. Sigfox backend API access function call
94

95. https://support.sigfox.com/apidocs#tag/Devices
Sigfox backend API access function call
95

96. Sigfox backend API access function call
96

97. Sigfox backend API access function call
97

98. Sigfox backend API access function call
https://support.sigfox.com/apidocs#tag/Coverages
https://support.sigfox.com/apidocs#tag/ApiUsers
98

99. Sigfox backend API access function call
https://support.sigfox.com/apidocs#tag/Devices
99

100. Sigfox API access version upgrade schedule
100

101. Webservice HTTP status code reference
101

102. Sigfox overview :
https://www.youtube.com/watch?v=CvmCxq91Si4
Overview of The Sigfox Backend:
https://www.youtube.com/watch?v=v0U5honpVYc&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=5&t=0s
Sigfox backend :
https://www.youtube.com/playlist?list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb
Sigfox Cloud Interfaces:
Sigfox Technology Overview Video summary #1
Sigfox Cloud Interfaces:
https://www.youtube.com/watch?v=7gTwFbiiJwE&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=2&t=0s
Sigfox Cloud organization:
https://www.youtube.com/watch?v=Keytbd2r9YI&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=3&t=0s
Sigfox Cloud Interfaces:
https://www.youtube.com/watch?v=7gTwFbiiJwE&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=1
Device management basics: devices and device type:
https://www.youtube.com/watch?v=HebSKvtJFpc&list=PLcw1TnahFRW-dpqGwxa3noSMLP_nTEhdb&index=3
102

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

104. • https://buy.sigfox.com/
• https://backend.sigfox.com/
• https://support.sigfox.com/
• https://support.sigfox.com/docs
• https://backend.sigfox.com/apidocs/callback
• https://build.sigfox.com/backend-callbacks-and-api
• https://support.sigfox.com/docs/custom-callback-creation
• https://partners.sigfox.com/
Sigfox Technology moreresources
• https://partners.sigfox.com/
• https://partners.sigfox.com/products/kit
• https://partners.sigfox.com/search/products?or[businessBenefits][0]=office
• https://resources.sigfox.com
• https://ask.sigfox.com
• https://sigfoxbuilders.herokuapp.com
• https://github.com/luisomoreau/iot-platform#add-sigfox-geolocalisation-service
104

105. Apply for March 5, 2019
https://Thehackinghouse.com
@TheHackingHouse Taipei
kochingchang@gmail.com
105