Development of Iot Broker Architecture Algorithm with Protocol Support for Multimodal Communication

Abstract

The IoT Integration Middleware (IoTIM) serves as an integration layer for newlinedifferent kinds of Sensors, Actuators, Devices, and Applications. It is responsible for newline(i) receiving data from the connected Devices, (ii) processing the received data, (iii) newlineproviding the received data to connected Applications, and (iv) controlling devices. A newlineDevice can communicate directly with the IoT Integration Middleware if it supports newlinean appropriate communication technology, such as a corresponding transport newlineprotocol, like CoAP, HTTP or MQTT. newlineServices offered can be used for communication, entertainment, sharing newlineknowledge and many other purposes. In addition to traditional devices (laptops, smart newlinephones, etc..), devices around us will soon be able to communicate with each other newlineCurrently, many studies are involved in developing solutions to solve the various newlineresearch challenges facing the IoT. Specifically, the development of new middleware newlinesolutions for the IoT is an active area of research. The proposed UniversalCom newlineGateway provides facility for CoAP, XMPP data communication via UniversalCom newlinemiddleware ucbroker . The Input registration process is executed for schema newlinemapping of the sending sensor s data. The SOAP architecture is used for both CoAP newlineand XMPP communication. Protocol specification uses the constructs [action], newline[destination], [message id], [reply endpoint], [address] format which can be easily newlinemapped with schema. The message scheduling is done by Request Validator Gateway newlineProxy Communication will check the priority of incoming request. Protocol newlineRegistration will be done to pass middleware requests. newline