Posts

Recourse Management of IOT

Image
 HOME             UNIT 1          UNIT 2    Recourse Management of IOT Why Resource Allocation is important for IoT?   Highly efficient, maintained and cost-benefit network ensure the Quality of Service (QoS) standards. IoT architecture has various resources connected with the network. The resource allocation is an important aspect for QoS standards be- cause of efficient and effective allocation of resources in the IoT network. Re- source allocation is also responsible for high standard of security because in IoT architecture the data is divided in many data streams gathered from different sensors and different types of services are provided by the networked devices. The IoT networked resources consists computing elements, storage and energy. Efficient Cloud resource allocation helps IoT networked devices to utilize these re- sources in an efficient and cost-effective way to improve system performance and productivity. IoT devices and resources are heterogeneous and gl

ZigBee

Image
   HOME             UNIT 1          UNIT 2   ZigBee  ZigBee is a Personal Area Network task group with low rate task group 4. It is a technology of home networking. ZigBee is a technological standard created for controlling and sensing the network. As we know that ZigBee is the Personal Area Network of task group 4 so it is based on IEEE 802.15.4 and is created by Zigbee Alliance.   ZigBee is an open, global, packet-based protocol designed to provide an easy-to-use architecture for secure, reliable, low power wireless networks. Flow or process control equipment can be place anywhere and still communicate with the rest of the system. It can also be moved, since the network doesn’t care about the physical location of a sensor, pump or valve. IEEE802.15.4 developed the PHY and MAC layer whereas, the ZigBee takes care of  upper higher layers. ZigBee is a standard that addresses the need for very low-cost implementation of Low power devices with Low data rates for short-range wireless commu

Modbus

Image
    HOME             UNIT 1           UNIT 2   Modbus Protocol Modbus is a data communication protocol that is based on a  request-response model. Previously  referred to as a master-slave protocol, the Modbus organization replaced the terms  master  and  slave  with  server  and  client  in 2020. Modbus is used for transmitting information between devices that are connected to buses or networks over serial lines or Ethernet and, increasingly, using wireless. Modbus is the most widely used network protocol in the industrial manufacturing sector. The  most common use case is the communication between a human-machine interface (HMI) or supervisory control and data acquisition (SCADA) system and a sensor, programmable logic controller (PLC), or programmable automation controller (PAC).  It provides a hardware-agnostic, cost-effective way to enable the interoperability of disparate automation equipment. Modbus is popular because it is open source, simple to use, and used everywhere, making

BACnet

Image
   HOME             UNIT 1           UNIT 2   BACnet is a communications protocol that is typically used by building management systems or process controllers to connect, monitor and control process values. BACnet can be used to connect to assets and allows multiple devices to initiate conversation and share data and information. BACnet can be used to control HVAC systems,  BMS systems  and other devices as well as allow them to to connect to graphical interfaces for the end user.  BACnet is both an international (ISO) and ANSI standard for interoperability between cooperating building automation devices. The protocol defines a set of rules and standards, such as the structure of messages or network addressing, and more specifically, it defines what kind of information can be exchanged.  BACnet provides live real time data for all zones connected to the BACnet network. For example, a facility manager can see if the boiler is running, or if an air-conditioner is cooling the building. Th

KNX Protocol

Image
 HOME             UNIT 1       UNIT 2    KNX Protocol Download What is KNX? What are its applications? Whats Special about it? Lets see: KNX is a network standard, basically OSI-based network communications protocol which is extensively designed and developed for building/home automation. KNX is an abbreviation for the word Konnex KNX is based on three technologies: EIB (European Installation Bus), EHS (European Home Systems Protocol) and BatiBUS. The KNX is not constrained by hardware compatibility, a KNX device could be controlled by anything from an 8-bit microcontroller to a PC, based on the level of implementation and application. Communications that support KNX: Twisted pair (Most commonly Implemented, Avg. bit rate: 9.6Kbits/sec) Radio frequency Infrared Power line IP/Ethernet KNX is used in residential and commercial building automation for HVAC, lighting, security, remote access, blind and shutter control, visualization, and energy management. KNX Model Here is how KNX provide

COMPaaS Middleware

Image
   HOME             UNIT 1       UNIT 2   COMPaaS Middleware COMPaaS (Cooperative Middleware Platform as a Service) is an IoT middleware system [3] that has been tailored to support the 5G technology integration. Basically, the goals of the COMPaaS can be summarized as follow: ∙ Abstraction of the integration and interoperation between applications and physical devices through the provision of hierarchical system services according to device profiles (i.e., a set of functional characteristics describing each physical device). ∙ Abstraction of the collection and management of data provided by physical devices through the provision of application-level services. ∙ Provision of high-level services to facilitate the development and integration of IoT applications. ∙ Provision of a software architecture based on IoT/M2M and WoT (Web of Things) standards.   Fig. 5 COMPaaS architecture COMPaaS architecture is based on SOA approach [4] and is composed of two main systems according to F

Perspectives and a Middleware Approach Toward 5G

Image
   HOME             UNIT 1       UNIT 2   Perspectives and a Middleware Approach Toward 5G According to [62], novel middleware architecture approaches toward 5G will not suffer major changes compared to what we have today in terms of SOA-based IoT middleware systems, and hence, the core of the architecture shown in Fig. 3 probably will be maintained. However, as mentioned in Sect. 3, IoT middleware systems will have to support the requirements imposed by 5G which will result in specific changes to allow the applications requirements demanded by 5G. Figure 4 illustrates a possible system architecture for 5G-based IoT Middleware with two application examples: (a) a “Healthcare Monitoring application” oriented to mission-critical services in a hospital (i.e., a group of medical devices and sensors for patients monitoring that continuously route data through redundant networks to guar- antee delivery of priority data), and (b) a non-critical example focused on “Social Networks” as WhatsApp