|
TECHNICAL SPECIFICATION
LTE;
5G;
Management and orchestration;
Intent driven management services for mobile networks
(3GPP TS 28.312 version 17.1.1 Release 17)
---------------------- Page: 1 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 1 ETSI TS 128 312 V17.1.1 (2022-10)
Reference
RTS/TSGS-0528312vh11
Keywords
5G,LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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 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 at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
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
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
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 2022.
All rights reserved.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 2 ETSI TS 128 312 V17.1.1 (2022-10)
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 Web server (https://ipr.etsi.org/).
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™ and LTE™ 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 under .
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
---------------------- Page: 3 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 3 ETSI TS 128 312 V17.1.1 (2022-10)
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 . 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 . 17
6.1 Management operation for Intent (MnS component type A) . 17
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 . 18
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 4 ETSI TS 128 312 V17.1.1 (2022-10)
6.2.1.2 Class definition . 19
6.2.1.2.1 Intent <> . 19
6.2.1.3 DataType definition . 19
6.2.1.3.1 IntentExpectation <> . 19
6.2.1.3.3 ExpectationObject <> . 20
6.2.1.3.4 ExpectationTarget <> . 20
6.2.1.3.5 Context <> . 21
6.2.1.3.6 FulfilmentInfo << dataType >> . 21
6.2.1.4 Attribute definition . 22
6.2.2 Scenario specific IntentExpectation definition . 25
6.2.2.1 Scenario specific IntentExpectation definition . 25
6.2.2.1.1 Radio Network Expectation . 25
6.2.2.1.2 Service Support Expectation . 26
6.2.2.2 Attribute definition . 28
6.3 Procedures for intent management . 33
6.3.1 Introduction. 33
6.3.2 Create an intent . 33
6.3.3 Modify an intent . 34
6.3.4 Delete an intent . 35
6.3.5 Query an intent . 36
7 Stage 3 definition for Intent Driven Management . 36
7.1 RESTful HTTP-based solution set . 36
7.2 OpenAPI specification . 36
7.2.1 OpenAPI document "TS28532_ProvMnS.yaml" . 36
7.2.2 OpenAPI document "TS28312_IntentNrm.yaml" . 36
8 Guidelines for using scenario specific intent expectation for intent driven use cases. 47
Annex A (informative): PlantUML source code . 49
A.1 Procedures for intent management . 49
A.1.1 Create an intent . 49
A.1.2 Modify an intent . 49
A.1.3 Delete an intent . 50
A.1.4 Query an intent . 50
A.2 Information model definition for Intent . 50
A.2.1 Relationship UML diagram for intent (Figure 6.2.1.1.2-1) . 50
Annex B (informative): Intent Life Cycle Management . 52
B.1 Intent Life Cycle Management . 52
Annex C (informative): Mapping the 3GPP and the TM Forum intentExpectation Models . 54
Annex D (informative): Change history . 55
History . 56
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 5 ETSI TS 128 312 V17.1.1 (2022-10)
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
---------------------- Page: 6 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 6 ETSI TS 128 312 V17.1.1 (2022-10)
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
---------------------- Page: 7 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 7 ETSI TS 128 312 V17.1.1 (2022-10)
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".
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
---------------------- Page: 8 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 8 ETSI TS 128 312 V17.1.1 (2022-10)
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. 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
---------------------- Page: 9 ----------------------
3GPP TS 28.312 version 17.1.1 Release 17 9 ETSI TS 128 312 V17.1.1 (2022-10)
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
...