Named data networking for IoT


1. What is a named data network for IoT

Source: of-named-data-networking.png & imgrefurl = https% 3A% 2F% 2Ffigure% 2FEntities-of-named-data-networking_fig1_327390170 & tbnid = E0ul-CvZu6QnzM & vet = 12ahU4KEwiC% 2FeNTities & QHVA & QHVA = 20HHVA & QHVA% = 20HU4KEwiC = 20HHVA & qhu6QnzM & vet = 12ahU4KEwiC = 20 2ahUKEwiC – HHnYvyAhUPHKYKHZx9B-AQMygAegUIARCaAQ

FinConDX 2021

The rise of the Internet of Things (IoT) advocated a new internet architecture because the IoT differs from the current internet architecture due to the resource constraints of the devices and the huge volumes of small data exchanged. Therefore, scientists and engineers have come up with Named Data Networking (NDN), a content-centric network that is more compatible with the requirements of IoT. The advantages of today’s device-centric IP solutions are undeniable: IP is a well-defined standard that enables communication between entities in different domains. However, on a larger scale such as in IoT with billions of interconnected devices, IP solutions face multiple challenges. Using IP addresses requires additional resolution systems to translate application-level requests into IP addresses as well as protocols to support mobility. Meanwhile, the novel Named Data Networking gives a name to each content / data and uses that name to retrieve any information. The nodes connected in the network specify what they are looking for without needing the expected location of the data of interest. Any authorized user can request data using a unique name of this self-authentication and self-identification object. In addition, the security of each packet is ensured by NDN at the time of its production and thus allows the caching of data at each node while maintaining the data security for the life of the package. These features make NDN a promising solution for the IoT ecosystem, where the same data can be requested by applications spanning multiple domains and billions of nodes communicate simultaneously.

2. Use and examples


NDN defines a simple model of communication with the exchange of only two packages types, interests, and data, which have application-specific and ordered content / data names. NDN carries the signature of the data editor and the authentication information in each data to guarantee the authenticity and integrity of the content.

Each NDN node is made up of three main components: a content store for temporary storage of incoming data packets, a routing table called the transmission information base (FIB) whose main purpose is to guide interests to data and a Pending Interest Table (PIT) which can be used to record transferred Interest which is not yet compatible with a returned Data packet. When an NDN node receives an interest, it searches its content store for a name prefix that matches the longest match. If such a name is found, the node returns the data to the original publisher of the interest. If, however, there is already a corresponding PIT entry, the last interest will be rejected because a previous equal request has already been submitted. If this new interest is unique, a new PIT entry is generated and, in the worst case, when a match cannot be located in the PIT, the data packet is dropped.


Research and development of NDN for IoT is still in its early stages, however, several viable applications have been proposed and one of the most notable is the NDN-based smart home architecture. In a smart home, a variety of sensors and actuators are used for multiple purposes, including energy management, security, and healthcare. Many smart home applications only involve two simple main operations of retrieving data and sending commands to actuators. Despite the simple characteristics of these actions, communication over IP can still be complex due to various communication technologies and resource constraints. By implementing the NDN architecture, users can retrieve data directly and instantly from a specific sensor, sending a packet of interest for information. In addition, the sensors can communicate with the home server and with the user simultaneously and the user can broadcast the same packet of interest and receive the data from the source closest to the range, rather than carrying the address. Server IP and packet when routing around the house to reach the server.

3. Conclusion

Named Data Networking is emerging as one of the promising future architectures of the Internet in general and the Internet of Things ecosystem in particular. Besides its potential as a viable solution for device interconnection, its innovative concepts, such as named content, network caching and also name-based routing, will be developed and implemented to address the challenges. challenges of the IoT in the years to come.

4. References

The post office Named data networking for IoT appeared first on Speranza.

*** This is a Syndicated Security Bloggers Network blog by Blog IoT – Speranza written by Allen. Read the original post on: