Ingateway entity within the context of IoT nodes can be deployed by the thousandsor even millions in support of a single application. Thus, havingself-management Fault, Configuration, Accounting, Performance and Security(FCAPS) capabilities is a must1,2. In IoT process the communication over longdistances between different systems, a range of communication protocols areinvolved in such as Wi-Fi, Bluetooth, GPRS, 3G, LTE, ZigBee, Z-Wave, homeautomation communication protocol, Near Field Communication (NFC) which is anensemble of protocols that allow electronic devices to establish radiocommunication either by touching them together or by bringing them into proximityand many other forms of data connectivity 3. TheIoT devices can be classified as two major categories first one isresource-constrained and resource-rich devices.
Most of IoT applications arelow-rate but the large number of IoT devices participating on a singleapplication needed gate way protocols. We believe that there is a re-programmabilityof the IoT gateway through a rule-based language can put the gateway in aunique position to offer smart autonomic management, data aggregation or flowaggregation, and protocol adaptation services. There is a huge IoT load among the gateways it become multiple gatewaysit required unique solution. Itneeds an efficient solution for protocol conversion, it required aprotocol-friendly mechanism inside the Protocol Translator that can increasethe conversion speed. The key point of this mechanism is a protocol Name-Valueindex table of data which is carried in the optional headers of the differentapplication protocols. In TCP/IP protocol suite contains at different levelsdifferent application protocols, some of the important protocols are CoAP, REST, MQTTM, MQTT-SN, AMQP. When apacket reach at the gateway, the Protocol Translator examines the optionalheader.
If it determines the index table there, then it grabs the dataimmediately from the payload it place the packets in destination protocol. Inindex table is stored as on optional header, application protocols may not use the index tables. In such cases, theconversion is done in the conventional form and consequently it takes span oftime.Figure 5: (a) Optional header of the application protocol and Index table (b) The conversionmechanism inside the gateway. In Figure 5, Inoptional header there are variousapplication protocol formats that assigned index number in index table. In index table wherea packet consisting of Name-Value pairs suppose for example x-97, y-99 etc.
they needed to be converted in gate way from asource protocol to a desired protocol in the protocol translator format. The data is storedin a linear structure inside the payload of each packet.The analysis of protocol translator has been implementedXMPP, in which data are stored in XML tags. In application layer format, it needO(n/2) operations are required to find a data item in the payload beforeinserting it into the desired protocol. There are O(n2) operations arerequired in name-value pairs data inside packets. The conversion of XMPP takesthe if the position of each Name-value item is available then the conversion time will be reduced to O(n).