Experimental Implementation of TinyIPFIX Protocol for Arduino and Raspberry Pi Platform

Petija, Rastislav; Glevanak, M.; Kucan, M.; Fecil'ak, Peter; Jakab, F.

doi:10.1109/iceta51985.2020.9379188

Cited by 1 publication

(2 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…TinyIPFIX [8] has less overhead than IPFIX due to the introduction of (1) template and data messages, similar to IPFIX as well as (2) in-network aggregation [12]. There are several implementations of TinyIPFIX [8,13,14] provided in the literature. Ref.…”

Section: Tinyipfixmentioning

confidence: 99%

“…Ref. [14] provides a Python-based implementation of TinyIPFIX for the Raspberry PI [17] platform and C++ implementation for ESP32 [3] devices implemented in the Arduino integrated development environment (IDE) [18]. However, the low-level implementation of a custom protocol is time-consuming due to difficulties introduced by low-level programming languages.…”

Section: Tinyipfixmentioning

confidence: 99%

See 1 more Smart Citation

Python-Based TinyIPFIX in Wireless Sensor Networks

2022

View full text Add to dashboard Cite

While wireless sensor networks (WSN) offer potential, their limited programmability and energy limitations determine operational challenges. Thus, a TinyIPFIX-based system was designed such that this application layer protocol is now used to exchange data in WSNs efficiently. The new prototype is based on the Espressif ESP32-WROOM-32D Internet-of-Things (IoT) platform, which is becoming famous, as it is inexpensive but powerful compared to older generations of IoT devices. The system implementation is provided in the programming language MicroPython, which provides a simple and efficient implementation, compared to a lower-level programming language. Therefore, this approach focuses on value creation rather than platform-specific implementation difficulties. The system is evaluated in smart home use cases and displays valuable overhead, reliability, and power efficiency. TinyIPFIX outperforms the data overhead of the type–length–value (TLV) paradigm by a factor of 7% when a TinyIPFIX data message carries only two records, and one TinyIPFIX template message is sent per three TinyIPFIX data messages. A further decrease in overhead is observed when the number of data records per message and the number of TinyIPFIX data messages sent per one TinyIPFIX template message increase to larger values. The message delivery between end devices and the application server resides at a very high level, close to 100%, when the transmission reliability is secured with acknowledgments and retransmissions. The energy efficiency resides at the limited level, as the experienced deep sleep power consumption of the ESP32 device resides at the milliwatt level.

show abstract