O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Presentation SIGFOX for BeMyapp Webinar

short introduction to the SIGFOX network with few technical details

  • Seja o primeiro a comentar

Presentation SIGFOX for BeMyapp Webinar

  1. 1. Anthony Charbonnier Startup relations & evangelist @Anth0_ Anthony.charbonnier@sigfox.com
  2. 2. Basics
  3. 3. Low Power Wide Area Network Ultra low power Ultra long range
  4. 4. Sigfox is not selling chips Sigfox is not building connected solutions Sigfox has invented a radio protocol Sigfox operates a global network
  5. 5. Global reach Cost effectiveness Simplicity Energy efficiency $
  6. 6. How to communicate 1. Detect something to send (that’s the hard part) 2. Power on the communication module 3. Send 4. Message is picked up by the network 5. Data is received on your server
  7. 7. How hard ? 1. Send an AT command (couple lines of code) 2. You receive an HTTP Request on your application server
  8. 8. Core concepts
  9. 9. Energy efficiency Designed to maximise energy efficiency Tx: ~20-35 mA during a few seconds (25mW ; 14dB) Key : idle consumption (unconnected 99.x% of the time)
  10. 10. Out of the box No configuration, no pairing, no signalisation Network serving the device Message is picked up by several base stations
  11. 11. Very Long Range Best case scenario +200 km between transmitter & receiver (base station) In reality A few kms (city) to tens of kms (countryside). highly depend on topography
  12. 12. Outdoor & Indoor Works indoor, But it’s no magic.
  13. 13. Two-way communication BI-directionnal communication : Uplink + Downlink Communication is requested by the device
  14. 14. Small messages payload: 12 bytes 7 msg / hour. ( 140 msg / day ) 100 bits/s
  15. 15. Payload examples GPS coordinates (lat x lng) : 6 bytes Temperature: 2 bytes State reporting : 1 byte Heartbeat, update request : 0 byte And … who needs full bytes when 5 bits are enough ?
  16. 16. Payload examples A (int): 17568 —> 0100010010100000 B (0-32): 17 —> 010001 C (state): 3 —> 10 Frame: 01000100 10100000 01000110 Frame: 0x44 0xA0 0x46 AT$SF=44A046
  17. 17. Low cost, high value. low subscription fees very short SW development cycle low cost HW components ( thx to open hardware approach)
  18. 18. Security Each message is signed with a key unique to the device Messages can be encrypted or scrambled No keys exchanged over the network, no handshake Security is an ever ongoing effort
  19. 19. Radio properties Great tolerance to interferors Jamming resistant Interception is hard: UNB & frequency diversity
  20. 20. Jammers
  21. 21. Interferors
  22. 22. Ultra Narrow Band
  23. 23. Sigfox use Currently spreads on a 200KHz part of the spectrum Each message is ~100Hz wide
  24. 24. Spectrum (undesired signals) 200 KHz wide
  25. 25. Each repetition is 100 Hz wide Messages
  26. 26. Frequencies ISM bands : unlicensed & shared Compliant with regulations Europe : 868MHz (ETSI 300-200) USA: 902MHz (FCC part 15)
  27. 27. Hardware solutions
  28. 28. open hardware approach Established partners: Atmel, TI, Silicon Labs, Axsem, Atim, TD, etc. most Sub-GHz radio transceivers are compatible
  29. 29. prototyping Arduino, Rasberry PI, Atmel etc. Very easy to start but not industrial
  30. 30. Antenna Most important part :) If you don’t know, ask somebody. Always a balance between design & performance
  31. 31. Coverage
  32. 32. This week’s update
  33. 33. Use cases EXAMPLES OF SOLUTIONS ALREADY IN PRODUCTION
  34. 34. Non visible stuff visible stuff Smart parkingsilver economyWater metering
  35. 35. Predictive maintenance Connected Beer
  36. 36. FFLY4U connected pallets
  37. 37. Optibee connected beehive
  38. 38. Weenat connected fields
  39. 39. CAPTURS Outdoor GPS
  40. 40. DOMINO Connected Mail
  41. 41. SensDumpster Connected Trash
  42. 42. Try to make some sense.
  43. 43. Cloud
  44. 44. Get your data View messages : Sigfox web platform Get messages : REST API (pull) Receive new messages : HTTP Callbacks (push)
  45. 45. Callbacks Each message received is pushed to your server Customisable headers & body More than one callback
  46. 46. 3rd party platforms We don’t analyze your data, it’s yours. Integrate your data to a 3rd party platform : AWS, Azure, Telefonica, thethings.iO, OVH, …
  47. 47. Downlink messages A downlink message can be Semi automatic : sent directly by the network Customised : sent by your own application server
  48. 48. Semi automatic callback Set up the message to send, it can be: - an hardcoded frame - pre defined variable (timestamp, rssi)
  49. 49. Downlink callbacks Same mechanism as for the uplink callback : 1. set an URL 2. Reply with the 8-byte downlink frame 3. Respect this JSON format : 1.{ 2. '{{deviceId}}': { 3. 'downlinkData':{{data}} 4. } }

    Seja o primeiro a comentar

    Entre para ver os comentários

  • nicolsc-slides

    Apr. 28, 2016
  • DrMohammadAbdurRazza

    Jan. 26, 2017

short introduction to the SIGFOX network with few technical details

Vistos

Vistos totais

980

No Slideshare

0

De incorporações

0

Número de incorporações

11

Ações

Baixados

48

Compartilhados

0

Comentários

0

Curtir

2

×