Abstract
Information-centric networking integrates by design a pull-based model which brings in advantages in terms of control as well as of in-network caching strategies. Currently, ICN main areas of action concern content distribution and IoT, both of which are environments that often require support for periodic and even-triggered data transmission. Such environments can benefit from push-based communication to achieve faster data forwarding. This paper provides an overview on the current push-based mechanisms that can be applied to information-centric paradigms, explaining the trade-off associated with the different approaches. Moreover, the paper provides design guidelines for integrating push communications in information-centric networking, having as example the application of this networking architecture in IoT environments.
Highlights
Information-centric networking (ICN) is being applied with success to content distribution in large-scale environments due to its capability to address data instead of hosts, and to natively support authenticated many-to-many communication
ICN pull-based communication models such as the ones supported by CCNx [12] and Named Data Networking (NDN) attain a two-way delay which is disruptive for situations where devices emit data periodically, or for situations where devices generate data in response to a trigger
While several ICN approaches have been developed, including CCN, NDN, NetInf [22], PURSUIT [23] there are still a number of challenges associated with ICN applicability to large-scale, resource-constrained and mobile heterogeneous scenarios, such as IoT scenarios
Summary
By design, the ICN publish/subscribe paradigm follows a pull-based communication approach, where consumers need to express interest to receive each data packet. Such a pull-based model may reduce performance in scenarios holding a large number of resource constrained, mobile devices, as occurs in IoT environments, due to the need to frequently broadcast Interest packets. This would require devices to be in reception mode all of the time, for instance, resulting in battery drain.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have