IG1253E Using Intent in AN – Use Cases, Scenarios and Examples v1.0.0

Intents comprise the requirements, goals, and constraints in a simplified manner that is abstract from complex technical definitions and dependencies. To put it even simpler, intents are the “what”, not the “how”. The “how” is left to the “handler”, which we call the “Intent Management Function”.

We express these requirements with a common grammar or vocabulary that we call “TM Forum Intent Ontology”, or TIO for short. Autonomous systems can only adapt to requirements if they know them. So it’s very important that we can express requirements in a formal (machine-readable) and unambiguous vocabulary, i.e., an ontology.