|
| 1 | +cff-version: 1.2.0 |
| 2 | +message: "If you use this software, please cite it as below." |
| 3 | +title: RIOT - The friendly Operating System for the IoT |
| 4 | +url: https://www.riot-os.org/ |
| 5 | +preferred-citation: |
| 6 | + type: article |
| 7 | + authors: |
| 8 | + - family-names: Baccelli |
| 9 | + given-names: Emmanuel |
| 10 | + - family-names: Gündoğan |
| 11 | + given-names: Cenk |
| 12 | + - family-names: Hahm |
| 13 | + given-names: Oliver |
| 14 | + - family-names: Kietzmann |
| 15 | + given-names: Peter |
| 16 | + - family-names: Lenders |
| 17 | + given-names: Martine S. |
| 18 | + - family-names: Petersen |
| 19 | + given-names: Hauke |
| 20 | + - family-names: Schleiser |
| 21 | + given-names: Kaspar |
| 22 | + - family-names: Schmidt |
| 23 | + given-names: Thomas C. |
| 24 | + - family-names: Wählisch |
| 25 | + given-names: Matthias |
| 26 | + title: "RIOT: An Open Source Operating System for Low-End Embedded Devices in the IoT" |
| 27 | + url: https://www.riot-os.org/assets/pdfs/riot-ieeeiotjournal-2018.pdf |
| 28 | + journal: IEEE Internet of Things Journal |
| 29 | + scope: "If you use this software, we prefer that you cite our paper as below." |
| 30 | + publisher: |
| 31 | + - name: IEEE |
| 32 | + month: 3 |
| 33 | + year: 2018 |
| 34 | + volume: 5 |
| 35 | + issue: 6 |
| 36 | + pages: 4428-4440 |
| 37 | + doi: 10.1109/JIOT.2018.2815038 |
| 38 | + abstract: > |
| 39 | + As the Internet of Things (IoT) emerges, compact operating systems (OSs) are |
| 40 | + required on low-end devices to ease development and portability of IoT |
| 41 | + applications. RIOT is a prominent free and open source OS in this space. In |
| 42 | + this paper, we provide the first comprehensive overview of RIOT. We cover |
| 43 | + the key components of interest to potential developers and users: the |
| 44 | + kernel, hardware abstraction, and software modularity, both conceptually and |
| 45 | + in practice for various example configurations. We explain operational |
| 46 | + aspects like system boot-up, timers, power management, and the use of |
| 47 | + networking. Finally, the relevant APIs as exposed by the OS are discussed |
| 48 | + along with the larger ecosystem around RIOT, including development and open |
| 49 | + source community aspects. |
0 commit comments