LoRa proxy: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== Architecture == == Uplink == == Downlink ==") |
|||
| Line 1: | Line 1: | ||
== Architecture == | == Architecture == | ||
[[File:lora_proxy_arch_sc.png]] | |||
The LoRa Proxy module is inside a Raspberry Pi. The module will subscribe to two or more LoRaWAN server to get the uplink message from LoRa node. | |||
Architecture flow: | |||
#Cache server inside the web server will subscribe to a MQTT Broker inside a Raspberry Pi. | |||
#The LoRa Proxy inside a Raspberry Pi will subscribe to two or more LoRaWAN Server. | |||
#When node send data from any LoRaWAN Server, The LoRa Proxy in RPi forward those data to MQTT Broker in RPi. | |||
#The cache server subscribe to MQTT Broker will receive the node data from any LoRaWAN Server through MQTT Broker install inside RPi and store those data in its database. | |||
#Whenever user make request to web server. The web server will look for data inside cache server. | |||
== Uplink == | == Uplink == | ||
== Downlink == | == Downlink == | ||
Revision as of 20:24, 20 December 2017
Architecture
The LoRa Proxy module is inside a Raspberry Pi. The module will subscribe to two or more LoRaWAN server to get the uplink message from LoRa node.
Architecture flow:
- Cache server inside the web server will subscribe to a MQTT Broker inside a Raspberry Pi.
- The LoRa Proxy inside a Raspberry Pi will subscribe to two or more LoRaWAN Server.
- When node send data from any LoRaWAN Server, The LoRa Proxy in RPi forward those data to MQTT Broker in RPi.
- The cache server subscribe to MQTT Broker will receive the node data from any LoRaWAN Server through MQTT Broker install inside RPi and store those data in its database.
- Whenever user make request to web server. The web server will look for data inside cache server.