11. CONFIDENTIAL
Connected Boilers
11
Create an affordable solution to monitor boilers and
create new services for customers.
Challenge
“e.l.m. leblanc early on recognized the value for our
professional customers, channel partners and for end
users of equipping and installing smart boilers” - Frédéric
Agar, e.l.m. leblanc’s president
12. Stolen Car Recovery
CONFIDENTIAL 12
Locate and recover stolen assets
through a small and discrete GPS
tracking device.
Challenge
LIVE
14. Complex ?
You send one AT command to your module
You receive the answer on your server
14
15. CONFIDENTIAL 15
HIGH ENERGY EFFICIENCY
to offer maximum autonomy to remote objects
Designed to maximize energy
efficiency
No Pairing
15 to 45 mA during a few
seconds (25mW; 14dB)
depending on the chip and the
size of the payload
Idle consumption: negligible
Idle state
Communication state
6 nA
30 mA
Current
Time
~6 sec
99.x% of the time
✓
✓
✓
✓
17. ETSI Regulation / ISM bands
Free ISM bands = Sharing rules.
1% emission each hour rule.
1% of 1 hour = 3600 sec / 100 = 36 secs of emission
1 message sigfox = 6 seconds
So we can send 36/6 = 6 messages per hour (12 bytes)
18. Long range
Ideal cases
• +200 kms( record at 1282)
Reality
• City : 2-10 km
• Rural : up to 100km.
18
19.
20. CONFIDENTIAL 20
HIGH NETWORK CAPACITY
ability to scale to the billions of objects to come
UNB
Frequency &
Time diversity
Spatial
diversity
+ + = Massive capacity &
High Quality of Service
21. CONFIDENTIAL 21
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
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
8 dB needed for
the signal to be
received
Jamming signal
✓
✓
Interference
impact
22. CONFIDENTIAL
ENCRYPTION OPTIONS : depends on the use case !
22
1. No encryption at all
• Saves on BOM and power consumption of the device
2. Sigfox encryption
• Requires a Sigfox validated Secure Element (multiple vendors)
• Sigfox will present a decrypted payload to user on the backend interfaces
(App, API, Callback)
3. End to end encryption (by the customer)
• Full implementation by the customer (device and application)
• Sigfox will transport an encrypted payload,
• Possible to reuse a Sigfox validated Secure Element, but not compulsory
23. SIGFOX SERVICE
CONFIDENTIAL 23
Customer ITBig Data
analytics
platforms
Object data Transmitted
through its radio
protocol on the
public spectrum
Global
network
SIGFOX
cloud
24. CONFIDENTIAL
OUTBOUND INTERFACES
24
1. Web application (aka the Sigfox backend)
• Technical interface : devices, device types, groups, users management…
• Raw payload view : No analytics, BI or business application.
2. HTTP REST API
• Same features as the backend, but scriptable,
• Customer applications pulls messages from the backend,
3. Callbacks
• Push messages to a specified URL / email
• Multiple callbacks are possible.
26. Additional: Geolocation
• New geolocation service
• Works with all devices on our network,
• KM accuracy , depends on density.
• Perfect for most of industrial tracking
28. What Sigfox is perfect for
28
•Devices which travel (asset tracking etc.)
•Sensor data monitoring
•Security use cases (as a backup)
•Agriculture
•Etc.
29. What Sigfox can’t do (Sigfox only)
29
• Devices who need a huge number of messages ( ATM, POS etc.)
o But you can do predictive maintenance or geolocation
• Important payloads ( Camera, videos, etc.)
o But you can do WIFi peering
• Device you need to wake up remotely instantly ( garage doors.. )
o But you can monitor activity
31. build.sigfox.com
• Evolutive online platform to support device makers and solution
providers at every stage of their journey
• Centralized document resource center
• Support for device development & tooling
• Simplify certification process
32. How to start ?
• Devkits !
• Works in couple of minutes
• Lots available (SNOC, Pycom, Arduino…)
• Connectivity is included for developers
33. Process (simplified)
• From 4 months to 24 months
• Understand your Market / Finance
• Hire professionals or go to an incubator (Hardware is
HARD)
1st contact
techno
Prototype 1st series
2nd series /
POC Certifs Prod Sales
34. What is a sigfox device ?
• Sigfox module
• Antenna
• Battery
• Sensor
• Casing
41. So.. Which one to choose ?
It all depends on the use case!
Most important:
• SDK?
• Other connectivity?
• Support?
• Price?
• Power Consumption?
• Availability?
• Size?
42. Antenna : THE most important
part
PLAN IT WHILE DOING YOUR PCB
• Balance between design & perf
• Depends on the use case
• Target best radio performance
• Hire an antenna guy if you need so
• https://build.sigfox.com/antennas
42
43. Antennas
• Lots of providers on shelves (Molex, Pulse, Linx..)
• Can do your own
• All depends what you have & need!
• Sens’it antenna: Open source design
45. Batteries
• Sigfox predictability: no signaling,
1 message = X uAh
• Different types of batteries = Different
Use Cases
Rechargeable device?
Size constraints?
Radio Zone has little impact on battery life
• Peak current while transmitting
20 to 50 mA in Europe, 130 to 250 mA in US
Coin cell: short lifetime
Can work with extra
(super)-capacitor circuit
Prefer multiple smaller
batteries over a big one
46. Batteries life example
• 10 msg (UL) + 1 DL / day
• 6 bytes
• Zone 4 Wisol module
• Idle + Sensor = 1 uA
Lithium , 2 Ah = 1140 days
Alkaline, 2 Ah = 3400 days
• 50 msg (UL) + 1 DL / day
• 0 bytes
• Zone 4 Wisol module
• Idle + Sensor = 1 uA
Lithium , 2 Ah = 618 days
Alkaline, 2 Ah = 1100 days
Sigfox trackerSensor
47. Casing
Completely depends on use case
• IPXX ?
• Size ?
but few advices:
• Plastic is always better for radio than metal
• Consider shelf casing
• Don’t aim for the smallest, aim the use case !
48. Radio zones
• RZ1: Europe, MEA
868 MHz, +14 dBm
• RZ2: North America, Brazil
902 MHz, +22 dBm
• RZ3: Japan, Korea
920 MHz, +14 dBm, LBT
• RZ4: South America
920 MHz, +22 dBm
49. Multi radio zones devices
• Hardware Single Zone
Different Hardware (modules)
Different module version but same pinout/PCB
• Hardware Multi Zones
Same Hardware, stay in the same zone
Set zone during production/firmware flashing
• Software Multi Zones: Monarch service
Same hardware, moving interzone
For specific worlwide asset tracking use cases
Require specific Sigfox firmware on module (more information coming soon)
50. Testing tools
• SDR Dongle
• End to End testing (not for prod)
• RSA (Radio Signal Analyzer)
• Included in SDR dongle
• Test radio compliance
• Litepoint analyzer IQxel-M
• RF testing (WiFi, BLE, Sigfox)
• Manufacturing tests
• Pre-certification
51. Transceiver Compatibility
•Texas Instruments: CC1120, CC1125,
CC1310, CC1350
•Silicon Labs : EFR32, EZR32
•Semtech : SX1272, SX1276
51
Need a Sigfox Verified to integrate
the Sigfox Stack
52. Sigfox presentation
Credentials management
52
ID = unique identifier for radio solutions provided by Sigfox
PAC = One-time Security code for ownership management
To register a device on the Sigfox backend, you need both codes.
• These Credentials are « preloaded » within the modules.
• You need to « read » them from the device on the production line
to understand which device in which box. (AT command)
• Print your own Serial N° on the box : no ID/PAC
• PAC code changes when used : owner the device can get the new
PAC on the Sigfox backend
55. • Sigfox VerifiedTM
Integration of the Sigfox stack
For modules & big volumes
Conducted tests
7.5k€
Sigfox ReadyTM
For all End Products
Radio tests
Approx 2.5k€
55
Certification for Modules & Devices
Certified product = Sigfox VerifiedTM + Sigfox ReadyTM
56. Sigfox presentation
Sigfox ReadyTM process
56
2 steps process :
1) Do the testing with accredited test
houses (<1k€)
2) Once done, Certification Filling with
Sigfox automatically trough
build.sigfox.com ( 1.5k€ and 1k)
• No need for Certification for POCs &
prototypes ( <200)
• Can be done very fast.
57. Sigfox Ready : tests performed
Maximum ERP and radiated power diagram
The device maximum ERP is measured to assess product transmitter radiated performances.
U0 (indoor) U1 (outdoor) U2 (Ourdoor high) U3
16dBm> EIRP >12dBm 12dBm>EIRP≥7dBm 7dBm>EIRP≥2dBm Below 2dBm
RC1
59. • Public coverage
• France : 95% outdoor, 85% indoor
• 17 countries fully covered (+= 85% indoor )
• 20+ deploying right now
• Additional coverage
• Mini Base station ( Connectivity As A Service )
• Repeater
• More coming
Coverage : multiple options
60. • For Rural & Deep indoor coverage
• Thousands of devices capacity
• 40€/ month
• Still public access point
• You still pay the connectivity
• Larger range to come
Connectivity As A Service
61. • « Edge coverage » (Rural or indoor)
• Few devices
• 40 euros (lower for next gen)
• 5 Years battery life
• No downlink
Repeater