ETSI TS 128 312 V17.8.0 (2025-01)

LTE; 5G; Management and orchestration; Intent driven management services for mobile networks (3GPP TS 28.312 version 17.8.0 Release 17)

RTS/TSGS-0528312vh80

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 30-Jan-2025

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
5G;
Management and orchestration;
Intent driven management services for mobile networks
(3GPP TS 28.312 version 17.8.0 Release 17)


3GPP TS 28.312 version 17.8.0 Release 17 1 ETSI TS 128 312 V17.8.0 (2025-01)

Reference
RTS/TSGS-0528312vh80
Keywords
5G,LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2025.
All rights reserved.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 2 ETSI TS 128 312 V17.8.0 (2025-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 3 ETSI TS 128 312 V17.8.0 (2025-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 6
1 Scope . 7
2 References . 7
3 Definitions of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 8
4 Concepts and Background . 8
4.1 Intent concept . 8
4.1.1 Introduction. 8
4.1.2 Intent categorizes based on user types . 8
4.1.3 Intent expectations for different types of management needs . 9
4.2 Intent driven management . 10
4.2.1 Support for intent driven management. 10
4.2.2 Intent driven MnS . 10
4.2.3 Intent translation . 11
4.3 Intent driven closed-loop . 12
4.4 Relation between rule, policy and intent . 12
4.5 General concept of Intent Content . 13
4.5.1 Intent Expectation . 13
4.5.2 Expectation Targets . 13
4.5.3 Expectation Objects . 14
4.5.4 Context . 14
5 Specification Level Requirements . 15
5.1 Use cases . 15
5.1.1 Intent containing an expectation for delivering radio network . 15
5.1.1.1 Introduction . 15
5.1.1.2 Requirements . 15
5.1.2 Intent containing an expectation for delivering a radio service . 15
5.1.2.1 Introduction . 15
5.1.2.2 Requirements . 16
5.1.3 Intent containing an expectation for delivering a service at the edge . 16
5.1.3.1 Introduction . 16
5.1.3.2 Requirements . 16
5.1.4 Intent containing an expectation on coverage performance to be assured . 16
5.1.4.1 Introduction . 16
5.1.4.2 Requirements . 16
5.1.5 Intent containing an expectation on RAN UE throughput performance to be assured . 17
5.1.5.1 Introduction . 17
5.1.5.2 Requirements . 17
5.2 Generic requirements for intent driven MnS . 17
6 Stage 2 definition for Intent Driven Management . 18
6.1 Management operation for Intent (MnS component type A) . 18
6.2 Information model definition for Intent (MnS component typeB) . 18
6.2.1 Generic Information model definition . 18
6.2.1.1 Class diagram . 18
6.2.1.1.1 Relationship . 18
6.2.1.1.2 Inheritance . 19
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 4 ETSI TS 128 312 V17.8.0 (2025-01)
6.2.1.2 Class definition . 19
6.2.1.2.1 Intent <> . 19
6.2.1.2.1.4 Notifications. 19
6.2.1.3 DataType definition . 20
6.2.1.3.1 IntentExpectation <> . 20
6.2.1.3.1.4 Notifications. 20
6.2.1.3.2 ExpectationObject <> . 20
6.2.1.3.3 ExpectationTarget <> . 21
6.2.1.3.3.4 Notifications. 21
6.2.1.3.4 Context <> . 21
6.2.1.3.5 FulfilmentInfo << dataType >> . 22
6.2.1.3.5.4 Notifications. 23
6.2.1.4 Attribute definition . 23
6.2.1.5 Common notifications . 26
6.2.1.5.1 Configuration notifications . 26
6.2.2 Scenario specific IntentExpectation definition . 27
6.2.2.1 Scenario specific IntentExpectation definition . 27
6.2.2.1.1 Radio Network Expectation . 27
6.2.2.1.2 Edge Service Support Expectation . 28
6.2.2.2 Attribute definition . 29
6.3 Procedures for intent management . 34
6.3.1 Introduction. 34
6.3.2 Create an intent . 34
6.3.3 Modify an intent . 35
6.3.4 Delete an intent . 37
6.3.5 Query an intent . 37
7 Stage 3 definition for Intent Driven Management . 38
7.1 RESTful HTTP-based solution set . 38
7.2 OpenAPI specification . 38
7.2.1 OpenAPI document "TS28532_ProvMnS.yaml" . 38
7.2.2 OpenAPI document "TS28312_IntentNrm.yaml" . 38
#7.2.3 OpenAPI document "TS28312_IntentExpectations.yaml" . 41
8 Guidelines for using scenario specific intent expectation for intent driven use cases. 49
Annex A (informative): PlantUML source code . 50
A.1 Procedures for intent management . 50
A.1.1 Create an intent . 50
A.1.2 Modify an intent . 50
A.1.3 Delete an intent . 51
A.1.4 Query an intent . 51
A.2 Information model definition for intent . 51
A.2.1 Relationship UML diagram for intent (figure 6.2.1.1.2-1) . 51
Annex B (informative): Intent Life Cycle Management . 53
B.1 Intent Life Cycle Management . 53
Annex C(informative): Mapping the 3GPP and the TM Forum intentExpectation Models . 55
Annex D (informative): Change history . 56
History . 58

ETSI
3GPP TS 28.312 version 17.8.0 Release 17 5 ETSI TS 128 312 V17.8.0 (2025-01)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 6 ETSI TS 128 312 V17.8.0 (2025-01)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
Introduction
The current 5G networks brings more operational complexities, and the telecom system need to be able to adapt their
operation to the business objectives of the operator as well as expectations of customer, which is driving customer to
shift the focus from "how" to "what". An intent driven system will be able to learn the behaviour of networks and
services and allows a customer to provide the desired state, without detailed knowledge of how to get to the desired
state. Thus, the intent driven management is introduced to reduce the complexity of management without getting into
the intricate detail of the underlying network resources.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 7 ETSI TS 128 312 V17.8.0 (2025-01)
1 Scope
The present document specifies concept, use cases, requirements and solutions for the intent driven management for
service or network management.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 28.531: "Management and orchestration; Provisioning".
[3] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[4] 3GPP TS 28.530: "Management and orchestration; Concept, use cases and requirements".
[5] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2
and stage 3".
[6] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM);
Integration Reference Point (IRP); Information Service (IS)".
[7] TM Forum IG1253A: "Intent Common Model v1.1.0".
[8] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception".
[9] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management".
[10] 3GPP TS 28.658: "Telecommunications management; Evolved Universal Terrestrial Radio Access
Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP):
Information Service (IS)".
3 Definitions of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term
defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
intent: expectations including requirements, goals and constraints given to a 3GPP system, without specifying how to
achieve them
3.2 Symbols
Void.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 8 ETSI TS 128 312 V17.8.0 (2025-01)
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
4 Concepts and Background
4.1 Intent concept
4.1.1 Introduction
An intent specifies the expectations including requirements, goals and constraints for a specific service or network
management workflow. In short, an intent is a statement towards a desired/wanted state of a system. The intent may
provide information on particular objective and possibly some related details. Following are some general concepts for
intent:
- An intent is typically understandable by humans, and also needs to be interpreted by the machine without any
ambiguity.
- An intent focuses more on describing the "What" needs to be achieved but less on "How" that outcomes should
be achieved, The intent expresses the metrics that need to be achieved and not how to achieve them. This not
only relieves the burden of the consumer knowing implementation details but also leaves room to allow the
producer to explore alternative options and find optimal solutions. Intent describes the properties that allows a
satisfactory outcome.
- The expectations expressed by an intent is agnostic to the underlying system implementation, technology and
infrastructure. Area can be used as managed object in the expectations expressed by an intent to achieve system
implementation, technology and infrastructure agnostic.

Figure 4.1.1-1
- An intent needs to be quantifiable from network data so that the fulfilment result can be measured and evaluated.
Intent can be categorized based on different user types or different management scenario types.
4.1.2 Intent categorizes based on user types
Based on roles related to 5G networks and network slicing management defined in clause 4.8 in 3GPP TS 28.530 [4],
different kinds of intents are applicable for different kinds of standardized reference interfaces.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 9 ETSI TS 128 312 V17.8.0 (2025-01)

Figure 4.1.2-1: High-level model of different kind of intents expressed by different roles
- Intent from Communication Service Customer (Intent-CSC): Intent from Communication Service Customer
enables Communication Service Customer (CSC) to express which properties of a communication service the
CSC may request from CSP without knowing how to do the detailed management for communication service.
For example, Intent-CSC can be 'Enable a V2X communication service for a group of vehicles in certain time'.
- Intent from Communication Service Provider (Intent-CSP): Intent from Communication Service Provider
enables Communication Service Provider (CSP) to express an intent about what CSP would like to do for
network without knowing how to do the detailed management for network. For example, Intent-CSP can be
'Provide a network service supporting V2X communications for highway-417 to support 500 vehicles
simultaneously'.
- Intent from Network Operator (Intent-NOP): Intent from Network Operator enables Network Operator
(NOP) to provide what NOP would like to do for group of network elements (i.e. subnetwork) management and
control without knowing how to do the detailed management for the network elements. For example, Intent-NOP
can be 'Provide a radio network service to satisfy the specified coverage requirements and UE throughput
requirement in certain area'.
4.1.3 Intent expectations for different types of management needs
Intent expectations for different types of management needs:
- Intent expectation for delivering network and service related object: enables a consumer to express the
intent expectation for the object (e.g. network, service, slice) to be delivered by the system. Examples of such
intent expectations are:
- "Delivering a radio network in the specified area with specified frequency information, transport information,
and radio information (e.g. range of PCI, Cell Id), network capacity and performance information".
- "Delivering a radio service in the specified area with certain service characteristics (e.g. SLS)".
- Intent expectation for network and service related object performance: enables a consumer to express the
performance objectives of the object (e.g. network, service, slice) to be assured. Examples of such intent
expectations are:
- "Ensure the radio network in the specified area meets certain expected RAN UE throughput objectives
(e.g. expected average RAN UE DL throughput, expected percentage of UE with the RAN UE DL
throughout less than 5 Mbps)".
- "Ensure the radio network in the specified area meets certain expected coverage objectives (e.g. expected
coverage ratio, expected average RSRP)".
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 10 ETSI TS 128 312 V17.8.0 (2025-01)
4.2 Intent driven management
4.2.1 Support for intent driven management
In intent driven management, the consumer provides its intent to the producer of a set of management services that
would be consumed in a specific domain. For example, for the purpose of requesting a radio network with a new
coverage, one possible solution (non-intent driven approach) is to use the set of classic MnSs (e.g. provisioning MnS) to
decommission a cell and instantiate the cell to a new Node B for the new coverage. The alternative solution (intent
driven approach) is to use management service produced by the domain, which may be referred to as the Intent-driven
MnS by stating the intent for the radio network for the new coverage, based on the intent, system can trigger actions
(e.g. decommission a cell and instantiate the cell to a new Node B) to satisfy received intent. The Intent driven MnS
could in principle deployed as a replacement of the deployed classic MnSs for the same network and service
management purpose, where the consumer focuses on the 'what' and the producer is concerned about the 'how'.
The producer of an Intent-driven MnS shall allow the consumer to manage the service and / or network resources
through the use of intents. The producer shall support the capabilities for intent fulfilment, which include the following:
- The consumer states the intent to be fulfilled (which can be implemented by createMOI operation on the Intent
IOC) and the producer receives and acknowledges the receipt of the intent.
- The producer validates and then translates the intent to identify which actions are needed for intent fulfilment.
- The producer executes the required actions to fulfil the intent.
- The producer may report about the fulfilment result of the intent.
4.2.2 Intent driven MnS
Introduction of service-based architecture for 5G, in combination with functional model of business roles, exceeds the
level of complexity for managing network in different scenarios (including scenarios for design/planning, deployment,
maintenance and optimization) both in a single and multivendor network. New/simpler ways of managing are needed.
Actions of an intent driven MnS related to the fulfilment of intents may be categorized as intent deployment and intent
assurance. Intent fulfilment refers to the steps taken to satisfy a newly received intent or an update to an existing intent.
The goal of intent fulfilment is to bring the network or service's state to satisfy the new or updated intent. The fulfilment
of some intents may end at the intent deployment, in these cases, if the intent's goal only describes the availability or
presence of a network or service. In other cases, the intent's goal additionally describes the assurance requirements for a
network or service (e.g. quality of service, end user experience, SLS, etc.). In addition to the need of existence of a
network or service. Those intents have their fulfilment tied to the operation of the referred network or service and may
require frequent recurring actions to keep those assurance requirements achieved. This part of the intent fulfilment is
referred to as intent assurance.
An Intent driven MnS allows its consumer to express intents for managing the network and services and obtain the
feedback of intent evaluation result. The Intent-driven MnS producer have the following intent handling capabilities:
- Validate the intent.
- Translate the received intent to executable actions as follows:
- Performing service or network management tasks.
- Identifying, formulating, and activating policies for service or network management.
- Evaluate the result/information about the intent fulfilment, including intent deployment (e.g. the intent is initially
satisfied or not) and intent assurance (e.g. the intent is continuously satisfied).
Figure 4.2.2-1 shows the model of Intent-driven MnS.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 11 ETSI TS 128 312 V17.8.0 (2025-01)

Figure 4.2.2-1: Intent-driven MnS
The intents may be fulfilled by utilizing multiple mechanisms including among others: Rule-based mechanisms, closed
loop mechanisms and AI/ML based mechanisms. These mechanisms can be combined in solutions of various
complexity, ranging from a simple approach rule-based mechanisms, to more elaborate solutions combining AI/ML,
closed loop automation to ensure the fulfilment of intents.
When the intent is created by MnS producer based on MnS consumer’s request, the MnS producer may consume other
management services (including non-intent driven MnS and intent driven MnS) to fulfil or satisfy the intent, e.g.
creating new assurance closed control loop instance(s) or using assurance closed control loop instance (s) to satisfy the
intent. The internal implementation of the intent fulfilment will however not be standardized.
An Intent driven MnS includes the following management capabilities to support intent lifecycle management:
- Create an intent, a MnS Consumer request MnS producer to create a new intent.
- Activate an intent, MnS Consumer request MnS producer to activate an intent when the intent is suspended.
- De-activate an intent, MnS consumer request MnS producer to de-activate an intent for a temporary suspension.
- Delete an intent, MnS Consumer request MnS producer to remove an intent.
- Modify an intent, MnS Consumer request MnS producer to modify the content of the intent (e.g. expectation
targets).
- Query an intent, MnS Consumer request MnS producer to return the content and state (e.g. active, inactive) of
the intent.
4.2.3 Intent translation
The Intent driven MnS producer is the provider of Intent driven MnS and is responsible for deriving activities for
networks and services or other intent(s).
The MnS consumer may consume Intent Driven MnS(s) provided by the Intent driven MnS producer(s) or may have the
consumer role for non-intent MnS producers.
The conflict(s) including conflict between the intent and other intent(s) and/or Non-intent requirements needs to be
detected and resolved during the intent translation. Figure 4.2.3-1 illustrate the potential way to satisfy intent-CSC :
- Intent-CSC MnS producer provides intent driven MnS for communication services. Intent-CSC MnS producers
receive the expressed intent and translate it to Intent-CSP or network requirements, then may consume Intent-
CSP MnS(s) or Non-Intent MnS(s) for network to fulfil the intent-CSC.
- Intent-CSP MnS producer provides intent driven MnS for network services. Intent-CSP MnS producers receive
the intent and translate it to new Intents for NOP or network requirements, then may consume Intent-NOP
MnS(s) or Non-Intent MnS(s) for NE to fulfil the intent-CSP.
- Intent-NOP MnS producer provides intent driven MnS for network equipment. Intent-NOP MnS Producers
receive the expressed intent, and translate it to detailed network requirements, then takes some internal actions to
fulfil the intent-NOP.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 12 ETSI TS 128 312 V17.8.0 (2025-01)

Figure 4.2.3-1: Potential way to satisfy intent-CSC
4.3 Intent driven closed-loop
Intent can be used for management and control of closed-loop automation (e.g. intent can be used to specify the goals
for the closed-loop), which means the intent can be translated to policies and management tasks that the MnS producer
needs to execute for the closed-loop automation. In the intent driven management approach, the mechanisms that the
MnS producer using closed-loop automation mechanisms to satisfy the intent is the implementation of the MnS
producer and shall not be standardized. The relation of the Intent driven MnS and the closed-loop automation with the
Intent driven MnS producer is shown in the figure 4.3-1.

Figure 4.3-1: Intent driven closed-loop
4.4 Relation between rule, policy and intent
An intent specifies the expectations including requirements, goals, and constraints for a specific service or network
management workflow, while a policy specifies the action(s) to be taken when given condition occurs and rules
specifies the explicit or formula logics to be executed. For certain scenarios, policies can be used in conjunction with
intents to achieve the autonomous purposes. Figure 4.4-1 describes the relation between rule, policy and intent in the
"what-how" view. As it now stands, the telecom systems are mainly focused on "how" and "less what". The current 5G
networks brings more operational complexities, and the telecom system need to be able to adapt their operation to the
business objectives of the operator as well as expectations of customer, which is driving customer to shift the focus
from "how" to "what". The first step towards that shift, has been shift from "Rule based management" to "Policy driven
management", with more focus on "how" and less on "what" covering domain specific issues/aspects (an example for
policy is when the average throughput is lower than certain threshold, take specified actions). As technologies are
evolving and the level of complexity exceeds, the need for an abstraction level description (i.e. Intent) becomes more
apparent (an example for intent is the target average throughput for certain area should be assured). An intent driven
system will be able to learn the behaviour of networks and services and allows a customer to provide the desired state,
without detailed knowledge of how to get to the desired state.
ETSI
3GPP TS 28.312 version 17.8.0 Release 17 13 ETSI TS 128 312 V17.8.0 (2025-01)

Figure 4.4-1: Relation between rule, policy and intent
4.5 General concept of Intent Content
4.5.1 Intent Expectation
In the most basic form, a consumer may use an intent to express to the producer the need for:
"an object O with characteristics S".
Where the characteristics S reflect the requirements, goals and contexts for an object.
The object may be a 3GPP managed object like a network slice, subnetwork (e.g. radio network) or other objects like a
service. The consumer may desire the same requirements, goals and contexts for multiple objects with the same
properties, in which case the intent may be stated for a list of objects as
"objects {O ,O , …O } with characteristics S"
1 2 N
However, the consumer may wish to express different requirements, goals and contexts for objects with different
properties. It is in that case necessary to distinguish the requirements, goals and contexts to be achieved for each set of
objects with the same properties. Correspondingly, the combination of requirements, goals and contexts for each set of
objects with the same properties is the Intent Expectation. Also the consumer may wish to distinguish the requirements,
goals and contexts for different objects with the same properties, in this case, the combination of requirements, goals
and contexts for each object instance may be contained in a separate Intent Expectation or requirements, goals and
contexts for the multiple object instances may be combined in a single Intent Expectation.
4.5.2 Expectation Targets
For a given intent expectation, the desired characteristics of the object(s) are the expectation targets to be achieved. The
expectation targets may include the metrics that characterize the performance of the object(s) or some abstract index
that expresses the behaviour of the object(s). A given intent expectation may include multiple expectation targets on the
same object or on different objects with th
...