Today at various locations and factories we have a lot of sensors and actuators that interact with each other and a control-unit. The control-unit is in most cases a cloud-based solution. This is in most cases a good solution. However, there is a rise in expected devices and sensors which will most likely be too much data for the existing network to handle. This paper researches if a fog-unit might be the solution to this problem. The setup of the fog-unit in the network is a unit between the cloud and the sensors and actuators. In this paper the fog-unit and sensors/actuators have been emulated on Raspberry Pi’s. The sensors are emulated using python-threads and communicate with the fog-unit using the UDP-based protocol CoAP and the fog communicates to the cloud using the TCP- based protocol MQTT. After a prototype was built it using said Raspberry Pi’s it was sent through a few measurements in the fields of bandwidth, cloud-utilization and response times. This was later compared to another setup without the fog-unit as the control setup. The result with this kind of setup was that a fog-unit lowers the cloud-utilization and use of bandwidth, however it increases the round trip time of a request from the cloud by a large amount. Which leads to the conclusion that a fog-unit in this kind of setup might be a good network solution if the response time to the cloud isn’t important.
| Identifer | oai:union.ndltd.org:UPSALLA1/oai:DiVA.org:miun-34048 |
| Date | January 2018 |
| Creators | Holm, Rasmus |
| Publisher | Mittuniversitetet, Avdelningen för informationssystem och -teknologi |
| Source Sets | DiVA Archive at Upsalla University |
| Language | English |
| Detected Language | English |
| Type | Student thesis, info:eu-repo/semantics/bachelorThesis, text |
| Format | application/pdf |
| Rights | info:eu-repo/semantics/openAccess |
Page generated in 0.0036 seconds