47
Network Layout
Smart-Home 2 had a more complex network setup compared to the other domotic ex-
ample. In this case the network layout was divided in four areas:
home network, ISP
provider, 3G mobile network and the backend IoT.
Figure 26 - Smart-Home 2 (SaaS) network topology
Despite
the need of four network, the setup was simpler compared to
previous scenario
as the IoT, DNS and DHCP server was not connected to the WLAN. Wireless network
was provided
by a wireless router that, in this case, also provided DHCP functionalities.
Being a simple home network the device setup was done only by using specific SSID
and password. Home cable modem was also utilized only to connect the router to inter-
net, no configuration could be done on this component.
The ISP network, similarly as in the other smart home example, was artificially connect-
ing different interfaces to each other in order to simulate internet connectivity. Coaxial
cables coming from home modem and 3G network provider were linked to the Ethernet
cable where the cloud IoT server was connected.
In order to simulate a remote network, a mobile 3G provider infrastructure was utilized in
this example. This allowed the home owner to connect to the IoT monitoring page using
its own mobile outside the home WLAN. Cellular network setup was very straight-forward
48
and only required a cell tower and a central office center server. Server consolidated all
the signals coming for the tower coaxial cables into a Ethernet backbone connection that,
via
cable modem, was then connected to the ISP network.
Both cell tower and central office server had only a limited amount of parameters that
could be configured. A maximum of six cell tower can be connected to
the central office
server.
The handheld devices were then connected to the 3G cell tower network by setting up
the correct APN name.
In order to simplify the cloud provider network, the remote IoT server was directly con-
nected to the ISP without the usage of any router. Server utilized static IP in order to
make sure that IoT device could always connect to it. DNS services were also running
on this server resolving the IOTSmarthome.com URL address into its own IP.
The setup of the SaaS cloud services utilized in the exercise was artificial and would not
be realistic in a real SaaS scenario.
