Intent-Driven Management Explained

Intent-driven management flips how networks are run: instead of telling the network how to do something step by step, you tell it what outcome you want, and it figures out the rest. This page explains what "intent" means in 3GPP, how it turns a goal into real configuration, and where it fits in the move toward self-running networks.

Status: Intent-driven management is normative in 3GPP (TS 28.312), introduced in Release 17 and expanded steadily through Releases 18–20. It is a key enabler for autonomous and 6G networks.

What "intent" means

An intent is a statement of the desired state of a network or service, given by a consumer (for example, an operator's management system) to a producer (a management function) — without saying how to achieve it. The system works out the "how" itself.

3GPP places intent at the top of a ladder of abstraction:

Rule — the most specific: "set this cell's transmit power to X."
Policy — conditional: "if coverage drops below a threshold, increase power."
Intent — outcome-based: "keep weak-signal coverage in this area under 5%."

That shift from "how" to "what" is the whole point — the operator states a goal, and the network determines the actions.

How a goal is expressed

An intent is structured so a machine can act on it. It contains one or more expectations, and each expectation has:

An object — what it applies to (a set of cells, a slice, a geographic area).
One or more targets — the measurable goals, each with a name (e.g. a throughput or coverage metric), a condition (greater than, less than, between), and a value or range.
A context — the scope and conditions (area, time, UE group, frequency).

So "ensure average uplink throughput above 10 Mbps for this user group in this area" becomes a precise, checkable target the system can pursue.

From intent to configuration

A handling function on the producer side does the translation:

The consumer creates the intent.
The producer acknowledges it and can run a feasibility check — is this even achievable right now?
It translates the targets into concrete actions — adjusting parameters, invoking self-organising-network functions, allocating resources — possibly breaking a big intent into sub-intents for different domains.
It executes those actions.
It monitors continuously against the targets and corrects course if fulfilment slips.

The intent lifecycle

An intent moves through clear states so both sides always know where it stands — roughly: received → evaluating → fulfilling → fulfilled, and it can become degraded (was met, no longer is), suspended, or terminated. A report is issued at each change, so the consumer can see the fulfilment status, any conflicts with other intents, and achieved values.

Later releases add richer behaviour: the system can explore what outcomes are achievable before committing, negotiate achievable target values when the exact ask isn't possible, use a utility function to trade off competing goals, and decompose and trace an intent into sub-intents.

Handling conflicts

Because many intents run at once, the producer detects conflicts — at the intent, expectation, or target level — and resolves them, often by priority, reporting back to the consumer whose intent was pre-empted.

Typical use cases

3GPP defines standardised intent use cases, including:

Coverage assurance — keep weak-signal ratio under a threshold in an area.
Capacity/throughput — assure user throughput for a group or area.
Radio network and service delivery — deploy cells or a slice to meet a goal.
Edge service support, energy saving, 5G core, and maintenance intents.

Why it matters

Intent is the vehicle for higher levels of network autonomy: the operator states the goal, and a closed control loop pursues it automatically. It is a cornerstone of the autonomous-network and 6G vision, where networks are too large and dynamic to configure by hand.

Reference points (3GPP)

TS 28.312 — intent-driven management services (the primary spec).
TS 28.100 — levels of autonomous network (how intent enables higher autonomy).
TS 28.567 — closed control loops (the autonomous execution mechanism).
TS 28.313 / TS 28.552 / TS 28.554 — SON functions and the KPIs used to check fulfilment.

In short

Intent-driven management lets you ask the network for an outcome and trust it to deliver — stating "what" instead of "how" — and it's the foundation 3GPP builds on for autonomous, self-running networks.