TY - JOUR
T1 - Defining Intent-Based Service Management Automation for 6G Multi-Stakeholders Scenarios
AU - Alemany, Pol
AU - Munoz, Raul
AU - Cisneros, Josue Castaneda
AU - Karaca, Mehmet
AU - Porambage, Pawani
AU - Tran, Huy Q.
AU - Giardina, Pietro G.
AU - Tzanettis, Ioannis
AU - Sousa, Xose R.
AU - Valero, Jose Maria Jorquera
AU - Ojaghi, Behnam
AU - Vilalta, Ricard
AU - Rugeland, Patrik
AU - Boussard, Mathieu
AU - Landi, Giada
AU - Zafeiropoulos, Anastasios
AU - Rodriguez, Santiago
AU - Perez, Manuel Gil
AU - Barmpounakis, Sokratis
AU - Uusitalo, Mikko A.
AU - Lopez, Diego
AU - Kerboeuf, Sylvaine
PY - 2025
Y1 - 2025
N2 - This article aims to explore the requirements and challenges that Intent-Based Management (IBM) systems should look towards to deliver proper automation management in multi-stakeholder 6G scenarios. To do so, the evolution of the telecommunications actors is presented to identify how they will interact with the use of intents and what IBM systems must face to fulfil with the tenants expectations while interacting among other IBM domains (aggregation vs. federation models). In a second step, this article presents how the IBM systems functionalities should be organized (based on standards research and comparative) and a set of enablers using them to properly deliver the automation needed to accomplish the requests done by the tenants. On a third step, a set of End-to-End (E2E) intent-based services are described to illustrate how the different enablers (and the functionalities they use) may work to reach the E2E service goal. Finally, a set of experimental results related to how intent conflicts should be manage is presented, followed by the conclusions.
AB - This article aims to explore the requirements and challenges that Intent-Based Management (IBM) systems should look towards to deliver proper automation management in multi-stakeholder 6G scenarios. To do so, the evolution of the telecommunications actors is presented to identify how they will interact with the use of intents and what IBM systems must face to fulfil with the tenants expectations while interacting among other IBM domains (aggregation vs. federation models). In a second step, this article presents how the IBM systems functionalities should be organized (based on standards research and comparative) and a set of enablers using them to properly deliver the automation needed to accomplish the requests done by the tenants. On a third step, a set of End-to-End (E2E) intent-based services are described to illustrate how the different enablers (and the functionalities they use) may work to reach the E2E service goal. Finally, a set of experimental results related to how intent conflicts should be manage is presented, followed by the conclusions.
KW - 6G
KW - end-to-end services
KW - intent-based networks
KW - multi-stakeholder
UR - https://www.scopus.com/pages/publications/105001978432
U2 - 10.1109/OJCOMS.2025.3554250
DO - 10.1109/OJCOMS.2025.3554250
M3 - Article
AN - SCOPUS:105001978432
SN - 2644-125X
VL - 6
SP - 2373
EP - 2396
JO - IEEE Open Journal of the Communications Society
JF - IEEE Open Journal of the Communications Society
ER -