IoT Chapter 3 Notes PDF

IOT chapter 3 notes Different steps in IOT design methodology: Explanation of each step: ### **1. Purpose & Requirements** The purpose and requirements phase defines the IoT system's goals and user needs, focusing on cost reduction, efficiency, and user convenience. It considers business objecti...

IOT chapter 3 notes Different steps in IOT design methodology: Explanation of each step: ### **1. Purpose & Requirements** The purpose and requirements phase defines the IoT system's goals and user needs, focusing on cost reduction, efficiency, and user convenience. It considers business objectives, stakeholder needs, and system constraints like budget and technical feasibility. Deliverables include a problem statement, system goals, and requirements. ### **2. Process Model Specification** This step defines use cases and system behavior, detailing user interactions, data collection, and workflows. It identifies processes like data processing and actuation. Deliverables include use case diagrams and process workflows. ### **3. Domain Model Specification** This phase identifies physical entities like sensors, virtual entities like cloud services, and resources/services in the system. It defines components, specifies hardware/software interfaces, and maps data sources. Deliverables include a domain model diagram. ### **4. Information Model Specification** This step defines how data is structured, stored, and processed. It outlines data types, attributes, and data flows while addressing metadata and security policies. Deliverables include information models like ERDs. ### **5. Service Specifications** Service specification defines system services like data collection, analysis, and actuation. It ensures interoperability by specifying APIs and communication endpoints. Deliverables include service descriptions and API documentation. ### **6. IoT Level Specification** This step determines the IoT system’s architecture, such as cloud-centric or edge-centric, and defines the communication hierarchy (D2D, D2C, or D2G). Deliverables include an IoT architecture diagram. ### **7. Functional View Specification** This phase maps the system into modules like sensing, data processing, and storage. It assigns responsibilities to each module and defines interactions. Deliverables include functional block diagrams. ### **8. Operational View Specification** The operational view defines system protocols, data storage, hosting, and deployment strategies. It specifies communication options like Wi-Fi, Zigbee, or LoRaWAN. Deliverables include operational design documents. ### **9. Device & Component Integration** This step integrates hardware and software components, including sensors, actuators, and communication modules. It tests system compatibility and ensures smooth interfacing. Deliverables include an integrated prototype. ### **10. Application Development** Application development involves creating user-facing apps, dashboards, and APIs. It ensures usability, scalability, and performance. Deliverables include fully developed applications ready for deployment. Q. Describe domain model of the home automation IOT systems.(w23) 1. User Domain The Human User represents individuals interacting with the system to monitor and control appliances. Roles include the Homeowner, who sets automation rules, monitors system statuses, and overrides commands, and the Guest User, who has limited access to certain controls. The Active Digital Artifact (App) acts as an interface between the user and the system, providing a way to monitor conditions like temperature and appliance statuses, and to execute commands such as turning appliances on or off. 2. Virtual Entity Domain This domain focuses on abstract representations of physical entities. The Virtual Entity: Room models a real room, tracking attributes like light levels or temperature. It serves as the context for controlling appliances. The Virtual Entity: Appliance represents devices like lights or fans, tracking their on/off states and enabling commands such as turning on lights when it gets dark. 3. Physical Entity Domain The Physical Entity: Room refers to the actual room, monitored by sensors for data like light intensity and occupancy. The Physical Entity: Appliance refers to real-world devices like lights or air conditioners, controlled by the system and responding to commands from their virtual counterparts. 4. Service Domain Services provide functionalities that link virtual and physical entities. The Lighting Service manages lights across rooms, while the Climate Control Service manages HVAC systems. Services allow the app to invoke actions (e.g., turning on lights) and receive notifications (e.g., motion detection alerts). 5. Resource Domain OnDevice Resources provide local processing and storage, such as a smart hub or microcontroller hosting automation logic. Network Resources represent cloud-based services for remote access and complex processing, like a cloud API for controlling the system outside the house. 6. Device Domain The Device Domain includes hardware that executes commands and collects data. Devices (Minicomputers) act as hosts for resources, running local rules and communicating with cloud services. Sensors like LDRs monitor light levels, while Actuators such as relays control appliances, executing commands like turning on lights when motion is detected. 7. Relationships in the Domain User ↔ App shows how the user interacts with the app to control the system. App ↔ Service describes how the app invokes services to perform actions or retrieve information. Service ↔ Virtual Entities connects services to virtual representations of rooms and appliances. Virtual Entities ↔ Physical Entities links virtual models to real-world objects. Device ↔ Sensors and Actuators shows how devices collect data and control appliances. Resources ↔ Devices indicates that resources hosted on devices manage logic and data processing. 8. Domain-Specific Use Cases Monitoring involves sensors sending data like light levels to virtual entities for decision- making. Control means sending commands to actuators via services, such as turning on lights. Automation Rules enable tasks like turning on the living room light when it’s dark and motion is detected, or turning off all appliances when the user leaves the house. Q. Describe process specification model of the home automation IOT systems.(s24,w22,s23). The above diagram shows the process specification model of home automation. There are two modes in which the home automation system will work: automatic mode and manual mode. In the automatic mode we use two sensors that are PIR sensor and LDR sensor. PIR sensor(Passive infrared sensor): This sensor is used to check the occupancy of the room. Occupancy means it will check whether the user is in the room or not. If the user is in the room then it will keep the Light ON until the user leaves the room. LDR sensor: This sensor is used to check the luminance of the room and decide whether to turn light ON or OFF. During the day when the there is sunlight in the room the sensor keeps the lights OFF. At night when the light level decreases the lights are turned on the the sensor. Both these sensors work together to ensure that the system functions properly with human intervention. These sensors also provide energy efficient system by keeping the lights OFF when not needed. In the manual mode of the system the user perform all the tasks manually. The user is the one who will decide when to turn ON the light and when to turn it OFF. Q. Describe information specification model of the home automation IOT systems. (w22,s24,s23) Certainly! Here's a more condensed version: 1. Virtual Entity: Room The Virtual Entity: Room represents a room in the home automation system, identified by a unique ID, like Room1. A key attribute is the Light-Level Attribute, which tracks the room’s light intensity. The attribute type is level, with possible states: High (bright room) and Low (dim room). This helps determine the room's brightness and can trigger automation, such as turning on lights when the light level is low. 2. Virtual Entity: Light Appliance The Virtual Entity: Light Appliance represents a light fixture in the system, identified by a unique ID, such as Light1. It is linked to a room via RoomID (e.g., Room1). The State Attribute tracks whether the light is On or Off, controlling the light's operational status. This attribute helps automate actions like turning the light on or off based on conditions like light levels. 3. Relationship Between Virtual Entities The Room and Light Appliance are connected through the RoomID, indicating the light's location. The room's lightLevel can influence the lightState of the appliance. For example, if lightLevel is Low, the light might be turned On, and if lightLevel is High, the light may be turned Off to save energy. 4. Home Automation Context This model links sensors, appliances, and automation rules. Sensors measure the room's light levels and update the lightLevel attribute. Automation rules can be set to control appliances based on these values. For example, when lightLevel is Low, the light is turned On, and when it's High, the light is turned Off. Q. Explain IOT level specification for home automation. 1. Local System The local system operates within the home environment, ensuring real-time control and functionality. App The app represents the user interface, such as a mobile or desktop application. It allows users to monitor the status of smart devices and send commands to control them, such as turning lights on or off or adjusting the thermostat. Communication is facilitated through RESTful APIs, ensuring smooth interaction between the user and the system. REST Services REST services act as an intermediary between the app and other components of the system. They accept user commands, fetch data from the database, and forward it to the app to provide real-time updates. REST ensures secure and structured data communication using its standard protocols. Database The database stores local system data such as device states, historical data, and user preferences or automation rules. It acts as a local backup, providing quick access to information without requiring constant cloud interaction. Controller Service The controller service is the central decision-making unit. It processes commands received from REST services and translates them into actionable instructions for devices. It also monitors device behavior, updates the database with changes in status, and executes automation rules, such as turning off all lights at 11 PM. Resource The resource provides a virtual abstraction of physical devices. It facilitates interaction between the controller service and devices while managing device-specific protocols to ensure compatibility with various hardware. Device Devices include the physical hardware, such as sensors and actuators, used in the home automation system. Sensors collect environmental data like temperature and motion, while actuators perform actions such as turning lights on/off or adjusting blinds. Examples include smart thermostats, motion sensors, and smart plugs. 2. Cloud System The cloud system extends the local system by providing advanced analytics, remote access, and centralized data storage. Monitoring Node The monitoring node represents the cloud-based component that handles data storage and analysis. It processes data from the local system to generate insights, such as energy usage patterns or predictive maintenance. It also stores historical data for long-term analysis and enables users to access and control their devices remotely through the app. Q. explain this functional specification model with respect to home automation. 1. Device Layer The Device Layer forms the foundation where physical devices interact with the environment. Sensors monitor factors like temperature, humidity, and motion, such as temperature sensors for climate control or motion sensors for security. Actuators carry out actions based on sensor data, like adjusting the thermostat or controlling motorized blinds. Computing Devices process data locally, such as smart hubs (e.g., Amazon Echo, Google Nest) that integrate and control multiple devices. 2. Communication Layer The Communication Layer ensures smooth data exchange between devices. Communication APIs enable device interaction across platforms, like mobile apps controlling smart lights. Communication Protocols define how devices communicate, with examples such as Zigbee and Z-Wave for low-power devices, Wi-Fi for internet connection, and MQTT for lightweight IoT communication. 3. Services Layer The Services Layer provides the functionality needed to deliver value to users. Native Services run on devices or hubs, like a smart thermostat adjusting temperature based on schedules. Web Services are cloud-based, enhancing device capabilities, such as remote control via a mobile app or integration with external services like weather forecasts to optimize climate control. 4. Management Layer The Management Layer handles system operations. Application Management ensures smooth app operation and updates, like managing firmware for security or new features. Database Management stores data like motion sensor logs or historical temperature data for analysis. Device Management covers device setup, configuration, and monitoring, such as pairing new smart bulbs or locks. 5. Security Layer The Security Layer protects against unauthorized access. Authentication verifies user or device identity, like password-protected apps or biometric access for smart locks. Authorization defines allowed actions, such as a guest account with limited device control (e.g., controlling lights but not unlocking doors). 6. Application Layer The Application Layer is the user-facing interface. A Web Application allows users to monitor and control their system through a browser, like viewing security cameras or controlling appliances. The Application Server processes user commands, like turning on lights. A Database Server stores user preferences, device configurations, and logs, such as tracking door lock activities.