A Self-Optimizing QoS-Based Access for IoT Environments
Affiliation auteurs | !!!! Error affiliation !!!! |
Titre | A Self-Optimizing QoS-Based Access for IoT Environments |
Type de publication | Journal Article |
Year of Publication | 2021 |
Auteurs | Khalil A, Mbarek N, Togni O |
Journal | WIRELESS PERSONAL COMMUNICATIONS |
Volume | 120 |
Pagination | 2861-2886 |
Date Published | OCT |
Type of Article | Article |
ISSN | 0929-6212 |
Mots-clés | 15, 4, IEEE 802, Internet of things, MAPE-K, QBAIoT, QoS, Self-management |
Résumé | Nowadays, providing Internet of Things (IoT) environments with service level guarantee is a challenging task. Moreover, IoT services should be autonomous in order to minimize human intervention and thus to reduce the operational management cost of the corresponding big scale infrastructure. We describe in this paper a service level-based IoT architecture enabling the establishment of an IoT Service Level Agreement (iSLA) between an IoT Service Provider (IoT-SP) and an IoT Client (IoT-C). The proposed iSLA specifies the requirements of an IoT service, used in a specific application domain (e-health, smart cities, etc.), in terms of different measurable Quality of Service (QoS) parameters. In order to achieve this agreement, several QoS mechanisms are to be implemented within each layer of the IoT architecture. In this context, we propose an adaptation of the IEEE 802.15.4 slotted CSMA/CA mechanism to provide different IoT services with QoS guarantee. Our proposal called QBAIoT (QoS-based Access for IoT) creates different Contention Access Periods (CAP) according to different traffic types of the IoT environment. These CAPs are QoS-based and enable traffic differentiation. Thus, a QoS CAP is configured with several slots during which only IoT objects belonging to the same QoS class can send their data. Furthermore, we specify a self-management closed control loop in order to provide our IoT architecture with a self-optimizing capability concerning QoS CAPs slots allocation. This capability takes into account the actual usage of QoS CAPs as well as the characteristics of the corresponding traffic class. |
DOI | 10.1007/s11277-021-08589-8 |