Projekt LoRaWAN: Unterschied zwischen den Versionen

Aus Opennet
Wechseln zu: Navigation, Suche
(Anbindung)
(Plan)
Zeile 58: Zeile 58:
  
 
= Plan =
 
= Plan =
 +
 +
== Nutzen für Opennet ==
 +
 +
* Neues Projekt
 +
* Bereitstellen eines Community LoRaWANs in Rostock und ggfs. sonstwo
 +
* Eigene Nutzungsmöglichkeiten
  
 
== Standorte ==
 
== Standorte ==

Version vom 14. März 2018, 11:24 Uhr

Inhaltsverzeichnis

Knowledge LoRa / LoRa-WAN

Einsatzmöglichkeiten

Protokoll

LoRaWAN Klassen (ausLoRaWAN Backend Interfaces 1.0 Specification)
  • Layer 1 - Chirp Spread Spectrum
  • Layer 2
    • Bi-directional end-devices (Class A): End-devices of Class A allow for biirectional communications whereby each end-device’s uplink transmission is followed by two short downlink receive windows. The transmission slot scheduled by the end-device is based on its own communication needs with a small variation based on a random time basis (ALOHA-type of protocol). This Class A operation is the lowest power end-device system for applications that only require downlink communication from the server shortly after the end-device has sent an uplink transmission. Downlink communications from the server at any other time will have to wait until the next scheduled uplink.
    • Bi-directional end-devices with scheduled receive slots (Class B): End-devices of Class B allow for more receive slots. In addition to the Class A random receive windows, Class B devices open extra receive windows at scheduled times. In order for the End-device to open its receive window at the scheduled time, it receives a time synchronized Beacon from the gateway.
    • Bi-directional end-devices with maximal receive slots (Class C): End-devices of Class C have nearly continuously open receive windows, only closed when transmitting. Class C end-device will use more power to operate than Class A or Class B but they offer the lowest latency for server to end-device communication.
LoRaWAN Network Reference Model (NRM), roaming End-Device (aus LoRaWAN Backend Interfaces 1.0 Specification)

Hardware

Gateways

Endgeräte

  • Anwendungen vor allem Sensordaten erfassen, Fernsteuern, Überwachen

Server-Software

Plan

Nutzen für Opennet

  • Neues Projekt
  • Bereitstellen eines Community LoRaWANs in Rostock und ggfs. sonstwo
  • Eigene Nutzungsmöglichkeiten

Standorte

Bei 2km Reichweite in Städten würden wir mit den ersten drei Gateways schon die komplette Innenstadt abdecken.

LoRaWAN.jpg

Anbindung

Was wir tun müssten

  • Gateways aufstellen
  • LoRaWAN Network Server bereitstellen
  • Eventuell Anbindung an The Things Network
  • Standorte so planen, dass gesamte Stadt abgedeckt wird

Kosten

  • Gateways ab 100,-EUR ohne Outdoor-Gehäuse und Antennen
  • Eigene Clients zum Basteln je nach Anwendung
Meine Werkzeuge
Namensräume

Varianten
Aktionen
Start
Opennet
Kommunikation
Karten
Werkzeuge