loading page

Intent Negotiation Framework for Intent-driven Service Management
  • +1
  • Yogesh Sharma ,
  • Deval Bhamare ,
  • Andreas Kassler ,
  • Javid Taheri
Yogesh Sharma
Thompson Rivers University
Author Profile
Deval Bhamare
Author Profile
Andreas Kassler
Author Profile
Javid Taheri
Author Profile


To automate network operations and compute ser- vices, intent-driven service management (IDSM) is essential. It enables network users to express their service requirements in a declarative manner as intents. To fulfill the intents, closed control-loop operations perform required configurations and deployments without human intervention. Despite the fact that the intents are fulfilled automatically, conflicts may arise between users and service providers due to limited capabilities of service providers and user requirements specified as intents. This triggers IDSM system to initialize an intent negotiation process among conflicting actors. Intent negotiation involves generating one or more alternate intents based on the current state of the underlying physical/virtual resources, which are then presented to the intent creator for acceptance or rejection. In this way, the quality of services (QoS) can be improved significantly by maximizing the acceptance rate of service requests in the scenario of limited resources. However, intent negotiation sub-systems are still in their infancy. The available solutions are platform dependent which pose various challenges in their adoption to diverse platforms. The main focus of this work has been to draft a comprehensive and generic intent negotiation framework which can be used across diverse IDSM platforms. In this work, we have identified and defined various processes that are necessary for a comprehensive intent negotiation framework. A generic intent negotiation framework is then presented incorporating all the interactions among all the identified processes while conflicting actors engage in the intent negotiation, towards the fulfilment of the given service.
Jun 2023Published in IEEE Communications Magazine volume 61 issue 6 on pages 73-79. 10.1109/MCOM.001.2200504