this is for holding javascript data
Nurzaman Ahmed edited But_consideration_of_technology_is__.tex
over 8 years ago
Commit id: 305d711b9d1a45d9b925beb2ee83961ad92771f2
deletions | additions
diff --git a/But_consideration_of_technology_is__.tex b/But_consideration_of_technology_is__.tex
index 3c451f2..0623132 100644
--- a/But_consideration_of_technology_is__.tex
+++ b/But_consideration_of_technology_is__.tex
...
\subsection{Components}
\subsubsection{Gateways}
Moving toward the “edge” of the IoT, we find the gateways, whose role is to interconnect the end devices to the main communication infrastructure of the system [6740844]. The gateway is hence required to provide protocol translation and functional mapping between the unconstrained protocols and their constrained counterparts, that is to say XML-EXI, HTTP-CoAP, IPv4/v6-6LoWPAN.
Note that while all these translations may be required in order to enable interoperability with IoT peripheral devices and control stations, it is not necessary to concentrate all of them in a single gateway. Rather, it is possible, and sometimes convenient, to distribute the translation tasks over different devices in the network. For example, a single HTTP-CoAP proxy can be deployed to support multiple 6LoWPAN border routers.
Gateway devices shall also provide the interconnection between unconstrained link layer technologies, mainly used in the core of the IoT network, and constrained technologies that, instead, provide connectivity among the IoT peripheral nodes.
