Professional Documents
Culture Documents
SMART HOME
There are several services that are required for a Smart Home service which are:
All smart home devices can communicate using openHAB which drives from Home
Automation Bus. The developer deploys Java and OSGi services and uses the open source
development environment and deployment platform. The following figure shows the architectural
layers in openHAB development environment.
A service in the above figure refers to service capabilities and the protocols that are needed
Internet and Web connectivity using OpenHAB service are, which can be called upon whenever
needed. The above figure shows the following:
There are several design steps in building the Smart Home Application which are
1. Abstraction
2. Reference Model
3. Identifying Requirements of Device and Gateway Domain
4. Identifying Requirements of Network Sub-domain
There are two domains and their high-level service capabilities in the home automation
system in IoT architecture reference model are:
The following diagram shows the data-flow diagram and domain Architecture reference
model for home automation lightning, appliances and intrusion monitoring services.
The above figure shows that openHAB has an event bus which is asynchronous and it refers
to a communication bus for all protocol bindings. The event bus is the base service of openHAB. The
openHAB service is integration-hub between such devices and bindings between different protocols
used for networking the home devices, OSGi and HTTP service.
The appropriate Addressing Mechanisms and the required network sub-domains that are
required are given below:
The Network management functions to ensure secure communication network between device
and gateway domain and applications/services. The openHAB cloud connector connects the local
openHAB runtime to a remote openHAB cloud, such as my.openHAB, instance from openHAB
foundation
Application/ Services layer & Applications support: can be exploited through attacks such as
SQL injection, where the developer has failed to ensure that user input is validated against a defined
schema.
Transport: This layer can be attacked by vulnerable ports while establishing connections.
Network: Packet sniffing and DoS attacks such as Ping floods, ICMP attacks and other
routing related attacks are possible
Data Adaption: This layer is the intermediate between the IoT network and Internet in which
the un-encrypted data store will be tampered or sniffed
Physical cum data-link layer: This layer is affected by insecure protocols such as DHCP or
STP, MAC flooding or ARP poisoning and service disruption attacks.