Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Presentation TTN Hackathon at Ordina Groningen

Presentation TTN Hackathon at Ordina Groningen

Given by Johan Stokking and Joshua Peper

Avatar for Joshua Peper

Joshua Peper

January 20, 2016
Tweet

More Decks by Joshua Peper

Other Decks in Technology

Transcript

  1. Our mission is to build a decentralized open and crowd

    sourced IoT data network Owned and operated by its users
  2. 21 okt 22 okt 08:15 19:56 stad 26 okt 11

    nov 27 okt 5 nov 1 2 28 dec 5 11 jan 7
  3. Groningen + Drenthe 0 15 30 45 60 75 Amsterdam

    Leiden Eindhoven Groningen Drenthe
  4. Groningen + Drenthe 0 27.5 55 82.5 110 137.5 Amsterdam

    Leiden Eindhoven Groningen + Drenthe
  5. Core Components R Router Routes raw packets from gateways to

    brokers NC Network Controller Node state, data rate and frequency management H Handler Decryption, deduping, works on behalf of apps A Application Application or IoT cloud platform Gateway Send data to and receive data from nodes B Broker Decoupling from router to handler
  6. R H S1, S2 S2, S1, S3 S2, S1, S3

    S3, S2 B Core Components B 041FBA43 R NR P A A H A NC NC uplink downlink
  7. Application and Cloud Platform Integrations H A B Integrate handler

    functionality in application H A B Connect Application with Node RED H NR B A Connect Application with AwS IoT, IBM Bluemix, FIWARE, etc H P B A Connect Application with the open source The Things Handler The Broker and the Handler are offered hosted services by the Foundation, but both services can be installed on-premise as well MQTT MQTT HTTP HTTP HTTP HTTP
  8. Fair Access Policy • Restricted to ETSI norms and capacity

    • We want to support at least 1.000 nodes per gateway • Duty cycle of the gateway (receiving) needs to remain << 10% • Assuming the 8 channels to be used at all SF • Achieved by limiting airtime per node to 30 seconds per day • This limits the duty cycle to less than 5%
  9. Fair Access Policy • Golden rule: 30 seconds airtime per

    device per day • For 10 bytes of payload, this translates in (approx.): • 20 messages per day at slow rate (SF12) • 500 messages per day at high rate (SF7) • more for SF7BW250 and FSK (local-area) • If your application requires more bandwidth, think of another solution • This allows for >1.000 nodes per gateway • Downlink bandwidth is even more restricted
  10. Don’t waste your airtime! • Simple: • { “Count”: 1234,

    "Temperature": 20.635 } • 40 bytes: 292 messages per day (SF7) • Remove counter, spaces, and compress names: • {“t”:20.63} • 11 bytes: 486 messages per day • No JSON: • 20.63 • 5 bytes: 582 messages per day • Signed 16 bit integer • 0x080F • 2 bytes: 648 messages per day
  11. How to get started • Think about a use case

    • Find expertise • Meetups: Sensemakers Amsterdam • Forums • The Things Network Cookbook • Build a prototype • List your requirements • Order stuff • Start coding
  12. Next steps: Q1 2016 • Build 1.0 of The Things

    Network components • Improve our community platform • Build and ship the Kickstarter products • Launch The Things Network Cookbook
  13. Contact and Contribute Do you want to know more, brainstorm

    about your idea, contribute to our community or applyfor an internship? 1. Register on the forum: http://forum.thethingsnetwork.org 2. Join Slack: http://slack.thethingsnetwork.org 3. Sign up for the newsletter: http://thethingsnetwork.org(go to Join Team) 4. Read background information: http://thethingsnetwork.org/wiki 5. Check out GitHub: http://github.com/TheThingsNetwork 6. Send an e-mail: [email protected]