# A Smart Parking Solution Architecture Based on LoRaWAN and Kubernetes
## 3 Analysis of Previous Works  
### Analysis of Works Based on Sensors  
The reviewed propose several ways to deploy a smart parking solution. Some of them emphasize on the types of sensors that might be used for deploying such solution as in [24]. Meanwhile, there are others that do not use specific purpose sensors and they attach sensing modules to Arduino or similar devices. These microcontrollers do not have the same energy autonomy properties as specific purpose sensors. Moreover, these microcontrollers are not IP68 compliant which make them no suitable for adverse weather conditions. Sensors must be able to sense the presence of a vehicle no matter the weather. Therefore, sensors in a smart parking solution have to be able to work under severe weather conditions (i.e., rains, dust). Likewise, sensors should be able to transmit information over long-range perimeters with low energy consumption. These sensors should not be invasive as RFID, but effective when determining vehicle presence and avoid false-positive detections. Based on that, magnetic sensors are the ones that best fit the detection requirement and will be part of the proposed solution.  
\begin{table}
\begin{tabular}{l l l l l} \hline
**Reference** & **Technology** & **Smart Parking Layer** & **Features Identified** \\ \hline
[5] & HTTP & Application & **0** & Unnecessary metadata \\ \hline
[14] & LoRaWAN & Network Infrastructure & ✓ & Long-range \\  & & & ✓ & Low-power consumption \\ \hline
[11] & Wi-Fi (WLAN) & Network Infrastructure & **0** & Short-Range \\  & & & **0** & Power consumption \\ \cline{2-5}  & Ultrasonic sensors & Sensing & **0** & Noise interference \\ \hline
[15] & Ultrasonic sensors & Sensing & **0** & Noise interference \\ \cline{2-5}  & Wi-Fi (WLAN) & Network Infrastructure & **0** & Short-Range \\  & & & **0** & Power consumption \\ \cline{2-5}  & Raspberry & Network Infrastructure & **0** & Limited resources \\  & & & **0** & Not a gateway \\ \cline{2-5}  & MQTT & Application & ✓ & Message Queuing \\ \hline
[16] & UDP & Network Infrastructure & Prone to packet loss \\ \hline
[18] & LoRaWAN & Network Infrastructure & ✓ & Long-range \\  & & & **0** & Low-power consumption \\ \cline{2-5}
[17] & MQTT & Application & **0** & Message Queuing \\ \cline{2-5}  & RFID & Sensing & **0** & Invasive \\  & & & **0** & Very short-range coverage \\ \hline
[21] & Wi-Fi (WLAN) & Network Infrastructure & **0** & Short-Range \\  & & & **0** & Power consumption \\ \cline{2-5}  & MQTT & Application & **0** & Message Queuing \\ \hline
[8] & Arduino Uno & Sensing & **0** & No specific purpose \\ \cline{2-5}  & Ultrasonic sensors & Sensing & **0** & Noise interference \\ \cline{2-5}  & Wi-Fi (WLAN) & Network Infrastructure & **0** & Short-Range \\  & & & **0** & Power consumption \\ \hline
[21] & RFID & Sensing & **0** & Invasive \\  & & & **0** & Very short-range coverage \\ \cline{2-5}  & Wi-Fi (WLAN) & Network Infrastructure & **0** & Short-Range \\  & & & **0** & Power consumption \\ \hline
[22] & MQTT & Network Infrastructure & ✓ & Message Queuing \\ \hline
[24] & Ultrasonic sensors & Sensing & **0** & Noise interference \\ \cline{2-5}  & Direct connection & Application & **0** & Scalability \\  & & & **0** & Multiple connections \\ \hline
[25] & Cameras & Sensing & **0** & Require more processing \\  & & & **0** & Lack of reliable algorithms \\ \hline \end{tabular}
\end{table}
Table 1: Summary of technologies, layers, features and issues identified.