Topic 3 - Intent-driven Closed-Loop automation

From ZSM Wiki
Revision as of 10:32, 19 November 2021 by Vreck (talk | contribs) (Description)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Intent-driven operations allow the introduction of self-adapting and self-monitoring capabilities in the operations software stack. This is a key ingredient for the transition from automation into autonomous, zero-touch networks. Closed loops are key enablers for automation that have been successfully used in many industries for long, and more recently for computing and networking applications. Closed-loop automation (CLA) can self-monitor, self-evaluate and self-heal and fulfill all specified requirements. The combination of intent and closed-loop automation prides a powerful tool to capture a consumers needs and provide an intelligent feedback loop.


ACTIVE (Approved at ZSM#17, Oct 2021)

Points to prove/refute

What aspects of automation were used to support the PoC, which means were used, and how did it enrich the PoC?

Criteria of success

Document how the scenarios, management solutions or management interfaces have been implemented.

Technical information to be provided by the PoC Team

• Scenario, management solution or management interface description

• High-level PoC architecture

• Specifics on the issues faced

• Specifics on the solutions provided

• Specifics on the lessons learnt

Template for the PoC Feedback Contribution

No specific template. POC Teams are expected to submit a Technical Report covering the points mentioned above.

Concerned WIs

  • ZSM-009-1 “Closed-Loop Automation; Part 1: Enablers”
  • ZSM-009-2 “Closed-Loop Automation; Part 2: Solutions for automation of E2E service and network management use cases”
  • ZSM-009-3 “Closed-Loop Automation; Part 3: Advanced topics”
  • ZSM-011 “Intent-driven autonomous networks; Generic aspects”