Abstract: Network management automation may use network intent (NI) which represents a network design and baseline configuration for that network or network devices with the ability to diagnose deviation from the baseline configuration. This may include automation of the diagnosis of repetitive problems and the enforcement of preventive measures across a network. This automation may be through an automation data table (ADT), which is an extended global data table for managing network assets and network intents associated with those network assets. ADT is a database for intents, supporting intent creation and replication, and can be used in the PDAS system.

Abstract: Problem Diagnosis Automation System (PDAS) automates the diagnosis of repetitive problems and the enforcement of preventive measures across a network. Automation assets across the network include Network Intent (NI) inside the no-code platform. A Network Intent Cluster (NIC) clones a NI across the network to create a group of NIs (member NIs) with the same design or logic. A subset of Member NIs can be executed according to user-defined conditions based on the member device, the member NI tags, or signature variables. A Triggered Automation Framework (TAF) matches the incoming API calls from a 3rd party system to current incidents and installs the automation (e.g., NI/NIC) to be triggered for each call. It may include: Integrated IT System defining the scope and data of the incoming API calls; Incident Type to match a call to an Incident; and Triggered Diagnosis to define what and how the NIC/NI is executed.