introduction of a gateway entity within the context of IoT nodes can be
deployed by the thousands or even millions in support of a single application.
Thus, having self-management Fault, Configuration, Accounting, Performance and
Security (FCAPS) capabilities is a must1,2. The communication over long
distances between different systems, a range of communication protocols are
involved in IoT processes such as Wi-Fi, Bluetooth, GPRS, 3G, LTE, ZigBee
networking protocol for very low-power environments, Z-Wave home automation
communication protocol, Near Field Communication or NFC which is an ensemble of
protocols that allow electronic devices to establish radio communication either
by touching them together or by bringing them into proximity, and many other
forms of data connectivity 3.
IoT devices can be classified as two major categories first one is
resource-constrained and resource-rich devices. Most of IoT applications are
low-rate but the large number of IoT devices participating on a single
application needed gate way protocols. We believe that there is a re-programmability
of the IoT gateway through a rule-based language can put the gateway in a
unique position to offer smart autonomic management, data aggregation or flow
aggregation, and protocol adaptation services.
There is a huge IoT load among the gateways it become multiple gateways
it required unique solution.
needs an efficient solution for protocol conversion, it required a
protocol-friendly mechanism inside the Protocol Translator that can increase
the conversion speed. The key point of this mechanism is a protocol Name-Value
index table of data which is carried in the optional headers of the different
application protocols. In TCP/IP protocol suite contains at different levels
different application protocols, some of the important protocols are CoAP, REST, MQTTM, MQTT-SN, AMQP. When a
packet reach at the gateway, the Protocol Translator examines the optional
header. If it determines the index table there, then it grabs the data
immediately from the payload it place the packets in destination protocol. In
index table is stored as on optional header,
application protocols may not use the index tables. In such cases, the
conversion is done in the conventional form and consequently it takes span of
Figure 5: (a) Optional header of the application protocol and Index table (b) The conversion
mechanism inside the gateway.
In Figure 5, In
optional header there are various
application protocol formats that assigned index number in index table. In index table where
a packet consisting of Name-Value pairs suppose for example x-97, y-99 etc. they needed to be converted in gate way from a
source protocol to a desired protocol in the protocol translator format. The data is stored
in a linear structure inside the payload of each packet.
The analysis of
protocol translator has been implemented XMPP, in which data are stored in XML
tags. In application layer format, it need O(n/2)
operations are required to find a data item in the payload before inserting it into the
desired protocol. There are O(n2) operations are
required in name-value pairs data inside packets. The conversion of XMPP takes
the if the position of each Name-value
item is available then the conversion time will be reduced to O(n).
this paper outlined the vision of Big Data Analytics, Fog and Cloud computing
their role in IoT and future of IoT. The layered architecture of IoT system
performed by the IoT framework and IoT elements. The IoT architecture of this
massive infrastructure has been defined, store and network devices. the
simulation of protocol translator provided by application layer in IoT is
defined. In future there is scope to investigate new Big data analytics
platform, Fog and Cloud computing platform of IoT, deliver a portfolio of new
services in IoT and develop better and
services of IoT.