We still have our two entities that have split up at the top and at the bottom of the screen. 1
At the top there is the LoRaWAN server. 2
And at the bottom there is the IoT platform with the user application. 3
Let's look at the uplink stream first. 4
In fact, if you think about it, the ideal solution isn't that the IoT platform requests the opening messages, 5
but instead it would be much better if the LoRaWAN server could push these messages without being 6
requested. 7
This is possible with the HTTP protocol, but the request will be different from the one we saw before. 8
This time the request is called an HTTP POST request and not HTTP GET. 9
In that case, the LoRaWAN server is the client and the IoT platform is the server to which we'll 10
connect to send the uplink messages. 11
With this way of proceeding, each time a data arrives, it's transmitted. 12
We can say that each time a data arrives it's POSTED. 13
Hence the name HTTP POST request. With an HTTP POST, 14
there is a very low latency between the time it arrives on the client and the time it arrives on the 15
IoT platform. 16
It's almost sent instantaneously. 17
For the downlink now, we'll have exactly the same approach. 18
The user downlink is stored on the IoT platform and in the same way the IoT platform will post the downlink 19
message using an HTTP POST request. 20
In that situation, the IoT platform is the client and the LoRaWAN server is the HTTP server. 21
With this way of doing it, each time a downlink message is generated by the user, it's transmitted 22
to the LoRaWAN server. 23
We can also say that it's POSTED, and therefore, there is a very low latency between the time the downlink 24
message is generated on the IoT platform and the time it arrives on the LoRaWAN server. 25
So let's make a demonstration of this and this time we'll do it in both directions: 26
So uplink and downlink messages.