# ndInIoT-FC: IoT Devices as First-Class Traffic in Name Data Networks
## 2 Related Work
However, its focus is on the orchestration of services where the scale is much smaller than IoT environment where thousands of sensors are expected. This difference in scale is perceived in the proposed solution, which does not use pub-sub strategies to make ICN as a whole more efficient. Our solution aims precisely to meet this scale. In [17] the authors discuss the impact that the receipt of considerable Interest packets by a specific NDN node can have in devices with limited PIT sizes and, present a fuzzy-based PIT-sharing algorithm addressed at solving these concerns. The work proposed makes an effort to identify an optimal node to serve as a sharing node, which can house the interest requests of several neighboring nodes and forward data accordingly, presenting improvements in account to both content delivery times and cache hit ratios, promoting the need for PIT size efficient solutions in NDN. However, the authors focus on a system supported by caching, not considering scenarios in which data is for immediate consumption, as is common in IoT environments. In [18], the authors present a sensor as a service platform to host live content streams from a diverse set of devices. They propose a data dissemination layer that uses a publication/subscription overlay based on the ICN paradigm. They detail the communication between publishers and subscribers with the centralized broker and show two examples of data delivery on their platform, publishing data from drone events and publishing data from traffic sensors. However, the results are few, and there is no discussion about them. For example, they do not show how the number of Interest packets decreases. The work in [19] proposed HoP-and-Pull (HoPP), an interesting publish-subscribe scheme for typical IoT scenarios targeting IoT networks with hundreds of resource constrained devices at intermittent connectivity. The strategy limits the Forwarding Information Base (FIB) tables to a minimum and naturally supports mobility, temporary network partitioning, data aggregation and near real time reactivity. [PERSON] et al. [20] presented a prototype of an integrated framework, dubbed NDNoT, to support IoT over NDN and provides services such as auto configuration, service discovery, data-centric security, content delivery, and other needs of IoT application developers. However, in both works, the authors do not discuss the performance of the proposed solution. The work in [21] proposed an IoT architecture and implementation details for devices and service networking, communication model, management, and naming. For each model they propose mechanisms supporting node mobility, hand-off, packet design, and push and pull data services without changing NDN data exchange model. The evaluation is done using ambient assisted living applications. The authors argue that their strategies based on semi-persistent interest, achieve lower control overhead and the losses related to mobility are kept at a minimum. However, a new table entity was introduced at each network node to handle subscription which essentially deviates from the native NDN design and can produce bottlenecks in memory limited devices. Finally, in [22] the authors discuss an IoT pub-sub architecture for 5G networks. They identify the main research challenges and possible solutions for scaling a pub-sub architecture to IoT applications on 5G networks. The main focus of the work is the distribution of brokers as a solution to address scale of this environment. They discuss a solution that use MQTT+ over an ICN-based architecture (POINT [23]). However, they do not present any implementation involving NDN or results about the proposed solution. Our architecture improves the coupling between the ICN paradigm and IoT devices by making a better use of persistent Interests and a finer subscription management of IoT-related subscriptions, while focusing on the common IoT circumstance of data meant for immediate consumption where caching policies are found lacking.