Information-centric Networking (ICN) is an emerging Internet architecture that offers promising features, such as in-network caching and named data addressing, to support the edge computing paradigm, in particular Internet-of-Things (IoT) applications. ICN can benefit from Complex Event Processing (CEP), which is an in-network processing paradigm to specify and perform efficient query operations on data streams. However, integrating CEP into ICN is a challenging task due to the following reasons: (1) typical ICN architectures do not provide support for forwarding and processing continuous data streams; (2) IoT applications often need short response times and require robust event detection, which both are hard to accomplish using existing CEP systems. In this article, we present a novel network architecture, called INetCEP, for efficient CEP-based in-network processing as part of ICN. INetCEP enables efficient data processing in ICN by means of (1) a unified communication model that supports continuous data streams, (2) a meta query language for CEP to specify data processing operations in the data plane, and (3) query processing algorithms to resolve the specified operations. Our experimental results for two IoT use cases and datasets show that INetCEP offers very short response times of up to 73 {\mu}s under high workload and is more than 15X faster in terms of forwarding events than the state-of-the-art CEP system Flink. Furthermore, the delivery and processing of complex queries is around 32X faster than Flink and more than 100X faster than a naive pull-based reference approach, while maintaining 100% accuracy.
翻译:以信息为中心的网络(ICN)是一个新兴的互联网结构,它提供了令人充满希望的特征,例如网络内缓存和命名的数据处理,以支持边际计算模式,特别是TH(IoT)应用程序。ICN可以受益于复杂事件处理(CEP),这是一个网络内处理模式,可以对数据流进行具体化和高效的查询操作。然而,将CEP纳入ICN是一项具有挑战性的任务,原因如下:(1) 典型ICN架构不支持更快速的传输和处理连续数据流;(2) IoT应用程序往往需要较短的反应时间,需要强有力的事件探测,而这两者都很难利用现有的CEP系统进行边际计算。在本篇文章中,我们提出了一个新的网络结构,称为INetCEP(CEP),作为ICN的一部分,高效的CEP(CEP)网络内部处理。INet CEP(CEP)通过(1) 支持连续数据流的统一通信模式,(2) CEP为基于数据流的数据处理操作提供一种元查询语言,维护数据平面上的链接,以及(3) 查询算算算,解决规定的操作的短期操作,两者都难以完成。在IOX(ITOX)中,在100x(ICT)的交付中,在100个案例和数据转发中,在超过Revild(lex)中,在100次的交付中,在100次的交付中,在15次的交付中,在超过R)中,在15次中,在提供较快中,在超过R)中提供高的交付的个案内,在100次中,在提供比快的交付的个案内,在15次中提供的实验结果中提供比为快。