Libelium Waspmote Smart Parking v2, Technical Manual

Page: 10 / 155

Network architecture
Libelium Smart Parking Cloud Service or to the Customer Server.
2.4. Libelium Smart Parking Cloud Service and Customer
Server
The LoRaWAN Network Server connects to the fi nal server, which can be the Libelium Smart Parking Cloud Service
or the Customer Server.
The LoRaWAN network servers currently supported are:
‚
Loriot
‚
Actility
‚
The Things Network
‚
The Things I ndustries
‚
The Embedded Network Server inside MultiTech base stations
I f the customer wants to use a new LoRaWAN Network Server, then the Data Parser block must be modi fi ed in
order to receive data properly. Keep in mind that each Network Server implements its own HTTPS callback using a
di
ff erent format.
The Remote Con fi guration Form allows the user to update the settings of each node (sleep time, keep-alive time,
night-mode, etc). The update is done remotely via LoRaWAN downlink radio packets.
The di ff erence between the 2 types of server di ff er in the the possible client needs:
‚
The Customer Server is a software system provided by Libelium which permits to receive, decode and insert
data into a standard
MySQL database. I t is mandatory that the user sets up her own server to host the
Customer Server. Read the “ Customer Server” chapter for further information.
‚
The Smart Parking Cloud Service is a software service provided by Libelium which permits to receive,
decode and redirect the data to the
fi nal 3rd party I oT cloud (Amazon, Azure, etc). This retransmission is
done thanks to the cloud connectors running on another Libelium Cloud ’ s service: the Bridge. Read the
“ Libelium Smart Parking Cloud Service ” chapter for further information.
- 9 - v7.5